MNB-00003-29 - User Manual Tait DMR Tier 3
MNB-00003-29 - User Manual Tait DMR Tier 3
MNB-00003-29 - User Manual Tait DMR Tier 3
Disclaimer
There are no warranties extended or granted by this
document. Tait International Limited accepts no
responsibility for damage arising from use of the
information contained in the document or of the
equipment and software it describes. It is the
responsibility of the user to ensure that use of such
information, equipment and software complies with the
laws, rules and regulations of the applicable
jurisdictions.
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Scope of Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Special Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Associated Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Acronyms and Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Publication Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.1 DMR Networks Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.2 Network Principles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1.2.1 RF Channels and Logical Channels. . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
1.2.2 Control Channels, Traffic Channels and Alternate Channels . . . . . . . . 22
1.2.3 Physical Sites and Functional Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1.2.4 Single Channel Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
1.2.5 Simulcast Channel Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2 Network Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.1 Network Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.2 Server Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.3 Channel Spacing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.4 Frequency Bands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.4.1 TB7300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.4.2 TB9300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.4.3 TB9400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.5 Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.6 Base Station Comparisons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2.7 IP Network Bandwidth. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.7.1 Bandwidth Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.7.2 IP Bandwidth Data Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2.7.3 Voice Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2.7.4 Packet Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2.7.5 Maintenance Traffic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.7.6 Node Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.7.7 Base Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.7.8 Network Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.7.9 Telephony Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.8 IP Protocols and Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
2.8.1 Additional Port Usage Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.9 IP Address Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
2.9.1 Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
5 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
5.1 Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
5.2 Logging on to the Control Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
5.3 Installing License Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
5.3.1 Checking That the License File is Correct. . . . . . . . . . . . . . . . . . . . . . 150
5.3.2 Obtaining the Host ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
5.3.3 Obtaining the license.dat File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
5.3.4 Installing the License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
5.3.5 Licensed Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
5.4 Loading SSL Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
5.4.1 Version 3.xx and Version 4.xx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
5.4.2 Version 2 and Earlier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
5.5 Setting Up Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
5.5.1 Version 3.xxx and Version 4.xx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
5.5.2 Version 2 and Earlier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
5.6 Configuring the Local Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
5.7 Configuring Network Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
5.8 Configuring Telephony. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
5.9 Configuring Subscribers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
5.9.1 Adding Encryption Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
5.9.2 Adding Unit/Group Profiles and Service Areas. . . . . . . . . . . . . . . . . . 160
5.9.3 Adding Partition Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
5.9.4 Add Fleets, Units and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
5.10 Configuring Nodes and Functional Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
5.11 Configuring Dual Control Channels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
5.12 Configuring Transmission Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
5.13 Configuring Transmit Interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
5.14 Configuring Interface Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
5.14.1 AIS Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
5.14.2 Conventional Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
5.14.3 DIP Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
5.14.4 Inter-network Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
5.14.5 TeamPTT Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
5.14.6 IP Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
5.14.7 MPT Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
6 Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
6.1 Stopping/Starting Node Controller Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
6.1.1 Version 3 and Version 4 Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
6.1.2 Version 2 Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
6.2 Powering Down the Node Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
6.3 Resetting a Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
6.4 Changing to a Local Time Zone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
6.4.1 TaitCentOS/Tait Ubuntu - Administration Application 1.16.01
and Later . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
6.4.2 TaitCentOS - Administration Application 1.14.xx and Earlier . . . . . . 189
6.4.3 Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
6.5 Downloading Call Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
6.6 Downloading Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
6.7 Downloading Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
6.8 Downloading General Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
6.9 Manually Downloading Files From a Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
6.10 Creating/Restoring Backups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
6.10.1 Version 3 and Version 4 Node Backups. . . . . . . . . . . . . . . . . . . . . . . . 194
6.10.2 Version 2 Node Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
6.11 Upgrading Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
6.11.1 Version 4 (Tait Ubuntu) Firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
6.11.2 Version 3 (TaitCentOS) Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
6.11.3 Version 2 Nodes Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
6.12 Setting Up Short Form and Network Operator Numbers. . . . . . . . . . . . . . . . . . . 201
6.12.1 Short Form PSTN Calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
6.12.2 Network Operator Calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
6.13 Using Status Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
6.14 Barring Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
6.15 Setting up Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
7 Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
7.1 Checking the Status of a Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
7.1.1 Using the Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
7.1.2 Using an ssh Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
7.2 Monitoring Calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
7.2.1 Call Records File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
7.2.2 Call Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
7.2.3 Call End Reasons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
7.2.4 Call Close Reasons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
7.2.5 Call Handler IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
7.2.6 System IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
7.3 Investigating Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
7.3.1 Alarm File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
7.3.2 Network Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
7.3.3 Radio Unit Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
7.4 Monitoring Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Scope of Manual
This manual is intended to provide a system-level introduction to TaitNet
DMR Trunked (Tier 3) radio systems, which are networks of IP
interconnected sites that enable radios with trunking capability to
communicate with each other.
Special Information
“File > Open” means “click File on the menu bar, then click Open on the
list of commands that pops up”. “Monitor > Module Details > Reciter”
means “click the Monitor icon on the toolbar, then in the navigation pane
find the Module Details group, and select Reciter from it”.
Please follow exactly any instruction that appears in the text as an ‘alert’.
An alert provides necessary safety information as well as instruction in the
proper use of the product. This manual uses the following types of alert:
This alert is used to warn about the risk of data loss or corruption.
Associated Documents
The current set of product documentation is available on the Tait Partner
Portal website (https://partnerinfo.taitcommunications.com).
■ Tait Core Networks Installation and Configuration Manual
(MNB-00012-xx)
■ TN9271 Analog Gateway Installation and Operation Manual
(MNB-00017-xx)
■ TN8271 Network Gateway Installation and Operation Manual
(MNA-00028-xx)
■ TB9300 Base Station Installation and Operation Manual
(MBC-00008-xx)
■ TB7300 Base Station Installation and Operation Manual
(MBD-00001-xx)
BCAST Data messages intended for all radios listening to the trunking
site control channel
IP Internet Protocol
MPT 1343 The most frequently used numbering scheme to partition the
MPT 1327 address space into more convenient sub-sections
for fleet management
OPUS Brand name of the interactive audio codec used to/from the
Tait AXIOM PTToX network
Publication Record
29 October 2022 Released for version 3.44 (TaitCentOS) and later, and version
4.44 (Tait Ubuntu) and later
■ Tait Ubuntu added throughout
■ Section 3.2.1 Tait TN9271 Analog Gateway and G.711
Connector updated
■ G.711/AIS-capable console systems added to Section 3.2.8
Interface Connectivity Options
■ Section 5.3.2 Obtaining the Host ID updated
■ Section 5.3.3 Obtaining the license.dat File updated
■ Section 6.2 Powering Down the Node Controller updated
■ Section 6.11.1 Version 4 (Tait Ubuntu) Firmware added
■ Section 7.2.2 Call Types updated
■ Section 7.2.3 Call End Reasons 121 added
■ Section 7.2.5 Call Handler IDs updated
■ Section 7.2.6 System IDs updated
■ Section 7.5 Monitoring Site Performance reference to html
reports removed
23 May 2020 Released for version 3.32 (and 2.32) and later
22 December 2019 Released for version 3.30 (and 2.30) and later
21 September 2019 Released for version 3.28 (and 2.28) and later
20 April 2019 Released for version 3.26 (and 2.36) and later
19 February 2019 Released for version 3.24 (and 2.24) and later
18 October 2018 Released for version 2.22, version 3.22 and later
17 May 2018 Released for version 2.20, version 3.02 and later
16 February 2018 Released for version 2.18, version 3.00 and later
All of the following DMR network types are available from Tait. In the
following diagram, the DMR trunked systems have been circled, as they
are the ones covered by this document:
Conventional Trunked
base station base station
Non-simulcast
Conventional non-simulcast
channel group
Channel group
(“voted channel”)
Simulcast
The following sections describe DMR trunked networks and their principal
concepts. DMR conventional networks are described in their own system
manual.
At its most fundamental level, a DMR trunked Access network can consist
of between one and four base stations/repeaters, located at an appropriate
location to provide coverage, operating with a number of radios (see “DMR
Access” on page 30). The base stations contain an embedded basic
software node controller, as well as performing normal repeater functions.
DMR mobile
radio(s)
interfaces to analog
equipment via TN9271
analog gateway
TB7300 base stations
WAN
All of these network types: Express6, Express20 and Full, support fallback
mode in the case of failure. If a base station loses its connection to the node,
and is configured for fallback, it will try to contact all the other base
stations at the same site and will start working in single-site trunking mode
to allow local calls to proceed. The base station in fallback mode will
advertise its alarm state by transmitting a limited service indicator to radios
until the network is returned to its normal operating mode. The Access
network type is configured as a standalone site, not fallback.
The embedded basic software node controller in the base station (that
allows for fallback mode or standalone operations) does not perform
any of the following:
There are other important network elements such as timing units, gateways,
and the IP linking network with switches and routers, but for reasons of
simplicity these (as well as the node controllers) will only be shown and
described in detail as required.
Version 3 and Version 3.xx (TaitCentOS) and version 4.xx (Tait Ubuntu) DMR systems
Version 4 DMR consist of a number of software application modules that are supplied
systems
depending on the network type.
Logical channel 1
Logical channel 1
Logical channel 2
DMR systems use digital modulation and 2-slot TDMA (time division
multiple access) on the RF path between the base stations and the mobile
radios. TDMA divides up the frequency spectrum using time slots whereby
user A gets a few milliseconds of access to the spectrum, then it’s the turn
of user B so that one physical channel (transceiver) provides two “logical”
channels on each 12.5 kHz bandwidth transmit and receive frequency (one
on each time slot).
The pair of RF frequencies for the two logical channels is the same.
The traffic channel is used to provide a communications path for many call
types, i.e. speech or packet data calls.
In a non-simulcast network, channel groups are not required, and all the
channels at one physical site form one functional site.
In a simulcast channel group, all the channels at all physical sites form one
functional site.
The following example shows a network with three functional sites (two
non-simulcast and one simulcast), made up of five physical sites.
Physical site 1 Physical site 2 Physical site 3 Physical site 4 Physical site 5
The grey frames show two functional sites (with two channels each) at
physical sites 1 and 2. Note that all the frequency pairs of the base stations
are different (Tx1/Rx1 to Tx4/Rx4).
The blue frame shows a simulcast functional site (with two channel groups)
at physical sites 3,4 and 5. Note that all the frequency pairs within each
channel group are the same (Tx5/Rx5 and Tx6/Rx6 respectively),
identifying it as a two-channel simulcast network.
Functional sites are configured in the node controller. If the physical sites
need to be defined (as the functional sites may contain more than one
physical site), this also needs to be defined in the node controller. If the
network has functional sites that consist of more than one physical site,
then configuration is also required in the Channel Group Manager
application.
In single channel base station operation, calls take place on only the
channels required for the call.
There are several issues that need to be taken into account when planning
a DMR trunked radio network. The areas to consider during this initial
planning phase are as follows:
■ Network Dimensions
■ Server Information
■ Channel Spacing
■ Frequency Bands
■ Power Supply
■ Base Station Comparisons
■ IP Network Bandwidth
■ IP Protocols and Ports
■ IP Address Planning
■ Network Linking Design
■ Audio Level Planning
■ Redundancy and High Availability
■ Speech Call Capacity
■ Data Support
■ Packet Data Transfer Times
■ Network Time Protocol
■ Centralized Authentication
Dell R240
Dell R230
Dell R220
Sintrones SBOX-2620
Sintrones SBOX-2621a
a. 560-00006-xx is the DIN rail mounting kit associated with this server
Note that the shaded areas denote equipment that has reached end-of-life
(by the manufacturer or by Tait), and whilst currently supported, is no
longer available.
It is important to note that the maximum dimensions listed below are for
individual DMR networks of each license type. Where larger systems are
required, a TN9500 Inter-network Gateway can be used to connect
individual DMR networks together to create a system of multiple networks
communicating together over a large coverage area.
Limits for high Limits for mid tier Limits for low tier
Element
tier servers servers servers
Nodes/network 20
Inter-network connections/networkg 1
G.711 connectors/network
■ co-located on TN9300 server 6 per server
■ co-located on TN9500 server 100 per server
The DMR high tier node supports 200 concurrent data calls. This means
200 single slot concurrent data calls, or 100 concurrent dual slot data
calls.
Where smaller networks are required, the DMR Express20, DMR Express6
and DMR Access licensed networks are available as follows:
DMR Express20 DMR Express20 has the following maximum dimensions, and requires
Express20 licenses for the node and reciters:
Sites/network 20
Control channels/network 20
Nodes/network 20
Inter-network connections/networka 1
Sites/network 6
Control channels/network 6
Nodes/network 1
Inter-network connections/networka 1
DMR Access DMR Access is for single site systems that do not require a node controller
as such, and has the following maximum dimensions. Access licenses are
installed in the reciters:
Element Limits
Sites/network 1
Control channels/network 1
Nodes/network Standalonea
As DMR Access does not have a node controller, some external interfaces
such as AIS, DIP and Voice Recorder connections are not supported.
Server Management
Server AC DC
Port
Idle current =
2.1A at -48V (101W)
250W maximum
2.4.1 TB7300
The TB7300 base station is available in the following frequency bands and
power:
Frequency
Frequency Band and Sub-band 40 W 50 W
Identification
The TB9300 base station is available in the following frequency bands and
power:
Frequency
50 W 100 W
Identification Frequency Band and Sub-band
2.4.3 TB9400
The TB9400 base station is available in the following frequency bands and
power:
Frequency
Frequency Band and Sub-band 50 W 100 W
Identification
Rx only Firmware only Firmware only - does not Hardware and firmware
affect maximum capacity options
a. The TB7300 base station is also available in a transportable variant in a Pelican case. The TB730x is the DMR
conventional transportable default package, and licenses are available for use in DMR trunked networks (see
Section 5.3.5 Licensed Features). Contact Tait for more information.
All DMR networks have a single designated control node. All other nodes
on the network are designated as switching nodes. Control traffic on the
network originates or terminates at the control node. In contrast, voice
traffic is switched by any one of the nodes on the network.
The control node is selected from any of the available nodes. The selection
algorithm is weighted so that the node with the lowest priority number will
be the control node. If the lowest priority number node should fail, then the
next lowest priority number node will become the control node.
The control node establishes connections to the base stations and network
gateways. The protocols used are UDP based, using ports 10001 to 10250
for base stations, and 9006 for network gateways1. The dispatch console
system establishes connections to the current control node using a TCP
based protocol on port 9005, or SIP on port 5060. For a full list of IP port
usage, go to “IP Protocols and Ports” on page 40.
The nodes maintain TCP connections to each other so that they can share
database updates and status. The bandwidth used by this link is normally
less than 100 kbit/sec, although this is dependent on system size (primarily
the number of radios on the system). Most of the traffic is from the control
node to the switching nodes and it is not necessary to scale the link
bandwidth when the number of nodes is increased.
1. Note that when a TN8271 network gateway is used for transcoding AMBE
to/from G.711, the network gateway uses port 9052 for the G.711 stream.
The following diagram shows the voice/packet data flow with no control
plane.
Call
The IP bandwidth allocation needs to take into account the number of base
stations and logical channels supported.
If the call is generated from the console instead of a radio, the flow is
similar. It is important to assign enough bandwidth for each of the nodes,
not only the control node.
Router with
2 – unicast mobile IP
Control node Switching node
1 - unicast
IP data
packets
Note that this scenario assumes that the IP data packets are not being sent
to other LMR equipment (i.e. other radios – as that is not the recommended
use of IP data).
Voice call requests are received by the control node from base stations,
dispatch console systems, and also from DIP, SIP, INP or legacy radio
network connections. On receipt by the control node, if the call request is
valid, the destination party or parties are available, and there is sufficient
resource (traffic channels, network gateways and switching nodes) to carry
the call, the call will be assigned to one of the switching nodes. The
resources required for the call are instructed to send and receive voice via
this switching node for the duration of the call. All voice traffic will be
switched directly through this node but control traffic will be switched
through the control node.
The control node will allocate a call to the switching node that is least
loaded. The control node is also treated as a switch in addition to its control
functions; it will be assigned to switch calls too.
It is possible to exclude one or more nodes from the list of switching nodes
that calls are assigned to by allocating a switching zone. If this is enabled
then voice packets will only be switched between nodes in the same
switching zone.
For traffic to and from each node, the expected traffic depends on the
number of nodes, number of network gateways and base stations. The
maximum number of devices a node can concurrently switch is 250, which
is approximately 4 Mbit/sec. This represents the absolute upper limit of
traffic to a node.
A basic estimate of bandwidth required for each node is: (bandwidth used
by dispatch system + bandwidth used by site) / (number of nodes available
For every site, we recommend that at least 100 kbit/sec is provided to allow
for the operation and collection of diagnostics using http or SNMP. As
using http cannot monitor many base stations simultaneously, it is not
normally necessary to provide the 100 kbit/sec to all sites at the same time.
It is acceptable to make a smaller bandwidth allowance on the backbone.
In the same way as the base stations, the bandwidth used by each network
gateway varies depending on the operating mode. Network gateways
(TN9271 analog gateway, G.711 connector, TN8271 network gateway)
process one call at a time.
2. Note that when a TN8271 network gateway is used for transcoding AMBE
to/from G.711, the network gateway uses port 9052 for the G.711 stream.
Notice Gratuitous ARP must be supported by the LAN for the high
availability feature in node controllers to work.
Where the port number could be in the range 3276 to 65535 (depending
on the Solaris/Linux/Windows ephemeral port range), it is listed as
‘UDP varies’ or ‘TCP varies’.
Destination Ports/
Source Ports
Type Usage Protocols
(on node)
(on remote device)
Core Interfaces
■ Voice data protocol Node controllers to/from UDP 9050 UDP 9050
(VDP) base stations and
network gateways, also
between control and
switching nodes for
packet data
■ Base station protocol Node controllers to/from UDP 10000 + site_ID UDP 9017, UDP11000 +
(BSP) base stations and Channel_Group_IDa
channel group managers
■ Channel group status Node controllers to/from UDP 9018 UDP 9018
protocol (SVP) base stations
■ Channel group voice Base stations to/from UDP 27260 UDP 27260
protocol (CGP) base stations
■ LDAP authentication LDAP authentication TCP varies TCP 389 and 636
server to/from node
controllers, switches,
base stations, network
gateways and routers
■ Mobile IP Cisco home agent router UDP 9070 UDP 434 and IP over IP
to node controllers
Management interfaces
a. For channel group managers, this is the port on which the channel group manager will listen for
messages from the TN9300 node controller.
You will need to make sure this port matches on both the node controller and channel group man-
ager. This can be found by logging into the node controller and navigating to the corresponding
site. From there select the channels tab. This tab lists the logical channels on the site. The logical
channels that represent channel groups will have an IP address of 127.0.0.1. Select the appropri-
ate channel and click View. On the next page there will be a field labelled IP address. This will con-
sist of an IP address and a port number, e.g.127.0.0.1:11001
In this example, the port number is 11001. For correct operation, the Simulcast/Voting > BS Chan-
nel Groups > Viewing and Editing a Base Station Channel Group's Configuration > Controller Port
field value in the channel group manager application must match. Tait recommends using port
11000 + channel group ID.
If you cannot find a corresponding logical channel on the node controller you will need to add one
and ensure that the Port field on the node controller matches this field.
Core Interfaces
■ Voice data protocol Node controllers to/from UDP 9050 UDP 9050
(VDP) base stations and
network gateways, also
between control and
switching nodes for
packet data
■ Base station protocol Node controllers to/from UDP 10000 + site_ID UDP 9017
(BSP) base stations
■ Channel group status Node controllers to/from UDP 9018 UDP 9018
protocol (SVP) base stations
■ Channel group voice Base stations to/from UDP 27260 UDP 27260
protocol (CGP) base stations
■ LDAP authentication LDAP authentication TCP varies TCP 389 and 636
server to/from node
controllers, switches,
base stations, network
gateways and routers
■ Mobile IP Cisco home agent router UDP 9070 UDP 434 and IP over IP
to node controllers
■ Real time protocol Dispatch systems to/from UDP varies UDP varies
(RTP) node controllers
Management interfaces
The ephemeral ports used by the base stations are in the range of 12500 to
14999 (inclusive).
They are all UDP ports which are configured via the base station WebUI
for communicating with the node controller, or within a channel group
when operating as a DMR base station.
These can be configured on the following base station WebUI pages when
the DMR software is running:
2.9.1 Structure
This section describes the Tait IP address plan for DMR systems. (This
standard address plan does not cater for simulcast networks. Please refer to
the TN9300 DMR Channel Group System Manual (MNB-00010-xx).)
All elements of the network require one IP address with the following
exceptions:
■ A virtual IP address is required for the node controller currently in
control mode. This IP address will move to whichever node controller
is operating in control mode. The use of the virtual IP address is not
required by all networks.
■ A second IP address is required for each node controller’s ILOM
(Oracle), BMC (Kontron) or iDRAC (DELL) console, depending on
server type
Tait builds its DMR systems with the private class B network 172.29.0.0
(mask 255.255.0.0), unless a customer has other requirements. The class B
block is split into ranges based on the third number of the IP address.
Host IP Description
Each site is assigned an ID in the range 1 to 100. The third number of the
IP address should be the site ID for site equipment.
Host IP Description
The following example shows the IP address plan for a network consisting
of:
■ 2 node controllers
■ 3 sites with 3 channels at each site
■ 2 dispatch consoles
■ 1 PC for general network management
■ 1 network gateway used for cross band repeat at Site 2
Host IP Notes
Switch 1 172.29.0.11
Site 1:
Host IP Notes
Site 2:
Host IP Notes
Site 3:
Host IP Notes
Network
Element
Node
Controller
Network Network
Element Element
Network
Element
For simulcast DMR networks, please refer to the TN9300 DMR Channel
Group System Manual (MNB-00010-xx).
Node For a single link (counting all network ‘hops’) between the node and
another element the standard requirements are:
For example, if the maximum link jitter is 20 ms, the base station and
network gateway delay buffers should be set to a minimum of 50 ms.
Site For (inter) site linking (both directions, each site) in DMR simulcast
networks, any base stations configured as master voters need to be
dimensioned to accept the aggregate uplink traffic from all satellite
receiver sites.
(n * 64 kbits/sec)
For all systems, increasing network latency causes a direct increase in call
setup delay or voice end-to-end delay.
The effects of not meeting timing requirements are worse for packet data
and encrypted voice than they are for clear voice. Voice communications
can tolerate some loss/late packets, but data cannot. With encrypted voice,
late entry performance is affected by late/lost packets.
For any delay and jitter outside of the specified limits, system performance
is not guaranteed. In addition, encrypted calls will be more affected by IP
links that are out of tolerance than clear speech. Digital artefacts may also
be heard due to over-the-air encryption synchronization issues caused by
late or missing voice packets.
2.10.4 QoS/DSCP
The table below lists the various packet types carried on Tait networks,
together with their recommended DSCP classification, based on their
criticality for the network.
Protocol/Port
Service Class Packet Type DSCP
Number
Expedited Voice data protocol (VDP/ UDP 9050 46 (EF)
Forwarding RTP)
(EF) Base station protocol (BSP) UDP 10001 to 10250 46 (EF)
Channel group status UDP 9018 46 (EF)
protocol (SVP)
Channel group voice UDP 27260 46 (EF)
protocol (CGP)
Voice recorder protocol UDP 9999 46 (EF)
(VRP)
Network gateway protocol UDP 9006 46 (EF)
(NGP)a
Protocol/Port
Service Class Packet Type DSCP
Number
Expedited Voice data protocol (VDP/ UDP 9050 46 (EF)
Forwarding RTP)
(EF) Base station protocol (BSP) UDP 10001 to 10250 46 (EF)
Assured Node to node TCP 9060 26 (AF31)
Forwarding communications
(AF) Application interface UDP 5060 26 (AF31)
specification (AIS)
Session initiation protocol UDP 5060 26 (AF31)
(SIP)
Location Information UDP 11433 26 (AF31)
protocol (LIP)
NTP TCP/UDP 123 26 (AF31)
Mobile IP UDP 434 26 (AF31)
ICMP (echo/ping) ICMP 26 (AF31)
Fragment Linking MiMOMax and routers using the Cisco multilink PPP protocol support
fragment linking. This breaks large lower-priority traffic into smaller
fragments and interleaves them with higher-priority traffic, so limiting
jitter for the higher-priority packets. In this situation the bandwidth
required for each site is smaller than 600 kb/s and is defined to be:
Bandwidth = 64 kb/s x physical channels + 100 kbps
Hence the minimum bandwidth for a single site running over MiMOMax
is 150-190 kbps.
RTP Header MiMOMax also supports RTP header compression, where redundant
Compression information is removed. In this case the bandwidth required for each site
is:
Bandwidth = 50 kb/s x physical channels + 100 kbps
Hence the minimum bandwidth for a single site running over MiMOMax
is 125-175 kbps.
For IP traffic in general, most linking backhaul does not fragment large
packets and interleave small packets within the data link. Because of this,
even if QoS is implemented, large TCP/IP packets (used to carry
management traffic) will cause delays unless the link speed/bandwidth is
high enough so that large packets are transmitted faster than the maximum
jitter time of 20 ms.
A TCP/IP packet of 1500 bytes takes a little less than 20 ms to send at 600
kbit/s. If we accept a higher permitted jitter then less link bandwidth is
required.
Jitter for a single link = (1500 x 8) / bandwidth in bit/s.
The following table indicates the delay buffer size required for different
link rates and maximum packet sizes. The values assume a system latency
The following table shows the effect of the delay buffer size on the end user
audio experience. The end-to-end audio latency excludes call setup delays.
Values over 400 ms are shaded, as they are not normally considered
acceptable. However, exceptions can be made on a case-by-case basis, for
example on networks largely used for one-way dispatch communications.
DMR servers have been thoroughly and successfully tested for both
10-BASE-T and 100-BASE-T.
Use a Cat-5 (minimum) cable for connecting the Ethernet socket to the
network via a router or switch. The Ethernet port speed is auto-negotiated
at start-up.
A level plan can establish the objective levels at each interface, in units of
measurements applicable to the interface, so that deployment engineers can
get them properly aligned. Without a level plan, audio from some interfaces
may appear much louder or quieter than from others. Signals may become
distorted (level too great for the local circuit) or signals may be excessively
noisy (level too low for the local circuit). It is important that regional
standards for telephony audio levels be taken into account so that levels can
be adjusted as necessary for each network.
Third party devices may also need to have their own audio levels adjusted.
Be aware that they may have different audio level requirements if they
operate in different modes (e.g. between MPT or DMR Trunking).
Regional Network
Node
Control Node
Switching Node
Regional Network
Node
Switching Node
Switching Node
This feature is integrated into the TN9300 architecture and does not need
any extra licensing, but it does require at least one switching node. Also all
the nodes in the network must be configured the same. If a modification is
made to the control node configuration, all the other switching nodes need
to be modified as well.
Other network interfaces between the node and third party equipment
needs to be defined carefully as defined in Section 2.12.6 Network
Interfaces.
The control node and the switching node that is the high availability backup
server are usually located together, and must be on the same subnet of the
IP network to provide a quick switchover. Whilst they have separate IP
addresses assigned to them, they are configured with the same active node
IP address for ease of hand-over.
This feature is integrated into the TN9300 architecture and does not need
any extra licensing, but it does require at least one switching node. Also all
the nodes in the network must be configured the same. If a modification is
made to the control node configuration, all the other switching nodes need
to be modified as well.
Regional Network
Node
Control Node
Switching Nodes
With the TNAS302 High Availability Node license installed however, the
control node and the switching nodes have their databases synchronized for
convenience. It is highly recommended to avoid having different
configurations on the servers. See Section 2.12.4 License TNAS302 for
more detail.
Other network interfaces between the node and third party equipment
needs to be defined carefully as defined in Section 2.12.6 Network
Interfaces.
Given these facts, if you are using an active node IP address, you must
ensure that your firewall will accept incoming and outgoing TCP/IP
communication on all three addresses: the active node IP address as
well as the two nodes’ actual IP addresses.
Examples of Using Case 1 - the node controller does not have an active IP address and it is not
Active IP HA (not recommended):
■ When the AIS client connects to the controller, it uses its physical IP
address
■ The controller then replies with its physical IP address in the SIP
message
Case 2 - Geographically diverse nodes with IP addresses that are not in the
same subnet. The node controllers do not have an active IP address and are
configured as HA:
■ When the AIS client connects to the controller, it uses its physical IP
address
■ The controller then replies with its physical IP address in the SIP
message
It is important that the AIS client is able to support more than one IP
address for this connection. If the control node fails, the AIS client will
need to go through the list of physical IP addresses (that are tried in
sequence) until one allows the client to register.
Case 3 - Nodes with IP addresses that are in the same subnet. The node
controllers are configured for HA and have an active IP address:
■ When the AIS client connects to the controller, it uses its physical IP
address
■ The controller then replies with its active IP address in the SIP message
It is important that the AIS client is able to support more than one IP
address for this connection. If the control node fails, the AIS client will
need to go through the list of physical IP addresses (that can be tried in
sequence) until one allows the client to register.
If the AIS client does not support more than one IP address for this con-
nection it could use the active IP address, but this is not recommended
because if the active IP fails, the connection to the controller is lost
(since active IP is managed by the node).
To Sites
To Sites
Node Controller
If the interface which has the active node IP address fails, the other
interface in the group/bond will become active and take over use of that IP
address.
Each node in the DMR network has its own database containing
configuration and unit registrations. The high availability license enables
the synchronization of the node databases so that if a hand-over occurs,
then the new control node is using a current set of data. This does not
include simulcast, so for channel group manager application
synchronization, see Section 2.12.7 High Availability in Version 3 and
Version 4 DMR Simulcast Systems.
This feature does not provide uninterrupted hand-over when control moves
to another node. In general all calls will be cleared as a result of a
switchover.
The active node IP address is used by multiple node controllers that are in
the same subnet. The use of the gratuitous ARP protocol requires high
availability nodes to be in the same subnet.
When a node is the control node it will be available via either its primary
IP address or the active node IP address. This allows connecting devices to
only be configured with one IP address for connecting to nodes in that
subnet.
Even with the use of the active node IP address, in the event of a hand-over
the connecting devices will still see the connection drop, and will need to
reconnect and login.
The active node IP address is only used for nodes on the same subnet.
Interfaces on the node such as DIP, AIS and SIP will reject incoming
connections unless they are from the control node.
Switchover The operation of the control node is not affected by the status of the other
modules (e.g. administration application or channel group manager). If one
of the other modules on the node fails, the control node has no way of
detecting this and will not switchover.
This means that in networks with more than one node controller server, the
control node’s controller application will not check if the channel group
manager is running on the server. If there are simulcast channels, the
controller application will not check the status of the channel group
manager application, therefore no switchover will happen if the channel
group manager application fails.
Synchronization The channel group manager module of the control node does not
synchronize its database to the switching nodes with HA licenses.
This means that after every configuration change, the channel group
manager database has to be backed up and restored as follows:
3. Select Files > Backup and load the backup file generated on the
control node’s channel group manager module (above).
The following formula calculates system utilization. The traffic load (or
carried traffic) is the average number of concurrent calls per unit time, and
in a system with 100% utilization, the number of erlangs will be equal to
the number of traffic channels.
t call
Load (erlangs) =
N .t
Where:
■ tcall is the summed duration of all calls
■ N is the number of channels
■ t is the time over which the load is measured
Where:
■ N is the number of channels
■ a is the load in erlangs
■ A = N·a
■ H is the mean call duration
■ t is the time to wait for service
The following graph shows that for a specified grade of service, the system
utilization improves as the number of channels increases. Ultimately,
adding more channels helps but the relationship between grade of service
and number of channels is not linear: adding more channels produces
Server
DMR RAP
application
Radio 1 Client
application
DIP RAP
BSP Base station DMR
Radio 2 Client
application
Unconfirmed
Dual Slot Single Slot
Packet Size Full 3/4 1/2 Full 3/4 1/2
Rate Rate Rate Rate Rate Rate
Confirmed No
Retries Dual Slot Single Slot
Packet Size Full 3/4 1/2 Full 3/4 1/2
Rate Rate Rate Rate Rate Rate
Confirmed 1 Retry
Dual Slot Single Slot
Packet Size Full 3/4 1/2 Full 3/4 1/2
Rate Rate Rate Rate Rate Rate
There are also two technical notes that can be used for reference:
■ TN-2674 Providing Synchronization to Tait Networks
■ TN-1779 Running an NTP server on the TN9300 DMR Node Controller
(this is applicable only to Solaris and TaitCentOS 6)
For their master time source, most NTP networks use Coordinated
Universal Time (UTC). This is because UTC is not only the same no matter
what time zone you are in, but also it is kept accurate by a constellation of
atomic clocks. These clocks ensure that UTC is maintained to extreme
precision, and getting a source of UTC time requires using an NTP time
server.
For Tait networks, NTP can be provided through a GPS sourced unit as part
of the system sale, or the customer may optionally provide their own. It is
recommended that all the network elements be synchronized to an external
NTP source connected to an atomic clock. If this is not the case, then at
least they should all be synchronized to the same source even if it is not
connected to an atomic clock.
Tait recommends the use of NTP for the reasons outlined below. It is a
compulsory requirement for Tait networks using DMR Mobile IP, but is
only optional for high availability systems.
Having an NTP time managed network can prevent all sorts of problems.
Because timestamps are the only method with which computers can tell
whether a transaction has occurred or not, if several devices on a network
are running different times, errors can easily occur as the network won’t
know which timestamp to trust. This could lead a network to believe a
transaction has taken place when it hasn’t, a transaction being repeated, or
data becoming lost. This is because to store any data, a system needs a
timestamp in order to store the information. However, if that timestamp
differs between machines, the system may believe the data has already
been stored, leading to information being discarded.
database
Authentication Authentication
request response
Login/
password
Access
granted/denied
Network users LMR network
(maintainers &
administrators)
AAA servers most commonly use one of two network protocols: LDAP or
RADIUS. The Tait AAA system supports both.
Current limitations ■ Start TLS method (TLS extension on port 389 by default) not supported
for LDAP in version 2 node controllers
■ No support for LDAP referrals
■ Nested groups not supported
■ LDAPS (LDAP over TLS on port 636) not supported
■ No support for posixGroups format (no support to memberUid
attribute), only LDAP Core schema is supported, i.e. groupOfNames or
groupOfUniqueNames format (member or uniqueMember attribute
containing the full user DN)
■ No support for TN8271 network gateway
3.1 Features
Tait DMR networks comply with the open, non-proprietary DMR ETSI
standard. Production of equipment according to this standard does not lie
with any one vendor, so network owners are not locked into obtaining their
equipment from one particular supplier. Interoperability between
equipment from different suppliers is assured by the DMR Association’s
interoperability testing process.
DMR offers two TDMA channels over a 12.5 kHz channel, providing
6.25 kHz equivalence voice calls.
3.1.2 Interoperability
Radio Support Tait DMR radios are trunked but also support a basic level of
interoperability. They can seamlessly roam or be manually switched onto
another organization’s conventional analog FM or trunked MPT network.
Infrastructure Tait DMR trunked networks can enable an analog FM talkgroup to join a
Support DMR talkgroup. The DMR network interfaces to analog FM base stations
via gateways, see “Analog FM Base Stations” on page 116. This interface
offers a fixed mapping between a DMR talkgroup and an analog FM
channel or a group defined by DCS code or CTCSS tone. Dispatch
equipment can provide a dynamically defined patch-style interface.
Tait TN9300 DMR Tier 3 Trunked System Manual Network Features and Interfaces 71
© Tait International Limited October 2022
Between DMR As different manufacturers bring DMR Tier 3 products to market, Tait will
Vendors actively work with the DMR Interoperability Process (IOP) to test and
certify that different vendors’ radios and infrastructure work together.
The DMR standard defines system level characteristics that all DMR
systems will have in common. The following table lists the significant
attributes inherent in the DMR standard.
Attribute Description
Alternate (or fast The control channel alternate slot (TSCCAS) can be
polling) channel configured for high capacity location polling using USBD
data transport
DMR standard Each site has an assigned priority, and vote now messages
priority vote now contain the priority of both the current site and the site to be
voted on. Radio units can be configured whether to use the
priority field or not. When enabled, radio units will use the
site with the highest priority.
72 Network Features and Interfaces Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
Attribute Description
TDMA Each time slot occupies 4800 bit/s per voice channel.
Two voice channels are supported at the same time on one
12.5 kHz RF channel with each occupying ~30 ms slot
periods. This provides 6.25 kHz equivalent operation and
meets the ultra narrow-banding regulations of almost all
countries in the world.
a. The lowest frequency band offered by Tait's TB9300 and TB7300 base stations is
B1 band (136MHz). The lowest frequency band offered by Tait's TB9400 base sta-
tion is B3 band (148MHz).
Tait TN9300 DMR Tier 3 Trunked System Manual Network Features and Interfaces 73
© Tait International Limited October 2022
3.1.4 Tait DMR System Features
The following table outlines the relevant features that Tait DMR supports.
Feature Description
Access priority Five priority levels exist (Emergency is the highest priority
levels level):
■ No priority - normal
■ Priority 1 - low
■ Priority 2 - medium
■ Priority 3 - high
■ Emergency
Adaptive channel When enabled, this feature speeds up the unit’s re-entry
grant (or GTC in time to a group when it hunts to a new site by sending
MPT) channel grants at an adapted rate. It does this when the
unit registers or when it affiliates to a group, if that group is
also configured to support adaptive channel grants. The
unit is then sent a channel grant for the highest priority
group that it is affiliated to, if a call for that group is currently
on channel.
AES voice AES 128 and AES 256 encryption and decryption (if
encryption installed) is available for radio-to-radio and radio-to-group
calls and for voice calls involving external interfaces such
as MPT gateways, phones, AIS, SIP, DIP, and VRP. Note
that audio to and from these external connections is
unencrypted. AES offers a higher standard of encryption
than DES.
Audio latency Latency time from the PTT of the ‘a’ party, including call
setup time, to the audio out of the ‘b’ party has a mean
value of 400 ms.
Due to the slotted and random access nature of the control
channel, this is a mean value assuming a relatively idle
control channel.
This could be longer in calls with late entry with encryption.
Automatic Vehicle The DMR system provides the facility for transferring GPS
Location information from mobiles and portables and making this
information available via a network connection. Tait Mobile
radios support direct connect GPS receivers and Tait
Portable radios include an internal GPS receiver. (See TD-
0044-xx for more information on AVL.)
74 Network Features and Interfaces Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
Feature Description
Call processing Call processing is distributed between the sites and nodes.
Calls between users on the same site are known as local
calls. Calls between users on different sites are referred to
as intersite calls.
Tait TN9300 DMR Tier 3 Trunked System Manual Network Features and Interfaces 75
© Tait International Limited October 2022
Feature Description
Caller ID For individual calls, user radios display the ID of the radio
initiating the call. For group calls, user radios display the ID
(or alias if it is programmed) of the radio initiating the call.
The user ID alias of the subscriber initiating the call is
displayed on dispatch consoles for both group and
individual calls. In addition, the ID of the talking party in a
group call can be displayed on a radio and dispatch
consoles.
Channel rotation Traffic channel rotation enables calls to rotate through the
available traffic channels, resulting in equal use of all
channels. Each consecutive call at the site is set up on the
next highest channel. When the highest channel number is
reached, the next call will set up on the lowest available
channel, thus forming a rotational channel allocation
pattern.
Use of this feature can extend the life of base stations by
keeping the average temperature down.
76 Network Features and Interfaces Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
Feature Description
Critical site Critical site assignment is covered by the Tait Essential Site
assignment feature:
■ A talkgroup can be configured so that calls to the group
must include any sites marked as essential sites for that
talkgroup. If a site marked as essential is busy for more
than the maximum configured queuing time when a call
is initiated to the group, then the call is aborted. Note
that a group call made at the Emergency level will pre-
empt calls in progress to make a traffic channel available
if necessary.
■ When a TN9500 Inter-Network Gateway is used, the
linked networks are autonomous, so their essential sites
will not be recognized by each other. If a group call is
made on network A, with a party of the call on network
B, network A will assign resources to the call when it can
and network B will do the same (independently). This
means that if network B is busy (no resources available),
the call will be queued on network B only, as linked
networks are considered non-essential. If network A is
busy (no resources available), the call will be queued on
network A only, and resources will be allocated on B
until the call times out.
Dispatch console Tait DMR supports AIS version 1.0 and this implementation
interfacing will be updated to stay aligned with the evolvement of AIS.
Dual / triple / quad Tait delivers radio solutions that offer conventional analog
modes of operation FM, MPT 1327, DMR conventional and DMR trunked
operation. This offers flexible system planning options for
legacy & migration support.
Tait TN9300 DMR Tier 3 Trunked System Manual Network Features and Interfaces 77
© Tait International Limited October 2022
Feature Description
Emergency call Emergency calls shall take precedence over all other calls.
pre-emption Emergency call may be pre-emptive causing another call to
be cleared down if the resource requested for the
emergency call is not available.
Packet data A dispatcher or radio can initiate a packet data call that
allows confirmed or unconfirmed data to be sent on a traffic
channel. Useful for sending large payloads. Note that if Tait
radios receive a channel grant for a voice call in the middle
of an existing packet data call, the radios’ default behavior
is to leave the current data call and join the newly setup
voice call.
Radio roaming Seamless roaming allows radio units to roam freely within
the parts of the network where they are authorized to have
service.
78 Network Features and Interfaces Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
Feature Description
Tait TN9300 DMR Tier 3 Trunked System Manual Network Features and Interfaces 79
© Tait International Limited October 2022
Feature Description
Tait adaptive vote This is a Tait-customized vote now feature where the vote
now now offset threshold and vote now margin can be adjusted
per site. By setting these levels you effectively configure
how to either make radio units hold on to one site for as
long as possible, or jump to another site faster. This feature
is for use on those sites that have better capacity than
others; where it is beneficial for the radio units to stay on
the site for as long as possible. See Section 3.1.13
Adaptive Vote Now for more information.
Tait group affiliation The system supports Tait group affiliation for subscribers.
Dispatch consoles are capable of monitoring multiple talk
groups.
Text messaging The dispatcher or a radio can send a radio user or group
free-form text, which can be read from the radio’s LCD
screen.
80 Network Features and Interfaces Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
Feature Description
Voice recorder The DMR system provides the ability to record the audio for
interfacing each voice call. The node sends Voice Recorder Protocol
(VRP) packets to the IP addresses configured in the node
controller.
Migration from an analog network to a Tait DMR network is easy and cost
effective, especially if the analog network uses the same 12.5 kHz channel
spacing as used by the DMR network. In such cases the antennas’
combiners and other RF site equipment can be re-used. TN9271 analog
gateways are used to facilitate communications between those still on the
old analog network and those on the new DMR network.
For migration from analog FM or MPT 1327, the Tait radios provide triple
functionality: DMR, MPT 1327 and Analog FM.
The use of TDMA means that there will be an effective doubling of logical
channels which doubles the network’s voice capacity. Coverage of a digital
DMR base station is comparable with coverage of the analog equivalent, so
additional transmission towers need not be built.
3.1.6 Scalability
A Tait DMR network is scalable from a single site with one base station to
a large, wide area network with multiple nodes, 1000 base stations and 300
network gateways. One node is needed for every 250 talk paths in the
network. One or more additional nodes are desirable for redundancy. Each
reciter in a base station provides two voice channels and each gateway a
single voice channel.
Tait TN9300 DMR Tier 3 Trunked System Manual Network Features and Interfaces 81
© Tait International Limited October 2022
To determine the number of nodes required, simply add all available voice
channels, divide by two hundred and fifty and add one:
The control node sets up and clears down all calls. Control communications
are with the control node’s logical IP address. This design avoids the
reliability problems experienced in networks that use multicast addressing,
which require careful configuration of routers and switches through the
many hardware and firmware changes over the life of the network.
This does not introduce a single point of failure, because if the control node
fails, another node takes over the logical IP address.
With channel authorization, when there are multiple call requests, only one
radio gets a go-ahead from the network. The winning radio gives a go-
ahead beep to let the radio user know they have succeeded gaining the
uplink, while other radios give an audible deny signal.
How Channel Radios operate in simplex mode, so once a radio begins transmitting it is
Authorization not possible for the user to hear if someone else may also be talking, and
Works
that they should stop transmitting to avoid a collision.
82 Network Features and Interfaces Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
Base stations recognise the initial burst as a reservation request. If the base
station has not already reserved the floor, it does so, and begins forwarding
a stream of the same reservation request to the controller. The controller
repeats the reservation stream back to the base stations so that all radios can
recognise that the floor is reserved, and can know who won the reservation.
If two radios at different sites both succeed in reserving the base station
floors, the controller still only repeats the first stream to arrive from any
base station.
PSTN calls
Notes ■ Good networks with heavy traffic and good coverage particularly
benefit from channel authorization. Networks with less traffic, greater
network delays and significant areas of poor coverage are likely to
benefit less.
■ The Tait network is flexible - the controller allows call overs to use the
authorization handshake (polite) or not (impolite). It is possible to mix
polite and impolite radios in the network, but the benefits of the feature
diminish as the proportion of radios using impolite access increases.
■ Channel authorization does impose a small additional call set-up delay
to complete the authorization handshake. This delay will be more
noticeable as network linking delays increase.
■ In a poor coverage or fading environment, call set-up can take longer if
radios need to time-out and retry when performing the authorization
handshake.
Deployment 1. The DMR network must be operating version 3.38 or later (or
Prerequisites version 4.xx).
Tait TN9300 DMR Tier 3 Trunked System Manual Network Features and Interfaces 83
© Tait International Limited October 2022
2. The DMR base stations must be operating version 3.20 or later.
3. The Tait radios must be operating version 2.28 or later, and have the
channel authorization parameters configured (Trunked > Radio
Calls > Call Options > DMR ‘Channel Authorization’).
Fallback and stand alone operation in the base station does not depend on
the controller. The base station has configuration parameters for channel
authorization for these cases.
The DMR external adjacent site feature can be configured for each site.
There are two types of external adjacent site: either those that are fixed,
as in cell extender sites, or those that are inter-network. For external
adjacent fixed (or cell extender) sites, the external adjacent site informa-
tion will enable radios to vote between the site and the external fixed
site. For external adjacent inter-network sites, the external adjacent site
belongs to an external DMR or MPT-IP network (using an inter-network
connection); and the current network will broadcast information about
this external site (RF number and syscode) to enable radios to vote
84 Network Features and Interfaces Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
between the site and the external inter-network site. For configuration
instructions, see Section 5.16 Configuring External Sites.
■ If voting is enabled, the radio will move to another site (DMR or MPT)
if the current signal is < L2 (default value -94dBm), and the sampled
signal is higher than the radio’s Vote Now Advice Margin
■ If the signal < L0 (default value for high power -113dBm) and there is
loss of service or if the codeword error is high, then the radio will
behave as follows:
a. It will first perform an adjacent channel hunt (this uses the chan-
nels it has learnt from the vote now messages)
b. It will then perform a preferential hunt (based on the channels
defined on the programming application’s hunt channels -
defined in the Hunting Parameters, then on the other channels it
has learnt from the vote now messages as well as on any other
channels that the radio has previously learnt and used for ser-
vice).
■ Background hunting will operate in fallback/failsoft modes, regardless
of the radio configuration
■ If the system for any reason enters fallback mode, Tait radios (TM9300/
TP9300/TP9500 and TM8200) will first perform a preferential hunt in
order to tune into the fallback channel
■ In TM9300/TP9300/TP9500 radios in fallback mode, at the end of each
call the radio will perform a preferential hunt in order to check if the
system is up and running again. This will affect radio behavior as radios
could miss any calls that may happen during the preferential hunt. This
will depend on the size of the hunt list.
In addition, at regular intervals when the system is idle (approximately
every 15 seconds), the radio will perform a background hunt. The radio
could miss any calls that may happen during this period.
■ The TM9300/TP9300/TP9500 (not the TM8200) when in fallback
mode, will display ‘Limited Service’ (if registration BCAST messages
are enabled, which is the default on Tait base stations). If Registration
BCAST is disabled, the radio will not know that the system is in
fallback mode and will not perform a preferential hunt at the end of each
call. It will however, perform a background hunt as configured.
The node keeps track of which groups have one or more members at a site,
so that when a group call is made, the call is set up only on those sites where
group members are present.
When a unit affiliates to a group (or multiple groups) the affiliation is one
of two types:
■ Subscription: this is the process by which a radio unit informs the
network of which talk groups are relevant for the said unit for the
purpose of registration-based groups. Standards-based subscription is
Tait TN9300 DMR Tier 3 Trunked System Manual Network Features and Interfaces 85
© Tait International Limited October 2022
analogous with Tait’s existing and proprietary Group Affiliation (also
referred to as RCGA).
■ Attachment: this is slightly different to subscription in that it allows a
network to authorize only certain groups for a radio unit at a particular
site. The unit can then choose to remain at the site, with perhaps no
access to unauthorized groups, or choose to move to a new site for better
service.
Group Affiliations Normally the node controller only requires group affiliations from a unit
Required on Site the first time it powers up, or if it changes its groups. The node controller
Move
will remember the groups a unit is in, even when it moves sites, so it will
set up group calls at the appropriate sites.
However, if the group attachment feature is enabled in a unit, the unit will
need to know if its groups are supported at each site it tries to register on,
so that it can select sites based only on where its group calls will still be set
up. This requires the unit to always affiliate when it registers at a new site,
as the acknowledgment report from the node controller is the only way to
inform the unit which groups can be setup at the site.
From release 3.40 of the node WebUI, the Group Affiliations Required on
Site Move parameter has been added to Settings >Network Parameters >
Features.
86 Network Features and Interfaces Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
move will use more control channel bandwidth on every site registration,
so it should only be used if talkgroup attachment is required.
The Subscribers > Group Profile parameters Restrict to Fleet Members and
Restrict Affiliations to Service Area are used by the node controller to
restrict group affiliations. If neither of these parameters are enabled, there
is no point enabling the Group Affiliations Required on Site Move
parameter, as all group affiliations will be allowed.
In a trunked network, when a radio user presses PTT, the radio does not
simply begin transmitting, as in a conventional system. Instead, it sends a
call request, which the node processes. If the request is approved, the radio
is instructed to tune itself to the frequency pair of a free traffic channel and
to use its timeslot. This happens so quickly that the user can simply press
PTT and begin talking.
calling destination
radio node group
group
voice
requ est [1
, 2]
control
] group
rant [3 voice channel
c ha nnel g c hanne
l
e grant
grou p voic [3]
conversation [5, 6]
call inactivity
timer [7] traffic
tion call te channel
rmina rm
call te inatio
n
The following describes how the trunked network handles a group call.
4. The user presses PTT, causing the radio to send a group voice request
to the control channel.
5. The control channel passes this request on to the node, which carries
out a validation check on it. The call can only proceed if it passes this
check. If it fails, the node sends a call deny message and the radio
beeps accordingly.
Tait TN9300 DMR Tier 3 Trunked System Manual Network Features and Interfaces 87
© Tait International Limited October 2022
message. If there is no free traffic channel, the call is queued and the
radio emits the corresponding tone.
7. The calling radio and other radios belonging to the group go to the
traffic channel specified in the message. The calling radio can
optionally give ‘go ahead’ beeps to indicate that the call has been set
up.
8. The caller begins talking. The traffic channel receives the call,
repeats it, and sends it to the node.
10. When the user releases PTT, the network behaves differently
depending on its configuration:
■ If the call inactivity timer is set to several seconds or more (it can
be configured to anything between 0 and 60 seconds), the
network provides quasi-transmission trunking. For quasi-
transmission trunking, the inactivity timer must be set to at least
1 second.
■ If it is set to 0 seconds, the network does not time out for
inactivity.
88 Network Features and Interfaces Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
3.1.12 Roaming
Radios are able to roam from one site to another. At a configurable interval,
control channels send C_BCAST (Vote Now) messages that instruct idle
radios to assess the signal quality of the control channel specified by the
message. If the quality of the control channel is significantly better, the
radio registers with it. Roaming cannot occur in the middle of a call.
Tait recommends that no more than twenty adjacent sites be configured for
each site. These adjacent sites can be internal sites, external inter-network
sites, or external fixed sites. Only the sites nearest in location to the current
control channel should be configured as adjacent in order to maintain
acceptable performance during site re-selection.
For external inter-network adjacent sites, only the site alias is configured
between the networks; using the inter-network connection protocol, the
networks regularly exchange this information, so if the site information
(site alias, RF control channel number, syscode) changes, each network
will receive the updated control channel parameters (which can be viewed
on the WebUI).
Tait TN9300 DMR Tier 3 Trunked System Manual Network Features and Interfaces 89
© Tait International Limited October 2022
3.1.13 Adaptive Vote Now
This is a Tait-customized vote now feature where the vote now offset
threshold and vote now margin can be adjusted per site. By setting these
levels you effectively configure how to either make radio units hold on to
one site for as long as possible, or roam to another site faster. This feature
is for use on those sites that have better capacity or higher importance than
others; where it is beneficial for the radio units to stay on the site for as long
as possible.
The adjustable settings are Vote Now Threshold Offset and Vote Now
Advice Margin. The vote now threshold applies an offset of the chosen
value to the radios pre-programmed L2 level. The selected vote now advice
margin, on the other hand, is an absolute value that replaces the advice
margin value pre-programmed into the radio for that voting instance. These
adjustable settings are not permanent in the radios, and are learned and used
per vote now request. If Non-preferred Site is selected as the setting for the
Vote Now Threshold Offset or Vote Now Advice Margin parameters, this
means that the radio will only use its programmed values.
Feature Example In the following diagram, all radios are currently registered at Site A, and
all are configured with an ‘RSSI Level for L2 (Hunt)’ parameter set to
-80dBm, and a Vote Now Advice Margin of 6dB configured via radio
programming.
This means that when Adaptive Vote Now is not enabled, or the adaptive
vote now parameters are set to ‘Non-preferred site’, the current control
channel signal received by all radios at Site A needs to be less than -80dBm
before the radio will consider roaming via Vote Now, and the candidate
control channel must be 6dB greater than the currently selected control
channel.
90 Network Features and Interfaces Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
Site A
Adaptive vote now parameters:
• Vote now threshold offset = -15dB
• Vote now advice margin = +9dB
Site C
Radio
One
Radio
Three
Radio
Two
Site B
Adaptive vote now parameters:
• Vote now threshold offset = -10dB
• Vote now advice margin = +3dB
■ When the adaptive vote now parameter ‘Vote Now Threshold Offset’ at
Site A is set to -15dB, and the adaptive vote now feature is enabled, the
radios will adjust their L2 for each vote to -95dBm. This is the ‘RSSI
Level for L2 (Hunt)’ parameter programmed into the radio plus the
broadcast ‘Vote Now Threshold Offset’ parameter
(-80 + -15 = -95dBm). This means that the current control channel
received by radios on Site A needs to be less than -95dBm before the
radio will consider roaming via Vote Now. If the L2 signal strength
validation is successful, the candidate control channel being sampled at
Site B and Site C via Vote Now would also have to be +9dB stronger
than the signal received from site A for the radio to move, due to
Site A’s advertised Vote Now Advice Margin.
■ If a radio registered on Site B were to be sampling Site A via vote now,
then the applied L2 and Vote Now Advice Margin for each vote would
be -92dBm and +3dB respectively. This is the ‘RSSI Level for L2
(Hunt)’ parameter programmed into the radio plus the ‘Vote Now
Threshold Offset’ parameter (-80 + -12 = -92dBm). This means That the
current signal strength from Site B would need to be less than -92dBm,
and Site A would have to be +3dB stronger in signal strength than the
currently received Site B for the radio to move.
■ If a radio registered on Site C were to be sampling Site A via vote now,
then the applied L2 and Vote Now Advice Margin for each vote would
be -90dBm and +3dB respectively.
Tait TN9300 DMR Tier 3 Trunked System Manual Network Features and Interfaces 91
© Tait International Limited October 2022
3.1.14 Failure Tolerance
92 Network Features and Interfaces Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
If this fails... Then...
Alternate channel The control channel has failed and a new control channel
will take over:
■ If the new control channel has its alternate channel
enabled, then polling will continue on the new alternate
channel, unless it is the only channel left at the site
configured for traffic channel use, in which case the
node will leave it available for traffic channel calls, and
not use it for polling
■ If only one alternate channel has been configured at the
site, polling will continue on the control channel, but only
for radios that have polling enabled on both the control
and alternate channels
Traffic channel Channel capacity is reduced by two (or four, if a full subrack
fails). The network automatically takes the RF channel(s)
out of service.
Gateway The devices attached to the gateway lose service. To
mitigate this, multiple network gateways may be used.
a. See Section 3.1.15 Single Site (DMR Access) or Fallback Mode.
Single site (DMR Access) is a DMR single site system where the base
station itself acts as a standalone node.
Similarly, in a multi-site system with a single node (if it should fail), at each
site a base station takes over, entering fallback mode and exercising control
channel and basic node functions as follows:
■ Status messages (on the control channel)
■ Individual calls (OACSU/FOACSU)
■ Group calls
■ Emergency calls (with pre-emption)2
Tait TN9300 DMR Tier 3 Trunked System Manual Network Features and Interfaces 93
© Tait International Limited October 2022
In fallback mode, each site sends a ‘limited connectivity’ message to the
radios at the site, which will then display ‘Limited Service’. The radios will
also periodically perform a background hunt to find another control
channel when in fallback mode. Since radios will spend less time listening
to the confirmed control channel, it is possible that important messages
may be missed.
Base station Single site trunking and trunked fallback require one base station at a site
operation in single to become a controller and the site’s other base stations to operate as traffic
site or fallback
mode channels.
■ The controller operates a control channel that allows radios to make
calls
■ The controller does not have a registration database. Any radio can
request registration and be granted it.
■ The controller hands off call requests to traffic channels which then
repeat the radio signal
■ Base stations at each site co-ordinate roles using the site discovery
protocol (set in the base station user interface at Configure > Network
interfaces > DMR network > Site)
Each base station user interface shows the statuses of other channels at the
same site at Monitor > Network > DMR site status.
The call amalgamation feature enables a radio to join an existing group call.
A call record will be created for the radio to show that it has been
amalgamated into an existing group call, but the group call’s original call
record remains unchanged.
The following examples show how the call amalgamation feature works.
Group Calls The call amalgamation feature allows a radio that has been in another call
to join a group call that was previously set up without it, simply by calling
the group. It can also be used to rejoin a group call if the radio has
previously left the call but wants to go back to it, providing it was not the
originator of the call.
Call amalgamation is also used to join to an existing group call when the
radio has not received or is ignoring GTC messages.
94 Network Features and Interfaces Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
Notice For emergency calls, call amalgamation will only happen if
the radio to be amalgamated into the group call has used the same pri-
ority, when calling the group, as the existing call. For non emergency
calls, call amalgamation will work even if different priorities are used.
For example: if a normal group call is in progress and a user calls this
group as an emergency call, then the original group call is closed and a
new emergency priority call is established.
Individual Calls If a radio that has been programmed to allow individual call override is in
an individual call, it can be amalgamated into a group call set up on a
different traffic channel. The individual call it was in will still be active,
and will only clear either:
■ At the end of the activity timeout
■ At the end of the call duration timeout
■ Or by the other party remaining in the call
If the radio it was in the individual call with has the same override settings
enabled and is also amalgamated into the group call, the original individual
call will again still be active until it times out, otherwise it will be left in the
original individual call.
Radio users outside the radio coverage area of the network, or working in
a team at a local site, may wish to operate in digital simplex mode (or direct
mode), communicating directly between their radios and bypassing the
network. Radios that are programmed to operate on a single frequency are
automatically set up in digital simplex mode. A number of services that are
supported in the wide area solutions are also supported in direct mode.
These include talkgroups, individual calls, GPS location updates, status,
etc.
Protected Access Radio access to the services of the network is controlled through
to Network Services administrator configuration of the node. Only radios using numbers that
have been declared to the node can use the network. A radio can also be
restricted to operation only at selected sites. A radio must first register on
the network before using its services.
To prevent radios from usurping the identity of a legitimate radio, the node
can ask radios to authenticate themselves when they register.
The authentication process is based on RC4 encryption (a popular
encryption algorithm commonly used to protect Internet and wireless
traffic). Radios have a 56-bit authentication key. The administrator can bar
any radio from using the network.
Tait TN9300 DMR Tier 3 Trunked System Manual Network Features and Interfaces 95
© Tait International Limited October 2022
Protected Access The nodes and base stations in a DMR network have various levels of
to Network protection against unauthorized access. Browser communications with
Infrastructure
these elements are encrypted using HTTPS. Users can be given different
levels of access. They must log in with a unique name and password.
Logs provide an audit trail that indicates the actions of each user.
Private Digital transmissions by their very nature ensure a certain level of privacy.
Communications Eavesdropping requires the use of DMR-capable scanners.
Some network users may want to increase that level of privacy through the
use of encryption. Tait can offer DES and ARC4 encryption.
3.1.19 Registration/Authentication
Before a radio can use the network, it must be registered and authenticated.
The node maintains a database of registered radios and their locations.
An authentication request is only accepted if the node knows about the
radio and the radio is at a site where it is authorized to have service.
Through authentication, the radio declares its location to the network as it
moves around. This permits calls to be connected without searching
through the network for the called party.
During a normal call setup, if the radio is not at the site where it is
registered, the node will hunt for the radio. When it finds the radio, the call
will setup, and the radio’s registration record will be updated.
However, with USBD AVL polling, the radio is only ever polled at the
control channel and site where it is registered, regardless of whether it is
still there or not. If AVL polling is the only interaction the node has with a
unit, the polls could potentially fail for a long period of time if the
registration record is out-of-date.
Background polls that are designed to try and find a potentially lost unit can
be enabled. The background checks work as follows:
■ If a registered radio fails to respond to a call setup or poll, it will be
added to a queue of radios to be background polled
■ By default, every 10 seconds, one radio in the queue will be sent an
availability check in the background to try and find the radio (system
poll period)
■ If the radio responds, the registration record is updated and the radio is
removed from the queue
96 Network Features and Interfaces Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
■ If the radio does not respond, it will be added back to the queue to be
polled again at a later time (minimum unit poll period)
■ Background polling for a unit will also stop if other activity by the radio
is detected, such as other call setups
3.1.21 Encryption
Tait DMR networks (also TM9300 and TP9300/TP9500 radios) support the
following encryption types3:
■ DES56
■ ARC4
■ AES 128
■ AES 256
The Tait radios that are loaded with DES, AES or ARC4 encryption keys
are very secure. The encrypted keys in the radios cannot be read. DMR
nodes using DES, AES or ARC4 encryption keys are also very secure. The
encrypted keys are securely stored in the node database. However Tait
programming applications do allow for the configuration files containing
the encryption keys to be backed up, so it is very important to store these
files in a secure location.
The DMR node webUI and programming applications for the TM9300 and
TP9300/TP9500 radios allow for the created keys to be copied/pasted,
allowing for ease of configuration. Note that on the node webUI, this can
only be done when the key is being entered, as after this the key is not
available to be read again.
Tait TN9300 DMR Tier 3 Trunked System Manual Network Features and Interfaces 97
© Tait International Limited October 2022
Notice Encryption stops in the node controller for all external inter-
faces.
Base station
A radio configured with an encryption key can receive clear voice from a
radio without encryption. Disabling encryption via a function key or menu
on a radio only affects the transmitter, the radio will still decrypt calls.
The network can be set up with secure remote access for use by Tait support
staff or by on-call network administrators working from home. (Tait offers
several tiers of service contract that can provide remote technical support
of the network.) For example, the remote PC can use a VPN (Virtual
Private Network) connection over the public Internet to an on-site
administrator PC and the Microsoft Remote Desktop protocol so that a
Tait Enable client can log in to base stations.
98 Network Features and Interfaces Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
3.1.23 IP Data
The IP data feature provides a generic IP data service that is able to pass IP
data between radios and a data server that is IP-connected to the network.
It provides the foundation that enables clients and partners to deliver data
applications and for network users to access them across the network.
Licenses are required for the DMR node controller and radios to operate IP
data.
Control Channel
• Network registration
• IP address registration PPP
• Data channel request/
grant
PC Application
Data Server
IP data uses mobile IP4. This protocol allows the radios to appear like other
IP devices on the IP network. Standard routing protocols and techniques
can be used to maintain connectivity to them.
For a radio to use IP data, the use of data must be enabled and an IP address
must be assigned in its configuration. When a radio registers with the DMR
network, it also registers its IP address. The node establishes a session with
the mobile IP home agent (generally a telephony router logically close to
the node). Radios can roam to other sites and still maintain the same mobile
IP session.
IP data is carried over the traffic channels. The traffic channels can be
configured with different priorities, depending on whether voice or data is
more important. Call timers are also configurable. Narrow band radio
channels provide a low bandwidth IP link, and applications using them will
get the best performance by using application protocols specifically
designed for half-duplex low bandwidth links.
4. DMR mobile IP requires the use of NTP (see “Network Time Protocol” on
page 67)
Tait TN9300 DMR Tier 3 Trunked System Manual Network Features and Interfaces 99
© Tait International Limited October 2022
3.1.24 Location
Mark a Point of This feature allows a radio user to press a button which sends their current
Interest location to a dispatcher.
For example, a train driver might see something on the tracks or by the side
of the train that should be reported to the dispatcher. Depending on the
incident, a dispatcher may need to alert the authorities and tell them where
it happened.
This used to be done using a voice call, which depended on the radio user
getting through to a dispatcher at the right time. Now, with the press of one
button, the AIS call-alert service (defined in AIS1.0) is used to pass the
location to the dispatcher immediately.
Compliance Transmit interrupt is only available when the DMR specification parameter
in Settings > Network Parameters > Compliance is configured as version
1.8.1 or later.
Functional In its simplest form, the Transmit Interrupt feature relies on two
Overview mechanisms over the air interface:
100 Network Features and Interfaces Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
for standard mode. Standard mode will typically be used if third
party radios are also used in the infrastructure.)
■ The network infrastructure sends a cease transmission command/
request via an embedded outbound reverse channel (RC) burst on
the adjacent TDMA slot
■ The transmitting radio unit receives and decodes the cease
transmission command/request and stops transmitting
Floor pre-emption The floor pre-emption type applies to voice transmissions using the
message trunking mode of operation only. In this mode, the same call stays
allocated to a traffic channel resource for a given duration which allows
parties to transmit voice in sequences; those are commonly called ‘overs’.
Resource pre- This type of pre-emption clears an active call to free an occupied radio
emption resource where another call with higher importance has to be made.
Tait TN9300 DMR Tier 3 Trunked System Manual Network Features and Interfaces 101
© Tait International Limited October 2022
The following table outlines scenarios where the Transmit Interrupt feature
is required:
User floor pre- Radio user wants to interrupt In an on-going call, a radio
emption of an the current transmitting radio user with pre-emption
on-going voice and take the floor to talk privilege can interrupt an
call interruptible radio user and
talk to all talkgroup members,
or in an individual call, to the
other user
All Call radio An ‘All Call’ broadcast must Node only feature. The
resource / floor stop everyone talking so that network will use transmit
pre-emption for everyone can hear the interrupt to stop the
voice calls announcement transmitting parties and
eventually free up required
radio resources.
102 Network Features and Interfaces Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
Use case Use case description Notes
Refer to Section 6.20 Adding SIP Lines to Outgoing Group Calls for
configuration instructions.
This section describes how All Ident calls work in Tait TN9300 DMR
trunked networks.
There are three types of All Ident call defined in the DMR standards:
■ Local All Ident calls - ALLMSIDL (0xFFFFD)
■ System wide All Ident calls - ALLMSID (0xFFFFF)
■ Subset of system wide All Ident calls - ALLMSIDZ (0xFFFFE)
Local All Ident Calls A local All Ident call is defined as one that is broadcast to all of the radios
- ALLMSIDL registered at the same site as the calling party. The following table
(0xFFFFD)
describes how they are handled in Tait DMR trunked networks.
Tait TN9300 DMR Tier 3 Trunked System Manual Network Features and Interfaces 103
© Tait International Limited October 2022
Note that:
■ The dialed string is only supported by radios using the DMR numbering
scheme
■ In the call records, the called party is correctly identified as ALLMSIDL
■ All local All Ident calls are broadcast calls, and have the correct priority
flags
System Wide All A system wide All Ident call is defined as one that is broadcast to all of the
Calls - ALLMSID radios registered at every site in the network. The following table describes
(0xFFFFF)
how they are handled in Tait DMR trunked networks.
High Priority All Ident Call *1981# Yes - but as local All Ident call
Emergency All Ident Call *1982# Yes - but as local All Ident call
Emergency Data All Ident Call *1984# Yes - but as local All Ident call
Normal All Ident Call *1987# Yes - but as local All Ident call
Note that:
■ The dialed string is supported by radios using any numbering scheme
■ In the call records, the called party is correctly identified as ALLMSID,
however the calls are set up as local All Ident calls (single site only)
■ All local All Ident calls are broadcast calls, and have the correct priority
flags
Subset of System This subset of system wide All Ident calls is defined as calls that are
All Calls - broadcast to all of the radios registered at every site in the network. The
ALLMSIDZ
(0xFFFFE) following table describes how they are handled in Tait DMR trunked
networks.
High Priority All Ident Call *1971# Yes - but as local All Ident call
Emergency All Ident Call *1972# Yes - but as local All Ident call
Emergency Data All Ident Call *1974# Yes - but as local All Ident call
Normal All Ident Call *1977# Yes - but as local All Ident call
104 Network Features and Interfaces Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
Note that:
■ The dialed string is only supported by radios using the DMR numbering
scheme
■ In the call records, the called party is correctly identified as
ALLMSIDZ, however the calls are set up as local All Ident calls (single
site only)
■ All local All Ident calls are broadcast calls, and have the correct priority
flags
Fast polling combines the USBD polling service and TSCCAS features of
the DMR Standard to provide a dedicated logical channel for location
services.
Tait TN9300 DMR Tier 3 Trunked System Manual Network Features and Interfaces 105
© Tait International Limited October 2022
second for USBD on the control channel, if it is not busy, and up to 2 polls
per second when using UDTs on the control channel).
Sites supporting
USBD over TSCCAS
avl
AVL Client
4 location polls per second
Sites supporting
USBD over CC
The DMR Standard provides for additional service types over the USBD
polling service, which will be added in future releases. However, the only
service type supported presently is LIP for location polling.
106 Network Features and Interfaces Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
Refer to Section 5.17 Configuring an Alternate Channel for instructions on
configuring an alternate channel for USBD polling.
3. The time the radios take to leave the current control channel and hunt
for and register on the new control channel when there is a
switchover.
Tait TN9300 DMR Tier 3 Trunked System Manual Network Features and Interfaces 107
© Tait International Limited October 2022
Shared channel operation has two levels of interference detection. With
level 1 monitoring, the base station monitors its own uplink for
interference, and in level 2 monitoring, a separate monitor receiver is used
as well, to monitor the downlink frequency for interference.
Points to note:
■ A mobile radio or a reciter can be used as a monitor receiver. The
monitor receiver must be sufficiently well isolated from the base
station’s transmissions that its receiver is not damaged. Ensure that the
RF site design ensures sufficient RF isolation between the base station
output and monitor receiver input.
■ Control channels operate continuously, so do not support shared
channel operation.
■ Channel groups do support this feature. The channel group manager
aggregates the interference information for the call manager, which
makes the appropriate call allocation decisions.
For full feature configuration details, refer to the relevant base station
documentation and help files.
3.2 Interfaces
The Tait DMR trunked network supports a number of interface types for
connecting a variety of equipment such as dispatch consoles, telephone
exchanges and other radio networks.
Note that the TN8271 network gateway has reached end-of-life, and
whilst currently supported, is no longer available. The TN9271 analog
gateway and G.711 connector application replace TN8271 network
gateway functionality.
108 Network Features and Interfaces Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
Up to four TN9271 analog gateway modules can be housed in a 4U
subrack, together with a PMU.
The TN9271 analog gateway converts the analog 4-wire audio to RTP VoIP
and vice versa. The RTP VoIP is used by TaitNet MPT-IP and DMR
networks. The TN9271 analog gateway is compatible with either type of
network without needing any special configuration (such as firmware
changes).
The following diagram illustrates the various connection options that are
available in a DMR network using the TN9271 analog gateway and/or the
G.711 connector. Note that AMBE is vocoded digital audio in the same
format as the DMR network's air interface, G.711 is un-vocoded PCM
(pulse code modulation) digital audio, and the balanced audio signal is
analog. The TN9271 analog gateway provides the electrical interface and
the G.711 connector provides the vocoder.
Analog balanced
AMBE console Other networks audio equipment
Digital AMBE
connected
equipment
Analog base station or
Balanced audio donor radio
AMBE
G.711
connector*
AMBE G.711
G.711
Voice recorder
Digital G.711
connected
* G.711 connectors can
equipment be located on TN9300 or
Other networks Voice recorder FxO/FxS
Digital console SIP phone TN9500 servers
Tait TN9300 DMR Tier 3 Trunked System Manual Network Features and Interfaces 109
© Tait International Limited October 2022
3.2.2 Dispatch Equipment
Each Tait CMD has an audio connection and a control connection to the
control node of the trunked network. If the Tait CMDs are remotely
located, they must be connected to the node via routers. Tait CMDs can also
be used as a dispatch solution in systems where different trunked networks
are connected together via the TN9500 Inter-Network Gateway.
110 Network Features and Interfaces Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
Tait has also partnered with Avtec, Omnitronics and Zetron to offer digital
dispatch consoles that can be interfaced to Tait TN9300 networks.
The Tait DMR network can support direct communications between radios
and external telephones through the PSTN. It also supports
communications between radios and private telephone extensions through
a switchboard (PBX), without dispatcher assistance (although dispatch
equipment can also automatically or manually patch telephone calls
through to radios and vice versa.)
Note that in telephone calls (from groups or individuals) the phone user
does not receive any audio indication that their call has been connected.
In addition, once the call has connected, if VOX detection has been
enabled, failing to speak will cause the call to timeout (due to the lack
of VOX detection).
Interfacing with SIP The Tait DMR network can interface directly to a SIP-enabled PABX via
phones an IP connection. The control path goes directly to the node but the voice
path goes through a network gateway or G.711 connector for transcoding.
A network gateway or G.711 connector is required for each PABX voice
path for translating between the DMR AMBE+2 and PABX G.711 voice
streams.
eg PABX/PSTN
PBX
interfaces to telephony
equipment SIP device
SIP over IP
Network Gateway(s)
SIP over IP
IP switch
Node(s)
Private IP Network
Other third party SIP endpoint devices can be connected to the DMR
network, allowing radios to make or receive calls to/from these devices.
The ETC CS-74 (SIP device), shown in the diagram, is a cost-effective
SIP-based console that can support up to four concurrent group calls at a
time.
Tait TN9300 DMR Tier 3 Trunked System Manual Network Features and Interfaces 111
© Tait International Limited October 2022
Network Gateway Telephone networks provide continuous audio signal, so a VOX (voice
VOX operated switch) is used to detect the presence of speech and create the
individual voice streams required by the radio network.
With a G.711 connector and TN9271 analog gateway, both have a VOX:
■ For a digital telephone network connection, use the VOX that is in the
G.711 connector
■ For an analog network connection, use the VOX that is in the TN9271
The recommended setting for the audio threshold is 10 dB above the audio
input line level when no speech is present. If low level line noise breaks
through the VOX, increase this value.
The holdoff (buffer length) is the duration in milliseconds that the input
audio must be continuously above the audio threshold in order to trigger the
VOX. Its purpose is to suppress short transient signals (clicks & pops).
The holdoff value adds to the overall input audio delay. If clicks and pops
break through the VOX, increase this value.
112 Network Features and Interfaces Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
■ Group calls from a telephone line to a group on the LMR side. If voice
detection is disabled on all the components in the phone audio path, a
phone user can make a group call that will be heard by all the radios
affiliated to this group, as well as affiliated consoles. But if a radio or
console replies to the call, only the party on the telephone line will hear
the response. The other participants will still stay on the traffic channel
but will only hear audio from the telephone side of the call.
Interfacing with If an interface to a SIP enabled PABX is not available, then the telephone
non-SIP phones interconnect requires one or more third-party telephony gateways to
interface the PBX or telephone exchange to the DMR network.
The telephony gateway converts the IP voice traffic from the node to the
signaling format required by the PBX/PSTN and vice versa. SIP is used for
setting up and clearing down calls.
The telephone user dials the number of a SIP line and then overdials the
number of an individual radio or group. The node receives the over-dialed
string and uses the rules in its in-phone table to find a match, replaces the
dialed digits with a number supplied by the in-phone table. It then sets up
the DMR call to the resulting number of the radio or group.
In the reverse direction, the radio user dials a string of numbers. When the
node receives the string, it uses the rules in its out-phone table to find a
match and replace the string with a telephone number. It then sets up the
call to that telephone number, routing it to a suitable FXO group. Out-
phone tables can be used to limit user access to the PSTN, for example
preventing long-distance calls.
eg PABX/PSTN
PBX
interfaces to
telephony equipment
Network Gateway(s)
Telephony Gateway
IP switch
Node(s)
Tait TN9300 DMR Tier 3 Trunked System Manual Network Features and Interfaces 113
© Tait International Limited October 2022
tions, since the protocols used between the node and network gateway
specify IP address destinations. NAT-aware routers that can understand
SIP will not understand Tait internal protocols.
1. The use of Tait’s Voice Recorder Protocol (VRP). Tait developed the
VRP protocol specifically for voice recording. The voice recorder
requires a Tait proprietary VRP interface and the ability to decode
AMBE streams.
Tait has partnered with Eventide to offer media recorders that can be
interfaced to Tait TN9300 DMR networks to provide the ability to
record voice calls and metadata such as the PTT ID and group ID.
These media recorders can be connected to the Tait DMR node for
recording all calls. Recordings are made in a digital format using
native DMR audio.
To configure voice recording on the TN9300, select Settings > Net-
work Parameters and enter the IP addresses of the voice recorders
(up to 2). The port numbers are fixed. Contact Tait for more informa-
tion about the ports.
For more information, refer to Technical Note TN-2623 How to con-
figure the Eventide NexLog Recorder.
RF infrastructure
Video Recorder
Client Node
Digital Voice
Recorder
LAN or WAN
114 Network Features and Interfaces Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
choice (contact your console provider for information on possible
external interfaces).
For configuration information, refer to “AIS Connections” on
page 171 or “DIP Connections” on page 171.
DMR RF infrastructure
AIS/ Analog
DIP line or
line other
TN9300 Optional
Voice
TN8271
Recorder
(required per Dispatcher
call for DIP)
DMR RF infrastructure
Analog
Conventional line 4-wire
line E&M
TN9300 TN8271
Voice
Recorder
Voice recorders are also available from Exacom and Total Recall.
Tait TN9300 DMR Tier 3 Trunked System Manual Network Features and Interfaces 115
© Tait International Limited October 2022
3.2.5 Location Information
interfaces to analog
equipment
4-wire E&M
TN9271
analog
gateway
IP switch
Base stations
Site Equipment
Node(s) with G.711
connector(s)
Private IP Network
When a DMR radio initiates a group call, the node includes the network
gateway in the call if the group includes analog FM radios The network
116 Network Features and Interfaces Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
gateway passes voice to the analog FM base station over its 4-wire E & M
interface. When an analog FM radio transmits, the analog FM base station
provides audio and signaling to the network gateway. The gateway passes
this to the node, which sets up a group call to the group to which the
network gateway belongs. The mapping between the analog FM channel
and the DMR trunked talkgroup is fixed in the network gateway
configuration.
Other TaitNet MPT, MPT-IP and DMR networks can establish an inter-
network connection to the Tait DMR trunked network through a TN9500
Inter-network Gateway.
6. Note that there are some SDM size restrictions. Refer to TN9500 Features
in the Migrating TaitNet MPT Networks using the TN9500 System Man-
ual (MNB-00009-xx).
Tait TN9300 DMR Tier 3 Trunked System Manual Network Features and Interfaces 117
© Tait International Limited October 2022
■ Legacy analog base stations (via a TN9271 analog gateway or TN8271
network gateway)
The TN8271 G.711 codec supports both μ-law and a-law. TN9271 ana-
log gateways currently support μ-law.
118 Network Features and Interfaces Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
AMBE/AIS-capable This connectivity type consists of an AIS connection from the node. It uses
console systems SIP-based and DMRA recognized protocols. This is a scalable solution
(where SIP trunking is supported), and the consoles support the AIS
protocol and AMBE codec.
TM93xx
Third party equipment
Site
TB9300 Dispatch
AIS console console
system
SIP/RTP or
proprietary
VDP (AMBE) BSP RTP (AMBE) AIS
Node
TN9300
Tait equipment
G.711/AIS-capable This connectivity type consists of an AIS connection from the node. It uses
console systems SIP-based and DMRA recognized protocols. This is a scalable solution
(where SIP trunking is supported), and the consoles support the AIS
protocol and G.711 codec. The G.711 connector is used for transcoding.
TM93xx
SIP/RTP or
proprietary
Tait equipment
Tait TN9300 DMR Tier 3 Trunked System Manual Network Features and Interfaces 119
© Tait International Limited October 2022
SIP-capable phone This connectivity type appears to be a SIP line (but it uses the G.711
systems connector for transcoding).
TM93xx
Phone
(VOIP)
Legacy analog This connectivity type uses a Conventional connection (but it uses the
consoles G.711 connector and TN8271 analog gateway for transcoding, and analog
inputs and outputs).
TM93xx
E&M Proprietary
Tait equipment
120 Network Features and Interfaces Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
Non-SIP legacy This connectivity type uses a SIP line (but it uses the G.711 connector for
phone systems transcoding).
TM93xx
Node
TN9300 Telephony gateway
Cisco 2911 w/FXO
SIP
4-wire E&M
Tait equipment audio
FXS
PBX
PABX/PSTN
(analog) Phone
Legacy base This connection type uses a Conventional connection (but it uses the G.711
stations connector and TN8271 analog gateway for transcoding and analog inputs
and outputs).
TM93xx
Node
TN9300
G.711
Analog equipment
(e.g. base station)
4-wire audio*
E&M
TN9271 analog gateway *1 per talk path
Tait TN9300 DMR Tier 3 Trunked System Manual Network Features and Interfaces 121
© Tait International Limited October 2022
3.2.9 Console Connectivity Protocol Comparisons
MAP27, AIS and DIP are protocols used by some Tait core networks for
console connectivity:
■ AIS (DMR Application Interface Specification) is a specification
created by the DMR association
■ DIP (Dispatcher Interface Protocol) is a Tait protocol documented in the
Dispatcher Interface Protocol Manual (MNA-00014-xx)
■ RAP (Radio Access Protocol) is part of MAP27, an MPT protocol. Tait
MAP27 includes Tait enhancements and modifications to the protocol
as described in the T1411 MAP27 Gateway User’s Manual (MNA-
00017-xx).
122 Network Features and Interfaces Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
Feature DIP AIS RAP
Non prescribed data calls Not available Not available Not defined
The MPT Gateway provides the means to interconnect the DMR network
to external MPT 1327 networks, such as TaitNet MPT, TaitNet MPT-IP or
Nokia ActioNet™.
It operates at the MPT 1327 air interface level. Conceptually the gateway
appears to be a population of radios to the external MPT 1327 network. The
gateway simulates MPT 1327 signaling, so that the external network thinks
it is talking directly to a radio. To the external network it looks like all the
radios in the DMR network are registered on the external system’s site that
the gateway is connected to.
Tait TN9300 DMR Tier 3 Trunked System Manual Network Features and Interfaces 123
© Tait International Limited October 2022
The following diagram shows the gateway interconnections:
Gateway Site
Ethernet switch
Network Network
Serial port server
gateway gateway
Intersite RS232
Intersite
GSM audio
site
bus
GCC GCC
Key
AGI AGI
GSM Gateway Site Module
LIC LIC
AGI Actionet Gateway Interface
Control Traffic
Tx/Rx Tx/Rx LIC Line Interface Card
For other system types, the Gateway Channel Controller can be connected
to the external channel using normal RF equipment or by directly
connecting the 4-wire audio.
Basic Registration When a radio registers on the DMR network, the gateway will forward this
and Individual Call registration request to the external network. This informs the external
Setup
network that calls to this radio should be routed to the gateway site.
124 Network Features and Interfaces Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
If a radio on the external network places an individual call request to this
radio and the radio is registered at a site on the DMR network then the call
will be routed to the gateway site, and then onto the site where the radio is
registered. If the radio roams back to the external network, the DMR
network receives no notification. If a radio on the external network places
an individual call request to this radio, the individual call request is
processed by the external network as normal. If a radio on the external
network places a call request to a radio on the DMR network, the DMR
node controller will explicitly register the external network radio.
However, in the situation where the individual call request to this radio is
made from a radio on the DMR network the following happens:
1. The network attempts to contact the called radio on the last site at
which it was registered.
2. If Step 1 fails, the network attempts to contact the called radio at any
site in the site zone.
3. The network attempts to contact the called radio at all sites on the
network including the gateway site.
Speech Call 1. When a group or individual call request is made to a party on the
Requests to the external network, an a RQS message for the call will be sent to the
External Network
external network’s control channel, and the call request will be
queued.
Speech Call 1. If the gateway receives an AHY from an interprefix party it should
Requests from the respond with an ACKX QUAL0.
External Network
Tait TN9300 DMR Tier 3 Trunked System Manual Network Features and Interfaces 125
© Tait International Limited October 2022
3. If the gateway receives a FOACSU AHY, it responds with an ACKI
QUAL0, and sends an $90 outgoing speech call setup request to the
node controller and initializes a new entry in the call table.
GTC Processing If the gateway receives a GTC from the control channel, it will allocate the
specified traffic channel to the call. If the traffic channel is already
allocated to an existing call and the called/calling parties do not match, then
the existing call will be terminated.
If a call does not already exist on the DMR network then a new call request
will be created. The gateway may be configured to generate hold tones on
the traffic channel to inform the external network that the call is not fully
allocated. If this is a group call, then the call maybe amalgamated into an
existing call.
If a call exists on the DMR network that matches the called and calling
parties in the GTC, and the existing call is queued waiting for the gateway,
the existing call will proceed.
Restricting Groups By default, group calls created on the DMR network are not routed via the
Forwarded via MPT MPT gateway to the external network unless they have been explicitly
Gateway
allowed. To do this, define the groups in the configuration file 7 on each of
the node controllers. Add an agw8.groups line to the file with the
following format:
Only group addresses in this list will be forward through to the MPT
gateway. Addresses can be entered in the current numbering scheme
format, as you would enter numbers in the user interface. Groups should be
separated by a space. Enter taitnet reload-cfg or restart the node to
force the node to reload this file.
If this configuration parameter is all, then all group calls on the network
will be routed to the external network. To do this, set the agw.groups
entry to the following:
agw.groups: all
7. Refer to Section 6.23 Node Resource File for node controller configura-
tion file name and directory path.
8. Note that agw refers to the MPT Gateway (historically called the ActioNet
Gateway).
126 Network Features and Interfaces Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
Diversion The network has the following behavior for diversions:
Messages that are longer than the maximum supported in DMR (see
table) will be rejected.
Binary 46 bytes
BCD 92 characters
Tait TN9300 DMR Tier 3 Trunked System Manual Network Features and Interfaces 127
© Tait International Limited October 2022
UDT format (appended data) Maximum SDM size in DMR
128 Network Features and Interfaces Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
4 Fleet Planning
Each fleet can have several options for different sets of call types (local
calls, telephone calls, data calls and so on) and different service areas (the
whole network, just the main city, just the country, and so on). Each fleet is
a named cluster of network numbers. Each radio assigned to the fleet is
programmed with a number from this cluster. Spare numbers are available
for future expansion.
The fleet can optionally have groups. Groups are also network numbers.
Radios that belong to a group join in a call made to that group number.
A radio has only one individual number but it can belong to many groups.
When you add a radio or a group to a fleet, you configure it so that you can
control the access that radio has to the network, or the way that a group call
is set up. Entering the configuration information for a radio or group is
known as validation.
The service area is part of a radio’s validation record. It is that part of the
network’s coverage area a radio is permitted to operate from. The coverage
area is the area where radios can receive signals from the network and the
network can receive signals from the radio. This is determined by the
number and location of sites in your network. The service area is a subset
of the network’s coverage area. Radios must be within their service area to
make or receive calls. This service area relates only to the location of the
radio, it does not limit the area that the radio can make calls to or receive
calls from. Service areas can be set up for individual radios and for groups
of radios.
Tait TN9300 DMR Tier 3 Trunked System Manual Fleet Planning 129
© Tait International Limited October 2022
4.2 Profiles and Service Areas
Profiles and service areas let you combine a set of call rights or a set of sites
under a meaningful name and apply them to a radio or group in a single
action.
While the trunked network has many features and configuration options,
the profiles and service areas are used to define the combination of network
features and configuration options that are actually required. For each
service option, you define a profile and/or service area to match.
This makes defining validation information for the radios and groups in a
fleet quicker and less error-prone. Profiles and service areas also make
maintaining validation information easier; you can change one profile or
service area and globally apply the changes to all radios or groups with that
profile or service area.
The network has three nodes; Node 1 is in the city, Node 2 is in the town,
and Node 3 is in a small town and serves a large rural area.
The network operator sets up the following profiles and service areas.
However, the network provider also establishes a policy that larger
customers are able to negotiate their own variations, should their needs not
be covered by the standard service options.
130 Fleet Planning Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
4.2.1 Service Areas
Bus companies in the city only need city coverage. Those in the town
probably only need town coverage. Transport organizations use the
interstate highway, the town and the city. Emergency services require full
coverage.
Newtown Site 11
All Sites 1 - 16
16
13
Country
12
14
15 11
Newtown
10
1
2
4
Metropolis
City
1
9 6 5
8
7
Key
1 Node 1 Site
Tait TN9300 DMR Tier 3 Trunked System Manual Fleet Planning 131
© Tait International Limited October 2022
4.2.2 Profiles
The provider wants to provide a basic set of call types, then to define
several options for additional types. It is decided to include status calls, call
diversion, and intersite individual calls in that basic set. The plan is to
include local group calls in the basic set, because they put little burden on
network resources, but the call rights do not distinguish between individual
and group calls. To make these distinctions, you need to configure the
validation information for each group number. Separate profiles are created
for PSTN calls only and for PSTN/PABX calls. The provider wants
flexibility in the pricing of connections to an organization’s PABX.
Basic Status calls, call diversion, intersite calls, group calls, short data
messages (single-segment transactions)
PABX As for the Basic call profile, plus PSTN and PABX calls
For example, when creating unit profiles, you may have need to have
separate profiles for:
■ TeamPTT smartphones
■ Basic mobile radios
■ Non-Tait radios
■ Dispatch consoles
■ Basic portable radios
■ PSTN supervisor portable radios
■ PABX manager portable radios
■ Special squad covert radios
When creating group profiles, you may have need to have separate profiles
for:
■ Dispatch consoles
■ Radios
■ Special groups
132 Fleet Planning Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
■ Special squad radios may need to be configured to use encryption, and
have the highest voice call access rights
For example:
■ A caller dials the radio number that it wishes to call.
■ The number is translated by the calling radio to an address and sent to
the node as a call request.
■ The called party is notified by the system of a call request from the
calling users address.
■ The called party radio translates the address into a number (which it
may be able to display depending on the radio model).
The number that a radio is assigned depends on the numbering scheme that
is in use. DMR supports the following schemes:
■ MPT 1327
■ MPT 1343
■ ANN
■ DMR standard
■ DMR native
Tait TN9300 DMR Tier 3 Trunked System Manual Fleet Planning 133
© Tait International Limited October 2022
Fleets with different numbering schemes can often not communicate
with each other (MPT1327 and MPT1343 can, but not with DMR).
Voice recorder connectivity will also be affected in this scenario. This
set up is recommended only for LMR service providers to independent
companies/customers where no communication is required between
customers, and each customer has their own independent console.
or
■ ppp / ffff / uuu (large fleet)
or
■ ppp / FFFF / ggg (large fleet)
where:
For systems using MPT 1343 numbering, group fleet numbers are always
5000 and above (which when translated to MPT 1327 equates to idents
above 6000).
134 Fleet Planning Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
■ If making an interprefix call:
needs to dial the full 9 or 10-digit number: pppffffuu or pppffffuuu
or pppFFFFgg or pppFFFFggg
Advantages ■ Easy for the system to determine if a call is to a group or individual radio
■ Can make fleets of any size and fit in to the address map where you like,
making a more compact map that can be easily added to
■ Radios can be programmed to belong to groups outside their own fleet
(i.e. to groups containing radios belonging to more than one fleet)
Disadvantages ■ Impossible for radios to display who the called party is if interfleet or
interprefix calls are made
■ Long dial numbers for interfleet or interprefix calls
■ Easy to program radios incorrectly (e.g. groups)
■ MPT 1343 requires knowledge of the size and base ident of all the fleets
in the prefix
The addresses in each prefix in the ANN numbering scheme are divided up
into a number of fleets with predefined sizes.
Fleet size Fleet size is restricted to one of three options. Within each fleet there is a
range of radio and group addresses. This is outlined below:
Small 70 10 20 to 89 90 to 99
Mini 22 4 20 to 41 90 to 93
The FPP and MEP In each prefix, there are 8100 individual addresses. The first 8000 of these
parameters are divided into ten blocks numbered from 1 to 10. Each block contains 800
addresses and can accommodate one of the following:
■ A single large fleet
■ Ten small fleets
■ Thirty mini fleets
The number of each type of fleet, that can be allocated within a prefix, is
governed by two parameters:
■ Fleet Partitioning Parameter (FPP)
■ Miniaturization Extent Parameter (MEP)
Tait TN9300 DMR Tier 3 Trunked System Manual Fleet Planning 135
© Tait International Limited October 2022
FPP and MEP can have values in the range 0 to 10 and the sum of the two
values must also lie within this range. For each set of values the following
applies:
■ Blocks 1 to FPP are made up of large fleets
■ Blocks (11 - MEP) to 10 are made up of mini sized fleets
■ All other blocks are used for small fleets
■ The number of large fleets = FPP
■ The number of small fleets = (10 - (FPP + MEP)) x 10
■ The number of mini fleets = MEP x 30
Figure 4.1 illustrates how the address space in a prefix is divided up when
FPP = 2 and MEP = 3
ANN dialled string The following table shows the full ANN dial string required to call a radio:
Prefix The prefix is identical to that used in the MPT 1327 standard (0 to 127).
It is possible to restrict the number of prefixes available in your system by
selecting an appropriate numbering model. The smaller the numbering
model, the fewer digits used by the prefix in an ANN number.
136 Fleet Planning Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
Numbering model Prefixes used Length of prefix
Mini 0 0 digits
Small 0 to 9 1 digits
Large 0 to 99 2 digits
Fleet number Fleet numbers are made up of two components, The first is referred to as L
and the second as R/rr.
■ L
For large and small fleets L is always 7. For mini fleets L can have the
value 7, 8 or 9.
■ R/rr
For large fleets the fleet number is referred to as R and is a single-digit
in the range 0 to 9.
For small and mini fleets the fleet number is referred to as rr and is a
two-digit number in the range 00 to 99.
When referring to fleets in general, R/rr is often used.
ANN Numbers ANN numbers are made up from L, the prefix, R/rr and the radio or group
number. L is displayed as a single digit. The prefix is displayed with
between 0 and 3 digits according to the numbering model used. For large
fleets R is displayed as a single digit and for small and mini fleets rr is
displayed as two digits. For large fleets the radio or group number is
displayed as 3 digits and for small and mini fleets with 2 digits.
For example the ANN number 7013200 has L = 7, prefix = 01, R = 3 and radio
number = 200.
Assigning L to a To explain how L is assigned we must examine how idents are organized.
fleet Within each block of 800, the idents are arranged between radios and
groups as follows:
A Large Fleet
0 to 699 Radios
The block is divided up into ten smaller blocks of 80 idents each. Each of
these sub-blocks can hold either one small fleet or three mini fleets. For a
small fleet the sub block is divided as follows.
0 to 69 Radios
70 to 79 Groups
Tait TN9300 DMR Tier 3 Trunked System Manual Fleet Planning 137
© Tait International Limited October 2022
For mini fleets the sub block is divided as follows.
66 to 67 Not used
All the mini fleets within a sub-block have the same value of rr but different
values of L.
For the first mini fleet in the block, L = 7. For the second, L = 8 and for the
third L = 9.
Assigning R/rr to a For large fleets R can take values in the range 0 to (FPP - 1).
fleet
For small fleets rr can take values in the range (FPP x 10) to (99 - (MEP x
10))
For mini fleets rr can take values in the range (100 - (MEP x 10)) to 99.
The following table shows valid values for R and rr for different values of
FPP and MEP:
138 Fleet Planning Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
FPP 0 1 2 3 4 5 6 7 8 9 10
R N/A 0 0..1 0.2 0..3 0..4 0..5 0..6 0..7 0..8 0..9
MEP
rr small 00..99 10..99 20..99 30..99 40..99 50..99 60..99 70..99 80..99 90..99 N/A
0
rr mini N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A
rr small 00..89 10..89 20..89 30..89 40..89 50..89 60..89 70..89 80..89 N/A N/A
1
rr mini 90..99 90..99 90..99 90..99 90..99 90..99 90..99 90..99 90..99 90..99 N/A
rr small 00..79 10..79 20..79 30..79 40..79 50..79 60..79 70..79 N/A N/A N/A
2
rr mini 80..99 80..99 80..99 80..99 80..99 80..99 80..99 80..99 80..99 N/A N/A
rr small 00..69 10..69 20..69 30..69 40..69 50..69 60..69 N/A N/A N/A N/A
3
rr mini 70..99 70..99 70..99 70..99 70..99 70..99 70..99 70..99 N/A N/A N/A
rr small 00..59 10..59 20..59 30..59 40..59 50..59 N/A N/A N/A N/A N/A
4
rr mini 60..99 60..99 60..99 60..99 60..99 60..99 60..99 N/A N/A N/A N/A
rr small 00..49 10..49 20..49 30..49 40..49 N/A N/A N/A N/A N/A N/A
5
rr mini 50..99 50..99 50..99 50..99 50..99 50..99 N/A N/A N/A N/A N/A
rr small 00..39 10..39 20..39 30..39 N/A N/A N/A N/A N/A N/A N/A
6
rr mini 40..99 40..99 40..99 40..99 40..99 N/A N/A N/A N/A N/A N/A
rr small 00..29 10..29 20..29 N/A N/A N/A N/A N/A N/A N/A N/A
7
rr mini 30..99 30..99 30..99 30..99 N/A N/A N/A N/A N/A N/A N/A
rr small 00..19 10..19 N/A N/A N/A N/A N/A N/A N/A N/A N/A
8
rr mini 20..99 20..99 20..99 N/A N/A N/A N/A N/A N/A N/A N/A
rr small 00..09 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A
9
rr mini 10..99 10..99 N/A N/A N/A N/A N/A N/A N/A N/A N/A
rr small N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A
10
rr mini 0..99 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A
Cells in the table that are shaded light grey represent combinations of FPP
and MEP which allow no fleets of the specified size.
Cells in the table that are shaded grey represent invalid combinations of
FPP and MEP.
Tait TN9300 DMR Tier 3 Trunked System Manual Fleet Planning 139
© Tait International Limited October 2022
requires knowledge of the size and base ident of all the fleets in the
prefix.
■ Radios can display the caller ID for interfleet and individual interprefix
calls
■ Interfleet dialing can be blocked if desired. The node/site only requires
the FPP/MEP parameters to work out if a call is an interfleet call.
The DMR standards based fleet numbering and dialing plan is defined in
Annex E of ETSI TS 102 361-4 V1.7.1 (Part 4: DMR trunking protocol)
for DMR Trunked (Tier 3) operation. This dial plan is backward
compatible with MPT 1327, MPT 1343 and ANN numbering schemes.
The length of an AI address is 24 bits. AI addresses are split into two parts.
The first 9 bits represent the Network Area Identity (NAI), the next 15 bits
represent the Short Subscriber Identity (SSI) or Short Group Identity (SGI)
as illustrated below.
ppppppppp / iiiiiiiiiiiiiii
140 Fleet Planning Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
The air interface address allocation is displayed in the following table.
(511 assigned to a
special gateway)
The permissible range is 328 to 806 (479 values in total). The DMR MS NP
values between 200 and 327 are reserved.
FIN range Total fleets Description IN range Total units per fleet
Tait TN9300 DMR Tier 3 Trunked System Manual Fleet Planning 141
© Tait International Limited October 2022
This is illustrated as follows:
For calls within your own fleet, a shortened 3 digit MS is represented as:
IN (3 digits)
The length of SGI is 15 bits. SGI = 0 is reserved. The range of values from
1 to 17 000 represents a group identity.
3 -d ig it G r o u p N u m b e r (G N )
(ra n g e is 9 0 0 to 9 9 9 )
p p p / ff / g g g
142 Fleet Planning Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
4.3.4 DMR Native Numbering Scheme
Notice Fleet sizes are limited to 5999 units and 2100 groups as per
MPT1327 numbering.
If there is a mix of MPT and DMR fleets within a network, the MPT
special/system idents are not allowed to be used as normal unit or group
addresses by DMR fleets using native address numbering.
MPT 1327 groups and radios are each assigned a unique 20-bit number,
consisting of a Prefix (the first seven bits), and an Ident (the remaining
thirteen bits). Prefixes range from 0 to 127, and Idents range from 1 to
8191.
Tait TN9300 DMR Tier 3 Trunked System Manual Fleet Planning 143
© Tait International Limited October 2022
PP or PPP is the Prefix and has a valid range of 0-127. In the case where a
2 digit prefix is dialed the first P is assumed to be a 0. When no Prefix is
dialed, the default Prefix is used and this is specified as a configuration
parameter to the equipment.
IIII is the Ident and has a valid range of 1-8191. Individual Idents are in the
range 1-5999 and group Idents are in the range 6000-8100. Calls may also
originate from special Idents in the range 8101 – 8191 and the console
system should accept these.
The Prefix and Ident map to the DMR identity in the following way
Where:
■ sip identifies a URI address scheme that is specific to AIS
■ identity is the numeric decimal value of the MPT 1327
representation as described above
■ networkname is a domain name or IP address
■ :port is optional and specifies the port number to use for the AIS
protocol
MPT 1343 numbers are in the form of Fleet Prefix/Fleet Number/Unit Ident
(FP/FN/UI) for individual unit numbers, and Fleet Prefix/Fleet Number/
Group Ident (FP/FN/GI) for group numbers, where Fleet Prefix ranges
from 200 to 327, Fleet Number ranges from 2001 to 6050, and for
individual radios, the Unit Ident ranges from 20 to 89 for a small fleet, or
200 to 899 for a large fleet. Group Idents range from 90 to 99 for a small
fleet, or 900 to 998 for a large fleet.
On Tait networks group fleets have Fleet Numbers in the range 5000 to
6050 and individual fleets have Fleet Numbers in the range of 2001 to
4999.
Tait historically used this numbering system on most networks but it has
been superseded by the MPT 1327 numbering system.
144 Fleet Planning Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
Numbers are displayed or/and dialed as:
XX
XXX
FFFFXX
FFFFXXX
PPPFFFFXX
PPPFFFFXXX
PPP is the Fleet Prefix, FFFF is the Fleet Number and XX or XXX is the
Unit or Group Ident. MPT 1343 numbers convert to MPT 1327 numbers
and these in turn convert to DMR identities as defined in “MPT 1327” on
page 143.
An MPT 1343 number may be converted to MPT 1327 and then the DMR
identities using the following algorithm.
To convert an MPT 1327 number to MPT 1343, the system must be aware
of the fleets in use on the network and test to determine if the MPT 1327
number is within the fleet. For a network with the following fleets:
Tait TN9300 DMR Tier 3 Trunked System Manual Fleet Planning 145
© Tait International Limited October 2022
The start and end MPT 1327 numbers for each fleet can be calculated.
To convert the MPT 1327 number, find the associated fleet and its
parameters then use the following algorithm:
PPP = Fleet Prefix = MPT 1327 Prefix + 200
4.4.3 ANN
In order to convert ANN numbers to DMR raw numbers, you need first to
convert them to MPT 1327, and then convert them from MPT 1327 to
DMR raw numbers as explained in Section 4.4.1 MPT 1327.
146 Fleet Planning Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
(ID for a unit) is ID=(L * 22) + (rr * 80) + unit number – 172
■ If the ANN address is member of a mini fleet then the MPT 1327 ident
(ID for a group) is ID=(L * 4) + (rr * 80) + group number – 48
Individual numbers All Number Prefixes have the same fleet structure. The relationship of NP,
FIN, IN and the raw DMR address is as follows:
■ For dialed digits 20 to 41
AI MS address = (NP - 328) × 8 00016 + (FIN - 20) × 700 + (IN - 200)
+ 100 00116
■ For dialed digits 42 to 89
AI MS address = (NP - 328) × 8 00016 + (FIN - 42) × 350 + (IN - 200)
+ 103C2916
Group numbers All Number Prefixes have the same fleet structure. The relationship of NP,
FGN, GN and the raw DMR address is as follows:
■ ID = (NP - 328) × 8 00016 + (FGN - 20) × 100 + (GN - 900) + 100 00116
Tait TN9300 DMR Tier 3 Trunked System Manual Fleet Planning 147
© Tait International Limited October 2022
4.5 Developing a Fleet Allocation Policy
Once you have decided on the numbering scheme(s) to use for each fleet,
you will need to develop a policy for allocating fleets, units and groups.
This process is important as it will be very difficult to change once your
system is up and running. For example, you should consider:
■ How many fleets are you likely to need in the long term?
■ What size fleets will be required?
■ Will your network be set up for partitions? If so, will the partition
classes be based on prefix? If the answer to both these questions is yes,
you will need to assign a group of prefixes to those users who will gain
preferential access.
■ Does the coverage area divide up into self-contained areas? If so, you
may want to divide up prefixes and assign them to regional areas.
■ Do you wish to restrict interfleet calls?
■ Do you wish to allocate unit numbers that relate to work related
numbers. For example a transport company may wish to use radio
numbers that reflect bus route numbers.
148 Fleet Planning Tait TN9300 DMR Tier 3 Trunked System Manual
© Tait International Limited October 2022
5 Configuration
To configure a control node for the first time, follow the order in which
the following sections have been laid out. This is because some features
have to be created before others can be configured. For example unit/
group profiles and service areas need to be set up before you can start
adding your units and groups.
The first time after a node has been reset, the node will display a warn-
ing message about the encryption keys. You should accept the warning.
License files can only be generated by Tait and each node must have its
own unique license. If the node has been set up by Tait then an appropriate
license file will have been installed on the node.
3. If you are setting up a new node from scratch, a new license file will
be required.
To get a license file, Tait must be supplied with the host ID of the
node controller that the node will be installed on (see below), and a
list of the features required (see “Licensed Features” on page 152).
Once you have provided the host ID and required features to Tait, you will
be provided a license file called license.dat for the node.
If you are getting multiple licenses, you may combine the license files into
one file that can be installed on all the nodes. Because the license file is a
text file, you can easily combine the information, but each line must be the
full text from the original file. Each node will only use the line in the license
information that matches its host ID.
2. Click Upload, then click Choose file from the Upload license dialog
box.
4. Once the license file has uploaded, the node will check if the license
is valid.
TNAS300 DMR node Indicates that the node is enabled for DMR (one
license required per node)
TNAS302 High availability nodea Indicates that the node is enabled as a high
availability node (this license is required in addition to
the DMR node license), allowing this node to
synchronize its database to other nodes. It does not
stop a switching node from taking over control if the
control node fails.
One license required to be purchased per network, to
be installed on each node controller.
TNAS303 DIP calls Indicates the number of concurrent calls that can be
made using DIP connections
TNAS304 AIS calls Indicates the number of concurrent calls that can be
made using AIS connections.
In HA, this license is required for all potential control
nodes.
Multiple AIS licenses may be required when
connecting consoles or using Tait TeamPTT.
TNAS305 Data calls Indicates the number of concurrent packet data calls
that can be made
TNAS306 Voice recorder protocol Indicates that the use of voice recorders are allowed.
In HA, this license is required for all potential control
nodes.
TNAS309 Telco (SIP) calls Indicates the number of concurrent calls that can be
made using SIP lines.
A maximum of 8 licenses is recommended (as tested
on the Cisco 4331).
Also required for Network Operator calls, and for
phone calls that traverse the TN9500 Inter-network
Gateway.
TNAS312 Simulcast Allows for trunked DMR simulcast and voted groups.
Base stations in simulcast sites also require
TBAS306 and/or TBAS307 when this license is
installed.
TNAS313 AES encryption Indicates if the use of AES encryption (if installed) is
allowed
TNAS320 DMR Express6 Indicates that the node will only allow a total of 6 sites
and 24 physical channels (48 logical channels). The
channels do not need to be evenly spread across the
sites. High availability is not available in DMR
Express6.
Base stations will require TBAS302 when this license
is installed.
TNAS321 DMR Express20 Indicates that the node will only allow a total of 20
sites and 80 physical channels (160 logical
channels). The channels do not need to be evenly
spread across the sites. High availability is available
in DMR Express20, in which case a second node is
required.
Base stations will require TBAS305 when this license
is installed.
a. Without the HA license you can have multiple nodes in a network, but no automatic or manual database syn-
chronization can be performed.
b. Without the encryption license the node will only stop encryption for external interfaces (DIP, AIS, SIP, etc.).
Encrypted calls between radios will not be affected.
TBAS300* DMR Trunking Full Allows a reciter to accept connections from any DMR
high tier or unlimited/full node/standalone node.
In single site trunking and fallback modes, this license
entitles a standalone node to control a single site of
up to 20 physical channels.
TBAS302* DMR Trunking Express6 Allows a reciter to accept connections from any DMR
Express6 node/standalone node or DMR Access
standalone node.
In single site trunking and fallback modes, this license
entitles a standalone node to control a single site of
up to 20 physical channels.
Base stations in an Express6 network will also work
with TBAS300 or TBAS303 licenses. However it is
recommended that all base stations at a site have the
same license. This is because, in fallback mode,
base stations with lower licensing levels will not work
correctly with base stations with a higher level
license.
TBAS303* DMR Trunking Access Limits a reciter to only accepting connections from a
DMR Access standalone node.
This license entitles a standalone node to control a
single site of up to four physical channels.
This license must be installed on all base stations at
the site.
TBAS305* DMR Trunking Express20 Allows a reciter to accept connections from any DMR
Express20, DMR Express6 node/standalone node or
DMR Access standalone node.
In single site trunking and fallback modes, this license
entitles a standalone node to control a single site of
up to 20 physical channels.
Base stations in an Express20 network will also work
with the TBAS300 license. However it is
recommended that all base stations at a site have the
same license. This is because, in fallback mode,
base stations with lower licensing levels will not work
correctly with base stations with a higher level
license.
G.711 Connector The G.711 connector is licensed for the following features:
a. The high availability feature is currently not supported, but will be re-
leased at a later date.
5. Once the reboot has been completed, the installed certificate will be
active.
Centralized This is configured in the administration application. Only the LDAP rules
Authentication can be updated in the DMR node controller.
Local users should not be created in the DMR control node web browser
if centralized authentication is used on your server.
Local Users Users are created in the Administration Application, but their access level
must be changed to enable access rights in the control node.
4. Click Save.
Local Users It is recommended that local users should not be created in the DMR
web browser if centralized authentication is used on your server.
2. Enter the required values or enable the required features for the node
you are currently logged on to from the General, Network
Connection, SNMP and NTP parameters. (Note that some
parameters, such as SNMP and NTP, are not required to be
configured here for version 3 and version 4 users.)
2. Enter the required values or enable the required features for your
network from the General, Compliance, Features, Timeouts,
Transmit Interrupt, Authentication Checks, Background Checks,
Signaling, Voice recording, DSCP and Control Channel Utilization
Thresholds parameters. Click Save when complete.
3. Enter the required information for each SIP group on your network
by entering each SIP group’s information, and clicking Save, before
clicking Add to create a new SIP group.
6. Enter the required values for your inphone table for the Identity and
Inphone Rules parameters.
7. Click Save to save this inphone table. Add more inphone tables as
required.
10. Enter the required values for your outphone table for the Identity and
Outphone Rules parameters.
14. Enter the required values for your local SIP line for the Identity,
Validation, Client, Network Gateways and Groups parameters.
15. Add group addresses and their outgoing destinations for the local
SIP line, if required.
16. Click Save to save this SIP line. Add more local SIP lines as
required.
20. Enter the same username and password as entered in the TN9500
gateway for this inter-network connection.
21. Select a SIP group from the drop-down list of groups that have been
defined, if required.
Encryption is an optional feature that requires a license. Note that the same
encryption ID and keys must also be programmed into the radio units for
encryption to work.
3. Select the encryption type. (Only some DMR release versions have
AES encryption types installed.)
4. Enter the required values for your encryption keys in the Identity and
Key sections.
3. Enter the required values or enable the required features for your unit
profiles from the Identity, Features, Location Polling, Transmit
Interrupt, Access Level, Minimum Access Level, Call Time Limits,
Call Inactivity Timeouts, Call Answer Timeouts, Registration
Timeout, Supplementary Data and Call Types parameters.
4. Click Save to save this unit profile. Add more unit profiles as
required.
7. Enter the required values for your unit service area parameters.
8. Click Save to save this unit service area. Add more unit service areas
as required.
11. Enter the required values or enable the required features for your
group profiles from the Identity, Minimum Access Level, Call Time
Limits, Call Inactivity Timeouts, Call Answer Timeouts, Emergency
Call, Features and Transmit Interrupt parameters.
For OTAP configurations, ensure that the group profile’s ‘Priority group
override’ feature is enabled.
It is the radio that actually decides that the voice takes precedence over
data, but, to get the group call grants (GTCs) onto active payload chan-
nels for the voice calls, you need to have the group priority override fea-
ture enabled, otherwise the node does not send the GTCs there for the
radio to make the decision.
12. Click Save to save this group profile. Add more group profiles as
required.
15. Enter the required values for your group service area parameters.
When external networks are connected to your network, the group ser-
vice area can be configured to allow for group calls to sites at both local
and external networks. Use the Service Area table for listing the local
sites, and the Service Network table for listing the external sites.
3. Enter the required values or enable the required features for your
partition classes from the Identity, Address Range (of the radio
units), Call Types and Access Level parameters.
4. Click Save to save this partition class. Add more partition classes as
required.
When adding a fleet with ANN numbering to the network, the FPP and
MEP for the fleet prefix must first be defined under Settings > ANN
Fleet Parameters.
10. If the fleet uses MPT 1327 numbering, follow these steps:
a. Enter the prefix.
b. Enter the number of units and the number of groups for allocation
to the fleet.
c. Click Find Space. The node calculates values for the Base unit
and Base group fields.
d. If required, you can manually edit the calculated values (these
will be checked when you click Save).
15. In the Identity area, enter the radio number. This must be a number
that lies within the number range assigned to the fleet. If you add
multiple radios, they will be numbered starting from this number.
16. Optionally add a comment to give more information about the radio.
17. If you want to add more than one unit, enter the number of units into
the Number of units to add box.
18. Enter the required values or enable the required features for your
radio unit(s) from the Validation, Diversion and Group Assignment
parameters.
22. In the Identity area, enter the group number. This must be a number
that lies within the number range assigned to the fleet. If you add
multiple groups, they will be numbered starting from this number.
23. Optionally add a comment to give more information about the group.
24. If you want to add more than one group, enter the number of groups
into the Number of groups to add box.
25. Enter the required values or enable the required features for your
group from the Validation and Diversion parameters.
6. Enter the required values or enable the required features for your site
from the Identity, Location, Features, Queuing, Framelength and
Pooled Sites parameters.
10. Enter the required values or enable the required features for your
channel from the Identity and Features parameters.
13. Select the Partition tab and click Edit, then Add.
14. Enter the address range and select the required partition class for
your partition.
18. Enter the required values or enable the required features for your site
from the Voting Parameters, Adjacent Sites and Adaptive Vote Now
parameters.
In a site with two control channels, you can configure them with the same
syscode or with complementary syscodes that have different PAR values
(A for one control channel, B for the other).
Options that can be selected for dual control channel operation are:
■ Dual - same syscode with identical PAR field (Partition Class A, B or
AB)
■ Dual - different PAR field (Partition Class A or B)
Using PAR values other than AB allows you to split your radio fleet,
forcing some radios to register on category A control channels, while other
radios register on category B control channels. Note: All radios can register
on AB control channels.
Whether the radio will use only logical channel A on control channels, only
logical channel B, or both (AB), requires the Control Category (PAR value)
to be programmed into the radio unit using the programming application
(Trunked > Network Settings > Network Identity form > DMR tab >
Control Category).
2. Click Edit and select a value from the drop down menu for Dual
control channels. Options are Single, Dual - same syscode, or Dual
- different PAR.
3. Use the Calculate button to assist setting the site syscode and PAR.
If Dual - different PAR is chosen, use of the Calculate feature is
mandatory as the syscode field is disabled.
5. Edit the channels to enable the dual control feature by selecting the
check box for the ‘Allow control’ parameter in the Features area.
6. Click Save.
Radio Units Radios must be programmed with the control channel to use. For maximum
benefits, ensure that the radios are distributed evenly between the control
channels.
Configuring the 1. Enable the Transmission Trunking mode option under each desired
node group profile (Subscribers > Group Profiles > Features >
Transmission trunking for broadcast calls).
3. Enable the Allow adaptive GTCs parameter in both Unit Profiles and
Group Profiles. This is to ensure that the radio units are included in
the group call as soon as possible.
4. Click Save.
2. Click Save.
4. Click Save.
6. Click Save.
The transmit interrupt feature is configurable only when the DMR spec-
ification parameter in Settings > Network Parameters > Compliance is
set to version 1.8.1 or later.
Configuring sites The traffic channel allocation at a site has an impact on the speed that a
transmit interrupt can be sent on the ‘Embedded Outbound Reverse
Channel’ (RC). If the reverse channel is on:
■ A control channel, the interrupt is sent whenever possible
■ A traffic channel with no audio, the interrupt is sent in the next 60ms
■ A traffic channel with audio, the interrupt is sent in the next 720ms
1. On the node controller webUI, select Network > Sites, click the
name of a site, and then click the Configuration tab.
Traffic 1 Traffic 1
Traffic 2 Traffic 2
Traffic 3 Traffic 3
Traffic 4 Traffic 4
Traffic 5 Traffic 5
Traffic 6 Traffic 6
Traffic 7 Traffic 7
Disabled Enabled
Configuring To allow control over the transmit interrupt operation or limit the amount
network parameters of attempted transmit interrupt signaling sent on air, the following
parameters can be configured on the node controller webUI:
Notice For the three Stop PTT parameters above (c to e), if the talker
is not interested in the call, the talker audio will be stopped early.
RC impact on late A radio joining late into an encrypted call will experience additional late
entry performance entry delays if the adjacent slot to it is bearing an encrypted voice call.
on encrypted call
Configuring radios 1. Select Trunked > Radio Calls > Call Options form > DMR tab and
configure the following as required:
3. Operational control:
a. PTT Press Initiates Tx Interrupt - Interrupt other radios whenever
the PTT is pressed
b. Tx Interrupt Timer - How long to wait for a response from the
system, after initiating a Tx interrupt request
1. On the DMR web browser, select Interfaces > AIS Connections and
then click Add.
1. On the DMR web browser, select Interfaces > DIP Connections and
click Add.
Notice The ‘Invite without SDP’ feature in the Client area is only
available on the inter-network connection that is supported by the reli-
able provisional scheme in the invite session (RFC6337#section-3.1.2).
This option can be used to synchronize inter-network calls over the
inter-network gateway connections. If this option is not used, the call
times for an inter-network voice call may differ between the inbound
and outbound networks. This option is supported on version 1.12 or
later of the TN9500 Inter-Network Gateway.
Each DMR ID used for the TeamPTT username also has to be config-
ured as a unit in Subscribers > Fleet > Units.
6. Click Save.
Changing the port The local port number on the node that is used for the TeamPTT service is
number set, by default, to 5062.
2. Once the node has restarted, delete the original TeamPTT connection
and add a new one.
5.14.6 IP Data
1. On the DMR web browser, select Interfaces > IP Data and then click
Edit.
2. Click Edit, then Add to enter the port server information for the
network gateway that is the interface to the MPT gateway.
Configuration 1. On the DMR web browser, select Settings > Authentication and click
procedure for LDAP Edit.
3. In the LDAP Server area enter the values for your network (as listed
above).
4. In the LDAP Rules area, click Add and create at least one rule.
The table of rules is used to determine the access level of a user. Each
rule is checked in order until a match is found. At least one LDAP
rule must be defined if LDAP is selected as the authentication proto-
col. The LDAP rules associate local access levels to remote LDAP
groups and/or user attributes.
5. Repeat for the next rule you want to define. You can define up to 10
rules. To add a rule to the bottom of the table click Add. Rules should
be added in order of Access level, with the highest first in the table.
The order is important because each rule is checked in order until a
match is found, so to add a rule in the middle of the table, select the
line above which you want the new rule to appear and click Insert.
Search Access
Id Group DN (example)
Filter Level
1 cn=Node_Administrator,ou=groups, Administrator
o=support_services,o=client,
dc=taitradio
2 cn=Node_Network_Administrator, Network
ou=groups,o=support_services, administrator
o=client,dc=taitradio
3 cn=Node_Fleet_Administrator, Fleet
ou=groups,o=support_services, administrator
o=client,dc=taitradio
4 Read only
In this example:
■ Users belonging to Node_Administrator LDAP group will have
Administrator access level
■ Users belonging to Node_Network_Administrator LDAP group
will have Network administrator access level
■ Users belonging to Node_Fleet_Administrator LDAP group will
have Fleet administrator access level
■ All other users under the LDAP search base (specified above)
will get Read only access level (it is recommended that this rule
is always included at the end of the rules table)
Optionally, additional Search Filters can be enabled for each access
level. This will add a test against a user attribute.
For example, if department=LMR_Operation was added to the
Search Filter column in row 4 (above) of the table, then only users
with an attribute department with a value set to LMR_Operation
would have Read only access.
Configuration 1. On the DMR web browser, select Settings > Authentication and click
procedure for Edit.
RADIUS
2. Select RADIUS from the Remote field drop down.
3. In the RADIUS server area, enter the IP address, port number, and
shared secret of the RADIUS server.
5. Click Save.
5.16.1 Overview
There are three types of adjacent site, of which two are external:
■ Local - the site belongs to the same network
■ External inter-network - the site belongs to another network, and is
updated dynamically as it may have dual control channels or rotating
control channels. Also recommended to be used to mitigate channel
failures at remote network sites.
■ External fixed - the site belongs to another network, and has a fixed
control channel RF number and syscode, or it is a cell extender site
Note that for the adjacent site feature to work, the DMR specification
must be 1.6.1 or higher (Settings > Network Parameters > Compliance).
DMR
Site 1
MPT
Site 1
TN9500 Inter-Network
Gateway
The external site feature enables radios to move seamlessly from one site
on one network to an adjacent site on another network. The external
adjacent site will belong to an external DMR, MPT-IP or TaitNet MPT
network (connected via a TN9500 gateway). The current network will
broadcast information to the radios about this external site (control channel
RF number and syscode) to enable the radios to vote between the site it is
on and the external inter-network site.
Only the sites nearest in geographic location to the current control channel
should be configured as adjacent, in order to maintain acceptable
performance during site re-selection.
Before you begin, you will need to know the site aliases of the DMR/MPT-
IP sites that are to be configured as external sites. On your DMR/MPT-IP
WebUI, select Network > Sites, click the name of a site, then click on the
Configuration tab to find the site alias.
For MPT sites, you will need to know the site name. Note that when entered
on the TN9500, any spaces in the name must be removed.
8. Select Add to add an external site. The Add MPT External Site page
is displayed.
9. Enter the site ID and alias, and select the type from the drop down
box. Options are Dynamic or Fixed.
Note that the site ID must be the same as the site ID assigned to this
site on the NMT (i.e. the order the sites are added must be the same
as the order the sites are added in the NMT).
10. If the type of external site selected is Fixed, then the primary control
channel RF number and syscode must also be entered, and
optionally, the secondary control channel RF number and syscode,
where required for sites with dual control channels.
4. Select Network > Sites, click the name of a site, and then click the
Voting Parameters tab to display voting configuration settings for the
site.
6. DMR only: In the Voting Parameters area, enter a site priority for the
current site. Options from the drop down menu are: No priority,
Highest priority, Priority 2 to Priority 6, and Lowest priority.
Each site has an assigned priority, and the vote now messages con-
tain the priority of both the current site and the site to be voted on.
Radio units can be configured whether to use the priority field or not.
When enabled, radio units will use the site with the highest site pri-
ority so long as the site signal strength is above the radio’s pro-
grammed L0 level.
Using the site priority may result in a radio roaming to a site with a
weaker signal strength than the currently registered site.
7. Enter the vote now interval and adjacent site info interval. These
represent the time between broadcasts of vote now and adjacent site
information messages from this site to the radios at the site.
9. To insert an adjacent site in the list, click in a row and then click
Insert. A new row is added above the selected row.
11. Enter the alias of the adjacent site. Note that for MPT sites, this is the
site name with any spaces removed.
TaitNet MPT The inter-node interface (INI) is used to communicate external inter-
network adjacent site information (using the NMT site ID) from the MPT
network to the TN9500 gateway. If the site information (site ID, control
channel RF number or syscode) changes, the TN9500 gateway will receive
the updated control channel parameters.
3. To add the TN9500 gateway (as a node) press the Add button to
display the Add Node window.
4. In the Node Number box, enter a number for the TN9500. It must be
a number between 0 and 31. It is recommended that you use the
highest number possible (i.e. 31) to distinguish the TN9500 from
other network nodes.
5. In the Node Name box, enter a suitable name for the TN9500.
8. To enter the sites, click on the cells in the Sites table and enter the
name and mnemonic (if required) for each external site configured
on the TN9500. Note that the site ID must be the same on both the
NMT and the TN9500, i.e. they must be entered in the same order.
10. Press Apply to save your changes then Close to close the window.
12. For each site, select Site > Configuration (where Site is the MPT site)
and select the Adjacent Site tab.
13. In the Vote Now area, enable vote now broadcasts, by checking the
box, and enter the required vote now broadcast interval for the
between vote now messages being transmitted.
14. In the Adjacent Sites table, click in the Site area and select the
adjacent sites as required from the pop-up node/site menu that
appears. For each entry, select Vote as the voting mode.
15. Click Apply to save your changes then Close when finished entering
adjacent sites for the selected site.
16. Select other sites as required until all external inter-network sites
have been added as adjacent sites to the relevant MPT sites.
3. In the Features area, the Alternate Poll Delay Threshold can be set to
determine if polls on the alternate channel can be marked as delayed.
■ Late poll data can be viewed in the site and channel statistics
reports. No alarm is raised if alternate polls are delayed by the
threshold set here.
■ Excess delays are recorded in both the poll-stats file (under
stats/polling/poll-stats_xxxxx.csv), and are also displayed in
the Alternate Channel Statistics area on the channel status page
(select Network > Sites and select a site, click the Channels tab
and then click on a channel ID to view channel status).
4. To enable the alternate channel at a site, select Network > Sites and
select a site. Click the Channels tab and then click on the channel ID.
Click Edit.
7. In the Location Polling area, select the Alternate poll type from the
drop down. Current options are DMR USBD LIP or Disabled.
■ The other selectable polling type is for the control channel. Valid
options for this are DMR Standard, Tait Format 1, Tait Format 2,
DMR USBD LIP format or Disabled. This allows for flexibility
in the types of control channel polling and alternate channel
polling required.
8. Enter the poll intervals for the poll types selected by entering a
numeric value in the first field and selecting the required interval
from the drop down menu. Interval options are seconds, minutes,
hours or days (note that the maximum interval is 1 day).
■ For control polling there is a limit of 5 seconds, but for alternate
polling, 1second is the minimum. The slowest rate is one day.
The DIP interface can now process polling at a speed faster than 5 sec-
onds. The avl.dip_min_report_interval parameter in the controller
configuration file is used to set the minimum interval between sending
AVL reports out on the DIP interface. This value should be set lower
than the lowest poll interval of the terminal population. If the DIP inter-
face is required to monitor large numbers of USBD polls, then reset the
avl.dip_min_report_interval to 3 seconds.
2. Individual unit location and update times (on the node web browser,
Subscribers > Fleets > Unit > Location tab).
Radio configuration 1. In the DMR Programming Application, select Trunked > Radio
Calls > Call Options > DMR ‘Channel Authorization’.
1. Select Settings > Local Parameters and click Edit to enter the
required values for the switching node you are currently logged on
to.
2. Click Save.
3. Select Network > Nodes to add the control node to the switching
node’s node table.
4. Click Save.
6. Under Mode, select Program, then click Save. This will propagate
the full database from the control node.
7. When the database has been propagated from the control node, the
mode will change to Offline.
9. For verification, log on to the control node and select Network >
Status > Nodes to check that the status for the switching node is
correct (i.e. Switching).
1. This is only true if High Availability is set up on all of the nodes. If it is not
set up, the switching nodes will still take over as control nodes in the event
of a control node failure, but their databases will not automatically be syn-
chronized. In this situation, the required information has to be manually
entered into each node.
Using ssh, log on to the node controller as the taitnet user. To stop the node
controller enter:
taitnet stop
If the node controller is running or the software is hung, you can restart it
by entering:
taitnet restart
Firstly you should use the WebUI to set the node to Offline. This will stop
the node processing calls.
There are several ways to power off the server in a controlled manner:
Tait Ubuntu ■ If you have access to the node controller hardware, simply press the
power button
■ If you are shutting the machine down remotely, ssh to the node and enter
the following:
sudo poweroff
TaitCentOS ■ If you have access to the node controller hardware, simply press the
power button
Solaris ■ If you have access to the node controller hardware, simply press the soft
power button. The shutdown will take a few moments. The button is on
the left of the front panel for the X4200, X4250, X4270 and X3-2
servers.
■ Use the ILOM web interface to select a “graceful shutdown and power
off”.
■ If you are shutting the machine down remotely, ssh to the node and
switch to the root user. Enter the following:
init 5
To restart the node controller, you will have to physically switch it on.
Failure to follow this advice may lead to corrupt system files which will
prevent the node operating.
Using the Node 1. On the DMR web browser, select Settings > Local Parameters.
2. Click Reboot. This will not only reset the node, but also reboot the
server. It takes several minutes to do a full reboot.
Using an ssh If you are unable to access the Node, you can perform a manual reset using
connection ssh:
3. This will restart all the node processes on the server. Unlike using the
Node however, it will not perform a full reboot, so does not take as
long.
Note that only one local time can be used per network. All nodes in a
network must be set to the same time zone, regardless of whether they
are physically located in different time zones.
To change the time zone, log into the Administration application and set the
desired timezone from the Configuration > General page.
The local time will be displayed in all log files as well as the alarms and
call records pages on the WebUI without a UTC offset.
The one exception is the status bar that is always displayed across the top
of the WebUI. It now has a time-date field in the middle that displays the
current time and UTC offset of the node in full date format as follows (for
example):
Tuesday, 2014 February 11 12:51:57 UTC+00:00 (the
node local time is the same as UTC)
Tuesday, 2014 February 11 12:51:57 UTC+13:00 (the
node local time is 13 hours ahead of UTC)
Note that only one local time can be used per network. All nodes in a
network must be set to the same time zone, regardless of whether they
are physically located in different time zones.
For first time installation and configuration the time zone can be set during
the installation of TaitCentOS (see the relevant section of the Tait Core
Networks Installation and Configuration Manual).
To change existing systems to a local time zone you must perform the
following procedure:
3. Login to the WebUI and check that the date/time is now being
correctly displayed as per the following example:
Fri Jan 17 01:39:30 GMT 2014 (before changing time zone)
Fri Jan 17 14:50:19 NZDT 2014 (after changing time zone)
The local time will be displayed in all log files as well as the alarms and
call records pages on the WebUI without a UTC offset.
The one exception is the status bar that is always displayed across the top
of the WebUI. It now has a time-date field in the middle that displays the
current time and UTC offset of the node in full date format as follows (for
example):
Tuesday, 2014 February 11 12:51:57 UTC+00:00 (the
node local time is the same as UTC)
Tuesday, 2014 February 11 12:51:57 UTC+13:00 (the
node local time is 13 hours ahead of UTC)
6.4.3 Solaris
Note that only one local time can be used per network. All nodes in a
network must be set to the same time zone, regardless of whether they
are physically located in different time zones.
For first time installation and configuration, refer to the TN9300 Node
Controller Installation Manual (MNB-00001-02), where the time zone can
be set during the installation of Solaris 10.
To change existing systems to a local time zone you must perform the
following procedure:
5. Login to the WebUI and check that the date/time is now being
correctly displayed as per the following example:
Fri Jan 17 01:39:30 GMT 2014 (before changing time zone)
Fri Jan 17 14:50:19 NZDT 2014 (after changing time zone)
The local time will be displayed in all log files as well as the alarms and
call records pages on the WUI without a UTC offset.
1. On the DMR web browser, select Files > Alarms to display the list
of alarm files.
Because log files can be quite large, they may be split into several files.
Each filename is appended with the timestamp of when the log file was
rolled over when the maximum file size was met. The node keeps the
latest 50 log files of each type, so it is recommended that they be regu-
larly downloaded for diagnostic purposes.
1. On the DMR web browser, select Files > Logs to display the list of
log files.
1. On the DMR web browser, select Files > General Statistics, then
click the relevant tab to display the list of files.
2. To download statistics files, select the required files using the check
box at the start of each row, and click Download (which only
displays once one or more files have been selected).
For a complete list of available statistics files and how to monitor them,
refer to Section 7.4 Monitoring Statistics.
Where <node_name> is the IP address of the node you wish to copy from.
Log in to the Administration application and select Files > Backups then
the tab for your DMR trunked node to list the backup files stored for that
service. Backup files contain server database and configuration settings.
Backup files are created automatically. From the tabs on this page, you can:
■ Download a backup file
■ Upload a backup file so that you can restore a previous configuration
You cannot create a DMR node backup from the Administration Appli-
cation. You must log in to the node and create the backup there.
Manual Backup 1. On the DMR web browser, select Files > Backups.
2. Click Backup.
4. Give the node time to create the backup and then use a browser
command to reload the page. This updates the display to show the
file that has been created.
Download a Backup 1. On the Administration application browser, select Files > Backups
File and the tab for your DMR trunked node.
Upload a Backup 1. On the Administration application browser, select Files > Backups
File and the tab for your DMR trunked node.
2. Click Upload and then select the name of the file you wish to upload.
When the Upload button is used, the maximum file size that can be
selected to upload is 700 MB, and 2000 MB for version 4.
View Backup File 1. On the Administration application browser, select Files > Backups
Details and Manage and the tab for your DMR trunked node.
Restore Options
2. Click the check box to select the file and then click View.
4. In the Manifest area all the files contained in the backup are listed in
either the Restore or Ignore boxes. These are default lists that can be
changed. You can move the files between the boxes to provide
advanced control over the settings to be restored.
5. Click the Restore button, and confirm, to restore the files listed in the
Restore box. The files in the Ignore box will not restore.
Delete Backup Files 1. On the Administration application browser, select Files > Backups
and the tab for your DMR trunked node.
2. Select one or more files, using the check box at the start of each row,
and click Delete.
The server automatically deletes backup files that are older than 30
days.
Manual backup 1. On the DMR web browser, select Files > Backups.
2. Click Backup.
Restoring 1. On the DMR web browser, select Settings > Local Parameters.
2. Click Edit.
4. Click Save.
8. Click Edit.
Some server firmware versions may not be compatible with other ver-
sions. Please consult the release notes before installing a new firmware
version.
The following types of firmware file are available from the Administration
application:
■ Updates to the Administration Application
■ Operating system updates
■ Anti Virus updates (pattern files and engine updates)
■ Tait Services, e.g. the TN9300 DMR Node
Tait services are delivered as container ‘Images’, which are bundles that
contain all the software and libraries necessary for the service to oper-
ate.
Upload a New 1. On the Administration application browser, select Files > Firmware.
Firmware Version
2. Click Upload.
When the Upload button is used, the maximum file size that can be
selected to upload is 2 GB.
Upgrade to a New 1. On the Administration application browser, select Files > Firmware.
Firmware Version
2. Select the correct firmware file from the list of uploaded firmware
files.
3. Click Install.
6. If you are upgrading the Operating System, you may need to reboot
the server afterwards. If a reboot is required, a message will appear
on the Configuration > General page.
7. If you are upgrading a Tait service, the installation merely copies the
new container image into a repository on the server. To start using
the new image you must configure the service to use it. At the end of
the installation you will be prompted to do so with the following
message “Installation complete. To use this software you must
configure the service to use it.” If you click Configure, you will be
taken to the configuration page for the service. Select the new
version from the drop down list, ensure Enabled is selected and click
Save.
Validate a Firmware 1. On the Administration application browser, select Files > Firmware.
Version
2. Select the correct firmware file from the list of uploaded firmware
files.
3. Click Validate.
3. Click Delete.
The following types of firmware file are available from the Administration
application:
■ Application packages (for example DMR, or the TN9500, which
includes the Inter-Network gateway, E1 gateway and transcoder
applications)
■ Lone applications (e.g. the Administration application)
Upload a New 1. On the Administration application browser, select Files > Firmware.
Firmware Version
2. Click Upload.
When the Upload button is used, the maximum file size that can be
selected to upload is for version 3 is 700 MB.
Upgrade to a New 1. On the Administration application browser, select Files > Firmware.
Firmware Version
2. Select the correct firmware file from the list of uploaded firmware
files.
3. Click Install.
4. The first step of the install process is to validate the upgrade file. The
install will not take place if problems are detected, otherwise the
install process is begun.
Validate a Firmware 1. On the Administration application browser, select Files > Firmware.
Version
2. Select the correct firmware file from the list of uploaded firmware
files.
3. Click Validate.
3. Click Delete.
Upload a New 1. On the DMR web browser, select Files > Firmware.
Firmware Version
2. Click Upload.
Upgrade the Node 1. On the DMR web browser, select Settings > Local Parameters.
to a New Version
2. Click Edit.
4. Click Save.
6. Select the correct firmware file from the list of uploaded firmware
files.
7. Click Install.
Reverting to an This procedure can also be used to revert to a previous version of the
Earlier Version firmware. When the node controller firmware is upgraded, the old
firmware is not overwritten. Simply select the firmware version you wish
to re-install.
3. Select or create the outphone table to which you wish to Add the
short form or network operator numbers.
7. Select the SIP Group required. Do not select the Divert option as the
diversion of short form numbers is not supported.
8. Click Save.
9. Select Subscribers > Fleets > Units to apply the Outphone table to
the Validation rights of the radio units you wish to use short form or
network operator dialing.
Short form dialing allows radio users to access telephone numbers without
having to enter the whole number. Instead, they dial two asterisks (**)
followed by a two-digit code.
The MPT 1343 standard specifies a set of three-digit numbers that radio
users can dial to access operator services such as fault reporting. Each
number can be mapped to an individual address, a group line dispatcher or
a phone number.
2. The network operator emergency number **000 can also be set up on sys-
tems using the ANN numbering system.
DMR
Status Node version
Meaning standards
number support
field valuea
a. The DMR specification TS 102 361-4 DMR Trunking Protocol with which the firm-
ware version is compliant. See WebUI Settings > Network Parameters > Compli-
ance > DMR Specification Version.
b. The default (recommended) configuration in Tait radios is to use 99 for cancel call
back requests.
3. Select or create the outphone table to which you wish to add the 0900
number to bar.
7. Click Save.
8. Select Subscribers > Fleets > Units to apply the Outphone table to
the Validation rights of the radio units you wish to prevent from
making 0900 calls.
Partition classes 1. On the DMR web browser, select Subscribers > Partition classes
2. Select the required Site. (If adding a new site, you must first enter the
site configuration details and save them. Then add the channels to
the site before creating the partitions).
6.16.1 On Registration
2. The site will first acknowledge the registration, but not record it in
the database.
4. If it does not get an authentication reply from the radio it will ignore
the registration.
5. If the radio replies, but does not support authentication keys, it will
accept the registration, and record this in the registration database.
6.16.2 On Call
2. The authentication check will be done as part of the call setup, before
the call is sent to channel.
3. If it does not get a reply from the radio, the call will not be set up.
4. If the radio that replies does not support authentication keys, and
there is no key in the database, then it is assumed the radio does not
support authentication keys, and the call setup will continue.
5. If the radio that replies does not support authentication keys but there
is a valid key in the database, it is assumed the radio does support
keys and the call will not be set up. The radio will be asked to re-
register.
When this is enabled, the system will reject registrations and/or call
requests if the calling party fails an authentication check.
The spare node can be prepared ahead of time with steps 6.17.1 and 6.17.2,
which may take up to two hours.
Instructions on how to do this are in the Tait Core Networks Installation and
Configuration Manual.
Instructions on how to do this are in the Tait Core Networks Installation and
Configuration Manual.
6. The node will reboot. This will take a few minutes. Once this is done,
log back into the node.
1. On the control node, select Network > Nodes and add the spare node
to this list.
2. Do the same on the spare node; add the other system nodes to
Network > Nodes.
3. Once this is done, on the spare node, put the node into program mode
(Settings > Local Parameters).
At this stage, the spare node will connect to the active control node
and synchronize its database. The spare node’s state will change
from ‘program’ to ‘offline’.
The spare node is now an active node on the system, replacing the failed
node.
The Assigned, Affiliated, and Dynamic groups lists each ‘represent’ a node
database table. With calls to registration-based groups, all three database
tables are searched to construct the list of sites that will be included in the
call.
The methods for group subscription are described in the following sections.
If groups have been entered into the radios at programming time, the only
way that the node can use registration-based groups is if these programmed
assignments are manually entered into the node’s databases using Group
Assignment. This list can also be used to perform dynamic regrouping from
the node (see Section 6.18.3 Dynamic Regrouping).
This is also useful for non-Tait radios which do not support radio controlled
group affiliation.
Procedure 1. Select Subscribers > Fleets and then click the name of the fleet that
the unit belongs to.
3. Using the arrow buttons at the bottom of the display, or the filter,
navigate to the page displaying the number of the unit.
4. Click the number of the unit and then click Edit to make the page
editable.
5. Edit the Group Assignment section and set the groups you wish the
radio to belong to.
a. To add a group, enter the group address in the Address box and
click Add.
b. To delete a group, select it from the Assigned groups list and click
Delete.
6. Click Save.
This does not affect the radio in any way, as no message is sent to the radio
about which groups the radio is assigned to. All that changes is the list of
sites on which a group call is set up. The node determines which radios are
assigned to the group and then sets up the call on only those sites with at
least one assigned radio.
Procedure 1. Select Subscribers > Fleets and then click the name of the fleet that
the unit belongs to.
3. Using the arrow buttons at the bottom of the display, or the filter,
navigate to the page displaying the number of the unit.
5. If the Assigned groups list does not list all the required groups, click
Edit to move to the Unit Edit page and edit the Group Assignment
section:
a. To add a group, enter the group address in the Address box and
click Add.
b. To delete a group, select it from the Assigned groups list and click
Delete.
6. After you have made the changes required, click Save and you will
be returned to the previous page
8. Use the <Ctrl> key and the mouse to select up to 15 groups in the
Assigned groups list, then select the Regroup Selected button to send
a dynamic regroup poll to the radio instructing it to affiliate to the
selected groups and to de-affiliate from other dynamic regroup
groups.
You can view the status of the poll in the Regroup Status field which will
display one of the following:
State Meaning
- No poll has taken place. The user must poll the radio
for the information
Reply corrupted The radio replied to the poll, but the information
received was unreadable
Rejected by radio The radio was contacted, but did not send the
requested information. This usually means that the
radio has old firmware.
Unknown failure The poll failed. The reason for the failure is not
known.
Radio
Unit Node
Regroup Poll
ACK
Group Affiliate
Whenever a dynamic regroup (or clear dynamic regroup) poll is sent, the
radio must first acknowledge it before the node updates its Dynamic Group
list. Furthermore, given that the Group Affiliation related settings are
enabled in the radio’s configuration, the radio will send an affiliation
message with the list of groups it remains affiliated to (but it does not
specify whether each group is radio affiliated or dynamically regrouped).
The node updates the Group Affiliation list groups list with this
information.
The key type, key ID and key variable created here must also be
entered on the DMR node WebUI. Each radio can be configured with
up to 4 encryption keys.
3. Then update the Encryption parameters in Network Settings:
This provides support for low-tier SIP-connected dispatchers, e.g. the ETC
desktop Mic CS-74.
Group calls from SIP line to SIP line are not supported.
Configuring the SIP lines can be added to outgoing group calls by entering up to four group
Node addresses and the associated destination (extension) numbers to each SIP
line.
When making a group call, the node will check if the group address is
configured in SIP lines and, if so, will then try to make a SIP call to the
corresponding SIP lines.
2. Click Add to create a new SIP line, or to update an existing SIP line,
select the line and click Edit.
3. Enter/edit the required values for your SIP line for the Identity and
Validation parameters.
4. Add group addresses and their outgoing destinations for the SIP line,
if required.
5. Click Save to save this SIP line. Add/edit more SIP lines as required.
Configuring the Configuration settings for the ETC desktop Mic CS-74 are suggested as
ETC CS-74 follows:
■ Jitter buffer: 100ms
■ Master volume level: 80%
■ Mic volume: 40 %
■ NGW audio level setting: default
1. Backup the current license file(s) so that they can be restored in case
the upload procedure for the new license is interrupted or fails.
a. Login to an ssh session (Tait Ubuntu users, see note for Version
4 users in Section 6.22 Additional taitnet commands).
The existing SIP, DIP, AIS and other interfaces should work as usual (as
previously licensed under the DMR Express6 or DMR Express20 sys-
tem). An upgrade only increases the number of sites and channels that
can be added to the system, as well as (for an upgrade from DMR
Express6) adding the ability to install an HA license, if required.
Version 4 users only. Before entering a command, you need to first log
into the container. Enter docker exec -it tait_dmrnc bash, fol-
lowed by cd dmrnc. Then enter your command(s) as required. When
you are ready to logout, enter logout or just press Ctrl-d. This will
return you to the command shell on the host server.
For version 3 and version 4 nodes, all commands must be preceded with
a dot and forward slash (./), for example ./taitnet backup
taitnet build Print the software version and build number of the currently running node
to the screen. The digits after the last . (period) represent the build number.
Example: 1.02.05.03
taitnet clean- Delete all log files and core files (if they exist), then restart the node
restart controller software. Tait does not recommend using this command without
good reason.
taitnet log Print a running copy of the node log to the console. Type <Ctrl>+c to stop.
taitnet net Re-read the network address parameter in the configuration file3 without
restarting the node.
taitnet Re-read the configuration file. This causes all parameters in this file to be
reload-cfg reloaded into the node software without restarting the node. Most, but not
all, parameters specified in the configuration file can be changed using this
command. To execute a change of the network address parameter use the
command taitnet net. Many parameter values are attached to a timer
that executes every minute, so it can take up to one minute from the time
taitnet reload-cfg is run until the change occurs.
taitnet Check if any of the logging levels in the configuration file have changed,
reload-log- and change the logging appropriately, without rebooting the node.
level
taitnet start Start the node. Do not use this command if the node is running already.
3. Refer to Section 6.23 Node Resource File for node controller configura-
tion file name and directory path.
taitnet start- Start the node in program mode. Do not use this command if the node is
program-mode already running, instead use the Web interface to move the node into
program mode.
taitnet status If the node controller software is running (in any mode, including program
mode) then print Node is running to the console screen, otherwise print
Node is NOT running to the console screen.
taitnet stop Stop the node. This will disable the WebUI as well.
taitnet Print the software version number of the currently running node to the
version screen.
Example: 1.02.05
TaitCentos File The version 3 node has a resource configuration file (tait_dmrnc.cfg),
Location located in the /home/taitnet/dmrnc directory. This file provides some
limited configuration parameters that cannot be changed when logged on
to the node. It is not recommended that they are changed unless Tait
Technical Support has requested it. These parameters are read at startup
and whenever the command ./taitnet reload-cfg is executed. The
file has to be edited by a text editor such as ‘vi’.
Tait Ubuntu File In version 4 nodes, the resource configuration file (tait_dmrnc.cfg), is
Location located inside the container in /home/taitnet/dmrnc. If a parameter has
been edited, you must then go to the directory /home/taitnet/dmrnc and
run the following command ./taitnet reload-cfg.
agw.groups This is a list of which groups should be sent to the MPT gateway if enabled.
Groups are separated by a space. By default no groups are enabled.
agw.groups This is a list of which groups should be sent to the MPT gateway if enabled.
Groups are separated by a space. By default no groups are enabled.
3. To find out more, click a row. This takes you to a page that lists
elements of that type and allows you to view their configuration, and
in some cases, monitor their current operation.
If you are unable to access the Node you can manually check the status of
the node.
3. You should see something like the following if the node is running
correctly:
$ taitnet status
Watchdog is running
Node is running
Packet Switch is running
4. If any of the processes are not running you should manually reset the
node (see “Resetting a Node” on page 188).
Call record files are saved in both comma separated file format (.csv) and
text file format (.txt).
Csv files The first line in the csv file contains the headings for the columns, and the
subsequent lines contain the values for each call record as follows:
date_time A string containing the date and time the call was created.
The format is: YYYYMMDDThhmmssZ, where T and Z are
the characters T and Z.
a_party_MPT 1327 The calling party address in extended MPT 1327 format
(prefix/ident). In MPT 1327 the prefix is restricted to the
range 0-127. The extended format allows prefixes in the
range 0-4196.
b_party_MPT 1327 The called party address in extended MPT 1327 format
(prefix/ident). In MPT 1327 the prefix is restricted to the
range 0-127. The extended format allows prefixes in the
range 0-4196. If the address is outside the MPT 1327
address range, or if it is a System ID (refer to Section 7.2.6
System IDs), the DMR number is displayed.
sip_a_party_digits The calling party digits received from the SIP gateway for
telephone-to-radio calls
sip_b_party_digits The destination digits sent to the SIP gateway for radio-to-
telephone calls, or the digits received from the SIP gateway
for telephone-to-radio calls
queue_time The number of seconds that the call waited for processing
(for example, the node was waiting for the radio’s IP
information during registration) or was queued due to lack
of channel resources
end_reason Refer to the table in Section 7.2.3 Call End Reasons for a
complete list of call end reasons
handler_id Refer to the table in Section 7.2.5 Call Handler IDs for a
complete list of call handler IDs
line_id For handlers with multiple lines, this represents the line ID
switch_node_id The ID (number) of the node that switched the audio for the
call. For calls that did not go to channel this will be 0.
switch_node_zone The switching zone assigned to the node that switched the
call
a. For PTT overs, the LOCAL flag actually indicates if it is the called or call-
ing party transmitting. i.e. if the local flag is set, it means called party.
Txt files The text file can have one of two formats:
DateTime: 20110922T232728
CallId: 32a35de6-f9cc-6a51-a653-0e5a1385756b (00000012)
From: 200-2100-204 (00000204) To: 200-2100-209 (00000209) Digits:
OnAirTime: 00000004 QueueTime: 000 AnswerTime: 001
CallType: I CallPriority: 1 CallFlags: 00020000 EndReason: 021
Site/HandlerID: 0002 Channel/LineID: 002 (293)
SwitchingNodeID: 0004 SwitchingNodeZone: 0003
or
DateTime: 20110922T232728
CallId: 32a35de6-f9cc-6a51-a653-0e5a1385756b (00000012)
From: 200-2100-204 (00000204) To: 200-2100-209 (00000209) Digits:
OnAirTime: 00000004 QueueTime: 000 AnswerTime: 001
CallType: I CallPriority: 1 CallFlags: 00020000 EndReason: 021
Site/HandlerID: 0002 Channel/LineID: 002 (293)
Info: Site B, calling, normal, individual_voice, calling_party_clear
SwitchingNodeID: 0004 SwitchingNodeZone: 0003
The following table lists the possible call types and characters representing
those call types.
Type Description
A Authentication check
b Broadcast
B Bar unit
F Force registration
ga Regroup
G Group voice
K Kill unit
L Revive unit
p AVL poll
R Registration
T Call diversion
U USBD poll
W Status poll
x Cancel call
y Supplementary data
Y Stun unit
z ALLMSID
This field contains a numeric code giving a detailed reason why the call
ended or failed. It is used to help diagnose configuration and equipment
faults.
Any call end reasons that have been generated by a TaitNet MPT net-
work (connected by a TN9500 Inter-Network Gateway) are identifiable
as they will be numbered as 1000 plus the TaitNet MPT call end reason.
Call end reasons generated by the TN9500 Inter-Network Gateway are
numbered as 2000 plus the call end reason. Refer to the TaitNet MPT
System Manual or TN9500 Installation and Configuration Manual for
their call end reasons.
The following table lists the number and name of each call end reason and
provides descriptions of them.
0 Unknown
The network was unable to establish why the call ended or failed
2 No control channel
The call was unable to be completed as there was no control channel available at the site to
handle this call request
3 Poll failed
A unit poll failed (either stun/revive/regroup/authentication)
4 Poll successful
A unit poll completed successfully (either stun/revive/regroup/authentication)
7 Registration accepted
The calling party registered at a site in its configured service area, and now has service on this
site
16 Connecting timeout
The call has failed to connect all links in the call to an unexpected error elsewhere in the
system
19 Data successful
A data call on the control channel was successfully completed
43 Channel failure
The channel carrying a call has failed, either due to a major fault (e.g. transmitter low forward
power alarm), or a communication loss to the channel. The call has been cleared down from
the system. However, as the channel is not working, it will be impossible to inform the radios
involved in the call.
44 Site overloaded
Call could not be set up because site is overloaded. The site can only process a certain
number of calls or messages at one time.
56 Authentication failed
The authentication check has failed
57 Authentication good
The authentication check is successful
58 No outphone table
An outgoing call to a PSTN or PABX failed because there is no outphone table set up for the
calling party
59 No outphone rule
An outgoing call to a PSTN or PABX failed because there is no outphone rule that meets the
criteria for the number the calling party has dialed
76 RCGA successful
The calling party has successfully requested a new group affiliation, or cleared its group
affiliation
77 RCGA failed
The calling party requested an invalid group affiliation, either with incorrect data in the SDM
request, or to a group that does not support group affiliation
81 PTT
A normal voice call over was completed
82 Call included
A call was included in another call at the site
84 PTT emergency
An emergency voice call over was completed
This field contains a numeric code giving a detailed reason why the call
closed.
The following table lists the number and name of each call close reason and
provides descriptions of them.
1 TE BUSY
The called party is busy
2 SYS_BUSY
The DMR system is too busy for this call
3 REJECTED
The called party rejected the call
4 NOT_HOME
Called party could not be found
5 COMPLETE
Cleared, completed, accepted
6 CALL_BACK
Queued in the radio for callback
7 INVALID
Call rights / service type failure
8 PREEMPT
The call link wants to pre-empt the call
9 AMALGAMATED
Call has been amalgamated into a group
call
99 UNKOWN
The call has closed for an unknown reason
System ID’s are addresses used in signaling over the air when making calls
to and from the special gateways, rather than to an individual or group (e.g.
phone calls).
ALLMSI 0xFFFED4 16776916 The totality of all individual MS and talkgroups (used in
Clears only)
ALLMSID 0xFFFFFF 16777215 ID used to address all MS (AllCall) in every site in the
system as a talkgroup
DISPATDI 0xFFFED3 16776915 Address of the system dispatcher using payload offset
timing
LINEDI 0xFFFED2 16776914 Address for services to a Line Gateway using payload
offset timing
LINEI 0xFFFEC2, 16776898 Address for services to a Line Gateway using payload
aligned timing
PABXDI 0xFFFED1 16776913 Gateway address for services to the PABX using
payload offset timing
PABXI 0xFFFEC1 16776897 Gateway address for services to the PABX using
payload aligned timing
PSTNDI 0xFFFED0 16776912 Gateway address for services to the PSTN using
payload offset timing
PSTNI 0xFFFEC0 16776896 Gateway address for services to the PSTN using
payload aligned timing
SDMI 0xFFFEC5 16776901 Address used to identify a UDT short data service
Each alarm message in the alarm log file consists of a string of ASCII
characters in comma-separated fields, terminated by the Enter character.
1. Date/Time
The Date/Time is represented as ISO8601 format of YYYYMMD-
DThhmmssZ where:
■ YYYY indicates a four-digit year, 0000 through 9999
■ MM indicates a two-digit month of the year in the range 01
through 12
■ DD indicates a two-digit day of that month in the range 01
through 31
■ hh indicates the hour between 00 and 23
■ mm refers to the minute between 00 and 59
■ ss refers to the second between 00 and 59
3. Alarm Type
This is the number of the alarm raised (see table below for alarm
types and details).
4. Alarm Details
These are the details of the alarm raised (see table below for alarm
types and details).
Alarm Alarm
Alarm Detail Name and description
Type Severity
0 Unknown OK
Alarm type is unknown
14 site=<int> Site up
The site has exited the ‘site failed’ state because at OK
least one channel has returned to service
32 site=<int>:bs=<int> Channel up
The node has established a connection to a OK
previously failed base station
49 Network up
The network check addresses are responding to OK
ping queries
55 site=<int>:bs=<int>:
Channel jammed Minor
channel=<int>
56 site=<int>:bs=<int>:
Channel unjammed OK
channel=<int>
74 user=<text>:id=<int>:
Tait TeamPTT link up OK
ip=<text>
75 user=<text>:id=<int>:
Tait TeamPTT link down Major
ip=<text>
Status
Alarm
Message Alarm Detail Name and description
Severity
ID
1. Refer to Section 6.23 Node Resource File for node controller configura-
tion file name and directory path.
A more detailed description of the site and channel statistics is given below.
For details on the other statistics files, refer to the online help under Files
> General Statistics.
Each file is labeled with the date that the statistics were recorded for, and
is written in a comma separated file (.csv) format that allows it to be
imported to Microsoft Excel, or viewed on a text editor. The simplest way
to download statistics is to select the appropriate file on your web browser
attached to the node. The files can also be manually downloaded from the
node by using a utility such as ‘scp’ to copy the statistics files from the The
statistics parameters are generally one of two types of parameters:
1. Absolute value: this is the actual real time value at the time the
record was written, and is generally what is displayed on the status
screens on the node.
2. Running total: these are the total values, or times, since startup of the
node and are accumulated over time. They are reset every time the
node is restarted.
Column Description
site Site number for the site these statistics are produced for
disabled Number of channels that have been disabled at the site at this
point in time
on_air Number of calls on air for this site at this point in time
cc_idle_tx Total number of transmit slots not used by the control channels
since startup
cc_idle_rx Total number of received slots not used on the control channels
since startup
chan_callsa Total number of calls that requested traffic channels (i.e. voice or
data) since startup. They may not have gone to channel.
t_queue Total time of queueing for all calls since startup, in seconds
t_cc Total time in seconds that channels have been control channels
since startup
t_tc Total time in seconds that channels have been traffic channels
since startup
t_idle Total time in seconds that channels have been idle since startup
t_fail Total time in seconds that channels have been failed since startup
Q_0s Number of calls that were queued for less than 5 seconds since
startup
Q_5s Number of calls that were queued for between 5 and 10 seconds
since startup
Q_10s Number of calls that were queued for between 10 and 20 seconds
since startup
Q_20s Number of calls that were queued for 20 seconds or more since
startup
t_ac Total time is seconds that channels have been alternate channels
since startup
a. Note that this represents all requests made for a traffic channel, including those
that did not result in a call being made.
The following calculations are examples of the type of information that can
be gathered from the statistics files, and are used in both the Daily Site
Details report and the Daily Site Summary report (Section 7.5). These may
help to determine when more channels or sites are required.
The channel statistics file is written to every 30 seconds, with a one line
record for every enabled channel in the system. It is a comma separated file
(.csv), with the following columns:
Column Description
rf RF channel number
2. Note that queue times also include the time that the node has to wait when
receiving registration or group affiliation information from radios.
rtp_ping_jitter Maximum Jitter time (ms) in the last 10 seconds. The jitter
indicates the time difference from when we expected an
RTP packet to arrive, to when it actually arrived.
failed Total seconds channel has been in failed state since startup
traffic Total seconds channel has been in use for traffic since
startup
control Total seconds channel has been in use for control since
startup
The node produces daily reports of site performance. There are two reports
generated for each day:
■ DailySiteSummaryReport-YYYYMMDD.pdf
■ DailySiteDetailsReport-YYYYMMDD.pdf
These reports are generated using data from the site statistics files, Daily
Site Summary Report
Traffic Channel The percentage of time that the traffic channels were not in
Availability a failed state. Traffic channels can be in one of three
modes: idle, carrying traffic and failed.
Control Channel The percentage of time that the control channel(s) were
Utilization busy.
Traffic Channel The percentage of time that the channels that were not in a
Utilization failed state were operating in traffic mode.
Traffic Channel The total number of calls that requested traffic channels
Calls (i.e. voice or data) for the day. They may not have gone to
channel.
Busy Hour/Start The time at which the busy hour started. The busy hour is
Time the 60 minute period during which the most calls were
made.
Busy Hour/Traffic The same as Traffic Channel Utilization (see above) but for
Channel Utilization the busy hour, rather than for the whole day
Busy Hour/Control The same as Control Channel Utilization (see above) but
Channel Utilization for the busy hour, rather than for the whole day
Busy Hour/Traffic The same as Traffic Channel Calls (see above) but for the
Channel Calls busy hour, rather than for the whole day
Busy Hour/Control The same as Control Channel Calls (see above) but for the
Channel Calls busy hour, rather than for the whole day
Busy Hour/GoS > A measurement of the grade of service (GoS) at the site.
5s This is the percentage of calls that were queued (waiting for
a traffic channel) for over 5 seconds. This is measured
during the busy hour.
Busy Hour/GoS > A measurement of the grade of service at the site. This is
20s the percentage of calls that were queued (waiting for a
traffic channel) for over 20 seconds. This is measured
during the busy hour.
This report is in the form of a series of graphs. Each site on the network has
two graphs, one for the control channel and one for the traffic channels.
3. Click Save.
The node will check its connection to the identified network element(s)
every 10 seconds. When only one network element’s IP address has been
entered, if the connection fails, then the node will automatically change
from control to switching mode. If two network elements IP addresses have
been entered, the node will remain in control mode if one connection has
failed, but if both connections fail, the node will change from control mode
to switching mode.