Dynamic Network Administration 5.

4
Technical Guide

EN/LZT 108 3855 R3I

Ericsson Enterprise AB 2004-2006 All rights reserved. No parts of this publication may be reproduced, stored in retrieval systems, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without prior written permission of the publisher except in accordance with the following terms: When this publication is made available on Ericsson media, Ericsson gives its consent to downloading and printing copies of the content provided in this file, only for private use and not for redistribution. No parts of this publication may be subject to alteration, modification or commercial use. Ericsson will not be liable for any damages arising from use of an illegal modified or altered publication.

Disclaimer
The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.

Table of Contents
Chapter 1 Key Information 1
Dynamic Network Administration ..................................................................................1 Compatibility.....................................................................................................1 D.N.A. Interworking .......................................................................................................2 D.N.A. Server ...................................................................................................3 D.N.A. Support for Extensions .........................................................................3 What You Will Find In This Help Guide.........................................................................4 Related Publications ........................................................................................5 Conventions Used in This Guide .....................................................................5 Glossary ........................................................................................................................5

Chapter 2 Applications

11

Description of Applications..........................................................................................11 Limitations ...................................................................................................................13 Add Component, Add Locale, Database Upsize, Reinstallation....................13 PPM Lite.........................................................................................................13 OWS Screen Resolution ................................................................................13 SQL Server 2000 Security mode ...................................................................14 SQL Server 2000 Named Instances ..............................................................14 Ericsson Communication Assistant................................................................14 Extension Manager ........................................................................................15 Licenses ......................................................................................................................15 Extension Manager ........................................................................................15 Personal Number ...........................................................................................15 OneBox Mailbox Integration........................................................................................16 Integration of OneBox and D.N.A. .................................................................16 OneBox Compatibility with Other Network Elements.....................................18 Compatibility with Other Network Elements...................................................20 Application Link ...........................................................................................................20 General Operations........................................................................................20 Application Link and ECA ..............................................................................21 Compatibility with Other Network Elements...................................................21 Name Display in MD110 .............................................................................................21 Dial By Name Directory..................................................................................22 Time System Server....................................................................................................22 CCM/D.N.A. Extension Manager Integration ..............................................................23 CCA/D.N.A. Directory Manager Integration ................................................................24 Solidus eCare / D.N.A. Integration..............................................................................24 LDAP Support in D.N.A...............................................................................................25 Other Interfaces ..........................................................................................................26 Directory Link .................................................................................................26 Extension Link................................................................................................26 D.N.A. CAAPI.................................................................................................26 Change Log....................................................................................................26 D.N.A. CTI......................................................................................................26 Mobile Executive .........................................................................................................27

Table of Contents

Dynamic Network Administration Technical Guide

WAP Gateway................................................................................................27 Phone Setup ..................................................................................................27 SNMP Agent ...............................................................................................................30 The Monitored Objects...................................................................................31 Remote Data Monitor ..................................................................................................31 Captured Filename ........................................................................................33 Visitor Registration ......................................................................................................33 Web Switch Net Manager ...........................................................................................34 Ericsson Communication Assistant.............................................................................35 Personal Assistant for Smartphone ............................................................................35

Chapter 3 License Administration

37

License handling with D.N.A. 5.4 ................................................................................37 The order and information flow ...................................................................................37 Generating Fingerprint file ..........................................................................................38 The Web application ...................................................................................................38 Providing access to the application.............................................................................39 Support........................................................................................................................39

Chapter 4 Pre-Installation

41

About Pre-Installation..................................................................................................41 Pre-Installation Meeting .................................................................................41 PBX Hardware Requirements.....................................................................................41 Configuration Options .................................................................................................42 Stand alone ....................................................................................................42 Single Server with Clients ..............................................................................43 PC Hardware Requirements .......................................................................................44 Server.............................................................................................................44 Client PC ........................................................................................................45 Additional Hardware Options .........................................................................47 Hard Disk Requirements.............................................................................................47 Recommendation ...........................................................................................47 Server Disk Space Requirements...............................................................................47 Client Disk Space Requirements ................................................................................49 Software Requirements ..............................................................................................51 Windows.........................................................................................................51 SQL Server ....................................................................................................51 Excel ..............................................................................................................51 Internet Tools .................................................................................................51 Client/MD110 Connections for Operator Workstation.................................................52 Server/MD110 Connection for Operator Workstation .................................................52 Client/ MX-ONE Telephony Server Connections for Operator Workstation............53 Server/ MX-ONE Telephony Server Connection for Operator Workstation ............54 Configuration Management Hardware Connections...................................................54 Hardware Connections for Extension Manager ..........................................................56

Chapter 5 SQL Installation

59

SQL Server 2005 ........................................................................................................59 To install SQL Server 2005............................................................................59 Upgrading to SQL Server 2005......................................................................60

ii

Dynamic Network Administration Technical Guide

Table of Contents

Security ..........................................................................................................60 Memory ..........................................................................................................60 Upgrade from MSDE to SQL Xpress Engine..............................................................61 SQL Server 2000 ........................................................................................................61 Upgrade .........................................................................................................61 New Installation..............................................................................................62 Unattended SQL Server Installation ...........................................................................63 Install SQL Server 2005 Standard Edition Unattended .................................64 Install SQL Server 2000 Standard Edition Unattended .................................64 Change SQL SA password .........................................................................................65 Install SQL Server Service Pack.................................................................................66 SNMP Master Agent ...................................................................................................67 Windows 2000................................................................................................67

Chapter 6 D.N.A. Installation

69

About Installation.........................................................................................................69 Hardware Connections ..................................................................................69 Software Installation.......................................................................................69 Installation Checklists..................................................................................................69 Using the Checklists ......................................................................................69 Application Suite Installation .......................................................................................71 Installation Features.......................................................................................71 Pre-Configured System..................................................................................72 Upgrading To D.N.A. 5.4.............................................................................................75 Upgrading from D.N.A. running on SQL Server 7.0 or MSDE.......................75 Transferring D.N.A. from one computer to another .......................................75 Installing Enterprise License Server ..............................................................76 Server Installation .......................................................................................................77 Auto-Run Installation......................................................................................77 Taskbar Installation........................................................................................77 New Server Installation ..................................................................................78 Installation Options ........................................................................................82 Add Components ...........................................................................................82 Resize Database............................................................................................83 Client Installation.........................................................................................................83 Auto-Run Installation......................................................................................83 Taskbar Installation........................................................................................84 New Client Installation ...................................................................................84 Client Installation Options ..............................................................................86 Silent Installation .........................................................................................................87 Modifying the Setup (dnasuite.ini) File...........................................................87 Installation Procedure ....................................................................................88 Using the Setup Command............................................................................88 PPM Lite......................................................................................................................89 Installing with Auto-Run .................................................................................89 Installation Options ........................................................................................90 Upgrade PPM Lite..........................................................................................90 Post Installation..............................................................................................91 PPMLite Installed on IIS 6.0...........................................................................96 Ericsson Communication Assistant...........................................................................100 Prerequisites ................................................................................................100 Installing with Auto-Run ...............................................................................105

iii

Table of Contents

Dynamic Network Administration Technical Guide

Installation Procedure ..................................................................................106 Virtual Machine ............................................................................................106 Installation Options ......................................................................................106 Upgrade Ericsson Communication Assistant...............................................107 Post Installation Only if IIS 6.0 is used .....................................................107 Mobile Executive .......................................................................................................110 Installing with Auto-Run ...............................................................................110 Installation Options ......................................................................................111 Upgrade Mobile Executive ...........................................................................111 Post Installation Only if IIS 6.0 is used .....................................................111 Personal Assistant ....................................................................................................114 Installing with Auto-Run ...............................................................................114 Installation Options ......................................................................................115 Post Installation Only if IIS 6.0 is used .....................................................115 Outlook Integration....................................................................................................118 Customizing Outlook Security Features ......................................................120 D.N.A. Outlook Integration Logging .............................................................138 Lotus Notes Integration.............................................................................................139 Installing Lotus Notes Integration Installation package on D.N.A. Server with Auto-Run...............................................................................................139 Installing D.N.A. Lotus Notes Integration Templates on Domino Server.....139 Setting up D.N.A. Lotus Notes Integration Templates.................................140 Installing D.N.A. Lotus Notes Integration on Notes Client ...........................145 Registry Value for Message Diversion Synchronization ..............................145 Registry location...........................................................................................145 COMPUTER or USER ID User Defined Fields............................................146 Help..............................................................................................................146 D.N.A. Client Installation on Windows XP ................................................................147 Successful Configuration .............................................................................147 Unsuccessful Configuration .........................................................................147 Personal Assistant for Smartphone Installation ........................................................149 D.N.A. Service Pack Installation ...............................................................................149

Chapter 7 ECC Installation

151

Server Installation .....................................................................................................151 Server Installation ........................................................................................151 Pre-requisites ...............................................................................................151 Installation Options ......................................................................................152 Registration Information...............................................................................152 Virtual Directory............................................................................................152 ApplicationLink Configuration ......................................................................153 Summary Information...................................................................................153 Configurations ..............................................................................................153 Post Installation Only if IIS 6.0 is used .....................................................157 Client Installation.......................................................................................................159 Installation Options ......................................................................................159 Configurations ..............................................................................................160 Client Update ............................................................................................................161 File Version Comparison..............................................................................161 Client Installation Download and Update.....................................................161 Compatibility..............................................................................................................162

iv

Dynamic Network Administration Technical Guide

Table of Contents

Chapter 8 Performance

163

Performance Enhancements ....................................................................................163 Creating More Available Memory..............................................................................163 Operator Workstation Supervisor..............................................................................164 RDS Performance .....................................................................................................164 LDB Integrity Check Feature........................................................................164 Reduce I/O Completion Ports in Large Systems .........................................165 Enable/Disable Incremental LDB Updates from DMG.................................165 Configure RDS to Use Fewer SQL Connections .........................................166

Chapter 9 D.N.A. Server

167

Facilities and Services ..............................................................................................167 Administrative Tools..................................................................................................169 Changing Users, Servers, and Passwords ...............................................................171 Registry .....................................................................................................................172 Registry Settings ..........................................................................................172 Server Identification .....................................................................................173 Maintenance..............................................................................................................173 SQL Database..............................................................................................173 Logging Facilities Server..............................................................................174 Short Message Service.............................................................................................174 Limitations ....................................................................................................175 Short Message Service Standby..................................................................175 Local Database Compression...................................................................................175 GICI Connection........................................................................................................176 Message Diversion and Secondary and/or Shared Extension .................................176

Chapter 10 Maintenance

179

Archival Backup ........................................................................................................179 Temporary Workspace.................................................................................179 Automatic Extraction .................................................................................................179 Performance Data Manager Operations......................................................180 Two Ways to Start the Extraction Process ..................................................180 The Data Extraction Command....................................................................180 Clock Synchronization .................................................................................181 Extraction Process .......................................................................................181 Skip Nodes for Polling..................................................................................181 Extend Polling Time .....................................................................................182 Presentation Manager...............................................................................................182 Operational Requirements ...........................................................................182 Traffic Measurement Reports ......................................................................182 Preserving Edited Reports ...........................................................................182 Database Utility .........................................................................................................182 Options.........................................................................................................183 Capacity and Limitations..............................................................................183

Chapter 11 Troubleshooting

185

Log Files....................................................................................................................185 D.N.A. Server Installation Logs....................................................................185 D.N.A. Client Installation Logs .....................................................................185

Table of Contents

Dynamic Network Administration Technical Guide

ECA Installation Logs...................................................................................185 ECC Client Installation Logs ........................................................................185 Mobile Executive Installation Logs...............................................................185 PPMLite Installation Logs ............................................................................185 Personal Assistant Installation Logs ............................................................185 Event Log Messages ................................................................................................186 Technical Support .....................................................................................................200 Before Contacting Technical Support ..........................................................200 Reporting Your Problem ...........................................................................................201 Problem Description.....................................................................................201 PBX ..............................................................................................................201 Operating System Information (mark all that apply) ....................................201 Configuration................................................................................................201 Network Protocol (mark all that apply) .........................................................201 PC ................................................................................................................202 D.N.A. Applications ......................................................................................202 Directory Manager.....................................................................................................202 Ericsson Communication Client ................................................................................206 Extension Manager ...................................................................................................208 Operator Workstation ................................................................................................214 OWS Supervisor .......................................................................................................216 Performance Data Manager......................................................................................218 Performance Presentation Manager .........................................................................221 Essential Requirements ...............................................................................221 Report Limitations ........................................................................................221 General PPM Problems ...............................................................................221 Remote Data Server .................................................................................................222 Mobile Executive .......................................................................................................223 Ericsson Communication Assistant...........................................................................223 Call Handling problems................................................................................224 Personal Number problems .........................................................................224 Trace ............................................................................................................225 Service .........................................................................................................226 Header Error ................................................................................................226 Fields are Disabled ......................................................................................228 Slow to logon................................................................................................229 Outlook Integration & Lotus Notes Integration..........................................................229 Outlook or Lotus Notes Integration would not start......................................229 Outlook or Lotus Notes Integration would not logon to the DNA Server .....229 Diversion information does not match between Outlook or Lotus Notes Integration and DNA ....................................................................................229 DNA Outlook Integration and Calendar Conflicts ........................................229 Troubleshooting with Remote Data Monitor ................................................230

Chapter 12 Application Data

231

Report Generation.....................................................................................................231 Directory Manager Database Organization ..............................................................232 Extension Manager Database Organization .............................................................238 PDM Database Organization ....................................................................................252 Operator Workstation Data .......................................................................................254 Directory Assistance Databases ..................................................................254 Operator Workstation Configuration ............................................................254

vi

Dynamic Network Administration Technical Guide

Table of Contents

Chapter 13 MML Commands

255

Extension Manager ...................................................................................................255 MD Support Utility .....................................................................................................257 Performance Data Manager......................................................................................259 MD Support Command Line Synchronization...........................................................261 Command Line Syntax.................................................................................261

Chapter 14 Frequently Asked Questions

265

Directory Manager.....................................................................................................265 D.N.A. Server ............................................................................................................266 Operator Workstation ................................................................................................267 Remote Data Server .................................................................................................270 Serial Communications Server .................................................................................272 Performance Data Manager......................................................................................272 D.N.A. Application Suite............................................................................................273 MD110..........................................................................................................273 Registry ........................................................................................................274 SQL Server ..................................................................................................275 ClockSync ....................................................................................................275 SNMP...........................................................................................................276 Export...........................................................................................................276 Ericsson Communication Assistant...........................................................................276

Chapter 15 Configuration

279

Networking (SNMP) Access Agent ...........................................................................279 Web Site Security......................................................................................................285 Windows 2000 Server and Windows Server 2003 ......................................285 Setup D.N.A. Web Applications on Windows 2003 and IIS 6.0 ................................285 Configurations setup automatically by D.N.A. installation ...........................285 Configurations to Run D.N.A. Web Applications in Worker Process Isolation Mode..............................................................................................286 D.N.A. Server and IIS 6.0 Server on Different Machines.............................292 D.N.A. Port Assignments ..........................................................................................293 D.N.A. 5.4.....................................................................................................293 Ericsson Communication Assistant...........................................................................296 To setup end users Web browser ...............................................................296 To setup Ericsson Communication Assistant user account.........................297 To configure Ericsson Communication Assistant Server.............................297 Personal Contact Search .............................................................................301 Ericsson Communication Client ................................................................................303 ECC Port Usage...........................................................................................303 Changing the default language setting for ECC ..........................................303 Using ECC with a Virtual Private Network (VPN) ........................................303 Monitor Feature Access for ECC .................................................................304 Restricting Display of External Numbers .....................................................304 User ID and Password for ECA, ECC, and DME......................................................305 D.N.A. Directory Configuration.....................................................................305 D.N.A. Directory Manager............................................................................305 User ID .........................................................................................................305 Password .....................................................................................................305 Operator Workstation ................................................................................................306
vii

Table of Contents

Dynamic Network Administration Technical Guide

Improving the Performance of OWS ............................................................306 E-mail Integration .........................................................................................306 Personal Assistant for Smartphone .............................................................307

Chapter 16 VSI and TSS

309

Voice System Interface .............................................................................................309 Setting Up Communications and Configuration Parameters .......................309 The VSI Protocol ..........................................................................................309 Capacities and Limitations ...........................................................................312 Time System Server..................................................................................................312 Interface .......................................................................................................312 Protocols ......................................................................................................312 FLEXIM Protocol ..........................................................................................313 General Protocol ..........................................................................................319 CTR Protocol................................................................................................322 TIMECON Protocol ......................................................................................328 Exchange Interface ......................................................................................329 Message Types.........................................................................................................329 IVR/Voice System to VSI Messages.........................................................................329 IVR/Voice System from VSI Messages.....................................................................331

Chapter 17 Security

335

Directory Security......................................................................................................335 Services and Accounts/Rights ..................................................................................337 ODBC Connection.....................................................................................................339 Files Copied to Other Directories..............................................................................340 Databases .................................................................................................................344 Registry .....................................................................................................................345 Location........................................................................................................345 Permissions..................................................................................................346

viii

Chapter 1 Key Information

Dynamic Network Administration
Congratulations on your selection of Ericsson's Dynamic Network Architecture (D.N.A.) application suite as your PBX call management system. The D.N.A. Application Suite is a comprehensive family of graphical PC-based programs and utilities supporting PBX operation and administration. D.N.A. provides PBX operational support in the following major areas: ! ! ! ! ! Operator Call Management Extension Management Directory Management High-level Telecommunications Network Supervision Traffic Measurement and Reporting

Compatibility
This release of the D.N.A. Application Suite is compatible with: ! Microsoft Windows 2000 Server with Service Pack 4, Windows 2003 with Service Pack 1, Windows 2003 Server R2 and Microsoft Windows 2000 Server with Service Pack 4 Note: It is assumed that both the D.N.A. server and D.N.A. clients are in the same domain. If D.N.A. clients exist in other domains, then domain trust relationships must be established. Please refer to your Windows documentation for more details. ! ! ! ! ! ! ! ! ! ! ! ! Microsoft Windows 2000 Professional with Service Pack 4 and Windows XP Professional with Service Pack 2 Ericsson MD110 PBX release BC12.1 Ericsson MX-ONE Telephony Switch Ericsson MX-ONE Telephony Server 3.0 Microsoft SQL Server 2000 Desktop Engine Microsoft SQL Server 2005 Microsoft SQL Server 2005 Express Edition Microsoft Internet Information Server 5.0, and 6.0 Microsoft Office 2002, and Office 2003 Service Pack 2 Ericsson Application Link 4.0 Ericsson CT Adapter, ZAT 505 120/1 Ericsson Extender Keyboard, KDT 252 001/02

Key Information

Dynamic Network Administration Technical Guide

! ! ! !

Ericsson D.N.A. Access Agent and SNMP application Microsoft Internet Explorer 5.5 or later Netscape 4.x, 6.x, and 7.x Notes 4.6.7, 5.0.2B and later, 6.0.x, and 6.5. Roaming User feature supported from Notes 6.0.1 is not supported by D.N.A. Notes Integration.

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 3.0 and newer Time Systems CCM CCA Solidus eCare LDAP Data Sources MD110 IP-PBX Business Phone Web Switch

The relevant network elements are

The following matrix shows current interworking between different network elements and the CTI applications: OneBox D.N.A. D.N.A. PMG Server /DMG/OWS MD110/MX- + ONE TSW IP-PBX 2.0 Business Phone + + + + App Link CCA CCM Solidus eCare

+ +

+ +*1

+ = full interworking

Dynamic Network Administration Key Information

Technical Guide

* = restricted interworking - = no interworking

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 PBX nodes. The central component of a D.N.A. Installation is the Remote Data Server (RDS). RDS maintains network database synchronization among all 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 PBX. 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.

D.N.A. Support for Extensions

The following matrix shows current support for various extension types in DNA 5.4 for MD110/MX-ONE TSW /MX-ONE 3.0: MD110/MX-ONE TSW Generic IP Mobile Cordless Analog Digital + + + + + + MX-ONE 3.0 + + + + + *

Key Information

Dynamic Network Administration Technical Guide

MD110/MX-ONE TSW Digital POTS Data Dual Access ISDN + + + +

MX-ONE 3.0 * -

NOTE: Equipment change is not allowed for Digital/Digital POTS extension types, since KSEXC command is removed in MX-ONE 3.0 release. + = full support * = restricted support - = no support

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 PBX operations. This guide includes the following help books. Applications - Provides a basic description of the applications. License Administration Describes the licenses handling in D.N.A. 5.4 based on the Enterprise License Manager. Pre Installation - Describes the main types of installations, PC hardware requirements, software which must be installed on the PC, and requirements for the PBX. SQL Installation - Describes SQL Server installation information, including SQL Server 2005 and 2000 installation, unattended SQL installation, change sa password, apply SQL Server service pack. D.N.A. Installation - Describes first-time installation of the D.N.A. applications, including hardware connections between the PBX and PC, and installation of the application software on the PC. ECC Installation - Describes both server and client installation for ECC including privilege needed to run installation. Performance - Describes basic steps to improve D.N.A. performance following installation. Installation problem - Describes where to find log files and event log error messages, to troubleshoot installation problem. D.N.A. Server - Describes the components that form the D.N.A. server, including the security and support platform for Dynamic Network Administration (D.N.A.) applications.

Dynamic Network Administration Key Information

Technical Guide

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. MML Commands - Tables of commands for Extension Manager, MDS Utilities, and Performance Data Manager. Frequently Asked Questions - Provides answers to some basic questions regarding D.N.A. Configuration - Describes other configuration items such as D.N.A. Agent Access module, Web site security and certificate request. VSI and TSS - Describes the Voice System Interface between an IVR system and D.N.A., as well as the optional Time System Server. Security - Describes D.N.A. Directory security, Service and Accounts/Rights, ODBC connection, Files copied to other directories, Database permissions, Registry location and permissions.

Related Publications
In addition to the "D.N.A. Technical Guide," getting started guides are available for the following products. ! ! ! ! ! Operator Workstation Extension Manager Directory Manager Performance Manager Mobile Executive

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 LAN that is hosting the D.N.A. server PC.

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 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.

Key Information

Dynamic Network Administration Technical Guide

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 PBX. Computer Telephony Adaptor (CT Adapter) - Enables an Operator Workstation (OWS) PC to connect to the PBX 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 PBXs to manage telecommunications operations. D.N.A. Mobile Executive (DME) - The D.N.A. Mobile Executive enables the user to access some of the D.N.A. Application Suite features via WAP enabled devices. The features supported are directory search, click to dial a phone number from search result, retrieve short messages, set message diversion, activate personal number profile, and manual dial. However, the features supported are dependent upon device type. D.N.A. Notes Integration (DNI) - Provides a client-side bi-directional integration to synchronize the message diversions between the Lotus Notes Calendar and D.N.A. server. The templates are supported to provide the needed fields to schedule a message diversion from Lotus Notes. D.N.A. Outlook Integration (DOI) - Provides a client-side bi-directional integration for synchronizing message diversions between Microsoft Office Outlook Calendar and the D.N.A. server. DOI invokes the Outlook Calendar appointment window with a message diversion reason code placed in the fixed calendar fields, to schedule the message diversion from Outlook. 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. Ericsson Communication Assistant (ECA) - A browser-based GUI end user application that provides the capabilities for directory search, message diversion, personal number profile, diversion, short messages, and call handling features. Ericsson IP-PBX - The IP-PBX that can be connected to the MD110 as a branch office. E&M Signaling Device - Electronic interface between the PBX and recorded voice announcement (RVA) equipment. See also Voice Server Unit (VSU).

Dynamic Network Administration Key Information

Technical Guide

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 PBX telephone data and extensions. Includes capabilities for administration of telephone and data extensions, messaging, and other PBX elements. General Information Communications Interface (GICI) - The logical interface for the ICU or NIU board in the PBX. 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. The list is available at http://www.microsoft.com/hcl. Information Computer Unit (ICU) - The board in an MD110 BC9 and earlier used for interception and message waiting services. Replaced by the NIU in BC10. 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 PBX 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, packet-switched connections, and semipermanent connections. The complete digital interface (2B+D) consists of two Bchannels 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 the directory 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 PBX controls. MD110 - The Ericsson PBX. MD Support (MDS) - A D.N.A. administrative utility that synchronizes 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 PBX. 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.

Key Information

Dynamic Network Administration Technical Guide

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. Windows File System (NTFS) The Windows file system. Operator Workstation (OWS) - A D.N.A. application that enables operators to manage PBX 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 PBX nodes, and PPM is used to generate reports based on data extracted by PDM. Performance Presentation Manager (PPM) - See Performance Manager. Performance Presentation Manager Lite (PPM Lite) - A Web-based application that provides a sub set of the PPM functionality by providing the user with a limited number of reports which may be viewed with a browser. Personal Assistant for Smartphone - The Personal Assistant for Smartphone is a graphical user interface (GUI) application running in the Sony Ericsson P900 smartphone that serves as an interface to the Mobile Extension (ME) features of the MD110. It also has the capability to access the Ericsson Dynamic Network Administration (DNA) directory through the Internet using General Packet Radio Service (GPRS). The directory is located on a Web-based server and accessed thru Hyper Text Transfer Protocol (HTTP). Primary Domain Controller (PDC) - A Windows 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, PBXs 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 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 the same physical PC.

Dynamic Network Administration Key Information

Technical Guide

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. Replaced by the CT-adapter. 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. TSS 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. Voice System Interface (VSI) - An optional D.N.A. module that allows voice mail integration. VSI acts as a compatibility interface between the 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. WAP - Wireless Application Protocol. Wide Area Network (WAN) - Inter-office private communication network.

Chapter 2 Applications
Description of Applications
The D.N.A. application suite is an integrated set of applications that allow you to operate and manage your PBX communications resources from stand-alone or networked PCs. The application suite includes the following applications. Application D.N.A. Server * Description 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. Localized into the following languages: French | German | Spanish Directory Manager (DMG) OWS support and administrative application that enables you to add, modify, and delete D.N.A. Directory entries. ** Localized into the following languages: Danish | Dutch | Chinese (Simplified) | Finnish | French | German | Italian | Norwegian (Bokmal) | Spanish | Swedish Operator Workstation (OWS) ** Localized into the following languages: Danish | Dutch | Chinese (Simplified) | Finnish | French | German | Italian | Norwegian (Bokmal) | Spanish | Swedish Extension Manager (EMG) D.N.A. application for management of PBX telephone data (extensions, extension groups, equipment assignments, and other resources). ** Localized into the following languages: Dutch | French | German | Spanish Performance Manager A traffic measurement and reporting application for network performance analysis. Allows analysts and D.N.A. traffic management application. Allows operators to access D.N.A. Directory subscriber information and route telephone traffic.

11

Applications

Dynamic Network Administration Technical Guide

Application (PMG) **

Description 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 PBX nodes. PPM creates reports from data extracted by PDM. Localized into the following languages: French | German | Spanish

Ericsson Communication Assistant (ECA) *

This application 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, Ericsson Communication Assistant allows you to send and receive short text messages, set and view message diversion, and make calls. Localized into the following languages: Danish | Dutch | Chinese (Simplified) | Finnish | French | German | Italian | Norwegian (Bokmal) | Spanish | Swedish

Ericsson Communication Client (ECC) *

Ericssons IP-based software telephony client. ECC offers IP based business class telephony along with directory search, message diversion and personal number management. Localized into the following languages: Danish | Dutch | Finnish | French | German | Italian | Norwegian (Bokmal) | Spanish | Swedish

PPM Lite **

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. Localized into the following languages: French | German | Spanish

D.N.A. Mobile Executive (DME) ***

A WAP application allowing users to access the D.N.A. directory, Message Diversion and Personal Number functions via a WAP enabled device like a cellular phone. Localized into the following languages: Danish | Dutch | Finnish | French | German | Italian | Norwegian (Bokmal) | Spanish | Swedish

12

Dynamic Network Administration Technical Guide

Applications

Application Personal Assistant for Smartphone ***

Description This application running in the Sony Ericsson P900 smartphone allows P900 users to search the corporate phone directory and its Contacts and then to click-anddial from the search result. The P900 acts as a mobile extension to the PBX. Users can make and receive calls through the PBX. In addition, P900 users can invoke a list of the PBX features, such as transferring calls. Localized into the following languages: Swedish

Available in GUI and online Help

** Available in GUI, online Help, and as electronic Getting Started Guide (Getting Started Guide for DMG, EMG and PMG are in English only). *** Available in GUI and electronic Getting Started Guide Note: All applications are offered in English.

Limitations
Add Component, Add Locale, Database Upsize, Reinstallation
If a component, locale, server database upsize, or reinstallation is needed, these actions must be performed from Control Panel > Add/Remove instead of the CD-ROM (media kit). The side effect of performing the above mentioned activities from the CD-ROM, is that the service pack version information in the About Boxes will be incorrect.

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 website must not be disabled. PPM Lite output must be viewed using monitors with minimum display capabilities of 256 colors, and 800 x 600 resolution.

OWS Screen Resolution

The minimum screen resolution requirement for the OWS is 800 x 600 for the Traditional mode, and 1024 x 768 for the Modern mode. The following items will take effect for OWS with the Modern appearance mode when running in a resolution of less than 1024 x 768: ! The Appearance menu item will be disabled, so the OWS user cannot switch to the Modern appearance mode.

13

Applications

Dynamic Network Administration Technical Guide

If the OWS user previously was running in the Modern mode, a warning message box will be displayed indicating that the Modern mode cannot be supported with the current display resolution, and the traditional appearance mode will be shown. Note: In this case, the OWS Background Color setting for the background of the directory search list will remain in the blue color for the Modern appearance mode. To change this to be compatible with the traditional appearance, change the Background Color setting to gray.

If the OWS user switches to a lower resolution while running OWS in the Modern mode, a warning message box will be displayed indicating that the Modern mode cannot be supported with the current display resolution, and the traditional appearance mode will be shown. Note: The warning message will be displayed for Windows XP only. For other operating systems, the traditional appearance mode will be shown without a warning message.

SQL Server 2000 Security mode

D.N.A. 5.4 will only work if the SQL 2000 server is installed with "Mixed mode" / "SQL Server and Windows" security mode. D.N.A. 5.4 does NOT support the "Windows authentication mode" / "Windows only" security mode.

SQL Server 2000 Named Instances

D.N.A. 5.4 supports the new SQL Server 2000 installation option "named instances," but the following feature does NOT work using this option: Call Accounting API. If you are installing SQL 2000 embedded from the D.N.A. installation program using the provided .iss files, you will get a default instance of SQL Server 2000 running in mixed security mode.

Ericsson Communication Assistant

Analog phone
When two calls are placed with an analog phone, users cannot toggle between the two calls. When the call on hold is selected in the Call Handling window or Hook Flash pressed on the analog phone, the "talking" call is dropped instead of going on hold.

Screen resolution
If screen resolution is set higher than 1280 x 1024, the background image will tile when the browser window is maximized, or made large enough to display more than 1280 x 1024 pixels inside the window.

Outlook integration
When configuring the Outlook integration in Ericsson Communication Assistant, the Microsoft Transaction Server Package user must have Administrator privileges on the Ericsson Communication Assistant server computer.

14

Dynamic Network Administration Technical Guide

Applications

Personal Number Profile Configuration

Only the users primary extension profile can be configured. If a user's profile cannot be configured or you cannot activate another profile, check the following: A D.N.A. account SYSTEM is created with EMG privileges granted. If the "Local System account" has been changed in the Ericsson RDS service's Properties, you need to add this new user in D.N.A. User Configuration Utility. This new user needs at least privileges for EMG, and all nodes related to users in ECA. Verify that this user can logon to EMG and connect to all the PBX nodes granted to it.

Extension Manager
When Extension Manager is used as a service by ECA, ECC, DME, or ExtLink to update Personal Number, it cannot be run as an application on the D.N.A. server. The Extension Manager application must be run from another machine. MD110 BC12 allows up to 30 night service positions. EMG only supports the initiation of one.

Licenses
Extension Manager
Extension Manager provides the capability to view available licenses for MD sale objects. To view this from Extension Manager, select the Properties menu and then select the License tab. A list of sale objects information, including whether licenses are available, will be displayed. If trial licenses are used, the expiration date will also be displayed in the dialog. Extension Manager interacts with licenses by allowing or disallowing certain sale objects to be initiated, changed, or deleted. Note: If you have modified a license file in the MD with new values for certain objects (e.g., updating a Personal Number license from a Trial license of 0 to 100 new licenses), use MD Support to synchronize the D.N.A. Database with the updated license information. A full synchronization is not required, only a feature that includes the updated license information (e.g., Operator Message Diversion).

Personal Number
Personal Number is the only PBX feature that requires licenses in ECA and ECC. There are different types of Personal Number licenses supported in PBX. ECA and ECC check licenses in the following sequence: 1. If a Trial license is not activated, or already expired, all Personal Number users will be allowed up to five profiles.

15

Applications

Dynamic Network Administration Technical Guide

2. If a Trial license is activated, and not expired, ECA and ECC will check for the existence of a Personal Number license. All Personal Number users will be allowed up to five profiles, if the Personal Number license is activated. However, ECA and ECC will not check for the license limit and will rely on the PBX to reject the Personal Number initiation if the license limit is reached. 3. If a Trial license and Personal Number license are not activated, ECA and ECC will check for Repeated-Individual-Diversion (RID) license. If it is set, all Personal Number users will be allowed one profile. 4. If there is no Trial license, Personal Number license, or RID license activated, all Generic extensions (including cordless extensions, IP extensions, and mobile extensions) will be allowed one profile.

OneBox Mailbox Integration

PBX 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.

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.

16

Dynamic Network Administration Technical Guide

Applications

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

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).

17

Applications

Dynamic Network Administration Technical Guide

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 six 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" From the Ericsson Communication Assistant Web interface D.N.A. users can initiate a diversion from Microsoft Outlook D.N.A. users can initiate a diversion from Lotus Notes Through the Telephone User Interface (TUI) of OneBox An Operator using D.N.A. Operator Workstation can initiate a diversion for any subscriber.

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."

18

Dynamic Network Administration Technical Guide

Applications

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. 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.

19

Applications

Dynamic Network Administration Technical Guide

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

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.

20

Dynamic Network Administration Technical Guide

Applications

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 CSTAbased API's or TAPI, however one server cannot support both.

Application Link and ECA

ECA 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. Windows 2000/XP/2003 clients in a TCP/IP network are supported.

Compatibility with Other Network Elements

! ! MD110 or Ericsson IP-PBX Business Phone (BusinessLink)

Name Display in MD110

The D.N.A. Extension Manager application allows users to upload the subscriber names from the Directory Database to the MD110. Since the MD110 has a limited display on digital phones, names are truncated according to two alternative methods. ! First letter of the first name, one blank and the first letters of the last name First name and the first letter of the last name

21

Applications

Dynamic Network Administration Technical Guide

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.

Time System Server

D.N.A. Time System Server (TSS) is an optional D.N.A. service module that connects to an external time monitoring system. TSS 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 Server 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 or Ericsson IP-PBX Business Phone (BusinessLink)

22

Dynamic Network Administration Technical Guide

Applications

CCM/D.N.A. Extension Manager Integration

With D.N.A. and CCM, you can configure the Call Center Manager (CCM) 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 Windows 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 to 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.

23

Applications

Dynamic Network Administration Technical Guide

CCA/D.N.A. Directory Manager Integration

With D.N.A. and CCA, CCA users can utilize the D.N.A. Directory Manager Information. Upon log-on, 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.

Solidus eCare / D.N.A. Integration

Solidus eCare can use the D.N.A. Directory Manager database. If a specially named user defined field (UDF) is configured in Directory Manager, Solidus eCare can import either the whole DMG Database or only subscribers with a "YES" entry in this field. The integration must be initiated manually from the Solidus eCare server. Upon log-on of a Solidus eCare 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 Solidus eCare agent can receive a copy of the D.N.A. Directory Manager Database. This database is stored locally on the Solidus eCare Agent PC.

24

Dynamic Network Administration Technical Guide

Applications

LDAP Support in D.N.A.

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 subscriber information and any LDAP Client (i.e., an Internet browser) is able to search the Directory Manager data through the D.N.A. LDAP Server.

25

Applications

Dynamic Network Administration Technical Guide

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 specifications are available for interested Ericsson Partners through the Ericsson Partner Program.

Extension Link
Extension Link is a real-time interface to the Extension Manager (EMG) application. Extension Link manages PBX extensions and facilities, and is designed to make EMG features reusable for customized configuration management applications. 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 or Ericsson IP-PBX Business Phone (BusinessLink)

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.

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.

26

Dynamic Network Administration Technical Guide

Applications

Mobile Executive
This section contains the administrator issues for the Mobile Executive. If you are using Ericsson D4 IP phone only, you can ignore the followings and use MD document for phone configurations.

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 WAP-gateway 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).

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).

27

Applications

Dynamic Network Administration Technical Guide

! ! !

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.

Click to Dial
This Call Handling feature can only be enabled if Mobile Extension features are activated. To enable the click to dial feature, complete the following steps: 1. 2. 3. 4. Turn on the Call Handling License. Open the Ericsson Communication Assistant Configuration Utility. Define the ApplicationLink Server. Define the access to outside lines for local and long distance calls.

Note: When the user logs on, the primary extension must be a mobile extension.

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 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.

2. 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.

3. Return to the Access menu, select 3 Service Center, and enter your Service Center number.

28

Dynamic Network Administration Technical Guide

Applications

4. 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.

5. Return to the GSM Data menu, select 2 Dial Type, and set the Dial Type to Analog.

6. Return to the GSM Data menu, select 3 User ID, and enter the user's ID.

7. Return to the GSM Data menu, select 4 Password, and enter the user's password.

29

Applications

Dynamic Network Administration Technical Guide

8. 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 2000, but is not part of the Typical Installation. To make the SNMP agent for D.N.A. work you must do two things, install D.N.A. and install the Windows master agent. You must have administrator privileges to perform this installation. SNMP is actually a DMI agent that emulates an SNMP agent. The following diagram shows an overview of the different components.

30

Dynamic Network Administration Technical Guide

Applications

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 must 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 master agent. Its function is to route SNMP requests to the correct DLL. Its functionality is built on installable sub-agents contained within DLL files that are loaded when the master agent is started (as a Windows service). The Registry entries 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 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.

Remote Data Monitor

The Remote Data Monitor (RDM) utility displays the messages exchanged between the Ericsson D.N.A. services and their client applications and services.

31

Applications

Dynamic Network Administration Technical Guide

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 PBX.

To start RDM, double-click on DNA_S\SHARE\BIN\rdm.exe.

RDM saves and restores the window size and position in the Registry. By default RDM connects with RDS on the D.N.A. server. If you want to monitor a different service and/or server, select the File > New menu item.

32

Dynamic Network Administration Technical Guide

Applications

RDM can be launched with command line arguments to connect with any server and service (except "Other"), making it possible to connect very quickly using a batch file or a command line submitted via Start/Run.... Here is the command line syntax: "/server n servername" where "n" is the index of the desired D.N.A. service to be monitored, as listed in the dialog displayed by the File > New menu item. 0) 1) 2) 3) 4) 5) LDAP LDS RDS SCS TSS VSI

The server name defaults to the D.N.A. server machine name unless RDM is already connected to a different machine when the dialog is displayed. In that case, just clear the server name combo box to get back to the D.N.A. server.

Captured Filename
The suggested capture filename concatenates the server name, service name, year number, month number and day number with ".log" as the extension. For example: "40POINTE_BREA_DRDS20030424.log" RDM supports the "auto-capture" command line switch "/ac". To run RDM monitoring RDS on the D.N.A. Server and capture the log file with the automatically generated name, place this batch file "RDM.bat" in the Startup folder for the appropriate user ID: start rdm /ac If there are other services you wish to log, add them to the batch file as well. For example to log SCS: start rdm /ac /server 3

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.

33

Applications

Dynamic Network Administration Technical Guide

Visitor data can also be entered, changed, or deleted in Directory Manager. Visitor entries are distinguished from permanent subscribers on the Options tab of the View/Update Subscriber dialog. A check in the "Show in Visitor Registration" box indicates the selected subscriber is a visitor, and the name will appear in the Visitor Name drop-down list in Visitor Registration. The absence of a check mark means this is a permanent subscriber who may act as a Contact Person and is therefore listed in the Contact Person drop-down list in Visitor Registration.

Web Switch Net Manager

To enable and launch Web Switch Net Manager from the Extension Manager application: Note: Before Web Switch Net Manager can be enabled, Ericsson Web Switch installation must be accomplished, to insure the necessary files are present. 1. From the Extension Manager application, select the Properties menu. 2. Select the PBX tab.

34

Dynamic Network Administration Technical Guide

Applications

1. In the Web Switch Net Manager path field, enter the path to the NetManager.jar file and click Apply. The Web Switch Net Manager is now enabled. 2. To launch Web Switch Net Manager, from the Others menu (in the Extension Manager application) select Web Switch Net Manager.

Ericsson Communication Assistant

The intent of the Ericsson Communication Assistant (ECA) is to help end users search phone directories, handle calls and manage your personal number and message diversion. Ericsson Communication Assistant is a web-based client/server application. Ericsson Communication Assistant replaces D.N.A. Directory Browser (DDB).

Personal Assistant for Smartphone

This application, running on the Sony Ericsson P900, lets user easily utilize the mobile extension feature of the PBX, thus making dialing to corporate users and personal contacts fast and easy. It also has the capability to access D.N.A. Directory through the Internet using General Packet Radio Service (GPRS). The Directory is located on a Web-based server and is accessed via Hyper Text Transfer Protocol (HTTP). The information to analyze the dialed number, to process the number with prefix, to dial the R1/R2 number, to display a list of PBX features, and to access the D.N.A. server, are all stored in an XML document with the file extension, .pbx, and is imported by the user to the P900 phone.

35

Applications

Dynamic Network Administration Technical Guide

36

Chapter 3 License Administration

License handling with D.N.A. 5.4
With the release of D.N.A. 5.4 the technical license for controlling the Right to Use (RTU) features and functions that are separately licensed from the basic system has been enhanced. The new solution is based on Software keys residing within a special license file to enable/disable the licensed features and functions. D.N.A. 5.4 is delivered with a 60 day fully opened license file giving the customer time to test and purchase features and functions that are licensed. Within 60 days a final license file (permanent license keys) has to be installed in the system to continue to use licensed features and functions. The license file is downloaded from an Ericsson Web interface on the Internet for smooth and fast administration. To access the Web application, the user needs a user ID and password (see Providing access to the application). The license file downloaded through the web must be installed in the Enterprise License Manager. Enterprise License Manager controls the licenses for the D.N.A. server. The D.N.A. server periodically communicates with Enterprise License Manager to determine whether the license information has changed. If this is the case, D.N.A. will update the internal license information within the D.N.A. server. The periodic interval is 15 minutes. Please note that the D.N.A. License Viewer will not show updated information until the next periodic interval has passed. However, restarting the Security Data Server service forces restarts the periodic interval and the license information is updated immediately. For detailed information of Enterprise License Manager, please refer to Enterprise License Manager documentation.

The order and information flow

Licenses are ordered in the same way as any other product from Ericsson Enterprise. Since licenses are a non-physical product there is no physical delivery. The concept that Ericsson Enterprise has developed for delivering licenses is based on the needs to be able to handle each ordered product as a individual item independent if it is a physical product or not. When purchasing licenses the deliverable will include a unique identity (Unique Pick Number UPN) for each license or license package ordered.

37

License Administration

Dynamic Network Administration Technical Guide

The Unique Pick Numbers (UPNs) are used in the License Web application described below to uniquely identify the purchased licenses. To access the ordered licenses, a user Id and password are needed to the License Web application and the unique pick numbers generated for each of the ordered licenses. The unique pick numbers are delivered through e-mail to a pre-defined email address. The unique pick numbers can then easily be re-distributed to the persons that need the unique pick number to be able to generate the license file for a specific D.N.A. system.

Generating Fingerprint file

To generate the fingerprint information needed to install permanent licenses, the fingerprint tool installed by Enterprise License Manager is used. For detailed information of how to use the tool, please refer to Enterprise License Manager documentation.

The Web application

The application is available through the Web page http://enterprise.Ericsson.net look for License Administration. Clicking on the link License Administration, the user will be requested to enter a user ID and password. After authentication, the user is able to choose to: ! ! ! Create License Download License Verify License information

To obtain a new license file for a D.N.A. 5.4 system the user has to select: ! Create License At this point the user will be taken to a Wizard which will guide them through the step-by-step process. The main steps are: Step 1. Select the UPN(s) to be assigned to the system. Step 2. Upload the fingerprint file from the D.N.A. system in question. The generated fingerprint file must be uploaded in order to create the new license file. Step 3. Give End Customer Information. Step 4. Verify that all are included before Submit. Step 5. Submit, which will generate a new license file. Submit initiates the creation of the new license file. Step 6. Download the new license file. The new license file can now be installed in the D.N.A. system. A number of checks are built into the Wizard to avoid basic faults.

38

Dynamic Network Administration Technical Guide

License Administration

If problem arises when using the tool, support is provided through the Enterprise License Centre.

Providing access to the application

The method for obtaining a user ID and password to the system is the same as for other applications like e-shop, Weblearn and Info Channel. The normal procedure for the partner to get the user ID and password is to send the user data for the users (name, company and e-mail address) to the contact person at the Partner Unit. The Partner Unit will then forward the information to Global Channel Operations for registration. A partner can also let his resellers obtain access to the applications in the same way. The e-mail address for UPN distribution is supplied in the same way.

Support
When a partner has a problem with the license Web application or a license file, they must contact the Enterprise License Center, ELC. The opening hours for ELC are from Sunday evening till Saturday morning CET. The email address for ELC is [email protected]. When a reseller has a problem with the license Web application or a license file, they must contact the partner where they have service support.

39

Chapter 4 Pre-Installation
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 PBX 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 System Guide MD110 Customer Library SQL Server Books Online (BOL)

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 (IT Dept. 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.

PBX Hardware Requirements

Each PC running Extension Manager, Operator Workstation or Performance Data Manager (PDM) must be connected to the PBX. Extension 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 PBX that will be connected to PCs running Extension Manager and Performance Data Manager.

41

Pre-Installation

Dynamic Network Administration Technical Guide

Note: For Ericsson IP-PBX, since only Ethernet connection is available, use NIU for connection option in EMG/MDS. Extension Manager, MD Support, and Performance Data Manager can optionally utilize Access Agent devices for extended communications. For MD110, -BC12.1 and above are supported. BC9 is only available for synchronization from MD Support (not for Extension Manager or Performance Manager).

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. 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 D.N.A. client applications are all installed on a single PC, and there are no connected PCs used to run applications. The standalone PC is set up as both the server and the client for all applications. Single node vs. multi-node Each D.N.A. installation can support one node or multiple nodes. Both network and stand-alone installations can be set up as single node or multi-node.

Stand alone
The following diagram represents a stand-alone installation of an Operator Work Station together with Directory Manager.

42

Dynamic Network Administration Technical Guide

Pre-Installation

The stand-alone PC contains Microsoft Windows (Windows 2000 Server or Windows Server 2003), 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 Clients

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 accounting application.

43

Pre-Installation

Dynamic Network Administration Technical Guide

The D.N.A. Server contains Microsoft Windows (Windows 2000 Server or Windows Server 2003), 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 PBX is necessary to transmit diversion information. All other communication is done through the clients. The Extension Manager and Performance Manager Clients communicate with the PBX via the same physical interface: Extension Manager to make adds, moves and changes in the PBX, Performance Manager to set up measurements in the PBX. Updates of the Extension Manager or Performance Manager Database are transferred from the PBX to the Client and from there to the server database. The call data records (CDRs) are transferred to the Client running the call accounting application via V.24 (as shown in this illustration) or via TCP/IP. 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.).

PC Hardware Requirements
This section lists basic hardware requirements for D.N.A. server and client PC installations of up to 500 extensions and < 1000 directory size.

Server
Each PC that will be configured as a D.N.A. server should meet the following requirements. This recommendation includes D.N.A. server, DME server, Ericsson Communication Assistant (ECA) server, and ECC server. For larger installations, more memory and faster CPU may be required for satisfactory operation (dependent upon specific D.N.A. installation). Component PC/CPU Memory Minimum Requirement Pentium IV, 2.4 Ghz (or better) 128 Mbytes RAM

Operating System Windows 2000 Server or Windows Server 2003 Monitor and Card 1024 x 768 monitor and video card resolution Mouse CD-ROM COM Ports Microsoft-compatible two-button mouse. Required for server PC only. Communications port requirements are based on which applications will be installed. A DigiBoard or COM port adapter may be used if additional

44

Dynamic Network Administration Technical Guide

Pre-Installation

COM ports are needed. For Event Manager, only ports COM1-COM4 are supported. Printer Ports Sound Board 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).

Speakers

Specific Requirements
Platform 1 COM port/PBX (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 PBX connection (if using serial interface) Not applicable if D.N.A. Access Agent or Ethernet connection is used. Database size: 6 Mbytes/PBX. 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 (PDM). Not applicable if the D.N.A. Access Agent or NIU 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.

DMG

EMG

OWS

PMG

Client PC
Each PC that will be configured as a D.N.A. client should meet the following requirements. This recommendation includes PMG, DMG, EMG, ECC, OWS and OWS Supervisor. For larger installations with larger directory size and merging of the directory, more RAM is required for the OWS client machine.

45

Pre-Installation

Dynamic Network Administration Technical Guide

Component PC/CPU Memory

Minimum Requirement Pentium III, 800 Mhz (or better) 256 Mbytes RAM (or better)

Operating System Windows 2000 Professional/Server, Windows XP Professional, or Windows Server 2003 Monitor and Card Mouse CD-ROM COM Ports 1024 x 768 monitor and video card resolution Microsoft-compatible two-button mouse. N/A Required for server PC only. Communications port requirements are based on which applications will be installed. For Event Manager, only ports COM1-COM4 are supported. IEEE-488 parallel port for printer (LPT1). OWS client (recommended for Visually Impaired option). OWS client (recommended for Visually Impaired option).

Printer Ports Sound Card Speakers

Specific requirements
Platform DMG EMG No specific requirements. No specific requirements. 1 COM port for PBX connection (for serial interface). Not applicable if the D.N.A. Access Agent or Ethernet connection is used. 1 COM port for CT adapter. 1 COM port for OWS keyboard (optional). 1 COM port for PBX connection (PDM). Not applicable if the D.N.A. Access Agent or NIU is used.

OWS

PMG

46

Dynamic Network Administration Technical Guide

Pre-Installation

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.

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 the best reliability, Ericsson recommends that you use the Windows NT File System (NTFS). NTFS has proven to be more stable than the FAT/FAT32. If you are supporting a large system requiring data redundancy, you may use any of Windows RAID software implementations. However, if you choose to employ a hardware RAID solution, make sure it is on the Windows 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 D.N.A. Server 60 MB for executable executable size files 200 MB for client installation and other files DNACOMMONDAT 4 MB 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 N/A N/A Memory map Log Files files (1MB / 1000) x Total extensions on all nodes x 15 [See D.N.A. Server note]

12 N/A MB/1000 subscriber s

47

Pre-Installation

Dynamic Network Administration Technical Guide

Application Customer Information Files Directory Manager

Executable SQL Database colors N/A Customer dependent

Caching for GUI Execution N/A N/A N/A

9 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)] DIRDBLOG -for fewer than 200 subscribers = [25 MB] -For more than 2000 subscribers = [25 MB + 1MB/200 x (number of subscribers - 2000)]

[1.5 MB + 4.6 N/A KB x No. of subscribers]

Extension Manager

14 MB

EMGDBDAT = 6 MB x no. of Nodes + total extension on all nodes / 100 x 3 MB

1 MB per 17 KB x No. 1000 of Nodes subscriber EMGDBLOG = 4 MB x no. s of Nodes + Total extension of all nodes/100 x 2 MB [See note (2)] N/A 6 MB/1000 N/A subscriber s 1 MB/1000 subscriber s

0.6 MB x No. of Nodes [See Extension Manager note]

Operator Workstation Performance Manager

7 MB

7 KB per logged-in User ID Archive files - 4 MB per node per month Logs - 2 MB per node

5.5 MB

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 the number of Active Measurements (e.g., 30-40 = base size x 2) 50-60 = base size x 3

Ericsson 15 MB Communicatio

12 MB/1000

48

Dynamic Network Administration Technical Guide

Pre-Installation

Application n Assistant

Executable SQL Database

Caching for GUI Execution subscriber s (share with ECC if co-exists)

Ericsson 6.5 MB Communicatio n Client Mobile Executive 28 MB 12 MB/1000 subscriber s (share with ECA if co-exists)

PPM Lite Notes 4.6 installation Notes 5.0 installation Notes 6.0 installation

14 MB 16 MB 30 MB 7 MB

*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. 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.

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. 5.4 installation program.

49

Pre-Installation

Dynamic Network Administration Technical Guide

Application

Executable

SQL Database Caching for GUI Execution Local DB Memory map files Log Files N/A N/A

D.N.A. Server

(EXE 24.5 MB) (installation files - 18 MB)

N/A*

N/A

Photos

N/A

N/A

N/A

N/A

N/A

Directory Manager

9 MB

N/A

N/A

[1.5 MB + 4.6 KB x N/A No. of subscribers]

Extension Manager

14 MB

N/A

1 MB per 1000 17 KB x No. of subscribers nodes

0.6 MB x No. of nodes [see Extension Manager note]

Ericsson 37 MB Communication Client Operator Workstation Performance Manager Notes 4.6 Notes 5 Notes 6 7 MB N/A 6 MB/1000 subscribers 1 MB/1000 subscribers N/A 7 KB per logged-in User ID 2 MB per node

5.5 MB

N/A

5 MB 5 MB 5 MB

*N/A = does not apply Note - 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.

50

Dynamic Network Administration Technical Guide

Pre-Installation

Software Requirements
Windows
The following are supported: ! ! Windows 2000 (with Service Pack 4), Windows XP Professional (with Service Pack 2), and Windows Server 2003 (with Service Pack 1). Microsoft SQL Server " 2005 Xpress Engine, Microsoft SQL Server " 2000 (with Service Pack 4), MSDE 2000 (with Service Pack 4), Microsoft SQL Server 2005 and Microsoft SQL Server 2005 Express Edition.

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. Also, if you are running D.N.A. on a Windows 2000 machine, please see the service advice 2003-08-11 D.N.A. 5.0 Hot Fix 802 (Windows 2000 SP4) before upgrading to Windows 2000 SP4.

SQL Server
D.N.A. applications use Microsoft SQL Server 2005, Xpress Engine, Microsoft SQL Server 2000 (with Service Pack 4), MSDE 2000 (with Service Pack 4), Microsoft SQL Server 2005 or Microsoft SQL Server 2005 Express Edition. If a database application does not exist on the server, the D.N.A. application suite installation program prompts you to choose between SQL Server 2000 Desktop Engine and Microsoft SQL Server 2000 for Simplified Chinese, and among SQL Server 2000 Desktop Engine, Xpress Engine, Microsoft SQL Server 2000,or Microsoft SQL Server 2005 for General Latin.

Excel
If you are installing Performance Presentation Manager, Excel 2003, Excel 2000 with SP3 or Excel 2002 with SP2 or later, it 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, Ericsson Communication Assistant, Mobile Executive, ECC Server and Personal Assistant must be installed on a server containing Microsoft Internet Information Server (IIS 5.0 for Windows 2000, or IIS 6.0 for Windows Server 2003). PPM Lite and Ericsson Communication Assistant work with Internet browsers Microsoft Internet Explorer 5.5 or later, or Netscape 4.x, 6.x, or 7.x. Warning: PPM Lite will not function properly without a session state. The Session Timeout feature for your PPM Lite website must not be disabled.

51

Pre-Installation

Dynamic Network Administration Technical Guide

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 Adapter (R6A or higher) between the client PC and the MD110, and an 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. 2. Connect the operator telephone (a D3 phone, for example) to the "PHONE" jack on the CT Adapter. 3. Connect the CT Adapter to an available COM port on the PC using an RS232 cable. 4. Follow MD110 instructions to initialize the ELU port for the Operator Workstation. 5. If a headset is used, set up the headset based on the headset installation guide. 6. If the optional Traffic Keyboard is available, connect it to an available COM port on the PC.

Server/MD110 Connection for Operator Workstation

If you use the Operator Workstation Message Diversion or Message Waiting features, 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.

52

Dynamic Network Administration Technical Guide

Pre-Installation

Direct/Local Connection

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.

Client/ MX-ONE Telephony Server Connections for Operator Workstation

The Operator Workstation connects to the MX-ONE Telephony Server via an Ethernet network connection for call traffic handling. The media data from the MX-ONE Telephony Server is not terminated at the Operator Workstation. Instead, the media data terminates at a D4 Phone with specialized firmware module (OMD).

53

Pre-Installation

Dynamic Network Administration Technical Guide

To connect an Operator Workstation client PC to Telephony Server

1. Select the Signaling channel as Network in the PBX Operator Console Configuration 2. Enter the PBX Server Name or IP address and the TCP Port of the MXONE Telephony Server. 3. Connect the Operator Media Device (OMD) in the LAN. Provide the Telephony Server and the Software server IP address in the Network setting of the OMD phone. 4. Close the OWS application and launch it again. 5. Operator Extension logon dialog is prompted after OWS is logged in. Provide the Operator Extension and password defined in the Telephony Server to register the OWS Application. 6. Logon the OMD phone with the same extension and password. OMD phone is also registered in the Telephony Server.

Server/ MX-ONE Telephony Server Connection for Operator Workstation

The following figures show cable connections for a direct connection between the server PC and the Telephony Server. Local Connection

Configuration Management Hardware Connections

The D.N.A. Application Suite contains the following configuration Management applications. ! ! ! MD110 Support Extension Manager Performance Data Manager (supports MD110 only)

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, and an Ethernet connection in the Ericsson IP-PBX. These connections can be shared with other applications connecting to the MD110/Ericsson IP-PBX.

54

Dynamic Network Administration Technical Guide

Pre-Installation

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, the client PC is connected to a TAU or modem that connects to a TAU or modem on the MD110. For Ericsson IP-PBX, only Ethernet connection is supported, so the option selected in EMG/MDS must be NIU. The following schematics show connection configurations for direct and remote communication.

55

Pre-Installation

Dynamic Network Administration Technical Guide

Hardware Connections for Extension 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, and an Ethernet connection in the Ericsson IP-PBX. These connections can be shared with other applications connecting to the MD110/Ericsson IP-PBX. 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, the client PC is connected to a TAU or modem that connects to a TAU or modem on the MD110. For Ericsson IP-PBX, only Ethernet connection is supported, so the option selected in EMG/MDS must be NIU. The following schematics show connection configurations for direct and remote communication.

56

Dynamic Network Administration Technical Guide

Pre-Installation

57

Chapter 5 SQL Installation

SQL Server 2005
Before installing SQL Server 2005, we recommend that you review the "ReadmeSQL2005.htm" and "RequirementsSQL2005.htm" sections prior to installing this release. Important! When installing SQL Server 2005 for the D.N.A. Application Suite, it is recommended you do the Custom installation and select Dictionary Order, case-sensitive for the Sort Order. When installing SQL Server 2005 from a network drive, do not use a Universal Naming Convention (UNC) file path such as:
!

\\<Servername>\Servers\ setup.exe

Instead, map a drive to the appropriate location and run the Setup program from the drive letter, for example:
!

F:\Servers\setup.exe

To install SQL Server 2005

1) Use Setup.exe to install SQL Server 2005 from a network drive or CD-ROM. 2) If Microsoft SQL Server 2005 installation is started on a Win 2000 server, make sure to first install Windows Installer 3.1. The setup will be available at F:\ Servers\redist\Windows Installer\ 3) When Microsoft SQL Server 2005 setup starts up, it will detect if the pre-requisites are installed. If not installed, setup will install the pre-requisites, such as .NET Framework 2.0. 4) From the autorun dialog, click Run the SQL Server Installation Wizard. 5) On the End User License Agreement page, read the license agreement, and then select the check box to accept the licensing terms and conditions. Accepting the license agreement activates the Next button. To continue, click Next. To end Setup, click Cancel. 6) On the SQL Server Component Update page, Setup installs software required for SQL Server 2005. For more information about component requirements, click the Help button at the bottom of the page. To begin the component update process, click Install. To continue after the update completes, click Finish. 7) On the Welcome page of the SQL Server Installation Wizard, click Next to continue. 8) On the System Configuration Check (SCC) page, the installation computer is scanned for conditions that may block Setup. For information about configuration check items, click Help at the bottom of the page or see Check Parameters for the System Configuration Checker. 9) On the Registration Information page, enter information in the Name and Company text boxes. To continue, click Next.
59

SQL Installation

Dynamic Network Administration Technical Guide

10) On the Components to Install page, select the components for your installation. A description for each component group appears in the Components to be Installed pane when you select it. To install individual components, click Advanced. Otherwise, click Next to continue. 11) If you clicked Advanced on the previous page, the Feature Selection page is displayed. On the Feature Selection page, select the program features to install using the drop-down boxes. To install components to a custom directory, select the feature and then click Browse. 12) On the Instance Name page, select a default or named instance for your installation. 13) On the Services Accounts screen, select the Use the Local System account option and click Next >. 14) On the Character Set/Sort Order/Unicode Collation screen, select Dictionary order, casesensitive from the Sort Order drop-down list and click Next >. 15) On the Authentication Mode page, choose the authentication mode to use for your SQL Server installation. You must also enter and confirm a strong password for the sa login. To proceed, click Next. 16) Click Next > on the Start Copying Files screen to proceed. 17) When the installation completes, click Exit on the Microsoft SQL Server options page.

Upgrading to SQL Server 2005

Upgrading from Microsoft SQL Server version 7.0 to Microsoft SQL Server 2005 is one of the basic choices offered by the SQL Server 2005 setup. Upgrade is possible when SQL SP4 is applied over SQL Server 7.0.

Security
For security reasons, you should change the default sa Login ID and blank password of MS SQL Server. 1) In the Service Manager window, open the registered D.N.A. Servers tree and the Logins tree. 2) Double-click on sa to open the Manage Logins dialog box. 3) 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.

Memory
SQL Server 2005 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.

60

Dynamic Network Administration Technical Guide

SQL Installation

5) In the memory box, select maximum size (MB), and slide it to the desired position.

Upgrade from MSDE to SQL Xpress Engine

Upgrading from MSDE to Microsoft SQL Xpress Engine requires Windows Installer 3.1 and .NET Framework 2.0 as the pre-requisites.

SQL Server 2000

Upgrading from Microsoft SQL Server version 7.0 to Microsoft SQL Server 2000 is one of the basic choices offered by the SQL Server Setup program on the initial Installation Selection screen. When you select the option to Upgrade, remove, or add components to an existing installation of SQL Server, Setup detects your current installation and initiates the correct sequence of setup screens for the upgrade selected. Upgrade variations include: ! ! ! ! ! A complete installation upgrade from SQL Server 7.0 to SQL Server 2000 (installing over SQL Server 7.0) Adding components to an installation of SQL Server 2000 An upgrade to the feature set of an existing installation of SQL Server 2000 (edition and component upgrade) An upgrade to SQL Server 2000 from SQL Server version 6.5 using the SQL Server Upgrade Wizard An online database upgrade of SQL Server 7.0 databases to SQL Server 2000 database format using the Copy Database Wizard

During the upgrade from SQL Server 7.0, external packages, such as Microsoft Management Console and the Microsoft Distributed Transaction Coordinator, must be installed for each upgrade, and the Registry updated. The Master database and other system databases are upgraded in various ways involving a series of scripts run on the server with specific options. If the upgrade process fails, built-in recovery mechanisms restart and resume the upgrade.

Upgrade
To upgrade from SQL Server 7.0 to SQL Server 2000
1. Use AUTORUN.EXE to upgrade to SQL Server 2000 from a network drive or CD-ROM. 2. Select SQL Server 2000 Components on the Microsoft SQL Server 2000 Enterprise Edition screen. 3. Select Install Database Server on the Install Components screen. 4. Click Next > on the Welcome screen. 5. Click Next > on the Computer Name screen to accept the default Local Computer option. 6. Select the Upgrade, remove, or add components to an existing installation of SQL Server option and click Next >. 7. Click Next > on the Instance Name screen. 8. Click Next > on the Existing Installation screen to accept the default Upgrade your existing installation option.

61

SQL Installation

Dynamic Network Administration Technical Guide

9. Check Yes, upgrade my SQL Server Tools and data on the Upgrade screen and click Next >. 10. On the Connect to Server screen, select the Authentication Mode setup should use to connect to SQL Server and click Next >. 11. Click Next > on the Start Copying Files screen to proceed. 12. Use the Choose Licensing Mode dialog box to set up the Licenses. The choices you make here depend on the type of SQL Server license the customer has purchased. When finished, click Continue to start the installation. 13. Click Next > on the Microsoft Data Access Components 2.6 Setup screen to shut down the tasks in the Task list. 14. When setup completes the installation of Microsoft Data Access Components 2.6, click Finish to begin the installation. 15. Click Finish on the Setup Complete screen to complete setup. 16. Install SQL Server 2000 Service Pack 3a

New Installation
Important! When installing SQL Server 2000 for the D.N.A. Application Suite, it is recommended you do the Custom installation and select Case-sensitive for the Sort Order.

To install SQL Server 2000

1. Use AUTORUN.EXE to install SQL Server 2000 from a network drive or CDROM. 2. Select SQL Server 2000 Components on the Microsoft SQL Server 2000 Enterprise Edition screen 3. Select Install Database Server on the Install Components screen 4. Click Next > on the Welcome screen 5. Click Next > on the Computer Name screen to accept the default Local Computer option 6. Click Next > on the Installation Selection screen to accept the default Create a new instance of SQL Server, or install Client Tools option. 7. Enter your Name and Company in the edit boxes on the User Information screen and click Next > 8. On the Software License Agreement screen, read the agreement, and select Yes to accept the license agreement and proceed. 9. Click Next > on the Installation Definition screen to accept the default Server and Client Tools option 10. Click Next > on the Instance Name screen to use the Default if this is the first instance of SQL Server 2000. Enter a unique instance name if this is not the first instance on this server. 11. Select Custom on the Setup Type screen and change the desired destination if desired 12. Click Next > on the Select Components screen to accept the default Components and Sub-Components

62

Dynamic Network Administration Technical Guide

SQL Installation

13. On the Service Account screen, select the Use the Local System account option for Service Settings. 14. On the Authentication Mode screen, select the Mixed Mode (Windows Authentication and SQL Server Authentication) option. Enter a password or check the Blank Password option (assigning a password is highly recommended). 15. On the Collation Settings screen, select SQL Collations option and Dictionary order, case-sensitive, for use with 1252 Character Set for all languages except Chinese. For Chinese, select Collation designator and Chinese_PRC. Check Case sensitive and uncheck Accent sensitive for Sort order. 16. Click Next > on the Network Library screen to accept the default settings 17. Click Next > on the Start Copying Files screen to proceed 18. Use the Choose Licensing Mode dialog box to set up the Licenses. The choices you make here depend on the type of SQL Server license the customer has purchased. When finished, click Continue to start the installation. 19. Click Next > on the Microsoft Data Access Components 2.6 Setup screen to shut down the tasks in the Task list 20. When setup completes the installation of Microsoft Data Access Components 2.6, click Finish to begin the installation. 21. Click Finish on the Setup Complete screen to complete setup 22. Install SQL Server 2000 with Service Pack 3a

Unattended SQL Server Installation

Unattended SQL Server installation is convenient if you want to install several SQL Servers with identical configurations. The Setup program reads the installation settings from a pre-defined installation information file instead of prompting in the SQL Server installation wizard. If a database application does not exist on the server, the D.N.A. application suite installation program prompts you to choose between SQL Server 2000 Desktop Engine and Microsoft SQL Server 2000 for Simplified Chinese, and SQL Server 2000 Desktop Engine, SQL Xpress Engine, Microsoft SQL Server 2000, or Microsoft SQL Server 2005 for General Latin. If you select SQL Server, you are asked for the SQL Server CD key, setup files, and the location of the installation information file (*.iss). 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 the recommended options for the SQL Server Enterprise edition. The following language settings are used in these files. General Latin Dictionary order, case-sensitive, for use with ISO code page 1252 character set. Simplified Chinese Dictionary order, case-sensitive, for use with Simplified Chinese code page 936 character set.

63

SQL Installation

Dynamic Network Administration Technical Guide

If you need to create your own *.iss file you can find a text file "SQL2000_Collation_Name.txt" located on the installation CD under \dna\DBEngineInstall. This file contains all SQL collation names and you can use it as reference if another SQL Collation is preferred than the predefined ones.

Install SQL Server 2005 Standard Edition Unattended

A pre-defined SQL Server configuration template is provided for customers who use SQL Server 2005 Standard Edition. The template setup_std_template.ini is located at installation CD \dna\DBEngineInstall\MSSQL2005\Configurations. Please follow the procedures below to use it. 1) Copy setup_std_template.ini to a system on the network that can be accessed by D.N.A Server installation. 2) Modify setup_std_template.ini a) b) Add your SQL Server CD key at line PIDKEY=xxxx xxxx xxxx xxxx.. This step is mandatory Specify the SQL Collation in the section SQLCOLLATION = SQL_Latin1_General_Cp1_CS_AS_KI_WI

During D.N.A Server installation 3) At the Database Application Selection dialog box, select Microsft SQL Server 2005. 4) At the Database Application Installation Configuration dialog box, enter (or browse for) the destination path of SQL Server files. Enter (or browse for) the location of the SQL Server installation files. Enter the location of your SQL Server configuration file. This is where the modified setup_std_template.iss with your SQL CD key is defined. Leave SQL Server CD Key as blank. Note: A hard-coded password, Ericsson123 is assigned to the sa login in setup_std_template.ini, because sa login should never have a blank password (for security reasons). You should change this password at your earliest opportunity. Please refer to Change SQL SA password for details.

Install SQL Server 2000 Standard Edition Unattended

A pre-defined SQL Server configuration template is provided for customers who use SQL Server 2000 Standard Edition. The template setup_std_template.iss is located at installation CD \dna\DBEngineInstall\MSSQL2000\Configurations. Please follow the procedures below to use it. 1. Copy setup_std_template.iss to a system on the network that can be accessed by D.N.A. Server installation. 2. Modify setup_std_template.iss a. Add your SQL Server CD key at line CDKey= xxxxx-xxxxx-xxxxx- xxxxxxxxxx. This step is mandatory.

64

Dynamic Network Administration Technical Guide

SQL Installation

b. Windows code page 1252 character set with Dictionary order, and casesensitive is used in the template (defined at line collation_name= SQL_Latin1_General_CP1_CS_AS). If another SQL Collation is preferred, you can use "SQL2000 Collation_Name.txt" located on the installation CD \dna\DBEngineInstall. This file contains all SQL collation names. 3. During D.N.A. Server installation: 4. At the Database Application Selection dialog box, select Microsoft SQL Server 2000. 5. At the Database Application Installation Configuration dialog box, enter (or browse for) the destination path of SQL Server files. Enter (or browse for) the location of the SQL Server installation files. Enter the location of your SQL Server configuration file. This is where the modified setup_std_template.iss with your SQL CD key is defined. Leave SQL Server CD Key as blank. Note: A hard-coded password, Ericsson is assigned to the sa login in setup_std_template.iss, because sa login should never have a blank password (for security reasons). You should change this password at your earliest opportunity. Please refer to Change SQL SA password for details.

Change SQL SA password

For security reasons, you should never have a blank password for the sa login. If you install SQL Server 2000 or MSDE 2000 through D.N.A. 5.4 installation, a hard-coded password Ericsson is assigned to the sa login. If you install SQL Server 2005 or SQL Xpress Engine through D.N.A 5.4 installation a hard-coded password Ericsson123 is assigned to the sa login. You should change this password at your earliest opportunity. If SQL Server is already installed and blank password is used, you should change it. If 2005 is used you can use SQL Server Management Studio or if SQL Server 2000 is used, you can run Enterprise Manager to change the password. You can also do it via command line as below. If SQL Xpress Engine or MSDE 2000 is used, you can only do it via the command line. 1. Run cmd 2. Launch osql by typing osql /U sa /P <sa password> and hit the <Enter key> to take you into osql 3. If sa has no password set, enter EXEC sp_password NULL, <sa new password>, sa -orIf sa has password set such as Ericsson, type EXEC sp_password <sa old password such as Ericsson>, <sa new password>, sa and hit the <Enter> key 4. Enter go and hit the <Enter> key 5. Type exit and hit the <Enter> key to close osql

65

SQL Installation

Dynamic Network Administration Technical Guide

Note: If you use D.N.A. DBCP utility for database backup, you must run DBCP to backup your databases again after sa password change. This is because backup files created with the old sa password cannot be restored with the new sa password.

Install SQL Server Service Pack

If you are using SQL Server 2000, or MSDE 2000 installed by D.N.A. 5.0 or 5.1, you must install the SQL Server Service Pack as described below. Only MSDE 2000 installed via D.N.A. 5.2, 5.3 or 5.4 installation can skip this step because the latest SQL Server service pack is already included. ! SP4 for SQL Server 2000 ! You must download SQL Server 2000 SP4 from the Microsoft download site. 1. <http://www.microsoft.com/sql/downloads/2000/sp4.asp> 2. Select a language the from Full Download drop-down and press Go 3. At the bottom of the Microsoft SQL Server 2000 Service Pack 4 page, click sql2ksp4 to download the package. 4. Unpack the package by clicking the downloaded package, sql2ksp4. 5. Shutdown all Ericsson Services and other processes connected with SQL Server 6. Double click \<sql2k sp4 package destination>\X86\setup\setupsql.exe and follow the wizard to install the service pack. 7. Reboot the system after service pack is installed ! SP4 for MSDE 2000 1. Shutdown all Ericsson Services and other processes connected with SQL Server 2. Run cmd 3. Launch setup by entering:
<cd drive>\dna\DBEngineInstall\DesktopEnging2000\ setup.exe /upgradesp SQLRun SECURITYMODE=SQL

-orDouble click the batch file:

<cd drive>\dna\DBEngineInstall\DesktopEnging2000\ Install_MSDE2000_SP4.bat

4. Reboot system after the service pack is installed. Note: D.N.A. database files must be deleted manually after MSDE removal. The MSDE un-installation process only removes the databases installed at MSDE installation time, such as Master database. All databases created later must be removed manually.

66

Dynamic Network Administration Technical Guide

SQL Installation

SNMP Master Agent

Windows 2000
1. Open the Control Panel by selecting Start!Settings!Control Panel. 2. Open the Add/Remove Program Properties dialog box by double-clicking on Add/Remove Windows Components. 3. Scroll down to Management and Monitoring Tools. 4. Click this line once (dont click in the checkbox). 5. Click the Details button. A new dialog-box appears. 6. Find the line Simple Network Management Protocol, click in the checkbox to enable it and click the OK button. 7. Click the Next > button; Windows 2000 will now start to install this component. After a few seconds the Insert disk message box is opened. 8. 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. 9. Click OK to continue the process. 10. When the Windows Component Wizard is displayed, click the Finish button. 11. This returns you to the Add/Remove Windows Components dialog box. 12. Click Close. 13. Close the Control Panel. 14. Click Start!Programs!Administrative Tools!Services. 15. In the right pane, find the line SNMP Service, right-click and choose Properties. 16. The SNMP Service Properties dialog box is opened. This dialog-box has seven tabs. Click the Agent tab. 17. 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. 18. Click the Traps tab. 19. Enter public as the community name and click the Add button next to it. 20. 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. 21. Click the Add button. 22. Click the Security tab. 23. 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. 24. Click OK to save these settings. Remember to stop and re-start the SNMP service to make the settings active.

67

SQL Installation

Dynamic Network Administration Technical Guide

68

Chapter 6 D.N.A. Installation

About Installation
Before installing D.N.A. application software, be sure all PCs and PBX 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 CDROM drive.

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 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.

69

D.N.A. Installation

Dynamic Network Administration Technical Guide

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 customer identity along with all software and hardware components to be included in this installation. Customer: Hardware Server: _____________________________________________ _____________________________________________ _____________________________________________ _____________________________________________ Software D.N.A.: Software PBX: _____________________________________________ _____________________________________________ Responsible Contact: _____________________________________________

Number of client PC's: _____________________________________________ Installation Eng. D.N.A.: _______________________________________ Installation Date: _____________

Installation Component Verification

"

Windows 2000 Server/Advanced Server/Datacenter Server + SP 4, -orWindows Server 2003, Standard or Enterprise. Windows 2000 Professional + SP 4 -or- Windows XP Professional + SP 2 Windows SQL Server 2005 Microsoft Xpress Engine Microsoft SQL Server 2000 + SP 4 Microsoft SQL Server 2000 Desktop Engine + SP 4 D.N.A. Access Agent: Base System Version R___ V__.__.__ Date: ______________

" " " " " "

Note: Microsoft SQL Server or MSDE can be installed by D.N.A. Installation.

Installation Product Identification

Product ID Windows Server __________________ Product ID Windows Workstation: __________________, __________________, __________________, __________________, __________________, __________________, Product ID SQL SERVER: Product ID (D.N.A. Server): Product ID DMG: __________________, __________________, __________________,

70

Dynamic Network Administration Technical Guide

D.N.A. Installation

Product ID OWS: Product ID PMG: Product ID EMG:

__________________, __________________, __________________,

Windows is a trademark# of Microsoft Corporation.

Application Suite Installation

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. 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. MD110 D.N.A. runs on the following Microsoft Windows operating systems. ! ! ! ! ! Windows 2000 Professional Windows XP Professional Windows 2000 Server Windows 2000 Advanced Server Windows Server 2003, Standard or Enterprise

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.

Installation Features
New installation features for D.N.A. include: ! Customizable System $ The application licenses must be enabled through Enterprise License Manager 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 defines users and privileges and configures the node information and communication with the PBX. The desired user-defined fields for Directory Manager will also be defined. Application licenses are enabled through Enterprise License Manager. Note: The pre-configured system does not support the configuration of communication with the Ericsson IP-PBX. ! 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.)

71

D.N.A. Installation

Dynamic Network Administration 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.

User Names and Privileges

There are two types of users that 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.

PBX Data Synchronization

After installation has completed successfully and the system is rebooted, the system will be automatically logged on with the system user and password you defined. The synchronization of PBX 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. Note: Data that can be synchronized are different between the MD110 and the Ericsson IP-PBX.

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.

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=domain UserName=user

72

Dynamic Network Administration Technical Guide

D.N.A. Installation

Password=123456 ;sample of MDS remote connection with phone number specified. ASB501Release=8(BC10),9(BC11),or 10(BC12.1) [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. ASB501Release=8(BC10),9(BC11),or 10(BC12.1) [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. ASB501Release=8(BC10),9(BC11),or 10(BC12.1) [MDSConfiguration3] Enable=1 ConnectionType=TELNET TelnetSetup1=195.150.112.120,4,,, TelnetSetup2=195.150.101.182,3,agent,password, SiteName=Test Telnet NIU_Password=HELP IPU_Password=1HELP NIULoginUserName=MDUSER ASB501Release=8 [GICIPortConfiguration1] Enable=1 PortName=test direct ConnectionType=DIRECT DNFillerCharacter=@ InformationSystemID=00 MaxDNLength=5 MaxTerminalID=2

73

D.N.A. Installation

Dynamic Network Administration Technical Guide

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.150.113.98 TelnetAccount=abcd TelnetPassword=test OutputTimeDelay=100 DNFillerCharacter=64 InformationSystemID=00 MaxDNLength=8 MaxTerminalID=2 [UserPrivileges] Enable=1 tstusr=test user;test user description;USER;MDS,1,2,3;PCOPI 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

74

Dynamic Network Administration Technical Guide

D.N.A. Installation

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

Upgrading To D.N.A. 5.4

This information only applies to customers with existing D.N.A. systems already installed. If you are doing a new installation from the CD containing D.N.A. 5.4, you will not need to upgrade your system. To apply D.N.A. 5.4 to your existing D.N.A. system you will need to upgrade using the new CD containing D.N.A. 5.4. There are basically two different environments of older D.N.A. systems. 1. D.N.A. 4.1 / 5.0 / 5.1 running on either SQL Server 7.0 or MSDE 2. D.N.A. 5.0 / 5.1 running on SQL Server 2000 or MSDE 2000 For any scenario it is strongly recommended to backup the older system before starting the upgrade.

Methodology to upgrade the environments is as follows:

Upgrading from D.N.A. running on SQL Server 7.0 or MSDE

1. Upgrade SQL Server. Upgrade SQL Server 7.0 to 2000 or SQL Server 7.0 to 2005 or upgrade MSDE to MSDE 2000 or MSDE to Microsoft Xpress Engine or keep the database engine that the system is currently using. This step is optional. 2. If running on Windows NT, upgrade your operating system to Windows 2000 Server or Windows 2003. 3. Upgrade D.N.A. ! Upgrade the existing D.N.A. system to 5.4.

Transferring D.N.A. from one computer to another

If your existing D.N.A. installation is running on an older hardware platform there might be a need to transfer the complete system from one computer to another.

Upgrade D.N.A. Server and SQL Server on your current D.N.A. Server computer
The upgrading of SQL Server and D.N.A. should always be carried out on the computer that is currently running the D.N.A. system. If you later want to move your D.N.A. installation from one computer to another, you must ensure that the two computers are on the same network and are able to use named pipe connections between them.

75

D.N.A. Installation

Dynamic Network Administration Technical Guide

Install the new D.N.A. 5.4 system

Next, install a new D.N.A. 5.4 system on your new machine. Use SQL Server 2005 or 2000, Windows 2000 Server, or Windows 2003, but install with the same number of extensions, sites and extensions per site as the old system. Also set the PMG database settings identical to the old system. Note: After the D.N.A. Server has been installed, a full PBX synchronization is required.

Transfer the databases

Finally, use the D.N.A. dbcp tool to backup the databases to flat files. Move the files from the old system to your new and use the dbcp tool to restore data from files to the database engine you are using at the new system. Reboot the PC after restoring the databases.

Upgrade D.N.A. clients

Do not forget to load any available service packs or hot fixes for Windows, SQL Server or D.N.A. When done, test the applications on the server computer and finally upgrade the clients.

Installing Enterprise License Server

A new license server Enterprise License Server will be used for D.N.A. 5.4. D.N.A. Application Suite Server installation will launch the Enterprise License Server if an older version of D.N.A. is detected.

Enterprise License Server Installation Wizard

This table lists the screens and prompts displayed when you perform an upgrade. Wizard Screen and Options Enterprise License Manager Installation Welcome Choose License Server Auto-discover license server(s) Manually specify a host Install license server locally Explanation D.N.A. Application Suite installation launches Enterprise License Manager installation. Click Next > to continue. Choose your license server host among three options. Choose Auto-discover to list all the Enterprise license servers in your network. You can also specify the host that contains a license server and also define the port number. The third choice is to install license server on the local machine. This screen is displayed when Auto-discover is selected. All the hosts on the network that contain the license server will be displayed. The server with permanent license will be list first.

Auto-discovering license servers

76

Dynamic Network Administration Technical Guide

D.N.A. Installation

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 Ericsson Communication Assistant, Mobile Executive, PPM Lite, Ericsson Personal Assistant, Lotus Notes, and Outlook Integration), and all administrative tools on your Windows Server PC. Windows Workstation client PCs may then connect to this server to install D.N.A. applications and support utilities.

Auto-Run Installation
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. ! ! ! ! ! ! ! ! ! ! ! ! Install Application Suite Install Ericsson Communication Assistant Install Lotus Notes Integration 4.6 Install Lotus Notes Integration 5.0 Install Lotus Notes Integration 6.0 Install PPM Lite Install Mobile Executive Install ECC Server Install Ericsson Personal Assistant View Technical Guide View Release Notes Exit

Taskbar Installation
Use this procedure to install from the CD-ROM on a PC that does not support auto-run. 1. Insert the installation CD. 2. Click Start, Run on the Windows taskbar. 3. Type the network path to the desired setup program (for example, installing from CD, type: d:\dna\setup.exe. Alternatively, 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.

77

D.N.A. Installation

Dynamic Network Administration Technical Guide

New Server Installation

IE 5.0 required for SQL Server 2000 or desktop engine 2000
If you are going to use the embedded SQL Server installation from within the D.N.A. installation program please make sure that the prerequisites for installing SQL Server 2000 or SQL Server 2000 Desktop Engine are met. This includes having Internet Explorer 5.0 or later installed.

MDAC 2.8 required

When MDAC 2.8 is not installed on the Windows computer, the Question message box is displayed. Click Yes if the following pre-requisites are met. ! Windows 2000 and IE 5 or later D.N.A. installation (both Server and Client) will install MDAC 2.8 if it is not found. However, the system must have right version of IE installed before MDAC can be installed properly.

Server Installation Wizard

This table lists the screens and prompts displayed when you perform a new installation. Wizard Screen and Options Welcome Explanation Overview of what the installation will accomplish, instructions for closing other applications, copyright warnings. 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. This screen is displayed only when SQL Server is not installed.

Installation Type Server Client

Database Server Language Collation General Latin Simplified Chinese Database Application

If installation cannot detect a database engine and General Latin was selected on the Database Server

78

Dynamic Network Administration Technical Guide

D.N.A. Installation

Wizard Screen and Options Selection

Explanation

Language Collation screen, this page is displayed. You must have licensed SQL Server if you choose SQL Server 2000 Desktop the Microsoft SQL Server option. Microsoft SQL Server 2000 Desktop Engine or MSDE is provided by Engine the D.N.A. Installation. SQL Xpress Engine Microsoft SQL Server 2000 Microsoft SQL Server 2005

Database Application Selection

This page is displayed when the installation cannot detect SQL Server and Windows Server 2003 or Simplified Chinese was selected on the Database SQL Server 2000 Desktop Server Language Collation screen. You must have a licensed SQL Server if you choose the Microsoft SQL Engine Server option. Microsoft SQL Server 2000 Desktop Microsoft SQL Server 2000 Engine is provided by the D.N.A. Installation.

Database Application Installation Configuration Enter or browse for the destination of SQL Server files. The default is the MSSQL7 directory on the OS drive. Enter or Browse for the location of the SQL Server Installation Files (not displayed of you chose Desktop setup files. Engine of MSDE) Enter the location of the SQL Server configuration file. Destination Path 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.

CD Key (not displayed of you chose Desktop Engine of MSDE) User Information Registration Confirmation Database Application Administrator Password Enter your name and company. Click Yes if the registration is correct. Enter a password for the Database Administrator (sa) account if desired. If the D.N.A. installation program installed MSDE or MSDE 2000 for you the password will be blank.

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 Number of Nodes (drop-down installation. You may change these options. list) Nodes and Extensions for Database

79

D.N.A. Installation

Dynamic Network Administration Technical Guide

Wizard Screen and Options Total Number of Extensions (drop-down list) Select Installation Method

Explanation

Choose Typical to install all available D.N.A. components (applications, databases, and D.N.A. Server support utilities and components). Choose Custom to select specific components to install.

Typical

Custom Select Components This screen is displayed when you select Custom on the Select Installation Method page. Check the components you want to install in the list. This screen is displayed when running a Custom Installation. Select the language of your choice from the list. The Typical Installation automatically installs English, and local support if the Regional Settings of the PC are supported. Note: In EMG application the phone layout will still be displayed in English. A French version is available on the CD under the directory (\dna\locale\Emg\French\DEF\French). When installation has completed you can copy these files locally to directory (DNA_S\EMG\DEF). 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.

Locale Support

OWS Level Selection Professional Basic Centrex Extension Per Node Performance Manager Databases Setup

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.

DNA PreConfiguration Option 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.

80

Dynamic Network Administration Technical Guide

D.N.A. Installation

Wizard Screen and Options

Explanation

Choose Destination Location Click Next > to accept the default folder for your installation, or click the Browse button to select another. Data Files and Log Files Locations RDS Scheduled Jobs Start Copying Files Accept or choose locations for D.N.A. SQL database components. Use this screen to change the location of Log and Data files if desired. Select or unselect tasks that will be scheduled for automated execution after the installation completes. 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. D.N.A. Application Suite installation launches Enterprise License Manager installation. Click Next > to continue. Choose your license server host among three options. Choose Auto-discover to list all the Enterprise license servers in your network. You can also specify the host that contains a license server and also define the port number. The third choice is to install license server on the local machine.

Enterprise License Manager Installation Welcome Choose License Server Auto-discover license server(s) Manually specify a host Install license server locally Auto-discovering license servers

This screen is displayed when Auto-discover is selected. All hosts on the network that contain the license server will be displayed. The server with permanent license will be listed first. After the installation has finished, this screen 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

81

D.N.A. Installation

Dynamic Network Administration Technical Guide

Installation Options
At any time after D.N.A. server software has been installed, you may use the Auto-Run or Taskbar installation methods to add, re-configure, and remove components using the following options. Option Add Components Explanation Allows you to add D.N.A. components not already installed. Installs new language capabilities to installed components. Note: In EMG application the phone layout will still be displayed in English. A French version is available on the CD under the directory (\dna\locale\Emg\French\DEF\French). When installation has completed you can copy these files locally to directory (DNA_S\EMG\DEF). 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 Control Panel.) Allows you to change the number of nodes, extensions, and other capacity parameters for the existing installation.

Install Locale

Reinstall

Remove All

Resize Database

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.

82

Dynamic Network Administration Technical Guide

D.N.A. Installation

Resize Database
You will encounter the following dialog boxes when resizing D.N.A. components in an existing installation. On the Ericsson Setup dialog box, select Resize Database. ! ! ! ! ! ! ! ! ! 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.

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 you are installing an instance of D.N.A. Client on Windows XP, refer to D.N.A. Client Installation on Windows XP.

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. ! ! ! ! ! ! ! ! ! ! Install Application Suite Install Ericsson Communication Assistant Install Lotus Notes Integration 4.6 Install Lotus Notes Integration 5.0 Install Lotus Notes Integration 6.0 Install PPM Lite Install Mobile Executive Install ECC Server Install Ericsson Personal Assistant View Technical Guide

83

D.N.A. Installation

Dynamic Network Administration Technical Guide

! !

View Release Notes Exit

1. Select Install Application Suite. 2. 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 auto-run. 3. If you are installing from a network location, connect to it. If you are installing from CD-ROM, insert the installation CD. 4. Click Start, Run on the Windows taskbar. 5. 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). Alternatively, use the Browse button to browse to the appropriate setup.exe program file. 6. Click the Client installation option button and follow the instructions from the installation wizard.

New Client Installation

MDAC 2.8 required for Windows 2000
When MDAC 2.8 is not installed on the Windows computer, the Question message box is displayed. Click Yes if the following pre-requisites are met. ! Windows 2000 and IE5 or later D.N.A. installation (both Server and Client) will install MDAC 2.8 if it is not found. However, the system must have right version of IE installed before MDAC can be installed properly.

Client Installation Wizard

This table lists the Screens and prompts displayed when you perform a new installation. Wizard Screens and Options Welcome Explanation Overview of what the installation will accomplish, instructions for closing other

84

Dynamic Network Administration Technical Guide

D.N.A. Installation

Wizard Screens and Options

Explanation applications, copyright warnings.

Installation Type Server Client

This screen is displayed when you install from the CD. Choose whether the PC you are setting up will be a D.N.A. Server or Client. The client installation places selected applications in a \\dna_c directory and assigns the connected server as the local server. Enter your name and company. Click Yes if the registration is correct. This screen is displayed when installing from a CD. Enter 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 the same version of D.N.A. you are installing and all the components you need to install.

User Information Registration Confirmation D.N.A. Server Name

Select Installation Method Choose Typical to install all the components installed on the server. Choose Custom to select specific components installed on the server. Custom Select Components This screen is displayed when you select Custom on the Select Installation Method page. Check the components you want to install in the list. This screen is displayed when running a Custom Installation. Select the language of your choice from the list. The Typical Installation automatically installs English, and local support if the Regional Settings of the PC are supported. Note: In EMG application the phone layout will still be displayed in English. A French version is available on the CD under the directory (\dna\locale\Emg\French\DEF\French). When installation has completed you can copy these files locally to directory (DNA_S\EMG\DEF).

Typical

Locale Support

85

D.N.A. Installation

Dynamic Network Administration Technical Guide

Wizard Screens and Options OWS Level Selection Professional Basic Centrex Choose Destination Location

Explanation 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 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 screen 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

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 to add, re-configure, and remove components using the following options. 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 Add Components Install Locale Explanation Allow you to add D.N.A. components not already installed. Installs new language capabilities to installed components. Note: In EMG application the phone layout will still be displayed in English. A French version is available on the CD under the directory (\dna\locale\Emg\French\DEF\French).

86

Dynamic Network Administration Technical Guide

D.N.A. Installation

When installation has completed you can copy these files locally to directory (DNA_C\EMG\DEF). Reinstall Repeats the latest installation to restore missing files and / or settings. Deletes all installed D.N.A. components. (You may also perform this task using Add/Remove Programs from the Windows Control Panel.)

Remove All

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.

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 Statement [SETUP] 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_T You must include the '/Q' switch to run YP.EXE, /Q, /C:"setup ADO in quiet mode.

87

D.N.A. Installation

Dynamic Network Administration Technical Guide

dnasuite.ini Statement /QNT",WAIT [OWS] Install=1 Level=Professional

Notes

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* * You can only install components that have been installed on the connected D.N.A. Server.

[DMG] [PMG] [EMG]

Install=1 Install=1 Install=1

Installation Procedure
At the client PC, the installer performs the following steps. 1. From the taskbar and click Start, Programs, Command Prompt. The Command Prompt window will be displayed. 2. To get command prompt help, type: command SETUP /? 3. 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

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 Notes

SETUP.EXE silent ini=[full path You can only install components of dnasuite.ini] that have been installed on the connected D.N.A. Server. SETUP.EXE silent reinstall Parameter ini=filename.ini is not needed. The setup will process using the current installed .ini file settings.

Re-install

88

Dynamic Network Administration Technical Guide

D.N.A. Installation

You can only install components that have been installed on the connected D.N.A. Server. Add Components SETUP.EXE silent add ini=[full Setup will add components that path of dnasuite.ini] have been flagged Install=1 You can only add components that have been installed on the connected D.N.A. Server.

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 website must not be disabled.

Installing with Auto-Run

D.N.A. provides auto-run support for PCs that support that feature. The installation process is automatically started when you insert the software installation CD into an auto-run compatible PC. The system will display an installation panel containing the following auto-run options. ! ! ! ! ! ! ! ! ! ! ! ! Install Application Suite Install Ericsson Communication Assistant Install Lotus Notes Integration 4.6 Install Lotus Notes Integration 5.0 Install Lotus Notes Integration 6.0 Install PPM Lite Install Mobile Executive Install ECC Server Install Ericsson Personal Assistant View Technical Guide View Release Notes 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 applications.

89

D.N.A. Installation

Dynamic Network Administration 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. Find and run the ppmlite\setup.exe program to start the installation. 3. Proceed through the Welcome dialog. 4. For New Virtual Directory, accept the PPM Lite IIS default, or type another choice. 5. 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. Note: Installing application files to Inetpub\wwwroot is not allowable, per Microsofts recommendation. 1. 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. Deletes all installed PPM Lite components. (You may also perform this task using Add/Remove Programs from the Windows Control Panel.)

Remove All

Upgrade PPM Lite

Only one upgrade option is available. Select this option to upgrade to PPM Lite version 5.2 from version 4.1, 5.0, or 5.1. You will get a warning message to inform you that the application files will be moved to a new location instead of \Inetpub\wwwroot and you will be prompted to choose a desired destination. This change is subject to the recommendation of the latest version of Microsoft IIS. PPM Lite uses D.N.A. security starting from PPM Lite 5.0. The user account needs to be recreated through User Configuration if you are upgrading from PPM Lite 4.1.

90

Dynamic Network Administration Technical Guide

D.N.A. Installation

Post Installation
Secure PPMLite Date/Time Format
The PPMLite date/time format is based on System Default Locale setting where PPMLite is installed. To secure the PPMLite date / time format, place PPMLite.dll in an MTS / COM+ package with a fixed user identity. Please follow the procedures below to setup PPMLite.dll as an MTS/COM+ package. 1. Log on the system where PPMLite is installed with the account that PPMLite.dll component will run under. 2. Configure the desired system default locale. Configure the locale for the user to be the same as the system default. Note: The locale for the system default and the local user must be the same. 3. Launch Component Services. Access Component Services via: Start!Settings!Control Panel!Administrative Tools!Component Services

4. Create a new COM+ application for PPMLite via the COM Application Install Wizard

91

D.N.A. Installation

Dynamic Network Administration Technical Guide

5. Right-click on COM+ Application | select "New Application" to start the COM application install wizard | select "Create an empty application" | click Next >.

6. Enter "PPMLite" for Server Application and click Next >.

92

Dynamic Network Administration Technical Guide

D.N.A. Installation

7. Select "This user" and enter the account name and password. PPMLite will use the system default locale settings for this particular account. Note: If IIS 6.0 is used, select the User identity that PPMLitePool is running under. Refer to PPMLite Installed on IIS 6.0 for more information.

93

D.N.A. Installation

Dynamic Network Administration Technical Guide

8. Click Finish 9. Create a new component for PPMLite via COM Component Install Wizard 10. Select the newly created COM+ Application "PPMLite" | Right-click the Component | Select New!Component to start the wizard | click Next >.

94

Dynamic Network Administration Technical Guide

D.N.A. Installation

11. Select Import component(s) that are already registered and click Next >.

95

D.N.A. Installation

Dynamic Network Administration Technical Guide

12. Import the PPMLite.CRegAPI and PPMLite.WebReports and then click Next >.

13. Finally, click Finish.

PPMLite Installed on IIS 6.0

PPMLite is installed on the same machine as D.N.A. Server
Note: Please also reference Configurations to Run D.N.A. Web Applications in Worker Process Isolation Mode in the Configuration section. Run PPMLite under a separate application pool and user identity 1. Create a custom user identity ! Create a new user such as EricssonWeb account. This account can be used for other Ericsson Web applications as well. ! Add the EricssonWeb account to the Users and IIS_WPG account groups on the PPMLite server. 2. Create a custom Application Pool ! In the IIS Manager, right-click on Application Pools, select New, then Application Pool ! A pop-up dialog will appear, prompting you for the application pool ID. Use a name such as PPMLitePool and select the first radio button that uses the default settings. 3. Customize the Application Pool

96

Dynamic Network Administration Technical Guide

D.N.A. Installation

! Right-click on PPMLitePool and select Properties ! In the Recycling tab, un-check "Recycle worker processes" ! In the Performance tab, un-check "Shutdown worker process after being idle for 20 minutes and check Enable CPU monitoring (to Max). For CPU use 100, and refresh CPU usage in 5 minutes increments. ! In the Identity tab, select the second radio button (Configurable) and specify the custom user identity that was created earlier in step 1. Enter the assigned password and click OK. You will then be asked to reconfirm the password. Enter the password and click OK again. ! Verify that the application pool has been started by refreshing the IIS Manager view (i.e., click on the Action menu and then Refresh). A started application pool will have an icon with green arrows overlaid on top. A pool that has not been started will have a red x overlaid on top of the icon (possible cause could be that an incorrect password was entered). Please ensure it is running properly. 4. Assign PPMLite Virtual Directory to Application Pool ! In the IIS Manager under the PPMLite virtual directory, right-click and select Properties. Under the Virtual Directory tab, in the Application Settings section, select the PPMLitePool option from the Application Pool dropdown list. 5. Assign Anonymous Identity Virtual Directory ! ! Go to the Directory Security tab. Under the Authentication and access control section, click Edit. An Authentication Methods dialog will appear. Check the Enable anonymous access checkbox and enter the EricssonWeb user created in step 1. Enter a valid password, and also ensure that the bottom checkboxes are unchecked.

! Click OK until all dialog boxes have disappeared 6. Create COM+ Package for PPMLite.dll if not created yet. If created already, proceed to step 6. Note: Reference previous section, Ensure PPMLite Date/Time Format for information on how to setup PPMLite.dll as a COM+ package. ! In the Control Panel under Administrative Tools, open the Component Services MMC snap-in. ! In the left hand tree, open: Component Services!Computers!My Computers!COM+ Applications ! Right-click on COM+ Applications and select New ! Follow the Wizard instructions and click Create an Empty Application ! Enter a name such as PPMLite, and keep the 2nd radio button selected (Server Application). Click Next >. ! For the application identity, select the This User: option and enter the user account and password that was created earlier in step 1, into the edit boxes. Click Next >. ! In the Roles section, click the Add Role button. ! Enter a new role name, such as PPMLite Role. Click OK!Next >.

97

D.N.A. Installation

Dynamic Network Administration Technical Guide

! Proceed to step 7 7. Add EricssonWeb user to Role ! In the Control Panel under Administrative Tools, open the Component Services MMC snap-in. ! In the left hand tree, open: Component Services!Computers!My Computers!COM+ Applications!PPMLite!Role ! Right-click on Role and select New!Role >. ! Enter the role name, such as PPMLite Role, and click OK. ! In the left hand tree, open: PPMLite Role!Users ! Right-click on Users and select New!User > ! Add the EricssonWeb user to the PPMLite Role and click OK 8. Set modify/write directory permission for the EricssonWeb user ! Set the root of your Windows drive to give modify/write access to the EricssonWeb user. This is done in Windows Explorer by right clicking on the drive, selecting Properties, selecting the Security tab, then adding EricssonWeb to the list with modify/write privileges. 9. Reset IIS ! Go to command prompt and execute iisreset to stop and restart IIS.

PPMLite is installed on a different machine than D.N.A. server

Note: Please also reference D.N.A. Server and IIS 6.0 Server on Different Machines in the Configuration section. Run PPMLite under a separate application pool and under a domain user. 1. Create a domain user account ! PPMLite will need to access data on the D.N.A. server, which means PPMLite needs to be properly authenticated on the D.N.A. server with a domain user account. ! Add this domain user to the IIS_WPG account group on the PPMLite server. 2. Create a custom Application Pool ! In the IIS Manager, right-click on Application Pools, select New, then Application Pool ! A pop-up dialog will appear, prompting you for the application pool ID. Use a name such as PPMLitePool and select the first radio button that uses the default settings. 3. Customize the Application Pool ! Right-click on PPMLitePool and select Properties ! In the Recycling tab, un-check "Recycle worker processes" ! In the Performance tab, un-check "Shutdown worker process after being idle for 20 minutes and check Enable CPU monitoring (to Max). For CPU use 100, and refresh CPU usage in 5 minutes increments.

98

Dynamic Network Administration Technical Guide

D.N.A. Installation

! In the Identity tab, select the second radio button (Configurable) and specify the domain user account that was created earlier in step 1. Enter the assigned password and click OK. You will then be asked to reconfirm the password. Enter the password and click OK again. ! Verify that the application pool has been started by refreshing the IIS Manager view (i.e., click on the Action menu and then Refresh). A started application pool will have an icon with green arrows overlaid on top. A pool that has not been started will have a red x overlaid on top of the icon (possible cause could be that an incorrect password was entered). Please ensure it is running properly. 4. Assign PPMLite Virtual Directory to Application Pool ! In the IIS Manager under the PPMLite virtual directory, right-click and select Properties. Under the Virtual Directory tab, in the Application Settings section, select the PPMLitePool option from the Application Pool dropdown list. 5. Assign Anonymous Identity Virtual Directory ! ! Go to the Directory Security tab. Under the Authentication and access control section, click Edit. An Authentication Methods dialog will appear. Check the Enable anonymous access checkbox and enter the EricssonWeb user created in step 1. Enter a valid password, and also ensure that the bottom checkboxes are unchecked.

! Click OK until all dialog boxes have disappeared 6. Create COM+ Package for PPMLite.dll if not created yet. If created already, proceed to step 7. Note: Reference previous section, Ensure PPMLite Date/Time Format for information on how to setup PPMLite.dll as a COM+ package. ! In the Control Panel under Administrative Tools, open the Component Services MMC snap-in. ! In the left hand tree, open: Component Services!Computers!My Computers!COM+ Applications ! Right-click on COM+ Applications and select New ! Follow the Wizard instructions and click Create an Empty Application ! Enter a name such as PPMLite, and keep the 2nd radio button selected (Server Application). Click Next >. ! For the application identity, select the This User: option and enter the user account and password that was created earlier in step 1, into the edit boxes. Click Next >. ! In the Roles section, click the Add Role button. ! Enter a new role name, such as PPMLite Role. Click OK!Next >. ! Proceed to step 7 7. Add the domain user created in step 1 to Role ! In the Control Panel under Administrative Tools, open the Component Services MMC snap-in.

99

D.N.A. Installation

Dynamic Network Administration Technical Guide

! In the left hand tree, open: Component Services!Computers!My Computers!COM+ Applications!PPMLite!Role ! Right-click on Role and select New!Role >. ! Enter the role name, such as PPMLite Role, and click OK. ! In the left hand tree, open: PPMLite Role!Users ! Right-click on Users and select New!User > ! Add the domain user crated in step 1 to the PPMLite Role and click OK 8. Set modify/write directory permission for the domain user. ! Set the root of your Windows drive to give modify/write access to the domain user created in step 1. This is done in Windows Explorer by rightclicking on the drive, selecting Properties, selecting the Security tab, and then adding the domain user created in step 1 to the list with modify/write privileges. 9. Reset IIS ! Go to command prompt and execute iisreset to stop and restart IIS. Note: If for any reason a domain account cannot be used, please reference MSDN article 176380, How To Use ASP with a SQL Trusted Connection with Guest Account: http://support.microsoft.com/kb/176380/EN-US/

Ericsson Communication Assistant

This section explains installation requirements and procedures for the Ericsson Communication Assistant application. You can install Ericsson Communication Assistant on a D.N.A. Server or Client PC. Warning: Ericsson Communication Assistant will not function properly without a session state, and the Session Timeout feature for your website must not be disabled.

Prerequisites
The following are the requirements for Ericsson Communication Assistant.

Call Controls
! For the Call Handling license, Application Link 4 must be installed for BC 10, BC 11, and BC12. You must also install the CSTA32.dll version 4 on the ECA server. For best viewing, the PC Display settings should be set to 32K colors or higher.

Simplified Chinese on English Operating System

For Simplified Chinese, the system default language settings must be set to Chinese (PRC) if English Operating System is used on the ECA Server. Otherwise, ECA pages will not show. Perform the following steps to change system default language settings.

100

Dynamic Network Administration Technical Guide

D.N.A. Installation

Windows 2000 Server 1. Start!Settings!Control Panel!Regional Options to open the Regional Options dialog. 2. Check the Simplified Chinese checkbox for the Language settings for the system and click the Set Default button.

3. Select Chinese (PRC) from the drop-down list and then click OK.

101

D.N.A. Installation

Dynamic Network Administration Technical Guide

4. East Asian language files will be installed (if they are not already). Have the Windows installation CD available for file copy. 5. Answer Yes to restart system to make settings effective.

Windows Server 2003 1. Start!Settings!Control Panel!Regional and Language Options to open the Regional and Language Options dialog. 2. Select Chinese (PRC) for standards and formats and China for Location. Click the Advanced tab and go to step 4. If these options are unavailable, click the Languages tab to install the language files (see step 3).

102

Dynamic Network Administration Technical Guide

D.N.A. Installation

3. Select Install files for East Asian languages and click OK to install the language files. Have the Windows installation CD available for file copy. Click the Advanced tab after files are installed.

103

D.N.A. Installation

Dynamic Network Administration Technical Guide

4. Select Chinese (PRC) for Language for non-Unicode programs, check the Apply all settings to the current user account and to the default user profile checkbox, and then click OK.

5. Click OK to change the default user settings.

104

Dynamic Network Administration Technical Guide

D.N.A. Installation

6. Answer Yes to restart system and make settings effective.

Installing with Auto-Run

D.N.A. provides auto-run support for PCs that support that feature. The installation process is automatically started when you insert the software installation CD into an auto-run compatible PC. The system displays an installation panel containing the following auto-run options. ! ! ! Install Application Suite Install Ericsson Communication Assistant Install Lotus Notes Integration 4.6

105

D.N.A. Installation

Dynamic Network Administration Technical Guide

! ! ! ! ! ! ! ! !

Install Lotus Notes Integration 5.0 Install Lotus Notes Integration 6.0 Install PPM Lite Install Mobile Executive Install ECC Server Install Ericsson Personal Assistant View Technical Guide View Release Notes Exit

Select Install Ericsson Communication Assistant to install from the Auto-Run interface.

Installation Procedure
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 applications.

To install Ericsson Communication Assistant (ECA Server)

1. Insert the D.N.A. 5.4 CD-ROM into the CD drive. -orIf you're installing from a network location, connect to it. 2. Double-click eca/setup.exe to start the installation. 3. For the Database Server Name dialog, type the Windows network name of the PC containing the desired D.N.A. SQL database. 4. For the Choose Destination Location dialog, accept the default, or type another choice. Note: Installing application files to Inetpub\wwwroot is not allowable, per Microsofts recommendation. 5. After reviewing the selection, the installation program will copy files and complete the installation settings. 6. In order to display pictures on Subscriber Detail Information pages, you must make the DNA_S\MRS\Photo folder shared (read only) on the D.N.A. Server.

Virtual Machine
Ericsson Communication Assistant requires the Java Virtual Machine software on your computer. You can download it from http://java.com.

Installation Options
The Ericsson Communication Assistant 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

106

Dynamic Network Administration Technical Guide

D.N.A. Installation

corrupted files. Remove All Deletes all installed Ericsson Communication Assistant components. (You may also perform this task using Add/Remove Programs from the Windows Control Panel.)

Upgrade Ericsson Communication Assistant

Only one upgrade option is available. Select this option to upgrade to Ericsson Communication Assistant version 1.2 from version 1.0 and 1.1. For existing ECA users, some of the new enhancements in ECA 1.2 require setting up in the ECA Configuration before taking effect. 1. Show diversion notes Turn on this flag to allow ECA users to view diversion notes, if available. 2. EMG is installed and Personal Number is used Turn on this flag only if EMG is installed on the D.N.A. Server and personal number feature is used. Note that this flag must be turned on if Personal Number feature is used after upgrade to ECA 1.2 from earlier releases. Otherwise, the Personal Number feature will not be available after logon. EMG must be configured properly. If it is off, ECA will not launch EMG and retrieve Profile information from PBX at logon time. If it is on but EMG is not installed or properly defined, the ECA logon process will be slowed. Refer to Configuration for Personal Number access in the Configuration section. 3. Personal Directory Set to Exchange if Outlook contact list is available for ECA directory search. In addition, ECA users must also configure the interface parameters with the Exchange Server in the Personal Options page before the Personal Contact search option will be available. 4. Directory Name Define the desired directory name for Local D.N.A. internal and external directory. These names will be used in the ECA Directory drop-down list for search. Additionally, the LDAP directory name listed in the ECA Directory search dropdown list will be changed to LDAP description defined in LDAP configuration instead of LDAP host name. No configuration is needed.

Post Installation Only if IIS 6.0 is used

ECA is installed on the same machine as D.N.A. Server
Note: Please also reference Configurations to Run D.N.A. Web Applications in Worker Process Isolation Mode in the Configuration section. Run ECA under a separate application pool and a user identity 1. Create a custom user identity ! Create a new user such as EricssonWeb account. This account can be used for other Ericsson Web applications as well.

107

D.N.A. Installation

Dynamic Network Administration Technical Guide

! Add the EricssonWeb account to the Users and IIS_WPG account groups on the ECA server. 2. Create a custom Application Pool ! In the IIS Manager, right-click on Application Pools, select New, then Application Pool ! A pop-up dialog will appear, prompting you for the application pool ID. Use a name such as ECAPool and select the first radio button that uses the default settings. 3. Customize the Application Pool ! Right-click on ECAPool and select Properties ! In the Recycling tab, un-check "Recycle worker processes" ! In the Performance tab, un-check "Shutdown worker process after being idle for 20 minutes and check Enable CPU monitoring (to Max). For CPU use 100, and refresh CPU usage in 5 minutes increments. ! In the Identity tab, select the second radio button (Configurable) and specify the custom user identity that was created earlier in step 1. Enter the assigned password and click OK. You will then be asked to reconfirm the password. Enter the password and click OK again. ! Verify that the application pool has been started by refreshing the IIS Manager view (i.e., click on the Action menu and then Refresh). A started application pool will have an icon with green arrows overlaid on top. A pool that has not been started will have a red x overlaid on top of the icon (possible cause could be that an incorrect password was entered). Please ensure it is running properly. 4. Assign Ericom Virtual Directory to Application Pool ! In the IIS Manager under the Ericom virtual directory, right-click and select Properties. Under the Virtual Directory tab, in the Application Settings section, select the ECAPool option from the Application Pool dropdown list. 5. Assign Anonymous Identity Virtual Directory ! ! Go to the Directory Security tab. Under the Authentication and access control section, click Edit. An Authentication Methods dialog will appear. Check the Enable anonymous access checkbox and enter the EricssonWeb user created in step 1. Enter a valid password, and also ensure that the bottom checkboxes are unchecked. Click OK until all dialog boxes have disappeared

6. Reset IIS ! Go to command prompt and execute iisreset to stop and restart IIS. Note: If for any reason a domain account cannot be used, please reference MSDN article 176380, How To Use ASP with a SQL Trusted Connection with Guest Account: http://support.microsoft.com/kb/176380/EN-US/

ECA is installed on a different machine than D.N.A. server

108

Dynamic Network Administration Technical Guide

D.N.A. Installation

Note: Please also reference D.N.A. Server and IIS 6.0 Server on Different Machines in the Configuration section. Run ECA under a separate application pool and under a domain user 1. Create a domain user account ! ECA will need to access data on the D.N.A. server, which means ECA needs to be properly authenticated on the D.N.A. server with a domain user account. ! Add this domain user to the IIS_WPG account group on the ECA server. 2. Create a custom Application Pool ! In the IIS Manager, right-click on Application Pools, select New, then Application Pool ! A pop-up dialog will appear, prompting you for the application pool ID. Use a name such as ECAPool and select the first radio button that uses the default settings. 3. Customize the Application Pool ! Right-click on ECAPool and select Properties ! In the Recycling tab, un-check "Recycle worker processes" ! In the Performance tab, un-check "Shutdown worker process after being idle for 20 minutes and check Enable CPU monitoring (to Max). For CPU use 100, and refresh CPU usage in 5 minutes increments. ! In the Identity tab, select the second radio button (Configurable) and specify the domain user account that was created earlier in step 1. Enter the assigned password and click OK. You will then be asked to reconfirm the password. Enter the password and click OK again. ! Verify that the application pool has been started by refreshing the IIS Manager view (i.e., click on the Action menu and then Refresh). A started application pool will have an icon with green arrows overlaid on top. A pool that has not been started will have a red x overlaid on top of the icon (possible cause could be that an incorrect password was entered). Please ensure it is running properly. 4. Assign Ericom Virtual Directory to Application Pool ! In the IIS Manager under the Ericom virtual directory, right-click and select Properties. Under the Virtual Directory tab, in the Application Settings section, select the ECAPool option from the Application Pool dropdown list. 5. Assign Anonymous Identity Virtual Directory ! ! Go to the Directory Security tab. Under the Authentication and access control section, click Edit. An Authentication Methods dialog will appear. Check the Enable anonymous access checkbox and enter the EricssonWeb user created in step 1. Enter a valid password, and also ensure that the bottom checkboxes are unchecked.

! Click OK until all dialog boxes have disappeared 6. Reset IIS ! Go to command prompt and execute iisreset to stop and restart IIS.

109

D.N.A. Installation

Dynamic Network Administration Technical Guide

Note: If for any reason a domain account cannot be used, please reference MSDN article 176380, How To Use ASP with a SQL Trusted Connection with Guest Account: http://support.microsoft.com/kb/176380/EN-US/

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 website must not be disabled.

Installing with Auto-Run

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 Ericsson Communication Assistant Install Lotus Notes Integration 4.6 Install Lotus Notes Integration 5.0 Install Lotus Notes Integration 6.0 Install PPM Lite Install Mobile Executive Install ECC Server Install Ericsson Personal Assistant View Technical Guide View Release Notes 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 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. Find and run the MobileExec\setup.exe program. Double-click setup.exe to start the installation.

110

Dynamic Network Administration Technical Guide

D.N.A. Installation

3. Proceed through the Welcome dialog. 4. For New Virtual Directory, accept the mobileexec default for Name, or type another choice. 5. 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. Note: Installing application files to Inetpub\wwwroot is not allowable, per Microsofts recommendation. 6. 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. Deletes all installed Mobile Executive components. (You may also perform this task using Add/Remove Programs from the Windows Control Panel.)

Remove All

Upgrade Mobile Executive

Only one upgrade option is available. Select this option to upgrade to Mobile Executive version 5.2 from version 5.0 and 5.1. You will get a warning message to inform you that the application files will be moved to a new location instead of \Inetpub\wwwroot and you will be prompted to choose a desired destination. This change is subject to the recommendation of the latest version of Microsoft IIS.

Post Installation Only if IIS 6.0 is used

Mobile Executive is installed on the same machine as D.N.A. Server
Note: Please also reference Configurations to Run D.N.A. Web Applications in Worker Process Isolation Mode in the Configuration section. Run Mobileexec under a separate application pool and a user identity 1. Create a custom user identity ! Create a new user such as EricssonWeb account. This account can be used for other Ericsson Web applications as well. ! Add the EricssonWeb account to the Users and IIS_WPG account groups on the Mobileexec server.

111

D.N.A. Installation

Dynamic Network Administration Technical Guide

2. Create a custom Application Pool ! In the IIS Manager, right-click on Application Pools, select New, then Application Pool ! A pop-up dialog will appear, prompting you for the application pool ID. Use a name such as MobileexecPool and select the first radio button that uses the default settings. 3. Customize the Application Pool ! Right-click on MobileexecPool and select Properties ! In the Recycling tab, un-check "Recycle worker processes" ! In the Performance tab, un-check "Shutdown worker process after being idle for 20 minutes and check Enable CPU monitoring (to Max). For CPU use 100, and refresh CPU usage in 5 minutes increments. ! In the Identity tab, select the second radio button (Configurable) and specify the custom user identity that was created earlier in step 1. Enter the assigned password and click OK. You will then be asked to reconfirm the password. Enter the password and click OK again. ! Verify that the application pool has been started by refreshing the IIS Manager view (i.e., click on the Action menu and then Refresh). A started application pool will have an icon with green arrows overlaid on top. A pool that has not been started will have a red x overlaid on top of the icon (possible cause could be that an incorrect password was entered). Please ensure it is running properly. 4. Assign Mobileexec Virtual Directory to Application Pool ! In the IIS Manager under the Mobileexec virtual directory, right-click and select Properties. Under the Virtual Directory tab, in the Application Settings section, select the MobileexecPool option from the Application Pool dropdown list. 5. Assign Anonymous Identity Virtual Directory ! ! Go to the Directory Security tab. Under the Authentication and access control section, click Edit. An Authentication Methods dialog will appear. Check the Enable anonymous access checkbox and enter the EricssonWeb user created in step 1. Enter a valid password, and also ensure that the bottom checkboxes are unchecked. Click OK until all dialog boxes have disappeared

6. Reset IIS ! Go to command prompt and execute iisreset to stop and restart IIS.

Mobile Executive is installed on a different machine than D.N.A. server

Note: Please also reference D.N.A. Server and IIS 6.0 Server on Different Machines in the Configuration section. Run Mobileexec under a separate application pool and under a domain user

112

Dynamic Network Administration Technical Guide

D.N.A. Installation

1. Create a domain user account ! Mobileexec will need to access data on the D.N.A. server, which means Mobileexec needs to be properly authenticated on the D.N.A. server with a domain user account. ! Add this domain user to the IIS_WPG account group on the Mobileexec server. 2. Create a custom Application Pool ! In the IIS Manager, right-click on Application Pools, select New, then Application Pool ! A pop-up dialog will appear, prompting you for the application pool ID. Use a name such as Mobileexec Pool and select the first radio button that uses the default settings. 3. Customize the Application Pool ! Right-click on Mobileexec Pool and select Properties ! In the Recycling tab, un-check "Recycle worker processes" ! In the Performance tab, un-check "Shutdown worker process after being idle for 20 minutes and check Enable CPU monitoring (to Max). For CPU use 100, and refresh CPU usage in 5 minutes increments. ! In the Identity tab, select the second radio button (Configurable) and specify the domain user account that was created earlier in step 1. Enter the assigned password and click OK. You will then be asked to reconfirm the password. Enter the password and click OK again. ! Verify that the application pool has been started by refreshing the IIS Manager view (i.e., click on the Action menu and then Refresh). A started application pool will have an icon with green arrows overlaid on top. A pool that has not been started will have a red x overlaid on top of the icon (possible cause could be that an incorrect password was entered). Please ensure it is running properly. 4. Assign Mobileexec Virtual Directory to Application Pool ! In the IIS Manager under the Mobileexec virtual directory, right-click and select Properties. Under the Virtual Directory tab, in the Application Settings section, select the MobileexecPool option from the Application Pool dropdown list. 5. Assign Anonymous Identity Virtual Directory ! ! Go to the Directory Security tab. Under the Authentication and access control section, click Edit. An Authentication Methods dialog will appear. Check the Enable anonymous access checkbox and enter the EricssonWeb user created in step 1. Enter a valid password, and also ensure that the bottom checkboxes are unchecked.

! Click OK until all dialog boxes have disappeared 6. Reset IIS ! Go to command prompt and execute iisreset to stop and restart IIS.

113

D.N.A. Installation

Dynamic Network Administration Technical Guide

Note: If for any reason a domain account cannot be used, please reference MSDN article 176380, How To Use ASP with a SQL Trusted Connection with Guest Account: http://support.microsoft.com/kb/176380/EN-US/

Personal Assistant
The basic D.N.A. Server client must be installed before you can install Personal Assistant. This section explains installation requirements and procedures for Personal Assistant. Personal Assistant 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 website must not be disabled.

Installing with Auto-Run

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 Ericsson Communication Assistant Install Lotus Notes Integration 4.6 Install Lotus Notes Integration 5.0 Install Lotus Notes Integration 6.0 Install PPM Lite Install Mobile Executive Install ECC Server Install Ericsson Personal Assistant View Technical Guide View Release Notes Exit

Select Install Personal Assistant 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 applications.

To install Personal Assistant 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. Find and run the PersonalAssistant\setup.exe program. Double-click setup.exe to start the installation.

114

Dynamic Network Administration Technical Guide

D.N.A. Installation

3. Proceed through the Welcome dialog. 4. For New Virtual Directory, accept the PersonalAssistant default for Name, or type another choice. 5. 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. Note: Installing application files to Inetpub\wwwroot is not allowable, per Microsofts recommendation. 6. 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 Personal Assistant 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. Deletes all installed Mobile Executive components. (You may also perform this task using Add/Remove Programs from the Windows Control Panel.)

Remove All

Post Installation Only if IIS 6.0 is used

Personal Assistant is installed on the same machine as D.N.A. Server
Note: Please also reference Configurations to Run D.N.A. Web Applications in Worker Process Isolation Mode in the Configuration section. Run Personal Assistant under a separate application pool and a user identity 1. Create a custom user identity ! Create a new user such as EricssonWeb account. This account can be used for other Ericsson Web applications as well. ! Add the EricssonWeb account to the Users and IIS_WPG account groups on the Personal Assistant server. 2. Create a custom Application Pool ! In the IIS Manager, right-click on Application Pools, select New, then Application Pool ! A pop-up dialog will appear, prompting you for the application pool ID. Use a name such as PAPool and select the first radio button that uses the default settings. 3. Customize the Application Pool

115

D.N.A. Installation

Dynamic Network Administration Technical Guide

! Right-click on PAPool and select Properties ! In the Recycling tab, un-check "Recycle worker processes" ! In the Performance tab, un-check "Shutdown worker process after being idle for 20 minutes and check Enable CPU monitoring (to Max). For CPU use 100, and refresh CPU usage in 5 minutes increments. ! In the Identity tab, select the second radio button (Configurable) and specify the custom user identity that was created earlier in step 1. Enter the assigned password and click OK. You will then be asked to reconfirm the password. Enter the password and click OK again. ! Verify that the application pool has been started by refreshing the IIS Manager view (i.e., click on the Action menu and then Refresh). A started application pool will have an icon with green arrows overlaid on top. A pool that has not been started will have a red x overlaid on top of the icon (possible cause could be that an incorrect password was entered). Please ensure it is running properly. 4. Assign PersonalAssistant Virtual Directory to Application Pool ! In the IIS Manager under the PersonalAssistant virtual directory, rightclick and select Properties. Under the Virtual Directory tab, in the Application Settings section, select the PAPool option from the Application Pool dropdown list. 5. Assign Anonymous Identity Virtual Directory ! Go to the Directory Security tab. Under the Authentication and access control section, click Edit. ! An Authentication Methods dialog will appear. Check the Enable anonymous access checkbox and enter the EricssonWeb user created in step 1. Enter a valid password, and also ensure that the bottom checkboxes are unchecked. ! Click OK until all dialog boxes have disappeared 6. Reset IIS ! Go to command prompt and execute iisreset to stop and restart IIS.

Personal Assistant is installed on a different machine than D.N.A. server

Note: Please also reference Configurations to Run D.N.A. Web Applications in Worker Process Isolation Mode in the Configuration section. Run Personal Assistant under a separate application pool and under a domain user 1. Create a domain user account ! Personal Assistant will need to access data on the D.N.A. server, which means Personal Assistant needs to be properly authenticated on the D.N.A. server with a domain user account. ! Add this domain user to the IIS_WPG account group on the Personal Assistant server. 2. Create a custom Application Pool

116

Dynamic Network Administration Technical Guide

D.N.A. Installation

! In the IIS Manager, right-click on Application Pools, select New, then Application Pool ! A pop-up dialog will appear, prompting you for the application pool ID. Use a name such as PAPool and select the first radio button that uses the default settings. 3. Customize the Application Pool ! Right-click on PAPool and select Properties ! In the Recycling tab, un-check "Recycle worker processes" ! In the Performance tab, un-check "Shutdown worker process after being idle for 20 minutes and check Enable CPU monitoring (to Max). For CPU use 100, and refresh CPU usage in 5 minutes increments. ! In the Identity tab, select the second radio button (Configurable) and specify the domain user account that was created earlier in step 1. Enter the assigned password and click OK. You will then be asked to reconfirm the password. Enter the password and click OK again. ! Verify that the application pool has been started by refreshing the IIS Manager view (i.e., click on the Action menu and then Refresh). A started application pool will have an icon with green arrows overlaid on top. A pool that has not been started will have a red x overlaid on top of the icon (possible cause could be that an incorrect password was entered). Please ensure it is running properly. 4. Assign PersonalAssistant Virtual Directory to Application Pool ! In the IIS Manager under the PersonalAssistant virtual directory, rightclick and select Properties. Under the Virtual Directory tab, in the Application Settings section, select the PAPool option from the Application Pool dropdown list. 5. Assign Anonymous Identity Virtual Directory ! Go to the Directory Security tab. Under the Authentication and access control section, click Edit. ! An Authentication Methods dialog will appear. Check the Enable anonymous access checkbox and enter the EricssonWeb user created in step 1. Enter a valid password, and also ensure that the bottom checkboxes are unchecked. ! Click OK until all dialog boxes have disappeared 6. Reset IIS ! Go to command prompt and execute iisreset to stop and restart IIS. Note: If for any reason a domain account cannot be used, please reference MSDN article 176380, How To Use ASP with a SQL Trusted Connection with Guest Account: http://support.microsoft.com/kb/176380/EN-US/

117

D.N.A. Installation

Dynamic Network Administration Technical Guide

Outlook Integration
The D.N.A. Outlook Integration (DOI) 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. 1. Before Installation, Microsoft Outlook 2000 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. 2. Use the MD110 Support utility to synchronize Operator Message Diversion for All applications on the D.N.A. server. 3. 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. 4. Use the RDS Configuration utility to configure a GICI/CSTA Port. 5. Use the Directory Configuration Utility to add a Person UDF of type Computer to the database. 6. 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 or upgrade Outlook Integration

Double-click on DNA_S\DMG\CALENDAR\setup.exe and follow the instructions in the Setup Wizard. Note: Starting from DOI 5.2, the message diversion reason code is retrieved from Subject by default (Registry value GetDivCodeFromSubject set to 1) unless it is changed manually (GetDivCodeFromSubject set to 0). This applies to any user who adds DOI as a new installation from D.N.A. 5.4. For existing users who upgrade to 5.4, this Registry setting remains the same.

To uninstall Outlook Integration

1. Open the Control Panel and double-click on Add/Remove Programs. 2. Remove D.N.A. Integration with Outlook.

Description of DOI at Synchronization Interval

DOI relies on message diversion code to distinguish the calendar event is set from DOI or Outlook for data synchronization. ! ! When you set or delete a message diversion with DOI, this information is stored in your local calendar. When the synchronization interval occurs, DOI will determine whether the calendar entry was created via DOI or not, based on the message diversion reason code from the Subject field (default) or Body Text (determined by Registry setting). Refer to Registry Values for Message Diversion Synchronization for details.

118

Dynamic Network Administration Technical Guide

D.N.A. Installation

The message diversions from the D.N.A. server are called "Message Diversion from DNA Server." DOI will not go through these message diversions, since they are already in the D.N.A. server database. DOI then sends the message diversions to the RDS (D.N.A. server process), which in turn adds or removes them from the D.N.A. server database. The process "dnamsgdv.exe" is always assigned low priority (to avoid flickering, etc.), when starting the DOI, or at synch interval.

! !

Registry Values for Message Diversion Synchronization

Two Registry values - SynchInterval and DiversionDays are used for message diversion synchronization from Outlook to the D.N.A. Server. Registry location:
HKLM\SOFTWARE\Ericsson\Integration\Outlook\

SynchInterval. This Registry key value is used to define the data synchronization period. The DOI will poll the new changes made from Outlook and send to D.N.A. Server based on SynchInterval. By default the value is set to 120 seconds (=78 Hex value). Message Diversions from D.N.A. server are sent instantly to the DOI client and are not affected by the SynchInterval value. DiversionDays. This Registry key value is used to define the number of days future message diversion information is displayed. Outlook will retrieve this setting whenever data synchronization occurs. By default the value is set to 15 days. If the value is > 31 days, it will be treated as 31 days. If value is < 3 days, it will be treated as 3 days. The number of days includes the current day (e.g., 15 days means today plus the next 14 days). Also: GetDivCodeFromSubject. This Registry value is used to get the message diversion reason code from the Subject field if set to 1 (default); otherwise message diversion reason code is retrieved from Body Text. Regardless of Registry settings, the message diversion reason code must be at the beginning of the Subject or Body Text field. By using Body Text field, the Subject can be used for more meaningful information about the appointment. However, the performance will be better if Subject field is used. Prior to D.N.A. 5.2, the GetDivCodeFromSubject is set to 0 by default, which means that the message diversion reason code is retrieved from Body Text. Starting from DOI 5.2, the GetDivCodeFromSubject is set to 1 and reason code is retrieved from Subject field by default. For existing users, this setting remains the same after upgrade to 5.4.

Registry Value for User ID instead of Computer UDF

In the D.N.A. Server Registry, change the following key:
HKLM\SOFTWARE\Ericsson\MRS\RemoteDS\Manager\ UseUserIDForCalendarIntegration

119

D.N.A. Installation

Dynamic Network Administration Technical Guide

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 Windows user login name as the identity for Outlook calendar diversion settings. The advantage of using the Windows user login name is that it 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. 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.

Limitations for Recurrent Diversions

The RDS can handle hourly, daily and weekly message diversion. Weekly, has different interpretation in RDS compared to the Outlook Calendar. In RDS weekly means only one time per week. In Outlook, users can select multiple days during the week. Ex. 1 If a user in Outlook selects "Daily" and "Every weekday", the DOI will pass this information to the RDS as weekly with every Monday to Friday. But RDS can only accept weekly and ignore the Monday to Friday. The result of this is that; the first time it will work (e.g., Wednesday), when the message diversion has expired, the record in the D.N.A. server database will change to the next start time (i.e., Wednesday the next week). Ex. 2 If a user in Outlook selects "Weekly" and multiple days (e.g., Monday, Wednesday, Friday), only the first one will be activated (i.e., Monday). The others will not be activated on the phone. Ex. 3 If a user in Outlook selects "Monthly" or "Yearly", only the first message diversion will be activated. The others will not be activated on the phone.

Customizing Outlook Security Features

The Microsoft Outlook Security features are installed by default with Microsoft Outlook 2002 and 2003. They are used to guard against most viruses spread via attachments to e-mail messages. For DOI users, the message A program is trying to access e-mail addresses you have stored in Outlook will be displayed whenever DOI synchronization occurs due to Outlook Address Book being guarded (if Outlook Security features are installed). To prevent this caution from appearing, it is necessary to customize the security features according to the following procedure.

Install Outlook Security Features Administrative Package

Exchange Server 2003

120

Dynamic Network Administration Technical Guide

D.N.A. Installation

1. Download Outlook Security Feature Administrative Package (Admpack.exe) from http://www.microsoft.com/office/ork/xp/appndx/appc00.htm. 2. Extract the files by double clicking Admpack.exe. This package consists of the following 4 files: OutlookSecurity.oft, an Outlook template that enables you to customize the security settings on the Microsoft Exchange server. Hashctl.dll, the file for the Trusted Code control, a tool used by the template to specify trusted COM add-ins. Comdlg32.ocx, control that provides a user interface for selecting the trusted COM add-in. Readme.doc, a document that provides information on the values and settings available in the template and describes how to deploy the new settings on Exchange Server. 3. Install and Register Trusted Code controls: Copy Hashctl.dll and Comdlg32.ocx extracted from Security Feature Administrative Package to <windir>\system32 on Administrative system. Register files: Start DOS command prompt Enter regsvr32 hashctl.dll and hit Enter Enter regsvr32 Comdlg32.ocx and hit Enter Exchange Server 2000 1. Download Outlook 2000 SR-1a Security Update Administrative (Admpack.exe) from http://www.microsoft.com/office/ork/2000/appndx/toolbox.htm#secupd 2. Extract the files by double clicking Admpack.exe. This package consists of the following 3 files: OutlookSecurity.oft, a template used for creating security settings. outlk9.adm, an Auto Distribution Manager (ADM) updated system policy. Readme.txt, a document that provides information on the values and settings available in the template and describes how to deploy the new settings on Exchange Server.

Create and Configure Security Folder on Exchange Server

You must have administrator privileges to create a public folder named Outlook Security Settings on the Exchange server.

121

D.N.A. Installation

Dynamic Network Administration Technical Guide

1. Click Start ! Programs ! Microsoft Exchange ! System Manager to open the Exchange System Manager dialog.

122

Dynamic Network Administration Technical Guide

D.N.A. Installation

2. Open Folders, then right-click Public Folders and select New ! Public Folder. Create a new folder by entering Outlook Security Settings in the Name field, then click Apply, followed by the OK button in Properties dialog.

123

D.N.A. Installation

Dynamic Network Administration Technical Guide

3. Configure the newly created Outlook Security Settings public folder by rightclicking it. Select Properties to open the Outlook Security Settings Properties dialog.

124

Dynamic Network Administration Technical Guide

D.N.A. Installation

4. Select the Permission tab and then click Client Permission

125

D.N.A. Installation

Dynamic Network Administration Technical Guide

5. Define who can access the Outlook Security Setting public folder by selecting Default name, and then change the Roles from Author to Reviewer (in the Roles drop-down list). Click OK to save and close the dialog.

Modify the Default Security Settings on Microsoft Exchange Server

Microsoft Outlook is required to perform the following procedures. Use the Outlook Security template to modify settings on Exchange Server.

126

Dynamic Network Administration Technical Guide

D.N.A. Installation

1. Click OutlookSecurity.oft extracted from Security Feature Administrative Package to open the Select Folder dialog.

127

D.N.A. Installation

Dynamic Network Administration Technical Guide

2. Select Outlook Security Settings folder that created on the Exchange Server. Click OK button to open the template in Compose mode.

128

Dynamic Network Administration Technical Guide

D.N.A. Installation

3. From the menu bar, select Tools ! Forms! Publish Form As to open the Publish Form As dialog.

4. From the Look In drop-down list, select Outlook Folders and click the Browse to open the Go to Folder dialog. Select Outlook Security Settings from Public Folder and click OK.

129

D.N.A. Installation

Dynamic Network Administration Technical Guide

5. Enter Outlook Security Form in the Display Name field, and the Form Name field will be filled in with Outlook Security Form automatically. Click Publish to publish the security template in the Security Settings folder and return to the Default Security Settings Description window.

130

Dynamic Network Administration Technical Guide

D.N.A. Installation

6. Select File from the menu bar, and then click Close to close the template.

7. Click No to discard changes.

Create and Customize Outlook Security Form

Note: If Outlook 2003 is used, make sure Use Cached Exchange Mode is turned off in the E-mail Accounts. Otherwise, you cannot save the security form. You can switch back to Use Cached Exchange Mode after the security form is saved.

131

D.N.A. Installation

Dynamic Network Administration Technical Guide

1. To check or change Cached Exchange Mode: Navigate to Tools ! E-mail Accounts Ensure that the radio button next to View or change existing e-mail accounts is selected, then click Next >. Highlight your Exchange server account and then click Change. Uncheck Use Cached Exchange Mode to turn it off (i.e., disable the feature). Logon to the Exchange administrator account. 2. Expand Public Folders ! All Public Folders and select the Outlook Security Settings folder.

132

Dynamic Network Administration Technical Guide

D.N.A. Installation

3. Click the down-arrow key next to the New button on the tool bar, and then click Choose Form

4. Select Outlook Folders from the Look In drop-down box, and then click the Browse button.

133

D.N.A. Installation

Dynamic Network Administration Technical Guide

5. Select Outlook Security Settings from All Public Folders and then click OK.

134

Dynamic Network Administration Technical Guide

D.N.A. Installation

6. Verify that the Display name: field shows Outlook Security Form in the Choose Form dialog and click Open.

7. Create either a default security setting or custom settings for a specific set of users: Select Default Security Settings for All Users to allow all Outlook users to use this security form. -orSelect Security Settings for Exception Group and enter the name in the Security Group Name field. Also type the name of each user requiring the custom security settings in the Members box. The names entered must be separated with a semi-colon (;).

135

D.N.A. Installation

Dynamic Network Administration Technical Guide

8. Specify settings as follows: Automatically approve When executing a custom action via Outlook object model Automatically approve When accessing the ItemProperty of a control on an Outlook custom form

136

Dynamic Network Administration Technical Guide

D.N.A. Installation

9. Open the Programmatic Settings tab and specify the settings as follows: Automatically approve When sending terms via Outlook object model Automatically approve When accessing the address book via Outlook object model Automatically approve When accessing address information via Outlook object model Automatically approve When responding to meeting and task requests via Outlook object model Automatically approve When executing Save As via Outlook object model

137

D.N.A. Installation

Dynamic Network Administration Technical Guide

10. Save the Security Settings by selecting File from the menu bar, then clicking Save. Administrator may or may not be prompted to enter the Password for credentials depending on the Windows version used.

11. Close the Custom Security Setting dialog by selecting File from the menu bar, then clicking Close.

Deploy the Customized Outlook Security Settings to Client Systems

To enable the customized settings for users, the following Registry key is needed on the client computers.
HKCU\Software\Policies\Microsoft\Security\CheckAdminSetting

with DWORD type, and value = 1

For D.N.A. 5.4 systems with DOI installed, please re-install the D.N.A. Outlook Integration installation distributed with D.N.A. 5.2 SP1 or later, to setup this Registry key.

D.N.A. Outlook Integration Logging

D.N.A. 5.4 provides improved DOI logging. A DOI log is created daily with the file format doi_yyyymmdd.log (e.g. doi_20050524 for May 24, 2005).

To enable DOI logging

1. Set the directory for storing DOI log file in HKEY_LOCAL_MACHINE\SOFTWARE\Ericsson\Integration\Outlook\LogPat h registry value. E.g. c:\temp. 2. Set HKEY_LOCAL_MACHINE\SOFTWARE\Ericsson\Integration\Outlook\LogLev el to 1 for minimum logging, 2 for more debugging logging. Note: Any DOI log files that are older than 7 days are purged automatically when DOI starts up.

138

Dynamic Network Administration Technical Guide

D.N.A. Installation

To disable DOI logging

! Set HKEY_LOCAL_MACHINE\SOFTWARE\Ericsson\Integration\Outlook\LogPat h registry value to BLANK.

Lotus Notes Integration

Installing Lotus Notes Integration Installation package on D.N.A. Server with Auto-Run
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 Install Ericsson Communication Assistant Install Lotus Notes Integration 4.6 Install Lotus Notes Integration 5.0 Install Lotus Notes Integration 6.0 Install PPM Lite Install Mobile Executive Install Ericsson Communication Client Install Ericsson Personal Assistant View Technical Guide View Release Notes

! Exit 1. Select Install Lotus Note Integration based on the Notes version you use. 2. Proceed through the installation. The Lotus Notes Integration installation package is installed on the D.N.A. Server at \\DNA_S\MRS\InstallationFiles\ClientInstallation\LotusNotes for Notes 4.6 or \\DNA_S\MRS\InstallationFiles\ClientInstallation\LotusNotes50 for Notes 5.0 or \\DNA_S\MRS\InstallationFiles\ClientInstallation\LotusNotes60 for Notes 6.0 3. Share \DNA_S\MRS\InstallationFiles\ClientInstallation for Notes client user to install D.N.A. Lotus Notes Integration.

Installing D.N.A. Lotus Notes Integration Templates on Domino Server

Before Lotus Notes clients can use the D.N.A. Lotus Notes Integration additions, the Lotus Notes Integration template (for the installed language) needs to be placed on the Lotus Notes Domino Server.

139

D.N.A. Installation

Dynamic Network Administration Technical Guide

1. Run Lotus Notes Integration client installation on the D.N.A. Server at \\DNA_S\MRS\InstallationFiles\ClientInstallation\LotusNotes for Notes 4.6 or \\DNA_S\MRS\InstallationFiles\ClientInstallation\LotusNotes50 for Notes 5.0 or \\DNA_S\MRS\InstallationFiles\ClientInstallation\LotusNotes60 for Notes 6.0 2. Choose installation option Lotus Notes Integration Template and desired language to install D.N.A. Integration templates to Integration software on a Lotus Notes client machine into the \\\Notes\Data directory.

Setting up D.N.A. Lotus Notes Integration Templates

There are two types of templates supported: ! Sub template (support Notes 4.6, 5.0, and 6.0) For customers who have their own customized Mail form or prefer to use standard mail form, sub template should be used to link with the standard or customized Mail form. D.N.A. provided modified Mail template (support Notes 4.6 and 5.0) For customers who have no preference of the form used, the modified Mail template provided by D.N.A. can be used.

Lotus Notes 4.6

Link DNI Sub-template with Standard Mail Template or Customized Mail Template (recommended) 1. Start up Lotus Notes 2. Open standard or customized Mail template ! ! From the menu bar, choose File!Database!Open to open the Open Database dialog box.

In Filename text field, enter mail46.ntf or your customized template file name and click the Open button. 3. Open DNI template ! ! From the menu bar, choose File!Database!Open to open the Open Database dialog box.

In Filename text field, enter dni46sub.ntf or your customized template file name and click the Open button. 4. Link form: ! ! ! ! ! ! ! From the DNA Template English v4.6 window, double-click the DNA Template icon in the left frame. Click Design to list the Design pane. Click Forms to list the forms in database. From the Forms list pane (right frame), select the AbsenceCode form and choose Edit!Copy from the menu bar. From Mail (R4.6) or your customized template window, double-click on Mail (R4.6) or your customized template icon in the left frame. Click Design to list the Design pane. Click Forms to list the forms in database.

140

Dynamic Network Administration Technical Guide

D.N.A. Installation

! From the menu bar, choose Edit!Paste. 5. Link view: ! ! ! From the DNA Template English v4.6 window, click Views in the Design pane (left frame). From the Views list pane (right frame), select (DiversionCode) view and choose Edit!Copy from the menu bar. From Mail (R4.6) or your customized template window, click Views to list the views in database.

! From the menu bar, choose Edit!Paste. 6. Link sub-form: ! ! ! From DNA Template English v4.6 window, click Subforms in the Design pane (left frame). From the Sub-forms list pane (right frame), select the EricssonDNI subform and choose Edit!Copy from the menu bar. From Mail (R4.6) or your customized template window, click Subforms to list the sub-forms in database.

! From the menu bar, choose Edit!Paste. 7. Insert DNI sub-form to Calendar form: ! ! ! ! From Mail (R4.6) or your customized template window, double-click Calendar Entry form in the Forms list pane (right frame). Click the spot in the Calendar Entry form that you want the sub-form to be inserted to. From the menu bar, choose Create!Insert Subform to bring up the Insert Sub-form dialog.

Select Ericsson DNI from the Insert Sub-form list box and click the OK button to insert the selected sub-form to the Calendar Entry form. 8. The updated mail template will take effect from the next day automatically. Use D.N.A. Provided Mail Template 1. Start up Lotus Notes 2. Inherit the mail database design for each individual user from DNI template ! ! From menu bar, choose File!Database!Open to open the Open Database dialog box. Select the clients mail template (e.g., psmith.nsf for Peter Smith) and

click the Open button. The icon

will be shown on main window.

! !

Right-click the icon

and select Database Properties

to go to the Design page. Check the Click the Design icon Inherit design from template and change the Template name text field to DNI template name (e.g., "dni46(s)" for English version). 3. Repeat step 2 for all other users 4. The new template will take effect from the next day automatically.

141

D.N.A. Installation

Dynamic Network Administration Technical Guide

Lotus Notes 5.0

Link DNI Sub-template with Standard Mail Template or Customized Mail Template (recommended) 1. Start up Lotus Domino Designer 2. Copy DNA template file from local to server ! ! ! ! From menu bar, choose File!Database!Open to open the Open Database dialog box. Select Local in the Server combo-box. Click the Browse button to select the dni50sub.ntf template file. Click Open. From menu bar, choose File!Database!Open to open the Open Database dialog box.

Select the server (Server Name/Certifier, e.g., bt-inv1247/domino50) in the Server combo-box and click the OK button. 3. Open standard or customized Mail template ! ! ! From menu bar, choose File!Database!Open to open the Open Database dialog box. Select the server (Server Name/Certifier, e.g., bt-inv1247/domino50) in the Server combo-box.

Select Mail [R5.0] or your customized database in Database list box. Click the Open button. 4. Open DNI template ! ! ! From menu bar, choose File!Database!Open to open the Open Database dialog box. Select the server (Server Name/Certifier, e.g., bt-inv1247/domino50) in the Server combo-box.

Select DNA Template English v5.0 in the Database list box. Click the Open button. 5. Link form: ! ! ! ! ! Select DNA Template English v5.0 database from the Design pane (left frame). Click Forms to list the forms in database. From the Form list Work pane (right frame), right-click on the AbsenceCode form and select Copy. Select Mail [R5.0] database or your customized database from the Design pane (left frame). Click Forms to list the forms in database.

! Right-click the Form list Work pane (right frame) and select Paste. 6. Link view: ! Select DNA Template English v5.0 database from the Design pane (left frame). Click Views to list the views in database. From the View list Work pane (right frame), right-click [EricssonDiversionCode] view and select Copy.

142

Dynamic Network Administration Technical Guide

D.N.A. Installation

Select Mail [R5.0] database or your customized database from the Design pane (left frame); click Views to list the views in database. Rightclick the View list Work pane (right frame) and select Paste. 7. Link sub-form: ! Select DNA Template English v5.0 database from the Design pane (left frame). Click Resources and then click Subforms to list the sub-forms in database. From the Sub-form list Work pane (right frame), right-click EricssonDNI sub-form and select Copy.

Select Mail [R5.0] database or your customized database from the Design pane (left frame). Click Resources and then click Subforms to list the sub-forms in database. Right-click the Sub-form list Work pane (right frame) and select Paste. 8. Insert DNI sub-form to Calendar form: ! ! ! ! ! Select Mail [R5.0] database or your customized database from the Design pane (left frame) and click Forms to list the forms in database. From the Form list Work pane (right frame), double click on the Calendar Entry form to bring up the Calendar Entry form. Click the spot in the Calendar Entry form that you want the sub-form to be inserted to. From the menu bar, choose Create!Insert Subform to bring up the Insert Sub-form dialog box.

Select Ericsson DNI from the Insert Sub-form list box and click the OK button to insert the selected sub-form to the Calendar Entry form. 9. The updated mail template will take effect from the next day automatically. Use D.N.A. Provided Mail Template 1. Start up Lotus Notes 2. Copy DNA template file from local to server ! ! ! ! From menu bar, choose File!Database!Open to open the Open Database dialog box. Select Local in the Server combo-box. Click Browse button to select dni50s.ntf template file. Click Open. From menu bar, choose File!Database!New Copy to open the Copy Database dialog box.

Select the server (Server Name/Certifier, e.g., bt-inv1247/domino50) in Server combo-box and click the OK button. 3. Inherit the mail database design for each individual user from DNI template ! ! ! ! From menu bar, choose File!Database!Open to open the Open Database dialog box. Select the server (Server Name/Certifier, e.g., bt-inv1247/domino50) in the Server combo-box. Select the clients mail template (e.g., jsmith.nsf for John Smith).

to go to the Design page. Check Inherit Click the Design icon design from template and change the Template name text field to DNI template name (e.g., DNI English v5.0 for English version). 4. Repeat step 3 for all other users

143

D.N.A. Installation

Dynamic Network Administration Technical Guide

5. The new template will take effect from the next day automatically.

Lotus Notes 6.0 or 6.5

Link DNI Sub-template with Standard Mail Template or Customized Mail Template (recommended) 1. Start up Lotus Domino Designer 2. Copy DNA template file from local to server ! ! ! ! From menu bar, choose File!Database!Open to open the Open Database dialog box. Select Local in the Server combo-box. Click Browse button to select the dni60sub.ntf template file. Click Open. From menu bar, choose File!Database!New Copy to open the Copy Database dialog box.

Select the server (Server Name/Certifier, e.g., bt-inv1247/domino60) in the Server combo-box and click the OK button. 3. Open standard or customized Mail template ! ! ! From menu bar, choose File!Database!Open to open the Open Database dialog box. Select the server (Server Name/Certifier, e.g., bt-inv1247/domino60) in the Server combo-box.

Select Mail [R6] or your customized database in Database list box. Click the Open button. 4. Open DNI template ! ! ! From menu bar, choose File!Database!Open to open the Open Database dialog box. Select the server (Server Name/Certifier, e.g., bt-inv1247/domino60) in the Server combo-box.

Select the DNA Template English v6.0 in Database list box. Click the Open button. 5. Link form: ! ! ! ! ! Select the DNA Template English v6.0 database from the Design pane (left frame). Click Forms to list the forms in database. From the Form list Work pane (right frame), right-click the AbsenceCode form and select Copy. Select Mail [R6] database or your customized database from the Design pane (left frame). Click Forms to list the forms in database.

! Right-click the Form list Work pane (right frame) and select Paste. 6. Link view ! Select the DNA Template English v6.0 database from the Design pane (left frame). Click Views to list the views in database. From the View list Work pane (right frame), right-click on [EricssonDiversionCode] view and select Copy.

144

Dynamic Network Administration Technical Guide

D.N.A. Installation

Select the Mail [R6] database or your customized database from the Design pane (left frame); click Views to list the views in database. Rightclick the View list Work pane (right frame) and select Paste. 7. Link sub-form: ! Select DNA Template English v6.0 database from the Design pane (left frame). Click Shared Code and then click Subforms to list the sub-forms in database. From the Sub-form list Work pane (right frame), right-click on the EricssonDNI sub-form and select Copy.

Select the Mail [R6] database or your customized database from the Design pane (left frame). Click Shared Code and then click Subforms to list the sub-forms in database. Right-click the Sub-form list Work pane (right frame) and select Paste. 8. Insert DNI sub-form to Calendar form: ! ! ! ! ! Select Mail [R6] database or your customized database from the Design pane (left frame) and click Forms to list the forms in database. From the Form list Work pane (right frame), double click on the Calendar Entry form to bring up the Calendar Entry form. Click the spot in the Calendar Entry form where you want the sub-form to be inserted. From the menu bar, choose Create!Resource!Insert Subform to bring up the Insert Subform dialog.

Select Ericsson DNI from the Insert Subform list box and click the OK button to insert the selected sub-form to the Calendar Entry form. 9. The updated mail template will take effect from the next day automatically.

Installing D.N.A. Lotus Notes Integration on Notes Client

Before Lotus Notes clients can use the D.N.A. Lotus Notes Integration additions, the user must install Lotus Notes Integration from the D.N.A. Server 1. Run Lotus Notes Integration client installation on the D.N.A. Server at \\DNA_S\MRS\InstallationFiles\ClientInstallation\LotusNotes for Notes 4.6 or \\DNA_S\MRS\InstallationFiles\ClientInstallation\LotusNotes50 for Notes 5.0 or \\DNA_S\MRS\InstallationFiles\ClientInstallation\LotusNotes60 for Notes 6.0 2. Choose installation option Lotus Notes Client Installation and the desired language to install D.N.A. Integration software on a Lotus Notes client machine into the \\\Notes directory.

Registry Value for Message Diversion Synchronization

Two Registry values - SynchInterval and DiversionDays are used for message diversion synchronization from Lotus Notes to D.N.A. Server.

Registry location
! ! ! Notes 4.6 - HKLM\SOFTWARE\Ericsson\Integration\Lotus\ Notes 5.0 - HKLM\SOFTWARE\Ericsson\Integration\Lotus50\ Notes 6.0 - HKLM\SOFTWARE\Ericsson\Integration\Lotus60\

145

D.N.A. Installation

Dynamic Network Administration Technical Guide

SynchInterval. This Registry key value is used to define the data synchronization period. The DNI will poll the new changes made from Lotus Notes and send to D.N.A. Server based on SynchInterval. By default the value is set to 120 seconds (=78 Hex value). Message Diversions from D.N.A. server are sent instantly to the DNI client and are not affected by the SynchInterval value. DiversionDays. This Registry key value is used to define the number of days future message diversion information is displayed. LNI will retrieve this setting whenever data synchronization occurs. By default the value is set to 3 days. If the value is > 31 days, it will be treated as 31 days. If value is < 3 days, it will be treated as 3 days. The number of days includes the current day (e.g., 3 days means today plus the next two days).

COMPUTER or USER ID User Defined Fields

You need to link a User Defined Field (UDF) with DMG subscribers for Message Diversion to work with Lotus Notes Integration. The default UDF type is COMPUTER and the USER ID type is an option. When COMPUTER type is used, the extension associated with the computer name can be diverted. With this option, Lotus Notes client computers can only handle message diversions to one extension regardless of the user logged on. When USER ID type is used, the extension associated with the logged on user ID can be diverted. With this option, Lotus Notes client computers can handle message diversions for any logged on user.

To use the COMPUTER type default

1. Run the Directory Configuration utility and add an unshareable UDF of type COMPUTER to the database. 2. Run Directory Manager and add the Lotus Notes client computer name information to D.N.A. Directory.

To use the USER ID type option

1. Change the following Registry key from 0 to 1. 2. HKLM\SOFTWARE\Ericsson\MRS\RemoteDS\Manager
\UseUserIDForCalendarIntegration

3. Stop and restart the Ericsson RDS service. 4. Run the Directory Configuration utility to add a non-shareable UDF of type USER ID. 5. Run Directory Manager and add the Windows user ID information to the D.N.A. Directory.

Help
After installation to a Lotus Notes Client Machine, the D.N.A. Lotus Notes Integration User Help can be accessed using the Start menu from the same program group as D.N.A. Integration. For example: Programs!Lotus Notes!D.N.A. Integration Help

146

Dynamic Network Administration Technical Guide

D.N.A. Installation

D.N.A. Client Installation on Windows XP

When installing D.N.A. on a Windows XP client, the default read/write privilege is read only. Write privileges must be granted to users of the D.N.A. applications for the DNA_C directory. Installation of a D.N.A. client on Windows XP will fail when different languages are chosen in the settings of the Input Locales, Text Services and Input Languages dialog box (for handwriting recognition, keyboards, or speech recognition). Only one language is supported during installation, after D.N.A. is successfully installed, these settings can be changed to handle multiple languages.

Successful Configuration

After D.N.A. is successfully installed, these settings can be changed to any desired configuration. To change settings, go to the Control Panel and select Regional and Language Options. Click the Languages tab and go to Details in the Text Services and Input Languages window.

Unsuccessful Configuration
This is not an exhaustive list of unsuccessful configurations.

147

D.N.A. Installation

Dynamic Network Administration Technical Guide

1. When more than one keyboard layout is installed:

2. In some configurations with Speech Recognition (only when Office XP is installed):

148

Dynamic Network Administration Technical Guide

D.N.A. Installation

Personal Assistant for Smartphone Installation

For how to install the Personal Assistant in the Sony Ericsson P900 phone, refer to the Installation Guide, Personal Assistant for P900 EN/LZT 108 7017/2.

D.N.A. Service Pack Installation

Ericsson releases D.N.A. Service Packs according to a published schedule. D.N.A. Service Pack installation normally contains patches only. Occasionally, a D.N.A. Service Pack may be released as a media kit. You should then treat the service pack as a new minor release and ignore this section. The service pack contents will vary since service packs are not full media kits, and contains patches only. The following components may be included: ! D.N.A. Fixes for MRS, DMG, EMG, OWS, PMG, PPMLite, ECA, DME and DOI. Note: Outlook Integration is released as a full installation package but packed with the D.N.A. installation under DMG. ! Lotus Released as a full installation package, if there are changes. May include LotusNotesIntegration46, LotusNotesIntegration50, and LotusNotesIntegration60, depending upon whether there is a fix for the version supported.

149

D.N.A. Installation

Dynamic Network Administration Technical Guide

! !

ECC Released as a full installation package, if there are changes. Personal Assistant Released as a full installation package, if there are changes.

You must apply the D.N.A. Service Pack under the following circumstances: ! ! ! ! ! Add component (DMG, EMG, OWS, or PMG) to the existing D.N.A. server or client. You must reapply the service pack even it has been installed before. Add new D.N.A. client Re-install D.N.A. server or client from CD or Control Panel Re-install ECA, DME, or PPMLite from CD or Control Panel Add ECA, DME, or PPMLite to an existing D.N.A. system regardless of whether the service pack has been applied previously.

D.N.A. service packs may contain fixes for ECA, DME, and PPMLite, However, these applications come with a separate installation package on the media kit. There are two ways to upgrade them to the latest service pack after they are installed. The first method is preferred. 1. Apply serviced pack only once - Install D.N.A. server or client - Install ECA, DME, or PPMLite - Install D.N.A. service pack 2. Apply service pack twice - Install D.N.A. server or client - Install D.N.A. service pack - Install ECA, DME, or PPMLite - Install D.N.A. service pack again to apply ECA, DME, or PPMLite fixes

150

Chapter 7 ECC Installation

Server Installation
Note: To optimize performance of ECC and IP Telephony, special consideration must be given to the network setup and throughput. For additional information on network setup and network bandwidth requirements for IP Telephony, consult the document INSTALLATION PLANNING 79/1531-APD 101 02 Uen. This document is available in the MD110 online documentation.

Server Installation
The server installation is installed on the IIS server machine. It can be installed from CD-ROM or from the network. Warning: An administrator privilege is required for Server installation.

Installation Wizard
A step-by-step wizard guide is provided to help the user to go through the installation procedures. This wizard will prompt all necessary questions with default values and capture all information and the installation can then be run without an attendant.

Pre-requisites
Existence of D.N.A. Server Component
The D.N.A. Server Component is an essential component for the ECC application. This means if the D.N.A. Applications Suite server version shares the same system with IIS Server, the D.N.A. Server Component must be installed first. If D.N.A. Application Suite and IIS Server are on different systems, then the D.N.A. Server Component client version must be installed on the IIS Server first. The ECC Server installation will check the existence of D.N.A. Server Component. An error message is displayed and installation is then aborted if D.N.A. Server Component does not exist. Note: ECC requires the SYSTEM user account to set or change Personal Number. For further information, refer to Configuration for Personal Number access in the Configuration section.

Existence of IIS
The ECC Server installation will check the existence of IIS 5.0 or later. An error message is displayed and installation is then aborted if IIS 5.0 or later does not exist.

151

ECC Installation

Dynamic Network Administration Technical Guide

Installation Options
There are various installation options supported and the available installation options are detected automatically based on first time installation or if the ECC has been installed before.

New Installation
The installation program performs as a first time installation if ECC was not previously installed.

Reinstallation
This option is available if the current product version of ECC installation is detected. All necessary information is retrieved from the Registry or other sources and no question is asked. The installation program reinstalls the product and updates the system configurations accordingly. During the reinstallation process, the Ecc.cfg will not be updated in order to preserve the locale specific settings that are changed by the System Administrator. Warning: Due to a limitation with InstallShield, if the installation files are stored on a network drive, the user must map the network drive to a local drive prior to invoking the Reinstallation process. Note: If you are reinstalling and your current version is D.N.A. 5.1 or prior, there is a new Registry value that must be configured. It is contained in the configuration file ECC_Update.cfg. Please ensure that the access code for Diversion Bypass is correct (i.e., replace the value 1 with the Diversion Bypass code for your market).

Uninstall
This option is available if a current version of ECC is detected. The user is prompted for confirmation of un-installation. All the installed components (including application files, Registry keys, Registry values, etc.) are removed when confirmation has been given.

Registration Information
For the first time installation (new installation), the User Name and Company Name are prompted and information is stored in the Registry.

Virtual Directory
The installation program will detect the D.N.A. application suite location and create two virtual directories ECC and ECC_Install under it. All files including ASP pages, locales, the client web-installation program, and the installation configuration file are installed in the selected directory. The target directory is stored in the Registry.

152

Dynamic Network Administration Technical Guide

ECC Installation

ApplicationLink Configuration
The installation program will prompt the user for the ApplicationLink server name and port number (defaults to 2555) for each of the defined PBX nodes. This dialog box will also be displayed during reinstallation if there are not any nodes defined for ApplicationLink configuration. The collected information is stored in the ecc.cfg configuration file for client installation to use. Note: If you need to rename or add/remove ApplicationLink servers later, reinstall ECC Server. This will update the ApplicationLink configuration information in the ecc.cfg configuration file on the server, and the clients will automatically retrieve this updated information the next time ECC is run.

Summary Information
For a first time installation (new installation), all the user options and selections are listed for verification before copying the files and setting up the systems. The user can change the selections if desired. The installation runs without attendant after this point.

Configurations
Registry Setting
The application key \ECC is created under
HKEY_LOCAL_MACHINE\SOFTWARE\Ericsson. All the sub-keys or Registry values associated with ECC must be under the \ECC key. No Registry values are allowed under the Ericsson key directly. The same rules also apply to the other Registry hives.

The following standard Registry values are created under

HKEY_LOCAL_MACHINE\SOFTWARE\Ericsson\ECC\CurrentVersion:

! ! ! ! ! !

InstallDateServer the date that installation is performed CompanyName UserName ProductNameServer the official complete product name ProductVersion the product version number TargetDirectoryServer the target directory where application files are stored

Client Configurations
ECCClient.ini The ECC Server Name is stored in ECCClient.ini. This file is included in the ECC Client installation CAB file by repacking the CAB file during ECC server installation run time. This is to prevent the ECC client installation from querying the user for the info. Ecc.cfg

153

ECC Installation

Dynamic Network Administration Technical Guide

Some of the features in ECC require the configuration of market dependent parameters. These should be updated in the installation configuration file Ecc.cfg, to match the specific installations configuration. Be sure to only change the access code digits, and not any of the other format characters. The Ecc.cfg file will, by default, be found in the virtual directory ECC_Install, located in the default website location (\dna_s\ or \dna_c\). The options configured in Ecc.cfg will be set at each ECC client installation in the ECC client machines Windows Registry. Note that when the ECC server is re-installed, the installation program will not overwrite the existing ECC.cfg so that the changes made by the ECC administrator will be preserved. Nonetheless, the installation program will append any new parameters to the end of the ECC.cfg file. The values that must be configured include: ! AudioCodec=729 Replace the digits 729 with the appropriate selection as follows. The options are: 711: G.711 Codec 7231: G.723 Codec 729: G.729 Codec 729ab: G.729a or G.729 Codec AutoGKDiscovery = 0 Set to 1 to enable or 0 to disable the Automatic Gatekeeper Discovery option AutoGKDiscovery_Backup=0 Set to 1 to enable or 0 to disable the Automatic Gatekeeper Discovery option for the backup gatekeeper BypassDiversionFmt=*1*%s# Replace the digit 1 with the appropriate market code for the dialling procedure to bypass diversion CancelAllCallbackFmt=#6# Replace the digit 6 with the appropriate market code for the dialling procedure to cancel all callbacks CancelIndCallbackFmt=#6*%s# Replace the digit 6 with the appropriate market code for the dialing procedure to cancel individual callbacks CancelManualMsgWaitingFmt=#31# Replace the digits 31 with the appropriate market code for the dialling procedure to cancel Manual Message Waiting DNAIIS=BT-PCA This entry indicates the name of the D.N.A. IIS Server, and will be set automatically by installation. DNAServerName=BT-PCA This entry indicates the name of the D.N.A. Server, and will be set automatically by installation. Gatekeeper = 138.85.0.0 Set to the IP address of the PBX gatekeeper

! !

154

Dynamic Network Administration Technical Guide

ECC Installation

Gatekeeper_Backup=138.85.0.0 If the clients will use a backup gatekeeper, set to the IP address of the backup gatekeeper GatekeeperID=LIM1 If your installation is using Automatic Gatekeeper Discovery, replace LIM1 with the identifier for the PBX Gatekeeper to which the client will connect GatekeeperID_Backup=LIM2 If the clients will use a backup gatekeeper, and use Automatic Gatekeeper Discovery to connect to the backup gatekeeper, replace LIM2 with the identifier for the backup gatekeeper to which the client will connect. GatekeeperPollFlag=0 Set to 1 to enable polling of the gatekeeper or 0 to disable (Refer to the ECC Users Guide for more information on gatekeeper polling) GatekeeperPollRate=60 Set to the frequency rate of the polling in number of seconds. The minimum is 30 seconds. LocalAreaCode=714 Set to the local area code. When the user enters a TAPI format dialling string, ECC uses this parameter to determine if the user is making a local call or not. If the call is not local, then ECC will prepend PrefixLongDistance to the dialing string. LocalCountryCode=1 Set to the country code. When the user enters a TAPI format dialling string, ECC uses this parameter to determine if the user is making an international call or not. If the call is international, then ECC will prepend PrefixInternational to the dialing string. PortDNAIIS=80 Set to the destination port number used to access the D.N.A. IIS Server. PortCallSignal=0 This is the source port number used for H.323 call control messages. If the value is 0, a port will be assigned dynamically. Only modify this value if you need to run simultaneous H.323 clients on one machine (such as ECC and NetMeeting) and there is a conflict, or due to restrictions on your network. Note that the destination port is either set to a well-known port, 1720, or specified by the gatekeeper and its not configured by ECC. PortRAS=0 This is the source port number used to register with the gatekeeper. If the value is 0, a port will be assigned dynamically. Only modify this value if you need to select a specific port for registration due to restrictions on your network. Note that the destination port is a well-known port, 1719, designated for gatekeepers and it is not configured by ECC. PortRTP=0 This is the source port number used for voice data packets. If the value is 0, the default port will be used, which is 2326. Only modify this value if you need to select a specific port due to restrictions on your network. Note that the destination port is specified by the other party and its not configured by ECC. PrefixInternational= To have ECC automatically prepend a prefix number(s) for international calls, set this value to the appropriate prefix.

! !

155

ECC Installation

Dynamic Network Administration Technical Guide

PrefixLocal= To have ECC automatically prepend a prefix number(s) for local calls, set this value to the appropriate prefix. PrefixLongDistance= To have ECC automatically prepend a prefix number(s) for long distance calls, set this value to the appropriate prefix. ScanAdapters=0 Set this value to 1 for ECC to automatically attempt to register with the gatekeeper on all network adapters visible to ECC. If ECC fails to register with the gatekeeper on the default network adapter (the first adapter which appears in the Adapter list of the ECC Network Setup dialog), it will continue connection attempts to the gatekeeper using the other defined network adapters, until it successfully connects, or all adapters fail to connect. Note that if ECC is configured to use a specific network adapter (i.e., Use Selected Network Adapter is checked in the ECC Network Setup dialog) or if ECC is configured to use a VPN with Network Address Translation (i.e., Using VPN with Network Address Translation (NAT) is checked in the ECC Network Setup dialog, or UsingVPNwithNAT is set to 1 in the ECC.cfg configuration file), the ScanAdapters value will be ignored. StatusLog=1 Set to 1 to enable or 0 to disable the output of the Ecc.log file. The Ecc.log records all the H323 messages sent to and received from the gatekeeper. UseGatekeeper = 1 Set to 1 to enable use of the gatekeeper or 0 to disable UseGatekeeper_Backup=0 Set to 1 to enable the user of a backup gatekeeper for the user, or set to 0 to disable UsingVPNwithNAT=0 Set this value to 1 if the gatekeeper connection is made through a Virtual Private Network which includes a Network Address Translator. For more details, refer to "Using ECC with a Virtual Private Network (VPN)" in the Configuration section. VPNClientIPAddress=138.85 If the UsingVPNwithNAT flag is set, ECC will attempt to retrieve the VPN Client IP Address from the system automatically. If more than one IP address is retrieved from the system, ECC will select the first one that matches VPNClientIPAddress. Since the last octet of the VPN client IP address is likely to be changed every time when the user logs on to the VPN, it is recommended that you set up only the first 2 or 3 octets of the IP address in this variable so that the user doesnt have to update this variable constantly whereas ECC is still able to select the correct address based on this variable. For more details, refer to "Using ECC with a Virtual Private Network (VPN)" in the Configuration section. AutoAnswer=0 Set to 1 to answer incoming calls automatically or set to 0 to answer manually from incoming dialog. AutoAnswerDelay=3 Set to 3 to play ring tone for 3 sec before answering automatically using AutoAnswer option.

! !

156

Dynamic Network Administration Technical Guide

ECC Installation

! HighPriority=1 Set to 1 to run ECC with High Priority. If this option is not set, ECC runs with Normal Priority. Version.cfg A configuration file containing the version number is maintained by the installation program and stored on the ECC server. ! ! FileVersion - ECC file version number ServicePackVersion Service Pack number for About Box use

Uninstall Access
The standard uninstall access is set via Control Panel / Add Remove Program function. In addition, the uninstall may also be accessed through CD-ROM or network shared-point.

Status and Log files

All operations and transactions performed during installation procedure are recorded in a detail log file for audit trail use.

Post Installation Only if IIS 6.0 is used

ECC Server is installed on the same machine as D.N.A. Server
Note: Please also reference the Configurations to Run D.N.A. Web Applications in Worker Process Isolation Mode and D.N.A. Server and IIS 6.0 Server on Different Machines sections. Run ECC Server under a separate application pool and a different user identity 1. Create a custom user identity ! Create a new user such as EricssonWeb account. This account can be used for other Ericsson Web applications as well. ! Add the EricssonWeb account to the Users and IIS_WPG account groups on the ECC server. 2. Create a custom Application Pool ! In the IIS Manager, right-click on Application Pools, select New, then Application Pool ! A pop-up dialog will appear, prompting you for the application pool ID. Use a name such as ECCPool and select the first radio button that uses the default settings. 3. Customize the Application Pool ! Right-click on ECCPool and select Properties ! In the Recycling tab, un-check "Recycle worker processes" ! In the Performance tab, un-check "Shutdown worker process after being idle for 20 minutes and check Enable CPU monitoring (to Max). For CPU use 100, and refresh CPU usage in 5 minutes increments.

157

ECC Installation

Dynamic Network Administration Technical Guide

! In the Identity tab, select the second radio button (Configurable) and specify the custom user identity that was created earlier in step 1. Enter the assigned password and click OK. You will then be asked to reconfirm the password. Enter the password and click OK again. ! Verify that the application pool has been started by refreshing the IIS Manager view (i.e., click on the Action menu and then Refresh). A started application pool will have an icon with green arrows overlaid on top. A pool that has not been started will have a red x overlaid on top of the icon (possible cause could be that an incorrect password was entered). Please ensure it is running properly. 4. Assign ECC Virtual Directory to Application Pool ! In the IIS Manager under the ECC virtual directory, right-click and select Properties. Under the Virtual Directory tab, in the Application Settings section, select the ECCPool option from the Application Pool dropdown list. 5. Assign Anonymous Identity Virtual Directory ! Go to the Directory Security tab. Under the Authentication and access control section, click Edit. ! An Authentication Methods dialog will appear. Check the Enable anonymous access checkbox and enter the EricssonWeb user created in step 1. Enter a valid password, and also ensure that the bottom checkboxes are unchecked. ! Click OK until all dialog boxes have disappeared 6. Reset IIS ! Go to command prompt and execute iisreset to stop and restart IIS.

ECC Server is installed on a different machine than D.N.A. server

Note: Please also reference D.N.A. Server and IIS 6.0 Server on Different Machines in the Configuration section. Run ECC Server under a separate application pool and under a domain user 1. Create a domain user account ! ECC Server will need to access data on the D.N.A. server, which means ECC Server needs to be properly authenticated on the D.N.A. server with a domain user account. ! Add this domain user to the IIS_WPG account group on the ECC server. 2. Create a custom Application Pool ! In the IIS Manager, right-click on Application Pools, select New, then Application Pool ! A pop-up dialog will appear, prompting you for the application pool ID. Use a name such as ECCPool and select the first radio button that uses the default settings. 3. Customize the Application Pool ! Right-click on ECCPool and select Properties

158

Dynamic Network Administration Technical Guide

ECC Installation

! In the Recycling tab, un-check "Recycle worker processes" ! In the Performance tab, un-check "Shutdown worker process after being idle for 20 minutes and check Enable CPU monitoring (to Max). For CPU use 100, and refresh CPU usage in 5 minutes increments. ! In the Identity tab, select the second radio button (Configurable) and specify the domain user account that was created earlier in step 1. Enter the assigned password and click OK. You will then be asked to reconfirm the password. Enter the password and click OK again. ! Verify that the application pool has been started by refreshing the IIS Manager view (i.e., click on the Action menu and then Refresh). A started application pool will have an icon with green arrows overlaid on top. A pool that has not been started will have a red x overlaid on top of the icon (possible cause could be that an incorrect password was entered). Please ensure it is running properly. 4. Assign ECC Virtual Directory to Application Pool ! In the IIS Manager under the ECC virtual directory, right-click and select Properties. Under the Virtual Directory tab, in the Application Settings section, select the ECCPool option from the Application Pool dropdown list. 5. Assign Anonymous Identity Virtual Directory ! Go to the Directory Security tab. Under the Authentication and access control section, click Edit. ! An Authentication Methods dialog will appear. Check the Enable anonymous access checkbox and enter the EricssonWeb user created in step 1. Enter a valid password, and also ensure that the bottom checkboxes are unchecked. ! Click OK until all dialog boxes have disappeared 6. Reset IIS ! Go to command prompt and execute iisreset to stop and restart IIS. Note: If for any reason a domain account cannot be used, please reference MSDN article 176380, How To Use ASP with a SQL Trusted Connection with Guest Account: http://support.microsoft.com/kb/176380/EN-US/

Client Installation
The client installation is a self-extracting file that can be accessed by the user through an internet/intranet website. The user needs to go to the applicable Web page and find the package to download, extract, and begin the installation. The default virtual URL to install the ECC client is http://<EccServer>/ecc_install.

Installation Options
There are various installation options supported. The available installation options are detected automatically based on first time installation or if ECC has been installed.

159

ECC Installation

Dynamic Network Administration Technical Guide

New Installation
The installation program performs as a first time installation if there is no ECC installed before.

Reinstallation
This option is available if the current product version of ECC installation is detected. All necessary information is retrieved from the Registry or other sources and no question is asked. The installation program reinstalls the product and updates the system configurations accordingly.

Uninstall
This option is available if a current version of ECC is detected. The user is prompted for confirmation of un-installation. All the installed components (including application files, Registry keys, Registry values, program groups, short-cut keys, etc.) are removed when confirmation has been given.

License Agreement
For a first time installation (new installation), the License Agreement is displayed.

Registration Information
For a first time installation (new installation), the User Name and Company Name are prompted and information is stored in the Registry.

File Destination
For a first time installation (new installation), the default destination \Program Files\Ericsson\ECC is prompted. The user can change the target directory if

desired through the standard directory selection browsing. All files are installed in the desired directory and target directory is stored in the Registry.

Connection with ECC Server Web Site

For a first time installation (new installation), the user is prompted for the ECC server name or server IP address for server website connection. If the connection fails at startup or runtime, a message is displayed and the user is prompted to enter the server name or IP address again. The server name or IP address is stored in the Registry if connection is made successfully.

Summary Information
For a first time installation (new installation), all the user options or selections are listed for verification before copying the files and setting up the systems. The user can change the selections if desired. The installation runs without an attendant after this point.

Configurations
Registry Setting
The application key \ECC is created under
HKEY_LOCAL_MACHINE\SOFTWARE\Ericsson. All the sub-keys or Registry values associated with ECC must be under the \ECC key. No Registry values are allowed under the Ericsson key directly. The same rules also apply to the other Registry hives.

160

Dynamic Network Administration Technical Guide

ECC Installation

The following standard Registry values are created under

HKEY_LOCAL_MACHINE\SOFTWARE\Ericsson\ECC\CurrentVersion:

! ! ! ! ! !

InstallDateClient the date that installation is performed CompanyName UserName ProductNameClient the official complete product name ProductVersion the product version number TargetDirectoryServer the target directory where application files are stored

Client Configurations
All the configuration settings are retrieved from the configuration file stored on the server and then saved in the client Registry. User specific Registry values are stored in HKEY_CURRENT_USER\Software\Ericsson\ECC.

Program Group and Short-cut Keys

The program group Start!Program!D.N.A. Application Suite is created with an entry for the Ericsson Communication Client, to invoke the ECC application.

Uninstall Access
The standard uninstall access is set via Control Panel / Add Remove Program function. In addition, the un-installation can also be accessed through CD-ROM or network shared-point.

Status and Log files

All operations and transactions performed during the installation procedure are recorded in a detail log file for audit trail use.

Client Update
The client update is required to make sure the ECC user is always using the latest application.

File Version Comparison

The ECC application version number is compared between the client and server whenever the ECC application is launched. If the server version is newer, the user is prompted to update. The user can choose between Accept and Postpone. If update is accepted, the connection with the ECC Sever website is established based on the ECC server name or IP address stored in the Registry. The user is prompted for a new URL entry or it will cancel out if the connection fails.

Client Installation Download and Update

After connection with the ECC Server website is made, the user can download the new version of the self-extracting file and begin the installation. The Reinstallation option is available to update the system.

161

ECC Installation

Dynamic Network Administration Technical Guide

Compatibility
The ECC Server installation must: ! Windows 2000 Server + SP4 ! ! ! ! ! -orWindows Server 2003

Install on IIS 5.0 or 6.0 Install on D.N.A. 5.4 server or client Distribute on CD-ROM

The ECC Client installation must: ! Run on Windows 2000 + SP4 ! ! ! -orWindows XP Professional + SP2

Run with IE 5.5 or later and Netscape 4.x, 6.x, or 7.x

162

Chapter 8 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.

Creating More Available Memory

To improve performance on your PC, you can make the paging space larger by increasing your virtual memory. The ideal paging size should be twice the size of your physical memory. Before you can increase your virtual memory, you must correctly calculate the needs of your PC by using the table in the PC Hardware Requirements section. Once you have calculated the physical memory needed for your PC, you must double that amount for the virtual memory needed. For example, if you need 256 MB of physical memory for your PC, you will need 512 MB of virtual memory. Once you have your virtual memory calculated, you can enter this amount in Performance Options by completing the following steps: Open the Control Panel on your PC. Select System Properties. Select the Advanced tab. Click the Performance Options button. The Performance Options dialog box appears. 5. Under the Virtual Memory section, click the Change button. The Virtual Memory dialog box appears. 6. Enter the amount of virtual memory (for purposes of this example, it would be 512 MB) in both the Initial size (MB) field and Maximum size (MB) field. 7. Click the Set button and exit the Control Panel. 1. 2. 3. 4.

163

Performance

Dynamic Network Administration Technical Guide

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 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 ncadg_ip_udp ncadg_ipx ncacn_ip_tcp ncacn_spx ncacn_nb_nb ncacn_nb_ipx Enhanced
ncacn_ip_tcp ncadg_ip_udp ncadg_ipx ncacn_spx ncacn_nb_nb ncacn_nb_ipx

Restart the client PC for the new settings to take effect.

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.

Note: If you choose to change any of the following Registry values, you must stop and restart RDS to have the change take effect.

LDB Integrity Check Feature

There is a 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 Windows Registry key on the D.N.A. Server to 1. Stop and restart RDS to take into account the modified Registry flag.
HKLM\SOFTWARE\Ericsson\RemoteDS\Manager\VerifyLDBIndexIntegrity

164

Dynamic Network Administration Technical Guide

Performance

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 PCs. Important! The disadvantage of enabling this integrity check will be a performance degradation of the server.

Reduce I/O Completion Ports in Large Systems

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:
HKLM\SOFTWARE\Ericsson\RemoteDS\Manager\UseMultiThreadedClientConn ections

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). 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.

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:
HKLM\SOFTWARE\Ericsson\RemoteDS\Manager\EnableIncrementalLDBUpdate s

=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. Note: This setting also makes the following additional Registry key relevant:
HKLM\SOFTWARE\Ericsson\RemoteDS\Manager\LDBFastSyncFactor

The key value is used to indicate the threshold (percentage) of database change which triggers theFast LDB Synchronization process. It can be set manually or via a spin-box in the GUI.

165

Performance

Dynamic Network Administration Technical Guide

=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.

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:
HKLM\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.

166

Chapter 9 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 PBX nodes, the D.N.A. SQL server, and all D.N.A. clients (LDB). 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. Time System Server - D.N.A. Time System Server (TSS) 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. Ericsson ECA Scheduler - A Windows service that handles the Profile scheduling. It will send the MML command to the corresponding PBX via a backend component (mmliosrv.exe) to activate the profile when the scheduled time arrives. However, the Scheduler only works with up to 50 PBXs, which is the limit of the backend component.

167

D.N.A. Server

Dynamic Network Administration Technical Guide

Voice System Interface (VSI) - An ASCII protocol that provides the D.N.A. Voice System Interface to an external third party Integrated Voice Response (IVR) system. The VSI module allows voice mail integration and acts as a compatibility interface between the 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. PBX Service The PBX Service provides access and control over the signaling channel by which the PBX and OWS communicate. Although present on the D.N.A. server, it is only necessary that it run when using OWS or configuring the OWS telephone parameters. Serial Communications Server (SCS) The D.N.A. Server Utility that allows you to manage direct, Telnet, SCS, and third party serial communications port settings. Clock Synchronization Service The Clock Synchronization service (Clock Synch) sets the system clocks of client machines to match the time setting on the server. This allows all machines in the network to have their clocks set to the same value. This is particularly useful when using the Performance Data Manager, because it avoids gathering data with incorrect time stamps. Ericsson LDAP A Windows service that provides an LDAP client (i.e., an Internet browser) to search and modify the D.N.A. directory. Ericsson IP Service A Windows service that acts as an interface between Application Link and ECA to allow ECA users to access the call features such as Make call, Answer call, Hang up call, Conference call, Transfer call, Send DTMF tone, etc. 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.

168

Dynamic Network Administration Technical Guide

D.N.A. Server

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

Allows you to configure the Remote Data Server Server for D.N.A. database and application support roles, including network database synchronization between PBX nodes, the D.N.A. SQL Server, and D.N.A. Local Databases (LDBs). Provides controls for assigning and managing user descriptions and corresponding application access privileges. Server

User Configuration

TSS Configuration

Use the D.N.A. Time System Server Server Configuration Utility to set up and maintain communications and translation settings for Diversion and Message Waiting features. Use this D.N.A. Server administrative tool Server to build and maintain a list of database servers accessible on the network. The Serial Communications Server Utility Server and allows you to manage direct, Telnet, SCS, Client and third party serial communications port settings. Allows you to display D.N.A. license information. The MD110 Support Utility allows you to perform initial MD110 node configuration and data extraction for the D.N.A. OWS, EMG, PMG and applications. Server

D.N.A. Server Configuration

SCS Configuration

License Viewer

MD110 Support

Server and Client

Directory Configuration

Enables you to define the user-defined Server fields for directory database that best meet the needs of organizations they support.

169

D.N.A. Server

Dynamic Network Administration Technical Guide

Tool

How It Is Used

Installed On

LDAP Configuration The LDAP Configuration Utility enables Server 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 and ECA. LDS Configuration Allows you to setup other local database servers from one that is already configured. Server and Client

Name Identity Conversion

Use the D.N.A. Name Identity Conversion Server Utility translate subscriber directory information into MML command files for D.N.A. telephone name display. Gives D.N.A. system administrators the Server 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 Server names to incoming trunks for efficient operator identification and routing. Use the D.N.A. Voice System Voice Server System Interface Configuration Utility to set up and maintain Diversion and Message Waiting communications settings between external Voice Systems and the D.N.A. Voice System Interface (VSI). For initial population of OWS directory assistance database. Runs on D.N.A. server and selected D.N.A. client workstations. Server and Client

Operator Configuration

Trunk Manager

VSI Configuration

Directory Import

Directory Export

Use the Export Utility to create .dat text Server and files of Dynamic Network Administration Client subscriber directory databases. The .dat files can then be imported into another D.N.A. installation with the Directory Import utility.

170

Dynamic Network Administration Technical Guide

D.N.A. Server

Tool ECA Configuration

How It Is Used Used to configure the ECA server and setting up the connection to Application Link.

Installed On Server

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.

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.

171

D.N.A. Server

Dynamic Network Administration Technical Guide

Field Total Length:

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.

Alphabetic:

Numeric:

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 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 and Ericsson Communication Assistant. Use the RDS Replication tab in RDS Configuration on your D.N.A. server or LDS Configuration on your D.N.A. client.

Scheduling a Task in the RDS Configuration Utility

Security settings on each machine is different. This causes scheduled tasks not to execute. In order to resolve this issue, RDS relies on a new registry key located below to determine how to start scheduled jobs.
HKLM\SOFTWARE\Ericsson\MRS\RemoteDS\Manage\UseSAForScheduledProcess

The default value of this registry key is 0, meaning new processes will not inherent the security attribute from its parent process. When the registry key value is set to 1, the new launched schedule tasks will inherent its parent process' security information. The RDS service must be restarted after changing this registry key.

Using non-DNA extensions

172

Dynamic Network Administration Technical Guide

D.N.A. Server

In a DNA-MD110 integrated system, message diversions of only DNA users (those whose extensions are listed in DMG) can be set from the phone or any DNA application. For non-DNA users who want to use only MD110 message diversion functionality (phone diversion) manually set the key HKEY_LOCAL_MACHINE\SOFTWARE\Ericsson\MRS\RemoteDS\Manager\Igno reNonDNAExt to 1 and restart RDS service. The default value of this key is 0, i.e diversions can only be set for DNA users.

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.

LDS Servers
After a D.N.A. Client machine has been removed, the list of LDS servers in the D.N.A. Server must be updated manually by deleting the following Registry keys and restarting RDS.
HKLM\SOFTWARE\Ericsson\MRS\RemoteDS\RDSClients\NumberOfLDSClients HKLM\SOFTWARE\Ericsson\MRS\RemoteDS\RDSClients\LDS000x

RDS will rebuild these Registry keys with the correct number of LDS servers.

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. Re-run the D.N.A. installation and choose the Resize Database button on the Ericsson Setup dialog box. 2. Choose or enter new space requirements in the Nodes and Extensions for Database, Upsizing Extension Per Node, and Upsizing Performance manager Node Setup dialogs. 3. 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.

173

D.N.A. Server

Dynamic Network Administration Technical Guide

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. PBXMessage 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.

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 ondemand 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.

Short Message Service

The Short Message Service (SMS) provides the capability to transfer short messages, up to 120 characters, between Short Message Terminals and DECT Mobile Stations via a Short Message Service Center (SMSC). SMSC is connected to the MD110 (BC11 or newer) via the NIU board. The procedure to initiate an SMS involves the following 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. A generic extension is initiated. 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. A generic extension is initiated.

Prior to MX-ONE TSW ! ! !

For MX-ONE TSW !

174

Dynamic Network Administration Technical Guide

D.N.A. Server

The generic extension number, the Message Service number, is affiliated to the SMS Service Centre through a specified I/O port using the MSCOI command. Multiple message service connections can be initiated with this command with the respective directory numbers and IO-DEVs.

From MX-ONE TSW onwards, more than one SMS Server can be initiated from Extension Manager. 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.

Short Message Service Standby

The standby SMS is started automatically once the SMS itself is started. To turn the standby service off, change the Registry value of HKLM\SOFTWARE\Ericsson\MRS\SMS\Manager\ActivateStandbySMS to 0 (zero) and restart the service.

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.
HKLM\SOFTWARE\Ericsson\RemoteDS\Manager\EnableFilexfrCompression

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.

175

D.N.A. Server

Dynamic Network Administration 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.

GICI Connection
Once started, RDS listens for a GICI connection. A GICI connection is a socket connection initiated from the PBX. Once RDS receives a connection attempt, it will monitor heartbeat events from the PBX. The heartbeat (event 98), is initiated from the client (PBX) to RDS. RDS will acknowledge the heartbeat with event 93, and then send a heartbeat response (event 99). The PBX will in turn acknowledge this with event 93. If no events (heartbeat or other event) are received from the PBX for 5 minutes, RDS will close the socket connection and then start listening for connection attempts. The event signaling can be monitored via RDM.

Message Diversion and Secondary and/or Shared Extension

This section describes in detail how message diversion works together with secondary extension and/or shared extension. Please note that other characteristics, such as overlapped message diversion and periodic message diversion have lower priority and may impact the active message diversion computation. However, once a message diversion is determined to become active, then the following applies. The functionality described is extension-centric. That is, the extension in question enters the state described. However, performing directory searches from OWS/ECA/ECC provides a user-centric view. Thus, a users message diversion state may not be reflected on extensions for the user. The definitions of secondary and shared extension are:

176

Dynamic Network Administration Technical Guide

D.N.A. Server

A user having more than one extension has one primary extension and one or more secondary extension(s). The primary extension is usually the published phone number (extension) for the user while the secondary extension is usually a non-published phone number (extension). As a user can have only one primary extension, all other extensions are considered secondary extensions. A shared extension is an extension that is shared among two or more users. A shared extension can be a primary extension or a secondary extension for the user. As a shared extension is shared among two or more subscribers, one of the subscribers is configured to be the primary subscriber.

There are two methods in which message diversion can propagate between primary and secondary extensions. ! Top-down. The message diversion is set on the users primary extension. RDS Configuration controls whether the message diversion shall also be considered for the users secondary extension(s). For more information refer to Message Diversion Options in RDS Configuration online help. Bottom-up. The message diversion is set on the users secondary extension. A Registry key controls whether the message diversion shall also be considered for the users primary extension. Set
HKLM\SOFTWARE\Ericsson\RemoteDS\Manager\MsgDivToPrimaryExtensio n to 0 to disable and 1 to enable.

Normally, message diversions are managed on an extension level. However, OWS can show information using both a subscriber view and extension view. The OWS main window uses a subscriber view when performing a search operation. The detailed information view shows the extension view. If searching based on an extension number, then the OWS main window will show the subscriber view, whereas the detail view will show the extension view. Depending on the extension number used in the search, the detail information can be for primary or secondary extension. Thus, it is possible to see a message diversion in the detail view that is not visible in the main window. The following is the rule for setting message diversion using top-down method. Secondary nonshared extension OWS (shared extension) No No
177

OWS (subscriber) Yes Yes

Trigger

Top-down method Set from primary extension Set from OWS (subscriber) Yes Yes Yes Yes No No Yes (1) Yes (1)

Bottom-up method

OWS (nonshared secondary extension)

Primary extension

Shared extension

D.N.A. Server

Dynamic Network Administration Technical Guide

Set from non-shared secondary extension Set from shared extension Set from OWS (nonshared secondary extension) Set from OWS (shared extension)

Yes No Yes

Yes No Yes

No Yes No

Yes Yes (2) Yes

Yes (1) No Yes

No Yes (3) No

No

No

Yes

No

No

No

(1) This is shown in the detail information when searching for the individual extension. (2) This will show in OWS subscriber view if the user has this extension number as the primary extension. (3) This will show in the extension view when searching for the particular extension.

178

Chapter 10 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. 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 by default from the configured start time. You can setup a Registry string to extend the polling time. Refer to Extend Polling Time for details. Note: PDM makes three extraction attempts for each measurement site.

179

Maintenance

Dynamic Network Administration Technical Guide

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 BC12.X, PDM may treat it as if the site is running BC12.1 if the latest PDM release supports BC12.1. A onetime 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 30 minutes after the scheduled job is started by RDS. PDM scheduling can be set during the installation procedure. This option is supported only on the D.N.A. Server.

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...

180

Dynamic Network Administration Technical Guide

Maintenance

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 Performance Data Manager extraction process is scheduled to run 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 2000, Excel 2002, or Excel 2003 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 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

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 (",").

181

Maintenance

Dynamic Network Administration Technical Guide

! Example: If there are five nodes and only node 2 and 4 should be polled, set the Registry string to: ! 1,3,5, (make sure you end with a comma ",")

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 six, polling time defaults to six hours. If this setting is greater than 12, it is treated as a 12 hour polling time. The Registry key is HKLM\SOFTWARE\Ericsson\PMG\BatchLength.

Presentation Manager
Following are important operation and maintenance considerations for Performance Presentation Manager.

Operational Requirements
PPM, like Microsoft Excel 2000, Excel 2002, or Excel 2003, 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, Cordless Extension Traffic and Mobility Function and IP Network Interface 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.

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 D.N.A. database utility (DBCP.EXE) is to backup/restore D.N.A. application-related databases to/from a files running on Microsoft SQL Server 7, Microsoft SQL Server 2000, MSDE and MSDE 2000. The backup feature provided by SQL Server 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.

182

Dynamic Network Administration Technical Guide

Maintenance

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, 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 PMG Backed Up/Restored All installed DNA databases Dnadfdb emgdb security db_xaction Dirdb SiteX 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 stopped while the operation is in progress. It can only be executed on the same machine where Microsoft SQL Server 7, Microsoft SQL Server 2000, MSDE or MSDE 2000 is installed. During the restore process, the target database should not be accessed or connected by other processes or applications.

183

Chapter 11 Troubleshooting
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 ASCII text files can be viewed with Windows Notepad.

D.N.A. Server Installation Logs

Located at: <dna installed directory>\dna_s\detail.log and \dna_s\summary.log

D.N.A. Client Installation Logs

Located at: <dna installed directory>\dna_c\detail.log and \dna_c\summary.log

ECA Installation Logs

Located at: <eca installed directory>\eca_install.log

ECC Client Installation Logs

Located at: <ecc installed directory>\install.log

Mobile Executive Installation Logs

Located at: <mobileexec installed directory>\mobileexec.log

PPMLite Installation Logs

Located at: <ppmlite installed directory>\ppmlite.log

Personal Assistant Installation Logs

Located at: <PersonalAssistant installed directory>\install.log

185

Troubleshooting

Dynamic Network Administration Technical Guide

Event Log Messages

D.N.A. applications utilize the event logging facility to record error messages returned from the SQL server and generated by D.N.A.. If you encounter application or database operation difficulties, you can use the Windows Event Viewer to display information for events related to the problem and assist in problem isolation. Event Viewer displays system events registered by Windows 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 System Guide" for information about using Event Viewer. Application D.N.A. Applications Error Message Corrective Action

Fix PC hardware. 1 CPBXLINK: InputHandler() cannot get timer capabilities. 2 CPBXLINK: Unable to contact the telephone. 3 Check phone, connection cable, and proper ELU initiation. N/A

4 Unable to open registry Check and correct Registry and user permissions. key. 5 No response from PBX port. Check all TAU connecting cables and cycle power on the TAU. This message ONLY appears when Operator Workstation is explicitly configured to use a TAU. Check all TAU connections and COM port assignments. Check connection to the PBX jack on the TAU. Check connection to PHONE jack of the TAU.

6 Unable to detect a terminal adapter on the PBX port. 7 The terminal adapter reports no PBX connection. 8 The terminal adapter reports no phone connection.

Restart Operator Workstation. This 9 CPBXLINK: SendSignal(%1!s!) failed. usually appears if the program is aborted unexpectedly. GetLastError returned %2!s!. 10 Error reading registry value. RegEnumValue() returned %1!s!. If the returned value is 234, there is a Registry value of type REG_SZ longer than 80 characters. Shorten

186

Dynamic Network Administration Technical Guide

Troubleshooting

Application

Error Message

Corrective Action that value.

11 13 14 SetCommState() Failed. GetLastError returned "%1!s!". 15 CreateFile(%1!s!) failed. GetLastError returned "%2!s!".

N/A 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. If error recurs, 16 CreateThread() for CCommLink::InputHandler contact system administrator. failed. GetLastError return "%2!s!". 17 18 No response from the Operator Workstation keyboard port. 19 Failed to connect to directory server. N/A 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.

20 Failed to open directory Verify that both the SQL server and D.N.A. Server are installed and database. running on the server PC. 21 Failed to retrieve subscriber user-defined fields. 22 ODBC Error: SQLState: "%1!s!", ODBCError: "%2!s!", NativeError: "%3!s!". 23 ODBC Information: SQLState: "%1!s!", ODBCInfo: 2!s!",NativeInfo: "%3!s!" 24 Warning physical memory is running low. 25 Warning Virtual memory is running low. Correct database setup using the Directory Configuration utility. Check SQL and ODBC driver using SQL utilities.

None (information message)

Either increase memory or close (exit) non-essential programs. Increase the paging file size via the Windows Control Panel. Select
187

Troubleshooting

Dynamic Network Administration Technical Guide

Application

Error Message

Corrective Action System and virtual memory.

Replace the telephone. 26 Equipment status signal reports telephone is faulty. 27 Warning Signal Buffer has exceeded 90% 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. Re-install the D.N.A. Server client software.

28 Warning Operator Workstation will not try to connect to Database. ODBC driver is not installed in registry. 29 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. 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. 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 or later.

30 Error Signal Buffer Overflow Loop Count

31 Department diversion database connection disconnected.

32 External search database connection disconnected.

33 Message and Diversion Same as event 31. If these two events (31 and 33) occur database connection independently, there may be an disconnected. installation related problem. 34 Department diversion None. This is an information

188

Dynamic Network Administration Technical Guide

Troubleshooting

Application

Error Message database connection complete.

Corrective Action 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 D.N.A. 4.0 or later.

35 External search database connection complete.

36 Message and Diversion None. This is an information message. The absence of this database connection message indicates a service or complete. network problem similar to events 31 and 33. 1001 E1001 - Database Server Error(37000): [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open user default database. Login failed. There is a problem connecting to SQL Server. Check if SQL Server is running. If not, start SQL Server. Note: When using Microsoft Desktop Engine (MDE) and rebooting the PC, there may be an instance of this message logged. This is due to Desktop Engine starting after RDS. RDS will enter reconnect mode and will connect to Desktop Engine when Desktop Engine is started. 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. 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

1001 Could not load resource library: %1

Ericsson ClockSync

1001 Could not duplicate thread handle.

Ericsson ClockSync

1002 Could not create event handle.

Ericsson ClockSync

1003 Could not open registry key %1, using defaults.

Ericsson ClockSync

1004 Client is enabled, but Initialization error.

189

Troubleshooting

Dynamic Network Administration Technical Guide

Application

Error Message server machine name is invalid. Client disabled.

Corrective Action Restart the service.

Ericsson ClockSync

1005 Receive broadcasts Initialization error. is enabled, but server Restart the service. machine name is invalid. Receive disabled. 1006 Could not open process token, client disabled. Initialization error. Lack of system resources. Reduce the number of running applications and start the service again. Initialization error. Lack of system resources. Reduce the number of running applications and start the service again.

Ericsson ClockSync

Ericsson ClockSync

1007 Could not enable time set privilege for process, client disabled.

Ericsson Installation

0 %1 unable to connect to Refer to database manual for database %2. detailed information of database error. Correct the problem per database manual and redo the installation. %1 = Application name. %2 = Database error message. 0 %1 error inserting application %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. Refer to database manual for detailed information of database error. Correct the problem per database manual and redo the installation. %1 = Application name.

Ericsson Installation

Ericsson Installation

0 %1 error inserting elements %2.

Ericsson Installation

0 %1 error inserting sites %2.

190

Dynamic Network Administration Technical Guide

Troubleshooting

Application

Error Message

Corrective Action %2 = Database error message.

Ericsson Installation

0 %1 number of licensed Refer to database manual for elements does not match detailed information of database element table. error. Correct the problem per database manual and redo the installation. %1 = Application name. %2 = Database error message. 1000 %1 number of Refer to database manual for elements in element table detailed information of database does not match site table. error. Correct the problem per database manual and redo the installation. %1 = Application name. %2 = Database error message. 1001 %1 error updating number of element licenses %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

Ericsson Installation

Ericsson Installation

1002 %1 the element type Refer to database manual for was not defined. detailed information of 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 service. Initialization error. Reduce the number of running applications and restart the service. Initialization error. Reduce the number of running

Ericsson LFS

Ericsson LFS

1001 Failed to initialize application.

Ericsson LFS

1002 Failed to duplicate thread handle.

Ericsson LFS

1003 Failed to open named pipe acceptor.

191

Troubleshooting

Dynamic Network Administration Technical Guide

Application

Error Message

Corrective Action applications and restart the service.

Ericsson LFS

1004 Failed to initialize database.

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. Initialization error. Reduce the number of running applications and restart the service.

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 Ustream.

Ericsson LFS

1008 Failed to open reactor.

Ericsson LFS

1009 Failed to set security Initialization error. attributes. Reduce the number of running applications and restart the service. 1010 Failed to create message queue thread. Initialization error. Reduce the number of running applications and restart the service.

Ericsson LFS

Ericsson LFS

1200 Failed to retrieve Initialization error. security data server name Restart the service. from registry. 1201 Failed to initialize Initialization error. security data server client. Reduce the number of running applications and restart the service. 1200 Cannot retrieve the Run-time error. password format data from Neither the primary nor the backup the local database. Notify databases are available. Password the system administrator. cannot be changed with this condition. Contact your system administrator. 1201 Cannot retrieve the Run-time error.

Ericsson LFS

Ericsson LFS

Ericsson LFS

192

Dynamic Network Administration Technical Guide

Troubleshooting

Application

Error Message

Corrective Action

password format data from Cannot retrieve data from the the server database. primary database. Password cannot Notify the system be changed with this condition. administrator. Contact your system administrator. Ericsson LFS 1202 Cannot retrieve the user 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

1203 Cannot retrieve the user data from the server database. Notify the system administrator.

Ericsson LFS

1204 Cannot save the new Run-time error. password. The server Cannot store data to the primary database is unavailable. database. Password cannot be changed with this condition. Contact your system administrator. 1205 Cannot save the new Run-time error. password. Unable to Cannot store data to the primary connect to the security database, due to communication data server. problems with the security data server. Password cannot be changed with this condition. Contact your system administrator. 1206 Cannot retrieve the user data from the server database. The application may not be installed. Notify the system administrator. 1207 Cannot retrieve the user data from the local database. The application may not be installed. Notify the system administrator. 1500 Failed to close Run-time error. Verify that the application is installed. Reinstall the application, if needed.

Ericsson LFS

Ericsson LFS

Ericsson LFS

Run-time error. Verify that the application is installed. Reinstall the application, if needed.

Ericsson LFS

Shutdown error.

193

Troubleshooting

Dynamic Network Administration Technical Guide

Application

Error Message

Corrective Action

message queue normally. Notify the system administrator. Ericsson LFS 1700 Out of memory. 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. 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. 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 SDS

1000 Could not load resource library.

Ericsson SDS

1001 Failed to initialize application.

Ericsson SDS

1002 Failed to duplicate thread handle.

Ericsson SDS

1003 Failed to open named pipe acceptor.

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.

Ericsson SDS

1007 Failed to push module on Ustream.

Ericsson SDS

1008 Failed to open reactor.

Ericsson SDS

1009 Failed to set security Initialization error. attributes. Reduce the number of running applications and restart the service.

194

Dynamic Network Administration Technical Guide

Troubleshooting

Application Ericsson SDS

Error Message 1010 Failed to create message queue thread.

Corrective Action Initialization error. Reduce the number of running applications and restart the service. 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

Ericsson SDS

1200 Database server error: %1.

Ericsson SDS

1201 Failed to connect to Run-time error. database server. Retrying Check whether database server is in %1 seconds. running and restart, if necessary. %1 = Database error message 1202 Failed to create database server connection thread. Run-time error. Reduce the number of running applications and restart the service.

Ericsson SDS

Ericsson SDS

1203 Failed reading the database source from the registry. Application type = %1.

Run-time error. Check the content of the Registry setting with RDS configuration. Check the access permission to the Registry entries with the Registry Editor. %1 = Application type

Ericsson SDS

1500 Failed to close Shutdown error. message queue normally. Notify the system administrator. 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

Ericsson SDS

Ericsson UserConfig

1000 Cannot connect to database server %1.

Ericsson UserConfig

1001 Cannot open user table %1.

Ericsson UserConfig

1002 Cannot update the

195

Troubleshooting

Dynamic Network Administration Technical Guide

Application

Error Message user %1.

Corrective Action 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 database error. Correct the problem per database manual and try again. %1 = Database error message.

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.

Ericsson UserConfig

1008 Cannot load the site Refer to database manual for table %1. detailed information of database error. Correct the problem per database manual and try again. %1 = Database error message.

Error Messages for SNMP Agent

GetAppSuiteRegInstalled: RegOpenKeyEx failed: 0xnnn Make sure that the HKLM\SOFTWARE\Ericsson\DMI\AppSuite Registry key actually exists and that System account has permission to read it. Make a note of the error code, 0xnnn.

196

Dynamic Network Administration Technical Guide

Troubleshooting

GetAppSuiteRegInstalled: RegQueryValueEx failed: 0xnnn Make sure that the Registry key 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 HKLM\SOFTWARE\Ericsson\DMI\AppSuite Registry key 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 HKLM\SOFTWARE\Ericsson\DMI\AppSuite\"name" Registry key 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 Make a note of the error code, 0xnnn.
HKLM\SOFTWARE\Ericsson\DMI\AppSuite\InstalledAppSuiteComponents. HKLM\SOFTWARE\Ericsson\DMI\AppSuite\InstalledAppSuiteComponents

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 HKLM\SOFTWARE\Ericsson\DMI\AppSuite\ Registry key 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.

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

197

Troubleshooting

Dynamic Network Administration Technical Guide

Make sure that the HKLM\SOFTWARE\Ericsson\DMI\AppSuite\ Registry key 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 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. GetAppSuiteServerName: RegOpenKeyEx failed: 0xnnn Make sure that the HKLM\SOFTWARE\Ericsson\MRS\CurrentVersion\ Registry key actually exists and that System account has permission to read it. GetAppSuiteServerName: RegQueryValueEx failed: 0xnnn
HKLM\SOFTWARE\Ericsson\DMI\AppSuite\InstalledAppSuiteComponents.

198

Dynamic Network Administration Technical Guide

Troubleshooting

Make sure that the

HKLM\SOFTWARE\Ericsson\MRS\CurrentVersion\ServerName Registry key actually exists and that System account has permission to read it.

GetAppSuiteServerID: RegOpenKeyEx failed: 0xnnn Make sure that the HKLM\SOFTWARE\Ericsson\MRS\CurrentVersion\ Registry key actually exists and that System account has permission to read it. GetAppSuiteServerID: RegQueryValueEx failed: 0xnnn Make sure that the HKLM\SOFTWARE\Ericsson\MRS\CurrentVersion\ServerID Registry key 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.

199

Troubleshooting

Dynamic Network Administration Technical Guide

Technical Support
The Troubleshooting book contains information needed to resolve most problems that can occur with the D.N.A. applications. However, situations may occur 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 + Service Pack Level SQL Server + Service Pack Level D.N.A. + Service Pack Status + Hot Fix Status TAU or CT Adapter Revision Level Type of LAN and LAN configuration

Local Area Network: System size:

Number of: ! ! ! ! OWS clients DMG clients Names in subscriber database MD110 or Ericsson IP-PBX nodes

If Hotfixes loaded:

Version of "fixed" .exe files (To view, use the Windows Explorer to select and right-click the .exe file, select Properties from the pop-up menu, click the Version tab. PBX software release CNI version or Service Pack Status Any special OWS patches System size (i.e., nodes, extensions, etc.) A detailed description of the problem. Although it is not necessary, it will also 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.

PBX setup:

Include:

200

Dynamic Network Administration Technical Guide

Troubleshooting

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.

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.)

PBX
PBX Type ______________ Version ________________ No. of Nodes ____________ IPU Revision _____________ ICU Revision _____________ NIU Revision _____________

Operating System Information (mark all that apply)

Windows Workstation ____ Version ________________ Windows Server _________ Language _______________

Configuration
Workgroup______________ Stand Alone_____________ FAT ___________________ Domain _________________ File System______________ NTFS___________________

Network Protocol (mark all that apply)

NetBEUI _______________ IPX/SPX _______________ None __________________ TCP/IP __________________ Other ___________________ Software ________________

201

Troubleshooting

Dynamic Network Administration Technical Guide

PC
Manufacturer ____________ CPU __________________ Memory (RAM) __________ Model __________________ Clock Speed _____________ Hard Disk _______________

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) ________________________ ________________________ Operator Workstation (OWS) ________________________ ________________________ Performance Data Manager (PDM) ________________________ ________________________ Performance Presentation Manager (PPM) Version/Release Level Language Supported

________________________ ________________________

Ericsson Communication Assistant (ECA) ________________________ ________________________ Ericsson Communication Client (ECC) Other ________________________ ________________________

________________________ ________________________

Directory Manager
When using Directory Manager (DMG) on the D.N.A. server to add a department name containing a comma (,), the following error message appears: The following characters are reserved by CAAPI and cannot be used in name, phone and cost centers fields: , ;

202

Dynamic Network Administration Technical Guide

Troubleshooting

DIRPOP will also generate an error if there is a comma (,) in the department name. However, using DMG or DIRPOP on a D.N.A. client (i.e., a computer other than the D.N.A. server) works without receiving any error message. The reason is as follows. The Registry settings for CAAPI reside on the D.N.A. server along with the CAAPI application. When DMG is run on the D.N.A. server, DMG will check to ensure that CAAPI delimiters are not used in the department names. On a D.N.A. client however, the Registry settings do not exist for CAAPI, so DMG cannot check for the CAAPI delimiters. DIRPOP exhibits this same limitation. Before any of the following procedures are used, close all D.N.A. applications (DMG, DIRPOP, DirLink, LDAP, etc.) to avoid a potential database mismatch. Note: The values for FieldMark and RecordMark may be changed to other values, provided there is no conflict with subscriber or department names. Ensure that the values for FieldMark and RecordMark are always synchronized between the D.N.A. server and its clients. The following procedure is used on a system where CAAPI is not used and department names with comma are used: 1. On the D.N.A. server open the Registry key Software\Ericsson\MRS\CAAPI under the HKEY_LOCAL_MACHINE hive. 2. Change string value FieldMark to $ (dollar sign). FieldMark is the divider between the data within one subscriber or department. 3. Change string value RecordMark to | (vertical pipe, or upper-case backslash symbol on QWERTY keyboard). RecordMark is the divider between the subscribers or departments. The following procedure is used on a system where CAAPI and department names containing commas are used: 1. On all D.N.A. client machines where DMG or DIRPOP is run, open the Registry key Software\Ericsson\MRS under the HKEY_LOCAL_MACHINE hive. 2. Create sub-key CAAPI. 3. Create string value FieldMark under the CAAPI sub-key. FieldMark is the divider between the data within one subscriber or department. 4. Set the value of FieldMark to $ (dollar sign). 5. Create string value RecordMark under the CAAPI sub-key. RecordMark is the divider between the subscribers or departments. 6. Set the value of RecordMark to | (vertical pipe, or upper-case backslash symbol on QWERTY keyboard). Change the corresponding Registry values on the D.N.A. server to match the values set on the D.N.A. clients The following table lists error messages displayed by the Directory Manager application that may indicate a setup problem.

203

Troubleshooting

Dynamic Network Administration Technical Guide

Problem

Corrective Action

An error occurred while closing Verify that there is a connection to RDS (Remote the database. Data Server) and the SQL server, and verify that RDS and the SQL server are responding to data retrieval and update requests. Cannot get user ID for transaction register entry. Could not add a new department to the database. 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 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.

Could not add extension.

Could not add the external directory entry.

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 A record in the delete_id table is locked. from IDMSC.

204

Dynamic Network Administration Technical Guide

Troubleshooting

Problem Could not retrieve authorization code from the logging services. Could not retrieve database source information from the logging services. Could not update extension data.

Corrective Action 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. 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. 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 update external directory data.

Could not update subscriber.

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.

205

Troubleshooting

Dynamic Network Administration Technical Guide

Ericsson Communication Client

Problem Possible Cause Corrective Action Stop IIS (allowing up to 30 seconds to completely stop). Delete all the files in dna_c\dirb\data. Reboot your PC. Insure that all the files are populated. Run the command from the browser or ECC again. Error message "Failed to Init Radvision" displayed when ECC client starts. Multiple H.323 clients running Modify the Registry value HKLM\SOFTWARE\Ericsson\ECC\C simultaneously.
urrentVersion\PortCallSignal

Unable to log on to If running ECC on a DNA DNA from an ECC Client, there might be client. instances when the local data on the DNA Client becomes faulty or corrupt.

to a value other than 1720, which is the default, to avoid a conflict. Restart ECC.

ECC fails to register with the gatekeeper

Gatekeeper configuration is incorrect

Confirm the settings in the Gatekeeper tab of the Setup property sheet

Failure to connect to the RAS Modify the Registry value port due to network limitation HKLM\SOFTWARE\Ericsson\ECC\C urrentVersion\PortRAS to a port (the port is restricted). number that is unrestricted by the network to avoid a conflict. Restart ECC. Multiple Network Cards installed When a call connects, there is no speech path. Failure to connect to the RTP port to send voice data packets due to network limitation (the port is restricted). Confirm that the correct network card is selected on the Network tab of the Setup property sheet. Modify the Registry value number that is unrestricted by the network to avoid a conflict. Restart ECC. Multiple sound cards installed. Make sure the sound card selected on the General tab of the Setup property sheet is correct.
HKLM\SOFTWARE\Ericsson\ECC\C urrentVersion\PortRTP to a port

206

Dynamic Network Administration Technical Guide

Troubleshooting

Problem The state Error appears in the ECC Monitor window for monitored extensions.

Possible Cause Only extensions that are on the same PBX node as the ECC users extension may be monitored by ECC. If the state Error is displayed for an extension in the ECC, it could indicate that either the ApplicationLink information is improperly configured, or the monitored extension is on another PBX node.

Corrective Action Confirm that ApplicationLink information was setup properly during ECC installation. This can be found in the Windows Registry at a pair of values for each PBX node (e.g., Node1Name, Node1Port, Node2Name, Node2Port).
HKLM\SOFTWARE\Ericsson\ECC\C urrentVersion. There should be

If the ApplicationLink information is correct, it may be the case that the users extension is defined on a different PBX node than the monitored users extension. Since ECC can only connect to a single ApplicationLink server, it will not be possible to monitor that extension, and Error will display as the state for the extension. If the ApplicationLink information is incorrect, reinstall the ECC Server. This will update the ApplicationLink configuration information in the ecc.cfg configuration file on the server, and clients will automatically retrieve this updated information the next time ECC is run. Wave files for incoming and outgoing calls (i.e., ring and ringback tones) are not played out the selected sound card. The selected sound card is This is a limitation in the not the active (default) system application. The wave files sound card. configured will not be affected by the sound card selected by the Audio Devices list. If you override the default system sound card, only the speech path for your calls will be affected. Wave files will be played using the system sound card.

207

Troubleshooting

Dynamic Network Administration Technical Guide

Problem Personal Number errors: Failed to delete choice Failed to change choice data Failed to initiate choice Failed to activate the profile

Possible Cause 1. Personal number data is out-of-synch between PBX and SQL database. 2. Backend component is not configured properly.

Corrective Action 1. Re-synchronize extension data for the faulty extension via the MD Support utility. 2. EMG connection with PBX will fail if configuration is not set up properly. The administrator must ensure that EMG can be logged onto with the System account and can connect with PBX successfully. Please refer to Configuration for Personal Number access section for details. Note: The administrator can also turn on the log for more information. Refer to Trace in the Personal Number problems section for Ericsson Communication Assistant.

Extension Manager
Problem 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. Restart the network.

Cannot connect to database server. (Message Box) Cannot get database server information. (Message Box) Cannot open database.

Network is down.

Data source points to Setup the data source. the wrong PC. Server database is Restart the server database.

208

Dynamic Network Administration Technical Guide

Troubleshooting

Problem (Message Box) Cannot connect to MD110.

Possible Cause down.

Corrective Action

Telephone number to Verify that MD110 telephone access MD110 number is correct and available. unavailable or incorrect. Make sure there is a port available. Verify there is a functioning cable connection between the Telnet server and the MD110 IPU port(s). Verify the SCS is running.

Cannot connect from the All Telnet ports are Telnet server to the serial occupied. 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. Access agent is not running. Incorrect Telnet server address, User ID, or password.

Make sure the access agent is running. 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.

Cannot get Telnet Network or SQL address from the server is not running. database. (Message Box) Cannot open communication device. Communication device is being used by another application.

Specify a valid communication Selected device. communication device does not exist. Cannot retrieve PBX error Server database is messages from database. down. (Message Box) Required entry in EMGDB database MDERR table does not exist. Cannot synchronize with PBX. Restart the server database. Reinstall the EMGDB database.

Logon to PBX not Verify that the connection to the completed due to PBX is good and verify that the PBX problem with is operating properly. connection to the PBX or the PBX itself.

209

Troubleshooting

Dynamic Network Administration Technical Guide

Problem 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)

Possible Cause

Corrective Action

Problem with Verify that the connection to the connection to the PBX is good and verify that the PBX PBX or the PBX itself. is operating properly.

Extension Manager Run MD support utility to MD database table is synchronize MD data. empty. Data source set up incorrectly. Setup the data source.

EMG client is killed when This occurs by RDS restarts. design. During startup, RDS kills all EMG instance(s) in order to allow the extension Link function to function properly. Error communicating with Network is down or the Remote Database the RDS is down. Server. Error disconnecting from the Telnet server. Error initializing the modem. Error resetting the modem. 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. Problem with connection to modem/TAU or modem/TAU itself. Network is not operating properly. Remote Data Server is not running. Incorrect entry in Registry for path in server for template files. Verify that the connection to the modem/TAU is good and that the modem/TAU is operating properly. Restart the network. Run RDS. Contact technical support. Restart the network and verify RDS is running.

210

Dynamic Network Administration Technical Guide

Troubleshooting

Problem

Possible Cause

Corrective Action When initiating the Dual access extension you select the Equipment position for the digital extension among the first 16 time slots, the remaining 16 time slots are used for the corresponding ISDN extension (Example: digital extensions equipment position was 1-0-40-3, the ISDN extensions equipment position will be 1-0-40-19). Restart the network. Setup the data source. As soon as the synchronization stops, (by letting it finish or by "breaking" it) restart the synchronization. Set up the communication parameters to match the communication device.

Error initiating extension. There is no space Not accepted. Equipment available for the position already assigned. corresponding ISDN extension. When the Dual access extension interface is provided, 32 time slots are required in the switch for each ELU 28/3 board. Failed to ... Network is down. Data source set up incorrectly. A command was sent to the PBX while synchronization was running. Incorrect communication settings. Communication parameters for the communication device are not set up correctly.

Invalid authorization to Telnet Access Agent. Invalid client path. Please Directory set for Contact technical support. check with your system TargetDirectoryClient administrator. in Registry does not exist. Invalid path to the log files. Extension Manager log sub-directory for the specific site does not exist. Online help subdirectory does not exist. Site sub-directory under client path does not exist. Create emg\log sub-directory under the site directory.

Invalid path to the online help parameter description. Invalid site path. Please contact your system administrator. Licenses in EMG do not match the licenses in the MD.

Create emg\help sub-directory.

Create the site sub-directory.

The D.N.A. Database If you have modified a license file in has not received the MD with new values for certain updated license objects (e.g., updating a Personal

211

Troubleshooting

Dynamic Network Administration Technical Guide

Problem

Possible Cause information.

Corrective Action Number license from a Trial license of 0 to 100 new licenses), use MD Support to synchronize the D.N.A. Database with the updated license information. A full synchronization is not required, only the feature that includes the updated license information (e.g., Operator Message Diversion). Restart the MD110 as described in the MD110 Operation and Maintenance manuals.

Logon rejected.

Logon attempt rejected by MD110 after three unsuccessful attempts. Time limit for MD110 feedback too short.

No character received from MD110 within time limitation.

Increase time limit.

Problem with Verify that the connection to the connection to the MD110 is good and verify that the MD110 or the MD110 MD110 is operating properly. itself. Problem with TAU/modem. All Telnet ports are occupied. No password assigned for user ID. Restart/reset the TAU/modem.

No dial tone received from the communication device. No free MML session is available. No password assigned.

Verify that there is a port available. Request that system administrator add Extension Manager access password to the user ID.

No prompt received from PBX.

Logon to PBX not Verify that the connection to the completed due to PBX is good and verify that the PBX problem with is operating properly. connection to the PBX or the PBX itself. Incorrect MD110 password entered. Enter correct password, or use MD Support application to assign a new password. Verify that the device is available. Resend command.

Password unknown.

SCS device is not available. Serial line not available.

The SCS device is occupied. Command to MD110 temporarily blocked.

212

Dynamic Network Administration Technical Guide

Troubleshooting

Problem The dialup number is busy.

Possible Cause The destination directory number is unavailable due to current activity. User ID not authorized for Extension Manager.

Corrective Action 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.

The logged in user is not allowed to run Extension Manager.

The number of extensions available for initiation reaches the maximum allowed.

The reason could be that during the installation of the DNA server, the value set per node was lower than the number of extensions you actually have in the node, and after synchronization of all extensions, you exceeded the maximum allowed for that node in the database.

Run the DNA server installation and select Resize Database. Any value in the Total Number of Extensions, and the Extensions for each node, can be used. These values have no impact towards the license value in ELM, as ELM is the master.

The site for the current transaction is different from the selected site.

You are attempting to Disconnect the current site and process a transaction reconnect to the site required for the for a different site transaction. than the site currently connected. Extension number is Run MD support and re-synchronize not a member of any "Directory Information" and "Number known number series Series". currently in the database. Network is down. Site security information does not exist in logging local database. Logging facility service is down. Restart the network. Run RDS on the server.

Unable to get the site for the current transaction.

Unable to retrieve site security information from logging service.

Run logging facility service on the client.

Unable to retrieve the TargetDirectoryClient value from the Registry.

TargetDirectoryClient Contact technical support. entry for Ericsson does not exist in

213

Troubleshooting

Dynamic Network Administration Technical Guide

Problem Please contact your Administrator. Unable to retrieve transaction data source from Logging service.

Possible Cause Registry. RDS not running. Logging facility service is down. Data mismatch between RDS and logging facility service.

Corrective Action

Run RDS on the server. Run logging facility service on the client. Restart logging facility service on the client.

Unknown communication The system does not error. recognize a communications failure.

Contact Ericsson Technical Support.

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 Possible Cause Corrective Action Use the Windows Performance Monitor to check the exchng32.exe and mapisp32.exe processes. See E-mail Integration for OWS, in the Configuration section.

Cannot deliver (send) OWS may not have e-mail messages to successfully attached D.N.A. subscribers to a MAPI session. from Operator Workstation.

Cannot send mail via System default locale is Force an update to the system default SMTP with localized not set to the localized locale. Run the windows Control Panel, versions of OWS. version. and select the Regional Options applet. Click the Set default button, choose your language, and click OK. If you are not prompted to restart the system, select a different language and restart the system. After the system restarts, set your language again and restart once more.

214

Dynamic Network Administration Technical Guide

Troubleshooting

Problem Error dialog box displayed when starting Operator Workstation.

Possible Cause Database settings configured incorrectly. PBX interface problem.

Corrective Action 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 RS-232C 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 to view IRQ and address settings. Reassign IRQs and/or address settings to resolve conflicts.

Operator Workstation Line initiation or cabling starts, but cannot get problem. any on/off duty indications.

Verify the RS-232C 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. Check the class of service and call origin group for this operator interface in the MD110.

Operator Workstation Setup problem. starts and you can go "on duty" but cannot make or answer calls.

215

Troubleshooting

Dynamic Network Administration Technical Guide

OWS Supervisor
Use the following table to correct problems found when running OWS Supervisor. Error Message Possible Cause Corrective Action

216

Dynamic Network Administration Technical Guide

Troubleshooting

Error Message Possible Cause Failed to find The user ID on the client Connection cannot logon to the D.N.A. Point in Server server. is displayed when starting OWS Supervisor.

Corrective Action Verify that the user ID logged on at the client has correct authority to logon at the D.N.A. server. This can be done by using domain rather than local accounts when the machines are in the same domain. When in separate domains or in a workgroup, the easiest solution is to create a local account on the server with the same user ID and password as the local account on the client. In addition to DCOM and Windows account permissions, SP2 adds a Firewall control panel. The exact steps necessary to enable OWS Supervisor depend on the network and security setup, i.e. whether clients and servers are in a domain or workgroup, and domain or local accounts being used. The minimum requirements are: 1. The Windows account in effect for OWS Supervisor must have permission to logon at the DNA server 2. DCOM Access and Launch permissions for OWS Supervisor (the client application) and DNASupervisorServer (the server service) must include that account or a group to which it belongs 3. The Firewall control panel must show OWS Supervisor checked (enabled) 4. The DNA user account must have Access permission to OWS Supervisor. Troubleshooting is aided greatly by enabling Security Auditing (in Local Security Policy) and D.N.A. auditing (in the D.N.A. User Manager under the Application menu).
217

Extra security running on Windows XP (with Service Pack 2 or higher).

Troubleshooting

Dynamic Network Administration Technical Guide

Performance Data Manager

Use the following table to investigate problems identified in PDM error messages. Error Message Possible Cause Corrective Action

Cannot connect Telephone number to access Verify that MD110 telephone to MD110. MD110 unavailable or incorrect. number is correct and available. Cannot open Communication device is being Close the other application using communication used by another application. the communication device or device. wait until the communication device is available. Selected communication device Specify a valid communication does not exist. device. Communication to this node is rejected because of mismatch in system identity. PBX system identity has been changed and does not match with the one stored in the database. Resynchronize data. If synchronize system identify only, you can synchronize Numbering Series.

Or, wrong communication node Check node configuration is defined. settings. Telnet is set for communication. Check the connection list via However, there is no IP Communications -> Define list. address set in the connection list.

No default attempt connection list is defined. DNA application will not be able to connect to MD with Telnet setting.

Cannot Logon to MD110 not completed Verify that the connection to the synchronize with due to problem with connection MD110 is good and verify that MD110. to the MD110 or the MD110 the MD110 is operating properly. itself. Communication Problem with connection to the Verify that the connection to the line blocked. MD110 or the MD110 itself. MD110 is good and verify that Communication the MD110 is operating properly. line failure.

218

Dynamic Network Administration Technical Guide

Troubleshooting

Error Message Possible Cause Data format error. Possibly caused by MD110 file system error. MD110 file system problem.

Corrective Action Contact MD service personnel. Consider skipping data for that day (unrecoverable error).

Data format Noise in the communication line Retry the operation at a later error. Possibly between the PC and MD110. time. caused by noise. Data sequence error during data transfer. Database No SQL server connection operation failed available. or there was an error connecting to database server. SQL server is down or network connection is down. Data source is not set up correctly. Check event log for more specific error messages provided by the SQL server. Restart PDM. Verify that at least two connections are available. Verify that SQL server is up and network connection is OK. Verify that the data source is set up properly. Verify that the connection to the modem/TAU is good and verify that the modem/TAU is operating properly.

Error initializing Problem with connection to the modem, or modem/TAU or modem/TAU an error itself. resetting the modem. Failed to allocate memory. Not enough system memory.

Close unnecessary applications and restart PDM.

Failed to create No disk space available on the Delete unneeded files from the temporary file. local drive. local drive to make space Failed to write to available. temporary file. Failed to get Network is down, or RDS is not Restart the network, and run data associated running. RDS on the server. with PMG from the logging server.

219

Troubleshooting

Dynamic Network Administration Technical Guide

Error Message Possible Cause

Corrective Action

Incorrect Communication parameters for Set up the communication communication the communication device are parameters to match the settings. not set up correctly. communication device. No character received from MD110 within time limitation. Time limit for MD110 feedback Increase time limit. Maximum is too short. 300 seconds (5 minutes). Time limit should be increased to reflect the size of the PABX switch (the larger the switch, the longer the time limit). Problem with connection to the Verify that the connection to the MD110 is good and verify that MD110 or the MD110 itself. the MD110 is operating properly. No prompt received from MD110. Logon to MD110 not completed Verify that the connection to the due to problem with connection MD110 is good and verify that to the MD110 or the MD110 the MD110 is operating properly. itself. Command to MD110 temporarily blocked. No SQL server connection available. Resend command.

Serial line not available. Unable to connect to database 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 available.

SQL server is down or network Verify that SQL server is up and network connection is OK. connection is down. Data source is not set up correctly. Verify that the data source is set up properly.

User for database is not set up Verify that the user ID and password for database is set up correctly. correctly. Not enough space for the auxiliary database. 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.

220

Dynamic Network Administration Technical Guide

Troubleshooting

Error Message Possible Cause Unable to lock Database has been locked by database. PDM running on another PC. Database is used exclusively by other process.

Corrective Action Retry the operation later.

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 table describes troubleshooting for specific messages displayed by PPM.

Essential Requirements
PPM, like Microsoft Excel 2000, Excel 2002, or Excel 2003, 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, Cordless Extension Common Fixed Part, Cordless Extension Traffic and Mobility Function and IP Network Interface 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 Possible Cause Corrective Action Start Excel, select Macro from Tools menu, select Security, then change to Medium in the Security Level tab. Start Excel, select Macro from Tools menu, select Security, then change to Medium in the

Excel 2000 and Excel The macro security level is 2002 - Launch PPM set too high. but only Excel is started Excel 2003 Launch The macro security level is PPM with Excel set too high. message Macros are

221

Troubleshooting

Dynamic Network Administration Technical Guide

Problem disabled because the security level is set to High

Possible Cause

Corrective Action Security Level tab.

Auto-formatted charts Incorrect print driver selected Use the Printers option for the do not print properly. or print driver not set up Windows Control Panel to properly. select a different printer or modify the printer setup. Cannot access SQL database. ODBC data source not set up Set up ODBC again. properly. PPM does not have access rights to one or more databases. Server goes down and the connection is damaged. Incorrect site database. 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).

Remote Data Server

Symptom RDS fails to execute a scheduled task. Probable Cause Corrective Action Security settings on Set security attributes so the return handle can each machine be inherited by child processes/threads. differ, therefore the default security Change the value of the following Registry key: attributes conflict HKLM\SOFTWARE\Ericsson\MRS\RemoteDS\ Manager\UseSAForScheduledProcess with the parent process. Format: N/A Value: [REG_DWORD] 0=no (default value); new processes will not inherit security attributes from parent process. 1=yes; new processes will inherit security attributes from parent process.

222

Dynamic Network Administration Technical Guide

Troubleshooting

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 and CallEvetn.dll have 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

Failed to Logon

WAP ERR-500 Internal server error

Failed to Logon

WAP ERR-408 Server timeout WAP ERR-408 Server timeout Error code: xxxx Failed to activate profile!

Failed to access Personal Number Failed to update the Personal Number

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.

Search results always empty

Wrong device (message only) Failed to make call

Call feature will not be available Wrong device

No call handling license or IPService is not enabled The extension is not a mobile extension

Ericsson Communication Assistant

For debugging purposes, you can use RegEdt32 to configure the Ericsson Communication Assistant Log at:
HKLM\SOFTWARE\ERICSSON\ECA\IPService

223

Troubleshooting

Dynamic Network Administration Technical Guide

The following values are recommended. CSTAEVENT (= 0) ENTERINGMETHOD (=1) events sent from AppLink to ECA. Stored if = 1, = 0 not stored LEAVINGMETHOD (=1) service requests sent from ECA to AppLink. Stored if = 1, = 0 not stored LOGFILE specifies where the log file is stored and the name of the log file (defaults to <eca directory>\bin\eca.log) PORTID (= 1f92 in hex, and 8082 in decimal) TRACE (= 1)

Call Handling problems

Use the following table to investigate call handling problems. Error Message Cannot establish communication to the Call Event Service Possible Cause IP Service is not started Corrective Action Start the service. Also change the startup type to automatic if set to manual. Make sure IP Service is running Make sure AppLink is running. Make sure the OAS settings have been defined with correctly information in ECA Configuration. Make sure AppLink is running. Find the failed event in eca.log. Also suggest to trace in CSTA log. Make sure AppLink is running. After problem is fixed, the ECA client should receive Communication to Call Event Service restored message.

Extension xxxxx in node Request has failed due to x cannot be monitored AppLink is not running

Function unsuccessful

Failure event received from AppLink. If getting this message continuously, check the ECA log for details. The connection between ECA client and IP Service has broken. This is usually due to the connection between IP Service and AppLink being broken.

Unable to communicate with ApplicationLink

Personal Number problems

Problem Causes
There are two common causes for Personal Numbers problems. 1. Data out-of-synch

224

Dynamic Network Administration Technical Guide

Troubleshooting

The personal number data that ECA presents is retrieved from the SQL database. You may encounter the following errors if personal number data is out-of-synch with the PBX. ! ! ! ! Failed to delete choice Failed to change choice data Failed to initiate choice Failed to activate the profile

To correct the problems, please re-synchronize extension data for the faulty extension through MD Support. 2. Backend component not configured properly The other possible cause is because EMG connection with PBX fails. The administrator must make sure EMG can be logged on with SYSTEM account and can connect with PBX successfully. Please refer to Configuration for Personal Number access section for details.

Trace
The administrator can turn on a log file to capture the errors if needed. Perform the following steps to turn on the log. ! Define the full path of the log file Specify the full path of the log file for Registry HKLM\SOFTWARE\Ericsson\ECA\CurrentVersion\DlinkLog E.g., c:\dna_c\eca\bin\Dlink.log Set the value of the following Registry keys to 1
HKLM\SOFTWARE\Ericsson\ECA\CurrentVersion\DlinkDebug HKLM\SOFTWARE\Ericsson\ECA\CurrentVersion\DlinkEntering HKLM\SOFTWARE\Ericsson\ECA\CurrentVersion\DlinkLeaving HKLM\SOFTWARE\Ericsson\ECA\CurrentVersion\DlinkWarning

Restart IIS Go to the command prompt and enter iisreset

Use the following table to investigate the errors. For any errors not listed, send the log to support personnel for analysis. Error Message DnaLink.ocx CoCreateInstance Failed. Failed to create DnaLink.ocx object. Possible Cause Dnalink.ocx is missing or not registered. Corrective Action Check the file in \share\bin. Reinstall D.N.A. if file is missing. Register the file using Regsvr32 if file exists. Check the file in \share\bin. Reinstall D.N.A. if file is missing. Register the file using Regsvr32 if file exists. Make sure EMG is installed on D.N.A. Server and EMG can be lauched with System account.

Dnalink.ocx is missing or not registered.

EmgMdConnect DnaLink.ocx failed to connect to EMG, node=XX

Dnalink.ocx failed to connect to EMG. Check if EMG is installed.

225

Troubleshooting

Dynamic Network Administration Technical Guide

ConnectToEmgDb() DnaLink.ocx failed to connect to EMG database. OCX_Error=XX, Node=XX GenerateTask failed OCX service stopped, TaskType=XXXX All other errors

Dnalink.ocx failed to connect to database.

Turn on SQL Trace to get detail information from SQL Server side.

Dnalink.ocx is missing or not registered.

Check the file in \share\bin. Reinstall D.N.A. if file is missing. Register the file using Regsvr32 if file exists. Send the log to support personnel for analysis.

Service
Ericsson IP Service is installed on the D.N.A. Server. Since this service interfaces with AppLink, it should be restarted if call handling becomes a problem.

Header Error
If you get a Header Error when attempting to access the Assistant Log from a client browser, make sure buffering is enabled on the D.N.A. Server. To enable buffering 1. Run Internet Information Services by selecting Start!Programs! Administrative Tools!Internet Services Manager.

226

Dynamic Network Administration Technical Guide

Troubleshooting

2. In the Internet Information Services window directory tree, expand the server directory to display its subdirectories. 3. Expand the Default Web Site directory. 4. Click on the eca directory and click the Properties icon on the toolbar.

5. Click the Configuration... button in the eca Properties dialog box. 6. In the Application Configuration dialog box, go to the App Options tab.

227

Troubleshooting

Dynamic Network Administration Technical Guide

7. Make sure Enable buffering is checked.

Fields are Disabled

Ericsson Communication Assistant requires the Java Virtual Machine software on your computer. You can download it from http://java.com. If not installed, the fields associated with Java will be disabled: ! ! ! ! ! Quick Search in the main page Quick Dial/Search in the main page after logon Quick Dial in the Call Handling window Start Date/Time and End Date/Time in the Message Diversion page Activate Date/Time and End Date/Time in the Active Profile page.

228

Dynamic Network Administration Technical Guide

Troubleshooting

Slow to logon
It will take longer to logon for the first ECA logon request. This is due to the backend EMG process which will be started by the first logon request if EMG/Personal Number flag is turned on by the administrator. However, if backend EMG connection to PBX failed, the logon will take even longer because ECA has to wait until the EMG connection request has returned. If EMG connection with PBX fails, the request will not return until time-out. The administrator must make sure EMG can be logged on with System account and can connect with PBX successfully.

Outlook Integration & Lotus Notes Integration

Outlook or Lotus Notes Integration would not start
This problem is caused because Outlook or Lotus Notes 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.

Outlook or Lotus Notes Integration would not logon to the DNA Server
This problem is caused when there is no subscriber entry found with the current computer name (or User ID) defined in the D.N.A. Directory. Make sure you added the computer name(or User ID) to the subscriber's entry in the D.N.A. Directory.

Diversion information does not match between Outlook or Lotus Notes 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).

DNA Outlook Integration and Calendar Conflicts

When you have 2 Outlook Calendar appointments on the same day and time, a problem in DOI might arise. If a problem does occur, DOI will not know how to handle this and will report this as an error. The error message when you start the DOI program will give you the following message: One or more Items in the folder you synchronized does not match. To resolve the conflicts, open the items, and then try this operation again. Users who have conflicting appointments in their Calendar can solve this problem by clearing ALL of the conflicting appointments manually in Outlook. The following steps are used to find and solve the conflicting appointments: 1) Open a table view in the Outlook Calendar.

229

Troubleshooting

Dynamic Network Administration Technical Guide

2) Go to the View menu, select Current View and then choose By Category. 3) Identify the conflicting appointment(s). ! ( The conflicting appointment(s) will be displayed with a crossed-swords icon ).

4) Clear the conflicting appointment(s). ! Double click on each conflicting appointment to bring up the "Conflict Message" Dialog Box, and follow the instructions to clear the conflicting appointment.

Troubleshooting 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. You can run RDM by double-clicking on DNA_S\SHARE\BIN\rdm.exe.

230

Chapter 12 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. 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.

231

Application Data

Dynamic Network Administration Technical Guide

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 main_department_recID picture_resid middle_name_alt1 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 udf11_recID udf12_recID udf13_recID udf14_recID udf15_recID udf16_recID udf17_recID udf18_recID Field Type int varchar bit varchar varchar varchar int varchar int tinyint tinyint int varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar int int int int int int int int int int int int int int int int int int 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 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 UDF record ID UDF record ID UDF record ID UDF record ID UDF record ID UDF record ID UDF record ID UDF record ID

30 30 30 30 30 30 30 30 30 30 30 30 30

subscriber

232

Dynamic Network Administration Technical Guide

Application Data

Table Name

Field Name udf19_recID udf20_recID

Field Type 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 int int

Max Characters

Description UDF record ID UDF record ID

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 recID nodeID

160 160 160 160 160 160 160 160 160 160 160 160 160 160 160 160 160 160 160 160 60

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

extension

site

50 50 30

node ID site name node name remote node ID remote server record ID node ID

numser

233

Application Data

Dynamic Network Administration Technical Guide

Table Name

Field Name start_extension end_extension type options

Field Type 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

Max Characters 30 30

Description start extension end extension

keyword

recID value

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

external_directory recID department_recID address listed_number name udf1_recID udf2_recID udf3_recID udf4_recID udf5_recID udf6_recID field_ definition recID SQL_type field_name field_type field_resid label_name record_type options table_name display_sequence UDF_number max_data_length 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

160 30 50

30 30 30 20

field name field type label display

display sequence personal UDF max length 45 record ID text value

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

20

234

Dynamic Network Administration Technical Guide

Application Data

Table Name

Field Name options

Field Type int int varchar int int varchar varchar int varchar varchar int int varchar int varchar varchar varchar varchar int int varchar datetime datetime varchar varchar varchar it datetime datetime int int varchar varchar int int tinyint int int int int int int

Max Characters 30 30 30

Description trunk name display global group ID global name Table "access codes" for multiple tenants

global_name

groupID name

access_codes

recID nodeID exchangeID access_code nodeID_connection remote_server table_name recID recid terminal

20 20 30 20

deleted_id dept_recid_tmp

deleted table record ID temporary department record ID table extension dialing information

16

dial_extension_inf recID o country_code area_code prefix suffix options numser_recID dirdb_info schema_ver_no created_date released_date database_server database_server_ver_n 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

10 10 10 10

30 30 30 30

Directory database version and release information

diversion

Message diversion

160 80

235

Application Data

Dynamic Network Administration Technical Guide

Table Name

Field Name repeat_every repeat_type_day_0 repeat_type_day_1 repeat_type_day_2 repeat_type_day_3 repeat_end_time oper_div_recID operatorID

Field Type int int int int datetime int varchar

Max Characters

Description

60 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 160 80 30 Message Waiting (incl. E-mail) indication Message Diversion Reason Table (Synchronized from extension database by RDS)

divr

nodeID pbx_reason_code dna_reason_code pbx_description dna_description tdn duration reference method options priority

10 30 1 40 30

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

60 20 30 30 OWS Outbound Dialer dynamic log

outbound_dialer

60 20 reserved table record ID time system translation codes

reserved_id_table table_name reserved_flag ts_trans_codes portID ts_reason_code reason_code diversion_flag

4 1 1

236

Dynamic Network Administration Technical Guide

Application Data

Table Name

Field Name tdn ts_reason_text

Field Type varchar varchar int varchar varchar int varchar varchar varchar int int varchar varchar int int varchar int int varchar varchar varchar int int int varchar int int varchar varchar int datetime datetime int varchar int int int

Max Characters 1 80 1 1 20 20 1

Description

ts_msg_convert

portID ts_msg_byte msg_byte

time system message conversion time system card number range

ts_card_no_range portID start_card_no end_card_no diversion_flag ts_message recID received_recID msgID card_no portID

time system message waiting 10 20 logged-in user search access voice system mailbox number range

user_search_acce recID ss userID department_recID vs_mail_box_no_r portID ange start_mail_box_no end_mail_box_no diversion_flag vs_message recID received_recID msgID mail_box_no portID

20

20 20 1

voice system message waiting 20 voice system reason codes

vs_reason_codes PortID reason_code reason_text sub_activation_ex subscriber_recID piration activation_time expiration_time options description vs_diversion rec_ID is_diverted_recID divID

1 80

subscriber to be activated time to activate time to expire 80 description of activation voice system diversion

237

Application Data

Dynamic Network Administration Technical Guide

Table Name

Field Name mail_box_no portID

Field Type varchar int

Max Characters 20

Description

Extension Manager Database Organization

Table Name accnt Field Name accountcode description acdpam acdnum acdval acdmisopt acdsup acgrp extno groupno traffic limno queuelen service selcat qindchannel cust name1 name2 info pres sat aveconvtime bkgroupno acmem groupno extno clericaltime qpriority Field Type varchar varchar smallint smallint smallint varchar varchar smallint smallint varchar varchar varchar varchar smallint varchar varchar varchar varchar smallint smallint varchar varchar varchar smallint smallint 5 5 5 null null 20 20 20 2 null null null null null null null 11 10 5 3 5 5 null null null null null null null null Max Default Characters 15 60 null

238

Dynamic Network Administration Technical Guide

Application Data

Table Name

Field Name qpritype

Field Type smallint varchar smallint varchar varchar varchar varchar varchar varchar varchar smallint varchar varchar varchar smallint smallint varchar smallint smallint smallint smallint smallint smallint varchar varchar varchar smallint varchar varchar varchar smallint varchar

Max Default Characters null 5 null 8 8 9 6 1 11 1 20 20 20 2 null null null null null null null null null null null null null 5 null null null null null null 4 20 20 64 5 5 10 null null null null null null null

adn

extno catno traffic service calldivcat routingcat transcat addcat callalt cust name1 name2 info pres datype

ancdgrp

ancd lim serv sel traf cust sat maxtim name1 name2 pres status

ancdmbr

ancd sat node distno

239

Application Data

Dynamic Network Administration Technical Guide

Table Name

Field Name string startTraf status

Field Type 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 varchar varchar varchar varchar int

Max Default Characters 20 64 null null null

anndesc

annnum annname

60

null null

apppam

pamnum pamval

authcode

authcodeno calllogcode comcat checkcode dir cust csp

7 6 null null null 5 null null null 5 5 5 8 9 9 6 9 4 1 20 20 20 2 null null null null null null null null null null null null null null null

auxana

extno prianano auxananext cat traffic service calldivcat routingcat addcat icat transcat cust name1 name2 info pres

bcrelease

bc

240

Dynamic Network Administration Technical Guide

Application Data

Table Name bpos callbyname

Field Name id dir name1 name2 type aux

Field Type 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

Max Default Characters 9 20 20 20 10 5 null null null null 20 20 20 2 null null null null null null

cbgrp

groupno traffic service queuelen cust name1 name2 info pres

channel

icuind node cho status

null null 64 5 5 26 4 null null null null 5 60 null null 5 null

chgrp comabb

groupno comabbno transno class cust

comabbdesc

comabbno description cust

comabbinfo

comabbno status

comdiv

comdivno

10

null

241

Application Data

Dynamic Network Administration Technical Guide

Table Name

Field Name divtype cust

Field Type int smallint 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

Max Default Characters null null 5 5 3 5 null null null

compg

pageno searchcode speechsrcarea pagecat

compgm

pageno psano

comsrvprf

cspno traf serv cdiv roc npres desc

10 12 8 6 3 60 5 8 13 48

null null null null null null

cordless

extno access authkey ipei authpar

null null null null null

corg

operator_id corg_id primary_f

cpagrp

cpgrpno cpagrpno

5 5 5 null 11 5 5 null

cpgrp

groupno limno

csta cstagrp

equ cstano odnno

242

Dynamic Network Administration Technical Guide

Application Data

Table Name

Field Name adnno odnkey adnkey

Field Type varchar varchar varchar varchar varchar smallint varchar varchar int varchar smallint smallint smallint varchar smallint smallint varchar varchar varchar varchar varchar varchar varchar varchar varchar smallint smallint smallint smallint varchar varchar

Max Default Characters 5 3 3 14 11 null null 14 14 null null null

cstaiodev

iodevice equ devtype

cstalgrp

linkgroupid iodevice

custinfo

custno custname

30

null null null null

custmusic

custno parkedann queuedann

dat

extno tau datcat traffic service termcat transcat routingcat devtype modgrp addcat

8 2 10 14 2 10 5 6 5

null null null null null null null null

datapool

dpnum dpgrp dptype

dayn

route type extno trunk

null null 5 6 null null

243

Application Data

Dynamic Network Administration Technical Guide

Table Name dcat

Field Name catno traffic service termcat transcat routingcat descp

Field Type smallint varchar varchar varchar varchar varchar varchar int varchar varchar varchar varchar smallint smallint varchar varchar varchar smallint varchar varchar int varchar varchar smallint varchar smallint varchar varchar smallint varchar

Max Default Characters

8 2 10 14 2 30

null null null null null null null

deftfunc

insttype keyno ktype kvalue

3 3 5 5 null null 2 4 5 null 5 5 3 5 null null null null null null

dgrp

groupno traffic service modemgrpno disturbinfo

dgrpstatus

groupno used

dirpg

pageno searchcode speechsrcarea pagecat

dirpgm

pageno psano

dnisnums

dnisnum used

5 null 5 5 null 20 null

dnisused

dnisnum servgrp servtype name1

244

Dynamic Network Administration Technical Guide

Application Data

Table Name

Field Name name2 info pres

Field Type varchar varchar varchar smallint smallint varchar varchar varchar varchar varchar varchar smallint smallint varchar varchar int varchar varchar smallint varchar varchar int smallint int int varchar varchar varchar varchar varchar

Max Default Characters 20 20 2 null null null

emdev emdevname

emdevnum dmdevnum devname

60 11 60 5 255 5

null

equloc

equpos location

null

extdesc

extno description

null

extinfo

extno type status

null null 5 5 3 5 null null null

extpg

pageno searchcode speechsrcarea pagecat

extpgm

pageno psano

gdgrp generic

groupno extno csp cust lim type name1 name2 info pres

5 5 null null 20 20 20 2 5 null null null null

grprva

grpno

245

Application Data

Dynamic Network Administration Technical Guide

Table Name

Field Name welno queno reqrueno cidreqno ewta

Field Type 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 varchar varchar

Max Default Characters null null null null null 5 null null null null 9 3 20 20 20 2 null null null null null null null

hgrp

groupno traffic queuelen limno trunkcat service selcat cust name1 name2 info pres

histtaskinfo

taskid batchid procid procinfo status resultdesc

2048 null 255 5 26 2 null null null

hot

hotfrom hotto hltype

icuequ

icuind equ

11 5 10 5

null

idiv

idivfrom idivto

null

indabb

extno

246

Dynamic Network Administration Technical Guide

Application Data

Table Name

Field Name indabbno type transno

Field Type 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

Max Default Characters 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

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

247

Application Data

Dynamic Network Administration Technical Guide

Table Name

Field Name batchid procid primkey1 primkey2 viewname marked

Field Type int int varchar varchar 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

Max Default Characters

32 32

null null

mdmgrp mdn

id odnno mdnno keyno callalt

5 5 3 1 5 5 null 5 5 20 5 5 null null 5 null 9 8 9 6 1 11 1 3 null null null null null null null null null null

memgrp

grpno grpmem type initorder

mns

odnno mnsno dig

msgint

extno term typeintserpos

odn

extno catno traffic service calldivcat routingcat transcat addcat callalt insttype

248

Dynamic Network Administration Technical Guide

Application Data

Table Name

Field Name cust name1 name2 info pres datype lang

Field Type smallint varchar varchar varchar varchar smallint smallint varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar int char varchar varchar smallint smallint varchar varchar smallint smallint varchar varchar

Max Default Characters null 20 20 20 2 null null null null null null 5 5 3 5 3 3 5 20 5 5 3 null null null null

odnadn

adnno odnno keyno

odnfunc

extno keyno ktype value dig

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 null null

249

Application Data

Dynamic Network Administration Technical Guide

Table Name pninfo

Field Name extno profile position answerno timeout busygoto frinternal froperator frpublic useonce

Field Type varchar smallint smallint varchar smallint smallint smallint smallint smallint smallint varchar smallint varchar varchar smallint varchar varchar varchar varchar varchar varchar varchar varchar smallint varchar varchar varchar varchar smallint smallint smallint varchar

Max Default Characters 5

20

null null null null null null null

pnstatus

extno profile

5 null 5 5 8 9 9 6 9 1 4 4 20 20 20 2 null null null null null null null null null null null null null null null

priana

extno auxno cat traffic service calldivcat routingcat addcat transcat insttype icat cust name1 name2 info pres

psarea

searchareano blockingtime repetitionno signaldiagtype

null null 3 null

250

Dynamic Network Administration Technical Guide

Application Data

Table Name

Field Name signaldiagvar holdingtime

Field Type varchar varchar varchar smallint smallint char char smallint smallint smallint int int smallint smallint varchar varchar varchar smallint varchar varchar varchar smallint varchar int varchar varchar int int int int

Max Default Characters 10 6 8 2 null null

rfp

bpos rpn

route routrunk

id id equpos route_id

11 11

null null

rvadata

annnum rvanum annfrom annto devtype

null null null

rvamsg

msgnum msgname

60 5 5 10 1 4

null null null null null null null null

satgrp

sat ancd node oflno inftyp ofltim ovflow

sms

extno msgserver iodevice

5 14 5 null null

spext

extno specexttype

taskinfo

taskid batchid procid

251

Application Data

Dynamic Network Administration Technical Guide

Table Name

Field Name procinfo status resultdesc

Field Type varchar smallint varchar varchar varchar varchar varchar varchar smallint varchar smallint varchar varchar varchar varchar varchar varchar varchar varchar

Max Default Characters 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

null null null null null

vmport

extno portno infocomind

null

PDM Database Organization

Table busy c_bell cfp code_r code_s confer cxnmob 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)

252

Dynamic Network Administration Technical Guide

Application Data

Table cxntrf datext dialdy extens ipbrd keyc_r keyc_s measinfo modgrp opcorg opindi opmann pagext pagsar pbxgrp pcmlin roubwy rouddi roudio rouinc rouout tone_r Trunks

Includes Data For Cordless Extensions Fixed Part (for BC11 or later) Data extension Dial tone delay Voice extension IP Extensions Key code receiver Key code sender Measurements initiated by the user 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

253

Application Data

Dynamic Network Administration Technical Guide

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.

D.N.A. Directory Manager Directory Manager is a day-to-day administrative Application application for both populating and managing the contents of Operator Workstation subscriber records.

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.

Operator Console Settings

Operator Console Configuration settings are stored in the Windows Registry under the HKEY_LOCAL_MACHINE\SOFTWARE\Ericsson\OPI\CurrentVersion key.

254

Chapter 13 MML Commands

Extension Manager
The Extension Manager Application uses the following MML commands in its communications with the PBX. Note: Only a subset of these commands are available in the Ericsson IP-PBX. Please consult the Ericsson IP-PBX O&M for details. Consult the EMG Users Guide for a list of functional differences between the MD110 and the Ericsson IPPBX. Functional Grouping Automatic 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

Automatic Network Call Distribution

Abbreviated Dialing Account Code

Application System Parameter ASPAC Authorization Code System Time Common Bell Group Call Diversion Charging Cordless Extension CSTA AUCOE AUCOI CATII CBCAC CBELI CBGME CBGMI CDCOE CDCOI CDINE CDINI CHGME CHGMI CXAKE CXAKI CSTPE CSTPI CSTLE CSTLI

255

MML Commands

Dynamic Network Administration Technical Guide

Functional Grouping 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

Commands DGCAC DGGME DGGMI DGGRE DGGRI DTCAC DTCCS DTEXC DTEXE DTEXI DTFUI ACTNI ACTNE EXCCS EXCAC EXCUC EXDPC EXTEE EXTEI GEDIC GEDIE GEDII GDNDE GDNDI GHCAC GHGME GHGMI GHGRI GPAGE GPAGI GPGME GPGMI GESPC GESPE GESPI DTCCS EXCCS IVBOI IVMAI IVMAE IVBOE

Interception Service & Message ISEPE ISEPI Waiting ISDN Terminal Digital Key System Telephone ITCAC ITCUC ITNUE 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 PEALC PELPC PELPE PELPI

Personal Number

256

Dynamic Network Administration Technical Guide

MML Commands

Functional Grouping Route Data Special Purpose Extension Voice Mail

Commands RODNE RODNI SPEXE SPEXI VMPOE VMPOI

Recorded Voice Announcement RADSE RADSI RAGAI RAGAE RAGAC RAMDE RAMDI Music On Hold Per Customer IP Extension Mobile Extension Short Message Service CUMHI CUMHE IPEXI IPEXE IPEXC REEXI REEXP REEXE NUTRI NUTRE 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 PBX. Note: Only a subset of these commands is available in the Ericsson IP-PBX. Please consult the Ericsson IP-PBX O&M for details. Functional Grouping Calendar Data and System Identity Digital Extension Analog Extension Data Extension ISDN Extension Number Series Name Identity Group Hunt Commands CADAP

KSCAP KSDDP KSTSP KSFKP KSMDP EXCAP EXDDP EXCCP DTCAP DTCCP DTDDP DTFUP ITDAP NADAP NIINP GHDAP

257

MML Commands

Dynamic Network Administration Technical Guide

Functional Grouping Automatic Call Distribution Automatic Network Call Distribution Common Bell Group Operator Data Group Modem Group Charging Group Group Call Pickup Group Do Not Disturb Account Code Authorization Code Intercept Computer

Commands ACGMP ACGCP ACPAP ACBGP NCNOP NCICP NCGRP NCGMP NCGSP NCSGP CBDAP OPDDP OPCGP OPRSP DGDAP MGMGP CHGMP GPDAP GDNDP AOCOP AUCOP ICFUP

Recorded Voice Announcement RAGAP RAMDP Special Purpose Extension Trunk Paging Abbreviation Call Diversion Voice Mail Message Interception SPEXP RODNP ROCAP ROEDP RADSP RADNP PAEDP PADAP PAALP ADCDP ADIDP CDIDP CDCDP VMPOP ISEPP

258

Dynamic Network Administration Technical Guide

MML Commands

Functional Grouping Computer Support Telephony Applications

Commands CSTPP CSTLP

Application System Parameters ASPAP 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 Mobile Extension Short Message Service CNPIP CNLIP CNBIP SYEDP SYEVP GJLCP PCLOP SUDIP SUSIP GEDIP GESPP CXAKP ACTNP PELPP NUTRP IONCP IVMAP IVBOP CUMHP IPEXP REEXP MSCOP

Performance Data Manager

The Performance Data Manager (PDM) application uses the following MML commands in its communications with the MD110.

259

MML Commands

Dynamic Network Administration Technical Guide

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

Commands TRCBI TRCOI TRCRI TRCSI TRDDI TRDIP TRDXI TREXI TRCFI TRKRI TRKSI TRMEE TRMGI TROMI TROPI TRPBI TRPGI TRPLI TRROI TRTLI TRTRI

260

Dynamic Network Administration Technical Guide

MML Commands

Functional Grouping Read traffic measurement data from MD110 HDU

Commands FIFCP

Specify Cordless Extension Common Fixed Part TRCFI 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 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.

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 PBX Features

Note: Only a subset of these features is available in the IP-PBX. Please consult the Ericsson IP-PBX O&M for details. ! ! ! ! ! ! ! ! ! !
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

261

MML Commands

Dynamic Network Administration Technical Guide

! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !

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 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

262

Dynamic Network Administration Technical Guide

MML Commands

!
!

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 to D.N.A.

To set up other schedule utilities to run MD Support

1. Set up an account in DNA having the same name as the Windows account. Assign the MD Support privilege to this account. 2. Scheduled a synchronization job running MDS. For example: ! mds.exe /site:1

263

Chapter 14 Frequently Asked 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\DNADir50.ocx or DNA_C\Share\bin\DNADir50.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: How do I change the starting day of the week for the calendar in the Activation tab, when adding or updating a user? Answer: You can change the starting day of the week by changing the CalendarFirstDay value under the HKEY_CURRENT_USER\Software\Ericsson\DMG\CurrentVersion Registry key. Use the following values: 0 1 2 3 4 5 6 Monday Tuesday Wednesday Thursday Friday Saturday Sunday

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.

265

Frequently Asked Questions

Dynamic Network Administration Technical Guide

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. Server
Question: Why do I repeatedly see the warning "PBX watchdog timed out" in the event log? Answer: This warning shows up if the Ericsson PBX Service is running but does not have a connection to the MD110 via a CT-adapter. If you do not plan to use OWS on your D.N.A. Server you can stop the messages by running the OWS / PBX Extension Line control panel program and set the com port to none. Question: Is it true that you should not configure a D.N.A. Server as a Primary Domain Controller (PDC)? We have a customer who has made their D.N.A. Server the Wins and PDC on their Windows domain for about 60 PCs. 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 with more than 20 operators, you have a lot of changes made to the database, and are using the diversion and messaging facilities. 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.

266

Dynamic Network Administration Technical Guide

Frequently Asked Questions

To determine if the problem is the server or the network/network card, run Windows 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 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 and they work fine. Important! Microsoft does state that you should never install SQL on a PDC, as it does affect system performance.

Operator Workstation
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 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. 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 ICU-board. This SCS Server must be a Windows 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 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 re-established 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.

267

Frequently Asked Questions

Dynamic Network Administration Technical Guide

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 Windows server is running with a Norwegian Windows workstation. Solution: The problem is in the default configuration of the Norwegian Windows Workstation and the English Windows Server. When installed, they default to Disable Distributed COM. To solve this problem: 1. Login as the Windows Administrator. 2. Run DCOMCNFG.EXE. You should find this file under the WINNT\System32 directory. 3. In Default Properties, select Enable Distributed COM. Enabling this flag eliminates this Operator Workstation crash problem.

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?

268

Dynamic Network Administration Technical Guide

Frequently Asked Questions

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). 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.

269

Frequently Asked Questions

Dynamic Network Administration Technical Guide

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 D.N.A. 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. 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.

270

Dynamic Network Administration Technical Guide

Frequently Asked Questions

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. However, starting from Windows 2000, the operating system provides support for restarting failed services. This provides equivalent functionality as the Standby Remote Data Server and is the preferred alternative. Open the RDS service properties in Windows Service Control Manager and display the tab called Recovery. Set First, Second, and Subsequent failures to Restart the service. Set reset failure count after 1 day and restart the service after 0 minutes. Save the configuration. Open RDS Configuration and disable Standby Service. 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. Question: Why do some MD110 PBXs fail to properly clear and/or update active diversions, even when the Ericsson RDS service has been verified as running? Answer: In BC11 SP2 and later, a new code (04) exists in the GICI protocol. The 04 will trigger a 54 response from the MD110 (DIM clears active diversions before sending 54). Check for presence and proper value of the following Registry key:
HKLM\SOFTWARE\Ericsson\MRS\RemoteDS\Manager\ EnableDNAGICIInitiateUpdateRequestToPBX

Format: N/A Value: [REG_DWORD] 0=disabled (default value); 1=enabled For a previously installed D.N.A. server, the administrator needs to start the "Ericsson RDS" service at least once for the Registry key to be created (with the default value). If the Registry key value is subsequently modified, the "Ericsson RDS" service must be stopped and restarted for the changes to take effect.

271

Frequently Asked Questions

Dynamic Network Administration Technical Guide

Note that this Registry key supercedes:

HKLM\SOFTWARE\Ericsson\MRS\RemoteDS\Manager\EnableDNAGICIUpdatesTo PBX If EnableDNAGICIInitiateUpdateRequestToPBX is set to 1, then EnableDNAGICIUpdatesToPBX will be ignored, since it is no longer relevant.

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 D.N.A. 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.

Performance Data Manager

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: B at chT i me , DWord , and enter the hour in hexadecimal. Example: Enter Batc hT ime= 0A if you want to start PDM downloading at 1000 Hours. 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\<computer name>Siten 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 nodes 2 and 4 should be polled, set the Registry string to 1,3,5, (end with a ",")

272

Dynamic Network Administration Technical Guide

Frequently Asked Questions

Question: Which 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.

D.N.A. Application Suite

Question: What different releases for D.N.A. exist? Answer: The following table contains the releases of D.N.A. that are supported. Version DNA 4.1 DNA 5.0 DNA 5.1 DNA 5.3 DNA 5.4 Release Information DNA 4.0 bug fixes, Outlook integration, and DDB General release version of DNA5 General release version of DNA 5.1 and BC12 support General release version of DNA 5.3 and BC12.1, and Ericsson IP-PBX support. General release version DNA 5.4 and MXONE Telephony System Telephony Server (TSE).

MD110
Question: What ASPAC parameters are available for operator functions? Answer: The following table list ASPAC parameters. ASPAC Format 2 9 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. 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.

10

PARNUM=10,PARVAL=DDDDD

0 - 32768 seconds

14

PARNUM=14,PARVAL=DDD

10 - 100 in 0.5 second units

15

PARNUM=15,PARVAL=DDD

10 - 100 in 0.5 second units 100 - 10000 in 0.2 second units

16

PARNUM=16,PARVAL=DDDDD

273

Frequently Asked Questions

Dynamic Network Administration Technical Guide

ASPAC Format 17 PARNUM=17,PARVAL=DDDD

Range 50 - 6000 in 0.2 second units

Description 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.

33 34

PARNUM=33,PARVAL=D PARNUM=34,PARVAL=D

0 - not allowed, 1 allowed 0 - manual, 1 automatic 0 - not allowed, 1 allowed 0 - 32768 seconds

36 38

PARNUM=36,PARVAL=D PARNUM=38,PARVAL=DDDDD

39

PARNUM=39,PARVAL=DDDDD

0 - 32768 seconds

40

PARNUM=40,PARVAL=DDDDD

0 - 32768 seconds

57 76

PARNUM=57,PARVAL=D PARNUM=76,PARVAL=D

0 - not allowed, 1 allowed 0 - not allowed, 1 allowed 0 - 12 hour, 1 - 24 hour 0 - manual, 1 automatic 0 - yes, 1 - no

101 102 175

PARNUM=101,PARVAL=D PARNUM=102,PARVAL=D PARNUM=175,PARVAL=D

195

PARNUM=195,PARVAL=DDD

99 - 255 calls in queue

Registry
Question: What are the following Operator Workstation Registry keys used for? Answers:
HKLM\SOFTWARE\Ericsson\OPI\CurrentVersion\Number

274

Dynamic Network Administration Technical Guide

Frequently Asked Questions

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-D.N.A. 4 method.
HKLM\SOFTWARE\Ericsson\OPI\CurrentVersion\Secrecy

This key holds the feature access code for the Business Phone secrecy feature.
HKLM\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.
HKLM\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.) If the server fails to restart, 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 "s q lse r vr Command-line Executable.

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.

275

Frequently Asked Questions

Dynamic Network Administration Technical Guide

When you have both a CCM and a D.N.A. server present in one Windows 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:
HKLM\SYSTEM\CurrentControlSet\Services\ClockSync\Parameters \ServerMachineName

The use of Windows 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 D.N.A.) 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 D.N.A. server, and then change all the CCM client machines to ask the D.N.A. 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.

Export
Question: When will Export.exe export the confidential UDF fields? Answer: Export.exe will export confidential UDF fields when it's running in: ! ! Interactive mode Batch mode with the "/c" switch (e.g., from the command prompt, enter export batch /c).

The only case when Export.exe will not export the confidential UDF fields is when it is running in: ! Batch mode without the /c switch (e.g., from the command prompt, enter export batch).

Note: A confidential UDF field is a UDF field defined in the Confidential tab in Directory Configuration.

Ericsson Communication Assistant

Question: What settings do my Internet Explorer 5.5 or 6.0 browser need to run ECA properly?

276

Dynamic Network Administration Technical Guide

Frequently Asked Questions

Answer: Under "Internet Options" Security tab you need to set "Allow cookies that are stored on your computer" to enable. Question: Why do I get the error message "PBX dialing information is not completely defined"? Answer: In order to make TAPI format dialing work the system administrator need to define country code and area code for the D.N.A. system. Please have the administrator run RDS Configuration and select the "PBX Dialing Extension Information" tab to define those settings. Question: I changed the "Place call from" setting in "Personal Options" but when I log on next time ECA will still use my primary number for call handling? Answer: After a new logon ECA will always use the subscriber's primary extension as the call handling number. The setting "Place call from" does only apply to the current session and is not saved after logoff. Question: Can I use favorites or bookmarks to access pages inside ECA? Answer: No. Due to the fact that you always need to logon first to be able to use ECA, you can not use favorites or bookmarks that bypass the logon screen. You can of course bookmark the first page of ECA to easily access the application. Question: When first displaying the ECA log on page my simplified Chinese characters do not show up, why? Answer: Make sure that your encoding in Internet explorer is not set to "Auto Select". This setting is found under View / Encoding. Question: Can I use Netscape 6.0 and the simplified Chinese version of ECA? Answer: No. Netscape 6.0 does not have a Chinese version and can therefore not support ECA Simplified Chinese. Question: What extension types can be used with ECA call handling features? Answer: Digital phones, analog phones, cordless phones, IP phones, and Mobile Extension. To make a call on an analog phone, you must pick up the handset first.

277

Chapter 15 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, RYS 109 004/1 R6A V1.4.8 Dec 23 1998 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: 6. (M)odify any of this, (C)ontinue or (A)bandon changes? [M] 7. 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 ru n SOF T imag e? 0 . D on 't r un SO FT i ma ge , s to p in BO OT s he l l 1 . R un th e S O FT im age W h ich one d o you w ant? [ 1 ] 1 Sec urity: Ch ang e use r Id an d /or p asswor d? [N ] n Cha nge this to Y if yo u wan t to ha ve a new lo gin_ na me /passwo rd H ARDW ARE P AR A M ET ER S : Ba ud ra te fo r s er ia l cha nne ls [9 60 0 ] D o y ou w an t t o c ha nge t he b oard 's M AC a dd r es s es ? [N ] U s e E th er ne t in t er face ? [Y] T h is bo ard 's Ethe rne t IP ad dress?

279

Configuration

Dynamic Network Administration Technical Guide

= R AR P) [16 4 .48 . 71 .16 6 ] Su bne t mask for Ether ne t? ( 0.0 .0 .0 for n one ) [255 .255 .255 .1 92 ] Eth erne t Ma ximum Tra nsmiss ion Un it? [1500 ] Do you want a PPP interface? [N] Sh ou ld th er e be a de fa ult ga tewa y for packe t r ou tin g? [Y] Wh a t is its IP ad dress? [164 .48 .71 .129 ]

To check for Telnet access

1. 2. 3. 4. 5. 6. 7. 8. 9. Go into Telnet somewhere on a network PC Type in the IP-address of the Agent Type in Login name (name you gave to your Agent host) Type in your password (password you gave to your Agent host) Now you should get a $-sign. This means you are in the Unix operating system of the Agent. Type after $-sign: ls -l. This will give you the directory of the UNIX RAM-disk . 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) Type after $-sign: tncom mml and then send your SSSSS as a normal synchronization. You should be able now to synchronize with the MD110. 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. 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. 2. 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. 3. Login with your login_name and password. 4. Type bin for binary download 5. Type get comport.cnf, and the file will be downloaded to your local disk 6. Change the comport.cnf file to your demands (i.e., add entry GICI): (Sample c o m p or t .cn f file) #------------------------------------------------------------------# Lines starting with '#' are comment lines. # # FILENAME: comport.cnf # Configuration file for the command tncom.

280

Dynamic Network Administration Technical Guide

Configuration

# 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".

281

Configuration

Dynamic Network Administration Technical Guide

! ! !

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> !

TCP/IP Protocols and Port Number Assignments

Service netstat ftp-data ftp telnet smtp nameserv nicname nicname login domain domain tftp gopher gopher finger finger Port 15 20 21 23 25 42 43 43 49 53 53 69 70 70 79 79 Type ? TCP TCP TCP TCP ? TCP UDP ? TCP UDP UDP TCP UDP TCP UDP Description 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

282

Dynamic Network Administration Technical Guide

Configuration

Service www-http kerberos kerberos pop3 sunrpc sunrpc auth auth ntp nntp ntp netbios-ns netbios-dgm Netbios-ss sqlsrv snmp snmp snmptrap snmptrap bgp imap3

Port 80 88 88 110 111 111 113 113 119 123 123 137 137 150 156 161 161 162 162 179 220

Type TCP TCP UDP TCP TCP UDP TCP TCP TCP TCP UDP ? ? ? ? TCP UDP TCP UDP ? TCP

Description 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 SNMPTRAP Border Gateway protocol Interactiv Mail Access Protocol

283

Configuration

Dynamic Network Administration Technical Guide

Service imap3 exe login who cmd syslog printer talk talk ntalk ntalk router uucp uucp uucp-rlogin uucp-rlogin klogin klogin pmd pmconsole radius

Port 220 512 513 513 514 514 515 517 517 518 518 520 540 540 541 541 543 543 1642 1643 1645

Type TCP TCP TCP UDP TCP UDP TCP TCP UDP TCP UDP UDP TCP UDP TCP UDP TCP UDP TCP TCP UDP

Description 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

284

Dynamic Network Administration Technical Guide

Configuration

Service radacct

Port 1646

Type UDP

Description RADIUS Accounting

Web Site Security

If you have installed D.N.A. Web-based applications such as PPMLite, Ericsson Communication Assistant, Mobile Executive, or Personal Assistant, you may want to set up SSL security for the Web site. This involves the use of Certificate Authorities (CA). There are several CAs on the Internet that will issue certificates and Verisign (www.verisign.com) is one of the largest. If you are also running Certificate Server, you can issue your own server certificate. To request a certificate from a CA, you need to generate a New Key Request from the Key Manager and send it to the CA. To use Key Manager you must have Internet Service Manager and Internet Information Server installed. This feature is standard in Windows 2000 and later. Note: Client-side browsers will not automatically trust the certificate that you generate since it is not a well-known CA such as Verisign, however they will still work.

Windows 2000 Server and Windows Server 2003

Please refer to the following Microsoft site for SSL setup with IIS 5.0 or 6.0: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q298805&sd=tech With SSL security, you prefix your URL with https:// instead of the usual http://. For example, change http://www.mysite.com/ppmlite to https://www.mysite.com/ppmlite.

Setup D.N.A. Web Applications on Windows 2003 and IIS 6.0

Configurations setup automatically by D.N.A. installation
The following settings are configured by D.N.A. Web Application installations automatically and D.N.A. Web applications will run properly with these configurations.

Enable the ASP Web Service Extension in IIS 6.0

IIS 6.0 is installed in a locked-down state. It can only serve static content (plain HTML pages, text, etc.) with its default configuration. For IIS 6.0 to be useful and serve dynamic content, the Active Server Pages and Server Side Include web service extensions should be allowed. These settings are configured by any of the D.N.A. web applications installation.

285

Configuration

Dynamic Network Administration Technical Guide

Enable the parent path property in the virtual directory

Many ASP applications (such as the Ericsson D.N.A. ECA web application) require the use of parent path notation to access include files, images, etc. In Windows 2003 Server, parent paths are turned off by default. This will cause certain applications to show an Internal Server Error when the Web application is accessed. This setting is per virtual directory.

NTFS Permissions
The NTFS permissions needed for D.N.A. web applications files and directories are also granted to the IUSR account during D.N.A. installation. The NTFS permissions set are: Directories \dirb\data NTFS permission Modify D.N.A. Applications Ericsson Communications Assistant, ECC, and Mobile Executive Mobile Executive PPMLite

\mobileexec\bin \ChartJPEG

Modify Modify

Configurations to Run D.N.A. Web Applications in Worker Process Isolation Mode

You can follow the procedures below to manually configure the D.N.A. Web Applications to take advantages of IIS 6.0 new features. These steps are optional.

D.N.A. Server and Web Application on the Same Machine

These are the steps to setup ECA when it is on the same machine as the D.N.A. server, either in a workgroup or a domain.

Create Custom User Identity

1. In the Computer Management console, click on the Local Users and Groups section on the left tree, right-click on the Users folder, and select New User.

286

Dynamic Network Administration Technical Guide

Configuration

2. Configure according to the following screenshot. (Enter your own password and remember it!) Once configured, the EricssonWeb account can be used for other Ericsson Web applications as well.

287

Configuration

Dynamic Network Administration Technical Guide

3. Assign the EricssonWeb account to the proper groups, Administrators, Users and IIS_WPG. IIS_WPG is a Windows 2003 account group that allows the user privilege to run an IIS 6.0 application pool, called a service account.

Assign NTFS Permissions

The EricssonWeb service account will need to have the proper privileges to read/write/modify files and directories that Ericsson Web Applications use. Refer to the table listed in section NTFS Permissions of Configurations setup automatically by D.N.A. installation for details.

Create New Application Pool

1. In the IIS Manager, right-click on Application Pools, Select New, then Application Pool.

288

Dynamic Network Administration Technical Guide

Configuration

2. It will pop up a dialog prompting you for the application pool ID. Enter EricssonWebPool and select the first radio button that uses the default settings.

3. Once the application pool has been created, right-click on EricssonWebPool and select Properties. In the Identity tab, select the second radio button and specify the EricssonWeb account that was created earlier in step 0. Enter in the correct password. Click OK. It will then ask you to reconfirm your password. Type in your password and click OK again.

289

Configuration

Dynamic Network Administration Technical Guide

4. Make sure that the application pool has been started by refreshing the IIS Manager view (i.e., click on the Action menu and then Refresh). A started application pool will have an icon with green arrows overlaid on top. A pool that has not been started will have a red x overlaid on top of the icon (possible cause could be that an incorrect password was entered). Please make sure it is running properly.

Assign Virtual Directory Application Pool (per Virtual Directory)

1. In the IIS Manager, configure each of the Ericsson Web Application virtual directories by right-clicking the name such as Ericom and selecting Properties. Under the Virtual Directory tab, in the Application Settings section, select the EricssonWebPool option from the Application Pool dropdown list.

290

Dynamic Network Administration Technical Guide

Configuration

Assign Virtual Directory Anonymous Identity (per Virtual Directory)

1. Go to the Directory Security tab. Under the Authentication and access control section, click on the Edit button. 2. An Authentication Methods dialog will pop up. Check the Enable anonymous access checkbox and select the EricssonWeb user that was created earlier. Enter the correct password as well. Also ensure that the bottom checkboxes are unchecked.

291

Configuration

Dynamic Network Administration Technical Guide

3. Click OK until all dialogs have disappeared.

Reset IIS
Go to the command prompt and enter iisreset. Wait until it is finished and then test the D.N.A. Web applications to make sure they are working as expected.

D.N.A. Server and IIS 6.0 Server on Different Machines

D.N.A. Server and IIS 6.0 Server in the Same Domain
The D.N.A. Web Application will need to access data on the D.N.A. server, which means the D.N.A. Web Application needs to be properly authenticated on the D.N.A. server with a domain user account that has the correct privileges. 1. The EricssonWeb account created in section D.N.A. Server and Web Application on the Same Machine is a local account on the ECA Server. For this scenario, the EricssonWeb account needs to be created as a domain account. Instead of creating the account on the IIS 6.0 server, create it on the domain controller. For example, on the domain DNA, the user would be accessed by specifying DNA\EricssonWeb.

292

Dynamic Network Administration Technical Guide

Configuration

2. Once the domain account has been created, on the IIS server, add DNA\EricssonWeb to the IIS_WPG account group. 3. Follow the steps in Create Custom User Identify and Assign NTFS Permissions sections and specify the domain account DNA\EricssonWeb as the user identity for the application pool and the anonymous identity. Again, make sure the correct permissions are assigned to the data directories for this new domain account. 4. Verify that D.N.A. Web Applications are working properly.

D.N.A. Server and ECA Server in Workgroups

For the D.N.A. Web Application to access the D.N.A. server, they need to have a shared account. Perform the following steps: 1. The EricssonWeb account created in section D.N.A. Server and Web Application on the Same Machine is a local account on the IIS server. The EricssonWeb account must be authenticated on the D.N.A. server as well. For this to work under workgroups, the D.N.A. server must have the same local EricssonWeb account and password. On the D.N.A. Server, follow the steps in Create Custom User Identify and Assign NTFS Permissions sections so that there is an EricssonWeb account on the D.N.A. server and an EricssonWeb account on the ECA server. 2. Verify that D.N.A. Web Applications are working properly.

D.N.A. Port Assignments

D.N.A. 5.4
Windows named pipes (referred to as NP herein) use the following default port assignments: ! ! TCP 139 and 445 UDP 137 and 138 Port NP --NP 23 23 2555 Comment Uses Windows named pipes. Port value is set in RDS Configuration. Uses Windows named pipes. Default value. Telnet session. Default value. Telnet session. Default value (can be changed via CSTA GUI). Potential Clients SDS MD110 D.N.A. Client applications MD110 MD110 Application Link (via CSTA client)

System Component Logging Facility Service (LFS) Shot Message Service (SMS) Clock Sync ECA Scheduler MD110 Time IP Service

293

Configuration

Dynamic Network Administration Technical Guide

System Component PBX Service Security Data Service (SDS) Remote Data Service (RDS) GICI SMTP Time System Service (TSS) Voice System Service (VSS) Service () Ows Supervisor Service Local Data Service (LDS) Serial Communication Service (SCS) LDAP Service

Port --NP NP --25 NP NP NP --NP NP 389

Comment Uses COM-port (not connected to the network). Uses Windows named pipes. Uses Windows named pipes. Port value is set in RDS Configuration. Default value (port value is set in RDS Configuration). Uses Windows named pipes. Uses Windows named pipes. Uses Windows named pipes. Uses DCOM (i.e., ports in the range 1024 to 65535) Uses Windows named pipes. Uses Windows named pipes. Default value (can be changed via LDAP Server Configuration). Default value. Telnet session. Default value. Telnet session. Default value. Telnet session. Default value (can be changed via GUI). (Serverport) Default value Multicast Default value (can be changed via GUI). Call control and Intercept calls.

Potential Clients CT-Adapter D.N.A. Client applications (via LFS) RDS, LDS, D.N.A. client applications. MD110 SMTP E-Mail Server RDS RDS RDS OWS Supervisor application, RDS RDS RDS LDAP Server

Extension Manager (EMG) MD110 Support (MDS) Performance Data Manager (PDM) Enterprise License Manager (ELM)

23 23 23 2580

MD110 MD110 MD110 SDS

11740 DNA Mobile Executive (DME) 8082

SDS IIS

294

Dynamic Network Administration Technical Guide

Configuration

System Component

Port 80

Comment Default value (can be changed via GUI). Logon and Search, using HTTP. Default value (can be changed via GUI). Logon and Search, using HTTPS (SSL). Uses Windows named pipes. Default value (can be changed via GUI). Call control and Intercept calls. Default value (can be changed via GUI). Logon and Search, using HTTP. Default value (can be changed via GUI). Logon and Search, using HTTPS (SSL). Microsoft CDO Uses Windows named pipes. Default value Uses UDP. Default value (can be changed via Registry or ECC.CFG configuration file). Uses UDP (PortRAS). Default value (can be changed via Registry or ECC.CFG configuration file). Uses TCP (PortCallSignal). Default value. ESSP communication with MD110. Uses UDP. Default value. Dynamically allocated (can be changed via Registry or ECC.CFG configuration file). RTP packets, using UDP. (PortRTP)

Potential Clients WAP Device

443

WAP Device

NP Ericsson Communication Assistant 8082

RDS ECA Clients

80

ECA Clients

443

IIS

135 NP Ericsson Communication Client 1718 1719

Exchange Server RDS H.323 Gatekeeper Discovery H.323 Registration and Status

1720

H.323 Call control

9200

ESSP Control

2326 2444

H.323 Media Data

295

Configuration

Dynamic Network Administration Technical Guide

System Component

Port 2327 2445 80

Comment Default value. Dynamically allocated. RTCP packets, using UDP. Default value. Can be changed via GUI. Logon and Search, using HTTP. (PortDNAIIS) Default value. Can be changed via GUI. Uses HTTP. Default value. Can be changed via GUI. Uses HTTPS (SSL). ADSI Logon. ADO TM data retrival Default value. Can be changed via GUI. Search, using HTTP. Default value. Can be changed via GUI. Search, using HTTPS (SSL).

Potential Clients H.323 Media Data Control

IIS

Performance Presentation Manager Lite (PPM Lite)

80

Web browser

443

Web browser

389 1433 Personal Assistant P900 80

ADSI provider SQL Server Personal Assistant clients

443

Personal Assistant clients

Ericsson Communication Assistant

To setup end users Web browser
Internet Explorer
Do not set Internet security in Internet Explorer to High. When you set Internet security to High, cookies and session variables are disabled. ASP session management requires the client browser to have cookies enabled to support sessions. Without sessions, the IIS server and hence the ASP application cannot store state information and will not work properly.

Netscape 6 (and later)

In order for Ericsson Communication Assistant to run on Netscape 6 or later, the Java 2 runtime environment plug-in must be installed. This is required for Java Applet support. You can download it from http://java.com.

296

Dynamic Network Administration Technical Guide

Configuration

To setup Ericsson Communication Assistant user account

The two fields with data types USER ID and USER PASSWORD must be setup with the Directory Configuration utility to enable administrators to create Ericsson Communication Assistant accounts in Directory Manager. Refer to User ID and Password for ECA, ECC, and DME for details.

To configure Ericsson Communication Assistant Server

There is an ECA Configuration Tool that is used to define the ECA Server configuration settings. To access this tool, Start the ECA Configuration utility by selecting Start!Programs!D.N.A. Application Suite!Administration Tools!ECA Configuration.

Configuration for Call Handling and Diversions

To define ApplicationLink connection information 1. To configure AppLink, press the Add... button. The Application Link Information dialog is opened.

297

Configuration

Dynamic Network Administration Technical Guide

2. Enter the Node ID that will be used for call handling and/or diversions. Enter the AppLink Server that is the name of the PC where AppLink is installed for the selected node. Enter the Port number used for AppLink connection. It defaults to 2555. Click OK to save your configuration. To set up IP Service settings ! Turn on ECA log Specify the log file name and full path. Defaults to <D.N.A. directory>\eca\bin\eca.log. It is used to trace the events between the IP service, the browser, and AppLink events. Define IP Service port number The default port number is 8082.

To set up Access Code Define the leading dialing codes for Local, Long distance, and internal calls for outbound dialing use.

Configuration for other ECA Server settings

Press Option button to open Options dialog for defining other ECA Server settings.

298

Dynamic Network Administration Technical Guide

Configuration

Free Seating This feature allows user to logon to an extension other than his/her primary extension during the current session. This means user will be logged with primary extension next time. This feature is off by default. Show node number This feature allows showing node number in addition to extension number. It is on by default. Wait Time after Diversion response from Data Server ECA Server interfaces with Data Server i.e either LDS or RDS for message diversion. After ECA Server receives message diversion response from Data Server, it needs to wait for enough time to ensure that the Data Server processes the message diversion request on the switch. After this wait time, ECA Server will send the proper message diversion details to the ECA client. This wait time depends on various parameters like performance of Data Server, connection between Data Server and the switch, and performance of switch. ECA Server will rely on the wait time specified here in seconds. The default is 5 seconds. User defined information page

299

Configuration

Dynamic Network Administration Technical Guide

Administrator can create a page to provide information for users having logon problems. In the Ericsson Communication Assistant Configuration utility, enter the link to an information page in the User defined information page edit box. When it is defined, a link entitled "Having trouble logging on?" appears on the Logon page. Default language Administrator can choose the default language. This language will be used for the ECA pages without logging on and first time logon. User can choose his/her own desired language after logging on. The selected language will be the language used each time you log on. The language is set to English by default. Show diversion notes This feature allows ECA users to view diversion notes, if available. It is off by default. EMG is installed and Personal Number is used ECA personal number features is handled by the backend EMG process. Do not turn on this feature unless EMG is installed on the D.N.A. Server and personal number feature is used. Otherwise, the ECA logon process will be slowed. If this feature is on, refer to Configuration for Personal Number access. Internal directory name Administrator can define the preferred directory name for Local D.N.A. internal directory. This name will be used for Directory drop-down list for search. External directory name Administrator can define the preferred directory name for Local D.N.A. external directory. This name will be used for Directory drop-down list for search. Personal Directory ECA supports personal contact search for Outlook only. If Personal Directory is set to none, personal contact will not be available in the Directory drop-down list.

Configuration for Personal Number access

The Personal Number feature is supported via backend Extension Manager to send MML command to the appropriate PBX. The backend EMG runs under a fixed D.N.A. user SYSTEM. To create a SYSTEM user ! Run the D.N.A. User Configuration Utility to create user ID SYSTEM with password SYSTEM (capitalized, as shown).

300

Dynamic Network Administration Technical Guide

Configuration

Grant Extension Manager privilege to System account. Select Extension Manager from the applications drop-down list, then select the PBX node from the Element drop-down list, select Access from the privilege drop-down list, and then select Full from Settings drop-down list.

Note: The following Registry value is created by ECC Server installation on the ECC server: HKEY_LOCAL_MACHINE\SOFTWARE\Ericsson\ECC\CurrentVersion\EmgAndPersonalNumber with REG_SZ type, and default value = 0. The user has to change this value to 1 to enable Personal Number feature for ECC.

To test EMG communication with PBX It is important to make sure EMG can connect with the node(s) on the ECA Server. ! ! Launch EMG and logon with SYSTEM Setup Communications and connect to all the nodes grant to System account

Configuration for IP Service to use HTTPS

If SSL security is used for ECA, you can also make IP Service to use HTTPS instead of HTTP. Please be aware that enforcing SSL has no impact to call handling features. There are two Registry settings used by IP Service to determine if SSL is enforced or not. ! !
HKLM\SOFTWARE\Ericsson\ECA\IPService\UserSSL DWORD 1 This value is used to determine if SSL is enforced and send with HTTPS HKLM\SOFTWARE\Ericsson\ECA\IPService\PortToIIS DWORD 443

This value is used to determine which port to use

Personal Contact Search

ECA Personal Contact search supports multiple Exchange servers. To support Personal Contact search, Ericsson Communication Assistant uses WebDAV protocol to interface with an Exchange Server. Currently the versions of Exchange Server which support WebDAV protocol are 2000 and 2003. This means that Personal Contact search is only supported on 2000 and 2003 versions of Exchange Server. By default, Exchange Server 2000 and 2003 installs a default HTTP Virtual server which provides support for WebDAV. However, you should ensure that default HTTP server is installed before using this search feature. The existence of IIS virtual directory Exchange confirms that the default HTTP server is installed. In addition, MSXML 4.0 SP2 needs to be installed on the ECA Server to perform the Personal Contact search from ECA.

301

Configuration

Dynamic Network Administration Technical Guide

By default on Windows 2003 server, the Internet Enhanced Security Configuration option is on, this security feature must be turned off on the ECA Server if installed on Windows 2003 server.

To configure interface parameters with Outlook

Each individual Ericsson Communication Assistant user must configure his / her "Personal Options" settings to make the searching of Outlooks personal contacts work. For an end user it can be quite tricky to get all this information correct. The recommended practice is that the Ericsson Communication Assistant administrator provides this information to each user in some way before the users first logon attempt. Look at the following illustration.

The following parameters must be entered on the Ericsson Communication Assistant Personal Options page in order to perform Personal Contact search: 1. Exchange Server Domain name 2. NT User name and password 3. Exchange Mailbox: To know exact mailbox name, logon to Outlook Web Access, and place your mouse pointer over the Inbox icon. The Exchange Server Mailbox will be shown in the URL displayed in the status bar between "http://ExchangeServerName/exchange/" and "/Inbox/" folder." 4. Exchange Server name The administrator of Ericsson Communication Assistant has several options as to how to communicate this information to the end users. The administrator can just send an email containing the following information:

302

Dynamic Network Administration Technical Guide

Configuration

! ! ! ! !

Ericsson Communication Assistant login name and password Exchange users domain name NT username and password Exchange mailbox Exchange Server name

Ericsson Communication Client

ECC Port Usage
ECC uses the following ports by default for H.323 telephony communication. Note that it is possible to modify the default values during ECC Server installation, by modifying the Ecc.cfg configuration file. Reference the ECC Installation section for more details. H.323 Call Control 1719 (for Gatekeeper registration and status, using UDP) 1720 (for call signalling, using TCP/IP) 9200 (for ESSP communication with the MD110, using UDP) 2326 to 2444 (for RTP packets, using UDP) 2327 to 2445 (for RTCP packets, using UDP)

H.323 Media Data

H.323 Gatekeeper Discovery 1718 (using UDP)

Changing the default language setting for ECC

ECC will automatically detect the Regional Setting configured by Windows and load the appropriate language file based on that setting. All language files are installed by default with ECC, so no additional installation is necessary to switch to another language. To change the language in Windows, select the Regional Options applet from the Windows Control Panel. Select the desired language, and press OK. Restart ECC. It will automatically load the selected language, if supported.

Using ECC with a Virtual Private Network (VPN)

The following information is for connecting ECC to the PBX Gatekeeper via a Virtual Private Network, for remote users. There are three scenarios: Case 1: The VPN does not use Network Address Translation (NAT) In this case, the IP address assigned by the VPN client is set as the machine IP address. In this case, initialization of the H.323 interface and registration with the PBX gatekeeper is done with the VPN IP Address. No further input is necessary. Case 2: The VPN uses Network Address Translation (NAT)

303

Configuration

Dynamic Network Administration Technical Guide

In this case, the IP address assigned by the VPN client is not set as the machine IP address. Initialization of the H.323 interface must be done with the original machine IP address, but registration with the PBX gatekeeper must be done with the VPN IP address. To handle this case, check the box "Using VPN with Network Address Translation (NAT)" in the Network property page of the ECC Setup property sheet. If the IP address assigned by the VPN provider is known, it can be entered in the VPN Client Address field. If the complete IP address is not known, the first two or three octets can be entered. When ECC attempts to register with the gatekeeper, it will use the IP address entered in the VPN Client Address field. If registration fails, the ECC user will be prompted to enter the IP address assigned by the VPN provider. The prompt will display the IP address entered in the VPN Client Address field by default, so the user can just edit this field to enter the correct address. To avoid waiting for a registration timeout, you can check the box "Always Prompt for VPN Address." In this case, ECC will display the prompt for the IP address immediately, before attempting to register with the gatekeeper. Case 3: The VPN uses Tunneling via the WAN In this case, the IP address assigned by the VPN is bound to the network card, so there are two IP addresses displayed when using the command "ipconfig", the original machine IP address and the VPN IP address. In this case, the H.323 interface must be initialized with the VPN IP address. To handle this case, make sure you select the WAN address in the Network tab of the Settings options. Select the WAN address from the "Use Selected Network Adapter" drop-down list.

Monitor Feature Access for ECC

The Monitor feature is only available to the users with the proper access rights. The Monitor menu item in ECC will be disabled if the user does not have the access rights. Set up the access rights as described in the following section.

D.N.A. User Configuration

From the D.N.A. User Configuration Utility, enter the User ID of the account to which you want to add permission for the Monitor feature. Select Ericsson Communication Client from the drop-down list of applications, then select Monitor from the list of privileges and set Allow from the drop-down list of settings. Note: The User ID entered in the D.N.A. User Configuration Utility must be the USER ID UDF defined for ECC (see the section User ID and Password for ECA, ECC, and DME for more details). This is the User ID that is used to logon to ECC. Also note that the User ID entered in the D.N.A. User Configuration Utility is case sensitive, so it must be entered in the same case as it is defined in Directory Manager.

Restricting Display of External Numbers

304

Dynamic Network Administration Technical Guide

Configuration

By default, when a monitored subscriber makes or receives a call to or from an external party, the number of the external party will not be displayed in the "Other Party" field of the Monitor dialog box. This is for privacy reasons. To override this, and display the external party's number (when available), you must add the following Registry value, and set it to 1:
HKEY_LOCAL_MACHINE\Software\Ericsson\ECC\CurrentVersion\Display

Type:

DWORD

Value: 1 to enable display of external parties Note: This Registry value is not created by default, to avoid legal issues in exposing this feature to end users.

User ID and Password for ECA, ECC, and DME

Both USER ID and USER PASSWORD are used for ECA, ECC, and DME. If you change a user ID or a user password it will reflect on all applications.

D.N.A. Directory Configuration

! In the Profile tab, add a Data Type called "USER ID" with the desired Field Name. Making the user ID Searchable is optional. If set as searchable, it will be available for search in ECA. In the Confidential UDF tab, add a Data Type called "USER PASSWORD" with the desired Field Name.

D.N.A. Directory Manager

! ! ! From the main display, select the desired user and bring up the View/Update Subscriber dialog box. In the Profile tab, enter the user ID in the predefined USER ID field. In the UDFs tab, enter the user password in the predefined USER PASSWORD field.

User ID
When creating a User ID, Profile, Person, and Confidential UDF can be used. Confidential UDFs are the only ones that can be excluded when exporting directory data via batch mode. The USER ID field is also used for other D.N.A. applications. The D.N.A. Outlook Integration (DOI) and D.N.A. Notes Integration (DNI) are using the data type to validate the Windows user with a subscriber. They can also use COMPUTER name (which is the default) to validate the subscriber. DOI and DNI are used to send message diversion information between the users Calendar and D.N.A.

Password
When creating a password, the Confidential UDF is recommended but Profile and Person UDF can also be used.

305

Configuration

Dynamic Network Administration Technical Guide

Confidential UDFs are the only ones that can be excluded when exporting directory data via batch mode. Since user passwords are stored as plaintext in the database, they become visible in the export file when defined as Profile or Person UDF.

Operator Workstation
Improving the Performance of OWS
1. Run LDS on the OWS PC. This helps RDS synchronize the directory replications locally to the OWS. Use the following procedure to install LDS. Note that you must have logged in with a Windows administrator account to be able to perform the first step successfully. 2. Run the Windows Control Panel and start Services. Set the "StartUp" of the Ericsson LDS entry to Automatic. Then start the "Ericsson LDS" Windows 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 D.N.A. server. 4. Run the Registry Editor (REGEDT32.EXE) on the 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 OWS is running on. Also modify HKEY_LOCAL_MACHINE\SOFTWARE\Ericsson\LocalDS\UseLDS and set this key to 1. This will force OWS to connect to LDS on the client OWS PC rather than on the SP D.N.A. Server. Now the OWS is ready to use 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

306

Dynamic Network Administration Technical Guide

Configuration

Operator Workstation can load the MAPI library if a MAPI-compatible e-mail system has been installed. Microsoft Mail from Windows and Microsoft Exchange satisfy this requirement. Look for 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 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 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.

Personal Assistant for Smartphone

SSL access to D.N.A. directory
There is a virtual directory under IIS 1) 2) 3) 4) PersonalAssistant PersonalAssistant/ASP PersonalAssistant/ASP/ASPProfile PersonalAssistant/ASP/ASPFiles

The file GetProfile.asp (under PersonalAssistant/ASP/ASPProfile) can be set with a value of 1 or 2, as follows: 1 = Https Used (preconfigured to 1 for HTTPS) 2 = Http Used Note: If the Profile value is set to 1, the virtual directory, PersonalAssistant/ASP/ASPFiles, needs to have SSL access enabled by using the administrator tool, Internet Service Manager.

307

Chapter 16 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. In the D.N.A. system, subscribers VSI number and/or TSS number should be entered through the UDF fields. In order to have these fields visible in the users UDF tab, you must define those fields via Directory Configuration under the Person UDF tab.

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)

309

VSI and TTS

Dynamic Network Administration Technical Guide

1 - Passive (Do Not Divert Phone) SSSS Start date/time* 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

EEEE

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****

! * 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. If it contains 000000000000 then the default or indefinite date/time is specified. ! ** Even though the message text maximum is 160 characters, Max field length VoiceDesigner can handle 132 characters. Long messages must therefore be split into two parts. Max (actual) text in one message is 80 characters. ! *** 0 = Unknown, 1 = Message Diversion, 2 = Direct forwarding, 3 = Busy, 4 = No answer. These values are configured using VSI Configuration Utility. ! **** This is 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.

310

Dynamic Network Administration Technical Guide

VSI and TTS

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. The EMDIP protocol (Extended Message Diversion Interface Protocol) is optionally available. If selected, VSI will generate a heartbeat event to the client at 2 minute intervals. The client application is responsible for checking the heartbeat event, but it does not send a response. If two consecutive heartbeat events are missed, the client application should close the current connection and attempt to reestablish a new connection with the server. If the server is shut down normally, the client should receive a server down notification. An abnormal server shutdown (e.g., power loss) will result in the client application closing the connection and attempting a new connection with the server, as described earlier (i.e., after two consecutive heartbeat events have been missed). 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); }

311

VSI and TTS

Dynamic Network Administration Technical Guide

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).

Time System Server

D.N.A. Time System Server (TSS) 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 configuration.

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

312

Dynamic Network Administration Technical Guide

VSI and TTS

! ! !

[ 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

! !

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 FLEXIM 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 means 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 retransmitted.

313

VSI and TTS

Dynamic Network Administration Technical Guide

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 retransmitting 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.

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 1-11,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

314

Dynamic Network Administration Technical Guide

VSI and TTS

2 In 3 Ou t 4 Tr ip in 5 Tr ip o u t 6 V ac a t ion o u t 7 S ic k o ut 8 O ver t im e o u t 9 O ther R eas on in 0 O ther R eas on o u t a Lunc h 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 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 N o r ma l L og in < S TX> 2 < T AB> 15 034 911 5 E < T A B> < TA B > < T A B> < BCC> <CR> No rma l L og ou t < ST X> 3 < T AB> 1 503 491 15E <T AB> <T AB> < TAB> < BCC> <CR> T ri p In < STX> 4 < TAB> 1 23 <T AB> <T AB> <T AB> < BCC> <CR>

315

VSI and TTS

Dynamic Network Administration Technical Guide

T ri p Ou t + r eturn tim e < ST X> 5 <T AB> 1 24 <T AB> < TAB> 15 07 <TAB> 1530 < BCC> <CR> T ri p Ou t + r eturn + log tim e < STX> 5 < TAB> 1 24 <T AB> <T AB> 1 507 < T AB> 1 530 < TAB> 13 07 <T AB> 1 300 < BCC> <CR> T r i p Ou t + r et ur n + log + v al id a tio n < S T X> 5 < T AB> 12 4 < T A B> <T AB> 1 507 < T AB> 15 30 <T AB> 1 307 < T AB> 13 00 <T AB> <1 407> <TAB> 0800 < BCC> <CR> Vac a ti on + r eturn tim e < ST X> 6 <T AB> 1 25 6 <T AB> < TAB> 13 05 <TAB> 0800 < BCC> <CR> Si ck + re tur n ti me < ST X> 7 <T AB> 11 15 <T AB> < TAB> 14 05 <TAB> 0630 < BCC> <CR> O ver ti me Ou t < STX> 8 <T AB> 1 11 5 <T AB> <T AB> < TAB> <BCC> <CR> O ther Re aso n + cod e + re turn < ST X> 0 <T AB> 15 03 <T AB> 2 < T A B> 3 05 < T A B> 1 20 0 < B C C > < C R > O t her R e aso n + c od e ( I n) < S T X> 9 < T AB> 89 0 < T A B> 3 < T AB> <TAB> < BCC> <CR> 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 are 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: < ST X> 2 <T AB> 1 19 99 < T AB> <T AB> < TAB> < BCC> <CR>

316

Dynamic Network Administration Technical Guide

VSI and TTS

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. < ST X> 3 <T AB> 2 35 6 <T AB> < TAB> 03 12 <T AB> 1 445 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. < ST X> 0 <T AB> 4 45 57 7 <T AB> < X> <T AB> 2 806 < T AB> <T AB> 2 106 < T AB> 07 32 < 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. 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.

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)

317

VSI and TTS

Dynamic Network Administration Technical Guide

' ' = 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 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. Removal of all messages STX = Start of message P = Remove Message -field type BCC = Checksum CR = End of message This message causes the removal of all call requests sent by the D.N.A. Time System Interface from the FLEXIM system. Init request STX = Start of message I = `I' is the Init Request message type CR = End of message

318

Dynamic Network Administration Technical Guide

VSI and TTS

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.

How DNA Handles Date and Time from FLEXIM

In DNA, diversions from the FLEXIM time system is set based on the date and time (Login\Logout, Validation and Return times) sent to it. If the date and time sent are within the past 1day from the current date and time of DNA, then it is considered as past. Otherwise, it is considered as in the future which means next year. DNA does further calculation to determine the end time of the activity to be scheduled. This is based on the whether Validation date and time are sent or not. If Validation time is sent, then the end time is compared with Validation date and time and if it is less, then the end time will be next year. Otherwise the end time is compared with Login date and time and if it is less, then the end time will be next year. For example, assume the current date of the DNA server is 10/08/2006 (dd/mm/yyyy) and the time is 12:00PM: Past activity: If FLEXIM sends the following login and return date and time, 09/08(dd/mm) 01:00PM and 11/08(dd/mm) 08:30AM, DNA considers it as the past and schedules a current activity with start time as 09/08/2006 01:00PM and end time as 11/08/2006 08:30AM. Future activity: If the login and return date and time are 08/08(dd/mm) 12:00PM and 09/08(dd/mm) 08:30AM, then this will be scheduled as the future activity by DNA with start time as 08/08/2007 12:00PM to end time 09/08/2007 08:30AM.

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

319

VSI and TTS

Dynamic Network Administration Technical Guide

! !

<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 message is invalid. Sending 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

320

Dynamic Network Administration Technical Guide

VSI and TTS

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. 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.

321

VSI and TTS

Dynamic Network Administration Technical Guide

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.

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.

! !

322

Dynamic Network Administration Technical Guide

VSI and TTS

<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 (entering office) Upon receiving this message from the CTR system, D.N.A. Time System Interface deletes all time monitoring system diversions and deactivates 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 Example: <stx>654444<cr><lf> where card number = 4444 Used to clear diversions for this TSI card. Gone Out Registrations (leaving office) 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 66 X = Card number CR LF Example: <stx>664444<cr><lf> where card number = 4444 Set diversion using the default diversion specified in TSS Configuration. 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 67 X = Card number A = Reason code CR LF Example: <stx>6744442<cr><lf> where card number = 4444 reason code = 2

323

VSI and TTS

Dynamic Network Administration Technical Guide

Set diversion using the selected reason code and end time/duration specified in RDS Configuration. 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. D.N.A. Time System Interface will use the previously set end date, if provided, to create a complete return time. If there is no previous end date entered, then the default end date is used to create a complete return time. STX = Start of message 68 = Message type is set to 68 X = Card number HHMM = Return time (hours and minutes) CR LF Example 1: <stx>6844441830<cr><lf> where card number = 4444 return time = 1830 Update the endtime of the previously set diversion (e.g., 66 or 67) for this TSI card (to 18:30). Here the return date is the default return date associated with the diversion code as configured in RDSSetup. Example 2: <stx>6944440625<cr><lf> <stx>6844441830<cr><lf> If a previously set diversion has a end date (e.g. "69") then sending "68" will update the end time for this TSI card (to 18:30) keeping the end date (June 25) set with "69". 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. D.N.A Time System Interface will use the previously set end time, if provided to create a complete return time. If there is no previous end time entered then the default end time is used to create a complete return time. STX = Start of message 69 = Message type is set to 69 X = Card number MMDD = Return time (month and day) CR LF Example 1: <stx>6944440625<cr><lf> where card number = 4444 return time = 0625 Update the end date of the previously set diversion (e.g. "66" or "67") for this TSI card (to June 25). Here the end time is the

324

Dynamic Network Administration Technical Guide

VSI and TTS

default end time associated with the diversion code as configured in RDSSetup Example 2: <stx>6844441830<cr><lf> <stx>6944440625<cr><lf> If a previously set diversion has an end time (e.g. "68") then sending "69" will update the end date for this TSI card (to June 25) keeping the end time (18:30) as set with "68".

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)

325

VSI and TTS

Dynamic Network Administration Technical Guide

TAB DDMM = Return date (0 to 4 digits) TAB HHMM = Return time (0 to 4 digits) BCC = Checksum CR 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). &#9;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, re-transmit 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

326

Dynamic Network Administration Technical Guide

VSI and TTS

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 the 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)

327

VSI and TTS

Dynamic Network Administration Technical Guide

CR TSS 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
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 is determined in the contents of this field. If position (3 & 4) is 01 - 12, it is treated as a date; otherwise as a time, this means that time contains minutes l to 60 and hours 1-24.

Clock Message
TIMECON has a message called clock message, the clock message is repeatedly sent from time system to TSS as an online check. TSS 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" TSS algorithm: IF F in ("A", "D", "Z") THEN Intepret_Clock_Message HHMM - Time info HHMM TSS 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 to 5 min and IS min.

328

Dynamic Network Administration Technical Guide

VSI and TTS

Exchange Interface
The D.N.A. Interface is compatible towards the exchange from ASB50101 R6/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 Windows 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 Show information about MMMM on Operator Workstation XX in node PPP because of W Command Example

STX 50 MMMM W XX STX 50 1234 1 99 001 Y CR PPP Y CR LF LF

Initiate Message Diversion Type for extension because of Reason from Start until End with Reason Text. 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 Example

STX 60 MMMM RRR STX 60 1234 000 0 T SSSS EEEE KK 961231113000 TEXT Y CR LF 961231123000 15 "Gone To Lunch" Y CR LF

Delete Message Diversion with recID for Extension Action Request Delete diversion DD for Command Example

STX 61 MMMM DD Y STX 61 1234 01 Y CR LF

329

VSI and TTS

Dynamic Network Administration Technical Guide

MMMM

CR LF

View Message Diversion(s) for Extension Action Request View diversion(s) for MMMM Command Example

STX 62 MMMM Y CR STX 62 1234 Y CR LF LF

Initiate Message Text for Extension Action Request Command Example STX 70 1234 16 "Call home soon" Y CR LF

Initiate message TEXT for STX 70 MMMM KK MMMM TEXT Y CR LF

Delete Message Text for Extension Action Request Delete message DD for MMMM Command Example

STX 71 MMMM DD Y STX 71 1234 02 Y CR LF CR LF

View Message(s) for Extension Action Request View message(s) for MMMM Command Example

STX 72 MMMM Y CR STX 72 1234 Y CR LF LF

Download all Message Diversions and Messages from D.N.A. Action Request Command 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.

Database Synchronization STX 90 Y CR LF Message

330

Dynamic Network Administration Technical Guide

VSI and TTS

View (synchronize) D.N.A. system time Action Request Time Synchronization Message Command Example

STX 91 This allows VSI Service to YYMMDDHHMMSS Y check the local date/time of CR LF 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 Windows event log. If local date/time deviates more than 10 minutes, then VSI Service prompts an error message in the D.N.A. Server Windows event log.

IVR/Voice System from VSI Messages

Start of showing Message Diversion(s) for Extension that has Number of Message Diversions Action Request Command Example

Start of showing message STX 10 MMMM NN Y See below diversion(s) for MMMM CR LF that has NN diversions

Show Message Diversion with recID for Extension Action Request Show diversion DD for MMMM Command STX 11 MMMM DD RRR T SSSS EEEE KK TEXT Y CR LF Example See below

End of showing Message Diversion(s) for Extension Action Request End of showing diversion(s) for MMMM Command Example

STX 12 MMMM Y CR (1234 has 2 diversions, LF lunch (0) 11:30-12:30 and vacation (7) June 25th until July 12th)

331

VSI and TTS

Dynamic Network Administration Technical Guide

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

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

Deactivate Message Diversion for Extension Action Request Deactivate diversion for MMMM Command Example

STX 14 MMMM Y CR STX 14 1234 Y CR LF LF

Start of showing Message(s) for Extension that has Number of Messages Action Request Command Example

Start of showing STX 20 MMMM NN Y See below message(s) for MMMM that CR LF has NN messages

Show Message with Number of characters with recID for Extension Action Request Show message DD for MMMM Command STX 21 MMMM DD KK TEXT 1 Y CR LF Example See below

332

Dynamic Network Administration Technical Guide

VSI and TTS

or STX 21 MMMM DD KK TEXT 0 Y CR LF

End of showing Message(s) for Extension Action Request Command Example

End of showing message(s) STX 22 MMMM Y CR (1234 has 2 messages, first for MMMM LF 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

333

VSI and TTS

Dynamic Network Administration Technical Guide

Indicate that Extension has a Message Waiting Indication Action Request Indicate message waiting indication for MMMM Command Example

STX 23 MMMM Y CR STX 23 1234 Y CR LF LF

Erase the Message Waiting Indication for Extension Action Request Erase message waiting indication for MMMM Command Example

STX 24 MMMM Y CR STX 24 1234 Y CR LF LF

334

Chapter 17 Security
Directory Security
The D.N.A. directories are open to anyone with full control, by default, if FAT is used. If NTFS is used, Read and Write permission is granted to the appropriate users by administrator. The following table contains the directories and the applications/services that require write permission.

D.N.A. Server
D.N.A. Components MRS Directory / File \CAAPI\data Applications / Services / User Call Accounting API (RDS Scheduled job) LFS RDS

\Data\LFS \Data\RDS and subdirectories \Data\SDS \Photo Share \Data\DirChangeLog

SDS RDS Not used today, for 3rd party use only LDS MD Support users Name Identity Conversion users SCS EMG users MD Support users

\Data\LDS \Data\MDS \Data\NameID

\Data\SCS Site1, 2, \EMG and sub-directories \MDS and sub-directories

335

Security

Dynamic Network Administration Technical Guide

D.N.A. Components

Directory / File \PMG and sub-directories

Applications / Services / User PDM users OWS users PDM users

OWS PMG

\OWS\Data \PMG\Data

D.N.A. Client
D.N.A. Components Share Directory / File \Data\DirChangeLog Applications / Services / User Not used today, for 3rd party use only LDS LFS MD Support users Name Identity Conversion users SCS EMG users MD Support users PDM users OWS users PDM users

\Data\LDS \Data\LFS \Data\MDS \Data\NameID

\Data\SCS Site1, 2, \EMG and sub-directories \MDS and sub-directories \PMG and sub-directories OWS PMG \OWS\Data \PMG\Data

336

Dynamic Network Administration Technical Guide

Security

Web Server
D.N.A. Components ECA, DME, or Personal Assistant ECA DME Directory / File DirB\data Applications / Services / User everyone

root \MobileExec\bin\session.m db

IUSER_<machine> everyone (this is done by DME installations automatically)

Services and Accounts/Rights

D.N.A. Server
Service Display Name: The name displayed in Service manager. Service Internal Name: The name listed in Registry,
HKLM\System\CurrentContolSet\Services

Service Display Name Ericsson ClockSync

Service Internal Name ClockSync

Startup Type Automatic

Logon Local System Account Local System Account Local System Account Local System Account Local System Account Local System Account

Remarks

Ericsson ECA Scheduler

ECA Scheduler

Manual

Ericsson IP Service

IP Service

Automatic

Ericsson LDAP

LDAP

Manual

Ericsson LDS

LDS

Manual

Ericsson LFS

LFS

Automatic

337

Security

Dynamic Network Administration Technical Guide

Service Display Name Ericsson MD110 Time

Service Internal Name MD110Time

Startup Type Manual

Logon Local System Account Local System Account Local System Account Local System Account Local System Account Local System Account Local System Account Local System Account Local System Account

Remarks

Ericsson OWS Supervisor

DNASupervisor Server

Automatic

If OWS installed

Ericsson PBX Service

PBXService

Automatic

If OWS installed

Ericsson RDS

RDS

Automatic

Ericsson SDS

SDS

Automatic

Ericsson SCS

SCS

Manual

Ericsson SMS

DNA_SMS

Manual

Ericsson TSS

TSS

Manual

Ericsson VSI

VSI

Manual

338

Dynamic Network Administration Technical Guide

Security

DNA Client
Service Display Name (in Service Manager) Ericsson ClockSync Service Internal Name (in Registry) ClockSync Startup Type Automatic Logon Remarks

Local System Account Local System Account Local System Account Local System Account If OWS installed

Ericsson LFS

LFS

Automatic

Ericsson SCS

SCS

Manual

Ericsson PBX Service

PBXService

Automatic

ODBC Connection
The ODBC User Data Source configuration is as follows: ! ! ! ! Data Source name Server name defined in the D.N.A. Server configuration. E.g., Local DNA Server (default for local server) Data Provider SQL Server name Authentication use SQL Authentication, login ID is oliver. Others Refer to the following screen capture for the remaining configurations

339

Security

Dynamic Network Administration Technical Guide

Files Copied to Other Directories

Microsoft introduced Protect Files when the Windows 2000 operating system was released. These files should be installed by Microsoft only. Since D.N.A. previously supported Windows NT 4.0, different sets of files may be copied to the WINNT and System32 directories by D.N.A. installation (depending on the version of Windows operating system).

Windows NT
Destination Directory WINNT System32 Files hh.exe opi_msg.dll owspbxext.cpl Api.dll Cstrain.dll Ossapi.dll Remarks MS redistribution files DNA files DNA files Third party files Third party files Third party files

340

Dynamic Network Administration Technical Guide

Security

Destination Directory

Files Ossdmem.dll Soedber.dll Ossmem.dll Asycfilt.dll Atl.dll Comcat.dll Gapi32.dll Mfcans32.dll Mscal.ocx Mscomct2.ocx Msflxgrd.ocx Msvbvm60.dll Msvcp50.dll Msvcp60.dll Oleaut32.dll Olemsg32.dll Olepro32.dll Stdole2.tlb Ctl3d32.dll Dbmssocn.dll

Remarks Third party files Third party files Third party files MS redistribution files MS redistribution files MS redistribution files MS redistribution files MS redistribution files MS redistribution files MS redistribution files MS redistribution files MS redistribution files MS redistribution files MS redistribution files MS redistribution files MS redistribution files MS redistribution files MS redistribution files MS redistribution files MS redistribution files

341

Security

Dynamic Network Administration Technical Guide

Destination Directory

Files Mfc40.dll Mfc42.dll Msvcrt40.dll Sqlstr.dll Sqlwid.dll Sqlwoa.dll Csh.dll Hhctrl.ocx Itircl.dll Itss.dll Roboex32.dll Sms_rl.dll

Remarks MS redistribution files MS redistribution files MS redistribution files MS redistribution files MS redistribution files MS redistribution files Third party files MS redistribution files MS redistribution files MS redistribution files Third party files Ericsson file DNA files

Program Files\Common files\EricssonShare \ADSI

adsdna.dll

applpy.dll Program Files\Common files\EricssonShare\DM I\CIManger CIMgr.exe

DNA files Intel files

CiMgrLdr.exe DmiProxy.dll Program Files\Common files\EricssonShare\DM I\Mapper Dmi2snmp.dll

Intel files Intel files Intel files

342

Dynamic Network Administration Technical Guide

Security

Destination Directory Program Files\Common files\EricssonShare\Ser viceProvider

Files *.*

Remarks Intel files

Windows 2000, Windows XP, or Windows Server 2003

Destination Directory System32 Files opi_msg.dll owspbxext.cpl Api.dll Cstrain.dll Ossapi.dll Ossdmem.dll Soedber.dll Ossmem.dll Gapi32.dll Mfcans32.dll Mscal.ocx Mscomct2.ocx Msflxgrd.ocx Msvcp60.dll Olemsg32.dll Csh.dll Roboex32.dll Remarks DNA files DNA files Third party files Third party files Third party files Third party files Third party files Third party files MS redistribution files MS redistribution files MS redistribution files MS redistribution files MS redistribution files MS redistribution files MS redistribution files Third party files Third party files

343

Security

Dynamic Network Administration Technical Guide

Destination Directory

Files Sms_rl.dll

Remarks Ericsson file DNA files

Program Files\Common files\EricssonShare \ADSI

adsdna.dll

applpy.dll Program Files\Common files\EricssonShare\DM I\CIManger CIMgr.exe

DNA files Intel files

CiMgrLdr.exe DmiProxy.dll Program Files\Common files\EricssonShare\DM I\Mapper Program Files\Common files\EricssonShare\Ser viceProvider Dmi2snmp.dll

Intel files Intel files Intel files

*.*

Intel files

Databases
Permissions: ! ! dbo: Database Owner with full controls SELECT: Read permission Database aux1, aux2 db_xaction dnadfdb dirdb emgdb Permission for User oliver dbo dbo dbo dbo dbo Permission for User thirdpty SELECT SELECT No permission SELECT SELECT

344

Dynamic Network Administration Technical Guide

Security

Database pmglocks security site1pmg, site2pmg site1, site2

Permission for User oliver dbo dbo dbo dbo

Permission for User thirdpty SELECT No permission SELECT SELECT

Registry
Location
The root of the DNA key is HKLM\SOFTWARE\Ericsson. The primary sub-keys for each individual DNA application is created under \Ericsson by various installations. DDB DMG DMI ECA ECC EMG Integration LocalDS MobileExec MRS OPI PersonalAssistant Installed by D.N.A. installation Installed if DMG is selected Installed on server only Installed by ECA installation Installed by ECC installation Installed if EMG is selected Installed by Outlook integration and Lotus Notes installations Installed on server and client Installed by Mobile Executive installation Installed on server only Installed if OWS is selected Installed by Personal Assistant installation

345

Security

Dynamic Network Administration Technical Guide

PMG PPMLite ServicePack

Installed if PMG is selected Installed by PPMLite installation under \PMG Installed by DNA Service Pack installation

Permissions
Permissions Setup by D.N.A. Installation
Default Permissions By default, the Ericsson Registry key permissions are set as follows by D.N.A. installations: ! ! Administrator Full Control Everyone Special Access. Reference the following screen capture for Special Access permissions.

Deviation from Default Permission

346

Dynamic Network Administration Technical Guide

Security

Due to special needs by applications, the following specific sub-keys under HKLM\SOFTWARE\Ericsson are granted for Full Control to Everyone by D.N.A. installation. ! ! LocalDS MRS ! ! ! ! ! ! ! ! ! ConnectionList DirChangeLog DrOhan HIS LDS RemoteDS SCS Servers SMS

Registry Keys that Require Write Permissions The following table contains the Registry keys and the applications that require write permission. All the Registry keys are located at \HKLM\SOFTWARE\Ericsson\ D.N.A. Server Registry Key Location HKLM\SOFTWARE\Ericsson MRS\ConnectionList MRS\DirChangeLog MRS\DrOhan MRS\HSI MRS\LDS MRS\MDS MRS\NameID MRS\RemoteDS MRS\SCS MRS\SMS MD Support RDS RDS HSI Configuration LDS Configuration MDS Name Identity Conversion RDS Configuration SCS Configuration RDS Configuration Applications

347

Security

Dynamic Network Administration Technical Guide

Registry Key Location HKLM\SOFTWARE\Ericsson MRS\Servers MRS\TSS MRS\VSI DMG\LDAP EMG PMG

Applications

DNA Server Configuration, LFS TSS Configuration VSI Configuration LDAP Configuration Extension Manager Performance Data Manager & Performance Presentation Manager

348

Dynamic Network Administration Technical Guide

Security

D.N.A. Client Registry Key Location HKLM\SOFTWARE\Ericsson MRS\ConnectionList MRS\DrOhan MRS\LDS MRS\MDS MRS\RemoteDS MRS\SCS MRS\Servers DMG\LDAP ECC EMG PMG

Applications

MD Support RDS LDS Configuration MDS LDS SCS Configuration LFS LDAP Configuration Ericsson Communication Client Extension Manager Performance Data Manager & Performance Presentation Manager

Web Server Registry Key Location HKLM\SOFTWARE\Ericsson ECA MRS\LDS

Applications

ECA Configuration LDS Configuration & LDS

349

351

353