6881009Y05-O Vol 1 Understanding Your Astro 25 PDF

ASTRO 25 Trunked Integrated
Voice and Data System Release 6.4
Volume 1
Understanding Your ASTRO 25
Trunking System
6881009Y05-O
*6881009Y05* April 2004
Copyrights
The Motorola products described in this document may include copyrighted Motorola computer programs. Laws in the United States and other countries
preserve for Motorola certain exclusive rights for copyrighted computer programs. Accordingly, any copyrighted Motorola computer programs contained in the
Motorola products described in this document may not be copied or reproduced in any manner without the express written permission of Motorola. Furthermore,
the purchase of Motorola products shall not be deemed to grant either directly or by implication, estoppel or otherwise, any license under the copyrights, patents
or patent applications of Motorola, except for the normal nonexclusive, royalty-free license to use that arises by operation of law in the sale of a product.
Disclaimer
Please note that certain features, facilities and capabilities described in this document may not be applicable to or licensed for use on a particular system, or
may be dependent upon the characteristics of a particular mobile subscriber unit or configuration of certain parameters. Please refer to your Motorola contact
for further information.
Trademarks
Motorola, the Motorola logo, and all other trademarks identified as such herein are trademarks of Motorola, Inc. All other product or service names are the
property of their respective owners.
Copyrights
2004 Motorola, Inc. All rights reserved.
No part of this document may be reproduced, transmitted, stored in a retrieval system, or translated into any language or computer language, in any form or by
any means, without the prior written permission of Motorola, Inc.
Table
of
Contents
Contents

Understanding Your ASTRO 25 Trunking System
Chapter 1: Radio System Concepts

What Is a Radio System? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Basic Radio System Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Radio System Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Radio System Range and Frequency Spectrum . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Communication Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Simplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Half-Duplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Duplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Conventional Radio Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Repeater Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Dispatch System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Conventional Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Repeater Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Trunking Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Trunking Technology and Radio Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Motorola Trunked Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Motorola Single Site Trunked System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Single Site Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Central Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Repeaters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Control Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Voice Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
Packet Data Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
System Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
Call Processing Basics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
Conventional vs. Trunked Radio Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
System Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21
Radio System Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21
Tracing a Basic Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23
Basic Call Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23
Call Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29
Talkgroup Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29
Multigroup Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29
Emergency Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29
Private Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30
Telephone Interconnect Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30
6881009Y05-O April 2004 eDoc i

Contents
Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31

Multiple Site Trunked Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31
Motorola SmartZone Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-33
Major System Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34
Radio Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34
Master Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-35
Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-35
Call Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-36
Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-36
Multiple Zone Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-37
Additional Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-38
Home Zone Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-39
Controlling Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-40
Participating Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-40
Interzone Group Service Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-40
Where Calls Occur . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-40
Single Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-40
Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-40
Multiple Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-40
Chapter 2: What Is an ASTRO 25 Trunking System?

ASTRO 25 Trunking System Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
ASTRO 25 Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Multicast Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
The Call Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Traffic Planes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Voice Control Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Audio Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Network Management Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Data Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
The Transport Core . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Ethernet LAN Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
WAN Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Core and Exit Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Gateway Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Functional Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Call Processing Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Network Management Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Console Operator Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Radio Frequency Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
ASTRO 25 Repeater Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
ASTRO 25 Repeater . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
PSC 9600 Site Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Remote Site Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Ethernet Switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Mutual Aid Channel Bank . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
IntelliRepeater Site Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Multisite Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Digital Simulcast Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Simulcast Prime Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Prime Site Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Prime Site LAN Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
MTC 9600 Simulcast Prime Site Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
ASTRO-TAC 9600 Comparator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
ii 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Contents
Simulcast Remote Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16

Single Transmitter Receiver Voting Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Telephone Interconnect Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Data Communication Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Network Security Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Other Band Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Operating Bands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Subscriber Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Radio Frequency (RF) Subsystem Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
Audio Quality Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
System Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
Chapter 3: Network Topology

Local Area Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Ethernet Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Shared Ethernet LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Star Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Wide Area Network Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Asynchronous Transfer Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Transport Methods and Protocols. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
10Base-T. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
10Base-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Balanced Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Fiber Optic Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Frame Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Open Shortest Path First. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Path Diversity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Simple Network Management Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Static Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Asynchronous Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Synchronous Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
TCP/IP Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
T1 Carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
E1 Carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Virtual LANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
V.35 Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Network Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Chapter 4: Hardware Functional Description

Master Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
MZC 3000 Zone Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Controller Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
MZC 3000 Zone Controller Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Transport Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Master Site LAN and WAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Routers An Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Site Routers An Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Gateway Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Gateway Router MGEG Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Gateway Router Data Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Gateway Router Zone Controller Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Gateway Router Audio Switch Interface Support . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Gateway Router Network Management Support . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Core and Exit Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
6881009Y05-O April 2004 iii

Contents
Core Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16

Exit Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
GPRS Gateway Support Node Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Border Routers and Peripheral Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Ethernet LAN Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Fault Tolerance and Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Supervisor Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
Switching Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
Network Analysis Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
Fan Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
WAN Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
Control Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
Function Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
WAN Switch Interface Panels - Port Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
Fast Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
Digital Access Cross-connect Switch (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38
System Redundancy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39
Physical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39
Motorola Packet Data Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44
Packet Data Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45
Radio Network Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45
Network Management Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
Operations Support Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
Transport Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47
Fault Management at the Zone Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47
Configuration Management at the Zone Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48
Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48
Security Management at the Zone Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49
Network Management at the System OSS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49
Fault Management at the System OSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
Configuration Management at the System OSS . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
Performance Management at the System OSS. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
Security Management at the Zone and System OSS . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
Private Radio Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-51
System-Level Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-51
Zone-Level Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-53
TRAK 9100 Network Time Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56
NTP Configuration in FSU 9104 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-57
Out-of-Band Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58
Remote Analog Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58
Console Operator Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-59
Motorola Gold Elite Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-59
Channel Marker and Alert Tone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-61
System Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-61
Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-61
Ambassador Electronics Bank . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-69
AEB Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-71
Central Electronics Bank Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-76
Ambassador Interface Multiplex Interface Board . . . . . . . . . . . . . . . . . . . . . . . . . . 4-78
Console Operator Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-79
Console Interface Electronics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-79
Console Database Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-80
CENTRACOM Elite Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-81
iv 6881009Y05-O April 2004

CENTRACOM Elite Admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-81

Central Electronics Bank Card Upload Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-81
Alias Database Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-81
Remote Dispatch Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82
Telephone Interconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-83
DTI-1000 Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-83
Adjunct Control Signaling Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-84
Avaya PBX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-85
Echo Canceller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-88
Network Control Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-89
Echo Canceller Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-89
Fan tray assembly and filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-89
Network Security Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-89
Core Security Management Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-89
Network Interface Barrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-91
Radios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-92
ASTRO 25 Portable Radio Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-93
Signalling Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-93
Scan Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-93
Call Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-93
Subscriber Radio Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94
Motorola XTS 5000 Portable and XTL 5000 Mobile . . . . . . . . . . . . . . . . . . . . . . . . 4-94
Motorola ASTRO Spectra and ASTRO Spectra Plus. . . . . . . . . . . . . . . . . . . . . . . . . 4-95
Considerations for Radio Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-96
Backup Power Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-97
Chapter 5: Radio Frequency Subsystems

ASTRO 25 Repeater Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
ASTRO 25 Repeater Site Operational Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
ASTRO 25 Repeater Site Subsystem Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Single Router, Single Switch Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Single Router, Dual Switch Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Dual Router, Dual Ethernet Switch Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
WAN Switch Redundant Link Interface Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
ASTRO 25 Site Repeaters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
QUANTAR ASTRO 25 Site Repeater . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
Receiver Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Station Control Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
STR 3000 ASTRO 25 Site Repeater . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
STR 3000 ASTRO 25 Site Repeater Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Control Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
PSC 9600 Site Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
LED Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Rear Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
PSC 9600 Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
Infrastructure Time of Day Synchronization ASTRO 25 Repeater Sites. . . . . . . . . . . . . . . . . . . 5-22
Site Reference ASTRO 25 Repeater Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
Site Ethernet Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
Reset Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
Clear Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
Power Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
Mode LED Select Button and Indicator LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
6881009Y05-O April 2004 v

Contents
Console Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26

LED Indicators and Buttons HP 2626 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
Reset and Clear Button HP 2626 Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29
Site Router S2500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29
S2500 Site Router Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
S2500 Site Router LED Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
S2500 Site Router Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
Site Router Supported Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
IntelliRepeater Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
Component Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
QUANTAR IntelliRepeater . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
Receiver Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
Station Control Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
Transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35
PS40 Hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35
Site Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35
IntelliRepeater Subsystem Operational Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36
Digital Simulcast Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36
Digital Simulcast Subsystem Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37
Digital Simulcast Subsystem Communication and Interface Links . . . . . . . . . . . . . . . . . . . 5-37
Digital Simulcast Subsystem Network Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37
Digital Simulcast Subsystem Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39
Simulcast Prime Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
MTC 9600 Simulcast Prime Site Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43
Standard Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44
Simulcast System Applications Network Management. . . . . . . . . . . . . . . . . . . . . . . . 5-46
The ASTRO-TAC 9600 Comparator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-46
Control Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-48
Wireline Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-49
Power Supply. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-49
Network Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-49
Prime Site LAN Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-49
Reset Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50
Clear Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51
Power Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51
Mode LED Select Button and Indicator LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51
Console Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52
Prime Site Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52
Channel Bank. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-53
CPU Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54
Wide Area Network Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54
Interface Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55
Sub Rate Unit Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56
HSU Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56
4-Wire Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56
Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56
TRAK 9100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-57
Simulcast Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-58
Simulcast Remote Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-58
STR 3000 Base Radio Simulcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-60
STR 3000 Control Module LED Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-61
Simulcast Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-63
QUANTAR Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-65
Simulcast Remote Site Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-66
Remote Site LAN Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-67
vi 6881009Y05-O April 2004

Channel Bank. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-67

Simulcast Subsystem Configuration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-68
Essential Remote Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-69
Digital Simulcast Subsystem Configuration Using CSS . . . . . . . . . . . . . . . . . . . . . . . . . 5-69
Software Download Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-70
Software Download Considerations for Subsystems with Receiver Only Sites . . . . . . . . . . . . . 5-71
Software Download Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71
Transfer Only Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71
Install Only Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71
Transfer and Install Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71
Single Transmitter Receiver Voting Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-72
Data Capability Characteristics STRV Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . 5-72
Wide Area Trunking, Site Trunking, and Failsoft mode . . . . . . . . . . . . . . . . . . . . . . . . . 5-73
Single Transmitter Receiver Voting Prime Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-73
STRV Prime Site with Colocated Transmit Remote Site . . . . . . . . . . . . . . . . . . . . . . . . . 5-74
STRV Prime Site with Colocated Receive Only Remote Site . . . . . . . . . . . . . . . . . . . . . . . 5-74
MTC 9600 Prime Site Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-74
Control Module MTC 9600 Site Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75
Power Supply. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75
Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75
STRV Transmit Remote Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-76
QUANTAR Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-76
Receive Only Remote Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-77
QUANTAR Satellite Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-78
ASTRO-TAC Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-79
Software Download Considerations Receive Only Remote Sites . . . . . . . . . . . . . . . . . . . . 5-79
Receive Only Remote Site Map to Transmit Site . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-80
Receive Only Remote Sites Using CSS to Configure the Comparator . . . . . . . . . . . . . . . 5-80
Digital Simulcast Subsystem 10Base-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-81
Chapter 6: ASTRO 25 Systems and Mutual Aid

Digital Mutual Aid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Remote CEB With Mutual Aid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Inbound Call Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Outbound Call Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Mutual Aid with CEBs at the Master Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Digital Mutual Aid Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
STR 3000 Digital Mutual Aid Station. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Control Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
Digital Interface Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Channel Bank. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
CPU Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
Interface Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
Low Delay SRU Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
HSU Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Analog Mutual Aid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
ASTRO 25 Repeater Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
Wireline Interface Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
Channel Bank. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
CPU Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
6881009Y05-O April 2004 vii

Contents

Interface Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17
4-Wire Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18
HSU Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18
ASTRO 25 Repeater Site Mutual Aid Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18
ASTRO 25 Repeater Site With 18 Channels and Single Site Link . . . . . . . . . . . . . . . . . . . . . 6-19
ASTRO 25 Repeater Site With 28 Channels and Single Site Link . . . . . . . . . . . . . . . . . . . . . 6-19
ASTRO 25 Repeater Site With 28 Channels and Redundant Site Links . . . . . . . . . . . . . . . . . . 6-20
Simulcast Subsystems and Mutual Aid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21
Chapter 7: Databases, Servers, and Controllers

Radio System Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
System Data Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
How the System Uses Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Subscriber Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Home Location Register. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Visitor Location Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
VLR and the Packet Data Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Alarm and Alert Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Alias Database and Console Database Management Information . . . . . . . . . . . . . . . . . . . . . . 7-6
Statistical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
System Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
System Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
System Statistics Server Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
User Configuration Server Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Zone Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Home Location Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Visitor Location Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Zone Infrastructure Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Zone Local Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
Zone Statistics Server Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
Console Database Manager/Alias Database Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
Console Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
Alias Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
FullVision INM Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
Air Traffic Router (ATR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
Database Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
System Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Hierarchical View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
Subsystem View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
Server Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15
User Configuration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
System Statistics Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
Zone Database Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
Zone Statistics Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
Air Traffic Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
FullVision INM Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
Console Database Manager/Alias Database Manager Server . . . . . . . . . . . . . . . . . . . . . . . . . 7-18
Server Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18
Server Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20
Introduction to the Administration Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24
User Configuration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24
System Statistics Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25
Zone Database Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
viii 6881009Y05-O April 2004

Zone Statistics Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27

Air Traffic Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27
FullVision INM Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28
Chapter 8: Network Security

Network Security Requirements and Considerations Overview . . . . . . . . . . . . . . . . . . . . . . . 8-2
System Security Planning and Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Analysis and Control of System and Service Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Network Security Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Core Security Management Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Core Security Management Server Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Antivirus Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Antivirus Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
User Access Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Firewall Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Intrusion Sensor Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Network Interface Barrier Optional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Network Interface Barrier Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
Network Interface Barrier Intrusion Detection System Sensor (IDSS) . . . . . . . . . . . . . . . . 8-9
Network Security Operations and Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
Antivirus Subscription Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
Chapter 9: Advanced Call Processing

Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Static User Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Default Access and Default Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Using Default Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
Identification Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
Home Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7
Radio Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7
Radio User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8
Data User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
Configuration Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
Talkgroup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
Multigroup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11
System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
Source Site Adjacent Control Channel Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14
Dynamic User Tracking/Mobility Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
Mobility Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
Mobility as Viewed by the Radio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
Mobility as Viewed by the Fixed Network Equipment . . . . . . . . . . . . . . . . . . . . . . . . 9-23
How the Location Registers are Created . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-23
Tracking Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-25
Interzone Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-27
Controlling Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-29
Call Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-32
Call Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-32
Group-Based Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-32
Talkgroup Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-33
Intrazone Talkgroup Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-33
Interzone Talkgroup Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-38
6881009Y05-O April 2004 ix

Contents
Multigroup Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-42

Channel Marker for Talkgroup Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-43
Channel Marker and Alert Tone Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-44
Emergency Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-44
Emergency Alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-45
Emergency Call. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-45
Individual Call Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-46
Unit-to-Unit Call Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-46
Intrazone Unit-to-Unit Audio Flow, Call Continuation, and Teardown . . . . . . . . . . . . . . . . 9-49
Interzone Unit-to-Unit Audio Flow, Call Continuation, and Teardown . . . . . . . . . . . . . . . . 9-49
Roaming During a Unit-to-Unit Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-50
Telephone Interconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-50
Relationship Between Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-51
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-52
Call Initiation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-57
Telephone Interconnect Call Continuation/Call Maintenance . . . . . . . . . . . . . . . . . . . . . 9-58
Telephone Interconnect Call Termination and Call Teardown. . . . . . . . . . . . . . . . . . . . . 9-58
Roaming During a Telephone Interconnect Call . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-59
Busy Call Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-60
Priority Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-61
Group Call Busies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-61
AllStart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-61
FastStart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-62
Unit-to-Unit Call Busies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-62
Typical Reasons for Rejects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-62
Effects of Loss of Service on Call Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-63
Loss of Service Within a Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-64
Loss of Service Between Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-64
Conditions Necessary for Interzone Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-65
Interzone Group Service Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-66
Interzone Individual Service Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-67
Zone Controller Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-69
Automatic Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-70
Ethernet Card Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-71
Ethernet Transition Card Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-71
Manual Disable from the Local Admin Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-72
CPU Card Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-72
Devices That Do Not Cause Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-72
User-Initiated Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-73
System Behavior During Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-73
Possible Call Processing Behavior During Recovery. . . . . . . . . . . . . . . . . . . . . . . . . 9-75
Switching Back to the Standby Controller (User Initiated) . . . . . . . . . . . . . . . . . . . . . . 9-76
Zone Controller States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-77
Chapter 10: Integrated Voice and Data

Integrated Voice & Data Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
Packet Data Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Trunked Data Service Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
IV&D Hardware Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Zone Controller and IV&D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
Zone Controller and Air Traffic Information Access Data Call Information. . . . . . . . . . . . . 10-4
Packet Data Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Packet Data Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Radio Network Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
x 6881009Y05-O April 2004

GPRS Gateway Support Node Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6

Site Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
Mobile Subscriber Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7
Integrated Voice and Data Theory of Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8
Context Management for Data Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8
Context Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
Context Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
Context Deactivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
Accessing the PDCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
Requested Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
Autonomous Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
Inbound and Outbound Data Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10
Inbound Data Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10
Outbound Data Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11
IV&D Fault Management Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12
IV&D Configuration Management Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13
Data System Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13
PDCH Resource Allocation and Data Service Timers . . . . . . . . . . . . . . . . . . . . . . . . . 10-14
Subscriber Radios Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16
Packet Data Gateway Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17
Packet Data Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17
Radio Network Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-18
GGSN Router Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-18
Simulcast Site Steering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19
Chapter 11: Other Band Trunking

800 MHz Frequency Band Plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
OBT Frequency Band Plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
Developing the OBT Band Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
Structured Band Plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
Unstructured Band Plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8
Creating the Band Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9
Mixed Band Plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10
Creating the Band Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10
Infrastructure Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-15
User Configuration Manager Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-15
Sub-Band Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-15
Configuring a Channel as a Sub-band Channel . . . . . . . . . . . . . . . . . . . . . . . . . . 11-16
UCS Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-16
Call Processing in OBT Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-17
Wide Area Call Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-17
Talkgroup Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-17
Multigroup Call. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-18
Group Regrouping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-18
Patch Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-19
Private Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-19
Emergency Alarm and Emergency Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-19
Dynamic Regrouping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-20
Interconnect Calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-20
Site Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-20
Failsoft . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-21
Private Call Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-21
Different Zone Private Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-22
6881009Y05-O April 2004 xi

Contents
Chapter 12: Introduction to the FCAPS Model and PRNM

System Objectives And Framework. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
Private Radio Network Management System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
Client/Server Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
Windows Based Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
Client Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
Network Management System Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
Function Of PRNM System Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
Zone-Level Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
System-Level Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
Core Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
FCAPS Model in ASTRO 25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8
Configuration Management Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8
Accounting Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9
Air Traffic Information Access Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9
System-Level Air Traffic Information Access Packets . . . . . . . . . . . . . . . . . . . . . . . . 12-9
Air Traffic Information Access Logger and Log Viewer . . . . . . . . . . . . . . . . . . . . . . . 12-9
Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9
Zone Historical Reports Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10
System-Wide Historical Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10
Dynamic Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10
Zone Watch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10
Affiliation Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10
Security Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11
User Client Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11
Security Partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11
Chapter 13: Introduction to Network Management Applications

Topics in this Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1
Overview of Network Management Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1
FCAPS Designation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
Motorola PRNM Suite Applications Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
Transport Network Management Applications Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
Other Motorola Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6
Private Radio Network Management Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6
Application Launcher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
Application Launcher Menu and Explorer Window . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
Why Use Application Launcher? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8
Application Launcher Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8
Using Application Launcher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8
Affiliation Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-15
Why Use Affiliation Display? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-16
Affiliation Display Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-16
Other Sources of Information on Affiliation Display. . . . . . . . . . . . . . . . . . . . . . . . 13-17
ATIA Log Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-18
Why Use ATIA Log Viewer? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-18
ATIA Log Viewer Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-19
Other Sources of Information on ATIA Log Viewer . . . . . . . . . . . . . . . . . . . . . . . . 13-19
Configuration/Service Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-19
Why Use CSS? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-20
CSS Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-21
Other Sources of Information on CSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-22
xii 6881009Y05-O April 2004

Custom Historical Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-23

Why Use Custom Historical Reports? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-23
Custom Historical Reports Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-23
Other Sources of Information on Custom Historical Reports . . . . . . . . . . . . . . . . . . . . 13-25
Dynamic Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-25
Why Use Dynamic Reports? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-26
Dynamic Reports Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-26
Other Sources of Information on Dynamic Reports . . . . . . . . . . . . . . . . . . . . . . . . 13-28
FullVision INM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-28
HP OpenView Network Node Manager and FullVision INM . . . . . . . . . . . . . . . . . . . . 13-29
Why Use FullVision INM? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-29
FullVision INM Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-29
Other Sources of Information on FullVision INM . . . . . . . . . . . . . . . . . . . . . . . . . 13-32
Historical Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-32
Why Use Historical Reports? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-33
Historical Reports Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-33
Other Sources of Information on Historical Reports . . . . . . . . . . . . . . . . . . . . . . . . 13-35
MOSCAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-35
Why Use MOSCAD? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-37
MOSCAD Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-37
Other Sources of Information on MOSCAD . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-38
Radio Control Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-38
Why Use RCM? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-39
RCM Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-40
Other Sources of Information on RCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-43
Radio Control Manager Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-43
Why Use RCM Reports? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-44
RCM Reports Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-44
Other Sources of Information on RCM Reports . . . . . . . . . . . . . . . . . . . . . . . . . . 13-46
Router Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-46
Why Use Router Manager? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-48
Router Manager Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-48
Other Sources of Information on Router Manager . . . . . . . . . . . . . . . . . . . . . . . . . 13-51
Software Download Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-52
Why Use Software Download? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-52
Software Download Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-52
Other Sources of Information on Software Download . . . . . . . . . . . . . . . . . . . . . . . 13-53
System Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-54
Why Use System Profile? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-54
System Profile Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-54
Other Sources of Information on System Profile. . . . . . . . . . . . . . . . . . . . . . . . . . 13-55
User Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-55
Why Use User Configuration Manager? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-56
User Configuration Manager Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-56
Other Sources of Information on User Configuration Manager . . . . . . . . . . . . . . . . . . . 13-57
Zone Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-57
Why Use Zone Configuration Manager? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-58
Zone Configuration Manager Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-58
Other Sources of Information on Zone Configuration Manager . . . . . . . . . . . . . . . . . . . 13-59
Zone Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-60
Why Use Zone Profile? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-60
Zone Profile Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-60
Other Sources of Information on Zone Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . 13-61
Zone Watch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-61
Why Use Zone Watch? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-62
6881009Y05-O April 2004 xiii

Contents
Zone Watch Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-63

Other Sources of Information on Zone Watch . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-64
Transport Network Management Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-65
Accessing the Transport Network Management Applications from the Start Menu . . . . . . . . . . . . 13-65
Accessing the Transport Network Management Applications from the Desktop Icons . . . . . . . . . . 13-66
CiscoWorks2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-67
Why Use CiscoWorks2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-69
CiscoWorks2000 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-70
Other Sources of Information on CiscoWorks2000 . . . . . . . . . . . . . . . . . . . . . . . . 13-72
Preside Multiservice Data Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-72
Why Use Preside MDM? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-73
Preside MDM Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-73
Other Sources of Information on Preside MDM . . . . . . . . . . . . . . . . . . . . . . . . . . 13-75
InfoVista . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-75
Why Use InfoVista?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-76
InfoVista Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-76
Other Sources of Information on InfoVista . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-77
Appendix A: Power Supply Reference
Appendix B: ASTRO 25 System Documentation

ASTRO 25 Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
xiv 6881009Y05-O April 2004

List
of
Figures
List of Figures

Figure 1-1: Basic Radio System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Figure 1-2: Fixed Equipment Base Station with Microphone, Speaker, and Antenna. . . . . . . . . . . . . . 1-3
Figure 1-3: Antenna Height and Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Figure 1-4: Radio Frequency Spectrum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Figure 1-5: Simplex Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Figure 1-6: Limitations of a Single Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Figure 1-7: Half-Duplex Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Figure 1-8: Conventional Dispatch System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Figure 1-9: Conventional Simulcast Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Figure 1-10: Single Site Trunked System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Figure 1-11: Subscriber to Repeater Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Figure 1-12: Conventional Radio System Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
Figure 1-13: Example: How a Conventional System Works . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Figure 1-14: Example: How a Trunked Radio System Works . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
Figure 1-15: Trunked Radio System Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
Figure 1-16: Example: Organization of Users in a Talkgroup . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Figure 1-17: Example: Organization of Talkgroups in Multigroups . . . . . . . . . . . . . . . . . . . . . . 1-22
Figure 1-18: Basic Single-Site Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23
Figure 1-19: Service Request. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24
Figure 1-20: Controller Receives Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24
Figure 1-21: Controller Sends Outbound Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25
Figure 1-22: Subscribers Receive Channel Grant Information . . . . . . . . . . . . . . . . . . . . . . . . 1-25
Figure 1-23: Subscribers Switch to Voice Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26
Figure 1-24: Receiving Radios at Voice Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26
Figure 1-25: Transmitting Radio at Voice Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27
Figure 1-26: Call in Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27
Figure 1-27: End of Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28
Figure 1-28: Return to Control Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28
Figure 1-29: Trunked Simulcast System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-32
Figure 1-30: Radio Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34
Figure 1-31: Master Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-35
Figure 1-32: Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-36
Figure 1-33: Wide Area Trunking Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-36
Figure 1-34: Example: Multiple Zone System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-38
Figure 1-35: Multiple Zone System - Conditions for Interzone Trunking . . . . . . . . . . . . . . . . . . . 1-39
Figure 2-1: Call Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Figure 2-2: ASTRO 25 System Logical Traffic Planes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Figure 2-3: Call Processing Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Figure 2-4: Network Management Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Figure 2-5: Console Operator Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Figure 2-6: ASTRO 25 Repeater Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Figure 2-7: Simulcast Prime Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
6881009Y05-O April 2004 xv

List of Figures
Figure 2-8: Simulcast Remote Site for the Simulcast Subsystem Supporting 700 MHz, 800 MHz or VHF/UHF
Bands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Figure 2-9: Telephone Interconnect Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Figure 2-10: Data Communication Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Figure 2-11: Network Security Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Figure 3-1: Switched Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Figure 3-2: Balanced Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Figure 3-3: TCP/IP Protocol Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Figure 3-4: T1 Carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Figure 3-5: E1 Carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Figure 4-1: ASTRO 25 Master Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Figure 4-2: MZC 3000 Zone Controller - Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Figure 4-3: MZC 3000 Zone Controller Components - Front View . . . . . . . . . . . . . . . . . . . . . . . 4-6
Figure 4-4: MZC 3000 Zone Controller - Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Figure 4-5: CPU Card and Transition Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Figure 4-6: Ethernet Card and Transition Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Figure 4-7: Alarm Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Figure 4-8: Gateway Router with ST6011 (FlexWAN) Module . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Figure 4-9: Core and Exit Router With ST6012 (T3/HSSI) Module . . . . . . . . . . . . . . . . . . . . . . 4-17
Figure 4-10: GGSN Router (S6000 Base Router) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Figure 4-11: Ethernet LAN Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Figure 4-12: WAN Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Figure 4-13: Control Processor Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
Figure 4-14: Function Processor - HSSI Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
Figure 4-15: Channelized, 4 Port, T1 or E1 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
Figure 4-16: Unchannelized, 8 Port, T1 or E1 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
Figure 4-17: Channelized or Unchannelized, 32 Port T1 Module . . . . . . . . . . . . . . . . . . . . . . . 4-29
Figure 4-18: DS1/E1 WAN Switch Interface Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
Figure 4-19: MSA WAN Switch Interface Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
Figure 4-20: DS1C 4P FP Card and WAN Switch Interface Panel - Fast Failover . . . . . . . . . . . . . . . 4-33
Figure 4-21: DS1 8P FP Card and WAN Switch Interface Panel - Fast Failover . . . . . . . . . . . . . . . . 4-34
Figure 4-22: DS1 32P MSA FP and WAN Switch Interface Panel - Fast Failover . . . . . . . . . . . . . . . 4-35
Figure 4-23: WAN Switch Configuration Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
Figure 4-24: Zhone Arca-DACS 100 Digital Cross-connect Switch . . . . . . . . . . . . . . . . . . . . . . 4-38
Figure 4-25: Packet Data Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44
Figure 4-26: PRNM System-Level Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52
Figure 4-27: Private Radio Network Manager Zone Level Servers . . . . . . . . . . . . . . . . . . . . . . 4-54
Figure 4-28: TRAK 9100 Network Time Reference - Front View . . . . . . . . . . . . . . . . . . . . . . . 4-57
Figure 4-29: TRAK 9100 Network Time Reference - Rear View . . . . . . . . . . . . . . . . . . . . . . . 4-57
Figure 4-30: In-Reach Server - Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58
Figure 4-31: In-Reach Server (40 port) - Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58
Figure 4-32: Motorola Gold Elite Gateway - Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-60
Figure 4-33: Voice Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64
Figure 4-34: Secure Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-65
Figure 4-35: E1 Line Card and E1 Transition Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-66
Figure 4-36: System Monitor Board (Alarm Card) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-67
Figure 4-37: Single Board Computer / CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68
Figure 4-38: Motorola Gold Elite Gateway - Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-69
Figure 4-39: Ambassador Electronics Bank . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-71
Figure 4-40: AEB Communication Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-71
Figure 4-41: Ambassador Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74
Figure 4-42: System Timer Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-75
Figure 4-43: Central Electronics Bank . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-77
Figure 4-44: Central Electronics Bank Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-78
Figure 4-45: Console Interface Electronics Unit - Front View. . . . . . . . . . . . . . . . . . . . . . . . . 4-80
xvi 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System List of Figures
Figure 4-46: Console Interface Electronics Unit - Rear View . . . . . . . . . . . . . . . . . . . . . . . . . 4-80

Figure 4-47: HP 2524 Procurve Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82
Figure 4-48: HP 2626 Procurve Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82
Figure 4-49: Elite Console LAN with Ethernet Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-83
Figure 4-50: Telephone Interconnect Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-84
Figure 4-51: Adjunct Control Signaling Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-85
Figure 4-52: Avaya PBX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-87
Figure 4-53: Core Security Management Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-90
Figure 4-54: Network Interface Barrier Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-91
Figure 4-55: Intrusion Detection System Sensor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-92
Figure 4-56: XTS 5000 Portable Radio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-95
Figure 4-57: ASTRO 25 Radio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-96
Figure 5-1: Single Router, Single Switch Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Figure 5-2: Single Router, Dual Ethernet Switch ASTRO 25 Repeater Site . . . . . . . . . . . . . . . . . . . 5-8
Figure 5-3: Dual Router, Dual Switch ASTRO 25 Repeater Site . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Figure 5-4: DS1 8P FP Card and WAN Switch Interface Panel - Redundant Interface . . . . . . . . . . . . . 5-10
Figure 5-5: QUANTAR ASTRO 25 Site Repeater, 800 MHz Version - Front View . . . . . . . . . . . . . . . 5-12
Figure 5-6: QUANTAR ASTRO 25 Site Repeater, UHF Version - Front View . . . . . . . . . . . . . . . . . 5-12
Figure 5-7: STR 3000 ASTRO 25 Site Repeater 700 MHz . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Figure 5-8: LED Indicators on Control Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Figure 5-9: PSC 9600 Site Controller - Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Figure 5-10: PSC 9600 - Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
Figure 5-11: HP 2524 Prime Site Ethernet Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
Figure 5-12: HP 2626 Prime Site Ethernet Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
Figure 5-13: LED Select Button and Indicator LEDs HP 2524 . . . . . . . . . . . . . . . . . . . . . . . 5-26
Figure 5-14: HP 2626 Ethernet Switch LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
Figure 5-15: Motorola Network Router S2500 Site Router . . . . . . . . . . . . . . . . . . . . . . . . 5-30
Figure 5-16: IntelliRepeater Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
Figure 5-17: QUANTAR IntelliRepeater, 800 MHz Receiver - Front View . . . . . . . . . . . . . . . . . . 5-34
Figure 5-18: Simulcast Prime Site Without Colocated Remote Site . . . . . . . . . . . . . . . . . . . . . . 5-41
Figure 5-19: Simulcast Prime Site With Colocated Remote Site. . . . . . . . . . . . . . . . . . . . . . . . 5-42
Figure 5-20: Terminal Server Out-of-Band Management at the Simulcast Prime Site . . . . . . . . . . . . 5-43
Figure 5-21: Prime Site Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44
Figure 5-22: MTC 9600 - Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45
Figure 5-23: ASTRO-TAC 9600 - Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-47
Figure 5-24: HP 2524 Procurve Prime Site Ethernet Switch . . . . . . . . . . . . . . . . . . . . . . . . . 5-50
Figure 5-25: LED Select Button and Indicator LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51
Figure 5-26: Prime Site Router - Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52
Figure 5-27: Channel Bank - Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54
Figure 5-28: Channel Bank - Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55
Figure 5-29: Prime and Remote Site TRAK 9100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-57
Figure 5-30: Simulcast Remote Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-60
Figure 5-31: STR 3000 Base Radio 700 MHz or 800 MHz . . . . . . . . . . . . . . . . . . . . . . . . 5-61
Figure 5-32: LED Indicators on Control Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-62
Figure 5-33: STR 3000 Base Station 800 MHz . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-64
Figure 5-34: STR 3000 Base Station 700 MHz . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-65
Figure 5-35: QUANTAR Base Station, UHF Version - Front View . . . . . . . . . . . . . . . . . . . . . . 5-66
Figure 5-36: Remote Site Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-66
Figure 5-37: HP 2524 Procurve Remote Subsite Ethernet Switch . . . . . . . . . . . . . . . . . . . . . . . 5-67
Figure 5-38: Simulcast Remote Subsite Channel Bank . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-68
Figure 5-39: CSS Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-70
Figure 5-40: SWDL in PRNM Application Launcher . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-70
Figure 5-41: Single Transmit Remote Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-76
Figure 5-42: QUANTAR Base Station, UHF Version - Front View . . . . . . . . . . . . . . . . . . . . . . 5-77
Figure 5-43: Receive Only Remote Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-78
6881009Y05-O April 2004 xvii

List of Figures
Figure 5-44: QUANTAR Satellite Receiver, UHF Version - Front View . . . . . . . . . . . . . . . . . . . . 5-79
Figure 5-45: ASTROTAC Receiver, UHF Version Front View . . . . . . . . . . . . . . . . . . . . . . 5-79
Figure 5-46: CSS ASTRO-TAC 9600, SubSite Configuration Tab . . . . . . . . . . . . . . . . . . . . . 5-81
Figure 5-47: Simulcast Prime Site with 10Base-2 LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-82
Figure 5-48: Simulcast Subsystem Remote Subsite with 10Base-2 LAN. . . . . . . . . . . . . . . . . . . . 5-83
Figure 6-1: Mutual Aid with Colocated CEB - Inbound Call . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Figure 6-2: Mutual Aid with Colocated CEB - Outbound Call . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Figure 6-3: Master Site CEB with Digital Mutual Aid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Figure 6-4: STR 3000 Digital Mutual Aid Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Figure 6-5: Control Module and LED Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
Figure 6-6: DIU - Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Figure 6-7: Channel Bank . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
Figure 6-8: Channel Bank - Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
Figure 6-9: QUANTAR Mutual Aid Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
Figure 6-10: Channel Bank . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
Figure 6-11: Channel Bank - Rear View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17
Figure 6-12: ASTRO 25 Site Repeater Subsystem With 18 Channels and Single Site Link . . . . . . . . . . . 6-19
Figure 6-13: ASTRO 25 Repeater Site With 28 Channels and Single Site Link. . . . . . . . . . . . . . . . . 6-20
Figure 6-14: ASTRO 25 Repeater Site With 28 Channels and Redundant Site Links . . . . . . . . . . . . . . 6-21
Figure 6-15: Simulcast Prime Site With Single Repeater Mutual Aid . . . . . . . . . . . . . . . . . . . . . 6-22
Figure 6-16: Simulcast Prime Site With Conventional Mutual Aid Simulcast System. . . . . . . . . . . . . . 6-23
Figure 6-17: Simulcast Prime Site With Redundant Site Routers and Mutual Aid . . . . . . . . . . . . . . . 6-24
Figure 6-18: Simulcast Remote Subsite With Mutual Aid . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25
Figure 6-19: Channel Bank - Simulcast Subsite With Analog Mutual Aid . . . . . . . . . . . . . . . . . . . 6-26
Figure 7-1: Subscriber Information Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Figure 7-2: UCS to Location Registers Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Figure 7-3: Information Flow for Infrastructure Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
Figure 7-4: Flow of Information to/from ATR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
Figure 7-5: Server Interactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
Figure 8-1: Network Security Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Figure 8-2: Core Security Management Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Figure 8-3: Network Interface Barrier Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
Figure 8-4: Intrusion Detection System Sensor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
Figure 9-1: UCM Home Zone Mapping Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7
Figure 9-2: Registration and Affiliation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
Figure 9-3: Adjacent Site Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19
Figure 9-4: Home Location Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24
Figure 9-5: Home Location Register - Visitor Location Register . . . . . . . . . . . . . . . . . . . . . . . 9-25
Figure 9-6: Multizone Call Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-28
Figure 9-7: Call Processing Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-31
Figure 9-8: Intrazone Talkgroup Request from an ASTRO 25 Repeater Site . . . . . . . . . . . . . . . . . . 9-34
Figure 9-9: Intrazone Talkgroup Request from Digital Simulcast Subsystem . . . . . . . . . . . . . . . . . . 9-35
Figure 9-10: Talkgroup Call Grant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-37
Figure 9-11: Interzone Call Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-40
Figure 9-12: Unit-to-Unit Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-47
Figure 9-13: Telephone Interconnect Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-51
Figure 9-14: Interconnect Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-54
Figure 9-15: Landline-to-Radio Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-56
Figure 9-16: Zone-to-Zone Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-65
Figure 9-17: Reduced Interzone Service Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-67
Figure 9-18: Interzone Individual Call with Radios in Their Home Zones . . . . . . . . . . . . . . . . . . . 9-68
Figure 9-19: Interzone Individual Call with Radios Not in Their Home Zones . . . . . . . . . . . . . . . . . 9-69
Figure 10-1: Integrated Voice and Data Communication Interface Diagram . . . . . . . . . . . . . . . . . 10-2
Figure 13-1: PRNM Applications from a System Perspective . . . . . . . . . . . . . . . . . . . . . . . . . 13-3
Figure 13-2: Application Launcher Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
xviii 6881009Y05-O April 2004

List of Figures
Figure 13-3: Example of the Explorer Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8

Figure 13-4: Motorola Private Radio Network Management Suite Icon . . . . . . . . . . . . . . . . . . . 13-10
Figure 13-5: Motorola PRNM Suite Login Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10
Figure 13-6: Windows Explorer Window (Displayed When Launcher Starts) . . . . . . . . . . . . . . . . 13-11
Figure 13-7: Motorola Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-11
Figure 13-8: Windows Explorer Window Used to Open Applications . . . . . . . . . . . . . . . . . . . . 13-12
Figure 13-9: Location of Zone-Level Applications on the Windows Explorer Window . . . . . . . . . . . . 13-13
Figure 13-10: Motorola PRNM Suite Menu Option on the Start Menu . . . . . . . . . . . . . . . . . . . 13-14
Figure 13-11: Example of the Affiliation Display Main Window . . . . . . . . . . . . . . . . . . . . . . 13-15
Figure 13-12: ATIA Log Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-18
Figure 13-13: Configuration/Service Software Main Window . . . . . . . . . . . . . . . . . . . . . . . 13-20
Figure 13-14: Dynamic Report Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-26
Figure 13-15: FullVision INM Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-28
Figure 13-16: Historical Reports (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-33
Figure 13-17: MOSCAD Submap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-36
Figure 13-18: MOSCAD GMC Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-37
Figure 13-19: Radio Control Manager Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-39
Figure 13-20: RCM Reports Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-44
Figure 13-21: Router Manager UI Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-47
Figure 13-22: Router Manager, HP OpenView. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-47
Figure 13-23: WEBLink Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-50
Figure 13-24: Software Download Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-52
Figure 13-25: System Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-54
Figure 13-26: User Configuration Manager Main Window . . . . . . . . . . . . . . . . . . . . . . . . . 13-55
Figure 13-27: Zone Configuration Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-57
Figure 13-28: Zone Profile Application Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-60
Figure 13-29: Zone Watch Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-62
Figure 13-30: Start Menu on the TNM Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-65
Figure 13-31: Start Menu on the PNM Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-66
Figure 13-32: Desktop Icons on the TNM Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-67
Figure 13-33: Desktop Icons on the PNM Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-67
Figure 13-34: CiscoWorks2000 with RME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-68
Figure 13-35: CiscoView Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-69
Figure 13-36: Preside MDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-73
Figure 13-37: MDMWeb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-74
Figure 13-38: InfoVista Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-76
6881009Y05-O April 2004 xix

List of Figures
This page intentionally left blank.
xx 6881009Y05-O April 2004

List
of
Tables
List of Tables

Table 2-1: RF Subsystem Frequency Bands Supported . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22

Table 2-2: ASTRO 25 System Audio Optimization Requirements. . . . . . . . . . . . . . . . . . . . . . . 2-23
Table 2-3: ASTRO 25 System Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
Table 2-4: ASTRO 25 System Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
Table 3-1: Network Cables and Link Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Table 4-1: I/O Modules for S6000 Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Table 4-2: Routers by Function with I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Table 4-3: I/O Modules for S2500 Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Table 4-4: S2500 Series Routers Function Description With I/O Modules . . . . . . . . . . . . . . . . . 4-14
Table 4-5: Ethernet Switching Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
Table 4-6: Network Analysis Module Status LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
Table 4-7: Power Supply Front Panel LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
Table 4-8: DS1/E1 WAN Switch Interface Panel - Port Access . . . . . . . . . . . . . . . . . . . . . . . . 4-31
Table 4-9: MGEG Card Placement - Front . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-62
Table 4-10: MGEG Card Placement - Rear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-63
Table 4-11: PBX Switch Interface Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-88
Table 4-12: Subscriber Radio Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94
Table 4-13: Components and UPS Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-97
Table 5-1: RF Subsystem Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Table 5-2: STR 3000 ASTRO 25 Site Repeater (700 MHz) Modules . . . . . . . . . . . . . . . . . . . . . 5-16
Table 5-3: LED Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Table 5-4: PSC 9600 Top Row LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Table 5-5: PSC 9600 LEDs Bottom Row . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Table 5-6: PSC 9600 Rear Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
Table 5-7: Mode LED Indicator LEDs HP 2524 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
Table 5-8: HP 2626 Switch Status LED Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
Table 5-9: HP 2626 Switch Port Mode LED Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
Table 5-10: Interfaces Supported by the Site Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
Table 5-11: Interfaces Supported by the Site Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
Table 5-12: LED Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-62
Table 5-13: System Operational Differences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-83
Table 6-1: 700 MHz Repeater Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Table 6-2: Control Module LED Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
Table 7-1: Summary of Database Administration Functions . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
Table 7-2: Hierarchical Listing of Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
Table 7-3: Subsystem Listing of Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15
Table 7-4: Server Interactions Defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
Table 7-5: Capacity Lost When Servers Fail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21
Table 7-6: UCS Administration Menu Items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25
Table 7-7: System Statistics Server Administration Menu Items . . . . . . . . . . . . . . . . . . . . . . . 7-25
Table 7-8: Database Server Administration Menu Items . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
Table 7-9: Zone Statistics Server Administration Menu Items. . . . . . . . . . . . . . . . . . . . . . . . . 7-27
6881009Y05-O April 2004 xxi

List of Tables
Table 7-10: Air Traffic Router Administration Menu Items . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28

Table 7-11: FullVision INM Server Administration Menu Items . . . . . . . . . . . . . . . . . . . . . . . 7-28
Table 9-1: Site Access Denial Set to Individual Only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
Table 9-2: Site Access Denial Set to Talkgroup Only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13
Table 9-3: Site Access Denial Set to Either . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13
Table 9-4: Site Access Denial Set to Both . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14
Table 9-5: Call Processing Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-29
Table 9-6: Zone Call Service States. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-64
Table 9-7: Levels of Group Service Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-66
Table 9-8: Failures That Cause Automatic Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-70
Table 9-9: Failures That Do Not Cause Automatic Switchover . . . . . . . . . . . . . . . . . . . . . . . . 9-71
Table 9-10: Call Processing Behavior During Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-75
Table 9-11: Zone Controller Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-78
Table 9-12: Zone Controller Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-78
Table 10-1: Packet Data Router and Radio Network Gateway FullVision INM Reporting . . . . . . . . . 10-12
Table 10-2: Data System Configuration Parameters User Configuration Manager . . . . . . . . . . . . . 10-13
Table 10-3: PDCH Resource Allocation Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-15
Table 10-4: Description of Data Service Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-15
Table 10-5: Subscriber Radio Configuration Parameters in CPS for IV&D . . . . . . . . . . . . . . . . . 10-16
Table 11-1: Analog 800 MHz Band Structure for Fixed Equipment . . . . . . . . . . . . . . . . . . . . . . 11-1
Table 11-2: ASTRO 25, 800 MHz Band Structure for Fixed Equipment . . . . . . . . . . . . . . . . . . . . 11-2
Table 11-3: ASTRO 25, 700 MHz Band Structure for Fixed Equipment . . . . . . . . . . . . . . . . . . . . 11-3
Table 11-4: Available Frequencies Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5
Table 11-5: Band Plan Element Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6
Table 11-6: Sample Band Plan as Programmed in Site Controllers and Radios . . . . . . . . . . . . . . . . . 11-7
Table 11-7: System Frequencies UHF and VHF Bands . . . . . . . . . . . . . . . . . . . . . . . . . 11-11
Table 11-8: UHF Frequencies Grouped by Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11
Table 11-9: VHF Frequencies Grouped by Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12
Table 11-10: Elements Needed to Cover the VHF Band . . . . . . . . . . . . . . . . . . . . . . . . . . 11-13
Table 11-11: VHF Frequencies with Channel Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . 11-14
Table 11-12: Assigning Band Plan Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-15
Table 11-13: Site with Single Sub-band Channel Operating as Control Channel . . . . . . . . . . . . . . . 11-18
Table 11-14: Target and Initiator in the Same Zone Different Sites . . . . . . . . . . . . . . . . . . . . 11-21
Table 11-15: Target and Initiator in Different Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-22
Table 13-1: Motorola PRNM Suite Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3
Table 13-2: Transport Network Management Applications . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
Table 13-3: Other Motorola Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6
Table 13-4: Other Information for Application Launcher . . . . . . . . . . . . . . . . . . . . . . . . . . 13-15
Table 13-5: Related Information for Affiliation Display . . . . . . . . . . . . . . . . . . . . . . . . . . 13-17
Table 13-6: Other Information for ATIA Log Viewer. . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-19
Table 13-7: Devices Programmed Using CSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-20
Table 13-8: Other Information for CSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-22
Table 13-9: Other Information for Custom Historical Reports. . . . . . . . . . . . . . . . . . . . . . . . 13-25
Table 13-10: Other Information for Dynamic Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-28
Table 13-11: Other Information for FullVision INM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-32
Table 13-12: Zone-Level and System-Level Objects Stored by Interval . . . . . . . . . . . . . . . . . . . 13-35
Table 13-13: Other Information for Historical Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-35
Table 13-14: Other Information for MOSCAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-38
Table 13-15: Radio Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-41
Table 13-16: Other Information for RCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-43
Table 13-17: Types of Emergency Alarms Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-45
Table 13-18: Types of Radio Command Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-45
Table 13-19: Other Information for RCM Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-46
Table 13-20: Other Information for Router Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-51
Table 13-21: Other Information for Software Download . . . . . . . . . . . . . . . . . . . . . . . . . . 13-53
xxii 6881009Y05-O April 2004

List of Tables
Table 13-22: Other Information for System Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-55

Table 13-23: High-Level Objects in UCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-56
Table 13-24: Other Information for User Configuration Manager . . . . . . . . . . . . . . . . . . . . . . 13-57
Table 13-25: High-Level Objects in ZCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-58
Table 13-26: Other Information for Zone Configuration Manager . . . . . . . . . . . . . . . . . . . . . . 13-59
Table 13-27: Other Information for Zone Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-61
Table 13-28: Watch Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-63
Table 13-29: Other Information for Zone Watch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-64
Table 13-30: Start Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-65
Table 13-31: Desktop Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-67
Table 13-32: Status Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-70
Table 13-33: Key Features of RME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-71
Table 13-34: Other Information for CiscoWorks2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-72
Table 13-35: Other Information for Preside MDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-75
Table 13-36: Other Information for InfoVista . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-77
Table A-1: Component Power Supply Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Table B-1: ASTRO 25 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Table B-2: Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
6881009Y05-O April 2004 xxiii

List of Tables
xxiv 6881009Y05-O April 2004

List
of
Procedures
List of Procedures

Procedure 11-1: How to Create an Unstructured Band Plan . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9

Procedure 13-1: How to Start Application Launcher . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10
Procedure 13-2: How to Open an Application from the Windows Explorer Window . . . . . . . . . . . . . 13-12
Procedure 13-3: How to Open an Application from the Start Menu . . . . . . . . . . . . . . . . . . . . . 13-14
6881009Y05-O April 2004 xxv

List of Procedures
xxvi 6881009Y05-O April 2004

List
of
Processes
List of Processes

Process 9-1: Channel Marker Distribution Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-44

Process 10-1: Inbound Data Request Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10
Process 10-2: Outbound Data Request Requested Access . . . . . . . . . . . . . . . . . . . . . . . . 10-11
Process 11-1: Creating a Structured Band Plan VHF/UHF . . . . . . . . . . . . . . . . . . . . . . . . . 11-5
Process 11-2: Creating a Mixed Band Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10
6881009Y05-O April 2004 xxvii

List of Processes
xxviii 6881009Y05-O April 2004

About
This
Manual
Understanding Your ASTRO 25 Trunking

System

This book provides radio system concepts and basic reference and component information.
The purpose of this book is to:
Describe the basic radio system concepts and call processing basics.
Provide an introduction to the various components and processes associated
with the ASTRO 25 system.
Perform as a base document for all other ASTRO 25 documentation volumes.
This booklet is intended to be used by field service managers and field service technicians after they have
attended the Motorola formal ASTRO 25 release training (including all multimedia presentations).
What is Covered In This Manual?

Chapter 1, "Radio System Concepts." This chapter provides an introduction
to the basic concepts of conventional radio systems and Motorola trunked radio
systems. The discussion of trunked systems includes only legacy systems that
use SMARTNET and SmartZone technology.
Chapter 2, "What Is an ASTRO 25 Trunking System?." This chapter discusses
basic structure and call processing of an ASTRO 25 system.
Chapter 3, "Network Topology." This chapter discusses network concepts
applicable to an ASTRO 25 system.
Chapter 4, "Hardware Functional Description." This chapter discusses the hardware
associated with an ASTRO 25 system master site.
Chapter 5, "Radio Frequency Subsystems." This chapter discusses the hardware
associated with an ASTRO 25 system remote site.
Chapter 6, "ASTRO 25 Systems and Mutual Aid." This chapter discusses the
hardware associated with mutual aid in an ASTRO 25 system.
Chapter 7, "Databases, Servers, and Controllers." This chapter presents an overview
of the databases, servers, and controllers found in the ASTRO 25 system.
Chapter 8, "Network Security." This chapter provides an overview of the network
security features for your ASTRO 25 radio and data communication system.
Chapter 9, "Advanced Call Processing." This chapter presents an overview of call processing,
which takes place at the master site equipment of an ASTRO 25 system.
Chapter 10, "Integrated Voice and Data." This chapter provides an overview of the integrated
voice and data features of your ASTRO 25 radio and data communication system.
6881009Y05-O April 2004 xxix

About This Manual
Chapter 11, "Other Band Trunking." This chapter discusses the structure of
other band trunking band plans and call processing.
Chapter 12, "Introduction to the FCAPS Model and PRNM." This chapter presents
an overview of the FCAPS model as described by The International Organization for
Standardization (ISO). In addition, it discusses Private Radio Network Management (PRNM)
and its software applications or tools used to manage the ASTRO 25 system.
Chapter 13, "Introduction to Network Management Applications." This chapter
presents an overview of the Network Management Software Tools that support the
management of the ASTRO 25 system and its component parts, which include
radios, computers, and inter-networking components.
Appendix A, "Power Supply Reference." This appendix contains information on
power supply characteristics for ASTRO 25 system components.
Appendix B, "ASTRO 25 System Documentation." This appendix contains information
on related ASTRO 25 system documentation, including third-party documentation.
For information on managing secure communications including information on the Key

Management Facility (KMF) and Key Variable Loader (KVL), see ASTRO 25 Trunked Integrated
Voice and Data System Release 6.4/6.4 SE Managing Secure Communications (6881009Y65).
Helpful Background Information

You will find this volume most helpful if you have already done the following:
Attended the Motorola Worldwide Learning Services (WLS) formal ASTRO
25 trunking training (including all multimedia presentations) to learn the
operating principles of ASTRO 25 trunking.
xxx 6881009Y05-O April 2004

Chapter
1
Radio System Concepts

Radio systems provide a convenient and timely method of communication for people engaged in various
public safety-related, transportation, and service occupations. Radio systems differ in design based on the
needs of the individual users. One radio system might support a towing company with a dispatcher and two
tow trucks communicating back and forth. Another radio system might support a public utility company
with a network of antenna towers, control sites, and field personnel scattered across a wide geographic
area. The type of radio system that you have depends on the needs of your organization.
Regardless of the type of radio system, knowledge of basic radio system concepts will help you
understand how your system works. It will also provide you with an appreciation, from a historical
perspective, regarding the development of newer technologies for radio systems.
This chapter provides an introduction to basic radio system concepts and includes the following topics:
"What Is a Radio System?" on page 1-1
"Motorola Trunked Systems" on page 1-11
"Motorola Single Site Trunked System" on page 1-12
"Multiple Site Trunked Systems" on page 1-31
"Multiple Zone Systems" on page 1-37
What Is a Radio System?

A radio uses electromagnetic waves to send information across the air. This is accomplished by producing
an electrical signal that moves back and forth, or oscillates, at a rapid rate.
The rate at which a radio signal oscillates back and forth is called its frequency and is measured in Hertz
(Hz). Most radio frequencies are in millions of Hertz, or Megahertz (MHz), per second.
Basic Radio System Components
A basic radio system consists of equipment for transmitting and receiving radio signals
that are used to carry voice (audio) or data.
6881009Y05-O April 2004 1-1

Radio System Equipment Chapter 1: Radio System Concepts
To handle voice, an audio signal from a microphone is combined, or modulated, with a radio carrier signal then
amplified by the transmitter. The modulated radio signal, when sent to an antenna, radiates the signal into the air.
The radiated signal is picked up by a receiving antenna and sent to a receiver. Here the radio signal
is processed back into the original audio signal, which is fed into a speaker so that the original voice
message can be heard. Figure 1-1 shows the components of a basic radio system.
Figure 1-1 Basic Radio System
Radio System Equipment

Two-way radio equipment can be classified as either fixed, mobile, or portable. Each one of
these units includes a transmitter, receiver, and antenna system.
Fixed equipment is located at a central site such as an office or a headquarters, and usually consists of a base
station, microphone, and antenna. The base station is used to transmit the signal generated through the
microphone to portable and mobile equipment located at some distance. The range of the base station depends
on its power, antenna system, terrain, and environmental conditions. Figure 1-2 shows fixed equipment.
1-2 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Radio System Range and Frequency Spectrum
Figure 1-2 Fixed Equipment Base Station with Microphone, Speaker, and Antenna
Fixed stations can have three types of control:

Local Control A local control base station is used when the dispatchers
position is close to the antenna site.
Extended Local Control An extended local control base station is used when the
dispatch point is up to 1000 feet from the base station. The transmitter and receiver
are located near the antenna site, the base station controls are in a separate unit at the
dispatchers position and connected to the equipment using a wireline cable.
Remote Control Remote control is used when the base station is located more than
1000 feet from the dispatch position. Leased telephone lines or microwave links may be
used to connect the base station equipment with the dispatchers control unit.
The location of the base station control is generally known as the dispatch center.
A mobile unit is a radio that is mounted in either the trunk or under the dash of a vehicle. A portable
unit is a battery-powered radio that is small enough to be carried by a person.
Radio System Range and Frequency Spectrum

This section provides an introduction to the effect antenna systems have on coverage area and presents a chart
showing the frequency spectrum to serve as a point of reference for a trunking systems frequency band.
Radio System Range
The range of a radio system is affected by many different factors. One of the most critical coverage factors
is antenna height and location, because the range of a radio system is limited to the horizon as seen by
the radio antenna. In general, the range of a radio system depends on the effective height of the antenna.
The higher an antenna is installed, the greater an area receives coverage. See Figure 1-3.
6881009Y05-O April 2004 1-3

Spectrum Management Chapter 1: Radio System Concepts
Figure 1-3 Antenna Height and Coverage
Spectrum Management
Because frequency spectrum is a finite resource, the use of channels is authorized and licensed
by government agencies in most countries. In the United States, the Federal Communications
Commission (FCC) is charged with regulating communications by radio (both commercial
broadcast and two-way), television, wire, satellite, and cable.
International regulations fall under the jurisdiction of the International Telecommunications Union (ITU).
In all cases, a license to operate radio equipment is required and must be applied for with the
appropriate governing body. The license is granted to operate on a particular frequency, or set
of frequencies, with specific eligibility rules that must be met.
The frequency spectrum is presented in Figure 1-4.
1-4 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Communication Types
Figure 1-4 Radio Frequency Spectrum
Communication Types
Radio systems use any of three types of communication: simplex, half-duplex, and duplex. The
communication type used depends on the number of users and the type of equipment available.
This section provides a description of the three types of communication.
Simplex
The most basic type of radio communication is simplex. Simplex communication consists of radio units
operating on a single frequency. Because everyone transmits and receives on the same frequency, users cannot
talk and listen at the same time. Simplex means transmission in one direction at a time. See Figure 1-5.
6881009Y05-O April 2004 1-5

Simplex Chapter 1: Radio System Concepts
Figure 1-5 Simplex Communication
A simplex radio system works well when there are only a few users who are closely located. When
additional users are added to the system, the competition for the one available frequency can make it
difficult to get a message across. In addition, great distances and natural obstacles such as high hills
and tall buildings can interfere with the single frequency. See Figure 1-6.
Figure 1-6 Limitations of a Single Frequency
1-6 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Half-Duplex
Half-Duplex
Half-duplex communication uses two frequencies: one for receive and one for transmit. The system can
consist of a base station and a number of portable/mobile radios. In a half-duplex system, the radios
transmit on one frequency and receive on another. This arrangement allows for dispatcher control of the
system. The mobile and portable units cannot talk to or hear each other directly because their receivers are
operating on a different frequency from their transmitters; all communication takes place through the base
station. The dispatcher can hear any of the transmitting radios in the system. See Figure 1-7.
Figure 1-7 Half-Duplex Communication
Duplex
Duplex communication uses different frequencies simultaneously, one to transmit and the second
to receive. The transmitter output is isolated and separated in frequency to prevent blocking the
input of its companion receiver. Also called full-duplex, this type of operation is used to indicate
that the equipment can receive and transmit at the same time.
Normally, fixed equipment (a base station) operates in full-duplex mode while mobile
equipment typically operates in half-duplex mode.
Conventional Radio Systems
A conventional radio system can be as simple or complex as required to support the number of radio users
in a geographic area. The system can consist of a single repeater or base station and a number of portable
or mobile radios, a number of base stations to support a larger number of users in a single geographic
area (single site system), or a number of repeater sites (multiple site system) to increase coverage to a
wider geographic area. A radio system can include several or all of the following components:
6881009Y05-O April 2004 1-7

Repeater Systems Chapter 1: Radio System Concepts
Radios
Antennas
Telephone lines
Microwave links
The simplest type of system can consist of portable or mobile radios that communicate
with each other in point-to-point fashion. This type of system restricts communication
to the range of the radios transmitting capability.
Repeater Systems
A repeater is a type of base station remotely and strategically located to improve the area of radio coverage.
When the repeater receives a signal from a radio unit, it acts as a relay and retransmits the signal immediately.
Typically, a repeater operates in duplex mode, because it can transmit and receive at the same time.
A conventional repeater system consists of portable and/or mobile radios that use a repeater
to extend the range of communication. The repeater, with its high power transmitter and high
antenna location, receives the signal from the transmitting radio and immediately sends it to
the rest of the radios tuned to the repeaters transmit frequency.
In this type of system, the transmitting radio controls the repeater activation and deactivation time.
Also, while one radio is transmitting, other radios needing to use the system have to wait or they
can attempt to ruthlessly displace the currently transmitting radio.
Communication discipline becomes an important factor when several agencies or departments need to share
the repeater system. A number of repeaters can be installed to provide reliable radio access in this type of
environment but the portables and mobiles are still limited by the number of frequencies they can access and
the coordination required to accomplish a frequency switch by all members of a communication group.
Coverage range of this system is limited by the repeaters transmit power, the type of terrain,
and the transmit power of the portable or mobile.
In a repeater system, radios can be programmed with an additional transmit frequency, which is the same as
the repeaters transmitter frequency. This enables the radios to talk to one another without using any repeater
resources or to monitor the repeater for channel activity when the radio is in range. The radios can also
communicate with each other when out of range of the repeater. This operation is called Repeater Talkaround.
Dispatch System
A dispatch system can consist of a base station controlled from a central location or a number
of base stations connected to centralized control equipment. The common point of control
provides many advantages to a conventional system that include:
Control of communication equipment

In this type of system, all radios are tuned to the same frequency. Any radio user desiring to
communicate with other radio users calls the dispatch point to request access to a base station.
The dispatcher sends a voice message, through the common frequency, with instructions for
the group to switch to a specific frequency accessible from their radios. The affected users can
then switch their radios to the assigned frequency and proceed with their communication.
The rest of the radios in the system remain at the common frequency, thus preventing the
interference problems found in conventional systems without central control.
1-8 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Conventional Systems
Frequency patch capability

The centralized control equipment can include circuitry that allows the dispatcher
to connect (patch) the audio from two or more groups transmitting in different
frequencies. This particular function can be used when two or more groups, such
as police and fire, need to coordinate their activities.
Figure 1-8 Conventional Dispatch System
Conventional Systems
Conventional systems can contain subsystems that consist of a number of repeater sites installed
at strategic locations to improve the signal quality and to increase the distance that radios can
be from each other while still being able to communicate.
One type of subsystem has the capability to simultaneously transmit a signal through several
repeater sites without the patch operation in the dispatch system previously described. A radio
can be anywhere in the coverage area and is still able to receive or initiate a transmission. This
type of system has a number of requirements that include:
Common frequencies
The repeaters activated for a specific call at each site (different sites) must
transmit the signal using the same frequency since a portable or mobile can only
receive or transmit on one frequency at a time.
6881009Y05-O April 2004 1-9

Repeater Control Chapter 1: Radio System Concepts
Centralized audio distribution

The signal sent by a portable or mobile radio is picked up by the receiver at one of
the repeater sites. In order to distribute this signal to the other repeater sites, the
receiving repeater routes the signal to a comparator that can simultaneously send it to
multiple sites for transmission. This is known as simulcasting.
The portable or mobile signal may be picked up by more than one receiver in the system. In
this case, the centralized audio distribution system must be able to compare multiple signals
and select the signal with the best quality for distribution to the rest of the system. The
selection process is referred to as voting and the equipment is called a comparator.
A transport medium
The system requires the means to transport the audio signals from the repeater sites (remote
sites) to the centralized audio distribution equipment and back to the remote sites. The
transport medium can include telephone facilities, microwave links, and fiber optic links.
Simulcast is the term applied to subsystems designed to transmit a signal simultaneously

through a number of repeaters programmed with the same frequency. Figure 1-9 shows a
representation of a basic, conventional simulcast system.
Figure 1-9 Conventional Simulcast Subsystem
Repeater Control
Repeater control in conventional systems, single or multiple site, takes two forms:
Direct control by the radio

A carrier signal (transmit frequency) is generated when the push-to-talk (PTT) switch is
activated in the portable or mobile radio initiating the call. This carrier signal causes the repeater
to go into activate mode until the radio user releases the PTT. In some systems, a sub-audible
signal is transmitted with the carrier to provide better control of the repeaters activation.
1-10 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Trunking Technology
Dispatch control
The radio user calls the dispatcher through the common access frequency and requests
permission to access a repeater. The dispatcher transmits a voice message indicating the
assigned frequency. The radio user changes the frequency selector in the radio to the
appropriate position and, at this point, assumes control of the repeater.
Activation of repeaters that are under direct control of the dispatcher is usually accomplished
through tones generated by circuitry in the dispatch equipment.
Trunking Technology
Trunking is a term introduced in telephony to define the use of a limited number of resources
by a large number of users. The limited resources refers to the number of telephone lines that
can be used to connect a telephone switch that services one area, to another switch that provides
service to a different area. The telephones connected to the switches constitute the large number
of users requiring access to the lines connecting the switches.
The implementation of trunking in telephony required the means to control access to the switches as well as
the telephone lines between those switches. Manual and mechanical control of those functions were rapidly
outpaced by the tremendous growth in the number of telephones installed. A faster and more efficient method
of responding to requests for service and selecting routing paths for the calls had to be provided.
Modern telephone switches are built with the intelligence to automatically respond to a request for service
from a telephone (dial tone), interpret the routing path desired (telephone number), select the appropriate
resource (telephone line and destination switch), set up the audio path, interpret the disconnect signal,
and return the resources in use to the available pool when the call is terminated.
Trunking Technology and Radio Systems

The concept of trunking suggested a much more efficient way of handling communication in a radio system.
If the resource control function could be translated from the selection of telephone lines and switches to the
selection and control of repeaters, trunking radio systems could be used to solve many of the limitations
of conventional radio systems, particularly the efficient use of the repeater resources.
Motorola Trunked Systems

The Motorola implementation of trunking technology in a radio system involved the development
of an intelligent device that could accomplish the following tasks:
Interpret inbound requests for service from the radios

Verify that the radios were valid users of the system
Select the appropriate resource (repeater)
6881009Y05-O April 2004 1-11

Motorola Single Site Trunked System Chapter 1: Radio System Concepts
Formulate and send an outbound message to the radios indicating the assigned frequency
Send an activation signal to the assigned repeater
Monitor the resources to detect when they were no longer in use
Maintain a list of available resources
Maintain a list of assigned resources
Monitor the health of the repeaters and its own circuitry
Maintain a list of radios active in the system
Advise users when all resources were assigned and subsequently assign a
resource automatically when it became available
The intelligent device became the central point of control for the radio system and is known
as the central controller. Its control function is extended to the radios use of the system and
the system features the radio users are able to access.
Trunking technology implementation extended to the repeaters and radios that were to be used in the system.
The repeaters needed the circuitry and programming necessary to be able to communicate with the central
controller. The radios needed the circuitry and programming necessary to encode the service requests, decode
the assignment messages, and be able to generate any frequency in the system. Trunking technology removed
from the radios the ability to directly access and activate a repeater, and in return gave them the capability
to access any one of the repeaters in the system. Repeater control resides in the central controller.
The following sections describe the evolution of Motorola trunking technology from
single site systems to multiple zone systems.
Motorola Single Site Trunked System

The original Motorola single site trunked system came to be known by the name of its feature set,
SMARTNET. This section provides an introduction to the basics of a Motorola SMARTNET trunked system,
the radio system components, and their role in the system. Figure 1-10 shows a single site trunked system.
1-12 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Single Site Components
Figure 1-10 Single Site Trunked System
Single Site Components
This section describes the following components of a single site:
Subscribers
Central controller
Repeaters
Control channel
Voice channel
Subscribers
Subscribers are the mobile or portable radios and desktop units with multiple frequency capability. They
provide users with the ability to communicate in the system. Each one of these units is assigned a unique
identification number and contains the logic circuitry necessary to perform the following trunking functions:
Generate and transmit requests for service in the form of data words that are
then used to modulate the carrier frequency.
Interpret the data messages sent by the central controller.
Generate the frequency of the assigned voice channel.
Generate tones to advise the radio user of the status of the call request.
Each subscriber has a unique six-digit ID assigned that serves to identify the radio to the central controller.
IDs for subscribers in a single site trunked system range between 700001 and 765534.
6881009Y05-O April 2004 1-13

Central Controller Chapter 1: Radio System Concepts
Central Controller
The central controller processes inbound and outbound data traffic, assigns repeaters for voice channel
access, and generally monitors and maintains order in the system. The controller maintains a database
that keeps track of each radios Unit ID and the current talkgroups to radio affiliation.
The controller in a single site system performs the following call processing functions:
Services call requests

Recovers and decodes inbound signal requests
Maintains a database of active radios and their system permissions
Receives group affiliations
Checks call access privileges
Issues call grants
Monitors and controls each call sequence
Maintains a list of subscribers that are waiting for repeater assignments
Selects and assigns voice channels as required
Selects the control channel
Decodes sub-audible control signals originated by the subscriber
Generates and encodes the proper outbound signaling words for such purposes
as directing system users to specific channels
Generates the sub-audible data which is superimposed on all voice communications and is
used to unmute the audio circuitry in receivers authorized to monitor audio transactions
The original central controller is generally referred to as a 6809 controller because its control cards are
based on 6809 microprocessors. Sites that use this controller are referred to as 6809 sites.
Repeaters
A repeater is an RF station that serves as the RF link between the system and the mobiles and
portables. Repeaters in a SMARTNET trunked system are connected in a site configuration
with a minimum of two and a maximum of 28 repeaters.
Repeaters in a trunked system have three primary interfaces:
A receiver to pick up the RF signal from the subscribers

A transmitter to send RF signals to the subscribers
A wireline interface to send audio to a centrally located device used for dispatch functions
Base stations and repeaters perform a repeater function (retransmission of a signal received
from subscriber radios). However, in addition to the repeater function, a base station typically
provides wire line support for dispatch or comparator equipment.
1-14 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Control Channel
Trunked repeaters also have a control interface that allows the exchange of information
between the repeater and the central controller
Antenna systems for the repeaters are usually located on top of high structures such as buildings,
hills, or towers. The repeaters are normally located close to their antennas in order to minimize the
losses inherent in the cables connecting the repeaters to the antennas.
In a single site system, the signal that comes in at the receiver is immediately passed to the
transmitter for transmission to the subscribers that are within the coverage area. The signal is also
sent through the wireline interface in systems with a dispatch center.
Standard trunked repeaters can operate in one of two modes, control channel or voice channel.
Figure 1-11 illustrates the relationship between the subscribers and a repeater.
Figure 1-11 Subscriber to Repeater Relationship
Control Channel
In a Motorola trunked system, the central controller is the equipment that has the intelligence to control and
monitor the operation of the system and make channel assignments. The controller needs to be able to
communicate with all radios in the system to receive call requests and send channel assignments to the
radios in the field. This is the role of the control channel. Each system has one of its channels assigned
to function as a control channel. The other channels are used for voice communication.
The control channel is the RF interface between the central controller and the radios. It is always active, and
transmits and receive the data traffic required to monitor and control the operation of the subscribers. The
subscribers are in communication with the control channel as long as they are not involved in a voice call.
A radio uses the control channel to send in call requests or to receive call assignments. A radio always
tunes to the control channel except when it is assigned to a call on a voice channel. When a call is
completed, the radios involved in the call switch back to the active control channel.
6881009Y05-O April 2004 1-15

Voice Channel Chapter 1: Radio System Concepts
To make a call on a trunked system, a radio user presses the push-to-talk (PTT) button on the radio.
A call request is sent over the control channel to the controller. The controller assigns a channel to
the users group and sends out an assignment message over the control channel telling all radios that
have that particular group selected to switch to a specific voice channel.
All active radios in that group automatically switch to the assigned voice channel. When the radio user
initiating the call begins speaking, the transmission is received by the repeater at the site and transmitted
back out. Subscribers in the group receive the radio signal, processes the signal to separate the audio from
the RF and send the audio signal to the local speaker so the users can hear the message.
Subscribers in the system send a signal to the controller, through the control channel, indicating their unique
identification and talkgroup selection. This signal is sent whenever a subscriber is powered up or the radio
user changes the position of the talkgroup selector. This process is known as affiliation.
Voice Channel
The voice channel is the name applied to the repeaters assigned to transmit and receive voice
information. When one of the members of a group requests voice channel services, the group is
assigned its own voice channel for the duration of the call. A group that is assigned to channel 3
cannot be heard by members of a talkgroup assigned to channel 9.
In a Motorola trunked system, the voice channels can be operated in one of three modes: Transmission
Trunking, Message Trunking, or Message Trunking with PTT ID.
Transmission Trunking
The central controller reclaims the voice channel immediately after detecting a disconnect
signal from the transmitting unit. The receiving radios immediately returns to the
control channel. The entire request and assignment procedure are repeated for each
PTT from the originator or a unit responding to the original call.
Message Trunking
This allows a group to retain the assigned voice channel when the transmitting unit releases
the PTT. When a message trunked call is in progress, other units within the same group are
allowed to key without returning to the control channel for a voice channel assignment.
Message Trunking with PTT ID

This is message trunking with the additional requirement that a radio return to the
control channel to send its individual ID anytime the PTT switch is pressed. This
mode of operation provides positive identification of the transmitting radio and must
be programmed in both the radio unit and the system.
Packet Data Channel

A packet data channel (PDCH) refers to the radio frequency (RF) or common air interface (CAI)
resources used for the IP transport of data in an ASTRO 25 trunked communication system.
The characteristics associated with the IP transport and handling of a PDCH are similar to those
associated with the IP transport of voice over RF or CAI resources.
For more details about integrated voice and data and the PDCH, see Chapter 10, "Integrated Voice and Data."
System Operation
The operation of a Motorola trunked system can be divided into four functions or planes of operation:
1-16 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Call Processing Basics
Control
Assignment of system resources is centralized.
Subscriber access to the system and its features is controlled from a central point.
System resource operation is monitored. Resources are removed from the available pool
if they are not operating properly and returned to service when the problem has been
resolved either by the system itself or through technical intervention.
Subscriber use of voice channels is controlled and monitored through data and subaudible
signals. The signals let the controller know if the receiver and transmitter are active and also
cause the subscribers to return to the control channel at the end of a communication or when
the repeater malfunctions. The central controller never has contact with the audio itself.
Audio
Repeaters provide the audio interface between members of a communication group.
Repeaters are assigned to one communication group at a time. Interference
from other radios is prevented.
Management
A program is included in the central controllers firmware that provides a user with the capability
to change some of the systems features. Some of the managed features control the operation of
all radios while others are applied to specific units through a subscriber control record.
The management feature also provides enable and disable features for some system resources.
Data
The trunked radio communication system uses channel resources to transmit data. This
system feature is known as integrated voice and data (IV&D) which involves the IP
transport of voice and data into one trunked communication system.
Call Processing Basics
Call processing is the sequence of events that the system goes through to process a call request.
This section provides an introduction to the basics of call processing in a Motorola single site
trunked system. The discussion includes a description of the hardware components that are
used in call processing, the types of calls available, and the flow a call takes as it makes its way
through the system. This section contains the following topics:
"Conventional vs. Trunked Radio Systems" on page 1-17

"System Enhancements" on page 1-21
"Radio System Users" on page 1-21
Conventional vs. Trunked Radio Systems

There are two types of radio systems: conventional and trunked. Conventional radio systems use
a method of distributing calls similar to a telephone party line. Users share a common RF channel
and compete for air time. In addition, users not only listen to other conversations, they must
monitor other conversations before they can make a call of their own.
6881009Y05-O April 2004 1-17

Conventional System Operation Chapter 1: Radio System Concepts
Conventional System Operation
In conventional radio systems, individual radio users are assigned a particular channel to use when
communicating with their group. The channel assignment is done by programming the portable or
mobile radio with the frequency of a specific repeater. If one group has a lot of radio activity while
another has only light usage, several people may be waiting to use their assigned channel, while
the other channel sits idle. For example, Figure 1-12 shows that channel 1 is providing services to
group A; channel 2 is providing services to group B and thus cannot accept requests from group C;
channel 3 is idle but cannot automatically provide services to group C.
Figure 1-12 Conventional Radio System Example
Trunked System Operation
To illustrate how trunking works, think of an airport. In a conventional setup, the customers would
all line up according to the type of transaction they are making. This would create longer lines
at some of the counters, while others may be idle. SeeFigure 1-13.
1-18 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Trunked System Operation
Figure 1-13 Example: How a Conventional System Works
Rather than have people line up in front of specific counters according to the type of transaction they are
making, a trunked solution would have the customers form one line. The first customer in line moves
to the next available customer service representative as in the example in Figure 1-14. This eliminates
long lines at the basic check-in counters while the priority flyer line is empty.
6881009Y05-O April 2004 1-19

Trunked System Operation Chapter 1: Radio System Concepts
Figure 1-14 Example: How a Trunked Radio System Works
With trunking, radio users are not assigned to a fixed channel. Channels are common resources that are
accessible to all users on an as-needed and as-available basis. When a radio user initiates a call, the
system assigns an available channel to that call, eliminating the condition where one channel is busy while
another channel is inactive. When the call is finished, the channel is released and made available for other
users. Figure 1-15 shows an example of channel assignments in a trunked radio system.
Figure 1-15 Trunked Radio System Example
1-20 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System System Enhancements
Trunking takes advantage of the fact that people do not talk on their radios continuously for 24
hours a day. Most radio users need access to a channel several times a day, but their total time
on the system may not exceed five minutes each. Temporary channel assignment helps ensure
that a channel is available when a conversation needs to take place.
System Enhancements
The section describes how two-way radio systems can be enhanced.
Telephone Interconnect
Most two-way radio systems can be enhanced by a telephone interconnect option. Telephone
interconnect allows the mobile or portable radio user to place and receive standard
telephone calls through the two-way radio system.
In a trunked system, a telephone interconnect terminal is connected to the central controller to
provide the means to route any telephone calls to an appropriate repeater. A radio-initiated telephone
call is routed by the central controller through the assigned repeater to the Telephone Interconnect
Device (TID). The TID completes the connection to the telephone system.
A landline user can call a mobile or portable by dialing a number to access the interconnect terminal
connected to the system and adding the radios unique identification number. The central controller
then assigns a repeater to the call and sends the signal to the appropriate radio.
Voice Security Through Encryption
Once voice information is transmitted over an RF channel, it is susceptible to interception by

almost anyone with an inexpensive scanner, as well as other users on the same frequencies.
A radio user transmitting sensitive information must accept the risks: avoid using the radio
system (which is not always practical) or encrypt the message.
The encryption solution sends a voice message as a scrambled, digital signal. Digital encryption
first converts the analog voice signal to a digital signal. Once the signal is in digital format, the
encryption system uses an electronic code key to encrypt or encode the digital signal. When
the encryption is completed, the encoded message is transmitted.
Receiving radios have to be programmed with the same key that was used for encoding the
audio. Once the signal is received, it is decoded, and converted back to its original analog
format for reproduction at the receiving radios speaker. No other radios or devices without the
proper code will be able to receive intelligible information.
Radio System Users

The radio system stores information about users according to their individual location, and
any groups to which they have been assigned. This section discusses the various user
classifications that are available in a radio system.
Radio Users
Personnel using the trunked system are assigned a radio that is active in the system. A subscriber record in the
central controller is used to control the system features that the radio user will be permitted to access.
6881009Y05-O April 2004 1-21

Talkgroups Chapter 1: Radio System Concepts
Talkgroups
A talkgroup is the basic unit of communication in a trunked system. In most organizations, radio
users work in groups that are based on their functions and responsibilities. In a trunked radio
system, these groups of radio users can be assigned to communication talkgroups that reflect their
function or responsibilities. Figure 1-16 is an example of a talkgroup.
Programming of talkgroups in a radio is based on the communication needs of radio users. A radio can be
programmed with only one or with several talkgroups. Radio users selecting a particular talkgroup on their
radios are assigned a voice channel when someone in the group requests talkgroup call services. Group
privacy during conversations is provided since only one talkgroup is assigned to each voice channel.
Talkgroups are identified in the system by a unique six-digit ID that ranges between 800000 and 804094.
Figure 1-16 Example: Organization of Users in a Talkgroup
Multigroups
Several talkgroups can be combined to form a multigroup (also called an announcement group) (Figure 1-17).
Multigroups are assigned a six-digit ID from the same pool of numbers as the talkgroups.
In this example, calls placed to the police multigroup would be heard by the radio users in
the narcotics as well as the homicide talkgroups.
Figure 1-17 Example: Organization of Talkgroups in Multigroups
1-22 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Tracing a Basic Call
Tracing a Basic Call
A trunked system enables people to communicate with one another, when they need to, wherever they are in
the coverage area. All communications within the system are processed as a call. A call is a specific instance
of the system providing a call service to a properly configured, registered, and affiliated user of the system.
The following scenario shows how a call is handled when a radio user in talkgroup A initiates a call
to the talkgroup. The high-level steps are shown in a process flow diagram (Figure 1-18). Each
step is then illustrated and described in detail in the following sections.
This process illustrates what happens in a single site, analog trunked system. It is used to
show the basic relationships of the subscribers to the repeaters, the repeaters to the controller,
and the subscribers to the controller. It also serves as background to understand the changes
that have taken place with the advent of digital trunked systems.
Figure 1-18 Basic Single-Site Call
Basic Call Description

This section breaks down each step in the call process flow diagram in Figure 1-18. When
voice or control data is being sent to or from a specific radio or piece of equipment, arrows
indicate the direction in which the information flows.
6881009Y05-O April 2004 1-23

Basic Call Description Chapter 1: Radio System Concepts
1. When the radio user presses the PTT, the radio sends a data signal in the form
of an Inbound Signal Word (ISW) to the control channel. The ISW contains the
radios unit ID and an indication of the type of call being made. The ISW is a
request for allocation of a voice channel for the call.
Figure 1-19 Service Request
2. The control channel forwards the received ISW to the central controller. The central controller
searches its database for a unit ID match. The ISW contains the selected talkgroup information.
The central controller updates the database to reflect the current talkgroup affiliation.
Figure 1-20 Controller Receives Request
1-24 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Basic Call Description
3. The central controller processes the ISW and assigns one of the idle repeaters to the
users talkgroup. The central controller then sends an Outbound Signal Word (OSW)
over the control channel. The OSW contains the talkgroup ID and unit ID of the
requesting radio, as well as voice channel assignment information.
Figure 1-21 Controller Sends Outbound Command
4. All radios monitoring the control channel receive the transmitted OSW and
examine the talkgroup ID contained in the OSW.
Figure 1-22 Subscribers Receive Channel Grant Information
6881009Y05-O April 2004 1-25

5. All of those radios assigned to the talkgroup associated with the talkgroup ID in
the OSW switch to the assigned voice channel frequency.
Figure 1-23 Subscribers Switch to Voice Channel
6. The central controller now sends a Low-Speed Handshake (LSHS) over the voice channel.
All radios that have switched to that voice channel receive the LSHS. The LSHS causes the
receiving radios to activate their receiver and process the incoming transmission.
Figure 1-24 Receiving Radios at Voice Channel
1-26 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Basic Call Description
7. The initiating radio transmits voice audio and a sub-audible connect tone. The connect
tone is used to inform the controller of voice channel activity.
Figure 1-25 Transmitting Radio at Voice Channel
8. The controller continues to send the LSHS on the assigned voice channel for the duration of the
transmission. This is used to keep the receiving radios locked on the voice channel.
Figure 1-26 Call in Progress
6881009Y05-O April 2004 1-27

9. When the radio user releases the PTT button, the radio transmits a disconnect tone to
the controller, indicating that the transmission has ended.
Figure 1-27 End of Transmission
10. When the call is completed, the radios in the talkgroup switch back to the control channel
frequency. The previously assigned voice channel now becomes available for other calls.
Figure 1-28 Return to Control Channel
While one call is in progress, any radio in another talkgroup can also initiate a call and will
be assigned an available voice channel in the same manner.
In addition, the controller continues to transmit OSWs over the control channel. The OSWs contain
the voice channel assignments for all active calls. This information is used by any radio that may
be turned on, or that may come into range, after a call is in progress.
1-28 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Call Types
Call Types
Several types of calls can be made in a Motorola trunked system. This section describes
five examples from the possible types of voice calls that can be made. The examples are
divided between two main types of call services:
Group-based call services

Group-based calls are services that provide for group (one-to-many) communication.
The following are examples of group-based calls:
Talkgroup calls
Multigroup calls
Emergency calls
Individual call services

Individual calls are services that provide for individual user to user communication.
The following are individual type calls:
Private calls
Telephone Interconnect calls
This section provides a brief introduction to each of the five call types.
Talkgroup Calls
Talkgroup calls are the basic method of communication in a trunked radio system. Most of
the conversations a radio user participates in are talkgroup calls. The example call illustrated
in Figure 1-18, on page 1-23 is a talkgroup call.
Multigroup Calls
A multigroup call is a call involving two or more talkgroups. You can transmit a message to several talkgroups
simultaneously by selecting a multigroup. Any user affiliated with any talkgroup in the multigroup (or to the
multigroup itself) hears the call. This type of call is also known as an Announcement Group call.
A multigroup call can be set to wait until all talkgroups in the multigroup finish any calls in progress.
Alternatively, a multigroup call can be set to interrupt existing talkgroup communications. In this case,
the setup of the call does not wait for transmitting users in the associated talkgroups to stop keying
their radios. Those users join the call in progress when they release their PTT switches. Multigroup
calls use message trunking, allowing those who receive the call to talk back to the multigroup.
Multigroup calls are processed in the same manner as talkgroup calls.
Emergency Calls
An emergency call is a specialized, high-priority version of a talkgroup or multigroup call. Emergency calls
always have the highest priority in the system. When an emergency call request is made during a period
of time when all voice channels are busy, the request takes priority over any other type of call request.
The emergency call is transmitted on each radios currently selected talkgroup or multigroup.
Emergency calls are processed by the system in one of two ways; top of queue or ruthless preemption.
6881009Y05-O April 2004 1-29

Top of Queue Chapter 1: Radio System Concepts
Top of Queue
In top of queue processing the controller places the incoming emergency call request at the top of the
busy queue. No other group in the busy queue or new channel requester will be granted a voice channel
until the emergency caller has been assigned to a voice channel. In addition, the central controller
monitors the voice channels for a disconnect signal. Upon detection of a disconnect signal on one of the
voice channels, the controller will assign that channel to the unit in emergency mode.
Ruthless Preemption
This mode of operation causes the controller to look at the priority of the talkgroups assigned to the voice
channels and preempt the group with the lowest priority so the channel can be assigned to the emergency caller.
Private Calls
Private calls allow properly equipped radios in the same system to enter into one-to-one conversations.
The sender enters into the private conversation mode, selects a target radio by dialing an ID on a
keypad, and presses the PTT to initiate the call. Based on the model of the radio, the target radio
emits two beeps or telephone type ringing to indicate that a private conversation request has been
received. Radios can be programmed to receive calls only, make calls from a programmed list only,
or with the capability to call radios from a list or through the keypad.
Telephone Interconnect Calls

Telephone interconnect adds to the capabilities of a trunked system by extending its communication
range to the use of the public service telephone facilities.
A properly equipped radio can access any land-based telephone. The type (long distance,
local) and number of calls that a radio can make over the system is determined by the radios
programming and the parameters enabled in the central controller.
Land-based telephones can access any properly equipped portable or mobile provided
that they have the proper access numbers.
The following two types of telephone interconnect calls can be made:
Radio-to-landline phone
To call a landline phone from a radio, a radio user presses the phone button, waits for a dial
tone, and enters the phone number. If all interconnect channels are busy, the user receives a
busy signal and is placed in the interconnect busy queue. The user will receive an interconnect
channel on a first-in-first-out basis if all radios in the queue have the same priority.
Landline phone-to-radio
To call a radio from a landline phone, a telephone user dials a central number to the
radio system. If an interconnect channel is available, a tone signals the caller to enter
the six-digit ID of the radio user being called. A telephone-like ring alerts the radio
user to press the phone button and respond to the call.
1-30 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Modes of Operation
An optional type of telephone line and service, called DID (Direct Inbound Dialing), can be added
to the system to allow direct dialing from a telephone to a radio. This option requires that a unique
telephone number be assigned to each radio that is to be provided with this type of service.
Modes of Operation
A single site trunked system provides two modes of operation, the normal trunking
mode (described previously) and Failsoft.
Failsoft is a mode of operation that provides conventional communications at the site by using repeaters
programmed with this capability. Calls are not trunked and only occur on dedicated channels.
Failsoft in a single site trunked system takes place when the central controller fails or all control channels
are lost. Internal programming will cause the repeaters to operate in Failsoft mode if they detect a loss of
the controller. If the controller detects the loss of all control channels, it places the remaining channels in
Failsoft mode. Radios attached to the system migrate to the channel programmed in their own memory
and continue to communicate as if they were attached to a conventional repeater.
Multiple Site Trunked Systems

Multiple site trunked systems increase the size of the coverage area and provide radio communication
in places that are out of reach of a single site trunked system.
A multiple site system can be analyzed as a grouping of single site systems with a centrally located point of
control and audio distribution. The central controller at each site supervises the equipment and subscribers at
its location while the centralized control coordinates and oversees the operation of the individual sites. This
coordination requires the use of a device that can communicate with the individual site controllers.
A multiple site system allows radios to roam across large geographic areas without losing communication with
their group. In addition, members of a group can be dispersed throughout the various sites in the system and
still be able to communicate with each other. The following sections describe how this can be accomplished.
One of the first implementations of a multiple site system consisted of the merger of two technologies,
trunking and simulcast. Single site trunking systems were provided with the technology to communicate
with a centralized master control and audio distribution system. The central control consisted of a central
controller, now called the prime site controller, with the software and hardware necessary to communicate
with the site controllers and coordinate calls that spanned more than one site.
6881009Y05-O April 2004 1-31

Multiple Site Trunked Systems Chapter 1: Radio System Concepts
Trunked simulcast systems still relied on the use of the same set of frequencies across multiple sites
and the activation of the same frequency repeaters at all sites when a call assignment was made.
The systems required specialized equipment to ensure that the same frequency transmitters were
activated simultaneously and that signal arrived at the same time in receiving radios that happened
to be in overlap areas. simulcast systems were limited to 10 sites.
A different type of multiple site system was also developed that required the use of a different set of
frequencies at each remote site. This type of system eliminated the need for the specialized timing equipment
required by simulcast but it increased the number of frequencies required for operation.
Figure 1-29 Trunked Simulcast System
1-32 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Motorola SmartZone Systems
The term multiple site is a generic term identifying multiple sites in the system. The term multiple
site should not to be confused with the term multisite subsystem. The term multisite subsystem is
used by the Motorola Zone Configuration Manager (ZCM) application to specifically identify
three distinct subsystems providing radio frequency coverage for the system. For more detailed
information on multisite subsystems, see Chapter 5, "Radio Frequency Subsystems."
Motorola SmartZone Systems
The next stage in the development of Motorola multiple site systems was SmartZone,
which has the following characteristics:
Extension of coverage area
SmartZone is a wide area trunking system using multiple sites with a variable number
of repeaters to cover large geographic areas such as a region, county, state or country.
Larger geographic areas can be covered since a single system can have up to 48 sites.
Operation of the radio is transparent; the radio operator does not have to change the
selector in the radio whenever a change in geographic area occurs.
Site Registration and Deregistration

Portable and mobile radios have the programming necessary for them to signal the controller
when they are activated and lock onto a control channel at one of the sites. Radios
are also programmed to send a signal when the radio is turned off.
Dynamic site assignment

Dynamic site assignment allows efficient utilization of voice channel resources. The
SmartZone controller can activate voice channel only at the sites where a talkgroup
has members. Dynamic site assignment, together with site registration, eliminates
the need to activate voice channels unnecessarily.
Subsystem integration
SmartZone accommodates a mixture of single site and simulcast trunked subsystems.
Variable density sites

SmartZone provides the capability to equip each site with only the number of repeaters needed
to handle the traffic volume at that site. Each site can have a different number of repeaters.
Intelligent repeaters
The IntelliRepeater, a repeater designed for SmartZone systems, eliminated the need for
dedicated remote controllers and is equipped with the capabilities necessary to maintain
trunking operation without the master controller and operate as a voice or control channel.
Introduction of new call processing features

New call processing features have made it possible for the subscribers to roam across
the system and still have quick access to a voice channel even when a conversation
had been initiated at a site different than the current location.
6881009Y05-O April 2004 1-33

Major System Components Chapter 1: Radio System Concepts
ASTRO capability
New radios were designed that made it possible to convert the users analog audio into
a digital format prior to transmission to the repeaters. The repeaters were provided
with the capability to handle these signals transparently. The new coding technique
also made it possible to increase the amount of data that could be sent along with the
audio as embedded signals, improve the quality of the audio signal, and reduced the
amount of channel space required from 25 kHz to 12.5 kHz.
The SmartZone system retained the three functions or planes of operation introduced in single site systems:
Subscriber and system control through the master controller and site controllers.
System-wide audio routing through the use of a new centralized audio routing system.
A management system that can be accessed locally or remotely and allows a system manager
to control equipment operation, as well as system access, by the subscribers.
All three functions received the enhancements necessary to support multiple site operation.
Major System Components
The following sections describe the components or subsystems that may be found in a multiple site system.
Radio Site
A radio site is a geographical area within which a two-way radio infrastructure allows communication
between mobile or portable two-way radios. It is the equivalent of a single site trunked system with
additional control and audio links to a central location. Under certain conditions, it can operate
independently but its normal mode of operation is in conjunction with other radio sites. A radio site is
the remote site in a multiple site system. Figure 1-30 shows an example of a radio site.
Figure 1-30 Radio Site
Three types of radio sites can operate in a SmartZone system:

Central Controller Sites (6809 Controller or MTC 3600)
Central controller sites are Motorola single site trunked systems with the software and
firmware required to operate in a SmartZone system. A 6809 or MTC 3600 controller is
provided with a control link to the zone controller. If the link to the zone controller fails,
the site controller will operate the site as if it were an independent single site system.
However, certain capabilities such as SAC, console communication, and telephone
interconnect communication are lost. This operation is called site trunking.
1-34 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Master Site
IntelliRepeater Sites
These sites consist of a number of repeaters connected to each other through a LAN.
Although all repeaters have site controller capability, only one of them takes control
of the site when the site is initialized. Should that repeater fail, another will take its
place as the site controller. Normally, one of the repeaters at the site is designated as
the primary control channel; the rest operate as voice channels.
Simulcast Systems
An entire Motorola trunked simulcast system can be connected and programmed to operate in a
SmartZone system. The zone controller communicates with the simulcast prime site controller
to coordinate calls that involve other sites and the simulcast system. Simulcast systems that
are part of a SmartZone system are also referred to as simulcast subsystems.
Master Site
A master site (Figure 1-31) is the central point of control for the operation of a multiple site system. It is
the site within a radio system that performs control, call processing, and network management functions.
Equipment at the master sites coordinates call processing, assignment of system-wide area resources, and
distribution of audio to all the other sites in the system. It is at this site that the master controller (now called
the zone controller), the audio distribution system, and the system management equipment are located.
Figure 1-31 Master Site
Zone
A zone (Figure 1-32) contains several radio sites and one master site. A zone can consist
of 6809 sites, simulcast subsystems, and IntelliRepeater sites that are connected to a master
site through a transport system such as microwave links.
6881009Y05-O April 2004 1-35

Call Processing Chapter 1: Radio System Concepts
Figure 1-32 Zone
Call Processing
A portable or mobiles interface to the SmartZone system is similar to that described for the
single site trunked system. Enhancements were made to the signalling that allow the radios
to automatically register at their current site, notify the system as they move through different
sites, and receive control channel accessibility at adjacent sites.
Modes of Operation
SmartZone provides the following three modes of operation:
Wide Area Trunking

The normal operating state for each site in the system. If all sites are in wide area trunking
mode within a zone, there are communication paths covering the entire zone. The zone
controller is in control of call processing and audio routing; each site has an active control
channel and at least one operational voice channel. Figure 1-33 illustrates the following
two additional conditions required to maintain wide area trunking:
A good control path to the sites.
A good audio path between the audio distribution system at the master
site and the voice channels at the sites.
Figure 1-33 Wide Area Trunking Requirements
1-36 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Multiple Zone Systems
Site Trunking
A mode of operation that takes place when there is a loss of the control path to a site or all the
audio paths to a site are lost. The affected site operates as a single site trunked system providing
services to radios that registered with the site. Audio is not routed to the master site, it remains
within the site. The remote site controller or IntelliRepeater site controller is in control of call
processing at the site while the zone controller maintains all other sites in wide area trunking.
The site can stay in site trunking mode as long as there is a good control path between the site
controller and the repeaters, an active control channel, and a working voice channel.
Failsoft
A mode of operation that provides conventional communications at the site by using repeaters
programmed with this capability. Calls are not trunked and only occur on dedicated channels.
If a remote site is configured with a standard controller (6809) and repeaters, the site
will go into Failsoft mode if the site controller fails or all control channels are lost.
The rest of the system will continue to operate in wide area mode.
If the remote site is configured with IntelliRepeaters, the site will have to lose the control
link to the master site and all but one of the repeaters to go into Failsoft. The site can
provide trunking services as long as there are two operational IntelliRepeaters at the site,
one acting as the control channel and the other one as the voice channel. Either one
can assume the additional responsibility of site controller. However, trunking services
will be limited and calls are more likely to be placed in the busy queue.
Multiple Zone Systems

A multizone system refers to a radio system that contains several interconnected zones. This type of
configuration provides a very wide area radio communications network based on the interconnection of
multiple zones. A multiple zone system operates with virtually transparent boundaries, creating a homogeneous
system operation over very large geographical areas. Figure 1-34 shows an example of a multizone system.
6881009Y05-O April 2004 1-37

Additional Requirements Chapter 1: Radio System Concepts
Figure 1-34 Example: Multiple Zone System
Additional Requirements
A multiple zone system adds three new elements to the list of requirements necessary to
maintain system-wide communication (see Figure 1-35).
An active control path is required between any two pair of zones in order to be able
to coordinate a call that involves sites in more than one zone.
Interzone audio paths are needed to route the audio to any zone required by
the location of the talkgroup members.
The zone controllers require the hardware and software necessary to maintain
communication with each other, operate the equipment in their own zone, and coordinate
call processing whether it is single zone or multiple zone.
1-38 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Home Zone Mapping
Figure 1-35 Multiple Zone System - Conditions for Interzone Trunking
Multiple zone systems introduced new hardware, software, and terminology to radio technology. The hardware
and software allow the system to exchange control information between zones, establish audio paths between
zones when necessary, track subscriber movement across sites or zones, and provide a management subsystem
that can be accessed from any one of the zones. The terminology was expanded to include home zone
mapping, controlling zone, and participating zonethree multizone terms described in the following sections.
Home Zone Mapping

Home zone mapping provides the capability to divide into ranges the total number of individual and
talkgroup IDs that can be used in the system and to assign the ranges to the various zones. All of the
home zone assignments for groups and individuals are compiled into two home zone maps:
Individuals to Home Zone
Groups to Home Zone
The zone assigned to a particular ID is that IDs home zone. The home zone to which an ID is assigned has an
impact on how the system operates. Home zone assignment affects system operation in the following ways:
Configuration information is distributed throughout the system based on
the IDs home zone assignment.
A zone controller stores only the configuration information for those individual
and group IDs that are home to that zone.
6881009Y05-O April 2004 1-39

Controlling Zone Chapter 1: Radio System Concepts
Controlling Zone
For group call services, the home zone of the group is always the controlling zone for the call, regardless
of the zone where the group member is currently registered. Depending on system configuration, this can
impact the number of interzone calls versus the number of single-zone calls that take place in the system. This
can then affect the number of interzone resources that are needed between any two pair of zones.
Participating Zone
A participating zone is any zone containing one or more users involved with a call controlled by another
zone. When a talkgroup member requests a call that requires more than one zone, the controlling
zone receives acknowledgments from all participating zones before the call is granted. The grant
message is sent to all zones in the call, prompting them to assign resources.
Interzone Group Service Availability
For group-based services, there are three possibilities for call requests:
Full interzone group service availability: All zones are in a state of interzone
trunking with respect to the groups home zone.
Reduced interzone group service availability: At least one participating zone is in
interzone trunking with the groups home zone and at least one zone is not.
Zone isolated group service availability: The zone can provide call services
only within its own site resources.
Where Calls Occur
Calls can occur in a single site, a single zone, and between multiple zones. The following
are some examples of where calls can occur.
Single Site
Calls can take place within a single site, such as the call that was described in Figure 1-18, on
page 1-23. In a multiple site or multiple zone system, single site calls take place only
when the remote site is isolated from its master site.
Zone
Calls can take place between multiple sites within a zone. The sites can be any combination of IntelliRepeater
sites or simulcast subsystems. Assignment of voice channels is done by the zone controller for both
IntelliRepeater sites and simulcast subsystems. In a simulcast subsystem, the prime site controller
coordinates the activation of the assigned voice channel at the remote simulcast subsites.
Multiple Zones
In a multiple zone system, calls can take place between more than one zone. The controllers at each
zones master site communicate with each other to coordinate the assignment of resources.
1-40 6881009Y05-O April 2004

Chapter
2
What Is an ASTRO 25 Trunking System?

An ASTRO
25 trunking system is a digital radio communications system that allows a mobile radio
user to make calls easily over a wide geographic area. Users at any location within the coverage area can
press the push-to-talk (PTT) button on their radios to make calls to any valid group or individual located
anywhere in the coverage area. The coverage area can cover thousands of square miles.
The system includes a complex network of computer servers and workstations, high-speed
local area network (LAN), wide area network (WAN) facilities, sophisticated databases and
management software, and radio frequency (RF) equipment.
The ASTRO 25 system allows communication across multiple zones and allows users from
different zones to be combined into talkgroups. This means that users can communicate across
each geographic coverage area and use a wide range of communication capabilities, provided that
the user configuration is well-planned and systematically implemented.
ASTRO 25 Trunking System Elements

The basic components of the ASTRO 25 trunking system are the following:
Radios (portable and mobile subscriber radios)
Sites (master site, ASTRO 25 Repeater sites, IntelliRepeater sites, simulcast
subsystems, and remote dispatch sites)
Zones (a zone or zones containing one or more RF sites)
System (single zone or multiple zones containing one or more RF sites)
The ASTRO 25 system distributes the call processing load between the zone or zones that comprise
the system. User configuration information also is shared among the zones. Each zone has a local
area network (LAN). The LANs are interconnected though a high-speed transport network to form
a wide area network (WAN). The WAN allows user configuration information, call processing
information, and audio to be conveyed throughout the system.
Each zone is responsible for managing its own elements. This includes configuring the physical
infrastructure, managing mobility within the zone, and processing calls within the zone. Some call
features operate only within a zone, so they are defined as zone level functions.
The remainder of this volume introduces various system components, concepts, and processes
associated with the ASTRO 25 radio communication system.
6881009Y05-O April 2004 2-1

ASTRO 25 Technology Chapter 2: What Is an ASTRO 25 Trunking System?
ASTRO 25 Technology

At the center of the ASTRO 25 system is a transport core designed to carry voice, data, and
management information through Internet Protocol (IP) packets.
This packet transport technology is beneficial for providing the system characteristics:
A scalable platform. The ASTRO 25 system supports seven zones and 100 sites per zone.
A digital-only platform. The digital platform supports the open standard
IMBE protocol for voice transmission.
Circuit-based console support. The system supports the operation of circuit-based
consoles in a packet-based environment.
Ability to transport vocoded and encrypted audio. The transport core provides the ability to
transparently transport vocoded and encrypted audio. Once voice is vocoded and/or encrypted at
a source, the digital information is passed all the way through the network with no conversions
required. Conversion to the original audio format is required only at the destination receiver.
Secure operation. The ASTRO 25 system supports radio-to-radio and
radio-to-console secure operation.
The ASTRO 25 system includes an Internet Protocol (IP)-based infrastructure that provides IP multicast
technology for dispatch services. This technology allows group calls to be set up, processed, and turn
down easily in a packet environment, replacing circuit switched methods.
Multicast Technology
IP Multicast routing, commonly referred to as simply multicast, is a method of transmitting

messages (datagrams) between a number of sites which are part of a multicast group. This
differs from unicast, which transmits messages between two endpoints, and broadcast, which
transmits messages from a single source to all hosts on a network.
Multicast employs a concept known as a Rendezvous Point (RP), in which a router or set of
routers is identified as an RP for an associated multicast group address range. The function of the
RP is to receive multicast transmissions from an originating site, and then fan them out to other
sites and zones, creating a multicast tree for each multicast group.
Multicast is closely aligned with the talkgroup concept. With multicast, the transmitting radios audio is
distributed to the appropriate sites by the RP router. Without multicast, the transmitting unit would have to
send a separate copy of each packet of a transmission to each receiving site. Multicast transmissions are
sent only to those sites which have subscribed or joined the specific multicast group. Once the join
message is received, the routers propagate multicast traffic to the appropriate sites and zones. Multicast trees
for audio traffic are set up on service request and are present only for the duration of the call.
A range of class-D IP addresses (addresses beginning with 224-239) are designated as multicast group addresses.
2-2 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System The Call Model
The Call Model

The main purpose of an ASTRO 25 system is to provide voice and data communication
services to subscribers and dispatchers throughout the system. The following describes how
a talkgroup voice call is serviced by the system. See Figure 2-1, on page 2-4 in conjunction
with the following description of a basic multicast call example.
1. A radio user presses the PTT switch to talk to other users in the talkgroup. The radio transmits
a Call Request on the RF control channel at the site. The control channel receives the Call
Request and forwards it to the site Ethernet LAN. Before placing the Call Request packet
on the site Ethernet LAN, the base station encapsulates the Call Request message in a User
Datagram Protocol (UDP)/IP datagram with the zone controllerss destination IP address.
UDP is a transport layer protocol that resides on top of the IP. UDP provides
a transaction-oriented, best-effort delivery service.
IP is the Internet layer protocol tasked with defining how data is transferred
across the network, how devices are addressed, and how to route data
appropriately. IP defines a standard addressing method and it defines how
to fragment, transport, and reassemble data packets.
2. The IP packet network routes the Call Request packet to the zone controller. Upon receiving
the Call Request message, the zone controller checks an internal database to determine the
location of all members in the requested talkgroup (such as RF sites and remote dispatch
sites locations). The zone controller then assigns a multicast group address to the call
and sends the assigned multicast group address to all the participating RF sites, remote
dispatch resources, and the Motorola Gold Elite Gateway (MGEG) at the master site. This
message is referred to as a Call Grant message and is sent in an IP datagram.
3. Upon receiving the Call Grant message, the RF and dispatch sites extract the IP
multicast address from the Call Grant. The assigned voice channels at IR sites, the
comparators at simulcast subsystems, and the MGEG at the master site generate a group
Join message. The group Join message is an IP control packet.
4. Upon receiving the IP group Join message, the RF and dispatch site routers communicate
with RP routers in the system to set up an IP multicast distribution tree. This tree is used
to distribute voice payload traffic to all sites participating in the call.
5. The radio begins transmitting vocoded audio on the assigned RF voice channel at its
site. The voice channel receives the audio and the audio is placed in an IP datagram
destined to the assigned IP multicast address (as assigned in the Call Grant). The
IP multicast packet is placed on the Ethernet LAN.
6. The IP multicast audio stream is distributed to all the RF and dispatch sites through
the Rendezvous Point router and IP multicast tree.
6881009Y05-O April 2004 2-3

The Call Model Chapter 2: What Is an ASTRO 25 Trunking System?
7. When the first user dekeys and a second member of the talkgroup transmits while the call
is still active (repeater call hang time has not expired), the same multicast tree is used. The
voice channel receives vocoded audio at the new source site and the vocoded audio is
placed in an IP packet destined for the groups Rendezvous Point router. The IP packet
flows down the same IP multicast tree generated earlier by the routers.
8. When the call is over (expiration of the message timer), the sites (RF or dispatch) generate an
IP group Leave message. The Leave messages cause the multicast tree to be taken down.
The preferred mode of operation for an ASTRO 25 system is message

trunking with PTT-ID. This parameter is programmed in the system, through
the User Configuration Manager (UCM), as message trunking, and in the
radios, through their programming software, as PTT-ID.
Figure 2-1 Call Processing
2-4 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Traffic Planes
Traffic Planes
There are four logical traffic planes set up in the transport network. The traffic planes describe the
communications paths which exist within the network and describe the traffic types carried over
those paths. The following traffic planes exist in an ASTRO 25 system:
Voice Control Plane
Audio Plane
Network Management Plane
Data Plane
ASTRO 25 systems use the same physical link for traffic from all four planes (Figure 2-2).
Figure 2-2 ASTRO 25 System Logical Traffic Planes
6881009Y05-O April 2004 2-5

Voice Control Plane Chapter 2: What Is an ASTRO 25 Trunking System?
Voice Control Plane

Traffic between the zone controller and the RF sites within a zone, and between zone controllers in
different zones is called Voice Control traffic. The logical plane used to transport this information is called
the Voice Control Plane. Voice Control traffic is responsible for setting up the audio path between the
transmitting site and the receiving site or sites. The zone controller, through the voice control plane, receives
talkgroup requests and sends messages to appropriate sites, assigning an IP multicast group address to
use for the call. Control communication from the zone controller to the RF sites is accomplished using
multicast. Unicast is used for transmissions from the RF sites back to the zone controller.
Audio Plane
The Audio Plane is made up of the unicast routes and multicast trees setup by voice control. Multicast
is used to carry audio packets for all call types (group calls, private calls, telephone interconnect calls)
between subscribers or dispatch consoles in the system, both intrazone and interzone.
Network Management Plane

The Network Management Plane carries all of the unicast network management traffic between
the ASTRO 25 network devices (for example, routers and switches), and the Operations Support
Systems network management servers and terminals.
Data Plane
This section describes the logical characteristics of the components supporting the data
plane of the ASTRO 25 data communication system.
The GGSN provides the networking between your data network and the Motorola ASTRO 25 communication
system, and handles IP routing services for end-to-end data messaging. This includes static and dynamic
IP addressing, IP fragmentation, and Internet Control Message Protocol (ICMP) error reporting to support
troubleshooting activities. If there is a GGSN failure, the system loses the ability to provide data messaging
from your data network to mobile data devices in your system, and all IP services are dropped. The Packet
Data Gateway (PDG) consists of the Packet Data Router (PDR) and Radio Network Gateway (RNG)
components. The PDR and RNG are both cabable of sourcing an ICMP echo request message and can
accept the resulting ICMP echo response message. Failure of the PDR results in a disconnect of the data
path between the ASTRO 25 data communication system and the mobile subscriber units (MSUs); therefore,
the ability to establish context activation for an MSU is lost. Border Routers do not affect the ASTRO 25
data communication system from providing packet data channel resources, but will inhibit your ability to
send data messages from your data network to MSUs and associated data devices should they fail.
The Transport Core
The transport core at the master site supports the logical and physical structure with
the following components and functions:
Ethernet LAN switch
WAN switch
Core and Exit routers
Gateway routers
2-6 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Ethernet LAN Switch
Ethernet LAN Switch

The Ethernet LAN switch provides the interface for all servers, clients, and routers to connect
into the core network. The ASTRO 25 system uses the layer 2 capability of this switch to handle
multicast traffic. See "Gateway Routers" on page 4-14 for layer 3 switching for handling network
management traffic. To meet system availability requirements, the LAN switch is equipped with
redundant power supplies, redundant CPUs and redundant layer 2 port cards. The LAN switch has
a network management system to provide proactive fault management.
Two virtual LANs are set up within the LAN switch. The purpose of these as Transitional LANs
(TLAN1 and TLAN2) is to carry intrazone traffic between the various core, exit, and gateway
routers. Two are needed to connect each of the two Ethernet ports in the routers. If an Ethernet
port fails, traffic is to be transferred to the remaining TLAN.
WAN Switch
The WAN switch is a Frame Relay/Asynchronous Transfer Mode (ATM) switch that interfaces a zone master
site to its remote sites and other zone master sites. The WAN switch is a chassis-based device with redundant
power supplies, redundant CPUs, network management, and backplane switching to increase availability.
Core and Exit Routers

Core routers perform routing control of audio, data, and network management traffic in and out of the
zone. The routers have two Ethernet ports that connect into different layer 2 modules on the LAN switch
and a High Speed Serial Interface (HSSI) port to connect to the WAN switch for intrazone and interzone
traffic. Redundant core routers are used. If the path through the primary router is lost, the redundant
router takes over. One-to-one core router redundancy increases system availability.
The number of core routers is dependent upon the number of channels in the zone. If more routers are required,
they must be added in pairs. The core router uses Frame Relay to communicate with the sites through the WAN
switch, which acts as a Frame Relay server. The core routers provide a proactive fault management system by
providing an indication to the fault management system when a redundant core router has taken control.
Exit routers serve two primary functions in an ASTRO 25 system:
Handle interzone links. The exit routers use ATM to transfer information to other zones
through the WAN switch. As with the core routers, the exit routers have two Ethernet
ports that will connect into different layer 2 modules on the LAN switch and a HSSI port
connected to the WAN switch for WAN traffic. Because only one HSSI per router is connected
to the WAN switch, redundant exit routers are used to ensure availability.
Maintain the list of all active rendezvous points and maintain the group
prefixes served by each. This task requires that exit routers be installed in
single zone as well as multiple zone systems.
Gateway Routers
Gateway routers are used for devices that require network redundancy and are multicasting beyond
their local LAN. Gateway routers provide support for the following:
Zone Controller (control router functionality)

MGEG (MGEG router functionality)
Packet Data Gateway (data router functionality)
Network Management
6881009Y05-O April 2004 2-7

Functional Subsystems Chapter 2: What Is an ASTRO 25 Trunking System?
Functional Subsystems
The following sections describe functional subsystems:

"Call Processing Subsystem" on page 2-8
"Network Management Subsystem" on page 2-9
"Console Operator Subsystem" on page 2-11
"Radio Frequency Subsystems" on page 2-12
"Telephone Interconnect Subsystem" on page 2-17
"Data Communication Subsystem" on page 2-18
"Network Security Subsystem" on page 2-19
Call Processing Subsystem
The call processing subsystem is a functional part of the ASTRO 25 trunking system, with
components primarily associated with the master site.
The Motorola MZC 3000 zone controller is a redundant processor that provides trunking call processing
for RF subsystems and telephone interconnect subsystem devices. The MZC 3000 is the central processing
hardware and software at the master site providing call processing and mobility management for the system.
The Motorola MZC 3000 zone controller incorporates CompactPCI hardware, which provides
adaptability to technology enhancements and better planning of future communication needs and
migration. Additional features and benefits of the MZC 3000 include:
Intelligent Switchover: The redundant zone controller configuration provides automatic
switchover to the standby controller if a loss of wide area communications is detected due to
a failure internal to the active zone controller. Notification can be sent to the user if other
components fail, allowing the user to manually switch to the standby controller if desired.
Cross-Controller Compatibility: The redundant zone controller platform is capable of
running a different version of software simultaneously to ensure that upgrades are fully
functional with one controller before upgrading the second controller.
2-8 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Network Management Subsystem
Figure 2-3 Call Processing Subsystem
Network Management Subsystem
The network management subsystem is a functional part of the ASTRO 25 trunking system,
with components primarily associated with the master site.
The network management subsystem (NMS) is based on the client/server networking model.
The NMS meshes and scales with the other ASTRO 25 infrastructure elements across the
packet-switched network. The NMS uses the Microsoft Windows operating system as the
platform for the client personal computer (PC) workstation applications.
The application and database servers run unattended on computers based on the CompactPCI standard.
The server applications run over Sun Microsystems Solaris 7 Operating Environment.
Network management is a set of software tools that supports the management of a complex radio
communications system and its component parts, which include radios, computers, and inter-networking
components. Network management tools support the maximization of resource availability while
helping to minimize system downtime and maintenance costs.
Network management applications used in an ASTRO 25 system can be divided into two categories:
6881009Y05-O April 2004 2-9

Network Management Subsystem Chapter 2: What Is an ASTRO 25 Trunking System?
Private Radio Network Management (PRNM) applications such as:

Zone Watch
Radio Control Manager (RCM)
Zone Configuration Manager (ZCM)
User Configuration Manager (UCM)
Historical Reports
Dynamic Reports
ATIA (Air Traffic Information Access) Log Viewer
Affiliation Display
FullVision Integrated Network Manager (INM)
Software Download Manager
Router Manager
Transport Network Management (TNM) applications such as:
CiscoWorks 2000
Preside Multiservice Data Manager (MDM)
InfoVista (Optional)
The PRNM and TNM applications are described in Chapter 13, "Introduction to
Network Management Applications."
Figure 2-4 Network Management Subsystem
2-10 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Console Operator Subsystem
Another network management tool that can be used in an ASTRO 25 system is Motorola Supervisory
Control and Data Acquisition or MOSCAD . MOSCAD is an optional component that can
provide a common method for controlling certain system equipment (such as tower lights and
power generators) and for collecting and forwarding data concerning the state of system equipment
such as channel banks, microwave, and time reference. MOSCAD can also be used to gracefully
shut down the zone controller on total loss of power conditions.
Console Operator Subsystem
The console operator subsystem is a functional part of the ASTRO 25 trunking system, with
components primarily associated with the master site.
ASTRO 25 supports standard CENTRACOM Elite dispatch positions. The Motorola Gold Elite
Gateway (MGEG) is an interface device that allows an existing CENTRACOM Elite dispatch
system to communicate over a packet-based ASTRO 25 trunked radio system. The MGEG allows
for support of the CENTRACOM Gold Series dispatch architecture [Ambassador Electronics Bank
(AEB), Central Electronics Bank (CEB), and Elite Ops] within the system.
Figure 2-5 Console Operator Subsystem
6881009Y05-O April 2004 2-11

Radio Frequency Subsystems Chapter 2: What Is an ASTRO 25 Trunking System?
Radio Frequency Subsystems
To satisfy the need to accommodate a variety of coverage areas and system feature requirements, the following
types of Radio Frequency (RF) subsystems are available in the ASTRO 25 trunking communication system:
ASTRO 25 Repeater Site subsystem

IntelliRepeaterSite subsystem
Multisite subsystems
ASTRO 25 Repeater Site
The network infrastructure at an ASTRO 25 Repeater Site includes a site router and an Ethernet switch
with 10/100Base-T interface. For increased availability, each site router is interfaced through the WAN
switch at the master site with a pair of redundant core routers. See Figure 2-6.
Figure 2-6 ASTRO 25 Repeater Site
ASTRO 25 Repeater
The ASTRO 25 repeater is the RF interface between the ASTRO 25 system and the subscriber
units. The ASTRO 25 Repeater includes Configuration/Service Software (CSS) capability,
software downloading, and packet-based voice operation only.
2-12 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System PSC 9600 Site Controller
PSC 9600 Site Controller

The PSC 9600 site controller is the control interface between the ASTRO 25 Repeater
site and the zone controller at the zone master site. The PSC 9600 site controller is
capable of supporting up to 28 trunked channels.
Remote Site Router

The remote site router provides a WAN interface that handles all of the traffic to and from the zone
for the RF site including voice, control, data, and network management traffic.
Ethernet Switch
The Ethernet switch provides a 10Base-T LAN interface for the ASTRO 25 Repeaters, ASTRO 25 Repeater
site controllers and a 100Base-T port for the site router. The switch also provides ports for interfacing
with MOSCAD and to allow access by a service technician with a properly configured PC.
Mutual Aid Channel Bank

The mutual aid channel bank (not included in Figure 2-6) is an option that can be used when
mutual aid channels are present at the site and audio from those channels needs to be routed
through the transport network. The channel bank can be equipped with the hardware necessary
to interface analog or ASTRO mutual aid stations to the system.
For more details on the ASTRO 25 Repeater Site subsystem, see Chapter 5, "Radio Frequency Subsystems."
For more details on the mutual aid, see Chapter 6, "ASTRO 25 Systems and Mutual Aid."
IntelliRepeater Site Subsystem
The ASTRO 25 system recognizes and treats each ASTRO 25 IntelliRepeater site as a separate site, each
covering a single and separate geographic area. However, because the communication characteristics
and components of each site are similar, a group of ASTRO 25 IntelliRepeater sites is considered to
be a subsystem. The repeaters in the IntelliRepeater subsystem have the built-in intelligence of a site
controller, in contrast to the physically separate site controller used in an ASTRO 25 Repeater Site
Subsystem. Each IntelliRepeater site can have up to 28 IntelliRepeaters. For more detailed information
on the IntelliRepeater subsystem, see Chapter 5, "Radio Frequency Subsystems."
Multisite Subsystem
The zone configuration manager categorizes the following as parts of the multisite subsystem:
Digital simulcast subsystem (700 MHz, 800 MHz, VHF, UHF)

Digital simulcast subsystem with support for receive only remote sites (VHF, UHF)
Single transmitter receiver voting subsystem (VHF, UHF)
In a multisite subsystem, the prime site is the central control location for the other sites in the subsystem.
Because the prime site controller at a prime site provides control of the subsystems remote sites, the
ASTRO 25 system recognizes and treats each of the multisite subsystems as a single site.
6881009Y05-O April 2004 2-13

Digital Simulcast Subsystem Chapter 2: What Is an ASTRO 25 Trunking System?
Digital Simulcast Subsystem
As part of a multisite subsystem, digital simulcast subsystems are most beneficial for providing
radio communication coverage in geographic coverage areas that present multiple or potential
obstruction to radio communication signals. These subsystems provide communication coverage by
using signal comparator equipment and multiple transmitters designed to simultaneously transmit a
best quality signal over the coverage area. Two simulcast subsystems are identified to distinguish
between the simulcast subsystems that do not support receiver only remote sites operating in the
700 MHz, 800 MHz, and VHF/UHF bands, from the simulcast subsystems that do support satellite
receiver only remote sites capable of operating in the VHF/UHF bands only.
The ASTRO 25 digital simulcast subsystem consists of a prime site and a number of simulcast remote sites.
Simulcast Prime Site

A prime site acts as a control and audio center for the simulcast subsystem. It interfaces with the
master site through the WAN infrastructure. From the prime site to each simulcast subsite, control
and audio use serial links from the comparators through channel banks. Only network management
traffic is routed over the IP network through the prime site to the subsites.
Simulcast subsystems are usually described by referring to the number of channels and the number of
simulcast remote subsites in the system. For example, a simulcast subsystem using 10 RF channels across
five simulcast remote subsites is referred to as a 5 site, 10 channel simulcast subsystem.
The simulcast prime site communicates with the simulcast remote subsites over two separate links.
Control channel data and voice traffic channel data are transported between the comparators at the
prime site and the base radios at the remote subsites using 9600 bps V.24 links. Network management
data is distributed to the simulcast remote subsites over V.35 links.
Remote site controllers are not needed in an ASTRO 25 digital simulcast subsystem. The
prime site controller and the ASTRO-TAC 9600 comparators perform all the tasks necessary
for the operation of the digital simulcast subsystem.
2-14 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Prime Site Router
Figure 2-7 Simulcast Prime Site
Prime Site Router

The prime site router provides a WAN interface that carries all of the traffic for the RF site
including voice, control, data, and network management traffic. The router provides the
network connectivity for the remote sites as well as encapsulation of Ethernet LAN packets in
Frame Relay IP packets on a serial (FlexWAN) interface.
Prime Site LAN Switch

The LAN switches are required to interface the prime site router to the prime site controllers and
the ASTRO-TAC 9600 comparators. Two switches are used at the site to increase availability.
Each of the two prime site controllers is connected to its own switch; an interface between the two
switches allows either controller to have access to all the site resources.
MTC 9600 Simulcast Prime Site Controller

The MTC 9600 simulcast prime site controller is designed for use in ASTRO 25 simulcast trunking systems
that use a 9600 bps control channel. The MTC 9600 controller provides call processing for individual
simulcast subsites and acts as a site link between the digital simulcast subsystem and the zone controller. The
MTC 9600 controller is capable of supporting up to 15 simulcast subsites, each with up to 30 channels.
The MTC 9600 ships standard in a fully redundant configuration of two controllers. The redundant (standby)
controller automatically takes over site control operations when the active MTC 9600 has failed.
6881009Y05-O April 2004 2-15

ASTRO-TAC 9600 Comparator Chapter 2: What Is an ASTRO 25 Trunking System?
ASTRO-TAC 9600 Comparator

The ASTRO-TAC 9600 comparator is a band-independent device that acts as a subsystem-wide signal
collector, voter, and distributor. The ASTRO-TAC 9600 comparator is designed for use in ASTRO
25 simulcast trunking systems that use a 9600 bps control channel. With multiple base stations
operating on the same frequency, it is possible for field radios to simultaneously hit multiple sites
when transmitting. The ASTRO-TAC 9600 comparator checks the incoming voice traffic signals and
selects the best one or develops a composite signal of the best ones for simulcast retransmission by
building a composite signal and by simultaneously transmitting an identical RF signal from multiple
sites within the system, both coverage and signal quality are enhanced.
An Ethernet interface in its control module provides the ASTRO-TAC with the mechanism to take the ASTRO
audio, sent by the base station receivers connected to it, as its input and provide audio packets as its output that
is ready for transmission over the IP-based network. The Ethernet interface sends these audio packets through
the prime site LAN, the site switches, and router to the master site for distribution to other sites and zones.
Simulcast Remote Sites

Simulcast remote sites use base radios that transmit on frequencies identical to those used by other
remote sites within the simulcast subsystem. When a signal to be transmitted is received at the
controlling zone, it is routed to a base radio at the remote sites in the subsystem. The controlling
zone is the zone in which the call originated. At a predetermined time, all of the assigned base
radios broadcast the signals simultaneously on the same frequency.
The receivers at the remote sites in the subsystem pick up signals transmitted by radios and route
them to a central location called the simulcast prime site. The audio signals for a particular call
are sent to a signal comparator at the prime site, where the best quality signal is determined. The
best quality audio signal is passed from the comparator to the base radios at each remote site in the
subsystem and to the master site for distribution to the rest of the system.
The simulcast remote site configurations include the following:
Simulcast Remote Site supporting the simulcast subsystem operating

in the 700 MHz and 800 MHz bands
Simulcast Remote Site (VHF/UHF) supporting the simulcast subsystem
operating in the VHF/UHF bands
Receive Only Remote Site supporting the simulcast subsystem with receive
only sites operating in the VHF/UHF bands only
Simulcast remote sites include radio frequency equipment for communication of signals to and from the radio
subscriber units, an Ethernet switch for LAN management and service access, a site router for a high speed
link of management information, a channel bank for audio and control channel interface to the comparators at
the prime site, and a time reference for the base radios to ensure proper simulcast operation.
Figure 2-8,"Simulcast Remote Site for the Simulcast Subsystem Supporting 700 MHz, 800 MHz
or VHF/UHF Bands" on page 2-17 shows the simulcast remote site used to support a simulcast
subsystem operating in the 700 MHz, 800 MHz or VHF/UHF bands. For more details on the
simulcast remote sites, see Chapter 5, "Radio Frequency Subsystems."
2-16 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Single Transmitter Receiver Voting Subsystem
Figure 2-8 Simulcast Remote Site for the Simulcast Subsystem Supporting 700 MHz, 800
MHz or VHF/UHF Bands
Single Transmitter Receiver Voting Subsystem
The Single Transmitter Receiver Voting (STRV) subsystem covers a single geographic area with a
single transmitter and provides radio communication support in the VHF/UHF frequency bands. An
STRV subsystem contains a single transmit site and at least one or more STRV remote sites. An
STRV subsystem must include an STRV prime site, an STRV transmit remote site (if not already
colocated with the STRV prime site), and STRV receive-only remote sites.
The STRV subsystem contains many of the same components found in a simulcast
subsystem, but the STRV subsystem does not require simulcast site reference devices,
because simultaneous transmission (time launching of signals) from multiple transmitters
is not required in a single transmitter subsystem.
For more details on the STRV subsystem, see Chapter 5, "Radio Frequency Subsystems."
Telephone Interconnect Subsystem
The telephone interconnect subsystem is a functional part of the ASTRO 25 trunking system
with components primarily associated with the master site.
6881009Y05-O April 2004 2-17

Data Communication Subsystem Chapter 2: What Is an ASTRO 25 Trunking System?
The ASTRO 25 Telephone Interconnect subsystem provides a means to connect the radio system with
the Public Switched Telephone Network (PSTN). This subsystem enables a subscriber to initiate and
receive calls through the PSTN. A Private Branch Exchange (PBX) is used to provide the telephone
interconnect and a control signaling server to provide all other system requirements.
The PBX performs all of the telephone switching functions and number handling operations
required by the PSTN. The PBX-to-radio system interface is accomplished with the
Adjunct Control and Signaling Server (ACSS).
The PBX in the telephone interconnect subsystem can interface with another PBX for tie trunk support.
Figure 2-9 Telephone Interconnect Subsystem
Data Communication Subsystem
The data communication subsystem supports the data communication features and functions in your
ASTRO 25 trunked communication system. The data communication subsystem handles the IP transport
of data over trunked data channels that currently exist in the same pool of channels used to support voice
communication. The data communication subsystem provides a wireless extension of your data network
through the Motorola radio communication network to mobile data devices. A packet data channel (PDCH)
represents the radio frequency resources used for the IP transport of data in the integrated voice and
data communication system. Characteristics associated with the IP transport and handling of a PDCH
are similar to those associated with the IP transport of voice. For more details on data communication
and integrated voice and data, see Chapter 10, "Integrated Voice and Data."
2-18 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Network Security Subsystem
Figure 2-10 Data Communication Subsystem
Network Security Subsystem
The network security subsystem for the ASTRO 25 trunked communication system provides components
contributing to protecting system information and communication assets. From a functional subsystem
perspective, the network security subsystem consists of hardware and software components contributing
to the protection of the system, as well as the security management activities and practices required
to meet network security objectives for your system. Network security products and services for
the ASTRO 25 system can be grouped into the following categories:
Core Security Management Server A required set of hardware and software

components used to administer and control system access and to manage
various aspects of the network firewall.
Network Interface Barrier An optional set of components providing boundary
enforcement and attack detection features to supplement protection of your system.
Network security components include the core security management server, the firewall server,
and the intrusion detection system sensor as illustrated in Figure 2-11. For more details on
network security, see Chapter 8, "Network Security."
6881009Y05-O April 2004 2-19

Other Band Trunking Chapter 2: What Is an ASTRO 25 Trunking System?
Figure 2-11 Network Security Subsystem
Other Band Trunking

Some ASTRO 25 systems support only 800 MHz trunking. However, other ASTRO 25 systems
support trunking in bands other than 800 MHz, such as the VHF, UHF, and 700 MHz bands,
either as standalone systems, or as mixed-band systems.
This section provides a basic description of Other Band Trunking (OBT). Hardware changes
necessary to accommodate other band trunking are explained in Chapter 11, "Other Band
Trunking," which provides a detailed description of the concepts that make it possible for
radios to communicate in a multi-band environment.
Operating Bands
The OBT feature allows trunking operations in frequency bands other than 800 MHz. These other bands
include frequency ranges in the VHF band (136-174 MHz) and the UHF bands (403-470 and 450-512 MHz).
2-20 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Subscriber Support
The VHF and UHF bands are further categorized as follows:
VHF: 136-174 MHz (full band range) with two possible sub-band ranges
of 136-162 MHz or 146-174 MHz.
UHF Full Band Range 1: 403-470 MHz (full band range) with two possible
sub-band ranges of 403-433 or 438-470 MHz.
UHF Full Band Range 2: 450-520 MHz (full band range) with two possible
sub-band ranges of 450-482 or 470-520 MHz.
The major new functions added by ASTRO 25 for OBT support include:
APCO Project 25 control and traffic channel standards
Overlapping band plans
New frequency ranges in the 380 MHz and 700 MHz bands.
Site controllers and ASTRO 25 Repeaters that allow inter-operation between individuals
and talkgroups that can only operate within one range of the full band (sub-band restricted)
and those that can operate in the full band (non-sub-band restricted).
Subscriber Support
This section describes the following:
VHF band and sub-band ranges

UHF band 1 and sub-band ranges
UHF band 2 and sub-band ranges
VHF Band and Sub-Band Ranges
The VHF Full Band Range (136-174 MHz) is supported by the Motorola XTS5000 and XTS2500
portable radios. The ASTRO Spectra Plus mobile radio currently can only support one sub-band
at a time, either the 136-162 MHz or the 146-174 MHz.
If an RF site has frequencies running from 136-174 MHz, the XTS5000 and XTS2500 will operate
as non-sub-band restricted radios operating in the full 136-174 band range, while all ASTRO Spectra
Plus mobiles can only operate in one of the two possible sub-bands at such a site.
UHF Band 1 and Sub-Band Ranges
The UHF Full Band Range 1 (380-470 MHz) is supported by Motorolas XTS5000 and XTS2500
portable radios. ASTRO Spectra Plus mobiles radios currently can support operation in only one
sub-band at a time, either the 403-433 MHz or the 438-470 MHz sub-band.
If an RF site has frequencies running from 380-470 MHz, the XTS5000 and XTS2500 will operate as
non-sub-band restricted radios operating in the full 380-470 MHz band range while all ASTRO Spectra
6881009Y05-O April 2004 2-21

UHF Band 2 and Sub-Band Ranges Chapter 2: What Is an ASTRO 25 Trunking System?
UHF Band 2 and Sub-Band Ranges
The UHF Full Band Range 2 (450-512 MHz) is supported by the Motorola XTS5000 and XTS2500
portable radios. ASTRO Spectra Plus mobiles radios currently can support operation in only one
sub-band at a time, either the 450-482 MHz or the 482-512 MHz sub-band.
If an RF site has frequencies running from 450-512 MHz, the XTS5000 and XTS2500 will operate as
non-sub-band restricted radios operating in the full 450-512 MHz band range, while all ASTRO Spectra
Radio Frequency (RF) Subsystem Support

Table 2-1 summarizes the communication frequency bands supported by each radio
frequency subsystem in an ASTRO 25 system.
Table 2-1 RF Subsystem Frequency Bands Supported
RF Subsystem Frequency Bands Supported

ASTRO 25 Repeater Sites 800 MHz, 700 MHz, UHF, VHF
IntelliRepeater Subsystem 800 MHz, UHF, VHF
Simulcast Subsystem (Multisite subsystem) 800 MHz, 700 MHz, UHF, VHF
Single Transmitter Receiver Voting UHF, VHF
Subsystem (Multisite subsystem)
For over-the-air rekeying (OTAR) and secure communications, see ASTRO 25 Trunked Integrated
Voice and Data System Release 6.4/6.4 SE Managing Secure Communications (6881009Y65).
Audio Quality Optimization

Audio quality optimization is the process of adjusting, setting, and configuring a piece of equipment to
transport audio signals (data) with as little distortion and attenuation as possible to ensure maximum
clarity to all subscribers. Traditionally, this meant that physical adjustments, such as adjusting a
potentiometer (mechanical or electronic), had to be performed. With the advent of digital systems, most
adjustments are software controlled, and manual adjustments are no longer required.
2-22 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Audio Quality Optimization
Table 2-2 presents a list of devices that are part of the audio path in an ASTRO 25 systems.
The table indicates if the device requires level adjustments.
Table 2-2 ASTRO 25 System Audio Optimization Requirements
Device Level Setting

Router No
Switch No
Channel Bank No
Central Electronics Bank (CEB) No
Ambassador Electronics Bank (AEB) No
Motorola Gold Elite Gateway (MGEG) No
ASTRO 25 Repeater No
Simulcast Base Radio No
Simulcast Site Controller (SSC) No
ASTRO-TAC 9600 Comparator No
Radios - Mobile and Portable No
Elite Console Workstation (microphone audio) Yes
Ethernet Switch No
Wide Area Network (WAN) Switch No
Customer Service Unit (CSU) No
Digital Access Cross-connect Switch (DACS) No
PBX Yes
Optimization of an ASTRO 25 system is a drastically different and much simpler process when compared
to level adjustments in previous systems. Once the proper parameters are entered in the configuration
screens of the appropriate devices, the devices themselves will use those parameters to maintain optimal
signal quality as the audio travels through the transport system. Parameters can be verified periodically
but resetting is not necessary unless the equipment is replaced or upgraded.
6881009Y05-O April 2004 2-23

System Summary Chapter 2: What Is an ASTRO 25 Trunking System?
System Summary

Table 2-3 summarizes the general system capabilities on an ASTRO 25 system while
Table 2-4 summarizes the systems capacity.
Table 2-3 ASTRO 25 System Capability
Feature Support
Digital frequency band supported 800 MHz, 700 MHz, UHF, VHF
Analog frequency band supported for mutual aid 800 MHz, UHF, VHF
Digital subscriber encryption types supported DES/DES-OFB, DES-XL,
DVP-XL, DVI-XL, AES, ADP
Trunking control channel rate 9600 bps
Digital Vocoder IMBE
Table 2-4 ASTRO 25 System Capacity
Feature Support
Maximum number of zones 7
Maximum number of sites/subsystems Up to 100 per Zone (See Note
below)
Number of individual IDs 64,000
Number of talkgroup IDs 16,000
Maximum channels per RF ASTRO 25 Repeater Site 28
Maximum channels per RF simulcast subsite 30
The IDs for simulcast subsystem, single transmit receive only subsystem, and IntelliRepeater sites
can be numbered from 1 to 64, while ASTRO 25 Repeater sites can be numbered from 1 to 100.
2-24 6881009Y05-O April 2004

Chapter
3
Network Topology

This chapter describes network concepts applicable to an ASTRO 25 system.
Local Area Network

A local area network (LAN) is a data communications system designed to link computers and peripheral
devices such as printers and modems. LAN cabling has a limited usable distance of up to 115 m (378 ft.)
and is best used within a building or campus environment. The advantage of using a LAN is that users can
share peripheral devices connected to the LAN instead of having those devices attached to each computer.
Network users can also share information stored in the network server, such as databases and programs.
In addition, network users can communicate with each other through messaging or E-mail.
Ethernet Technology
Ethernet technology refers to a LAN used to connect computers and peripheral devices (such as
printers, modems) so they can be shared by users of the network. Originally developed to run
at 10 Mbps, Ethernet networks can now run at 100 Mbps. Ethernet can use twisted pair, coaxial,
or fiber optic cabling with BNC, RJ45, or fiber optic connectors.
The Institute of Electrical and Electronic Engineers (IEEE) created the 802.3 standard for the operation of 10
Mbps networks. Based on the type of cabling used, the following is a list of the different versions of 802.3:
10Base-5 - Thick Ethernet
10Base-2 - Thin Ethernet
10Base-T - Twisted pair Ethernet
10Base-FL - Fiber optics
Ethernet accesses data using Carrier Sense Multiple Access with Collision Detection (CSMA/CD).
This method allows multiple users to access the network through a common cable. All devices
attached to the network check for transmissions in progress, signals are checked at the start of
transmission and during transmission. Signals are sent if no other transmission is detected; otherwise,
the transmission is delayed. Collision detection is applied when two or more devices transmit at the
6881009Y05-O April 2004 3-1

Shared Ethernet LAN Chapter 3: Network Topology
same time. A device knows if a collision occurred when it does not receive its own transmission
back. Each device stops transmission and attempts to retransmit after waiting a certain amount of
time, which is different for each device and determined by an algorithm.
Shared Ethernet LAN

A shared Ethernet LAN (10Base-2 LAN) is a system in which all transmitting stations on the LAN share
the same common transmission facility. Stations transmit when they have data to send and recover
from the failures that occur when two stations transmit simultaneously. Because of the contention
that results when a number of stations share the same transmission facility, all the transmission
capacity is not always available to two stations that need to communicate.
Star Topology
Another type of LAN topology, generally known as a star topology (also referred to as 10/100Base-T), is one
in which the end points on a network are connected to a common central device by point-to-point links. The
information arriving at the common device is broadcast to all the end point devices; each device is responsible
for determining whether the information is intended for it or not. Characteristics of the star topology include:
Twisted pair cable is used for the links between the central and end devices.
Link isolation is usedif a fault occurs on one link, the other links remain unaffected.
A hub serves as the central device.
The end devices share the available bandwidth.
Switched Ethernet
Switched Ethernet is a 10Base-T system in which all devices are connected to a central distribution point
through their own cable. With switched Ethernet, the central, passive hubs used to form conventional Ethernet
unshielded twisted pair (UTP) LANs are replaced with intelligent switches. The switches allow each sending
computer to be temporarily directly connected to a single receiving computer. The switch acts as the central
point of a star topology network. Therefore, the two computers do not experience collisions, and the full
bandwidth of the transmission medium is available to any two stations that wish to communicate.
3-2 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Switched Ethernet
Figure 3-1 Switched Ethernet
Both shared and switched Ethernet technologies are used to allow equipment to communicate within an
ASTRO 25 zone. An ASTRO 25 system uses LAN transmission to handle the flow of intrazone data.
It also uses wide area network (WAN) transmission to handle the flow of interzone data.
Three basic types of information are exchanged in an ASTRO 25 system: voice, call control, and
network management traffic. In an ASTRO 25 system, network management and control information
must be exchanged between devices installed within each individual zone, and between devices
installed in different zones. Ethernet and Frame Relay are the primary communication technologies
used to implement high-speed exchanges of management, control, and voice traffic among the various
devices within an individual ASTRO 25 zone. Asynchronous Transfer Mode (ATM) technology
is added when any information must be exchanged between zones.
Ethernet hubs are often used to implement shared Ethernet communication between pieces of
equipment that do not require the full, dedicated bandwidth of the Ethernet transmission medium.
Ethernet switches are used to implement high-performance, switched Ethernet connections when the
full Ethernet bandwidth is required between interconnected equipment.
Routers are used to implement high-level transport connections between network nodes in an ASTRO
25 system. Routers make the LAN connections and WAN transmission facilities transparent to the
network nodes that may be communicating either within the same zone or between one zone and
another. Routers also allow alternate paths to be implemented between interconnected equipment to
permit the ASTRO 25 system to continue operating should specific physical links fail.
6881009Y05-O April 2004 3-3

Wide Area Network Services Chapter 3: Network Topology
Wide Area Network Services

The three types of WAN services used are: leased lines (point to point), packet-switched , and circuit-switched.
Leased lines:
Leased lines provide a dedicated single path through a telephone company from one
location to another. Speeds range from 56 kbps to 1.544 Mbps (T1). Fractional T1
speeds are between 128 kbps and 768 kbps. Leased lines provide dedicated service
and no call setup time, but the bandwidth is not flexible. A 4-wire analog leased
line provides slower speeds, generally up to 33.6 kps.
Packet-switched networks:
Packet-switched networks break messages apart into packets and tag each packet with
source and destination addresses. Packet-switching has several advantages:
Packets can be routed around network problems.
They can maximize link efficiency by making optimal use of bandwidth.
They can be more cost effective than leased lines.
Frame relay switching provides high-speed packet-switching over Permanent Virtual
Circuits (PVCs) referenced by Data Link Connection Identifiers. Local Management
Interface (LMI) extensions provide additional management capability. Frame relay includes
a cyclic redundancy check (CRC) algorithm that detects corrupted bits. Any needed
retransmission is performed at higher protocol layers such as TCP.
Circuit-switching:
Circuit-switching provides a dedicated path between a sender and receiver for the duration of
the communication. The advantages of the circuit-switched networks are dedicated circuits for
the call and customers do not pay for idle bandwidth. Disadvantages are call setup time and
potential under-utilization of the communication channel. Circuit-switching is useful for short
duration transmissions, for feeders to main sites or for backup/disaster recovery situations.
Asynchronous Transfer Mode
Asynchronous Transfer Mode (ATM) technology began with methods that divided the transmission
stream into small pieces called cells. Equipment within a public or private network was used
to accomplish this and has evolved to current ATM technology.
ATM protocols are typically used in an ASTRO 25 network for traffic that flows over WAN links. Frame
Relay technology is used to control transmission over the site links that connect remote IntelliRepeater,
ASTRO 25 Repeater sites, and simulcast subsystems to the master site within a zone. Frame relay is also
used between exit routers for interzone communication. ATM technology is used to control transmission
over the WAN links that interconnect separate zones in multizone ASTRO 25 system.
ATM is a form of packet-switched data transmission that uses fixed-sized packets called cells. As with
other forms of packet switching, an ATM network supports multiple logical connections multiplexed
over the same physical links. ATM assumes the use of reliable digital transmission facilities, such
as those provided by a good quality microwave or fiber optic system. The cell relay protocol does
not perform error correction, but leaves this function to a higher layer.
3-4 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Transport Methods and Protocols
By using a fixed cell size, as opposed to the variable-length frames used by many other protocols,
transmission overhead in an ATM network can be very low. ATM networks are typically characterized by
very high throughput, short delays, and very low error rates. A cell relay network can provide for highly
reliable data transport without the overhead of unnecessary error control functions.
Transport Methods and Protocols
The following sections describe transport methods and protocols.
10Base-T
10Base-T Ethernet uses unshielded twisted pair (UTP) cabling. The following list
demonstrates how the term 10Base-T is broken down:
10 = 10 Megabits per second (Mbps) operation
Base = Baseband operation
T = Twisted pair cable used for network connections
The Network Interface Card (NIC) performs the functions of a transceiver so that no external transceiver
is needed for stations. 10Base-T is used in a star topology configuration and thus requires the use
of a hub or concentrator. The hub serves as a central switching station, controlling the incoming
and outgoing signals. When using the star topology, if a station goes down it does not affect the
rest of the network. Typically, an RJ45 connector is found at each end of the UTP cabling. Pins
1 and 3 transmit data, pins 3 and 6 receive data, the other pins are not used.
100Base-T Ethernet, also called fast Ethernet, is an upgraded standard for connecting computers into a LAN.
It works just like 10Base-T Ethernet except that it can transfer data at a peak rate of 100 Mbps.
10/100Base-T networks installed in ASTRO 25 systems use twisted pair cable rather
than the more common UTP cable.
10Base-T Parameters and Wiring Rules
Maximum length per segment is 100 meters (330 feet).

Maximum of two devices per segment; one is the station and the other is the hub.
Maximum of two Inter-Repeater Links between devices without using a bridge
or switch. (A hub is considered a repeater.)
Hubs can connect to fiber optic or coax networks.
Unshielded twisted pair no less than category 2 is required for 10Base-T operation; however,
category 3 or higher is preferred. ASTRO 25 systems use category 5 cables.
UTP cabling is not recommended for areas with electromagnetic or radio
frequency interference (EMI/RFI).
NICs come with built-in transceivers so connections are made directly to the NIC.
NICs with standard AUI ports must use a twisted pair transceiver.
6881009Y05-O April 2004 3-5

10Base-2 Chapter 3: Network Topology
10Base-2
10Base-2 consists of a shared common cable with a 50 ohm terminator connected to each end.
Devices can be attached anywhere on the cable with the use of a T-connector. Transmission
signals are sent throughout the entire cable; however, only the device with the proper address
receives the signal. This is known as a bus topology and its disadvantage is that if a break occurs
anywhere in the cable the entire network connected to it is disabled.
Balanced Line Interface

A pair of wires is used to carry each signal in the balanced line interface; the data is encoded and decoded as a
differential voltage between the two lines. A sample truth table for a balanced interface is as follows:
Av-Bv < -0.2v =0
Av-Bv > +0.2v=1
Figure 3-2 Balanced Line Interface
A differential voltage interface, in principle, is unaffected by differences in ground voltage

between sender and receiver. Lines A and B will be affected almost identically by external
electromagnetic noise if they are close to each other. If the lines are also twisted together, neither
line is permanently closer to a noise source than the other. The well known twisted pair is
considered to be extremely effective in eliminating noise from the signal.
Balanced systems are used by LAN topologies like Ethernet and token ring. They can support line
speeds over 100 Mbps and work reliably at distances of several kilometers.
Fiber Optic Cable

An optical fiber can be used to carry data signals in the form of modulated light beams. In practice,
a number of individual optical fibers are often bound together into a fiber optic cable, with all of the
individual fibers surrounded by a protective sheath. Fiber optic cables have the potential for supporting very
high transmission rates. Transmission rates of up to 565 Mbps are routinely employed in commercially
available systems, and data rates of up to 200,000 Mbps have been demonstrated. Signals transmitted over
fiber optic cables are not subject to electrical interference. A fiber optic cable is also typically smaller
in size and lighter in weight than electrical cable. Fiber optic cable is sometimes used in an Ethernet
LAN to tie together hubs and switches when relatively long distances separate them.
Frame Relay
Frame Relay is a simplified form of connection-based, packet-switching service in which
synchronous frames of data are routed to destinations indicated on the header information. Frame
Relay assumes an error-free physical link and therefore does not guarantee data integrity. Error
detection and correction responsibility is left with the end devices.
3-6 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Virtual Circuits
Frame Relay uses the synchronous High-level Data Link Control (HDLC) frame format up to 4096
octets in length. Each frame contains a start flag, two octets that contain the information required for
multiplexing across the link, the data information (payload), two octets generated by a cyclic redundancy
check (CRC) of the rest of the octets between the flags, and the end flag.
Virtual Circuits
Permanent virtual circuits (PVCs) are used to form a connection between any two devices attached to
a Frame Relay cloud. Virtual circuits are logical, bi-directional, end-to-end connections that appear to
the user as dedicated links. Each PVC is given a unique number on each physical circuit along the path
between the two devices. This unique number is called a data link connection identifier (DLCI). The DLCI
is automatically changed to the PVC number of the next physical circuit as it passes through each switch
along the path. A DLCI is different from a network address in that it identifies a circuit in both directions,
not a particular endpoint. A frame contains only one DLCI, not a source and destination.
In general, the only DLCI numbers you see are those numbers assigned to the physical circuits on the
perimeter of the Frame Relay cloud. DLCIs only have local significance and represent end-to-end virtual
connections that have a permanently configured switching path to a certain destination. Thus, by having a
system with several DLCIs configured, you can communicate simultaneously with several different sites.
Flow Control
Although there is no flow control, Frame Relay indicates that the network is becoming congested by means of
the Forward Explicit Congestion Notification (FECN) and Backward Explicit Congestion Notification (BECN)
bits in data frames. These are used to tell the application to slow down before packets start to be discarded.
High-Level Data Link Control
HDLC is responsible for the error-free movement of data between network nodes. The job of the
HDLC layer is to ensure that data passed up to the next OSI layer has been received exactly as
transmitted, error free, without loss and in the correct order. Flow control is another feature of HDLC;
it ensures that data is transmitted only as fast as the receiver can accept it.
There are two distinct HDLC implementations: HDLC NRM and HDLC Link Access Procedure Balanced
(LAPB). LAPB is a bit-oriented synchronous protocol that provides data transparency in a full-duplex
point-to-point system. It supports peer-to-peer links, neither end of the link plays the role of a permanent
master station. HDLC NRM (also known as SDLC) has a permanent primary station with one or more
secondary stations. References to HDLC usually mean LAPB or some variation of LAPB.
Most modern WAN framing is built on the HDLC frame structure. An HDLC frame
has the following general structure:
Flag field: A bit sequence used to mark the start and end of the frame.
Address field: It is possible to have multiple stations connected to a single wire. The address
field, usually one byte, is used to indicate the sender or intended receiver of the frame.
Control field: One or more bytes. It contains information on the type of frame (for
instance, user data or link control). Often it contains a rotating sequence number that
allows the receiver to check that no frame has been lost.
Data field: Contains the information to be delivered to the destination point.
The data in this field is completely transparent.
6881009Y05-O April 2004 3-7

Open Shortest Path First Chapter 3: Network Topology
Cyclic Redundancy Check: Following the data field are two bytes comprising
the CRC. The value of these bytes is the result of an arithmetic calculation based on
every bit of data between the flags. When the frame is received, the calculation is
repeated and compared with the received CRC bytes. If the answers match, there is a
very high degree of certainty that the frame has been received exactly as transmitted.
The received frame is usually discarded if there is a CRC error.
Open Shortest Path First

Open Shortest Path First (OSPF) is a link state routing protocol that is used to advertise routing
tables to other devices in the network. OSPF in the ASTRO 25 network is used to advertise routes
leading from the remote sites to the devices at the master site. In order to do this, OSPF must be
able to advertise both its static routes and the routes that it has learned through OSPF. In order
to advertise static routes, the Static Policy feature has to be enabled.
In the OSPF routing algorithm, routers exchange information about their own data links and then use that
information to develop a map of the network topology. Routes are calculated based on the topology.
Periodically, routers test neighbor availability, and broadcast status information about links. A router
can also request information about specific links. OSPF allows for multiple routes to a destination
based on different types of service, such as low delay or high throughput.
OSPF is the routing protocol most often used in an ASTRO 25 network for intrazone routing (routing that
takes place within a zone). OSPF is the Interior Gateway Protocol (IGP). The Border Control Protocol (BGP)
is used for interzone routing (routing between zones). BGP is the Exterior Gateway Protocol (EGP).
Path Diversity
Path diversity is a term used to describe the capability of a system to route information
through alternate or multiple network paths to assure reliability. An example of a system that
uses alternate paths is a system with redundant routers.
ASTRO 25 systems use redundant routers at the master site and, as an option, the design can also implement
redundant site routers at the subsystem level. Redundant site routers, together with redundant transport
paths (T1s), provide higher reliability than the single router and single T1 implementation.
Simple Network Management Protocol

The Simple Network Management Protocol (SNMP) is an application-layer protocol that facilitates the
exchange of management information between network devices. It is part of the Transmission Control
Protocol/Internet Protocol (TCP/IP) protocol suite. SNMP enables network administrators to manage
network performance, find and solve network problems, and plan for network growth.
An SNMP managed network consists of the following three key components: managed
devices, agents, and network management systems (NMSs).
Managed device: A managed device is a network node that contains an SNMP agent
and resides on a managed network. Managed devices collect and store management
information and make this information available to the network management system
using SNMP. Managed devices, sometimes called network elements, can be routers,
access servers, switches, bridges, hubs, computer hosts, or printers.
Agent: An agent is a network-management software module that resides in a
managed device. An agent has local knowledge of management information and
translates that information into a form compatible with SNMP.
3-8 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Static Routing
Network management system: An NMS executes applications that monitor and control
managed devices. NMSs provide the bulk of the processing and memory resources required
for network management. One or more NMSs must exist on any managed network.
SNMP is used to monitor and manage some of the features of the network equipment in an ASTRO
25 system. This must be set up properly in the initial configuration in order to ensure proper
communication between the SNMP management station and the equipment.
Static Routing
Static routing is often used in simple networks in which routes can be pre-configured and do not change during
system operation. When static routing is used, routing tables in the routers are pre-configured and are not
dynamically updated. Static routing is often used in the routers that are connected to the intrazone site links.
Asynchronous Communications
Asynchronous communication is the transmission of data between two devices which are not synchronized
with one another through a clock or timing mechanism. With asynchronous communication, the receiving
device must be ready to accept the communication at any time when it arrives from the transmitting
device. For example, asynchronous transmission is used to transmit characters from a keyboard or terminal
device as the user periodically presses keys. The receiving device or system waits for the each keypress.
Modems are typically asynchronous devices and the console interface ports on the Packet Data Router
(PDR) and Radio Network Gateway (RNG) are asynchronous communication ports.
Synchronous Communications
Synchronous communication, in contrast to asynchronous communication, is a communication method
where the data transmission is timed precisely into a stream and the start of the communication is
identified using a clock or timing mechanism. The Ambassador Electronics Bank (AEB), when used in
your system, contains system timer boards to support the synchronous communication requirements
of the Central Electronics Bank (CEB), console equipment, and telephone interconnect devices. In
synchronous communications, information is sent as frames of large data blocks. Frame sizes vary
from a few bytes through 1500 bytes for Ethernet or 4096 bytes for most Frame Relay systems. The
clock is embedded in the data stream encoding, or provided on separate clock lines such that the sender
and receiver are always in synchronization during a frame transmission.
TCP/IP Protocols
The following are brief descriptions of the major protocols defined by the TCP/IP protocol suite
that are used in transporting data in an ASTRO 25 system.
Transmission Control Protocol
The Transmission Control Protocol operates in the TCP/IP transport layer. TCP provides a
connection-oriented, reliable data transfer service used to transmit an unstructured stream of data between
two end systems. Before data delivery can begin, the TCP user at one end requests a connection, both the
TCP protocol itself and the TCP user at the other end agree, and TCP establishes the connection.
User Datagram Protocol
The User Datagram Protocol (UDP) operates in the TCP/IP Transport layer. It permits packets to be sent
between end systems with a minimum of protocol overhead. With UDP, delivery is not guaranteed. There is
no checking for missing, out-of-sequence, or duplicate packets, and no acknowledgments are sent.
6881009Y05-O April 2004 3-9

Internet Protocol Chapter 3: Network Topology
Internet Protocol
The Internet Protocol is used by both UDP and TCP. IP operates below UDP and TCP in
the TCP/IP Internet layer. IP routes packets across interconnected networks and performs
packet segmentation and reassembly functions.
Figure 3-3 TCP/IP Protocol Relationship
An ASTRO 25 network makes use of the IP, UDP, and TCP protocols in the TCP/IP suite to
handle network layer and transport layer communication functions.
The TCP/IP protocols allow the ASTRO 25 network to be logically divided into subnetworks, or
subnets, which permit a large network to be subdivided into logical sections. The devices in one subnet
communicate with devices in the other subnets through the Ethernet switches and routers.
The Ethernet switches used in an ASTRO 25 system support communication within multiple independent
subnets, the routers do not forward traffic to a subnet unless it is intended for a device in that subnet. The use
of Ethernet switches and routers eliminates unwanted traffic and improves the performance of the network.
T1 Carrier
A T1 carrier is a telecommunications facility designed to carry digital information at a bit rate of 1.544 Mbps.
In conventional telecommunications, the most common use for a T1 carrier is to connect central offices within
an individual telephone company. Telephone companies also lease T1 carriers to their customers for their
own private purposes. Most ASTRO 25 systems in the United States and Canada use T1 circuits to transmit
digitized voice, management, and control traffic between zones. The Frame Relay and Cell Relay protocols
provide the means for exchanging information over the T1 communication facilities that connect remote zones.
Various types of transmission media can be used in implementing a private T1 facility, such as various
types of privately installed cabling or point-to-point microwave circuits.
3-10 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System E1 Carrier
A T1 circuit is divided into 24 time slots, each of which implements a separate communication
channel that can support a bit rate of 64,000 bps. Each of these individual channels is
referred to as a Digital Signal Level zero (DS0) channel.
The term framing refers to the order in which user bits and other information is transmitted over a
physical transmission medium. A T1 frame comprises a total of 193 bits. Each of the 24 inputs is
assigned a fixed time slot; the T1 uses a time-division multiplexing technique to divide the capacity
of the carrier into 24 channels. The framing bit is used to create a pattern to help synchronize the
equipment. Figure 3-4 illustrates the format of the T1 transmission frame.
Figure 3-4 T1 Carrier
E1 Carrier
An E1 carrier is a telecommunications facility designed to carry digital information at the rate of
2.048 million bits per second (Mbps). The E1 carrier originates from the Conference of European
Postal and Telecommunications (CEPT) administration. An E1 has 30 digital channels (64 Kbps)
to carry voice or data information, plus two other 64 kpbs digital channels; one carries signalling
information and another carries framing (synchronization) and maintenance information. The
increased transmission rate is the primary advantage for employing equipment capable of handling
E1 carrier transmission signals. Figure 3-5 illustrates the format of the E1 transmission frame. For
network cabling recommendations, see "Network Cabling" on page 3-12.
Figure 3-5 E1 Carrier
Virtual LANs
The use of intelligent switches instead of passive hubs to form Ethernet networks permits the use of
Virtual LAN (VLAN) technology. With VLAN technology, a network designer or network administrator
can form Virtual Ethernet segments. In a conventional Ethernet LAN, a group of communicating stations
were physically connected to a shared hub or a shared cable segment. All members of the group needed
to be within 100 cable meters of that groups hub. If one of the group members had to move to a new
location, cabling changes would have to be made to accommodate the move.
6881009Y05-O April 2004 3-11

V.35 Interface Chapter 3: Network Topology
VLAN technology allows a system administrator to assign each port of a switch to members of
different Ethernet segments. In most cases, a single switch with VLAN capability can replace
a number of shared Ethernet hubs. Use of an Ethernet switch also increases the performance of
the individual segments. The zone master sites in an ASTRO 25 system use Ethernet switches
that support VLAN technology in an extended stackable configuration.
V.35 Interface
The V.35 interface was originally specified by CCITT as an interface for 48 kbps line transmissions.
It was replaced in 1988 by recommendations V.10 and V.11.
V.35 has been adopted for all line speeds above 20 kbps. It is a mixture of balanced and
common earth signal interfaces. The control lines including DTR, DSR. DCD, RTS and CTS
are single wire common earth interfaces, functionally compatible with RS-232 level signals.
The data and clock signals are balanced, like RS-422 signals.
The control signals in V.35 are common earth single wire interfaces because these signal levels are mostly
constant at low frequencies. The high-frequency data and clock signals are carried by balanced lines.
Network Cabling

Various types of cables are to be used based on the type of link. See Table 3-1 for a list of cable and link types.
Table 3-1 Network Cables and Link Type
Link Cable Type

10 Mbps (10Base2) RJ58/U 50 Ohm Coax or Equivalent
10 Mbps STP Ethernet Minimum CAT5, Preferred CAT5E
100 Mbps STP Ethernet Minimum CAT5, Preferred CAT5E
Single T1/E1 Link Minimum, UTP; Preferred STP
Single E1 Link Minimum, UTP; Preferred STP; 120 Ohm
Single E1 Link Minimum, RJ59/U 75 Ohm Coax or Equivalent
Multi T1/E1 Links Minimum, UTP; Preferred STP (Tx and Rx pairs must be separate)
Multi E1 Links Minimum, UTP; Preferred STP (Tx and Rx pairs must be separate)
V.24 links UTP
600 ohm balance lines UTP
The site has to meet R56 Grounding and Bonding standards before using STP Ethernet Cables.
STP Ethernet cables are required to use metallized connectors.
All T1/E1 shielded cables must be grounded at one end only where you cannot guarantee
what the PTT/Telco is using for a ground reference.
3-12 6881009Y05-O April 2004

Chapter
4
Hardware Functional Description

The ASTRO 25 system consists of a complex network of servers, computer workstations, high-speed
LAN/WAN devices, sophisticated databases, and management software.
This chapter discusses the hardware that is associated with an ASTRO 25 system in the following topics:
"Master Site" on page 4-1
"Transport Network" on page 4-11
"Network Management Subsystem" on page 4-46
"Console Operator Subsystem" on page 4-59
"Telephone Interconnect" on page 4-83
"Network Security Components" on page 4-89
"Radios" on page 4-92
"Backup Power Recommendations" on page 4-97
Master Site

An ASTRO 25 system can be single zone or multiple zone. A zone has a master site that contains the
computing backbone for that zone. The master site contains the following subsystems:
Call processing
Network management
Telephone interconnect
Dispatch
The master sites contain all the components necessary for controlling calls within a zone and for communicating
with other zones to manage interzone calls (calls that go between zones). In addition, the master sites provide
the hardware and software components that are used for network management and system configuration.
All the components that communicate over Ethernet are connected through a central switch called
the master site Ethernet LAN switch. This switch provides two separate internal LANs which are
integrated to provide redundant links for critical network traffic.
6881009Y05-O April 2004 4-1

MZC 3000 Zone Controller Chapter 4: Hardware Functional Description
One of the master sites in a multiple zone system is generally designated as the system master
site. Although not necessary to physically locate them in any master site, the User Configuration
Server (UCS) and System Statistics Server (SSS) are generally located at the system master site.
There is only one UCS and one SSS per system; they are not duplicated for each zone. A single
zone system does not require an SSS, but may have a Zone Statistics Server (ZSS) instead.
An example of a master site is shown in Figure 4-1.
Figure 4-1 ASTRO 25 Master Site
MZC 3000 Zone Controller
The MZC 3000 is responsible for processing calls, managing audio paths, controlling zone infrastructure,
and providing services to subscribers and console operators. The MZC 3000 directs and controls most
of the components in the zone. The critical components shown in Figure 4-1 are:
MZC 3000 zone controller
Ethernet switch
Telephone Interconnect Device (TID)
Ambassador Electronics Bank (AEB)
4-2 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System MZC 3000 Zone Controller
Wide area network (WAN) switch

Console subsystem
Network management servers and various routers used for control and audio information
The MZC 3000 zone controller, as shown in Figure 4-2, is equipped with two CompactPCI chassis with
Ethernet ports that interface with the various system devices. The MZC 3000 includes redundant zone
controllers connected to the network through the LAN switch. This LAN switch is used to switch system
resources between the zone controllers and provide high availability call management within the zone.
While both zone controllers are powered and enabled at the same time, only one zone controller is actively
participating in call processing tasks at any one time while the second controller is in standby mode.
A zone controller may have a redundant state of either active or standby. The zone controller
responsible for call processing is in the active state. The zone controller that is not actively processing
calls in the zone is in the standby state. System information that is necessary for call processing
is downloaded to both zone controllers. The zone controllers include hardware for storing data,
controlling zone activities, and communicating with zone resources.
6881009Y05-O April 2004 4-3

Controller Interfaces Chapter 4: Hardware Functional Description
Figure 4-2 MZC 3000 Zone Controller - Front View
Controller Interfaces
As shown in Figure 4-1, the MZC 3000 has four primary connections with the radio network:
Ethernet connections for site and interzone call processing control links
Ethernet connection for zone controller network management
4-4 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Site Interfaces
Ethernet connection to the Telephone Interconnect Device (TID)

User interface
Site Interfaces
Each redundant zone controller in ASTRO 25 systems interfaces to the site links, through the LAN and
WAN switches, to provide more reliable site communications. The ASTRO 25 systems support ASTRO
25 Repeater sites, digital simulcast subsystems, and single transmitter receiver voting subsystems.
Network Manager Interface
Each redundant zone controller is connected to the Private Radio Network Management
(PRNM) subsystem through an IP interface.
Telephone Interconnect Interface
In the ASTRO 25 system, the zone controller can be connected to an optional Telephone Interconnect
subsystem using an IP interface. Each zone configured with a telephone interconnect subsystem
can support up to 24 simultaneous telephone interconnect conversations using a T1 interface, and
up to 30 telephone interconnect conversations using an E1 interface.
Zone Controller User Interface
In addition to the system maintenance interface, the system user is able to evaluate the operation of the MZC
3000 using the zone controller user interface. Each zone controller supports a serial interface. The zone
controller supports fault and configuration information. Access to the zone controller is password protected.
MZC 3000 Zone Controller Architecture

Figure 4-3 and Figure 4-4 illustrate the MZC 3000 zone controller components, front and rear view.
6881009Y05-O April 2004 4-5

MZC 3000 Zone Controller Architecture Chapter 4: Hardware Functional Description
Figure 4-3 MZC 3000 Zone Controller Components - Front View
4-6 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System CPU Card and Transition Card
Figure 4-4 MZC 3000 Zone Controller - Rear View
CPU Card and Transition Card
Figure 4-5 shows the Central Processing Unit (CPU) card with its connectors, LEDs, and buttons.
It also shows the CPU Transition card with its connectors.
6881009Y05-O April 2004 4-7

Ethernet Card and Transition Card Chapter 4: Hardware Functional Description
Figure 4-5 CPU Card and Transition Card
The CPU card manages all operations within the zone controller and provides processing and
control for the zone controller application. The zone controller application handles all tasks for call
processing, resource management, and continuous resource availability.
The CPU card provides the required processor and memory capabilities, two on-board Ethernet ports,
four on-board serial ports, and a series of LEDs for status and notification information. The CPU card
communicates to other cards over the backplane and communicates to the peripherals through a SCSI interface.
The transition card interfaces directly with the CPU card and provides additional external connections.
Transition modules are necessary to provide through-connections in a CompactPCI environment and
are inserted opposite their corresponding cards in the back of the zone controller.
Ethernet Card and Transition Card
Figure 4-6 illustrates the Ethernet card, its Transition card, and corresponding LEDs and connectors.
4-8 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Alarm Card
Figure 4-6 Ethernet Card and Transition Card
The Ethernet card provides eight, 10/100 Ethernet interfaces for the zone controller. The Ethernet
transition card provides one RJ-45 port per channel. Both the Ethernet card and its Transition
card provide LEDs for link/activity feedback for each port.
In conjunction with the Ethernet ports on the CPU card, the ports on the Ethernet card
are used for connection to the network manager, the interconnect devices for ASTRO 25,
remote sites, interzone communication, and MGEGs.
Additional Ethernet ports are located on the CPU transition card.
Alarm Card
Figure 4-7 illustrates the alarm card and its components.
6881009Y05-O April 2004 4-9

Tape Drive Chapter 4: Hardware Functional Description
Figure 4-7 Alarm Card
The alarm card, also called the system monitor board (SMB), provides LED indication of power
supply and other fault conditions in the zone controller. The alarm card provides an RJ-45 interface
which can be used to gather three types of alarms. This RJ-45 port can be connected to a customer
paging system for remote alerting of zone controller failures.
The Motorola SMB2408 alarm card fits into the right slot of the chassis. This is a slot specifically designed
for the alarm card (non-CompactPCI slot). The alarm card LEDs identify the operational condition of
the CPU card, power supplies, power references, and fault status of the zone controller.
The alarm cards firmware can be updated through a manual or automatic flash programming process.
Tape Drive
The Digital Audio Tape (DAT) drive, located in the top slot of the zone controller panel, is used for
backing up and restoring the infrastructure database, which is locally stored on the zone controller
hard drive. Use 12 GB, 4 mm DAT tapes with the tape drive.
4-10 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System CD-ROM Drive
CD-ROM Drive
The CD-ROM drive, located in the second slot of the zone controller panel, is used for installation and
upgrading zone controller application software and the installation of the Sun Solaris operating system.
The CD-ROM communicates to the CPU card through a SCSI interface connection.
Hard Drive
The hard drive is located in the third slot in the zone controller panel. The hard drive stores the
Solaris operating system and the zone controller application, which is the program that processes calls
and controls zone activities. The hard drive also stores a local copy of the infrastructure database,
which is used for managing resources and communications within the zone.
Power Supply
Dual redundant 400 W power supplies, located in the rear of the zone controller, provide
highly available power to the zone controller subcomponents. The alarm card reports the
status of the power supplied to the zone controller.
For additional information on component power supplies, see Appendix A, "Power Supply Reference.".
Transport Network

The following sections describe the transport network.
Master Site LAN and WAN
The master site LAN and WAN can include the following components:
Routers See "Routers An Overview" on page 4-12

LAN switch See "Ethernet LAN Switch" on page 4-18
WAN switch See "WAN Switch" on page 4-23
Digital Access Cross-connect Switch (DACS) See "Digital Access
Cross-connect Switch (Optional)" on page 4-37
The network is also equipped with an out-of-band management system for support of dial up services.
Out-of-band management provides access to the serial (console) interface of all supported devices at
the master site. The out-of-band management system requires two analog phone lines.
6881009Y05-O April 2004 4-11

Routers An Overview Chapter 4: Hardware Functional Description
Routers An Overview
Network transport and control functions for the ASTRO 25 trunking communication
system are provided by the following routers:
Gateway routers provide functional support for the MGEG, zone controller,
packet data gateway, and network management routing.
Core routers handle network traffic between the master site and other
sites within a zone (intrazone support).
Exit routers handle network traffic between a master site and sites in
other zones (interzone support).
GPRS Gateway Support Node (GGSN) router handles network traffic between the
Motorola radio network and external networks to support data services.
Simulcast Prime Site router handles network traffic between a simulcast
subsystem and master site.
Remote OSS router supports the implementation of a remote operations support system
which establishes a separate geographical location for mission critical components.
Digital Remote Access router extends network management client connectivity
to the Motorola radio network.
Border and Peripheral routers provide an interface to the Motorola Radio Network
Infrastructure (RNI) to extend the peripheral network (DMZ), respectively.
Site routers meet various types of remote site interface requirements. See
"Site Routers An Overview" on page 4-13.
The S6000 series routers replace the ST5000 series routers, as necessary.
The S6000 base router has three Ethernet (10Base-T / 100Base-TX) ports, a console (serial) port,
and two I/O slots for optional I/O modules. The base router (model ST6000) can be configured
with the I/O modules necessary to meet the operating requirements of each functional router. The
I/O modules are installed in slots labeled with port numbers 4 and 5. Table 4-1 contains a list of the
I/O modules used to meet the functional requirements of each router.
Table 4-1 I/O Modules for S6000 Series Routers
S6000 I/O Module ID S6000 I/O Module I/O Module Description

ST6000 No I/O modules required The S6000 base router provides three
Ethernet ports, LAN 1, LAN 2, and LAN 3.
ST6010 4-Port UltraWAN module (T1/E1) Supports integrated, channelized T1, E1,
CSU, DSU.
4-12 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Site Routers An Overview
Table 4-1 I/O Modules for S6000 Series Routers (Continued)

S6000 I/O Module ID S6000 I/O Module I/O Module Description
ST6011 4-Port FlexWAN module Provides a high-speed multifunction serial
interface to V.35, RS-232, RS-449, EIA-530,
or X.21 DCE or DTE serial devices.
ST6012 1-Port T3/E3 (HSSI) module A T3 or E3 WAN interface module that can
interface to an external CSU/DSU using the
HSSI connector or directly to a T3 or E3 line
using the BNC connector.
Table 4-2 lists the routers used in the ASTRO 25 trunking communication system.
Table 4-2 Routers by Function with I/O Modules
S6000 S6000
Functional Router ST5000
I/O Slot 1 I/O Slot 2
Description ST4000
Port 4 Port 5
Core Router ST6012 Empty ST5594
Exit Router ST6012 Empty ST5594
Gateway Router ST6011 Empty N/A
GGSN Router Empty Empty not applicable
Simulcast Prime Site ST6010 ST6010 S4000
Remote OSS Router ST6010 ST6010 ST5598
Remote Digital Access ST6011 ST6011 ST5580
Router for DDS
Remote Digital Access ST6011 ST6010 ST5598
Router for DSS and
T1/FT1
MGEG Router See gateway router See gateway router ST5500
Data Router See gateway router See gateway router ST5000
ST5598 legacy
Control Router See gateway router See gateway router ST5580
Network Management See gateway router See gateway router Previously provided by Ethernet
Router (function) LAN switch
Border Router as needed as needed not applicable
Peripheral Router as needed as needed not applicable
Site Routers An Overview

Routers used at remote sites to handle various types of network traffic include the following:
Remote site router Master site interface only: handles network traffic between the
master site and remote site without the need to support mutual aid or remote console sites.
6881009Y05-O April 2004 4-13

Gateway Routers Chapter 4: Hardware Functional Description
Remote site router Mutual aid support: handles network traffic between the master
site and remote site with channel bank support for sites with mutual aid.
Remote site router Colocated Dispatch or NM Site support with Plant 911
support at master site: handles network traffic between the master site and remote site
with support for colocated dispatch or network management equipment.
Remote Site Router Control room site: handles network traffic between
the master site and control room remote site.
The S2500 series routers replace the S4000 series routers, as necessary.
The S2500 base router has a single Ethernet port, a console (serial) port, and two I/O slots for
optional I/O modules. The base router (model ST2500) can be configured with the I/O modules
necessary to meet the operating requirements of each functional router. The I/O modules
are installed in slots labeled with port numbers 2 and 3. Table 4-3 contains a list of the I/O
modules used to meet the functional requirements of each router.
Table 4-3 I/O Modules for S2500 Series Routers
S2500 I/O Module ID S2500 I/O Module Description

ST2510 1-Port 10Base-T module
ST2511 1-Port FlexWAN module
ST2512 1-Port WAN/Telco (T1/E1) module
Table 4-4 provides a reference list of the site routers used in the ASTRO 25 trunking communication system.
Table 4-4 S2500 Series Routers Function Description With I/O Modules
S2500 I/O Module Slot 1 S2500 I/O Module Slot 2

Functional Router Description
Port 2 Port 3
Remote Site Router ST2512 Empty
Master Site Interface Only
Remote Site Router ST2511 Empty
Mutual aid support
Remote Site Router Empty ST2510
Colocated Dispatch/NM Site, Plant 911 at Master Site
Remote Site Router ST2512 ST2510
Control Room Site
Gateway Routers
Gateway routers are used for devices that require network redundancy and are multicasting beyond
their local LAN. Gateway routers provide several benefits for the zones master site:
4-14 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Gateway Router MGEG Support
Provide a single access point or gateway to access the core and exit routers.
Isolate multicast traffic from the various hosts they are servicing.
Provide redundant connections for hosts with redundant interfaces (zone controller) or
load balancing devices (MGEGs) because there are two for each function.
The gateway router is a Motorola Network Router (MNR) S6000 with an ST6011
module in I/O slot 1 as shown in Figure 4-8.
Figure 4-8 Gateway Router with ST6011 (FlexWAN) Module
The console operator subsystem and telephone interconnect subsystem are optional subsystems.
Components common to these optional subsystems (console operator subsystem and telephone
interconnect subsystem) include the AEB and the MGEG. When either one of these two
subsystems are employed by the system, these common components are required and the
gateway routers are populated with the ST6011 (FlexWAN) modules to accommodate the
gateway routers synchronous serial interface with the audio switch (AEB). When neither of
these subsystems are employed by the system, these common components are not required
and the gateway routers are not populated with the ST6011 (FlexWAN) modules.
The gateway router functions as an MGEG, data, and control router and also provides audio
switch interface and network management functionality.
Gateway Router MGEG Support

The gateway router is configured with one subnet for each supported MGEG. Because the MGEG is
deployed in pairs, two or four subnets are established for the gateway router to support the MGEGs
in the console operator or telephone interconnect subsystems. A gateway router uses two 10Base-T
interfaces for interconnection to the Ethernet LAN switch and the MGEGs.
Gateway Router Data Support

When used to support the Packet Data Gateway, the two gateway routers are used in this
system as an interface between the Packet Data Gateway and the Ethernet LAN switch. The
data router uses two 100Base-TX interfaces for interconnection. When remote OSS is a
requirement, the S6000 is configured with UltraWAN ports.
6881009Y05-O April 2004 4-15

Gateway Router Zone Controller Support Chapter 4: Hardware Functional Description
Gateway Router Zone Controller Support

Gateway routers serve as the interface for all control information that flows between the zone controller and
the resources necessary to process a call. These resources include the RF sites, the MGEGs, consoles, and
telephone interconnect. These routers use 100Base-TX for the zone controller interface to the LAN switch.
Gateway Router Audio Switch Interface Support

Each gateway router supports a synchronous serial interface to a ZAMBI card in the AEB audio switch.
A switch in gateway routers causes a corresponding switch in the synchronous links.
The zone controller uses the synchronous link in the gateway routers to program the audio
switch with the connections necessary to route audio between the MGEG and the consoles or
between the MGEG and the telephone interconnect device.
The FlexWAN ports on the gateway router provide the audio switch interface.
Gateway Router Network Management Support

The gateway routers provide support for network management.
Core and Exit Routers
Although they perform different services for the system, a core and exit router use the same platform.
The core/exit router is shown in Figure 4-9, on page 4-17.
Core Routers
Core routers route traffic between the master site and the remote sites. The core router interfaces to the WAN
switch using dedicated HSSI ports and to the Enterprise Ethernet switch on two 100Base-TX links.
The core routers perform tasks such as routing control, audio, data, and network management traffic
in and out of the master site. They provide control path redundancy and the segregation of network
management traffic. The primary router provides the necessary services to the sites while the secondary
serves as the standby router. The core router can also be configured to receive Network Time Protocol
(NTP) and to interface with the network management server using SNMP.
The core router uses Frame Relay to communicate to the sites through the WAN switch, which acts as
a Frame Relay server. There are two Frame Relay, Permanent Virtual Circuits (PVC) to each site, which
originate at the core routers, travel over the HSSI links, through the WAN switch, over the physical site
link, and ultimately terminate on the site router. Each PVC originates on a separate core router for
redundancy, and they are set up in an active/standby configuration. Most of the traffic follows the primary
PVC; if there is a failure in the primary PVC, traffic switches over to the secondary PVC.
The system requires a minimum of two core routers for 1:1 redundancy. Each core router has two separate
LAN connections to the Ethernet switch and an HSSI connection to the WAN switch. Each core router is
capable of supporting any combination of up to 250 channels and dispatch sites. Two core routers are added to
the network for every additional 250 devices up to a limit of 700 RF channels/dispatch sites in the zone.
Exit Routers
There are two exit routers in each zone of a multizone system. The Motorola exit routers
serve two primary functions in an ASTRO 25 system:
4-16 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System GPRS Gateway Support Node Router
Maintain the list of all active rendezvous points and the group prefixes served by each.
A single zone system must have two exit routers in order to execute this task.
Route interzone audio. The Frame Relay PVCs start at the exit routers in one zone, go
through the Frame Relay server side of the WAN switch, the ATM server side of the WAN
switch, the T1 transport (as ATM cells), to the WAN switch and exit routers at the other zone.
The exit routers use Frame Relay to talk to other zones and System OSS. The WAN switch provides both a
Frame Relay server and an ATM server to support the interzone traffic. The routers learn about the PVCs
on the HSSI port from the local WAN switch. Each PVC originates on an exit router in one zone, and
terminates on an associated exit router in the adjacent zone. The System OSS communicates with the
management network at the master site using the Frame Relay server side of the WAN switch.
Exit routers use the Border Gateway Protocol (BGP) for interzone routing.
The exit router uses dynamic routes to deploy packets among its multiple connections on both the
LAN and WAN interfaces. The packets destined for the control Ethernet interfaces on the zone
controller, as well as the packets for network management, are routed through the Transitional
LAN (TLAN) ports of the Ethernet LAN switch using dynamic routes.
Figure 4-9 Core and Exit Router With ST6012 (T3/HSSI) Module
GPRS Gateway Support Node Router
The GPRS Gateway Support Node (GGSN) router is a Motorola Radio Network Infrastructure (RNI)
router. One side of the GGSN router provides an interface to the Motorola RNI while the other side
of the GGSN router attaches to a peripheral network to interface with the border routers of your
Customer Enterprise Network (CEN). The GGSN router supports data communication service capabilities
of the ASTRO 25 integrated voice and data trunking communication network. One GGSN router
is provided with each ASTRO 25 IV&D trunking communication system.
6881009Y05-O April 2004 4-17

Border Routers and Peripheral Routers Chapter 4: Hardware Functional Description
Figure 4-10 provides a front view of the GGSN router.
Figure 4-10 GGSN Router (S6000 Base Router)
The front of the GGSN router has no input/output modules in I/O Slot 1 (port 4) or I/O Slot 2 (port
5) . Additionally, the GGSN has three Ethernet ports (RJ-45 connectors), a console port (DB-9
pin serial connector), an interrupt button, a reset button, and system LEDs. The rear panel of the
GGSN router provides two standard power receptacles for providing redundant power to the router
and a grounding screw to ground the router to an appropriate ground.
Border Routers and Peripheral Routers
Border routers are part of your CEN. One side of the border router provides an interface with
your CEN while the other side of the border router attaches to a peripheral network to interface
with devices included as part of the Motorola Radio Network Infrastructure (RNI). The border
router may interface with the GGSN, ATIA, or CADI.
Peripheral routers connect or link various peripheral networks together and expand border router
access capability to the peripheral network for your enterprise network.
The border and peripheral routers must be S6000 routers to provide data communication support
for the ASTRO 25 IV&D radio communication network.
The front and rear physical configuration of the border router and peripheral router is the same physical
configuration as the GGSN router. Figure 4-10 shows the S6000 router with no modules installed.
Border and peripheral routers may contain appropriate modules for the WAN 1 and WAN 2 slots to
accommodate your enterprise network and the peripheral network, respectively.
Ethernet LAN Switch
The Ethernet LAN switch is used to aggregate all the Ethernet interfaces for all servers, clients, and
routers. Devices are physically connected into the switch in a way that provides the highest reliability. For
example, devices with two network interfaces are connected to different Layer 2 modules. The Ethernet
LAN switch is a chassis based Ethernet switch that is deployed with redundant supervisor modules and a
minimum of 96 10/100Base-T ports. The backplane handles connections between the modules.
4-18 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Fault Tolerance and Redundancy
Two redundant Virtual LANs (VLANs) are set up within the LAN switch. The purpose of these as transitional
LANs (TLAN1 and TLAN2) is to carry intrazone traffic between the various core, gateway, and exit
routers. Two are needed to provide redundancy to address a single point of failure for Ethernet ports in
the routers. If an Ethernet port fails, traffic will be transferred to the remaining TLAN.
Figure 4-11 Ethernet LAN Switch
Fault Tolerance and Redundancy

All modules, fans, and power supplies, support hot swapping. Modules can be added, replaced,
or removed without interrupting the system power or causing other software or interfaces to
shut down. The supervisor engines and power supplies require redundant modules in order to
support the hot swap feature without interrupting service.
6881009Y05-O April 2004 4-19

Supervisor Engine Chapter 4: Hardware Functional Description
When you remove or insert a switching module while the switch is powered on and
operating, the switch does the following:
Determines if there is sufficient power for the module.
Scans the backplane for configuration changes.
Initializes all newly inserted switching modules, notes any removed modules,
and places them in the administratively shutdown state.
Places any previously configured interfaces on the switching module back to
the state they were in when they were removed.
Puts any newly inserted interfaces in the administratively shutdown state, as if
they were present (but unconfigured) at boot time.
If you insert a similar switching-module type into a slot, its ports are configured and
brought online up to the port count of the original switching module.
Runs diagnostic tests on any new interfaces. If the test passes, the switch is
operating normally. If the new switching module is faulty, the switch resumes
normal operation but leaves the new interface disabled.
Modules that can be found in the LAN switch installed in an ASTRO 25 system include:
Redundant supervisor engines
Switching modules
Fan assembly
Power supplies
Supervisor Engine
The LAN switch chassis has nine slots. Slot 1 is reserved for the supervisor engine, which provides
switching, local and remote management, and multiple gigabit uplink interfaces. Slot 2 can contain an
additional redundant supervisor engine, which can act as a backup if the first module fails. If a redundant
supervisor engine is not required, slot 2 is available for a switching module.
Reset Button
The Reset button allows you to restart the switch.
Console Port
The console port allows access to the switch either locally (with a console terminal) or
remotely (with a modem). The console port is an EIA/TIA-232 asynchronous, serial connection
with hardware flow control and an RJ-45 connector.
Switch Load
The switch load meter provides a visual approximation of the current traffic load across the backplane.
4-20 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System PCMCIA Slot
PCMCIA Slot
The Flash PC card (PCMCIA) slot holds a Flash PC card for additional flash memory. The flash
memory can be used to store and run software images or to serve as an I/O device.
Uplink Ports
The supervisor engine provides two Gigabit Ethernet ports that can be configured with any combination
of copper, shortwave (SX), long-wave/long-haul (LX/LH), and extended-reach (ZX) Gigabit Interface
Converters (GBICs). The two 1000BASE-X Gigabit Ethernet ports operate in full-duplex mode only.
In a redundant configuration with two supervisor engines, the uplink ports on the redundant (standby)
supervisor engine are active and can be used for normal traffic like any other ports in the chassis.
Switching Modules
The 48-port 10/100TX switching module provides 48 switched, 10/100-Mbps autosensing, full- or
half-duplex ports. Ports have RJ-45 connectors for Category 5 cable. The front-panel LEDs provide
status information for the module and the individual port connections.
Table 4-5 Ethernet Switching Module LEDs
LED Color Description

STATUS Green All diagnostics pass; the module is
operational.
Orange The module is booting or running diagnostics.
An over-temperature condition has occurred.
A minor threshold has been exceeded during
environmental monitoring.
Red The module is resetting. The switch has just
been powered on or the module has been
hot inserted during the normal initialization
sequence.
An over-temperature condition has occurred.
A major threshold has been exceeded during
environmental monitoring.
If the module fails to download code and
configuration information successfully
during the initial reset, the LED stays red and
the module does not come online.
Off The module is not receiving power.
LINK Green The port is active (the link is connected and
operational).
Orange The module or port is disabled through the
CLI command or the module is initializing.
Flashing orange The port is faulty and has been disabled.
Off The port is not active or the link is not
connected.
6881009Y05-O April 2004 4-21

Network Analysis Module Chapter 4: Hardware Functional Description
Network Analysis Module

The Network Analysis Module (NAM) monitors and analyzes network traffic using Remote Monitoring
(RMON), RMON2, and other MIBs. The RMON support that the NAM provides for Ethernet
VLANs is an extension of the RMON support provided by the Supervisor engine. The Switched
Port Analyzer (SPAN) selects network traffic and directs it to the NAM. Traffic Director can analyze
link characteristics, packet layers for capacity planning or departmental accounting, differentiated
service deployment and policies, and filter/capture packets for debugging.
The NAM can analyze Ethernet VLAN traffic up to 160 K packets per second (pps). The NAM is
managed and controlled from an SNMP management application, such as CiscoWorks2000.
Table 4-6 Network Analysis Module Status LED
Color Description
Green All diagnostic tests passed. The NAM is operational.
Orange The NAM is running through its boot and self-test diagnostics
sequence, or the NAM is disabled.
Red A diagnostic test, other than an individual port test, has failed.
Off The NAM is powered down.
The NAM supports hot swap replacement but it must complete its shutdown procedure and the Status LED
must be off before you can physically remove the module. The shutdown procedure in the NAM can be
activated through a Command Line Interface (CLI) or NAM shutdown commands, or by using the Shutdown
button. Removing the NAM without going through the shutdown process can corrupt or damage the module.
Fan Assembly
The system fan assembly provides cooling air for the supervisor engines and the switching modules.
The fan assembly is located in the chassis. Figure 4-11, on page 4-19 shows the fan assembly at the
top of the switch. Sensors on the supervisor engine monitor the internal air temperatures. If the
air temperature exceeds a preset threshold, the environmental monitor displays warning messages.
If an individual fan within the assembly fails, the FAN LED turns red.
Power Supplies
The chassis can house two fully redundant, hot-swappable, AC-input or DC-input, load-sharing power
supplies. Each power supply has a separate power input. If dual power supplies are installed, it is acceptable
to have one AC-input and one DC-input power supply. The power supplies are available in three ratings:
1000 Watt AC-input
1300 Watt AC- and DC-input
2500 Watt AC-input
All power supplies have the same form factor.
When two power supplies are installed and turned on, each power supply concurrently provides approximately
half of the required power to the system. If one power supply fails, the second power supply immediately
assumes full power to maintain uninterrupted system operation. Load sharing and fault tolerance are enabled
automatically when the second power supply is installed; no software configuration is required.
4-22 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Power Supply Fan Assembly
For proper load sharing operation in a redundant power supply configuration, at least
two modules must be installed in the chassis. Any combination of supervisor, switching,
or clock modules can be installed. If you fail to install at least two modules, you
might receive spurious OUTPUT FAIL indications on one or both power supplies.
The power supplies monitor their own internal temperature and voltages. In the event of excessive
internal temperature, the power supply will shut down to prevent damage. The power supply
restarts automatically when it returns to a safe operating temperature. In the event of an abnormal
voltage on one or more outputs of the power supplies, the OUTPUT FAIL LED will light.
Power Supply Fan Assembly
The power supplies have a built-in fan; air enters the front of the fan (power-input end)
and exits through the back. An air dam keeps the airflow separate from the rest of the
chassis, which is cooled by the system fan assembly.
Table 4-7 describes the power supplies LED indications.
Table 4-7 Power Supply Front Panel LEDs
LED Function Description

INPUT OK AC input Green when the input voltage is 85 VAC or
greater.
Off when the input voltage falls below 70
VAC, or if the power supply shuts down.
DC input Green when the input voltage is -40.5 VDC
or greater.
Off when the input voltage falls below -33
VDC, or if the power supply shuts down.
FAN OK Green when the power supply fan is operating
properly.
OUTPUT FAIL Red when there is a problem with one or
more of the DC-output voltages of the power
supply.
WAN Switch
The WAN switch is a Frame Relay/ATM switch that interfaces the master site to
RF sites, dispatch sites, and other zones.
6881009Y05-O April 2004 4-23

WAN Switch Chapter 4: Hardware Functional Description
Figure 4-12 WAN Switch
The WAN switch provides Frame Relay PVCs between routers in the core network, routers at
sites, and other zones. The use of Frame Relay allows for multiple logical links (PVCs) to be set
up over a single physical link to provide a level of path redundancy without the added cost of
multiple physical links. Frame Relay PVCs are set up on all links.
The WAN switch provides T1/E1 interfaces to connect the zone to RF and Dispatch sites. The
Interzone links use unchannelized T1/E1 links (channelized links are not supported). ATM provides
the ability to load share multiple T1/E1 links using Inverse Multiplexing bundling, which results in
a single logical link over multiple physical links. Intrazone links use unchannelized T1/E1 links for
sites without mutual aid and channelized T1/E1 links for sites with mutual aid.
Three types of modules can be housed in the WAN switch:
Control Processors (CP) for WAN switch management functions.
4-24 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Control Processors
Function Processors (FP)

Function processors provide interface ports that physically connect network communications
facilities and Passport switches. They switch data from external sources through
the bus and out of the switch through other FPs.
Power supplies
Control Processors
Two CP modules are installed in the system for redundancy. The primary CP module must always be inserted in
slot 0, while the backup CP module must always be inserted into slot 15. Each module includes two connectors:
V.24 DCE 9-pin D-type connector
10Base-T Ethernet port from an RJ45 connector
Figure 4-13 Control Processor Module
6881009Y05-O April 2004 4-25

Function Processors Chapter 4: Hardware Functional Description
Function Processors
The HSSI module is one type of Function Processor module used in a WAN switch installed in an
ASTRO 25 system. The HSSI module in the WAN switch is a single port module that takes up a
single slot in the switch. The port in the HSSI card is used to connect a core or exit router to the
switch. The WAN switch requires a HSSI module for each core and exit router.
Figure 4-14 Function Processor - HSSI Connections
Function processor modules providing a T1 or E1 WAN switch interface include the following modules:
4-26 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Function Processors
DS1C 4P FP module or E1C 4 port FP card. This is a 4-port channelized T1 or E1 module

that can be used to interface a remote site to the master site when the remote site has mutual aid
stations. The module has two connectors, each serving as the interface for two T1s or E1s.
A site link that carries both ASTRO 25 traffic and mutual aid audio terminates at a
Digital Cross-connect Switch (DCS) at the master site. The DCS separates the two
components, placing the ASTRO 25 traffic on a T1/E1 link that connect directly to a port
on a DS1C 4P FP module. The mutual aid audio from the site is placed on another T1/E1
directed toward the mutual aid system (channel bank/CEB/console).
Figure 4-15 Channelized, 4 Port, T1 or E1 Module
6881009Y05-O April 2004 4-27

Function Processors Chapter 4: Hardware Functional Description
DS1 8P FP module. This is an 8 port unchannelized T1 or E1 module that can be

used for those sites that do not have mutual aid channels. The site link is directly
connected to a port on this module through a channel service unit interface. One 8-port
unchannelized T1 or E1 module will support up to 8 sites.
Figure 4-16 Unchannelized, 8 Port, T1 or E1 Module
An 8-port E1 unchannelized equivalent card is not supported.
4-28 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System WAN Switch Interface Panels - Port Access
DS1 32P MSA FP or E1 32P MSA FP module for 32-port channelized or unchannelized
support. The unchannelized module can be used for sites that do not have mutual aid channels
while the channelized module can be used for sites that have mutual aid.
A site link that carries both ASTRO 25 traffic and mutual aid audio terminates at a
DCS at the master site. The DCS separates the two components, placing the ASTRO
25 traffic on a T1/E1 link. The mutual aid audio from the site is placed on another T1/E1
directed towards the mutual aid system (channel bank/CEB/console).
Each 32-port module occupies two slots in the WAN switch and supports up to 32 sites
through four connectors. Each connector provides an 8-port T1/E1 interface.
Figure 4-17 Channelized or Unchannelized, 32 Port T1 Module
WAN Switch Interface Panels - Port Access

WAN switch interface panels provide port access to the various ports associated with the connectors found
on WAN switch interface cards. There are two types of WAN switch interface panels as follows:
DS1/E1 WAN switch interface panel
MultiService Access (MSA) WAN switch interface panel
6881009Y05-O April 2004 4-29

DS1/E1 WAN Switch Interface Panel Chapter 4: Hardware Functional Description
DS1/E1 WAN Switch Interface Panel
The DS1/E1 WAN switch interface panel provides access to various ports associated with
the following WAN switch interface cards:
DS1C 4P FP (For equivalent channelized E1 support, the E1C 4-port FP card is used.)
DS1 8P FP (An 8-port E1 unchannelized equivalent card is not supported.)
DS1 8P ATM FP (An 8-port E1 unchannelized equivalent card is not supported.)
Figure 4-18 provides a view of an DS1/E1 WAN switch interface panel for port access.
Figure 4-18 DS1/E1 WAN Switch Interface Panel
Each of the 15-pin, subminiature, high density, D-type connectors on a DS1 8P FP card provides
two ports. With four of these connectors on the card, eight ports are available.
To access the two ports associated with the D-type connector labeled P0 on the DS1 8P FP card,
a cable is connected from the D-type connector labeled P0 on the DS1 8P FP card to the D-type
connector labeled Main Conn 0/2 on the DS1/E1 WAN switch interface panel.
With the connection in place, user port connectors on the DS1/E1 WAN switch interface panel
labeled User Port P0/4 and P1/5 provide access to each of the two ports associated with the
D-type connector labeled P0 on the DS1 8P FP card.
Table 4-8 identifies each connector on the DS1 8P FP card and the associated ports
on the DS1/E1 WAN switch interface panel.
4-30 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System MSA WAN Switch Interface Panel
Table 4-8 DS1/E1 WAN Switch Interface Panel - Port Access
WAN Switch Interface Panel WAN Switch Interface Panel Number of

DS1 8P FP Card Connector
Main Conn Connector User Port Connector Ports
Connector P0 Main Conn 0/2 Connector User Port Connector P0 (P0/4) 2
User Port Connector P1 (P1/5)
Connector P1 Main Conn 1/3 Connector User Port Connector P2 (P2/6) 2
User Port Connector P3 (P3/7)
Connector P2 Main Conn 0/2 Connector (Panel User Port Connector P4 2
2) (P0/4)(Panel 2)
User Port Connector P5
(P1/5)(Panel 2)
Connector P3 Main Conn 1/3 Connector (Panel User Port Connector P6 2
2) (P2/6)(Panel 2)
User Port Connector P7
(P3/7)(Panel 2)
In order to access all eight ports on the DS1 8P FP card, two DS1/E1 WAN switch interface panels
(Panel 1 and Panel 2) are required since each panel only supports access to four ports.
The Spare Conn 0/2 connector and Spare Conn 1/3 connector on each interface panel are reserved to interface
a spare DS1 8P FP card to the panel for implementation of the fast failover feature of the WAN switch.
MSA WAN Switch Interface Panel
The MSA WAN switch interface panel (Figure 4-19) provides access to the 32 ports associated
with the DS1 32P MSA FP WAN switch interface card (Figure 4-17).
Figure 4-19 provides a view of an MSA WAN switch interface panel for port access.
Figure 4-19 MSA WAN Switch Interface Panel
The DS1 32P MSA FP (or E1 32P MSA FP) has four high density connectors, each connector
has 44 pins which are used to provide connections for eight T1 links. With four of these
connectors on the card, 32 ports are available.
For equivalent E1 support, the E1 32P MSA FP card is used.
6881009Y05-O April 2004 4-31

Fast Failover Chapter 4: Hardware Functional Description
To access the eight ports associated with the D-type connector labeled P0 on the DS1 32P MSA FP
(or E1 32P MSA FP) card, a cable is connected from the D-type connector labeled P0 on the DS1 32P
MSA FP card to the D-type connector labeled P0 on an MSA WAN switch interface panel.
With this connection in place, RJ45 connectors on the MSA WAN switch interface panel labeled
P0, P1, P2 P3, P4, P5, P6, P7 provide access to each of the eight ports associated with the D-type
connector labeled P0 on the DS1 32P MSA FP (or E1 32P MSA FP) card.
By connecting each of the 4 D-type connectors on the DS1 32P MSA FP (or E1 32P MSA FP) card (labeled
P0, P1, P2 and P3) to one of the D-type connectors on the MSA WAN switch interface panels (labeled
MSA P0, MSA P1, MSA P2, and MSA P3, respectively), the RJ45 connectors on the MSA WAN switch
interface panel provide access to all 32 ports on the DS1 32P MSA FP (or E1 32P MSA FP) card.
Four additional connectors on the back of the MSA WAN switch interface panel are used to
interface a spare DS1 32P MSA FP (or E1 32P MSA FP) card to the panel for implementation
of the fast failover feature of the WAN switch.
For a more detailed view of port access implementation, see Figure 4-22, on page 4-35.
Fast Failover
The WAN switch supports a feature called fast failover in ASTRO 25 systems without redundant site
routers and the corresponding redundant site links. Fast failover is implemented through the installation
of main and redundant site interface cards. If the WAN switch detects a site interface card failure,
it quickly switches from the failed active card to the standby interface card. The switchover is fast
enough to prevent a site from entering site trunking if the active card fails.
The fast failover feature of the WAN switch can be implemented with the following WAN switch interface cards:
DS1C 4P FP (For equivalent channelized E1 support, the E1C 4-port FP card is used.)
DS1 8P FP (An 8-port E1 unchannelized equivalent card is not supported.)
DS1 32P MSA FP (For equivalent channelized E1 support, the E1 32P MSA FP card is used.)
The fast failover feature is not implemented on a per port basis. It is

implemented on a per card basis.
The fast failover feature of the WAN switch cannot be implemented with the following
WAN switch interface cards:
HSSI FP
DS1 8P ATM FP
WAN Switch DS1C 4P FP Card
The DS1C 4P FP (or E1C 4 port FP) card is used in ASTRO 25 systems that include mutual aid
channels. The digital cross-connect switch at the master site is used to drop and insert information
from a group of T1/E1s to another group of T1/E1s. The T1/E1s transporting the combined ASTRO 25
4-32 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System WAN Switch DS1 8P FP Card
traffic and mutual aid audio from the remote sites are terminated at the digital cross-connect switch.
The digital cross-connect switch drops the mutual aid audio from the inbound T1/E1 and inserts
the information into a T1 that will carry the audio to the dispatch system.
Figure 4-20 shows how the DS1C 4P FP (or E1C 4 port FP) card in the WAN switch connects to the interface
panel at the master site. The four user ports on the interface panel connect to the digital cross-connect switch
to provide the WAN switch with access to four channelized T1/E1s. The digital cross-connect switch drops
the ASTRO 25 traffic from the inbound remote site T1/E1s and inserts the information into the channelized
DS1C 4P FP (or E1C 4 port FP) modules through the WAN switch interface panel connections.
Figure 4-20 DS1C 4P FP Card and WAN Switch Interface Panel - Fast Failover
Each DS1C 4P FP (or E1C 4 port FP) card in the WAN switch provides 4 channelized T1/E1 links to the
WAN switch interface panel. Cables (Category 5 with RJ45 connectors) from the user ports on the WAN
switch interface panels connect directly to the digital cross-connect switch interface panel.
WAN Switch DS1 8P FP Card
The DS1 8P FP card can be used when mutual aid support is not a remote site link requirement. Figure 4-21
shows how the DS1 8P FP cards in the WAN switch connect to the interface panel at the master site.
The eight user ports on the interface panel provide eight unchannelized T1 site links, through the
transport network, to Telco/WAN ports on ST2500 routers at ASTRO 25 Repeater subsystems or to the
UltraWAN ports on ST6010 simulcast prime site routers at simulcast subsystems.
6881009Y05-O April 2004 4-33

WAN Switch DS1 32P MSA FP Card Chapter 4: Hardware Functional Description
Figure 4-21 DS1 8P FP Card and WAN Switch Interface Panel - Fast Failover
WAN Switch DS1 32P MSA FP Card
Figure 4-22 shows how the DS1 32P MSA FP (or E1 32P MSA FP) card in the WAN switch
connects to the interface panel at the master site. The 32 RJ45 (T1/E1 ports) on the interface
panel provide 32 channelized T1/E1 site links to the digital cross-connect switch (DCS) at the
master site or 32 unchannelized links to the transport network.
4-34 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System WAN Switch DS1 32P MSA FP Card
Figure 4-22 DS1 32P MSA FP and WAN Switch Interface Panel - Fast Failover
The ports labeled P0 and P1 on the main and spare DS1 32P MSA FP (or E1 32P MSA FP) cards connect
to the four ports on the back of the MSA interface panel. Ports P2 and P3 on the DS1 32P MSA FP cards
connect to the four ports on the front of the MSA interface panel. Cables (Category 5 with RJ45 connectors)
from the T1 output ports on the WAN switch interface panel connect directly to the front of the DCS interface
panels for channelized cards or the transport networks interface panels in the case of unchannelized cards.
6881009Y05-O April 2004 4-35

WAN Switch Configuration Chapter 4: Hardware Functional Description
WAN Switch Configuration
Figure 4-23 shows a very high-level view of an ASTRO 25 network configuration consisting of
three remote zones. The circles represent each of the three zones connected through the WAN
switches and the wide area network transmission facilities.
The voice, trunking control, and network management traffic that must be transported between
multizone master sites is processed by the Ethernet switches, routers, and WAN switches installed
in each zone. Only the WAN switches are shown in this simplified diagram.
The WAN switch in each multizone master site converts the interzone voice traffic, trunking control
traffic, and network management traffic to ATM cells and then sends the ATM traffic over the WAN
circuits between zones. In an ASTRO 25 system, the voice traffic, trunking control traffic, and
network management traffic all share the same WAN circuits that interconnect zones. Typical transport
networks used to carry the traffic between zones consist of T1/E1 digital circuits.
For information on component power supplies, see Appendix A, "Power Supply Reference.".
Interzone Interface
The interzone connections provide connectivity for control, voice, and network management traffic between
zones. These links are typically higher bandwidth than the site links and require higher levels of redundancy.
The links are provided by the exit routers through the WAN switch. Two exit routers are used in each zone.
The interzone links are similar to the site links in that to the router, they are Frame Relay PVCs provided by
the WAN switch. They differ in that they exit the WAN switch as ATM cells. The interzone links are Inverse
Multiplexing on ATM (IMA) bundles running over unchannelized T1/E1 links. The bundling operates as a
single logical link to the networking layer. The minimum bandwidth required between zones is 6 Mb or four
T1/E1s. Physical redundancy is accomplished by provisioning up to a maximum of eight T1/E1 lines.
It is possible for some system configurations that consist of three or more zones to include a spur zone.
This is a zone with connectivity to only one other zone in the system and becomes isolated if its interzone
links are down. A spur zone requires two T1/E1 lines to link to its connecting zone.
4-36 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Digital Access Cross-connect Switch (Optional)
Figure 4-23 WAN Switch Configuration Example
Digital Access Cross-connect Switch (Optional)
The Zhone Arca-DACS 100 is an integrated broadband network access device specifically deployed with
systems that include mutual aid channels. The Zhone Arca-DACS Digital Access Cross-connect Switch
(DACS) is a DS0 switch that grooms T1s or E1s from sites so that trunking control, ASTRO voice, and
network management can be transported to the WAN switch. Voice from the conventional mutual aid channels
is routed to a Central Electronics Bank through a channel bank connected to the cross-connect switch.
6881009Y05-O April 2004 4-37

Features Chapter 4: Hardware Functional Description
Figure 4-24 Zhone Arca-DACS 100 Digital Cross-connect Switch
The DACS system consists of a chassis, backplane, and a combination of I/O and logic plug-in
cards. The chassis can either be rack-mounted with associated equipment or operated as a standalone
unit. The cards can be either intelligent or non-intelligent. The intelligent cards are equipped
with microprocessors and can function independently of the system CPU. The unintelligent cards
do not have microprocessors and are, therefore, under CPU control. The system may be fully
redundant, with protected input lines under most circumstances.
Protection can be provided for all network I/O channels through use of protection cards. The system is
operated using software commands from a VT100 compatible terminal, through an RS232 interface to
the chassis, using the TL1 transaction language protocol. The system can also be operated remotely
by way of a Telnet session after initial setup of an Ethernet interface.
Features
The Zhone Arca-DACS 100 supports the following features in an ASTRO 25 system:
TL1 Command Line Interface (CLI) programming, with downloaded software
4-38 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System System Redundancy
Configuration Management Tool (CMT) graphical user interface

Up to six simultaneous TL1 command sessions
Controlled access to system functions using application keys
Channelized T1 or E1 mapping capability with 1:N redundancy
Up to 72 T1 or E1 lines with protection
TDM cross-connect capability with 1:1 redundancy
2400 by 2400 DS0 static cross-connect capacity
Performance monitoring on all ports, with capability of viewing alarms in TL1
sessions or from SNMP management stations.
If you have a network of Arca-DACS 100 nodes, you can monitor the alarms
from all of the nodes at the SNMP monitoring station.
Equipment and line loopback capability
Metallic service unit (MSU) card with DS0 and DS1 monitor and split
test capability (for T1 or E1 lines)
Separate A/B power feeds for input DC voltage
Front panel connector and alarm access points
MC68360-based CPU with optional 1:1 system redundancy
Ethernet support, including IP address assignment, TFTP client process, TCP
Telnet access for multiple (up to five) simultaneous TL1 command sessions, and
IP routing over facility data link (FDL) channels.
System Redundancy
The Arca-DACS 100 system is configured to be fully redundant with the following components.
1:1 spared DC input (-48 V, nominal) power

1:1 spared CPU card and clock I/O card
1:N spared ST1 mapper card (CT1-CSU) and SE1 mapper card using one
T1 I/O protection card per mapper card type
1:1 spared TDM cross-connect card (XCON) card.
Physical Description
The Arca-DACS 100 system consists of a 17-slot chassis and up to 15 plug-in I/O cards and 15 plug-in
logic cards (see Figure 4-24). The I/O cards are located in the upper bank of card slots while the logic
cards occupy the lower card slots. The front connector, alarm, and power feed (FCAPF) assembly
panel is mounted in the chassis, between the upper and lower card slots.
6881009Y05-O April 2004 4-39

I/O Cards Chapter 4: Hardware Functional Description
I/O Cards
The following I/O cards are supported in an ASTRO 25 system:
Clock I/O (CLK IO) card (maximum of two per system)

The Clock I/O (CLK IO) card provides the primary and secondary reference clocks for the
system, as well as an Ethernet, 10Base-T, Media Access Unit (MAU) interface for the Telnet
and TFTP connectivity. The Clock I/O card supports up to five clock input sources. You can
configure the first four sources, and the fifth source is always set to the local system clock.
The Clock I/O card can be fully redundant, with each card synchronizing to the other,
matching clock phases (known as phase copy) and driving the clocks to the backplane.
If a fault occurs on one card, the other card is already active.
Although one Clock I/O card is active and one is standby, both cards function all of
the time. The active card operates in master mode, while the standby card operates in
phase-copy mode. In this mode, all frequencies and phases of the active Clock I/O card are
copied as close to the same time as possible on the standby Clock I/O card.
When a system is installed, the Clock I/O card that is inserted first is assigned the
active status. If two Clock I/O cards are present when the system restarts, the card
in slot 1 initializes quicker and assumes the active status.
TE I/O (T1 or E1 input/output) card (maximum of nine per system)

The TE I/O card provides the physical connection for up to eight T1/E1 lines. The card
plugs into any one of the universal slots 3 to 15 in the I/O (upper) card slot bank of the
chassis. The TE I/O card operates under CPU control. It controls the T1/E1 signals but
does not process them, and provides surge protection to meet Bellcore GR-1089-CORE
Network Equipment Building Systems (NEBS) Physical Protection Requirements.
GR-1089-CORE is Bellcores view of electromagnetic compatibility

and electrical safety criteria necessary for equipment to perform reliably
and safely in a clients networks.
TE I/O protection (TE IOP) card (one per chassis)

The TE IOP card provides 1:N protection for all of any one type of mapper card (CT1-CSU)
installed in the system. The type of mapper card protected depends upon the type of redundant
mapper card installed in the logic card slot immediately below the I/O slot of the protection
card. The protection card can be installed in any I/O slot from 3 to 15.
When a mapper card of the protected type fails or is removed from service, its T1/E1 signals
are routed to the protection bus. The relays on the protection card route the protection bus
signals to the I/O bus of the protection card or redundant mapper card slot. From the I/O bus,
the T1/E1 signals are applied to the redundant mapper card below the protection card. The
protection card remains in the protection state until the failure that caused the protection
switching is lifted. If another failure occurs on a mapper card of the same type, protection is
not available until the original problem clears and releases the protection bus.
4-40 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Logic Cards
Metallic service unit (MSU) card (maximum of one per system)

The MSU card provides the physical access connections and the switching capability to test
active DS1 lines and DS0 channels. The MSU card uses the TE I/O protection bus to obtain its
DS1 lines and DS0 channels for testing. The MSU card shares the protection bus with the
equipment protection circuits and yields it whenever protection switching is required.
The MSU card can reside only in slot 16 or 17 of the upper (I/O) slots of the
chassis. Under CPU control, any of eight T1 (DS1) lines present on the protection
bus can be switched through the MSU card relay array to either of two test access
connectors on the MSU card front panel for testing.
Logic Cards
The DACS supports the following logic cards in an ASTRO 25 system:
CPU card (maximum of two per system)

The CPU card can be inserted only in logic (lower) card slots 1 and 2 of the system chassis.
The CPU card communicates with other intelligent cards using Digital Port RAM (DPRAM)
and accesses Non Volatile RAM (NVRAM) through system memory. System function
during power-on requires at least one working CPU card. When the system is running,
it can sustain normal operations even under a temporary CPU card outage. NVRAM
stores nonvolatile system information on both CPU cards for redundancy. It includes
input and output interface circuits used for activities such as serial communications,
Ethernet LAN network management, and alarm generation.
When configured for full protection, the CPU cards are hot synchronized to each other,
which means that the redundant CPU card has an exact, current copy of the data on the
active CPU card. Both CPU cards contain complete system configuration and card
provisioning data. The system configuration data includes TDM termination pointer (TP)
data used in cross connections. When you reset or replace any provisioned card in the
system, the active CPU card downloads the provisioning data to the card.
Channelized (Structured) T1 mapper CSU (ST1-CSU) card (maximum of 10

per system, nine working and one protection)
The structured T1 (ST1) mapper card receives eight structured T1 frames from its associated
T1 I/O card and dismantles each T1 frame into its individual structured 24 DS0 signals.
It then maps the DS0 signals to the cross-connect (XCON, STS1) card for standard
DS0-to-DS0 cross-connection. In the opposite direction, the structured T1 mapper card
receives cross-connected DS0 signals from the TDM cross-connect (XCON) card for
standard DS0-to-DS0 cross-connect applications. In all cases, the input structured DS0
signals are placed in their proper slots on their assigned TL1 lines for application to
their T1 interfaces through the associated T1 I/O card. The ST1 cards are designed for
insertion into any of the logic (lower) chassis card slots 3 through 15.
The ST1 mapper cards are available in channel service unit (CSU) or digital signal cross-connect
(DSX) versions. The CT1-CSU mapper card performs the functions of a CSU in that it
terminates a digital channel, performs line coding, line equalization, and line conditioning.
The ST1 mapper card can operate independently of the CPU. It is not affected by
removal of a CPU card from the system. The ST1 mapper card communicates
with the CPU through the backplane.
6881009Y05-O April 2004 4-41

Intelligent Cards Chapter 4: Hardware Functional Description
Structured E1 mapper SE1 card

The structured E1 (SE1) mapper card receives frames from its associated TE I/O card and
dismantles each E1 frame into its individual structured 32 DS0 signals. It then maps the DS0
signals to the cross-connect card for standard DS0-to-DS0 cross-connection. In the opposite
direction, the structured E1 mapper card receives cross-connected DS0 signals from the TDM
cross-connect (XCON) card for standard DS0-to-DS0 cross-connect applications. In all cases,
the input-structured DS0 signals are placed in their proper slots on their assigned TL1 lines
for application to their E1 interfaces through the associated TE I/O card. The SE1 cards are
designed for insertion into any of the logic (lower) chassis card slots 3 through 15.
The SE1 mapper card can operate independently of the CPU. It is not affected by
removal of a CPU card from the system. The SE1 mapper card communicates
with the CPU through the backplane.
TDM cross-connect (XCON) card (maximum of two per system, one

working and one redundant)
The TDM cross-connect (XCON) card permits large-capacity digital cross-connection and
test access for T1 and E1 applications. The cross-connect card is a non-blocking 2,400 by
2,400 DS0 cross-connect card that can be installed in any of logic (lower) chassis slots
3 through 15. The number of DS0 signals that are available for cross connections depends
on the system configuration. For T1 cross-connections, see "T1 Cross-Connections" on
page 4-43. For E1 cross-connections, see "E1 Cross-Connections" on page 4-43
The I/O and logic cards of the system may also be classified as intelligent or non-intelligent. Intelligent cards
contain an on-board microprocessor and can function independently of the CPU except when they are reset or
replaced. Unintelligent cards do not have on-board microprocessors and, therefore, are under CPU control at
all times. Listing of the cards by intelligence classification is as described in the following sections.
Intelligent Cards
The following cards form the series of intelligent cards supported by the system:
CPU or CPU-G2 card

Clock I/O (CLK IO) card
Structured T1 mapper CSU (ST1-CSU) card
Structured E1 mapper SE1 card
Unintelligent Cards
The following cards form the series of Unintelligent cards available for the system:
TDM cross-connect (XCON) card

TE I/O card
TE I/O protection (TE IOP) card
Metallic service unit (MSU) card
4-42 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System T1 Cross-Connections
Front connector, alarm, and power feed (FCAPF) assembly; as part of the SYSC
If the system does not have any mutual aid services, the DACS is not required.
T1 Cross-Connections
An ST1 card supports 192 DS0 signals, for a maximum of 1728 DS0 signals with nine ST1 cards.
Input T1 signals are routed through the TE I/O cards and terminated in the structured T1 (ST1) mapper
cards. The ST1 mapper cards convert each T1 signal to 24 DS0 signals and place them on the TDM
transmit bus. The cross-connect (XCON) card takes the DS0 signals from the TDM transmit bus, performs
the cross connections, and places the resultant DS0 signals on the TDM receive bus. The ST1 mapper
cards then retrieve the cross-connected DS0 signals from the TDM receive bus, convert them back
to T1 signals, and route them to their destinations through the TE I/O cards. Maximum cross-connect
card capacity is 2400 DS0 time slots while maximum system T1 line capacity is 72, providing a usable
cross-connect space for a T1 to T1 configuration of 1,728 DS0 signals. The 2,400 time slots are all written
sequentially into fixed positions in data memory (DM). The 2,400 time slots are arranged as 75 buses
(0-74) with 32 time slots on each bus (75x32 = 2,400). The TDM bus is divided into transmit and receive
sections, operating at 19.2 MHz. Since the TDM bus is 75 buses wide, one XCON card supports all
TDM connections for the system. Two of the 75 buses are reserved for conferencing.
E1 Cross-Connections
An SE1 card supports 256 DS0 signals, for a maximum of 2304 DS0 signals with nine SE1 cards.
E1 signals are routed through the TE I/O cards and terminated in the SE1 mapper cards. The E1
mapper cards convert each E1 signal to 32 DS0 signals and place them on the TDM transmit bus.
The cross-connect card (XCON) takes the DS0 signals from the TDM transmit bus, performs the
cross-connections, and places the resultant DS0 signals on the TDM receive bus. The E1 mapper cards
then retrieve the cross-connected DS0 signals from the TDM receive bus, convert them back to E1
signals, and route them to their destinations through the T1/E1 I/O cards. Maximum cross-connect
card capacity is up to 2400 DS0 time slots while maximum system E1 line capacity is 72, providing
a usable cross-connect space for an E1 to E1 configuration of 2304 DS0 signals.
6881009Y05-O April 2004 4-43

Motorola Packet Data Gateway Chapter 4: Hardware Functional Description
Motorola Packet Data Gateway

The Motorola Packet Data Gateway (PDG) is a modular hardware and software platform designed
to link a customers data network to the Motorola ASTRO 25 trunked IV&D network. The
PDG employs Internet Protocol Version 4 (IPv4) routing. A multizone system requires one PDG
per zone for seamless system-wide packet data service operation.
Figure 4-25 Packet Data Gateway
The PDG is a CompactPCI device with the following components:
Chassis a CompactPCI chassis housing two power supplies and cooling fans
A SCSI hard drive connected to the Packet Data Router (PDR) module
A SCSI CD-ROM drive connected to the PDR module
PDR processing module
RNG processing module
4-44 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Packet Data Router
Power supplies For information on component power supplies, see

Appendix A, "Power Supply Reference.".
Packet Data Router
The PDR is one of two processing modules in the PDG. The PDR manages all aspects of the IP protocol
and provides a logical interface between the GGSN router and the RNG module.
The hardware and software components of the PDR module are as follows:
Motorola Computer Group MCP750 card, 366 MHz PPC, 256 Mb RAM
Linux Operating System, SC/EM PDG environment
PDR Application
Console interface port for terminal server access (V.24 / RS232 Asynchronous serial)
Ethernet port for Ethernet LAN switch interface
The PDR forwards outbound data traffic to the RNG in the zone where the subscriber is located. The
RNG in the zone where the subscriber is located is known as the serving RNG.
For more details on the functional application of the PDG and PDR, see
Chapter 10, "Integrated Voice and Data."
Radio Network Gateway
The Radio Network Gateway (RNG) is one of two processing modules in the PDG. The RNG provides a
logical interface between the local RF resources and the PDR to support data calls to subscriber radios.
The hardware and software components of the RNG module are as follows:
Motorola Computer Group MCPN750a card

Lynx Operating System
Radio Network Gateway Application
Console interface port RJ45 Asynchronous serial port for terminal server access
Ethernet port for Ethernet LAN Switch interface
6881009Y05-O April 2004 4-45

Network Management Subsystem Chapter 4: Hardware Functional Description
For more details on the functional application of the PDG and RNG, see
Network Management Subsystem

Network management provides the tools for fault, configuration, accounting, performance,
and security management, commonly known as FCAPS.
Network management functions in ASTRO 25 are distributed across several applications and servers in
various Operational Support System (OSS) configurations. See "Operations Support Systems" on page 4-46.
The system and zone OSS can be divided into two categories:
Transport Network Management (TNM) hardware and applications

Private Radio Network Management (PRNM) hardware and applications
An additional network management tool for an ASTRO 25 system is MOSCAD (Motorola Supervisory
Control and Data Acquisition). MOSCAD provides a common method for controlling a variety of
system components (such as tower lights and power generators). MOSCAD is also used to collect and
forward data concerning the state of system equipment such as channel banks, microwave, and time
reference. MOSCAD is covered in its own set of manuals and will not be covered here.
Operations Support Systems
Operations Support Systems (OSS) is a term used to specify the devices used to manage the system. This
includes network management servers and clients. There are two levels of the OSS: Zone and System.
Zone OSS
The Zone OSS refers to the network management system for a given Zone. The servers
are always colocated with the master site equipment. Examples are Zone Database
Server (ZDS), Air Traffic Router (ATR), Zone Statistics Server (ZSS), and FullVision
INM. The FullVision INM server includes the router manager software.
4-46 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Transport Network Management
System OSS
The System Operations Support System (System OSS) manages the whole system
from a single location. To accomplish its task, the System OSS must have a routed
path to all zones. The System OSS consists of the User Configuration Server (UCS),
System Statistics Server (SSS), Nortel Preside MDM manager, CiscoWorks, and
InfoVista (optional performance monitoring tool).
Remote System OSS

If located remotely from any zone, the Remote System OSS connects to one or
more zones through the WAN. The Remote System OSS physically connects to
multiple zones (up to 5) and the various zones data routers. A minimum of two
zones should be connected to a remote OSS site.
Transport Network Management
Transport network management involves the management of the network transport devices at the master site,
RF sites, and dispatch sites. This includes management of the links between zones (interzone links) and the
links between the sites (intrazone links). Transport network management applications in a zone include:
HP OpenView Network Node Manager

Motorola Router Manager for management of Motorola Network Routers (MNR)
FullVision INM for management of the Motorola communication system
A zone workstation contains the HP OpenView, FullVision INM, and Router Manager applications. This
integrated set of software application tools provides fault management and configuration management
capability for a majority of the transport devices and includes the following services:
HP Open View (HPOV) provides the topology map, alarm browser,

and MIB browser interface.
Router Manager adds configuration, fault and performance management tools
specific to Motorola Network Routers.
The FullVision INM application adds network management tools and hierarchical
topology maps specific to Motorola devices.
Traps and MIBs add fault and performance network management tools.
Configuration management tools for the Ethernet and WAN switches are installed at the
System OSS level, but are accessible from the zone level.
Fault Management at the Zone Level

Fault management applications at the zone level ensure that the local network operators have
timely fault information even if the zone becomes isolated from the rest of the network. Users
are able to access fault management information for a zone or System OSS from any network
management client in the system to which they have access rights.
Fault management information is available both from local displays and through Web access so
that a user can navigate to any zone or system-level information.
Fault management encompasses fault detection, fault isolation, and correction of abnormal
operation. Central fault management tasks include:
6881009Y05-O April 2004 4-47

Configuration Management at the Zone Level Chapter 4: Hardware Functional Description
Monitoring status history for a system and its components

Displaying system fault information
Performing diagnostics on components as needed
Motorola FullVision Integrated Network Manager (INM) is the fault management application for ASTRO
25 systems. FullVision INM provides a centralized view of the operational status of the system by
displaying intuitive, graphical representations (subsystem topology maps) of the system. Problems
are identified rapidly when they occur. Functions and tools also provide the ability to notify support
personnel, and track, diagnose, and correct faults in an effective manner. FullVision INM also maintains
a data warehouse, storing up to 30 days of event history for report generation.
Other essential infrastructure and site equipment status can be viewed on FullVision INM using the optional
MOSCAD plug-in. The MOSCAD system is capable of monitoring a broad range of analog, digital, and simple
closure inputs. As such, environmental sensors that do not otherwise have connectivity to the networksuch
as uninterruptible power supplies (UPSs), channel banks, microwave gear, and antenna systemscan be
monitored for fault conditions and reported to the FullVision INM through the MOSCAD Gateway.
FullVision INM offers an optional SNMP trap message forwarding capability to pass fault information
to a higher level, Enterprise network manager through a separate Network Interface Card (NIC).
Additionally, faults and interpretive messages may optionally be forwarded to a service technicians
alphanumeric pager through a compatible dialup, commercial paging service.
One FullVision INM server is installed at each zone.
Configuration Management at the Zone Level

Zone-level configuration management tools are available to configure all the devices in the
zone. For network management users, there is a single integrated interface for accessing
configuration information for all devices in the zone.
The network management clients allow users to navigate and configure network devices.
The tools for configuration management include:
Router Manager a configuration management and software upgrade

tool for Motorola Network Routers.
WEBlink for individual configuration of the Motorola Network Routers. Weblink is
launchable from the HP OpenView topology map when Router Manager is installed.
Telnet for Command Line Interface (CLI) of the routers, WAN switch and
LAN switch. A Telnet session to a device can be launched by clicking an icon
on the topology map in HP Open View.
CiscoWorks 2000 a Graphical User Interface (GUI) tool to configure the
Ethernet LAN switch. Cisco applications are Web enabled and can be launched
from NM clients with web browsers.
Nortel Network Management application provides a GUI tool to configure the WAN
switch. The applications are Web enabled and are launched from the NM clients.
Performance Management
InfoVista can be installed at the Zone or System OSS level to collect performance information on the LAN
and WAN devices. Additionally, HP Open View SNMP Data Collect and MIB browser allow the user to
view performance statistics for any device as long as their MIBs are loaded in HP OpenView.
4-48 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Security Management at the Zone Level
InfoVista is a performance monitoring tool that can provide a graphical representation of network statistics.
The InfoVista client software can be loaded on any Windows XP Network Management (NM) client and
launched from the NM client using the InfoVista icon located on the desktop or on the start menu.
In an ASTRO 25 system InfoVista provides the following features:
Discovery of all routers, LAN switches, WAN switches, Digital Access
Cross-connect Switches (DACS), and PDG
Creation of single report instances for each discovered device. It can
also provide group report instances
Security Management at the Zone Level

All network management applications have defined access privileges for each user. At a minimum,
all the applications support password protection. A single login allows each authorized user access to
the network management applications without having to login to multiple applications.
The routers and switches have an independent login, which is required when a user accesses the
device using Telnet. Independent logins prevent those users with access to an HP Open View topology
map from accessing network devices to change configuration information.
PRNM includes features for setting user privileges and controlling their access to view and/or modify
information contained in the configuration databases. Optional Agency Partitioning software allows
a system administrator to assign access privileges to specific applications. These applications include
Configuration Manager, Radio Control Manager, Historical Reports, and Zone Watch. The system
administrator can grant or restrict a users access to multiple zones.
Network Management at the System OSS

The System OSS acts as a system-level integration point. Therefore, the System OSS consists of applications to
manage the devices at the System OSS, critical devices at each zone and critical interface links between them.
At each System OSS the following network management applications will be available
to manage the networking backbone.
HP Open View Network Node Manager: Integrated with HP Open View is the Motorola
Router Manager application for router management and the FullVision INM application for
management of Motorola devices. Each HP Open View application integrates LAN and WAN
MIBs and traps to support fault management and performance management of the system.
Cisco Network Management application for managing the Ethernet switch.
CiscoWorks for management of the Cisco LAN switch
Nortel Preside Multiservice Data Manager (MDM) for management of the WAN switch.
InfoVista with integrated MIBs from all networking devices to collect
detailed network performance information.
Notice that the applications are similar with a few exceptions. In a multiple zone system, the Cisco network
management application is necessary to manage the Ethernet switch at each zone. The application is
centralized at the System OSS since there are few Ethernet switches in the system and they can be
more efficiently managed from a centralized location. The centralized Cisco application is available for
downloading software concurrently to all switches and for configuring the switches consistently.
Also centralized at the system level is the Nortel Preside application for configuration
management of the WAN switches throughout the system.
6881009Y05-O April 2004 4-49

Fault Management at the System OSS Chapter 4: Hardware Functional Description
In addition, some configuration needs to be done at the device level to report information appropriately
to either the zone applications, the system OSS applications, or both. For example, the trap destination,
IP address, and community string needs to be configured for each device.
Fault Management at the System OSS

One of the FullVision INM servers in a multiple zone system is equipped with the capability to collect
and present information from all zones. A system manager can quickly assess the global system health
and can also obtain information on any system alarm presented by FullVision INM.
Configuration Management at the System OSS

Access to configuration management tools at the system level for devices that cross zone boundaries is
normally restricted to factory personnel because of the severe impact that improper changes can have
on the entire system. The appropriate Motorola personnel should be contacted if it is ever necessary to
re-configure the network equipment, particularly the equipment at any of the master sites.
Performance Management at the System OSS

Performance management tools are used to conduct network performance reviews and trending analysis.
Installed as a component of the System OSS, InfoVista can produce long-term historical performance
reports and provide trending information on LAN and WAN devices. InfoVista collects and stores
statistical data and is capable of producing daily, weekly, and monthly graphs.
InfoVista can collect statistical data and provide performance reports for the following devices:
LAN switches
WAN switches
Gateway routers
Site routers
Core routers
Exit routers
PDG
DACS
WAN links
InfoVista is configured with integrated MIBs from the managed devices.
Security Management at the Zone and System OSS

All network management applications have defined access privileges for each user. All the applications
support password protection at a minimum. A single login allows the user to access all the applications for
which they have access privileges without having to login to multiple applications. However, this does not
include applications, such as Command Line Interface (CLI), that are resident on the networking devices.
Users must log on to the networking devices to run resident network management applications.
4-50 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Private Radio Network Management
Private Radio Network Management
The Motorola Private Network Radio Management (PRNM) suite is comprised of the software
and infrastructure required to support fault, configuration, accounting, performance, and security
management. The PRNM subsystem includes the following servers:
System Level Servers:

User Configuration Server (UCS)
System Statistics Server (SSS) (for multizone systems only)
Zone Level Servers:
Zone Database Server (ZDS)
Air Traffic Router (ATR) server
Zone Statistics Server (ZSS)
FullVision INM server (single zone and multizone)
Network management servers are Solaris-based servers installed in a CompactPCI chassis.
System-Level Servers
The UCS and SSS are typically installed in the same chassis.Figure 4-26 shows the PRNM system-level servers.
6881009Y05-O April 2004 4-51

User Configuration Server Chapter 4: Hardware Functional Description
Figure 4-26 PRNM System-Level Servers
User Configuration Server
The UCS is the host to information entered through the User Configuration Manager (UCM)
application running on a Windows PC client.
The UCS provides database storage and back-end processes required for most system-wide functions.
Included are the mobile radio records, talkgroup records, and services to automatically distribute and
replicate these records to the Zone Database Servers at each zone in a multiple zone system.
The UCS is accessible to authorized users from any client PC workstation.
Only one UCS is required per single or multiple zone system.
Role of the User Configuration Manager
The UCM is a tool used to configure information for users during various stages of system life.
The UCM spans system-level and zone-level configuration information.
You can configure the following types of information:
4-52 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System System Statistics Server
System Configuration
Configuration of system-level parameters, such as Adjacent Control Channels (ACCs)
Subscribers
Configuration of zone-level parameters, such as talkgroups and radio user information
Security
Configuration of records that control system management functions
Zone Watch Configuration

Configuration of zone-level parameters for Zone Watch, such as filters, watch
window definitions, and watch profiles
System Statistics Server
The SSS is the data repository for the statistics necessary to drive Historical Reports. The SSS is
required only with multiple zone systems. Statistics such as the number of calls, push-to-talks, and
busies are accumulated over preset time intervals. Data can be accumulated over a one-hour interval and
retained up to 10 days, or can be accumulated monthly and retained for one year.
For information on the relationship between the PRNM servers and applications and the
FCAPS model, see Chapter 12, "Introduction to the FCAPS Model and PRNM."
Zone-Level Servers
Figure 4-27 shows the Private Radio Network Manager zone level servers.
6881009Y05-O April 2004 4-53

Zone Database Server Chapter 4: Hardware Functional Description
Figure 4-27 Private Radio Network Manager Zone Level Servers
Zone Database Server
The ZDS is a Solaris-based server residing on a CompactPCI chassis. The ZDS maintains the infrastructure
database for the zone, retains a replica of the current UCS database and home zone map, and exports
the subscriber information it received from the UCS to the zone controller. The ZDS also exports
the infrastructure information from its database to the zone controller where it is stored as the local
infrastructure database. This server passes commands and information from the Radio Control Manager
(RCM) application to the zone controller. The ZDS also performs all network management and fault
management polling of system devices to support the network management clients. The fault management
information that the ZDS collects is passed on to the FullVision INM server.
The ZDS handles a variety of tasks, including:
Hosts the zone configuration database

Administers the standard and optional applications licenses
Authenticates network manager users accessing the system
Performs back-end support services for user applications
Handles telephone interconnect record processing
4-54 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Air Traffic Router
Air Traffic Router
The ATR is a Solaris-based server residing on a CompactPCI chassis. The ATR receives air traffic
information from the zone controller, creates Air Traffic Information Access (ATIA) packets, and
broadcasts them as the ATIA data stream on the network. Various clients listen to this data stream
to perform their functions. These clients include the ZSS and SSS, the ZDS, the RCM application,
the Zone Watch application, Affiliation Display, and third-party clients.
The ATR hosts a variety of real-time data processing applications to support user
and system applications, including:
Affiliation Server, the back-end of the optional Affiliation Display

Processes real-time call transactions, being the information source for Zone Watch and RCM
Source of the optional ATIA data stream to third-party applications
Logs to disk ATIA data for viewing or exporting to a text file
Routes RCM command and status packets to/from the zone controller
Routes call logging packets from the zone controller to the ZSS and SSS
Hosts the statistics proxy agent for the zone controller as a source for
Dynamic and Historical Reports statistics
Zone Statistics Server
The ZSS is the data repository for the statistics necessary to drive Historical Reports. Statistics such as the
number of calls, push-to-talks, and busies are accumulated over preset time intervals. Data can be accumulated
over a one-hour interval and retained up to 10 days, or can be accumulated monthly and retained for one year.
FullVision INM Server
The FullVision INM server is a Solaris server on a CompactPCI chassis. FullVision INM is a
Windows-based GUI tool used for monitoring the health of the devices in your network. FullVision
INM lets you view alarm information in a variety of formats:
Map views
Filtered alarm logs
Graphical representations of alarm information
Report form
FullVision INM spans system-level and zone-level configuration information that allows monitoring
of the health of system and zone-level objects, such as servers, zone controllers, or sites. Each
zone in an ASTRO 25 system is equipped with a FullVision INM server. The server at one of
the zones is configured for both system- and zone-level monitoring.
The FullVision INM application is accessed through Windows-based PC clients running terminal
emulation software. The application launcher allows you to launch fault management sessions
transparently from any zones FullVision INM server. Therefore, you can access fault management
information for any zone or for the system from one user PC.
More information on FullVision INM can be accessed through the online help available within the program.
6881009Y05-O April 2004 4-55

TRAK 9100 Network Time Reference Chapter 4: Hardware Functional Description
TRAK 9100 Network Time Reference
TRAK 9100 is a Global Positioning Satellite (GPS)-based frequency and time reference unit. It is
primarily designed to provides 1 pps, 5 Mpps, and 1 pps + 5 Mpps composite signals.
TRAK 9100 Simulcast Site Reference (SSR) unit provides the following outputs to meet the network
time and network transport synchronization requirement of the ASTRO 25 system:
UTC time for the network time synchronization through the 10Base-T NTP
T1 or E1signals for the network transport synchronization (framed, RS422, and
TTL) through Telecommunication modules
IRIG-B signals for time stamps on the analog data logging recorders
The TRAK 9100 SSR is used at the master site, simulcast prime site, and simulcast remote sites.
If the prime site is colocated with the master site, only one TRAK 9100 with a TRAK 9200
DDU unit will be required to serve the master site and prime site.
Figure 4-28 presents the front view and Figure 4-29 presents the rear view of the TRAK 9100 model SSR
GPS Modular Frequency/Time System. The modules installed in the TRAK 9100 are the following:
GPS receiver with Rubidium oscillator

GPS receiver with double ovenized oscillator
AC/DC power supplies - For information on component power supplies, see
Appendix A, "Power Supply Reference.".
Digital Distribution Modules (DDMs)
Frequency Distribution Modules (FDMs)
Telecommunications modules (TEL)
Fault Sensing Unit (FSU) module
4-56 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System NTP Configuration in FSU 9104
Figure 4-28 TRAK 9100 Network Time Reference - Front View
Figure 4-29 TRAK 9100 Network Time Reference - Rear View
The TRAK 9100 SSR is configured for redundant operation in order to meet the availability requirement. The
redundant configuration consists of one GPS Rubidium oscillator module as the main frequency reference,
another GPS double over-sized oscillator module as standby reference unit, and two power supplies.
NTP Configuration in FSU 9104

The Network Time Server (NTS) module is used to time synchronize clients on an Ethernet
network to within several milliseconds of UTC. Control and Status of the Model 9104 is also
available over the network and is obtained using a Telnet session.
The default IP address and netmask of the TRAK 9100 must be changed in order for it to operate in the radio
system network. Refer to TRAK 9100 users manual for programming the IP address and netmask.
6881009Y05-O April 2004 4-57

Out-of-Band Management Chapter 4: Hardware Functional Description
Out-of-Band Management
Out-of-band management consists of a set of modems and one 40-port or two 20-port terminal
servers. The servers provide interfaces to the Ethernet LAN switch on one side and to the modems
on another. The LAN interface provides connections to the serial (console) interfaces of all the
devices at the master site. This connection provides the means to program an IP address in any
device which in turn allows access to all the other programmable functions. The modems provide
a method to dial into the terminal server connected to the master site LAN. Telnet is supported, as
well as connectivity to the serial ports of the routers, switches, and servers.
Figure 4-30 and Figure 4-31 display the In-Reach terminal server.
Figure 4-30 In-Reach Server - Front View
Figure 4-31 In-Reach Server (40 port) - Rear View
Remote Analog Access

A feature supported by ASTRO 25 is remote analog access. This allows properly configured PCs
to dial into the network and access the Network Management applications through the terminal
server and the LAN switch. Up to 24 ports of analog access is supported.
Once the dial up client is granted access to the system through a login and password, the client can launch the
zone manager applications or launch the Web browser to access the FullVision INM server. Performance of
applications such as Zone Watch will depend on the amount of bandwidth allocated to the connection.
4-58 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Console Operator Subsystem
Console Operator Subsystem

The CENTRACOM Gold Series control operations center acts as the central focus of
most radio communication systems. It seamlessly integrates radio, telephone, paging and
other communication resources for convenient use.
The Embassy system is designed for customers requiring wide area coverage or audio capacity that is
beyond the limitations of a non-Embassy system. In an Embassy system, multiple Central Electronics
Banks (CEB) are connected through an Ambassador Electronics Bank (AEB).
Each console operator position consists of an IBM compatible personal computer (PC) and a CENTRACOM
Gold Series Console Interface Electronics (CIE) unit. The PC, while it is running the console operator
client software, controls the operation of the CIE. The CIE is the physical equipment interface between
the Central Electronics Bank (CEB) and operator personnel. The CEB contains the equipment that
routes audio between the base stations and the operators. All of the operator PCs in the center are
connected to a local area network (LAN) so they can share information.
Each zone in an ASTRO 25 multiple zone system may have console operator equipment in various
configurations. Appropriately equipped consoles extend functionality to all talkgroups regardless of
talkgroup zone affiliation. That is, they are capable of transmitting and/or receiving audio (including
Logging Recorders) to/from programmed talkgroups that may operate across multiple zones.
For information on component power supplies for this subsystem, see Appendix A,
"Power Supply Reference.".
Motorola Gold Elite Gateway
The Motorola Gold Elite Gateway (MGEG) is an interface device that allows an existing
circuit-switched CENTRACOM Elite system to communicate over an IP or packet-based
system. The MGEG provides two additional services:
6881009Y05-O April 2004 4-59

Motorola Gold Elite Gateway Chapter 4: Hardware Functional Description
Encryption/decryption capability to and from the console operator position or client.

Audio connectivity for telephone interconnect in ASTRO 25 systems that
include the telephone interconnect option.
Figure 4-32 Motorola Gold Elite Gateway - Front View
In an ASTRO 25 system, the audio is transported over an IP-based network. However, the CENTRACOM Gold
Series equipment uses a circuit switched architecture through the AEB. The MGEG is the interface between the
IP packet switched transport of an ASTRO 25 system and the circuit switched transport of the CENTRACOM
Gold Series system. The MGEG also provides the same service for the telephone interconnect subsystem.
Radio frequency sites place audio onto the packet switched IP network. The zone controller commands
the MGEG to pick up audio from the IP network, translate it in clear pulse code modulation (PCM)
digital audio, and place it on one of its E1 links to the AEB bus. The zone controller will have
already programmed the audio routes in the AEB accordingly.
The zone controller sends and receives control requests from the console operator positions through the
zone controller-control router ZAMBI link and the CEBs AIMI to AEBs AMB link.
For CEBs located at the master site, console sites place unencrypted PCM digital audio on the E1 link
to the AEB. Remote sites use a T1 link between the CEBs and the AEB. The zone controller sends the
necessary information for the MGEG to pick up the audio from one of its AEB to MGEG E1 links,
convert it to ASTRO audio, encrypt if required, and place the audio onto the IP network.
4-60 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Channel Marker and Alert Tone
Channel Marker and Alert Tone

A channel marker tone is a distinct, periodic, audible tone sent to consoles or subscriber radios. The
primary purpose of a channel marker is to inform radio users (console operators or subscribers) that a
conventional channel or trunked talkgroup is involved in a high priority situation. The tone indicates
to radio users that these system resources should only be used if they are involved in the high priority
situation. The tone also informs radio users that a console operator is monitoring the talkgroup.
One role of the console operator subsystem is to process channel marker and alter tone information
for distribution to the sites. To do this, the MGEG takes digitized PCM audio tones and converts
them into IP packets for distribution to the sites. For more on channel marker and alert tones,
see "Channel Marker for Talkgroup Calls" on page 9-43.
System Interaction
Upon initialization, the MGEG reports its call capacity status to the zone controller. The MGEG also
sends a message, indicating its operational status, to the zone manager application.
The zone controller requires a properly operating control path, audio path, and link to the AEB in order
to supply audio services, through the MGEG, for consoles and telephone interconnect.
The MGEG interfaces with the Zone Database Server (ZDS) for two reasons:
To report component operational status using Simple Network Management

Protocol (SNMP). The ZDS then does trap forwarding to the FullVision
Integrated Network Manager (INM) server.
To download specific configuration data from the Zone Configuration Manager (ZCM).
Components
Software and hardware components are used to maintain the MGEG in operational status.
Software
The MGEG software consists of Microsoft Windows operating system and custom application
software. The custom application software provides the following services:
Audio vocoding
Protocol translation
System fault management
Configuration services
Optional secure voice services
Anti-virus software
Hardware
The CompactPCI chassis contains three main areas for installing components.
The drive bay area contains the hard disk drive, CD-ROM drive and the 3.5 in. floppy
drive. It is located on the right side of the MGEG when viewed from the front.
6881009Y05-O April 2004 4-61

Component List Chapter 4: Hardware Functional Description
The front card slot area contains seven slots for user-defined cards and four slots for system
cards. It is located on the left side of the MGEG when viewed from the front.
The rear transition module area contains 11 slots for transition modules. It is located
on the right side of the MGEG when viewed from the back.
Two power supplies and a fan tray are also included in the chassis
Component List
The following is a list of components of the MGEG:

(1) CompactPCI chassis
(1) Hard drive
(1) 3.5 in. floppy drive
(1) CD-ROM drive
(2) Power supply
(2) Voice cards (VC) with (1) transition module
(2) Secure cards (for encryption)
(1) System Monitor Board (SMB)
(1) Single Board Computer (also referred to as CPU board)
(1) E1 Line card with (1) transition module
Card Placement
The MGEG chassis includes 11 front slots for function card placement. The slots are numbered 1 to 11, from
left to right as you face the front of the chassis. Table 4-9 shows the locations for the cards.
Table 4-9 MGEG Card Placement - Front
Card Slot
Quad E1 Line Card Slot 1
Secure Card Slot 3
Secure Card Slot 5
Voice Card Slot 6
Voice Card Slot 7
Single Board Computer Card (CPU) Slot 8
System Monitoring and Alarm Card Slot 11
4-62 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Voice Cards
Transition modules are located in the rear slots (rear slots are numbered 1 to 11) from right to left, as
viewed from the rear of the chassis. Table 4-10 shows the locations for the modules.
Table 4-10 MGEG Card Placement - Rear
Card Slot
Quad E1 Transition Module Slot 1
Ethernet Transition Module (for secure) Slot 3
Ethernet Transition Module (for non-secure) Slot 6
Single Board Computer (CPU) Transition Module Slot 8
Voice Cards
The MGEG voice cards (Figure 4-33) perform the following functions:
Translate the protocols between the circuit-switched and packet-switched

portions of the radio system.
Audio encoding and decoding services between IP packets and ASTRO audio.
Audio routing between the MGEG and the LAN switch in a clear system.
Audio routing between the line card and the encryption card in a system that must
provide encryption services for the console system. Each voice card contains 16 digital
signal processors (DSPs), a controller, an Ethernet port, and switching circuitry for
moving data between the Ethernet port, the DSPs, the controller and the buses in
the MGEG. The voice card does not alter audio levels of the audio packets that it is
decoding; AMBs in the Embassy switch (AEB) perform this task. For MGEG systems
with telephone interconnect, this card generates the go-ahead tone.
Process channel marker and alert tones from the console.
One of the two voice cards supplied, and the transition module mounted behind it, is configured to act as the
Network Interface Card (NIC) for MGEGs in systems that do not support encryption. In an ASTRO 25 clear
mode system, this card must occupy slot 6 in the chassis and does not at this time support hot swapping.
In systems that support encryption, one of the two encryption cards supplied, and the transition module
mounted behind it, is configured to act as the MGEGs network interface to the LAN switch.
Communication between the voice card and the encryption card is accomplished
through the backplane data busses.
6881009Y05-O April 2004 4-63

Secure Cards Chapter 4: Hardware Functional Description
Figure 4-33 Voice Card
Secure Cards
The secure cards (Figure 4-34) provide audio encryption services for the MGEG. One of the
cards also serves as an interface to the Ethernet LAN switch for MGEGs that support secure
capability. Each secure card occupies two slots in the chassis.
The secure card contains 13 encryption engines (one master and 12 slaves handling audio), a
controller, an Ethernet port and switching circuitry for moving data between the Ethernet port,
the encryption engines, the controller, and the buses in the MGEG.
There is a hard key erase button on the front panel of each secure card that is used to
quickly erase all keys on that specific card.
4-64 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System E1 Line Card
Figure 4-34 Secure Cards
The secure card can be populated with traffic encryption keys using a Key Variable Loader (KVL) device.
The KVL communicates with the secure card using the KVL interface port located above the reset key erase
button on the secure card as shown in Figure 4-34. Encryption keys are manually entered in the KVL or
delivered from the KMF using a store and forward method. For more details, see ASTRO 25 Trunked
Integrated Voice and Data System Release 6.4/6.4 SE Managing Secure Communications (6881009Y65).
E1 Line Card
The E1 board (Figure 4-35) is a communication card that enables PCM digital audio routing to and
from the MGEG to the AEB. The E1 configuration is possible because the AEB and the MGEGs are
colocated. The AEB Interface and its protocol of E1 mu-law consists of four E1 links from the E1
line card to the Ambassador Boards at the AEB. One E1 line card is supplied with each MGEG and
is required to be inserted into the furthest left slot, or Position 1, of the CompactPCI.
6881009Y05-O April 2004 4-65

System Monitor Board Chapter 4: Hardware Functional Description
Figure 4-35 E1 Line Card and E1 Transition Board
System Monitor Board
The System Monitor Board (SMB) (Figure 4-36) is a Phillips 80C552 microprocessor-based circuit board
that communicates over serial connections and continuously monitors the following:
Internal chassis temperature sensors

On-board temperature sensor
Chassis fan speed
DC power supply outputs
Power supply power fail signals
The SMB keeps you informed of system status through external LEDs on the front panel of the SMB.
4-66 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Single Board Computer
Figure 4-36 System Monitor Board (Alarm Card)
Single Board Computer
Also referred to as a CPU board, one single board computer (SBC) (Figure 4-37) is
supplied with each MGEG and installed in slot 8.
The CPU board includes a Pentium III, 500 MHz microprocessor, 256 MB RAM, and 512 K cache.
6881009Y05-O April 2004 4-67

Transition Modules Chapter 4: Hardware Functional Description
Figure 4-37 Single Board Computer / CPU
Transition Modules
Transition modules are necessary to provide through-connections in a CompactPCI environment

for the E1 line card, the voice card, and the encryption cards. The transition cards are inserted
opposite their corresponding control cards in the back of the MGEG.
If the MGEG has encryption cards installed, a transition module is installed in slot 3 to provide
the connectivity to the Ethernet switch. If the MGEG does not include the encryption cards, the
transition module is installed in slot 6 as shown in Figure 4-38.
Figure 4-38 shows the rear view of the MGEG chassis.
4-68 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Ambassador Electronics Bank
Figure 4-38 Motorola Gold Elite Gateway - Rear View
Ambassador Electronics Bank
The heart of a CENTRACOM Gold Series Embassy system is the Ambassador Electronics
Bank (AEB) (Figure 4-39). A CENTRACOM Gold Series Embassy system is comprised of
one or more Motorola CENTRACOM Gold Series Central Electronics Banks (CEBs), with
their associated operator positions, connected to an AEB.
In a CENTRACOM Gold Series Embassy system, the CEB and operator positions
function in the following manner:
An operator position includes control for each radio channel along with the speakers
6881009Y05-O April 2004 4-69

Ambassador Electronics Bank Chapter 4: Hardware Functional Description
and microphone used by the operator to access those channels.

The CEB includes the interfaces to the radio base stations, each operator position and the
switching electronics to route audio between base stations and operator positions.
Embassy system networks can be viewed as a star. The center of the star is the AEB (which processes
all CENTRACOM audio), and the arms of the star are channel banks, CEBs, and zone controllers.
Two unique boards support the link between the AEB and CEB: the Ambassador board (AMB) and
the Ambassador Interface Mux Interface board (AIMI). Both boards send and receive audio and
data across the link to the other board. The AMB interfaces the AEB side of the link and the AIMI
interfaces the CEB side of the link. In an ASTRO 25 system, the AEB also provides the audio link
between the telephone interconnect audio and the repeaters at the sites.
The AEB sends the digitized PCM audio tone to the MGEG voice card for conversion to IP vocoded
packets. Consoles on the same AEB that are members of the selected talkgroup receive digitized
values these tones without going through the MGEG. For more detailed information on channel markers
and alert tones, see "Channel Marker for Talkgroup Calls" on page 9-43.
4-70 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System AEB Architecture
Figure 4-39 Ambassador Electronics Bank
AEB Architecture
The AEB is made up of three types of boards:
AMB
System Timer
Zone Controller Ambassador Interface (ZAMBI)
These boards reside in the AEB card cage and are interconnected with buses provided on the
backplane. Audio interconnection is provided on 32 of these buses. Each audio bus is dedicated to
one Ambassador link in the system and carries all the audio received from that link.
Maximum throughput on the audio buses is obtained using Time Division Multiplexing (TDM). Each bus
is divided into time frames and each frame is divided into 32 slots. Within each slot is a digital sample
from one audio source in the system. All 32 of the audio buses are available to every AMB in the AEB,
each board can select and route any audio source to the desired audio slot on one of its links.
Figure 4-40 AEB Communication Structure
6881009Y05-O April 2004 4-71

Ambassador Board Chapter 4: Hardware Functional Description
Ambassador Board
The Ambassador board processes audio coming from and going to its links (Figure 4-41). Each
board supports two independent, full duplex links conforming to the T1 or E1 transmission standard;
for colocated CEBs, a unidirectional (AEB to CEB) RS-422 Manchester-encoded link, carrying
audio from the AEB to the colocated CEB, is also supported. The Ambassador board supports data
communication to other Ambassador boards throughout the system and to ZAMBIs.
4-72 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Ambassador Board
Digital audio received from the link arrives at the Ambassador board as a serial bit stream. The link interface
circuitry recovers the clock and framing information from the link and aligns the recovered TDM audio to
the AEB system side TDM bit rate clock and frame clock. Finally, this digital audio bit stream is driven
onto the AEB TDM bus dedicated to that Ambassador link. On links from CEBs, signaling information is
extracted from the second TDM slot and supplied to Ambassador data link controller circuitry.
The Ambassador board engages in two types of data communication in the Embassy system: AEB-CEB and
intra-AEB. Both types of data communication follow the High-Level Data Link Control (HDLC) protocol.
This protocol provides error-free data transfers with minimal microprocessor control. The AEB-CEB data
link (between the Ambassador and AIMI boards) is a point-to-point link that operates in LAPB (Link Access
Procedure Balanced) mode. This mode of operation allows full duplex and balanced (no link master) data
transfers. The intra-AEB data link (AMB to AMB/ZAMBI) is a multi-point configuration that operates in
transparent mode. This results in half-duplex, unbalanced data communication and requires that one AMB
be the primary station (or bus master) and that all others be secondary stations (or slaves). Arbitration
of which AMB is the primary station is accomplished by the AEB System Timer board.
6881009Y05-O April 2004 4-73

AEB System Timer Chapter 4: Hardware Functional Description
Figure 4-41 Ambassador Board
AEB System Timer
Each Embassy system utilizes two AEB System Timer boards (Figure 4-42) to provide
system clocking and data bus arbitration.
The system clocks provided include: the system TDM bit rate and E1 link transmit clock (2.048 MHz),
the system frame sync clock (8 kHz) and the T1 link transmit clock (1.544 MHz). All system clocks are
derived from one master clock that is synchronized from one of three possible sources:
Internal 2.048 MHz crystal oscillator
4-74 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System ZAMBI Card
Recovered 1.544/2.048 MHz from an Ambassador link

External 1.544/2.048 MHz reference source
Data bus arbitration uses three control buses to arbitrate which AMB is the data bus master. The
busy buses, data ready bus and data bus, along with the bit clock and frame sync clock from each
System Timer board, form a data bus group on the backplane. Only one System Timer board and its
associated data bus group are required at any time. The second module and data bus group are in hot
standby, for redundancy, unless an external sync source or reference is used.
Figure 4-42 System Timer Board
ZAMBI Card
The ZAMBI card acts as an interface between the AEB and the zone controller in an ASTRO 25
system. The hardware for the ZAMBI is identical to that of the AMB; the boards differ only in their
firmware. The primary responsibility of the ZAMBI is to accept routing instructions from the zone
controller and communicate these instructions to all AMBs in the AEB.
6881009Y05-O April 2004 4-75

AEB-CEB Interface Chapter 4: Hardware Functional Description
For a picture of the ZAMBI card installed in the AEB, see Figure 4-39, on page 4-71.
AEB-CEB Interface
The AEB-CEB interface (composed of the AIMI board, the AMB, and the link between them) has fault
tolerance protection against a single fault with the use of redundant interface boards and links.
AEB-Zone Controller Interface
The AEB-zone controller interface is accomplished through sync card interfaces in the control routers. Each
one of the control routers has a synchronous card interface that connects to one of the ZAMBI boards in the
AEB. This configuration provides protection in the event of a control router failure or a ZAMBI card failure.
Central Electronics Bank Architecture
Although the CEB in an Embassy system consists of much of the same hardware as the CENTRACOM
Gold Series CEB, the functionality of the hardware is somewhat different. In a CENTRACOM Gold
Series CEB, all audio routing and summing is done within the CEB. In an Embassy system, the primary
purpose of the CEB is to convert all received analog audio to a digital format and pass it to the AEB for
summing and routing to all the CEBs and channel banks in the system. Also, the CEB must receive
digital audio from the AEB, convert it to analog format and route it to the analog outputs. The analog
inputs to the CEB consist of audio received from conventional base stations and/or telephone lines, and
audio from operator microphones. The analog outputs from the CEB consist of audio for speakers at the
operators position, audio to conventional base stations and/or audio to telephone lines.
The CEB is also used to process channel marker and alert tones. Upon receipt of the channel grant
from the zone controller, a tone is generated by the Console Operator Interface Module (COIM) in
the Central Electronics Bank (CEB). The COIM in the CEB generates a tone in the form of digitized
PCM data and sends it in a TDM timeslot to the AEB. For more detailed information on channel
markers and alert tones, see "Channel Marker for Talkgroup Calls" on page 9-43.
A basic CEB in an Embassy system includes:
Base Interface Modules (BIMs) to interface with conventional base stations

external to the trunked system
Console Operator Interface Modules (COIMs) to interface with operator positions
AIMIs to interface with the AEB
Logging Recorder/Operator Interface Modules (LOMIs) to interface tape recording devices
4-76 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Central Electronics Bank Architecture
Figure 4-43 Central Electronics Bank
6881009Y05-O April 2004 4-77

Ambassador Interface Multiplex Interface Board Chapter 4: Hardware Functional Description
Figure 4-44 Central Electronics Bank Interfaces
Ambassador Interface Multiplex Interface Board

The AIMI board resides in the CEB and has two major functions:
Provide the interface between the AEB and CEB
4-78 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Console Operator Interface Module
Provide CEB timing and data bus arbitration

The AIMI supports one full duplex T1 or E1 link (for colocated equipment) to the AEB. In addition,
for a CEB colocated with the AEB, a unidirectional Manchester link carrying audio from the AEB
to the colocated CEB accompanies each E1 link. For remote CEBs, a similar option exists which
allows a second T1 link to be connected between the AEB and CEB if more audio resources from the
AEB to the CEB are required. Time Division Multiplex (TDM) bus timing and data bus arbitration
is performed by the System Timer section of the AIMI. This section of the AIMI replaces the CEB
System Timer module which is normally used in non-Embassy CEBs. In addition to these primary
functions, the AIMI supports control communication with all other CEB modules.
For fault tolerance purposes, each CEB contains two AIMIs. At any given time, only one AIMI has its link(s)
in the active state (that is, CEB audio is being sent/received on that link) while the other AIMI has its
link(s) in the inactive (hot standby) state. Every 24 hours the inactive AIMI is activated to prevent the
occurrence of an undetected failure in the inactive AIMI. In a similar manner, only one AIMI has its System
Timer section active while the other AIMI has its System Timer in the standby state. The System Timers
also switch states every 24 hours under control of a voting mechanism that is totally independent of that
used to switch the links. Selection of the active System Timer and active link(s) are independent.
Another major function of the system timer function of the AIMI is to provide CEB TDM bus timing and
data bus arbitration signals. In an Embassy system, the TDM buses in the CEBs must be synchronized
with the AEB. In order to accomplish this, the AEB uses a master clock which is used to transmit bits
onto all its links. The link interface circuit of each AIMI recovers this clock and passes it to its System
Timer section for generation of the TDM bit rate clock. In this manner, the CEB TDM buses operate at
the same nominal rate as the AEB TDM buses. The AIMI System Timer also uses this clock to generate
other system timing signals including signals which arbitrate usage of the system data bus.
Console Operator Interface Module

The COIM provides the link between console operator positions and the CEB. The COIM contains
all the electronics to convert and route audio from the dispatch position and the CEBs TDM
buses. The COIMs personality is programmed through the Console Database Manager (CDM).
Aliases are programmed using the Alias Database Manager (ADM).
Console Interface Electronics
The CIE provides the audio interface to the console operator. A microphone connected to the CIE
captures and transmits dispatch audio to the CEB. The console operator hears radio traffic audio
received through the CEB through the loudspeakers mounted in the CIE. The CIE acts as an interface
and format converter for data flowing between the console operator and the CEB.
The CIE may be located at the master site or at a remote dispatch site. A single CIE is required for each Dispatch
Console in the system. Figure 4-45 displays the front view of the CIE and Figure 4-46 displays the rear view.
6881009Y05-O April 2004 4-79

Console Database Manager Chapter 4: Hardware Functional Description
Figure 4-45 Console Interface Electronics Unit - Front View
Figure 4-46 Console Interface Electronics Unit - Rear View
Console Database Manager
The CDM is a CENTRACOM Gold Series applications program used to set up the specific customer
configuration of a CENTRACOM Gold Series console. It is used to create and maintain the consoles resource
configuration. For all Embassy systems, the CDM is used to program the COIM, AIMI, AMB, and ZAMBI.
4-80 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System CENTRACOM Elite Operator
In an Elite dispatch position the personality information entered in the CDM is automatically
disseminated to the PC client at the Elite console operator positions through the LAN. When the
operator starts the client position, the console operator client application checks for changes in the
configuration. If a new configuration is found, it is uploaded to the COIM.
The CDM operates at the zone level. Systems with consoles require one CDM per zone
installed on a server running the Windows operating system.
CENTRACOM Elite Operator

CENTRACOM Elite is the console GUI. CENTRACOM Elite Client OS is installed
on all Elite operator position workstations.
CENTRACOM Elite Admin

CENTRACOM Elite Admin pre-defines the console operator GUI resources. The screen configuration
files produced by this product can be shared by multiple Elite operator positions over the network.
Install CENTRACOM Elite Admin on all workstations that will be used to configure the console GUI
resources. Some customers may elect to have this product installed on each operator position workstation,
while others may elect to have this product installed on a subset of the workstations.
Admin Overview
The Admin software runs on a PC equipped with Windows operating system. The software creates
a virtual desktop on the screen where resources that are part of the system are displayed graphically.
Resources are grouped into folders, and one or more folders are stored as a configuration.
The system administrator uses the Admin software to set up configurations for the console operator client
desktops that group resources together in a logical way. The system administrator interacts with the
Admin software using the keyboard and a pointing device such as a mouse or a trackball.
The Admin software cannot monitor actual resources; its only purpose is to set up desktop
configurations for use by console operators.
Central Electronics Bank Card Upload Utility

The CEB Card Upload Utility is provided to upload databases directly into the CEB cards. This utility can also
upload the link information to the boards in the AEB. This product is required to upload signaling databases
into the modem boards for all signaling systems. Install this utility on any number of workstations as needed.
Alias Database Manager
The ADM software program is used in a CENTRACOM Gold Series system to provide on-line aliasing of
radio unit IDs, status numbers, message numbers, and outbound phone numbers. If aliases are used on any of
the console operator positions, then the ADM is required. The ADM operates at the zone level. Systems with
consoles require one ADM per zone installed on a server running the Windows operating system.
The ADM offers a GUI for easy operation. It may be run on one standalone computer or
multiple Elite console position computers simultaneously.
6881009Y05-O April 2004 4-81

Remote Dispatch Subsystem Chapter 4: Hardware Functional Description
The ADM on Elite console positions is a client/server application. The client portion of the software
is installed on each Elite console position PC. The server portion of the software is installed on one
of the computers, which then becomes the ADM server. The master alias database is stored on this
server. The ADM server downloads the alias information to each console PC through the LAN. The
downloaded aliases are stored on the Elite console positions PC hard drive.
Information on CDM/ADM alias download procedures can be found in the following manuals:
CENTRACOM Gold Series Console Database Manager (CDM) Manual (68P81094E45)

CENTRACOM Gold Series Alias Database Manager (ADM) Manual (68P81096E50)
Remote Dispatch Subsystem

Configuration and alias information for the Elite console operator centers is routed through the WAN switches
through a Fractional T1/E1 link. Each console operator location has a router and hubs or switches for
the Elite PC connections. Up to 30 Elite console operator centers are supported with up to 30 operator
positions per dispatch center. The maximum Elite Operator positions supported is 400. If more than 30
Elite Operator positions are required at any one location, multiple links should be deployed.
Ethernet Switch
The Elite console equipment is often connected to the LAN switch in a master site using Ethernet switches
such as the HP 2524 Procurve (Figure 4-47) or the HP 2626 Procurve (Figure 4-48) to create a shared Ethernet
LAN segment rather than connecting each piece of equipment to the LAN switch directly.
Figure 4-47 HP 2524 Procurve Switch
Figure 4-48 HP 2626 Procurve Switch
Since the Ethernet bandwidth requirements for the Elite LAN are much lower when compared to the Ethernet
bandwidth requirements of many of the other subnets, Elite console connections are often attached to one
of the site Ethernet switches. Figure 4-49 shows a sample remote site console configuration.
4-82 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Telephone Interconnect
Figure 4-49 Elite Console LAN with Ethernet Switch

This section describes ASTRO 25 Telephone Interconnect capabilities.
DTI-1000 Subsystem
The ASTRO 25 Telephone Interconnect subsystem (Figure 4-50) provides a means to connect the radio
system with the Public Switched Telephone Network (PSTN). This subsystem enables a subscriber to
initiate and receive calls through the PSTN. The Avaya Private Branch Exchange (PBX) and a control
and signalling server satisfy the telephone interconnect subsystem requirements. An optional echo
canceller can provide enhanced voice quality for the telephone interconnect subsystem.
The PBX performs all of the telephone switching functions and number handling operations required by the
PSTN. The PBX-to-radio system interface is accomplished with the Adjunct Control Signaling Server (ACSS).
6881009Y05-O April 2004 4-83

Adjunct Control Signaling Server Chapter 4: Hardware Functional Description
Figure 4-50 Telephone Interconnect Subsystem
The ASTRO 25 system architecture supports a maximum of one Telephone Interconnect subsystem per zone.
The Telephone Interconnect subsystem is located at the prime site and is capable of supporting a DS1 link to
the radio system. With an analog interface between the PBX and PSTN, a maximum of 24 analog trunks (LS,
GS, DID) are supported (eight ports on three analog interface cards). With a digital interface (a DS1) between
the PBX and PSTN, 24 trunks are supported when a T1 is employed and 30 trunks are supported when an E1
is employed. The ACSS provides operational status locally through alarm indications and front panel LEDs.
Configuration of the ACSS and fault messages is accessible through a TCP/IP connection to the ACSS.
The two modems connected to the PBX in Figure 4-50 are used for remote diagnostics and configuration. One
modem allows dial up access to the PBX terminal interface by factory personnel (Avaya) only. The second
modem provides access to the PBXs network interface for configuration and troubleshooting purposes.
Adjunct Control Signaling Server

The ACSS (Figure 4-51) is a Pentium computer running the Windows operating system. The
ACSS provides a call control link between the zone controller and the PBX so that calls can be
routed properly between a mobile radio and the PSTN. To serve this purpose, off-the-shelf Computer
Telephony (CT) Connect software is used. A CT Connect client, resident in the zone controller,
initiates call control messages to the PBX. The CT Connect software is capable of communicating
with many different types of PBXs using various different protocols.
4-84 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Avaya PBX
Figure 4-51 Adjunct Control Signaling Server
For the ASTRO 25 system, the Avaya PBX requires all adjunct call control messages
to be formatted as Avaya proprietary protocol.
The ACSS also provides the necessary signaling and tones that are not supported within the PBX itself.
For instance, a radio user may request that a string of overdial digits be sent towards the PSTN. Since
a digital mobile radio is not capable of generating DTMF tones, it must instead send a request to the zone
controller that the digits be generated on its behalf. Upon receiving such a request, the zone controller must
be capable of ensuring that the appropriate tones are played towards the PSTN. In order to accomplish
this, the ACSS is equipped with additional hardware capable of providing this functionality. All audio
connections between the PBX and radio system must be routed through the ACSS.
A customized application, referred to as the Tone Generation Server (TGS) application, is required
for proper control of the hardware. A client for the TGS application resides on the zone controller,
allowing the zone controller to control the TGS application over a TCP/IP connection.
In addition to the generation of DTMF overdial, the TGS application provides various tones,
such as time out timer warning tone, as well as the appropriate signaling to ensure the PBX
keeps all of its radio resources in auto-available mode.
The CT connect server is administered using the Intel-Dialogic configuration manager
application loaded on the ACSS.
Avaya PBX
The Avaya PBX (Figure 4-52) supports hunt groups. When more than one ground start (GS) or loop
start (LS) lines are installed, the GS/LS lines are linked together in such a way that if the first Central
Office (CO) GS/LS line is busy, the call is routed to the next line. This is called a hunt group and is
also sometimes referred to as a busy hunt sequence. Similarly, the lines can be linked in a 3 ring
transfer or no answer transfer sequence. If the DTI-1000 does not answer an inbound call within
three rings, the call will transfer to the next line in the hunt group. This is useful when the circuit
for a particular line malfunctions; inbound calls can still be processed on the remaining lines. Both
inbound (toward the DTI-1000) and outbound calls can be placed on this line.
Telephone features such as hunt and no-answer transfer are optional features
provided by your local phone company.
6881009Y05-O April 2004 4-85

Avaya PBX Chapter 4: Hardware Functional Description
DID lines allow landline users to directly dial into mobile subscriber units that have been setup to
receive direct calls. Typically, the DID trunk will be a block of one hundred numbers. When the
telephone company receives a call from a landline party, the CO switch strips off the exchange digits
and forwards the last five digits to the DTI-1000. The DTI-1000 passes the five digits to the zone
controller, which translates the digits into the user ID of the assigned mobile unit.
The total number of digits forwarded to the PBX may not always be five. The exact number
is set up between the local phone company and the PBX owner. However, the total number of
digits passed to the zone controller is five. Of these, the PBX may have to add or remove
digits to or from the number sent by the local Central Office (CO)
The DID line is unique in that a minimum of 100 different consecutive numbers, assigned by
the phone company, appear on one pair of wires. When additional DID lines are added it is not
necessary to order additional phone numbers. When a second DID line is added it sets up a hunt
group similar to that used in the CO GS/LS case described above.
The connection of the PBX to the telephone network can be either digital or analog. A digital connection is
provided through a T1 interface and is capable of having any combination of its time slots configured
as either ground start or direct inward dialing. The analog option requires either a CO Trunk interface
card (capable of either loop start or ground start signaling) or a DID Trunk interface card (capable of
servicing analog direct inward dial lines). Each card is capable of supporting up to eight phone lines.
ASTRO 25 systems do not support combining both analog and digital phone lines.
4-86 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Avaya PBX
Figure 4-52 Avaya PBX
Your PBX hardware configuration may be different than the one shown.
6881009Y05-O April 2004 4-87

Echo Canceller Chapter 4: Hardware Functional Description
Table 4-11 identifies the interface cards (circuit packs) installed in the PBX switch.
Table 4-11 PBX Switch Interface Cards
Slot Interface Card

1 TN2402 Processor
2 TN2182 Clock
3 TN2501 Announcement
4 TN464 DS1
5 Optional see Note below.
6, 7 TN 801 MAP-D (takes 2 slots, but 3 spaces)
8 TN799 C-LAN
Slots 5, 9, and 10 may be populated with either analog or digital trunk interface cards depending
on your specific hardware configuration (TN464, TN2224 digital line, TN793 analog line).
The Definity PBX is administered using the Avaya site administration application loaded on the
ACSS. Also, the PBX can interface with another PBX for tie trunk support.
Echo Canceller
The echo canceller provides enhanced voice quality for the telephone interconnect subsystem by adjusting
speech level and minimizing PSTN background noise when these conditions are affecting the overall
voice quality of a mobile subscribers telephone interconnect call. Call quality is enhanced when the
echo canceller reacts intelligently to varying signal levels and when it automatically optimizes signal
levels in the network. The echo canceller is typically installed in a standard 2 rack unit (2 RU) 19
shelf, but it can also be positioned as a desktop unit. In addition to the installation and mounting
assembly equipment, the echo canceller includes the following components:
Network Control Module (NCM) provides system control and monitoring

Echo Canceller Module (ECM) provides echo cancellation and voice quality enhancement
Fan tray assembly and filter provides thermal cooling for the modules
4-88 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Network Control Module
The echo canceller is an optional component of the telephone interconnect

subsystem and supports T1 and E1 interfaces.
The (3100M VQE) echo canceller is administered using the Tellabs 3105 craft station
application loaded on the ACSS.
Network Control Module

The NCM detects and collects data regarding the status of each ECM and communicates
this information to the LEDs and to a log file.
Echo Canceller Module

The ECM provides echo cancellation and voice quality enhancement to telephone interconnect
calls. Echo cancellation is accomplished through the interpretation of PCM signalling bits, line
idle code status, or processing of the serial communication commands. The typical ECM is a dual,
bi-directional wireline type module capable of supporting two DS1 circuits.
Fan tray assembly and filter

The fan assembly ensures that appropriate thermal cooling is provided to the echo canceller.
Network Security Components

Network security products and services in an ASTRO 25 communication system can

be grouped into the following categories:
Core Security Management Server (CSMS)

Network Interface Barrier
Core Security Management Server
The Core Security Management Server consists of hardware and software components required to ensure
that only authorized users access the radio network system. The CSMS is required to safely enable use of
system interfaces for remote service access and remote network management service activities.
The CSMS performs the following functions:
Administration of network antivirus software
6881009Y05-O April 2004 4-89

Core Security Management Server Chapter 4: Hardware Functional Description
Authentication of service interface users to ensure secure remote access

Administration of antivirus software for service users optional
Management of the firewalls and intrusion detection system sensors components
of a network interface barrier (optional)
The CSMS is shown in Figure 4-53.
Figure 4-53 Core Security Management Server
Administration of antivirus software for service users is optional depending upon whether
or not your service laptops are setup to be clients of the radio networks antivirus server.
Also, management of the network interface barrier is optional depending upon whether
or not the system employs Motorolas Network Interface Barrier (NIB).
The CSMS functions as a user authentication server controlling access through dial-in terminal servers
or service routers by maintaining individual user accounts and passwords for each authorized remote
user. Access to the network is denied if users do not provide appropriate credentials.
Authorized service and support personnel typically have a valid service support computer. A valid
service support computer has appropriate antivirus software installed. Service personnel using
a valid service support computer can be granted an authentication account and password. Once
service and support personnel (with an activated account and password) login to the radio network
with a valid service support computer, the CSMS is discovered. .
The anti-virus definitions for the valid service support computer can be identified and
updated when the computer is managed by the CSMS.
The following hardware and software components are part of the Core Security Management Server:
Core Security Management Server (CSMS) a rack-mounted Windows-based

server with keyboard, monitor and mouse
Windows 2000 Server Operating System (OS) software the CSMS
operating system software
SmartStart software server setup support software
Symantec Antivirus Server Corporate Edition - antivirus protection software
ISS RealSecure SiteProtector a network security monitoring, analysis, and reporting tool
Check Point SmartCenter Firewall Manager software tool for
configuring, managing, and monitoring firewalls
4-90 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Network Interface Barrier
RSA ACE Server software user authentication software to manage user credentials
and collect authentication events, logs, and alarms. Accepts or denies user access to
the system by matching user accounts to passwords.
RSA ACE Agent software optional authentication software support for remote access.
The ISS Real Secure SiteProtector software and Checkpoint firewall management software
may be installed, but not activated. When an optional network interface barrier (NIB) is
included with your system, the appropriate license keys should be available to activate
the software. The NIB provides firewall and intrusion detection support. Check Point
SmartCenter Pro is required when more than one NIB is employed.
Other service interface control products to support the CSMS include an InReach
terminal server for remote access.
Network Interface Barrier
The Network Interface Barrier is an optional set of hardware and software components providing
boundary enforcement and attack detection features to provide supplemental network security
protection. The NIBs safely enable use of the systems defined interfaces for integrated data, network
management, computer-aided dispatch, and billing. Deploying NIBs at each connection point
between radio system resources and external networks and equipment provides an important and
recommended level of security. The NIB firewall is shown in Figure 4-54.
Figure 4-54 Network Interface Barrier Firewall
It is recommended that one NIB is established for each access point to the radio
network. Up to six NIBs are supported.
6881009Y05-O April 2004 4-91

Radios Chapter 4: Hardware Functional Description
Basic components of the NIB include a firewall, an intrusion detection system sensor (IDSS), and Ethernet
LAN switch. The following hardware and software components are part of the NIB subsystem:
Firewall server a rack-mounted Nortel Alteon 5105 firewall server

Nortel Operating System (OS) software operating system software for the firewall server
Check Point Smartcenter software firewall component of the Check
Point Smartcenter suite on the CSMS
Intrusion Detection System Sensor (IDSS) a SUNFire V100 server
Solaris 8 Operating Environment operating system software for the IDSS
ISS RealSecure Network Sensor the IDSS sensor software
RSA Ace Agent UNIX-based authentication service software
Ethernet switch an HP ProCurve 2524 Ethernet LAN switch providing a
parallel connection between the Firewall and IDSS so that the IDSS can monitor
and report on traffic encountered by the firewall.
Check Point Smartcenter Pro is required when more than one firewall is employed.
The intrusion detection system (IDS) sensor is shown in Figure 4-55.
Figure 4-55 Intrusion Detection System Sensor
For more information on network security, see Chapter 8, "Network Security."
Radios

The ASTRO 25 system provides the infrastructure that allows communication between subscriber
radios. The radios can be portables and/or mobiles, but both must support the IMBE vocoder and the
ASTRO 25 feature set. The new Motorola radios are ASTRO 25 compatible.
Motorola radios that are ASTRO IMBE capable and currently operate in SmartZone or
SmartZone/OmniLink trunked systems can also operate in an ASTRO 25 system if they are flash
capable and can be upgraded to the new ASTRO 25 feature set.
4-92 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System ASTRO 25 Portable Radio Features
ASTRO 25 radios support various signaling schemes, analog / digital compatibility, conventional
capability, type 3 encryption, and military specifications C, D, and E. In addition, radios in the 800
MHz range offer an expanded frequency range of 762-870 MHz. The radios are FLASHport capable
through a Windows operating system-based CPS to allow for future software upgrades.
Data-capable radios are also supported.
ASTRO 25 Portable Radio Features
This section describes features supported by ASTRO 25 portable radios.
Signalling Types
The following is a list of signalling types:
ASTRO 25 9600cc trunking

APCO P25 digital conventional
Analog conventional
Scan Features
Scan - both priority and non-priority scan
Talk Group Scan - supported in 9600 trunking
Conventional Scan - supported in 9600 trunking
Call Types
Talkgroup call
Announcement call
Call alert - supported in 9600 trunking
Private call - supported in 9600 trunking
Telephone Interconnect - supported in 9600 trunking
Emergency alarm and Emergency call - supported in 9600 and 3600 trunking
Radio-to-radio encryption
6881009Y05-O April 2004 4-93

Subscriber Radio Overview Chapter 4: Hardware Functional Description
Subscriber Radio Overview

Table 4-12 provides a summarized list of commonly used mobile and portable radios for your system.
Table 4-12 Subscriber Radio Overview
Encryption Module Voice or Data

Subscriber Radio Frequency Bands Encryption Support
Supported Usage
XTS 5000 Portable UCM 700 MHz, 800 MHz, voice and data DES/DES-OFB,
VHF, UHF R1/R2 DES-XL, DVP-XL,
DVI-XL, AES, ADP
XTL 5000 Mobile UCM 700 MHz, 800 MHz, voice and data DES/DES-OFB,
VHF, UHF R1/R2 DES-XL, DVP-XL,
DVI-XL, AES, ADP
ASTRO Spectra Plus UCM 800 MHz, VHF, UHF voice and data DES/DES-OFB,
Mobile R1/R2 DES-XL, DVP-XL,
DVI-XL, AES, ADP
ASTRO Spectra Mobile EMC, UCM 800 MHz voice DES/DES-OFB,
DES-XL, DVP-XL,
DVI-XL (no ADP)
ASTRO Spectra EMC, UCM 800 MHz voice DES/DES-OFB,
Consolette DES-XL, DVP-XL,
DVI-XL (no ADP)
XTS 3000 Portable EMC, UCM 800 MHz voice DES/DES-OFB,
DES-XL, DVP-XL,
DVI-XL (no ADP)
ASTRO SABER EMC, UCM 800 MHz voice DES/DES-OFB,
Portable DES-XL, DVP-XL,
DVI-XL (no ADP)
Of the subscriber radios listed in Table 4-12, only the XTS 5000 portable, XTL 5000 mobile,
and ASTRO Spectra Plus mobile subscriber radios support over-the-air rekeying (OTAR).
For more information on OTAR, see ASTRO 25 Trunked Integrated Voice and Data System
Release 6.4/6.4 SE Managing Secure Communications (6881009Y65)
Motorola XTS 5000 Portable and XTL 5000 Mobile

The XTS 5000 Project 25 Digital Radio is an IP-enabled digital radio to enhance security and performance
with seamless, high quality communication features. The versatile XTS 5000 portable radio is designed
to operate on ASTRO 25 Digital Trunked systems, ASTRO Analog and Digital Trunked systems, and
Analog and Project 25 Digital conventional operation. The XTS 5000 provides FLASHport technology
support for upgrading software to easily update the radio with future enhancements, if necessary.
As a companion to the XTS 5000 portable radio, the XTL 5000 mobile radio is capable of digital or analog
operation supporting analog or digital conventional, APCO 16, and APCO 25 systems. The XTL 5000 also
has mutual aid capability. For increased security, a universal encryption module for the XTL 5000 can be
4-94 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Motorola ASTRO Spectra and ASTRO Spectra Plus
added without having to open the radio. The XTL 5000 is programmed through the Customer Programming
Software (CPS) using an RS-232 or USB port for faster programming. FlashPort support for the XTL
5000 lets you customize the mobile radio with new software to ensure future enhancements.
Figure 4-56 XTS 5000 Portable Radio
Motorola ASTRO Spectra and ASTRO Spectra Plus

The ASTRO Digital Spectra mobile radios represent the first fully digital two-way radio from Motorola for
the land mobile environment. ASTRO Spectra mobile radios are designed for maximum interoperability. As
part of an ASTRO 25 digital trunking solutions system, the ASTRO Spectra mobile radios transmit 9.6 kb/s of
user information while operating on narrow band 12.5 kHz channels. ASTRO Spectra mobile radios can
operate on both wide band (25/30 kHz) and narrow band (12.5 kHz) channels, and on both conventional and
trunked systems. These different operating modes are programmed into the radios on a channel-by-channel
basis. The ASTRO Spectra mobile can be upgraded through FLASHport to full ASTRO 25 capability.
The ASTRO Spectra Plus mobile is a digital vehicular-mounted radio subscriber with model options that
cover power ranges from 15 watts to 110 watts. It is fully compatible with ASTRO 25 systems.
6881009Y05-O April 2004 4-95

Considerations for Radio Use Chapter 4: Hardware Functional Description
Figure 4-57 ASTRO 25 Radio
Considerations for Radio Use
When operating a radio, consider the following:
Hold the radio in a vertical position in front of face with the microphone (and other
parts of the radio including antenna) at least one to two inches (2.5 to 5 cm) away
from the lips. Keeping the radio at a proper distance is important since RF exposures
decrease with (increasing) distance from the antenna.
For body-worn operation, always place the radio in a Motorola-approved clip, holder,
holster, case, or body harness, if available for this product. (All Motorola-approved accessory,
antenna, and device combinations comply with FCC occupational/controlled environment
RF exposure limits. Exposure information on various accessory, antenna, and device
combinations can be found under the Display Exhibit section of http://www.fcc.gov/oet/fccid
after searching on the FCC ID number, which can be obtained from the label of your
radio.) Use of non-Motorola-approved accessories may result in exposure levels which
exceed the FCCs occupational /controlled environment RF exposure limits.
If you are not using a body-worn accessory and are not using the radio in the intended use
position in front of the face, then ensure the antenna and the radio are kept 2.5 cm (one
inch) from the body when transmitting. Keeping the radio at a proper distance is important
since RF exposures decrease with (increasing) distance from the antenna.
To enable the feature to expand the number of adjacent sites, subscriber radios
must be expanded Adjacent Site Broadcast capable radios.
4-96 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Backup Power Recommendations
Backup Power Recommendations

At a minimum , Motorola recommends backup power support be provided for the

components marked with an X in Table 4-13.
Table 4-13 Components and UPS Support
Component Component Component

Zone Controller X Master Site Channel Bank Simulcast Remote Site Router X
MOSCAD DACS X Simulcast ASTRO TAC X
Comparator
AEB UCS X Site Repeaters X
CEB SSS X STR 3000 Base Stations X
MGEG X ZDS X Quantar Receiver X
DIU ZSS X ASTRO TAC Receiver X
PDG X ATR X Core Security Mgmt Server X
Core & Exit Routers X FV INM X Firewall Server X
Gateway Routers X ESMS IDSS X
GGSN Router X WSMS Simulcast Site Controller X
PSC 9600 X TNPS Prime Site Channel Bank X
Simulcast Prime Site X PNM Client Simulcast Prime Site Ethernet X
Controller Switch
Remote OSS Router TNM Client Ethernet LAN Switch X
Digital Remote Access Router Terminal Servers X Ethernet Switch (HP2524) X
(for DDS or DDS/T1/FT1)
Border Router ACSS X WAN Switch X
Peripheral Router Elite Console CIE
Remote Site Router X Trak 9100 NTP X
The list does not suggest that any component not indicated as recommended for UPS
support should not also be supported. A minimum consideration should be made to keep
the system in wide area trunking, in case of a power interruption.
6881009Y05-O April 2004 4-97

Backup Power Recommendations Chapter 4: Hardware Functional Description
4-98 6881009Y05-O April 2004

Chapter
5
Radio Frequency Subsystems

A radio frequency (RF) subsystem in an ASTRO

25 system consists of a group of hardware and
software components providing radio communication coverage to the system.
To satisfy the need to accommodate a variety of coverage areas and system feature requirements,
the following types of RF subsystems are available:
ASTRO 25 Repeater Site subsystem: A 700 MHz or 800 MHz subsystem

with ASTRO 25 Repeater sites
IntelliRepeater Site subsystem: A 700 MHz or 800 MHz subsystem
with Quantar IntelliRepeater sites
Digital Simulcast Subsystem: A 700 MHz or 800 MHz subsystem with
a prime site and remote sites
Digital Simulcast Subsystem with support for receive only sites: A VHF/UHF subsystem
with a prime site and remote sites, capable of providing support for receive only remote sites
Single Transmitter Receiver Voting (STRV) Subsystem: A VHF/UHF single-transmitter
subsystem with a prime site and remote sites, including support for a colocated prime
site, transmit remote site and receive only remote sites
ASTRO 25 Repeater Site subsystem
The ASTRO 25 system recognizes and treats each ASTRO 25 Repeater site as a separate site, each
covering a single and separate geographic area. However, because the communication characteristics and
components of each site are similar, a group of ASTRO 25 Repeater sites is considered to be a subsystem.
Each ASTRO 25 Repeater site has one ASTRO 25 Site Repeater for each communication channel and
two separate site controllers. Up to 28 ASTRO 25 site repeaters can exist in an ASTRO 25 repeater
site. For more detailed information, see "ASTRO 25 Repeater Site" on page 5-3.
IntelliRepeater Site subsystem
The ASTRO 25 system recognizes and treats each ASTRO 25 IntelliRepeater site as a separate site, each
covering a single and separate geographic area. However, because the communication characteristics and
components of each site are similar, a group of ASTRO 25 IntelliRepeater sites is considered to be a subsystem.
The repeaters in the IntelliRepeater subsystem have the built-in intelligence of a site controller, in contrast to
the physically separate site controller used in an ASTRO 25 Repeater site subsystem. Each IntelliRepeater site
can have up to 28 IntelliRepeaters. For more detailed information, see "IntelliRepeater Site" on page 5-32.
Digital Simulcast Subsystems
Two simulcast subsystems are identified to distinguish between the simulcast subsystem that operates in the
700 MHz or 800 MHz bands but do not support receiver only remote sites, from the simulcast subsystem that
operates in the VHF/UHF bands and do support receiver only remote sites. In either simulcast subsystem,
the simulcast prime site is the central control location for the other sites in the subsystem. Because the
simulcast prime site controller at the simulcast prime site provides control of the simulcast remote sites for the
subsystem, the ASTRO 25 system recognizes and treats the each simulcast subsystem as a single site.
6881009Y05-O April 2004 5-1

Backup Power Recommendations Chapter 5: Radio Frequency Subsystems
A simulcast subsystem can contain up to 15 remote sites each with up to 30 base radios. A simulcast subsystem
also contains two site controllers, two Ethernet switches, one or two site routers, up to 30 comparators, and
site reference components. Simulcast subsystems support either a 10/100Base-T LAN or a 10Base-2 LAN at
the prime site and remote sites. For more details, see "Digital Simulcast Subsystems" on page 5-36
The Single Transmitter Receiver Voting (STRV) subsystem covers a single geographic area with a single
transmitter and provides radio communication support in the VHF/UHF frequency bands. An STRV
subsystem must include an STRV prime site and a single transmit remote site (if not already colocated with
the STRV prime site). Some remote sites can be receive-only remote sites. An STRV subsystem must contain
at least one or more remote sites. The STRV subsystem contains many of the same components found in
a simulcast subsystem, but the STRV subsystem does not require simulcast site reference devices because
simultaneous transmission (time launching of signals) from multiple transmitters is not required in a single
transmitter subsystem. For more details, see "Single Transmitter Receiver Voting Subsystem" on page 5-72.
The simulcast subsystems and the single transmitter receiver voting subsystems are part of
the multi-site subsystem shown in the Zone Configuration Manager.
For integrated voice and data functionality for the ASTRO 25 repeater site subsystem, digital
simulcast subsystems, or STRV subsystem, see Chapter 10, "Integrated Voice and Data."
The repeaters and base stations used for various types of sites support each RF subsystem as shown in Table 5-1.
Table 5-1 RF Subsystem Overview
Subsystem Sites Repeater or Base Stations

ASTRO 25 Repeater site subsystem ASTRO 25 Repeater sites QUANTAR ASTRO 25 Site Repeater,
800 MHz, 700 MHz, VHF, UHF 800 MHz, VHF, UHF
ASTRO 25 Repeater sites STR 3000 ASTRO 25 Site Repeater,
700 MHz
IntelliRepeater subsystem 800 IntelliRepeater sites QUANTAR IntelliRepeater 800 MHz,
MHz, VHF, UHF VHF, UHF
Simulcast subsystem 800 MHz or Simulcast prime site Not used, unless a simulcast remote
700 MHz A prime site with remote site is colocated with the prime site.
sites.
Simulcast remote site, 800 MHz STR 3000 base station, 800 MHz
Simulcast remote site, 700 MHz STR 3000 base station, 700 MHz
Simulcast Subsystem VHF/UHF Simulcast VHF/UHF prime site Not used, unless a simulcast remote
A prime site with remote sites. site is colocated with the prime site.
Simulcast VHF/UHF remote site QUANTAR base station, VHF/UHF
5-2 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System ASTRO 25 Repeater Site
Table 5-1 RF Subsystem Overview (Continued)

Subsystem Sites Repeater or Base Stations
Simulcast Subsystem VHF/UHF Simulcast VHF/UHF receiver only QUANTAR base station receiver,
A prime site with receive only remote sites VHF/UHF
remote sites.
Simulcast VHF/UHF receiver only ASTRO-TAC receiver, VHF/UHF
remote sites alternative receiver
Single Transmitter Receiver Voting STRV prime site (same as simulcast Not used, unless an STRV remote site
(STRV) subsystem A prime site subsystem prime site for VHF/UHF) is colocated with the prime site.
with remote sites.
STRV transmit remote site QUANTAR Base Station, VHF/UHF
STRV receive only remote site (same QUANTAR base station receiver,
as the simulcast VHF/UHF receive VHF/UHF
only remote site)
STRV receive only remote site (same as ASTRO-TAC receiver, VHF/UHF
the simulcast VHF/UHF receive only
remote site alternative receiver)
In the ASTRO 25 system, a repeater is a functional characteristic of a radio frequency

communication device providing both transmit and receive functionality without
the need to accommodate system components requiring a wireline communication
interface which is typically used for dispatch or voting equipment. In contrast, a
base station is a radio frequency communication device that typically does provide
wireline support for dispatch or voting equipment.
The hardware and software components of a receive only remote site as part of a
simulcast subsystem or single transmitter receiver voting subsystem are the same. A
receive only remote site provides support for either subsystem.

An ASTRO 25 Repeater site is a single-solution, RF communication site designed to optimize

your channel capacity requirements operating in the 800 MHz and VHF/UHF bands. An ASTRO
25 Repeater site can include the following components:
6881009Y05-O April 2004 5-3

ASTRO 25 Repeater Site Operational Modes Chapter 5: Radio Frequency Subsystems
ASTRO 25 Site Repeaters One for each communication channel at the

site, each includes an Ethernet interface.
PSC 9600 site controllers Dual controllers for redundancy.
Ethernet switch Single or dual switches (10/100 BaseT) to meet
channel capacity requirements.
Remote site router(s) Single router or dual router configuration for
master site and site repeater interfacing.
Channel Bank Only for mutual aid support. For more information, see
Chapter 6, "ASTRO 25 Systems and Mutual Aid."
MOSCAD An optional component to support monitoring and reporting
operating system status.
The ASTRO 25 Site Repeaters can be configured as voice channels, data channels, or
control channels. Up to four ASTRO 25 Site Repeaters per site can be designated as control
channels. ASTRO 25 Site Repeaters include the following:
QUANTAR ASTRO 25 Site Repeater Non-linear C4FM Transmit-

ter/Receiver, 800 MHz, VHF, UHF
STR 3000 ASTRO 25 Site Repeater Linear LSM Transmitter/Receiver, 700 MHz
Two PSC 9600 site controllers provide protection against a single point of failure. Each PSC 9600 is
programmed with a set of rules that helps the controller determine which one of the two assumes the role of
primary controller initially and when it is necessary for the other controller to take over the operation of the
subsystem. If the active site controller fails, the other site controller automatically takes control of the site.
The network infrastructure at an ASTRO 25 Repeater site includes an Ethernet switch and a site
router. Based on the number of base stations at the site, one or two 10/100Base-T Ethernet switches
provide ports for interfacing the controllers, base stations, site router(s), and MOSCAD. A computer,
loaded with the Configuration/Service Software (CSS) application, can be connected to a port on the
Ethernet switch to conduct programming changes or troubleshooting services.
The site router(s) process the physical and logical data link to support communication between
the zone controller and the site controller. The site router provides a WAN interface that handles
all of the traffic to and from the zone for the RF Site including voice, control, data, and Network
Management traffic. The site router also provides the connection between the ASTRO 25 Repeater
Site LAN and the transport network. Communication between site controllers, site Ethernet
switches and all the repeaters, takes place through a dedicated LAN.
A channel bank is installed as part of the subsystem only if mutual aid is required at the geographical
site. Mutual aid audio can use the same transport facilities (T1 or E1) as the ASTRO 25 system, but it is
not processed by the IP components in the network. The IP based devices in the system are not aware of
the existence of mutual aid audio. The channel bank also connects to a FlexWAN port on the site router(s)
to transport voice and network management data IP packets to and from the master site.
In addition to the components listed above, radio frequency distribution at an ASTRO 25
Repeater site is accomplished through equipment that includes the receive and transmit
antennas, isolators, multicouplers, and combiners.
ASTRO 25 Repeater Site Operational Modes
The operational modes for an ASTRO 25 Repeater site are:
5-4 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System ASTRO 25 Repeater Site Operational Modes
Wide Area Trunking An ASTRO 25 Repeater site can remain in wide area
trunking as long as the following resources are available:
One voice channel
One control channel
A site controller
Connectivity through the Ethernet switch or switches
A site router
A physical link between the subsystem and the master site
A logical path between the site router and the master site IP equipment.
If a PSC 9600 site controller switchover occurs while the subsystem is in wide area trunking state,
all active voice calls at the site continue without an interruption in service. No in progress voice
calls are lost on a PSC 9600 site controller switchover. This is possible because the active voice
call states and databases of the active and standby PSC 9600 site controllers are synchronized.
Site Trunking Site trunking operation takes place when there is no physical
or logical link between the site router(s) and the master site. Conditions
required to maintain site trunking include:
One voice channel
One control channel
A site controller
Connectivity through the Ethernet switch or switches.
Site trunking can also be initiated from the diagnostic capability in the ZCM.
If a PSC 9600 site controller switchover occurs while the site is in the site trunking
state, all active calls at the site will be transmission trunked.
Failsoft Failsoft mode of operation at an ASTRO 25 Repeater Site takes place only when
both site controllers fail, the Ethernet switch fails (or both fail in a dual switch configuration),
there are no operational control channel capable repeaters, or all voice channels are inoperative.
Failsoft can also be initiated from the diagnostic capability in the ZCM.
Site Off Site Off is an operational mode that can be initiated from the diagnostic
capability in the ZCM. In this state, the subsystem is not available to the radios.
If one of the PSC 9600 site controllers fails, the other maintains the system in
wide area trunking. If the site is in site trunking mode, however, the PSC 9600
manages all site functions and call processing.
6881009Y05-O April 2004 5-5

ASTRO 25 Repeater Site Subsystem Configurations Chapter 5: Radio Frequency Subsystems
For ASTRO 25 Repeater sites using dual site routers, a master site interface link failure or
a site router failure has no effect on wide area operations since the remaining site router
maintains the links. With a single router configuration, however, the subsystem enters site
trunking mode if a master site interface link failure or a site router failure occurs.
ASTRO 25 Repeater Site Subsystem

Configurations

The ASTRO 25 Repeater site is a single-site solution supported by ASTRO 25 systems. Supported
configurations for an ASTRO 25 Repeater site include:
Single router, single Ethernet switch for subsystems with 18 or fewer base stations
Single router, dual Ethernet switch for subsystems with more than 18 base
stations, up to 28 base stations.
Dual router, dual Ethernet switch for subsystems with up to 28 base stations
The specific configuration installed in a system depends on customer requirements
and transport (T1 or E1) resources.
Single Router, Single Switch Subsystem

Single Ethernet switch configurations are supported at ASTRO 25 Repeater Sites with fewer
than 18 RF channels. Figure 5-1 illustrates this configuration.
5-6 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Single Router, Dual Switch Subsystem
Figure 5-1 Single Router, Single Switch Subsystem
Two site controllers are installed in this type of configuration to provide a level of
redundancy at the control level.
Conditions required for wide area operation include:
One operational site controller.
The site router. If the site router fails, the subsystem enters the site trunking mode.
The Ethernet switch. If the Ethernet switch fails, the site enters Failsoft.
One control channel.
One voice channel
If the site router fails, the subsystem enters the site trunking mode. If the Ethernet
switch fails, the site enters Failsoft.
Single Router, Dual Switch Subsystem

Figure 5-2 illustrates one of the possible configurations for an ASTRO 25 Repeater Site.
This particular configuration supports 28 base stations.
6881009Y05-O April 2004 5-7

Single Router, Dual Switch Subsystem Chapter 5: Radio Frequency Subsystems
Figure 5-2 Single Router, Dual Ethernet Switch ASTRO 25 Repeater Site
An interface between the two Ethernet switches provides access to all the base stations by either controller.
The interface also makes it possible for any base station to be able to route its traffic to the site router.
Conditions required for wide area operation include:
One operational site controller
The site router
Connectivity through one Ethernet switch
One control channel
One voice channel
This type of installation prevents loss of trunking operation in cases of a single Ethernet switch failure. The
system remains in wide area trunking mode with half the RF resources if the Ethernet switch that is connected
to the site router remains operational. If the switch that is connected to the site router fails, the site operates in
site trunking mode with the remaining Ethernet switch and the RF resources connected to it.
The dual Ethernet switch configuration can be used with any channel configuration. It is required at
ASTRO 25 Repeater Sites with more than 18 trunked channels. Optionally, it can be used at sites
with fewer than 18 channels to permit the site to remain in a trunked mode.
5-8 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Dual Router, Dual Ethernet Switch Subsystem
Dual Router, Dual Ethernet Switch Subsystem

The dual site router, dual Ethernet switch configuration (Figure 5-3) provides the highest level of
redundancy to the subsystem. Single point failures can occur at the site routers, site controllers,
and repeaters, without bringing the subsystem out of wide area operation.
The dual site router link to the zone master site yields path diversity for the RF site link. It
requires two Ethernet switches at the ASTRO 25 Repeater Site.
Figure 5-3 Dual Router, Dual Switch ASTRO 25 Repeater Site
Conditions required to maintain wide area operation include:

A site controller
A site router
Connectivity through one or both Ethernet switches
One voice channel
One control channel
A logical path between the site router and the master site IP equipment
6881009Y05-O April 2004 5-9

WAN Switch Redundant Link Interface Configuration Chapter 5: Radio Frequency Subsystems
WAN Switch Redundant Link Interface Configuration

Remote Subsystems with redundant routers and site links require additional resources at the master site.
Figure 5-4 demonstrates the implementation of a redundant link interface configuration using DS1 8P
FP (or equivalent E1) WAN switch interface cards and WAN switch interface panels.
Figure 5-4 DS1 8P FP Card and WAN Switch Interface Panel - Redundant Interface
5-10 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System ASTRO 25 Site Repeaters
The Fast Failover feature of the WAN switch cannot be used with sites that have redundant site links.
ASTRO 25 Site Repeaters

Two types of ASTRO 25 Site Repeaters that can be used in ASTRO 25 Repeater sites:
The QUANTAR ASTRO 25 Site Repeater Used for 800 MHz, VHF, and UHF
installations. See "QUANTAR ASTRO 25 Site Repeater" on page 5-11
The STR 3000 ASTRO 25 Site Repeater Used for 700 MHz installations. See
"STR 3000 ASTRO 25 Site Repeater" on page 5-15.
Both repeaters provide a modular, flexible design and support upgrades through hardware and/or
software to accommodate future repeater or system enhancements.
QUANTAR ASTRO 25 Site Repeater
The QUANTAR ASTRO 25 Site Repeater includes the following modules:

Receiver module
Station Control Module (SCM)
Transmitter (The exciter and power amplifier provide the repeaters transmit functions.)
Exciter module
Power Amplifier module
Power supply
Figure 5-5 and Figure 5-6 show front views of the ASTRO 25 Site Repeater.
6881009Y05-O April 2004 5-11

QUANTAR ASTRO 25 Site Repeater Chapter 5: Radio Frequency Subsystems
Figure 5-5 QUANTAR ASTRO 25 Site Repeater, 800 MHz Version - Front View
Figure 5-6 QUANTAR ASTRO 25 Site Repeater, UHF Version - Front View
The VHF version, not shown, has a receiver module with five frequency adjusting knobs,
compared to the three shown on the UHF version Figure 5-6.
5-12 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Receiver Module
Receiver Module
The Receiver module provides the receiver functions for the repeater. Each receiver module is comprised
of a Preselector Filter Assembly and a Receiver Board, all contained with a slide-in module housing.
The receiver module performs highly selective bandpass filtering and dual down conversion of the
station receive RF signal. A custom receiver integrated circuit then performs an analog-to-digital
conversion of the received signal and outputs a differential data signal to the SCM.
Station Control Module
The SCM serves as the main controller for the station to provide signal processing and operational
control over the other station modules. The SCM board contains the following:
A microprocessor
A Digital Signal Processor (DSP)
An Ethernet interface
Support circuitry
The SCM also contains the station operating software (stored in FLASH memory) and codeplug
information to define the personality of the station. This includes system capabilities and operating
parameters, such as output power and operating frequency.
The Ethernet interface provides the ASTRO 25 Site Repeater with the mechanism to take the ASTRO
audio, after processing by the receiver and DSP circuitry, as its input and provide audio as packets at its
output that are ready for transmission over the IP-based network. The Ethernet interface sends these audio
packets through the subsystem LAN, and system infrastructure, to the master site for distribution.
Audio that is received from the master site for transmission to subscribers is also processed by the
Ethernet interface. The ASTRO audio is recovered from the audio IP packets and delivered to the DSP
and transmission circuitry to be processed for transmission to the subscribers.
The Ethernet interface also provides the connectivity between the repeaters and the LAN. Three
types of information flow across the LAN to/from the repeaters:
Control information that carries site information, channel assignments, and

identification numbers for call processing
Audio encapsulated as Ethernet packets
Network management information
Transmitter
The transmitter is made up of the exciter board and the power amplifier.
The exciter board generates a low-level, modulated RF signal, which it passes to the
power amplifier. The exciter is contained in a slide-in module.
6881009Y05-O April 2004 5-13

Power Supply Chapter 5: Radio Frequency Subsystems
The power amplifier module amplifies the modulated signal and sends it to the
transmit antenna for transmission to the subscribers.
Power Supply
The power supply module accepts an AC input (90 - 280 V AC, 47 - 63 Hz) and generates + 5 V
DC and + l4.2 V DC operating voltages to power the station modules. Each power supply module
is made up of several switching type power supply circuits, power factor correction circuitry,
battery charger/revert circuitry (only on stations with battery back up capability), and diagnostics
and monitoring circuitry, all contained within a slide in module housing.
The power supply module provides the following features:
Auto ranging for input voltage and frequency circuitry automatically adjusts for input ranges
of 90 - 280 V AC and 47 - 63 Hz; no jumpers, switches, or other settings are required.
Input transient and EMI protection, gas discharge, and filter devices protect the power
supply circuitry from AC line voltage transients and electromagnetic interference.
Internal voltage and current limiting circuitry continually monitors critical voltages and
currents and shuts the power supply down if preset thresholds are exceeded.
Temperature protection from a temperature protection module which contains a
thermostatically controlled, built-in cooling fan. The power supply shuts down
if the temperature exceeds a preset threshold.
Continuous diagnostic monitoring for critical internal parameters. The results are reported to
the SCM, which can automatically provide correction for certain operating conditions.
The power supply module contains the following circuitry:
Input Conditioning Circuitry Consists of AC line transient protection, EMI filtering,
rectifier, and power factor correction circuitry, and filtering.
Startup Inverter Circuitry Provides VCC for power supply circuitry
during initial power up.
Main Inverter Circuitry Consists of switching type power supply that
generates the + 14.2V DC supply voltage.
+ 5 V Inverter Circuitry Consists of switching type power supply that
generates the + 5 DC supply voltage.
Clock Generator Circuitry Generates 267 kHz and 133 kHz clock signals used
by pulse width modulators in the three Inverter circuits.
Diagnostics Circuitry Converts analog status signals to digital format for transfer to SCM.
Address Decode Circuitry Performs address decoding to provide chip
select signals for the A/D and D/A converters.
Battery Charging/Revert Circuitry (optional) Charges external storage battery and
automatically reverts to battery power in case of AC power failure.
5-14 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System STR 3000 ASTRO 25 Site Repeater
STR 3000 ASTRO 25 Site Repeater

The Motorola STR 3000 ASTRO 25 Site Repeater is the solution for 700 MHz installations and is based
on the STR 3000 platform previously developed for ASTRO 25 simulcast subsystems. The 700 MHz
band is designated as a digital-only band and therefore compatible with ASTRO 25 systems. This
repeater supports expansion of 800 MHz subsystems where frequencies in this higher band are not
available. A subsystem with a mixture of 800 MHz and 700 MHz repeaters requires portables and
mobiles capable of operating across both bands. A software solution is available to allow 700 MHz only
radios to access the system and communicate with 700 MHz or 800 MHz radios.
Figure 5-7 illustrates the new 700 MHz, STR 3000 ASTRO 25 Site Repeater, which
supports the following features:
Coverage of the 700 MHz public safety band, which currently consists of 764-776
MHz transmit range and 794-806 receive range
C4FM modulation in 12.5 kHz channel bandwidths
A standard cavity combiner with a minimum 150 kHz transmitter to transmitter spacing
12 transmitters maximum per antenna
Software Download Manager upgrade capability
Programmable with CSS
The Radio Frequency Distribution System (RFDS) consists of a preselector, receive multicoupler
(RMC), transmit circulators, transmit combiner with integrated isolators, and a power monitor unit
(PMU). This unit has been designed specifically for the 700 MHz, STR 3000 repeaters.
Figure 5-7 STR 3000 ASTRO 25 Site Repeater 700 MHz
6881009Y05-O April 2004 5-15

STR 3000 ASTRO 25 Site Repeater Components Chapter 5: Radio Frequency Subsystems
STR 3000 ASTRO 25 Site Repeater Components
The 700 MHz STR 3000 site repeater is similar to the simulcast STR 3000 base radio from the hardware
perspective. Differences exist in the receive and transmit modules to enable the repeater to process
frequencies in the 700 MHz frequency band. The modules and their function are listed in Table 5-2.
Table 5-2 STR 3000 ASTRO 25 Site Repeater (700 MHz) Modules
STR 3000 ASTRO 25 Site

Description
Repeater Module
-48 VDC power supply Receives -48 VDC as its input and converts it to the
voltages required by the other repeater modules. For
additional information on component power supplies,
see Appendix A, "Power Supply Reference."
Exciter Generates the transmit frequency and provides the
modulation functions for the repeater. It supplies the
modulated signal to the power amplifier.
Power Amplifier (PA) Provides the transmitter functions for the repeater
in conjunction with the exciter. The PA accepts the
low-level modulated RF signal from the exciter and
amplifies the signal for transmission through the RF
output connector.
Base Radio Control (BRC) module Provides signal processing and operational control for
the repeater modules.
Receiver Provides detection, amplification, conversion, and
filtering of incoming signals.
The STR 3000 ASTRO 25 Site Repeater requires an external 5 MHz frequency reference. The reference
is provided by a frequency standard internal to the PSC 9600 site controller.
Control Module
The DB9 connector on the control module is used to program the repeater with its IP address. All
other programming is accomplished through the repeaters LAN connection.
The control module monitors the functions of the repeater modules. The LEDs on the front
panel indicate the status of the monitored modules. The CTL LED on the front panel illuminate
momentarily on initial repeater power-up and resets. Figure 5-8 shows the front panel of the
control module and Table 5-3 describes the function of the LEDs.
5-16 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Control Module
Figure 5-8 LED Indicators on Control Module
Table 5-3 LED Description
LED Color Normal State If the LED is It indicates that

On Green On On The repeater is on.
Fail Red Off On The repeater failed.
Blinking on once per second. The external frequency reference
failed or the receiver or transmitter
is not locked on frequency.
Blinking on twice per second. The station is being configured.
SVC Amber Off Blinking on once per second. The repeater is in service mode.
Blinking on twice per second. The transmitter is inhibited.
CTL Green Off On This channel is the current control
channel.
On and blinks off for 250 An inbound signaling packet arrived.
milliseconds.
Blinking once per second. This channel is in failsoft.
Rx Green Off On The receiver is active.
Off The receiver is inactive
Blinking once per second. The channel is detecting an illegal
carrier.
PA Green On On The base radio is transmitting.
Blinking Power has dropped below the
programmed level.
StnD Red Off Off The repeater is operating normally.
Blinking on once per second. The receiver is inhibited.
Blinking on twice per second. The transmit function (Exciter, PA)
is inhibited.
V24 Green On On PSC link is established.
Blinking once per second. PSC link is lost.
6881009Y05-O April 2004 5-17

PSC 9600 Site Controller Chapter 5: Radio Frequency Subsystems
PSC 9600 Site Controller

Figure 5-9 shows the PSC 9600 site controller, which is the control interface between the
ASTRO 25 Repeater site and the zone controller at the zones master site. The PSC 9600 site
controller is capable of supporting up to 28 trunked channels.
Figure 5-9 PSC 9600 Site Controller - Front View
The primary functions of the PSC 9600 site controller include:

Provides redundant site control.
Redundant PSC 9600 site controllers are required at each
ASTRO 25 Repeater site. Upon initialization, the PSC 9600 site controllers negotiate
which one will be the active controller and which one will be the standby controller. If
the active PSC 9600 site controller fails, the standby controller automatically takes over
command and control of site communications, channel resources, and active calls at the
site. The standby controller detects that the active controller is no longer available and
become the active controller prior to the channels entering Failsoft mode.
Maintains a link to the zone controller at the zones master site.
Translates and routes call control information from the zone controller to the RF channels.
Selects and assigns channel resources based on service requests when in site trunking.
Decode Inbound Signaling Packet (ISP) requests received from the Control channel (CC).
Generates Outbound Signaling Packet (OSP) grants that are transmitted through the
Control channel to direct subscriber units to a specific channel.
Determines required link control for transmission on active channels.
Performs resource and fault management functions for the site and RF channels.
Reports changes in site state or RF channel capability to the zone controller
when in wide area mode.
Sends SNMP traps to FullVision INM, reporting critical alarm conditions,
device status, link status, and alarm messages.
Supports configuration changes from the ZCM and CSS applications.
Maintains an alarm log to capture diagnostic test failures.
Generates the Base Station Identifier (BSI) on command from the zone controller when in
wide area operation or based on an internal timer when in site trunking operation.
Provides a frequency reference signal to the site repeater no need for the
high speed oscillator in the QUANTAR site repeater.
5-18 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System LED Description
LED Description
Table 5-4 describes the LEDs located in the top row of the PSC 9600.
Table 5-4 PSC 9600 Top Row LEDs
Name Color State Function

Power Green On Power is on.
Off Power is off.
Active Green On Active Site Reference (Usually indicates the active site controller).
See Note Below.
Off Standby Site Reference (Usually indicates the standby site controller).
See Note Below.
Data Svc Green On Data service enabled
Off No data service
Blinking Establishing an RNG link
The Data Svc (data service) LED is only valid on the active site controller (ASC). The LED
will be off on the non-active site controller.
T1-1 Green On Locked
Off Disabled
Blinking Not locked
T1-2 Green Not used
St Wide Green On Wide area trunking
Off Site trunking or Failsoft
Blinking Site off
The St Wide (site/wide) trunking LED and ZC Link LED (see Table 5-5) are only valid if the site controller is
in an Enabled state. In a Disabled or Critical Malfunction state, the LEDs will be off. A site controller in one of
these states does not know the state of the site nor does it try to communicate with the zone controller. The
LEDs will be off.
If both the St Wide and St Loc LEDs are off, this indicates that the site controller is not functioning as an active
or standby site controller. The site controller is either coming up or in a Disabled or Critical Malfunction state.
St Loc Green On Site trunking
Off Wide area trunking or site off
Blinking Failsoft
6881009Y05-O April 2004 5-19

LED Description Chapter 5: Radio Frequency Subsystems
The Active LED always indicates the active site reference. The Active LED usually indicates
the active site controller (ASC), except for certain cases, as follows:
During an ACS rollover, the Active LED will not switch until the former ASC completes
its application reset and becomes the standby site controller
When both site controllers are disabled, one of the site controllers still needs to
drive the Site Reference and therefore, the Active LED will be lit. However, in
this case, neither site controller will be the ASC.
Table 5-5 describes the LEDs located in the bottom row of the PSC 9600.
Table 5-5 PSC 9600 LEDs Bottom Row
Name Color State Function

VLAN Yellow On VLAN is operating with more than one VLAN.
Off VLAN is operating in single VLAN mode.
Blinking VLAN detection/validation
SWDL Yellow On Software download activity
Off No software download activity
Blinking Version validation failure
The SWDL and VLAN LEDs will blink together to indicate a Version Validation failure.
Fault Red On Major fault
Off No faults
Blinking Minor fault
ZC Link Yellow On This is the active site controller and its link to the zone controller
is up.
Off This is the standby site controller.
Blinking Zone controller link is down.
The ZC Link LED and St Wide (site/wide) trunking LED are only valid if the site controller is in an Enabled
state. In a Disabled or Critical Malfunction state, the LEDs will be off. A site controller in one of these states
does not know the state of the site nor does it try to communicate with the zone controller. The LEDs will be off.
If both the St Wide and St Loc LEDs are off, this indicates that the site controller is not functioning as an active
or standby site controller. The site controller is either coming up or in a Disabled or Critical Malfunction state.
5-20 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Rear Connectors
There are three unlabeled, red LEDs in the bottom row that have no function in the PSC 9600.
These LEDs remain in the off state during normal operation.
Rear Connectors
Figure 5-10 shows the PSC 9600 backplane.
Figure 5-10 PSC 9600 - Rear View
Table 5-6 provides a list of the connectors on the PSC 9600.
Table 5-6 PSC 9600 Rear Connectors
Name Purpose Quantity

Power 48 VDC (optional 110 VAC) For additional 1
information on component power supplies,
see Appendix A, "Power Supply Reference."
Redundancy Link to redundant controller 1
Frequency Reference Site Ref Out Port Provides frequency 3 (middle port used)
reference to 700 MHz stations
10Base-2 Not used 1
10Base-T Connection to the site LAN 1
PSC 9600 Configuration Parameters
The PSC 9600 controller programming consists of two sets of parameters; device-owned
parameters and manager-owned parameters.
Device-owned parameters are programmed at the site controller using CSS and include:
ID of the site in which the device is configured (Site ID)
Numeric identifier for each channel (Channel ID)
Site controller name (Controller Name)
Site controller number (Controller Number)
Site controller IP address (Controller IP Address)
6881009Y05-O April 2004 5-21

Infrastructure Time of Day Synchronization ASTRO 25 Repeater Sites Chapter 5: Radio Frequency Subsystems
Device-owned parameters are not overwritten by values from the Zone Database Manager.
Manager-owned parameters are programmed at the Zone Database Manager and downloaded to the site
controller when the link is established between the site controller and the zone controller. Manager-owned
parameters can be programmed or changed locally at the site controller, using CSS, but the values are
overwritten by the zone database values once the link is established to the zone controller.
The manager-owned parameters are marked with an asterisk (*) at the site controller.
All site parameters can be programmed locally when the site is installed but not yet linked
to the zone controller. The ability to program locally provides the means to test the site
prior to making it available for system operation.
Whenever possible, manager-owned parameters should be configured through ZCM or UCM.
Infrastructure Time of Day Synchronization

ASTRO 25 Repeater Sites

Infrastructure Time of Day is an automatic function used to maintain a common time across the
system. A common time makes it possible to associate log files from different devices across the
system by time stamping faults as they occur and providing a method to simultaneously update
operational parameters in critical devices. Time is synchronized through the Network Time Protocol
(NTP). Most NTP clients have a primary and secondary NTP source.
For ASTRO 25 Repeater sites, the active PSC 9600 serves two functions:
It acts as the NTP client for the site. The PSC 9600 uses the TRAK 9100 at the zone master site
as the primary NTP source and the Zone Database Server (ZDS) as the secondary NTP source.
It serves as the primary NTP source for devices at the site. The PSC 9600 polls the
NTP server at the zone master site for NTP server time of day updates.
The active PSC 9600 broadcasts time updates every 64 seconds. The idle PSC 9600 and ASTRO
25 Site Repeaters use the NTP source time to verify correct time setting. If the internal time
variance in a device is equal to, or greater than 500 ms from the NTP source time, the device
corrects the NTP Time of Day clock to match the received NTP time.
5-22 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Site Reference ASTRO 25 Repeater Sites
Site Reference ASTRO 25 Repeater Sites

A site reference signal (or frequency reference signal) is a highly accurate 5 MHz output signal
generated from a high stability oscillator. This site reference signal is used by an ASTRO 25 Site
Repeater to generate a highly stable carrier frequency. The source of the site reference signal may
be different based on the type of ASTRO 25 Site Repeater installed at the site.
QUANTAR ASTRO 25 Site Repeater: Uses an internal site reference signal

from the QUANTAR, or external site reference signal from the PSC 9600 site
controllers Ultra High Stability Oscillator (UHSO)
STR 3000 ASTRO 25 Site Repeater (700 MHz): Uses an external site reference
signal from the PSC 9600 site controllers UHSO.
If the PSC 9600 site controller provides a frequency reference signal to the site repeater,
the high speed oscillator in the QUANTAR site repeater is not needed.
Site Ethernet Switch

Figure 5-11 and Figure 5-12 show the HP 2524 and HP 2626 10/100Base-T LAN Ethernet switches,
respectively. Either switch can provide the required LAN interface the ASTRO 25 Repeater site
equipment. Both site controllers, the site router, and the repeaters are connected to the switch in a single
switch subsystem configuration. In a subsystem with two switches, each of the two site controllers
is connected to one of the switches. The ASTRO 25 Site Repeaters are connected to the switches
in an odd-even configuration scheme; all odd repeaters are connected to one Ethernet switch while
all even repeaters are connected to the second Ethernet switch. If the subsystem is configured with
four control channels, one and three are connected to the odd-numbered channels switch, and control
channels two and four are connected to the even-numbered channels switch.
Each switch provides 24 ports that support connectivity for a 10/100Base-T LAN. The HP 2524
switches are connected to each other through a Gigabit stacking interface that makes it possible for
either controller to communicate with up to 28 ASTRO 25 Site Repeaters. The HP 2626 switches are
connected to each other using one of the Ethernet ports. If one switch fails, at least one controller
has connectivity to maintain the site in a trunked mode with half the subsystem resources. The
LAN switches send SNMP traps back to the Network Management system.
6881009Y05-O April 2004 5-23

Site Ethernet Switch Chapter 5: Radio Frequency Subsystems
Figure 5-11 HP 2524 Prime Site Ethernet Switch
Figure 5-12 HP 2626 Prime Site Ethernet Switch
The HP Procurve switches support the following features:

24 auto-sensing 10/100Base-TX RJ-45 ports with Auto MDI/MDI-X.
HP Auto-MDIX on all 10/100 twisted-pair ports, and IEEE 802.3ab Auto MDI
/MDI-X on all 100/1000 twisted-pair ports, meaning that all connections can be
made using straight-through twisted-pair cables.
Two slots for installing supported gigabit transceivers.
All ports are enabled. Connect the network cables to active network devices
and the switched network is operational.
The pin operation of each port is automatically adjusted for the attached device: if the
switch detects that another switch or hub is connected to the port, it configures the port as
MDI; if the switch detects that an end-node device is connected to the port, it configures the
port as MDI-X. Crossover cables are not required, although they also work.
Automatic learning of the network addresses in each switchs 4096 address forwarding
table. As devices are connected to the switch ports, either directly or through hubs or other
switches, the MAC addresses of those devices are learned automatically and stored in the
4096-entry address table. The switches also identify the number of the port on which each
address is learned so they know the network location of each connected device.
Automatically negotiated full-duplex operation for the fixed 10/100 RJ-45 ports when
connected to other auto-negotiating devices. The transceiver ports always operate at full duplex.
Switch management through several available interfaces:
Web browser interface: A built-in graphical interface that can be
accessed from common web browsers.
Console interface: A VT-100 terminal interface that can be used for out-of-band
switch management or for Telnet access to the switch.
HP TopTools for hubs & switches: An SNMP-based, graphical network
management tool that can be used to manage your entire network. This
product is included with a new switch.
Support for the Spanning Tree Protocol: This interface eliminates network loops.
5-24 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Reset Button
Reset Button
This button clears any temporary error conditions that have occurred and executes the switch
self test. The Reset button may also be pressed after installing any optional transceivers
to initialize the transceiver and make it operational.
Resetting the switch also resets all network activity counters to zero. The counters
appear in the switch console interface, the web browser interface, and through
SNMP network management applications.
Clear Button
This button is used for two purposes:

Deleting Passwords When pressed by itself for at least one second, the button deletes
any switch console access passwords that you may have configured. This feature may be
used when the password has been misplaced and console access is needed.
Restoring Factory Default Configuration When pressed in combination with the Reset
button in a specific pattern, any configuration changes that may have made through the switch
console, the web browser interface, and SNMP management are removed, including the IP
address, if one is configured. The factory default configuration is then restored to the switch.
The presence of the clear button means that if you are concerned with the security of
the switch configuration and operation, you should make sure the switch is installed
in a secure location, such as a locked wiring closet.
Power Connector
The Ethernet switch does not have a power switch; it is powered on when connected to
an active AC power source. The switch automatically adjusts to any voltage between
100-127 and 200-240 volts and either 50 or 60 Hz.
Mode LED Select Button and Indicator LEDs
To optimize the amount of information that appears for each of the switch ports, the switch uses a Mode LED
for each port. The operation of this LED is controlled by the Mode LED Select button, and the current setting
is indicated by the Mode LED Select indicator LEDs near the button. The Mode LED Select button is pressed
to step from one mode to the next. Figure 5-13 shows the location of the button in relation to the indicators.
6881009Y05-O April 2004 5-25

Console Port Chapter 5: Radio Frequency Subsystems
Figure 5-13 LED Select Button and Indicator LEDs HP 2524
Table 5-7 provides a list of the LEDs on the HP 2524 LAN switch.
Table 5-7 Mode LED Indicator LEDs HP 2524
When the following is

Then
illuminated
Activity (Act) indicator Each Mode LED displays activity information for the
associated port. It flickers as network traffic is received
and transmitted through the port.
Full Duplex (FDx) indicator LED Mode LEDs illuminate for those ports that are operating
in full duplex.
Maximum speed (Max) indicator Mode LEDs illuminate for those ports that are operating
LED at their maximum possible link speed: 100 Mbps for
10/100 ports and 100-FX fiber optic ports, and 1000
Mbps for 100/1000Base-T or gigabit fiber optic ports.
Attention (!) indicator LED Each Mode LED illuminates briefly for each network
event that could require operator attention, for example,
late collisions or CRC errors.
Console Port
The console port is used to connect a console to the switch with the serial cable supplied with the switch.
The console can be a PC or workstation running a VT-100 terminal emulator, or a VT-100 terminal.
The console interface is also accessible through a Telnet connection.
LED Indicators and Buttons HP 2626
The following list provides a brief description of the LEDs on the HP 2626 Procurve Switch:
5-26 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System LED Indicators and Buttons HP 2626
Switch Status LEDs Four switch status LEDs to indicate the status of
the switch. These include the following:
Power LED reports whether or not the switch is receiving power.
Fault LED reports the fault condition of the switch.
Self Test LED reports whether or not the switch is operating in a self-test condition.
Fan Status LED reports the operating status of the fan.
Port Mode LEDs Four LEDs to indicate the mode of the port indicated by
the Port Indicator LED. These include the following:
Link LED Indicates that the Port Indicator LEDs are in the Link reporting
mode to report on the link or connection status of a port.
Act LED Indicates that the Port Indicator LEDs are in the network Activity
reporting mode to report network activity for a port.
FDx LED Indicates that the Port Indicator LEDs are in the Full Duplex
reporting mode to report which ports are in full duplex mode.
Spd LED Indicates that the Port Indicator LEDs are in the Speed reporting
mode to report the operation speed for a port.
Port Indicator LEDs Indicate the port on the switch being reported to the Port Mode
LEDs. There is one Port Indicator LED for each port on the switch. Each Port Indicator LED
displays port link information, network activity information, whether the port is configured for
full-duplex operation, or the speed of the connection depending on the Port Mode LED selected.
The Port LED View select button to the left of the Port Mode LEDs is used to select one of
the Port Modes to be reported by ports on the switch.
Figure 5-14 HP 2626 Ethernet Switch LEDs
6881009Y05-O April 2004 5-27

LED Indicators and Buttons HP 2626 Chapter 5: Radio Frequency Subsystems
Table 5-8 and Table 5-9 provide the operation status descriptions for LED indicators
on the HP 2626 Procurve switch.
Table 5-8 HP 2626 Switch Status LED Descriptions
Switch Status LED State Description

Power Green: On The switch is receiving power.
Green: Off The switch is not receiving power.
Fault Orange: Off Normal state: No fault conditions.
Orange: Blinking Operational fault has occurred on a port or fan. If a port has
failed, the Port LED will also blink.
Orange: On On briefly after the switch is powered up or reset or at the
beginning of the self test. On for a prolonged time indicates a
hardware or self test failure.
Self Test Green: Off Normal state: no self test being conducted.
Green: On Self test and initialization is in progress. The switch is not
operational in this mode.
Green: Blinking A switch component or port has failed the self test. Port LED
and Fault LED will blink.
Fan Status Green: On Normal state: cooling fan is operating normally.
Green: Blinking Cooling fan operation has failed. Fault LED will also blink.
Table 5-9 HP 2626 Switch Port Mode LED Descriptions
Port Mode LED State Description

Link Green Indicates the Port Indicator LEDs are reporting Link information:
Port Indicator LED On: The port is enabled and is receiving a likn
indication from the connected device.
Port Indicator LED is Off: The port has no active network cable
connected, is not receiving a signal, or has been disabled..
Port Indicator LED is Blinking (together with a blinking Fault LED):
The port has failed the self test.
Act Green Indicates the Port Indicator LEDs are reporting network activity.
FDx Green Indicates the Port Indicator LEDs are illuminated for ports that are in
full-duplex mode.
Spd Green Indicates the Port Indicator LEDs are reporting the connection speed:
LED Off: Port operating at 10 Mbps

LED Flashing: Port operating at 100 Mbps
LED On, continuous: Port operating at 1000 Mbps
With power supplied to the switch, the reset button will clear any temporary error
conditions and will execute a self-test.
5-28 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Reset and Clear Button HP 2626 Switch
Reset and Clear Button HP 2626 Switch

With power supplied to the switch, use the reset button to clear any temporary error condition.
When the reset button is pressed, the switch executes a self-test.
Before using the reset and clear buttons, make sure you have a backup of the switch
configuration so that the switch configuration can be restored, if necessary.
The clear button is used for the following:
Delete Passwords: When pressing this button by itself for at least one second, the switch
console access passwords you may have configured are deleted. Use the clear button in this
way if misplace or forget the password and need console access to the switch.
Restore Factory Default Configuration: Using the reset and clear buttons, you can
restore the switch to factory default settings. Using these buttons for this function will clear
passwords, clear the console event log, reset the network counters to zero, perform a self test,
delete the IP address and reboot the switch. To do this, simultaneously press the reset and clear
buttons until the power and fault lights turn on. Then, continue to hold in the clear button while
you release the reset button. When the self-test LED begins to blink, release the clear button.
Site Router S2500

The site router integrates voice and data traffic over a single converged network, compressing
and routing voice calls between devices directly connected to the switch or between
telephones or PBXs through an IP data network.
The site router provides a WAN interface that handles all of the traffic to and from the
master site for the RF site including voice, control, data, and network management traffic.
The site routers provide the following functions:
Media conversion The router converts the 10MB Ethernet LAN packets to IP packets
encapsulated in Frame Relay on a FlexWAN connector or cable.
Traffic prioritizing The router applies the correct prioritizing masking
to the packets leaving the site.
Fragmentation The router fragments large IP packets per standards.
Dynamic Host Configuration Protocol (DHCP) service This service allows a technician
with a properly configuration Windows PC to connect to the LAN at the site.
6881009Y05-O April 2004 5-29

S2500 Site Router Front Panel Chapter 5: Radio Frequency Subsystems
At an ASTRO 25 Repeater site, the site router is used to provide connectivity between the subsystem
LAN and the master site zone controller, zone manager, FullVision INM and MOSCAD Network
Management servers. At an ASTRO 25 Repeater site with mutual aid, the site router connects
directly to the TeNSr channel bank HSU card through the FlexWAN/V.3. The mutual aid station
is interfaced to the channel bank through a 4-wire analog card.
Figure 5-15 Motorola Network Router S2500 Site Router
The site router used at an ASTRO 25 Repeater site is the same site router used in an IntelliRepeater
Site. For other details on the IntelliRepeater site, see "IntelliRepeater Site" on page 5-32.
S2500 Site Router Front Panel
The front panel of the site router features the following components:
Service Interfaces Supports one Ethernet interface, provides for a WAN/Telco module in
I/O Slot A (a T1/E1 module is shown in I/O Slot A), and provides a FlexWAN serial interface
module in I/O Slot B. Some modules may vary, based on the hardware configuration specified.
Console port Used to connect the site router to a PC, terminal, or modem.
LED Indicators LEDs indicate the router interface and system status information.
5-30 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System S2500 Site Router LED Indicators
S2500 Site Router LED Indicators
Table 5-10 provides a descriptive list of the LED indicators on a S2500 site router.
Table 5-10 Interfaces Supported by the Site Router
LED Type LED Description

LAN 100 Mb Lights green when 100Base-T Ethernet is in use.
Link Lights green when the path is up.
Active Flashes green when a packet is detected.
Fault Lights amber when an error is detected or the
self-test has failed.
T1/E1 Module Link Lights green when the path is up.
FlexWAN Link Lights green when the path is up.
System Run Lights green when the software has successfully
loaded and is running.
Load Unlit in normal operation. Flashes green during
startup to indicate system is loading software.
Lights solid green when there is a load problem.
Test Unlit in normal operation. Lights amber during
startup to indicate system is running self-tests.
Fwd Flashes green each time a packet is forwarded
between ports.
Power/Fault Lights green when unit has power. Lights amber
if there is a problem with power. When unlit,
power to the unit is off.
Status Status Provides additional status for the Run, Load,
and Test LEDs.
S2500 Site Router Rear Panel
The rear panel of the S2500 site router includes the following:
Power receptacle
Configuration label
Grounding screw
6881009Y05-O April 2004 5-31

Site Router Supported Interfaces Chapter 5: Radio Frequency Subsystems
For more information on component power supplies, see Appendix A, "Power Supply Reference."
Site Router Supported Interfaces
Table 5-11 lists the interfaces supported by the site router in an ASTRO 25 system.
Table 5-11 Interfaces Supported by the Site Router
Number of
Interface Description
Ports
LAN (Ethernet) 1 port (built-in) LAN ports that provide connection to Ethernet
LANs using either 10Base-T or 100Base-TX
Ethernet.
T1/E1 1 port per module T1/E1 port handles master site to remote site
interface.
FlexWAN Serial 1 port per module High-speed multifunction serial interfaces
that provide connection to industry-standard
V.35, RS-232, RS-449, RS-530, or X.21 Data
Communications Equipment (DCE) or Data
Terminal Equipment (DTE) serial devices.
FlexWAN port handles master site to channel bank
at a remote site supporting mutual aid.
IntelliRepeater Site

An IntelliRepeater is a trunked QUANTAR repeater capable of performing the trunking functions

of a site controller. IntelliRepeaters may be configured for a control channel or for voice channels;
up to four IntelliRepeaters per site can be designated as control channels.
One IntelliRepeater at an IntelliRepeater site serves as the site controller, known as the active Master
IntelliRepeater (MI). The MI relays call control information between the rest of the IntelliRepeaters at the
site and the zone controller. It also manages all site functions and call processing when the site is in site
trunking mode. All IntelliRepeaters are programmed with the active master function and a set of rules that
determines which one assumes the role initially and whenever the current site active MI fails. Communication
between all IntelliRepeaters at a site takes place through a dedicated local area network (LAN).
5-32 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Component Diagram
The site data link from the zone controller is a logical link, processed by the router, that provides the connection
between the site IntelliRepeater LAN and the transport network. If this link fails, the site enters site trunking
mode, and the active master IntelliRepeater provides call processing for the site. If the master IntelliRepeater
itself fails, another IntelliRepeater automatically takes control of the site. Failsoft mode of operation at an
IntelliRepeater site can take place only when all but one of the IntelliRepeaters at the site have failed.
The radio frequency distribution system at an IntelliRepeater site consists of the equipment, including
antennas, necessary to interface the IntelliRepeaters with the subscribers.
The network infrastructure at an IntelliRepeater site includes a site router and a site hub with a 10Base-2
interface. A channel bank is added if mutual aid is required at the site.
Component Diagram
IntelliRepeater sites (Figure 5-16), together with the ASTRO 25 Repeater site, are the
only single site solution in ASTRO 25 systems.
Figure 5-16 IntelliRepeater Site
IntelliRepeater sites are supported in this release as legacy equipment. The system can be
expanded only with ASTRO 25 Repeater sites or digital simulcast subsystems.
An IntelliRepeater site consists of the following main components:
QUANTAR IntelliRepeater
PS40 hub
Site router
6881009Y05-O April 2004 5-33

QUANTAR IntelliRepeater Chapter 5: Radio Frequency Subsystems
QUANTAR IntelliRepeater
The Motorola QUANTAR IntelliRepeaters provide a modular, flexible design that allows for
upgrades within systems through hardware and/or software to avoid total infrastructure replacement.
An IntelliRepeater is equipped with the computer capability that allows it to perform the trunking
functions of a site controller, control channel, or voice channel. The IntelliRepeater can perform site
controller/control channel or site controller/voice channel functions simultaneously.
Figure 5-17 QUANTAR IntelliRepeater, 800 MHz Receiver - Front View
Receiver Module
The Receiver Module provides the receiver functions for the QUANTAR station. Each receiver module
includes a Preselector Filter Assembly and a Receiver board, contained by a slide-in module housing.
The receiver module performs highly selective bandpass filtering and dual down conversion of the station
receive RF signal. A custom receiver integrated circuit then performs an analog-to-digital conversion
of the received signal and outputs a differential data signal to the Station Control Module.
Station Control Module

The Station Control Module (SCM) serves as the main controller for the station. The SCM board contains a
microprocessor, a digital signal processor, an Ethernet interface, and support circuitry which combine to
provide signal processing and operational control over the other station modules. The SCM also contains the
station operating software (stored in FLASH memory) and codeplug, which define the personality of the
station, including system capabilities and operating parameters, such as output power and operating frequency.
5-34 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Transmitter
The Ethernet interface provides the IntelliRepeaters with the mechanism to take the ASTRO audio, after
processing by the receiver and DSP circuitry, as its input and provide audio as packets at its output that
are ready for transmission over the IP-based network. The Ethernet interface sends these audio packets
through the IntelliRepeater LAN, the site hub, and router to the master site for distribution.
Audio that is received from the master site for transmission to subscribers is also processed by the
Ethernet interface. The ASTRO audio is recovered from the audio IP packets and is delivered to the
DSP and transmission circuitry to be processed for transmission to the subscribers.
The Ethernet interface also provides the connectivity between the IntelliRepeater and the LAN. Two
types of information flow across the LAN to/from the IntelliRepeaters:
Control information that carries site information, channel assignments, and
identification numbers for call processing
Audio encapsulated as Ethernet packets
Transmitter
The Power Amplifier module together with the Exciter board provide the transmitter function
for the QUANTAR IntelliRepeater. Contained within a slide-in module housing, the Exciter
board generates a low-level, modulated RF signal, which is sent to the power amplifier module
for further amplification and output to the transmit antenna.
PS40 Hub
The PS40 hub performs three main functions at the IntelliRepeater site:
Serves as the interface between the IntelliRepeater sites 10Base-2 LAN
and the site routers 10Base-T port.
Provides a port to interface with MOSCAD.
Provides the service technicians with the means to access the system GUIs maintain
the system or, using CSS software, to service the site.
Site Router
The site router for the IntelliRepeater site integrates voice and data traffic over a single converged network,
compressing and routing voice calls between devices directly connected to the switch or between telephones
or PBXs through an IP data network. The site router provides a WAN interface to handle traffic to and
from the zone for the RF site including voice, control, data, and network management traffic.
The Site Router used at an IntelliRepeater site is the same site router used for the ASTRO
25 Repeater Site. For details, see "Site Router S2500" on page 5-29.
6881009Y05-O April 2004 5-35

IntelliRepeater Subsystem Operational Modes Chapter 5: Radio Frequency Subsystems
IntelliRepeater Subsystem Operational Modes
The operational modes for an IntelliRepeater subsystem are:

Wide Area Trunking
An IntelliRepeater subsystem can remain in wide area trunking as long as
the following resources are available:
Two IntelliRepeaters. One of the IntelliRepeaters can operate as the site controller and
voice channel while the other IntelliRepeater operates as the control channel.
The site router
Connectivity through the hub
The IntelliRepeater LAN
A logical path between the site router and the master site IP equipment
Site Trunking
Site trunking operation takes place when there is no physical or logical link between the site
router(s) and the master site. Conditions required to maintain site trunking include:
Two IntelliRepeaters. One of the IntelliRepeaters can operate as the site controller and
voice channel while the other IntelliRepeater operates as the control channel.
The IntelliRepeater LAN.
Site trunking can also be initiated from the diagnostic capability of the ZCM.
Failsoft
Failsoft mode of operation at an IntelliRepeater subsystem takes place only when there are
no operational control channel capable base stations or all voice channels are inoperative.
Failsoft can also be initiated from the diagnostic capability of the ZCM.
Digital Simulcast Subsystems

The digital simulcast subsystem for ASTRO 25 is a radio system employing multiple transmitters on
a single frequency in separate locations. A digital simulcast subsystem is designed to simultaneously
transmit information on one frequency throughout the entire subsystem from a base radio at each remote
site. GPS input is used to synchronize these transmissions. The digital simulcast subsystem allows
for improved portable communication coverage in dense, urban environments and provides a solution
for covering large populated areas where limited frequencies are available.
5-36 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Digital Simulcast Subsystem Infrastructure
The system treats each digital simulcast subsystem as a single site.
Digital Simulcast Subsystem Infrastructure
The digital simulcast subsystem consist of a prime site and at least two simulcast remote sites; up
to 15 remote subsites and 30 voice channels per subsite are supported.
The remote subsites can be 15 physically separate sites or 14 physically separate sites with
one colocated at the prime site. A remote subsite installed in the same physical location as the
prime site is known as a prime site with colocated remote site.
Digital Simulcast Subsystem Communication and Interface

Links
The ASTRO-TAC 9600 comparators at the simulcast prime site encapsulate the V.24 audio into
Ethernet packets which are then sent to a router for encapsulation as Frame Relay packets. A T1
link is used to transport the Frame Relay packets containing voice, site control information, and
network management information between the prime site and the master site.
Communication between the simulcast prime site and simulcast remote sites takes place as follows:
V.24 links between the base stations and the ASTRO-TAC comparators
for voice and control information.
Ethernet link for network management.
The following frequency bands are supported in the digital simulcast subsystem:
700 MHz
800 MHz
UHF
VHF
Digital Simulcast Subsystem Network Topology
The network topology for the digital simulcast subsystem can be divided into the following categories:
Simulcast voice network
Simulcast trunking control
Simulcast network management
Simulcast site reference
6881009Y05-O April 2004 5-37

Digital Simulcast Subsystem Network Topology Chapter 5: Radio Frequency Subsystems
The voice channel links interface directly to the comparator for audio routing to the simulcast remote subsites
in the form of V.24 links. Every voice channel and simulcast remote subsite has a V.24 link.
The ASTRO 25 comparator collects all of the data for a single channel from all of the subsites. The
comparator selects the best received ASTRO frames from all its inputs and routes a single data stream
to the master site core router. In the reverse direction, the comparator forwards outbound audio from
the master site core router to the base radios at the simulcast remote sites.
The ASTRO 25 comparator supports digital system operation as part of an ASTRO 25 digital simulcast
subsystem. Analog or mixed-mode (analog and digital) operation is not supported. The voted ASTRO
audio from the comparator is sent to the master site router as IP packets, where they are routed to all the
required sites as well as the MGEG if the call involves the consoles or telephone interconnect.
Simulcast operation requires a 1 pulse-per-second (pps) input and a 5 Mpps reference to the ASTRO-TAC
9600 comparator from a GPS site reference to synchronize the launch times. All stations at the remote sites
use a composite signal, consisting of 1 pps embedded in a 5 Mpps signal, as a site reference. All required
software for controlling launch times is included in the standard ASTRO-TAC 9600 software package.
The site control path from the simulcast prime site is connected to the prime site LAN. In addition, the
site controllers and the comparators also reside on the prime site LAN. The simulcast prime site routes
call processing traffic between the zone controller and the simulcast site controller. Unlike past simulcast
configurations, there are no separate data links to the simulcast remote site. The trunking control link to the
simulcast remote site uses the V.24 link of the voice channel that is acting as the control channel.
The simulcast prime site controller acts as the control interface between the digital simulcast subsystem and
the zone controller. The simulcast prime site controller supervises the digital simulcast subsystem resources.
The standard installation uses two simulcast prime site controllers in a redundant configuration. The network
management link from the simulcast prime site network system is connected to the prime site LAN to
establish network management between the master site and the digital simulcast subsystem.
Network management between the simulcast prime site and the simulcast remote sites is established through
the simulcast prime site network. The simulcast prime site network creates multiple connections to the
simulcast remote sites (one connection per site). These are point-to-point connections.
The simulcast site reference (SSR) supplies a highly accurate time and frequency reference signal
to the comparator. The comparator uses the time reference to compute transmission launch times
and uses the frequency reference to generate the data transmission clock. The SSR is configured
with redundant power supplies, GPS receivers, and oscillators.
Simulcast subsystems support two types of LANs at the prime site and remote subsites, a 10/100Base-T
LAN or a 10Base-2 LAN. The 10/100Base-T LAN is supplied with all new simulcast subsystems or
when additional subsites are added to an existing simulcast subsystem. Simulcast subsystems with
10Base-2 LANs are supported in the current release only as legacy equipment.
The LAN at a prime site, or subsite, must consist of all 10/100Base-T or all
10Base-2 equipment. Equipment with these two different LAN interfaces cannot
be mixed at the same prime site or subsite.
For a description of the digital simulcast subsystem prime site with 10/100Base-T LANs
see "Simulcast Prime Site" on page 5-40 and for the remote sites, see "Simulcast Sites"
on page 5-58. Differences between subsystems with 10/100Base-T and 10Base-2 LANs
are discussed in the"Digital Simulcast Subsystem 10Base-2" on page 5-81.
5-38 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Digital Simulcast Subsystem Modes of Operation
Digital Simulcast Subsystem Modes of Operation
The operational modes of a digital simulcast subsystem include the following:
Wide Area Trunking

Site Trunking
Failsoft
Site Off
Wide Area Trunking Simulcast Subsystem: A simulcast subsystem remains in wide area trunking
as long as the following resources are available and functioning properly:
The site control path (transport link, zone controller, control router, LAN and
WAN switches and core router at the master site)
One site router
One prime site controller
One site switch
At least one voice channel and associated comparator
At least one control channel
The site control path includes the any transport link between the subsystem and master
site, as well as zone controller, control router, WAN and LAN switch, and core router
equipment. A functioning site control path results from good communications between
the prime site controller, comparator, and remote site.
Site Trunking Simulcast Subsystem: When a simulcast or STRV subsystem (voting subsystem) loses
the site control path (due to a failure in the transport link or site control path equipment) and the subsystem
continues to provide trunked operations, the subsystem is in site trunking mode. In site trunking mode, radios
can continue to communicate with members of their talk group that are also registered at the site. The
following resources must be available and functioning properly to support site trunking mode:
One prime site controller

One site switch
At least one voice channel and associated comparator
At least one control channel
Communication outside the subsystem, communication with console operators, and centralized
6881009Y05-O April 2004 5-39

Simulcast Prime Site Chapter 5: Radio Frequency Subsystems
telephone interconnect is not available when the subsystem is in site trunking mode.
Any remote site designated as an essential remote site must have the required resources to
provide trunking services. See "Essential Remote Sites" on page 5-69
Failsoft Simulcast Subsystem: If the simulcast subsystem cannot maintain wide area trunking or site
trunking, the subsystem enters the failsoft mode of operation. Failsoft mode occurs when the subsystem
controller is not functioning properly, when all control channels are disabled or malfunction, or when only
one channel is enabled. A wide area failsoft mode occurs in failsoft mode when the comparators are still
available and local failsoft mode occurs in failsoft mode when the comparators are not available.
If a malfunctioned remote site is an essential remote site, the digital simulcast

subsystem is placed in failsoft regardless of the health of the rest of the subsystem.
See "Essential Remote Sites" on page 5-69
Site Off Simulcast Subsystem: Site Off is a mode of operation that is initiated from the diagnostics
capability of the zone configuration manager (ZCM). In this state, the subsystem is not available to the radios.
Simulcast Prime Site

A prime site acts as a control and audio center for the digital simulcast subsystem. It interfaces with the
master site through the WAN infrastructure. From the prime site to each simulcast remote site, control
and audio use serial links from the comparators through channel banks. Only network management
traffic is routed over the IP network through the prime site to the remote sites.
Digital simulcast subsystems are usually described by referring to the number of channels and the number of
simulcast remote sites in the system. For example, a digital simulcast subsystem utilizing 10 RF channels
across five simulcast remote sites is referred to as a 5 site, 10 channel digital simulcast subsystem.
The simulcast prime site communicates with the simulcast remote sites over two separate data
links. Control channel data and voice traffic channel data are passed between the comparators
at the prime site and the base radios at the remote subsites using 9600 bps V.24 links. Network
management data is distributed to the simulcast remote sites over V.35 links.
The prime site controller and the ASTRO-TAC 9600 comparators perform all the tasks necessary
for the operation of the digital simulcast subsystem and therefore, remote site controllers are
not needed in an ASTRO 25 digital simulcast subsystem.
5-40 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Simulcast Prime Site
Two prime site configurations are supported:

Prime site without colocated remote site (Figure 5-18)
Prime site with colocated remote site (Figure 5-19)
Figure 5-18 Simulcast Prime Site Without Colocated Remote Site
6881009Y05-O April 2004 5-41

Simulcast Prime Site Chapter 5: Radio Frequency Subsystems
Figure 5-19 Simulcast Prime Site With Colocated Remote Site
For simulcast remote site information, see "Simulcast Remote Site" on page 5-58
At a simulcast prime site, a terminal server can be employed for out-of-band management. Out-of-band
management implementation at a simulcast prime site provides serial access to various prime site components.
Figure 5-20 illustrates the use of the terminal server at the simulcast prime site for out-of-band management.
5-42 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System MTC 9600 Simulcast Prime Site Controller
Figure 5-20 Terminal Server Out-of-Band Management at the Simulcast Prime Site
Out-of-band management is typically provided to the following simulcast prime site components:
Simulcast Prime Site Controller
Comparator
Channel Bank
Prime Site Router
LAN Switches
Site Reference
MTC 9600 Simulcast Prime Site Controller
Figure 5-21 shows the MTC 9600 simulcast site controller, which is designed for use in ASTRO 25
simulcast trunking systems that use a 9600 bps control channel. Simulcast trunking systems are often
deployed in high-density environments, such as major metropolitan areas where wide area coverage is
desired. The MTC 9600 controller provides call processing for individual simulcast remote sites and acts
as the link between the digital simulcast subsystem and the zone controller. The MTC 9600 controller
is capable of supporting up to 15 remote sites and up to 30 channels per remote site.
6881009Y05-O April 2004 5-43

Standard Features Chapter 5: Radio Frequency Subsystems
Figure 5-21 Prime Site Controller
The MTC 9600 simulcast site controller communicates with surrounding ASTRO 25
infrastructure elements, such as the STR 3000 base radio subsystem and the ASTRO-TAC
9600, which are designed to be Project 25 compliant.
Standard Features
Redundant MTC 9600 controllers are required for each digital simulcast subsystem. The MTC 9600
controller is shipped in redundant configuration and is only compatible with Motorola STR 3000 simulcast
base radios that operate on a 9600 bps control channel. Only digital voice operation is supported.
Configuration/Service Software (CSS) is used to configure and service the MTC 9600 controller.
The redundant (standby) controller automatically takes over site link and site control operations when the
active MTC 9600 has failed. Communications between the active and standby controllers are configured
through an Ethernet link. Channel status information is kept consistent between the active and standby site
controller to assure that accurate channel capability information will always be sent to the zone controller.
Diagnostics
5-44 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Control Module
The MTC 9600 controller has been designed with internal diagnostic tests that occur on power up and reset.
Diagnostic tests are available for the hard drive, control module, and power supply. If a problem occurs
during operation, it will be reported as an alarm. All alarms are stored in the Alarm Log, accessible with
CSS. The alarm log contains the name of the diagnostic test that failed and the time since the last power
up. Critical alarm conditions alarms are also reported directly to the Network Manager.
Control Module
A CompactPCI module and a transition card that are interconnected by the mid-backplane control the MTC
9600 controller. Although options are available for channel capacity, there is only one control module for
all channel configurations. Application software is installed on both controller units; however, during
software upgrade, the MTC 9600 controller supports software cross-load between the standby and active
units. The transition module contains an RS-232 connector for local access to the controller.
Power Supply
The standard MTC 9600 controller has been designed with a power supply, which operates over
a wide range of voltages (110/220 VAC) and frequencies (50-60 Hz) without any modifications
or jumper changes. The power supply is enclosed in a metal case with a self-contained,
thermostatically controlled cooling fan as illustrated in Figure 5-22.
Figure 5-22 MTC 9600 - Rear View
6881009Y05-O April 2004 5-45

Simulcast System Applications Network Management Chapter 5: Radio Frequency Subsystems
A DC power supply is also available for the MTC 9600. For more information on component
power supplies, see Appendix A, "Power Supply Reference."
Simulcast System Applications Network Management

The MTC 9600 controller provides device status, link status, and alarm messages directly to the network
manager through the Simple Network Management Protocol (SNMP) agents controller.
Flash Capability
The MTC 9600 controller has FLASHport capabilities that allow for easy installation of software.
The ASTRO-TAC 9600 Comparator
Figure 5-23 shows the ASTRO-TAC 9600 comparator, which is designed for use in ASTRO 25 simulcast
trunking systems that use a 9600 bps control channel. With multiple base stations operating on the same
frequency, it is possible for field radios to simultaneously hit multiple sites when transmitting. The
ASTRO-TAC 9600 comparator compares the various voice traffic signals and selects the best one or develops
a composite signal for simulcast broadcasting. With the composite signal and by simultaneously transmitting
an identical RF signal from multiple sites within the system, both coverage and signal quality are enhanced.
5-46 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System The ASTRO-TAC 9600 Comparator
Figure 5-23 ASTRO-TAC 9600 - Front View
In order for the transmitter signals to be launched at precisely the same time from all transmitters, Global
Positioning Satellite (GPS) site reference receivers are required to time synchronize all base stations and the
comparator. In a Motorola ASTRO 25 simulcast trunking system, the comparator receives an absolute time
reference from a local GPS receiver. Because the ASTRO-TAC 9600 comparator processes information in a
digital format, the launch time information is integrated into the digital bit stream. This launch time instructs
the stations to launch the transmission at the precise release time. With this capability integrated into the
comparator, expensive controlling and delaying equipment used in other simulcast systems is not required.
Along with the voting and launch time functionality for voice traffic, the ASTRO-TAC 9600 also assists
the ASTRO 25 simulcast prime site controller. The ASTRO-TAC 9600 has expanded capabilities to
vote Inbound Signaling Packets (ISPs) on the 9600 bps control channel. Additionally, the ASTRO-TAC
9600 comparator controls the sequencing of the trunking Outbound Signaling Packets (OSPs) on the
control channel as generated by the prime site controller. On the voice channel, the ASTRO-TAC
9600 comparator controls the sequencing of the embedded talkgroup and priority monitor commands.
Alternative routing during site trunking and Failsoft modes is also supported.
The ASTRO-TAC 9600 comparator is not a replacement for the ASTRO-TAC or

ASTRO-TAC 3000 comparators. It is intended to be used in ASTRO 25 trunked simulcast
subsystems and single transmitter receiver voting subsystems that use a 9600 bps control
channel and IMBE (CAI - Common Air Interface) vocoding.
6881009Y05-O April 2004 5-47

Control Module Chapter 5: Radio Frequency Subsystems
The ASTRO-TAC 9600 comparator is a band-independent device that acts as a digital simulcast subsystem
signal collector, voter, and distributor. In order to do these things, the comparator communicates with
surrounding Simulcast infrastructure elements, such as the STR 3000 radio subsystem, MTC 9600 site
controllers, site Ethernet switches, and site router. The method of signal selection is based upon a combination
of specific voting parameters, such as bit error rate (BER) and error correction coding (ECC). The
ASTRO-TAC 9600 comparator is capable of supporting from 2 to 16 synchronous serial input/output ports.
The ASTRO-TAC 9600 comparator features a digital voting methodology called Frame Diversity
Reception. As the ASTRO-TAC 9600 comparator receives the various signals, it looks at each of the
data frames and compares the BER and ECC. The comparator then selects the data frame or signal
with the lowest BER and ECC and resends it. By using the best pieces (data frames) of each input
signal, the result is often a better output signal than any one signal being received at the comparator.
Signals destined for the master site are routed as voice on IP packets.
The entire ASTRO-TAC 9600 comparator is housed in a card cage that is divided into 13 slots (module units)
where modules can be inserted. The modules plug into a backplane, which routes the signals between
modules and also provides external connections to the comparator. The backplane is shielded to provide
added protection for the backplane connectors against RF interference. Gold card-edge connectors, designed
for blind insertion, are used to ensure reliable connectivity between the modules and the backplane.
A flexible bus structure is used between the control and wireline modules in the comparator. Control processors
on the modules communicate over a high-speed (11.5 MB/s) High-level Data Link Control (HDLC) packet
bus. A standard Serial Peripheral interface (SPI) bus is used to communicate to the power supply.
The comparator is designed to be front-side serviceable. All modules and boards can be removed
from the front without requiring access to the rear of the unit.
Control Module
The ASTRO-TAC 9600 contains an EPIC Control Module. This module uses a 33 MHz 68EC040
microprocessor in conjunction (through companion mode) with a 25 MHz 68360 microprocessor to provide
functions such as voting of ASTRO digital signals, audio routing control, input/output priority schemes, and
support for external digital interfaces such as the Ethernet port and an RS -232 port. The module also supports
a 56002 Digital Signal Processor (DSP) to accept a 1-pulse-per-second (pps) synchronizing signal and to
provide launch times for simulcast operation. The EPIC control module uses one slot (module unit).
The Ethernet interface provides the ASTRO-TAC with the mechanism to take the ASTRO audio, sent by the
various base station receivers connected to the wireline interfaces, as its inputs and provides audio packets at
its output that are ready for transmission over the IP based network. The Ethernet interface sends these audio
packets through the prime site LAN, the site switches, and router to the master site for distribution.
Audio that is received from the master site for transmission to subscribers is also processed by the Ethernet
interface. The ASTRO audio is recovered from the audio IP packets and are delivered to the DSP and
wireline circuitry to be processed for transmission to the base stations and subscribers.
The Ethernet interface also provides the connectivity between the ASTRO-TACs, the
Ethernet switches at the prime site, and the prime site controllers. Two types of information
flow across the LAN to/from the ASTRO-TACs:
Inbound Signaling Packets (ISPs), channel assignment information, wireline link status,
comparator diagnostic information, and remote site station diagnostic information.
Audio encapsulated as Ethernet packets. These audio packets are only routed
to the ASTRO-TACs, never to the controller.
5-48 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Wireline Module
Wireline Module
The wireline modules serve as the interface between the comparator and the base stations in the ASTRO 25
digital simulcast subsystem. The number of wireline boards is dependent upon the number of input/output
(I/O) ports required. For example, if a six-I/O comparator is ordered, three wireline boards will ship
with the comparator. Each wireline module takes up one slot within the comparator chassis. However,
the first wireline module and the control module share a common two-slot front panel.
A 5-Volt expansion power supply is necessary in Comparators equipped with 11 or more I/O
ports. This power supply is included as part of the 12, 14, and 16 I/O port options (X228-X230).
Audio and control information is sent to the base stations over the wireline link through V.24 boards.
Each wireline module accommodates one V.24 satellite board (which supports both input/output
ports of the wireline module). The V.24 boards are required to provide the audio and control links
between the ASTRO 25 Simulcast base stations and the comparators.
Power Supply
The standard ASTRO-TAC 9600 comparator was designed with a switching power supply, that operates
over a wide range of voltages (90280 VAC) and frequencies (4763 Hz) without any modifications or
jumper changes. The power supply is enclosed in a metal case with a self-contained, thermostatically
controlled cooling fan. The power supply takes up three slots in the card cage.
There are several optional power supplies available for the ASTRO-TAC 9600 comparator. The
power supply that is ordered with the comparator is determined by the type of input power that is
required (AC Power, Optional DC-Only, Optional Battery Revert). The DC-only power supply can be
driven from various voltage inputs (12/24 VDC or 48/60 VDC, depending on option ordered). It may
require a jumper to set the supply to match the voltage of the site battery.
The front panel of each power supply module includes an on/off switch and two LED indicators,
which are designed to easily show the functional status of the module.
Network Management
The ASTRO-TAC 9600 provides device and link status, diagnostics, and alarm messages
directly to the network manager through Simple Network Management Protocol (SNMP) agents
without having to pass information through a controller. Commands such as enable/disable can
also be sent to the comparator through the network manager.
Prime Site LAN Switch
10/100Base-T LAN switches are required to interface the prime site router to the ASTRO-TAC
9600 comparators. Two switches are used at the prime site, each of the two prime site controllers
is connected to one of the switches. The comparators are connected to the switches in an odd-even
configuration scheme; all odd comparators are connected to one HP 2524 Procurve Ethernet switch
while all even comparators are connected to the second Ethernet switch.
6881009Y05-O April 2004 5-49

Reset Button Chapter 5: Radio Frequency Subsystems
Each switch has 24 ports that provide connectivity for a 10/100Base-T LAN. The switches are connected to
each other through a Gigabit stacking interface that makes it possible for either controller to communicate
with up to 30 ASTRO-TACs. If one switch should fail, at least one controller will have connectivity
to maintain the site in a trunked mode with half the subsystem resources. The LAN switches send
SNMP traps back to the Network Management system for event notification purposes.
Figure 5-24 HP 2524 Procurve Prime Site Ethernet Switch
The HP Procurve switch supports the following features:
24 autosensing 10/100Base-TX RJ-45 ports with Auto MDI/MDI-X.

HP Auto-MDIX on all 10/100 twisted-pair ports, and IEEE 802.3ab Auto MDI
/MDI-X on all 100/1000 twisted-pair ports, meaning that all connections can be
made using straight-through twisted-pair cables.
Two slots for installing supported gigabit transceivers.
All ports are enabled. Connect the network cables to active network devices
and the switched network is operational.
The pin operation of each port is automatically adjusted for the attached device: if the switch
detects that another switch or hub is connected to the port, it configures the port as MDI; if
the switch detects that an end-node device is connected to the port, it configures the port
as MDI-X. Crossover cables are not required, although they will also work.
Automatic learning of the network addresses in each switchs 4096- address forwarding
table. As devices are connected to the switch ports, either directly or through hubs or other
switches, the MAC addresses of those devices are learned automatically and stored in the
4096-entry address table. The switches also identify the number of the port on which each
address is learned so they know the network location of each connected device.
Automatically negotiated full-duplex operation for the fixed 10/100 RJ-45 ports when
connected to other auto-negotiating devices. The transceiver ports always operate at full-duplex.
Switch management through several available interfaces:
Web browser interface
A built-in graphical interface that can be accessed from
common web browsers.
Console interface
a VT-100 terminal interface that can be used for
out-of-band switch management or for Telnet access to the switch.
Support for the Spanning Tree Protocol
Eliminates network loops.
Reset Button
This button clears any temporary error conditions that may have occurred and executes the
switch self test. The Reset button may also be pressed after installing any optional transceivers
to initialize the transceiver and make it operational.
5-50 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Clear Button
Resetting the switch also resets all network activity counters to zero. The counters
are displayed in the switch console interface, the web browser interface, and through
SNMP network management applications.
Clear Button
This button is used for two purposes:
Deleting Passwords When pressed by itself for at least one second, the button deletes
any switch console access passwords that you may have configured. This feature may be
used when the password has been misplaced and console access is needed.
Restoring Factory Default Configuration When pressed in combination with the Reset
button in a specific pattern, any configuration changes that may have been made through the
switch console, the web browser interface, and SNMP management are removed, including the
IP address, if one is configured. The factory default configuration is then restored to the switch.
The presence of the clear button means that you are concerned with the security of
the switch configuration and operation, you should make sure the switch is installed
in a secure location, such as a locked wiring closet.
Power Connector
The HP 2524 Ethernet switch does not have a power switch; it is powered on when connected
to an active AC power source. The switch automatically adjusts to any voltage between
100-127 and 200-240 volts and either 50 or 60 Hz.
Mode LED Select Button and Indicator LEDs

To optimize the amount of information that can be displayed for each of the switch ports, the switch uses a
Mode LED for each port. The operation of this LED is controlled by the Mode LED Select button, and the
current setting is indicated by the Mode LED Select indicator LEDs near the button. The Mode LED Select
button is pressed to step from one mode to the next. Figure 5-25 illustrates the location of the button and LEDs.
Figure 5-25 LED Select Button and Indicator LEDs
6881009Y05-O April 2004 5-51

Console Port Chapter 5: Radio Frequency Subsystems
When the Activity (Act) indicator LED is lit, each Mode LED displays activity information for the
associated port. It flickers as network traffic is received and transmitted through the port.
If the Full Duplex (FDx) indicator LED is lit, the Mode LEDs light for those ports
that are operating in full duplex.
If the maximum speed (Max) indicator LED is lit, the Mode LEDs light for those ports that are
operating at their maximum possible link speed: 100 Mbps for 10/100 ports and 100-FX fiber optic
ports, and 1000 Mbps for 100/1000Base-T or gigabit fiber optic ports.
If the attention (!) indicator LED is lit, each Mode LED lights briefly for each network event that
could require operator attention, for example, late collisions or CRC errors.
Console Port
The console port is used to connect a console to the switch with the serial cable supplied with the switch.
The console can be a PC or workstation running a VT-100 terminal emulator, or a VT-100 terminal.
The console interface is also accessible through a Telnet connection.
Prime Site Router
Figure 5-26 shows the prime site router, which provides a WAN interface to carry all of the
traffic for the RF site including voice, data, and network management traffic. The router provides
network connectivity for the remote sites, in addition to the following:
Media conversion The router converts the 10MB Ethernet LAN packets to IP packets
encapsulated in Frame Relay on a serial (UltraWAN) interface.
Traffic prioritizing The router applies the correct prioritizing marking
to the packets leaving the site.
Fragmentation The router fragments large IP packets per standards.
Dynamic Host Configuration protocol (DHCP) service This service allows the
technician with a properly configured Windows PC to connect to the LAN at the site.
Figure 5-26 Prime Site Router - Front View
5-52 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Channel Bank
The prime site router is based on the Motorola Network Router (MNR) S6000. A built-in Ethernet
port (LAN port) provides connectivity to the site Ethernet switch where both the primary site
controller and the backup site controller are accessible. The UltraWAN module (ST6010) provides
either a T1 or E1 interface to the TeNSr channel bank WAN card.
The prime site router facilitates network management activity at the site and provides a means of receiving
and reporting failure alarms. The Zone Manager, FullVision INM, and MOSCAD Network Management
servers have access to the simulcast prime site and remote sites through the prime site router.
Channel Bank
In a digital simulcast subsystem, the TeNSr is used to cross-connect bandwidth from 2

DS0s used for the Network Management Link into another WAN. This second WAN is
interfaced to the router at the simulcast prime site.
Figure 5-27 illustrates the prime site channel bank, which generally consists of the following cards:
Two cross-connect (XCON) CPUs
One single port WAN card for sites with 21 channels or less, a two port
card for sites with 22 channels or more
A channel service unit (CSU) card for each WAN T1 port in use
Dual power supplies
Interface card
V.24 cards (a 10-port, low delay sub rate unit (LDSRU) card; the number of
cards depends on the number of channels at the site)
A V.35 card (a high-speed unit (HSU) card)
4-Wire analog cards can also be installed when the system includes analog mutual
aid repeaters at the simulcast prime site.
6881009Y05-O April 2004 5-53

CPU Card Chapter 5: Radio Frequency Subsystems
Figure 5-27 Channel Bank - Front View
CPU Card
The CPU card controls all operations of the channel bank. One CPU card is required for all
installations. The CPU performs the following functions:
Initializes the channel bank upon power up, and runs a self-test on all cards
plugged into the chassis at that time.
Polls all cards in the channel bank every second to determine their operating status.
Processes all incoming operator commands and displays the responses in a series of
operator interface screens for each card in the channel bank. The operator interface system
(local VT-100 terminal, remote computer, or network management system) connects to the
Interface card, which sends these commands to the CPU card for processing.
Includes circuitry that allows you to cross-connect DS0 time slots between T1
lines connected to the system WAN cards.
Includes a test pattern generator for T1 test purposes.
Performs primary-secondary CPU arbitration. In a system with redundant CPU cards, the
two CPU cards communicate their status to each other. If the primary CPU card fails, the
redundant card takes control of the channel bank.
Wide Area Network Cards

Wide area network (WAN) cards manage the flow of data to and from the network. They are also the
point of T1 or E1 termination and generate or receive clocking. Both CSU and DSX modules are used
to connect to T1 facilities operating at 1.544 Mbps or E1 facilities operating at 2.048 Mbps.
The WAN cards at the prime site channel bank perform three primary functions:
5-54 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Interface Card
Receive the audio and control traffic from the remote sites and route it to the
LDSRU interfaces for delivery to the comparators.
Receive the audio and control information from the comparators, through the LDSRU
interfaces, and route the information to the transport network for delivery to the subsites.
Receive and transmit the network management traffic, through the HSSI card,
between the remote subsites and the prime site router.
Interface Card
The interface card (Figure 5-28) is always present, occupies the slot furthest to the left in
the rear of the channel bank, and controls many critical functions in the system. It provides
interfaces to external control devices, terminates all T1 and E1 WAN links, and holds the
nonvolatile RAM. The Interface card includes an internal modem.
The Interface card provides the means to select the clock source that is to be used by the channel bank. It
also provides a connector (sync port) for an external time reference such as the TRAK 9100.
Figure 5-28 Channel Bank - Rear View
Interface Card Ports and Functions
T1/E1 WAN Link Connector The WAN link connector allows you to connect
the WAN card ports to incoming and outgoing T1/E1 lines.
Computer Port The RS-232 port is used for direct reporting of alarms to an outside device.
Control Terminal (Term) Port The RS-232 control terminal interface
port allows you to connect the system to a VT100 compatible terminal, with
which you can send commands to the unit.
6881009Y05-O April 2004 5-55

Sub Rate Unit Card Chapter 5: Radio Frequency Subsystems
Node Port The RS485 node port allows you to activate external alarms to
alert the operator to critical situations. Using the ACO function will keep the
alarm active until manually cleared from the terminal.
Sync Port The Sync port is used to connect an external reference for T1 synchronization.
Modem Connector The modem port is used to connect the Interface cards internal dial
modem to a standard telephone line. This port may be used either to log into the unit from a
remote VT100 terminal or to send system alarms to a remote device. The internal modem is an
asynchronous CCITT V.22 bis modem. It allows remote access to the terminal interface and
automatic logging of alarm messages to a remote device. The modem communicates at 2.4
kbps using 8 data bits, one stop bit and no parity. As with a local terminal, the network operator
must dial in using a VT-100 compatible terminal. If an operator is logged on to the system with
a local terminal when a modem call is received, the operator will automatically be logged off
the system and will not be able to restore local access until the modem connection is broken.
Sub Rate Unit Card

The sub rate unit (SRU) card in a prime site channel bank performs three functions:
It formats audio and control signals from the simulcast subsystem comparators
for insertion into WAN card time slots.
It recovers and formats the signal from the remote site WAN card time slots for
delivery to the simulcast subsystem comparators. The connections between the
LDSRU ports and the comparators consist of V.24 links.
It serves as the interface to the digital mutual aid stations when present at the prime site.
Each SRU card has ten interfaces for external equipment.
HSU Card
The HSU card in the channel bank is used to interface the prime site router to the prime site
channel bank. It is a high speed communication card used to transmit the network management
information between the subsystem and the master site.
4-Wire Card
In an ASTRO 25 system the 4-wire card is used when the prime site includes analog mutual aid
channels. In such cases the 4wire card performs two functions:
It translates an analog signal to a digital bitstream (PCM) and places the digital
signal in a specified WAN card time slot.
It recovers the PCM signal from a WAN card time slot, converts the digital signal to an
analog signal, and delivers the signal to an analog mutual aid repeater.
Each 4-wire card has eight interfaces for external equipment.
Power Supplies
The channel bank can accommodate two power supplies, both AC or both DC. One power
supply can provide all the necessary power for the modules in the channel bank. If two power
supplies are installed, they operate in load share mode.
5-56 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System TRAK 9100
TRAK 9100
Figure 5-29 shows the TRAK 9100 Simulcast Site Reference (SSR), which is a GPS-based Frequency
and Time reference unit. The signal requirements that TRAK 9100 SSR box provides for the simulcast
system are 1 pps (pulse per second), 5 Mpps, and 1 pps + 5 Mpps composite signals.
At the prime site the TRAK 9100 SSR provides 1 pps and 5 Mpps for the comparators. The 1 pps
+ 5 Mpps composite signals is used by the simulcast base radios at the remote sites.
For the digital simulcast subsystem, the TRAK 9100 SSR in the prime site will serve the Universal Time
Configuration (UTC) time to the comparator, site controller, and colocated simulcast base radios. If the TRAK
9100 at the prime site fails, the clients at the prime site must request UTC time from the master site TRAK 9100.
To accomplish this, the clients at the prime site must be programmed with the IP address of the TRAK 9100 at
the prime site as first choice and the IP address of the TRAK 9100 at the master site as the second choice.
The TRAK 9100 at the remote sites will serve the UTC time for the remote site router and the simulcast
base radios at the remote site. The remote site router and simulcast base radios at the remote site
must be programmed with the IP address of the TRAK 9100 at the remote site as the first choice
and the IP address of the TRAK 9100 at the prime site as the second choice.
Figure 5-29 Prime and Remote Site TRAK 9100
The Trak 9100 supplies a highly accurate time and frequency reference signal to the comparator. The
comparator uses the time reference to compute transmission launch times, and uses the frequency reference to
generate the data transmission clock. The DDM modules in the Trak 9100. The digital distribution modules
(DDM) in the Trak 9100 distribute a 1 pps, 5 pps or composite signal. The BNC connector on the front of the
station control module of the comparator accepts an external 5 MHz or 10 MHz frequency reference signal.
6881009Y05-O April 2004 5-57

Simulcast Sites Chapter 5: Radio Frequency Subsystems
The Telcom module in the Trak 9100 can provide either framed T1 or E1 output; 1.544
MPPS for T1 and 2.048 MPPS for E1. The telcom module is factory configured for either
T1 or E1 output and can not be changed in the field.
For information on component power supplies, see Appendix A, "Power Supply Reference."
Simulcast Sites

A digital simulcast subsystem consist of a prime site and a number of remote sites. The following
two remote sites are supported in a digital simulcast subsystem:
Simulcast remote site supporting the simulcast subsystem operating in the

700 MHz, 800 MHz or VHF/UHF bands
Simulcast receive only remote site supporting the simulcast subsystem with
receive only sites operating in the VHF/UHF bands only
The receive only remote site used in the simulcast subsystem with receive only remote sites uses
the same hardware components as the receive only remote site used in the Single Transmitter
Receiver Voting (STRV) subsystem. Both operate in the VHF/UHF bands.
All simulcast subsites are linked to the simulcast prime site in the digital simulcast subsystem.
Simulcast Remote Site

A simulcast remote site, as defined here, is a simulcast subsite equipped with at least one station providing
a transmitter and receiver. Simulcast remote sites in a subsystem are all linked to a simulcast prime site.
At least two simulcast remote sites are required in a digital simulcast subsystem.
5-58 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Simulcast Remote Site
A simulcast remote site with both transmit and receive capability is differentiated
from a simulcast receive only remote site. See "Receive Only Remote Sites" on page
5-77 for information on a Receive Only Remote Site.
A number of receivers from various simulcast remote sites, covering a particular area in the subsystem,
may receive the same signal (a call) transmitted from a portable or mobile subscriber unit. The simulcast
remote sites route these signals to the simulcast prime site where the audio signals for a particular call are
processed by a comparator to establish the best quality audio signal. The best quality audio signal for the
call is packaged and sent to the zone master site where it picks up routing information (the core router or
rendezvous point). The audio signal is then routed through the system to the intended destination(s).
When a signal to be transmitted in a digital simulcast subsystem is received from the zone master site, it is
routed to a base radio at each simulcast remote site in the subsystem. At a predetermined time, all of the base
radios broadcast the audio signal simultaneously on the same frequency to complete the communication.
Simulcast remote sites accept multiple V.24 links and an Ethernet link from the simulcast prime site. The V.24
links are interfaced to RF base station equipment (one per base station) to carry the voice traffic. In the case
where the channel is the control channel, the V.24 link handles the trunking control channel traffic.
The simulcast remote network systems Ethernet output is connected to the remote site LAN. In addition
to the remote site router, all the base stations reside on the LAN. The Simulcast Remote Network System
routes network management traffic between the simulcast prime site and the simulcast remote sites.
The simulcast remote subsites contain the following components:
Base station The STR 3000 base radio (700 MHz or 800 MHz) or the QUANTAR
base station for VHF (134 MHz175 MHz) or UHF (380 MHz520 MHz)
Radio Frequency Distribution Systems (RFDS) STR 3000 base station equipment
Global Positioning Satellite (GPS) timing equipment
Channel bank
Routers
6881009Y05-O April 2004 5-59

STR 3000 Base Radio Simulcast Chapter 5: Radio Frequency Subsystems
Ethernet switches
Figure 5-30 Simulcast Remote Site
STR 3000 Base Radio Simulcast
Figure 5-31 illustrates the STR 3000 Base Radio, which is the RF component of the digital-only
simulcast trunking infrastructure. The STR 3000 includes from one to six base radios, the Radio
Frequency Distribution System (RFDS), and cabling in a single cabinet. This equipment provides
the transmit/receive capabilities for the digital simulcast subsystem, improves the site separation
capability and delivers an ASTRO compliant digital simulcast solution.
The STR 3000 base radio supports two frequency bands, the 800 MHz and the 700 MHz bands. The 700
MHz base radios can be used to add new subsites to a 700 MHz simulcast subsystem. 700 MHz base
radios can also be used to expand the number of channels in 800 MHz simulcast subsystems.
Subscriber radio frequency band and roaming capabilities must be considered when 700 MHz base
radios are used to expand 800 MHz subsites. 700 MHz channels must not be designated as control
channel capable if the subsystems include subscribers that can only operate in the 800 MHz band.
The base radio forwards data from the comparator to the transmitter and forwards data
from the receiver to the comparator. The base radio transmits data using Linear Simulcast
Modulation (LSM) and receives C4FM modulated data.
5-60 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System STR 3000 Control Module LED Indicators
Figure 5-31 STR 3000 Base Radio 700 MHz or 800 MHz
The Radio Frequency Distribution System (RFDS) provides the interface between the base radios
and the site antennas. The transmitter combiner portion and the receiver multicoupler portion of
the RFDS are required equipment. One RFDS services a rack with up to six base radios. Up to 12
transmitters may be combined on to a single transmit antenna. Up to 24 receivers may be fed from
one receive antenna. Separate transmit and receive antennas are required.
Eliminating or choosing an alternative RFDS is NOT possible. The RFDS has been
designed by Motorola as an integral component of the STR 3000. It is supplied by
Celwave to meet the necessary specifications of the product. The RFDS product
has not been certified as a standalone product.
STR 3000 Control Module LED Indicators

The control module monitors the functions of other repeater modules. The LEDs on the front
panel indicate the status of the monitored modules. The CTL LED on the front panel light
control module and Table 5-12 describes the function of the LEDs.
6881009Y05-O April 2004 5-61

STR 3000 Control Module LED Indicators Chapter 5: Radio Frequency Subsystems
Figure 5-32 LED Indicators on Control Module
Table 5-12 LED Description
Normal
LED Color If the LED is It indicates that
State
On Green On On The repeater is on.
Fail Red Off On A station failed. If the STR 3000 is exhibiting a failure
that prevents it from operating, use CSS to review the
radios status report to determine which module failed.
Blinking on once The external frequency reference failed. It also indicates
per second. if the receiver or transmitter are not locked on frequency.
Blinking on twice The station is being configured.
per second.
SVC Amber Off Blinking on once The repeater is in service mode.
per second.
Blinking on twice The transmitter is inhibited.
per second.
CTL Green Off On This channel is operating as the current control channel.
On and blinks An inbound signaling packet arrived.
off for 250
milliseconds.
Blinking once per This channel is in Failsoft.
second.
Rx Green Off On The receiver is active.
Off The receiver is inactive
Blinking once per The channel is detecting an illegal carrier.
second.
PA Green On On The base radio is transmitting at programmed power
levels.
Blinking Power has dropped below the programmed level.
5-62 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Simulcast Base Station
Table 5-12 LED Description (Continued)

Normal
State
Blinking on once The receiver is inhibited.
per second.
Blinking on twice The transmit function (Exciter, PA) is inhibited.
per second.
V24 Green On On Link to ASTRO TAC comparator is active.
Blinking on once Link to ASTRO TAC comparator is lost.
per second.
Simulcast Base Station
Simulcast base radios, installed together in a cabinet with Radio Frequency Distribution System
(RFDS) equipment installed above the base radios, completes the STR 3000 Simulcast base station.
The Simulcast base station for an 800 MHz subsystem is shown in Figure 5-33 while the Simulcast
base station for a 700 MHz subsystem is shown in Figure 5-34.
6881009Y05-O April 2004 5-63

Simulcast Base Station Chapter 5: Radio Frequency Subsystems
Figure 5-33 STR 3000 Base Station 800 MHz
5-64 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System QUANTAR Base Station
Figure 5-34 STR 3000 Base Station 700 MHz
The RFDS equipment supporting a 700 MHz STR 3000 base station is slightly different
from RFDS equipment supporting an 800 MHz STR 3000 base station.
QUANTAR Base Station
The QUANTAR base station is a non-linear, C4FM base station providing support in the VHF/UHF
frequency bands and wireline support for the ASTRO-TAC comparators.
6881009Y05-O April 2004 5-65

Simulcast Remote Site Router Chapter 5: Radio Frequency Subsystems
The RFDS provides an interface between the base stations and the site antennas. The RFDS for the non-linear
base station is not a structured part of the base station. Separate transmit and receive antennas are required.
The QUANTAR base station provides V.24 wireline support. The V.24 audio signal is sent to
comparators for receiver voting in a simulcast or single transmitter receiver voting subsystem.
The J15 jumper off the backplane handles the digital V.24 interface. A DB25 to RJ-45 connector
adapter on the rear of the QUANTAR provides the physical interface.
Figure 5-35 QUANTAR Base Station, UHF Version - Front View
Simulcast Remote Site Router
In a simulcast remote site, the remote site router transports the site network management information to and
from the Zone Manager, FullVision INM and MOSCAD Network Management servers. The remote site router
connects directly to the TeNSr channel bank HSU card through the FlexWAN/V.35 interface. The LAN port is
connected to the Ethernet switch where the STR 3000 and MOSCAD RTU are also connected. See Figure 5-36.
Figure 5-36 Remote Site Router
5-66 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Remote Site LAN Switch
While Figure 5-36 shows the Motorola Network Router (MNR) S2500 with two
I/O modules, the T1/E1 module and FlexWAN module, respectively, the simulcast
remote site router requires one FlexWAN module.
Remote Site LAN Switch
10/100Base-T LAN switches are required to interface the remote site router to the base
radios. Two switches are used at the site, odd numbered base radios are connected to one
switch, even numbered base radios to the other switch.
Each switch provides 24 ports that provide connectivity for a 10/100Base-T LAN. The switches are
connected to each other through a Gigabit stacking interface that makes it possible to provide a management
communication link with up to 30 base radios. The two switch configuration also provides a degree
of protection in the case of a switch failure. If one switch should fail, a management link still exists
to the base radios connected to the unaffected switch, audio services are not affected.
The LAN switches send SNMP traps back to the Network Management system.
Figure 5-37 HP 2524 Procurve Remote Subsite Ethernet Switch
Channel Bank
The simulcast remote site channel bank provides the connectivity to the simulcast prime
site. It is configured with the following cards:
CPU card
Interface card - Use the WAN link connector to connect the WAN card ports
to incoming and outgoing T1 or E1 lines.
A two-port WAN card for sites with more than 22 channels or a one port WAN card
for sites with fewer than 22 channels. For T1 or E1 termination.
A CSU card for each WAN T1 port in use
V.24 cards (10-port LDSRU). The number of cards depends on the number of
channels at the site. These cards are used to interface the ASTRO 25 trunked repeaters
as well as the conventional, digital mutual aid repeaters.
A V.35 card (HSU) for site router connections
A 4wire interface card for analog mutual aid repeaters
6881009Y05-O April 2004 5-67

Simulcast Subsystem Configuration Overview Chapter 5: Radio Frequency Subsystems
Dual power supplies

Figure 5-38 shows a remote site channel bank.
Figure 5-38 Simulcast Remote Subsite Channel Bank
The simulcast remote site data link is embedded within the 9600 bps voice link. These are
connected to the stations through LDSRU V.24 ports from the TeNSr.
A separate 64 Kbps management link is connected to the site for Network Management functionality.
This Network Management link is connected from the TeNSr through an HSU V.35 port to the remote
site router. The router converts the information to 10Base-T and delivers it to the LAN through the two
Ethernet switches. The base radios connect to the LAN through their 10Base-T interface.
Simulcast Subsystem Configuration Overview

Configuration considerations for a simulcast subsystem include establishing essential remote

sites and using the Configuration/Service Software (CSS) to program the configuration and
operating modes of simulcast subsystem equipment.
5-68 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Essential Remote Sites
Essential Remote Sites
In a digital simulcast subsystem, a remote subsite can be designated as essential in the zone
configuration manager, simulcast remote subsite configuration records. The record contains a field
called Subsite Availability Number which is used to specify the percentage of traffic channels
required to malfunction before the subsystem ignores a subsite. If the percentage of malfunctioned
subsite channels rises above the availability number, the simulcast subsite is placed in the Malfunctioned
state. If the malfunctioned remote subsite is an essential subsite, the digital simulcast subsystem is
placed in failsoft regardless of the health of the rest of the subsystem.
The Subsite Availability Number field specifies a value of 100 to designate an essential remote
subsite. At least one control channel and one voice channel must be enabled for the entire digital
simulcast subsystem to remain in trunking mode. An essential remote subsite can cause the
subsystem to go into failsoft under either of the following conditions:
No control channel is available at the essential remote subsite and at least
one wide area failsoft channel is available.
No voice channels are available at the essential remote subsite. If the control channel is
functional and has failsoft capability, the digital simulcast subsystem goes to failsoft.
An essential remote subsite cannot support failsoft if its link to the prime site fails. In such
instances, the simulcast subsystem is programmed to ignore the essential remote subsite in order
to maintain communication with the rest of the subsystem.
Remote subsites with the Subsite Availability Number set for less than 100 is ignored by the system if
all of its control channels or a certain percentage of its traffic channels have malfunctioned. The rest
of the digital simulcast subsystem continues to operate in wide area trunking mode.
Digital Simulcast Subsystem Configuration Using CSS
Once the subsystem is installed, it is necessary to use the Configuration/Service Software (CSS) to program the
configuration and operation modes. CSS can be used to configure the STR 3000, the ASTRO-TAC 9600 and
the MTC 9600. Figure 5-39 shows the menu structure and four of the programming windows available in CSS.
6881009Y05-O April 2004 5-69

Software Download Manager Chapter 5: Radio Frequency Subsystems
Figure 5-39 CSS Software
The Software Download (SWDL) Manager is an application that centralizes the transfer and restart of
new ASTRO 25 digital simulcast subsystem software. The application is a standalone utility that can be
launched from the PRNM Application Launcher, as shown in Figure 5-40. SWDL can also be installed
and run from a PC laptop or desktop that does not include the PRNM applications.
Figure 5-40 SWDL in PRNM Application Launcher
5-70 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Software Download Considerations for Subsystems with Receiver Only Sites
While software download is run from the application launcher, your

operating system may be different.
Software Download Considerations for Subsystems with Receiver Only Sites
Before you download software to an MTC 9600 prime site controller in a simulcast subsystem or in
an STRV subsystem, you must un-configure the receiver-only sites, perform the software upgrade
using the software download manager application, then re-configure the receiver only sites.
Software Download Operations

Apart from allowing centralized transfer and installation of new software on digital simulcast subsystem
components, the SWDL Manager minimizes the total system downtime encountered during the
upgrade process. The SWDL Manager application performs three operations:
Transfer Only operation
Install Only operation
Transfer and Install operation
Transfer Only Operation

The Transfer Only operation is the process by which software is transferred to a proxy device and cross-loaded
to the other devices on the LAN. The Transfer Only operation identifies the proxy devices within the
target digital simulcast subsystem, and transfers new software directly to the proxy device. Transfer and
subsequent cross-loading of software to devices can be done while the site is still trunking to minimize
system downtime. The software is only transferred to the devices not already installed.
Install Only Operation

The Install Only operation allows the user to install previously transferred software. Install Only is
first done on a proxy device selected by the SWDL Manager, and then on the rest of the non-proxy
devices. Channel installation begins with the highest channel number and continues down through
all the channels. The control channel is the last in the sequence.
Transfer and Install Operation

The Transfer and Installation operation is designed to execute the transfer operation and the install operation,
one after the other, without user intervention. You can cancel the transfer and install operation before the
transfer is complete and the transfer operation will always finish. Once the target device has gone past the
transfer operation, the operation cannot be interrupted. The install operation always finishes once it starts.
More information on CSS is available in the programs online help files. Software download is
discussed in more detail in Volume 3, Managing Zone Infrastructure.
6881009Y05-O April 2004 5-71

Single Transmitter Receiver Voting Subsystem Chapter 5: Radio Frequency Subsystems

A Single Transmitter Receiver Voting (STRV) subsystem covers a single geographic area with a single
transmitter and provides radio communication support in the UHF/VHF frequency bands. The STRV
subsystem contains many of the same components found in a simulcast subsystem, but the STRV subsystem
does not require simulcast site reference devices since simultaneous transmission (time launching of
signals) from multiple transmitters is not required in a single transmitter subsystem.
STRV prime site (with or without colocated remote site)

STRV transmit remote site
STRV receive only remote site (VHF/UHF bands only)
The receive only remote site, as mentioned above, is the same as the receive only remote site
found in the simulcast subsystem with receive only remote sites operating in the VHF/UHF bands.
The following are other characteristics of the STRV subsystem:
The STRV subsystem must have a single transmit (colocated or remote) site
and one or more receive only remote sites.
The STRV subsystem can have a maximum of 30 RF channels.
All remote sites in the STRV subsystem contain the same number of channels
variable density is not supported.
The audio in the STRV subsystem is transported in digital format only.
The STRV subsystem operates in the VHF and UHF frequency bands only.
Data Capability Characteristics STRV Subsystem
The STRV subsystem is a data-capable subsystem when the following conditions exist:
The subsystem must be in wide area trunking.

Both the MTC 9600 Prime Site Controllers must be on the same virtual
local area network (VLAN).
The Radio Network Gateway (RNG) at the zone master site must be linked
with the Digital Cross-connect Switch (DCS).
When the simulcast or STRV subsystem is data-capable, the zone controller at the master site determines
how many channels can be used for data and coordinates channel preemption.
Alarms are sent to FullVision INM when data capability is enabled, disabled, or reset.
5-72 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Wide Area Trunking, Site Trunking, and Failsoft mode
The MTC 9600 prime site controller must be configured with the RNG IP address, the maximum number
of users per data channel, a page wait timer, and a voice grant filter to be data-capable.
Wide Area Trunking, Site Trunking, and Failsoft mode
Wide area trunking is the normal operating state of the STRV subsystem. In this state, the remote sites
receive call processing instructions from the master site zone controller and a radio subscriber, registered
at a site, can communicate with any other radio subscribers in the system. The basic criteria for wide
area trunking includes an active RF site control path between zone controller and site, an enabled audio
rendezvous point in the zone, a control channel, and a voice channel at a site.
When the STRV subsystem loses communication with the master site zone controller, the subsystem
continues to trunk its channel resources within its boundaries and is in the site trunking state.
When the site controllers are not available to provide trunking operations, the subsystem
enters a failsoft mode of operation. This also occurs if all control channels are disabled
or malfunctioned or if only one channel is enabled.
The operating modes of the STRV subsystem are similar to those for the digital simulcast subsystem.
See "Digital Simulcast Subsystem Modes of Operation" on page 5-39.
Single Transmitter Receiver Voting Prime Site

The STRV prime site provides an interface between the subsystems remote sites and the zone master site. The
prime site router is the device supporting this site link interface. As an option, a second prime site router is
employed to establish a redundant site link from the STRV prime site to the zone master site. The STRV prime
site can support a colocated remote site. A STRV prime site with colocated remote contains a remote site within
the same physical location of the prime site. The remote site can be an STRV remote site or receiver only site.
An STRV prime site with colocated remote site has either a colocated transmit remote
site or colocated receive only remote site, but not both.
The following components are included at the single transmitter receiver voting prime site:
MTC 9600 site controller two are included for redundancy

ASTRO TAC 9600 comparator one for each channel in the subsystem
Prime site LAN switches two 24 port Ethernet switches
6881009Y05-O April 2004 5-73

STRV Prime Site with Colocated Transmit Remote Site Chapter 5: Radio Frequency Subsystems
Prime site router one router required, a additional second router for
an optional redundant site link
Prime site channel bank one channel bank for WAN interface with the zone master
site and V.24 (LDSRU cards) interface with the ASTROTAC comparators
MOSCAD an optional component
The following are characteristics of the STRV prime site:
The link between the STRV prime site and the zone master site is a T1
link using IP over Frame Relay.
The ASTRO-TAC 9600 comparators at the STRV prime site encapsulate the V.24 audio into
Ethernet packets which are then sent to the prime site router for encapsulation as Frame Relay
packets. A T1 link is used to transport the Frame Relay packets containing voice, site control
information, and network management information between the prime site and the master site.
The ASTRO-TAC comparators at the prime site interface with the remote site base
stations using V.24 links for voice and control information.
Ethernet links are used for network management information.
STRV Prime Site with Colocated Transmit Remote Site
To support a remote site colocated at the prime site, the following additional components are included:
QUANTAR base station A non-linear, C4FM base station operating in the VHF/UHF
frequency range providing transmitter and receiver functionality
STRV Prime Site with Colocated Receive Only Remote Site
To support a receive only remote site colocated at the prime site, the following components are included:
Satellite receiver A QUANTAR satellite receiver (VHF/UHF with Ethernet interface)

or an ASTROTAC satellite receiver (VHF/UHF with no Ethernet interface)
MOSCAD required when the ASTRO-TAC receiver is used to support
software download operations
MTC 9600 Prime Site Controller
The MTC 9600 prime site controller is designed for use in an ASTRO 25 STRV prime site using a
9600 bps control channel. The MTC 9600 site controller communicates with the zones master site
zone controller to provide call processing support for STRV remote sites. The MTC 9600 controller
is capable of supporting up to 15 subsites and up to 30 channels per subsite.
Two (redundant) MTC 9600 prime site controllers are required at the STRV prime site; one is the
active controller, the other is a standby controller. The standby controller automatically takes over
site link and control operations if the active site controller fails. Both site controllers have an
5-74 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Control Module MTC 9600 Site Controller
Ethernet link through the Ethernet switch to support redundant operations. Channel status information
is constantly maintained between the active and standby site controller to ensure that accurate
channel capability information is always sent to the zone controller.
See Figure 5-21, on page 5-44 for an illustration of the MTC prime site controller
The following characteristics apply to the MTC 9600 prime site controller in the STRV
prime site. The MTC 9600 prime site controller:
Supports Integrated Voice and Data.

Generates the Outbound Signalling Packet (OSP).
Provides support for explicit OBT See Table 2-1 on page 2-22.
Processes inbound and outbound data requests at the site by requesting new
data channels from the master site zone controller and by routing data between
the channels and the radio network gateway.
For more on the data capability of the MTC 9600 prime site controller, see
Control Module MTC 9600 Site Controller

The control module in the MTC 9600 site controller consists of a single board computer module and a
transition module interconnected by the mid-backplane in the CompactPCI chassis. There is only one
control module for all channel configurations. The transition module contains an RS-232 connector for
local access to the controller. Application software is installed on both site controllers. The MTC 9600
controller supports software cross-load between the standby and active units for software upgrades.
Power Supply
The standard MTC 9600 controller has been designed with a power supply, which operates over a wide range
of voltages (110/220 VAC) and frequencies (5060 Hz) without any modifications or jumper changes. The
power supply is enclosed in a metal case with a self-contained, thermostatically controlled cooling fan.
Diagnostics
The MTC 9600 controller has been designed with internal diagnostic tests that occur on power up and reset.
Diagnostic tests are available for the hard drive, control module, and power supply. If a problem occurs
during operation, it will be reported as an alarm. All alarms are stored in the Alarm Log, accessible with
CSS. The alarm log contains the name of the diagnostic test that failed and the time since the last power
up. Critical alarm conditions alarms are also reported directly to the Network Manager.
6881009Y05-O April 2004 5-75

STRV Transmit Remote Site Chapter 5: Radio Frequency Subsystems
STRV Transmit Remote Site

The STRV transmit remote site has transmitter and receiver functionality operating in the VHF/UHF
band. At least one STRV remote site must exist in the STRV subsystem.
The following components are included at the STRV transmit remote site:
QUANTAR base station A non-linear, C4FM base station operating in the VHF/UHF
frequency range providing transmitter and receiver functionality
Remote site router Motorola Network Management (MNR) S2500
Remote site Ethernet LAN switch
Remote site channel bank
MOSCAD optional
Figure 5-41 Single Transmit Remote Site
QUANTAR Base Station
The QUANTAR base station used for the Transmit Remote Site in an STRV subsystem is
the VHF/UHF version as shown in Figure 5-42.
5-76 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Receive Only Remote Sites
Figure 5-42 QUANTAR Base Station, UHF Version - Front View
Receive Only Remote Sites

Receive only remote sites operate in the VHF/UHF bands and are supported by the following subsystems:
Simulcast subsystem with receive only remote sites

STRV subsystem
Receive only remote sites help to balance the coverage (talk-in coverage with talk-out
coverage) for the subsystem.
A receive only remote site includes the following components:
Satellite receiver A QUANTAR satellite receiver (VHF/UHF with Ethernet interface)

or an ASTRO-TAC satellite receiver (VHF/UHF with no Ethernet interface).
Channel bank Provides a V.24 interface connection to each receiver and a WAN
interface for T1 transport to the simulcast prime site for receiver voting.
MOSCAD Provides support for monitoring and reporting operating system status. Optional
with the QUANTAR receiver. Required with the ASTRO-TAC receiver for software download.
6881009Y05-O April 2004 5-77

QUANTAR Satellite Receiver Chapter 5: Radio Frequency Subsystems
Receiver multicoupler specified and/or provided by the field engineer.
Figure 5-43 Receive Only Remote Site
The QUANTAR receiver in a receive only remote site is a QUANTAR station without the
transmitter (that is, the power amplifier or exciter modules).
QUANTAR Satellite Receiver
The QUANTAR satellite receiver (VHF/UHF with Ethernet Interface) used in a receive only remote
site for the simulcast subsystem or STRV subsystem is shown in Figure 5-44.
5-78 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System ASTRO-TAC Receiver
Figure 5-44 QUANTAR Satellite Receiver, UHF Version - Front View
ASTRO-TAC Receiver
The ASTRO-TAC satellite receiver (VHF/UHF with no Ethernet interface) used in a receive only remote
site for the simulcast subsystem or STRV subsystem is shown in Figure 5-45.
Figure 5-45 ASTROTAC Receiver, UHF Version Front View
Software Download Considerations Receive Only Remote Sites
Software download functionality for receive only remote sites is different depending
on the type of receiver used at the site.
6881009Y05-O April 2004 5-79

Receive Only Remote Site Map to Transmit Site Chapter 5: Radio Frequency Subsystems
The Software Download (SWDL) Manager application centralizes the transfer and restart of
new ASTRO 25 digital simulcast subsystem software. The application is a standalone utility
you can launch from the PRNM Application Launcher.
Receive Only Remote Site Map to Transmit Site
Receive only remote sites used in either the simulcast subsystem with receive only sites or
the STRV subsystem must be mapped to a transmitter site in their respective subsystems to
support comparator equipment at the subsystems prime site.
Using the Zone Configuration Manager (ZCM) to set up zone infrastructure for a multisite subsystem involves
selecting a subsystem topology (simulcast, simulcast with receive-only remote sites, or STRV), establishing a
subsystem name (alias) and identification number (multisite subsystem ID), and establishing configuration
parameters for the remote sites objects associated with the subsystem. The following configuration parameters
must be established when establishing configuration parameters for receive only remote sites:
Subsite type Receive-only

Base radio type QUANTAR receiver or ASTRO-TAC receiver
Map to transmit site ID Remote site ID number of a remote site with a transmitter
For more detailed information regarding how to map a receive only remote site to a transmit
site ID, see Volume 11: Simulcast Installation and Configuration.
Receive Only Remote Sites Using CSS to Configure the Comparator

In addition to using ZCM to set up the zone infrastructure, the CSS must be used to configure
the ASTRO-TAC 9600 comparator (a subsystems prime site component) by mapping receive
only remote sites to a transmit site for a given subsystem.
After CSS is successfully connected to the comparator (for example, connecting a laptop running
CSS to the comparator) and after successfully reading the configuration file, the comparator
supporting subsystems with receive only remote sites can be configured to map the receive
only remote sites to a transmit site ID (site with a transmitter).
See Figure 5-46. Use CSS to map the receive only remote sites to a transmit site ID (site with a
transmitter) for the comparator. To do this, select the ASTRO-TAC 9600 Configuration object, then
chose the SubSite Configuration Tab to access a table with the following columns:
SubSite Number a list of the remote sites

SubSite Type a drop-down list for selecting the type of remote site
(Tx/Rx, Rx Only, Disabled)
Associated TX Site ID a drop-down list for selecting the remote transmit site ID
number to be associated with the Rx Only remote site
5-80 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Digital Simulcast Subsystem 10Base-2
Figure 5-46 CSS ASTRO-TAC 9600, SubSite Configuration Tab
For any SubSite Type field associated with an Rx Only value, select the appropriate transmit
site ID from the Associated TX Site ID drop-down list.
Digital Simulcast Subsystem 10Base-2

ASTRO 25 systems support two types of LAN for the prime site and the remote subsites, a 10/100Base-T
LAN and a 10Base-2 LAN. A system with 10Base-2 LAN is shown Figure 5-47 and Figure 5-48.
6881009Y05-O April 2004 5-81

Digital Simulcast Subsystem 10Base-2 Chapter 5: Radio Frequency Subsystems
Figure 5-47 Simulcast Prime Site with 10Base-2 LAN
Hardware differences between the simulcast subsystem previously described and the one
shown in Figure 5-47 and Figure 5-48 are:
The LAN connecting the comparators, Ethernet switches, and the site
controllers is a 10Base-2 LAN.
Only one of the Ethernet switches is connected to the prime site router
through a 10Base-T connection.
A hub is used to convert the management LAN for the colocated remote
subsite base radios from 10Base-2 to 10Base-T.
All hardware at the prime site is identical to the system with the 10Base-T
LAN with the exception of the Ethernet switches.
5-82 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Digital Simulcast Subsystem 10Base-2
All hardware at the remote sites is identical to the system with the 10Base-T LAN
with the exception of the LAN interface between the base radios and the site router.
A hub is used in the subsite shown in Figure 5-48 to convert the 10Base-2 LAN for
the base radios to the site routers 10Base-T interface.
Figure 5-48 Simulcast Subsystem Remote Subsite with 10Base-2 LAN
Table 5-13 summarizes the operational differences between two simulcast subsystems, each
representing the type of LAN supported in ASTRO 25 systems.
Table 5-13 System Operational Differences
System with 10Base2 LAN and System with 10BaseT LAN and
Condition
Single Site Router Single Site Router
Simulcast operation No difference between the two systems.
Failure of switch connected to site Simulcast subsystem operates in Simulcast subsystem operates in site
router site trunking with all the operating trunking with the resources connected
resources. to the functioning switch.
Failure of switch not connected to the Simulcast subsystem operates in wide Simulcast subsystem operates in wide
site router area mode with all the operating area with the resources connected to
resources. the functioning switch.
6881009Y05-O April 2004 5-83

Digital Simulcast Subsystem 10Base-2 Chapter 5: Radio Frequency Subsystems
Table 5-13 System Operational Differences (Continued)

System with 10Base2 LAN and System with 10BaseT LAN and
Condition
Single Site Router Single Site Router
Single point break in the prime site The simulcast subsystem operates in The simulcast subsystem continues to
LAN failsoft mode. The simulcast subsystem operate in wide area mode minus the
operates in site trunking mode if the resources lost at the break point. The
break takes place between the switch simulcast subsystem operates in site
and the site router. trunking mode if the break takes place
between the switch and the site router.
Single point break at the remote site Management and software download Management and centralized software
LAN functions are lost if the break is between functions are lost if the break is
the base radios and the hub. Only the between the site router and the switch.
management functions are lost if the Management and software functions
break is between the hub and the site are lost only to the affected component
router. if the break is between one of the base
radios and its corresponding switch.
5-84 6881009Y05-O April 2004

Chapter
6
ASTRO 25 Systems and Mutual Aid

Mutual aid is a system of conventional radio resources shared by public safety agencies
from various geographical locations. The resources are used whenever inter-agency
communications is required during an emergency situation.
ASTRO 25 systems support mutual aid operation by providing the means to transport the mutual aid
audio from the ASTRO 25 Repeater sites, IntelliRepeater sites, and Multisite subsystems (simulcast
subsystems or single transmit receiver voting subsystem) to the dispatch equipment. ASTRO 25
audio and mutual aid audio share the transport resources to the master site where they are separated
at a digital cross connect switch and routed to the appropriate destinations.
The IP resources in an ASTRO 25 system do not process mutual aid audio.

This section covers the equipment required by the subsystems to support mutual aid and
some of the possible subsystem configurations.
Digital Mutual Aid

Availability of the 700 MHz band makes it possible to expand mutual aid capabilities to areas
where other bands are not available. The 700 MHz band has been designated as a digital band and
thus requires the use of ASTRO capable base stations and subscribers.
The Motorola solution for digital mutual aid fixed equipment is based on the STR 3000 platform
previously developed for ASTRO 25 simulcast subsystems. A conventional, 700 MHz, digital base
radio is available to agencies requiring digital mutual aid. The Motorola XTS 5000 portable radios
and Motorola XTL 5000 mobile radios are capable of operation in this new band.
Configurations
The following sections describe some sample mutual aid configurations.
6881009Y05-O April 2004 6-1

Remote CEB With Mutual Aid Chapter 6: ASTRO 25 Systems and Mutual Aid
Remote CEB With Mutual Aid
Figure 6-2,"Mutual Aid with Colocated CEB - Outbound Call" on page 6-4 shows the configuration used
when 700 MHz mutual aid stations are colocated with a Central Electronics Bank (CEB). Note that in this
type of configuration the only component shared between the mutual aid subsystem and the ASTRO 25
system is the console with its ability to monitor and patch, both, conventional and trunked talkgroups.
ASTRO 25 remote sites sharing transport resources with mutual aid support up to
eight digital mutual aid stations.
In ASTRO Common Air Interface (CAI), mutual aid systems, an RS-232 link between the ASTRO
Console Interface Module (ACIM) and DIU carries all control and status information that flows between
the Digital Interface Unit (DIU) and the console. The control and status information include:
ID information such as individual IDs or conventional talkgroup IDs
Received call indication
Received mode (ASTRO secure or ASTRO clear)
Base station keying commands
The DIU embeds conventional feature signaling, station keying commands, and other control sequences sent
from the console through the ACIM link into ASTRO voice frames bound for the station. The DIU also
extracts the digital signaling from the station and sends it to the console through the ACIM link.
Inbound Call Sequence

Figure 6-1,"Mutual Aid with Colocated CEB - Inbound Call" on page 6-3) illustrates
the inbound call sequence operation as follows:
1. The subscribers transmit into the base station.
2. The base station, through its ASTRO wireline interface, sends the ASTRO information
to the DIU where it is divided into audio and signaling.
3. The DIU converts the ASTRO audio to analog audio and routes it to the Base Station
Interface Module (BIM) through the DIUs analog interface.
4. The signaling information is sent to the ACIM through one of the DIUs communication ports.
5. The BIM recognizes the activity and sends a message to the Console Operation Interface
Module (COIM), which activates a call light on the dispatch position.
6. The ACIM decodes the control information and sends it to the BIM.
7. The BIM converts the received analog audio to Pulse Code modulation (PCM)
and places it on the CEBs digital audio bus.
8. The BIM also relays the Push-To-Talk ID information to the COIM through the CEBs data bus.
9. The COIM converts the PCM audio to analog and sends it to one of the speakers in the console
interface unit. It also sends the ID information to the console through a data link.
6-2 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Outbound Call Sequence
10. On Elite consoles, the IDs are sent to the client workstation where it performs
a local alias lookup function. If aliasing is not used, the radio IDs appear on
the channel resources at the dispatch positions.
Figure 6-1 Mutual Aid with Colocated CEB - Inbound Call
Outbound Call Sequence

Figure 6-2,"Mutual Aid with Colocated CEB - Outbound Call" on page 6-4) illustrates the
following sequence of events that take place when the Elite console operator activates the
Push-To-Talk (PTT) switch on the dispatch position:
1. The Console Interface Equipment (CIE) sends the PTT to the COIM in the form of a data signal.
2. The Console Operator Interface Module (COIM) sends a message to the Base
Interface Module (BIM) requesting channel activation.
3. The BIM sends the channel activation instructions to the ACIM through the Aux I/O link.
4. The ACIM converts the request into ASTRO data and transfers the information to the DIU.
5. If the channel is not busy, the BIM instructs the COIM to route the operators microphone audio.
6. The COIM converts the analog audio from the microphone to Pulse Code Modulation (PCM).
7. The operators audio is routed to the BIM where it is converted from digitized
audio (PCM) to analog audio.
6881009Y05-O April 2004 6-3

Outbound Call Sequence Chapter 6: ASTRO 25 Systems and Mutual Aid
8. The audio is sent to the DIU through its analog connection with the BIM.
9. The DIU performs the following actions:

Converts the analog audio from the BIM to ASTRO CAI frames
Combines the audio with the ID and control information supplied by the ACIM
10. The DIU, through its ASTRO interface, sends the ASTRO information (audio
and embedded data) to the mutual aid station.
11. The mutual aid station transmits the audio to the subscribers.
If the dispatcher tries to transmit on a busy channel, a busy LED illuminates at the console.
Figure 6-2 Mutual Aid with Colocated CEB - Outbound Call
6-4 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Mutual Aid with CEBs at the Master Site
Mutual Aid with CEBs at the Master Site

Figure 6-3 illustrates a configuration where the mutual aid base stations are located at an ASTRO 25 Repeater
site and the CEBs are located at the master site. Note that the connections between the DIUs and the master
site CEB are identical to those between the DIUs and the CEB at the remote site. The audio routing
mechanism between the repeaters and the DIUs is the main difference in the two configurations.
At the RF site, the audio from the mutual aid base stations is connected to LDSRU interfaces
in a channel bank and transported through the system infrastructure together with the
trunked system data (control, audio, management).
The Digital Access Cross-connect Switch (DACS) at the master site routes the mutual aid time slots to a
channel bank and the ASTRO information to the WAN switch. The channel bank decouples the time slots
from the T1 interfaces and delivers the mutual aid ASTRO data to the appropriate low delay sub rate unit
(LDSRU) interface. Each LDSRU interface delivers its ASTRO data to a dedicated DIU.
Audio processing by the DIUs and CEBs, for outbound and inbound calls, is the same as previously
described. The only difference is in the audio routing through the infrastructure.
Figure 6-3 Master Site CEB with Digital Mutual Aid
6881009Y05-O April 2004 6-5

Digital Mutual Aid Equipment Chapter 6: ASTRO 25 Systems and Mutual Aid
Digital Mutual Aid Equipment

This section describes the STR 3000 digital mutual aid station, the DIU 3000, and the channel banks.
STR 3000 Digital Mutual Aid Station
The STR 3000 mutual aid station supports the following features:
Two transmit modes from the console or the subscribers, clear CAI digital voice and
encrypted CAI digital voice. The encrypted mode supports DES-OFB and AES
Coverage of the 700 MHz public safety band which currently consists of 764-776
MHz transmit range and 794-806 receive range
Repeater operation only (does not support simulcast or voting systems)
C4FM modulation in 12.5 kHz channel bandwidths
CSS can be used to configure a single transmit Network Access Code (NAC), a single
receive NAC, repeat or base station operation, and console priority
Software Download Manager upgrade capability
Console receive and transmit interfaces using a V.24 port
Repeater set up and knockdown control from a console
A standard cavity combiner with 250 kHz transmitter to transmitter spacing
12 transmitters maximum per antenna
The Radio Frequency Distribution System (RFDS) consists of a preselector, Receive Multicoupler
(RMC), Transmit circulators, transmit combiner and a Power Monitor Unit (PMU).
6-6 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Components
Figure 6-4 STR 3000 Digital Mutual Aid Station
Components
The 700 MHz STR 3000 is similar to the simulcast STR 3000 base radio from the hardware perspective.
Differences exist in the receive and transmit modules to enable the mutual aid station to process frequencies
in the new frequency band. The modules and their function are listed in Table 6-1.
Table 6-1 700 MHz Repeater Modules
Module Description
-48 VDC Power Supply Receives -48 VDC as its input and converts it to the
voltages required by the other repeater modules.
Exciter Generates the transmit frequency and provides the
modulation functions for the repeater. It supplies
the modulated signal to the power amplifier.
Power Amplifier (PA) Provides the transmitter functions for the repeater
in conjunction with the exciter. The PA accepts the
low-level modulated RF signal from the exciter and
amplifies the signal for transmission through the
RF output connector.
Control Module Provides signal processing and operational control
for the repeater modules.
Receiver Provides detection, amplification, conversion, and
filtering of incoming signals.
6881009Y05-O April 2004 6-7

Control Module Chapter 6: ASTRO 25 Systems and Mutual Aid
The 700 MHz STR 3000 requires an external 5 MHz frequency reference. The reference can be provided
by an internal frequency standard in the PSC 9600 site controller when the mutual aid equipment is
colocated with an ASTRO 25 Repeater site or by the TRAK 9100 when the mutual aid equipment is
colocated with a simulcast prime site or remote subsite. Equipment that can provide a stable 5 MHz
reference is a requirement for standalone, 700 MHz, mutual aid installations.
Control Module
The DB9 connector on the control module is the programming interface for the repeater. A
computer with Configuration/Service Software (CSS) is connected through this serial port to
configure the repeater with the appropriate operating parameters.
The control module monitors the functions of other repeater modules. The LEDs on the front
panel indicate the status of the monitored modules. The CTL LED on the front panel light
control module and Table 6-2 describes their function.
Figure 6-5 Control Module and LED Indicators
Table 6-2 Control Module LED Description
Normal
State
On Green On On The repeater is receiving power.
Fail Red Off On A station failed. If the STR 3000 is exhibiting a failure
that prevents it from operating, use CSS to review the
radios status report to determine which module failed.
Blinking on once The external frequency reference failed. It also indicates
per second. if the receiver or transmitter are not locked on frequency.
Blinking on twice The station is being configured.
per second.
6-8 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Digital Interface Unit
Table 6-2 Control Module LED Description (Continued)

Normal
State
SVC Amber Off Blinking on once The repeater is in service mode.
per second.
Blinking on twice The transmitter is inhibited.
per second.
CTL Green On Blinking off for An inbound signaling packet arrived.
250 milliseconds.
Rx Green On On The receiver is active.
PA Green On On The base radio is transmitting at programmed power
levels.
Blinking Power has dropped below the programmed level.
Blinking on once The receiver is inhibited.
per second.
Blinking on twice The transmit function (Exciter, PA) is inhibited.
per second.
Blinking Software download is in progress.
continuously.
V24 Green On On The V.24 link is active.
Blinking The V.24 link failed.
Digital Interface Unit
The ASTRO Digital Interface Unit (DIU 3000) (see Figure 6-6) provides the interface between the
700 MHz mutual aid RF equipment and the dispatch console subsystem.
The DIU performs several important functions:
Voice coding (vocoding) from analog to ASTRO digital and ASTRO digital to analog.
CENTRACOM Digital Link Interface The CENTRACOM Digital Link Interface
is an option, which, in conjunction with the ACIM (ASTRO Console Interface
Module) installed in the CENTRACOM, enables the CENTRACOM analog
console to use ASTRO signalling (such as PTT ID).
Embedding advanced conventional feature signaling, station keying, and other control
information from the console into ASTRO voice frames for transmission to the repeaters.
The DIU also separates the embedded signaling from the voice frames of inbound calls
and sends them to the console through the ACIM-BIM interface.
Suppling encryption and decryption functions (optional) for console audio.
6881009Y05-O April 2004 6-9

Digital Interface Unit Chapter 6: ASTRO 25 Systems and Mutual Aid
Dual Mode Operation In a digital mutual aid system, the DIU can transmit in two
modes through control by the ACIM link: clear digital and coded digital. The DIU can
also auto-receive in these modes, but can indicate only two mode choices at the console.
The DIU can be programmed to indicate one of the following choices:
ASTRO-Coded/ASTRO-Clear
ASTRO-Clear/Undefined
Full Duplex Operation The DIU can handle both inbound and outbound signals.
Multikey Capability Up to eight encryption keys can be selected by a console position. These
keys are used to encode outbound calls from a console and to decode inbound transmissions.
Compliance with FIPS 140-1 Security Requirements The DIU can be programmed through
Radio Service Software (RSS) to restrict access to encryption/decryption services.
Alert Tones When an encryption option is enabled, the DIU alerts the console operator if
there is key failure or when the operator tries to transmit in the clear mode.
Keyboard and LCD The DIU has a keyboard and an LCD that greatly facilitate installation
and maintenance operations. The keyboard is also used for controlling access to encryption
services from analog consoles that do not comply with security requirements of FIPS 140-l.
Handset Support The optional handset facilitates installation and maintenance
operations (check inbound/outbound audio, perform test transmissions, and provides
intercom function with other ASTRO equipment).
AC Battery Backup The DIU supports an external battery as a backup
for the AC power supply.
External Terminal Interface The DIU provides an RS-232 interface that can be used to
connect a diagnostic printer, a terminal or a computer running RSS. The interface is accessible
through an RJ45 connection in the front. The computer running RSS is used to program DIU
parameters, perform in-box diagnostics and retrieve stored diagnostic information.
Built-In Test Capability This capability allows the DIU to perform self-tests at
power-on and during operation. Detected failures are stored in memory and can either be
displayed on the DIU LCD or retrieved through the RS-232 interface.
Mounting Flexibility The DIU is available in a standard 19" rack or desktop.
6-10 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Components
Figure 6-6 DIU - Front View
Components
The DIU includes the following internal components:
Control and Audio Processing A host microprocessor contains and runs all the DIU
application and protocol software. It is connected to and controls four other microprocessors:
I/O controller
Two Digital Signal Processors for signal processing
Encryption Controller
Another microprocessor is connected indirectly to the host through the I/O controller.
This microprocessor is used to interface the keyboard and display (LCD).
An internal audio switch The audio switch provides all the internal audio
routing between the various DIU analog sections.
Power supply Power input to the DIU is 15 V DC.
Wireline Interface (WLI) Boards There are two WLI boards in the DIU. One board
is used as the interface between the DIU and the analog console, the other WLI board
interfaces an analog base station to the DIU (not used in an ASTRO 25 mutual aid
system). Each WLI board includes a transmit and receive section.
Encryption Adaptor Board This board serves as an interconnection adaptor
between the DIU and the Encryption cartridge. It also houses the 3 Volt Lithium
battery used for the clock and RAM power backup.
6881009Y05-O April 2004 6-11

Channel Bank Chapter 6: ASTRO 25 Systems and Mutual Aid
Communication Board The Communication board supports three serial links. One
link is dedicated to the base station interface (V.24 link). A second link is used as the
CENTRACOM signalling link. The third link is reserved for future use.
Channel Bank
A specifically designed channel bank can be used in sites that have digital mutual aid stations. The
channel bank can provide access to High Speed Unit (HSU) interfaces for site router connections and
low delay sub rate unit (LDSRU) digital interface ports for digital mutual aid stations.
Figure 6-7 Channel Bank
CPU Card
6-12 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Wide Area Network Cards
Performs primary-secondary CPU arbitration. In a system with redundant CPU cards,

the two CPU cards communicate their status to each other. If the primary CPU card
fails, the redundant card takes control of the channel bank.

Wide area network (WAN) cards (Figure 6-8) manage the flow of data to and from the network.
They are also the point of T1 or E1 termination and generate or receive clocking. Both CSU and
DSX modules are used to connect to T1 facilities operating at 1.544 Mbps.
Interface Card
The interface card is always present, occupies the slot furthest to the left in the rear of the channel bank, and
controls many critical functions in the system. It provides interfaces to external control devices, terminates all
T1 and E1 WAN links, and holds the nonvolatile RAM. The interface card includes an internal modem.
The interface card provides the means to select the clock source to be used internally by the channel bank.
Computer Port The RS232 port is used for direct reporting of alarms to an outside device.
6881009Y05-O April 2004 6-13

Low Delay SRU Card Chapter 6: ASTRO 25 Systems and Mutual Aid
Node Port The RS485 node port allows you to activate external alarms to
Modem Connector The modem port is used to connect the Interface cards internal
dial modem to a standard telephone line. This port may be used either to log into the unit
from a remote VT100 terminal or to send system alarms to a remote device. The internal
modem is an asynchronous CCITT V.22 bis modem. It allows remote access to the terminal
interface and automatic logging of alarm messages to a remote device.
The modem communicates at 2.4 kbps using 8 data bits, one stop bit and no parity. As with a
local terminal, the network operator must dial in using a VT-100 compatible terminal.
If an operator is logged on to the system with a local terminal when a modem call is
received, the operator will automatically be logged off the system and will not be able
to restore local access until the modem connection is broken.
Low Delay SRU Card

In an ASTRO 25 site repeater, the LDSRU card is used to interface the mutual aid repeaters
to the ASTRO 25 system. Each card has 10 interfaces for external equipment. The LDSRU
card in a mutual aid channel bank performs two functions:
It provides the interface between the ASTRO audio coming from the repeater
and the assigned time slot in the specified WAN card.
It recovers the signal from a WAN card time slot and delivers it to a digital mutual aid repeater.
HSU Card
The High Speed Unit (HSU) card in the channel bank is used to interface the remote subsite router
to the T1 network. It is a high speed communication card used to transmit the network management
information between the subsystem and the master site. A DACS is used at the master site to reroute the
network management information and the mutual aid audio to their proper destinations.
Analog Mutual Aid

Analog mutual aid is supported in all ASTRO 25 RF subsystems. Equipment can

be in the VHF, UHF, or 800 MHz bands.
The following sections describe the implementation of analog mutual aid in ASTRO 25 Repeater sites and
Simulcast subsystems. As a general rule, the number of analog mutual aid repeaters is limited to five when the
transport resources are shared between the trunked ASTRO 25 traffic and the mutual aid analog audio.
6-14 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System ASTRO 25 Repeater Sites
ASTRO 25 Repeater Sites
ASTRO 25 Repeater sites require the addition of a channel bank at the site to provide an
access point to mutual aid audio. The RF equipment can be conventional QUANTAR
base stations or the customers own RF resources.
A standard QUANTAR base station can be used at sites that require mutual aid support. These
base station requires the modules shown in Figure 6-9.
Figure 6-9 QUANTAR Mutual Aid Base Station
The receiver, power supply, exciter, and power amplifier function the same way as those described in the
repeater section of the ASTRO 25 Repeater site. The Station Control Module (SCM) can be the same as that
used in the ASTRO 25 Site Repeater or it can be an SCM without the Ethernet interface support.
Wireline Interface Board

The Wireline Interface Board (WIB) serves as the interface between the customers analog
facilities and the station equipment. Each WIB contains circuitry to interface with a
variety of analog configuration and signal types.
In an ASTRO 25 system, the WIB is present only in QUANTAR stations used for mutual aid.
The Wireline Interface Board contains the following circuitry:
Audio and Data Circuits The WIB provides a number of voice and data
circuits which interface with the channel bank.
Microprocessor The WIB microprocessor provides overall control of the WIB
operation, communicates with the Station Control Module microprocessor, and provides
monitoring and control for a variety of on board I/O circuits.
6881009Y05-O April 2004 6-15

Channel Bank Chapter 6: ASTRO 25 Systems and Mutual Aid
Peripheral Application Specific IC (PASIC) In general, the PASIC is responsible

for accepting PCM voice information and routing the information to the proper
destination (that is, from channel bank to station, and from station to channel bank). It
injects and retrieves PCM voice signals into/from the Time Division Multiplex (TDM)
bus that connects the WIB to the Station Control Module.
Channel Bank
A specifically designed channel bank can be used in sites that have analog or digital mutual
aid stations. The channel bank can provide access to HSU interfaces for site router connections
and 4-wire analog interface ports for analog mutual aid stations.
Figure 6-10 Channel Bank
CPU Card
6-16 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Wide Area Network Cards

Performs primary-secondary CPU arbitration. In a system with redundant CPU cards,
the two CPU cards communicate their status to each other. If the primary CPU card
fails, the redundant card takes control of the channel bank.

WAN cards (Figure 6-11) manage the flow of data to and from the network. They are also the
point of T1 or E1 termination and generate or receive clocking. Both CSU and DSX modules
are used to connect to T1 facilities operating at 1.544 Mbps.
Interface Card
The interface card is always present, occupies the slot furthest to the left in the rear of the channel bank, and
controls many critical functions in the system. It provides interfaces to external control devices, terminates all
T1 and E1 WAN links, and holds the nonvolatile RAM. The interface card includes an internal modem.
The Interface card provides the means to select the clock source that is to be used by the channel bank.
Computer Port The RS-232 port allows for direct reporting of alarms to an outside device.
6881009Y05-O April 2004 6-17

4-Wire Card Chapter 6: ASTRO 25 Systems and Mutual Aid
Node Port The RS-485 node port allows you to activate external alarms to
Modem Connector The modem port is used to connect the Interface cards internal
dial modem to a standard telephone line. This port may be used either to log into the unit
from a remote VT-100 terminal or to send system alarms to a remote device. The internal
modem is an asynchronous CCITT V.22 bis modem. It allows remote access to the terminal
interface and automatic logging of alarm messages to a remote device.
The modem communicates at 2.4 kbps using 8 data bits, one stop bit and no parity. As with a
local terminal, the network operator must dial in using a VT-100 compatible terminal.
If an operator is logged on to the system with a local terminal when a modem call is
received, the operator will automatically be logged off the system and will not be able
to restore local access until the modem connection is broken.
4-Wire Card
The 4-wire card in a mutual aid channel bank performs two functions:
It translates an analog signal to a digital bitstream (PCM) and places the digital
signal in a specified WAN card time slot.
It recovers the PCM signal from a WAN card time slot, converts the digital signal to an
analog signal, and delivers the signal to an analog mutual aid repeater.
The 4-wire card is used to interface the mutual aid repeaters to the ASTRO 25 system. Each card has eight
interfaces for external equipment. ASTRO 25 Repeater sites support up to five analog mutual aid repeaters.
HSU Card
The HSU card in the channel bank is used to interface the remote subsite router to the T1 network.
It is a high speed communication card used to transmit the network management information
between the subsystem and the master site. A DACS is used at the master site to reroute the network
management information and the mutual aid audio to their proper destinations.
ASTRO 25 Repeater Site Mutual Aid Configurations

This section presents diagrams of ASTRO 25 Repeater Site configurations with analog mutual aid channels.
6-18 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System ASTRO 25 Repeater Site With 18 Channels and Single Site Link
ASTRO 25 Repeater Site With 18 Channels and Single Site Link
In this configuration (Figure 6-12) the channel bank provides a V.35 interface for the site router,
4-wire interfaces for analog mutual aid stations, and the WAN interfaces necessary to transport the
subsystem information to the master site. If conventional ASTRO stations are used for mutual aid,
the channel bank also includes LDSRU interfaces for the ASTRO audio.
The WAN card is programmed to carry the ASTRO 25 traffic and the mutual aid audio in separate
time slots. The digital cross-connect switch at the master site is used to route the mutual aid analog
audio to a channel bank and the trunked ASTRO 25 traffic to the WAN switch.
Figure 6-12 ASTRO 25 Site Repeater Subsystem With 18 Channels and Single Site Link
ASTRO 25 Repeater Site With 28 Channels and Single Site Link
This configuration (Figure 6-13) provides the resources necessary for greater trunked call capacity. It
supports the installation of up to 28 ASTRO 25 Site Repeaters in the subsystem.
Impact on mutual aid by the increased number of trunked repeaters at the subsystem is limited to the
bandwidth resources needed between the subsystem and the master site.
6881009Y05-O April 2004 6-19

ASTRO 25 Repeater Site With 28 Channels and Redundant Site Links Chapter 6: ASTRO 25 Systems and Mutual Aid
Figure 6-13 ASTRO 25 Repeater Site With 28 Channels and Single Site Link
ASTRO 25 Repeater Site With 28 Channels and Redundant Site

Links
Figure 6-14 shows an ASTRO 25 Repeater Site with dual site routers and a single channel
bank configuration. The two site routers provide protection for the ASTRO 25 traffic against
single point failures. As shown in the diagram, one of the site routers can share the transport
resources (channel bank and T1s) with the mutual aid audio.
6-20 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Simulcast Subsystems and Mutual Aid
Figure 6-14 ASTRO 25 Repeater Site With 28 Channels and Redundant Site Links
It is possible to place a channel bank on each T1 link to the master site on ASTRO 25 Repeater
sites with dual site routers. This configuration can be used in situations where multiple mutual aid
channels are present at the site and it is desired to route the analog audio through different paths to
the master site. It is important to note that this configuration not only requires an additional channel
bank at the site, but also doubles the DACS port requirements per site.
Simulcast Subsystems and Mutual Aid

Simulcast subsystems support mutual aid at the prime site and remote subsites. Channel bank
resources are already available at both, the prime site and the remote subsites, making it feasible to
provide the connections and transport mechanism for mutual aid repeaters.
The equipment used in simulcast subsystems to support mutual aid is similar to the equipment
described in the ASTRO 25 Repeater site section. Conventional QUANTAR base stations can be
used as the RF resource; analog audio cards can be installed in the channel bank. The following
figures represent configurations supported in ASTRO 25 systems.
6881009Y05-O April 2004 6-21

Simulcast Subsystems and Mutual Aid Chapter 6: ASTRO 25 Systems and Mutual Aid
Figure 6-15 Simulcast Prime Site With Single Repeater Mutual Aid
The configuration in Figure 6-16 displays a system where single base stations are used for mutual
aid. The four wire interface in the channel bank can accommodate up to eight analog sources. Each
mutual aid audio source requires a time slot in the T1 to the master site. ASTRO 25 traffic sharing
the same T1 is routed in different time slots than the mutual aid audio.
6-22 6881009Y05-O April 2004

Figure 6-16 Simulcast Prime Site With Conventional Mutual Aid Simulcast System
ASTRO 25 simulcast subsystems can support conventional mutual aid simulcast systems. The TRAK 9100
present at the prime site and the remote subsites can provide the frequency reference required for simulcasting
audio. Analog comparators are used to provide the voting mechanism required in the simulcast operation.
As with the single base station, mutual aid system, ASTRO 25 traffic and mutual aid audio are
independently transported to the master site using the channel bank and T1 resources.
6881009Y05-O April 2004 6-23

Figure 6-17 Simulcast Prime Site With Redundant Site Routers and Mutual Aid
This configuration enhances the ability of the ASTRO 25 simulcast subsystem to stay in wide
area trunking mode. It has no impact on the mutual aid system.
6-24 6881009Y05-O April 2004

Figure 6-18 Simulcast Remote Subsite With Mutual Aid
The channel bank at the simulcast subsystem remote subsite can support mutual aid with the addition of
4-wire interfaces. Figure 6-19 shows one of the possible channel bank card configurations.
The HSU card (slot 3 from left to right) in the channel bank is used to interface the remote subsite
router to the T1 network. A DACS is used at the master site to reroute the network management
information and the mutual aid audio to their proper destinations.
The 4-wire interface card (slot 5) at the channel bank converts the analog mutual aid audio to PCM and
delivers that audio to an assigned time slot in a T1. The WAN card formats the T1 and transmits the entire
stream, through the channel banks interface card, to the prime site through the transport medium.
The LDSRU cards (slots 8 and 9) are used to interface the remote site simulcast base radios to
the channel bank. Each card has 10 interfaces for external equipment.
6881009Y05-O April 2004 6-25

Figure 6-19 Channel Bank - Simulcast Subsite With Analog Mutual Aid
ASTRO 25 traffic and mutual aid audio only share the transport resources.
6-26 6881009Y05-O April 2004

Chapter
7
Databases, Servers, and Controllers

This chapter contains the following topics:

"Radio System Databases" on page 7-1
"How the System Uses Data" on page 7-2
"Server Descriptions" on page 7-15
"Server Interaction" on page 7-18
"Server Failure" on page 7-20
"Introduction to the Administration Menus" on page 7-24
Radio System Databases

The system uses a variety of databases to provide communication services to individual users. Configuration
data for users, talkgroups, and the system infrastructure are stored in these databases. Other types of
information stored include system performance and fault data. The databases are the organizing element
that transforms the computers and radios in the system into a versatile communications platform.
System Data Requirements
The system collects data for use at the system, zone, and site levels. The various databases
include information related to the following:
Subscriber Access Control This data includes all the access control information
for the subscriber units. Individual user permissions are configured through profiles
that define characteristics common to a group of users.
Infrastructure This data includes all the hardware, links, slots, connections, and
configuration information necessary to support call processing.
Alias This data provides the mapping of names to IDs.
6881009Y05-O April 2004 7-1

How the System Uses Data Chapter 7: Databases, Servers, and Controllers
Statistical This data provides information on the numbers and types of calls,
resource assignments (such as channels), busies, and rejects. This information
can then be gathered to generate reports.
Affiliation This data provides a listing of radio to talkgroup associations and site locations.
Fault This data provides state or diagnostic information on IP-managed devices.
How the System Uses Data

The system collects data for use at the system, zone, and site levels. The various
databases include information concerning:
User and talkgroup profiles

Statistical and trending information
Configuration and fault management information
Call processing information
This section includes the following high-level overviews of the types of data and how they are used:
Subscriber information
Home Location Register (HLR) and Visitor Location Register (VLR)
call processing information
Alarm and alert information
Alias database and console database manager information
Statistical data
Subscriber Information
User profiles are established to define those user characteristics most common to a particular type of user.
When a new user is entered into the system, the user is assigned a user profile to take on the common
characteristics associated with the profile, then characteristics are changed or unique characteristics
can be established to complete the individual user profile, as necessary.
Talkgroups are established by a similar method. Talkgroup profiles are created to define talkgroup
characteristics most common to a particular type of talkgroup, then the characteristics are changed or
unique characteristics are added and saved as a new talkgroup, as necessary.
This information is initially entered into the User Configuration Manager (UCM) as a single point of
entry to avoid duplicating effort or generating mismatched databases. Afterwards, the information
is replicated to each zone database server in the system for use by the zone.
7-2 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Home Location Register
Figure 7-1 shows the flow of information when a subscriber record is added.
Figure 7-1 Subscriber Information Flow
Home Location Register

A Home Location Register (HLR) is a zone controller and packet data router database. Because the home
zone is responsible for controlling all voice group calls for a talkgroup, the zone controller coordinates
the assignment of resources based on the home zone map and the information stored in its HLR and
Visitor Location Registers (VLR). The Packet Data Router (PDR) uses the HLR in a similar manner.
See "HLR and the Packet Data Gateway" on page 7-4 HLR and the Packet Data Gateway.
When an ASTRO 25 system is first installed, home zone subscriber and talkgroup information is
entered into the User Configuration Manager (UCM). When this data is entered for all the zones in
the system, each subscriber radio and talkgroup is assigned a home zone.
6881009Y05-O April 2004 7-3

HLR and the Packet Data Gateway Chapter 7: Databases, Servers, and Controllers
The UCM is a single point of data entry for the entire system to prevent any mismatched records.
Talkgroup information is entered in table format using ranges to divide and assign the available
talkgroup IDs to a home zone. For example, the talkgroup range from 80000001 to 80001024
can be assigned to Home Zone 1. Individual subscriber radio ID information is also entered in a
table format using ranges to divide and assign the total number of individual radio IDs to a home
zone. For example, individual radio IDs 1 to 2400 can be assigned to Home Zone 1.
The home zone information is then downloaded to each Zone Database Server (ZDS) in the system.
From each ZDS in the system (one ZDS per zone), only those records belonging to a particular zone
are transferred to that zones zone controller in the form of a HLR The exact same HLR is also
transferred to the PDR module in the PDG. The PDR module uses the HLR to process data calls in
a similar way that the zone controller uses the HLR to process voice calls.
A Home Location Register for each zone contains subscriber radio and talkgroup information
(home zone information) specifically designated for that zone. The Home Location Register
database includes the following information:
Privileges and capabilities of radios

Current zone location of radios
Talkgroup affiliation of radios
Capabilities of talkgroups
Current zone location of talkgroups
The HLR is made up of two components:
Group Home Locations Register (GHLR) stores information about groups.

Individual Home Location Register (IHLR) stores information about radio users.
HLR and the Packet Data Gateway
Using the HLR, the PDR module in the PDG processes mobility queries to support data
transport services in your ASTRO 25 communication system.
Mobility queries by the PDR are used to obtain subscriber radio status and zone affiliation information
used for data transport to a data device through a data capable subscriber. The PDR in the PDG
is updated with HLR information in a similar fashion as the zone controller.
Visitor Location Register
The Visitor Location Register (VLR) is a zone controller database containing information on all radios
currently affiliated to the sites at a zone. The VLR manages a local copy of zone-specific information for
individuals and talkgroups. This includes subscriber database information and site location information for
both the individual and the talkgroup. Each zone has an individual VLR (IVLR) and a group VLR (GVLR).
This relationship between the information in the User Configuration Server (UCS) and
the location registers is shown in Figure 7-2.
7-4 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System VLR and the Packet Data Gateway
Figure 7-2 UCS to Location Registers Relationship
VLR and the Packet Data Gateway

The zone controller updates the RNG module in the PDG with changes in the VLR database. Registration,
de-registration, site roaming and zone roaming, information is communicated from the zone controller
to the RNG for processing the data service requests from data capable subscriber units.
Alarm and Alert Information
FullVision INM can provide integrated fault information for a single zone system or from any and all
zones in a multiple zone system. The server monitors faults from each of the zones and local area
network equipment (hubs, switches, and routers). An optional MOSCAD plug in allows FullVision
INM to show a subset of MOSCAD alarms from equipment that normally would not report to
FullVision INM, such as microwaves and environment monitoring systems.
6881009Y05-O April 2004 7-5

Alias Database and Console Database Management Information Chapter 7: Databases, Servers, and Controllers
Alias Database and Console Database Management Information
Each mobile radio and each talkgroup have a unique eight-digit ID number. Each object on the
CENTRACOM Elite dispatch screen that permits a dispatcher to establish communication with a talkgroup
or radio resource is also assigned a unique ID and therefore can be assigned an alias. An alias is used to
assign a more easily recognizable and memorable designation, such as a name, to the IDs.
Talkgroup aliases can be entered in the CENTRACOM Gold Elite dispatch system in one of two ways:
Locally at the Elite dispatch system server through the Console Database Manager (CDM)
Through a remote download from the ZDS to the CDM
Individual IDs residing at the UCS can also be entered in the CENTRACOM Gold
Elite dispatch system in one of two ways:
Locally at the Elite dispatch system server through the Alias Database Manager (ADM)
Through a remote download from the ZDS to the ADM
Any other alias information, such as page group aliases, specific to a dispatch system is entered
through the CDM and resides only in that dispatch subsystem.
More detailed information on Alias download is provided in the following manuals:
CDM alias download: CENTRACOM Gold Series, Console Database

Manager Users Guide (68P81094E45)
ADM alias download: CENTRACOM Gold Series, Alias Database Manager
Users Guide (68P81094E45)
Statistical Data
The system organizes statistical information into reports.

The data is collected based on groups specified by the administrator. The groups are based on
object type, time interval, and number of intervals. For example, a collection group may be defined
to collect statistics about talkgroups. A single collection group will not, however, be capable of
collecting statistics about both sites and zones; two separate collection groups would be needed.
Also, a collection group will collect statistics for a single collection interval.
Two types of reports are supported: Dynamic and Historical. Dynamic reports are updated for each interval
selected by the user. Historical reports are static. Once the Historical report is generated, it does not change.
7-6 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System System Databases
System Databases

Various databases provide support for the ASTRO 25 wide area trunking communications system.
System Databases
ASTRO 25 builds on the concept of a wide area trunked, multiple-zone communications system. A zone
contains a number of RF sites connected to a master site, which contains the zone management computers, the
zone controller, and the audio switch. Zones are linked together through a high-speed wide area network
(WAN) to provide virtually seamless communications throughout the entire system coverage area.
This section describes the individual databases, the relationship between the databases, and the
way the system uses the data. The following databases are covered here:
System Statistics Server (SSS) database This database is used to summarize and
report on usage statistics for the system. It is used only in multizone systems.
User Configuration Server (UCS) database This database contains subscriber
configuration data and user configuration data.
Zone database This database resides on the Zone Database Server (ZDS)
and contains system and subscriber information.
Zone Local database This database is a flat text file that resides on the zone controller
and contains the infrastructure information for that particular zone.
Zone Statistics Server (ZSS) database This database is used to summarize
and report on usage statistics for the zone.
Console Database Manager (CDM)/Alias Database Manager (ADM) The databases
used with the CENTRACOM Gold Elite Dispatch system.
FullVision INM database FullVision INM is the software tool used to analyze
alarm and state data for fault and performance management.
Air Traffic Router (ATR) The ATR gathers statistics about call control traffic on the
system from the zone controller and passes the information along to the ZSS and the SSS.
The ATR also generates the ATIA stream used by application such as Zone Watch.
System Statistics Server Database
Statistics concerning resource usage and allocation are kept in the SSS database. As an administrator, you will
use reports generated from system statistics to make decisions concerning resource usage and allocation.
The SSS database is used in conjunction with the system reporting tools to provide Historical
reports. Historical reports are static and provide a snapshot of system usage for a specified time
interval. Historical reports can be manually or automatically generated.
Statistics are kept for sites, channels, zones, talkgroups, and users. Statistics are kept
on call duration, busies, and call counts.
6881009Y05-O April 2004 7-7

User Configuration Server Database Chapter 7: Databases, Servers, and Controllers
User Configuration Server Database
The User Configuration Server (UCS) stores information about subscribers, talkgroups, critical
sites, Adjacent Control Channels (ACC), interzone control paths, and user security information at
a system level. Group and Unit ID home zone assignments are also made at the UCS level. The
UCS provides the benefit of a single point of entry for ease of use, with automatic propagation
throughout the system to support distributed call processing.
The zone database contains all of the information entered at the UCS and, therefore, can
be used as a backup to restore system-level data.
Zone Database
The zone database, located on the ZDS, stores a replicated copy of the UCS database.
Home Location Register
The Home Location Register (HLR) stores the current zone location of any registered individual
or affiliated group members whose configuration information is stored in the HLR. The location
information in the HLR is continually updated as radios are turned on and off, roam the system,
and switch between talkgroups. The HLR resides in the zone controller.
Visitor Location Register
Each zone has a Visitor Location Register (VLR) to address the radios and talkgroups which are currently
active in the zone. The VLR stores access configuration information for both individuals and groups
along with their current site locations. The VLR resides in the zone controller.
Zone Infrastructure Database
The Zone Infrastructure database, located on the ZDS, contains information about zone objects
such as ASTRO 25 Repeater sites, simulcast site controllers, and interzone communication
objects (the physical cards, paths, and audio slots).
7-8 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Zone Local Database
Figure 7-3 Information Flow for Infrastructure Record
Zone Local Database
The Zone Local database, located in the zone controller, is a simplified text file containing much of the same
infrastructure data that is found in the zone database. The primary reason that the local database exists is to
allow continued communications within a zone in the case of a failure resulting in a zone controller reset
while the zone database is not available. The local database allows the controller to provide wide area
services in default mode until the HLR and VLR are restored with records from the ZDS/UCS.
Zone Statistics Server Database
The Zone Statistics Server (ZSS) database takes information in the form of the Air Traffic
Information Access (ATIA) stream from the Air Traffic Router (ATR) and parses these records
to the Report Players, which run on the Network Manager client.
The zone-wide statistical information in the ZSS database summarizes call processing traffic.
The reports generated can be one of two types:
Historical These are static reports that cover a specific time interval. The amount of
historical information that can be recovered depends on the specified time interval.
Dynamic These reports are real-time, short term reports that are updated
for each interval of time selected by the user.
Console Database Manager/Alias Database Manager
Each zone has one Console Database Manager (CDM) and one Alias Database Manager (ADM). The
CDM allows profile changes to the console positions and talkgroup aliases. The ADM provides a
central location to store individual ID aliases used in the dispatch consoles.
Console Database
The Console database, located on the CENTRACOM Gold Elite server of each zone, stores
all the configuration and management information for the console clients, such as console
user profiles and window screen configurations. The dispatch consoles in the Elite subsystem
retrieve their configuration settings from the Console database.
6881009Y05-O April 2004 7-9

Alias Database Chapter 7: Databases, Servers, and Controllers
The CDM also stores talkgroup IDs and their aliases. This information can be programmed locally at
the CDM or downloaded from the ZDS. When a console receives a call from a talkgroup, multigroup, or
another console, the Elite dispatch screen will display a meaningful alias to the console operator.
Alias Database
The Alias database, which resides on the Elite console server, stores all the alias identifiers for
radio users and consoles. When a console receives a call from a radio user, it will show the alias
(such as Sgt. Smith), rather than the underlying radio or object ID.
Like the Console database, a master copy of the Alias database is stored in the Elite server. The alias
information can be programmed locally at the ADM or downloaded from the ZDS.
The FullVision INM server handles most fault management tasks for the system. The FullVision
INM server hosts the Hewlett Packard OpenView (HPOV) Network Node Manager, which is the
foundation upon which FullVision INM is built. Hewlett Packard Open View handles object discovery,
topology map generation and polling. The Motorola Router Manager is integrated with HPOV to manage
Motorola Network Routers. The Motorola MOSCAD system (optional) can integrated with FullVision
INM for monitoring alarms from a variety of devices including environmental sensors, uninterruptable
power supplies (UPS), channel banks, microwave gear, and antenna systems.
Air Traffic Router (ATR)
The Air Traffic Router (ATR) receives Air Traffic Information Access (ATIA) packets from the zone
controller. ATIA packets represent all of the call control traffic that occurs on the system. The ATR measures
and supplies statistics to the Dynamic Reports application. The ATR also collects and supplies the ATIA
information to the collection managers in the Zone Statistics Server (ZSS) and the System Statistics Server
(SSS). Figure 7-4 shows source and destination for the information recovered by the ATR
7-10 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Air Traffic Router (ATR)
Figure 7-4 Flow of Information to/from ATR
6881009Y05-O April 2004 7-11

Database Summary Chapter 7: Databases, Servers, and Controllers
Database Summary

Table 7-1 summarizes the pertinent information for each database, including the databases
function, how it is accessed, and the server on which it resides.
Table 7-1 Summary of Database Administration Functions
Database Server Function

UCS Database UCS Database Server The User Configuration Subsystem is used for subscriber
management as described in the following list:
Group and Unit ID home zone assignments are
made at the UCS level.
System-level security information and some
system-level parameters are set in the UCS.
Subscribers, talkgroups, critical sites, Adjacent
Control Channels (ACC), and Interzone Control
Path IDs are configured in the UCS.
Zone Database Zone Database Server All infrastructure configuration information for a specific
zone, along with a copy of the user configuration
information replicated from the UCS.
Alias Database CDM/ADM Server
CDM contains dispatch resource information that
includes talkgroup IDs and aliases.
ADM includes all aliases assigned to radios,
consoles, and other named entities.
Console Database CDM/ADM Server CDM contains configuration information for all dispatch
resource such as COIMS, AIMIs, ZAMBIs, Aux I/Os,
talkgroups.
Radio Configuration Manager Air Traffic Router Server The RCM database carries information that allows the
(RCM) Database user to perform several monitoring and control functions.
System Statistics Server System Statistical Server Used in conjunction with Historical Reports Player to
Database generate system-wide reports.
Zone Statistics Server Zone Statistical Server Used in conjunction with Historical Reports Player to
Database generate zone-wide reports.
Zone Local Database Zone Controller A copy of the local infrastructure database is downloaded
to the zone controller once the ZDS is populated with
the zones hardware configuration records. This copy
of the local infrastructure database is stored in the zone
controller to provide wide area communication in cases
where the zone controller needs to re-initialize without
having access to the ZDS.
7-12 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System System Servers
System Servers

Servers are computers that serve data to other computers and devices (clients). Servers are different
from client computers. In general, clients consume and manipulate information and resources,
while servers are providers of information and resources. In the ASTRO 25 system, there are
many servers and each has a specialized function or set of functions.
The ASTRO 25 servers perform the following functions:
Collect and display system fault information

Compile system statistics
Store records for users, infrastructure and radios
Manage call processing activities
6881009Y05-O April 2004 7-13

Hierarchical View Chapter 7: Databases, Servers, and Controllers
Hierarchical View

Table 7-2 shows the hierarchical listing of servers. Since the ASTRO 25 system is a functional hierarchy
(system-zone), visualizing how the servers fall into that hierarchy can be helpful.
Table 7-2 Hierarchical Listing of Servers
System-Level Servers Zone-Level Servers
User Configuration Server Zone controller (ZC)

(UCS)
(SSS)
One of the zone-level FullVision INM

servers also provides system-level
duties.
ATR
Console Database Manager /Alias Database
Manager Server (CDM/ADM)
Subsystem View

The ASTRO 25 system can be broken down into functional logical subsystems. Logical subsystems
are not pieces of equipment that you can point to; instead, logical subsystems are made up of
separate components that all contribute to a common system function.
Table 7-3 presents each subsystem and its servers.
7-14 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Server Descriptions
ASTRO 25 subsystems that do not contain servers are not shown.
Table 7-3 Subsystem Listing of Servers
Subsystem Servers
Private Radio Network Management
(PRNM) Subsystem
System Statistics Server (SSS)
One of the zone-level FullVision

INM servers also provides
system-level duties.
Call Processing Subsystem Zone Controller

Console Subsystem Console Database Manager /Alias Database Manager
(CDM/ADM) server
Server Descriptions

To work with the servers, an understanding of the physical design of each server, as well as its function in the
ASTRO 25 system, is essential. The following sections provide brief descriptions of each server in the system.
6881009Y05-O April 2004 7-15

User Configuration Server Chapter 7: Databases, Servers, and Controllers

The User Configuration Server (UCS) is a UNIX-based server. There is only one UCS per system and it is
generally located at the OSS site. The UCS makes it possible for management personnel to configure
home zone maps, management users, radios, talkgroups, critical sites, Adjacent Control Channels (ACC),
security information at a system-level, and other system-level parameters. This information is configured
using the User Configuration Manager (UCM) application and is saved in the UCS database.
The current UCS database and the home zone maps are distributed to each zone database server in
the system. In this way, an identical copy of the most up-to-date UCS database is available to each
zone at all times while at the same time ensuring that there is always an available copy to restore
the UCS database should it become necessary. Whenever changes are made to the UCS database,
the changes are sent to all of the Zone Database servers in the system.

The System Statistics Server (SSS) is a UNIX-based server. There is only one SSS per system,
located at the system OSS site. This server collects and stores system-wide statistical information
from each of the Air Traffic Routers (ATRs) for use by the system-level Historical Reports
application. The SSS is not used in a single-zone system.

The Zone Database Server (ZDS) is a UNIX-based server. The ZDS maintains the infrastructure
database for the zone, retains a replica of the current UCS database and Home Zone map, and exports
the subscriber information it received from the UCS to the zone controller. The ZDS also exports
the infrastructure information from its database to the zone controller where it is stored as the local
infrastructure database. This server passes commands and information from the Radio Control Manager
(RCM) application to the zone controller. The ZDS also performs all network management and fault
management polling of system devices to support the network management clients. The fault management
information that the ZDS collects is passed on to the FullVision INM server.
7-16 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Zone Statistics Server

The Zone Statistics Server (ZSS) is a UNIX-based server. There is one ZSS per zone. The ZSS collects and
stores zone-wide statistics regarding call processing traffic. It derives this information from the Air Traffic
Information Access (ATIA) stream supplied by the air traffic router. The ZSS serves up this information to
the Historical Reports application, which is used to map out zone resource usage and performance.
Air Traffic Router

The Air Traffic Router (ATR) is a UNIX-based server. The ATR receives air traffic information from the
zone controller, creates ATIA packets, and broadcasts them as the ATIA stream on the network. Various
clients listen to this stream to perform their functions. These clients include the ZSS, SSS, and ZDS; the
RCM application and Zone Watch application; Affiliation Display; and other third-party clients.

The FullVision INM server is a UNIX-based server. There is one FullVision INM server per zone. In
addition, one of the FullVision INM servers also fills the role of system-level FullVision INM server. The
FullVision INM servers are the heart of the fault management system. Using a network management client
workstation, you can use the FullVision INM application to access the fault management information that the
FullVision INM server obtains from the ZDS and other IP-managed devices in the system.
6881009Y05-O April 2004 7-17

Console Database Manager/Alias Database Manager Server Chapter 7: Databases, Servers, and Controllers
Console Database Manager/Alias Database Manager

Server

The Windows 2000-based Console Database Manager/Alias Database Manager (CDM/ADM)

server is part of the console subnet that is also home to a number of operator dispatch
workstations. Each zone has one CDM/ADM server.
The CDM allows personality changes to the Elite console positions and is capable of uploading configuration
information to the associated Console Operator Interface Modules (COIM).
The ADM provides a central alias database for Elite consoles.
The CDM/ADM server is not covered in this document. Refer to the following Control Center
documents for more information on the CDM/ADM server:
CENTRACOM Gold Series Alias Database Manager (ADM) Manual (68P81096E50)
CENTRACOM Gold Series Console Database Manager (CDM) Manual (68P81094E45)
Server Interaction

As with many components of the ASTRO 25 system, the system servers are highly interdependent; they
rely heavily on each other to supply critical data in support of their individual functions.
Figure 7-5 shows a high-level flow of information between the servers in a ASTRO 25 system. Each
interaction is numbered. See Table 7-4 for definitions of each of the numbered interactions.
7-18 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Server Interaction
Figure 7-5 Server Interactions
Table 7-4 Server Interactions Defined
No. Server Interaction

1 UCS Database Restore/Replication/Synchronization between the UCS and the ZDS. This is performed
automatically at predefined times or can be user-initiated from the database administration menus.
2 Subscriber (subset of UCS database) and infrastructure database export from the ZDS to the zone
controller. Diagnostic and fault information, including fault information proxied for other devices are
sent through this link to the ZDS.
3 Live call data is passed from the zone controller to the ATR. Radio user and RCM commands and
information are sent through this link.
4 Statistical data is sent from the ATR to the ZSS.
6881009Y05-O April 2004 7-19

Server Failure Chapter 7: Databases, Servers, and Controllers
Table 7-4 Server Interactions Defined (Continued)

No. Server Interaction
5 Zone statistical data is sent from the air traffic router to the SSS.
6 Call control information is sent from the zone controller to the Telephone Interconnect server. Telephone
Interconnect fault information is passed to the zone controller.
7 Call control information is passed between the zone controller and a simulcast site controller.
8 FullVision INM derives listing of system objects from data on the ZDS. Traps and polled device status
information from all managed devices is sent from zone database server to the FullVision INM server.
Device status information is derived from Simple Network Management Protocol (SNMP) agents and
MOSCAD.
9 Updated alias and configuration information is passed between the zone database server and the
CDM/ADM server.
10 Configuration data is passed from the ZDS to the ATR (for example, object aliases). Fault events are sent
to the ATR. Configuration data for the Dynamic Shared Services Algorithm (DSSA) is sent to the ATR.
Telephone Interconnect call termination records are sent to the ZDS.
11 Represented by gray dotted lines on illustration: Polling paths between the ZDS and all managed devices.
This includes all illustrated relationships, as well as the ASTRO 25 Repeaters, simulcast base radios,
Ambassador Electronics Bank (AEB), and simulcast comparators. This is how SNMP agent data and
trapped alarm information from these devices is acquired by the Zone Database Server for distribution to
the FullVision INM server.
12 Default subscriber records are sent to UCS by all zone controllers.
Server Failure

Each ASTRO 25 server performs different duties or carries specific data. The impact of server failure on the
rest of the system is dependent on the server that fails and the systems state at the time of the failure.
7-20 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Server Failure
Table 7-5 illustrates the system capacity lost upon failure of each type of server.
Table 7-5 Capacity Lost When Servers Fail
Subsystem Server Capacity Lost

Network Management User Configuration Server
Prevents the UCS database restore/replication process
Subsystem
from occurring.
Subscriber information cannot be edited, default
subscriber records are not created, and home zone maps
cannot be modified or viewed.
System-level parameters cannot be changed with the
User Configuration Management (UCM) application.
Synchronization of infrastructure changes made at the
ZDS will not be made until the UCS recovers.
The ability of the system to process call requests

and assignments is not affected since the zone
controllers can utilize the information in their
HLR/VLRs to handle call processing during this
type of failure.
System Statistics Server Prevents the viewing of system-wide statistics until the server
is available. ATR will buffer the ZDS data for 8 hours. If the
SSS becomes available during that time, it is able to collect and
store the system-level statistics from the time it was down.

type of failure.
6881009Y05-O April 2004 7-21

Server Failure Chapter 7: Databases, Servers, and Controllers
Table 7-5 Capacity Lost When Servers Fail (Continued)

Results in the loss of most fault management functionality;
zone configuration management, affiliation display; UCS
database restore from the affected zone, UCS database
replication to the affected zone; and RCM functionality.
Domain Name Server (DNS) services are lost.
Users may be able to switch to a different ZDS at the
login prompt to recover network management application
access to other zones.

type of failure.
Prevents the viewing of zone-wide historical and statistics.
System-level statistics from the zone are unavailable.
ATR will buffer 8 hours of data. If the ZSS recovers in
this time, then no statistical information will be lost. If the
ZSS recovery takes more than 8 hours, only the last 8
hours of data will be available.

type of failure.
7-22 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Server Failure

Air Traffic Router
The ATIA packet data and zone statistics are no longer
available.
Devices that are dependent on the ATIA stream are
affected.
Zone statistics upload to the ZSS and SSS are interrupted.
Consolidation of zone and system statistics is delayed
until the ATR recovers, or 8 hours elapse.
Affiliation data is unavailable for the zone. Dynamic
Reports are unavailable. ATIA Log Viewer is unavailable
(cannot access log files). The Affiliation Display
application becomes unavailable. Zone Watch application
data becomes unavailable.

type of failure.
Results in the loss of FullVision INM fault/network
management functionality for the zone.
If this server is also performing the system-wide
FullVision INM server role, system-wide fault viewing
will be disabled in every zone; the remaining zones with
FullVision INM capability are only able to view their own
fault management information.

type of failure.
Call Processing Zone Controller
ASTRO 25 systems are installed with redundant zone
Subsystem
controllers. If the active zone controller fails, all sites in
the zone go into site trunking mode until the switch to the
redundant zone controller is completed.
Fault management is unavailable for devices whose fault
management information is proxied by the active zone
controller.
6881009Y05-O April 2004 7-23

Introduction to the Administration Menus Chapter 7: Databases, Servers, and Controllers

Console Subsystem CDM/ADM Server The ability to configure/reconfigure the consoles is lost.
Call processing is not affected.

Telephone Interconnect Telephone Interconnect
Causes all telephone interconnect calls handled by the
Subsystem Server
server to be ended.
Interconnect call requests will be rejected.
Introduction to the Administration Menus

Most of the servers mentioned in this chapter are UNIX servers that have a strict security scheme
designed to limit access to the system. The systems servers provide an Administration menu that
allows you to access a variety of functions. These are text-based menus.
This chapter provides an introduction to the Administration menus for each of the servers and a brief
description of the menu items. For more information, see Volume 3, Administering Databases.
This section provides examples of administration menus; some menus may vary.
The User Configuration Server Administration menu contains the menu options to enable, disable, power down
the server, and administer the ASTRO 25 database. The following menu appears when you log on to the server:
User Configuration Server Administration
1. Enable User Configuration Server
2. Disable User Configuration Server
3. Display Server Status
4. Database Administration
5. Feature Administration
6. Unix Administration
7. Backup Server Administration
7-24 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System System Statistics Server
Enter Selection: (1 - 7, q,?) [q] >
Table 7-6 UCS Administration Menu Items
Menu Item Function

1. Enable User Configuration Enables the UCS after it has been disabled.
Server
2. Disable User Configura- Disables the UCS. This must be done prior to
tion Server power down.
3. Display Server Status Displays the servers current status: Enabled or
Disabled.
4. Database Administration Displays the Database Administration menu.
5. Feature Administration Displays the Feature Administration menu. Used to
enable features, show installed features, inquire on
the status of the license manager, and display the
current software version.
Displays the UNIX Administration menu. This
6. UNIX Administration menu contains many of the functions that you will
use to administer the server, such as Powerdown
and Change Administrator Password.
7. Back up Server Displays the Backup Server Administration menu.
Administration This menu contains the functions for backing up
and restoring the database.
The System Statistics Server Administration menu contains the menu options to enable, disable, power
down the System Statistics Server (SSS), and administer the Statistics database.
System Statistics Server Administration menu
1. Enable System Statistics Server
2. Disable System Statistics Server
Table 7-7 System Statistics Server Administration Menu Items
Menu Item Function

1. Enable System Statistics Enables the SSS after it has been disabled.
Server
2. Disable System Statistics Disables the SSS. This must be done prior to power
Server down.
6881009Y05-O April 2004 7-25

Zone Database Server Chapter 7: Databases, Servers, and Controllers
Table 7-7 System Statistics Server Administration Menu Items (Continued)

Menu Item Function
Disabled.
4. Unix Administration Displays the UNIX Administration menu. This
menu contains many of the functions that you will
The Zone Database Server Administration menu contains menu options to enable, disable, and power
down the server; maintain the ASTRO 25 database, and turn alarm and channel capabilities on or off.
You can access this menu only through the Zone Database Server console.
Database Server Administration Menu
1. Enable Database Server
2. Disable Database Server
3. Display Database Server Status
5. Database Administration
6. Feature Administration
7. Turn Off/On Channel Capabilities
8. Configure Routes
Table 7-8 Database Server Administration Menu Items
Menu Item Function

1. Enable Database Server Enables the zone database server after it has been
disabled.
2. Disable Database Server Disables the zone database server. This must be
done prior to power down.
3. Display Database Server Displays the servers current status: Enabled or
Status Disabled.
5. Database Administration Displays the Database Administration menu.
6. Feature Administration Displays the Feature Administration Menu. Used
to enable features, show installed features, inquire
on the status of the license manager, and display
the current software version.
7-26 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Zone Statistics Server
Table 7-8 Database Server Administration Menu Items (Continued)

Menu Item Function
7. Turn off/on Channel Displays the Turn off/on Alarm/Channel
Capabilities Capabilities menu. Used to disable and enable
alarm and current channel capabilities displays.
8. Configure Routes Displays the Route Configuration menu. Used to
add, delete, and make changes to routes for remote
manager terminals.
The Zone Statistics Server Administration menu contains menu options to enable, disable,
and power down the zone statistics server.
Zone Statistics Server Administration
1. Enable Zone Statistics Server
2. Disable Zone Statistics Server
5. Backup Server Administration
Table 7-9 Zone Statistics Server Administration Menu Items
Menu Item Function

1. Enable Zone Statistics Enables the ZSS after it has been disabled.
Server
2. Disable Zone Statistics Disables the ZSS. This must be done prior to power
Server down.
Disabled.
5. Backup Server Administra- Displays the Backup Server Administration menu.
tion This menu contains the functions for backing up
and restoring the database.
Air Traffic Router
The Air Traffic Router Administration menu contains menu options to enable, disable,
and power down the air traffic router server.
ATR Server Administration Menu
1. Enable ATR Server
6881009Y05-O April 2004 7-27

FullVision INM Server Chapter 7: Databases, Servers, and Controllers
2. Disable ATR Server

5. ATIA Call Logging Parameter Setup
6. ATIA Unicast IP Address Configuration
7. Set Up Automatic Radio Control Manager Export
Table 7-10 Air Traffic Router Administration Menu Items
Menu Item Function

1. Enable ATR Server Enables the ATR after it has been disabled.
2. Disable ATR Server Disables the ATR. This must be done prior to
power down.
Disabled.
5. ATIA Call Logging Displays a menu that allows you to enable or
Parameter Setup disable ATIA call logging. Must be enabled if you
wish to view ATIA logs with the ATIA Log Viewer.
6. ATIA Unicast IP Address Displays a menu that allows you to change or
Configuration display the ATIA unicast IP address.
The FullVision Server Administration Menu contains options to start and shutdown FullVision INM
FullVision Server Administration Menu
1. Enable FullVision Server
2. Disable FullVision Server
5. Server Maintenance
6. License Administration
7. Networking and Communication
Table 7-11 FullVision INM Server Administration Menu Items
Menu Item Function

1. Enable FullVision Server Enables the FullVision INM server after it has been
disabled.
2. Disable FullVision Server Disables the FullVision INM server. This must be
done prior to power down.
3. Display Server Status Shows the status of all FullVision INM applications.
7-28 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System FullVision INM Server
Table 7-11 FullVision INM Server Administration Menu Items (Continued)

Menu Item Function
5. Server Maintenance Allows the user to configure FullVision
system parameters, such as agent
registration/deregistration, database delete,
and database optimization.
6. License Administration Allows the user to activate optional licensed
features using feature ID codes obtained from
Motorola.
7. Networking and Allows the user to add one or more IP addresses
Communication to the routing table.
6881009Y05-O April 2004 7-29

FullVision INM Server Chapter 7: Databases, Servers, and Controllers
7-30 6881009Y05-O April 2004

Chapter
8
Network Security

Radio network security is vital for safeguarding valuable system information and communication assets
within and across your ASTRO 25 system. Network security is achieved through implementation of your
ASTRO 25 network security features and by employing best practices contributing to an appropriate level
of protection. Implementing and maintaining a secure environment for network communication of voice
and data across the Motorola radio network and within your network infrastructure is essential.
Security is an ongoing process of risk management implemented to satisfy the needs and requirements
of the communication network identified in the policies, plans, and practices established by those
responsible for its availability, reliability, and confidentiality.
The following security requirement categories define the scope, nature, and characteristics
associated with implementing a risk management process:
Administrative Security: To establish an ongoing focus on the security responsibilities

of those assigned to develop and support security plans and practices.
Physical Security: To provide protection against the threats to physical
components and assets of the communication system.
Network Security: To provide a defense against electronic intrusion and virus infection.
Communication Security: To safeguard the system through access control and to focus
on system features and functions contributing to information confidentiality.
For more on security management, see Volume 6: Security Management.

This chapter focuses on network security features and functions of your ASTRO 25 radio and
data communication system, including the following topics:
"Network Security Requirements and Considerations Overview" on page 8-2

"Network Security Operations and Services" on page 8-9
This chapter does not cover topics relating to the use of encryption for protecting radio communication
privacy, encryption key management, and over-the-air rekeying. For these topics, see ASTRO 25
Trunked Integrated Voice and Data System Release 6.4/6.4 SE Managing Secure Communications
(6881009Y65). The requirements and considerations for preventing unauthorized radios from
accessing the system and authentication are also not covered.
6881009Y05-O April 2004 8-1

Network Security Requirements and Considerations Overview Chapter 8: Network Security
Network Security Requirements and

Considerations Overview

Evolutions in system infrastructure technology, combined with new patterns of system usage, maintenance,
and interconnection with external networks, make it essential that sound network security policies and
practices be applied to a mission critical ASTRO 25 communications system. While it remains a highly
specialized infrastructure, the ASTRO 25 radio network does utilize commercial computing platforms and a
number of public and Internet protocols. At the same time, many customers are implementing greater
connectivity between the ASTRO 25 network and multiple external networks for system maintenance,
integration of data services, computer aided dispatch services, and network management functions. These
two factors combine to heighten the threats of electronic attack and unauthorized use. Network security
countermeasures, polices and practices are necessary to defend the communications system.
A review and assessment of the ASTRO 25 communication system from a network security perspective is
essential for successfully protecting communication assets. This includes, but is not limited to, the following:
"System Security Planning and Review" on page 8-2

"Analysis and Control of System and Service Users" on page 8-3
"Network Security Operations and Services" on page 8-9
System Security Planning and Review
Frequent reviews of network security policies and procedures supporting communication network
security are important. Network security policies and practices should be an integral part of the use and
administration of the system. These policies and procedures should include the following:
Security requirements for attached networks

System access controls for system operators and service/maintenance
users, including remote access
Antivirus policy for service/maintenance users
Ongoing maintenance of security enforcing functions, including update of antivirus
definitions and application of operating system security patches
Ongoing monitoring of security enforcing functions, including monitoring of network
interface barriers, antivirus functions, authentication functions, and element event logs
Emergency response procedures for dealing with network security issues
Access controls and antivirus policies for mobile data users
8-2 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Analysis and Control of System and Service Users
Motorola does not provide antivirus or customer network access controls for mobile data
users as members of the your network domain from within the radio network. Data traffic is
tunneled transparently through the radio network, making the radio network infrastructure
inaccessible to mobile computers. However, access via mobile data users of the radio system
to your enterprise network should be as secure as any other form of remote access to your
enterprise network, presumably by requiring user authentication and enforcing utilization
antivirus, personal firewalls and other security mechanisms on remote computers.
Analysis and Control of System and Service Users
A periodic analysis and control of system users is important for network security. System administrators and
communication system stakeholders must identify users and potential users of the system. This includes
individual users, user groups, agencies, and any other users who might have access to the system infrastructure.
Understanding the user community is a critical element for establishing a fundamental level of network security.
Network security requires user authentication and justification for user access to various system
features and functions. Information about the numbers and types of users and their access
level must be identified, recorded, and periodically reviewed.
Access control policies and procedures for user access should be clear and unambiguous.
Support personnel can access the network locally or remotely. Local access can be accomplished
through a terminal server. Remote access can be accomplished through a private link or with a
dial-up connection. Service interface control is an important network security consideration. Service
technician and system support providers are typically, but not necessarily, given high-level access
rights to conduct diagnostics and troubleshooting on an as-needed basis.
In all cases, user authentication is required for all service personnel using a properly configured client
running the RSA ACE/Radius client authentication software. User account and password credentials
for service personnel are stored in the Core Security Management Server (CSMS).
Communications systems operators are responsible for defining and administering user access
control. Users include all those who directly interface with radio network applications such as
dispatch and network management. User access management includes:
Establishing remote user and system user accounts and privileges

Provisioning and maintaining user credentials
Training users. Users should receive training in for password selection, protection, file
access permissions, expectations of privacy, and risks of social engineering.
Implementing procedural controls such as disabling floppy or CD drives (if appropriate) and
restricting access to and logging entry and exit information to critical areas.
Maintaining logs of system configuration changes.
6881009Y05-O April 2004 8-3

Network Security Components Chapter 8: Network Security
Network Security Components

Network security products and services in an ASTRO 25 communication system can

be grouped into the following categories:
"Core Security Management Server" on page 8-4

"Network Interface Barrier Optional" on page 8-8
Figure 8-1 Network Security Components
Core Security Management Server
The Core Security Management Server (CSMS) is required for each system. It consists of hardware and
software components to ensure that only authorized users access the radio network system. The CSMS is
required to safely enable use of system interfaces for remote service access and remote network management
service. The CSMS functions as a user authentication server controlling access through dial-in terminal
servers or service routers by maintaining individual user accounts and passwords for each authorized remote
8-4 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Core Security Management Server
user. Access to the network is denied if users do not provide appropriate credentials. The CSMS also verifies
that a remote computer, typically used by service and support personnel, meets qualifying criteria before
connecting to the network by checking for the presence of antivirus software required to be installed on the
remote computer. The following hardware and software components are part of the CSMS:
CSMS a rack-mounted Windows-based server with keyboard, monitor and mouse

Windows 2000 Server Operating System (OS) software the CSMS
operating system software
SmartStart software server setup support software
Symantec AntiVirus Server Corporate Edition - antivirus protection software
ISS RealSecure SiteProtector a network security monitoring, analysis, and reporting tool
Check Point Smartcenter Firewall Manager optional software tool for
configuring, managing, and monitoring firewalls
RSA ACE Server software user authentication software to manage user credentials
and collect authentication events, logs, and alarms. Accepts or denies user access to
the system by matching user accounts to passwords.
RSA ACE Agent software optional authentication software support for remote access.
Figure 8-2 Core Security Management Server
Other service interface control products to support the CSMS include a Motorola System Support
Center router and InReach terminal server for remote access. For more on the terminal
server, see Volume 9, Master Site Hardware Installation and Configuration.
The ISS Real Secure SiteProtector software and Checkpoint firewall management software
may be installed, but not activated. When an optional network interface barrier (NIB) is
included with your system, the appropriate license keys should be available to activate
the software. The NIB provides firewall and intrusion detection support. Check Point
SmartCenter Pro is required when more than one NIB is employed.
6881009Y05-O April 2004 8-5

Core Security Management Server Functions Chapter 8: Network Security
For a system-level perspective of the CSMS, see Figure 8-1.
Core Security Management Server Functions
The CSMS provides the following network security functions.
"Antivirus Management" on page 8-6

"User Access Management" on page 8-7
"Firewall Management" on page 8-7
"Intrusion Sensor Management" on page 8-7
Antivirus Management
The systems antivirus elements include antivirus scanning clients and the antivirus server.
The antivirus server functions as follows:
Manages the configuration of each client.

Receives and reports events and alarms.
Distributes antivirus definition updates to each client.
Antivirus Software
Motorola installs antivirus client software on the Windows-based computers that Motorola supplies.
The antivirus client software is capable of scanning for all known viruses.
The Symantec Norton Corporate Edition antivirus software resides on network servers and
client nodes to provide virus scanning activities and regular (weekly) updates to protect against
virus attacks. This software is installed on the following:
CSMS
Private Network Management (PNM) client
Transport Network Management (TNM) client
Console Operator positions
Console Database Management/Alias Database Management (CDM/ADM) servers
Motorola Gold Elite Gateway (MGEG)
MOSCAD client & server
InfoVista server
Adjunct Control and Signalling Server (ACSS) for telephone interconnect
8-6 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System User Access Management
Antivirus systems require regular updates of virus definitions. Commercial antivirus

suppliers have historically released virus definition updates on a weekly and sometimes
daily basis. Because there is some risk that a commercial antivirus scanner may mistakenly
interpret normal radio system functionality as virus activity, Motorola pre-tests antivirus
definitions and configurations prior to making them available.
Antivirus software should be deployed on service technician computers and

laptops accessing the system.
User Access Management
User access management involves establishing and maintaining remote user and service user accounts,
privileges, and credentials in authentication server applications hosted on the CSMS.
Firewall Management
Firewall management involves ensuring that only legitimate traffic travels between authorized points in
external networks and the radio system. Firewall management protects against unauthorized connections,
restricts traffic to known applications and protocols, and ensures that network resources cannot be accessed
from external systems unless authorized. Firewall management consists of the following activities using
the Check Point SmartCenter (or SmartCenter Pro) firewall management application of the CSMS:
Development and periodic maintenance of the rules that specifically define the
applications and protocols allowed to enter and exit the radio network.
Ongoing monitoring, management, and resolution of events and alarms
generated by the firewall.
Intrusion Sensor Management
Intrusion sensor management involves monitoring network traffic through the network security firewall
and reacting to alert messages. Intrusion management also includes recording and maintaining network
intrusion detection information to detect anomalies and protect against potential attacks.
Intrusion sensor management consist of the following activities using the ISS Re-
alSecure Site Manager application:
6881009Y05-O April 2004 8-7

Network Interface Barrier Optional Chapter 8: Network Security
Development and periodic maintenance of a filtering or tuning rule base that defines what
constitutes normal or abnormal traffic that may enter and exit the radio network.
Ongoing monitoring, management, and resolution of events and alarms
generated by the sensor.
Network Interface Barrier Optional
The network interface barrier (NIB) is an optional set of hardware and software components providing
boundary enforcement and attack detection features to provide supplemental network security protection.
NIBs safely enable use of the systems defined interfaces for integrated data, network management,
computer-aided dispatch, and billing. Deploying NIBs at each connection point between radio system
resources and external networks and equipment provides an important and recommended level of security.
Typically, radio communication systems with integrated data, console operator positions working with
Computer Aided Dispatch (CAD) applications, or systems that interface with external network management
have external network connections. These external network connections introduce the potential threat of a
virus or hacker attack propagating into the radio system. The degree of threat varies. If an external network
is a general-purpose intranet shared by multiple end-users and employs Internet connectivity, a significant
potential threat may exist. If the external networks are specifically dedicated to interfacing with the radio
system and contain no other functions or forms of connectivity, then very little threat may exist.
Placing NIBs local to each connection point tends to maximize the number of barriers; minimize delay;
and minimize bandwidth, routing, and backhaul requirements. Placing barriers in a central location tends
to minimize the number of barriers while maximizing delay impacts and maximizing requirements for
bandwidth and backhaul routing. It is generally best to plan on placing barriers local to each connection
point. External network connectivity is typically aggregated at major dispatch centers, switching offices, or
control rooms. Therefore, the number of these types of facilities can provide a good estimate of the number
of external network connection points which will likely require a network interface barrier.
For a system-level perspective of the network interface barrier components, see Figure 8-1.
The following hardware and software components are part of the network interface barrier firewall:
Firewall a rack-mounted firewall server

Nortel OS software operating system software for the firewall server
Check Point Smartcenter software firewall component of the Check
Point Smartcenter suite on the CSMS
Intrusion Detection System Sensor (IDSS) a SUNFire V100 server
Solaris 8 Operating Environment operating system software for the IDSS
ISS RealSecure Network Sensor the IDSS sensor software
RSA Ace Agent UNIX-based authentication service software
Ethernet switch an HP ProCurve 2524 Ethernet LAN switch providing a
parallel connection between the Firewall and IDSS so that the IDSS can monitor
and report on traffic encountered by the firewall.
8-8 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Network Interface Barrier Firewall
It is recommended that one NIB is established for each access point to the radio network. Also,
Check Point SmartCenter Pro is required when more than one firewall is employed.
Network Interface Barrier Firewall

The network interface barrier firewall is a rack mount, stateful-inspection firewall server used to ensure that
only legitimate traffic travels between authorized points in external networks and the radio system. The
firewall blocks unauthorized connections, restricts traffic to known applications and protocols, and ensures
that radio system resources cannot be accessed from external systems. See Figure 8-3.
Figure 8-3 Network Interface Barrier Firewall
Network Interface Barrier Intrusion Detection System Sensor (IDSS)

The Intrusion Detection System Sensor (IDSS) provides intrusion traffic monitoring of network traffic through
the network security firewall, see Figure 8-4. The IDSS software is designed and configured to send alert
messages to the CSMS to record and maintain network intrusion detection information. The intrusion detection
sensor works with the firewall to monitor traffic to detect anomalies and protect against potential attacks.
Figure 8-4 Intrusion Detection System Sensor
Network Security Operations and Services

Conducting network security operations and services is an investment in safeguarding the security of the
radio network. Security operation and service considerations include the following:
6881009Y05-O April 2004 8-9

Antivirus Subscription Service Chapter 8: Network Security
Establish a centralized security program authority to maintain a focus on security issues,

define security policies and procedures, and oversee ongoing security strategies and activities.
Promote and build a security culture to establish awareness through training and support.
Manage and maintain security enforcing functions by focusing on antivirus management,
user authentication management, firewall management, and intrusion sensor management.
Antivirus Subscription Service
The Motorola antivirus subscription service is a supporting function of antivirus management.
8-10 6881009Y05-O April 2004

Chapter
9
Advanced Call Processing

Separate hardware and software components in the ASTRO 25 system work together to process
calls. Two system perspectives help to understand call processing:
Physical System Perspective A hierarchical subsystem and component view of

the system focusing on how system components and subsystems physically connect
to handle voice, control, and data signals to process a call.
Logical System Perspective A functional view of the system focusing on how system
hardware and software components work together to handle voice, control, and data signals
to process a call. The logical perspective describes how system configuration affects call
processing, how the system tracks mobile subscriber units as they roam throughout coverage
areas, and how the system processes call requests from mobile subscriber units.
This chapter focuses on a logical perspective of the system. Diagrams supporting the logical
view of the system are designed to show a functional relationship of system components and
subsystems. Do not confuse logical diagrams with physical diagrams designed to support the
physical view of the system, showing how system components and subsystems are connected.
From a logical perspective, the master site, in an ASTRO 25 system, is the center of call
processing. The master site provides the following functions:
The zone controller processes requests for registration, individual dispatch calls,
group dispatch calls, and telephone interconnect calls. The zone controller validates
the requests and assigns the resources required to set up call services.
The Private Radio Network Management (PRNM) subsystem is a logical
infrastructure subsystem which provides the radio and user information necessary
to coordinate the resources for different types of calls.
Network transport equipment at the master site (routers, switches, and so on) provides the
IP connectivity to set up network communication paths to process calls. Network transport
equipment makes it possible to send voice through the system as IP packets.
The following sections provide a logical perspective to explain how the system
manages call processing activities:
"Configuration Information" on page 9-2

"Call Processing" on page 9-32
"Group-Based Services" on page 9-32
6881009Y05-O April 2004 9-1

Configuration Information Chapter 9: Advanced Call Processing
"Individual Call Services" on page 9-46

"Busy Call Handling" on page 9-60
"Effects of Loss of Service on Call Processing" on page 9-63
"Zone Controller Switchover" on page 9-69
Configuration Information

Configuration information is the foundation upon which all other aspects of call processing are built.
Configuration information, from a hierarchical perspective, is established at the system, zone and site
level. This includes configuration information for the mobile radios, portable radios, Console Database
Manager/Alias Database Manager (CDM/ADM) servers and console positions.
Two types of configuration information are identified:
Infrastructure Configuration.
Infrastructure configuration information defines how the underlying Fixed Network Equipment
(FNE) handles signal flow. For example, this type of configuration determines which MGEG,
site, and zone resources are assigned to a call. In general, this type of configuration is
handled by Motorola personnel prior to and during system installation
Static User Configuration

Static user configuration information for call processing support identifies
system users and services..
Dynamic User Configuration

Dynamic configuration information for call processing support includes tracking and
mobility management information. Tracking and mobility management information,
based on user configuration and location information, changes frequently and
is typically handled automatically by the system.
Static User Configuration
Static user configuration information, for call processing support, identifies individuals and talkgroups that
use the system and it identifies the services the system must provide to those individuals or talkgroups.
Static user configuration information is entered in three places:
The User Configuration Server (UCS) through the User Configuration Manager (UCM)
application. Within this application, records are built for radios, radio users, talkgroups,
and multigroups. Parameters that affect the operations of all radios in the system,
including site access denial, are also entered in the UCM application.
9-2 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Default Access and Default Records
The radios through their specific programming software.

The console positions and CDM/ADM servers through the Console Database Manager
(CDM) and Alias Database Manager (ADM) applications.
Static configuration information may be divided into four parts:
Home Zone assignment for individual and talkgroup IDs

Identification numbers and aliases for individuals and talkgroups
Call services and system features allowed for an individual or talkgroup
Valid site settings for each individual and talkgroup
Valid site settings, in conjunction with the system-wide Site Access Denial setting (see
"System Information" on page 9-12), play an important role in mobility management when
a radio attempts to register or a group member attempts to affiliate to a site.
The static user configuration information is referenced by the system each time a radio attempts
to register to a site and/or affiliate with a talkgroup.
Configuration information must be consistent when programming the UCS, radios, and consoles.
Default Access and Default Records

Normally, system recognition of a subscriber radio attempting to access the system is achieved after a
radio record is configured and established through the User Configuration Manager application. However,
default access is a system condition (configured for a zone using UCM) that allows subscriber radios to
access the communication system using a default configuration record when no configuration information is
available from the UCS. Under default access, when a subscriber radio attempts to access the system,
a default configuration record is automatically assigned to the subscriber radio. This default record
provides the subscriber radio with a predefined set of call services and permissions.
Default access allows all radio users and talkgroups to access the system with a predefined
set of permissions. Individual control of default access for a radio user or talkgroup is not
possible. This operating mode is not recommended under normal operating conditions.
The zone object in the Zone Configuration Manager (ZCM) configures and manages the attributes relating to a
specific zone. The zone controllers use these parameters to allocate resources. The zone object configuration
information is replicated from the Zone Database Server (ZDS) to the User Configuration Server (UCS).
6881009Y05-O April 2004 9-3

Individual Default Access Permission Chapter 9: Advanced Call Processing
Two of the fields in the zone object record determine whether radios are allowed to access the system only if
they have a record in the UCS, or whether they can access the system under default conditions using a default
record. The fields are called Individual Default Access Permission and Talkgroup Default Access Permission.
Individual Default Access Permission
This parameter can be set to Yes or No.
Yes indicates that a zone can automatically create a record in both the Radio and Radio User
objects (located in the UCM) using default settings for new radios that contact the system
(affiliations). The new Radio and Radio User records appear in the database as ZC$RADIO ID.
No indicates that under normal operating conditions, a new radio cannot access the
system until you manually enter a record in both the Radio and Radio User objects
in the UCM. Any requests from new radios are rejected.
Talkgroup Default Access Permission
This parameter can be set to Yes or No.
Yes indicates that a zone can create a new talkgroup record in the talkgroup object
(located in the UCM) using default settings when a radio request is received on
a talkgroup not currently in the talkgroup database. The new talkgroup records
appear in the database as ZC$TALKGROUP ID.
No indicates that under normal operating conditions, you cannot create a default
talkgroup record. Any requests on a new talkgroup will be rejected.
Using Default Records

Two types of default records are used by the zone controller when the individual and talkgroup
access permissions are set to yes: SZ$INIT and SZ$DEF.
SZ$INIT Record
The SZ$INIT record appears as a default record for the objects talkgroup, radio, radio user, and all
profiles. SZ$INIT defines privileges and default information for users and is the default record for a new
user or talkgroup whose UCM information is not available at the zone controller. During initialization the
zone controller is in the process of receiving records from the ZDS, SZ$INIT is the record that makes
it possible to provide call processing services to the radios during this time period.
The Initialization state occurs after the controller powers up or after a reset. It is the state where the
infrastructure database has already been downloaded from the ZDS, but the subscriber database has not.
The controller starts handling wide area calls after initialization and infrastructure download; however,
the subscriber and talkgroup records from the database are not available for call processing.
The controller uses the SZ$INIT records for any radio that is part of the system while the ZDS populates
the controllers Home Location Register with the home zone maps for all zones, the SZ$DEF record
for its zone, and the talkgroup and radio user records specific to that zone. The SZ$INIT records
define the default access that should be available during initialization.
9-4 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System SZ$DEF Record
The SZ$INIT record can be customized. The SZ$INIT Radio User and Talkgroup records are unique
to the zone. System access and level of service provided to the radio users are controlled through the
parameters set in the SZ$INIT record while the radios are in that specific zone.
Parameters set in the SZ$INIT record are not forwarded if the radio roams into a new
zone. The radio user will be under control of the parameters set in the new zones
SZ$INIT or SZ$DEF record. site access, Storm plans, and events, such as those monitored
by Inbound Event Display, can be severely impacted since the new zone cannot import
information from the previous zones SZ$INIT record.
As records are downloaded from the ZDS, the controller begins granting privileges according to the
subscribers configuration records and associated profiles. After all records have been downloaded and the
zone has returned to normal operations, the zone controller used the SZ$DEF records as the default access
for any subscribers or talkgroups that do not have that zone as their home zone, provided that the Default
Subscriber Access field in the UCM is set to Yes. If Default Subscriber Access is set to No, any requests
for service (ISPs) received from subscribers and talkgroups without actual records will be rejected.
SZ$DEF Record
The SZ$DEF is a default record that the zone controller uses after the ZDS database has been loaded. The
record defines guest privileges and default information for all radios, radio users, and talkgroups attempting to
access the system when no UCS record is available and default access is enabled. This situation could happen
for radios added to the UCS database while the link to a zone is down and who try to register or affiliate before
their data is downloaded to the ZDS. New radios or talkgroups created by the zone controller are a clone of the
SZ$DEF record. This includes the profile settings of this record as well. Changes made to SZ$DEF records
are always sent to the zone controller (once the ZDS database is loaded). Once the zone controller receives
user-entered records or profiles, those records are used by the zone controller instead of the SZ$DEF records.
The SZ$INIT and SZ$DEF records can be customized to control services to the radios
until their UCS record is available. For example, private call can be allowed for all users
through the SZ$INIT record but disallowed by the SZ$DEF record. Once the UCS records
are available, the feature can be controlled for each individual user.
Parameters set in the SZ$DEF record are not forwarded if the radio roams into a new zone.
The radio user will be under control of the parameters set in the new zones SZ$INIT
or SZ$DEF record. Site access, Storm plans, and events, such as those monitored by
Inbound Event Display, can be severely impacted since the new zone cannot import
information from the previous zones SZ$INIT or SZ$DEF record.
6881009Y05-O April 2004 9-5

Radio User and Talkgroup Record Download Chapter 9: Advanced Call Processing
Radio User and Talkgroup Record Download
After the Infrastructure database has been downloaded and the channel capabilities have been verified,
the Network Management Subsystem (NMS) begins sending subscriber and talkgroup records to the
zone controller. The time required for this download varies depending on the number of subscribers
and talkgroups in the system. Typically, this will take approximately thirty minutes for a system with
15,000 subscribers. A system with 64,000 subscribers could take as long as two hours.
Any radio, radio user, and talkgroup records added to the UCS database during the
initialization period remain in the database until the initialization period is complete. Once
the initialization period is complete, the controller replaces the default records with the
permanent records as it receives them from the UCS through the ZDS.
Identification Numbers
ID numbers are one of the key configuration elements that must be entered into the system. Based
on the ID numbers that have been entered, the system determines the following:
Whether or not the individual radio or group is allowed to register at a site

Which call services the individual radio or group can use
What system features the individual radio or group can use
Which zone is responsible for controlling the call (for group calls)
Programming ID Numbers
Individual and group IDs information from the system fleetmap is programmed into
the following areas of the system:
Using the UCM application, all individual and talkgroup IDs are entered in the UCS.
Using the applicable programming software, each radio is programmed with the system
ID, its unique individual ID, and as many talkgroup IDs as needed
Using the CDM and ADM applications, the console subsystem is programmed
with the necessary talkgroup and individual IDs.
Each console position uses one individual ID for each resource window presented to the
console operator. If two console positions have a window to monitor the same talkgroup,
they each have a different individual ID assigned for that specific window at each
console position. (Each resource window acts like a virtual radio, registering/affiliating
with the system in a manner similar to a mobile unit.)
9-6 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Home Zones
Home Zones
The home zone mapping object in the UCM application provides the capability to divide into ranges the total
number of individual and talkgroup IDs that can be used in the system and to assign the ranges to the various
zones. All of the home zone assignments for groups and individuals are compiled into two home zone maps:
Individuals to Home Zone

Groups to Home Zone
For example, Zone 1 can be assigned an Individual ID range that can include IDs 1 - 701, and a talkgroup ID
Range that can include IDs 1-17. Zone 1 becomes the home zone to any radio or talkgroup programmed
with a corresponding ID from the Zone 1 individual and talkgroup range tables.
Figure 9-1 shows the home zone mapping window, which is part of the UCM application. The
tabs in this window allow you to modify the individual and group home zone maps to associate
a range of IDs with a particular zone. The record creates two tables for each zone, one for the
individual IDs, and a separate table for the talkgroup IDs.
Figure 9-1 UCM Home Zone Mapping Window
An ASTRO 25 system with a single zone requires that all individual and talkgroup IDs be
assigned to Zone 1. Failure to do so will cause undesirable system operation.
Home zone mapping requires that all system wide IDs be accounted for in the ranges used to create a map.
Whether the map consists of one range or 32 ranges, individual IDs 0 through 16,777,215 and talkgroup IDs 0
through 65,535 must be assigned to the map. SZ$INIT and SZ$DEF records are considered zone specific
records, have their own unique IDs, and do not need to be tracked through the home zone maps.
Radio Identification
The Radio object is used to create records that contain attributes related to the physical radio
unit, such as its unique identity, serial number, RF band, and interconnect capability. A radio
record is required for each radio that will be accessing the system.
Objects created in an Elite dispatch operator position that will need audio resources when active, such as
talkgroup objects, also require a unique identification number. The identification is programmed in two places:
6881009Y05-O April 2004 9-7

Radio User Chapter 9: Advanced Call Processing
The Console Database Manager where the talkgroup resources for the
console system are created.
The User Configuration Manager, through the Radio object. If a talkgroup
resource is created in multiple console positions, each instance of the resource must
be identified with a unique record in the UCS database.
Identifying console resources in the same way as radios allows the system to properly identify the source
for requests for service and to forward information to the correct destination(s).
The total range of individual identification numbers used by the system is 16,777,218.
The IDs are distributed as follows:
ID 0 is reserved by the system and cannot be assigned to a radio or console resource.

1 - 16,777,211 are available for assignment to radios and console resources.
16,777,212 is assigned to RCM as a system wide ID.
16,777,213 is reserved by the system for internal use.
16,777,214 is reserved by the system for internal use.
16,777,215 Reserved for future use.
16,777,216 is assigned to the SZ$INIT record.
16,777,217 is assigned to the SZ$DEF record.
A unique radio serial number, radio ID, and radio user alias identify a specific radio and radio user in the
system. Some of these radios are data ready subscriber radios capable of requesting data messaging services
across packet data channel (PDCH) resources. Subscriber radios interfacing with mobile data devices
are capable of providing data to mobile data applications. These data-ready subscriber radios and mobile
data devices are configured and identified with an IP address, as well as other parameters, to support data
calls for data communication services. You use the radio object and radio user object in UCM to establish
the IP addresses and other necessary parameters to support data capable subscriber radios.
Radio User
The Radio User object is used to create records that identify specific users on the system and their
capabilities. The object can also be used to modify existing records. A radio user record includes specific
priority levels and access rights for dispatch and interconnect. To configure a radio user, you must know
how they will access the system and what capabilities they require for this access.
Radio user records rely on the replication of data between the User Configuration Server (UCS)
and the Zone Database Server (ZDS). For example, if a site is added to a specific zone in the Zone
Configuration Manager (ZCM), it cannot be configured as a valid site in the radio user record until the
information has been replicated to the UCS. If that site is deleted from the zone, the ZCM user continues
to specify it as a valid site for a radio user until the UCS is notified of the deletion.
Radio User to Radio Relationship
A radio user is associated with a specific radio. You associate the user with a radio by entering the
radios ID into the radio users record. This relationship between the radio user and a radio allows
you to change which radio a user may be attached to at any particular time.
9-8 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Data User
Data User
The data system object, together with the radio object and radio user object, establish a data user in the
system. Data capable subscriber radios and data devices configured and identified with an IP address
and associated with unique radio ID distinguish these users as data users in the system.
Profiles
A profile is a master list of common attributes or capabilities used by radio users, talkgroups, and multigroups.
Creating a profile allows you to enter the information one time and reference the profile from an individual
record. You do not have to enter the information separately into each record. You can create a different profile
for each type of function and group of users in your system, up to a maximum of 500 profiles.
Using a profile helps to reduce the amount of data that has to flow through the network between the UCM
and the zone controller. Profile information includes data that relates to radios, radio users, and talkgroups
who perform the same function. For example, all radio users associated with the fire department require
the same resources, so you can use a profile to create a master file for their records.
A record can have a one-to-one relationship with a profile (up to the 500 profile limit), or
many records can be mapped to the same profile.
Radio User Capabilities Profile
The Radio User Capabilities Profile object defines access parameters for radio users such as:
Group/Private Call Priority Level

Multigroup Call Enabled
Call Alert Enabled
Private Call (PC) Enabled
Group Call Enabled
You can use a Radio User Capabilities Profile object to define a set of parameters that are common to a
specific group of radio users. Every radio user is assigned a Radio User Capabilities Profile.
Radio User Site Access Profile
The Radio User Site Access Profile object is used to define a list of specific sites in the system the radio user
has permission to access. Every radio user is assigned a Radio User Site Access Profile. You can use a Radio
User Site Access Profile record to define a set of sites that are common to a specific group of radio users.
Radio User Interconnect Profile
The Radio User Interconnect Profile object defines interconnect call capabilities for radio users. Every
radio user is assigned a Radio User Interconnect Profile. You can use the Radio User Interconnect Profile
record to define a set of parameters that are common to a specific group of radio users.
Templates
A template provides the means to configure a record that can be applied to radio users who
will need the same set of system access parameters. Templates consist of a combination of
attached profiles and parameters set directly on the record.
6881009Y05-O April 2004 9-9

Configuration Updates Chapter 9: Advanced Call Processing
Configuration Updates
During system operation, updates are sometimes needed to an existing users configuration information.
Changes to a radio users configuration are entered in the UCS. Once entered, the changes are copied
to the ZDS in each zone during the database replication process. Each ZDS then distributes the applicable
home zone information to its zone controller; the zone controller uses this information to populate its
Group Home Location Register (GHLR) and Individual Home Location Register (IHLR).
For more information about User Profiles see Volume 3, Managing Radio Users.
Talkgroup
The talkgroup object consists of information that identifies a group of radios that
communicate and interact together on the system.
Defining Talkgroup IDs
Talkgroup IDs consist of an eight-digit decimal number beginning with 80000000. Talkgroups and
multigroups are created from the same pool of eight-digit decimal numbers.
The following numbers are reserved:
80000000 is reserved for system use.

80065535 is reserved for system use.
80065536 is reserved for the SZ$DEF default record.
80065537 is reserved for the SZ$INIT default record.
You can create a total of 16,384 talkgroups and multigroups on a system using this set of decimal
numbers. The assignable ID numbers can be anywhere in the range from 80000001 to 80065534.
TG/MG Capabilities Profile
The TG/MG [talkgroup/multigroup] Capabilities Profile object defines the capabilities for a talkgroup or
multigroup. You can use the TG/MG Capabilities Profile record to define a set of parameters that are
common to a specific talkgroup or multigroup. A partial list of parameters include:
9-10 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Multigroup
Message or Transmission Mode operation

Selecting Message indicates that the system assigns one repeater to the call for the duration of
the conversation within the parameters of the Message Trunk Timer. Selecting Transmission
indicates the system assigns one repeater for the duration of a single transmission by one radio.
The Message mode of operation causes the radio to return to the control
channel to send its individual ID anytime the push-to-talk (PTT) switch
is pressed. This mode of operation provides positive identification of the
transmitting radio and must be programmed in both the radio unit and the
system. In the radios programming the field is identified as PTT-ID, in
the TG/MG profile record the field is identified as Message.
Calls Without Console Allowed

Selecting Yes allows the system to process talkgroup calls without a console being
involved, if resource failures (for example, MGEG) prevent the console from accessing
the system. Selecting No requires that any affiliated consoles be part of the call. If
a console is affiliated to a talkgroup and resource failures are preventing consoles
from participating in the call, then the call is not allowed.
Audio Interrupt Mode Never or Always

Selecting Never prevents all audio interrupt requests. Selecting Always lets the system
automatically grant audio interrupt requests on the same talkgroup. The radio user
interrupting must have the same or higher priority level than the radio user who is
currently transmitting for the interrupt request to be granted.
Each TG/MG Capabilities Profile contains capability parameters that can be customized per configured
profile. Every talkgroup and multigroup is assigned a TG/MG Capabilities Profile. For more information
on Talkgroup/Multigroup Capabilities Profiles, see Volume 3, Managing Radio Users.
Multigroup
The Multigroup object is used to create records that identify a group of talkgroups that will be the
target of multigroup announcements. These records include the same parameters as the talkgroup
record plus two parameters specific to the multigroup record:
Interrupt or Wait Mode

Interrupt mode requires that all radios in the designated talkgroups participate in the call
whether the radios are monitoring the control channel or participating in a talkgroup call
as receiving radios. A message sent through the voice channel, as part of the ASTRO
embedded signaling, causes the receiving radios to return to the control channel to receive
the multigroups voice channel assignment. The only radios unable to participate in
a multigroup call are those radios currently transmitting.
Wait mode allows talkgroup calls in progress to end before a multigroup call begins,
the multigroup waits for all talkgroup members to be available.
6881009Y05-O April 2004 9-11

TG/MG Site Access Profile Chapter 9: Advanced Call Processing
Talkgroup in Multigroup
This parameter is used to enter the list of talkgroup associated with the specified Multigroup ID.
All talkgroups that are assigned to the multigroup must have the
same home zone as the multigroup.
TG/MG Site Access Profile
The TG/MG Site Access Profile object defines which sites the talkgroup or multigroup has access permission
for in the system. Every talkgroup and multigroup is assigned a Site Access Profile. You can use the TG/MG
Site Access Profile record to define a set of sites that are common to a specific talkgroup or multigroup.
System Information
The System object in the UCM configures parameters at the system level. These parameters are common for
every zone and may affect all radios in the system. The system record is created when the system is staged for
testing at the Motorola facility. Subsequently, the record can be opened to modify the fields that affect operation
of the radios in the system. This record includes the system identification, access control timers such as the
duration of the message timer for various types of calls, and maximum call duration for group or private calls.
Another field included in this record is the Site Access Denial Type. This field works in conjunction with
the Radio User Site Access Profile and TG/MG Site Access Profile records. Site access can be allowed
or denied to Radio Users and TG/MG through the corresponding Site Access Profile record.
The setting chosen for the Site Access Denial field in the system record has a direct impact on
radio unit mobility. The impact is discussed in the following sections.
Site Access Denial Set to Individual Only
Individual Only rejects the radio if the individual radio is not valid at the site. Reject means the
radio is given a Site Access Denial message. The radio leaves the current site and attempts
to register at another site based on its adjacent control channel list. Table 9-1 lists the effects
of site access denial and site access permissions for this setting.
Table 9-1 Site Access Denial Set to Individual Only
Service Request at a Service Request at a Site

Site in the TG/MG Site in the Radio User Site Result
Access Profile Table Access Profile Table
Yes Yes Group Call Allowed
Individual Call Allowed
Yes No Group Call Denied
Individual Call Denied
No Yes Group Call Denied
No No Group Call Denied
9-12 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Site Access Denial Set to TG Only
Site Access Denial Set to TG Only
TG (Talkgroup) Only rejects a radio if its affiliated talkgroup is not valid at the site. The setting in the Valid
Sites Profile for the Radio User has no effect in this case. Reject means the radio is given a Site Access
Denial message. The radio leaves the current site and attempts to register at another site based on its adjacent
control channel list. Table 9-2 lists the effects of site access denial and site access permissions for this setting.
Table 9-2 Site Access Denial Set to Talkgroup Only

Yes No Group Call Allowed
Site Access Denial Set to Either
Either rejects the radio if either the individual radio or its affiliated talkgroup is not valid at the site.
Reject means the radio is given a Site Access Denial message. The radio leaves the current site
and attempts to register at another site based on its adjacent control channel list.Table 9-3 lists the
effects of site access denial and site access permissions for this setting.
Table 9-3 Site Access Denial Set to Either

Yes No Group Call Denied
6881009Y05-O April 2004 9-13

Site Access Denial Set to Both Chapter 9: Advanced Call Processing
Site Access Denial Set to Both
Both rejects the radio if the talkgroup and the radio are not valid at the site. Table 9-4 lists the
effects of site access denial and site access permissions for this setting.
Table 9-4 Site Access Denial Set to Both

Yes No Group Call Allowed
As illustrated by the tables, the type of rejection depends on the valid sites set for each radio and affiliated
talkgroup in the corresponding UCS records. For example, with a site access denial setting of BOTH, if you
have a Radio User that is valid at the site but a talkgroup that is not valid, the radio is allowed to register and
stay at the site. The radio is allowed to make unit-to-unit calls but requests for a talkgroup call are rejected.
Continuing this example, if the mobile user switches to another talkgroup, the radio unit sends another
affiliation request, which is accepted or denied based upon the valid site setting for that group. If it is a
valid group, the system begins to provide both group and individual call services at that site.
Valid site and site access denial are the means by which a system manager can specifically control
the operating sites and individual/talkgroup services for each radio unit.
Source Site Adjacent Control Channel Object

The Source Site Adjacent Control Channel (ACC) object in the UCM application provides a means for
system administrators to identify a list of sites that are in close RF proximity to any given site. The site list
information is used by the system to provide subscriber radios with an Adjacent Site List (ASL). Subscriber
radios use the ASL to rank potential control channel candidates. In the event that the control channel of a
subscriber radio becomes too weak for acceptable use, a subscriber radio will attempt to find a control
channel from one of the adjacent sites in the list based on the control channel ranking.
System engineers create the new Source Site ACC record when they initially configure the
system. Subsequent users can only open and modify the existing record. System administrators
must consider the ramifications when changing the initial configuration. Selection and
programming of the source site adjacent control channel object requires detailed knowledge
about system coverage characteristics. Random selection of sites can severely impact system
operation as radios may experience problems accessing the system.
For more information about the Adjacent Site List, see "Adjacent Site List Control
Channel List" on page 9-18.
9-14 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Dynamic User Tracking/Mobility Management
Dynamic User Tracking/Mobility Management
Dynamic User Tracking/Mobility Management encompasses the system tasks which track where every
active individual and group member is located at any time. It utilizes the information supplied by the static
configuration and the information supplied by the radios as they register, access, and move about the system.
Individual radios must register at sites in the system. This allows them to make and receive
individual-based call services. In addition, radios affiliate with a talkgroup so that they can
participate in talkgroup calls and utilize other group-based call services.
The system determines whether to accept or deny a registration/affiliation request based on configuration
settings which are programmed into their UCS records and in the radio itself. Mobility management
is the primary function performed by dynamic user configuration.
Mobility Management
Mobility management describes the activities performed by the Fixed Network Equipment (FNE),
management software, and the control software in the radios, which enable radio users to roam and
communicate throughout the system without the need for user intervention.
During initial power-up, the radio uses its pre-programmed list of control channels to determines which of the
available sites it locks on to; subsequent power-up activity causes the radio to check its list of adjacent control
channel for availability. Once locked on to a site, the radio attempts to register itself with the site. The FNE
management software controls whether or not a radio is allowed to register, if the radio is allowed to register,
the system then keeps track of the location of that radio, and to which talkgroup the unit is currently affiliated.
Mobility information allows the system to know the site and zone location of every active, registered
radio. The system also knows which groups (both talkgroups and multigroups) have affiliated
members, and their site and zone locations. When the system is aware of the locations of all users
and their talkgroup affiliations, it is possible to identify the sites which need a voice channel assigned
when a user presses the PTT button on their radio to make a call request.
Registration
Registration is how a radio makes its presence known to the FNE in a geographical area. The
radio establishes and maintains a control channel link with the system as it moves from site to
site within a zone or from a site in one zone to a site in another zone.
In the sections that follow, mobility management is discussed from the two different
views that make up the overall process:
The radios view

The fixed network equipments view
In general, the location information is used for site and group affiliations. When a radio registers or roams
to a new site, the zone controller checks whether the radio/talkgroup member is at a valid site (according
to the valid site settings made in the UCM). If the radio is valid at the site, the zone controller updates
the location of the radio/talkgroup member in its mobility (HLR/VLR) databases.
Mobility as Viewed by the Radio

To a radio, the system is simply a collection of control channels and sites. The radio constantly monitors its
RF environment, and automatically switches to the best site available based upon received signal strength,
internal programming and responses to registration and affiliation requests sent to the FNE.
6881009Y05-O April 2004 9-15

Finding a Valid Control Channel Chapter 9: Advanced Call Processing
Finding a Valid Control Channel
When a newly programmed radio comes on the system, it references a preprogrammed list of control
channels to find a valid channel to lock on to. If the radio cannot find a valid control channel on the
preprogrammed list, it resorts to full spectrum scanning, if enabled, to find a channel.
Registration and Affiliation
When a valid control channel is found, the unit goes through a registration/affiliation
request sequence. This sequence registers the radio with the system and also affiliates the
radio with the selected talkgroup or multigroup.
If the registration/affiliation is accepted by the FNE, as defined by the Valid Sites and Access Denial settings,
the radio sets the current site as its home site and is now ready to make and receive calls.
If the registration/affiliation request is not accepted by the FNE, as defined by the Valid Sites and Access Denial
settings, the radio continues to search for a valid site and system, repeating the registration/affiliation request
sequence each time a control channel with the correct frequency and an acceptable signal strength is found.
If a subscriber radio is in a coverage area where the radio can receive outbound communication (system to
radio) but inbound communication (radio to system) is not possible, the subscriber radio will not be able
to receive acknowledgement to any affiliation requests on any available site. The subscriber radio can
provide notification of this condition with a tone, a display, or a combination of tone and display.
Figure 9-2 is a logical representation of the path the registration takes between the radio and the zone controller.
9-16 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Types of Registration and Affiliation Requests
Figure 9-2 Registration and Affiliation
Types of Registration and Affiliation Requests
There are three types of registration/affiliation requests a radio sends to the FNE:
Unit registration
Group affiliation
Location registration
6881009Y05-O April 2004 9-17

Situations When a Radio Must Register/Affiliate Chapter 9: Advanced Call Processing
Situations When a Radio Must Register/Affiliate
A radio makes registration/affiliation requests in three different situations:

When a radio initially comes on to the system or powers up. The radio performs a full
registration (a unit registration followed immediately by a talkgroup affiliation).
When the mobile user changes the talkgroup selection. The radio sends only a
talkgroup affiliation request since it is not necessary to re-register.
When the radio switches sites. The radio performs a location registration. This is
essentially a compact version of a full registration procedure that passes the individual
ID to the FNE. No talkgroup affiliation is necessary.
Radios in an ASTRO 25 system send a deaffiliation message when the user turns the radio off.
The message causes the appropriate zone controller to take the radio off the list of active radios.
Special circuitry allows the radio to send this signal prior to completely powering down.
Adjacent Site List Control Channel List
When a radio has registered at a site, it begins receiving Adjacent Site Broadcast (ASB) packets
from the site. A site broadcasts ASB packets for each site that is adjacent to it in order to inform the
radios of possible control channel availability. Using the UCM application to configure the Source
Site Adjacent Control Channel object, the zone controller receives this information and sends the
appropriate Adjacent Sites List (ASL) to the sites. The sites can now transmit the ASB packets to the
radios. Upon reception of the packets, the radios build an ASL in their memory. In addition, each radio
maintains a second dynamic list that contains the identification of up to three backup control channels
at its current site.Figure 9-3 illustrates the transmission of the ASB packets.
9-18 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Adjacent Site List and Adjacent Control Channels Requirements and Considerations
Figure 9-3 Adjacent Site Information
Once the ASL is populated, the radio periodically ranks the sites on the list. Each site is evaluated
against a number of parameters (described in the following section) which comprise the overall quality
value for the site. After each of these evaluation sequences, the radio checks the quality values of
each site in the list. If an adjacent site has a higher quality value than the current site, the radio
automatically switches to that better quality site, registers with the system, and then makes the new site
the home site. At the new home site, the radio begins receiving ASB packets, repopulates its ASL,
and continues the process of evaluating and ranking the sites in the ASL.
Adjacent Site List and Adjacent Control Channels Require-

ments and Considerations
By default, the system is typically configured to identify up to seven adjacent sites. In some topologies,
it is useful to expand the number of sites in the adjacent site list. For some systems, the number of
adjacent sites in the ASL can be expanded to fifteen sites. Before you can expand the adjacent site list
to fifteen sites, the subscriber radios must be expanded ASB capable. That is, the subscriber radios
must be able to accept the expanded number of sites. The configuration tab in the system window of
the User Configuration Manager application allows you to enable or disable this feature using the
Are all subscribers expanded ASB capable parameter (a yes/no parameter).
Be careful when enabling the feature to expanded the number of adjacent sites to fifteen.
Problems can occur if you enable this parameter when there are subscriber radios on
the system that have not been upgraded for this feature. For more detailed information,
contact your local Motorola technical field representative.
6881009Y05-O April 2004 9-19

Radio Signal Strength Indicator Chapter 9: Advanced Call Processing
If you attempt to add more records to the Source Site ACC in UCM that would increase the
number of adjacent sites beyond the standard number of seven and the expanded ASB capable
parameter is not enabled, the UCM application will respond to confirm that the parameter must be
enabled before you can increase the number of adjacent sites beyond seven sites.
Radio Signal Strength Indicator
As part of its ranking evaluation, the radio samples the signal strength of each site in its ASL. Several samples
for each site are averaged to create a filtered strength value for that particular site. The filtered value is
compared against the Radio Signal Strength Indicator (RSSI) threshold values programmed into the radio.
This comparison determines the signal strength value for the site. The five values are as follows:
Excellent
Very Good
Good
Acceptable
Poor
The RSSI value is one of the parameters which determine a sites overall quality value. For example, an
RSSI level of Poor dramatically lowers a sites quality value. If the current home site is rated Poor, and
there is an adjacent site which is rated Acceptable or better, the radio will switch to that site.
If all sites in the ASL are ranked with at least an Acceptable RSSI value (and all other ranking
parameters are the same), the RSSI value must move up at least two-levels before a site switch
will occur. For example, an RSSI value must move from Acceptable to Very Good, or a Good
level must move to Excellent before it will cause a radio to switch sites.
RSSI Example Scenario
Consider the following scenario:
A radio user moves through the coverage area of one site into the
coverage area of an adjacent site.
All ranking parameters (other than RSSI) are the same between the two sites.
The RSSI value of the current home site begins to drop, while the RSSI
value of the adjacent site begins to rise.
At some point, the quality values change sufficiently to influence the overall quality value for
each of the two sites so that the radio switches from the current home site to the new site.
Preferred Site
Preferred site is another contributing parameter to the overall quality value of sites in the ASL.
This parameter is programmed into the radio with one of four settings:
Always Preferred
9-20 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Site Preference During Site Trunking
Preferred
No Preference
Least Preferred
While each of the four settings can influence a sites quality value, they cannot single-handedly cause a radio
to switch to another site. For example, a radio will switch to a Least Preferred site with an excellent RSSI
value over a Preferred site with only a Poor RSSI value. However, if both sites have the same RSSI value,
then the radio would select the Preferred site over a No Preference or Least Preferred site.
You cannot force a radio go to a particular site based on the programming in the radio. There
are too many factors involved in determining the quality value for a site. If required, you
can ensure that a radio does NOT go to a specific site by using the valid site and site access
denial settings in the User Configuration Manager (UCM) application.
A setting of Always Preferred has a much greater impact on determining the quality value
for a site than do the other preferred site settings. A radio attempts to stay at an Always
Preferred site until the RSSI value drops to Poor.
Site Preference During Site Trunking
If a site loses contact with the master site, it goes into site trunking (radios at this site can only communicate
with radios registered at this same site). A radio programmed with that site as Always Preferred will stay
at that site (assuming at least an Acceptable RSSI value). For any other site preference setting, the radio
attempts to switch to a wide area site when the current site goes to site trunking.
Timing of Site Switches
For the radio user, RSSI sampling and site switching are transparent and require no user intervention.
If the radio is idle on the control channel and determines it needs to register at another site, the radio
simply changes to a control channel from its ACC list and completes a location registration.
A radio will not switch sites while it is transmitting on a voice channel. If the radio user is transmitting at the
time a site switch becomes necessary, the radio will wait to switch sites until the user releases the PTT button.
Site Trunking User Requested vs. Non User Requested
When a site enters site trunking due to a network management user request, the site controller immediately
informs the subscriber radio. The Site Trunking Indicator Holdoff Timer (STIHT) is not used to delay
notification of the site trunking mode of operation to the subscriber radios.
When a site enters site trunking due to a situation other than a network management user request,
the STIHT is used by the site controller to slightly delay notification to the subscriber radios of the
site trunking condition. Site trunking notification is sent when the STIHT expires.
6881009Y05-O April 2004 9-21

Random Holdoff Timers Chapter 9: Advanced Call Processing
Random Holdoff Timers
When a site goes into site trunking mode, radios registered at the site and with their internal site preference
parameter set for other than always preferred, will try to leave and find another site that is still in wide
area trunking mode. If a large number of radios all try to switch at once, as could be the case if the current
site goes into site trunking, it is possible to flood the inbound control channel of adjacent sites with
registration request packets. Random Holdoff Timers (RHOTs) are designed to prevent this.
RHOTs spread out the registration requests over a longer time period. RHOTs force a radio to
calculate a random value that determines when that radio attempts to register at the new site. Since
each radio will come up with a slightly different value, the registration requests are spread out, and
the inbound control channel of adjacent sites do not become overloaded.
Types Of Random Holdoff Timers
There are two Random Holdoff Timer values used with radios:
Failure Random Holdoff Timer (FRHOT)

FRHOT is the time value sent by wide area sites adjacent to a failed site. It controls the time
within which a radio attempts to randomly register at an adjacent site when the current home
site transitions to site trunking or directly to failsoft. The radios must wait from a random time
up to the FRHOT time to expire before it can register to an adjacent wide area site. This value
is configured at the site level and transmitted to the radios listening to the control channel.
Recovery Random Holdoff Timer (RRHOT)

RRHOT is the time value sent by wide area sites adjacent to a site which has just
recovered. Radios are allowed to roam back to the recovered site in a random time
period up to the time period specified by the RRHOT timer. This value is configured
at the site level and transmitted to the radios listening to the control channel. The use
of FRHOT and RRHOT is illustrated in the example below:
A site goes into site trunking due to a network transport failure. The
radios at the site switch to an available adjacent site and randomly register
based on the FRHOT time period.
The network problem is quickly corrected and the failed site transitions
back to wide area. Radios that had just left the site will now attempt to
return, since this site has a better signal quality.
Each radio attempts to switch back to the restored site randomly within
their programmed RRHOT value.
Random Holdoff Timer Value Settings
The RHOT values are set in the ASTRO 25 Repeater site, IntelliRepeater site, and digital simulcast
subsystem records in the Zone Configuration Manager. The range is 1 to 60 minutes, the default value
for these timers is set to 16 minutes and should be sufficient to cover most situations. If there is a need
to adjust the timers to cover a special case, using the following guideline is recommended:
9-22 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Mobility as Viewed by the Fixed Network Equipment
Choose an FRHOT and RRHOT value that is equivalent to the maximum number
of radios at the site multiplied by one second. For example, if it is expected that a
maximum number of 900 radios will affiliate to the site, set the timer for 15 minutes
(900/60 seconds). This will accommodate one location registration per second at
the site in addition to the normal requests for service.
Calculated values may be rounded to the next available time increment.
Mobility as Viewed by the Fixed Network Equipment

The Fixed Network Equipment (FNE) has two functions in mobility management:
To respond to the registration/affiliation requests from radio units

To track the current zone/site location of each registered individual radio
unit and each affiliated talkgroup member
To respond to registration/affiliation requests from radio units, the FNE in a zone where the unit is
registering needs a copy of the access control information for that individual and/or group. The FNE
in each zone also needs a place to store the site location of unit and group member.
How the Location Registers are Created

ASTRO 25 uses a distributed processing architecture that shares the call processing load between all the
zone controllers in the system. To enable this, the responsibility for storing (and using) the configuration
information is also spread among the zones in the system. Each individual and group ID is assigned
to a zone, based upon ID ranges, in the home zone mapping object in the UCS.
The zone assigned to a particular ID is said to be that IDs home zone. The home zone to
which an ID is assigned has an impact on how the system operates. Home zone assignment
affects system operation in the following ways:
Configuration information is distributed throughout the system based on the IDs

home zone assignment. A zone controller stores only the configuration information for
those individual and group IDs that are home to that zone.
For group call services, the home zone of the group is always the controlling zone for the
call, regardless of the zone where the group member is currently registered. Depending
on system configuration, this can impact the number of interzone calls versus the number
of single-zone calls that take place in the system. This, in turn, can affect the number
of interzone resources that are needed between any two pair of zones.
User configuration information is entered in the appropriate objects in the UCS: Radio and Radio
User for individuals, Talkgroup and Multigroup for groups. Once entered, user configuration
information is replicated automatically to each zone, where it is stored in the zones master
database (ZDS). The replication process makes it possible, if needed, to use any zone to promote
its copy of the user configuration information back to the UCS.
6881009Y05-O April 2004 9-23

How the Location Registers are Created Chapter 9: Advanced Call Processing
There is no separate backup routine to back up the UCS database. Backing up a zone
database also backs up the UCS information replicated to that zone.
Next, based on the home zone mapping, each zone transfers the configuration information for its
individuals and groups to the Home Location Register (HLR) in the zone controller. The home zone
mapping information is replicated to each zone from the UCS in the form of map tables. There are
two map tables: an individual to home zone map and a group to home zone map.
Whenever any individual or group configuration information is needed by any zone, it gets that information
from the HLR in the individuals or groups home zone. Figure 9-4 illustrates this information flow.
Figure 9-4 Home Location Register
When the HLR receives its information from the UCM and HLRs from other zones, the system uses a
specialized database, called the Visitor Location Register (VLR), in each zone controller to track the activity of
radios currently active. A VLR stores access configuration information for both individuals and groups along
with the current site location of the individual or group member. Figure 9-5 illustrates this information flow.
9-24 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Tracking Location
There are two VLRs: one for individuals and one for groups. The individual VLR stores the
access configuration information and current site location for each registered individual radio unit
in the zone. The group VLR stores the access configuration information for a group that has
affiliated members in the zone along with the site location of each affiliated member.
Figure 9-5 Home Location Register - Visitor Location Register
In ASTRO 25, all operator positions monitoring a talkgroup and the logging recorders
assigned to a talkgroup affiliate with the system. Thus, operator positions and
logging recorders have entries in a zones VLR.
Tracking Location
Location information is kept in two parts in two places:
6881009Y05-O April 2004 9-25

Handling Registration/Affiliation Requests Chapter 9: Advanced Call Processing
The HLR in the home zone keeps track on the individual/groups current zone location.
For groups, the group HLR tracks which zones have affiliated members.
The VLR in the local zone keeps track of the individual/groups current site location.
For groups, the group VLR tracks which sites have affiliated group members.
When a radio unit roams to a new site within the current zone, only the VLRs in that zone are updated
with the new site location. When the radio unit roams to a site in a new zone, the individual VLR in
the new zone requests the individual access control record from the appropriate individual HLR. If
there are no other affiliated group members in the new zone, the group VLR in the new zone also
requests the group access configuration information from the appropriate group HLR. If there are
other affiliated group members in the new zone, the group HLR simply updates its list of sites with
members. (The groups HLR already knows that members are in that zone.)
When a VLR requests the configuration information from an HLR, the HLR also updates the current
zone location for the individual and/or group. Note that the zone location in the HLR is updated
before the local zone has serviced the registration/affiliation request. If the request is accepted, the
VLR in the zone is updated, and the HLR stays as it is. If the request is denied, the local zone sends a
deaffiliation message to the appropriate HLR, which then removes the location tracking information
from that individual. For a group, if the unit being deaffiliated is the last group member in that
zone, the zone is removed from the HLRs list of zones with members.
Handling Registration/Affiliation Requests
A number of circumstances can cause a radio unit to send in a registration/affiliation request. For example, the
user just turned on the unit, or the radio unit automatically switched sites. From the FNEs view, however, it
just services requests and responds to them based upon the access configuration information.
The FNE in the zone that receives a request uses part of the access configuration information
from the appropriate VLR in that zone (either individual or group).
The access configuration information also defines what call services can be used by a
radio unit once it is registered at a site and affiliated to a talkgroup.
Getting the Access Configuration Information
When the FNE in a zone receives a registration/affiliation request, it first checks in the appropriate VLR
(individual or group) to see if an entry exists already for that unit/group. If an entry exists, the FNE services
the request. If an entry does not exist, the FNE requests the configuration information from the appropriate
HLR in the individual/groups home zone. (There are also two HLRs: an individual HLR and group HLR).
The home zone for a particular individual or group is found in a map table that is replicated to all zones
from the UCS. There is an individual to home zone map and a group to home zone map.
Once the VLR has the appropriate access configuration information, the FNE in that zone evaluates
the request and sends either an accept or reject reply to the radio unit.
A VLR keeps the configuration and location information only as long as there is a registered unit/group
member in the zone. If a radio unit roams to a site in a new zone, the VLR in the new zone gets the appropriate
configuration information and starts tracking the location. The individual VLR in the previous zone (the
9-26 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Checking for Valid Site
one the radio unit just left) deletes its entry for that radio unit. The group VLR in the previous zone deletes
the site location for that group member. If the radio unit that just roamed was the last affiliated group
member in the old zone, the group VLR also deletes the group access configuration information.
Checking for Valid Site
For a radio unit to be able to operate at a site, the unit must receive an accepted response from the FNE to a
registration or affiliation request. When the FNE receives a registration/affiliation request, the system
accepts or denies the request based upon the valid site settings for the individual unit and/or group, and
the settings of the Site Access Denial parameter (see "System Information" on page 9-12).
Interzone Communications
In a system with more than one zone, each zone controller communicates with the zone controllers in the
other zones to coordinate multizone calls, determine interzone trunking status relative to each other, and
share mobility information. Each zone controller communicates with other zones through the exit routers
and the wide area network (WAN) switch through two Interzone Control Paths (IZCPs) between each pair
of zones. The zone controller has redundant Ethernet links to the master site Ethernet switch through the
Control routers. An IZCP to each zone is associated with each of the two Control routers. The zone controller
uses these links to send command messages through the exit routers. One of the exit routers transports the
messages encapsulated in frame relay packets through its WAN switch to the WAN switch in the destination
zone. The WAN switch transports IZCPs and audio within ATM packets. See Figure 9-6.
6881009Y05-O April 2004 9-27

Interzone Communications Chapter 9: Advanced Call Processing
Figure 9-6 Multizone Call Services
The gateway router performs control, MGEG, and data router functionality.
9-28 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Controlling Zone
Controlling Zone
Assignment of controlling zone for interzone call services is based on the type of call. For multizone
individual calls, the zone location of the radio that first transmits audio becomes the controlling zone for
the call, while the zone of the call recipient becomes the participating zone. For talkgroup calls, the home
zone of the talkgroup (as defined in the GHLR in the groups home zone) becomes the controlling zone,
and all other zones with talkgroup members become participating zones. Throughout the duration of the
call, all control data and audio is routed from the originators zone to the controlling zone, then the audio is
routed from the controlling zone to all participating zones. The controlling zone controller is responsible
for managing the call and organizing all participating zone controllers into the call.
Table 9-5 lists the components and equipment required to process a call request.
Table 9-5 Call Processing Equipment
Component Function
Zone Controller CPU card The CPU card processes service requests, location information, outbound
commands, and maintains the HLR/VLR databases. The HLR and VLR are used
to determine access rights and location of the radios and talkgroups. Other zone
controller databases provide information on site and repeater availability. One
of its Ethernet connections is used to link with network management servers
through the LAN switch.
Zone Controller hard drive The hard drive stores the software required for operation of the zone controller,
the local infrastructure database, and the default radio and talkgroup records.
The stored information makes it possible for the zone controller to reestablish
wide area trunking in a single zone system and interzone trunking in a multiple
zone system. The HLR and VLR use the default records after a zone controller
reset to allow the radios to operate in the system while the subscriber database
is being restored from the ZDS. A copy of the local infrastructure database is
downloaded to the zone controller once the ZDS is populated with the zones
hardware configuration records. This copy of the local infrastructure database is
stored in the zone controller to provide wide area communication in cases where
the zone controller needs to re-initialize without having access to the ZDS.
Zone Controller Ethernet card The Ethernet card is responsible for the site link, interzone link, and link with the
telephone interconnect device.
Site Link - The zone controller uses this link for control and management
information from/to the sites.
Interzone Link - A zone controller uses this link to send and receives control
and management information from other zone controllers. The interzone
links are established through an ATM WAN switch.
Gateway (control) router Provides the routing path for call processing control information and becomes the
RP for zone controller to RF site control paths (SCPs). In multiple zone systems
the gateway (control) router also serves as the RP for IZCPs.
Core routers Act as the distribution point for audio, control information and network
management traffic destined for the same zone sites. The core routers become the
RP for audio routing in the system due to the multicast address sent by the zone
controller. Information is transmitted within IP packets.
6881009Y05-O April 2004 9-29

Controlling Zone Chapter 9: Advanced Call Processing
Table 9-5 Call Processing Equipment (Continued)

Component Function
Exit routers Act as the distribution point for audio, control information and network
management traffic destined for other zones. Information is passed as Frame
Relay packets to the WAN switch where they get converted to ATM for
transmission through the infrastructure.
Master site Ethernet switch Provides the backbone for the routers within the master site to pass IP traffic. The
zone controller communicates over this switch to reach the network management
servers for radio and interzone information, to reach the WAN switch for
intrazone and interzone transmissions, and select the MGEG resources for audio
conversion and distribution to the console operator and telephone interconnect.
Master site WAN switch The WAN switch encapsulates the Frame Relay information into ATM (inverse
IMA) packets for transmission to other zones. It also passes the packets destined
for same zone sites as Frame Relay.
MGEG and Gateway (MGEG) router The Motorola Gold Elite Gateway (MGEG) is an interface device that allows
an existing Elite circuit-switched, dispatch system to communicate over an IP
or packet-based system. The MGEG also provides the audio connectivity for
telephone interconnect in ASTRO 25 systems that include the interconnect
option. The Gateway (MGEG) router supports two 10Base-T interfaces for
interconnection to the Enterprise Ethernet switch and the MGEGs. The MGEG
can be equipped with Secure Voice modules to provide subscriber to MGEG
encryption capability.
Remote site router Serves as the site interface to the wide area infrastructure. Receives and transmits
control, audio, and management information. Accomplishes the Frame Relay -
Ethernet conversions. As an option, redundant site routers can be installed at
the sites.
Remote RF sites/subsystems IntelliRepeater remote sites and/or digital simulcast subsystems serve as the RF
interface between the radios and the ASTRO 25 system.
Figure 9-7 shows the call processing infrastructure.
9-30 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Controlling Zone
Figure 9-7 Call Processing Infrastructure
6881009Y05-O April 2004 9-31

Call Processing Chapter 9: Advanced Call Processing
Call Processing

Call processing is the term used to describe the sequence of processes that service a mobile users
call request. Call processing can be divided into the following phases:
Call request
Call setup
Audio routing
Call continuation
Call teardown
Call Types
Several types of calls can be made in a Motorola trunked system. This section describes
five examples from the possible types of voice calls that can be made. The examples are
divided between two main types of call services:
Group-based Group-based calls are services that provide for effective group (one
-to-many) communication. The following are examples of group-based calls:
Talkgroup calls
Multigroup calls
Emergency calls
Individual Individual calls are services that provide for effective individual (one-to-one)
communication. The following are individual type calls:
Private calls
The following sections describe these five call types using the call processing structure.
Group-Based Services

The ASTRO 25 system offers several types of group-based services. This section describes the following:
"Talkgroup Call" on page 9-33
9-32 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Talkgroup Call
"Multigroup Call" on page 9-42

"Emergency Services" on page 9-44
Talkgroup Call
The talkgroup is the primary level of communication in a trunked radio system. Most of the
conversations a radio user participates in are talkgroup calls. This section describes in detail
call processing for a talkgroup call. Two variations are shown:
Intrazone calla talkgroup call where all resources are within one zone
Interzone calla talkgroup call where resources are in more than one zone.
Intrazone Talkgroup Call

This is the most common type of ASTRO 25 call. Home zones are generally assigned to match up to
geographic areas where radios are used most frequently, such as a patrol district or management area.
When possible, talkgroups and radio users should be configured so that the majority of the calls take
place within this geographic area, thus reducing the need for interzone resources.
Call Request
A talkgroup call begins with a call request. The call request resolution determines whether the
call is set up or not. A talkgroup call request is initiated when the caller selects the appropriate
mode on the radio and then presses the PTT switch.
When the caller presses the PTT switch, the call request, in the form of an Inbound Signaling
Packet (ISP) is sent over the control channel to the current site. The information is passed to
the site controller for processing and routing to the zone controller through the site router.
The zone controller, for the zone where the request originates, determines if this is a valid
call request by checking the access configuration information stored in the VLR. If it is a valid
request, the zone controller checks its talkgroup-to-home zone map table to see which zone is
the talkgroups home zone. For group calls, the talkgroups home zone becomes the controlling
zone for the call, regardless of which zone the caller is in when the request is made.
If the zone where the request originates is the home zone, the zone controller coordinates
the call setup. If another zone is the home zone, the zone controller, for the zone where
the request originates, forwards the request to the appropriate zone.
Call Request from an ASTRO 25 Repeater Site
If the call request originates at an ASTRO 25 Repeater site, the request is encapsulated as 10Base-T
Ethernet packets by the base station and is then routed to the corresponding site Ethernet switch. The
information is routed from the switch to the site router, where it is encapsulated in Frame Relay packets,
for transmission to the zone master site. Figure 9-5 illustrates this process.
6881009Y05-O April 2004 9-33

Call Request from a Digital Simulcast Subsystem Chapter 9: Advanced Call Processing
Figure 9-8 Intrazone Talkgroup Request from an ASTRO 25 Repeater Site
Call Request from a Digital Simulcast Subsystem
Refer to Figure 9-9 and the following description of a call request from a digital simulcast subsystem:
9-34 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Call Setup
If the call request originates at a simulcast remote subsite, the base station takes
the call request from the radio and routes it through its V.24 link to its SRU-LD
interface at the local channel bank. The SRU card formats the information for
placement in a DS0 and inserts it into a time slot in the appropriate WAN link for
transmission to the ASTRO-TAC at the simulcast prime site.
Figure 9-9 Intrazone Talkgroup Request from Digital Simulcast Subsystem
A channel bank at the simulcast prime site receives the information from the infrastructure
and routes it to the appropriate ASTRO-TAC through its SRU interface and V.24 link.
The ASTRO-TAC receives the information through its wireline interface, votes the
signal, converts it to 10Base-2 Ethernet in legacy subsystems or 10Base-T in new
simulcast subsystems, and routes it to an Ethernet switch.
The prime site controller receives the call requests through the Ethernet switch, processes the
request and routes it to the zone controller through the Ethernet switch and the prime site router.
The prime site router encapsulates the Ethernet information in Frame Relay packets
and routes it to the master site through the infrastructure.
The receiving zone controller checks its VLR to see if the requesting individual
is configured to make talkgroup calls. If the talkgroup is affiliated to the current
zone, the zone controller checks for site affiliations.
Call Setup
Once a valid call request is received, the zone controller starts to set up the call:
The zone controller checks the VLR to determine talkgroup affiliations and subscriber
location. This information will indicate which sites need to participate in the call.
6881009Y05-O April 2004 9-35

Call Grant Chapter 9: Advanced Call Processing
The zone controller checks that all needed resources, such as channels at sites, consoles, and
MGEGs, are available to make the call. The zone controller sends the multicast information if
the needed resources are available. If some resource is not available, the zone controller sends a
busy signal to the radio requesting the call. (See "Busy Call Handling" on page 9-60 for details.)
Call Grant
When the call is granted, the following occurs (see Figure 9-10):
1. Routing information is sent to the appropriate master site and remote site routing equipment.
2. The Home Zone for the call request sets up a core router as the distribution point
for the audio information. This audio focal point is known as the Rendezvous
Point (RP) and its router becomes the Rendezvous Point router. The Rendezvous
Point for intrazone audio is the core router.
3. Channel assignments are sent to the needed sites.
4. The site controllers in ASTRO 25s broadcast the channel assignment, through the control
channel, to the radios and send the activation message to the assigned voice channels.
The assigned voice channels send a join message back to the master site.
5. The ASTRO-TAC for the designated channel sends a join message if the
call involves a simulcast subsystem.
6. The zone controller selects MGEG resources and sends audio routing instructions
to the Embassy switch for calls that involve consoles.
7. The designated MGEG sends a join message if the call involves a console.
8. The sites cause the activation of the receive and transmit circuits in the designated voice channels.
9. The receiving radios tune to the assigned voice channel at their respective sites.
10. The requesting radio electronically activates its transmitter.
9-36 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Intrazone Talkgroup Call Audio Routing
Figure 9-10 Talkgroup Call Grant
Intrazone Talkgroup Call Audio Routing
When the call is set up, voice communications can begin:
6881009Y05-O April 2004 9-37

Talkgroup Call Continuation and Teardown Chapter 9: Advanced Call Processing
1. When the radio user speaks into the radios microphone, the radio converts the speakers
analog audio into ASTRO and transmits the signal to the assigned voice channel.
2. The audio signal is transmitted by the radio over the assigned frequency to the
callers site and received by the assigned voice channel.
3. The voice channel places the audio into the sites Ethernet LAN as IP packets
and routes the audio signal through the site router to the assigned rendezvous
point router (core router) at the master site.
4. The rendezvous point router forwards the audio to any device that responded with a join
message to the zone controllers call grant. The devices responding with a join message
can be an ASTRO 25 Repeater, IntelliRepeater, a Comparator at a digital simulcast
subsystem, and an MGEG (if audio is to be routed to a console).
5. The talkgroup members already locked on to the voice channel receive the audio.
Talkgroup Call Continuation and Teardown
When the original speaker releases the PTT button, a control message is sent over the voice channel. This
message is extracted from the audio stream by the remote site and forwarded to the zone controller.
Control information flows continually during a call: over the control channel during call
setup and embedded in the digital audio signal during the active call phases.
1. When the speaker releases the PTT button, a message is sent to the controlling zone
controller. If the call is message trunked, a message hang time timer starts when
the message is received. All system resources, previously assigned to the call, are
held available during the timers hang time period.
2. If a person responds to the initial caller, by pressing the PTT button within the hang timer period,
the call continues. The message hang timer is reset and the new speakers audio is routed as the
source audio using the voice channels and router assignments already allotted for this call.
Interzone Talkgroup Call

The difference between an interzone call and an intrazone call is the other zone controllers that
must be included in the call control process. In an interzone call, each zone controls its local
resources in a similar manner to the previously described intrazone call. However, because the
controlling zone must coordinate with the needed participating zones prior to granting the call,
there is much more activity during the call request and setup phases.
9-38 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Interzone Talkgroup Call Request
Interzone Talkgroup Call Request
The call request is sent by the radio over the control channel at the local zone and site when the radio user
presses the PTT switch. This request is relayed through the remote site to the local zone controller.
Based on the talkgroup ID information in the call request, the zone controller receiving the
request checks its VLR and determines if the requester is able to make the call. The zone
controller then checks the talkgroup-to-home zone map and determines if it is the home zone
(and thus the controlling zone controller) for the call.
If it is the home zone, the local zone controller becomes the controlling zone controller and takes responsibility
for the call. The call request is acknowledged, and the controlling zone controller begins to set up the call. If
the receiving zone is not the home zone, the call request is passed on to the appropriate zone controller, which
accepts control of the call and becomes the controlling zone controller for the call (Figure 9-11).
6881009Y05-O April 2004 9-39

Interzone Talkgroup Call Request Chapter 9: Advanced Call Processing
Figure 9-11 Interzone Call Request
9-40 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Interzone Talkgroup Call Setup
Interzone Talkgroup Call Setup
The controlling zone controller determines which zones must be included in the call and sends a message
to the appropriate zone controllers, requesting their participation in the call. All interzone call control
messages between any pair of zone controllers goes over the Interzone Control Path between those two
zones. There is an active Interzone Control Path between any two zones in the system.
Each zone controller checks its VLR to determine which sites, along with which fixed resources, should
be included in the call, and if all the resources are available to set up the call. The call is busied if any
zone cannot participate due to lack of resources. If all the resources are available, the participating
zone controllers acknowledge their participation back to the controlling zone.
When all participating zones acknowledge the call request, the controlling zone controller grants the call.
The grant message is sent to each participating zone through its active Interzone Control Path with the
controlling zone. At this point, each zone is responsible for setting up the resources within its zone.
Within each zone, the zone controller:
Assigns voice channels at the appropriate sites within its zone.

Assigns the necessary audio resources and sends multicast addresses.
Notifies the consoles of the talkgroup call and its audio source, if needed. The
zone controller relays the audio assignments to the Embassy switch through the
ZAMBI link, the MGEG through the LAN switch, and the channel assignments to
the appropriate remote sites through their site control paths.
Once the resources are assigned, the rendezvous point router becomes the
center of control for audio distribution.
The site control function at each site performs the following:
Activates the repeater assigned as the voice channel.

Sends the voice channel assignment to the affiliated radios over the control channel.
End Devices
The assigned voice channel at ASTRO 25 Repeater sites, IR sites, the appropriate
comparator at a digital simulcast subsystem, and the selected MGEG at the master site
send a join message to the RP after they receive the multicast address.
As resources are set up in each zone, the radios in the talkgroup in each zone switch to the
assigned voice channel. The initiating users radio activates the transmit circuitry and begins
sending the audio to the receiver at the assigned voice channel.
Interzone Talkgroup Call Audio Routing
When the transmitting User speaks into the microphone, the audio signal is transmitted on the assigned voice
channel frequency and received by the repeater at its site, which routes the audio stream to the core router
at the local zone master site. The core router relays the audio signal to the assigned sites through their
remote site router, to the consoles through the LAN-MGEG-AEB-CEB link, and over the assigned interzone
resources to the exit routers in the participating zones. The exit routers in the participating zones then route
the audio to the LAN switch, the core router, MGEG router, MGEG, consoles in their respective zones,
and the assigned sites. The sites transmit the signal to the members of the target talkgroup.
6881009Y05-O April 2004 9-41

Interzone Talkgroup Call Continuation and Teardown Chapter 9: Advanced Call Processing
Interzone Talkgroup Call Continuation and Teardown
When the original speaker releases the PTT button a control message is sent over the voice channel. This
message is extracted from the audio stream by the remote site and forwarded to the controlling zone controller.
In transmission trunking mode, the call is ended after the PTT released message is received. In message
trunking mode, however, the controlling zone controller starts the message hang-time timer upon reception
of the PTT released message. If another user in the talkgroup responds to the call within the hang-time
period, the controlling zone controller receives the new call request (either from a site in its zone or from a
participating zone controller), sees that it is for a talkgroup that has an active call, and continues the call using
the resources currently assigned to the talkgroup. The audio source is the only resource change in this instance.
The call is ended when no one from the talkgroup keys-up within the message hang-time
period. The controlling zone controller sends a message to each participating zone to tear down
the call. Each zone goes through the teardown process, disabling the audio and marking the
resources used in the call as available for other call assignment.
Roaming During a Talkgroup Call
When a receiving radio user in an active talkgroup call roams into a new zone, the call is continued
automatically. Depending upon whether or not resources, such as a voice channel, are available to set
up the call at the new site, the roaming user experiences the following conditions:
If resources are available at the new site and the talkgroup call is already active in
the new zone (there are talkgroup members at sites within the zone), the roaming user
experiences a short loss of audio while the call is set up at the new site.
If resources are available in the zone to set up the call but the talkgroup call is not active (there
are no affiliated talkgroup members in that zone), the roaming user experiences a longer loss of
audio while the interzone call setup process takes place. The access control information needs to
be transferred from the home zone HLR to the HLR in the new zone and from there to its VLR,
the call request validated in the new zone, and a channel assigned and activated at the new site.
If resources are not available at the site or in the zone, the call continuation request to the
new zone is placed in its busy queue. When the needed resources become available, the
roaming user rejoins the call in process. A longer loss of audio occurs in this case.
Multigroup Call
A multigroup is a collection of talkgroups. You can transmit a message to two or more talkgroups
simultaneously by selecting a multigroup. Any user affiliated to any of the talkgroups in the
multigroup (or to the multigroup itself) hear the call.
The multigroup and all talkgroups in the multigroup must have the same home zone assignment.
A multigroup call can be set to wait or interrupt mode.
9-42 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Channel Marker for Talkgroup Calls
Wait allows talkgroup calls in progress to end before a multigroup call begins, so
the multigroup waits for all talkgroup members to be available. This mode allows
all of the radios in the multigroup to hear the call.
Alternatively, a multigroup call can be set to interrupt existing talkgroup communications,
not waiting for transmitting radio users in the talkgroups to stop keying their radios. Those
users join the call in progress when they release their PTT buttons.
Multigroup calls use message trunking, allowing those who receive the call to talk back to the
multigroup A multigroup call is processed in a similar manner as a talkgroup call. Audio for a
multigroup call is routed through the FNE in the same manner as a talkgroup call.
All call requests in the busy queue for the affected radios are dropped.
Multigroup information is programmed in two places:
One Multigroup per personality can be programmed in the subscribers radios.

Multigroup records must be created in the UCS database identifying the Multigroup
itself as well as the individual talkgroups associated with that Multigroup.
A radio unit with the selector in the Multigroup mode position can monitor talkgroup activity for talkgroups
associated with the selected multigroup if and only if the monitored talkgroups have an affiliated
member in the same zone as the monitoring subscriber. The system will not pass audio between zones
exclusively for a unit that is scanning talkgroup activity while in multigroup mode.
Channel Marker for Talkgroup Calls
A channel marker is a distinct, periodic, audible tone sent to consoles or subscriber radios. The primary
purpose of a channel marker is to inform radio users (console operators or subscribers) that a conventional
channel or trunked talkgroup is involved in a high priority situation. The tone indicates to radio users
that these system resources should only be used if they are involved in the high priority situation. The
tone also informs radio users that a console operator is monitoring the talkgroup.
A channel marker tone (a 700 Hz sine wave) is initiated and cancelled by a console operator only for a
talkgroup (multiselect, patch or customer-defined talkgroup) selected by the console operator. The duration of
the tone is .5 seconds. The reoccurrence rate, by default, is once every 10 seconds. While the reoccurrence
rate is a configurable parameter from 1 to 255, it is recommended that you establish the parameter no lower
than a reoccurrence rate of 8 to 10 seconds to avoid an unnecessary increase in communication traffic.
Once the channel marker button is active, the console sends periodic requests to the zone controller. If
there is voice activity on the selected talkgroup when a request is received, the request is not granted
and no tone is heard. Once the request is granted, the channel marker tone is received by all consoles
and available subscriber radios that are members of the currently selected talkgoup.
6881009Y05-O April 2004 9-43

Channel Marker and Alert Tone Process Chapter 9: Advanced Call Processing
The tone of a channel marker on a priority talkgroup will not interrupt a subscriber
on a voice channel involved in another talkgroup call.
Channel Marker and Alert Tone Process

Process 9-1provides a summarized description of the channel marker distribution process.
Process 9-1 Channel Marker Distribution Process
1 When a console operator initiates a channel marker on a selected talkgroup, a

push-to-talk request (for a tone, not voice) is sent to the zone controller.
2 At the zone controller, a new channel grant OSW assigns a channel for sending
the tone to radio users of the selected talkgroup.
3 Upon receipt of the channel grant from the zone controller, a tone is generated
by the Console Operator Interface Module (COIM) in the Central Electronics
Bank (CEB).
4 The COIM in the CEB generates a tone in the form of digitized PCM data and
sends it in a TDM timeslot to the AEB.
5 The AEB sends the digitized PCM audio tone to the MGEG voice card for
conversion to IP vocoded packets.
Consoles on the same AEB that are members of the selected talkgroup
receive digitized values of the tone without going through the MGEG.
6 In the MGEG, to convert the tone into IMBE vectors (frames), the vocoder is
bypassed (by detecting and identifying the tone before the vocoder) to avoid tone
distortion. The voice card converts the tone into IP packets for distribution.
For more MGEG, voice card, channel marker tone and alert tone information, see
"Motorola Gold Elite Gateway" on page 4-59.
Emergency Services
There are two types of emergency services:
Emergency alarmA radio to console or Radio Control Manager (RCM)

function that is sent over the control channel.
Emergency callA radio or console call function.
9-44 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Emergency Alarm
Emergency Alarm
When the emergency button on a radio is pressed, an emergency alarm is transmitted through the control
channel. This alarm is forwarded to any consoles monitoring the radios currently selected talkgroup or
multigroup. Any RCM positions that are active, and have the currently selected talkgroup or multigroup
as part of their list of attachments, also receive and display the emergency signal. The radio can be
configured to enter emergency call mode automatically when the emergency button is pressed.
Emergency Call
An emergency call is a specialized, high-priority version of a talkgroup or multigroup call. Emergency
calls always have the highest priority in the system. When an emergency call request is made, the
request takes priority over any other type of call request. The emergency call can be programmed
in the radio as tactical or revert. When programmed as tactical the call is made on the radios
currently selected talkgroup or multigroup. When programmed as revert, a talkgroup ID that
identifies the users emergency talkgroup must be programmed in the radio.
If a voice channel is not available at the requestors site, there are two possible methods for
giving the emergency caller quick access to a voice channel:
Top of QueueThe emergency caller is placed at the top of the busy queue and all calls
active at that site are set to transmission trunking. As soon as any user at any channel at the site
releases the PTT, the emergency caller is granted that channel while the other call is torn down.
Ruthless PreemptionA repeater currently in use is assigned to the emergency caller.
The remote site selects the repeater with the lowest priority user on the system. At
this point, the channel is given to the emergency users call.
An emergency call is routed to all affiliated talkgroup or multigroup members, including all
console positions and logging recorders affiliated to talkgroup or multigroup. All needed
resources for receiving sites are ruthlessly preempted.
Once an emergency call is granted, it is handled by the system as a talkgroup call although emergency
calls are message trunked with their own longer hang-time timer setting. The range for this timer is 0
to 3660 seconds, the default message hang-time for an emergency call is 30 seconds.
A value of 3660 disables the message timer for emergency calls. Radio Users
have unlimited time between PTTs.
A console operator can initiate an emergency call on any talkgroup or multigroup being monitored.
The system handles a console emergency call request the same as a radio-generated request, with one
exception: a console generated emergency call has an unlimited hang time, so the call stays active
until the operator knocks down the emergency call at the operator position.
Emergency calls initiated from the console are always processed in Ruthless Preemption
mode when resources are not available to grant the call immediately.
6881009Y05-O April 2004 9-45

Individual Call Services Chapter 9: Advanced Call Processing
Individual Call Services

Individual, unit-to-unit call services are available with ASTRO 25. Controlling zones are determined in
a manner different from that used for group-based calls for this type of call service. In an individual
call, the controlling zone is determined by the first radio to transmit audio.
This section describes the call process operations for unit-to-unit, individual-based
calls and telephone interconnect calls..
In unit-to-unit calls, the initial call request goes over the control channel. An audio channel is
not assigned until the target radio responds to the initial request. Audio channel resources
are assigned once the target radio responds to the call request.
Unit-to-Unit Call Request
Figure 9-12 graphically represents a unit-to-unit call request.
9-46 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Unit-to-Unit Call Request
Figure 9-12 Unit-to-Unit Call
A unit-to-unit call begins with a call request. The call request resolution determines whether the call is set
up or not. Requests will be rejected if the target radio does not respond to the request or if the target radio
is not registered with the system. Other reasons for a call to be rejected would be configuration-related
(one of the radios blocked from private calls, site not allowed, and so on).
The following sequence explains a unit-to-unit call request:
1. A private or unit-to-unit call request is initiated when the caller selects the appropriate mode
on the radio, and then enters the target radios ID or selects it from a list.
6881009Y05-O April 2004 9-47

Unit-to-Unit Call Request Chapter 9: Advanced Call Processing
2. When the caller presses the PTT switch, the call request is sent over the control channel
to the current site. The information is passed to the site controller for processing and
routing to the zone controller at the initiators master site.
3. If the call request originates at an IntelliRepeater site, the request is converted to

10Base-2 Ethernet by the base station and is then routed to a hub for conversion
to 10Base-T. The information is then sent to a router, where it is encapsulated into
Frame Relay, for transmission to the zone master site.
4. If the call request originates at a simulcast remote subsite, the base station takes the call
request from the radio and routes it through its V.24 link to its SRU-LD interface at the
local channel bank. The channel bank inserts the audio into a time slot in the appropriate
WAN link for transmission to the ASTRO-TAC at the simulcast prime site.
5. A channel bank at the simulcast prime site receives the information from the infrastructure and
routes it to the appropriate ASTRO-TAC through its SRU-LD interface and V.24 link.
6. The ASTRO-TAC receives the information through its wireline interface,

votes the signal, encapsulates as 10Base-2 Ethernet packets, and routes it to an
Ethernet switch for conversion to 10Base-T.
7. The prime site controller receives the call requests through the Ethernet switch, processes the
request and routes it to the zone controller through the Ethernet switch and the prime site router.
8. The prime site router encapsulates the Ethernet information in Frame Relay packets
and routes it to the master site through the infrastructure.
9. The receiving zone controller checks its VLR to see if the requesting individual
is configured to make unit-to-unit calls.
10. If the call is allowed, the zone controller checks its individual VLR to see if the target
radio is currently affiliated in the zone, and if it is, at which site.
11.
When Target Radio is in the Same Zone
If the target radio is active (registered) in the zone, the zone controller sends it a
unit-to-unit call request over the control channel at its current site.
When Target Radio is not in the Same Zone

If the target radio is not in the current zone, the callers zone controller determines the
target radios home zone by checking its individual-to-home zone map.
12. The callers zone controller sends a message to the target radios home zone
controller requesting the current location of the target radio (which the home
zone controller gets from its individual HLR).
13. Once the target radios current zone is known, the receiving zone controller sends
the call request to the zone controller in that zone.
9-48 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Intrazone Unit-to-Unit Audio Flow, Call Continuation, and Teardown
14. The target radios zone controller checks its individual VLR for the targets site location and
sends the call request to the target radio through the control channel at its current site.
15. Call Request Response

If the target radio is not registered with the system, the requester receives a call
reject. Otherwise, the requester hears a ringing tone. If the target radio does not
respond within the time-out period, the call request is ended.
If the target radio responds to the call request, the unit-to-unit call is set up.
Intrazone Unit-to-Unit Audio Flow, Call Continuation, and Teardown

At this point, the call proceeds with only the two affected users participating in the call.
1. When the initiating user presses the PTT on the radio, the audio signal is received by the
assigned voice channel at the local site and is routed to the RP at the zone.
2. The RP routes the audio packets through the WAN switch where they get encapsulated
as Frame Relay packets for transmission to the participating sites.
3. When the target user responds, the same path is used, but the source and
destination of the audio are swapped.
4. When neither party to the call responds within the message hang-time, the call is ended.
Interzone Unit-to-Unit Audio Flow, Call Continuation, and Teardown

1. When the initiating user presses the PTT on the radio, the audio signal is received by the
assigned voice channel at the local site and is routed to the RP at the controlling zone.
2. The core router at the transmitting radios zone sends the audio to the exit router through the
LAN switch. The exit router sends the audio to the WAN switch where they get encapsulated
as ATM packets for transmission to the participating zones WAN switch.
3. When the target user responds, the same path is used, but the source and
destination of the audio are swapped.
When neither party to the call responds within the message hang-time, the call is ended.
If either user keys up to respond after the hang timer has expired, but while still in
unit-to-unit call mode, a new unit-to-unit call is established.
6881009Y05-O April 2004 9-49

Roaming During a Unit-to-Unit Call Chapter 9: Advanced Call Processing
Roaming During a Unit-to-Unit Call

The ASTRO 25 system supports call continuation during roaming for unit-to-unit call calls. When a
non-transmitting radio user roams to a new site during a call, the audio is redirected automatically to the
new site. The radio user experiences a brief interruption of the audio when moving to another site within
the same zone. The audio interruption when moving to a site in a new zone may be slightly longer.
A transmitting radio user in an active unit-to-unit call cannot roam automatically. When
a transmitting radio fades out (due to moving away from the current site), the system
detects the loss and begins the call termination process.
Figure 9-13 illustrates the telephone interconnect capability that allows radio users to access the
Public Switched Telephone Network (PSTN). The PSTN is the traditional landline telephone
network to which most telephones are connected.
Besides the usual ASTRO 25 infrastructure, telephone interconnect requires two
additional hardware components:
Telephone Interconnect Server: a device with hardware and software components

that interface between the zone controller, AEB and the PBX.
Private Branch Exchange (PBX): a telephone switch that is operated
privately, instead of publicly.
9-50 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Relationship Between Components
Figure 9-13 Telephone Interconnect Diagram
The telephone interconnect feature builds upon all of the configuration and infrastructure
discussed up to this point. With talkgroup calls and unit-to-unit calls, all parties to the
conversations all reside somewhere on the ASTRO 25 system.
For telephone interconnect calls, one of the parties is outside of the ASTRO 25 system and is
connected through telephone to the radios in the ASTRO 25 system.
The ASTRO 25 system supports radio-to-landline and landline-to-radio interconnect calls.

It does not support interconnect calls to and from talkgroups.
Relationship Between Components

The zone controller uses call control client software to interface with call control server software
running on the telephone interconnect server. The call control server software translates the zone
controllers commands into a format compatible with the PBX and forwards them to the PBX. In
this way, the zone controller communicates to the PBX so that telephone interconnect calls can be
made from radios to the PSTN, and from the PSTN to individual radios.
In addition to audio, the telephone interconnect system supports the generation of Dual Tone Multi-Frequency
(DTMF) overdial tones (touch-tone), and other messaging tones (for example, end-of-call warning). This is
done using tone generation client and server software and an audio board installed in the telephone interconnect
server. This is a necessary feature since digital radios cannot generate their own overdial tones (touch-tones).
This capability is essential for accessing automated voice mail systems, or other types of automated resources.
6881009Y05-O April 2004 9-51

Configuration Chapter 9: Advanced Call Processing
Configuration
Radios must be properly programmed in order to make and receive telephone interconnect calls.
Limiting Access to Interconnection Services
Telephone interconnect services are very intensive users of system time. Each call requires a single channel to
be dedicated for the duration of the call, and telephone calls typically last longer than talkgroup calls. Because
of this, and because of direct toll costs, it is essential that you have the ability to limit the use of this feature.
Limiting Interconnect through Radio and User Configuration
Radios can be configured through the Radio Service Software (RSS) so that they can receive telephone
interconnect calls, but not initiate them. Radios can also be programmed with specific call lists (telephone
numbers) and configured to prevent users from calling non-programmed phone numbers. Individual radio
users may be configured with maximum monthly call times through the Radio User object in the UCM.
Individual Interconnect Profiles
Each radio user is assigned an Individual Interconnect Profile (a UCM object). These profiles are
created in the UCM and assigned to radio users. Your system may have a variety of different individual
interconnect profiles available for assignment to radio users. Among other settings, the individual
interconnect profiles specify a Facilities Restriction Level (FRL) and a Priority Level.
This FRL is a number from 1 to 7 which corresponds to a set of dialing restrictions stored in
the PBX. FRLs are set up in the Avaya PBX using the Definity Site Administration application.
A FRL of 7 has the least restrictions, 1 has the most.
Telephone interconnect calls can be assigned as priority level 2 through level 10, depending on individual
requirements. The priority level for interconnect calls is separate from the priority level assigned to
dispatch calls (a user could have different priorities for interconnect and dispatch). Level 2 is the highest
assignable priority while level 10 is the default priority setting. Priority levels are used by the system
to determine the assignment of system resources during busy periods. There are ten levels of priority
available, levels 1 through 10. The highest priority, level 1, is reserved for emergency calls.
See "Busy Call Handling" on page 9-60 for more information on how busied calls are handled by the system.
Limiting Interconnect through Infrastructure Configuration
In addition to individual radio programming, the infrastructure can be configured in such

a way to limit telephone interconnect services.
Sites or channels can be configured to limit interconnect calls through the Shared Services feature.
Enable or Disable Interconnect Based on Shared Service
The Shared Service feature is a more sophisticated method of balancing telephone interconnect
capability with dispatch traffic. Two types of shared service are available:
9-52 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Limit Interconnect Time at the Zone Level
Table-Driven Shared Service

A standard feature that allows the system manager to specify the maximum number and
duration of interconnect calls which will be allowed at any given time for each site. This
is done using the Level of Service (LOS) object in the ZCM. A number of LOSs can be
configured with different settings for maximum numbers and maximum duration of calls.
These levels of service can then be assigned individually for two-hour time blocks throughout
the day in the Shared Service object of the UCM. Each site is configured with its own table.
Dynamic Shared Service

Dynamic Shared Service (DSS) is an optional feature that expands the table-driven shared
service functionality. Dynamic shared service provides an automatic adjustment to the
configured table-driven shared service tables according to current system loading. DSS
allows you to create more flexible telephone interconnect usage patterns which can be
saved as different Levels of Service (LOS). These dynamic levels of service can then
be assigned individually for two-hour time blocks throughout the day in the Shared
Service object of the UCM. Each site is configured with its own table.
Limit Interconnect Time at the Zone Level
Interconnect can also be limited by the Maximum Interconnect Call Duration setting for the zone object.
Call Setup Restrictions
The following is a list of call setup restrictions:
The request for an interconnect call is placed in the busy queue if the radio
initiates the call and no channel resources are available.
If no MGEGs are available, interconnect calls will be busied until one becomes available.
Regardless of the infrastructure configuration, user limitations, or channel availability, CPS
programming of the radio can prevent interconnect calls from being attempted.
If shared service dictates that an interconnect call needs to be placed in the busy queue,
the call will be placed in the queue, even if there is a channel available at the site.
Radio-to-Landline Interconnect Calls
A radio user can place a radio-to-landline telephone call from any zone. The radio must be registered
at a site. Once a call is set up, the radio user can roam to any zone in the system.
Radio-to-landline calls are initiated with a request that includes all dialed digit information for the call.
This allows the system to check dialing restrictions before granting the voice channel for the call.
Restricted phone numbers will result in a denial of the interconnect call request.
The call setup process for a radio-to-landline call is shown in Figure 9-14. The call
maintenance/continuation and call termination/teardown processes for radio-to-landline
calls are similar to those for landline-to-radio calls.
6881009Y05-O April 2004 9-53

Call Setup Chapter 9: Advanced Call Processing
Figure 9-14 Interconnect Call Setup
Call Setup
This section describes the process used to initiate and setup a radio-to-landline call. The following sequence
describes the events that occur during the setup of a successful radio-to-landline call:
1. The radio user selects telephone interconnect mode on the radio, enters the number
to be called and then presses the PTT key on the radio.
2. The radio sends a telephone interconnect call request over the control channel
with the dialed digits information.
9-54 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Landline-to-Radio Interconnect Calls
3. The system verifies that the radio is authorized for telephone interconnect service.
4. The system determines from which zones PBX will be used for the call. The location of
the PBX will determine the controlling zone for the call, the point where the multicast
addresses originate, and the location of the RP for the call.
5. Radio system resources are assigned to the call. The resources include an AMB at
the Embassy switch to provide the audio and telephone control link between the PBX
and an MGEG, site where the radio is located, an MGEG for audio conversion to
IMBE, and an MGEG router for distribution to the network.
6. The zone controller sends two multicast addresses, one for the receive side of the call and one
for the transmit side. Transmission of the multicast addresses sets up the audio RP.
7. The MGEG and sites send a join message to the RP for the assigned multicast addresses.
8. The system checks the telephone number dialed to verify that the number represents
a valid telephone number and that dialing restrictions allow the radio to initiate
calls to the dialed telephone phone number.
9. A PBX-to-PSTN resource is selected for the call.
10. The PBX initiates the call to the PSTN.
11. Radio system resources are granted for the call.
12. The radio switches to the voice channel.
13. The caller hears a ringing tone to indicate that the call is being placed.
Landline-to-Radio Interconnect Calls
A telephone user initiates a landline-to-radio call by calling an access number. The system automatically
locates the target radio, regardless of the radios current zone affiliation, and routes the call through the
network to the target radio. The radio must be registered in a site which is in wide area trunking (Figure 9-15).
6881009Y05-O April 2004 9-55

Direct Inward Dialing vs. Non-Direct Inward Dialing Calls Chapter 9: Advanced Call Processing
Figure 9-15 Landline-to-Radio Request
Direct Inward Dialing vs. Non-Direct Inward Dialing Calls
Both Direct Inward Dialing (DID) and non-DID (overdial) operation is available with the ASTRO 25 system.
DID allows the telephone caller to directly dial a telephone number representing a specific
radio user. While the caller hears a ringing tone, the PBX forwards the number to the zone
controller. The zone controller cross-references the ID number to a specific user.
Non-DID requires that the telephone caller dial a common access number. The PBX answers
the call and prompts the caller to dial the mobile ID number (overdialing) assigned to the
9-56 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Call Initiation
radio user they wish to reach. The PBX forwards the mobile ID number to the zone controller.
The call initiation and setup process for a landline-to-radio call is described in the following sections.
The call maintenance/continuation and call termination/teardown processes for landline-to-radio
calls are similar to those for radio-to-landline calls. For more information, see "Telephone
Interconnect Call Termination and Call Teardown" on page 9-58.
Call Initiation
This section describes the process used to initiate a landline-to-radio call.
Call Initiation Process for Direct Inward Dialing Operation
The following sequence occurs during the call initiation process for DID operation.
1. The Private Branch Exchange (PBX) detects an incoming call and receives the
DID digits as provided by the central office.
2. The PBX notifies the zone controller about the call, and forwards the DID
digits to the zone controller.
3. The PBX issues a ringback tone to the landline user so that they hear a ringing tone.
4. The radio system performs a DID database lookup to cross-reference the

DID number to a specific user.
Call Initiation Process for Non-Direct Inward Dialing Operation
The following sequence describes the events that occur during the call initiation
process for a non-DID operation.
1. The PBX answers an incoming call and issues a tone or voice announcement prompting
the landline user to enter the ID number representing the target radio user.
2. After the PBX receives the ID number, the PBX notifies the zone controller about the
call, and provides the system with the target radio ID number.
3. The PBX issues a ringback tone to the landline user so that they hear a ringing tone.
Call Setup Process for Direct Inward Dialing and Non-Direct

Inward Dialing Operation
The call setup process is the same for both DID and non-DID types of calls.
1. The zone controller verifies that the target radio is registered on the system
and is authorized for interconnect service.
6881009Y05-O April 2004 9-57

Telephone Interconnect Call Continuation/Call Maintenance Chapter 9: Advanced Call Processing
2. Radio system resources are reserved for the call.
3. The system sends a control channel message to the radios registered site to
notify the radio of the incoming call.
4. The radio monitoring the control channel responds to this message and starts ringing.
5. When the radio user answers the call, the radio sends a control channel message,
after which radio system resources are granted for the call.
Telephone Interconnect Call Continuation/Call Maintenance

When a radio-to-landline or landline-to-radio interconnect call is established, the radio moves over to the
assigned voice channel for the duration of the call. If necessary, the radio can move to the control channel to
perform special functions, such as an overdial request, or to send a request to cancel the interconnect call.
During the call continuation and call maintenance phase of a telephone interconnect
call, the following of events take place:
Control signalling
Channel grant updates
Overdial support
Half-duplex operation notification
Control Signalling
Control signalling as well as voice is sent on the interconnect voice channel, both inbound
(sent by the radio) and outbound (sent by the system). This control information is sent as data
messages. Interconnect data messages sent during active telephone interconnect calls include
information about the radio participating in the call (its radio ID).
Update Grants
After the initial channel grant for the call is sent over the control channel, channel grant updates
are sent periodically throughout the call. During an active interconnect call, if the participating
radio enters a fade situation and moves away from the voice channel, the channel grant update
function makes it possible for the radio to rejoin the call.
Half-Duplex Operation Notification
Telephone interconnect calls are half-duplex. This means that the radio cannot transmit and receive
at the same time. Because of this, the system sends a go ahead tone to the landline caller when a
half-duplex radio has dekeyed. This tells the landline caller that they are free to speak.
Telephone Interconnect Call Termination and Call Teardown

Either the radio or the landline party can terminate a telephone interconnect call by hanging
9-58 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Radio-Initiated Termination During Active Interconnect Call
up. Either party is able to terminate the interconnect call when the call is in the active
state, or at any point during the call setup process.
The system can also initiate termination of interconnect calls because of the following call timeout scenarios:
The duration of an interconnect call exceeds a configured call duration limit.

The time between radio PTTs exceeds the configured Call Timeout timer.
Radio-Initiated Termination During Active Interconnect Call
The system can accommodate call termination requests sent on either the control channel or the voice
channel. Motorola brand radios send these requests over the control channel.
If the radio is turned off during an interconnect call (active call, or while in a call setup state), the radio
automatically cancels the interconnect call before de-registering from the system and powering down.
Landline Initiated Termination During Active Interconnect Call
During an active interconnect call, when the landline caller hangs up, the PBX detects this
condition and notifies the zone controller to terminate the call.
For analog, loopstart telephone lines, disconnect detection is not always possible. If a
landline caller hangs up during a call of this type, the PBX may not be able to detect
the hang up, and the call may continue until either the radio user terminates the call, or
the call is terminated because of timeout timers. For this reason, analog groundstart or
channelized T1 or E1 interfaces are preferred over analog loopstart lines.
System Initiated Interconnect Call Termination
The system can terminate a telephone interconnect call that exceeds one of the system timers. This is
controlled by setting the Maximum Interconnect Call Duration timer in the Zone Configuration Managers
(ZCM) zone object, in conjunction with the shared services configuration and current system loading. The
system also disconnects an interconnect call if the participating radio does not rekey within a set time period.
1. Prior to automatic call termination, the system notifies both parties using
an end-of-call warning tone.
2. After a set interval of time (set by the Interconnect Final setting in the ZCM
Zone Configuration tab), the call is terminated.
Roaming During a Telephone Interconnect Call

A radio can roam from one site to another during an interconnect call. This can occur during an
active call, while the call is being set up, or while in a busy state.
This section describes how roaming affects an active interconnect call, an interconnect call in a call setup
6881009Y05-O April 2004 9-59

Roaming During an Active Interconnect Call Chapter 9: Advanced Call Processing
state, or an interconnect call in the process of being terminated. For each scenario, there are several
possibilities that can occur once the radio has roamed to the new site, depending on variables such as resource
availability at the new site, and whether or not the radio is valid for this individual call activity at the new
site. It is assumed that the radio has previously performed a full registration on the system.
Roaming During an Active Interconnect Call
If a radio roams during an active interconnect call, the following takes place:
The zone controller determines whether the radio is valid for individual services at the new
site, and whether the radio can support interconnect calls according to shared service.
If the required resources at the new site are available, the zone controller
grants the call immediately.
If the required resources at the new site are busy, the zone controller places the
call in a busy queue until the busy resource becomes available. The landline user
is not notified about the busy condition of the call.
Roaming During Busy Interconnect Call
If the zone controller determines that the required resources are not available during the
setup of a radio-to-landline or landline-to-radio call, the call is placed in the busy queue
until the required resources are available.
If a radio involved in a busy call roams and registers at a new site, the zone controller
checks again to see if the required resources are now available.
If the resources are available at the new site, the call will be granted.
If there are no resources at the new site, the call will remain in the busy queue.
Roaming While Ringing for Landline-to-Radio Call
If the radio roams while ringing for a landline-to-radio call, the radio continues to generate the
ringing indication for the duration of the ring timer. The zone object in the ZCM includes a
field, called Interconnect Transpond/Ring, that can be used to limit the amount of time the zone
controller waits for the radio to respond to the interconnect call message. The interconnect call
setup is discontinued if the timer expires before the radio responds.
Busy Call Handling

This section describes how the system modifies the calling process to handle situations where
resources are not available at the time a call request is made.
9-60 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Priority Levels
A call request that cannot be granted the necessary resources when the call request is made is
placed in the busy queue of the controlling zone controller.
Calls are placed in the busy queue in the order in which they are received. However, priority
setting of each call type influences the order in which calls in the busy queue are evaluated.
Higher-priority calls are evaluated before lower-priority calls. Calls of equal priority are evaluated
on the basis of the order in which they were placed in the queue.
Priority Levels
Priority levels are used by the system to determine the assignment of system resources when
multiple calls are competing for system resources. Emergency calls always have the highest
priority level. The system has ten priority levels:
Priority level 1 Priority level 1 calls are the highest priority and are reserved for
emergency calls. Priority level 1 calls cannot be assigned to any other call types.
Priority levels 2-10 Priority levels in this range are assigned to talkgroup,
individual, or telephone interconnect calls. Priority level 2 is the highest assignable
priority, while priority level 10 is the default priority setting.
Group Call Busies
Two calling features determine when group (talkgroup and multigroup) calls are busied:
AllStart
FastStart
These calling features are assigned to the groups in the User Configuration Manager (UCM) application.
AllStart
An AllStart setting for a group indicates that all the available resources for the call must be present for
the call to start. An AllStart call requires the following resources before a call is granted:
A voice channel at all sites that have affiliated group members.

All affiliated consoles and logging recordersthis includes all resources,
such as the MGEG, to support console calls.
Encryption resources at the MGEG if the call is secure.
A voice channel at all critical sites. Critical sites for a talkgroup are designated in
the TG/MG Site Access Profile record available in the UCM.
If any of the above conditions are not met, the call is placed in the busy queue.
6881009Y05-O April 2004 9-61

FastStart Chapter 9: Advanced Call Processing
FastStart
A FastStart setting for a group call indicates that only mandatory resources (that is, critical sites, critical
resources and requested sites) are required to grant a call. Any other resources available at the time the call is
set up are also included in the call. In FastStart, not all affiliated members in a talkgroup must have a channel
available in order for a call to start. FastStart requires the following resources before a call is granted:
A voice channel at the requestors site.

All affiliated consoles and logging recorders - this includes all resources,
such as the MGEG, to support console calls.
Encryption resources at the MGEG if the call is secure.
A voice channel at all critical sites.
If any of the above conditions are not met, the call is placed in the busy queue.
When a group call is busied, the priority that is assigned to the call in the queue is determined by
the higher of the talkgroups or requestors individual priority. For example, if the talkgroup is
priority 8 and the requestor is priority 5, then the call is queued with priority 5.
Unit-to-Unit Call Busies
Unit-to-unit calls are placed in the busy queue if the required resources for the call, including
encryption, are not available at the time of the request.
Unit-to-unit calls can have a priority level assigned that determines how the call request is serviced
in the busy queue, the higher the priority, the sooner the call gets serviced.
When a unit-to-unit call is busied, the priority that is assigned to the call in the queue is
determined by the better of the target or requestors individual priority. For example, if the targets
priority is 8 and the requestors priority is 5, then the call is queued with priority 5.
Typical Reasons for Rejects
When a radio requests a particular service, the zone controller can choose to grant the request, reject
the request, or respond with a busy signal. When a service is granted, the zone controller assigns the
appropriate resources and sends a message to the requestor granting the service. When the zone controller
rejects a request, the zone controller sends a reject message to the requestor. When the zone controller
is experiencing a busy situation, the zone controller sends a busy signal to the requestor.
9-62 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Effects of Loss of Service on Call Processing
When a radio has been rejected from using a particular service, the zone controller sends an abort message
to any resources that need to be released from the service, then sends a reject message to the radio. The
following items are typical reasons why a radio may be rejected during registration or during a call request.
The radio may be sending an individual ID or talkgroup ID that is not

loaded in the zone controllers memory.
The radio may be requesting a service that is restricted or not available to the particular radio.
The system or the receiving radios may not support the call type requested
by the initiating radio.
The system may be in a failure situation. Depending on the settings and the situation,
the sites may be in site trunking and only allow certain types of calls, or the zone
controller may be using default access permissions.
The radio may be calling an individual or talkgroup that does not exist or
that is not registered with the system.
The radio may not be configured to make the requested type of call.
For talkgroup calls, a console that should be attached to the call may not able to participate in
the call. Failure of a single MGEG in a zone does not prevent a console from participating in a
talkgroup call, only failure of all MGEGs in a zone can cause this problem.
The radio is not operating at one of its valid sites.
The zone is not able to communicate with the home zone of the initiating radio.
The zone is not in interzone trunking with the other zones that need to participate in
the call. The particular resources may not be available for the call.
Effects of Loss of Service on Call Processing

For purposes of this discussion, loss of service indicates that part of the ASTRO 25 infrastructure has failed,
and that the failure affects the ability of calls to be made through some part of the system.
This section describes the impact of loss of service on call processing. See "Zone Controller Switchover" on
page 9-69 for a discussion of the impact of a zone controller switchover on call processing within a zone.
Generally, in an ASTRO 25 system, a service state for a site other than wide area trunking causes
the radios at the affected site to attempt to register at a site that is in wide area trunking mode.
6881009Y05-O April 2004 9-63

Loss of Service Within a Zone Chapter 9: Advanced Call Processing
Loss of Service Within a Zone
Within a zone, three types of service states are available for sites that affect call processing: wide
area trunking, site trunking, and site Failsoft. These states are listed in Table 9-6.
Table 9-6 Zone Call Service States
State Definition
Wide Area Trunking Wide area trunking is the normal state for a site within a zone. In this state, the site
receives call processing instructions from the zone controller. A radio registered at the
site can communicate with any other radio in the system. The basic criteria for wide
area trunking includes an active RF site control path between zone controller and site,
an enabled audio rendezvous point in the zone, a control channel and a voice channel
at a site.
Site Trunking Site trunking mode is entered when the remote site loses communication with the zone
controller. In this mode, the remote site takes over call processing responsibility. In
an IntelliRepeater site, one of the IntelliRepeaters will function as a controller for the
site and perform all call processing functions for the call traffic at that site. A radio
registered at the site can communicate only with other radios registered at the same
site. In a simulcast subsystem, the simulcast prime site controller performs the same
function as the site controller in an IntelliRepeater site. Communication to the console
and telephone interconnect are lost when the system is in site trunking.
Site Failsoft Losing all site controllers or losing all the control channel capable repeaters at a site
forces the site into Failsoft mode. Basically, there is no trunking functionality. In this
mode, and if programmed with Failsoft capability, the individual repeaters become
active (bring up their carrier) continuously. Individual radios can communicate in a
conventional manner on fixed channels. The radios receive a data word from their
repeater that instructs them to generate a tone at fixed intervals to indicate to the users
that the system is in Failsoft. Communication to the console and telephone interconnect
are lost when in failsoft.
Loss of Service Between Zones
Loss of service between zones is a more complex situation since a zone may be functional
overall, but lose contact with one or more of the other zones.
Interzone trunking is a state between any pair of zones in a system. In a four-zone system, see
Figure 9-16, there are six pairs of relationships between the zones in the system:
Zone 1 to Zone 2
Zone 1 to Zone 3
Zone 1 to Zone 4
Zone 2 to Zone 3
Zone 2 to Zone 4
9-64 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Conditions Necessary for Interzone Trunking
Zone 3 to Zone 4
Figure 9-16 Zone-to-Zone Service
Conditions Necessary for Interzone Trunking
For each zone pair, the following conditions must be in place for interzone trunking
to take place between the zones:
A functioning interzone control path between the zone controllers.
A functioning audio RP at each zone.
An identical talkgroup-to-home zone map in each zone.
If any of these conditions are not met, the zone pair cannot enter interzone trunking with each other.
The trunking state between zones determines how interzone calls are processed.
Interzone call processing is divided into two types of services:
Group-based services
Individual-based services
Group-based and individual-based services each have their own level of service availability,
based on their interzone trunking state.
6881009Y05-O April 2004 9-65

Interzone Group Service Availability Chapter 9: Advanced Call Processing
Interzone Group Service Availability

Table 9-7 describes three possible levels of service for group-based call requests in systems with three or more
zones. FullVision INM provides an indication of the interzone trunking state between each pair of zones but
there is no application that can indicate the level of service being provided. The information in Table 9-7 can
be applied to situations where the system appears normal but users do not have full access to their talkgroup.
Table 9-7 Levels of Group Service Availability
Service Level Description

Full Interzone All zones are in a state of interzone trunking with respect
to the groups home zone.
Reduced Interzone At least one participating zone is in interzone trunking
with the groups home zone, and at least one zone is not.
Zone Isolated The current zone may only process the groups calls
locally within the zone. This occurs when either the
participating zones have no interzone trunking with
the groups home zone, or when the home zone loses
interzone trunking with all the other zones in the system.
The three levels of group service availability are based on a group members perspective from the current
zone to every other zone in the system, and whether the current zone is the groups assigned home zone.
Example 1
It is possible for some members of a talkgroup to have zone isolated service for a short interval
during loss of the links between the zones (generally microwave).
In Figure 9-17, the microwave link between Zone 1 and Zone 3 is down
(interruption of interzone trunking), while the links between Zones 1 and 2,
and between Zones 2 and 3, are intact.
Talkgroup As home zone is Zone 1.
A user in Talkgroup A placing a call in Zone 1 or Zone 2 has full interzone service availability.
9-66 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Interzone Individual Service Availability
Talkgroup A members in Zone 3 will have zone isolated group service availability
for a short period of time while the exit routers reestablish the call through an
alternate IP path, in this case, through Zone 2.
Figure 9-17 Reduced Interzone Service Availability
Interzone Individual Service Availability

Interzone individual services do not have the same service availability concepts as group calls.
Interzone individual calls are always two-zone calls, with the controlling zone dynamically
assigned as the zone responsible for initiating the audio.
Conditions for Interzone Unit-to-Unit Calls
The following conditions must be in place for unit-to-unit calls to take place between the zones:
The two zones involved in the call must be in interzone trunking.
The call requestors zone must have, at minimum, an active zone controller to
zone controller interzone control path between itself and the target radios home
zone so it can access the target radios Individual HLR.
The target radios zone must have, at minimum, an active zone controller to zone
controller Interzone Control Path between itself and the requestors home zone
so it can access the requestors individual HLR.
Example 1
6881009Y05-O April 2004 9-67

Example 2 Chapter 9: Advanced Call Processing
In this example:
User 1 is in Zone 1, its individual home zone.
User 2 is in Zone 2, its individual home zone.
Zone 1 and Zone 2 are in interzone trunking.
In this case, all criteria are met (Figure 9-18).
Figure 9-18 Interzone Individual Call with Radios in Their Home Zones
Example 2
In a less commonly occurring example:

User 1 is in Zone 1 but its individual home zone is Zone 4.
User 2 is in Zone 2 but its individual home zone is in Zone 3.
To make an interzone individual call between User 1 and User 2 (Figure 9-19), the
following conditions must exist:
Zone 1 and Zone 2 must be in interzone trunking.
Zone 1 must have at least an Interzone Control Path to Zone 3.
9-68 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Zone Controller Switchover
Zone 2 must have at least an Interzone Control Path to Zone 4.
Figure 9-19 Interzone Individual Call with Radios Not in Their Home Zones
Zone Controller Switchover

The redundant MZC 3000 zone controller in each zone provides protection against a
hardware or software failure that may result in the loss of wide area trunking until the
zone controller is repaired or recovers automatically.
The MZC 3000 includes two controller chassis. One controller actively processes calls and manages MZC
3000 resources in the zone, while the other controller acts as a standby that can be brought online when the
active controller is being serviced or has an internal failure that causes the loss of wide area trunking.
6881009Y05-O April 2004 9-69

Automatic Switchover Chapter 9: Advanced Call Processing
The two controllers communicate with each other through the link connected directly between the
two or, should that link fail, through the links connected to the Ethernet LAN switch. The direct
link, also called the negotiating link, is used by the controllers to notify each other of their ability to
maintain the zone in wide area trunking mode and to negotiate the switchover should that action be
necessary. The Ethernet LAN switch establishes the connections between the controllers and the sites,
MGEGs, and Telephone Interconnect Devices (TIDs). Although both controllers can receive network
traffic, only one controller is actively in charge of the zone. Both controllers maintain links to the
Network Management Subsystem in order to report individual controller status.
The Redundant controller can be switched automatically or by user-initiated switchover. Automatic
switchover takes place upon internal failure that causes the loss of wide area trunking or loss of dispatch
operations. User-initiated switchover is performed from the ZCM application in the PRNM application
suite. In the event that access through ZCM is not possible due to failure, the Local User Terminal,
through the zone controller Administration menu, may be used to perform the switchover.
Performing a user initiated switchover from the local user terminal could have adverse
affects, like increased down time, on system operation and should only be used when
access through the ZCM application is not possible.
This section explains what causes an automatic switchover and how the system reacts when an
automatic switchover occurs and when a user-initiated switchover occurs.
For information about performing the user-initiated switchover, see Volume

3, Administering Servers and Controllers.
For information on configuring zone controller redundancy and switchover
see Volume 3, Managing Zone Infrastructure.
Automatic Switchover
Automatic switchover occurs when a failure event within the controller causes a loss of wide
area trunking for all sites or loss of dispatch operations. The failure event can be software- or
hardware-based. Table 9-8 is a partial listing of the major cards and components in the MZC
3000 that will directly cause an automatic controller switchover.
Table 9-8 Failures That Cause Automatic Switchover
Failure that Causes

Reference
Switchover
CPU card failure "CPU Card Failure" on page 9-72
Both Power Supplies fail In the event that both power supplies fail, there is no
source of operating voltages for any of the controller
cards; consequently, an automatic controller switchover
occurs.
Ethernet card failure "Ethernet Card Failure" on page 9-71
9-70 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Ethernet Card Failure
Table 9-8 Failures That Cause Automatic Switchover (Continued)

Failure that Causes
Reference
Switchover
Ethernet Transition card failure "Ethernet Transition Card Failure" on page 9-71
Manual disable from the Local "Manual Disable from the Local Admin Menu" on page
Administration menu 9-72
also see "User-Initiated Switchover" on page 9-73
Table 9-9 is a partial listing of the cards and components in the MZC 3000 that do not
directly cause an automatic controller switchover.
Table 9-9 Failures That Do Not Cause Automatic Switchover
Failure that Does Not

Reference
Cause Switchover
CPU Transition card failure "CPU Transition Card" on page 9-72
Single Power Supply failure "Single Power Supply Failure" on page 9-72
Hard disk failure "Hard Disk Drive" on page 9-73
CD-ROM failure "CD-ROM Drive" on page 9-72
The items in Table 9-9 do not directly cause an automatic controller switchover, however,
their failure may indirectly cause an automatic switchover if the failure of an item
in Table 9-9 causes a component in Table 9-8 to fail. (For example, the failure of a
CPU Transition card may cause a failure of the CPU card.)
Ethernet Card Failure

When the Ethernet card fails the controller is no longer able to communicate with the sites, TID,
MGEGs, and controllers in other zones. The primary negotiation link between the controllers is also
lost. When an Ethernet card fails, the controller automatically switches over.
Since the backup negotiation link is through the NMS link on the CPU card, communication
is still possible to the redundant controller and the NMS.
Ethernet Transition Card Failure

When the Ethernet Transition card fails the controller is no longer able to communicate with the sites,
TID, MGEGs, and controllers in other zones. The primary negotiation link between the controllers is also
lost. When an Ethernet Transition card fails the controller automatically switches over.
Since the backup negotiation link is through the NMS link on the CPU card, communication
is still possible to the redundant controller and the NMS.
6881009Y05-O April 2004 9-71

Manual Disable from the Local Admin Menu Chapter 9: Advanced Call Processing
Manual Disable from the Local Admin Menu

An automatic controller switchover will occur if the active controller is disabled from the
Local Admin Menu and the standby controller is able to support wide are trunking. This
action is not advisable due to the severe system impact of a switchover event. It is always
recommended to perform this function from the ZCM application.
Verify the health and status of the standby controller subsystem in FullVision before performing
any kind of User initiated switchover or action that results in a controller switchover.
CPU Card Failure

A CPU card failure affects all controller functions, consequently affecting all sites and causing a switchover.
Devices That Do Not Cause Switchover

The following sections describe the devices that do not cause switchover.
CPU Transition Card
When the CPU transition card fails, the controller loses connection to the Network Management
Subsystem (NMS), terminal server, and optional MOSCAD. The NMS link failure is reported
to FullVision INM. Without the terminal server connection, local admin terminal access is
lost. If the MZC 3000 uses the optional Unattended Shutdown through MOSCAD to shutdown
the controller during AC power loss, this capability is also lost.
Single Power Supply Failure
The controller only requires one power supply to run. Failure of a single power supply does not cause a
controller switchover, since the MZC 3000 zone controller cPCI chassis features redundant power supplies.
In the event that both power supplies fail, there is no source of operating voltages for any
of the controller cards; consequently, an automatic controller switchover occurs.
CD-ROM Drive
A failure of the CD-ROM drive does not cause a controller switchover since the CD-ROM drive
is only used to load controller operating software and patches.
9-72 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Tape Drive
Tape Drive
A failure of the tape drive does not cause a controller switchover since the tape drive is only
used to make a back-up copy of the zone local database or to restore the zone local database
in the event of a failure of the ZDS and a controller reset.
Hard Disk Drive
A failure of the hard disk drive does not cause a controller switchover since all of the necessary
information is loaded into Synchronous Dynamic Random Access Memory (SDRAM).
User-Initiated Switchover
Due to the severe system impact of a switchover event, user-initiated switchover

should be initiated ONLY when absolutely necessary.
User-initiated switchover is a feature that gives you the ability to disable the automatic switchover feature
and perform a user-initiated controller switchover. The feature uses the ZCM application. If the Network
Management link is down, and a user-initiated switchover still must be performed, switchover may be
done through the zone controller Administration menu through the Local User Terminal. User initiated
switchover is typically used when performing a software upgrade or performing maintenance such as
replacing a faulty field replaceable unit (FRU) that did not cause an automatic switchover.
Verify the health and status of the standby controller subsystem in FullVision
INM before performing a user-initiated switchover or take any kind of action
that results in a controller switchover.
System Behavior During Switchover
When an automatic switchover to the redundant controller is commanded, the fol-

lowing sequence of events take place:
1. A failure of any one of the items referred to in Table 9-8 on page 9-70 causes the standby
controller to compare its operational health against the health of the active controller. An
automatic switchover is initiated if the standby controller is capable of wide area trunking.
2. If the standby controller is capable of wide area trunking, the standby controller
informs the active controller, through the negotiation link, that it is going
active and the active must go to standby.
6881009Y05-O April 2004 9-73

System Behavior During Switchover Chapter 9: Advanced Call Processing
3. All sites in the zone lose connectivity to the controller and subsequently enter site trunking mode.
If the controller has malfunctioned, the switch to site trunking has probably already occurred.
4. All active wide area calls are ended including Talkgroup, Multigroup, Interconnect, Private,
and Emergency. The active talkgroup and emergency calls will revert to in-cabinet repeat
for ASTRO 25 Repeater sites and IntelliRepeater subsystems. Simulcast subsystems
will still simulcast within the subsystem. All console patches are lost.
5. All subscriber radios, upon receiving the site trunking system status Outbound Signalling
Packet (OSP), leave their current site and search for a site in wide area trunking. Since all
sites are in site trunking mode, the subscribers return to the original site and inform the
radio user of the site trunking mode through audible tone and, when so equipped, with a
visual indication. For more information see "Subscriber Scatter" on page 9-75.
6. The sites constantly send link requests to the controller. Once the newly active controller is
online, it acknowledges the link requests to bring the sites into wide area trunking.
7. As each site transitions to wide area trunking from site trunking, they transmit a wide area
System Status Outbound Signalling Packet (OSP) to inform the subscriber radios of the change.
The time duration to transition from wide area trunking to site trunking
and return to wide area trunking will vary depending on system size and
configuration but should take less that two minutes.
8. If the subscriber radios ended up on a site other than their starting point during their search for
a wide area trunking site, they will transmit an affiliation Inbound Signalling Packet (ISP).
9. The active controller begins gathering the current location of subscriber radios and
talkgroup members from the affiliation tables sent from the sites.
Only limited wide area services are available until the controller receives all of
the site affiliation tables. The time to recover the site affiliation information
will vary depending on the number of active subscribers, talkgroups, and the
number of sites in the system, but should be less that twenty minutes.
10. For multizone systems, if the active controller is the controlling zone for an interzone call,
it must also receive talkgroup affiliation information from the other zones before those
zones are included in call requests. The time required will vary depending on the number
of subscribers and talkgroups in the system but in general should be less than 25 minutes.
Prior to this being completed, interzone services to other zones may be affected.
9-74 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Possible Call Processing Behavior During Recovery
11. The newly standby controller resets and if it initializes in service mode, the controller
receives infrastructure, radio, and talkgroup information from the ZDS. This includes
all infrastructure, radio user, and talkgroup configuration information.
Possible Call Processing Behavior During Recovery

Table 9-10 lists the types of call processing disruptions that may occur during the recovery of the primary
controller. These disruptions could be caused by incomplete location and configuration data.
Table 9-10 Call Processing Behavior During Recovery
Call Type Possible Disruptions

Private Calls/Telephone Calls to a target subscriber radios whose affiliation is not
Interconnect Calls yet known to the controller will not be successful.
Talkgroup/Multigroup Calls Talkgroup members need to have at least one affiliated
member known by the controller at their site, to be
included in talkgroup calls.
Subscriber Scatter
All of the sites transition to site trunking mode regardless of whether a controller switchover is
automatic or user-initiated. The sites notify the subscribers of this change through a System Status
OSP. Upon receiving this OSP, the subscribers automatically start scanning the adjacent site list for
another site that is still in wide area trunking mode unless the site that the subscriber is currently
affiliated to is set to Always Preferred in the subscriber programming. When no wide area site is
found, the subscriber stops scanning and returns the original site.
Some subscribers can be affiliated at more than one site during controller switchover.
Multiple affiliations can occur if a radio happens to affiliate to a new site while the radio
is also searching the adjacent site list for a wide area site. Because connectivity to the
controller is temporarily lost during controller switchover, entries in some of the site
affiliation tables do not get updated to reflect subscribers who have changed sites. Normally
the controller de-affiliates subscribers when they roam out of a site, however, during a
controller switchover the communications path from the controller to the site is temporarily
unavailable preventing the controller from performing de-affiliation.
The site transitions to wide area trunking mode when the site re-establishes a link with the controller.
The site then notifies the subscribers of the change through System Status OSP.
The wide area feature called Dynamic Site Assignment requires that the controller have up-to-date
affiliation tables. All sites need to upload the affiliation tables to the controller. After the controller receives
all of the uploads from the sites, it will look through the compiled affiliation table for subscribers that
are registered on more than one site. If the controller finds duplicate affiliations it will request, through
all sites where the subscriber shows affiliations, that the subscriber re-affiliate. This must happen before
Dynamic Site Assignment can guarantee all intended parties are included in the call.
6881009Y05-O April 2004 9-75

Switching Back to the Standby Controller (User Initiated) Chapter 9: Advanced Call Processing
The length of time it takes to update the affiliation tables depends on the number of sites,
subscribers, and talkgroups in the system, but in general it should be less than twenty minutes
from the time the first site transitions back to wide area trunking.
As with subscribers, console affiliations must also be sent to the controller from all CEBs within the
zone. This happens within the fist few minutes after the switchover occurs.
For a given talkgroup to be monitored by the dispatch subsystem, at lease one console
affiliation must be received for that talkgroup. After that, all CEBs with console operator
positions monitoring that talkgroup can receive the audio.
Switching Back to the Standby Controller (User Initiated)
Do not switch back to the standby controller until the Infrastructure database has been
downloaded from the Zone Database Server (ZDS) or the system will remain in site trunking
until the Infrastructure database has been downloaded. The download time will vary by
system configuration, but in general should take less than 10 minutes.
If for some reason the newly active controller is not functioning properly, you may need to switch
the standby controller back to active. This is considered a double switchover. The following is
a description of what occurs when performing a double switchover before the standby controller
has received the user configuration database from the ZDS.
Infrastructure Database Download
The Zone Database Server contains infrastructure information such as the configuration information
for the site and channel capabilities. The standby, reset controller will not have any knowledge of
infrastructure objects until the database has been loaded into the controller memory.
There is no indication that the download has completed other than the controller
state changing to enabled idle or enabled active.
The controller begins acknowledging the link requests from the sites once the database is downloaded. A link
request contains information such as the site ID. The controller checks the site ID against the information in the
database and requests the sites capabilities. The controller instructs the site to transition to wide area trunking
if the capabilities are normal. The controller then requests the affiliation tables for subscribers and talkgroups.
This operation is performed for every site in the system. The controller handles multiple sites simultaneously.
SZ$INIT Initialization Records
The Initialization state occurs after the controller powers up or after a reset. It is the state where the
infrastructure database has already been downloaded from the ZDS, but the subscriber database has not.
The controller starts handling wide area calls after initialization and infrastructure download; however,
the subscriber and talkgroup records from the database are not available for call processing.
9-76 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Radio User and Talkgroup Record Download
During this time, the controller uses the SZ$INIT records for any unrecognized subscribers or talkgroups. The
SZ$INIT records define the default access that should be available during a failure or initialization.
As records are downloaded from the ZDS, the controller begins granting privileges according to the
subscribers configuration records and associated profiles. After all records have been downloaded and the
zone has returned to normal operations, the zone controller begins using SZ$DEF records as the default access
for any subscribers or talkgroups that are not recognized as part of that zones Home Zone map, provided
that the Default Subscriber Access field in the UCM is set to YES. If Default Subscriber Access is set
to NO, any ISPs received from subscribers and talkgroups without records will be rejected.
The controller replaces the default records with the permanent records as it receives
them from the UCS through the ZDS.
Radio User and Talkgroup Record Download
After the Infrastructure database has been downloaded and the channel capabilities have been
verified, the NMS begins sending subscriber and talkgroup records to the zone controller. The time
required for this download varies depending on the number of subscribers and talkgroups in the
system. Typically, this will take approximately thirty minutes for a system with 15,000 subscribers.
A system with 64,000 subscribers could take as long as two hours.
Zone Controller States
The zone controllers can be in one of the following states depending on the health of the MZC
3000 and what is happening in the ASTRO 25 system.
6881009Y05-O April 2004 9-77

Zone Controller States Chapter 9: Advanced Call Processing
Table 9-11 describes the zone controller operating modes and Table 9-12 describes
the zone controller operating status.
Table 9-11 Zone Controller Operating Modes
Mode Viewed From Definition

STANDALONE Local Admin Menu ZDS is not communicating with the zone controller
INTEGRATED Local Admin Menu ZDS is communicating with the zone controller
Table 9-12 Zone Controller Status
Status Viewed From Definition

ENABLED_ACTIVE FV/INM & Local Admin The active zone controller is running and has been fully
Menu loaded by the database server.
ENABLED_IDLE FV/INM & Local Admin The standby zone controller is running and has been fully
Menu loaded by the database server.
STANDALONE_ACTIVE FV/INM & Local Admin The active zone controller is running, has not been loaded
Menu by the database server and is operating off the local
database because it is not connected to the ZDS.
STANDALONE_IDLE FV/INM & Local Admin The standby zone controller is running, has not been
Menu loaded by the database server and is operating off the
local database because it is not connected to the ZDS.
REMAPPING_ACTIVE FV/INM & Local Admin The active zone controller is running and reception of
Menu Home Zone mapping tables from the database server
is not yet complete. System is running with Default
subscriber access = yes.
REMAPPING_IDLE FV/INM & Local Admin The standby zone controller is running and reception of
Menu Home Zone mapping tables from the database server
is not yet complete. System is running with Default
subscriber access = yes.
LOADING_ACTIVE FV/INM & Local Admin The active zone controller is running and receiving
Menu mapping tables, subscriber talkgroup records, and other
data from the database server.
LOADING_IDLE FV/INM & Local Admin The standby zone controller is running and receiving
Menu mapping tables, subscriber talkgroup records, and other
data from the database server.
UNKNOWN FV/INM & Local Admin Zone controller is connected to the NMS.
Menu
ENABLING_ZC Local Admin Menu Zone controller is coming up. This is a transition state
that normally is not seen.
DISABLING_ZC Local Admin Menu Zone controller is going down. This is a transition state
that normally is not seen.
UNCONFIGURED Local Admin Menu Initial state upon powering up.
9-78 6881009Y05-O April 2004

Chapter
10
Integrated Voice and Data

Integrated Voice and Data (IV&D) is a feature available with your Motorola ASTRO 25 trunked
communication system providing voice and data communication services integrated into one
trunked communication system. IV&D involves the IP transport of voice and data over trunked
data channels that are in the same channel pool as the voice channels.
Integrated Voice & Data Introduction

The IV&D feature of the ASTRO 25 trunking communication system provides a wireless extension
of your data network through the radio communication network to mobile data devices. Data
travels between your fixed wireline network and the wireless clients on the Motorola ASTRO 25
communication network. Figure Figure 10-1 shows the logical communication interface between
ASTRO 25 system components and your data enterprise network.
6881009Y05-O April 2004 10-1

Packet Data Channel Chapter 10: Integrated Voice and Data
Figure 10-1 Integrated Voice and Data Communication Interface Diagram
Packet Data Channel
A packet data channel (PDCH) refers to the radio frequency resources used for the IP transport of data in
an ASTRO 25 trunked communication system. The characteristics associated with the IP transport and
handling of a PDCH are similar to those associated with the IP transport of voice over radio frequency
resources, however, there are differences. For instance, while the zone controller processes voice call
requests from subscriber radios and tracks which subscribers are using channel resources for voice calls,
the site controller keeps track of which subscribers are using data channel resources for data calls.
As long as a subscriber radio stays in its home zone, a site controller in the home zone
can track the subscriber radios using data channel (PDCH) resources.
10-2 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Trunked Data Service Capabilities
Trunked Data Service Capabilities
Trunked data service is capable of supporting the following:
Operation in the 800 MHz frequency bands, 9600 baud communications

Operation in up to seven zones; 100 sites per zone
Up to 20,000 active data subscribers
A data call capacity of 300,000 data calls per hour
Support for up to three PDCHs per site (configurable) a minimum of one PDCH per site
From one to 60 users per channel (configurable)
Potential total capacity for 180 data capable subscriber radios per site with 3
data channels at a site and 60 subscriber units per channel
Industry standard protocols Subnetwork Dependence Convergence Protocol
(SNDCP), Virtual Private Network/Internet Protocol (VPN/IPSec), Dynamic Host
Control Protocol (DHCP), Point-to-Point Protocol (PPP)
Industry standard services such as static and dynamic IP addressing, IP fragmentation
and Internet Control Message Protocol (ICMP) error reporting
Network Address Translation (NAT) to coordinate Radio Network Infrastructure
IP plans and outside network infrastructure IP plans.
Unicast transmissions only
Confirmed delivery of messages
General Packet Radio Service (GPRS) Tunneling Protocol (GTP)
IV&D Hardware Components

The following components are specifically designed to support the IVD feature:
Zone controller
Packet Data Gateway (PDG)
GPRS Gateway Support Node (GGSN) router
Site controller
Subscriber units (data-capable)
FullVision INM server
Network manager
6881009Y05-O April 2004 10-3

Zone Controller and IV&D Chapter 10: Integrated Voice and Data
Zone Controller and IV&D
The zone controller supports and manages channel resource allocation for both voice and data. From
the data services perspective, the zone controller provides the following functions:
Responds to the Home Location Register (HLR) query by the PDR to obtain zone
affiliation information (subscriber location) and subscriber status information.
Responds to Visitor Location Register (VLR) of the RNG module to obtain
site affiliation information. In addition, registration, de-registration, site roaming
and zone roaming information is communicated from the zone controller to the
RNG for processing data service requests.
Assigns a 9600 baud channel as a data channel and allocates the channel to the base
station. A subscriber radio communicates with the PDG over this channel.
Tracks the number of active data channels at a site.
Manages and enforces channel preemption rules.
Maintains data channel lease with the site controllers.
Maintains the busy queue for data channel request from the sites.
Provides mobility management functions for each MSU.
Allocates and manages radio channel resources and determines which
channels are used as the PDCH.
Determines PDCH pre-emption based on preemption rules. Provided that the system-wide
Data Channel Preemption parameter is set, the TG can preempt data parameters.
Maintains Busy Queue for data channel requests from site. PDCH requests
follow existing priority levels for call processing.
A data channel is busied when either of the following occurs: all voice channels are
in use, the maximum number of data channels at the site has been reached, or when
none of the available channels are sub-band restricted.
Zone Controller and Air Traffic Information Access Data Call Information
The zone controller provides data call information to the Air Traffic Information Access (ATIA)
data stream. This data call information includes the following:
Start of the data call Data channel request granted

Data call reject Data channel request rejected
Data call busy Data channel request busied
End of data call Data channel de-assigned
Cancel of data channel request Data channel request cancelled
Renew data channel request Data channel request renewed
10-4 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Packet Data Gateway
Packet Data Gateway
The PDG is a hardware and software platform used to link a customers data network
to the Motorola ASTRO 25 RF network.
The PDG is a CompactPCI device with the following components:
Packet Data Router (PDR) processing module

Radio Network Gateway (RNG) processing module
Chassis a CompactPCI chassis housing two power supplies and cooling fans
A SCSI hard drive connected to the PDR
A SCSI CD-ROM drive connected to the PDR
One PDG is required for each zone.
Packet Data Router
The PDR is one of two processing modules in the PDG. The PDR manages all aspects of the IP protocol
and provides a logical interface between the GGSN router and the RNG module. (The RNG module
provides a logical interface to RF subsystems). The PDR provides the following functions:
Receives and maintains HLR information from the zone controller to identify a
subscribers home zone location for processing data calls.
Interfaces with the RNGs within its zone and RNGs in other zones in the system.
Maintains database of data-capable mobile subscriber units (MSUs) that are in
its home zone (based on home zone mapping).
Controls routing of data messages. Routing information for attached users is
stored by the PDR and used to tunnel user payload data to an MSUs current
point of attachment, which is the serving RNG.
Manages context activation and deactivation. Authorizes and approves context activations
based on provisioned, as opposed to requested value validation and other processing.
Determines when context deactivation for an MSU is needed. Example
triggers include the following:
Deactivation by the GGSN. The PDR deactivates the mobile if the
GGSN deletes the context.
Subscriber powers off. The PDR deactivates the mobile if the power is turned off.
Change or deletion of MSU provisioning information.
Queries the zone controllers HLR to determine MSU status and location affiliation.
6881009Y05-O April 2004 10-5

Radio Network Gateway Chapter 10: Integrated Voice and Data
The term home PDR or servicing PDR refers to the PDR that contains provisioned
information for a particular mobile subscriber radio.
The RNG is one of two processing modules in the PDG. The RNG provides a logical interface between the local
RF resources and the PDR to support data calls to subscriber radios. The RNG provides the following functions:
Maintains a database of context activated MSUs registered in the zone. The database is based
on MSU location and not home zone affiliation. For every MSU location update, the local
zone controller pushes VLR information to the local RNG to provide routing information
to the packet data service. By doing this, the RNG tracks MSU mobility to the site.
Validates inbound data messages for errors, then generates an acknowl-
edgement (ACK) or SACK.
A serving RNG refers to the RNG in the zone in which a radio is currently
located and being serviced. The term co-resident RNG is used to identify the
RNG located in the same zone as the PDR.
GPRS Gateway Support Node Router
The GGSN interfaces between the Motorola Radio Network and the Customer Enterprise Network
(CEN). It provides the following support functions for IV&D:
Isolates customer wireline and wireless network traffic from the Motorola RF network
Facilitates the use of a customers DHCP servers and IP plan
Isolates customer agencies from each other
The GGSN maintains routing information for all attached packet data users. This routing information
is used to tunnel (via GTP) user datagrams to each MSUs current point of attachment, which
is the home PDR, and to customer hosts (through IP-IP tunnels).
Site Controller
The site controller functions as a data site controller having trunked data resource allocation functionality.
The following list characterizes the data functionality responsibilities of the site controller:
10-6 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Mobile Subscriber Units
Processes inbound and outbound data requests at the site. (The zone
controller handles ISPs for voice calls).
Requests new data channels (those PDCHs not already allocated for the
site) from the zone controller.
Routes data between the PDCH and RNG.
Provides control and routing between the RNG and base radio.
Uses the manager-owed Voice Grant Filter parameter to control urgency of voice
channel grants to preempt ongoing data calls (enabled or disabled).
Controls RF channel access and load control for the PDCHs currently associated with the site.
Interfaces with the base radios at the site to manage outbound RF channel queues and
to allow prioritized access for control signaling over the PDCH.
Determines and advertises the current status of the PDCH at the site data channel
announcement (OSP) and system service class (OSP and LCs).
Maintains a database of active data users at the site (which includes group affiliation).
Maintains a busy queue for data users.
Controls the number of users permitted on a PDCH. Range is one to
60, configured by the manager.
Maintains data channel lease with the zone controller.
The following conditions relating to the SSC require data requests to be reactivated. When any of these
conditions exist, data channels are dropped and subscriber radios need to reactivate data requests.
The site controllers at a site switch operating modes (active to standby or standby to active).
Active site controller (ACS) contention occurs..
Both site controllers are not on the same VLAN (as is required during software download).
A data channel failure occurs.
The site controller characteristics, listed above, are common to either the simulcast site
controller or PSC 9600 site controller, unless otherwise specified.
Mobile Subscriber Units
MSUs terminate the SNDCP tunnel, implement service interaction rules, provide IP bearer
service processing, and provide an interface between a mobile computer and the radio
network. The MSU performs the following functions:
Monitors status of data service (that is, data channel announcement and system service class).
Monitors the control channel for autonomous access status.
6881009Y05-O April 2004 10-7

Integrated Voice and Data Theory of Operations Chapter 10: Integrated Voice and Data
Manages context. (Initiates context activation - based on configuration,

and renews active context when needed).
Communicates with a mobile computer through PPP.
Monitors voice call LCs for activity on affiliated talk groups while on the PDCH.
Departs the PDCH if the PTT is pressed or if the talk group changes. PDCH departure
depends on MSU configuration (RX voice interrupts data).
Provides a platform to run Network Address Translation (NAT) service, which permits
the MSU to support multiple applications with one context.
Generates and sends ICMP error notifications to a mobile computer.
These include the following:
Message Lifetime Expiration
Not Context Activated
Site Trunking
Service Interaction
Integrated Voice and Data Theory of Operations

The ASTRO 25 trunking communication system involves the coordination of various system components
specifically designed and configured to successfully process the data request with available system resources.
These system resources require the attention of specific system components and include the
PDCH resources allocated to participate in the process.
Context Management for Data Services
Context management includes the activities to establish hardware and software configuration parameters for
system components supporting data calls, the context activation process used to provide data services in an
ASTRO 25 IV&D communication system, and the context deactivation process to tear-down a data call.
It is the role of the systems fixed network equipment (FNE) to implement the
context activation and context deactivation process.
10-8 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Context Configuration
Context Configuration
Context configuration involves establishing hardware and software configuration parameters for system
components supporting data services. For example, this includes using the Customer Programming
Software (CPS) to configure subscriber units, using network management applications to configure
manager-owned parameters for the PDG (PDR and RNG), and using InfoVista to establish access point
and virtual private network (VPN) parameters to configure the GGSN router. For more details on context
configuration, see "IV&D Configuration Management Overview" on page 10-13.
Context Activation
Context activation is the process by which data call registration and service activation is
implemented by the ASTRO 25 IV&D communication system.
Context activation is achieved when a subscriber radio uses the control channel to identify the availability
of a data channel (see "Accessing the PDCH" on page 10-9 for more details) and a PDCH is made
available to the subscriber for data services. Context activation begins as the PPP link is established
between a data device and subscriber radio. Over the PPP link, the data device sends an IP message
(addressed to the host where the data resides) to the subscriber radio. During context activation,
various resource allocation timers and data service timers begin to monitor the status of the context
until the context is deactivated. (See "Context Deactivation" on page 10-9.
Context Deactivation
Context deactivation occurs when resource allocation timers, data service timers, or data service
configuration parameters dictate that the data call is to be deactivated. See "IV&D Configuration
Management Overview" on page 10-13 for more details about these timers and parameters. Context
deactivation can also occur upon an equipment failure or other similar condition.
Accessing the PDCH
There are two methods for accessing the PDCH, depending on the state of PDCH availability,
requested access and autonomous access.
Requested Access
Requested access by a subscriber radio for a PDCH is necessary when a PDCH is not already set up and
available for the site, and therefore, a request for a PDCH is established. When a subscriber radio requests a
PDCH, it is processed by the site controller. If necessary, the site controller will request a PDCH grant from
the zone controller. When the site controller or zone controller responds with a PDCH grant, the site controller
can assign any outstanding requests (there could be more than one request) until the resource is full.
Autonomous Access
Autonomous Access for data services occurs when a PDCH is already set up and available for a site and
the subscriber radio has automatic access to the PDCH. While a PDCH is set up, PDCH availability is
identified on the control channel at the site. If a subscriber radio needs the PDCH, the system provides the
radio immediate access to the PDCH. Therefore, in this case, a controller does not need to allocate a PDCH
and identify the availability of the PDCH on the control channel since this is already accomplished.
6881009Y05-O April 2004 10-9

Inbound and Outbound Data Calls Chapter 10: Integrated Voice and Data
Inbound and Outbound Data Calls
The direction of a data call is described from the subscriber radio perspective. An inbound
data call is a call that initiates from the subscriber radio and travels over the air and through the
infrastructure to a host computer. Conversely, an outbound data call is one that travels from the
host, through the infrastructure, and over the air to the subscriber radio.
Inbound Data Request
Process 10-1 describes an inbound data request from a data device and mobile subscriber
unit in a home zone and provides a description of requested access and autonomous access
for obtaining PDCH resources as necessary.
Process 10-1 Inbound Data Request Process
1 An MSU establishes a PPP link to a data device. Over the PPP link, a data device
sends a request for data in the form of an IP message to its MSU. The IP message
contains the IP address of the host where the data resides.
2 The MSU receives the data request message from the data device and while
listening on the control channel, attempts to register for data services, a process
called context activation. Context activation involves obtaining an IP address
(static or dynamic) and uniquely associating it to a logical connection between
the host and data device through the MSU.
3 Requested Access: The subscriber unit checks the current data status at the site
to determine the method of PDCH access required. If a PDCH is not currently set
up or available at the site, a request is sent from the subscriber unit to the site
controller (requested access) for a PDCH. If necessary, the site controller requests
a resource grant from the zone controller.
Autonomous Access: When the control channel at the site is advertising that
a PDCH is currently set up and available at the site, the subscriber unit has
autonomous access to the PDCH and therefore no separate PDCH request is
necessary (autonomous access).
4 Requested Access: When the zone controller grants a data channel request, it
communicates this information to the site controller. The site controller tracks
which MSUs are granted access to the PDCH. The site starts a channel lease
operation by sending PDCH renew messages for the channel allocated to data,
every five minutes.
Autonomous Access: The site controller tracks which MSUs are granted access
to the PDCH.
5 The MSU, upon notification that a data channel is available, formats the IP
message from the data device in APCO CAI format (an IP datagram) and
transmits it to the RNG at the site.
6 The RNG receives a page from the site controller indicating that the MSU is on
the PDCH. The page starts the page ready timer.
7 The RNG acknowledges receipt of the data request with an ACK to the MSU.
8 The PDR removes the encapsulation set by the RNG, adds GTP encapsulation
around the data request, then forwards the data request to the GGSN router.
10-10 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Outbound Data Request
Process 10-1 Inbound Data Request Process (Continued)

9 The GGSN router removes the encapsulation and sends the data request to the
host or default gateway of the data enterprise network.
10 Context deactivation occurs when resource allocation timers, data service
timers or data service configuration parameters dictate that the data call is to be
deactivated.
Outbound Data Request
Process 10-2 describes a data request from a customer network to the mobile subscriber and data device
in a home zone employing the requested access method for obtaining PDCH resources.
Process 10-2 Outbound Data Request Requested Access
1 A host computer on a data enterprise network sends an IP datagram addressed to

a data device through the peripheral network (or DMZ) to the GGSN router.
2 The GGSN router sends the IP datagram to the PDR in the home zone of the MSU.
3 The PDR uses the home location registration database to determine the location
of the MSU, encapsulates the datagram, and forwards it to the serving RNG (the
RNG servicing the MSU at the MSUs current location).
4 Using the control channel, the RNG sends notification (a page) to the site
controller currently responsible for the MSU of the data request destined for the
data device linked to the MSU.
5 The MSU answers the page on the control channel and notifies the site controller
that it received the page.
6 The site controller informs the servicing RNG that the MSU is on the PDCH.
7 The RNG creates the APCO signaling with the data, sends it to the site, and the
data is transmitted from the site out to the MSU.
8 The MSU receives the data and sends an ACK back to the RNG where it is
forwarded to the home PDR.
9 The data is then sent over the PPP link from the MSU to the RS232 port of the
data device linked to the MSU.
6881009Y05-O April 2004 10-11

IV&D Fault Management Overview Chapter 10: Integrated Voice and Data
IV&D Fault Management Overview

Each PDG (one in each zone) sends fault and status information in the form of SNMP traps to the FullVision
INM server in that zone and provides the information to the FullVision INM topology map.
Fault and status information from the PDG comes from the PDR. Table 10-1 lists the
status/conditions reported to FullVision INM.
It is the role of the PDR to report faults. Some faults reported by the RNG to
the PDR are routed to the network manager.
Table 10-1 Packet Data Router and Radio Network Gateway FullVision INM Reporting
PDG Module or Link (Object) State or Conditions Reported

Packet Data Router Enabled, Overloaded, Restarting
Packet Data Router to Radio Network Link Up or Down
Gateway Link
Packet Data Router to Zone Controller Link Up or Down
Packet Data Router to GGSN Router Link Up or Down
Radio Network Gateway Enabled, Restarting
Radio Network Gateway Communication Reachable or Unreachable
Radio Network Gateway to Zone Controller Link Up or Down
Link
Radio Network Gateway to Site Link Link Up or Down
Fault and state change information originating from the PDR and RNG are received by the Zone
Database Server (ZDS) and available to the FullVision INM server in the zone where they are
displayed on the FullVision INM topology map for review and analysis.
Typically, the ZDS polls the PDR and RNG to obtain status information. However,
the PDR does not respond to the ZDS poll when the PDR is restarting since the PDR
agent and application are not running during this time. Therefore, the PDR sends the
Restarting trap to the ZDS at the time of restart and but does not respond to a ZDS
poll until after the restart when the state becomes Enabled.
10-12 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System IV&D Configuration Management Overview
The PDR actually responds to polls from the network manager to obtain the state of the RNG, RNG
communication object, RNG to zone controller link, and RNG to site link. The PDR is aware of RNG status
and when polled for RNG states, it relays the last known state of the RNG to the network manager.
The network manager allows you to set the state of the PDR or RNG module to Restarting by sending a
"Restart" request. When the PDR or RNG restarts, the Restarting state is reported in the form of traps.
The PDR maintains a separate and local 30-day log of the events resulting in traps being forwarded.
IV&D Configuration Management Overview

Data system configuration parameters, established to support data services for the ASTRO 25 IV&D
communication system, include parameters established in the User Configuration Manager (UCM), data service
timers, and configuration parameters specifically associated with system components supporting data service.
Data System Configuration Parameters
Data system configuration parameters established in UCM to support data services for the ASTRO 25
integrated voice and data communication system include the parameters listed in Table 10-2.
Table 10-2 Data System Configuration Parameters User Configuration Manager
Data System Parameter Description Range and Default Value

Data Channel Preemption Indicates whether preemption of a data Range: Enabled or Disabled
channel is allowed on a systemwide basis. Default: Disabled
Users Per Data Channel Limits the number of users permitted on a Range: 160
PDCH. Default: 35
Data busy Queue Priority Indicates the priority level a PDCH request Range: 210 (with 2 being the highest
Level has in the busy queue. priority)
Default: 10
Voice Grant Filter Enabled enforces the rule that voice activity Range: Enabled or Disabled
must start within 2 seconds of call initiation. Default: Enabled
Disabled gives data priority over voice
activity.
Message Life Timer Sets the limit on how long an outbound Range: 15 60 sec.
message is permitted to remain active. When Default: 25 sec.
the this timer expires, the data message is
removed from the queue and an Internet
Control Message Protocol (ICMP) message
is generated.
6881009Y05-O April 2004 10-13

PDCH Resource Allocation and Data Service Timers Chapter 10: Integrated Voice and Data
Table 10-2 Data System Configuration Parameters User Configuration Manager (Continued)
Data System Parameter Description Range and Default Value
Ready Time Delta Used in combination with the Ready Timer Range: 2 20 sec.
specified for a subscriber radio to determine Default: 3 sec.
the Ready Timer value forwarded to the
subscriber radio during context activation.
Page Wait Timer Used to determine how long the RNG will Range: 5 50 sec.
wait for a indication that a subscriber radio Default: 10 sec.
has gained access to a PDCH in response to a
page for an Outbound data session.
Standby Timer Determines how long a subscriber radio can Discrete Range: 1, 2, 4, 8, 12, 24, 48, 72 hrs.
maintain an active context. Default: 12 hrs.
Mobility Query Determines how many mobility query Range: 1 to 10 sec.
retries the PDR or RNG will perform before Default: 1 sec.
indicating the user location is unknown.
Outstanding Queries Determines the number of outstanding Range: 1 to 5 queries
mobility requests to the zone controller that Default: 5 queries
the PDR or RNG is allowed to have at any
point in time.
GTP T3 The time interval between retries when PDR Range: 1 to 30 sec.
sends a signaling request to the GGSN. Default: 4 sec.
GTP N3 The maximum number of attempts when Range: 1 to 7
PDR sends a signaling request to the GGSN. Default: 4
Logical Link Control Used to set the no response to a fully Range: 1 to 10 sec.
(LLC) timer transmitted LLC data segment. Default: 4 sec.
LLC Attempts Determines the number of LLC retry attempts Range: 1 to 7
the RNG will perform on a data segment. Default: 4
Talkgroup/Multigroup Indicates whether a group is allowed to Range: Enabled or Disabled
Preemption preempt a data channel. Default: Disabled
Maximum number of Limits the number of channels that can be Range: 13
PDCHs per site. allocated for data. Default: 1
Access Point Name Indicates the IP domain name used for IP Domain name
routing user data to the customer network
infrastructure.
PDCH Resource Allocation and Data Service Timers
To maximize the efficient use and optimal performance of system components and channel resources, resource
allocation timers and data service timers monitor and react to system conditions to accomplish this objective.
The PDCH resource allocation timers are non-configurable, hard-coded timers used
at the site and at the zone controller.
10-14 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System PDCH Resource Allocation and Data Service Timers
Table 10-3 provides a description of the PDCH resource allocation timers for the system.
Table 10-3 PDCH Resource Allocation Timers
Timer Description Default Value

Tz Zone Controller PDCH Lease Timer 11 minutes
Ts Site PDCH Lease Timer 5 minutes
Trsp Site Retry Timer for PDCH resource request 1 second
Tbusy Site Busy Timer for busy pending state 1 minute
Data service timers used to manage data service operations are found in Table 10-4.
Table 10-4 Description of Data Service Timers
Data Service Timer Description

Ready Timer The Ready Timer determines how long a subscriber radio will remain on the PDCH after
data service activity.
Default Ready Timer The operation of the Default Ready Timer is similar to that of the Ready Timer except that
it is only used when a Ready Timer has not been negotiated between the MSU and Fixed
Network Equipment (FNE). Upon successful context activation, the Default Ready timer is
replaced with the negotiated Ready timer.
Standby Timer See "Data System Configuration Parameters" on page 10-13.
New User Timer The New User timer is a calculated timer which monitors the time the RNG is waiting for the
(calculated) PDR to perform a New User action. When the New User Timer expires, the RNG deletes the
MSU record and discards any related data. This parameter is calculated using GTP T3 and
GTP N3. See "Data System Configuration Parameters" on page 10-13.
Mobility Timer The Mobility Timer in the PDR is used during a mobility change and context activation,
(hard-coded) in case the PDR could not complete the new user transaction (due to lack of delete user
response from old RNG, or lack of add user response from new RNG). When the Mobility
Timer expires, the specified action varies based on current state of the new user transaction.
Set at 5 seconds.
Page Wait Timer See "Data System Configuration Parameters" on page 10-13.
PDCH Holdoff Timer The PDCH Holdoff Timer is used in the RNG when a PDCH is assigned. This timer prevents
the RNG from sending data to the MSU before it can reach the PDCH. When the PDCH
Holdoff Timer expires, the RNG is allowed to send LLC data to the MSU.
Response Wait Timer The Response Wait Timer is used in the MSU while there is an outstanding request for a
PDCH (Normal or Reconnect). When the Response Wait Timer expires, the channel access
has failed. The MSU discards the datagram, and returns to the Standby state.
Update Location Timer The Update Location Timer (HLR Update Timer) is used in the PDR during a context
(HLR Location Timer) activation request, while waiting for a response from the PD-HLR. When the HLR Update
(hard-coded) Timer expires, the context activation has failed, and the PDR generates a New User Response
to the RNG, with a PD-Registration-Reject attached. Set to 21 seconds.
MM QueryTimer The MM Query Timer is used in the RNG and PDR while requesting mobility information
from the zone controller. When the MM Query timer expires, the RNG or PDR retries the
query once. If the retry fails, the message is rejected.
6881009Y05-O April 2004 10-15

Subscriber Radios Configuration Overview Chapter 10: Integrated Voice and Data
Table 10-4 Description of Data Service Timers (Continued)

Data Service Timer Description
Subscriber Update Timer The Subscriber Update Timer is used in the PD-HLR while inserting the subscriber data into
(calculated) the PDR. This timer is also used in the PD-HLR while deleting subscriber data from the PDR.
When the Subscriber Update Timer expires, the PD-HLR may retry the subscriber update
(depending on the application layer reliability algorithm). This parameter is calculated using
GTP T3 and GTP N3. See "Data System Configuration Parameters" on page 10-13.
MIP Timer The MIP Timer is used in the PDR when a message has been sent to the RNG. If no response
is received from the RNG, the MIP timer expires. When the MIP timer expires, the PDR
removes the message from the queue and generates an ICMP message. The remainder of the
outbound IP queue is then flushed.
PD Activate Wait Timer The PD Activate Wait Timer is used in the MSU while waiting for a response to a Context
Activation Demand. When the PD Activate Wait Timer expires, the MSU determines that it
has failed to activate the context. The MSU then responds to the application with a NAK to
the Configure Request. The PD Activate Wait Timer is started after receiving a CAI ACK
that the SNDCP Packet Data Context Activation message has arrived at the FNE.
SNDCP Queue Dwell-time The SNDCP Queue Dwell-time Timer is a mechanism to determine if an SNDCP message
Timer (while in queue) has exceeded the configured maximum dwell-time. When SNDCP messages
are placed in the SNDCP queue in either the MSU, or the PDR, a timestamp of the time
at which the message is queue is tagged onto the message. When SNDCP messages are
de-queued, a verification takes place. The SNDCP Message Timestamp + Maximum SNDCP
Dwell-time is verified to be greater than the current time when the SNDCP message is
de-queued. If the message fails this verification (for example, the message was queued
beyond the aforementioned time limit), the message is discarded (as are all messages in the
queue). Also, each message has an ICMP non-delivery notification generated for it (given
that the message is an actual IP datagram and not an ICMP message).
Subscriber Radios Configuration Overview
Data-capable subscriber radios contain a variety of configuration parameters used to support

integrated voice and data in the ASTRO 25 communication system. Table 10-5 provides an
overview of the configuration parameters you can establish for a data capable subscriber radio
using CPS, the software used to configure a subscriber radios.
Table 10-5 Subscriber Radio Configuration Parameters in CPS for IV&D
Configuration Parameter Description

Subscriber IP Address The subscriber radio IP address when communicating to a mobile computer while
running CPS or when NAT is disabled.
Mobile Computer IP Address The IP address of the mobile computer when the link is setup between the subscriber
unit and mobile computer. Network address translation (NAT) is to be enabled, not
disabled.
Disable NAT NAT is to be enabled, not disabled. When network address translation is enabled, the
system assigns an IP address to the mobile computer.
SNMP Traps When selected, status messages are sent to the mobile computer.
10-16 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Packet Data Gateway Configuration Overview
Table 10-5 Subscriber Radio Configuration Parameters in CPS for IV&D (Continued)
Configuration Parameter Description
Context Deactivation Alert Tone When selected, an alert tone is generated when the radio has context deactivated.
Terminal Data Enables or disables terminal data.
SNDCP Queue Dwell Timer This value represents the amount of time an IP datagram will remain in the SNDCP
(sec) queue.
Rx Voice Interrupts Data When enabled, Rx voice has a higher priority than data and will interrupt the data
session. When disabled, the Rx voice will not interrupt a data session.
Packet Data Capable System Enables or disables packet data.
Common Air Interface timers These configuration parameters are established to set limits on CAI threshold timers.
and thresholds For more details on these parameters and for hardware and software encryption
parameters, see the CPS manual or see ASTRO 25 Trunked Integrated Voice and Data
System Release 6.4/6.4 SE Managing Secure Communications (6881009Y65).
With NAT enabled, the mobile computer IP address field (in the CPS software) becomes invalid
and the mobile data computer is assigned an IP address by the system.
Packet Data Gateway Configuration Overview
Local configuration of the PDR and RNG modules in the PDG is accomplished by accessing the
PDG through the serial port connection of through a telnet session. The Configuration/Service
Software (CSS) does not support configuration of the PDG.
For detailed installation and local configuration of the PDG, see Volume 9, Master
Site Hardware Installation and Configuration.
The PDR and RNG software objects are created in the Zone Configuration Manager (ZCM) after PDG
hardware and software installation is complete. These objects represent the Data Service Objects in ZCM.
Packet Data Router
After installation and local configuration of the PDG is complete, the PDR (software) object is created
and configured in the ZCM application to support data communication services. The following list
summarizes configuration parameters established in ZCM for the PDR.
Unique PDR ID: A number used to uniquely identify each PDR in the system.
Security Group: A name representing a particular set of access rights and
privileges for the PDR object in the ZCM application.
6881009Y05-O April 2004 10-17

Radio Network Gateway Chapter 10: Integrated Voice and Data
NTP Active: Indicates if a packet data router uses the Network Time Protocol
(NTP). Motorola recommends setting this field to Yes to ensure date and time
information is consistent throughout the system.
NTP Service Address: (Primary and Backup) The IP address of the primary
or backup NTP server. This IP address is set automatically by the ZCM, but
you can modify the setting if necessary.
After installation and local configuration of the RNG is complete, the RNG (software) object
is created and configured in the ZCM application to support data communication services. The
following are important ZCM configuration characteristics of the RNG:
The RNG object in ZCM is automatically created when the PDR object is created.
Home zone mapping updates should not be executing when creating the PDR object in ZCM.
The RNG object is automatically deleted in ZCM when the associated PDR object is deleted.
GGSN Router Configuration Overview
The GGSN provides a logical interface to the PDR module in the PDG. Local configuration
of the GGSN is established during hardware install and configuration. See Volume 9, Master
Site Hardware Installation and Configuration for more details.
After installation of the GGSN is complete, data system service configuration of the GGSN is conducted
to establish the following parameters in the Data System window of the UCM application:
GGSN ID: A numeric ID for the GGSN router (GGSN List tab).
GGSN IP Address: A unique IP address for the router (GGSN List tab).
APN Network ID: A description of the external network a radio user
connects to for data service.
GTP T3: The time interval between retries when PDR sends a signaling
request to the GGSN (Advanced Settings tab).
GTP N3: The maximum number of attempts when PDR sends a signaling
request to the GGSN (Advanced Settings tab).
Each virtual interface to the data enterprise network is assigned an Access Point Node (APN) ID.
10-18 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Simulcast Site Steering
Simulcast Site Steering

Simulcast site steering describes a functional feature of the ASTRO 25 communication system to
steer a data transmission to a specific site. Even though all messages are physically broadcast to all
the stations connected to a given comparator in all the remote sites of the subsystem, the effect of
site steering is achieved, because only the specific base station addressed in the Terminal Endpoint
Indicator (TEI) of the ASTRO Infrastructure Signaling (AIS) frame of the transmission recognizes
the transmission. All of the other Simulcast base stations ignore the message.
Site steering transmits payload data packets only at the most recently recorded transmit subsite.
When an inbound transmission from a subscriber is received from simulcast receive-only remote sites, the
comparator not only establishes a best quality signal, but determines which transmit site to use for the
outbound transmission by using configuration information entered into the Map to Transmit Subsite field in
the ZCM. This field is used to associate the best transmission site for each simulcast receive-only remote site.
Transmissions are still time launched (as when simulcasting packets) to allow the comparator to
retain control and keep a common pacing engine in the comparator.
Base stations in a single transmitter receiver voting subsystem do not use the
time launching information sent by the comparator, since this is unnecessary in a
subsystem configuration with a single transmitter.
The comparator must know the best subsite for each subscriber on the packet data channel.
The information is gathered from two areas:
Inbound messages from the subscriber unit radio on the control channel
Inbound data responses on the packet data channel
Use the CSS to provision the TEI address into the base station/receiver. When the link between the
base station/receiver and comparator is established, the comparator records the base stations TEI
address. For simulcast subsystems with simulcast receiver-only subsites and for single transmitter
receiver voting subsystem configurations, the comparator is configured with information about which
subsites are transmit remote sites and which subsites are receiver-only remote sites.
6881009Y05-O April 2004 10-19

Simulcast Site Steering Chapter 10: Integrated Voice and Data
10-20 6881009Y05-O April 2004

Chapter
11
Other Band Trunking

Support for Other Band Trunking (OBT) increases the capability of an ASTRO 25 system. You can add
ASTRO 25 Repeater sites in the 700 MHz, VHF and UHF bands to an ASTRO 25 system to increase RF
coverage in areas where 800 MHz frequencies are no longer available or cause considerable interference
problems. ASTRO 25 also supports standalone VHF and UHF trunking systems.
The following sections describe how OBT is implemented in ASTRO 25 systems. The first section provides a
historical perspective to the development of the ASTRO 25 radio-to-infrastructure signaling interface.
800 MHz Frequency Band Plans

The 800 MHz band has a highly structured and controlled band plan. Table 11-1 shows the analog
band structure from the infrastructure perspective (that is, repeaters, base radios).
Table 11-1 Analog 800 MHz Band Structure for Fixed Equipment
Parameter Description
Receive Frequency Range 806 - 821 MHz for general use
821 - 825 MHz reserved for public safety organizations
Transmit Frequency Range 851 - 870 MHz
T/R Offset 45 MHz
Base Transmit Frequency 851.0125 MHz
Base Receive Frequency 806.0125 MHz
Channel Separation 25 kHz in the 806 - 821 MHz range.
25 kHz or 12.5 kHz in the 821 - 825 range.
Bandwidth 19 MHz from 806 - 825 MHz
Each of the repeaters has a consistent separation between transmit and receive and the repeater
receive frequency is always selected from the 806-825 MHz range. Assignment of frequencies is
carefully coordinated and limited to appropriate agencies and functions. Frequencies are assigned
in contiguous blocks, not as individual entities. This is in direct contrast to the variation in
frequency assignments typical of the VHF and UHF frequency bands.
6881009Y05-O April 2004 11-1

800 MHz Frequency Band Plans Chapter 11: Other Band Trunking
Motorola first deployed trunking in the 800 MHz band. Its coordinated and structured frequency plan
enabled the development of a simplified channel assignment scheme whereby a number representing the
actual frequencys place in the 800 MHz frequency band plan is sent to the radio.
To send the actual voice channel assignment value in MHz over the control channel requires a significant
amount of time and space in the control channel data stream. The assignment of channel numbers, from 0 to
759 in the 800 MHz analog band, addresses both the time and space concerns. The total number of channel
numbers was derived by dividing the bandwidth, 19 MHz, by the channel spacing, 25 kHz.
To support the representation of frequencies by channel numbers, the subscriber radios are programmed
with an algorithm that allows them to convert the channel number to the actual subscriber radio transmit
frequency. The algorithm is represented in this description by the following formula:
Subscriber Receive Frequency = (N * 25 kHz) + 851.0125
N is the channel number sent through the control channel.
851.0125 is the base frequency for the band.
The subscriber radio then simply adds the standard offset (-45 MHz ) to derive its receive frequency.
The formula programmed in the radios and the use of channel numbers is the reason Motorola radios
do not need to be reprogrammed when you add new channels to the 800 MHz system. The FNE only
needs to know which channel numbers have been added. Once the new channels are operational, the
new numbers may be sent over the control channel as voice channel assignments.
The introduction of digital systems in the 800 MHz band brought the following changes to the band plan:
Channel spacing went from 25 kHz to 12.5 kHz.
The number of available channels doubled.
The channel numbering system, under APCO 25 rules, accommodates up to 4096 channel
numbers, leaving room for future channel spacing changes.
Table 11-2 shows the 800 MHz band structure for ASTRO 25 systems.
Table 11-2 ASTRO 25, 800 MHz Band Structure for Fixed Equipment
Receive Frequency Range 806 - 821 MHz for general use
821 - 825 MHz reserved for public safety organizations
Transmit Frequency Range 851 - 870 MHz
Transmit to Receive Offset 45 MHz
Channel Separation 12.5 kHz
Bandwidth 19 MHz from 806 - 825 MHz
11-2 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System OBT Frequency Band Plans
OBT Frequency Band Plans

The 700 MHz band has a structured and controlled band plan. Table 11-3 shows the band
structure from the infrastructure perspective (repeaters, base radios).
Table 11-3 ASTRO 25, 700 MHz Band Structure for Fixed Equipment
Receive Frequency Range 794797 MHz for general use
803806 MHz reserved for public safety organizations
Transmit Frequency Ranges 764767 MHz
773776 MHz
T/ R Offset 30 MHz
Base Transmit Frequency 764.00625 MHz
Channel Separation 12.5 kHz
Each of the 700 MHz repeaters has a consistent separation between transmit and receive. Frequencies
in the above ranges are assigned in contiguous blocks, not as individual entities.
VHF and UHF frequency bands do not have the same kind of structure as the 800 MHz band. Historically,
assignment of VHF and UHF frequencies took place at a time when trunking in two-way radio systems did
not exist; random assignment of frequencies had no impact on conventional system operation.
Now that ASTRO 25 makes it possible to integrate OBT with 800 MHz systems, the unpredictably
of VHF frequency assignments leads to a lack of consistency in separation between transmit and
receive frequencies in a repeater pair and to an unpredictable relationship between the pairs. The
transmit frequency of a repeater pair may be higher or lower than the receive frequency and
the relationship may be reversed in the adjacent frequencies.
The UHF band is somewhat more structured than the VHF band but the structure is not consistent.
Different frequency separations are used in different parts of the band. As in the VHF band, the frequencies
are used for many different types of applications ranging from dispatch to telemetry.
In OBT, some of the infrastructure equipment and all of the subscriber radios must be
configured with channel definition information. The information serves as the key to translating
frequency information to and from channel numbers.
The band plan information must be consistent throughout the system. Consequences when all
devices are not using the exact same channel definitions may include:
Improper frequency information is calculated by the radios.
The radios respond to channel assignments by moving to the wrong channels.
The radios cannot lock on to a control channel.
Adding new frequencies to an OBT system require careful planning, especially if the new frequency does
not fall within the currently configured channel definitions on the system. In those cases, all subscribers
radios and FNE would need to be programmed with new or additional channel element definitions.
6881009Y05-O April 2004 11-3

Developing the OBT Band Plan Chapter 11: Other Band Trunking
Developing the OBT Band Plan

The latest release of ASTRO 25 systems are capable of addressing the following
configurations through an appropriate OBT band plan:
Systems where a structured plan can be built from the available frequencies.
Systems where a structured band plan cannot be built from the available frequencies.
Systems where some of the frequencies can be organized into a structured band plan,
but other frequencies cannot be included in the structured plan.
Structured Band Plans
The current release of ASTRO 25 systems use the APCO 16 ID channel identifier method to define a
structured band plan. The frequency band plan is made up of 1 to 16 elements (numbered 0 thru
15), each defining a group of 4096 possible channels related by the transmit to receive frequency
differential. Each element contains the following information:
An identifier number (element) that is between 1 and 16
The element number points to a set of channels that have the same offset
between their transmit and receive frequencies.
A base frequency
Base frequency is the lowest site transmit frequency defined by the table.
Channel spacing
Channel spacing is the separation between adjacent channels and can be set in 125 Hz
increments under this band plan. The default value used in Motorola equipment is 6.25 kHz.
T/R offset
Transmit offset is the value added to the site transmit frequency to determine the
corresponding receive frequency for any channel.
T/R offset sign

This can be negative if the subscribers Tx frequency is above its Rx frequency or a
positive number if the Tx frequency is below the Rx frequency.
Channel bandwidth
Channel bandwidth is 12.5 kHz in ASTRO 25 systems.
For organized frequency bands, such as the 800 MHz and 700 MHz bands, where the T/R offset is a fixed
value, a single element can implicitly define every possible channel that can be assigned. In a system with a
band plan that includes frequencies from the 800 MHz and 700 MHz bands, 800 MHz band with its fixed
offset of 45 MHz can be assigned to element one. The 700 MHz band with its fixed offset of 30 MHz can
be assigned to element 2. Since each element defines all frequencies within the specified band, any future
expansion of 800 MHz or 700 MHz sites will not require any adjustments to the band plan.
11-4 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Structured Band Plans
The process and tables that follow describe a sample system with frequencies in the VHF
band. Table 11-4 lists the frequencies used in the example. Process 11-1 is an example of the
methodology that can be followed when creating a structured band plan for the VHF band. The
process can also be applied to a system with UHF frequencies.
Table 11-4 Available Frequencies Example
Repeater Rx Repeater Tx
136,375,000 138,900,000
141,450,000 144,950,000
141,725,000 145,125,000
139,875,000 143,250,000
141,375,000 138,925,000
139,850,000 143,000,000
138,875,000 142,000,000
144,250,000 141,000,000
137,750,000 141,500,000
143,250,000 140,500,000
139,750,000 142,875,000
139,625,000 142,500,000
140,975,000 143,500,000
141,300,000 139,050,000
141,250,000 138,875,000
142,500,000 140,000,000
142,250,000 139,000,000
140,550,000 143,750,000
Process 11-1 Creating a Structured Band Plan VHF/UHF
1 List all the frequencies available for use in the system. Arrange in ascending order, in two columns, TX and RX.
2 Determine the T/R offset and sign (positive or negative) for each frequency pair.
3 Determine the channel spacing that can be divided into each member without leaving a remainder (2.5 kHz,
5.0 kHz or 6.25 kHz).
4 Verify that the T/R Offset is also divisible (no remainders) by the channel spacing chosen.
5 Separate all frequencies into groups that have the same T/R offset and sign.
6 Verify that the difference between the maximum and minimum receive frequency in each group divided by the
channel spacing is an integer less than 4095. If the difference is 4095 or greater, the group must be further
subdivided to fit within the range.
7 Verify that the difference between the maximum and minimum transmit frequency in each group divided by the
channel spacing is an integer less than 4095. If the difference is 4095 or greater, the group must be further
8 Select a base frequency for each group.
6881009Y05-O April 2004 11-5

Structured Band Plans Chapter 11: Other Band Trunking
Process 11-1 Creating a Structured Band Plan VHF/UHF (Continued)

9 Determine the channel number for each receive and transmit frequency in the plan. The channel number must
be 4094 or less. Channel number 4095 is reserved for system use and cannot be assigned to any frequency
in the plan.
10 Count the number of groups created in step 1 through step 5. The total number must be 16 or less.
11 Assign each group a unique band plan number from 1 through 16.
12 Enter the band plan elements into the UCM.
13 Enter the band plan elements into the CPS to program the subscribers.
The steps in Process 11-1 produce the results shown in Table 11-5. The information in Table 11-5 can
be used to implement a frequency band plan such as the one shown in Table 11-6.
Table 11-5 Band Plan Element Identification
Element Base Channel Channel

Repeater Rx Repeater Tx T/R Offset
Number Frequency Spacing Number
1 137,750,000 141,500,000 3,750,000 136,000,000 6.25 kHz 880
2 141,450,000 144,950,000 3,500,000 136,000,000 6.25 kHz 1432
3 141,725,000 145,125,000 3,400,000 136,000,000 6.25 kHz 1460
4 139,875,000 143,250,000 3,375,000 136,000,000 6.25 kHz 1160
5 140,550,000 143,750,000 3,200,000 136,000,000 6.25 kHz 1240
6 139,850,000 143,300,000 3,150,000 136,000,000 6.25 kHz 1120
7 138,875,000 142,000,000 3,125,000 136,000,000 6.25 kHz 960
7 139,750,000 142,875,000 3,125,000 136,000,000 6.25 kHz 1100
8 139,625,000 142,500,000 2,875,000 136,000,000 6.25 kHz 1040
9 136,375,000 138,900,000 2,525,000 136,000,000 6.25 kHz 464
9 140,975,000 143,500,000 2,525,000 136,000,000 6.25 kHz 1200
10 141,300,000 139,050,000 2,250,000 136,000,000 6.25 kHz 488
11 141,250,000 138,875,000 2,375,000 136,000,000 6.25 kHz 460
12 141,375,000 138,925,000 2,450,000 136,000,000 6.25 kHz 468
13 142,500,000 140,000,000 2,500,000 136,000,000 6.25 kHz 640
14 143,250,000 140,500,000 2,750,000 136,000,000 6.25 kHz 720
15 142,250,000 139,000,000 3,250.000 136,000,000 6.25 kHz 480
15 144,250,000 141,000,000 3,250.000 136,000,000 6.25 kHz 800
16 139,750,000 136,250,000 3,500,000 136,000,000 6.25 kHz 40
The T/R offset sign establishes the relationship between the transmit and receive frequencies of the stations.
Table 11-5 shows that elements 1 - 9 have a negative offset while elements 10 - 16 have a positive offset. The
negative offset helps the subscriber determine that the receive frequency of the station is below its transmit
frequency. A positive offset indicates that the receive frequency of the station is above its transmit frequency.
11-6 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Structured Band Plans
Tools such as Table 11-5 can be used to develop the frequency band plan for a system. The receive
and transmit frequencies for the repeaters are listed, the difference (offset) between each pair is
determined, a base frequency is selected, and an element number is assigned based on similar offsets.
The channel number column is included to verify that none of the frequencies in the plan exceed the
4094 limit for channel numbers (channel number 4095 is reserved for system use).
Table 11-6 provides an example of the band plan as programmed in the system and in the subscribers.
Table 11-6 Sample Band Plan as Programmed in Site Controllers and Radios
Element Base Channel Subscriber T/R Channel

T/R Offset Sign
Number Frequency Spacing Offset Bandwidth
1 136,000,000 6.25 kHz 3,750,000 Negative 12.5 kHz
2 136,000,000 6.25 kHz 3,500,000 Negative 12.5 kHz
3 136,000,000 6.25 kHz 3,400,000 Negative 12.5 kHz
4 136,000,000 6.25 kHz 3,375,000 Negative 12.5 kHz
5 136,000,000 6.25 kHz 3,200,000 Negative 12.5 kHz
6 136,000,000 6.25 kHz 3,150,000 Negative 12.5 kHz
7 136,000,000 6.25 kHz 3,125,000 Negative 12.5 kHz
8 136,000,000 6.25 kHz 2,875,000 Negative 12.5 kHz
9 136,000,000 6.25 kHz 2,525,000 Negative 12.5 kHz
10 136,000,000 6.25 kHz 2,250,000 Positive 12.5 kHz
11 136,000,000 6.25 kHz 2,375,000 Positive 12.5 kHz
12 136,000,000 6.25 kHz 2,450,000 Positive 12.5 kHz
13 136,000,000 6.25 kHz 2,500,000 Positive 12.5 kHz
14 136,000,000 6.25 kHz 2,750,000 Positive 12.5 kHz
15 136,000,000 6.25 kHz 3,250,000 Positive 12.5 kHz
16 136,000,000 6.25 kHz 3,500,000 Positive 12.5 kHz
The OSP that is transmitted to a radio in response to a voice channel request contains an element
number and a channel number. The element number helps the radio to identify the base frequency,
channel spacing, T/R offset, T/R offset sign, and the channel bandwidth. Together with the channel
number, the radio can then determine the frequencies of the assigned repeater.
The subscriber radios are programmed with the information in Table 11-6 using Customer Programming
Software (CPS). Algorithms that allows them to convert the channel number to the actual receive
and transmit frequencies are programmed at the factory as part of the radios firmware. The
algorithms are represented in this description by the following formulas:
Subscriber Rx = (Base Frequency) + (N * Channel Spacing)
Subscriber Tx = (Base Frequency) + (N * Channel Spacing) + (T/R Offset sign)(T/R Offset)
Where N = the assigned channel number sent over the control channel.
6881009Y05-O April 2004 11-7

Unstructured Band Plans Chapter 11: Other Band Trunking
For organized and narrow frequency bands, such as the 800 MHz and 700 MHz bands, where
the T/R offset is a fixed value, a single element can define every possible channel that can be
assigned. If the band is not organized, like VHF, or covers a wide frequency band, like UHF, it
may require all 16 elements to define all the channels that can be assigned.
Unstructured Band Plans
OBT planning and operation require that each transmit and receive frequency be described by one of the
elements being used in the system. Each element can used frequencies in one of two ways to define frequencies:
When the Rx-Tx differential of a station pair is equal to the T/R Offset in an existing
element, knowing one of the frequencies implicitly defines the other. For a repeater with a
channel number of N, the corresponding transmit and receive frequencies are:
Repeater Tx = (Base Frequency) + N* (Channel Spacing)
Repeater Rx = (Base Frequency) + N* (Channel Spacing) + (T/R Offset sign)(T/R Offset)
For an implicitly defined channel, the site must send only the channel number and one
element number to the subscriber to define the assigned voice channel.
When the Rx-Tx differential of a station pair is not equal to the T/R Offset in any
element, the implicit method can no longer be used to define frequencies. The transmit
and receive frequencies must be explicitly defined. In this case, each frequency is
defined separately, using different elements, if necessary. For a repeater with a channel
number of T for the transmit frequency and a channel number of R for the receive
frequency, the corresponding transmit and receive frequencies are:
Repeater Tx = (Base Frequency) + T*(Channel Spacing)
Repeater Rx = (Base Frequency) + R*(Channel Spacing)
For an explicitly defined channel, the site must send the element number and the channel
number for the receive and transmit frequency, to define the assigned voice channel to the
subscriber. The element number in this case defines the base frequency, and the channel spacing.
The explicit method of defining frequencies is not available in previous ASTRO 25 releases.
11-8 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Creating the Band Plan
Creating the Band Plan

Procedure 11-1 illustrates an example of the methodology to follow when creating a
band plan out of unstructured frequency pairs.
Procedure 11-1 How to Create an Unstructured Band Plan
1 Determine the T/R offset for each frequency pair.
This information is necessary for step 3.

2 Arrange the frequency pairs in ascending order.
3 Starting with the lowest frequency in each group, look for a channel spacing
that can be divided into each member without leaving a remainder (2.5 kHz,
5.0 kHz, or 6.25 kHz).
The T/R Offset also has to be divisible (no remainders) by the

selected channel spacing.
4 Subdivide the frequency pairs into groups that have a common channel spacing.
5 Verify that the difference between the maximum receive frequency in each group
divided by the channel spacing is an integer less than 4095.
If the difference is 4095 or greater, the group must be further

6 Verify that the difference between the maximum and minimum transmit frequency
in each group divided by the channel spacing is an integer less than 4095.
7 Determine the channel number for each receive and transmit frequency in the
plan.
The channel number must be 4094 or less. Channel number 4095

is reserved for system use and cannot be assigned to any frequency
in the plan.
8 Select a base frequency for each group.
9 Assign an element number to each group.
6881009Y05-O April 2004 11-9

Mixed Band Plans Chapter 11: Other Band Trunking
Selection of a base frequency for each group must take into consideration the operating
frequency band of the subscribers and plans for future expansion of the system.
Mixed Band Plans
It is possible for a system to include sites or zones in different frequency bands. A band plan for such
a system may be required to define structured and unstructured elements. Transmission of control
channel information, such as channel grants and adjacent control channel lists, requires that the system
be programmed to transmit the structured band plan elements using the Implicit format, and to transmit
the elements representing the unstructured part of the band plan using the Explicit format.
Subscribers operating in the system can then receive channel information that allows them to
operate with the system resources that are within their frequency range.
Creating the Band Plan

This example demonstrates band plan development for a system with a structured
and unstructured frequency pairs.
The initial frequency/channel configuration that the system planners receive for an actual system,
may be analyzed in a manner similar to that shown in the example. By doing the analysis when the
channel becomes known, the planners can anticipate the configuration tasks that will be required, the
intra-system and inter-system interference and site compatibility issues, and may be able to suggest some
rearrangement of frequencies to minimize the effect of unique Tx-Rx frequency pairs.
The sample system includes sites with frequencies in the 800 MHz, 700 MHz, UHF, and
VHF bands. Use Process 11-2 to create the band plan.
Process 11-2 Creating a Mixed Band Plan
1 Separate the Transmit-Receive pairs by frequency band.

2 Separate all UHF frequencies into groups that have the same T/R offset and sign.
3 For UHF frequencies that do not have a common offset, separate into groups with
a common channel spacing.
4 Separate all VHF frequencies into groups that have the same T/R offset and sign.
5 For VHF frequencies that do not have a common offset, separate into groups with
a common channel spacing.
6 Count the number of groups created in step 1 through step 5. The total number
must be 16 or less.
7 Assign each group a unique band plan number from 1 through 16.
8 Enter the band plan elements into the UCM.
9 Enter the band plan elements into the CPS to program the subscribers.
11-10 6881009Y05-O April 2004

Step one in the process consists of organizing the frequencies by band. For organized frequency bands,
such as the 800 MHz and 700 MHz bands, where the transmit to receive offset is a fixed value, a single
element can implicitly define every possible channel that can be assigned. In the sample band plan, the
800 MHz band with its fixed offset of 45 MHz must be assigned to element one. The 700 MHz band
with its fixed offset of 30 MHz must be assigned to element 2. Since each element defines all frequencies
within the specified band, any future expansion of 800 MHz or 700 MHz sites will not require any
adjustments to the band plan. Elements one and two can be assigned to other bands if there are no
plans to include or expand the system with 800 MHz and/or 700 MHz frequencies.
The UHF and VHF frequencies used in the sample system are listed in Table 11-7.
Table 11-7 System Frequencies UHF and VHF Bands
Station Rx Station Tx Station Rx Station Tx

500.0875 503.0875 151.2725 158.9775
500.4750 503.4750 151.2875 153.9275
500.4875 503.4875 151.2875 156.0525
500.5125 503.5250 151.2875 159.0150
500.5250 503.5120 151.2950 153.8900
500.5500 503.5500 151.2950 159.3000
500.6250 503.6250 151.2950 159.3675
500.6625 503.6625 151.3100 158.8500
500.6875 503.6875 151.3250 155.4600
500.7125 503.7125 151.3250 158.8800
151.3025 153.9425 151.3325 153.8225
151.2725 154.9350
Multiple groups may be required to define all the channels that could be assigned in VHF and UHF.
Table 11-8 and Table 11-9 lists the frequencies by band and offset.
Step two in the process consists of computing the offset to determine commonality. Table 11-8
lists the UHF frequencies and Table 11-9 lists the VHF frequencies.
Table 11-8 UHF Frequencies Grouped by Offset
Frequency Pair # Station Rx in MHz Station Tx in MHz T/R Offset in MHz

1 500.0875 503.0875 3.000
2 500.4750 503.4750 3.000
3 500.4875 503.4875 3.000
4 500.5125 503.5120 3.000
5 500.5250 503.5250 3.000
6 500.5500 503.5500 3.000
7 500.6250 503.6250 3.000
8 500.6625 503.6625 3.000
6881009Y05-O April 2004 11-11

Creating the Band Plan Chapter 11: Other Band Trunking
Table 11-8 UHF Frequencies Grouped by Offset (Continued)

9 500.6875 503.6875 3.000
10 500.7125 503.7125 3.000
For the UHF band, all of the frequency pairs have a common T/R Offset and are close to each other. Each
station frequency and the T/R Offset is divisible by 6.25 kHz and 12.5 kHz. A single element can be
constructed to cover all of these frequencies. With 6.25 kHz channel spacing assigned to the UHF frequencies
in Table 11-8, one element can cover channels that span a 25.5 MHz range (6.25 kHz * 4094 channels).
Selection of a base frequency needs to account for three factors:
Future expansion plans.

The operating range of the subscribers, specifically, the operating band of mobile radios.
Relationship of the receive and transmit frequencies. It is possible for transmit
frequencies to be above or below the receive frequency.
For this example, the assumption is that the need for future expansion is limited and the
assigned frequencies will be close to the current frequencies. A base frequency of 490 MHz
implicitly covers all pairs with a 3 MHz T/R Offset.
Repeating step two for the VHF frequencies generates the results in Table 11-9. The
frequencies are arranged in ascending order by offset.
Table 11-9 VHF Frequencies Grouped by Offset

1 151.3325 153.8225 2.4900
2 151.2950 153.8900 2.5950
3 151.2875 153.9275 2.6400
4 151.3025 153.9425 2.6400
5 151.2825 1534.9350 3.6525
6 151.3250 155.4600 4.1350
7 151.2875 156.0525 4.7650
8 151.2725 158.9775 7.7050
9 151.2875 159.0150 7.7275
10 151.3100 158.8500 7.5400
11 151.3250 158.8800 7.5550
12 151.2950 159.3000 8.0050
13 151.2950 159.3675 8.0725
Analysis of Table 11-9 yields the following factors to consider in mapping the VHF
frequencies to elements on the band plan:
Unlike the UHF frequencies, the VHF frequencies yield only 2 pairings that
share a common T/R Offset, pairs 3 and 4.
11-12 6881009Y05-O April 2004

The channel spacing that can be divided into all frequency pairs and their
offset without generating a remainder is 2.5 kHz.
The difference between the highest and lowest receive frequency is 60 kHz.
The difference between the highest and lowest transmit frequency is 5.545 kHz.
The table also shows the following:
Pairs 3, 7, and 9 share the same frequency, 151.2875 MHz.

Pairs 2, 12, and 13 share the same receive frequency, 151.2950 MHz.
Pairs 6 and 11 share the same receive frequency, 151.3250 MHz.
The last three items become an important factor when planning frequency distribution at the sites. System
operation can be greatly affected when using such frequency pairs at adjacent sites. Subscriber radios
transmitting into multiple receivers with the same frequency can cause intra- and inter-system interference.
It is necessary at this point to calculate the channel capacity for the range of frequencies in
Table 11-9 and to also calculate the channel numbers to determine if the limit of 4095 channels
per element or any channel number higher than 4094 is exceeded.
To calculate the channel capacity, subtract the lowest frequency from the highest
frequency and divide by the channel spacing.
For the receive frequencies:
(151.3325 151.2725)/.0025=24 channel numbers needed to cover the range
For the transmit frequencies:
(159.3675 153.8225)/.0025=2218 channel numbers needed to cover the range.
The results of the calculations indicate that the receive and transmit frequencies are well within the 4094 limit.
To calculate the channel numbers, select a base frequency or frequencies for the VHF groups.
Selection of a base frequency needs to account for four factors:
Future expansion plans

The operating range of the subscribers, specifically, the operating band of mobile radios
Relationship of the receive and transmit frequencies. It is possible for transmit
frequencies to be above or below the receive frequency.
The channel spacing
Channel spacing becomes a factor with VHF frequencies because of the number of elements that
may be required to fully cover the current frequencies and support for future expansion. One
element, with its 4095 assignable channels, covers a 10.235 MHz range at 2.5 kHz spacing. See
Table 11-10 for the effect this has on the VHF band (136 to 174 MHz).
Table 11-10 Elements Needed to Cover the VHF Band
Start Frequency in MHz Element Range in MHz End Frequency in MHz

136.0000 10.2350 146.2350
146.2375 10.2350 156.4725
6881009Y05-O April 2004 11-13

Creating the Band Plan Chapter 11: Other Band Trunking
Table 11-10 Elements Needed to Cover the VHF Band (Continued)

Start Frequency in MHz Element Range in MHz End Frequency in MHz
156.4750 10.2350 166.7100
166.7125 10.2350 176.9475
The structure shown in Table 11-10 provides the framework necessary to choose the base frequencies for the
frequency information used in this example. Table 11-10 adds two more factors to the analysis of Table 11-9:
Only one element is necessary to cover the receive frequencies 9151.2725

MHz 151.3325 MHz)
Two elements are necessary to cover the transmit frequencies (153.8225
156.0525 and 158.8500 159.3675). The base frequency becomes the determining
factor in the number of required elements.
For this example, the base frequency selected for the receive channels is 146.2375 MHz. Two base
frequencies are selected for the transmit channels, 146.2375 MHz and 156.4725 MHz.
Analysis of the range between the lowest receive frequency and the highest transmit
frequency (8.0950 MHz) shows that all frequencies can be covered with one element by
choosing a different base frequency. This can, however, affect future system expansion by
limiting the choice of frequencies, increasing the number of elements required to rebuild
the band plan, and possibly having to reprogram system equipment.
To calculate the receive channel numbers, subtract the base frequency from the receive frequency and
divide the result by the channel spacing. To calculate the Transmit channel numbers subtract the base
frequency from the transmit frequency and divide the result by the channel spacing. The calculations
for the frequencies shown in Table 11-9 yield the results in Table 11-11.
Table 11-11 VHF Frequencies with Channel Numbers
Rx Base Tx Base Channel

Channel Channel
Frequency Frequency Frequency Frequency Spacing in
Number Number
in MHz in MHz in MHz in MHz kHz
151.2725 146.2375 2014 158.9775 156.4750 1001 2.5
151.2825 146.2375 2018 154.9350 146.2375 3479 2.5
151.2875 146.2375 2020 153.9275 146.2375 3076 2.5
151.2875 146.2375 2020 156.0525 146.2375 3926 2.5
151.2875 146.2375 2020 159.0150 156.4750 1016 2.5
151.2950 146.2375 2023 153.8900 146.2375 3061 2.5
151.2950 146.2375 2023 159.3000 156.4750 1130 2.5
151.2950 146.2375 2026 159.3675 156.4750 1157 2.5
151.3025 146.2375 2026 153.9425 146.2375 3082 2.5
151.3100 146.2375 2029 158.8500 156.4750 950 2.5
11-14 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Infrastructure Programming
Table 11-11 VHF Frequencies with Channel Numbers (Continued)

Rx Base Tx Base Channel
Channel Channel
Frequency Frequency Frequency Frequency Spacing in
Number Number
in MHz in MHz in MHz in MHz kHz
151.3250 146.2375 2035 155.4600 146.2375 3689 2.5
151.3250 146.2375 2035 158.8800 156.4750 962 2.5
151.3325 146.2375 2038 153.8225 146.2375 3034 2.5
Table 11-11 shows that all channel numbers are within the 4094 limit. At this point, step 7 of Process 11-2
can be completed by determining the number of elements needed for the complete band plan. See
Table 11-12 for a summary of this activity. The last column is included to indicate the type of signaling
format used by the control channel to transmit channel information to the subscribers.
Table 11-12 Assigning Band Plan Elements
Control
Base Channel
T/R Offset Channel
Element Frequency in Spacing in
in MHz Signaling
MHz kHz
Format
1 851.00625 45 6.25 Implicit
2 764.00625 30 6.25 Implicit
3 490.00000 3 6.25 Implicit
4 146.23750 NA 2.50 Explicit
5 156.47500 NA 2.50 Explicit
The band plan can now be implemented to program the system and subscriber information.
Infrastructure Programming
Infrastructure programming consists of the following:
Programming of frequency band plan information in the UCM.

Programming of sub-band restriction for channels in the ZCM.
Defining of Individual and Talkgroup sub-band ranges in the UCM.
User Configuration Manager Programming

You can enter and store up to 20 frequency band plans in the UCM, but only one frequency band plan is used by
the system at any one time. The information is downloaded to the site controllers when their link to the master
site is first established and at any time changes are made to the current band plan or a new one is put into effect.
Sub-Band Operation
Sub-band operation is used by zone controllers and site controllers to manage the infrastructure resources,
radios, and talkgroups. Properly identified resources make the following types of communication possible:
6881009Y05-O April 2004 11-15

Configuring a Channel as a Sub-band Channel Chapter 11: Other Band Trunking
Sub-band restricted radio to sub-band restricted private radio private calls

Sub-band restricted radio to unrestricted radio private calls
Talkgroup calls when all members of the talkgroup are sub-band restricted
Talkgroup calls when some members of the talkgroup are sub-band restricted
and some have no band restriction
Multigroup calls when all talkgroup members are sub-band restricted
Multigroup calls when some talkgroups are sub-band restricted and some
talkgroups have no band restriction
Supergroup calls
Emergency calls
Emergency alerts
Configuring a Channel as a Sub-band Channel

There is one field in the ZCM application to configure a channel as a sub-band channel. This field is set
at the channel level at each site for any channel that needs to be set up as sub-band restricted. The field
is set to yes on a channel required to operate in the smaller sub-band frequency range.
UCS Tables
There are two UCS tables that control sub-band operation in the system. These are:
Restricted talkgroups ID table
This is a table that allows configuration of up to 32 contiguous, non-overlapping ID
ranges for talkgroups that are restricted to operate only on sub-band channels. This
table is a manager-owned parameter that is sent to all zone controllers, for use in wide
area calls, and to site controllers for use in site trunking.
Restricted radios ID table

This is a table that allows configuration of up to 32 contiguous, non-overlapping ID
ranges for individuals that are restricted to operate only on sub-band channels. This
table is a manager-owned parameter that is sent to all zone controllers, for use in wide
area calls, and to site controllers for use in site trunking.
You must ensure that individual and talkgroup ID start and end ranges
fall within the ranges specified in the home zone mapping object in the
User Configuration Manager. Improper mapping results in subscribers
being unable to access the system.
11-16 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Call Processing in OBT Systems
Call Processing in OBT Systems

Careful planning during the fleetmapping stage of system design enhances accomplishment of call processing
tasks in systems that include OBT sites, OBT zones, or a combinations of OBT sites and zones.
The following sections describe the impact OBT has on various types of calls.
Wide Area Call Processing
Sites operating in different frequency band may be involved in a call in OBT systems. Call processing assigns
a sub-band channel, if one exists at a site, for calls involving sub-band individuals and talkgroups. If a site has
sub-band channels in service but all of those channels are busy, then the call will be busied. If no sub-band
channels are programmed at a site or all sub-band channels are out of service, call processing rejects a call
request initiating at that site or assigns an unrestricted channel if the call is initiated at another site.
If a site only had one sub-band channel, and it is currently operating as the control channel,
call processing allows sub-band subscribers to register. Call processing will issue a reject if a
sub-band subscriber initiates a group or individual call at such a site.
The sections that follow describe in more detail how OBT affects wide area call processing.
Talkgroup Call
Call processing permits inter-operation among sub-band and full band individuals affiliated to
the same talkgroup. Talkgroups are flagged as sub-band based on inclusion in the sub-band
restricted ID table or by member affiliations. Talkgroups that are flagged as having sub-band
members require sub-band channels at all sites where sub-band channel resources exist, otherwise
unrestricted channels are assigned. Sites where sub-band restricted subscribers are registered must
have sub-band channels otherwise the subscribers cannot initiate calls.
Talkgroups may have a mixture of different frequency bands across the system. For example, a
talkgroup may consist of subscribers that operate in 800 MHz sites, subscribers that operate in VHF
low range sites and subscribers that operate in VHF high range sites (band unrestricted channels). The
affiliated members at the VHF low range site cause the controller to flag this talkgroup as a sub-band
restricted talkgroup. Channels for such a talkgroup are assigned as follows:
Unrestricted channels are assigned at the 800 MHz site (there are no sub-band
restrictions in this band in ASTRO 25 systems).
Unrestricted channels are assigned at the VHF high range site that contains
no sub-band (VHF low range) channels.
A sub-band restricted channel is assigned at the VHF low-range site even if talkgroup
members in the VHF high range are also registered at the site.
If the system has VHF sites with low range and high range voice channels, assignments take place as follows:
Sites with both sub-band restricted channels and unrestricted channels assign a sub-band
channel for talkgroups flagged as having sub-band members.
Sites with both sub-band restricted channels and unrestricted channels, but with all
sub-band channels busy, cause the call to be placed in the busy queue.
6881009Y05-O April 2004 11-17

Multigroup Call Chapter 11: Other Band Trunking
Sites with both sub-band restricted channels and unrestricted channels, but all sub-band
channels are out of service, cause the call to be rejected if the call is initiated at this site.
The site assigns an unrestricted channel if the call originates at a different site. If a high
range channel is assigned, low range members present at the site cannot participate in
the call as they have no way of generating the appropriate frequency.
Sites that have only one sub-band channel, that is currently operating as the control channel, create
some unique operating conditions. Table 11-13 lists some possible scenarios that can occur when
a talkgroup is flagged as sub-band restricted and has at least one member at such a site. These
conditions can occur in any band that uses sub-band restrictions.
Table 11-13 Site with Single Sub-band Channel Operating as Control Channel
Subscriber At Sub-band Requesting

Results
This Site Restricted Flag Subscriber
Yes Yes Yes Call processing issues a reject since the requesting
subscriber is not able to use an unrestricted channel.
Yes No Yes Call processing assigns an unrestricted channel if
available. The subscriber receives a busy signal if
there are no unrestricted channels available.
Yes Yes No The site is not included in the call if this is the only
subscriber at the site affiliated to the requesting
talkgroup. If there are other members of the
talkgroup at the site, and they are not sub-band
restricted, call processing assigns an unrestricted
channel if available. The requesting subscriber
receives a busy signal if there are no unrestricted
channels available.
Yes No No Call processing assigns an unrestricted channel if
available. The requesting subscriber receives a
busy signal if there are no unrestricted channels
available.
Multigroup Call
The zone controller ensures that sub-band channel resources are assigned to multigroups containing
both sub-band and unrestricted band users. Any multigroup flagged as having sub-band members
will be processed the same way as a talkgroup having sub-band members.
A multigroup with an ID that is not part of the sub-band restricted range cannot include any radios or
talkgroups that are sub-band restricted. A multigroup that is sub-band restricted can include full band
members since a full band radio can be assigned to a sub-band restricted channel.
Group Regrouping
Any sub-band restricted talkgroup that becomes part of a supergroup automatically makes the
supergroup sub-band restricted. All sites in the supergroup call that have a sub-band channel
in service assign a sub-band channel, if available, to the call.
11-18 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Patch Calls
Patch Calls
Sub-band restricted talkgroups cannot be added to an active patch call unless the patch already includes
sub-band restricted members. If the active patch does not include sub-band restricted members, the
talkgroup with sub-band members may be added once the patch call ends.
Private Calls
Private calls that include the console are processed as follows:
Private calls to and from a console are supported to subscribers in any band.
For console initiated private calls, the channel assignment is based on whether
the target ID is part of a sub-band restricted range or not.
Private calls when target and initiator are in the same zone are processed as follows:
For private calls between two sub-band subscribers, both subscribers must have sub-band
channel resources available in their respective sites for the call to be assigned.
The controller rejects requests for private calls from sub-band restricted radios if
the sub-band voice channels are not available due to failure.
If either target or initiating subscriber is in a sub-band range, call processing
assigns a sub-band channel at all sites in the call.
If an initiating subscriber is unrestricted and the target is sub-band restricted, call processing
issues a reject if there are no sub-band voice channel resources in service at the target location.
If neither target nor initiating subscriber ID belongs to a sub-band range, call processing
assigns a full band channel if available, otherwise a sub-band channel is assigned to the call.
Private calls when target and initiator are in different zones are processed as follows:
If either target or initiating subscriber is in a sub-band range in the UCS, call processing
assigns a sub-band channel at the site in the zone containing the sub-band subscriber.
If all sub-band channels at the sub-band users site are being used by other
calls, the call receives a busy.
A sub-band subscriber locked onto a sub-band control channel whose site
has no sub-band voice resources in service causes a call to receive a reject
when attempting to call the sub-band user.
If an initiating subscriber is in a sub-band range in the UCS and the sub-band voice channels
are not in service at its site due to failures, the sub-band subscriber receives a reject.
If an initiating subscriber is not sub-band, but the target is sub-band, and a sub-band voice
channel resource is not in service at the target subscribers zone, call processing rejects the call.
Call processing assigns an unrestricted channel if available, otherwise a sub-band
channel is assigned, if neither the targets ID nor the initiating subscribers ID
is part of the sub-band ranges in the UCS.
Emergency Alarm and Emergency Call

Emergency calls are processed as follows:
If a site has only one sub-band channel and it is currently operating as the control
channel, the controller allows the subscriber to affiliate but rejects any requests for
an emergency call due to the lack of voice channels.
6881009Y05-O April 2004 11-19

Dynamic Regrouping Chapter 11: Other Band Trunking
Emergency alarms are processed through the control channel and do not require a voice
channel. If a sub-band subscriber initiates an emergency alarm, the alarm processes normally.
Dynamic Regrouping
Call processing rejects a request to dynamically regroup a sub-band subscriber to a talkgroup that is not
flagged as having sub-band members. However, a request to dynamically regroup an unrestricted subscriber
to a talkgroup flagged as having sub-band members is processed based on the availability of resources.
Interconnect Calls
There are only two types of interconnect calls supported in ASTRO 25 systems:
Subscriber-to-landline
Landline-to-subscriber
Processing of both types of calls is based on the individual radios ID.
Sub-band users performing subscriber-to-landline calls require a sub-band control channel and a
sub-band voice channel. If there is only one sub-band voice channel at the sub-band users site and
it is assigned to another call, a sub-band interconnect call request will receive a busy.
If a sub-band subscriber locks onto a sub-band control channel and that site has no sub-band
voice channels in service, the zone controller records the subscribers registration but issues
a reject to any requests for service from that subscriber.
A sub-band control channel and a sub-band channel are required when a landline initiates a
landline-to-subscriber call involving sub-band users. The landline user receives a busy if all sub-band
channels at the targets site are being used by other calls. A sub-band subscriber locked onto a
sub-band control channel whose site has no sub-band voice resources in service causes a landline
to receive a reject message when attempting to call the sub-band user.
Site Trunking
PSC 9600 site controllers in ASTRO 25 Repeater sites support local programming, through CSS, of
up to 32 individual and talkgroup sub-band range tables. PSC 9600 settings for the 32 ranges are
used only in site trunking. The site controller handles sub-band channel user steering for talkgroups,
private calls, and emergency calls in site trunking independent of frequency band.
The sub-band range tables are manager-owned parameters; the local tables are overwritten
by the UCM values as soon as the site connects to the network manager.
Local configuration of a channel as sub-band is done by the user at the PSC 9600 through CSS. The
channel configuration is set by the user at the channel level at each site for any sub-band channel
that needs to be setup at the site. Only sites intended to support sub-band channel users need to
mark channels as sub-band. Default for the channel sub-band field is Yes.
11-20 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Failsoft
The sub-band range tables and channels parameters are zone manager owned and under control of
the ZC in wide area mode. The local settings, programmed through CSS, are overwritten by the
ZCM values for these fields as soon as the site connects to the zone configuration manager.
Failsoft

Sub-band channel users must be programmed for sub-band channels when the site is in the
Failsoft condition. For example, mixed talkgroups with both VHF low- and full-band users
must be programmed for VHF low-range channels.
Private Call Processing
Table 11-14 describes the processing results when the target and initiator are in the same zone.
Table 11-14 Target and Initiator in the Same Zone Different Sites
And the Channel

If the Sub-band Restriction flag is set this way:
Status (either site) is:
Channel Channel Then the call is:
Initiating Target Out of
Initiating Target Busy
Radio Radio Service
Site Site
Yes Yes Yes Yes No No Accepted and sub-band restricted
resources are assigned to the call.
Yes Yes Yes Yes Yes No Placed in busy queue.
Yes Yes Yes Yes No Yes Rejected.
Yes Yes No Yes NA NA Rejected.
Yes Yes Yes No NA NA Rejected.
No Yes Yes Yes No No Assigned with sub-band restricted
channels at both sites.
Yes No Yes Yes No No Assigned with sub-band restricted
channels at both sites.
No Yes Yes No No No Rejected. Both subscribers
must have sub-band channels
available.
6881009Y05-O April 2004 11-21

Different Zone Private Calls Chapter 11: Other Band Trunking
Table 11-14 Target and Initiator in the Same Zone Different Sites (Continued)
And the Channel
Status (either site) is:
Initiating Target Out of
Initiating Target Busy
Radio Radio Service
Site Site
No Yes No Yes NA NA Rejected. Both subscribers
available.
Yes No Yes No NA NA Rejected. Both subscribers
available.
Yes No No Yes NA NA Rejected. Subscribers at
initiating site does not have
sub-band channels available.
No No No No No No Assigned to unrestricted
channels.
No No Yes Yes No No Assigned to unrestricted channels
if available, otherwise it is
assigned to the sub-band
restricted channels.
Different Zone Private Calls
Table 11-15 describes the processing results when the target and initiator are in different zones.
Table 11-15 Target and Initiator in Different Zones
And the Voice Channel

status is:
Initiating Target Initiating
Initiating Target Target Zone
Radio Radio Zone
Site Site
Yes Yes Yes Yes Available Available Accepted and sub-band
restricted resources are
assigned to the call.
Yes Yes Yes Yes Available Busy Placed in busy queue.
Yes Yes Yes Yes Busy Available Placed in busy queue.
Yes Yes No Yes Unrestricted Available Rejected. The initiating
channels radio is sub-band restricted
available and does not have sub-band
resources available.
11-22 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Different Zone Private Calls
Table 11-15 Target and Initiator in Different Zones (Continued)

status is:
Radio Radio Zone
Site Site
Yes Yes Yes No Available Unrestricted Rejected. The target radio
channels is sub-band restricted and
available does not have sub-band
Yes Yes Yes Yes Available Out of service Rejected.
Yes Yes Yes Yes Out of service Available Rejected.
Yes No Yes Yes Available Available accepted and sub-band
Yes No Yes No All resources Unrestricted Accepted. The initiating
available channels radio is assigned sub-band
available restricted resources while
the target radio is assigned
unrestricted resources.
Yes No No Yes Unrestricted Available Rejected. The initiating
channels radio is sub-band restricted
available and does not have sub-band
No Yes Yes Yes Available Available Accepted and sub-band
No Yes No Yes Unrestricted Available Accepted. The initiating
channels radio is assigned
available unrestricted resources
while the target radio
is assigned sub-band
restricted resources.
No Yes No Yes Unrestricted Out of service Rejected.
channels
available
No Yes Yes No Unrestricted Unrestricted Rejected.
channels channels
available available
No No Yes Yes All resources All resources Accepted. Unrestricted
available available resources are assigned.
No No Yes Yes Unrestricted Unrestricted Accepted. Sub-band
channels not channels restricted resources are
available available assigned at the initiating
site.
6881009Y05-O April 2004 11-23

Different Zone Private Calls Chapter 11: Other Band Trunking
Table 11-15 Target and Initiator in Different Zones (Continued)

status is:
Radio Radio Zone
Site Site
No No Yes Yes Unrestricted Unrestricted Accepted. Sub-band
channels channels not restricted resources are
available available assigned at the target site.
No No No No Unrestricted Unrestricted Placed in the busy queue.
channels busy channels
available
No No No No Unrestricted Unrestricted Placed in the busy queue.
channels channels busy
available
11-24 6881009Y05-O April 2004

Chapter
12
Introduction to the FCAPS Model and PRNM

This chapter provides an introduction to the FCAPS model and Private Radio Network Manager (PRNM).
System Objectives And Framework

As a telecommunications network, the ASTRO 25 system needs to be managed as any other

telecommunications network is managed. The Private Radio Network Management (PRNM) subsystem can
be viewed as a set of software applications or tools used to manage the ASTRO 25 system and its components.
These tools are intended to maximize the available resources and minimize system downtime.
Five key functional areas or services are associated with a network management framework:
Fault Management
Configuration Management
Accounting
Security Management
The International Organization for Standardization (ISO) refers to this as the FCAPS model. The PRNM
subsystem offers effective and efficient solutions that address each of the FCAPS requirements.
The PRNM subsystem supports the following services:
Fault Management Applications are included for monitoring the status of the transport
network and the individual infrastructure components, displaying fault information,
forwarding alert information, and performing diagnostic procedures.
Configuration Management Facilities are provided for entering and
maintaining the operational parameters of the infrastructure components and
user devices (such as portables and mobiles).
Accounting Management PRNM supports the tracking of radio usage of the system by
providing an optional interface to third-party accounting and/or billing applications.
Performance Management Standard and optional applications are available for
monitoring, reporting, controlling, and optimizing the use of system resources.
6881009Y05-O April 2004 12-1

Private Radio Network Management System Chapter 12: Introduction to the FCAPS Model and PRNM
Security Management PRNM includes features for setting user privileges and controlling
their access to view and/or modify information contained in the configuration databases.
Systems continue to grow in size and technical complexity. Work demands are increasing on system
administrators who are routinely faced with handling multiple tasks. PRNM configurable paging alert and
remote access features help leverage system administrators time. At the same time, the mobile work force
increasingly relies on radio communication services to fulfill their critical missions. Even a brief service
interruption or degraded quality of service could impact organizational effectiveness, productivity, or safety.
Rapid fault detection, notification, and repair require sophisticated tools that are technologically equal to the
managed network. The Motorola PRNM applications are designed for ease of use (user-friendly GUIs) and
operational efficiency. These and other features and benefits are detailed in the following sections.
Private Radio Network Management System

ASTRO 25 introduces the Motorola new generation Private Radio Network Management (PRNM)
System based on the client/server networking model. PRNM meshes seamlessly and scales with the
other infrastructure elements across the network. The new PRNM represents a significant change for the
system manager/administrator users as well, the network management applications are now deployed on
personal computer (PC) workstations running the Microsoft Windows operating system.
In the equipment room, the application and database servers run unattended on industrial-class computers
based on the CompactPCI standard1. The server applications run over Sun Microsystems Solaris 7 Operating
Environment, a leading UNIX operating system (OS) supported by industry standard network management
applications and vendors of embedded software solutions. Solaris is a mature OS known for its security, an
important characteristic Motorola considered in selecting it to run the PRNM business-critical applications.
The architecture and implementation are not all thats new about the Motorola PRNM subsystem. Motorola
also has enhanced and further integrated the Zone Manager applications and the FullVision Integrated
Network Manager (INM) software platform used in earlier system releases.
Client/Server Networking
Application processing, data collection and storage are distributed across multiple computer servers
and client PC workstations connected to a local area network (LAN). The client PC workstations
are commercial personal computers running the Microsoft Windows operating system for networked
computers. Authorized system managers or network administrator personnel use the client
PC workstations to start and run the software applications for configuring, viewing equipment
operational status, and monitoring network utilization and performance.
The servers are industrial grade, high performance computers geared to handle the intense,
typically real-time, data processing tasks associated with managing a single zone or handling
specific system-level tasks, in multiple zone systems.
1. This standard is driven by the Peripheral Component Interconnect (PCI) Industrial Computer Manufacturers
Group (PICMG) increasingly referenced throughout the telecommunications industry.
12-2 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Windows Based Clients
Windows Based Clients

PRNM Windows based client/server architecture eliminates the User Servers and X-Terminals
associated with the previous architecture. Previously, user applications ran on at least one User
Server; additional User Servers were necessary to accommodate more users and concurrently running
applications. The new PRNM architecture distributes most of the user application processing to
the client PC workstations. This approach yields important benefits:
Application performance is less dependent on the number of concurrent
users and open applications.
Personnel typically responsible for managing a radio system or computer network
are already familiar with, or easily trained to use, the GUI of PRNM applications
that conform to Windows operating system conventions.
Remote operation performance over a limited bandwidth link (for example, a telephone
line used for accessing the network remotely through dial-up modems) is improved.
Client Applications
The following PRNM applications run on or may be accessed from the PC client workstations:
System-Level Applications
User Configuration Manager (UCM) - A management application used to

enter and maintain configuration information for the User Configuration Server
(UCS). The User Configuration Manager (UCM) configures System, Subscribers,
Security, and Zone Watch Configuration objects.
Historical Reports - A management application for multiple zone systems. Radio
traffic statistics from multiple zones, including interzone traffic, are accumulated in the
System Statistics Server and collated to produce system-wide reports.
System Profile - Displays how system-level applications are being used by the network
management clients. It displays the users that are currently accessing system-level
applications, the number of purchased licenses for these applications, and displays
the number of licenses that are currently being used.
System Profile displays information for the following applications:
Historical Reports
System Profile
Software Download for digital simulcast subsystems
Zone-Level Applications
Zone Profile
The Zone Profile application displays detailed information about the servers and
applications that are operating in the zone. The first tab in the Zone Profile application
displays the active processes and installed software on each of the servers in the zone.
The second tab in the Zone Profile application displays how zone-level applications
are being used by the network management clients.
6881009Y05-O April 2004 12-3

Zone-Level Applications Chapter 12: Introduction to the FCAPS Model and PRNM
Zone Configuration Manager (ZCM)

A management application used to enter and maintain configuration information for the Zone
Database Server (ZDS). The ZCM configures the infrastructure equipment for the system.
The ZCM is part of the Motorola Private Radio Network Management Suite.
Zone Watch
A Windows application that monitors trunking activity and radio call traffic for an individual
zone in real time. This application is part of the Private Network Management Suite. (2) A
Motorola software application that allows users to monitor activity within a zone.
Affiliation Display
Affiliation Display is a Private Radio Network Management (PRNM) Suite management
application that monitors how radio users travel between different sites in a zone and
how they communicate with other members of their assigned talkgroup or even with
members outside of their talkgroup within a particular zone.
Air Traffic Information Access (ATIA) Log Viewer

The Air Traffic Router (ATR) collects radio traffic information from the zone controller
and broadcasts the information stream as packets on the network. The data packets
with radio traffic information contain talkgroup and site affiliation and deaffiliation
information for each radio user in a particular zone.
Dynamic Reports
An application intended for short term monitoring. The display provides zone-level,
real-time charts that illustrate channel utilization for all call types group, private,
interconnect, control channel, and dynamically blocked calls.
Historical Reports
A management application producing reports on radio infrastructure and radio
resource usage within an identified zone.
Fault Manager using FullVision Integrated Network Manager (INM)

The ASTRO 25 fault management application. FullVision INM identifies problems rapidly
and provides functions and tools for notifying support personnel, tracking, diagnosing, and
correcting faults. It also maintains a data warehouse, storing up to 30 days of event history.
Radio Control Manager (RCM)

A management application used to issue commands to radios and monitor events from radios.
The Radio Control Manager (RCM) is part of the Motorola PRNM Suite.
Radio Control Manager Reports

The application provides reports of RCMs two types of functions: radio
commands initiated and radio events displayed.
These applications input to or extract information from one or more of the PRNM servers where system
configuration parameters are stored, transactional statistics are accumulated, real-time data streams are
sourced, and supporting processes are performed. In addition to these user applications, the PRNM
servers also run several autonomous processes in the background to support the ongoing operation of the
ASTRO 25 system. Applications and processes are described later in this section.
12-4 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Network Management System Servers
Network Management System Servers

CompactPCI is an industry standard for computer backplane architecture and peripheral integration.
Motorola has integrated the PRNM application and database servers on Motorola Computer Group (MCG)
CompactPCI industrialized chassis. Central Processing Unit (CPU) cards from Sun Microsystems with
their respective hard disk drives, shared CD-ROM, and Digital Audio Tape (DAT) drives are assembled to
provide a high-density, rack mounted solution. A shared, switchable maintenance terminal (CRT monitor
and keyboard) completes the model complement. The new PRNM equipment requires considerably
less floor and desk space, fewer supporting components and reduced inter-cabling than the previous
generation PRNM that was based on standalone computer workstation servers.
Function Of PRNM System Servers

The PRNM subsystem is comprised of the following servers at the zone and system
levels of the ASTRO 25 system.
PRNM Zone-Level Servers (One Each Per Zone)

System-Level Servers (One Each Per System)

System Statistics Server (SSS) optional, used on multiple zone systems only
The role of each server is described in the following sections.
Zone-Level Servers
This section describes zone-level servers.
Air Traffic Router
The ATR hosts a variety of real-time, data processing applications to support user and
system applications. Its functions include:
Providing the affiliation server, the back-end of the optional Affiliation Display
Processing real-time call transactions, being the information source for Zone Watch and RCM
Serving as the source for the optional ATIA data stream used by third-party applications
Logging to disk ATIA data for viewing or export to a text file
Routing RCM command and status/messages to/from the zone controller
Routing call logging information from the zone controller to the ZSS and SSS
Hosting the statistics proxy agent for the zone controller as a source for
Dynamic and Historical Reports statistics
6881009Y05-O April 2004 12-5

Zone Database Server Chapter 12: Introduction to the FCAPS Model and PRNM
The ZDS handles a variety of tasks, including:

Hosting the zone configuration database
Administering the standard and optional applications licenses
Authenticating network manager users accessing the system
Performing back-end support services for user applications
Handling telephone interconnect record processing
The FullVision INM server handles most fault management tasks for the system. FullVision INM server
hosts the HP OpenView Network Node Manager (NNM), which is the foundation upon which FullVision
INM is built. NNM handles object discovery, topology map generation and polling, and is integrated
with FullVision INM server also integrates with the optional Motorola MOSCAD system for monitoring
on the FullVision INM screen alarms from sources such as environmental sensors, uninterruptible
power supplies (UPSs), channel banks, microwave gear, and antenna systems.
Zone Statistics Server and System Statistics Server
The statistics servers are the data repositories for data statistics necessary to drive Historical Reports.
The ZSS is comparable to the Historical Reports Server of the previous generation PRNM. Statistics
such as the number of calls, push-to-talks, and busies are accumulated over preset time intervals. Data
accumulated on an hourly basis for 10 days, daily for 62 days, and monthly for one year.
System-Level Servers
This section describes the system-level servers.
The UCS provides database storage and back-end processes required for most system-wide functions.
Included are the mobile radio records, talkgroup records, and services to automatically distribute
and replicate these records in the ZDS for all zones in a multiple zone system. Only one UCS
is required per single or multiple zone system. The UCS is accessible to authorized users from
any client PC workstation in the single or multiple zone system.
The SSS is the data repository for the statistics necessary to drive system wide Historical Reports.
The SSS is required only with multiple zone systems. Statistics such as the number of calls,
push-to-talks, and busies are accumulated over preset time intervals. Data accumulated on an
hourly basis for 10 days, daily for 62 days, and monthly for one year.
12-6 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Core Services
Core Services
In addition to the user applications, the PRNM system performs a number of vital tasks and core
services essential to its operation and maintenance. Network manager user authentication is one
of the core tasks performed in conjunction with the ZDS. Another is the Application Launcher
on client workstations from where each user application is started. The applications available to
the user are displayed in a Microsoft Explorer window; the License Manager running on the ZDS
checks out a user license for the selected and authorized application.
The PRNM system also time synchronizes the servers using Network Time Protocol (NTP) time
synchronization. The ZDS serves as a secondary master clock if the primary, GPS-based reference at the
master site is not available. Finally, since the servers are interdependent, a Database Blocking process notifies
users if the database is being shut down (such as for required maintenance) and terminates any open sessions.
The PRNM provides the capability to backup each database to DAT-format cassettes. Since the UCS
database is replicated in each ZDS, the system includes an application to rebuild the UCS database from
the ZDS, thus providing an automatic backup of the user configuration database.
FCAPS Model in ASTRO 25

This section details the FCAPS model as it applies to ASTRO 25 systems.
Fault Management
Fault Management encompasses fault detection, fault isolation, and correction of abnormal
operation. Central fault management tasks include:
Monitoring status history for a system and its components
Displaying system fault information
Performing diagnostics on components as needed
Motorola FullVision Integrated Network Manager (INM) is the fault management application for ASTRO
25 releases. FullVision INM provides a centralized view of the operational status of an entire multiple or
single zone system by displaying intuitive, graphical representations (subsystem topology maps) of the
system. Problems are identified rapidly when they occur. Functions and tools also provide the ability
to notify support personnel, track, diagnose, and correct faults in an effective manner. FullVision INM
also maintains a data warehouse, storing up to 30 days of event history for report generation.
Other essential infrastructure and site equipment status can be viewed on FullVision INM using the optional
MOSCAD plug-in. The MOSCAD system is capable of monitoring a broad range of analog, digital,
and simple closure inputs. As such, environmental sensors that do not otherwise have connectivity to
the networksuch as UPSs, channel banks, microwave gear, and antenna systemscan be monitored
for fault conditions and reported to the FullVision INM through the MOSCAD Gateway.
6881009Y05-O April 2004 12-7

Configuration Management Chapter 12: Introduction to the FCAPS Model and PRNM
FullVision INM offers an optional SNMP trap message forwarding capability to pass fault information
to a higher level, Enterprise network manager through a separate Network Interface Card (NIC).
Additionally, faults and interpretive messages may optionally be forwarded to a service technicians
alphanumeric pager through a compatible dial-up, commercial paging service.
Configuration Management gives the operator an interface for configuring the system. The interface
specifies the operational parameters of devices used within a system, such as sites, base radios, switches,
subscriber radios, individual users, and groups. Configuration Management establishes each component in
the system, its relationship to other components, and the associated parameters of the component.
Configuration Management Applications

ASTRO 25 Configuration Management applications provide a point of entry for configuring
devices in the system. PRNM applications manage configuration information at two
levels: the system level and the zone level.
System Level Configuration: User Configuration Manager
The User Configuration Manager (UCM) is the network management application used to enter
and maintain system level configuration information. Through the UCM, the system manager
can configure subscribers, talkgroups, critical sites, adjacent control channels, and security
information at a system level. The UCS database stores parameters that govern a users access
to the system and its features. Stored information includes:
Identities, including radio serial number, use identifier, and group memberships
Radio user capabilities, such as priority level and the ability to place and receive telephone calls
Group and Multigroup capabilities, such as priority levels, and group
memberships in multigroups
Radio user and group access to each site in the system. A network manager can limit a radio
user or group to one site or a group of sites, prohibiting them from using other sites in the system
Operator information, such as privileges, passwords, network access, and identification
Zone Level Configuration: Zone Configuration Manager
The Zone Configuration Manager (ZCM) is a tool used to configure information for the radio system
infrastructure (for example, zone controller, site controllers, base station repeaters, voting subsystems,
and telephone interconnect devices) during various stages of the systems life. Every zone has a ZCM
to manage infrastructure in the zone, and each zone can support up to 64 sites, each with different
infrastructure equipment. Types of information managed by the ZCM includes:
Radio system infrastructure information for sites and equipment
Management infrastructure information such as that provided through
the Zone Statistics Server (ZSS)
12-8 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Accounting Management
Accounting Management
Accounting Management enables charges to be established for the use of resources in the system.
The central tasks accomplished within accounting management include:
Informing users of costs incurred and resources consumed

Enabling accounting limits to be set and tariff schedules to be associated with resource use
Enabling costs to be combined where multiple resources are invoked to
achieve a given communication objective
The ATIA data stream is provided by the ASTRO 25 PRNM subsystem as an optional, licensed interface to
support third-party applications designed to collect individual radio unit and talkgroup traffic data. ATIA data
(a data stream) provides information on the activity of individual radio users and talkgroups, which includes the
number of calls, total call duration, number of busies, total busy time, and so on. This data can be used as input
to an external accounting or billing package. Both intrazone and interzone data is passed through the interface.
Air Traffic Information Access Data

This optional interface provides the raw air traffic data for intra-zone calls. With the addition of
third-party products or services, the ATIA option allows the system owner/operator to generate billing
information to charge individual departments or agencies for their use of the system.
System-Level Air Traffic Information Access Packets

System-Level ATIA Packets provides air traffic data for interzone calls in a multiple zone system.
Air Traffic Information Access Logger and Log Viewer

The ATIA Logger records one days worth of ATIA packets and stores them on the Air Traffic
Router. The log may be viewed on a client PC workstation.
Performance Management tools are used to monitor, collect, log, and evaluate network performance and
resource utilization data. Performance applications for the radio resources are described in this section.
PRNM collects statistics of radio resource usage in the Zone Statistics Server (ZSS) and System Statistics
Server (SSS) for radio units, talkgroups, channels, sites, zones and system-wide activity report generation.
Separate, optional performance applications display real-time communications activity (such as, Zone Watch)
or collect traffic statistics over predetermined intervals for report generation (such as, Dynamic and Historical
Reports). Historical statistics are aggregated into detailed and summarized reports on both an individual
zone and system-wide basis. Statistics are available on an hourly basis for 10 days, daily for 62 days, and
monthly for one year at a zone, site, channel, and user. Other statistics that are useful in troubleshooting,
sizing, and monitoring the system are also collected. The system logs these statistics for a period of 62
days. PRNM also has archival and export features for saving reports or offline data analysis.
6881009Y05-O April 2004 12-9

Zone Historical Reports Application Chapter 12: Introduction to the FCAPS Model and PRNM
Zone Historical Reports Application

This application produces reports on radio infrastructure and radio resource usage within an identified zone. A
predefined set of reports, with field selection capability, is supplied to produce standard or tailored reports.
Custom reports can be developed using Historical Reports underlying Crystal Reports2 reporting engine.
Historical Reports are generated automatically or on demand. Automatic reports are produced at a specific
scheduled time and date or on a recurring time and date interval. Reports can be sent to the monitor screen, a
printer, or Hyper Text Markup Language (HTML) or Comma Separated Values (CSV) files.
System-Wide Historical Reports

The System-Wide Historical Reports application is introduced with the new PRNM system for multiple
zone systems. Radio traffic statistics from multiple zones, including interzone traffic, are accumulated
in the System Statistics Server and collated to produce system-wide reports.
Dynamic Reports
Dynamic Reports are intended for short term monitoring. Report intervals may be set for 15 seconds, one
minute or 15 minutes, and up to 100 intervals can be collected. Multiple objects and up to 12 statistics
can be included in a single report. Like for the Historical Reports, a complete set of predefined Dynamic
Reports is provided. Reports can be output to the client PC workstation display, printer, or file.
This display provides zone-level, real-time line charts that illustrate channel utilization for all call
types group, private, interconnect, control channel, and dynamically blocked calls.
Zone Watch
Zone Watch is a performance management tool having customizable displays and grids to monitor real-time
communications activity in a single zone. The information displayed can help system managers be proactive in
making better resource planning decisions, such as when additional channels need to be added to busier sites.
Zone Watch Grid Screen
Air traffic within a single zone is displayed on a site/channel grid. Real-time call activity
for each channel is displayed in its respective cell.
Zone Watch Control Display
This display presents call activity messages that can be used to isolate errors, trace the progress of a call
and troubleshoot, or analyze current system activity. It also provides information about activity occurring
on the control channel, such as rejects, emergency alarms, and unit affiliations.
Affiliation Display
Upon initial power-up and as mobile users move across a geographic area covered by one radio site
to another, ASTRO 25 mobile and portable radios affiliate to the zone and site now providing the
radio service. The responsibility for providing radio service to the unit is thus handed-off to another
zone and/or site. This mobility management function allows the zone controller to have knowledge
of the site currently serving the unit, such that the unit can be immediately connected or included in
private or group dispatch calls without having to broadcast to all sites.
2. Crystal Reports is an industry-leading reporting engine licensed from Crystal Decisions, a Seagate technologies Company.
12-10 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Security Management
The optional Affiliation Display provides a dynamic view of the sites to which all operating units
are currently affiliated, displaying zone, site, and talkgroup details. This feature makes it easy to
track and troubleshoot radios in the system. Affiliation Display is not a vehicle or unit locator in
an absolute sense; affiliation only suggests the area in which the unit may currently be operating
based on the units last affiliation and the sites radio coverage.
The focus of the Affiliation Display can be on an individual site, a specific talkgroup, or an
individual radio. Graphing capabilities are also included.
Security Management
Security Management controls or limits access to applications, certain features, and configuration data
according to definable access privileges. All users must identify themselves to the system at log-on by
entering a name/ID and a password. The optional Agency Partitioning feature makes it easy to grant
or restrict access by department, location, user type, application, and function.
User Client Security

User Client Security provides the first level of security by denying access to all network management
applications unless the user enters a valid log-on name/ID and the corresponding password.
Security Partitioning
Optional Security Partitioning allows a system administrator to assign access privileges to specific
applications. These applications include Configuration Manager, RCM, Historical Reports, and Zone
Watch. The system administrator can also grant or restrict a users access to multiple zones.
See Volume 6, Security Management for more detailed information on security management.
6881009Y05-O April 2004 12-11

Security Partitioning Chapter 12: Introduction to the FCAPS Model and PRNM
12-12 6881009Y05-O April 2004

Chapter
13
Introduction to Network Management
Applications

This chapter provides a brief overview of each application used to manage your radio system, describes key
features, and explains how to find additional information about the application within your documentation set.
After reading this chapter, you will understand when you would use each application and what you can
do with the application. This chapter also describes the process for accessing the Network Management
Applications. It includes information on the Private Radio Network Management (PRNM) Suite
Application Launcher and the Transport Network Management Application Launcher.
Topics in this Chapter

This chapter contains the following topics:

"Overview of Network Management Applications" on page 13-1
"Private Radio Network Management Applications" on page 13-6
"Transport Network Management Applications" on page 13-65
Overview of Network Management Applications

A network management application is a software tool that helps you to manage a complex radio
communications system and its components, including radios, computers, and internet working components.
Network management applications provide the following benefits for radio system networks:
Minimize system downtime and maintenance costs.
6881009Y05-O April 2004 13-1

FCAPS Designation Chapter 13: Introduction to Network Management Applications
Maximize available resources by assisting with system resource planning.

Simplify monitoring and control of systems.
Reduce human intervention through monitoring.
Provide system security.
Reduce troubleshooting time.
Provide reporting tools to optimize system usage.
Provide near real-time monitoring.
FCAPS Designation

This section groups the applications that are used to manage your ASTRO 25 system by
function. The rest of the chapter discusses each application in alphabetical order, so that you
can easily scan the document to find the application.
Where applicable, the FCAPS designation for each application appears.
F for Fault Management
C for Configuration Management
A for Accounting Management
P for Performance Management
S for Security Management
For more information about the FCAPS model, see Chapter 12, "Introduction to the FCAPS Model and PRNM."
Motorola PRNM Suite Applications Overview

This section lists the Motorola Private Radio Network Management (PRNM) Suite applications.
The PRNM Suite is a set of software applications or tools developed by Motorola to manage your
radio system and its components, such as resources, users, and infrastructure.
Figure 13-1 shows the areas impacted by the PRNM Suite applications.
13-2 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Motorola PRNM Suite Applications Overview
Figure 13-1 PRNM Applications from a System Perspective
Table 13-1 lists the Motorola PRNM Suite applications. These management applications
are available through Application Launcher.
Table 13-1 Motorola PRNM Suite Applications
Applications FCAPS Purpose

Application Launcher N/A A launch point for PRNM applications.
System-Level Applications:
Historical Reports (System Wide) A, P A reporting tool that uses predefined reports to show data from
archived information.
Software Download C A tool that provides software upgrades to specific devices.
System Profile P A tool that allows you to track usage at the system level. Shows
the number of applications open, who is using the application,
the number of available licenses, and the processes of the open
applications.
User Configuration Manager C, S The primary tool to configure and manage radio network users.
Zone-Level Applications:
Affiliation Display P A tool to monitor radio, talkgroup, and site use. Affiliation
Display spans zone, site, and radio unit levels in Figure 13-1.
ATIA Log Viewer P A tool that allows you to view radio events occurring in the
zone in a raw data format from the Air Traffic Router (ATR).
6881009Y05-O April 2004 13-3

Motorola PRNM Suite Applications Overview Chapter 13: Introduction to Network Management Applications
Table 13-1 Motorola PRNM Suite Applications (Continued)

Applications FCAPS Purpose
Dynamic Reports A, P A report tool that provides predefined reports using data taken
dynamically from the database.
FullVision INM, includes: F, P, S The primary fault management tool that you can use to monitor
the status of the system. FullVision Integrated Network
FullVision INM Administration
Manager (INM) spans system and zone-level activity in
FullVision INM Web Browser Figure 13-1.
FullVision INM
FullVision INM allows access to the
following HP OpenView plug-in:
MOSCAD (MOtorola Supervisory F A network fault management solution that you use to monitor
Control And Data acquisition) the status of various third-party devices, such as microwave
radios and environmental equipment.
Historical Reports A, P A reporting tool that uses predefined reports to show data from
archived information. Historical Reports spans zone, site, and
unit levels in Figure 13-1.
Custom Historical Reports A, P A reporting tool that uses provided data from archives to meet
customer parameters.
Radio Control Manager Reports A, P A reporting tool that provides reports on radio activity.
Radio Control Manager C, S The primary tool used to control and monitor radio activity.
Has configuration capability in the Dynamic regrouping
feature. Radio Control Manager spans zone, site, and unit
levels in Figure 13-1.
Router Manager F, C, P, S A tool used to manage routers. This includes the ability to
group routers to perform backup, restore, reboot, and software
download operations on more than one router at a time. This
application is also available from HP OpenView as an alarm
reporting tool that you use to monitor the status of routers.
Zone Configuration Manager C The primary tool used to configure zone-level and system-level
infrastructure equipment.
Zone Profile P A tool to track usage at a zone level. Shows the number of
applications open, who is using the application, the number of
available licenses, and the processes of the open applications.
Zone Watch F, P A tool that monitors call processing resource assignments,
including channels, sites, and any hardware assigned to a call.
Zone Watch spans zone, site, and unit levels in Figure 13-1.
13-4 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Transport Network Management Applications Overview
Transport Network Management Applications

Overview

The Transport Network Management (TNM) applications share a common launching point and are
grouped due to their focus on the network transport equipment. See"Transport Network Management
Applications" on page 13-65 for more information about how to access the TNM applications.
Table 13-2 lists the TNM applications.
Table 13-2 Transport Network Management Applications
Application FCAPS Purpose

CiscoWorks2000 FCPS A tool used to manage the LAN switch.
InfoVista PS The primary tool for performance reports on the network
transport devices in the system.
Preside Multiservice Data Manager FCPS A tool used to manage the WAN switch.
(MDM)
6881009Y05-O April 2004 13-5

Other Motorola Applications Chapter 13: Introduction to Network Management Applications
Other Motorola Applications

Table 13-3 lists other Motorola applications that are used to configure RF infrastruc-
ture equipment and subscribers.
Table 13-3 Other Motorola Applications
Application FCAPS Purpose

Configuration/Service Software (CSS) CF A tool used to configure and service specific RF infrastructure
devices at a site. CSS allows you to determine the equipment
status and operational state. You can change operating
parameters to meet changing system requirements. Lastly, you
can program the specific device. Devices include the following:
Private site controller (PSC 9600)
Simulcast subsystem equipment, including the STR 3000
simulcast base radio
Simulcast site controller (MTC 9600)
ASTRO 25 Repeater Site equipment, including the
ASTRO 25 Site Repeater
ASTRO-TAC 9600 comparator
You can also troubleshoot or test specific equipment.
Customer Programming Software (CPS) C A tool that programs both portable and mobile subscribers. You
can also use it to learn the operating parameters, personalities,
and modes of mobiles and portables. This software is
documented in the CPS program for your radio. The CPS
Online Help is available from the Help menu.
Radio Service Software (RSS) C A tool that configures analog, mutual aid QUANTAR ASTRO
25 Site Repeater. This software is documented elsewhere, see
the QUANTAR and QUANTRO RSS Manual (6881085E35).
Private Radio Network Management Applications

This section describes the PRNM applications, including how to access the applica-
tions using Application Launcher.
13-6 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Application Launcher
Application Launcher
Application Launcher is the starting point to access the Motorola PRNM management applications. Application
Launcher provides a quick and easy way to access one or more management applications without going through
the process of logging on to each application separately and entering your user name and password each time.
Application Launcher provides two ways to access the applications:
Start menu
Windows Explorer window
Application Launcher Menu and Explorer Window

Figure 13-2 shows the Application Launcher menu from the Start menu.
Figure 13-2 Application Launcher Menu
The Windows Explorer window shows you all system-level applications, zones, and zone-level
applications that you have permission to access. Your access permissions, which are set by
the system manager, determine your view of the system in the Windows Explorer window.
Figure 13-3 shows an example of the Windows Explorer window.
6881009Y05-O April 2004 13-7

Why Use Application Launcher? Chapter 13: Introduction to Network Management Applications
Figure 13-3 Example of the Explorer Window
Application Launcher does not provide access to the console prompt or to

Administration menus for any servers in the system.
Why Use Application Launcher?

Application Launcher provides a quick and easy way to access one or more PRNM Suite
applications. With Application Launcher, you do not have to log on to each application
separately and enter your user name and password each time.
Application Launcher Features

You can launch applications from the Start menu or an Explorer window that is launched from a desktop
icon. The system manager assigns permissions to each user in the system. These permissions determine
which applications, security groups, and objects you can access. These permissions also determine your
view of the system by displaying only the system-level applications, zones, and zone-level applications
for which you have access permissions in the Windows Explorer window.
Application Launcher allows you access to the applications that manage and monitor the
system and zones. It also allows you to do the following:
View applications available for the system and for each zone.
Change and store your password.
Change server access.
Exit Application Launcher in a secure manner so that the next user is prompted to log on.
Using Application Launcher

This section explains how to use Application Launcher to access the PRNM network management applications.
13-8 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Using Application Launcher
The Application Launcher online help provides detailed help on windows and menu options.
6881009Y05-O April 2004 13-9

Starting Application Launcher Chapter 13: Introduction to Network Management Applications
Starting Application Launcher
The Private Radio Network Management (PRNM) Suite Application Launcher provides a
quick and easy way to open management applications on the workstation. Procedure 13-1
describes how to start Application Launcher.
Procedure 13-1 How to Start Application Launcher
1 Double-click the Motorola Private Radio Network Management Suite icon

on the desktop (Figure 13-4).
Figure 13-4 Motorola Private Radio Network Management Suite Icon
Result: The Motorola PRNM Suite Login dialog box (Figure 13-5) appears
if you:
Are logging on for the first time.
Did not select the Remember Username and Password check box during
your last session.
Figure 13-5 Motorola PRNM Suite Login Dialog Box
2 In this dialog box, enter the following:

Your user name in the Username field. The default user name is supermgr.
Your password in the Password field. The default password is secure.
The alias or IP address of a Zone Database Server in the Server field, if the
default is not shown. You can change the server at the Login dialog box, but
the change is not permanent.
Do not select the Remember Username and Password check

box. This feature allows users to save their password settings as
a cookie on the workstation. This selection eliminates the need
to enter the ID and password at log in, but it is not a desirable
option for system security reasons. See "Deleting the Stored
Password" on page 13-11 if you select this option by mistake.
13-10 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Deleting the Stored Password
Procedure 13-1 How to Start Application Launcher (Continued)

3 Click OK.
Result: The Windows Explorer window appears (Figure 13-6). This window
shows the system-level applications and zones that you can access.
Figure 13-6 Windows Explorer Window (Displayed When Launcher

Starts)
4 To open the applications, continue to "Opening an Application" on page 13-11.
Deleting the Stored Password
If you accidently turn on the stored password option, the Delete Password Cookie option in the Motorola
pop-up menu lets you delete the password information stored on the local workstation for a particular
user. This means you must enter your login name and password the next time you open Application
Launcher. From the taskbar, right-click the Motorola icon (Figure 13-7).
Figure 13-7 Motorola Icon
See the Application Launcher online help for the full procedure.
Opening an Application
After starting Application Launcher, you can open the management applications for which
you have permissions from one of the following:
Windows Explorer window
6881009Y05-O April 2004 13-11

Opening an Application from the Explorer Window Chapter 13: Introduction to Network Management Applications
Start menu
The Motorola PRNM Suite menu option does not appear in the Start menu until
after you start Application Launcher for the first time. The applications in this
menu are determined by your permissions at the time you log on.
Opening an Application from the Explorer Window
Procedure 13-2 describes how to open a system-level or zone-level application from

the Windows Explorer window.
Procedure 13-2 How to Open an Application from the Windows Explorer Window
1 Start Application Launcher. See "Starting Application Launcher" on page 13-10

for this procedure.
2 From the Windows Explorer window (Figure 13-8), do one of the following:
Double-click a system-level application under the Motorola PRNM Suite
folder.
Continue to step 3 to open a zone-level application.
Result: The application opens.
Figure 13-8 Windows Explorer Window Used to Open Applications
13-12 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Opening an Application from the Explorer Window
Procedure 13-2 How to Open an Application from the Windows Explorer Window (Continued)
3 Select a zone folder, and then double-click a zone-level application (Figure 13-9).
Figure 13-9 Location of Zone-Level Applications on the Windows

Explorer Window
6881009Y05-O April 2004 13-13

Opening an Application from the Start Menu Chapter 13: Introduction to Network Management Applications
Opening an Application from the Start Menu
Procedure 13-3 describes how to open a system-level or zone-level application from the Start menu.
Procedure 13-3 How to Open an Application from the Start Menu
1 From the taskbar, click the Start button.

2 From the Start menu, select Motorola PRNM Suite (Figure 13-10).
Result: A submenu displays a list of zones and system-level applications that
you can access.
Figure 13-10 Motorola PRNM Suite Menu Option on the Start Menu
Your operating system may be Windows 2000 or Windows XP.

3 Do one of the following:
Select a system-level application from the submenu.
Click a zone, and then select a zone-level application on the submenu.
13-14 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Other Sources of Information on Application Launcher
Other Sources of Information on Application Launcher
Table 13-4 shows related information for Application Launcher.

Table 13-4 Other Information for Application Launcher
Related Information Where to find:

How to access See "Starting Application Launcher" on page 13-10.
Procedures See the Application Launcher online help.
Application Launcher online help is available from the Start
menu for the system and zone application levels.
Online help
Includes an overview, procedures, and reference information for
the user interface, including fields, windows, tabs, and buttons.
Affiliation Display
Affiliation Display is an optional PRNM Suite application that monitors the mobility of radios
for a particular zone. Mobility describes how radio users travel between different sites in a zone
and how they communicate with other members of their assigned talkgroup or even with members
outside of their talkgroup. You can view a radio in more than one zone.
As a radio roams from one site to another or changes talkgroups, Affiliation Display updates and
displays the affiliation and de-affiliation information for a monitored radio.
Figure 13-11 shows the main window for Affiliation Display, which provides a summary of affiliation
information from the Radio Viewer, Site Viewer, and Talkgroup Viewer. Each viewer window is represented
on the main window and constantly provides updated information as affiliations on the system change.
Figure 13-11 Example of the Affiliation Display Main Window
6881009Y05-O April 2004 13-15

Why Use Affiliation Display? Chapter 13: Introduction to Network Management Applications
Summary forms on the main window are read-only. You must open the viewer associated
with the summary form to perform any tasks on the information.
Why Use Affiliation Display?

Affiliation Display enables you to view the association of a radio with a talkgroup and site.
This information can be useful for troubleshooting and tracking of radios in the system and
for monitoring the movement of traffic within a zone.
The affiliation information is displayed in three ways: for the entire zone, by site ID, by talkgroup ID, or by
radio ID. This information is near real-time data and is only available when the application is open.
Affiliation Display allows you to do the following:
Monitor affiliation for one or more radios using the Radio Viewer at one or
more sites. You can locate specified radios by ID.
Monitor affiliations by site using the Site Viewer and view a list of talkgroups or radios at a site.
Monitor affiliations by talkgroup using the Talkgroup Viewer. You can view
information for sites at talkgroup or radios at talkgroup.
Affiliation Display can be used to perform the following functions:
Monitor selected radios, talkgroups, and sites dynamically using the main window.
Monitors affiliation and de-affiliation information for the location of radios and
their current talkgroup at a site within a zone.
Note the radio communication about a site, so you can see how traffic moves
within sites in a zone. By tracking selected talkgroups and radio users through a
zone, you can see which sites get the most use.
From the Talkgroup Viewer, create a dynamic graphical display of radio usage at a site.
The usage information is captured in a graph format for talkgroups and sites.
Affiliation Display and Zone Watch
Affiliation Display and Zone Watch are different in the type of information they display. Affiliation Display is
oriented to location and affiliation information organized by site, radio, or talkgroup. It shows only selected
radios as opposed to every radio. Zone Watch is oriented to call traffic and primarily organized by channel.
Affiliation Display Features

The main window of the Affiliation Display shows a summary of the entries that are currently being
viewed by each of the Site Viewer, Talkgroup Viewer, and Radio Viewer.
Site Viewer
The Site Viewer displays the number of talkgroups and number of radios affiliated to that site. You
can see a table displaying each talkgroup ID/alias for that site, along with the number of radios
affiliated to each talkgroup. For even more detail, you can view the individual radio ID/alias
13-16 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Talkgroup Viewer
affiliated to that site. It also shows the radio talkgroup ID/alias and time stamp of affiliation. In
addition to viewing this information at a site level, you have the option to display all sites so that
the affiliation information for the entire zone can be viewed at once.
Talkgroup Viewer
The Talkgroup Viewer can summarize how many radios are affiliated to that talkgroup and the number of
sites at which the talkgroup has radios affiliated. For the next level of detail, you can view the individual
site ID/aliases with radios affiliated to that talkgroup, with the number of radios at each site.
Radio Viewer
The Radio Viewer window displays affiliation information for a custom list of radios. Each row in the
table shows the radio ID, radio alias, talkgroup ID, talkgroup alias, and time stamp of the last change
in affiliation for a particular radio. For the most detail, you can view the talkgroup ID/alias and site
ID/alias that each radio is affiliated to as well as the time stamp of affiliation.
How Affiliation Display Works
Affiliation Display accesses the affiliation database to dynamically update its windows with real-time
affiliation information. As a radio roams from one site to another or changes talkgroups, Affiliation
Display can update the affiliation and de-affiliation information for a monitored radio. Using this
application, you can learn if a radio is turned off or has roamed to another zone.
The affiliation database resides on the Air Traffic Router (ATR) server, which receives radio
call traffic in the form of air traffic information access (ATIA) packets from the zone controller
and broadcasts these packets on the network as an ATIA stream.
The radio call traffic information in this ATIA packet contains talkgroup and site affiliation and
de-affiliation information for each radio user in a particular zone. The affiliation database collects this
information and provides updates to PRNM applications, such as Affiliation Display.
Other Sources of Information on Affiliation Display

Table 13-5 shows related information for Affiliation Display.
Table 13-5 Related Information for Affiliation Display

Through Application Launcher. See "Application Launcher "
How to access
on page 13-7.
Procedures Volume 5, Monitoring System Performance
Affiliation Display online help is available from the Help menu
within the application.
Online help
6881009Y05-O April 2004 13-17

ATIA Log Viewer Chapter 13: Introduction to Network Management Applications
ATIA Log Viewer
ATIA Log Viewer is a PRNM Suite application that allows you to view the raw
ATIA data straight from the ATIA log.
You must first enable ATIA data logging through the ATR servers Administration
menu. Otherwise, no ATIA log data is collected for viewing. See Volume 3,
Administering Servers and Controllers.
Data for Historical and Dynamic Reports is collected regardless of the ATIA log setting.
Figure 13-12 shows the ATIA Log Viewer.
Figure 13-12 ATIA Log Viewer
Why Use ATIA Log Viewer?

The ATIA Log Viewer is a technician tool that allows you to examine air traffic historical data in a
specified zone for one or more particular time intervals. You can also do the following:
View the radio events occurring in a zone. The information is the same as what you
view from Zone Watch, but is presented in a raw data format from the ATR server.
Shows active sites, channel numbers, and radio affiliations.
View a log of what occurs on an hourly interval in the zone.
13-18 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System ATIA Log Viewer Features
ATIA Log Viewer Features

The ATIA Log Viewer allows you to examine historical air traffic data in a specified zone for a particular
time interval or intervals. This feature is normally used to examine data logs when debugging the system.
The ATIA Log Viewer records the last 25 hours of ATIA data packets on the ATR server. The data is
displayed on an hourly basis, and you can select which interval packets you want to view.
The data is displayed in an easy-to-read format and can be printed or saved for future evaluation.
Since the information displayed in the ATIA Log Viewer is a text document, you can format
the information, if required using a third-party application.
ATIA Log Viewer Compared to Zone Watch
ATIA Log Viewer is a log form of the information displayed in Zone Watch. You can use
ATIA Log Viewer to study information at a later time.
Other Sources of Information on ATIA Log Viewer

Table 13-6 shows related information about ATIA Log Viewer.
Table 13-6 Other Information for ATIA Log Viewer

Through Application Launcher.
How to access
See "Application Launcher " on page 13-7.
Procedures Volume 4, Accounting Management
ATIA Log Viewer online help is available from the Help menu
Online help
the user interface, including fields, windows, tabs, and buttons
Configuration/Service Software
Configuration/Service Software (CSS) is a Motorola application that lets you configure devices
after installation or replacement. You can also use CSS to optimize a device, run tests to check
performance, and troubleshoot components of a device.
CSS consists of a core application and specific device applications that depend on the device to which you
are connected. The core application uses all of the common menus that are available before you read the
configuration data from a device. The device application is only active after you read the configuration
data from a device. This application uses the Service menu to perform tasks with the device.
Figure 13-13 shows the CSS main window.
6881009Y05-O April 2004 13-19

Why Use CSS? Chapter 13: Introduction to Network Management Applications
Figure 13-13 Configuration/Service Software Main Window
Why Use CSS?

Table 13-7 lists the devices programmed by CSS. CSS is used to program IP addresses in a
device, as well as to optimize, configure, monitor, and troubleshoot.
You can access the CSS Core application, and from there, use the CSS Core online
help or access the other CSS online help files.
Table 13-7 Devices Programmed Using CSS
Purpose Component For more information:

Simulcast subsystem MTC 9600 simulcast site controller MTC 9600 help
ASTRO-TAC 9600 Comparator ASTRO-TAC 9600 help
800 MHz STR 3000 simulcast base radio STR 3000 simulcast base radio help
or STR 3000 Service help
700 MHz STR 3000 simulcast base radio
13-20 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System CSS Features
Table 13-7 Devices Programmed Using CSS (Continued)

Purpose Component For more information:
ASTRO 25 repeater PSC 9600 PSC 9600 help
subsystem
QUANTAR ASTRO 25 Site Repeater (800, UHF, and ASTRO 25 Site Repeater help
VHF) QUANTAR Service help
or 700 MHz STR 3000 Site Repeater help
700 MHz STR 3000 ASTRO 25 Site Repeater
IntelliRepeater IntelliRepeater IntelliRepeater help
subsystem
Digital mutual aid 700 MHz STR 3000 Conventional Base Radio STR 3000 Conventional Base Radio
help
The 800 MHz QUANTAR conventional base radio, used for digital mutual aid, and the
QUANTAR ASTRO 25 Site Repeater (analog, VHF, UHF, 800), used for analog mutual aid are
both programmed using Radio Service Software (RSS), see the RSS documentation.
The following list provides some of the common tasks you can perform using CSS:
Troubleshoot connectivity of devices.
Connect to a device through a serial or Ethernet connection.
Read the configuration file from a device.
Modify the parameters of a device.
Write the configuration file to a device.
Open and save an archive file.
Set the IP Address for specified devices.
Set the date and time for a device.
Specify an Network Time Protocol server.
Migrate from an IntelliRepeater site.
Verify the VLAN configuration prior to an operating system upgrade.
CSS Features
The CSS application provides the following features and capabilities:
Perform most device configuration and servicing tasks either through a serial connection
to the device or an Ethernet connection over the LAN from the Network Management
subsystem. You use an Ethernet connection to configure almost all parameters for
infrastructure devices (except IRs) through the CSS. The only parameter that requires a
serial connection to configure is the IP address, which is true for all devices. Only the
IR requires a serial connection to configure all of its parameters.
Configure operating parameters for infrastructure devices. CSS provides a mechanism
to archive programming information for specific equipment.
6881009Y05-O April 2004 13-21

Interaction Between CSS and Other Configuration Applications Chapter 13: Introduction to Network Management Applications
Perform alignment procedures for the infrastructure devices that are capable of using the CSS.
Perform service tasks for the device.
Determine if sites or channels are enabled.
Retrieve status and operational information from a device. Along with FullVision INM,
CSS can be used to provide more troubleshooting information on the selected equipment.
You can connect through Ethernet to the equipment to check status and connectivity.
Interaction Between CSS and Other Configuration Applications
CSS is used to configure parameters in the infrastructure devices, for example, the simulcast
subsystem devices, which include the ASTRO-TAC 9600 comparator, the MTC 9600 simulcast
site controller, and the STR 3000 at the simulcast sites.
Each piece of equipment contains a parameter database (nonvolatile memory on a board in the device)
that stores the operating parameters for that device. The parameters are a mix of equipment owned (that
is, the device owns the master copy) and manager owned (that is, the Zone Configuration Manager
(ZCM) owns the master copy). Some parameters are common to both databases.
Manager-Owned and Equipment-Owned Parameters
If you connect CSS locally to configure a device (such as a comparator), you must consider the
effects of manager-owned parameters. In particular, if you change one or more manager-owned
parameters, a change flag is set. This sends a message to the ZCM to notify it that at least one of
the manager-owned parameters has been changed. The ZCM notices the change and downloads the
manager-owned parameters (from the ZCM database) to the agent device so that it is in sync with the
ZCM. The CSS windows show [*] beside all manager-owned parameters as an alert that the parameter
is manager owned. CSS must be used to change equipment-owned parameters.
For example, if you are installing an ASTRO 25 Repeater Site, you must configure the site locally
first. Once you have configured the site locally, you can test the equipment, set up parameters, and
connect the equipment to the network. Once communication occurs between the master and remote
site, any parameter with [*] is downloaded from the ZCM database.
If you change manager-owned parameters on an agent device, the ZCM overwrites the changes at
some point in time depending on the change flag message to the ZCM. Usually this becomes
apparent if you make a change to parameters, but they return to the original settings.
Other Sources of Information on CSS

Table 13-8 shows related information for CSS.
Table 13-8 Other Information for CSS

See the CSS Getting Started booklet that ships with the CD.
How to access
CSS is accessed from the Start/Programs menu.
13-22 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Custom Historical Reports
Table 13-8 Other Information for CSS (Continued)

Volume 7: Diagnostics and Troubleshooting
Volume 10: ASTRO 25 Site Installation and Configuration
Procedures
Volume 11, Simulcast Subsystem Software Installation and
Configuration
CSS core Online help and device-specific Online help is
available from the Help menu within the application.
Online help
Custom Historical Reports
Custom Historical Reports is very similar to Historical Reports. Like Historical Reports, it uses a
third-party application (Seagate Crystal Reports), but the difference is that you can create your own
reports. You select the parameters for the report instead of using predefined parameters and templates
that Historical Reports uses. Custom Historical Reports is a purchasable option.
Using a report generator, you create a customized report with the parameters that you want.
Custom Historical Reports uses Crystal Reports to step you through a series of dialog boxes to
define each set of parameters that you could include in the report.
The Custom Historical Report features apply only to Historical Reports

and not to Dynamic Reports.
Why Use Custom Historical Reports?

If you need to customize your performance reports (zone-level and system-level Historical Reports
only), the Custom Historical Reports option is an additional software package that allows you to modify
existing report templates and create new templates to meet your system needs.
You use Custom Historical Reports to create user-specific reports using predefined data collected by Motorola.
Custom Historical Reports Features

Custom Historical Reports has the following features:
The Report Expert wizard from Crystal Report allows you to select from parameters
collected by the ATIA stream or other reports.
6881009Y05-O April 2004 13-23

Creating Custom Reports Chapter 13: Introduction to Network Management Applications
Reports may be customized to suit your individual needs. Customization includes:

Group and sorting
Charts (bar, line, 3-D)
Top and bottom X filtering
Calculated values
Cross tab, form, form letter, drill-down reports
Special formulas can be included in Custom Historical Reports to create certain effects.
Creating Custom Reports
Custom Historical Reports uses the following statistical data elements to generate a report:
Channel
Zone radio
Zone talkgroup
Zone
System radio
System talkgroup
System
You can use two methods for creating custom reports.
Using one of the predefined reports as a template (easiest way). You can use one
of the standard reports as a template and modify it. Use this method whenever you
are creating a report of the same general format with different statistics, or whenever
a small modification will satisfy your requirements.
You can use the Report Designer feature of Seagate Crystal Reports to customize a report.
Develop a report from the beginning, which generally takes more time,
but allows you greater flexibility.
Using Data Dictionaries
When using either of the two methods to create a custom report, you must select a data dictionary
for the report. All predefined reports are written using the dictionaries. When modifying an existing
report, you may be prompted to supply the dictionary upon opening the report, in which case you
must select the dictionary originally used to develop the report.
The data dictionaries serve two purposes.
The first purpose is to provide a simple table view of zone and system data so that
you do not have to deal with the underlying technicalities.
The second purpose is to isolate the database so that the reports (standard or custom)
do not have to be rewritten each time the database structure changes.
13-24 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Other Sources of Information on Custom Historical Reports
All reports are installed as read-only files. Standard report template files should not be
modified. A new report template should be created by copying or saving the desired
report template to a new file in the same directory.
Other Sources of Information on Custom Historical Reports

Table 13-9 shows related information for Custom Historical Reports.
Table 13-9 Other Information for Custom Historical Reports
To create a custom report, open Seagate Crystal Reports.

How to access
To access a custom report, you can open it from Historical
Reports.
Historical Reports online help is available from the Help menu
Online help
Dynamic Reports
Dynamic Reports is a PRNM Suite application that provides near real-time call data collection
and allows you to display usage trends and patterns of activity for effective monitoring and
reporting. Dynamic Reports is a purchasable option.
Dynamic Reports is based on a third-party application (Seagate Crystal Reports). Dynamic Reports
provides predefined parameters and template formats to display the value of multiple statistics for
one or more managed objects. Once a report is activated, a Dynamic Report window appears and
data is plotted according to the object and the time interval selected.
At the end of each interval, a new set of statistical values is added to the display. When the display reaches the
specified number of intervals, each new interval added causes the oldest interval to be removed from the display.
Figure 13-14 shows a Dynamic Report example.
Dynamic Reports are not available at the system level.
6881009Y05-O April 2004 13-25

Why Use Dynamic Reports? Chapter 13: Introduction to Network Management Applications
Figure 13-14 Dynamic Report Example
Why Use Dynamic Reports?

Use Dynamic Reports to monitor and report usage trends and patterns of activity. You can do the following:
Generate real-time line graphs for a zone or site.
Use predefined formats to display the value of multiple statistics for a zone or site.
Use the data to make changes in how radios and talkgroups are managed. You can closely
examine what happens during a shift or set period of time; for example, you can look at
the busy count and see if calls are being missed.
Based on your monitoring, you could recommend system expansion or decide to modify
your system design to improve communication.
Dynamic Reports Features

Dynamic Reports uses predefined report templates and specified time intervals to create a report.
Report Templates
This section contains descriptions of the predefined reports available with Dynamic Reports.
Zone Templates
Dynamic Reports allows you to create different types of zone-level reports for sites, busies, call
activity, Push-to-Talks (PTTs), channel utilization, affiliations, and call rejects.
13-26 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Site Templates
For example, the Zone Call Activity report provides statistics for determining the levels of different
activities within the zone, such as rejects, site activity packets, and call activity packets.
You can find a complete list of report templates and descriptions in the
Dynamic Reports online help.
Site Templates
Dynamic Reports allows you to create different types of site level reports for channel
utilization, busies, call activity, and PTTs.
For example, the Site Busy Count report contains statistics for the number of busies caused by lack
of resources at this site and the number of busy calls originating at this site.
You can find a complete list of report templates and descriptions in the
Dynamic Reports online help.
Timed Intervals
Dynamic Reports allows you to view statistics in a predefined graphical form for zones and sites.
Dynamic statistical data objects are presented in time-based intervals.
At the end of each interval, a new set of statistical values is added to the display. When the display reaches the
specified number of intervals, each new interval added causes the oldest interval to be removed from the display.
The timed intervals are defined as follows:
15 seconds (default), 1 minute, or 15 minutes
1 to 100 intervals
Dynamic reports are always presented on screen. The graphing window needs to remain open in order
to graph the data. From the screen, you can print the report and save it to disk.
6881009Y05-O April 2004 13-27

Other Sources of Information on Dynamic Reports Chapter 13: Introduction to Network Management Applications
Other Sources of Information on Dynamic Reports

Table 13-10 shows related information for Dynamic Reports.
Table 13-10 Other Information for Dynamic Reports

How to access
Dynamic Reports Online Help is available from the Help menu
Online help
FullVision INM
FullVision Integrated Network Manager (INM) is a PRNM Suite application that is the primary fault
management tool for your system. You can use FullVision INM to monitor the status of the system.
FullVision INM communicates with managed RF system devices using Simple Network Management
Protocol (SNMP), the industry standard communication protocol. SNMP enables the use of industry
standard tools (HP OpenView) as a basis for the development of FullVision INM.
FullVision INM integrates the fault management of Motorola devices and approved third-party
devices. Figure 13-15 shows the root submap of FullVision INM.
Figure 13-15 FullVision INM Main Window
13-28 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System HP OpenView Network Node Manager and FullVision INM
HP OpenView Network Node Manager and FullVision INM

FullVision INM is integrated with Hewlett Packard (HP) OpenView Network Node Manager (NNM).
HP OpenView is a network management tool that works with many integrated solution providers. Router
Manager and MOSCAD are also products that are integrated with HP OpenView.
FullVision INM adds specific Motorola features and functions to HP OpenView, while allowing HP
OpenView manage a variety of standard networking devices. HP OpenView provides an effective third-party
network management platform that is scalable from one node to unlimited number of nodes.
For more information, refer to the HP OpenView manuals.
Why Use FullVision INM?

FullVision INM allows you to monitor the status of components at the system level and zone
level, such as servers, zone controllers, or sites in the zone.
The system-level submap displays multiple zones that make up the system.
The zone-level submap displays only one zone.
FullVision INM is the primary troubleshooting tool that allows you to view alarm information. You use
FullVision INM to monitor your system for faults and the status of devices in the system.
Submap views show the status of devices by color and the graphical
representations of alarm information.
Alarm Categories show different categories of alarms, for the radio
system, routers, or other devices.
Alarms Browsers show a record of what devices are sending alarms or events.
FullVision INM Features

FullVision INM has the following features:
Topology map windows
Alarm Categories and Alarms Browser windows
Web interface
Purchasable options
Topology Maps
FullVision INM provides a graphical user interface with multiple subsystem topology maps. Topology maps
display a centralized view of the system state and can indicate fault conditions of the entire communications
network. Topology maps are the preferred way to track system faults, although you can also use the Alarms
Browser windows. The maps are arranged in a hierarchy with a symbol for each managed device.
The Root map in FullVision INM is the highest level (parent) submap. The following
combinations of symbols can appear in the Root map:
Internet (IP network)
Radio system
MOSCAD
MNR router
6881009Y05-O April 2004 13-29

FullVision INM Managed Objects Chapter 13: Introduction to Network Management Applications
Topology maps have the following features:

Status background color of each symbol that shows the overall health
of the communications system.
Representations of SNMP agents that report on communications devices.
Automatic discovery of the Motorola communications network devices
and approved third-party devices.
Map customization feature that allows you to add geographically accurate background maps.
FullVision INM menu capabilities, such as Paging or Testing Mode.
A quick status map that provides high level zone information.
A topological hierarchy, from there you can drill down to a device to look at
individual devices down to the card level. From there, you can open an Alarms
Browser to view status on a particular device.
FullVision INM Managed Objects
FullVision INM can manage an element in one of two ways. It can use SNMP, if supported by the
device, or it can use a proxy agent. An SNMP proxy agent provides SNMP support for devices that
do not support their own SNMP agent. Multiple devices can be proxied by one of these agents. The
two proxy agents are the Zone Database server and the MOSCAD SNMP Gateway. The following
list shows the high level elements and links managed by FullVision INM.
Elements:
IntelliRepeater site
Motorola Gold Elite Gateway (MGEG) with voice cards and secure cards
Simulcast site
Call processing subsystem (includes the zone controller)
Servers
Switch
Interconnect subsystem
Application platform
Rendezvous Point (RP) routers
Links:
Air Traffic Router to Zone Controller Link
Motorola Gold Elite Gateway to Zone Controller Link
Site Control Path Link
Site Manager Link
Subsite Manager Link
Interconnect Audio Path
13-30 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Alarm Categories and Alarms Browser Windows
Alarm Categories and Alarms Browser Windows
The Alarm Categories and Alarms Browser windows provide access to alarm information.
Alarm Categories
When the FullVision INM application opens, the Alarm Categories window appears. The Alarm Categories
window is used to open the Alarms Browser window and view different types of alarms.
Alarms Browser
The Alarms Browser window displays alarms received by FullVision INM. This list of alarms
shows the severity of the alarm, the date and time it was received by FullVision INM, the
object (device) to which the alarm is related, and the alarm text.
The Filter option allows you to look at filtered alarms. For example, you can track specific
radio system information for long-term troubleshooting. You can also see only related and
specific alarms rather than information on every alarm.
Web Interface
The HP OpenView Java-based FullVision INM Web interface presents the same
information that is available from the Root map.
With the FullVision (fullvis) map open on a NM client, the Web interface allows access
to FullVision INM for up to four additional users.
You can use the Web browser to log on to FullVision INM to view maps and submaps. The FullVision INM
Web interface allows you to easily monitor the status of your network from any place and at any time.
FullVision INM Web interface features include the following:
Perform manual polling and manual discovery.
View topology maps in the Network Presenter.
View alarms in the Alarms Browser windows.
View event recommendations.
The FullVision INM Web interface allows for remote access of FullVision INM using less bandwidth than the
regular fullvis login. This is useful when you have to access the system using an analog phone line.
Purchasable Options
The following features are optional for FullVision INM:

SNMP Trap Forwarding
This option allows FullVision INM to automatically forward non-poller generated
SNMP events sent by Motorola system devices.
Paging
This option allows you to designate faults from system devices to be routed to selected
alphanumeric pagers, through an external alphanumeric paging system.
6881009Y05-O April 2004 13-31

Other Sources of Information on FullVision INM Chapter 13: Introduction to Network Management Applications
Other Sources of Information on FullVision INM

Table 13-11 shows related information for FullVision INM.
Table 13-11 Other Information for FullVision INM

How to access
Volume 2: Fault Management
Procedures Volume 7: Diagnostics and Troubleshooting
Volume 9, Master Site Software Installation and Configuration
FullVision INM online help is available from the Help menu
Online help
Historical Reports
Historical Reports is a PRNM Suite application that allows you to generate reports for system-wide
activity and for individual zones. These reports display data that is stored on the server.
The Historical Reports application generates reports of statistical data that is gathered at specific, predefined
time intervals. You can then create reports from this data to monitor and analyze information about zones,
sites, channels, talkgroups, and radio users. This data is displayed using predefined report templates and
parameters. Historical Reports is based on a third-party application (Seagate Crystal Reports).
Figure 13-16 shows a Historical Report example.
13-32 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Why Use Historical Reports?
Figure 13-16 Historical Reports (Example)
Why Use Historical Reports?

You can use Historical Reports for resource management. For example, you can determine if
interconnect resources are being overused because too many interconnect calls appear in the report.
Historical reports allows you to do long term analysis of traffic data.
Historical Reports Features

Historical Reports uses predefined report templates and specified time intervals to create a report.
You can use Historical Reports to do the following with the report:
View the reports on screen or print a hard copy.
Export the report to one of the following formats:
Comma Separated Values (CSV) Creates a text file where entries
are separated by commas. This format is suitable for export to database
programs, such as Microsoft Access.
HTML Creates an HTML version of the report. This format is suitable for viewing
in a number of external programs such as Web browsers and word processors.
Use the Report Scheduler window to schedule zone-wide and system-wide reports to
occur automatically at specified times with an output to a printer or data file.
6881009Y05-O April 2004 13-33

Report Templates Chapter 13: Introduction to Network Management Applications
Report Templates
This section describes the systemwide and zone reports for Historical Reports.
Standard System Reports
System-wide Historical Reports allows you to create different types of system-level reports by
resources, such as radio user, talkgroup, and system usage.
For example, the Radio User at System Summary Report summarizes the use of the system by all
radio users, providing information such as the total number of all calls.
You can find a complete list of report names and descriptions in the Historical Reports online help.
Standard Zone Reports
Zone Historical Reports allows you to create different types of zone-level reports by resources, such
as channel, radio user, site, talkgroup, zone, ATIA packets, and shared service.
For example, the Zone Busy Report provides busy statistics at the zone level.
You can find a complete list of report names and descriptions in the Historical Reports online help.
Time Intervals
Historical data is stored in time-based intervals. For each interval type, the oldest interval in storage is
removed as a new interval is added to storage. The timed intervals are defined as follows:
Every 15 minutes for 100 intervals (approximately one day, zone level only)
Hourly for 241 intervals (approximately ten days, system and zone level)
Daily for 62 intervals (approximately two months, system and zone level)
Monthly for 12 months (one year, system and zone level)
13-34 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Other Sources of Information on Historical Reports
Table 13-12 shows which zone-level and system-level objects are stored and at what intervals.
Table 13-12 Zone-Level and System-Level Objects Stored by Interval
Object 15 Minutes Hourly Daily Monthly

Zone-level
Zone
Site
Channel
Talkgroup at Zone
Radio User at Zone
System-level
System
Talkgroup at System
Radio User at System
Other Sources of Information on Historical Reports

Table 13-13 shows related information for Historical Reports.
Table 13-13 Other Information for Historical Reports

How to access
Historical Reports Online Help is available from the Help menu
Online help
MOSCAD
MOSCAD is an recommended optional network fault management solution that

provides two levels of management:
Network management levelMOSCAD is a FullVision INM plug-in that is accessible from
the PRNM Suite application. MOSCAD communicates with managed components using
Simple Network Management Protocol (SNMP), the industry standard communication protocol.
Element management levelThe MOSCAD Graphic Master Central (GMC) and the
Graphic Workstation (GWS) (also known as MOSCAD central) enables you to access the
InTouch software, which provides more detailed site alarm information.
Figure 13-17 shows the MOSCAD submap, shown by the Supporting System object.
6881009Y05-O April 2004 13-35

MOSCAD Chapter 13: Introduction to Network Management Applications
Figure 13-17 MOSCAD Submap
Figure 13-18 shows the MOSCAD GMC software.
13-36 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Why Use MOSCAD?
Figure 13-18 MOSCAD GMC Main Window
Why Use MOSCAD?

MOSCAD is an recommended optional network fault management solution that provides a common method
for controlling specific system devices (such as tower lights and power generators) and for collecting and
forwarding data concerning the state of system devices, such as channel banks, microwave, and time reference.
Provides fault information to FullVision INM on a variety of third party devices, including
microwave radios, channel banks, power and environmental equipment.
Provides additional robustness to fault management reporting through acknowledged
trap receipt, alarm filtering, and Remote Terminal Unit (RTU)-based logging.
MOSCAD Features
MOSCAD is a proxy agent to the FullVision INM by forwarding alarm or status information from Motorola
infrastructure and site environmental devices, as well as other approved third party devices.
MOSCAD options include the following:
Remote Terminal Units (RTUs)
RTUs and the Graphic Master Central (GMC) server and Graphic Workstation
(GWS) that allows you to access the InTouch software
6881009Y05-O April 2004 13-37

MOSCAD Remote Terminal Units Chapter 13: Introduction to Network Management Applications
MOSCAD Remote Terminal Units
MOSCAD RTUs are devices connected to end infrastructure or site environmental devices, typically at
remote locations. RTUs gather the alarm or status information and automatically forward it back to the
MOSCAD gateway. The MOSCAD Gateway, in turn, sends the information using SNMP to FullVision
INM. The operation of the MOSCAD Gateway and the associated RTUs is transparent.
FullVision INM provides the user interface that displays the alarm or status information for the end devices.
The functions provided by the FullVision INM are a subset of what a MOSCAD system can support.
MOSCAD GMC
MOSCAD GMC is the central control point. The MOSCAD GMC provides additional resolution to
the alarms being generated, as well as control and logging functions. The MOSCAD GMC can be
used to discover a problem with the equipment and then isolate the problem.
Other Sources of Information on MOSCAD

Table 13-14 shows related information for MOSCAD.
Table 13-14 Other Information for MOSCAD

Through FullVision INM, Chapter 13, "Introduction to Network
How to access
Management Applications."
Volume 2,Fault Management
Procedures Volume 7,Diagnostics and Troubleshooting
Volume 9,Master Site Software Installation and Configuration
MOSCAD Service Manual on CD (9808901C76)
Documentation Third Party Protocols (6802952C50)
MOSCAD Owners Manual (6802994G10)
Radio Control Manager
The Radio Control Manager (RCM) is a PRNM Suite application used to monitor radio
events, issue and monitor commands, and make informational queries of the ASTRO 25
system. The RCM is a purchasable option.
Figure 13-19 shows the RCM main window.
13-38 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Why Use RCM?
Figure 13-19 Radio Control Manager Main Window
Why Use RCM?

The RCM enables you to monitor and manage radio events and commands and to search the database
for radio status information. Using the RCM, you can do the following:
Submit radio commands over the air, select radios to receive the commands, and
track the progress of the commands. After you issue a radio command, you can
view the command and its status in the Command Monitor.
Submit queries to check the status of the radio.
Monitor events in real time as the information becomes available in the system.
An event is an unsolicited message sent from a radio or a solicited command. You
can view and acknowledge radio events in the system.
Create reports. You can create reports for emergency alarms, login sessions, and
radio commands using the RCM Reports application.
All monitoring displays are updated in near real-time as the information becomes available
in the system. Some of these features are available as purchasable options.
6881009Y05-O April 2004 13-39

RCM Features Chapter 13: Introduction to Network Management Applications
RCM Features
This section explains the features of RCM, including how RCM operates, radio commands,
status commands, events, and other specific features.
Normal System Operations
Zone controllers are an integral part of the RCM capabilities because they provide coordination
and communication from the RCM to the radios throughout the system. The RCM has an
inbound and an outbound connection to the zone controller.
During normal system operations when all sites and zones are fully communicating with one another,
the RCM commands operate across multiple zones. An RCM user can issue control commands to radios
regardless of the zone where the radio is currently affiliated. Restricting factors include the following:
Talkgroup attachment RCM users monitor traffic only on their attached talkgroups
and communicate with their attached talkgroups and the zones in the system. Talkgroup
attachment distributes responsibility for talkgroups across multiple RCM users.
Through the User record in the UCM, RCM users are attached to a number
of talkgroups or to all talkgroups. An attachment list determines how radio
events are distributed. To send commands or status queries to radios, the RCM
user must be attached to a radios primary talkgroup.
Through the Radio User record in the UCM, radio users are assigned a
primary talkgroup. Primary talkgroups do not change based upon the target
radios current site, talkgroup, or zone affiliation.
The primary talkgroup and an RCM users list of attachment groups are used to determine
which RCM users can issue radio commands to a radio user, and from which radio users
the RCM user can receive radio activities, such as Status messages.
Security group assignment Through the User record in the UCM, RCM users are assigned
access permissions to one or more security group. Security groups allow you to partition the
system by creating logical groupings. Every Talkgroup record is also assigned a security group.
This means that the RCM user manages talkgroups that belong to their assigned security groups.
The radios primary talkgroup must belong to one of the RCM users assigned security groups.
To send commands and receive events, the User record for the RCM User must contain the appropriate
configuration information. See User Configuration Manager Online Help for more information.
13-40 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Radio Commands
Radio Commands
Radio commands are outbound functions, meaning that the command is sent from the RCM to the
target radios. Radio commands affect the behavior of or request information from the target radios and
can control the behavior of radios anywhere in the system. The status of each command is tracked
through the Command Monitor. Table 13-15 lists the radio commands.
Table 13-15 Radio Commands
Command Description
Regroup Assigns an affiliated radio to a new talkgroup for communication purposes. This command
allows radios to be reassigned over the air without the need for intervention by the radio user.
The Regroup command is useful during emergency situations when radios from different
talkgroups need to communicate.
One useful application of Regroup is to regroup radios to a talkgroup called Stolen rather
than issuing a Selective Inhibit command. This way, the radio can still communicate with
you, but it has been isolated from its normal talkgroup communication.
Storm Plans operate in a similar manner as Regroup on a predefined list of radios.
Cancel Regroup Cancels the last Regroup command for selected radios and removes the radios from the
regrouped talkgroup, allowing the radios to return to their original talkgroups. If you cancel
a regroup without canceling a Selector Lock, no talkgroup is associated with the dynamic
regroup position, and the radio provides an audible tone to notify the radio user of the
problem.
Selector Lock Disables the talkgroup selector switch on a radio, so that the radio user cannot switch to
another talkgroup. The Selector Lock command is useful in tandem with the Regroup
command where it is used to lock a radio on the regrouped talkgroup.
Cancel Lock Cancels the last Selector Lock command for a selected radio, unlocking the radios selector.
Regroup and Lock Sends a Regroup command and then a Selector Lock command for all selected radios. When
you send these commands together for execution, you should cancel both using Cancel
Regroup and Lock or cancel the lock first. Otherwise, no talkgroup is associated with the
dynamic regroup position, and the radio provides an audible tone to notify the radio user
of the problem.
Cancel Regroup and Lock Sends a Cancel Regroup and then a Cancel Lock command to all selected radios.
Selective Inhibit Functionally disables selected radios that are currently affiliated to the system. If an Inhibit is
sent to a radio, that radio is disabled. It can still be powered on and off, but only accepts a
Cancel Inhibit command. No voice communications are possible, but the radio continues to
listen to the control channel and reaffiliates to the system.
You can use Selective Inhibit to disable a stolen radio, invalid radio user, or less important
radios during an emergency situation.
Cancel Inhibit Cancels a Selective Inhibit command and reactivates the radios that were selectively inhibited
in that Selective Inhibit command.
Issuing Status Commands
Status commands are outbound functions that request information from the zone controller.
The following features allow you to issue status commands:
Radio Check: Checks the affiliation status of the radio in order to obtain current
information, including the talkgroup, site, and zone of the radio. The Radio Check
feature operates over-the-air and across zone boundaries.
6881009Y05-O April 2004 13-41

Monitoring Events Chapter 13: Introduction to Network Management Applications
SnapShot: Issues a database inquiry to the RCM database to retrieve the last known status
of a radio, including site, zone, talkgroup, and recent commands to the radio. Unlike Radio
Check, SnapShot does not initiate a direct communication with the radio.
Zone Status: Zone Status requests and receives information regarding the current status of
the zone controller and the links between the zone controller and the RCMs zone.
Monitoring Events
Radio events are inbound events, meaning that the function was initiated by a radio user and sent to
the RCM. Because radio users can select their current affiliation group, they maintain primary control
of the inbound event routing. Radio event displays include the following:
Emergency Alarms
When a radio user presses the emergency alarm button, an Emergency Alarm event appears
in the RCM, and an audible alarm sounds. (Consoles also include this capability.)
Status Events
A radio user can send a predefined radio status over the air without talking. This event
quickly informs you of the radios current operating condition without interrupting normal
talkgroup communication. (A properly configured radio is required.) Some typical
status events include: Arrived at scene, Enroute, or Available.
ChangeMe Requests
A radio user can send an event to ask the RCM to issue a Cancel Lock command to unlock
their selector lock. This is useful when the radio has been regrouped to an affiliated talkgroup,
and the radio user wants to change to a different talkgroup of their choice.
Purchasable Features
The available options depend on which RCM features have been purchased for the
system. The following are purchasable options:
Dynamic Regrouping
You can change the talkgroup assignment of any radio to handle an emergency
situation. Dynamic Regroup arranges radios in your system to handle unique problems
or situations more efficiently. Regroup Commands, Selector Lock Commands,
ChangeMe Requests, and Storm Plans use this function.
If this feature is not purchased, the ChangeMe Requests pane and Storm Plans menu
option are not available, and you cannot issue regroup commands.
Status
A radio user can send a predefined radio status over the air without talking. If this feature
is not purchased, the Status Event pane of the RCM is not available.
13-42 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System RCM on CENTRACOM Elite
Inbound Event Display (IED) on Consoles

This feature is related to Status Events. IED allows a radio user to send a predefined status
event over the air without talking. These status events were previously sent only to RCM. IED
allows you to send these events to a console to ensure that an operator has received the status.
Therefore, the console operator does not have to open RCM to obtain and manage a status event.
IED appears as a floating window that can be displayed on top of the CENTRACOM Elite radio
console position main screen. The IED alerts the operator of new events with a single audible
tone. The operator can then select and acknowledge that he or she has received the status.
When multiple statuses arrive in the queue, the IED default is to put those events on hold. The
operator can then handle events based on highest priority and can delete an event when the call
has been completed. This feature is configured in the User Configuration Manager.
RCM Reports
You can create reports for Emergency Alarms, login sessions, and radio commands.
RCM on CENTRACOM Elite
A CENTRACOM Elite radio console position, equipped with the proper software, is able to open an
RCM user session. Since the RCM is a separate application from CENTRACOM Elite, the console
operator can run both the CENTRACOM Elite and RCM applications simultaneously.
Other Sources of Information on RCM

Table 13-16 shows related information for RCM.
Table 13-16 Other Information for RCM

How to access
Procedures Volume 3,Managing Radio Users
RCM online help is available from the Help menu within the
application.
Online help
Radio Control Manager Reports
Radio Control Manager (RCM) Reports is a PRNM Suite application that is used to create, view, print,
and export standard reports from RCM. These reports use a common format so the data can be used in
spreadsheets. The report information is gathered from current or archived entries in the RCM. RCM
Reports enables you to present and analyze data showing RCM activity on the system.
You can export RCM Reports as either HTML files or Comma Separated Values (CSV)
files for use with other applications. All RCM reports can be scheduled, with the exception
of the Radio Commands by Command report.
Figure 13-20 shows an RCM Reports example.
6881009Y05-O April 2004 13-43

Why Use RCM Reports? Chapter 13: Introduction to Network Management Applications
Figure 13-20 RCM Reports Example
Why Use RCM Reports?

You can create reports that show the following:
Current Login sessionsView who is currently logged in.
Emergency alarm reportsMonitor a historical list of emergency alarms received by
RCM in a selected period. You could false alarms are sent by a particular individual.
If protocol demands this type of message, an excessive number could indicate the
need to find a better way to communicate this message.
Radio commandsView radio commands grouped by command, user or radio.
RCM Reports Features

RCM Reports application allows you to create the following types of reports:
Current Login Sessions
Emergency alarms
Radio Command
Current Login Sessions Report
This report contains the following information about the current login sessions:
Time of Login
13-44 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Emergency Alarms Reports
User Alias
User ID
User Type
Host IP Address
Emergency Alarms Reports
The Emergency Alarms Reports provide a historical listing of the last 50,00l emergency
alarms received by the RCM in a selected period of time. The reports display all emergency
alarms in the active or historical event queues
Table 13-17 lists the types of Emergency Alarms Reports.
Table 13-17 Types of Emergency Alarms Reports
Type of Report Description

Emergency Alarms by Radio This report allows you to select emergency alarm records by time range and radio.
The Time Range and either the Radio User Alias or the Radio ID parameters must be
entered to generate the report.
Emergency Alarms by Talkgroup This report allows you to select emergency alarm records by time range and talkgroup.
The Time Range and either the Talkgroup Alias or the Talkgroup ID parameters must
be entered to generate the report.
Emergency Alarms in the Deleted This report allows you to select deleted emergency alarm records by time range and the
State user who deleted the alarm. The Time Range and Deleting User parameters must be
entered to generate the report.
Emergency Alarms in the This report allows you to select emergency alarm records by time range and the user
Responded State who responded to the alarm. The Time Range and Responding User parameters must
be entered to generate the report.
Radio Command Reports
Radio Command Reports are general purpose reports comprised of radio commands selected
by the Report Generator because they meet certain user specified parameters. Each of the
Radio Command reports has the same output format.
Table 13-18 lists the types of Radio Command Reports.
Table 13-18 Types of Radio Command Reports
Type of Report Description

Radio Commands by Command This report allows you to select commands by Time Range and Command Type
parameters.
Radio Commands by User This report allows you to select commands by Time Range and Manager User
parameters.
Radio Commands by Radio This report allows you to select commands by Time Range and Radio User Alias or
Radio ID parameters.
6881009Y05-O April 2004 13-45

Other Sources of Information on RCM Reports Chapter 13: Introduction to Network Management Applications
Other Sources of Information on RCM Reports

Table 13-19 shows related information for RCM Reports.
Table 13-19 Other Information for RCM Reports

How to access
Procedures Volume 3,Managing Radio Users
RCM Reports online help is available from the Help menu
Online help
Router Manager
Router Manager is a PRNM Suite application that also operates as an HP OpenView

plug-in. Router Manager has two aspects:
Router Manager User Interface (UI), a standalone application
Enables you to group routers to perform backup, restore, reboot, and software download
operations on more than one router at a time. You can also use Router Manager to
maintain router configuration files and software files on the FullVision INM server,
view router information, and configure GGSN routers.
Router Manager, HP OpenView plug-in

Allows you to perform many (but not all) tasks that you can perform in the Router Manager
UI. You can also view a hierarchy of the routers and alarm events.
Figure 13-21 shows the Router Manager UI application.
13-46 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Router Manager
Figure 13-21 Router Manager UI Main Window
Figure 13-22 shows the Router Manager, HP OpenView plug-in. The MNR container map provides
access to the router manager topology, while the Router Manager menu provides options that allow you to
perform checksums, view router information, and launch WEBLink against selected routers.
Figure 13-22 Router Manager, HP OpenView
6881009Y05-O April 2004 13-47

Why Use Router Manager? Chapter 13: Introduction to Network Management Applications
Why Use Router Manager?

Use Router Manager to manage a router or groups of routers. You can perform the following tasks:
View a hierarchy of Motorola Network Router (MNR) S Series (S2500, S4000, S6000)
and Motorola Network Router (MNR) ST Series (ST5000) routers.
Group routers in ways that make your management tasks easier, so that you can perform
tasks on a group of routers, such as downloads and reboots.
Back up and restore Router Manager data files to the FullVision INM server.
You can use this function to input new router sets.
Upgrade router software and firmware.
View runtime logs.
Perform management tasks, such as:
Download files to the routers from the FullVision INM server and upload
files from routers to the FullVision INM server.
Reboot routers.
Set routers reboot directories.
Launch WEBLink or Telnet against routers.
Perform checksums.
View router information.
Overview the default Enterprise OS (EOS) software package
specified for a router model.
Manage router system root passwords.
Configure Router Manager community strings.
Configure and monitor the status of the EOS GGSN service.
Router Manager Features

This section explains the features of Router Manager UI and HP OpenView, and also includes
WEBLink, a tool accessed from Router Manager.
Router Manager UI
The Router Manager UI has the following features and functions:

Build default groups Group routers based on your network topology. It groups by
type of router, for example, all core routers or all exit routers.
Router Manager Log function View runtime logs, which are status displays that monitor
error and status messages from the FullVision INM server backend.
Backup Back up files on the FullVision INM server.
Restore Input new files or restore backup files to the FullVision INM server.
Capture Capture files from a router and upload them to the FullVision INM server.
Download Download software, configuration files, and other non-software files
from the FullVision INM server to selected routers.
13-48 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Router Manager, HP OpenView
Reboot Reboot selected groups and routers, either immediately, in a specified

amount of time, or at a specified time.
View router View information about a particular router and launch
configuration applications against that router.
Checksum Perform checksum calculations on one or more routers. These calculations
verify the validity of key router files. You can direct Router Manager to check the
files on the router against the files stored for the router on the FullVision INM server;
any inconsistencies are reported in the runtime log displays.
Monitor router status Conduct dynamic status monitoring.
Install MIBs Install new MIBs in the HP OpenView database.
File version management View time, date, size and content of configuration files and
router command log files. Also, compare, version, and remove files.
System root password management Change and synchronize system-level root passwords
Community string management Configure the read-only and read-write community
string variables Router Manager uses to communicate with MNR routers.
Router Manager server jobs View, execute and manage jobs queued for execution.
GGSN management Enable or disable GGSN control, configure GGSN parameters,
and create and manage access point names (APNs).
Edit router files Edit router files on the FullVision server
Delete EOS and WEBlink Delete existing EOS software versions and
WEBlink help files from the FullVision server.
Overwrite EOS Overwrite the default EOS software package specified for the router
model with a package appropriate for the routers specific use and function.
Router Manager, HP OpenView
The Router Manager, HP OpenView plug-in has the following features:

A customized Router Manager menu on the HP OpenView menu bar. From
there you can perform checksums, view router information, and launch WEBLink
against selected routers or groups of routers.
An MNR router topology map that allows you to view the hierarchy of the routers.
An MNR Alarms Browser that allows you to view events sent from routers.
An MNR topology map (network presenter), available from the HP OpenView Web interface
that allows you to view the hierarchy of the routers and perform checksums, view router
information, and launch WEBLink against selected routers or groups of routers.
You should use the Router Manager UI, not the Router Manager menus in HP OpenView, to
perform most router management tasks. Router Manager functionality in HP OpenView is limited
to viewing router information, performing checksums, and launching WEBLink.
6881009Y05-O April 2004 13-49

Differences Between Router Manager UI and HP OpenView Chapter 13: Introduction to Network Management Applications
Differences Between Router Manager UI and HP OpenView
In general, using the Router Manager UI provides more features and functions for managing routers than
using Router Manager available from HP OpenView. While the Router Manager UI should be used whenever
possible, the following functions are available when using Router Manager available from HP OpenView:
Checksum. While the Checksum function available from HP OpenView allows you to
perform checksum calculations on the password (user) file or the router command log
(capture.cfg file), you cannot compare the checksum calculations to those stored on the
FullVision INM server. To checksum a password or capture.cfg file, or to compare checksum
calculations to those stored on the FullVision INM server, you must use the Router Manager UI.
View Router. You can view the status of a router when using Router
Manager available from HP OpenView.
WEBLink. You can launch WEBLink when using Router Manager within HP OpenView.
WEBLink
Router Manager provides a launch point for WEBLink, a graphical user interface (GUI) that enables
you to manage MNR S Series and ST Series routers through a Web-based server embedded on the
routers. It provides a more user-friendly way to execute the configuration commands available in
the routers CLI, but configuration changes made through WEBLink are not permanent. WEBLink
also provides router performance statistics in the form of graphs.
Figure 13-23 shows the WEBLink main window.
Figure 13-23 WEBLink Main Window
13-50 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Other Sources of Information on Router Manager
Other Sources of Information on Router Manager

Table 13-20 shows related information for Router Manager.
Table 13-20 Other Information for Router Manager

How to access Router Manager UIThrough Application Launcher. See
"Application Launcher " on page 13-7.
Router Manager, HP OpenViewThrough FullVision
INM, Chapter 13, "Introduction to Network Management
Applications."
Procedures Volume 3, Managing Network Transport Equipment
Reference
FullVision INM Online HelpExplains the MNR S Series
and ST Series router topology maps available using HP
OpenView and the HP OpenView Web Interface.
Volume 2, Fault Management Contains router trap
definitions.
Online help from the

Router Manager Online Help
vendor
Enterprise Operating System (EOS) command line
interface help through WEBLink
Other documentation
S Series S6000 Hardware User GuideProvides
instructions for installing a Motorola S Series S6000
router and performing basic device configuration.
ST Series ST5000 Hardware User GuideProvides
instructions for installing a Motorola ST5000 Series
Enterprise OS Software User GuideProvides
information about how to use Enterprise OS (EOS)
software to operate and configure your router.
Enterprise OS Software Reference GuideProvides
detailed information about commands and syntax for all
EOS service parameters.
The manuals listed under Other documentation above are available from within the Router
Manager UI by selecting the Help menu, then EOS Documents.
6881009Y05-O April 2004 13-51

Software Download Manager Chapter 13: Introduction to Network Management Applications
The Software Download (SWDL) Manager is a PRNM Suite application used to transfer and install new
software from a central location or locally. The subsystem types and the devices they contain are:
Digital simulcast subsystem (also known as site)
MTC 9600 simulcast site controller
ASTRO-TAC 9600 comparator
800 MHz STR 3000 simulcast base radio or 700 MHz STR 3000 simulcast base radio
700 MHz STR 3000 Conventional base radio (this device can only
be downloaded to while off-line).
ASTRO 25 Repeater subsystem (also known as site)
Private Site Controller 9600 (PSC 9600)
QUANTAR ASTRO 25 Site Repeater (800, UHF, and VHF)or 700
MHz STR 3000 ASTRO 25 Site Repeater
800 MHz QUANTAR conventional base radio (this device can only
be downloaded to while off-line).
Figure 13-24 shows the Software Download Manager window for a simulcast site.
Figure 13-24 Software Download Manager
Why Use Software Download?

The SWDL Manager allows you to do the following tasks:
Download software to simulcast and ASTRO 25 Repeater Site devices.
Once a channel is added to a subsystem or a subsite is added to a simulcast subsystem
using CSS or ZCM, SWDL can update the software on the newly added devices. Off-line
Software Download allows the transfer and installation of software to a single instance of
a device (such as, one base station) that has been disconnected from the radio network.
See "Software Download Features" on page 13-52 for more information.
Determine the software version.
Obtain device IP information.
Query the Private Site Controller for the number of channels of the ASTRO 25 Repeater Site.
Query the simulcast site controller for the number of channels and subsites
of the simulcast subsystem.
Purge (delete) a software version from selected target devices.
Audit a session using historical information recorded by SWDL Manager.
Software Download Features

Software Download can be accomplished in two ways.
13-52 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Other Sources of Information on Software Download
Centralized Software Download is a Network Management application. It provides

the ability to transfer and install an agents application software from a centralized
location. The Software Download application resides on the Network Management
client and a PC loaded with Configuration/Service Software (CSS). From either PC, you
select device types to which to download software. Centralized Software Download
allows you to select the zone, site, device types and software download operation to
perform. Downloading to a site allows the update of software for:
all of the RF devices at a site
all the RF devices of one type at a site
a combination of the RF device types at a site
Off-line Software Download allows the transfer and installation of software to a single
instance of a device (such as, one base station) that has been disconnected from the radio
network. When you download software to a site, all the devices at the site receive the
software. If all the devices at the site (except the newly added channel) already have the
software, then only the new channel will actually transfer the software to itself.
The SWDL Manager application performs three operations:
Transfer Only: The Transfer Only operation transfers software to a proxy device
and cross-loads it to other devices on the LAN for a simulcast subsystem. The proxy
device for an ASTRO 25 Repeater Site only negotiates with the SWDL Manager
and the other devices handle their own transfers.
Install Only: The Install Only operation allows you to install previously transferred software.
Transfer and Install: The Transfer and Install operation is designed to run both the Transfer
and the Install operations without your intervention. To monitor the progress of Transfer and
Install operations, the SWDL Manager receives progress updates from target devices. SWDL
Manager also creates and stores historical information about each task and operation in log files.
Other Sources of Information on Software Download

Table 13-21 shows related information for Software Download.
Table 13-21 Other Information for Software Download
Use the SWDL Manager icon on the desktop of a

computer with Configuration/Service Software (CSS)
How to access installed.
Procedures Volume 3, Managing Zone Infrastructure
Software Download online help is available from the Help
menu within the application.
Online help
6881009Y05-O April 2004 13-53

System Profile Chapter 13: Introduction to Network Management Applications
System Profile
The System Profile is a PRNM Suite application that displays how system-level applications are
being used by the network management clients. System Profile shows the following system-level
Private Radio Network Management (PRNM) applications:
Historical Reports
Software Download
Figure 13-25 shows an example of System Profile.
Figure 13-25 System Profile
Why Use System Profile?

System Profile allows you to do the following:
View the system-level application usage.
View the system-level application license usage.
System Profile Features

The System Profile application displays information about users that are accessing system-level
applications. The following are key features:
User Application Distribution
The User Application Distribution tab displays a list of system-level applications that are being
run on network management clients in the system. The User Application Distribution tab
also shows the login name of the user and the time the application was started.
License Usage
The License Usage tab shows the purchased licenses for each of the system-level
applications and shows the number of licenses that are currently in use.
13-54 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Other Sources of Information on System Profile
Other Sources of Information on System Profile

Table 13-22 shows related information for System Profile.
Table 13-22 Other Information for System Profile

How to access
User Configuration Manager
The User Configuration Manager (UCM) is a PRNM Suite application used to enter and maintain
subscriber-related configuration information for the User Configuration Server (UCS).
Figure 13-26 shows the UCM main window.
Figure 13-26 User Configuration Manager Main Window
6881009Y05-O April 2004 13-55

Why Use User Configuration Manager? Chapter 13: Introduction to Network Management Applications
Why Use User Configuration Manager?

The UCM configures information for initial configuration of the system and then is used as needed to update
the information. To configure an ASTRO 25 system, you need to enter information into both the UCM and
the Zone Configuration Manager (ZCM). When you initially configure or make changes in the UCM, the
configuration information updates the UCS and is replicated to the Zone Database Server (ZDS) in each zone.
Use the UCM to perform the following tasks:
Configure systemlevel parameters for call capability, including the Adjacent Control
Channels (ACCs) and interzone control paths. You can configure system-level parameters for
the master site, such as parameters for home zone mapping and sub-band restricted ID mapping.
Configure radios, radio users, talkgroups, and multigroups.
Configure security access for users in the system.
Configure the type of Zone Watch windows that users want to monitor.
You must create at least one watch profile before you can start Zone Watch.
User Configuration Manager Features

The UCM spans system-level and zone-level configuration information. Table 13-23
shows the high-level objects.
Table 13-23 High-Level Objects in UCM
Object Types Description

System Configuration Configuration of system-level parameters, such as Adjacent
Control Channels. (ACCs) and interzone control paths.
Subscribers Configuration of zone-level parameters, such as talkgroups
and radio user information. You can also set up home zone
mapping, sub-band restricted mapping, and use profiles to
quickly create records.
Security Configuration of system-level parameters for management
users, such as security information.
Zone Watch Configuration Configuration of zone-level parameters for Zone Watch, such
as filters, watch window definitions, and watch profiles.
13-56 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Other Sources of Information on User Configuration Manager
Other Sources of Information on User Configuration Manager

Table 13-24 shows related information for User Configuration Manager.
Table 13-24 Other Information for User Configuration Manager

How to access
Volume 3, Administering Management Application Users Users
Volume 3, Managing Radio Users
Procedures
Volume 7:Diagnostics and Troubleshooting
User Configuration Manager online help is available from the
Help menu within the application.
Online help
Zone Configuration Manager
The Zone Configuration Manager (ZCM) is a PRNM Suite application that is used to configure and maintain
operational parameters for equipment in an ASTRO 25 system. The Zone Database Server (ZDS) hosts the
ZCM database, which stores configuration information for the zones infrastructure equipment.
To configure a ASTRO 25 system, you need to enter information into the ZCM and the UCM applications.
Figure 13-27 shows the ZCM main window with the ASTRO 25 Site Repeater object selected.
Figure 13-27 Zone Configuration Manager
6881009Y05-O April 2004 13-57

Why Use Zone Configuration Manager? Chapter 13: Introduction to Network Management Applications
Why Use Zone Configuration Manager?

Use ZCM to manage the infrastructure in a zone. Infrastructure refers to the physical equipment in the
zone, such as the ASTRO 25 Site Repeaters, simulcast base radios, and the zone controller.
Use the ZCM application to perform the following tasks:
Configure the zone infrastructure equipment.
Execute diagnostic commands to force a device in the zone into a certain functional state.
Zone Configuration Manager Features

The ZCM spans zone-level configuration information. For example, you can configure
zone-level parameters, such as ASTRO 25 Repeater Sites and simulcast subsystem
equipment. Table 13-25 shows the high-level objects.
Table 13-25 High-Level Objects in ZCM
Object Types Description

Zone Configures and manages the attributes relating to a zone.
Air Traffic Router Configures the ATR server, which collect statistics on the
system and distributes airtime usage data.
Zone Controller Represents the zone controller for the zone. Provides access to
the Rendezvous Point (RP) routers.
Level of Service Configures the level of service availability for call requests,
such as the number of interconnect calls allowed or the average
maximum busy delay that is acceptable for group calls or
interconnect calls.
Application Platform Configures the application platform, which hosts the MGEG
application. Provides access to the MGEG object as well as the
voice and line card related objects.
ASTRO 25 Site Repeater Configures the ASTRO 25 Site Repeater operations within a
zone, setting the parameters for a site so that it will function
correctly in the system.
IR Site Configures the IntelliRepeater (IR) site operations within a
zone, setting the parameters for a site so that it will function
correctly in the system.
Simulcast Subsystem Configures a simulcast subsystem within a zone. Includes the
site controller, channels, comparators, and other equipment or
paths required in a simulcast subsystem.
Switch Includes the Ambassador Electronics Bank (AEB) within a
zone, plus the paths, slots, and cards, and connections for the
switch.
Interconnect Subsystem References the telephone interconnect equipment in the zone
and represents the path selection for telephone interconnect
calls.
13-58 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Interaction Between ZCM and Other Configuration Applications
Interaction Between ZCM and Other Configuration Applications
CSS is used to configure parameters in the infrastructure devices, for example, the simulcast
subsystem devices, which include the ASTRO-TAC 9600 comparator, the MTC 9600 simulcast
site controller, and the STR 3000 at the simulcast sites.
Each piece of equipment contains a parameter database (nonvolatile memory on a board in the
device) that stores the operating parameters for that device. The parameters are a mix of equipment
owned (that is, the device owns the master copy) and manager owned (that is, the ZCM owns
the master copy). Some parameters are common to both databases.
Manager-Owned and Equipment-Owned Parameters
If you use CSS to configure a device (such as a comparator), you must consider the effects of
manager-owned parameters. In particular, if you change one or more manager-owned parameters, a
change flag is set. This sends a message to the ZCM to notify it that at least one of the manager-owned
parameters has been changed. The ZCM notices the change and downloads the manager-owned
parameters (from the ZCM database) to the agent device so that it is in sync with the ZCM. The CSS
windows show [*] beside all manager-owned parameters as an alert that the parameter is manager
owned. CSS must be used to change equipment-owned parameters.
If you change manager-owned parameters on an agent device, the ZCM overwrites the changes at
some point in time depending on the change flag message to the ZCM. Usually this becomes
apparent if you make a change to parameters, but they return to the original settings.
Other Sources of Information on Zone Configuration Manager

Table 13-26 shows related information for Zone Configuration Manager.
Table 13-26 Other Information for Zone Configuration Manager

How to access Through Application Launcher.
Procedures Volume 3, Managing Zone Infrastructure
Volume 7, Diagnostics and Troubleshooting
Volume 11, Simulcast Subsystem Software Installation and
Configuration
Online help Zone Configuration Manager online help is available from the
Help menu within the application.
6881009Y05-O April 2004 13-59

Zone Profile Chapter 13: Introduction to Network Management Applications
Zone Profile
Zone Profile is a PRNM Suite application that displays detailed information about the
servers and applications that are operating in the zone.
Figure 13-28 shows the Zone Profile application windows.
Figure 13-28 Zone Profile Application Windows
Why Use Zone Profile?

Use Zone Profile to perform the following tasks:
View the server status.
View the system processes running on a server.
View all processes running on a server.
View the system applications installed on a server.
View the zone-level application usage.
View the zone-level application license usage.
Zone Profile Features

The Zone Profile application displays server and application information. Zone Profile also
displays information such as the user login, the client being used, and the time of access. Zone
Profile also keeps an account of the number of licenses that are available and the number of
licenses that are being used. The following are key features:
Servers Tab
The Servers tab displays servers in the selected zone. The Servers tab allows you to
13-60 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Other Sources of Information on Zone Profile
access specific information about the processes and software products on the server.
After selecting a server, a secondary window opens with tabs for viewing general server
information, server processes, and software installed in the server.
User Application Distribution Tab

The User Application Distribution tab (located in the Application Usage tab) presents a
list of zone-level applications that users are running in the selected zone.
License Usage Tab

The License Usage tab (located in the Application Usage tab) lists the licensing information of
the zone-level applications, as well as the number of licenses that are currently in use.
Application Processes Tab

The Application Processes tab shows the application processes that are running on
the selected server. These application processes include user interface processes and
user-invoked application processes. Each process is listed with information such as its
ID, priority, size, time started, and total running time accumulated.
All Processes Tab

The All Processes tab displays all the processes running on the server. Each process is listed
with information such as its ID, priority, size, time started, and total running time accumulated.
Products Tab
The Products tab displays each software application installed on the server
and the softwares version information.
Other Sources of Information on Zone Profile

Table 13-27 shows related information for Zone Profile.
Table 13-27 Other Information for Zone Profile

How to access
Zone Watch
Zone Watch is a PRNM Suite application that lets you monitor radio call traffic for an
individual zone in real time. This application uses different watch windows that allow you
to display only the information you need to see.
Examples of trunking activity and radio call traffic displayed in the watch windows include the following:
Radio IDs
Talkgroup IDs
Aliases
Specific call information
6881009Y05-O April 2004 13-61

Why Use Zone Watch? Chapter 13: Introduction to Network Management Applications
Channel assignments
Figure 13-29 shows the Zone Watch main window.
Figure 13-29 Zone Watch Main Window
Why Use Zone Watch?

This application monitors all radio call activity by pulling trunking information from the
Air Traffic Router (ATR) server, which receives updates from the Air Traffic Information
Access (ATIA) stream distributed by the zone controller.
Zone Watch uses different types of watch windows to display zone, site, talkgroup, and radio information
for a specific zone. The different window profiles, which contain window definitions and filters,
define how to display the information and how to apply limits to the type of data that you can view.
The following are examples of the types of information that you may choose to view:
Activity in a Zone
You can open Zone Watch to monitor radio call activity within a zone. You can see constantly
updated information on who is using the system, where the radio users are located, what
infrastructure resources are being used, and any significant changes in system usage.
Message Type
Information can be selectively displayed by one or any combination of three types
of messages: Secure, ASTRO 25, and Emergency.
13-62 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Zone Watch Features
Raw Data
A Raw Data filter allows the selection or exclusion of information. The data that
is selected for inclusion is displayed as raw data (no formatting).
Site Information
A site filter object allows you to specify the site that the Zone Watch user wants to monitor.
The site selection must consist of a site within the same zone as the Zone Watch. The
site filter essentially limits the view to only a specific site in a zone. You can, however,
have other windows open to show information from other sites in the zone.
Zone Watch Features

The Zone Watch main window displays all of the watch windows for the selected watch
profile. Table 13-28 lists the watch windows.
Table 13-28 Watch Windows
Type of Watch Window Description

Single Site Scroll This watch window displays all of the important data to monitor
radio call information for a single site. This data includes:
Start of event and end of event
Type of event
Emergency flag
Secure flag
Talkgroup alias or ID
Radio alias or ID
Elapsed time of event
Multi-site Scroll This watch window displays all important radio call information
for a two or more sites within a zone.
This information includes:
Time of event
Start of event and end of event
Type of event
Emergency flag
Secure flag
Talkgroup alias or ID
Radio alias or ID
Elapsed time of event
Channel Grid This watch window lets you view control channel and call
information within the zone. You can view all information or
use filters to limit what you view in the window.
6881009Y05-O April 2004 13-63

Other Sources of Information on Zone Watch Chapter 13: Introduction to Network Management Applications
Table 13-28 Watch Windows (Continued)

Type of Watch Window Description
Busy Queue This watch window monitors all busies that occur within the
zone. When a call request receives a busy, the call information
is put into the queue of the Busy Queue watch window. Call
requests are removed from the queue as the call is granted after
a busy.
If a call request does not require resources at all sites and the
request receives a busy at one or more sites, the call request can
appear active and busy at the same time. This means you might
see the call taking place in a site window while the busy queue
shows a busy condition for one or more sites.
The information displayed in the Busy Queue window includes:
Radio aliases or IDs of the radio users involved in the busy
Talkgroup aliases or IDs where the radios are affiliated
Type of call activity, such as talkgroup call or Private Call
Sites involved in the busy
Reason for the busy condition
Raw Display This watch window displays all of the raw packet data for
trunking activities in the zone. This raw packet data is not
formatted and is displayed in a single line, which does not wrap
in the window.
Other Sources of Information on Zone Watch

Table 13-29 shows related information for Zone Watch.
Table 13-29 Other Information for Zone Watch

How to access
Zone Watch online help is available from the Help menu within
the application.
Online help
13-64 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Transport Network Management Applications
Transport Network Management Applications

This section describes the launching mechanisms for the transport network management applications.
Accessing the Transport Network Management Applications from

the Start Menu
This section describes how to access the transport network management applications, including:
Ethernet Switch Management Server software (CiscoWorks2000)
Transport Network Performance Server software (InfoVista)
WAN Switch Management Server software (Preside MDM)
For information about user permissions and more detailed logon instructions, see
Volume 3, Managing Network Transport Equipment and Volume 5, Managing
Network Transport Equipment Performance.
To access the applications, do the following:
1. From the Start menu, select Programs, and then select Transport Network
Management Applications.
2. Select one of the Transport Network Management Applications (Table 13-30).
Table 13-30 Start Menu
IF using the: THEN:

TNM client You can access the following menu options (Figure 13-30):
workstation
CiscoWorks Web Access
InfoVista Network Perf. Client Access
Preside Client Access
Preside Web Access
Figure 13-30 Start Menu on the TNM Client
6881009Y05-O April 2004 13-65

Accessing the Transport Network Management Applications from the Desktop Icons Chapter 13: Introduction to Network Management Applications
Table 13-30 Start Menu (Continued)

IF using the: THEN:
PNM client You can access the following menu options (Figure 13-31):
workstation
Preside Web Access
Figure 13-31 Start Menu on the PNM Client
Accessing the Transport Network Management Applications from

the Desktop Icons
Table 13-31 explains how to access the Transport Network Management Applications from the desktop icons.
13-66 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System CiscoWorks2000
Table 13-31 Desktop Icons
IF using the: THEN:

TNM client workstation You can access the following desktop icons (Figure 13-32):
CiscoWorks Web Access
Preside Web Access
Figure 13-32 Desktop Icons on the TNM Client
PNM client workstation You can access the following desktop icons (Figure 13-33):
Preside Web Access
Figure 13-33 Desktop Icons on the PNM Client
CiscoWorks2000
CiscoWorks2000 is a third-party Transport Network Management (TNM) application that is used

to manage the Cisco Catalyst 6509 Ethernet LAN switch. CiscoWorks2000 includes CiscoView
Device Manager and Resource Manager Essentials (RME).
Figure 13-34 shows CiscoWorks2000 to highlight the Resource Manager Essentials feature.
6881009Y05-O April 2004 13-67

CiscoWorks2000 Chapter 13: Introduction to Network Management Applications
Figure 13-34 CiscoWorks2000 with RME
Figure 13-35 shows CiscoView and the components that appear.
13-68 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Why Use CiscoWorks2000
Figure 13-35 CiscoView Main Window
Why Use CiscoWorks2000

You use CiscoWorks2000 to manage the LAN switches and Multilayer Switch Feature Card (MSFC) routers.
CiscoView
CiscoView provides a graphical representation to manage the LAN switches and MSFC routers providing
both back and front panel displays using a Web browser interface. CiscoView enables you to do the following:
View the system time and system information.
Display VLAN members.
Monitor the performance of Ethernet ports.
Create and monitor system logs.
Monitor the performance of LAN switches and MSFC routers.
Reset the Ethernet card.
Resource Manager Essentials
Resource Manager Essentials (RME) delivers the ability to manage inventory, configuration, and software
updates in the LAN switches, all using a Web browser interface. You can do the following:
View the LAN switch configuration.
6881009Y05-O April 2004 13-69

Using HP OpenView to View LAN Switch Alarms Chapter 13: Introduction to Network Management Applications
Back up and restore the LAN switch software and configuration.

Transfer new software to the LAN switch.
Check device configuration changes for a record of CiscoWorks2000 users who made changes.
Using HP OpenView to View LAN Switch Alarms
You can view alarms on the LAN switches using HP OpenView.
CiscoWorks2000 Features
This section explains the features of CiscoWorks Resource Manager Essentials and CiscoView.
CiscoView
CiscoView is a Web-based device management tool that provides real-time views of networked
LAN switches. These views deliver a continuously updated physical picture of device
configuration and performance conditions, with simultaneous views available for multiple
sessions. Multiple users can access CiscoView simultaneously.
Use CiscoView to do the following:
View a physical representation of front and back device panels, including
component (interface, card, power supply) status.
Monitor real-time statistics for interfaces, resource utilization, and device performance.
Monitoring capabilities display performance and other statistics.
Display the status of a device to monitor the health of the device (Table 13-32).
Table 13-32 Status Colors
Color of Light Status

Green Normal and active status
Red Abnormal status
Yellow Standby status
Brown Inactive mode
13-70 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Resource Manager Essentials
Resource Manager Essentials
RME is a suite of Web-based applications that manage the LAN switches and the MSFC router cards on
the LAN switch. Table 13-33 lists the primary RME features that you use in a Motorola system.
Table 13-33 Key Features of RME
Feature Description
24-Hour Reports
Tells you if the switch is available from the last 24 hours
for performance management purposes.
Informs you when the switch was reloaded and why.
Gives you real-time performance (statistics on the device)
with shorter time intervals than InfoVista, for example,
every minute. See the online CiscoWorks2000 User
Manual for more information.
Change Audit
Views and searches a central repository of all
network changes (for example, inventory or software
management).
Sets up periods of time to monitor network changes.
Maintains the repository.
Converts changes into SNMP traps and forwards them to
your HP OpenView.
Backs up a copy of the switch and router configuration
files.
Searches the archive for configuration files based on
criteria you specify.
Creates custom reports for repetitive tasks.
Groups configuration files and labels them as a set.
Edits configuration files stored in configuration archive
and downloads files to devices.
Creates network show command sets.
Assigns users to network show command sets.
Defines and schedules batch reports that can be executed
at any time you specify.
Software Management
Analyzes upgrade needs and performs upgrades for
Cisco devices on your network.
Validates images with devices before initiating downloads,
and defines and monitors the progress of scheduled tasks.
6881009Y05-O April 2004 13-71

Other Sources of Information on CiscoWorks2000 Chapter 13: Introduction to Network Management Applications
Other Sources of Information on CiscoWorks2000

Table 13-34 shows related information for CiscoWorks2000.
Table 13-34 Other Information for CiscoWorks2000

How to access Through the Transport Network Management menu. See
"Accessing the Transport Network Management Applications
from the Start Menu" on page 13-65 or "Accessing the
Transport Network Management Applications from the
Desktop Icons" on page 13-66.
Procedures Volume 3,Managing Network Transport Equipment
Volume 9,Network Transport Applications Installation and
Configuration
Online help from the CiscoWorks2000 User Manual (HTML). Available online from
vendor the CiscoWorks2000 Help button.
Other vendor
Reference documentation CDIncludes all
documentation
documentation in pdf format in the /doc folder.
CiscoWorks2000 Product Tutorial CDIncludes CD-One
CiscoView and Resource Manager Essential.
CiscoWorks Release Notes (HTML)Available online at
www.cisco.com.
Preside Multiservice Data Manager
The Preside Multiservice Data Manager (MDM) from Nortel Networks is a third-party Transport
Network Management (TNM) application that is used to manage the Nortel WAN switch. Preside
MDM is installed on the WAN Switch Management Server (WSMS).
Preside MDM allows you to view inventory for the WAN switch and view alarms. You can also
use the MDMWeb online browser to view alarms and perform some of the same tasks as the
Preside MDM application. Figure 13-36 shows Preside MDM.
13-72 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Why Use Preside MDM?
Figure 13-36 Preside MDM
Why Use Preside MDM?

You use Preside MDM to manage the WAN switch, including the following tasks:
Perform inventory on the WAN switch.
Back up and restore the WAN switch.
Download software to the WAN switch.
Add a WAN switch.
Connect to the WAN switch by command line.
Collect and display real time performance information.
View the status of WAN switch components.
Display WAN switch alarms.
You can use MDMWeb to do the following:
Connect to the WAN switch by command line.
Display alarms.
Preside MDM Features

Preside MDM provides various features to manage the WAN switch.
Preside MDM
Preside MDM enables you to download software from the Preside MDM server to managed
WAN switches. It also provides the following key features:
Performance Viewer (PV)
Use to collect and display performance information about traffic throughput on the WAN switch
and CPU memory utilization. The PV application provides real-time performance graphs of
important statistical information to help determine the behavior of element components.
6881009Y05-O April 2004 13-73

MDMWeb Chapter 13: Introduction to Network Management Applications
Network Viewer (NV)

Displays a real-time graphic network map that shows the status of the WAN
switch components on the network.
MDMWeb
MDMWeb is part of the Preside MDM software package that allows you to perform fault management tasks
from the Web browser. MDMWeb has more limited functionality than Preside MDM, but offers convenient
multiple Web access for remote users or workstations without PC-Xware. You primarily use MDMWeb to
access the command line and to display alarms on the WAN switch. Figure 13-37 shows Preside MDM.
Figure 13-37 MDMWeb
HP OpenView
You can display alarm information and traps for the WAN switch using HP OpenView.
13-74 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Other Sources of Information on Preside MDM
Other Sources of Information on Preside MDM

Table 13-35 shows related information for Preside MDM.
Table 13-35 Other Information for Preside MDM

Through the Transport Network Management menu. See
How to access from the Start Menu" on page 13-65 or "Accessing the Transport
Network Management Applications from the Desktop Icons" on
page 13-66.
Volume 3, Managing Network Transport Equipment
Procedures Volume 9, Network Transport Applications Installation and
Configuration
Preside Online HelpAvailable from the Help menu
on the Preside MDM window or from MDMWeb
vendor
(http://10.0.0.16:8080/WebNMS/WebNMS.html).
Other vendor Preside MDM 13.3 CDIncludes all documentation in pdf format.
documentation
InfoVista
InfoVista is a customizable performance management application that interfaces with network devices
supporting SNMP. By importing Management Information Base (MIB) files, InfoVista can report and graph a
wide variety of data from multiple devices, such as routers, Ethernet LAN switches, and WAN switches.
InfoVista performs the following performance management tasks:
Collects MIB data at any specified time interval.
Displays the collected data in daily, weekly, monthly, and yearly reports.
Reports and graphs single and multiple device information.
Provides customized reports using preconfigured standardized report templates for
network transport devices in your Motorola radio system.
Figure 13-38 shows the InfoVista main window.
6881009Y05-O April 2004 13-75

Why Use InfoVista? Chapter 13: Introduction to Network Management Applications
Figure 13-38 InfoVista Main Window
Why Use InfoVista?

You can use InfoVista reports for proactive network performance, troubleshooting, and network
capacity planning. Use InfoVista to do the following:
View Motorola custom reports for the Motorola Network Routers (MNR), LAN switch,
WAN switch, and the Transport Network Performance Server (TNPS).
Filter (search) for a particular report.
Use the traps sent to HP OpenView and daily individual reports for troubleshooting purposes.
Navigate folders that are organized by system and zone.
Monitor the system for troubleshooting clues. You see activity on a device
and use it to troubleshoot the device.
InfoVista Features
InfoVista is a performance management tool that provides individual and group report types. Each
report type has four templates to provide daily, weekly, monthly, and yearly reports.
InfoVista client application is used to access the server software. It provides an online
connection to the server to perform administrative tasks, such as starting and stopping existing
reports, adding an instance, or creating a new report.
Traps sent to HP OpenView are generated from the individual device daily reports. Group
reports do not show thresholds or generate traps.
13-76 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Other Sources of Information on InfoVista
InfoVista sends warning and major traps to HP OpenView for key statistics that it
collects. All key statistics have two thresholds:
Tw = Threshold Warning
Tm = Threshold Major
Other Sources of Information on InfoVista

Table 13-36 shows related information for InfoVista.
Table 13-36 Other Information for InfoVista

Through the Transport Network Management menu. See
How to access from the Start Menu" on page 13-65 or "Accessing the
Transport Network Management Applications from the
Desktop Icons" on page 13-66.
Volume 5, Managing Network Transport Equipment
Performance
Procedures
Volume 9, Network Transport Applications Installation and
Configuration
Documentation Guide (pdf): Available from the Help menu in
InfoVista.
QuickStart Manual and Runtime Users Guide. Available
vendor
from the Start menu of the server or client workstation, select
Programs, select InfoVista, and then select Documentation.
6881009Y05-O April 2004 13-77

Other Sources of Information on InfoVista Chapter 13: Introduction to Network Management Applications
13-78 6881009Y05-O April 2004

A
Appendix
Power Supply Reference

The power supply characteristics for each component in the ASTRO 25 communication
system are provided in Table A-1.
The power supply characteristics for system components may vary over time; therefore,
the information in Table A-1 should be used only as a guideline.
Uninterruptible power supply (UPS) backup is recommended for components listed in Table A-1,
however, this list does not suggest that any component not indicated as recommended for UPS
support should not also be provided backup power. A minimum consideration should be made to
keep the system in a wide area trunking mode of operation under a power interruption condition.
Table A-1 Component Power Supply Reference
Power Supply UPS

Component
(AC, DC or both as indicated) Recommendation
Zone Controller 110/220 VAC, no DC available Yes
6509 Cisco LAN Switch Input Power: 110/220 VAC Yes
WAN Switch Input Power: 110/220 VAC Yes
Ethernet Switch HP 2524 or HP 2626 Input Power: 110/220 VAC Yes
AEB Input: 110/220 VAC
Upper and lower busbars connect to an
external +7.0V DC power supply. The upper
busbar connects to a +7.0V DC power supply
and the lower busbar connects to common.
CEB Redundant power supplies to deliver power
to up to six tiers of cards on the CEB
backplane. AC and DC input power supplies
are available.
MGEG Input Power: 110/220 VAC Yes
DIU 110 VAC or optional 220 VAC
6881009Y05-O April 2004 A-1

Other Sources of Information on InfoVista Appendix A: Power Supply Reference
Table A-1 Component Power Supply Reference (Continued)

Power Supply UPS
Component
Channel Bank Supports AC or DC power supply cards with Yes
optional redundancy. The AC power supply
supports 110/240 VAC, and the DC power
supply supports 48 VDC input through the
terminal block on the chassis.
Comparator A 110/220 VAC power supply delivers power Yes
to the cards. A battery revert option is also
available. When more than five wireline
modules are installed in the chassis, a +5V
expansion module must also be installed.
ASTRO-TAC Receiver Input Power: 110 VAC or 12 VDC Yes
Wireline module provides the power supply.
Core Security Mgmt Server Input Power: 110/220 VAC Yes
ACSS Input Power: Two redundant 350 W AC Yes
power supply modules.
Output: The power supply modules sense
their 3.3V, 5V, and 12 VDC power outputs
and provide predictive failure warning when
possible.
Digital Access Cross-connect Switch (DACS) Input Power: 48 VDC (36.5 to 56.5 V) Yes
Firewall Input Voltage 90-260 VAC auto-switch 47-63 Yes
Hz
Input Voltage -42 to -56 VDC (-48 VDC
nominal)
IDS (Intrusion Detector Sensor) A 350 watt power supply operating Yes
voltages:
100127 volts (V) at 50/60 Hertz (Hz); 4.96
amperes (A) maximum
200240 volts (V) at 50/60 Hertz (Hz); 2.48
amperes (A) maximum
System-level Servers (UCS, SSS) Input Power: 110/220 VAC; VDC not Yes
available
Zone-level Servers (ZDS, ZSS, ATR, FullVision Input Power: 110/220 VAC; VDC not Yes
INM) available
Network Transport Servers (ESMS, WSMS, TNPS) Input Power: 110/220 VAC; VDC not
available
MTC 9600 Simulcast Site Controller Input Power: 110/220 VAC, A DC power Yes
supply is also available.
Clients (PNM, TNM Clients) Input Power: 110/220 VAC (depending on
client chosen); VDC not available
A-2 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Other Sources of Information on InfoVista
Table A-1 Component Power Supply Reference (Continued)

Power Supply UPS
Component
Trak 9100 Input Power: Redundant 100/240 VAC Yes
(module 91202)
Output: +5, +15, and -15 VDC reference
output
Each AC input has a 3 amp slo-blo fuse. The
power supply module 9121-1 is for 20 - 60V
dc operation.
Packet Data Gateway Input Power: 110/220 AC (2 auto-sensing, Yes
self-adjusting AC power supplies
An alternative configuration supports DC
power input.
PSC 9600 Site Controller Input Power: 100/240 VAC, 50-60Hz Yes
standard or
DC 48 VDC, 1.5 A
Echo Canceller Input Power: 100 to 240 VAC 5060 Hz
or 40.5 to 60 VDC with positive ground
reference
Quantar Base Station Input Power: 110/220VAC (265W), Yes
110/220VAC (625W), 24VDC, and
48/60VDC. Battery revert options are also
available for AC power supplies.
S6000 Series Routers Input Power: 110 VAC Yes (Core, Exit,
Gateway, GGSN,
Remote Site router)
No (Remote OSS
router, Remote
digital access router,
Border, Peripheral)
STR 3000 Base Station Input Power: 48 VDC from the breaker panel Yes
to provide power to all the modules in the
base radio.
Terminal Server(s) Input Power: 110/220 VAC; VDC not
available
6881009Y05-O April 2004 A-3

A-4 6881009Y05-O April 2004

B
Appendix
ASTRO 25 System Documentation

This appendix provides a listing of manuals applicable to the hardware and software
found in an ASTRO 25 system.
ASTRO 25 Documentation

Table B-1 ASTRO 25 Documentation
Document Title Part Number Purpose

Volume 1: Understanding Your ASTRO 25 6881009Y05 Provides a general view of the system to become
Trunking System familiar with system, system components and
the FCAPS network management model prior to
installation.
Volume 2: Fault Management 6881009Y10 Includes how to use FullVision INM and Router
Manager in your Motorola system.
Volume 3 6881009Y15 Volume 3 contains the following booklets:
Volume 3, Managing Zone Infrastructure 6881009Y16 Explains how to perform tasks in the Zone
Configuration Manager (ZCM) and how to use the
associated windows.
Volume 3, Administering Management 6881009Y17 Contains information about creating users and their
Application Users access rights.
Volume 3, Managing Radio Users 6881009Y18 Provides information about subscriber IDs and
radio user management.
Volume 3, Administering Servers and 6881009Y19 Presents procedures for server administration,
Controllers such as enabling and disabling servers. Includes
procedures that are performed from the servers
administration menu.
Volume 3, Administering Databases 6881009Y21 Describes administering databases, including such
tasks as backup and restore, database optimization,
and exporting database information.
Volume 3, Managing Network Transport 6881009Y22 Discusses how to perform the tasks required to
Equipment manage network transport equipment.
6881009Y05-O April 2004 B-1

ASTRO 25 Documentation Appendix B: ASTRO 25 System Documentation
Table B-1 ASTRO 25 Documentation (Continued)

Volume 4: Accounting Management 6881009Y20 Explains the features and procedures for the
Affiliation Display, System Profile, Zone Profile,
and ATIA Log Viewer applications in the Private
Radio Network Management (PRNM) suite.
Volume 5, Monitoring System Performance 6881009Y26 Provides procedures necessary to monitor ASTRO
25 system performance. Explains how to configure
reports of system usage and view statistics and
real-time information about site, talkgroup, and
radio activities.
Volume 5, Managing Network Transport 6881009Y27 Explains how to use InfoVista, a Network
Equipment Performance Transport management application, for historical
performance reporting and proactive performance
management of critical network transport devices.
Volume 6: Security Management 6881009Y30 Discusses security aspects of an ASTRO 25 system.
Volume 7: Diagnostics and Troubleshooting 6881009Y35 Discusses the system approach to troubleshooting.
Volume 8, Master Site Field Replaceable 6881009Y41 Contains instructions for replacing Field
Units and Entities Replaceable Units and Field Replaceable Entities
in an ASTRO 25 system master site
Volume 8, ASTRO 25 Repeater Site Field 6881009Y42 Contains details and instructions for replacing Field
Replaceable Units and Entities Replaceable Units and Field Replaceable Entities
in an ASTRO 25 Repeater site.
Volume 8, Simulcast Subsystem Field 6881009Y43 Contains details and instructions for replacing Field
Replaceable Units and Entities Replaceable Units and Field Replaceable Entities
in an ASTRO 25 simulcast subsystem.
Volume 9, Master Site Hardware Installation 6881009Y46 Provides hardware installation procedures and
and Configuration hardware configuration information to support
master site hardware installation activities.
Volume 9, Master Site Software Installation 6881009Y47 Provides software installation procedures and
and Configuration software configuration information to support
master site software installation activities.
Volume 9, Network Transport Applications 6881009Y48 Provides insight into software and configuration
Installation and Configuration activities associated with the network transport
components.
Volume 10: ASTRO 25 Site Installation and 6881009Y50 Provides hardware and software installation and
Configuration configuration information supporting the ASTRO
25 Repeater sites.
B-2 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Related Documentation
Table B-1 ASTRO 25 Documentation (Continued)

Volume 11, Simulcast Subsystem Hardware 6881009Y56 Provides hardware installation and configuration
Installation and Configuration procedures to support simulcast subsystem
installation activities.
Volume 11, Simulcast Subsystem Software 6881009Y57 Provides software installation and configuration
Installation and Configuration procedures to support simulcast subsystem
installation activities.
Volume 12: Remote Site Equipment 6881009Y60 Provides information and procedures to support the
Installation and Configuration installation of remote site equipment.
Related Documentation

The following is a list of related documentation.

Table B-2 Related Documentation
Component Vendor Document Name Part Number

CiscoWorks2000 Cisco n/a
Reference documentation (CD),
includes all documentation in the
/doc folder in pdf format
User Manual (HTML): Available
from the CiscoWorks2000 Help
menu
CiscoWorks 2000 Product Tutorial
CD, includes CD-One CiscoView
and Resource Manager Essential
CiscoWorks Release Notes (HTML):
available online: www.cisco.com
Console Database Manager Motorola CENTRACOM Gold Series Console 68P81094E45
Database Manager (CDM) Manual
Alias Database Manager Motorola CENTRACOM Gold Series Alias 68P81096E50
Database Manager (ADM) Manual
DACS Zhone Arca-DACS 100 Quick Start Guide n/a
Version 2.3.0
DACS Zhone Arca-DACS 100 Release 2.3.0 Release n/a
Notes
6881009Y05-O April 2004 B-3

Related Documentation Appendix B: ASTRO 25 System Documentation
Table B-2 Related Documentation (Continued)

Ethernet Switch 3Com 3COM SuperStack II Switch 1100 - Quick DQA1695-0AAA04
Reference Guide
Ethernet Switch 3Com 3COM SuperStack II Switch Family - DNA1695-0AAA06
Release Notes
Ethernet Switch Cisco Catalyst 6000 Family Installation Guide 78-6050-06
Ethernet Switch Cisco Catalyst 6000 Family Quick SW Config. 78-11206-01
Guide - SW Release 6.x
Ethernet Switch Cisco Site Preparation and Safety Guide n/a
Routers 3Com Using the Pathbuilder S5xx Switch 09-1868-000
Ethernet Switch Cisco Cisco Product Documentation Disk 1 and (0112R) 80-5813-03
2 and 80-5815-03
Ethernet Switch Cisco Site Preparation and Safety Guide n/a
Ethernet Switch 3Com SuperStack II Switch 1100 User Guide DUA1695-0AAA04
Ethernet Switch 3Com SuperStack II Switch Management Guide DNA1695-0BAA03
Preside MDM MDM
CD-ROM: Preside MDM 13.1
Online Help: available from Help
menu on the Preside MDM window
or from MDMWeb: http://<ipad-
dress of server>:8080/Web-
NMS/Web/NMS.html
Quality Standards Motorola Quality Standards Fixed Network 6881089E50
Installation Manual (R56) Equipment (FNE)
QUANTAR/IntelliRe- Motorola QUANTAR Digital Capable Station for 68P81095E05
peater Conventional, SECURENET, ASTRO,
6809 Trunking, and IntelliRepeater
Systems
QUANTAR/IntelliRe- Motorola QUANTAR and Quantro RSS Manual 6881085E35
peater
MOSCAD Owners Motorola Motorola Configuration Service Software Site Configuration
Manual Installation Guide CD-ROM
Core/Exit Routers Motorola MNR S Series ST5000 Hardware User CLN7894A-O, tbd
Guide, MNR S Series S6000 Hardware
User Guide.
GGSN Router Motorola MNR S Series S6000 Hardware User tbd
Guide.
Site Routers Motorola MNR S Series ST2500 Hardware User CLN7900A-O,
Guide, MNR S Series S4000 Hardware CLN7891A-O
User Guide.
B-4 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Related Documentation
Table B-2 Related Documentation (Continued)

Site Hub 3Com 3Com / Motorola PS40 Hub Installation Site Configuration
Guide CD-ROM
Site Hub 3Com 3Com SuperStack II Hub - Quick 99-001-995
Reference Guide
Site Hub 3Com 3Com SuperStack II Hub - Release Notes DNA1640-5AAA02
Site Hub 3Com 3Com SuperStack II Hub - User Guide DUA1640-5AAA02
WAN Switch Nortel Companion Supplement - Release Name: n/a
MDM125Pav Version 1.0
WAN Switch Nortel Preside Multiservice Data Manager a/n
Release 12.5 Volume 1-11
WAN Switch Nortel Supplement - Release Name: n/a
MDM125Pav Version 1.0
Zhone TeNSr Channel Zhone Technologies, Channel Bank Manual Integrated Access Pub. 999-001995
Bank Inc. Server, Software Release 5.3
Router Manager Motorola Router ManagerUsers Guide, Release CLN8083E-O
3.10
Secure Communications Motorola ASTRO 25 Trunked Integrated Voice 6881009Y65
and Data System Release 6.4/6.4 SE
Managing Secure Communications
6881009Y05-O April 2004 B-5

B-6 6881009Y05-O April 2004

Index
Index

10Base-2 . . . . . . . . . . . . . . . . . . . 3-6 10Base-T (contd.)

10Base-T . . . . . . . . . . . . . . . . . . . 3-5 parameters and wiring rules . . . . . . . . . . 3-5
accounting management . . . . . . . . . . . . 12-9 application launcher (contd.)

adjacent control channel (ACC) . . . . . . . . . 9-14 features . . . . . . . . . . . . . . . . . . . 13-8
administration menus . . . . . . . . . . . . . . 7-24 overview . . . . . . . . . . . . . . . . . . 13-7
Affiliation Display . . . . . . . . . . . . . . 12-10 starting . . . . . . . . . . . . . . . . . . 13-10
features . . . . . . . . . . . . . . . . . . 13-16 tasks . . . . . . . . . . . . . . . . . . . . 13-8
overview . . . . . . . . . . . . . . . . . 13-15 applications
tasks . . . . . . . . . . . . . . . . . . . 13-16 client . . . . . . . . . . . . . . . . . . . . 12-3
AIMI . . . . . . . . . . . . . . . . . . . . . 4-76 configuration management . . . . . . . . . . 12-8
air traffic information opening . . . . . . . . . . . . . . . . . . 13-11
access . . . . . . . . . . . . . . . . . . . . 12-9 zone level . . . . . . . . . . . . . . . . . . 12-3
access data . . . . . . . . . . . . . . . . . 12-9 ASTRO
logger and log viewer . . . . . . . . . . . . 12-9 Spectra . . . . . . . . . . . . . . . . . . . 4-95
air traffic router . . . . . . . . . . . . . . . . 4-55 Spectra Plus . . . . . . . . . . . . . . . . . 4-95
Air Traffic Router (ATR) . . . . . . . . . 7-10, 7-17 ASTRO 25
menu . . . . . . . . . . . . . . . . . . . . 7-27 components . . . . . . . . . . . . . . . . . 2-1
alarm . . . . . . . . . . . . . . . . . . . . . 7-5 defined . . . . . . . . . . . . . . . . . . . 2-1
emergency. . . . . . . . . . . . . . 9-45, 11-19 functional subsystems . . . . . . . . . . . . 2-8
Alarm card. . . . . . . . . . . . . . . . . . . 4-9 master site . . . . . . . . . . . . . . . . . . 4-1
Alarms Browser window . . . . . . . . . . . 13-31 system capabilities . . . . . . . . . . . . . . 2-24
alert . . . . . . . . . . . . . . . . . . . . . . 7-5 system capacity . . . . . . . . . . . . . . . 2-24
alias database . . . . . . . . . . . . . . . . . 7-10 technology. . . . . . . . . . . . . . . . . . 2-2
alias database manager (ADM) . . . . . . . . . 7-6 transport core . . . . . . . . . . . . . . . . 2-6
alias database manager server . . . . . . . . . . 7-18 ASTRO 25 Repeater Site . . . . . . . . . . . . 5-3
AllStart . . . . . . . . . . . . . . . . . . . . 9-61 Ethernet switch . . . . . . . . . . . . . . . 5-23
Ambassador board (AMB) . . . . . . . . 4-70, 4-72 PSC 9600 Site Controller . . . . . . . . . . . 5-18
Ambassador Electronics Bank (AEB) . . . . . . 4-69 Quantar ASTRO 25 Site Repeater . . . . . . . 5-11
Ambassador board (AMB) . . . . . . . . . . 4-72 site reference . . . . . . . . . . . . . . . . 5-23
architecture . . . . . . . . . . . . . . . . . 4-71 Site Repeater . . . . . . . . . . . . . . . . 5-11
CEB interface . . . . . . . . . . . . . . . . 4-76 site router . . . . . . . . . . . . . . . . . . 5-29
system timer boards . . . . . . . . . . . . . 4-74 STR 3000 ASTRO 25 Site Repeater . . . . . . 5-15
ZAMBI board . . . . . . . . . . . . . . . . 4-75 subsystem configurations . . . . . . . . . . . 5-6
zone controller interface . . . . . . . . . . . 4-76 time of day synchronization. . . . . . . . . . 5-22
Ambassador Interface Mux Interface (AIMI) ASTRO-TAC 9600 comparator . . . . . . . . . 5-46
board . . . . . . . . . . . . . . . . . . . . 4-70 Asynchronous Transfer Mode (ATM) . . . . . . 3-4
functional description . . . . . . . . . . . . 4-78 ATIA log viewer
antivirus software . . . . . . . . . . . . . 4-89, 8-4 features . . . . . . . . . . . . . . . . . . 13-19
application launcher overview . . . . . . . . . . . . . . . . . 13-18
6881009Y05-O April 2004 IX-1

Index
ATIA log viewer (contd.) audio routing

tasks . . . . . . . . . . . . . . . . . . . 13-18 defined . . . . . . . . . . . . . . . . . . . 9-37
audio flow private call . . . . . . . . . . . . . . . . . 9-49
interzone unit-to-unit . . . . . . . . . . . . . 9-49 authentication . . . . . . . . . . . . . . . 4-89, 8-4
intrazone unit-to-unit . . . . . . . . . . . . . 9-49 firewall server software. . . . . . . . . . . . 4-91
audio plane . . . . . . . . . . . . . . . . . . 2-6 autonomous access
audio quality . . . . . . . . . . . . . . . . . . 2-22 autonomous access . . . . . . . . . . . . . . 10-9
backup power . . . . . . . . . . . . . . . . . 4-97 block diagram

balanced line interface . . . . . . . . . . . . . 3-6 IntelliRepeater site . . . . . . . . . . . . . . 5-33
behavior busy call handling . . . . . . . . . . . . . . . 9-60
system switchover . . . . . . . . . . . . . . 9-73 group calls. . . . . . . . . . . . . . . . . . 9-61
BIM . . . . . . . . . . . . . . . . . . . . . . 4-76 individual calls. . . . . . . . . . . . . . . . 9-62
call call processing . . . . . . . . . . . . . . . . . 9-32

basic call flow . . . . . . . . . . . . . . . . 1-23 advanced . . . . . . . . . . . . . . . . . . 9-1
basic, description. . . . . . . . . . . . . . . 1-23 configuration . . . . . . . . . . . . . . . . 9-2
busy call handling . . . . . . . . . . . . . . 9-60 default records . . . . . . . . . . . . . 9-3 to 9-4
emergency. . . . . . . . . . . . . . 9-45, 11-19 during recovery . . . . . . . . . . . . . . . 9-75
grant . . . . . . . . . . . . . . . . . . . . 9-36 equipment . . . . . . . . . . . . . . . . . . 9-29
interzone talkgroup. . . . . . . . . . . . . . 9-38 failure and recovery . . . . . . . . . . . . . 9-75
intrazone talkgroup. . . . . . . . . . . . . . 9-33 home zones . . . . . . . . . . . . . . . . . 9-7
multigroup. . . . . . . . . . . . . . . . . . 9-42 identification numbers . . . . . . . . . . . . 9-6
multiple zone . . . . . . . . . . . . . . . . 1-40 infrastructure configuration . . . . . . . . . . 9-2
occurrances . . . . . . . . . . . . . . . . . 1-40 loss of service . . . . . . . . . . . . . . . . 9-63
priority levels . . . . . . . . . . . . . . . . 9-61 OBT systems . . . . . . . . . . . . . . . 11-17
rejects . . . . . . . . . . . . . . . . . . . . 9-62 static user configuration . . . . . . . . . . . 9-2
requests user configuration . . . . . . . . . . . . . . 9-2
unit-to-unit . . . . . . . . . . . . . . . . 9-46 wide area . . . . . . . . . . . . . . . . . 11-17
single site . . . . . . . . . . . . . . . . . . 1-40 Call Processing. . . . . . . . . . . . . . . . . 1-36
talkgroup . . . . . . . . . . . . . . . . . . 9-33 basics . . . . . . . . . . . . . . . . . . . . 1-17
zone. . . . . . . . . . . . . . . . . . . . . 1-40 subsystem . . . . . . . . . . . . . . . . . . 2-8
call continuation . . . . . . . . . . . . . 9-49, 9-58 call request
defined . . . . . . . . . . . . . . . . . . . 9-32 defined . . . . . . . . . . . . . . . . . . . 9-37
private call . . . . . . . . . . . . . . . . . 9-49 private call . . . . . . . . . . . . . . . . . 9-49
telephone interconnet. . . . . . . . . . . . . 9-58 call setup
call initiation . . . . . . . . . . . . . . . . . . 9-57 defined . . . . . . . . . . . . . . . . . . . 9-35
call maintenance . . . . . . . . . . . . . . . . 9-58 restrictions. . . . . . . . . . . . . . . . . . 9-53
call management . . . . . . . . . . . . . . . . 9-36 call teardown. . . . . . . . . . . . . . . . . . 9-58
phases private call . . . . . . . . . . . . . . . . . 9-49
audio routing . . . . . . . . . . . . . . . 9-37 call termination . . . . . . . . . . . . . . . . 9-58
call continuation . . . . . . . . . . . . . . 9-32 call types . . . . . . . . . . . . . 1-29, 4-93, 9-32
call request . . . . . . . . . . . . . . . . 9-37 emergency calls . . . . . . . . . . . . . . . 1-29
call setup . . . . . . . . . . . . . . . . . 9-35 multigroup calls . . . . . . . . . . . . . . . 1-29
IX-2 6881009Y05-O April 2004

Understanding Your ASTRO 25 Trunking System Index
call types (contd.) configuration management . . . . . . . . . . . 12-8

private calls . . . . . . . . . . . . . . . . . 1-30 applications . . . . . . . . . . . . . . . . . 12-8
ruthless preemption . . . . . . . . . . . . . 1-30 Configuration/Service Software (CSS)
talkgroup calls . . . . . . . . . . . . . . . . 1-29 features . . . . . . . . . . . . . . . . . . 13-21
telephone interconnect . . . . . . . . . . . . 1-30 interaction with ZCM . . . . . . . . . . . 13-22
top of queue . . . . . . . . . . . . . . . . . 1-30 overview . . . . . . . . . . . . . . . . . 13-19
CD-ROM drive . . . . . . . . . . . . . . . . 4-11 tasks . . . . . . . . . . . . . . . . . . . 13-20
CENTRACOM dispatch center . . . . . . . . . 4-59 console database . . . . . . . . . . . . . . . . 7-9
central controller . . . . . . . . . . . . . . . . 1-14 console database manager . . . . . . . . . . . . 4-80
Central Electronics Bank (CEB) architecture . . . 4-76 console database manager (CDM) . . . . . . . . 7-6
ChangeMe requests. . . . . . . . . . . . . . 13-42 console database manager server . . . . . . . . 7-18
channel bank . . . . . . . . . . . . . . . . . . 6-16 Console Interface Electronics (CIE) . . . . . . . 4-79
4-wire card . . . . . . . . . . . . . . . . . 5-56 console operator subsystem . . . . . . . . 2-11, 4-59
digital simulcast subsystem . . . . . . . . . . 5-53 control channel . . . . . . . . . . . . . . . . . 1-15
HSU card . . . . . . . . . . . . . . . . . . 5-56 controllers . . . . . . . . . . . . . . . . . . . 7-1
power supply . . . . . . . . . . . . . . . . 5-56 controlling zone . . . . . . . . . . . . . 1-40, 9-29
simulcast remote site . . . . . . . . . . . . . 5-67 conventional multiple site systems . . . . . . . . 1-9
CiscoWorks2000 conventional radio systems
accessing . . . . . . . . . . . . . . . . . 13-65 basics . . . . . . . . . . . . . . . . . . . . 1-17
features . . . . . . . . . . . . . . . . . . 13-70 operation . . . . . . . . . . . . . . . . . . 1-18
overview . . . . . . . . . . . . . . . . . 13-67 core router . . . . . . . . . . . . . . . . . 2-6, 4-16
tasks . . . . . . . . . . . . . . . . . . . 13-69 core router. . . . . . . . . . . . . . . . . . 4-16
client applications . . . . . . . . . . . . . . . 12-3 core security management server . . . . . . 4-89, 8-4
client/server networking . . . . . . . . . . . . 12-2 antivirus . . . . . . . . . . . . . . . . . . . 8-6
clients firewall management . . . . . . . . . . . . . 8-7
windows-based . . . . . . . . . . . . . . . 12-3 function . . . . . . . . . . . . . . . . . . . 8-6
COIM . . . . . . . . . . . . . . . . . . . . . 4-76 intrusion sensor management . . . . . . . . . 8-7
communication types . . . . . . . . . . . . . . 1-5 user access management . . . . . . . . . . . 8-7
duplex. . . . . . . . . . . . . . . . . . . . 1-7 core services . . . . . . . . . . . . . . . . . . 12-7
half duplex . . . . . . . . . . . . . . . . . 1-7 CPU card and CPU transition card . . . . . . . . 4-7
simplex . . . . . . . . . . . . . . . . . . . 1-5 Current Login Sessions Report . . . . . . . . 13-44
components, MGEG . . . . . . . . . . . . . . 4-61 custom historical reports
configuration data dictionaries . . . . . . . . . . . . . . 13-24
call processing . . . . . . . . . . . . . . . . 9-2 features . . . . . . . . . . . . . . . . . . 13-23
infrastructure . . . . . . . . . . . . . . . . 9-2 overview . . . . . . . . . . . . . . . . . 13-23
updates . . . . . . . . . . . . . . . . . . . 9-10 tasks . . . . . . . . . . . . . . . . . . . 13-23
data database (contd.)

statistical . . . . . . . . . . . . . . . . . . 7-6 user configuration server . . . . . . . . . . . 7-8
system . . . . . . . . . . . . . . . . . . . 7-2 zone. . . . . . . . . . . . . . . . . . . . . 7-8
data dictionaries . . . . . . . . . . . . . . . 13-24 local . . . . . . . . . . . . . . . . . . . 7-9
data service timer zone infrastructure . . . . . . . . . . . . . . 7-8
data service timer . . . . . . . . . . . . . 10-14 zone statistics server . . . . . . . . . . . . . 7-9
database . . . . . . . . . . . . . . . . . . . . 7-1 databases . . . . . . . . . . . . . . . . . . . 7-1
alias. . . . . . . . . . . . . . . . . . . 7-6, 7-10 Digital Access Cross-connect Switch (DACS) . . 4-37
console . . . . . . . . . . . . . . . . . 7-6, 7-9 description. . . . . . . . . . . . . . . . . . 4-39
summary . . . . . . . . . . . . . . . . . . 7-12 features . . . . . . . . . . . . . . . . . . . 4-38
system . . . . . . . . . . . . . . . . . . . 7-7 system redundancy . . . . . . . . . . . . . . 4-39
system statistics server . . . . . . . . . . . . 7-7
6881009Y05-O April 2004 IX-3

Index
digital interface unit (DIU) . . . . . . . . . . . 6-9 dispatch subsystem (contd.)

digital mutual aid. . . . . . . . . . . . . . . . 6-1 Central Electronics Bank (CEB). . . . . . . . 4-76
digital simulcast subsystem . . . . . 2-14, 5-36, 6-19 Console Interface Electronics (CIE) . . . . . . 4-79
10Base-2 . . . . . . . . . . . . . . . . . . 5-81 Packet Data Gateway (PDG) . . . . . . . . . 4-44
ASTRO TAC 9600 comparator . . . . . . . . 5-46 TRAK 9100 . . . . . . . . . . . . . . . . . 4-56
channel bank . . . . . . . . . . . . . . . . 5-53 documentation
communication and interface links . . . . . . 5-37 ASTRO 25 . . . . . . . . . . . . . . . . . B-1
infrastructure . . . . . . . . . . . . . . . . 5-37 related. . . . . . . . . . . . . . . . . . . . B-3
modes of operation . . . . . . . . . . . . . . 5-39 DTI-1000 subsystem . . . . . . . . . . . . . . 4-83
MTC 9600 simulcast prime site controller . . . 5-43 duplex . . . . . . . . . . . . . . . . . . . . . 1-7
network topology . . . . . . . . . . . . . . 5-37 full . . . . . . . . . . . . . . . . . . . . . 1-7
prime site LAN switch . . . . . . . . . . . . 5-49 half . . . . . . . . . . . . . . . . . . . . . 1-7
prime site router . . . . . . . . . . . . . . . 5-52 Dynamic Regrouping . . . . . . . . . . . . . 13-42
remote subsite . . . . . . . . . . . . . . . . 2-16 dynamic reports . . . . . . . . . . . . . . . 12-10
simulcast prime site . . . . . . . . . . . . . 5-40 features . . . . . . . . . . . . . . . . . . 13-26
simulcast remote site . . . . . . . . . . . . . 5-58 overview . . . . . . . . . . . . . . . . . 13-25
simulcast sites . . . . . . . . . . . . . . . . 5-58 tasks . . . . . . . . . . . . . . . . . . . 13-26
dispatch subsystem dynamic user tracking . . . . . . . . . . . . . 9-15
Embassy Dispatch . . . . . . . . . . . . . . . 4-59 ethernet LAN switch

emergency alarm . . . . . . . . . . . . 9-45, 13-42 Ethernet LAN switch . . . . . . . . . . . . . 4-18
emergency alarms . . . . . . . . . . . . . . 11-19 fan assembly. . . . . . . . . . . . . . . . . 4-22
Emergency Alarms Report . . . . . . . . . . 13-45 network analysis module . . . . . . . . . . . 4-22
emergency call . . . . . . . . . . . . . 9-45, 11-19 power supply . . . . . . . . . . . . . . . . 4-22
emergency services . . . . . . . . . . . . . . . 9-44 redundancy . . . . . . . . . . . . . . . . . 4-19
encryption supervisor engine . . . . . . . . . . . . . . 4-20
voice security . . . . . . . . . . . . . . . . 1-21 switching modules . . . . . . . . . . . . . . 4-21
Ethernet . . . . . . . . . . . . . . . . . . . . 3-1 exit router . . . . . . . . . . . . . . . . . . . 4-16
card . . . . . . . . . . . . . . . . . . . . . 4-8 Explorer, Windows
switch . . . . . . . . . . . . . . . . . . . . 2-6 opening applications using . . . . . . . . . 13-12
transition card . . . . . . . . . . . . . . . . 4-8
Failsoft . . . . . . . . . . . . . . . . . . . 11-21 full duplex . . . . . . . . . . . . . . . . . . . 1-7

FastStart . . . . . . . . . . . . . . . . . . . . 9-62 FullVision INM
fault management . . . . . . . . . . . . . . . 12-7 features . . . . . . . . . . . . . . . . . . 13-29
FCAPS model . . . . . . . . . . . . . . . . . 12-7 overview . . . . . . . . . . . . . . . . . 13-28
feature administration tasks . . . . . . . . . . . . . . . . . . . 13-29
purchasable features in RCM . . . . . . . . 13-42 Web Interface . . . . . . . . . . . . . . . 13-31
fiber-optic cable . . . . . . . . . . . . . . . . 3-6 Fullvision INM server . . . . . . . . . . . . . 4-55
firewall FullVision INM server . . . . . . . . . . 7-10, 7-17
management . . . . . . . . . . . . . . . 4-89, 8-4 menu . . . . . . . . . . . . . . . . . . . . 7-28
fixed network equipment (FNE) . . . . . . . . . 9-23 functional subsystems
flow control . . . . . . . . . . . . . . . . . . 3-7 call processing . . . . . . . . . . . . . . . . 2-8
frame relay. . . . . . . . . . . . . . . . . . . 3-6 console operator . . . . . . . . . . . . . . . 2-11
frequency spectrum. . . . . . . . . . . . . . . 1-3 digital simulcast . . . . . . . . . . . . . . . 2-14
management . . . . . . . . . . . . . . . . . 1-4
IX-4 6881009Y05-O April 2004

remote subsite . . . . . . . . . . . . . . . 2-16

IntelliSite . . . . . . . . . . . . . . . . . . 2-12
network management. . . . . . . . . . . . . 2-9
telephone interconnect . . . . . . . . . . . . 2-17
group-based services (contd.) group-based services (contd.)

gateway routers . . . . . . . . . . . . . . . . 2-6 interzone service availability . . . . . . . . . 9-66
MGEG, control, and data routers . . . . . . . 4-14
ggsn router
exit routers . . . . . . . . . . . . . . . . . 4-17
Gold Series Embassy system . . . . . . . . . . 4-70
grant
call . . . . . . . . . . . . . . . . . . . . . 9-36
group-based services . . . . . . . . . . . . . . 9-32
half duplex. . . . . . . . . . . . . . . . . . . 1-7 historical reports (contd.)

hard drive . . . . . . . . . . . . . . . . . . . 4-11 tasks . . . . . . . . . . . . . . . . . . . 13-33
hardware home location register (HLR) . . . . . 7-3, 7-8, 9-23
functional description . . . . . . . . . . . . 4-1 packet data gateway . . . . . . . . . . . . . 7-4
high-level data link control . . . . . . . . . . . 3-7 home zone mapping . . . . . . . . . . . . . . 1-39
historical reports home zones . . . . . . . . . . . . . . . . . . 9-7
features . . . . . . . . . . . . . . . . . . 13-33 HP OpenView
overview . . . . . . . . . . . . . . . . . 13-32 relationship to FullVision INM . . . . . . . 13-29
system-wide . . . . . . . . . . . . . . . . 12-10
identification numbers . . . . . . . . . . . . . 9-6 integrated voice and data . . . . . . . . . . . . 10-1

inbound data request configuration management overview . . . . 10-13
inbound data request . . . . . . . . . . . . 10-10 context activation . . . . . . . . . . . . . . 10-9
individual call context configuration . . . . . . . . . . . . . 10-9
services . . . . . . . . . . . . . . . . . . . 9-46 context deactivation . . . . . . . . . . . . . 10-9
individual-based services context management . . . . . . . . . . . . . 10-8
interzone service availability . . . . . . . . . 9-67 data calls . . . . . . . . . . . . . . . . . 10-10
information data service timer . . . . . . . . . . . . . 10-14
alarm and alert . . . . . . . . . . . . . . . . 7-5 data system configuration parameters . . . . 10-13
InfoVista fault management overview. . . . . . . . . 10-12
accessing . . . . . . . . . . . . . . . . . 13-65 GGSN router
features . . . . . . . . . . . . . . . . . . 13-76 configuration overview. . . . . . . . . . 10-18
overview . . . . . . . . . . . . . . . . . 13-75 GPRS gateway support node . . . . . . . . . 10-6
tasks . . . . . . . . . . . . . . . . . . . 13-76 hardware components . . . . . . . . . . . . 10-3
infrastructure configuration . . . . . . . . . . . 9-2 inbound data request . . . . . . . . . . . . 10-10
mobile subscriber units (MSU) . . . . . . . . 10-7
outbound data request . . . . . . . . . . . 10-11
6881009Y05-O April 2004 IX-5

Index
integrated voice and data (contd.) IntelliRepeater site (contd.)

packet data channel . . . . . . . . . . . . . 10-2 site router . . . . . . . . . . . . . . . . . . 5-35
packet data gateway . . . . . . . . . . . . . 10-5 IntelliSite subsystem . . . . . . . . . . . . . . 2-12
configuration overview. . . . . . . . . . 10-17 interaction between ZCM and CSS . . . . . . 13-59
packet data router . . . . . . . . . . . . . . 10-5 interconnect calls
radio network gateway . . . . . . . . . . . . 10-6 landline-to-radio . . . . . . . . . . . . . . . 9-55
configuration overview. . . . . . . . . . 10-18 radio-to-landline . . . . . . . . . . . . . . . 9-53
resouce allocation timers . . . . . . . . . . 10-14 interconnection services. . . . . . . . . . . . . 9-52
simulcast site steering internet protocol . . . . . . . . . . . . . . . . 3-10
configuration overview. . . . . . . . . . 10-19 interzone communication . . . . . . . . . . . . 9-27
site controller . . . . . . . . . . . . . . . . 10-6 interzone operation
subscriber radios service availability
configuration overview. . . . . . . . . . 10-16 group . . . . . . . . . . . . . . . . . . . 9-66
theory of operations . . . . . . . . . . . . . 10-8 individual . . . . . . . . . . . . . . . . . 9-67
trunked service capabilities . . . . . . . . . . 10-3 interzone talkgroup call . . . . . . . . . . . . . 9-38
zone controller . . . . . . . . . . . . . . . . 10-4 interzone trunking . . . . . . . . . . . . . . . 9-65
IntelliRepeater site . . . . . . . . . . . . . . . 5-32 intrazone talkgroup call . . . . . . . . . . . . . 9-33
operational modes . . . . . . . . . . . . . . 5-36 intrusion detection system sensor . . . . . . . . 4-91
PS40 hub . . . . . . . . . . . . . . . . . . 5-35 IP . . . . . . . . . . . . . . . . . . . . . . . 3-10
QUANTAR IntelliRepeater . . . . . . . . . . 5-34
local area network (LAN) . . . . . . . . . . . . 3-1 loss of service . . . . . . . . . . . . . . . . . 9-63

Ethernet technology . . . . . . . . . . . . . 3-1 between zones . . . . . . . . . . . . . . . . 9-64
master site, transport network . . . . . . . . . 4-11 within a zone . . . . . . . . . . . . . . . . 9-64
star topology. . . . . . . . . . . . . . . . . 3-2 zone controller switchover . . . . . . . . . . 9-69
virtual LANs . . . . . . . . . . . . . . . . 3-11 low delay subrate unit card . . . . . . . . . . . 5-56
LOMI . . . . . . . . . . . . . . . . . . . . . 4-76
IX-6 6881009Y05-O April 2004

management multicast technology . . . . . . . . . . . . . . 2-2

accounting. . . . . . . . . . . . . . . . . . 12-9 multigroup
configuration . . . . . . . . . . . . . . . . 12-8 call . . . . . . . . . . . . . . . . . . . . . 9-42
fault. . . . . . . . . . . . . . . . . . . . . 12-7 multigroup object. . . . . . . . . . . . . . . . 9-11
performance . . . . . . . . . . . . . . . . . 12-9 multigroups . . . . . . . . . . . . . . . . . . 1-22
security . . . . . . . . . . . . . . . . . . 12-11 multiple site system . . . . . . . . . . . . . . 1-31
management information components . . . . . . . . . . . . . . . . . 1-34
alias database . . . . . . . . . . . . . . . . 7-6 multiple zone system . . . . . . . . . . . . . . 1-37
console database . . . . . . . . . . . . . . . 7-6 multizone system . . . . . . . . . . . . . . . . 1-37
mapping additional requirements. . . . . . . . . . . . 1-38
home zone. . . . . . . . . . . . . . . . . . 1-39 mutual aid . . . . . . . . . . . . . . . . . . . 6-1
master site . . . . . . . . . . . . . . . . . 1-35, 4-1 analog. . . . . . . . . . . . . . . . . . . . 6-14
menu ASTRO 25 Repeater sites . . . . . . . . . 6-15
administration menus. . . . . . . . . . . . . 7-24 channel bank . . . . . . . . . . . . . . . 6-16
air traffic router . . . . . . . . . . . . . . . 7-27 ASTRO 25 Repeater Site . . . . . . . . . . . 6-18
FullVision INM server . . . . . . . . . . . . 7-28 18 channels . . . . . . . . . . . . . . . . 6-19
system statistics server . . . . . . . . . . . . 7-25 28 channels . . . . . . . . . . . . . . . . 6-19
user configuration server . . . . . . . . . . . 7-24 channel bank . . . . . . . . . . . . . 5-53, 6-12
zone database server . . . . . . . . . . . . . 7-26 digital . . . . . . . . . . . . . . . . . . . . 6-1
zone statistics server . . . . . . . . . . . . . 7-27 DIU . . . . . . . . . . . . . . . . . . . . . 6-9
mobility management . . . . . . . . . . . . . . 9-15 equipment . . . . . . . . . . . . . . . . . . 6-6
modes of operation . . . . . . . . . . . . 1-31, 1-36 low delay subrate unit card . . . . . . . . . . 5-56
MOSCAD master site CEB . . . . . . . . . . . . . . . 6-5
features . . . . . . . . . . . . . . . . . . 13-37 remote CEB . . . . . . . . . . . . . . . . . 6-2
overview . . . . . . . . . . . . . . . . . 13-35 simulcast subsystem . . . . . . . . . . . . . 6-21
tasks . . . . . . . . . . . . . . . . . . . 13-37 STR 3000 . . . . . . . . . . . . . . . . . . 6-6
Motorola Gold Elite Gateway (MGEG) . . . . . 4-59 MZC 3000 zone controller . . . . . . . . . . . 4-2
card placement. . . . . . . . . . . . . . . . 4-62 alarm card . . . . . . . . . . . . . . . . . . 4-9
components . . . . . . . . . . . . . . . . . 4-61 architecture . . . . . . . . . . . . . . . . . 4-5
CPU board . . . . . . . . . . . . . . . . . 4-67 CD-ROM drive . . . . . . . . . . . . . . . 4-11
E1 line card . . . . . . . . . . . . . . . . . 4-65 components . . . . . . . . . . . . . . . . . 4-5
encryption cards . . . . . . . . . . . . . . . 4-64 controller interfaces . . . . . . . . . . . . . 4-4
single board computer . . . . . . . . . . . . 4-67 CPU card/transition card . . . . . . . . . . . 4-7
system interaction . . . . . . . . . . . . . . 4-61 Ethernet card/transition card . . . . . . . . . 4-8
system monitor board . . . . . . . . . . . . 4-66 hard drive . . . . . . . . . . . . . . . . . . 4-11
transition modules . . . . . . . . . . . . . . 4-68 power supply . . . . . . . . . . . . . . . . 4-11
voice cards . . . . . . . . . . . . . . . . . 4-63 tape drive . . . . . . . . . . . . . . . . . . 4-10
Motorola SmartZone system . . . . . . . . . . 1-33
network interface barrier network management plane . . . . . . . . . . . 2-6

firewall . . . . . . . . . . . . . . . . . 4-91, 8-9 network management router . . . . . . . . . . . 4-16
intrusion detection system sensor . . . . . . . 8-9 network management subsystem. . . . . . . 2-9, 4-46
intrusion sensor management . . . . . . . . . 8-8 OSS. . . . . . . . . . . . . . . . . . . . . 4-46
network management Private Radio Network Management
servers . . . . . . . . . . . . . . . . . . . 12-5 (PRNM) . . . . . . . . . . . . . . . . . . . 4-51
Network Management Applications . . . . . . . 13-1 transport network management . . . . . . . . 4-47
6881009Y05-O April 2004 IX-7

Index
network security network security (contd.)

analysis and control of system and users . . . . 8-3 planning and review . . . . . . . . . . . . . 8-2
components . . . . . . . . . . . . . . . 4-89, 8-4 requirements overview . . . . . . . . . . . . 8-2
core security management server . . . . . 4-89, 8-4 subscription service . . . . . . . . . . . . . 8-10
FullVision INM server . . . . . . . . . . . . 8-1 networking
operations and services . . . . . . . . . . . . 8-9 client/server . . . . . . . . . . . . . . . . . 12-2
object Other Band Trunking (OBT) (contd.)

home zone. . . . . . . . . . . . . . . . . . 9-7 800 MHz . . . . . . . . . . . . . . . . . . 11-1
multigroup. . . . . . . . . . . . . . . . . . 9-11 band plan development . . . . . . . . . . . . 11-4
radio . . . . . . . . . . . . . . . . . . . . 9-7 call processing . . . . . . . . . . . . . . . 11-17
radio user . . . . . . . . . . . . . . . . . . 9-8 frequency band plans . . . . . . . . . . . . . 11-3
source site ACC . . . . . . . . . . . . . . . 9-14 UHF band 1/sub-bands . . . . . . . . . . . . 2-21
system . . . . . . . . . . . . . . . . . . . 9-12 UHF band 2/sub-bands . . . . . . . . . . . . 2-22
talkgroup . . . . . . . . . . . . . . . . . . 9-10 VHF/sub-bands . . . . . . . . . . . . . . . 2-21
open shortest path first . . . . . . . . . . . . . 3-8 out-of-band management . . . . . . . . . . . . 4-58
operations support systems . . . . . . . . . . . 4-46 outbound data request
Other Band Trunking (OBT) . . . . . . . . . . 2-20 outbound data request . . . . . . . . . . . 10-11
packet data channel Preside MDM (contd.)

access . . . . . . . . . . . . . . . . . . . . 10-9 overview . . . . . . . . . . . . . . . . . 13-72
autonomous access . . . . . . . . . . . . . . 10-9 tasks . . . . . . . . . . . . . . . . . . . 13-73
requested access . . . . . . . . . . . . . . . 10-9 prime site
Packet Data Gateway (PDG) . . . . . . . . . . 4-44 LAN switch S1100 . . . . . . . . . . . . . . 5-49
packet data router (PDR) . . . . . . . . . . . 4-45 priority levels . . . . . . . . . . . . . . . . . 9-61
radio network gateway (RNG) . . . . . . . . 4-45 private call . . . . . . . . . . . . . . . . . . . 1-30
packet data router (PDR) audio routing . . . . . . . . . . . . . . . . 1-30
packet data router (PDR) . . . . . . . . . . . 4-45 call continuation . . . . . . . . . . . . . . . 1-30
participating zone . . . . . . . . . . . . . . . 1-40 call teardown . . . . . . . . . . . . . . . . 1-30
performance roaming during . . . . . . . . . . . . . . . 1-30
management . . . . . . . . . . . . . . . . . 12-9 Private Radio Network Management (PRNM). . 4-51,
Performance Reports 12-2
data dictionaries . . . . . . . . . . . . . . 13-24 PRNM suite
power supply. . . . . . . . . . . . . . . . . . 4-11 start menu applications . . . . . . . . . . . 13-11
Preside MDM profiles . . . . . . . . . . . . . . . . . . . . 9-9
accessing . . . . . . . . . . . . . . . . . 13-65 PS40 hub
features . . . . . . . . . . . . . . . . . . 13-73 site ethernet switch . . . . . . . . . . . . . . 5-23
IX-8 6881009Y05-O April 2004

Radio Command Reports . . . . . . . . . . . 13-45 records

Radio Control Manager (RCM) default . . . . . . . . . . . . . . . . . . . 9-4
features . . . . . . . . . . . . . . . . . . 13-40 records, default. . . . . . . . . . . . . . . . . 9-3
monitoring events . . . . . . . . . . . . . 13-42 recovery
overview . . . . . . . . . . . . . . . . . 13-38 call processing behavior . . . . . . . . . . . 9-75
purchasable features . . . . . . . . . . . . 13-42 Redundant Switchover Module . . . . . . . . . 4-69
radio commands . . . . . . . . . . . . . . 13-41 redundant zone controller
status commands . . . . . . . . . . . . . . 13-41 failure and recovery . . . . . . . . . . . . . 9-75
tasks . . . . . . . . . . . . . . . . . . . 13-39 register
radio frequency subsystems . . . . . . . . . . . 5-1 home location . . . . . . . . . . . . . . 7-3, 7-8
ASTRO 25 Repeater Site . . . . . . . . . . . 5-3 visitor location . . . . . . . . . . . . . . 7-4, 7-8
radio identification object . . . . . . . . . . . . 9-7 rejected calls . . . . . . . . . . . . . . . . . . 9-62
radio network gateway (RNG) related documentation . . . . . . . . . . . . . B-3
radio network gateway (RNG) . . . . . . . . 4-45 remote analog access . . . . . . . . . . . . . . 4-58
radio signal strength indicator (RSSI) . . . . . . 9-20 repeater control . . . . . . . . . . . . . . . . 1-10
radio site. . . . . . . . . . . . . . . . . . . . 1-34 Repeater Site
radio system ASTRO 25 Site Repeater subsystem
basic components . . . . . . . . . . . . . . 1-1 operational modes . . . . . . . . . . . . . 5-4
communication types . . . . . . . . . . . . . 1-5 repeaters . . . . . . . . . . . . . . . . . . . . 1-14
conventional . . . . . . . . . . . . . . . . . 1-7 reports
dispatch system . . . . . . . . . . . . . . 1-8 dynamic . . . . . . . . . . . . . . . . . . 12-10
repeater system . . . . . . . . . . . . . . 1-8 historical . . . . . . . . . . . . . . . . . 13-32
conventional, example . . . . . . . . . . . . 1-18 requested access
definition . . . . . . . . . . . . . . . . . . 1-1 requested access . . . . . . . . . . . . . . . 10-9
equipment . . . . . . . . . . . . . . . . . . 1-2 requests
frequency spectrum and range. . . . . . . . . 1-3 unit-to-unit call . . . . . . . . . . . . . . . 9-46
range . . . . . . . . . . . . . . . . . . . . 1-3 requirements, system data . . . . . . . . . . . . 7-1
trunked, example. . . . . . . . . . . . . . . 1-18 resouce allocation timers
trunking technology . . . . . . . . . . . . . 1-11 resouce allocation timers . . . . . . . . . . 10-14
users . . . . . . . . . . . . . . . . . . . . 1-21 restrictions
radio system databases . . . . . . . . . . . . . 7-1 call setup . . . . . . . . . . . . . . . . . . 9-53
radio user . . . . . . . . . . . . . . . . . . . 1-21 roaming during private call . . . . . . . . . . . 9-50
radio user object . . . . . . . . . . . . . . . . 9-8 router
radios . . . . . . . . . . . . . . . . . . . . . 4-92 ATR. . . . . . . . . . . . 4-55, 7-10, 7-17, 12-5
ASTRO Spectra . . . . . . . . . . . . . . . 4-95 audio switch interface function . . . . . . . . 4-16
ASTRO Spectra Plus . . . . . . . . . . . . . 4-95 border router. . . . . . . . . . . . . . . . . 4-18
call types . . . . . . . . . . . . . . . . . . 4-93 control function . . . . . . . . . . . . . . . 4-16
portable radio features . . . . . . . . . . . . 4-93 core and exit router. . . . . . . . . . . . . . 4-16
scan features . . . . . . . . . . . . . . . . . 4-93 core router. . . . . . . . . . . . . . . . . . 4-16
signaling types . . . . . . . . . . . . . . . . 4-93 data function. . . . . . . . . . . . . . . . . 4-15
subscriber radio overview. . . . . . . . . . . 4-94 exit router . . . . . . . . . . . . . . . . . . 4-16
RCM Reports gateway router . . . . . . . . . . . . . . . . 4-14
application overview . . . . . . . . . . . . 13-43 ggsn. . . . . . . . . . . . . . . . . . . . . 4-17
as a purchasable option . . . . . . . . . . . 13-43 MGEG function . . . . . . . . . . . . . . . 4-15
Current Login Sessions report. . . . . . . . 13-44 network management function . . . . . . . . 4-16
Emergency Alarms Report . . . . . . . . . 13-45 overview . . . . . . . . . . . . . . . . . . 4-12
features . . . . . . . . . . . . . . . . . . 13-44 peripheral router . . . . . . . . . . . . . . . 4-18
Radio Command Reports . . . . . . . . . . 13-45 prime site . . . . . . . . . . . . . . . . . . 2-15
tasks . . . . . . . . . . . . . . . . . . . 13-44 remote site. . . . . . . . . . . . . . . . . . 2-13
site routers. . . . . . . . . . . . . . . . . . 4-13
Router Manager . . . . . . . . . . . . . . . 13-46
6881009Y05-O April 2004 IX-9

Index
Router Manager (contd.) Router Manager (contd.)

features . . . . . . . . . . . . . . . . . . 13-48 tasks . . . . . . . . . . . . . . . . . . . 13-48
security management . . . . . . . . . . . . . 12-11 simulcast subsystem

security partitioning . . . . . . . . . . . . . 12-11 configuration overview . . . . . . . . . . . . 5-68
server configuration using CSS . . . . . . . . . . . 5-69
alias database manager . . . . . . . . . . . . 7-18 essential remote site . . . . . . . . . . . . . 5-69
console database manager . . . . . . . . . . 7-18 mutual aid . . . . . . . . . . . . . . . . . . 6-21
failure . . . . . . . . . . . . . . . . . . . . 7-20 software download manager . . . . . . . . . 5-70
FillVision INM . . . . . . . . . . . . . . . 7-10 single transmitter receiver voting subsystem . . 2-17,
FullVision INM . . . . . . . . . . . . . . . 7-17 5-72
interaction . . . . . . . . . . . . . . . . . . 7-18 data capability characteristics . . . . . . . . . 5-72
PRNM system . . . . . . . . . . . . . . . . 12-5 operating modes . . . . . . . . . . . . . . . 5-73
PRNM system-level . . . . . . . . . . . . . 4-51 prime site . . . . . . . . . . . . . . . . . . 5-73
server descriptions . . . . . . . . . . . . . . 7-15 colocated transmit remote site . . . . . . . 5-74
system statistics server receive only remote site . . . . . . . . . . 5-74
local . . . . . . . . . . . . . . . . . . . 7-16 site controller . . . . . . . . . . . . . . . 5-74
ucs server descriptions receive only remote site
local . . . . . . . . . . . . . . . . . . . 7-16 ASTRO-TAC receiver . . . . . . . . . . . 5-79
zone database . . . . . . . . . . . . . . . . 7-16 map to transmit site . . . . . . . . . . . . 5-80
zone level . . . . . . . . . . . . . . . . . . 12-5 QUANTAR base station . . . . . . . . . . 5-77
zone statistics . . . . . . . . . . . . . . . . 7-17 QUANTAR Satellite Receiver . . . . . . . 5-78
servers. . . . . . . . . . . . . . . . . . . . . 7-1 software download. . . . . . . . . . . . . 5-79
network management system . . . . . . . . . 12-5 transmit remote site
system level . . . . . . . . . . . . . . . . . 12-6 QUANTAR base station . . . . . . . . . . 5-76
service site controller . . . . . . . . . . . . . . . 5-76
availability site router . . . . . . . . . . . . . . . . . . . 5-29
interzone group . . . . . . . . . . . . . . 9-66 site trunking . . . . . . . . . . . . . . . . . 11-20
interzone individual . . . . . . . . . . . . 9-67 Software Download Manager
loss . . . . . . . . . . . . . . . . . . . . . 9-63 features . . . . . . . . . . . . . . . . . . 13-52
loss between zones . . . . . . . . . . . . . . 9-64 overview . . . . . . . . . . . . . . . . . 13-52
loss within zone . . . . . . . . . . . . . . . 9-64 tasks . . . . . . . . . . . . . . . . . . . 13-52
services source site ACC object . . . . . . . . . . . . . 9-14
core . . . . . . . . . . . . . . . . . . . . . 12-7 star topology . . . . . . . . . . . . . . . . . . 3-2
emergency. . . . . . . . . . . . . . . . . . 9-44 start menu
group-based . . . . . . . . . . . . . . . . . 9-32 opening applications . . . . . . . . . . . . 13-14
individual call . . . . . . . . . . . . . . . . 9-46 states
shared Ethernet. . . . . . . . . . . . . . . . . 3-2 zone controller . . . . . . . . . . . . . . . . 9-77
simple network management protocol . . . . . . 3-8 static routing . . . . . . . . . . . . . . . . . . 3-9
simplex . . . . . . . . . . . . . . . . . . . . 1-5 static user configuration
simulcast prime site. . . . . . . . . . . . . . . 5-36 call processing . . . . . . . . . . . . . . . . 9-2
MTC 9600 simulcast site controller . . . . . . 5-43 statistical data . . . . . . . . . . . . . . . . . 7-6
simulcast remote site . . . . . . . . . . . . . . 5-58 Status Events. . . . . . . . . . . . . . . . . 13-42
channel bank . . . . . . . . . . . . . . . . 5-67 Status feature description . . . . . . . . . . . 13-42
LAN switch . . . . . . . . . . . . . . . . . 5-67 STR 3000 . . . . . . . . . . . . . . . . . . . 5-60
QUANTAR base station . . . . . . . . . . . 5-65 subscriber . . . . . . . . . . . . . . . . . . . 7-2
remote site router . . . . . . . . . . . . . . 5-66 information flow . . . . . . . . . . . . . . . 7-3
simulcast base station . . . . . . . . . . . . 5-63 Subscriber Information Flow . . . . . . . . . 7-3
STR 3000 base radio . . . . . . . . . . . . . 5-60
IX-10 6881009Y05-O April 2004

subscribers . . . . . . . . . . . . . . . . . . . 1-13 system (contd.)

switched Ethernet . . . . . . . . . . . . . . . 3-2 major components . . . . . . . . . . . . . . 1-34
switching multiple zone . . . . . . . . . . . . . . . . 1-37
to standby controller system databases . . . . . . . . . . . . . . . . 7-7
user initiated . . . . . . . . . . . . . . . 9-76 system interaction . . . . . . . . . . . . . . . 4-61
switchover . . . . . . . . . . . . . . . . . . . 9-72 system object . . . . . . . . . . . . . . . . . 9-12
automatic . . . . . . . . . . . . . . . . . . 9-70 system operation . . . . . . . . . . . . . . . . 1-16
system . . . . . . . . . . . . . . . . . . . 9-73 System Profile
user-initiated. . . . . . . . . . . . . . . . . 9-73 features . . . . . . . . . . . . . . . . . . 13-54
zone controller . . . . . . . . . . . . . . . . 9-69 overview . . . . . . . . . . . . . . . . . 13-54
Synchronous card and Transition card . . . . . . 4-8 tasks . . . . . . . . . . . . . . . . . . . 13-54
synchronous communications . . . . . . . . . . 3-9 system servers
system hierarchical view. . . . . . . . . . . . . . . 7-14
air traffic information subsystem view . . . . . . . . . . . . . . . 7-14
packets . . . . . . . . . . . . . . . . . . 12-9 summary . . . . . . . . . . . . . . . . . . 7-13
data . . . . . . . . . . . . . . . . . . . . . 7-2 system statistics server . . . . . . . . . . . . . 4-53
data requirements . . . . . . . . . . . . . . 7-1 menu . . . . . . . . . . . . . . . . . . . . 7-25
enhancements . . . . . . . . . . . . . . . . 1-21 system statistics server (SSS) . . . . . . . . . . 7-7
framework. . . . . . . . . . . . . . . . . . 12-1 system-level servers . . . . . . . . . . . . . . 12-6
historical reports . . . . . . . . . . . . . . 12-10
T1 carrier . . . . . . . . . . . . . . . . . . . 3-10 transport core . . . . . . . . . . . . . . . . . 2-6

talkgroup . . . . . . . . . . . . . . . . . . . 1-22 transport methods and protocols . . . . . . . . . 3-5
call . . . . . . . . . . . . . . . . . . . . . 9-33 transport network. . . . . . . . . . . . . . . . 4-11
interzone call . . . . . . . . . . . . . . . . 9-38 Digital Access Cross-connect Switch
intrazone call . . . . . . . . . . . . . . . . 9-33 (DACS) . . . . . . . . . . . . . . . . . . . 4-37
talkgroup object . . . . . . . . . . . . . . . . 9-10 Ethernet LAN switch . . . . . . . . . . . . . 4-18
tape drive . . . . . . . . . . . . . . . . . . . 4-10 exit routers . . . . . . . . . . . . . . . . . 4-16
TCP/IP protocols . . . . . . . . . . . . . . . . 3-9 gateway routers . . . . . . . . . . . . . . . 4-14
teardown. . . . . . . . . . . . . . . . . . . . 9-49 master site LAN/WAN . . . . . . . . . . . . 4-11
telephone interconnect . . . . . . . 1-21, 4-83, 9-50 out-of-band management . . . . . . . . . . . 4-58
Adjunct Control Signaling Server (ACSS) . . . 4-84 WAN switch . . . . . . . . . . . . . . . . . 4-23
Avaya PBX . . . . . . . . . . . . . . . . . 4-85 WAN switch interface panel . . . . . . . 4-31, 4-2
call continuation . . . . . . . . . . . . . . . 9-58 transport network management (TNM). . . . . . 4-47
call roaming . . . . . . . . . . . . . . . . . 9-59 applications . . . . . . . . . . . . . . . . . 13-5
components . . . . . . . . . . . . . . . . . 9-51 trunked system . . . . . . . . . . . . . . 1-11, 1-17
configuration . . . . . . . . . . . . . . . . 9-52 multiple site . . . . . . . . . . . . . . . . . 1-31
definition . . . . . . . . . . . . . . . . . . 9-51 components . . . . . . . . . . . . . . . . 1-34
DTI-1000 subsystem . . . . . . . . . . . . . 4-83 SmartZone . . . . . . . . . . . . . . . . 1-33
subsystem . . . . . . . . . . . . . . . . . . 2-17 operation . . . . . . . . . . . . . . . . . . 1-18
templates . . . . . . . . . . . . . . . . . . . 9-9 single site . . . . . . . . . . . . . . . . . . 1-12
tracking location . . . . . . . . . . . . . . . . 9-25 trunking
Traffic Planes . . . . . . . . . . . . . . . . . 2-5 and radio systems . . . . . . . . . . . . . . 1-11
audio plane . . . . . . . . . . . . . . . . . 2-6 interzone . . . . . . . . . . . . . . . . . . 9-65
network management plane . . . . . . . . . . 2-6 Motorola systems . . . . . . . . . . . . . . 1-11
voice control plane . . . . . . . . . . . . . . 2-6 other bands . . . . . . . . . . . . . . . . . 2-20
TRAK 9100 . . . . . . . . . . . . . . . 4-56, 5-57 site . . . . . . . . . . . . . . . . . . . . 11-20
transmission control protocol (TCP) . . . . . . . 3-9 technology. . . . . . . . . . . . . . . . . . 1-11
6881009Y05-O April 2004 IX-11

Index
UDP. . . . . . . . . . . . . . . . . . . . . . 3-9 user configuration

unit-to-unit call processing . . . . . . . . . . . . . . . . 9-2
call busies . . . . . . . . . . . . . . . . . . 9-62 user configuration manager (UCM)
call requests . . . . . . . . . . . . . . . . . 9-46 features . . . . . . . . . . . . . . . . . . 13-56
user overview . . . . . . . . . . . . . . . . . 13-55
configuration server tasks . . . . . . . . . . . . . . . . . . . 13-56
menu . . . . . . . . . . . . . . . . . . . 7-24 user configuration server . . . . . . . . . . 4-52, 7-8
menu . . . . . . . . . . . . . . . . . . . . 7-24
user datagram protocol . . . . . . . . . . . . . 3-9
V.35 interface . . . . . . . . . . . . . . . . . 3-12 voice

virtual circuits . . . . . . . . . . . . . . . . . 3-7 security
virtual LANs . . . . . . . . . . . . . . . . . . 3-11 encryption. . . . . . . . . . . . . . . . . 1-21
visitor location register (VLR). . . . . 7-4, 7-8, 9-23 voice channel . . . . . . . . . . . . . . . . . 1-16
packet data gateway . . . . . . . . . . . . . 7-5 voice control plane . . . . . . . . . . . . . . . 2-6
WAN switch . . . . . . . . . . . . . . . . 2-6, 4-23 wide area network (WAN) (contd.)

wide area network (WAN) . . . . . . . . . . . 3-4 path diversity . . . . . . . . . . . . . . . . 3-8
10Base-2 . . . . . . . . . . . . . . . . . . 3-6 simple network management protocol . . . . . 3-8
10Base-T . . . . . . . . . . . . . . . . . . 3-5 static routing. . . . . . . . . . . . . . . . . 3-9
asynchronous transfer mode . . . . . . . . . 3-4 synchronous communications . . . . . . . . . 3-9
balanced line interface . . . . . . . . . . . . 3-6 T1 carrier . . . . . . . . . . . . . . . . . . 3-10
fiber-optic cable . . . . . . . . . . . . . . . 3-6 TCP/IP protocols. . . . . . . . . . . . . . . 3-9
frame relay . . . . . . . . . . . . . . . . . 3-6 transport methods and protocols. . . . . . . . 3-5
master site, transport network . . . . . . . . . 4-11 V.35 interface . . . . . . . . . . . . . . . . 3-12
OSPF . . . . . . . . . . . . . . . . . . . . 3-8 virtual LANs . . . . . . . . . . . . . . . . 3-11
ZAMBI board . . . . . . . . . . . . . . . . . 4-75 zone controller . . . . . . . . . . . . . . . . . 4-2

zone . . . . . . . . . . . . . . . . . . . . . . 1-35 call processing behavior during recovery. . . . 9-75
controlling. . . . . . . . . . . . . . . . . . 1-40 states . . . . . . . . . . . . . . . . . . . . 9-77
home . . . . . . . . . . . . . . . . . . . . 9-7 switchover. . . . . . . . . . . . . . . . . . 9-69
loss of service . . . . . . . . . . . . . . . . 9-64 zone database . . . . . . . . . . . . . . . . . 7-8
loss of service in zone . . . . . . . . . . . . 9-64 zone database server . . . . . . . . . . . 4-54, 7-16
participating . . . . . . . . . . . . . . . . . 1-40 menu . . . . . . . . . . . . . . . . . . . . 7-26
Zone Configuration Manager (ZCM) zone historical reports
features . . . . . . . . . . . . . . . . . . 13-58 application. . . . . . . . . . . . . . . . . 12-10
interaction with CSS . . . . . . . . . . . . 13-59 zone infrastructure database . . . . . . . . . . . 7-8
overview . . . . . . . . . . . . . . . . . 13-57 zone local database . . . . . . . . . . . . . . . 7-9
tasks . . . . . . . . . . . . . . . . . . . 13-58 Zone Profile
IX-12 6881009Y05-O April 2004

Zone Profile (contd.) zone-level servers . . . . . . . . . . . . 4-53, 12-5

features . . . . . . . . . . . . . . . . . . 13-60 ZoneWatch. . . . . . . . . . . . . . . . . . 12-10
overview . . . . . . . . . . . . . . . . . 13-60 features . . . . . . . . . . . . . . . . . . 13-63
tasks . . . . . . . . . . . . . . . . . . . 13-60 overview . . . . . . . . . . . . . . . . . 13-61
zone statistics server . . . . . . . . . . . 4-55, 7-17 tasks . . . . . . . . . . . . . . . . . . . 13-62
database . . . . . . . . . . . . . . . . . . . 7-9
menu . . . . . . . . . . . . . . . . . . . . 7-27
6881009Y05-O April 2004 IX-13

Index
IX-14 6881009Y05-O April 2004

Glossary
Glossary
700 MHz STR 3000 ASTRO 25 Site Repeater The 700 MHz STR 3000 ASTRO 25
Site Repeater enables you to add extra channels to 800 MHz QUANTAR ASTRO 25 Repeater
sites by using additional frequencies in the 700 MHz band. It also supports mutual aid. The 700
MHz STR 3000 Simulcast base radio operates in the 700 MHz digital band. It can be deployed
as an ASTRO 25 Repeater, Simulcast base radio, and conventional mutual aid base radio.
ACC See Adjacent Control Channel (ACC)
Access Code Index (ACI) A digital code that is part of the Network Access Code
(NAC). The ACI ensures that a radio communicates with the proper site and not one of
its co-channel neighbors. See Dynamic Network Access Code (DNAC).
ACI See Access Code Index
ACK See Acknowledgment (ACK)
Acknowledgment (ACK) A positive response to an event. For example, the Radio
Control Manager sends an ACK to notify radio users that an event was received.
Address Resolution Protocol (ARP) Conversion of a network layer address into a
corresponding physical address, as with resolving an IP address. A protocol defining the
rules for mapping an IP address to a physical machine address that is recognized in the local
network. The MAC Address is equal to 48 bits; the IPV4 is equal to 32 bits.
Adjacent Control Channel (ACC) Allows a radio to learn about the control channel
frequencies and current availability status of sites programmed in the User Configuration
Manager (UCM) as adjacent sites for the specific radios site. The radio then uses this
information to rank potential control channel candidates; based on the ranking, the
radio selects a control channel to use to communicate within the ASTRO 25 system if
the current sites control channel becomes too weak for acceptable use.
Adjacent Channel Radio frequencies that are immediately next to,
but not overlapping, one another.
ADM See Alias Database Manager (ADM)
AEB See Ambassador Electronics Bank (AEB)
AEI See Audio Expansion Interface (AEI)
Affiliated Zone The zone to which a radio is currently affiliated.
Affiliation The process by which a radio sends its talkgroup information to
the zone controller. The radio registers to a site, sending talkgroup information to
the zone controller, and affiliates with a talkgroup.
Affiliation Display A Private Radio Network Management (PRNM) Suite application.
This application monitors how radio users travel between different sites in a zone and how
they communicate with other members of their assigned talkgroup. It also monitors how radio
users communicate with members outside of their talkgroup within a particular zone.
Affiliation Group The talkgroup to which a radio is currently affiliated.
6881009Y05-O April 2004 GL-1

Glossary
Agent A software application that runs at each node of the network. This application
collects network and terminal information for devices specified in the Management
Information Base (MIB). See Management Information Base (MIB).
AIMI See Ambassador Interface Mux Interface (AIMI)
Air Traffic Information Access (ATIA) Data packets that contain talkgroup and
site affiliation and deaffiliation information for each radio user in a particular zone. The
Air Traffic Router (ATR) collects this radio traffic information from the zone controller
and broadcasts an information stream of these packets on the network.
Air Traffic Router (ATR) A server that collects and distributes radio system usage data
for a specific zone. Each zone is required to have one ATR server installed.
Alias An alphanumeric name used to identify a radio, talkgroup, or
multigroup rather than using an ID number. Aliases can be assigned to represent
something more meaningful to the users.
Alias Database Manager (ADM) A software tool for managing the alias database,
which stores all radio, console, talkgroup, and multigroup aliases used in the system.
Algorithm See encryption algorithm.
AllStart A talkgroup setting that controls how a call grant is handled. When AllStart
is selected, resources for all affiliated members must be available before the system
grants the call. For additional call grant information, see FASTStart.
AMB See Ambassador Board (AMB)
Ambassador Board (AMB) A circuit board in the Ambassador Electronics Bank (AEB)
that interfaces Central Electronics Banks (CEBs) or mutual aid resources to the AEB.
Ambassador Electronics Bank (AEB) The audio switch used to route
audio to the console and to the Telephone Interconnect Device (TID). Each zone
contains one AEB. See also Embassy Switch.
Ambassador Interface Mux Interface (AIMI) The Central Electronics Bank (CEB)
interface board used to interface with an Embassy Audio Switch using a T1/E1 line.
Anchor Zone The zone in which the telephone interconnect device is connected to the
Public Switched Telephone Network (PSTN) for the duration of a telephone interconnect call.
APCO Project 25 (P-25) Created by the Association of Public Safety
Communications Officials (APCO). Project 25 brings together representatives of federal,
state and local government agencies. These agencies and other user organizations
evaluate basic technologies in advanced land mobile radio to find solutions that
best serve the needs of the public safety marketplace.
APN Access Point Node
Application Launcher A Private Radio Network Management (PRNM) Suite application
used to open other management applications from a workstation within one of the zones.
ARP See Address Resolution Protocol
Assigning Zone The zone that assigns a radio request.
ASTRO 25 Repeater A type of base station. For more information see
700 MHz STR 3000 ASTRO 25 Site Repeater.
ASTRO-TAC 9600 Comparator The ASTRO-TAC 9600 comparator features the
Frame Diversity Reception voting methodology. As the comparator receives the various
signals, it looks at each of the data frames and compares the bit error rate (BER) and error
GL-2 6881009Y05-O April 2004

correction coding (ECC). The comparator then selects the data frame or signal with the lowest
BER and ECC and resends it. By using the best pieces (data frames) of each input signal, the
result is often a better output signal than any one signal being received at the comparator.
ATIA See Air Traffic Information Access (ATIA)
Attached RCM A Radio Control Manager (RCM) user who has a radios primary
talkgroup configured as an Attachment Group in the users parameters.
Attachment Group Allows Radio Control Manager (RCM) operations to be performed
on a talkgroup by a particular RCM user. RCM users monitor traffic only on their
attached talkgroups and communicate with their attached talkgroups and the zones in the
system. An attachment list determines how radio events are distributed.
Attachment List List of talkgroups attached to a particular Radio Control
Manager (RCM) user. Each RCM user monitors traffic only on attached talkgroups
and communicates with their attached talkgroups.
Audio Expansion Interface (AEI) A Central Electronics Bank (CEB) interface board
that provides two 4wire audio outputs to the speakers on a console operator position.
Audio Rendezvous Point A voice resource that resides on a core router that is
assigned and managed by the controlling zone controller for the call.
Auto-KLK Auto-KLK is a configurable parameter which turns this feature on and
off system-wide, as well as per unit. See also Key Loss Key Rekeying.
Autonomous Access Autonomous Access for data services occurs when
a Packet Data Channel (PDCH) is already set up and available for a site and the
subscriber radio has automatic access to the PDCH.
Base Station Identification (BSI) The assigned station identification callsign
issued for the system by the local licensing authority. In the U.S., this is the FCC for
non-federal government customers, and the NTIA for government customers.
Base Station Interface Module (BIM) An interface card between a base
station and the Central Electronics Bank (CEB). Each base station connects to
one card. Applies to conventional systems only.
CAI See Common Air Interface (CAI)
Call Continuation The capability of passing active calls across site or zone boundaries.
Also called Call Handoff, Call Coordination, or Call Reconnect.
Cancel Inhibit A Radio Control Manager (RCM) radio command that cancels
a Selective Inhibit command and reactivates radios that were prevented from
using the system with a Selective Inhibit command.
Cancel Lock A Radio Control Manager (RCM) radio command that cancels the last
Selector Lock command for a selected radio, unlocking the radios selector.
Cancel Regroup A Radio Control Manager (RCM) radio command that cancels the
last Regroup command for selected radios and removes the radios from the regrouped
talkgroup, allowing the radios to return to their original talkgroups.
Cancel Regroup and Lock A Radio Control Manager (RCM) radio command
that allows an RCM user to send a Cancel Regroup command and then a Cancel Lock
command for all selected radios. See also Cancel Regroup and Cancel Lock.
CCW See Channel Control Window (CCW)
CDM See Console Database Manager (CDM)
6881009Y05-O April 2004 GL-3

Glossary
CDM/ADM Server A network server running the Console Database Manager

(CDM) and Alias Database Manager (ADM) applications.
CEB See Central Electronics Bank (CEB)
CENTRACOM Elite Admin An application that creates objects on the
CENTRACOM Elite console operator position desktops.
CENTRACOM Gold Series Elite Console A Motorola product line of
console dispatch equipment, includes a workstation and Console Interface Electronics
(CIE) for an RF interface and audio capability.
Central Electronics Bank (CEB) An equipment enclosure that houses the
interfaces between consoles and logging recorders and the AEB. It contains AIMI
and COIMs that route audio between consoles and the AEB.
ChangeMe Request A Radio Control Manager (RCM) event sent by a radio
user asking the RCM user to send a Cancel Lock command to unlock the selector on
the radio, whose selector lock has been locked as part of a Selector Lock command
and who wants to regain control of talkgroup selection so the radio user can change
talkgroups. This is useful when the radio has been regrouped to an affiliated
talkgroup and wants to return to their primary talkgroup.
Channel Bank The network infrastructure element that multiplexes channel
data from a site or subsystem onto the T1/E1 line for transport. The channel bank
allows the system to combine different types of equipment or subsites onto a
common T1/E1 line for transport between sites.
Channel Control Window (CCW) The display seen by a console operator when using a
CENTRACOM Gold Series Elite console operator position. Each CCW corresponds to a
specific talkgroup, multigroup, or range of frequencies that are monitored by the console.
Channel Service Unit (CSU) Device used to terminate a DS-1 or
DS-0 [56/64 kb/s] digital circuit. The CSU also performs line-conditioning,
protection, loop-back and timing functions.
CiscoView Device Manager A Web interface provided with CiscoWorks 2000
that provides real-time views of networked Enterprise LAN Switch Systems devices.
This application is not included with an ASTRO 25 SE system.
CiscoWorks 2000 A network management application that includes CiscoView
Device Manager and Resource Manager Essentials (RME). CiscoWorks 2000 is used to
manage the Cisco Catalyst 6509 Ethernet switch. The CiscoWorks applications reside on
the Ethernet Switch Management Server (ESMS) and work together as a LAN management
solution. This application is not included with an ASTRO 25 SE system.
CKEK See Common Key Encryption Key (CKEK)
CKR See Common Key Reference (CKR)
Class of Objects A group of objects that represents a hierarchy of class objects.
Clear Calls Non-secure, non-encrypted calls. These are not protected from
eavesdropping by unauthorized persons. See also Encrypted Calls
Cloning A way to duplicate a radio record by saving it with a different
name, but retaining common parameters. Cloning enables you to program
common parameters into additional radios.
Co-Channel A channel that is on the same frequency as another channel.
Codeplug A memory chip inside a device that contains various programmable
parameters, including frequencies, time-out-timer, and so on.
GL-4 6881009Y05-O April 2004

COIM See Console Operator Interface Module (COIM)

Command Radio Control Manager (RCM) outbound functions, such as Selective
Inhibit, Regroup, Selector Lock, and the commands to cancel each of these. An
RCM user can send a command to one or more radios in the system. Each radio
is considered an individual task of a command.
Command Monitor This pane in the Radio Control Manager (RCM) main window
allows you to view the progress of all commands that you have submitted to the system.
Common Air Interface An Association of Public Safety Communications Officials
(APCO) standard governing the transmission of digital information.
Common Key Encryption Key (CKEK) The CKEK is a Key Encryption Key
(KEK) assigned to a group of units for encrypting keys within a group-delivered
over-the-air-rekeying (OTAR) command.
Common Key Reference (CKR) All secure devices use CKRs to indicate a storage
location for encryption keys. Calls are initiated using keys stored in a given CKR ID.
Comparator This device performs voting and routing functions in a Simulcast
subsystem or Voting subsystem. The comparator collects all of the data for a single
channel from all of the sites. It then chooses the best signal or frame from all of
the received signals or frames and sends a single output representing all physical
receivers for that channel. See ASTRO-TAC 9600 Comparator.
Configuration/Service Software (CSS) The software application
used to configure, maintain, and troubleshoot individual devices in a radio
system, such as a Simulcast site controller.
Console An operator position that allows console operators and administration users
to interact with the system and communicate with radio users.
Console Database Manager (CDM) A software tool that enables you
to create and maintain the console database, which stores all programmed
features and parameters for the console.
Console Operator Interface Module (COIM) A circuit card located in the
Central Electronics Bank that provides an interface to the CENTRACOM Gold Series
console. One COIM is required for each console operator position.
Context Activation The process by which data call registration and service activation
is implemented by the ASTRO 25 IV&D communication system.
Context Deactivation Context deactivation occurs when resource
allocation timers, data service timers, or data service configuration parameters
dictate that a data call is to be deactivated.
Control Channel A dedicated channel at a site on which radios send
and receive instructions for call processing.
Controlling Zone (CZ) The zone that coordinates the resources for a call. For
group calls, the designated Home Zone of the group is always the Controlling Zone
for the call, regardless of where group members are affiliated. For individual calls,
the Controlling Zone is the zone from which the voice service is being requested.
The affiliated zone of the subscriber requesting the call.
Controlling Zone Controller (CZC) The zone controller that controls
a call throughout its duration.
6881009Y05-O April 2004 GL-5

Glossary
Core Security Management Server (CSMS) The CSMS consists of hardware

and software components required to ensure that only authorized users access the radio
network system. The CSMS is required to safely enable use of system interfaces for
remote service access and remote network management service activities.
Crypto Period The length of time in which an encryption key is in use in system devices.
CSMS See Core Security Management Server (CSMS)
CSS See Configuration/Service Software (CSS)
CSU See Channel Service Unit (CSU)
Current Subscriber A secure subscriber is considered current when its internal
state and configuration is known to match the state and configuration defined in
the KMF database for that specific subscriber.
CZC See Controlling Zone Controller (CZC)
DACS See Digital Access Cross-connect Switch
Data Service Unit (DSU) Device used to interface to a digital circuit. Provides
termination of a data circuit and is typically combined with a Channel Service Unit (CSU).
Performs conversion of customers data stream to bipolar format for transmission.
Deaffiliation The process by which a radio is deassociated from a talkgroup when
it powers down, or when the radio is changing talkgroups or sites.
Default Record A record that contains basic parameters to define privileges during
system initialization and to define privileges for default access to the system. You can
use this record to create new records with the same privileges.
Demilitarized Zone (DMZ) Ethernet Switch In an ASTRO 25 system, the DMZ
(demilitarized zone) is an Ethernet switch used as a neutral area between the Customer
Enterprise Network (CEN) and the radio network infrastructure. The DMZ Ethernet switch
connects to the peripheral network router, firewall, and intrusion detection sensor server
(IDSS) server on the radio network infrastructure side, and to border routers on the CEN side.
Deregistration The process by which a radio deassociates from one site and registers to
another site, powers down, or is out of range of a system for a designated period of time.
Diagnostics Through the Zone Configuration Manager (ZCM), you can send
a Diagnostic message to a device on the system that causes it to change state. The
resulting change in state can be viewed from FullVision INM.
DID See Direct Inbound Dialing (DID)
Digital Access Cross-connect Switch (DACS) A data concentrator
and organizer for T1/E1-based systems.
Digital Interface Unit (DIU) A transcoding device used to convert digital
signals to analog signals (and vice versa) between console positions and other
components of the system. The DIU can also provide encryption and decryption
services to the console or telephone interconnect devices.
Direct Inbound Dialing (DID) A select number of digits that are associated with
a specific radio user that allows a landline caller to reach the user directly. The private
branch exchange (PBX) forwards the dialed digits to the zone controller.
DIU See Digital Interface Unit (DIU)
DMZ See Demilitarized Zone (DMZ) Ethernet Switch
DS0 A single time slot of information in a Tl/El system. A time slot is equal to 64 Kbps.
GL-6 6881009Y05-O April 2004

DSU See Data Service Unit (DSU)

Dynamic Frequency Blocking (DFB) Prevents a channel from interfering with another
channel. When a channel is in use, any channels listed as interfering with that channel are made
unavailable (blocked). DFB is available with IntelliRepeater and Simulcast Subsystems.
Dynamic Network Access Code (DNAC) A code generated by base radios that
contains the System ID and the ACI. This code ensures that radios or base stations transmit and
receive DNAC signals that are different between each site and system. Using different DNACs
allows a radio or base station to ignore signals from distant sites or from other systems.
Dynamic Regrouping A Radio Control Manager (RCM) purchasable option that allows
you to change the talkgroup assignment of any radio to handle unique problems or situations
more efficiently. The radios receive reprogramming of certain parameters using signaling over
the control channel. The following RCM features are linked to Dynamic Regroup: Regroup
commands, Selector Lock commands, ChangeMe Requests, and Storm Plans.
E&M Voice Card A channel bank card that uses 2 or 4wire to convert outgoing
analog voice to digital and manages the flow of voice traffic over the network.
E1 High-capacity transmission system (2.048 mbps) used for voice and data primarily
in Europe. An E1 is equal to 32 DS0, which is 2.048 Mbps.
Elite Operator Position See CENTRACOM Gold Series Elite Console
Embassy Switch An Ambassador Electronics Bank (AEB) and Central
Electronics Bank (CEB) multiplexing subsystem that expands the connectivity
of console operator positions and RF resources.
Emergency Alarm Text A short message associated with a radio that sends an
Emergency Alarm. The text is added in the User Configuration Manager (UCM).
Emergency Alarms A Radio Control Manager (RCM) event type that is
normally sent in an emergency situation or when the radio user needs assistance.
When a radio user presses the emergency alarm button, an Emergency Alarm event
appears in the RCM, and an audible alarm sounds.
Emergency Call The highest priority call type in a system. There are extended
time-out periods set for this type of call and special notifications of the emergency
identities for the CENTRACOM Elite Consoles.
Enable A Motorola proprietary over-the-air-rekeying (OTAR) command that
reactivates a radio after it has been set to Inhibited.
Encryption Algorithm A defined series of calculations used to perform encryption.
Encrypted Calls Calls that use an encryption algorithm and an encryption
key to prevent unauthorized persons from eavesdropping on the transmitted
message. Encrypted calls must be decrypted using the correct encryption key or
the message will be unintelligible. See also Clear Calls.
Encryption Key A numeric code used in combination with an encryption algorithm,
used to encrypt and decrypt data, voice or over-the-air-rekeying (OTAR) messages.
Encryption Mode The two encryption modes are clear (red) and encrypted
(black). See also Clear Calls and Encrypted Calls.
Ethernet Switch Management Server (ESMS) The CompactPCI
server where the CiscoWorks2000 suite of applications resides. This application
is not included with an ASTRO 25 SE system.
Event An unsolicited inbound message sent from a radio or a solicited command
viewable from the Radio Control Manager (RCM). Also called a Radio Event.
6881009Y05-O April 2004 GL-7

Glossary
Explicit Other Band Trunking The ASTRO 25 system uses two methods for defining
transmit and receive frequencies on a given channel: explicit and implicit. Channels defined as
explicit enable the use of two very different frequencies for transmitting and receiving. When
transmitting on a channel using an explicitly-defined frequency, the site sends the Tx and Rx
frequencies. Trunking systems typically use a standard 800 MHz full range of Tx/Rx pairs of
frequencies. Other band trunking uses frequencies outside of this standard trunking range.
Failsoft A method of communication used if a site or subsystem cannot perform wide area
or site trunking operations. Each channel works like a single-channel, conventional repeater.
Failure Random Holdoff Time (FRHOT) The maximum amount of time that
radios are told to wait when a site fails before registering to a new site.
FASTStart A feature that allows a talkgroup call to start as long as resources programmed
as critical are available. Non-critical resources are added to a call in progress as they become
available. This means that the call is granted as soon as critical resources are available, but
some affiliated members might not receive the call until additional resources become available.
Fault Management A software tool that uses the FullVision INM
application in conjunction with HP Openview to monitor the current state,
diagnostics, and alarm history of the system.
FCAPS An ISO standard for organizing these network management activities:
Fault Management, Configuration Management, Accounting Management,
Performance Management, and Security Management.
Field Replaceable Entity (FRE) An entire assembly (for example, a router) that can
be removed in the field and replaced with a new assembly in the case of a malfunction. An
assembly typically consists of a self-contained chassis and all of the cards within the chassis.
Field Replaceable Unit (FRU) A component (for example, a card) that can be removed
in the field and replaced in the case of a malfunction. A FRU is not customer or field repairable.
Filter A parameter that allows you to set criteria for a selection to limit the
data that appears in a screen or is returned for a report.
Firewall A network security device providing network boundary
enforcement and attack detection features.
Fleetmap A document that lists configuration information for all users
and resources in the system.
FLM Formatted Logical Messaging
FRE See Field Replaceable Entity (FRE)
FRU See Field Replaceable Unit (FRU)
FullVision Integrated Network Manager (INM) An icon-based network
management tool that monitors the system from a system-level view.
FullVision INM Server A network server running the FullVision INM application that
can access fault management information obtained from the Zone Database Server (ZDS).
Global GPRS Support Node (GGSN) Provides general packet radio service (GPRS)
network access to external hosts to communicate with mobile subscribers. The GGSN acts
as a fixed relay point between the external hosts and the mobile subscribers.
GGSN See Global GPRS Support Node (GGSN)
Global Positioning System (GPS) A satellite system that transmits geographical
location and precision time information to radio receivers.
GPRS General Packet Radio Service.
GL-8 6881009Y05-O April 2004

Graphical User Interface (GUI) An icon-based user interface.

Group-Based Service Radio service that includes Talkgroup Calls, Multigroup Calls,
Emergency Calls, Group Regrouping, Emergency Alarm, and Statuses.
Group Call Service Timeout In message trunking, this is the time that an assigned
channel resource remains active and keyed up. Also called hang time.
Group Calls Calls addressed to talkgroups or multigroups.
Group Home Location Register (GHLR) The database that stores
information for talkgroups that are home to that zone.
Group Home Zone The zone to which the group places calls most often.
Group RSI Group-delivered over-the-air-rekeying (OTAR) messages are addressed
to the Group RSI shared by the group of units. Group RSI is provisioned or changed in
units via Unit OTAR Full Updates to each unit in the group. See also RSI.
Group Updates Over-the-air-rekeying (OTAR) messages targeted to groups of
radios (CKR update or Radio Group Update). See also Unit Update.
GUI See Graphical User Interface (GUI)
Hang Time See Group Call Service Timeout
Hexadecimal Refers to the base-16 number system, which consists of 16 unique
symbols using the numbers 0 to 9 and the letters A to F. For example, the decimal
number 15 is represented as F in the hexadecimal numbering system.
High Speed Unit (HSU) Data Card A high-speed card that offers synchronous network
access at speeds of 56k, 64k, or multiples of 56/64k all the way up to T1/E1 speeds. Access
can be directly to a T1 DS0 (or group of DS0s), a resource card, or another HSU port.
Home Location Register (HLR) The database located in each zone that receives a
master copy of individual and talkgroup information from the User Configuration Server
(UCS) for call processing. The HLR also contains mobility information for individuals and
talkgroups on a per zone level. See Group Home Location Register (GHLR) .
Home Zone The zone in which a radio or talkgroup is primarily located. This zone is
designated to be the zone where the radio user and talkgroups are most active. The home zone
is the controlling zone for group calls. See Group Home Zone and Individual Home Zone.
Host Name The name (usually an alias) given to a machine.
HSSI High speed serial interface at 40 mbps.
ICMP Internet Control Message Protocol
IDSS See Intrusion Detection Sensor Server (IDSS)
Implicit Other Band Trunking The ASTRO 25 system uses two methods for defining
transmit and receive frequencies on a given channel: explicit and implicit. When transmitting
on a channel using an implicitly-defined frequency, the site sends only the transmit
frequency, with the receive frequency being a standard calculated offset from the transmit
frequency. Trunking systems typically use a standard 800 MHz full range of frequencies.
Other band trunking uses frequencies outside of this standard trunking range.
Inbound Message Number Period This number indicates the acceptable inbound
message number range that the Key Management Facility (KMF) defined to validate
inbound a Key Management Message (KMM) message number.
Improved Multi-Band Encoder (IMBE) APCO standard vocoding algorithm
used in the conversion of voice from analog to digital.
6881009Y05-O April 2004 GL-9

Glossary
Inbound Event A request made by a radio user and sent to the

Radio Control Manager (RCM).
Inbound Signaling Packet (ISP) A data packet from the radio to the
zone controller that contains identification information for accessing the system,
zone, and one or more specific talkgroups.
Individual-Based Service Services that include Call Alerts, Private Call,
Landline-to-Radio Interconnect Call, and Radio-to-Landline Interconnect Call.
Individual Call A private call or a telephone interconnect call between two units, a
radio and a console, or a radio and a landline. See Individual-Based Service.
Individual Home Location Register (IHLR) The database that stores
information for individual radios that are home to that zone.
Individual Home Zone Each radio in the system has an individual home
zone. This should be the zone that the radio is located in most of the time and is
configured in the User Configuration Manager (UCM).
InfoVista A customizable performance management application that reports and
graphs a wide variety of data from multiple devices, such as routers, the Ethernet LAN
switch, and the WAN switch. InfoVista resides on the Transport Network Performance
Server (TNPS). This application is not included in an ASTRO 25 SE system.
Integrated Voice and Data IV&D) A feature of a Motorola ASTRO 25
trunked communication system providing voice and data communication services
integrated into one trunked communication system. IV&D involves the IP transport
of voice and data over trunked data channels.
IntelliRepeater A base station that uses the QUANTAR platform and contains
additional capability to perform the trunking functions of a remote site controller. At the
site, one IntelliRepeater is designated as the Active Master and acts as the site controller.
(Note: ASTRO 25 SE systems do not contain IntelliRepeaters.)
Interconnect Subsystem The telephone interconnect equipment in the
zone. Telephone interconnect capability allows radio users to access the Public
Switched Telephone Network (PSTN).
International Organization for Standardization (ISO) A network of national
standards institutes from 145 countries working in partnership with international
organizations, governments, industry, business, and consumer representatives.
A bridge between public and private sectors.
Interfering Channel Any RF channel whose frequency interferes with another channel.
Internet Protocol (IP) A protocol used for carrying packets of data
primarily in Ethernet-based systems.
Interzone Refers to call processing that involves more than one zone in the system.
InterZone Control Path A communications path between a zone controller
in one zone and a zone controller in another zone.
InterZone Trunking State when calls are trunked between a pair of zones. The
following must be in place for InterZone Trunking: users in each zone, an active
interzone control path, group home zone maps entered in both zones, and an active
and enabled audio rendezvous point in each zone.
Intrusion Detection Sensor Server (IDSS) The intrusion detection sensor server
(IDSS) is part of the optional network interface barrier (NIB). The IDSS provides intrusion
traffic monitoring of network traffic through the network security firewall, and works with
the firewall to detect anomalies and protect against potential attacks.
GL-10 6881009Y05-O April 2004

IP See Internet Protocol (IP)

ISO See International Organization for Standardization
KEK See Key Encryption Key
Key See Encryption Key
Key Encryption Key A key used to encrypt traffic keys when they
are delivered over the air.
Key ID An ID number associated with a key. This enables the system to use
a key when encrypting or decrypting voice, data, or over-the-air-rekeying (OTAR)
commands, without revealing the actual key variable.
Key Loss Key Rekeying This Motorola proprietary feature enables a KMF
to restore a units UKEK after it has been erased by using the units Key Loss Key
to receive OTAR commands. A proprietary warm-start and proprietary modify
key OTAR command are used to restore the UKEK.
Key Management Message (KMM) A KMM is a series of commands
and responses between a Key Management Facility (KMF) and secure devices,
such as subscribers. The commands and responses carry out the key management
and secure configuration of the devices.
Keyset A keyset is a group of keys that a radio (portable or mobile) and MGEGs use for
the same crypto period. This allows you to manage the keys in the keyset as a single entity.
Key Variable Loader (KVL) A handheld device used to load or erase keys, view or
modify secure configuration parameters of secure devices, and substitute for over-the-air
transport of OTAR messages between the Key Management Facility (KMF) and devices.
KMF See Key Management Facility
KMM See Key Management Message (KMM)
KLK See Key Loss Key Rekeying
KVL See Key Variable Loader (KVL)
LAN See Local Area Network (LAN)
LAN Switch A local area network (LAN) device that forwards packets
(incoming frame data) from one interface out through another interface based on
the OSI models layer 2 frame switch data.
LKEK See Lost Key Encryption Key
Local Area Network (LAN) A privately owned and administered network for data
communications that provides a relatively high bandwidth over a limited geographical
area for communication between the attached devices.
Logging Operator Multiplex Interface (LOMI) A circuit board in the Central
Electronics Bank (CEB) that separates multiple audio sources into single sources, and then
allocates each talkgroup to an assigned Logging Recorder Interface (LORI).
Logging Recorder Interface (LORI) A board in the Central Electronics Bank
(CEB) that connects one Logging Operator Multiplex Interface (LOMI) board and one
Audio Expansion Interface (AEI) or two AEI modules to one external logging recorder. A
logging recorder logs audio transmissions to create a permanent record. The LORI provides
filtering and further reconstruction of audio sources from the LOMI and AEI.
LLC Logical Link Control
6881009Y05-O April 2004 GL-11

Glossary
Lost Key Encryption Key A lost key used to encrypt traffic keys
when they are delivered over the air.
MAC Address Media Access Control Address.
Management and Administration Users One or more persons who are responsible
for day-to-day operation of the system, system performance, and monitoring alarms. For
security purposes, the User Configuration Manager application is used to assign different
levels of system access to the management and administration users.
Management Information Base (MIB) Defines information that can be
obtained in a simple network management protocol (SNMP).
Master Site In an ASTRO 25 system, this site provides communication support
associated with system-level and zone-level call processing and control. Only one
master site exists per zone in an ASTRO 25 Release 6.1 system.
MDM See Preside Multiservice Data Manager (MDM)
MDMWeb A Web interface provided with Preside MDM that allows you
to perform fault management tasks from the web browser. This application
is not included in an ASTRO 25 SE system.
Metallic Service Unit (MSU) Card The MSU card provides the physical access
connections and the switching capability to test active DS1 lines and DS0 channels.
MIB See Management Information Base (MIB)
MNR Motorola Network Router
Mobile Station A mobile radio such as the XTL 5000 Digital Mobile Radio.
Monitored PDR-GGSN Link This link has at least one active mobile context associated
with it. When a monitored link is UP, echo requests are sent from the Packet Data Gateway
(PDR) to the Gateway GPRS Support Node (GGSN) and from the GGSN to the PDR.
MOSCAD Motorola Supervisory Control and Data Acquisition
MSEL See MultiSelect (MSEL)
MSFC Multilayer Switch Feature Card
MSU See Metallic Service Unit (MSU) Card
MTC 9600 Simulcast Site Controller (SSC) The site controller for a Simulcast
subsystem that communicates with the zone controller.
Multigroup Two or more talkgroups that are combined into a permanent
multigroup in trunked systems. Calls to the multigroup reach all members of
the talkgroups that comprise the multigroup.
Multigroup Call A call addressed to all radios of a specific multigroup
and its associated talkgroups.
MultiSelect (MSEL) A console feature that allows the console operator to select
multiple talkgroups and transmit to all of them simultaneously.
Multisite subsystem In the graphical user interface of the Zone Configuration
Manager application, the simulcast subsystems and single transmit receiver voting
subsystems are part of a multi-site subsystem.
Multizone-Level Operation or function that operates across zone boundaries.
NAK Negative Acknowledgement
NAM Network Analysis Module
GL-12 6881009Y05-O April 2004

Network Address Translation (NAT) A functional process used to coordinate the radio
network infrastructure IP plan with IP plans used outside the radio network infrastructure.
Network Interface Barrier (NIB) The set of hardware and software components
providing boundary enforcement and attack detection network security features.
The NIBs safely enable use of the systems defined interfaces for integrated data,
network management, computer-aided dispatch, and billing.
Network Interface Card (NIC) A generic term for a networking interface card used to
connect a device to a network. The NIC is where the physical connection to the network occurs.
Network Time Protocol (NTP) A standard protocol for sharing time of day
information between networked devices, such as the servers in a zone.
Non-Tactical A radio operation that determines how a radio behaves in an emergency
situation. In non-tactical mode (also called revertive mode), the radio reverts to a
preconfigured emergency talkgroup to issue an emergency alarm or call.
Object A data module that encapsulates attributes, properties, and relationships
of software components. Objects can represent a system device (such as a radio)
or device connectivity (such as Interzone Control Path).
Operations Support System (OSS) Servers and applications for managing the
networking backbone within a zone. A system OSS serves the same purpose at a system level.
OSS See Operations Support System (OSS)
Other Band Trunking Trunking systems typically use a standard 800 MHz full
range of frequencies. Other band trunking uses frequencies outside of this standard
trunking range. In this release, a system can have radios and other resources that operate
on another frequency besides 800 MHz. These other frequency ranges are: VHF
(136-174 MHz) and UHF (380-470 MHz and 450-520 MHz).
Outbound Function Initiated by the Radio Control Manager (RCM) user
from the RCM and sent to a target radio.
Outbound Signaling Packet (OSP) A data packet sent from the zone
controller to the radio which contains the channel assignment and service information
for the radio to access a site within the zone.
Over-the-Air-Rekeying (OTAR) ASTRO 25 systems with the OTAR feature
enable you to rekey subscribers at their current physical location by using over-the-air
commands. This means that you do not have to obtain the subscriber and connect
it directly to the Key Variable Loader (KVL) for rekeying.
Packet Data Channel (PDCH) The radio frequency resources used for the IP
transport of data in an ASTRO 25 trunked communication system.
Packet Data Gateway (PDG) The PDG is an optional device which supports packet
data services for the radio system. The PDG includes cards which provide an interface
between the ASTRO 25 infrastructure and a packet data host network.
Packet Data Router (PDR) The PDR manages traffic to the data host network.
Participating Zone This type of zone contains one or more users who are involved
in a call that is controlled by another zone. See Controlling Zone.
Participating Zone Controller A zone controller that is active in a call or busy,
but that does not necessarily have overall control of the call.
Patch A feature performed by a CENTRACOM console where radio groupings
are combined for common communications purposes.
PBX See Private Branch Exchange (PBX)
6881009Y05-O April 2004 GL-13

Glossary
PDCH See Packet Data Channel (PDCH)

PDG See Packet Data Gateway (PDG)
PDR See Packet Data Router (PDR)
Polling Sends what is known as a hello command to each device in the system as
a way to cause subscribers to transmit delayed acknowledgements of group-delivered,
over-the-air-rekeying (OTAR) messages (rather than waiting for the subscribers to
respond on their own with push-to-talk (PTT) commands.
Preside Multiservice Data Manager (MDM) A network management
application from Nortel Networks that manages the Nortel WAN switch. Preside
MDM resides on the WAN Switch Management Server (WSMS). This application
is not included in an ASTRO 25 SE system.
Primary Talkgroup A talkgroup to which a radio is attached by default. This
is the talkgroup that the radio user primarily uses for communication. The primary
talkgroup is assigned in the User Configuration Manager (UCM).
Private Branch Exchange (PBX) A telephone switch that is operated privately within
a confined setting, instead of publicly. Most large offices have a PBX to handle intraoffice
calls and to connect calls to and from the public switched telephone network (PSTN).
Private Branch Exchange (PBX) Switch A telecommunication system
component providing the interface between the public switched telephone network
(PSTN) and the Telephone Interconnect Server.
Private Call Ring The maximum length of time in seconds that the target
radio is given to respond to a private call request.
Private Radio Network Management (PRNM) Suite The Motorola PRNM suite
is a collection of network management applications that are based on the Microsoft
Windows operating system. PRNM provides configuration, monitoring, and diagnostic
functions for the system. Included in this product suite are Zone Watch, User Configuration
Manager, Zone Configuration Manager, Affiliation Display, ATIA Log Viewer, Historical
Reports, Radio Control Manager, and Radio Control Manager Reports.
Profile In the User Configuration Manager (UCM), this object maps a group of
attributes or data common to a number of users who perform a particular function.
Profiles can also act as templates to create new records.
PRNM Suite See Motorola Private Radio Network Management (PRNM) Suite
Public Switched Telephone Network (PSTN) Commercial land-based
telecommunications. Radios in the system require a telephone interconnect
device as the interface to the PSTN.
Push-to-Talk (PTT) The method by which a radio user initiates a call. When
the user presses the PTT switch on a radio (also known as keying up), the radio
sends data to the zone controller to request call services.
Push-to-Talk (PTT) ID An 8-digit alphanumeric ID sent to the zone controller
to identify the radio and its permissions on the system.
PVC Permanent virtual circuit
Radio An individual portable or mobile two-way radio unit.
Radio Check A Radio Control Manager (RCM) command that checks the affiliation
status of the radio in order to obtain current information, including the talkgroup, site, and
zone of the radio. The Radio Check feature operates over the air and across zone boundaries.
GL-14 6881009Y05-O April 2004

Radio Command An outbound function initiated by a Radio Control Manager

(RCM) user. Radio commands affect the behavior of or request information from the
target radios and can control the behavior of radios anywhere in the system.
Radio Control Manager (RCM) A management application used to issue commands
to radios and monitor events from radios. The Radio Control Manager (RCM) is part
of the Motorola Private Radio Network Management (PRNM) Suite.
Radio Event An unsolicited inbound message sent from a radio or a solicited command
viewable from the Radio Control Manager (RCM). Also called an Event.
Radio Frequency (RF) General term for the range of frequencies that are used in radio
communication systems. RF is electromagnetic energy wavelengths above the audio range
and below visible light. The frequency is typically between 30 kHz and 300 GHz.
Radio ID A unique number that refers to a specific radio on the system.
Radios must have a unique ID in order to communicate with other radios in the
system. The assignable range is from 1 to 16,777,211.
Radio ID Filter Object An object in the User Configuration Manager (UCM) that
filters data based on the radios that a Zone Watch user wants to monitor.
Radio Network Gateway A processing module in the packet data gateway
which provides a logical interface between the packet data router and radio frequency
subsystem within a zone to support data calls to subscriber radios.
Radio Set Identifier (RSI) Each radio needs a unique RSI assigned to it in order
for over-the-air-rekeying (OTAR) messages to be directed to the proper radio.
Radio Serial Number The unique serial number assigned to a specific radio on the
system. This unique serial number is part of the radios programming.
Radio Viewer A window used in the Affiliation Display application to display the current
affiliation and deaffiliation information for an individual radio by ID or alias.
RCM See Radio Control Manager (RCM)
Receiving Zone The zone that receives a radio request. This zone may or
may not become the controlling zone for a call.
Receiving Zone Controller The zone controller that receives a call request.
Recovery Random Holdoff Time (RRHOT) The maximum time that radios are told
to wait when a site recovers, before returning and registering to the recovered site.
Red or Black Mode Keys can be transferred from the Key Variable Loader (KVL)
to a subscriber unit in Black mode only if the subscriber unit already has both the (Key
Encryption Key) KEK and the Traffic Encryption Key (TEK) in common with the Key
Management Facility (KMF). Before the subscriber unit has the KEK and TEK keys, the
KVL must once load keys in Red mode, meaning the keys are delivered unencrypted
from the KVL to the target unit. See also Encryption Mode.
Refresh A command used to update data on a window.
Registration The process by which a radio sends radio site information to the
zone controller when powering up or moving between sites.
Rekey Rekeying is the loading of a key into a subscriber or group of subscribers.
Rekeying is done using either the Key Variable Loader (KVL) or over-the-air-rekeying
(OTAR) via a Rekey command in a Full Update.
Remote Access Server A network access component device typically
providing remote access to a master site.
6881009Y05-O April 2004 GL-15

Glossary
Replication An identical copy of the User Configuration Management (UCM) Database

is stored in each Zone Database Server (ZDS). This is called database replication.
Resource Manager Essentials (RME) A suite of Web-based applications that
manage the LAN switches and the MSFC router cards on the LAN switch.
Requested Access Requested access by a subscriber radio for a PDCH
is necessary when a PDCH is not already set up and available for the site, and
therefore, a request for a PDCH is established.
Requesting Radio A radio requesting service on the system.
Requesting Zone The zone to which a radio sending inbound event information
or requesting a call or service is currently affiliated.
Retry Opportunities This feature guarantees the delivery of an over-the-air-rekeying
(OTAR) command that was not acknowledged by a secure device when it was originally
sent. When a non-current subscriber with OTAR commands pending registers on the system,
the Key Management Facility (KMF) retries sending the pending commands.
RF See Radio Frequency (RF)
Ring Time See Private Call Ring
Router A local area network device commonly used to link local area networks (LANs).
Routers choose the best path for directing network traffic based on address data found
in the network layer (layer 3) of the OSI network architecture model.
Router Manager User Interface A configuration management application that enables
you to group routers so you can backup, restore, and reboot more than one server at a time.
You can also use Router Manager to maintain router configuration and software files on
the FullVision server and view router information, perform tasks, and launch WebLink
sessions. Router Manager User Interface resides on the FullVision INM server.
Ruthless Preemption An emergency handling mode that allows an emergency call to
terminate the call with the lowest priority at all sites involved to handle the emergency.
Secure Calls Encrypted calls.
Selective Inhibit A Radio Control Manager (RCM) command that inhibits
a radio so that it cannot communicate on the system.
Selector Lock A Radio Control Manager (RCM) command that locks the selector
on a radio so that the radio user cannot change talkgroups.
Service Interface Barrier Hardware and software components providing
user authentication and access control for service personnel to network resources.
See also Core Security Management Server.
Simple Network Management Protocol (SNMP) This type of protocol allows system
managers to monitor and control the operation of the network. This protocol defines the format
of a set of management messages and the rules governing how those messages are exchanged
in monitoring and controlling the network. The SNMP messages are used to make requests for
performing network management functions and to report on events that occur in the network.
Simulcast Simulcast is a two-way radio system topology that uses multiple transmitters
on the same frequency in separate locations to transmit the same signal.
Simulcast Prime Site The site where audio information is received and distributed in a
Simulcast subsystem. The main equipment includes the site controller and comparator.
Simulcast Remote Site The sites where the simulcast base stations
are located. Also called a Subsite.
GL-16 6881009Y05-O April 2004

Simulcast Site A simulcast subsystem. The Simulcast site is functionally

equivalent to a single site as viewed by the master site.
Single Transmit Receiver Voting (STRV) Subsystem A radio frequency subsystem
providing radio communication support in the VHF/UHF frequency bands. An STRV
subsystem contains a single transmit site and at least one or more STRV remote sites. An
STRV subsystem must include an STRV prime site, an STRV transmit remote site (if not
already colocated with the STRV prime site), and STRV receive-only remote sites.
Site A physical location that contains equipment to receive, process, and
transmit calls in an RF system. Typically, equipment at a site includes a
controller, base stations, and T1/E1 multiplexers.
Site Access Denial Rejection that occurs when a radio or its affiliation
group do not have access to a site.
Site Control Path The control path between a zone controller and a site.
Examples of sites include Simulcast subsystems.
Site Reference Signal An output signal generated from a highly stable oscillator.
Site Trunking A trunking state where a site or subsystem loses its link to the Master Site
zone controller and the local site controller handles all call processing. Radios affiliated to a
site or subsystem in this state can only communicate with other radios and resources at that site.
Site Viewer A window used in the Affiliation Display application to display the
current affiliation and deaffiliation information for each site within a zone.
SnapShot A Radio Control Manager (RCM) command that issues a database
inquiry to the RCM database to retrieve the last known status of a radio, including
site, zone, talkgroup, and recent commands to the radio. SnapShot does not
initiate a direct communication with the radio.
SNDCP Subnetwork Dependent Convergence Protocol
SNMP See Simple Network Management Protocol (SNMP)
SRP SRP is the communication protocol used between the Radio Network
Gateway (RNG) and the Data Site Controller
Status Commands Radio Control Manager (RCM) outbound functions that request
information from the zone controller or radios, include Radio Check and Zone Status.
Status Event A Radio Control Manager (RCM) event type that allows a radio user to
send a predefined radio status message over the air without talking. This event quickly
informs the user of the radios current operating condition without interrupting normal
talkgroup communication. (A properly configured radio is required.)
Store and Forward This feature enables the Key Variable Loader (KVL)
to store responses to Key Management Messages (KMM) commands it receives
from the Key Management Facility (KMF). The messages are forwarded to the
KMF the next time the KVL connects to the KMF.
Storm Plan A Radio Control Manager (RCM) command that issues a set of predefined
commands, which are easily executed in an emergency or expected situation, such as a parade.
The details of Storm Plans are defined and set up using the UCM and distributed to the RCM.
STR 3000 Base Radio Subsystem A rack of equipment containing power
supplies, distribution panels, and STR 3000 Simulcast Base Radios.
STR 3000 Simulcast Base Radios A base station capable of linear simulcast operations.
STRV Subsystem See Single Transmit Receiver Voting (STRV) Subsystem
6881009Y05-O April 2004 GL-17

Glossary
Subscriber An individual portable or mobile two-way radio unit.

Subsite See Simulcast Remote Site
Supermgr The default account in the network management applications that has
more permissions than the other users. The Supermgr has all allowable permissions
of all the products in the Private Radio Network Management (PRNM) Suite, and
can configure other PRNM users and assign permissions.
System ID Factory-assigned hexadecimal number that references a specific system.
System Manager Person or set of people who have the highest level of system
permissions and can basically do anything to any part of the system.
System Statistics Server (SSS) For systems having more than one
zone, this statistics server collects and stores system-wide statistical information
from each Air Traffic Router (ATR).
T1 High-capacity transmission system used for voice and data primarily in North
America. A T1 is equal to 24 DS0, which is 1.544 Mbps.
Tactical A radio operation that determines how a radio behaves in an emergency situation.
In tactical mode, the radio sends an emergency alarm on the currently affiliated talkgroup.
This setting is preconfigured in the radio through Radio Service Software (RSS).
Talkgroup A uniquely named group of radios that can share calls and messages. A
talkgroups normal communications do not require interfacing with other talkgroups.
Typically, the majority of a radio users communications are within their own talkgroup.
Talkgroup Call A call addressed to all radios in a specific talkgroup.
Talkgroup ID A unique number that refers to a specific talkgroup defined on the
system. The assignable range is from 80000001 to 80065534.
Talkgroup Viewer A window used in the Affiliation Display application to display the
current affiliation and deaffiliation information for a talkgroup or multigroup by ID or alias.
Target Radio The radio whose operation is affected by an outbound
radio command function or a radio selected to receive a call, Call Alert, or
telephone interconnect call is being initiated.
Target Zone The zone to which a radio that is the target of a call,
command, or service is currently affiliated.
TCP/IP Transmission Control Protocol/Internet Protocol. A complex suite of protocols that
includes IP, TCP, and the associated application protocols for exchanging data over a network.
TEK See Traffic Encryption Key (TEK)
Telephone Interconnect Device (TID) Equipment that interfaces the Public
Switched Telephone Network (PSTN) to the ASTRO 25 radio system.
Top of Queue An emergency queue mode that indicates emergency calls have
highest priority and will receive the next available repeater.
Traffic Encryption Key (TEK) A TEK encrypts voice or OTAR and is
assigned to a Common Key Reference (CKR).
Transitional LANs Two LANs that redundantly connect all the
routers in the zone core together.
Transport Network Management (TNM) The applications such as Nortel
Preside, CiscoWorks, and InfoVista that manage the transport network. These
applications are not included in an ASTRO 25 SE system.
GL-18 6881009Y05-O April 2004

Transport Network Performance Server (TNPS) The HP NetServer server where

the InfoVista application resides. This application is not included in an ASTRO 25 SE system.
Trunking The automatic and dynamic sharing of a small number of radio frequencies
among many users. A trunking system distributes message traffic among the available
channels for greater efficiency and to reduce channel waiting time.
Trunking State Defines the ability of a system or site to perform normal
trunking operations. Each site has a trunking state and a pair of zones have
trunking states relative to each other.
UCM See User Configuration Manager (UCM)
UCS See User Configuration Server (UCS)
UKEK See Unique Key Encryption Key (UKEK)
Unattended Emergency Alarm Display In the User Configuration Manager (UCM),
you should ensure that at least one user is configured with unattended Emergency Alarm
display capability so that the users see all Emergency Alarm events in case an attached
Radio Control Manager (RCM) user is not logged in to receive them.
Unique Key Encryption Key (UKEK) This is a Unique Key Encryption Key (UKEK)
assigned to a subscriber for encrypting keys within an over-the-air-rekeying (OTAR)
command sent only to the specific subscriber. Each radio has its own UKEK.
Unmonitored A link that does not have active mobile context associated with it. When
a monitored link is UP, echo requests are sent from the Packet Data Gateway (PDR) to
the Gateway GPRS Support Node (GGSN) and from the GGSN to the PDR.
User A person or group of people who utilize the services and functions of a system.
Users include individual radio users, console operators, management users (administrators and
maintainers of the system), the system manager, technicians, and engineers.
User Configuration Manager (UCM) A management application used to enter and
maintain configuration information for the User Configuration Server (UCS). The UCM
configures System, Subscribers, Security, and Zone Watch Configuration objects. The UCM
is part of the Motorola Private Radio Network Management (PRNM) Suite.
User Configuration Server (UCS) The server that contains the network database
and stores information on system users. User information has to be configured in
the User Configuration Manager (UCM) and is then propagated to each zone so
the same database is present throughout the system.
Values Window A window that allows you to search for information at
a field-entry level rather than a record level.
Visitor Location Register (VLR) A database containing information on all
radios currently in the zone that are based in another zone. The VLR manages a
local copy of zone-specific information for individuals and VLR talkgroups. This
includes subscriber database information and site location information for both the
individual and the talkgroup. Each zone has a VLR.
VistaPortal A Web interface provided with InfoVista that is used to view reports from
the web. You can view offline reports or connect to view online reports.
Voice Channel A channel used to provide voice communications on a radio system.
Voting See ASTRO-TAC 9600 Comparator
VPLMN Visited Public Land Mobile Network
WACN ID See Wide Area Communications Network (WACN) ID
6881009Y05-O April 2004 GL-19

Glossary
WAN Switch Management Server (WSMS) The CompactPCI server where the
Preside MDM application resides. This server is not included in an ASTRO 25 SE system.
Warm-start A warm-start KMM delivers a traffic encryption key to the
radio encrypted with the radios UKEK.
WEBLink A Web-based network management application for management of the
routers. Router Manager provides a launch point for WEBLink.
Wide Area Communications Network (WACN) ID A number that references
a specific network of systems that are connected to one another.
Wide Area Network (WAN) A computer or communications network
that covers a large geographic area.
Wide Area Trunking The normal trunking state of a site. The following
must be in place for wide area trunking: an active site control path to the site, an
enabled control channel at the site, an enabled voice channel at the site, and an
enabled audio rendezvous point at the master site.
Wild card A keyboard character that can be used to represent one or
many characters, such as * or ?.
ZAMBI See Zone Ambassador Interface Board (ZAMBI)
ZCM See Zone Configuration Manager (ZCM)
ZDS See Zone Database Server (ZDS)
Zeroize An over-the-air-rekeying (OTAR) command sent to an individual subscriber
which erases all of the keys in the subscriber. The subscriber must be serviced directly
with a Key Variable Loader (KVL) to restore secure operations.
Zone A geographical area within the system, containing one or more base
stations controlled by a single zone controller.
Zone Ambassador Interface Board (ZAMBI) A board that interfaces
between the Ambassador Electronics Bank (AEB) with the zone controller. This
board contains firmware to accept routing instructions from the zone controller and
communicate these instructions to other boards in the AEB.
Zone Configuration Manager (ZCM) A management application used to enter
and maintain configuration information for the Zone Database Server (ZDS). The
ZCM configures the infrastructure equipment for the system. The ZCM is part of the
Motorola Private Radio Network Management (PRNM) Suite.
Zone Controller The computer responsible for performing call processing.
There is one zone controller per zone.
Zone Database Server (ZDS) This server hosts the Zone Configuration Manager (ZCM)
database, which stores configuration information for the entire infrastructure equipment. It
also provides back-end processes for the network management applications within a zone.
Zone Only Operation within a single zone using one zone controller
and its coverage area only.
Zone Statistics Server (ZSS) This server collects and stores zone-wide
statistical information regarding call processing traffic. This traffic is derived from
the Air Traffic Information Access (ATIA) stream supplied by the Air Traffic Router
(ATR). Historical Reports and Dynamic Reports applications use this information
to create reports on resource usage and performance.
Zone Status A Radio Control Manager (RCM) command that checks the status of the
zones and displays if the zone is enabled or disabled and provides link status for trunking.
GL-20 6881009Y05-O April 2004

Zone Watch A network management application that monitors trunking activity and radio
call traffic for an individual zone in near real time. This application is part of the Private Radio
Network Management (PRNM) suite. See Private Radio Network Management (PRNM) Suite.
6881009Y05-O April 2004 GL-21

Glossary
GL-22 6881009Y05-O April 2004

MOTOROLA and the Stylized M Logo
are registered in the U.S. Patent and
Trademark Office. All other product or
service names are the property of their
respective owners.
Motorola, Inc. 2004

6881009Y05-O Vol 1 Understanding Your Astro 25 PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

6881009Y05-O Vol 1 Understanding Your Astro 25 PDF

Transféré par

Droits d'auteur :

Formats disponibles

ASTRO 25 Trunked Integrated

Voice and Data System Release 6.4

Understanding Your ASTRO 25 Trunking System

Chapter 1: Radio System Concepts

6881009Y05-O April 2004 eDoc i

Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31

Chapter 2: What Is an ASTRO 25 Trunking System?

ii 6881009Y05-O April 2004

Simulcast Remote Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16

Chapter 3: Network Topology

Chapter 4: Hardware Functional Description

6881009Y05-O April 2004 iii

Core Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16

iv 6881009Y05-O April 2004

CENTRACOM Elite Admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-81

Chapter 5: Radio Frequency Subsystems

6881009Y05-O April 2004 v

Console Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26

vi 6881009Y05-O April 2004

Channel Bank. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-67

Chapter 6: ASTRO 25 Systems and Mutual Aid

6881009Y05-O April 2004 vii

Wide Area Network Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17

Chapter 7: Databases, Servers, and Controllers

viii 6881009Y05-O April 2004

Zone Statistics Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27

Chapter 8: Network Security

Chapter 9: Advanced Call Processing

6881009Y05-O April 2004 ix

Multigroup Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-42

Chapter 10: Integrated Voice and Data

x 6881009Y05-O April 2004

GPRS Gateway Support Node Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6

Chapter 11: Other Band Trunking

6881009Y05-O April 2004 xi

Chapter 12: Introduction to the FCAPS Model and PRNM

Chapter 13: Introduction to Network Management Applications

xii 6881009Y05-O April 2004

Custom Historical Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-23

6881009Y05-O April 2004 xiii

Zone Watch Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-63

Appendix A: Power Supply Reference

Appendix B: ASTRO 25 System Documentation

xiv 6881009Y05-O April 2004

Figure 1-1: Basic Radio System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

6881009Y05-O April 2004 xv

xvi 6881009Y05-O April 2004

Figure 4-46: Console Interface Electronics Unit - Rear View . . . . . . . . . . . . . . . . . . . . . . . . . 4-80

6881009Y05-O April 2004 xvii

xviii 6881009Y05-O April 2004

Figure 13-3: Example of the Explorer Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8

6881009Y05-O April 2004 xix

This page intentionally left blank.

xx 6881009Y05-O April 2004

Table 2-1: RF Subsystem Frequency Bands Supported . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22

6881009Y05-O April 2004 xxi

Table 7-10: Air Traffic Router Administration Menu Items . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28

xxii 6881009Y05-O April 2004

Table 13-22: Other Information for System Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-55

6881009Y05-O April 2004 xxiii

This page intentionally left blank.

xxiv 6881009Y05-O April 2004

Procedure 11-1: How to Create an Unstructured Band Plan . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9