iden™ netdispatch messenger (ndm) administration manual

Technical Manual

iDEN™

NetDispatch Messenger (NDM)

Administration manual

68P81001Y98-I

04/25/2011

NDMR01.03.10

iDEN NetDispatch Messenger System

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.

About This ManualPurpose ......................................................................... ATM-1

Customer Network Resolution Center .................................... ATM-2Overview ....................................................................... ATM-2

Related Manuals ..................................................................... ATM-3

Manuals On-line ..................................................................... ATM-4Overview ....................................................................... ATM-4

Reporting Manual Errors ........................................................ ATM-5Overview ....................................................................... ATM-5

Conventions ............................................................................ ATM-6Software ........................................................................ ATM-6Hardware ...................................................................... ATM-6Safety ............................................................................ ATM-6

Product Specific Safety Notices ............................................. ATM-7

General Safety ........................................................................ ATM-8Keep Away From Live Circuits ...................................... ATM-8Ground the Equipment .................................................. ATM-9Electro-Static Discharge ............................................... ATM-9Do Not Operate In An Explosive Atmosphere ............... ATM-9Do Not Service Or Adjust Alone .................................... ATM-9Use Caution When Handling a Cathode-Ray Tube ...... ATM-9Do Not Substitute Parts Or Modify Equipment .............. ATM-9

Revision History .................................................................... ATM-10

Chapter 1NetDispatch Messenger Overview

High-Level Architecture ................................................................ 1-1Overview ............................................................................. 1-1Purpose of NDM ................................................................. 1-1NDM Product Description ................................................... 1-2

Dispatch Messenger ..................................................................... 1-3Overview ............................................................................. 1-3PC Requirements ................................................................ 1-3Downloading Dispatch Messenger ..................................... 1-4Dispatch Messenger Homepage ......................................... 1-5Basic Operation .................................................................. 1-5User Features ..................................................................... 1-5Business Unit Description ................................................. 1-11Auto e-Mail Notification ..................................................... 1-12

NDMR01.03.10 NetDispatch Messenger (NDM)04/25/2011 68P81001Y98-I 1

Chapter 2NDM Hardware / Software Installation

Overview ............................................................................. 2-1NDM Hardware Installation ................................................. 2-1ASP Node Hardware ........................................................... 2-2PTx AS Hardware ............................................................... 2-3NDM Software Installation .................................................. 2-4

Chapter 3NDM Components Connectivity

Overview ....................................................................................... 3-1

Networking Requirements ............................................................ 3-2ASP ..................................................................................... 3-2PTx AS ................................................................................ 3-2DM Client ............................................................................ 3-2IP Network Connectivity ...................................................... 3-3NDM Domain Name ............................................................ 3-5Public IP Address ................................................................ 3-5Internal (Intern-Nodal) IP Addresses .................................. 3-6Providers IP Address (NDM Element Manager IP Address) 3-6 Installation of the ASP ........................................................ 3-6NDM IP Addresses ............................................................. 3-6

Chapter 4NDM Configuration

Overview ....................................................................................... 4-1

Configuration and Setup ............................................................... 4-2Overview ............................................................................. 4-2NDM Configuration. ............................................................ 4-2Initial Installation Process ................................................... 4-4

ASP Element Manager ................................................................. 4-5Overview ............................................................................. 4-5ASP Element Manager Requirements ................................ 4-5Connecting to the ASP Element Manager .......................... 4-5Logging in to the ASP Element Manager ............................ 4-6Changing the EM Password ............................................... 4-8Updating the DM Client Version .......................................... 4-9Logging Out of the ASP Element Manager ......................... 4-9

ASP System Configuration ......................................................... 4-10Overview ........................................................................... 4-10

NetDispatch Messenger (NDM) NDMR01.03.10

2 68P81001Y98-I 04/25/2011

NDAP Connection Configuration Table ............................ 4-10APD Configuration ............................................................ 4-12TCP/IP Configuration ........................................................ 4-12Operator Changeable Parameters Table .......................... 4-14PTx AS Configuration ....................................................... 4-15IP Addressing for PTx AS ................................................. 4-15System Status from Element Manager ............................. 4-16Registration Status ............................................................ 4-16Registration Status Query ................................................. 4-17Reg Status Query Result .................................................. 4-18

Chapter 5Provisioning

Overview ....................................................................................... 5-1NDM Provisioning Web Interface (PWI) .............................. 5-2

User Management ........................................................................ 5-3Add User ............................................................................. 5-3Search User ........................................................................ 5-4Search User Results ........................................................... 5-5Edit User ............................................................................. 5-6Bulk Provisioning ................................................................ 5-7Change Operator Password ............................................... 5-8Add BU Admin Account ...................................................... 5-9Business Unit Admin Account Management Screen ........ 5-10Edit BU Admin Account ..................................................... 5-11Modify BU Admin Account ................................................ 5-11Delete BU Admin Account ................................................ 5-12Search BU Administrator .................................................. 5-13UDGC Agents Provisioning ............................................... 5-14UDGC Agents Management ............................................. 5-15Notifying E-Mail configuration ........................................... 5-16Retrieve NDM Subscriber by Key ..................................... 5-17Retrieve Multiple NDM Subscribers .................................. 5-18Retrieve Business Unit Administrator ............................... 5-19Retrieve Multiple Business Unit Administrators ................ 5-20Registration Status ............................................................ 5-21Reg Status Results ........................................................... 5-22About IPP .......................................................................... 5-22NDM BU Admin Web Interface (BU Admin) ...................... 5-23BU Admin Login ................................................................ 5-24BU Admin Welcome Screen ............................................. 5-25BU Admin User Management Screen ............................... 5-26


BU Admin User Information Screen .................................. 5-27BU Admin Change Password Screen ............................... 5-28BU Admin Logout Screen ................................................. 5-293P Applications Management Overview ........................... 5-31Access 3P Applications Management ............................... 5-323P Bulk Provisioning ......................................................... 5-333P Bulk Provisioning Limit Restriction .............................. 5-36Send 3P Email .................................................................. 5-37Notifying 3P Email Configuration ...................................... 5-39Delete 3P Application ........................................................ 5-40Delete 3P Application based on Company Name and Application Name ........................................................ 5-42Search 3P Dispatch Client ................................................ 5-43Retrieve 3P Application By Key Client .............................. 5-45Retrieve Multiple 3P Application ....................................... 5-46Retrieve 3P Dispatch Client .............................................. 5-48Retrieve Multiple 3P Dispatch Clients ............................... 5-50

Chapter 6DM Installation Overview

Introduction ................................................................................... 6-1Download ............................................................................ 6-1Application Installation ........................................................ 6-1Upgrade .............................................................................. 6-2

Chapter 7Billing

Billing Files ................................................................................... 7-1Overview ............................................................................. 7-1Billing File Maintenance ...................................................... 7-1Billing File Location ............................................................. 7-2Billing File Organization ...................................................... 7-2Billing File Retention ........................................................... 7-3Viewing Billing Files ............................................................ 7-3Downloading Billing Files .................................................... 7-3Billing File Structure ............................................................ 7-3Billing Filename Format ...................................................... 7-4Billing Header Record ......................................................... 7-5Billing Call Detail Records ................................................... 7-6Billing Trailer Records ....................................................... 7-12


4 68P81001Y98-I 04/25/2011

Chapter 8Statistics

Statistics, Log, & Config Files ....................................................... 8-1Organization of Statistics Files ............................................ 8-1Statistics File Maintenance ................................................. 8-2Viewing Statistics Files ....................................................... 8-2Downloading Statistics ........................................................ 8-3Statistics Description ........................................................... 8-4

Chapter 9Alarms and Events

Viewing Alarms & Events .................................................... 9-1Alarms Description .............................................................. 9-3

Chapter 10Troubleshooting & Maintenance

Troubleshooting .......................................................................... 10-1Before Calling... ................................................................ 10-1CNRC Telephone Numbers .............................................. 10-2Backing up the Configurable NDM Parameters ................ 10-2

AppendixA - Acronyms and Computer Software CopyrightB - RR Cause Values


N O T E S . . .


6 68P81001Y98-I 04/25/2011

About This Manual

About This ManualThis chapter of the manual describes the manual in general terms. The major topics of the chapter include:• The intended content of the manual• How the manual is to be used• Who is to use the manual• Other reference material that supports information in this manual• Elements in the appearance of the manual and their meaning• General safety guidelines• The changes to the manual over time• Who helped produce and validate information in the manual

Purpose The NetDispatch Messenger is accessed by PC Users using its client appli-cation, Dispatch MessengerTM. Dispatch Messenger connects the PC User to the ASP over an IP network. The IP network can be based on wire line Ethernet, Wireless LAN, or dial-up modem connections. This manual’s intent is to assist users when administrating this system.

NDMR01.03.10 NetDispatch Messenger (NDM)

04/25/2011 68P81001Y98-I ATM-1

About This Manual

Customer Network Resolution Center

Customer Network Resolution Center 0

Overview The Customer Network Resolution Center (CNRC) is a integral part of the network support process.

Before performing any major changes or optimization on the system, please contact the CNRC. Notify the CNRC with the nature of the change and the schedule for the change. This will allow CNRC to have the correct technical support engineers on call in case they are needed.

The CNRC can be contacted at the following telephone numbers:

Domestic1-800-499-6477

International Peru: 0-800-52-121Colombia: 01-800-700-1614Argentina: 0800-666-1559China: 10-800-130-0617Singapore: 800-1301-285Philippines: 1-800-1-116-0119Korea: 00-308-13-1358

All other International locations1-847-725-4555


ATM-2 68P81001Y98-I 04/25/2011

About This Manual

Related Manuals

Related Manuals 0

The following publications may be required to supplement the information contained in this manual:

Number Title

68P81001Y99 NDM Hardware manual

68P81131E90 Guide to Motorola Acronyms and Terms


04/25/2011 68P81001Y98-I ATM-3

About This Manual

Manuals On-line

Manuals On-line 0

Overview This manual is available on the World Wide Web at Mynetworksupport, the iDEN customer site. This site was created to provide secure access to critical iDEN Infrastructure information. This web site features a library of iDEN Infrastructure technical documentation such as bulletins, system release documents and product manuals.

The documents are located on the secured extranet website at the URL:http://mynetworksupport.motorola.com


ATM-4 68P81001Y98-I 04/25/2011

About This Manual

Reporting Manual Errors

Reporting Manual Errors 0

OverviewIf you locate an error or identify a deficiency in this document, please send an e-mail notice to [email protected] and identify the problems that were found.

Feedback from you, our user, will enable us to improve our documentation. Thank you for your time. We appreciate any comments from the users of our documents


04/25/2011 68P81001Y98-I ATM-5

mailto:

About This Manual

Conventions

Conventions 0

Software • submenu commands—Table > Table Designer

• new terms—mobile subscriber• keystrokes—Ctrl+Alt+Delete, Return

• mouse clicks—click, double-click• user input—Type delete

• screen output—iHLR is starting....

Hardware • CD-ROM

Safety This manual contains safety notices (alerts). Alerts are based on the standards that apply to graphics on Motorola equipment. Specific procedural notices are stated in the procedures as required and have specific visual representations. The representations are:

DANGER!INDICATES AN IMMINENTLY HAZARDOUS SITUATION WHICH, IF NOT AVOIDED, WILL RESULT IN DEATH OR SERIOUS INJURY.

WARNING!Indicates a potentially hazardous situation which, if not avoided, could result in death or serious injury.

CAUTION!Indicates a potentially hazardous situation which, if not avoided, could result in minor or moderate injury.

CAUTIONWithout the alert symbol indicates a potentially hazardous situation which, if not avoided, may result in property damage.

Important Indicates an item of the essence of a topic that is indispensable. Note Indicates something of notable worth or consequence.


ATM-6 68P81001Y98-I 04/25/2011

About This Manual

Product Specific Safety Notices

Product Specific Safety Notices 0

The specific procedural safety precautions are stated in the procedures and are also listed here.Note No specific procedural safety precautions to report at this time.


04/25/2011 68P81001Y98-I ATM-7

About This Manual

General Safety

General Safety 0

Important Remember Safety depends on you!! General safety precautions must be observed during all phases of operation, service, and repair of the equipment described in this manual. Failure to comply with these precautions or with specific warnings elsewhere in this manual violates safety standards of design, manufacture, and intended use of the equipment.

You must heed the safety precautions and warnings listed in the product manuals for your equipment. Any individual using or maintaining the product(s), should follow these warnings and all other safety precautions necessary for the safe operation of the equipment in your operating environment. Motorola Solutions, Inc. assumes no liability for failure to comply with these requirements.

Keep Away From Live Circuits

DANGER!HAZARDOUS VOLTAGE, CURRENT, AND ENERGY LEVELS ARE PRESENT IN THIS PRODUCT. POWER SWITCH TERMINALS CAN HAVE HAZARDOUS VOLTAGES PRESENT EVEN WHEN THE POWER SWITCH IS OFF. DO NOT OPERATE THE SYSTEM WITH THE COVER REMOVED. ALWAYS REPLACE THE COVER BEFORE TURNING ON THE SYSTEM.

Operating personnel must:• Not remove equipment covers. Only Factory Authorized Service Personnel

or other qualified maintenance personnel may remove equipment covers for internal subassembly, or component replacement, or any internal adjustment.

• Not replace components with power cable connected. Under certain conditions, dangerous voltages may exist even with the power cable removed.

• Always disconnect power and discharge circuits before touching them.


ATM-8 68P81001Y98-I 04/25/2011

About This Manual

General Safety

Ground the Equipment

To minimize shock hazard, the equipment chassis and enclosure must be connected to an electrical earth ground. The power cable must be either plugged into an approved three-contact electrical outlet or used with a three-contact to two-contact adapter. The three-contact to two-contact adapter must have the grounding wire (green) firmly connected to an electrical ground (safety ground) at the power outlet. The power jack and mating plug of the power cable must meet International Electrotechnical Commission (IEC) safety standards.

Electro-Static Discharge

Motorola strongly recommends that you use an anti-static wrist strap and a conductive foam pad when installing or upgrading the system. Electronic components, such as disk drives, computer boards, and memory modules, can be extremely sensitive to Electro-Static Discharge (ESD). After removing the component from the system or its protective wrapper, place the component flat on a grounded, static-free surface, and in the case of a board, component-side up. Do not slide the component over any surface.

If an ESD station is not available, always wear an anti-static wrist strap that is attached to an unpainted metal part of the system chassis. This will greatly reduce the potential for ESD damage.

Do Not Operate In An Explosive Atmosphere

Do not operate the equipment in the presence of flammable gases or fumes. Operation of any electrical equipment in such an environment constitutes a definite safety hazard.

Do Not Service Or Adjust Alone

Do not attempt internal service or adjustment, unless another person, capable of rendering first aid and resuscitation, is present.

Use Caution When Handling a Cathode-Ray Tube

Breakage of the Cathode-Ray Tube (CRT) causes a high-velocity scattering of glass fragments (implosion). To prevent CRT implosion, avoid rough handling or jarring of the equipment. The CRT should be handled only by qualified maintenance personnel, using approved safety mask and gloves.

Do Not Substitute Parts Or Modify Equipment

Because of the danger of introducing additional hazards, do not install substitute parts or perform any unauthorized modification of equipment. Contact Motorola Warranty and Repair for service and repair to ensure that safety features are maintained.


04/25/2011 68P81001Y98-I ATM-9

About This Manual

Revision History

Revision History 0

Date Issue Description of Changes

03/10/05 -O General Release.

01/31/06 -A Updates for NDM R01.1 Release

05/30/06 -B Update for NDM R01.1 Patch Release

07/20/06 -C Update for NDM R01.1 Billing Record descriptions

10/05/06 -D Updates for NDM R01.2 Release

11/22/06 -E Updates for NDM R01.2 Patch Release

02/01/07 -F Final updates for NDM R01.2.8 Release

09/12/07 -G Final updates for NDM R01.3 Release

04/28/2010 -H Updates for Firewall Friendly NDM feature

04/25/2011 -I Further updates for the Firewall Friendly feature. NDMR01.03.10 Release.


ATM-10 68P81001Y98-I 04/25/2011

Chapter 1

NetDispatch Messenger Overview

High-Level Architecture 1

Overview This section gives a brief overview of the iDEN (Integrated Digital Enhanced Network) and how NetDispatch Messenger (NDM) is integrated into the iDEN. NDM is intended to provide a cost-effective, commercial IP-solution offering i.e. Net Dispatch Services to iDEN customer. Net Dispatch services imply legacy Dispatch Services and added messaging capabilities between IP Clients and legacy subscriber units.

Purpose of NDM This solution is intended to offer services to the following users:• Located in areas of poor or no RF coverage.• Work in fixed locations, and require access to Dispatch Services.• Work in areas where handsets are prohibited.• Are interested in legacy asset reuse.• Travel and require Dispatch Communications with users in the home

network.


04/25/2011 68P81001Y98-I 1-1


High-Level Architecture

NDM Product Description

The NDM provides the Legacy Dispatch Services and the Extended Dispatch Services.• Private Call• Group Call• Call Alert• Emergency Group Call• User Defined Group Call• Dispatch Voice Mail• PTT ID• Failure Notification and Indication in Legacy Calls.• Dispatch Voice Notification

Note: Services listed above depends on the carrier network configuration and policies. Some carriers may not offer one or more services to end users such as User Defined Group Call or Emergency Group Call.

Figure 1-1 NDM System High Level Architecture


1-2 68P81001Y98-I 04/25/2011


Dispatch MessengerThe hardware platform for NetDispatch Messenger consists of two (2) server types, quantity two (2) each for a total of 4 servers. The first server type is the Advanced Services Platform (ASP). The ASP in NetDispatch Messenger system terminates the iDEN connectivity and handles NDM call processing. It appears to the iDEN MSO as a pseudo EBTS. Each ASP has minimum 1 pseudo EBTS sites and each NDM has exactly two (2)ASP Nodes.

The second server type is a Push to Talk Application Server (PTxAS). The PTxAS servers are responsible for deploying the NDM Dispatch Messenger application (including user authentication and user web interfaces), distrib-uting the service configuration parameters after successful client authenti-cation, and support for the Business Unit Administrator web interface. Each NDM system has exactly two (2) PTxAS Nodes.

The NetDispatch Messenger should be implemented using a MSO-Centric configuration. In the MSO-Centric configuration, the ASP and PTxAS servers are located at the Mobile Switching Office (MSO). The NDM Servers will communicate to Dispatch MessengerTM Users (DM Users) over an IP network, and to the iDEN telecommunications network over a T1/E1 interface. In this configuration, a firewall is recommended for network security. VPN tunnels are also recommended between DM user network(s) and ASP MSO network for maximum security.

Note Dispatch MessengerTM Users (DM Users) refer to users who interface to the NetDispatch Messenger from their Personal Computer (PC), i.e. PC Users, and Mobile users refer to those who interface to the system via their mobile subscriber unit.

Dispatch Messenger 1

Overview NetDispatch Messenger is accessed by PC Users using its client application, Dispatch MessengerTM. Dispatch Messenger connects the PC User to the ASP over an IP network. The IP network can be based on wire line Ethernet, Wireless LAN, or dial-up modem connections. Note that the Dispatch Messenger user’s IP network must be routable (connected) to the NDM server IP network for dispatch services to be possible.

PC Requirements Dispatch MessengerTM runs on the user’s Personal Computer (PC). Dispatch MessengerTM application can be installed on any desktop or laptop Personal Computer (PC) with the following characteristics: • Pentium III, 500 MHz or greater• 128 MB RAM, or greater


04/25/2011 68P81001Y98-I 1-3


Dispatch Messenger• Full duplex sound card• Integrated or external microphone or headset microphone• Integrated or external speakers or headset speakers• Operating System: Microsoft Windows XP or Windows Vista• IP Network Access --Connection to LAN or WAN• At least a 56K modem (for dial-up networking only)

Downloading Dispatch Messenger

Downloading the Dispatch MessengerTM Application

The Dispatch MessengerTM application is downloaded by clicking on the "Download" button on the Dispatch MessengerTM Home Page. The format of the URL for the Dispatch MessengerTM Home Page is

https://<PTx_IP>/

where <PTx_IP> is PTx AS public IP address.

Before downloading the Dispatch MessengerTM application, the PC User must be provisioned for Dispatch MessengerTM services. See Chapter 4, Provisioning DM Users for more information on provisioning users for Dispatch MessengerTM.

Once the Dispatch MessengerTM is downloaded, follow the installation instructions provided by clicking on the "Instructions" link on the Dispatch MessengerTM Homepage.


1-4 68P81001Y98-I 04/25/2011


Dispatch Messenger

Dispatch Messenger Homepage

The Dispatch MessengerTM Homepage also contains the following buttons:• Online Help• Download• Change Password

Click on the "Online Help" button to download/open a .pdf file of the Dispatch MessengerTM User’s Manual.

Click on the "Download" Button to download the Dispatch MessengerTM application onto your PC.

Click on "Change Password" to change a user password through the NDM web interface directly.

Basic Operation Once logged in via the client application, a Dispatch MessengerTM appli-cation window pops-up and displays the user’s iDEN Dispatch Information and an empty Phonebook. A "green PC" indicator next to any phonebook entry means that the PC User is active or logged in to Dispatch MessengerTM. A "Red PC" indicator refers to an inactive or PC User that is logged out of Dispatch MessengerTM. A "blue/grey" phone indicator represents a mobile subscriber. Mobile subscribers do not have active or inactive status indicators.

Dispatch Calls initiated by PC Users will be processes in the same manner as calls initiated by mobile subscribers. The PC User selects the Private or Group Name/ID form the Dispatch MessengerTM window, presses and holds the “TALK” button icon, and speaks into the microphone. Call setup information is sent over the PC User’s IP network, or dial-up connection, to the ASP, and is forwarded to the DAP on the iDEN MSO, where it is processed.

Calls initiated by PC Users, via the ASP, are transparent to the iDEN Telecommunications System. These calls are processed as if they were initiated via an EBTS.

User Features Dispatch MessengerTM provides a variety of legacy and extended Dispatch services to PC Users and mobile subscribers. These services include: • Private Dispatch Call• Call Alert• Group Dispatch Call • User Defined Group Call • Instant Message Text to Speech Dispatch Voice• Dispatch Voicemail


04/25/2011 68P81001Y98-I 1-5


Dispatch Messenger• Presence and Availability• Dispatch Voice Notification• Emergency Group Call

PC Users and mobile subscribers can initiate and receive Private Dispatch Calls, Call Alerts, and Group Dispatch Calls with one another. This includes PC User to PC User, PC User to mobile subscriber, and mobile subscriber to PC User.

User Defined Group Calls can only be initiated by PC Users, but can be joined in by other PC Users and mobile subscribers. Mobile subscribers cannot initiate User Defined Group Calls since this service requires the use of the Dispatch MessengerTM and a PC.

Instant Message Text to Speech Dispatch Voice can only be initiated by PC Users but received by other PC Users and mobile subscribers. Mobile subscribers cannot initiate Instant Message Dispatch Voice since this service requires the use of the Dispatch MessengerTM and a PC.

Only PC Users have Dispatch Voicemail. Mobile subscribers and PC Users can leave a message with the PC User’s Dispatch Voicemail.

Presence and Availability is only available for PC Users. This is not a feature that can be utilized by mobile subscribers because this service requires the use of the Dispatch MessengerTM and a PC.

Emergency Group Call may be initiated and received by DM users if the NDM system, carrier network, and user provisioning are configured to support this call type

Private Dispatch Call

Private Dispatch Call allow PC Users to initiate “one-to-one” Dispatch calls to other PC Users and mobile subscribers registered on the iDEN. The PC User selects the target party from the Dispatch MessengerTM address book, and double clicks on the icon. A window will appear for the target user. To initiate the Dispatch call, the PC User clicks on the “TALK” button and then speaks into the PC microphone. Responses received from the target user will be heard through the PC speakers.

Mobile subscriber can also initiate Private Dispatch Calls with PC Users by selecting the private ID of the PC User and pressing the Push-To-Talk (PTT) button.


1-6 68P81001Y98-I 04/25/2011


Dispatch MessengerCall Alert

The Call Alert feature allows PC Users to “alert” or notify other PC Users and mobile subscribers registered on the iDEN. When an alert is sent, the target PC User will receive a notification in the form of a call window and audible tones.

To send a Call Alert, the PC User double-clicks on the icon of the target user from the Dispatch MessengerTM window. A Private Call Window appears for that target user. To send an alert, the PC User then selects "Send Alert" from the Private Call Window Actions Menu or clicks on the "Send Call Alert" button.

Upon receiving a Call Alert, a Call Alert window is displayed with the caller’s member ID with an audible tone. The Call Alert window will remain displayed as a visual indication for the call, but the audible tone does not last as it does on a handset. Call Alerts are cleared by responding to the sender (clicking on the "TALK" button in the Call Alert window), or by clicking on the "X" button in the upper right hand corner of the Call Alert window.

Call Alerts are stacked if the user receives more than one Call Alert. The Call Alerts windows are stacked one on top of the other on the PC desktop, such that the most recent Call Alert window is on the top of the stack and the least recent is on the bottom of the stack. Therefore, if a user has a stack of Call Alerts, the most recent Call Alert window is displayed on the users PC desktop. Once the most recent Call Alert window is closed, the next most recent Call Alert window is displayed. The user can also view multiple Call Alert windows by clicking and dragging the windows anywhere on the PC desktop.

Mobile subscriber can also initiate Call Alerts with PC Users by selecting the private ID of the PC User, selecting "Alert" from the handset’s menu and pressing on the PTT button. Mobile subscriber hear only an audible tone on the handset upon receipt of a Call Alert.

Group Dispatch Call

Group Dispatch Call allows the PC User to communicate with a pre-defined group of PC Users and/or mobile subscribers that have been provisioned for NetDispatch Messenger services and are currently registered on the iDEN. To initiate a Group Dispatch Call with a pre-defined talk group, the PC User simply selects the target talk group from the Dispatch MessengerTM address book, and double-clicks on the icon. A window will appear for the target Group ID. To initiate or join in on a Group Dispatch Call, the PC User clicks on the “TALK” button and speaks into the microphone. Responses from group members will be heard through the PC speakers.


04/25/2011 68P81001Y98-I 1-7


Dispatch MessengerMobile subscribers can also initiate group calls with PC Users by selecting the group call ID and pressing the PTT button.

User Defined Group Call (UDGC)

User Defined Group Call provides PC Users with instant dispatch conference capabilities. PC Users can dynamically create a UDGC consisting of other PC Users and/or mobile subscribers registered on the iDEN. UDGC can only be originated by PC Users. Mobile subscribers cannot originate a UDGC. To initiate a UDGC, the PC User selects the target users from the Dispatch MessengerTM address book, and then “drags” the target users into an existing or newly defined talk group. Users added to a UDGC will immediately become active members on the dispatch conference call, and can participate in the call.

DM Users can also be removed from a UDGC. To remove a user from an active talk group, the PC User selects and ‘drags” the user from the talk group from the group call window to the Dispatch MessengerTM address book. The change will take effect immediately and the user will be dropped from the active group call.

UDGC will remain active until the PC User, that originated the call, disables the group or closes the UDGC window. The PC User that originates the call cannot leave the call without terminating it. In addition, the ASP supports a TTL timer for every activated UDGC on the system. An inactive UDGC is an activated UDGC, in which there is no talk activity for TTL period. The default TTL period is 2 minutes. Every two minutes, the TTL timer expires and the call state is checked. If the call is inactive when the TTL timer expires, the UDGC call is terminated and the call resources released. This means the actual billed call length of a UDGC call can vary by up to 120 seconds (Example: A 118 second UDGC call will be billed for 120 seconds (118 seconds talk time/hang timer, 2 seconds idle whereas a 122 second UDGC call will be billed for 240 seconds (122 seconds talk time/hang timer, 118 seconds idle).Note The PC User that originates the group call cannot leave the call without

terminating it. The only way the originator can leave the call is by terminating the call. This is accomplished by closing the UDGC window.

UDGC calls are actually Private Calls initiated by the NDM system’s UDGC Agent IMEIs. UDGC agent IMEIs are provisioned at system installation time by the carrier. Each UDGC participant consumes one UDGC agent IMEI from the pool. Once the UDGC is ended, the agent IMEIs are released back to the pool for use by other calls.


1-8 68P81001Y98-I 04/25/2011


Dispatch MessengerThe maximum number of users allowed on a UDGC is set on a per user basis when provisioned. The maximum number of simultaneous UDGC sessions is limited by the number of UDGC agents available (currently 500 max) and/or the maximum number of calls on a given ASP server. Once the maximum is reached, the Dispatch MessengerTM will not allow a PC User to create a new UDGC session or add an additional user to a group.

Instant Message Text to Speech Dispatch Voice

The Instant Message Dispatch Voice feature allows PC Users to send text-to-speech messages to other PC Users and/or mobile subscribers, registered on the iDEN. To send a text-to-speech message, a PC User selects a target from the Dispatch MessengerTM address book, and double clicks on the icon, or selects the “Make Private Call” option from the “Actions” menu, and manually enters the target users ID. A window will appear with a “TALK” button icon. From this window, the PC User selects the “Send Text as Speech” option from the “Actions” menu. Another window appears, and overlays the existing Private Call window. The PC User then enters the text message in the overlaying window and clicks the “send” icon after completing the text message entry. A text-to-speech conversion is performed by the Dispatch MessengerTM application local on the PC User’s PC. The target user then hears a computerized voice conveying the text message.

Dispatch Voicemail

The Dispatch Voicemail feature allows PC Users to receive voice mails for Private Dispatch calls, and retrieve them at a later time. Voice mails and can be retrieved at a later time via the "Recent call logs list", which accessible via the "Actions" menu in the main Dispatch MessengerTM window. An external voice mail system is not required.

As with traditional voice mail systems, PC Users will have the capability of recording a personalized greeting for their voice mail. To record a person-alized greeting, the PC User selects the "Set Greeting" option from the "Actions" menu in the main Dispatch MessengerTM window, and records his or her voice.

Unlike traditional telephone voicemail systems, Dispatch Voicemail gives each PC User the flexibility of manually enabling/activating or disabling/de-activating voicemail. To activate or deactivate Dispatch Voicemail, the PC User selects the "Toggle Auto Answer" option from the "Actions" menu in the main Dispatch MessengerTM window.

If a user activates/enables Dispatch Voicemail, all Private Dispatch calls made to that user will automatically receive the prerecorded greeting. After the greeting has finished playing, the caller has up to six (6) seconds to leave a voice message. Callers can be other PC Users or mobile subscribers.


04/25/2011 68P81001Y98-I 1-9


Dispatch MessengerAll voicemail messages are saved locally on the PC User’s PC hard drive. The default directory for voicemail files is C\:Program Files\Motorola\DM. The voicemail files will be stored in the same directory as the Dispatch Messenger executable. During DM installation, the PC User specifies where he/she wants to save the DM executable. This is the directory where the voice mails will be stored. The default directory for the DM executable is C\:Program Files\Motorola\DM.

There is no limit on the number and length of voicemail messages stored. Voicemail message are saved as wave files. The number and size of voicemail files that can be stored is based on the size of the user’s PC hard drive. Voicemail files will remain on the user’s PC hard drive until they are manually deleted.

Presence and Availability

NetDispatch Messenger provides real-time Presence and Availability infor-mation to all PC Users. The ASP is capable of detecting if PC Users are online (logged in) or offline (logged out).

The Presence and Availability information is provided to PC Users through the use of color-coded icons, located to the left of a member’s ID, in the main Dispatch MessengerTM window. If the icon is "green", the PC User is online or logged in. If the icon is "red", the PC User is offline.

Presence and Availability information is not available to mobile subscribers. Mobile subscribers have a “blue” icon located next to their ID in the main Dispatch MessengerTM window, regardless if the unit is actively registered on the iDEN, or not.

Dispatch Voice Notes (DVN)

The Dispatch Voice Notes feature allows PC Users to send pre-recorded audio messages to other PC Users and/or mobile subscribers, registered on the iDEN. To send a Dispatch Voice Notes message, a PC User selects a target from the Dispatch MessengerTM address book, and double clicks on the icon, or selects the “Make Private Call” option from the “Actions” menu, and manually enters the target users ID. A window will appear with a “TALK” button icon. From this window, the PC User selects the “Send Dispatch Voice Note” option from the “Actions” menu. Another window appears, and overlays the existing Private Call window. The PC User then uses this menu and interface to record and playback a pre-recorded audio message. Once the message is verified, the user then clicks the “send” icon to send the audio message via PTT to the target user. The target user then hears the pre-recorded audio message.


1-10 68P81001Y98-I 04/25/2011


Dispatch MessengerEmergency Group Call (EGC)

Emergency Group Dispatch Call allows the PC User to communicate with a pre-defined group of PC Users and/or mobile subscribers that have been provisioned for NetDispatch Messenger services and are currently registered on the iDEN. This feature is similar to the Group Dispatch Call feature, but incorporates some call priority aspects as well as emergency tones to alert other participants to the high call priority. To initiate an Emergency Group Dispatch Call with a pre-defined talk group, the PC User simply presses the small Emergency Group Call icon on the DM client main window (a small red and white cross). A window will appear for the target Group ID with flashing background and emergency tones. To send audio using the Emergency Group Dispatch Call, the PC User clicks on the “TALK” button and speaks into the microphone. Responses from group members will be heard through the PC speakers.

Business Unit Description

The NDM system allows the iDEN operator to group Dispatch Messenger users into Business Units. The maximum number of Dispatch Messenger users that can be allocated to a single business unit is by default set to 1,000.

Each Business Unit may optionally have a Business Unit Manager (also known as BU Admin) assigned to manage users assigned to that Business Unit. BU Admin will access the ASP Data store from a public IP thru the PTx AS. BU Admin is provided with an account with its own business unit ID/password/e-mail address. BU Admin is allowed minimal privileges such as assigning users to provisioned records on the system.

BU Admin accounts are provisioned by the provisioning operator by creating user account on ASP. NDM supports a maximum of 5,000 BU Admin accounts on a single NDM system. There is no limit, however, on the number of business units that can be assigned to Dispatch Messenger users.


04/25/2011 68P81001Y98-I 1-11


Dispatch Messenger

Auto e-Mail Notification

The provisioning sub-system will send an e-mail to the DM Client user and BU Admin, for every user of that type when provisioned on the ASP. The e-mail contains the https:// URL required to connect to the PTx AS servers. The e-mail is automatically generated when the key fields are changed in the ASP Datastore using the ASP provisioning interface or the BU Admin provi-sioning interface. (i.e, password and username)

The e-mail contains the following information• username• password• BU ID• PTxAS URL (for accessing the PTx AS servers via., web-browser)• Customer Support Phone Number (defined by the carrier)

From the auto-E-mail, users will be able to access the PTxAS web pages to download and install the DM client software. All the users will sign in to the DM Client with username, password and BU ID to access the DM services.


1-12 68P81001Y98-I 04/25/2011

Chapter 2

NDM Hardware / Software Installation

Overview This section gives a brief overview of the iDEN System and how NetDispatch Messenger is integrated into the iDEN System. The NetDispatch Messenger 1.2 Release supports iDEN System Releases 9.5 thru 14.0.

NDM Hardware Installation

The purpose of this section is to describe the hardware platform and the associated components used in the NDM consists of 2 ASP Nodes, 2 stand-alone PTx AS, one or more DM clients

The Sun TS 230 server makes up all 4 NDM server components (2 for ASP, 2 for PTxAS) and contains a Dual AMD Opteron server board. The following components are included with the TS230: • 2RU rack mount system chassis • Front access bays for storage peripherals include:

• One 5.25” half high bay. • One 5.25” slim-height bay. • One 3.5” bay. • Six SCSI hot-swap, six SATA hot swap or six IDE cold-swap hard drive

trays.• Power supply options: one fixed –48V, 400W, DC/DC, one fixed 460W

AC/DC, or two hot-swappable 460W, AC/DC redundant. • One AMD* Opteron* server motherboard. • One 64/32-bit riser card to enable the use of up to three full-height PCI

boards (three full-length). • One removable fan bracket consisting of two 80mm and one dual 40mm

fans for system cooling. • One internal USB cable connected to the front panel board. • One SCSI data cable connected to the motherboard (for version with SCSI).


04/25/2011 68P81001Y98-I 2-1


• Rack mount slide rails with hardware.

ASP Node Hardware Each ASP Node will be running on SUN TS 230 server and runs the Red Hat Enterprise Linux Operating System. There will be 2 ASP nodes in every NDM System.

The SUN TS230 box will have following specifications:

Dual 2.4 Ghz AMD 64-bit Opteron Processors.

2 U Height

2 GB Memory

4 PCI Slots

146 GB Ultra SCSI Disk Drive

OS: Red Hat Enterprise Linux ES Version 3

T1/E1 Card: Interphase 5539F Quad port T1/E1 Board.

Ethernet Board: Intel Quad Ethernet PCI Board.

Accelerator Board: Cavium CN1230-350-NPB-DDR

ASP is rack mounted. T1/E1 connectivity to iDEN Network via the PCI Card in each ASP Node. A PCI Card can support up to 4 T1/E1 ports.


2-2 68P81001Y98-I 04/25/2011


PTx AS Hardware NDM Consists of 2 PTxAS Application Servers. Two Application Servers are provided for redundancy purpose. The application server will be running on SUN TS 230 Hardware.

Dual 2.4 Ghz AMD opteron Processors

2 U Height

2 GB Memory

4 PCI Slots

146 GB Ultra SCSI Disk Drive

OS: Windows Server 2003 Standard Edition

Figure 2-1 NDM Hardware Installation


04/25/2011 68P81001Y98-I 2-3


NDM Software Installation

This section explains the software components in the platform that provide the platform services in the NDM System.

Software upgrade capability is provided for both new installations and upgraded SW versions. The source for upgrade objects in either case is a DVD ROM disk as opposed to the OMC.

Please consult the NDM MOP (Method of Procedures) Manual for detailed information on NDM installation procedures.


2-4 68P81001Y98-I 04/25/2011

Chapter 3

NDM Components Connectivity

Overview 3

This chapter provides an overview of the components of the NDM and connectivity between the components. NDM for iDEN is comprised of 2 ASP Nodes one or more DM clients, and 2 PTx Application Servers. The connec-tivity of NDM with iDEN system, NDM with Dispatch Messenger are described within.


04/25/2011 68P81001Y98-I 3-1


Networking Requirements

Networking Requirements 3

ASP The ASP (Advanced Services Platform) provides gateway services for an IP Client and accesses all legacy Dispatch and messaging services on the iDEN Network. The ASP servers are typically located in the iDEN MSO.

PTx AS The PTxAS (Push to Talk Application Server) provides the authentication for the DM Application Users. It provides Non-Dispatch Services like download of DM Client., Phonebook, configuration of NDM, Text to Speech Service and provides the BU Admin and DM User Web Interfaces. PTxAS servers must be co-located with the ASP servers and are typically located at the iDEN MSO.

DM Client The Dispatch Messenger is the Windows software application that enables Dispatch Services and messaging capabilities to IP Users. The software is resident on a user’s Personal Computer (PC)

A DM User could be on a public network and behind a firewall as well as behind a NAT. Enterprise network users should consult their Enterprise IT support team prior to installing Dispatch Messenger client software to ensure their enterprise has the necessary firewall configuration changes to support dispatch calls.


3-2 68P81001Y98-I 04/25/2011



Figure 3-1 Network Connections with DM Clients and ASP

As shown in the diagram above, the ASP is accessible by any PC (Personal Computer) User over the Operator’s LAN/WAN IP network. This means that PC Users connected to the Operator’s LAN/WAN IP network can use Dispatch Messenger to communicate with other PC Users connected on the Operator’s LAN/WAN IP and mobile subscribers who are active on the iDEN System.

The ASP and PTxAS servers may also accessible by PC Users over the Public IP network. This means that remote PC Users (outside of the Operator’s IP network) can use Dispatch Messenger to communicate with other remote, internal PC Users, and/or mobile subscribers active on the iDEN System.

Important Motorola strongly recommends the use of a Firewall/NAT for security purposes. DM Clients are also recommended to be behind a Firewall and connected to the MSO NDM system IP network via VPN tunnels for maximum security.

IP Network Connectivity

NDM consists of components like ASP, PTx AS and DM. All the components interface with one another with different category of networks.

The ASP will participate in 3 networks in the course of normal operator:• A public IP Network (For DM Clients) - this is referred to at the E0

interface for the ASP• A Provider’s Internal Network.(For access of Element Manager - based OA

& M functionality) - this is referred to as the E1 interface for the ASP


04/25/2011 68P81001Y98-I 3-3


Networking Requirements• An inter-nodal Network - this is referred to as the E2 interface for the ASP

The PTx AS will participate in 3 networks in the course of normal operation.• A public IP Network (Internet, DM Client users and DM Client

Applications) - this is referred to as the E0 interface for the PTxAS server• A Providers Internal Network. (for access of Element Manager - based OA

& M functionality) - this is referred to as the E1 interface for the PTxAS server

• An Inter-nodal Network - this is referred to as the E2 interface for the PTxAS server


3-4 68P81001Y98-I 04/25/2011



Figure 3-2 IP Address Scheme of NDM

NDM Domain Name NDM System will have an associated Domain Name (DNS entry). DM Client users will use this single Domain Name when attempting to download the DM Client Executable. DNS will resolve the domain name to public IP Addresses of the BOTH of the PTx AS boxes (i.e. DNS resolution will return two IP addresses)

Public IP Address PTx AS provides a public IP Address which will be used by all DM Users when connecting to PTx AS.

ASP provides one public IP Addresses per ASP Node for use by all DM users.

DM clients will be aware of IP Addresses of both the ASP Nodes automati-cally after PTxAS sign in is completed.


04/25/2011 68P81001Y98-I 3-5



Internal (Intern-Nodal) IP Addresses

A Inter-nodal network is created between the 2 ASP nodes for inter-nodal communication, IP Multicasting and Database Synchronization. Note that this network must be private (no other equipment on this subnet) and have NO port or firewall restrictions, as this may interfere with some ASP and PTxAS inter-nodal communications traffic.

The Dispatch Messenger Presence feature is supported in the NDM archi-tecture using IP Multicasting in this Inter-nodal network.

Providers IP Address (NDM Element Manager IP Address)

Provider’s Internal Network is used by the NDM Element Manager for web-based OA & M operations and NDM Provisioning.

Debugging related services like Telnet, Secure Shell are intended for this network.

Both ASP and PTx AS will have IP Address on the providers network. These addresses are used for NE Management by the ASP EM

Installation of the ASP Motorola installs the ASP at the Operator’s site. The ASP is configured by Motorola to connect to the Operator’s LAN/WAN IP network. Installation tasks performed by Motorola at the Operator’s site are:• IP Address / Network setup and configuration at MSO• Physical install of ASP and PTxAS Servers.• Application software Installation• IP configuration on the NDM Components• T1 Connectivity to the iDEN System• Subscriber provisioning and Test Calls

See the NDM MOP for Complete installation details

NDM IP Addresses IP addresses will be assigned to all ASP/PTX interfaces during installation of the NDM. The operator must provide Motorola with these IP addresses for the NDM Public network and EM network interfaces as part of the NDM prework. A static IP address must be used for all interfaces (DHCP is not supported)


3-6 68P81001Y98-I 04/25/2011

Chapter 4

NDM Configuration

Overview 4

This chapter provides an overview of configuring the ASP and the PTx AS on the operator’s site and other possible configuration sources. This chapter also provides overview of the ASP Element Manager and the configuration of the ASP using the ASP Element Manager.


04/25/2011 68P81001Y98-I 4-1

NDM Configuration

Configuration and Setup

Configuration and Setup 4

Overview Configuration for the ASP and PTx AS are performed and done via many sources. Most of the customer configurable NDM parameters used after installation (Install MOP completed) are changeable on the NDM Element Manager web interface. Configuration parameters not modifiable via the NDM Element Manager Interface should be checked/modified using instruc-tions in the latest version of the NDM MOP.

NDM Configuration. Configuration data for the ASP will come from 4 primary sources.• Initial Installation Process (IIP)• Element Manager (EM)• ACG Configuration Files (ACF)

The NDM ASP nodes will automatically request the OMC download image when the ASP is restarted. Once the download image is obtained on all configured T1/E1 lines, the ASP will automatically configure the ACG configuration parameters and restart the ASP application. Additional configu-ration of the ASP can be done via the Element Manager for select parameters

Table describes the parameters and the sources for parameters.

Table 4-1 Configuration Parameters

Configuration ParametersParameter Description

System Type This parameter tells whether the ASP is connecting to iDEN or Harmony. Configured using EM

ASP Supported iDEN Version

Sets the DAP Link Version Check protocol the ASP will use. Configured using EM

Back Haul Type

Whether the WAN Interface is E1 or T1. NDM R01.2 supports both T1 and E1 interface type. E1 configurations require some manual command line modifications at install time (see the NDM MOP). Also note in the NDM MOP the T1/E1 line settings required, as they are fixed in the ASP. Configured using EM

EBTS SR Version

Select either 13.4 (all iDEN SR up to 13.4) or 14.0 (iDEN SR14.0). This parameter determines how the ASP will parse the ACG configuration files upon download from the OMC. Configured using EM

DM Version The latest version of the DM Client supported by the ASP. Configured at installation time via command line only

Node ID This is the Node Id of each ASP Node. Configured at installation time via command line only


4-2 68P81001Y98-I 04/25/2011

NDM Configuration


These parameters are user configured. All other iDEN related parameters are set automatically by the acg.cf on download /parsing or set by Motorola personnel at installation time based on purchased system configuration.

Provider IP address Network Mask Default Gateway

This is the IP Interface that the operator uses to access the Element Manager services. Configured at installation time via command line only.

Public IP address Network Mask Default Gateway

This is the IP interface that will be accessed by DMs to receive services from ASP. Configured at installation time via command line only.

Inter Nodal IP address Network Mask Default Gateway

This is the IP Interface that will be used by ASP nodes to communicate with each other and perform database replication. Configured at install time via command line only

Mail Server IP Address/setting information

External SMTP mail server used to send E-mail. Configured using the ASP EM Provisioning interface.

NTP Server IP Address External NTP server to time synchronize the ASP and PTxAS servers correctly via the IP network

Customer Web Page Banner

.jpg banner added at install time to be displayed on all NDM PTxAS (end user) web interfaces. Details on banner specs and location in the NDM MOP. Configurable via PTxAS KVM

Customer Defined DM Client Logo

.bmp logo file added at install time to be displayed on all NDM DM client GUIs. Details on logo specs and location in the NDM MOP. Configurable via PTxAS KVM.

Netcool Server IP address (optional)

IP address of the Netcool server for NDM Alarms/traps. This is an optional feature, and is configured via MOP procedure by Motorola personnel at install/upgrade time

Configuration ParametersParameter Description


04/25/2011 68P81001Y98-I 4-3

NDM Configuration


Initial Installation Process

The operator is prompted with configuration parameters during the initial installation. The node will reset and automatically download and automati-cally configure the ACG configuration parameters. Once configuration is done it restarts the ASP Application.

Figure 4-1 Network Connections with DM Clients and ASP


4-4 68P81001Y98-I 04/25/2011

NDM Configuration

ASP Element Manager

ASP Element Manager 4

Overview Each ASP Node has its own instance of ASP -EM (Element Manager) that will provide Configuration, Fault and Performance Management of that node. ASP EM is located local to the ASP Node. ASP - EM Interface can be accessed thru a web-based URL identifying the web server running on any node.The alarm and statistics of other ASP Node in the same cluster can be viewed on logging in to the ASP EM The ASP Element Manager is installed on the ASP during installation. Note The E1 (Element Manager) interface should be used for all ASP EM

activities. Although the E0 and E2 interfaces may allow users to log in, some of the ASP EM functionality will not work on these interfaces

ASP Element Manager Requirements

The ASP Element Manager has the following requirements for the Machine. • Operating System: Microsoft Windows XP or Windows Vista• IP Network Access --Connection to E1 IP network LAN or WAN

• JavaTM capable web browser (JRE 1.5 or greater)

JRE 1.5 or greater is required to operate any buttons and view indicators located in the bottom window on the ASP Element Manager. Failure to use the appropriate JavaTM version will result in browsing malfunctions, in opera-bility of buttons and/or incorrect indicator values.

Connecting to the ASP Element Manager

The ASP Administrator connects to the ASP Element Manager over the E1 IP network. The ASP Element Manager can be accessed over the Operator’s E1 IP network or over the Public IP network. To connect to the ASP Element Manager, type the URL for the ASP in the address box of the Internet web browser and press the enter/return key. The format of the URL for the ASP Element Manager will be:

http://<ASP EM IP Address>

Where ASP IP Address is the ASP E1 IP address for your particular network. The browser configuration setting must be set properly for your particular network environment, and the ASP must be accessible from your network.


04/25/2011 68P81001Y98-I 4-5

NDM Configuration

ASP Element Manager

Logging in to the ASP Element Manager

After connecting to the ASP, the ASP Element Manager Users Login screen appears. Enter the default password for the EM User ID and the EM password to login to the ASP Element Manager.

Important The default EM User ID and password is set during installation. It is strongly recommended to change the EM password after logging in to the ASP Element Manager. See section on Changing the EM Password. The User ID is not changeable via the ASP Element Manager.

Figure 4-2 ASP Element Manager Users Login Screen

After logging into the ASP Element Manager, the ASP Element Manager Welcome Screen appears.


4-6 68P81001Y98-I 04/25/2011

NDM Configuration

ASP Element Manager

Figure 4-3 ASP Element Manager Welcome Screen

The top of the ASP Element Manager Welcome Screen has links to various functions: • System Management - Configure and view ASP parameters.• Statistics - View a listing and download of ASP statistics files.• Billing - To view and access the CDR files and Billing Files.• Provisioning - PWI (Provisioning Web Interface) that will allow access and

modification of all fields in Provisioning Data store on the ASP Nodes.• Alarms - ASP Logs alarm data to log files. • System Status - The status of ASP host and I/O, DAP, T1/E1 links are

displayed.• Change Password - change the admin password for ASP Element Manager

access.• Update DM Version - set the value for the most current DM application

version supported• Logout - Logs the user out of the ASP Element Manager.

The following Files provides the information of different functions of System Management.• The Statistics/ is described in Chapter, Statistics


04/25/2011 68P81001Y98-I 4-7

NDM Configuration

ASP Element Manager• the Alarms, Events and the Status of system are described in Chapter,

Status_Alarms • The Billing information is described in Chapter, Billing• The provisioning of users is described in Chapter, Provisioning

Changing the EM Password

From the ASP Element Manager Welcome Page, click on the Change Password link. On the Change Password screen, select the admin ID from the pull down menu, current password, and new password (twice for verification) and then click on the "Submit" bottom. This will change the admin password from the current password to the new password.Note The NDM system has two level of Element Manager permissions.

Admin level has read/write access. icc user level has just read permissions

Note The NDM Element Manager change password pull down menu not only contains the admin and icc users, but also the ndmprov1 (provisioning) user, as well as all the BU Admin users.

Figure 4-4 Change Your Password Screen


4-8 68P81001Y98-I 04/25/2011

NDM Configuration

ASP Element Manager

Updating the DM Client Version

From the ASP Element Manager Welcome Page, click on the Update DM Client Version Number link. On this screen, you will see the current maximum version of DM client supported. Enter the new numeric version numbers and press "Submit" to update the ASP server for a newer client version.Note The DM client version number set here is checked by each DM client

upon sign-in with the NDM system. Setting the DM client version incorrectly may result in users being incorrectly prompted to update their DM client version on their next sign-in!

Figure 4-5 Update the DM Client Version Screen

Logging Out of the ASP Element Manager

Click on the “Logout” link to log out of the ASP Element Manager.


04/25/2011 68P81001Y98-I 4-9

NDM Configuration

ASP System Configuration

ASP System Configuration 4

Overview This section describes the configuration tables contained in the ASP System Configuration screen. The ASP System Configuration screen is accessed by clicking on the “System Configuration” link on the ASP Element Manager Welcome Screen. The ASP System Configuration screen contains several tables. The editable configuration fields in "Operator Changeable parameters" table are the following:• Backhaul Type (T1 or E1)• iDEN System Version• System Type (iDEN)• EBTS version (SR13.4 and below or SR14.0)

Important The data in the fields above are filled by Motorola during installation of the ASP. No changes to these fields should be made by the operator without prior contact with Motorola CNRC and/or the local Motorola support team!

• VOICE ROUTING PORT (UDP Inbound to NDM)• CONTROL TCP PORT (TCP inbound and outbound)• DM CLIENT VOICE PORT (UDP outbound from NDM)

Several other tables are not-editable and displayed for operator viewing in the System Configuration screen. Description for each of these configuration tables follows.

NDAP Connection Configuration Table

NDAP stands for Number of DAPs on the System. The purpose of this table is to assign a Primary Device #’ and secondary Device #’ to the DAP.


4-10 68P81001Y98-I 04/25/2011

NDM Configuration


Figure 4-6 NDAP Connection Configuration Table

Definition of Fields• DAP ID - The identification assigned to the DAP.• Primary Device # - The value typed in this field references the

corresponding ’Device Number’ in the Device Configuration table. The Primary Device # is always ’1’ and references the first row entry (Device Number = 1) of the Device Configuration table.

• Secondary Device # The value typed in this field references the corresponding ’Device Number’ in the Device Configuration table. The Secondary Device # is always ’2’ and references the second row entry (Device Number = 2) of the Device Configuration table.

• Link Status - Is initially be set to ’1’, but is updated by the ASP software to reflect the DAP link status to the ASP.

Note The current Link Status for the DAP may not be accurately reflected via the ASP Element Manager System Configuration Screen as this parameter is updated only at initialization, and also because this screen is not updated real time.


04/25/2011 68P81001Y98-I 4-11

NDM Configuration


APD Configuration The Packet Duplication Table consists of APD ID and the DLCI fields. The fields are not editable via the EM and are configured automatically by the ACG config file download

TCP/IP Configuration The TCP/IP Configuration table consists of IP Addresses of all the three networks. It contains Public, Provider and Inter Nodal IP Addresses used for accessing the ASP Node. The table is not editable via the EM and is set during NDM installation time.

The NDM boxes (PTxAS and ASP) require specific TCP and UDP ports to be opened on each of the networks (within the customer firewall) for NDM services to operate correctly. The following ports must be opened for the ASP E0 IP network to permit DM client call processing and registration:

CONTROL TCP PORT (TCP inbound and outbound on the ASP site, default value is 10020)VOICE ROUTING PORT (UDP inbound and outbound on the ASP site, default value is 16700)DM CLIENT VOICE PORT (UDP inbound and outbound on the NDM client site, default value is 16800)

Firewall friendly

The firewall friendly feature was introduced in NDM version 01.03.10.

This feature was designed to allow flexibility in port selection in the NDM to accommodate a customer's unique set of firewall rules. Using this feature, the customer can define above port values in the NDM as desired to match that of ports enabled in their firewall configuration.

In previous versions of NDM above port values were hardcoded (with default values).

Starting from NDM version 01.03.10 these port values can be changed after installation (default values) with using ASP Element Manager.


4-12 68P81001Y98-I 04/25/2011

NDM Configuration

ASP System ConfigurationImportant Ports that are used for internal communications and applications on

ASP shall not be selected on the ASP site for DM client call processing and registration. The following ports are used for internal communication on ASP and shall not be selected on the ASP site for DM client call processing and registration (CONTROL TCP PORT and VOICE ROUTING PORT UDP): - TCP ports: 21, 22, 23, 25, 80, 111, 631, 729, 8005, 8009, 8080, 9000, 10020, 13000, 13001, 16000, 16002, 24999, 32772, 32774, 32775, 32778, 32784 - UDP ports: 111, 123, 631, 723, 726, 1036, 2000, 7005, 7007, 7008, 7010, 7011, 7012, 7013, 7015, 7016, 7017, 7018, 7019, 7020, 7023, 15879, 16700, 22333, 23444, 25855, 25999, 30277, 30279, 30286, 30296, 30297, 30300, 30506, 37489, 37541 DM CLIENT VOICE PORT must be free from any other applications on the DM client site.

Note Please refer to "Operator Changeable Parameters Table" of this chapter to choose ports other than the default ports shown above. The corresponding ports will need to be opened in the customer firewall access control list (ACL).

443 TCP (inbound to NDM)

The following ports must be opened for the NDM E1 IP network to allow NDM Element Manager operations:

80 TCP (HTTP port)8080 TCP (HTTP port - tomcat)13000 TCP (Element manager status applet)13001 TCP (Element Manager status applet)161/162 TCP/UDP (SNMP traps for Netcool feature)123 TCP/UDP (NTP)25 TCP/UDP (SMTP - outbound)25444 UDP (Element Manager Alarms applet)The following ports must be opened for the NDM E2 IP network to al-low NDM Element Manager operations. Note that because the E2 IP network is entirely private, it is recommended that no IP/port restrictions be placed on this network to avoid disruptions to any NDM operations.

25999 UDP (Element Manager replication)25855 UDP (Element Manager replication)9000 TCP (Timesten replication)1040 TCP (Timesten replication)15102 TCP (Timesten server)21 TCP (FTP - CNRC access)23 TCP (Telnet - CNRC access)


04/25/2011 68P81001Y98-I 4-13

NDM Configuration


Operator Changeable Parameters Table

The Operator Changeable Parameter table defines the backhaul type (T1/E1), System Release Version, System Type (iDEN/ Harmony), Voice Routing Port, TCP control port and Clients’ UDP port. The backhaul type can be either T1 or E1 interface. The System Release Version contains different iDEN Release versions. System Type consists of either iDEN / Harmony system. Note Modifying the backhaul type from T1 to E1 requires some additional

manual command line steps. Please refer to the NDM MOP for details.

Figure 4-7 Operator Changeable & APD configuration

The Voice Routing Port is used to assign the port number via which the voice packet are transferred. The EBTS SR version must be set either to SR13.4 (all iDEN SR up to and including SR13.4), or SR14.0. Control TCP port is used by clients to establish connections. DM client voice port is used by clients to send/receive voice packets• Submit Changes - Clicking this button causes the values in the table to be

stored in the database.

Important ASP restart must be performed after the database update (Submit Changes button) to make the changes effective!


4-14 68P81001Y98-I 04/25/2011

NDM Configuration


PTx AS Configuration PTx AS assigns configuration for DM Client on successful user sign in with the DM client application. The PTxAS servers are responsible for the download of Service configuration information to an authorized DM Client. The Configuration information contains some service configuration param-eters as well as provisioning information parameters. required for configuring the client for accessing various services on NDM.

The PTxAS services that can be accessed by the DM Client on a NDM are • Phonebook Service• TTS Service• Change Password Service

PTx AS updates the DM Service Configuration upon successful sign-in with the DM client application. DM users will be prompted automatically to upgrade their DM clients to a new version when the DM client version number configured in the ASP Element Manager is newer than the current version the user is running.

Note that the DM client <-> PTxAS Authentication over https requires that the PTxAS have a valid certificate assigned to the PTxAS web service on each PTxAS box. The certificate must be from a trusted certificate authority, such as Verisign, and is installed on the PTxAS boxes during system commis-sioning. Obtaining the certificate from the certificate authority is the NDM operator’s responsibility prior to starting NDM system installation.

IP Addressing for PTx AS

PTx AS is configured with an IP Address on the NDM public interface.This is done as a part of NDM configuration procedure at installation time

The well defined-port numbers and IP Address of PTx AS are hard-coded in the DM Client. See the NDM CIQ and NDM MOP for a list of these IP ports.


04/25/2011 68P81001Y98-I 4-15

NDM Configuration


System Status from Element Manager

The NDM Element Manager supports Real Time System status for compo-nents of both the ASP and PTX boxes. To access the system status screen, click on the System Status link on the NDM Element Manager Home Page. The java applet will load up and display the real time status of critical ASP and PTX components.

Figure 4-8 System Status

T

Registration Status On the top corner of the screen above is a Registration status link. Clicking on this link will direct you to a page that displays a snapshot (not updated in real time) of the users registered on the NDM system.

Registration Status will clearly indicate on which ASP node the user is regis-tered on i.e. Node 1 or 2.


4-16 68P81001Y98-I 04/25/2011

NDM Configuration


Registration Status Query

User can query for the Registration Status of a single user or all users in a BU or All DM Users registered on the NDM system.

Reg Status of a single user is obtained by entering the IMEI or UFMI or username/Business Unit of a user and pressing on Get Reg Status button (Fig 4-9).

Reg Status of all users in a Business Unit is obtained by entering the Business Unit name and pressing on Get Reg Status button (Fig 4-9).

Reg Status of all DM users on the NDM system is obtained by pressing on Reg Status of All DM Users button (Fig 4-9).

Figure 4-9 NDM Registration Status Query Screen


04/25/2011 68P81001Y98-I 4-17

NDM Configuration


Reg Status Query Result

The same layout in the window below (Fig 4-10) will be seen when the Reg Status of a single user or multiple users is displayed. Reg Status for a single user will have a single row displayed. Empty rows indicate absence of regis-tered user/s at the time when the search was done, as per the search criteria specified.

Figure 4-10 NDM Registration Status Query Result Screen


4-18 68P81001Y98-I 04/25/2011

Chapter 5

Provisioning

Overview 5

This section describes the interfaces available to provision users in the NDM system. By default, the NDM provides the following interfaces for provi-sioning:

Provisioning Web Interface (PWI) - accessible through ASP Element Manager)

BU Admin Web Interface (BU Admin or BU WI) - accessible through PTxAS web interface

The NDM system also supports a version of the iPP protocol (currently version 1.6) which provides support for custom 3rd party provisioning appli-cations to interface to the NDM system.


04/25/2011 68P81001Y98-I 5-1

Running H/F 2

Overview

NDM Provisioning Web Interface (PWI)

The NDM Provisioning Web Interface (PWI) sections below describe the interfaces used to assign user identity information used for authentication purpose and service access - related parameters using the PWI. Provisioning in ASP using the PWI implies associating the IMEI, UFMI, Ki with the ASP specific provisioning fields. Every DM User has to be provisioned in iHLR (step 1) and in ASP (step 2), so that it can be successfully authenticated.

The Provisioning link on the EM page displays operator login screen for entering into the PWI. Provisioning operator shall access ASP only from within the private, customer-network. The PWI is implemented using iPP, which will provide sufficient security

NDM NDMR01.03.10

5-2 68P81001Y98-I 04/25/2011

Provisioning

User Management

User Management 5

Add User The standard iDEN Operator’s procedure will be used to provision a DM user in iHLR for Dispatch Services. Once the iHLR user provisioning is completed, the IMEI provisioned in the iHLR can then be provisioned and assigned user information in the NDM ASP. The NDM Provisioning operator will use the UFMI and Ki associated with each IMEI and to provision in ASP via the Provisioning Web Interface (PWI).

Upon selecting “Add User” link on the NDM PWI page, it leads to screen where new users can be provisioned by entering information about the users. The information that can be entered include user name, first name, last name, E-mail, phone number, UFMI number, IMEI number, BU ID, Default Password, Ki, UDGC Service Permissions, Max. Number of UDGC members.

The UFMI, IMEI and Business Unit are mandatory fields that need to be entered before attempting to provision a user.Note The DM User’s IMEI must be added to the iDEN HLR prior to

adding the user to NDM system using PWI!

Figure 5-1 PWI Add User


04/25/2011 68P81001Y98-I 5-3

Running H/F 2

User Management

Search User The Search User screen is used to search for existing users by providing user’s information and getting results which match the search criteria.

Search can be done either on a single user or all users in a BU or all users on the NDM system.

Figure 5-2 PWI Search User

NDM NDMR01.03.10

5-4 68P81001Y98-I 04/25/2011

Provisioning

User Management

Search User Results Pressing ’List all DM Users’ button shall give a screen containing information about all the DM Users on the NDM system. The screen displays a maximum of 100 records, at a time. The screen has ’Previous’ and ’Next’ button to navigate thru any additional records.

’Edit’ Link is used to modify the fields or attributes in an individual record (refer Fig 5-4).

Figure 5-3 PWI Search User Results


04/25/2011 68P81001Y98-I 5-5

Running H/F 2

User Management

Edit User The Edit User screen allows either ’Modify’ or ’Delete’ operation on a subscriber record. UFMI, IMEI and Business Unit are mandatory fields. IMEI or UFMI can be used as the key for searching the record; IMEI is set as the default key. When Operator presses ’Modify’, the existing record is updated in the database with the new entered values. If the update is successful, it displays the Search User screen showing the modified record in the displayed list. If the update is unsuccessful, it will display a dialog box with an appro-priate error message.

When the Operator presses ’Delete’ button, it will display a dialog box saying ’Do you want to delete this user?’; if responds with No, it reverts back to the Search User screen; if Yes, it deletes the record and reverts back to the Search screen; the deleted record will not be in the displayed list.

Figure 5-4 PWI Edit User

NDM NDMR01.03.10

5-6 68P81001Y98-I 04/25/2011

Provisioning

User Management

Bulk Provisioning PWI supports bulk provisioning of DM subscribers via a well-defined text file. The Show Sample File link on the Bulk Provisioning page contains instructions and a template that can be used for generating a file for Bulk Provisioning. User can use the Browse button to select the desired file and click on the Upload button to provision a collection of IMEIs specified in the file.

System generates log file recording the results (success or errors) generated during bulk provisioning. User will be prompted to optionally view this file.

Figure 5-5 PWI Bulk Provisioning


04/25/2011 68P81001Y98-I 5-7

Running H/F 2

User Management

Change Operator Password

The provisioning operator will be able to change his/her password thru the Change Password window in PWI.

The Provisioning operator has to provide the user credentials i.e. username and the old password. Must confirm the new password by retyping the new password. When the user presses the Change button, the password field in the ASP Datastore will be updated, if user credentials are successfully verified.

The Clear button clears all the entered information on the window and allows the Operator to start all over again.

Figure 5-6 PWI Operator Password Change

NDM NDMR01.03.10

5-8 68P81001Y98-I 04/25/2011

Provisioning

User Management

Add BU Admin Account

A Business Unit (BU) is identified by using BU ID or Business Unit name. The BU Administrator can be created for each Business Unit if desired. Each BU Admin account shall assign individual users to pre-provisioned records in his/her Business Unit.

A BU Admin is created by the Provisioning Operator by entering information about the BU Administrator and clicking on the Add button.

Note that Business Unit, password and E-mail are mandatory fields.

The Clear button clears all the entered information on the window and allows the Operator to start all over again.Note It displays ’Update Successful’ following a successful addition of a

new BU Admin record. It will display ’Value for Business Unit is not unique’, if the addition of a new record failed because The entered value of Business Unit already exists in the database.

Note The maximum number of BU Admin accounts that can exist on an NDM system is 5,000

Figure 5-7 PWI Add BU Administrator


04/25/2011 68P81001Y98-I 5-9

Running H/F 2

User Management

Business Unit Admin Account Management Screen

A BU Admin record that has been created on the system can be modified by the Provisioning Operator via the Business Unit Management link.

Upon pressing the Business Unit Management link, it shows a Business Unit Administrator List, which displays fields such as BUID, password, e-mail address and phone number of every BU Admin record provisioned on the system. Every record displayed is modifiable via the Edit Link (Fig 5-7).

Figure 5-8 PWI Business Unit List

NDM NDMR01.03.10

5-10 68P81001Y98-I 04/25/2011

Provisioning

User Management

Edit BU Admin Account

Edit BU implies either modification/update or deletion of an existing BU Admin record. Note that the credential fields of Business Unit name, password and E-mail are mandatory fields. BU must be selected as the key for searching the record; it is set by default.

Modify BU Admin Account

The Provisioning Operator shall modify a BU Admin record by entering the information and pressing the Modify button in Fig 5-8.

Figure 5-9 PWI BU Management - Delete / Modify Screen


04/25/2011 68P81001Y98-I 5-11

Running H/F 2

User Management

Delete BU Admin Account

Please note that subscribers can be provisioned on the system without being managed by a BU Admin, and a BU Admin can exist without Business Unit users.

The Provisioning Operator shall delete a BU Admin record by entering the information and pressing the Delete button in Fig 5-8

! CAUTION

CAUTION! When the Delete button is pressed, it will pop up a dialog box as shown below. If the user answers Yes, it will delete all the subscribers assigned to this BU and then delete the BU Admin record. If the Operator answers No, it will delete the BU Admin record without deleting the subscribers assigned to this BU. If the user closes this dialog box by clicking on ’x’, it will say ’Problem encountered while Deleting BU’ and the BU Admin record will not be deleted.

If a record is successfully deleted, it shall no longer appear in the BU Admin List which is displayed after the deletion operation.

Figure 5-10 Delete BU - Dialog Box

NDM NDMR01.03.10

5-12 68P81001Y98-I 04/25/2011

Provisioning

User Management

Search BU Administrator

Edit BU Administrator window (see below) is accessed by clicking on the Search Administrator link. A Business Unit Administrator record may be searched by BU name using this screen.

When you click on the Search button, it will display the BU Administrator List (Fig 5-7) with a single row with the selected BU Admin record.

Figure 5-11 PWI Edit BU Administrators


04/25/2011 68P81001Y98-I 5-13

Running H/F 2

User Management

UDGC Agents Provisioning

UDGC Bulk provisioning is used to provision IMEIs for UDGC Agents in bulk. This windows is obtained by clicking on the UDGC Bulk Provisioning link under UDGC Management. A Sample File is provided with steps on how to create a file for bulk provisioning.

To bulk provision, a file must be selected via Browse button. When Upload button is pressed, the IMEIs in the selected file will be provisioned on the system.

It will prompt the user to optionally view the log results. Log files are generated for Parsing errors and Upload errors in the same directory where input file exists. Only records with valid format are provisioned.

Figure 5-12 UDGC Bulk Provisioning

NDM NDMR01.03.10

5-14 68P81001Y98-I 04/25/2011

Provisioning

User Management

UDGC Agents Management

UDGC Management screen contains the list of all the agent IMEIs existing in the database on both nodes. The ASP node assigned to each agent, and the Registration state of each agent is also displayed.

’Next’ and ’Previous’ buttons existing in the screen are used to navigate forward and backward.’Delete’ button is used to remove a particular or selected IMEIs from the Database. To delete all the IMEIs, click on ’Select All’ check box, to select all the displayed IMEIs for the delete operation.

Figure 5-13 UDGC IMEI List


04/25/2011 68P81001Y98-I 5-15

Running H/F 2

User Management

Notifying E-Mail configuration

E-mail configuration screen consisting of many fields configurable at the operator level. SMTP IP Address, NDM Website URL, Customer Support Phone number, From Field in E-mail. E-mail notification Text Area is available for DM User and BU Administrators. Maximum 500 characters is allowed in the Text Area.’Preview BU Admin’ button displays the E-mails format that is sent to newly added BU Administrators. ’Preview DM Mail’ button displays the E-mail format that is sent to newly added DM Users.’Submit Changes’ buttons will update the modified changes in the Database. The E-Mail configuration page currently supports English, Spanish, Portuguese, and Hebrew languages.

Figure 5-14 Notifying E-Mail Configuration

NDM NDMR01.03.10

5-16 68P81001Y98-I 04/25/2011

Provisioning

User Management

Retrieve NDM Subscriber by Key

The Retrieve NDM Subscriber by Key allows the PWI operator to locate a subscriber record based on IMEI and/or UFMI and display ’all attributes’ or ’selected attributes’ of the selected subscriber record, if found. The ’all attri-butes’ is selected by default.

Figure 5-15 Retrieve NDM Subscriber by Key


04/25/2011 68P81001Y98-I 5-17

Running H/F 2

User Management

Retrieve Multiple NDM Subscribers

The Retrieve Multiple NDM Subscriber page allows the PWI operator to locate groups of NDM subscriber records based on key fields.

The Number of Objects field, if specified, regulates how many search results are displayed.

The Operator can select ’all attributes’ or ’count of records’ or ’selected attri-butes’ for displaying results of the search. The ’all attributes’ is selected by default.

Figure 5-16 Retrieve Multiple NDM Subscribers

NDM NDMR01.03.10

5-18 68P81001Y98-I 04/25/2011

Provisioning

User Management

Retrieve Business Unit Administrator

The Retrieve Business Unit Administrator allows the PWI operator to search and display results of a specific BU Admin record based on search criteria.

Figure 5-17 Retrieve Business Unit Administrator


04/25/2011 68P81001Y98-I 5-19

Running H/F 2

User Management

Retrieve Multiple Business Unit Administrators

The Retrieve Multiple Business Unit Administrators feature allows the PWI operator to locate and display multiple BU Admin records based on the search criteria.

Figure 5-18 Retrieve Multiple Business Unit Administrators

NDM NDMR01.03.10

5-20 68P81001Y98-I 04/25/2011

Provisioning

User Management

Registration Status Registration Status screen allows the PWI user to display a snapshot (not updated in real-time) the user registrations on the NDM system, at the time when the.

The Operator can get the registration status of a single subscriber by entering the IMEI or UFMI or username/BU and pressing on Get Reg Status button. The Operator can obtain the status of all subscribers in a BU by entering the BU name and pressing on Get Reg Status button. The Operator can get the status of all the users on both nodes by pressing on Get Reg Status of All DM Users button.

Figure 5-19 Registration Status Screen


04/25/2011 68P81001Y98-I 5-21

Running H/F 2

User Management

Reg Status Results The Registration Status Results screen displays the registration status of 1 or more subscribers on either node, based on the search criteria.

Figure 5-20 Registration Status Results Screen

About IPP The About IPP link displays to the PWI operator the iPP/iSDK version(s) supported by the current NDM/PWI software release.

Currently, iPP version 1.6 is supported.

NDM NDMR01.03.10

5-22 68P81001Y98-I 04/25/2011

Provisioning

User Management

NDM BU Admin Web Interface (BU Admin)

The NDM BU Admin Interface sections below describe how to use the BU Admin Web interface. The BU Admin interface is intended to be used by an authorized 3rd party or customer representative to manage users and IMEIs assigned to a specific carrier Business Unit. For example, if Carrier X had a signed contract to provide Motorola users with 100 Dispatch Messenger users, Carrier X could create a Business unit (Motorola) and assign a Business Unit Administrator (Joe Admin, username MotorolaBU) to manage these 100 users. Carrier X would only provision 100 IMEIs for Motorola and assign those IMEIs the Motorola business unit and appropriate call permissions. The BU Admin could then assign any of those 100 IMEIs to a Motorola user and manage the user information himself.

It should be noted that BU Admins cannot add IMEIs to their Business Unit - their capability is limited to assigning user information to specific IMEIs the Carrier has placed in their Business Unit.

Using the BU Admin interface, carriers can off load the user management operations for large clients to the clients themselves.


04/25/2011 68P81001Y98-I 5-23

Running H/F 2

User Management

BU Admin Login The BU Admin interface can be accessed through the PTxAS server(s) using the following URL:

https://<your PTX URL>/buadmin/index.jsp

where <your PTX URL> is the URL of the carrier PTxAS server (example. dm.carrier.com). The BU Admin interface requires Java JRE 1.4.2 or better on the user’s PC. Due to issues with java 1.5 traversing proxy servers, Motorola recommends 1.4.2 as the JRE to operate the BU Admin web interface.

To login to the BU Admin screen, the NDM Carrier must have create a BU Admin account (username, password) using the PWI. See the PWI section above in this manual for information on how to do this.

Figure 5-21 BU Admin Login Screen

NDM NDMR01.03.10

5-24 68P81001Y98-I 04/25/2011

Provisioning

User Management

BU Admin Welcome Screen

After successful login, the BU Admin welcome screen is displayed. Three options are available to the user: User Management, Change Password, and Logout

Figure 5-22 BU Admin Welcome Screen


04/25/2011 68P81001Y98-I 5-25

Running H/F 2

User Management

BU Admin User Management Screen

From the BU Admin User Management Screen, the BU Admin user can view/add/delete/modify user records from his IMEI allotment from the carrier. An unassigned UFMI count can be seen above the top left of the user management table. Unassigned UFMIs will show in the table below with blank user information

To add a new user, click the edit button on one of the unassigned UFMIs (blank user information) and fill out the user information window when it pops up and click on Modify when complete.

To edit an existing user, locate the user record in the listing, and click the Edit button on the right side of the record. When the user information window pops up, edit the information and click on Modify. Note that several pages of user information may be available, so be sure to page through all the available listings when searching for a user.

To delete a user, locate the user record listing, and click the Edit button on the right side of the record. When the user information window pops up, press the Delete button. Note that this will revert the record back to blank state only (no user information) - it will not delete the record from the BU Admin listing.

Also note that carrier fields (UDGC permissions, UDGC max number of participants, UFMI, IMEI, etc.) are not editable by the BU Admin.

Figure 5-23 BU Admin User Management Screen

NDM NDMR01.03.10

5-26 68P81001Y98-I 04/25/2011

Provisioning

User Management

BU Admin User Information Screen

The BU Admin User Information screen (accessed by pressing Edit on the BU Admin User Management screen next to a BU Entry).

Figure 5-24 BU Admin User Information Screen


04/25/2011 68P81001Y98-I 5-27

Running H/F 2

User Management

BU Admin Change Password Screen

The BU Admin Change password screen allows the BU Admin user to change the password for the BU account.

Figure 5-25 BU Admin Change Password Screen

NDM NDMR01.03.10

5-28 68P81001Y98-I 04/25/2011

Provisioning

User Management

BU Admin Logout Screen

The BU Admin Logout screen is displayed when the BU Admin user clicks on the Logout link from the BU Admin Welcome Page.

Figure 5-26 BU Admin Logout Screen


04/25/2011 68P81001Y98-I 5-29

Running H/F 2

User ManagementNDM iPP Interface (iPP)

The NDM supports version of the iPP (iDEN Provisioning Protocol). iSDK v1.7.4 was created specifically for the NDM system, and should not be used to provision the iDEN iHLR unless approved by the iDEN iHLR product team. A separate provisioning client is required for iSDK v1.7.4 for NetDis-patch Messenger.

For additional information on the iPP interface, contact Motorola CNRC and/or the Motorola NDM Product Team.

NDM NDMR01.03.10

5-30 68P81001Y98-I 04/25/2011

Provisioning

User Management

3P Applications Management Overview

The NetDispatch Messenger (NDM) Third-Party Application Programming Interface (API) feature extends current NDM product functionality and capabilities by providing an API to the NDM System. The API provides Third-Party PTx application developers with access to iDEN Dispatch services, including Dispatch Registration/De-registration, Private Call, Call Alert, and Traditional Group Call through Motorola proprietary NDM protocol.

3P API feature is an optional feature. Contact Motorola CNRC to purchase/enable the feature.

This section describe the interfaces available to the Third-Party Applications Provisioning Web-Interface (3P PWI).

Provisioning of 3P API applications and associated IMEIs on the ASP will support the a new created 3P Provisioning Web-Interface.

3P Applications Provisioning is accessible through ASP Element Manager. The NDM 3P supports version 1.7 of the iPP protocol.

The following functions are supported for 3P Applications Provisioning:• 3P Bulk Provisioning• Send 3P Email• Delete 3P Application• Search 3P Dispatch Client• Retrieve 3P Application By Key• Retrieve Multiple 3P Applications• Retrieve 3P Dispatch Client By Key• Retrieve Multiple 3P Dispatch Clients


04/25/2011 68P81001Y98-I 5-31

Running H/F 2

User Management

Access 3P Applications Management

This section describes how to access and login to Third Party (3P) Applica-tions Provisioning through ASP Element Manager. This 3P PWI will be accessible only to the Provisioning Operator and System Administrator.

Follow the steps provided below:

Step 1: Using a PC with Microsoft Internet Explorer 6.0 or better and Java JRE 1.5 or better connect to the ASP Element Manager. The address is http://<ASP Element Manger IP>:8080/prov/Login.html.

Step 2: Login to the NDM Provisioning web page using the administrator is login information user name "admin" or "provision" account.

After logging in successfully, the screen displays "Welcome to the NDM Provisioning Web Interface" as below:

Figure 5-27 3P Applications Management

List of all 3P Applications Management Provisioning functions are allows for 3P API feature.

NDM NDMR01.03.10

5-32 68P81001Y98-I 04/25/2011

Provisioning

User Management

3P Bulk Provisioning

3P PWI allows bulk provisioning of Dispatch Clients associated with a 3P application. This function has control for the user entry of file name to be uploaded and triggering the bulk upload.

Bulk provisioning is allowed on the upload in Excel template (.csv) with pre-defined format with fields such as:

• Company Name• Application Name• Set of Dispatch Client IMEI• Set of Dispatch Client UFMI

The 3P Bulk Provisioning procedure is limited to provisioning of a maximum of 256 Dispatch Clients per application.

Follow the steps provided below to perform 3P Bulk Provisioning:

Step 1: Click on "3P Bulk Provisioning" tab in the sub menu from NDM Provisioning web page. The "3P Bulk Provisioning" displays as in Figure 5-28:

Figure 5-28 3P Bulk Provisioning


04/25/2011 68P81001Y98-I 5-33

Running H/F 2

User ManagementStep 2: Click on "Show a sample file" link on the "3P Bulk Provisioning" page contains instructions and a template that can be used for generating a file for Bulk Provisioning. Sample 3P Bulk Provisioning displays as in Figure 5-29:

Figure 5-29 Sample of 3P Bulk Provisioning

Step 3: Right Click on "download" button to download 3P Provisioning template and. Click on "Save Target As"". Save As Window appears and save the sample template on the local Desktop and click on "Save". Verify it is saved in .csv format.Note The 3P user’s IMEI must be provisioned to the iDEN iHLR prior

perform the upload of 3P Bulk Provisioning.

Step 4: Using Microsoft Excel to modify the sample template as saved in step 3 as:

Company Name: Name of company 3P Applications belongs to.

Application Name: Name of the 3P Applications managed by this 3P Appli-cation Administrator.

IMEI: The 3P Dispatch Client unique identifies as 3P Client. It is 15 decimal digits.

UFMI: The 3P Dispatch Client unique identifies as (Urban ID*Fleet ID*MemberID).

NDM NDMR01.03.10

5-34 68P81001Y98-I 04/25/2011

Provisioning

User ManagementSee Figure 5-30 for an example of upload template file in Microsoft Excel updated with Company Name

"Motorola", Application Name as "iden", with valid IMEI and UFMI.

Figure 5-30 Example of 3P Bulk Provisioning template upload file

Step 4: Click on "Browse" button in "3P Bulk Provisioning" to upload 3P Provisioning File which saved as .csv format the in Figure 5-30.

Step 5: Click on "Upload" button to provisioning a collection of 3P IMEI specified in the file above in Figure 5-30.

System generates log file recording the results (success or errors) generated during 3P Bulk Provisioning.

Note UFMI(s) specified in the bulk provisioning file (s) MUST match the UFMI provisioned in the iHLR or incorrect 3P API user information will be provided to 3P client users !


04/25/2011 68P81001Y98-I 5-35

Running H/F 2

User Management

3P Bulk Provisioning Limit Restriction

The user can provision multiple dispatch clients to the 3P Application using the sample template bulk File:• In the bulk file, the user must enter the SAME Company Name and

Application name for all IMEI/UFMIs.• If more than 256 entries exist in the bulk file, it will abort and warn the user

about the upper limit per application.• 3P Provisioning on NDM System is restricted to a maximum of 256

Dispatch Clients per application.• 3P Provisioning on NDM System is restricted to a maximum of 1000

applications per NDM System. • Only Bulk Provisioning of 3P Dispatch Clients is supported for the in 3P

API feature. Every provisioning update request will trigger a unique new serial number to be generated on the ASP and associated with the Application.

• Performing 3P Bulk Provisioning with duplicated IMEI which the IMEI has been already provisioned will overwrite the previous provisioned record.

• Total combined 3P Client and Dispatch Messenger Client usage on the system is limited to 80,000.

• Perform 3P provisioning only during maintenance.• Registration will be needed with new serial number when adding additional

instances.

NDM NDMR01.03.10

5-36 68P81001Y98-I 04/25/2011

Provisioning

User Management

Send 3P Email Send a 3P email to notify the 3P customer with information required to enable the 3P Application to access dispatch services on iDEN via NDM.

Email Information includes the following fields:• URL for accessing NDM system.• Company Name/Application Name/Serial Number• UFMI of Dispatch Clients provisioned for the Application.

Follow the steps provided below to perform Send 3P Email:

Step 1: Click on "Send 3P Email" tab in the sub menu from NDM Provi-sioning web page. The "Send 3P Email" displays as in Figure 5-31:

Figure 5-31 Send 3P Email window

Step 2: Enter in the Serial Number in the "Serial Number" box.Note Serial Number is the unique ID of the 3P Application to which 3P

Dispatch Clients belongs to.

Step 3: Enter in the desired email address in the "E-mail Address" box.

Step 4: Click on "Preview" tab to allows the user to view the Email Infor-mation for user convenience. See Figure for an example of "3P Preview Email".


04/25/2011 68P81001Y98-I 5-37

Running H/F 2

User Management

Figure 5-32 Preview Email window

Note This 1st line in E-mail description "Here is the requested 3P Dispatch Application account details:" can be customized in "Email Configuration".

Note The E-mail Subject can be customized in "Email Configuration".

Step 5: Click on "Send Email" tab to send email with to the desired target address specified. This email address will not be stored on the system.

Step 6: A message window will appear when the email has been sent success-fully as in figure below.

See Note

NDM NDMR01.03.10

5-38 68P81001Y98-I 04/25/2011

Provisioning

User Management

Notifying 3P Email Configuration

The first line in the 3P EMail description and 3P EMail Subject as in Figure 5-32 can be customized and configurable at the operator level.

The 3P EMail Content description maximum 500 characters is allowed in the Text Area.

The 3P EMail Subject maximum 500 characters is allowed in the Text Area.

Follow the steps provided below to customize the first line in the 3P Email content description in ASP Database.

Follow the steps provided below to customize the EMail Subject in the ASP Database.

Step 1: Click on "Email Configuration" tab in the sub menu from NDM Provisioning web page. The "Email Configuration" displays as in Figure 5-33

Figure 5-33 Notifying 3P Email Configuration

Step 2: Enter the "3P EMAIL SUBJECT" to customize the 3P EMail Subject.

Step 3: Enter the "3P EMAIL CONTENT" to customize the first line in the 3P EMail Description.

Step 4: Click on "Submit Changes" button will update the modified changes in the Database.


04/25/2011 68P81001Y98-I 5-39

Running H/F 2

User Management

Delete 3P Application

Delete 3P Application supports Bulk Deletion. It allows the user delete of all Dispatch Client provisioning records associated with the application name. Note 3P Application Management does not support single Client deletion

of 3P Application.

Delete 3P Application support search and delete based on Company Name, Application Name, or Serial Number or any combination of these:Note The user is permitted to enter ONLY serial number or a combination

of company name AND application name".

If the user enter any invalid combination (example: if the user enter only Company Name and clicks on the "Delete" tab). The screen error displays "Enter either ONLY serial number or a combination of Company Name AND Application Name". Click on "OK" tab to ackowlege the error.

Follow the steps provided below to perform "Delete 3P Application" based on Serial Number:

Step 1: Click on "Delete 3P Application" tab in the sub menu under NDM Provisioning. "Delete 3P Application" display is below in Figure 5-34.

Figure 5-34 Delete 3P Application

Step 2: Enter the Serial Number in the "Serial Number" box as shown in Figure 5-34

NDM NDMR01.03.10

5-40 68P81001Y98-I 04/25/2011

Provisioning

User Management

Figure 5-35 Delete 3P Application based on Serial Number

Step 3: Click on the "Delete" box to initiate deletion of the 3P Application based on Serial Number entered above.

A warning window is displayed to notify the user that all Dispatch Clients provisioned for this Application Name will be deleted before actual removal occurs.

Step 4: If the user wants to continue to delete all Dispatch Clients belonging to the Application Name or Serial Number, then Click on "Yes" button. The screen displays a confirmation stating "Application Successfully Deleted" if the delete 3P Application is successfully completed.


04/25/2011 68P81001Y98-I 5-41

Running H/F 2

User Management

Delete 3P Application based on Company Name and Application Name

Delete 3P Application is Bulk Deletion. It allows the user to delete of all Dispatch Client provisioning based on Company Name AND Application Name.

Step 1: Click on "Delete 3P Application" tab in the sub menu in the NDM Provisioning. Enter Application Name and Company Name as in figure below.

Figure 5-36 Delete 3P Application based on Application Name AND Company Name

Step 2: Click on the "Delete" box to initiate the delete 3P Application based on Company Name AND Application Name as above:

A warning window displays telling the user that all Dispatch Clients provi-sioned for this Application Name will be deleted actual removal occurs.

Step 3: If the user wants to continue to delete all Dispatch Clients belong to the Application Name or Serial Number, then Click on "Yes" button. The screen displays a confirmation stating "Application Successfully Deleted" if deletion of the 3P Application is successfully completed.

NDM NDMR01.03.10

5-42 68P81001Y98-I 04/25/2011

Provisioning

User Management

Search 3P Dispatch Client

Search/Retrieve 3P Dispatch Client allows user to search and retrieve all 3P Dispatch Client records belong to the serial number. The search is based on key field such as 3P Application Name or Serial Number.

The user is allowed to enter any valid key based on Application Name or Company Name or starting IMEI.

Follow the steps provided below to perform "Search 3P Dispatch Client" based on Serial Number.

Step 1: Click on "Search 3P Dispatch Client" tab in the sub menu from NDM Provisioning web page. The "Search 3P Dispatch Client" displays as in Figure 5-37:

Figure 5-37 Search 3P Dispatch Client based on Serial Number

Step 2: Enter the Serial Number in the "Serial Number" box as shown in Figure 5-37.

Step 3: Click on "Search" or "List All DCs" to search/retrieve for all Dispatch Client belong to the serial number as enter above. The screen displays the search result as in Figure 5-38.


04/25/2011 68P81001Y98-I 5-43

Running H/F 2

User Management

Figure 5-38 Search Result from 3P Dispatch Client based on Serial Number

NDM NDMR01.03.10

5-44 68P81001Y98-I 04/25/2011

Provisioning

User Management

Retrieve 3P Application By Key Client

Retrieval of 3P Application Client by key allows the user to search based on Application Name, Company Name, or Serial Number and display ’all attribute’ or ’select attribute’ of the selected 3P record, if found. The ’all attri-butes’ is selected by default.Note Users must enter Application Name and Company Name OR Serial

Number.

Follow the steps provided below to perform "Retrieve 3P Application By Key" based on Serial Number.

Step 1: Click on "Retrieve 3P Application By Key" tab in the sub menu from NDM Provisioning web page. The "Retrieve 3P Application By Key" is displayed as follows in Figure 5-38 and user enter a valid serial number.

Figure 5-39 Result of Retrieve 3P Application By Key based on Serial Number with ’all attributes’


04/25/2011 68P81001Y98-I 5-45

Running H/F 2

User Management

Retrieve Multiple 3P Application

Retrieval of Multiple 3P Applications allows users to search and display multiple records from the 3P Application Mapping based on the search criteria. A Company Name could potentially have multiple applications provi-sioned.


The user can select ’all attributes’ or ’count of records’ or ’selected attributes’ to display results for the search. The ’all attributes’ is selected by default.

Follow the steps provided below to perform "Retrieve Multiple 3P Appli-cation based on Company Name.

Step 1: Click on "Retrieve Multiple 3P Application By" tab in the sub memu from NDM Provisioning web page. The "Retrieve Multiple 3P Application" displays as in Figure 5-40 and user enter a valid Company Name.

Figure 5-40 Retrieve Multiple 3P Application

Step 2: Click on "Search" to locate Multiple 3P Application records. A screen displays the search result as Figure 5-41.

NDM NDMR01.03.10

5-46 68P81001Y98-I 04/25/2011

Provisioning

User Management

Figure 5-41 Result screen from Retrieve Multiple 3P Application


04/25/2011 68P81001Y98-I 5-47

Running H/F 2

User Management

Retrieve 3P Dispatch Client

The retrieve of 3P Dispatch Client allows user to search and display 3P Dispatch Client records belonging to the associated UFMI or IMEI and display if found in the data store. The retrieve 3P Dispatch Client is based on search criteria such as UFMI or IMEI.

The user can select ’all attributes’ or ’selected attributes’ to displaying results of the search. The ’all attributes’ is selected by default.

Follow the steps provided below to perform "Retrieve 3P Dispatch Client" based on UFMI.

Step 1: Click on "Retrieve 3P Dispatch Client" tab in the sub menu from NDM Provisioning web page. The "Retrieve 3P Dispatch Client" displayed as in Figure 5-42 where users enter a valid UFMI.

Figure 5-42 Retrieve 3P Dispatch Client

Step 2: Click on "Search" to locate the 3P Dispatch Client. A screen displays the search result as in Figure 5-43.

NDM NDMR01.03.10

5-48 68P81001Y98-I 04/25/2011

Provisioning

User Management

Figure 5-43 Result from Retrieve 3P Dispatch Client based on UFMI


04/25/2011 68P81001Y98-I 5-49

Running H/F 2

User Management

Retrieve Multiple 3P Dispatch Clients

Retrieval of Multiple 3P Dispatch Clients allows users to search and display multiple records from the 3P Dispatch Clients based on the search criteria.


The user can select ’all attributes’ or ’count of records’ or ’selected attributes’ for display results of the search. The ’all attributes’ is selected by default.

Follow the steps provided below to perform "Retrieve Multiple 3P Dispatch Clients based on the Company Name.

Step 1: Click on "Retrieve Multiple 3P Dispatch Clients" tab in the sub menu from NDM Provisioning web page. The "Retrieve Multiple 3P Application" displays as in Figure 5-44 and user enter a valid Company Name.

Figure 5-44 Retrieve Multiple 3P Dispatch Clients

Step 2: Click on "Search" to start locate Multiple 3P Dispatch Clients records and a screen displays the search result as Figure 5-45.

NDM NDMR01.03.10

5-50 68P81001Y98-I 04/25/2011

Provisioning

User Management

Figure 5-45 Result screen from Retrieve Multiple 3P Dispatch Client


04/25/2011 68P81001Y98-I 5-51

Running H/F 2

User Management

N O T E S . . .

NDM NDMR01.03.10

5-52 68P81001Y98-I 04/25/2011

Chapter 6

DM Installation Overview

Introduction 6

DM Client Executable is located on the PTx AS servers. The Executable has to be downloaded for installing the DM Client on to the Local PC Drive. The download site will be accessible from the User Web interface (UWI) on the PTxAS server(s). The user must be authenticated before downloading the client application is permitted.

Download The download executable is available on the PTx AS. The User has to connect to the PTx AS by providing the https URL. The user will be prompted for credentials like username, password and BU ID via the User Login procedure supported on the web-page. These credentials are provided in the provisioning confirmation e-mail

The Latest version of the DM software is uploaded and stored on the PTx AS file system.• The user can access this service any time, after receiving e-mail.• User has to download client application prior to initial installation• User can re-download client application when DM Client user is notified of

version change by the ASP.

Application Installation

The download Client Application is installed by the user on his/her PC based on instructions provided on the UWI website.

The application on starting connects to the system and registers with first the PTxAS and then the ASP. the client user is authenticated during installation.


04/25/2011 68P81001Y98-I 6-1

DM Installation Overview

IntroductionThe client user is authenticated on the system every time the Client accesses services on the system

Upgrade The system maintains a version number on the DM Application Executable. Should the NDM operator notify users a new DM Application Executable is available, the end users would be required to Upgrade their current NDM application using the Windows Add/Remove Programs methods.


6-2 68P81001Y98-I 04/25/2011

Chapter 7

Billing

Billing Files 7

Overview The NetDispatch Messenger generates it own billing files unique from the iDEN DAP. Each billing file contains a record of completed DM calls processed by the ASP. The call data stored in the billing file can be used by the administrator to create billing records for utilization charges, and perform statistical analysis on call profiles.

Because the ASP has an internal clock, the timestamp for billing files generated by the ASP may differ from the timestamp for billing files generated by the iDEN DAP.

Billing File Maintenance

It is strongly recommended to download the latest billing files on your PC hard drive on a daily basis. Billing files can be downloaded onto your PC hard drive by simply right clicking on the billing file name and saving the file onto your PC hard drive. A day’s worth of billing information can be downloaded on your PC hard drive by simply right clicking on the <Day of the Week>_Stats.tar.gz filename located in the Index of/Statistics directory and saving the file on your PC hard drive.

Important The oldest billing files are overwritten by the most recent billing files, such that only the most recent four weeks of billing files (prior to the most recent Sunday) are stored on the ASP database. It is strongly recommended to save billing files onto your PC hard drive before they are overwritten.


04/25/2011 68P81001Y98-I 7-1

Billing

Billing Files

Figure 7-1 Billing Screen

Billing File Location The billing files are located in the Index of/Statistics directory within the Billing folder. The Index of /Statistics directory is accessed by clicking on the Statistics/Alarms link on the ASP Element Manager. The billing files are in a binary format and are not viewable on the ASP Element Manager.

Billing File Organization

The billing folder contains a number of billing files. Each billing file contains records of completed DM calls processed by the ASP for a 30-minute period. A billing file is opens at the zero-minute or 30-minute point of each hour, remains open for 30 minutes while records of completed DM calls are copied into the file, and then closes after 30 minutes.


7-2 68P81001Y98-I 04/25/2011

Billing

Billing Files

Billing File Retention Billing files are created every 30 minutes. Billing files are overwritten with more recent billing files such that only the most recent four weeks of billing files prior to the last Sunday are available for download from the ASP database.

Viewing Billing Files The billing files are in a binary format and are not viewable on the ASP Element Manager. A billing processor is required to convert the billing files from binary format to a readable text format. The Billing file parser is available for download at the bottom of the Element Manager Billing page.

Downloading Billing Files

The billing files can be downloaded to the PC hard drive by right clicking on the file name and then clicking on the Save button. Billing files can be downloaded from any PC with IP connectivity to the ASP

Billing File Structure The billing file is made of the following types of records:

Table 7-1 Billing Record Types.

The billing file is structured such that the Header Record is always the very first record, followed by one or more Call Detail Records. The last record in the billing file is always the Trailer Record.

Each record always contains the following fields: • Record Size- specifies the size of the record which includes the record size

field itself and all appended modules inside the record.• Record Type- specifies the type of the record (e.g. Header, Call Alert,

Private Call, Group Call, or Trailer). If the record is not recognized by the billing processor, the record size can be used to skip to the next billing record.

Record Type Description

Header Record Describes the contents and format of the billing file. This is always the very first record in the billing file.

Call Detail RecordContains all call information necessary for the operator to create a billing record. There are three types of call detail records: Call Alert, Private Call, and Group Call. Call Detail Records make up the middle section of the billing file.

Trailer RecordMarks the end of the billing file. The trailer record will always be present in the billing record even if the ASP is shutdown or powered off. This is always the last record of the billing file.


04/25/2011 68P81001Y98-I 7-3

Billing

Billing Files• Date & Time- denotes the start of a billing interval. See Table 7-4 Date and

Time Field Format for a description of this field. This field is only found in Header and Trailer records.

Billing Filename Format

A billing file name for an opened billing file which was generated at 1 PM, April 14, 2003 has the following format: ABA030414130026.

Table 7-2 Billing Filename Format

Field Description

File TypeFirst two letters of the billing file name. Always set to ‘AB’ for billing files created by the ASP.

Status

Third letter of the billing file name.Set to ‘A’ when the file opened.Set to ‘U’ after closing the file.Set to ‘P’ after the file has been ftped to a downstream billing processor.

Year 00-99

Month 00-12

Day 00-31

Hour 00-23

Minute 00-59

File Sequence Number 00-99


7-4 68P81001Y98-I 04/25/2011

Billing

Billing Files

Billing Header Record The header record describes the contents of a billing file. The format of the header record is given below.

Table 7-3 Header Record Format

FieldSize

(bytes) Description

Record Size 2 Specifies the size of header record including the record size itself.

Record Type 1

Specifies the type of record. In this instance, the record type indicates a header record. The billing parser should map the value in the Record Type field (value = 0x05) from binary format to text format to say "Header" in the billing header record.

File Format Version 2Specifies the version of the records in the billing file. Has the form ‘XY’ where ‘X’ is incremented each time a large change to the billing format is made and ‘Y’ is incremented each time a small change to the billing format is made.

ASP EBTS ID 4 The EBTS ID assigned to the ASP. For example, if an EBTS ID of ‘48’ is assigned to the ASP, the filed would say ‘0048’.

Date and Time 6 Denotes the start of the billing interval. The format of date and time field is given below.


04/25/2011 68P81001Y98-I 7-5

Billing

Billing FilesTable 7-4 Date and Time Field Format

Billing Call Detail Records

Call Detail Record for Call Alert

The ASP will record a call alert in the billing file as along as the call alert is successful and involves the ASP. Call alerts between DMs registered on the same ASP will be recorded as one call.

FieldSize

(bytes) Description

Year 1 Specifies the last 2 digits of the year in which the Date and Time Module was created. Possible values range from 0 to 99.

Month 1 Specifies the month in which the Date and Time Module was created. Possible values range from 1 to 12.

Day 1 Specifies the day in which the Date and Time Module was created. Possible values range from 1 to 31.

Hour 1 Specifies the hour in which the Date and Time Module was created. Possible values range from 0 to 23.

Minute 1 Specifies the minute in which the Date and Time Module was created. Possible values range from 0 to 59.

Second 1 Specifies the second in which the Date and Time module was created. Possible values range from 0 to 59.


7-6 68P81001Y98-I 04/25/2011

Billing

Billing FilesThe CDR format for call alerts is given below.

Table 7-5 CDR Format for Call Alerts

*See Appendix B for a listing of RR Cause values.

FieldSize

(bytes) Description

Record Size 2 Specifies the size of the Call Detail Record including the record size itself and any appended modules and sub-modules.

Record Type 1

Specifies the type of record. In this instance, the record type indicates an Individual Dispatch Call Detail Record. The billing parser should map the value in the Record Type field (value = 0x07) from binary format to text format to say "Call Data" in the billing call detail record.

Transaction Type 1Specifies the type of individual call attempted. The billing parser should map the value in the Transaction Type field (value = 0x05) from binary format to text format to say "Call Alert" in the billing call detail record.

Time of Received Request 6

Specifies the time which the DAP received the initial call request. For a call alert, the time of the received request is the time when the ASP receives a call request from the NetDispatch Messenger or when the ASP receives an inbound Call Alert Request message from the DAP. The time of the received request uses the date and time field format.

Call Duration 2Specifies the length of the call from initial channel allocation through call termination. This field is incremented in the tenths of seconds. For call alerts, this value is always zero.

Call Reference Identifier 9 This is the call identifier that is generated by the DAP.

Originator UFMI 9 Specifies the UFMI of the originating subscriber.

Originator IMSI 8 Specifies the IMSI of the originating subscriber. The IMSI will appear only when it is a DM client.

Target UFMI 9 Specifies the UFMI of the call target.

Target IMSI 8 Specifies the IMSI of the call target. The IMSI will appear only when it is a DM client.

Originator’s Access Point 17 This field is always will be null.

Target’s Access Point 17 This field is always will be null.

RR Cause* 2 The result of the call alert.


04/25/2011 68P81001Y98-I 7-7

Billing

Billing FilesCall Detail Record for Private Call

The ASP will record a private call in the billing file as long as the call is successful and the ASP is involved. A private call between two Dispatch Messengers registered on the same ASP will be recorded as one call. A private call involving two different ASPs will be recorded as one call per ASP.

The CDR format for Private Calls is given below.

Table 7-6 CDR Format for Private Call

FieldSize

(bytes) Description

Record Size 2 Specifies the size of the Call Detail Record including the record size itself and any appended modules and sub-modules

Record Type 1


Transaction Type 1Specifies the type of individual call attempted. The billing parser should map the value in the Transaction Type field (value = 0x01) from binary format to text format to say "Private Call" in the billing call detail record.


Specifies the time which the ASP received the initial call request.

If the call is from one DM User to another DM User, or, if the call is from an MS (Mobile Subscriber) to a DM User on the same ASP, the value is the time the ASP received the call request for the private call.

If the call is from an MS to a DM User, the value is the time that the ASP receives an inbound Private Call Request message from the DAP.

A CDR is placed in the billing file at the time the call ends (when the ASP receives a PC_STOP message from the DAP).

The time of the received request uses the date and time field format.

Call Duration 2

Specifies the length of the call from initialization (when the ASP receives an inbound Private Call Request message) though call termination (when the ASP receives a Private Call End message). This field is incremented in the tenths of seconds but displayed to the user in seconds.


Originator UFMI 9 Specifies the UFMI of the originating subscriber.


Target UFMI 9 Specifies the UFMI of the call target


7-8 68P81001Y98-I 04/25/2011

Billing

Billing Files


Call Detail Record for Group Call

The ASP will record the group call into the billing file as long as the call is successful and if any of the DM Users are served by the ASP involved in the group call. If a DM Users does not accept an invitation on the group call, the call will not be recorded into the billing file.

The CDR format for Group Call is given below.

Table 7-7 CDR Format for Group Call

Target IMSI 8 Specifies the IMSI of the call target. The IMSI will appear only when it is a DM client.

Originator’s Access Point 17 This field is always will be null.

Target’s Access Point 17 This field is always will be null.

Number of WLAN AP Handovers 2 This field is always will be null.

RR Cause* 2 The result of the private call.

FieldSize

(bytes) Description

FieldSize

(bytes) Description


Record Type 1


Transaction Type 1Specifies the type of individual call attempted. The billing parser should map the value in the Transaction Type field (value = 0x02) from binary format to text format to say "Group Call" in the billing call detail record.


04/25/2011 68P81001Y98-I 7-9

Billing

Billing Files


Call Detail Record for User Defined Group Call

The ASP will record the user defined group call into the billing file as long as the call is successful.

The CDR format for User Defined Group Call is given below.

Table 7-8 CDR Format for User Defined Group Call


Specifies the time which the ASP received the initial call request. If the call is from a DM User to another DM User, or, if the call is from a Mobile Subscriber to a DM User on the same ASP, the value is the time the ASP receives a call request for a group call.

If the call is from an MS to a DM User, the value is the time that the ASP receives a Group Call Page Request message from the DAP.

A CDR is placed in the billing file at the time the call ends (when the ASP receives a Group Call End message from the DAP).


Call Duration 2

Specifies the length of the call from initialization (when the ASP receives a Group Call Page Request message) though call termination (when the ASP receives a Group Call End message). This field is incremented in the tenths of seconds but displayed to the user in seconds.


Talkgroup ID 4 This is the ID of the talkgroup.

Originator UFMI 9 Specifies the UFMI of the originating subscriber. Note this will only contain a partial UFMI (Fleet/ID only)


Number of Paricipants 2 Specifies the number of subscribers, including the originator itself, that are

involved in the call.

Number of WLAN AP Handovers

2 This field is always will be null.

RR Cause* 2 The result of the group call.

FieldSize

(bytes) Description


7-10 68P81001Y98-I 04/25/2011

Billing

Billing Files

FieldSize

(bytes) Description


Record Type 1


Transaction Type 1 Specifies the type of individual call attempted.


Specifies the time which the ASP received the initial call request. A CDR is placed in the billing file at the time the call ends (when the UDGC timer in ASP expires).


Call Duration 2 Specifies the length of the call from initialization though call termination. This field is incremented in the tenths of seconds but displayed in the CDR in seconds.

UDGC Name 20 This is the text name assigned to the UDGC call by the UDGC originator.

Originator UFMI 9 This is the UFMI of the UDGC call originator.


Number of Participants 2 Number of participants in this UDGC call (3-20)

Member UFMI List 40 UFMI of each participating member in this UDGC.


04/25/2011 68P81001Y98-I 7-11

Billing

Billing Files

Billing Trailer Records The trailer record marks the end of the billing file.Note The trailer record will always be present in the billing file even if the

ASP was shutdown in the middle of a billing period, or disk error occurred preventing the ASP to write to the billing file, etc.

The format of the trailer record is given below.

Table 7-9 Trailer Record Format.

*

FieldSize

(bytes) Description

Record Size 2 Specifies the size of the trailer record including the record size itself.

Record Type 1

Specifies the type of record. In this instance, the record type indicates a trailer record. The billing parser should map the value in the Record Type field (value = 0x06) from binary format to text format to say "Trailer" in the billing trailer record.

Date and Time 6 The date and time field specifies the ending of the billing interval. The format for this field is described in Table 7-4 Date and Time Field Format.

File Sequence Number 2

This is a number (from 0 to 99) which specifies the sequence of billing files. The same file sequence number is used in the dispatch billing file name. The file sequence number is incremented each time a billing file is created. There may be cases where the trailer record is not created but the file sequence number will still be incremented. Once the file sequence number reaches 99, the next number rolls over to ‘0’.

Record Count 4 Specifies the number of records in the file. The record count includes the header record(s) all individual CDRs, and the trailer record.


7-12 68P81001Y98-I 04/25/2011

Chapter 8

Statistics

Statistics, Log, & Config Files 8

Organization of Statistics Files

There are three types of statistics files or folders available in the Index of/Statistics directory. • Downloadable Text File• Downloadable Binary File• Downloadable Zip File.

Downloadable Text File

At the start of each day of the week, a statistics file will be generated for that day. The file is named according to the particular date(e.g., asp_20050218_emt_stats.txt, asp_20040613_emt_stats.txt,.). Where first four digits indicates the year, next two digits indicates the month, following two digits indicates the day of the month. Statistics for private call, group call, call alert, dispatch statistics, and alarm statistics are collected and assigned to a unique file.

The statistics files can be downloaded locally or remotely by right-clicking on the file name and saving the file onto the PC hard drive.

Downloadable Binary File

At the end of each day a binary file is generated with naming convention as “asp_<year><month><day of the month>_emt_stats.bin”. The binary file can be downloaded locally or remotely by clicking on the link. A system window is popped up indicating options like “save”, “open” “cancel” and “more info”.


04/25/2011 68P81001Y98-I 8-1

Statistics

Statistics, Log, & Config FilesDownloadable Zip File:

The Statistics screen contains a link to zip file. The Zip file can be downloaded locally or remotely by right-clicking on the link. After downloading the zip file, unzip and extract the actual file. The filenames have the following name convention:

“asp<year><month>em_stats.bin" (or txt).tgz

Statistics File Maintenance

It is strongly recommended to download the latest statistics files onto your PC hard drive on a regular basis. Statistics files can be downloaded onto your PC hard drive by simply right-clicking on the statistics file name (e.g. “asp<year><month><day of the month>_emt_stats.bin”) and saving the file onto your PC hard drive.

Important Statistics files are updated on a daily basis, and tarred/gzipped up on a monthly basis. Only the most recent two weeks of statistics files (prior to the most recent Sunday) are available on the ASP database. It is strongly recommended to save statistics files onto your PC hard drive before they are overwritten by more recent statistics.

Viewing Statistics Files Statistics and alarms generated during the most recent 7 days are available for viewing on the ASP Element Manager. Call statistics and alarm statistics generated during a particular time period are viewed on the ASP Element Manager by clicking on the statistics folder of interest (e.g. Monday, Tuesday, Wednesday, etc.), and opening the file of interest.

A Statistics Parser can be downloaded from the bottom of the Element Manager Statistics Web Page. This parser is capable of parsing and displaying Binary Statistics files on the local PC hard disk. Users must download the Statistics files to be parsed and store them in a common location on the local hard disk for parsing.

The raw statistics data file is also available for viewing by clicking to the statistics folder (e.g. Monday, Tuesday, Wednesday, etc.) of interest and opening the raw statistics data file. This is of limited usefulness however, as there is no header or descriptive information in these files.


8-2 68P81001Y98-I 04/25/2011

Statistics

Statistics, Log, & Config Files

Downloading Statistics The various types of statistics files available for download are discussed above. In addition to the files discussed above, a compressed and zipped statistics file containing statistics data (and raw statistics data) for the most recent four weeks prior to the date indicated by its filename is available for download from the Index of/Statistics directory. The filename format is stats.<date>.gz. For example, the file named “stats.25May2003.gz” contains the statistics and raw statistics data for the most recent four weeks prior to 3:00 am of May 25, 2003. This file is updated with the most recent four weeks of data every Sunday at 3:00 am local time.

This file can be downloaded from the ASP Element Manager by right clicking on the filename and saving it to the PC hard drive.


04/25/2011 68P81001Y98-I 8-3

Statistics


Statistics Description The various statistics collected by the ASP are given below.

Table 8-1 Statistics Descriptions

Name Description Type

ASG_TOT_ORIG_CANumber of Call Alerts originated by the DM Users served by the ASP. Call Alerts originated by DM Users are counted regardless of who the target is.

Counter

ASG_TOT_CANumber of Call Alert targeted the DM Users served by the ASP. Call Alerts targeted to a DM User are counted regardless of who the originator is.

Counter

ASG_TOT_ORIG_PCNumber of Private Calls Originated by the DM Users served by the ASP. Private Calls originated by DM Users are counted regardless of who the target is.

Counter

ASG_TOT_PCNumber of Private Calls Targeted to DM Users served by the ASP. Private Calls targeted to DM Users are counted regardless of who the originator is.

Counter

ASG_TOT_ORIG_GC Number of Group Calls originated by the DM Users served by the ASP. Counter

ASG_TOT_GCNumber of Group Calls Targeted to the DM Users served by the ASP. Group calls targeted to DM Users are counted regardless of who the originator is.

Counter

ASG_TOT_ORIG_UDGC Number of User Defined Group Calls originated by the DM User served by the ASP. Counter

ASG_TOT_UDGC Number of User Defined Group Calls originated by the DM Users served by the ASP. Counter

ASG_TOT_UDGC_MEM Total number of UDGC Members participating in UDGC calls for this Stats period Counter

ASG_TOT_DM2DM_PC Total number of private call involving only DM Users served by the ASP. Counter

ASG_TOT_FAIL_CA Total number of call alerts that failed. Counter

ASG_TOT_FAIL_PC Total number of private calls that failed. Counter

ASG_TOT_FAIL_GC Total number of group calls that failed. Counter

ASG_TOT_DM2DM_CA Total number of call alerts involving only DM Users served by the ASP. Counter

ASG_TOT_PC_CALL_DUR Total duration of private calls. Counter

ASG_MAX_PC_CALL_DUR Maximum private call duration for this stats period Counter

ASG_TOT_GC_CALL_DUR Total duration of group calls. Counter


8-4 68P81001Y98-I 04/25/2011

Statistics


ASG_MAX_GC_CALL_DUR Maximum group call duration for this stats period Counter

ASG_TOT_UDGC_CALL_DUR Total duration of user defined group calls. Counter

ASG_MAX_UDGC_CALL_DUR Maximum UDGC call duration for this stats period Counter

ASG_TOT_GC_IP_MEM Total number of DM Users involved in the group call, this is calculated by summing the number of talkgroup members for each group call.

Counter

ASG_MAX_GC_IP_MEM Maximum number of DM users involved in a group call during this stats period Counter

Name Description Type


04/25/2011 68P81001Y98-I 8-5

Statistics


Figure 8-1 Statistics Screen


8-6 68P81001Y98-I 04/25/2011

Chapter 9

Alarms and Events

Viewing Alarms & Events

Alarms are viewed in real time by clicking on the "Alarms" button on the ASP Element Manager Welcome Page. The Alarms’ button is located at the bottom of the screen.

Events are viewed in real time by clicking on the "Events" button on the ASP Element Manager Welcome Page. The "Events" button is located at the bottom of the screen.

The NDM R01.2 system supports forwarding alarms/events to a Netcool server. Please consult the MOP for instructions on how to configure the Netcool server forwarding feature.


04/25/2011 68P81001Y98-I 9-1

Alarms and Events

Figure 9-1 Alarm Screen


9-2 68P81001Y98-I 04/25/2011

Alarms and Events

Alarms Description Descriptions of the various alarms generated by the ASP for the T1, DAP, I/O boards, and Host boards are given below.

Table 9-1 ASP Alarm Codes and Descriptions

Device TypeAlarm Code Alarm Text Category Severity Additional Text Info

T1 Link 1 T1 Loss of Signal Failure communication critical The physical T1 link

<span> is down.

T1 Link 1 T1 Loss of Signal Failure communication clear The physical T1 link

<span> is up.

DAP Link 3 LAPD Link Failure communication critical DAP link failure for <id>

DAP Link 3 LAPD Link Failure communication clear DAP link established for <id>

Host Board 3 LAPD Link Failure communication critical DAP link failure for <id>

Host Board 3 LAPD Link Failure communication clear DAP link established for <id>

Host Board 9 DAP Protocol Failure communication critical <none>

Host Board 9 DAP Protocol Failure communication clear <none>


04/25/2011 68P81001Y98-I 9-3

Alarms and Events

N O T E S . . .


9-4 68P81001Y98-I 04/25/2011

Chapter 10

Troubleshooting & Maintenance

Troubleshooting 10

Important In the event of an ASP system failure, contact the Motorola Customer Network Resolution Center (CNRC) immediately.

! WARNING

Do not attempt to install ASP software onto the ASP under any circumstances without consulting CNRC first!

Before Calling... Collect the following information prior to contacting Motorola Customer Network Resolution Center (CNRC) to help minimize down-time:• Location of the system• Date the product was put in service• PC Operating System• NetDispatch Messenger and ASP Software version• State of NetDispatch Messenger (e.g. online, offline and link status)• Date and Time problem occurred• Symptoms of the problems:

• Users Impacted (DM Users, Subscriber Units, or both, associated IMEIs/UFMIs, one user or multiple users).

• Logs, Statistics & Billing at the time problem occurred.• If the problem can be reproduced• Any unusual circumstances contributing to the problem


04/25/2011 68P81001Y98-I 10-1

Troubleshooting & Maintenance

Troubleshooting

CNRC Telephone Numbers

1-800-499-6477 in United States of America

1-847-725-4555 outside of the USA

Backing up the Configurable NDM Parameters

From the NDM Element Manager Statistics Web interface, download the ndm_db_archive.<date>.gz file periodically and save in a secure location. In the event of a catastrophic NDM failure, this file contains all the user and customer configurable parameters required to restore the NDM system from FRU hardware.

Please refer to the NDM MOP for additional information and troubleshooting tips regarding the NDM product and it’s components.


10-2 68P81001Y98-I 04/25/2011

Appendix A

Acronyms and Computer Software Copyright

Acronym Definition Description

APD Advance Packet Duplicator Duplicates dispatch voice packets for distribution to multiple cells involved in a call.

ASP Advanced Services Platform This is the hardware platform for the NetDispatch Messenger.

ASP Element Manager

Advanced Services Platform Element Manager

This it the Element Manger that runs on the ASP. There are two Element Managers on the iDEN. One runs on the ASP (ASP Element Manager), the other runs on the Controller of the iDEN and is known as the "Element Manager".

BSC Base Station ControlleriDEN system component - responsible for forwarding NDM SNMP traffic between the NDM site(s) and the OMC.

CDR Call Detail Record

Contains information about the network facilities and services used for processed calls. Mobile Originated, Mobile Terminated, and Call Forwarding CDRs are produced for mobile subscribers. Supplementary services are captured in separate CDRs.

CNRC Customer Network Resolution Center Motorola Technical Support for iDEN operators.

CPU Central Processing Unit Microprocessor that forms the central core of a computing platform.

DACS DACS T1/E1 switch card that terminates the NDM EBTS site(s) in the iDEN MSO


04/25/2011 68P81001Y98-I A-1

DAP Dispatch Application Processor

The brain of the iDEN dispatch function. Provides the communications processing and database management functions for coordination and control of dispatch communications.

DLCI Data Link Control/Connection Identifier Target identifier for end equipment used by the Frame Relay protocols

DM Dispatch MessengerTMThis is the user application which runs on the DM users PC. This application is downloaded to a PC and is operated from the PC.

DM User Dispatch MessengerTM UserThe DM User uses the DM application from a PC.

DNS Domain Name Server Network servers dedicated to translating network names to numeric IP addresses

EBTS Enhanced Base Transceiver System

The iDEN Radio Frequency (RF) transmission/receiver site consisting of a set of radio transceivers, controlling equipment and antennas; provides radio coverage for a specific geographic area.

ELIU EBTS Line Interface Unit The communications interface between the MSO and the EBTS.

EM Element ManagerThe Element Managers on the NDM-ASP. The Element Manager is the interface for the NDM configuration and provisioning.

iBSC iDEN Base Station Controller New BSC hardware in the iDEN network with SR12.0.

iDEN Integrated Digital Enhanced Network

iPP a proprietary protocol used at the provisioning interfaces on iDEN Network. It is an application layer protocol which supports secure transmit of XML pages containing provisioning information.

iHLR iDEN Home Location Register

A database oriented processing entity which contains the service authorization and personality parameter databases and performs mobility management services for a set of mobile stations which are administratively associated with it.

iPP iDEN Provisioning ProtocolProtocol defined by Motorola to format/send provisioning requests to iDEN provisioning equipment such as the iHLR.

iVPU iDEN Voice Processing Unit New iDEN NE with SR14.0



A-2 68P81001Y98-I 04/25/2011

IMSI International Mobile Station IdentifierNormally fifteen BCD digits. Parts of the number are assigned by Motorola and parts are provided by the service providers.

IMEI International Mobile Equipment Identifier

An IMEI is a unique number identifying one and only one MS. The number is assigned to, and burned into, the MS as part of the manufacturing process.

IP Internet Protocol A method or protocol by which data is sent from one computer to another on the Internet.

LAN Local Area Network A geographically localized network consisting of both hardware and software.

LAPD Link Access Procedure

Link Access Procedure on the D-channel is a connection based Data Link Layer Protocol. On iDEN, LAPD is used, for example, between DAP - EBTS.

MOBIS Motorola ABIS Motorola adaptation of the GSN A.bis protocol.

MS Mobile Station A Harmony Subscriber Unit. On a iDEN, this is a mobile or portable radio.

MSC Mobile Switching Center

Provides interconnection services among wireless subscriber stations and the public switched telephone network via one or more base stations under its control. It performs switching, routing, and call control functions along with charging, accounting, and interworking with the public switched telephone networks.

MSIN Mobile Station Identification NumberA part of the E.212 IMSI identifying the mobile station within its home network. See ITU-T Recommendation E.212.

MSO Mobile Switching Office

For iDEN, the MSO includes the Power and Control Cabinets. The Control Cabinets contains the interconnect and dispatch subsystems.

NDAP N number of DAPsNDAP is used to increase the dispatch throughput of an MSO. Up to six DAPs can run in parallel.

NDM NetDispatch Messenger NetDispatch Messenger System

NTP Network Time ProtocolProtocol designed to permit computing equipment to synchronize clocks with a trusted server via an IP network



04/25/2011 68P81001Y98-I A-3

PLIU PSTN Line Interface Unit The communications interface between the MSO and the PSTN.

PMC PCI Mezzanine Card This is the I/O card on the ASP.

PTx AS Push To X Application Server Support Configuration Services for DM User using Configuration Server.

RF Radio FrequencyThe electromagnetic energy wavelengths usually between 500 kHz and 300 GHz. The audio and light range frequencies.

RNC Regional Network Code

A globally unique system ID. When th eMS does an IMEI registration, the MS takes the first RNC broadcast in the System Info and stores it as the home RNC.

SMTP Simple Mail Transfer Protocol Protocol designed for the transport of text and content based e-mail messages

SNMP Simple Network Management Protocol Protocol developed to manage remotely, via an IP network, computing equipment

TCP Transmission Control Protocol

The suite of protocols developed and used by DAR PA and the US DOD. They build up to Layer Four of the ISO OSI model, but there is no direct correspondence layer for layer.

UDGC User Defined Group Call An NDM call type allowing multiple users to dynamically participate in a common call

UDP User Datagram Protocol

The IP standard protocol that allows an application program on one machine to send a datagram to another application program on another machine.

UFMI Universal Fleet Member Identifier Identifies a Subscriber within a Fleet within an Urban

URL Uniform Resource Locator

A dynamically created group call where DM User or Mobile Subscribers can be dynamically added or removed from a group call at the group call originator’s discretion. The group call originator must be a DM User.

VLR Visitor Location Register

A register based mobility management entity which manages call processing and location tracking for mobile stations operating in its radio subnetwork.



A-4 68P81001Y98-I 04/25/2011

NDM 1.2 Computer Software Copyright

Below is the NDM Copyright Notice Information:

Computer Software Copyrights

The Motorola and 3rd Party supplied Software (SW) products described in this documentation may include copyrighted Motorola and other 3rd Party supplied computer programs stored in semiconductor memories or other media. Laws in the United States and other countries preserve for Motorola and other 3rd Party supplied SW certain exclusive rights for copyrighted computer programs, including the exclusive right to copy or reproduce in any form the copyrighted computer program. Accordingly, any copyrighted Motorola or other 3rd Party supplied SW computer programs contained in the Motorola products described in this documentation may not be copied (reverse engineered) or reproduced in any manner without the express written permission of Motorola or the 3rd Party SW supplier. 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 or other 3rd Party supplied SW, except for the normal non-exclusive, royalty free license to use that arises by operation of law in the sale of a product.

VRT Voice Routing TaskInternal NDM task responsible for routing and duplicating dispatch audio voice for NDM clients.

XCDR Transcoder Transforms signals from one type of digital representation to another.

WAN Wide Area Network

A network which covers a larger geographical area than a LAN and where telecommunications links are implemented, normally leased from the appropriate Private Telecommunications Operator. Example of WANs includes packet switched networks, public data networks and Value Added Networks.



04/25/2011 68P81001Y98-I A-5

* May contain purchased SW and Open Source SW which may be subject to a license fee.

VENDOR COPYRIGHT Douglas Schmidt * Copyright 2003 All Rights Reserved InstallShield Corp Copyright 2004 All Rights Reserved Jakarta * Copyright 2004 All Rights Reserved Microsoft * Copyright 2003, 2004

All Rights Reserved Open Source * Copyright 1999 All Rights Reserved Redhat * Copyright 2003, 2004

All Rights Reserved Stardock Copyright 2004 All Rights Reserved SUN Microsystems * Copyright 2004 All Rights Reserved Tarma Copyright 2004 All Rights Reserved TimesTen Copyright 2005 All Rights Reserved


A-6 68P81001Y98-I 04/25/2011

Appendix B

RR Cause Values

Value Description

%0000 0000 Normal Release

%0000 0001 Abnormal release, unspecified

%0000 0010 Abnormal release, channel unacceptable

%0000 0011 abnormal release, timer expiry

%0000 0100 abnormal release, no activity on the radio path

%0000 0101 Preemptive release

0100 0001 Call already cleared

0101 1111 Invalid message, unspecified

0110 0001 Message type non-existent or not implemented

0110 0010 Message type not compatible with state or not implemented

0110 0100 Invalid information element

0110 0101 Not used

0110 1111 Protocol error, unspecified

1000 0000 Normal end of call

1000 0010 Call aborted at user’s request

1000 0100 Not authorized to initiate call

1000 0101 Requested service not available

1000 1000 Unrecognized Individual ID

1000 1001 Registration required

1001 0000 Incorrect Group ID

1010 0000 Call target non-existent

1010 0001 Insufficient number of call targets


04/25/2011 68P81001Y98-I B-7

1010 0010 Call target busy in dispatch call

1010 0011 Call target busy in packet data

1010 0100 Call target not authorized to receive call

1010 0101 Call target not reachable

1100 0000 Call target not responding

1100 0001 Required resources not available

1100 0010 Temporary call failure

1100 0100 Network out of order

1111 1111 Requested Service not available

all others Reserved

Value Description


B-8 68P81001Y98-I 04/25/2011

This Page Intentionally Left Blank.

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. © 2011 Motorola Solutions, Inc. All rights reserved.

68P81001Y98-I

iden™ netdispatch messenger (ndm) administration manual

Documents