Registration; RID=1 REFUSED

[16b]

It's on each P25 system.View attachment 174984

There is a note in the help section that says:

Each trunking system can set different SUID, this feature is only for G5N Model. If you are using old Gx model, you can set the SUID on "Conventional Group ID Setting / Pager ID Setting" page.

I don't know what a G5N model is (I have a G5, never heard of a G5N), but it's probably a good idea to adjust the SUID in the other location it mentions (screen E6, click on the "Pager ID Setting" tab) also. You have the same options there--setting an ID or unchecking the "Enable" box.

I expect it would be enough to simply uncheck the "Enable" box, but to be on the safe side I set all of my SUIDs to something other than "1" before disabling. If any of you system admins wants to experiment and let us know if unchecking the box is enough to cause the pager to ignore inhibit commands, please do

 

[KevinC]

If any of you system admins wants to experiment and let us know if unchecking the box is enough to cause the pager to ignore inhibit commands, please do

And hope it responds to the uninhibit command if it doesn't ignore it.

 

[GTR8000]

And hope it responds to the uninhibit command if it doesn't ignore it.

I believe it will. This happened to us a few months ago, details are fuzzy, but a big surprise to say the least.

 

[RaleighGuy]

There is a note in the help section that says:


I don't know what a G5N model is (I have a G5, never heard of a G5N), but it's probably a good idea to adjust the SUID in the other location it mentions (screen E6, click on the "Pager ID Setting" tab) also. You have the same options there--setting an ID or unchecking the "Enable" box.

I expect it would be enough to simply uncheck the "Enable" box, but to be on the safe side I set all of my SUIDs to something other than "1" before disabling. If any of you system admins wants to experiment and let us know if unchecking the box is enough to cause the pager to ignore inhibit commands, please do

G5N is a newer model which had a different chip in it.

When I click disable in both E2 and E6 (and save it) and go back in to the setting it is back to enabled and 1 again. However, if left enabled and changed to something greater than 1 it does save it. All mine currently say no setting.

 

[rr60]

This is an excellent thread, I care for (pro bono) about a dozen G5 for various responders. I have some work to do. Folklore had some other locals G5’s stunned that had to go back to Uni, now I understand. Thanks all.

 

[GTR8000]

I just refreshed my memory...most of the Unications responded to the uninhibit command, however at least one G5 did not (unsure of the vintage/firmware)

 

[Echo4Thirty]

My strategy was to put my NAS and Unication RIDs way outside of the range of IDs that were in use on the system. Typically something random in the 16 million range. Of course if some knucklehead happens to use that ID and gets his radios shut off while I happen to be listening,, I am hooped as well. But I figured the odds were much better than using an ID in the ranges that they have in use.

 

[GTR8000]

The upper range of UIDs is normally reserved for ISSI roaming/temporary working dynamically assigned UIDs, when the system is ISSI capable and provisioned as such.

 

[billy2047]

I've been seeing several "Registration; RID=1 REFUSED" entries when monitoring our state's (TACN) system.

Interesting, it looks like TACN radios have full spectrum CC scan, non adjacent site search and/or Intra WACN all enabled then? I've seen a few attempting to register on our system during DXing when atmospheric conditions were right and we're states away from TACN. And yes we do log/monitor our systems very closely.

 

[nhfdcadet]

Am I correct to assume that if it is left as no setting, it would not validate any stun command as it doesn't have an ID?

 

[wa8pyr]

Radios need to register before they can affiliate.

Sorry, just couldn't resist.



That being said, some system administrators occasionally enable RID 1 just to see what shows up; then they hit the kill switch to inhibit the culprits, and then disable RID 1. I did it a couple of times on our old Type II system; caught a couple of rogue radios in the process.

I enjoyed a hearty, evil belly laugh after that.

 

[DVINTHEHOUSEMAN]

RID 1 is somehow a valid ID on WISCOM. Someone was lazy and assigned it to a unit on SWLAW1 (TG 55501). Saw it show up in my PRO96Com logs when I left it to monitor my control channel to log TG's.

 

[RaleighGuy]

RID 1 is somehow a valid ID on WISCOM. Someone was lazy and assigned it to a unit on SWLAW1 (TG 55501). Saw it show up in my PRO96Com logs when I left it to monitor my control channel to log TG's.

Was it a regular unit, or a service tech, comm manager or other specialized position used for testing or repairing the system?

 

[DVINTHEHOUSEMAN]

Looked like a regular unit to me as I saw it pop up in voice grants almost every time (over the span of the better part of a year) a deputy was in NE Sawyer county and dragged that TG onto my site. Never saw it aff directly to the site. Unfortunately since PRO96Com only decodes CC data I have no record of what was actually said. Radio techs would be in the range of 81X08XX.

 

[krokus]

As for Unication, why they chose to do anything with the inhibit packet is beyond me except that maybe they wanted a way to shut off stolen system pagers. Since they can be keyloaded, If our users had them I would like a way to shut them off just as I would a two-way radio that was lost/stolen.

It might carry over from the European models, where they can be used on GSM.