PJH
Member
- Joined
- Aug 23, 2002
- Messages
- 3,622
- Reaction score
- 87
Well, not really if you take a proactive approach to this sort of thing. If a system manager was proactive, you would disable all valid range ID's and set it to auto inhibit. You can also run reports that will show unexpected affliations then you can log those ID's. If you need need to change a radio ID, assign a new one to the affected radio, leave the other one active with an inhibit command on next log in. Problem will cure itself really quick.
2nd fun trick is to place all unassigned/lost/stolen ID's to a talkgroup regroup with a message. San Diego did this at one time (or still does). With a little detective work (unless you zap those ID's too) is see what site they are on, monitor the local email lists and here and I am sure you will come up with a couple of people to visit.
In my case, we have all unassigned ID's affiate to a statewide talkgroup and its logged by site. This way we can remotely allow full TRS access or let them sit there without being able to access the other talkgroups. You might have 30 TG's in the radio, but it reverts back to the TG of our choice.
Lots of little tricks one can do with Motorola's or a few third party system monitoring software packages.
2nd fun trick is to place all unassigned/lost/stolen ID's to a talkgroup regroup with a message. San Diego did this at one time (or still does). With a little detective work (unless you zap those ID's too) is see what site they are on, monitor the local email lists and here and I am sure you will come up with a couple of people to visit.
In my case, we have all unassigned ID's affiate to a statewide talkgroup and its logged by site. This way we can remotely allow full TRS access or let them sit there without being able to access the other talkgroups. You might have 30 TG's in the radio, but it reverts back to the TG of our choice.
Lots of little tricks one can do with Motorola's or a few third party system monitoring software packages.
