Amount of time MSU waits for a
busy conventional channel to be
available to proxy LPSU call
request before denying the request.
Amount of time the MSU will stay
on the control channel to proxy a
system response for a given
signaling request from a LPSU.
P25 Trunking OTAR via VR
For the MSU interfaced to the VR to provide packet data services to associated PSUs on a P25
Trunking system, the MSU must be configured for packet data operation and must be context
activated on the system.
MSU Scan Programming Requirements
The MSU Scan feature is allowed while the VR is active (System or Local Mode) if the MSU Scan
type is configured as one of the following:
• Trunking Scan
• Conventional Scan
• Mixed Conventional Voting Scan
• Legacy Voting Scan
• Multi System Scan
• Priority Monitoring
The MSU does not support any other modes of scan operation, apart from those listed above,
while the VR operates in SYSTEM or LOCAL mode. In such unsupported cases, the MSU will
automatically suspend scan operation when the VR is set to SYSTEM or LOCAL mode of
operation and resume it when the VR is OFF.
NOTE:
The LPSU calls will be repeated on the MSU Selected Channel.
MSU Group Services Programming Requirements
The “Group Text Messaging Service” in the corresponding Trunking system screen has to be set
to ‘Full Decode’ in order to enable the Group Text Feature in the MSU.
To enable the Group Alias Update feature, the MSU must have the ‘OTA Radio Alias Type’ set to
‘Decode Only’ in the corresponding Trunking system screen.
The MSU may have Group Text Messaging Services and/or Group Alias Update disabled so it
will not store group texts and update its UCL but will still pass along the group texts and alias
updates to the VR and its affiliated PSUs.
To Next Page
Loading...