System comments

[RolnCode3]

I've been monitoring the new Sacramento digital/mixed-mode system that is being implemented, and have been running Treport on it. I've been seeing a few system comments or commands (whatever they're called). Can anyone help tell me what is occurring to generate the comment.

Here's most of the comments I'm wondering about:

Rejection ASTRO
Earlier Req to AFF had no reply
System Req for RID to Affiliate
Send Affiliation Request
Interconnect termination
Disabled Function
Group Call to Busy Group

There are a few others, but I can't get them verbatim because I wasn't logging the system.

 

[greenthumb]

Rejection ASTRO: My guess is that a radio is attempting to make an ASTRO call on a talk group that is not deinfed as ASTRO in the central controller, or a radio is trying to use an analog individual ID for an ASTRO call.

Earlier Req to AFF had no reply: In SmartZone, the system will poll each radio every couple of hours to make sure that it is still around and that the talk group that the radio is "bringing up" on the site still needs to be brought up. If the radio does not reply with the affiliation request, the talk group will be torn down and not broadcast on the site. If the affiliation request is acknowledged, the talk group will continue to be broadcast. The message shown here is indicating that an eariler affiliation request that was sent to this radio had no reply.

System Req for RID to Affiliate: See above - this is the system requesting the radio to affiliate.

Send Affiliation Request: My guess here is that a standalone terminal (e.g. Site Lens, SystemWatch, etc.) has been manipulated to send a radio check to a radio. This command could be that statndalone terminal telling the central controller to send a system request for a radio ID to affiliate. You probably saw the "System Req for RID to Affiliate" command sent shortly after this command.

Interconnect termination: This is simply stating that a telephone interconnect call has ended.

Disabled Function: Could be a bunch of things: Radio not enabled to make a systemwide call attempting a systemwide call, same for a private call or call alert, etc. I couldn't venture to guess which one this might be, but in general - it was a radio attempting to perform a function that had not been enabled for that radio on the system.

Group Call to Busy Group: This is a simple busy call - there wasn't a trunking repeater available on the system when the call was placed, so the user was placed into the busy queue until a trunked repeater was available.

There are a few others, but I can't get them verbatim because I wasn't logging the system.

You may want to check some of Treport's documentation, I think that some/most of these are defined in it. Good luck!

 

[RolnCode3]

I did look in the FAQs and the other text files in the Treport folder. It lists the system comments, but provides no explanation as to what they mean. At least that I could see. I did pull one of the commands I couldn't remember from there. I don't know where the Treport webpage is, if there is one.

A few of these I kind of figured were self-explanatory (such as the Busy Group one and the Disabled Function), but thought maybe there was more to them.

Thanks for the answer.

 

[WayneH]

I haven't gotten around to writing a FAQ on what every event means. It's easier to answer each question. It also helps to include the whole event or the code in brackets at the end. I haven't had the chance to ID every rejection event. Some explanations are educated guesses like the disabled function one.

"Earlier Req to AFF had no reply" This happens when the radio reappears on the system and never acknowledged the request earlier. Generally it's because the radio left the system and did not deaffiliate.

"Send Affiliation Request" GreenThumb is correct. A user terminal or console sent a request to a radio to affiliate to whichever site it's on. There's a passive command with TREPORT, if you've been running it long enough, which is similar. You enter the radio id and it will tell you the last TG the radio had activity on (By Aff or Call for example). See docs.

The interconnect termination often occurs when a button is programmed for interconnect yet the system doesn't allow it. When the subscriber pushes this button this rejection is sent. It also happens on interconnect enabled systems and means as GreenThumb stated.

Also, you can check the Yahoo Group for Treport and search the archives. If all else fails just email me. My attendance on the forums lately is very random.

-Wayne