They were probably typing fast and added an extra zero to APX 900.Apx9000? 🤔
Me too hahaThey were probably typing fast and added an extra zero to APX 900.
Though it could be a foreign radio.
Just went through a PM refresher course a couple of months ago. Motorola instructor very specifically said that the most the system will show is that licensing capability has been exceeded, or needs to be purchased at some time. Enforcement will be at a later date. It was interesting how many features, and hardware could be added without an appropriate license, with only a warning being provided to the system administrator. Educated guesses were that it may be more than a year, think covid impact, before anything changes.A couple of other items RE Group Services.
To clarify, the alias update originates in PM. It is NOT changed by a field unit.
Available w/APX subscribers only.
Group Services is available on P25 trunked systems WITHOUT IV&D. (7.17.x and later I believe) BUT, group services requires system licensing. (Along with subscriber radio feature set). Whether the system licensing is enforced,,,,,,,, (My opinion is even if Moto is currently not enforcing group services system licensing, there will be a day when they do.) Current suggested list. $5K per 500 subscriber units.
Sorry to side track from UCL conversation.
IMO - the less people that have access to the PM, the better. If the user can update their own alias via their subscribers menu like MOTOTRBO then it has the possibility (with proper template setup and the right user training), to save a lot of headaches with subscribers that traverse neighboring systems for MA
That right there is the biggest Catch-22 when it comes to this feature. I worked with one of my customers to implement subscriber-based aliasing (6500+ radios) on their Capacity Max system (being there is no “PM” for administrative OTA alias group changes) and for the past month there haven’t been any users that purposely enter fictitious handles. The configuration was setup so that on power up they had to enter an alphanumeric string or press the ok (or PTT) button to leave the Alias unchanged from the previous power up. From watching the NBI traffic I can say that users are entering their first + last initial followed by their PID number DS-770896. Now that’s not to say that in a few months we won’t start seeing fictitious handles, but that’s what write ups and disciplinary actions help enforce.All you need is a flock of firefighters who create alias names like "HOTLUVR" and other such nonsense (and I know people who would do that) for some serious havoc to result.
Well stated. Once we start giving users too much autonomy, control of our systems goes away. And once we give them a feature, good luck on taking it away.Subscribers being able to update their own alias would be a major headache, IMHO. All you need is a flock of firefighters who create alias names like "HOTLUVR" and other such nonsense (and I know people who would do that) for some serious havoc to result.
Changing alias names etc in PM should stay with PM; no "field updated" alias names or other info should be allowed.