MD110 DNA Tech Guide Help

MD110 Dynamic Network Administration
Technical Guide
Version 5
Contents
KEY INFORMATION.............................................................................................................. 15 What is D.N.A...................................................................................................................... 15 Compatibility .................................................................................................................. 15 D.N.A. Interworking ........................................................................................................... 16 D.N.A. Server ................................................................................................................. 17 What You Will Find In This Help Guide.......................................................................... 17 Related Publications ....................................................................................................... 18 Conventions Used in This Guide.................................................................................... 18 Using Help............................................................................................................................ 18 Tips for using Help ......................................................................................................... 18 Printing Help................................................................................................................... 18 Glossary................................................................................................................................ 19 APPLICATIONS ....................................................................................................................... 22 Description of Applications ................................................................................................ 22 Limitations ........................................................................................................................... 23 PPM Lite......................................................................................................................... 23 Directory Browser .......................................................................................................... 23 OneBox Mailbox Integration.............................................................................................. 23 Integration of OneBox and D.N.A.................................................................................. 24 OneBox Controls...................................................................................................... 24 Automatic Mailbox Creation/Deletion..................................................................... 25 OneBox Database Synchronization.......................................................................... 25 OneBox Compatibility with Other Network Elements................................................... 25 OneBox Integration with D.N.A. Voice System Interface....................................... 25 Using Diversion Reasons ......................................................................................... 26 OneBox Intercept Capabilities ................................................................................. 26 Compatibility with Other Network Elements ................................................................. 27 D.N.A. Application Suite - MD110..................................................................................... 27 Dial By Name Directory................................................................................................. 27 Compatibility with Other Network Elements ................................................................. 27 Personal Screen Call ........................................................................................................... 28 PSC integration with D.N.A. RDS ................................................................................. 29
2
Technical Guide
PSC 1.1..................................................................................................................... 30 PSC 2.0..................................................................................................................... 31 Compatibility with Other Network Elements........................................................... 31 PSC Server...................................................................................................................... 31 Compatibility with Other Network Elements........................................................... 31 Application Link.................................................................................................................. 32 General Operations ......................................................................................................... 32 Application Link and CCA............................................................................................. 32 Application Link and PSC.............................................................................................. 32 Compatibility with Other Network Elements ................................................................. 33 Time System Interface ........................................................................................................ 33 Compatibility with Other Network Elements........................................................... 33 CCM/D.N.A. Extension Manager Integration.................................................................. 34 Compatibility with Other Network Elements........................................................... 34 CCA/D.N.A. Directory Manager Integration ................................................................... 35 Compatibility with Other Network Elements........................................................... 35 Next CC/D.N.A. Integration............................................................................................... 36 Compatibility with Other Network Elements........................................................... 36 LDAP.................................................................................................................................... 37 Compatibility with Other Network Elements........................................................... 37 Other Interfaces .................................................................................................................. 37 Directory Link ................................................................................................................ 37 Extension Link................................................................................................................ 38 D.N.A. CAAPI................................................................................................................ 38 Change Log..................................................................................................................... 38 D.N.A. CTI ..................................................................................................................... 39 Mobile Executive ................................................................................................................. 39 WAP Gateway ................................................................................................................ 39 Phone Setup .................................................................................................................... 40 R320s Phone setup for D.N.A. WAP....................................................................... 40 SNMP Agent ........................................................................................................................ 42 The Monitored Objects ................................................................................................... 43 as_dmi.exe................................................................................................................ 43 asdmi.exe.................................................................................................................. 43 CIMgr & Win32sl .................................................................................................... 43 NT SNMP ................................................................................................................ 43 Dmi2snmp................................................................................................................ 43 Remote Data Monitor ......................................................................................................... 44
3
Visitor Registration............................................................................................................. 45 PREINSTALLATION............................................................................................................... 45 About Pre-Installation ........................................................................................................ 45 Pre-Installation Meeting ................................................................................................. 45 Addressing Important Issues .................................................................................... 45 Pre-installation Checklist ......................................................................................... 45 MD110 Hardware Requirements....................................................................................... 46 REQUIREMENTS .................................................................................................................... 46 Configuration Options ........................................................................................................ 46 Single Server................................................................................................................... 46 Single Server with Operator Workstation VIP ............................................................... 47 Multiple Servers ............................................................................................................. 48 LDAP Servers................................................................................................................. 49 Basic Requirements............................................................................................................. 50 Server.............................................................................................................................. 50 Specific Requirements ............................................................................................. 51 Minimum Recommendations ................................................................................... 51 Client PC......................................................................................................................... 52 Specific requirements............................................................................................... 52 Additional Hardware Options......................................................................................... 52 Hard Disk Requirements.................................................................................................... 53 Recommendation ............................................................................................................ 53 Server Disk Space Requirements....................................................................................... 53 Notes............................................................................................................................... 54 Client Disk Space Requirements........................................................................................ 55 Notes............................................................................................................................... 56 Software Requirements....................................................................................................... 56 Windows......................................................................................................................... 56 SQL Server/MSDE ......................................................................................................... 57 Excel ............................................................................................................................... 57 Internet Tools.................................................................................................................. 57 CONNECTIONS........................................................................................................................ 57 Connection Between Server PC and Client PC ................................................................ 57 Client/MD110 Connections for Operator Workstation ................................................... 58
4
Technical Guide
Server/MD110 Connection for Operator Workstation.................................................... 58 Configuration Management Hardware Connections....................................................... 59 Hardware Connections for Extension Manager............................................................... 60 CHECKLISTS ........................................................................................................................... 62 Installation Checklists......................................................................................................... 62 Using the Checklists ....................................................................................................... 62 For More Information .............................................................................................. 62 Submit Your Comments........................................................................................... 62 Pre-installation Checklist ................................................................................................... 62 Installation Profile .......................................................................................................... 62 Installation Component Verification .............................................................................. 63 Installation Product Identification .................................................................................. 63 Account Strategy ................................................................................................................. 63 Check Hardware before You Start.................................................................................. 64 OS AND DATABASE INSTALLATION ................................................................................ 64 NT 4.0 Server....................................................................................................................... 64 NT 4.0 Workstation............................................................................................................. 68 Check Hardware before You Start.................................................................................. 68 Installing Windows NT from a Local CD-ROM Drive.................................................. 69 Installing Windows NT from a Network Drive .............................................................. 69 Date and Time Properties......................................................................................... 70 Display Properties .................................................................................................... 70 Copying Files and Restarting ................................................................................... 70 Regional Settings Properties .................................................................................... 71 NT Workstation PC Description .............................................................................. 71 System Performance Settings................................................................................... 71 System Startup/Shutdown Settings .......................................................................... 71 Install NT Service Packs .......................................................................................... 71 Display All File Extensions ..................................................................................... 72 Enable Disk Performance Counters ......................................................................... 72 Install Microsoft Excel ................................................................................................... 72 Reboot and Verify Setup Success................................................................................... 72 Windows 2000 Upgrade...................................................................................................... 72 Installing Windows 2000 from a Local CD-ROM Drive ............................................... 73 Installing Windows 2000 from a Network Drive ........................................................... 73 SQL Server .......................................................................................................................... 73
Installation ...................................................................................................................... 74 Post-installation .............................................................................................................. 74 Security........................................................................................................................... 74 Unattended SQL Server Installation............................................................................... 74 Database Upsizing .......................................................................................................... 75 Memory .......................................................................................................................... 75 SNMP Master Agent ........................................................................................................... 75 Windows NT................................................................................................................... 75 Windows 2000................................................................................................................ 76 D.N.A. INSTALLATION .......................................................................................................... 77 About Installation................................................................................................................ 77 Hardware Connections.................................................................................................... 77 Software Installation....................................................................................................... 77 Application Suite Installation............................................................................................. 77 Installation Features........................................................................................................ 78 Silent Installation ..................................................................................................... 78 Auto-Run.................................................................................................................. 78 Unattended SQL Server Installation............................................................................... 78 Pre-Configured System................................................................................................... 79 License ..................................................................................................................... 79 User Names and Privileges ...................................................................................... 79 MD110 Communications ......................................................................................... 79 GICI Configurations................................................................................................. 79 MD110 Data Synchronization.................................................................................. 79 User-defined Fields for Directory Manager ............................................................. 79 Configuration File Parameters ................................................................................. 80 Installation Dialog Explanations........................................................................................ 82 New Installation Dialogs (Server) .................................................................................. 82 New Installation Dialogs (Client)................................................................................... 84 Re-Installation Dialogs ................................................................................................... 85 Server Installation............................................................................................................... 85 Auto-Run Installation ..................................................................................................... 86 Taskbar Installation ........................................................................................................ 86 Server Installation Options ............................................................................................. 86 Add Components ............................................................................................................ 87 Upsizing Server Components................................................................................... 87 Stand-alone Installation .................................................................................................. 88
6
Technical Guide
Client Installation................................................................................................................ 88 Auto-Run Installation ..................................................................................................... 88 Taskbar Installation ........................................................................................................ 88 Client Installation Options.............................................................................................. 88 Silent Installation ................................................................................................................ 89 Modifying the Setup (dnasuite.ini) File.......................................................................... 90 Installation Procedure ..................................................................................................... 90 Using the Setup Command....................................................................................... 91 Numbering Plan Manager.................................................................................................. 91 Server Installation........................................................................................................... 91 Client Installation ........................................................................................................... 91 Installation Procedure ..................................................................................................... 91 Upgrade D.N.A. Application Suite................................................................................. 92 PPM Lite .............................................................................................................................. 92 Installing with Auto-Run ................................................................................................ 92 Installation Options......................................................................................................... 93 Upgrade PPM Lite .......................................................................................................... 93 Directory Browser............................................................................................................... 94 Installation and Uninstall................................................................................................ 94 Installing with Auto-Run ................................................................................................ 94 Installation Procedure ..................................................................................................... 94 Client Installation ........................................................................................................... 95 Directory Browser Configuration...................................................................................... 96 Mobile Executive ................................................................................................................. 96 Installing with Auto-Run ................................................................................................ 97 Installation Options......................................................................................................... 97 Post Installation Setup .................................................................................................... 98 Windows NT ............................................................................................................ 98 Windows 2000 ......................................................................................................... 98 Outlook Integration ............................................................................................................ 98 User ID instead of Computer UDF................................................................................. 99 Troubleshooting.............................................................................................................. 99 SYSTEM PERFORMANCE .................................................................................................. 100 Performance Enhancements............................................................................................. 100
Memory .............................................................................................................................. 100 Operator Workstation Supervisor................................................................................... 101 RDS Performance.............................................................................................................. 102 LDB Integrity Check Feature (RDS 2.x) ...................................................................... 102 Reduce I/O Completion Ports in Large Systems (RDS2.1).......................................... 102 System Requirements............................................................................................. 103 Enable/Disable Incremental LDB Updates from DMG................................................ 103 Configure RDS to Use Fewer SQL Connections.......................................................... 104 INSTALLATION PROBLEMS ............................................................................................. 104 Log Files ............................................................................................................................. 104 Server Installation Logs................................................................................................ 104 Client Installation Logs................................................................................................. 104 Event Log Messages .......................................................................................................... 104 D.N.A. SERVER ...................................................................................................................... 112 Facilities and Services ....................................................................................................... 112 Administrative Tools......................................................................................................... 113 Changing Users, Servers, and Passwords ....................................................................... 115 Registry .............................................................................................................................. 116 Registry Settings........................................................................................................... 116 Operator Workstation Registry Settings ................................................................ 116 Server Identification ..................................................................................................... 117 Maintenance....................................................................................................................... 117 SQL Database ............................................................................................................... 117 Database Upsizing.................................................................................................. 117 Tasks ...................................................................................................................... 117 Transaction Log ..................................................................................................... 117 The CleanDB Routine ............................................................................................ 117 Logging Facilities Server.............................................................................................. 118 Ovwin.log File........................................................................................................ 118 Short Message Service ...................................................................................................... 118 Limitations.................................................................................................................... 118 Local Database Compression ........................................................................................... 118 MAINTENANCE..................................................................................................................... 119 Archival Backup................................................................................................................ 119
Technical Guide
Temporary Workspace.................................................................................................. 120 Automatic Extraction........................................................................................................ 120 Performance Data Manager Operations........................................................................ 120 Two Ways To Start The Extraction Process................................................................. 120 The Data Extraction Command .................................................................................... 121 Clock Synchronization ................................................................................................. 121 Extraction Process ........................................................................................................ 121 The First Extraction after PMG Installation........................................................... 121 Data Collected Prior to PMG Installation .............................................................. 121 Issuing MML Commands ...................................................................................... 122 Skip Nodes For Polling................................................................................................. 122 Extend Polling Time..................................................................................................... 122 Presentation Manager....................................................................................................... 122 Operational Requirements ............................................................................................ 122 Traffic Measurement Reports ....................................................................................... 122 Preserving Edited Reports ............................................................................................ 123 Database Utility ................................................................................................................. 123 Options.......................................................................................................................... 123 Capacity and Limitations.............................................................................................. 123 TROUBLESHOOTING .......................................................................................................... 124 Technical Support ............................................................................................................. 124 Before Contacting Technical Support .......................................................................... 124 Reporting Your Problem.................................................................................................. 124 Problem Description ..................................................................................................... 125 MD110.......................................................................................................................... 125 Operating System Information (mark all that apply).................................................... 125 Configuration................................................................................................................ 125 Network Protocol (mark all that apply) ........................................................................ 125 PC ................................................................................................................................. 125 D.N.A. Applications ..................................................................................................... 126 Event Viewer...................................................................................................................... 126 Error Messages ............................................................................................................. 126 Error Messages for SNMP Agent .......................................................................... 129 Directory Manager............................................................................................................ 131
Extension Manager ........................................................................................................... 133 Operator Workstation ...................................................................................................... 137 Performance Data Manager............................................................................................. 137 Performance Presentation Manager................................................................................ 139 Essential Requirements................................................................................................. 140 Report Limitations ........................................................................................................ 140 General PPM Problems................................................................................................. 140 Mobile Executive ............................................................................................................... 141 APPLICATION DATA ........................................................................................................... 141 Report Generation ............................................................................................................ 141 Directory Manager Database Organization.................................................................... 142 Extension Manager Database Organization ................................................................... 147 PDM Database Organization ........................................................................................... 160 SQL Server Data Volume Estimates ............................................................................ 161 Operator Workstation Data ............................................................................................. 161 Directory Assistance Databases.................................................................................... 161 Operator Workstation Configuration............................................................................ 161 How Settings Files are Created .............................................................................. 161 Permissions for Changing User and Directory Settings......................................... 161 Where to Find Settings Files .................................................................................. 161 Operator Console Settings...................................................................................... 162 DIRECTORY STRUCTURES ............................................................................................... 162 D.N.A. Directory Structures............................................................................................. 162 Directory Manager (Server)............................................................................................. 162 Extension Manager (Server) ............................................................................................ 163 Administrative Tools (Server).......................................................................................... 164 Numbering Plan Manager ................................................................................................ 165 Operator Workstation (Server) ....................................................................................... 165 Performance Manager (Server) ....................................................................................... 166 Directory Browser............................................................................................................. 166 Directory Manager (Client).............................................................................................. 167 Extension Manager (Client) ............................................................................................. 167
10
Technical Guide
Administrative Tools (Client)........................................................................................... 168 Operator Workstation (Client) ........................................................................................ 168 Performance Manager (Client) ........................................................................................ 169 MML COMMANDS................................................................................................................ 170 Extension Manager ........................................................................................................... 170 MD Support Utility ........................................................................................................... 171 Numbering Plan Manager................................................................................................ 172 Performance Data Manager............................................................................................. 173 MD Support Command Line Synchronization .............................................................. 173 Command Line Syntax ................................................................................................. 174 Supported MD110 Features ................................................................................... 174 FREQUENTLY ASK QUESTIONS ...................................................................................... 176 Directory Manager............................................................................................................ 176 D.N.A./CCM Server .......................................................................................................... 176 Operator Workstation ...................................................................................................... 177 Digital Telephone Set............................................................................................. 179 Operator Workstation LAN.................................................................................... 179 Remote Data Server .......................................................................................................... 180 Serial Communications Server ........................................................................................ 181 Performance Data Manager............................................................................................. 181 D.N.A. Application Suite .................................................................................................. 183 MD110 BC ................................................................................................................... 183 Registry......................................................................................................................... 185 SQL Server ................................................................................................................... 185 ClockSync..................................................................................................................... 186 SNMP ........................................................................................................................... 186 CONFIGURATION ................................................................................................................ 187 Networking (SNMP) Access Agent .................................................................................. 187 Features in Agent.......................................................................................................... 189 TCP/IP Protocols and Port Number Assignments.................................................. 190 Customers .......................................................................................................................... 192 Service Provider Customer Groups .............................................................................. 192
11
Configuring Type I Customers............................................................................... 192 Configuring Type II Customers ............................................................................. 193 D.N.A. Server..................................................................................................................... 193 Serial Communication Server .......................................................................................... 195 OPERATOR WORKSTATION............................................................................................. 195 NCOP-OWS....................................................................................................................... 195 Definitions .................................................................................................................... 196 Service Provider Customer Groups .............................................................................. 196 Configuring Type I customers ...................................................................................... 197 Configuring Type II customers..................................................................................... 198 Configuring the SP DNA Server............................................................................ 198 Configuring the NCOP-OWS ................................................................................ 199 Configuring the SCS .............................................................................................. 200 Performance.................................................................................................................. 201 E-mail Integration............................................................................................................. 201 Operator Workstation E-mail Requirements ................................................................ 201 Loading the MAPI library...................................................................................... 201 Performing a Null Logon ....................................................................................... 202 Obtaining an E-mail Address ................................................................................. 202 E-mail Related D.N.A. System Administration............................................................ 202 Directory Configuration ......................................................................................... 202 RDS Configuration................................................................................................. 202 System Maintenance .............................................................................................. 202 Troubleshooting............................................................................................................ 203 Troubleshooting Operator Workstation E-mail with Performance Monitor .......... 203 Troubleshooting Operator Workstation E-mail with Remote Data Monitor.......... 203 VSI AND TSS........................................................................................................................... 204 Voice System Interface...................................................................................................... 204 Setting Up Communications and Configuration Parameters ........................................ 204 The VSI Protocol .......................................................................................................... 204 Capacities and Limitations ........................................................................................... 205 Time System Interface ...................................................................................................... 206 Interface ........................................................................................................................ 206 Logical Interface .................................................................................................... 206 Protocols ....................................................................................................................... 206 Finnish Character Coding ...................................................................................... 206 Message Format ..................................................................................................... 206 FLEXIM Protocol......................................................................................................... 207
12
Technical Guide
Messages sent from FLEXIM to D.N.A. Time System Interface .......................... 208 Messages sent from D.N.A. Time System Interface to FLEXIM .......................... 212 General Protocol ........................................................................................................... 213 Login/logout message ............................................................................................ 213 Messages sent from General Time Monitoring System to Time System Interface 214 Messages sent from Time System Interface to General Time Monitoring System 216 CTR Protocol................................................................................................................ 217 Messages sent from the CTR Time Monitoring System to D.N.A. ....................... 217 Messages sent from Time System Interface to CTR Time Monitoring System..... 219 ESMI Protocol .............................................................................................................. 219 Messages sent from ESMI Time System To D.N.A. Time System Interface........ 219 Messages sent from D.N.A. Time System Interface to ESMI Time System................ 221 TIMECON Protocol ..................................................................................................... 222 Stamping Message ................................................................................................. 222 Return Time ........................................................................................................... 222 Clock Message ....................................................................................................... 222 Exchange Interface ....................................................................................................... 223 Message Types ................................................................................................................... 223 IVR/Voice System to VSI Messages................................................................................. 223 IVR/Voice System from VSI Messages............................................................................ 225 APPENDIX............................................................................................................................... 227 Busy PDM Data Table ...................................................................................................... 227 PDM C_bell Data Table.................................................................................................... 229 PDM Code_r Data Table .................................................................................................. 231 PDM Code_s Data Table .................................................................................................. 233 PDM Confer Data Table................................................................................................... 235 PDM Datext Data Table ................................................................................................... 237 PDM Dialdy Data Table ................................................................................................... 239 PDM Cordless Extension Common Fixed Part Data Table .......................................... 241 PDM Extens Data Table ................................................................................................... 243 PDM Keyc_r Data Table .................................................................................................. 245 PDM Keyc_s Data Table .................................................................................................. 247 PDM Measinfo Data Table............................................................................................... 249 PDM Modgrp Data Table................................................................................................. 251 PDM Opindi Data Table................................................................................................... 253
13
PDM Opcorg Data Table.................................................................................................. 256 PDM Opmann Data Table................................................................................................ 258 PDM Pagext Data Table ................................................................................................... 260 PDM Pagsar Data Table................................................................................................... 262 PDM Pbxgrp Data Table .................................................................................................. 264 PDM Pcmlin Data Table................................................................................................... 266 PDM Roubwy Data Table................................................................................................. 268 PDM Rouddi Data Table .................................................................................................. 270 PDM Roudio Data Table .................................................................................................. 272 PDM Rouinc Data Table................................................................................................... 274 PDM Rouout Data Table .................................................................................................. 276 PDM Tone_r Data Table .................................................................................................. 278 PDM Trunks Data Table .................................................................................................. 280 PDM Cordless Extensions Mobility Table ...................................................................... 282 PDM Cordless Extensions Fixed Part Table................................................................... 284 PDM IP Extensions Table................................................................................................. 286 Remote Data Server .......................................................................................................... 287 Security Data Server ......................................................................................................... 287 System Clock Synchronization......................................................................................... 287 To Generate Reports Using Access.................................................................................. 287 To Log Off.......................................................................................................................... 288 To Logon ............................................................................................................................ 288 PPM Error Messages ........................................................................................................ 288
14
Technical Guide
Key Information
What is D.N.A.
Congratulations on your selection of Ericsson's Dynamic Network Architecture (D.N.A.) application suite as your MD110 PBX call management system. The D.N.A. Application Suite is a comprehensive family of graphical PC-based programs and utilities supporting MD110 PBX operation and administration. D.N.A. provides PABX operational support in the following major areas = = = = = = Operator Call Management Extension Management Directory Management High-level Telecommunications Network Supervision Traffic Measurement and Reporting Numbering Plan Management
Compatibility
This release of the D.N.A. Application Suite is compatible with: = AppLink 3.0 or 4.0 = CT Adapter, ZAT 505 120/1 = D.N.A. Access Agent software and hardware as specified in Ordering Information for Access Agent and SNMP applications = Extender Keyboard, KDT 252 001/02 = MD110 releases BC9, BC10, and BC11. = Microsoft Excel 97 or Excel 2000 = Microsoft Internet Explorer 4.0 and 5.0 = Microsoft Internet Information Server 4.0 and 5.0 = Microsoft SQL Server Version 7.0 or MSDE = Microsoft Windows NT Server Version 4.0 and Windows 2000 = Microsoft Windows NT Workstation Version 4.0
15
D.N.A. Interworking
D.N.A. is compatible with a broad family of Ericsson Computer Telephony Integration network and telephony products. This section explains the interworking of different CTI products with a focus on the D.N.A. Application Suite. The interworking products are: = = = = = = = = D.N.A. MD110 Application Suite OneBox PSC and PSC Server Time Systems CCM CCA Next CC LDAP Data Sources
The relevant network elements are = MD110 = Business Phone The following matrix shows current interworking between different network elements and the CTI applications:
One Box MD110 Business Phone + + D.N.A. Server/DMG/OWS + + D.N.A. PMG + App Link + +*1 PSC PSC Serv + + * CCA CCM Next CC + + + + -
+ = full interworking * = restricted interworking - = no interworking
16
Technical Guide
D.N.A. Server
The D.N.A. Server lets you administrate the D.N.A. Application Suite users. It also contains different utilities to set up the connection with MD110 Nodes. The central component of a D.N.A. Installation is the Remote Data Server (RDS). RDS maintains network database synchronization between MD110 PBX nodes, the D.N.A. SQL Server, and D.N.A. Local Databases. Some of the most important database support functions are: = = = = = = = = = = = = Message Diversion Synchronization with the MD110. Message Waiting Synchronization that updates the Voice System Interface configuration utility. Application-to-Application Interactive Updates. Security and Licensing Support. D.N.A. Distributed Database Synchronization. Photo Storage and Retrieval for Operator Workstation and Directory Manager . Data File Storage and Retrieval Templates for Performance Manager and Extension Manager. Configuration File Storage and Retrieval for Operator Workstation and OCX . Administrative Task Scheduling. A tool to set up the Voice System Interface. A tool to upload directory information into MD110 phone displays. A tool to specify the replication between multiple D.N.A. Servers.
What You Will Find In This Help Guide

This guide is written for technicians responsible for installing and maintaining Ericssons Dynamic Network Administration (D.N.A.) applications. The D.N.A. Application Suite is a family of PC-based telephony applications for management and control of MD110 PABX operations. This guide includes the following help books. Applications - Provides a basic description of the applications. Pre Installation - Describes the main types of installations, PC hardware requirements, software which must be installed on the PC, and requirements for the MD110. Installation - Describes first-time installation of the D.N.A. applications, including hardware connections between the MD110 and PC, and installation of the application software on the PC. D.N.A. Server - Security and support platform for the Dynamic Network Administration (D.N.A.) applications. Maintenance - Describes tasks that should be performed periodically to ensure proper operation of your applications. Troubleshooting - Describes how to resolve problems that may occur. Application Data - Report generation, data organization, and populating directory assistance databases. Disk Space - Helps you determine how much hard disk space is needed on PCs used for D.N.A. applications.
17
Technical Support - Hardware specifications and problem reporting. MML Commands - Tables of commands for Extension Manager, MDS Utilities, and Performance Data Manager. Installation Checklist - Checklists for D.N.A. server and client workstation installation.
Related Publications
In addition to the MD110 D.N.A. Technical Guide, getting started guides are available for the following products. = = = = = Operator Workstation Extension Manager Directory Manager Performance Manager Numbering Plan Manager
Conventions Used in This Guide

The D.N.A. server PC may be part of a larger network that uses another computer as a server for that network. Throughout this help guide, however, "server" refers to the PC set up as the server for the D.N.A. application suite, and "network" refers to the Windows NT LAN that is hosting the D.N.A. server PC.
Using Help
Click the Contents tab to scroll through a table of contents for the Help file. Click the Index tab Search tab to use a full-text search to search for topics by using an index of Help subjects. Click the for specific words or phrases.
Tips for using Help

When viewing Help, you can maximize the window or resize it if you want. Click Help Topics to show or hide the Navigation Pane. Click Print to print the current topic. Click to go to the next topic in the browse sequence. Click to go to the previous topic in the browse sequence. The Options menu provides additional display controls.
Printing Help
Click the Print button to print the current topic. To print the entire help file you need to have Microsoft Word or Word Viewer installed on the PC. Word Viewer is a free download from Microsofts web site. To print the entire help file 1 Right-click on the MD110TechGuideHelp.doc file in the MRS\HELP directory under DNA_C or DNA_S. 2 Click Print on the pop-up menu.
18
Technical Guide
Glossary
Refer to the descriptions in this section for help with understanding terms used in this guide. Alarm Unit (ALU) - MD110 circuit board that handles PBX alarm input/output. Backup Domain Controller (BDC) - A Windows NT/2000 configuration option. Call Origin Group - A group number defined for an operator that serves a unique call type, such as internal calls, public trunk calls, tie lines, and DID lines. An operator can be assigned to several different call origin groups. Client - A PC in a network installation that is connected to a server PC and accesses data on the server when running applications. In a D.N.A. network installation, the SQL database and the D.N.A. Server reside on a server PC, and one or more client PCs run applications that access the data on the server. For a stand-alone installation, the server and the client are the same PC. COM Port - An RS-232C serial communication interface on a PC that allows direct connection to another PC or an MD110 with a cable or indirect connection using a modem or TAU. Computer Supported Telephony Application (CSTA) - Supports Computer Telephony Integration (CTI) between the Distributed Network Architecture (D.N.A.) environment and the MD110 PABX. Computer Telephony Adaptor (CT Adaptor) - Enables an Operator Workstation (OWS) PC to connect to the MD110 to perform call handling. DigiBoard - A communications port multiplexor that adds COM ports to a PC. Directory Manager (DMG) - A D.N.A. application that allows administrative personnel to manage subscriber directory entries. Includes capabilities for adding, modifying, and deleting subscriber directory records. D.N.A. Applications - The set of software applications that run on PC clients and are used in combination with one or more MD110s to manage telecommunications operations. D.N.A. Server - D.N.A. platform services and utilities that reside on the server and act as the intermediary between all D.N.A. applications and databases. E&M Signaling Device - Electronic interface between the MD110 PBX and recorded voice announcement (RVA) equipment. See also Voice Server Unit (VSU). Extension Line Unit (ELU) - The board in an MD110 that connects to physical subscriber telephones. Extension Manager (EMG) - A D.N.A. application for managing MD110 telephone data and extensions. Includes capabilities for administration of telephone and data extensions, messaging, and other PBX elements. General Information Communications Interface (GICI) - The physical interface for the ICU board in the MD110.
19
Graphical User Interface (GUI) - The user interface presented by D.N.A. applications and management utilities. Hardware Compatibility List (HCL) - A list of hardware tested and verified to work with Windows NT/2000. The list is available at http://www.microsoft.com/hcl. Information Computer Unit (ICU) - The board in an MD110 used for interception and message waiting services. Input/output Processor Unit (IPU) - A board in an MD110 that enables external devices to communicate with the MD110. Integrated Digital Network Exchange (IDNX) - For ISDN networks, the IDNX uses routing access information to enhance MD110 performance. This unit helps achieve efficient bandwidth utilization, high network reliability and availability, and control over the usage of network resources. Integrated Services Digital Network (ISDN) - ISDN uses a 64 kbit/s channel for transmitting digitally coded speech and data. This digital medium is normally used for circuit-switched connections, packetswitched connections, and semi-permanent connections. The complete digital interface (2B+D) consists of two B-channels for speech/data and one D-channel for signaling. Each MD110 Line Interface Module (LIM) supports up to 240 individual external ISDN lines. Lightweight Directory Access Protocol Service (LDAP) - Directory lookup and modification services for LDAP clients accessing Directory Manager databases. Local Area Network (LAN) - A computer network based on one or more centralized server PCs and one or more locally or remotely connected client PCs. Man-Machine Language (MML) - Command interface for MD110 PBX controls. MD110 - The Ericsson PBX. MD Support (MDS) - A D.N.A. administrative utility that synchronizes MD110 PBX configuration data with D.N.A. application databases. Additional capabilities include synchronization connections for serial, Telnet, and Serial Communications Services. Also called MD110 Support. Modem - Modulator/demodulator. A communications device that converts digital information from computers into analog electrical signals that can be transmitted over telephone lines and vice versa. A modem may be used to connect a PC to a remote MD110. Modem/Loop Extender - Communications adapter that enables the connection of a PC to a remote (150 feet or more away) MD110 ICU, IPU, or NIU. Network Interface Unit (NIU) - MD110 I/O Board interface supporting V.24, Ethernet, and SCSI communications. An NIU V.24 port configured as a network port (Ethernet) provides Telnet service via logical network/MML ports. Up to six logical network/MML ports can be initiated on an NIU. The NIU serves as an alternative to the Input/Output Processor (IPU) interface. Numbering Plan Manager (NPM) - A D.N.A. administrative application for Providers of Business Subscriber System (BSS) Services. NPM helps manage the mapping and administration of private customer numbering plans spanning multiple Business Subscriber Systems.
20
Technical Guide
NT/2000 File System (NTFS) - Windows NT/2000 file administration and management system. Operator Workstation (OWS) - A D.N.A. application that enables operators to manage MD110 telephone traffic through subscriber databases. Performance Data Manager (PDM) - See Performance Manager. Performance Manager (PMG) - The D.N.A. application that is used to collect traffic data and generate reports. Performance Manager actually consists of two applications: Performance Data Manager (PDM), and Performance Presentation Manager (PPM). PDM is used to extract traffic measurement data from one or more MD110 nodes, and PPM is used to generate reports based on data extracted by PDM. Performance Presentation Manager (PPM) - See Performance Manager. Primary Domain Controller (PDC) - A Windows NT/2000 configuration option. Private Branch Exchange (PBX) - Telephone switching system that supports a private community of subscribers, typically a business environment. Usually managed from a central operator console, PABXs interconnect internal subscribers to one another, and to other subscribers in the public network. Also known as Private Business Exchange and Private Automated Business Exchange (PABX). Remote Data Server (RDS) - D.N.A. Server Utility that allows you to configure the Remote Data Server for D.N.A. database and application support roles, including network database synchronization between MD110 PBX nodes, the D.N.A. SQL Server, and D.N.A. Local Databases (LDBs). Serial Communications Server (SCS) - D.N.A. Server Utility that allows you to manage direct, Telnet, SCS, and third party serial communications port settings. Server - The central PC for a D.N.A. network installation. In a network installation, the SQL database and the D.N.A. Server software reside on a server. One or more client PCs may run D.N.A. applications that access the data on the server. The server acts as a database referee, providing data security, centralized file access, management services, and controlling ID master files and external subscriber directories. For a stand-alone installation, the server and the client is one PC. Stand-alone - An installation of D.N.A. applications on a single PC instead of a network of PCs. In a network installation, the SQL database and the D.N.A. Server reside on a server PC, and one or more client PCs run D.N.A. applications that access the data on the server. In a stand-alone installation, all of these elements (SQL database, D.N.A. Server, and D.N.A. applications) are installed on a single PC. Terminal Adapter Unit (TAU) - Terminal Adapter Unit, a device that enables connection of a PC to a remote MD110. Time System Server (TSS) Configuration - An optional D.N.A. module that allows connection to an external time monitoring system. Through this interface, diversions can be entered in the time monitoring system and registered in the D.N.A. directory database. TSI also allows control signals for message waiting indications to be sent from D.N.A. to the time monitoring system. Trunk Manager (TRM) - Enables you to assign easily recognizable names to incoming trunks for efficient operator identification and routing. Voice Server Unit (VSU) - Line Interface Module (LIM) hardware for storing voice messages.
21
Voice System Interface (VSI) - An optional D.N.A. module that allows voice mail integration. VSI acts as a compatibility interface between the MD110 PBX and Ericsson Voice Message Processing Systems. Capabilities include call diversion options, support for Message Waiting Indicators (MWI), and increased reliability of voice processing operations. Wide Area Network (WAN) - Inter-office private telecommunications networks.
Applications
Description of Applications
The D.N.A. MD110 application suite is an integrated set of applications that allow you to operate and manage your MD110 communications resources from stand-alone or networked PCs. The application suite includes the following applications.
D.N.A. Server The operational and administrative platform for the D.N.A. utilities and data structures. Includes system configuration and maintenance utilities for supporting D.N.A. applications. OWS support and administrative application that enables you to add, modify, and delete D.N.A. Directory entries. The D.N.A. Directory Browser provides directory services to a corporate-wide phone directory on a corporate intranet or to external customers on the internet. You can search a phone directory with your web browser. No other plug-ins are necessary. In addition to the searching the corporate phone directory, Directory Browser allows you to send and receive short text messages, set and view message diversion, and make calls. D.N.A. traffic management application. Allows operators to access D.N.A. Directory subscriber information and route telephone traffic. D.N.A. application for management of MD110 telephone data (extensions, extension groups, equipment assignments, and other resources). A traffic measurement and reporting application for network performance analysis. Allows analysts and administrators to capture traffic data and generate reports. This application consists of Performance Data Manager (PDM), and Performance Presentation Manager (PPM), two separate applications. PDM extracts traffic measurement data from one or more MD110 nodes. PPM creates reports from data extracted by PDM. An Internet Server-based version of Performance Presentation Manager. The application is installed as a web site. Users point their browsers to the PPM Lite server and log on to view traffic analysis reports. A D.N.A. administrative application for Providers of Business Subscriber System (BSS) Services. NPM helps manage the mapping and administration of private customer number plans
Directory Manager (DMG) Directory Browser
Operator Workstation (OWS)
Extension Manager (EMG)
Performance Manager (PMG)
PPM Lite
Numbering Plan Manager (NPM)
22
Technical Guide
spanning multiple Business Subscriber Systems.
Limitations
PPM Lite
Observe the following requirements for reliable PPM Lite operation. = PPM Lite will not function properly without a session state. The Session Timeout feature for your PPM Lite web site must not be disabled. = PPM Lite output must be viewed using monitors with minimum display capabilities of 256 colors, and 800x600 resolution.
Directory Browser
The D.N.A. Directory Browser supports HTML 3.2. Although it will function properly on many browsers, it was tested on Internet Explorer 4.0 Service Pack 1, Internet Explorer 5.0, and Netscape 4.0. Dialing is enabled only when you have AppLink installed and the number you are dialing from must be a valid number in a numbering series.
OneBox Mailbox Integration

D.N.A. MD110 systems with a OneBox mailbox can access voice mail, e-mail, or fax mail messages from a unified interface such as Microsoft Outlook or their telephone.
23
Integration of OneBox and D.N.A.

You may create, modify or delete OneBox mailboxes from the D.N.A. Directory Manager and Extension Manager applications. During D.N.A. setup, the system administrator can assign one or more OneBox servers to an MD110 node via the MD110 Support utility. Supported attributes include a OneBox Server name or IP address, password, and extension ranges.
OneBox Controls OneBox mailbox integration allows you to configure the following basic mailbox attributes. = = = = = = = Extension Callout Capabilities Local or Long Distance Enabling/Disabling of Message Waiting Indicators Message Retention Duration Message Clearing Options Set-up of Tutorial Prompts Desktop Options on OneBox Message Manager
24
Technical Guide
Automatic Mailbox Creation/Deletion OneBox mailboxes are automatically created or deleted when assigned subscribers are created or deleted in the D.N.A. Directory Manager. OneBox Database Synchronization There is no synchronization between the OneBox Directory and the D.N.A. Directory Manager Database. There is only one-way communication, from Directory Manager towards OneBox. If a mailbox is created with the OneBox System Administration, Directory Manager is not informed.
Communication between OneBox and the D.N.A. Server is conducted via Local Area Network (LAN).
OneBox Compatibility with Other Network Elements

This integration is available for D.N.A. Directory Manager and Extension Manage. It is not compatible with D.N.A Application Suite for Mobility Server or the Application Suite for Business Phone. OneBox Integration with D.N.A. Voice System Interface Subscribers have five possible options for initiating message diversions. Any diversion reason that is entered is stored on the D.N.A. Application Suite Server. These options are: = = = = = Entering a diversion code on the numeric keypad. E.g., * 23 * 4 *1300 # for "Lunch until 1300" D.N.A. users can initiate a diversion from Microsoft Outlook PSC users can initiate a diversion from these applications Through the Telephone User Interface (TUI) of OneBox An Operator using D.N.A. Operator Workstation can initiate a diversion for any subscriber.
25
Using Diversion Reasons OneBox can query diversion reasons from the D.N.A. Server. OneBox can use this information to play an appropriate voice prompt to a caller matching the diversion reason, e.g., "Gina is out for lunch and will be back at 13:00. Please leave a message after the tone, or dial zero for operator."
Note Communication between OneBox and the D.N.A. Server requires a serial link. OneBox Intercept Capabilities Integration with D.N.A. provides OneBox with the ability to: = = = = Accept Intercept Call Diversion requests entered by a subscriber Store the diversion information Provide audio intercept messages to callers trying to reach the mailbox subscriber Support various "next action" options presented to the caller
Audio intercept messages can present callers a selected set of "next action" options, including: = = = = = Leaving a message Transfer to operator or personal assistant Hang-up Transfer to another number Hear choices in another language
Messages left in mailboxes are available to mailbox users through normal Voice Mail services.
26
Technical Guide
When a caller chooses the "transfer to operator" option, and the call is forwarded from OneBox to the PABX Operator, the original called extension is displayed for the operator. The operator can also retrieve the diversion reason from the D.N.A. Database. The OneBox Telephone User Interface (TUI) is the only means of initiating message diversions from a remote location, without having access to a PC. This integration is available for D.N.A. Directory Manager.
Compatibility with Other Network Elements

= MD110 = Business Phone = Not applicable for Mob Server OneBox can also be used with Mobility Server, where basic functionality is available.
D.N.A. Application Suite - MD110

The D.N.A. Extension Manager application allows users to upload the subscriber names from the Directory Database to the MD110. The MD110, however, can only display 10 Characters on digital phones. Therefore names are truncated according to two alternative methods. = First letter of the first name, one blank and the first 8 letters of the last name = First name and the first letter of the last name
Dial By Name Directory

The Dial By Name data in the MD110 is separate from the data for name display on digital phones. The D.N.A. Name Identity Configuration utility allows system administrators to upload names from the Directory Manager Database to the MD110.

= MD110
27
Personal Screen Call

PSC can be run in two modes. = Using just a private database = Using a private database for each user and a corporate database for all PSC users. One option for the second mode is to use the D.N.A. Directory Manager Database as a common information source. (For PSC 2.0, this is the only option.)
Upon launching the PSC application the local PSC database is synchronized with the Directory Manager Database. All relevant information is copied locally to the PSC PC. Re-synchronization of the local copy and the D.N.A. Server Database is performed at each logon. Clients who are logged on are updated the moment a change is made by D.N.A. Directory Manager.
28
Technical Guide
PSC integration with D.N.A. RDS

As mentioned above, PSC users can initiate call diversions from within the PSC application.
29
PSC 1.1 PSC 1.1 sends diversion information to the MD110 via CT Adapter or ApplicationLink. The MD110 forwards this information to the D.N.A. Server to make it available to D.N.A. Operators.
30
Technical Guide
PSC 2.0 PSC addresses diversion information directly towards the D.N.A. Server. The D.N.A. Server forwards the information to the MD110. This enables users to initiate "future diversions" from the PSC 2.0 application. This capability is not available with PSC 1.1.
If no D.N.A. Server is present, PSC 2.0 initiates diversions directly to the MD110 via Application Link or CT Adapter. (To enable Future diversions, PSC has to be running on the user PC) Compatibility with Other Network Elements = MD110
PSC Server
PSC Server integrates with the D.N.A. Directory in the same way as Personal Web Directory. A copy of the Directory Manager Database resides on the company WWW Server along with the PSC Server application. PSC Server synchronizes message diversions with D.N.A. in the same way as does PSC. Additionally, PSC Server can be integrated with any Lightweight Directory Access Protocol (LDAP) compatible data source. These functions are available for D.N.A >=3.0 Compatibility with Other Network Elements = MD110 = Business Phone
31
Application Link
MD110 Application Link is a software interface for Computer Telephony Integration. It provides a command and status link between the MD110 and the D.N.A. computer. Application Link allows computer controlled call management. Application Link supports applications provided by computer vendors, by Ericsson, or applications developed directly by D.N.A. customers.
General Operations
Using a D.N.A. PC as a telephone console, users can send telephony requests from the PC to the switch through MD110 Application Link. The D.N.A. PC can also receive MD110 events as well as A-party and B-party information through the MD110 Application Link. This information can be used by the computer to route the call or call-related data to a computer display.
Through its Computer Supported Telephony (CSTA) based interface, MD110 Application Link supports a variety of Application Programming Interfaces (APIs), including Dialogic's CT Connect, IBM's Call Path, Novell's TSAPI and Tandem's CAM. MD110 Application Link also supports Microsoft's TAPI via its proprietary protocol. Any MD110 Application Link can be configured to support either CSTA-based API's or TAPI, however one server cannot support both.
Application Link and CCA

CCA is using the TSAPI API. On the server side MD110 Application Link is required. At each client a 32-bit Client DLL must be installed that converts the TSAPI API into CSTA messages. Win 95 and Win NT/2000 clients in a TCP/IP network are supported.
Application Link and PSC

On the Server side MD110 Application Link and Microsoft TAPI 2.1 is required. At each client a remote service provider (provided by Microsoft) must be installed. The remote service providers also include
32
Technical Guide
management and security tools. Clients currently supported by Microsoft are Windows NT/2000 and Windows 95."

= MD110 = Business Phone (BusinessLink)
Time System Interface

D.N.A. Time System Interface (TSI) is an optional D.N.A. service module that connects to an external time monitoring system. TSI allows diversions to be entered in the time monitoring system, transferred to the D.N.A. Directory Manager application, and registered in the D.N.A. Directory database. As well, Message Waiting (MWT) indications can be sent from D.N.A. to the time monitoring system. The D.N.A. Time System Interface enables the D.N.A. Directory Database to receive message diversions from Time Entry Systems. If an employee checks out, the Time System can forward the check out time to the D.N.A. Server (a special time system protocol via a serial link). The D.N.A. server can then initiate a diversion for the subscriber's phone.
Compatibility with Other Network Elements = MD110 = Business Phone
33
CCM/D.N.A. Extension Manager Integration

With D.N.A. and CCM it is possible to configure in the Call Center Manager (CCM) Setup to either use the EMG or the CCM database. If the EMG database is selected, the CCM Configuration Manager will be able to: = Launch EMG to perform initiations, deletions, and updates for ACD/ANCD/DNIS objects. When launched, EMG uses the NT/2000 logon user name if found and verified. If not found, the user is required to log on. In case of multiple MD110 nodes, the user must logon to each site individually to make changes of these objects. = The creation, deletion and name change of ACD/ANCD/DNIS objects will be disabled in Configuration Manager. Others will be available for editing. = Multiple-Member Busy and Queue Timeout fields are disabled in Configuration Manager. The Remote Data Server (RDS) is the communication link between CCM and EMG. If the EMG database is selected in CCM setup, the Configuration Service in CCM can query ACD/ANCD/DNIS, Multiple-Member Busy and Queue Timeout information stored in the EMG database via RDS. CCM synchronizes with the EMG database on notification (via RDS) of its use.
Compatibility with Other Network Elements Available for MD110 only.
34
Technical Guide
CCA/D.N.A. Directory Manager Integration

With D.N.A and CCA and, CCA users can utilize the D.N.A. Directory Manager Information. Upon logon each CCA user gets a private database on the CCA Server assigned and the Directory database is updated with the actual extension number where the agent is seated. At the same time this CCA user can receive a copy of the D.N.A. Directory Manager Database, which is stored locally on his PC.
Compatibility with Other Network Elements = MD110 = Business Phone.
35
Next CC/D.N.A. Integration

In its first release the Next CC can use the D.N.A. Directory Manager database. If a specially named user defined field (UDF) is configured in Directory Manager, Next CC can import either the whole DMG Database or only subscribers with a "YES" entry in this field. The import process must be initiated manually from the Next CC Server. Upon log-on of a Next CC user, the Directory Manager database is updated with the actual extension number of the agent (through the D.N.A. Directory Link, <see The D.N.A. Directory Link>). As well, the Next CC Agent can receive a copy of the D.N.A. Directory Manager Database. This database is stored locally on the Next CC Agent PC.
Compatibility with Other Network Elements Available for MD110 only.
36
Technical Guide
LDAP
The Lightweight Directory Access Protocol (LDAP) standard dictates how clients, applications, and servers access directory information. LDAP is a directory service protocol that runs over TCP/IP. The LDAP Directory service is based on the client-server model.
D.N.A. includes LDAP Server in the D.N.A. Server and an LDAP Client in the Operator Workstation. The OWS can search any LDAP Server for a subscriber and can use this information in the same manner as information from the Directory Manager Database. On the other hand, any LDAP Client (i.e. an Internet Browser) is able to search the Directory Manager Database through the D.N.A. LDAP Server. Compatibility with Other Network Elements This integration is only available for D.N.A. Directory Manager; therefore it does not work with D.N.A Application Suite for Mobility Server 2.0 or the Application Suite for Business Phone (Internal name Application Suite 3.4).
Other Interfaces
Directory Link
The Directory Link interface allows non-D.N.A. applications to modify D.N.A. Directory data. Directory Link can be thought of as a DMG client without a user interface. Directory Link accesses and modifies directory databases through the database API library, and communicates with other DMG and OWS clients through RDS. Directory Link is currently in service with Next CC and by a third-party Application from BITEK. Directory Link specifications are available for interested Ericsson Partners through the Ericsson Partner Program.
37
Extension Link
Extension Link is a real-time interface to the Extension Manager (EMG) application. Extension Link manages MD110 extensions and facilities and is designed to make EMG features reusable for customized configuration management applications. Extension Link is currently in service with a third-party Application from BITEK. Extension Link specifications are available for interested Ericsson Partners through the Ericsson Partner Program.
D.N.A. CAAPI
The D.N.A. Call Accounting Application Programming Interface (CAAPI) enables Third-party Call Accounting Applications to utilize Directory Manager data. Directory Manager generates a file containing an extract of the DMG data. Call accounting applications can now import these data on a scheduled basis from a single point-of-entry. D.N.A. CAAPI is compatible with the following Network Elements = MD110 = Business Phone
Change Log
The Directory Change Log allows directory data changes to be collected by external applications like Call Accounting Packages, desktop applications, or other Ericsson CTI applications. With previous D.N.A. releases it was necessary to re-import all data after adds/moves/changes. With D.N.A, only changed data is imported. The Change Log is a client component of the Remote Data Server (RDS) that sequentially records all Directory Manager and Directory Link modifications made to the Directory Database.
38
Technical Guide
D.N.A. CTI
This schematic summarizes most D.N.A. CTI Interworking capabilities and illustrates the central role of the D.N.A. Directory.
Mobile Executive
This section contains the administrator issues for the Mobile Executive.
WAP Gateway
If you use your mobile operator's WAP-service you will probably have to open up your company's firewall to accept and route WAP-traffic to your Mobile Executive server. If you set up your own WAPgateway and dial-in connection you open a hole where a potential hacker could sneak in. Many companies will probably not allow this, so to strengthen security the RAS-server could, for example, be put on a separate LAN segment that is separated from the real company-intranet with a firewall (this is just one way to increase security, there are more).
39
Phone Setup
Setting up a WAP phone is telephone-specific, however, the following information is required for all phones. = = = = A phone number (to the company's or your mobile operator's RAS-server). Username and password (to log on to the RAS-server). The address of the WAP-gateway (IP-address). Username and password for the WAP-gateway (if used).
The user needs the address for the Mobile Executive server. To log on to Mobile Executive the user needs a username and a password. When users have entered this information to their phones they are ready to use WAP. R320s Phone setup for D.N.A. WAP Perform the following steps to setup an R320s Mobile Phone to be used with the WAP Gateway in the MD110 D.N.A. If you don't have all the information required, see your mobile phone administrator.
1
Go to the WAP Services menu and select 6 WAP Settings.
Select one of the available profiles, select 4 Access on the WAP Settings menu, select 1 Access Type on the Access menu, and set the Access Type to GSM Data.
40
Technical Guide
Return to the Access menu, select 3 Service Center, and enter your Service Center number.
Return to the Access menu, select 4 GSM Data, select 1 Phone number on the GSM Data menu, and enter the number of the modem pool used to the WAP Gateway. GSM stands for Global System for Mobile Communications.
Return to the GSM Data menu, select 2 Dial Type, and set the Dial Type to Analog.
Return to the GSM Data menu, select 3 User ID, and enter the user's ID.
41
Return to the GSM Data menu, select 4 Password, and enter the user's password.
Return to the Access menu, select 5 Gateway, select 3 Data Access on the Gateway menu, and enter the IP Address of the WAP Gateway server.
SNMP Agent
SNMP Agent comes with Windows NT and Windows 2000, but is not installed by default. To make the SNMP agent for D.N.A. work you have to do two things, install D.N.A. and install the Windows NT master agent. You must have administrator privileges to perform this installation. SNMP is actually a DMI agent that pretends to be an SNMP agent. The following diagram shows an overview of the different components.
42
Technical Guide
The Monitored Objects

SDS, RDS, TSS, VSI, SCS, LDS and OWS Supervisor are the components that are monitored. They all include a small piece of code that acts like a wrapper between the applications and the as_dmi.exe component. They call functions in the wrapper class to initialize, report status, and shutdown applications. When the applications run for the first time they are added to a persistent table that as_dmi.exe keeps in the registry. This can be seen under HKLM\Software\Ericsson\DMI\AppSuite. InstalledAppSuiteComponents is a bit mask where the "known" applications APP_ID are ord together. Each application also has its own value there, describing its current state. These are named with the applications short name. as_dmi.exe This is the central repository for the status information. The applications store their current status here and DMI picks it up from here. This component is a singleton. That means that there should only be one instance of it running on the machine, all applications (running on this machine) plus asdmi.exe connect to the same object. asdmi.exe This component is the glue that actually makes this into a DMI agent. Its instantiated by the CIMgr (i.e. it comes and goes with it) and there is only one at a time on each machine. CIMgr & Win32sl These services make up the core of the DMI run-time system. Win32sl has to be started before you can start this service (dependency is set in the registry). Actually, CIMgr isnt a service. The service is called CIMgrLdr and its only purpose is to run CIMgr. The registry keys for CIMgr can be seen under HKLM\Software\Intel\CIMgr. The registry keys for Win32sl can be seen under HKLM\Software\Intel\DMI 2.0 SDK. NT SNMP This is the Windows NT master agent. Actually, this piece routes SNMP requests to the right DLL. All its functionality is built on installable sub-agents contained in DLL files that are loaded when the master agent is started (as an NT service). The registry keys for NT SNMP can be seen under HKLM\System\CurrentControlSet\Services\SNMP. Dmi2snmp This is both a DMI management application and an SNMP sub-agent. It performs this double duty as the middle layer that maps SNMP requests to DMI calls and also transforms DMI events into SNMP traps. It has no user interface and no configuration, its just loaded by the master agent when it starts and then does its job quietly. The registry keys for Dmi2snmp can be seen under HKLM\Software\Intel\DMI 2.0 to SNMP Mapper. See Also: SNMP Master Agent
43
Remote Data Monitor

The Remote Data Monitor (RDM) utility displays error information and audit messages for D.N.A. applications. To start RDM, double-click on DNA_S\SHARE\BIN\rdm.exe.
Some of the things you can see with RDM are: = = = = Local Database Transfers Clients Registering and Disconnecting from RDS LDAP Queries and Answers GICI Codes Sent to and from the MD110
44
Technical Guide
Visitor Registration
Customers can use Visitor Registration to have visitors to a facility register in the lobby. The Visitor Registration dialog box is opened from the Start menu. Start Programs D.N.A. Application Suite Visitor Registration
The Visitor Registration dialog box provides edit boxes for Visitor Name, Contact Person, Extension, and Keyword. The Extension field defaults to the contact persons extension, but can be changed. Visitor information is registered with the Add button and unregistered with the Delete button. The Refresh button updates the dialog box fields with the latest information from the database. Visitor information can be printed with the Print... button.
Preinstallation
About Pre-Installation
Before installing D.N.A. Application Suite components, perform checks and preparations necessary for a smooth and successful completion. Specifically, make certain you perform the following:
1 2 3 4
Conduct a pre-installation meeting with the customer. Verify that all PC hardware requirements have been addressed. Verify that all software requirements have been addressed. Verify that all MD110 requirements have been addressed.
Pre-Installation Meeting
You can avoid many common D.N.A. installation problems by including at least one pre-installation meeting in your preparations. Use this meeting to coordinate your plans with the customer well in advance of the actual installation. The following manuals could be useful for Installation. = Windows NT / 2000 System Guide = SQL Server Books Online (BOL) = MD110 Customer Library (Dynatext) Addressing Important Issues Try to cover all the major issues involved in the installation process. Don't make presumptions about issues that may seem "obvious." For example: Who is responsible for arrangements and preparation of the computer network (Ericsson or the customer)? Pre-installation Checklist Ericsson provides a Pre-Installation Checklist to help with installation planning. Use this checklist to identify and verify the all-responsible persons and essential D.N.A. components.
45
MD110 Hardware Requirements

Each PC running Extension Manager, Operator Workstation, Numbering Plan Manager or Performance Data Manager (PDM) must be connected to the MD110. Extension Manager, Numbering Plan Manager and PDM utilize connections from the PCs COM or Telnet ports to an IPU board on the MD110, either by direct connection or modem/TAU/Telnet connection. An IPU or NIU board with an adequate number of free ports must be installed on each MD110 that will be connected to PCs running Extension Manager, Numbering Plan Manager, and Performance Data Manager. Extension Manager, Numbering Plan Manager, MD Support, and Performance Data Manager can optionally utilize Access Agent devices for extended communications. MD110 BC9, BC10 and BC11 are supported.
Requirements
Configuration Options
Ericssons D.N.A. Application Suite consists of flexible products that can be used in a wide range of configurations. For purposes of this help guide, however, the general configuration options are explained in the following table.
Configuration Options Explanation Network vs. stand-alone In a network installation, D.N.A. MD110 applications are spread across multiple PCs. One PC (the server) includes the SQL database server and D.N.A. Server software. One or more other PCs (clients) are connected to the server and are used to run the applications. If desired, the server can also be set up as a client that runs applications. In a stand-alone installation, the SQL database server, D.N.A. Server software, and MD110 applications are all installed on a single PC, and there are no connected PCs used to run applications. The stand-alone PC is set up as both the server and the client for all applications. Each MD110 installation can support one node or multiple nodes. Both network and standalone installations can be set up as single node or multi-node.
Single node vs. multi-node
Single Server
The following diagram represents a stand-alone installation of an Operator Work Station together with Directory Manager.
46
Technical Guide
The stand-alone PC contains Microsoft Windows (NT 4 or Windows 2000) , the D.N.A. Server, and the Operator Workstation and Directory Manager applications. The Operator Workstation voice connection to MD110 is by means of a CT adapter via ELU28. In order to provide diversion information to and from the Operator Workstation, the D.N.A. server is connected to the MD110 NIU via TCP/IP.
Single Server with Operator Workstation VIP

This configuration represents a single D.N.A. Server with 5 clients. The clients are running Operator Workstation, Operator Workstation VIP, Directory Manager, Extension Manager, Performance Manager, and a call account application.
The D.N.A. Server contains Microsoft's Windows NT Server 4.0 or Windows 2000 Server, the Microsoft SQL Server and the D.N.A. Server application. The D.N.A. Server and the MD110 Access Agent are connected via the LAN and TCP/IP. Direct communication between the server and the
47
MD110 is necessary to transmit diversion information. All other communication is done through the clients. The Extension Manager and Performance Manager Clients communicate with the MD110 via the same physical interface: Extension Manager to make adds, moves and changes, Performance Manager to set up measurements in the MD110. Updates of the Extension Manager or Performance Manager Database are transferred from the MD110 to the Client and from here to the server database. The call data records (CDRs) are transferred to the Client running the call accounting application via V.24. The call account application also communicates with the D.N.A. Server via the LAN to get the directory information (like Names, Departments, Cost centers etc.).
Multiple Servers
This configuration represents a network of 3 D.N.A. Servers in 3 different domains.
The 3 domains are connected via routers with full trust relationship. Each domain contains a D.N.A. server. The servers are configured in such way that any D.N.A. client can connect to any of the D.N.A. servers. In order for the client to successfully connect to a remote D.N.A. server, the user must have a D.N.A. user account in that particular server. With the MD110 D.N.A. Application Suite the user can be connected to multiple D.N.A. servers at the same time. A remote connection is per application only. This enables the user to connect to a remote server without impacting other running D.N.A. applications. For example, a user working with OWS connected to Server A in Domain 1, can start and connect DMG to Server B in Domain 2 while keeping the OWS connection intact. The MD110s are connected to the LAN via D.N.A. Access Agents. Access from EMG and PMG applications are performed through the D.N.A. Access Agents. Users can make global searches. This means that the user searches for a particular subscriber without specifying which server to search. By default this searches all servers. To enable this feature in the OWS the D.N.A. servers must be configured to subscribe to directory data from the other D.N.A. servers.
48
Technical Guide
After configuring the data subscription, each D.N.A. Server is configured to publish this data to its clients. The D.N.A. Server is configured to publish each D.N.A. server's data individually, or combining the data for all D.N.A. servers. For the global search scenario, the data needs to be combined for all D.N.A. servers. Diversion information and detailed subscriber information, is requested from OWS to the Local D.N.A. server which forwards the request to the D.N.A. server in question.
LDAP Servers
This configuration represents a network consisting of a D.N.A. server, a Web server, and an LDAP compliant directory server.
LDAP and 3rd party clients
OWS LDAP client DMG, EMG, PMG
Router
Web Server with DNA Directory Web access
Other LDAP servers and 3rd party application servers
D.N.A. Server D.N.A. LDAP interface D.N.A. Access Agents
The D.N.A. server co-exists in the same domain with a Web server and another LDAP compliant directory server. The MD110s are connected to the LAN via D.N.A. Access Agents. The OWS clients are configured to perform directory searches towards the D.N.A. server and the LDAP compliant server. The Web server is used to provide a Web based access to the D.N.A. directory information through Web browsers. The LDAP compliant applications are configured to perform directory searches towards the D.N.A. LDAP interface and the LDAP compliant server. With the MD110 D.N.A. Application Suite, 3rd party applications can act as the master for the data in the D.N.A. Directory and the D.N.A. Extension manager Database. This enables 3rd party applications to perform moves, adds, and changes towards both the directory database and the MD110 with the Extension Manager database using the Extension Link and Directory Link interfaces.
49
Basic Requirements
This section lists basic hardware requirements for D.N.A. server and client PCs.
Server
Each PC that will be configured as a D.N.A. server should meet the following requirements.
Component PC CPU Memory Monitor and Card Mouse CD-ROM Network Card COM Ports Minimum Requirement Intel Pentium III. 64 Mbytes RAM (Minimum 128 RAM for Windows 2000) 1024X768 monitor and video card resolution Microsoft-compatible two-button mouse. (Required for server PC only.) LAN network card (not required for stand-alone system). Communications port requirements are based on which applications will be installed. A DigiBoard or COM port adapter may be used if additional COM ports are needed. For Event Manager, only ports COM1-COM4 are supported. A DigiBoard that adds COM ports beyond COM4 cannot be used with Event Manager under Windows NT. IEEE-488 parallel port for printer (LPT1). Server (optional), OWS client (recommended for Visually Impaired option). Server (optional), OWS client (recommended for Visually Impaired option).
Printer Ports Sound Board Speakers
50
Technical Guide
Specific Requirements
Platform 1 COM port/MD110 (used for diversion information). Not applicable if the D.N.A. Access Agent or NIU is used. 1 COM port/Time system. 1 COM port/Voice mail. Database size: 20 Mbytes. Database size: 45 Mbytes for the first 2000 subscribers. 2.5 Mbytes for each additional 500 subscribers. 10 Kbytes / photo (2.5 cm x 1.5 cm in 256 colors). 1 COM port for MD110 connection. Not applicable if the D.N.A. Access Agent or NIU is used. Database size: 6 Mbytes/MD110. 15 Mbytes per 500 extensions + 7.5 Mbytes. 1 COM port for CT adapter. 1 COM port for OWS keyboard (optional). Disk drive (memory) requirement 3 MB per 1000 directory entries 1 COM port for MD110 connection. Not applicable if the D.N.A. Access Agent or NIU is used. Database size: 4.5 Mbytes/MD110 + 7.5 Mbytes. 1 COM port for MD110 connection (PDM). Not applicable if the D.N.A. Access Agent is used. Primary database size: 9 Mbytes/month + 19 Mbytes (for 20 measurements). Auxiliary database size: 9 Mbytes/month + 10 Mbytes (for 20 measurements). Archive files: 4 Mbytes/month. 0-500 PII 266 64 MB 501-3000 PII 300 96 MB 3001-6000 P III 450 128MB 6001- 10000 PIII 500 256MB
DMG
EMG
OWS
NPM
PMG
Minimum Recommendations
Subscribers Processor Memory
The required hard disk capacity is dependent on the applications installed and the data they store.
51
Client PC
Each PC that will be configured as a D.N.A. server should meet the following requirements.
Component PC/CPU Memory Minimum Requirement 266 MHz Pentium II 64 Mbytes RAM (Minimum 128 RAM for Windows 2000)
Monitor and Card 800x600 monitor and video card resolution Mouse CD-ROM Network Card COM Ports Microsoft-compatible two-button mouse. Required for server only. LAN network card (not needed for a standalone installation) Communications port requirements are based on which applications will be installed. For Event Manager, only ports COM1-COM4 are supported. A DigiBoard that adds COM ports beyond COM4 cannot be used with Event Manager under Windows NT. IEEE-488 parallel port for printer (LPT1). OWS client (recommended for Visually Impaired option). OWS client (recommended for Visually Impaired option). No specific requirements. No specific requirements. 1 COM port for MD110 connection. Not applicable if the D.N.A. Access Agent is used. 1 COM port for CT adapter. 1 COM port for OWS keyboard (optional). 1 COM port for MD110 connection. Not applicable if the D.N.A. Access Agent is used. 1 COM port for MD110 connection (PDM). Not applicable if the D.N.A. Access Agent is used.
Printer Ports Sound Card Speakers
Specific requirements
Platform DMG EMG OWS NPM PMG
Additional Hardware Options

Additional hardware that can be installed on a PC includes Ethernet adapter, tape drive, and serial port adapter (or DigiBoard). To install the hardware, follow the manufacturer installation instructions to set the IRQ and I/O address. You may need to run setup programs from the vendor to configure the hardware. IRQ and I/O addresses must be unique for each port and hardware device.
52
Technical Guide
Hard Disk Requirements

When estimating hard disk storage requirements, always allow for the storage requirements of all applications, data, and support files that will reside on the hard disk. The following tables list server and client PC disk space requirements for individual D.N.A. applications. Note You must have 100 MB free disk space on each server or client PC in order to run the D.N.A. installation program.
Recommendation
For best reliability Ericsson recommends that you use the Windows NT File System (NTFS). NTSF has proven to be more stable than the FAT. If you are supporting a large system requiring data redundancy, you may use any of Windows NT's RAID software implementations. However, if you choose to employ a hardware RAID solution, make sure it is on the Windows NT hardware compatibility list (HCL).
Server Disk Space Requirements

The following table lists server PC disk space requirements for individual D.N.A. applications. Note You must have 100 MB free disk space on each server or client PC in order to run the D.N.A. installation program.
Application Executable SQL Database Caching for GUI Execution Local DB Memory map Log Files files (1MB / 1000) x Total extensions on all nodes x 15 [See D.N.A. Server note]
D.N.A. Server
30 MB for executable files 44 MB for client installation files
DNACOMMONDAT 4 MB 12 MB/1000 N/A subscribers DNACOMMONLOG 2 MB DNADFDAT 2 MB DNADFLOG 10 MB SECUDAT 4 MB SECULOG 2 MB XDAT - 4 MB XLOG - 4 MB
Photos
N/A
10 KB per 2.5 cm x 1.5 cm N/A (1" x ") photo in 256 colors Customer dependent N/A
N/A
N/A
Customer Information Files Directory Manager
N/A
N/A
N/A
10 MB
DIRDBDAT -for fewer than 1 MB 2000 subscribers = [20 MB] -For more than 2000 subscribers = [20 MB + 1 MB/200 x (No. of subscribers - 2000)]
[1.5 MB + 4.6 N/A KB x No. of subscribers]
53
DIRDBLOG -for fewer than 200 subscribers = [25 MB] -For more than 2000 subscribers = [25 MB + 1MB/200 x (number of subscribers - 2000)] Extension Manager 9.4 MB 1 MB per 17 KB x No. EMGDBDAT device = 6 of Nodes MB x no. of Nodes + total 1000 subscribers extension on all nodes / 100 x 3 MB EMGDBLOG device = 4 MB x no. of Nodes + Total extension of all nodes/100 x 2 MB [See note (2)] Operator Workstation 3 MB N/A 6 MB/1000 N/A subscribers 1 MB/1000 subscribers 7 KB per logged-in User ID Archive files 4 MB per node per month Logs - 2 MB per node 0.6 MB x No. of Nodes [See Extension Manager note]
Performance 4.5 MB Manager
For minimum 20 measurements: PDMDAT - 10 MB + 9 MB x (primary month + auxiliary month) PDMLOG - 21 MB (if auxiliary is used) or 11 MB (if auxiliary is not used) + 9 MB x (primary month + auxiliary month) Database device size will be increased based on nuMBer of Active Measurements (e.g. 30-40 = base size x 2) 50-60 = base size x 3
Numbering Plan Manager
1MB
N/A NPMDBDAT = 3 MB x Number of nodes + 5 MB NPMDBLOG = 2 MB x Number of nodes + 3 MB
N/A
0.6 MB [see Numbering Plan Manager note]
*N/A = does not apply
Notes
D.N.A. Server Assume that MDS is used not more than 15 days per month and the following month the log file is overwritten.
54
Technical Guide
Extension Manager Site# database in EMGDBDAT = 6 MB + Extension of the node# / 100 x 3 MB Site# database in EMGDBLOG = 4 MB + Extension of the node# / 100 x 2 MB Assume 20 KB per log file per day and there are 31 log files in a month and EMG is used everyday. The following month the log file will be overwritten. Numbering Plan Manager Assume 20 KB per log file per day for the entire network and there are 31 log files in a month and NPM is used everyday. The following month the log file will be overwritten. SQL Server Data Volume Estimates To avoid confusion, it is important that you understand the difference between automatic recording and automatic data extraction. Recording is performed by the MD110 and extraction is performed by Performance Data Manager.
SQL DB Primary Auxiliary Period 6 months 12 months Data 63 MB 108 MB Log Files 10 MB 10 MB Total Volume 73 MB 118 MB
Client Disk Space Requirements

The following table lists client PC disk space requirements for individual D.N.A. applications. Important You must have 100 MB free disk space on each server or client PC in order to run the D.N.A. 4.0 installation program.
SQL Database Caching for GUI Execution Local DB Memory map files N/A N/A
Application
Executable
Log Files N/A
D.N.A. Server
(EXE - 10 MB) N/A* (installation files - 1.5 MB)
Photos
N/A
N/A
N/A
N/A
N/A
Directory Manager Extension Manager
3.5 MB
N/A
N/A
[1.5 MB + 4.6 KB N/A x No. of subscribers] 0.6 MB x No. of nodes [see Extension Manager note]
9.4 MB
N/A
1 MB per 1000 17 KB x No. of subscribers nodes
Operator W k t ti
3 MB
N/A
6 MB/1000 b ib
N/A
7 KB per loggedi U ID 55
Workstation Performance Manager Numbering Plan Manager 4.5 MB N/A
subscribers 1 MB/1000 subscribers N/A N/A
in User ID 2 MB per node
1 MB
N/A
0.6 MB [see Numbering Plan Manager note]
*N/A = does not apply
Notes
Extension Manager Assume 20 KB per log file per day and there are 31 log files in a month and EMG is used everyday. The following month the log file will be overwritten. Numbering Plan Manager Assume 20 KB per log file per day for the entire network and there are 31 log files in a month and NPM is used everyday. The following month the log file will be overwritten.
Software Requirements
Windows
PCs running D.N.A. applications require Microsoft Windows NT Version 4.0, SP6A or Windows 2000. The "Microsoft Windows NT System Guide: or "Microsoft Windows 2000 System Guide" contains instructions for installing and configuring these operating systems. Important You must have 100 MB free disk space on each server or client PC in order to run the D.N.A. installation program. You should have all the recommended hardware installed on a PC before installing Windows NT. The installation program only loads device drivers for hardware detected during installation. If hardware is added later, after Windows NT installation, you will need to run the appropriate Control Panel application to load the necessary driver(s) and DLLs at that time from the installation CD. The Windows 2000 family consists of the Professional, Server, Advanced Server, and Datacenter Server versions. Windows 2000 Professional is a direct replacement for Windows NT 4.0 Workstation and is designed for standalone or network client PCs. It has a limited Web server and can handle two CPUs. Windows 2000 Server has all of the features of Professional in addition to supporting 4 CPUs with up to 4 GB of RAM. It has an Active Directory controller and a full version of Microsoft Internet Information Services 5.0, XML support, and integrated Virtual Private Networking. Windows 2000 Advanced Server can handle up to 8 CPUs, address 8 GB of RAM, and provides load balancing and clustering. The Windows 2000 Datacenter Server has the ability to handle 32 CPUs and address 64 GB of RAM. It also contains a high level of scalability.
56
Technical Guide
SQL Server/MSDE
D.N.A. applications use Microsoft SQL Server 7.0 with SP2 or MSDE with SQL Server SP2 as a centralized database server. In a network installation, SQL Server or MSDE is installed on the D.N.A. application server. For a stand-alone installation, SQL Server or MSDE is installed on the PC used for all D.N.A. applications.
Excel
If you are installing Performance Presentation Manager, Microsoft Excel 97 with SP2 or Excel 2000 must be installed on each PC where Performance Presentation Manager will be installed. Refer to the Microsoft Excel documentation for installation instructions.
Internet Tools
PPM Lite, Directory Browser, and Mobile Executive must be installed on a server containing Microsoft Internet Information Server (IIS 4.0 for Windows NT 4.0 or IIS 5.0 for Windows 2000). PPM Lite and Directory Browser works with Internet browsers Microsoft Internet Explorer 4.0 or later, or Netscape Navigator 4.0 or later. Warning PPM Lite will not function properly without a session state. The Session Timeout feature for your PPM Lite web site must not be disabled.
Connections
Connection Between Server PC and Client PC
For network installation of D.N.A. applications, each client PC must be connected to the central server PC that has the SQL database and Management Repository Server software. Each client PC is connected to the server PC using standard Ethernet or Token Ring cards and cabling. Once the client PC is connected to the server PC, use Windows 2000 to set up the network. Refer to the Windows 2000 documentation for a description of how to set up the network.
57
Client/MD110 Connections for Operator Workstation

Each client PC running the OWS application communicates with an MD110 via a COM port on the client PC, a CT Adaptor (R4A or higher) or TAU 2610 (R3A or higher) between the client PC and the MD110, and an ELU 25 or ELU 28 interface board in the MD110. The operator telephone also connects to the CT Adaptor or TAU. If the optional OWS Traffic Keyboard is provided, it is connected to a separate COM port on the OWS client PC. The following figure illustrates the possible connections between the client OWS PC and the MD110.
To connect an Operator Workstation client PC to an MD110 1 Connect the telephone wire from the ELU 28 board in the MD110 to the PBX jack on the CT Adapter or TAU 2610. 2 Connect the operator telephone (a D3 phone, for example) to the PHONE jack on the CT Adapter or TAU. 3 Connect the CT Adapter or TAU to an available COM port on the PC using an RS-232 cable. 4 If you are using a TAU, connect the power adapter to the TAU 2610 and check the power indicator. 5 Follow MD110 instructions to initialize the ELU port for the Operator Workstation. 6 If a headset is used, set up the headset based on the headset installation guide. 7 If the optional Traffic Keyboard is available, connect it to an available COM port on the PC.
Server/MD110 Connection for Operator Workstation

If the Operator Workstation message diversion or message waiting features are to be used, a connection between a COM port on the server PC and a GICI port on the ICU board for the MD110 is required. If multiple MD110 nodes are supported, a separate line is required for each node. This connection can be direct or remote. The following figures show cable connections for a direct connection and remote connection between the server PC and the MD110.
Direct/Local Connection
58
Technical Guide
Direct LAN/Telnet Connection
Remote Connection Through Public Switched Telephone Network (PSTN) After connecting the server PC to the MD110, initialize the GICI port on the ICU board as described in the MD110 documentation.
Configuration Management Hardware Connections

The D.N.A. MD110 Application Suite contains the following configuration Management applications. = = = = MD110 Support Extension Manager Performance Data Manager Numbering Plan Manager
Each server or client PC running a configuration management application communicates with an MD110 via a COM port or Ethernet connection on the client PC and either an IPU or NIU board in the MD110. These connections can be shared with other applications connecting to the MD110.
59
Make a direct connection by connecting an RS-232 cable between a COM port on the client PC and the IPU board on the MD110. TCP/IP LAN connection is achieved through an access agent connected to an IPU board. For a remote connection, a client PC is connected to a TAU or modem that connects to a TAU or modem on the MD110. The following schematics show connection configurations for direct and remote communication.
Hardware Connections for Extension Manager

Each server or client PC running Extension Manager communicates with an MD110 via a COM port or Ethernet connection on the client PC and either an IPU or NIU board in the MD110. These connections can be shared with other applications connecting to the MD110. To make a direct connection, connect an RS-232 cable between a COM port on the client PC and the IPU board on the MD110. TCP/IP LAN connection is achieved through an access agent connected to an
60
Technical Guide
IPU board. For a remote connection, a client PC is connected to a TAU or modem that connects to a TAU or modem on the MD110. The following schematics show connection configurations for direct and remote communication.
61
Checklists
Installation Checklists
This section provides checklists for D.N.A. server and client workstation installation. Use these checklists to assist in installing D.N.A. Application Suite Version components.
Using the Checklists

These checklists help insure that important installation issues are not overlooked. Perform the steps listed in each checklist and check off each item as you proceed through each D.N.A. component installation. For future reference, leave copies of these records with the customer and with the responsible Ericsson Customer Services location. For More Information For more detailed information, see the user documentation delivered with the individual D.N.A. products. Submit Your Comments Send comments and remarks about D.N.A. installation checklists and other Technical Guide issues to the EBC Enterprise Support Center.
Pre-installation Checklist
Use this pre-installation checklist to verify and identify all hardware and software components before beginning the installation process.
Installation Profile
List the your customer identity along with all software and hardware components to be included in this installation. Customer: Responsible Contact: Hardware Server: _____________________________________________ _____________________________________________ _____________________________________________ _____________________________________________ _____________________________________________ _____________________________________________ _____________________________________________ _____________________________________________ _____________________________________________ _____________
Software D.N.A.: Software MD110: Number of client PC's: Installation Eng. D.N.A.: Installation Date:
62
Technical Guide
Installation Component Verification

Microsoft Windows NT Server + Service Pack 6A or Windows 2000 Server/Advanced Server/Datacenter Server Microsoft Windows NT Workstation + SP6A or Windows 2000 Professional Microsoft SQL Server V7.0 + SP2 D.N.A. Access Agent: Base System Version R___ V__.__.__ Date: ______________ Note Microsoft SQL Server 7.0 or MSDE can be installed by D.N.A. Installation.
Installation Product Identification

Product ID NT/2000 Server: __________________ Product ID NT/2000 Workstation: __________________, __________________, __________________, __________________, __________________, __________________, Product ID SQL SERVER: __________________, Product ID (D.N.A Server): __________________, Product ID DMG: __________________, Product ID OWS: __________________, Product ID PMG: __________________, Product ID EMG: __________________, Product ID NPM: __________________, Windows is a trademark of Microsoft Corporation. The information in this document is subject to change without notice. ERICSSON MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Ericsson shall not be liable for errors contained herein nor for incidental or consequential damages in connection with the furnishing, performance or use of this material.
Account Strategy
Local/Domain Passwords for Windows NT/2000 (username/password) Please use the same case for all passwords, i.e. take all passwords lower case! NT/2000 Server Domain 'administrator account' (customer can decide): administrator/_______ NT/2000 Server Domain 'administrator account emergency' (only for Ericsson!): admin/xxxxxxx NT/2000 Workstations Local 'administrator account' (only for Ericsson!): admin/xxxxxxx OWS Workstations 'user account' (place user only in 'domain users'-group): ows/ows EMG/DMG/... Workstations 'user account' (place user only in 'domain users'-group): _______/_______ It is best that every FSC creates a common password: xxxxxxx = ...............
63
Check Hardware before You Start

Go into the PC's BIOS and check the following settings. = Primary Operating System: Windows NT/2000 = Check interrupts of serial port, parallel port, network card, graphic board = Others (i.e., Ethernet resources: check "twisted pair" or "BNC" settings)
OS and Database Installation

NT 4.0 Server
When your PC has a CD-ROM drive, you will need to boot from the 3 Microsoft NT boot-diskettes. These diskettes will detect your hardware, and will load the necessary CD-ROM drivers for installing Windows NT.
1 2 3 4 5 6
At the "Welcome to Setup" screen, press Enter. Press Enter again to allow Setup to detect mass storage devices in your computer. Press Enter again to continue without manually specifying additional devices. Read the Windows NT License Agreement and press <F8> to accept. At the "Windows NT Server Setup", you may need to change the Keyboard Layout. (E.g., in Belgium the Keyboard Layout needs to be set to: Belgian Dutch/French) Make sure that you "Format the partition using the NTFS file system" Note Compaq machines have a small partition pre-installed with Compaq diagnostic/Setup utilities. Do not delete this partition. It may be useful later on.
Choose the directory location where you want to install Windows NT. (The suggested location is \WINNT) 8 Press Enter to perform a thorough secondary examination of your hard disk(s) 9 Next, Setup will copy the Windows NT files to your hard disk. 10 When the files are copied, press Enter to restart your computer.
7
Note Remove diskette #3 from the disk drive. The PC will reboot, and start the 32-bit installation of NT/2000. The FAT formatted hard disk will be converted to NTFS.
11 Setup will request some information. Enter your Name and Organization 12 Enter the registration/licensing CD-Key. You will find this number on the yellow sticker on the back
of your CD case. 13 Licensing Mode: Select Per Server or Per Seat mode. Normally, select Per Server and the amount of CLIENT ACCESS LICENSES that are delivered. Note The Windows NT Server delivered via EBC (Ericsson OEM agreement) has 10 Client Access Licenses (CAL).
64
Technical Guide
14 Specify the Computer Name
Note Remember that every computer name needs to be unique on the entire Windows NT/2000 network, even if you work with separate domains. Therefore, do not use a common name like server. Also note that the customer does not have computer-names equal to your Ericsson L.C. site. Then you will get into problems when dialing-in via RAS (you then connect these two networks together, and this may result in NetBIOS-naming-conflicts). Please also try not to use underscores ( _) in the NetBIOS computer names, because these give problems in at the Domain Name Server (UNIX DNS). The underscores will be translated to dashes in DNS environments, and this can give unwanted results. Do not use computer names longer than 15 characters
15 Select the Server Type.
= Primary Domain Controller (PDC) = Backup Domain Controller (BDC) = Stand-Alone Server Note Select Primary Domain Controller if you want to create a new domain for D.N.A. Application Suite. Ericsson recommends a separate domain for the D.N.A. applications, because our engineers need to have an administrative account for the D.N.A. domain (e.g., to install D.N.A. services, etc.).
15 Enter the Administrator Account Password
Note By default NT will install an account called "Administrator". When installing the NT Server as a PDC (see above), then this account will be the domain-wide administrator account (full control for all objects). And this "Administrator" password can be used domain-wide (also on all clients connected to this domain). See Account Strategy.
16 Select YES to create an emergency repair disk 17 Select components:
= = = = = =
Accessibility Options Accessories Communications Games Multimedia Windows Messaging
Note For D.N.A. Application Suite installation, please accept the default selections
18 Select that Windows NT is Wired to the network
Note Verify that your network adapter is correctly installed (on a free IRQ), and physically connected to the network.
65
19 UNSELECT Install Microsoft Internet Information Server
Note D.N.A. Application Suite does not use the Windows NT IIS.
20 Select Start Search to look for Network Adapters
Note If NT does not find your Network Adapter, choose Select from list. If you have a standalone installation (only 1 PC, no network), also install networking. If you have no network card installed in the Server, select MS Loopback Adapter as Network Adapter (do this during NT installation). If you have a network adapter card installed in the PC, but no network cabling: You might need to loop the network adapter card. I.e. make a TP-loopback plug, otherwise, NT might complain every time you boot (this depends on the type of network adapter card installed).
21 Select the appropriate Network Protocol:
= NetBEUI = TCP/IP = IPX/SPX Note When the network is not segmented (no routers), use the NetBEUI protocol when the network has routers (segmented), select the TCP/IP protocol for the best performance, AND select only one Network Protocol. See document "D.N.A. Networking EBC/FSE-96:6918" for detailed information
22 Install the default Network Services 23 Click Next to install the selected components 24 Answer the Windows NT Setup questions according to your selected components (see step 19.)
Note Use the default settings unless you are experienced with customizing your configuration.
25 Supply the name of the D.N.A. Application Suite domain.
Note Preferably, use a unique name containing the letters DNA (e.g., NACKA_DNA).
26 Set the Date/Time Properties.
= Set the correct "Time Zone" = Enable "Automatically adjust clock for daylight savings changes" Note Please make sure that all the client PC's have the same "Date/Time Properties" settings as the server PC.
27 Set the Display Properties and use at least the following minimum settings:
= Color Palette: 256 colors = Desktop Area: 800 by 600 pixels = Refresh Frequency: as high as possible (test with monitor)
28 Windows NT Setup will now start copying files.
66
Technical Guide
29 Insert a floppy diskette labeled as "Emergency Repair Diskette", and let NT create it. 30 Restart the computer when installation is finished. 31 Select My Computer on the Windows NT Desktop, then Control Panel on the My Computer
dialog box. 32 On the control panel, select Regional Settings, then select the Regional Settings tab.: = Select the appropriate language (i.e. Dutch Belgian). = Also, Enable Set as system default locale Note This setting will also effect your localization of the D.N.A. Application Suite.
33 On the Control Panel dialog box, select Server. Type a Description for your server (e.g., Ericsson
D.N.A. Server) 34 On the Control Panel dialog box, select System, then select the Performance tab. Set the Application Performance slider control to None to give all programs equal amount of CPU time. 35 On the Control Panel dialog box, select System, then select the Performance tab. Set the Virtual Memory paging file size to: = Initial Size= 150Mb = Maximum Size= 150 MB Note For large installations, set the paging file to Initial Size = 250 MB and Maximum Size = 250 MB
36 On the Control Panel dialog box, select System, then select the Startup/Shutdown tab. 37 Select "Windows NT Server" from the Startup drop-down list. 38 Select Show list for 5 seconds 39 Check all Recovery checkboxes, and type %System Root%\MEMORY.DMP into the Write
debugging information to edit box. 40 Install the latest Microsoft Service Pack for Windows NT 4.0 Important There are no separate service packs for Windows NT Workstation and Windows NT Server.
41 In NT/2000 Event Viewer, set the Log Settings to:
= Maximum Log Size: 1024Kb = Event Log Wrapping: Overwrite Events as Needed
42 Repeat these settings for System, Security and Application Log 43 In the Windows NT Explorer, select Options on the View menu. Disable (uncheck) the Hide file
extensions for known file types option Note One of the features of the Windows NT Explorer is that it can hide file extensions for recognized file types. Unfortunately this has a side effect on some programs that rely on the file extension: they don't work.
67
44 Install Remote Access Service (RAS) on the customer's Server.
Note Enable only one account to dial-in (security reason). And set this account to dial-back to a fix number (Ericsson RAS machine).
45 In Command Prompt mode, enter:
DISKPERF -Y Note This command will enable the disk performance counters, the next time you reboot. This allows you to view the disk performance in NT's Performance Monitor. On a Pentium system, the performance-counter overhead will not be detectable.
46 Go to Control Panel. Select Network, Services, and Server. Set Server Optimization to Maximize
Throughput for Network Applications 47 If you have more than 10 D.N.A. clients, we suggest increasing the HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/Lanmanworkstation/Parameters registry value.
48 Change MaxThreads from 0x32 to 0x64 (if it does not exist, you may create it). This increases the
server's performance in updating clients. Increasing the workstation services MaxThreads parameter increases the number of kernel threads that the registry will create, thus allowing more operations to be outstanding at any given time. Note When you have a lot of warning messages of Event ID 232 in NTs Event Manager (Failed To Write To Named Pipe Port XXXX; NT Error Code=232), this value setting will improve performance of the Named Pipe LDB updating. Following this change you should not receive many of these warnings.
49 Verify that you have no errors in NT/2000's Event Viewer after a reboot.
NT 4.0 Workstation
Check Hardware before You Start
Go into the PCs BIOS and check the following settings (for Compaq PCs, press F10 during the system boot process). = Check setting Primary Operating System: Windows NT. = Check interrupts of serial port, parallel port, network card, and graphic board. = For Ethernet resources: check the twisted pair or BNC setting There are two methods of installing Windows NT. = Installation when you have a local CD-ROM drive build in your client computer = Network installation
68
Technical Guide
Installing Windows NT from a Local CD-ROM Drive

When your PC has a CD-ROM drive, you will need to boot from the 3 Microsoft NT boot-diskettes. These diskettes will detect your hardware, and will load the necessary CD-ROM drivers to load the NT system.
Installing Windows NT from a Network Drive

When your PC has no CD-ROM drive, you will need to boot your PC with a network boot diskette. You can then download the NT installation via the network. See the "D.N.A. Additional Technical Guide" on how to create such a network boot diskette. And run the "WINNT.EXE" command to start the installation.
1 2 3 4 5 6
At the "Welcome to Setup" screen, click Enter to set up Windows NT now. Press Enter again to allow Setup to detect mass storage devices in your computer. Press Enter again to continue and not to specify manually extra devices. Read the Windows NT License Agreement and press F8 to agree. At the "Windows NT Workstation Setup", you may choose to accept or change the Keyboard Layout. For example, in Belgium, Keyboard Layout needs to be set at: Belgian Dutch/French. Make sure that you Format the partition using the NTFS file system. Note Compaq machines may have a small partition pre-installed with Compaq diagnostic/Setup utilities. Please do not delete this partition, because it can be very useful later on.
Choose the location where you want to install Windows NT 4.0. (The recommended location is \WINNT). 8 Press Enter to perform an exhaustive secondary examination of your hard disk(s). Setup will now start copying the Windows NT files to your hard disk. 9 Remove the diskette # 3 from the disk drive 10 Press Enter to restart your computer. The PC will now reboot, and start the 32-bit installation of NT. The FAT formatted hard disk will now be converted to NTFS. Setup will ask issue additional prompts. = Setup Options: choose Typical = Enter your Name and Organization = Enter the CD-Key. You will find this number on the sticker on the back of your CD case. = Enter the Computer Name = Enter your Administrator Account Password
7
Remember, every computer-name needs to be unique on the entire network, even if you work with separate domains. Therefore, do not use a generic name like server. Also verify that the customer sight is not assigned computer names used by your Ericsson L.C. site. Otherwise, you will encounter problems when dialing-in via RAS. Once the two networks are interconnected, NetBIOS-namingconflicts may arise. Do not use underscores ( _) in NetBIOS computer names. Underscores in computer names can cause problems at the Domain Name Server (UNIX DNS). The underscores will be translated into dashes in DNS environments, causing unwanted results. Do not use computer names longer than 15 characters.
69
By default NT will install an account called "Administrator". This account will be added to the local account list (it will not be stored on the domain controller). Please see Account Strategy.
11 Select YES to create an emergency repair disk 12 Choose to install the most common Windows NT/2000 components. 13 Select Windows NT Wired to the network
Note Verify that your network adapter is correctly installed (on a free IRQ), and connected to the network
14 Select Start Search to look for Network Adapters
Note If NT does not automatically find your Network Adapter, choose Select from list. If you have a standalone installation (only 1 PC, and no network) also install networking:
15 If you have no network card installed in the Server PC, select MS Loopback Adapter as Network
Adapter (do this during NT installation). If you have a network-card installed in the PC but no network cabling, you may need to loop the network-card. I.e. make a TP-loopback plug, otherwise NT might complain whenever you boot (this depends on the type of network adapter). Select the appropriate Network Protocol. When the network is not segmented (no routers), use the NetBEUI protocol. When network has routers (segments), select TCP/IP protocol. For the best performance, select only one Network Protocol. See the "D.N.A. Application Suite Networking" document for more detailed information. 16 Install the default Network Services 17 Click Next to install the selected components 18 Answer the questions that the Windows NT Setup application asks. These questions will depend on your selected components (see above). Date and Time Properties 1 Use the default settings for date and time properties unless you are experience with custom configuration options. 2 Choose the appropriate Time Zone 3 Enable Automatically adjust clock for daylight savings changes. Make sure that all client PCs have the same "Date/Time Properties" settings as the server PC. Display Properties Use the following minimum display color and quality settings. = Color Palette: 256 colors = Desktop Area: 800 by 600 pixels = Refresh Frequency: as high as possible (test with monitor) Copying Files and Restarting The Windows NT Setup applications will now start copying.
1 2
Insert a floppy to create an Emergency Repair Diskette Restart the computer.
70
Technical Guide
Regional Settings Properties 1 Select the My Computer icon on the Windows NT desktop, then Control Panel. 2 Double-click Regional Settings on the Control Panel, then select the Regional Settings tab. 3 Select the appropriate language (e.g., Dutch Belgian). 4 Enable Set as system default locale. This selection will also effect localization of the D.N.A. Application Suite. NT Workstation PC Description 1 Select the My Computer icon on the Windows NT desktop, then Control Panel. 2 Select Server. 3 Type a description for the intended use for this NT Workstation client. (For example, "Ericsson D.N.A. Client OWS".) System Performance Settings 1 Select the My Computer icon on the Windows NT desktop, then Control Panel. 2 Double-click the System icon on the Control Panel, then select the Performance tab. 3 Set the Application Performance slider control to "Intermediate" (midway between None and Maximum). 4 Click the Change button. On the Virtual Memory dialog box, set the Paging File Size for Selected Drive to: Initial Size= (2 x installed physical memory) Maximum Size= (2 x installed physical memory) For OWS clients, the local database (LDB) files will be loaded into memory. If the physical memory is not big enough, virtual memory will be used. Microsofts recommended size for the paging file is equivalent to the total amount of available RAM, plus 12 megabytes.
5
Ericsson recommends the following formula for an OWS Client PC: Paging File Size: (OWS LDB Size + 40%) + (RAM + 12 MB) Example: With a total LDB size of 100 MB (large system), and your client PC has 48 MB of RAM, the recommended paging file size will be 200 MB.
System Startup/Shutdown Settings 1 Select the My Computer icon on the Windows NT desktop, then Control Panel. 2 Double-click the System icon on the Control Panel, then select the Startup/Shutdown tab. 3 In the System Startup box, select Windows NT Workstation 4.00 and Show list for 5 seconds. 4 For the Recovery box, ENABLE Write an event to the system log, DISABLE Send and administrative alert, ENABLE Write debugging information to %System Root%\MEMORY.DMP. Ericsson recommends disabling Send, an administrative alert so that the "Alerter" service does not need to be installed on the client computer. Install NT Service Packs Install the Microsoft Service Pack 5 for Windows NT 4.0. Both Windows NT Workstation and Windows NT Server use the same service packs. Use the same language in Service Pack as for your Windows NT language version. DO NOT INSTALL NT4.0 Service Pack 2! This can cause serious problems (see
71
D.N.A. newsgroup "erinet.ebc.dna"). For more information, see http://support.microsoft.com/support/. In \Programs\Administrative Tools\Event Viewer, set the "Log Settings" to: Maximum Log Size: 512Kb Event Log Wrapping: ENABLE Overwrite Events as Needed Repeat these settings for System, Security and Application Logs Display All File Extensions Windows NT Explorer provides the option of hiding file extensions for recognized file types. Unfortunately, some applications that rely on file extensions fail when extensions are hidden. They don't work. To display all file extensions 1 In Windows NT Explorer, select Options on the View menu. 2 DISABLE Hide file extensions for known file types. Enable Disk Performance Counters The following command will enable the disk performance counters, the next time you reboot. To view the disk performance in NTs Performance Monitor, beginning the next time you reboot, enable the disk performance counters. On a Pentium system, the performance-counter overhead will not be detectable.
1 2
Open the Windows NT Command Prompt Enter the command: DISKPERF -Y
Install Microsoft Excel

Install Microsoft Excel 97 or Excel 2000 before you install the D.N.A. Application Suite. Install Excel on all systems that will run Performance Presentation Manager. MS Office Service Pack 2 is required for Excel 97. Note MS Excel versions 5.0 and 7.0 are no longer compatible with D.N.A. 4.0. You must install a later version.
Reboot and Verify Setup Success

Reboot the PC and verify that you have no errors in NT/2000s Event Viewer.
Windows 2000 Upgrade

There are two methods of installing Windows 2000. = Installation when you have a local CD-ROM drive build in your client computer = Network installation
72
Technical Guide
Installing Windows 2000 from a Local CD-ROM Drive

1 2
Insert a Windows 2000 CD in the CD-ROM drive. Respond Yes to the following message. Would you like to upgrade to Windows 2000?
3 4
Follow the instructions in the Windows 2000 Setup Wizard and accept the default options. Select the appropriate configuration option for your network in the Windows 2000 Configure Your Server window.
Installing Windows 2000 from a Network Drive

When your PC has no CD-ROM drive, you will need to boot your PC with a network boot diskette. You can then download the NT installation via the network and run the "WINNT.EXE" command to start the installation.
SQL Server
Before installing SQL Server, you can run SQL Server Books Online directly from the compact disc. We recommend that you review the "Getting Started" and "Installing SQL Server" sections prior to installing this release. After installation of SQL Server, Service Pack 2 must be installed. When installing SQL Server from a network drive, do not use a Universal Naming Convention (UNC) file path such as: \\<Servername>\Microsoft\MsSql.70\x86\SETUP\SETUPSQL.EXE Instead, map a drive to the appropriate location and run the Setup program from the drive letter, for example: F:\MsSql.70\x86\SETUP\SETUPSQL.EXE SQL Server Books Online states that the Desktop Edition does not support read-ahead scans, merge joins, or hash joins. The Desktop Edition does support these features.
73
Installation
Use autorun.exe or SETUPSQL.EXE to install SQL Server 7.0 from a network drive or CD-ROM. Accept all the default installation options except for the following: Option
Do you want to run the SQL Server Upgrade Wizard to convert existing SQL Server 6.x databases to the SQL Server 7.0 data formats? Licensing Mode concurrent connections
Choose
Yes, run the SSQL Server Upgrade Wizard. (You will only see this option if you are upgrading from Version 6.5.) Per Server for The number of Client Access Licenses (CALs) should be equal or greater than the number of PCs that will connect to SQL Server. Also, count the Server PC as one connection.
Post-installation
Install SQL Server Service Pack 2.
Security
For security reasons, you should change the default sa Login ID and blank password of MS SQL Server.
1 2 3
In the Service Manager window open the registered D.N.A. Servers tree and the Logins tree. Double-click on sa to open the Manage Logins dialog box. Change the Login Name and Password and click Modify. Note After changing the "sa" password, also change your "Login ID Password" for the registered D.N.A. Server in SQL Enterprise Manager. You can do this by right-clicking the Server Name.
Unattended SQL Server Installation

Unattended SQL Server installation can be convenient if you want to install multiple instances of SQL Servers with identical configurations. The Setup program reads the installation settings from a predefined installation information file instead of prompting in the SQL Server installation wizard. The D.N.A. application suite installation program will prompt you to choose between SQL Server and MSDE if a database application does not exist on the server. If you select SQL Server, you are asked for the SQL Server CD key, setup files, and the location of the installation information file. The installation information file location defaults to the template that comes with D.N.A. installation. The default installation information file provided in the D.N.A. application suite installation contains all recommended options for the SQL Server Enterprise edition. Note D.N.A. database files must be deleted manually after MSDE un-installation. The MSDE uninstallation process only removes the databases installed at MSDE installation time such as Master database. All databases created later have to be removed manually.
74
Technical Guide
Database Upsizing
To change your D.N.A. database configuration at any time after the initial installation:
1 2 3
Re-run the D.N.A. installation program. Choose the Resize Database button on the Ericsson Setup dialog box. Respond, based on your requirements, to the prompts and instructions from the installation wizard.
Memory
SQL Server 7 is configured dynamically. However, memory should be limited to for SQL Server use. To set a maximum value for memory (Enterprise Manager) 1 Expand a server group. 2 Right-click a server. 3 Click Properties. 4 Click the Memory tab. 5 In the memory box, select maximum size (MB), and slide it to the desirable position.
SNMP Master Agent

Windows NT
The D.N.A. SNMP agent requires Windows NT service pack 6A. Make sure you have the service pack and the Windows NT 4.0 distribution CD handy before starting this installation. You must also have administrator privileges to perform this installation.
1 2 3 4 5 6
Open the Control Panel by selecting Start Settings Control Panel. Open the Network dialog box by double-clicking on Network. Click the Services tab. Open the Select network Service dialog box by clicking the Add button. Scroll down in the list-box until you see SNMP Service. Click once on that line to select it and then click the OK button. After a few seconds a the Windows NT Setup dialog-box is opened. This means that Windows needs to know where it can find the necessary files to complete this installation. These files are on the Windows NT distribution CD. Insert the CD in the CD-drive of this machine or enter the path to where this CD is. When this is done, click OK and the process will continue. After the SNMP installation is done, the SNMP properties screen will come up. This dialog-box has three tabs. On the first tab, named Agent, enter your name in the contact field and the address where the machine is located in the second text field. You can leave the checkboxes under Service with default values. On the Traps tab, enter public as community name and click the Add button next to it. Click the Add button under the Trap Destinations list and enter the IP address or hostname of the machine running EVM in the small dialog-box that pops-up and click Add to close it. On the Security tab, make sure Send Authentication Trap is checked, that public has READ CREATE rights and that Accept SNMP Packets from Any Host is checked. These settings are a good starting point since they dont put many restrictions on the SNMP traffic. When you feel comfortable with SNMP configuration, feel free to change them.
75
10 When you now click the OK button, the Microsoft SNMP Properties dialog-box will close and
youll have to restart the machine. 11 After the machine starts up again you might get an error message about a function entry point not found. This is normal if you had service pack 6A installed before the SNMP installation. The solution is to re-apply the service pack again.
Windows 2000
1 2 3 4 5 6 7 8
9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
24
Open the Control Panel by selecting Start Settings Control Panel. Open the Add/Remove Program Properties dialog box by double-clicking on Add/Remove Windows Components. Scroll down to Management and Monitoring Tools. Click this line once (dont click in the checkbox). Click the Details button. A new dialog-box appears. Find the line Simple Network Management Protocol, click in the checkbox to enable it and click the OK button. Click the Next button; Windows2000 will now start to install this component. After a few seconds the Insert disk message box is opened. Click OK. The Insert disk dialog box is opened. This means that Windows needs to know where it can find the necessary files to complete this installation. These files are on the Windows 2000 distribution CD. Insert the CD in the CD-ROM drive of this machine or enter the path to where this CD is located. Click OK to continue the process. When the Windows Component Wizard is displayed, click the Finish button. This returns you to the Add/Remove Windows Components dialog box. Click Close. Close the Control Panel. Click Start Programs Administrative Tools Services. In the right pane, find the line SNMP Service, right-click and choose Properties. The SNMP Service Properties dialog box is opened. This dialog-box has seven tabs. Click the Agent tab. Enter your name in the Contact field and the address where the machine is located in the second text field. You can leave the checkboxes under Service with the default values. Click the Traps tab. Enter public as the community name and click the Add button next to it. Click the Add button under the Trap Destinations list and enter the IP address or hostname of the machine running EVM in the small dialog-box that pops-up. Click the Add button. Click the Security tab. Make sure Send Authentication Trap is checked, that public has READ CREATE rights, and that Accept SNMP Packets from Any Host is checked. These settings are good starting points since they dont put many restrictions on the SNMP traffic. When you feel comfortable with the SNMP configuration, feel free to change them. Click OK to save these settings. Remember to stop and re-start the SNMP service to make the settings active.
76
Technical Guide
See Also Networking (SNMP) Access Agent SNMP Agent
D.N.A. Installation
About Installation
Before installing D.N.A. application software, be sure all PCs and MD110 nodes are set up as described in Hardware Requirements. Software installation for most D.N.A. applications is separated into server installation and client installation.
Hardware Connections
You must perform or verify installation of all necessary communications and signaling connections before proceeding to software installation.
Software Installation
Server Installation. For a D.N.A. Server installation, all server software is installed on one PC, and the client software is then installed on one or more PCs connected to the server. Client Installation. Client software can be installed from a network D.N.A. Server or directly from a D.N.A. software CD-ROM inserted in the client PC's CD-ROM drive.
Application Suite Installation

You can install D.N.A. applications on a client PC or server. When you install the D.N.A. applications, you may include just the components you want, ranging from a minimal configuration to the entire suite of D.N.A. applications. The full installation installs all D.N.A. components with the exception of the Numbering Plan Manager application. MD110 D.N.A. runs on the following Microsoft Windows operating systems. Windows NT 4.0 Workstation Windows NT 4.0 Server Windows 2000 Professional Windows 2000 Server Windows 2000 Advanced Server Warning It is against Microsoft's End User License Agreement to use, in any way, Windows NT 4.0 Workstation or Windows 2000 Professional as a server.
77
Installation Features
New installation features for D.N.A. include: = Silent Installation You may use the graphical D.N.A. setup.exe interface, or the "Silent Installation" method supported by a pre-configured .ini file. (Silent Installation only applies to client installations.) = Auto-run is now supported for compatible CD-ROM drives. = Customizable System The application licenses must be turn on through License Administration and user privileges through User Configuration. The node information such as node name, communication method, etc. must be set through MD110 Support. The user-defined fields in the Directory database must be defined through Directory Configuration. = Pre-configured System The installation sets up licenses and turns on the application licenses. The defined users and privileges will be assigned and the node information and communication with the MD110 will be configured. The desired user-defined fields for Directory Manager will also be defined. Silent Installation D.N.A. now supports "hidden installations" that allow system administrators to control client installations without having to be physically present at installation sites. Auto-Run D.N.A. provides auto-run support for PCs that support that feature. When you insert the software installation CD into an auto-run compatible PC, the installation process is automatically started. The system will display an installation panel containing the following auto-run options. = = = = = = Install Application Suite Install PPM Lite Install Directory Browser Install Mobile Executive View Technical Guide Exit
Unattended SQL Server Installation

Unattended SQL Server installation can be convenient if you want to install multiple instances of SQL Servers with identical configurations. The Setup program reads the installation settings from a predefined installation information file instead of prompting in the SQL Server installation wizard. The D.N.A. application suite installation program will prompt you to choose between SQL Server and MSDE if a database application does not exist on the server. If you select SQL Server, you are asked for the SQL Server CD key, setup files, and the location of the installation information file. The installation information file location defaults to the template that comes with D.N.A. installation. The default installation information file provided in the D.N.A. application suite installation contains all recommended options for the SQL Server Enterprise edition
78
Technical Guide
Pre-Configured System
You can use a pre-configured installation file (dna.cfg) to retrieve system information and make the installation automatic. The dna.cfg file contains default settings for pre-configured information that you can edit for your installation. The installation program prompts you for the location and file name. In addition, the installation program validates the pre-configured information file to make sure all required information is defined correctly. License Application Licenses All installed applications or utilities automatically enabled. Number of Extensions and Subscribers The Number of extension licenses can be defined and are stored in the security database if Extension Manager or PMG is installed. The number of subscriber licenses can also be defined if Directory Manager or Operator Workstation is installed. Number of Concurrent Users The number of users of an application that are allowed to have the application active at any one time can be defined. User Names and Privileges There are two types of users can be defined in the pre-configuration information file: Administrator Account All application with pre-defined (highest privilege) privileges are assigned. Regular User Account The desired application with associated pre-defined privilege (highest privilege) will be assigned. MD110 Communications Node Information All information associated with a node can be defined. For example, Node name, BC release, MD password. Communication with MD110 Your choice of communication with the MD110 can be defined. For example, Direct, Modem, IPU and NIU. The registry settings are loaded to the client system for all installed applications that requires the MD110 interface, such as MD Support, Extension Manager, and PDM. GICI Configurations You can specify GICI configuration methods, including Direct, Telnet, and NIU. MD110 Data Synchronization After installation has completed successfully and the system is rebooted, the system will be automatically logged on with the NT user and password you defined. The synchronization of MD110 data then can be started automatically from a batch file that contains the command for data synchronization for each individual node. The synchronization is executed one node at a time. User-defined Fields for Directory Manager The desired user-defined fields for all categories such as Department, Profile, Person, Confidential, Room, Function, External, and Information can be defined. The searchable flag and icon can also be identified.
79
Configuration File Parameters You can edit the following parameters in the dna.cfg file for a pre-configured installation. [NTlogon] Validate=YES (validate user) DomainName=EBUNT UserName=qbuniq Password=123456 ;sample of MDS remote connection with phone number specified [MDSConfiguration1] Enable=1 ConnectionType=REMOTE SiteName=Test Remote NIU_Password=HELP IPU_Password=HELP NIULoginUserName=MDUSER ASB501Release=8 Port=1 phonesetup1=6632 ;sample of MDS direct connection [MDSConfiguration2] Enable=1 ConnectionType=DIRECT SiteName=Test Direct NIU_Password=HELP IPU_Password=HELP NIULoginUserName=MDUSER ASB501Release=8 Port=2 ;sample of MDS telnet connection [MDSConfiguration3] Enable=1 ConnectionType=TELNET TelnetSetup1=195.100.112.120,4,,, TelnetSetup2=195.100.101.182,3,agent,FreakShow:-), SiteName=Test Telnet NIU_Password=HELP IPU_Password=1HELP NIULoginUserName=MDUSER ASB501Release=8 [GICIPortConfiguration1] Enable=1 PortName=test direct
80
Technical Guide
ConnectionType=DIRECT DNFillerCharacter=@ InformationSystemID=00 MaxDNLength=5 MaxTerminalID=2 BaudRate=9600 DataBits=8 StopBits=1 Parity=1 FlowControl=0 OutputTimeDelay=50 Port=COM2 [GICIPortConfiguration2] Enable=1 PortName=test niu ConnectionType=NIU DNFillerCharacter=A InformationSystemID=00 MaxDNLength=5 MaxTerminalID=2 NIUPortID=12345 [GICIPortConfiguration3] Enable=1 ConnectionType=TELNET PortName=test telnet DNFillerCharacter=@ InformationSystemID=00 TelnetAddress=195.100.113.98 TelnetAccount=abcd TelnetPassword=test OutputTimeDelay=100 DNFillerCharacter=64 InformationSystemID=00 MaxDNLength=8 MaxTerminalID=2 [Licence] Enable=1 NumberOfExtensions=100 NumberOfSubscribers=200 NumberOfConcurrentUsers=-1 [UserPrivileges] Enable=1 tstusr=test user;test user description;USER;MDS,1,2,3;PCOPI
81
tstusr2=test user2;test user2 description;all,3 [UserDefinedFields] Enable=1 ;Number of Profile fields is even number from 8 to 20 NumberProfileFields=14 Profile1= Prof Assistant,6, Yes, Assistant Profile2= Prof Cost_Center, 1, No,None Person1 = Person Home, 43, Yes, HOME Confidential1 = Conf password, 53 Department1 = My department, 31, NONE External1 = My external, 3, MAIL Function1 = function Cellular number, 38, Yes, CELLULAR Room1= room Secretary Name, 6, NO, SECRETARY Information1 = My info, 29, yes, NONE
Installation Dialog Explanations

This section helps you to prepare for the decisions and responses required during the installation process. You will encounter a different prompts and dialog boxes depending on whether yours is a new installation, a re-installation, a server installation, or a client installation.
New Installation Dialogs (Server)

This table lists the dialog boxes and prompts displayed when you perform a new installation.
Dialog Box Name and Options Welcome Explanation Overview of what the installation will accomplish, instructions for closing other applications, copyright warnings. Conditions for using the installed D.N.A. software. Choose whether the PC you are setting up will be a D.N.A. Server or Client. The server installation creates a \\dna_s directory containing selected applications. The client installation places selected applications in a \\dna_c directory and assigns the connected server as the local server. If installation cannot detect database engine this dialog box is displayed. You must have licensed SQL Server if you choose the Microsoft SQL Server option. Microsoft Data Engine is provided by the D.N.A. Installation. This dialog box is displayed when you choose Microsoft Data Engine. Enter or browse for the destination of MSDE files. The default is the MSSQL7 directory on the OS drive. This dialog box is displayed when you choose Microsoft SQL Server. Enter or browse for the destination of SQL Server files. The default is the MSSQL7 directory on the OS drive
Software License Agreement Installation Type Server (option button) Client (option button)
Installation Type Microsoft SQL Server Microsoft Data Engine
Choose Destination Location
SQL Server Installation Configuration Destination Path Installation Files
82
Technical Guide
Configuration File CD Key
MSSQL7 directory on the OS drive. Enter or Browse for the location of the SQL Server setup files. Enter the location of the SQL Server configuration file. The D.N.A. Installation displays the default configuration file provided by the installation package. Enter the SQL Server CD Key if required. Registration information for this installation. Fill-in or accept the contents of the Name and Company fields.
User Information Name Company Registration Confirmation Yes (button) No (button) Nodes and Extensions for Database Number of Nodes (drop-down list) Total Number of Extensions (drop-down list) Select Installation Method Typical (button) Custom (button)
Choose whether or not the user information you just entered is accurate.
Select from 1-256 nodes and 500 to 200,000 extensions for your network. This information is used to determine the amount of disk space needed for the installation. You may change these options. Choose Typical to install all available D.N.A. components (applications, databases, and D.N.A. Server support utilities and components), excluding Numbering Plan Manager. Choose Custom to select specific components to install, including Numbering Plan Manager. Choose Professional for fully configurable Operator Work Station interface and options. Choose Basic for no configurable options and no remote search capabilities. Select Centrex for a BSS (service provider) configuration. Click the Change button to change the number of extensions for a selected node. Allows you to choose database sizes for primary and auxiliary databases, and for storing active measurements. This option can be skipped. To use this option, enter the full path name of the pre-configuration file or browse to it. Check Run MD Support synchronization if you want installation to start MD110 data synchronization after installation is completed. Click Next to accept the default folder for your installation, or click the Browse button to select another. Type the assigned SQL password or, if no password was assigned, leave the field blank and click Next. Accept or choose locations for D.N.A. SQL database components. Select or unselect tasks that will be scheduled for automated execution after the installation completes.
OWS Level Selection Professional (option button) Basic (option button) Centrex (option button) Extensions Per Node Performance Manager Databases Setup DNA PreConfiguration Option File Name Checkbox
SQL Administrator Password Data Files and Log Files Locations RDS Schedules
83
Start Copying Files
Review a comprehensive summary of your installation choices. Click Next to begin the installation process based on your choices. Click Back to change your selections before proceeding. Click Cancel to abort the installation. After the installation has finished, this dialog box displays a list of the D.N.A. components installed. It also displays any problems encountered during the installation. Choose Yes, I want to restart my computer now to restart your PC and complete the installation process. Choose No, I will restart my computer later to close the installation program and restart the PC later.
Summary Installations
Setup Complete
New Installation Dialogs (Client)

This table lists the dialog boxes and prompts displayed when you perform a new installation.
Dialog Box Name and Options Welcome Explanation Overview of what the installation will accomplish, instructions for closing other applications, copyright warnings. Conditions for using the installed D.N.A. software. Choose whether the PC you are setting up will be a D.N.A. Server or Client. The server installation creates a \\dna_s directory containing all standard applications. The client installation places selected applications in a \\dna_c directory and assigns the connected server as the local server. Registration information for this installation.
Software License Agreement Installation Type Server (option button) Client (option button)
User Information Name Company Registration Confirmation Yes (button) No (button) D.N.A. Server Name
Choose whether or not the user information you just entered is accurate.
Type the network name of the D.N.A. server you wish to use as your installation source. Be sure to select a server that contains all the components you need to install. Choose Typical to install the recommended D.N.A. components (applications, databases, and D.N.A. Server support utilities and components), excluding Numbering Plan Manager. Choose Custom to select specific components to install, including Numbering Plan Manager. Choose Professional for fully configurable Operator Work Station interface and options. Choose Basic for no configurable options and no remote search capabilities. Select Centrex for a BSS (service provider) configuration.
Select Installation Method Typical (button) Custom (button)
OWS Level Selection Professional (option button) Basic (option button) Centrex (option button)
84
Technical Guide
Click Next to accept the default folder for your installation, or click the Browse button to select another. Review a comprehensive summary of your installation choices. Click Next to begin the installation process based on your choices. Click Back to change your selections before proceeding. Click Cancel to abort the installation. After the installation has finished, this dialog box displays a list of the D.N.A. components installed. It also displays any errors encountered during the installation. Choose Yes, I want to restart my computer now to restart your PC and complete the installation process. Choose No, I will restart my computer later to close the installation program and restart the PC later.
Start Copying Files
Summary Installations
Setup Complete
Re-Installation Dialogs
This table lists the dialog boxes and prompts displayed when you install D.N.A. on a PC containing existing D.N.A. components (i.e., previously installed \\dna_s or \\dna_c directories).
Server Installation
D.N.A. application setup now recommends which applications to install and where to install them. For example, you will probably want to choose the Typical option in the installation wizard, which installs all D.N.A. applications. Alternatively, you may choose the Custom option that allows you to select individual applications to include in the installation, omitting those you do not want. The D.N.A. Server installation process installs the D.N.A. operating platform, all applications (except Directory Browser, Mobile Executive, and Outlook Integration), and all administrative tools on your Windows NT/2000 Server PC. Windows NT/2000 Workstation client PCs may then connect to this server to install D.N.A. applications and support utilities. Important If youre using a virus-protection utility, disable it before you run the D.N.A. Setup program. Also, close the control panel and any open Windows NT/2000 applications. Perform the following procedures to install D.N.A. on a server PC. For this purpose, a server PC is one running the Windows NT/2000 Server operating system.
85
Auto-Run Installation
Use this procedure to install from CD-ROM on a PC that supports auto-run. Insert the D.N.A. CD in the CD-ROM drive. If supported by your PC, auto-run will activate the installation program and you will be presented with the following auto-run options. = = = = = =
1 2
Install Application Suite Install PPM Lite Install Directory Browser Install Mobile Executive View Technical Guide Exit Select Install Application Suite. Click the Server installation option button and follow the instructions from the installation wizard.
Taskbar Installation
Use this procedure to install from the network, or from CD-ROM on a PC that does not support autorun. 1 If you are installing from a network location, connect to it. If you are installing from CD-ROM, insert the installation CD. 2 Click Start, Run on the Windows NT/2000 taskbar. 3 Type the network path to the desired setup program (for example, installing from CD, type: d:\dna\setup.exe; installing from network, type: d:\dna_s\mrs\InstallationFiles\ClientInstallation\setup.exe). Or, use the Browse button to browse to the appropriate setup.exe program file. 4 Click the Server installation option button and follow the instructions from the installation wizard.
Server Installation Options

At any time after D.N.A. server software has been installed, you may use the Auto-Run or Taskbar installation methods explained above to add, re-configure, and remove components using the following options.
86
Technical Guide
Option
Explanation
Add Components Allows you to add D.N.A. components not already installed. Install Locale Reinstall Remove All Installs new language capabilities to installed components. Allows you to repeat the last installation to restore missing or corrupted files. Deletes all installed D.N.A. components. (You may also perform this task using Add/Remove Programs from the Windows NT/2000 Control Panel.)
Resize Database Allows you to change the number of nodes, extensions, and other capacity parameters for the existing installation.
Add Components
On the Ericsson Setup dialog box, select Add Components. You will encounter the following dialog boxes when adding D.N.A. components to an existing installation. Select Components Lists components available to be added. Locale Support Select language support for the new applications. Database Application Administrator Password Data Files and Log Device Locations Start Copying Files Summary Installations Setup Complete Setup program has performed the requested upsizing tasks. Click Finish. The system will now restart to complete the installation. Refer to Installation Dialog Explanations for more information. Upsizing Server Components You will encounter the following dialog boxes when upsizing D.N.A. components in an existing installation. On the Ericsson Setup dialog box, select Resize Database. Refer to Installation Dialog Explanations for more information. Nodes and Extensions for Database Upsizing Components Lists components eligible for upsizing. Upsizing Extension Per Node Allows you to change node and extension quantities. Upsizing [Application ...Setup] SQL Administrator Password Start Copying Files Summary Installations Setup Complete Setup program has performed the requested upsizing tasks. Click Finish.
87
Stand-alone Installation
For a stand-alone installation on a non-networked PC, a single PC performs both the server and client roles
Client Installation
The latest D.N.A. installation application improves the installation process. It now recommends which applications to install and where to install them. For example, youll probably want to choose the Typical option in the installation wizard, which installs all the D.N.A. applications available on the selected D.N.A. server. Alternatively, you may choose the Custom option that allows you to select individual applications to include in the installation, omitting those you do not want. Important If youre using a virus-protection utility, disable it before you run the D.N.A. Setup program. Also, close any open Windows NT/2000 applications.
Auto-Run Installation
Use this procedure to install from CD-ROM on a PC that supports auto-run. Insert the D.N.A. CD in the CD-ROM drive. If supported by your PC, auto-run will activate the installation program and you will be presented with the following auto-run options. = = = = = =
1 2
Install Application Suite Install PPM Lite Install Directory Browser Install Mobile Executive View Technical Guide Exit Select Install Application Suite. Click the Client installation option button and follow the instructions from the installation wizard.
Taskbar Installation
Use this procedure to install from the network, or from CD-ROM on a PC that does not support autorun.
1 2 3
If you are installing from a network location, connect to it. If you are installing from CD-ROM, insert the installation CD. Click Start, Run on the Windows NT/2000 taskbar. Type the network path to the desired setup program (for example, installing from CD, type: d:\dna\setup.exe; installing from network, type: d:\dna_s\mrs\InstallationFiles\ClientInstallation\setup.exe). Or, use the Browse button to browse to the appropriate setup.exe program file. Click the Client installation option button and follow the instructions from the installation wizard.
Client Installation Options

At any time after D.N.A. client software has been installed, you may use the Auto-Run or Taskbar installation methods above to add, re-configure, and remove components using the following options.
88
Technical Guide
Note You must perform these operations using the D.N.A. server that was the source for the original installation. To change to a different server, you must first un-install all D.N.A. software and repeat the installation using the new server.
Option Explanation
Add Components Allows you to add D.N.A. components not already installed. Install Locale Remove All Installs new language capabilities to installed components. Deletes all installed D.N.A. components. (You may also perform this task using Add/Remove Programs from the Windows NT/2000 Control Panel.)
Silent Installation
You may now offer customers file-directed D.N.A. client installation assistance without being present at the installation site. This installation feature supports client New Installation, Re-installation, and Add Component options. Client Un-install is NOT supported. Note Your users can run silent client setup from the D.N.A. Application Suite CD-ROM or from a local D.N.A. server. For the CD-ROM method, however, you must maintain an input file such as dnasuite.ini and use it as the input file for running the setup. The installation process gets system setup information from a .ini file created by the system administrator. The administrator provides approved installation parameters via a configuration (.ini) file. The client PC user can then initiate the installation. The installation will proceed automatically without further intervention.
89
Modifying the Setup (dnasuite.ini) File

As a starting point, use the dnasuite.ini file (located in the same installation directory as setup.exe) that comes with the D.N.A. installation software. Copy and carefully modify this file for your needs. DO NOT delete any parts of this file, since all existing statements are used during the installation process. Make the following changes to the temporary installation file.
dnasuite.ini [SETUP] Statement InstallClientPath= Notes Type a destination path for the installed files on the client PC, or leave blank to accept the default location (c:\dna_c). Type the name of your local server. If left blank, the install program will prompt the user for a response. This is a required parameter.
ServerName=
LaunchEXE=ADO\MDAC_TYP.EXE, You must include the '/Q' switch /Q, /C:"setup /QNT",WAIT to run ADO in quiet mode. [OWS] Install=1 Level=Professional Set to 1 to install, 2 to not install* Level options are: Professional for fully configurable Operator Work Station interface and options; Basic for no configurable options and no remote search capabilities; Centrex for a BSS (service provider) configuration. Set to 1 to install, 2 to not install* Set to 1 to install, 2 to not install* Set to 1 to install, 2 to not install* Set to 1 to install, 2 to not install* * You can only install components that have been installed on the connected D.N.A. Server.
[DMG] [PMG] [EMG] [NPM]
Install=1 Install=1 Install=1 Install=1
Installation Procedure
At the client PC, the installer performs the following steps.
1 2
From the taskbar and click Start, Programs, Command Prompt. The Command Prompt window will be displayed. To get command prompt help, type: command SETUP /?
At the client PC, use the following setup command to execute the file-driven installation. (See details on SETUP command below.) SETUP.EXE silent ini=full path of dnasuite.ini
90
Technical Guide
Using the Setup Command There are three versions of the setup command for silent installation. One each for: New Installation, Re-Install, and Add Components. Type
New Installation
Setup Command
SETUP.EXE silent ini=[full path of dnasuite.ini] SETUP.EXE silent reinstall
Notes
You can only install components that have been installed on the connected D.N.A. Server. Parameter ini=filename.ini is not needed. The setup will process using the current installed .ini file settings. You can only install components that have been installed on the connected D.N.A. Server.
Re-install
Add Components SETUP.EXE silent add ini=[full path of Setup will add components that have been flagged Install=1 dnasuite.ini] You can only add components that have been installed on the connected D.N.A. Server.

The D.N.A. Typical installation option does not install the Numbering Plan Manager application. However the Custom installation option allows you include Numbering Plan Manager in your installation selections.
Server Installation
NPM can only be installed on a server using the Custom option for a new installation, or from the Add Component option for an existing installation.
Client Installation
For a new installation, NPM can only be installed if it is available on the connected server.
D.N.A. provides auto-run support for PCs that support that feature. When you insert the software installation CD into an auto-run compatible PC, the installation process is automatically started. The system will display an installation panel containing the following auto-run options. = = = = = = Install Application Suite Install PPM Lite Install Directory Browser Install Mobile Executive View Technical Guide Exit
91
Use this procedure (if you are not using Auto-Run) to install this application after the initial installation of other components.
1
Insert the D.N.A. CD in the CD-ROM drive. -orIf youre installing from a network location, connect to it.
2 3 4 5 6
Click Start, Run on the Windows NT/2000 taskbar. Type the network path to the desired setup program (for example d:\setup). Or, use the Browse button to browse to the appropriate setup.exe program file. Click the Client installation option button and follow the instructions from the installation wizard. Choose Add Components when the Ericsson Setup dialog box appears. Check the Numbering Plan Manager check box when the Follow the remaining instructions from the setup wizard.
Upgrade D.N.A. Application Suite

Only one upgrade option is available. Selecting this option to upgrade to D.N.A. version 5.0 from versions 3.0, 4.0, or 4.1. This applies to both server and client upgrades.
PPM Lite
The basic D.N.A. Server client must be installed before you can install PPM Lite. This section explains installation requirements and procedures for Performance Presentation Manager Lite (PPM Lite). No installation steps are necessary for PPM Lite clients. Users simply point their browsers to a PPM server and enter their user ID and password. Warning PPM Lite will not function properly without a session state. The Session Timeout feature for your PPM Lite web site must not be disabled.
Installing with Auto-Run

D.N.A. provides auto-run support for PCs that support that feature. When you insert the software installation CD into an auto-run compatible PC, the installation process is automatically started. The system will display an installation panel containing the following auto-run options. = = = = = = Install Application Suite Install PPM Lite Install Directory Browser Install Mobile Executive View Technical Guide Exit
Select Install PPM Lite to install from the Auto-Run interface. Important If youre using a virus-protection utility, disable it before you run the D.N.A. Setup program. Also, close the control panel and any open Windows NT/2000 applications.
92
Technical Guide
To install PPM Lite on a server PC 1 Insert the D.N.A. installation CD in the CD-ROM drive. -orIf youre installing from a network location, connect to it.
2 3 4 5 6
Find and open the DNA50_installation\PPM Lite folder. Double-click setup.exe to start the installation. Proceed through the Welcome, License Agreement, and User Information dialogs. For New Virtual Directory, accept the PPM Lite IIS default, or type another choice. Accept the default settings or provide your preferences for the Locale Support and Destination Location dialogs. The installation program will copy files and complete the installation settings. When the installation completes, choose Yes, I want to restart my computer now. The system will shutdown, restart, and the installation will be complete.
Installation Options
The PPM Lite installation provides Reinstall and Remove All options. Remove All can run from CD and Control Panel.
Option Reinstall Explanation Allows you to repeat the last installation to restore missing or corrupted files.
Remove All Deletes all installed PPM Lite components. (You may also perform this task using Add/Remove Programs from the Windows NT/2000 Control Panel.)
Upgrade PPM Lite

Only one upgrade option is available. Selecting this option to upgrade to PPM Lite version 5.0 from version 4.0. PPM Lite uses D.N.A. security and the user account needs to be recreated through User Configuration.
93
Directory Browser
This section explains installation requirements and procedures for D.N.A. Directory Browser. No installation steps are necessary for Directory Browser clients. Users simply point their browsers to a D.N.A server and select the destination directory folder. Directory Browser is installed on an Internet server. Even though the Internet server and the D.N.A. server can be on the same machines, we recommend they be on separate machines for better performance. In addition, Internet servers are periodically taken down for maintenance. AppLink can also be installed on the same server as Directory Browser. AppLink is a separate installation. If you install Directory Browser on an Internet server, LDS must be running on that server. Warning Directory Browser will not function properly without a session state. The Session Timeout feature for your Directory Browser web site must not be disabled.
Installation and Uninstall

The Directory Browser installation installs or updates all files to run D.N.A. Directory Browser. To clean up Directory Browser installation, simply go to Windows NT/2000 Control Panel, Add/Remove programs icon, select D.N.A. Directory Browser.

D.N.A. provides auto-run support for PCs that support that feature. When you insert the software installation CD into the CD-ROM, an auto-run compatible PC, the installation process is automatically started. The system displays an installation panel containing the following auto-run options. = = = = = = Install Application Suite Install PPM Lite Install Directory Browser Install Mobile Executive View Technical Guide Exit
Select Install Directory Browser to install from the Auto-Run interface.
Important If you're using a virus-protection utility, disable it before you run the D.N.A. Setup program. In addition, close the control panel and any open Windows NT/2000 applications.
94
Technical Guide
To install Directory Browser on a server PC 1 Insert the D.N.A. installation CD in the CD-ROM drive. -orIf you're installing from a network location, connect to it. Double-click ddb/setup.exe to start the installation. For the Database Server Name dialog, Type the Windows NT/2000 network name of the PC containing the desired D.N.A. SQL database. For the Choose Destination Location dialog, accept the default, or type another choice. After review the selection, the installation program will copy files and complete the installation settings. When the installation completes, please do go through the Readme.txt for more details to use D.N.A. Directory Browser.
2 3 4 5 6
Client Installation
When running Directory Browser on a separate D.N.A. client installation, we recommend that you setup and run Ericsson LDS NT/2000 service on the same PC as the Directory Browser. This eliminates the need to setup security for Directory Browser in RDS. To setup and run the Ericsson LDS service 1 After installing of the D.N.A. client and Directory Browser, run the NT/2000 Control Panel, and double click on Services. Select the "Ericsson LDS" service and change the Startup option to "Automatic". Start the Ericsson LDS service by clicking the "Start" button. 2 Run the NT/2000 Registry Editor (regedt32.exe) and modify the following registry value. HKEY_LOCAL_MACHINE\SOFTWARE\Ericsson\LocalDS\UseLDS and set this to 1. The Directory Browser uses this flag to connect to LDS rather than RDS that is running on the D.N.A. server.
3
Set the following registry value. HKEY_LOCAL_MACHINE\SOFTWARE\Ericsson\LocalDS\LDSServerName to the same PC computer name that LDS is running on.
4 5
Restart IIS and Directory Browser if they are already running in order to force the changes take into effect. If you are planning to use Directory Replications from other D.N.A. servers, run LDS Configuration Utility and add a number of Subscriptions and Publications so that the Directory Browser can conduct searches on remote D.N.A. servers.
95
Directory Browser Configuration

Telephony functions require you to logon, and the user logon ID and password are expected to be in the DNA directory. It is necessary that two fields of the directory be dedicated to storing the user credentials that Directory Browser checks before enabling Messages, Diversions, and dialing functions. To configure Directory Browser for dialing 1 It is recommended as a precaution that you backup the existing directory using the Backup command in Enterprise Manager. Right-click on the dirdb database, and select All Tasks Backup Database... from the popup menu. 2 Run Directory Configuration on the D.N.A. server machine. 3 Add a Person UDF field of type USER ID and name it. We suggest that you leave the Searchable check box unchecked to provide a little better security. 4 Add a Confidential UDF field of type USER PASSWORD, and then exit Directory Configuration. It is possible to add this as a simple Person UDF as well, but again, making it Confidential promotes a little better security. 5 Run Directory Manager and fill in the User ID and password fields you just added. Note Resist the temptation to use an SQL script to do the initial fill. Unless you have a very thorough knowledge of the DNA database schema, you could end up with IDs and passwords shared by several users. When one is later changed, they all could change! A suggested practice is to wait until a user specifically asks for access to Directory Browser before issuing a password. Then I send it via email with instructions to change it after the first successful logon. You can monitor logon requests via RDM running against RDS on the DNA server machine. (LDS passes logon requests to RDS for authentication). Here is a logon request message example. [99/11/08 09:40:59] I7336 - Message From Client 3256: PWD Logon Request; Server Name=ENS-EXPLOSION, Security Level=1, UserID=ebugsf Success is indicated with a message like this. [99/11/08 09:40:59] I7017 - Message To Client 3256: Message ID=127, Status=1 A failure is indicated by Status=2. The signaling is asynchronous, so if RDS is busy, the two messages can be separated by other messages. In fact, if RDS is busy, Directory Browser logons fail after a timeout.
Mobile Executive
The basic D.N.A. Server client must be installed before you can install Mobile Executive. This section explains installation requirements and procedures for Mobile Executive. Mobile Executive is installed on an Internet server. Even though the Internet server and the D.N.A. server can be on the same machines, we recommend they be on separate machines for better performance. In addition, Internet servers are periodically taken down for maintenance. Warning Mobile Executive will not function properly without a session state. The Session Timeout feature for your Mobile Executive web site must not be disabled.
96
Technical Guide

D.N.A. provides auto-run support for PCs that support this feature. When you insert the software installation CD into an auto-run compatible PC, the installation process is automatically started. The system will display an installation panel containing the following auto-run options. = = = = = = Install Application Suite Install PPM Lite Install Directory Browser Install Mobile Executive View Technical Guide Exit
Select Install Mobile Executive to install from the Auto-Run interface. Important If youre using a virus-protection utility, disable it before you run the D.N.A. Setup program. Also, close the control panel and any open Windows NT/2000 applications. To install Mobile Executive on a server PC 1 Insert the D.N.A. installation CD in the CD-ROM drive. -orIf youre installing from a network location, connect to it.
2 3 4 5 6
Find and open the DNA50_installation\MobileExecutive folder. Double-click setup.exe to start the installation. Proceed through the Welcome, Software License Agreement, and User Information dialogs. For New Virtual Directory, accept the mobileexec default for Name, or type another choice. Accept the default Destination Folder settings or browse to a new location of your choice. The installation program will copy files and complete the installation settings. When the installation completes, choose Yes, I want to restart my computer now. The system will shutdown, restart, and the installation will be complete.
Installation Options
The Mobile Executive installation provides Reinstall and Remove All options. Remove All can run from CD and Control Panel.
Option Reinstall Explanation Allows you to repeat the last installation to restore missing or corrupted files.
Remove All Deletes all installed Mobile Executive components. (You may also perform this task using Add/Remove Programs from the Windows NT/2000 Control Panel.)
97
Post Installation Setup

Windows NT 1 Select Programs Windows NT 4.0 Option Pack Microsoft Internet Information Server Internet Service Manger from the Start menu. 2 In the Tree pane, locate and click on the Internet Server name. 3 Click Default Web Site. 4 In the View pane, right-click mobileexec, and select Properties. 5 On the Virtual Directory tab (default), check Run in separate memory space (isolated process). 6 Click the HTTP Headers tab. 7 Click the File Types button. 8 In the File Types dialog box, click the New Types button. 9 In the File Type dialog box, enter .wml in the Associated Extension edit box and text/vnd.wap.wml in the Content Type (MIME) edit box. 10 Apply all the settings and close all the dialog boxes by clicking OK in each one.
11 If NTFS is used, make sure read and write permissions are given to \Inetpub\WWWRoot\MobileExec\bin\session.mdb (uncheck Read-only checkbox in properties).
Windows 2000 1 Select Programs AdministrativeTools Internet Service Manger from the Start menu. 2 In the Tree pane, locate and click on the Internet Server name. 3 Click Default Web Site. 4 In the View pane, right-click mobileexec, and select Properties. 5 On the Virtual Directory tab (default), select High (Isolated) from the Application Protection drop-down list. 6 Click the HTTP Headers tab. 7 Click the File Types button. 8 In the File Types dialog box, click the New Types button. 9 In the File Type dialog box, enter .wml in the Associated Extension edit box and text/vnd.wap.wml in the Content Type (MIME) edit box. 10 Apply all the settings and close all the dialog boxes by clicking OK in each one.
11 If NTFS is used, make sure read and write permissions are given to \Inetpub\WWWRoot\MobileExec\bin\session.mdb (uncheck Read-only checkbox in properties).
Outlook Integration
The D.N.A. Outlook Integration provides a bi-directional Integration between the Microsoft Office Outlook Calendar and D.N.A. Directory Calendar. This allows D.N.A. Directory Subscribers using Outlook's Calendar to synchronize the message diversion information with other D.N.A. applications through the D.N.A. Remote Data Server (RDS). Several pre-installation tasks must be completed before installing and running Outlook Integration. Usually these tasks are completed after D.N.A. server installation.
98
Technical Guide
2 3 4 5 6
Before Installation, Microsoft Outlook 98 or greater must be installed on the system. If Outlook is not installed, the installation process will report an error. Outlook Integration does not need the exchange server. Use the MD110 Support utility to synchronize Operator Message Diversion for All applications on the D.N.A. server. Use the RDS Configuration utility to set Default Diversion Duration and Default Diversion Stop Time for all Message Diversion Reason Codes on the D.N.A. server. Use the RDS Configuration utility to configure a GICI/CSTA Port. Use the Directory Configuration Utility to add a Person UDF of type Computer to the database. Use Directory Manager to add the Outlook computer name information to D.N.A. Directory.
Outlook Integration needs to be installed on both client and server machines. To install Outlook Integration Double-click on DNA_S\DMG\CALENDAR\setup.exe and follow the instructions in the Setup Wizard. To uninstall Outlook Integration 1 Open the Control Panel and double-click on Add/Remove Programs. 2 Remove D.N.A. Integration with Outlook.
User ID instead of Computer UDF

In the D.N.A. Server Registry, change the following registry key. HKEY_LOCAL_MACHINE\SOFTWARE\Ericsson\MRS\RemoteDS\Manager\UseUserIDForCalend arIntegration This value is set to 0 by default, which requires you to link a computer name (UDF type Computer) with a DMG subscriber. Setting this value to 1 changes Outlook Integration from using the PC name as the identity reference, to using the NT user's login name as the identity for Outlook calendar diversion settings. The advantage of using the NT user's login name allows you to use a Person UDF of type User ID instead of type Computer. This makes Outlook Integration more flexible and easier to manage. However, you cannot use User ID for Outlook Integration if you are using it for Directory Browser. After changing this registry key, stop and restart the Ericsson RDS service. It may take a few minutes for RDS to repopulate the local database. You can then use the Directory Configuration utility to add a UDF of type User ID, and then Directory Manager to add the Outlook user ID information to the D.N.A. Directory.
Troubleshooting
Outlook Integration would not start This problem is caused because Outlook was not installed on the system or there is no Outlook profile created in the logged on user's account. Make sure Outlook is installed and able to run under the logged on user's account.
99
Outlook Integration would not logon to the DNA Server This problem is caused when there is no subscriber entry found with the current computer name defined in the D.N.A. Directory. Make sure you added the computer name to the subscriber's entry in the D.N.A. Directory. Diversion information does not match between Outlook Integration and DNA This problem is caused when the current desktop extension does not match the primary extension of the D.N.A. subscriber entry that has the computer name (or user ID) defined for that subscriber. Make sure the subscriber entry in the D.N.A. directory has the correct primary extension with the correct computer name (or user ID). Trouble shooting with Remote Data Monitor Use the Remote Data Monitor to help determine if the correct messages are transferred between Outlook Integration and RDS. This utility reports Remote Data Service events and is started by double-clicking on DNA_S\SHARE\BIN\rdm.exe.
System Performance
Performance Enhancements
This section introduces steps you can take to improve D.N.A. performance, following system installation. Some of the improvements covered include: = Creating more available memory (RAM) = Improving OWS Supervisor performance = Improving RDS performance Note Not all of these performance remedies may apply to your situation. You must evaluate these options individually, with respect to your system requirements, system stability, and your own technical capabilities.
Memory
When Windows NT/2000 starts up, it loads several applications as part of the system. You can change the startup options for the applications that you don't use or need and free up additional memory and increase performance. Warning Make sure you know what each service does before changing it's startup setting. Many default NT/2000 services are essential to the operation of NT/2000 and without them your system will NOT function. Some of the following applications, however, may not be necessary for your particular system configuration:
100
Technical Guide
= = = = = = =
Alerter: requires the Messenger (thread in SERVICES.EXE 50K) ClipBook Server: shares Clipboard files (CLIPSRV.EXE 1280K) Messenger: sends and receives Win Pop-up messages and system alerts (thread in Services.exe 60K) Network DDE: Dynamic Data Exchange across the Network (NETDDE.EXE 96K) Network DDE DSDM: Dynamic Data Exchange across the Network (NDDEAGNT.EXE 1560K) Schedule: programs run at scheduled times in background (ATSVC.EXE 1348K) Spooler: handles printing from that computer (SPOOLSS.EXE up to 1280K)
To change the startup options 1 Open the Services control panel and select the Service you wish to change. 2 Stop the service. Once the service is stopped, select Startup. Some services will not stop if they are in use by the system. You can still change the startup option, but you will need to reboot for the change to take effect. 3 You can now change the service startup from Automatic to Manual or Disabled. Manual means the system can start the service when it is needed and Disabled means it will not be available at all.
Operator Workstation Supervisor

Use this information to improve the time required for the OWS Supervisor application on a D.N.A. client PC to connect with the OWS Supervisor server on a D.N.A. server PC. For more information, see http://www.microsoft.com/com/dcom.asp. In one documented case, connection time was reduced from about 15-20 seconds to 5-7 seconds. These changes apply only to the D.N.A. server PC. This change applies to the Windows NT/2000 Registry on the D.N.A. server PC. You must change the order that Microsoft's Distributed Component Object Model (DCOM) tries the installed network protocols. By default, TCP/IP is third. Performance is enhanced significantly when TCP/IP it is moved to the first position in the list. The protocol order is set by the registry value "DCOM Protocols" found under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc. The type is REG_MULTI_SZ. Confirm the following Default settings, then set the Registry according to the order of the Enhanced settings.
Default Enhanced
ncadg_ip_udp ncadg_ipx ncacn_ip_tcp ncacn_spx ncacn_nb_nb ncacn_nb_ipx
ncacn_ip_tcp ncadg_ip_udp ncadg_ipx ncacn_spx ncacn_nb_nb ncacn_nb_ipx
Restart the client PC the new settings to take effect.
101
RDS Performance
This section provides the following performance remedies and enhancements for the Remote Data Server (RDS). = = = = Enable/Disable Local Database Integrity Check Reduce I/O Completion Ports in Large Systems Enable/Disable Incremental LDB Updates from DMG Configure RDS to Use Fewer SQL Connections.
LDB Integrity Check Feature (RDS 2.x)

Warning This feature is intended for use during Field Trials only. There is a hidden feature in RDS to check the integrity of local databases. By default this feature is set to OFF, to activate this feature, set the following NT/2000 Registry key on the D.N.A. Server to 1. Stop and restart RDS to take into account the modified registry flag. HKEY_LOCAL_MACHINE SOFTWARE Ericsson RemoteDS Manager VerifyLDBIndexIntegrity <== set this to 0x1 After each change in Directory Manager, RDS will run an integrity check of the master local database files. If this check is successful, the changes will be synchronized to all client LDBs. This causes RDS to repopulate corrupted local databases whenever it detects DMG updates. This helps prevent corrupted server LDBs from being distributed to client PC's. Important The disadvantage of enabling this integrity check will be a performance degrade of the server.
Reduce I/O Completion Ports in Large Systems (RDS2.1)

Support I/O Completion Ports in RDS. This allows the D.N.A. administrator to select the option to run RDS to allocate one thread per connected client or to allocate an I/O Completion port per connected client. This option can be selected by toggling the following registry key: HKEY_LOCAL_MACHINE SOFTWARE Ericsson RemoteDS Manager UseMultiThreadedClientConnections UseMultiThreadedClientConnections The default setting for this flag is 1; i.e. use multi-threaded client connections. For installation sites with more than 50 D.N.A. client installations, it is recommended that this flag be set to 0; i.e. use I/O completion ports instead.
102
Technical Guide
For example, in a large system (more than 50 clients), RDS may run 410 threads at normal operation and 650 threads during peak times. With this change, RDS will run at 20 threads at normal operation and 260 threads during peak time. This should improve your server performance. Note If you choose to change this flag, you must stop and restart RDS to have the change take effect. System Requirements The minimum system requirements are: = REMOTEDS.EXE Version 2.1.004 = CONMGR.DLL Version 2.1.001 = SDS.EXE Version 2.1.001
Enable/Disable Incremental LDB Updates from DMG

By default this feature is enabled. Therefore, when DMG makes any updates, RDS broadcasts those updates to all clients; e.g. Operator Workstation. If this feature is disabled, RDS will not broadcast DMG updates until next scheduled LDB update. To configure the "Incremental Local Database Updates" flag, modify the following registry key: HKEY_LOCAL_MACHINE SOFTWARE Ericsson RemoteDS Manager EnableIncrementalLDBUpdates =0: No incremental updates are sent to LDBs. Also, when DMG moves a department, it will not start a repopulation of the related LDB tables. Only scheduled updates will repopulate the LDB with the latest changes. =1: This is the default setting. The LDBs are updated immediately after a DMG change to the SQL database. =2: This option enables incremental updates (this is small work for RDS), but with the condition to ignore any updates that force RDS to fully repopulate the LDB. Therefore, when DMG moves or changes the name of a department, RDS will not start the repopulation of related tables. This task is left to the scheduled nightly repopulation routine. The above settings only effect DMG changes. So if you select configure RDS for maintenance repopulation, it will execute based on the current EnableIncrementalLDBUpdates setting. If you choose to change this flag, you must stop and restart the RDS Service to have the changes take effect. This function is implemented in REMOTEDS.EXE 2.1.016 & REMOTEDS.EXE 3.0.008. Function =2 is implemented in REMOTEDS.EXE 2.1.021 & REMOTEDS.EXE 3.0.019.
103
Configure RDS to Use Fewer SQL Connections

System administrators can configure RDS to use fewer SQL connections by sharing the ODBC connections between threads. This feature is only recommended for small installations such as startup packages using a limited number of SQL connections (e.g., when using SQL Workstation 6.50 you have only 15 user connections). You may configure this option by modifying the following registry key: HKEY_LOCAL_MACHINE SOFTWARE Ericsson RemoteDS Manager ShareODBCConnection This flag is set to default to 0 (Disabled). To activate this option, set the flag to 1 (Enabled). If you choose to change this flag, you must stop and restart the RDS Service to have the changes take effect. This feature is implemented in REMOTEDS.EXE 3.0.009 and REMOTEDS.EXE 2.1.017
Installation Problems
Log Files
The D.N.A. installation program creates two logs that can be used to troubleshoot installation problems. The Detail log contains all operations performed during the installation process. The Summary log contains the final status (success or failure) for each installed component. These are ASCII text files that can be viewed with the Windows NT/2000 notepad.
Server Installation Logs

Located at: \dna_s\detail.log and \dna_s\summary.log
Client Installation Logs

Located at: \dna_c\detail.log and \dna_c\summary.log
Event Log Messages

The following table lists D.N.A. Server error messages and recommended remedies.
Application Ericsson ClockSync Error Message 1001 Could not load resource library: %1 Corrective Action Initialization error. Verify that the cloksync.lll is in the same directory as the service. %1 = file name Initialization error. Lack of system resources. Reduce the number of running applications and start the service again.
Ericsson ClockSync
1001 Could not duplicate thread handle.
104
Technical Guide
Ericsson ClockSync
1002 Could not create event handle.
Initialization error. Lack of system resources. Reduce the number of running applications and start the service again. Initialization error. Verify the permission level of the service. Restart the service. %1 = Registry key name.
Ericsson ClockSync
1003 Could not open registry key %1, using defaults.
Ericsson ClockSync
Initialization error. 1004 Client is enabled, but server machine name is invalid. Restart the service. Client disabled. 1005 Receive broadcasts is enabled, but server machine name is invalid. Receive disabled. 1006 Could not open process token, client disabled. Initialization error. Restart the service.
Ericsson ClockSync
Ericsson ClockSync
Initialization error. Lack of system resources. Reduce the number of running applications and start the service again.
Ericsson ClockSync
1007 Could not enable time set Initialization error. Lack of system resources. privilege for process, client Reduce the number of running disabled. applications and start the service again. 0 %1 unable to connect to database %2. Refer to database manual for detailed information of database error. Correct the problem per database manual and redo the installation. %1 = Application name. %2 = Database error message.
Ericsson Installation
0 %1 error inserting application Refer to database manual for detailed information of %2. database error. Correct the problem per database manual and redo the installation. %1 = Application name. %2 = Database error message. 0 %1 error inserting elements %2. Refer to database manual for detailed information of database error. Correct the bl d t b l 105
problem per database manual and redo the installation. %1 = Application name. %2 = Database error message. Ericsson Installation 0 %1 error inserting sites %2. Refer to database manual for detailed information of database error. Correct the problem per database manual and redo the installation. %1 = Application name. %2 = Database error message. Refer to database manual for detailed information of database error. Correct the problem per database manual and redo the installation. %1 = Application name. %2 = Database error message.
0 %1 number of licensed elements does not match element table.
1000 %1 number of elements in Refer to database manual for element table does not match detailed information of database error. Correct the site table. problem per database manual and redo the installation. %1 = Application name. %2 = Database error message. 1001 %1 error updating number Refer to database manual for detailed information of of element licenses %2. database error. Correct the problem per database manual and redo the installation. %1 = Application name. %2 = Database error message. 1002 %1 the element type was Refer to database manual for detailed information of not defined. database error. Correct the problem per database manual and redo the installation. %1 = Application name. %2 = Database error message. 1000 Could not load resource library. Initialization error. Verify that the lfs.lll is in the same directory as the service. Initialization error. Reduce the number of running applications and restart the i
Ericsson LFS
Ericsson LFS
1001 Failed to initialize application.
106
Technical Guide
service. Ericsson LFS 1002 Failed to duplicate thread Initialization error. handle. Reduce the number of running applications and restart the service. 1003 Failed to open named pipe acceptor. Initialization error. Reduce the number of running applications and restart the service. Initialization error. Reduce the number of running applications and restart the service. Initialization error. Reduce the number of running applications and restart the service. Initialization error. Reduce the number of running applications and restart the service.
Ericsson LFS
Ericsson LFS
1004 Failed to initialize database.
Ericsson LFS
1005 Failed to set low water mark.
Ericsson LFS
1006 Failed to set high water mark.
Ericsson LFS
1007 Failed to push module on Initialization error. Reduce the number of running Ustream. applications and restart the service. 1008 Failed to open reactor. Initialization error. Reduce the number of running applications and restart the service. Initialization error. Reduce the number of running applications and restart the service.
Ericsson LFS
Ericsson LFS
1009 Failed to set security attributes.
Ericsson LFS
1010 Failed to create message Initialization error. queue thread. Reduce the number of running applications and restart the service. 1200 Failed to retrieve security Initialization error. data server name from registry. Restart the service.
Ericsson LFS
107
Ericsson LFS
1201 Failed to initialize security Initialization error. Reduce the number of running data server client. applications and restart the service. 1200 Cannot retrieve the password format data from the local database. Notify the system administrator. Run-time error. Neither the primary nor the backup databases are available. Password cannot be changed with this condition. Contact your system administrator. Run-time error. Cannot retrieve data from the primary database. Password cannot be changed with this condition. Contact your system administrator.
Ericsson LFS
Ericsson LFS
1201 Cannot retrieve the password format data from the server database. Notify the system administrator.
Ericsson LFS
1202 Cannot retrieve the user Run-time error. data from the local database. Neither the primary nor the Notify the system administrator. backup databases are available. Password cannot be changed with this condition. Contact your system administrator. 1203 Cannot retrieve the user Run-time error. data from the server database. Cannot retrieve data from the Notify the system administrator. primary database. Password cannot be changed with this condition. Contact your system administrator. Run-time error. 1204 Cannot save the new password. The server database Cannot store data to the primary database. Password is unavailable. cannot be changed with this condition. Contact your system administrator. 1205 Cannot save the new Run-time error. password. Unable to connect to Cannot store data to the primary database, due to the security data server. communication problems with the security data server. Password cannot be changed with this condition. Contact your system administrator. 1206 Cannot retrieve the user Run-time error.
Ericsson LFS
Ericsson LFS
Ericsson LFS
Ericsson LFS
108
Technical Guide
data from the server database. Verify that the application is installed. Reinstall the The application may not be application, if needed. installed. Notify the system administrator. Ericsson LFS 1207 Cannot retrieve the user data from the local database. The application may not be installed. Notify the system administrator. 1500 Failed to close message queue normally. 1700 Out of memory. Run-time error. Verify that the application is installed. Reinstall the application, if needed.
Ericsson LFS
Shutdown error. Notify the system administrator. Initialization error. Reduce the number of running applications and restart the service. Initialization error. Verify that the sds.lll is in the same directory as the service. Initialization error. Reduce the number of running applications and restart the service.
Ericsson LFS
Ericsson SDS
1000 Could not load resource library.
Ericsson SDS
1001 Failed to initialize application.
Ericsson SDS
1002 Failed to duplicate thread Initialization error. Reduce the number of running handle. applications and restart the service. 1003 Failed to open named pipe acceptor. Initialization error. Reduce the number of running applications and restart the service. Initialization error. Reduce the number of running applications and restart the service. Initialization error. Reduce the number of running applications and restart the service. Initialization error. Reduce the number of running applications and restart the
Ericsson SDS
Ericsson SDS
1004 Failed to initialize database.
Ericsson SDS
1005 Failed to set low water mark.
Ericsson SDS
1006 Failed to set high water mark.
109
service. Ericsson SDS 1007 Failed to push module on Initialization error. Ustream. Reduce the number of running applications and restart the service. 1008 Failed to open reactor. Initialization error. Reduce the number of running applications and restart the service. Initialization error. Reduce the number of running applications and restart the service.
Ericsson SDS
Ericsson SDS
1009 Failed to set security attributes.
Ericsson SDS
1010 Failed to create message Initialization error. Reduce the number of running queue thread. applications and restart the service. 1200 Database server error: %1. Initialization error. Refer to the database manual for information on database error. Correct the problem per database manual and try again. %1 = Database error message Run-time error. Check whether database server is running and restart, if necessary. %1 = Database error message
Ericsson SDS
Ericsson SDS
1201 Failed to connect to database server. Retrying in %1 seconds.
Ericsson SDS
1202 Failed to create database Run-time error. Reduce the number of running server connection thread. applications and restart the service. 1203 Failed reading the Run-time error. database source from the Check the content of the registry. Application type = %1. registry setting with RDS configuration. Check the access permission to the registry entries with the Registry Editor. %1 = Application type 1500 Failed to close message queue normally. Shutdown error. Notify the system administrator.
Ericsson SDS
Ericsson SDS
110
Technical Guide
Ericsson SDS
1700 Out of memory.
General error. Reduce the number of running applications and restart the service. Refer to database manual for detailed information of database error. %1 = Database error message. Refer to database manual for detailed information of database error. %1 = Database error message. Refer to database manual for detailed information of database error. %1 = Database error message. Refer to database manual for detailed information of database error. Correct the problem per database manual and try again. %1 = Database error message. Refer to database manual for detailed information of database error. Correct the problem per database manual and try again. %1 = Database error message. Refer to database manual for detailed information of database error. Correct the problem per database manual and try again. %1 = Database error message. Refer to database manual for detailed information of database error. Correct the problem per database manual and try again. %1 = Database error message. Refer to database manual for detailed information of d t b C t th 111
Ericsson UserConfig
1000 Cannot connect to database server %1.
Ericsson UserConfig
1001 Cannot open user table %1.
Ericsson UserConfig
1002 Cannot update the user %1.
Ericsson UserConfig
1003 Cannot delete the user %1.
Ericsson UserConfig
1004 Cannot reset the users password %1.
Ericsson UserConfig
1005 Cannot access the privilege/authority codes %1.
Ericsson UserConfig
1006 Cannot update the password properties %1.
Ericsson UserConfig
1007 Cannot load the application table %1.
database error. Correct the problem per database manual and try again. %1 = Database error message. Ericsson UserConfig 1008 Cannot load the site table Refer to database manual for detailed information of %1. database error. Correct the problem per database manual and try again. %1 = Database error message.
D.N.A. Server
Facilities and Services
The D.N.A. Server is the security and support platform for the Dynamic Network Administration (D.N.A.) applications. The D.N.A. Server provides the structural platform for flexible integration of D.N.A. applications. Major components include the Open Database Connectivity (ODBC) module, the Remote Data Server (RDS), the common SQL database, security administration, license management facilities, and a set of comprehensive application support utilities. The D.N.A. Server is a collection of secured facilities and services that provide support and software security for D.N.A. applications. Primary D.N.A. Server facilities and services include: Security Data Server - The Security Data Server (SDS) provides high-level security in the form of licensing enforcement. SDS references encrypted licensing data to enforce authorized license limits. SDS also accesses data based on Logging Facilities Server requests. Remote Data Server - Remote Data Server (RDS) is a D.N.A. service module that maintains continuous network database synchronization between MD110 PBX nodes, the D.N.A. SQL server, and all D.N.A. local databases. Logging Facilities Server - When a you attempt to log-on to a D.N.A. application, the Logging Facilities Server (LFS) performs user authentication. LFS attempts to connect to SDS for on-demand access to D.N.A. SQL server security data. If the attempt fails, LFS connects to a local version of the database allowing essential security operations to proceed. When you attempt to access a remote data server (a server on a different network), LFS attempts to validate your access authorization at the remote server. Time System Interface - D.N.A. Time System Interface (TSI) is an optional D.N.A. service module that connects to an external time monitoring system. TSI allows diversions to be entered in the time monitoring system, transferred to the D.N.A. Directory Manager application, and registered in the D.N.A. Directory database. As well, Message Waiting (MWT) indications can be sent from D.N.A. to the time monitoring system. These support resources are maintained and operated by network administrative and technical specialists. The following diagram illustrates the interaction between these D.N.A. client and server support resources.
112
Technical Guide
Administrative Tools
Administrative tools installed with the D.N.A. Server platform and with individual applications support various system configuration operations. The D.N.A. installation process automatically installs these tools. The following table explains how these utilities are used.
Tool RDS Configuration How It Is Used Installed On Server Allows you to configure the Remote Data Server for D.N.A. database and application support roles, including network database synchronization between MD110 PBX nodes, the D.N.A. SQL Server, and D.N.A. Local Databases (LDBs). Provides controls for assigning Server and managing user descriptions and corresponding application access privileges. Server Use the D.N.A. Time System Server Configuration Utility to set up and maintain communications and translation settings for Diversion and Message Waiting features. Server Use this D.N.A. Server administrative tool to build and maintain a list of database servers accessible on the network. The Serial Communications S Utilit ll t Server and Client
User Configuration
TSS Configuration
D.N.A. Server Configuration
SCS Configuration
113
Server Utility allows you to manage direct, Telnet, SCS, and third party serial communications port settings. License Viewer MD110 Support Allows you to display D.N.A. site license information. Server
Server and Client The MD110 Support Utility allows you to perform initial MD110 node configuration and data extraction for the D.N.A. OWS, EMG, PMG, and NPM applications. Enables you to set up Operator Server Workstation subscriber directory assistance structures that best meet the needs of organizations they support. The LDAP Configuration Utility Server enables you to configure the Lightweight Directory Access Protocol (LDAP) Server from anywhere on the network. It also allows you to add more LDAP directories to be used for searching people over the Internet/intranet from the Operator Workstation application. Allows you to setup other local Server and Client database servers from one that is already configured. Use the D.N.A. Name Identity Server Conversion Utility translate subscriber directory information into MML command files for D.N.A. telephone name display. Server Gives D.N.A. system administrators the ability to assign operators access to various departments within the organization. Determines what department data a given operator can access. Enables you to assign easily recognizable names to incoming trunks for efficient operator identification and routing. Use the D.N.A. Voice System Voice System Interface Configuration Utility to set up Server
Directory Configuration
LDAP Configuration
LDS Configuration
Name Identity Conversion
Operator Configuration
Trunk Manager
VSI Configuration
Server
114
Technical Guide
and maintain Diversion and Message Waiting communications settings between external Voice Systems and the D.N.A. Voice System Interface (VSI). License Administrator Provides controls for application licenses and corresponding network resource licenses. Server
Directory Import
Server and Client For initial population of OWS directory assistance database. Runs on D.N.A. server and selected D.N.A. client workstations. Use the Export Utility to create Server and Client .dat text files of Dynamic Network Administration subscriber directory databases. The .dat files can then be imported into another D.N.A. installation with the Directory Import utility.
Directory Export
Changing Users, Servers, and Passwords

As with D.N.A. applications, most D.N.A. Server utilities are protected by access security controls. Access facilities allow you to change logged users, change D.N.A. servers, and change your personal password. To Change Logged Users 1 Select Change Current User on the Application menu. 2 When the User Log On dialog box appears, type the new User Name and Password into the corresponding edit boxes. As you type the password, a string of asterisk characters (********) appears in the Password edit box, one asterisk for each character you type. Both the User Name and Password fields are case-sensitive, and you are allowed only a limited number of attempts. 3 Select a local or remote server from the DNA Server drop-down list. The initial security authorization check and all subsequent validation actions are directed toward the server you select. 4 Click the OK button. If the user name and password are valid, the new user will be logged on to the application with the access authorizations permitted in their user profile. If the logon attempt fails, the Logging Facilities Server (LFS) restores the original user as the currently logged on user.
115
To Change Logged D.N.A. Servers 1 Select Change Current User on the Application menu. 2 When the User Log On dialog box appears, type the new User Name and Password into the corresponding edit boxes. As you type the password, a string of asterisk characters (********) appears in the Password edit box, one asterisk for each character you type. Both the User Name and Password fields are case-sensitive, and you are allowed only a limited number of attempts. 3 Select a new local or remote server from the DNA Server drop-down list. 4 Click the OK button. If the user name and password are valid, user authentication and all subsequent actions will be directed to the new server. To Change Your Password Your password is your personalized access code that, along with your User Name, D.N.A. uses for verifying your access authorization. Changing your password from time to time is a recommended security precaution that helps prevent unauthorized access.
1
Select Change Password... on the Application menu. The Change Password dialog box is displayed. A user password can be up to 20 characters in length, and is case-sensitive. The Password Format box explains minimum character requirements for defining passwords. Field
Total Length: Alphabetic: Numeric:
Explanation
Minimum number of characters required for a valid password. From the Total Length, the minimum number of alphabetic characters required. From the Total Length, the minimum number of numeric characters required.
Non-alphanumeric: From the Total Length, the minimum number of non-alphabetic characters required. Example of non-alphanumeric characters are: -,&*# etc. 2 3 4 5
Enter your existing password into the Old Password edit box. Enter your new password into the New Password edit box. Again, enter your new password into the Confirm New Password field. Check your entries and click the Save button.
Registry
Registry Settings
The Windows NT/2000 Registry is a database repository for information about a computers configuration. It is organized in a hierarchical structure of sub-trees and their keys, hives, and value entries. This section explains registry settings that correspond to D.N.A. component properties not found in the GUI. Operator Workstation Registry Settings Setting up Subscriptions and Publications in RDS and/or LDS controls the D.N.A. directory servers accessed by Operator Workstation. Use the RDS Replication tab in RDS Configuration on your D.N.A. server.
116
Technical Guide
Server Identification
Use the D.N.A. Server Configuration Utility to build and maintain a list of available database servers. Ericsson's Dynamic Network Architecture relies on uniquely identified servers for centralized database and application support services. D.N.A. applications and utilities accessing network servers through security services require user logon and server selection. The Server Configuration Utility allows you to specify names and other attributes for the servers appearing in the User Logon D.N.A. Servers selection list.
Maintenance
SQL Database
This section explains SQL database upsizing and maintenance procedures. Database Upsizing You can re-size D.N.A. database components to accommodate changes in the network. Use the Resize Database option.
1 2 3
Re-run the D.N.A. installation and choose the Resize Database button on the Ericsson Setup dialog box. Choose or enter new space requirements in the Nodes and Extensions for Database, Upsizing Extension Per Node, and Upsizing Performance manager Node Setup dialogs. Respond to the remaining prompts and instructions from the installation wizard.
Tasks You must schedule or perform maintenance tasks such as backing up databases and dumping transaction logs in support of SQL Server database operations. Refer to your SQL server documentation for information on managing these maintenance tasks. Transaction Log Important Do not confuse the SQL transaction log with the D.N.A. Transaction Log. These resources serve two unrelated purposes. Expired message diversions are kept as reference information until being deleted daily. MD110 Message Waiting indications are updated daily. Use the SCHEDULE1 on the RDS Schedules tab to schedule daily database clean up for message diversion and message waiting. RDS performs this maintenance routine CheckDB once per day. The CleanDB Routine To maintain efficient D.N.A. operation, run CleanDB. CleanDB is an RDS function that deletes unused User-defined Fields (UDFs) and keywords. This routine is performed on a nightly basis. You may reschedule CleanDB from the RDS Schedules tab. If you choose to do so, it is recommended that you schedule this task to be run at least once per day.
117
Logging Facilities Server

When you attempt to log-on to a D.N.A. application, the Logging Facilities Server (LFS) performs user authentication. LFS attempts to connect to SDS for on-demand access to D.N.A. SQL server security data. If the attempt fails, LFS connects to a local version of the database allowing essential security operations to proceed. When you attempt to access a remote data server (a server on a different network), LFS attempts to validate your access authorization at the remote server. Ovwin.log File This file records all failed API calls. Check here to see if there is anything relevant to the problem you are investigating.
Short Message Service

The Short Message Service (SMS) provides the capability to transfer short messages, up to 160 characters, between Short Message Terminals and DECT Mobile Stations via a Short Message Service Center (SMSC). SMSC is connected to the MD110 via the NIU board. The procedure to initiate an SMS involves three steps: = A generic extension is initiated with the license parameter set to SMS. = The SMS server number is initiated using CXSYI with the SMSN parameter set to the generic extension initiated in previous step. = Connection between the SMS server and the NIU I/O device is established using MSCOI command. Extension Manager supports initiation, change, and removal of SMS. An SMS message will continually attempt to send the message to the phone until it is received.
Limitations
You can only send SMS messages from Operator Workstation. Sending an SMS message to more than 1 handset at a time or from one handset to another are not supported. You cannot have the D.N.A. SMS server and another SMS server connected to the MD110 at the same time. This is a MD110 limitation.
Local Database Compression

The Local Databases used by Operator Workstation can be compressed. If you have WAN links, we recommend you enable this feature. To enable this feature, you have to set the following registry key. This default setting for this flag is 0 (Disabled). Set it to 1 to enable it. HKEY_LOCAL_MACHINE\SOFTWARE\Ericsson\RemoteDS\Manager\EnableFilexfr Compression The compression is done just before the Local Database (LDB) files are sent over the network. They are then uncompressed by Operator Workstation right after they are retrieved from the network. Thus, the files can be accessed by Operator Workstation uncompressed.
118
Technical Guide
The machines at both ends must have D.N.A. installed. The supporting components are in the client files in DNA_C\SHARE\BIN. Both machines must have the registry value set to 1. You can see when compression is active by watching the file transfers in Remote Data Manager.
Maintenance
Archival Backup
PDM creates one archive file for each MD110 node that is written to the Dna_s\Siten\Pmg\Archive directory on the server PC (where n is the node number). Automatic or manual data extraction that exceeds the disk space configured for the primary D.N.A. server traffic measurement database causes the overflow to be extracted to archival flat files. For example, if D.N.A. traffic measurement disk space has been allocated for 3 months of data and you attempt to manually extract 6 months of data, the first 3 month's data will be placed in three separate monthly files, and the most recent 3 month's data are stored in the primary database. Important It is imperative that there be a minimum of 4 MB of disk space free for each node on the server disk where the Dna_s directory resides. To maintain available disk space, the archival files in the Archive subdirectory for each node should be periodically backed up to auxiliary storage and deleted from the server disk drive.
119
The archival files are used when setting up the auxiliary database, and all required files must be in the appropriate directory in order for it to be set up correctly. Therefore, when setting up the auxiliary database, you should restore any required files that were backed up and deleted from disk.
Temporary Workspace
PDM uses local drives for temporary files to store data during data extraction and to display MD110 system information. There must be at least 2 MB of free space free on the disk drive where the D.N.A. directory is installed. Be sure to maintain this minimum of 2 MB of free space on the disk drive where the D.N.A. directory is installed.
Automatic Extraction
Automatic data extraction refers to Performance Data Manager's downloading, translating, and transferring traffic measurement data to the D.N.A. database server on a daily basis. PDM performs this task once each morning between 00:30 (or 30 minutes after midnight) and 06:00, based on a 24-hour time scale. The 00:30 time is the default setting and can be changed in the PDM application. The polling period for database extraction extends to six hours from the configured start time. Note PDM makes three extraction attempts for each measurement site.
Performance Data Manager Operations

Since there may not be a corresponding PDM release for each MD110 release, PDM defaults to the latest available PDM releases after receiving the MD110 identity. For example, if the customer site is running BC10.1, PDM may treat it as if the site is running BC10.0 if the latest PDM release supports BC10.0. A one-time notification per login is issued in the audit trail when such discrepancies are detected.
Two Ways To Start The Extraction Process

There are two ways to have data extraction process started automatically at a pre-defined time. = Leave PDM running on PC. The data extraction process will start automatically at the pre-defined time. = Schedule PDM via the Remote Data Server scheduler to start as a batch job. It must be scheduled prior to the pre-defined data extraction time. The data extraction process will then start automatically when the scheduled time arrives. PDM scheduling can be set during the installation procedure. This option is supported only on the D.N.A. Server.
120
Technical Guide
The Data Extraction Command

PDM extracts traffic measurement data from the HDU by issuing the MD110 FIFCP command consisting of the following syntax: FIFCP:PATH=/SYSN/USR1/ACS/TM/Dnyddd, FORMAT=HEX; Where: PATH specifies the directory where traffic measurement data files reside. The path name must be as specified and must not be altered. FORMAT specifies the traffic measurement file format, which is always hexadecimal. The file name is encrypted in the form Dnyddd where: n = the sequence of dumped files, valued 0, 1, 2 or 3. A maximum of 4 dumped files are allowed per day, e.g. the first dump of the day has n = 0. Although the traffic measurement data is being collected by MD110 software in 15 minute intervals, dumping only occurs when the temporary buffer in MD110 software is full or at the end of the day. After the midnight dump occurs, the temporary buffer is erased to pre-pare for traffic measurement data collection of the new day. y = the last unit digit of the year. For example, 4 for 1994 or 2004. ddd = the day of the year. The day of the year, for example 031 is Jan 31, 032 is Feb 1, 033 is Feb 2, and so on...
Clock Synchronization
The MD110 midnight dump occurs at 11 minutes after midnight. The midnight dump signifies that dumping of the day's traffic measurement data to the HDU has been completed. The Data Manager extraction process is scheduled to perform automatically at 00:30 (or 30 minutes after midnight). These time-related events require that the MD110 and PC clock to be synchronized with one another.
Extraction Process
The data extraction process includes Performance Data Manager converting collected traffic measurement data from hexadecimal to decimal format and store the results in the D.N.A. database. PDM is able to perform the extraction process for both local and remote D.N.A. database servers. The First Extraction after PMG Installation The first automatic data extraction after the initial installation of Performance Manager attempts to retrieve existing data from the HDU for the currently active MD110 measurements, store them in the D.N.A. database. The first extraction process, therefore, may require more time to execute. This functionality also further enhances the Presentation Manager utility by immediately allowing you to view your collected traffic measurement data in Microsoft Excel 97 or Excel 2000 instead of having to wait for the data to be collected. Data Collected Prior to PMG Installation If PC-traffic measurement was used to collect traffic measurement data prior to Performance Manager installation, it is possible that the traffic measurement data collected on the HDU is incomplete. This is caused by the PC-traffic measurement commands TRPEI and TRPEE, which allow PC-traffic
121
measurement to retrieve traffic measurement data from a temporary buffer, transfer it to the PC-traffic measurement collection PC, then erase the buffer data before writing to the HDU. Issuing MML Commands We recommend against issuing MML commands such as TRREP or FIFCP during your scheduled data extraction interval. These commands access the HDU traffic measurement data and may otherwise interfere with the data extraction process.
Skip Nodes For Polling

All nodes on the server will be polled by default. However, polling selected nodes can also be setup through registry settings. To setup nodes to skip when polling 1 Create a key with DNA Server machine name under HKEY_LOCAL_MACHINE/SOFTWARE/ Ericsson/PMG/ Example: HKEY_LOCAL_MACHINE/ SOFTWARE/Ericsson/PMG/DNA_SERVER1
2
Add a string SkipSites with the nodes you want to skip separated by commas (",") under the key created in Step 1 and end with a comma (","). Example: If there are five nodes and only node 2 and 4 should be polled, set the to: 1,3,5, (make sure you end with a comma ",") registry string
Extend Polling Time

The PDM data polling routine will poll data for six hours starting from the BatchTime setting. You can setup a registry string to extend the polling time. The polling time should be set between six to twelve hours. If no setting is present, or the setting is less than 6, polling time defaults to six hours. If setting is greater than 12, it will be treated as 12 hour polling time. The registry is \HK_LM\Software\Ericsson\PMG\BatchLength.
Presentation Manager
Following are important operation and maintenance considerations for Performance Presentation Manager.
Operational Requirements
PPM, like Microsoft Excel 97 or Excel 2000, requires an installed printer driver to function when connected to a printer.
Traffic Measurement Reports

Although all traffic measurement data is stored in the SQL database, only objects related to Operators, Trunk Routes, Voice Extensions, PCM lines, PBX Hunt Groups, Cordless Extension Common Fixed Part (BC10), Cordless Extension Traffic and Mobility Function (BC11) and IP Network Interface (BC11) are available in pre-defined reports. As a functional subset of PPM, PPM Lite only provides reports on objects related to Operators, Trunk Routes, and PBX Hunt Groups.
122
Technical Guide
Preserving Edited Reports

All traffic measurement reports generated from the Query Measurements panel are write-protected. You must save edited traffic measurement report worksheets under different filenames to preserve their contents and to distinguish them from the original files.
Database Utility
The purpose of the DNA database utility (DBCP.EXE ) is to backup/restore DNA application related databases to/from a files running on Microsoft SQL Server 7.0 and MSDE. The backup feature provided by SQL Server 7.0 sometimes may corrupt ogins/users/ownership of databases. Therefore, DBCP is preferred as a more secure backup/restore method. Besides, this is the only way to backup databases if MSDE is used.
Options
The Following command line options are available when you execute this console application. -B Backup database from SQL server to file -D DNA application (All, MRS, DMG, EMG, NPM, or PMG) -F Display full path where data file is residing -O Change database ownership to D.N.A. default account -P User account password, defaults to (blank) -R Restore database from file to SQL server -U User account name for accessing SQL server (defaults to sa) ? Help and usage information The following table shows what is backed up or restored with the D option.
DNA Application All MRS DMG EMG NPM PMG Backed Up/Restored All installed DNA databases Dnadfdb emgdb security db_xaction Dirdb SiteX Npmdb Pmglocks auxXpmg siteXpmg
All will be used, if -D is omitted Note X indicates the site number.
Capacity and Limitations

This backup/restore utility cannot be undone while the operation is in progress. It can only be executed on the same machine where Microsoft SQL server or MSDE is installed. During the restore process, the target database should not be accessed or connected by other processes or applications.
123
Troubleshooting
Technical Support
The Troubleshooting book contains information needed to resolve most problems that can occur with the D.N.A. applications. However, there may occur situations in which you are unable to resolve problems using troubleshooting information. For additional technical assistance, contact your Ericsson representative.
Before Contacting Technical Support

In order to help restore your productivity as rapidly as possible, Ericsson engineers will need the following information.
Versions for: Windows NT/2000 + Service Pack Level SQL Server + Service Pack Level D.N.A. + Service Pack Status TAU or CT Adapter Revision Level
Local Area Network: Type of LAN and LAN configuration System size: Number of: OWS clients DMG clients Names in subscriber database Version of "fixed" .exe files (To view, use the Windows NT/2000 Explorer to select and rightclick the .exe file, select Properties from the pop-up menu, click the Version tab. BC software release CNI version Any special OWS patches System size (i.e., nodes, extensions, etc.) A detailed description of the problem. And although it is not necessary, it will be helpful if you can try to guess the source of the problem and then try to provide Ericsson engineers with detailed information relating to that part of your system.
If Hotfixes loaded:
MD110 setup:
Include:
Reporting Your Problem

To assist our support staff, please obtain the following information before contacting technical support. You should include as much information as is available on system specifications, applications, and the problem itself.
124
Technical Guide
Problem Description
State each problem description clearly and include any available details relating to the problem, including: = = = = Time-of-day problem occurred Operations in progress when the problem occurred Applications and/or databases involved General type of failure (i.e., transitory, repeatable/non-repeatable, application halt, system halt, etc.)
MD110
Version ________________ No. of Nodes ____________ IPU Revision _____________ ICU Revision _____________
Operating System Information (mark all that apply)

Windows NT/2000 Workstation___ Windows NT/2000 Server________ Version_________________ Language________________
Configuration
Workgroup______________ Stand Alone_____________ FAT ___________________ Domain _________________ File System______________ NTFS___________________
Network Protocol (mark all that apply)

NetBUEI________________ TCP/IP__________________ IPX/SPX________________ Other ___________________ None __________________ Software ________________
PC
Manufacturer ____________ CPU __________________ Memory (RAM) __________ Model __________________ Clock Speed _____________ Hard Disk _______________
125
D.N.A. Applications
Report each application that was running when the problem occurred. Include the version/release level and which national language the application supports. Application
Directory Manager (DMG) Extension Manager (EMG) Numbering Plan Manager (NPM) ________________________ Operator Workstation (OWS) Performance Data Manager (PDM) ________________________ Performance Presentation Manager ________________________ Other ________________________ ________________________ ________________________ ________________________ ________________________ ________________________
Version/Release Level
________________________
Language Supported
________________________ ________________________ ________________________ ________________________
Event Viewer
D.N.A. applications utilize the event logging facility to record error messages returned from the SQL server. If you encounter database operation difficulties, you can use the Windows NT/2000 Event Viewer to display information for events related to the problem and assist in problem isolation. Event Viewer displays system events registered by Windows NT/2000 and application events recorded by the various applications. Event Viewer can also display events for other PCs on the same network. Refer to the Windows NT/2000 System Guide for information about using Event Viewer.
Error Messages
Event ID Error messages 1. CPBXLINK: InputHandler() cannot get timer capabilities. CPBXLINK: Unable to contact the telephone. Unable to open registry key. Corrective Action Fix PC hardware.
2.
Check phone, connection cable, and proper ELU initiation Check and correct registry and user permissions. Check all TAU connecting cables and cycle power on the TAU 2520. This message ONLY appears when Operator Workstation is explicitly configured to use TAU 2520 with ELU5.` Check all TAU connections and COM port assignments.
4.
5.
No response from PBX port.
6.
Unable to detect a terminal adapter on the PBX port.
126
Technical Guide
7.
The terminal adapter reports no PBX connection. The terminal adapter reports no phone connection. CPBXLINK: SendSignal(%1!s!) failed. GetLastError returned %2!s!.
Check connection to the PBX jack on the TAU. Check connection to PHONE jack of the TAU. Restart Operator Workstation. This usually appears if the program is aborted unexpectedly. If the returned value is 234, there is a registry value of type REG_SZ longer than 80 characters. Shorten that value. Fix COM port configuration or hardware problem. Fix COM port assignment problem. This can also occur if Operator Workstation is configured to use a non-existing port. Reinstall Windows NT/2000. If error recurs, contact system administrator.
8.
10.
Error reading registry value. RegEnumValue() returned %1!s!.
14.
SetCommState() Failed. GetLastError returned "%1!s!". CreateFile(%1!s!) failed. GetLastError returned "%2!s!".
15.
16.
CreateThread() for CCommLink::InputHandler failed. GetLastError return "%2!s!". No response from the Operator Workstation keyboard port. Failed to connect to directory server.
18.
Check Operator Workstation keyboard connection and COM port assignment. Verify that both the SQL server and D.N.A. Server are installed and running on the server PC. Verify that both the SQL server and D.N.A. Server are installed and running on the server PC.
19.
20.
Failed to open directory database.
21.
Failed to retrieve subscriber user-defined Correct database setup using the Directory Configuration utility. fields. ODBC Error: SQLState: "%1!s!", ODBCError: "%2!s!", NativeError: "%3!s!". ODBC Information: SQLState: "%1!s!", ODBCInfo: "%2!s!",NativeInfo: "%3!s!" Check SQL and ODBC driver using SQL utilities.
22.
23.
None (information message)
24.
Warning physical memory is running low. Either increase memory or close (exit) non-essential programs. 127
25.
Warning Virtual memory is running low.
Increase the paging file size via the Windows NT/2000 Control Panel. Select System and virtual memory. Replace the telephone.
26.
Equipment status signal reports telephone is faulty. Warning Signal Buffer has exceeded 90%
27.
Signals from the PBX and/or the phone are not being processed fast enough. This is usually due to some other process consuming most of the available CPU time. Use the Task Manager to determine which process is at fault and end it.
28.
Re-install the D.N.A. Server client Warning Operator Workstation will not try to connect to Database. ODBC driver software. is not installed in registry. Error Signal Buffer Overflow Count Signals from the PBX and/or phone have been lost. This is an increase of the severity of the problem indicated by event 27. Take the same corrective action.
29.
30.
Error Signal Buffer Overflow Loop Count The signal buffer pointer has advanced beyond its upper boundary. It is unlikely that this would occur in the absence of more serious operating system problems. Department diversion database connection disconnected. There is a problem with one or more services on the server or the client, or a network problem. Try to stop and restart the Ericsson LFS service on the local machine. Verify that RDS and SDS on the server are running. Verify that the server is reachable over the network. This event is obsolete and not used in D.N.A. 4.0. Same as event 31. If these two events (31 and 33) occur independently, there may be an installation related problem. None. This is an information message. The absence of this message indicates a service or network problem similar to events 31 and 33. This event is obsolete and not used in DNA 40
31.
32.
External search database connection disconnected. Message and Diversion database connection disconnected.
33.
34.
Department diversion database connection complete.
35.
External search database connection l t
128
Technical Guide
complete. 36. Message and Diversion database connection complete.
D.N.A. 4.0. None. This is an information message. The absence of this message indicates a service or network problem similar to events 31 and 33.
Error Messages for SNMP Agent GetAppSuiteRegInstalled: RegOpenKeyEx failed: 0xnnn Make sure that the registry key HKLM\SOFTWARE\Ericsson\DMI\AppSuite actually exists and that system account has permission to read it. Make a note of the error code "0xnnn". GetAppSuiteRegInstalled: RegQueryValueEx failed: 0xnnn Make sure that the registry key HKLM\SOFTWARE\Ericsson\DMI\AppSuite\InstalledAppSuiteComponents actually exists and that system account has permission to read it. Make a note of the error code "0xnnn". GetAppSuiteRegState: RegOpenKeyEx failed: 0xnnn Make sure that the registry key HKLM\SOFTWARE\Ericsson\DMI\AppSuite actually exists and that system account has permission to read it. Make a note of the error code "0xnnn". GetAppSuiteRegState: RegQueryValueEx failed: name 0xnnn Make sure that the registry key HKLM\SOFTWARE\Ericsson\DMI\AppSuite\"name" actually exists and that system account has permission to read it. Make a note of the name and error code "0xnnn". SetAppSuiteRegInstalled: RegCreateKeyEx failed: 0xnnn Make sure that the system account has permission to create and/or write registry key HKLM\SOFTWARE\Ericsson\DMI\AppSuite. Make a note of the error code "0xnnn". SetAppSuiteRegInstalled: RegSetValueEx failed: 0xnnn Make sure that the system account has permission to create and/or write registry key HKLM\SOFTWARE\Ericsson\DMI\AppSuite\InstalledAppSuiteComponents. Make a note of the error code "0xnnn". SetAppSuiteRegState: RegCreateKeyEx failed: 0xnnn Make sure that the system account has permission to create and/or write registry key HKLM\SOFTWARE\Ericsson\DMI\AppSuite. Make a note of the error code "0xnnn". SetAppSuiteRegState: RegSetValueEx failed: name 0xnnn Make sure that the system account has permission to create and/or write to registry keys under HKLM\SOFTWARE\Ericsson\DMI\AppSuite\"name". Make a note of the name and error code "0xnnn". AddAppX: GetAppSuiteRegInstalled failed Make sure that the registry key HKLM\SOFTWARE\Ericsson\DMI\AppSuite\ actually exists and that system account has permission to read it. AddAppX: SetAppSuiteRegInstalled failed Make sure that the system account has permission to create and/or write registry key HKLM\SOFTWARE\Ericsson\DMI\AppSuite\InstalledAppSuiteComponents.
129
AddAppX: SetAppSuiteRegState failed Make sure that the system account has permission to create and/or write to registry keys under HKLM\SOFTWARE\Ericsson\DMI\AppSuite. RemoveApp: GetAppSuiteRegInstalled failed Make sure that the registry key HKLM\SOFTWARE\Ericsson\DMI\AppSuite\ actually exists and that system account has permission to read it. RemoveApp: SetAppSuiteRegInstalled failed Make sure that the system account has permission to create and/or write registry key HKLM\SOFTWARE\Ericsson\DMI\AppSuite\InstalledAppSuiteComponents. Init: AddApp failed: 0xnnn Make sure that the system account has permission to create and/or write registry key HKLM\SOFTWARE\Ericsson\DMI\AppSuite\InstalledAppSuiteComponents. Make a note of the application id "0xnnn". SetAppState: Can't find app: 0xnnn The function SetAppState was called with an invalid application id. Make a note of the application id "0xnnn". SetAppState: SetAppSuiteRegState failed Make sure that the system account has permission to create and/or write to registry keys under HKLM\SOFTWARE\Ericsson\DMI\AppSuite. SetModified: Can't find id: 0xnnn The function SetModified was called with an invalid application ID. Make a note of the application id "0xnnn". CheckPID: SetAppSuiteRegState failed Make sure that the system account has permission to create and/or write to registry keys under HKLM\SOFTWARE\Ericsson\DMI\AppSuite. GetApps: Map is empty A list of known applications has been requested and the list was empty. This might or might not be an error. GetEventType: Can't find id: 0xnnn The function GetEventType was called with an invalid application ID. Make a note of the application id "0xnnn". GetEventSeverity: Can't find id: 0xnnn The function GetEventSeverity was called with an invalid application ID. Make a note of the application id "0xnnn". GetAppStart: Can't find id: 0xnnn The function GetAppStart was called with an invalid application ID. Make a note of the application id "0xnnn".
130
Technical Guide
GetAppSuiteServerName: RegOpenKeyEx failed: 0xnnn Make sure that the registry key HKLM\SOFTWARE\Ericsson\MRS\CurrentVersion\ actually exists and that system account has permission to read it. GetAppSuiteServerName: RegQueryValueEx failed: 0xnnn Make sure that the registry key HKLM\SOFTWARE\Ericsson\MRS\CurrentVersion\ServerName actually exists and that system account has permission to read it. GetAppSuiteServerID: RegOpenKeyEx failed: 0xnnn Make sure that the registry key HKLM\SOFTWARE\Ericsson\MRS\CurrentVersion\ actually exists and that system account has permission to read it. GetAppSuiteServerID: RegQueryValueEx failed: 0xnnn Make sure that the registry key HKLM\SOFTWARE\Ericsson\MRS\CurrentVersion\ServerID actually exists and that system account has permission to read it. GetAppVer: Can't find id: 0xnnn The function GetAppVer was called with an invalid application ID. Make a note of the application id "0xnnn". GetAppState: Can't find id: 0xnnn The function GetAppState was called with an invalid application ID. Make a note of the application id "0xnnn".
Directory Manager
The following table lists error messages displayed by the Directory Manager application that may indicate a setup problem.
Error Message An error occurred while closing the database. Corrective Action Verify that there is a connection to RDS (Remote Data Server) and the SQL server, and verify that RDS and the SQL server are responding to data retrieval and update requests. Verify that the D.N.A. Server utilities are running and that Remote Data Server is set up correctly. Verify that there is a connection to RDS (Remote Data Server) and the SQL server, and verify that RDS and the SQL server are responding to data retrieval and update requests. Verify that there is a connection to RDS (Remote Data Server) and the SQL server, and verify that RDS and the SQL server are responding to data retrieval and update requests. Verify that there is a connection to RDS (Remote
Cannot get user ID for transaction register entry. Could not add a new department to the database.
Could not add extension.
Could not add the external directory
131
entry.
Data Server) and the SQL server, and verify that RDS and the SQL server are responding to data retrieval and update requests. Verify that there is a connection to RDS (Remote Data Server) and the SQL server, and verify that RDS and the SQL server are responding to data retrieval and update requests. Verify that there is a connection to RDS (Remote Data Server) and the SQL server, and verify that RDS and the SQL server are responding to data retrieval and update requests. Verify that there is a connection to RDS (Remote Data Server) and the SQL server, and verify that RDS and the SQL server are responding to data retrieval and update requests. Verify that there is a connection to RDS (Remote Data Server) and the SQL server, and verify that RDS and the SQL server are responding to data retrieval and update requests. Verify that there is a connection to RDS (Remote Data Server) and the SQL server, and verify that RDS and the SQL server are responding to data retrieval and update requests. A record in the delete_id table is locked.
Could not connect to the Extension Manager database.
Could not connect to the transaction database.
Could not delete subscriber.
Could not delete the department.
Could not delete the external directory entry.
Could not get a valid record ID from IDMSC. Could not retrieve authorization code from the logging services.
Verify that the Management Repository Server utilities are running and that Remote Data Server is set up correctly. Verify that the Management Repository Server utilities are running and that Remote Data Server is set up correctly. Verify that there is a connection to RDS (Remote Data Server) and the SQL server, and verify that RDS and the SQL server are responding to data retrieval and update requests.
Could not retrieve database source information from the logging services.
Could not update extension data.
Could not update external directory data. Verify that there is a connection to RDS (Remote Data Server) and the SQL server, and verify that RDS and the SQL server are responding to data retrieval and update requests.
132
Technical Guide
Could not update subscriber.
Verify that there is a connection to RDS (Remote Data Server) and the SQL server, and verify that RDS and the SQL server are responding to data retrieval and update requests. Verify that there is a connection to RDS (Remote Data Server) and the SQL server, and verify that RDS and the SQL server are responding to data retrieval and update requests. Verify that there is a connection to RDS (Remote Data Server) and the SQL server, and verify that RDS and the SQL server are responding to data retrieval and update requests. Verify that there is a connection to RDS (Remote Data Server) and the SQL server, and verify that RDS and the SQL server are responding to data retrieval and update requests. A record in the delete_id table is locked. Verify that there is a connection to RDS (Remote Data Server) and the SQL server, and verify that RDS and the SQL server are responding to data retrieval and update requests.
Data for the selected department could not be retrieved.
Data for the selected external directory entry could not be retrieved.
Data for the selected subscriber could not be retrieved.
See your Database Administrator. The department could not be updated.
Extension Manager
Error Message Cannot access database at this time. Synchronization is currently running. (Message Box) Possible Cause Another user is using Extension Manager or MD Support to access the database, or database remained locked when MD Support application terminated abnormally. Corrective Action Use Access Control option on Application menu to display information about user accessing database. If the other user is still accessing the database, try to access the database again later. If it is suspected that the other user is not still accessing the database, the record in the database which is blocking access to other users can be deleted manually. Cannot connect to database server. (Message Box) Cannot get database server information. (Message Box) Cannot open database. Network is down. Restart the network.
Data source points to the wrong Setup the data source. PC. Restart the server database.
133
(Message Box) Cannot connect to MD110.
Server database is down.
Restart the server database.
Telephone number to access Verify that MD110 telephone MD110 unavailable or incorrect. number is correct and available. Make sure there is a port available. Verify there is a functioning cable connection between the Telnet server and the MD110 IPU port(s).
Cannot connect from the Telnet All Telnet ports are occupied. server to the serial port. No connection from the Telnet server to the MD110 IPU port.
Cannot connect to the Serial Communication Service. Cannot connect to the Telnet server.
Connection attempt has failed. Verify the SCS is running. Make sure the access agent is Access agent is not running. running. Incorrect Telnet server address, User ID, or password. Verify that the Telnet server logon information is entered correctly. Restart the network.Restart the database server. Close the other application using the communication device or wait until the communication device is available. Specify a valid communication device.
Cannot get Telnet address from Network or SQL server is not the database. (Message Box) running. Cannot open communication device. Communication device is being used by another application. Selected communication device does not exist.
Cannot retrieve MD110 error messages from database. (Message Box)
Server database is down. Required entry in EMGDB database MDERR table does not exist. Logon to MD110 not completed due to problem with connection to the MD110 or the MD110 itself.
Restart the server database. Reinstall the EMGDB database.
Cannot synchronize with MD110.
Verify that the connection to the MD110 is good and verify that the MD110 is operating properly.
Communication line blocked. Communication line failure. Communication line not available. Connection to this site is not allowed. Please synchronize this site before reconnecting. Data source retrieved from Logging service for node database is undefined. Data source retrieved from Logging service for transaction database is undefined. (Message Box)
Problem with connection to the Verify that the connection to the MD110 or the MD110 itself. MD110 is good and verify that the MD110 is operating properly. Extension Manager MD database table is empty. Run MD support utility to synchronize MD data.
Data source set up incorrectly. Setup the data source.
134
Technical Guide
Error communicating with the Remote Database Server. Error disconnecting from the Telnet server. Error initializing the modem. Error resetting the modem.
Network is down or the RDS is Restart the network and verify down. RDS is running.
Problem with connection to modem/TAU or modem/TAU itself. Network is not operating properly. Remote Data Server is not running.
Verify that the connection to the modem/TAU is good and verify that the modem/TAU is operating properly. Restart the network. Run RDS.
Error loading the template file from the server. Make sure the Remote Data Server is running. Also make sure that the Registry contains the correct path to the D.N.A. directory structure.
Contact technical support. Incorrect entry in registry for path in server for template files.
Failed to connect to transaction Network is down. Restart the network. database. (Message Box) Data source set up incorrectly. Setup the data source. Incorrect communication settings. Communication parameters for Set up the communication the communication device are parameters to match the communication device. not set up correctly.
Invalid authorization to Telnet Access Agent. Invalid client path. Please check with your system administrator. Invalid path to the log files. Contact technical support. Directory set for TargetDirectoryClient in registry does not exist. Extension Manager log subdirectory for the specific site does not exist. Create emg\log sub-directory under the site directory.
Invalid path to the online help parameter description.
Online help sub-directory does Create emg\help sub-directory. not exist. Create the site sub-directory.
Invalid site path. Please contact Site sub-directory under client your system administrator. path does not exist. Logon rejected.
Restart the MD110 as Logon attempt rejected by MD110 after three unsuccessful described in the MD110 attempts. Operation and Maintenance manuals. Time limit for MD110 feedback Increase time limit. too short. Problem with connection to the Verify that the connection to the MD110 or the MD110 itself. MD110 is good and verify that the MD110 is operating properly.
No character received from MD110 within time limitation.
No dial tone received from the communication device. No free MML session is available.
Problem with TAU/modem. All Telnet ports are occupied.
Restart/reset the TAU/modem. Verify that there is a port available.
135
No password assigned.
No password assigned for user Request that system ID. administrator add Extension Manager access password to the user ID. Logon to MD110 not completed due to problem with connection to the MD110 or the MD110 itself. Incorrect MD110 password entered. Verify that the connection to the MD110 is good and verify that the MD110 is operating properly. Enter correct password, or use MD Support application to assign a new password. Verify that the device is available. Resend command. Try to connect again. If the attempt fails, try again after intervals of several minutes. Request that system administrator add Extension Manager access privilege to the user ID.
No prompt received from MD110.
Password unknown.
SCS device is not available. Serial line not available. The dialup number is busy.
The SCS device is occupied. Command to MD110 temporarily blocked. The destination directory number is unavailable due to current activity. User ID not authorized for Extension Manager.
The logged in user is not allowed to run Extension Manager.
You are attempting to process Disconnect the current site and The site for the current transaction is different from the a transaction for a different site reconnect to the site required for the transaction. than the site currently selected site. connected. Unable to get the site for the current transaction. Extension number is not a member of any known number series currently in the database. Network is down. Site security information does not exist in logging local database. Logging facility service is down. Unable to retrieve the TargetDirectoryClient value from the Registry. Please contact your Administrator. Unable to retrieve transaction data source from Logging service. TargetDirectoryClient entry for Ericsson does not exist in registry. RDS not running. Contact technical support. Run MD support and resynchronize Directory Information and "Number Series". Restart the network. Run RDS on the server. Run logging facility service on the client.
Unable to retrieve site security information from logging service.
Run RDS on the server.
Logging facility service is down. Run logging facility service on the client. Data mismatch between RDS Restart logging facility service and logging facility service. on the client.
Unknown communication error. The system does not recognize Contact Ericsson Technical a communications failure. Support.
136
Technical Guide
Operator Workstation
This table lists problems that may occur during Operator Workstation operation. It provides an explanation of the probable causes and recommended remedies.
Problem Cannot deliver (send) e-mail messages to D.N.A. subscribers from Operator Workstation. Possible Cause OWS may not have successfully attached to a MAPI session. Corrective Action Use the Windows NT/2000 Performance Monitor to check the exchng32.exe and mapisp32.exe processes. See Troubleshooting in E-mail Integration for OWS. Check D.N.A. Server installation and restart Operator Workstation after correcting database configuration. Perform the suggested corrective action and restart Operator Workstation. If the problem recurs, verify the RS232C connection between the TAU and the PC by using a breakout box, and verify the line by initiating the line as a digital station and verify that the D3 works on that line. IRQ conflict or I/O address problem. Multiple ports or devices assigned the same IRQ (interrupt request), or address settings improperly configured. Use the winmsd.exe utility in the system32 directory for Windows NT/2000 to view IRQ and address settings. Reassign IRQs and/or address settings to resolve conflicts. Verify the RS-232C connection between the TAU and the PC by using a break-out box, and verify the line by initiating the line as a digital station and verify that the D3 works on that line. Check the class of service and call origin group for this operator interface in the MD110.
Error dialog box displayed when starting Operator Workstation.
Database settings configured incorrectly. PBX interface problem.
Operator Workstation starts, but cannot get any on/off duty indications.
Line initiation or cabling problem.
Operator Workstation starts and you can go on duty but cannot make or answer calls.
Setup problem.
Performance Data Manager

Use the following table to investigate problems identified in PDM error messages.
Error Message Cannot connect to MD110. Possible Cause Corrective Action Telephone number to access Verify that MD110 telephone MD110 il bl i t b i t d 137
MD110 unavailable or incorrect. number is correct and available. Cannot open communication device. Communication device is being Close the other application using the communication used by another application. device or wait until the communication device is Selected communication device available. does not exist. Specify a valid communication device. Logon to MD110 not completed due to problem with connection to the MD110 or the MD110 itself. Verify that the connection to the MD110 is good and verify that the MD110 is operating properly.
Cannot synchronize with MD110.
Communication line blocked. Communication line failure.
Problem with connection to the Verify that the connection to the MD110 or the MD110 itself. MD110 is good and verify that the MD110 is operating properly. MD110 file system problem. Contact MD service personnel. Consider skipping data for that day (unrecoverable error).
Data format error. Possibly caused by MD110 file system error. Data format error. Possibly caused by noise. Data sequence error during data transfer. Database operation failed or there was an error connecting to database server.
Noise in the communication line Retry the operation at a later between the PC and MD110. time.
No SQL server connection available.
SQL server is down or network Verify that at least two connection is down. connections are available. Data source is not set up correctly. Verify that SQL server is up and network connection is OK. Verify that the data source is set up properly. Error initializing the modem, or Problem with connection to an error resetting the modem. modem/TAU or modem/TAU itself. Failed to allocate memory. Not enough system memory. Verify that the connection to the modem/TAU is good and verify that the modem/TAU is operating properly. Close unnecessary applications and restart PDM.
Check event log for more specific error messages provided by the SQL server. Restart PDM.
Failed to create temporary file. No disk space available on the Delete unneeded files from the Failed to write to temporary file. local drive. local drive to make space available. Failed to get data associated with PMG from the logging server. Incorrect communication settings. 138 Network is down, or RDS is not Restart the network, and run running. RDS on the server. Communication parameters for Set up the communication the communication device are parameters to match the
Technical Guide
settings. No character received from MD110 within time limitation.
not set up correctly.
communication device.
Time limit for MD110 feedback Increase time limit. Maximum is 300 seconds (5 minutes). Time too short. limit should be increased to reflect the size of the PABX switch (the larger the switch, Problem with connection to the the longer the time limit). MD110 or the MD110 itself. Verify that the connection to the MD110 is good and verify that the MD110 is operating properly. Logon to MD110 not completed due to problem with connection to the MD110 or the MD110 itself. Command to MD110 temporarily blocked. Verify that the connection to the MD110 is good and verify that the MD110 is operating properly. Resend command.
No prompt received from MD110.
Serial line not available.
Unable to connect to database No SQL server connection available. server. Unable to establish connection to database server.
Check event log for more specific error messages provided by the SQL server, restart PDM, and verify that at least two connections are SQL server is down or network available. connection is down. Verify that SQL server is up Data source is not set up and network connection is OK. correctly. Verify that the data source is User for database is not set up set up properly. correctly. Not enough space for the auxiliary database. Verify that the user ID and password for database is set up correctly. Reinstall the database for PDM. Increase the size for the auxiliary database. You may want to back up the databases and restore them after reinstallation.
Unable to lock database. Database is used exclusively by other process.
Database has been locked by PDM running on another PC.
Retry the operation at a later time.
Performance Presentation Manager

There are two troubleshooting tables and a description of the ppm.ini file to help you identify and resolve problems for Performance Presentation Manager. The first troubleshooting table describes troubleshooting for general problems, and the second tables describes troubleshooting for specific messages displayed by PPM.
139
Essential Requirements
PPM, like Microsoft Excel 97 or Excel 2000, requires an installed printer driver to function when connected to a printer.
Report Limitations
Although all traffic measurement data collected on the hard drive is stored in the SQL database, only objects related to Operators, Trunk Routes, Voice Extensions, PCM lines, PBX Hunt Groups, and Cordless Extension Common Fixed Part are available in pre-defined traffic measurement reports for PPM. Because PPM Lite is only a subset of PPM, only objects related to operators, Trunk Routes, and PBX Hunt Groups are available to PPM Lite. All traffic measurement reports generated from the Query Measurements panel are write-protected. You must save edited report worksheets under new filenames to preserve their contents and to distinguish them from the original files.
General PPM Problems

Use the following table to analyze Performance Presentation Manager problems.
Problem Auto-formatted charts do not print properly. Possible Cause Corrective Action
Incorrect print driver selected or Use the Printers option for the print driver not set up properly. Windows NT/2000 Control Panel to select a different printer or modify the printer setup. Set up ODBC again. Make sure that all databases set up by PDM and the different site databases grant the proper access to PPM. Exit and restart PPM to reestablish the connection. Use PPM Switch Sites option to select the correct site and database (primary or auxiliary).
Cannot access SQL database. ODBC data source not set up properly. PPM does not have access rights to one or more databases. Server goes down and the connection is damaged. Incorrect site database.
PPM Error Messages
140
Technical Guide
Mobile Executive
The following table contains recovery information for phone error codes.
Symptoms Failed to load Mobile Executive URL Error on Phone WAP ERR-500 Internal server error Possible Cause Make sure the MobileDNAObject.dll has been registered and assigned the correct permission (read + execute). Make sure the session.mdb has the correct permission (read + write), and the Mobile Executive logged on user's phone number is assigned in the DMG database. Make sure SQL server and RDS are running. Make sure SQL server is running Make sure EMG is not running in the foreground on the same machine where Mobile Executive is installed, the MD connection is OK, and the SYSTEM user has been added in DNA User Configuration with EMG privileges. Make sure RDS is running and LDB files exist in \DNA_C or DNA_S\DDB\DATA.
Failed to Logon
WAP ERR-500 Internal server error
Failed to Logon Failed to access Personal Number Failed to update the Personal Number
WAP ERR-408 Server timeout WAP ERR-408 Server timeout Error code: xxxx Failed to activate profile!
Search results always empty
Application Data
Report Generation
Although D.N.A. applications can be used to display and report a wide variety of information, you may want to extract data directly from the application databases and use other applications to manipulate the data or generate reports. To Generate Reports Using Access 1 Click the Attach Table tool on the Access toolbar to attach the SQL Database. 2 After selecting SQL Database, Access prompts you for a data source. Select the data source pointing to the SQL server with MD110 data. 3 Login to the SQL server by entering thirdpty as the user ID and password. Click on the Options buttons to select a database. 4 Select a table from the list and attach all tables that you want to use for your reports. 5 Click on the Query tab, and then on the New button to define a New Query. In order to correctly set the table relations, you should refer to the technical documentation for the specific D.N.A. application.
141
After setting the table relationships, run the query and check the results to see if the data is coming back correctly. Click on the ! tool on the toolbar to run the query. 7 Once you are satisfied with your query, click on the Report tab and then click on the New button. Access prompts you with the Database dialog box. Select the query that you defined in the previous steps, and then click on the Report Wizard button. 8 The report wizard guides you through the steps of defining a report. 9 Select the fields and the sort order that you want to include in your report, and define the report style and page orientation. 10 The Report Wizard asks you for a report title. After you have entered the title of the report, you can choose to run the report or go to report design view to further customize the report layout.
Directory Manager Database Organization

The following table lists the directory database tables used by D.N.A. applications and utilities.
Table Name subscriber Field Name recID middle_name absent first_name honorary last_name options primary_extension primary_nodeID record_type sort_priority Field Type Max Characters 30 30 30 30 30 Description record ID middle name subscriber alert first name honorary last name ext. number node ID print priority dept record ID picture file name alternative spelling alternative spelling alternative spelling alternative spelling int varchar bit varchar varchar varchar int varchar int tinyint tinyint int main_department_recI varchar varchar D varchar picture_resid varchar middle_name_alt1 varchar middle_name_alt2 middle_name_alt3 middle_name_alt4 first_name_alt1 first_name_alt2 first_name_alt3 first_name_alt4 last_name_alt1 last_name_alt2 last_name_alt3 last_name_alt4 udf1_recID udf2_recID udf3_recID udf4_recID udf5_recID udf6_recID udf7_recID udf8_recID udf9_recID udf10_recID varchar varchar varchar varchar varchar varchar varchar varchar int int int int int int int int int int
30 30 30 30 30
subscriber
30 30 30 30 30 30 30 30
alternative spelling alternative spelling alternative spelling alternative spelling alternative spelling alternative spelling alternative spelling alternative spelling UDF record ID UDF record ID UDF record ID UDF record ID UDF record ID UDF record ID UDF record ID UDF record ID UDF record ID UDF record ID
142
Technical Guide
udf11_recID udf12_recID udf13_recID udf14_recID udf15_recID udf16_recID udf17_recID udf18_recID udf19_recID udf20_recID subscriber udf1_field udf2_field udf3_field udf4_field udf5_field udf6_field udf7_field udf8_field udf9_field udf10_field udf11_field udf12_field udf13_field udf14_field udf15_field udf16_field udf17_field udf18_field udf19_field udf20_field recID name dept_type_recID parent_recID child_recID sibling_recID udf1_recID udf2_recID udf3_recID udf4_recID sort_priority recID nodeID directory_number options primary_user_recID nodeID sitename nodename remote_nodeID remote_server options
int int int int int int int int int int varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar int varchar int int int int int int int int int int int varchar int int int varchar varchar int varchar int 50 50 30 160 160 160 160 160 160 160 160 160 160 160 160 160 160 160 160 160 160 160 160 60
UDF record ID UDF record ID UDF record ID UDF record ID UDF record ID UDF record ID UDF record ID UDF record ID UDF record ID UDF record ID Personal UDF value
department
dept. record ID dept. name parent record ID child record ID sibling record ID UDF record ID UDF record ID UDF record ID UDF record ID sort priority ext. record ID node ID directory number user record ID node ID site name node name remote node ID remote server
extension
site
143
numser
recID nodeID start_extension end_extension type options recID value recID department_recID address listed_number name udf1_recID udf2_recID udf3_recID udf4_recID udf5_recID udf6_recID recID SQL_type field_name field_type field_resid label_name record_type options table_name display_sequence UDF_number max_data_length
int int varchar varchar int int int varchar int int varchar varchar varchar int int int int int int int tinyint varchar tinyint varchar varchar tinyint int varchar int int int int varchar int int int int int int int int int int varchar varchar int int varchar
30 30
record ID node ID start extension end extension
keyword external_directory
45
record ID text value record ID dept. record ID address phone number name UDF record ID UDF record ID UDF record ID UDF record ID UDF record ID UDF record ID record ID
160 30 50
field_ definition
30 30 30
field name field type label display
20 display sequence
personal UDF max length 45 record ID text value
char_fields
recID value def_char_recID share_count department_recID subscriber_recID extension_recID subscriber_recID keyword_recID subscriber_recID recID nodeID trunkID trunk_name options groupID name
sub_dept sub_ext sub_key trunks
dept. record ID sub. record ID ext. record ID sub. record ID keyword record ID sub. record ID record ID node ID trunk number trunk name display global group ID global name
20 30 30 30
global_name
144
Technical Guide
access_codes
recID nodeID exchangeID access_code nodeID_connection remote_server table_name recID recid terminal recID country_code area_code prefix suffix options numser_recID schema_ver_no created_date released_date database_server
int int varchar varchar int varchar varchar int int varchar int varchar varchar varchar varchar int int
20 20 30 20
Table "access codes" for multiple tenants
deleted_id dept_recid_tmp
deleted table record ID temporary department record ID table extension dialing information
16
dial_extension_info
10 10 10 10
dirdb_info
varchar datetime datetime varchar varchar database_server_ver_n varchar odbc_ver_no recID start_time end_time duration reason_code reason_text cancel_text counter options status is_diverted_recID diversion_type dept_diversion_recID link_diversion_recID owner_appID repeat_type repeat_every repeat_type_day_0 repeat_type_day_1 repeat_type_day_2 repeat_type_day_3 repeat_end_time oper_div_recID it datetime datetime int int varchar varchar int int tinyint int int int int int int int int int int datetime int varchar
30
30 30 30
Directory database version and release information
diversion
Message diversion
160 80
145
operatorID 60 divr nodeID pbx_reason_code dna_reason_code pbx_description dna_description tdn duration reference method options priority message recID msg_text cancel_text phone status when_received oper_msg_recID received_recID options operatorID recID userID external_extension sub_extension sub_recID status options name table_name reserved_flag portID ts_reason_code reason_code diversion_flag tdn ts_reason_text portID ts_msg_byte msg_byte portID start_card_no end_card_no diversion_flag recID received_recID msgID card_no tID int int int varchar varchar varchar int varchar varchar int int int varchar varchar varchar tinyint datatime int int int varchar int varchar varchar varchar int int int varchar varchar int int varchar varchar varchar varchar varchar int varchar varchar int varchar varchar varchar int int varchar varchar i t 160 80 30 Message Waiting (incl. E-mail) indication Message Diversion Reason Table (Synchronized from extension database by RDS)
10 30 1 40 30
60 20 30 30 OWS Outbound Dialer dynamic log
outbound_dialer
60 20 reserved table record ID time system translation codes
reserved_id_table ts_trans_codes
4 1 1 1 80 1 1 20 20 1
ts_msg_convert
time system message conversion time system card number range
ts_card_no_range
ts_message
time system message waiting 10 20
146
Technical Guide
portID user_search_access recID userID department_recID portID start_mail_box_no end_mail_box_no diversion_flag recID received_recID msgID mail_box_no portID portID reason_code reason_text sub_activation_expiration subscriber_recID activation_time expiration_time options description
int int varchar int int varchar varchar varchar int int int varchar int int varchar varchar int datetime datetime int varchar 80 description of activation 1 80 subscriber to be activated time to activate time to expire 20 logged-in user search access voice system mailbox number range
vs_mail_box_no_range
20 20 1
vs_message
voice system message waiting 20 voice system reason codes
vs_reason_codes
vs_diversion
rec_ID is_diverted_recID divID mail_box_no portID
int int int varchar int 20
voice system diversion
Extension Manager Database Organization

Table Name accnt Field Name accountcode description acdpam acdnum acdval acdmisopt acdsup acgrp extno groupno traffic limno Field Type varchar varchar smallint smallint smallint varchar varchar smallint smallint 5 5 null null null null Max Characters 15 60 null Default
147
queuelen service selcat qindchannel cust name1 name2 info pres sat aveconvtime bkgroupno acmem groupno extno clericaltime qpriority qpritype adn extno catno traffic service calldivcat routingcat transcat addcat callalt cust name1 name2 info pres datype ancdgrp ancd lim serv sel traf
varchar varchar varchar varchar smallint varchar varchar varchar varchar smallint smallint varchar varchar varchar smallint smallint smallint varchar smallint varchar varchar varchar varchar varchar varchar varchar smallint varchar varchar varchar smallint smallint varchar smallint smallint smallint smallint
11 10 5 3
null null null null
20 20 20 2
null null null null null null
5 5 5
null
null null null 5 null 8 8 9 6 1 11 1 null null null null null null null null 20 20 20 2 null null null null null 5 null null null null
148
Technical Guide
cust sat maxtim name1 name2 pres status ancdmbr ancd sat node distno string startTraf status anndesc annnum annname apppam pamnum pamval authcode authcodeno calllogcode comcat checkcode dir cust csp auxana extno prianano auxananext cat traffic service calldivcat routingcat addcat icat transcat cust
smallint smallint varchar varchar varchar smallint varchar varchar varchar smallint varchar varchar smallint varchar smallint varchar smallint int varchar varchar smallint smallint varchar smallint smallint varchar varchar varchar smallint varchar varchar varchar varchar varchar varchar varchar smallint 8 9 9 6 9 4 1 5 5 5 5 7 6 60 64 10 20 64 5 5 4 20 20
null null null null null
null
null null
null null null null null null null null null null null
149
name1 name2 info pres bcrelease bpos callbyname bc id dir name1 name2 type aux cbgrp groupno traffic service queuelen cust name1 name2 info pres channel icuind node cho status chgrp comabb groupno comabbno transno class cust comabbdesc comabbno description cust comabbinfo comabbno status comdiv comdivno divtype cust
varchar varchar varchar varchar int char varchar varchar varchar smallint varchar varchar smallint smallint smallint smallint varchar varchar varchar varchar smallint smallint smallint varchar varchar varchar varchar varchar smallint varchar varchar smallint varchar smallint varchar int smallint
20 20 20 2
null null null null
9 20 20 20
null
10 5
null
null null null null 20 20 20 2 null null null null
null null 64 5 5 26 4 null null null null 5 60 null null 5 null
10
null null null
150
Technical Guide
compg
pageno searchcode speechsrcarea pagecat
varchar varchar int varchar varchar smallint int varchar varchar varchar varchar varchar varchar varchar smallint varchar varchar varchar int smallint tinyint varchar varchar varchar smallint varchar varchar varchar varchar varchar varchar varchar varchar smallint varchar varchar int
5 5 null null 3 5 null
compgm
pageno psano
comsrvprf
cspno traf serv cdiv roc npres desc
10 12 8 6 3 60 5
cordless
extno access authkey ipei authpar
8 13 48
corg
operator_id corg_id primary_f
cpagrp
cpgrpno cpagrpno
5 5 5 null 11 5 5 5 3 3 14 11 null null 14 14 null null null null
cpgrp
groupno limno
csta cstagrp
equ cstano odnno adnno odnkey adnkey
cstaiodev
iodevice equ devtype
cstalgrp
linkgroupid iodevice
custinfo
custno
151
custname custmusic custno parkedann queuedann dat extno tau datcat traffic service termcat transcat routingcat devtype modgrp addcat datapool dpnum dpgrp dptype dayn route type extno trunk dcat catno traffic service termcat transcat routingcat descp deftfunc insttype keyno ktype kvalue dgrp groupno traffic service modemgrpno
varchar smallint smallint smallint varchar smallint smallint varchar varchar varchar varchar varchar varchar varchar varchar varchar smallint smallint smallint smallint varchar varchar smallint varchar varchar varchar varchar varchar varchar int varchar varchar varchar varchar smallint smallint varchar
30
null null null null
8 2 10 14 2 10 5 6 5
null null null null null null null null
null null 5 6 null null
8 2 10 14 2 30
null null null null null null null
3 3 5 5 null null 2 null null
152
Technical Guide
disturbinfo dgrpstatus groupno used dirpg pageno searchcode speechsrcarea pagecat dirpgm pageno psano dnisnums dnisnum used dnisused dnisnum servgrp servtype name1 name2 info pres emdev emdevname emdevnum dmdevnum devname equloc equpos location extdesc extno description extinfo extno type status extpg pageno searchcode speechsrcarea pagecat extpgm pageno psano gdgrp generic groupno extno csp
varchar varchar smallint varchar varchar int varchar varchar smallint varchar smallint varchar varchar smallint varchar varchar varchar varchar smallint smallint varchar varchar varchar varchar varchar varchar smallint smallint varchar varchar int varchar varchar smallint varchar varchar int
4 5
null
null 5 5 null null 3 5 null
5 null 5 5 null 20 20 20 2 null null null null
60 11 60 5 255 5
null
null
null
null null 5 5 null null 3 5 null
5 5
153
cust lim type name1 name2 info pres grprva grpno welno queno reqrueno cidreqno ewta hgrp groupno traffic queuelen limno trunkcat service selcat cust name1 name2 info pres histtaskinfo taskid batchid procid procinfo status resultdesc hot hotfrom hotto hltype icuequ icuind equ idiv idivfrom
smallint int int varchar varchar varchar varchar varchar smallint smallint smallint smallint smallint varchar smallint smallint smallint smallint varchar varchar smallint varchar varchar varchar varchar int int int varchar smallint varchar varchar varchar smallint smallint varchar varchar 11 5 255 5 26 2 2048 20 20 20 2 9 3 5 20 20 20 2 5
null null
null null null null
null null null null null null null null null null null
null null
null null
null
154
Technical Guide
idivto indabb extno indabbno type transno ipext extno password isdn dir cat traf serv cdiv roc adc acctyp cust name1 name2 info pres da ivmbox vsdno extno vcat pergr lang lvmsys vsdno equpos sideno lang idx name lim marker id taskid batchid procid primkey1 primkey2
varchar varchar int smallint varchar varchar varchar varchar smallint varchar varchar varchar varchar varchar smallint smallint varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar smallint varchar smallint int int int varchar varchar
10 5
null
null 26 5 30 5 null 8 8 9 6 8 null null null null null null null 20 20 20 2 5 5 5 2 2 2 5 11 2 5 16 null null null null null null null null null null null null
32 32
null null
155
viewname marked mdmgrp mdn id odnno mdnno keyno callalt memgrp grpno grpmem type initorder mns odnno mnsno dig msgint extno term typeintserpos odn extno catno traffic service calldivcat routingcat transcat addcat callalt insttype cust name1 name2 info pres datype lang odnadn adnno odnno keyno
int smallint smallint varchar varchar varchar varchar varchar varchar smallint int varchar varchar varchar varchar varchar smallint varchar smallint varchar varchar varchar varchar varchar varchar varchar varchar smallint varchar varchar varchar varchar smallint smallint varchar varchar varchar 5 5 3 null null 20 20 20 2 9 8 9 6 1 11 1 3 5 null null null null null null null null null null null null null null null null 5 5 20 5 5 null null null null 5 5 3 1 5 5 null
156
Technical Guide
odnfunc
extno keyno ktype value dig
varchar varchar varchar varchar varchar varchar varchar varchar int char varchar varchar smallint smallint varchar varchar smallint smallint varchar varchar varchar smallint smallint varchar smallint smallint smallint smallint smallint smallint varchar smallint varchar varchar smallint varchar varchar
5 3 3 5 20 5 5 3 null null
odntaut
tautno odnno keyno
operator
id equpos
11 5 5
null
pgagrp
grpcodeno pageno
pgchl
channelno psano equ
11 11
null
phyequ
equpos boardid status prodno rev
null null 20 8 5 null null
pninfo
extno profile position answerno timeout busygoto frinternal froperator frpublic useonce
20
pnstatus
extno profile
5 null 5 5 null null 8 9 null null
priana
extno auxno cat traffic service
157
calldivcat routingcat addcat transcat insttype icat cust name1 name2 info pres psarea searchareano blockingtime repetitionno signaldiagtype signaldiagvar holdingtime rfp bpos rpn route routrunk id id equpos route_id rvadata annnum rvanum annfrom annto devtype rvamsg msgnum msgname satgrp sat ancd node oflno inftyp ofltim ovflow
varchar varchar varchar varchar varchar varchar smallint varchar varchar varchar varchar smallint smallint smallint varchar varchar varchar varchar smallint smallint char char smallint smallint smallint int int smallint smallint varchar varchar varchar smallint varchar varchar varchar smallint
9 6 9 1 4 4
20 20 20 2
null null null null
null null 3 10 6 8 2 null null null
11 11
null null
null null null
60 5 5
null null null null
10 1 4
null null null null
158
Technical Guide
sms
extno msgserver iodevice
varchar int varchar varchar int int int int varchar smallint varchar varchar varchar varchar varchar varchar smallint varchar smallint varchar varchar varchar varchar varchar varchar varchar varchar
14 5
null
spext
extno specexttype
null
taskinfo
taskid batchid procid procinfo status resultdesc
2048 null 255 5 3 5 20 5 null 11 null null null null
taufunc
extno keyno value dig
usedext
extno type equpos
vcat
catno traffic service calldivcat routingcat descp
8 9 9 6 30 5 5 2
vmport
extno portno infocomind
null
159
PDM Database Organization

Data in the PDM database is organized in the following data tables. Some fields are included in multiple data tables. Which Table do you want to look at?
Table busy c_bell cfp code_r code_s confer cxnmob cxntrf datext dialdy extens ipbrd keyc_r keyc_s Includes Data For Busy hour Common bell group Cordless Extension Common Fixed Part MFC code receiver MFC code sender Conference Cordless Extension Mobility (for BC11 or later) Cordless Extensions Fixed Part (for BC11 or later) Data extension Dial tone delay Voice extension IP Extensions Key code receiver Key code sender
measinfo Measurements initiated by the user modgrp opcorg opindi opmann pagext pagsar pbxgrp pcmlin roubwy rouddi roudio rouinc rouout tone_r trunks Modem group Call origin groupfor PBX operator Individual PBX operator PBX operator manned time Paging number Paging search area Internal group hunting group number PCM line Both way (incoming and outgoing) route Direct indialing route Direct indialing outgoing route Incoming route Outgoing route Tone receiver Individual trunk
160
Technical Guide
SQL Server Data Volume Estimates

To avoid confusion, it is important that you understand the difference between automatic recording and automatic data extraction. Recording is performed by the MD110. Extraction is performed by Performance Data Manager.
SQL DB Period Primary Auxiliary 6 months 12 months Data 63 MB 108 MB Log Files 10 MB 10 MB Total Volume 73 MB 118 MB
Operator Workstation Data

Directory Assistance Databases
You must use the Directory Configuration Utility to set up directory data structures before using Directory Manager. After using this utility to create directory assistance data structures, you can add contents using Directory Manager or the Directory Import utility.
Application/Utility D.N.A. Directory Import Utility Description The Directory Import Utility can initialize your directory database with subscriber extension information extracted from MD110 hard disk tables or from appropriately formatted ASCII text files. Directory Manager is a day-to-day administrative application for both populating and managing the contents of Operator Workstation subscriber records.
D.N.A. Directory Manager Application
Operator Workstation Configuration

The following notes explain how and where Operator Workstation configuration settings are stored. How Settings Files are Created Operator Workstation user configuration and directory configuration settings are stored on Operator Workstation server and client machines. User and directory configuration files are not included with the initial installation of the Operator Workstation application. Instead, these files are created either when a user first makes changes to Operator Workstation settings, or when the user accepts the default settings and logs off Operator Workstation the first time. Permissions for Changing User and Directory Settings D.N.A. user permissions, which are controlled by the D.N.A. Server User Configuration Utility, are stored in the security database on the SQL Server. Note that one of the permissions for Operator Workstation is Preferences. The Operator Workstation application checks this setting to determine of the logged user is permitted to make changes to the Operator Workstation settings found under the Options menu. Where to Find Settings Files User configuration settings are stored in the username.ows file, and the directory configuration settings are found in the username.stg file. These files are located in the \Dna_s\Ows\Data or Dna_c\Ows\Data sub-directories, for server and client PCs, respectively.
161
Operator Console Settings Operator Console Configuration settings are stored in the Windows NT/2000 Registry under the HKEY_LOCAL_MACHINE\SOFTWARE\Ericsson\OPI\CurrentVersion key.
Directory Structures
D.N.A. Directory Structures
Refer to the directory structure illustrations in this section to validate system integrity. These structures represent the D.N.A. server and client directory configurations created by the D.N.A. installation program. Although the files contained in individual directories may vary from system to system, these fundamental structures must be maintained. Any differences may indicate the need to re-install some or all D.N.A. components.
Directory Manager (Server)
162
Technical Guide
Extension Manager (Server)
163
Administrative Tools (Server)
164
Technical Guide
Operator Workstation (Server)
165
Performance Manager (Server)

The Performance Manager directories support both the Performance Data Manager (PDM) and Performance Presentation Manager (PPM) applications.
Directory Browser
166
Technical Guide
Directory Manager (Client)
Extension Manager (Client)
167
Administrative Tools (Client)
Operator Workstation (Client)
168
Technical Guide
Performance Manager (Client)

The Performance Manager directories support both the Performance Data Manager (PDM) and Performance Presentation Manager (PPM) applications.
169
MML Commands
Extension Manager
The Extension Manager Application uses the following MML commands in its communications with the MD110.
Functional Grouping Automatic Call Distribution Automatic Network Call Distribution Commands ACGCC ACGMC ACGME ACGMI ACGRI ACPAC ACGRE ACBGI ACBGE NCNOI NCNOE NCICI NCICE NCCOI NCCOE NCGRI NCGRC NCGRE NCSGI NCSGC NCSGE NCGMI NCGMC NCGME NCGTI NCGTE NCGSP ADCOE ADCOI ADINE ADINI AOCOE AOCOI ASPAC AUCOE AUCOI CATII CBCAC CBELI CBGME CBGMI CDCOE CDCOI CDINE CDINI CHGME CHGMI CXAKE CXAKI CSTPE CSTPI CSTLE CSTLI DGCAC DGGME DGGMI DGGRE DGGRI DTCAC DTCCS DTEXC DTEXE DTEXI DTFUI ACTNI ACTNE EXCCS EXCAC EXCUC EXDPC EXTEE EXTEI GEDIC GEDIE GDNDE GDNDI GHCAC GHGME GHGMI GHGRI GPAGE GPAGI GPGME GPGMI GESPC GESPE GESPI DTCCS EXCCS IVBOI IVMAI IVMAE IVBOE
Abbreviated Dialing Account Code Application System Parameter Authorization Code System Time Common Bell Group Call Diversion Charging Cordless Extension CSTA Data Group Data Extension DNIS Analogue Extension Generic Extension Group Do Not Disturb Internal Group Hunting Group Call Pickup Common Service Profile Data Category Voice Category Integrated Voice Mail
Interception Service & Message Waiting ISEPE ISEPI ISDN Terminal ITCAC ITCUC ITNUE
170
Technical Guide
Digital Key System Telephone
KSANE KSANI KSCAC KSCAP KSCUC KSDDP KSEXE KSEXI KSFKC KSMDE KSMDI
Name Identity/Call By Name Night Service Paging
NIINE NIINI NSCOI NSCOE PAALE PAALI PACAC PACHE PACHI PAGIE PAGII PASAE PASAI
Personal Number Route Data Special Purpose Extension Voice Mail Recorded Voice Announcement Music On Hold Per Customer IP Extension Short Message Service
PEALC PELPC PELPE PELPI RODNE RODNI SPEXE SPEXI VMPOE VMPOI RADSE RADSI RAGAI RAGAE RAGAC RAMDE RAMDI CUMHI CUMHE IPEXI IPEXE IPEXC CXSYI CXSYC CXSYE MSCOI MSCOE
MD Support Utility
The D.N.A. Server MD Support Utility uses the following MML commands in its communications with the MD110.
Functional Grouping Calendar Data and System Identity Digital Extension Analog Extension Data Extension ISDN Extension Number Series Name Identity Group Hunt Automatic Call Distribution Automatic Network Call Distribution Common Bell Group Operator Data Group Modem Group Charging Group Group Call Pickup Commands CADAP KSCAP KSDDP KSTSP KSFKP KSMDP EXCAP EXDDP EXCCP DTCAP DTCCP DTDDP DTFUP ITDAP NADAP NIINP GHDAP ACGMP ACGCP ACPAP ACBGP NCNOP NCICP NCGRP NCGMP NCGSP NCSGP CBDAP OPDDP OPCGP OPRSP DGDAP MGMGP CHGMP GPDAP
171
Group Do Not Disturb Account Code Authorization Code Intercept Computer Recorded Voice Announcement Special Purpose Extension Trunk Paging Abbreviation Call Diversion Voice Mail Message Interception Computer Support Telephony Applications Application System Parameters Configuration System Data Group Junction Lines Program Correction Log Print System User Information Generic Extension Cordless DNIS Personal Number Number Conversion I/O-Data Integrated Voice Mail Customer Music On Hold IP Extension Short Message Service
GDNDP AOCOP AUCOP ICFUP RAGAP RAMDP SPEXP RODNP ROCAP ROEDP RADSP RADNP PAEDP PADAP PAALP ADCDP ADIDP CDIDP CDCDP VMPOP ISEPP CSTPP CSTLP ASPAP CNPIP CNLIP CNBIP SYEDP SYEVP GJLCP PCLOP SUDIP SUSIP GEDIP GESPP CXAKP ACTNP PELPP NUTRP IONCP IVMAP IVBOP CUMHP IPEXP MSCOP

The Numbering Plan Manager uses the following MML commands in its communications with the MD110.
Functional Grouping Number Conversions Private / Public Prefix Commands NUTRI, NUTRE CUPRI, CUPRE
172
Technical Guide

The Performance Data Manager (PDM) application uses the following MML commands in its communications with the MD110.
Functional Grouping Common Bell Groups Conference Units MFC Code Receivers MFC Code Senders Dial Tone Delay List active measurements in MD110 Data Extensions Extensions Cordless Extension Common Fixed Part Key Code Receivers Key Code Senders End individual active measurement in MD110 Modem Groups PBX Operator Manned Time PBX Operator CORG Internal Group Hunting (PBX) Group Number Paging on Search Area PCM Lines Direct In dialing Outgoing Route Trunks Tone Receivers Read traffic measurement data from MD110 HDU Commands TRCBI TRCOI TRCRI TRCSI TRDDI TRDIP TRDXI TREXI TRCFI TRKRI TRKSI TRMEE TRMGI TROMI TROPI TRPBI TRPGI TRPLI TRROI TRTLI TRTRI FIFCP
Specify Cordless Extension Common Fixed Part TRCFI for BC10 only Cordless Extension Traffic for BC11 or later IP Network Interface for BC11 or later TRCFI TRIPI
MD Support Command Line Synchronization

You can control the MD Support utility from the Windows NT/2000 command line. With this new release, you may specify: which individual node to synchronize, extension(s) or range of extensions to synchronize, or, LIM(s) or range of LIMs to synchronize, or features (e.g. digital, analog, ACD group) to synchronize. This means MD Support can be scheduled to synchronize the MD110 on a regular basis via a scheduling utility such as RDS Scheduler.
173
Command Line Syntax

Command line syntax for MD Support is: MDS /site:<site#> [/sync:{ext=(digit,..,digit-digit..)} | {digdual,ana,...} | {lim=(digit,..,digit-digit..)} ] The /site parameter is required, while the following settings are optional: = Individual extensions or range of extension = Individual LIMs or range of LIMs Supported MD110 Features digdual - Digital and Dual Access isdn - ISDN ana - Analog data - Data genext - Generic Extension dirinfo - Directory Information cbn - Call By Name opequ - Operator Equipment ocorg - Operator Call Origin Group cb - Common Bell Group dg - Data Group mg - Modem Group ch - Charging Group gh - Hunt Group ad - Automatic Call Distribution ancd - Automatic Network Call Distribution rvagnac - RVA Group Announcement rvamdat - RVA Message Data custmoh - Customer Music On Hold dnis - Dialed Number Information Service gcp - Group Call Pickup gdnd - Group Do Not Disturb accnt - Account Code auth - Authorization Code spext - Special Purpose Extension daynig - Day/Night Position page - Paging cabb - Common Abbreviation idiv - Individual Diversion cdiv - Common Diversion vm - Voice Mail
174
Technical Guide
msgint - Message Interception pn - Personal Number csta - Computer Supported Telecom. Appl. route - Route trunk - Trunk vcat - Common Voice Category dcat - Common Data Category csp - Common Service Profile equ - Equipment Position numse - Number Series pcm - System PCM/LIM msgdiv - Operator Message Diversion loc - Location Code numconv - Number Conversion lim - Line Interface Module pripubpref - Private/Public Prefix Examples To synchronize all information in node 1: MDS.EXE /site:1 To synchronize a range of extensions in node 1: MDS.EXE /site:1 /sync:ext=(1000,1004-1005) To synchronize a range of LIM in node 1: MDS.EXE /site:1 /sync:lim=(1-3) To synchronize digital and number series in node 1: MDS.EXE /site:1 /sync:digdual,numse To set up RDS Scheduler to run MD Support 1 Assign MD Support privilege to a D.N.A. account, e.g. Ericsson. 2 Log into RDS Configuration using the account in step 1. = Set up a schedule job running MDS, e.g. mds.exe /site:1. = RDS will save the current account into the registry. = Make sure to check the option Activate Using the Current Logged-In DNA Account.
3
When RDS Schedule invokes MDS, it will pass to MDS the schedule identifier that MDS uses to retrieve from the registry the account identification. Internally MDS uses this account to log in into D.N.A.
175
To set up other schedule utilities to run MD Support 1 Set up an account in DNA having the same name as the NT account. Assign the MD Support privilege to this account. 2 Scheduled a synchronization job running MDS. For example: mds.exe /site:1
Frequently Ask Questions

Directory Manager
Question: Directory Manager supports the following checkbox options. = Show in Visitor Registration OCX = Show in DNA Directory OCX How are these controls implemented? Answer: The DNA Directory OCX file (i.e. DNA_S\Share\bin\DNADir.ocx or DNA_C\Share\bin\DNADir.ocx) is used by many DNA and Non-DNA applications, including Operator Workstation, CCA, PSC, etc. It can also be used by third-party vendors or Web based applications. When used by third-party vendors, the Show in DNA Directory OCX option will enable/disable this display capability for the selected Directory Manager entry. Question: What does the extension category in Directory Manager stand for? Answer: In Directory Manager, the extension category is shown in the Subscriber window. When you select an extension from the Extension to Add list box, the category is shown in the Category list box. If you add a new extension, you may choose a category for it by using the Category list box. Categories apply to all extensions, not just primary extensions. The extension category was implemented to integrate Directory Manager and Operator Workstation with PSC. Directory Manager and Operator Workstation treat the extensions the same regardless of their categories. Since Directory Manager or Operator Workstation does not use the extension category, it is not shown at all in Operator Workstation, and it is not shown prominently in Directory Manager. Directory Manager just provides an easy way to assign a category to a new extension so that PSC can use the category.
D.N.A./CCM Server
Question: Is it true that you should not configure a D.N.A./CCM server as a Primary Domain Controller (PDC)? We have a customer who has made there DNA3 /CCM2 Server the Wins and PDC on the NT/2000 domain for about 60 pc's, we are noticing some very strange things happening on this LAN, Operator Workstation running very slowly etc. Answer: It has been noted that there are problems if your installation is supporting a fairly large D.N.A. installation (without CCM) with more than 20 operators, you have a lot of changes made to the database, and are using the diversion and messaging facilities.
176
Technical Guide
It is also assumed that you are using a standard 10 M-bit Ethernet LAN with the server connected via a hub. Indeed, such a configuration will exhibit such conditions (as you mentioned) as slow Operator Workstation performance and unpredictable network performance. This is probably due to the fact that making a lot of changes forces RDS to repopulate the database. However, at the same time there are a lot of requests coming in from the clients to the server to get information from SQL. Initially, it may appear that the problem would be in the server, but this is not necessarily the case. Instead, it is possible that the network card cannot handle the volume of information being sent and received, resulting in traffic collisions and impacted packages. This in turn will further increase the network traffic load because of the increased rate of re-transmissions. Note A 10Mbit ethernet LAN should never have a network utilization above 30%. The conclusion, in this case, is that the fewer requests the server's network card must handle the better the performance. You can achieve better performance by either reducing the amount of traffic generated and received by the server and not assign it as a PDC and WINS. Another possible solution would be to change from a hub to a switch for connecting the server to the LAN. This solution provides dedicated bandwidth to and from the server. Alternatively, a 100M-bit network card and port on the hub could also be a solution. To determine if the problem is the server or the network/network card, run Windows NT/2000 Performance Monitor and use the object "network segment" with counter %network utilization% and object "network interface" with counters Bytes total/sec, Bytes sent/sec, Packets Outbound Discarded and Packets Outbound Errors. This should give an indication of where the problem lies. Note Try to get the "Windows NT/2000 in the Enterprise" course material from Microsoft, where these details are explained. Wins and Dhcp should not be a problem for 60 PCs. Also, If your PDC only handles logon requests for these 60 PCs, there should be no problem. There exists similar installations (but without CCM on the same machine) and they work fine. Important Microsoft does state that you should never install SQL on a PDC, as it does affect system performance.
Question: How do I setup message diversion to work in a stable way? Answer: The issue is that it is not always the best idea to put a General Information Communications Interface (GICI) link over the Agent Box. The GICI link is used for Operator Workstation (OWS) messages and diversions. You can have RDS connect with the GICI Access Agent via the Telnet protocol (this Telnet connection is open all the time). However, a problem arises when the network link fails, or the Agent Box is restarted, etc. Windows NT/2000 does not inform D.N.A. that the Telnet connection is lost. This means that when phones are initiating diversions (with *23*x#), the Agent Box cannot deliver data to the Remote Data Server (RDS). The Agent Box does not have a buffer, so the data will be lost. When, on the other hand, Operator Workstation attempts to send a diversion (or message) it will try to contact the Agent Box without success and will re-establish the Telnet connection. The MML connection towards an Agent Box (for Extension Manager) is not so critical, and there is no problem in this area.
177
As an intelligent solution you can use the Serial Communications Server (SCS) to connect on one side towards the Remote Data Server (RDS) and on the other side towards an RS-232 connection to the ICUboard. This SCS Server must be a Windows NT/2000 computer that is located near the PABX to setup SCS start the SCS service in Control Panel / Services then run scssetup.exe. The communication between RDS and SCS is done via Named Pipes. Windows NT/2000 monitors each Named Pipe and informs the application when a pipe is broken. Then RDS will buffer the Operator Workstation messages and diversions and SCS will buffer the phone diversions. When the network link is reestablished all the data will be transferred. (max. down time of link is 24H). Question: What kind of local databases does Operator Workstation use? Answer: The LDBs have *.DAT and *.NDX files (like FoxPro) but they are in an Ericsson specific format. The local database files are a binary tree based design implemented by Ericsson. It is not based on any commercial products. You cannot read it with any 3rd party applications. To refresh the local databases try to delete the following files: \DNA_C\OPI\DATA\ *.DAT and *.NDX and restart Operator Workstation. Do not delete the *.OWS and the *.STG files because they are the configuration files for each user account in Operator Workstation. If the *.DAT and *.NDX files are not rebuilt again you will have a problem with your network or your RDS Service. To refresh the local databases 1 Delete the files \DNA_S\OPI\DATA\ *.DAT (or \DNA_C\OPI\DATA\ *.DAT) and *.NDX 2 Restart the Operator Workstation. 3 Do not delete the *.OWS and the *.STG files because they are the configuration files for each user account in Operator Workstation. If the *.dat and *.ndx files are not rebuilt again you have some problem with your network or Remote Data Server. Problem: Operator Workstation application crashes (fails) within 5 hours of startup in a configuration where an English language NT/2000 server is running with a Norwegian NT/2000 workstation. Solution: The problem is in the default configuration of the Norwegian NT/2000 Workstation and the English NT/2000 Server. When installed, they default to Disable Distributed COM. To solve this problem 1 Login as the NT/2000 Administrator. 2 Run DCOMCNFG.EXE. You should find this file under WinNT\System32 directory. 3 In Default Properties, select Enable Distributed COM. Enabling this flag eliminates this Operator Workstation crash problem.
178
Technical Guide
Digital Telephone Set Question: What are the key assignments for managing calls via the Digital Telephone Set (DTS)? Answer: This is the key configuration for handling calls via a DTS in D.N.A.
DTS Key Prog Clear Speaker Access 1 Access 2 Inquiry Transfer OWS Function On/Off Duty Clear Left and Right Answer incoming call Speech left Speech right Both-way speech Extend
Question: How does the receipt function in the Operator Workstation messaging dialog box work? Answer: If a MAPI session has been established, the Snd Rcpt key sends the message with a request for a return receipt. If the recipient's mail system honors the request, the operator's mailbox receives a message when the recipient opens the message from the operator. If sender and receiver both use the same mail server or post office (i.e. Microsoft Exchange Server or Microsoft Mail with a work group post office) return receipts are quite reliable. If one or both parties use SMTP mail, the results are less reliable. If the receiver is using Outlook with preview, it is possible for the message to be read without being opened. In that case, the return receipt is not sent until the message is either opened or deleted. If it was read in a preview and then deleted, the return receipt will say that the message was deleted without being read! Question: What is the function of the Operator Workstation meter key? Answer: Call metering requires hardware support on the MD110. If the MD110 is equipped with pulse counters and the public exchange uses metered trunks, then the operator can request that trunk calls be metered and get the pulse count (which represents time and charges) when the call ends. The count is displayed in the dial box. If the system does not support metering, pressing the meter key just displays Meter in the dial box, and then VACANT in the speech window. In this case it is better to program some other function for the key. Operator Workstation LAN Question: How much bandwidth is needed for a good performance in the Operator Workstation? Answer: This is impossible to say without knowing how many subscribers, UDFs, keywords, etc. your database has. Each time your Operator Workstation starts up, it copies the LDB of the server to the clients. If you have the size of the LDB, you know how much data will be copied over the network (only at startup of Operator Workstation and by default at 0200 Hours). For normal operation, during the day, Operator Workstation does not use much network traffic. This is of course depending on how many changes they do in Directory Manager during the day (changes will be send to the LDB of Operator Workstation client).
179
Factors other than bandwidth are more likely to cause network performance problems. In particular, be careful about the operating system security setup and the DNS and/or WINS servers. If possible, keep the D.N.A. client machines in the same Domain as the D.N.A. server. Whether your network uses a WINS (Windows Internet Naming Service) server or DNS (Domain Name Service) for address resolution, try to insure that an outage on that server does not adversely affect the D.N.A. machines. Problems with WINS/DNS do not affect Operator Workstation directly, but can become a factor if other applications are used concurrently. For example, something as simple as expanding a subdirectory in the Explorer or the Network Neighborhood can take a ridiculous amount of time if the primary WINS server is offline. Similarly, the logon and load of the user profile can be delayed as much as 15 minutes when the primary domain controller is down. The only time when bandwidth may be an issue is immediately after RDS has finished a database repopulation. It then pushes all the new local tables and indices to all its registered clients. Depending on the size of the database and the number of clients, the network (and RDS) can be very busy for a few minutes. RDS repopulation can be controlled via the RDS configuration utility. Its activity can be monitored (and recorded if desired) with the RDM utility. Both should be available in \DNA_S\MRS\BIN on the DNA server.
Remote Data Server

Question: What is the LOGDB? Answer: In the \DNA_S\MRS\DATA\RDS directory there is a part of the local database called LOGDB. This part of the database is getting bigger and bigger. It seems that RDS is sometimes very busy updating this file resulting in problems on the Operator Workstation clients. What is this LOGDB used for and why is it getting so big? LOGDB is the transaction log for RDSs local databases. All the updates to the local databases will be registered in this transaction log, and it is quite natural that it grows as new subscribers are added, deleted, or updated. Also, updates from messages and diversions are also logged. RDS uses this transaction log to synchronize all the DNA clients. This transaction log gets cleaned up on a nightly basis. Please refer to RDS Configuration Utility - SCHEDULE 2 - Local Database Clean Up Scheduled Audit. Question: Why is RDS so busy after using Dirpop? Answer: If you (for example) use dirpop.exe and close Dirpop before it changed anything, you may experience RDS active for about 20 minutes or so and take up substantial CPU time. Each change in Directory Manager is updated in the LDBs (local databases). These LDBs are mainly used by Operator Workstation (plus EMG and LFS). When Dirpop updates the database, these changes are not transferred to the LDBs during the importing. This would take to much CPU and Network resources. This is why Dirpop gives the command to populate the local databases to RDS when you exit. When you have used Dirpop, RDS has to make sure that the LDBs have the same information as the SQL database. This does take some time and resources, but Dirpop and RDS do not provide any notice to whether you actually changed something or not.
180
Technical Guide
Question: What does "Enable Automatic Data Synchronization From Extension To Directory D.N.A. Database" mean? Answer: This is a checkbox on the RDS Options tab. The Extension Manager database has three tables that need to be queried by RDS for internal purposes. However, since RDS only has access to the Directory Manager database, these three tables should be kept synchronization between Extension Manager and Directory Manager databases. If this is checked, RDS performs database synchronization with Extension Manager by copying Site, Divr, and Numser tables from EMGDB (Extension Manager side) to DIRDB (RDS side) at startup time. The Site table contains information on sites, the Divr table diversion reason codes, and the Numser table number series. It is checked by default and we highly recommend you to keep it checked. Question: How does the Standby Remote Data Server work? Answer: If (for example) RDS crashes, it switches over to the standby side and generates a DrOhan.log crash dump file under WINNT directory. You will also get the following message in the Event Log. E1186 - Remote Data Server Unexpectedly Terminated - Switching Over To Standby Remote Data Server This log entry indicates that the standby Remote Data Server has taken over the RDS business. The new active RDS spawns for another standby process to monitor it. Unfortunately, the new active RDS is now running as a process and not as a service. This is because it is not possible to run two instances of the same service simultaneously.
Serial Communications Server

Question: Can I run two different diversion systems on one GICI port? Answer: It could be practical to run two different diversion programs on the same GICI port when introducing a new diversion program. Then you can have old and new running in parallel for a period before switching. The optional SCS service (a.k.a. GICI Server) in D.N.A. was designed for that purpose. It allows multiple DNA servers to share the same GICI port and it also allows a third party Interception Computer to share the same GICI port. It is however not recommended to run multiple diversion and directory systems due to the overhead in work with updating two systems instead of one.

Question: How do I change the polling time for PDM? Answer: You can change this download time by adding a registry-value. /HKEY_LOCAL_MACHINE/SOFTWARE/ERICSSON/ You need to add the value: BatchTime, DWord, and enter the hour in hexadecimal. Example: Enter BatchTime=0A if you want to start PDM downloading at 1000 Hours.
181
Question: How does PDM work in BATCH mode? Answer: Is it possible, in a multi node environment, to extract data from only a certain node? For example, in a two-node system the second node is created for future use. When PDM.EXE BATCH is scheduled, PDM is also trying to extract from node two, witch results in errors because there is no MD110 to connect to. However, it is possible to select the desired node to poll. To select a node to poll 1 Create a key with the DNA Server machine name under HKEY_LOCAL_MACHINE/SOFTWARE/Ericsson/PMG/ Example:
HKEY_LOCAL_MACHINE/SOFTWARE/Ericsson/PMG/DNA_SERVER1
2
Add the key SkipSites with the string of the nodes you want to skip separated by commas (",") under the key created in Step 1. Example: If there are 5 nodes and only node 2 and 4 should be polled, set the registry string to 1,3,5, (end with a ",")
Question: Witch account is used for PDM in batch mode? Answer: In User Configuration you can allow or disallow a User to use PDM for a certain node. PDM polling however bypasses this D.N.A. security feature.
182
Technical Guide
D.N.A. Application Suite

Question: What different releases for D.N.A. exist? Answer: The following table contains the releases of MD110 D.N.A.
Version DNA 1.0 DNA 1.1 DNA 2.0 DNA 2.1 DNA 3.0 DNA 3.1 DNA 3.2 DNA 3.3 DNA 3.4 DNA 3.5 DNA 4.0 DNA 4.1 DNA 4.2 DNA 4.3 DNA 5.0 Release Information General released version of DNA1 Bug fix release of DNA1.0 General released version of DNA2 Bug fix release of DNA2.0 General released version of DNA3 Version for European Parliament (3 countries) BSS support for Global One EMG / MDS Leading Zero Support Business Phone Operator Workstation version Mobility Server 2 PMG & Operator Workstation General release version of DNA4 DNA 4.0 bug fixes, Outlook integration, and DDB Business Phone version AXE version General release version of DNA5
MD110 BC
Question: What ASPAC parameters are available for operator functions? Answer: The following table list ASPAC parameters.
ASPAC 2 9 Format PARNUM=2,PARVAL=DDDDD PARNUM=9,PARVAL=DDDDD Range 0 - 32768 seconds 0 - 32768 seconds Description Time before recall to PABX operator from a parked party. Time before a PABX operator is recalled, after a call is extended to a busy extension. Time before a PABX operator is recalled on no answer, after a call is extended to a free extension. Time before a call in the common operator queue is indicated by a flashing common queue counter on an alphanumeric console.
10
PARNUM=10,PARVAL=DDDDD
0 - 32768 seconds
14
PARNUM=14,PARVAL=DDD
10 - 100 in 0.5 second units
183
15
Time before calls in the individual PABX operator queue will be indicated as delayed. Time before a PABX operator is marked as absent after automatic call acceptance. Time before a PABX operator is marked as absent automatically when an indicated call is not answered. PABX operator call extending by means of Loop keys. Automatic and manual recall of the PABX operator after parking an external call Intrusion on a party with an external call. Maximum time a PABX operator can reserve an extension after conversation is complete. Time before a PABX operator is recalled, when a call is extended before answer to a paged extension. Maximum time a PABX operator can reserve an extension before ringing. PABX operator forced release of third party after intrusion. Request for camp-on busy facility for PABX operator calls over public ISDN. Choice of clock format on PABX operator console and DTS. Manual and automatic ringing for Operator Workstation. PABX operator can extend to busy extension without call waiting category. Common PABX operator call queue size.
16
17
PARNUM=17,PARVAL=DDDD
33 34
PARNUM=33,PARVAL=D PARNUM=34,PARVAL=D
0 - not allowed, 1 - allowed 0 - manual, 1 - automatic
36 38
PARNUM=36,PARVAL=D PARNUM=38,PARVAL=DDDDD
0 - not allowed, 1 - allowed 0 - 32768 seconds
39
0 - 32768 seconds
40
0 - 32768 seconds
57 76
PARNUM=57,PARVAL=D PARNUM=76,PARVAL=D
0 - not allowed, 1 - allowed 0 - not allowed, 1 - allowed
101 102 175
PARNUM=101,PARVAL=D PARNUM=102,PARVAL=D PARNUM=175,PARVAL=D
0 - 12 hour, 1 - 24 hour 0 - manual, 1 - automatic 0 - yes, 1 - no
195
99 - 255 calls in queue
184
Technical Guide
Registry
Question: What are the following Operator Workstation registry keys used for? Answers: HKEY_LOCAL_MACHINE\Software\Ericsson\OPI\CurrentVersion\Number This key holds a prefix number that will be dialed before the directory number of the subscriber selected in the directory list box. A typical use is to enable an easy way to override diversions. HKLM\Software\Ericsson\OPI\CurrentVersion\UseAltSpelling This key is intended to control the display of the closest matched names in the directory. Previous versions of Operator Workstation showed only the first and last names in the directory list box, even when the name that caused the match was an alternate spelling. The default is now to show the name that matched, surrounded with pairs of asterisks. By setting this registry value to 0, the name display reverts to the pre-DNA 4 method. HKEY_LOCAL_MACHINE \Software\Ericsson\OPI\CurrentVersion\Secrecy This key holds the feature access code for the Business Phone secrecy feature. HKEY_LOCAL_MACHINE \Software\Ericsson\OPI\CurrentVersion\ActivateMapiDialog When this value is set to 1 and MapiResolveName fails the MAPI dialog is displayed to permit the user to choose an email address. HKEY_LOCAL_MACHINE \Software\Ericsson\OPI\CurrentVersion\SendMessageOnCancel The default value for SendMessageOnCancel is 1. When set to 1, a message is sent when the MAPI Resolve Name dialog box is displayed and the user clicks the Cancel button. The ActivateMapiDialog registry item must also be set to 1 to display the MAPI Resolve Name dialog box.
SQL Server
Question: I cannot administer my SQL Server anymore, what to do? Answer: There have been other cases in which the SQL Server for a D.N.A. system has become difficult or impossible to control by normal methods. In most cases, the trouble begins when the log segment of the syslogs database is running out of space. When that happens, apparently the only command the SQL Server can respond to is "stop". Sometimes, a simple restart will clear up the problem. That turned out to be the case for a D.N.A. server that had been running continuously for 40 days. (It could not allocate any more pages in tempdb that was running in 2MB in RAM.) A real problem is when the server fails to restart. In this case, try starting it from the command line with the /m (single user mode) and/or the /f (minimally configured mode) options. Then make any necessary repairs and restart normally. A list of the command line options could be found in the Transact-SQL Reference Help, available under the Help menu of the SQL Server Enterprise Manager. Click the Search button, then the Find tab. Type in "command line" and scroll down the resulting list to the topic "sqlservr Command-line Executable".
185
ClockSync
Question: Does anyone know what happens if you have more than one ClockSync Server running on the network? How does a specific client know which ClockSync Server it needs to read? I do not see a computer name in the ClockSync part of the registry. When you have both a CCM and a D.N.A. server present in one NT/2000 domain, how will the CCM clients know that they need to use CCM server ClockSync, and vice versa for D.N.A. clients? Answer: It is OK to have multiple ClockSync servers on the network. The ClockSync server on which they were installed will update the clients. This is defined in the Registry in: HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/ClockSync/Parameters/ServerMachin eName The use of Windows NT/2000 named pipes means that the time request event is directed. ClockSync does not use TCP/IP Broadcast packets to send out the time. If you have two servers (CCM and DNA) each with a ClockSync Server process (EnableServer in the above key is 0x1), you could change one to be a client of the other. For example change CCM server machine to be a ClockSync client of the DNA server, then change all the CCM client machines to ask the DNA server for time updates. If you change the CCM server and not the CCM clients, then they will not get the updates. Note A ClockSync client cannot also act as a server.
SNMP
Question: I started one or more of the services that are flagged as manual start but they didn't show up in EVM, what's wrong? Answer: EVM, SNMP and DMI don't know which services are installed until they are started for the first time, due to a limitation in DMI that won't be propagated to EVM if the DMI runtime is already running. The solution is to briefly stop and then restart the CIMgr service. From that point on, all components will be aware of its existence whether it's running or not.
186
Technical Guide
Configuration
Networking (SNMP) Access Agent
The SNMP Agent for MD110 consists of two functional elements: = Access Agent = SNMP Agent This guide only explains the Access Agent, the only element used by the D.N.A. Application Suite. (The SNMP Agent element is used in D.N.A. Node Manager.) To configure the access agent device 1 Connect the supplied female RS-232 cable to COM4 (COM4 can only be used for programming the agent device, not for communications) 2 Configure your communication program to: 9600,8,n,1 3 Press the agent device's Reset button 4 Set the appropriate settings for the agent, Expect a system response similar to: Base System Boot r0.4.5 Apr 12 1996 Copyright (c) 1994 - 1995, Ericsson Business Networks AB Restart due to power-up reset
5
To change the agent configuration, press any key within five (5) seconds: (M)odify any of this, (C)ontinue or (A)bandon changes? [M]
For each of the following questions, you can press Enter to select the value shown in braces, or you may enter a new value. How do I run SOFT image? 0. Don't run SOFT image, stop in BOOT shell 1. Run the SOFT image Which one do you want? [1] 1 Security: Change user Id and/or password? [N] n Change this to Y if you want to have a new login_name/password HARDWARE PARAMETERS: Baud rate for serial channels [9600] Do you want to change the board's MAC addresses? [N] Use Ethernet interface? [Y]
187
This board's Ethernet IP address? (0.0.0.0 = RARP) [164.48.71.166] (0.0.1.0 Subnet mask for Ethernet? (0.0.2.0 (0.0.0.0 for none) [255.255.255.192] Ethernet Maximum Transmission Unit? [1500] Do you want a PPP interface? [N] Should there be a default gateway for packet routing? [Y] What is its IP address? [164.48.71.129] To check for Telnet access 1 Go into Telnet somewhere on a network PC 2 Type in the IP-address of the Agent 3 Type in Login name (name you gave to your Agent host) 4 Type in your password (password you gave to your Agent host) 5 Now you should get a $-sign. This means you are in the Unix operating system of the Agent. 6 Type after $-sign: ls -l. This will give you the directory of the UNIX RAM-disk . 7 Check the configuration of COM-ports with CAT comport.cnf. D.N.A. will try to access the IPU via the mml-port (see mml-entry in comport.cnf) 8 Type after $-sign: tncom mml and then send your SSSSS as a normal synchronization. You should be able now to synchronize with the MD110. 9 If you want to go back out of your session: type CTRL-D twice until you have the $-prompt again. To Configure D.N.A. Agent Box Access To link each D.N.A.-TELNET session with the IP-address of your agent, you need to setup TELNET in MD Support:
1
2 3 4 5 6
Set the Connection Type selection for each D.N.A. application to Telnet. The D.N.A. applications will select the mml-entry by default (see comport.cnf in Agent). Now setup the GICI-link via Agent Box. In RDS Setup you need to configure the GICI link to the Agent. Remember to enter a GICI-entry in the comport.cnf file. Connect with an FTP application into the Agent. Login with your login_name and password. Type bin for binary download Type get comport.cnf, and the file will be downloaded to your local disk Change the comport.cnf file to your demands (i.e., add entry GICI):
188
Technical Guide
(Sample comport.cnf file) #------------------------------------------------------------------# # # # # # # # # # # # # # # # # # # # # # # # # # # Lines starting with '#' are comment lines. FILENAME: comport.cnf Configuration file for the command tncom. tncom is used for a telnet-to-V24 connection. This configuration file gives the COM-port setting for a special TELNET connection. PARAMETERS: A configuration row has the following format, and the items must be separated by space: <symbol> <comport> <baudrate> <databits> <parity> <stopbits> <flow> <symbol> : Any symbolic name (maximum 50 character). Used to identify a port configuration. <comport> : Communication port COM1,COM2 and COM4. COM3 may be used but are reserved for MD110 or BIM. <baudrate>: 300, 600, 1200, 2400, 4800, 9600, 19200 or 38400 <databits>: Number of databits; 7 or 8 <parity> : e = even, o = odd, n = no parity <stopbit> : Number of stopbits; 1 or 2 <flow> : Software or hardware flow control; XON/XOFF, CTS or NONE EXAMPLE: Configuration:mml COM1 9600 8 n 1 XON/XOFF Start tncom:tncom mml
#------------------------------------------------------------------mml COM1 9600 8 n 1 XON/XOFF mml COM2 9600 8 n 1 XON/XOFF
gici COM3 9600 8 n 1 XON/XOFF

7
Type put comport.cnf to overwrite the file in your Agent with the updated version.
Note "mml" and "gici" must be lower-case!
Features in Agent
Agent has the ability to work with more than one login account. The default login account with version 1.0.x was "agent/spectre". Administrator Agent Box account is "root/sysadmin". = You cannot delete the Administrator Agent Box account; you can only add new accounts. = There is a possibility to change the root/sysadmin account, but we do not recommend this. = If you want to change the configuration of the Agent box, you can also do this remotely via Telnet (without the need of connecting to COM4). You can do this by typing the command "CONFIG" after the $ prompt. Note You must use <Ctrl> + J instead of <Enter> !
189
TCP/IP Protocols and Port Number Assignments Service Port Type Description
netstat ftp-data ftp telnet smtp nameserv nicname nicname login domain domain tftp gopher gopher finger finger www-http kerberos kerberos pop3 sunrpc sunrpc auth auth ntp nntp ntp netbios-ns netbios-dgm Netbios-ss sqlsrv snmp snmp snmptrap 15 20 21 23 25 42 43 43 49 53 53 69 70 70 79 79 80 88 88 110 111 111 113 113 119 123 123 137 137 150 156 161 161 162 ? TCP TCP TCP TCP ? TCP UDP ? TCP UDP UDP TCP UDP TCP UDP TCP TCP UDP TCP TCP UDP TCP TCP TCP TCP UDP ? ? ? ? TCP UDP TCP What is the network status File Transfer (Default Data) File Transfer (Control) Telnet Simple Mail Transfer (email) Host Name Server Who is Who is Login Host Protocol Domain Name Server Domain Name Server Trivial File Transfer Gopher Gopher Finger Finger World Wide Web HTTP Kerberos Kerberos Post Office Protocol - Version 3 SUN Remote Procedure Call SUN Remote Procedure Call Authentication Service Authentication Service Network Transfer Protocol Network Time Protocol Network Time Protocol NetBIOS Name Servicer NetBIOS Datagram Service NetBIOS Session Service SQL Server SNMP SNMP SNMPTRAP
190
Technical Guide
snmptrap bgp imap3 imap3 exe login who cmd syslog printer talk talk ntalk ntalk router uucp uucp uucp-rlogin uucp-rlogin klogin klogin pmd pmconsole radius radacct
162 179 220 220 512 513 513 514 514 515 517 517 518 518 520 540 540 541 541 543 543 1642 1643 1645 1646
UDP ? TCP TCP TCP TCP UDP TCP UDP TCP TCP UDP TCP UDP UDP TCP UDP TCP UDP TCP UDP TCP TCP UDP UDP
SNMPTRAP Border Gateway protocol Interactiv Mail Access Protocol Interactiv Mail Access Protocol Remote process execution Remote login Remote who (rwhod) Remote command (rsh) System Log Facility lpd spooler Terminal to terminal chat Terminal to terminal chat Newer version of terminal to terminal chat Newer version of terminal to terminal chat RIP UNIX to UNIX Copy UNIX to UNIX Copy a different variant of UNIX to UNIX Copy a different variant of UNIX to UNIX Copy Kerberized login Kerberized login PortMaster daemon in.pmd PortMaster Console Protocol Remote Authentication Dial In User Service RADIUS Accounting
See Also SNMP Agent
191
Customers
Service Provider Customer Groups
Service provider customers can be divided into two types. Type I Represents customers that have their own Operator Workstation and require the Service Provider to provide operator functionality through the NCOP-OWS only after working hours. These customers will have their own DNA Server, with DNA Administrative Tools, Directory Manager, and Operator Workstation software installed. Type II Represents customers that do not have their own Operator Workstation and require the Service Provider to provide operator functionality through the NCOP-OWS. These customers do not have their own DNA Server, and require the Service Provider to configure and manage their directory in the Service Provider DNA Server. Configuring Type I Customers After successfully installing Directory Manager, and Operator Workstation server and client installations:
1 2
Run the RDS Configuration Utility. In the RDS Options dialog box, disable the Enable Automatic Data Synchronization From Extension To Directory D.N.A. Databases option. This prevents RDS from attempting to synchronize data from the extension database to the directory database. In the PBX Information dialog box, enable the PBX Network Setup As Uniform Numbering Plan option. This will hide the node ID when customers use Directory Manager to assign extensions to their subscribers. Click the PBX Site Information Settings >>> button. Add as many PBX MD110 Centrex nodes as the customer's extensions are distributed on. Then, in the PBX Extension Numbering Series Settings >>>, add the appropriate extension ranges the customer is allowed to enter in Directory Manager. (Note that the customer is expected to enter only CDIR extensions, and will not know what EDIR extensions are.) The D.N.A. server is ready for use by the customer.
Note The customer should not have permission to access and modify the RDS Configuration Utility, this is to prevent them from adding extra nodes and extension numbering series.
192
Technical Guide
Configuring Type II Customers 1 Run Directory Manager on the Service Provider D.N.A. server. 2 Configure the directory for each of the Type II customers. (Note that each Type II customer should be assigned a particular department, and all subscribers that belong to a given Type II customer should be under the same department with their corresponding Customer Node ID (Node ID >= 1000) and CDIR extensions.) Each of the departments will be later used to identify which customer it is. For example, customers D through Z in the example above can be configured in the Service Provider Directory Manager as follows:
D.N.A. Server
After successfully installing Directory Manager, Operator Workstation, NPM, and other D.N.A. server and client components:
1 2
Run the MD Support Utility and synchronize the MD110 Centrex data to the SP D.N.A. server. Run Numbering Plan Manager (NPM) and configure each customer's numbering plan. This information is distributed to the NCOP-OWS clients by RDS on the service provider's D.N.A. Server, to be used for context switching between customer directories, making outgoing calls, identifying incoming calls, etc. Next run RDS Configuration Utility and in the RDS Options dialog box, make sure that the Enable Automatic Data Synchronization From Extension To Directory D.N.A. Databases option is enabled. This allows RDS to synchronize data between the extension and directory databases. In the PBX Information dialog box, disable the PBX Network Setup As Uniform Numbering Plan option. This will show the node ID when the service provider uses Directory Manager to assign extensions to subscribers.
193
Next configure the RDS Replication dialog box. There are two items to configure; Subscriptions and Publications. Under Subscriptions for each Type I customers that have their own D.N.A. server, add subscriptions to their D.N.A. server. Also add a subscription to the service provider's D.N.A. Server to subscribe the Type II customers. Under Publications, for each customer add a publication to the subscriptions made above. For customer Type II you need to publish a subscription from the SP D.N.A. server. For example, Customer D needs to be configured as follows:
The information in the Customer Name list box comes from Numbering Plan Manager. If NPM is not installed, this item will be grayed-out. For customer Type I, publish a subscription from that customer's subscription. If Customer A has more than one D.N.A. server, it is possible to add more than one subscription in the publication. Continue the publication of the rest of the customers.
194
Technical Guide
Serial Communication Server

Use the following procedure to install the Serial Communications Service (SCS). (Note that you must log on as a Windows NT/2000 administrator.)
1
2 3
Run and install the D.N.A. client installation program from the service provider's D.N.A. Server. It is important that the SCS Service is installed from the service provider's D.N.A. Server since it needs to access the Numbering Plan Manager database information. Next, run the NT/2000 Control Panel and start Services. Set the "StartUp" of the Ericsson SCS entry to Automatic. Then start the "Ericsson SCS" NT/2000 service. Next, run the SCS Configuration Utility from the D.N.A._C\SHARE\BIN directory and configure the SCS GICI devices. For each MD110 Centrex GICI communication port, set the Maximum DN Length to 10. Make sure the Filler Character and Maximum Terminal ID Length matches that of the MD110 Centrex configuration. Next, configure the customer list associated with this GICI port by clicking Customer List >>> button. Enter the D.N.A. Server Name of Type I customers and associated customer name. For Type II customers that have their directories maintained on the service provider's D.N.A. Server, enter the service provider's D.N.A. Server Name and select All Other Customers as a choice for the customer name. For third party customers that require sharing of the GICI connection, add a "Third Party Connection" and set the Coupled SCS Device ID. Configure the customer list by selecting Customer List >>> button for the Third Party GICI connection port. In this dialog box, enter any Server Name of the third party customer and associated customer name. (Note that only the first entry in the customer list is used. If you enter more associated customers in the list, these entries will be ignored by SCS; (i.e. only one customer is allowed to be associated to a third party GICI connection). Finally, run the RDS Configuration Utility on the service provider's D.N.A. Server and each of the D.N.A. Servers for Type I customers and configure RDS GICI ports to make SCS Connections. Make sure that you map the correct RDS GICI port to the correct SCS Serial Device. Incorrect mapping may result in GICI messages being sent to the wrong MD110 Centrex PBX.
NCOP-OWS
There is a general market requirement to be able to offer a twenty-four hour seven-day-a-week operator service. Many companies cannot justify the cost of having an operator on site outside of normal working hours, yet there is a market resistance, particularly high in Europe, to the use of answering machines. Network Centralized Operator Workstation (NCOP-OWS) can be a cost-effective way of delivering this type of service, enabling a single operator to support a large number of customers. NCOP-OWS is intended to offer this service only to customers using service provider-managed PABX solution, based on the Ericsson MD110 Centrex switch with D.N.A. Operator Workstations. There are a number of configurations required to successfully install and manage a NCOP-OWS with a large number of customers. This document is intended to address the D.N.A. administrator's specific needs to successfully configure the NCOP-OWS.
195
Definitions
SP FID D.N.A. DMG OWS NCOP-OWS EMG PMG NPM RDS LDS SCS EDIR CDIR LC (Service Provider) (Feature Implementation Description) (Dynamic Network Administration) (Directory Manager) (Operator Workstation) (Network Centralized Operator Workstation) (Extension Manager) (Performance Manager) (Numbering Plan Manager) (Remote Data Server) (Local Data Server) (Serial Communication Server) (Exchange Directory Number) (Customer Directory Number) (Location Code)
Service Provider Customer Groups

Service provider customers can be divided into two types. Type I Represents customers that have their own Operator Workstation and require the Service Provider to provide operator functionality through the NCOP-OWS only after working hours. These customers will have their own DNA Server, with DNA Administrative Tools, Directory Manager, and Operator Workstation software installed. Type II Represents customers that do not have their own Operator Workstation and require the Service Provider to provide operator functionality through the NCOP-OWS. These customers do not have their own DNA Server, and require the Service Provider to configure and manage their directory in the Service Provider DNA Server.
196
Technical Guide
The illustration below represents an example of a Service Provider with Type I and II customers.
Type I customers are represented by customers A, B, and C that have their own DNA servers. Customers D through Z, which are configured on the Service Provider DNA server, represent Type II. The DNA server for customers A, B, and C require that the Administrative Tools, Directory Manager, and OWS software to be installed. The Service Provider DNA server requires all DNA software to be installed. Directory from customers A, B, and C are replicated from their DNA servers to the Service Provider DNA server. Directories for customers D through Z are replicated from the Service Provider central directory into separate local directories (as shown above). The NCOP-OWS uses the replicated directories A through Z to conduct automatic and manual context switching.
Configuring Type I customers

After successfully installing Administrative Tools, Directory Manager, and Operator Workstation server and client installations, run the registry editor (REGEDT32.EXE) on the DNA Server, and set the following registry key to 1. HKEY_LOCAL_MACHINE\SOFTWARE\Ericsson\RemoteDS\Manager\AllowVirtualNod es This is a hidden key used to allow the RDS Configuration Utility to add new PBX Node Information, since the customer cannot run MD110 Support to synchronize the PBX Node Information and Extension Numbering Series against the MD110 CENTREX switch. Next run the RDS Configuration Utility and in the RDS Options dialog box, disable the Enable Automatic Data Synchronization From Extension To Directory D.N.A. Databases option. This is to stop RDS from attempting to synchronize data from the extension database to the directory database. In the PBX Information dialog box, enable the PBX Network Setup As Uniform Numbering Plan option. This will hide the node ID when customers use Directory Manager to assign extensions to their subscribers.
197
In the PBX Site Information Settings , add as many PBX MD110 CENTREX nodes as the customers extensions are distributed on, and then in the PBX Extension Numbering Series Settings add the appropriate extension ranges the customer is allowed to enter in Directory Manager. Note The customer is expected to enter only CDIR extensions, and does not know what EDIR extensions are! The customer should not have permission to access and modify the RDS Configuration Utility, this is to prevent them from adding extra nodes and extension numbering series. Now the DNA server is ready for use by the customer.
Configuring Type II customers

Run Directory Manager on the Service Provider DNA server, and start configuring the directory for each of the Type II customers. Each Type II customer should be assigned a particular department, and all subscribers that belong to a given Type II customer should fall under the same department with their corresponding Customer Node ID (Node ID >= 1000) and CDIR extensions. Each of the particular departments are later used to identify which customer it is.
Configuring the SP DNA Server After successfully installing the Administrative Tools, Directory Manager, Operator Workstation, NPM, and other DNA server and client installations, run MD110 Support and synchronize the MD110 CENTREX data to the Service Provider DNA server. Then run the Numbering Plan Manager (NPM) and configure each customers numbering plan. This information is used by RDS on the Service Provider DNA server to distribute to the NCOP-OWS clients to be used to context switch between customer directories, making outgoing calls, identifying incoming calls, etc. Next run the RDS Configuration Utility and in the RDS Options dialog box, make sure that the Enable Automatic Data Synchronization From Extension To Directory D.N.A. Databases option is enabled. This is to allow RDS to synchronize data from the extension database to the directory database. In the PBX Information dialog box, disable the PBX Network Setup As Uniform Numbering Plan
198
Technical Guide
option. This shows the node ID when the service provider uses Directory Manager to assign extensions to their subscribers. Next, configure the RDS Replication dialog box. There are two items to configure. = Subscriptions = Publications Under the Subscriptions for each Type I customers that have their own DNA server, add subscriptions to their DNA server. Also add a subscription to the Service Provider DNA server itself to subscribe the Type II customers. For example, in the above example, we should subscribe from the Service Provider DNA server and Customer A, B, and C DNA servers.
Under the Publications, for each customer add a publication to the subscriptions made above. For customer Type II need to publish a subscription from the Service Provider DNA server. The information of the Customer Name list box comes from the Numbering Plan Manager. If NPM is not installed, then this item will be grayed out. For customer Type I, you need to publish a subscription from that particular customers subscription. If Customer A has more than one DNA server, it is possible to add more than one subscription in the publication. Continue the publication of the rest of the customers. Configuring the NCOP-OWS After successfully installing Administrative Tools, and Operator Workstation client installations, run the registry editor (REGEDT32.EXE) on the NCOP-OWS client, and set the following registry key to 1. HKEY_LOCAL_MACHINE\SOFTWARE\Ericsson\OPI\CurrentVersion\CentralizedWo rkstation
199
This key is used to indicate that this Operator Workstation client is an NCOP-OWS. Next run the Operator Workstation client and configure the communication ports, user preferences, etc. as you normally configure for a normal Operator Workstation client. Now the NCOP-OWS is ready for use. To improve the performance of the NCOP-OWS, we recommend you run LDS on the same PC as the NCOP-OWS to help RDS synchronize the directory replications locally to the NCOP-OWS. Use the following procedure to install LDS. You must have logged in with an administrator account to be able to perform the first step successfully.
1 2 3
Run the Control Panel and start Services. Modify the StartUp of the Ericsson LDS to Automatic. Start the Ericsson LDS service. Run the LDS Configuration Utility from the DNA_C\SHARE\BIN directory and configure the LDS Replication Subscription and Publication items as you have done in the RDS Configuration Utility when configuring the Service Provider DNA server. Run the registry editor (REGEDT32.EXE) on the NCOP-OWS client, and set this key to the client computer name that the LDS service and NCOP-OWS is running on. HKEY_LOCAL_MACHINE\SOFTWARE\Ericsson\LocalDS\LDSServerName
Set the following key to 1. This forces NCOP-OWS to connect to LDS on the client NCOP-OWS PC rather than to RDS on the Service Provider DNA server. HKEY_LOCAL_MACHINE\SOFTWARE\Ericsson\LocalDS\UseLDS
Configuring the SCS Use the following procedure to install SCS. You must have logged in with an administrator account to be able to perform the first two steps successfully.
1 2 3
Run Control Panel and start the Services, modify the StartUp of the Ericsson SCS to Automatic. Start the Ericsson SCS service. Run the SCS Configuration Utility from the DNA_C\SHARE\BIN directory and configure the SCS GICI devices. For each MD110 CENTREX GICI communication port, set the Maximum DN Length equal to 10. Make sure that the Filler Character and Maximum Terminal ID Length matches that of the MD110 CENTREX configuration. Configure the customer list associated with this GICI port by selecting Customer List button. In this dialog box, enter the DNA Server Name of the Type I customers and the associated customer name. For Type II customers that have their directories maintained on the Service Provider DNA Server, enter the Service Provider DNA Server Name and select All Other Customers as a choice for the customer name as shown below. For third party customers that require sharing of the GICI connection, add a Third Party Connection and set the Coupled SCS Device ID. Next configure the customer list by selecting Customer List >>> button for the Third Party GICI connection port. In this dialog box, enter any Server Name of the third party customer and associated customer name. Note that only the first entry in the customer list is used. If you enter more associated customers in the list, then these entries are will be ignored by SCS; i.e. only one customer is allowed to be associated to a third party GICI connection.
200
Technical Guide
Next run RDS Configuration Utility on the SP DNA Server and each of the DNA Servers for Type I customers and configure RDS GICI ports to make an SCS Connection. Make sure that you map the correct RDS GICI port to the correct SCS Serial Device. Incorrect mapping may result in GICI messages being sent to the wrong MD110 Centrex PBX.
Performance
After successfully installing D.N.A. client installation with Centrex Operator Workstation option run the Operator Workstation client and configure the communication ports, user preferences, etc. as you normally configure for a normal Operator Workstation client. To improve the performance of the NCOP-OWS 1 Run LDS on the NCOP-OWS PC. This helps RDS synchronize the directory replications locally to the NCOP-OWS. Use the following procedure to install LDS. Note that you must have logged in with an NT/2000 administrator account to be able to perform the first step successfully. 2 Run the NT/2000 Control Panel and start Services. Set the "StartUp" of the Ericsson LDS entry to Automatic. Then start the "Ericsson LDS" NT/2000 service. 3 Run LDS Configuration Utility from the D.N.A._C\SHARE\BIN directory and configure the LDS Replication Subscription and Publication items as you have done in RDS Configuration Utility when configuring the SP D.N.A. server. 4 Run the registry editor (REGEDT32.EXE) on the NCOP-OWS client, and modify the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Ericsson\LocalDS\LDSServerName and set this key to the client computer name that the LDS service and NCOP-OWS is running on. Also modify HKEY_LOCAL_MACHINE\SOFTWARE\Ericsson\LocalDS\UseLDS and set this key to 1. This will force NCOP-OWS to connect to LDS on the client NCOP-OWS PC rather than to RDS on the SP D.N.A. Server. Now the NCOP-OWS is ready for use using LDS.
E-mail Integration
The Operator Workstation (OWS) application, which is a part of the Dynamic Network Administration (D.N.A.) suite, enables operators to take messages and deliver them via electronic mail systems. Operator Workstation employs Messaging Application Programming Interface (MAPI) functions for preparing and sending messages. Operator Workstation can obtain e-mail addresses from an external messaging system or from the D.N.A. subscriber database. Due to the variety of e-mail systems and their associated security requirements, a number of factors can prevent Operator Workstation from sending e-mail. It is the intent of this document to explain the requirements that must be met for successful integration of e-mail with Operator Workstation.
Operator Workstation E-mail Requirements

Operator Workstation will send e-mail when it can: = Load the MAPI library = Perform a null logon = Obtain an e-mail address Loading the MAPI library Operator Workstation can load the MAPI library if a MAPI-compatible e-mail system has been installed. Microsoft Mail from Windows NT/2000 and Microsoft Exchange satisfy this requirement. Look for
201
c:\winnt\system32\mapi32.dll, or use the Task Manager to determine if the MAPISP32.EXE process is running. There may be other MAPI-compatible e-mail systems, but they have not been tested. Performing a Null Logon A Windows NT/2000 user ID and password may (or may not) be needed to make a network connection to the work group post office. (If the connection is mapped in the Windows NT/2000 Explorer, be sure to check the "Reconnect at Logon" box.) The most reliable way of getting the Operator Workstation MAPI logon to succeed is to assign the same user ID to all the accounts an individual operator will use and to start the e-mail client program before Operator Workstation. Starting the e-mail client before Operator Workstation can be done either by double-clicking the Inbox on the desktop, or by including an Inbox shortcut in the Startup program group in the Windows NT/2000 user profile used by each operator. If an Operator Workstation shortcut is also included in the startup group, make sure that it runs after the e-mail client. Obtaining an E-mail Address Operator Workstation looks in two places: the Address Book for the local MAPI-compliant e-mail system (by using the MAPIResolveName function in mapi32.dll), and in the user-defined fields of the "subscriber" table in the SQL database "dirdb" which are of type EMAIL. (Note: Operator Workstation must have a data connection to the SQL server or it will not try to send e-mail.)
E-mail Related D.N.A. System Administration

There are a number of administrative tasks to perform for successful integration of e-mail with Operator Workstation, including directory configuration, RDS configuration, and system maintenance. Directory Configuration Use the Directory Configuration Utility to define any EMAIL fields in the database - before running any other programs that will use the database, e.g. Directory Import, Directory Manager, and Operator Work Station. RDS Configuration Use the RDS Configuration Utility to control how the Message Waiting lamps on subscriber telephones are utilized when e-mail messages are sent. It is usually best to not turn on the Message Waiting Lamp for e-mail messages because the subscriber can retrieve them without the operator's help. When RDS is configured to turn the lamps on, they are only extinguished when the operator deletes or prints all the messages for a subscriber. System Maintenance D.N.A. user account permissions - Control over the Operator Workstation e-mail options (and all the other Operator Workstation user configuration settings) is determined by the Preferences permission for the Operator Workstation in the D.N.A. User Configuration Utility. Choose Read/Write to allow operators to change their settings. Choose Denied to prevent changes. Subscriber database maintenance - It is important for continued success that changes in the D.N.A. subscriber database, the Windows NT/2000 user accounts, and the e-mail accounts are coordinated. Establish a procedure whereby updates in one system are made available for review and possible update in the other systems. Consider appointing someone specifically responsible for directory updates.
202
Technical Guide
Troubleshooting
Two effective ways of troubleshooting Operator Workstation e-mail problems involve using Windows NT/2000's Performance Monitor, and the D.N.A. Remote Data Monitor utility. Troubleshooting Operator Workstation E-mail with Performance Monitor Check whether Operator Workstation has successfully attached to a MAPI session with the help of Performance Monitor. When Windows Messaging (which is actually an Exchange client) is running, there are two processes of interest: exchng32.exe and mapisp32.exe. Set up Performance Monitor to watch the processor time and thread count for these two by selecting "Add to Chart", Object: Process, Instance: mapisp32.exe, and Counter: "% Processor time". Add another trace by selecting Counter: "Thread Count". Repeat the counter selections for Instance: exchng32.exe, then click "Done". You should have four traces on the chart now. If e-mail is sent with the mail program or by the Operator Workstation Message dialog, spikes will be seen in the processor time for both processes. Now "Exit and Log Off" from the mail program. If Operator Workstation succeeded with it's NULL MAPI logon, the thread count for mapisp32.exe will remain constant while the count for exchng32.exe falls to zero. If it has not, the thread count for mapisp32.exe will fall to zero within a few seconds of exchng32.exe. Troubleshooting Operator Workstation E-mail with Remote Data Monitor Use the Remote Data Monitor to help determine when messages are sent via e-mail. RDM.EXE is the utility program, usually found on the D.N.A. server at DNA_S\MRS\BIN, which reports Remote Data Service events. When RDS is configured to not turn on the Message Waiting lamps for e-mail, a lit lamp indicates that e-mail was NOT sent. The events reported by RDM enable you to determine whether the lamp was turned on without the need to go to each telephone. The following typical sequence of RDS events indicates e-mail was sent. [97/12/24 10:32:30] I7027 - Message From Client 1724: Message Waiting On; RecordID=780, NodeID=1, DN=66794 [97/12/24 10:32:31] I7128 - Broadcast To Clients: Message ID=7, TableID=1, RecordID=780, Update Type=8 [97/12/24 10:32:31] I7132 - Local Database Update Event Signal [97/12/24 10:32:31] I7128 - Broadcast To Clients: Message ID=7, TableID=1, RecordID=780, Update Type=8 [97/12/24 10:32:31] I7296 - Local Database Update End Of Event Signal The next sequence indicates a failure. Note the extra message sent via the MD's GICI port to turn on the lamp. [97/12/24 10:36:00] I7027 - Message From Client 1724: Message Waiting On; RecordID=780, NodeID=1, DN=66794 [97/12/24 10:36:00] I7128 - Broadcast To Clients: Message ID=7, TableID=1, RecordID=780, Update Type=8 [97/12/24 10:36:00] I7132 - Local Database Update Event Signal [97/12/24 10:36:00] I7128 - Broadcast To Clients: Message ID=7, TableID=1, RecordID=780, Update Type=8 [97/12/24 10:36:00] I7296 - Local Database Update End Of Event Signal [97/12/24 10:36:00] I7182 - Message To GICI ERICSSON1 Communication Port COM3: \0x02066679400\0x0D\0x0A
203
VSI and TSS

Voice System Interface
VSI is an ASCII protocol used to establish the serial (RS232) communication between the D.N.A. Serial Communications Server (SCS) and the Host connection of the Integrated Voice Response System (or IVR system). The VSI retrieves or updates Operator Workstation messages and message diversions. This level of integration between Operator Workstation allows Message Diversion Reason and Return Times to be presented by the IVR, without operator intervention.
Setting Up Communications and Configuration Parameters

The VSI user interface allows the system administrator to setup configuration parameters necessary for VSI to establish connections with the IVR (Voice) System. The user interface is similar to that of the Serial Communications Server (SCS) utility. VSI supports a protocol similar to that of TSS or GICI.
The VSI Protocol

As with GICI and TSS, the STX and CR LF characters are used, respectively, for triggering and ending message packages. STX CR LF 0 MMMM RRR T Start of Text Carriage Return Line Feed End of text msg Voice Mailbox Number Diversion Reason Diversion Type ASCII 02 ASCII 13 ASCII 10 ASCII 48 1-10 characters 000-999 0 - Non Passive (Divert Phone) 1 - Passive (Do Not Divert Phone) 12 character format (YYMMDDHHMMSS) 12 character format (YYMMDDHHMMSS) 00-99 00-80 0-160 characters 0-9 2-5 characters 00-99 ASCII 49 000-999 ASCII 32-127
SSSS EEEE
Start date/time* End date/time*
DD KK TEXT V XX NN 1 PPP Y
Record ID Length of Message text Message text** Voice Reason *** Terminal number Number of msgs/div. First part of text msg PBX Node ID Check Sum Byte****
204
Technical Guide
*If the Start and End date/time contains YYMMDD000000 then only the date is specified; if it contains 000000HHMMSS then only the time is specified; and if it contains 000000000000 then the default or indefinite date/time is specified. ** The maximum text length is 160 characters, but Max field length VoiceDesigner can handle is 132. Long messages must therefore be split into 2 parts. Max (actual) text length in one message will be 80 characters. *** 0 = Unknown, 1 = Message Diversion, 2 = Direct forwarding, 3 = Busy, 4 = No answer. These values are configured using VSI Configuration Utility. **** The 7-bit arithmetic sum of all the bytes in the message disregarding the checksum and the final CR and LF. If the sum is smaller than 20H (32 Decimal), then 20H is added to it. All messages sent between VSI Service and the receiver should acknowledge the VOICE System. An ACK (06H) must be sent if the received message is correct. A NAK (15H) must be sent if the received message is invalid due to incorrect checksum or missing the end code (i.e. CR LF). In the event the sender did not receive an acknowledgement message within 5 seconds, the sender re-transmits the message. Sending of acknowledge messages can be deactivated by using the VSI Configuration Utility. For the VSI protocol, it is required that all parts of each message type are included in order to be acknowledged by the Voice System Interface. All messages sent between VSI Service and the Voice System include a checksum byte. The VSI service can disregard the checksum byte if the checksum option is deactivated using the VSI Configuration Utility. Calculating the checksum is done by a 7-bit arithmetic sum of all the bytes in the message disregarding the checksum and the final CR and LF. If the sum is smaller than 20H (32 Decimal), then 20H is added to it. Following is a C-language example to calculate the checksum. int checksum(str, len) char *str; int len; { int sum = 0; while (len-- > 0) sum += *str++; sum &= 0x7f; if (sum < 0x20) sum += 0x20; return (sum); }
Capacities and Limitations

It must be possible to setup communication through at least 4 ports simultaneously towards a single voice system. This enables multiple Voice System callers to simultaneously access D.N.A. services. Note that this capacity may be increased in the future. Also note that more than one voice system may be connected in future releases. In this first version, handling of one Voice System only can be enough. Configuration settings for baud rate, COM port, SCS port etc. should be the same as for the Time System Server (TSS).
205
Time System Interface

D.N.A. Time System Interface (TSI) is an optional D.N.A. service module that connects to an external time monitoring system. TSI allows diversions to be entered in the time monitoring system, transferred to the D.N.A. Directory Manager application, and registered in the D.N.A. Directory database. As well, Message Waiting (MWT) indications can be sent from D.N.A. to the time monitoring system.
Interface
The time monitoring system is connected to a V.24 (RS-232C) port directly on to D.N.A. Server. Several time monitoring systems can be connected to D.N.A. at once. D.N.A. Time System Interface Module can be configured for 256 connections of each protocol type. In practice, the maximum number of connections is limited to the customer's Windows NT/2000. Logical Interface The logical interface between D.N.A. and the various time monitoring systems is defined in CCITT's Rec. V.24. The protocol is defined by a number of signals sent between the time monitoring system and D.N.A. Time System Interface. These signals are composed of a group of characters, each consisting of one start bit, seven to eight information bits, one parity bit, and one stop bit. The information bits are to be coded in accordance with ASCII. Baud rate, seven/eight information bits, parity, XON/XOFF and modem control are selectable.
Protocols
Five different protocols can be applied to the D.N.A. Time System Interface: CTR, GENERAL, FLEXIM, ESMI, and TIMECON. The protocols are grouped into different protocol families: CTR, GENERAL, and TIMECON belong to group 1 and FLEXIM and ESMI belongs to group 2. Asynchronous RS-232C, 8 data bits, no parity, transfer rate select able. The character code is 7 bit ASCII, with the Finnish special characters code as follows: Finnish Character Coding { 7B hex - 7C hex } 7D hex [ 5B hex \ 5C hex ] 5D hex Message Format <STX><message type><data><BCC><CR><LF> = = = = STX = 02H, Start of message message type = A char which determines how the rest of the message should be interpreted. data = Data space BCC = The 7-bit arithmetic sum of all the bytes in the message disregarding the checksum itself and the final CR. If the sum is smaller than 20H (32 dec), then 20H is added to it. = CR = End of message = LF = Optional
206
Technical Guide
FLEXIM Protocol
The phone switch operator has a FLEXIM info terminal. FLEXIM sends a message to the D.N.A. Time System Interface each time a person logs in or out using his card. The message contains that person's id information (card number, phone number or personal id-number) and in addition the return time (if known), the login/logout time (optional 1) and the validation time (optional 2). The D.N.A. Time System Interface tells FLFXIM if any person has a call request or some other message. The next time such a person logs in or out, this message will be displayed on the FLEXIM console in plain text form in addition to the time and date when it was entered. A person can have multiple messages in the system at the same time - when the login or logout is completed, all read messages are deleted from the system. A message may contain a maximum of ten 16-character lines. In addition, FLEXIM sends Time Sync messages to the D.N.A. Time System Interface. Either end can initiate data transfer. All messages are acknowledged as either correct or faulty. There are two kinds of fault acknowledgement messages: frame error and message error. Frame error means that the receiver has gotten the beginning code of the message but not the end code, or that the checksum is wrong. The sender must send the message again. Message error The receiver has received a message that has a correct length and a correct checksum, but which contains an invalid message. The sender writes an entry about the faulty message in its own log file and continues by sending the next message in line (if any). The faulty message is not re-transmitted. When the FLEXIM send program starts it first sends the status information of all the people in the system to the receiving end, regardless of what data has been previously transmitted. In the event of a frame error (see above), message re-transmitting is attempted until midnight. If the frame error persists after 00:00 the message is discarded and the system revert back to sending all of the system status information from the beginning. The same situation forms in the event of a takeout. The system waits 5 seconds for an acknowledgement message before retrying. When the status information for all the people in the system has been successfully sent the program starts sending information on logouts and logins from the program starting time onwards.
207
Messages sent from FLEXIM to D.N.A. Time System Interface Login/logout message STX = Start of message X = Reason code TAB = Field separator X = Phone number / Card number / ID number (field length 111,bytes) TAB X = Other Reason code (length 0-3 bytes) TAB DDMM = Return date (4 bytes if specified, otherwise 0) TAB HHMM = Return time (4 bytes if specified, otherwise 0) TAB DDMM = Login/logout date (optional') TAB HHMM = Login/logout time (optional 1) TAB DDMM = Validation date (optional 2) TAB HHMM = Validation time (optional2) BCC = Checksum CR = End of message LF optional 1: Configurable when the system is installed. optional 2: Configurable when the system is installed, contains option I. Reason Code 2 In 3 Out 4 Trip in 5 Trip out 6 Vacation out 7 Sick out 8 Overtime out 9 Other Reason in 0 Other Reason out a Lunch out b Personal out Other Reason is a customer-specified function. Pressing a number and the "Other Reason" key on the FLEXIM terminal uses it. This results in either `0' (In) or `9' (Out) being passed to the info system, with the other reason number (`0' ... `199') in the Other Reason field of the message. Return date/time is not checked by the system, it is always sent exactly in the form that the user types it in - it is possible to leave incomplete or impossible return times. The return time must be in numeric
208
Technical Guide
form. However, in the FLEXIM system the login/logout information and the return date/time information are given separately, so when the user specifies a return date the D.N.A. Time System Interface receives two messages with the same reason code. The second of these contains the return date/time information. Login/logout time, when sent, is always some time of the on going day. The information is not necessarily sent in a chronological order, however. Validation date/time comes into play when the so-called "double login/logout" feature of the system is in use, in which the user gives information of a future event using the FLEXIM terminal (for example: "Working overtime today, on a trip tomorrow". The validation field gives the time when the second event becomes valid. In a double-login/logout situation the D.N.A. Time System Interface may receive up to three consecutive "logout" messages for the same person. = A logout message-without a validation time or a return time, for example a simple "Out". = A message with a double-log field, for example "Trip" with a validation time and date of 8:00 AM the next morning. = A message with all of the information in the previous case and the addition of a return time/date field. The interval between these messages may be several minutes, and messages from other people may occur between them, naturally. Examples Normal Login <STX> 2 <TAB> 150349115E <TAB> <TAB> <TAB> <BCC> <CR> Normal Logout <STX> 3 <TAB> 150349115E <TAB> <TAB> <TAB> <BCC> <CR> Trip In <STX> 4 <TAB> 123 <TAB> <TAB> <TAB> <BCC> <CR> Trip Out + return time <STX> 5 <TAB> 124 <TAB> <TAB> 1507 <TAB> 1530 <BCC> <CR> Trip Out + return + log time <STX> 5 <TAB> 124 <TAB> <TAB> 1507 <TAB> 1530 <TAB> 1307 <TAB> 1300 <BCC> <CR> Trip Out + return + log + validation <STX> 5 <TAB> 124 <TAB> <TAB> 1507 <TAB> 1530 <TAB> 1307 <TAB> 1300 <TAB> <1407> <TAB> 0800 <BCC> <CR> Vacation + return time <STX> 6 <TAB> 1256 <TAB> <TAB> 1305 <TAB> 0800 <BCC> <CR> Sick + return time <STX> 7 <TAB> 1115 <TAB> <TAB> 1405 <TAB> 0630 <BCC> <CR> Overtime Out <STX> 8 <TAB> 1115 <TAB> <TAB> <TAB> <BCC> <CR> Other Reason + code + return <STX> 0 <TAB> 1503 <TAB> 2 <TAB> 305 <TAB> 1200 <BCC> <CR> Other Reason + code (In) <STX> 9 <TAB> 890 <TAB> 3 <TAB> <TAB> <BCC> <CR>
209
Absence deactivate registration STX = Start of message X = Reason code (2 or 4 or 9) TAB X = Card number TAB TAB TAB TAB TAB BCC = One byte checksum CR = End of message D.N.A. has only one absent code while FLEXIM has many. Because of this, the field F sent from FLEXIM with the values 2, 4 or 9 will all be translated by D.N.A. as deactivate absence. It will delete corresponding diversion in D.N.A. that previously was created by the time system diversion originator. Diversions that were created by other diversion originators will only be deactivated. Absence activate registration: The same as login message. Reason code sent from FLEXIM with the values 3, 5, 6, 7. 8, A or B will all be translated by D.N.A. Time System Interface as activate absence. It will create a diversion for the corresponding subscriber. The D.N.A. Time System Interface absent code that will be used for the diversion will be defined by the configuration command TRANS. Since not all fields in a message are required, a message can be composed in several different ways. See the following examples: <STX> 2 <TAB> 11999 <TAB> <TAB> <TAB> <BCC> <CR> Deactivate absence for card number 11999. Note three is the minimum number of < TAB> after the card number, even if the message does not contain any more information after the card number. <STX> 3 <TAB> 2356 <TAB> <TAB> 0312 <TAB> 1445 Activate absence for card number 2356 with return date and time 3 December 14:45. Reason code 3 will be translated to corresponding D.N.A. Time System Interface absent code and assigned to the diversion. <STX> 0 <TAB> 445577 <TAB> <X> <TAB> 2806 <TAB> <TAB> 2106 <TAB> 0732 <BCC> <CR> Activate absence for card number 445577 with return date 28 June and from date and time 21 June 07:32. Other reason code <X> will be translated to corresponding D.N.A. absent code and assigned to the diversion.
210
Technical Guide
Time Sync messages STX = Start of message K = `K' is the Time Sync message type TAB YYMMDDHHMMSS = Date and time (12 bytes) BCC = Checksum CR = End of message If the D.N.A. Time System Interface does not respond to a Time Sync message it is not resent. If the D.N.A. Time System Interface responds with a frame error the sending of the message is retried (max. three times). FLEXIM message acknowledgements Correct: <STX> <A> TAB <id field, as in message> <CR> Message Error: <STX> <N> <CR> Frame Error: <STX> <E> <CR> Note As has been said before, a "Frame Error" message is sent only in case of an error in the message frame (Start/End codes or checksum). A message with a correct frame but bad contents is acknowledged with a "Message Error" message. If no acknowledgement is received, the message is resent. Retries continue until midnight, at which time a "line down" condition is logged and all status info is resent. The status info is resent until successful, after which normal sending of login/logout messages is resumed.
211
Messages sent from D.N.A. Time System Interface to FLEXIM Call requests STX = Start of message S = `S' is the Call Request message type TAB X = Personal ID field (1-10 chars) ' ' = SPACE (optional 3) MMDDHHMM = Request ID (optional 3) TAB message = The message body, max. 16 chars TAB message = A second message (mix. 10 messages) etc. BCC = Checksum CR = End of message optional 3: Configurable when the system is installed The Request ID is equal to the time and date that the message was entered into the system. Using this field, the D.N.A. Time System Interface can sends messages that have an entry time that is different from the current (real) time. The default if to consider the entry time to be the current real time if this field is missing. Removal of messages STX = Start of message P = `P' is the Remove Message message type TAB X = Personal ID and optional Message ID as in the Call Request message BCC = Checksum CR = End of message This message causes the removal of all call requests for the given person from the FLEXIM system. If a Message ID is specified, only matching messages are removed.
212
Technical Guide
Removal of all messages STX = Start of message P = Remove Message -field type BCC = Checksum CR = End of message This messages causes the removal of all call requests sent by the D.N.A. Time System Interface from the FLEXIM system. 3.1.1.2.4 Init requestSTX = Start of message I = `I' is the Init Request message type CR = End of message The FLEXIM system acknowledges the message and sends the status of all the people in the system to the info system. D.N.A. Time System Interface message acknowledgements As FLEXIM.
General Protocol
Data messages exchanged between D.N.A. Time System Interface and the time monitoring system are composed by ASCII coded characters. The messages are composed of the following fields Login/logout message STX = Start of message X = Message type (B or C or D) X = Card number (field length 1-11,bytes) X = Reason code (A-Z, a-z) X = Ignored data (field length 1 byte) X = Return time (the length is depending on the message types ) X = Message waiting indication ETX = Start text BCC = Checksum
213
= <STX> Start of Text - A one byte ASCII code denoting the start position of the text. Each message will start with the STX field. = Message type - A one character message type with the value B, C or D. D.N.A. Time System Interface will ignore messages with other message types. The ignored message will also be acknowledged with ACK. = Card Number - A unique card number that can be up to ten alphanumeric characters long. Normally this field is set to any number in the range 1 to 9999999999 that is then translated to a subscriber in D.N.A.. The length of the card number is configured at installation. Card number length will be defined by the configuration command CARD. = Reason Code - A one character absent reason code ( A-Z, a-z ). The translation table for D.N.A. absence codes will be defined by the configuration command TRANS. = Ignored data - A one character long data field ignored by D.N.A. Time Information System. ( Could hold any value ). = Return Time - A four character long number giving the time of return for message type C. This field becomes a six plus four character long number for message type D. See further description of message type D. Interpretation depends on absent reason code given. ( DDMM = Day and month. HHMM = Hour and minute.) = Message Waiting Indication - A one character long data field specifying if message-waiting indication should be activated or deactivated. = <ETX> Start text - A one byte with ASCII character ETX. Each message will start with ETX. = BCC Checksum - A one-byte check character. The check character is calculated as an XQR sum of all characters from F up to and including <ETX> ( <STX> is not included ). All messages sent between D.N.A. Time System Interface and the time monitoring system should be acknowledged by the receiver. An ACK must be sent if the received message is correct. A NAK ( H15 ) must be sent if the received messages is invalid. Sending of acknowledge messages can be deactivated by using the configuration command ACK. For the General protocol it is required that all parts of each message type are included in order to be acknowledged by the D.N.A. Time System Interface. Messages sent from General Time Monitoring System to Time System Interface Arrival and Gone Out Registration STX = Start of message B = Message type is set to B X = Card number (field length 1-11,bytes) X = Reason code (A-Z, a-z), lowercase: arrival, upper case: gone out X = Ignored data (field length 1 byte) ETX = Start text BCC = Checksum
214
Technical Guide
If the absent reason code is a lower case character, the message is considered to be an arrival message. In this case, D.N.A. Time System Interface deletes all old diversions created from the time monitoring system and deactivates all other active diversions. If the absent reason code is an upper case character, the message is considered to be a gone out registration. D.N.A. Time System Interface creates a diversion with the given absent reason code and a default return time. Example : <STX>B1234a <ETX>? An arrival message (lowercase a), for card number 1234. ( The check character is not calculated correct in the example. ) Gone Out Registration STX = Start of message C = Message type is set to C X = Card number (field length 1-11,bytes) X = Reason code (A-Z, a-z). absent reason code. X = Ignored data (field length 1 byte) TTTT = Return time (DDMM or HHMM: 4 bytes if specified, otherwise 0) ETX = Start text BCC = Checksum This message is always a gone out registration. D.N.A. Time System Interface creates a diversion with the given absent reason code and the return time that is specified. Depending on the absent reason code, the TTTT is interpreted either as a time ( HHMM = Hour and Minute ) or as a date ( DDMM = Day and Month ). For the time format D.N.A. Time System Interface will use a default date to create a complete return time. For the date format D.N.A. Time System Interface will use a default time when creating the complete return time. The connection between a certain absent reason code and a time/date format is defined during installation.
215
Gone Out Registration STX = Start of message D = Message type is set to D X = Card number (field length 1-11,bytes) A = Reason code (A-Z, a-z) X = Ignored data (field length 1 byte) DDMMYYHHMM = Return time (the length is 10) ETX = Start text BCC = Checksum This message is always a gone out registration. D.N.A. Time System Interface creates a diversion with the given absent reason code and the return time that is specified. The return time can contain both information about date (DDMMYY) and time (HHMM). If DDMMYY has the value 000000 then no return date is included. D.N.A. Time System Interface will then use the default date for the current absent code. IF HHMM has the value "0000 then no return time is included. D.N.A. Time System Interface will then use the default time. The connection between a certain absent reason code and a default return date/time is defined during installation. Messages sent from Time System Interface to General Time Monitoring System Message Waiting Indication STX = Start of message C = Message type is set to C X = Card number (field length 1-11,bytes) M = Set to A if activate, set to B if deactivate ETX = Start text BCC = Checksum To activate the message waiting, the M character is set to "A". To deactivate the message waiting, the M character is set to "B". Using the configuration command WAIT can deactivate sending of the message waiting indication.
216
Technical Guide
CTR Protocol
Data messages exchanged between D.N.A. Time System Interface and the CTR Time Monitoring System are composed of ASCII coded characters. The messages are composed of the following fields: STX = Start of message X = Message type ( 2 digits from 65 to 71) X = Card number X = Absent reason code (0~9) X = Return time (MMDD or HHMM) CR LF = <STX> Start Text - A one-byte field with the ASCII character STX. Each message will start with STX. = Card Number - A four character long card number. ( "0000"-"9999" ) Card number length is usually defined by the configuration command CARD, but for the CTR system, the card number length is fixed to 4. = Absent Reason Code - A one character absent reason code ( "0"-"9" ). Translation table for D.N.A. absence codes will be defined by the configuration command TRANS. = Return Time - A four character long number giving the return time. HHMM ( MMDD = Month and day, HHMM = Hour and minute.) = <CR> Carriage Return - A one-byte field with the ASCII character CR. = <LF> LF - A one byte field with the ASCII character LF. Each message sent from the CTR system will end with the combination <CR> <LF>. For the CTR protocol, it is required that all fields of each message are included in order to be acknowledge by the D.N.A. Time System Interface. Messages sent from the CTR Time Monitoring System to D.N.A. Arrival Registration Upon receiving this message from the CTR system, D.N.A. Time System Interface deletes all time monitoring system diversions and deactivate all other active diversions for the given card number. STX = Start of message 65 = Message type is set to 65 X = Card number CR LF
217
Gone Out Registrations Upon receiving this message from the CTR system, D.N.A. Time System Interface will create a diversion with a default absent reason code and a default return time for the given card number. STX = Start of message 66 = Message type is set to 65 X = Card number CR LF In this case, D.N.A. Time System Interface will create a diversion with the given absent reason code and a default return time. STX = Start of message 67 = Message type is set to 65 X = Card number A = Reason code CR LF D.N.A. Time System Interface will, in this case, update a previously created time monitoring system diversion with the specified return time. D.N.A. Time System Interface will use a default date to create a complete return time. STX = Start of message 68 = Message type is set to 68 X = Card number HHMM = Reason code CR LF Update a previously created time monitoring system diversion with the specified return time. D.N.A. Time System Interface will use a default time to create a complete return time. STX = Start of message 69 = Message type is set to 69 X = Card number MMDD = Return time CR LF
218
Technical Guide
Messages sent from Time System Interface to CTR Time Monitoring System Sending of these messages can be disabled in D.N.A. Time System Interface by using the configuration command WAIT. Deactivate Message Waiting Upon receipt of this message, D.N.A. Time System Interface will deactivate message waiting for card number X. STX = Start of message 70 = Message type is set to 70 X = Card number CR LF Activate Message Waiting D.N.A. Time System Interface will, in this case, activate message waiting for card number X. STX = Start of message 71 = Message type is set to 71 X = Card number CR LF
ESMI Protocol
The ESMI protocol is in the same protocol family as the FLEXIM protocol. Messages sent from ESMI Time System To D.N.A. Time System Interface The message format (absence codes): STX = Start of message X = Message type (2 or 3 or A or E) TAB X = Identification number (1 - 10 digits) TAB MS = Reason code for out (1-9: pre-defined. 10-63: free) TAB DDMM = Return date (0 to 4 digits) TAB HHMM = Return time (0 to 4 digits) BCC = Checksum CR
219
Explanation of the records = STX Start of message (= ASCII 2) = X Message type: 2 = in, 3= out, A = reply message ok, E = reply message error = TAB TAB-mark, works as a separator = xxxxxx Identification number, Iength 1 - 10 digits = MS Reason code for out (1-2 marks if given, otherwise 0 marks). Explanations used: 1=trip, 2=vacation, 3=sick, 4=health care, 5= business, 6=own, 7=overtime, 8=extended working time, 9=Iunch, 10...63 free codes = DDMM The return date. 0-4 digits = HHMM The return time. 0-4 digits. The date and time of return wouldn't be set if it is not known. = BCC Checksum. = CR Carriage-Return. In this case the separator won't send anything. Message will re-transmit after 5 S, if TS won't get any reply. Also if TS-system gets error message, retransmit will be done. Re-transmit will be done only once. If the OK -reply won't come after this, system continues with a new message. Reason codes in TS-system (in case): All messages will be sent by "in" code. Out codes: - All reason codes will be in MS field. Others: Correction message will be sent from TS-system Reply from the TS-system to D.N.A. Time System Interface Reply, if the message is OK: STX = Start of message A = Message type is set to A TAB X = Identification number (1 - 10 digits) CR Reply, if there is an error in the message: STX = Start of message E = Message type is set to E CR
220
Technical Guide
Messages sent from D.N.A. Time System Interface to ESMI Time System
TS-system terminal setting message: STX = Start of message S = Message type is set to S (S is TS-system message) TAB XXXXXX = Identification number (1 - 10 digits) TAB sss = Message contents TAB sss = Message contents TAB BCC = Checksum CR Explanation of the records STX Start of message (= ASCII 2) X Message type: S = TS terminal message, A = reply message ok, E = reply message error TAB TAB-mark, works as a separator XXXXXX Identification number, length 1 - 6(10) digits ss... s TS Terminal message contents, CR or TAB not included. A message can include up to 10 text rows. Since a message row in D.N.A. Time System Interface can be up to 40 characters, these rows will be divided into several text rows. Words longer than 20 characters will be truncated. Overall, length should not exceed 80 characters. NOTE: Only first two ss.. .ss records will be approved as TS-system terminal message, others will not be handled. if ss... ss records are blanks, will the XXXXX persons TS terminal message be removed BCC Checksum, will be counted by marks (including the STX-mark) sum mod 128, and if the sum is under 20H, there will be added 20H. CR Carriage-Return Reply from the D.N.A. Time System Interface to TS-system if the message is OK; STX = Start of message A = Message type is set to A (A is OK) TAB XXXXXX = Identification number CR Reply, if there is an error in the message: STX = Start of message E = Message type is set to E (E is error) CR
221
TSI systems checking and replies: Message should start with STX S TAB -marks and checking sum should be right, otherwise error in message -reply will be sent, In case: error in reply, TS-system won't send any error in message -reply.
TIMECON Protocol
The TIMEC0N protocol is in the same protocol family as the GENERAL protocol. Stamping Message The stamping message type: "B" and "C" , is equal to the stamping message into GENERAL-protocol. However the return time should be interpreted different than in GENERAL-protoco1 (see below). Return Time The return time unit determined in the contents of this field. If position (3 & 4) is between 01 - 12 then it is treated as a date, otherwise as a time, this means that time contains minutes l to 12 each hour are sent as 00 , 13 or bigger. Clock Message TIMECON has a message called clock message, the clock message is repeatedly sent from time system to TSI as an online check. TSI should answer with an <ACK> if this message is OK. STX = Start of message X = Message type (A or D or Z) HHMM = Time information YYMMDD = Date information EXT BCC = Checksum X - Message type is something else than "B" or "C". TSI algorithm: IF F in ("A", "D", "Z") THEN Intepret_Clock_Message HHMM - Time info HHMM TSI algorithm: IF ABS( HHMM - D.N.A. Time ) > 5 min THEN Logg_Warning IF ABS( HHMM - D.N.A. Time ) > 15 min THEN Logg_Error YYMMDD Date number starting with a value of 0001 from 76-01-01. TS-system algorithm: None, ignore this field The time info from TSU will be check and logged as a Warning if it differs 5 - 15 minutes and an error will be logged if it differs more than 15 minutes, it should only log first time it receives a time zone outside D.N.A. time. It should be possible to change the range value for the invalid time zone, but it will default be 5 min and IS min.
222
Technical Guide
Exchange Interface
The D.N.A. Interface is compatible towards the exchange from ASB50101 R4/1 and later releases of the exchange.
Message Types
There are two types of invalid messages. Frame error - This means that the receiver has received the beginning code of the message but not the end code, or that the checksum is wrong. The sender must send the message again. This is done when the receiver sends a NAK to the sender. Message error - The receiver has received a message that has a correct length and correct checksum, but which contains an invalid message. The receiver sends an ACK message to the sender and writes an entry about the faulty message in its own log file or NT/2000 event log. The sender continues sending the next message in line (if any). The faulty message is not re-transmitted by the sender.
IVR/Voice System to VSI Messages

Show information about extension on Operator Workstation ID in Node Number because of Reason Text
Action Request Command Example STX 50 1234 1 99 001 Y CR LF Show information about MMMM STX 50 MMMM W XX PPP Y on Operator Workstation XX in CR LF node PPP because of W
Initiate Message Diversion Type for extension because of Reason from Start until End with Reason Text.
Action Request Initiate diversion for MMMM because of RRR from SSSS until EEEE Command STX 60 MMMM RRR T SSSS EEEE KK TEXT Y CR LF Example STX 60 1234 000 0 961231113000 961231123000 15 Gone To Lunch Y CR LF
Delete Message Diversion with recID for Extension

Action Request Command Example STX 61 1234 01 Y CR LF Delete diversion DD for MMMM STX 61 MMMM DD Y CR LF
View Message Diversion(s) for Extension

Action Request View diversion(s) for MMMM Command STX 62 MMMM Y CR LF Example STX 62 1234 Y CR LF
Initiate Message Text for Extension

Action Request Initiate message TEXT for MMMM Command Example STX 70 MMMM KK TEXT Y CR STX 70 1234 16 "Call home LF soon" Y CR LF
223
Delete Message Text for Extension

Action Request Command Example STX 71 1234 02 Y CR LF Delete message DD for MMMM STX 71 MMMM DD Y CR LF
View Message(s) for Extension

Action Request View message(s) for MMMM Command STX 72 MMMM Y CR LF Example STX 72 1234 Y CR LF
Download all Message Diversions and Messages from D.N.A.

Action Request Database Synchronization Message Command STX 90 Y CR LF Example This message is sent from VOICE System to VSI Service to download all messages and diversions from the D.N.A. Server to VOICE System. This is used to synchronize database information between both systems when VOICE System restarts.
View (synchronize) D.N.A. system time

Action Request Command Example This allows VSI Service to check the local date/time of the D.N.A. Server against the local date/time of the VOICE system. If local date/time deviates more than 1 minute and less than 10 minutes, then VSI Service prompts a warning message in the D.N.A. Server NT/2000 event log. If local date/time deviates more than 10 minutes, then VSI Service prompts an error message in the D.N.A. Server NT/2000 event log. Time Synchronization Message STX 91 YYMMDDHHMMSS Y CR LF
224
Technical Guide
IVR/Voice System from VSI Messages

Start of showing Message Diversion(s) for Extension that has Number of Message Diversions
Action Request Command Example See below Start of showing message STX 10 MMMM NN Y CR LF diversion(s) for MMMM that has NN diversions
Show Message Diversion with recID for Extension

Action Request Command Example See below Show diversion DD for MMMM STX 11 MMMM DD RRR T SSSS EEEE KK TEXT Y CR LF
End of showing Message Diversion(s) for Extension

Action Request Command Example (1234 has 2 diversions, lunch (0) 11:30-12:30 and vacation (7) June 25th until July 12th) STX 10 1234 02 Y CR LF STX 11 1234 01 000 0 961231113000 961231123000 15 Gone To Lunch Y CR LF STX 11 1234 02 007 0 960625000000 960712000000 25 Vacation To The Bahamas Y CR LF STX 12 1234 Y CR LF End of showing diversion(s) for STX 12 MMMM Y CR LF MMMM
Activate Message Diversion for Extension

Action Request Activate diversion for MMMM Command Example STX 13 MMMM DD PPP RRR STX 13 1234 01 001 000 0 T SSSS EEEE KK TEXT Y CR 961231113000 961231123000 LF 15 Gone To Lunch Y CR LF
Deactivate Message Diversion for Extension

Action Request Command Example STX 14 1234 Y CR LF Deactivate diversion for MMMM STX 14 MMMM Y CR LF
Start of showing Message(s) for Extension that has Number of Messages

Action Request Command Example See below Start of showing message(s) for STX 20 MMMM NN Y CR LF MMMM that has NN messages
225
Show Message with Number of characters with recID for Extension

Action Request Command Example Show message DD for MMMM STX 21 MMMM DD KK TEXT 1 See below Y CR LF or STX 21 MMMM DD KK TEXT 0 Y CR LF
End of showing Message(s) for Extension

Action Request Command Example (1234 has 2 messages, first with 130 characters, second only few) STX 20 1234 02 Y CR LF STX 21 1234 01 80 "This message contains information about this and that, especially that. Please" 1 Y CR LF STX 21 1234 01 50 " remember that this is a very small example only" 0 Y CR LF STX 21 1234 02 15 "Short message" 0 Y CR LF STX 22 1234 Y CR LF End of showing message(s) for STX 22 MMMM Y CR LF MMMM
Indicate that Extension has a Message Waiting Indication

Action Request Indicate message waiting indication for MMMM Command STX 23 MMMM Y CR LF Example STX 23 1234 Y CR LF
Erase the Message Waiting Indication for Extension

Action Request Erase message waiting indication for MMMM Command STX 24 MMMM Y CR LF Example STX 24 1234 Y CR LF
226
Technical Guide
Appendix
Busy PDM Data Table
Field Name Description date_x Date Field includes date and time, but only date portion is valid. time_s Start time of busy hour date/time Field includes date and time, but only time portion is valid. mid Measurement ID Foreign key referring to the primary key in the measinfo table. bhvalue Busy hour value A value which makes up the busy hour (see below). number (double) 8 number (long) 4 8 SQL Data Type date/time Bytes 8
227
The data fields used to calculate the bhvalue field vary according to the data object being measured. The table below lists the data fields used to calculate bhvalue for each traffic measurement data table.
Table c_bell code_r code_s confer datext dialdy extens keyc_r keyc_s modgrp opcorg opindi opmann pagext pagsar pbxgrp pcmlin roubwy rouddi roudio rouinc rouout tone_r trunks Includes Data For Common bell group MFC code receiver MFC code sender Conference Data extension Dial tone delay Voice extension Key code receiver Key code sender Modem group Call origin groupfor PBX operator Individual PBX operator PBX operator manned time Paging number Paging search area Internal group hunting group number PCM line Both way (incoming and outgoing) route Direct indialing route Direct indialing outgoing route Incoming route Outgoing route Tone receiver Individual trunk Fields Used to Calculate bhvalue calls traff traff traff traff calls traff traff traff traff ans corgc, opc, rec, opic not applicable calls traff traff traff traff traff traff traff traff traff traff
228
Technical Guide
PDM C_bell Data Table

Field Name Description date_x Date Date for information contained in the record. Field includes date and time, but only date portion is valid. time_s time_e Start time, end time Data for each record is recorded on the date indicated by date_x during the 15-minute interval defined by time_s and time_e. Each time field includes date and time, but only time portion is valid. Measurement ID Foreign key referring to the primary key in the measinfo table. calls Total call attempts Total number of successful calls, unanswered calls, and calls that encounter congestion (busy). cong Total congested calls Number of calls which encounter congestion (busy). tot_wtime Total wait time Total wait time (in seconds) for calls entering the queue. tot_wcount Total wait count Number of calls entering the queue. qtime Queue time Average wait time (in seconds) for calls entering the queue. Calculated as tot_wtime divided by tot_wcount. half_h Half hour grouping Indicates the half-hour time period during which this records data was collected. The first 1-2 digits indicate the hour during which data was collected (one digit for hours 0-9, two digits for hours 10-23), and the last digit indicates whether data was 229 number (integer) 2 number (long) 4 number (long) 4 number (long) 4 number (long) 4 number (long) 4 number (long) 4 date/time 8 SQL Data Type date/time Bytes 8
mid
collected during the first or second half hour (1 for data collected during minutes 0-29, 2 for data collected during minutes 30-59). For example, if time_s is 9:15 and time_e is 9:29, then data for the record was collected during the first half hour for 9:00 A.M. In this case, half_h would be 91. whole_h Whole hour grouping Indicates the hour time period during which this records data was collected (0-23). This is the same as the hour portion only of the time_s and time_e fields. valid_f Validity of record Indicates whether the record passed validity checks. The field will be either 1 (valid) or 0 (invalid). number (integer) 2 number (integer) 2
230
Technical Guide
PDM Code_r Data Table

Field Name Description date_x Date Date for information contained in the record. Field includes date and time, but only date portion is valid. time_s time_e Start time, end time Data for each record is recorded on the date indicated by date_x during the 15-minute interval defined by time_s and time_e. Each time field includes date and time, but only time portion is valid. Measurement ID Foreign key referring to the primary key in the measinfo table. traff Traffic intensity Intensity of call traffic (in erlangs). This can be between 0.00 (no traffic) and 9999.99 (maximum traffic). Calculated as follows: # of seizures # of scans # of seizures is defined as the number of times in a 15 minute period that a measurement object was scanned and found busy. calls Total call attempts Total number of successful calls, unanswered calls, and calls that encounter congestion (busy). ndv Number of individuals (devices) Total number of devices used for measurement. nblo Number of blocked individuals (devices) Number of devices blocked. congo Congestion overflowing Number of calls which encounter congestion when making attempts in some other LIM. congp Congestion-PCM line Number of calls which encounter number (long) 4 number (long) 4 number (long) 4 number (long) 4 number (long) 4 number (double) 8 number (long) date/time 8 8 SQL Data Type date/time Bytes 8
mid
231
congestion on a PCM line when making seizure attempts in some other LIM. oflo Overflow Number of calls which result in seizure attempts in some other LIM or the number of calls which result in switch-over to an alternative route. half_h Half hour grouping Indicates the half-hour time period during which this records data was collected. The first 1-2 digits indicate the hour during which data was collected (one digit for hours 09, two digits for hours 10-23), and the last digit indicates whether data was collected during the first or second half hour (1 for data collected during minutes 0-29, 2 for data collected during minutes 3059). For example, if time_s is 9:15 and time_e is 9:29, then data for the record was collected during the first half hour for 9:00 A.M. In this case, half_h would be 91. whole_h Whole hour grouping Indicates the hour time period during which this records data was collected (0-23). This is the same as the hour portion only of the time_s and time_e fields. valid_f Validity of record Indicates whether the record passed validity checks. The field will be either 1 (valid) or 0 (invalid). number (integer) 2 number (integer) 2 number (integer) 2 number (long) 4
232
Technical Guide
PDM Code_s Data Table

mid
233
234
Technical Guide
PDM Confer Data Table

Field Name Description date_x Date Date for information contained in the record. Field includes date and time, but only date portion is valid. time_s time_e Start time, end time Data for each record is recorded on the date indicated by date_x during the 15-minute interval defined by time_s and time_e. Each time field includes date and time, but only time portion is valid. Measurement ID Foreign key referring to the primary key in the measinfo table. traff Traffic intensity Intensity of call traffic (in erlangs). This can be between 0.00 (no traffic) and 9999.99 (maximum traffic). Calculated as follows: # of seizures # of scans # of seizures is defined as the number of times in a 15 minute period that a measurement object was scanned and found busy. calls Total call attempts Total number of successful calls, unanswered calls, and calls that encounter congestion (busy). ndv Number of individuals (devices) Total number of devices used for measurement. nblo Number of blocked individuals (devices) Number of devices blocked. cong Total congested calls Number of calls which encounter congestion (busy). half_h Half hour grouping Indicates the half-hour time period during which this records data was number (integer) 2 number (long) 4 number (long) 4 number (long) 4 number (long) 4 number (double) 8 number (long) date/time 8 8 SQL Data Type date/time Bytes 8
mid
235
collected. The first 1-2 digits indicate the hour during which data was collected (one digit for hours 09, two digits for hours 10-23), and the last digit indicates whether data was collected during the first or second half hour (1 for data collected during minutes 0-29, 2 for data collected during minutes 3059). For example, if time_s is 9:15 and time_e is 9:29, then data for the record was collected during the first half hour for 9:00 A.M. In this case, half_h would be 91. whole_h Whole hour grouping Indicates the hour time period during which this records data was collected (0-23). This is the same as the hour portion only of the time_s and time_e fields. valid_f Validity of record Indicates whether the record passed validity checks. The field will be either 1 (valid) or 0 (invalid). number (integer) 2 number (integer) 2
236
Technical Guide
PDM Datext Data Table

Field Name Description date_x Date Date for information contained in the record. Field includes date and time, but only date portion is valid. time_s time_e Start time, end time Data for each record is recorded on the date indicated by date_x during the 15-minute interval defined by time_s and time_e. Each time field includes date and time, but only time portion is valid. Measurement ID Foreign key referring to the primary key in the measinfo table. traff Traffic intensity Intensity of call traffic (in erlangs). This can be between 0.00 (no traffic) and 9999.99 (maximum traffic). Calculated as follows: # of seizures # of scans # of seizures is defined as the number of times in a 15 minute period that a measurement object was scanned and found busy. calls Total call attempts Total number of successful calls, unanswered calls, and calls that encounter congestion (busy). ndv Number of individuals (devices) Total number of devices used for measurement. nblo Number of blocked individuals (devices) Number of devices blocked. rejinc half_h Number of rejected incoming data calls Half hour grouping Indicates the half-hour time period during which this records data was collected. The first 1-2 digits number (long) 4 number (long) 4 number (long) 4 number (long) 4 number (double) 8 number (long) date/time 8 8 SQL Data Type date/time Bytes 8
mid
number (integer) 2
237
indicate the hour during which data was collected (one digit for hours 09, two digits for hours 10-23), and the last digit indicates whether data was collected during the first or second half hour (1 for data collected during minutes 0-29, 2 for data collected during minutes 3059). For example, if time_s is 9:15 and time_e is 9:29, then data for the record was collected during the first half hour for 9:00 A.M. In this case, half_h would be 91. whole_h Whole hour grouping Indicates the hour time period during which this records data was collected (0-23). This is the same as the hour portion only of the time_s and time_e fields. valid_f Validity of record Indicates whether the record passed validity checks. The field will be either 1 (valid) or 0 (invalid). number (integer) 2 number (integer) 2
238
Technical Guide
PDM Dialdy Data Table

Field Name Description date_x Date Date for information contained in the record. Field includes date and time, but only date portion is valid. time_s time_e Start time, end time Data for each record is recorded on the date indicated by date_x during the 15-minute interval defined by time_s and time_e. Each time field includes date and time, but only time portion is valid. Measurement ID Foreign key referring to the primary key in the measinfo table. calls Total call attempts Total number of successful calls, unanswered calls, and calls that encounter congestion (busy). call1 Call-one second delay Number of calls with a dial tone delay of more than one second. call3 Call-three second delay Number of calls with a dial tone delay of more than three seconds. call10 Call-ten second delay Number of calls with a dial tone delay of more than ten seconds. term Terminated call attempts Number of terminated call attempts without dial tone after one second. accu Accumulated delay time Accumulated time of delay (in seconds) for all calls with a dial tone delay of more than one second. half_h Half hour grouping Indicates the half-hour time period during which this records data was collected. The first 1-2 digits indicate the hour during which data was collected (one digit for hours 0number (integer) 2 number (long) 4 number (long) 4 number (long) 4 number (long) 4 number (long) 4 number (long) 4 number (long) date/time 8 8 SQL Data Type date/time Bytes 8
mid
239
9, two digits for hours 10-23), and the last digit indicates whether data was collected during the first or second half hour (1 for data collected during minutes 0-29, 2 for data collected during minutes 3059). For example, if time_s is 9:15 and time_e is 9:29, then data for the record was collected during the first half hour for 9:00 A.M. In this case, half_h would be 91. whole_h Whole hour grouping Indicates the hour time period during which this records data was collected (0-23). This is the same as the hour portion only of the time_s and time_e fields. valid_f Validity of record Indicates whether the record passed validity checks. The field will be either 1 (valid) or 0 (invalid). number (integer) 2 number (integer) 2
240
Technical Guide
PDM Cordless Extension Common Fixed Part Data Table

Field Name Description date_x Date Date for information contained in the record. Field includes date and time, but only date portion is valid. time_s time_e Start time, end time Data for each record is recorded on the date indicated by date_x during the 15-minute interval defined by time_s and time_e. Each time field includes date and time, but only time portion is valid. Measurement ID Foreign key referring to the primary key in the measinfo table. traff Traffic intensity (recommended grouping = AVG) Intensity of call traffic (in erlangs). This can be between 0.00 (no traffic) and 9999.99 (maximum traffic). Calculated as follows: # of seizures # of scans # of seizures is defined as the number of times in a 15 minute period that a measurement object was scanned and found busy. calls Total call attempts (recommended grouping = SUM) Total number of successful calls, unanswered calls, and calls that encounter congestion (busy). ndv Number of individuals (devices) (recommended grouping = AVG) Total number of devices used for measurement. nblo Number of blocked individuals (devices) (recommended grouping = AVG) Number of devices blocked. cong Total congested calls (recommended grouping = SUM) Number of calls which encounter number (long) 4 number (long) 4 number (long) 4 number (long) 4 number (double) 8 number (long) date/time 8 8 SQL Data Type date/time Bytes 8
mid
241
congestion (busy). half_h Half hour grouping Indicates the half-hour time period during which this records data was collected. The first 1-2 digits indicate the hour during which data was collected (one digit for hours 09, two digits for hours 10-23), and the last digit indicates whether data was collected during the first or second half hour (1 for data collected during minutes 0-29, 2 for data collected during minutes 3059). For example, if time_s is 9:15 and time_e is 9:29, then data for the record was collected during the first half hour for 9:00 A.M. In this case, half_h would be 91. whole_h Whole hour grouping Indicates the hour time period during which this records data was collected (0-23). This is the same as the hour portion only of the time_s and time_e fields. valid_f Validity of record Indicates whether the record passed validity checks. The field will be either 1 (valid) or 0 (invalid). number (integer) 2 number (integer) 2 number (integer) 2
242
Technical Guide
PDM Extens Data Table

Field Name Description date_x Date Date for information contained in the record. Field includes date and time, but only date portion is valid. time_s time_e Start time, end time Data for each record is recorded on the date indicated by date_x during the 15-minute interval defined by time_s and time_e. Each time field includes date and time, but only time portion is valid. Measurement ID Foreign key referring to the primary key in the measinfo table. traff Traffic intensity (recommended grouping = AVG) Intensity of call traffic (in erlangs). This can be between 0.00 (no traffic) and 9999.99 (maximum traffic). Calculated as follows: # of seizures # of scans # of seizures is defined as the number of times in a 15 minute period that a measurement object was scanned and found busy. calls Total call attempts (recommended grouping = SUM) Total number of successful calls, unanswered calls, and calls that encounter congestion (busy). ndv Number of individuals (devices) (recommended grouping = AVG) Total number of devices used for measurement. nblo Number of blocked individuals (devices) (recommended grouping = AVG) Number of devices blocked. rejinc Number of rejected incoming data calls number (long) 4 number (long) 4 number (long) 4 number (long) 4 number (double) 8 number (long) date/time 8 8 SQL Data Type date/time Bytes 8
mid
243
half_h
Half hour grouping Indicates the half-hour time period during which this records data was collected. The first 1-2 digits indicate the hour during which data was collected (one digit for hours 09, two digits for hours 10-23), and the last digit indicates whether data was collected during the first or second half hour (1 for data collected during minutes 0-29, 2 for data collected during minutes 3059). For example, if time_s is 9:15 and time_e is 9:29, then data for the record was collected during the first half hour for 9:00 A.M. In this case, half_h would be 91.
number (integer) 2
whole_h
Whole hour grouping Indicates the hour time period during which this records data was collected (0-23). This is the same as the hour portion only of the time_s and time_e fields.
number (integer) 2
valid_f
Validity of record Indicates whether the record passed validity checks. The field will be either 1 (valid) or 0 (invalid).
number (integer) 2
244
Technical Guide
PDM Keyc_r Data Table

mid
245
246
Technical Guide
PDM Keyc_s Data Table

mid
247
248
Technical Guide
PDM Measinfo Data Table

Field Name Description meno Active measurement number Number from 0-19 assigned by the MD110 when the measurement is active. An MD110 can perform 20 measurements at a time, and the meno field is used to track the current group of active measurements. As long as a measurement is active, the meno number assigned to that measurement cannot be assigned to any other active measurement. The PDM database retains the meno number assigned to each measurement. active_f Active status Indicates whether the measurement is still active in the MD110. The field will be either 1 (active) or 0 (inactive). object Measurement type Also the name of the corresponding data table in SQL. date_s1 First start date Start date for measurement. date_e1 First end date End date for measurement. If the measurement occurs over two date ranges with a gap between the first and second date range, then this field indicates the end of the first date range. date_s2 Second start date Start date for second part of measurement. If the measurement occurs over two date ranges with a gap between the first and second date range, then this field indicates the start of the second date range. date_e2 Second end date End date for second part of measurement. If the measurement occurs over two date ranges with a gap between the first and second date/time 8 date/time 8 date/time 8 date/time 8 Text 30 number (integer) 2 SQL Data Type Bytes number (integer) 2
249
date range, then this field indicates the end of the second date range. time_s time_e Start time, end time Data for each record is recorded on the date indicated by date_x during the 15-minute interval defined by time_s and time_e. Each time field includes date and time, but only time portion is valid. Date killed If the measurement was killed (stopped) manually, this field indicates the date that the measurement was killed. time_k Time killed If the measurement was killed (stopped) manually, this field indicates the time that the measurement was killed. date_up Date updated Most recent date that the database was updated for this measurement. Unlike date_last, this date is advanced as long as the measurement continues, even if there is no new data to report. date_last Last valid date Most recent date that valid data was recorded for the measurement. mid Measurement ID Unique number assigned by PDM to each record (primary key). parameter Item/device measured Identifies the specific item or device within the type defined by the object field that is being measured for this record. For example, if the object field is ROUDDI, the parameter field identifies the specific route measured. name memo This field is reserved for future use. -Memo text Free-form text field. text -255 text 255 number (long) 4 date/time 8 date/time 8 date/time 8 date/time date/time 8 8
date_k
250
Technical Guide
PDM Modgrp Data Table

Field Name Description date_x Date Date for information contained in the record. Field includes date and time, but only date portion is valid. time_s time_e Start time, end time Data for each record is recorded on the date indicated by date_x during the 15-minute interval defined by time_s and time_e. Each time field includes date and time, but only time portion is valid. Measurement ID Foreign key referring to the primary key in the measinfo table. traff Traffic intensity Intensity of call traffic (in erlangs). This can be between 0.00 (no traffic) and 9999.99 (maximum traffic). Calculated as follows: # of seizures # of scans # of seizures is defined as the number of times in a 15 minute period that a measurement object was scanned and found busy. calls Total call attempts Total number of successful calls, unanswered calls, and calls that encounter congestion (busy). ndv Number of individuals (devices) Total number of devices used for measurement. nblo Number of blocked individuals (devices) Number of devices blocked. cong Total congested calls Number of calls which encounter congestion (busy). half_h Half hour grouping Indicates the half-hour time period during which this records data was number (integer) 2 number (long) 4 number (long) 4 number (long) 4 number (long) 4 number (double) 8 number (long) 4 date/time 8 SQL Data Type date/time Bytes 8
mid
251
252
Technical Guide
PDM Opindi Data Table

Field Name Description date_x Date Date for information contained in the record. Field includes date and time, but only date portion is valid. time_s time_e Start time, end time Data for each record is recorded on the date indicated by date_x during the 15-minute interval defined by time_s and time_e. Each time field includes date and time, but only time portion is valid. Measurement ID Foreign key referring to the primary key in the measinfo table. corgc Call origin group calls (recommended grouping = SUM) Number of calls to a call origin group. hcorgc Call origin group handling time (recommended grouping = SUM) Total handling time (in seconds) for calls to a call origin group. opc Operator calls answered (recommended grouping = SUM) Number of calls answered by an operator. hopc Operator handling time (recommended grouping = SUM) Total handling time (in seconds). dlyopc Operator delay time (recommended number (long) grouping = SUM) Total delay time (in seconds). Delay time is the amount of time from when a call is detected (queued) to when the call is answered by an operator. rec Recalls (recommended grouping = number (long) SUM) Number of answered recalls. hrec Recall handling time (recommended grouping = SUM) number (long) 4 4 4 number (long) 4 number (long) 4 number (long) 4 number (long) 4 number (long) 4 date/time 8 SQL Data Type date/time Bytes 8
mid
253
Total handling time (in seconds) for recalls. dlyrec Recall delay time (recommended grouping = SUM) Total delay time (in seconds) for recalls. Delay time is the amount of time from when a call is detected (queued) to when the call is answered by the operator. opic Operator initiated calls (recommended grouping = SUM) Number of calls initiated by an operator. hopic Handling time for operator initiated number (long) calls (recommended grouping = SUM) Total handling time (in seconds) for calls initiated by an operator. abnd Abandoned calls (recommended grouping = SUM) Number of abandoned calls. wabnd Wait time for abandoned calls (recommended grouping = SUM) Total wait time (in seconds) for abandoned calls. This is the amount of time from when a call is detected to when it disappears without being attended to. abndrec Abandoned recalls (recommended number (long) grouping = SUM) Number of abandoned recalls. wabndrec Wait time for abandoned recalls (recommended grouping = SUM) Total wait time (in seconds) for abandoned recalls. respt Response time (recommended grouping = SUM) Total response time (in seconds) for all calls. half_h Half hour grouping Indicates the half-hour time period during which this records data was collected. The first 1-2 digits indicate the hour during which data was collected (one digit for hours 09, two digits for hours 10-23), and number (integer) 4 number (long) 4 number (long) 4 4 number (long) 4 number (long) 4 4 number (long) 4 number (long) 4
254
Technical Guide
the last digit indicates whether data was collected during the first or second half hour (1 for data collected during minutes 0-29, 2 for data collected during minutes 3059). For example, if time_s is 9:15 and time_e is 9:29, then data for the record was collected during the first half hour for 9 A.M. In this case, half_h would be 91. whole_h Whole hour grouping Indicates the hour time period during which this records data was collected (0-23). This is the same as the hour portion only of the time_s and time_e fields. valid_f Validity of record Indicates whether the record passed validity checks. The field will be either 1 (valid) or 0 (invalid). number (integer) 2 number (integer) 2
255
PDM Opcorg Data Table

Field Name Description date_ Date Date for information contained in the record. Field includes date and time, but only date portion is valid. time_s time_e Start time, end time Data for each record is recorded on the date indicated by date_x during the 15-minute interval defined by time_s and time_e. Each time field includes date and time, but only time portion is valid. Measurement ID Foreign key referring to the primary key in the measinfo table. ans Answered calls (recommended grouping = SUM) Number of answered calls (primary and secondary). anssec Answered secondary calls (recommended grouping = SUM) Number of calls answered by a secondary operator. dlytot Total delay time (recommended grouping = SUM) Total delay time (in seconds). Delay time is the amount of time from when a call is detected (queued) to when the call is answered by an operator. hndltot Total handling time (recommended number (long) grouping = SUM) Total handling time (in seconds). Handling time is the amount of time from when a call is answered to when the handling procedure is completed. abnd Abandoned calls (recommended grouping = SUM) Number of abandoned calls. waittot Total wait time (recommended grouping = SUM) Total wait (queue) time (in seconds) number (long) 4 number (long) 4 4 number (long) 4 number (long) 4 number (long) 4 number (long) date/time 8 8 SQL Data Type date/time Bytes 8
mid
256
Technical Guide
for calls not attended to. waitexceed Calls exceeding standard wait time number (long) (recommended grouping = SUM) Number of calls whose wait (queue) time exceeds a predefined value. half_h Half hour grouping Indicates the half-hour time period during which this records data was collected. The first 1-2 digits indicate the hour during which data was collected (one digit for hours 09, two digits for hours 10-23), and the last digit indicates whether data was collected during the first or second half hour (1 for data collected during minutes 0-29, 2 for data collected during minutes 3059). For example, if time_s is 9:15 and time_e is 9:29, then data for the record was collected during the first half hour for 9:00 A.M. In this case, half_h would be 91. whole_h Whole hour grouping Indicates the hour time period during which this records data was collected (0-23). This is the same as the hour portion only of the time_s and time_e fields. valid_f Validity of record Indicates whether the record passed validity checks. The field will be either 1 (valid) or 0 (invalid). number (integer) 2 number (integer) 2 number (integer) 2 4
257
PDM Opmann Data Table

Field Name Description date_x Date Date for information contained in the record. Field includes date and time, but only date portion is valid. time_s time_e Start time, end time Data for each record is recorded on the date indicated by date_x during the 15-minute interval defined by time_s and time_e. Each time field includes date and time, but only time portion is valid. Measurement ID Foreign key referring to the primary key in the measinfo table. pres Present operators (recommended grouping = AVG) Average number of operators marked present. idle Idle operators (recommended grouping = AVG) Average number of idle (free) operators. Idle means an operator is present but not busy. presi Present state for an operator (recommended grouping = AVG) Average value of the present state for an individual operator. This will be from 0.00 (always absent) to 1.00 (always present). idlei Idle state for an operator (recommended grouping = AVG) Average value of idle (free) state for an individual operator. Idle means an operator is present but not busy. prespri Present state for primary operators number (double) 8 (recommended grouping = AVG) Average number of primary operators marked present. pressec Present state for secondary operators(recommended grouping = AVG) Average number of secondary number (double) 8 number (double) 8 number (double) 8 number (double) 8 number (long) 4 number (long) date/time 8 8 SQL Data Type date/time Bytes 8
mid
258
Technical Guide
operators marked present. idlepri Idle state for primary operators (recommended grouping = AVG) Average number of primary operators marked idle (free). idlesec Idle state for secondary operators (recommended grouping = AVG) Average number of secondary operators marked idle (free). numop numop2 Number of operators (recommended grouping = AVG) These fields indicate the number of operators that data is collected for. The entries for these fields will change depending upon the range of operators included: If data is collected for a single operator, numop is 1 and numop2 is not used. If data is collected for all operators, numop indicates the number of operators and numop2 is not used. If data is collected for all operators in a call origin group, numop indicates the total number of primary operators and numop2 indicates the total number of secondary operators in this call origin group. half_h Half hour grouping Indicates the half-hour time period during which this records data was collected. The first 1-2 digits indicate the hour during which data was collected (one digit for hours 09, two digits for hours 10-23), and the last digit indicates whether data was collected during the first or second half hour (1 for data collected during minutes 0-29, 2 for data collected during minutes 3059). For example, if time_s is 9:15 and time_e is 9:29, then data for the record was collected during the first half hour for 9:00 A.M. In this case, half_h would be 91. whole_h Whole hour grouping Indicates the hour time period 259 number (integer) 2 number (integer) 2 number (integer) 2 number (double) 8 number (double) 8
during which this records data was collected (0-23). This is the same as the hour portion only of the time_s and time_e fields. valid_f Validity of record Indicates whether the record passed validity checks. The field will be either 1 (valid) or 0 (invalid). number (integer) 2
PDM Pagext Data Table

Field Name Description date_x Date Date for information contained in the record. Field includes date and time, but only date portion is valid. time_s time_e Start time, end time Data for each record is recorded on the date indicated by date_x during the 15-minute interval defined by time_s and time_e. Each time field includes date and time, but only time portion is valid. Measurement ID Foreign key referring to the primary key in the measinfo table. calls Total call attempts Total number of successful calls, unanswered calls, and calls that encounter congestion (busy). half_h Half hour grouping Indicates the half-hour time period during which this records data was collected. The first 1-2 digits indicate the hour during which data was collected (one digit for hours 09, two digits for hours 10-23), and the last digit indicates whether data was collected during the first or second half hour (1 for data collected during minutes 0-29, 2 for data collected during minutes 3059). For example, if time_s is 9:15 and time_e is 9:29, then data for the record was collected during the first half hour for 9:00 A.M. In this case, half_h would be 91. number (integer) 2 number (long) 4 number (long) date/time 8 8 SQL Data Type date/time Bytes 8
mid
260
Technical Guide
whole_h
number (integer) 2
valid_f
number (integer) 2
261
PDM Pagsar Data Table

Field Name Description date_x Date Date for information contained in the record. Field includes date and time, but only date portion is valid. time_s time_e Start time, end time Data for each record is recorded on the date indicated by date_x during the 15-minute interval defined by time_s and time_e. Each time field includes date and time, but only time portion is valid. Measurement ID Foreign key referring to the primary key in the measinfo table. traff Traffic intensity Intensity of call traffic (in erlangs). This can be between 0.00 (no traffic) and 9999.99 (maximum traffic). Calculated as follows: # of seizures # of scans # of seizures is defined as the number of times in a 15 minute period that a measurement object was scanned and found busy. calls Total call attempts Total number of successful calls, unanswered calls, and calls that encounter congestion (busy). cong Total congested calls Number of calls which encounter congestion (busy). tot_stime Total search time Total search time (in seconds) for all calls. Search time is the amount of time from when a call is detected to when the call is answered. tot_scount Total search count Number of search calls. stime Average search time tot_stime divided by tot_scount. number (long) 4 number (long) 4 number (long) 4 number (long) 4 number (long) 4 number (double) 8 number (long) date/time 8 8 SQL Data Type date/time Bytes 8
mid
262
Technical Guide
tot_wtime
Total wait time Total wait time (in seconds) for calls entering the queue.
number (long)
tot_wcount
Total wait count Number of calls entering the queue.
number (long)
qtime
Queue time Average wait time (in seconds) for calls entering the queue. Calculated as tot_wtime divided by tot_wcount.
number (long)
half_h
number (integer) 2
whole_h
number (integer) 2
valid_f
number (integer) 2
263
PDM Pbxgrp Data Table

Field Name Description date_x Date Date for information contained in the record. Field includes date and time, but only date portion is valid. time_s time_e Start time, end time Data for each record is recorded on the date indicated by date_x during the 15-minute interval defined by time_s and time_e. Each time field includes date and time, but only time portion is valid. Measurement ID Foreign key referring to the primary key in the measinfo table. traff Traffic intensity (recommended grouping = AVG) Intensity of call traffic (in erlangs). This can be between 0.00 (no traffic) and 9999.99 (maximum traffic). Calculated as follows: # of seizures # of scans # of seizures is defined as the number of times in a 15 minute period that a measurement object was scanned and found busy. calls Total call attempts (recommended grouping = SUM) Total number of successful calls, unanswered calls, and calls that encounter congestion (busy). cong Total congested calls (recommended grouping = SUM) Number of calls which encounter congestion (busy). qcal Queued calls (recommended grouping = SUM) Number of calls leaving the queue due to answer or abandonment. qtime Queue time (recommended grouping = SUM) Average wait time (in seconds) for number (long) 4 number (long) 4 number (long) 4 number (long) 4 number (double) 8 number (long) date/time 8 8 SQL Data Type date/time Bytes 8
mid
264
Technical Guide
queued calls. qlen Average queue length (recommended grouping = SUM) Average number of queued calls. qabn Abandoned calls in queue (recommended grouping = SUM) Number of queued calls that were abandoned. qmaxt Maximum queue time (recommended grouping = AVG) Maximum time (in seconds) that any call spent in the queue. premb Present group members (recommended grouping = AVG) Number of call origin group members marked present. absmb Absent or blocked group members (recommended grouping = AVG) Number of call origin group members marked absent or blocked. mean_qtime Mean queue time Calculated as follows: qtime + qcal qcal half_h Half hour grouping Indicates the half-hour time period during which this records data was collected. The first 1-2 digits indicate the hour during which data was collected (one digit for hours 09, two digits for hours 10-23), and the last digit indicates whether data was collected during the first or second half hour (1 for data collected during minutes 0-29, 2 for data collected during minutes 3059). For example, if time_s is 9:15 and time_e is 9:29, then data for the record was collected during the first half hour for 9:00 A.M. In this case, half_h would be 91. whole_h Whole hour grouping Indicates the hour time period during which this records data was number (integer) 2 number (integer) 2 number (long) 4 number (long) 4 number (long) 4 number (long) 4
265
collected (0-23). This is the same as the hour portion only of the time_s and time_e fields. valid_f Validity of record Indicates whether the record passed validity checks. The field will be either 1 (valid) or 0 (invalid). number (integer) 2
PDM Pcmlin Data Table

Field Name Description date_x Date Date for information contained in the record. Field includes date and time, but only date portion is valid. time_s time_e Start time, end time Data for each record is recorded on the date indicated by date_x during the 15-minute interval defined by time_s and time_e. Each time field includes date and time, but only time portion is valid. Measurement ID Foreign key referring to the primary key in the measinfo table. traff Traffic intensity (recommended grouping = AVG) Intensity of call traffic (in erlangs). This can be between 0.00 (no traffic) and 9999.99 (maximum traffic). Calculated as follows: # of seizures # of scans # of seizures is defined as the number of times in a 15 minute period that a measurement object was scanned and found busy. calls Total call attempts (recommended grouping = SUM) Total number of successful calls, unanswered calls, and calls that encounter congestion (busy). ndv Number of individuals (devices) (recommended grouping = AVG) Total number of devices used for measurement. number (long) 4 number (long) 4 number (double) 8 number (long) date/time 8 8 SQL Data Type date/time Bytes 8
mid
266
Technical Guide
nblo
Number of blocked individuals (devices) (recommended grouping = AVG) Number of devices blocked.
number (long)
cong
Total congested calls (recommended grouping = SUM) Number of calls which encounter congestion (busy).
number (long)
half_h
number (integer) 2
whole_h
number (integer) 2
valid_f
number (integer) 2
267
PDM Roubwy Data Table

Field Name Description date_x Date Date for information contained in the record. Field includes date and time, but only date portion is valid. time_s time_e Start time, end time Data for each record is recorded on the date indicated by date_x during the 15-minute interval defined by time_s and time_e. Each time field includes date and time, but only time portion is valid. Measurement ID Foreign key referring to the primary key in the measinfo table. traff Traffic intensity (recommended grouping = AVG) Intensity of call traffic (in erlangs). This can be between 0.00 (no traffic) and 9999.99 (maximum traffic). Calculated as follows: # of seizures # of scans # of seizures is defined as the number of times in a 15 minute period that a measurement object was scanned and found busy. outg_calls Outgoing calls (recommended grouping = SUM) Number of outgoing calls. inc_calls Incoming calls (recommended grouping = SUM) Number of incoming calls. ndv Number of individuals (devices) (recommended grouping = AVG) Total number of devices used for measurement. nblo Number of blocked individuals (devices) (recommended grouping = AVG) Number of devices blocked. oflo Overflow (recommended grouping SUM) number (long) 4 number (long) 4 number (long) 4 number (long) 4 number (long) 4 number (double) 8 number (long) date/time 8 8 SQL Data Type date/time Bytes 8
mid
268
Technical Guide
= SUM) Number of calls which result in seizure attempts in some other LIM or the number of calls which result in switch-over to an alternative route. cong Total congested calls (recommended grouping = SUM) Number of calls which encounter congestion (busy). half_h Half hour grouping Indicates the half-hour time period during which this records data was collected. The first 1-2 digits indicate the hour during which data was collected (one digit for hours 09, two digits for hours 10-23), and the last digit indicates whether data was collected during the first or second half hour (1 for data collected during minutes 0-29, 2 for data collected during minutes 3059). For example, if time_s is 9:15 and time_e is 9:29, then data for the record was collected during the first half hour for 9:00 A.M. In this case, half_h would be 91. whole_h Whole hour grouping Indicates the hour time period during which this records data was collected (0-23). This is the same as the hour portion only of the time_s and time_e fields. valid_f Validity of record Indicates whether the record passed validity checks. The field will be either 1 (valid) or 0 (invalid). number (integer) 2 number (integer) 2 number (integer) 2 number (long) 4
269
PDM Rouddi Data Table

Field Name Description date_x Date Date for information contained in the record. Field includes date and time, but only date portion is valid. time_s time_e Start time, end time Data for each record is recorded on the date indicated by date_x during the 15-minute interval defined by time_s and time_e. Each time field includes date and time, but only time portion is valid. Measurement ID Foreign key referring to the primary key in the measinfo table. traff Traffic intensity (recommended grouping = AVG) Intensity of call traffic (in erlangs). This can be between 0.00 (no traffic) and 9999.99 (maximum traffic). Calculated as follows: # of seizures # of scans # of seizures is defined as the number of times in a 15 minute period that a measurement object was scanned and found busy. calls Total call attempts (recommended grouping = SUM) Total number of successful calls, unanswered calls, and calls that encounter congestion (busy). ndv Number of individuals (devices) (recommended grouping = AVG) Total number of devices used for measurement. nblo Number of blocked individuals (devices) (recommended grouping = AVG) Number of devices blocked. half_h Half hour grouping Indicates the half-hour time period during which this records data was number (integer) 2 number (long) 4 number (long) 4 number (long) 4 number (double) 8 number (long) date/time 8 8 SQL Data Type date/time Bytes 8
mid
270
Technical Guide
271
PDM Roudio Data Table

Field Name Description date_x Date Date for information contained in the record. Field includes date and time, but only date portion is valid. time_s time_e Start time, end time Data for each record is recorded on the date indicated by date_x during the 15-minute interval defined by time_s and time_e. Each time field includes date and time, but only time portion is valid. Measurement ID Foreign key referring to the primary key in the measinfo table. traff Traffic intensity (recommended grouping = AVG) Intensity of call traffic (in erlangs). This can be between 0.00 (no traffic) and 9999.99 (maximum traffic). Calculated as follows: # of seizures # of scans # of seizures is defined as the number of times in a 15 minute period that a measurement object was scanned and found busy. outg_calls Outgoing calls (recommended grouping = SUM) Number of outgoing calls. inc_calls Incoming calls (recommended grouping = SUM) Number of incoming calls. ndv Number of individuals (devices) (recommended grouping = AVG) Total number of devices used for measurement. nblo Number of blocked individuals (devices) (recommended grouping = AVG) Number of devices blocked. oflo Overflow (recommended grouping SUM) number (long) 4 number (long) 4 number (long) 4 number (long) 4 number (long) 4 number (double) 8 number (long) date/time 8 8 SQL Data Type date/time Bytes 8
mid
272
Technical Guide
= SUM) Number of calls which result in seizure attempts in some other LIM or the number of calls which result in switch-over to an alternative route. cong Total congested calls (recommended grouping = SUM) Number of calls which encounter congestion (busy). half_h Half hour grouping Indicates the half-hour time period during which this records data was collected. The first 1-2 digits indicate the hour during which data was collected (one digit for hours 09, two digits for hours 10-23), and the last digit indicates whether data was collected during the first or second half hour (1 for data collected during minutes 0-29, 2 for data collected during minutes 3059). For example, if time_s is 9:15 and time_e is 9:29, then data for the record was collected during the first half hour for 9:00 A.M. In this case, half_h would be 91. whole_h Whole hour grouping Indicates the hour time period during which this records data was collected (0-23). This is the same as the hour portion only of the time_s and time_e fields. valid_f Validity of record Indicates whether the record passed validity checks. The field will be either 1 (valid) or 0 (invalid). number (integer) 2 number (integer) 2 number (integer) 2 number (long) 4
273
PDM Rouinc Data Table

Field Name Description date_x Date Date for information contained in the record. Field includes date and time, but only date portion is valid. time_s time_e Start time, end time Data for each record is recorded on the date indicated by date_x during the 15-minute interval defined by time_s and time_e. Each time field includes date and time, but only time portion is valid. Measurement ID Foreign key referring to the primary key in the measinfo table. traff Traffic intensity (recommended grouping = AVG) Intensity of call traffic (in erlangs). This can be between 0.00 (no traffic) and 9999.99 (maximum traffic). Calculated as follows: # of seizures # of scans # of seizures is defined as the number of times in a 15 minute period that a measurement object was scanned and found busy. calls Total call attempts (recommended grouping = SUM) Total number of successful calls, unanswered calls, and calls that encounter congestion (busy). ndv Number of individuals (devices) (recommended grouping = AVG) Total number of devices used for measurement. nblo Number of blocked individuals (devices) (recommended grouping = AVG) Number of devices blocked. half_h Half hour grouping Indicates the half-hour time period during which this records data was number (integer) 2 number (long) 4 number (long) 4 number (long) 4 number (double) 8 number (long) date/time 8 8 SQL Data Type Bytes date/time 8
mid
274
Technical Guide
275
PDM Rouout Data Table

Field Name Description date_x Date Date for information contained in the record. Field includes date and time, but only date portion is valid. time_s time_e Start time, end time Data for each record is recorded on the date indicated by date_x during the 15-minute interval defined by time_s and time_e. Each time field includes date and time, but only time portion is valid. Measurement ID Foreign key referring to the primary key in the measinfo table. traff Traffic intensity (recommended grouping = AVG) Intensity of call traffic (in erlangs). This can be between 0.00 (no traffic) and 9999.99 (maximum traffic). Calculated as follows: # of seizures # of scans # of seizures is defined as the number of times in a 15 minute period that a measurement object was scanned and found busy. calls Total call attempts (recommended grouping = SUM) Total number of successful calls, unanswered calls, and calls that encounter congestion (busy). ndv Number of individuals (devices) (recommended grouping = AVG) Total number of devices used for measurement. nblo Number of blocked individuals (devices) (recommended grouping = AVG) Number of devices blocked. oflo Overflow (recommended grouping = SUM) Number of calls which result in number (long) 4 number (long) 4 number (long) 4 number (long) 4 number (double) 8 number (long) date/time 8 8 SQL Data Type date/time Bytes 8
mid
276
Technical Guide
seizure attempts in some other LIM or the number of calls which result in switch-over to an alternative route. cong Total congested calls (recommended grouping = SUM) Number of calls which encounter congestion (busy). half_h Half hour grouping Indicates the half-hour time period during which this records data was collected. The first 1-2 digits indicate the hour during which data was collected (one digit for hours 09, two digits for hours 10-23), and the last digit indicates whether data was collected during the first or second half hour (1 for data collected during minutes 0-29, 2 for data collected during minutes 3059). For example, if time_s is 9:15 and time_e is 9:29, then data for the record was collected during the first half hour for 9:00 A.M. In this case, half_h would be 91. whole_h Whole hour grouping Indicates the hour time period during which this records data was collected (0-23). This is the same as the hour portion only of the time_s and time_e fields. valid_f Validity of record Indicates whether the record passed validity checks. The field will be either 1 (valid) or 0 (invalid). number (integer) 2 number (integer) 2 number (integer) 2 number (long) 4
277
PDM Tone_r Data Table

mid
278
Technical Guide
279
PDM Trunks Data Table

Field Name Description date_x Date Date for information contained in the record. Field includes date and time, but only date portion is valid. time_s time_e Start time, end time Data for each record is recorded on the date indicated by date_x during the 15-minute interval defined by time_s and time_e. Each time field includes date and time, but only time portion is valid. Measurement ID Foreign key referring to the primary key in the measinfo table. traff Traffic intensity Intensity of call traffic (in erlangs). This can be between 0.00 (no traffic) and 9999.99 (maximum traffic). Calculated as follows: # of seizures # of scans # of seizures is defined as the number of times in a 15 minute period that a measurement object was scanned and found busy. calls Total call attempts Total number of successful calls, unanswered calls, and calls that encounter congestion (busy). ndv Number of individuals (devices) Total number of devices used for measurement. nblo Number of blocked individuals (devices) Number of devices blocked. rejinc half_h Number of rejected incoming data calls Half hour grouping Indicates the half-hour time period during which this records data was collected. The first 1-2 digits number (long) 4 number (long) 4 number (long) 4 number (long) 4 number (double) 8 number (long) date/time 8 8 SQL Data Type date/time Bytes 8
mid
number (integer) 2
280
Technical Guide
indicate the hour during which data was collected (one digit for hours 09, two digits for hours 10-23), and the last digit indicates whether data was collected during the first or second half hour (1 for data collected during minutes 0-29, 2 for data collected during minutes 3059). For example, if time_s is 9:15 and time_e is 9:29, then data for the record was collected during the first half hour for 9:00 A.M. In this case, half_h would be 91. whole_h Whole hour grouping Indicates the hour time period during which this records data was collected (0-23). This is the same as the hour portion only of the time_s and time_e fields. valid_f Validity of record Indicates whether the record passed validity checks. The field will be either 1 (valid) or 0 (invalid). number (integer) 2 number (integer) 2
281
PDM Cordless Extensions Mobility Table

Field Name Description date_x Date Date for information contained in the record. Field includes date and time, but only date portion is valid. time_s time_e Start time, end time Data for each record is recorded on the date indicated by date_x during the 15-minute interval defined by time_s and time_e. Each time field includes date and time, but only time portion is valid. Measurement ID Foreign key referring to the primary key in the measinfo table. locreg_ok locreg_f detach_ok detach_f extho_ok extho_f falho_ok falho_f conho_ok conho_f half_h Half hour grouping Indicates the half-hour time period during which this records data was collected. The first 1-2 digits indicate the hour during which data was collected (one digit for hours 09, two digits for hours 10-23), and the last digit indicates whether data was collected during the first or second half hour (1 for data collected during minutes 0-29, 2 for data collected during minutes 3059). For example, if time_s is 9:15 and time_e is 9:29, then data for the record was collected during the first half hour for 9:00 A.M. In this case, half_h would be 91. int int int int int int int int int int number (integer) 2 number (long) date/time 8 8 SQL Data Type date/time Bytes 8
mid
282
Technical Guide
whole_h
number (integer) 2
valid_f
number (integer) 2
283
PDM Cordless Extensions Fixed Part Table

Field Name Description date_x Date Date for information contained in the record. Field includes date and time, but only date portion is valid. time_s time_e Start time, end time Data for each record is recorded on the date indicated by date_x during the 15-minute interval defined by time_s and time_e. Each time field includes date and time, but only time portion is valid. Measurement ID Foreign key referring to the primary key in the measinfo table. traff Traffic intensity Intensity of call traffic (in erlangs). This can be between 0.00 (no traffic) and 9999.99 (maximum traffic). Calculated as follows: # of seizures # of scans # of seizures is defined as the number of times in a 15 minute period that a measurement object was scanned and found busy. calls Total call attempts Total number of successful calls, unanswered calls, and calls that encounter congestion (busy). ndv Number of individuals (devices) Total number of devices used for measurement. nblo Number of blocked individuals (devices) Number of devices blocked. cong Total congested calls Number of calls which encounter congestion (busy). half_h Half hour grouping Indicates the half-hour time period during which this records data was number (integer) 2 number (long) 4 number (long) 4 number (long) 4 number (long) 4 number (double) 8 number (long) date/time 8 8 SQL Data Type date/time Bytes 8
mid
284
Technical Guide
285
PDM IP Extensions Table

Field Name Description date_x Date Date for information contained in the record. Field includes date and time, but only date portion is valid. time_s time_e Start time, end time Data for each record is recorded on the date indicated by date_x during the 15-minute interval defined by time_s and time_e. Each time field includes date and time, but only time portion is valid. Measurement ID Foreign key referring to the primary key in the measinfo table. traff Traffic intensity Intensity of call traffic (in erlangs). This can be between 0.00 (no traffic) and 9999.99 (maximum traffic). Calculated as follows: # of seizures # of scans # of seizures is defined as the number of times in a 15 minute period that a measurement object was scanned and found busy. calls Total call attempts Total number of successful calls, unanswered calls, and calls that encounter congestion (busy). nbrd nblo Number of blocked individuals (devices) Number of devices blocked. cong Total congested calls Number of calls which encounter congestion (busy). jitter pac_lost pac_drop half_h Half hour grouping int int int number (integer) 2 number (long) 4 int number (long) 4 number (long) 4 number (double) 8 number (long) date/time 8 8 SQL Data Type date/time Bytes 8
mid
286
Technical Guide
Indicates the half-hour time period during which this records data was collected. The first 1-2 digits indicate the hour during which data was collected (one digit for hours 09, two digits for hours 10-23), and the last digit indicates whether data was collected during the first or second half hour (1 for data collected during minutes 0-29, 2 for data collected during minutes 3059). For example, if time_s is 9:15 and time_e is 9:29, then data for the record was collected during the first half hour for 9:00 A.M. In this case, half_h would be 91. whole_h Whole hour grouping Indicates the hour time period during which this records data was collected (0-23). This is the same as the hour portion only of the time_s and time_e fields. valid_f Validity of record Indicates whether the record passed validity checks. The field will be either 1 (valid) or 0 (invalid). number (integer) 2 number (integer) 2
Remote Data Server

Remote Data Server (RDS) is a D.N.A. service module that maintains continuous network database synchronization between MD110 PBX nodes, the D.N.A. SQL server, and all D.N.A. local databases.
Security Data Server

The Security Data Server (SDS) provides high-level security in the form of licensing enforcement. SDS references encrypted licensing data to enforce authorized license limits. SDS also accesses data based on Logging Facilities Server requests.
System Clock Synchronization

D.N.A. client and server installations maintain ongoing clock synchronization. D.N.A. Server provides synchronization via client polling, server-initiated client updates, and clock drift monitoring and correction with the server's clock as reference.
To Generate Reports Using Access

1 2
Click the Attach Table tool on the Access toolbar to attach the SQL Database. After selecting SQL Database, Access prompts you for a data source. Select the data source pointing to the SQL server with MD110 data.
287
Login to the SQL server by entering thirdpty as the user ID and password. Click on the Options buttons to select a database. 4 Select a table from the list displayed and attach all tables that you want to use for your reports. 5 Click on the Query tab, and then on the New button to define a New Query. In order to correctly set the table relations, you should refer to the technical documentation for the specific D.N.A. application. 6 After setting the table relationships, run the query and check the results to see if the data is coming back correctly. Click on the ! tool on the toolbar to run the query. 7 Once you are satisfied with your query, click on the Report tab and then click on the New button. Access prompts you with the Database dialog box. Select the query that you defined in the previous steps, and then click on the Report Wizard button. 8 The report wizard guides you through the steps of defining a report. 9 Select the fields and the sort order that you want to include in your report, and define the report style and page orientation. 10 The Report Wizard asks you for a report title. After you have entered the title of the report, you can choose to run the report or go to report design view to further customize the report layout.
To Log Off
If the application is your only logged D.N.A. application, you will be logged off both that application and the D.N.A. Server. However, if you are logged on to other D.N.A. applications, you will only be logged off the current application. Your access to the other applications will not be affected.
1 2
Select Exit from the Application menu. Click OK on the confirmation dialog box. Your session will be terminated.
To Logon
1 2
3 4
When you select a D.N.A. support application from the Administrative Tools taskbar, the support application will start, and the User Log On dialog box is displayed. Type your User Name and Password into the corresponding edit boxes. As you type the password, a string of asterisk characters (********) appears in the Password edit box, one asterisk for each character you type. Both the User Name and Password fields are case-sensitive, and you are allowed only a limited number of attempts. Select a local or remote server from the DNA Server drop-down list. The initial security authorization check and all subsequent validation actions are directed toward the server you select. Click the OK button. If your user name and password are valid, you will be logged on to the application with the access authorizations permitted in your user profile.
PPM Error Messages

Use the following table to investigate problems identified in PPM error messages. Error Message
Any error when generating reports using the Scheduler.
Possible Cause
Cause is indicated in the error message displayed with the Windows NT/2000 Event Viewer.
Corrective Action
Install and configure the appropriate printer driver.
Any ADO/ODBC data access
Cause of the error described in Verify ADO/ODBC data source
288
Technical Guide
error.
the error message.
is set up correctly. Refer to the SQL server troubleshooting booklet for further assistance.
Invalid mid: nn
Check the site database for the Scheduled report not printed because measurement ID was scheduled report. not found in the data table. No traffic recorded. Not an error. No action needed.
No busy hour data found. Printer device unavailable.
Printer is turned off, off-line, not Verify printer is powered on, installed, or cannot be found on on-line, and connected the network. properly. Check network connection if printing to a network printer. Scheduler was turned off successfully. Scheduler was started successfully. Ran out of Windows timer resource. Not an error. No action needed. Not an error. No action needed. Quit one or more Windows applications. Make sure the DLL exists and that the names of the directories in it's path have not changed since installation.
Scheduler is OFF. Scheduler is ON. Unable to start scheduler.
Application error: ActiveX PPMDBOBJ.DLL is not component can't create object. properly registered.
An error occurred while getting The database table that stores Report the problem to your system administrator. the Custom Reports info from custom reports on the server cannot be accessed. the Server. An error occurred while getting the Custom Report definition from the Server. The report definition may be deleted The .xxx method is not supported. Unknown error: nnnn A custom report definition selected by the user or defined as part of a Scheduled Report no longer exists on the Server. Write permissions to the registry are not allowed for the current logged user. Unanticipated run-time error occurred while formatting reports for printing. Re-create the desired custom report definition, or select another default or custom report. Report the problem to your system administrator. Record the error number and report it to the system administrator.
289
Index
A
Access................................................................................................................................ 287, 288 Access Agent ............................................................................................................................. 187 Accounts ...................................................................................................................................... 63 Administrative Tools................................................................................................... 113, 164, 168 Application Data......................................................................................... 141, 142, 147, 160, 287 Applications.................................................................................................................................. 22 Archival Backup ......................................................................................................................... 119 Automatic Extraction .................................................................................................................. 120
B
Backup ....................................................................................................................................... 123 Basic Requirements..................................................................................................................... 50 Busy Data Table ........................................................................................................................ 227
C
c_bell Table................................................................................................................................ 229 CCA.............................................................................................................................................. 35 CCM ............................................................................................................................................. 34 CCM Server ............................................................................................................................... 176 Change............................................................................................................................... 115, 116 Change Log ................................................................................................................................ 38 Checklists..................................................................................................................................... 62 CleanDB..................................................................................................................................... 117 Client .......................................................................................................................... 57, 58, 62, 77 Client Installation.......................................................................................................................... 88 Client Requirements .................................................................................................................... 55 ClockSync................................................................................................................................. 186 Code_r Table ............................................................................................................................. 231 Code_s....................................................................................................................................... 233 Commands ....................................................................................................... 170, 171, 172, 173 Communication .................................................................................................................. 204, 205 Communications ........................................................................................................................ 206 Confer ........................................................................................................................................ 235 Configuration ............................................................................. 46, 47, 48, 49, 96, 192, 193, 195 Configuration Management.......................................................................................................... 59 Connection ................................................................................................................. 57, 58, 59, 60 Cordless Extensions .......................................................................................................... 282, 284 Customer Groups .................................................................................................................... 196 Customers.......................................................................................................................... 192, 193
D
D.N.A............................................................................................ 15, 16, 17, 77, 78, 183, 185, 186 D.N.A. CAAPI .............................................................................................................................. 38 D.N.A. CTI.................................................................................................................................... 39 D.N.A. Server ..................................................................................................................... 193, 194
290
Technical Guide
Data141, 142, 160, 161, 233, 234, 235, 236, 237, 238, 239, 240, 243, 244, 245, 246, 247, 248, 249, 250, 251, 252, 253, 254, 255, 256, 257, 258, 259, 260, 261, 262, 263, 264, 265, 266, 267, 268, 269, 270, 271, 272, 273, 274, 275, 276, 277, 278, 279, 280, 281 Data Tables................................................................................................................................ 227 Database.................................................................................................................................... 123 Database Compression ............................................................................................................. 118 Database Organization ...................................................................................................... 147, 160 Databases .......................................................................................................... 142, 147, 160, 161 Datex.......................................................................................................................................... 237 Dialdy ......................................................................................................................................... 239 Directory Assistance ............................................................................................................... 161 Directory Browser .................................................................................................... 94, 95, 96, 166 Directory Configuration .............................................................................................................. 114 Directory Database ............................................................................................................ 142, 145 Directory Export ......................................................................................................................... 115 Directory Import ......................................................................................................................... 115 Directory Link....................................................................................................................... 37, 38 Directory Manager ....................................................................................... 35, 131, 162, 167, 176 Directory Structures ................................................................................................................... 162
E
E-Mail ......................................................................................................................... 201, 202, 203 Error Messages.......................................................................................... 126, 129, 223, 225, 288 Event Log ................................................................................................................................... 104 Event Viewer .............................................................................................................................. 126 Excel............................................................................................................................................ 57 Extens ........................................................................................................................................ 243 Extension Link ........................................................................................................................... 38 Extension Manager ................................................ 34, 60, 133, 134, 135, 136, 147, 163, 167, 170
F
Facilities ..................................................................................................................................... 112 FAQ............................................................................................................................................ 176 Fixed Part................................................................................................................................... 284
G
Glossary....................................................................................................................................... 19
H
Hard Disk ..................................................................................................................................... 53 Hardware ............................................................................................................................... 59, 77 Hardware Connections ................................................................................................................ 60
I
Installation62, 64, 65, 66, 67, 68, 69, 70, 72, 73, 74, 75, 76, 77, 78, 79, 80, 82, 83, 84, 85, 88, 89, 90, 91, 92, 93, 94, 95, 104, 105, 106 Installationj ................................................................................................................................... 85 Internet Tools ............................................................................................................................. 57 IP Extensions ............................................................................................................................. 286
K
Keyc_r ........................................................................................................................................ 245 Keyc_s ....................................................................................................................................... 247
291
L
LDAP............................................................................................................................................ 37 LDAP Configuration ................................................................................................................... 114 License Administrator ................................................................................................................ 115 License Viewer........................................................................................................................... 114 Limitations .................................................................................................................................... 23 Local Data Server ...................................................................................................................... 113 Local Database .......................................................................................................................... 118 Log Files..................................................................................................................................... 104 Log Off ....................................................................................................................................... 288 Logging ..................................................................................................................................... 118 Logon ......................................................................................................................................... 288
M
Maintenance .............................................................................................................................. 117 MD Support ................................................................................................ 171, 173, 174, 175, 176 MD110.............................................................................................................................. 46, 58, 59 MD110 BC ................................................................................................................................. 183 MD110 Support.......................................................................................................................... 114 Measinfo..................................................................................................................................... 249 Memory ...................................................................................................................................... 100 Messages................................................................................................... 104, 223, 224, 225, 226 MML Commands................................................................................................ 170, 171, 172, 173 Mobile Executive................................................................................................ 39, 40, 96, 97, 141 Mobility ....................................................................................................................................... 282 Modgrp ....................................................................................................................................... 251 MSDE........................................................................................................................................... 57
N
NCOP-OWS............................................................................... 195, 196, 197, 198, 199, 200, 201 Network .............................................................................................................................. 188, 190 Next CC........................................................................................................................................ 36 NPM ........................................................................................................................................... 165 Numbering Plan ..................................................................................................................... 91, 92 Numbering Plan Manager .......................................................................................................... 172
O
OneBox ................................................................................................................ 23, 24, 25, 26, 27 Opcorg ....................................................................................................................................... 256 Operator Configuration .............................................................................................................. 114 Operator Workstation ........................ 58, 137, 161, 165, 168, 177, 178, 179, 180, 201, 202, 203 Opindi......................................................................................................................................... 253 Opmann ..................................................................................................................................... 258
P
Pagext ........................................................................................................................................ 260 Pagsar........................................................................................................................................ 262 Passwords ................................................................................................................................. 116 Pbxgrp........................................................................................................................................ 264 PCM ................................................................................................................... 239, 247, 249, 256 PDM119, 120, 121, 122, 137, 138, 139, 160, 227, 229, 231, 233, 235, 237, 243, 245, 251, 253, 258, 260, 262, 264, 266, 268, 270, 272, 274, 276, 278, 280, 282, 284, 286 PDM CFP Data Table ................................................................................................................ 241 Performance ...................................................................................................... 100, 101, 102, 103
292
Technical Guide
Performance Data Manager .............................................................................................. 173, 181 Performance Manager ....................................................................................................... 166, 169 Personal Screen Call ................................................................................................................... 28 PPM ........................................................................................................................... 122, 139, 140 PPM Lite ................................................................................................................................ 92, 93 Pre-configured Installation ........................................................................................................... 77 Pre-installation ............................................................................................................................. 62 Pre-Installation ............................................................................................................................. 45 Problem Reporting ..................................................................................................................... 124
R
RDS Performance...................................................................................................................... 102 Registry............................................................................................................................. 185, 186 Registry Settings ..................................................................................................................... 116 Remote Data Monitor................................................................................................................... 44 Remote Data Server .......................................................................................................... 113, 181 Reports ............................................................................................................. 122, 123, 141, 288 Requirements................................................................................................................... 46, 53, 55 Restore ...................................................................................................................................... 123 Roubwy ...................................................................................................................................... 268 Rouddi........................................................................................................................................ 270 Roudio........................................................................................................................................ 272 Rouinc ........................................................................................................................................ 274 Rouout ....................................................................................................................................... 276
S
SCS............................................................................................................................................ 195 Serial Communications Server .......................................................................................... 113, 181 Server....................................................... 57, 58, 59, 62, 64, 65, 66, 67, 68, 77, 78, 85, 86, 87, 88 Server Configuration .................................................................................................................. 113 Server ID .................................................................................................................................... 116 Server Requirements ................................................................................................................... 53 Servers............................................................................................................................... 115, 116 Service Provicer......................................................................................................................... 195 Services ..................................................................................................................................... 112 Short Message Service.............................................................................................................. 118 SNMP................................................................................................................. 186, 187, 190, 191 SNMP Agent ................................................................................................................................ 42 SNMP Master Agent .................................................................................................................... 75 Software ....................................................................................................................................... 77 SQL Database........................................................................................................................... 117 SQL Server ................................................................................................ 57, 73, 74, 75, 161, 185 Supervisor .................................................................................................................................. 101 Synchronization ......................................................................................................................... 176
T
Table .......................................................................................................................................... 276 Tables229, 231, 233, 235, 237, 243, 245, 247, 249, 251, 253, 256, 258, 260, 262, 264, 266, 268, 270, 272, 274, 278, 280 Technical Support.................................................................................................................... 124 Tempoary Workspace................................................................................................................ 119 Time System Interface33, 206, 207, 208, 209, 210, 211, 212, 213, 214, 215, 216, 217, 218, 219, 220, 221 Time System Server .................................................................................................................. 113 Tone_r........................................................................................................................................ 278
293
Transaction Log ......................................................................................................................... 117 Troubleshooting ......................................................................................................................... 124 Trunk Manager........................................................................................................................... 114 Trunks ........................................................................................................................................ 280
U
Upgrade ....................................................................................................................................... 73 User Configuration ..................................................................................................................... 113 Users.......................................................................................................................................... 115
V
Visitor Registration....................................................................................................................... 45 Voice System Interface ...................................................................................................... 114, 205
W
WAP........................................................................................................................... 39, 40, 41, 42 What is D.N.A.? ........................................................................................................................... 15 Windows ................................................................................................. 56, 57, 68, 69, 70, 71, 72 Windows 2000 ....................................................................................................................... 72, 73
294

MD110 DNA Tech Guide Help

Uploaded by

Copyright:

Available Formats

MD110 DNA Tech Guide Help

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MD110 DNA Tech Guide Help

Uploaded by

Copyright:

Available Formats

MD110 Dynamic Network Administration

MD110 Dynamic Network Administration

MD110 Dynamic Network Administration

MD110 Dynamic Network Administration

MD110 Dynamic Network Administration

MD110 Dynamic Network Administration

MD110 Dynamic Network Administration

MD110 Dynamic Network Administration

MD110 Dynamic Network Administration

+ = full interworking * = restricted interworking - = no interworking

What You Will Find In This Help Guide

MD110 Dynamic Network Administration

Conventions Used in This Guide

Tips for using Help

MD110 Dynamic Network Administration

MD110 Dynamic Network Administration

Directory Manager (DMG) Directory Browser

Operator Workstation (OWS)

Extension Manager (EMG)

Performance Manager (PMG)

Numbering Plan Manager (NPM)

spanning multiple Business Subscriber Systems.

OneBox Mailbox Integration

MD110 Dynamic Network Administration

Integration of OneBox and D.N.A.

OneBox Compatibility with Other Network Elements

MD110 Dynamic Network Administration

Compatibility with Other Network Elements

D.N.A. Application Suite - MD110

Dial By Name Directory

Compatibility with Other Network Elements

MD110 Dynamic Network Administration

Personal Screen Call

PSC integration with D.N.A. RDS

MD110 Dynamic Network Administration

MD110 Dynamic Network Administration

Application Link and CCA

Application Link and PSC

Compatibility with Other Network Elements

Time System Interface

Compatibility with Other Network Elements = MD110 = Business Phone

MD110 Dynamic Network Administration

CCM/D.N.A. Extension Manager Integration

Compatibility with Other Network Elements Available for MD110 only.

CCA/D.N.A. Directory Manager Integration

Compatibility with Other Network Elements = MD110 = Business Phone.

MD110 Dynamic Network Administration

Next CC/D.N.A. Integration

Compatibility with Other Network Elements Available for MD110 only.

MD110 Dynamic Network Administration

MD110 Dynamic Network Administration

Go to the WAP Services menu and select 6 WAP Settings.

MD110 Dynamic Network Administration

The Monitored Objects

MD110 Dynamic Network Administration

Remote Data Monitor

MD110 Dynamic Network Administration

MD110 Hardware Requirements

Single node vs. multi-node

Single Server with Operator Workstation VIP