MCD 5000

a
2ELEASE
-#$$%3+3%4SYSTEM
WITH OMC
INSTALLATION &CONFIGURATION '5)$%
July
@6802987C96@
2011 Motorola Solutions, Inc. All rights reserved.
6802987C96-A
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.
2011 Motorola Solutions, 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 Solutions, Inc.
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, MOTO, MOTOROLA SOLUTIONS, and the Stylized M Logo are trademarks or registered trademarks of Motorola Trademark Holdings, LLC
and are used under license. All other trademarks are the property of their respective owners.
European Union (EU) Waste of Electrical and Electronic Equipment (WEEE) directive
The European Union's WEEE directive requires that products sold into EU countries must have the crossed out trashbin label on the product (or the package
in some cases).
As defined by the WEEE directive, this cross-out trashbin label means that customers and end-users in EU countries should not dispose of electronic and
electrical equipment or accessories in household waste.
Customers or end-users in EU countries should contact their local equipment supplier representative or service centre for information about the waste collection
system in their country.
Document
History
Document History
6802987C96-A
Edition
Description
Date
Release 1.0
First release of MCD 5000 Deskset System with OMC

Installation and Configuration Guide
July 2011
July 2011
MCD 5000 Deskset System with OMC Installation and Configuration Guide
This page intentionally left blank.
ii
6802987C96-A
July 2011
Table
of
Contents
Contents
Chapter 1: MCD 5000 Deskset System Overview
Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MCD 5000 Deskset System Use Cases . . . . . . . . . . . . . . . . . . . . . .
MCD 5000 Deskset System Architecture and Functionality. . . . . . . . . . . . .
System Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MCD 5000 System Administrator . . . . . . . . . . . . . . . . . . . .
Users with the Privilege to Logon to the MCD 5000 Deskset . . . . . . . .
Technician Users . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Logical Deployment Design . . . . . . . . . . . . . . . . . . . .
System Logical Design Principles . . . . . . . . . . . . . . . . . . .
Example of a Large MCD 5000 Deskset System logic design . . . . . . .
Resources and Identifications . . . . . . . . . . . . . . . . . . . . . . . .
MCD 5000 Deskset System with OMC Topology . . . . . . . . . . . . . . . . .
MCD 5000 Deskset System Capacities . . . . . . . . . . . . . . . . . . . .
MCD 5000 Deskset System with OMC . . . . . . . . . . . . . . . . . . . .
Talkpath Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MCD 5000 Deskset to Single Radio Talkpath (over Cable Connection) . . . . .
MCD 5000 Deskset to Radio Talkpath Over IP Network . . . . . . . . . . . .
Multiple MCD 5000 Deskset to Radio - MCD 5000 RGU Multi-Talkpath Service
MCD 5000 Deskset to Radio through IRC Proxy Talkpath . . . . . . . . . . .
Talkpaths in the System . . . . . . . . . . . . . . . . . . . . . . . . . . .
Emergency in the System . . . . . . . . . . . . . . . . . . . . . . . . .
Inbound Emergency. . . . . . . . . . . . . . . . . . . . . . . . . .
Multiple Inbound Emergency Alarms . . . . . . . . . . . . . . . . .
Outbound Emergency . . . . . . . . . . . . . . . . . . . . . . . . .
Radio Alias Database . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MCD 5000 Deskset System Deployments Architecture. . . . . . . . . . . . . . .
One-to-One MCD 5000 Deskset to Radio . . . . . . . . . . . . . . . . . . .
Single MCD 5000 Deskset to Many Radios . . . . . . . . . . . . . . . . . .
Many MCD 5000 to a Single Radio . . . . . . . . . . . . . . . . . . . . .
Many MCD 5000 Desksets to Many Radios. . . . . . . . . . . . . . . . . .
IRC Proxy Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deployment in Parallel to MC3000 Units . . . . . . . . . . . . . . . . . . .
MCD 5000 Deskset in Parallel to MC3000 Units . . . . . . . . . . . . .
Many-to-Many MCD 5000 Desksets to Radios . . . . . . . . . . . . . .
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6802987C96-A
July 2011
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-1
1-2
1-2
1-2
1-4
1-4
1-4
1-5
1-5
1-5
1-6
1-7
1-8
1-9
1-10
1-10
1-11
1-11
1-12
1-13
1-14
1-14
1-14
1-14
1-15
1-15
1-16
1-16
1-16
1-17
1-18
1-19
1-20
1-21
1-21
1-22
iii
MCD 5000 Deskset Users Authentication . . . . . . . . . . . . . . . . . .

For a Deployed MCD 5000 Deskset with OMC System . . . . . . . . .
OMC/ACP Administrator and Technician Users Authentication . . . . . . .
MCD 5000 Deskset Authentication: Radio Access Permissions . . . . . . .
MCD 5000 Deskset System Functionaries Responsibilities . . . . . . . . . .
Technician/Administrator . . . . . . . . . . . . . . . . . . . . . . .
Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Technician Authentication . . . . . . . . . . . . . . . . . . . . . . .
Summary of Factory Credentials Authentication Cases . . . . . . . . .
VPN Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Customer Owned VPN Protection: Supporting Remote Sites over VPN .
MCD 5000 Deskset Credentials . . . . . . . . . . . . . . . . . . . . . .
MCD 5000 Deskset Application Credentials . . . . . . . . . . . . . .
MCD 5000 Deskset Factory Credentials . . . . . . . . . . . . . . . .
MCD 5000 RGU Credentials. . . . . . . . . . . . . . . . . . . . . . . .
MCD 5000 RGU Factory Credentials. . . . . . . . . . . . . . . . . .
SSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hardening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disaster Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MCD 5000 Deskset Systems Backup . . . . . . . . . . . . . . . . . . . .
Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-22
1-22
1-23
1-23
1-24
1-24
1-25
1-25
1-26
1-26
1-26
1-28
1-28
1-28
1-29
1-29
1-29
1-29
1-29
1-30
1-30
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-1
2-3
2-3
2-3
2-4
2-5
2-5
2-6
2-6
2-7
2-7
2-7
2-8
2-8
2-9
2-9
2-9
2-9
2-10
2-10
2-10
2-10
2-12
2-12
2-13
2-13
Overview of Operations Management Center Server . . . . . . . . . . . . . . . . . . . . . . . . .

OMC Server Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-1
3-1
3-2
Chapter 2: General Hardware Installation Practices

General Safety Precautions. . . . . . . . . . . . . . .
Maintenance Requiring Two People . . . . . . . .
Hazardous Materials . . . . . . . . . . . . . . .
Seismically Active Areas . . . . . . . . . . . . .
Site Preparation . . . . . . . . . . . . . . . . . . . .
Security Considerations . . . . . . . . . . . . . .
Environmental Considerations . . . . . . . . . . .
Surge Protection . . . . . . . . . . . . . . . . .
General Installation Guidelines . . . . . . . . . . . . .
Equipment Inspection and Inventory . . . . . . . .
Placement Recommendations . . . . . . . . . . .
Spacing Requirements . . . . . . . . . . . . . . .
Grounding . . . . . . . . . . . . . . . . . . . .
AC Power . . . . . . . . . . . . . . . . . . . .
FCC Requirements . . . . . . . . . . . . . . . . . .
Equipment Compliance . . . . . . . . . . . . . .
Electromagnetic Safety Requirements. . . . . . . . . .
OSHA Related Safety Requirements (United States) .
Compliance with Local Regulations . . . . . . . .
Guidelines . . . . . . . . . . . . . . . . . .
Installations Outside the United States . . . . .
References . . . . . . . . . . . . . . . . . . . .
Installation and Configuration Tools . . . . . . . . . .
General Tools . . . . . . . . . . . . . . . . . . .
Site-Specific Information . . . . . . . . . . . . . . .
MCD 5000 System Training . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 3: OMC Server - Installation, Configuration, and Maintenance
iv
6802987C96-A
July 2011
OMC Server Logical Architecture . . . . . . . . . . . . . . .

OMC Server Physical Description . . . . . . . . . . . . . . . . .
OMC Server Initial Installation and Configuration . . . . . . . . . . . .
Installing MCD 5000 OMC Server OS . . . . . . . . . . . . . . .
Installing MCD 5000 OMC Server Application . . . . . . . . . . .
Changing the Root Account Password . . . . . . . . . . . . . . .
Viewing/Configuring Network Parameters . . . . . . . . . . . . .
Configuring MCD 5000 Deskset System OMC Servers IP Addresses .
Configuring the Time of Day, Date or Time Zone . . . . . . . . . .
Configuring NTP Client . . . . . . . . . . . . . . . . . . . . . .
Configuring the System Geographical Area . . . . . . . . . . . . .
Advanced Maintenance for OMC Server . . . . . . . . . . . . . . . .
Restarting the OMC Server Service. . . . . . . . . . . . . . . . .
Restarting the MySQL Server Service . . . . . . . . . . . . . . .
Checking the OMC Database Replication Status. . . . . . . . . . .
Restoring the OMC Database from a Backup File . . . . . . . . . .
Synchronizing the OMC Servers Databases . . . . . . . . . . . . .
Backing-up the OMC Server Database . . . . . . . . . . . . . . .
Updating the System and Database Users Passwords. . . . . . . . .
Contents
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-3
3-4
3-7
3-8
3-11
3-12
3-13
3-15
3-17
3-18
3-19
3-20
3-21
3-21
3-22
3-24
3-24
3-26
3-26
MCD 5000 Deskset System Devices . . . . . . . . . . . . . . . . . . . .

MCD 5000 Deskset . . . . . . . . . . . . . . . . . . . . . . . . . .
MCD 5000 Radio Gateway Unit (RGU) . . . . . . . . . . . . . . . .
MCD 5000 Deskset Unit Hardware Description . . . . . . . . . . . . . . .
MCD 5000 Deskset Upper Panel Layout . . . . . . . . . . . . . . . .
MCD 5000 Deskset Bottom and Side Panels Layout . . . . . . . . . . .
MCD 5000 Deskset & Accessories Configurations. . . . . . . . . . . . . .
MCD 5000 Deskset Accessories . . . . . . . . . . . . . . . . . . . .
MCD 5000 Deskset Accessories Description . . . . . . . . . . . . . .
AC In-line Adapter Power Supply Unit . . . . . . . . . . . . . . .
Desktop Paddle Microphone . . . . . . . . . . . . . . . . . . . .
Dual PTT Footswitch (2-pedal) . . . . . . . . . . . . . . . . . .
MCD 5000 Headset Jack Box . . . . . . . . . . . . . . . . . . .
Headset Base with PTT Switch . . . . . . . . . . . . . . . . . .
Headset Base without PTT Switch . . . . . . . . . . . . . . . . .
Cabling the MCD 5000 Deskset . . . . . . . . . . . . . . . . . . . . . .
Connecting Peripheral Equipment to the MCD 5000 Deskset . . . . . . . . .
Phone Like . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting a Handset . . . . . . . . . . . . . . . . . . . . . . .
Classic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting a Desktop Paddle Microphone . . . . . . . . . . . . .
Hands-free Option 1. . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting the Dual PTT Footswitch . . . . . . . . . . . . . . .
Connecting the Headset, Headset Base and Headset Jack Box . . . .
Hands-free option 2 . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting the Headset, Headset Base and Headset Jack Box . . . .
MCD 5000 Radio Gateway Unit (RGU) Hardware Description . . . . . . . .
MCD 5000 Radio Gateway Unit (RGU) Front and Rear Panels Layout . .
Understanding Cables Color Coding . . . . . . . . . . . . . . . . . . . .
Cabling the MCD 5000 RGU. . . . . . . . . . . . . . . . . . . . . . . .
Cabling a Radio to an MCD 5000 RGU or MCD 5000 Deskset . . . . . . . .
Connecting an MCD 5000 Deskset to an SB9600 Radio in Parallel to MC3000
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-1
4-2
4-2
4-2
4-2
4-4
4-6
4-7
4-8
4-8
4-8
4-9
4-10
4-11
4-11
4-12
4-14
4-14
4-14
4-14
4-14
4-14
4-14
4-14
4-15
4-15
4-16
4-16
4-18
4-19
4-21
4-22
Chapter 4: Installing MCD 5000 Deskset System Units
6802987C96-A
July 2011
Connecting Many MCD 5000 Desksets through MCD 5000 RGU to SB9600 Radio in Parallel to
MC3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Chapter 5: Installing the Administrator Control Panel Client PC

ACP Client PC Functional Description . . .
ACP Client PC Physical Description . . . .
ACP Client PC Location and Layout . . . .
ACP Client PC Cabling . . . . . . . . . .
Installing Software on the ACP Client PC . .
Installing Microsoft MapPoint Software
Installing the ACP Software . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5-2
5-2
5-4
5-4
5-4
5-4
5-5
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6-1
6-2
6-8
6-8
6-9
6-14
6-16
6-17
6-21
6-22
6-33
6-36
6-43
6-47
6-50
6-52
6-54
6-55
6-56
6-57
6-58
6-59
6-61
6-62
6-62
6-64
6-66
6-66
6-69
6-73
6-75
6-76
6-76
6-77
6-77
6-79
6-79
6-80
6-81
6-81
6-82
Chapter 6: Administering your System with the Configuration Tool

Installing the Configuration Tool . . . . . . . . . . . . . . .
Accessing the OMC Server and Creating the Technician Profile
Configuring Gateway Units with the Configuration Tool . . . .
Entering User Credentials . . . . . . . . . . . . . . . .
Configuring a GU External LAN IP through Internal LAN .
Installing New MCD 5000 Deskset System Units . . . . .
Grounding the MCD 5000 RGU . . . . . . . . . . . . .
Connecting to a GU . . . . . . . . . . . . . . . . . . .
Adding a GU . . . . . . . . . . . . . . . . . . . . . .
Modifying a GU Configuration. . . . . . . . . . . . . .
Viewing GU System Parameters . . . . . . . . . . . . .
Configuring System Parameters for an Individual GU . . .
Cloning a GU Configuration to Another GU . . . . . . .
Copying a GU Configuration. . . . . . . . . . . . . . .
Configuring the Radio Alias Database . . . . . . . . . .
Saving a GU Configuration to a File . . . . . . . . . . .
Reading a GU Configuration . . . . . . . . . . . . . . .
Resetting a GU . . . . . . . . . . . . . . . . . . . . .
Removing a GU. . . . . . . . . . . . . . . . . . . . .
Changing the RPDFL ID . . . . . . . . . . . . . . . .
CT Application Settings . . . . . . . . . . . . . . . . . . .
MCD 5000 CT Settings . . . . . . . . . . . . . . . . .
OMC IP Connection List . . . . . . . . . . . . . . . .
Monitoring Your System with the Configuration Tool . . . . .
Monitoring MCD 5000 Deskset Audio . . . . . . . . . .
Modifying Audio Monitoring Settings . . . . . . . .
Monitoring MCD 5000 RGU Audio . . . . . . . . . . .
Performing a Radio Scope Test . . . . . . . . . . .
Performing Tx Calibration. . . . . . . . . . . . . .
Equalizer . . . . . . . . . . . . . . . . . . . . . .
Viewing Radio Activity Statistics for MCD 5000 RGUs . .
Working with System Logs . . . . . . . . . . . . . . .
Viewing the Log . . . . . . . . . . . . . . . . . .
Clearing the Logger Window . . . . . . . . . . . .
Setting Logger Window Content . . . . . . . . . . .
Including the Date for Logger Entries . . . . . . . .
Saving the Log to a File . . . . . . . . . . . . . . .
Determining Log File Content . . . . . . . . . . . .
Managing GU Software Loads with the Configuration Tool . .
Installing a GU Software Version on the GU . . . . . . .
Removing a GU Software Version from the GU . . . . . .
vi
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6802987C96-A
July 2011
Contents
Activating a Software Version on the GU . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-83

Programming Radio Buttons with the Configuration Tool . . . . . . . . . . . . . . . . . . . . . . 6-84
Manually Programming Radio Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-85
Chapter 7: MCD 5000 Deskset System Troubleshooting

Troubleshooting with the ACP . . . . . . . . . . . . . . . . . . . . . .
Using Alarms and Events to Flag Problems . . . . . . . . . . . . . .
Using System Logs to Aid in Debugging Efforts. . . . . . . . . . . .
Windows Firewall Alerts . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting OMC Servers . . . . . . . . . . . . . . . . . . . . . .
Gateway Unit Troubleshooting and Configuration . . . . . . . . . . . . .
Gateway Unit Troubleshooting/Configuration Tools . . . . . . . . . .
Troubleshooting Gateway Units . . . . . . . . . . . . . . . . . . .
Pinging Gateway Units on the Internal and External LANs . . . . . . .
How to Ping a Gateway Unit on the External LAN (External LAN).
How To Ping a Gateway Unit on the Internal (local) LAN . . . . .
Updating System Parameters on Gateway Units . . . . . . . . . . . .
Advanced Troubleshooting and Configuration . . . . . . . . . . . . . . .
How to Use the sFTP Command of WinSCP . . . . . . . . . . . . .
How to Revive a Gateway Unit-Gateway Unit Can Load VxWorks . . .
How to Revive a Gateway Unit-Gateway Unit Cannot Load VxWorks .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7-1
7-2
7-2
7-3
7-3
7-5
7-5
7-6
7-10
7-11
7-11
7-12
7-13
7-13
7-15
7-16
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
A-1
A-2
A-2
A-3
A-3
MCD 5000 Deskset System Ports and Services . . . . . . . . . . . . . . . . . . . . . . . . . . .
B-1
Appendix A: Secure Password Rules

ACP Account Password Rules . . . . . . . . . . . . . . .
MCD 5000 Deskset Account PIN Rules. . . . . . . . . . .
Configuration Tool/MMI/SSH/SFTP Account Password Rules
Linux Account Password Rules. . . . . . . . . . . . . . .
Database Account Password Rules . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Appendix B: MCD 5000 Deskset System Ports and Services

for Firewall Configuration
Appendix C: MCD 5000 RGU and MCD 5000 Deskset Specifications

MCD Deskset System Operation and Environmental Specifications .
MCD 5000 Radio Gateway Unit . . . . . . . . . . . . . . .
MCD 5000 Deskset . . . . . . . . . . . . . . . . . . . . .
MCD 5000 RGU and MCD 5000 Deskset Connectors Specifications
Grounding Bolt . . . . . . . . . . . . . . . . . . . . . . .
4W-E&M Line Connections . . . . . . . . . . . . . . . . .
MCD 5000 Headset Jack Box/DeskMIC Audio Specifications .
Connection Audio Input . . . . . . . . . . . . . . . . .
Connection Audio Output . . . . . . . . . . . . . . . .
Radio Digital Communication Connector . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
C-1
C-1
C-2
C-3
C-3
C-3
C-4
C-4
C-4
C-5
MCD 5000 Deskset and MCD 5000 RGU Cable Connectors . . . . . . . . . . . . . . . . . . . . .

4W E&M Connector (RJ45) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E-1
E-2
Appendix D: MCD 5000 Deskset Call Scenarios

Appendix E: MCD 5000 Deskset and MCD 5000 RGU Connectors Pinouts and Settings
6802987C96-A
July 2011
vii
COMM Connector . . . . . . . . . . . . . . . . . . . . . . . .
MCD 5000 Headset Jack Box and Desk MIC Connector . . . . . . .
Footswitch Connector . . . . . . . . . . . . . . . . . . . . . . .
MMI/Local O&M Connector. . . . . . . . . . . . . . . . . . . .
MCD 5000 Deskset/ MCD 5000 RGU External LAN-PoE Connector .
Internal LAN Connector . . . . . . . . . . . . . . . . . . . . . .
MCD 5000 Deskset Handset Connector 4P4C . . . . . . . . . . . .
MCD 5000 Deskset Logger Cable Connector . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
E-2
E-3
E-4
E-4
E-5
E-5
E-6
E-6
MCD 5000 Radio Cable - MCS 2000 Model III Radio Pinouts (cable part number FKN8688)
MCD 5000 Radio Cable CDM Pinouts (cable part number FKN8689) . . . . . . . . . . .
MCD 5000 Radio Cable W9 Pinouts (cable part number FKN8690) . . . . . . . . . . . .
MCD 5000 Radio Cable DS-DJB-W9 Pinouts (cable part number FKN8691). . . . . . . .
MCD 5000 Radio Cable DS-DJB-MCS Pinouts (cable part number FKN8692) . . . . . . .
MCD 5000 Radio Cable DS-DJB-CDM Pinouts (cable part number FKN8693). . . . . . .
MCD 5000 Headset Jack Box Cable Pinouts (cable part number FKN8694) . . . . . . . . .
MCD 5000 External LAN/ PoE Cable Pinouts (cable part number FKN8695) . . . . . . . .
MCD 5000 Deskset Logger Cable Pinouts (cable part number FKN8696) . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
G-1
G-3
G-4
G-5
G-6
G-8
G-9
G-10
G-11
Appendix F: Radios Used With the MCD 5000 Deskset System

Appendix G: Radio Cables Pinouts
Appendix H: Cables Used for MCD 5000 Deskset Connection in Parallel to MC3000
Cable Used for Other than CDM 1550 Family . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cable Used for CDM 1550 Family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
H-1
H-2
Appendix I: Radio Cables and Replacement Parts

Appendix J: Contacting Motorola
Motorola Support Centers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Gathering Information before Calling Motorola . . . . . . . . . . . . . . . . . . . . . . . . .
Telephone Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
J-1
J-1
J-2
Glossary
viii
6802987C96-A
July 2011
List
of
Figures
List of Figures
Figure 1-1: MCD 5000 Deskset System Components Scheme . . . . . . . . . . . . . . . . . .

Figure 1-2: MCD 5000 Deskset System Resources Organization Example. . . . . . . . . . . . .
Figure 1-3: MCD 5000 Deskset System Topology . . . . . . . . . . . . . . . . . . . . . . . .
Figure 1-4: MCD 5000 Deskset to Radio Talkpath Over Cable Connection Example . . . . . . . .
Figure 1-5: Deskset User to Radio Talkpath Example . . . . . . . . . . . . . . . . . . . . . .
Figure 1-6: Multi- MCD 5000 Desksets to Radio - MCD 5000 RGU Multi-Talkpath Service . . . .
Figure 1-7: MCD 5000 Deskset to Radio through IRC Proxy Talkpath Service. . . . . . . . . . .
Figure 1-8: One-to-One MCD 5000 Deskset to Radio Physical Connection Example . . . . . . . .
Figure 1-9: Single MCD 5000 Deskset to Many Radios Example . . . . . . . . . . . . . . . . .
Figure 1-10: Many MCD 5000 Desksets to Single Radio Example . . . . . . . . . . . . . . . .
Figure 1-11: Many MCD 5000 Desksets to Many Radios Example . . . . . . . . . . . . . . . .
Figure 1-12: Example of Many-to-Many System Configuration with IRC Proxy . . . . . . . . . .
Figure 1-13: One MCD 5000 Deskset in Parallel to MC3000 Units using DJB Example . . . . . .
Figure 1-14: Many MCD 5000 Desksets in Parallel to MC3000 Units using DJB Example . . . . .
Figure 1-15: System Access Permission Group Example . . . . . . . . . . . . . . . . . . . . .
Figure 1-16: Remote Sites Over VPN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 1-17: Remote Sites Over Motorolas CRYPTR 2 IP Encryption Modules . . . . . . . . . .
Figure 3-1: OMC Server - Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3-2: OMC Server - Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4-1: MCD 5000 Deskset Upper Panel Layout. . . . . . . . . . . . . . . . . . . . . . .
Figure 4-2: MCD 5000 Deskset Bottom and Side Panels Layout . . . . . . . . . . . . . . . . .
Figure 4-3: AC In-line Adapter (US cord not shown) . . . . . . . . . . . . . . . . . . . . . .
Figure 4-4: Desktop Paddle Microphone . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4-5: Dual PTT Footswitch Two Foot Pedals . . . . . . . . . . . . . . . . . . . . . .
Figure 4-6: MCD 5000 to Headset Connection Scheme . . . . . . . . . . . . . . . . . . . . .
Figure 4-7: MCD 5000 Headset Jack Box RJ45 View . . . . . . . . . . . . . . . . . . . . . .
Figure 4-8: Headset Base with PTT Switch . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4-9: Headset Base without PTT Switch. . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4-10: MCD 5000 RGU Front and Rear Panels (Example) . . . . . . . . . . . . . . . . .
Figure 4-11: Cables Color Coding Radio Cable Type. . . . . . . . . . . . . . . . . . . . . .
Figure 4-12: Cables Color Coding Jackbox Cable Type. . . . . . . . . . . . . . . . . . . . .
Figure 4-13: Cables Color Coding LAN Cable Type . . . . . . . . . . . . . . . . . . . . . .
Figure 4-14: Cables Color Coding Logger Cable Type . . . . . . . . . . . . . . . . . . . . .
Figure 4-15: One MCD 5000 Deskset to SB9600 Radio in Parallel to MC3000 . . . . . . . . . .
Figure 4-16: Many MCD 5000 Desksets to SB9600 Radio in Parallel to MC3000 . . . . . . . . .
Figure 5-1: ACP Client PC - Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5-2: ACP Client PC - Rear View. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-1: MCD 5000 with OMC Configuration Tool Main Window - Disconnected . . . . . . .
Figure 6-2: Configuration Tool - Connect to OMC Window . . . . . . . . . . . . . . . . . . .
Figure 6-3: Configuration Tool Main Window - Connected to OMC . . . . . . . . . . . . . . .
Figure 6-4: Configuration Tool - Create Technician Profile Message Window . . . . . . . . . . .
Figure 6-5: Create Technician Profile - Step 1 of 3 (Download GU Configuration Files) Dialog Box
6802987C96-A
July 2011
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-3
1-7
1-9
1-11
1-12
1-12
1-13
1-16
1-17
1-18
1-19
1-20
1-21
1-22
1-24
1-27
1-28
3-5
3-6
4-3
4-5
4-8
4-9
4-10
4-11
4-11
4-11
4-12
4-16
4-18
4-18
4-19
4-19
4-23
4-26
5-3
5-3
6-3
6-3
6-4
6-4
6-5
ix
List of Figures
Figure 6-6: Create Technician Profile - Step 2 of 3 (Download GU Software Versions) Dialog Box .
Figure 6-7: Create Technician Profile - Step 3 of 3 (Download Radio Alias Database Files) Dialog
Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-8: Create Technician Profile Message Window . . . . . . . . . . . . . . . . . . . . .
Figure 6-9: Enter User Credentials Window . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-10: User Credentials Failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-11: MCD 5000 Deskset Connection . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-12: MCD 5000 RGU Connection . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-13: Configuration Tool Main Window - Connected to GU . . . . . . . . . . . . . . . .
Figure 6-14: Modify MCD 5000 Gateway Unit Configuration Dialog Box - General Properties Tab .
Figure 6-15: Modify Gateway Unit Configuration Dialog Box - IP Configuration Tab . . . . . . .
Figure 6-16: GU Notification Message Window . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-17: MCD 5000 Deskset External Connector . . . . . . . . . . . . . . . . . . . . . .
Figure 6-18: MCD 5000 RGU External Connector. . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-19: MCD 5000 RGU Connection . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-20: MCD 5000 Deskset Connection . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-21: MCD 5000 with OMC Configuration Tool Main Window - Disconnected . . . . . . .
Figure 6-23: Configuration Tool - Change Local Mode GU IP Window . . . . . . . . . . . . . .
Figure 6-26: Modify MCD 5000 Gateway Unit Configuration Dialog Box - General Properties Tab .
Figure 6-27: Modify Radio Gateway Unit Configuration Dialog Box General Properties Tab . .
Figure 6-28: Modify Gateway Unit Configuration Dialog Box - MCD 5000 Properties Tab . . . . .
Figure 6-29: Configuration Tool - Select Group Dialog Box . . . . . . . . . . . . . . . . . . .
Figure 6-30: Modify Gateway Unit Configuration Dialog Box - Radio Resource Properties Tab. . .
Figure 6-31: Configuration Tool - Select Group Dialog Box . . . . . . . . . . . . . . . . . . .
Figure 6-32: Advanced Radio Resource Properties Window . . . . . . . . . . . . . . . . . . .
Figure 6-33: Modify Gateway Unit Configuration Dialog Box - IP Configuration Tab . . . . . . .
Figure 6-34: GU Notification Message Window . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-36: System Parameters Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-38: System Parameters Dialog Box, MCD 5000 Sites Tab - No Data . . . . . . . . . . .
Figure 6-39: System Parameters Dialog Box - MCD 5000 Sites Tab, Example . . . . . . . . . . .
Figure 6-40: System Parameters Dialog Box - Talkpath Tab . . . . . . . . . . . . . . . . . . .
Figure 6-41: System Parameters Dialog Box - Quality of Service Tab . . . . . . . . . . . . . . .
Figure 6-42: Warning Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-44: Modify Gateway Unit Configuration Dialog Box - General Properties Tab . . . . . .
Figure 6-45: System Tree Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-48: Select Specific Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-49: Radio Alias Database Main Window . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-50: Radio Alias Database Save to File. . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-51: Radio Alias Database Read from File . . . . . . . . . . . . . . . . . . . . . .
Figure 6-54: Read GU Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-55: Read GU Configuration from File Open File Dialog . . . . . . . . . . . . . . .
Figure 6-57: Confirmation Dialog Box, before Resetting a GU . . . . . . . . . . . . . . . . . .
Figure 6-58: Confirmation Dialog Box, Before Removing a GU . . . . . . . . . . . . . . . . .
Figure 6-59: Notification Dialog Box, After Removing a GU . . . . . . . . . . . . . . . . . . .
. .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6-6
6-7
6-7
6-9
6-9
6-10
6-10
6-11
6-12
6-13
6-13
6-14
6-14
6-15
6-16
6-18
6-19
6-20
6-21
6-22
6-24
6-24
6-26
6-27
6-28
6-29
6-30
6-32
6-32
6-33
6-35
6-36
6-37
6-38
6-39
6-41
6-43
6-44
6-45
6-46
6-48
6-49
6-50
6-51
6-51
6-52
6-52
6-53
6-54
6-54
6-55
6-56
6-56
6-56
6802987C96-A
July 2011
List of Figures
Figure 6-60: Get GU RPDFL Data Window . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 6-61: Set RPDFL ID Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-62: CT Settings Dialog Box - Timeouts Tab . . . . . . . . . . . . . . . . . . . . . .
Figure 6-63: CT Settings Dialog Box - Logger Tab . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-64: CT Settings Dialog Box Language Settings Tab . . . . . . . . . . . . . . . . . .
Figure 6-65: OMC IP Connection List Dialog Box. . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-66: MCD 5000 Deskset Audio Monitoring Dialog Box . . . . . . . . . . . . . . . . .
Figure 6-67: Audio Monitoring Dialog Box Showing Audio Sample . . . . . . . . . . . . . . .
Figure 6-68: Trigger Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-69: Y Axis Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-70: Radio Audio Monitoring Dialog Box, Scope Test Tab . . . . . . . . . . . . . . . .
Figure 6-71: Resources List Dialog Box for Audio Monitoring . . . . . . . . . . . . . . . . . .
Figure 6-72: Scope Test Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-73: Radio Audio Monitoring Dialog Box, TX Calibration Tab . . . . . . . . . . . . . .
Figure 6-74: Resources List Dialog Box for Audio Monitoring . . . . . . . . . . . . . . . . . .
Figure 6-75: Tx Calibration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-76: Radio Audio Monitoring Dialog Box, Equalizer Tab. . . . . . . . . . . . . . . . .
Figure 6-77: Resources List Dialog Box for Equalizing . . . . . . . . . . . . . . . . . . . . .
Figure 6-78: Radio Activity Statistics Dialog Box . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-79: Logger Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-80: Logger Window Printout Level Dialog Box . . . . . . . . . . . . . . . . . . . . .
Figure 6-81: Save As Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-82: Log File Printout Level Dialog Box . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-83: Manage SW Releases on GU Dialog Box . . . . . . . . . . . . . . . . . . . . . .
Figure 6-84: Browse For Folder Window . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-85: Configuration Tool - Manage SW Releases on GU Dialog Box . . . . . . . . . . . .
Figure 6-86: Manage SW Releases on GU Dialog Box . . . . . . . . . . . . . . . . . . . . . .
Figure 6-87: Motorola MCS 2000 Radio Showing Two Types of Buttons . . . . . . . . . . . . .
Figure 6-88: Programmable Buttons Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-89: Programmable Buttons Dialog Box Selective Call Tab . . . . . . . . . . . . . .
Figure 6-90: Programmable Buttons Dialog Box Displayed Icons . . . . . . . . . . . . . . .
Figure 6-91: Defining Your Set of Icons Per Radio Opcode . . . . . . . . . . . . . . . . . . .
Figure 6-92: Possible Icons Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7-1: Internal vs. External LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7-2: WinSCP Login Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7-3: WinSCP New Session Window . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7-4: WinSCP Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure G-1: MCD 5000 Radio Cable MCS 2000 Cable Pinouts (cable part number FKN8688) . .
Figure G-2: MCD 5000 Radio Cable - CDM Radio Pinouts (cable part number FKN8689) . . . . .
Figure G-3: MCD 5000 Radio Cable W9 Radio Pinouts (cable part number FKN8690) . . . . . .
Figure G-4: MCD 5000 Radio Cable DS-DJB-W9 Radio Pinouts (cable part number FKN8691) .
Figure G-5: MCD 5000 Radio Cable DS-DJB-MCS Radio Pinouts (cable part number FKN8692)
Figure G-6: MCD 5000 Radio Cable DS-DJB-CDM Radio Pinouts (cable part number FKN8693)
Figure G-7: MCD 5000 Headset Jack Box Cable Pinouts (cable part number FKN8694) . . . . . .
Figure G-8: MCD 5000 External LAN/ PoE Cable Pinouts (cable part number FKN8695) . . . . .
Figure G-9: MCD 5000 Deskset Logger Cable Pinouts (cable part number FKN8696) . . . . . . .
Figure H-1: MCD 5000 Deskset in Parallel to MC3000 Units using DJB to Radio other than CDM .
Figure H-2: MCD 5000 Deskset in Parallel to MC3000 Units using DJB to CDM Radio . . . . . .
6802987C96-A
July 2011
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6-57
6-58
6-59
6-60
6-60
6-61
6-62
6-63
6-65
6-65
6-67
6-67
6-69
6-70
6-71
6-73
6-74
6-74
6-75
6-76
6-77
6-79
6-80
6-81
6-82
6-83
6-84
6-85
6-86
6-87
6-88
6-89
6-89
7-11
7-14
7-14
7-15
G-2
G-3
G-4
G-5
G-6
G-8
G-9
G-10
G-11
. H-1
. H-2
xi
List of Figures
xii
6802987C96-A
July 2011
List
of
Tables
List of Tables
Table 1-1: Maximum Entities Per Each Hierarchy Level . . . . . . . . . . . . . . . . . . . . . . . 1-6

Table 1-2: MCD 5000 Deskset System Capacities . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Table 2-1: Site Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Table 2-2: Operating and Environmental Specifications . . . . . . . . . . . . . . . . . . . . . . . 2-6
Table 3-1: Operating and Environmental Specifications for the OMC Server (Hewlett Packard ProLiant
server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Table 3-2: OMC Server Rear View Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Table 4-1: MCD 5000 Deskset Upper Panel Features . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Table 4-2: MCD 5000 Deskset Bottom and Side Panels Features . . . . . . . . . . . . . . . . . . . 4-5
Table 4-3: MCD 5000 Deskset Unit Accessories. . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Table 4-4: MCD 5000 Deskset Supported Headset Models . . . . . . . . . . . . . . . . . . . . . . 4-7
Table 4-5: MCD 5000 RGU Front and Rear Panels Features . . . . . . . . . . . . . . . . . . . . . 4-17
Table 6-1: Differentiated Services CodePoint (DSCP) Quality of Service Types . . . . . . . . . . . . 6-42
Table 7-1: System Information in the ACP Used for Troubleshooting . . . . . . . . . . . . . . . . . 7-1
Table 7-2: Troubleshooting OMC Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Table 7-3: MCD 5000 Deskset LED Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Table 7-4: MCD 5000 RGU LED Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Table 7-5: Troubleshooting Gateway Unit Installation . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Table B-1: MCD 5000 Deskset System Ports and Services . . . . . . . . . . . . . . . . . . . . . . B-1
Table C-1: MCD 5000 RGU Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Table C-2: MCD 5000 Deskset Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Table C-3: Audio IN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
Table C-4: Radio Output Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
Table C-5: Headset Input Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
Table C-6: Headset Output Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
Table C-7: Radio Digital Communication Connector Specifications. . . . . . . . . . . . . . . . . . C-5
Table D-1: Possible Call Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Table E-1: MCD 5000 Deskset and MCD 5000 RGU Cable Connectors . . . . . . . . . . . . . . . . E-1
Table E-2: Radio 4W E&M Connector Pin List . . . . . . . . . . . . . . . . . . . . . . . . . . . E-2
Table E-3: Radio COMM Connector Pin List (RJ45). . . . . . . . . . . . . . . . . . . . . . . . . E-2
Table E-4: JckBx/DskMIC Connector Pin List (RJ45) . . . . . . . . . . . . . . . . . . . . . . . . E-3
Table E-5: Footswitch Connector Pin List (KK MOLEX 3 pos.) . . . . . . . . . . . . . . . . . . . E-4
Table E-6: MMI/Local O&M Connector Pin List (RJ45) PoE. . . . . . . . . . . . . . . . . . . . . E-4
Table E-7: MCD 5000 Deskset/MCD 5000 RGU Connector 8 pos. Pin List (RJ45) . . . . . . . . . . E-5
Table E-8: Internal LAN Connector Pin List (RJ45) . . . . . . . . . . . . . . . . . . . . . . . . . E-5
Table E-9: MCD 5000 Deskset Handset Connector 4P4C Pin List (RJ22) . . . . . . . . . . . . . . . E-6
Table E-10: MCD 5000 Deskset Logger Cable Connector Pin List (RJ45) . . . . . . . . . . . . . . . E-6
Table I-1: List of Supported Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-1
Table I-2: Replacement Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-2
6802987C96-A
July 2011
xiii
List of Tables
xiv
6802987C96-A
July 2011
List
of
Procedures
List of Procedures
Procedure 3-1: How to Install the OMC Server OS . . . . . . . . . . . . . . . . . . . . . . .

Procedure 3-2: How to Install the OMC Server Application . . . . . . . . . . . . . . . . . . .
Procedure 3-3: How to Change the Root Account Password . . . . . . . . . . . . . . . . . . .
Procedure 3-4: How to View/Configure Network Parameters . . . . . . . . . . . . . . . . . . .
Procedure 3-5: How to Configure OMC Servers IP Addresses . . . . . . . . . . . . . . . . . .
Procedure 3-6: How to Configure the Time of Day, Date, or Time Zone of the OMC Server . . . .
Procedure 3-7: How to Configure NTP Client of the OMC Server . . . . . . . . . . . . . . . .
Procedure 3-8: How to Configure MCD 5000 Deskset System Geographical Area . . . . . . . . .
Procedure 3-9: Restarting the OMC Server Service . . . . . . . . . . . . . . . . . . . . . . .
Procedure 3-10: Restarting the MySQL Server Service. . . . . . . . . . . . . . . . . . . . . .
Procedure 3-11: Checking the OMC Database Replication Status . . . . . . . . . . . . . . . . .
Procedure 3-12: Restoring the OMC Database from a Backup File . . . . . . . . . . . . . . . .
Procedure 3-13: Synchronizing the OMC Servers Databases . . . . . . . . . . . . . . . . . . .
Procedure 3-14: Backingup the OMC Server Database . . . . . . . . . . . . . . . . . . . .
Procedure 3-15: How to Change Database or System-user Password on MCD 5000 Deskset System
Procedure 4-1: Cabling the MCD 5000 Deskset . . . . . . . . . . . . . . . . . . . . . . . . .
Procedure 4-2: Connecting the Headset . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedure 4-3: Connecting the Headset and Headset Jack Box . . . . . . . . . . . . . . . . . .
Procedure 4-4: Cabling an MCD 5000 RGU. . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedure 4-5: Connecting a Radio to the MCD 5000 Equipment . . . . . . . . . . . . . . . . .
Procedure 4-6: Connecting the Radio, the Digital Junction Box and the MCD 5000 Equipment . . .
Procedure 4-7: Connecting the Radio, the Digital Junction Box and the MCD 5000 Equipment . . .
Procedure 5-1: Installing the ACP Software on the ACP Client PC . . . . . . . . . . . . . . . .
Procedure 6-1: Installing the Configuration Tool Application on the Technician PC . . . . . . . .
Procedure 6-2: Accessing the OMC Server and Creating the Technician Profile . . . . . . . . . .
Procedure 6-3: Entering User Credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedure 6-4: Configuring a GU External LAN IP Through Internal LAN . . . . . . . . . . . .
Procedure 6-5: Installing a New MCD 5000 RGU Unit with Internal LAN Connection . . . . . . .
Procedure 6-6: Installing a New MCD 5000 Deskset Unit with Internal LAN Connection . . . . .
Procedure 6-7: Grounding the MCD 5000 RGU . . . . . . . . . . . . . . . . . . . . . . . . .
Procedure 6-8: Connecting Directly to a GU . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedure 6-9: Connecting to the GU Using a LAN . . . . . . . . . . . . . . . . . . . . . . .
Procedure 6-10: Adding a GU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedure 6-11: Modifying a GU Configuration . . . . . . . . . . . . . . . . . . . . . . . . .
Procedure 6-12: Viewing GU System Parameters . . . . . . . . . . . . . . . . . . . . . . . .
Procedure 6-13: Configuring System Parameters for an Individual GU . . . . . . . . . . . . . .
Procedure 6-14: Cloning a GU Configuration to Another GU. . . . . . . . . . . . . . . . . . .
Procedure 6-15: Copying a GU's Configuration to Another GU . . . . . . . . . . . . . . . . . .
Procedure 6-16: Configuring the Radio Alias Database . . . . . . . . . . . . . . . . . . . . .
Procedure 6-17: Saving a GU Configuration to a File . . . . . . . . . . . . . . . . . . . . . .
Procedure 6-18: Reading a GU Configuration . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedure 6-19: Resetting a GU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6802987C96-A
July 2011
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-8
3-11
3-12
3-13
3-16
3-17
3-18
3-19
3-21
3-22
3-22
3-24
3-25
3-26
3-27
4-12
4-15
4-15
4-19
4-21
4-22
4-24
5-5
6-2
6-3
6-8
6-9
6-14
6-15
6-16
6-17
6-19
6-21
6-22
6-33
6-36
6-43
6-47
6-50
6-52
6-54
6-55
xv
List of Procedures
Procedure 6-20: Removing a GU . . . . . . . . . . . . . . . . . . . . . . . . .

Procedure 6-21: Changing the RPDLFL ID . . . . . . . . . . . . . . . . . . . .
Procedure 6-22: Modifying CT Settings. . . . . . . . . . . . . . . . . . . . . .
Procedure 6-23: Modifying the OMC IP Connection List. . . . . . . . . . . . . .
Procedure 6-24: Changing MCD 5000 Deskset Audio Monitoring Settings . . . . .
Procedure 6-25: Setting the Trigger Value . . . . . . . . . . . . . . . . . . . . .
Procedure 6-26: Setting Y Axis Options . . . . . . . . . . . . . . . . . . . . .
Procedure 6-27: Performing a Scope Test . . . . . . . . . . . . . . . . . . . . .
Procedure 6-28: Performing Tx Calibration . . . . . . . . . . . . . . . . . . . .
Procedure 6-29: Equalizer . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedure 6-30: Viewing Radio Activity Statistics for MCD 5000 RGUs . . . . . .
Procedure 6-31: Viewing the Log. . . . . . . . . . . . . . . . . . . . . . . . .
Procedure 6-32: Setting the Level of Logger Window Messages . . . . . . . . . .
Procedure 6-33: Setting Logger Window Message Type . . . . . . . . . . . . . .
Procedure 6-34: Saving a Log to a File . . . . . . . . . . . . . . . . . . . . . .
Procedure 6-35: Setting the Level of Log File Messages . . . . . . . . . . . . . .
Procedure 6-36: Installing a GU Software Version on the GU. . . . . . . . . . . .
Procedure 6-37: Removing a GU Software Version from the GU . . . . . . . . . .
Procedure 6-38: Activating a Software Version on the GU . . . . . . . . . . . . .
Procedure 6-39: Programming Radio Buttons Manually with the Configuration Tool .
Procedure 7-1: How to Ping a Gateway Unit on the External LAN . . . . . . . . .
Procedure 7-2: How to Ping a Gateway Unit on the Local (internal) LAN . . . . . .
Procedure 7-3: How to Use the sFTP Command of WinSCP . . . . . . . . . . . .
Procedure 7-4: How to Revive a Gateway Unit-Gateway Unit can load VxWorks . .
Procedure 7-5: How to Revive a Gateway Unit-Gateway Unit Cannot Load VxWorks
xvi
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6-56
6-57
6-59
6-61
6-62
6-65
6-65
6-66
6-69
6-73
6-75
6-76
6-77
6-78
6-79
6-80
6-81
6-82
6-83
6-86
7-11
7-11
7-13
7-15
7-16
6802987C96-A
July 2011
List
of
Processes
List of Processes
Process 1-1: How to Install an MCD 5000 Deskset System . . . . . . . . . . . . . . . . . . . . . . 1-30
6802987C96-A
July 2011
xvii
List of Processes
xviii
6802987C96-A
July 2011
About
This
Manual
MCD 5000 Deskset System with OMC

Installation and Configuration Guide
The purpose of this manual is to help you install and service the current release of the Motorola
MCD 5000 Deskset System with OMC. This document is written for technicians and Motorola
field support engineering who are responsible for the installation and servicing of an MCD 5000
Deskset System with OMC. This manual details generic installation techniques to assemble an
MCD 5000 Deskset System with OMC and troubleshoot problems.
What Is Covered In This Manual?

This manual focuses on the installation, configuration, and advanced maintenance of site
hardware and software for the MCD 5000 Deskset System:
6802987C96-A
July 2011
Chapter 1, "MCD 5000 Deskset System Overview" - presents an overview of the system
and a detailed list of components and system configuration options.
Chapter 2, "General Hardware Installation Practices"- presents background installation,

safety information, and equipment placement information.
Chapter 3, "OMC Server - Installation, Configuration, and Maintenance"- presents

detailed information about the Operations Management Center (OMC) Server, including
installation, configuration, and advanced maintenance information.
Chapter 4, "Installing MCD 5000 Deskset System Units"- presents detailed information
about the MCD 5000 Deskset System units, including installation information.
Chapter 5, "Installing the Administrator Control Panel Client PC"- presents

detailed information about the Administrator Control Panel (ACP) Client PC,
including installation and configuration information.
Chapter 6, "Administering your System with the Configuration Tool"- presents detailed
information about configuring the technician PC, configuring gateway units, adding
gateway units, and monitoring your system with the Configuration Tool.
Chapter 7, "MCD 5000 Deskset System Troubleshooting"- presents information

about troubleshooting servers and gateway units.
Appendix A, "Secure Password Rules". This appendix gives the secured password
rules for the different usernames defined in the system.
Appendix B, "MCD 5000 Deskset System Ports and Services for Firewall
Configuration". This appendix lists the firewall ports that should be configured
in the MCD 5000 Deskset System firewall.
xix
About This Manual
Appendix C, "MCD 5000 RGU and MCD 5000 Deskset Specifications". This appendix
provides MCD 5000 Deskset and MCD 5000 RGU connectors specifications.
Appendix D, "MCD 5000 Deskset Call Scenarios". This appendix provides

MCD 5000 Deskset possible call scenarios.
Appendix E, "MCD 5000 Deskset and MCD 5000 RGU Connectors Pinouts and Settings".
This appendix provides pin lists for the gateway unit connections.
Appendix F, "Radios Used With the MCD 5000 Deskset System". This appendix
provides lists of radios used with the MCD 5000 Deskset System.
Appendix G, "Radio Cables Pinouts". This appendix provides information about the
special cables used to connect Motorola radios to the MCD 5000 RGU.
Appendix H, "Cables Used for MCD 5000 Deskset Connection in Parallel to MC3000".
This appendix provides information about the special cables used to connect the MCD
5000 Deskset to a CDM 1550 family radio in parallel to an MC3000.
Appendix I, "Radio Cables and Replacement Parts". This appendix presents information
about the special cables used to connect Motorola radios to the MCD 5000 RGU, and
about various replacement parts of the MCD 5000 Deskset.
Appendix J, "Contacting Motorola". This appendix provides information for

contacting the Motorola System Support Center.
Master Glossary: This glossary defines terms for all MCD 5000 Deskset
System configurations and tools.
Helpful Background Information

Motorola offers a variety of courses designed to assist in learning about the system. For information, go to
http://www.motorola.com/training to view the current course offerings and technology paths.
Related Information
In addition to this manual, the following documents are available for the MCD 5000 Deskset System:
xx
MCD 5000 Deskset User Guide (6802987C94)
MCD 5000 Deskset System without OMC Installation and Configuration Guide (6802987C97)
MCD 5000 Deskset System Administration Control Panel User Guide (6802987C99)
MCD 5000 Deskset System Information Assurance Guide (6802987C98)
6802987C96-A
July 2011
Icon Conventions
Other related documentation:
CRYPTR 2 datasheet on the Motorola website or contact Motorola support.
Another set of manuals exist for Radios and other system related Units:
MC3000TM Digital Deskset Operator and Installation Manual (6880309L15)
CDM1550LS VHF-UHF User Guide (6881094C79)
Digital Spectra Models W4, W5, W7, and W9 Users Guide (68P81074C80)
MCS2000 Model III Users Guide (68P81083C10)
XTL 5000 Consolette Instruction Manual (6881098C21)
RF energy awareness information and operating instructions in the Product

Safety and RF Exposure booklet (68P81095C99)
Icon Conventions
CAUTION Indicates a potentially hazardous situation which, if not avoided, MAY

result in minor or moderate injury. CAUTION may also be used to alert against
unsafe practices and property-damage-only accident hazards.
IMPORTANT contains information that emphasize points or remind readers of something,

or to indicate minor problems in the outcome of what they are doing.
NOTEs contain information about exceptions or preconditions, refer the reader elsewhere for
additional information, remind the reader how to complete an action (when it is not part of
the current procedure), or tell the reader where something is located on the screen.
6802987C96-A
July 2011
xxi
Icon Conventions
xxii
6802987C96-A
July 2011
Chapter
1
MCD 5000 Deskset System Overview
Background
The MCD 5000 Deskset is the Next-Generation radio dispatch deskset platform that uses VoIP technology.
The MCD 5000 Deskset provides digital control to a variety of Motorola land mobile radios. Through
the digital control link the MCD 5000 Deskset emulates the control head of the radio allowing the
deskset to perform all the functions that can be performed using the radio control head.
The following radios can be controlled via the MCD 5000 Deskset:
ASTRO Consolette (W9): ASTRO Spectra, ASTRO Spectra Plus, XTL 5000
CDM Series Radios: CDM 1550, CDM 1550 LS, CDM 1550 LS+
MCS 2000 Model III Control Station
The MCD 5000 Deskset System solution uses a new or existing IP network allowing remote control
of a 2-way radio located elsewhere on the network. Each MCD 5000 Deskset user can dynamically
select a radio to control and have a range of capability from simple talk/listen thru complete radio
feature access. The 2-way radio connects to the IP network thru a MCD 5000 Radio Gateway Unit
(RGU) that allows from 1 to 4 radios to be connected to a single MCD 5000 RGU. The MCD 5000
Deskset can only connect to and monitor one radio channel at a time.
Throughout this manual the term Gateway Unit (GU) refers to both the MCD
5000 Deskset and the MCD 5000 RGU.
6802987C96-A
July 2011
1-1
MCD 5000 Deskset System Use Cases
MCD 5000 Deskset System Use Cases
The MCD 5000 Deskset System use cases are as follows:
Used in a backup dispatch center operation; if the main consoles are not operational for some
reason, the Desksets could be used to provide emergency backup dispatch capability.
Used in a mobile command center vehicle where limited dispatch functionality is needed.
Used in an Emergency Operation Center type situation where focused dispatch operations
are set up in a conference room to handle a specific emergency situation.
Used in a remotely located area (e.g. a guard shack) where someone needs
dispatch capability on one radio channel.
Used on a Captain's or Commanders desk where a full dispatch console is not required,
but only the ability to monitor some channels in certain situations.
Used in a very small dispatch center.
MCD 5000 Deskset System Architecture and Functionality
System Components
Figure 1-1 depicts the MCD 5000 Deskset System Components scheme.
1-2
6802987C96-A
July 2011
Figure 1-1
System Components
MCD 5000 Deskset System Components Scheme
The system consists of the following components:
6802987C96-A
July 2011
MCD 5000 Deskset: Phone-like devices used by the End-User for operating the MCD 5000
Deskset System. Each MCD 5000 Deskset connects to a single Radio Device at a time.
MCD 5000 Radio Gateway Unit (RGU): The Radio Gateway units connect Radio equipment
to the MCD 5000 Deskset System. The Radio Gateway can interface up to 4 Radio devices.
Configuration Tool (CT): The CT is a Windows based utility, used to configure all parameters
and settings of the MCD 5000 Deskset and the Radio Gateway. The CT can be located
remotely, anywhere on the IP network, or locally, using an Ethernet connection.
IP Network: This is the customer provided WAN/LAN IP Network.
Two-Way Radio Devices: Provide the access to the customer LMR system. The Radios
control panel appear at the MCD 5000 Deskset as a Virtual Control Head in the lower part of
the display.
The MCD 5000 Deskset can connect to following radios:
ASTRO Consolette (W9): ASTRO Spectra, ASTRO Spectra Plus, XTL5000
CDM Series Radios: CDM1550, CDM1550 LS, CDM1550 LS+
MCS 2000 Model III Control Station
Operation and Maintenance Center (in System with OMC only) Server: The OMC Server
is the main management server in the MCD 5000 Deskset System. It is responsible for the
MCD 5000 Deskset System operation, maintenance, provisioning, and control. It is the central
repository, where all system users (administrators, technicians) and resources (MCD 5000s,
Radios) are registered, and where system-wide information (alarms, logs, audits) is stored.
The server runs on the Red Hat Linux operating system. The Administrator Control Panel
(ACP) Client PC provides a user level interface to the OMC. Because of its importance,
the OMC Server can be provided in a warm-standby redundant configuration.
Administrator Control Panel (ACP) Client Personal Computer (PC): The ACP Client PC
provides a user level interface to the OMC. It allows an administrator, located locally at the
OMC, or remotely anywhere on the customer WAN network, to perform management activities
for the system. The ACP Client PC runs on the Microsoft Windows 7 operating system.
1-3
Users
Users
The following classes of MCD 5000 Deskset System users are defined:
MCD 5000 System Administrator

This class contains the highest privileged users. An MCD 5000 system administrator manages
access permissions and is responsible for updating the system-wide Database table at the OMC
using the ACP application to download to all system MCD 5000 Desksets.
The following MCD 5000 system administrator user types (classes) are available when configuring users:
State-wide Administrator: a super user that is allowed all privileges including OMC
control, security management, and software downloading.
It is highly recommended that the customer define and use at least two different
State-wide administrators in the system. This is important for providing
backup, in case one of the State-wide administrators forgets or loses his/her
password. Having a backup to the state-wide administrator is important, as only
state-wide administrators can reset user passwords in the system.
Regional Administrator: limited to working with resources for the assigned region
only and not allowed to handle software downloading.
Local Administrator: limited to working with resources for the assigned local PSAP
only and not allowed to handle software downloading.
Users with the Privilege to Logon to the MCD 5000 Deskset
The MCD 5000 Deskset user authentication is optional. This might be turned off/on
on a System-wide basis using the ACP Application.
There are three levels of users. The distinction between the three levels of users is given below:
1-4
MCD 5000 Dispatcher Administrator user type: is allowed to unlock the MCD 5000
Deskset when the MCD 5000 Deskset is locked by another user.
The MCD 5000 Deskset becomes locked for an administrator-configurable period of
time if the user has incorrectly typed passwords for an administrator-configurable
number of consecutive attempts within a configurable time.
MCD 5000 Dispatcher Supervisor type: will have the supervisor option available.
A Supervisor is given PTT Priority over all other MCD 5000 Desksets with lower
priorities. The Supervisor type user can pre-empt a Radio transmission of a User
type user; the supervisory initiator is notified about the preemption success. The MCD
5000 Desksets which have been preempted are immediately prevented from transmission,
and are notified about that on their MCD 5000 Deskset GUI.
MCD 5000 Dispatcher User type: will work as regular user. This class includes all personnel
with the privilege to logon to the MCD 5000 Deskset and gain access to radios.
6802987C96-A
July 2011
Technician Users
Technician Users
The Technician users are differentiated by their point of access to the system. There are two types of
Technician users: The ACP Technician that configures the System parameters, e.g. resource groups,
and the second Technician user type that configures each device of the system.
ACP Technicians.
The ACP Technician user type configures the MCD 5000 Deskset System from the ACP, when
the OMC Server is in use.
There are three System level ACP Technician user types:
Technician 1: not allowed to handle users, regions, resource groups,

or software downloading.
Technician 2: not allowed to handle users, regions, or resource groups.
Technician 3: a super user that is allowed all privileges including OMC

control, and software downloading.
Technician users
The Technician user uses the MCD 5000 Deskset/MCD 5000 RGU Configuration Tool. In
addition, the Technician can retrieve and manage MCD 5000 Deskset/MCD 5000 RGU log data
by either connecting to the devices serial MMI port or remotely via SSH client connection.
System Logical Deployment Design

The MCD 5000 Deskset System supports large hierarchy organization deployments. Up to four hierarchy
levels are supported. These levels are named: State, Region, County, and PSAP Site. In addition,
the MCD 5000 Deskset System supports a cross-organization property classification called Agency.
These hierarchy levels and cross-organizational classification can be configured and set during MCD
5000 Deskset System installation or modified during maintenance time window. A correct logical
MCD 5000 Deskset System design, will provide an efficient and easy access to system resources, to
set MCD 5000 Deskset users permissions, and to system graphical display.
System Logical Design Principles

It is obligatory to use all the MCD 5000 Deskset System possible hierarchy levels when configuring
the MCD 5000 Desksets and/or MCD 5000 RGUs for a PSAP. When setting up the hierarchy levels it
is required to take into account the maximum number of the levels entities per a higher entity level as
appear in Table 1-1. For example, when a hundred of MCD 5000 Desksets need to be configured per
6802987C96-A
July 2011
1-5
Example of a Large MCD 5000 Deskset System logic design
one PSAP location, then at least five logical PSAP entities would need to be configured. Each PSAP
Site can be located under the systems Counties. It is not obligatory to define the property of Agency
per resource, though it can be used as a cross-organization classification property.
Table 1-1 Maximum Entities Per Each Hierarchy Level
Maximum number of MCD 5000

Desksets and MCD 5000 RGUs per
PSAP Site
20
Maximum Number of PSAPs per

County
40
Maximum Number of Counties per

Region
40
Maximum Number of Regions per State
20
Example of a Large MCD 5000 Deskset System logic design

A commercial customer is deploying a MCD 5000 Deskset System in five different locations:
Companys administration Control Center
North area Regional Control Center
South area Regional Control Center
North area Transmit/ Receive Radio site
South area Transmit/ Receive Radio site
This commercial customer has several organizations that are concurrently utilizing the MCD 5000 Deskset System:
Distributors MCD 5000 Deskset center
Administrators MCD 5000 Deskset center
Emergencys MCD 5000 Deskset center
This customer would organize the MCD 5000 Deskset System resources in accordance with Figure 1-2.
1-6
6802987C96-A
July 2011
Resources and Identifications
Figure 1-2 MCD 5000 Deskset System Resources Organization Example
Radio1 of Admin Transmit/Receive Radio Site 1 is one resource under MCD 5000 RGU. While
configuring the resources, the user can allocate the Radios and/or the Desksets to an Agency.
For example, MCD 5000 Deskset 1 and MCD 5000 Deskset 2 can be set to belong to the
Distributors MCD 5000 Deskset center which represents a Logical hierarchy of Agency.
Resources and Identifications

A resource in the system is an end-point that an MCD 5000 Deskset user can be connected to. A
resource can be a certain radio, connected to a certain MCD 5000 RGU radio port or a certain MCD
5000 Deskset position. Each resource in the system has a unique identity. A resource is initially
configured in the system database using the Configuration Tool (CT). Once configured, the MCD 5000
Deskset resource can be assigned to one or more Access Control Groups. The Access Control Group
mechanism allows a system administrator to control the access to a Radio resource. See "MCD 5000
Deskset Authentication: Radio Access Permissions" on page 1-23 for additional details.
The resources in the MCD 5000 Deskset System are Radios and MCD 5000 Desksets.
6802987C96-A
July 2011
1-7
MCD 5000 Deskset System with OMC Topology
Radios: Each Radio has configured administrator-given alpha-numeric identifiers:
Radio Name
Radio Type
Radio Location
Radio Agency
RPDFL ID
This is an internal system identifier in use by the software; the RPDFL

ID is not presented to the MCD 5000 Deskset user.
MCD 5000 Deskset: An MCD 5000 Deskset has a configured administrator-given alpha-numeric identifier:
MCD 5000 Name
MCD 5000 Deskset location
MCD 5000 Deskset agency
RPDFL ID
This is an internal system identifier in use by the software; the RPDFL

ID is not presented to the MCD 5000 Deskset user.
MCD 5000 Deskset System with OMC Topology
The general MCD 5000 Deskset System is depicted in Figure 1-3.
1-8
6802987C96-A
July 2011
MCD 5000 Deskset System Capacities
Figure 1-3 MCD 5000 Deskset System Topology
"M", "N" and "X" represent the number of MCD 5000 Deskset sites, number of MCD
5000 RGU sites and number of MCD 5000 Desksets in a site.
As can be seen in the layout, Firewall is an optional add-on to the system that can be used to
protect the systems servers. For the list of ports to configure in the Firewall, see Appendix B.
MCD 5000 Deskset System Capacities

The MCD 5000 Deskset System capacities are specified in Table 1-2 below.
Table 1-2 MCD 5000 Deskset System Capacities
MCD 5000 Deskset System
Capacities
Maximum # of Radio Resources
512
Maximum # of MCD 5000 Radio

Gateway Units (RGUs)
128
Maximum # of Radios per MCD 5000

Radio Gateway Unit (RGU)
6802987C96-A
Capacity in
Maximum # of MCD 5000 Desksets
100
Maximum # of Users per MCD 5000

Deskset
1000
July 2011
Notes
See note 1 below.
1-9
Table 1-2
MCD 5000 Deskset System Capacities (Continued)

Capacities
Capacity in
Maximum # of Users per MCD 5000

Deskset System
1000
Maximum # of IRC Proxy MCD 5000

Desksets in a system (can have all
connected to the same radio or all
connected to different radios)
10
Maximum # of groups for each

resource/user
20
Notes
See note 2 below.
1.
A system with OMC has central management capability; thus all of the 1000 users can log
in to any MCD 5000 Deskset in the system, if configured for access in the OMC.
2.
The total number of MCD 5000 Desksets and IRC Proxy MCD 5000 Desksets in an MCD
5000 Deskset System cannot exceed the maximum number of MCD 5000 Desksets (100).

In an MCD 5000 Deskset System with OMC, multiple sites and MCD 5000 RGU/
MCD 5000 Desksets can be deployed in parallel.
This topology is applicable for deployments where the customer seeks a central management
tool, to operate, maintain, provision, and control the MCD 5000 Desksets and MCD
5000 RGUs; it provides an improved IA solution.
Talkpath Capabilities
This section discusses the talkpath capabilities of the system.
1-10
6802987C96-A
July 2011
5000 Deskset to Single Radio Talkpath (over Cable Connection)
MCD
MCD 5000 Deskset to Single Radio Talkpath (over Cable

Connection)
An MCD 5000 Deskset to Radio talkpath over cable connection includes Analog payload transmission
and reception, and exchanging of control and data. The control and data are dependent on the connected
radio device type. The serial connection has limited length of up to 50 feet. The connected radio might
communicate over the air with the Radio System depending on the Radio type; it can be a Conventional,
a Trunking, or MDC Radio. Figure 1-4 depicts an example of such a connection.
Figure 1-4
MCD 5000 Deskset to Radio Talkpath Over Cable Connection Example
MCD 5000 Deskset to Radio Talkpath Over IP Network

An MCD 5000 Deskset to radio talkpath in the MCD 5000 Deskset System is a direct peer-to-peer IP
connection between the MCD 5000 Deskset and the radio systems MCD 5000 RGU.
A user to radio talkpath is illustrated in Figure 1-5. The connection carries audio and PTT information from
the user to the radio system and audio plus monitoring information from the radio system to the user. The
talkpath (like all other talkpaths in the system) is dynamically established by a user (from the MCD 5000
Deskset device).
Talkpath performance and survivability: The peer-to-peer structure of the talkpath carries audio directly from
the user to the radio (and vice-versa) with no server processing in the middle. This ensures that optimal
end-to-end delay performance is achieved and that the talkpath survives as long as the IP network can provide
connectivity between the Deskset and the MCD 5000 RGUs.
Extending the survivability: A good system design would provide access to an external radio system through
two MCD 5000 RGUs at disparate locations for redundancy. This design enables a user to immediately
establish a talkpath using the redundant interface in case of a failure of the first talkpath.
6802987C96-A
July 2011
1-11
Multiple MCD 5000 Deskset to Radio - MCD 5000 RGU Multi-Talkpath Service
Figure 1-5 Deskset User to Radio Talkpath Example
Multiple MCD 5000 Deskset to Radio - MCD 5000 RGU

Multi-Talkpath Service
Up to 15 MCD 5000 Desksets can have direct peer-to-peer IP connection to a single Radio over the IP
Network. With this capability, the MCD 5000 RGU manages the communications so that all connected
MCD 5000 Desksets can listen to Received calls from the radio, can issue a Transmit through the
radio (other MCD 5000 Desksets can listen to this Transmit as well) and can converse with each other
using the Base Intercom button. Figure 1-6 depicts the topology of this connectivity. Appendix D,
"MCD 5000 Deskset Call Scenarios" summarizes the possible call scenarios.
When the required number of MCD 5000 Desksets to be connected exceeds 15, then an IRC Proxy
configuration needs to be set (see "MCD 5000 Deskset to Radio through IRC Proxy Talkpath").
Figure 1-6 Multi- MCD 5000 Desksets to Radio - MCD 5000 RGU Multi-Talkpath Service
1-12
6802987C96-A
July 2011
MCD 5000 Deskset to Radio through IRC Proxy Talkpath
Base Intercom allows all MCD 5000 Desksets, connected to the same Radio (and MCD 5000
RGU), to communicate among themselves, without disturbing field users, in a Half Duplex mode,
and monitor each other without keying the connected Radio Channel. The MCD 5000 Deskset
operator can see the Talker-ID on the Deskset GUI. By pressing the Base Intercom button on the
MCD 5000 Deskset, the operators voice is sent to all the MCD 5000 Desksets attached to the
Radio. The Base Intercom state is active as long as the operator presses the Base Intercom button.
MCD 5000 Deskset to Radio through IRC Proxy Talkpath

The IRC Proxy needs to be deployed in a many to one, or many to many deployment, whenever the customer
requires more than 15 MCD 5000 Desksets to be connected to a same Radio resource. Figure 1-7 provides an
example of a deployment with audio and control head distribution to 50 MCD 5000 Desksets per radio.
Figure 1-7 MCD 5000 Deskset to Radio through IRC Proxy Talkpath Service
This connection requires a preconfigured MCD 5000 Deskset to serve as an IRC Proxy for
the Important Radio Channel to allow connection of up to hundred MCD 5000 Desksets to
a Radio while using a small amount of Network bandwidth.
A Dispatch Site is the location where the IRC Proxy and the connected MCD 5000 Desksets share
the same LAN. MCD 5000 Desksets in the Headquarters LAN have the capability of connecting
with the MCD 5000 RGU through the IRC Proxy.
The MCD 5000 Desksets to Radio through IRC Proxy Talkpaths example is illustrated
in Figure 1-7. Radio1 Proxy1 and Radio1 Proxy2 are both statically configured
to run a permanent IRC Proxy in the system.
6802987C96-A
July 2011
1-13
Talkpaths in the System
The MCD 5000 Deskset configured with IRC Proxy capability will be able to
communicate only with the Important Radio Channel.
Any MCD 5000 Deskset that is not configured with IRC Proxy, but is connected to the Dispatch
Site LAN with another MCD 5000 Deskset that is configured with IRC Proxy, is able to create
Talkpath to the IRC Radio either through the IRC Proxy or directly depending on its setup.
The MCD 5000 system administrator should ask the IP network administrator to allocate
a unique multicast IP address per each IRC Proxy in a Dispatch Site.
Talkpaths in the System

The MCD 5000 users have the following ways to create and handle talkpaths in
the system as the situation requires.
MCD 5000 Buttons and Display: This application is for the user who owns an
MCD 5000 Deskset and has full MCD 5000 Deskset System capabilities. It offers
the ability to create/delete talkpaths in the system.
ACP: This application allows the MCD 5000 Deskset System administrator to
view the Talkpaths currently set in the system..
Talkpath creation is mission-critical. Talkpaths are set within a few seconds (1- 3
sec.) following the user command.
Emergency in the System

Inbound Emergency
The MCD 5000 Deskset system supports an emergency alarm coming from a parallel MCD 5000 Deskset
or a field radio holder via the air-interface to the MCD 5000 Deskset System. This causes the MCD 5000
Desksets attached to the radio to display the emergency alarm for the user. All other MCD 5000 Desksets
attached to the radio will receive this emergency alarm. The alarm is displayed until one of the attached
users acknowledges the alarm. The acknowledge message is sent to the MCD 5000 RGU, which spreads
the acknowledge to all attached MCD 5000 Desksets. This causes all MCD 5000 Desksets to change
the display from alarm state to alarm acknowledge state. This state remains until the alarm is cleared
by one of the users. Clearing the alarm sets the MCD 5000 Desksets to normal operation.
Multiple Inbound Emergency Alarms

The MCD 5000 Deskset System is capable of handling inbound multiple alarms, coming from several
field radio holders and/or other MCD 5000 Desksets attached to the radio. Multiple alarm is set only
if each alarm initiator can be identified by ID (PTT ID). Each alarm is treated as a single alarm and
the user has to point out which alarm he is acknowledging. The same is for alarm clearing, The
MCD 5000 Deskset returns to normal only after all alarms are cleared.
1-14
6802987C96-A
July 2011
Outbound Emergency
Outbound Emergency
The MCD 5000 Deskset is equipped with a dedicated Emergency button that allows the MCD
5000 Deskset user to display an emergency alarm and by that, notify other users sharing the same
radio. By pressing the Emergency button at the top right of the MCD 5000 Deskset unit, the
user sets the outbound Emergency alarm. This outbound emergency will cause the MCD 5000
Deskset to display an indication on the MCD 5000 Deskset screen.
The alarm is sent to the MCD 5000 RGU which sends it to all attached MCD
5000 Desksets and to the attached radio.
If no radio has been selected by the MCD 5000 Deskset, the MCD 5000 Deskset will send the
alarm to a default radio (and all attached MCD 5000 Desksets) as configured by the CT.
Outbound alarm cannot be set if a user is not logged in.

The message causes the MCD 5000 Desksets attached to the radio to display the emergency alarm
for the user. The alarm is displayed until one of the attached users acknowledges the alarm. The
acknowledge message is sent to the MCD 5000 RGU, which disctirbutes the acknowledge to all
attached MCD 5000 Desksets. This causes all MCD 5000 Deskset to change the display from alarm
state to alarm acknowledge state. This state remains until the alarm is cleared by one of the users.
Clearing the alarm sets the MCD 5000 Desksets to normal operation.
Radio Alias Database

The Radio Alias Database contains a list of radio names and their corresponding Radio IDs.
This database is configured and loaded to the MCD 5000 Desksets using the CT, as described
in "Configuring the Radio Alias Database" on page 6-50.
When the radio connected to an MCD 5000 RGU receives a transmission, the MCD 5000 RGU collects the
transmitting radio's ID and sends it to the attached MCD 5000 Deskset(s). The MCD 5000 Deskset uses
the Radio Alias Database to translate the Radio IDs into a user meaningful Radio Alias. The Radio Alias
is used when displaying information to the MCD 5000 Deskset user instead of the Radio ID.
The Radio Alias Database can be one file which is loaded to all MCD 5000 Desksets and used
for all system radios. If it is a large system, the administrator can create a different file for each
MCD 5000 Deskset, containing only those radios which are relevant to each MCD 5000 Deskset.
The file capacity on each MCD 5000 Deskset is up to 4600 entries.
If the Radio ID does not appear in the MCD 5000 Deskset's Radio Alias Database, the
information is displayed using the Radio ID instead the Radio Alias.
6802987C96-A
July 2011
1-15
MCD 5000 Deskset System Deployments Architecture
MCD 5000 Deskset System Deployments Architecture
One-to-One MCD 5000 Deskset to Radio

The customer deploys a single MCD 5000 Deskset and a single Radio device. The MCD
5000 Deskset is set to connect, physically, to the Radio. Figure 1-8 depicts a one-to-one
MCD 5000 Deskset to Radio physical connection.
Figure 1-8 One-to-One MCD 5000 Deskset to Radio Physical Connection Example
Single MCD 5000 Deskset to Many Radios

The customer deploys a single MCD 5000 Deskset and multiple Radio devices. This deployment requires
one or more MCD 5000 RGUs that may be co-located with the MCD 5000 Deskset at the same site
or at remote locations. The MCD 5000 Deskset can be set to possibly connect with many Radios over
the IP Network only one Radio at a time. Figure 1-9 depicts such a system configuration.
1-16
6802987C96-A
July 2011
Many MCD 5000 to a Single Radio
Figure 1-9 Single MCD 5000 Deskset to Many Radios Example
Many MCD 5000 to a Single Radio

The customer deploys a single Radio device and Multiple Desksets possibly spread over different
locations. Figure 1-10 depicts such a system configuration. If the required number of MCD 5000
Desksets to be connected exceeds 15 then an IRC Proxy configuration needs to be set.
6802987C96-A
July 2011
1-17
Many MCD 5000 Desksets to Many Radios
Figure 1-10
Many MCD 5000 Desksets to Single Radio Example
Many MCD 5000 Desksets to Many Radios

The customer deploys many MCD 5000 Desksets and many Radio devices, all possibly spread over
multiple locations. Many MCD 5000s can be connected to many Radios over the IP Network. Each MCD
5000 is connected to only one Radio at a time; this connection is selected by the MCD 5000 Deskset
operator. Figure 1-11 depicts such a system configuration. When the required number of MCD 5000
Desksets to be connected exceeds 15, then an IRC Proxy configuration needs to be set.
1-18
6802987C96-A
July 2011
IRC Proxy Deployment
Figure 1-11 Many MCD 5000 Desksets to Many Radios Example
IRC Proxy Deployment

The IRC Proxy needs to be deployed in a many-to-one or many-to-many deployment whenever the customer
requires more than 15 MCD 5000 Desksets to be connected to a same Radio resource.
Figure 1-12 provides an example of a deployment with audio and control head distribution to 50 MCD 5000
Desksets per radio.
In this example, there is a radio site with one MCD 5000 RGU connected to four SB9600 radios and Dispatch
sites 1-15 that are stationed in different locations.
In each of the Dispatch sites 1-14 only one MCD 5000 Deskset is deployed and in site 15, more than one MCD
5000 Desksets are deployed on a LAN network, while one of the MCD 5000 Desksets which is connected
to the radio serves as an IRC Proxy - named in the figure as Radio 1 Proxy. This radio proxy distributes
over the LAN multicast the radio audio and control head information of the radio named Radio 1 for the
additional MCD 5000 Desksets.
Also seen in the layout is another proxy in Dispatch site 15, named Radio 2 Proxy This proxy
is configured as connected to Radio 2. However as displayed in the layout, currently no MCD
5000 Desksets are connected to receive Radio Proxy 2 distribution.
6802987C96-A
July 2011
1-19
Deployment in Parallel to MC3000 Units
Figure 1-12 Example of Many-to-Many System Configuration with IRC Proxy
Network elements are not shown in the figure above (e.g. routers, switches).
1.
The CT is used to initially configure the Proxy and set the Proxy connection to the radio. The
CT is also used to change the proxy connection to a different radio when necessary.
2.
The proxy implemented in the MCD 5000 Deskset serves as connection to a

single radio only, as was configured by the CT. The MCD 5000 Deskset user
will not be able to use it to connect to other radios.
Deployment in Parallel to MC3000 Units

The customer deploys an MCD 5000 solution in parallel to the existing MC3000 solution.
This deployment configuration differs from the One-to-One or Many-to-Many MCD
5000(s) to Radio(s) configurations as follows:
1-20
1.
A special cable is required for this configuration.
2.
The MCD 5000 Deskset Busy LED is active when the other MC3000
is transmitting to the radio.
6802987C96-A
July 2011
MCD 5000 Deskset in Parallel to MC3000 Units
3.
The Supervisory feature between the MCD 5000 Desksets and the MC3000s
is not supported in this type of connection (the Supervisory feature between
the MCD 5000 Desksets is still available).
4.
The MCD 5000 Deskset can listen to the outbound audio generated by the MC3000
unit (or units) attached to the same Radio. When the MCD 5000 Deskset is listening
to the outbound audio, its Busy LED is turned on.
The MCD 5000 Desksets can be connected in parallel to RCH3000 units with the same special
cables used for the MC3000 unit parallel connections to MCD 5000 Desksets/MCD 5000
RGUs. On the RCH3000 unit side, add a DB25 Female-to-Female cable adapter.
MCD 5000 Deskset in Parallel to MC3000 Units

The MCD 5000 Deskset is connected in parallel to legacy MC3000 units. A Digital Junction
Box (DJB) is connected in parallel to the MCD 5000 Deskset.
Figure 1-13 One MCD 5000 Deskset in Parallel to MC3000 Units using DJB Example
Many-to-Many MCD 5000 Desksets to Radios

In this configuration, many MCD 5000 Desksets share a single Radio along with many MC3000 Desksets.
The connection is implemented with a Digital Junction Box (DJB) installed in parallel to an MCD 5000 RGU.
6802987C96-A
July 2011
1-21
Security
Figure 1-14 Many MCD 5000 Desksets in Parallel to MC3000 Units using DJB Example
Security
The MCD 5000 uses authentication credentials in the following manner:
MCD 5000 Deskset Users Authentication

A user name and PIN, PIN length 4 to 15 digits, are required. This user name and PIN also allow Radio access
permissions. The MCD 5000 Deskset user PIN is saved in a concealed manner, and it is not displayed to an
Administrator. It is the user's responsibility to log off the MCD 5000 Deskset upon completion of usage.
For a Deployed MCD 5000 Deskset with OMC System

Verification is performed remotely using OMC Database information. The OMC checks the password
complexity upon password update by the user. Passwords must expire after 60 days. The OMC alerts
the MCD 5000 Deskset user 10 days before the password expires. Upon a password expiration date, if
the password has not been changed, the OMC forces the users to change the password.
1-22
6802987C96-A
July 2011
OMC/ACP Administrator and Technician Users Authentication
OMC/ACP Administrator and Technician Users Authentication

The ACP is the OMC user interface. This interface allows Administrators to manage the MCD 5000 Deskset
System operations (such as: configuration, provisioning, Software Load management, security management).
The ACP user is required to use the ACP login (user and password), in order to access the OMC information.
Only provisioned users are allowed to access the OMC information and manage the system. Additionally,
OMC supports a service Authorization mechanism through a provisioned user class.
For detailed description of users types, refer to "Users" on page 1-4.
In the MCD 5000 Deskset System, only the administrator and technician user classes have access to the ACP
tool. The passwords meet STIG requirements. For the password requirements, see Appendix A.
MCD 5000 Deskset Authentication: Radio Access Permissions

MCD 5000 Deskset System users are authenticated prior to being authorized to access radios in the system.
When the OMC is deployed, the system includes an Access control groups mechanism that
allows an Administrator to limit access to radios to authorized users only. If an MCD 5000
Deskset user types a user PIN incorrectly up to a configurable number of consecutive times, the
MCD 5000 Deskset will be locked for a configurable period time.
Figure 1-15 illustrates the Access control group mechanism.
6802987C96-A
July 2011
1-23
MCD 5000 Deskset System Functionaries Responsibilities
Figure 1-15 System Access Permission Group Example
MCD 5000 Deskset System Functionaries Responsibilities

Technician/Administrator
The Technician/Administrator manages access permissions and is responsible for updating the system-wide
DB table using the CT application to download to all system MCD 5000 Desksets.
1-24
6802987C96-A
July 2011
Users
Users
1.
The users are informed of their MCD 5000 Deskset username and PIN that will allow them to
log on to the MCD 5000 Deskset and gain access to radios according to their privileges.
2.
It is the user responsibility to log off the MCD 5000 Deskset station upon usage completion.
The MCD 5000 Deskset users PIN is a Numeric (digits only) password as the MCD
5000 Deskset is in Numeric state when the PIN is typed.
Technician Authentication
Configuration Tool (CT) Users Authentication

Local/remote connection of the CT to an MCD 5000 Deskset/MCD 5000 RGU will include an initial 15-char
Password, which is set in the MCD 5000 Deskset/MCD 5000 RGU at the factory.
Therefore only authorized personnel that know the Password will be able to connect with the CT to
the MCD 5000 Deskset/MCD 5000 RGU. By default, MCD 5000 Deskset/MCD 5000 RGU factory
credentials (username and password) are common to all customers. Assignment of different credentials
for a customer can be performed after shipment. Updating the factory credentials in the MCD 5000
Deskset//MCD 5000 RGU in the customer system is done using the local O&M connection.
Once the factory data is updated, the old credentials are no longer accessible. Therefore,
if the customer loses or forgets the new password, the units must be returned to
the factory for re-phasing of the FLASH memory.
It is always recommended that all MCD 5000 Desksets and MCD 5000 RGUs in a
customer deployment use the same password. The CT application is ready for this
case and will ask for the password only once in a CT session.
O&M (MMI) Users Authentication

When a technician connects with O&M (MMI) connection to an MCD 5000 RGU or to an MCD 5000
Deskset, either locally using serial connection or remotely over SSH, the technician must use the Factory
credentials authentication burned to MCD 5000 RGU/MCD 5000 Deskset in the factory.
6802987C96-A
July 2011
1-25
SFTP Users Authentication
SFTP Users Authentication

When the SFTP is used for downloading files to an MCD 5000 RGU or to an MCD 5000 Deskset,
(e.g. in Software download case), the authentication credentials in use are also the Factory credentials
burned to the MCD 5000 RGU/MCD 5000 Deskset in the factory.
Summary of Factory Credentials Authentication Cases

Factory credentials (username and passwords) are required every time an MCD 5000 CT
tries to access an MCD 5000 RGU/MCD 5000 Deskset:
On TCP port 5063 (using the Configuration Tool), either locally (10.0.0.X) or remote
Locally on O&M serial connection
Remotely over SSH (for O&M) and SFTP
The factory username and password are initially burned in the factory to all MCD 5000 RGUs/MCD
5000 Desksets. The customer will be able to change the factory credentials, using the O&M MMI. This
is available either locally using the O&M connection or remotely over SSH. Once the factory password
is updated, there is no back door capability of returning to the older password.
Once the factory password is updated, the new password is relevant to all access
methods: CT and MMI; locally and over SSH and SFTP.
Factory Password Complexity

The password must be between 4 and 15 characters, including upper case letters, lower
case letters, numbers, and special characters.
VPN Protection
Customer Owned VPN Protection: Supporting Remote Sites over VPN
Remote sites connection over customer's VPN is supported by the MCD 5000 Deskset System. In this case
Firewall/Routers are placed by the customer on the border of MCD 5000 sites, and a VPN tunnel is established
between them. MCD 5000 information is carried over the VPN tunnel, encapsulated by the Firewall/Router
on one side and de-encapsulated by the second Firewall/Router on the other side.
In this case MCD 5000 components do not take part in the encapsulation process, only the
Firewall/Routers do. From the MCD 5000 Deskset System perspective, the VPN is transparent
and adds only some delay and jitter. The system performance should remain within the IP system
performance prerequisite requirements, even when the delay and jitter is added.
1-26
6802987C96-A
July 2011
Owned VPN Protection: Supporting Remote Sites over VPN
Customer
Figure 1-16 Remote Sites Over VPN
The VPN functionality seen in the layout can also be implemented by using Motorolas CRYPTR
2 IP Encryption module for customers that manage their keys with KMF.
For more information on the CRYPTR 2 IP Encryption module, see the CRYPTR 2 datasheet on
the Motorola website or contact Motorola support.
CRYPTR 2 Security Features
AES 256 Encryption
Internet Protocol Security (IPSec) (RFC 4869)
Internet Key Exchange (IKE) v1
Tamper Protection
Key Material Erase (Zeroize) button
FIPS 140-2 Level 2
Non-CCI
CRYPTR 2 Functionality
20 Mbps throughput
QOS Support
Support for remote key management by the Motorola Key Management Facility
(KMF) and Key Variable Loader (KVL).
SNMPv3 Management Capability
Simple Configuration via USB Port & Command Prompt
Figure 1-17 illustrates a deployment scenario of MCD 5000 Remote sites over Motorola's CRYPTR 2 IP
Encryption modules.
Also as reflected in the layout, Firewalls are an optional addition to provide protection
to the servers sites when requested by customer.
6802987C96-A
July 2011
1-27
MCD 5000 Deskset Credentials
Figure 1-17
Remote Sites Over Motorolas CRYPTR 2 IP Encryption Modules
MCD 5000 Deskset Credentials

The MCD 5000 Deskset stores the following security data:
MCD 5000 Deskset application credentials
MCD 5000 Deskset factory credentials
The factory credentials are used in both the MCD 5000 Deskset and in the MCD 5000 RGU.
MCD 5000 Deskset Application Credentials

The MCD 5000 Deskset stores the Username and Password of the last 10 logged-in users. The
updating is done automatically once the user has successfully logged in.
This is used so that login service continues even for cases when the active OMC is temporarily
out-of-service, e.g. when there is a failover between the active and backup OMCs. Until the
backup OMC becomes active, the authentication of MCD 5000 Deskset users is performed locally
in the MCD 5000 Deskset, for the last 10 users who used the MCD 5000 Deskset.
MCD 5000 Deskset Factory Credentials

See "Summary of Factory Credentials Authentication Cases" on page 1-26.
1-28
6802987C96-A
July 2011
MCD 5000 RGU Credentials
MCD 5000 RGU Credentials

The MCD 5000 RGU stores the following security data:
MCD 5000 RGU factory credentials
MCD 5000 RGU Factory Credentials

See "Summary of Factory Credentials Authentication Cases" on page 1-26.
SSH
SSH is used for remote O&M (MMI) connection to the MCD 5000 RGU and to the MCD 5000 Deskset. The
MCD 5000 Deskset/MCD 5000 RGU VxWorks platform employs SSH to protect MCD 5000 Deskset/MCD
5000 RGU access. SSH is a network protocol that allows data to be exchanged using a secure channel
between two network devices (replaces Telnet). In the next release SSH will run in FIPS-140-2 mode.
SSH user authentication parameters are updated to the MCD 5000 Deskset and MCD 5000 RGU either
locally via MMI O&M connection or remotely over the SSH secured connection.
Hardening
The MCD 5000 Deskset System supports hardened Operating Systems (OS) in both the Linux
server (OMC) and in the Windows applications (ACP and CT).
Disaster Recovery
Backup and restore capabilities of the MCD 5000 Deskset System are available.
1.
OMC: The OMC Server can be provided in a warm-standby redundant configuration. The
duplicate servers operate in synchronization so that if the main one fails, the MCD 5000 system
administrator can switch to the backup unit (using manual switchover, performed on the ACP
Client PC).
In addition to the synchronization performed with a backup site, an OMC supports
a backup procedure of the OMC DB data, which is stored locally on the disk
and can be downloaded to an external device.
2.
MCD 5000 Deskset/MCD 5000 RGU: Using the CT/ACP, a backup can be performed of each
of the MCD 5000 Deskset/MCD 5000 RGU Configuration files.
When performing such a backup, data is saved locally on the CT/ACP PC/laptop and then can
be exported to external media.
See "MCD 5000 Deskset Systems Backup" on page 1-30.
In addition, each MCD 5000 Deskset and MCD 5000 RGU keeps its configuration and current
connectivity state on a non-volatile FLASH memory that allows fast recovery from power cycles.
6802987C96-A
July 2011
1-29
MCD 5000 Deskset Systems Backup
MCD 5000 Deskset Systems Backup

MCD 5000 Deskset Systems with OMC can perform a system-wide backup to the OMC DB, as well
as individual backups of each MCD 5000 RGU/MCD 5000 Deskset device.
Installation Overview
This section provides a summary of the tasks required to install and configure an MCD 5000 Deskset System
and the order in which they should be performed. Where appropriate, there are references to the parts of this
manual where you can find more detailed information. See Figure 1-1 for an overview of a sample system.
Process 1-1 How to Install an MCD 5000 Deskset System
1-30
Install the OMC Server, as described in "OMC Server Initial Installation and
Configuration" on page 3-7.
Install the MCD 5000 ACP software as described in "Installing Software on the
ACP Client PC" on page 5-4.
Install the MCD 5000 CT with OMC software, as described in the "Installing the
Configuration Tool" on page 6-1 section under Chapter 6, "Administering your
System with the Configuration Tool".
For each MCD 5000 RGU/MCD 5000 Deskset, configure the IP Address
according to your System topology. Use Procedure 6-8, "Connecting Directly to
a GU," on page 6-17 in order to connect to a GU via Internal LAN port. Change
the GU IP Address using Procedure 6-11, " Modifying a GU Configuration,"
on page 6-22, step 14.
Create a version of the System Parameters using the MCD 5000 ACP application,
as described in the MCD 5000 Deskset System Administration Control Panel
User Guide (6802987C99) in the Installing System Parameters Version in OMC
Database section. Use the following procedures: Installing a System Parameters
Version in the OMC Database, and Activating a System Parameters Version
in the OMC Database.
Add Users using the MCD 5000 ACP application, as described in the MCD
5000 Deskset System Administration Control Panel User Guide (6802987C99),
in the section entitled Adding Users.
Create Groups using the MCD 5000 ACP application, as described in the MCD
in the section entitled Configuring Resource Groups. Use the procedure entitled
Adding a Resource Group.
6802987C96-A
July 2011
Process 1-1 How to Install an MCD 5000 Deskset System (Continued)

8
Perform Unit connections:

1. Connect the cables to the MCD 5000 Deskset units as described in Procedure
4-1, "Cabling the MCD 5000 Deskset," on page 4-12.
2. Connect the MCD 5000 Deskset Peripherals as described in "Connecting
Peripheral Equipment to the MCD 5000 Deskset" on page 4-14. Use one of the
connection methods (Phone Like, Classic, Hands-free Option 1 or Hands-free
Option 2) to connect peripherals to an MCD 5000 Deskset.
3. Connect the cables to the MCD 5000 RGU units as described in Procedure
4-4, "Cabling an MCD 5000 RGU," on page 4-19.
4. Connect each of the MCD 5000 RGU units in the MCD 5000 Deskset
System to a chassis ground as described in Procedure 6-7.
Failure to connect the MCD 5000 RGU to a proper ground

may cause injury to personnel or damage to the unit.
5. Connect the customer-supplied SB9600 radios to the MCD 5000 Desksets
and MCD 5000 RGU units as described in Procedure 4-5, "Connecting a Radio to
the MCD 5000 Equipment," on page 4-21.
6802987C96-A
Add MCD 5000 Desksets and MCD 5000 RGUs to the system one by one, as
described in the MCD 5000 Deskset System Administration Control Panel User
Guide (6802987C99), in the section entitled Adding a GU. Use the procedure
entitled Adding a GU.
10
Update the system parameters for all system GUs, as described in the MCD
in the section entitled Downloading and Activating System Parameters. Use
the procedure entitled Downloading and Activating System Parameter Versions
onto GUs.
July 2011
1-31
1-32
6802987C96-A
July 2011
Chapter
2
General Hardware Installation Practices
Effective installation is important for good performance in a communication system. A

pre-installation site review and evaluation can eliminate any potential equipment installation
problems. This chapter provides an installation overview and describes important considerations.
These considerations include: safety, site facilities, lighting, grounding, and lightning protection,
which you should consider when installing or modifying the system.
This chapter covers the following topics:
"General Safety Precautions" on page 2-1.
"Site Preparation" on page 2-4.
"General Installation Guidelines" on page 2-6.
"FCC Requirements" on page 2-9.
"Electromagnetic Safety Requirements" on page 2-9.
"Installation and Configuration Tools" on page 2-12.
General Safety Precautions
Observe the following general safety precautions during all phases of operation, service, and repair
of the equipment described in this manual. These safety precautions represent warnings of dangers
of which Motorola is aware. Follow these warnings and all other safety precautions necessary
for the safe operation of the equipment in the operating environment.
The installation process requires preparation and knowledge of the site before installation begins.
Review installation procedures and precautions in Standards and Guidelines for Communications
Sites (R56) (68P81089E50) before performing any site or component installation.
6802987C96-A
July 2011
2-1
General Safety Precautions
Compliance with FCC guidelines for human exposure to Electromagnetic Energy

(EME) at Transmitter Antenna sites generally requires that personnel working
at a site shall be aware of the potential for exposure to EME and can exercise
control of exposure by appropriate means, such as adhering to warning sign
instructions, using standard operating procedures (work practices), wearing
personal protective equipment, or limiting the duration of exposure. For more
details and specific guidelines, see Appendix A of the R56 Standards and
Guidelines for Communications Sites (68P81089E50) manual.
You must follow all applicable safety procedures, such as Occupational, Safety, and Health Administration
(OSHA) requirements, National Electrical Code (NEC) requirements, local code requirements, and safe
working practices. You should also use your own good judgment in performing the installation.
The general safety precautions include the following:
2-2
Read and follow all warning notices and instructions marked on the product or
included in this manual before installing, servicing, or operating the equipment.
Retain these safety instructions for future reference.
Refer to the appropriate section of the product service manual for additional pertinent safety information.
Do not install substitute parts or perform any unauthorized modifications of equipment.

Unauthorized modifications or substitute parts may introduce additional hazards.
Beware of live circuits if you are performing a troubleshooting procedure

that requires having the power on.
Do not operate the radio transmitters unless all RF connectors are secure
and all connectors are properly terminated.
Do not store combustible material in or near the equipment racks. The combination of
combustible material, heat, and electricity increases the risk of fire.
Verify that all MCD 5000 RGUs equipment is properly grounded, in accordance
with the Standards and Guidelines for Communications Sites (R56) (68P81089E50)
and specified installation instructions for safe operation.
Do not block or cover any ventilation slots or openings. These ventilation slots are used to
remove heat from the equipment, thereby reducing overheating problems.
Only qualified technicians who are familiar with similar electronic equipment should
service the MCD 5000 Deskset System equipment.
Turn off all power to the equipment and wait until it is sufficiently cool before touching or
working on it. Some components can become extremely hot during operation.
Work out a communications routine during certain higher risk procedures. The on-site
technician updates management or safety personnel continually about the procedure's
progress. This makes the dispatching easier if something goes wrong.
6802987C96-A
July 2011
Maintenance Requiring Two People
Maintenance Requiring Two People

Identify maintenance actions that may require two people. Use two people when:
A repair has the risk of injury that would require one person to provide first aid or call for
emergency support. For example, working around high voltage sources can result in injuries to
one person that would require a second person to remove the power and call for emergency aid.
A repair requires removing and replacing a system component from its rack. Use
the National Institute of Occupational Safety and Health (NIOSH) lifting equation
to determine whether the task requires one or two people.
Sometimes working alone is unavoidable. In situations where you have to work alone at a site:
Let your dispatcher know where you are working.
Let others know when you expect to arrive and when you expect to return.
Hazardous Materials
Hazardous materials (HAZMAT) include all materials deemed hazardous under applicable
local, state and national statutes and regulations. Examples include: caustics, acids, flammable
materials, explosives, and bio-hazards, and other.
This information is provided as an aid for the planning of sites. Compliance with all local, state,
and national statutes and regulations concerning the storage, handling, and use of hazardous
materials are the sole responsibility of the customer and associated agents.
Seismically Active Areas

Sites in seismically active areas may require additional bracing of the equipment cabinets or racks.
This manual does not contain specific procedures related to seismic bracing. For further information, see the
following chapters in the Standards and Guidelines for Communication Sites (R56) (68P81089E50):
6802987C96-A
July 2011
Chapter 2, Safety Summary
Chapter 5, Communications Site Building Design and Installation
Chapter 11, Equipment Installation
2-3
Site Preparation
Site Preparation
Performing the activities listed in Table 2-1 ensures proper site preparation. It also references specific chapters
in the Standards and Guidelines for Communication Sites (R56) (68P81089E50) manual for more information.
Table 2-1
Site Preparation
Activity
Review the site plan
Description
Prevents potential
on-site and off-site
interference by local
trunked systems.
Standards and Guidelines for

Communication Sites (R56)
Chapter Reference
Chapter 4, Site Design and
Development
Minimizes cable lengths

between RF equipment.
Determines the
location of TELECOM
equipment.
Determine site access security
Outlines site access and

security.
Chapter 3, Site Acquisition

Chapter 4, Site Design and
Development
Review safety considerations
Review the site's telephone

service
2-4
Outlines general, installation,

and environmental safety
guidelines and requirements,
as well as OSHA-related
considerations.
Ensures options and functions
of two-way communications
for personal safety and
maintenance.
Chapter 2, Safety Summary

Chapter 5, Communications Bite
Building Design and Installation
Chapter 3, Site Acquisition
6802987C96-A
July 2011
Table 2-1
Security Considerations
Site Preparation (Continued)

Activity
Description
Review grounding specifications
Ensures that the site meets or

exceeds the standards in the
(68P81089E50).
Review the site's power source
Provides grounding, power

sources, and surge protection.

Chapter Reference
Chapter 6, External Grounding
Chapter 7, Internal Ground
Chapter 8, Power Sources

Chapter 9, Transient Voltage
Surge Suppression
Security Considerations
The structures that contain the MCD 5000 Deskset System components should meet the
requirements of all local building codes and any relevant regulations.
For security purposes, the building should have tamper-proof locks installed on the external doors.
Environmental Considerations
A major site-design consideration is maintaining an environment in which the equipment can operate
efficiently. A properly designed Heating, Ventilation, and Air Conditioning (HVAC) system provides
the proper environmental conditions for the communications equipment.
Each manufacturer specifies an operating or ambient temperature for their equipment, defined as follows:
Operating temperature refers to the temperature within the equipment case with
the equipment operating at a given capacity or load.
Ambient temperature refers to the internal ambient temperature at the site. It is typically
measured 152.4 cm (5 ft) above the floor in the center of an adjacent aisle.
The structure that contains the MCD 5000 Deskset System components must be able to
resist extreme weather conditions as described below:
Keep the MCD 5000 Deskset and the MCD 5000 RGU in an interior site environment.
The site should be able to maintain this temperature within the MCD 5000
Deskset or the MCD 5000 RGU operating temperature range as specified and
according to the units installed within the site.
The MCD 5000 Deskset System components are not approved for outdoor use.
6802987C96-A
July 2011
2-5
Surge Protection
For the specific environmental requirements for the equipment in an MCD 5000 Deskset System,
including temperature and humidity parameters, see Table 2-2.
The Operating Temperature in this chart is the internal ambient temperature at the site. You
can use a thermometer to monitor the temperature of the equipment cover.
Table 2-2 Operating and Environmental Specifications
Component
Operating Temperature
Relative Humidity
MCD 5000 Deskset
0 C to 50 C (32 F to 122 F)
10% to 90%
MCD 5000 RGU
30 C to 60 C (22 F to 140 F)
5% to 95%
Using the MCD 5000 Deskset Handset under extreme temperature can cause
injuries. Verify that the Handset temperature as approximately 27 C before use.
Surge Protection
Proper surge protection is required for all power inputs to prevent potential damage to site equipment.
General Installation Guidelines
This section provides guidelines for insuring quality of the installation. Review these guidelines before
unpacking and installing the system. This section contains information about:
"Equipment Inspection and Inventory" on page 2-7.
"Placement Recommendations" on page 2-7.
"Spacing Requirements" on page 2-7.
"Grounding" on page 2-8.
"AC Power" on page 2-8.
See the installation information in the Standards and Guidelines for Communication
Sites (R56) (68P81089E50) manual for more details.
2-6
6802987C96-A
July 2011
Equipment Inspection and Inventory
Equipment Inspection and Inventory

Motorola recommends the following:
Taking an inventory of all equipment to ensure that the order is complete.
Inspecting all equipment and accessories carefully to verify that they arrived in good condition.
Reporting any damaged or missing items promptly to the Motorola representative.
Placement Recommendations
Follow these recommendations for placing equipment at a site:
Place each unit on a firm, and stable surface.
Place the MCD 5000 RGU on a level surface. Place the MCD 5000 Deskset on a level
surface or wall mount it using the FHN7394 Wall-Mount kit.
Use strain relief when installing and positioning cables and cords to help
ensure that no interruption of service occurs.
Service personnel require access to both the front and rear of the MCD 5000 RGU.
Locate the system in an area that is free of dust, smoke, pouring or splitting
water, and Electrostatic Discharge (ESD).
Ground the MCD 5000 RGU according to the Standards and Guidelines for
Communication Sites (R56) (68P81089E50) manual.
Spacing Requirements
Proper spacing of equipment is essential for efficient use of the room area, ease of maintenance,
and safety of personnel. Spacing requirements have been established to meet the standards
of both the National Fire Protection Associations (NFPA) Code and the American Society of
Heating, Refrigerating, and Air Conditioning Engineers (ASHRAE).
See the Standards and Guidelines for Communication Sites (R56) (68P81089E50) manual for details on the space requirements.
You must also adhere to any local regulations that apply to the installation. If
the Standards and Guidelines for Communication Sites (R56) manual and your
local regulations conflict, follow the latter.
6802987C96-A
July 2011
2-7
Grounding
Grounding
The MCD 5000 RGU include 2 grounding bolts located at the back panel. Connect either of
them to the site ground using the supplied FKN8704 grounding cable.
See the Standards and Guidelines for Communication Sites (R56) (68P81089E50) manual for
more information on proper bonding and grounding at a site.
AC Power
The Standards and Guidelines for Communication Sites (R56) (68P81089E50) manual
defines the guidelines and requirements for equipment that requires AC power input. Some
of the guidelines and requirements are as follows:
2-8
All AC power equipment and electrical components must conform to proper electrical codes.
Place a surge protector, designed to protect equipment systems from a 120/240 V service
and load center on the power feed ahead of all individual load center circuit breakers.
Select a surge protector based on the susceptibility of the equipment powered by the
electrical service with a margin provided for locally generated disturbances.
6802987C96-A
July 2011
FCC Requirements
FCC Requirements
This section contains information about:
"Equipment Compliance" on page 2-9.
Equipment Compliance
Motorola has tested the MCD 5000 Deskset System equipment and found it compliant with the limits for a
Class A digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable
protection against harmful interference when the equipment is operated in a commercial environment.
The radios which are connected to the MCD 5000 Desksets and MCD 5000 RGUs
generate, use, and can radiate radio frequency energy. If not installed properly and used in
accordance with the instruction manuals, the radios may cause harmful interference to radio
communications. Operation of this equipment in a residential area is likely to cause harmful
interference, in which case you are required to correct the interference.
Electromagnetic Safety Requirements
This section describes information you need to know about working with electromagnetic energy. It includes sections on:
"OSHA Related Safety Requirements (United States)" on page 2-9
"Compliance with Local Regulations" on page 2-10
"References" on page 2-10
OSHA Related Safety Requirements (United States)

The United States Department of Labor, through the provisions of the Occupational Safety and Health
Act (OSHA) of 1970, has established an electromagnetic energy safety standard that applies to the use
of this equipment. Proper use of this equipment results in exposure below the OSHA limit.
6802987C96-A
July 2011
2-9
Compliance with Local Regulations
Compliance with Local Regulations

Compliance with the local regulations of the final installation should be assessed and site specific
characteristics, such as site accessibility of occupational personnel (controlled environment) and general public
(uncontrolled environment) should be taken into account. Only trained technicians should install and maintain
this equipment. Licensees of the FCC using this equipment are responsible for ensuring that its installation and
operation comply with FCC regulations Part 1 section 1.1310 as published in title 47 code of federal regulations.
Whether a given installation meets FCC limits for human exposure to radio frequency radiation
may depend on frequency fields from other equipment, the effects of which may add to the level
of exposure. Accordingly, the overall exposure is affected by radio frequency generating facilities
that exist at the time when the licensee's equipment is being installed or even by equipment
installed later. Therefore, the effect of any such facilities must be considered in site selection and
in determining whether a particular installation meets the FCC requirements.
FCC OET Bulletin 65 provides materials to assist in determining if a given facility is compliant with
the human exposure to RF radiation limits. Determining the compliance of transmitter sites of various
complexities may be accomplished by means of computational methods.
Guidelines
Observe the following general guidelines when working in or around radio MCD 5000 RGU sites:
Ensure that all personnel have undergone electromagnetic energy awareness training.
Ensure that all personnel entering the site are authorized to do so.
Follow all posted signs.
Notify owners and disable appropriate transmitters before working on

attached MCD 5000 RGUs.
Maintain a minimum of 1 m (approximately 3 ft) clearance between the

hardware and all antennas.
Do not stop in front of antennas.
Use personal RF monitors while working near antennas.
Do not operate transmitters without shields during normal operation.
Do not operate base radio antennas in equipment rooms.
Installations Outside the United States

For installations outside of the United States, consult the applicable governing body and standards for RF
energy human exposure requirements and take the necessary steps for compliance with local regulations.
References
For more complex sites, direct measurement of the power density may be expedient. Additional information
on electromagnetic exposure is contained in the Standards and Guidelines for Communications Sites (R56)
(68P81089E50) manual. Motorola urges persons responsible for installing this equipment to consult the listed
reference material to assist in determining whether a given installation complies with the applicable limits:
2-10
6802987C96-A
July 2011
References
TIA/EIA TSB92: Report on EME Evaluation for RF Cabinet Emissions Under FCC MPE
Guidelines, available from Global Engineering Documents at http://global.ihs.com
FCC OET Bulletin 65: Evaluating Compliance with FCC Guidelines for Human Exposure
to Radio Frequency Electromagnetic Fields at http://www.fcc.gov/oet/rfsafety/
Motorola web pages does not include Global Engineering Documents or the
Federal Communications Commission (FCC) sites. Motorola has no control over
any fees that these organizations may charge for their documents.
6802987C96-A
July 2011
IEEE Recommended Practice for the Measure of Potentially Hazardous Electromagnetic

Fields -- RF and Microwave, IEEE Std C95.3-1991, Publication Sales, 445 Hoes
Lane, P.O. Box 1331, Piscataway, NJ 08855-1331
IEEE Standard for Safety Levels with Respect to Human Exposure to Radio Frequency
Electromagnetic Fields, 3 kHz to 300 GHz, IEEE C95.1-1991, Publication Sales,
445 Hoes Lane, P.O. Box 1331, Piscataway, NJ 08855-1331
2-11
Installation and Configuration Tools
Installation and Configuration Tools
This section lists the different types of tools needed to install, configure, and service the equipment in an
MCD 5000 site. If you need more information about obtaining any of the equipment and tools listed, please
contact your Motorola System Support Center (see "Motorola Support Centers" on page J-1).
General Tools
The following is a list of general tools recommended for installing, configuring, and
servicing equipment at an MCD 5000 RGU site:
2-12
150 MHz oscilloscope
Digital multimeter (DMM)
RJ45-to-RJ45 one-to-one cable
DB9 to RJ45 Adaptor
MODAPT RJ45 breakout box
Remote RJ45 cable tester (1200 ft length maximum)
PC cable tester with RJ45, DB9 pin connectors
ESD field service kit
Amprobe Instruments GP-1 Earth Tester
AEMC 3730 clamp-on ground resistance tester
3/8 inch open-end spanner (for tightening the ground cable to the GU)
Megger tester (for determining AC resistance between a GU and a non-trivial reference ground)
Configuration Tool software (to configure GUs with the technician PC)
Ethernet cable (to connect the technician PC to the local LAN)
Wire cutter
Adjustable wrench
Pliers or crimper
Tie-wraps
6802987C96-A
July 2011
Site-Specific Information
Site-Specific Information
If your system was staged by the Motorola Center for Customer Solution Integration (CCSI), CCSI
created a set of staging build books. These books may include some of the following:
Site design drawings that show the location of all components.
Cable matrix in a table format that shows each cable and its connections.
Interconnect wiring diagrams that show cable connections between devices.
Preprogrammed parameters of each site component.
Templates used to program each device.
All firmware and software revisions of each site component.
Test data from each device that requires operational verification.
Optimization requirements and settings of each electrical path.
Acceptance Test Procedures for the site components. The Acceptance Test Procedures
are in the System Installation Guide for your system.
You must maintain this site-specific information to reflect the current site
configuration and layout of the system.
MCD 5000 System Training
MCD 5000 System training slides are available from Motorola. Contact your Motorola
Support Center for further information".
6802987C96-A
July 2011
2-13
MCD 5000 System Training
2-14
6802987C96-A
July 2011
Chapter
3
OMC Server - Installation, Configuration,
and Maintenance
This chapter provides detailed information about the MCD 5000 Deskset System Operations Management
Center (OMC), including installation and configuration instructions. This chapter contains the following topics:
"Overview of Operations Management Center Server" on page 3-1
"OMC Server Initial Installation and Configuration" on page 3-7
"Advanced Maintenance for OMC Server" on page 3-20
Overview of Operations Management Center Server
The following information is provided as an overview of the Operations Management Center

(OMC) servers used in MCD 5000 Deskset Systems:
"OMC Server Functional Description" on page 3-1.
"OMC Server Physical Description" on page 3-4.
OMC Server Functional Description

The OMC Server is a central location where all the system users and resources (administrators, dispatchers,
radios) are registered, and where system-wide information (active talkpaths, security parameters, and so on)
is stored. The OMC Server is responsible for the operation, maintenance, provisioning, and control of the
MCD 5000 RGU and the MCD 5000 Deskset. The server runs on the Red Hat Linux operating system. A
user level interface to the OMC is provided by the Administrator Control Panel (ACP) Client PC, and the
maintenance interface to the OMC is provided by a command line administration tool.
6802987C96-A
July 2011
3-1
System Capacity
Motorola recommends the purchase of this server through Motorola because configuration
must be done at the factory. Motorola will not support other servers.
Because of its importance to interoperability operation, the OMC Server can be provided in a
hot-standby redundant configuration. The duplicate servers operate in synchronization so that if
the main one fails, the MCD 5000 Deskset System administrator can switch to the backup unit
(this is a manual switchover performed on the ACP Client PC).
Although the OMC Server is the main server, it is not a single-point of failure in
the system for the following reasons:
All system active connections are peer-to-peer (P2P) IP connections and continue to
operate even when the primary and backup OMC Servers are offline.
Intercom and radio connections are initiated by the MCD 5000 Desksets. Therefore,
new intercom and radio connections may be established even in the absence of the
OMC Server. (However, any system-wide information that is updated while the OMC
Server is down is not provided to the dispatchers, who must rely on the existing
system-wide information stored in their dispatch consoles.
The OMC Server interacts with the MCD 5000 RGU to:
Download new software versions.
Collect activity information.
Handle asynchronous alarms and event reports.
Command the MCD 5000 RGU to set up/disconnect audio talkpaths for
radio switchover purposes.
Configure the radio parameters connected to the MCD 5000 RGU (radio type,
audio and RF settings, channel settings, and others).
The OMC Server interacts with the MCD 5000 Deskset to:
Download new software versions.
Authenticate the MCD 5000 Deskset operator.
Set the MCD 5000 Deskset with the PTT priority assigned to its operator. The
PTT priority is an attribute of the operator and is assigned by the OMC right after
the user login. Eight PTT priority levels are supported.
Handle asynchronous alarms and events.
System Capacity
The following lists the maximum system capacity (see "System Logical Deployment Design" on page 1-5).
3-2
Maximum number of devices (MCD 5000 RGUs, MCD 5000 Desksets) in a PSAP: 20
Maximum number of PSAPs in a county: 40
Maximum number of counties in a region: 40
Maximum number of regions in a state: 30
6802987C96-A
July 2011
OMC Server Logical Architecture
OMC Server Logical Architecture

The OMC Server logical architecture has three layers:
Interface Layer: This layer consists of all OMC interface packages, including:
OMC Control Interface: Used by the OMC Server to control the operation of MCD
5000 Desksets and MCD 5000 RGUs across the MCD 5000 Deskset System.
OMC Client Link: The OMC Server provides an interface to the Administrator Control
Panel (ACP) which allows administrators to view and modify system information, the
command line administration tool which provides a way for technicians to configure,
maintain, monitor, and troubleshoot from the Linux command prompt, and the
Configuration Tool which provides a way to configure the MCD 5000 Deskset and MCD
5000 RGU, and perform audio monitoring tasks at the site where the GU is located.
OMC Backup Interface: Used to synchronize the main and backup databases, allowing
smooth switchover between the primary and backup OMC sites in case of OMC Server
failure. This interface is based on standard multi-master replication protocols available
for the database with minimal overhead of this link on the OMC application layer.
Application Layer: This layer consists of all MCD 5000 Deskset System functionality driven
by user requests and events. The application layer includes the following subsystems:
Authorization Authentication Accounting (AAA): It supports user authorization and

authentication to the system upon user login, and supports user authorization upon any
user service request. The AAA uses the user profile in the database for these functions.
Connection Management (CMM): It provides all connection-related functionality

including connection setup, connection monitoring, connection fault management,
connection garbage collection, and connection release.
OMC Redundancy Management: It guarantees highOMC Server availability,

based on a dual redundant warm-backup OMC site.
Database Layer: This layer contains all the system information, including:
Users Information Base: It provides a centralized users directory, including

user profile and privilege information.
Managed Information Base: It contains information about MCD

5000 Deskset System resources.
Connection Information Base: It contains the connection specification

data for each active voice connection.
Fault Log: It contains MCD 5000 Deskset System fault monitoring.
Software Loads: It contains a copy of the current gateway unit software load
and a standby MCD 5000 Deskset software load.
The database layer also includes:
6802987C96-A
July 2011
Data regarding history of connections (date and time the connection

started/ended and by whom)
System alarms
Data about the system parameters
Information about the limitations implied in the system and current settings
3-3
OMC Server Physical Description

The OMC Server operates on the Hewlett Packard ProLiant server. The ProLiant is a versatile,
high-performance server that provides industry leading management and serviceability.
Table 3-1 Operating and Environmental Specifications for the OMC Server (Hewlett Packard
ProLiant server)
Details
Specification
3-4
Processor
Intel
Xeon
Base Memory
HP 2GB PC3-10600E 2x1GB.
Operating System
Red Hat Enterprise Linux ES 5.3, one year subscription

with 3 incidents support on CD-ROM
Hard Disk Controller
Integrated 6-port SATA (4-ports for hard disks)
Hard Drives
Quantity 1 - 250GB Total Raw Disk Space (1x HP

250GB 3G SATA 7200RPM Non-Hot Plug ETY HDD)
CD-ROM/DVD DVD RW
HP 16x Half-height SATA DVD-RW Optical Drive

(Mfg Part #: 447328-B21)
Network Interface Card (NIC)
1 Embedded HP NC107i Single Port Gigabit NIC
Power Supply
HP 300W HNP Power Supply
System Unit Dimensions
(HxWxD feet) 14.38 x 6.9 x 16.8 in (36.52 x 17.5 x

42.6 cm)
Weight
Minimum: 25.13 lb (11.4 kg) Maximum: 30.53 lb

(13.85 kg)
Input Requirements
Rated Line Voltage: 90 to 132 VAC, 180 to 264 VAC

Rated Input Current: 5 A (at 100 VAC), 2.5 A (at 200
VAC)
Rated Input Frequency: 47 to 63 Hz
Rated Input Power: 400 W (at 100 VAC), 400 W (at
200 VAC)
Temperature Range
Operating: 10 to 35C (50 to 95F).

Non-operating: -35 to 65C (-31 to 149F).
Relative Humidity
Operating: 10% to 90% relative humidity (Rh),

28C (82.4F) maximum wet bulb temperature,
non-condensing.
Non-operating: 10% to 95% relative humidity (Rh),
38.7C (101.7F) maximum wet bulb temperature,
non-condensing.
Acoustic Noise
Idle:
L WAd (BELS): 4.32
L pAm (dBA): 24.9
Operating:
L WAd (BELS): 4.41
L pAm (dBA): 25
processor X3430 (2.40 GHz, 8MB cache,

95W, 1333MHz) Quad-Core.
6802987C96-A
July 2011
Figure 3-1 OMC Server - Front View
6802987C96-A
July 2011
3-5
Figure 3-2 OMC Server - Rear View
Table 3-2 OMC Server Rear View Connectors

No.
3-6
Description
1.
Kensington lock notch
2.
Cable lock provision notch
3.
Access panel thumbscrew
4.
Expansion slot cover retainer thumb screw
5.
Expansion slot cover
6.
Expansion slot 1
7.
Expansion slot 2
8.
Expansion slot 3
9.
Expansion slot 4
10.
Management NIC port (RJ45)
11.
Video port
12.
Serial port
13.
USB ports
14.
Embedded NIC port (RJ45)
15.
PS/2 keyboard port
6802987C96-A
July 2011
Table 3-2
OMC Server Initial Installation and Configuration
OMC Server Rear View Connectors (Continued)
No.
Description
16.
PS/2 mouse port
17.
Power supply cable socket
OMC Server Initial Installation and Configuration
General information on hardware installation is provided in Chapter 2, "General Hardware Installation

Practices".
The OMC server can be physically located at a separate Operations Management Center
(OMC) site or at any site of the system.
The OMC server OS is installed, configured and tested before shipment from the factory. The
MCD 5000 OMC server OS Installation CDs (RHEL 5.3 KICK START,RED HAT ENTERPRISE
5.3) are provided with the server and can be used to reinstall the server OS if needed. Perform
the following procedure in order to install the OMC server OS.
"Installing MCD 5000 OMC Server OS " on page 3-8.
The OMC server Application installation is provided on an additional CD (OMC SERVER APPLICATION).
Perform the following procedure in order to install the OMC server application.
"Installing MCD 5000 OMC Server Application" on page 3-11.
Some settings are specific to the customer system and cannot be set until the servers are installed in the field.
Perform the following procedures to configure the OMC server:
"Changing the Root Account Password" on page 3-12.
"Viewing/Configuring Network Parameters " on page 3-13.
"Configuring MCD 5000 Deskset System OMC Servers IP Addresses" on page 3-15.
"Configuring the Time of Day, Date or Time Zone " on page 3-17
"Configuring NTP Client" on page 3-18
"Configuring the System Geographical Area" on page 3-19
For configuration functions that are not part of the initial installation and configuration, see
"Advanced Maintenance for OMC Server" on page 3-20.
6802987C96-A
July 2011
3-7
Installing MCD 5000 OMC Server OS

Follow Procedure 3-1 to install the MCD 5000 OMC server OS.
The Linux password must conform to the following rules:

Must be at least nine characters long.
Must contain at least two uppercase letters.
Must contain at least two lowercase letters.
Must contain at least two numbers.
Must contain at least two special characters, i.e. any character that is not a letter or a number.
Procedure 3-1 How to Install the OMC Server OS
1
Insert the KickStart CD into the DVD-ROM drive.

Result: The DVD-ROM light begins to blink.
Be sure that you have the appropriate version of Kickstart CD and

RHEL 5.3 operating system on DVD.
2
Restart the MCD 5000 OMC server by pressing the Power button.
Result: The KickStart CD loads and the following messages appear:
Motorola Custom Kickstart, version Rxx.xx.xx
**- All installs are in text mode and VGA only. **
-To install without configuring the serial port, press
<ENTER>
-To install and configure the serial port type serial and
then <ENTER>
Press Enter.
Result: The installation starts. After some time, the Kickstart CD opens and a
warning prompt CD Not Found appears, prompting you to insert the Red Hat
Enterprise Linux media.
Insert the Red Hat Enterprise Linux DVD into the DVD-ROM drive and press
Enter.
Result: The Red Hat Enterprise Linux OS install starts and the following
message appears:
Enter network device parameters
Network device eth0
ipaddr [def: ]:
3-8
6802987C96-A
July 2011
Procedure 3-1 How to Install the OMC Server OS (Continued)

5
To configure network device parameters, use the following steps:

1. Type the IP address for the MCD 5000 OMC server and press Enter.
Result: The following message appears:
Netmask [def:
]:
2. Type the netmask and press Enter.

Is this the primary interface [y/n] :
3. Type y and press Enter.

default gateway[def:
]:
4. Type the default gateway and press Enter.

hostname[def:
]:
5. Type the hostname and press Enter.

domain name[def:
]:
6. Type the domain name and press Enter.

Primary DNS nameserver [def:
]:
Configuring DNS nameservers is not required; enter . to leave this field blank
and press Enter for all four DNS nameservers.
Primary NTP server [def:
]:
Configuring NTP Servers is not required; enter . to leave this field blank and
press Enter for both NTP servers, Primary and Secondary.
To set the GRUB Bootloader password, use the following steps:

1. Type the password you want at the password prompt and press Enter.
Make sure that the password conforms to the rules described at the
start of procedure.
The default password that is set by the factory should be as quoted

wngWNG123!?.
2. Type the password again exactly as you did in the step above and press Enter.
Result: The Linux OS Installer prompts you about the success of setting the
GRUB bootloader password.
6802987C96-A
July 2011
3-9
Procedure 3-1 How to Install the OMC Server OS (Continued)

9
To set the root password, use the following steps:

1. Type the password you want at the root password prompt and press Enter.
Make sure that the password conforms to the rules described at the
start of procedure.
Make sure that you remember the root password; you will need it for
server configuration and management.
The default password that is set by the factory should be as quoted

wngWNG123!?.
2. Type the password again exactly as you did in the step above and press Enter.
Result: The Linux OS Installer prompts you about the success of setting the
root password.
10
To set the timezone, use the following steps:

1. Use the Space key for the asterisk if the system clock uses UTC.
2. Use the Tab key to move to the timezone list.
3. Use the arrow keys to select a timezone.
4. Press the Tab key to select OK and press Enter.
Result: The Linux OS Installer prompts you to set the system time. OS
installation should start. If you use CDs, the installer will prompt when and
which CD should be inserted.
11
When the Install complete message appears, press Enter to continue.
12
Remove the media with Red Hat Enterprise Linux from the DVD-ROM when the
OS Installer Complete screen appears and press Enter for reboot.
The system continues the booting process.

Result: The login prompt appears after the system completes the rebooting
process.
3-10
6802987C96-A
July 2011
Installing MCD 5000 OMC Server Application
Installing MCD 5000 OMC Server Application

Follow Procedure 3-2 to install the MCD 5000 OMC server application.
Procedure 3-2 How to Install the OMC Server Application
1
Log on to the OMC server as the root user.

Result: The root prompt appears.
Insert the MCD 5000 OMC Server Application CD into the server DVD-ROM
drive. Type mount /media/cdrom and then press Enter.
Result: The DVD-ROM drive is mounted.
Verify that the DVD-ROM drive is mounted by typing

ls /media/cdrom and then press Enter.
Result: The content of the DVD-ROM is displayed.
Type /mnt/media/install_omc and press Enter.

Result: The following screen appears:
Select the Install from CDROM option.

Result: The installation and configuration script runs and the OMC server
application is installed. The process may take several minutes.
Type umount /mnt/media and press Enter.

Result: The DVD-ROM drive is unmounted.
6802987C96-A
July 2011
Remove the Installation CD from the drive.
3-11
Changing the Root Account Password
Changing the Root Account Password

Follow Procedure 3-3 to change the password for the root account from the command line
of the OMC server in an MCD 5000 Deskset System.
In an MCD 5000 Deskset System, the root account is a local account on the server. It is
not managed by the OMC administration tool. Root account passwords are specific to an
individual Linux-based server. A password change on one server is not propagated to other
servers. The root account password can only be changed while logged in as root.
The default root password for an OMC server that was set by the factory is as
quoted wngWNG123!?. The root password should be remembered, because it is
needed for OMC server configuration and maintenance.
The root password must meet the following criteria:
Must be at least nine characters long
Must contain at least two uppercase letters
Must contain at least two lowercase letters
Must contain at least two numbers
Must contain at least two non-alphanumeric characters, i.e. any character

that is not a letter or a number.
Procedure 3-3 How to Change the Root Account Password

1
Log on to the OMC server as the root user.

Result: The root prompt appears.
Type passwd, than press Enter.

Changing password for user root.
New UNIX password:
At the prompt, type the new Unix password for the root account, then press Enter.
Result: If the new password is valid, a Retype new UNIX password prompt
appears.
If the password entered does not meet the Password Restrictions,

a BAD PASSWORD message appears, followed by the New
Unix password: string being displayed at the prompt. After three
consecutive BAD PASSWORD messages the following message is
displayed: passwd: Authentication token manipulation
error
3-12
6802987C96-A
July 2011
Viewing/Configuring Network Parameters
Procedure 3-3 How to Change the Root Account Password (Continued)

4
Retype the password you had just entered, then press Enter.
Result: The root password is set to be the new password.
At the command prompt, type logout then press Enter.

Result: The login prompt is displayed.

Follow Procedure 3-4 to change network parameters of an OMC server in an MCD
5000 Deskset System, including:
IP addresses for DNS servers, if present in the system
Hostname, IP address, netmask, and default gateway
Executing this procedure can lead to an unexpected OMC server disconnection.

For example, the OMC server will not operate if this procedure results in improper
configuration of its hostname, IP address, netmask, and default gateway.
Before performing Procedure 3-4, obtain the required network parameter information from
your IP network administrator. Use the root account to perform Procedure 3-4.
Procedure 3-4 How to View/Configure Network Parameters
1
Log on to the OMC server using the root account, and enter the following
command: admin_menu
Result: The main administration menu for the server displays.
Enter the number for the menu option OS Administration.

Result: The OS Administration menu appears.
To view network parameters, enter the number for the option to Display Platform
Configuration Information.
Result: Platform configuration information is displayed and prompts you to press
a key to display additional information. Included in the information: operating
system, kernel release version, host name, domain name, MAC address, uptime,
and IP address.
6802987C96-A
July 2011
To change network parameters, perform the operations given in the following

steps.
3-13
Procedure 3-4 How to View/Configure Network Parameters (Continued)

5
At the OS Administration menu, enter the number for the option to Manage
Platform Configuration.
Result: The Manage Platform Configuration menu appears.
Enter the number for the option to Configure Network Parameters.

Result: The system prompts you to enter a new hostname.
Perform one of the following:

Press Enter to accept the existing hostname (which is displayed within [ ])
Type the new hostname for the device you are configuring and press Enter.
Result: The system prompts you to enter a new domain name.

Press Enter to accept the existing domain name (which is displayed within
[ ]).
Type the new domain name for the device you are configuring.
Result: The system prompts you to enter the new First (Primary) DNS Name
Server IP address.

Press Enter to accept the existing DNS Name Server IP address (which is
displayed within [ ]).
Type the new DNS Name Server IP address.
Result: The system prompts you to enter the new Second (Secondary) DNS
Name Server IP address.
10
At the prompts for the second, third, and fourth DNS name servers, perform one
of the steps below to retain, change, or delete the IP addresses:
To retain the existing DNS Name Server IP address (which is displayed
within [ ]), press Enter.
To change the DNS Name Server IP address, type the new DNS Name
Server IP address and press Enter.
To delete the existing DNS Name Server IP address, type - and press Enter.
If [def:] is displayed, the system is not configured with the specific

DNS Name Server IP address.
Result: After you have made changes to the fourth DNS name server, the system
prompts you to enter the Primary Interface (network adapter number).
3-14
6802987C96-A
July 2011
MCD 5000 Deskset System with OMC Installation and Configuration Guide Configuring MCD 5000 Deskset System OMC Servers IP Addresses
Procedure 3-4 How to View/Configure Network Parameters (Continued)

11

Press Enter to accept the existing Primary Interface number (which appears
within [ ]).
Type the new Primary Interface number for the OMC server you are
configuring. This parameter cannot be left blank.
Result: The system prompts you to enter an IP address.
12
Press Enter to retain the existing IP address for the OMC server you are
configuring (which is displayed within [ ]).
Perform the steps below to change the IP address:
To change the IP address, type the new IP address and press Enter.
To delete the existing IP address, type - and press Enter.
13
Press Enter to retain the existing netmask address for the OMC server you are
configuring (which is displayed within [ ]).
To change the netmask address, type the new netmask address and press Enter.
Result: The system prompts you to enter a new default gateway IP address.
14

Press Enter to accept the existing default gateway for the OMC server you
are configuring (which appears within [ ]).
Type the new default gateway IP address for the device you are configuring.
Result: If you entered a new IP address or netmask address in the following
steps, for the OMC server you are configuring, the system prompts you to enter y
to restart networking with new values.
15
Type y and press Enter to restart networking with the new values.
16
Type reboot and press Enter for all the changes to be effective.
Result: The system restarts and the login prompt appears on the screen.
Configuring MCD 5000 Deskset System OMC Servers IP

Addresses
Follow Procedure 3-5 to configure OMC servers IP addresses.
In an MCD 5000 Deskset System with two OMC servers Main and Redundant, configure the
network settings for both OMC servers (Procedure 3-4) before performing the following procedure.
6802987C96-A
July 2011
3-15
Configuring MCD 5000 Deskset System OMC Servers IP Addresses
If you have a Main and Redundant OMC servers in your MCD 5000 Deskset System,
perform the following procedure for the Main OMC server only.
Procedure 3-5
1
How to Configure OMC Servers IP Addresses
Log on to the OMC server using the root account.

Result: The command prompt displays.
Enter the following command: admin_menu.

Result: The server administration Main Menu appears.
Enter the number for the option Application Administration.

Result: The Services Administration menu appears.
Enter the number for the option OMC Servers IP Configuration.

Result: The OMC Servers IP Configuration menu appears.
To see how the OMC servers IP addresses are currently configured,

enter the number for the option Show OMC servers Configuration.
5
Enter the number for the option Update OMC server Configuration.
Result: The system prompts you to enter the Main OMC server IP address.

Press Enter to accept the existing Main OMC server IP address (which is
Type the new Main OMC server IP address.
Result: The system prompts you to enter Redundant OMC server IP address.

Press Enter to accept the existing Redundant OMC server IP address
(which is displayed within [ ]).
Type the new Redundant OMC server IP address.
Result: The OMC server database is updated with the new IP configuration.
Press q to exit the OMC configuration Menu.

Result: The Application Administration window appears.
Enter the number for the option OMC Server Service Restart.
Result: The OMC service is restarted.
3-16
6802987C96-A
July 2011
Configuring the Time of Day, Date or Time Zone
Procedure 3-5 How to Configure OMC Servers IP Addresses (Continued)

10
Perform the OMC Server Service Restart action on the Redundant server.
In a system with a Main and Redundant OMC server, the OMC servers databases
will be synchronized and the replication process will start.
Configuring the Time of Day, Date or Time Zone

Follow Procedure 3-6 to configure the time of day, date, or time zone of the OMC server.
Procedure 3-6 How to Configure the Time of Day, Date, or Time Zone of the OMC Server
1


Enter the number for the option OS Administration.

Result: The OS Administration menu appears.
Enter the number for the option Manage Platform Configuration.

Result: The Manage Platform Configuration menu appears.
Enter the number for the option Configure Time Parameters.

Result: A menu displays numbered options to change Time of Day, Date, or
Time Zone.
Enter the number for the parameter you want to change:

Time of Day: This option prompts you to enter a value for hour, then
a value for minutes. The time of day change will take effect only after
rebooting the OMC server.
Date: This option prompts you to enter a value for the year, then a value
for the month, and then a value for the day of the month. The change will
take effect only after rebooting the OMC server.
Time Zone: This option starts by prompting you for region of the world,
or you can choose to specify the time zone using the Posix TZ format.
Continue responding to the prompts until you see a message regarding
/usr/bin/tzselect. You can ignore the message. The time zone change will
take effect only after rebooting the OMC server.
To exit from the prompts above, press the Ctrl-C keys. The Manage
Platform Configuration menu will appear.
6802987C96-A
July 2011
3-17
Configuring NTP Client
Configuring NTP Client

Follow Procedure 3-7 to configure NTP Client of the OMC server.
The time of the OMC servers in an MCD 5000 Deskset System should be in
sync. If a NTP server is not available in the system, set one of the OMC servers
to be the NTP server and the other as its client.
Procedure 3-7 How to Configure NTP Client of the OMC Server
1


Enter the number for the option Services Administration.

Enter the number for the option Manage NTP Configuration.

Result: The Manage NTP Configuration menu appears.
To see what NTP servers are currently configured, enter the number
for the option Display NTP Client Configuration.
5
Enter the number for the option Configure NTP Client.

Result: A numbered list of NTP Client Configuration options appears.
Enter the number for one of the following options:

Add NTP Server IP Address: After selecting this option, you will be
prompted to enter the IP address.
Remove NTP Server: After selecting this option, you will be prompted to
enter the number for one of the NTP servers in a numbered list.
Result: The Manage NTP Configuration menu appears. To verify the changes,
enter the number for the option Display NTP Client Configuration.
To add another NTP server, enter the number for the option Add
NTP Server IP Address.
3-18
6802987C96-A
July 2011
Configuring the System Geographical Area
Configuring the System Geographical Area

Follow Procedure 3-8 to configure the system geographical area.
The MCD 5000 Deskset System geographical area determines the part of the
map that is displayed in the ACP.
Procedure 3-8 How to Configure MCD 5000 Deskset System Geographical Area
1



Enter the number for the option Set System Geographical Area.
Result: The Set System Geographical Area menu appears.
To see how the current system geographical area is configured, enter

the number for the option Show System Geographical Area.
5
Enter the number for the option Select a state.

Result: A list of available states is displayed and prompts you to enter the
desired state number.
Enter the number for the desired state.

Result: The selected state name and coordinates are set as the system
geographical area.
To update the current configured geographical area, enter the number for the
option Update System Geographical Area.
Result: The system prompts you to enter a new geographical area name.

Press Enter to accept the existing geographical area name (which is
Type the new geographical name and press Enter.
Result: The system prompts you to enter a new upper left latitude value between
(-90 - 90).
6802987C96-A
July 2011
3-19
Advanced Maintenance for OMC Server
Procedure 3-8 How to Configure MCD 5000 Deskset System Geographical Area (Continued)
9

Press Enter to accept the existing upper left latitude (which is displayed
within [ ]).
Type the new upper left latitude and press Enter.
Result: The system prompts you to enter a new upper left longitude value
between (-180 - 180).
10

Press Enter to accept the existing upper left longitude (which is displayed
within [ ]).
Type the new upper left longitude and press Enter.
Result: The system prompts you to enter a new lower right latitude value
between (-90 - 90).
11

Press Enter to accept the existing lower right latitude (which is displayed
within [ ]).
Type the new lower right latitude and press Enter.
Result: The system prompts you to enter a new lower right longitude value
between (-180 - 180).
12

Press Enter to accept the existing lower right longitude (which is displayed
within [ ]).
Type the new lower right longitude and press Enter.
Result: The system geographical area is updated.
Advanced Maintenance for OMC Server
The following OMC Server maintenance tasks should be performed by MCD 5000 Deskset System
administrators only. These procedures use the administration menu tool.
3-20
"Restarting the OMC Server Service" on page 3-21.
"Restarting the MySQL Server Service" on page 3-21.
"Checking the OMC Database Replication Status" on page 3-22.
6802987C96-A
July 2011
Restarting the OMC Server Service
"Restoring the OMC Database from a Backup File" on page 3-24.
"Synchronizing the OMC Servers Databases" on page 3-24.
"Backing-up the OMC Server Database" on page 3-26.
"Updating the System and Database Users Passwords" on page 3-26.
Restarting the OMC Server Service

Follow Procedure 3-9 to restart the OMC server service.
The following procedure should be performed after procedures that update the OMC server database.
Procedure 3-9 Restarting the OMC Server Service
1



Result: The Application Administration menu appears.
Enter the number for the option OMC Server Service Restart.
Result: The OMC service restarts and the following output is displayed:
Stopping ssrnomcd: [ OK ]
Starting ssrnomcd: [ OK ]
Restarting the MySQL Server Service

Follow Procedure 3-10 to restart the MySQL server.
The following procedure should be performed after changes in the database user password.
6802987C96-A
July 2011
3-21
Checking the OMC Database Replication Status
Procedure 3-10 Restarting the MySQL Server Service

1
Log on to the Linux-based server using the root account.



Enter the number for the option MYSQL Service Restart.

Result: The MySQL service restarts and the following output is displayed:
Stopping mysqld: [ OK ]
Starting mysqld: [ OK ]

Follow Procedure 3-11 to check the OMC database replication status.
Perform the following procedure on the standby OMC server in order to check
the replication status of the OMC server database.
Procedure 3-11 Checking the OMC Database Replication Status
1



Enter the number for the option Database replication status.

Result: The OMC server database replication status is displayed:
show master status:
------------------File: mysqld-bin.000002
Position: 691674
Binlog_Do_DB:
Binlog_Ignore_DB:
3-22
6802987C96-A
July 2011
Procedure 3-11
Checking the OMC Database Replication Status (Continued)
show slave status:

-----------------Slave_IO_State: Waiting for master to send event
Master_Host: 10.108.15.105
Master_User: replicuser
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: mysqld-bin.000001
Read_Master_Log_Pos: 5678421
Relay_Log_File: mysqld-relay-bin.000008
Relay_Log_Pos: 418894
Relay_Master_Log_File: mysqld-bin.000001
Slave_IO_Running: Yes
Slave_SQL_Running: Yes
Replicate_Do_DB: ssrn
Replicate_Ignore_DB:
Replicate_Do_Table:
Replicate_Ignore_Table:
Replicate_Wild_Do_Table:
Replicate_Wild_Ignore_Table:
Last_Errno: 0 Last_Error:
Skip_Counter: 0
Exec_Master_Log_Pos: 5678421
Relay_Log_Space: 445129
Until_Condition: None
Until_Log_File:
Until_Log_Pos: 0
Master_SSL_Allowed: No
Master_SSL_CA_File:
Master_SSL_CA_Path:
Master_SSL_Cert:
Master_SSL_Cipher:
Master_SSL_Key:
Seconds_Behind_Master: 0
Master_SSL_Verify_Server_Cert:
No Last_IO_Errno: 0
Last_IO_Error:
Last_SQL_Errno: 0
Last_SQL_Error:
If the status of both the Slave_IO_Running and Slave_SQL_Running

is Yes, then the database of the Standby OMC server is in sync
with the Active OMC server. If the status of Slave_IO_Running or
Slave_SQL_Running is No, then the database out of sync, and a
database synchronization should be performed from the Active OMC
server (the most updated OMC server).
6802987C96-A
July 2011
3-23
Restoring the OMC Database from a Backup File

Follow Procedure 3-12 to restore the OMC database from a backup file.
In order to restore a database from a backup file not located on the OMC server, the file
must first be uploaded to the OMC server by a SFTP client (winscp for example) to the
following directory: /opt/Motorola/motobridge/omcserver/ssrnDBbackups/.
Procedure 3-12
1



Enter the number for the option Database restore.

Result: A list of the database files located under the directory
/opt/Motorola/motobridge/omcserver/ssrnDBbackups/ is displayed.
Enter the number for the OMC server database file you want to restore.
Result: The selected OMC server database backup file is restored. If there is a
redundant OMC server in the MCD 5000 Deskset System then the OMC server
databases are synchronized.
After restoring the OMC server database, restart the OMC server
service on all the OMC servers in the MCD 5000 Deskset System
using Procedure 3-9.
Synchronizing the OMC Servers Databases

Follow Procedure 3-13 to synchronize the OMC servers database.
Use the following procedure, if the OMC servers databases are not synchronized.
3-24
6802987C96-A
July 2011
Synchronizing the OMC Servers Databases
Always perform the database synchronization from the Active OMC server
which has the most updated database.
Procedure 3-13 Synchronizing the OMC Servers Databases
1



Enter the number for the option Database synchronize.

Result: The OMC servers' databases are synchronized and the replication process
restarts; the following messages will be displayed during the synchronization:
Starting databases synchronization... Backup [other OMC server IP] database
to /opt/ssrn/omcserver/ssrnDBbackups/sync_backup.sql Starting databases
replication process...
The synchronization process can take several minutes to complete

depending on the database size.
After synchronizing the OMC servers' databases, restart the OMC

server service on all the OMC servers in the MCD 5000 Deskset
System using Procedure 3-9.
5
6802987C96-A
July 2011
Stop and start the OMC service on both OMC servers.
3-25
Backing-up the OMC Server Database
Backing-up the OMC Server Database

Follow Procedure 3-14 to backup the OMC servers' database.
The OMC server database is backed up to a file every night; use the following procedure if you
want to create a backup of the current database state. The database backup files are located
under the following directory: /opt/Motorola/motobridge/omcserver/ssrnDBbackups/.
The OMC server database is backed up to the local hard drive; it is advisable to copy
the database backups to an external media every once in a while.
Procedure 3-14 Backingup the OMC Server Database
1



Enter the number for the option Database backup.

Result: The OMC server database is backed up to file and the following
messages is displayed (for example): Database was backed up to file:
/opt/Motorola/motobridge/omcserver/ssrnDBbackups/ssrndb_Apr_05_2011.sql.9
Updating the System and Database Users Passwords

Follow Procedure 3-15 to change the password of the system users and the database users.
The default password for the database and system users is wngWNG123!?.
When changing the default user password make sure to remember the new given password.
3-26
6802987C96-A
July 2011
In an MCD 5000 Deskset System with two OMC servers Main and Redundant,
the database and system users passwords must be identical on both OMC servers,
so if you choose to change the user password on one of the OMC servers, you must
change the user password on the other OMC server as well.
Procedure 3-15 How to Change Database or System-user Password
on MCD 5000 Deskset System
1



Enter the number for the option Password update for database/system user.
Result: The Password update for database/system menu appears.
To update the system user ssrn password:

1. Enter the number of the option Update System-User password.
2. You will be asked to enter the current ssrn password.
3. You will be asked to enter the new ssrn password.
4. You will be asked to confirm the new ssrn user password.
Result: The system user ssrn password is updated.
To update one of the database's user passwords:

1. Enter the number of the option Update database password.
2. Enter the option number of the database user that you want to update his
password.
3. You will be asked to enter the current database user password.
4. You will be asked to enter the new database user password.
5. You will be asked to confirm the new database user password.
Result: The database user password is updated.
After changing the database user password, restart the MySQL server
using Procedure 3-10. After restarting the MySQL service, restart
the OMC server service on all the OMC servers in the MCD 5000
Deskset System using Procedure 3-9.
6802987C96-A
July 2011
3-27
Procedure 3-15 How to Change Database or System-user Password on MCD 5000 Deskset
System (Continued)
After changing the system user password, restart the OMC server
using Procedure 3-9.
3-28
6802987C96-A
July 2011
Chapter
4
Installing MCD 5000 Deskset System Units
This chapter includes hardware information specific to MCD 5000 Deskset System units,
including installation instructions. General information on hardware installation is provided
in Chapter 2, "General Hardware Installation Practices".
This chapter covers the following topics:
"MCD 5000 Deskset System Devices" on page 4-1.
"MCD 5000 Deskset Unit Hardware Description" on page 4-2.
"MCD 5000 Deskset & Accessories Configurations" on page 4-6.
"Cabling the MCD 5000 Deskset" on page 4-12
"Connecting Peripheral Equipment to the MCD 5000 Deskset" on page 4-14.
"MCD 5000 Radio Gateway Unit (RGU) Hardware Description" on page 4-16.
"Understanding Cables Color Coding" on page 4-18.
"Cabling the MCD 5000 RGU" on page 4-19.
"Cabling a Radio to an MCD 5000 RGU or MCD 5000 Deskset" on page 4-21
"Connecting an MCD 5000 Deskset to an SB9600 Radio in Parallel to MC3000" on page 4-22
"Connecting Many MCD 5000 Desksets through MCD 5000 RGU to SB9600
Radio in Parallel to MC3000" on page 4-24
"Installing New MCD 5000 Deskset System Units"
MCD 5000 Deskset System Devices
The system consists of the following devices.
6802987C96-A
July 2011
4-1
MCD 5000 Deskset
MCD 5000 Deskset

The MCD 5000 Deskset is a part of the MCD 5000 Deskset System. The unit is a desktop console that
provides the capability to connect to a radio. The MCD 5000 Deskset may connect directly to a radio or it
may connect to a selected radio over an IP network via the MCD 5000 Radio Gateway Unit (RGU).
The MCD 5000 Deskset includes the Buttons & Display Unit used by the MCD 5000 end-user as the
Man-Machine Interface (MMI). Each MCD 5000 Deskset can be connected to a single Radio Device at a time.
MCD 5000 Radio Gateway Unit (RGU)

The MCD 5000 Radio Gateway Unit (RGU) is a part of the MCD 5000 Deskset System. The MCD 5000 RGU
serves as the interface unit to link up to 4 radios to the MCD 5000 Deskset System IP network. An MCD 5000
Deskset user can create a talkpath over the IP network to a radio resource connected to the MCD 5000 RGU.
MCD 5000 Deskset Unit Hardware Description
MCD 5000 Deskset Upper Panel Layout

Figure 4-1 shows the MCD 5000 Deskset upper panel layout.
4-2
6802987C96-A
July 2011
Figure 4-1
Table 4-1 describes the features of the MCD 5000 Deskset upper panel shown in Figure 4-1.
Table 4-1 MCD 5000 Deskset Upper Panel Features
No.
6802987C96-A
Name
Description
Handset
For audio transmit and receive, with a microphone in the mouthpiece and
an audio speaker in the earpiece and a built-in PTT.
Internal Speaker
For hands-free public audio receive.
Internal Microphone
For hands-free audio transmit.
Transmit Button
For transmitting on the radio channel.
Transmit LED
Indicating that the MCD 5000 Deskset is transmitting on the radio

channel.
Busy LED
Indicating that another Deskset is using the radio channel.
Receiver Indicator
Indicating that the MCD 5000 Deskset is receiving on the radio channel.
Volume Control
Increases or decreases received audio volume for the handset, speaker

phone, or headset (depending upon which is currently active).
All Mute Button
Toggles the mute on or off. Allowing the MCD 5000 Deskset user to
mute all received audio. Pressing any button will remove the MCD 5000
Deskset from "All Mute" state. Internal red LED indicates "All Mute"
is turned on.
July 2011
4-3
MCD 5000 Deskset Bottom and Side Panels Layout
Table 4-1
MCD 5000 Deskset Upper Panel Features (Continued)
No.
Name
Description
10
Speaker Button
Toggles the internal speaker on or off, allowing the MCD 5000 Deskset
user to turn on the internal speaker as additional audio source to the
headset or the handset. The Speaker Button operation has a corresponding
indication LED. The Internal green LED indicates the internal speaker
is turned on.
11
Navigation Keys
For browsing through menus.
12
Emergency Button
For activating an Emergency Outbound function from the MCD 5000

Deskset.
13
Menu Button
Toggles upper soft keys between "MCD 5000 Deskset Home Screen" and
"Emulated Radio Screen".
14
LCD display
For displaying: digital radio messages or test and configuration messages,

radio icons, soft keys and VU meter readings.
15
Radio Soft keys

(Radio Function
Buttons)
Radio programmable buttons or radio soft keys buttons.
16
Mode Up and Mode

Down Buttons
For moving up and down through the MCD 5000 Deskset or radio menu
of modes, channels or functions that appear on the LCD display. Used as
page up/down button to review logs on the MCD 5000 Deskset screen
(not active MCD 5000 Deskset Home Screen).
17
Keypad
For emulating the keypad of the radio and entering numbers to operate the
MCD 5000 Deskset functionality.
18
Base Intercom Button

& LED
Toggles the Base Intercom on or off. The Base Intercom button allows
direct communication between parallel MCD 5000 Deskset users that are
connected to the same radio in the system without transmitting over the
radio channel. The Base Intercom button has an internal LED. The green
LED indicates incoming transmission and red LED indicates outgoing
transmission.
19
MCD 5000 Deskset

Soft keys (MCD 5000
Deskset Function
Buttons)
Programmable buttons for MCD 5000 Deskset-specific (not radio)

functions.
20
Home Button
Emulates the "Home Key" on a given radio.

Figure 4-2 shows the MCD 5000 Deskset lower and side panels layout.
4-4
6802987C96-A
July 2011
Figure 4-2 MCD 5000 Deskset Bottom and Side Panels Layout
Table 4-2 describes the features of the MCD 5000 Deskset bottom and side panels shown in Figure 4-2.
Table 4-2 MCD 5000 Deskset Bottom and Side Panels Features
No.
6802987C96-A
Name
Description
12V DC
12V DC input voltage (A type connector).
Int. LAN
Internal LAN connection (RJ45 connector).
Ext. LAN-PoE
External LAN connection includes input from Power over Ethernet (RJ45
connector).
Footswitch
Connection for Dual PTT Footswitch that contains PTT and Monitor
Buttons (3 PIN KK Molex connector).
DskMIC/JckBx
Connection for Desktop Microphone or Headset Jack Box (RJ45

connector).
Logger
Connection for Analog logging recorder (RJ45 connector).
Radio Comm.
Connection for RS-232 Digital signaling to a radio (RJ45 connector).
Radio 4W E&M
Analog connection to radio via internal input and output transformers

(RJ45 connector).
Handset
A telephone like handset that includes a PTT (Push to Talk) Button. A

magnet is installed inside the handset upper side, to set the On-Hook/
Off-Hook switch located on the Deskset cradle upper side.
10
MMI
RS-232 connection to Hyper terminal (RJ45 connector).
11
Footstand
Used to adjust the angle of the MCD 5000 Deskset base.
12
PTT Button
Handset Push-to-Talk (PTT) Button.
13
Footstand Release
Latch
Used to lock the footstand in position after adjusting the MCD 5000
Deskset angle.
14
Cable Holder
15
Handset Port
July 2011
Used for routing cables from the MCD 5000 Deskset connectors.
Connecting Handset (RJ22 connector).
4-5
MCD 5000 Deskset & Accessories Configurations
For the MCD 5000 Deskset connectors pinout, see Appendix E, "MCD 5000 Deskset and
MCD 5000 RGU Connectors Pinouts and Settings" .
The MCD 5000 Deskset and the MCD 5000 RGU are not equipped with an ON-OFF
switch or with a Reset button. To reset the unit, disconnect it from all of its power
supplies (12v DC or External LAN-PoE or both).
The Desk MIC and the MCD 5000 Headset Jack Box share the same connector and thus
cannot be connected to the MCD 5000 Deskset at the same time.
MCD 5000 Deskset & Accessories Configurations
The MCD 5000 Deskset can be used with accessories to support the following operating configurations:
Phone Like: Uses the Deskset attached Handset (and internal speaker).
Classic: Uses a desktop paddle microphone and internal speaker.
Hands-free option 1: Uses a Dual PTT footswitch, Headset and Headset

Base without PTT (and internal speaker).
Hands-free option 2: Uses a Headset and Headset Base with PTT (and internal speaker).
Instructions for connecting the audio accessories and peripherals to the MCD 5000
Deskset to create these operating configurations are listed in "Connecting Peripheral
Equipment to the MCD 5000 Deskset" on page 4-14.
4-6
6802987C96-A
July 2011
MCD 5000 Deskset Accessories
MCD 5000 Deskset Accessories

The MCD 5000 Deskset unit can be used with the audio accessories listed in Table 4-3.
Table 4-3 MCD 5000 Deskset Unit Accessories
Part Number
Accessory Type
RMN5068
Desktop Paddle Microphone
BLN6732
(2-pedal) Dual PTT Footswitch
FHN7470
MCD 5000 Headset Jack Box
CDN6281
Headset Base with PTT Switch
CDN6282
Headset Base without PTT Switch
For the part number list

of supported Headsets see
table below
List of supported Headsets
FHN7469
AC In-line Adapter Power Supply

unit
FHN7290
K-STYLE Handset (including

cable)
Handset is supplied
with the Deskset.
The headset can be picked from a variety of headset models authorized for the MCD
5000 Deskset and listed in Table 4-4.
Table 4-4 MCD 5000 Deskset Supported Headset Models
No.
6802987C96-A
Part
Number
Name
Description
CDN6284
Supra Binaural H.S. Top
Headband style, without tone control
CDN6285
Tristar H.S. Top
Over the ear
CDN6286
Encore Monaural H.S.

Top
Single SPK H.S. with tone control
CDN6287
Encore Binaural H.S. Top
Dual ear, with tone control switch, headband

style
CDN6288
Starset Noise Canceling

H.S. Top
Unidirectional microphone, ear lip style
CDN6289
Mirage Noise canceling

H.S. Top
Over the ear style
CDN6291
Supra Binaural Noise

canceling H.S. Top
Headband style, without tone control
CDN6292
Tristar Noise cancelling

H.S. Top
Unidirectional microphone, ear bud style
July 2011
4-7
MCD 5000 Deskset Accessories Description
Table 4-4 MCD 5000 Deskset Supported Headset Models (Continued)

No.
Part
Number
Name
Description
CDN6293
Encore Monaural Noise

canceling H.S. Top
Unidirectional microphone, with tone control,

headband style
10
CDN6294
Encore Binaural Noise

canceling H.S. Top
Unidirectional microphone, with tone control,

switch headband style
11
CDN6295
Starset H.S. Top
Over the ear, with ear lip receiver
12
CDN6296
Mirage H.S. Top
Over the ear
13
CDN6297
Supra Monaural H.S. Top
Single SPK headband style, without tone

control
MCD 5000 Deskset Accessories Description

AC In-line Adapter Power Supply Unit
Provides power to the MCD 5000 Deskset/MCD 5000 RGU by converting from 96 262 VAC @
48 62 Hz to 11.4-12.6 vDC (12vDC NOM) (Part number FHN7469, with US cord). DC output
current: 2.0 Amp. DC cable length: 1.5 m (integral to power supply).
Figure 4-3 AC In-line Adapter (US cord not shown)
Desktop Paddle Microphone

The Desktop Paddle Microphone supports PTT buttons and Monitor. The recommended
Desktop Paddle Microphone part number is RMN5068.
4-8
6802987C96-A
July 2011
Dual PTT Footswitch (2-pedal)
Figure 4-4 Desktop Paddle Microphone
Verify that the RMN5068 Desktop Paddle Microphone Hotmic/Intercom option is activated.
If activated, the user voice will be collected by the Desktop Paddle Microphone while
either pressing the Deskset PTT or the Dual PTT footswitch PTT.
Connect a Desktop Paddle Microphone, part number RMN5068, to the MCD 5000 Desksets
DskMIC/JackBx connector. The microphone sensitivity potentiometer can be found on the rear of
the RMN5068. The Desktop Paddle Microphone must be connected after the MCD 5000 Deskset
is configured using the MCD 5000 CT application to expect a paddle microphone on this port,
otherwise a constant PTT will result. The Desktop Paddle Microphone dip switches must be
configured as 5082. Contact Motorola Customer Support if the Desktop Paddle Microphone does
not function as described here. Disconnecting the Desktop Paddle Microphone from the MCD
5000 Deskset must be followed with a correct MCD 5000 Deskset configuration using the CT.
Dual PTT Footswitch (2-pedal)

Each MCD 5000 Deskset can support up to 1 Dual PTT footswitch. The Dual PTT footswitch
provides two foot pedals in a rugged, metal housing with a 7 foot cable. One pedal is used for the
general transmit feature while the other pedal is used for the monitor feature.
6802987C96-A
July 2011
4-9
Figure 4-5
Dual PTT Footswitch Two Foot Pedals
The MCD 5000 Deskset System Dual PTT footswitch does not support a Sticky PTT operation
mode. Sticky PTT is an operation mode where the PTT button is pressed twice, once for
originating the PTT session and second for releasing the PTT; in the MCD 5000 Deskset
System the PTT button has to be kept pressed; otherwise the PTT is released.

A headset may be used with the MCD 5000 Deskset to allow the Deskset user to listen and receive
audio on the selected radio channels, and talk on any radio channels. The MCD 5000 Deskset supports
one headset per Deskset. A headset must be connected to an MCD 5000 Headset Jack Box. The
headset is hooked up to the MCD 5000 Deskset as shown in Figure 4-6.
The headset is connected to the headset base using the Plantronics Quick Disconnect connector.
The headset base is an amplifying unit which comes with or without PTT. This unit is hooked
onto an MCD 5000 Headset Jack Box unit by two prong connectors. The Headset Jack Box unit
is connected to the MCD 5000 Deskset via RJ45 to RJ45 cable. The headset and the Headset
base are pre-defined units and need no mechanical involvement.
The RJ45-to-RJ45 cable connecting the MCD 5000 Headset Jack Box to the
Deskset is a custom cable (not a straight cable).
4-10
6802987C96-A
July 2011
Figure 4-6 MCD 5000 to Headset Connection Scheme
The FHN7470 MCD 5000 Headset Jack Box DESKSET connector is marked with a color matched with
the Jack Box connector of the FKN8694 MCD 5000 Deskset to Headset Jack Box Cable.
Figure 4-7 MCD 5000 Headset Jack Box RJ45 View

Provides connectivity to the headset with PTT functionality. Recommended part number: CDN6281.
Figure 4-8 Headset Base with PTT Switch

Provides connectivity to the headset. Recommended part number: CDN6282.
6802987C96-A
July 2011
4-11
Cabling the MCD 5000 Deskset
Figure 4-9
Before cabling or connecting MCD 5000 Deskset peripherals, the MCD 5000 Desksets
and MCD 5000 RGUs must be configured as explained in Chapter 6.
Follow Procedure 4-1 to attach the cables to an MCD 5000 Deskset.
Procedure 4-1 Cabling the MCD 5000 Deskset
4-12
Place the MCD 5000 Deskset on a horizontal surface or tie it to a vertical surface,
using the Wall Mount Kit, Motorola Part Number: FHN7394 (not supplied).
Place the Power Supply near the MCD 5000 Deskset on a safe horizontal surface.
Connect the Handset cable to the MCD 5000 Deskset and to the handset.
Connect the MCD 5000 Deskset accessory cables to the MCD 5000 bottom panel
connectors, see "Connecting Peripheral Equipment to the MCD 5000 Deskset"
on page 4-14.
Pull and hold the Footstand Release Latch and rotate the Footstand to your
convenient angle. Release the Footstand Release Latch and verify that the
Footstand is latched.
6802987C96-A
July 2011
Procedure 4-1
Cabling the MCD 5000 Deskset (Continued)
Connect the External LAN PoE cable to the MCD 5000 Deskset. Attach the black
label from the FKN8695 cable kit to the cable side close to the MCD 5000 Deskset
"External LAN PoE" connector. Attach the white label (from the FKN8695 cable
kit) marked with "PoE/LAN external" to the other side of the cable.
Connect the External LAN PoE cable (other cable side) to the site LAN outlet.
If the site LAN outlet includes an active PoE-PSE, the MCD 5000
Deskset will be powered and start its booting process (PoE-PSE is
not supplied).
8
Connect the DC cable of the Power Supply unit to the DC Inlet on the bottom
side of the MCD 5000 Deskset. Make sure the cable is not routed with tension.
Connect the AC cord of the power supply unit to the AC power wall mount
outlet (110-240 VAC, 50/60 Hz). The AC power outlet should be as near as
possible to the equipment and should be accessible. Make sure that the cable is
not routed with tension.
If the AC line is alive, the MCD 5000 Deskset unit will be powered
and start its booting process.
The MCD 5000 Deskset can be connected to both AC power source

and PoE-PSE power source at the same time. The two power sources
will backup each other. Connecting the second power source will not
interrupt the Deskset operation.
10
For connecting the MCD 5000 Deskset directly to a Radio, see "Cabling a Radio
to an MCD 5000 RGU or MCD 5000 Deskset" on page 4-21.
11
Connect the radio cable Radio side to the proper radio connector.
12
Verify that the MCD 5000 Deskset topside LEDs turn on (which indicates the
MCD 5000 Deskset booting state) and after a while, they will turn off.
Observe the MCD 5000 Deskset main screen for any fault messages.
6802987C96-A
July 2011
4-13
Connecting Peripheral Equipment to the MCD 5000 Deskset
Connecting Peripheral Equipment to the MCD 5000

Deskset
The MCD 5000 Deskset has a variety of audio and peripherals accessories that can be connected to the
MCD 5000 Deskset. This section includes the procedures to assemble the operating configurations.
For a diagram of the connections, see the section entitled Connection to Power, Accessories
and Network in the MCD 5000 Deskset User Guide (6802987C94).
Phone Like
Connecting a Handset
Connect a Deskset handset, part number FHN7290, to the MCD 5000 Desksets Handset Port connector.
Classic
Connecting a Desktop Paddle Microphone
Connect a Desktop Paddle Microphone, part number RMN5068, to the MCD 5000
Desksets DskMIC/JackBx connector.
The microphone's sensitivity potentiometer, located on the rear of the RMN5068, can be adjusted
for better sound quality produced at the end user radio speaker.
The desktop microphone must be connected after the MCD 5000 Deskset is configured via the MCD 5000
CT application to expect a paddle microphone on this port. Otherwise, a constant PTT will result.
Hands-free Option 1
Connecting the Dual PTT Footswitch
Connect the Dual PTT footswitch accessory & cable, part number BLN6732, to the Deskset Footswitch
connector (3-Pin connector) located at the MCD 5000 Deskset bottom panel (see number 4 in Table 4-2).
Connecting the Headset, Headset Base and Headset Jack Box

Follow Procedure 4-2 to connect the headset and Headset Jack Box.
4-14
6802987C96-A
July 2011
Hands-free option 2
Procedure 4-2 Connecting the Headset

1
Connect the cable of the available headset (one of the headsets listed in Table 4-4,
"MCD 5000 Deskset Supported Headset Models," on page 4-7) to the Headset
Base without PTT accessory, part number CDN6282.
Connect the Headset Base without PTT prong connectors, part number CDN6282,
into the MCD 5000 Headset Jack Box, part number FHN7470.
Connect the MCD 5000 Headset Jack Box, part number FHN7470, to the MCD
5000 Desksets DskMIC/JackBx connector using the FKN8694 cable.
Hands-free option 2
Connecting the Headset, Headset Base and Headset Jack Box
Follow Procedure 4-3 to connect the headset.
Procedure 4-3 Connecting the Headset and Headset Jack Box
6802987C96-A
Connect the cable of the available headset (one of the headsets listed in Table 4-4,
"MCD 5000 Deskset Supported Headset Models," on page 4-7) to the Headset
Base with PTT accessory, part number CDN6281.
Connect the Headset Base with PTT prong connectors, part number CDN6281,
into the MCD 5000 Headset Jack Box, part number FHN7470.
Connect the MCD 5000 Headset Jack Box, part number FHN7470, to the MCD
5000 Desksets DskMIC/JackBx connector using the FKN8694 cable labeled as
IPDS JACKBOX CABLE.
July 2011
4-15
MCD 5000 Radio Gateway Unit (RGU) Hardware Description
MCD 5000 Radio Gateway Unit (RGU) Hardware

Description
MCD 5000 Radio Gateway Unit (RGU) Front and Rear Panels
Layout
Figure 4-10 shows the MCD 5000 RGU front and rear panels layout.
Figure 4-10 MCD 5000 RGU Front and Rear Panels (Example)
All rear connectors are RJ45 type except the DC IN, Footswitch,
REF, SPK and the ground pin.
The operator has an easy access to the MCD 5000 RGU connectors for
connecting the required cables.
Two MCD 5000 RGUs can be installed side by side on a standard 19" rack shelf, using
the FTN7490 MCD 5000 RGU Rack Mount Panel plus screws.
4-16
6802987C96-A
July 2011
MCD 5000 Deskset System with OMC Installation and Configuration Guide MCD 5000 Radio Gateway Unit (RGU) Front and Rear Panels Layout
Table 4-5 describes the MCD 5000 RGU front and rear panels shown in Figure 4-10.
Table 4-5 MCD 5000 RGU Front and Rear Panels Features
No.
1
Name
R1, R2, R3, R4
Description
Shows the attached radio state.
Green: Radio is in Transmit State
Red: Radio is in Receive State
No Light: Radio is in Idle State or no radio is attached
COMM
Shows the communication state.

Green: The MCD 5000 RGU maintains a good connection to one
or more MCD 5000 Desksets.
Blinking Green: Assigned talkpaths are yet to be established after
MCD 5000 RGU normal boot.
Red: Talkpath to the MCD 5000 RGU has been accidentally
disconnected or assigned talkpath was not established.
Blinking Red: There is a fault or no connection between the MCD
5000 RGU and the OMC.
No Light: The MCD 5000 RGU was not set to establish any
talkpath to radio.
PWR
Shows the MCD 5000 RGU Power state.

Green: The MCD 5000 RGU is powered from the DC PWR input,
or both from DC PWR and PoE LAN inputs and working properly.
Blinking Green: The MCD 5000 RGU is powered from the PoE
LAN Connection and working properly.
Red: The MCD 5000 RGU is powered up but not operational due to
unfinished reboot process.
Blinking Red: There is a malfunction within the MCD 5000 RGU.
No Light: The MCD 5000 RGU is not powered up.
12V DC
DC Input Voltage (DC PWR Jack).
Local O&M
Debugging (RJ45).
Ext. LAN-PoE
Public Ethernet & PoE (RJ45).
Int. LAN
Local Ethernet (RJ45).
R1-4W-E&M
Analog radio - Voice & E&M via internal input and output transformers
(RJ45).
R1-Comm
Connection for RS-232 Digital signaling to a radio (RJ45).
10
R2,3,4-4W-E&M
Analog radio - Voice & E&M (RJ45).
11
R2,3,4-Comm
Connections for RS-232 Digital signaling to a radio (RJ45).
For the MCD 5000 RGU connectors pinout, see Appendix E, "MCD 5000 Deskset and
MCD 5000 RGU Connectors Pinouts and Settings"
6802987C96-A
July 2011
4-17
Understanding Cables Color Coding
Understanding Cables Color Coding
A description of the cables to be attached to the MCD 5000 Deskset or MCD 5000 RGU connectors
can be seen in Figure 4-11 to Figure 4-14. These cable colors are in conjunction with the MCD
5000 Deskset and the MCD 5000 RGU colored connectors.
1.
Radio Cables: consist of 2 colors: one for the 4W-E&M connection and one for
the Comm connection. The radio connector is not colored.
2.
Headset Jack Box Cable (FKN8694): This cable connects the MCD 5000 Deskset to
the MCD 5000 Headset Jack Box. Each cable side has its own color.
3.
External LAN Cable (FKN8695): The cable side which is attached to the MCD
5000 Deskset or the MCD 5000 RGU is colored. This is done to mark the External
LAN connection (which is a non-secured IP Network).
4.
Internal LAN Cable (FKN8695): The cable side which is attached to the MCD
5000 Deskset or the MCD 5000 RGU is colored. This is done to mark the External
LAN connection (which is a secured IP Network).
5.
MCD 5000 Deskset Logger Cable (FKN8696): The cable includes an RJ45
colored connector to be connected to the MCD 5000 Deskset and an open-ended
side to be connected to the analog logger.
6.
Desktop Paddle Microphone includes its own cable. The Paddle microphone connector is not colored.
Figure 4-11 Cables Color Coding Radio Cable Type
Figure 4-12
4-18
Cables Color Coding Jackbox Cable Type
6802987C96-A
July 2011
Cabling the MCD 5000 RGU
Figure 4-13 Cables Color Coding LAN Cable Type
Figure 4-14
Cables Color Coding Logger Cable Type
Follow Procedure 4-4 to attach the cables to an MCD 5000 RGU.

Procedure 4-4
6802987C96-A
Cabling an MCD 5000 RGU
Place the MCD 5000 RGU on a horizontal surface.
Place the Power Supply near the MCD 5000 RGU on a safe horizontal surface.
Connect the MCD 5000 RGU to the site ground as described in Procedure 6-7,
"Grounding the MCD 5000 RGU," on page 6-16.
Connect the DC cable of the Power Supply unit to the DC Inlet of the MCD 5000
RGU. Make sure the cable is not routed with tension.
July 2011
4-19
Procedure 4-4 Cabling an MCD 5000 RGU (Continued)

5
Connect the proper radio cable Y cable side (the side with the two RJ45
connectors marked with blue and pink labels) to the MCD 5000 RGU RJ45
connectors marked with COMM blue and 4W E&M pink labels respectively.
Refer to "Cabling a Radio to an MCD 5000 RGU or MCD 5000 Deskset" on
page 4-21.
Connect the radio cable Radio side to the proper radio connector.
Connect the External LAN PoE cable to the MCD 5000 RGU. Attach the black
label from the FKN8695 cable kit to the cable side close to the MCD 5000 RGU
"External LAN PoE" connector. Attach the white label (from the FKN8695 cable
kit) marked with "PoE/LAN external" to the other side of the cable.
Connect the External LAN PoE cable (other cable side) to the site LAN outlet.
If the site LAN outlet includes an active PoE-PSE, the MCD 5000
RGU unit will be powered and start its booting process (PoE-PSE is
not supplied).
9
Connect the AC cord of the Power Supply unit to the AC wall mount power
If the AC line is alive, the MCD 5000 RGU unit will be powered and
start its booting process.
The MCD 5000 RGU can be connected to both AC power source and
PoE-PSE power source at the same time. The two power sources will
backup each other. Connecting the second power source will not
interrupt the MCD 5000 RGU operation.
10
Verify that the MCD 5000 RGU PWR LED turns RED (which indicates the MCD
5000 RGU booting state) and after a while, it turns GREEN.
If the MCD 5000 RGU PWR LED remains RED, refer to Chapter 7,
"MCD 5000 Deskset System Troubleshooting"
4-20
6802987C96-A
July 2011
Cabling a Radio to an MCD 5000 RGU or MCD 5000 Deskset
Cabling a Radio to an MCD 5000 RGU or MCD 5000 Deskset
The following is required to connect a radio:
A customer provided radio
A proper radio cable
Radios are normal mobile control stations of a given radio system, connected to one of the MCD
5000 RGU radio ports and placed in the coverage area of the radio system.
In this section, the MCD 5000 RGU or MCD 5000 Deskset are referred to as equipment.
The MCD 5000 RGU supports up to four Radio connections in a mix-and-match approach; each Radio can be
of a different Radio type. For the list of supported Radios, see Appendix F, "Radios Used With the MCD 5000
Deskset System".
The MCD 5000 Deskset supports one Radio connection. For the list of supported Radios, see
Appendix F, "Radios Used With the MCD 5000 Deskset System".
The MCD 5000 equipment to radio cable has:

Two RJ45 connectors to interface with the MCD 5000 equipment side: one RJ45 connector
for the 4W-E&M connection marked with a pink label and second RJ45 connector for
the SB9600 serial communication marked with a blue label.
A connector to interface the Radios accessory connection, each Radio with its own Radio
connector type that carries 4W-E&M and SB9600 communication.
Follow Procedure 4-5 to connect a radio to the MCD 5000 equipment.
Procedure 4-5
6802987C96-A
Connecting a Radio to the MCD 5000 Equipment
Connect the cables Radio Cable connector, depending on the radio type, to
the radio accessory connector.
Connect the cables RJ45 connectors for the 4W-E&M Deskset and the COMM
Deskset to either the MCD 5000 RGU Radio ports or the MCD 5000 Deskset port.
July 2011
4-21
Connecting an MCD 5000 Deskset to an SB9600 Radio in Parallel to MC3000
Connecting an MCD 5000 Deskset to an SB9600 Radio

in Parallel to MC3000
The purpose of this parallel connection is to add an MCD 5000 Deskset to an already existing MC3000
system (see Appendix H, "Cables Used for MCD 5000 Deskset Connection in Parallel to MC3000").
The following are required for this connection type:
A cable for interconnecting the MCD 5000 Deskset Unit in parallel with the MC3000 to the Radio
A customer-provided Digital Junction Box
A customer-provided radio
A customer-provided Radio Cable (attached to the customer radio)
Customer-provided MC3000 units
Connecting the MC3000 to the Digital Junction box is done according the to the Digital
Junction Box Installation and Troubleshooting Manual (6880309K29).
In this section, the MCD 5000 RGU or MCD 5000 Deskset are referred to as equipment.
The radio to MCD 5000 equipment in parallel with the MC3000 cable has:
Two RJ45 connectors to interface with the MCD 5000 equipment side: one RJ45
for the 4W-E&M connection marked with a pink label and second RJ45 for the
SB9600 serial communication marked with a blue label.
A connector to interface with the cable that runs to the radios accessory connection, each
Radio with its own Radio connector type that carries 4W-E&M and SB9600 communication.
Two connectors to the Digital Junction Box: One is connected to the Console/Deskset
port (RJ45) (connect to one of the free RJ45 front connectors) to allow the
MC3000 users to hear the MCD 5000 users on Tx, and one is connected to the
Digital Spectra or to the IDEN/MCS connector.
Follow Procedure 4-6 to connect the radio, the Digital Junction Box and the MCD 5000 equipment.
Procedure 4-6 Connecting the Radio, the Digital Junction Box and the MCD 5000 Equipment
1
4-22
Connect the cables Radio Cable connector, depending on the Radio type, to
the customer cable that is already hooked up to the radio accessory connector.
6802987C96-A
July 2011
MCD 5000 Deskset to an SB9600 Radio in Parallel to MC3000
Connecting an
(Continued)
2
Connect the cables DJB-Rear connector, depending on the Radio type, to the
relevant connector on the rear of the proper Digital Junction Box (see Digital
Junction Box Installation and Troubleshooting Manual (6880309K29)).
For CDM radio, keep the RJ45 to DB25 Adapter (3210761)

attached to the L3239 Digital Junction Box.
3
Operate the MC3000, Digital Junction box and the Radio and verify that these
devices are working properly.
Connect the cables RJ45 4W-E&M and the COMM connectors to the
4W-E&M and the COMM Deskset connectors according to "Cabling a Radio
to an MCD 5000 RGU or MCD 5000 Deskset" on page 4-21
The MCD 5000 RGU will be set up according to Chapter 6.
The CDM Digital Junction Box (L3239) and the MCS/Consolette Digital Junction Box
(L3208) are supplied and configured by the customer according to Digital Junction
Box Installation and Troubleshooting Manual (6880309K29).
Figure 4-15 shows the connection of an MCD 5000 Deskset in parallel to MC3000 units using DJB.
Figure 4-15 One MCD 5000 Deskset to SB9600 Radio in Parallel to MC3000
6802987C96-A
July 2011
4-23
Connecting Many MCD 5000 Desksets through MCD 5000 RGU to SB9600 Radio in Parallel to MC3000
4: Installing MCD 5000 Deskset System Units
Chapter
Connecting Many MCD 5000 Desksets through MCD 5000

RGU to SB9600 Radio in Parallel to MC3000
The purpose of this parallel connection is to add many MCD 5000 Desksets to an already existing MC3000
system.
The MCD 5000 RGU supports up to four Radio connections in a mix-and-match approach,
each Radio can be of a Radio different type. For the list of supported Radios, see Appendix F,
"Radios Used With the MCD 5000 Deskset System".
The following are required for this connection type:
A cable for interconnecting the MCD 5000 RGU in parallel with the MC3000 to the radio
A customer-provided Digital Junction Box
MCD 5000 RGUs
A customer-provided Radio
A customer-provided Radio Cable (attached to the customer radio)
Customer-provided MC3000 Units
Connecting the MC3000 to the Digital Junction box is done according to Digital Junction
The radio to MCD 5000 equipment in parallel with the MC3000 cable has:
Two RJ45 connectors to interface with the MCD 5000 equipment side: one RJ45
for the 4W-E&M connection marked with a pink label and second RJ45 for the
SB9600 serial communication marked with a blue label.
A connector to interface with the cable that runs to the radios accessory connection, each
Radio with its own Radio connector type that carries 4W-E&M and SB9600 communication.
Two connectors to the Digital Junction Box: One is connected to the Console/Deskset
port (RJ45) and one is connected to the Digital Spectra connector.
Follow Procedure 4-7 to connect the radio, the Digital Junction Box and the MCD 5000 equipment.
1
4-24
Connect the cables Radio Cable connector, depending on the Radio type, to
the customer cable that is already hooked up to the radio accessory connector.
6802987C96-A
July 2011
Desksets through MCD 5000 RGU to SB9600 Radio in Parallel to MC3000
Connecting Many MCD 5000
(Continued)
2
Connect the cables DJB-Rear connector, depending on the Radio type, to the
relevant connector on the rear of the proper Digital Junction Box (see Digital
Junction Box Installation and Troubleshooting Manual (6880309K29)).
For CDM radio, keep the RJ45 to DB25 Adapter (3210761)

attached to the L3239 Digital Junction Box.
3
Operate the MC3000, Digital Junction box and the Radio and verify that these
devices are working properly.
Connect the cables DJB-Cons.Port connector to one of the front connectors of

the proper Digital Junction Box.
Connect the cables RJ45 4W-E&M and to the COMM connectors to one
pair of the 4W-E&M and the COMM RGU connectors according to "Cabling
a Radio to an MCD 5000 RGU or MCD 5000 Deskset" on page 4-21.
Connecting a CDM radio to the MCD 5000 RGU in parallel with the MC3000,
requires use of the RJ45 to DC25 adaptor (3210761).
The CDM Digital Junction Box (L3239) and the MCS/Consolette Digital Junction Box
(L3208) are supplied and configured by the customer according to Digital Junction
Figure 4-16 shows the connection of MCD 5000 Desksets in parallel to MC3000 units using DJB.
6802987C96-A
July 2011
4-25
Connecting Many MCD 5000 Desksets through MCD 5000 RGU to SB9600 Radio in Parallel to MC3000
4: Installing MCD 5000 Deskset System Units
Chapter
Figure 4-16 Many MCD 5000 Desksets to SB9600 Radio in Parallel to MC3000
4-26
6802987C96-A
July 2011
Chapter
5
Installing the Administrator Control Panel
Client PC
This chapter provides detailed information about the Administrator Control Panel (ACP) Client PC, including
hardware and software installation instructions. This chapter includes the following topics:
6802987C96-A
July 2011
"ACP Client PC Functional Description" on page 5-2.
"ACP Client PC Physical Description" on page 5-2.
"ACP Client PC Location and Layout" on page 5-4.
"ACP Client PC Cabling" on page 5-4.
"Installing Software on the ACP Client PC" on page 5-4.
5-1
ACP Client PC Functional Description
ACP Client PC Functional Description
The Administrator Control Panel (ACP) is a Microsoft Windows 7 (64 bit) application that runs on a client PC
connected to the MCD 5000 Deskset System LAN. The ACP Client PC is the interface to the Operations
Management Center (OMC) Server and allows the operator to perform system management activities as
determined by the operators service class. Up to 10 ACP Client PCs can interface with one OMC Server
simultaneously. The ACP Client PC can be located anywhere that has secure access to the IP network.
The following administrative functions can be performed on an MCD 5000 Deskset System using the ACP:
System structure configuration - Enables an MCD 5000 system administrator to

set the structure of the system, including regions, counties, Public Safety Answering
Points (PSAPs), agencies, and resource groups.
User provisioning - Enables an MCD 5000 system administrator to add or remove system
users and assign or change user privileges. Nine user privilege levels are supported.
Resource configuration - Enables an MCD 5000 system administrator or technician to add or

remove a gateway unit to or from the system, and to define or update gateway unit attributes.
Performance monitoring - Enables an MCD 5000 system administrator to continuously

monitor (online) and analyze (offline) the network quality of service.
Fault management - Enables an MCD 5000 system administrator to monitor gateway

unit health and provides an alarm on permanent malfunction.
Radio connection management - Enables an MCD 5000 system administrator to view MCD
5000 Deskset to Radio connections. Eight Push ToTalk (PTT) priority levels are supported.
Software load management - Enables an MCD 5000 system administrator or technician

to install new gateway unit software versions on the specified MCD 5000 Deskset or
MCD 5000 RGUs and remove old software versions from the system.
System parameter management - Enables an MCD 5000 system administrator or technician

to install new system parameter versions on specified gateway units.
This manual describes the functions performed on the ACP Client PC. For details about functions performed on
the ACP Client PC, refer to MCD 5000 Deskset System Administrator Control Panel User Guide (6802987C99).
ACP Client PC Physical Description
The ACP client PC should meet the following minimum system requirements:
5-2
Processor: Dual Core E2180
Memory: 4 GB
6802987C96-A
July 2011
Free space on hard disk: 4 GB
Network adapter with LAN: 10/100 Mbps
Screen resolution: 1024x768
Operating system: Windows 7 (64 bit)
ACP Client PC Physical Description
Figure 5-1 shows the front view of the ACP Client PC.
Figure 5-1
ACP Client PC - Front View
Figure 5-2 shows the rear view of the ACP Client PC.
Figure 5-2
6802987C96-A
July 2011
ACP Client PC - Rear View
5-3
ACP Client PC Location and Layout
ACP Client PC Location and Layout
The ACP Client PC can be located anywhere where it has secure access to the IP network.
ACP Client PC Cabling
The ACP Client PC has the following connections:
The monitor for the PC is attached using the monitor cable.
The keyboard and mouse for the PC are attached using their respective cables.
The PC is attached to the switch using a LAN cable.
The power supply for the PC is attached to a power source using the power cord.
Installing Software on the ACP Client PC
The ACP Client PC is normally shipped with Windows 7 and the Microsoft MapPoint application pre-loaded.
MCD 5000 ACP software should be installed by the customer. If the Microsoft Map Point application
software needs to be reloaded, refer to "Installing Microsoft MapPoint Software" below. To install MCD 5000
ACP application, follow Procedure 5-1, "Installing the ACP Software on the ACP Client PC," on page 5-5.
Installing Microsoft MapPoint Software

The ACP software works with Microsoft MapPoint software to provide a map-based representation of
your MCD 5000 Deskset System. Before you install the ACP software, you must install Microsoft
MapPoint software. Install Microsoft MapPoint software on the ACP Client PC according to manufacturer's
instructions. Start the MapPoint application once and then close the application.
5-4
6802987C96-A
July 2011
Installing the ACP Software

Follow Procedure 5-1 to install the ACP software on the ACP Client PC.
Procedure 5-1 Installing the ACP Software on the ACP Client PC
1
Place the MCD 5000 Administrator Control Panel CD in your

CD-ROM drive. Assuming the CD-ROM drive is E:\, double-click the
E:\MCD5000-ACPSetup.exe file.
Result: The Motorola MCD 5000 ACP Setup Welcome screen opens.
Click Next.
Result: The End-User License Agreement window opens.
Read the license agreement and then click Yes.

Result: The Select Destination directory window opens.
Ensure that the correct location for installation of the ACP program appears in
the topmost box and click Next.
Result: The Installing MCD 5000 ACP Window opens and the software is
installed and then the Setup Finished window opens.
Click Finish.
Result: The ACP program is installed and a shortcut appears on the desktop.
6802987C96-A
July 2011
5-5
5-6
6802987C96-A
July 2011
Chapter
6
Administering your System with the
Configuration Tool
The Configuration Tool application is designed to run on a technician PC and is used to configure a GU (MCD
5000 Deskset or MCD 5000 RGU) and perform audio monitoring tasks when the technician is at the site
where the GU is located. You can also add a new GU to the system using the Configuration Tool.
To use the Configuration Tool, a technician must first load the application onto the PC. The application is
available for installation on the CD supplied with the system (FVN5847A). Next, the technician must download
the latest version of the system parameters by connecting the PC to the network, accessing the OMC Server,
and creating the technician profile, which ensures that the most current system parameters are loaded on the PC.
The system parameters load is used as a starting point for configuring the GU or performing audio monitoring
tasks, tasks that are accomplished by connecting the PC directly to the GU and using the Configuration Tool.
This chapter provides procedures for:
"Installing the Configuration Tool" on page 6-1.
"Accessing the OMC Server and Creating the Technician Profile" on page 6-2.
"Configuring Gateway Units with the Configuration Tool" on page 6-8.
"CT Application Settings" on page 6-58.
"Monitoring Your System with the Configuration Tool" on page 6-62.
"Managing GU Software Loads with the Configuration Tool" on page 6-81.
"Programming Radio Buttons with the Configuration Tool" on page 6-84.
Installing the Configuration Tool
The Configuration Tool application requires a PC with the following minimum system requirements:
6802987C96-A
July 2011
Processor: Dual Core E2180
Memory: 4 GB
Free space on hard disk: 4 GB
6-1
Network adapter with LAN: 10/100 Mbps
Screen resolution: 1024x768
Operating system: Windows 7 (64 bit)
For best results, set the Start menu properties to Classic Start Menu.
The Configuration Tool is available for installation on the CD supplied with the system (FVN5847A).
Follow Procedure 6-1 to install the Configuration Tool application on the technician PC.
Procedure 6-1
1
Installing the Configuration Tool Application on the Technician PC
To install the application from the CD supplied with the system, insert the CD
into the CD drive.
Result: The application installation begins automatically. The Motorola MCD
5000 Deskset System with OMC-CT Setup Welcome screen opens.
Click Next.
Result: The End-User License Agreement window opens.
Click Yes to accept the terms of the license agreement.

Result: The Select Destination Directory window opens.
Ensure that the correct location for installation of the Configuration Tool software
appears in the topmost box and then click Next.
Result: The Installing MCD 5000 Deskset System with OMC Configuration
Tool window opens and the software is installed and then the Setup Finished
window opens.
Click Finish.
Result: The Configuration Tool program is installed and a shortcut icon appears
on the PC desktop.
Accessing the OMC Server and Creating the Technician

Profile
After installing the Configuration Tool on your PC, you must access the OMC Server and create a technician
profile. Creating a technician profile loads the most current default system database onto your PC. This
database is used as a starting point for configuring or adding a GU or performing audio monitoring tasks.
Follow Procedure 6-2 to access the OMC Server and create the technician profile.
6-2
6802987C96-A
July 2011
To access the active OMC Server, you must know its IP address.
Before performing Procedure 6-2 you must connect the CT PC to the MCD 5000 IP network / LAN.
SUGGESTION
An administrator can create a technician profile using the Administrator Control Panel
(ACP), for distribution to technicians using the network or a CD-ROM. See the MCD 5000
Deskset System Administrator Control Panel User Guide (6802987C99).
Procedure 6-2 Accessing the OMC Server and Creating the Technician Profile
1
Double-click the MCD 5000 System with OMC CT icon on the desktop.
Result: The MCD 5000 with OMC Configuration Tool main window opens.
Figure 6-1 MCD 5000 with OMC Configuration Tool Main Window Disconnected
Click the yellow lightning bolt icon to log in to the OMC Server.
Result: The Connect to OMC window opens.
Figure 6-2
6802987C96-A
July 2011
Configuration Tool - Connect to OMC Window
6-3
Procedure 6-2 Accessing the OMC Server and Creating the Technician Profile (Continued)
3
Type your user name in the User Name field. Type your password in the
Password field. Type the IP address of the OMC Server to which you want to
connect in the OMC IP Address field. Click Connect.
Result: The Configuration Tool main window shows the OMC Server IP address
and the status as Active in the title bar. Now the yellow lightning bolt has two
black bars running through it, which indicates that you are connected to the OMC
Server. In the bottom row, User <user ID> connected to OMC indicates that
you are connected to the OMC Server.
Figure 6-3 Configuration Tool Main Window - Connected to OMC
On the menu bar, click OMC, and then click Create Technician Profile.
Result: The Create Technician Profile message
Would you like to download GU configuration files from OMC
server?
appears.
If the technician profile is already created, the message window

Technician profile already exists.
create new?
Do you want to
appears. Click Yes to create a new profile.

Figure 6-4 Configuration Tool - Create Technician Profile Message
Window
6-4
6802987C96-A
July 2011
5
Click Yes.
Result: The Create Technician Profile - Step 1 of 3 (Download GU Configuration
Files) dialog box appears. The GU Configuration Files box shows all GU
configuration files on the technician PC. The OMC Server box shows all GU
configuration files available on the OMC Server.
Figure 6-5 Create Technician Profile - Step 1 of 3 (Download GU
Configuration Files) Dialog Box
Perform the following:

To download all GU configuration files from the OMC Server to the System
with OMC CT PC, click the << Copy All button.
To copy certain GU configuration files from the OMC Server, select the
GU configuration files in the OMC Server list, and then click the < Copy
button.
To remove GU configuration files from your computer, select the GU
configuration files from the GU Configuration Files list and click the
Remove Selected Files button.
Click the Next button.
Result: The Create Technician Profile - Step 2 of 3 (Download GU Software
Versions) dialog box appears. The GU Software Versions box shows all GU
software versions on the PC. The OMC Server box shows all GU software
versions available on the OMC Server.
6802987C96-A
July 2011
6-5
Figure 6-6 Create Technician Profile - Step 2 of 3 (Download GU

Software Versions) Dialog Box
Perform the following:

To download all GU software versions from the OMC Server to the System
with OMC CT PC, click the << Copy All button.
To download only selected versions from the OMC Server, select the
versions you want to download in the OMC Server list and click the <Copy
button.
To remove some of the GU software versions from your computer, select
them in the GU software versions list and click the Remove Selected Files
button.
Click the Finish button.
Result: The Create Technician Profile message window opens, informing you
that the technician profile was successfully created and the location on the System
with OMC CT PC, where it can be found.
Downloading files from the OMC server can take time, depending on
the network bandwidth and the amount of data to copy.
8
Click Yes.
Result: GU software versions are downloaded from the OMC Server. The Create
Technician Profile message window opens with the message
GU Software Versions successfully downloaded.
6-6
6802987C96-A
July 2011
9
Click the Next button.

Result: The Create Technician Profile - Step 3 of 3 (Download Radio alias
database) dialog box appears. The Radio alias database Files box lists all the
Radio alias database files on the System with OMC CT PC. The OMC Server
box shows all Radio alias database files available on the OMC Server.
Figure 6-7 Create Technician Profile - Step 3 of 3 (Download Radio
Alias Database Files) Dialog Box
10
To download all Radio alias database files from the OMC Server to the System
with OMC CT Client PC, click the << Copy All button. To copy certain Radio
alias database files from the OMC Server, select the Radio alias database files in
the OMC Server list and click the < Copy button. To remove some of the Radio
alias database files from your computer, select the Radio alias database files in
the Radio alias database files list and click the Remove Selected Files button.
11
Click the Finish button.

Result: The Create Technician Profile message window opens, displaying the
message that the technician profile was successfully created. It also displays the
location of the profile on the System with OMC CT PC.
Figure 6-8 Create Technician Profile Message Window
12
6802987C96-A
July 2011
Click OK to return to MCD 5000 with OMC CT main window.
6-7
Configuring Gateway Units with the Configuration Tool
Configuring Gateway Units with the Configuration Tool
The base set of system parameters are configured for each Gateway Unit (GU) at the factory. As
a technician, you may need to make modifications to the existing GU configuration. This section
shows you how to configure a GU using the Configuration Tool. You can also configure a GU using
the Administrator Control Panel (ACP). For details on configuring GUs with the ACP, refer to MCD
5000 Deskset System Administrator Control Panel User Guide (6802987C99).
This section provides the following procedures for configuring gateway units with the Configuration Tool:
"Entering User Credentials" on page 6-8.
"Configuring a GU External LAN IP through Internal LAN" on page 6-9.
"Installing New MCD 5000 Deskset System Units" on page 6-14.
"Grounding the MCD 5000 RGU" on page 6-16.
"Connecting to a GU" on page 6-17.
"Adding a GU" on page 6-21.
"Modifying a GU Configuration" on page 6-22.
"Viewing GU System Parameters" on page 6-33.
"Configuring System Parameters for an Individual GU" on page 6-36.
"Cloning a GU Configuration to Another GU" on page 6-43.
"Copying a GU Configuration" on page 6-47.
"Saving a GU Configuration to a File" on page 6-52.
"Resetting a GU" on page 6-55.
"Removing a GU" on page 6-56.
Entering User Credentials

User credentials are requested each time the application connects to a GU to add or modify the GU
configuration, or to modify audio monitoring settings. Once the user has entered the credentials and the
authentication succeeds, credentials will be sent automatically without asking the user to enter them
again. If authentication fails, the user will be requested to enter the credentials again.
Procedure 6-3 Entering User Credentials
1
When adding/modifying the GU or modifying audio monitoring settings, the

user credentials may need authentication. In this case, the user clicks on the
desired operation.
Result: The Enter User Credentials Window appears.
6-8
6802987C96-A
July 2011
Configuring a GU External LAN IP through Internal LAN
Procedure 6-3 Entering User Credentials (Continued)

Figure 6-9 Enter User Credentials Window
Enter the User Name and User Password. By default the user name is "tech" and
the password is "ABCD123456efgh*".
Result: The identification with the GU(s) begins.
1. If the identification is successful, the required operation continues.
2. If the identification fails, the following error message is displayed and the
user is asked to re-enter the User Name and Password.
Figure 6-10 User Credentials Failed

After you have installed the Configuration Tool application on your technician PC, follow Procedure
6-4 to configure the External LAN (external) IP for each GU in your system.
Procedure 6-4 Configuring a GU External LAN IP Through Internal LAN
6802987C96-A
Install the Gateway Unit using procedures Procedure 6-5, "Installing a New MCD
5000 RGU Unit with Internal LAN Connection," on page 6-14 and Procedure
6-6, "Installing a New MCD 5000 Deskset Unit with Internal LAN Connection,"
on page 6-15.
Connect the technician PC directly to a GU using Procedure 6-8, "Connecting

Directly to a GU," on page 6-17.
July 2011
6-9
Procedure 6-4 Configuring a GU External LAN IP Through Internal LAN (Continued)
The connection should be performed according to the following

figures.
Figure 6-11 MCD 5000 Deskset Connection
Figure 6-12 MCD 5000 RGU Connection
Result: The MCD 5000 system with OMC CT main window displays a list of
resources defined on the connected GU.
6-10
6802987C96-A
July 2011

Figure 6-13 Configuration Tool Main Window - Connected to GU
Press Modify GU Configuration on the CT main window.

Result: The Modify Gateway Unit Configuration dialog box appears, with the
General Properties tab active.
6802987C96-A
July 2011
6-11

Figure 6-14 Modify MCD 5000 Gateway Unit Configuration Dialog Box General Properties Tab
On the Modify Gateway Unit Configuration Dialog Box select the IP

Configuration tab.
Result: The IP Configuration tab opens.
6-12
6802987C96-A
July 2011

Figure 6-15 Modify Gateway Unit Configuration Dialog Box - IP
Configuration Tab
Type in the desired IP address, netmask and Default Gateway IP address (if using
WAN) for the connected MCD 5000 RGU or MCD 5000 Deskset.
Result: The Are you sure you want to apply current configuration? message
opens.
Click Yes.
Result: The GU Notification message window opens.
Figure 6-16
GU Notification Message Window
Click OK.
Result: Gateway Unit IP configuration is changed and the GU restarts.
6802987C96-A
Repeat step 1 through step 6 for each MCD 5000 RGU/MCD 5000 Deskset you
have in your system.
When you have no other GU External LAN ports to configure through the
internal IP, re-enter MCD 5000 system unique IP and netmask in your PC.
July 2011
6-13
Installing New MCD 5000 Deskset System Units

9
Connect one end of the cable to External LAN port on the bottom panel of the
MCD 5000 Deskset or on the back panel of the MCD 5000 RGU and the other
end to the network switch, as shown below.
Figure 6-17
MCD 5000 Deskset External Connector
Figure 6-18 MCD 5000 RGU External Connector
10
Ping each of the configured, refer to Procedure 7-1, "How to Ping a Gateway Unit
on the External LAN," on page 7-11

Follow the procedures below to install new MCD 5000 Deskset System units.
Procedure 6-5 Installing a New MCD 5000 RGU Unit with Internal LAN Connection
6-14
Place the MCD 5000 RGU on a horizontal surface.
Place the Power Supply near the MCD 5000 RGU on a safe horizontal surface.
Connect the MCD 5000 RGU to the site ground as described in Procedure 6-7,
"Grounding the MCD 5000 RGU," on page 6-16.
Connect the DC cable of the Power Supply unit to the DC Inlet of the MCD 5000
RGU. Make sure the cable is not routed with tension.
6802987C96-A
July 2011
Procedure 6-5 Installing a New MCD 5000 RGU Unit with Internal LAN Connection (Continued)
5
Connect the Internal LAN cable to the MCD 5000 RGU. Attach the Red label
from the FKN8695 cable kit to the cable side close to the MCD 5000 RGU
"Internal LAN" connector. Attach the white label (from the FKN8695 cable kit)
marked with "LAN Internal" to the other side of the cable.
Figure 6-19 MCD 5000 RGU Connection
Verify that the MCD 5000 RGU PWR LED turns RED (which indicates the MCD
5000 RGU booting state), and that after a while, it turns GREEN.
If the MCD 5000 RGU PWR LED remains RED, refer to Chapter 7,
"MCD 5000 Deskset System Troubleshooting".
Procedure 6-6
6802987C96-A
Installing a New MCD 5000 Deskset Unit with Internal LAN Connection
Place the MCD 5000 Deskset on a horizontal surface.
Place the Power Supply near the MCD 5000 Deskset on a safe horizontal surface.
Connect the Handset cable to the MCD 5000 Deskset and to the handset.
Connect the DC cable of the Power Supply unit to the DC Inlet of the unit. Make
sure the cable is not routed with tension.
Connect the Internal LAN cable to the MCD 5000 Deskset. Attach the Red label
from the FKN8695 cable kit to the cable side close to the MCD 5000 Deskset
"Internal LAN" connector. Attach the white label (from the FKN8695 cable kit)
marked "LAN Internal" to the other side of the cable.
July 2011
6-15
Grounding the MCD 5000 RGU
Procedure 6-6 Installing a New MCD 5000 Deskset Unit with Internal LAN Connection (Continued)
Figure 6-20 MCD 5000 Deskset Connection
Verify that the MCD 5000 Deskset topside LEDs turn on (which indicates the
Deskset booting state), and that after a while, they turn off.
Observe the MCD 5000 Deskset main screen for any fault messages.
Grounding the MCD 5000 RGU

The MCD 5000 RGUs must be grounded to the rack with the grounding screw on the back panel. To use the
grounding screw, use the grounding wire included as part of the MCD 5000 RGU power supply kit.
Follow Procedure 6-7 to ground the MCD 5000 RGU.
Procedure 6-7 Grounding the MCD 5000 RGU
1
6-16
Connect one end of the grounding wire to one of the grounding screws at the
back panel of the MCD 5000 RGU. Install the spring washer and the nut. Tighten
the nut.
6802987C96-A
July 2011
Connecting to a GU
Procedure 6-7 Grounding the MCD 5000 RGU (Continued)

2
Connect the other end of the grounding wire to the site grounding port.
The MCD 5000 Deskset does not require grounding.
Connecting to a GU
After installing the Configuration Tool application and creating a technician profile on your PC, connect
to a GU to perform various configuration tasks in any of the following two ways:
Direct connection, where the technician PC is connected directly to the GU through the
Internal LAN port on the GU and the Ethernet port on the PC. Direct connection works
with the internal IP address set in the GU which is always 10.0.0.1.
Network connection, where the technician PC is indirectly connected to the GU using

a LAN. Network connection works with the external IP address for the GU which is
configurable according to the PSAP where the GU is located.
Follow Procedure 6-8 to connect the technician PC directly to a GU.

Procedure 6-8 Connecting Directly to a GU
1
Install the new MCD 5000 Deskset unit via internal LAN:
To install an MCD 5000 RGU unit, follow Procedure 6-5, "Installing a New
MCD 5000 RGU Unit with Internal LAN Connection," on page 6-14.
To install an MCD 5000 Deskset, follow Procedure 6-6, "Installing a New MCD
5000 Deskset Unit with Internal LAN Connection," on page 6-15.
Ensure that the IP address of your technician PC is 10.0.0.2 and that of the
netmask is 255.255.255.248.
6802987C96-A
July 2011
6-17
Connecting to a GU
Procedure 6-8 Connecting Directly to a GU (Continued)

Figure 6-21 MCD 5000 with OMC Configuration Tool Main Window
- Disconnected
Click the Read from GU icon in the tool bar.

Result: Configuration information about the GU appears in the Configuration
Tool main window.
If the message
No response from Gateway Unit 10.0.0.1
opens or the Error! window opens with the error message

Failed to connect to Gateway Unit 10.0.0.1 ,
the PC is not connected to the Internal LAN port or has a bad network
configuration. Do not attempt to enter any other IP address because
only 10.0.0.1 is correct.
6-18
6802987C96-A
July 2011
Connecting to a GU
Procedure 6-8 Connecting Directly to a GU (Continued)

Follow Procedure 6-9 to connect the technician PC to a GU using a LAN.

Procedure 6-9 Connecting to the GU Using a LAN
1
Attach the technician PC to the LAN using an Ethernet cable. Connect one end
of the cable to the LAN switch or router and the other end to the Ethernet port
on the technician PC.
6802987C96-A
July 2011
6-19
Connecting to a GU
Procedure 6-9 Connecting to the GU Using a LAN (Continued)

3
In the tool bar on the Configuration Tool main window, click the Change Local
IP icon.
Result: The Change Local Mode GU IP window opens.
Figure 6-23 Configuration Tool - Change Local Mode GU IP Window
In the Gateway Unit IP field, type the IP address of the gateway unit to which
you want to connect, and then click OK.
Result: The Configuration Tool is connected to the GU you specified.

Tool main window.
If you see the message

No response from Gateway Unit X.X.X.X
opens, or the error message

Failed to connect to Gateway Unit X.X.X.X
check the PC network configuration and make sure it is connected

to the network. Also check the GU to which you are trying to
connect, to make sure that it has the correct IP address and network
configuration, and that the GU is connected to the network.
6-20
6802987C96-A
July 2011
Adding a GU
Procedure 6-9 Connecting to the GU Using a LAN (Continued)
Adding a GU
Follow Procedure 6-10 to add a GU to the network.
Procedure 6-10 Adding a GU
6802987C96-A
Connect to the GU you want to add. See "Connecting to a GU" on page 6-17
for details.
Perform the procedure "Modifying a GU Configuration" on page 6-22.
When you have finished performing the procedure, click the Add GU to MCD
5000 button.
July 2011
6-21
Modifying a GU Configuration
Procedure 6-10 Adding a GU (Continued)

4
Click OK to close the confirmation dialog box.
Follow Procedure 6-11 to modify a GU configuration.
Procedure 6-11
Connect to the desired GU. See "Connecting to a GU" on page 6-17 for details.
On the Configuration Tool main window, click the Read from GU icon on
the tool bar.
Tool main window. The Modify GU Configuration button is now active.
Click the Modify GU Configuration button.

6-22
6802987C96-A
July 2011
Procedure 6-11
Modifying a GU Configuration (Continued)
Figure 6-26 Modify MCD 5000 Gateway Unit Configuration Dialog Box
- General Properties Tab
If this is an MCD 5000 RGU, then the dialog box looks as follows:
6802987C96-A
July 2011
6-23
Procedure 6-11
Figure 6-27 Modify Radio Gateway Unit Configuration Dialog Box

General Properties Tab
On the General Properties tab you can modify the following fields:
Gateway Unit type: It is either MCD 5000 Deskset or MCD 5000 RGU.
Region: It is the region affiliated with the GU.
County: It is the county affiliated with the GU.
Agency: It is the agency affiliated with the GU.
PSAP: The Public Safety Answering Point affiliated with the GU.
Jitter Buffer: It is the amount of delay in milliseconds added to voice
packets so that all packets appear to be received without delay. This
number is determined by the IP provider.
6-24
6802987C96-A
July 2011
Procedure 6-11
You can clone another GU's configuration to this GU, see "Cloning
a GU Configuration to Another GU" on page 6-43 for details. You
can copy another GU's configuration to this GU, see "Copying a GU
Configuration" on page 6-47 for details.
When modifying the MCD 5000 GU, you cannot change the GU type
to Radio GU. When modifying the Radio GU you cannot change
the GU type to MCD 5000 GU.
5
When you have finished making changes on the General Properties tab, do one
of the following:
If you are configuring an MCD 5000 RGU, proceed to step 9.
If you are configuring an MCD 5000 Deskset, click the MCD 5000
Properties tab.
Result: The MCD 5000 Properties tab opens.
6802987C96-A
July 2011
6-25
Procedure 6-11
Figure 6-28 Modify Gateway Unit Configuration Dialog Box - MCD

5000 Properties Tab
In the MCD 5000 Properties tab you can modify the following fields:
Resource Name: Type the name of the gateway unit.
Cross Busy Unmute Timer: Defines the time on the MCD5000 Deskset
between releasing PTT by the dispatcher and the UNMUTE of all radios
with the same Cross Mute Index.
Max PTT Duration Timer: Defines the maximal time that the dispatcher
can press and hold the PTT button.
Desk Microphone: If checked, an external microphone is connected to
the MCD 5000 external input, and will be used as active input when the
handset is on hook. When the handset is off hook, then the microphone of
the handset is used as active input.
6-26
6802987C96-A
July 2011
Procedure 6-11
If checked, please ensure that the microphone is connected to the

MCD 5000. Otherwise, when the handset is on hook there will
be no actual voice input.
Polarity: Active high /Active low.
Audio Settings: At the bottom of the dialog include the following
parameters:
Internal audio settings: Input and output gain;
Handset: Input, output, echo gain;
Headset: Input, output, echo gain;
External: Input, output gain.
You can click the Default button to set default values for the items
in this tab.
Click the Assign Access Control Group button.
Result: The Select Group dialog box appears.
Figure 6-29 Configuration Tool - Select Group Dialog Box
6802987C96-A
July 2011
6-27
Procedure 6-11
7
In the Available Groups list, select the resource groups to which you want this
MCD 5000 Resource to be associated and click the Add button or click the Add
all button to associate this MCD 5000 Resource to all resource groups.
You can associate up to 20 resource groups to each resource.

If you want to remove the MCD 5000 Resource from a resource group, select
the group in the Chosen Groups list and click the Remove button or click the
Remove all button to remove the MCD 5000 Resource from all resource groups.
Click OK when you have finished making changes on this window.
Result: You return to the MCD 5000 Resource Properties tab.
8
When you are finished making changes in the MCD 5000 Resource Properties
tab, proceed to step 14.
If you are configuring an MCD 5000 RGU, click the Radio Resource Properties
tab.
Result: The Radio Resource Properties tab opens.
Figure 6-30 Modify Gateway Unit Configuration Dialog Box - Radio
Resource Properties Tab
6-28
6802987C96-A
July 2011
Procedure 6-11
10
In the Radio Resource Properties tab you can modify the following fields for
each radio by selecting the port number in the Port column:
On/Off: Set the desired radio ports ON or OFF. Ensure that a radio is
connected to any ports marked ON.
Radio Name: Type the name of the radio.
Type: Select the type of radio - 4 Wire E&M (used for MaxTrac and
non-Motorola radios), MCS2000 type III, CDM 1550, ASTRO Consolette
(W9).
RF Mode: Select Conventional or Trunked.
RF Cross Mute index: Enter a number between 0 and 255, where 0 means
that the Radio does not belong to any Cross Table.
Click the Assign Access Control Group button.
Result: The Select Group dialog box appears.
Figure 6-31 Configuration Tool - Select Group Dialog Box
11
In the Available Groups list, select the resource groups to which you want this
radio to be associated and click the Add button or click the Add all button to
associate this radio to all resource groups. You can associate up to 20 resource
groups to each radio. If you want to remove the radio from a resource group,
select the group in the Chosen Groups list and click the Remove button or click
the Remove all button to remove the radio from all resource groups. Click OK
when you have finished making changes on this window.
Result: You return to the Radio Resource Properties tab.
12
Click the Advanced button.

Result: The Advanced Radio Resource Properties window opens.
6802987C96-A
July 2011
6-29
Procedure 6-11
Figure 6-32
Advanced Radio Resource Properties Window
Complete the following fields in the Main Advanced Radio properties:

Voice Detection Mode: Select the method the MCD 5000 RGU uses to
detect incoming audio from the radio:
VAD (Voice Activity Detector): The DSP detects changes in
energy and determines that there is speech when the change is over
the VAD threshold.
Protocol based: The Radio provides a data message (in some
protocol) that is used like a signal for Start/End of receiving.
Direct COR: The Radio provides a separate physical line for
Start/End of receiving signaling.
Status Tone: The Radio provides constant tone when the radio
is not receiving. This tone disappears during receiving. Thus the
MCD 5000 RGU can distinguish Start/End of the receiving period.
Status Tone & VAD: Both Status Tone and VAD (see options
above) are used to detect voice.
The voice detection mode selection depends on the radio type. For
MCS2000 Type III, CDM 1550, and ASTRO Consolette (W9) radios use
either VAD or Protocol Based.
6-30
6802987C96-A
July 2011
Procedure 6-11
COR Polarity and Rebounce(ms) : Rebounce of 40ms will filter/ignore

changes on COR line that occur during less than 40ms. Rebounce sensitivity to the changes on COR line.
VAD Threshold:
Level (db): Type the minimum number of decibels required to
detect audio; defaults to the recommended value
Spike Filter:
-
Spike Width: The maximum width of spike that has to be

filtered.
Activation Window: The length of time window during

which VAD mechanism will be insensitive to noise spikes.
Status Tone Timeout: Absence of Status Tone for more than "timeout
value" will cause an alarm to be sent.
Discriminator Gain: Select the discriminator volume, which increases
as the slider is moved to the right. The discriminator takes voice or data
information received by the radio from the air at various frequencies, and
recasts it into digital samples.
Modulator Gain: Select the modulator volume, which increases as the
slider is moved to the right. The modulator takes voice or data information
and superimposes it onto a radio frequency (RF) carrier so that it can
transmit at various frequencies.
Selective Call Enabled: Indicates that the Radio Resource is configured
to use the Selective Call feature configured in the Configuration Tool,
Programmable Buttons configuration.
Radio without Control Head: Check this box to add the option of the
MCD 5000 RGU to send a press PTT SB9600 protocol message in addition
to the hardware PTT press.
Received Voice Decay Time: Refers to the gaps between words. Only if
speech is not recognized by the VAD for a time over this parameter, then it
determines the speech has ended. The received voice decay time is added
at the end of the voice session. This parameter is also communicated to the
receiving side where the warm-up buffer can discard the length of this
buffer at the end of transmission; defaults to the recommended value.
13
Click Apply when you have finished making changes to this window.
Result: You return to the Modify Gateway Unit Configuration dialog box, Radio
Resource Properties tab. If you are configuring an MCD 5000 RGU, proceed to
step 14.
14
When you are finished making changes in the other tabs, click the IP
Configuration tab.
Result: The IP Configuration tab opens.
6802987C96-A
July 2011
6-31
Procedure 6-11
Figure 6-33 Modify Gateway Unit Configuration Dialog Box - IP

Configuration Tab
On the IP Configuration tab you can modify the following fields:

IP Address: Type the IP address of the gateway unit.
Subnet Mask: Type the subnet mask of the gateway unit.
Default Gateway: Type the default gateway address for the gateway unit.
Speed and Duplex: Choose the appropriate network parameters from
the combo-box: 10 Mbps Full/Half duplex, 100 Mbps Full/Half Duplex
or Auto settings.
15
When you are finished making changes on the IP Configuration tab, click Apply.
Result: The
Are you sure you want to apply current configuration
message opens.
Click Yes.
Result: The GU Notification message window opens.
Figure 6-34 GU Notification Message Window
6-32
6802987C96-A
July 2011
Procedure 6-11
16
Viewing GU System Parameters
Click OK. Depending on the modifications made, talkpaths may be removed

and/or the GU may be reset.

You can view the system parameters activated for a GU. Follow Procedure 6-12 to view GU system parameters.
Procedure 6-12 Viewing GU System Parameters
1
Connect to the desired GU. Refer to "Connecting to a GU" on page 6-17 for
details.
Click the Read from GU icon in the tool bar on the Configuration Tool main
window.
6802987C96-A
July 2011
6-33
Procedure 6-12 Viewing GU System Parameters (Continued)

3

Click the Modify System Parameters button.

Result: The System Parameters dialog box will be opened, where you can view
the system parameters activated for the GU including the Main/Secondary OMC,
Talkpath and QoS parameters.
If the system parameters saved in the GU, differ from the system
parameters stored in the OMC Server, the message
System Parameters are not updated.
update them?
Do you want to
appears. Click No, to view the system parameters existing on the GU.
6-34
6802987C96-A
July 2011
Procedure 6-12 Viewing GU System Parameters (Continued)

Figure 6-36
System Parameters Dialog Box
Navigate through the sites to view the parameters. When finished click Cancel
button to close the System Parameters dialog and return to return to the Modify
GU Configuration dialog.
Changing the OMC main or secondary IP address can have

detrimental effects on the system. Therefore only statewide and
regional administrators and Motorola technician can change these
parameters. To save the changes - click OK.
Result: The Modify System Parameters dialog closes and returns to the
Modify GU dialog box.
6802987C96-A
July 2011
6-35
Configuring System Parameters for an Individual GU

System parameters are usually set for the entire system. However, you might need to configure system
parameters for an individual GU if you want to control or check a parameter change. If you want to change a
specific parameter, you can test the parameter on a GU that is physically nearby and control its operation. If
the parameter performs correctly, then you can issue a new set of system parameters to all GUs in the system.
Follow Procedure 6-13 to configure system parameters for an individual GU with the Configuration Tool
Procedure 6-13 Configuring System Parameters for an Individual GU
1
Connect to the desired GU. Refer to "Connecting to a GU" on page 6-17 for details.
Click the Read from GU icon in the tool bar on the Configuration Tool main window.
Result: Configuration information about the GU appears in the Configuration Tool main
window. The Modify GU Configuration button is now active.
Figure 6-37
Configuration Tool Main Window - Connected to GU

Result: The Modify Gateway Unit Configuration dialog box appears, with the General
Properties tab active.
Click the Modify System Parameters button.

Result: The System Parameters dialog box appears on the MCD 5000 Sites tab.
6-36
6802987C96-A
July 2011
Procedure 6-13 Configuring System Parameters for an Individual GU (Continued)

Figure 6-38 System Parameters Dialog Box, MCD 5000 Sites Tab - No Data
If you want to configure parameters related to main, secondary, or regional sites, enter new
parameter settings on the MCD 5000 Sites tab:
Site Name: Select the site for which you want to set parameters for this GU.
OMC IP: Type the IP address of the OMC Server affiliated with this site.
The following shows an example of information entered on the MCD 5000 Sites tab.
6802987C96-A
July 2011
6-37

Figure 6-39 System Parameters Dialog Box - MCD 5000 Sites Tab, Example
When you have finished entering information on the MCD 5000 Sites tab, click the Talkpath
tab.
Result: The System Parameters Talkpath tab opens.
To enter G.711 Encoding Type parameters and Frame Duration values, click the
Advanced button located above the OK button.
6-38
6802987C96-A
July 2011

Figure 6-40 System Parameters Dialog Box - Talkpath Tab
6802987C96-A
July 2011
6-39

7
If you want to configure parameters related to Talkpath, enter new parameter settings in the
Talkpath tab:
Select for the Radio Talkpath option:
Encoding Type: Audio Codec selection.
Frame Duration: Length of sent/received audio packets.
Select for all GU Types:
Disconnect after Timeout: Enable the Disconnect Talkpath option if there is
no voice.
Timeout before Disconnect: Time before disconnecting Talkpath if there is no
voice.
G711 Encoding Type - G711 defines two main compression algorithms:
ULAW: Used in America.
ALAW: Used in Europe.
After entering information on the Security tab, click the Quality of Service tab.
Result: The System Parameters dialog box appears, with the Quality of Service tab open.
6-40
6802987C96-A
July 2011

Figure 6-41 System Parameters Dialog Box - Quality of Service Tab
To configure the Quality of Service parameters, choose an appropriate value from the drop-down
list, for Audio Voice Packets and for Signaling and Controls Packets. If you cannot find the
desired Type of Service in the lists you can use the Advanced button. Clicking the Advanced
button provides you with an option to set any value for each service, Audio Voice, or Signaling
and Controls Packets. This option was designed for future growth of the network options.
Table 6-1 contains the Differentiated Services CodePoint (DSCP) QoS types.
6802987C96-A
July 2011
6-41

Table 6-1
Differentiated Services CodePoint (DSCP) Quality of Service Types
QoS Code
Binary
Description
Decimal
CS0
000000
Best Effort - Routine
CS1
001000
Class Selector 1 - Priority
CS2
010000
Class Selector 2 - Immediate
16
CS3
011000
Class Selector 3 - Flash Class
24
CS4
100000
Class Selector 4 - Flash Override
32
CS5
101000
Class Selector 5 - Critical
40
CS6
110000
Class Selector 6 - Inter-network Control
48
CS7
111000
Class Selector 7 - Network Control
56
AF11
001010
Assured Forwarding - Class 1 Low
10
AF12
001100
Assured Forwarding - Class 1 Medium
12
AF13
001110
Assured Forwarding - Class 1 High
14
AF21
010010
18
AF22
010100
20
AF23
010110
22
AF31
011010
26
AF32
011100
28
AF33
011110
30
AF41
100010
34
AF42
100100
36
AF43
100110
38
EF
101110
Expedited Forwarding - Class 5
46
When you have finished configuring the parameters for the GU, click Apply or Cancel if you
do not want to save the updated parameters.
Result: You return to the Advanced dialog box.
10
Click Apply.
Result: The next warning window appears
6-42
6802987C96-A
July 2011
Cloning a GU Configuration to Another GU
Figure 6-42
11
Warning Window
Click Yes.
To ensure the parameters for the GU are changed, you must do all four steps:
change the system parameters for the GU, click OK on System Parameters
dialog, click Yes on the warning window, click Apply on the Modify Gateway
Unit Configuration dialog box.
Result: The GU Notification window opens, informing you that the changes have been made
and the GU will restart.

You can clone a GU's configuration to another GU. Clone a GU configuration when you want the option to
preserve the GU IP Address and Resources Names fields. A successful clone changes the data according
to the selected configuration, but if fields have been preserved, the data is untouched.
Follow Procedure 6-14 to clone a GU's configuration to another GU.
Procedure 6-14 Cloning a GU Configuration to Another GU
1
window.
6802987C96-A
July 2011
6-43
Procedure 6-14 Cloning a GU Configuration to Another GU (Continued)


6-44
6802987C96-A
July 2011

Figure 6-44 Modify Gateway Unit Configuration Dialog Box - General
Properties Tab
On the Modify Gateway Configuration dialog box, click the Clone button.
Result: The System Tree window opens. In parentheses next to the name of
territory, the total number of resources displays and, after a slash, the number of
resources that can be cloned.
In parentheses next to each territory name, the user can see the total
number of resources and, after a slash, the number of those resources
that can be cloned.
6802987C96-A
July 2011
6-45

Figure 6-45 System Tree Window
State: It is represented by a building icon. The first number in parentheses,

before the slash, indicates the total number of resources in the state. The
number after the slash in parentheses indicates the number of currently
active resources in the state.
Region: It is represented by an icon containing the letter R. The first
number in parentheses, before the slash, indicates the total number of
resources in the region. The number after the slash in parentheses indicates
the number of currently active resources in the region.
County: It is represented by an icon containing the letter C. The first
number in parentheses, before the slash, indicates the total number of
resources in the county. The number after the slash in parentheses indicates
the number of currently active resources in the county.
PSAP: It is represented by a car icon. The first number in parentheses,
before the slash, indicates the total number of resources in the PSAP. The
number after the slash in parentheses indicates the number of currently
active resources in the PSAP. Click the Show Info button to display the
latitude, longitude, and bandwidth for the PSAP. Click the Hide Info button
to hide this information.
Radio resource: It is represented by a radio tower icon. An active Radio
Resource has an icon with a highlighted yellow.
MCD 5000: It is represented by a person at a terminal icon. An active
MCD 5000 has an icon with a highlighted yellow.
5
Select the source GU from which you want to clone the configuration in the
system tree. Select the GU IP Address check box if you want to keep the existing
IP address for the GU. Select the Resources Names check box if you want to
keep the existing GU name. Click OK.
Result: The GU configuration is cloned. If you selected the GU IP Address
check box or the Resources Name check box, the GU IP Address or the GU
name are not cloned respectively.
6-46
6802987C96-A
July 2011
Copying a GU Configuration
Please avoid copying from an MCD 5000 RGU to an MCD 5000

Deskset or vice versa!
You can copy a previously saved GU's configuration to another GU. Copy a GU configuration if you
have already saved the configuration to a file and you do not want to copy the GU IP Address to the
new configuration. A successful copy changes the data according to selected configuration, except for
the GU IP address. Follow Procedure 6-15 to copy a GU's configuration to another GU.
Procedure 6-15 Copying a GU's Configuration to Another GU
1
window.
6802987C96-A
July 2011
6-47
Procedure 6-15
Copying a GU's Configuration to Another GU (Continued)

6-48
6802987C96-A
July 2011
Procedure 6-15

Properties Tab
On the Modify Gateway Configuration dialog box, click the Read From File
button.
Result: The Open window appears.
6802987C96-A
July 2011
6-49
Configuring the Radio Alias Database
Procedure 6-15
5
Select the file name for the gateway unit configuration you want to copy and
click Open.
Result: The Select Specific Port Dialog opens.
Figure 6-48 Select Specific Port
You can select either a whole GU configuration copying or to copy Radio Ports
for example: from port 1 to port 2. Click OK to perform copying.
Result: The selected GU configuration is copied except for the GU IP address.
Please avoid cloning from an MCD 5000 RGU to an MCD 5000

Deskset or vice versa!

Follow Procedure 6-16 to configure the Radio Alias database.
Procedure 6-16 Configuring the Radio Alias Database
1
In the MCD 5000 with OMC CT main window, select the MCD 5000 Deskset for which you
want to change the Alias database and then select GU-> Radio alias database in the main menu.
Result: The Radio alias database window appears with the Talk groups tab active (see Figure
6-49).
6-50
6802987C96-A
July 2011
Procedure 6-16 Configuring the Radio Alias Database (Continued)
Figure 6-49 Radio Alias Database Main Window
In the Talk group tab, use the Add, Remove, and Modify buttons to complete the Talk groups.
Complete the Users tab in the same way.
To backup the radio alias database, click the Save as button.

Result: The Save as dialog box will be opened.
Figure 6-50 Radio Alias Database Save to File
Enter the file name, or use the suggested one, and click Save in the dialog box.
Result: The data will be saved to the text file.
4
To load the radio alias database from a file, click the Read button.
Result: The Open dialog box will be opened.
Figure 6-51 Radio Alias Database Read from File
Select the needed file from the dialog box and click the Open button.
Result: The selected radio alias database file will be loaded into the Radio alias database
window.
5
6802987C96-A
July 2011
To apply your changes, press Apply.

6-51
Saving a GU Configuration to a File
Procedure 6-16 Configuring the Radio Alias Database (Continued)

Result: The Radio alias database will be loaded to the selected Radio resource using FTP.

You can save a GU's configuration to a file for use in the future. Follow Procedure
6-17 to save a GU's configuration to a file.
Procedure 6-17 Saving a GU Configuration to a File
1
window.
6-52
6802987C96-A
July 2011
Procedure 6-17 Saving a GU Configuration to a File (Continued)

3

Properties Tab
On the Modify Gateway Configuration dialog box, click the Save to File button.
Result: The Save As window opens.
Type a name for the file you want to save the configuration as and then click
Save. Change the location of the file if desired.
Result: The configuration is saved to the file in the location you specified.
6802987C96-A
July 2011
6-53
Reading a GU Configuration
Reading a GU Configuration
Any GU Configuration stored to a file can be read and viewed using Procedure 6-18:
Procedure 6-18 Reading a GU Configuration
1
From the application main menu, select File->Read GU Configuration:

Figure 6-54 Read GU Configuration
Result: The Open Configuration File dialog opens.

Figure 6-55 Read GU Configuration from File Open File Dialog
6-54
6802987C96-A
July 2011
Resetting a GU
Procedure 6-18 Reading a GU Configuration (Continued)

2
Select a *.cfg file to read.

Result: The GU configuration file contents will be shown in a dialog similar to
the Modify GU Configuration dialog (see Figure 6-26.)
Resetting a GU
If a GU is not operating properly you can perform a remote software reset. Reset restarts the
GU and reloads the software. Follow Procedure 6-19 to reset a GU.
Procedure 6-19 Resetting a GU
1
window.
6802987C96-A
July 2011
6-55
Removing a GU
Procedure 6-19 Resetting a GU (Continued)

3
On the Configuration Tool main window, click O&M, and then click Reset GU.
Result: The confirmation dialog box appears.
Figure 6-57
Confirmation Dialog Box, before Resetting a GU
Click the Yes button.
Removing a GU
The Configuration Tool allows you to remove a GU from the MCD 5000 Deskset System. Follow Procedure 6-20 to remove a GU.
Procedure 6-20 Removing a GU
1
On the Configuration Tool main window, click O&M, and then click Remove
GU.
Result: The confirmation dialog box appears.
Figure 6-58 Confirmation Dialog Box, Before Removing a GU
Click the Yes button.

Result: After the GU is removed, an appropriate notification is shown.
Figure 6-59
6-56
Notification Dialog Box, After Removing a GU
6802987C96-A
July 2011
Procedure 6-20
3
Changing the RPDFL ID
Removing a GU (Continued)
Click OK to return to the main window.
Changing the RPDFL ID
The following procedure is seldom required to be performed in the field. In factory

we make sure that each unit has a unique RPDFL ID. The procedure of changing
RPDFL ID is required only if the customer happens to receive two units (MCD 5000
Deskset or MCD 5000 RGU) with the same RPDFL ID.
It is possible to set the soft ID to a new GU. If the GU belongs to the system then first remove it and
then add it again as a new GU. Follow Procedure 6-21 to change the RPDFL ID.
Procedure 6-21 Changing the RPDLFL ID
1
In the MCD 5000 with OMC CT main window, click GU and then click Change
RPDFL ID.
Result: The Get GU RPDFL Data window appears.
Figure 6-60 Get GU RPDFL Data Window
Enter the GU IP and click the OK button.

Result: The Set RPDFL ID window opens.
6802987C96-A
July 2011
6-57
CT Application Settings
Procedure 6-21
Changing the RPDLFL ID (Continued)
Figure 6-61 Set RPDFL ID Window
The currently data set is displayed.

3
Select one of the following options:

Burned ID Factory burned ID
Soft ID ID dynamically selected by the user
If you selected Soft ID and you are connected to the OMC, click on the Get
Free ID button to request a free RPDFL ID in the system from the OMC Server.
Otherwise, enter the ID manually (not recommended).
Click on the Apply button to perform the validity check on the Soft ID to make
sure not to affect SW IDs.
Result: The Set RPDFL ID window is closed and the GU is added to the system
with its new ID.
CT Application Settings
You can select the following options from the System with OMC CT menu on the
Configuration Tool main window:
6-58
"MCD 5000 CT Settings" on page 6-59.
"OMC IP Connection List" on page 6-61.
6802987C96-A
July 2011
MCD 5000 CT Settings

You can change timeouts, log settings, user names, and passwords by selecting the MCD
5000 CT Settings option from the MCD 5000 CT menu on the Configuration Tool main
window. Follow Procedure 6-22 to modify CT Settings.
Procedure 6-22 Modifying CT Settings
1
In the Configuration Tool main window, click MCD 5000 CT and then click
MCD 5000 CT Settings.
Result: The CT Settings dialog box appears, with the Timeouts tab active.
Figure 6-62 CT Settings Dialog Box - Timeouts Tab
You can always return to the default settings on a specific tab by

clicking the Default button on that tab.
2
6802987C96-A
July 2011
Click the Logger Tab to access fields for changing Logger window and log file
settings.
6-59
Procedure 6-22 Modifying CT Settings (Continued)

Figure 6-63 CT Settings Dialog Box - Logger Tab
Click the Language Settings tab to change language support preferences.

Enable Hebrew option allows the system to support Hebrew resource names.
Figure 6-64 CT Settings Dialog Box Language Settings Tab
When selecting the Enable Hebrew option, make sure your

Language Settings supports Hebrew. To verify it go to Windows,
press Start > Settings > Control Panel > Regional and
Language Options. Select Advanced tab and choose Hebrew as
Language for non-Unicode programs.
6-60
6802987C96-A
July 2011
OMC IP Connection List
Procedure 6-22 Modifying CT Settings (Continued)

4
Click OK to accept all the changes you made in the CT Settings dialog box.
OMC IP Connection List

You can edit the list of Operation Management Centers (OMCs) with which you work. You can store a
comment for every OMC that you edit. Generally, when you connect at least once to the OMC Server,
the OMC IP is automatically saved in an OMC IP list. It is recommended to use Procedure 6-23 in
case there is an unused OMC IP in the OMC IP list. The current procedure provides an option to
remove an unused OMC IP, add an OMC IP, provide a comment to an OMC, and reorder the OMC IP
list. The OMC IP list feeds the list of IP addresses into the OMC Login window.
Procedure 6-23
1
Modifying the OMC IP Connection List
On the Configuration Tool main window, click MCD 5000 CT and then click
OMC IP Connection List.
Result: The OMC IP Connection List dialog box appears.
Figure 6-65
OMC IP Connection List Dialog Box
In the OMC IP field, type a new OMC server IP or select an existing one from
the list.
Type a comment for that OMC IP.
Click Add.
Result: The OMC IP and its comment display in the list.
6802987C96-A
July 2011
Click OK to save the changes or Cancel to discard them and return to the main
window.
6-61
Monitoring Your System with the Configuration Tool
Monitoring Your System with the Configuration Tool
The audio monitoring feature is used to solve problems of poor audio quality and optimize audio
quality. For each radio resource, the monitoring should be performed separately. This section
explains how to monitor your system with the Configuration Tool. The following procedures are
available for monitoring your system with the Configuration Tool:
"Monitoring MCD 5000 Deskset Audio" on page 6-62.
"Monitoring MCD 5000 RGU Audio " on page 6-66.
"Working with System Logs" on page 6-76.
Monitoring MCD 5000 Deskset Audio

The Configuration Tool enables you to change audio monitoring settings for an MCD 5000 Deskset
Resource. Follow Procedure 6-24 to monitor and change MCD 5000 Deskset audio settings.
Procedure 6-24 Changing MCD 5000 Deskset Audio Monitoring Settings
1
Connect to the desired MCD 5000 Deskset. Refer to "Connecting to a GU" on

page 6-17 for details.
In the Configuration Tool main window, in the Resources List, select the MCD
5000 resource for which you want to monitor audio or change audio settings, and
then click the Audio Monitoring button.
Result: The Audio Monitoring dialog box appears.
Figure 6-66 MCD 5000 Deskset Audio Monitoring Dialog Box
6-62
Select the Active Input Device (Internal, Handset, Headset and External) from
the drop-down list. Then use the buttons and sliders to adjust microphone,
speaker and equalizer volume for the selected device.
6802987C96-A
July 2011
Procedure 6-24
Monitoring MCD 5000 Deskset Audio
Changing MCD 5000 Deskset Audio Monitoring Settings (Continued)
Volume increases as the sliders are moved to the right.

Echo gain level can be adjusted in Handset and Headset.
Echo suppression increases as the slider is moved to the right.

Result: The new audio settings are saved.
4
In the Trigger Settings area:

1. Select A or B from the Source Channel drop-down list.
2. Type the trigger level (0-32767; 15000 is the approximate midpoint) in the
Trigger Level field.
The trigger level is the value that the volume has to be greater than, in order
to appear on the graph.
Click the check boxes Input and/or Output for relevant audio monitoring. Select
the duration (2-10 seconds) for the test from the Test Duration drop-down list.
The test duration is how long the audio capture lasts after the trigger starts. Click
the Start button.
Result: MCD 5000 Deskset audio monitoring begins.
Figure 6-67 Audio Monitoring Dialog Box Showing Audio Sample
6802987C96-A
July 2011
6-63
Modifying Audio Monitoring Settings
Procedure 6-24
Changing MCD 5000 Deskset Audio Monitoring Settings (Continued)
In order to see the audio graph, some audio traffic must exist on the
Radio. To check the Input channel, ensure that a voice is received. To
check the Output channel, press the PTT button and talk.
If the trigger value is not reached and the test does not start, you
can stop the test by clicking the Stop button. Otherwise, the test
will time out after one minute.
6
You can zoom into the graph by clicking the Zoom In button, zoom out of the
graph by clicking the Zoom Out button, and return to the original graph size
by clicking the Home button. To save the modulator and discriminator values
to the GU(s) database(s), click the desired Save button near the modulator and
discriminator settings you want to save.
It is recommended to adjust the modulator and discriminator gain sliders so the
graph amplitude value is around 60%-70% of the axis Y graph scale. If the audio
is saturated, decrease the gain. If the audio is too low, increase the gain.
Click the Stop button to stop sampling audio. If you want to save the audio
sample to a file for later review, click the File menu item, and then click Save
Audio Files.
Result: The Audio Monitoring message opens, showing the location of the
stored audio sample.
Close the Audio Monitoring dialog box to return to the Configuration Tool main
window.
Modifying Audio Monitoring Settings

There are three items you can modify that affect how audio monitoring appears:
Graph view
Trigger value
Y axis options
Setting Audio Monitoring Graph View

You can set the audio monitoring graph view by using the View menu in the Audio Monitoring dialog box:
6-64
Click the View menu and then click Zoom In to zoom into the graph.
Click the View menu and then click Zoom Out to zoom out of the graph.
Click the View menu and then click Original Size to restore the graph to its original size.
6802987C96-A
July 2011
Setting the Trigger Value
Setting the Trigger Value

The trigger value is the value that the volume has to be greater than to appear on the
graph on the Audio Monitoring dialog box. By default, this value is set to zero. Follow
Procedure 6-25 to set the trigger value higher than zero.
Procedure 6-25 Setting the Trigger Value
1
On the Audio Monitoring dialog box, click Settings and then click Trigger Value.
Result: The Trigger Value dialog box appears.
Figure 6-68 Trigger Dialog Box
Type the new trigger value (0-32000) in the New Trigger Value field and then
click OK.
Result: The trigger value is changed.
Setting Y Axis Options

The Y axis represents the maximum range permitted in the graph on the Audio Monitoring dialog
box. By default, this value is set to dynamic, which means the display automatically adjusts
itself when showing sampled audio on the graph. You can set the value to a fixed number from
1K to 32K. Follow Procedure 6-26 to set the Y axis options.
Procedure 6-26 Setting Y Axis Options
1
On the Audio Monitoring dialog box, click Settings and then click Y Axis
Options.
Result: The Y Axis Options dialog box appears.
Figure 6-69
6802987C96-A
July 2011
Y Axis Options Dialog Box
6-65
Monitoring MCD 5000 RGU Audio
Procedure 6-26
2
Setting Y Axis Options (Continued)
Click the Fixed button, select the fixed number from the drop-down list, and
then click OK.
Result: The Y axis number is changed.
Monitoring MCD 5000 RGU Audio

The Configuration Tool enables you to monitor and change audio settings for an MCD 5000 RGU. For
the MCD 5000 RGU, there are three actions you can perform related to monitoring audio:
Radio Scope Test: It displays audio from up to 2 radio resources. The

trigger can be used with one of them.
Tx Calibration: It works with only one radio resource and can display its receive and transmit
audio, press PTT to radio, and play a .WAV file to a radio. An audio file can also be downloaded
to a GU from the PC through this screen. Tx Calibration allows you to calibrate Tx (Modulator)
gain of the radio without depending on an existing talkpath with any MCD 5000 Deskset.
Equalizer: It enables you to adjust/improve the quality of the audio stream before D2A
(Digital to Analog) conversion on Radio port (Modulator direction, Tx)
Performing a Radio Scope Test

The radio scope test is performed to monitor and calibrate the modulator and discriminator gains of the radios
and to detect problems related to radios, such as when the audio from a radio is poor. This test can be used
when the radio levels are first tuned in the GU. Follow Procedure 6-27 to perform a scope test.
Procedure 6-27
Performing a Scope Test

1
Connect to the desired GU. See "Connecting to a GU" on page 6-17 for
instructions.
In the Configuration Tool main window, in the Resources List, select the Radio
resource for which you want to monitor audio or change audio monitoring
settings, and then click the Audio Monitoring button.
Result: The Radio Audio Monitoring dialog box appears, with the Scope Test
tab visible.
6-66
6802987C96-A
July 2011
Performing a Radio Scope Test
Procedure 6-27 Performing a Scope Test (Continued)

Figure 6-70
Radio Audio Monitoring Dialog Box, Scope Test Tab

1. Select A or B from the Source Channel drop-down list.
Trigger Level field. The trigger level is the value that the volume has to be
greater than to appear on the graph.
Select the check box for channel A or B (according to the Source Channel
selected in the previous step).
Result: The Resources List dialog box appears, containing only radio resources.
Figure 6-71 Resources List Dialog Box for Audio Monitoring
Select the radio resource you want to test, then click the Select button.
Result: You return to the Radio Audio Monitoring dialog box.
6802987C96-A
July 2011
6-67
Scope Test Example
Procedure 6-27 Performing a Scope Test (Continued)

6
Select the audio direction (modulator or discriminator). If selecting the same

resource for both channels, you must select different audio directions. Select the
duration (2-10 seconds) for the test from the Test Duration drop-down list. The
test duration is how long the audio capture lasts after the trigger starts. Click
the Start button.
Result: The radio scope test begins. Refer to the section "Scope Test Example"
on page 6-68 to see what happens in a radio scope test.
In order to see the audio graph, some audio traffic must exist on the
Radio.
7
It is recommended to adjust the modulator and discriminator gain

sliders so the graph amplitude value is around 60%-70% of the axis
Y graph scale. If the audio is saturated, decrease the gain. If the
audio is too low, increase the gain.
8
Close the Radio Audio Monitoring dialog box to return to the Configuration
Tool main window.
Scope Test Example

Figure 6-72 shows a scope test performed on two radio resources (166-r1 and 166-r6). The trigger is on
channel B. On the graph you can see the audio in blue and the COR (Carrier Operated Relay) status in
green for the second resource. The trigger is shown in light blue and the PTT status in red.
6-68
6802987C96-A
July 2011
Performing Tx Calibration
Figure 6-72 Scope Test Example
Another way to optimize the audio quality of a Radio resource is Tx Calibration, a continuous audio test which
provides the option of adjusting the modulator gain during the test without the need to press Start each time.
The test is performed until the Stop button is pressed. Follow Procedure 6-28 to perform Tx calibration.
Procedure 6-28 Performing Tx Calibration
1
Connect to the desired GU. See "Connecting to a GU" on page 6-17 for
instructions.
In the Configuration Tool main window, in the Resources List, select the MCD
5000 RGU for which you want to monitor audio or change audio monitoring
settings, and then click the Audio Monitoring button.
Result: The Radio Audio Monitoring dialog box appears, with the Scope Test
tab visible.
Click the TX Calibration tab.

Result: The TX Calibration tab displays.
6802987C96-A
July 2011
6-69
Procedure 6-28
Performing Tx Calibration (Continued)
Figure 6-73 Radio Audio Monitoring Dialog Box, TX Calibration Tab

1. (Optional) If you want to see a picture of the voice wave, select A or B from
the Source Channel drop-down list.
Trigger Level field. The trigger level is the value that the volume has to be
greater than to appear on the graph.
For the input stream, if you want to transmit to the radio resource, select one
of the following:
Select File to Download (and the .WAV file you want to download to the
GU) or
GU Local WAV
Click the TX Resource button to select the radio resource you want to calibrate.
6-70
6802987C96-A
July 2011
Procedure 6-28
Figure 6-74 Resources List Dialog Box for Audio Monitoring
Select the radio resource you want to test and then click the Select button.
Result: You return to the Radio Audio Monitoring dialog box.
For each channel, mark the check box labelled On then perform the following
steps:
Select the audio direction (modulator or discriminator) for each channel;
different audio directions are automatically selected.
Select the duration (2-10 seconds) for the sample from the Sample Duration
drop-down list. The test duration is how long the audio capture lasts after
the trigger starts.
Click the Start button.

Result: The PTT ON and Stop buttons are enabled and the .WAV file is played.
10
Press PTT ON to transmit to radio. Press PTT OFF to stop transmitting to

the radio resource.
Result: The radio resource begins transmitting audio from the selected input
stream. Both channels display selected resource results-one channel displays the
discriminator direction and the other displays the modulator direction.
The TX calibration test is continuous and will continue until the Stop
button is pressed. If the PTT ON button was pressed, PTT will stay
on for 50 seconds or until the PTT OFF button is pressed.
6802987C96-A
July 2011
6-71
Tx Calibration Example
Procedure 6-28
11
It is recommended that the modulator and discriminator gain sliders

be adjusted so the graph amplitude value is around 60%-70% of the
axis Y graph scale. If the audio is saturated, decrease the gain. If the
audio is too low, increase the gain. When calibrating the modulator
gain it is very important to connect to and listen to the physical radio.
There are radios that will give better performance when they receive
high modulating audio, and there are radios that prefer to receive low
modulating audio. In these cases, calibrate according to the voice
quality heard in the portable radio.
12
Click Stop if you want to stop the test, begin another test, or choose other
settings. Use Save Audio Files button to save audio file(s) received since the
Start button was last pressed. Close the Radio Audio Monitoring dialog box to
return to the Configuration Tool main window.
When you close the Audio Monitoring window you will be asked if you would
like to save the audio files received during the last session. If Yes, the files will
be saved and the Audio Monitoring message will appear.
Tx Calibration Example
Tx Calibration is the same as the scope test but with additional transmit capabilities. You can
play a .WAV file and press PTT, and the file will be received at the portable radio. Figure 6-75
shows the results when a WAV file is played and PTT is selected.
6-72
6802987C96-A
July 2011
Equalizer
Figure 6-75 Tx Calibration Example
Equalizer
Equalizing is used to improve/adjust the quality of audio that is transmitted through the donor radio of the
radio resource. Follow Procedure 6-29 to perform equalizer.
Procedure 6-29 Equalizer
1
Connect to the desired GU. See "Connecting to a GU" on page 6-17 for instructions.
In the Configuration Tool main window, in the Resource List, select the Radio for which
you want to monitor audio or change audio monitoring settings, and then click the Audio
Monitoring button.
Result: The Radio Audio Monitoring dialog box appears, with the Scope Test tab visible.
Click the Equalizer tab.

Result: The Equalizer tab displays.
6802987C96-A
July 2011
6-73
Equalizer
Procedure 6-29 Equalizer (Continued)
Figure 6-76 Radio Audio Monitoring Dialog Box, Equalizer Tab
Click the Select Resource button to select the radio resource for which you want to adjust the
equalizer.
Figure 6-77 Resources List Dialog Box for Equalizing
6-74
Create a talkpath between the current radio and some other already calibrated resource in the
system, and start to transmit from the connected resource to this one. During transmission, adjust
equalizer gains until you hear the desired quality at the portable.
6802987C96-A
July 2011
Viewing Radio Activity Statistics for MCD 5000 RGUs
Another way of calibrating is to go to the TX Calibration tab first, activate transmission of some
.WAV file through the radio (as described in step 5 of Procedure 6-28), and then go to the Equalizer
tab and adjust equalizer gains until you hear the desired quality at the portable. After calibration,
go back to the TX Calibration tab and release the PTT and stop the test.
Viewing Radio Activity Statistics for MCD 5000 RGUs

Follow Procedure 6-30 to view radio activity statistics for selected MCD 5000 RGUs.
Procedure 6-30 Viewing Radio Activity Statistics for MCD 5000 RGUs
1
In the Configuration Tool main window, click GU and then click Radio Activity
Statistics.
Result: The Radio Activity Statistics dialog box appears.
Figure 6-78
Radio Activity Statistics Dialog Box
The Radio Activity Statistics dialog box includes the following data:
Port number: Physical port to which a radio is connected.
Sample Duration (hh:mm): The time that passed since the last reboot.
Total/Average/Maximum TX (total, average per minute, maximum per
minute): Gives an indication how often a radio was transmitting.
Total/Average/Maximum RX (total, average per minute, maximum per
minute): Gives an indication how often a radio was receiving.
Last RX Time: Gives an indication of last time radio receiving.
Last RX Duration (sec): Gives an indication of last duration for radio
receiving.
2
6802987C96-A
July 2011
If you want to save the results to a file, click Save to File.
6-75
Working with System Logs
Procedure 6-30 Viewing Radio Activity Statistics for MCD 5000 RGUs (Continued)
Click Close to return to the Configuration Tool main window.
Working with System Logs

The system logs are used to display events and errors that might be useful in debugging
efforts. This section covers the following tasks:
"Viewing the Log" on page 6-76.
"Clearing the Logger Window" on page 6-77.
"Setting Logger Window Content" on page 6-77.
"Including the Date for Logger Entries" on page 6-79.
"Saving the Log to a File" on page 6-79.
"Determining Log File Content" on page 6-80.
You can also work with the logger by using the Administrator Control Panel (ACP). See the MCD 5000
Deskset System Administrator Control Panel User Guide (6802987C99) for details.
Viewing the Log

Follow Procedure 6-31 to view the log.
Procedure 6-31 Viewing the Log
1
In the Configuration Tool main window, click File and then select Open Logger.
Result: The Logger window opens.
Figure 6-79
6-76
Logger Window
6802987C96-A
July 2011
Procedure 6-31
2
Clearing the Logger Window
Viewing the Log (Continued)
Click the Close button.

Result: Returns to Configuration Tool main window.
Clearing the Logger Window

To clear the logger, click File in the Logger window and then click Clear Screen.
Setting Logger Window Content

The View menu in the Logger window works with the Debug menu in the Configuration Tool
main window to display the messages you see in the Logger window. The View menu in the
Logger window controls the level of messages you see (Printout level), the Debug menu in the
Configuration Tool main window determines the type of messages you see.
Setting the Level of Logger Window Messages

Follow Procedure 6-32 to set the level of messages that appear in the Logger window (Printout Level).
Procedure 6-32 Setting the Level of Logger Window Messages
1
In the Logger window, click View and then click Logger Window Printout
Level.
Result: The Logger Window Printout Level dialog box appears.
Figure 6-80 Logger Window Printout Level Dialog Box
6802987C96-A
July 2011
6-77
Setting Logger Window Message Type
Procedure 6-32
2
Setting the Level of Logger Window Messages (Continued)
Select one of the following:

No printouts: To view no messages.
Errors only: To view error messages only.
Most important printouts: To view the most important messages.
Medium printout level: To view important messages and higher level
messages.
All printouts: To view all levels of messages.
Click Select.
Result: The level of Logger window messages that are visible is set.
Setting Logger Window Message Type

Follow Procedure 6-33 to set the type of messages that appear in the Logger window,
and view them in the Logger window.
Procedure 6-33 Setting Logger Window Message Type
1
In the Configuration Tool main window, click File and then select Open Logger
in the drop-down menu that displays.
Result: The Logger window opens.
In the Configuration Tool main window, click Debug and then point to Show.
Then click any one of the following options in the menu, to show information in
the Logger window pertaining to that option:
Gateway Units
Resources
Groups
PSAPs
Counties
Regions
Agencies
Profiles Download Dates
6-78
6802987C96-A
July 2011
Including the Date for Logger Entries
Procedure 6-33 Setting Logger Window Message Type (Continued)

Result: Messages appear immediately in the Logger window.
Including the Date for Logger Entries

To include the date for each logger entry, click the View menu in the Logger window and then click Print With Date.
Saving the Log to a File

Save a log to a file if you want to analyze it later or send it to technical support. Follow Procedure 6-34 to save a log to a file.
Procedure 6-34 Saving a Log to a File
1
When the log you want to save is in the Logger window, click File in the Logger
window and then click Save.
Result: The Save As window opens.
Figure 6-81 Save As Window
Type the name of the log file you want to save in the File Name field and then
click Save.
Result: The .txt file is saved with the name you specified to the location you
specified.
Logs are saved automatically on your PC in the <InstallDirectory>/Logs directory. If

you use the default installation path, then logs are saved in the C:\Motorola\MCD 5000
System with OMC CT\Logs directory. Log files amount, size of each log file, and log
file printout level can be defined using the MCD 5000 CT Settings window, Logger tab
(see Procedure 6-22, "Modifying CT Settings," on page 6-59).
6802987C96-A
July 2011
6-79
Determining Log File Content
The default is five log files of 1 MB each - these parameters can be changed using
the MCD 5000 CT Settings window as mentioned above. Files are saved in a ring
order, which means when the number of log files reaches five, and after the sixth file
is created, the oldest log file is deleted automatically.
Determining Log File Content

Follow Procedure 6-35 to set the level of messages that appear in the log file.
Procedure 6-35 Setting the Level of Log File Messages
1
In the Logger window, click View and then click Log File Printout Level.
Result: The Log File Printout Level dialog box appears.
Figure 6-82 Log File Printout Level Dialog Box
Select one of the following:

No printouts: To include no messages in the log file.
Errors only: To include only error messages in the log file.
Most important printouts: To include only the most important messages
in the log file.
Medium printout level: To include important messages and higher level
messages in the log file.
All printouts: To include all levels of messages in the log file.
Click Select.
Result: The level of messages that will be in the log file is set.
6-80
6802987C96-A
July 2011
Managing GU Software Loads with the Configuration Tool
Managing GU Software Loads with the Configuration Tool
You can use the Configuration Tool software to manage GU software versions that reside
on the GU. This section includes the following topics:
"Installing a GU Software Version on the GU" on page 6-81.
"Removing a GU Software Version from the GU" on page 6-82.
"Activating a Software Version on the GU" on page 6-83.
Installing a GU Software Version on the GU

The GU software may need to be updated periodically. Follow Procedure 6-36 to
install a GU software version on the GU.
Procedure 6-36
1
Installing a GU Software Version on the GU
In the Configuration Tool main window, click O&M, point to GU DB, and then
click SW Load.
Result: The Manage SW Releases on GU dialog box appears. The GU software
versions installed on the GU are shown in the Select Version list. Active status
indicates the software version is currently in use; standby status indicates the
software version is not currently in use. Only two releases can be installed on a
GU.
Figure 6-83 Manage SW Releases on GU Dialog Box
6802987C96-A
July 2011
6-81
Removing a GU Software Version from the GU
Procedure 6-36 Installing a GU Software Version on the GU (Continued)

2
To install a new GU software version onto the GU, click the Install a New
Version on GU button.
Result: The Browse for Folder window opens.
If two GU software versions are already installed on the GU, the

warning message
Only two releases can be installed on GU.
Are you sure you want to replace existing standby
release with new one?
opens. Click Yes if you want to replace the existing standby release
with another one.
Figure 6-84 Browse For Folder Window
Select the folder that contains the new GU software version files and then click
OK.
Result: The folder contents are automatically verified to contain the correct files.
The new GU software release is named after the folder in which the files are
located, so name the folder according to the name you want to use for the new
GU software release.
Result: When the operation completes, the overall status is shown in the status
line above the progress bar. The new GU software version appears at the bottom
of the Select Version list.

Removal of unused GU software releases is essential for conserving GU disk space. Follow
Procedure 6-37 to remove a GU software version from the GU memory.
Procedure 6-37
1
6-82
click SW Load.
6802987C96-A
July 2011
Activating a Software Version on the GU
Procedure 6-37 Removing a GU Software Version from the GU (Continued)

indicates the software version is currently in use; standby status indicates the
GU.
Figure 6-85 Configuration Tool - Manage SW Releases on GU Dialog
Box
To remove a GU software version from the GU, select the version of the software
you want to remove in the Select Version list and then click the Remove Version
button. Only releases in standby status can be removed from the GU.
Result: The message
Are you sure you want to remove the <software version name>
release from GU?
displays.
3
Click Yes.
Result: The software version is removed. When the operation completes, the
overall status is shown in the status line above the progress bar.
Activating a Software Version on the GU

Up to two versions of the GU software are stored on the GU. A GU software version must be activated
to be used by the GU. Follow Procedure 6-38 to activate a software version on the GU.
Procedure 6-38 Activating a Software Version on the GU
1
6802987C96-A
July 2011
click SW Load.
6-83
Programming Radio Buttons with the Configuration Tool
Procedure 6-38 Activating a Software Version on the GU (Continued)

indicates the software version is currently in use, standby status indicates the
GU.
Figure 6-86 Manage SW Releases on GU Dialog Box
To activate a GU software version, select the version of the software you want to
make active in the Select Version list and then click the Set As Active button.
Result: The message

Do you want to set the <version name> as active release?
opens.
Click Yes to activate the version.
Result: The version is set to active and the previous active version is set to
standby. When the operation completes, the overall status is shown in the status
line above the progress bar.
Programming Radio Buttons with the Configuration Tool
For radios that do not use the standard software or radios that are not programmed according to the system
defaults, it is necessary to manually program the radio buttons with the Configuration Tool.
6-84
6802987C96-A
July 2011
Manually Programming Radio Buttons
Motorola radios have two basic parts, the radio and the control panel. The radio and the
control panel use Internal Motorola protocols (SB9600, ESBEP) to communicate with each
other. There are two types of buttons on the control panel:
Press and Release buttons
Rotate buttons
The two types of buttons are shown in Figure 6-87.

Figure 6-87 Motorola MCS 2000 Radio Showing Two Types of Buttons
When a user activates buttons on the control panel, the control panel sends button control messages to
the radio, informing it about the pressing, releasing, or rotating of the specific button.
When the Press and Release button is pressed and released, the control panel sends the radio two messages, a
Press Notification message and a Release Notification message. When the Rotate button is rotated one time
to right or left, the control panel sends one message to the radio-Press Notification. Different button key IDs
are used to identify rotating left and rotating right. For the Press and Release button there is always a pair of
commands sent when each key pressed- a Button Pressed command followed by a Button Release command.
Using the Emulated Radio buttons/soft keys in the MCD 5000 Deskset, a user in one location can press radio
buttons for remote radios. The buttons are available when a connection to a radio exists. For radios that do not
use the standard software or radios that are not programmed according to the system defaults, the radio buttons
must be configured manually using the Configuration Tool. The Configuration Tool allows a technician to
press the buttons on the side of the radio and detect which key is assigned to every key pressed. The MCD
5000 Deskset supports emulation of up to 10 radio buttons in the Deskset Radio Mimic Display, such as:
Home: Causes the radio to move to its "home system" which is one of its trunking groups.
Mode Up: Switches up to another talkgroup (for example, if there are four talkgroups
and the radio is currently in talkgroup 2, it moves to talkgroup 3).
Mode Down: Switches down to another talkgroup (for example, if there are four talkgroups
and the radio is currently in talkgroup 2, it moves to talkgroup 1).
Zone Up: Switches up to another trunking zone (for example, if there are four trunk zones
and the radio is currently in trunk zone 2, it moves to trunk zone 3).
Zone Down: Switches down to another trunking zone (for example, if there are four trunk
zones and the radio is currently in trunk zone 2, it moves to trunk zone 1).

Follow Procedure 6-39 to program radio buttons manually with the Configuration Tool.
6802987C96-A
July 2011
6-85
Procedure 6-39 Programming Radio Buttons Manually with the Configuration Tool
1
Connect to the desired GU.
Select a radio from the Resources List and click Program Buttons. (This
button is active for all radios. Some radios do not support this procedure so an
appropriate message box will be displayed.)
Result: The Programmable Buttons dialog box appears.
Figure 6-88 Programmable Buttons Dialog Box
Select a button to program in the Select Fixed/Dynamic Key to Program area.
To define a new button in the Dynamic Key area just click on an empty button - an editable box will
open. You should enter the button name there and
click Enter.
To deallocate an existing button in the Dynamic
Key area - right-click over selected button and in
the popup menu choose Deallocate.
To edit an existing button name in the Dynamic Key
area - right click over the desired button and in the
popup menu choose Edit.
5
6-86
Click the Detect <button name> Command button. The GU will send all display
updates and all button control messages to the respective panels in this window.
6802987C96-A
July 2011
Procedure 6-39 Programming Radio Buttons Manually with the Configuration Tool (Continued)
6
Click the Try button to test a command displayed in the Try panel. If no messages
appear, go to step 8.
Go to step 10.
On the radio control panel, press the selected button (corresponding to the button
selected in the System with OMC Configuration Tool in step 4).
Click the Try button to try the last command stored in the System with OMC
Configuration Tool.
Be sure that the last button pressed on the radio control panel is the
button you are programming; otherwise you will Try the wrong
command. To properly test the Home Command:
1.
Press the Stop Detecting Home Command button.
2.
Change the channel on the radio using the buttons

on the radio control panel.
3.
Press the Detect Home Command button.
4.
Press the Try button.
10
Observe the radio. It must react as if you are pressing the physical button on the
radio rather than emulating it from the System with OMC Configuration Tool.
11
If the tried command showed the desired result, click the Apply Command
button.
12
If you know the opcode of the command you want to insert, check the Manual
Entry check box, enter the known opcodes for Press and Release commands, and
click Try/Apply to use these values.
13
Repeat step 4 through step 11 for each of the remaining buttons that you want
to program for the MCD 5000 RGU.
14
Click the Selective Call tab.

Result: The following window displays:
Figure 6-89
6802987C96-A
July 2011
Programmable Buttons Dialog Box Selective Call Tab
6-87
In the Selective Call Configuration tab the user should check either
Enabled or Disabled check box. If Disabled was checked there is
nothing to program.
15
If you checked Enabled - act like in previous tab select a key and program it.
The difference is that button names are not editable (unlike the previous tab).
16
When programming Radio keys in Selective Key Configuration tab you should
program buttons 0-9: Buttons that were programmed will have no red frame,
while unprogrammed buttons will have a red frame so a user can know which
buttons are still not programmed.
17
Select the Displayed Icons tab.

This page configures which icon will be displayed for which opcode arriving
from the radio and at which place it should be located.
Result: The following window appears:
Figure 6-90 Programmable Buttons Dialog Box Displayed Icons
18
Use the Default button or alternatively define your set of icons per radio opcode.
Click on any green button.
Result: A new window appears.
6-88
6802987C96-A
July 2011
Figure 6-91 Defining Your Set of Icons Per Radio Opcode
Define up to six opcodes/icons for the selected place on the green display. Icon
definition is performed by clicking on one of the left white squares - it will open
the window with possible icons:
Figure 6-92 Possible Icons Window
Choose an icon and click OK. Click Apply when finished.

19
6802987C96-A
July 2011
Click Close to return to the MCD 5000 with OMC Configuration Tool window.
6-89
20
To verify functionality of the newly programmed buttons, create a talkpath

between the MCD 5000 Deskset and the radio. Connect the MCD 5000 Deskset
to the radio.
Result: The Emulated Radio Buttons screen appears.
Use these to test the commands.
6-90
6802987C96-A
July 2011
Chapter
7
MCD 5000 Deskset System Troubleshooting
This appendix contains information on how to troubleshoot problems with the MCD 5000
Deskset System. The following topics are included:
"Troubleshooting with the ACP" on page 7-1.
"Troubleshooting OMC Servers" on page 7-3.
"Gateway Unit Troubleshooting and Configuration" on page 7-5.
"Advanced Troubleshooting and Configuration" on page 7-13.
Troubleshooting with the ACP
The Operations Management Center (OMC) Server is the main repository of system data. You can
view the System Performance screen in the Administrator Control Panel (ACP) to get a general idea of
the health of the system. The screen is found by selecting the System Performance option from the
O&M menu on the Administrator Control Panel main window. The screen has several information
sections. Table 7-1 describes the sections and their purpose for troubleshooting.
Table 7-1 System Information in the ACP Used for Troubleshooting
OMC Performance Screen
6802987C96-A
Troubleshooting
Connections
Indicates the number of IP connections that

the system is setting up and breaking down,
and gives a count of any failures in these
setups and breakdowns. A high number
of failed attempts may indicate a problem
somewhere in the system.
Clients
Indicates the number of Users logged

in to MCD 5000 Desksets and system
Administrators/Technicians logged in to the
OMC via the ACP.
GUs
Indicates the number of GUs in the system

Online and offline.
July 2011
7-1
Using Alarms and Events to Flag Problems
Table 7-1
System Information in the ACP Used for Troubleshooting (Continued)
OMC Performance Screen
Troubleshooting
Bandwidth
Shows the bandwidth for Transmit and

Receive.
CPU/Memory
Shows the real-time CPU loading and

memory usage of the OMC Server. Sustained
CPU loading of above 95% may indicate
a problem in the system or with the OMC
Server. Likewise, memory usage of above
95% indicates the same. Also on this tab, the
total number of gateway units (GU) in the
system is indicated. If this number differs
from what is expected, check if a GU has
failed or has been removed from the system.
Using Alarms and Events to Flag Problems

You can view alarms and events for a specified time period (historical), or for the current day. To view
historical alarms and events, select the System Status History option from the O&M menu on the
Administrator Control Panel main window. To view alarms and events for the current day, select the
System Status Window option from the O&M menu. Some alarms indicate problems and/or failures.
The IP addresses of the resources involved in the alarm or event are displayed, allowing correlation of
any reported problems to a particular site, or allowing investigation of the site even before a problem
is reported. For example, an alarm involving a particular MCD 5000 RGU can be followed up with an
audio test of that MCD 5000 RGU, using the techniques described in the previous section.
Alarms can be filtered by level. In some cases the user/administrator may want to
monitor only errors, while filtering out warnings and notifications. In other cases, the
user/administrator may want to monitor alarms of all levels.
Using System Logs to Aid in Debugging Efforts

From the ACP main window, select the File menu, and then click on Open Logger. Once in the Logger
window, the level of messages that appear in the window can be set. In the Logger Window, select the View
menu, and then click Logger Window Printout Level. Select the desired priority levels to be displayed.
From the ACP main window, select the Debug menu, and then point to Show. Here you can filter to see
messages that pertain only to PSAPs, only to gateway units, only to connections, and so on. Use this filter to
help narrow down the source of a problem that is reported. Is a particular PSAP reporting trouble? Look
only at PSAP-related messages. Logs can be saved to files for further analysis. See the MCD 5000 Deskset
Administrator Control Panel User Guide (6802987C99A) for instructions on how to save logs to files.
7-2
6802987C96-A
July 2011
Windows Firewall Alerts
Windows Firewall Alerts

When running the MCD 5000 Administrator Control Panel (ACP) and Configuration Tool on
Windows 7 (64 bit) while the Windows Firewall is enabled, you may receive a Windows Security
Alert asking if you want to keep blocking the raw_com1 program.
Windows Security alert may be seen in the ACP in the following cases:
When right clicking on a resource (in the map, in the System Tree, in the Group
Management dialog box), or when selecting the Audio Monitoring option from
the Resources List and pressing the Play button.
While trying to download a software version, as follows: In the ACP main window, select the
O&M menu, point to OMC DB, and select SW Load. In the Manage GU SW Releases
in OMC DB dialog box, click the Install a new Version on OMC button.
While running the Configuration Tool, the problem might occur in the following cases:
When clicking the Audio Monitoring button on the Configuration Tool main
window and then clicking the Play button.
While trying to download a software version, as follows: In the Configuration Tool main
window, select the O&M menu, point to GU DB, and select SW Load. In the Manage
SW Releases on GU dialog box, click the Install a new Version on GU button.
Solution: Select the Unblock option and then open the Windows Firewall -> Exceptions tab from the
Windows Control Panel. Ensure that File Transfer Program and raw_com1 are selected.
Troubleshooting OMC Servers
Table 7-2 contains instructions for correcting problems with the Operations Management Center (OMC) Server.
Table 7-2
6802987C96-A
Fault
Corrective Action
The OMC server

is in standby
mode without
any possibility to
change to active
mode.
Verify that the OMC servers are configured correctly [for information
about verifying the OMC Server configuration, see the "Advanced
Maintenance for OMC Server" section in this manual]. Follow the
instructions to correct the problem.
If the problem persists, reconfigure the MCD 5000 Deskset System using
Procedure 3-4, "How to View/Configure Network Parameters," on page
3-13 of this manual.
July 2011
7-3
Table 7-2 Troubleshooting OMC Servers (Continued)

Fault
The OMC server
machine needs
to be replaced.
Corrective Action
Change the other OMC server to active mode using the ACP [see the
MCD 5000 Deskset System Administrator Control Panel User Guide
(6802987C99)].
Use the following procedures to install a new OMC server:
1. "Installing MCD 5000 OMC Server OS ".
2. "Installing MCD 5000 OMC Server Application".
3. "Changing the Root Account Password".
4. "Viewing/Configuring Network Parameters ".
5. "Synchronizing the OMC Servers Databases"
If the new OMC server is the secondary OMC server configure the Main
OMC server as its time-server.
7-4
Both OMC
servers appear
to be in Active
mode.
Verify that the OMC servers are configured correctly [see the "Advanced
Maintenance for OMC Server" section in this manual].
The standby
OMC cannot
change OMC
IP because the
other one does
not seem to be
active.
Verify that the OMC servers are configured correctly [see the "Advanced
Maintenance for OMC Server" section in this manual].
Then try to change the OMC server IP again.
The date and

time of the
OMC server is
not configured
correctly
Use the following procedures to configure the OMC server time

settings:"Configuring the Time of Day, Date or Time Zone ", and
"Configuring NTP Client" in this manual.
The Active
OMC has
disconnected
from the
network.
Change the other OMC server to active mode using the ACP [see the
MCD 5000 Deskset System Administrator Control Panel User Guide
(6802987C99)].
6802987C96-A
July 2011
Gateway Unit Troubleshooting and Configuration
Gateway Unit Troubleshooting and Configuration
Gateway Unit Troubleshooting/Configuration Tools

Refer to Chapter 4, "Installing MCD 5000 Deskset System Units" for hardware information specific
to MCD 5000 Deskset System units, including installation instructions.
The following applications may be used for troubleshooting problems with the MCD
5000 Deskset System Gateway Units:
MCD 5000 Deskset System with OMC Configuration Tool
MCD 5000 Deskset System Administrator Control Panel (ACP)
Table 7-3 MCD 5000 Deskset LED Descriptions

LED
6802987C96-A
Description
Indication
Transmit
Indicator
Audio Flow
Status
Red light: Indicates that the audio is sent to remote radio.

No light: Indicates that no audio is being sent.
Transmitter
Busy Indicator
Audio Flow
Status
Orange light: Indicates that other dispatcher transmits

audio to radio network through this radio resource.
No light: Indicates that no other dispatcher transmits
audio to radio network through this radio resource.
Receiver
Indicator
Audio Flow
Status
Green light: Indicates that audio is received from radio.

No light: Indicates that no audio is being received.
Add Speaker
Internal
speaker control
Light: Indicates that internal speaker is added as the

second output channel.
No light: Indicates that only one output channel is in use
(handset/headset/internal speaker).
Mute Button
Light: Indicates that audio input/output is muted by the

Mute button.
No light: Indicates that audio input/output is not muted
by the Mute button.
Base Intercom
Red light: Indicates that audio is sent to MCD 5000 units

through remote radio resource.
Orange light: Indicates that other MCD 5000 dispatcher
July 2011
7-5
Troubleshooting Gateway Units
Table 7-3 MCD 5000 Deskset LED Descriptions (Continued)

LED
Description
Indication
speaks to this MCD 5000 dispatcher through radio
resource.
No light: Base intercom is not in use.
Table 7-4 MCD 5000 RGU LED Descriptions

LED
Description
Indication
Port 1
Port 2
Port 3
Port 4
Audio Flow
Status
Red light: Indicates that the radio is in transmission state.

Green light: Indicates that the radio is in receiving state.
No light: Indicates that radio is in idle state.
COMM
Connections
state
Green light: Indicates that the MCD 5000 RGU has a

good connection to all MCD 5000 Desksets.
Blinking Green light: Assign talkpaths are yet to be
established after MCD 5000 RGU normal boot.
Red light: Talkpath to the MCD 5000 RGU has been
accidentally disconnected or assigned talkpath has not
been established.
No light: The MCD 5000 RGU has not been set to
establish any talkpath to radio.
Blinking Red light: Fault or no connection between the
MCD 5000 RGU and the OMC.
PWR
Red light: The MCD 5000 RGU is in boot state.

Blinking red light: There is a malfunction within the
MCD 5000 RGU. DSP problem.
Green light: The MCD 5000 RGU is powered from
the DC PWR input or both DC PWR and PoE LAN
Connection, and working properly.
Blinking green light: The MCD 5000 RGU is powered
from the DC PWR input or both DC PWR and PoE LAN
Connection, and working properly.
No light: The MCD 5000 RGU is in OFF state.

Table 7-5 contains instructions for correcting common problems with the MCD
5000 RGU and MCD 5000 Deskset.
Table 7-5
Troubleshooting Gateway Unit Installation
Fault
Alarm
Unknown GU
displays in the
ACP
7-6
Corrective Action
Add the GU to the system using the ACP or Configuration Tool. If a new
GU replaces an existing malfunctioning GU, the user must Delete Old GU
resources and then add the new GU using the old GU database from file.
6802987C96-A
July 2011
Table 7-5 Troubleshooting Gateway Unit Installation (Continued)

Fault
Corrective Action
Alarm
From ACP:
Territory
does not
exist
1. Log onto the OMC Server.
displays in the
ACP
2. Download the active version of the System Parameters to both GUs.

From the Configuration Tool:
1. Log onto the OMC Server.
2. Create the technician profile.
3. Click Modify GU Configuration. If the warning message System
Parameters are not updated. Do you want to update them? appear, press
Yes and then Apply.
GU does
not connect
to OMC,
Alarm GU
connected
to OMC
doesnt appear
1. Check the Ethernet connection to the External LAN port.

2. Verify that the cable is connected to the LAN switch/router (External
LAN connector LED is blinking orange and green).
3. Ping the gateway unit to verify that its IP is properly configured.
To view or change the IP configuration, open the Modify Gateway Unit
Configuration dialog box on the ACP or Configuration Tool, and select
the IP Configuration tab. If the gateway unit is properly connected to the
LAN, but the problem still exists:
4. Log onto the OMC using the ACP. Open the Modify Gateway Unit
Configuration dialog box, and agree for update system parameters.
Talkpath
creation fails
1. Ensure that MCD 5000 Deskset is connected to the OMC.

2. Reload the System Resource Table on MCD 5000 Deskset using
quit->update.
Talkpath
1. Log onto the OMC using the ACP or the Configuration Tool.
creation is slow
2. Update the profile.
3. Modify the GU using the new profile.
Dispatcher
does not hear
connected
resource
Option 1: Dispatcher hears all resources except one specific resource.

1. Check the RX LED on the front panel of the MCD 5000 Deskset. If
there is no light, there is no voice to hear.
2. Check Port led of the radio at the time of voice receiving. If it is not
green, radio is not in receiving state radio configuration and physical
connection to radio equipment should be checked.
3. Ask another dispatcher to connect to radio and test the link. If it is OK,
remove and add the connection again. Check that there are no firewalls
between radio and MCD 5000 Deskset, or that the firewalls are properly
configured. If there is still no audio, call support.
Option 2: Dispatcher cant hear audio from any other gateway units:
1. Check the RX LED on the front panel of the GU. If there is no light,
there is no voice to hear. Connect to a radio that is sourcing audio.
6802987C96-A
July 2011
7-7

Fault
Corrective Action
2. Check that your handset/headset is connected. Check the volume on
your internal speaker/handset/headset.
3. Check that there are no firewalls between the radio and MCD 5000
Deskset, or that the firewalls are properly configured.
Option 3: Dispatcher cant hear audio through headset, while it can hear
through handset.
Check that usage of external microphone is set to off. MDC5000 Deskset
should be configured with ACP/CT not to use external microphone. Use
Modify GU Configuration window, MCD 5000 Deskset properties tab.
Use Microphone checkbox should be unchecked.
Remotely
connected
resource can
not hear
dispatcher
When speaking to a radio, the PTT switch must be pressed.

1. Verify that you are logged into the MCD 5000 Deskset.
2. Check the microphones of the MCD 5000 Deskset.
a. If you speak through a handset, check that your handset is
physically connected.
b. If you speak through a headset, check that your headset is
physically connected to port JckBx/DskMic, and your handset is
on hook.
c. If you speak through an external microphone, check that your
external microphone is physically connected to port JckBx/DskMic.
The cable should be connected according to the labels on the cable
(one side to the microphone, and the other to the port on the GU).
the MCD 5000 Deskset should be configured with ACP/CT to use
external microphone, use Modify GU Configuration window, MCD
5000 Deskset properties tab, Use Microphone checkbox.
d. If you speak through an internal microphone, check that handset
is on hook, handset is unplugged, and GU is not configured to use
external microphone.
3. Open the Audio Monitoring window on the ACP or the Configuration
Tool. Choose input channel. Increase the Input volume.
7-8
6802987C96-A
July 2011

Fault
Corrective Action
Radio does not

hear connected
resource
Option 1: Radio can hear all resources except one. Refer to the instructions
for the fault: Remotely connected resource cannot hear dispatcher.
Option 2: Radio cannot hear any resource:
1. Check the appropriate port led on the front panel of the MCD 5000
RGU. If there is no red light, there is no voice to transmit. Connect to a
dispatcher/radio that is sourcing audio.
2. Check that there are no firewalls between the radio and the MCD 5000
Deskset, or that the firewalls are properly configured.
3. Check that the radio cable is connected to the proper port on the MCD
5000 RGU. The MCD 5000 RGU should be configured to work with the
same port where the cable is connected.
4. Check that this MCD 5000 RGU port is properly defined. Open
the Modify Gateway Unit Configuration dialog box on the ACP or the
Configuration Tool and check the radio type on the given port on the Radio
Resource Properties tab. Also, check the protocol definition and PTT
mode defined on the radio.
5. Open the Audio Monitoring window on the ACP or the Configuration
Tool and increase the transmit audio gain (modulator) of the radio.
Remotely
connected
resource can
not hear radio
Option 1: The radio can hear all resources except one. Refer to the fault:
Dispatcher does not hear connected resource.
Option 2: No other resource can hear the radio:
1. Check that the radio cable is connected to the proper port on the MCD
5000 RGU. The MCD 5000 RGU should be configured to work with the
port where the cable is connected.
2. Open the Modify Gateway Unit Configuration dialog box on the ACP
or the Configuration Tool and check the radio type on the given port on
the Radio Resource Properties tab. Also check the protocol definition and
Audio Detection mode defined on the radio.
3. Increase the receive audio gain (discriminator) of the radio. You can
do it from the Audio Monitoring dialog box or from the Modify Gateway
Unit Configuration dialog box, Radio Resource Properties tab, on the ACP
or the Configuration Tool.
Noise Is Heard
Instead of
Voice
Poor Audio
Quality and
High Packet
Loss Shown In
Performance
menu of the
MCD 5000
Deskset
6802987C96-A
July 2011
If the audio to and from all resources is scrambled, the units do not
have the appropriate audio key. Download the correct audio key from the
ACP to correct this.
1. Check that the number of talkpaths in the PSAP does not exceed the
allowed bandwidth. Delete some talkpaths and see if the audio improves.
Remember that activities like audio monitoring can consume bandwidth
too.
2. Enlarge the jitter buffer length. You can change it from the Modify
Gateway Unit Configuration dialog box, General Properties tab.
7-9
Pinging Gateway Units on the Internal and External LANs

Fault
Corrective Action
Poor Audio
Quality
Check that the input level is not too high. Open the resource-input audio
monitoring window from the Configuration Tool or the ACP and check
the audio level of the input.
Then open the resource-output audio monitoring window from the
Configuration Tool or the ACP and check the audio level of the output.
If the radio is the source of poor audio quality, check that the radio port
is configured to proper radio type and audio detection mode. If the audio
detection mode is VAD, try to increase the Voice Decay Time. Use the
ACP or the Configuration Tool Modify Gateway Unit Configuration dialog
box, Radio Properties tab, choose radio port and click the Advanced button.
The GU cannot
connect to the
network
1. Check the Ethernet connection to the External LAN port.

2. Verify that cable is connected to LAN switch/router (External LAN
connector LED is blinking orange and green).
3. Ping the GU to verify that its IP address is properly configured.
To view/change IP configurations, open the Modify Gateway Unit
Configuration dialog box, IP Configuration tab using the Configuration
Tool.
Configuration
Tool cannot
connect to GU
If you receive the message

Failed to connect to Gateway Unit
, when trying to open the Configuration Tool, try the following:

1. Connect the PC to the Internal LAN port.
2. Check that the PC has the proper network settings:
On the Desktop, right click on My Network Places and select
Properties.
Right-click on Local Area Connection and select Properties.
Local Area Connections are listed. Select the one that is used to
connect to the GU.
Select Internet Protocol and select Properties.
Check that the IP address is 10.0.0.2, and the netmask is
255.255.255.248. If the IP address or the netmask is changed, the
PC must be restarted.
3. Using the Start-> Run, type ping 10.0.0.1 -t and press OK. A
Reply screen displays when the IP address is available.
Pinging Gateway Units on the Internal and External LANs

This section provides procedures for pinging gateway units. The following procedures are included:
7-10
"How to Ping a Gateway Unit on the External LAN (External LAN)" on page 7-11.
"How To Ping a Gateway Unit on the Internal (local) LAN" on page 7-11.
6802987C96-A
July 2011
MCD 5000 Deskset System with OMC Installation and Configuration Guide How to Ping a Gateway Unit on the External LAN (External LAN)
Figure 7-1 shows the internal and external LANs.

Figure 7-1 Internal vs. External LAN
How to Ping a Gateway Unit on the External LAN (External LAN)

Follow Procedure 7-1 to ping a GU with a computer that is connected to the network.
Procedure 7-1
1
How to Ping a Gateway Unit on the External LAN
Click Start and then click Run.

Result: The Run window opens.
In the Open box, type ping <ip of Gateway Unit> -t and click OK.
Result: The Reply screen displays.
If the ping takes a long period of time to complete, there may be a

delay in the network and also packet loss. If there is no reply from
the GU that was pinged, try to ping the router or switch. If the router
or switch does not reply, then the whole LAN segment is unavailable.
How To Ping a Gateway Unit on the Internal (local) LAN

Procedure 7-2 describes the procedure for pinging a gateway unit on the local (internal) LAN.
Procedure 7-2 How to Ping a Gateway Unit on the Local (internal) LAN
1
Connect the PC to the Internal LAN port.
On the desktop, right click on My Network Places and click Properties.

Result: The Network Connections window opens.
6802987C96-A
July 2011
7-11
Updating System Parameters on Gateway Units
Procedure 7-2 How to Ping a Gateway Unit on the Local (internal) LAN (Continued)
3
Right-click on appropriate local area connection and click on Properties.

Result: The Local Area Connection Properties dialog box appears.
In the This Connection Uses the Following Items box, select Internet Protocol
and click the Properties button.
Result: The Internet Protocol (TCP/IP) Properties dialog box appears.
Check that the IP address is 10.0.0.2, and the Netmask is 255.255.255.248. If the
IP address or the Netmask is changed, the PC must be restarted.
Click Start and then click Run.

Result: The Run window opens.
In the Open box, type ping 10.0.0.1 -t and press OK.
Updating System Parameters on Gateway Units

If the system parameters configuration on the gateway unit is different from the currently active
system parameters stored on the OMC Server, the message
System Parameters are not updated.
Do you want to update them?
appears. If you want the system parameters to remain different, click No and continue configuring
the GU. If you want to synchronize the system parameters on the GU with those stored on the OMC
Server, click Yes and then click Apply. The Are you sure you want to apply current configuration?
message appears. Click Yes. The changes are saved in the GU database. The GU Notification message
appears. Click OK. All connections are cleared and the GU is rebooted.
Refer to the MCD 5000 Deskset System Administrator Control Panel User Guide (6802987C99) for:
Detailed instructions about changing and configuring system parameters for

an individual GU using the ACP.
Detailed instructions about synchronizing system parameters for an individual GU

with those stored on the OMC database using the ACP.
The Configuration Tool takes the system parameters settings from the technician profile, and not
from the OMC, so the system parameters set by the Configuration Tool may be obsolete.
7-12
6802987C96-A
July 2011
Advanced Troubleshooting and Configuration
Advanced Troubleshooting and Configuration
This section provides additional troubleshooting and configuration information for use only by qualified
Motorola service personnel. The following procedures describe how to directly reload gateway
unit (GU) files from a PC, using secure File Transfer Protocol (sFTP). This action should only be
attempted after other methods for reviving a failed GU have been unsuccessful.
The qualified Motorola service representative must have knowledge of the following:
Software directory structure of a GU
Updated GU files (application and databases)
Internal process of the GU during the power cycle
The following topics are included in this section:
"How to Use the sFTP Command of WinSCP" on page 7-13.
"How to Revive a Gateway Unit-Gateway Unit Can Load VxWorks" on page 7-15.
"How to Revive a Gateway Unit-Gateway Unit Cannot Load VxWorks" on page 7-16.
How to Use the sFTP Command of WinSCP

WinSCP is a freeware application that provides SFTP access. The application can be downloaded
from the Internet. Any other application which supports the SFTP protocol can be used. Follow
the instructions in Procedure 7-3 to use the sFTP command of WinSCP.
Procedure 7-3 How to Use the sFTP Command of WinSCP
1
6802987C96-A
July 2011
Open WinSCP. In the WinSCP login window, press New button to define a new
session (If you already have a session defined, proceed to step 3).
7-13
How to Use the sFTP Command of WinSCP
Procedure 7-3 How to Use the sFTP Command of WinSCP (Continued)
Figure 7-2 WinSCP Login Window
Fill GU IP, user and password. Use Login button to login immediately or save
button to save session definition to further use.
Figure 7-3 WinSCP New Session Window
Default user: tech

Default password: ABCD123456efgh*
3
7-14
Choose saved session and press login button.
6802987C96-A
July 2011
How to Revive a Gateway Unit-Gateway Unit Can Load VxWorks
Procedure 7-3 How to Use the sFTP Command of WinSCP (Continued)

4
Connection to GU will appear on the right side of panel.

Figure 7-4
WinSCP Session
How to Revive a Gateway Unit-Gateway Unit Can Load VxWorks

Follow the instructions in Procedure 7-4 to revive a gateway unit, when the gateway unit can load VxWorks.
Procedure 7-4 How to Revive a Gateway Unit-Gateway Unit can load VxWorks
1
Connect one end of an RJ45 cable to the LOCAL O&M port on the right side
of the MDC5000 Deskset or on the rear panel of the MCD 5000 RGU. Connect
the other end to your technician PC.
Stop main out loading by pressing any key when you see Press any key to
stop loading (second countdown after reset).
Result: You should see the [AGU Loader]: prompt.
6802987C96-A
July 2011
Enter the IP address into the Gateway Unit. If the Gateway Unit IP and your
computer IP are from different segments, enter the netmask/gateway IP.
Commands:
c1 - to configure external LAN
c2 - to configure IP of internal LAN
7-15
How to Revive a Gateway Unit-Gateway Unit Cannot Load VxWorks
Procedure 7-4 How to Revive a Gateway Unit-Gateway Unit can load VxWorks (Continued)
4
Copy the image to the Gateway Unit, using WinScp or other sFTP agent.
How to Revive a Gateway Unit-Gateway Unit Cannot Load

VxWorks
Follow the steps in Procedure 7-5 to revive a gateway unit when that unit cannot load VxWorks.
Procedure 7-5 How to Revive a Gateway Unit-Gateway Unit Cannot Load VxWorks
1
Connect one end of an RJ45 cable to the LOCAL O&M port on the right side
of the MDC5000 Deskset or on the rear panel of the MCD 5000 RGU. Connect
the other end to your technician PC.
Stop the loading of VxWorks by pressing any key when you see Press any
key to stop auto-boot... (first countdown after reset).
Result: You should see the [VxWorks Boot]: prompt.
Run the sFTP server on your computer. If you do not have one installed on your
computer, download any freeware sFTP server from the Internet. Connect the
external LAN of the Gateway Unit to the network.
To construct the bootline, gather the following information:

computer name
path where the VxWorks file is located
IP of the Gateway Unit
IP address of computer
IP address of gateway
User name to connect to the FTP server on your computer
Password to connect to FTP server on your computer
Bootline is: $motetsec(0,0)<computer name>:<path to VxWorks> e=<Gateway
Unit
IP>[:<netmask>] h=<computer IP> g=<gateway IP> u=<user> [pw=<password>]
For example: $motetsec(0,0)bml014-01:D:\vxWorks e=10.98.66.109:ffffff00
h=10.110.26.130 g=10.98.66.254 u=vxworks pw=vxworks
7-16
Stop main.out loading and follow "How to Revive a Gateway Unit-Gateway

Unit Can Load VxWorks" where the Gateway Unit can load VxWorks.
6802987C96-A
July 2011
Appendix
Secure Password Rules

In an MCD 5000 Deskset System which includes an OMC server, secured password rules are
applied per the different usernames defined in the system.
Security rules per application are listed below.
ACP Account Password Rules
6802987C96-A
July 2011
The password must be between 4 and 15 characters, and must include at least one
upper case letter, lower case letter, number, and special character.
The password expires after 60 days. The ACP displays a warning to replace
the password 10 days before expiration.
The user may not reuse the previous 10 passwords.
The user may not change passwords more than once a day, except in the case of an
administrator or privileged user. Privileged users may be required to reset a users forgotten
passwords and the ability to change passwords more than once per day.
When a password is changed, the new password must differ from the previous
password by at least four characters.
A-1
MCD 5000 Deskset Account PIN Rules
Appendix A: Secure Password Rules
MCD 5000 Deskset Account PIN Rules
The PIN must be between 4 and 15 digits.
The PIN expires after 60 days. The Deskset displays a warning to replace
the PIN 10 days before expiration.
The user may not reuse the previous 10 PINs.
The user may not change PINs more than once a day, except in the case of an administrator
or privileged user. Privileged users may be required to reset a users forgotten PINs
and the ability to change PINs more than once per day.
Configuration Tool/MMI/SSH/SFTP Account Password

Rules
The password must be between 4 and 15 characters, including upper case letters, lower
case letters, numbers, and special characters.
A-2
6802987C96-A
July 2011
Linux Account Password Rules
Linux Account Password Rules
The password must be at least nine characters long, including
at least two upper case letters,
at least two lower case letters,
at least two numbers,
at least two non-alphanumeric characters.
The Linux account password rules are the default settings and may have
been updated by system administrator.
Database Account Password Rules
6802987C96-A
July 2011
The password must be between 4 and 15 characters, including upper case letters,
lower case letters, numbers, and special characters.
The user may not reuse the previous 10 passwords.
The user may not change passwords more than once a day, except in the case of an
administrator or privileged user. Privileged users may be required to reset a users forgotten
passwords and the ability to change passwords more than once per day.
When a password is changed, the new password must differ from the previous
password by at least four characters.
A-3
A-4
6802987C96-A
July 2011
Appendix
MCD 5000 Deskset System Ports and

Services for Firewall Configuration
The table below lists the MCD 5000 Deskset System ports and services for configuring
the firewall in the MCD 5000 Deskset System.
MCD 5000 Deskset System Ports and Services
The following table lists the firewall ports that should be configured in the MCD 5000 Deskset
System firewall. To review the system architecture with firewall deployment, please refer
to Chapter 1, "MCD 5000 Deskset System Overview".
Table B-1 MCD 5000 Deskset System Ports and Services
Index
#
Service
Source
Device
Source
Port
Destination
Device
Destination
Port
Network
Layer 3
Transport
Layer 4
Application Layer
7
L (Proprietary)
ACP
Any
OMC Server
5062
unicast
TCP
L-Reverse
flow
OMC
Server
5062
ACP
Any
unicast
TCP
SFTP
ACP
Any
OMC Server
22
unicast
TCP
SFTP
SFTPReverse
flow
OMC
Server
22
ACP
Any
unicast
TCP
SFTP
SFTP
Deskset/
RGU
Any
OMC Server
22
unicast
TCP
SFTP
SFTPReverse
flow
OMC
Server
22
Deskset/
RGU
Any
unicast
TCP
SFTP
SFTP
Any
Any
OMC Server
22
unicast
TCP
SFTP
SFTPReverse
flow
OMC
Server
22
Any
Any
unicast
TCP
SFTP
SFTP
CT
Any
Deskset/
RGU
22
unicast
TCP
SFTP
6802987C96-A
July 2011
B-1
Appendix B: MCD 5000 Deskset System Ports and Services for Firewall Configuration
Table B-1 MCD 5000 Deskset System Ports and Services (Continued)
Index
#
Service
Source
Device
Source
Port
Destination
Device
Destination
Port
Network
Layer 3
Transport
Layer 4
Application Layer
7
10
SFTP
Deskset/
RGU
22
CT
Any
unicast
TCP
SFTP
11
O-C (Proprietary)
Deskset/
RGU
Any
OMC Server
5062
unicast
TCP
O-C
12
O-C
-Reverse
flow
OMC
Server
5062
Deskset/
RGU
Any
unicast
TCP
O-C
13
MySQL
Server
Database
Sync
OMC
Server
3306
OMC Server
3306
unicast
TCP
14
NTP
OMC
Server
Any
OMC Server
123
unicast
UDP
NTP
15
NTPReverse
flow
OMC
Server
123
OMC Server
Any
unicast
UDP
NTP
16
OMC
Sync
(Proprietary)
OMC
Server
5062
OMC Server
5062
unicast
UDP
OMC Sync
17
SSH
Any
Any
OMC Server
22
unicast
TCP
SSH
18
SSHReverse
flow
OMC
Server
22
Any
Any
unicast
TCP
SSH
19
SSH
Any PC
Any
Deskset/
RGU
22
unicast
TCP
SSH
20
SSH
Deskset/
RGU
22
Any PC
Any
unicast
TCP
SSH
21*
RPDFL
Deskset/
RGU
6000
Deskset/
RGU
6000
unicast
UDP
RPDFL
cFL
Deskset/
RGU
6003
Deskset/
RGU
6003
unicast
UDP
cFL
cFL
CT
Any
Deskset/
RGU
6005
unicast
UDP
cFL
see note
below
22 **
see note
below
23***
see note
below
B-2
6802987C96-A
July 2011
Table B-1 MCD 5000 Deskset System Ports and Services (Continued)
Index
#
Service
Source
Device
Source
Port
Destination
Device
Destination
Port
Network
Layer 3
Transport
Layer 4
Application Layer
7
24
cFL
Deskset/
RGU
6005
CT
Any
unicast
UDP
cFL
25
O-C
CT
Any
Deskset/
RGU
5063
unicast
TCP
O-C
26
O-C
Deskset/
RGU
5063
CT
Any
unicast
TCP
O-C
*RPDFL
Voice Traffic between MCD 5000 RGUs and between MCD 5000 Desksets
Firewall rules depend on where firewalls are deployed - if protecting all MCD 5000 Desksets and
MCD 5000 RGU sites, then the rule should be configured between MCD 5000 Desksets and
MCD 5000 RGUs, between MCD 5000 RGUs and MCD 5000 Desksets, between MCD 5000
Desksets and MCD 5000 Desksets, and between MCD 5000 RGUs and MCD 5000 RGUs.
**cFL
Voice Control Traffic between MCD 5000 RGUs and between MCD 5000 Desksets
Firewall rules depend on where firewalls are deployed - if protecting all MCD 5000 Desksets and
MCD 5000 RGU sites, then the rule should be configured between MCD 5000 Desksets and
MCD 5000 RGUs, between MCD 5000 RGUs and MCD 5000 Desksets, between MCD 5000
Desksets and MCD 5000 Desksets, and between MCD 5000 RGUs and MCD 5000 RGUs.
***cFL
6802987C96-A
July 2011
used for Audio monitoring.
B-3
B-4
6802987C96-A
July 2011
Appendix
C
MCD 5000 RGU and MCD 5000 Deskset
Specifications
MCD Deskset System Operation and Environmental

Specifications
MCD 5000 Radio Gateway Unit

Table C-1 MCD 5000 RGU Specifications
Details
Specification
Dimensions
Height: 1.65" (42 mm)

Width: 8.58" (218 mm)
Depth: 10.39" (264 mm)
Weight: 5.73 lb (2.6 Kg)
Environmental
Operating temperature:
30 C to 60 C (22 F to 140 F)
Storage temperature:
40 C to 80 C (40 F to 176 F)
Humidity:
5% to 95% @ +50 C (122 F), Non-Condensing
Power
Input power:
+10.8 to +14VDC, (+12 V nominal)
Dispassion: 9W Max.
37VDC to 57VDC. Powered via POE-PD; meeting 802.3af
Standard for Powered Desksets class 0.
Audio
The end-to-end distortion is no more than 3% THD.

The generated audio is no more than -50 dBm of Hum and
Noise below the rate audio output.
The crosstalk between any audio signals is no more than -65
dBm at 0 dBm transmit audio power.
Supported Radio Protocols
6802987C96-A
July 2011
RS-232 TTL; SB9600; USB 1.1 for MCD 5000 RGU.
C-1
MCD 5000 Deskset
Table C-1 MCD 5000 RGU Specifications (Continued)

Details
Specification
Regulatory-EMC
FCC part 15 class A.
Safety
EN60950-1
Green Product
RoHS, WEEE Mark
Certified Standard
Compliance Requirements
CE Mark, FCC part 15 A Mark, UL Mark (for P.S. only) US

federal government Environmentally Preferable Specification
(EPP) Program.
Non-certified Standard
CSA, UL, MOTOROLA W18 certification, CMM.
Deskset Regulatory
Requirements
For distribution in US, For distribution in Canada, For

distribution in Israel.
Vocoders
G.711 and G.729.
MCD 5000 Deskset

Table C-2 MCD 5000 Deskset Specifications
Details
Specification
Dimensions
Height: 4.17" (106 mm)

Width: 10.35" (263 mm)
Depth: 8.27" (210 mm)
Weight: 3.97 lb (1.8 Kg)
Environmental
Operating temperature:
0 C to 50 C (32 F to 122 F)
Storage temperature:
40 C to 80 C (40 F to 176 F)
Humidity:
5% to 95% @ +50 C (122 F), Non-Condensing
Power
Input power:
+10.8 to +13.2VDC, (+12 V nominal)
Dispassion: 12.5W Max.
37VDC to 57VDC. Powered via POE-PD; meeting 802.3af
Standard for Powered Desksets class 0.
Audio
The end-to-end distortion is no more than 3% THD.

The generated audio is no more than -50 dBm of Hum and
Noise below the rate audio output.
The crosstalk between any audio signals is no more than -65
dBm at 0 dBm transmit audio power.
C-2
Supported Radio Protocols
RS-232 TTL using RJ45 connector; SB9600; USB 2.0.
Regulatory-EMC
FCC part 15 class A.
6802987C96-A
July 2011
MCD 5000 RGU and MCD 5000 Deskset Connectors Specifications
Table C-2 MCD 5000 Deskset Specifications (Continued)

Details
Specification
Safety
EN60950-1
Green Product
RoHS, WEEE Mark
Certified Standard
CE Mark, FCC part 15 A Mark, UL Mark (for P.S. only) US

federal government Environmentally Preferable Specification
(EPP) Program.
Non-certified Standard
CSA, UL, MOTOROLA W18 certification, CMM.
Deskset Regulatory
Requirements
For distribution in US, For distribution in Canada, For

distribution in Israel.
Vocoders
G.711 and G.729.
MCD 5000 RGU and MCD 5000 Deskset Connectors

Specifications
The connectors associated with the MCD 5000 devices are listed below.
Grounding Bolt
The MCD 5000 RGU is equipped with a ground bolt. This bolt is especially required when
the MCD 5000 RGU is installed within RF environment.
4W-E&M Line Connections

The Audio IN of the 4W-E&M connector is fitted for radios with the characteristics given in the table below:
Table C-3 Audio IN
Parameter
6802987C96-A
Value
Radio Input voltage (LINE)
-40dBm to +12dBm@600
Radio Input impedance
600, 10K, Balanced
July 2011
C-3
MCD 5000 Headset Jack Box/DeskMIC Audio Specifications
-40dBm to +15dBm @ 600 is equal to 7.75mv to 3.09v RMS.

The Audio OUT of the 4W-E&M connector is fitted for radios with the characteristics given in the table below:
Table C-4 Radio Output Characteristics
Parameter
Value
Radio Output voltage (LINE)
-40dBm to +12dBm@600
Radio Output impedance
600, 10K, Balanced
-40dBm to +15dBm @ 600 is equal to 7.75mv to 3.09v RMS.
MCD 5000 Headset Jack Box/DeskMIC Audio Specifications

Connection Audio Input
The Audio IN is fitted for headsets with the characteristics given in the table below:
Table C-5 Headset Input Characteristics
Parameter
Headset Output voltage (MIC)
Value
50mV RMS
Remarks
12VDC powered
Connection Audio Output

The Audio OUT is fitted for headsets with the characteristics given in the table below:
Table C-6 Headset Output Characteristics
Parameter
C-4
Value
Headset Input voltage (Earpiece)
200mV RMS
Output Impedance
50
6802987C96-A
July 2011
Radio Digital Communication Connector
Radio Digital Communication Connector

The digital radio port specification for the MCD 5000 Deskset and the MCD 5000 RGU are listed below:
Table C-7 Radio Digital Communication Connector Specifications
MCD 5000 Deskset/
MCD 5000 RGU
6802987C96-A
Protocol
Remarks
MCD 5000 Deskset &

MCD 5000 RGU
RS232
TTL, 300 115Kbps
MCD 5000 Deskset &

MCD 5000 RGU
SB9600
TTL, 9600bps
MCD 5000 RGU
USB
1.1
MCD 5000 Deskset
USB
2.0
July 2011
C-5
C-6
6802987C96-A
July 2011
Appendix
D
MCD 5000 Deskset Call Scenarios
This appendix gives possible MCD 5000 Deskset call scenarios.
Table D-1
No.
6802987C96-A
Possible Call Scenarios

My MCD 5000
Deskset
Other MCD 5000

Desksets
Mobile Radios
on the same
Channel/TG
1.
Press transmit and

talk
Transmit indicator
ON.
Hear Tx-Monitor audio Receive audio.

and see the Talkers
MCD 5000 Deskset
Name.
Transmitter Busy
Indicator ON.
2.
Receive audio (see PTT

ID if applicable)
Receiver indicator
ON.
Receive audio (see

PTT ID if applicable)
Receiver indicator
ON.
Press transmit audio

and talk
3.
Press Base Intercom

and talk
Base Intercom
indicator ON.
Hear Base Intercom

audio and see Talkers
Deskset Name
Base Intercom Red
LED ON.
N/A
4.
Mon-> hear audio
Hear mon. audio
N/A
July 2011
Priority Method
Priorities will follow
implementation of
RPDFL Priority field
1 to 8. RPDFL voice
packet marked with
Supervisor will have
the highest priority.
RPDFL voice packet

marked with Base
Intercom command
will have the lowest
priority.
D-1
D-2
6802987C96-A
July 2011
Appendix
MCD 5000 Deskset and MCD 5000 RGU

Connectors Pinouts and Settings
This appendix contains pin listings for each of the connections to the MCD 5000 RGU and MCD 5000 Deskset.
MCD 5000 Deskset and MCD 5000 RGU Cable Connectors
Table E-1 MCD 5000 Deskset and MCD 5000 RGU Cable Connectors
Table
Number
Connector
Name
Connector
Type
# of Connectors in
MCD 5000
Deskset
6802987C96-A
Remarks
RGU
E2
4W E&M
RJ45
Colored Pink
E3
COMM
RJ45
Colored Blue
E4
JckBx/DskMIC
RJ45
Colored Green/
Orange
E5
Footswitch
KK 3 pos
MOLEX 3 pos.
MOLEX: 26506030
E6
MMI/Local O&M RJ45
E7
External LANPoE
E8
1 (MMI)
1 (Local
O&M)
RJ45
Colored Black
Internal LAN
RJ45
Colored Red
E9
Handset
Connector
RJ22
4P/4C
E-10
Logger
RJ45
1. Colored Gray
2. Same pin list as
4W E&M
July 2011
E-1
4W E&M Connector (RJ45)
4W E&M Connector (RJ45)
Table E-2 Radio 4W E&M Connector Pin List

Pin Number
Signal Name
Characteristics
Tx+/2W
Balanced audio Tx+ or 2w

bidirectional
Tx-/2W
Balanced audio Tx- or 2w

bidirectional
Rx+
Balanced audio Rx+
Rx-
Balanced audio Rx-
PTT -M
I/O open drain 150mA,60V

and optocoupler
COR -E

and optocoupler
5 V Ctrl
5V, 100mA
GND
Analog GND
MCD 5000 Deskset 4W E&M connector Tx pins (1 and 2) run via transformer.
MCD 5000 RGU Radio 1 4W E&M connector Tx pins (1 and 2) run via transformer.
MCD 5000 Deskset 4W E&M connector Rx pins (3 and 4) run via transformer.
MCD 5000 RGU Radio 1 4W E&M connector Rx pins (3 and 4) run via transformer.
MCD 5000 RGU Radio 4 4W E&M connector Tx pins (1 and 2) frequency

response is flat from 3Hz and up to 3400Hz.
COMM Connector
Table E-3 Radio COMM Connector Pin List (RJ45)

Pin Number
1
E-2
Signal Name
SB9600 Data+ /RS232 TX
Characteristics
Balanced bidirectional
data+/unbalanced Tx
6802987C96-A
July 2011
Table E-3
MCD 5000 Headset Jack Box and Desk MIC Connector
Radio COMM Connector Pin List (RJ45) (Continued)
Pin Number
Signal Name
Characteristics
SB9600 Data-/ RS232 RX/

CMOS input
Balanced bidirectional
data-/unbalanced Rx / Used as
CMOS input - 10K pull up to
3.3V
SB9600 Busy/ RS232 RTS/

CMOS input
Bidirectional Busy/ RTS/

CMOS inp. 10K pull up to
3.3V
SB9600 RST/ RS232 CTS/

CMOS input
Reset I/O/ CTS/ CMOS inp.

10K pull up to 3.3V
5V USB
5V, 100mA limit
USB Data+/ RxClk
Host, Low and full speed
USB Data-/TxClk
Host, Low and full speed
GND
Digital GND
MCD 5000 Headset Jack Box and Desk MIC Connector
Table E-4
JckBx/DskMIC Connector Pin List (RJ45)
Pin Number
6802987C96-A
July 2011
Signal Name
Characteristics
GND
Analog GND
Jack Sense
Dry Contact to GND
PTT
Dry Contact to GND
Mic
Microphone input - 50 mV
RMS
GND
Analog GND
Line Monitor
Dry Contact to GND
Earphone
Audio output -200mV RMS at

50 Ohm
GND
Analog GND
E-3
Footswitch Connector
Footswitch Connector
Table E-5 Footswitch Connector Pin List (KK MOLEX 3 pos.)

Pin Number
Signal Name
Characteristics
PTT
Dry Contact to GND
GND
Digital GND
Line Monitor
Dry Contact to GND
MMI/Local O&M Connector
Table E-6
MMI/Local O&M Connector Pin List (RJ45) PoE
Pin Number
E-4
Signal Name
Characteristics
KVL sense
Sense KVL connection input
5V
5V through 10k
Cable sense
Sense cable connection input
GND
Digital GND
Rx
RS232 Rx Input
Tx
RS232 Tx Output
CTS
RS232 Clear to Send
RTS
RS232 Request to Send
6802987C96-A
July 2011
MCD 5000 Deskset/ MCD 5000 RGU External LAN-PoE Connector
MCD 5000 Deskset/ MCD 5000 RGU External LAN-PoE

Connector
The MCD 5000 Deskset requires 802.3 at PoE supply.

Table E-7 MCD 5000 Deskset/MCD 5000 RGU Connector 8 pos. Pin List (RJ45)
Pin Number
Signal Name
Tx +
Tx -
Rx +
Reserved
-48VDC
Rx -
Reserved
GND for 48VDC
Characteristics
-48VDC P.S.
GND for -48VDC P.S.
This connection supports automatic MDI/MDI-X.
Internal LAN Connector
Table E-8 Internal LAN Connector Pin List (RJ45)

Pin Number
6802987C96-A
July 2011
Signal Name
Tx +
Tx -
Rx +
Reserved
Reserved
Characteristics
E-5
MCD 5000 Deskset Handset Connector 4P4C
Table E-8 Internal LAN Connector Pin List (RJ45) (Continued)

Pin Number
Signal Name
Rx -
Reserved
Reserved
Characteristics
This connection supports automatic MDI/MDI-X.
MCD 5000 Deskset Handset Connector 4P4C
Table E-9 MCD 5000 Deskset Handset Connector 4P4C Pin List (RJ22)
Pin Number
Signal Name
Characteristics
GND
Analog GND
Earphone
Audio output -200mV RMS at

50 Ohm
Microphone
Microphone input 50mV RMS
PTT
Dry Contact to GND
MCD 5000 Deskset Logger Cable Connector
Table E-10 MCD 5000 Deskset Logger Cable Connector Pin List (RJ45)
Pin Number
1
E-6
Signal Name
Tx+/2W
Characteristics
Balanced audio Tx+ or 2w
bidirectional
6802987C96-A
July 2011
MCD 5000 Deskset Logger Cable Connector
Table E-10 MCD 5000 Deskset Logger Cable Connector Pin List (RJ45) (Continued)
Pin Number
6802987C96-A
July 2011
Signal Name
Characteristics
Tx-/2W
Balanced audio Tx- or 2w

bidirectional
Rx+
Balanced audio Rx+
Rx-
Balanced audio Rx-
PTT -M

and optocoupler
COR -E

and optocoupler
5 V Ctrl
5V, 100mA
GND
Analog GND
E-7
E-8
6802987C96-A
July 2011
Appendix
Radios Used With the MCD 5000 Deskset

System
The MCD 5000 Deskset System supports the Motorola SB9600 based Radios connected to the MCD
5000 RGU radio ports through a direct serial connection or directly to the MCD 5000 Deskset. MCD
5000 also supports 'virtual control head' functionality to certain Motorola subscriber radios:
6802987C96-A
July 2011
W9 consolettes:
W9 Spectra Consolette
W9 Spectra Plus Consolette
W9 XTL5000 Consolette
CDM Radios:
CDM1550
CDM1550LS
CDM1550LS+
MCS2000 Model III Radio
F-1
F-2
6802987C96-A
July 2011
Appendix
G
Radio Cables Pinouts
This appendix provides information about the pinouts of cables used to connect Motorola radios
to the MCD 5000 RGU. For a list of the cables, see Appendix I.
MCD 5000 Radio Cable - MCS 2000 Model III Radio Pinouts
(cable part number FKN8688)
The MCD 5000 Radio Cable - MCS 2000 Model III radio pinouts (cable part number
FKN8688) are shown in Figure G-1.
6802987C96-A
July 2011
G-1
MCD 5000 Radio Cable - MCS 2000 Model III Radio Pinouts (cable part number FKN8688)
Figure G-1 MCD 5000 Radio Cable MCS 2000 Cable Pinouts (cable part number FKN8688)
JA = RJ45 connector for the 4W-E&M MCD 5000 Deskset/MCD 5000 RGU radio port.
JC = RJ45 connector for the COMM MCD 5000 Deskset/MCD 5000 RGU radio port.
JB = 25 pin connector for the MCS2000 radio accessory connector.
G-2
6802987C96-A
July 2011
MCD 5000 Radio Cable CDM Pinouts (cable part number FKN8689)
MCD 5000 Radio Cable CDM Pinouts (cable part number

FKN8689)
The MCD 5000 Radio Cable - CDM radio pinouts (cable part number FKN8689) are shown in Figure G-2.
Figure G-2 MCD 5000 Radio Cable - CDM Radio Pinouts (cable part number FKN8689)
JB = 25 pin connector for the CDM radio accessory connector.
6802987C96-A
July 2011
G-3
MCD 5000 Radio Cable W9 Pinouts (cable part number FKN8690)
MCD 5000 Radio Cable W9 Pinouts (cable part number

FKN8690)
The MCD 5000 Radio Cable W9 radio pinouts (cable part number FKN8690) are shown in Figure G-3.
Figure G-3 MCD 5000 Radio Cable W9 Radio Pinouts (cable part number FKN8690)
JB = 25 pin connector for the CDM radio accessory connector.
G-4
6802987C96-A
July 2011
MCD 5000 Deskset System with OMC Installation and Configuration Guide MCD 5000 Radio Cable DS-DJB-W9 Pinouts (cable part number FKN8691)
MCD 5000 Radio Cable DS-DJB-W9 Pinouts (cable part

number FKN8691)
The MCD 5000 Radio Cable DS-DJB-W9 radio pinouts (cable part number
Figure G-4
MCD 5000 Radio Cable DS-DJB-W9 Radio Pinouts (cable part number FKN8691)
JB = 25 pin connector for connecting to the customer cable already hooked
up to the W9 radio accessory connector.
JD = 25 pin connector for the rear side of the DJB Model L3208.
JE = RJ45 connector for the front side of the DJB Model L3208.
6802987C96-A
July 2011
G-5
MCD 5000 Radio Cable DS-DJB-MCS Pinouts (cable part number FKN8692)
MCD 5000 Radio Cable DS-DJB-MCS Pinouts (cable part

number FKN8692)
The MCD 5000 Radio Cable DS-DJB-MCS radio pinouts (cable part number
Figure G-5
G-6
MCD 5000 Radio Cable DS-DJB-MCS Radio Pinouts (cable part number FKN8692)
6802987C96-A
July 2011
MCD 5000 Deskset System with OMC Installation and Configuration Guide MCD 5000 Radio Cable DS-DJB-MCS Pinouts (cable part number FKN8692)
JB = 25 pin connector for connecting to the customer cable already hooked
up to the MCS radio accessory connector.
JD = 25 pin connector for the rear side of the DJB Model L3208.
JE = RJ45 connector for the front side of the DJB model L3208.
6802987C96-A
July 2011
G-7
MCD 5000 Radio Cable DS-DJB-CDM Pinouts (cable part number FKN8693)
MCD 5000 Radio Cable DS-DJB-CDM Pinouts (cable part

number FKN8693)
The MCD 5000 Radio Cable DS-DJB-CDM radio pinouts (cable part number
Figure G-6
MCD 5000 Radio Cable DS-DJB-CDM Radio Pinouts (cable part number FKN8693)
JB = RJ45 connector for connecting to the customer cable already hooked
up to the CDM radio accessory connector.
JD = RJ45 connector for the rear side of the DJB Model L3239.
JE = RJ45 connector for the front side of the DJB Model L3239.
G-8
6802987C96-A
July 2011
MCD 5000 Headset Jack Box Cable Pinouts (cable part number FKN8694)
MCD 5000 Headset Jack Box Cable Pinouts (cable part

number FKN8694)
The MCD 5000 Headset Jack Box Cable pinouts (cable part number FKN8694) are shown in Figure G-7.
Figure G-7 MCD 5000 Headset Jack Box Cable Pinouts (cable part number FKN8694)
JA = RJ45 connector for the JCKBX MCD 5000 Deskset/MCD 5000 RGU port.
JB = RJ45 connector for the JACKBOX accessory connector.
Cable length: 2900 mm.
6802987C96-A
July 2011
G-9
MCD 5000 External LAN/ PoE Cable Pinouts (cable part number FKN8695)
MCD 5000 External LAN/ PoE Cable Pinouts (cable part

number FKN8695)
The MCD 5000 External LAN/ PoE Cable pinouts (cable part number FKN8695) are shown in Figure G-8.
Figure G-8
MCD 5000 External LAN/ PoE Cable Pinouts (cable part number FKN8695)
JA, JB = RJ45 connectors. The cable is used for either the External or Internal LAN connection,
and the use of the cable for either one of these is marked by sticking an appropriate supplied label.
Cable length: 2900 mm.
G-10
6802987C96-A
July 2011
MCD 5000 Deskset Logger Cable Pinouts (cable part number FKN8696)
MCD 5000 Deskset Logger Cable Pinouts (cable part

number FKN8696)
The MCD 5000 Deskset Logger Cable pinouts (cable part number FKN8696) are shown in Figure G-9.
Figure G-9
6802987C96-A
July 2011
MCD 5000 Deskset Logger Cable Pinouts (cable part number FKN8696)
G-11
G-12
6802987C96-A
July 2011
Appendix
H
Cables Used for MCD 5000 Deskset
Connection in Parallel to MC3000
Cable Used for Other than CDM 1550 Family
Connecting the MCD 5000 Deskset in parallel with the MC3000 units to different Radios is made using the
Digital Junction Box (DJB) to Radio cable. The following scheme describes the special cable:
Figure H-1 MCD 5000 Deskset in Parallel to MC3000 Units using DJB to Radio other than CDM
The Customer Existing MC3000 Radio Cable is already installed at the customer site that includes the
MC3000, the attached radio and the L3208 Digital Junction Box (if installed). The cable shown in the
left side of the figure is the cable that serves the parallel connection between the MCD 5000 Deskset
(or MCD 5000 RGU) and the MC3000 to the relevant (non-CDM 1550 family) radio.
Connect each cable end connector to the appropriate device according to the labels on the cable.
6802987C96-A
July 2011
H-1
Cable Used for CDM 1550 Family
Appendix H: Cables Used for MCD 5000 Deskset Connection in Parallel to MC3000
The CDM Radio is equipped with RLN4802 Remote Adapter Kit.

The CDM Radio is connected to DJB using RJ45-to-RJ45 cable and RJ45-to-DB25 adaptor
(3210761). The following scheme describes the special cable:
Figure H-2 MCD 5000 Deskset in Parallel to MC3000 Units using DJB to CDM Radio
The Customer Existing MC3000 Radio Cable is already installed at the customer site that includes the
MC3000, the attached radio and the L3239 Digital Junction Box (if installed). The cable shown in the
left side of the figure is the cable that serves the parallel connection between the MCD 5000 Deskset
(or MCD 5000 RGU) and the MC3000 to the relevant CDM 1550 family radio.
H-2
6802987C96-A
July 2011
Appendix
Radio Cables and Replacement Parts

This appendix provides information about the special cables used to connect Motorola radios to the MCD
5000 RGU, and about the various replacement parts of the MCD 5000 Deskset.
The list of supported Radio cables is provided in the table below:
Table I-1 List of Supported Cables
Cable No.
6802987C96-A
Cable Name
Use for
FKN8688
Cable - MCD 5000 RGU

to MCS 2000 III Direct
Connect
Connecting MCD 5000

Deskset or MCD 5000
RGU to MCS2000 Model
III Radio.
FKN8689

to CDM 1550 Series Direct
Connects
Connecting MCD 5000

Deskset or MCD 5000
RGU to CDM1550,
CDM1550LS or
CDM1550LS+ Radio.
FKN8690

to ASTRO Consolette W9
Direct Connect
Connecting MCD 5000

Deskset or MCD 5000
RGU to W9 Spectra
consolette, W9 Spectra
Plus Consolette or W9
XTL5000 Consolette
Radio.
FKN8691
Cable - MCD 5000 RGU to

MC3000 DJB for ASTRO
Consolette W9
Connecting MCD 5000

Deskset or MCD 5000
RGU in parallel with
DJB to W9 Spectra
consolette, W9 Spectra
Plus Consolette or W9
XTL5000 Consolette
Radio.
FKN8692
Cable - MCD 5000 RGU to Connecting MCD 5000

MC3000 DJB for MCS 2000 Deskset or MCD 5000
III
RGU in parallel with DJB
to MCS2000 Model III
Radio.
FKN8693

to MC3000 DJB for CDM
1550 Series
July 2011
Remarks
Connecting MCD 5000

Deskset or MCD 5000
RGU in parallel with
DJB to to CDM1550,
CDM1550LS or
CDM1550LS+ Radio.
I-1
Table I-1
Appendix I: Radio Cables and Replacement Parts
List of Supported Cables (Continued)
Cable No.
Remarks
Cable Name
Use for
FKN8694
Cable - MCD 5000 Deskset

to Headset Jack Box
Connecting the FKN7470

Jackbox to the MCD 5000
Deskset.
FKN8695
Ethernet Cable 10' with Red

& Black Labels
Connecting the MCD 5000 The Cable kit include

Deskset or the MCD 5000 red and black labels
RGU to the customer LAN. to be attached by
the operator to the
FKN8695 cable to
indicates it usage as
External (black) or
internal (red) LAN
cable.
FKN8696
Cable - MCD 5000 Deskset

to Logger
Connecting the MCD

5000 Deskset to an analog
Logger (Recorder).
The FKN7470
Jackbox include
the FKN8694 cable
within the kit.
The list of replacement parts for the MCD 5000 Deskset/MCD 5000 RGU is provided in the table below:
Table I-2 Replacement Parts
Part
Number
I-2
Description
FHN7290
MCD 5000 Deskset K-Style Handset (includes coiled cable)
FHN7469
MCD 5000 Deskset/MCD 5000 RGU Power Supply with USA Power Cord
FHN6726
MCD 5000 Deskset/MCD 5000 RGU Power Supply without Power Cord
FKN8706
Power Cord for USA MCD 5000 Deskset/MCD 5000 RGU Power Supply
FHN7470
MCD 5000 Headset Jack Box and Cable
FKN8694
Cable MCD 5000 Headset Jack Box
6802987C96-A
July 2011
Appendix
Contacting Motorola
Motorola has made every effort to ensure that the MCD 5000 Deskset System is of excellent quality.
However, if you experience any problem with the product, refer to this User Guide for assistance.
If you need more help, please contact your Motorola System Support Center (SSC).
Motorola Support Centers
Motorola provides support centers that can help technicians and engineers resolve system
problems and ensure that warranty requirements are met.
Motorola assigns a tracking ticket number that identifies the specific call. This allows Motorola to
track problems, resolutions, and activities for the call. If possible, communicate the resolution and a
status of call so that the support center can note the resolution and close the ticket.
Gathering Information before Calling Motorola

Before calling one of the support centers, log all steps that you or your technicians took to
troubleshoot the problem and any results of those steps. The support center can use this
information to determine the appropriate support actions.
Collect the following information:
6802987C96-A
July 2011
Unit ID hexadecimal number (for example, 2CB).
Location of the system.
Date the system was put into service.
Software and firmware versions for:
Gateway Units (MCD 5000 RGU, MCD 5000 Deskset)
Configuration Tool (CT) software
MCD 5000 ACP
OMC Server
J-1
Telephone Numbers
Appendix J: Contacting Motorola
Hardware information (type of PC, manufacturer, manufacturer, version, type of

operating system, memory size, and disk space) for:
OMC Server
ACP PC
CT PC
Symptom or observation of the problem, such as:
When did it first appear?
Can it be reproduced?
Are there any other circumstances (for example, loss of power) contributing to the problem?
Maintenance action preceding the problem, such as:
Upgrade of software or equipment.
Changes to hardware or software configuration.
Reload of software from a backup disk or from the CD-ROM with the version and date.
Telephone Numbers
After collecting the information pertaining to the problem, contact your Motorola System Support Center (SSC):
J-2
From the USA 800-221-7144
From Latin America - 847-725-8367
For all other international customers - 847-576-7300
6802987C96-A
July 2011
Glossary
Glossary
Glossary
access radio See donor radio.
ACP See MCD 5000 ACP.
ACP Client PC The ACP Client PC runs the Administrator Control Panel software
application. The ACP Client PC runs on the Microsoft XP operating system.
Administrator Control Panel (ACP) See MCD 5000 ACP.
Advanced Encryption Standard (AES) AES is a block cipher adopted as an
encryption standard by the National Institute of Standards and Technology (NIST) in
2001 to replace Data Encryption Standard (DES). AES supports encryption key sizes of
128 bits, 192 bits, and 256 bits, while DES only offers 56 bit keys.
AES See Advanced Encryption Standard.
audio encryption Audio encryption ensures that conversations over
the IP network are private.
Carrier Operated Relay (COR) A device that causes a repeater to
transmit in response to a received signal.
CCSI Motorola Customer Center for Solution Integration
CDM Cellular Digital Message (type of radio).
Central Processing Unit (CPU) The heart of a computer system, where
arithmetic and logical operations are performed.
CHI See Concentration Highway Interface bus.
Concentration Highway Interface (CHI) bus In the MCD 5000 Deskset System, the
CHI bus is a full duplex interface bus designed for future interface with the gateway unit (GU).
Configuration Tool The Configuration Tool is designed to run on a technician laptop
PC and is used to configure a new GU, modify a GU configuration, and perform audio
monitoring tasks when the technician is at the site where the GU is located.
COR See Carrier Operated Relay.
County The second highest level of the MCD 5000 Deskset System
hierarchy. A county consists of PSAPs.
CPU See Central Processing Unit.
CRC Cyclic Redundancy Code
CT See Configuration Tool.
D2A Digital to Analog.
dBm See decibel.
DC See direct current.
decibel (dBm) The decibel referenced to one milliwatt, a measure of the power value.
6802987C96-A
July 2011
GL-1
Glossary
default gateway In computer networking, a gateway is a node (a router) on a

TCP/IP network that serves as an access point to another network.
direct current (DC) The continuous flow of electricity through a conductor
where electric charges flow in the same direction.
donor radio Donor radios are normally mobile control stations for a given
radio system which are connected to one of the MCD 5000 RGU radio ports.
The radio and MCD 5000 RGU/MCD 5000 Deskset are placed in the coverage
area of the radio system to establish a connection.
DNS servers DNS Servers translate easily remembered domain names and hostnames
into the corresponding numeric Internet Protocol (IP) addresses.
DS See MCD 5000 Deskset.
DSP Digital Signal Processing.
E&M See ear and mouth signaling.
ear and mouth signaling (E&M) E&M is an analog trunk interface with
a trunk circuit side and a signaling unit side.
Electromagnetic Compatibility (EMC) Branch of electrical sciences which studies
the unintentional generation, propagation and reception of electromagnetical energy with
reference to the unwanted effects that such an energy may induce. In particular, the
aim of EMC is the correct operation, in the same environment, of different equipment
which involve electromagnetic phenomena in their operation.
EMC See Electromagnetic Compatibility.
EME Electromagnetic energy.
ESD Electrostatic discharge.
File Transfer Protocol (FTP) A standard Internet protocol, the simplest way
to exchange files between computers on the Internet. Like the Hypertext Transfer
Protocol (HTTP), which transfers displayable web pages and related files, and the
Simple Mail Transfer Protocol (SMTP), which transfers e-mail, FTP is an application
protocol that uses the Internet's TCP/IP protocols.
firewall A security system that enforces an access control policy between a network and
the Internet. For computer networks, it separates a local network from the outside world.
FTP See File Transfer Protocol.
FW See firewall.
G.711 Encoding Type An ITU standard for audio companding. Represents 8 bit
compressed pulse code modulation (PCM) samples for signals of voice frequencies, sampled
at a rate of 8000 samples / second. Creates a 64 Kbit/second bitstream.
G.729 Encoding Type An audio data compression algorithm that compresses voice
audio in chunks of 10 milliseconds (or multiples thereof). Mostly used in Voice over
IP (VoIP) applications due to its low bandwidth requirement. Standard G.729 operates
at 8 Kbits / second. The annex B of G.729 is a silence compression scheme supporting
Voice Activity Detect (VAD) and Comfort Noise Generator (CNG).
Gateway Unit (GU) In the MCD 5000 Deskset System there are two types of GUs:
MCD 5000 Deskset and MCD 5000 Radio Gateway Unit (RGU). The MCD 5000 Deskset
can also have one port, where a radio device can be connected. The MCD 5000 RGUs
have 4 radio ports and can connect with up to 4 radio devices simultaneously.
GB See gigabyte.
GL-2
6802987C96-A
July 2011
Glossary
gigabyte (GB) A GB is one billion bytes.

graphical user interface (GUI) A GUI is a user interface in which information is
displayed graphically on the screen. A combination of icons, scroll bars, windows, help
systems, menus, and other services are also used to simplify a program.
group A list of resources.
GU See Gateway Unit.
GUI See graphical user interface.
hostname A hostname is a label that is assigned to a device connected to a
computer network which is used to identify the device in various forms of electronic
communication such as the World Wide Web, e-mail or Usenet.
HTTP See Hyper Text Transfer Protocol.
Hyper Text Transfer Protocol (HTTP) HTTP is the set of rules for exchanging
files (text, graphic images, sound, video, and other multimedia files) on the World Wide
Web. Relative to the TCP/IP suite of protocols, which is the basis for information
exchange on the Internet, HTTP is an application protocol.
IA Information Assurance.
IETF See Internet Engineering Taskforce.
IKE See Internet Key Exchange.
Internet Engineering Taskforce (IETF) IETF is an open international
community of network designers, operators, vendors, and researchers concerned
with Internet architecture evolution and operation.
Internet Key Exchange (IKE) IKE is a protocol used to distribute
encryption and authentication keys and to provide a way for VPN endpoints
to agree on how the data should be protected.
Internet Protocol (IP) IP is a set of standards designed to enable different types
of computers to communicate with one another and to exchange information through
the Internet. Internet protocol (IP) provides the appearance of a single, seamless,
communication system and makes the Internet a virtual network.
interoperability Interoperability is defined by the Association of Public-Safety
Communications Officials (APCO) as the ability of different government agencies
or first responders (such as law enforcement, EMS, fire fighters) to communicate
within and across departmental and jurisdictional boundaries. First responders identify
interoperability as a key factor in the success of any coordinated response.
IP See Internet Protocol.
IRC Important Radio Channel.
IRC Proxy A Radio Proxy running on an MCD 5000 Deskset acts as a mediator
between the MCD 5000 Deskset's and the IRC; it is utilized for multiple MCD
5000 Desksets, on the same LAN, to connect with the same remote Important
Radio Channel (IRC). An Important Radio Channel is defined by the customer to be
important for many MCD 5000 Deskset operators to listen to.
Jitter Jitter is the phase shift of digital pulses over a transmission medium.
LAN See Local Area Network.
LED See Light Emitting Diode.
6802987C96-A
July 2011
GL-3
Glossary
Light Emitting Diode (LED) An LED is a semiconductor diode that emits light when
voltage is applied. LEDs can emit red, green, yellow, blue, and other colors. LEDs are used as
power indicators, information displays, and as light sources in some fiber optic systems.
Local Area Network (LAN) A LAN is a high speed data communication system for
linking computer terminals, programs, storage, and graphic devices at multiple workstations
distributed over a relatively small geographic area such as a building or campus.
MB See megabyte.
Mbps See million bits per second.
MCD 5000 ACP Administrator Control Panel MCD 5000 PC application,
allows an administrator located anywhere in the system, to perform management
activities for the MCD 5000 Deskset System with OMC .
MCD 5000 Configuration Tool with OMC The Configuration Tool is designed to run
on a technician laptop PC and is used to configure a new MCD 5000 Deskset/MCD 5000
RGU device, modify an MCD 5000 Deskset/MCD 5000 RGU configuration, and perform
audio monitoring tasks when the technician is at the site where the GU is located.
MCD 5000 Configuration Tool without OMC The MCD 5000 without
OMC Configuration Tool PC application is used to define and maintain an
MCD 5000 Deskset System without OMC.
MCD 5000 Deskset The MCD 5000 Deskset is a phone-like device used by the
End-User for operating the MCD 5000 Deskset System. It provides the MCD 5000
Deskset user position of the MCD 5000 Deskset System. The MCD 5000 includes the
Buttons & Display Unit used by the MCD 5000 end-user as the Man-Machine Interface.
Each MCD 5000 Deskset connects to a single Radio Device at a time.
MCD 5000 Deskset GUI The MCD 5000 Deskset graphical user interface.
MCD 5000 Deskset Radio Gateway Unit (RGU) The MCD 5000 Radio
Gateway Unit connects Radio equipment to the MCD 5000 Deskset System. The
MCD 5000 RGU can interface up to 4 Radio devices.
MCD 5000 OMC Server The OMC Server is the main management server in the
system, a central repository where all system users (administrators, dispatchers, radios)
are registered, and where system-wide information (active patches, security parameters,
and so on) is stored. The server runs on the Red Hat Linux operating system. A user level
interface to the OMC is provided by the Administrator Control Panel (ACP) Client PC
and a command line maintenance interface is available on the OMC Server.
MDC See Motorola Digital Control.
msec See millisecond.
megabyte (MB) A MB is one million bytes.
million bits per second (Mbps) Mbps is the data transmission rate
measured in millions of bytes per second.
millisecond (msec) An msec is the amount of time equal to one-thousandth (.001) of a second.
Motorola Digital Control A Motorola two-way radio low-speed data system
using audio frequency shift keying (AFSK). Data bursts are sent over the radio system's
voice channel. Also known as MDC-1200 and MDC-600.
netmask address A netmask is a 32-bit mask used to divide an IP address
into subnets and specify the network's available hosts.
GL-4
6802987C96-A
July 2011
Glossary
O&M Operations and Maintenance. An option on the menu bar on the Administrator
Control Panel (ACP) main window and the Configuration Tool main window.
OMC Operations Management Center. The OMC is a location that houses the
OMC Server, which contains the system database; and often the ACP Client PC,
which enables an administrator to manage the system.
OMC See MCD 5000 OMC Server.
OMC Server See MCD 5000 OMC Server
Operating System (OS) The OS is the underlying computer software that controls
the execution of application programs and enables the computer to communicate
with the operator. The operating system performs essential housekeeping tasks
such as input/output (I/O) control and memory allocation.
OS See Operating System.
P2P See peer-to-peer.
packet jitter Packet jitter is short term variations in packet arrival times due to an error
along the path or Internet congestion, resulting in audio impairment if severe.
packet loss Packet loss is a condition in which data packets appear to be transmitted
correctly to one end of a connection but never arrive at the destination due to an error
along the path or Internet congestion, resulting in audio impairment.
peer-to-peer (P2P) P2P is a network connection where either system
involved in the connection can be a client or server.
pin A pin is a lead protruding from a connector.
portable radio A subscriber radio, which transmits (receives) audio over the air on a
specific channel to (from) mobile control station physically connected to MCD 5000 RGU.
MCD 5000 RGU transmits (receives) audio via physically connected mobile control station.
Primary Interface (network adapter) The interface the operating system
identifies as the first adapter in the list of network adapters.
PSAP See Public Safety Answering Point.
PTT Push To Talk.
Public Safety Answering Point (PSAP) The second lowest level of
the MCD 5000 Deskset System hierarchy. It represents the site where MCD
5000 Desksets and MCD 5000 RGUs are located.
QoS See Quality of Service.
Quality of Service (QoS) An alarm category which indicates a failure is degrading service.
rack mounting bracket The rack mounting bracket is used to mount
an MCD 5000 RGU to a rack.
radio frequency (RF) RF is electromagnetic energy wavelengths above the audio
range and below visible light, typically between 30 KHz and 300 GHz.
Radio Gateway Unit (RGU) See MCD 5000 RGU.
Region A geographic area consisting of counties.
Remote PTT Dedicated Framing Layer (RPDFL) In the MCD 5000 Deskset
System, used to implement the radio-service function.
RF See radio frequency.
RGU See Radio Gateway Unit.
6802987C96-A
July 2011
GL-5
Glossary
router A router is a protocol-dependent device that connects subnetworks. Routers

can break down very large networks into manageable subnetworks but introduce
longer delays and have slower throughput rates than bridges.
RPDFL See Remote PTT Dedicated Framing Layer.
RPDFL ID RPDFL Identifier. Used by the applications to identify the MCD
5000 Deskset or the radio port on the MCD 5000 RGU as a unique resource
within the MCD 5000 Deskset System. Duplicate RPDFL IDs can cause system
failure and cannot be permitted within the system.
Rx Rx is receive or receiver.
Secure Sockets Layer (SSL) Secure Sockets Layer is an Internet Engineering
Task Force (IETF) security protocol that provides authentication and encryption over
the Internet. It provides services at layer 4 and secures two applications.
SNMP See Simple Network Management Protocol.
SSL See Secure Sockets Layer.
System Planner A Motorola internal document that provides information relevant
to planning a Motorola MCD 5000 Deskset system. It describes the architecture, the
supported features, various considerations that must be taken into account when designing
the system and information about how to order the MCD 5000 Deskset System.
talkpath A talkpath is a call across the MCD 5000 Deskset System.
TCP Transmission Control Protocol
Tx Tx is transmit or transmitter.
UDP See User Datagram Protocol.
Universal Serial Bus (USB) USB is a hardware interface for low-speed computer
peripherals. USB has a maximum bandwidth of 12 Mbps and supports hot swapping so that
devices can be plugged into (and removed from) USB ports without turning the computer off.
USB See Universal Serial Bus.
User Datagram Protocol (UDP) UDP is a TCP/IP protocol describing
how messages reach application programs.
VAD See Voice Activity Detector.
VoIP See Voice Over Internet Protocol.
Voice Activity Detector (VAD) An algorithm used in speech processing wherein the
presence or absence of human speech is detected from the audio samples. VAD inserts
artificial noise during silent periods of speech, thus saving bandwidth.
Voice Over Internet Protocol (VoIP) VoIP is a two-way transmission of
audio over an intranet that is called "Internet telephony" when transmitted over the
Internet. Both parties involved in an Internet/intranet telephone conversation must
have software that uses the same communications protocol. Users are identified by
the IP (Internet protocol) address rather than a telephone number.
vocoder A vocoder is voice and a coder, a voice processing technique that
converts spoken language into digital information.
VPN Virtual Private Network.
WAN See Wide Area Network.
Wide Area Network (WAN) A WAN is a public or private data communication
system for linking computers distributed over a large geographic area.
GL-6
6802987C96-A
July 2011
Index
Index
AC power installation guidelines . . . . . . .

active OMC server . . . . . . . . . . . . . .
Administrator Control Panel (ACP) application
installing . . . . . . . . . . . . . . . . .
used for troubleshooting . . . . . . . . . .
Administrator Control Panel (ACP) Client PC
cabling . . . . . . . . . . . . . . . . . .
functional description . . . . . . . . . . .
installing software . . . . . . . . . . . . .
location and layout . . . . . . . . . . . . .
photo
front . . . . . . . . . . . . . . . . . .
.
.
2-8
7-3
.
.
5-5
7-1
.
.
.
.
5-4
5-2
5-4
5-4
5-3
Administrator Control Panel (ACP) Client PC (contd.)

photo (contd.)
rear . . . . . . . . . . . . . . . . . . . . 5-3
physical description . . . . . . . . . . . . . 5-2
agency
affiliating with a GU
with the Configuration Tool . . . . . . . . 6-24
audio monitoring
for gateway units
audio recognition statistics . . . . . . . . . . . 6-75
cabling
Administrator Control Panel (ACP) Client
PC . . . . . . . . . . . . . . . . . . . . . 5-4
microphone . . . . . . . . . . . . . . . . . 7-8
Client PC
for Administrator Control Panel (ACP) . . . . 5-1
Configuration Tool . . . . . . . . . . . . . . . 6-1
accessing OMC server . . . . . . . . . . . . 6-2
audio monitoring settings
setting graph view . . . . . . . . . . . . . 6-64
setting Y axis options . . . . . . . . . . . 6-65
firewall alerts . . . . . . . . . . . . . . . . 7-3
GU audio monitoring. . . . . . . . . . . . . 6-62
GU configuration
cloning . . . . . . . . . . . . . . . . . . 6-43
copying . . . . . . . . . . . . . . . . . . 6-47
modifying . . . . . . . . . . . . . . . . . 6-22
reading . . . . . . . . . . . . . . . . . . 6-54
saving to a file. . . . . . . . . . . . 6-50, 6-52
GU software version
activating . . . . . . . . . . . . . . . . . 6-83
installing . . . . . . . . . . . . . . . . . 6-81
removing . . . . . . . . . . . . . . . . . 6-82
GUs
adding . . . . . . . . . . . . . . . . . . 6-21
configuring system parameters for an
individual . . . . . . . . . . . . . . . . . 6-36
connecting to . . . . . . . . . . . . . . . 6-17
6802987C96-A
July 2011
Configuration Tool (contd.)

GUs (contd.)
removing . . . . . . . . . . . . . . .
resetting. . . . . . . . . . . . . . . .
viewing radio activity statistics . . . . .
installing . . . . . . . . . . . . . . .
radio button programming . . . . . . . .
system logs . . . . . . . . . . . . . . .
clearing the Logger window . . . . . .
determining log file content . . . . . .
including date for logger entries . . . .
saving the log to a file . . . . . . . . .
setting level of Logger window messages
setting Logger window content . . . . .
setting Logger window message type . .
viewing the log . . . . . . . . . . . .
system monitoring with. . . . . . . . . .
system requirements . . . . . . . . . . .
technician profile
creating . . . . . . . . . . . . . . . .
connection list
OMC servers
viewing in the ACP . . . . . . . . . .
Connection Mode . . . . . . . . . . . . .
Console PC
operating and environmental specifications
county
. . 6-56
. . 6-55
. . 6-75
6-1 to 6-2
. . 6-84
. . 6-76
. . 6-77
. . 6-80
. . 6-79
. . 6-79
. . 6-77
. . 6-77
. . 6-78
. . 6-76
. . 6-62
. . 6-1
. .
6-2
. . 6-61
. . 7-7
. .
2-6
IX-1
Index
customer support . . . . . . . . . . . . . . . .
county (contd.)
affiliating with a GU (contd.)
J-1
echo suppression . . . . . . . . . . . . . . . . 6-63

Electromagnetic Energy (EME) . . . . . . . . . 2-1
electromagnetic safety requirements . . . . . . .

environmental considerations . . . . . . . . . .
2-9
2-5
failover options for servers . . . . . . . . . . . 7-7

FCC requirements . . . . . . . . . . . . . 2-1, 2-9
firewall
alerts . . . . . . . . . . . . . . . . . . . . 7-3
frame duration
configuring
FTP file loads to GUs. . . . . . . . . . . . . . 7-13
G.711 Encoding Type

configuring parameters
with the Configuration Tool
Gateway Unit
activating a software version
adding
audio monitoring
cloning a configuration
configuring system parameters
individual . . . . . . . . . .
connecting to
connectors pin list . . . . . .
copying a configuration
IP address
Gateway Unit (contd.)

IP address (contd.)
changing . . . . . . . . . . . . . . . . . 6-32
modifying configuration
operating and environmental specifications . . 2-6
reading the configuration
removing
removing a software version
resetting
saving a configuration to a file
with the Configuration Tool . . . . . 6-50, 6-52
software version installation
troubleshooting . . . . . . . . . . . . . . . 7-6
viewing radio activity statistics
. . . . . . . . 6-38
. . . . . . . . 6-83
. . . . . . . . 6-21
. . . . . . . . 6-62
. .
for
. .
. .
. . . . . . 6-43
an
. . . . . . 7-12
. . . . . . 6-36
. . . . . . . . 6-17
. . . . . . . . E-1
. . . . . . . . 6-47
hardware installation
client PC . . . .
gateway units . .
general . . . . .
headset
troubleshooting .
IX-2
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . .
5-1
4-1
2-1
. . . . . . . . . . . . . .
7-8
headset (contd.)
volume
setting with the Configuration Tool . . . . . 6-62
Headset
installing . . . . . . . . . . . . . . . . . . 4-15
6802987C96-A
July 2011
Index
installation of hardware
client PC . . . . . .
gateway units . . . .
general . . . . . . .
installation of software .
IP address
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
IP address (contd.)
configuring for servers .
gateway units . . . . .
OMC server
affiliating with a site .
connection list . . . .
5-1
4-1
2-1
5-4
. . . . . . . 3-12 to 3-13
. . . . . . . . 6-17, 6-32
. . . . . . . . . . . 6-37
. . . . . . . . . . . 6-61
Jitter Buffer
configuring
Log file
configuring on the CT Settings window
printing with date
from the Configuration Tool . . . .
saving
with the Configuration Tool . . . .
setting content
Logger window
clearing
Logger window (contd.)

configuring on the CT Settings window
setting content
setting message level
setting message type
troubleshooting tips . . . . . . . . .
viewing
. . . . 6-59
. . . . 6-79
. . . . 6-79
. . . . 6-80
. . . . 6-77
. . . . 6-59
. . . . 6-77
. . . . 6-77
. . . . 6-78
. . . . 7-2
. . . . 6-76
maintenance requiring two people

MapPoint sofware . . . . . . .
MCD 5000 Deskset
installing . . . . . . . . . .
MCD 5000 RGU
installing . . . . . . . . . .
microphone
. . . . . . . .
. . . . . . . .
microphone (contd.)
cabling . . . . . . . . . . . . . .
troubleshooting . . . . . . . . . .
volume
setting with the Configuration Tool
monitoring system performance
with the Configuration Tool. . . . .
2-3
5-4
. . . . . . . . 4-12
. . . . . . . . 4-19
. . . . .
. . . . .
7-8
7-8
. . . . . 6-62
. . . . . 6-62
netmask . . . . . . . . . . . . . . . . . . . . 3-12
operating and environmental specifications . . .

gateway units . . . . . . . . . . . . . . .
OMC server . . . . . . . . . . . . . . . .
Operations Management Center (OMC) Server
accessing with Configuration Tool. . . . . .
6802987C96-A
July 2011
.
.
.
2-6
2-6
3-4
6-2
Operations Management Center (OMC) Server (contd.)

configuring
IP address . . . . . . . . . . . . . 3-12 to 3-13
using administration menu tool . . . . . . . 3-20
connection list
IX-3
Index

connection list (contd.)
in the ACP . . . . . . . . . . . . . . . . 6-61
connection mode . . . . . . . . . . . . . . . 7-7
database . . . . . . . . . . . . . . . . . . . 3-3
functional description . . . . . . . . . . . . 3-1
IP address
affiliating with a site . . . . . . . . . . . . 6-37
listed in the ACP . . . . . . . . . . . . . 6-61
logical architecture . . . . . . . . . . . . . . 3-3
application layer . . . . . . . . . . . . . . 3-3

logical architecture (contd.)
database layer . . . . . . . . . . . . . . . 3-3
interface layer . . . . . . . . . . . . . . . 3-3
photo
front view . . . . . . . . . . . . . . . . . 3-5
rear view . . . . . . . . . . . . . . . . . 3-6
physical description . . . . . . . . . . . . . 3-4
system capacity . . . . . . . . . . . . . . . 3-2
troubleshooting . . . . . . . . . . . . . . . 7-3
Public Safety Answering Point (PSAP) (contd.)

affiliating with a GU (contd.)
PTT statistics . . . . . . . . . . . . . . . . . 6-75

Public Safety Answering Point (PSAP)
radio scope test

example . . . . . . . . . . .
with the Configuration Tool. .
radio type . . . . . . . . . . .
radios
programming buttons
redundancy configuration options
region
resource groups . . . . . . . .
R56 Standards and Guidelines for Communication

Sites . . . . . . . . . . . . . . . . . 2-1, 2-6, 2-10
Radio Gateway Unit
Radio Gateway Unit (RGU)
audio monitoring
configuring system parameters for an
individual . . . . . . . . . . . . . . . 6-36, 7-12
IP address
changing . . . . . . . . . . . . . . . . . 6-32
viewing radio activity statistics
. . . . . . . . 6-68
. . . . . . . . 6-66
. . . . . . . . 6-29
. . . . . . . . 6-84
. . . . . . . . 7-7
. . . . . . . . 6-24
. . . . 6-28 to 6-29
safety precautions
general . . . . . . . . . . . . . . . .
hazardous materials . . . . . . . . . .
seismically active areas . . . . . . . . .
SB9600 control button messages . . . . .
security
configuring system parameters for a site
with the Configuration Tool . . . . .
site considerations . . . . . . . . . . .
site preparation . . . . . . . . . . . . . .
software installation . . . . . . . . . . .
speaker
troubleshooting . . . . . . . . . . . .
volume
setting with the Configuration Tool . .
specifications . . . . . . . . . . . . . .
IX-4
.
.
.
.
.
.
.
.
. 2-1
. 2-3
. 2-3
. 6-85
.
.
.
.
.
.
.
.
. 6-37
. 2-5
. 2-4
. 5-4
. . .
7-8
. . . 6-62
. . . 2-6
specifications (contd.)
OMC server . . . . . . . . . . . . . . . . . 3-4
Standards and Guidelines for Communication
Sites . . . . . . . . . . . . . . . . . 2-1, 2-6, 2-10
standby OMC server . . . . . . . . . . . . . . 7-3
support center . . . . . . . . . . . . . . . . . J-1
synchronization
replacing parameters for individual GU with
system-wide parameters . . . . . . . . . . . 7-12
system log
determining log file content
including the date
saving the log to a file
6802987C96-A
July 2011
Index
system log (contd.)

viewing
system monitoring . . . . . . . . . . . . . . . 6-62
system parameters
system parameters (contd.)

configuring for an individual GU
not updated
impact of Yes vs. No response . . . . . . . 7-12
talkpath
configuring parameters
server connection mode . . .
troubleshooting . . . . . . .
technical support . . . . . . . .
technician PC . . . . . . . . .
technician profile
creating
6802987C96-A
July 2011
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 6-38
. 7-7
. 7-6
. J-1
. 6-1
. . . . . . . .
trigger value
for audio monitoring . . . .
troubleshooting. . . . . . . .
OMC servers . . . . . . .
using the ACP . . . . . . .
Tx calibration
example . . . . . . . . . .
with the Configuration Tool.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 6-65
. 7-1
. 7-3
. 7-1
. . . . . . . . . 6-72
. . . . . . . . . 6-69
6-2
IX-5

MCD 5000

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

MCD 5000

Hochgeladen von

Copyright:

Verfügbare Formate

a

2011 Motorola Solutions, Inc. All rights reserved.

First release of MCD 5000 Deskset System with OMC

This page intentionally left blank.

MCD 5000 Deskset Users Authentication . . . . . . . . . . . . . . . . . .

Overview of Operations Management Center Server . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 2: General Hardware Installation Practices

Chapter 3: OMC Server - Installation, Configuration, and Maintenance

OMC Server Logical Architecture . . . . . . . . . . . . . . .

MCD 5000 Deskset System Devices . . . . . . . . . . . . . . . . . . . .

Chapter 4: Installing MCD 5000 Deskset System Units

Chapter 5: Installing the Administrator Control Panel Client PC

Chapter 6: Administering your System with the Configuration Tool

Activating a Software Version on the GU . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-83

Chapter 7: MCD 5000 Deskset System Troubleshooting

MCD 5000 Deskset System Ports and Services . . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendix A: Secure Password Rules

Appendix B: MCD 5000 Deskset System Ports and Services

Appendix C: MCD 5000 RGU and MCD 5000 Deskset Specifications

MCD 5000 Deskset and MCD 5000 RGU Cable Connectors . . . . . . . . . . . . . . . . . . . . .

Appendix D: MCD 5000 Deskset Call Scenarios

Appendix F: Radios Used With the MCD 5000 Deskset System

Appendix I: Radio Cables and Replacement Parts

Figure 1-1: MCD 5000 Deskset System Components Scheme . . . . . . . . . . . . . . . . . .

Figure 6-60: Get GU RPDFL Data Window . . . . . . . . . . . . . . . . . . . . . . . . . . .

This page intentionally left blank.

Table 1-1: Maximum Entities Per Each Hierarchy Level . . . . . . . . . . . . . . . . . . . . . . . 1-6

This page intentionally left blank.

Procedure 3-1: How to Install the OMC Server OS . . . . . . . . . . . . . . . . . . . . . . .

Procedure 6-20: Removing a GU . . . . . . . . . . . . . . . . . . . . . . . . .

Process 1-1: How to Install an MCD 5000 Deskset System . . . . . . . . . . . . . . . . . . . . . . 1-30

This page intentionally left blank.

MCD 5000 Deskset System with OMC

What Is Covered In This Manual?

Chapter 2, "General Hardware Installation Practices"- presents background installation,

Chapter 3, "OMC Server - Installation, Configuration, and Maintenance"- presents

Chapter 5, "Installing the Administrator Control Panel Client PC"- presents

Chapter 7, "MCD 5000 Deskset System Troubleshooting"- presents information

About This Manual

Appendix D, "MCD 5000 Deskset Call Scenarios". This appendix provides

Appendix J, "Contacting Motorola". This appendix provides information for

Helpful Background Information

MCD 5000 Deskset User Guide (6802987C94)

MCD 5000 Deskset System Information Assurance Guide (6802987C98)

Other related documentation:

CRYPTR 2 datasheet on the Motorola website or contact Motorola support.

MC3000TM Digital Deskset Operator and Installation Manual (6880309L15)

CDM1550LS VHF-UHF User Guide (6881094C79)

MCS2000 Model III Users Guide (68P81083C10)

XTL 5000 Consolette Instruction Manual (6881098C21)

RF energy awareness information and operating instructions in the Product

CAUTION Indicates a potentially hazardous situation which, if not avoided, MAY

IMPORTANT contains information that emphasize points or remind readers of something,

This page intentionally left blank.

MCS 2000 Model III Control Station

MCD 5000 Deskset System Use Cases

Chapter 1: MCD 5000 Deskset System Overview

MCD 5000 Deskset System Use Cases

The MCD 5000 Deskset System use cases are as follows:

Used in a very small dispatch center.

MCD 5000 Deskset System Architecture and Functionality

MCD 5000 Deskset System Components Scheme

The system consists of the following components: