Specifications

AE/LZB 119 1897 R1A SOFTWARE CONFIGURATION
60
In the console application, the top line of the message panel displays status information for both RSM status and RTT
status.
6.2.7.3.2 RTT Basics
The RTT option is similar to the RSM option primarily in regards to status code transmission from the radios and general
handling throughout the EDACS radio system. At the console however RTT allows the dispatcher to, as desired, individually
reply to each unit sending request-to-talk status to dispatch operations. A reply is accomplished via an individual call, with the
dispatcher being the caller and the requesting-to-talk unit being the callee. The individual call is initiated directly via an RTT
module holding the queued-up requesting-to-talk unit(s) of a particular status message/code.
As statuses change, the RTT modules update accordingly as previously described for RSM modules. However unlike
RSM module listings, RTT module listings do not include a time-stamp for each requesting-to-talk unit. Typically, a group of
RTT status messages/codes are distributed across multiple consoles in a dispatch center to prevent long RTT queue-up times
during busy periods.
Like the console RSM module configuration, the console RTT configuration must ensure RTT module configurations
matches the radio unit configurations. For example, the RSM module for status code 100 must also be configured with an “in
route” (or very similar) descriptive text string. This descriptive text string is displayed in the RSM module’s title bar. In
addition, per personality programming, all radio units in the system must have an “in route” status selection = status code 100.
6.2.7.3.3 Configuration
Throughout an EDACS radio system, 128 status codes are available for status operations. Radio and system-level
messaging does not define a particular status code as an RSM status message or RTT status message. The console simply
receives the unit’s transmitted status code number along with its logical ID and logged-in group ID number. RSM or RTT
definition is accomplished via proper console configuration.
As previously stated, status code numbers must correspond to the code numbers programmed into the radio units. Each
C3 Maestro console for Windows NT supports 128 status codes numbered 0 - 127. Most EDACS radios which can transmit
status information can store and transmit ten (10) different status codes.
For the RSM option, up to 127 RSM modules may exist across multiple console module pages at a single console.
Likewise, for the RTT option, up to 127 RTT modules may exist across multiple console module pages. However, the
combined total of RSM and RTT modules at a single console cannot exceed 127.
In a properly configured system, each console status code’s description text string should match or approximately match
the corresponding radio status code’s text string programmed into the radios. Exact text string matching may not always be
possible or desired since maximum text string lengths differ between the console and the radios. At the console, each
description text string can be up to sixteen (16) characters in length. On a per status code basis, this text string along with
either RSM or RTT selection is stored in the console’s STATUS.INI file. For additional information on the STATUS.INI file,
refer to section 6.2.1.4 in this manual (page 27).
The following procedure lists the basic steps required to set-up RSM and RTT status options. Console-related and radio-
related configurations are included:
1. If system-wide status definitions are not already defined, define all needed statuses which will be required throughout
the system. Again, 128 statuses are available. Definitions should be well organized and planned-out for the system.
For example, if both RSM and RTT will be used, use status codes 0 — 63 for RSM status operations and use status
codes 64 — 127 for RTT status operations. Another good plan could use, for example, even-numbered status codes
for RSM and odd-numbered status codes for RTT.
2. If necessary, verify all EDACS radio unit’s in the system which require status operations are programmed
accordingly. A typical EDACS radio can store and transmit up to ten (10) different status codes. Again, this radio
personality programming must be consistent between all radios and consoles in the system. In addition, program each
radio for automatic group log-in, if desired. Also program each radio to either send status upon radio PTT or
automatically when the selected status is entered.
3. At a master C3 Maestro console for Windows NT in the system, use the Configuration Editor’s Radio Status dialog
box to construct a master STATUS.INI file. This file should contain all needed statuses and each status code’s
descriptive text string should match or approximately match the radios. Refer to section 6.2.2.10 in the manual (page
48) for Configuration Editor operation information.