IDAS MultiTrunk Configuration Guide 5th Ed
IDAS MultiTrunk Configuration Guide 5th Ed
12421 Willows Rd NE
Kirkland, WA 98034
TABLE OF CONTENTS
Part One
BEFORE YOU BEGIN
PROGRAMMING
1 Introduction
IDAS Multi Site Trunking blends IDAS 6.25 conventional and trunking technologies, LTR-like
channel efficiencies, and multiple site-roaming capabilities to form an efficient and
affordable trunking system.
With the latest firmware and software upgrades available on the Icom Dealer Business to
Business Knowledge Base, the radios in conjunction with the FR5000 series
Repeaters/Controllers can be used as part of a feature-rich multiple site trunking system.
IDAS Multi-Site Trunking requires that the Installer/Programmer be familiar with all aspects
of the set-up and theory of Multi-Site Trunking. It is mandatory that they become very
familiar with this manual before attempting to install and operate and IDAS Multi-Site
Trunking system.
2 Applicable Radios
The procedures and descriptions in this guide apply to the following radio models.
• F3161/F3261 series portables
• F3210D series portables
• F3230 series portables
• F3400D series portables
• F5400D series mobiles
• F5061 series mobiles
• F5220D series mobiles
All software windows in this guide are from the CS-F3160/F5060 cloning software.
3 Prerequisites
Important: Do not proceed with configuration or installation of an IDAS
Multi Site system without fulfilling all the requirements listed below.
• IP Connectivity must be installed by an IT professional. Because there are countless
variables in the ISP provider’s internet configuration, Modem setup, and router choice
and configuration, you must use an IP professional to set up your internet connection to
allow 2 way IPSec/voice traffic with the IDAS system. Icom is not able to troubleshoot
your connection problems remotely, thus the requirement of an on-site professional.
• Obtain the following IP information from your ISP, per site:
Internet connection type (Static IP only)
IP address
Subnet mask
Default gateway
DNS
User name and Password (if applicable)
• Use Icom’s IP numbering system. Using our IP system gives our technical support the
ability to troubleshoot multi site issues effectively.
• Remote Connectivity. Icom recommends that all sites be configured so that they can be
accessed remotely, if necessary. There may be situations where the Administrator may
require that Icom be able to access the Routers/Controllers on the site to inspect
settings.
• All IP Addresses Must be Static.
• You must use VPNs with the system if using the public internet. Using VPNs (if using the
public internet) provides the system with necessary features: proper data authentication,
access control, confidentiality, and data integrity.
• Select an Appropriate Router. Router Selection is the responsibility of the dealer,
customer, and IP professional. There are many variables to consider such as cost,
reliability, and commercial grade. The dealer’s choice is entirely up to his team and will
require your IP professional to configure.
• The IDAS multi site trunking system is for 6.25kHz digital only, not P25 digital or analog.
• Icom recommends a minimum 40kbps (kilobits per second per voice path) Internet
connection speed. Refer to the following link for further information. For additional
information, refer to this link: Bandwidth Requirements.
4 Equipment Requirements
• FR5000 Repeaters with UR-FR5000 module(s)
• UC-FR5000 Controller Board Installed with MCU Firmware version 3.0 or greater installed
and SCU Firmware version 3.0 or greater installed.
• Uninterrupted Power Source for repeaters, routers, and modems. This is because even a
momentary loss of power results in all equipment re-initializing. It can take a minute for
repeaters and controllers to be functional, causing all radios to de-register.
5 Components
The following describes the hardware that is required to assemble a Multi-site Trunking
system.
5.4 Router
One Router per site. Router choice is determined by your IP professional. Router screen shots
in this Guide are for reference only.
9 Bandwidth Requirements
Understanding and establishing the Bandwidth requirements for your system is an essential
prerequisite. The following paragraphs describe in detail the necessary specifications.
9.1 Introduction
An Icom Multisite Trunking site requires 100kbps of minimum bandwidth to maintain
baseline data exchange/synchronization between sites. In addition to this 100kbps, each site
requires a continuous 40kbps minimum of bandwidth per voice path to and from that site.
These bandwidth requirements assume levels that are minimal and 100% continuous. It
should be understood that other users on the network can impact this minimum bandwidth
to a degree where bandwidth is reduced to levels insufficient to operate the Icom
equipment, especially at hours of peak use.
Icom recommends that a system be administrated by an IP Networking professional and that
it be monitored 24/7. This enables system security and consistency, and allows for
troubleshooting any communications abnormalities. Since Multi-site efficiency is possible
only with efficient network communications, operators must be aware of the network’s
condition at all times.
9.2.1 Notes
• These values are for reference purposes only and are subject to change without
notice.
• The network latency is one-way latency (i.e. not “Round Trip Time” as measured by a
PING command).
• As an additional method for monitoring and controlling network performance and
device conditions, Icom has used network monitoring software such as “The Dude”
from Mikrotik, PRTG Network Monitor (http://www.paessler.com/prtg) and
SysUPTime (http://ireasoning.com/network_monitor.shtml). Many network
monitoring software products are free for trial or evaluation with limited
SCU and WEB access show the greatest bandwidth usage, but they do not send data until
they receive a request, so the bandwidth will be larger if the delay is smaller, as in a LAN
environment. The Voice frame is UDP so it will be lost when the bandwidth is not large
enough. Firmup/Web packets are TCP or HTTP so the client will send a request again if the
bandwidth does not have enough capacity.
The first service degraded by a restricted network bandwidth will be Web access.
1 Introduction
The following paragraphs describe only the settings that are particular to programming
repeaters and subscriber radios for a Multi-site Trunking System.
2 Programming Repeaters
The following describes the basics of programming for IDAS Multi-Site Trunking. For standard
IDAS Features, refer to our FR5000/FR6000 Repeater Programming Guide, which can be
found on our Dealer B-B Knowledge Base.
1. Go to Memory CH.
2. Enter your RX and TX frequencies.
3. In the Operation Mode field, select Full-Duplex.
7. Ensure that Synchronization Error Parameter counter (N7) is set to 5 for both the
radio and repeater. This value allows data to pass between the radio and repeater at
the same rate.
Zone Window
Prefix ID Use this radio’s Prefix ID as entered in the Fleet Settings -> Unit
Settings Window of the UCFR5000 Controller programming.
Unit ID This radio’s Individual ID when on this channel.*
*ID’s can be assigned on a channel by channel basis or by assigning a Global ID in the Digital -
> Option window.
For additional information, click on the following links:
• Fleet Structure
• Programming Prefixes
• About Individual IDs
• About Call Routing
Site Code Enter in the Site Code from the Site Settings-Site Management
window of the UC FR5000. The Site Code must match the number
in the No column.
Repeater Channel Double-clicking this field opens up the Repeater Setting window.
This is where you enter Repeater Frequency Sets (the
corresponding radio frequencies) for all repeaters, along with
corresponding repeater numbers from 1-30 (as programmed in
the UC FR5000 controller programming). The assigned Collect
Channel repeater number will also be displayed in the Multisite
Trunk-Site List window.
Area bit As set in the Trunk Site Settings -> Area window of the UC-
FR5000 controller. Normally set to Off.
Data Write Inh Set to Enable to allow Over the Air Updates.
3.2 Registration/Deregistration
3.2.1 Introduction
Registration to a site occurs when a radio is first turned on or is roaming. Current radio
software and firmware uses two methods for registration/deregistration: Time based and
Message based.
The System Administrator must evaluate both methods of site signal analysis described
below and determine the best option for their customers.
Setting Description
Setting Description
Note: All radios in
a fleet are not Roaming Priority • Last- During roaming, the radio first looks at the last site
required to have the radio was registered on, followed by the Home Site,
the same Home then Adjacent Sites. If none of these sites are available,
Site in a System, the subscriber looks at the remaining sites.
nor is this setting
• Home- During roaming, the radio first looks at its
related to the
programmed “Home” site, followed by the programmed
Home Channel in
Adjacent Sites. If none of these sites are available, the
a site.
subscriber looks at the remaining sites.
• Adjacent- This is also called “Strongest Site Search” and
allows the radio to find Adjacent Site RSSI signals and
choose the strongest one. Note: This can increase
roaming time to unacceptable levels.
In-range RSSI Sets the minimum level that the radio uses to attempt to register.
For example: a setting of -97 results in the subscriber, while
roaming, attempting to register on the first site it sees that is
stronger than -97dBm.
Adjacent RSSI Sets the minimum level the subscriber will consider when
performing a strongest site search. This is active only when
Adjacent is selected in Roaming Priority. Note: This will increase
roaming time considerably.
Setting Description
Roaming configuration
Setting Description
In-Range Judgments
Used during the roaming process for making decisions on which sites the subscribers will
consider registering on.
Setting Description
Note: All radios in
a fleet are not Roaming Priority • Last- During roaming, the radio first looks at the last site
required to have the radio was registered on, followed by the Home Site,
the same Home then Adjacent Sites. If none of these sites are available,
Site in a System, the subscriber looks at the remaining sites.
nor is this setting
• Home- During roaming, the radio first looks at its
related to the
programmed “Home” site, followed by the programmed
Home Channel in
Adjacent Sites. If none of these sites are available, the
a site.
subscriber looks at the remaining sites.
• Adjacent- This is also called “Strongest Site Search” and
allows the radio to find Adjacent Site RSSI signals and
choose the strongest one. Note: This can increase
roaming time to unacceptable levels.
In-range RSSI Sets the minimum level that the radio will attempt to register to.
For example: a setting of -97 results in the subscriber, while
roaming, attempting to register on the first site it sees that is
stronger than -97dBm.
Adjacent RSSI
Sets the minimum level the subscriber will consider when
performing a strongest site search. This is active only when
Adjacent is selected in Roaming Priority.
Setting Description
Each Idle message is composed of 4 Control Frames, each of which has 3 “messages” or
“Words” in it. Complete Idle Messages are counted over a Sample Period of 40, 20 or 10
seconds. The radio must see a minimum number of complete Idle Messages over this sample
period in order to stay on the site.
Example: Let’s say Site 1 is designated as a Large Site in the UCFR5000 Web Settings; In the
subscribers, make the following settings.
Detect Number of Control Frames Since there are 4 Control Frames per Idle message, this
represents 2 complete Idle messages (8/2=4) necessary
within the sample time.
Timeout of Control Frame Sample Period for Idle Message check. This corresponds
to the Site Size as transmitted by the registered site.
In this example, the radio will require that it receive 2
perfect Idle Messages ( 8/2 ) in a 40 second period.
Message Error Rate: Number of Error Codes per Sample of Control Frames
An Idle Message has 4 control frames in it and each Control Frame has 3 “messages” within
it. As these Control frames are received, the presence of a CLC or Error Code is counted as an
error in the counting process. The radio counts up the Error Codes
Setting Description
Continuous Error Count Set to 3. This is the number of Error Codes (messages
with errors) detected within the Number of Sampling
Frames setting.
Number of Sampling Frames Set to 16. This is a rolling number of frames the radio
inspects to see the number of errors. Example: If the
radio sees an error it will check the next 16 frames to
see if there is a total of 3 errors in that group. If there is,
the radio will go into roam.
Number of Allowance Set as depicted in the Settings sheet that follows. This is
the number of error rate occurrences allowed. Example:
3/16 is one occurrence. If this occurs again, that would
be 2.
UCFR5000 Settings: Each Site Master has its site designated as Small, Medium, or Large.
This programming parameter is transmitted to the subscribers in each idle message. The
subscribers refer to their own Digital Options screen and use the settings designed for Small
or Medium or Large when making roaming decisions. A subscriber will use the Large Zone
settings on one site, but will use different settings (Medium or Small) if the radio roams to a
Medium or Small site.
Setting Description
Talk Back Timer Subscriber will transmit in the same mode (Analog or Digital)
and/or call type (Individual Call or TG Call) for this period of time
after receiving a signal. If set to “Off” the radio will always transmit
as programmed in the subscribers memory channel settings.
RX Type Determines when the Talk Back timer will be operational.
— Voice Only. Operates when receiving voice calls.
— Normal. Operates when any call, voice or other features (such
as call alert), is received.
Talk Back Lock on PTT When radio receives a call, then receives a 2nd call with a different
mode within the Talk Back Timer time period, the radio will retain
the first mode. After the timer has elapsed, the next call
determines what mode the Talk Back will be in.
Setting Description
Prefix ID/Unit ID Determines if the Prefix and Unit ID will be assigned on a channel by
channel basis or globally
• MR Ch Individual: The ID and Prefix are programmed on a
channel-by-channel basis.
• Global (Edit): The ID and Prefix are assigned globally in the
Prefix and Global ID settings below.
• Global (Auto): Prefix is assigned below. The Unit ID is
generated based on the serial number of the radio.
Note: This feature is not recommended.
Synchronization Error Parameter counter (N7)- Set to 5 for both the radio and repeater. This
value allows data to pass between the radio and repeater at the same rate.
Setting Description
Ack TX Delay Leave at Default. Set the time (in seconds) to delay
transmission of the acknowledgment signal after receiving
a Status, Status request, SDM, Call Alert, Radio Check, Stun,
Kill, Revive or Remote Monitor call. Range between 0.000
and 60.000 sec.
Ack RX Wait(sec) Leave at Default. The time allowed for receiving an ACK
after a transmission. It has to account for IP delay and the
delay incurred by multiple repeaters.
Attempt No Leave at Default. Set the maximum number of times the
radio transmits a call attempt without receiving an ACK
(Handshake) when PTT is pressed continuously.
Handshake Timer Leave at Default. Set the time period to wait for the
Handshake of the Single-site and Multi-site Trunk
operation. Range within 0.000 to 60.000 sec.
Wait Timer For Network Delay Leave at default. This timer increases the waiting time for
the radio to receive an acknowledge signal from the
repeater. It is used in addition to the Ack RX Wait timer in
situations where excessive network delay makes the radio
require more time to wait for that Ack. The total wait time
is the sum of both timers (see the following graphic).
Setting Description
Primary Talk Group and Enter a value when the Dec. Pri. TG (Decode Primary TG)
feature is being used. This radio will decode its own TalkGroup
Prefix ID
and whatever Primary TalkGroup is entered in this setting.
Block Mode Enable or disable the ability to decode Talk Group ID’s (within
the programmed Prefix ID) within the range specified by Start
ID and End ID. The radio will decode any TGID within this
range.
RX Broadcast Grp ID If enabled, this radio will always receive from the Talk Group
assigned. Prefix ID is assigned in RX Broadcast Prefix ID. The
radio will not automatically transmit on this Broadcast group.
Channel Group: Set to ON to to enable the Channel Group Table/feature in the radio.
2. Quickly press the User Set Mode key repeatedly until RSSI shows on the radio screen.
3. Press the Ch Up key until you see the parameter you want: RSSI, BER or Site
Number/Packets.
4. Pressing any key/button causes the radio to leave this mode.
For Site Number and Packets, you should see the packets increment in sets of 4 if the packets
are perfect. If the packets show less than 4, some degradation is occurring.
• Large Site: You will see at least 26 good packets every 40 seconds to stay on the site.
• Medium Site: You will see at least 13 good packets every 20 seconds to stay on the
site.
• Small Site: You will see at least 14 good packets every 20 seconds to stay on site.
Part Three
CONTROLLER PROGRAMMING
Important: Use only Static IPs. This is due to the high availability and
reliability of static IPs.
Important: Do not proceed with configuration without ensuring that the
Prerequisites have been met, as described in the Before You Begin Programming
folder.
Important: Before proceeding, plan all IP addresses, Site Numbers, repeater
job functions and numbers (Collector and Home Channel assignments), and Voice
Channel priority assignments. Reading and understanding this manual is mandatory
in establishing a system that works properly.
2. Enter the default User Name and Password and click OK.
Top Menu
General Settings
Note: If any
The General Settings window includes setting the IDAS operating mode and configuring the
setting is not
network information.
understood, it is
best to leave it at Operation Settings
default. The Operation Window includes Area Bits, various signaling timers for that repeater,
Repeater Number assignment, Cross Busy settings, repeater voice channel priority settings,
Note: Any screen
and non-Multi-Site trunking parameters.
programming
changes must be Multi-site Settings
followed by This window contains the settings for the System Master, Site Master, Collect, Home and
clicking WRITE to Voice channels.
activate the Maintenance
settings. The Maintenance window contains the Site/Repeater settings such as file saving, firmware
updates and current revisions, and Log In.
Initialization clears UC card and CF card settings and returns them to factory default settings.
IMPORTANT Icom always recommends initializing each UC card before any major programming change,
Always initialize such as changing from Conventional to Multi-Site or Single Site Trunking.
the repeater
before
programming.
This should be
performed any
time a CF or UC
card has been
added to the
system.
Previously
entered settings
can conflict with 1. Go to Maintenance at the Top Menu.
new settings
unless the
repeater is Initialize Window
initialized.
6 General Settings
1. Assign the mode for the Controller board and network settings.
Operation Mode Window
3. Go to Network Settings.
Network Settings Window
Note: Network
settings apply to
this repeater only.
Authorization Window
IMPORTANT
Do not use this
feature unless
this warning is
understood
completely.
Misuse of this
feature may
disable your
repeater. Icom
recommends that
this feature be
left at default.
• Once this window is populated, no other device can be used to program the repeater.
• Once populated, the Controllers will then need to be sent to Icom for re-setting.
• Icom STRONGLY recommends not entering any data on this window.
3 Operation Settings
Area Window
The Area bit is used to differentiate between two Sites with identical frequency sets during
the registration process. Leave all settings at OFF.
Idle Message
IMPORTANT This setting is for Single-site Trunking use only. Leave at default.
Hold Timer for Timer
Normal Program/check the following settings.
Leave at 1.2. Setting Description
Shorter times will
result in longer or Hold Timer for Normal The minimum allowed time the repeater will stay
failed Handshake engaged after a Handshake Attempt while waiting
times. for the subscriber to respond.
Hold Timer for Data Ack The minimum allowed time the repeater will stay
engaged after a Signaling Attempt that requires an
Ack (Emergency, Radio Check, etc…) while waiting
IMPORTANT for the subscriber to respond.
Hold Timer for Hold Time for Message Trunk Mode If Message Trunking is used, this is the time that
Data Ack the repeater will stay engaged for that particular 2
way conversation. Currently not operational.
This time must be
longer than the
setting in the
subscribers Ack RX
Wait timer.
Shorter times will
result in failed
acknowledgments.
The Cross Busy feature acts as a busy channel lockout for either uplink or downlink,
depending on your programming.
The following table describes the Cross Busy Function.
Setting Description Action
Uplink Monitoring If set to Enable: The repeater monitors the RSSI Generally,
of the repeaters RX Channel. Any signal that leave at
exceeds the “RSSI Level (dBm)” (lowest level) Disable
disables the repeater’s TX function as long as the
signal is present. If set to Disable: The repeater
doesn’t monitor RX frequency signals.
Downlink Monitoring If this feature is set to Enable, the repeater will Generally,
monitor the TX frequency of the repeater. leave at
Disable
For more on Cross Busy Monitoring (Downlink Monitoring), click: Cross Busy Monitoring.
Set this repeater for Low Priority, Middle Priority, or High Priority.
Note: Each Information for this window is for repeaters that are or will be Home Channels for this
potential Home particular site. If there is more than one Home Repeater in a site, then this window will need
Channel must have to be filled out for each of those Home Repeaters (and future Home Repeaters). Each Home
a Free Repeater list Repeater will be filled out differently. You do not need to fill out this window for non-home
programmed in it channel repeaters.
to determine traffic • This repeater ID (the Home Repeater) should always be High Priority. The first voice
priority path will always be assigned to this repeater.
assignments.
• The System/Site/Collector ID should always be Low Priority and will be the last-resort
Please fill out the
Multisite Trunking voice traffic assignment.
Work Sheet/Voice • Voice channel IDs should all be set for Middle Priority. Voice channels (after the
Priority Worksheet Home Channel) are assigned randomly amongst the “middle” assigned repeaters.
in Before You Begin • In any Free Repeater Assign screen, there should be only one High Priority checked
Programming for (always THIS repeater number, only one Low Priority checked ((Control Channel), and
each site prior to
the rest set at Middle Priority.
UC FR5000
programming.
For more details about assigning repeater priorities, click: Assigning Repeaters for Voice
Channel Priorities
Integrator Code This is the manufacturer code. Currently there is only one
manufacturer code so enter a “1” in this space.
System Code The system code number. This number will be the same for all
sites/repeaters in the system.
Repeater number Auto populates when accessing this specific repeater controller.
Class of Repeater Assigns the function of this repeater.
• Normal: Voice channels. Or Home channels or Collect
channels not paired with the Site Master.
• Site Master: This site’s Site Master repeater. One per site.
On one site in a multi site system, the System master will
perform the function of the Site Master.
• System Master: This system’s System Master. One per
System.
Init Sync IP Address • This is the IP address that this repeater will send its data. to.
• Voice Channels (Normal channels): Enter the IP of this site’s
Site Master (or System Master at the main site).
• Site Master: Enter the IP of the System Master that this
repeater reports to.
• System Master: Enter its own IP address (It reports to itself).
For more information, refer to Synchronization and Init Sync
IP Address Functions.
Init Sync Port Reporting data goes through this port. Leave as default.
Synchronization Synchronization info from site to site travels through this port. Leave
at Default.
Voice Data The port that voice data will travel through. Leave at Default.
IMPORTANT
In a properly
operating System,
every repeater will
have the same
information in this
table. If there is
different in Registration Information Notes
formation in this This window displays currently registered subscriber units.
screen from
• The Main window shows the radios that are currently registered.
repeater to
repeater, this • The window does not update in real time.
indicates Network
• The Search engine allows administrator to search and display currently registered
deficiencies, such
radios by category.
as bandwidth
issues, connectivity
issues, etc.
SNMP Window
Settings in this window enable you to use 3rd party SNMP software to manage your system.
Expert Window
The PDV (Packet Delay Variation) Control Waiting Timer is a buffer that allows some variation
in TX and RX packets without affecting packet (voice) loss. Icom recommends using the 30ms
default.
Currently not used. Future monitoring software will use this data to calculate usage per
customer.
Set the Site Code, Site Type and Adjacent Site Code as described in the following notes.
For additional information, refer to the following:
• Adjacent Site Codes
• Collector Channel Idle Messages
• Home Channel Idle Messages
Conversion Table
The settings in the example Conversion Table show that any radio signal with a Prefix of 2 will
be steered to Home Channel 3 when operating on this particular site. Different sites can have
different Prefix/Home Channel relationships. This allows different Fleets to use different
Home Channels on the same site.
Restriction Window
These settings use a complex algorithm that allows radios to register (or not register) during
times of busy activity. This window shows settings currently not fully researched and Icom
recommends that all settings be left at default.
Enter Subscriber Fleet, Prefix and Alias information for this system. This window allows you
to add new Fleets, Prefixes and Aliases, or edit existing ones. Before programming settings in
this window, refer to Fleet Structure and Programming Prefixes for creating proper IDs.
1. Click Edit to access existing Fleets and make changes to them.
2. Click New to enter a new Fleet and Alias.
Note: Failing to Enter the fleet Prefix and Individual ID’s to be allowed in the system for this Fleet.
click Enable will
nullify the unit
settings.
Note: Failing to Enter the fleet Prefix (must match the same fleets Individual Prefixes) and TalkGroup ID’s to
click Enable will be allowed in the system for this Fleet.
nullify the unit
settings.
Roaming Settings Window
Set in the System Master only.
This Window lists all System Master and Site Master IP addresses in the system. Unlike the
fleet destinations, this window lists all Sites and therefore, potential destinations for all
communication within your system.
Program this system by entering the Site Codes. The IP Address and default ports will auto-
populate as long as the Sites are connected.
Note: Although named the same as the Fleet Settings -> Destination Settings window, this
window lists every Site and System master in the system (up to 48 sites).
Note: These Enter all Collect Repeaters with frequencies and IP addresses for the system.
frequencies are This window lists all the Collect Repeater IP addresses and Collect Repeater frequency sets
used for over the that are in the system. Enter all Collect Repeaters with frequencies and IP addresses for the
air updating, and system.
any inaccurate
entries will cause
errors in Subscriber
radios, which will Collect Repeater Information Notes
impair their ability Setting Description
to register.
Site List No The Site List entry must match the Site Code in this table and
in the programming of the respective sites.
Collector Repeater ID Must match the repeater number of each collector on each
site.
Collect Repeater RX and TX Freq Enter the respective frequencies. Note: Errors in repeater
frequency entry will be downloaded into subscriber radios,
resulting in a non functional fleet.
Always turn off Over the Air Update when changing Collector repeater IDs. Re-enable only
after writing to the system and testing functionality on all sites.
ESN Registration
Set in System Master only.
If ESN Registration is necessary, enter all ESN’s here. Any ESN that is missing will result in that
radio being kept off the system.
Note: This is an all-or-none setting. If any ESN is entered, every radio trying to access the
system will have to have a matching ESN in this screen. If NO ESNs are entered, then ESNs are
not checked. Refer to ESN Validation and Registration for information regarding entering
ESNs into the system using Notepad.
IMPORTANT: ESN recognition can only be enabled if the Authentication window field has
been filled out. Setting is 1 through 30. This sets whether the ESN will be verified every time
it registers (1) or the 30th time it registers (30). For example, if it is set to 3, the ESN will be
validated every 3 times the radio registers. If set to Off, ESN Authentication/Registration is
disabled and ESN’s will be ignored.
Authentication
Set in the System Master only.
Calling Operation determines which sites will retransmit any group communication.
Suggested setting: Mode 3.
• Mode 1: All sites will transmit a call regardless of whether there are registered radios
with matching fleets on those sites.
• Mode 2: All sites with registered radios (even with non-matching fleets) will
transmit.
• Mode 3: Recommended-Only sites with radios registered with matching fleets will
transmit. Sites that have no matching fleet radios registered will not transmit a call.
Target Availability Check: for UC Firmware 3.1 and Radio 4.2 or Greater
Note: If Target Availability is enabled, the handshake time will be considerably longer (sometimes 2
This is a global to 3 seconds) for every radio on the system.
setting, and Target Availability gives an indication if an individual call target radio is not available. If an
enabling this individual call is made, the transmitting radio waits for an ACK to return to the transmitting
feature will result radio, signaling availability of the target.
in longer
If the target radio is available, the handshake is completed and conversations can begin.
handshakes
system-wide, If the target radio is not available, the transmitting radio receives no return Ack and the
taking as long as handshake fails.
1.5 seconds.
To work, this feature must be enabled in this window and also be enabled in the radio
software (Digital/Options window).
This feature applies only to individual calls.
Part Four
SUPPLEMENTAL PROGRAMMING
INFORMATION
1.1.1 Introduction
The radios in a Multi-site Trunking system are organized into large customer groups called
“Fleets”. Each Fleet is composed of a Prefix or Prefixes, Talk Groups, and within the Talk
Groups, Individual radio ID’s. Organizing radios by Fleet gives the system administrator the
ability to activate or deactivate the customer group and to assign the sites that the fleet can
roam and register to.
Fleets, Prefixes, Talkgroups, and Individual IDs are assigned by the system Administrator who
must plan for optimal traffic loads on the system.
1.1.2 Definitions
1.1.3 Fleet
A fleet is a logical grouping of radios that could represent a company or a part of a company.
1.1.4 Prefix
A two-digit code which is used in assigning Home Channels on each site. This gives the system
administrator flexibility in managing the traffic on a site.
1.1.5 Talkgroup
A common grouping of radios within a Fleet.
1.1.6 Individual ID (radios)
Each radio in a fleet has its own ID. These radios are assigned to Talkgroups and Fleets.
• 30 Prefixes
A Fleet may contain one Prefix or all 30 Prefixes, depending on the needs of the system.
A Prefix may contain as many as:
• 2000 Individual IDs and Talkgroup IDs total
• With all 30 Prefixes used, total System ID capacity is 60,000 (30 Prefixes X 2000
Individual or Talkgroup IDs).
02-1003
02-1004
↓
02-2000
• The UC-FR5000 Conversion Table uses the Prefix in the ID to direct the subscriber
radio to its Home Channel. This Prefix structure allows the administrator to assign
different Home Channels on different sites.
• In each Fleet, the Talk Group Prefix must match the Individual ID Prefix.
• Each Prefix can have a maximum of 2000 Individual ID’s assigned to it. In the
previous example, we set up 4 Fleets with Individual ID’s ranging from 02-0001 02-
2000. Within any prefix, ID’s cannot repeat. Attempts to enter the same Prefix/ID
into the Fleet management screen will result in an error message. However, the
System considers Talkgroups and Individual IDs as different numbers (if programmed
in the radio as two separate numbers), so it is acceptable for the Talkgroup and
Individual IDs to be the same in a Fleet, as shown in the Fleet 1 example.
• Talk Group ID’s must be different for each Fleet. In the preceding examples, Fleet 1
used TG’s 02-0001 and 02-0002. Fleet 2 must use different Talk Groups, and in this
example, uses Talk Groups 02-0003 and 02-0004.
1.2.1 Introduction
A prefix is an important part of a subscriber’s ID. It is used as a reference number to steer the
subscriber to the proper Home Channel on a particular site and it is an integral part of the
Individual ID for use in assigning it to a Fleet.
It is important to note that the prefix is not an actual Home Channel number.
This example shows Prefix 2 associated with Individual IDs 1 through 15 in Fleet 1.
To get the Ack back from a SU which is on another site, it will take longer than a single site
system. A 2 way IP delay should be considered to configure the Ack RX Wait. The default
value of the Ack RX Wait is 0.8sec but this is not long enough to get Ack back from another
site.
Also, the local repeater needs to keep transmitting until the Ack is repeated. The SU
answering Ack can’t let the repeater start transmission so the Repeater Hold Timer for the
Ack should be configured long enough to accommodate this (Default value of 2.6sec is
normally enough).
[Subscriber] > Digital > Multisite Setting > Individual ID List > Prefix ID
• Default: 1
• Range: 1 – 30
Set the Prefix ID within the range of 1 to 30.
[Subscriber] > Digital > Multisite Setting > Individual ID List > ID
Set the Individual ID within the range of 1 to 2000.
• Default: Blank
• Range: 1 – 2000
[Subscriber] > Digital > Multisite Setting > Individual ID List > ID Name
Enter up to a 12-character Unit ID name.
When a matched ID is received, the ID name is displayed on the LCD.
[Subscriber] > Digital > Option > Ack RX Wait
• Default: 0.8 [sec]
• Range: 0.000 – 60.000 [sec]
Enter the time period to wait for an acknowledgment, after transmitting a call that requests
an Ack. Generally, if multiple sites are involved, use 2.6 seconds. If no acknowledgment is
received in this set time period, the transceiver repeatedly transmits the call up to the
maximum number of retries.
To get the Ack back from a SU which is on another site, it will take longer than on a single site
system. Two way IP delay should be considered to configure the Ack RX Wait. The default
value of the Ack RX Wait is 0.8sec, but this is not long enough to get Ack back from another
site.
1.4.1 Overview
Ultimately, call data packets are routed within a Multi-Site Trunking system based on Fleets.
These calls are routed to other sites within the system based on Fleet Assignment, Fleet
Destination List, Call Type (Talk Group or Individual calls) and system “Mode” selection.
• Mode 2- Fleet Calls for the transmitting radio are sent to all sites in the Fleets
Destination List that have radios from ANY Fleet registered on it. Each site in the
Destination List will transmit the call based on the presence of any registered radios.
In normal applications, this, also, is not the most efficient way to utilize channels in
the system.
• Mode 3- Fleet Calls for the transmitting radio are sent to all sites in the Fleets
Destination List that have any matching-Fleet radios currently registered on it. Each
site in the Destination List will transmit the call based on the presence of this Fleets
registered radios. This selection is generally the most efficient way to utilize
channels on a system.
Mode-1: Frames (Group calls) will be transferred to other sites according to the Destination
Settings of each fleet. All sites TX regardless of whether the radios or fleets are registered on
a particular site.
Mode-2: Frames (Group calls) will be transferred to other sites according to the Destination
Settings of each fleet, except sites that have no registered SU. Sites with ANY radio registered
from ANY Fleet will TX a call.
Mode-3: Frames (Group calls) will be transferred to other sites if the site is entered in the
Destination Settings screen of each fleet, AND if there is a radio with a matching Fleet on that
site. Sites without matching Fleets will not TX.
1.4.7 Examples
Using the same example, on Mode-1, even if the Fleet 1 radios are only on Site 1 and 2, a
Talkgroup Call will be transferred to all 5 sites.
On Mode-2, if the Fleet 1 radios are only on Site 1 and 2, a Talkgroup Call will be transferred
to Site 1 and 2 only but if there is another Fleet radio is on Site 3, Fleet 1’s call is transferred
to the Site 3 as well.
On Mode-3, if the Fleet 1 radios are only on Site 1 and 2, a Talkgroup Call will be transferred
to Site 1 and 2 only, even if the non-matching Fleet radios are on Site 3, 4, and 5.
Conclusion: Mode-3 is the most efficient way to transfer the voice to the other sites.
At this moment, there is no way to transfer the voice to only the sites which same Talkgroup
radios registered. It is not available to satisfy Block Mode function.
Status
• Default: Disable
• Range: Disable / Enable
Select whether or not to transfer the group calls to other sites, for each talkgroup ID.
[Controller] Multi-site Settings > System Setting > Fleet Setting > Destination
Setting
Select destination sites of group calls for the fleet. If an SU belonging to the fleet makes a
group call, it is transferred to the sites which are designated as a destination site The list
shows all the sites in the system, and their site codes and alias names. Click one or more
sites, to designate it as a destination site.
NOTE: Regardless of the setting, individual calls will be transferred to other sites.
[Controller] Multi-site Settings > System Setting > Option > Calling Operation
• Default: Mode-1
• Range: Mode-1 / Mode-2 / Mode-3
Set the ID code for the Priority Talk Group within the range below.
The set ID code is used for the selected operation in Dec. Pri. TG.
[Subscriber] Zone Operation > Block Mode
• Default: Disable
• Range: Disable / Enable
Set the Prefix ID for block mode operation within the range of 1 to 30.
[Subscriber] Zone Operation > Start ID
Set the Start ID for block mode operation within the range below.
• Default: 1
• Range: 1 – 2000
Enter an RX Broadcast Group Prefix ID (within the range of 1 to 30) to specify an RX Broadcast
group from which the transceiver can receive calls, regardless of the transceiver's Talkgroup
ID.
However, the transceiver cannot transmit to the group.
To specify an RX Broadcast group, you have to configure RX Broadcast Group ID, as well.
[Subscriber] Zone Operation > RX Broadcast Group ID
• Default: 1
• Range: 1 – 2000
Select the Talkgroup ID list number from the list to call the desired talkgroup.
Set the talkgroup ID in the Digital-Multisite-Trunk-Talkgroup ID List screen.
[Subscriber] > Digital > Multisite Setting > Talkgroup ID List > Prefix ID
• Default: 1
• Range: 1 – 30
* Talkgroup ID "2047" is used for All Calls, and matches to any Talkgroup ID.
[Subscriber] > Digital > Multisite Setting > Talkgroup ID List > ID Name
Enter up to a 12-character talkgroup ID name.
When a matched ID is received, the ID name is displayed on the LCD.
1.5.1 Introduction
If programmed as First Available Search (using the selections of Last or Home in the Digital-
MultiSite-Roaming Settings-Roaming Priority setting), the radio attempts to register on the
first site that meets the programmed minimum RSSI level (Digital-Options Roaming Level).
When a radio begins its roaming process, it searches the Collect Repeater frequencies of each
site, as entered into the radio programming Site List. The Collect Repeaters send out an Idle
Message “beacon” every 4 seconds. When the radio receives a signal which is stronger than
its programmed “Roaming Level” (a programmable setting in the radio software), it starts the
registration negotiation on the Collect Channel. If the radio data meets the system
requirements, the Collect repeater registers the radio onto the Site/System.
Home Site
The radio checks the Home Site of the Fleet first, and then the last registered
Site, and finally the numerical sequence of the repeaters. This technique
assumes that the administrator wants the radios to stay on the Home Site as
much as possible, especially on power up, in order to conserve channel
resources on other sites.
• Strongest Site Search (Roaming Priority set to Adjacent RSSI) – This method allows
the radio to make a list of the adjacent sites (as programmed into the Site Master
UC-FR5000 controller for that site) and search them in order to compare their
Receive Signal Strength Indicators (RSSI). From this list, the radio chooses the
strongest site of the adjacent group and registers on that site. If no signal is found
within the adjacent site group that is stronger than the In Range RSSI setting, the
radio will start looking at the other non-adjacent sites to find a possible strong site.
1.5.4 Basic Rules of First Available Site search with No Home Site Enabled
• When the radio is turned on, it monitors the last registered site for 6 seconds.
• If the Last Registered site is not present, the radio builds a scan list of Site Collector
frequencies (up to five sites) and scans through them, from lowest assigned number
to highest (example: 1->2->3->4->5).
• Each of these frequencies is examined for 50ms as it goes through the list. The Fast
Scan Timer is 50ms. The radio scans these 5 sites for a total of 6 seconds.
• If no Collector signals are found above -114dBm, the radio makes another scan list
for the next 5 sites (example 6->7->8->9->10), etc.
When Adjacent Channels are enabled (Site Settings -> Site Management window), the roam
sequence will include those adjacent channels after the Home Site and/or Last Registered
channels are scanned.
Example c: Radio goes to fringe of Site 7 and begins Roaming. No Home Site
enabled.
In this example, the behavior is the same as Example b. Site 7 (Last Site) is ignored. If there is
no acceptable RSSI level, the radio will continue to scan all the sites in sequence.
Example d: Radio is powered up with Home Site information Enabled (Home Site =
1, Last Site = 7, Roaming Home Priority = Home)
When the Home Site information is set on the site list of a subscriber radio, the home site
monitoring process is added. With this configuration, radios will have a better chance of
connecting to the home site. If there is no acceptable RSSI level, the radio will continue to
scan the sites in sequence.
Example f: Radio starts roaming at the fringe of Site 7 (Home Site = 1, Roaming
Home Priority = Home)
The radio keeps monitoring site 1 for 6 sec. (Home Site). If there is no acceptable RSSI level,
the radio will continue to scan the sites in sequence.
Example g: Radio starts roaming at the fringe while on home site (Home Site = 1,
Last Site = 7, Roaming Home Priority = Home)
The radio knows that both the Home Site and Last Site are low signal sites. If there is no
acceptable RSSI level, the radio will continue to scan all the sites in sequence.
Example h: Radio is powered up with Home Site information Enabled (Home Site 1,
Last Site is 7, Roaming Home Priority = Last)
The radio keeps monitoring site 7 (Last Site) for 6 sec. If there is no acceptable RSSI level, the
radio will continue to scan all the sites in sequence.
Example i: Radio starts roaming at the fringe of Site 7 (Roaming) with ADJ Site
information
This example shows 13 total sites. Adjacent sites are scanned first. If there is no acceptable
RSSI level, the radio will continue to scan all the sites in sequence.
Example j: Radio starts roaming at the fringe of Site 7 (Home Site = 1, Roaming
Home Priority = Home) with ADJ site information.
Adjacent sites and Home site are scanned first. If there is no acceptable RSSI level, the radio
will continue to scan all the sites in sequence.
2.1.1 Introduction
If Cross Busy Monitoring is enabled, it prevents voice channel use of the repeaters RX or TX
frequency if that frequency is already in use. If enabled on a Voice channel that has detected
a frequency during trunk-off, the repeater will be bypassed in favor of the next available
repeater.
• Idle messages are not inhibited.
• You will need a separate radio receiver to monitor the repeater TX frequency.
This feature is enabled by programming in each Home Channel and voice Channel on the site
(see the following).
Setting Description
If set to Enable, the repeater monitors the RSSI of its RX channel. Any
Uplink Monitoring
signal in excess of the RSSI Level (dBm) results in inhibiting the repeater
TX as long as the signal is present.
If set to Enable, the repeater’s TX frequency will be monitored and the
Downlink Monitoring
repeater’s TX frequency will not be able to transmit a voice signal if a
signal is detected. If a signal tried to trunk off to this channel, the channel
will be skipped.
2.2.1 Introduction
• Repeater 2 is the Home Channel and must be the 1st assigned (High Priority) Voice
Channel.
• Repeaters 3, 4, and 5 are the primary Voice channels and are all assigned as Middle
Priority. Trunk offs are assigned randomly between “Middle” assigned repeaters.
• Each Site may have more than one Home Channel (see below). In the Network
Trunking Controller section, choose those repeaters that are going to be Home
Channels on that site and fill in the Free Repeater List taking that Home Channel in
consideration. Each Home Channel will have its Free Repeater Assign screen filled
out differently that the other Home Channels.
• A Home Channel will be High Priority in its Free Repeater List, but the same repeater
will be a Middle Priority in another Home channel’s list.
• There is generally one Low Priority on a site: the Site Master/Collector.
• Only Home Channels are High Priority.
Notes: Prefix 1 radio is told to go to Home Channel 2 by the conversion table. The Free
Repeater table tells the traffic what sequence to assign Voice traffic when using THIS
repeater as HC. This repeater is the HC and the High Priority.
Prefix 2 is told to go to Home Channel 4 by the same conversion table. The Free Repeater
table for repeater 4 tells what sequence to assign voice traffic. Home Channel 4 is the High
Priority voice channel.
In these examples, the repeater that is the Home Channel for a particular prefix is also the
High Priority. The Site Master/Collector is always the Low Priority and the other voice
channels (trunk-off channels) are Middle Priorities and are selected randomly for voice
traffic.
2.3.1 Synchronization
All activity on an IDAS Multi-site System is synchronized with other repeaters in the system.
For example, as subscriber radios register or de-register, this activity is sent to the Site
Master of the site where your subscriber radio is registered. This Site Master sends this
information to the System Master, who then resends it back out to all Site Masters for
distribution to all repeaters on their respective sites.
This sequence allows all repeaters in all sites to have a continuous list of the locations of all
registered radios. When a call is made, (either Individual or Talk Group), the repeater that the
call originated from knows what IP address destination to send the call to by referring to data
in the Registration Information window (read only).
2.4.1 Introduction
The Adjacent Site Codes are the Site Numbers of the four possible sites (maximum) for
consideration when your radio leaves this particular site.
In the following example, your radio de-registers from Site 1.
• It will form a roam scan list (as described in the Site Search Theory article).
• The Adjacent Sites are the first sites checked in this scan list.
• If the Adjacent Site numbers in the Site Management screen are assigned correctly,
the radio will immediately detect strong signals from the “Adjacent Sites”.
• If no Adjacent Sites are detected, the radio checks the other sites. This will be a
sequential scan list with no regard to logical close sites.
The System Administrator is responsible for choosing Adjacent Sites from the following
window. Proper Adjacent Site selection should give the radio the best opportunity to quickly
find a new site to register on when the radio de-registers from that site.
2.5.1 Introduction
The Repeater assigned as the Collector in an IDAS Multi-site Trunking Site sends out an Idle
message every 5 seconds by default. This message contains that Collector’s site code and is
used as a beacon that allows actively roaming radios to see this site when searching to
register on a location.
A roaming radio searches its Collector Channel list until it sees an Idle message with an
acceptable RSSI level, and it then starts the registration sequence by transmitting its own
Radio Prefix, Unit ID, TG ID, and other parameters.
Green lights on the Subscriber radio will flash when receiving data from the Collect Channel.
With this protocol, if many radios try to register at the same time it can result in de-sensing
and therefore, failed registrations.
The number that you set in this field represents the range of time slots (each 80ms long) that
is available for your radio to transmit back to the Collect Channel, after it has received a valid
Idle Message.
Use a lower number (such as 10) for applications where radios will always be powered up
and registered at random times.
Higher numbers (20, 30, 40, etc.) are better if larger numbers of radios will be powering up
and registering at the same time. A higher number increases the randomness of registration
transmissions.
Example:
The following shows 8 radios attempting to register at the same time with the Random
Registration Slot set to 10.
A setting of 10 means the radio will randomly choose one of 10 time slots (lasting 80ms each)
to begin its registration. If there are 8 radios that are powered up at the same time, each
one of them will have a different time slot in which it transmits its registration attempt. Since
radios won’t be transmitting at the same time, collisions will be decreased.
2.6.1 Introduction
Each fleet in a system monitors a Home Channel. Radios that are registered on a system
monitor their assigned Home Channels so that they can receive calls and obtain operating
data. Each radio monitors the quality of each Home Channel Idle message. Low RSSI (or too
many errors in older firmware) or a complete loss of packets will cause a radio to de-register
and roam.
When a registered radio receives an Idle message from its Home Channel, it analyses the RSSI
(or packet errors in older firmware) to determine if the radio will stay on the site or roam. If
there are too many errors, the radio will roam.
2.7.1 Introduction
Occurs when Adjacent RSSI is selected in the Digital > Multi-Site Trunk-Roaming Setting > In
Range Judgments.
The IDAS Multi-Site Trunking Strongest Site Search feature enables the subscriber radio,
when actively roaming, to scan each Adjacent Site (as programmed in the UC-FR5000 Site
Management window). The radio evaluates the RSSI signals of these adjacent sites, and
registers on the strongest of these signals.
If no adjacent site signals are seen during this scan cycle, the subscriber proceeds to scan the
remaining Non-Adjacent sites in a scan cycle that will stop and make a registration attempt
on the first site that has an RSSI stronger than the In Range setting.
Previously, the subscriber roamed to the first acceptable site based on its RSSI level. This
feature can still be configured as an option. Each subscriber radio can only be configured as
either strongest site (Adjacent RSSI) or first acceptable – not both.
Any of the following conditions may cause a radio to roam and start the Strongest Site Search
function (if enabled).
• At Power On
• When the [Roam request] key is pressed
• When the Radio become out of range, as determined by Digital->Options settings
• When a different Multi-Site Trunking Zone is selected
• When MCH is changed
• When “Forced Roam at Handshake Failure” is initiated
2.7.3 Prerequisites
• Properly functioning MultiSite trunking system
• Up to 4 adjacent sites must be configured in each site master UC-FR5000 Site
Management screen.
• Subscriber Firmware for F3061/F5061 at Main 4.6/DSP 3.0 or greater or Next Gen
IDAS radios.
• Software revision CS-F3161/5060 v 4.6 or greater and Next Gen IDAS radio software.
• With Strongest Site Search, the first group of 5 sites is composed of the Last
Registered site and the Adjacent Sites from that same last site. After this group, the
following groups are composed of the remaining sites in numerical order. Note: If
there are fewer than 4 Adjacent Sites programmed in the Site Manager for this last
registered site, this group will be less than 5 total.
Example: ( 3,1,2,4,5) -> (6,7,8,9,10)-> (11,12,13,14,15)
• The first group composed of the Last Registered and the Adjacent Sites, in this
example (3,1,2,4,5) will be searched using the Strongest Site Search sequence. If no
acceptable sites are found in the Group 1 list, the radio proceeds to sites (6,7,8,9,10)
where it performs a First Acceptable Site search. If no acceptable sites are found
within this group, the subscriber goes to sites (11,12,13,14,15) for a First Acceptable
Site search, etc. If no sites are detected on this last group, the subscriber returns to
group number 1 and begins a “First Acceptable” search.
Note: Only Group 1, composed of the Last Registered and Adjacents for that site, has the
Strongest Site Search. If no acceptable RSSI’s are detected in Group 1, the subscriber radio
moves to Group 2 for a First Acceptable Site search.
2. The subscriber radio will continue this cycle until it detects a carrier on one of the
Scan List Collector carriers, or until 6 seconds has elapsed (Roaming Wait Timer),
whichever comes first. If the RSSI of this detected carrier is stronger than the
Roaming Level,the scan is stopped, the Site ID is decoded and the site ID/ RSSI levels
are stored in a table for comparison. The process of verifying the site ID and entering
it with the assciated RSSI takes approximately 160 mS.
Any carrier that is detected during the scan process, but is weaker than the Roaming
Level setting is treated as “no signal”.
3. Any Strongest Site Search that does not detect a site is terminated. If this occurs, the
subscriber radio will then look at previously detected sites. If these sites are no
longer detected, the Strongest Site Search will stop and the subscriber radio will
move to a First Acceptable Site Search.
In this example, Site 4 is detected and the site ID and RSSI are entered into a table for
comparison.
Site 4 in this example is now removed from the original Scan List Group and another scan is
started using the remaining sites (4 sites in this example)in this original group of 5.
During this second cycle, Site 1 is detected and the site ID and RSSI are entered into the table.
In this third cycle, Site 3 is detected and the site ID and RSSI are entered into the table.
In this example, this 2-site scan list results in no signals seen (stronger than the Roaming
Level dBm) so after the 6 second maximum-allowed scan time (Roaming Wait Timer), the
Strongest Site Search ends and the subscriber radio looks at the Site/RSSI table to determine
the strongest-site.
In this example, Site 1 is the strongest site, so the subscriber radio registers on that site.
• Each Scan takes a maximum of 6 seconds (Roaming Wait Timer) or a minimum of
whatever time it takes to detect a qualifying site RSSI.
• This Strongest Site Search will repeat itself until all 5 sites in this initial Scan List
Group (Last Registered + Adjacents) are detected and stored in the table for
comparison or until a scan results in “no signals found”. In other words, for Scan List
group 1, there can be as many as 5 scan sequences necessary in order to detect and
log the 5 sites in the group.
• It is possible (but not probable) that the scan can take 5 seconds to see the first site
in this group, reset the scan and take 5 more seconds to see the 2nd site, etc., for a
total of 25 seconds to detect and store RSSI/ID’s for this Strongest Site Search
sequence. This scenario is unlikely, but possible.
• In the strongest Site Search Group 1, if a scan cycle occurs with no accepable RSSI’s
detected for any site, this “Strongest Site Search” group will be terminated and the
subscriber will proceed to the next group (in our example 6,7,8,9,10), where a
standard “First Acceptable” search occurs. If no sites are detected in the 1st 6 second
scan, for example, the Strongest Site Search is terminated and the subscriber moves
to the 2nd group (in our example, sites 6,7,8,9,10) for a standard First Acceptable
scan.
• Assuming the Strongest Site Search has examined all 5 Sites in the first Scan List
group, and detected some or all, it will compare the Site ID’s and associated RSSI’s
and attempt to register on the strongest site of the group.
Note: If Adjacent RSSI Level (dBm) is enabled and a Stronger RSSI is entered into the
programming, detection of a site during a scan of Group 1 with a stronger RSSI will result in
the subscriber terminating the Strongest site Search scan and registering immediately on that
site.
2.8.1 Introduction
If programmed as First Available Search, the radio attempts to register on the first site that
meets the programmed minimum RSSI level (Digital-Options Roaming Level). When a radio
begins its roaming process, it searches the Collect Repeater frequencies of each site, as
entered into the radio programming Site List. The Collect Repeaters send out an Idle Message
“beacon” every 4 seconds. When the radio receives a signal which is stronger than its
programmed “Roaming Level” (a programmable setting in the radio software), it starts the
registration negotiation on the Collect Channel. If the radio data meets the system
requirements, the Collect repeater registers the radio onto the Site/System.
Last Site
Home Site
2.8.3 Basic Rules of First Available Site search with No Home Site Enabled
• When the radio is turned on, it monitors the last registered site for 6 seconds.
• If the Last Registered site is not present, the radio builds a scan list of Site Collector
frequencies (up to five sites) and scans through them, from lowest assigned number
to highest (example: 1->2->3->4->5).
• Each of these frequencies is examined for 50ms as it goes through the list. The Fast
Scan Timer is 50ms. The radio scans these 5 sites for a total of 6 seconds.
• If no Collector signals are found above -114dBm, the radio makes another scan list
for the next 5 sites (example 6->7->8->9->10), etc.
Notes:
When a radio reaches a site fringe and goes into a roam sequence, it will not examine the
Last Registered site because it assumes it is unacceptable.
When the radio is turned on right after the programming, it doesn’t have Last Site
information so that step is skipped in the roaming sequence.
When Adjacent Channels are enabled (Site Settings -> Site Management window), the roam
sequence will include those adjacent channels after the Home Site and/or Last Registered
channels are scanned.
Case Study Examples
Specifications of examples:
• The number of sites: 12+ sites
• Last Site Registered: Site 7
• Home Site (if enabled): Site 1
• Optional: Adjacent Sites of Site 7: Site 8, Site 9
The examples that follow describe the roaming sequence under various situations.
a. When the radio is initially powered up in the morning (Last Site = 7). No Home Site
enabled
b. When the radio is powered up right after programming (No last site information). No
Home Site enabled
c. Radio goes to fringe of Site 7 and begins Roaming. No Home Site enabled
d. When the radio is powered up with Home Site information Enabled (Home Site = 1,
Last Site = 7, Roaming Home Priority = Home)
e. The radio is powered up right after programming with Home Site information
Enabled (Home Site = 1, No last site information, Roaming Home Priority = Home)
f. The radio begins to roam at the fringe of Site 7 (Home Site = 1, Roaming Home
Priority = Home)
g. When the radio goes into fringe while on home site (Home Site = 1, Last Site = 1,
Roaming Home Priority = Home)
h. When the radio is powered up with Home Site information Enabled (Home Site 1,
Last Site is 7, Roaming Home Priority = Last).
i. The radio goes to fringe of Site 7 (Roaming) with Adjacent Site information
j. The radio goes to fringe of Site 7 (Home Site = 1, Roaming Home Priority = Home)
with adjacent site information.
Example a: Radio is initially powered up in the morning (Last Site = 7). No Home Site
enabled.
Last Site is the site the radio was on when it was turned off. Looking for this site first enables
the radio to find the last site easily. The radio stops scanning and registers when it finds an
acceptable RSSI level, as set in the programming.
If the Last Site is not at an acceptable RSSI level, the radio will build a table of the next 5 sites
in numeric sequence and scan them over a period of 6 seconds, looking at each channel for
50ms. If there is no acceptable RSSI level, the radio will continue to scan the sites in
sequence.
Example b: Radio is turned on immediately after programming (No Last Site information)
No Home Site Enabled.
The radio will build a table of the first 5 sites in numeric sequence and scan them over a
period of 6 seconds, looking at each channel for 50ms. If there is no acceptable RSSI level, the
radio will continue to scan the sites in sequence.
Example c: Radio goes to fringe of Site 7 and begins Roaming. No Home Site enabled.
In this example, the behavior is the same as Example b. Site 7 (Last Site) is ignored. If there is
no acceptable RSSI level, the radio will continue to scan all the sites in sequence.
Example d: Radio is powered up with Home Site information Enabled (Home Site = 1, Last
Site = 7, Roaming Home Priority = Home)
When the Home Site information is set on the site list of a subscriber radio, the home site
monitoring process is added. With this configuration, radios will have a better chance of
connecting to the home site. If there is no acceptable RSSI level, the radio will continue to
scan the sites in sequence.
Example e: Radio is powered up right after programming with Home Site information
Enabled (Home Site = 17, No last site information, Roaming Home Priority = Home)
The radio starts by monitoring site 1 for 6 sec. (Home Site). If there is no acceptable RSSI
level, the radio will continue to scan all the sites in sequence.
Example f: Radio starts roaming at the fringe of Site 7 (Home Site = 1, Roaming Home
Priority = Home)
The radio keeps monitoring site 1 for 6 sec. (Home Site). If there is no acceptable RSSI level,
the radio will continue to scan the sites in sequence.
Example g: Radio starts roaming at the fringe while on home site (Home Site = 1, Last Site
= 7, Roaming Home Priority = Home)
The radio knows that both the Home Site and Last Site are low signal sites. If there is no
acceptable RSSI level, the radio will continue to scan all the sites in sequence.
Example h: Radio is powered up with Home Site information Enabled (Home Site 1, Last
Site is 7, Roaming Home Priority = Last)
The radio keeps monitoring site 7 (Last Site) for 6 sec. If there is no acceptable RSSI level, the
radio will continue to scan all the sites in sequence.
Example i: Radio starts roaming at the fringe of Site 7 (Roaming) with ADJ Site information
This example shows 13 total sites. Adjacent sites are scanned first. If there is no acceptable
RSSI level, the radio will continue to scan all the sites in sequence.
Example j: Radio starts roaming at the fringe of Site 7 (Home Site = 1, Roaming Home
Priority = Home) with ADJ site information.
Adjacent sites and Home site are scanned first. If there is no acceptable RSSI level, the radio
will continue to scan all the sites in sequence.
Roaming Level
[Subscriber Radio] Digital > Option > Multi-site Trunk > Roaming Level(dBm)
• Default: -114dBm
• Range: -120 - -80
This level is used by the radio to distinguish if the site signal is strong enough while scanning
for Collect Channels. It is not used for out of range decisions. (The message error rate is used
for out of range decisions). If the radio detects a signal stronger than -114dBm, it will stay on
the site and if the system code was matched, the radio starts registration. Normally, it
shouldn’t be changed. Lower values will make the radio attempt to find very weak sites and
consume more battery charge. Higher values make it difficult to find the higher signal
strength site, thus increasing roaming times.
2.10.1 Introduction
In an IDAS Multi-site Trunking System, values entered in the Conversion Table establish which
Fleet Prefix is assigned to a particular Home Channel. The Collect Repeater references the
Conversion Table during the registration process to determine which Home Channel the
registering subscriber radio will monitor while operating on that site.
Each site requires a Conversion Table that lists the prefixes /Home channel relationships for
subscribers on that site. As each subscriber registers on a site, the Collector Channel checks
that radio’s Prefix and applies it to the Conversion table for that site, telling the radio what
Home Channel to monitor. Since there are 30 prefixes possible, there are 30 Prefix/Home
Channel relationships on the Conversion table.
The Conversion Table is located at the Site Master only.
The Conversion Table does not list the Home Channels for that site. It lists which Home
Channel will be used in relation to each subscriber prefix that accesses the site. A subscriber
that has multiple prefixes on different channels may utilize more than one Home Channel, as
dictated by the Conversion table.
The Home Channel numbers listed in the Conversion Table will be used to determine which
repeaters send out Home Channel idle messages, even if these channels are not used as
Home Channels. Icom recommends that the default settings be changed to reflect only the
channels that will potentially be Home Channels. If the Conversion Table is left at the default
settings, i.e. 1, 2, 3… 30, then every repeater will send out idle messages in anticipation of
being a home channel at some time. To avoid this, do not assign every repeater per site as a
Home Channel in the Conversion Table. Icom recommends that only Collect Channels and
active Home Channels send out Idle Messages.
In the default settings as above, Prefixes 1-30 correspond with Home Channels 1-30, which
occurs only if you have 30 channels.
In this example, when a radio registers on the above site, any radio ID with Prefixes 1-4 will
be directed to monitor Channel 2 as its Home Channel.
In this example, when a radio registers on the above site, any radio ID with Prefixes 1or 2 will
monitor Channel Two as its Home Channel. Prefixes 3 and 4 will monitor Home Channel
Three.
3. The Collector directs the subscriber radio to its assigned Home Channel as set in the
Conversion Table.
4. The Subscriber radio diverts to the assigned Home Channel for normal
communications.
2.11.1 Introduction
A prefix is an important part of a subscriber’s ID. It is used as a reference number to steer the
subscriber to the proper Home Channel on a particular site and it is an integral part of the
Individual ID for use in assigning it to a Fleet.
It is important to note that the prefix is not an actual Home Channel number.
This example shows Prefix 2 associated with Individual IDs 1 through 15 in Fleet 1.
2.12.1 Introduction
The radios in a Multi-site Trunking system are organized into large customer groups called
“Fleets”. Each Fleet is composed of a Prefix or Prefixes, Talk Groups, and within the Talk
Groups, Individual radio ID’s. Organizing radios by Fleet gives the system administrator the
ability to activate or deactivate the customer group and to assign the sites that the fleet can
roam and register to.
Fleets, Prefixes, Talkgroups, and Individual IDs are assigned by the system Administrator who
must plan for optimal traffic loads on the system.
2.12.2 Definitions
Fleet
A fleet is a logical grouping of radios that could represent a company or a part of a company.
Prefix
A two-digit code which is used in assigning Home Channels on each site. This gives the system
administrator flexibility in managing the traffic on a site.
Talkgroup
A common grouping of radios within a Fleet.
Individual ID (radios)
Each radio in a fleet has its own ID. These radios are assigned to Talkgroups and Fleets.
• The UC-FR5000 Conversion Table uses the Prefix in the ID to direct the subscriber
radio to its Home Channel. This Prefix structure allows the administrator to assign
different Home Channels on different sites.
• In each Fleet, the Talk Group Prefix must match the Individual ID Prefix.
• Each Prefix can have a maximum of 2000 Individual ID’s assigned to it. In the
previous example, we set up 4 Fleets with Individual ID’s ranging from 02-0001 02-
2000. Within any prefix, ID’s cannot repeat. Attempts to enter the same Prefix/ID
into the Fleet management screen will result in an error message. However, the
System considers Talkgroups and Individual IDs as different numbers (if programmed
in the radio as two separate numbers), so it is acceptable for the Talkgroup and
Individual IDs to be the same in a Fleet, as shown in the Fleet 1 example.
• Talk Group ID’s must be different for each Fleet. In the preceding examples, Fleet 1
used TG’s 02-0001 and 02-0002. Fleet 2 must use different Talk Groups, and in this
example, uses Talk Groups 02-0003 and 02-0004.
2.13.1 Introduction
An IDAS Multi-Site Trunking system can be programmed by a System Administrator to use
the radio’s ESN (Electronic Serial Number) to validate whether that radio can register on the
system. This is a global setting and once enabled, only radio ESN’s entered into the system
programming will be allowed onto the system. Radios not entered into the system will fail to
register.
ESN’s for each radio are found in the Clone/Information window of the CS-F3160/F5060
programming software. Note: The ESN is the first 4 numerical digits of the FCC ID plus the
radio’s serial number.
If the ESN feature enabled in the Authentication window of the UC-FR5000 Web Settings
screen, ALL radio’s ESN’s must be entered into the ESN Registration screen. Any radio ESN
that is NOT in the list will not allow that radio to register on the system.
ESN Validation can happen with every registration or as little as once every 30 registrations.
This frequency of validation is enabled in the Authentication window of the UC-FR000 Web
settings.
The Validation process adds approximately 100mS to the registration process, so the interval
between validations to registrations must be considered. ESN Validation occurs during the
registration negotiation between the subscriber radio and the collector repeater. The
Handshake process is not affected by ESN validation.
3. Go to ESN Registration and enter radio ESNs. There are two methods for entering
radio ESNs:
• For each radios intended for the system, enter the ESN in the Regist ESN
Number field.
• You can also enter the numbers in a Note Pad document and load all the
numbers at once. The numbers must be entered in the following format. For
Example:
Comment <e.g. fleet name, customer, etc.>
###ESN List Start###
12345678912
12345678913
12345678914
###ESN List End###
Once a file has been written, click Browse and select either Overwrite or Addwrite.
Overwrite will write over any other ESNs in the system; ADDwrite will add to existing ESNs.
Note: Only ESNs contained between ###ESN List Start### and ending with ### ESN List
End### will be recognized.
If ESN Registration is enabled, all ESN’s must be entered into this list. If a radio ESN is missing,
that radio will not be allowed to register on the site.
2.14.1 Introduction
Each subscriber radio in a Multi-site system requires all of the system Collector channels and
the channels in the site to which it is registering. Over the Air Updating allows a subscriber
radio to update its Collector repeater list and its site repeater list over the air. This occurs
when the radio first registers on a system and when it registers to each site.
When a system administrator adds or removes repeaters from a site, OTAU enables
subscriber radios to update their repeater list automatically over the air, eliminating the need
to gather all the subscriber radios and reprogram by hand.
OTAU starts at registration. When a radio registers for the first time on a system, the
collector sends a Data Write Request to the radio. When the radio responds with an ACK, the
Collector sends the first Collector frequency pair. The collector then sends another Data
Write Request, etc. until all collector frequencies are downloaded to the subscriber radio.
Once a radio receives all collector frequencies, the system makes note of this and that radio
doesn’t download the collector frequencies again unless changes in the list are made.
Each frequency set downloaded into the subscriber radio takes approximately 80 mS. For
example, if a site has 5 channels, it would add 5 X 80mS = 400mS to the registration process.
Click Enable at Date Write Inh for each site you want to update upon registration.
IMPORTANT
Updating of
Collector and
Home Channel
information in
the Web
Settings will be
downloaded into
the radios at
registration. If
this information
does not match
frequencies in
the repeaters,
Radios on the
site can be
stranded.
Enter how often you want the radio to update with OTAU. For example, if you enter “5”,
subscriber radios will update every fifth registration.
Note: Entering “1” will require the radios to update every time the radio registers, adding
extra time to every site registration.