And can that be batch loaded into ProScan, somehow? Say you run it for 1-2 weeks and then import the aliases.
New Jersey Interoperability Communication System (NJICS)
- Thread starter etr37
- Start date
The NJICS only broadcasts console aliases, not subscribers.
And no, OTA aliases for ASTRO 25 systems are not deployed "by individual subsites" (I think you probably meant site; subsite refers to one of multiple physical sites that make up a simulcast cell).
OTA aliases is a per-system option that is enabled/disabled within the Radio Capabilities Profile. Systems can have multiple profiles that subscribers are assigned to, ergo you may have a subset of subscribers with OTA enabled and some disabled. As per usual, nothing cut and dry with these very complex systems.
And no, OTA aliases for ASTRO 25 systems are not deployed "by individual subsites" (I think you probably meant site; subsite refers to one of multiple physical sites that make up a simulcast cell).
OTA aliases is a per-system option that is enabled/disabled within the Radio Capabilities Profile. Systems can have multiple profiles that subscribers are assigned to, ergo you may have a subset of subscribers with OTA enabled and some disabled. As per usual, nothing cut and dry with these very complex systems.
- Joined
- Dec 22, 2005
- Messages
- 1,915
That is outstanding thanks. Hypothetically if Elizabeth who primarily use Site 7 decided to enable this feature in subscribers profiles would it work, or can it be inhibited system wide? I wonder if Group Services option is related.
Again, sites has nothing to do with the OTA aliases; it's done at the system level within Provisioning Manager on a subscriber basis. Specifically the Radio Capabilities Profile Security Group(s) must have the Radio Alias Update parameter set to enabled. If the system has only one Radio Capabilities Profile, then it applies to the entire system. If there are multiple Radio Capability Profiles (most likely the case), then the feature can be enabled individually for each profile, and thus would only apply to a subset of subscribers.
In your example, Elizabeth would need to have their own unique profile in order to enable OTA aliases (or be part of a profile that has the feature enabled). Of course this would need to be enabled by someone with access to Provisioning Manager and the ability to make changes to the Radio Capabilities Profile, which would most likely be the state themselves, not individual agencies.
Group Services is the APX subscriber feature that must be purchased in order to display the OTA aliases in the radios. If Elizabeth has Group Services in their APX radios and they enabled decoding of OTA aliases, they would see whatever the state provisioned to be encoded. In this case, console aliases.
In your example, Elizabeth would need to have their own unique profile in order to enable OTA aliases (or be part of a profile that has the feature enabled). Of course this would need to be enabled by someone with access to Provisioning Manager and the ability to make changes to the Radio Capabilities Profile, which would most likely be the state themselves, not individual agencies.
Group Services is the APX subscriber feature that must be purchased in order to display the OTA aliases in the radios. If Elizabeth has Group Services in their APX radios and they enabled decoding of OTA aliases, they would see whatever the state provisioned to be encoded. In this case, console aliases.
Similar threads
