Nortel 1000 Installation And Configuration Manual
  1. Manuals
  2. Brands
  3. Nortel Manuals
  4. Software
  5. 1000 Con?guration guide
  6. Installation and configuration manual
Nortel 1000 Installation And Configuration Manual

Nortel 1000 Installation And Configuration Manual

Nortel 1000 servers: user guide
Hide thumbs Also See for 1000:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Administration Manual, Reference Manual
Title page
Nortel Communication Server 1000
Nortel Networks Communication Server 1000 Release 4.0

Telephony Manager 3.0

Installation and Configuration
Document Number: 553-3001-230
Document Number: Standard 10.01
Date: September 2007
Copyright © 2007 Nortel Networks. All rights reserved.
Produced in Canada
The information in this document is subject to change without notice. The statements, configurations, technical
data, and recommendations in this document are believed to be accurate and reliable, but are presented
without express or implied warranty. Users must take full responsibility for their applications of any products
specified in this document. The information in this document is proprietary to Nortel Networks.
Nortel, Nortel (Logo), the Globemark, SL-1, Meridian 1, and Succession are trademarks of Nortel Networks.

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the 1000 and is the answer not in the manual?

Questions and answers

Related Manuals for Nortel 1000

Summary of Contents for Nortel 1000

  • Page 1: Telephony Manager

    Users must take full responsibility for their applications of any products specified in this document. The information in this document is proprietary to Nortel Networks. Nortel, Nortel (Logo), the Globemark, SL-1, Meridian 1, and Succession are trademarks of Nortel Networks.

  • Page 2: Restricted Rights Legend

    The software described in this document is furnished under a license agreement and may be used only in accordance with the terms of that license. The software license agreement is included in this document. Nortel Networks, the Nortel Networks logo, the Globemark, Unified Networks, SL-1, Meridian 1, Succession, and Optivity are trademarks of Nortel Networks.

  • Page 3: Statement Of Conditions

    In the interest of improving internal design, operational function, and/or reliability, Nortel Networks Inc. reserves the right to make changes to the products described in this document without notice. Nortel Networks Inc. does not assume any liability that may occur due to the use or application of the product(s) or circuit layout(s) described herein.
  • Page 4 Software is provided will be free from defects in materials and workmanship under normal use for a period of 90 days from the date the Software is first shipped to Licensee. Nortel Networks will replace defective media at no charge if it is returned to Nortel Networks during the warranty period along with proof of the date of shipment.
  • Page 5 7. Term and termination. This license is effective until terminated; however, all of the restrictions with respect to Nortel Networks’ copyright in the Software and user manuals will cease being effective at the date of expiration of the Nortel Networks copyright; those restrictions relating to use and disclosure of Nortel Networks’ confidential information shall continue in effect.
  • Page 6 553-3001-230 Standard 10.01 September 2007...

  • Page 7: Revision History

    Standard 3.00. This document is up-issued to support Communication Server 1000 Release 4.5. September 2004 Standard 2.00. This document is up-issued for Communication Server 1000 Release 4.0. October 2003 Standard 1.00. This document is a new NTP for Succession 3.0. It was created to support a restructuring of the Documentation Library.
  • Page 8 553-3001-230 Standard 10.01 September 2007...

  • Page 9: Table Of Contents

    How to get help ......Getting help from the Nortel Web site ......
  • Page 10 Checking local security settings ......Installing TM 3.0 software ........Installing TM 3.0 client software .

  • Page 11: Contents

    Creating a user group ........CS 1000 Telephony Manager Installation and Configuration...
  • Page 12 Adding a user ..........Authenticating users .
  • Page 13 TM 3.0 language support ........CS 1000 Telephony Manager Installation and Configuration...
  • Page 14 Appendix B: Installation checklist ... . . 313 Contents ..........Overview .

  • Page 15: How To Get Help

    Getting help over the telephone from a Nortel Solutions Center If you don’t find the information you require on the Nortel Technical Support Web site, and have a Nortel support contract, you can also get help over the phone from a Nortel Solutions Center.

  • Page 16: Getting Help From A Specialist By Using An Express Routing Code

    To access some Nortel Technical Solutions Centers, you can use an Express Routing Code (ERC) to quickly route your call to a specialist in your Nortel product or service. To locate the ERC for your product or service, go to: www.nortel.com/erc...

  • Page 17: About This Document

    About this document Subject Telephony Manager 3.0 (TM 3.0) is designed for managers of telecommunications equipment and authorized Nortel* distributors. TM 3.0 provides a single point of access for management of Nortel systems. TM 3.0 uses internet protocol (IP) technology to target: •...

  • Page 18: System Migration

    Signaling Server, the Call Server, or both. System migration When particular Meridian 1 systems are upgraded to run CS 1000 Release 4.0 software and configured to include a Signaling server, they become CS 1000M systems. Table 1 lists each Meridian 1 system that supports an upgrade path to a CS 1000M system.

  • Page 19: Intended Audience

    Procedures (553-3021-258) • Communication Server 1000S: Upgrade Procedures (553-3031-258) Intended audience This document is intended for Communication Server 1000 and Meridian 1 system administrators using a Microsoft Windows®-based PC for management activities. It assumes that you have the following background: •...
  • Page 20 Communication server 1000M Single Group (CS 1000M SG)* • Communication server 1000M Multi Group (CS 1000M MG)* * Systems that are referred to as “CS 1000” Text In this document, the following text conventions are used: angle brackets (< >) Indicates that you must input some command text. You choose the...
  • Page 21 LDAP ONMS SNMP application programming interface active server page consolidated call cost reports customer local area network (see Nortel server subnet*) command line interface Common Network Directory Consolidated Reporting System Data Buffering and Access directory number embedded local area network...

  • Page 22: Related Information

    TLAN VLAN *Nortel server subnet, formerly known as the CLAN, is the subnet to which the TM Network interface is connected. Related information This section lists information sources that relate to this document. NTPs The following NTPs are referenced in this document: •...
  • Page 23 Describes telephones and related features. The telephones provide access to an OTM -generated Corporate Directory. • DECT: Description, Planning, Installation, and Operation (553-3001-370) Provides an overview of OTM for Nortel Integrated DECT (DECT) systems. • Software Input/Output: System Messages (553-3001-411) Describes the meaning of system messages.
  • Page 24 Provides information about the Survivable IP Expansion (SIPE) feature for CS 1000S systems. • Data Networking for Voice over IP (553-3001-160) Provides information for Data Networking about Communication server 1000 and Meridian 1 systems. Online To access Nortel documentation online, click the Technical Documentation link under Support on the Nortel home page: www.nortel.com...

  • Page 25: Preparing For Installation

    Overview TM 3.0 combines with the Optivity Network Management System (ONMS) to give an integrated data, voice, and video network, as part of the Nortel Unified Networking system. The resulting integration provides converged LAN, WAN, and voice management, and the capacity to monitor TM 3.0 server activity through the ONMS.

  • Page 26: What's New

    What’s new TM 3.0 features the following installation and upgrade enhancements: • Improvements in the installation and upgrade workflow for TM 3.0 have resulted in tasks requiring fewer clicks. • The OTM 2.2 database migration utility is used in the new workflow (See “Performing migrations”...

  • Page 27: Supported Systems

    24, 25 24, 25 24, 25 24, 25 24, 25 24, 25 24, 25 24, 25 CS 1000 Telephony Manager Installation and Configuration X21 software releases 3, 4 3, 4 3, 4 3, 4 3, 4 3, 4 3, 4 2, 3, 4, 4.5...
  • Page 28 • Meridian 802.11 Wireless IP Gateway (TM 3.0 ITG Wireless Application) Note: TM 3.0 concurrence follows the life cycle plans of the Meridian 1 and CS 1000 systems and components with which it interworks. Some CPU/X11 release/system configurations that have reached their end-of-life cycle, and thus are not supported by Nortel, are also not supported by TM 3.0.
  • Page 29 Communication Server 1000 release 4.5 support Optivity Telephony Manager 2.20.78 (OTM 2.2) and Telephony Manager 3.0 (TM 3.0) provide limited support for Communication Server 1000 Release 4.5. The following table lists the features and capabilities introduced in Release 4.5, support status on OTM 2.2 and TM 3.0, and patch details, if any.
  • Page 30 IP 2007/2033 set support Partial IP ACD set & KEM support Enhanced FW download Support for 3rd party layer 2 switches for campus redundancy - support for remote MG 1000E New DSP Peg counter traffic report CLID enhancements - option for "Announce Redirecting DN"...

  • Page 31: Supported Upgrade Paths

    TM 3.0 client communicating with the TM 3.0 server. The appendix also provides information about the different network configurations that are possible. in this document for further details on bandwidth and other CS 1000 Telephony Manager Installation and Configuration "Appendix A: TM...

  • Page 32: Tm 3.0 Hardware Requirements

    The Web clients operate as thin clients connecting directly to a Web server running on the TM 3.0 server. All operations performed using a Web client are executed on the TM 3.0 server. The TM 3.0 server requires connectivity to the ELAN subnets of the systems managed.
  • Page 33 Intel Pentium III Intel Pentium III Processor 1 GHz Processor 600 1 GByte 1 GByte 512 MByte 512 MByte CS 1000 Telephony Manager Installation and Configuration Client Configuration Intel Pentium III Processor 600 Intel Pentium III Processor 400 512 MByte...
  • Page 34 Table 3 TM 3.0 hardware requirements (Part 2 of 3) Requirement Hard Drive Space (May increase depending on number of telephones) Custom Help Web Help (all languages - excluding custom help) SVGA Color Monitor and interface card CD-ROM drive Ethernet Network Interface Card Hayes- compatible modem is optional...

  • Page 35: Tm 3.0 Software Requirements

    — name the system to reflect hardware when adding the system — add information into comments field to describe hardware Single Server (stand-alone) Configuration Configuration Required Required Required Required CS 1000 Telephony Manager Installation and Configuration Client Configuration Required Required...
  • Page 36 1000 software releases. • If a Meridian 1 system running CS 1000 Release 4.0 in TM 3.0 Navigator connects to a system running X11 release software, the non-applicable associated hardware is deleted, and a message for each deleted hardware (Survivable Cabinet and Media Gateways 1000B) is logged in the Event Log.
  • Page 37 TM 3.0 PC Configuration TM 3.0 as a stand-alone (supporting no TM 3.0 Windows TM 3.0 as a client) Windows client Yes (only supported in a non-clustered environment) CS 1000 Telephony Manager Installation and Configuration page 40 list the TM 3.0 Web clients...
  • Page 38 Table 5 OS Service Packs OS software Windows Server 2003, Enterprise Edition Windows Server 2003, Standard Edition Windows 2000 Server Windows XP Professional Windows 2000 Professional Table 6 Application software requirements (Part 1 of 2) Application software Internet Explorer 6.0 SP 1 (Windows only) TCP/IP Protocol RAS (Remote Access...
  • Page 39 Application software IIS FTP Service Note 1: Nortel does not recommended to run more than one Web client from Windows 2000 Professional or Windows XP Professional standalone platforms. Regional Operating System support The Windows 2000 server Operating System (OS) is supported for the following languages: •...

  • Page 40: Third-Party Software Requirements

    Third-party software requirements Table 7 lists the third party software or firmware included as part of the TM 3.0 application. Table 7 Third-party software requirements Software and version MDAC & Jet Engine 4.0 SP7 Crystal Reports 10.0 Runtime JRE 1.5 MsXML 4.0 SP2 Sentinel Driver 5.41 used for dongle support.
  • Page 41 Data Buffering and Access - Serial Database Disaster Recovery Virtual Terminal server Table 9 lists CS1000 and Meridian 1 software requirements. Table 9 CS 1000 and Meridian 1 software requirements (Part 1 of 2) TM 3.0 Functionality Alarm Management System Terminal ESN Art Traffic Analysis...
  • Page 42 Table 9 CS 1000 and Meridian 1 software requirements (Part 2 of 2) TM 3.0 Functionality Virtual Terminal server Maintenance Pages/Inventory Web Station/List Manager Access server DECT 1. Ethernet and PPP connections require the MAT Management Interface software package 296. For version 4.5 and beyond, unsecure shells must be enabled.

  • Page 43: Installing Tm 3.0 Server (Standalone) Software

    To install the program from a hard drive instead of from a CD, create a folder in the root of the drive called CD. Copy the contents of the CD or unzip the files from the archive into this folder. Run the installation program. CS 1000 Telephony Manager Installation and Configuration...
  • Page 44 Web Help Web Help can be installed at the same time as the TM 3.0 software installation; however the Web Help installation is time consuming. The user can install only the TM 3.0 software first, and then run setup again in Maintenance Mode to install WebHelp later (see “Maintenance mode”...

  • Page 45: Users And Groups

    CAUTION — Service Interruption TM 3.0 is not supported on a Windows Server system that is configured as a Primary Domain Controller (PDC). DO NOT install TM 3.0 on a PDC. IMPORTANT! CS 1000 Telephony Manager Installation and Configuration page...
  • Page 46 Figure 1 User Rights Assignment Double-click the policy Log on locally. See Figure 2 on For Windows 2003 Server, the policy name is Allow log on locally. 553-3001-230 Standard 10.01 Installing TM 3.0 server (standalone) software page 47. The Users group should be granted this policy. September 2007...
  • Page 47 Log in to the PC as the local administrator. Check the policies. Move the PC out of the domain. Check the policies prior to installing TM. Move the PC back into the domain. CS 1000 Telephony Manager Installation and Configuration...

  • Page 48: Installing Tm 3.0 Software

    Installing TM 3.0 software Procedure 3 Installing TM 3.0 software Configure the Windows steps: Log on to Windows as Administrator. Exit all Windows programs. Install security patches as advised through Product Bulletins available on the Partner Information Center Website. Double-click Setup.exe on the TM 3.0 CD-ROM. The following prerequisites are checked: •...
  • Page 49 The following prerequisites were not installed on the computer. Telephony Manager requires these components to be installed. Please install them and re-launch the installation if you are planning a server (standalone) installation. CS 1000 Telephony Manager Installation and Configuration page 50).
  • Page 50 Figure 4 Welcome and Licence Agreement window The Server/Client installation selection page appears (See Server /Standalone. If all prerequisites are not met, installation cannot continue beyond this point. Some prerequisites are automatically installed by TM 3.0. Note: Installation types cannot be changed for upgrades. It is pre-selected based on the existing installation.
  • Page 51 Installing TM 3.0 server (standalone) software Figure 5 Select Server/Client Installation The User and Keycode information screen appears (see Figure 6 on page 52). CS 1000 Telephony Manager Installation and Configuration...
  • Page 52 Figure 6 User and Keycode Information Enter the user information and keycode. Click Next to continue. At this point the installation decides which applications to install based on the keycode entered. If the keycode is invalid, an error message appears (see Note: There are no restrictions on the number of keycode entry attempts.
  • Page 53 The Setup Type page screen appears or custom installation options. Figure 8 Setup Type The Installation Summary page appears and the installation proceeds with default values. (Figure 8), providing a choice of either default CS 1000 Telephony Manager Installation and Configuration...
  • Page 54 Figure 9 Program and Data Location Figure 9 shows the Choose Program and Data Location screen, which lists the features to be installed on the PC. The list includes: • Core Program. This cannot be deselected by the user. However, the folder selection option displayed within the Core Program Destination Folder group box allows the user to select the destination folder where the Core Program is to be installed.
  • Page 55 Specify a destination directory and click OK. Figure 10). IMPORTANT! You must not install TM 3.0 in the root directory (for example, C:\). During the installation process, you must specify a folder (for example, C:\Nortel). CS 1000 Telephony Manager Installation and Configuration...
  • Page 56 Clicking the Disk Space button in Figure 9 on Space dialog box (see drives on the PC. Note: If the selected drive doesn’t have enough disk space to accommodate the selected options, an error message appears asking the user to select another drive. Figure 11 Available Disk Space 10 The Common Network Directory (CND) Selection screen prompts for the location of...
  • Page 57 Click Back to return to the previous screen • Click Install to begin the Installation process. The Setup Status screen appears. (See Figure 14 on page 59). CS 1000 Telephony Manager Installation and Configuration Figure 13 on page 58), listing the...
  • Page 58 Figure 13 Installation Summary 553-3001-230 Standard 10.01 Installing TM 3.0 server (standalone) software September 2007...
  • Page 59 If Yes is clicked (see Figure 16 on to its original state. If No is clicked, the installation continues. Figure 15 Exit Setup 59) prompts for confirmation before terminating and rolling back page CS 1000 Telephony Manager Installation and Configuration 60), the system is restored...
  • Page 60 Figure 16 Install interrupted 13 Upon completion, the installation Wizard Complete screen appears, prompting the installer to restart the PC now or at a later time. See Figure 17 on 553-3001-230 Standard 10.01 Installing TM 3.0 server (standalone) software September 2007 page...

  • Page 61: Maintenance Mode

    InstallShield Wizard Maintenance mode (see Figure 18 on page 62). TM 3.0 can also be uninstalled by using the Add/Remove Programs window. For details, see “Uninstall using Add/Remove Programs” on page 217. CS 1000 Telephony Manager Installation and Configuration...
  • Page 62 Figure 18 Maintenance mode Maintenance mode provides the following options: • Modify: The Modify option allows the user to perform install and uninstall of TM 3.0 components such as Web Help. • Repair: The Repair option performs a reinstall of the existing installation, overwriting the existing installation's application files without modifying the data files.
  • Page 63 Installing TM 3.0 server (standalone) software Figure 19 Maintenance Complete CS 1000 Telephony Manager Installation and Configuration...
  • Page 64 Installing TM 3.0 server (standalone) software 553-3001-230 Standard 10.01 September 2007...

  • Page 65: Installing Tm 3.0 Client Software

    TM 3.0 server. All operations performed using a Web client are executed on the server requires connectivity to the ELAN subnets of the TM 3.0 CS 1000 Telephony Manager Installation and Configuration client software. TM 3.0 server installation. The steps TM 3.0...
  • Page 66 The TM 3.0 client is a thick client that runs on a Windows PC. It does not operate in a traditional client-server model. Rather, the TM 3.0 client runs similar software to that running on the TM 3.0 server. The TM 3.0 client communicates directly with the managed systems, and therefore requires connectivity to the ELAN subnets of those systems.
  • Page 67 /savecred: Stores the provided credentials for re-use. Meaning Information that the user must supply Elements that the user must type exactly as shown Optional items Set of choices from which the user must choose only one CS 1000 Telephony Manager Installation and Configuration...

  • Page 68: Installing The Client Software

    • Password: Specifies the password needed to access the shared resource. Type an asterisk (*) to produce a prompt for the password. The password is not displayed when typed in at the password prompt. • /user: Specifies a different user name with which the connection is made. •...
  • Page 69 Note: Although the pre-requisite summary appears during a client install, it is only relevant to a server install. Figure 21 page 25). page CS 1000 Telephony Manager Installation and Configuration appears. 70), listing the mandatory...
  • Page 70 Figure 22 Prerequisite Summary Click Next to continue. The Welcome screen and Licence Agreement appears (see Figure 23 on Read the Licence Agreement and Click Yes to accept and continue. 553-3001-230 Standard 10.01 September 2007 Installing TM 3.0 client software page 71).
  • Page 71 Welcome screen and Licence Agreement The Server/Client installation selection page appears (See Figure 24 on Select Client. Note: Installation types cannot be changed for upgrades. It is pre-selected based on the existing installation. CS 1000 Telephony Manager Installation and Configuration page 72).
  • Page 72 Figure 24 Select Server/Client Installation The Setup Type page screen appears (Figure 25 on either Default or Custom installation options. Select Default. 553-3001-230 Standard 10.01 September 2007 Installing TM 3.0 client software page 73), providing a choice of...
  • Page 73 Installing TM 3.0 client software Figure 25 Setup Type If Default is chosen, the Installation Summary page appears and the installation proceeds with default values. If Custom is chosen, the following pages appear. CS 1000 Telephony Manager Installation and Configuration...
  • Page 74 Figure 26 Common Data Destination Folder Figure 26 shows the Common Data Destination Folder screen. The Common Data Destination Folder Browse button allows the user to select the destination folder for the Common Data. Clicking the Browse button displays the Choose Folder dialog box (see Figure 27 on 553-3001-230 Standard 10.01...
  • Page 75 You must not install TM 3.0 in the root directory (for example, C:\). During the installation process, you must specify a folder (for example, C:\Nortel). Figure 28), showing the available disk space in each of the CS 1000 Telephony Manager Installation and Configuration page 74 displays the Available Disk...
  • Page 76 Figure 28 Available Disk Space The Installation Summary screen appears (See options chosen during the installation. Figure 29 Installation Summary 553-3001-230 Standard 10.01 September 2007 Installing TM 3.0 client software Figure 29 on page 76), listing the...
  • Page 77 If No is clicked, the installation continues. Figure 31 Exit Setup 31) prompts for confirmation before terminating and rolling back the CS 1000 Telephony Manager Installation and Configuration page 78), the installation is...
  • Page 78 Figure 32 Install interrupted 11 Upon completion, the installation Wizard Complete screen appears, prompting the installer to restart the PC now or at a later time. See Figure 33 on 553-3001-230 Standard 10.01 September 2007 Installing TM 3.0 client software page...
  • Page 79 Re-enable the DCOM service Go to Control Panel->Administrative Tools->Component Services Click Computers folder Right-click on My Computer. Select Properties. Select Default Properties tab. Place a check next to "Enable Distributed COM on this computer". CS 1000 Telephony Manager Installation and Configuration...
  • Page 80 Click OK and close the Component Services window. Reboot the machine for the changes to take effect. 553-3001-230 Standard 10.01 End of Procedure September 2007 Installing TM 3.0 client software...

  • Page 81: Performing A Keycode Upgrade

    Procedure 6 Keycode upgrade From the Utilities menu in TM Navigator, select Keycode Upgrade ( Note: The menu items shown in of TM 3.0 Figure 34 are not available for a Client installation CS 1000 Telephony Manager Installation and Configuration Figure...
  • Page 82 Figure 34 Keycode upgrade Utilities menu The Keycode Upgrade dialog box appears (see details of the currently available licenses and a keycode entry facility to upgrade the keycode. Enter the appropriate information and click Upgrade. 553-3001-230 Standard 10.01 September 2007 Performing a keycode upgrade Figure 35 on page 83).
  • Page 83 Performing a keycode upgrade Figure 35 Keycode Upgrade dialog box The Confirm Keycode Upgrade dialog box appears (see proceed. Figure 36 Confirm Keycode Upgrade dialog box End of Procedure CS 1000 Telephony Manager Installation and Configuration Figure 36). Click yes to...
  • Page 84 Performing a keycode upgrade 553-3001-230 Standard 10.01 September 2007...

  • Page 85: Performing Migrations

    Custom reports created in TM 2.2 will be lost after migration to TM 3.0. The TM 3.0 Corporate Directory does not support customized reports. Although TM 3.0 works with CS 1000 Release 4.5 software, it has limited support. See “Communication Server 1000 release 4.5 support” on Additional manual steps are necessary to migrate Employee Directory data (see “Migrating employee data”...

  • Page 86: Operating System Migration

    The database migration utility then migrates all data to TM 3.0. Complete the following steps to perform this migration: • Perform a full backup of the TM 3.0 data on the Windows 2000 Server system, using the TM 3.0 backup utility. •...
  • Page 87 Select Corporate Directory Export and click on the ellipsis button (…) to access the configuration dialog. Select File Type as Text File (comma separated values). Click on the Format button to select the employee fields that you want to export. End of Procedure CS 1000 Telephony Manager Installation and Configuration...
  • Page 88 For each field selected, make sure the External Column Name matches the supported attribute names in CND (refer to CND Administrator Guide, Subscriber Import section, Header Record description). Click OK to save Format settings. Click OK to save Configuration settings. Click Go or Schedule to run report.

  • Page 89: Configuring Secure Sockets Layer (Ssl)

    (for example, Verisign) or generate your own certificate using a certificate server. This document assumes you have already obtained a server certificate and only describes the steps required to install the certificate. CS 1000 Telephony Manager Installation and Configuration...

  • Page 90: Configuring Ssl On The Tm 3.0 Server Platform

    Configuring SSL on the TM 3.0 server platform Procedure 9 Configuring SSL on the TM 3.0 server platform To install the certificate from the Internet Services Manager application on a Windows server, complete the following procedure: Launch the application from Programs > Administrative Tools > Internet Services Manager.

  • Page 91: Importing Tm 3.0 Root Certificate

    If the CND server certificate is issued by well known certificate authorities such as VeriSign etc., the certificate authority can already be in the Netscape Communicator certificate database by default. End of Procedure CS 1000 Telephony Manager Installation and Configuration...
  • Page 92 Copy the three files to the TM 3.0 Common Data directory (usually under c:\Nortel\Common Data). Set up the CND SSL connection in TM 3.0 server: Open TM 3.0 Windows Navigator, select Utilities > CND Setup & Logs.

  • Page 93: License Management

    Each time you log in to TM 3.0, your TN license is checked. If the number of set TNs (telephone TNs and virtual TNs) configured in your system is approaching the maximum for your license, the TN Warning window appears. See page CS 1000 Telephony Manager Installation and Configuration Figure 37 on...

  • Page 94: Ru License

    Figure 37 TN license warning License exceeded If your TN license is exceeded, an Error window appears. See appears every 15 minutes. Contact your vendor to obtain a license for additional TNs. Figure 38 TN license error License reuse TN checking is performed on bootup and after every 12 hours of operation. If you delete a site, the TN licenses associated with that site becomes available for reuse after the next TN check.

  • Page 95: Client License

    When TM 3.0 is launched from a TM 3.0 client, the TM 3.0 server’s dongle is checked. The TM 3.0 client cannot launch the TM 3.0 System Window if the TM 3.0 server’s dongle is missing. CS 1000 Telephony Manager Installation and Configuration...
  • Page 96 If the dongle is removed from the TM 3.0 server, it takes approximately 5 minutes, when it is reattached, for the TM 3.0 client to recognize the dongle. Note: When a user attempts to log in to Web Navigator after installing TM 3.0 for the first time, an error message displays stating that the TM 3.0 dongle is missing, when in fact it is not missing.
  • Page 97 The customer is expected to discard the old dongle. This dongle swap or transfer is only for end-user licensed dongles, not for distributor or enterprise licensed dongles. Distributors can just simply order more dongles of either type. CS 1000 Telephony Manager Installation and Configuration...
  • Page 98 License management 553-3001-230 Standard 10.01 September 2007...

  • Page 99: Before Configuring Tm 3.0

    “Security Management” on page 135 • “Adding TM 3.0 Web users” on page 111 • “Setting up the FTP server, CND server and Terminal server” on page 157 • “Configuring the Web browser client” on page 167 CS 1000 Telephony Manager Installation and Configuration...

  • Page 100: Testing The Connection

    • “Integrating TM 3.0 with ONMS” on page 169 • “Integrating TM 3.0 with HP OpenView” on page 187 Testing the connection Use the following procedures to test the connection between TM 3.0 and your equipment. For detailed instructions on adding sites and systems, see “Setting up system data”...
  • Page 101 Enter the information in the System Properties—Communications dialog box for the connection type selected in step 6. For an Ethernet connection type (see Enter the IP address that you configured on the system. Click Apply. Figure 41 on page CS 1000 Telephony Manager Installation and Configuration 102):...
  • Page 102 Figure 41 System Properties—Communications tab—Ethernet Profile For a PPP connection type (see Enter all modem parameters and dial-up information. Select PPP in the Modem Script text box and enter the telephone number. There can be conditions, depending on your particular installation, where you can be required to enter a modem access ID, a modem password, and a modem initialization string.
  • Page 103 Enter all modem parameters and dial-up information. Select the appropriate value in the Modem Script text box. This is commonly “None” unless a specific value is defined for your system. Click Apply. Figure 43 on page 104): CS 1000 Telephony Manager Installation and Configuration...
  • Page 104 Figure 43 System Properties dialog box—Communications tab—Serial Profile 553-3001-230 Standard 10.01 End of Procedure September 2007 Before configuring TM 3.0...

  • Page 105: Setting Up Customer Information

    Setting up customer information Click Customers tab. See Figure 44 System Properties dialog box—Customers tab Click Properties. The Customer Properties dialog box appears with the General tab selected. See Figure 45 on page Figure 106. CS 1000 Telephony Manager Installation and Configuration...

  • Page 106: Setting Up Tm 3.0 Applications

    Figure 45 Customer Properties—General tab In the Scheduler System ID box, change the user ID and password to one that is valid for logging onto the system, and then click OK. HLOC appears the home location code (ESN) defined in LD 90. Setting up TM 3.0 applications Procedure 15 Setting up TM 3.0 applications...
  • Page 107 If there is no serial profile added, then Call Tracking is not enabled. If the user has added any serial profile, then the first profile is set as the communication profile. CS 1000 Telephony Manager Installation and Configuration...

  • Page 108: Setting Up System Data

    The General Cost Allocation System and Telecom Billing System applications are enabled without a communication profile. Disable All: Disables the communication profile for all available applications under the Application tab. Click OK. Setting up system data Procedure 16 Setting up system data Double-click the Sample System icon to open the System window.
  • Page 109 Before configuring TM 3.0 When the data is copied from the system into TM 3.0, the test procedure is complete. End of Procedure CS 1000 Telephony Manager Installation and Configuration...
  • Page 110 Before configuring TM 3.0 553-3001-230 Standard 10.01 September 2007...

  • Page 111: Adding Tm 3.0 Web Users

    Installing and configuring desktop services ..... Overview This chapter contains information about: • Web capabilities • User login and security • Access permissions • User authentication • User groups • Desktop services CS 1000 Telephony Manager Installation and Configuration...

  • Page 112: Capabilities

    Capabilities For details on TM 3.0 Web capabilities, see Optivity Telephony Manager: System Administration (553-3001-330). User login and security Users log in to the TM 3.0 Web using their Windows userID and password. Login security for TM 3.0 Web services ensures protection against unauthorized entry and enforces access permissions for logged-on users.

  • Page 113: Access Permissions

    Persons belonging to the Administrators user group on the TM 3.0 server can log in to the TM 3.0 Website and get unrestricted access. The Administrators group has unrestricted access by default. Access permissions for the Administrators user group can not be altered. CS 1000 Telephony Manager Installation and Configuration “User groups” on...

  • Page 114: User Group Access Rights

    French or German OS Administrator groups Important advice for localized OS — The name of the administrators user group in the French and German operating systems is not Administrators. These names are localized by Microsoft in the regional operating system software. In a default French installation the local administrators user group is “Administrateurs”.
  • Page 115 User Authentication page Use the check boxes to select one or more of the available authentication methods. If CND authentication is selected, use the drop-down list to choose either Common Name, EmployeeID, or Email. Figure CS 1000 Telephony Manager Installation and Configuration...

  • Page 116: User Groups

    Use the drop-down lists to assign the order in which the authentication methods are performed. If multiple authentication methods is selected, TM 3.0 respects the configured order; however, note that the best performance is achieved by using the Local TM 3.0 server account method.
  • Page 117 • Default — No access. To view the available user groups, click the User Groups link located under Web Administration in the TM 3.0 Web tree. The User Groups page appears. See Figure CS 1000 Telephony Manager Installation and Configuration...
  • Page 118 Figure 49 User Groups page Navigator access Access to the sites, systems, and applications available in both the Windows and Webs is controlled on a user-group basis through the User Group Properties Java application. When the user group name is entered into the User Group field in an TM 3.0 user’s directory record, the entry must match the user group name exactly.
  • Page 119 This is the same tree structure and performs the same function as the Windows-based New User Group Properties dialog box. The question mark indicates that the sub-items belonging to the item displaying the question mark have mixed access settings. CS 1000 Telephony Manager Installation and Configuration...

  • Page 120: Telephone Access

    To modify access rights: Use the drop-down list to select ReadWrite, ReadOnly, or No Access for each item in the tree. Click Apply. Telephone access The Telephone tab in the User Group Properties dialog box is used to control access to the telephone pages on the Web for each user group.
  • Page 121 By putting keys into the left column, users in this group can interchange these key types and change the key parameters. If the user selects a key that is not in the left-hand column while viewing the Telephone—Keys page, the Change button does not appear. CS 1000 Telephony Manager Installation and Configuration...

  • Page 122: Features Tab

    Click Apply. Features tab In the Features tab (see determine whether the Telephone—Features page appears and, if so, which features the users in this group can view and change. The list of features contains all the non-key features listed alphabetically by prompt in LD 10 and LD 11. Each feature is assigned a restriction of Hidden, ReadOnly, or ReadWrite.
  • Page 123 Use the drop-down lists in the Restrictions column to configure each feature as ReadWrite, ReadOnly, or Hidden. The Show drop-down list contains All, Hidden, ReadOnly, and ReadWrite. This is used to limit the size of the list. CS 1000 Telephony Manager Installation and Configuration...

  • Page 124: Installing And Configuring Desktop Services

    Click Apply. Installing and configuring desktop services Procedure 21 Installing and Configuring Desktop Services The following procedure outlines the steps required to install and configure Desktop Services. Install TM 3.0. Create accounts for Help Desk users and End Users as required. Log in to the Web as Administrator, and go to the User Groups page.
  • Page 125 For end user reference information, and for information about populating entries using CND import and CND sync, see Corporate Network Directory 2.0 (NN-10300-028). For information about configuring users in CND, see Corporate Network Directory 2.0 (NN-10300-028). CS 1000 Telephony Manager Installation and Configuration...
  • Page 126 Adding TM 3.0 Web users 553-3001-230 Standard 10.01 September 2007...

  • Page 127: Configuring A Modem For Tm 3.0 Applications

    INIT string is set to use numeric (V0) result code, the “Can’t set modem parameters” error message occurs and the dial-up attempt is aborted. To change the factory INIT string to use verbal (V1) result code, follow the steps in Procedure 22. CS 1000 Telephony Manager Installation and Configuration...

  • Page 128: Configuring High-Speed Smart Modems

    Procedure 22 Changing the factory INIT string From the Start menu, select Settings > Control Panel > Phones and Modems > Properties > Advanced Type in the appropriate INIT string. Configuring high-speed smart modems As modem technology progresses, the new generation of high-speed modems provides additional functionality to achieve the highest possible connection rate.
  • Page 129 (for example, 7 = 7/10 of a second). When increasing the value of the S9 register, timing adjustments may be required on some of the modem/buffer equipment scripts. CS 1000 Telephony Manager Installation and Configuration...

  • Page 130: Troubleshooting Modem Connections

    Troubleshooting modem connections The following procedures are solutions to the most common troubles. Modem does not dial Procedure 23 Verifying that the modem is properly configured Verify that the modem is configured on the correct COM port: From the Start menu, select Settings > Control Panel. Open the Modems file and click Properties.
  • Page 131 Right-click on the desired system in the Navigator window. Select Properties, and then click Communications tab in the Properties dialog box. End of Procedure “Testing the COM port” on page 130 End of Procedure End of Procedure CS 1000 Telephony Manager Installation and Configuration to establish...
  • Page 132 Modem dials but does not connect Procedure 27 Verifying the modem connection Verify that the dialed telephone number is not busy. Verify that all necessary digits in the telephone number have been included. Check the PPP or Serial Communications profiles for the system to which you wish to connect.
  • Page 133 Select the COM port to which your modem is connected, and then click Next. Click Finish to complete the modem installation. Restart the system, and try to establish a PPP or serial connection. End of Procedure End of Procedure CS 1000 Telephony Manager Installation and Configuration...
  • Page 134 Configuring a modem for TM 3.0 applications 553-3001-230 Standard 10.01 September 2007...

  • Page 135: Security Management

    IP phone set, the list of feature values is displayed only in English. The values are not translated into German or French. See Figure 53: “End User page in French language” on page 136. CS 1000 Telephony Manager Installation and Configuration...

  • Page 136: Assigning Access Properties

    Figure 53 End User page in French language Assigning access properties TM 3.0 provides easy access to users for personal, system, site, or network-wide management of systems. The administrator determines the level of access for the users in a particular user group. The administrator also determines which sites and systems the members of the user group can manage.

  • Page 137: Security For Upgrades And Re-Installations

    Users log in to the TM 3.0 Web Navigator using their Microsoft Windows userID and password. Login security for TM 3.0 Web services ensures protection against unauthorized entry and enforces access permissions for logged-on users. CS 1000 Telephony Manager Installation and Configuration...

  • Page 138: Authentication Methods

    Access to Web applications applies to a group, not to individual users. To change the security access for individual users, their group membership should be changed. For information about setting user access, refer to With the exception of Administrators, do not place a person in multiple groups. The first group detected by TM 3.0 is used to determine access permissions.

  • Page 139: Password Policy

    The passwords must be updated manually on the Call Server, Signalling Server and Voice Gateway Media Card through CLI commands. TM 3.0 system properties must also be updated with the new passwords before proceeding with any TM 3.0 functionality. CS 1000 Telephony Manager Installation and Configuration...

  • Page 140: Blank Passwords

    • TM 3.0 Windows client passwords are encrypted using Crypto APIs prior to transmission. The same private key is used by both the client and the server. • For TM 3.0 Web clients, by default, clear text passwords are used; however, if the TM 3.0 server has the proper certificate installed, the use of SSL encrypted transport during authentication can be forced.
  • Page 141 Login name. When configuring CND authentication, the login name may be one of the following: — commonName — email — employee number • User group • Web Reporting Access Rights 145. CS 1000 Telephony Manager Installation and Configuration “Configuring TM 3.0 Navigator...

  • Page 142: Login Process

    For information about using the CND Directory to configure end users for access to TM 3.0, see the Corporate Network Directory 2.0 (NN-10300-028). Login process This chapter describes the activities performed by TM 3.0 to authenticate and log in TM 3.0 users.
  • Page 143 — Web Desktop Services is read-only; however, all except 21 of the most commonly used features are set to “Hidden” • Default — This user group has no access to any TM 3.0 features or applications. CS 1000 Telephony Manager Installation and Configuration...

  • Page 144: User Management Recommendations

    Even though it is not listed in the Users window, the OS Administrator account can always be used to log in to TM 3.0. Nortel strongly recommends that a new user group be created in TM 3.0 based on the Administrators user group. TM 3.0 users should be assigned to this new user group instead of adding them to the Administrators user group.

  • Page 145: Configuring Tm 3.0 Navigator Users

    When adding or modifying a user group, only systems that have applications enabled are presented. If no applications are enabled for the systems within a given site, the site and system(s) do not appear in the User Group Properties dialog box. CS 1000 Telephony Manager Installation and Configuration...
  • Page 146 For information about configuring end users for access to the TM 3.0 Website, see groups” on page User authentication Any of the following three methods or combination of these methods can be used to authenticate TM 3.0 users: • Local TM 3.0 server account •...
  • Page 147 Use the drop-down lists to assign the order in which the authentication methods are performed. If choosing multiple authentication methods, TM 3.0 respects the order configured; however, it should be noted that the best performance is achieved by using the “Local TM 3.0 server account” method. CS 1000 Telephony Manager Installation and Configuration...

  • Page 148: Creating A User Group

    To use the SSL during the authentication process, the TM 3.0 server must have the required certificate installed as described in (SSL)” on page after installing the certificate. If the TM 3.0 server has the required certificate installed, selecting the check box causes TM 3.0 to use SSL-encrypted transport during authentication.
  • Page 149 The Administrators, Default, EndUser, and HelpDesk User Groups are always available and cannot be deleted. All groups except for Administrators can be modified. The Administrators User Group has access to all Windows-based and Web-based TM 3.0 applications. (Figure 55). (Figure 56). CS 1000 Telephony Manager Installation and Configuration...
  • Page 150 Figure 56 New User Group Properties dialog box Enter a name for this User Group. For each site, system, and application in the tree, use the right mouse button to assign user privileges (Read-write, Read-only, or No Access). Each click of the right mouse button causes the access privileges and corresponding icon to change.

  • Page 151: Icon Explanation

    Click OK to save changes and close the User Group Properties dialog box. Explanation Read and write access Read only access No access Indicates that the access privileges in the branch are mixed between one or more of the above levels End of Procedure CS 1000 Telephony Manager Installation and Configuration...

  • Page 152: Adding A User

    Adding a user The “Administrator” user account for the Windows 2000 OS does not appear in the TM 3.0 Users window. This is to prevent users from changing the Administrator account password from within TM 3.0. Even though it is not listed in the Users window, the OS Administrator account can always be used to log in to TM 3.0.

  • Page 153: Authenticating Users

    CND Directory for the user’s assigned User Group. To configure authentication, complete Procedure 30 on End of Procedure page CS 1000 Telephony Manager Installation and Configuration 146.
  • Page 154 Security Management 553-3001-230 Standard 10.01 September 2007...

  • Page 155: Initial Login

    Users” in Optivity Telephony Manager: System Administration (553-3001-330) for detailed instructions on adding TM 3.0 users. Users that are not created from within TM 3.0 do not appear in the TM 3.0 Users window. CS 1000 Telephony Manager Installation and Configuration...
  • Page 156 Initial login 553-3001-230 Standard 10.01 September 2007...

  • Page 157: Setting Up The Ftp Server, Cnd Server And Terminal Server

    To configure, go to Start > Programs > Telephony Manager Navigator. From the Configuration menu, select Configure FTP Server and enter the correct TM Server IP address, UserID and password. See Figure 58 on page 158 CS 1000 Telephony Manager Installation and Configuration...

  • Page 158: Cnd Server

    Figure 58 Configure FTP Server CND server The CND server utility allows you to link and synchronize the TM 3.0 and Corporate CND databases. TM 3.0 acts as a CND client to the Corporate CND server database. • If CND is installed on the same server as TM 3.0, then all properties are preconfigured and no changes are required.

  • Page 159: Terminal Server

    Note: TM 3.0 does not support Remote Desktop with Terminal Server. Terminal server setup To launch the Terminal server application, from the Start menu, select Programs > Nortel CS 1000 Telephony Manager > Terminal server. The Terminal server dialog box appears. See Figure...
  • Page 160 Figure 59 Terminal server dialog box Click Hide on Terminal server dialog box (see the window close button (“X”) as this loses all configuration. The Terminal server window appears two lists: • configured systems • configured ports The configured systems list appears information about the virtual port that is configured: 553-3001-230 Standard 10.01 Setting up the FTP server, CND server and Terminal server...
  • Page 161 TM 3.0 server and the TM 3.0 Web System Terminal Figure 60 on page changed. • Help Get context-sensitive Help on the application. See “Virtual ports” on page 162. The default is 4789. Typically, this does not need to be CS 1000 Telephony Manager Installation and Configuration 162”.

  • Page 162: Virtual Ports

    Figure 60 Terminal Properties dialog box Virtual ports In the Terminal server application, the Virtual Ports Properties window allows the user to enable or disable connection to a particular device. It appears the virtual port number for each configured device, and the corresponding serial or network settings. In the Virtual Port Properties window, a tree appears the devices that can be connected through a virtual port.

  • Page 163: Serial Connections

    The default is the serial settings from the TM 3.0 database. The settings in the dialog box can be changed, as shown page 164. CS 1000 Telephony Manager Installation and Configuration Figure 61 on...

  • Page 164: Network Connections

    Refresh to update all of the network ports with the latest settings from the TM 3.0 database. • If selecting an M1 or CS 1000 System, the fields for M1 port settings are enabled (default = SCH). The Telnet port field is disabled. •...
  • Page 165 If this ASCII log is to be viewed from a Web browser, the file is stored in a Web-accessible path.Virtual Port Properties (Network with Logging disabled) See Figure Figure 62 Virtual Port Properties (Network with Logging disabled) CS 1000 Telephony Manager Installation and Configuration...
  • Page 166 Setting up the FTP server, CND server and Terminal server 553-3001-230 Standard 10.01 September 2007...

  • Page 167: Configuring The Web Browser Client

    From the Internet Explorer menu bar, Tools > Internet Options > Security > Trusted Sites > click Sites > and then add server IP address to trusted site. IMPORTANT! between the TM server, clients, and communication servers. End of Procedure CS 1000 Telephony Manager Installation and Configuration “TM 3.0 hardware...

  • Page 168: Accessing The Tm 3.0 Web Server From A Web Browser

    Accessing the TM 3.0 Web server from a Web browser Procedure 34 Accessing the TM 3.0 Web server from a Web browser Enter the TM 3.0 server IP address or computer name in the location bar of the Web browser on the PC client. To access the TM Administrator page enter http:/ <tmserver hostname>/admin/ Press Enter.

  • Page 169: Integrating Tm 3.0 With Onms

    Nortel inter-networking devices. Through ONMS, the TM 3.0 servers can be monitored. TM 3.0 Alarm Manager receives SNMP traps from managed CS 1000 and Meridian 1 entities. Through Alarm Notification, TM 3.0 sends filtered traps to ONMS. By using ONMS InfoCenter, TM 3.0 servers can be added manually into the Telephony Managers Resources folder.

  • Page 170: Integration Requirements

    • For optimum performance, install TM 3.0 on a separate computer from ONMS. • For more information refer to the OIT support Website at www.nortel.com. See “Downloading the OIT files” on • TM 3.0 integrates with ONMS through OIT on any NMS platform. See “Checklist for installing the Optivity Integration Toolkit”...

  • Page 171: Tm Oit Files

    — OTM Open Alarm II definitions • NMS_otmApp_v10-B.oit — OTM Web Application integration entries — OTM also contains the following mib file: • rfc1223.mib — Standard RFC 12313 MIB definitions www.nortel.com End of Procedure page 171 for details. CS 1000 Telephony Manager Installation and Configuration...

  • Page 172: Checklist For Installing The Optivity Integration Toolkit

    Run oitInstall for each .oit file, one at a time. The .mib file must be present in the same directory when oitInstall is executed. See step Optivity Integration Checklist for installing the Optivity Integration Toolkit This section provides general information about OIT. Refer to the NTPs, release notes, and read me files that are provided with your ONMS software package for specific information about OIT.

  • Page 173: About Oitinstall

    For TM 3.0, the TM 3.0 server must be added manually. What OIT does The oitInstall program does the following: • Automatically stops and restarts all ONMS daemons (UNIX) or services (Windows). End of Procedure CS 1000 Telephony Manager Installation and Configuration...

  • Page 174: Using Onms Infocenter

    Figure 63 on page Open the Management server folder. Select Telephony Manager. See Click Apply. The wizards provided in ONMS 9.0.1 and later add new TM 3.0 servers to ONMS. These wizards automatically establish the Device-Agent-Interface relationship in ONMS databases. 553-3001-230 Standard 10.01...
  • Page 175 Integrating TM 3.0 with ONMS Figure 63 InfoCenter Resources CS 1000 Telephony Manager Installation and Configuration...
  • Page 176 Figure 64 InfoCenter Voice Management Properties dialog box Adding TM 3.0 server object to ONMS InfoCenter Add a TM 3.0 server resource for every TM 3.0 server that you integrate and monitor with ONMS. If Access Control is enabled, you must have a valid local user account (UserID and password) and an ONMS user account to log in to InfoCenter.
  • Page 177 Elements integrated into ONMS. Double-click the Telephony Managers folder to open it. Modify the default view properties of the folder or you cannot view the TM 3.0 servers that are added to this folder. Right-click the Telephony Managers folder and choose Properties. Open the Management server folder.

  • Page 178: Viewing Tm 3.0 Server Object Properties

    Figure 65 InfoCenter Object Properties dialog box Viewing TM 3.0 server object properties Procedure 39 Viewing TM 3.0 server Object Properties Follow these steps to view the properties of a TM 3.0 server in InfoCenter. In InfoCenter, open a folder in the Folders pane. Select the TM 3.0 server that you added.

  • Page 179: Modifying Tm 3.0 Server Object Properties

    This action launches the default Web browser for your system and connects to the TM 3.0 Web server. page 180 for details on JRE. End of Procedure Figure 66 on page 180. See “Java Runtime Environment for TM 3.0 and Optivity NMS” on CS 1000 Telephony Manager Installation and Configuration...
  • Page 180 Figure 66 Starting TM 3.0 Web applications Java Runtime Environment for TM 3.0 and Optivity NMS TM 3.0 Web applications require Java Plug-In 1.5 on the client browser. Optivity NMS uses JDK 1.1.x, which is older than the version used by TM 3.0. JRE clash for TM 3.0 and Optivity NMS Web clients In both coresident and non-coresident situations, TM 3.0 and Optivity NMS applications cannot be launched simultaneously.
  • Page 181 Start > All Programs > Apache Tomcat 5.5 > Configure Tomcat. Select Java tab on the Apache Tomcat properties page. Update Apache Tomcat path. Click OK or Apply to save changes. Restart Apache Tomcat service. page 182. End of Procedure CS 1000 Telephony Manager Installation and Configuration...

  • Page 182: Web Server

    Figure 67 Apache Tomcat Properties dialog Web server ONMS uses Apache Web server for its Web applications, whereas TM 3.0 uses Internet Information server (IIS). Using FaultSummary TM 3.0 filters and then forwards system traps to ONMS. Because TM 3.0 forms the main representative agent for systems, all alarms received by ONMS result in the change of status state of TM 3.0 depicted in Optivity InfoCenter.
  • Page 183 Modify Application Launch dialog box Procedure 43 Launching FaultSummary Select the TM 3.0 icon and use the right-click menu to launch FaultSummary. See Figure 69 on page Figure 68 on page End of Procedure 184. CS 1000 Telephony Manager Installation and Configuration 183.

  • Page 184: Configuring Tm 3.0

    Figure 69 Launch FaultSummary Configuring TM 3.0 The TM 3.0 server must be set up to forward traps to Optivity NMS. Forwarded traps must be in the TM 3.0 Open Alarm II format to be recognized. 553-3001-230 Standard 10.01 End of Procedure CAUTION —...

  • Page 185: Removing A Tm 3.0 Server

    Check to see if the TM 3.0 OIT files are present and in the correct folder. • Check the oitInstall log file to verify that the TM 3.0 entries were updated. • You need to run oitInstall again. End of Procedure CS 1000 Telephony Manager Installation and Configuration...
  • Page 186 If you cannot see the TM 3.0 server that you have added: • Check the View Properties of the folder to verify that it can display TM 3.0 servers. If you cannot launch or connect to TM 3.0 Web applications: •...

  • Page 187: Integrating Tm 3.0 With Hp Openview

    HP OV NNM to access TM 3.0-related functionality and information. Nortel’s technical support for this feature is limited to support of the two software files that are distributed with TM 3.0, OtmOpenAlarms.mib and OtmStMon.exe. These files are compatible with the version of HP OpenView that was current at the time your TM software was released.

  • Page 188: Limitations

    The TM 3.0 server does not support auto-discovery from NNM. 553-3001-230 Standard 10.01 Telephony TM 3.0 Alarms Manager (TM) Figure 70, Communication Server 1000 and Meridian 1 systems, Meridian September 2007 Integrating TM 3.0 with HP OpenView Meridian 1 M1 Alarms Meridian 1 Device CS1000...

  • Page 189: Hardware And Software Requirements

    TM 3.0 server or of the devices monitored by the TM 3.0 server. Figure 71 on page 190, a TM 3.0 server can be CS 1000 Telephony Manager Installation and Configuration...
  • Page 190 Figure 71 HP OpenView Network Node Manager Network Map The TM 3.0 Status Monitor (OtmStMon) is the program that is used to update the color of the icon for a TM 3.0 object. When the color is changed upon the receipt of an incoming event, a message is also logged and appears in the NNM Alarm Browser to indicate the status update.
  • Page 191 To access the TM 3.0 server from NNM: Highlight the TM 3.0 object on the Network. Select Tools > Web Browser > server Home Page Figure 74 on CS 1000 Telephony Manager Installation and Configuration Figure 73. You can page...

  • Page 192: Installation And Configuration

    TM 3.0 Alarm Browser. Installation and configuration TM 3.0 Alarm Integration Package (HP OV PC) Copy the OtmStMon.exe to the Openview/bin ($OV_BIN) directory. Copy the OtmOpenAlarms.mib to the directory $OV_SNMP_MIB/Vendor/Nortel. Create this directory if it does not already exist. 553-3001-230 Standard 10.01...
  • Page 193 Procedure 46 Installing TM 3.0 Alarm MIB Select Options > Load/Unload MIBs: SNMP. See Figure 75 NNM Load/Unload MIBs Click Load in the Load/Unload MIBs dialog box. See Figure Figure 76 on page CS 1000 Telephony Manager Installation and Configuration 194.
  • Page 194 Figure 76 Load/Unload MIBs Open the OtmOpenAlarms.mib file. See Figure 77 Load MIB 553-3001-230 Standard 10.01 Figure September 2007 Integrating TM 3.0 with HP OpenView...
  • Page 195 Select Options > Event Configuration. See Figure 78 NNM Main Menu - Event Configuration Locate and select “otmOpenAlarmEp” from the list of Enterprises. See page 196. End of Procedure Figure CS 1000 Telephony Manager Installation and Configuration Figure 79 on...
  • Page 196 Figure 79 Event Configuration There are six events defined for the otmOpenAlarmEp Enterprise. For each event, you configure the desired actions to be taken if the event occurs. Use the TM 3.0 Major Alarm event (otmOpenAlarmMajor, Specific 2) as an example: Double-click the corresponding entry on the list.
  • Page 197 Integrating TM 3.0 with HP OpenView Figure 80 Modify Events - Description Select the Event Message tab. See Figure 81 on page 198. CS 1000 Telephony Manager Installation and Configuration...
  • Page 198 Figure 81 Modify Events - Event Message Configure the following: Actions: Select Log and display in category: Status Alarms. This enables the display of the incoming event message in the NNM Alarm Browser. Severity: Select Major for this event. Event Log Message: Enter the following default text: TM 3.0 event $o (enterprise:$e generic:$G specific:$S), $# args: $* The displayed message shows the contents of the event message.
  • Page 199 Print the number of attributes in the event. Print all the attributes as seq name (type): value strings, where seq is the attribute sequence number. CS 1000 Telephony Manager Installation and Configuration Figure 82 on page 200.
  • Page 200 Figure 82 Modify Events - Actions TM 3.0 Status Monitor The TM 3.0 Status Monitor enables you to change the color of the TM 3.0 object on the Network Map to reflect the current status of the server. In addition, a message is also logged onto the HP OV NNM Alarm Browser to indicate the status change.
  • Page 201 To set up a TM 3.0 server object on the Network Map: Locate the appropriate place in the Network Map for the TM 3.0 server. Select Edit > Add Object. See Figure 84 on page 202. CS 1000 Telephony Manager Installation and Configuration Figure...
  • Page 202 Figure 84 NNM Edit - Add Object Select Computer from the Symbol Classes in the Add Object Palette dialog box. Figure 85 on page 553-3001-230 Standard 10.01 203. September 2007 Integrating TM 3.0 with HP OpenView...
  • Page 203 Add Object Palette dialog box Select and drag the standard WindowsNT icon from the Symbol Subclasses. See Figure 86 on page 204 The Add Object dialog box appears. onto the appropriate location on the Network Map. CS 1000 Telephony Manager Installation and Configuration...
  • Page 204 Figure 86 Add Object Palette dialog box II Fill in the Label field (TM 3.0 server-A in this example). See 553-3001-230 Standard 10.01 September 2007 Integrating TM 3.0 with HP OpenView Figure 87 on page 205.
  • Page 205 Integrating TM 3.0 with HP OpenView Figure 87 Add Object dialog box Select IP Map under Object Attributes, and click Set Object Attributes. See Figure 88 on page 206. CS 1000 Telephony Manager Installation and Configuration...
  • Page 206 Figure 88 Add Object - IP Map Select and enter the Hostname, IP Address, and Subnet Mask. See page 207. 553-3001-230 Standard 10.01 September 2007 Integrating TM 3.0 with HP OpenView Figure 89 on...
  • Page 207 Click OK. You are returned to the Add Object dialog box. In the Selection Name field, enter the same value as that of the Hostname in the previous step (pmpkzs5.engwest.baynetworks.com in this example). See CS 1000 Telephony Manager Installation and Configuration Figure 90 on page 208.
  • Page 208 Figure 90 Add Object - Selection Name 553-3001-230 Standard 10.01 September 2007 Integrating TM 3.0 with HP OpenView...
  • Page 209 See address cannot be interpreted locally, then enter the dotted decimal representation. Figure 93 on page CS 1000 Telephony Manager Installation and Configuration to retrieve the DNS Figure 91. If the IP...
  • Page 210 Figure 92 NNM Main Menu - Symbol Properties 553-3001-230 Standard 10.01 September 2007 Integrating TM 3.0 with HP OpenView...
  • Page 211 End of Procedure Procedure 49 Configuring TM 3.0 Web server Access You can also configure the Management URL to access the TM 3.0 server. See Figure 94 on page 212 Figure 95 on page 213. CS 1000 Telephony Manager Installation and Configuration...
  • Page 212 For an object on the Network Map, under General Attributes in the Object Properties dialog box: Enter the address (IP address or the DNS name) of the TM 3.0 server in the ManagementURL field. Set isHTTPSupported to True. Figure 94 Object Properties dialog box 553-3001-230 Standard 10.01...
  • Page 213 Refer to the Alarm Management section in Optivity Telephony Manager: System Administration (553-3001-330) for information about configuring the TM 3.0 server to forward SNMP traps to HP OV NNM or other remote systems. CS 1000 Telephony Manager Installation and Configuration...
  • Page 214 Integrating TM 3.0 with HP OpenView 553-3001-230 Standard 10.01 September 2007...

  • Page 215: Uninstalling Tm 3.0

    Uninstalling TM 3.0 Maintenance mode With TM 3.0 successfully installed, run Setup.exe from the installation CD ROM to enter the InstallShield Wizard Maintenance mode (see Figure 96 on CS 1000 Telephony Manager Installation and Configuration page 216).
  • Page 216 Figure 96 Maintenance mode Maintenance mode provides the following options: • Modify: The Modify option allows the user to perform install and uninstall of TM 3.0 components such as Web Help. • Repair: The Repair option performs a reinstall of the existing installation, overwriting the existing installation's application files without modifying the data files.
  • Page 217 The CND components, if installed, are not removed during a TM uninstallation. You must reboot your computer after TM is uninstalled. Upon completion of the uninstall operation, is Uninstall Complete window appears. See Figure 99 on page 218. CS 1000 Telephony Manager Installation and Configuration...
  • Page 218 Figure 99 Uninstall Complete 553-3001-230 Standard 10.01 September 2007 Uninstalling TM 3.0...

  • Page 219: Windows 2000 Server Reference

    This procedure shows you how to install Windows server using the setup program: Make sure the first bootup option on CD-ROM in the BIOS is enabled. Insert the Windows server setup CD-ROM into the CD-ROM drive. Boot the system. CS 1000 Telephony Manager Installation and Configuration...
  • Page 220 In the Windows server Setup Welcome dialog box, press Enter to set up the Windows server. In the Windows Licensing Agreement dialog box, press Page Down to go to the bottom of the page, and then choose F8. Press C to create a partition, and then type the size of the partition that you want to create.
  • Page 221 Select the Identity tab and click on the This User radio button. Enter the local administrator account and password. Click OK. Note: This procedure works for all applications except DECT. End of Procedure End of Procedure CS 1000 Telephony Manager Installation and Configuration...

  • Page 222: Installing Network Adapter Software

    Before configuring the network adapters, make sure that the adapters are inserted properly into the slots and RJ45 cables are plugged into the adapters. The Nortel server Subnet Interface card is recommended to install on the top PCI slot and ELAN subnet on the second-from-the-top PCI slot.

  • Page 223: Configuring Tcp/Ip

    If the client's IP address changes, the client is not able to log in until the licence file is adjusted. 293" in Appendix A for information about CS 1000 Telephony Manager Installation and Configuration Figure 100 on...
  • Page 224 For PCs with two adapters: • Select adapter “[1]…” and enter the IP Address, Subnet Mask, and Default Gateway for the Nortel server Subnet Interface connection. • Select adapter “[2]…” and enter the IP Address, Subnet Mask, and Default Gateway for the ELAN subnet connection.
  • Page 225 Nortel server Subnet. This causes the server to prefer the Nortel server Subnet network interface for multicast traffic, rather than the ELAN network interface.
  • Page 226 In the “IP Settings” tab, modify the “Interface Metric” value to a value greater than that of the Nortel server Subnet network interface. Click OK to save all changes. Alter the binding order of the Nortel server Subnet network interface to a number-one position by completing the following procedure: Select Start >...

  • Page 227: Installing A Modem

    Double-click the Make New Connection icon. In the Network Connection Wizard welcome dialog box, click Next. In the Network Connection Type dialog box, select Accept incoming connections, and then click Next. End of Procedure CS 1000 Telephony Manager Installation and Configuration...
  • Page 228 In the Devices for Incoming Connections dialog box, select the appropriate connection device, and then click Next. In the Incoming Virtual Private Connection dialog box, select Do not allow virtual private connections check box, and then click Next. In the Allowed Users dialog box, select the users that are allowed to connect to the server, and then click Next.

  • Page 229: Testing Network Cards

    Testing the Nortel server subnet interface Network connectivity can be verified by pinging a server or workstation known to be accessible only through the Nortel server subnet. This could be an TM 3.0 Web client or other server. From Command Prompt window on the TM 3.0 server, enter the command ping <IP address>.
  • Page 230 Windows 2000 server reference 553-3001-230 Standard 10.01 September 2007...

  • Page 231: Windows Server 2003 Configuration

    Web service extensions node in IIS Manager. To do this, the administrator must either enable a pre-existing Web service extension or add a new Web service extension. For TM Web navigator to function, 3 Web Service extensions need to be enabled in IIS. CS 1000 Telephony Manager Installation and Configuration...
  • Page 232 Enabling Web Service extensions in IIS 6.0 Procedure 60 Enabling Web Service extensions in IIS 6.0 To enable IIS to serve content that requires the ASP extension and Server Side Includes, follow these steps: Open IIS Manager, expand the master server node (that is, the Servername node), and select the Web service extensions node.

  • Page 233: Add A New Isapi Web Service Extension To Iis 6.0

    Repeat step 4 for Jakarta ISAPI file. After selecting the path and file name (<tmroot>/ Tomcat/Bin/ISAPI_redirector2.dll), click OK. Click to select the Set extension status to Allowed check box. Click OK to save your changes. page 234). End of Procedure CS 1000 Telephony Manager Installation and Configuration...

  • Page 234: Enabling Parent Paths

    Figure 104 Enabling new ISAPI extension Enabling parent paths Procedure 62 Enabling parent paths Enabling parent paths specifies whether an ASP page allows paths relative to the current directory (using the ..\ notation). In IIS 6.0, parent paths are no longer enabled by default. This affects TM 3.0 as it has Web pages that contain the #include server-side include directive and uses ".."...
  • Page 235 Windows server 2003 configuration In the Application configuration section, select the Enable parent paths check box. Click OK. Figure 105 Enabling parent paths CS 1000 Telephony Manager Installation and Configuration...

  • Page 236: Configuring Iis 5.0 Isolation Mode

    Figure 106 Options tab Configuring IIS 5.0 isolation mode Procedure 63 Configuring IIS 5.0 isolation mode IIS 6.0 can run in one of two possible modes on Microsoft Windows Server 2003, IIS 5.0 isolation mode and worker process isolation mode. The default isolation mode of IIS 6.0 in Windows 2003 is worker process.
  • Page 237 Click the Service tab, select the Run WWW service in IIS 5.0 isolation mode check box, and then click OK (see To restart the WWW service, click Yes. Figure 107 Run in IIS 5.0 isolation mode Figure 107). End of Procedure CS 1000 Telephony Manager Installation and Configuration...

  • Page 238: Adjusting Internet Explorer Security Settings

    Adjusting Internet Explorer security settings Procedure 64 Adjusting Internet Explorer security settings In Windows Server 2003, Internet Explorer is set to enhanced security configuration by default. The default settings of the security zones in Windows Server 2003 are also changed. TM 3.0 Web applications have functions that require privileges granted in the Medium-low default security template.
  • Page 239 Windows server 2003 configuration Figure 108 Adding Trusted site CS 1000 Telephony Manager Installation and Configuration...

  • Page 240: Remote Desktop And Terminal Server

    Figure 109 Add the TM 3.0 Web site Remote Desktop and Terminal Server Remote Desktop for Administration and Terminal Server are components of Windows Server 2003. Terminal Server allows multiple remote clients to simultaneously access Windows-based applications that run on the server and Remote Desktop provides administrators with remote access to manage the server.

  • Page 241: Configuring Client Authentication On The Server Side

    Windows 2003 Service Pack 1 COM permissions restrict remote calls that are not authenticated. Complete Procedure 65 on page 242 to allow TM 3.0 clients to authenticate to the TM 3.0 server. For more information, refer to the following URL: http://support.microsoft.com/?kbid=892500 CS 1000 Telephony Manager Installation and Configuration...
  • Page 242 Procedure 65 Configuring client authentication on the server side For client authentication, grant remote access, launch and activation permissions to Anonymous Logon: Click Start, click Administrative Tools, Component Services. Expand the Component Services\Computers container. Right-click My Computer, click Properties (see Figure 111 on On the COM Security tab, click Edit Limits in the Access Permissions (see Figure 112 on Add Anonymous to the list of UserIDs and click Allow for Remote Access...
  • Page 243 Windows server 2003 configuration Figure 111 Component Services CS 1000 Telephony Manager Installation and Configuration...
  • Page 244 Figure 112 Com Security tab 553-3001-230 Standard 10.01 September 2007 Windows server 2003 configuration...
  • Page 245 Windows server 2003 configuration Figure 113 Access Permissions CS 1000 Telephony Manager Installation and Configuration...
  • Page 246 Figure 114 Launch Permission Data Execution Prevention Settings Data Execution Prevention (DEP) settings can cause applications within TM to not execute, therefore you must ensure that (DEP) settings are appropriately set. DEP is controlled through parameters in the BOOT.ini file which can be set in the System dialog box in Control Panel.

  • Page 247: Configuring Security For Tm 3.0

    Configuring security for TM 3.0 Note: IIS and FTP services must be installed before completing this procedure. Run the Security Configuration Wizard from Start > Programs > Administrative Tools (see Figure 115 on page 248). Click Next. CS 1000 Telephony Manager Installation and Configuration...
  • Page 248 Figure 115 Security Configuration Wizard The Configuration Action window appears (see Figure 116 on Create a new security policy and click Next. 553-3001-230 Standard 10.01 September 2007 Windows server 2003 configuration page 249). Select...
  • Page 249 Figure 116 Create a new security policy The Select Server window appears (see Figure 117 on page 251). Select or enter a server name and click Next. CS 1000 Telephony Manager Installation and Configuration page 250 and Figure 118 on...
  • Page 250 Figure 117 Select a server 553-3001-230 Standard 10.01 September 2007 Windows server 2003 configuration...
  • Page 251 The Role based service configuration window appears (see Figure 119 on page 252). Click Next. The Select Server Roles window appears. Ensure your checked server roles match those in Figure 120 on page 254. page 253 CS 1000 Telephony Manager Installation and Configuration and Figure 121 on...
  • Page 252 Figure 119 Role based service configuration 553-3001-230 Standard 10.01 September 2007 Windows server 2003 configuration...
  • Page 253 Windows server 2003 configuration Figure 120 Role based service configuration CS 1000 Telephony Manager Installation and Configuration...
  • Page 254 Figure 121 Role based service configuration The Select Client Features screen appears (see Figure 122 on check mark in each box and click Next. 553-3001-230 Standard 10.01 September 2007 Windows server 2003 configuration page 255). Place a...
  • Page 255 The Select Administration Options window appears (see Figure 123 on Accept the defaults for all options, ensuring the following options have check marks: • IIS 5.0 compatibility mode • Task Scheduler CS 1000 Telephony Manager Installation and Configuration page 256).
  • Page 256 Figure 123 Select administration options Note: The following Administration Options are not supported: • Remote desktop administration • Remote windows administration • Terminal Server clustering • Windows Firewall The correct selected options are shown in Figure 124 on page 258. 553-3001-230 Standard 10.01 September 2007...
  • Page 257 Windows server 2003 configuration Figure 124 Select administration options CS 1000 Telephony Manager Installation and Configuration...
  • Page 258 Figure 125 Select administration options The Select additional services window appears (see Figure 126 on Accept the defaults for all options, ensuring the following options have check marks: • Apache Tomcat • OpenLDAP Directory Service change to CND • TMResourceManager •...
  • Page 259 Windows server 2003 configuration Figure 126 Select additional services The Handling Unspecified Services window appears (see Figure 127 on Select Do not change the startup mode of this service and click Next CS 1000 Telephony Manager Installation and Configuration page 260).
  • Page 260 Figure 127 Handling unspecified services The Confirm service changes window appears (see Figure 128 on Next. 553-3001-230 Standard 10.01 September 2007 Windows server 2003 configuration page 261). Click...
  • Page 261 Windows server 2003 configuration Figure 128 Confirm service changes 10 The Network security window appears (see Figure 128 on page 261). Place a checkmark in the Skip this section checkbox and click Next. CS 1000 Telephony Manager Installation and Configuration...
  • Page 262 Figure 129 Network security 11 The Open Ports and Approve Applications window opens (see Figure 128 on page 261). Accept the defaults, ensuring the inclusion of the following: • Nortel Common Network Directory • TMResourceManager • TMSingletonServer • TMTaskScheduler •...
  • Page 263 12 The Registry Settings window appears (see Figure 131 on checkmark in the Skip this section checkbox and click Next. Do not attempt to edit the Windows Registry. Doing so may result in system failure. IMPORTANT! CS 1000 Telephony Manager Installation and Configuration page 264). Place a...
  • Page 264 Figure 131 Registry settings 13 The Audit Policy window appears (see Figure 132 on in the Skip this section checkbox and click Next. 553-3001-230 Standard 10.01 September 2007 Windows server 2003 configuration page 265). Place a checkmark...
  • Page 265 Windows server 2003 configuration Figure 132 Audit policy 14 The Internet Information Services window appears (see Figure 133 on page 266). Click Next. CS 1000 Telephony Manager Installation and Configuration...
  • Page 266 Figure 133 15 The Select Web service extensions for dynamic content window appears (see Figure 134 on Server Side Includes checkboxes. Click Next. 553-3001-230 Standard 10.01 page 267). Place checkmarks in the Active Server Pages and September 2007 Windows server 2003 configuration...
  • Page 267 16 Click Next until the Prevent anonymous users from accessing content files window appears. Ensure the Deny anonymous users write access to content files check box is not checked (see Figure 135 on page 268). CS 1000 Telephony Manager Installation and Configuration...
  • Page 268 Figure 135 Prevent anonymous users from accessing content files 17 After clicking Next on the IIS Settings Summary windows, save the Security Policy, apply the Security Policy, and reboot the system. 553-3001-230 Standard 10.01 End of Procedure September 2007 Windows server 2003 configuration...

  • Page 269: Setting Up The Metabase Editor Utility

    The Session Timeout value must be entered in all other folders with ASPSessionTimeout as a parameter. Select Administrative Tools > IIS > Default WebSite > Properties. Select HomeDirectory Tab > Configuration. Figure 136 on page CS 1000 Telephony Manager Installation and Configuration 270.
  • Page 270 Select Options Tab and change the SessionTimeout value to 90 - 120 minutes, the same as that selected in step 3. Save the changes. Open the web.xml file of Tomcat in the path <TM installed path>\Tomcat\conf\Web.xml and change the SessionTimeout value to that which was entered in the Metabase.bin.

  • Page 271: Appendix A: Tm 3.0 Engineering Guidelines

    CPU usage, physical memory (RAM), and disk storage • Web and TM 3.0 clients and their impact on TM 3.0 server resources • Communication Server 1000 and Meridian 1 systems and their impact on TM 3.0 server resources IMPORTANT! product bulletins. Please check for updates from Nortel.
  • Page 272 • Communications between the TM 3.0 server and Communication Server 1000 and Meridian 1 systems, TM 3.0/Web clients, and so on, and their impact on the network to which they are connected. The Billing applications result in a processor load that is not possible to predict. The exact impact depends on several factors, including types of reports generated and quantity of data merged.

  • Page 273: Hardware And Software Comparisons

    Appendix A: TM 3.0 engineering guidelines Hardware and software comparisons Table 13 shows a list of machine types for Meridian 1 with CS 1000 Release 4.0. Table 13 Hardware Machine Type with CS 1000 Release 4.0 When ‘Signaling server’ checkbox in ‘Network’...

  • Page 274: Software Limits

    Software limits Co-residency support Table 14 shows the current list of available co-residency support for TM 3.0. Table 14 Co-residency support (Part 1 of 9) Operating System Browser Windows XP IE 6 English Professional Windows IE 6 English Server 2003 553-3001-230 Standard 10.01 Office...
  • Page 275 • Excel 2003 3.0 English server • Word 2003 (from Office installation XP) in English CS 1000 Telephony Manager Installation and Configuration Other Coresident Applications • ONMS 10.3 • CallPilot 3.0/4.0 Application Builder • SCCS 5.0 System Management Interface (SMI) Workbench (English) •...
  • Page 276 Table 14 Co-residency support (Part 3 of 9) Operating System Browser Windows IE 6 French 2000 Professional in French 553-3001-230 Standard 10.01 Office TM 3.0 Components Installed • Excel 2003 3.0 French client or • Word 2003 (from Office standalone XP) in French September 2007 Appendix A: TM 3.0 engineering guidelines...
  • Page 277 Excel 2003 3.0 German client or • Word 2003 (from Office standalone XP) in German CS 1000 Telephony Manager Installation and Configuration Other Coresident Applications • ONMS 10.3 • CallPilot 3.0/4.0 Application Builder • SCCS 5.0 System Management Interface (SMI) Workbench (German) •...
  • Page 278 Table 14 Co-residency support (Part 5 of 9) Operating System Browser Windows IE 6 2000 Japanese Professional in Japanese 553-3001-230 Standard 10.01 Office TM 3.0 Components Installed • Excel 2003 3.0 English client or • Word 2003 (from Office standalone XP) in Japanese September 2007...
  • Page 279 3.0 English client or • Word 2003 (from Office standalone XP) in Simplified Chinese CS 1000 Telephony Manager Installation and Configuration Other Coresident Applications • ONMS 10.3 • CallPilot 3.0/4.0 Application Builder • SCCS 5.0 System Management Interface (SMI) Workbench (Simplified Chinese) •...
  • Page 280 Table 14 Co-residency support (Part 7 of 9) Operating System Browser Windows IE 6 Spanish 2000 Professional in Spanish 553-3001-230 Standard 10.01 Office TM 3.0 Components Installed • Excel 2003 3.0 English client or • Word 2003 (from Office standalone XP) in Spanish September 2007...
  • Page 281 Excel 2003 3.0 English server • Word 2003 (from Office installation XP) in Simplified Chinese CS 1000 Telephony Manager Installation and Configuration Other Coresident Applications • ONMS 10.3 • CallPilot 3.0/4.0 Application Builder • SCCS 5.0 System Management Interface (SMI) Workbench (English) •...
  • Page 282 Symposium Agent Greeting 2.0 on IE 6 • BCM 3.5 Web Management Interface on IE 6 • Nortel Hospitality Integrated Voice Services version 1.17 Web browser management tool on IE 6. • CallPilot 2.5/3.0 Web clients (My CallPilot) on IE 6 •...
  • Page 283 Max String Length for: Site name System name Address City State/Province Country Zip/Postal Code Comments IP Address Timeout Phone Number Modem Access ID Parameter CS 1000 Telephony Manager Installation and Configuration Maximum Value 3 000 0-9999999 3 000 2 000...
  • Page 284 Table 15 TM 3.0 capacity parameters (Part 2 of 5) Modem Password Modem Installation String Issue System ID Maximum Speed Call Lists Maximum ACD Agents PDT password Customer Name Directory Numbers Customer Password HLOC Dial Intercom Group User ID Corporate Directory Maximum number of reports that can be generated at the same time Maximum string length of all parameters Maximum number of entries in Corporate Directory file uploaded to Large...
  • Page 285 Maximum number of DECT Systems Maximum String length for: DECT system name Password IP Address TM 3.0 server IP Interface Phone Number PARI (Access Right Identification tab) SARI (Access Right Identification tab) Parameter CS 1000 Telephony Manager Installation and Configuration Maximum Value Unlimited...
  • Page 286 Table 15 TM 3.0 capacity parameters (Part 4 of 5) Upstream Manager IP address (Access Right Identification tab) Web Maintenance Maximum number of maintenance commands that can be executed at the same time in Web Maintenance TM 3.0 Web Maximum supported number of clients that can log on to the Administration page of the same TM 3.0 server at the same time Maximum number of telephones that can be assigned to an end user Data Buffering and Access (DBA)
  • Page 287 Starting with Release 25 of Meridian 1 system software and in all releases of Communication server 1000 software, there is the capability of filtering traps, on the PBX, based upon their categorization (for example, minor, major, critical, and so on).

  • Page 288: Operational Limits

    determines how often call records are archived to ensure that there is adequate capacity to receive additional call records. However, the larger the database, the more often archiving is required to achieve the desired result. The recommended maximum of 3,500 lines per PBX is a conservative limit based upon the assumption that a PBX with 3,500 lines generates approximately 800,000 call records per month.
  • Page 289 When additional clients attempt to access Web Services and there are no available connections, an error message appears. See IIS on Windows 2000 server Only limited by TM 3.0 capacity Figure 137 on page CS 1000 Telephony Manager Installation and Configuration PWS on Windows 2000 Professional 290.

  • Page 290: Pc Hardware

    Figure 137 Too-many-users-are-connected error message PC hardware This section describes the PC hardware requirements necessary to run TM 3.0 optimally. Use the guidelines provided in the sections “Physical memory” on disk” on page See “TM 3.0 hardware requirements” on • Add additional serial interface cards as needed.

  • Page 291: Hard Disk

    TM 3.0 disk-intensive applications analyzed in this document include: • CDR and traffic collection • TBS report generation “Hard disk” on page -291 for details.) CS 1000 Telephony Manager Installation and Configuration...
  • Page 292 • Simultaneous Update of Station Data Station Update from a single system is not affected by disk performance, as the speed of transmission from the system is slower than the PC accessing its disk. • Web station Access “Physical memory” also recommends a single hard disk.

  • Page 293: Typical Configurations

    Note that some TM 3.0 applications cannot work over a serial connection. For more information, Table 9: “CS 1000 and Meridian 1 software requirements” on page shows how TM 3.0 connects to systems that do not support Ethernet. In this...
  • Page 294 The diagram only shows the TM 3.0 server, but it is possible for a TM 3.0 client to be used. The TM 3.0 client requires the same serial connections to the managed systems as the TM 3.0 server. The usual limitations of the TM 3.0 client apply, such as the need for a high bandwidth connection between the TM 3.0 client and the TM 3.0 server.
  • Page 295 ELAN subnet when other application servers (e.g., SCCS) are present. The use of shared media hubs can result in adverse system impact under some conditions. and, in this appendix, CS 1000 Telephony Manager Installation and Configuration “TM 3.0 server “Network bandwidth” on...
  • Page 296 There are two choices for this ELAN configuration: • The TM 3.0 server or client is connected only to the Nortel server subnet (or another subnet of the customer’s Enterprise IP network) and has a routed connection to the ELAN subnets of managed systems.
  • Page 297 Appendix A: TM 3.0 engineering guidelines • If an ELAN Network interface is not present to the ELAN subnet of any managed system, a routed connection is required from the Nortel server subnet interface to the ELAN subnet. • TM 3.0 client access to the TM 3.0 server. Due to the high bandwidth requirements of this connection it is important that the TM 3.0 client to TM 3.0 server connection...
  • Page 298 Figure 139 Standalone TM 3.0 server with Dual NIC configuration Figure 140 Standalone TM 3.0 server with routed connections 553-3001-230 Standard 10.01 Appendix A: TM 3.0 engineering guidelines September 2007...

  • Page 299: Vpn Connections

    LAN and only the connectivity to the remote Switch is allowed to go over the WAN. In such scenarios, Nortel recommends that pcAnywhere be used to connect to the TM 3.0 server and/or TM 3.0 clients for management.

  • Page 300: Bandwidth Utilization

    Table 17 lists the average and peak traffic for the ELAN subnet and Nortel server subnet. This is based upon traffic analysis of a system running on a CP4 CPU. For an Cabinet system system, divide the ELAN subnet numbers by 2, except for alarms. For the CPP CPU, multiply the ELAN subnet numbers by 4, except for alarms.

  • Page 301: Recommended Usage

    1000 devices, each producing one trap every 10 seconds, would require a bandwidth of 320 Kbps: 400 bytes/trap * 8 bits/byte * 1000 devices * 0.1 trap/sec/device = 320 Kbps IP Line/IP Trunk /Switch alarm details Under normal conditions, a system generates one trap approximately every ten seconds.

  • Page 302: Tm 3.0 System Performance

    When retrieval occurs, the information is collected from all cards on all nodes. There is no capability to retrieve the information about an individual node basis. The retrieved information is parsed and written to comma separated values (CSV) files on the TM 3.0 server. The number of files created is dependent upon the number of records retrieved.
  • Page 303 Bandwidth in a lab environment. Note the negative exponential impact of using bandwidth that is less than 2 Mbps. Figure 143 Response Time versus Network Bandwidth RTT (miliseconds) CS 1000 Telephony Manager Installation and Configuration Response vs RTT Linear (Response vs RTT)

  • Page 304: Hostname Resolution

    The LMHOSTS file is a text file in the Windows directory that lists the IP addresses and computer names of remote Windows networking servers with which you want to communicate. The LMHOSTS file should list all the names and IP addresses of the servers you regularly access.
  • Page 305 Appendix A: TM 3.0 engineering guidelines Figure 144 Example of LMHOSTS file (part 1) CS 1000 Telephony Manager Installation and Configuration...
  • Page 306 WINS database (because name query requests are not broadcast beyond the local subnetwork). If WINS servers are in place on an internetwork, users do not have to rely on broadcast queries for name resolution because WINS is the preferred method for name resolution.
  • Page 307 The HOSTS file contains a list of host name to IP address mappings. It is a regular text file. The HOSTS file is located in the <system root>\system 32\drivers\etc directory for Windows XP and Windows 2000 systems. See End of Procedure Figure 146 on page CS 1000 Telephony Manager Installation and Configuration 308.

  • Page 308: Tm 3.0 Port Usage

    Figure 146 Sample HOSTS file Use a text editor to edit the HOSTS file. In the HOSTS file, type the IP address and the host name of each computer with which you want to communicate, for example, on each TM 3.0 client computer add the TM 3.0 server IP address followed by its name. Separate the items with at least one space.
  • Page 309 Alarm Notification TM 3.0 NetBEUI Windows client File Sharing CND Synchronization CND synchronization Type Protocol Component CS 1000 Telephony Manager Installation and Configuration Component Remarks Using netstat Microsoft Default Port Microsoft Default Port Microsoft Default Port FTP -data Microsoft Default...
  • Page 310 TM 3.0 Sending Port Web client Web client 8080 Web client 4789- 5045 Win client Win client Meridian 1 or Communication Port server 1000 sending to TM 3.0 TM 3.0 1929 2058 DECT 5099 553-3001-230 Standard 10.01 Type Protocol HTTP...

  • Page 311: Tm 3.0 Language Support

    English TM 3.0 English TM 3.0 English TM English English English TM 3.0 TM 3.0 TM 3.0 CS 1000 Telephony Manager Installation and Configuration Portuguese Spanish French German Win2K/XP Win2K/ Win2K/ XP Pro XP Pro English English English TM 3.0 TM 3.0...
  • Page 312 Appendix A: TM 3.0 engineering guidelines 553-3001-230 Standard 10.01 September 2007...

  • Page 313: Appendix B: Installation Checklist

    PC/server installation requirements......Overview Use the following quick reference as a checklist or reminder when starting a new TM 3.0 installation. CS 1000 Telephony Manager Installation and Configuration...

  • Page 314: Installation Requirements

    Installation requirements Software and memory Required X11 packages (296, 315, and 351 depending on applications installed) Ethernet connections [ ] Release 24B or later for Data Buffering and Access [ ] IOP, IOP/CMDU, or IODU/C cards for Meridian 1 PBX 51C, 61C, 81, or 81C [ ] Ethernet AUI cables to be attached to each IOP (Meridian 1 PBX 51C, 61C, 81, or 81C) [ ] NTDK27 Ethernet cable for Meridian 1 PBX 11C CA...
  • Page 315 [ ] Set up filtering in the system to filter out information and minor messages. PC/server installation requirements For detailed TM 3.0 minimum hardware and software requirements, see installation” on page CS 1000 Telephony Manager Installation and Configuration “Preparing for...
  • Page 316 Appendix B: Installation checklist 553-3001-230 Standard 10.01 September 2007...

  • Page 317: Appendix C: Configuring A Usb Modem

    If running Windows 2000, go to Start > Settings > Control Panel > Phone and Modem Options. From Windows XP, go to Start > Control Panel > Phone and Modem Options. CS 1000 Telephony Manager Installation and Configuration...
  • Page 318 Figure 147 Phone and modem options Click the Modems tab (see If the modem is not connected to the computer, it does not appear in the installed modems list. Connect the modem and repeat steps 1-3. If your modem is connected to your server, and is properly installed, but still does not appear in this list, TM 3.0 does not support your modem.
  • Page 319 Expand the Modems node of the tree and select your USB modem. Right-click and select Properties from the popup menu. Click the Advanced tab. Figure 148 on U.S. Robotics USB modem. page 320 shows an example for the CS 1000 Telephony Manager Installation and Configuration...
  • Page 320 Figure 148 Modem properties 10 Select the Advanced Port Settings button. A dialog similar to Figure 149 on page 321 553-3001-230 Standard 10.01 appears. September 2007 Appendix C: Configuring a USB modem...
  • Page 321 COM port, the old virtual COM port is removed, and the new one created. You can now use this virtual COM port in the Telecom Billing System. 13 Close all open Device Manager and property dialogs. CS 1000 Telephony Manager Installation and Configuration...
  • Page 322 Appendix C: Configuring a USB modem 553-3001-230 Standard 10.01 September 2007...
  • Page 323 OTM Server, 213 hardware and software requirements, 189 installation and configuration, 192 installation Desktop Services, 124 HP OpenView, 192 Windows 2000, 219 Windows NT component installation network adapter software CS 1000 Telephony Manager Installation and Configuration , 220 , 222...
  • Page 324 Java Runtime Environment, 172, 180 JRE. See Java Runtime Environment. keycode, 93 licenses Reporting Unit, 94 Terminal Number, 93 limitations software hard-coded , 283 operational , 288 local users, 141 login, 112, 142 M1. See Meridian 1. memory requirements, 291 Meridian 1 programming, 314 software requirements, 314...
  • Page 325 Web, 165 Web reporting role, 124 Web Station, 288 Web Virtual System Terminal, 165 Windows 2000 installing, 219 setup program, 219 Windows NT component installation, 220 network adapter software installation, 222 X11 packages, 314 CS 1000 Telephony Manager Installation and Configuration...
  • Page 326 553-3001-230 Standard 10.01 September 2007...
  • Page 328 Users must take full responsibility for their applications of any products specified in this document. The information in this document is proprietary to Nortel Networks. Nortel, Nortel (Logo), the Globemark, SL-1, Meridian 1, and Succession are trademarks of Nortel Networks.

This manual is also suitable for:

Telephony managerTelephony manager 3.0

Table of Contents