Page Type: REFERENCE
Normally a trunked system is scanned in ID-SCAN mode, where only selected talkgroups are received, and each received talkgroup is routed to a unique channel on Rangecast. An alternative is scanning a trunked system in ID-SEARCH mode, where all traffic received from a specific broadcast tower (regardless of talkgroup ID) is received, and all traffic is routed to a single channel on Rangecast.
To receive a system in ID-SEARCH mode:
1) Choose a custom channel ID for this content. Although this is from a trunking system, a conventional code is used (e.g. CX99999) because reception does not involve writing a talkgroup ID to the scanner programming.
1) In the Hub Overrides text entry form, compose a line in this format:
CX99999:f=L12345,r=50,n=Name to display
... where the frequency parameter (f) is the ID of the broadcast tower, and the receive parameter (r) is the ID of the receive site. Other parameters normally used to define custom channels may be applied, such as a channel name (n) or geocode (g).
The tower ID can be obtained from the programmer (if the system is listed there), or the Rangecast channel database query utility otherwise. (Entering the system ID as the search parameter in that utility results in a list of towers at the end of the page.)
Reception in ID-SEARCH mode does not conflict with receiving talkgroups from the same tower in normal ID-SCAN mode.
If reception of a tower in ID-SEARCH mode results in more than 1 Erlang of content, there may be some unexpected behavior in the player when in HOLD mode on this channel, in particular greater fallback in time than would be expected under the circumstances (player modes to limit fallback.) The player assumes that fallback cannot happen in HOLD mode, since a normal broadcast channel is naturally limited to 1 Erlang, so certain fallback protections are not applied.
INDEX