Avaya Ip Line Users Manual Description, Installation, And Operation
2015-06-01
: Avaya Avaya-Ip-Line-Users-Manual-737189 avaya-ip-line-users-manual-737189 avaya pdf
Open the PDF directly: View PDF 
.
Page Count: 772
| Download | |
| Open PDF In Browser | View PDF |
Title page Nortel Networks Communication Server 1000 Nortel Networks Communication Server 1000 Release 4.0 IP Line Description, Installation, and Operation Document Number: 553-3001-365 Document Release: Standard 3.00 Date: September 2004 Year Publish FCC TM Copyright © 2003- 2004 Nortel Networks All Rights Reserved Produced in Canada Information is subject to change without notice. Nortel Networks reserves the right to make changes in design or components as progress in engineering and manufacturing may warrant. SL-1, Meridian 1, and Succession are trademarks of Nortel Networks. 4 Page 3 of 770 Revision history September 2004 Standard 3.00. This document is up-issued for Nortel Networks Communication Server 1000 Release 4.0. May 2004 Standard 2.00. This document is up-issued to support the Nortel Networks Mobile Voice Client 2050 (MVC 2050). 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. This document contains information previously contained in the following legacy document, now retired: IP Line: Description, Installation and Operation (553-3001204). Content from IP Line: Description, Installation and Operation (553-3001204) also appears in: • Data Networking for Voice over IP (553-3001-160), • Communication Server 1000M and Meridian 1: Small System Planning and Engineering (553-3011-120), and • Communication Server 1000M and Meridian 1: Large System Planning and Engineering (553-3021-120). IP Line Description, Installation, and Operation Page 4 of 770 553-3001-365 Standard 3.00 September 2004 12 Page 5 of 770 Contents About this document . . . . . . . . . . . . . . . . . . . . . . . 13 Subject .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Applicable systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Conventions .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Related information .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Contents .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Applicable systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 System configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Software delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Required packages .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 IP Line package components lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Voice Gateway Media Cards .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Virtual superloops, virtual TNs, and physical TNs .. . . . . . . . . . . . . . . 50 Licenses .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Administration .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 IP Line Description, Installation, and Operation Page 6 of 770 Contents Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Introduction .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 NAT Traversal feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Firmware download using UNIStim FTP . . . . . . . . . . . . . . . . . . . . . . . 83 Personal Directory, Callers List, and Redial List . . . . . . . . . . . . . . . . . 93 IP Call Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 pbxLink connection failure detection . . . . . . . . . . . . . . . . . . . . . . . . . . 96 LD 117 STAT SERV enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 IP Phone support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Corporate Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Element Manager support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Call Statistics collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 User-defined feature key labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Private Zone configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Run-time configuration changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Network wide Virtual Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Branch Office and Media Gateway 1000B .. . . . . . . . . . . . . . . . . . . . . 126 802.1Q support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Data Path Capture tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 IP Phone firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Graceful Disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Hardware watchdog timer .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Codecs .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Set type checking and blocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Enhanced Redundancy for IP Line nodes .. . . . . . . . . . . . . . . . . . . . . . 142 Personal Directory, Callers List, and Redial List . 145 553-3001-365 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Introduction .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Standard 3.00 September 2004 Contents Page 7 of 770 Personal Directory .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Callers List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Redial List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 IP Phone Application Server configuration and administration . . . . . . 152 IP Phone Application Server database maintenance . . . . . . . . . . . . . . . 160 Call Server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Password administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 User profile management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Codecs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Contents .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Codec configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Codec registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Codec negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Codec selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Installation and configuration summary . . . . . . . . 195 Contents .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Installation summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Voice Gateway Media Card installation summary sheet . . . . . . . . . . . 198 Installation and initial configuration of an IP telephony node . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Contents .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Equipment considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Install the hardware components .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Initial configuration of IP Line 4.0 data . . . . . . . . . . . . . . . . . . . . . . . . 228 Node election rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 IP Line Description, Installation, and Operation Page 8 of 770 Contents Configuration of IP telephony nodes using OTM 2.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 Introduction .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 Configure IP Line data using OTM . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 Transmit node configuration from OTM 2.2 to the Voice Gateway Media Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 Upgrade the Voice Gateway Media Card software and IP Phone firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 Configure OTM Alarm Management to receive IP Line SNMP traps .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 Assemble and install an IP Phone .. . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 Change the default IPL> CLI Shell password . . . . . . . . . . . . . . . . . . . 328 Configure the IP Phone Installer Passwords .. . . . . . . . . . . . . . . . . . . . 328 Configuration of IP Telephony nodes using Element Manager . . . . . . . . . . . . . . . . . . . . . 329 553-3001-365 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 Introduction .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 Configure IP Line 4.0 data using Element Manager . . . . . . . . . . . . . . 331 Transfer node configuration from Element Manager to the Voice Gateway Media Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . 371 Upgrade the Voice Gateway Media Card software and IP Phone firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382 Configure Alarm Management to receive IP Line SNMP traps .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408 Assemble and install an IP Phone .. . . . . . . . . . . . . . . . . . . . . . . . . . . . 408 Change the default IPL> CLI Shell password . . . . . . . . . . . . . . . . . . . 408 Configure the IP Phone Installer Passwords .. . . . . . . . . . . . . . . . . . . . 408 Import node configuration from an existing node . . . . . . . . . . . . . . . . 409 Standard 3.00 September 2004 Contents Page 9 of 770 IP Line 4.0 administration . . . . . . . . . . . . . . . . . . . . 413 Contents .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 IP Line feature administration .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 Password security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420 IP configuration commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441 TLAN configuration commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441 Display the number of DSPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 Display IP Telephony node properties . . . . . . . . . . . . . . . . . . . . . . . . . 443 Display Voice Gateway Media Card parameters . . . . . . . . . . . . . . . . . 445 Packet loss monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448 Transfer files using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449 Download the IP Line 4.0 error log .. . . . . . . . . . . . . . . . . . . . . . . . . . . 451 Reset the Operational Measurements file . . . . . . . . . . . . . . . . . . . . . . . 451 IP Line administration using OTM 2.2 . . . . . . . . . . 453 Contents .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454 OTM administration procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454 Back up and restore OTM data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467 Update IP Telephony node properties using OTM . . . . . . . . . . . . . . . . 468 Update Voice Gateway Media Card card properties .. . . . . . . . . . . . . . 491 Add an IP Telephony node in OTM by retrieving an existing node . . . 499 IP Line CLI access using Telnet or local RS-232 maintenance port . . 503 IP Line administration using Element Manager . . 505 Contents .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506 Element Manager administration procedures . . . . . . . . . . . . . . . . . . . . 506 Backup and restore data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516 Update IP Telephony node properties .. . . . . . . . . . . . . . . . . . . . . . . . . 520 IP Line Description, Installation, and Operation Page 10 of 770 Contents Update other node properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551 Telnet to a Voice Gateway Media Card using Virtual Terminal . . . . . 551 Check the Voice Gateway Channels .. . . . . . . . . . . . . . . . . . . . . . . . . . 554 Setting the IP Phone Installer Password . . . . . . . . . . . . . . . . . . . . . . . . 558 Voice Gateway Media Card maintenance . . . . . . . 567 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567 Introduction .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568 Faceplate maintenance display codes . . . . . . . . . . . . . . . . . . . . . . . . . . 568 System error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573 IP Line and IP Phone maintenance and diagnostics – LD 32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579 IP Line CLI commands .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585 Lamp Audit and Keep Alive functions . . . . . . . . . . . . . . . . . . . . . . . . . 627 Voice Gateway Media Card self-tests . . . . . . . . . . . . . . . . . . . . . . . . . 633 Troubleshoot a software load failure . . . . . . . . . . . . . . . . . . . . . . . . . . 633 Troubleshoot an IP Phone installation . . . . . . . . . . . . . . . . . . . . . . . . . 636 Maintenance telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637 Upgrade Voice Gateway Media Card 8051 XAController firmware . . 638 Replace the Media Card’s CompactFlash .. . . . . . . . . . . . . . . . . . . . . . 645 Voice Gateway Media Card maintenance using OTM 2.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647 553-3001-365 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647 Introduction .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647 Replace a Voice Gateway Media Card . . . . . . . . . . . . . . . . . . . . . . . . . 648 Access the IPL> CLI from OTM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658 Add a “dummy” node for retrieving and viewing IP Telephony node configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658 Standard 3.00 September 2004 Contents Page 11 of 770 Voice Gateway Media Card maintenance using Element Manager . . . . . . . . . . . . . . . . . . . . . 667 Contents .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667 Replace a Voice Gateway Media Card . . . . . . . . . . . . . . . . . . . . . . . . . 668 Add another Voice Gateway Media Card . . . . . . . . . . . . . . . . . . . . . . . 674 Access CLI commands from Element Manager . . . . . . . . . . . . . . . . . . 677 Access the IPL> CLI from Element Manager .. . . . . . . . . . . . . . . . . . . 691 Convert IP Trunk Cards to Voice Gateway Media Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693 Contents .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693 Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694 Convert the IP Trunk cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694 Add the converted cards to an IP Telephony node . . . . . . . . . . . . . . . . 697 Appendix A: NAT router requirements for NAT Traversal feature . . . . . . . . . . . . . . . . . . . . . . . . . . . 709 Contents .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709 Requirements .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710 Natcheck output .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714 Appendix B: I/O, maintenance, and extender cable description . . . . . . . . . . . . . . . . . . . 717 Contents .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717 NTMF94EA I/O cable .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718 Connector pin assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720 NTAG81CA maintenance cable description .. . . . . . . . . . . . . . . . . . . . 724 NTAG81BA maintenance extender cable .. . . . . . . . . . . . . . . . . . . . . . 725 IP Line Description, Installation, and Operation Page 12 of 770 Contents Replace the NT8D81BA cable with the NT8D1AA cable and install the NTCW84JW special IPE filter . . . . . . . . . . . . . . . . . . . 726 Appendix C: RM356 Modem Router . . . . . . . . . . . 731 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731 Introduction .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731 RM356 Modem Router security features . . . . . . . . . . . . . . . . . . . . . . . 732 Install the RM356 Modem Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734 Configure the RM356 Modem Router from the manager menu . . . . . 735 RM356 Modem Router manager menu description . . . . . . . . . . . . . . . 743 Appendix D: Product integrity . . . . . . . . . . . . . . . . 753 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753 Introduction .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753 Reliability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753 Environmental specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754 Electrical regulatory standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756 Appendix E: Subnet Mask Conversion from CIDR to Dotted Decimal Format . . . . . . . . . . . . . . . . . . . 761 Introduction .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761 Appendix F: Download IP Line 4.0 files from Nortel Networks web site . . . . . . . . . . . . . . . . . . . . 763 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763 Introduction .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763 Download files from Nortel Networks web site . . . . . . . . . . . . . . . . . . 763 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765 553-3001-365 Standard 3.00 September 2004 18 Page 13 of 770 About this document This document is a global document. Contact your system supplier or your Nortel Networks representative to verify that the hardware and software described are supported in your area. Subject This document: • describes the physical and functional characteristics of the IP Line 4.0 application for Nortel Networks Communication Server (CS) 1000 Release 4.0 and Meridian 1 systems and describes its use on the Voice Gateway Media Cards. • explains how to engineer, install, configure, administer, and maintain an IP Telephony node that contains Voice Gateway Media Cards. Structure This document has separate chapters which are applicable only to either Optivity Telephony Manager (OTM) or Element Manager. The configuration, administration, and maintenance sections are divided into three chapters each. For example, there is a generic configuration chapter dealing with tasks related to installing and configuring IP Line 4.0. This chapter is followed by two other configuration chapters, one for OTM and another for Element Manager. The administration and maintenance chapters have the same format. IP Line Description, Installation, and Operation Page 14 of 770 About this document Note on legacy products and releases This NTP contains information about systems, components, and features that are compatible with Communication Server 1000 Release 4.0 Software. For more information on legacy products and releases, click the Technical Documentation link under Support on the Nortel Networks home page: http://www.nortelnetworks.com/ Applicable systems This document applies to the following systems: • Communication Server 1000S (CS 1000S) • Communication Server 1000M Chassis (CS 1000M Chassis) • Communication Server 1000M Cabinet (CS 1000M Cabinet) • Communication Server 1000M Half Group (CS 1000M HG) • Communication Server 1000M Single Group (CS 1000M SG) • Communication Server 1000M Multi Group (CS 1000M MG) • Communication Server 1000E (CS 1000E) • Meridian 1 PBX 11C Chassis (Meridian 1 PBX 11C Chassis) • Meridian 1 PBX 11C Cabinet (Meridian 1 PBX 11C Cabinet) • Meridian 1 PBX 51C • Meridian 1 PBX 61C • Meridian 1 PBX 61C CP PII • Meridian 1 PBX 81 • Meridian 1 PBX 81C • Meridian 1 PBX 81C CP PII Note: When upgrading software, memory upgrades may be required on the Signaling Server, the Call Server, or both. 553-3001-365 Standard 3.00 September 2004 About this document Page 15 of 770 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. Table 1 Meridian 1 systems to CS 1000M systems This Meridian 1 system... Maps to this CS 1000M system Meridian 1 PBX 11C Chassis CS 1000M Chassis Meridian 1 PBX 11C Cabinet CS 1000M Cabinet Meridian 1 PBX 51C CS 1000M Half Group Meridian 1 PBX 61C CS 1000M Single Group Meridian 1 PBX 61C CP PII CS 1000M Single Group Meridian 1 PBX 81 CS 1000M Multi Group Meridian 1 PBX 81C CS 1000M Multi Group Meridian 1 PBX 81C CP PII CS 1000M Multi Group For more information, see one or more of the following NTPs: • Communication Server 1000M and Meridian 1: Small System Upgrade Procedures (553-3011-258) • Communication Server 1000M and Meridian 1: Large System Upgrade Procedures (553-3021-258) • Communication Server 1000S: Upgrade Procedures (553-3031-258) IP Line Description, Installation, and Operation Page 16 of 770 About this document Conventions Terminology In this document, the following systems are referred to generically as “system”: • Communication Server 1000S (CS 1000S) • Communication Server 1000M (CS 1000M) • Communication Server 1000E (CS 1000E) • Meridian 1 The following systems are referred to generically as “Small System”: • Communication Server 1000M Chassis (CS 1000M Chassis) • Communication Server 1000M Cabinet (CS 1000M Cabinet) • Meridian 1 PBX 11C Chassis (Meridian 1 PBX 11C Chassis) • Meridian 1 PBX 11C Cabinet (Meridian 1 PBX 11C Cabinet) The following systems are referred to generically as “Large System”: 553-3001-365 • Communication Server 1000M Half Group (CS 1000M HG) • Communication Server 1000M Single Group (CS 1000M SG) • Communication Server 1000M Multi Group (CS 1000M MG) • Meridian 1 PBX 51C • Meridian 1 PBX 61C • Meridian 1 PBX 61C CP PII • Meridian 1 PBX 81 • Meridian 1 PBX 81C • Meridian 1 PBX 81C CP PII Standard 3.00 September 2004 About this document Page 17 of 770 Related information This section lists information sources that relate to this document. NTPs The following NTPs are referenced in this document: • Data Networking for Voice over IP (553-3001-160) • Transmission Parameters (553-3001-182) • Signaling Server: Installation and Configuration (553-3001-212) • Branch Office: Installation and Configuration (553-3001-214) • Optivity Telephony Manager: Installation and Configuration (553-3001-230) • Features and Services (553-3001-306) • Emergency Services Access: Description and Administration (553-3001-313) • Optivity Telephony Manager: System Administration (553-3001-330) • Element Manager: System Administration (553-3001-332) • IP Phones: Description, Installation, and Operation (553-3001-368) • Software Input/Output: System Messages (553-3001-411) • Communication Server 1000M and Meridian 1: Small System Planning and Engineering (553-3011-120) • Communication Server 1000M and Meridian 1: Large System Planning and Engineering (553-3021-120) • Communication Server 1000S: Planning and Engineering (553-3031-120) • Communication Server 1000S: Installation and Configuration (553-3031-210) • Communication Server 1000S: Upgrade Procedures (553-3031-258) • Communication Server 1000S: Maintenance (553-3031-500) • Communication Server 1000E: Planning and Engineering (553-3041-120) IP Line Description, Installation, and Operation Page 18 of 770 About this document • IP Phone 2001 User Guide • IP Phone 2002 User Guide • IP Phone 2004 User Guide • Nortel Networks IP Softphone 2050 User Guide • Nortel Networks Mobile Voice Client 2050 User Guide Online To access Nortel Networks documentation online, click the Technical Documentation link under Support on the Nortel Networks home page: http://www.nortelnetworks.com/ CD-ROM To obtain Nortel Networks documentation on CD-ROM, contact your Nortel Networks customer representative. 553-3001-365 Standard 3.00 September 2004 56 Page 19 of 770 Description Contents This section contains information on the following topics: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Voice Gateway Media Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 20 21 Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Applicable systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unsupported products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 23 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OTM 2.2 and Element Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 23 System configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Meridian 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CS 1000 systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 25 25 Software delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Required packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 IP Line package components lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CS 1000 and Meridian 1 package components . . . . . . . . . . . . . . . . IP Line 4.0 Media Card 8-port card package components . . . . . . . . Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 28 30 31 Voice Gateway Media Cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Media Card controls, indicators, and connectors . . . . . . . . . . . . . . . ITG-P 24-port card controls, indicators, and connectors . . . . . . . . . Functional description of the Voice Gateway Media Cards. . . . . . . 31 34 35 38 43 IP Line Description, Installation, and Operation Page 20 of 770 Description IP Phone registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Virtual Terminal Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interactions with IP Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Signaling and messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Signaling protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ELAN TCP transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 46 46 48 48 49 Virtual superloops, virtual TNs, and physical TNs . . . . . . . . . . . . . . . Virtual TNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 51 Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . License limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 53 Zones. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IP Line 4.0 application in OTM 2.2 . . . . . . . . . . . . . . . . . . . . . . . . . Element Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overlays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 54 54 56 56 Introduction CS 1000 Release 4.0 introduces the IP Line 4.0 application. The IP Line 4.0 application provides an interface that connects an IP Phone to a Meridian 1 PBX and a CS 1000 Call Server. Note: IP Line 4.0 does not operate on Meridian 1 or CS 1000 systems running software earlier than CS 1000 Release 4.0. IMPORTANT! IP Line 3.1 (or earlier) is not supported in CS 1000 Release 4.0. Features IP Line 4.0 introduces the following features: • 553-3001-365 support for the Nortel Networks IP Phone Key Expansion Module (KEM) Standard 3.00 September 2004 Description Page 21 of 770 • support for the Nortel Networks IP Phone 2001 • IP Call Recording • Personal Directory for IP Phones • Callers List for IP Phones • Redial List for IP Phones • password protection for the Personal Directory, Callers List, and Redial List • centralized database and administration for the Personal Directory, Callers List, and Redial List • support for UNIStim File Transfer Protocol (UFTP) for IP Phone firmware downloads • support for traversal of Network Address Translation (NAT) devices Voice Gateway Media Cards If a Media Card 32-port card, a Media Card 8-port card, or an ITG-P 24-port card is running IP Line 4.0 software, it is known as a Voice Gateway Media Card. DHCP server A Dynamic Host Configuration Protocol (DHCP) server can be used to provide the required information to enable the IP Phone network connection and connect to the Voice Gateway Media Card. For more information on DHCP, refer to Data Networking for Voice over IP (553-3001-160) and IP Phones: Description, Installation, and Operation (553-3001-368). Interworking The IP Phone uses the IP network to communicate with the Voice Gateway Media Card and the optional DHCP server. Figure 1 on page 22 shows a diagram of the system architecture. IP Line Description, Installation, and Operation Page 22 of 770 Description Figure 1 System architecture CS 1000M IP Line Branch Media Gateway LAN IP Trunk 3.0 or later Signaling Server (Optionally Redundant) -Terminal Proxy Server -H.323 proxy -Primary Gatekeeper -Element Manager Web Server Signaling Server Signaling Server (Optionally Redundant) -Terminal Proxy Server -H.323 proxy -Alternate Gatekeeper -Element Manager Web Server WAN CS 1000 Call Server Web Browser for Element Manager Signaling Server BCM LAN Requires BCM Release 3.0 or higher IP Phones Media streams routed directly using IP Media Gateway and Media Gateway Expansion 553-AAA0400 553-3001-365 Standard 3.00 September 2004 Description Page 23 of 770 Applicable systems The CS 1000 and Meridian 1 systems support the Media Card 32-port line card, Media Card 8-port line card, and ITG-Pentium 24-port line card. Unsupported products The following remote service products do not support the Media Card 32-port line card, Media Card 8-port line card, and ITG-Pentium 24-port line card: • Carrier Remote • Mini-carrier Remote • Fiber Remote • Fiber Remote Multi-IPE System requirements CS 1000 Release 4.0 software is the minimum system software for IP Line 4.0. OTM 2.2 and Element Manager Optivity Telephony Manager (OTM) 2.2 and Element Manager are used throughout this document as the primary interface for Voice Gateway Media Cards and IP Line 4.0. OTM 2.2 is the minimum required version. CS 1000 systems Either OTM 2.2 or Element Manager can be used as the configuration, administration, and maintenance interface for IP Line 4.0 on a CS 1000 system. If trying to use OTM 2.2 to perform an action available through Element Manager, then OTM 2.2 launches Element Manager automatically. OTM 2.2 is used for configuration activities not supported by Element Manager, such as terminal administration. IP Line Description, Installation, and Operation Page 24 of 770 Description Meridian 1 OTM 2.2 is used as the configuration, administration, and maintenance interface for IP Line 4.0 on a Meridian 1. Element Manager cannot be used, as Element Manager is located on a Signaling Server, and there is no Signaling Server in a Meridian 1. Corporate Directory OTM 2.2 is necessary for creation of the Corporate Directory database. SNMP and alarms Element Manager does not provide a SNMP alarm browser, so the OTM 2.2 Alarm Manager is recommended when SNMP alarm collection is required. System configurations Although IP Line 4.0 can be used in different system configurations and its use can vary in those configurations, there are four basic system configurations. See Table 2. Table 2 Possible system configurations System Signaling Server present 1 Meridian 1 No 2 CS 1000E Yes 3 CS 1000M Yes 4 CS 1000S Yes IP Line 4.0 can use the Signaling Server if the Signaling Server is deployed in the system configuration. 553-3001-365 Standard 3.00 September 2004 Description Page 25 of 770 Meridian 1 A Meridian 1 system does not have a Signaling Server in its configuration. Each Voice Gateway Media Card functions as both a UNIStim Line Terminal Proxy Server (LTPS) and voice gateway. In this system configuration, one line card is configured as the Leader. IP Phones register with individual Voice Gateway Media Cards. Note: If a Media Card 32-port card, a Media Card 8-port card, or an ITG-P 24-port card is running IP Line 4.0 software, it is known as a Voice Gateway Media Card. CS 1000 systems CS 1000 systems have a Signaling Server in their network configuration. The Signaling Server is a server that provides signaling interfaces to the IP network. The Signaling Server’s central processor drives the signaling for IP Phones and IP Peer networking. In IP Line 4.0, the LTPS executes on the Signaling Server and the voice gateway executes on the Voice Gateway Media Cards. All IP Phones register with the Signaling Server. The Voice Gateway Media Cards only provide access to the voice gateway. The Signaling Server is the node leader and, by default, acts as a Master for the node. Signaling Server redundancy There are several methods of redundancy for a Signaling Serve. See Table 3. Table 3 Methods of Signaling Server redundancy (Part 1 of 2) Stage Description With a backup Signaling Server 1 A backup Signaling Server can be configured in a normal configuration. IP Line Description, Installation, and Operation Page 26 of 770 Description Table 3 Methods of Signaling Server redundancy (Part 2 of 2) Stage Description 2 If the primary Signaling Server fails, the backup Signaling Server takes over and all IP Phones register with the backup Signaling Server. 3 If the backup Signaling Server fails, one of the Voice Gateway Media Cards is elected to be the node Master. 4 The IP Phones then register to the Voice Gateway Media Cards. Without a backup Signaling Server 1 If there is no backup Signaling Server, and the primary Signaling Server fails, one of the Voice Gateway Media Cards is elected to be the node Master. 2 The IP Phones then register to the Voice Gateway Media Cards. Software delivery IP Line 4.0 supports software delivery through the following formats: 1 CompactFlash 2 Signaling Server CD-ROM 3 Download from the Nortel Networks web site Note: Stand-alone IP Line 4.0 software is not available through CD-ROM. 553-3001-365 Standard 3.00 September 2004 Description Page 27 of 770 The IP Line 4.0 software and related documentation (such as Readme First documents) can be downloaded from the Nortel Networks web site. Required packages The IP Phones require the software packages listed in Table 4. Table 4 Required packages Package Package number M2000 Digital Sets (DSET) 88 Aries Digital Sets (ARIE) 170 Note: To configure IP Line 4.0 in groups 5-7 on Option 81C CP PII or CS 1000M MG, the Fiber Network (FIBN) software package 365 is required. IP Line Description, Installation, and Operation Page 28 of 770 Description IP Line package components lists CS 1000 and Meridian 1 package components Table 5 lists the IP Line 4.0 package components for CS 1000 and Meridian 1 systems. Table 5 IP Line 4.0 Media Card 32-port line card package components (Part 1 of 2) Component Code Media Card 32-port - IP Line 4.0 Voice Gateway Systems Package includes the following: NTDU41DB • Media Card 32-port assembly NTVQ01BB • IP Line 4.0 Voice Gateway CompactFlash NTM403AB • ITG EMC Shielding Kit (NTVQ83AA) • Readme First Document • Shielded 50-pin to Serial/ELAN/TLAN adaptor • PC Maintenance cable (NTAG81CA) • IP Line 4.0 NTP (CD-ROM) • ITG-specific Meridian 1 Backplane 50-pin I/O Panel Filter Connector (NTCW84JA) (see Note) 553-3001-365 Standard 3.00 September 2004 Description Page 29 of 770 Table 5 IP Line 4.0 Media Card 32-port line card package components (Part 2 of 2) Component Code IP Line 4.0 Voice Gateway NTP (CD-ROM), includes: NTDW81AF • IP Line: Description, Installation, and Operation (553-3001-365) • IP Phones: Description, Installation, and Operation (553-3001-368) • IP Phone 2001 User Guide • IP Phone 2001 Quick Reference Card • IP Phone 2002 User Guide • IP Phone 2002 Quick Reference Card • IP Phone 2004 User Guide • IP Phone 2004 Quick Reference Card • IP Softphone 2050 and Mobile Voice Client 2050 User Guide Note: The I/O panel filter connector is not required for Meridian 1 Option 11C Cabinet, Meridian 1 Option 11C Chassis, CS 1000M Cabinet, CS 1000M Chassis, or CS 1000S systems. IP Line Description, Installation, and Operation Page 30 of 770 Description IP Line 4.0 Media Card 8-port card package components Table 6 lists the IP Line 4.0 Media Card 8-port card package components. The Media Card 8-port card is intended for branch office configurations. The card is applicable to the CS 1000 and Meridian 1 systems. Table 6 IP Line 4.0 Media Card 8-Port card package components Component Code Media Card 8-port - IP Line 4.0 Voice Gateway Systems Package includes: NTDU41EB • Media Card 8-port Assembly NTVQ01AB • IP Line 4.0 CompactFlash NTM403AB • ITG EMC Shielding Kit NTVQ83AA • Readme First Document • Shielded 50-pin to Serial/ELAN/TLAN adaptor • PC Maintenance Cable NTAG81CA • IP Line 4.0 NTP (CD-ROM) NTDW81AF • ITG-specific Meridian 1 Backplane 50-pin I/O Panel Filter Connector (NTCW84JA) (see Note) Note: The I/O panel filter connector is not required for Meridian 1 Option 11C Cabinet, Meridian 1 Option 11C Chassis, CS 1000M Cabinet, CS 1000M Chassis, or CS 1000S systems. 553-3001-365 Standard 3.00 September 2004 Description Page 31 of 770 Documentation The following documents are available on the IP Line 4.0 CD-ROM and on the Nortel Networks web site: • IP Line: Description, Installation, and Operation (553-3001-365) • IP Phones: Description, Installation, and Operation (553-3001-368) • IP Phone 2001 User Guide • IP Phone 2001 Quick Reference Card • IP Phone 2002 User Guide • IP Phone 2002 Quick Reference Card • IP Phone 2004 User Guide • IP Phone 2004 Quick Reference Card • IP Softphone 2050 and Mobile Voice Client 2050 User Guide Voice Gateway Media Cards Voice Gateway Media Card is a term used to encompass the Media Card 32-port line card, Media Card 8-port line card, and ITG-P 24-port line card. These cards plug into an Intelligent Peripheral Equipment (IPE) shelf in the Meridian 1 and CS 1000M systems, and into a Media Gateway 1000S and Media Gateway 1000S Expander in the CS 1000S system. The ITG-P 24-port line card occupies two slots while the Media Card line card occupies only one slot. The Media Card comes in two versions: 8-port and 32-port. The Media Card has the following features: • 32-port card’s packet processing power is greater than that of the ITG-P 24-port line card • increases the channel density from 24 to 32 ports (for 32-port version) IP Line Description, Installation, and Operation Page 32 of 770 Description • reduces the slot count from a dual IPE slot to a single IPE slot • supports up to 128 IP Phones for the 32-port version, while 32 IP Phones are supported on the 8-port version (if a Signaling Server is not present in the network configuration). The 8-port version is typically intended for the Media Gateway 1000B used with the Branch Office feature in branch office locations. Table 7 provides a comparison of the ITG-P 24-port line card and Media Card 32-port and 8-port line cards. Table 7 Comparison of ITG-P 24-port and Media Card 32-port and 8-port line cards (Part 1 of 2) Item ITG-P 24-port line card Media Card 32-port line card Media Card 8-port line card Total DSP Channels 24 32 8 Number of slots the card occupies 2 1 1 Operating System VxWorks 5.3 VxWorks 5.4 VxWorks 5.4 Processor Pentium IXP1200 IXP1200 DSP 8 x TI5409 4 x TI5421 1 x TI5421 Telogy version 7.01 8.1 High Density version (8 ports for each DSP) 8.1 High Density version (8 ports for each DSP) Number of IP Phones that can register on each Voice Gateway Media Card 96 (in a Meridian 1 – see note) 128 (in a Meridian 1 – see note) 32 (in a Meridian 1 – see note) Image file name prefixes shown by swVersionShow command IPL P IPL SA IPL SA 553-3001-365 Standard 3.00 September 2004 Description Page 33 of 770 Table 7 Comparison of ITG-P 24-port and Media Card 32-port and 8-port line cards (Part 2 of 2) ITG-P 24-port line card Media Card 32-port line card Media Card 8-port line card /C: drive On board Flash 2 x 4Mb Plug-in CompactFlash 16Mb Plug-in CompactFlash 16Mb Upgrade Two images files One image file (no backup) One image file (no backup) Item Note: If a Voice Gateway Media Card is used in a CS 1000 system, then the IP Phones register to the Signaling Server instead of the Voice Gateway Media Card, and are not subject to these restrictions. A Signaling Server can register a maximum of 5000 IP Phones. Voice Gateway Media Cards have an ELAN network interface (10BaseT) and a TLAN network interface (10/100BaseT) on the I/O panel. Note: The ELAN (Embedded LAN) subnet isolates critical telephony signaling between the Call Server and the other components. The ELAN subnet is also known as the Management LAN subnet. The TLAN (Telephony LAN) subnet carries telephony/voice/signaling traffic. The TLAN subnet, also known as the Voice LAN subnet, connects to the customer network and the PSTN. There is an RS-232 Maintenance Port connection on the faceplates of both the ITG-P 24-port line card and the Media Card line card. The ITG-P 24-port line card has an alternative connection to the same serial port on the I/O backplane. CAUTION Do not connect maintenance terminals to both the faceplate and the I/O panel serial maintenance port connections at the same time. IP Line Description, Installation, and Operation Page 34 of 770 Description Capacity The Virtual TN (VTN) feature allows each Voice Gateway Media Card to support more IP Phones than there are physical bearer channels. There are 24 bearer channels on each ITG-P card and 8 or 32 channels on each Media Card. Both cards support a 4:1 concentration of registered IP Phones (IP Phones type 2002 and 2004, IP Softphone 2050, and Mobile Voice Client (MVC) 2050) to gateway channels. The ITG-P supports 96 registered IP Phones. The Media Card supports 32 registered IIP Phones (when the card has 8 channels) or 128 registered IP Phones (when the card has 32 channels). The IP Phones require the services of the bearer channels only when they are busy on a call that requires a TDM circuit such as an IP Phone-to-digital telephone/trunk/voice mail/conference. When an IP Phone is idle or there is an IP-to-IP call, no gateway channel is required. When the total number of IP Phones that are registered or are attempting to register reaches the limit (96 on the ITG-P, 32 or 128 on the Media Card), the Voice Gateway Media Card recognizes this and no more IP Phones are assigned to the card. Each Voice Gateway Media Card is restricted to a total of 1200 call attempts per hour distributed across all the IP Phones associated with the card. 553-3001-365 Standard 3.00 September 2004 Description Page 35 of 770 Media Card controls, indicators, and connectors Figure 2 shows the Media Card 32-port and 8-port card faceplate. Figure 2 Media Card faceplate Reset Button Reset MC Enable LED PC Card Slot (Drive /A:) A: MAC Address label (TLAN and ELAN addresses) E T 100 Ethernet Activity LEDs 10 A HEX Display NTVQ01AA RS-232 Maintenance Port J2 Lock Latches 553-SMC0001 IP Line Description, Installation, and Operation Page 36 of 770 Description Faceplate components The components on the faceplate of the Media Card 32-port and 8-port card are described in the following sections. Reset button Use the Reset button on the faceplate to manually reset the Media Card. This enables the card to be reset without cycling power to it. The Reset button is used to reboot the card after a software upgrade or to clear a fault condition. Enable LED The faceplate red LED indicates the following: • the enabled/disabled status of the card • the self-testing result during power up or card insertion into an operational system PC Card slot This slot accepts the Type I or Type II standard PC Flash Cards, including ATA Flash cards (3 Mb to 170 Mb). The slot is labeled /A:. Nortel Networks supplies PC Card adaptors that enable CompactFlash cards to be used in the slot. WARNING Do not format the PC Card using a Windows application. As well, only format the PC Card using the type of card on which it will be running. For example, a PC Card formatted using a Small System Controller (SSC) card is only readable by the SSC card. It is not readable by the ITG-P 24-port card or the Media Card. A PC Card formatted using a Voice Gateway Media Card (ITG-P 24-port card or Media Card) is only readable by another Voice Gateway Media Card. It is not readable by the SSC card. 553-3001-365 Standard 3.00 September 2004 Description Page 37 of 770 MAC address label The MAC address label on the card’s faceplate is labeled ETHERNET ADDRESS. It shows the TLAN and ELAN network interface MAC addresses. The Management /ELAN network interface MAC address for each card is assigned during manufacturing and is unchangeable. The MAC address label on the Media Card is similar to the following example: ETHERNET ADDRESS TLAN 00:60:38:BD:C9:9C ELAN 00:60:38:BD:C9:9D Ethernet activity LEDs The faceplate contains six Ethernet activity LEDs, three for the ELAN network interface and three for the TLAN network interface. The LEDs indicate the following links on the ELAN network interface and TLAN network interface (in order from the top): 1 100 (100BaseT) 2 10 (10BaseT) 3 A (Activity) Maintenance hex display This is a four-digit LED-based hexadecimal display that provides the role of the card. It also provides an indication of fault conditions and the progress of PC Card-based software upgrades or backups. RS-232 Maintenance Port The Media Card faceplate provides a female 8-pin mini-DIN serial maintenance port connection. The faceplate on the card is labeled J2. IP Line Description, Installation, and Operation Page 38 of 770 Description ITG-P 24-port card controls, indicators, and connectors Figure 3 shows the ITG-P 24-port card faceplate components. Figure 3 ITG-P 24-port card faceplate NWK Not used ITG-P LED (card status) Reset Button ITG-P Reset NWK Status MAC Address label (motherboard and daughterboard addresses) TLAN Ethernet Activity LED's PC Card Slot (Drive /A:) A: Four-character LED-based Matrix Maintenance Display NTVQ55AA RS-232 Maintenance Port Maint Port Inboard: - Type III PCMCIA slot (ATA Drive /B:) - Onboard Flash Drive /C: 553-9150 553-3001-365 Standard 3.00 September 2004 Description Page 39 of 770 Faceplate components The components on the faceplate of the ITG-P 24-port line card are described in the following sections. NWK The faceplate connector labeled NWK is a 9-pin, sub-miniature D-type connector. The connector is not used for the IP Line 4.0 application. WARNING The NWK connector looks like a 9-pin serial connector. Do not connect a serial cable or any other cable to it. If a cable is connected to the NWK connector, the TLAN is disabled. ITG-P LED (card status) The red status faceplate LED indicates the enabled/disabled status of the 24 card ports. The LED is on (red) during the power-up or reset sequence. The LED remains lit until the card is enabled by the system. If the LED remains on, the self-test failed, the card is disabled, or the card rebooted. Reset button Press the Reset button to reset the card without having to cycle power to the card. This button is normally used after a software upgrade to the card or to clear a fault condition. IP Line Description, Installation, and Operation Page 40 of 770 Description MAC address label The MAC address label on the card’s faceplate shows the motherboard and daughterboard addresses. The ELAN network interface address corresponds to the Management MAC address. The Management MAC address for each card is assigned during manufacturing and is unchangeable. The ELAN network interface MAC address is the MOTHERBOARD Ethernet address found on the label. The MAC address label on the ITG-P 24-port line card is similar to the following example: ETHERNET ADDRESS MOTHERBOARD 00:60:38:8c:03:d5 DAUGHTERBOARD 00:60:38:01:b3:cb TLAN network interface activity LEDs (labeled NWK Status LEDs) The two NWK Status LEDs display TLAN network interface activity. • Green – the LED is on if the carrier (link pulse) is received from the TLAN network interface switch. • Yellow – the LED flashes when there is data activity on the TLAN network interface. During heavy traffic, the yellow LED can stay continuously lit. Note: There are no Ethernet status LEDs for the ELAN network interface. 553-3001-365 Standard 3.00 September 2004 Description Page 41 of 770 PC Card slots The ITG-P 24-port line card has one faceplate PC Card slot (designated Drive /A:). It is used for optional maintenance. The ITG-P 24-port line card also has one unused inboard slot (designated Drive /B:). The PC Card slots support high-capacity PC flash memory cards. WARNING Do not format the PC Card using a Windows application. As well, only format the PC Card using the type of card on which it will be running. For example, a PC Card formatted using a Small System Controller (SSC) card is only readable by the SSC card. It is not readable by the ITG-P 24-port card or the Media Card. A PC Card formatted using a Voice Gateway Media Card (ITG-P 24-port card or Media Card) is only readable by another Voice Gateway Media Card. It is not readable by the SSC card. Matrix maintenance display A four-character, LED-based dot matrix display shows the maintenance status fault codes and other card state information. For a list of the fault codes, see Table 64: “ITG-P 24-port line card faceplate maintenance display codes” on page 569 and Table 65: “Media Card faceplate maintenance display codes” on page 571. RS-232 maintenance port The ITG-P 24-port line card faceplate provides a female 8-pin mini-DIN serial maintenance port connection, labeled Maint Port. An alternative connection to the faceplate serial maintenance port exists on the NTMF94EA I/O panel breakout cable. CAUTION Do not connect maintenance terminals or modems to the faceplate and I/O panel DB-9 male serial maintenance port at the same time. IP Line Description, Installation, and Operation Page 42 of 770 Description Backplane interfaces The backplane provides connections to the following: • ELAN network interface • TLAN network interface • alternate connection to the DS-30X serial maintenance port • Card LAN interface connectors DS-30X voice/signaling The DS-30X serial maintenance port carries Pulse Code Modulation (PCM) voice and proprietary signaling on the IPE backplane between the ITG-P 24-port line card and the Intelligent Peripheral Equipment Controller (XPEC). Card LAN Card LAN carries card polling and initialization messages on the IPE backplane between the ITG-P 24-port line card and the Intelligent Peripheral Equipment Controller (XPEC). Assembly description The ITG-P 24-port line card assembly is a two-slot motherboard and daughterboard combination. A PCI interconnect board connects the motherboard and the DSP daughterboard. See Figure 4 on page 43. 553-3001-365 Standard 3.00 September 2004 Description Page 43 of 770 Figure 4 ITG-P 24-port line card physical assembly Functional description of the Voice Gateway Media Cards The Media Card and ITG-P 24-port line cards can perform two separate functions, depending on the system in which the card is located: 1 The card acts as a gateway between the circuit-switched voice network and the IP network. 2 The card acts as a Line Terminal Proxy Server (LTPS) or “virtual line card” for the IP Phones, based on whether a Signaling Server is used in the configuration or not. IP Line Description, Installation, and Operation Page 44 of 770 Description Gateway functional description The Gateway performs the following functions: • registers with the system using the TN Registration messages • accepts commands from the system to connect/disconnect audio channel • uses Realtime Transport Protocol/Realtime Conferencing Protocol (RTP/RTCP) protocol to transport audio between the gateway and the IP Phone • encodes/decodes audio from PCM to and from the IP Phone’s format • provides echo cancellation for the speaker on IP Phones for echoes originating in the circuit-switched voice network (not applicable to the IP Softphone 2050 or MVC 2050 as they have no handsfree capability) Gateway functionality on the Meridian 1 Since there is no Signaling Server, each Voice Gateway Media Card functions as both the LTPS and Voice Gateway. The Gateway portion of the card connects to the Meridian 1 through the DS-30X backplane. The Gateway portion also receives call speech-path setup and codec selection commands through the ELAN network interface. The IP Phone connects to both the Gateway and the LTPS functions through the TLAN network interface. Gateway functionality on the CS 1000 systems A Signaling Server is always present in the CS 1000 systems. The LTPS executes on the Signaling Server and the Voice Gateway executes on the Voice Gateway Media Cards. The Voice Gateway Media Cards only provide the voice gateway access. Active Master The LTPS maintains a count of the number of IP Phones registered to the card. Each IP Telephony node has one active Master. The active Master broadcasts to all Voice Gateway Media Cards and requests a response if it has room for another IP Phone. 553-3001-365 Standard 3.00 September 2004 Description Page 45 of 770 The Election function uses a selection process to determine the node’s Master. The Census function determines the Voice Gateway Media Cards within an IP Telephony node. IP Phone registration IP Phone registration on a Meridian 1 system Table 8 describes the maximum number of IP Phones that can be registered to each type of line card in a Meridian 1 system. Table 8 Maximum number of IP Phones that can register to a Voice Gateway Media Card in a Meridian 1 Card type Maximum number Media Card 32-port 128 Media Card 8-port 32 ITG-P 24-port 96 For more information, refer to “System capacities” in Communication Server 1000M and Meridian 1: Large System Planning and Engineering (553-3021-120), Communication Server 1000M and Meridian 1: Small System Planning and Engineering (553-3011-120), and Communication Server 1000S: Planning and Engineering (553-3031-120). IP Phone registration on a CS 1000 system On a CS 1000 system, the IP Phones register with the LTPS on the Signaling Server. If a secondary Signaling Server exists, the IP Phone registrations are split between the primary and secondary Signaling Servers to aid in load balancing. In that case, the IP Phone registrations alternate between the primary and secondary Signaling Servers. IP Line Description, Installation, and Operation Page 46 of 770 Description If the primary Signaling Server fails, the secondary Signaling Server takes over (if it exists) and the IP Phones that were registered with the failed Signaling Server re-register with the LTPS on the secondary Signaling Server. If there is no secondary Signaling Server or the secondary Signaling Server fails, the IP Phones register with the LTPS on the Voice Gateway Media Cards. IMPORTANT! Each Signaling Server supports the registration of up to 5000 IP Phones. For more information on Signaling Server failure and redundancy, see Communication Server 1000S: Planning and Engineering (553-3031-120), Communication Server 1000E: Planning and Engineering (553-3041-120), and Signaling Server: Installation and Configuration (553-3001-212). Virtual Terminal Manager The Virtual Terminal Manager (VTM) performs the following functions: • arbitrates application access to the IP Phones • manages all the IP Phones between the applications and the UNIStim messaging to the IP Phone • maintains context-sensitive states of the IP Phone (for example, display or lamp state) • isolates IP Phone-specific information from the applications (for example, the number of display lines, number of characters for each display line, tone frequency, and cadence parameters) Interactions with IP Phones The following information describes the process by which an IP Phone registers and unregisters with a Meridian 1 or CS 1000 system. 553-3001-365 Standard 3.00 September 2004 Description Page 47 of 770 Registration Table 9 describes the registration process. Table 9 Registration process Step Description 1 The IP Phone receives the IP address of the Connect Server (co-located with the LTPS) through either DHCP or manual configuration. 2 The IP Phone contacts the Connect Server. 3 The Connect Server instructs the IP Phone to display a message on its display screen requesting the customer’s IP Telephony node number and TN. 4 The node number and TN are entered. The Connect Server redirects the IP Phone to the Node Master. 5 The IP Phone contacts the Node Master. The Node Master redirects the IP Phone to the LTPS. 6 The IP Phone contacts the LTPS. 7 If the IP Phone is valid, the LTPS registers it with the system. Unregistration Table 10 describes the unregistration process. Table 10 Unregistration process Step Description 1 If the LTPS detects a loss of connection with one of its registered IP Phones, it logs the event. 2 The LTPS then sends an unregister message to the system for that IP Phone. IP Line Description, Installation, and Operation Page 48 of 770 Description Signaling and messaging The IP Line 4.0 application sends Scan and Signaling Distribution (SSD) messages to the Call Server through the system’s ELAN subnet. When tone service is provided, the service is signaled to the LTPS using new SSD messages sent through the ELAN subnet. Signaling protocols The signaling protocol between the IP Phone and the IP Telephony node is the Unified Networks IP Stimulus Protocol (UNIStim). The Reliable User Datagram Protocol (RUDP) is the transport protocol. RUDP RUDP is used for: • signaling between the Call Server and the Voice Gateway Media Cards • signaling between the IP Telephony node and the IP Phones Description Signaling messages between the Voice Gateway Media Card and IP Phones use RUDP. Each RUDP connection is distinguished by its IP address and port number. RUDP is another layer on top of UDP. RUDP is proprietary to Nortel Networks. The features of RUDP are as follows: 553-3001-365 • provides reliable communication system over a network • packages are resent if an acknowledgement message (ACK) is not received following a time-out • messages arrive in the correct sequence • duplicate messages are ignored • loss of contact detection Standard 3.00 September 2004 Description Page 49 of 770 When a data sequence is packetized and sent from source A to receiver B, RUDP adds a number to each packet header to indicate its order in the sequence. • If the packet is successfully transmitted to B, B sends back an ACK to A, acknowledging that the packet has been received. • If A receives no message within a configured time, it retransmits the packet. • If B receives a packet without having first received its predecessor, it discards the packet and all subsequent packets, and a NAK (no acknowledge) message which includes the number of the missed packet is sent to A. A retransmits the missed packet and continues. UNIStim The Unified Network IP Stimulus protocol (UNIStim) is the single point of contact between the various server components and the IP Phone. UNIStim is the stimulus-based protocol used for communication between an IP Phone and an LTPS on the Voice Gateway Media Card or Signaling Server. ELAN TCP transport Although TCP is used for the signaling protocol between the Call Server and the Voice Gateway Media Card, RUDP remains for the Keep Alive mechanism for the link. This means RUDP messages are exchanged to maintain the link status between the Call Server and the Voice Gateway Media Card. There is no change to UNIStim signaling. IP Phones continue to use the RUDP transport protocol to communicate with the Voice Gateway Media Card. The TCP protocol enables messages to be bundled. Unlike the RUDP transport that creates a separate message for every signaling message (such as display updates or key messages), the TCP transport bundles a number of messages and sends them as one packet. IP Line Description, Installation, and Operation Page 50 of 770 Description Handshaking is added to the Call Server and IP Line software so that the TCP functionality is automatically enabled. A software version check is performed by the IP Line application each time before it attempts to establish a TCP link with the CS 1000 and Meridian 1 CPUs. TCP transports messages, while RUDP establishes and maintains the link. If the version does not satisfy the minimum supported version (CS 1000 Release 4.0), a RUDP link is used instead to maintain the link and all signaling. Virtual superloops, virtual TNs, and physical TNs Virtual TNs (VTNs) enable configuration of service data for an IP Phone, such as key layout and class of service, without requiring the IP Phone to be dedicated (hard-wired) to a given TN on the Voice Gateway Media Card. Calls are made between an IP Phone and circuit-switched telephone/trunks using the full CS 1000 and Meridian 1 feature set. Digital Signal Processor (DSP) channels are allocated dynamically for this type of call to perform the encoding/decoding required to connect the IP Phone to the circuit-switched network. To create an IP Phone using VTNs, create a virtual superloop in LD 97. 553-3001-365 • Up to 1024 VTNs can be configured on a single virtual superloop for Large Systems, CS 1000M Cabinet and CS 1000M Chassis systems, and CS 1000E systems • Up to 128 VTNs can be configured on a single virtual superloop for Meridian 1 Option 11C Cabinet and Meridian 1 Option 11C Chassis systems, leading to support for a maximum of 640 VTNs for each of these systems. Standard 3.00 September 2004 Description • Page 51 of 770 Up to 1024 VTNs can be configured on a single virtual superloop for CS 1000S systems. Table 11 describes the virtual superloop and virtual card mapping on a CS 1000S system. Each superloop has two ranges of cards. Table 11 Virtual superloop/virtual card mapping for CS 1000S SUPL Card 96 61-64 81-84 100 65-68 85-88 104 69-72 89-92 108 73-76 93-96 112 77-80 97-99 Each ITG-P 24-port line card provides 24 physical TNs and each Media Card 32-port line card provides 32 physical TNs. The physical TNs are the gateway channels (DSP ports). Configure the physical TNs (IPTN) in LD 14. They appear as TIE trunks without a Route Data Block (RDB). Virtual TNs Virtual TNs enable service data to be configured for an IP Phone, such as key layout and class of service, without requiring a physical IP Phone to be directly connected to the Call Server. The concentration of IP Phones is made possible by dynamically allocating a port (also referred to as a physical TN) of the Voice Gateway Media Card for a circuit-switched- to-IP Phone call. All system speech path management is done with physical TNs instead of virtual TNs. The channels (ports) on the Voice Gateway Media Cards are pooled resources. The IP Phones (virtual TNs) are defined on virtual superloops. IP Line Description, Installation, and Operation Page 52 of 770 Description A virtual superloop is a hybrid of real and phantom superloops. Like phantom superloops, no hardware (for example, XPEC or line card) is used to define and enable units on a virtual superloop. As with real superloops, virtual superloops use the time slot map to handle IP Phone (virtual TNs)- to-IP Phone calls. Licenses CS 1000 Release 4.0 introduces the Basic IP User License, a new License for the IP Phone 2001. The existing IP User License is used for the IP Phone 2002, IP Phone 2004, IP Softphone 2050 and the Mobile Voice Client (MVC) 2050. Note: If insufficient Basic IP User Licenses are available for the IP Phone 2001, then the IP User License can also be used for configuration of the IP Phone 2001. If there are no Basic IP User Licenses available for IP Phone 2001 configuration and IP User Licenses are used, then an error message is generated. “SCH1976: Basic IP User License counter has reached its maximum value. IP User License was used to configure basic IP Phone(s) type 2001. Action: (Recommended) Purchase additional Basic IP User Licenses for IP Phones type 2001, instead of using higher-priced IP User Licenses.” Each time an IP Phone is configured, the system TN ISM counter is decremented. Customers must purchase one License for each IP Phone installed on CS 1000 and Meridian 1 systems. A new License uses the existing keycode to enable the IP Phone in the system software. The default is zero. To expand the License limits for the IP Phones, order and install a new Meridian 1 or CS 1000 keycode. Refer to the Incremental Software Management feature module in the Features and Services (553-3001-306) NTP. 553-3001-365 Standard 3.00 September 2004 Description Page 53 of 770 Note: Individual Licenses are not supported on Functional Pricing. With Functional Pricing, Licenses are provisioned in blocks of eight. License limits The total number of TNs configured with Basic IP User Licenses must not exceed 32767. The total number of TNs configured with IP User Licenses must not exceed 32767. The total number of IP phones configured within the system must not exceed the allowed system capacity limit controlled by customer keycodes). Zones To optimize IP Line traffic bandwidth use between different locations, the IP Line network is divided into “zones”, representing different topographical areas of the network. All IP Phones and IP Line ports are assigned a zone number indicating the zone to which they belong. When a call is made, the codecs that are used vary, depending on which zone(s) the caller and receiver are in. By default, when a zone is created in LD 117: • codecs are selected to optimize voice quality (BQ - Best Quality) for connections between units in the same zone. • codecs are selected to optimize voice quality (BQ - Best Quality) for connections between units in different zones. Each zone can be configured to: • optimize either voice quality (BQ) or bandwidth usage (BB - Best Bandwidth) for calls between users in that zone • optimize either voice quality or bandwidth usage within a zone and all traffic going out of a zone For more information about zones, refer to the following: • Shared and Private zones (see “Private Zone configuration” on page 118) IP Line Description, Installation, and Operation Page 54 of 770 Description • Zones and Virtual Trunks (see IP Trunk: Description, Installation, and Operation (553-3001-363)) • Zones and branch office locations (see Branch Office: Installation and Configuration (553-3001-214)) Administration The Voice Gateway Media Card is administered using multiple management interfaces including the following: • the IP Line 4.0 application GUI provided by OTM 2.2 • a Command Line Interface (CLI) • administration and maintenance overlays of Call Servers • a web browser interface provided by Element Manager. Element Manager is used for administering Voice Gateway Media Cards in the systems that use a Signaling Server IP Line 4.0 application in OTM 2.2 For Meridian 1 systems, OTM 2.2 is required for IP Line 4.0. OTM 2.2 is used for tasks such as the following: • creating a node • adding Voice Gateway Media Cards to the node • transmitting loadware to the Voice Gateway Media Cards • upgrading loadware • defining SNMP alarms • selecting codecs Element Manager The Element Manager web server is required for CS 1000 systems. Element Manager’s web interface enables IP Line 4.0 to be configured and managed from a web browser. 553-3001-365 Standard 3.00 September 2004 Description Page 55 of 770 The Element Manager web interface is divided into two categories: 1 Element Manager – used to manage the Call Server and IP Telephony nodes (IP Line). 2 Gatekeeper Element Manager – used to administer network numbering plan for the Network Connect Server that is used by Network-Wide Virtual Office and Media Gateway 1000B. Description Element Manager is a simple and user-friendly web-based interface that supports a broad range of system management tasks, including: • configuration and maintenance of IP Peer and IP telephony features • configuration and maintenance of traditional routes and trunks • configuration and maintenance of numbering plans • configuration of Call Server data blocks (such as configuration data, customer data, Common Equipment data, D-channels) • maintenance commands, system status inquiries, backup and restore functions • software download, patch download, patch activation Element Manager has many features to help administrators manage systems with greater efficiency. Examples are as follows: • Web pages provide a single point-of-access to parameters that were traditionally available through multiple overlays. • Parameters are presented in logical groups to increase ease-of-use and speed-of-access. • The “hide or show information” option enables administrators to see information that relates directly to the task at hand. • Full-text descriptions of parameters and acronyms help administrators reduce configuration errors. • Configuration screens offer pre-selected defaults, drop-down lists, checkboxes, and range values to simplify response selection. IP Line Description, Installation, and Operation Page 56 of 770 Description The Element Manager web server resides on the Signaling Server and can be accessed directly through a web browser or Optivity Telephony Manager (OTM). The OTM navigator includes integrated links to each network system and their respective instances of Element Manager. Command Line Interface Definition The Command Line Interface (CLI) provides a text-based interface to perform specific Signaling Server and Voice Gateway Media Card installation, configuration, administration, and maintenance functions. Access Establish a CLI session by connecting a TTY or PC to the card serial port or Telnet through the ELAN or TLAN network interface IP address. IMPORTANT! In the case of an IP Telephony node with no Signaling Server, the CLI must be used to configure the Leader card of the IP Telephony node. This enables OTM 2.2 and Element Manager to communicate with the Leader card and the node. For more information about the CLI commands, see “IP Line CLI commands” on page 585. Overlays For information on the overlays, refer to Software Input/Output: Administration (553-3001-311). 553-3001-365 Standard 3.00 September 2004 144 Page 57 of 770 Features Contents This section contains information on the following topics: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 NAT Traversal feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Echo Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NAT Mapping Keep Alive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mute and Hold considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NAT and VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NAT Traversal and Proactive Voice Quality Management . . . . . . . Configuring NAT Traversal in Element Manager . . . . . . . . . . . . . . Configuring NAT Traversal in LD 117 . . . . . . . . . . . . . . . . . . . . . . CLI commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 62 63 65 66 68 70 70 70 73 Firmware download using UNIStim FTP . . . . . . . . . . . . . . . . . . . . . . . CLI commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 87 Personal Directory, Callers List, and Redial List . . . . . . . . . . . . . . . . . 93 IP Call Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 95 pbxLink connection failure detection . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying pbxLink information . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 97 LD 117 STAT SERV enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . pbxLink information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 98 98 IP Phone support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 IP Line Description, Installation, and Operation Page 58 of 770 553-3001-365 Features IP Phone Key Expansion Module . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Corporate Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Element Manager support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BOOTP and CONFIG.INI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 106 Call Statistics collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Counting IP Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IP Phone Zone Traffic Report 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 107 112 User-defined feature key labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Private Zone configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shared Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Private Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LD 117 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 119 119 119 Run-time configuration changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Network wide Virtual Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Branch Office and Media Gateway 1000B. . . . . . . . . . . . . . . . . . . . . . 126 802.1Q support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration of 802.1Q on IP Phones . . . . . . . . . . . . . . . . . . . . . . Control of the IP Phone’s 802.1Q . . . . . . . . . . . . . . . . . . . . . . . . . . 802.1Q and the Voice Gateway Media Cards . . . . . . . . . . . . . . . . . 127 127 129 130 Data Path Capture tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 IP Phone firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Minimum firmware version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Firmware download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Meridian 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CS 1000 systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 130 130 132 133 Graceful Disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operation of the LTPS DISI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Feature operation of the Voice Gateway DISI. . . . . . . . . . . . . . . . . 135 136 137 Hardware watchdog timer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Watchdog Timer and Voice Gateway Media Card firmware . . . . . 138 139 Codecs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Set type checking and blocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Enhanced Redundancy for IP Line nodes. . . . . . . . . . . . . . . . . . . . . . . 142 Standard 3.00 September 2004 Features Page 59 of 770 Introduction Table 12 outlines the features available for CS 1000 and Meridian 1 systems with CS 1000 Release 4.0 software. Table 12 IP Line 4.0 feature support (Part 1 of 3) Feature Meridian 1 CS 1000M CS 1000S Support for Media Card Yes Yes Yes Support for Element Manager No Yes Yes Support for Signaling Server Yes Yes Yes Support of the following IP Phones: Yes Yes Yes Network Address Translation (NAT) Traversal * No Yes Yes Personal Directory, Callers List, and Redial List with password protection* No Yes Yes • IP Phone 2001 • IP Phone 2002 • IP Phone 2004 Support of the following software clients: • IP Softphone 2050 • Mobile Voice Client (MVC) 2050 Support of the IP Phone Key Expansion Module (KEM) * a. Node level patching is not provided by OTM 2.2. The patching CLI command of the Media Card 32-port line card, Media Card 8-port line card, and ITG-Pentium 24-port line card can be used. * = introduced in IP Line 4.0 IP Line Description, Installation, and Operation Page 60 of 770 Features Table 12 IP Line 4.0 feature support (Part 2 of 3) Feature Meridian 1 CS 1000M CS 1000S UNIStim File Transfer Protocol (UFTP) for IP Phone firmware downloads * Yes Yes Yes IP Call Recording * Yes Yes Yes pbxLink connection failure detection Yes Yes Yes LD 117 STAT SERV enhancement * Yes Yes Yes Dynamic Loss Plan Yes Yes Yes Network-wide Virtual Office Yes Yes Yes Patching Partial Partial Yes 802.1Q Yes Yes Yes Corporate Directory Yes Yes Yes Data Path Capture tool Yes Yes Yes Call statistics enhancements Yes Yes Yes User-defined Feature Key Labels Yes Yes Yes Private Zone Yes Yes Yes Graceful TPS Disable Yes Yes Yes Run-time download Yes Yes Yes Codec selection, configuration, and registration enhancements Yes Yes Yes a. Node level patching is not provided by OTM 2.2. The patching CLI command of the Media Card 32-port line card, Media Card 8-port line card, and ITG-Pentium 24-port line card can be used. * = introduced in IP Line 4.0 553-3001-365 Standard 3.00 September 2004 Features Page 61 of 770 Table 12 IP Line 4.0 feature support (Part 3 of 3) Feature Meridian 1 CS 1000M CS 1000S Watchdog Timer Yes Yes Yes Password Guessing Protection Yes Yes Yes Ringer and buzzer volume adjustment Yes Yes Yes Set-based installation Yes (Small Systems only) Yes (Small Systems only) Yes Maintenance Audit enhancement Yes Yes Yes Multi-language support Yes Yes Yes Yes yes Yes Enhanced Redundancy for IP Line nodes IP Softphone 2050 user-selectable codec (not applicable to MVC 2050 as it only supports G.711 codec) a. Node level patching is not provided by OTM 2.2. The patching CLI command of the Media Card 32-port line card, Media Card 8-port line card, and ITG-Pentium 24-port line card can be used. * = introduced in IP Line 4.0 NAT Traversal feature Network Address Translation (NAT) provides the following benefits: • the ability to network multiple sites with overlapping private address ranges • added security for servers on a private network • conservation of public IP address allocation A NAT device (router) exists between a private network and a public network. The NAT device maps private addresses to public addresses. IP Line Description, Installation, and Operation Page 62 of 770 Features With the CS 1000 Release 4.0 NAT Traversal feature, several IP Phones are now supported behind a single Cone NAT router with, or without, Virtual Private Network (VPN) capabilities. This support enables large-scale deployment of Voice over Internet Protocol (VoIP) in teleworking and Small Office/Home Office (SOHO) environments. Supported Cone NAT routers include: • Full Cone • Restricted Cone • Port Restricted Cone Note: A Cone NAT router with more than one IP Phone connected to it must support hairpinning. Hairpinning occurs when an IP Phone behind a NAT router can send packets to the Public IP address and port of another IP Phone connected to the same NAT router. IMPORTANT! Symmetric NAT routers are not supported. If the IP Phone is behind a Symmetric NAT, IP Phone registration is unsuccessful and the IP Phone displays a “NAT Error! ITG3053” message. Echo Servers NAT Traversal is a function of the CS 1000 Release 4.0 software, and not a function of the NAT router. NAT Traversal uses two Echo Servers residing on the Signaling Server. Echo Server 1 detects the presence of a NAT router, while Echo Server 2 detects the type of NAT router. Both Echo Server 1 and Echo Server 2 are required for the NAT Traversal feature to function properly. If a compatible NAT router is detected, successful IP Phone registration occurs and the software invokes the NAT Mapping Keep Alive function to prevent loss of the IP connection. If a non-compatible NAT is detected, an error is displayed on the IP Phone’s display and the IP Phone is not allowed to register. 553-3001-365 Standard 3.00 September 2004 Features Page 63 of 770 Mapping When an IP Phone is used in a private network behind a NAT device, the NAT router strips the IP Phone’s private IP address and private port number and assigns it a public IP address and public port number. To support multiple IP Phones behind one NAT device, it is necessary for NAT to map between public and private IP addresses, and ports for each IP Phone behind it. There is a mapping for both a signaling port and a media (voice) port. Placing an IP Phone behind Multiple NAT devices is an unsupported configuration. If it is necessary to have a configuration with multiple NATs between the IP Phone and the Voice Gateway Media Card, all NATs on the path must follow the rules described in the following sections for signaling and media streams. Mapping is configured and implemented using the NAT device. The IP Line application does not implement any of the mappings. NAT and signaling NAT hides the true identity of the IP Phone from the LTPS. The LTPS is only aware of any IP Phone based on the public IP address and port of the signaling messages. A signaling message originates from the IP Phone on the private side from port 5000. That signaling message is then mapped from the private side to a public IP and port and that is the IP address seen by the LTPS. Signaling messages between the Voice Gateway Media Card and IP Phones are carried by RUDP. Each RUDP connection is distinguished by its IP address and port number. IP Line Description, Installation, and Operation Page 64 of 770 Features The NAT device performs private-to-public mapping for the signaling port for each IP Phone behind it to support multiple IP Phones. The TPS uses fixed port numbers for signaling. The NAT device must perform consistent private-to-public mapping for these port numbers. Table 13 lists the UDP port number used. Table 13 Signaling UDP Ports UDP Port Device Use 5000 IP Phone incoming signaling messages to the IP Phones, including UFTP messaging 5100 LTPS incoming call processing messages to the LTPS 5105 UFTP incoming UFTP packets to the UFTP server 4100 LTPS incoming registration message to Connect Server 7300 LTPS incoming registration messages to node Master Port numbers on the Voice Gateway Media Card use a fixed numbering scheme where the starting number for the port range is configurable. The first port on the card uses the configured starting port number; the rest of the port numbers follow in sequence. Each port has two sequential numbers: one for RTP and one for RTCP. 553-3001-365 Standard 3.00 September 2004 Features Page 65 of 770 Do not change this port at any time. Map this port to port 5200 on the IP Phones. Table 14 IP Line UDP Ports UDP Port Device Use 5200-5262 Media Card RTP packets (configurable starting port number – IP Phone’s port matches it) 5201-5263 Media Card RTCP packets into Media Card (port number is RTP port number + 1) 5200-5246 ITG-P 24-port line card RTP packets (configurable starting port number IP Phone’s port matches it) 5201-5247 ITG-P 24-port line card RTCP packets into Media Card (port number is RTP port number + 1) 5200 IP Phone RTP packets into IP Phone (port matches first RTP port of the Voice Gateway Media Card) 5201 IP Phone RTCP packets into IP Phone (port matches first RTCP port of the Voice Gateway Media Card) NAT Mapping Keep Alive The normal operation of the LTPS and the IP Phone requires the LTPS to send a periodic Watchdog Reset UNIStim message. This message resets the hardware watchdog timer running on the IP Phone and specifies the period for the time-out. If the LTPS does not send the Watchdog Reset message before the watchdog timer expires, the IP Phone resets and begins a new registration cycle with the LTPS. IP Line Description, Installation, and Operation Page 66 of 770 Features To avoid loss of the IP connection, CS 1000 Release 4.0 introduces NAT Mapping Keep Alive which sends the Watchdog Reset message more frequently. Default values are recommended. However, if it is necessary to increase the frequency of the Reset Watchdog message, increase the NAT Mapping Keep Alive timer value. NAT Traversal can be configured to provision the length of time the audio and signaling port mapping is refreshed. This configuration can be done in Element Manager, on the Call Server in LD 117, or in OTM through a window to the Call Server. By default, all IP Phones behind a NAT device have the signaling and audio path kept alive. The default value is 30 seconds. The value can be decreased to 20 seconds or increased to 600 seconds. Mute and Hold considerations IP Line 4.0 must handle two special situations when interworking with NAT: Mute and Hold. Mute Table 15 describes the Mute process. Table 15 Mute process (Part 1 of 2) Description Problem 1 When a user enables Mute, the LTPS sends a Mute Transmit (Tx) command to the IP Phone. That command forces the IP Phone to generate silence in the transmit direction. 2 If the IP Phone is using an evocator that implements silence suppression, for example G.729AB, the IP Phone sends one silence frame to the far end, and then stops sending any further frames until Mute is cancelled. 3 Data sent from the IP Phone stops. 553-3001-365 Standard 3.00 September 2004 Features Page 67 of 770 Table 15 Mute process (Part 2 of 2) Description 4 The NAT device sees that the IP Phone’s UDP connection is not active in the transmit direction and starts aging the translation. 5 Depending on the length of time the call is muted and the duration of the NAT’s translation aging timeout value, the NAT device might time-out the translation and drop the connection. 6 All packets coming from the far end are dropped by the NAT device. 7 When mute is cancelled, the IP Phone starts transmitting again. 8 NAT considers this to be a new connection and creates a new translation. NAT sends data to the far end using this new translation, resulting in half-duplex voice connection between the IP Phone and the far-end device. 9 Data sent to the far end device gets there but the data coming back is lost. Solution 1 The IP Phone periodically sends an extra non-RTP packet to the far end to keep the NAT translation alive, ensuring that the NAT’s session time-out does not expire. 2 The non-RTP packet is constructed to fail any RTP validation tests so it is not played out by the far-end device (IP Phone or gateway channel. IP Line Description, Installation, and Operation Page 68 of 770 Features Hold The Hold function differs from the Mute function as Hold does not cause problems with the audio stream. Table 16 describes the Hold process. Table 16 Hold process Description 1 When an IP Phone user places a call on Hold, the audio stream in both the Transmit (Tx) and Receive (Rx) directions closes. 2 The NAT device begins aging the translation. When the audio stream is closed and no voice path is present, the IP Phone defaults to sending periodic non-RTP packets to keep the NAT translation alive. Therefore, when a call is put on Hold, the IP Phone defaults to sending these non-RTP packets 3 When the call is retrieved from Hold, a new set of open audio-stream messages are issued by the LTPS and new connections are established reusing the same NAT translation NAT and VLANs Support of Virtual LANs (VLANs) is entirely dependent on the Layer 2 switch to which the IP Phone is immediately connected. Users behind a NAT router may find that the configuration of a VLAN ID is unsupported by their NAT router. Refer to the documentation of the NAT router to determine if a VLAN ID is supported. Users who attempt to use an IP Phone with VLAN enabled on a NAT router that does not support VLANs cannot connect to the CS 1000 system. If DHCP is used, the IP Phone cannot even obtain an IP address. Note: Most NAT routers do not support 802.1Q Tagging. If 802.1Q Tagging is not supported on the NAT device, the checkbox Enable 802.1Q support in Element Manager’s Node Summary Page under the “QoS” Section must be left unchecked. If 802.1Q Tagging is enabled for 553-3001-365 Standard 3.00 September 2004 Features Page 69 of 770 IP Phones behind NAT, the IP Phones are able to send the initial “Resume Connection” message, but then the IP Phones reset and no call path is established. Figure 5 802.1Q Tagging on Node Summary page in Element Manager IP Line Description, Installation, and Operation Page 70 of 770 Features NAT Traversal and Proactive Voice Quality Management IP Line 4.0 introduces Proactive Voice Quality Management. Real-Time Control Protocol (RTCP) signaling provides statistics (for example, latency, packet loss, and jitter) about the Real-Time Transfer Protocol (RTP) stream. For the RTCP signaling to be successful, the PUBLIC RTCP port number must be the RTP port number + 1. For example, if the PUBLIC RTP port is 12000, then the PUBLIC RTCP port must be 12001. The NAT router typically assigns the RTCP port number as RTP port number + 1.However, the NAT router is not guaranteed to properly assign the RTCP port number. When the RTCP port number is not properly assigned, the RTCP message exchange fails and the Proactive Voice Quality Management feature does not receive the required RTCP data. A message is printed to the LTPS console and syslog file and an SNMP trap (ITG3054) is generated. The NAT Traversal feature attempts a “best effort” approach to initiate the NAT router to properly assign the RTPC port number. The “best effort” approach is dependent on the NAT router’s implementation, may vary from NAT router to NAT router, and cannot be guaranteed by the NAT Traversal feature. Configuring NAT Traversal in Element Manager To configure and print the Echo Servers IP addresses/port numbers and NAT Keep Alive time-out setting using Element Manager, select Configuration > IP Telephony > Network Address Translation Parameters. Configuring NAT Traversal in LD 117 Commands have been added to LD 117 to configure and print the Echo Servers IP addresses/port numbers and NAT Keep Alive time-out setting. No configuration is required for the Echo Servers to work. The default IP address of 0.0.0.0 means that Echo Server 1 uses the TLAN network interface IP address. The default IP address of 0.0.0.0 means that Echo Server 2 uses the Node IP address. 553-3001-365 Standard 3.00 September 2004 Features Page 71 of 770 Note: An IP address of 0.0.0.0 means the default local Echo Server will be enabled. IMPORTANT! The NAT Traversal feature is essentially automatic. Changing the IP addresses or ports should only be done in exceptional cases when an Echo Server external to the CS 1000 system is used. If IP addresses are specified, they must be for servers external to the system. The IP addresses cannot be the same. Duplicate IP addresses can only be used if the default of 0.0.0.0 is used. If the IP addresses are the same (and not 0.0.0.0), an error message is generated and the input is not accepted. Table 17 LD 117 commands for NAT (Part 1 of 2) Command Description CHG ES1Change Echo Server 1’s IP address and port number, where: • Default Echo Server 1 IP Address = 0.0.0.0 • Default Echo Server 1 Port number = 10000 Note: Echo Server 1 default IP address uses the TLAN IP address of the LTPS. CHG ES2 Change the Echo Server 2 IP address and port number, where: • Default Echo Server 2 IP Address = 0.0.0.0 • Default Echo Server 2 Port number = 10000 Note: Echo Server 2 default IP address uses the node IP address on the node’s master card. PRT ES1 Print Echo Server 1’s IP address and port number. PRT ES2 Print Echo Server 2’s IP address and port number. PRT ESS Print both Echo Servers IP addresses and port numbers. IP Line Description, Installation, and Operation Page 72 of 770 Features Table 17 LD 117 commands for NAT (Part 2 of 2) Command Description CHG NKT Change NAT Mapping Keep Alive Time-out setting of port mapping for devices behind a NAT router, where: time out setting = 20-(30)-600 seconds PRT NKT Print NAT Mapping Keep Alive Time-out setting of port mapping for devices behind a NAT router. CHG ES1/CHG ES2 If the IP addresses entered for ES1 and ES2 are the same and both are not 0.0.0.0 or for external servers, an error message is generated and the input is not accepted. Any value between 1000 and 60000 can be entered for the port. If the port value is outside of that range, an error message is generated. Just the port (and not the IP addresses) can also be configured. This is accomplished by entering data similar to the following: =>chg es1 0 5400 The value 0 for the IP address is interpreted as: 0.0.0.0. This means the Echo Server runs locally using the configured port value. The port values both default to 10000. If an IP address is configured, it is also necessary to configure the port. An error message is generated if no port is configured but an IP address is configured. If both Echo Servers are not configured then the LTPS on the Signaling Server or the Voice Gateway Media Card uses two local instances of the Echo Server. If both Echo Servers are configured, then the LTPS uses the external Echo Servers. If an external Echo Server fails, that functionality is lost unless the external Echo Server implements a transparent redundancy scheme. The external Echo Server is responsible for its redundancy and reliability. 553-3001-365 Standard 3.00 September 2004 Features Page 73 of 770 PRT commands Figure 6 is an example of the output of the PRT commands when the defaults are used. If other IP addresses or port numbers have been configured, then these appear in place of the 0.0.0.0 or 10000 in the examples in Figure 6. Figure 6 PRT commands output CLI commands The following CLI commands provide information about IP Phones behind a NAT device and the Echo Servers IP Line Description, Installation, and Operation Page 74 of 770 Features isetShow When the isetShow command is used, a NAT column lists the NAT type if an IP Phone is behind a NAT, where: • C – Cone NAT • S – Symmetric NAT • U – Unknown. Behind a NAT of unknown type (response received from only Echo Server 1). • P – Pending. Waiting for response from the IP Phone or the IP Phone never received a response from Echo Server 1. • . . - Blank space. Indicates the IP Phone is not behind any kind of NAT (normal case). For example (partial output from the left side of the screen): IP Address NAT 47.11.215.183 47.11.179.168 47.11.179.167 Type RegType i2001 Regular C i2004 Regular C i2004 Regular isetReset The isetReset command resets an IP Phone based on the entered IP address or TN. The IP address must be the Public IP address for IP Phones behind a NAT. If the entered IP address identifies an IP Phone that is behind a NAT and no other IP Phone are sharing the address, then the IP Phone is reset. However, if the entered IP address identifies multiple IP Phones (multiple IP Phones behind a NAT sharing the same public IP address), then an error message is printed. This message indicates there is more than one IP Phone with the IP address, lists the IP Phones and their TNs, and recommends using the isetReset TN command. For example: oam> isetReset “47.11.217.102” 553-3001-365 Standard 3.00 September 2004 Features Page 75 of 770 WARNING: There are 2 IP Phones that use the public IP address of 47.11.217.102 Please reset the IP Phone using the TN: isetReset “TN”. The number of IP Phones that share the same public IP address is printed. Note: Commands such as isetScpwQuery, isetScpwModify, and isetScpwVerify have the same error handling as isetReset. If an IP address is entered that multiple IP Phones are using, an error message prints. For example, WARNING: There are 2 IP Phones that use the public IP address of 47.11.217.102. isetGet The isetGet command can search on the NAT type. NAT = xxx where x is: • C – the IP Phone is behind a Cone NAT • S – the IP Phone is behind a Symmetric NAT • U – the IP Phone is behind a NAT of unknown type (response only received from Echo Server 1) • P - waiting on a response from the IP Phone or the IP Phone never received a response from Echo Server 1 • . . - Blank space: the IP Phone is not behind any kind of NAT (normal case) • Y - true when an IP Phone’s NAT is C, S or U • N - true when an IP Phone’s NAT is . . (blank), meaning no NAT detected IP Line Description, Installation, and Operation Page 76 of 770 Features For example: IPL> isetGet “NAT == Y” returns the output (partial output from the left side of the screen): IP Address NAT Type RegType State Up Time 47.11.179.168 C i2004 Regular online 0 04:20:34 47.11.179.167 C i2004 Regular online 0 03:48:17 isetNATShow IP Line 4.0 introduces the isetNATShow command. This command outputs information about IP Phones behind a NAT device. The public and private IP address and ports are provided for both signaling and media. In most cases, the private signaling port information is available. If the firmware on the IP Phone is outdated, the private signaling port information is not printed. If the IP Phone is found to be behind a Symmetric NAT device, the media IP information is not printed out. The following is an example of output for a Symmetric NAT device. Signalling Media Public IP Addr:Port (Private IP Addr:Port) Type Set-TN Regd-TN Public IP Addr:Port (Private IP Addr:Port) NAT Type RTCP ---------------------------- ------------------------------------ ---- ------------ ------------- -----------47.11.217.102:10000 < > Symmetric Y i2002 Ph2 061-08 061-08 (192.168.1.3:5000) 553-3001-365 Standard 3.00 September 2004 Features Page 77 of 770 The type of NAT is indicated, as detected by Echo Server 2. The support of RTCP signaling is indicated by Y; if N is displayed, then features that depend on RTCP, such as Proactive Voice Quality Management (PVQM), will not work. An IP Phone’s TN or public signaling IP address can be entered after the command. Entering the isetNATShow command at the CLI of any card in an IP Telephony Node along with the TN or IP address of a particular IP Phone displays the information shown in the previous example, as well as the identification of the card with which the IP Phone is registered. This is useful when it is necessary to identify the card on which to enable a message monitor, or to connect a sniffer, when debugging a specific IP Phone’s problem. Figure 7 on page 78 shows a sample output. IP Line Description, Installation, and Operation Page 78 of 770 Features Figure 7 isetNATShow sample output IPL> isetNATShow "47.11.217.102" value = 0 = 0x0 IPL> Signalling Media Public IP Addr:Port Public IP Addr:Port (Private IP Addr:Port) (Private IP Addr:Port) NAT Type RTCP Type Set-TN Regd-TN ---------------------------- ---------------------------- --------- ---- ------------ ------------- ------------>Found on Card TN 009-00 , ELAN IP 47.11.217.21, TLAN IP 47.11.216.185 : 47.11.217.102:10000 47.11.217.102:10354 Cone Y i2002 Ph2 061-08 061-08 (192.168.1.3:5000) (192.168.1.3:5200) ->Found on Card TN 009-00 , ELAN IP 47.11.217.21, TLAN IP 47.11.216.185 : 47.11.217.102:10006 47.11.217.102:10007 Cone Y i2004 061-00 061-00 (192.168.1.4:5000) (192.168.1.4:5200) The command “isetShow” and “isetNATShow” can display the information about an IP Phone based on IP or TN. The “IP” is the Public IP address used for signaling. If “isetShow” or “isetNATShow” is typed with a Public IP address used by multiple IP Phones, then all those IP Phones are displayed, even if the IP Phones are registered to different cards. Therefore, the “isetShow” and “isetNATShow” now display the information similar to the following example: Signaling.... Public... (Private... ---->Found on Card TN 009-00, ELAN IP.... 47.11.217.102.... 553-3001-365 Standard 3.00 September 2004 Features Page 79 of 770 Notice how the “Found on” line is below the title, and is displayed before every IP Phone. Note: If a PVQM command is entered with an IP address that multiple IP Phones are using, then an error message is also printed. WARNING: There are 2 IP Phones that use the public IP address of 47.11.217.102 These PVQM commands include: • RTPStatShow • RTPTraceShow • RTPTraceStop • rPing • rPingStop • rTraceRoute • rTraceRouteStop • eStatShow • RUDPStatShow • isetInfoShow echoServerShow The echoServerShow command provides both configuration information about the Echo Servers and information about interactions with the Echo Servers for the IP Phones on a specific LTPS. Use this command on an LTPS card to investigate a problem with an IP Phone registered to that LTPS card. This is a per-card command that provides information on the Echo Servers from the viewpoint of the LTPS on the card where the command is entered. The command has one optional parameter, “action”; the only valid value is 99. When echoServerShow 99 is entered, the counter values are reset after they are displayed. When just echoServerShow is entered, the counter values are displayed without being reset. IP Line Description, Installation, and Operation Page 80 of 770 Features The output for each Echo Server displays the following information: • Configured – the IP address: port configured for this Echo Server in LD 117 • Actual – the IP address: port used for this Echo Server, followed by an explanation in parenthesis. This is different from the “Configured” parameter only when the default address (0.0.0.0) has been configured. The explanation in parenthesis is one of the following: — (TLAN IP, this card) – the IP address used is the TLAN network interface of this card; the Echo Server is active on this card. — (node IP, this card) – the IP address used is the Node IP address; the Echo Server is active on this card because it is the node master. — (node IP, other card) – the IP address used is the Node IP address, but anther card is currently the Node master; the Echo Server is not active on this card. — (not this card) – the IP address is not this card’s TLAN IP address or the Node’s IP address; the Echo Server is not active on this card. • LTPS request sent – the number of Resolve Port Mapping Request messages sent from the LTPS to IP Phones, with this Echo Server identified as the one to contact. • Failed resp rec.d – the number of Resolve Port Mapping Ack messages received from the IP Phones that had the public IP address and port configured as 0.0.0.0:0000. Each increment of this counter indicates an IP Phone never received the Discover Port Mapping Ack response from the Echo Server (all 10 attempts failed). The two peg counts give an indication of the interaction this LTPS is having with the Echo Server. It is not a direct sign of the health of the Echo Server; network conditions for IP Phones registered to this LTPS may be preventing communication with this Echo Server while another LTPS’s IP Phones have no problem. The echoServerShow command helps understand why a particular IP Phone registered to a LTPS may be having difficulties or to uncover patterns of communication problems between IP Phones and Echo Servers. A sample output is shown in Figure 8 on page 81. 553-3001-365 Standard 3.00 September 2004 Features Page 81 of 770 Figure 8 echoServerShow sample output When the echoServerShow command with the reset parameter 99 is entered, the counter values are displayed and then reset. If the echoServerShow command is entered again and no requests have since been sent, the counter values are displayed as 0. A sample output is shown in Figure 9 on page 82. IP Line Description, Installation, and Operation Page 82 of 770 Features Figure 9 echoServerShow 99 sample output vgwShow The vgwShow command has been modified to allow the optional entry of an IP Phone’s IP address and port. A search is made of all the Voice Gateway Media Cards in the node to find the IP Phone’s IP address and port. With the introduction of NAT Traversal, more than one IP Phone may map to a single IP address. The command input is modified to allow the entry of the public port number for a specific IP Phone. vgwShow <“IPAddr”>, 553-3001-365 Standard 3.00 September 2004 Features Page 83 of 770 If no port number is entered, the first entry found with the specified IP address on a Voice Gateway Media Card is returned. An example is shown in Figure 10. Figure 10 vgwShow with IP address command output When the IP address is found in the list of VGW channels for a card other than where the command was entered, the VGW channel information for the first occurrence is returned, plus a count of the number of times the IP address occurs in that card’s list. Multiple instances can occur when the customer’s network is configured so that multiple IP Phones are behind a NAT device sharing the NAT device’s public IP address. If there is more than one match, the administrator can log into that specific card and enter the vgwShow command without entering an IP address and port number. That will print all the busy channels on the card. To quickly find a particular IP Phone, use the IPDN or DNIP commands in LD 117 to obtain the IP Phone’s media stream public IP address and port number; then enter the public IP address and port number as parameters for the vgwShow command. Firmware download using UNIStim FTP Previously, IP Phones on CS 1000 and Meridian 1 systems downloaded their firmware using Trivial File Transfer Protocol (TFTP). Firewalls often have their well-known TFTP port (port 69) disabled to maintain security. When port 69 is blocked, IP Phones cannot obtain firmware downloads. This situation prevents the IP Phone from registering and coming into service. IP Line Description, Installation, and Operation Page 84 of 770 Features In order to eliminate the file transfer problem with the firewalls and TFTP, CS 1000 Release 4.0 implements a UNIStim File Transfer Protocol (UFTP) download solution. UFTP enhances security, because it is a proprietary protocol, as opposed to TFTP which is an open protocol. It enables customers to improve their firewall security by closing port 69 to block TFPT in their firewall and policy-based switches and routers. IMPORTANT! For the UFTP IP Phone firmware download to work, it is necessary to explicitly open port 5100 (UNIStim signaling) and port 5105 (UFTP signaling). If a network firewall is in use, ports 5100 (UNIStim signaling) and 5105 (UFTP signaling) must be explicitly opened in the IP Phone-to-UFTP server direction. Opening these ports enables UNIStim and UFTP firmware download messages to travel through the firewall. Both of these ports can be safety enabled by firewalls. See Table 18. Table 18 Source/destination port usage on either side of the connection Port IP Phone signaling IP Phone UFTP UFTP Server Source port 5000 (see note) 5000 (see note) 5105 Destination port 5100 5105 5000 (see note) Note: The UFTP firmware download is compatible with the NAT Traversal feature. If the IP Phone is behind a Network Address Translation (NAT) device, then a different public signaling port is used. The public signaling port is assigned dynamically. See Figure 11 on page 85. 553-3001-365 Standard 3.00 September 2004 Features Page 85 of 770 Figure 11 Using NAT with UFTP NAT router 192.168.0.1 <-> 47.10.221.114 Private IP Information: IP: 192.168.0.101 DN: 23215 Signaling Port: 5000 UFTP Port: 5000 Audio Port: 5200 Public IP Information IP: 47.10.221.114 DN: 23215 Signaling Port: 1500 (dynamic) UFTP Port: 1500 (dynamic) Audio Port: 1501 (dynamic) IP Cloud CS 1000 Release 4.0 System Node IP: 47.10.220.100 TLAN IP: 47.10.220.105 Signaling Port: 5100 UFTP Port: 5105 IP: 47.10.221.201 DN: 42121 Signaling Port: 5000 UFTP Port: 5000 Audio Port: 5200 Two Download log files log the results of the UFTP firmware downloads: “uftplog0.txt” and “uftplog1.txt”. One file is active and one file is inactive. When a file is full, it becomes the inactive file, and the other file is written to. The active file displays the most recent entries. On Voice Gateway Media Cards, the log files are located in the /C:/LOG directory. The Download log files are limited to 10K each for a total of 20K. Approximately 128 log messages can be saved in each log file. On the Signaling Server, the log files are located in the /U/LOG directory. The Download log files are limited to 400K each, for a total of 800K. Approximately 5000 log messages can be saved in each log file. IP Line Description, Installation, and Operation Page 86 of 770 Features The Download log files are generated during initialization of the UFTP Server task. If the Download log files do not exist during the start-up of the UFTP Server task, new Download log files are created. The Download log file is a circular file, writing over the oldest information when the log file is full. Each log file entry contains the following download information about the IP Phone: • F/W download date • F/W download start time • F/W download status (specifies if the download succeeded or failed) • IP Address of the IP Phone • IP Phone type • • F/W download error code. If the F/W download was successful, this field is empty. The following is the list of all possible error codes: — 00 = F/W not exist — 01 = F/W size is 0 — 02 = F/W corrupted — 03 = RUDP connection down — 04 = Response time out — 05 = Reason: Unknown The format of the download log message is: < IP Phone type> The following is an example of the Download log message: 31/01/04 17:04:36 F/W Dnld fail:(47.11.215.44) i2004 Ph2 (F/W Corrupted) 31/01/04 17:05:46 F/W Dnld success:(47.11.215.44) i2004 553-3001-365 Standard 3.00 September 2004 Features Page 87 of 770 CLI commands CS 1000 Release 4.0 introduces the following CLI commands to support UFTP firmware downloads: • uftpNodeShow • uftpShow • uftpRunTimeDataReset • activeDlogShow • nActiveDlogShow • dnldFailShow uftpNodeShow The uftpNodeShow command provides a complete UFTP IP Phone firmware download summary of each node. This includes the configured cards in the node that are not responding. Each node summary contains the following information: • Index • TN - LL S CC or C C • Host Type • TLAN IP Address • Data Period • Active Download Count (Act) • Server Up Time (Srv Up Time) • Successful Download Count (Ok) • Failure Download Count (Fail) Figure 12 on page 88 is an example of output from the uftpNodeShow command. IP Line Description, Installation, and Operation Page 88 of 770 Features Figure 12 uftpNodeShow command output uftpShow The uftpShow command displays the following information: • configuration information about UFTP • count of successful downloads since the Signaling Server/Voice Gateway Media Card reboot • count of downloads that failed or prematurely ended since the Signaling Server/Voice Gateway Media Card reboot • number of active downloads, and a list of each, including: — type of IP Phone — IP addresses of the IP Phones that downloaded firmware — number of bytes downloaded Figure 13 on page 89 is an example of output from the uftpShow command. 553-3001-365 Standard 3.00 September 2004 Features Page 89 of 770 Figure 13 uftpShow command output IP Line Description, Installation, and Operation Page 90 of 770 Features uftpRunTimeDataReset The uftpRunTimeDataReset command is used to reset the run time data field in the UFTP data block. Figure 14 is an example of output from the uftpRunTimeDataReset command. Figure 14 uftpRunTimeDataReset command output activeDlogShow The activeDlogShow command displays the active log file information for UFTP IP Phone firmware downloads. When no parameter is entered, the output displays the contents of the entire active log file. When a line number is entered, activeDlogShow[numOfLine], the output displays the active log file by the number of lines. Figure 15 on page 91 is an example of output from the activeDlogShow command. 553-3001-365 Standard 3.00 September 2004 Features Page 91 of 770 Figure 15 activeDlogShow command output inActiveDlogShow The inActiveDlogShow command displays the non-active dlog file information for UFTP IP Phone firmware downloads. When no parameter is entered, the output displays the contents of the entire file. When a line number is entered, inActiveDlogShow [numOfLine], the output displays the non-active dlog file by the number of lines. Figure 16 on page 92 is an example of output from the inActiveDlogShow command. IP Line Description, Installation, and Operation Page 92 of 770 Features Figure 16 inActiveDlogShow command output dnldFailShow The dnldFailShow command displays the “download failed” status logged in the active and inactive files. When no parameter is entered, the output displays the all the failed UFTP download information in the active and inactive files. When a line number is entered, dnldFailShow[numOfLine], the output displays the download fail status in the active and inactive files by the number of lines. Figure 17 on page 93 is an example of output from the dnldFailShow command. 553-3001-365 Standard 3.00 September 2004 Features Page 93 of 770 Figure 17 dnldFailShow command output Personal Directory, Callers List, and Redial List IP Line 4.0 introduces the Personal Directory, Callers List, and Redial List features. These features are supported on CS 1000 systems running CS 1000 Release 4.0 software. The Personal Directory allows a user to enter or copy names to a personal directory, and delete those entries if desired. The Callers List and Redial List are call log features. The content of these lists is generated during call processing. A user can scroll through the Callers List to see who has called. The user can dial a number from the Redial List. The Personal Directory, Callers List, and Redial List use a separate central database, called the IP Phone Application Server, to store directory data and user profile options. IP Line Description, Installation, and Operation Page 94 of 770 Features Note: Since the IP Phone Application Server is part of the IP Line 4.0 software on the Signaling Server, the Personal Directory, Callers List, and Redial List are only supported on CS 1000 systems. Password protection is available to control access to a user’s Personal Directory, Callers List, and Redial List. IMPORTANT! CPND must be configured on the system to enable Personal Directory, Callers List, and Redial List. Fore more information, refer to “Personal Directory, Callers List, and Redial List” on page 145. IP Call Recording IP Call Recording provides the IP address and port information for an IP Phone in new Information Elements (IE) over Application Module Link (AML) for Meridian Link Services (MLS). This information correlates the TN of a specific IP Phone with its associated IP address for a call recording application. When enabled in LD 17, IP Call Recording sends a modified AML message for each call. The modified message identifies the call’s IP endpoint and makes it possible to correlate the RTP packets for that call to a particular IP Phone IP Call Recording introduces a new IE pair: • This Party IP IE (monitored party) • Other Party IP IE (remote party) The IP IE pair is similar to the existing IE pairs: 553-3001-365 • For DNs: This Party DN IE, Other Party DN IE • For TNs: This Party TN IE, Other Party TN IE Standard 3.00 September 2004 Features Page 95 of 770 The IP IEs are optional in the Unsolicited Message Status (USM) (Active) and USM (Restore) messages. Note the following: • If the USM message applies to a monitored key on a digital telephone, then the IP IEs are not sent. • If the USM message applies to a monitored key on an IP Phone, then the IP IEs are sent: one for the monitored party and one for the remote party. A call recording application is provided with status update messages for the call keys of any IP Phone it is monitoring. These USM messages contain the IP address and port number information for the monitored IP Phone and the remote party in the active call. By using a Layer 2 switch that supports port mirroring, the call recording device can monitor the media stream for the active call and record it. Administration LD 17 introduces the Enhanced Unsolicited Status Message (USM) IE enable (IPIE) prompt. The IPIE prompt enables or disables IP Call Recording on a system-wide basis. The functionality is disabled by default. When enabled, a modified Application Module Link (AML) message that identifies the IP endpoint is sent for each call. The IPIE prompt is added in LD 17 under system parameters (PARM). LD 17 – IP Call Recording (Part 1 of 2) Prompt Response Description REQ CHG Change existing data. TYPE PARM Change system parameters. LPIB 96 – 7500 Low priority Input Buffers NDRG (NO) YES New Distinctive Ringing MARP (YES) NO Multiple Appearance Redirection Prime feature allowed. ... IP Line Description, Installation, and Operation Page 96 of 770 Features LD 17 – IP Call Recording (Part 2 of 2) Prompt Response Description IPIE (NO) YES Enhanced Unsolicited Status Message (USM) IE enable. YES = Allow “This Party IP IE” and “Other Party IE” to send with USM. FRPT (NEFR) OLFR (Deny) or allow access to incoming calls by FRE station. ... OTM and Element Manager do not support LD 17. However, OTM does support the corresponding print overlay, LD 22, which prints the prompt IPIE. pbxLink connection failure detection IP Line 4.0 introduces pbxLink connection failure detection. The pbxLink connection failure detection feature provides a means of detecting the link status of Voice Gateway Media Cards. An alarm is generated if the pbxLink is not detected after a warm or cold start of the Call Server. The Call Server monitors the pbxLink. The Call Server maintains a list of all known registered elements (Signaling Servers and Voice Gateway Media Cards). When booted, a Call Server has a 5-minute delay to enable these known elements to re-establish contact with the Call Server. If a known element fails to register with the Call Server, an ELAN0028 alarm is generated. If an unknown Signaling Server or Voice Gateway Media Card registers with the Call Server, an ELAN0029 alarm is generated. 553-3001-365 Standard 3.00 September 2004 Features Page 97 of 770 Displaying pbxLink information Element Manager For CS 1000 systems, use the Element Manager System Status > IP Telephony > Node > Gen Cmds > Group - pbxLink > Command pbxLinkShow window to display the pbxLink information. CLI For a Meridian 1 or CS 1000 system, use the LD 117 STAT SERV command at the Command Line Interface (CLI) of the Call Server to display the pbxLink information. LD 117 STAT SERV enhancement The suite of STAT SERV (Statistic Services) commands enables a technician to display link-status information for Voice Gateway Media Cards that are registered to a Call Server. STAT SERV can provide consolidated link-status information by application type, IP address, host name, and IP Telephony Node ID. Prior to CS 1000 Release 4.0 software, STAT SERV status information included the following: • node ID • host name • ELAN IP address • element role • platform type • connection ID • enabled applications • registered/unregistered endpoints, such as IP Phones and Voice Gateway Media Cards. IP Line Description, Installation, and Operation Page 98 of 770 Features In CS 1000 Release 4.0 software, the STAT SERV command has been enhanced to provide information about the pbxLink and enabled applications. It also provides a Signaling Server resource count to aid in determining the number of virtual trunks that can be configured. pbxLink information The STAT SERV command provides the following pbxLink information: • the time the pbxLink was last established • the time the pbxLink was lost, if previously established • the time the pbxLink last attempted to establish a connection, if the pbxLink failed to establish • the Signaling Server resource count Application information If an active link to an element is established, the Call Server obtains information about the applications running on the element. Table 19 lists the applications and describes the information provided by those applications. Table 19 Queried information in STAT SERV (Part 1 of 2) Application / element Information provided LTPS application number of registered IP Phone number of busy IP Phones VTRK application number of registered VTRKs number of busy VTRKs 553-3001-365 Standard 3.00 September 2004 Features Page 99 of 770 Table 19 Queried information in STAT SERV (Part 2 of 2) Application / element Information provided Voice Gateway Media Cards number of registered Voice Gateway Media Cards Signaling Servers and Voice Gateway Media Cards time that the element established its link with the Call Server number of busy Voice Gateway Media Cards elements that failed to register or lost their link Figure 18 shows an example of LD 117 STAT SERV output. Figure 18 Sample LD 117 STAT SERV output => stat serv ELANIP LDR SRV APPS PBXLINK NODE HOSTNAME PBXLINK PBXLINK CONNECTID ID STATE DATE TIME 9090 host82 47.11.217.176 NO SMC LTPS LINK UP 28/07/2004 17:51:31 200a4048 Sets: [reg - 00000] [busy - 00000] VGWs: [reg - 00032] [busy - 00000] 9090 host9 47.11.217.177 YES SS LTPS LINK UP 28/07/2004 17:51:33 200a3f68 VTRK Sets: [reg - 00003] [busy - 00000] VTRK: [reg - 00383] [busy - 00000] SIGNALLING SERVER CAPACITY (SSRC): 2048 9090 itgCard 47.11.217.2 28/07/2004 17:51:16 0 IP Line NO ITGP LTPS FAILED Description, Installation, and Operation Page 100 of 770 Features Table 20 lists the descriptions for the fields in the STAT SERV response. Table 20 STAT SERV response fields and description (Part 1 of 3) STAT SERV response field Description NODE ID Identifies the related node. Value is a number from 0 – 9999. HOSTNAME Identifies the alias that the host has been given by the system. Value is a string. ELANIP Identifies the element’s IP connection to the Call Server. Value is an IP address. LDR Specifies if the element is the Leader for the related node. Value is YES or NO. SRV Specifies the element type. Values are: • SMC – Media Card 32-port card • ITGP – ITG-P 24-port card • SS – Signaling Server APPS Specifies the application running on the element. Values are: • LTPS • VTRK 553-3001-365 Standard 3.00 September 2004 Features Page 101 of 770 Table 20 STAT SERV response fields and description (Part 2 of 3) STAT SERV response field Description PBXLINK STATE Specifies the element’s current pbxLink state. Values are: • LINK UP • LOST • FAILED • INV CONN (element is connected, but its configuration was not found on the Call Server, indicating that this element might be connected to the wrong Call Server) PBXLINK DATE/TIME Specifies when the element’s pbxLink state last changed. CONNECTED Specifies the element’s connection ID. sets Values are: • reg – the number of IP Phones registered to the element • busy – the number of IP Phones that are currently busy vgws Values are: • reg – how many voice gateways (DSP resources) are configured on the element • busy – how many voice gateways (DSP resources) are active/busy on the element IP Line Description, Installation, and Operation Page 102 of 770 Features Table 20 STAT SERV response fields and description (Part 3 of 3) STAT SERV response field Description VTRK Values are: • reg – how many VTRK channels are configured on the element • busy – how many VTRK channels are active/busy on the element SSRC Signaling Server capacity IP Phone support The IP Line 4.0 application supports the following IP Phones: • IP Phone 2001 • IP Phone 2002 • IP Phone 2004 • IP Softphone 2050 • Mobile Voice Client (MVC) 2050 For detailed information about IP Phones, see the following guides: 553-3001-365 • IP Phone 2001 User Guide • IP Phone 2002 User Guide • IP Phone 2004 User Guide • Nortel Networks IP Softphone 2050 User Guide • IP Phones: Description, Installation, and Operation (553-3001-368) Standard 3.00 September 2004 Features Page 103 of 770 Table 21 shows a comparison of the IP Phone 2001, IP Phone 2002, and IP Phone 2004. Table 21 Comparison of the IP Phone 2001, IP Phone 2002, and IP Phone 2004 (Part 1 of 2) Feature IP Phone 2001 IP Phone 2002 IP Phone 2004 Display size and format 1 line display 1 line display 3 line display 24 characters 24 characters 24 characters on each line Information Line 1 line – 24 characters 1 line – 24 characters 3 lines – 24 characters on each line Dedicated Data/Time field No No Yes Context Label field No No Yes Soft Keys 4 soft keys, soft-labeling 6 characters long 4 soft keys, soft-labeling 6 characters long 4 soft keys, soft-labeling 7 characters long Feature Keys No 4 soft keys, soft-labeling 10 characters long 6 soft keys, soft-labeling 10 characters long DHCP support Yes Yes Yes Transducers Handset (HD) Headset (HS) / Handset (HD) / Handsfree (HF) Headset (HS) / Handset (HD) / Handsfree (HF) Mute key No Yes Yes Navigation keys Left and right Up, down, left, and right Up, down, left, and right Display Keys Other features IP Line Description, Installation, and Operation Page 104 of 770 Features Table 21 Comparison of the IP Phone 2001, IP Phone 2002, and IP Phone 2004 (Part 2 of 2) Feature IP Phone 2001 IP Phone 2002 IP Phone 2004 Voice codec support G.711, G729A, G729AB, G.723.1 G.711, G729A, G729AB, G.723.1 G.711, G729A, G729AB, G.723.1 Firmware download Automatic firmware version checking and download Automatic firmware version checking and download Automatic firmware version checking and download 3-port unmanaged Layer 2 switch for data and voice No Built-in Built-in Corporate Directory access No Note: Earlier models have an external switch. Yes Yes IP Phone Key Expansion Module IP Line 4.0 supports the Nortel Networks IP Phone Key Expansion Module (KEM). The IP Phone KEM is a hardware component that attaches to the Nortel Networks IP Phone 2002 and IP Phone 2004 and provides additional line appearances and feature keys. Note: The IP Phone KEM is not supported on the Nortel Networks IP Phone 2001. Up to two IP Phone KEMs can be attached to an IP Phone 2002 or IP Phone 2004. With two IP Phone KEMs attached, the IP Phone 2004 can have up to 60 lines/feature keys, while the IP Phone 2002 can have up to 52 lines/feature keys. Note: The IP Phone 2004 can also have up to 60 lines/feature keys using the shift key and one IP Phone KEM. With two IP Phone KEMs attached, the shift key does not affect the IP Phone KEMs since the maximum number of lines/feature keys is already available. The IP Phone 2002 does not support shift key functionality. 553-3001-365 Standard 3.00 September 2004 Features Page 105 of 770 When an IP Phone KEM is installed on an IP Phone 2002 or IP Phone 2004, the controls on the IP Phone affect both the IP Phone itself and the IP Phone KEM. The IP Phone KEM must be configured in LD 11 before it can be used. For information on using the IP Phone KEM, refer to IP Phone Key Expansion Module User Guide. Corporate Directory The Corporate Directory feature is based on the M3900 telephone Corporate Directory feature. The Corporate Directory database is created using OTM 2.2 and is generated from one of the following: • the configured DN information from the Call Server • the data from a corporate LDAP server The database is downloaded and stored on the Call Server. It is then accessible to the IP Phones. The Signaling Server can support Corporate Directory access for the same number of IP Phones that are registered. The Directory key on the IP Phone is used to access the directory, select a listing, and then dial a number from the Corporate Directory. The Navigation keys are used to refine the search within the Corporate Directory. Corporate Directory is configured in LD 11. LD 11 accepts CRPA/CRPD class of service for the IP Phones (see “Corporate Directory: LD 11 configuration” on page 415). For more information about the operation of the Corporate Directory feature, refer to the following: • Optivity Telephony Manager: Installation and Configuration (553-3001-230) • IP Phones: Description, Installation, and Operation (553-3001-368). IP Line Description, Installation, and Operation Page 106 of 770 Features Element Manager support Element Manager enables configuration of IP Line 4.0 using a web browser on CS 1000 systems. Each Signaling Server hosts a web server, Element Manager, that allows configuration, administration, and maintenance to be performed on the system components. Element Manager is a graphical web interface that provides a graphical alternative to the traditional CLI and overlays. The interface is available to users running a web browser on a PC. No special client software is required. The Element Manager web server runs on each Signaling Server and the Signaling Server acts as a file server. When a web browser is opened and the IP address of the Signaling Server is entered, the Element Manager interface is displayed. Element Manager is then used to perform tasks such as configuring an IP Telephony Node, checking and uploading loadware and firmware files, and retrieving the CONFIG.INI and BOOTP.TAB configuration files from the Call Server. The Voice Gateway Media Cards are notified to FTP the files from the Call Server. OTM 2.2’s Navigators incorporate links to each Element Manager web server in a network. BOOTP and CONFIG.INI If the Voice Gateway Media Card is a Follower of a primary Signaling Server, it generates a BOOTP request to retrieve its network information. The request for IP address, node ID, and node IP is directed to a BOOTP server within its node. If the BOOTP request fails, the Voice Gateway Media Card uses the last configuration. This fallback configuration data is stored locally on the Voice Gateway Media Card. If the BOOTP request is successful, the Voice Gateway Media Card refreshes its current fallback configuration data. 553-3001-365 Standard 3.00 September 2004 Features Page 107 of 770 If the Voice Gateway Media Card is located in a stand-alone IP Telephony node, and is designated as the Leader for its node, it provides BOOTP service to all other configured Voice Gateway Media Cards within its node. The Leader determines its own network information using a combination of locally stored static information and the bootp.tab file. If the Voice Gateway Media Card is located in a stand-alone IP Telephony node, and is designated as a Follower, it generates a BOOTP request to retrieve its network information. The request for IP address, node ID, and node IP is directed to a BOOTP server within its node. If the BOOTP request fails, the Voice Gateway Media Card uses the last configuration. This fallback configuration data is stored locally on the Voice Gateway Media Card. If the BOOTP request is successful, the Voice Gateway Media Card refreshes its current fallback configuration data. The Voice Gateway Media Card reads the contents of the CONFIG.INI file located on its disk for additional configuration parameters. Call Statistics collection IP Line 4.0 enables statistics on the Quality of Service (QoS) of calls connected by the Call Server to be collected. These commands print the number of IP Phones registered on a card, zone, node, or Signaling Server. Traffic printouts are available per zone at user-configurable intervals for the following: • blocked calls • bandwidth used • call attempts and completions Counting IP Phones The commands to count registered IP Phones are available in LD 32. The commands are: • ECNT CARDS L S C • ECNT ZONE zoneNum IP Line Description, Installation, and Operation Page 108 of 770 553-3001-365 Features • ECNT NODE nodeNum • ECNT SS hostName Standard 3.00 September 2004 Features Page 109 of 770 Table 22 describes these commands. Table 22 LD 32 commands to count registered IP Phones (Part 1 of 2) Command Description ECNT CARD L S C Counts and prints the number of IP Phones registered for the specified card. • If the parameter is specified, the count is specific to that customer. A card must be specified to enter a customer; otherwise, the count is across all customers. • If no parameters are entered, the count is printed for all zones. A partial TN can be entered for the card (L or L S) which then prints the count per that parameter. A customer cannot be specified in this case. Example: ECNT CARD 81 << Card 81 >> Number of Registered Ethersets: 5 Number of Unregistered Ethersets: 27 ECNT ZONE zoneNum Counts and prints the number of IP Phones registered for the specified zone. • If parameter is specified, the count is specific to that customer. A zone must be specified to enter a customer; otherwise, the count is across all customers. • If no parameters are entered, the count is printed for all zones. Example: ECNT ZONE 0 0 << Zone 0 Customer 0 >> Number of Registered Ethersets: 4 Number of Unregistered Ethersets: 17 IP Line Description, Installation, and Operation Page 110 of 770 Features Table 22 LD 32 commands to count registered IP Phones (Part 2 of 2) Command Description ECNT NODE nodeNum Counts and prints the number of IP Phones registered for the specified node. • If the nodeNum parameter is not entered, the count is printed for all nodes. Example: ECNT NODE 8765 << Zone 8765 >> Number of Registered Ethersets: 3 ECNT SS Counts and prints the number of IP Phones registered for the specified Signaling Server. • If hostName parameter is not entered, the count is printed for all Signaling Servers. Example: ECNT SS << Signaling Server: BVWAlphaFox IP 10.10.10.242>> Number of Register Ethersets: 1000 Note: If the hostName variable contains an underscore (_), then an NPR001 error message is returned, as an underscore is considered to be an invalid character. Error messages for the ECNT commands Error messages are printed when invalid data is entered for these commands. The messages include valuable information such as the correct ranges for the command parameters. See the following tables for the error messages: 553-3001-365 • Table 23: “ECNT Card command error messages” on page 111. • Table 24: “ECNT Zone command error messages” on page 111. Standard 3.00 September 2004 Features Page 111 of 770 • Table 25: “ECNT Node command error messages” on page 112. • Table 26: “ECNT SS command error message” on page 112. Table 23 ECNT Card command error messages Error Error Message Slot out of range error Slot out of range. Range: [61-99] Slot non-virtual loop error Slot does not correspond to a virtual loop. Slot not configured loop error Slot corresponds to a virtual loop but it is not configured. Customer out of range error Customer out of range. Range: [0-31] Customer not configured error Customer does not exist. Combination of invalid slot and invalid customer Slot does not correspond to a virtual loop. Customer out of range. Range: [0-31] Table 24 ECNT Zone command error messages Error Error Message Zone out of range error Zone out of range. Range: [0-255] Zone not configured error Zone not configured. Customer out of range error Customer out of range. Range: [0-31] Customer not configured error Customer does not exist. Combination of invalid zone and invalid customer error Zone not configured. IP Line Customer out of range. Range: [0-31] Description, Installation, and Operation Page 112 of 770 Features Table 25 ECNT Node command error messages Error Error Message Node out of range error Node out of range. Range: [0-9999] Node not configured error Node not registered. Table 26 ECNT SS command error message Error Error Message SS not found in system error Signaling Server does not exist. IP Phone Zone Traffic Report 16 A system traffic report, IP Phone Zone Traffic Report 16 in LD 2 is created on the system to print IP Phone data at the zone level. The data is printed for the following categories at the end of each collection period on a per-zone basis: • Total inter/intra-zone calls made • Total inter/intra zone calls blocked • Percent average inter/intra zone bandwidth used • Percent maximum inter/intra zone bandwidth used • Total inter/intra zone bandwidth threshold exceeded count The counters are reset after the data is printed. 553-3001-365 Standard 3.00 September 2004 Features Page 113 of 770 The “Total inter/intra zone bandwidth threshold exceeded count” prints the number of times a user-configured bandwidth threshold was exceeded for the zone during the collection period. LD 2 commands that are related to setting the system threshold are used with a value defined for the bandwidth threshold. Table 27 System threshold commands Command Description TTHS TH tv Prints the current system thresholds. STHS TH tv -- TV Sets the system thresholds. Note 1: A TH value of 5 is used for the zone bandwidth threshold. Note 2: The system thresholds TV value is the percentage of the zone’s maximum bandwidth. The range values are 000 – 999, where 000 corresponds to 00.0% and 999 corresponds to 99.9%. The default is 90.0%. The following examples first set the system bandwidth to 75% and then print the actual value. .STHS 5 750 .TTHS 5 Table 28 describes the intrazone IP Phone Zone Traffic Report 16 output data. Table 28 IP Phone Zone Traffic Report 16 intrazone data output (Part 1 of 2) Data Description zone number of the zone cmi intrazone calls made (successful) cbi intrazone calls blocked pi intrazone peak bandwidth (%) IP Line Description, Installation, and Operation Page 114 of 770 Features Table 28 IP Phone Zone Traffic Report 16 intrazone data output (Part 2 of 2) Data Description ai intrazone average bandwidth usage (%) vi intrazone bandwidth usage threshold violations cul counts of unacceptable latency samples cupl counts of unacceptable packet loss cuj counts of unacceptable jitter samples cur counts of unacceptable R factor samples cuerl counts of unacceptable Echo Return Loss cwl counts of warning latency samples cwj counts of warning jitter samples cwpl counts of warning packet loss samples cwr counts of warning R factor samples cwerl counts of warning Echo return Loss cmip counts of measuring interval samples Table 29 describes the interzone IP Phone Zone Traffic Report 16output data. Table 29 IP Phone Zone Traffic Report 16 interzone data output (Part 1 of 2) 553-3001-365 Data Description zone number of the zone cmo interzone calls made cbo interzone calls blocked po interzone peak bandwidth (%) ao interzone average bandwidth usage (%) Standard 3.00 September 2004 Features Page 115 of 770 Table 29 IP Phone Zone Traffic Report 16 interzone data output (Part 2 of 2) Data Description vo interzone bandwidth usage threshold violations cwpl counts of warning packet loss cwl counts of warning latency samples cwj counts of warning jitter samples cupl counts of unacceptable packet loss cul counts of unacceptable latency samples cuj counts of unacceptable jitter samples cur counts of unacceptable R factor samples cuerl counts of unacceptable Echo Return Loss cwr counts of warning R factor samples cwerl counts of warning Echo Return Loss cmip counts of interval measuring samples IP Line Description, Installation, and Operation Page 116 of 770 Features The following is an example of the output from Traffic Report 16. >ld 2 TFC000 .invs 16 0000 TFS016 ZONE 003 INTRAZONE 00005 00000 00002 00000 00000 00051 00000 00020 00000 00000 00000 00000 00000 00000 00000 00000 INTERZONE 00003 00000 00007 00006 00000 00006 00000 00006 00000 00000 00000 00000 00000 00000 00000 00000 ZONE 006 INTRAZONE 00008 00000 00001 00000 00000 00050 00000 00048 00001 00000 00000 00000 00000 00002 00025 00000 INTERZONE 00003 00000 00007 00006 00000 00007 00000 00007 00001 00000 00000 00000 00000 00000 00007 00000 All other commands (SOPS, COPS, TOPS) function in the normal manner. Table 30 shows the SOPS, COPS, and TOPS commands: Table 30 SOPS, COPS, TOPS commands 553-3001-365 .tops 1 2 3 4 5 14 display the current system report list .sops 1 2 3 4 5 14 -- 16 add report 16 to be printed .tops 1 2 3 4 5 14 16 display system report list with report 16 added .cops 1 2 3 4 5 14 16 -- 16 delete report 16 .tops 1 2 3 4 5 14 display system report list with report 16 deleted Standard 3.00 September 2004 Features Page 117 of 770 User-defined feature key labels Definition IP Line 4.0 gives the IP Phone user the ability to program the label on the feature key. This label change is saved and then displayed on the feature key. Availability Table 31 describes the feature key availability on the IP Phones. Table 31 Feature key availability on IP Phones Model Number of feature keys Number of feature keys using Shift key Maximum label character length IP Phone 2002 4 N/A 10 IP Phone 2004 6 12 10 IP Softphone 2050 6 12 10 MVC 2050 6 12 10 Note: There are no feature keys on the IP Phone 2001. The feature key labels for each IP Phonee are stored in the Call Server’s database. When the Call Server performs an EDD, the feature key labels are saved to the database. The feature key label information is retrieved from the file into memory during the sysload of the Call Server. When the system performs an INI or sysload, feature key label changes performed by users between the last EDD and the INI or sysload are lost. When the IP Phone registers with the Call Server, the Call Server looks up the feature key label in the memory, based on the TN of the IP Phone. If the labels are found, they are sent to the IP Phone when the key map download occurs. If the labels are not found, the Call Server sends out the key number strings or key functions. IP Line Description, Installation, and Operation Page 118 of 770 Features For more information about programmable line (DN)/feature keys (self-labeled), refer to IP Phones: Description, Installation, and Operation (553-3001-368). Private Zone configuration Private Zones are available for the CS 1000 and Meridian 1 systems. Lack of DSP resources DSP resources for each customer are placed in one common pool. A DSP channel is allocated to an IP-to-circuit-switched call based on a round-robin searching algorithm within the pool. If an available resource cannot be found, the overflow tone is given. For most installations, this approach works because all IP Phone users share the IP Line DSP resources. The DSPs can be provisioned using a DSP-to-IP Phone ratio similar to trunk resources, since the DSPs are used only for circuit-switched access or conference calls. When IP-to-PSTN calls are used, such as with ACD agents or other users who consistently are using trunk resources when making calls, it becomes difficult to provision the system in a way that guarantees an available DSP channel when these users need it. If the other users suddenly make a lot of conference calls or trunk calls, the DSP resources can deplete and as a result, calls cannot be made. This occurs because all DSP channels are in one pool. DSP resources and Private Zones To address this situation, IP Line 4.0 provides the Private Zone Configuration feature for DSP configuration and allocation to the zone configuration. This feature enables the configuration of one or more gateway channels as a private resource. This guarantees DSP availability for critical or ACD agent IP Phone. A zone can be configured as shared or private. 553-3001-365 Standard 3.00 September 2004 Features Page 119 of 770 Shared Zone The current default zone type is a Shared Zone. IP Phones configured in Shared Zones use DSP resources configured in shared zones. If all the Shared Zones’ gateway channels are used, the caller receives an overflow tone and the call is blocked. Select gateway channels in the following order: • Select a channel from the same zone as the zone where the IP Phone is configured. • Select any available channel from the Shared Zones’ channels. Private Zone The Private Zone enables DSP channels configured in a Private Zone to be used only by the IP Phones that have also been configured for that Private Zone. If more DSP resources are required by these IP Phones than what are available in the zone, DSPs from other Shared Zones are used. IP Phones configured in Shared Zones cannot use the Private Zones’ channels. Select the gateway channels in the following order: • Select a channel from the same Private Zone as the zone where the IP Phone is configured. • Select any available channel from the pool of Shared Zones’ channels. LD 117 VGW channels and IP Phones are set as shared or private based on zone configuration. In LD 117, zone configuration can be set to either shared or private using the parameter . IP Line Description, Installation, and Operation Page 120 of 770 Features A zone is configured in LD 117 as follows: NEW ZONE [ ] CHG ZONE [ ] By default, a zone is configured as shared (zoneResourceType=shared). Example The command to add a new zone, in this example zone 10, is as follows: new zone 4 BQ 10000 BQ 10000 private Zone 4 added. Total number of Zones = n (where n is the total number of zones) Site details Use the PRT ZONE or PRT ZONE ALL command to see details for all configured zones. Table 32 gives a sample output of the PRT ZONE or PRT ZONE ALL command. Table 32 Sample output from PRT ZONE or PRT ZONE ALL command Intrazone Interzone Zone State Type Bandwidth (Kbps) Strategy Usage (%) Peak Bandwidth (Kbps) (Kbps) Strategy Usage (%) Peak (Kbps) HO/BRCH 0 ENL SHARED 100000 BQ 0 0 100000 BQ 0 0 HO 1 ENL SHARED 10000 BQ 0 0 10000 BQ 0 0 HO 4 ENL PRIVATE 10000 BQ 0 0 10000 BQ 0 0 HO 10 ENL SHARED 10000 BQ 0 0 10000 BQ 0 0 HO 553-3001-365 Standard 3.00 September 2004 Features Page 121 of 770 Resource-sharing for Shared and Private Zones If a resource-critical IP Phone is configured for a Private Zone, and there are not enough resources found within that zone, the search continues into the Shared Zones within the same customer for an available DSP channel. However, if an IP Phone is configured in a Shared Zone, the Call Server limits its search to the pool of shared DSP channels. The search does not extend into the Private Zones’ channels. When configuring the allocation of shared versus private resources, consideration must be given to the number of private resources that are needed. Enough DSP resources should be configured to prevent the IP Phones configured in Shared Zones from running out of channels. WARNING The Call Server does not search for voice gateway channels in Private Zones when the IP Phone is configured in a Shared Zone. Only IP Phones configured in the same Private Zone can use the Private Zone voice gateway channels. Since the voice gateway channels in the Private Zone are not accessible to IP Phones in the Shared Zone, ensure that only enough private channels are configured to cover the IP Phones in the Private Zone. Do not configure more channels than are required in the Private Zone as the Shared Zone IP Phones cannot access these channels. Run-time configuration changes IP Line 4.0 enables most changes to be made without disabling or rebooting the Voice Gateway Media Cards. After adding configuration information for a new Voice Gateway Media Card and downloading the BOOTP file to the Leader, a new Voice Gateway Media Card can be added to an existing node without rebooting the other cards. IP Line Description, Installation, and Operation Page 122 of 770 Features The following exceptions require a reboot: • a role change; that is, changing a Leader to Follower or changing Follower to Leader. • changing the node IP subnet masks or gateway IP addresses requires a reboot of all cards in the node. • changing the AudioPort parameter in the “config.ini” file on the Voice Gateway Media Card requires a reboot of the card • changing the IP address of a particular card so it can retrieve its new IP address information. Supported run-time changes Therefore, IP Line 4.0 supports only run-time changes for the following: • changes to the CONFIG.INI file • add card or delete card changes to the BOOTP.TAB file Configuration changes have an effect only on new calls. Existing calls are not interrupted. However, there are exceptions: • If the active Call Server ELAN link’s configuration data is changed (for example, a changed IP address), then active calls are released. Note: If the non-active Call Server is changed (for example, survivable side IP address), then the calls are not affected. When the Call Server’s ELAN network interface is re-initialized to implement the configuration change, the IP Phones and gateway channels registrations are unregistered on the Call Server. The Call Server releases the calls. When the link is re-established, the LTPS synchronizes the call states and releases the active calls. Service is interrupted during this re-establishment period and the following are affected: — New IP Phones cannot register. 553-3001-365 Standard 3.00 September 2004 Features Page 123 of 770 — Registered IP Phones cannot establish new calls. — The Voice Gateway Media Card’s faceplate displays S009. Once the ELAN link comes back up, the Line Terminal Proxy Server (LTPS) re-registers the IP Phone s with the Call Server and all service is resumed. • If the codec list is changed, the Voice Gateway Media Card's DSPs might need to be reloaded. For instance, one DSP image contains G.711, FAX, and G.729A/G.729AB. The other DSP image contains G.711, FAX, and G.723.1. If the user has a node configured with the G.729AB codec and the user performs an administrative change to use G.723.1 (or vice versa), the DSPs must be reloaded. After the CONFIG.INI file containing the administrative change is downloaded to a Voice Gateway Media Card, the card's DSPs are reloaded as they become idle. For instance, if all DSPs are idle on the card, the new image is loaded to all of them at once. If one or more DSPs have active calls, the DSP is not reloaded until the active calls have been released. This can cause some DSPs to be reloaded later than others. This functionality is supported by both Element Manager and OTM 2.2. Network wide Virtual Office Network Wide Virtual Office is supported for the CS 1000 systems. IP Line 4.0 provides the Network Wide Virtual Office feature. This feature enables a user to use any IP Phone within the network. The Virtual Office feature provides a call service to “travelling” users who want to use a different physical IP Phone (other than the IP Phone they normally use). Users can log into another IP Phone using their DN and pre-configured Station Control Password (SCPW). IP Line Description, Installation, and Operation Page 124 of 770 Features Once logged in, users have access to their DNs, autodial numbers, key layout, feature keys, and voice mail indication/access that are configured on their own home/office IP Phones. For example, if users go to another office or to a different location within the same office, they can log into any available IP Phone and have all the features of their home/office IP Phone. When the user logs off the IP Phone, the features that were “transferred” to that IP Phone are removed. Network Wide Virtual Office and the Gatekeeper Network Wide Virtual Office is limited to a single Gatekeeper zone. As long as Virtual Offices share the same Gatekeeper, a Virtual Office login can redirect an IP Phone to any of the systems. Requirements A Signaling Server or stand-alone gatekeeper is required in the network. Supported IP Phones Virtual Office is supported for the IP Phone 2001, IP Phone 2002 and IP Phone 2004, the IP Softphone 2050, and the MVC 2050. An IP Phone 2004, IP Softphone 2050, or MVC 2050 users can log in from an IP Phone 2002 under certain conditions. See “Set type checking and blocking” on page 140. Table 33 shows which users can log in to particular IP Phones. Table 33 Virtual Office login from various IP Phones (Part 1 of 2) IP Phone User Virtual Office login An IP Phone 2001 user... ... can Virtual Office log in from another IP Phone 2001, an IP Phone 2002, an IP Phone 2004, an IP Softphone 2050, and an MVC 2050. An IP Phone 2002 user... ...can Virtual Office log-in from another IP Phone 2002, an IP Phone 2004, an IP Softphone 2050, and an MVC 2050. ... can log in under certain conditions when the user attempts a Virtual Office login from an IP Phone 2001. See “Set type checking and blocking” on page 140. 553-3001-365 Standard 3.00 September 2004 Features Page 125 of 770 Table 33 Virtual Office login from various IP Phones (Part 2 of 2) IP Phone User Virtual Office login An IP Phone 2004 user... ...can Virtual Office log in from an IP Phone 2004, an IP Softphone 2050, and an MVC 2050. ...can log in under certain conditions when the user attempts a Virtual Office login from an IP Phone 2001 and IP Phone 2002. See “Set type checking and blocking” on page 140. An IP Softphone 2050 user... ...can virtually login from an IP Phone 2004, another IP Softphone 2050, or an MVC 2050. ...can log in under certain conditions when the user attempts a Virtual Office login from an IP Phone 2001 and IP Phone 2002. See “Set type checking and blocking” on page 140. An MVC 2050 user... ...can virtually log in from an IP Phone 2004, an IP Softphone 2050, or another MVC 2050. ...can log in under certain conditions when the user attempts a Virtual Office login from an IP Phone 2001 and IP Phone 2002. See “Set type checking and blocking” on page 140. Virtual Office User Allowed (VOUA) and Virtual Office Login Allowed (VOLA) must be configured on the IP Phones as follows: • The IP Phone where the user wants to virtually login (destination) must have Virtual Office User Allowed (VOUA) configured. • The IP Phone where the user wants to log in from (source) must have Virtual Office Login Allowed (VOLA) configured. IP Line Description, Installation, and Operation Page 126 of 770 Features Failed password attempt Three failed password attempts to log in using the Virtual Office feature locks the user out from Virtual Office login at the Call Server for one hour. The Call Server lock can be removed by an administrator using an LD 32 command to disable and re-enable that TN. Refer to Communication Server 1000S: Maintenance (553-3031-500) or Software Input/Output: Maintenance (553-3001-511) for more information. Passwords and IP Phone Registration An IP Phone registers using the TN (in its EEPROM). A valid user ID and password are used to determine the Home LTPS for the IP Phone during the Virtual Office connection. A Gatekeeper is required if the Home LTPS is not the LTPS where the IP Phone is registered when the Virtual Office login is initiated. Virtual Office capabilities Virtual Offices provides the following capabilities: 1 A network-wide connection server (Gatekeeper) is equipped to provide addressing information of call servers, based on a user’s DN. 2 A key sequence is entered at an IP Phone to initiate the login sequence. Then the current network DN and a user-level password is entered. The password is the Station Control Password configured in LD 11. If a SCPW is not configured, the Virtual Office feature is blocked. 3 A user logs out when leaving the location. For more detailed information about Virtual Office, see IP Phones: Description, Installation, and Operation (553-3001-368). Branch Office and Media Gateway 1000B The Media Gateway 1000B (MG 1000B) provides a means of extending CS 1000 Release 4.0 features to one or more remotely-located branch offices using the Branch Office feature. A branch office is a remote location in the network where IP Phones, PSTN access, and TDM telephones are located. 553-3001-365 Standard 3.00 September 2004 Features Page 127 of 770 Definition Branch Office is a feature set of the equipment and software that a secondary location needs to centralize the call processing of its IP-based communications network. The Call Server at the main office provides the call processing for the IP Phones in both the main office and the MG 1000B in the branch office location. The MG 1000B in the branch office location provides access to the local PSTN. Connections The MG 1000B is connected to the main office over virtual trunks on a WAN or LAN. IP Phone calls and IP network connections are controlled by, and come from, the main office. If the main office fails to function, or a network outage occurs, the Small System Controller (SSC) in the MG 1000B provides service to the IP Phones located in the branch office location. The IP Phones then survive an outage between the MG 1000B and the main office. Components The basic hardware of an MG 1000B includes the Media Gateway and the Signaling Server. The Media Gateway provides access to the local PSTN for users in the branch office location. It also provides support for analog devices such as fax machines or telephones in the branch office location. For detailed information about MG 1000B, refer to Branch Office: Installation and Configuration (553-3001-214). 802.1Q support The IP Phone 2001, IP Phone 2002, and IP Phone 2004 support 802.1Q. This support enables the definition of virtual LANs (VLANs) within a single LAN. This improves bandwidth management, limits the impact of broadcast and multicast messages, and simplifies VLAN configuration and packet prioritization. Configuration of 802.1Q on IP Phones The 802.1Q support for the IP Phones is configured and controlled using the IP Phone’s user interface or DHCP. The DHCP approach eliminates the need to manually configure the VLAN ID during the installation. IP Line Description, Installation, and Operation Page 128 of 770 Features To configure 802.1Q, set the following: • “p” bits • VLAN ID Set the “p” bits By default, the 3-bit field “p” bits are set to 110b (6), which is the value recommended by Nortel Networks. The “p” bit value can be changed using either OTM or Element Manager. Two fields in OTM 2.2 and Element Manager are used to set the “p” bits: 1 A checkbox that, when selected, means the priority bits should be set to the value specified by the 802.1Q priority bit value field. If the checkbox is unselected, the IP Phone sends out the default priority of 6. 2 A 802.1Q priority bit value field. This field sets the value that the IP Phones sends out. The range is 0 – 7. Set the VLAN ID The contents of the VLAN ID field can be specified on a “per interface” basis and is a global setting. This means that all packets transmitted by the IP Phone have the same VLAN ID. The VLAN ID is specified as follows: • the default VLAN ID is 000 (hex) • the VLAN ID can be set during a manual configuration of the IP Phone using the IP Phone keypad, or automatically retrieved using DHCP (automatic VLAN discovery) Note: For more information about manual or automatic IP Phone configuration, refer to IP Phones: Description, Installation, and Operation (553-3001-368). 553-3001-365 Standard 3.00 September 2004 Features Page 129 of 770 DHCP requirements Some implementation requirements of the Automatic VLAN Discovery using DHCP are: 1 A DHCP server IP address pool must exist for each subnet (also VLANs). This is standard DHCP operation. The requirement is the same for PCs or IP Phones. 2 A DHCP server should not exist in more than one VLAN at one time (one subnet for each VLAN), unless the link to the DHCP server is tagged and the DHCP server can recognize this. With an untagged link to the DHCP server, traffic could originate on one VLAN and end up on the other VLAN. In this case, the VLAN using DHCP feature does not work. 3 Voice and data subnets must be separate if the three-port switch with VLANs is being used. 4 A Layer three switch (or router) with a relay agent must be used because traffic from the voice VLAN to the data VLAN must be routed. Presumably, the DHCP server is on the data VLAN. Without a relay agent, a DHCP server must exist on each subnet. 5 At least two IP address pools are used on the DHCP server – one for the Voice VLAN/subnet and another for the Data VLAN/subnet. Additional pools can be added as required as long as one IP address pool per subnet and VLAN is used. A relay agent is required if it is a PC-only network. Control of the IP Phone’s 802.1Q The 802.1Q header in the outgoing packets from the IP Phones is enabled by one of the following: • If the IP Phone’s VLAN GUI response is set to 1, then the 802.1Q functionality is enabled. All packets from the IP Phone have the 802.1Q header as part of the Ethernet frame. • If the IP Phone’s VLAN GUI response is set to 2, then the 802.1Q functionality is enabled after the DHCP response is received with the VLAN ID. • If the OTM or Element Manager configuration enables the use of the “p” bits, once downloaded to the IP Phone, the 802.1Q functionality is enabled. IP Line Description, Installation, and Operation Page 130 of 770 Features 802.1Q and the Voice Gateway Media Cards The ITG-P 24-port and Media Card line cards cannot send the 802.1Q header because the cards’ operating system does not support it. The switch ports connecting the Voice Gateway Media Card’s TLAN network interface should be configured for untagged operation so if a 802.1Q header is present, it is stripped before a packet is passed to the card. The configuration in OTM and Element Manager is for the control of the priority bits in the 802.1Q header sent by the IP Phones only. Data Path Capture tool IP Line 4.0 contains the Data Path Capture tool, a built-in utility used to capture audio information. This tool helps debug audio-related gateway problems and allows after-the-fact analysis of what the user heard. The Data Path Capture process is controlled by a set of CLI commands. IP Phone firmware Minimum firmware version Refer to the ReadmeFirst documentation to determine the IP Phone minimum firmware (F/W) versions supported by IP Line 4.0. Firmware download The firmware files for the IP Phones are downloaded from OTM 2.2 or Element Manager to the node Master. They are compressed as they are stored on the node Master card’s /C: drive. File compression reduces the firmware file to less than 900 K. However, the /C: drive Flash disk space is limited on the ITG-P 24-port line card. The IP Phone normally does not have to be pre-loaded with the firmware file because, during normal operation, the IP Phone’s firmware is automatically upgraded as part of the registration to the LTPS. If the firmware cannot be upgraded, perhaps due to firewall restrictions, then the IP Phone must be upgraded with the current firmware version before distributing the IP Phone. 553-3001-365 Standard 3.00 September 2004 Features Page 131 of 770 Firmware filenames The IP Phone firmware files are released on CD-ROM. The files are also available from the Nortel Networks web site. The IP Phone firmware files are labelled as follows: • 0602Bnn.BIN is the filename for the Phase I IP Phone 2004 firmware where Bnn = F/W version 1.nn. • 0603Bnn.BIN is the filename for the Phase I IP Phone 2002 firmware where Bnn = F/W version 1.nn. • 0604Dnn.BIN is the file name for the Phase II IP Phone 2001, IP Phone 2002, and IP Phone 2004 where Dnn = F/W version 4.nn If the external file server option is used (in OTM 2.2 or Element Manager) for firmware distribution with a node, the files must be renamed before being placed on the server: • 0602Bnn.BIN must be renamed to i2004.fw • 0603Bnn.BIN must be renamed to i2002.fw • 0604Dnn.BIN must be renamed to IPP2SETS.fw For the external file server options: • see Procedure 29 on page 291 for OTM 2.2 • see Procedure 47 on page 363 for Element Manager IP Line Description, Installation, and Operation Page 132 of 770 Features Meridian 1 Default location of firmware files The firmware files for the IP Phones are stored in the C:/FW directory. The firmware files are downloaded and saved to this directory when the user checks the firmware download checkbox in the OTM Synchronize/Transmit dialog and presses the Transmit button. The IP Line application saves the firmware file for the Phase I IP Phone 2004 as i2004.fw, the firmware file for the Phase I IP Phone 2002 as i2002.fw, and the firmware file for the Phase II IP Phone 2001, IP Phone 2002, and IP Phone 2004 as IPP2SETS.fw. Then at card bootup time, if the firmware file is not retrieved from the external server or the /A: drive, the /C:/FW directory is accessed and the firmware files present in the directory are loaded into memory and uncompressed. Firmware file management with IP Line 4.0 The firmware file is stored and retrieved from the local /C:/FW directory. The IP Line 4.0 application searches for the firmware first at the file server, then in the /A:/FW directory, and finally in the /C:/FW directory. • Normally the file server is not configured in OTM 2.2. OTM 2.2 places IP address 0.0.0.0 in the CONFIG.INI file for the file server address. If an address of “0.0.0.0” (the default) is read from the file, the IP Line 4.0 application ignores the file server settings. As a result, the normal search ends with the firmware file being retrieved from the /C:/FW directory. • If a file server address is configured, the file is downloaded into the /ums directory in memory. In order for all the Voice Gateway Media Cards to get the same firmware files, it is necessary to ensure that the configured file server is up and running before any of the cards boot up. The “/A:” drive (faceplate PC Card slot) of the Voice Gateway Media Card can also be used with a PC Card containing the firmware files. The card is specified as the server and the file directory specifies the “/A:/FW” drive. 553-3001-365 Standard 3.00 September 2004 Features Page 133 of 770 Download Protocol The TFTP download mechanism is used in IP Line 4.0. The Master card notifies the Followers about changes to the status of the firmware file using a broadcast on the TLAN network interface. The UFTP download mechanism is used to download the IP Phone firmware files. Bootup Scenarios If the Master is unable to retrieve a firmware file, the upgrade policy is set as “Never”. When the upgrade policy is set to “Never”, the IP Phone’s firmware version is not checked and the IP Phone registers with the firmware version that is currently on the IP Phone. If the Master card reboots, the Election process selects another Voice Gateway Media Card as the Master. That Voice Gateway Media Card has all firmware files in its memory. When the original Master card finishes rebooting, it becomes the Master and does the normal Master start-up procedure for retrieving the firmware files. In a power-on situation, where all cards reboot together, the first card that is elected Master retrieves the firmware files from the server. CS 1000 systems Default location of firmware files For CS 1000 system configurations, the default storage location for the firmware files is on the Signaling Server in the /u/fw directory. The firmware file is downloaded to this directory, the file is selected in Element Manager, and the Transmit button is clicked. IP Line Description, Installation, and Operation Page 134 of 770 Features Firmware file management with IP Line 4.0 Due to the limited flash drive space on the Voice Gateway Media Cards, IP Line 4.0 manages the firmware file in the following manner: 1 Each IP Phone type has one firmware file. These files are saved and retrieved in one of the following two locations: a to/from a file server (The file server can be a dedicated external server, the Call Server, or a Voice Gateway Media Card.) b to/from a Master card’s RAM device 2 The server’s information is configured in Element Manager and the information is saved in the CONFIG.INI file. The server’s IP address, routing table, file path, user name, and password are specified during configuration time. 3 When the Master card boots, it searches for the firmware files on the specified server. 4 a If found, they are retrieved and stored on the RAM drive in the /ums directory. b Otherwise, i. for a Voice Gateway Media Card, the Master card continues to search for the firmware files in the local A:/fw directory and then the C:/fw directory until the files are found. ii. for a Signaling Server, the Master card attempts to search for the firmware files in the /u/fw directory, and then the /A:/fw directory. When a Follower card boots, it looks for the firmware files on the Master card’s RAM drive in the /ums directory. If the Master has not yet retrieved the files, the Follower waits until the Master sends notification that the firmware files are retrieved. Using FTP, the Follower transfers the files from the Master and stores them in the /ums directory on its RAM drive. 553-3001-365 Standard 3.00 September 2004 Features Page 135 of 770 5 Once a firmware file is found and stored in the card’s RAM drive, the upgrade manager parses the file and updates its policy based on the firmware version it received from file. 6 The IP Phones are checked against the upgrade policy at the time they register. If a firmware update is required, the firmware is downloaded from the Signaling Server or the Voice Gateway Media Card’s TFTP server to the IP Phone. The firmware file for the Phase I IP Phone 2004 is saved as i2004.fw, as i2002.fw for the Phase I IP Phone 2002, and as IPP2SETS.fw for the Phase II IP Phone 2001, IP Phone 2002, and IP Phone 2004. These filenames are required for the upgrade manager to find certain files in either the stand-alone file server or the Master card’s RAM drive. In order for all Voice Gateway Media Cards to obtain the same firmware files, ensure that the configured file server is running before any of the Voice Gateway Media Cards boot up. In CS 1000 systems, the Signaling Server acts as the file server and the Master function is on the Signaling Server. As a result, no time to download the firmware files from the file server is needed. The /A: drive (the PC Card slot on the card’s faceplate) of the Voice Gateway Media Card can also be used with a PC Card containing the firmware files; the Voice Gateway Media Card is specified as the server and the file directory specifies the /A: drive. Graceful Disable The DISI command in LD 32 can be used to disable the Voice Gateway Media Card’s gateway channels when they become idle. This command removes gateway call traffic from a Voice Gateway Media Card; however, it does not remove the IP Phones registered to the Voice Gateway Media Card. Even after the gateway channels are disabled, all IP Phones registered to the card are impacted when the card is unplugged or reset. Also, if a Voice Gateway Media Card or Signaling Server is the node Master when it is removed, the IP Phone registration service is interrupted until the next election occurs. IP Line Description, Installation, and Operation Page 136 of 770 Features To overcome these problems, the Graceful TPS enhancement provides a card-level CLI command that disables the LTPS service on the Voice Gateway Media Card or Signaling Server. The Graceful TPS command: • prevents new IP Phones from registering • soft-resets any idle, registered IP Phones Since the LTPS does not accept new registrations, the IP Phones register with another card’s LTPS after the reset. Eventually, all IP Phones are registered with other TPSs and the card can be removed without impact to any users. Operation of the LTPS DISI The Graceful TPS Disable is controlled from the CLI of the card. When the disiTPS command is executed on the card’s LTPS, the following occurs: 553-3001-365 • The card does not accept any new registration requests. • The card soft-resets all registered IP Phones that are in the idle state and redirects the IP Phones to the node Master. Standard 3.00 September 2004 Features Page 137 of 770 • The card soft resets the remaining busy registered IP Phones after they release their active call. • If the card is node Master, an election is held to transfer the mastership. This occurs only on the Voice Gateway Media Card. The Signaling Server’s node mastership is not transferred. IMPORTANT! When only the disiTPS command is entered on a Signaling Server and the mastership remains with that Signaling Server, then IP Phones can re-register to both Voice Gateway Media Cards and another Signaling Server in the node. To ensure that the IP Phones re-register only to the secondary Signaling Server, Nortel Networks recommends that the command disableServices be used on the Signaling Server instead of disiTPS. Using the disiTPS command alone on the on the Signaling Server is not recommended. Alternatively, the vtrkShutdown command followed by the disiTPS can be entered. Feature operation of the Voice Gateway DISI The Voice Gateway can also be disabled from the CLI of a Voice Gateway Media Card. When the disiVGW command is executed, the following happens on that card’s Voice Gateway: • Idle gateway channels are unregistered. • A busy gateway channel is unregistered when it becomes idle. IP Line Description, Installation, and Operation Page 138 of 770 Features Note: Care should be taken with this command to avoid a potential problem when calls are placed on hold. When an IP Phone has a call on hold, the voice gateway channel on the card is idle; however, it is still reserved in the Call Server. If the voice gateway is still disabled when the call is taken off hold, the call does not have a speech path. Recommendation Nortel Networks recommends that the LD 32 DISI command be used for disabling the gateway channels. Hardware watchdog timer A hardware watchdog timer is enabled on the ITG-P 24-port and Media Card line cards. This functionality adds further robustness to the existing exception handler and maintenance task audits. The hardware watchdog timer handles scenarios such as the following: • the CPU failing • the code running and not triggering an exception • resetting the card and bringing it back to normal operation The timer runs on the ITG-P 24-port and Media Card line card processors. The card’s main processor is polled every 20 seconds. If three pollings are missed, then the card is reset. This gives the main processor 60 seconds to respond, covering most normal operating conditions. A reset reason is logged and saved when a card resets. The reset reason is displayed as a message during the start-up sequence and appears in the SYSLOG file. The following are examples of reset reasons: • 553-3001-365 JAN 04 12:17:45 tXA: Info Last Reset Reason: Reboot command issued Output after card reset using the CLI command cardReboot. Standard 3.00 September 2004 Features Page 139 of 770 • JAN 04 12:17:45 tXA: Info Last Reset Reason: Watchdog Timer Expired Output after card reset due to watchdog timer expiration. • JAN 04 12:17:45 tXA: Info Last Reset Reason: Manual reset Output after card reset due to either the faceplate reset button press or a power cycle to the card. • JAN 04 12:17:45 tXA: Info Last Reset Reason: Unknown Output after card reset due either the card F/W not supporting the reset reason or a corruption of the reset reason code. The last reset reason can also be displayed at any time by entering the lastResetReason CLI command. Watchdog Timer and Voice Gateway Media Card firmware The application starts the Watchdog Timer as part of the application start-up process. The timer is started only if the application’s check of the firmware version indicates the card’s firmware supports the Watchdog Timer function. Required Voice Gateway Media Card firmware version A firmware upgrade can be required on the Voice Gateway Media Cards to invoke the Watchdog Time functionality: • ITG-P 24-port line card – Version 5.3 of the firmware file is the required minimum to enable the Watchdog Timer functionality on the ITG-P 24-port line card. To upgrade the firmware version of the ITG-P 24-port line card to support the Watchdog functionality, see Procedure 99 on page 639. • Media Card – Version 6.0 of the firmware file is the required minimum to enable the Watchdog Timer functionality on the Media Card line cards. To upgrade the firmware version of the Media Card line cards to support the Watchdog functionality, see Procedure 100 on page 642. IP Line Description, Installation, and Operation Page 140 of 770 Features Codecs Codec refers to the voice coding and compression algorithm used by the DSPs on the Voice Gateway Media Card. Different codecs provide different levels of voice quality and compression properties. The specific codecs and the order in which they are used are configured on the LTPS and CS 1000 and Meridian 1. Table 34 shows which codecs are supported on the systems. Table 34 Supported codecs Codec Payload size G.711 a-law, G.711 mu-law, NOVAD 10, 20, and 30 ms G.729A 10, 20, 30, 40, and 50 ms G.729AB 10, 20, 30, 40, and 50 ms G.723.1 1 30 ms T.38 2 supported for fax calls on gateway channels G.711 Clear Channel 2 supported for fax calls on gateway channels Note 1: The G.723.1 codec has bit rates of 5.3 Kbps and 6.3 Kbps. In IP Line 4.0, The G.723.1 codec can only be configured with a 5.3 Kbps bit rate; however, the system accepts both G.723.1 5.3Kbps and 6.4Kbps from the far end. Note 2: T.38 is the preferred codec type for fax calls over virtual trunks. However, the G.711 Clear Channel codec is used if the far end does not support the T.38 codec. For detailed information about codecs, refer to “Codecs” on page 179. Set type checking and blocking If the registration is a regular request (not a Virtual Office login), the Call Server checks the configured TN type against the actual IP Phone type. If the set types don’t match, the registration is blocked. 553-3001-365 Standard 3.00 September 2004 Features Page 141 of 770 However, if the registration request is a virtual login, this check is not performed. All IP Phones are allowed to be registered onto any IP TN type when the login is through Virtual Office. Special checking on the DN/ Feature keys is performed when an IP Phone 2004 or IP Softphone 2050 user logs in from an IP Phone 2002, or when an IP Phone 2004, IP Phone 2002, or IP Softphone 2050 user logs in from an IP Phone 2001. Special checking is required to prevent a user from logging in from an IP Phone that cannot display an incoming call because the IP Phone used to log in does not have the DN/Feature key(s) to display the incoming call. If the login were allowed to occur, the IP Phone could ring without providing the user a way to answer the call. The configuration of the logging-in user is examined for DN/Feature key types that receive incoming calls. If DN/Feature key types appear on any keys not present on the type of IP Phone being used for the login, the login is blocked. Note: The login from an IP Phone 2002 is blocked for users configured for ACD. IP Phone 2002 login restrictions Because the IP Phone 2002 supports only 4 feature keys, a restricted VO login is applied to IP Phone 2004 and IP Softphone 2050 TNs when they log in using an IP Phone 2002. When the IP Phone 2004 or IP Softphone 2050 user logs in from an IP Phone 2002, the login is blocked if the user’s configuration has one of the following: • key 0 defined as ACD • any key from key 4 to key 15 defined as AAK, CWT, DIG, DPU, GPU, ICF, MCN, MCR, MSB, PVN, PVR, SCR or SCN IP Phone 2001 login restrictions Because the IP Phone 2001 does not support any feature keys, a restricted VO login is applied to IP Phone 2002, IP Phone 2004, and IP Softphone 2050 TNs when they log in using an IP Phone 2001. When an IP Phone 2002, IP Phone IP Line Description, Installation, and Operation Page 142 of 770 Features 2004, or IP SoftPhone 2050 user logs in from an IP Phone 2001, the login is blocked if the user’s configuration has one of the following: • key 0 defined as ACD • any other key (from key 1 to key 15) defined as AAK, CWT, DIG, DPU, GPU, ICF, MCN, MCR, MSB, PVN, PVR, SCR or SCN. Enhanced Redundancy for IP Line nodes The Enhanced Redundancy for IP Line nodes feature relaxes the checking performed by a node on the Node ID that is presented by a registering IP Phone. Under the circumstances described in this section, an IP Phone with a 3-digit Node ID can register to a node that is configured with a 4-digit Node ID. To enable the registration to be successful, the 3-digit Node ID must match the first 3 digits of the node’s 4-digit Node ID. This feature enhances the IP Phone’s survivability in the case of network outages or equipment failure, as it allows an IP Phone to register to more than one node on a system. By configuring the IP Phone’s S1 and S2 Connect Server IP addresses to the node addressees of two different nodes, and properly configuring the Node IDs, the IP Phone is able to register to another secondary node if it cannot register to the primary node. The rules are as follows: • if the Node ID on the system has 3 digits or less, the Node ID from the IP Phone must match exactly • if the Node ID on the system has 4 digits and: — the Node ID from the IP Phone has fewer than 3 digits, reject the registration — the Node ID from the IP Phone has 4 digits, the Node ID must match exactly — if the Node ID from the IP Phone has 3 digits and they match the first 3 digits of the node's 4 digit Node ID (left to right), then allow the IP Phone to register. If the first three digits do not match, reject the registration. 553-3001-365 Standard 3.00 September 2004 Features Page 143 of 770 Up to 10 nodes can be configured on a system (3-digit Node ID base + 0-9 for the fourth digit). The IP Phones are distributed among the nodes by programming different S1 and S2 IP addresses into the IP Phones. The IP Phones register to the primary Connect Server (the S1 IP address) if possible. If a network outage or equipment failure prevents the registration to the primary Connect Server, the IP Phone can register to a secondary Connect Server (the S2 IP address). This feature enables a node’s registered IP Phones to spread across the spare IP Phone registration capacity of the other nodes in the system in the event of a network outage or equipment failure. Example: For example, the installer configures two nodes on a system with Node IDs 3431 and 3432. An IP Phone configured with Node ID 343 can register with either node. If the IP Phone presented one of the following Node IDs, it would be rejected for registration • 3 • 34 • 3433 The TN must still match before the IP Phone is allowed to register. If the customer does not want to use the Enhanced Redundancy for IP Line Nodes feature, programming 2- or 4-digit Node IDs retains the “exact match” requirement. IP Line Description, Installation, and Operation Page 144 of 770 553-3001-365 Features Standard 3.00 September 2004 178 Page 145 of 770 Personal Directory, Callers List, and Redial List Contents This section contains information on the following topics: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Virtual Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Media Gateway 1000B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User key for Personal Directory, Callers List, and Redial List . . . . 146 147 148 148 Personal Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Callers List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call log options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 150 Redial List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 IP Phone Application Server configuration and administration . . . . . . 152 Configure the IP Phone Application Server and remote backup . . . 153 Configure IP Phone Application Server on a separate Signaling Server. . . . . . 156 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 IP Phone Application Server database maintenance . . . . . . . . . . . . . . . IP Phone Application Server database backup. . . . . . . . . . . . . . . . . Full database recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selective database recovery for a single user . . . . . . . . . . . . . . . . . . Fault clearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 160 162 165 168 Call Server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Password administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initial password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 169 IP Line Description, Installation, and Operation Page 146 of 770 Personal Directory, Callers List, and Redial List Password guessing protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Forgotten password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 171 User profile management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User profile management in Element Manager . . . . . . . . . . . . . . . . 171 172 Introduction Personal Directory, Callers List, and Redial List are supported on the IP Phone 2002, IP Phone 2004, IP Softphone 2050, and Mobile Voice Client (MVC) 2050. The IP Phone 2001 is not supported. An IP Phone must be registered to a Signaling Server to access the Personal Directory, Callers List, and Redial List features. The IP Phone Application Server ELAN interface IP address must be configured (see “IP Phone Application Server configuration and administration” on page 152). IMPORTANT! CPND must be configured as a Class of Service on the system to enable Personal Directory, Callers List, and Redial List. Personal Directory is controlled by the user, who can enter or copy names to their personal directory, delete entries, or delete the entire list. Callers List and Redial List are call log features. The content of these lists is generated during call processing. CPND must be configured as a Class of Service to generate the names in the logs. Content cannot be changed; however, a user can delete or, in some cases, copy entries or lists. Note: Personal Directory is not a call log feature. 553-3001-365 Standard 3.00 September 2004 Personal Directory, Callers List, and Redial List Page 147 of 770 Table 35 compares the Personal Directory with the Callers List and Redial List features. Table 35 Comparison of Personal Directory with Callers List and Redial List Operation Personal Directory Callers List and Redial List Displays date and time of transaction No Yes Modify entry Yes No Dial from the list Yes Yes Delete entry Yes Yes Content view mode (IP Phone 2002 and IP Phone 2004 displays name and DN simultaneously; IP Phone 2002 displays only DN) Yes Yes Delete list Yes Yes Edit and dial (Temporarily modify an entry and dial out. Does not modify record in database.) No Yes Access through soft keys No No Maximum number of entries 100 20 (Redial List) 100 (Callers List) Virtual Office Personal Directory, Callers List, and Redial List are available when using Virtual Office (VO). Data is stored on the Signaling Server, not on the IP Phone. This means when a user logs on using Virtual Office or logs on in a branch office in normal mode, they can always access their stored names and numbers. IP Line Description, Installation, and Operation Page 148 of 770 Personal Directory, Callers List, and Redial List Media Gateway 1000B Personal Directory, Callers List, and Redial List are supported in a branch office configuration when the Media Gateway (MG) 1000B in the branch office location is in normal mode. Personal Directory, Callers List, and Redial List are not available in local mode, as the entries are stored on the main office Signaling Server. User key for Personal Directory, Callers List, and Redial List An IP Phone’s Private Network Identifier (PNI) + Home Location Code (HLOC) + primary DN (PDN) are used as the lookup key for the IP Phone’s Personal Directory, Callers List, and Redial List data. For the HLOC, if a CLID table entry exists (CLID = yes in LD 15) for the Primary DN (PDN) or the first non-ACD key DN, the CLID table’s HLOC is used. When no CLID entry exists, the HLOC defined in LD 15’s Network Data section is used (it might be 0's if HLOC is not configured). The PNI ensures the HLOC + PDN is unique across customers on a system if the system is multi-customer. Since the user’s PDN and HLOC are used, then to identify a specific user, a user’s primary DN and HLOC must be unique to the network to support their own specific Personal Directory, Callers List, and Redial List. If using Multiple Appearance DN (MADN) for a group of users and it is necessary to provide users with their own Personal Directory, Callers List, and Redial List, do not configure the Primary DN (PDN) as MADN. If the MADN is used as the PDN for a group of users, this results in a shared Personal Directory, Callers List, and Redial List. This means that a call arriving on any IP Phone sharing the PDN MADN appears in the Callers List. Calls to a secondary DN on another IP Phone in the shared group appear in the Callers List for all IP Phones, even though the call did not ring on the other IP Phone. 553-3001-365 Standard 3.00 September 2004 Personal Directory, Callers List, and Redial List Page 149 of 770 Personal Directory Personal Directory supports the following features: • maximum entries = 100 • maximum characters in name = 24 • maximum characters in DN = 31 • multiple actions: — add new entry — edit entry — delete entry — delete contents of directory — copy an entry from Personal Directory to Personal Directory — copy an entry from Corporate Directory to Personal Directory — dial DN of an entry — name search • password protection to control access to Personal Directory • one minute time-out Callers List Callers List supports the following features: • maximum entries = 100 • maximum characters in name = 24 • maximum characters in DN = 31 • multiple actions: — dial DN of an entry — edit entry — copy entry IP Line Description, Installation, and Operation Page 150 of 770 Personal Directory, Callers List, and Redial List — delete entry • sorted by the time the call is logged • contains caller name, DN, time of last call occurrence, and how many times the caller has called this user • Idle Display option: display and count all calls or only unanswered calls • displays caller name (Redial List only displays caller DN) • once 100 entry limit is reached, newest entry overwrites oldest entry • one minute time-out Call log options Call log options allows a user to configure preferences on the IP Phone for the following: • if the Callers List logs all incoming calls or only unanswered calls • if Idle Set Display indicates when new calls have been logged to the Callers List • if a name stored in the Personal Directory that is associated with the incoming call’s DN is displayed instead of the name transmitted by the Call Server • what three area codes should be displayed after the DN rather than before it (for example, local area codes) Follow the steps in Procedure 1 to access the call log options for the IP Phone. Procedure 1 Accessing the call log options 1 Press the IP Phone’s Services key. The Telephone Options menu displays. 2 From the Telephone Options menu, select Call Log Options. 3 Select the desired options. End of Procedure 553-3001-365 Standard 3.00 September 2004 Personal Directory, Callers List, and Redial List Page 151 of 770 Table 36 summarizes the call log options. Table 36 Call log options Call log option Description Default value Log all/unanswered incoming calls Configures the Callers List to log all incoming calls or only the unanswered incoming calls Log all calls New Call Indication When New Call Indication is turned on, a message is displayed on the IP Phone to inform the user of a new incoming call. If not configured, nothing is displayed. On Preferred Name Match Configures whether the caller name displayed is the CPND from the Call Server or the name associated with the DN stored in the Personal Directory CPND from the Call Server is displayed Area code set-up Configures how the incoming DN is displayed. If the area code of the incoming call matches a specified area code, the DN is displayed in the configured manner (for example, the area code may be displayed after the DN) No area code Name display format Configures the format of the name display of the incoming call on the IP Phone. (see note) There are two choices: Note: The IP Phone 2002 does not display the New Call Indication on the idle screen at the same time as the date and time. Instead, the New Call Indication alternates with the date and time display. IP Line Description, Installation, and Operation Page 152 of 770 Personal Directory, Callers List, and Redial List Redial List Redial List supports the following features: • maximum entries = 20 • maximum characters in name = 24 • maximum characters in DN = 31 • contains name, DN, and the time the last call to that DN occurred in each entry • newest entry overwrites oldest entry once 20-entry limit is reached • sort by the time the call is logged • multiple actions: — dial DN of an entry — edit entry — copy entry — delete entry — delete contents of list • one minute time-out IP Phone Application Server configuration and administration The IP Phone Application Server runs on the Signaling Server. If less than 1000 users are supported, then the IP Phone Application Server can run on the same Signaling Server as Element Manager. If more than 1000 users are supported, then the IP Phone Application Server must run on a separate Signaling Server (preferably a Follower) with no co-located applications. Therefore, it is necessary to configure in Element Manager the ELAN interface IP address of the specific Signaling Server where the IP Phone Application Server is installed. Note: The IP Phone Application Server can be shared across multiple IP Telephony nodes on the same Call Server. 553-3001-365 Standard 3.00 September 2004 Personal Directory, Callers List, and Redial List Page 153 of 770 Configure the IP Phone Application Server and remote backup Note: If the IP Phone Application Server must support more than 1000 users, refer to “Configure IP Phone Application Server on a separate Signaling Server” on page 156. The IP Phone Application Server and remote backup configuration are configured in Element Manager by clicking (in the navigation tree) Configuration > IP Telephony > Personal Directories Server Configuration. See Figure 19. Figure 19 Personal Directory Server Configuration Since a backup and restore of the IP Phone Application Server’s database can be performed, it is necessary to configure information to support the backup/restore functionality. The following parameters are configured (see Figure 20 on page 154): • ELAN interface IP address of the IP Phone Application Server where the database is located • checkbox to turn on/off the remote backup functionality • IP address of the server where the backup is saved • path, filename, user ID, and password to support the backup/restore functionality IP Line Description, Installation, and Operation Page 154 of 770 Personal Directory, Callers List, and Redial List Figure 20 Personal Directories Server Configuration window 553-3001-365 Standard 3.00 September 2004 Personal Directory, Callers List, and Redial List Page 155 of 770 Table 37 provides a sample IP Phone Application Server configuration. Table 37 Sample IP Phone Application Server configuration Data field name Example Description 92.168.10.12 IP address of the database server (for example, the Leader Signaling Server’s ELAN network interface IP address) Perform scheduled remote backup Checkbox is selected Select checkbox to enable scheduled remote backups. Remote backup time of day (hh:mm) 00:00 the time of day to perform the backup (default is 00:00 midnight) Remote backup IP address 47.11.22.11 remote backup server’s IP address Remote backup path /auto/etherset remote path where the back up file will be saved Remote backup file name ipldb.db file name of the backup file Remote backup userid etherset login name for the remote backup Remote backup password etherset password for remote backup Server Configuration Server IP Address Backup Configuration The Personal Directory, Callers List, and Redial List features are not available to the user if the Voice Gateway Media Cards to which the IP Phones are registered lose contact with the Signaling Server. The features become available again when contact with the Signaling Server is re-established. IP Line Description, Installation, and Operation Page 156 of 770 Personal Directory, Callers List, and Redial List Note: In a node composed of Voice Gateway Media Cards and Signaling Server(s), IP Phones only register to the Voice Gateway Media Cards when the Signaling Server(s) are not present due to a failure condition. Five minutes after a node election is completed, each Voice Gateway Media Card with IP Phones registered to it checks to see if a Signaling Server is present in the node. If a Signaling Server is present, any idle IP Phones that are found are reset (server-switched) back to S1 (Server 1) so they can re-register to the Signaling Server. If an IP Phone is busy, a one-minute timer is started. Every one minute, the process comes back to check for idle IP Phones and idle phones are reset. This checking continues until no IP Phones remain registered to the Voice Gateway Media Cards. Configure IP Phone Application Server on a separate Signaling Server If the IP Phone Application Server must support more than 1000 users, follow the steps in Procedure 2 on page 157 to configure the IP Phone Application Server on a separate Signaling Server. 553-3001-365 Standard 3.00 September 2004 Personal Directory, Callers List, and Redial List Page 157 of 770 Procedure 2 Configuring the IP Phone Application Server on a separate Signaling Server 1 In Element Manager, configure a new node. Enter a unique Node ID in the New Node field. Click the to Add button. See Figure 21. 2 Configure the IP addresses and subnet masks for the Signaling Server. 3 Configure the IP Phone Application Server using the ELAN address of the new Signaling Server. Figure 21 Add a new node Click Configuration > IP Telephony > Personal Directories Server Configuration. See Figure 22 on page 158. IP Line Description, Installation, and Operation Page 158 of 770 Personal Directory, Callers List, and Redial List Figure 22 Personal Directory Server Configuration 4 553-3001-365 Configure the backup parameters for Personal Directory, Callers List, and Redial List and click Submit. See Figure 23 on page 159. Refer to Table 37 on page 155 for more information. Standard 3.00 September 2004 Personal Directory, Callers List, and Redial List Page 159 of 770 Figure 23 Personal Directories Server Configuration window 5 Reboot the Signaling Server that was configured as the IP Phone Application Server. 6 When the Signaling Server comes back online, reset all the IP Phones by performing isetResetAll on every LTPS in the system. See Table 74 on page 595 for more information. End of Procedure Alarms If the IP Phone Application Server is not installed on the primary Signaling Server, and the other Signaling Server(s) cannot contact the IP Phone IP Line Description, Installation, and Operation Page 160 of 770 Personal Directory, Callers List, and Redial List Application Server, then an SNMP alarm is raised. The alarm indicates that the Personal Directory, Callers List, and Redial List are not available. If this occurs, the other Signaling Server(s) track the Signaling Server where the IP Phone Application Server resides. When contact with the IP Phone Application Server is made, Personal Directory, Callers List, and Redial List access is resumed. IP Phone Application Server database maintenance All IP Phone Application Server database maintenance is performed in Element Manager. Backup can be configured to occur daily at a scheduled time. Database recovery can be performed for the entire database of the IP Phone Application Server or for one user’s entries. IP Phone Application Server database backup Follow the steps in Procedure 3 to perform a manual backup of the IP Phone Application Server’s database. Note: A scheduled backup of the database can also be configured. Refer to “Configure the IP Phone Application Server and remote backup” on page 153. Procedure 3 Backing up the IP Phone Application Server database Server manually 1 Click System Utility > IP Telephony. The IP Telephony System Utility window opens. See Figure 24 on page 161. 553-3001-365 Standard 3.00 September 2004 Personal Directory, Callers List, and Redial List Page 161 of 770 Figure 24 IP Telephony System Utility window 2 Click Personal Directories Backup. The Personal Directories Backup window opens. See Figure 25 on page 162. IP Line Description, Installation, and Operation Page 162 of 770 Personal Directory, Callers List, and Redial List Figure 25 Personal Directories Backup window 3 Enter the data for the Remote backup IP address, Remote backup userid, Remote backup password, Remote backup path, and Remote backup file name fields. 4 Click Submit. End of Procedure Full database recovery Follow the steps in Procedure 4 on page 163 to perform a full database backup for the IP Phone Application Server. 553-3001-365 Standard 3.00 September 2004 Personal Directory, Callers List, and Redial List Page 163 of 770 Procedure 4 Performing a full database recovery 1 Click System Utility > IP Telephony. The IP Telephony System Utility window opens. See Figure 26. Figure 26 IP Telephony System Utility window 2 Click Personal Directories Restore. The Personal Directories Restore window opens. See Figure 27 on page 164. IP Line Description, Installation, and Operation Page 164 of 770 Personal Directory, Callers List, and Redial List Figure 27 Personal Directories Restore window 3 From the Action drop-down list, select FTP from Remote Site if the backup is save on a remote server. If the backup is saved locally, go to Step 7. 4 Enter the data for the Remote backup IP address, Remote backup userid, Remote backup password, Remote backup path, and Remote backup file name fields. 5 Click Submit. After the file is transferred by FTP to the local drive, a Switch-over button appears. 6 553-3001-365 Click the Switch-over button. Standard 3.00 September 2004 Personal Directory, Callers List, and Redial List 7 Page 165 of 770 If the backup is saved locally, select Restore All Users from the Action drop-down list and click Submit. End of Procedure Note: When switch-over occurs, the database is off-line for approximately two minutes. Selective database recovery for a single user Follow the steps in Procedure 5 to perform a database recovery for a single user. The procedure cannot be performed unless there is a valid backup file. Procedure 5 Performing a selective database recovery 1 Click System Utility > IP Telephony. The IP Telephony System Utility window opens. See Figure 28. Figure 28 IP Telephony System Utility window IP Line Description, Installation, and Operation Page 166 of 770 Personal Directory, Callers List, and Redial List 2 Click Personal Directories Restore. The Personal Directories Restore window opens. See Figure 29. Figure 29 Personal Directories Restore window 3 From the Action drop-down list, select Restore Single User. The Personal Directories Restore window for a single user opens. See Figure 30 on page 167. 553-3001-365 Standard 3.00 September 2004 Personal Directory, Callers List, and Redial List Page 167 of 770 Figure 30 Personal Directories Restore for a single user window 4 Enter the Customer Number and DN of the user. 5 Select the check box(es) of the data that is to be restored. 6 Click Submit. End of Procedure IP Line Description, Installation, and Operation Page 168 of 770 Personal Directory, Callers List, and Redial List Fault clearance The recovery of the database clears any faults. Recommendation Nortel Networks recommends that the IP Phone Application Server be installed on a dedicated Signaling Server to ensure that database operations do not affect call processing. Call Server configuration To provide password protection for an IP Phone user’s Personal Directory, Callers List, and Redial List, Station Control Password (SCPW) must be configured on the Call Server. If SCPW is not configured, password administration on the IP Phone cannot be accessed. In LD 15 and in Element Manager, a new prompt, DFLT_SCPW, has been added to the Flexible Feature Code (FFC) parameters for the Call Server. When DFLT_SCPW is set to YES, the system assigns a default password (the primary DN) to IP Phone users when an IP Phone is added or changed in LD 11. IMPORTANT! System administrators must ensure that users change the default password on the IP Phone to control access, as the default password is the same on all IP Phones when DFLT_SCPW is set to YES. The new prompt DFLT_SCPW and the existing prompt Station Control Password Length (SCPL) are prompted only if FFC package 139 is enabled. The SCPL is also defined in LD 15’s Flexible Feature Code (FFC) configuration parameters and in Element Manager. If the SCPL length is changed, the change takes effect only after a data dump and then a sysload of the Call Server. The SCPL is changed to the new length during the sysload. If the length has been increased, then “0” is inserted at the beginning of the 553-3001-365 Standard 3.00 September 2004 Personal Directory, Callers List, and Redial List Page 169 of 770 SCPW to conform to the new length. If the password length has been reduced, then the leading digits are removed during the sysload. Password administration The Station Control Password (SCPW) controls access to the user’s private Personal Directory, Callers List, and Redial List information. When the IP Phone first registers to the system after it has been created, by default the password protection is turned off. If a default password has been defined for the user, then the user can enable or disable password protection and change the password. The changed password is updated on the Call Server and can be viewed in LD 20. Other applications that use this password, such as Virtual Office and Remote Call Forward, are affected by the password change. Initial password When an IP Phone first registers with the system, by default the password protection is turned off. SCPW must be initially configured for each user. If no SCPW has been defined, password protection for the IP Phone cannot be enabled. The prompt DFLT_SCPW in LD 15 specifies that a default SCPW is assigned to an IP Phone user when an IP Phone is added or changed in LD 11. See Table 38. Table 38 LD 15 – Enable a default SCPW. (Part 1 of 2) Prompt Response Description REQ: CHG Change existing data. TYPE: FFC Change Flexible Feature Code parameters. CUST Customer number 0 – 99 Range for Large System and CS 1000E system 0 – 31 Range for CS 1000M Small System, Meridian 1 Small System, CS 1000S system, Media Gateway 1000B, and Media Gateway 1000T IP Line Description, Installation, and Operation Page 170 of 770 Personal Directory, Callers List, and Redial List Table 38 LD 15 – Enable a default SCPW. (Part 2 of 2) Prompt Response Description FFCS (NO) YES Change Flexible Feature Code end-of dialing indicator. ADLD (0) – 20 Auto Dial Delay (in seconds) DFLT_SCPW (NO) YES Default Station Control Password ... NO = disable Default Station Control Password (default) When DFLT_SCPW = YES, the system automatically assigns an SCPW when a new IP Phone 2002, IP Phone 2004, or IP Softphone 2050 is created. Note: An SCPW is not automatically assigned to an existing IP phone unless that IP Phone is given a service change. Password guessing protection A password retry counter tracks how many incorrect password entries are made. If the IP Phone password verification fails three times in one hour, then the user is locked out for one hour. This means that the Personal Directory, Callers List, and Redial List cannot be accessed and no password administration can be performed. A message displays on the IP Phone to indicate that access is locked. After one hour, the retry counter is reset and access is unlocked. The retry counter also resets when the password is entered correctly. The administrator can reset the counter and unlock the access either in Element Manager or in LD 32. 553-3001-365 Standard 3.00 September 2004 Personal Directory, Callers List, and Redial List Page 171 of 770 Note: If a user is locked out from using their SCPW to access their Personal Directory, Callers List, and Redial List, then the user is also blocked from accessing their Virtual Office login, since VO uses the same SCPW. Conversely, a user who is locked out from the VO login is also locked out from accessing their Personal Directory, Callers List, and Redial List. Forgotten password If the user forgets his or her IP Phone password, the administrator can reset the retry counter and change the user’s password in Element Manager. Once the administrator changes the password, the lock is released automatically. User profile management The User Profile screen(s) in Element Manager are used to perform all administer-related maintenance functions for a user. These functions include: • erasing databases for a user • viewing a user profile • resetting the password Once a user profile is selected, a user identification number (ESN+DN) must be entered to retrieve a user profile from the datbase.When a user profile has been retrieved from the database, an administrator can perform the following functions: • move/copy the following to another user: — user profile — Personal Directory — Callers List — Redial List • delete Personal Directory • delete Callers List • delete Redial List IP Line Description, Installation, and Operation Page 172 of 770 Personal Directory, Callers List, and Redial List • delete user preferences • delete all user-related databases • reset user’s SCPW to the default • unlock the user’s SCPW Note: If a user’s Personal Directory, Callers List, Redial List, and User Preferences are all removed individually, this has the same effect as selecting the “Delete all user-related databases” option. Either way, all the data related to that user is deleted from the database. The user’s entry must be recreated the next time the user tries to access his or her Personal Directory, Callers List, and Redial List. User profile management in Element Manager To access the user profile management functionality in Element Manager, follow the steps in Procedure 6. Procedure 6 Accessing User Profile Management in Element Manager 1 Select Configuration > IP Telephony in the Element Manager navigation tree. The IP Telephony Configuration window opens. See Figure 31. Figure 31 IP Telephony Configuration window 553-3001-365 Standard 3.00 September 2004 Personal Directory, Callers List, and Redial List 2 Page 173 of 770 Click the Personal Directories User Profile link. The Personal Directories User Profile Configuration window opens. 3 From the drop-down list, select the desired action. End of Procedure Reset the IP Phone user password To reset the password for an IP Phone user, follow the steps in Procedure 7. Procedure 7 Resetting the IP Phone user password 1 Select Reset Station Control Password from the drop-down list from the drop-down list in the Personal Directories User Profile Configuration window. The Reset Station Control Password window opens. See Figure 32 on page 174. IP Line Description, Installation, and Operation Page 174 of 770 Personal Directory, Callers List, and Redial List Figure 32 Reset password window 2 Enter the User ID. 3 Click Submit or click Cancel to cancel the action. End of Procedure Copy a Personal Directory to another user To copy a user’s Personal Directory to another user, follow the steps in Procedure 8 on page 175. 553-3001-365 Standard 3.00 September 2004 Personal Directory, Callers List, and Redial List Page 175 of 770 Procedure 8 Copying a Personal Directory to another user 1 Select Copy Personal Directories from the drop-down list from the drop-down list in the Personal Directories User Profile Configuration window. The Copy Personal Directories window opens. See Figure 33. Figure 33 Copy Personal Directories window 2 Enter the User ID of the user from which the Personal Directory is being copied and the User ID of the user who will receive the Personal Directory copy. 3 Click Submit. Click Cancel to cancel the action. End of Procedure IP Line Description, Installation, and Operation Page 176 of 770 Personal Directory, Callers List, and Redial List Delete a Personal Directory, Callers List, Redial List, or user preferences To delete a Personal Directory, Redial List, Callers List, or User Preferences, follow the steps in Procedure 9. Procedure 9 Deleting a Personal Directory, Callers List, Redial List, or user preferences 1 Select Delete Personal Directories from the drop-down list from the drop-down list in the Personal Directories User Profile Configuration window. The Delete Personal Directories window opens. See Figure 34. Figure 34 Delete Personal Directories window 2 553-3001-365 Select the item or items to be deleted. Standard 3.00 September 2004 Personal Directory, Callers List, and Redial List 3 Page 177 of 770 Click Submit or click Cancel to cancel the action. End of Procedure When a new user is configured on the Call Server, a user profile can be copied to create the new user profile. If a new IP Phone registers and the user is not found in the database, then the system automatically creates a user profile based on default settings and the data on the IP Phone. In this case, the Personal Directory, Callers List, and Redial List are automatically created as empty lists. IP Line Description, Installation, and Operation Page 178 of 770 553-3001-365 Personal Directory, Callers List, and Redial List Standard 3.00 September 2004 194 Page 179 of 770 Codecs Contents This section contains information on the following topics: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pre-defined codec table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Codec selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 180 180 Codec configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Codec selection in OTM 2.2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Codec selection in Element Manager . . . . . . . . . . . . . . . . . . . . . . . . 182 182 183 Codec registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Codec registration for IP Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . Codec registration for DSPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Voice Gateway codec registration . . . . . . . . . . . . . . . . . . . . . . . . . . 183 184 185 187 Codec negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Codec sorting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 188 Codec selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H.323’s Master/Slave algorithm. . . . . . . . . . . . . . . . . . . . . . . . . . . . Best Bandwidth Codec Selection algorithm. . . . . . . . . . . . . . . . . . . 191 192 193 Introduction The IP Phones and Voice Gateway Media Cards support different codecs and codec parameters with different compression rates and audio quality. The CS 1000 and Meridian 1 systems select the appropriate codecs based on user-configurable parameters. IP Line Description, Installation, and Operation Page 180 of 770 Codecs For instance, an IP Phone-to-IP Phone call in the same zone within a LAN can be set up using G.711 at 64 Kbps. For an IP Phone-to-IP Phone call over a WAN, the call can be set up using G.729A or G.729AB at 8 Kbps. These data rates and the Voice Gateway Channel Server on the Voice Gateway Media Card are for the voice stream only. Packet overhead is not included. Pre-defined codec table The Line Terminal Proxy Server (LTPS) and the Voice Gateway Channel Server on the Voice Gateway Media Card have a pre-defined table of codec option sets that can be supported. The first entry in the table has the highest quality audio (BQ = Best Quality) and requires the largest amount of bandwidth. The last entry requires the least amount of bandwidth (BB = Best Bandwidth) with lower voice quality. When the Call Server sets up a Call Server connection between an IP Phone-to-IP Phone or IP Phone-to-Voice Gateway Channel Server, the pre-defined table determines which codec it selects for that connection. This information is provided to the system as part of the IP Phone registration sequence. For more information about the registration sequence, refer to “Configuring the DHCP Server” in Data Networking for Voice over IP (553-3001-160). Codec selection The systems use this information to set up a speech path and select a codec that both endpoints support. As part of zone management, the system further selects the codec based on whether it is trying to optimize quality (BQ) or bandwidth usage (BB). CAUTION When voice compression codecs are used, voice quality is impaired if end-to-end calls include multiple compressions. 553-3001-365 Standard 3.00 September 2004 Codecs Page 181 of 770 The term “codec” refers to the voice coding and compression algorithm used by the DSPs on the Voice Gateway Media Card. Different codecs provide different levels of voice quality and compression properties. The specific codecs, and the order in which they are used, are configured in the LTPS, and on the system. Table 39 shows which codecs are supported on the CS 1000 and Meridian 1 systems. Table 39 Supported codecs Codec Payload size G.711 a-law, G.711 mu-law, NOVAD 10, 20, and 30 ms G.729A 10, 20, 30, 40, and 50 ms G.729AB 10, 20, 30, 40, and 50 ms G.723.1 1 30 ms T.38 2 supported for fax calls on gateway channels G.711 Clear Channel 2 supported for fax calls on gateway channels Note 1: The G.723.1 codec has bit rates of 5.3 Kbps and 6.3 Kbps. In IP Line 4.0, the G.723.1 codec can only be configured with a 5.3 Kbps bit rate; however, the system accepts both G.723.1 5.3Kbps and 6.4Kbps from the far end. Note 2: T.38 is the preferred codec type for fax calls over virtual trunks. However, the G.711 Clear Channel codec is used if the far end does not support the T.38 codec. Note: The MVC 2050 supports only the G.711 codec with 30 ms payload. Note: If there are multiple nodes on a system and the same codec is selected on more than one node, ensure that each node has the same voice payload size configured for the codec. IP Line Description, Installation, and Operation Page 182 of 770 Codecs Codec configuration Configure the codec in the DSP Profile sections of OTM 2.2 and Element Manager. Codec selection in OTM 2.2 Figure 35 shows the list of codecs available on the DSP Profile tab within OTM’s IP Line 4.0 application. The Codec Options sub-tab presents a table of different sets of codec options identified by a codec setting index number. There is a list of up to 32 codec settings for G.711, G.729A, and G.729AB. The lesser codec setting index corresponds to BQ (Best Quality) in LD 117 zone configuration. The greater codec setting index corresponds to BB (Best Bandwidth). For more information, see Data Networking for Voice over IP (553-3001-160). Figure 35 Codec list on OTM 2.2 553-3001-365 Standard 3.00 September 2004 Codecs Page 183 of 770 For more information, see “Configure DSP profile data” on page 271. Codec selection in Element Manager Figure 36 shows the list of codec types that are displayed in Element Manager. Figure 36 Codec list in Element Manager The G.711, G.711 Clear Channel, and T.38 Fax codecs are automatically selected and cannot be un-selected. Even though these codecs cannot be un-selected, the payload size and the jitter buffer for G.711 can be changed. For G.711 Clear Channel, only the jitter buffer can be changed. Select all three, any two, any one, or none of the G.729A, G.729AB, and G.723.1 codecs. If the G.729A or G.729AB codec is selected, the payload size and the jitter buffer settings can be changed. If the G.723.1 codec is selected, only the jitter buffer can be changed, as the only supported payload size is 30 msec. For codec configuration in Element Manager, see “Configure Voice Gateway Profile data” on page 349. Codec registration After the configuration of codecs is complete, the IP Phones and DSPs have to register the configured codecs with the Call Server. IP Line Description, Installation, and Operation Page 184 of 770 Codecs Codec registration for IP Phones The IP Phones always register both the G.711 a-law and mu-law codecs, as well as all codec(s) configured by the user. The codecs that can be configured by the user are G.729A, G.729AB, and G.723.1. The minimum number of codecs registered for an IP Phone is two: G.711 a-law and G.711 mu-law (G.711 is always configured). The maximum number of codecs registered for an IP Phone is five: G.711 a-law, G.711 mu-law, G729A, G729AB, and G.723.1. Note: IP Phones do not register the fax codecs (T.38 and G.711 Clear Channel). Example 1 A user configures a G.711 mu-law codec (with a 30 msec payload) and a G.723.1 codec (with a 30 msec payload). The following three codecs are actually registered: 1 G.711 mu-law (30 msec) 2 G.711 a-law (30 msec) 3 G.723.1 (30 msec) Example 2 A user configures four codecs: 1 G.711 a-law codec with a 10 msec payload 2 G.729A codec with 50 msec payload 3 G.729AB codec with 30 msec payload 4 G.723.1 codec with a 30 msec payload The following five codecs are actually registered: 553-3001-365 1 G.711 a-law (10 msec) 2 G.711 mu-law (10 msec) Standard 3.00 September 2004 Codecs 3 G.729A (50 msec) 4 G.729AB (30 msec) 5 G.723.1 (30 msec) Page 185 of 770 Codec registration for DSPs DSPs register the following codecs: • both G.711 a-law and G.711 mu-law codecs are always registered • both fax codecs (T.38 and G.711 Clear Channel) are always registered • one best bandwidth (BB) codec, if at least one of G.729A, G.729AB, or G.723.1 codecs was configured. The BB codec is based on the codec type. The order of preference for choosing the BB codec is G.729AB, G.729A, and then G.723.1. IMPORTANT! When G.723.1 codec is configured on the Media Card 32-port line card, the number of channels is reduced to 24. This is a limitation of the DSP software. The unused channels are not registered, therefore the Call Server software does not access them Minimum codecs The minimum number of codecs registered for DSPs is four: • G.711 a-law • G.711 mu-law • T.38 • G.711 Clear Channel Maximum codecs The maximum number of codecs registered for DSPs is five: • G.711 a-law • G.711 mu-law IP Line Description, Installation, and Operation Page 186 of 770 Codecs • T.38 • G.711 Clear Channel • one of G.729AB, G.729A, or G.723.1 Example 1 A user configures four codecs: 1 G.711 a-law codec with a 10 msec payload 2 G.729A codec with 50 msec payload 3 G.729AB codec with 30 msec payload 4 G.723.1 codec with a 30 msec payload The following six codecs are actually registered: 1 G.711 a-law (10 msec) 2 G.711 mu-law (10 msec) 3 G.729AB (30 msec) 4 G.729A (50 msec) 5 T.38 6 G.711 Clear Channel The G.729AB codec is selected, as it is the first in the order of preference of the BB codecs. The G.723.1 codec does not get registered. Example 2 A user configures three codecs: 553-3001-365 1 G.711 mu-law codec with a 20 msec payload 2 G.729A codec with 30 msec payload 3 G.723.1 codec with a 30 msec payload Standard 3.00 September 2004 Codecs Page 187 of 770 The following five codecs are actually registered: 1 G.711 mu-law (20 msec) 2 G.711 a-law (20 msec) 3 G.729A (30 msec) 4 T.38 5 G.711 Clear Channel The G.729A codec is selected, as it precedes the G.723.1 codec in the order of preference of the “best bandwidth” codecs. Voice Gateway codec registration The Voice Gateway registers codecs for the gateway channels as follows: • G.711 a-law and G.711 mu-law are always registered. • T.38 and G.711 Clear Channel fax codecs are always registered. G.711 Clear Channel is used for IP Trunk connections to BCM, which does not support T.38 fax. • A minimum of two codecs are registered if only G.711 was configured. • A maximum of four codecs can be registered - the G.711 a-law and mu-law for BQ codec, and some BB codecs (defined by the following rules). — If the G.729A codec is configured, only the G.729A codec is registered with the Call Server. — If the G.729AB codec is configured, the G.729A codec and the G.729AB codec are registered with the Call Server. — If the G.723 codec is configured, the G.723 codec is registered with the Call Server. Example 1 G.711 a-law, G.729A, G.729AB, and G.723.1 are configured. The Voice Gateway registers G.711 a-law, G.711 mu-law, G.729A, and G.729AB. IP Line Description, Installation, and Operation Page 188 of 770 Codecs Example 2 G.711 mu-law, G.729A, and G.723.1 are configured. The Voice Gateway registers G.711 a-law, G.711 mu-law, and G.729A. Example 3 G.711 mu-law and G.723.1 are configured. The Voice Gateway registers G.711 a-law, G.711 mu-law, and G.723.1. Codec negotiation For every virtual trunk call, a common codec must be selected for the call. This is known as codec negotiation. Codec negotiation for virtual trunk calls is performed through the H.323 FastStart and Terminal Capability Set (TCS) messages. For a call setup with the FastStart procedure, the originating node sends its codec list in the FastStart element in the SETUP message to the terminating node. For a call setup using the SlowStart procedure or for a call modification (media redirection), each node sends its codec list in the TCS message to the other node. Codec sorting Before sending a codec list in FastStart and TCS messages, the codec list must be sorted according to the BB or BQ policy. This is determined by the following: 553-3001-365 • the zone configuration of the IP Phone/DSP involved in the call • the zone configuration of the virtual trunk used for the call Standard 3.00 September 2004 Codecs Page 189 of 770 Codec sorting methods There are two methods for sorting the codec list: 1 BQ sorting – the codec list is sorted so that the first codec in the list is the best BQ codec, the second codec is the second best BQ codec in the list, and so on. 2 BB sorting – the codec list is sorted so that the first codec in the list is the best BB codec, the second codec is the second best BB codec in the list, and so on. IP Line Description, Installation, and Operation Page 190 of 770 Codecs Table 40 shows the codec list sorting order for the BQ and BB codecs. To know if a codec is BQ (as compared to another codec), refer to the lists in columns 1 and 2. To determine if a codec is BB (as compared to another codec), refer to the lists in columns 3 and 4. The BQ or BB codec is listed at the top of the column. Table 40 BQ and BB codec sorting lists Best Quality (BQ) sorting For mu-law systems For a-law systems Best Bandwidth (BB) sorting For mu-law systems For a-law systems G.71_mu_law_10msec G.711_a_law_10msec G.729AB_50msec G.729AB_50msec G.711_mu_law_20msec G.711_a_law_20msec G.729AB_40msec G.729AB_40msec G.711_mu_law_30msec G.711_a_law_30msec G.729AB_30msec G.729AB_30msec G.711_a_law_10msec G.711_mu_law_10msec G.729AB_20msec G.729AB_20msec G.711_a_law_20msec G.711_mu_law_20msec G.729AB_10msec G.729AB_10msec G.711_a_law_30msec G.711_mu_law_30msec G.729A_50msec G.729A_50msec G.729A_10msec G.729A_10msec G.729A_40msec G.729A_40msec G.729A_20msec G.729A_20msec G.729A_30msec G.729A_30msec G.729A_30msec G.729A_30msec G.729A_20msec G.729A_20msec G.729A_40msec G.729A_40msec G.729A_10msec G.729A_10msec G.729A_50msec G.729A_50msec G.723.1_5.3kbps_30ms G.723.1_5.3kbps_30ms G.729AB_10msec G.729AB_10msec G.723.1_6.4kbps_30ms G.723.1_6.4kbps_30ms G.729AB_20msec G.729AB_20msec G.711_mu_law_30msec G.711_a_law_30msec G.729AB_30msec G.729AB_30msec G.711_mu_law_20msec G.711_a_law_20msec G.729AB_40msec G.729AB_40msec G.711_mu_law_10msec G.711_a_law_10msec G.729AB_50msec G.729AB_50msec G.711_a_law_30msec G.711_mu_law_30msec G.723.1_5.3kbps_30ms G.723.1_5.3kbps_30ms G.711_a_law_20msec G.711_mu_law_20msec G.723.1_6.4kbps_30ms G.723.1_6.4kbps_30ms G.711_a_law_10msec G.711_mu_law_10msec T.38 T.38 T.38 T.38 G.711CC G.711CC G.711CC G.711CC 553-3001-365 Standard 3.00 September 2004 Codecs Page 191 of 770 Codec selection For every virtual trunk call, a codec must be selected before the media path is opened. When a call setup with the FastStart procedure is used, the terminating node selects a common codec and sends the selected codec to the originating node. For a call modification (media redirection) or for a call setup using the SlowStart procedure, the codec selection occurs on both nodes. Each node has two codec lists: its own list and the far-end’s list. To select the same codec on both nodes, it is essential to use the same codec selection algorithm on both nodes. For the codec selection, both the near- and far-end codec lists are retrieved: • The far-end list is not modified because it is already sorted when it is received (in FastStart or TCS message). • The near-end list is sorted and then expanded to include lower payloads, the same way it is done before sending the codec list in FastStart message. The following conditions are met before codec selection occurs: • There are two codec lists: — The near-end list is the codec list of the local unit. — The far-end list is the codec list received from the far end. • Each codec list can contain more than one payload size for a given codec type. The codec list depends on the codec configuration. • Each codec list is sorted by order of preference. The first codec in the near-end list is the near-end’s most preferred codec and the first codec in far-end list is the far end’s most preferred codec, and so on. IP Line Description, Installation, and Operation Page 192 of 770 Codecs Once the above conditions are met, a codec selection algorithm is used to select the codec to be used for a call. There are two different codec selection algorithms: 1 H.323’s Master/Slave algorithm 2 Best Bandwidth codec Selection algorithm H.323’s Master/Slave algorithm The codec selection algorithm proposed by the H.323 standard involves a Master/Slave negotiation, initiated each time two nodes exchange their capabilities (TCS message). The Master/Slave information decides that one node is Master and the other node is Slave. The outcome of the Master/Slave negotiation is not known in advance, it is a random result: one node could be Master then Slave (or Slave then Master) during the same call. • The Master node uses its own codec list as the preferred one. From the far-end list, it finds the common codec. The Master gets the first codec in its own list (Codec1). The Master then checks the far-end list to see if Codec1 is a common codec (that is, is Codec1 also listed in the far-end list). If Codec1 is common to both lists, Codec1 becomes the selected codec. Otherwise, the Master obtains the second codec from its own list and repeats the search in the far-end list, and so on. • The Slave node uses the far-end list as the preferred list. The Slave selects a codec from the far-end list and then searches in its own list to find the common codec. The issues caused by the Master/Slave algorithm are due to the random nature of the Master/Slave information. The codec that is selected and used during a virtual trunk call cannot be pre-determined. This can make bandwidth usage calculations and bandwidth management difficult. 553-3001-365 Standard 3.00 September 2004 Codecs Page 193 of 770 Known issues include: • After an on-hold and off-hold scenario (that triggers Master/Slave negotiation), the codec used for the restored call can be different than the codec used before the call was placed on hold. The Master/Slave information could have been changed when the call was on hold. • Since the terminating end of a call is always the Master, a call from Telephone1 (Node1) to Telephone2 (Node2) can use a different codec than a call from Telephone2 (Node2) to Telephone1 (Node1). • For tandem calls, the Master/Slave information is not relevant. That is, the Master/Slave information is designed to be used only between two nodes, not among three or more nodes. The Master/Slave algorithm makes the codec selection for tandem calls more complex and inefficient. To solve the issues, another codec selection algorithm was needed. This algorithm is called the Best Bandwidth codec Selection algorithm and is not based on the unpredictable Master/Slave information. The Best Bandwidth codec Selection algorithm is used for virtual trunk calls between Nortel Networks equipment, since any change to the Master/Slave algorithm implies a change to the H.323 standard. The H.323’s Master/Slave algorithm is used when there is a virtual trunk call between Nortel Networks equipment and third-party equipment. Best Bandwidth Codec Selection algorithm The Best Bandwidth Codec Selection algorithm was implemented to solve the issues caused by the H.323 Master/Slave algorithm. The Best Bandwidth Codec Selection algorithm selects one common codec based on two codec lists. With this algorithm, every time the selection is done using the same two lists, the selected codec is always the same. The “Best Bandwidth” codec selection is based on the codec type only; it does not take into account the fact that some codecs, while generally using less bandwidth, consume more bandwidth than others at certain payload sizes. • The Best Bandwidth Codec Selection algorithm finds the first codec in the near-end list that is also in far-end list (codec is the same type and has the same payload size). Call the selected codec C1. IP Line Description, Installation, and Operation Page 194 of 770 Codecs • Find the first codec in the far-end list that is also in the near-end list (same type, same payload size). Call this codec C2. • The C1 and C2 codec that is selected is considered to be the BB codec type. To determine which codec type is Best Bandwidth, the following rules are used: — a G.729AB codec is considered BB compared to G.729A, G.723.1, G.711_mu-Law, and G.711_a-Law codecs — a G.729A codec is considered BB compared to G.723.1,G.711_muLaw, and G.711_aLaw codecs — a G.723.1 codec is considered BB compared to a G.711_mu-Law and G.711_a-Law codec — a G.711_mu-Law codec is considered BB compared to a G.711_a-Law codec Table 41 shows the codec that would be selected between any two codecs. For example, if the two codecs are the G.729A and G.723.1, the selected codec is the G.729A. Table 41 Best Bandwidth codec Selection between any two codecs types Codec type G.711_a-Law G.711_mu-Law G.729A G.729AB G.723.1 G.711_a-Law G.711_a-Law G.711_muLaw G.729A G.729AB G.723.1 G.711_mu-Law G.711_mu-Law G.711_mu-Law G.729A G.729AB G.723.1 G.729A G.729A G.729A G.729A G.729AB G.729A G.729AB G.729AB G.729AB G.729AB G.729AB G.729AB G.723.1 G.723.1 G.723.1 G.729A G.729AB G.723.1 553-3001-365 Standard 3.00 September 2004 200 Page 195 of 770 Installation and configuration summary Contents This section contains information on the following topics: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Installation summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Voice Gateway Media Card installation summary sheet . . . . . . . . . . . 198 ........................................................ 199 Introduction This chapter provides a summary of the procedures required to install a new IP Telephony node, add cards to the node, install the cards, transmit data to the cards, and install the IP Phones. It also includes information on what is required before beginning the installation procedures. Read “Codecs” on page 179 before installing an IP Telephony node. Before you begin Ensure that the system meets the following minimum requirements: • CS 1000 or Meridian 1 system running CS 1000 Release 4.0 software IP Line Description, Installation, and Operation Page 196 of 770 Installation and configuration summary Installation summary The following summary of steps can be used as a reference guide to install and configure an IP Telephony node and Voice Gateway Media Cards on a system. This summary is intended to serve as a pointer to the more detailed procedures contained in other chapters and to provide a sequential flow to the steps involved in the overall installation procedure. Note: Complete all installation and configuration steps before transmitting data to the Voice Gateway Media Cards. 1 Complete the Voice Gateway Media Card installation summary sheet. See Table 42 on page 199. 2 Complete the IP Phone configuration data summary sheet. See Table 43 on page 200. 3 Install the hardware components: 4 553-3001-365 a. Install the Voice Gateway Media Card(s). See Procedure 10 on page 208 for installing the ITG-P 24-port line cards and Procedure 12 on page 216 for installing the Media Card 8-port and 32-port line cards. b. Cable the Voice Gateway Media Cards: i. Install the ELAN network, TLAN network, serial interface cable for the ITG-P 24-port line card. See Procedure 14 on page 224. ii. Install the Shielded 50-pin to Serial/ELAN/TLAN Adapter for the Media Card 8-port and 32-port line card. See Procedure 15 on page 228. Configure IP Line data on the system: a. Configure the IP address for the ELAN network interface. See Procedure 16 on page 229. b. Configure VoIP bandwidth management zones. See page 230. c. Configure IP Line physical TNs. See page 234. d. Configure virtual superloops. See page 240. e. Configure Small System (if applicable) mapping of virtual superloops. See page 241. f. Configure IP Phone features. See page 243. Standard 3.00 September 2004 Installation and configuration summary 5 Page 197 of 770 Configure IP Line data using Element Manager: a. Manually add an IP Telephony node. See page 339. b. Configure SNMP traps and community names access for security. See page 345. c. Configure DSP Profile data. See page 349. d. Configure DiffServ CodePoint (DSCP) data, 802.1Q support, and NAT support. See page 355. e. Configure Call Server ELAN network interface (Active ELNK) IP address, TLAN Voice port (RTP UDP port), and the routing tables on the Voice Gateway Media Card. See page 357. f. Configure file server access. See page 362. g. Configure the loss plan. See page 364. h. Configure Voice Gateway Media Care properties. See page 365. 6 Submit and transfer the node information to the Call Server. See page 368. 7 Transmit Voice Gateway Media Card configuration data to the Voice Gateway Media Cards: 8 a. Set Leader IP Address. See Procedure 51 on page 373. b. Transmit node and card properties to the Leader. See Procedure 52 on page 375. Upgrade the card software and IP Phone firmware: a. Verify card software version. See page 386. b. Verify card firmware release. See page 389. c. Download software and firmware files from the Nortel Networks web site. See page 392. d. Upload the software and firmware files to the file server. See page 393. e. Upgrade the software on the Voice Gateway Media Card. See page 396. f. Reboot the card. See page 400. g. Upgrade the firmware on the card. See page 400. IP Line Description, Installation, and Operation Page 198 of 770 Installation and configuration summary 9 Configure OTM alarm notification feature to receive IP Line SNMP traps. See Procedure 38 on page 322. 10 Assemble and install an IP Phone. Refer to IP Phones: Description, Installation, and Operation (553-3001-368). 11 Change the default IP Line CLI (IPL>) Shell password. See Procedure 63 on page 435. 12 Configure the IP Phone Installer Passwords (see page 425). a. Enable and set the administrative IP Phone Installer Password. See Procedure 63 on page 435. b. If needed, enable and set a temporary IP Phone Installer Password. See Procedure 64 on page 438. Voice Gateway Media Card installation summary sheet Nortel Networks recommends that a Voice Gateway Media Card installation summary sheet (see Table 42 on page 199) be filled out as the line cards are unpacked, inventoried, and provisioned. IP address information is usually supplied by the IP Network Administrator. To complete the installation summary sheet, the following information is required: • MAC address. This is the ELAN network interface MAC address on the Voice Gateway Media Card faceplate sticker (for example, 00:60:38:01:12:77). • ELAN network interface IP address, used to perform management through OTM and to communicate with the system • TLAN Node IP address for the IP Telephony node • TLAN network interface IP address on each card • IP address of the active ELNK Ethernet interface on the system core Nortel Networks recommends that an IP Phone configuration data summary sheet (see Table 43 on page 200) be filled out as the IP Phones are installed and configured. 553-3001-365 Standard 3.00 September 2004 Installation and configuration summary Page 199 of 770 Table 42 Voice Gateway Media Card installation summary sheet Site________________ Meridian 1/CS 1000 system ___________________ Meridian 1/CS 1000 customer________________________ Node ID (Number)________________________ TLAN Node IP address________________________ Meridian 1/CS 1000 active ELNK IP address_______________________ SNMP Manager List IP addresses________________________ TLAN gateway (router) IP address________________________ TLAN subnet mask________________________ ELAN gateway (router) IP address________________________ ELAN subnet mask__________________________ TN ELAN Management MAC address ELAN Management IP address TLAN (Voice) Card IP address Card role Leader Follower (OTM: Leader1) Follower Follower Follower Follower Follower Follower Follower Follower Follower Follower IP Line Description, Installation, and Operation Page 200 of 770 Installation and configuration summary Table 43 IP Phone configuration data summary sheet No DHCP Partial DHCP Full DHCP IP address Subnet mask Gateway IP address Connect Server IP address* Node# VTN *Connect Server IP address is the Node IP address of the IP Telephony node. 553-3001-365 Standard 3.00 September 2004 DN User Name User Location 252 Page 201 of 770 Installation and initial configuration of an IP telephony node Contents This section contains information on the following topics: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Equipment considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Required equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Optional equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 203 204 Install the hardware components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary of installation steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identify the IPE card slots on a CS 1000M or Meridian 1 . . . . . . . . Installing and cabling the ITG-P 24-port line card. . . . . . . . . . . . . . Installing and cabling the Media Card 8-port and 32-port line cards Installing the NTCW84JA ITG-specific I/O Panel filter connector for a Large System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Voice Gateway Media Card ELAN and TLAN network interfaces. 204 205 206 207 209 Initial configuration of IP Line 4.0 data . . . . . . . . . . . . . . . . . . . . . . . . Summary of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure IP address for the system active ELNK Ethernet interface (LD 117) . . . . . . . . . . . . . . . . . . . . . . . . . Configure VoIP bandwidth management zones (LD 117) . . . . . . . . Element Manager for Zone Configuration . . . . . . . . . . . . . . . . . . . . Configure physical TNs (LD 14) . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Element Manager for Voice Gateway channels. . . . . . . . . . . Configure virtual superloops for IP Phones (LD 97) . . . . . . . . . . . . 228 228 IP Line 217 221 229 230 232 234 235 240 Description, Installation, and Operation Page 202 of 770 Installation and initial configuration of an IP telephony node Configure IP Phone features in LD 11. . . . . . . . . . . . . . . . . . . . . . . Configure the IP Phone KEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IP Phone dedicated soft keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 245 250 Node election rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 Introduction This chapter explains how to install and perform the initial configuration of new IP Telephony nodes, Voice Gateway Media Cards (ITG-P 24-port and Media Card line cards), and associated cables. Before installing an IP Telephony node, refer to Data Networking for Voice over IP (553-3001-160) for information on IP network engineering guidelines. IMPORTANT! The maximum number of Voice Gateway Media Cards that can be installed in each node is 30. When more than 30 Voice Gateway Media Cards are needed on a single CS 1000 system, then multiple nodes must be used. The maximum number of Signaling Servers and Voice Gateway Media Cards that can be combined within a node is 35. Meridian 1 If configuring IP Line 4.0 on a Meridian 1, the remainder of the configuration of IP Line data is completed using Optivity Telephony Manager (OTM) 2.2. CS 1000 If configuring IP Line 4.0 on a CS 1000 system, the remainder of the configuration of IP Line data is completed using Element Manager. Installation and configuration procedures The following is a list of procedures in this chapter: 553-3001-365 • “Installing the ITG-P 24-port line card” on page 208 • “Installing the CompactFlash card on the Media Card” on page 210 Standard 3.00 September 2004 Installation and initial configuration of an IP telephony node Page 203 of 770 • “Installing the Media Card” on page 216 • “Replacing the existing I/O Panel Filter Connector” on page 218 • “Installing the NTMF94EA ELAN, TLAN, serial interface cable” on page 224 for the ITG-P Line Card • “Installing the Shielded 50-pin to Serial/ELAN/TLAN Adapter onto the Media Card” on page 228 for the Media Card • “Configuring the ELAN network interface IP address for the active ELNK” on page 229 Equipment considerations This section lists the required and optional equipment that can be used to install, configure, and maintain the Voice Gateway Media Cards and IP Phone products. Required equipment The required equipment includes the following: • a PC to manage IP Line 4.0, with the following installed: — OTM 2.2 must be installed for a Meridian 1 system — Internet Explorer 6.0.2600 (or later) to run Element Manager for CS 1000 systems • local TTY or terminal in a switch room. This is required for Leader configuration. • two shielded CAT 5 Ethernet cables to connect the Voice Gateway Media Card to an external switch (recommended) or hub equipment • 10/100BaseT network interface (optional auto-sensing) to support TLAN and 10BaseT ELAN network connections • 10/100BaseT network interface (optional auto-sensing) in each location where an IP Phone resides • serial cables IP Line Description, Installation, and Operation Page 204 of 770 Installation and initial configuration of an IP telephony node Optional equipment The optional equipment includes the following: • a server configured with Dynamic Host Configuration Protocol (DHCP); for example, a Nortel Networks NetID server • an external modem router to enable remote dial-up connection to the ELAN for technical support (Nortel Networks RM356 modem router is recommended) Install the hardware components There are three cards that use the IP Line 4.0 software; the Media Card 8-port and 32-port line cards and the ITG-P 24-port line card. • See page 209 for installation instructions for the Media Card 8-port and 32-port line card. • See page 207 for installation instructions for the ITG-P 24-port line card. IMPORTANT! The ITG-P 24-port card is not supported in the Media Gateway 1000E of the CS 1000E system. Voice Gateway Media Card If a Media Card 32-port card, a Media Card 8-port card, or an ITG-P 24-port card is running IP Line 4.0 software, it is known as a Voice Gateway Media Card. 553-3001-365 Standard 3.00 September 2004 Installation and initial configuration of an IP telephony node Page 205 of 770 Summary of installation steps The following table summarizes the steps for installing each Voice Gateway Media Card. Table 44 Installation summary (Part 1 of 2) ITG-P 24-port line card Media Card line card Determine card slot. See “Identify the IPE card slots on a CS 1000M or Meridian 1” on page 206 See “Identify the IPE card slots on a CS 1000M or Meridian 1” on page 206 Unpack the card. Remove all contents from the packaging box. Remove all contents from the packaging box. Install the CompactFlash Card. Not applicable Procedure 11 on page 210 Install the Voice Gateway Media Cards. Procedure 10 on page 208 Procedure 12 on page 216 Install NTCW84JA ITG-specific I/O Panel Filter Connector for Option 51C/61C/81/81C. Procedure 13 on page 218 Procedure 13 on page 218 Install the NTMF94EA ELAN, TLAN, RS-232 Serial Maintenance I/O interface cable. Procedure 14 on page 224 Not applicable Install the A0852632 Shielded 50-pin to Serial/ELAN/TLAN Adapter. Not applicable Procedure 15 on page 228 Step IP Line Description, Installation, and Operation Page 206 of 770 Installation and initial configuration of an IP telephony node Table 44 Installation summary (Part 2 of 2) Step ITG-P 24-port line card Media Card line card Configure card as a Leader or Follower. In OTM 2.2: Procedure 31 on page 296 In OTM 2.2: Procedure 31 on page 296 In Element Manager: Procedure 51 on page 373 (Leader) Procedure 53 on page 379 (Follower) In Element Manager: Procedure 51 on page 373 (Leader) Procedure 53 on page 379 (Follower) In OTM 2.2: Procedure 22 on page 269 In OTM 2.2: Procedure 22 on page 269 In Element Manager: Procedure 49 on page 365 In Element Manager: Procedure 49 on page 365 In OTM 2.2: Procedure 32 on page 298 Procedure 33 on page 300 In OTM 2.2: Procedure 32 on page 298 Procedure 33 on page 300 In Element Manager: Procedure 52 on page 375 In Element Manager: Procedure 52 on page 375 Add the card and configure the card properties Transmit/Transfer properties Identify the IPE card slots on a CS 1000M or Meridian 1 Depending on the module that is used, the ITG-P 24-port line card must be installed in a specific slot. Use Table 45 to identify the IPE card slots selected for the Voice Gateway Media Card. Table 45 Voice Gateway Media Card installation by module type 553-3001-365 C 1000M/Meridian 1 modules ITG-P 24-port line card slots NT8D37BA/EC IPE modules All available IPE card slots NT8D37AA/DC IPE modules 0, 4, 8, and 12 Standard 3.00 September 2004 Installation and initial configuration of an IP telephony node Page 207 of 770 Note: EMC restriction must be considered when installing the Voice Gateway Media Cards. For more information see “Electro-Magnetic Containment” on page 757. Installing and cabling the ITG-P 24-port line card Each ITG-P 24-port line card requires two slots in the CS 1000 or Meridian 1. Only the left slot of the card connects to the IPE backplane and I/O panel. A maximum of eight ITG-P 24-port line cards can be installed in an IPE shelf in a Large System. The ITG-P 24-port line card can occupy any two adjacent slots in an IPE shelf, with the left slot of the card plugging into slots 0 to 6 and 8 to 15. The left slot of an ITG-P 24-port line card cannot be plugged into slot 7, because the XPEC card is situated between slots 7 and 8. To enable a module to hold the maximum number of ITG-P 24-port line cards, install each card with the left slot of the card inserted into an even-numbered slot. CAUTION WITH ESD DEVICES Wear an ElectroStatic Discharge Strap (ESDS) when handling ITG-P 24-port and Media Card line cards. As an additional safety measure, handle all cards by the edges, and when possible, with the loosened packaging material still around the component. WARNING The CAT5 Ethernet cable between the ITG-P 24-port line card TLAN network interface and the Layer 2 switch must have a length of 50 meters or less for proper operation of the TLAN network interface To install an ITG-P 24-port line card, follow the steps in Procedure 10 on page 208. IP Line Description, Installation, and Operation Page 208 of 770 Installation and initial configuration of an IP telephony node Procedure 10 Installing the ITG-P 24-port line card 1 For each ITG-P 24-port line card in the node, identify the IPE card slot selected for the ITG-P 24-port line card. Use the information from the “Voice Gateway Media Card installation summary sheet” on page 198, and Table 42 on page 199. Table 46 ITG-P 24-port line card installation by module type Meridian 1 Modules ITG-P 24-port line card NT8D37BA/EC IPE modules All available IPE card slots NT8D37AA/DC IPE modules 0, 4, 8, and 12 Note: Even though the ITG-P 24-port line card is a two-slot card, only the left slot is counted for the card slot number. For example, for an ITG-P 24-port line card installed in slots 2 and 3, the slot number is 2. 2 Remove any existing I/O panel cabling associated with any card previously installed in the selected card slot. 3 Insert the ITG-P 24-port line card into the card guides and gently push it until it makes contact with the backplane connector. Hook the locking devices. Note 1: The red LED on the card faceplate remains lit until the card is configured and enabled in the software, at which point the LED turns off. Note 2: The faceplate display window displays start-up self-test results (T:xx) and status messages. A display “F:XX” indicates a failure of the self-test. It is normal for the ITG-P 24-port line card to display “F:10” during the start-up self-test. F:10 indicates that the self-test did not find a Security Device. The ITG-P 24-port line card does not have a security device. Some failures indicate that the card must be replaced. See Table 64 on page 569 for a list of the ITG-P 24-port line card display codes. End of Procedure 553-3001-365 Standard 3.00 September 2004 Installation and initial configuration of an IP telephony node Page 209 of 770 Installing and cabling the Media Card 8-port and 32-port line cards The Media Card 32-port line card is the successor of the ITG-P 24-port line card. It increases the packet processing power of the ITG-P 24-port line card, increases the channel density from 24 to 32 ports, and reduces the slot usage from a dual slot to a single IPE slot. Both the Media Card 32-port and 8-port line card require only one slot in the IPE shelf. CAUTION WITH ESDS DEVICES Wear an ElectroStatic Discharge strap when handling Media Card line cards. As an additional safety measure, handle all cards by the edges, and when possible, with the loosened packaging material still around the component CompactFlash installation The Media Card package contains the following items: • Media Card • CompactFlash card • retaining pin The CompactFlash card must be installed on the Media Card before installing the Media Card in the system. Follow the steps in Procedure 11 on page 210 to install the CompactFlash card. Note: If it is necessary to remove the CompactFlash card, follow the steps outlined in Procedure 101 on page 645. IP Line Description, Installation, and Operation Page 210 of 770 Installation and initial configuration of an IP telephony node Procedure 11 Installing the CompactFlash card on the Media Card 1 Remove the Media Card and CompactFlash card from the packaging. CAUTION WITH ESDS DEVICES Observe the necessary precautions for handling ESD-sensitive devices. Wear a properly connected anti-static wrist strap while removing the cards from the packaging and work on a static-dissipating surface. 2 Locate the CompactFlash card socket in the lower left-hand corner of the Media Card. See Figure 37. Figure 37 CompactFlash card socket on Media Card 3 553-3001-365 Position the CompactFlash card with the label facing up, the metal clip pulled up, and contact pins toward the socket as shown in Figure 38 on page 211. Standard 3.00 September 2004 Installation and initial configuration of an IP telephony node Page 211 of 770 Figure 38 Position the CompactFlash in socket 4 Insert the Compact Flash card in the socket. Ensure force is applied equally at both ends of the Compact Flash when pushing it in. See Figure 39 on page 212. IP Line Description, Installation, and Operation Page 212 of 770 Installation and initial configuration of an IP telephony node Figure 39 Insert CompactFlash 5 553-3001-365 Gently insert the CompactFlash card, so that it is fully in contact with the connectors on the drive. See Figure 40 on page 213. Standard 3.00 September 2004 Installation and initial configuration of an IP telephony node Page 213 of 770 Figure 40 Seat CompactFlash card 6 Push the metal clip down so that the CompactFlash card is locked in. See Figure 41 on page 214. IP Line Description, Installation, and Operation Page 214 of 770 Installation and initial configuration of an IP telephony node Figure 41 Lock card into place 553-3001-365 Standard 3.00 September 2004 Installation and initial configuration of an IP telephony node Page 215 of 770 Figure 42 CompactFlash card locked into position End of Procedure IP Line Description, Installation, and Operation Page 216 of 770 Installation and initial configuration of an IP telephony node Install the Media Card To install a Media Card, follow the steps in Procedure 12. Procedure 12 Installing the Media Card 1 For each Media Card in the node, identify the IPE card slot selected for the Media Card. Use the information from the “Voice Gateway Media Card installation summary sheet” on page 198, and Table 42 on page 199. Table 47 Media Card installation by module type Meridian 1 Modules Media Card NT8D37BA/EC IPE modules All available IPE card slots NT8D37AA/DC IPE modules 0, 4, 8, and 12 2 Remove any existing I/O panel cabling associated with any card previously installed in the selected card slot. 3 Insert the Media Card into the card guides and gently push it until it makes contact with the backplane connector. Hook the locking devices. Note 1: The red LED on the faceplate remains lit until the card is configured and enabled in the software, at which point the LED turns off. Note 2: The card faceplate display window displays start-up self-test results (T:xx) and status messages. A display “F:xx” indicates a failure of the self-test. Some failures indicate that the card must be replaced. Note 3: Refer to “Transfer node configuration from Element Manager to the Voice Gateway Media Cards” on page 371. Note 4: Refer to Table 65 on page 571 for a listing of the Media Card display codes. End of Procedure 553-3001-365 Standard 3.00 September 2004 Installation and initial configuration of an IP telephony node Page 217 of 770 Installing the NTCW84JA ITG-specific I/O Panel filter connector for a Large System For Large Systems, the standard IPE module I/O filtering is provided by the 50-Pin filter connectors mounted in the I/O Panel on the back of the IPE shelf. The filter connector attaches externally to the MDF cables and internally to the NT8D81AA Backplane to the I/O Panel ribbon cable assembly. For 100BaseTX TLAN operation, the standard I/O filter connector must be replaced with the NTCW84JA ITG Line-specific I/O filter connector for the following: • the leftmost of the two card slots occupied by the ITG-P 24-port line card • the slot occupied by the Media Card For Small Systems, and CS 1000SS systems, the standard I/O filter connector already supports 100BaseTX TLAN operation. To replace an existing I/O Panel Filter Connector, follow the steps in Procedure 13 on page 218. Note: This NTCW84JA ITG-specific Filter Connector is not required on Small Systems or CS 1000S systems. CAUTION For Large systems manufactured between 1998-1999 and shipped in North America, the IPE modules have the NT8D81BA Backplane to I/O Panel ribbon cable assembly with a non-removable filter connector. The NT8D81BA is compatible with a 10BaseT operation of the TLAN network interface, but if a 100BaseT operation of the TLAN network interface is required, order the NT8D81AA Backplane to I/O Panel ribbon cable assembly to replace it. Do not install the NTCW84JA ITG-specific filter connector onto the existing non-removable filter connector. IP Line Description, Installation, and Operation Page 218 of 770 Installation and initial configuration of an IP telephony node Replace existing I/O panel filter connector The standard I/O filter connector is shielded metal with a black plastic insert connector. The NTCW84JA connector uses yellow warning labels to indicate EMC filtering modifications and which MDF connection points can support 100BaseT connections. Procedure 13 Replacing the existing I/O Panel Filter Connector 1 Before any of the following steps, remove the ITG pack, or any other IPE pack, from the IPE shelf card slot corresponding to the I/O Panel connector to be removed. Note: Make sure to use the I/O Panel Filter Connector which corresponds to the left slot number of the DCHIP card. 553-3001-365 2 Remove the NT8D81AA Backplane to I/O Panel ribbon cable assembly, that is connected to the Backplane side of the existing block, by releasing the latching pins on the filter block and pulling the NT8D81AA cable away. 3 Unscrew the existing filter connector from the I/O panel. There is one screw on the lower front of the connector and one screw on the upper back of the connector. Remove the connector. 4 Re-position the new NTCW84JA filter connector in the now vacant I/O panel opening. See Figure 43 on page 219. Standard 3.00 September 2004 Installation and initial configuration of an IP telephony node Page 219 of 770 Figure 43 NTCW84JA 50 pin ITG-specific I/O Panel filter connector for Large Systems System backplane side (inside I/O Panel) MDF Cable Exterior side of system (to MDF, and so on) NT8D81AA Cable System I/O Panel 5 Attach the new NTCW84JA ITG-specific filter connector to the I/O panel by securely fastening the top back screw and the bottom front screw. 6 Reconnect the NT8D81AA cable and secure it in place by snapping shut the locking latches provided on the NTCW84JA connector. End of Procedure IP Line Description, Installation, and Operation Page 220 of 770 Installation and initial configuration of an IP telephony node Incorrect configuration problems TLAN network interface operation problems can arise from the standard I/O filter connector in IPE modules on Large Systems. Some problem scenarios and their respective solutions are outlined in Table 48. Table 48 I/O filter connector Scenario Solution The installer forgets to replace the standard IPE module I/O filter connector with the provided Voice Gateway Media Card/ITG-specific filter connector that removes filtering from pairs 23 and 24. Correctly install the Voice Gateway Media Card/ITG-specific filter connector by replacing the standard IPE Module I/O filter connector. The installer installs the Voice Gateway Media Card/ITG-specific filter connector on top of the standard IPE module I/O filter connector. Correctly install the Voice Gateway Media Card/ITG-specific filter connector by replacing the standard IPE Module I/O filter connector. The installer encounters an IPE module that is equipped with standard filter connectors molded onto the backplane I/O ribbon cable assemblies. The installer does not replace the IPE module backplane I/O ribbon cable assemblies with the ones that have interchangeable I/O filter connectors. Order new IPE Module Backplane I/O ribbon cable assemblies that have interchangeable I/O filter connectors if it becomes necessary to use one of the IPE Modules with molded-on I/O filter connectors. The UTP cabling from the TLAN network interface to the Layer 2 switch does not meet the UTP CAT5 termination and impedance uniformity standards. Always ensure that UTP cabling from the TLAN network interface to the Layer 2 switch is CAT5-compliant. 553-3001-365 Standard 3.00 September 2004 Installation and initial configuration of an IP telephony node Page 221 of 770 Voice Gateway Media Card ELAN and TLAN network interfaces CS 1000M and Meridian 1 systems The ELAN and TLAN network interfaces are provided by one of the following: • NTMF94EA ELAN, TLAN, RS-232 Serial Maintenance I/O interface cable (see Figure 44 on page 223) • A0852632 Shielded 50-pin to Serial/ELAN/TLAN Adapter (see Figure 45 on page 226) The ITG-P 24-port line card uses the NTMF94EA ELAN, TLAN, RS-232 Serial Maintenance I/O interface cable. The Media Card uses the A0852632 Shielded 50-pin to Serial/ELAN/TLAN Adapter. The ELAN network interface supports 10BaseT operation and the TLAN network interface supports 10/100BaseT operation. To support the 100BaseT operation on Large Systems, the TLAN network interface requires specialized I/O panel mounting connectors. These replace the standard connectors provided on the system. Cables and connectors for the ELAN and TLAN network interface functions include the following: • the NTCW84JA I/O panel filter block • NTMF94EA ELAN, TLAN, RS-232 Serial Maintenance I/O interface cable • A0852632 Shielded 50-pin to Serial/ELAN/TLAN Adapter. Standard shielded, CAT5 LAN cables (<100 meters) are recommended to attach the LAN ports to the local network. IP Line Description, Installation, and Operation Page 222 of 770 Installation and initial configuration of an IP telephony node CS 1000S systems For information on Voice Gateway Media Card ELAN and TLAN network interfaces on a CS 1000S system, refer to Communication Server 1000S: Installation and Configuration (553-3031-210). 553-3001-365 Standard 3.00 September 2004 Installation and initial configuration of an IP telephony node Page 223 of 770 Install the NTMF94EA ELAN, TLAN, RS-232 Serial Maintenance I/O interface cable The NTMF94EA cable provides the ELAN, TLAN and serial interface for the ITG-P 24-port line card. See Appendix B: “I/O, maintenance, and extender cable description” on page 717 for pinouts and technical specifications on the NTMF94EA cable. Figure 44 NTMF94EA ELAN, TLAN, and RS-232 Serial Maintenance I/O cable Mounting Screw Shielded 25-pair Amphenol Connector Shielded RJ-45 Mating Coupler To Switch Ferrite Shielded RJ-45 Cable To Switch 9 Pin D-Sub Female 553-ITG0006 IP Line Description, Installation, and Operation Page 224 of 770 Installation and initial configuration of an IP telephony node To install the NTMF94EA ELAN, TLAN, serial interface cable, complete the steps in Procedure 14. Procedure 14 Installing the NTMF94EA ELAN, TLAN, serial interface cable WARNING Plug all Voice Gateway Media Card ELAN network interfaces belonging to the same node into the same ELAN hub or Layer 2 switch port group. 1 On Large Systems, connect the NTMF94EA ELAN, TLAN, and RS-232 Serial Maintenance I/O cable to the I/O panel connector for the left hand card slot. For Small Systems, connect the cable to the I/O connector in the cabinet that corresponds to the IP Line card slot (see Figure 218 on page 719). 2 Connect a shielded CAT5 Ethernet cable from the customer’s TLAN Layer 2 or Layer 3 switch port to the RJ-45 port labeled “TLAN”. 3 Connect a shielded CAT5 Ethernet cable from the customer’s ELAN Layer 2 or Layer 3 switch port to the RJ-45 port labeled “ELAN”. 4 Install the NTAG81CA serial cable into the faceplate Maintenance port. This connection is used to configure the IP address for Leader 0. If required, use the NTAG81BA maintenance extender cable. Note: Alternatively, for a permanent connection to the maintenance port, use the DB9 female connector on the NTMF94BA breakout cable to connect a modem (using a null modem) or directly to a local TTY terminal. WARNING The serial maintenance ports presented at the faceplate and at the backplane are identical. Do not connect a terminal to both access points simultaneously. This results in incorrect and unpredictable operation of the Voice Gateway Media Card. 553-3001-365 Standard 3.00 September 2004 Installation and initial configuration of an IP telephony node Page 225 of 770 Note 1: The switch LEDs and the faceplate link LEDs light when the card is connected to the WAN/LAN through the TLAN network interface. Note 2: Refer to Data Networking for Voice over IP (553-3001-160) for more information about engineering and connecting the LAN/WAN. End of Procedure Install the Shielded 50-pin to Serial/ELAN/TLAN Adapter The Media Card can support a single connector solution for access to the TLAN and ELAN network interfaces. This connector (see Figure 45 on page 226) is called the A0852632 Shielded 50-pin to Serial/ELAN/TLAN Adapter. It replaces the single NTMF94EA ELAN, TLAN, RS-232 Serial Maintenance I/O interface cable (‘octopus’ cable). The adapter breaks out the signals from the I/O connector to the following: • ELAN network interface • TLAN network interface • one RS-232 (local console) port IP Line Description, Installation, and Operation Page 226 of 770 Installation and initial configuration of an IP telephony node Figure 45 Shielded 50-pin to Serial/ELAN/TLAN Adapter TLAN RJ-45 port ELAN RJ-45 port RS-232 Connector Identification Label 50-pin connector On Large Systems, the NT8D81AA cable is used to bring all 24 Tip and Ring pairs to the I/O panel. The NTCW84JA I/O panel mounting block must be installed on Large Systems before the A0852632 Shielded 50-pin to Serial/ELAN/TLAN Adapter is installed. Refer to Figure 45. To ensure proper connection, install the adapter securely; otherwise, connectivity could be lost. 553-3001-365 Standard 3.00 September 2004 Installation and initial configuration of an IP telephony node Page 227 of 770 EMC Shielding Kit An ITG EMC shielding kit (NTVQ83AA) must be installed on the ELAN and TLAN network interface cables to meet regulatory requirements at the installation site. As shown in Figure 46, a ferrite must be placed on both the ELAN and TLAN network interface CAT5 Ethernet cables during installation. Cable ties are then placed to retain the ferrites in the correct position. This applies to Small Systems and Large Systems. Figure 46 ITG EMC Shielding Kit Deployment ITG Card Adapter ELAN/TLAN Serial/maintenance cable ELAN cable To LAN/hub cable tie 3 in TLAN cable snap-on ferrite EMC Kit Deployment Follow the steps in Procedure 15 on page 228 to install the ITG EMC shielding kit (NTVQ83AA) on the ELAN and TLAN network interface cables. IP Line Description, Installation, and Operation Page 228 of 770 Installation and initial configuration of an IP telephony node Procedure 15 Installing the Shielded 50-pin to Serial/ELAN/TLAN Adapter onto the Media Card 1 Install the Shielded 50-pin to Serial/ELAN/TLAN Adapter into the card connector (1, 2, 3, or 4) where the Media Card is located. 2 Connect a shielded Cat 5 cable from the customer’s TLAN switch equipment to the port labeled “TLAN”. 3 Connect a shielded Category 5 cable from the customer’s ELAN hub or switch equipment to the port labeled “ELAN”. 4 Install the NTAG81CA serial cable into the faceplate Maintenance port. End of Procedure Initial configuration of IP Line 4.0 data Before beginning the configuration: • Ensure the system is running CS 1000 Release 4.0 software. • Verify the License system limit in LD 22. The License system limit must have sufficient unused units to support the number of IP Phones to be installed. For more information, refer to Software Input/Output: Maintenance (553-3001-511). • Expand the License limit, if necessary, by ordering additional Licenses. See “Licenses” on page 52 for more information. Summary of procedures 553-3001-365 1 Configure IP address for the system active ELNK Ethernet interface (LD 117). See page 229. 2 Configure VoIP bandwidth management zones (LD 117). See page 230. 3 Configure physical TNs (LD 14). See page 234. 4 Configure virtual superloops for IP Phones (LD 97). See page 240. 5 Configure IP Phone features in LD 11. See page 243. Standard 3.00 September 2004 Installation and initial configuration of an IP telephony node Page 229 of 770 Configure IP address for the system active ELNK Ethernet interface (LD 117) To configure the Call Server’s ELAN network interface IP address (active ELNK), follow the steps in Procedure 16. Procedure 16 Configuring the ELAN network interface IP address for the active ELNK 1 Go to LD 117. 2 Create host entries with the IP address on the ELAN subnet by entering one of the following commands: NEW HOST PRIMARY_IP xx.xx.xx.xx NEW HOST SECONDARY_IP xx.xx.xx.xx (for Large Systems only) 3 Assign the host entry IP address to active and inactive ELNK interfaces on ELAN by entering one of the following commands: CHG ELNK ACTIVE PRIMARY_IP CHG ELNK INACTIVE SECONDARY_IP (for Dual CPU only) 4 Verify the IP address for the Ethernet by entering the following command: PRT ELNK. 5 Enter the following command: Update DBS. 6 Go to LD 137. Check the status of the Ethernet interface by entering the command: STAT ENLK. If the ELNK is disabled, enable it by entering: ENL ELNK. End of Procedure IP Line Description, Installation, and Operation Page 230 of 770 Installation and initial configuration of an IP telephony node Configure VoIP bandwidth management zones (LD 117) Up to 256 zones can be defined in LD 117. The Call Server uses the zones for VoIP bandwidth management. For more information, see Data Networking for Voice over IP (553-3001-160). The term Intrazone means within the same zone. Interzone means between two different zones. Table 49 on page 231 lists the zone parameters as follows: • p1 – total bandwidth (Kbps) available for Intrazone calls • p2 – defines the codec for Intrazone calls (that is, preserve voice quality or preserve bandwidth). BQ provides the best voice quality but uses the most bandwidth. BB uses the least amount of bandwidth but reduces voice quality. • p3 – total bandwidth available for Interzone calls • p4 – preferred strategy for the choice of the codec for Interzone calls • p5 – zone resource type. The type is either shared or private. LD 117 also includes the DIS and ENL commands to disable or enable a zone. When a zone is created, its default state is enabled. CAUTION Zone 0 must be configured in LD 117 first before other zones are configured or all calls associated with zone 0 are blocked. 553-3001-365 Standard 3.00 September 2004 Installation and initial configuration of an IP telephony node Page 231 of 770 Table 49 LD 117 bandwidth management zone configuration Command Description NEW ZONE xxx p1 p2 p3 p4 p5 Create a new zone, where: xxx = zone number = (0) – 255. p1 = Intrazone available bandwidth = 0 – (10000) – 100000 (Kbps) p2 = Intrazone preferred strategy = (BQ – Best Quality) or BB – Best Bandwidth p3 = Interzone available bandwidth = 0 – (10000) – 100000 (Kbps) p4 = Interzone preferred strategy = BQ for Best Quality or BB for Best Bandwidth p5 = Zone resource type = (shared) or private New ZONE xxx Create a new zone with default values for the parameters: p1 = 10000 (Kbps) p2 = BQ p3 = 10000 (Kbps) p4 = BQ p5 = shared CHG ZONE xxx p1 p2 p3 p4 p5 Change parameters of a zone. All parameters must be re-entered, even those that are unchanged. OUT ZONE xxx Remove a zone. DIS ZONE xxx Disable a zone. When a zone is disabled, no new calls are established inside, from, or toward this zone. ENL ZONE xxx Enable a zone. PRT ZONE xxx Print zone and bandwidth information, where xxx specifies a zone. If no zone is specified, information for all zones is printed. PRT ZONE ALL also prints information for all zones. PRT ZONE ALL IP Line Description, Installation, and Operation Page 232 of 770 Installation and initial configuration of an IP telephony node Element Manager for Zone Configuration Optionally, zones can be configured for CS 1000 systems using Element Manager instead of LD 117. To view Element Manager for zone configuration, follow the steps in Procedure 18: Procedure 17 Viewing Element Manager for Zone Configuration 1 Launch and log into Element Manager. See Procedure 40 on page 335. 2 In the navigation tree, click Configuration > Call Server and then click Zone. The Zone List window opens. See Figure 47. Figure 47 Zone List 3 553-3001-365 Click the to Add button to add a new zone. Standard 3.00 September 2004 Installation and initial configuration of an IP telephony node Page 233 of 770 The Zone Basic Property and Bandwidth Management window opens. See Figure 48. Figure 48 Zone Basic Property and Bandwidth Management window End of Procedure IP Line Description, Installation, and Operation Page 234 of 770 Installation and initial configuration of an IP telephony node Configure physical TNs (LD 14) Use LD 14 to define the physical TNs for the Voice Gateway Media Card. Also use LD 14 to disable the cards. The OTM IP Telephony Gateway - IP Line application requires Voice Gateway Media Cards to be in a disabled state before transmitting card properties. See Table 50 for a list of the prompts and responses in LD 14. Table 50 Configure physical TNs in LD 14 (Part 1 of 2) Prompt Response Description REQ NEW CHG OUT Create the Voice Gateway channels on a line card. Change configuration data for a Voice Gateway channel. Delete the Voice Gateway channels on a line card. TYPE VGW Voice Gateway TN TN of the first ITG Physical TN lscu DES Format for Large System and CS 1000E system, where l = loop, s = shelf, c = card, u = unit. cu Format for Small System, CS 1000S system, Media Gateway 1000B, and Media Gateway 1000T, where c = card and u = unit. aa.......a Description for gateway channel. Identify the channel using the card’s TLAN network interface IP address or MAC address. XTRK aaa ITG8 – ITG 486 8-port card ITGP – ITG-P 24-port card MC8 – Media Card 8-port card MC32 – Media Card 32-port card 553-3001-365 Standard 3.00 September 2004 Installation and initial configuration of an IP telephony node Page 235 of 770 Table 50 Configure physical TNs in LD 14 (Part 2 of 2) Prompt Response Description ZONE 0 – 255 Zone number to which this ITG Physical TN belongs. Verify that the zone exists in LD 117. CUST xx Customer number as defined in LD 15 Using Element Manager for Voice Gateway channels Alternatively, for CS 1000 systems, configure the Voice Gateway channels using Element Manager instead of using LD 14. To use Element Manager to configure Voice Gateway channels, follow the steps in Procedure 18. Procedure 18 Using Element Manager to configure Voice Gateway channels 1 Launch and log into Element Manager. See Procedure 40 on page 335 for details. 2 In the navigation tree, click Configuration > IP Telephony. The Node Summary window opens. See Figure 49 on page 236. IP Line Description, Installation, and Operation Page 236 of 770 Installation and initial configuration of an IP telephony node Figure 49 Node Summary window 3 553-3001-365 Expand a node by clicking the arrow to the left of the node. Click the DSP Channels button. The VGW Channels summary window opens. See Figure 50 on page 237. Standard 3.00 September 2004 Installation and initial configuration of an IP telephony node Page 237 of 770 Figure 50 VGW Channels summary window 4 To add new gateway channels, click the Add button at the top in the Gateway Channel summary window. The Add VGW channels window opens. See Figure 51 on page 238. Note: Figure 51 is the equivalent to LD 14’s NEW command. IP Line Description, Installation, and Operation Page 238 of 770 Installation and initial configuration of an IP telephony node Figure 51 Add VGW channels window 5 To edit a specific Voice Gateway channel, click the Edit button to the right of the channel in the VGW Channels summary window seen in Figure 50 on page 237. The Edit VGW channel window opens. See Figure 52 on page 239. The Edit VGW channel window is equivalent to LD 14’s CHG command that enables the changing of the DES and ZONE parameters of the channel. 553-3001-365 Standard 3.00 September 2004 Installation and initial configuration of an IP telephony node Page 239 of 770 Figure 52 Edit VGW channel window 6 To delete a Voice Gateway channel, click the Delete button in the Gateway Channel summary window. See Figure 50 on page 237. The Delete VGW channels for the Voice Gateway channel opens. See Figure 53 on page 240. Select a gateway channel from the drop-down list box and click Delete. Figure 53, the Delete VGW channels window, is the equivalent of LD 14’s OUT command. IP Line Description, Installation, and Operation Page 240 of 770 Installation and initial configuration of an IP telephony node Figure 53 Delete VGW channels window End of Procedure Configure virtual superloops for IP Phones (LD 97) One or more virtual superloops must be configured to support IP Phone Virtual TNs (VTNs). Large Systems In Large Systems, virtual superloops contend for the same range of loops with phantom, standard and remote superloops, digital trunk loops, and all service loops. Virtual superloops can reside in physically-equipped network groups or in virtual network groups. Group maximums Without FIBN, Package 365, there is a maximum of five network groups available, 0 – 4. With Package 365, there are a maximum of eight network groups, 0 – 7. For normal traffic engineering, provision up to 1024 VTNs on a single virtual superloop for a Large System. For non-blocking, do not exceed 120 VTNs on a single virtual superloop for a Large System. 553-3001-365 Standard 3.00 September 2004 Installation and initial configuration of an IP telephony node Page 241 of 770 Nortel Networks recommends that virtual superloops are configured starting in the highest non-physically equipped group available. Table 51 lists the prompts and responses required to configure virtual superloops in LD 97. Table 51 LD 97 – Virtual superloop configuration for Large Systems Prompt Response Description REQ CHG Change existing data. TYPE SUPL Superloop SUPL Vxxx V represents a virtual superloop and xxx is the number of the virtual superloop where: • xxx = 0 – 156 and multiple of four for a Large System without FIBN package 365 • xxx = 0 – 252 and multiple of four for a Large System with FIBN package 365 Small Systems In Small Systems, virtual superloops contend for the same range of superloops, 96 – 112, with phantom superloops. Up to 128 VTNs can be configured on a single virtual superloop for a Meridian 1 Option 11C Cabinet and Option 11C Chassis system, for a maximum of 640 VTNs in each system. A maximum of 1000 VTNs can be configured on a CS 1000M Cabinet and CS 1000M Chassis system. IP Line Description, Installation, and Operation Page 242 of 770 Installation and initial configuration of an IP telephony node In a Small System, mapping virtual superloops to virtual cards is the same as mapping phantom superloops to phantom cards. See Table 52. Table 52 Virtual superloop/virtual card mapping for Small Systems SUPL Card 96 61-64 100 65-68 104 69-72 108 73-76 112 77-80 CS 1000S systems Table 53 lists the virtual superloop and virtual card mapping for the CS 1000S system. Table 53 Virtual superloop/virtual card mapping for CS 1000S systems SUPL Card 96 61-64 81-84 100 65-68 85-88 104 69-72 89-92 108 73-76 93-96 112 77-80 97-99 LD 97 PRT TYPE SUPL prints the implicit virtual, phantom, or DECT cards for a virtual, phantom, or DECT superloop. 553-3001-365 Standard 3.00 September 2004 Installation and initial configuration of an IP telephony node Page 243 of 770 LD 21 LUU allows the user to list unused units of a specified type (iset, vtrk, phantom, DECT) in a specified range of TNs (for example, Virtual TNs). Similarly, LUC of a specified type (virtual, phantom, or DECT) prints a list of unused cards on configured superloops. Configure IP Phone features in LD 11 The existing License header that is printed at the start of LD 11 includes the new License limit for the IP Phone. Refer to Table 43 on page 200 to configure the IP Phone features in LD 11. Table 54 LD 11 – Configure an IP Phone (Part 1 of 3) Prompt Response Description REQ: NEW CHG PRT OUT CPY MOV New Change Print Out Copy Move TYPE: i2001 i2002 i2004 i2050 For IP Phone 2001, IP Phone 2002, and IP Phone 2004, IP Softphone 2050, or MVC 2050. The system accepts this response if it is equipped with packages 88 and 170. The IP Phone 2001 and IP Phone 2002, IP Softphone 2050, and MVC 2050 are also restricted by the IP Phone License setting. IP Line Description, Installation, and Operation Page 244 of 770 Installation and initial configuration of an IP telephony node Table 54 LD 11 – Configure an IP Phone (Part 2 of 3) Prompt Response Description TN lscu Format for Large System and CS 1000E system, where l = loop, s = shelf, c = card, u = unit. Enter loop (virtual loop), shelf, card, and unit (terminal number), where unit = 0 – 31 cu Format for Small System, CS 1000S system, Media Gateway 1000B, and Media Gateway 1000T, where c = card and u = unit. Enter card slot (virtual slot) and unit. Note: See Table 52 on page 242 for virtual superloop to virtual card slot mapping for Small Systems. DES a...z ODAS telephone designator CUST xx Customer number as defined in LD 15 ZONE 0 – 255 Zone number to which this IP Phone belongs. The zone prompt is applied only when TYPE = i2001, i2002, i2004, or i2050. Note: Verify that the zone number exists in LD 117. 553-3001-365 Standard 3.00 September 2004 Installation and initial configuration of an IP telephony node Page 245 of 770 Table 54 LD 11 – Configure an IP Phone (Part 3 of 3) Prompt Response Description CLS ADD ADD - Automatic Digit Display, default for IP Phone. For a complete list of responses, refer to Software Input/Output: Administration (553-3001-311). KEY xx aaa yy zz...zz Telephone function key assignments where: xx = keys 0 – 5 (and 6 – 11 using the Shift key) for IP Phone 2004 and xx = keys 0 – 3 for the IP Phone 2002. These are self-labeled physical keys that can be programmed with any feature. xx = 0 for the IP Phone 2001; any other key number entered returns an error message. aaa = key name or function yyy, zzz = additional information required for the key. Note: Keys 16 – 26 are reserved for dedicated IP Phone soft keys. Table 55 lists the dedicated IP Phone key name values (aaa). Other key name values can be found in Software Input/Output: Administration (553-3001-311). Configure the IP Phone KEM Configure the optional IP Phone KEM in LD 11. IP Line Description, Installation, and Operation Page 246 of 770 Installation and initial configuration of an IP telephony node Note: The IP Phone KEM is not supported on the IP Phone 2001. LD 11 – Configure the IP Phone KEM. (Part 1 of 4) Prompt Response Description REQ: NEW Add new data. CHG Change existing data. i2002 IP Phone 2002 i2004 IP Phone 2004 ZONE 0-255 Zone number to which the IP Phone 2002 or IP Phone 2004 belongs KEM (0)-2 Number of attached IP Phone KEMs TYPE: ... Note: Up to two IP Phone KEMs can be attached to an IP Phone. Pressing without entering a number leaves the value unchanged. ... 553-3001-365 Standard 3.00 September 2004 Installation and initial configuration of an IP telephony node Page 247 of 770 LD 11 – Configure the IP Phone KEM. (Part 2 of 4) Prompt Response Description KEY xx aaa yyyy (cccc or D) zz..z Telephone function key assignments The following key assignments determine calling options and features available to a telephone. Note that KEY is prompted until just a carriage return is entered. Where: xx = key number For IP Phone 2002, where: xx = 0-31, when KEM = 0 xx = 0-55, when KEM = 1 xx = 0-79, when KEM = 2 For IP Phone 2004, where: xx = 0-31, when KEM = 0 xx = 0-79, when KEM = 1 xx = 0-79, when KEM = 2 Note: Type xx = NUL to remove a key function or feature. aaa = key name or function yyyy = additional information required for the key zz..z = additional information required for the key aaa The cccc or D entry deals specifically with the Calling Line Identification feature, where: cccc = CLID table entry of (0)-N, where N = the value entered at the SIZE prompt in LD 15 minus 1. You can enter a CLID table entry if aaa = ACD, HOT d, HOT L, MCN, MCR, PVN, PVR, SCN, or SCR. D = the character “D”. When the character “D” is entered, the system searches the DN keys from key 0 and up, to find a DN key with a CLID table entry. The CLID associated with the found DN key will then be used. IP Line Description, Installation, and Operation Page 248 of 770 Installation and initial configuration of an IP telephony node LD 11 – Configure the IP Phone KEM. (Part 3 of 4) Prompt Response Description Note: The position of the (cccc or D) field varies depending on the key name or function. PAGEOFST Automatically calculates the IP Phone KEM key based on the entered values. This prompt enables the system administrator to enter a Page number of 0 or 1 and a Key Offset number from 0-23. Once entered, the KEY prompt is prompted with the appropriate KEY value filled in. Enter to terminate data entry. Note 1: Applies to an IP Phone 2004 with KEM = 1, and where was entered at the KEY prompt. Note 2: Does not apply to an IP Phone 2002. When values are entered for Page and KeyOffset, the KEY xx prompt displays, followed by PAGEOFST prompt. This loop continues until no values ( only) are entered at the PAGEOFST prompt. KEY xx Edit the IP Phone KEM key number specified by PAGEOFST, where: xx = the number of the key (for example, KEY 36) Enter to keep the current setting. 553-3001-365 Standard 3.00 September 2004 Installation and initial configuration of an IP telephony node Page 249 of 770 LD 11 – Configure the IP Phone KEM. (Part 4 of 4) Prompt Response Description KEMOFST Automatically calculates the IP Phone KEM key based on the entered values. This prompt enables the system administrator to enter a KEM number of 1 or 2 and a Key Offset number from 0-23. Once entered, the KEY prompt is prompted with the appropriate KEY value filled in. Enter to terminate data entry. When values are entered for KEM and KeyOffset, the KEY xx prompt displays, followed by KEMOFST prompt. This loop continues until no values ( only) are entered at the KEMOFST prompt. Note 1: Applies to an IP Phone 2002 if was entered at the KEY prompt. Note 2: Applies to an IP Phone 2004 with KEM = 2, and where was entered at the KEY prompt. KEY xx Edit the IP Phone KEM key number specified by KEMOFST, where: xx = the number of the key (for example, KEY 36) Enter to keep the current setting. IP Line Description, Installation, and Operation Page 250 of 770 Installation and initial configuration of an IP telephony node IP Phone dedicated soft keys Table 55 describes the features that can be assigned to dedicated soft keys 16-26 on the IP Phone 2001, IP Phone 2002, and IP Phone 2004, IP Softphone 2050, or MVC 2050. Remove unused feature keys by configuring the dedicated soft keys to NUL. Some features depend on the given Class of Service. If an attempt is made to configure anything other than the permitted response, the system generates an error code. For related error messages, see SCH messages in Software Input/Output: System Messages (553-3001-411). Table 55 LD 11 – IP Phone dedicated soft key assignment (Part 1 of 2) IP Phone key number Response(s) Allowed Key 16 MWK, NUL MWK – Message Waiting key Key 17 TRN, NUL TRN– - Call Transfer key Key 18 A03, A06, NUL AO3 – 3-party conference key AO6 – 6-party conference key Key 19 CFW, NUL CFW – Call Forward key Key 20 RGA, NUL RGA – Ring Again key Key 21 PRK, NUL PRK – Call Park key Key 22 RNP, NUL RNP – Ringing Number pickup key 553-3001-365 Standard 3.00 September 2004 Installation and initial configuration of an IP telephony node Page 251 of 770 Table 55 LD 11 – IP Phone dedicated soft key assignment (Part 2 of 2) IP Phone key number Response(s) Allowed Key 23 SCU, SSU, SCC, SSC, NUL SCU – Speed Call User SSU – System Speed Call User SCC – Speed Call Controller SSC – System Speed Call Controller Key 24 PRS, NUL PRS – Privacy Release key Key 25 CHG, NUL CHG – Charge Account key Key 26 CPN, NUL CPN – Calling Party Number key Node election rules The rules for the node election process are as follows: 1 A Signaling Server wins over any Voice Gateway Media Cards. 2 A Leader card always wins over a Follower card. 3 A Media Card wins over an ITG-P card. 4 Within each class (Leader/Follower), the card with the longest up-time wins. 5 In the event of a tie in up-time length, the card with the lowest IP address wins. The precedence of the rules is from 1 (highest) to 5 (lowest). This means, for example, that since Rule 2 is applied before Rule 3, a Media Card Follower card cannot win over an ITG-P Leader card. IP Line Description, Installation, and Operation Page 252 of 770 553-3001-365 Installation and initial configuration of an IP telephony node Standard 3.00 September 2004 328 Page 253 of 770 Configuration of IP telephony nodes using OTM 2.2 Contents This section contains information on the following topics: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 Configure IP Line data using OTM. . . . . . . . . . . . . . . . . . . . . . . . . . . . Launch OTM and the IP Line 4.0 application . . . . . . . . . . . . . . . . . Add a site, system, and customer . . . . . . . . . . . . . . . . . . . . . . . . . . . Manually add an IP Telephony node . . . . . . . . . . . . . . . . . . . . . . . . Configure the card properties of the Voice Gateway Media Card . . Configure DSP profile data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure SNMP traps and ELAN gateway routing table . . . . . . . . Configure node synchronization with the Call Server . . . . . . . . . . . Configure the Call Server ELAN IP address and the TLAN voice port. . . . . . Configure security for SNMP access . . . . . . . . . . . . . . . . . . . . . . . . Configure SNMP access and community name strings . . . . . . . . . . Configure SNMP trap destinations for an IP Telephony node. . . . . Configure file server access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure SNTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 256 258 264 268 271 275 279 282 284 284 287 290 292 294 Transmit node configuration from OTM 2.2 to the Voice Gateway Media Cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . Set the Leader 0 IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmit node and card properties to Leader 0 . . . . . . . . . . . . . . . . Transmit card properties to all cards in the node . . . . . . . . . . . . . . . 295 296 298 300 IP Line Description, Installation, and Operation Page 254 of 770 Configuration of IP telephony nodes using OTM 2.2 Upgrade the Voice Gateway Media Card software and IP Phone firmware . . . . . IP Phone firmware installation and upgrade . . . . . . . . . . . . . . . . . . IP Phone firmware upgrade from a new Voice Gateway Media Card . Verify card software and IP Phone firmware. . . . . . . . . . . . . . . . . . Upgrade options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade Voice Gateway Media Card software . . . . . . . . . . . . . . . . Upgrade the Voice Gateway Media Card software . . . . . . . . . . . . . Upgrade the IP Phone firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 303 305 306 310 311 314 315 Configure OTM Alarm Management to receive IP Line SNMP traps. . . . 322 Assemble and install an IP Phone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 Change the default IPL> CLI Shell password . . . . . . . . . . . . . . . . . . . 328 Change the default IPL> CLI Shell password . . . . . . . . . . . . . . . . . . . 328 Introduction This chapter explains how to configure IP Telephony nodes and Voice Gateway Media Cards using Optivity Telephony Manager (OTM) 2.2. This chapter also provides instruction for transmitting data to Voice Gateway Media Cards, upgrading card software, and upgrading IP Phone firmware using OTM. Read about IP network engineering guidelines in Data Networking for Voice over IP (553-3001-160) before installing an IP Telephony node. Configure IP Line data using OTM OTM can be used to manually add and configure IP Telephony nodes. OTM 2.2 includes an IP Line 4.0 application that is used to configure nodes on CS 1000 or Meridian 1 systems. Multiple IP Telephony nodes for IP Phones are configured and managed from the same OTM PC. 553-3001-365 Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 Page 255 of 770 Node definition A node is defined as a collection of Signaling Servers and Voice Gateway Media Cards (ITG-P 24-port line cards and Media Card 8-port and 32-port line cards). Each node in the network has a unique Node ID. This Node ID is an integer value. A node has only one primary or Leader Voice Gateway Media Card. All the other Voice Gateway Media Cards are defined as Followers. Note 1: All IP addresses and subnet mask data must be in dotted decimal format. Convert subnet mask data from Classless Inter-Domain (CIDR) format. Note 2: Refer to Table 42 on page 199 for IP addresses and information required in this procedure. WARNING OTM 2.2 does not support configuration of nodes which reside on a CS 1000 system. However, since OTM 2.2 is required for retrieval of Operational Measurement (OM) reports from nodes on these systems, OTM is capable of being configured with basic network connection information of the node. The necessary configuration to retrieve the OM reports is covered in Procedure 19 on page 256 through Procedure 23 on page 271. In these procedures, pay special attention to any comments specific to nodes which reside on a CS 1000 system. IP Line Description, Installation, and Operation Page 256 of 770 Configuration of IP telephony nodes using OTM 2.2 Launch OTM and the IP Line 4.0 application To launch OTM and start the IP Line 4.0 application, follow the steps in Procedure 19. Procedure 19 Launching OTM 1 Select Start > Programs > Optivity Telephony Manager > OTM Navigator. 2 The OTM Login screen appears. See Figure 54. Figure 54 OTM Login screen 3 Enter the Login Name and Password. Click OK. 4 The OTM Navigator window opens. OTM Navigator has two tabs: Sites and Gatekeeper Zones. The IP Line 4.0 application, called IP Telephony, that is available with OTM is located on the Sites tab. Click the Sites tab. See Figure 55 on page 257. 553-3001-365 Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 Page 257 of 770 Figure 55 OTM Navigator 5 Expand the Services folder. Double-click the IP Telephony icon to launch the IP Line 4.0 application. See Figure 55. The IP Telephony window opens. This application is used to configure and administer the IP Telephony nodes and the Voice Gateway Media Cards. End of Procedure IP Line Description, Installation, and Operation Page 258 of 770 Configuration of IP telephony nodes using OTM 2.2 Add a site, system, and customer A site, system, and customer must be added before nodes and Voice Gateway Media Cards can be configured. Follow the steps in Procedure 20 to add a site, system, and customer using OTM Navigator. Procedure 20 Adding a site, system, and customer 1 In the OTM Navigator window, click Configuration > Add Site. See Figure 56. Figure 56 OTM Navigator – Configuration > Add Site The New Site Properties window opens. See Figure 57 on page 259. 553-3001-365 Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 Page 259 of 770 Figure 57 New Site Properties window 2 In the New Site Properties window, configure the following: a. Site Name: Enter the name of the site. b. Short Name: Enter a short name for the site. c. Under Site Location, add the Address, City, State/Province, Country, and Zip/Postal Code of the site. d. Under Contact Information, add the Name, Phone Number, Job Title, and any Comments for the site contact person(s). IP Line Description, Installation, and Operation Page 260 of 770 Configuration of IP telephony nodes using OTM 2.2 3 Click Apply. The Add System button (located in the upper right corner of the New Site Properties window) is enabled. 4 Click the Add System button. The Add System dialog box opens. See Figure 58. Figure 58 Add System 5 In the Add System dialog box, select the system and click OK. The New System Properties window opens. See Figure 59 on page 261. 553-3001-365 Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 Page 261 of 770 Figure 59 New System Properties window 6 7 In the New System Properties window, configure the following: a. System Name: Enter the name of the system. b. Short Name: Enter a short name for the system. Click Apply. The System Properties window opens. 8 Click the Customers tab and then click the Add button. The Add Customer dialog window appears. See Figure 60 on page 262. IP Line Description, Installation, and Operation Page 262 of 770 Configuration of IP telephony nodes using OTM 2.2 Figure 60 System Properties window – Add Customer 9 Select the Customer Number. Click OK. This adds a customer to the system and opens the New - (Customer n) Properties window. 10 Click OK. The System Properties window opens. 11 Click OK to save and close the System Properties. 553-3001-365 Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 Page 263 of 770 Note: Only the Customer Number is required to add a system. There is no need to enter any other customer data. The other data in the Customer tab and other System Properties tabs is not required for the IP Line 4.0 application. This data is used by other OTM applications. End of Procedure The following is a summary of steps required to configure a Voice Gateway Media Card using OTM 2.2: 1 “Manually add an IP Telephony node” on page 264. 2 “Configure the card properties of the Voice Gateway Media Card” on page 268. 3 “Configure DSP profile data” on page 271. 4 “Configure SNMP traps and ELAN gateway routing table” on page 275. 5 “Configure the Call Server ELAN IP address and the TLAN voice port” on page 282. 6 “Configure security for SNMP access” on page 284. 7 “Configure file server access” on page 290. 8 “Configure QoS” on page 292. IP Line Description, Installation, and Operation Page 264 of 770 Configuration of IP telephony nodes using OTM 2.2 Manually add an IP Telephony node Follow the steps in Procedure 21 to manually add an IP Telephony node. Procedure 21 Adding an IP Telephony node manually 1 In the OTM Navigator window, click on the Services folder. 2 Double-click the IP Telephony icon. See Figure 55 on page 257. The IP Telephony window opens. 3 Click Configuration > Node > Add. See Figure 61. Figure 61 IP Telephony main window The Add Node dialog box opens.See Figure 62 on page 265. 553-3001-365 Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 4 Page 265 of 770 Ensure the “Define node configuration manually” radio button is selected. Select the IP Line software release being installed. Click OK. Figure 62 Add Node The New Node window opens. See Figure 63 on page 266. IP Line Description, Installation, and Operation Page 266 of 770 Configuration of IP telephony nodes using OTM 2.2 Figure 63 New Node – General tab 5 On the General tab, under Node Location: a. 553-3001-365 From the drop-down lists, select an OTM site, OTM system, and Customer number. Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 b. Page 267 of 770 Type in a Node number (one to four digits). The Node Number field in the tab corresponds to the Node ID field in the IP Phone configuration. When defining the node number, determine if the Enhanced Redundancy for IP Line Nodes functionality is required (see “Enhanced Redundancy for IP Line nodes” on page 142). If it is required, factor the requirement into the node number assignment process. CAUTION The Voice Gateway Media Cards identify themselves with a node using the node number. If there are multiple IP Telephony nodes sharing the same TLAN, each node must have a unique ID. Each system on the TLAN must have a unique node ID assigned to the Voice Gateway Media Cards on the system. c. 6 Write down the node number, which is used in the IP Phone configuration. Under Network Connections: a. Voice LAN Node IP: Enter the Voice LAN (TLAN) Node IP address in dotted decimal format. Press the space bar to move between each decimal point. The Voice LAN Node IP is on the TLAN. The Node IP address is the IP address used by the IP Phones to communicate with the Voice Gateway Media Cards on the TLAN. If a Voice Gateway Media Card becomes the primary (Leader) during an election, it assigns itself the Node IP address. b. Management LAN gateway IP: Enter the Management LAN (ELAN) gateway IP address in dotted decimal format. This is the IP address of the gateway of the subnet to which the Voice Gateway Media Card belongs. This is the IP address of the router interface on the ELAN, if present. If there is no management LAN gateway, enter 0.0.0.0. c. Management LAN subnet mask: Enter the Management LAN (ELAN) subnet mask address in dotted decimal format. This is the subnet mask that is used, along with the ELAN network interface IP address, to identify the subnet to which the Voice Gateway Media Card belongs. IP Line Description, Installation, and Operation Page 268 of 770 Configuration of IP telephony nodes using OTM 2.2 d. 7 Voice LAN subnet mask: Enter the Voice LAN (TLAN) subnet mask address in dotted decimal format. This is the subnet mask used along with the TLAN IP address, to identify the subnet to which the Voice Gateway Media Card belongs. Click the Configuration tab and continue with Procedure 22 on page 269. End of Procedure Configure the card properties of the Voice Gateway Media Card If the IP Network Administrator provides IP addresses and subnet masks in CIDR format, for example, “10.1.1.10/24”, convert the subnet mask to dotted decimal format. See Appendix E on page 761. Note 1: On the Configuration tab, cards can be added, changed, or deleted in the node one at a time. Note 2: The Leader 0 card cannot be deleted in the Configuration tab. It is necessary to delete the node to delete Leader 0. Follow the steps in Procedure 22 on page 269 to configure card properties for the Voice Gateway Media Card. 553-3001-365 Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 Page 269 of 770 Procedure 22 Configuring card properties for the Voice Gateway Media Card 1 Click the Configuration tab in the New Node window. See Figure 64. Figure 64 New Node – Configuration tab IP Line Description, Installation, and Operation Page 270 of 770 Configuration of IP telephony nodes using OTM 2.2 2 Enter the Card Properties data for the Leader 0 and Follower cards as follows: a. Card role: Assign the Card role of Leader 0, to the first card configured. For the second card configured, assign the role of Leader 1. For all remaining cards, assign the role of Follower. Note: When adding cards for a node that resides on a CS 1000S system for the purpose of retrieving OM reports, always assign the Signaling Server to be the Leader 0 card. A backup Signaling Server, if present, is assigned to be the Leader 1 card and all the Voice Gateway Media Cards in the node are assigned to be Follower cards. If no Backup Signaling Server is present, assign one of the Voice Gateway Media Cards in the node to be the Leader 1 card. 553-3001-365 b. Management IP: This is the ELAN network interface IP address for the card. OTM 2.2 and Meridian 1/CS 1000M use this address to communicate with the card. c. Management MAC: This is the motherboard Ethernet address from the “Voice Gateway Media Card installation summary sheet” on page 199. d. Voice IP: This is the TLAN IP address for the card. e. Voice LAN gateway IP: This is the IP address of the router interface on the TLAN. f. Card TN: For Large Systems, enter Card TN (l s c) information. For Small Systems and CS 1000S systems, enter two zeros followed by the card slot number (1-50); for example, 0 0 49. The card TN format is determined by the system type that is configured in the OTM Navigator. Ensure the correct system type is entered in the OTM Navigator before adding the node. g. Card Type: Choose either Pentium or StrongArm. Select Pentium if using a ITG-P 24-port line card (dual-slot card). Select StrongArm if using a Media Card (single-slot card). h. Click Add. The card role and address information appears in a working list at the bottom of the New Node window. i. Repeat the above steps for each card that is being added to the node. Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 3 Page 271 of 770 Click Apply to add the card(s) to the Node. Note: When Apply is clicked, the title of the window changes from New Node to Node Properties. End of Procedure Configure DSP profile data In OTM 2.2, the DSP Profile tab and its two sub-tabs (DSP Options and Codec Options) are used to configure DSP profile data. Follow the steps in Procedure 23 to configure DSP profile data. Procedure 23 Configuring DSP profile data using OTM 1 Click the DSP Profile tab. The DSP Options sub-tab opens. See Figure 65 on page 272. IP Line Description, Installation, and Operation Page 272 of 770 Configuration of IP telephony nodes using OTM 2.2 Figure 65 New Node – DSP Profile tab Table 56 lists the configurable DSP parameters, the range of the values, and the default values. Table 56 DSP parameters (Part 1 of 2) Parameter Range Default value Enable DTMF tone detection checked or unchecked checked Enable echo canceller checked or unchecked checked Echo canceller tail delay 64 or 128 ms 128 ms Idle noise level –327 to +327 dB –65 553-3001-365 Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 Page 273 of 770 Table 56 DSP parameters (Part 2 of 2) Parameter Range Default value Voice activity detection threshold –20 to +10 dB –17 dB Enable V.25 FAX/Modem tone detection checked or unchecked checked Enable V.21 FAX tone detection checked or unchecked checked FAX maximum rate 2400, 4800, 7200, 9600, 12000, 14400 bps 14400 bps FAX playout nominal delay 0 – 300 ms 100 ms FAX no activity timeout 10 – 32000 seconds 20 seconds FAX packet size 20 – 48 bytes 30 bytes 2 Click the Codec Options sub-tab. See Figure 66 on page 275. Up to four codecs can be selected. Note: The T.38 Fax and G.711 Clear Channel Fax codecs are not counted in this limit. The G.711 codec type is mandatory and is automatically selected. Recommendation Nortel Networks recommends that the system be configured with both G.711 and G.729A if there is a possibility that IP Softphone 2050 could be configured with the “I use a modem to connect to the network” check box checked. If the node does not have G.729A and/or G.723 configured, IP Softphone 2050 users with that checkbox selected will have calls blocked. (Note: This does not apply to the MVC 2050.) For more information, refer to IP Phones: Description, Installation, and Operation (553-3001-368) in the “Select Sound Devices tab” section. IP Line Description, Installation, and Operation Page 274 of 770 Configuration of IP telephony nodes using OTM 2.2 3 Under Codec Options, the following parameters are user-configurable on a per-codec basis: Leave the values at their default settings unless directed to change them as follows or by Nortel Networks Field Support. a. Law type: The law type is applicable to G.711 only. The default is mu-law. b. Voice Activity Detection: The default is VAD disabled. The VAD value is stored in the Config.ini file under the entry VadEnabled= VAD is not supported for G.711. c. Voice payload size: The default is the maximum supported. This parameter is not configurable for the following: • G.723.1 • T.38 Fax • G.711 Clear Channel Fax The payload size is stored in the Config.ini file under the entry VxPayload= d. Voice playout nominal delay (nominal jitter buffer) Voice playout maximum delay (maximum jitter buffer) The default values and the range of allowed values are displayed in the drop-down lists. 4 553-3001-365 Click OK. Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 Page 275 of 770 Figure 66 New Node – DSP Profile tab - Codec Options sub-tab with G.729 AB Codec selected Note: If there are multiple nodes on a system and the same codec is selected on more than one node, ensure that each node has the same voice payload size configured for the codec. End of Procedure Configure SNMP traps and ELAN gateway routing table Follow the steps in Procedure 24 to configure SNMP traps and the ELAN gateway routing table. Procedure 24 Configuring SNMP traps and ELAN GW Routing table 1 Click the SNMP Traps/Routing and IPs tab in the New Node window. See Figure 67 on page 276. IP addresses that are added in this tab create special card routing tables that direct packets out the ELAN and ELAN gateway. Exercise caution when adding entries since the entry could result in one-way voice transmission if a change results in voice packets being streamed out the ELAN network interface instead of the TLAN network interface. IP Line Description, Installation, and Operation Page 276 of 770 Configuration of IP telephony nodes using OTM 2.2 Figure 67 New Node – SNMP Traps/Routing and IPs tab 2 553-3001-365 On the left side of the window, under SNMP traps: a. Enable SNMP traps: Check the Enable SNMP traps checkbox, if configuring one or more SNMP management IP addresses to receive SNMP traps from cards in the IP Telephony node. b. IP address: If SNMP traps are enabled, this is the IP address of the destination where the SNMP traps are sent. c. Subnet mask: If SNMP traps are enabled, this is the subnet mask of the destination where SNMP traps are sent. Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 Page 277 of 770 To add a trap destination IP address, enter the IP address in the SNMP IP address fields, and click Add. Add SNMP Manager IP addresses for the following: — local or remote OTM server — PPP IP address configured in the router on the ELAN subnet for the remote support OTM PC — SNMP manager for remote alarm monitoring Note 1: Up to six SNMP trap destinations can be defined. Note 2: A net route or host route through the ELAN gateway is added to the Voice Gateway Media Cards IP Routing Table for each SNMP management address that is added to the SNMP traps list. 3 Click Apply. 4 To transmit the information to the node, from the menu select Configuration > Synchronize > Transmit. 5 On the SNMP Traps/Routing and IPs tab on the right side of the window, under Card routing table entries, enter the IP address and Subnet mask for any host that is not on the ELAN subnet but requires access to the Voice Gateway Media Card across the ELAN. A Telnet session for maintenance from a remote PC is an example of when this would be needed. The address of the remote PC would be added in the Route list. IP Line Description, Installation, and Operation Page 278 of 770 Configuration of IP telephony nodes using OTM 2.2 The default route on the card causes packets for unknown subnets to be sent out on the TLAN network interface. Packets from an external host arrive on the ELAN network interface and responses are sent on the TLAN network interface. This can cause one-way communication if the TLAN subnet is not routed to the ELAN subnet. It is necessary to add an entry in the Route list, to correct the routing so that response packets are sent on the ELAN network interface. Each entry creates a route entry in the card's route table that directs packets to the ELAN network interface. See Figure 68 on page 279. CAUTION Use caution when assigning card routing table entries. Do not include the IP address of an IP Phone. Otherwise, voice traffic to this IP Phone is incorrectly routed through the ELAN and ELAN gateway. To avoid including the wrong IP address, Nortel Networks recommends that Host IDs be defined for the card routing table entries. 553-3001-365 6 To add a net route or host route, type the IP address and subnet mask in the entry field of the card routing table, and click Add. 7 Click Apply. Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 Page 279 of 770 Figure 68 Specifying additional ELAN routes ELAN subnet ELAN route+ additional routes TLAN route/ default route TLAN subnet Meridian 1 or CS 1000 Some other LAN Management Workstation In this diagram, an additional ELAN route is required to reach the management workstation, which is accessible through the ELAN interface but is not on the ELAN subnet. 8 Click OK to exit the window. End of Procedure Configure node synchronization with the Call Server The SNMP MIB II parameters are configured as a node property in the group box “SNMP parameters” on the New Node - General tab. See Figure 69 on page 280. The check box enables/disables synchronization of the SNMP parameters with the Call Server. The default value is selected. During Update System Data, the SNMP parameters are propagated to all existing IP nodes that have the “Synchronize with PBX system” option selected. Status of the node is set to changed (CHG). IP Line Description, Installation, and Operation Page 280 of 770 Configuration of IP telephony nodes using OTM 2.2 When the check box is selected, the fields are set to read-only. When the check box is not selected, the fields are set to read/write, and synchronization does not occur for that node. Follow the steps in Procedure 25 to configure node synchronization with the Call Server. Procedure 25 Configuring node synchronization with the Call Server 1 Click the Node Properties - General tab for the desired node. See Figure 69. Figure 69 SNMP parameters 553-3001-365 Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 Page 281 of 770 2 Check the Synchronize with PBX system during Update System Data check box. 3 Click Apply. 4 Click OK to exit the window. End of Procedure IP Line Description, Installation, and Operation Page 282 of 770 Configuration of IP telephony nodes using OTM 2.2 Configure the Call Server ELAN IP address and the TLAN voice port Follow the steps in Procedure 26 to configure the Call Server IP address (Active ELNK) and the TLAN voice port. Procedure 26 Configuring the Call Server ELAN IP address (Active ELNK) and the TLAN voice port 1 Click the Ports tab. See Figure 70. Figure 70 New Node – Ports tab 553-3001-365 Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 2 Page 283 of 770 Enter the following ELAN settings: a. Call Processor IP: Enter the Call Processor ELAN IP Address (Active ELNK). Note: The Call Processor ELAN IP address must correspond to the Active ELNK IP address configured in LD 117. It must be in the same subnet as the ELAN for the IP Telephony node. b. Survival Cabinet IP: If applicable, enter the Survivable Cabinet ELAN IP address (Active ELNK). This is the IP address that is configured for survivability. The survivable Cabinet IP is enabled only for Small Systems and CS 1000S systems. Note: For Small Systems or CS 1000S, this field is disabled unless at least one cabinet has been defined as a survival cabinet of the main system in OTM Navigator. There is only one survival cabinet IP address for each node. The survival cabinet is equipped with sufficient trunk cards and Voice Gateway Media Cards. In case of Call Server equipment failure, it provides a large degree of survivability for IP Phone users. 3 c. Signaling port: The default value is 15000. This field is read-only. d. Broadcast port: The default value is 15001. This field is read-only. Enter the following TLAN settings: a. Signaling port: b. Voice port: Change the Voice port only as instructed by the IP network administrator to improve QoS for the IP Phones. For example, if RTP Header compression is used to reduce voice bandwidth on narrow-band WAN links, then TLAN voice port range must be set to 16384 or higher. The exact range will be provided by the system administrator. Note: The TLAN Voice port range is 1024 to 65535. The default Voice ports are 5200-5295. IP Line Description, Installation, and Operation Page 284 of 770 Configuration of IP telephony nodes using OTM 2.2 Note 3: The TLAN Signaling occurs on UDP ports 7300, 4100, 5100, and 5000. CAUTION Do not set the Voice port to a value that is already used for signaling (4100, 5000, 5100, 7300). The Voice port defines the first port in a range spanning the gateway channels on the card; this means a Voice port value of 5200 reserves the following: • ports 5200-5263 on the Media Card 32-port line card • 5200-5215 on the Media Card 8-port line card • 5200-5247 on the ITG-P 24-port line card. If this value is changed from the default, confirm the selected Voice port value does not range into one of the reserved signaling port values. 4 Click Apply. End of Procedure Configure security for SNMP access Change the SNMP community names to control access to the IP Telephony node. OTM uses the community names to refresh the Voice Gateway Media Card status, and to control the transmitting and retrieving of configuration data files for database synchronization. Use OTM to configure SNMP on the Meridian 1 Call Server and Voice Gateway Media Cards. Configure SNMP access and community name strings Follow the steps in Procedure 27 on page 285 to configure SNMP access for the system. 553-3001-365 Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 Page 285 of 770 Procedure 27 Configuring SNMP access and community name strings 1 Click the General tab on System properties. See Figure 71. Figure 71 System properties - General tab 2 Enter the System Name data. 3 Select the Configure SNMP parameters using OTM data in this tab during Update System Data check box. IP Line Description, Installation, and Operation Page 286 of 770 Configuration of IP telephony nodes using OTM 2.2 4 Change the default System Mgmt Read, System Mgmt Read/Write, Admin 1, Admin 2, and Admin 3 community names. 5 Enter the System Location and Contact Information data. 6 Click Apply. 7 Click OK to exit the window. 8 To update the system data, from the System Window menu bar, click File > Update System Data. The Update System Data dialog box opens. See Figure 72. Figure 72 Update System Data dialog box 9 Select Update the data stored in the PC. 10 Click OK to update the system data. End of Procedure SNMP community name strings (passwords) are required to access the Voice Gateway Media Card. The community name strings are not configured on the 553-3001-365 Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 Page 287 of 770 Security tab. They are displayed as read-only for information purposes. See Figure 73. Community name strings are configured on the System Properties - General tab. See Procedure 27 on page 285. Figure 73 Node Properties – Security tab Configure SNMP trap destinations for an IP Telephony node Follow the steps in Procedure 28 on page 288 to use OTM to configure SNMP trap destinations for an IP Telephony node. IP Line Description, Installation, and Operation Page 288 of 770 Configuration of IP telephony nodes using OTM 2.2 Procedure 28 Configuring SNMP trap destinations for an IP Telephony node 1 Click the SNMP Traps/Routing and IPs tab in the Node Properties window. See Figure 67. Figure 74 Node Properties – SNMP Traps/Routing and IPs tab 2 553-3001-365 On the left side of the window, under SNMP traps: a. Enable SNMP traps: Select the Enable SNMP traps check box, if configuring one or more destination SNMP management IP addresses to receive SNMP traps from cards in the IP Telephony node. b. IP address: If SNMP traps are enabled, this is the IP address of the destination where the SNMP traps are sent. Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 c. Page 289 of 770 Subnet mask: The subnet mask for the IP address of the trap destination must always be configured as 255.255.25.255. WARNING Do not enter the actual value of the subnet mask on the interface of the SNMP trap destination. Doing so can cause misrouting of RTP media and signaling, leading to no speech path between the IP Phones and the Voice Gateway Media Cards or failure of the IP Phones to register with the LTPS. d. To add a trap destination IP address, enter the IP address and subnet mask (if applicable) in the SNMP IP address field, and click Add. Add trap destination IP addresses for the following: — local or remote OTM server — PPP IP address configured in the router on the ELAN for the remote support OTM PC — SNMP manager for remote alarm monitoring Note: Up to six SNMP trap destinations can be defined. 3 Click Apply. 4 Click OK to exit the window. 5 To transmit the information to the node, from the menu select Configuration > Synchronize > Transmit. End of Procedure Note: If the community names are forgotten, connect a TTY to the Voice Gateway Media Card maintenance port. Restart the card. The card displays the community name on the TTY during start-up. IP Line Description, Installation, and Operation Page 290 of 770 Configuration of IP telephony nodes using OTM 2.2 Configure file server access With the addition of new IP Phones, there are also additional firmware files for the IP Phones. The Voice Gateway Media Card has limited space to store the files for all the IP Phones on the card. Instead, a file server can be used to store the IP Phone firmware files. The Phase I IP Phone 2002 firmware filename is 0603Bnn.BIN where Bnn = firmware version 1.nn. The Phase I IP Phone 2004 firmware filename is 0602Bnn.BIN where Bnn = F/W version 1.nn. The Phase II IP Phone 2001, IP Phone 2002, and IP Phone 2004 firmware filename is 0603Dnn.BIN where Dnn = F/W version 3.nn. External file server option If the external file server option is used in OTM 2.2 for firmware distribution with a node, the following files must be renamed before being placed on the server. • 0602Bnn.BIN file renamed to i2004.fw • 0603Bnn.BIN file renamed to i2002.fw • 0604Dnn.BIN renamed to IPP2SETS.fw To configure the file server, follow the steps in Procedure 29 on page 291. 553-3001-365 Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 Page 291 of 770 Procedure 29 Configuring access to the File Server 1 Click the File Server tab. See Figure 75. Figure 75 New Node – File Server tab 2 Under File Server Parameters, specify the parameters needed to connect to the file server: a. File Server IP: Enter the IP address of the file server. b. Subnet Mask: Enter the subnet mask of the file server. c. User ID: Enter the user ID that is required to access the file server. d. Password: Enter the password that is required to access the file server. e. Location of the firmware files: Enter the path for the location of the firmware files. See page 132 for the default location of firmware files for the system. IP Line Description, Installation, and Operation Page 292 of 770 Configuration of IP telephony nodes using OTM 2.2 3 Click Apply. End of Procedure Configure QoS Configure QoS by enabling 802.1Q and NAT support, configuring DiffServ CodePoint (DSCP) settings, and configuring OM QoS thresholds. Procedure 30 Enabling 802.1Q and configuring DSCP settings 1 Click the QoS tab. See Figure 76. Figure 76 New Node – QoS tab 553-3001-365 Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 2 Page 293 of 770 802.1Q enables virtual LANs (VLANs) to be defined within a single LAN. This improves bandwidth management and limits the impact of broadcast and multicast messages. Configure the 802.1Q settings as follows: a. Enable 802.1Q support: Select the check box to enable 802.1Q support. By default, 802.1Q support is disabled. b. Priority Bits value (802.1p): The priority field is a 3-bit value, with a default value of 6. The range is 0 – 7. A value of 6 is recommended by Nortel Networks. The p bits within the 802.1Q standard enables packet prioritization at Layer 2, improving network throughput for IP Telephony data. Note: These values are applied to all Voice Gateway Media Cards in the node. 3 Under DiffServ Codepoint, modify the DSCP Control and Voice values only as directed by the IP network administrator. The recommended configuration values are: a. Control packets: A value of 40 – Class Selector 5 (CS5). This sets the priority of the signaling messaging. b. Voice packets: A value of 46 Control DSCP – Expedited Forwarding (EF). The DSCP determines the priorities of the management and voice packets in the IP Line network. The range for both management and voice packet DSCP is 0 – 63 inclusive. The DSCP value can be configured, if required, to obtain better QoS over the IP data network (LAN/WAN). The value entered depends on the policy in the customer’s data network. Note: Do not change DSCP from the default values unless instructed. 4 Click Apply and then click OK. Note: As described on the QoS tab, NAT and QoS parameters are no longer configured here. Therefore, those areas are grayed out. End of Procedure IP Line Description, Installation, and Operation Page 294 of 770 Configuration of IP telephony nodes using OTM 2.2 Configure SNTP Simple Network Time Protocol (SNTP) can be configured for an SNTP Server and SNTP Client. See Figure 77. Figure 77 SNTP configuration tab SNTP Server parameters The following are the parameters for the SNTP Server: 553-3001-365 • Mode: Can be configured as active or passive. The default is active. • Intervals (seconds): The range is 0 –2147483646. The default is 256. • Port: The range is 0 – 99999. The default is 20000 + the Node number. Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 Page 295 of 770 Note: The Node number is the same value as the value stored in the Node number field in the main IP Telephony application window. SNTP Client parameters The following are the parameters for the SNTP Client: • Mode: Can be configured as active or passive. The default is passive. • Intervals (seconds): The range is 0 –2147483646. The default is 256. • Port: The range is 0 – 99999. The default is 20000 + the Node number. • SNTP Server IP address. The default is 0.0.0.0. Note: The Node number is the same value as the value stored in the Node number field in the main IP Telephony application window. Transmit node configuration from OTM 2.2 to the Voice Gateway Media Cards Before transmitting the node configuration to the Voice Gateway Media Cards, ensure the following: • Voice Gateway Media Cards and cables have been installed. • ELAN and TLAN network interfaces of all cards are connected with access to the IP network. • IP Line 4.0 data has been configured in OTM 2.2. • OTM 2.2 server is connected to the local ELAN subnet or to a remote subnet with IP router access to the ELAN and TLAN subnets. The IP Telephony node and card properties are configured using OTM 2.2’s IP Line 4.0 application. The configuration data is converted to text files by OTM 2.2 and is then transmitted to the Voice Gateway Media Cards. The process consists of the following steps: 1 Set the Leader 0 IP address from a TTY connected to the local RS-232 maintenance port. See Procedure 31 on page 296. 2 Reboot Leader 0. IP Line Description, Installation, and Operation Page 296 of 770 Configuration of IP telephony nodes using OTM 2.2 3 Transmit the node and card properties from the OTM IP Line 4.0 application to Leader 0. See Procedure 32 on page 298. 4 Reboot Leader 0. 5 Transmit card properties to all cards in the node. See Procedure 33 on page 300. Set the Leader 0 IP address Follow the steps in Procedure 31 to set the IP address of a factory-new Leader 0 Voice Gateway Media Card. If the card is being re-used from an existing installation, enter the commands NVRClear, followed by clearLeader, at the card’s CLI. Procedure 31 Setting the Leader 0 IP address 1 Access the IPL> CLI by connecting the COM port of an OTM 2.2 PC to the RS-232 serial maintenance port on the faceplate of the Leader 0 Voice Gateway Media Card. Use an NTAG81CA PC Maintenance cable. If required, use an NTAG81BA Maintenance Extender cable between the PC Maintenance cable and the OTM PC. Alternatively, connect the NTAG81BA Maintenance Extender cable to the female DB-9 connector of the NTMF94EA ELAN, TLAN RS-232 Ports cable for a more permanent connection to the Voice Gateway Media Card serial maintenance port. Note: Never connect two terminals to the faceplate and I/O panel breakout cable serial maintenance port connectors at the same time. 2 3 553-3001-365 Use the following communication parameters for the TTY terminal emulation on the OTM PC: • 9600 baud • 8 bits • no parity • one stop bit Observe the Leader 0 card faceplate maintenance display window. Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 Page 297 of 770 When the display reads “T:20”, it begins to send BootP requests on the ELAN. A series of dots is printed on the TTY. If the card does not display “T20”, or has stopped printing the series of dots on the TTY, reboot the card and wait for “T20” to be displayed. 4 Type +++ to escape from the BootP request. 5 At the Login prompt, enter the default user ID and password of itgadmin and itgadmin to access the IPL> CLI: itg Login: itgadmin Password: itgadmin 6 When the maintenance window displays “T:21”, at the IPL> prompt, enter: setLeader “xx.xx.xx.xx”,“yy.yy.yy.yy”,“zz.zz.zz.zz” The three parameters must each be enclosed in double quotation marks. Ensure that there is a space after the command and before the first parameter. Put commas and no spaces between the following parameters: “xx.xx.xx.xx”=IP address. Enter the same IP address that was entered in the Management LAN IP field for Leader 0 in the Configuration tab of the Node Properties window. “yy.yy.yy.yy”=Gateway IP address. Enter the same address that was entered in the Management LAN gateway IP field in the General tab of the Node Properties window. If there is none, enter the following: “0.0.0.0” “zz.zz.zz.zz”=Management LAN subnet mask. Enter the same address that was entered in the Management LAN subnet mask field in the General tab of the Node Properties window. Note: This step assumes that the new IP Telephony node has already been configured in OTM 2.2. 7 Reboot the Leader 0 Voice Gateway Media Card. At the IPL> prompt, enter: cardReset, or press the Reset button on the faceplate of the Leader 0 Voice Gateway Media Card. 8 Check the maintenance display for T:22 to confirm a successful reboot. IP Line Description, Installation, and Operation Page 298 of 770 Configuration of IP telephony nodes using OTM 2.2 9 From the OTM IP Telephony Gateway - IP Line 4.0 application, select View > Refresh to show the card status. Otherwise, verify LAN connections and IP configuration. End of Procedure Transmit node and card properties to Leader 0 To transmit the node and card properties to Leader 0, follow the steps in Procedure 32. CAUTION OTM 2.2 does not support transmitting node and/or card properties to a node (or any of the card within the node) which resides on a CS 1000 system. Procedure 32 Transmitting node and card properties to Leader 0 1 Log into LD 32 on the system. Disable the card in order to transmit the card properties. 2 Open OTM. From the OTM Navigator window, click on the Services folder to expand the menu. Double-click on IP Line 4.0. The IP Telephony Gateway - IP Line 4.0 window opens. 3 From the list of IP Telephony nodes in the upper part of the window, select the node to which configuration data is to be transmitted. 4 Select the Configuration > Synchronize > Transmit. The Transmit Options window appears. See Figure 78 on page 299. 553-3001-365 Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 Page 299 of 770 Figure 78 Transmit Options dialog box 5 Use the default setting of Transmit to selected nodes. Select both the Node Properties to Active Leader and the Card properties to all cards in the node check boxes.? IP Line Description, Installation, and Operation Page 300 of 770 Configuration of IP telephony nodes using OTM 2.2 6 Click the Start transmit button. Monitor progress in the Transmit control area. Confirm that the node and card properties are transmitted successfully to Leader 0. Note: At this point, it is normal that the card properties fail to transmit to the other cards in the node, because they have not yet received the IP address from Leader 0 BootP server. 7 When the transmission is complete, click Close. 8 Reboot the Leader 0 Voice Gateway Media Card. At the IPL> prompt, enter cardReset. Alternatively, push the Reset button on the faceplate of the Voice Gateway Media Card. End of Procedure Transmit card properties to all cards in the node To transmit the card properties to all the Voice Gateway Media Cards in the node, follow the steps in Procedure 33. CAUTION OTM 2.2 does not support transmitting node and/or card properties to a node (or to any of the cards within the node) which resides on a CS 1000 system. Procedure 33 Transmitting card properties to all cards in the node 1 553-3001-365 To verify installation and configuration of the node properties, observe the displays on the card faceplate. • After successfully rebooting, the Leader 0 card is now fully configured with the Node Properties of the node and enters a state of “active Leader”. The card faceplate display shows Lxxx, where xxx = the number of IP Phones registered with the LTPS on the Leader card. L000 means that no IP Phones are registered. • The Leader 1 card and any Follower cards receive their configuration from the Leader 0 card. The faceplate display shows Fxxx, where xxx = the number of IP Phones registered with the LTPS on the Leader card. F000 means that no IP Phones are registered. Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 2 Page 301 of 770 In the IP Telephony window, select the new IP Telephony node from the list in the upper part of the window. All Voice Gateway Media Cards in the node are displayed in the lower part of the window. See Figure 79. Figure 79 IP Telephony window 3 Press function key F5 to refresh the card status of all cards in the selected node. Alternatively, from the upper menu, select View > Refresh > Selection. The card status changes from “Unknown” or “Not responding” to “Disabled”, “Enabled”, and “Unequipped”. Note: If it is not possible to communicate with the Leader 1 and Follower cards in the node after transmitting the node and card properties and rebooting the Leader 0 card, this means that the Voice Gateway Media Cards are unable to communicate back to the remote OTM PC through the voice gateway or TLAN router. IP Line Description, Installation, and Operation Page 302 of 770 Configuration of IP telephony nodes using OTM 2.2 To establish communication with the Leader 1 or Follower cards in the IP Telephony node, perform the following actions: a. Verify the TLAN physical and logical connections on all the non-responsive cards. Ensure the following: i. cables are plugged securely into the correct TLAN connection ii. switch is connected to correct TLAN router iii. remote OTM can communicate with TLAN router b. If remote OTM 2.2 cannot communicate using the TLAN router, connect to the Voice Gateway Media Card maintenance port with a TTY and use the IPL> routeAdd command on each Voice Gateway Media Card to add a new IP route through the management gateway that points to the remote OTM PC subnet. c. Repeat step b if the card is reset before OTM successfully transmits the card properties (containing the SNMP Manager IP addresses and the card routing IP addresses). 4 When Leader 1 and all Follower cards show a status of disabled, click Configure > Synchronize > Transmit. When the Transmit window opens, click the Transmit to selected nodes radio button. Select the Card properties to all disabled cards check box. 5 Click Start transmit. Carefully monitor the progression in the Transmit Control window. Confirm that the card properties are successfully transmitted to every Voice Gateway Media Card in the selected node identified by its TN 6 Verify that all Voice Gateway Media Cards in the node have established a signaling link to the Call Server. End of Procedure 553-3001-365 Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 Page 303 of 770 Upgrade the Voice Gateway Media Card software and IP Phone firmware WARNING Before beginning the upgrade, ensure that a PWD1 user name and password has been configured on the Call Server. If there is no PWD1 user name and password, configure them in LD 17. This is necessary to enable login to the Voice Gateway Media Cards and Signaling Server. Before upgrading the software and firmware, determine the version of card software and IP Phone firmware that is currently installed. Compare the versions to the latest available versions by accessing the Nortel Networks web site. Refer to Procedure 34 on page 306 for complete instructions. When a software or firmware upgrade is required, go to the Nortel Networks web site to download the appropriate upgrade files. When Internet access is unavailable from the OTM PC, use a PC with Internet access and transfer the files to the OTM PC. See Appendix F on page 763. IP Phone firmware installation and upgrade The firmware files for the IP Phones are downloaded from OTM 2.2 to the node Master and saved in a directory on the Master card’s Flash disk. The node Master then notifies the other cards in the node to retrieve the new files. When those firmware files are downloaded from OTM, they are compressed and stored on the /C: drive. File compression reduces the firmware file to less than 900 Kbytes. There is no requirement on operations to pre-load the IP Phones with the correct version of firmware. Except in the case where the UFTP download to the IP Phone would be blocked (such as when the IP Phone is behind a firewall that has port 5105 blocked), the IP Phone’s firmware is automatically upgraded as part of the registration to the LTPS. If the firmware cannot be upgraded due to firewall restrictions, then upgrade the IP Phone with the current firmware version before distributing the telephone. IP Line Description, Installation, and Operation Page 304 of 770 Configuration of IP telephony nodes using OTM 2.2 There is one firmware file each for the Phase I IP Phone 2002 and 2004. There is one firmware file for the Phase II IP Phone 2001, IP Phone 2002, and IP Phone 2004. There is limited space on the Voice Gateway Media Card running IP Line 4.0 to store the firmware files. Therefore, the firmware is stored on a file server or on the Master card’s RAM device. Note: A firmware download does not occur with IP Phones performing a Virtual Office login or Branch Office login to a remote system. No firmware upgrade takes place during a Virtual Office Login or MG 1000B User registration with the LTPS. The registration is allowed because the IP Phone firmware version must be 1.33 or later to do a Virtual Office login or MG 1000B User registration. The umsUpgradeAll command has no impact on Virtual Office Login IP Phones. These IP Phones are not reset. If the Virtual Office Login is on the same Call Server, then the IP Phone firmware is upgraded after the user logs out. If the Virtual office Login is between different Call Servers, then the IP Phone just registers back to its home LTPS and follows the normal firmware rules for regular registration. When the umsUpgradeAll command is executed, MG 1000B User IP Phones that are on an active call are flagged. After the IP Phone becomes idle, the IP Phones are switched by the Call Server back to the MG 1000B for the firmware upgrade. Requirements If a file server is used to store the firmware file, the following items are required to access the firmware: 553-3001-365 • IP address of the file server • routing table • file path to the file server • user name and password required to access the file server Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 Page 305 of 770 This information is configured in the OTM 2.2 IP Line 4.0 application. If using OTM 2.2, this information is configured in the File Server tab of the Node properties. See Figure 75 on page 291. IMPORTANT! All IP Phones in a system must use the same version of firmware as is on the Voice Gateway Media Card(s).The same version of firmware for a specific IP Phone type must reside on all Voice Gateway Media Cards in a system. If retrieved from an external server, ensure all Voice Gateway Media Cards retrieve the same firmware files The IP Phones use UNIStim File Transfer Protocol (UFTP) to transfer the firmware; therefore, if the customer’s network has a firewall, port 5105 must be explicitly opened in the firewall to enable IP Phone firmware downloads to take place. For more information, refer to “Firmware download using UNIStim FTP” on page 83. CAUTION The OTM PC should not be used as the file server for the firmware download. IP Phone firmware upgrade from a new Voice Gateway Media Card Meridian 1 When the Voice Gateway Media Card is received from the factory, the IP Line 4.0 software is located on the CompactFlash card. Go to the Nortel Networks web site and download the firmware for the IP Phones to the Leader card. See Appendix F on page 763. IP Line Description, Installation, and Operation Page 306 of 770 Configuration of IP telephony nodes using OTM 2.2 As each IP Phone comes online, its firmware version is automatically compared to the version that is stored on the Voice Gateway Media Card. If they are different, the new firmware is downloaded from the Voice Gateway Media Card to the IP Phones. After the new firmware has been downloaded, the IP Phone reboots and registers again with the Voice Gateway Media Card. CS 1000M and CS 1000S For CS 1000M and CS 1000S systems, it is not necessary to download software and firmware files to the card. All required software and firmware files are on the Signaling Server Installation CD and are copied over at installation. The Signaling Server is the Leader, so all Voice Gateway Media Cards in the node go to the Signaling Server to obtain the IP Phone firmware files. Note: The IP Phone does not necessarily register with the same card as before the upgrade. Verify card software and IP Phone firmware Before beginning, ensure that the following software is installed on the PC: • Software to extract zipped files (WinZip or equivalent) • A web browser such as Microsoft Internet Explorer 6.0.2600 (or later) To verify the Voice Gateway Media Card software and the firmware on the IP Phone, follow the steps in Procedure 34. Procedure 34 Verifying card loadware and IP Phone firmware using OTM 2.2 1 In the OTM Navigator, select the Services folder. Double-click on the IP Line Telephony icon. The IP Telephony window opens. 553-3001-365 2 Select an IP Telephony node in the upper part of the window. A list of all line cards for that node appears in the lower part of the window. 3 Starting with the Leader 0 Voice Gateway Media Card, double-click each Voice Gateway Media Card in the list to open the Card Properties window. Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 Page 307 of 770 There are two tabs in the Card Properties window: Maintenance and Configuration. See Figure 80 and see Figure 81 on page 308. Figure 80 Card Properties – Maintenance tab 4 Keep the default settings shown in the Maintenance tab. Click the Configuration tab. See Figure 81 on page 308. IP Line Description, Installation, and Operation Page 308 of 770 Configuration of IP telephony nodes using OTM 2.2 Figure 81 Card Properties – Configuration tab The current Voice Gateway Media Card software and IP Phone firmware versions are displayed on the Configuration tab. The Voice Gateway Media Card software is labelled S/W version and the IP Phone firmware is labeled i2001, i2002, or i2004 F/W version. 5 553-3001-365 Write down the loadware and firmware version for each Voice Gateway Media Card. Compare the loadware and firmware version with the latest recommended software release on the Nortel Networks web site. Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 6 Page 309 of 770 Check the Nortel Networks web site for the latest IP Line 4.0 software and IP Phone firmware releases. Download the files. See Appendix F on page 763. Note: The IP Line 4.0 software files and IP Phone firmware files are contained in the IP Line 4.00xx. SA file in the Internet Telephony Gateway product list on the Nortel Networks web site. The zipped file contains the following: • The IPL400xx.p2 and IPL400xx.sa loadware files. The IPL400xx.p2 file is the IP Line 4.0 application for the ITG-P 24-port line card. The IPL400xx.sa is the IP Line 4.0 application for the Media Card. • The 0602Bxx.BIN (Phase I IP Phone 2004), 0603Bxx.BIN (Phase I IP Phone 2002), and 0604Dnn.BIN (Phase II IP Phone 2001, IP Phone 2002, and IP Phone 2004) firmware files. For example, a firmware version can be labelled 0602B38. This means IP Phone firmware version 1.38. • 7 — The 02 represents the IP Phone 2004. — The letter B represents the version number. — 38 represents the release number .38. A readme.txt file. The readme.txt file explains important considerations when installing the new software and firmware versions. The readme file also includes identifying information for the software and firmware files such as the date and time, size and checksum. Locate the saved file and double-click the *.zip file. The zipped file opens in a compression utility program and the uncompressed files are listed. 8 If the card’s software and firmware are not up-to-date, transfer the downloaded files (*.p2, *.sa, and firmware file(s)) from an Internet-enabled PC to the OTM PC. 9 If the card’s software and firmware are not up-to-date, upgrade the Voice Gateway Media Card with the software and firmware files. IP Line Description, Installation, and Operation Page 310 of 770 Configuration of IP telephony nodes using OTM 2.2 Refer to Procedure 35, “Upgrading Voice Gateway Media Card software from the OTM 2.2 PC” on page 311, and Procedure 37, “Upgrading the IP Phone firmware” on page 316 for detailed instructions on how to perform the upgrades. Note: All cards must be running the same version of the software. End of Procedure Upgrade options Once the Voice Gateway Media Card software and IP Phone firmware has been verified, there are three upgrade options: 1 Upgrade the Voice Gateway Media Card software. – In this case, perform Procedure 35 on page 311 only. This is the most frequently-used option is used; however, verify if an IP Phone firmware upgrade is also required. 2 Upgrade both the Voice Gateway Media Card software and IP Phone firmware. – In this case, perform a combination of Procedure 35 on page 311 and Procedure 37 on page 316. Note: Do not restart the Voice Gateway Media Cards until the end of Procedure 37, as restarting the cards restarts all the IP Phones. 3 Upgrade the IP Phone firmware. – In this case, perform Procedure 37 on page 316 only. Note: In this case, restart all IP Phones instead of all Voice Gateway Media Cards. To do this, select a single test IP Phone and reset the firmware only on that test telephone before completing the procedure on all IP Phones. If the upgrade works properly, use the umsUpgradeAll command to complete the upgrade on all the IP Phones. 553-3001-365 Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 Page 311 of 770 Upgrade Voice Gateway Media Card software To upgrade the software on the Voice Gateway Media Card, follow the steps in Procedure 35. If Procedure 34 has just been completed, the correct software should have been verified and obtained for the Voice Gateway Media Card, and the files transferred to the OTM PC. Note: A node can contain a mix of Media Cards 32-port and 8-port line cards and ITG-P 24-port line cards. Each card type has a different software version. If a node contains a mix of cards, the software upgrade must be performed separately for each card type. That is, upgrade the ITG-P 24-port line card’ software and then the Media Card line card’s software. Procedure 35 Upgrading Voice Gateway Media Card software from the OTM 2.2 PC 1 Open the OTM Navigator, and click on the Services folder. Double-click the IP Telephony icon. The IP Telephony window opens. 2 Select the Voice Gateway Media Cards that are to be upgraded from the main card list view. Upgrade all the cards in the node together, unless a spare card that has older software is being installed. 3 Disable all Voice Gateway Media Cards to be upgraded. Use the LD 32 DISI command from OTM Maintenance Windows, the OTM System Passthru terminal, or a system management terminal directly connected to a TTY port on the system. Note: Nortel Networks recommends that a Voice Gateway Media Card be disabled prior to upgrading the software. However, it is possible to perform the transfer of the software to the card while the card is enabled. A Voice Gateway Media Card does not have to be disabled to transfer the software, however, the card must be disabled before it is rebooted. 4 In the IP Telephony Gateway - IP Line 4.0 main window, select View > Refresh and verify that the card status is showing “Disabled.” 5 Select Configuration > Synchronize > Transmit. The Transmit Options dialog box is displayed. See Figure 82 on page 312. IP Line Description, Installation, and Operation Page 312 of 770 Configuration of IP telephony nodes using OTM 2.2 6 Under Transmit options, select the Transmit to selected cards radio button. Figure 82 Transmit Options window 553-3001-365 7 Select the Card software check box. 8 Click on the Browse button to the right of the Software location text box. Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 9 Page 313 of 770 Select the appropriate file filter (that is, *.sa, *.p2, *.mms, *.*) from the Files of type: drop-down list. 10 Locate the Voice Gateway Media Card software that was verified to be the correct version in Procedure 34 on page 306. Select the file and click Open to save the selection. The path and file name of the Voice Gateway Media Card loadware appears in the Software location text box. 11 Click Start transmit to begin the Voice Gateway Media Card software upgrade process. The software is transmitted to each card in turn, and burned into the flash ROM on the Voice Gateway Media Card. 12 Monitor progress in the Transmit control window. Confirm that the card software is transmitted successfully to all cards. Note any error messages, investigate and correct any problems, and repeat card software transmission until it is completed successfully for each Voice Gateway Media Card. The cards continue to run the old software until they are rebooted. 13 Reboot each Voice Gateway Media Card that received the transmitted software. This enables the new loadware to take effect. Reboot Leader 0 first, followed by the other cards. These cards must remain in the “Disabled” state after the upgrade, so that a “Reset” command can be issued from the Maintenance menu. Alternatively, click the Reset button on the Maintenance tab in the Card Properties window of each card to reboot the cards. Also, the cards can be reset by using a pointed object to press the “Reset” button on the card faceplate. WARNING Do not use a pencil to reset the Voice Gateway Media Card. The graphite carbon can create an electrical short circuit on the board. IP Line Description, Installation, and Operation Page 314 of 770 Configuration of IP telephony nodes using OTM 2.2 14 After all the Voice Gateway Media Cards have been reset, have successfully rebooted, and are responding again to the OTM 2.2 IP Line 4.0 application, do a Status refresh (disabled: active; disabled: backup; disabled). 15 Double-click each upgraded card and verify the card software version in the S/W version field of the Configuration tab in the Card Properties window. 16 Use the LD 32 ENLC command to re-enable the Voice Gateway Media Cards. Use LD 32 in the TTY or OTM Overlay passthru to re-enable the Voice Gateway Media Card with one of the following commands: • ENLC l s c (for Meridian 1 and CS 1000M Large Systems) • ENLC c (for Meridian 1 and CS 1000M Small Systems, and CS 1000S) 17 Repeat the previous two steps for each Voice Gateway Media Card. End of Procedure Upgrade the Voice Gateway Media Card software The minimum versions of IP Line 4.0 software for the Voice Gateway Media Card vintages earlier than NTVQ01BB and NTVQ01AB are: • Version 6.7 for the Media Card • Version 5.7 for the ITG-P 24-port card The minimum versions of IP Line 4.0 software for the Voice Gateway Media Cards NTVQ01BB and NTVQ01AB is Version 8.0. There is no need to download the Version 8.0 software for the Voice Gateway Media Cards NTVQ01BB and NTVQ01AB as the software is pre-loaded at the factory. Note: Refer to the ReadMe First document or the General Release Bulletin to ensure that the latest firmware is identified. To upgrade the IP Line software for the Voice Gateway Media Card, follow the steps in Procedure 36 on page 315. 553-3001-365 Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 Page 315 of 770 Procedure 36 Upgrading the Voice Gateway Media Card software 1 Check the Nortel Networks web site for the most current versions of the IP Line software for the ITG-P 24-port line card and Media Card line cards. 2 Once the most current version of the software has been downloaded, follow the steps in: • Procedure 99 on page 639 to upgrade the software on the ITG-P 24-port line card • Procedure 100 on page 642 to upgrade the software on the Media Card line cards End of Procedure Upgrade the IP Phone firmware When the IP Line 4.0 software has been upgraded on the Voice Gateway Media Card, verify if an IP Phone firmware upgrade is also required. Check the Readme First document for the OTM IP Line 4.0 application to determine which IP Phone firmware version is required to be compatible. Note: The firmware upgrade procedure does not apply to the IP Softphone 2050 and the MVC 2050. • In Procedure 34 on page 306, the correct software for the Voice Gateway Media Card should have been obtained and verified. The files should have been transferred to the OTM PC. • If using Procedure 35 on page 311 and Procedure 37 on page 316 together, do not restart the Voice Gateway Media Card until Procedure 37 is completed. All the cards must be restarted because the software has not been upgraded. The new software will not run until the cards are rebooted, because the new firmware is incompatible with the old software. • If using Procedure 37 on page 316 alone (a firmware upgrade only), it is only necessary to reboot the node. IP Line Description, Installation, and Operation Page 316 of 770 Configuration of IP telephony nodes using OTM 2.2 To upgrade the firmware on the IP Phone, follow the steps in Procedure 37. This procedure has two major steps: • placing the IP Phone firmware onto each card in the node • propagating the firmware from the card to each IP Phone registered on that card Procedure 37 Upgrading the IP Phone firmware 1 Open OTM Navigator, and click the Services folder. Double-click the IP Telephony icon. The IP Telephony window opens. 2 In the main card list view, disable all Voice Gateway Media Cards that are to be upgraded with the new firmware. All cards must have the same IP Phone firmware version. 3 Verify that all Voice Gateway Media Cards that require a firmware upgrade have established a signaling link with the Call Server. Note: The Voice Gateway Media Cards must first be disabled in order to update the firmware. Use the LD 32 DISI command from OTM Maintenance Windows, the OTM system Passthru terminal, or a system management terminal directly connected to a TTY port. To verify that the link is available between the Call Server and Voice Gateway Media Card, Telnet to each card and log in. From the command line, type pbxLinkShow. The status of the Call Server link appears. If the link is active, the screen displays the following: RUDPLinkState = Up 4 Select Configuration > Synchronize > Transmit. The Transmit Options dialog box is displayed. See Figure 83 on page 317. 553-3001-365 Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 Page 317 of 770 Figure 83 Transmit Options window 5 Under Transmit options, click the Transmit to selected nodes radio button. 6 Select the IP Phone firmware to Active Leader check box. 7 Click on the Browse button to the right of the Firmware location text box to locate the IP Phone firmware that was previously verified as required for the Voice Gateway Media Card software version. Select the firmware file, and click Open. IP Line Description, Installation, and Operation Page 318 of 770 Configuration of IP telephony nodes using OTM 2.2 The path and file name of the IP Phone firmware appears in the Firmware location text box. The IP Line 4.0 software determines the target IP Phone type (2001, 2002, or 2004) based on the firmware filename. A filename of the format xx02xxx.BIN (where “x” can be any alpha-numeric character) represents a firmware file for the Phase I IP Phone 2004. Similarly a filename of the format xx03xxx.BIN represents a firmware file for the Phase I IP Phone 2002. A filename of the format xx04xxx.BIN represents a firmware file for the Phase II IP Phone 2001, IP Phone 2002, and IP Phone 2004. . CAUTION Downloading an incorrect version of the IP Phone firmware can result in extended service interruptions and require special recovery procedures. 8 Click the Start transmit button to begin upgrading the IP Phone firmware on the Voice Gateway Media Cards. 9 Monitor progress in the Transmit control window. Confirm the card firmware is transmitted successfully to all cards. Note any error messages, investigate, correct any problems, and repeat card firmware transmission until it is completed successfully on each Voice Gateway Media Card. The IP Phones continue to run the old firmware until each telephone re-registers with a Voice Gateway Media Card that contains the new IP Phone firmware. Note: Commands are available from the IPL> command line to upgrade a single IP Phone immediately, all IP Phones immediately, or schedule all IP Phones to be upgraded at a later time. Before doing this, verify that each card has the correct firmware version and check the date and time on the node. 10 Select an IP Phone for test purposes. Telnet to the Voice Gateway Media Card. Log into the IPL> command line, and enter the following: iSetReset “xxx.xxx.xxx.xxx” where xxx.xxx.xxx.xxx is the IP Address of the selected IP Phone. 11 Monitor the display on the test telephone. As it upgrades the firmware, note the IP Address of the Voice Gateway Media Card from where the test telephone is receiving its upgrade. 553-3001-365 Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 Page 319 of 770 12 Press the Services key (key with globe with arrow pointing East and West) on the IP Phone. The Services key provides access the Telephone Options list. i. Press Select to select Telephone Options. ii. Use the Navigation keys to scroll to Set Info. iii. Press the Select softkey, then press the Navigation keys until it displays FW Version:. For the Voice Gateway Media Card, select the appropriate firmware. Note: For example, a firmware version can be labelled 0602B38, which means IP Phone firmware version 1.38. • 02 represents the IP Phone 2004. • B represents the Version number 1. • 38 represents the Release number .38 13 Lift the handset and make a call to verify the IP Phone works. 14 When the IP Phone is working, verify the date and time on the node. Ensure each Voice Gateway Media Card has the correct loadware and firmware before using the umsUpgradeAll command to upgrade all the IP Phones. To verify the date and time on the node from OTM 2.2, select the node in the top of the IP Telephony Gateway - IP Line 4.0 window. 15 Double-click on Leader 0 in the bottom of the window. The Card Properties window opens. Note: Cards receive their time from the Leader 0 card. If the time for Leader 0 is correct, all cards on the node should be the same. If Leader 0 displays the incorrect time, reset the time. The time propagates to the other cards. 16 Click the Maintenance tab. This displays the Node time. If the time is incorrect, click on the Set Node Time button. The Set Node Time window opens. Under Time and date, set the Time, where the time is displayed in the HH:MM:SS AM/PM format. Click OK to close the window. 17 Click the Configuration tab. Note the card’s software version and the IP Phone firmware version. IP Line Description, Installation, and Operation Page 320 of 770 Configuration of IP telephony nodes using OTM 2.2 Double-click on each card to verify the software and firmware version. Do this for every card. 18 Before proceeding, ensure the time on the card is set correctly. Telnet to each Voice Gateway Media Card and log in. At the IPL> command line, enter the following: umsUpgradeAll “hh:mma/p” hh:mma/p specifies the time when the upgrade will occur, a represents A.M., and p represents P.M. The time is in Standard format. Example: umsUpgradeAll “11:30a” or umsUpgradeAll “2:45p”. At the time specified, all the IP Phones on the Voice Gateway Media Card go out of service. This can take several minutes. Upon completion of the firmware upgrade, the IP Phones are brought back online in groups of ten. WARNING The umsUpgradeAll command (without the time parameter) causes the IP Phones registered on all cards that are logged into to be immediately taken out of service, unless the time parameter is specified. After the test telephone is working, the umsUpgradeAll does not need the time parameter. However, without the time parameter, the command immediately resets all the IP Phones currently registered on that line card. If the technician does not want to immediately reset all the phones, and wants to schedule the reset time of the IP Phones, check the time on all the cards. If necessary, reset the time to ensure all cards have the same time. Then issue the umsUpgradeAll “hh:mma/p” command, where “hh:mma/p” represents the time when the upgrade will occur. 19 At the IPL> prompt, verify that the IP Phones are upgraded for each Voice Gateway Media Card by entering the following command: isetShow Inspect the list to ensure all IP Phones have the correct firmware version. 553-3001-365 Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 Page 321 of 770 20 For any IP Phones that did not upgrade successfully, try one of the following (in order): • use the isetReset ''IP Address'' command • enter the following combination of keystrokes on the IP Phone: release, mute, up, down, up, down, up, mute, 9, release • power the IP Phone off and then on again If the upgrade was unsuccessful on any of the IP Phones, this is probably due to one of the following reasons: • one of the Voice Gateway Media Cards did not upgrade the software successfully • an IP Phone is loaded with a firmware version that was unable to be upgraded by the Voice Gateway Media Card in the normal manner • the umsUpgradeAll command was not issued • one of the cards has not been reset If the upgrade was unsuccessful, re-do the appropriate procedure. If the upgrade is still unsuccessful, contact the technical support representative for further assistance. End of Procedure For additional information on configuring the IP Phones, the IP Softphone 2050, and the MVC 2050, refer to IP Phones: Description, Installation, and Operation (553-3001-368). Upgrading the MVC 2050 For information on upgrading the MVC 2050 software, refer to the Nortel Networks Mobile Voice Client 2050 User Guide. IP Line Description, Installation, and Operation Page 322 of 770 Configuration of IP telephony nodes using OTM 2.2 Configure OTM Alarm Management to receive IP Line SNMP traps To configure the alarm notification feature in OTM 2.2 to receive SNMP traps, follow the steps in Procedure 38. For more information about OTM Alarm Management, refer to Optivity Telephony Manager: System Administration (553-3001-330). Procedure 38 Configuring SNMP Traps 1 In the OTM Navigator window, select the Utilities menu option and click on Alarm Notification. See Figure 84 on page 323. 553-3001-365 Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 Page 323 of 770 Figure 84 OTM Navigator – Utilities > Alarm Notification The OTM Alarm Notification window opens. 2 Select Configuration > Run Options. The Alarm Notification Run Options dialog box opens. 3 Click the Control Files tab. See Figure 85 on page 324. IP Line Description, Installation, and Operation Page 324 of 770 Configuration of IP telephony nodes using OTM 2.2 Figure 85 Alarm Notification Run Options – Control Files tab 4 Click the Browse button located to the right of the Devices text box. The Open dialog box opens. 5 Select the Devices file from the Control Files folder and click Open. See Figure 86 on page 325. 553-3001-365 Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 Page 325 of 770 Figure 86 Open dialog box The Devices.txt file opens. See Figure 87 on page 326. IP Line Description, Installation, and Operation Page 326 of 770 Configuration of IP telephony nodes using OTM 2.2 Figure 87 Devices.txt file 6 For each Voice Gateway Media Card in each monitored IP Telephony node, add a line consisting of three fields separated by spaces, as shown in Table 57 on page 327. Enter the first line under the last line that begins with a “#”. 7 Click File > Save As. Save the template as a new file, for example, ITGDevices1.txt, to avoid overwriting the template file. 8 In the Alarm Notification Run Options window, verify that the devices field name is correct (ITGDevices1.txt). Click Apply, and then OK. Note: OTM Alarm Notification must be restarted whenever Control Files are changed. 553-3001-365 Standard 3.00 September 2004 Configuration of IP telephony nodes using OTM 2.2 9 Page 327 of 770 If OTM Alarm Notification is running (the red traffic light is showing on the toolbar), click on the red traffic light to stop alarm notification. The traffic light changes to green. Click the green traffic light to restart alarm notification. The traffic light should turn to red to indicate it is running. If OTM Alarm Notification is not running, as indicated by the green traffic light, click on the green traffic light to change it to red. This starts Alarm Notification. 10 Telnet to each Line card and log in. At the IPL> command line, enter the itgAlarmTest command. A series of SNMP traps is emitted by the Voice Gateway Media Card and appears in the OTM Alarm Notification browser window. Verify that the device name identifies the correct Voice Gateway Media Card. Table 57 Format of Devices.txt file Device Type IP Address Device Name ITG_IP_PHONE xxx.xxx.xxx.xxx Site_Leader_0 ITG_IP_PHONE xxx.xxx.xxx.xxx Site_Leader_1 ITG_IP_PHONE xxx.xxx.xxx.xxx Site_Follower_2 For every Voice Gateway Media Card in every node, there is a line in the table. For example, a line in the table can look like this: ITG_IP_PHONE 192.9.200.1 MySite_MySystem_Leader_1 The following is a description of each field in the table: Device Type – a dedicated receive string or name used as an index for the IP Line application. The Device Type must be ITG_IP_PHONE. IP Address – the source IP address on the Voice Gateway Media Card from which the traps are coming (either the card Voice IP address (TLAN) or card Management IP address (ELAN)). By default, the SMNP traps are issued from the card Voice IP address (TLAN). If a card routing table entry on the IP Telephony node was previously configured pointing to the IP address of the OTM, then the SMNP trap issues from the Management IP address (ELAN) of the card. IP Line Description, Installation, and Operation Page 328 of 770 Configuration of IP telephony nodes using OTM 2.2 Device Name – the device name can be any string. Nortel Networks recommends that abbreviations for the site and system, the card functions, and the Terminal Numbers (TNs) are used, such as Site_System_Leader/Follower_TN. Note: Spaces should not be used in the Device Name. Use an underscore (_) as a separator. The Leader card has two IP addresses: the card voice IP address (TLAN) and the node IP address. The Follower cards have only a single IP address, the TLAN IP address. End of Procedure Assemble and install an IP Phone To assemble and install an IP Phone, refer to IP Phones: Description, Installation, and Operation (553-3001-368). Change the default IPL> CLI Shell password The IPL> CLI is password-protected for Telnet access and access to the local maintenance port. The same user name and password also protects FTP access to the Voice Gateway Media Card. The IPL> CLI has a default user name of itgadmin and a default password of itgadmin. Refer to “IPL> CLI Shell user name and password” on page 421 and “Node password synchronization” on page 423 for more detailed information on the passwords. Configure the IP Phone Installer Passwords The IP Phone Installer Password protection, required for changing the TN on the IP Phone, controls registration with a virtual line TN on the Call Server. See page 425 for more information about the IP Phone Install Passwords. To enable and set the administrative IP Phone Installer Password, see Procedure 63 on page 435. If needed, enable and configure a temporary IP Phone Installer Password. See Procedure 64 on page 438. 553-3001-365 Standard 3.00 September 2004 412 Page 329 of 770 Configuration of IP Telephony nodes using Element Manager Contents This section contains information on the following topics: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade the ITG-P 24-port line cards to IP Line 4.0 . . . . . . . . . . . . 330 331 Configure IP Line 4.0 data using Element Manager. . . . . . . . . . . . . . . Internet Explorer browser configuration . . . . . . . . . . . . . . . . . . . . . Launch Element Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manually add an IP Telephony node . . . . . . . . . . . . . . . . . . . . . . . . Configure SNMP trap destinations and community name string access . . . . . Configure Voice Gateway Profile data. . . . . . . . . . . . . . . . . . . . . . . Configure Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure ELAN IP address (Active ELNK), TLAN voice port, and routes (Small Systems and CS 1000S only). . . . . . . . . . . . . . . . . Configure file server access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure loss and level plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Add card and configure the card properties of the Voice Gateway Media Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Submit and transfer the node information . . . . . . . . . . . . . . . . . . . . 331 332 335 338 339 345 349 355 Transfer node configuration from Element Manager to the Voice Gateway Media Cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Leader IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmit node properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure the Follower cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IP Line 357 362 364 365 368 371 372 375 379 Description, Installation, and Operation Page 330 of 770 Configuration of IP Telephony nodes using Element Manager Upgrade the Voice Gateway Media Card software and IP Phone firmware . . . . . 382 IP Phone 2001, IP Phone 2002, and IP Phone 2004 firmware requirements 383 Default location of firmware files . . . . . . . . . . . . . . . . . . . . . . . . . . 384 IP Phone Firmware upgrade from a new Voice Gateway Media Card . . . . . . 385 Determine Voice Gateway Media Card software version . . . . . . . . 386 Determine the IP Phone firmware version . . . . . . . . . . . . . . . . . . . . 389 Download the current software and IP Phone firmware . . . . . . . . . 392 Upload the software and firmware files to the file server . . . . . . . . 393 Upgrade the Voice Gateway Media Card software . . . . . . . . . . . . . 396 Reboot the Voice Gateway Media Card . . . . . . . . . . . . . . . . . . . . . 400 Upgrade the IP Phone firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . 400 Upgrade the Voice Gateway Media Card firmware. . . . . . . . . . . . . 407 Configure Alarm Management to receive IP Line SNMP traps . . . . . . 408 Assemble and install an IP Phone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408 Change the default IPL> CLI Shell password . . . . . . . . . . . . . . . . . . . 408 Configure the IP Phone Installer Passwords. . . . . . . . . . . . . . . . . . . . . 408 Import node configuration from an existing node . . . . . . . . . . . . . . . . 409 Introduction This chapter explains how to configure IP Telephony nodes and Voice Gateway Media Cards using Element Manager. Element Manager is accessed using a PC with Internet Explorer 6.0.2600 (or later). The PC must be connected to a LAN that has access to the Signaling Server’s Node IP address, either directly or routed through the network. Note: The ELAN subnet IP address might be required, instead of the Node IP address, to access the Element Manager login window in secure environments. This chapter also provides instruction for transmitting files to Voice Gateway Media Cards, upgrading card software, and upgrading IP Phone firmware. Read the information on IP network engineering guidelines in Data Networking for Voice over IP (553-3001-160) before installing an IP Telephony node. 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 331 of 770 Upgrade the ITG-P 24-port line cards to IP Line 4.0 Note: Element Manager cannot be used with the Meridian 1 system, as a Signaling Server is required in the system configuration. Meridian 1 and CS 1000 systems require the ITG-P 24-port line cards to be running IP Line 4.0. WARNING In CS 1000 systems, the ITG-P 24-port line card using an earlier release of the IP Line application must be upgraded to IP Line 4.0, or communication with Element Manager fails. OTM 2.2 is required to upgrade an ITG-P 24-port line card to IP Line 4.0. Once the card’s software has been upgraded to IP Line 4.0 using OTM 2.2, configuration, administration, and maintenance tasks can be performed using Element Manager. Refer to “ITG-P 24-port card upgrades” in Communication Server 1000S: Upgrade Procedures (553-3031-258) for the procedure to upgrade an ITG-P 24-port line card to IP Line 4.0 software. Configure IP Line 4.0 data using Element Manager Element Manager can be used to manually add and configure an IP Telephony node on CS 1000 systems. Multiple nodes can be configured and managed from Element Manager. Node definition A node is defined as a collection of Signaling Servers and Voice Gateway Media Cards. Each node in the network has a unique Node ID. This Node ID is an integer value. A node has only one Primary Signaling Server or Leader Voice Gateway Media Card. All the other Voice Gateway Media Cards are defined as Followers. IP Line Description, Installation, and Operation Page 332 of 770 Configuration of IP Telephony nodes using Element Manager Note 1: All IP addresses and subnet mask data must be in dotted decimal format. Convert subnet mask data from Classless Inter-Domain (CIDR) format. for more information, see “Subnet Mask Conversion from CIDR to Dotted Decimal Format” on page 761. Note 2: See Table 42 on page 199 for IP addresses and information required in this procedure. Note 3: The following sections discuss how to configure IP Line 4.0 using Element Manager. The following three sections (of the IP Telephony section) in Element Manager are not covered in this NTP: – SNTP (see IP Peer Networking: Installation and Configuration (553-3001-213) – Gatekeeper (see IP Peer Networking: Installation and Configuration (553-3001-213) – Signaling Server (see Signaling Server: Installation and Configuration (553-3001-212) Internet Explorer browser configuration Element Manager requires Microsoft Internet Explorer 6.0.2600 (or later). Element Manager is not supported on the Netscape Navigator browser. The PC should be a PIII with a 500 MHz processor (at minimum). IMPORTANT! Internet Explorer caching interferes with the Element Manager application, in that users cannot see real-time changes as they occur. For this reason, Internet Explorer caching must be turned off. Follow the steps outlined in Procedure 39 on page 333 to prevent caching of web pages by Internet Explorer. 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 333 of 770 Procedure 39 Turning off browser caching in Internet Explorer 1 Launch Internet Explorer. 2 Click Tools > Internet Options. The Internet Options window opens. See Figure 88. Figure 88 Internet Explorer – Internet Options IP Line Description, Installation, and Operation Page 334 of 770 Configuration of IP Telephony nodes using Element Manager 3 On the General tab, under the Temporary Internet files section, click the Settings button. The Settings window opens. See Figure 89. Figure 89 Temporary Internet files Settings window 4 Click the Every visit to the page radio button. This checks for new versions of stored pages on every visit to the web page. 5 Click OK in the Settings window. 6 Click OK in the Internet Options window. End of Procedure 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 335 of 770 Launch Element Manager Follow the steps in Procedure 40 to launch Element Manager. Procedure 40 Launching Element Manager 1 Open Internet Explorer. 2 Enter the Signaling Server Node IP address in the Address Bar (url line) of the browser window. Click Go or press Enter on the keyboard. Note: The ELAN subnet IP address might be required, instead of the Node IP address, to access the Element Manager login window in secure environments. 3 Element Manager opens and the Login window appears. See Figure 90 on page 336. a. Enter the User ID and Password of the Call Server. b. Enter the IP Address of the Call Server in the CS IP Address field. c. Click the Login button. IP Line Description, Installation, and Operation Page 336 of 770 Configuration of IP Telephony nodes using Element Manager Figure 90 Element Manager – Login window 4 The System Information window opens. See Figure 91 on page 337. The navigation tree is located on the left side of the browser window. The System Status menu is expanded in the navigation tree. 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 337 of 770 Figure 91 Element Manager – System Information Note 1: To log out of Element Manager, click Logout at the bottom of the navigation tree. Note 2: When a user is in the Configuration -> IP Telephony -> Node ->Edit window seen in Figure 95 on page 343, Element Manager times out after a period of inactivity. Users are prompted with a warning five minutes before Element Manager times out. If the user clicks OK within the warning time out period, the timer is reset. If the user does not respond, the session is cancelled and the user is forced to login again. Any data that was modified, but not submitted, is lost. IP Line Description, Installation, and Operation Page 338 of 770 Configuration of IP Telephony nodes using Element Manager Figure 92 Timeout message End of Procedure Summary of procedures The following is the summary of the steps required to configure a node and a Voice Gateway Media Card using Element Manager: 553-3001-365 1 “Manually add an IP Telephony node” on page 339 2 “Configure SNMP trap destinations and community name string access” on page 345 3 “Configure Voice Gateway Profile data” on page 349 4 “Configure Quality of Service” on page 355 5 “Configure ELAN IP address (Active ELNK), TLAN voice port, and routes (Small Systems and CS 1000S only)” on page 357 6 “Configure file server access” on page 362 7 “Configure loss and level plan” on page 364 8 “Add card and configure the card properties of the Voice Gateway Media Card” on page 365 9 “Submit and transfer the node information” on page 368 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 339 of 770 Manually add an IP Telephony node Follow the steps in Procedure 41 to add an IP Telephony node using Element Manager. Procedure 41 Adding an IP Telephony node manually 1 To manually add a new IP Telephony node, click Configuration in the navigation tree. 2 In the Configuration menu, click IP Telephony. The Node Summary window opens. See Figure 93. Figure 93 Element Manager – Node Summary - Adding a new node If this is the first node to be added, the “No nodes are configured” message is displayed. There are two options: “New Node to Add” or “Import Node Files”. IP Line Description, Installation, and Operation Page 340 of 770 Configuration of IP Telephony nodes using Element Manager The Node Summary window shows a list of all the configured nodes. To expand a node and view its elements, click the arrow (>) to the left of the Node information. Figure 94 shows one expanded node. The Node Summary window includes five buttons: • to Add – This button is used to add a new IP Telephony node. Enter an unused Node ID and then click to Add. • Import Node Files – This button imports the configuration files from an existing node. • Transfer/Status – This button is used to transfer/obtain the status on the requested changes to the node. The node then obtains its information (CONFIG.INI and BOOT.P files) from the Call Server. Note: If any element within the Node fails to transfer either BOOTP or CONFIG files, the Transfer/Status button is highlighted in red. If the transfer status of the node elements is unavailable, the Transfer/Status button is highlighted in yellow 553-3001-365 • Edit – This button retrieves the node information from the Call Server and returns the information to the Edit window. The node information can then be changed. • Delete – This button is used to delete the selected node and its information from the Call Server. Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 341 of 770 Figure 94 Node Summary – expand a node IP Line Description, Installation, and Operation Page 342 of 770 Configuration of IP Telephony nodes using Element Manager 3 Enter the new Node ID in the New Node text box. The Node ID can be one to four digits in length. When defining the node number, determine if the Enhanced Redundancy for IP Line Nodes functionality is required (see “Enhanced Redundancy for IP Line nodes” on page 142). If it is required, factor the requirement into the node number assignment process. CAUTION The Voice Gateway Media Cards identify themselves with a node using the node number or node ID. If there are multiple IP Telephony nodes sharing the same TLAN subnet, each node must have a unique ID. Each system on the TLAN subnet must have a unique node ID assigned to the Voice Gateway Media Cards on the system. Note: The Node ID field corresponds to the Node ID field in the IP Phone configuration. Write down the node number, which is used during the IP Phone configuration. 4 Click the to Add button. The Edit window opens. See Figure 95 on page 343. 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 343 of 770 Figure 95 Element Manager – Edit The Edit window includes three different buttons: 5 • Save and Transfer – This button saves and transfers changes to the Call Server and returns the users to the Node Summary window. • Cancel – This button discards changes made to the IP Telephony node and returns the users to the Node Summary window. • Add - The Add buttons are associated with specific sections of the IP Telephony node properties. The user can add new SNMP traps, cards, and Signaling Servers. Click Node to edit the Node information, if it is not already expanded by default. See Figure 96 on page 344. IP Line Description, Installation, and Operation Page 344 of 770 Configuration of IP Telephony nodes using Element Manager Figure 96 IP Telephony Configuration > Node Summary > Edit > Node a. Node ID: The node ID entered on the previous page appears. b. Voice LAN (TLAN) Node IP address: Enter the Voice LAN (TLAN) Node IP address in dotted decimal format. The Voice LAN Node IP address is on the TLAN subnet. The Node IP address is the IP address used by the IP Phones to communicate with the Voice Gateway Media Cards on the TLAN subnet. If a Voice Gateway Media Card becomes the primary (Leader) during an election, it assigns itself the Node IP address. Note: A green asterisk (*) indicates that a field is a required/mandatory field. c. 553-3001-365 Management LAN (ELAN) gateway IP address: Enter the Management LAN (ELAN) subnet gateway IP address in dotted decimal format. This is the IP address of the gateway of the subnet to which the Voice Gateway Media Card belongs. Also, this is the IP address of the router interface on the ELAN subnet, if present. If there is no Management LAN subnet gateway, enter 0.0.0.0. Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 345 of 770 d. Management LAN (ELAN) subnet mask: Enter the Management LAN subnet mask address in dotted decimal format. This is the subnet mask that is used along with the ELAN subnet IP address to identify to which subnet the Voice Gateway Media Card belongs. e. Voice LAN (TLAN) subnet mask: Enter the Voice LAN subnet mask address in dotted decimal format. This is the subnet mask that is used along with the TLAN IP address, to identify the subnet to which the Voice Gateway Media Card belongs. Note: Do not click Submit until all the node information has been entered. If the Submit button is clicked prematurely, the Node Summary window reappears. To continue the configuration, click the Edit button to return to the Node Edit window. End of Procedure Configure SNMP trap destinations and community name string access For more information on SNMP, refer to Simple Network Management Protocol: Description and Maintenance (553-3001-519). Configuring SNMP trap destinations To configure the SNMP trap destinations for the Signaling Server and Voice Gateway Media Cards in Element Manager, follow the steps in Procedure 42 on page 346. IP Line Description, Installation, and Operation Page 346 of 770 Configuration of IP Telephony nodes using Element Manager Procedure 42 Configuring SNMP trap destinations 1 On the Node > Edit window, click SNMP. See Figure 97. Figure 97 Node > Edit > SNMP 2 553-3001-365 Select the Enable SNMP traps check box, if configuring one or more SNMP management IP addresses to receive SNMP traps from cards in the IP Telephony node. f. IP address: Enter the IP address of the trap destination. If SNMP traps are enabled, the SNMP traps are sent to the IP address entered here. More than one IP address can be configured. g. Subnet mask: The subnet mask for the IP address of the trap destination must always be configured as 255.255.255.255. Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 347 of 770 WARNING Do not enter the actual value of the subnet mask on the interface of the SNMP trap destination. Doing so can cause misrouting of RTP media and signaling, leading to no speech path between the IP Phones and the Voice Gateway Media Cards or failure of the IP Phones to register with the LTPS. h. Click ADD to enter the IP address for another trap destination. Add destination SNMP Manager IP addresses for the following: • • local or remote OTM server • PPP IP address configured in the router on the ELAN for the remote-support OTM PC SNMP manager for remote alarm monitoring. Note 1: Up to eight SNMP trap destinations can be defined. Note 2: A net route or host route through the Management (ELAN) gateway is added to the Voice Gateway Media Cards IP Routing Table for each SNMP destination address that is added to the SNMP traps list. Note 3: To remove an SNMP trap destination, click the corresponding Remove button. End of Procedure Configuring community name strings The SNMP community name strings control access to the IP Telephony node. Element Manager uses the community name strings to refresh the Voice Gateway Media Card status and to control the transmitting and retrieving of configuration data files for database synchronization. Note: If the community name strings are forgotten, connect a TTY to the Voice Gateway Media Card maintenance port. Restart the card. The card displays the community name on the TTY during start-up. IP Line Description, Installation, and Operation Page 348 of 770 Configuration of IP Telephony nodes using Element Manager To configure the community name strings in Element Manager, follow the steps in Procedure 43. Procedure 43 Configuring the community name strings 1 Select Configuration > IP Telephony > SNMP Configuration. See Figure 98. Figure 98 Configuration > IP Telephony Configuration > SNMP Configuration window 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager 2 Obtain the following information from the system administrator and enter it in the appropriate fields: • 3 Page 349 of 770 • Navigation Site Name (NAV_SITE) • Navigation System Name (NAV_SYSTEM) • Contact person for this machine (SNMP_SYSCONTACT) • Name assigned to this machine by the administrator (SNMP_SYSNAME) • System Management Read community string (SYSMGMT_RD_COMM) • System Management Write community string (SYSMGMT_WR_COMM) Admin Group community string (ADMIN_COMM). Select 1, 2, or 3 from the drop-down list. Click Submit to save the configuration or Cancel to cancel the entry. Note: Click Refresh to retrieve the current information from the system. End of Procedure Synchronization of community name strings After the system community name strings are configured, it is necessary to perform a data dump to synchronize these community name strings from the Call Server to the Signaling Server and Voice Gateway Media Cards. As well, when a link is established between the Signaling Server or Voice Gateway Media Cards and the Call Server, the Call Server transmits the community name strings to those devices. Configure Voice Gateway Profile data Follow the steps in Procedure 44 on page 350 to configure the Voice Gateway Profile data. IP Line Description, Installation, and Operation Page 350 of 770 Configuration of IP Telephony nodes using Element Manager Procedure 44 Configuring DSP Profile data 1 On the Edit window, click VGW Profile. The VGW Profile window opens. See Figure 99. The VGW Profile area includes VGW Profile information and a list of codecs. Figure 99 Configuration > Node Summary > Edit > VGW Profile 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager 2 Page 351 of 770 Under VGW Profile, leave the values at their default settings unless directed to change them by Nortel Networks Field Support. a. Enable Echo canceller: The echo canceller is enabled by default. Do not uncheck this box. Never disable echo canceller unless directed by Nortel Networks Field Support. b. Echo canceller tail delay: Select the maximum value available. The default value is 128ms. Never reduce the echo canceller value unless directed by Nortel Networks Field Support. c. Voice activity detection threshold: The default value is –17db. The range is –20db to +10db. d. Idle noise level: The default value is –65db. The range is –327db to +327db. e. DTMF Tone detection: Ensure this is checked to enable DTMF tone detection. This is enabled by default. f. Enable V.21 FAX tone detection: Ensure this is checked to enable V.21 FAX tone detection. This is enabled by default. g. FAX maximum rate: The FAX maximum rate is one of the following values: 2400, 4800, 7200, 9600, 12000, or 14400. The default value is 14400 bps. h. FAX playout nominal delay: The default value is 100 ms. The range is 0ms to 300ms. i. FAX no activity timeout: The default value is 20 secs. The range is 10secs to 32000 secs. j. FAX packet size: Select the packet size. The default value is 30 bytes. The range is 20 to 48 bytes. IP Line Description, Installation, and Operation Page 352 of 770 Configuration of IP Telephony nodes using Element Manager To select a codec, scroll through the list, and click the corresponding Select check box. See Figure 100 for codec samples. A maximum of four codecs can be selected. Recommendation Nortel Networks recommends that the system be configured with both G.711 and G.729A if there is a possibility that an IP Softphone 2050 could be configured with the “I use a modem to connect to the network” check box checked. If the node does not have G.729A and/or G.723 configured, IP Softphone 2050 users with that checkbox selected will have calls blocked. (Note: This does not apply to the MVC 2050 as it only supports G.711 capability; there is no dial-up capability.) For more information, refer to IP Phones: Description, Installation, and Operation (553-3001-368) in the “Select Sound Devices tab” section. Figure 100 Codec list Note: The codec list contains six codec settings for G.711, G.729A, G.729AB, C.723.1, G711 Clear Channel, and T.38 FAX for the Voice Gateway Media Card. 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager 3 Page 353 of 770 The G.711, G711 Clear Channel, and T.38 FAX codecs are selected by default, and these selections cannot be cleared. However, the following changes can be made: • The payload size, jitter buffer setting, and companding law for the G.711 codec can be changed. The default is G.711 mu-law. • Only the jitter buffer can be changed for the G.711 Clear Channel codec. Up to three additional codecs can be optionally selected: G.729A, G.729AB, and/or G.723.1 codecs. • If the G.729A or G.729AB codec are selected, the payload and jitter buffer can be changed. The payload defaults are the maximum supported payload. • If the G.723.1 codec is selected, only the jitter buffer can be changed. The payload size of 30 msec is the only supported payload. Note: The supported G.723.1 codec has bit rates of 5.3 Kbps and 6.3 Kbps. 4 Expand the selected Codec. See Figure 101. Figure 101 Selected Codec Element Manager performs some jitter buffer adjustments on the browser side. The following are the jitter buffer adjustment that are made in Element Manager: • A change of payload resets the Nominal Voice Playout (NVP) and Maximum Voice Playout (MVP) values to the default recommended values: IP Line Description, Installation, and Operation Page 354 of 770 Configuration of IP Telephony nodes using Element Manager NVP = 2 * payload MVP = NVP + 2 * payload 5 • A change of NVP value changes the MVP value to the default (MVP = NVP + 2 * payload) and changes the values listed in the MVP pull down list so the minimum value listed does not violate the requirement of NVP + 2 * payload. • The MVP value can be changed. The pull-down values range from the minimum recommended value (see above) to the maximum allowed value for the selected codec type. Set the following values for the codec: a. Codec Name: The codec name is based on the selected codec. b. Voice payload size (msecs/frame): The payload size is determined by the selected codec. For each codec type, the payload is defaulted to the maximum supported: 30 msec for G.711 (a-law and mu-law), 50 msec for G.729A, 50 msec for G.729AB, and 30 msec for the G.723.1. Note: If a system has multiple nodes and the same codec is selected on more than one node, ensure that each node has the same voice payload size configured for the codec. 6 c. Voice playout (jitter buffer) nominal delay: Set the nominal value to the highest setting that the device allows. The range is 20–200 ms and is dependent on the codec. Changing this value can cause the automatic adjustment of the other settings for this codec. For more information, see Data Networking for Voice over IP (553-3001-160).” d. Voice playout (jitter buffer) maximum delay: The maximum delay has a range of 60–500 ms and is dependent on the codec. Changing this value, can cause the automatic adjustment of the other settings for this codec. e. VAD: Select this check box to enable Voice Activity Detection. Repeat the last step for each of the selected codecs. End of Procedure 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 355 of 770 Configure Quality of Service The Quality of Service (QoS) section includes the settings for the following: • DiffServ CodePoint (DSCP) • 802.1Q support Follow the steps in Procedure 45 to configure QoS. Procedure 45 Configuring QoS 1 Click QoS. See Figure 102. Figure 102 Configuration > IP Telephony > Node Summary > Edit > Qos IP Line Description, Installation, and Operation Page 356 of 770 Configuration of IP Telephony nodes using Element Manager 2 The Differentiated Service (DiffServ) CodePoint (DSCP) determines the priorities of the management and voice packets in the IP Line network. The range for both management and voice packet DiffServ is 0 – 63 inclusive. The DiffServ value can be configured, if required, to obtain better QoS over the IP data network (LAN/WAN). The value entered depends on the policy in the customer’s data network. Note: Do not change DiffServ from the default values unless instructed by the IP network administrator. Under QoS, only modify the Control priority and Voice priority values as and when directed by the IP network administrator. The recommended configuration values are as follows: 3 a. Diffserv CodePoint (DSCP) Control packets: A value of 40 - Class Selector 5 (CS5). The range is 0 – 63. This sets the priority of the signaling messaging. b. Diffserv CodePoint (DSCP) Voice packets: A value of 46 Control DSCP - Expedited Forwarding (EF). The range is 0 – 63. 802.1Q enables Virtual LANs (VLANs) to be defined within a single LAN. This improves bandwidth management and limits the impact of broadcast storms and multicast messages. a. Enable 802.1Q support: 802.1Q support is disabled by default. b. 802.1Q Bits value (802.1p): The priority field is a 3-bit value, with a default value of 6. The range is 0 – 7. A value of 6 is recommended by Nortel Networks. The p bits within the 802.1Q standard enables packet prioritization at Layer 2 improving network throughput for IP Telephony data. End of Procedure 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 357 of 770 Configure ELAN IP address (Active ELNK), TLAN voice port, and routes (Small Systems and CS 1000S only) The LAN configuration section is used for configuring the Call Server ELAN IP address (Active ELNK), TLAN voice port, and routes. This information is applicable only to Small Systems. Procedure 46 Configuring the Call Server ELAN IP address (Active ELNK), TLAN voice port, and routes on a Small System 1 Click LAN Configuration. See Figure 103. Figure 103 Configuration > Node Summary > Edit > LAN configuration IP Line Description, Installation, and Operation Page 358 of 770 Configuration of IP Telephony nodes using Element Manager 2 Enter the following Management LAN (ELAN) configuration settings: a. Call Server IP address: This is the IP address of the Call Server on the ELAN subnet. Enter the Call Server ELAN subnet IP Address (Active ELNK). Note: The Call Server ELAN subnet IP address must correspond to the Active ELNK IP address configured in LD 117. The IP address must be in the same subnet as the ELAN subnet for the IP Line node. b. Survivable Media Gateway IP address: This address is configured for survivability. It is the IP address of the Survivable CS 1000S Media Gateway on the ELAN subnet. Note 1: The Survivable CS 1000S Media Gateway IP address must correspond to the Active ELNK IP address. If configured, all Voice Gateway Media Cards in the same node should be in the same Survivable Cabinet. Note 2: The Survivable Media Gateway associated with the Primary Signaling Server IP Telephony node is called the Alternate Call Server. It is normally located in the same equipment rack with the Call Server and Signaling Server; therefore, it is normally connected to the same ELAN subnet as the Call Server and the Primary Signaling Server IP Telephony node. The Alternate Call Server Media Gateway should be equipped with sufficient trunk cards, Voice Gateway Media Cards, and centralized CallPilot, so that it provides a large degree of survivability in case of Call Server equipment failure for IP Phone users who normally register through the Signaling Server. Refer to Communication Server 1000S: Planning and Engineering (553-3031-120) and Communication Server 1000S: Installation and Configuration (553-3031-210) for more information about survivability. 553-3001-365 c. Signaling port: The default value is 15000. The range is 1024 to 65535. d. Broadcast port: The default value is 15001. The range is 1024 to 65535. Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager 3 Page 359 of 770 Under Voice LAN (TLAN) configuration: a. Signaling port: The default value is 5000. The range is 1024 to 65535. The TLAN Signaling occurs on UDP ports 7300, 4100, 5100, and 5000. b. Voice port: Change the Voice port only as instructed by the IP network administrator to improve QoS for the IP Phones. For example, if RTP Header compression is used to reduce voice bandwidth on narrow band WAN links, then the TLAN voice port range needs to be set to 16384 or higher. The exact range is provided by the system administrator. The TLAN Voice port range is 1024 to 65535. The default Voice ports are 5200 – 5295. CAUTION Do not set the Voice port to a value that is already used for signaling (4100, 5000, 5100, 7300). The Voice port defines the first port in a range spanning the gateway channels on the card; this means a Voice port value of 5200 reserves the following: • ports 5200 – 5263 on the Media Card 32-port line card • ports 5200 – 5215 on the Media Card 8-port line card • and 5200 – 5247 on the ITG-P 24-port line card. If this value is changed from the default, verify that the selected Voice port value does not intrude into one of the reserved Signaling port values. 4 Click the Add button to the right of Routes if entries must be made to the card routing table. See Figure 104 on page 360. The Routes fields expand. IP Line Description, Installation, and Operation Page 360 of 770 Configuration of IP Telephony nodes using Element Manager Figure 104 Routes Under Routes, enter the IP address and Subnet mask for any host that is not on the ELAN subnet but requires access to the Voice Gateway Media Card across the ELAN subnet. A Telnet session for maintenance from a remote PC is an example of when this would be needed. The address of the remote PC would be added in the Route list. The default route on the card causes packets destined for unknown subnets to be sent out on the TLAN network interface. Packets from an external host arrive on the ELAN network interface and responses are sent on the TLAN network interface. This process can cause one-way communication if the TLAN subnet is not routed to the ELAN subnet. It is necessary to add an entry in the Route list to correct the routing so that response packets are sent on the ELAN subnet. Each entry creates a route entry in the card's route table that directs packets out the ELAN network interface. See Figure 105 on page 361. CAUTION Use caution when assigning card routing table entries. Do not include the IP address of an IP Phone. Otherwise, voice traffic to these IP Phones is incorrectly routed through the ELAN subnet and ELAN subnet gateway. To avoid including the wrong IP address, Nortel Networks recommends that Host IDs are defined for the card routing table entries. 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager 5 Page 361 of 770 To add additional routes, click the Add button again and enter the route information. Repeat this step for each route to be added. Figure 105 Specifying additional ELAN routes ELAN subnet ELAN route+ additional routes TLAN route/ default route TLAN subnet Meridian 1 or CS 1000 Some other LAN Management Workstation In this diagram, an additional ELAN route is required to reach the management workstation, which is accessible through the ELAN interface but is not on the ELAN subnet. End of Procedure IP Line Description, Installation, and Operation Page 362 of 770 Configuration of IP Telephony nodes using Element Manager Configure file server access With the addition of more IP Phones, there are also additional firmware files for the IP Phones. The Voice Gateway Media Card has limited space to store the files on the card for all the telephones. As a result, a file server is used to store the telephone firmware files. For more information, see “IP Phone firmware” on page 130 The IP Phone firmware files are labeled as follows: • 0603Bnn.BIN is the filename for the Phase I IP Phone 2002 firmware where Bnn = F/W version 1.nn. • 0602Bnn.BIN is the filename for the Phase I IP Phone 2004 firmware where Bnn = F/W version 1.nn. • 0603Dnn.BIN is the filename for the Phase II IP Phone 2001, IP Phone 2002, and IP Phone 2004 firmware where Dnn = F/W version 3.nn If the external file server option is used in Element Manager for firmware distribution with a node, the files must be renamed before being placed on the server: • 0602Bnn.BIN must be renamed to i2004.fw • 0603Bnn.BIN must be renamed to i2002.fw • 0604Dnn. BIN must be renamed to IPP2SETS.fw To configure the file server, follow the steps in Procedure 47 on page 363. 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 363 of 770 Procedure 47 Configuring access to the file server 1 Click Firmware. See Figure 106. Figure 106 Configuration > Node Summary > Edit > Firmware 2 Specify the parameters needed to connect to the file server: a. Firmware download server IP address: Enter the IP address of the file server where the firmware will be downloaded. b. Firmware file path: Enter the path for the location of the firmware files. See page 133 for the default location of firmware files for the CS 1000 system. c. User ID: Enter the User ID that is required to access the file server. d. Password: Enter the Password that is required to access the file server. End of Procedure IP Line Description, Installation, and Operation Page 364 of 770 Configuration of IP Telephony nodes using Element Manager Configure loss and level plan The loss and level plan determines parameters, such as transmission gain, that vary from country to country. Dynamic Loss Plan A Dynamic Loss Plan has been implemented to define the gateway loss value per endpoint connection type. The loss plan adjusts the Voice Gateway Media Card gateway channel's loss for each call by sending pad values to the card. Loss plan values are now configured through LD 73. Default values The default values in the system are for the North American loss plan. Non-North American countries Installation of IP Line 4.0 in any other country requires setting the pad values in Table 15 to that country's loss plan. If the system is installed in other countries, the GPRI package (International 1.5/2.0 Mb/s Gateway package 167) must be used, and the NTP-specified values must be entered in LD 73. At the PDCA prompt, enter Table 15. Refer to Transmission Parameters (553-3001-182) for more information. United Kingdom In addition, when a system is installed in the UK, the CLI command UKLossPlanSet is entered at the CLI of one card in each node. This adjusts the loss plan of the IP Phones to the higher transmit levels required in the UK. Follow the steps in Procedure 48 to set the loss plan for the UK. Procedure 48 Setting the loss plan for the UK 553-3001-365 1 Telnet to the card, connect to the maintenance port, or use OTM 2.2 or Element Manager to access the Voice Gateway Media Card. 2 Log into the IPL> shell. 3 At the IPL > CLI, enter the command UKLossPlanSet. 4 Press . Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager 5 Page 365 of 770 Exit from the login session. End of Procedure After the UKLossPlanSet command is entered, the loss plan adjustment is transmitted by that card to all other cards in the node. The loss plan is then adjusted on any registered IP Phones, and on other IP Phones as they register. To clear the loss plan adjustment, use the command UKLossPlanClr. Refer to “IP Phone Loss Plan (UK) commands” on page 615 for more information on these and other loss plan commands. Add card and configure the card properties of the Voice Gateway Media Card If the network administrator provides IP addresses and subnet masks in CIDR format, for example, “10.1.1.10/24”, convert the subnet mask to dotted decimal format. See Appendix E on page 761. Note: In the Cards section, cards can be added, changed, or removed in the node one at a time. WARNING Every node must has a Leader. Exercise caution when removing the Leader card. If the Leader card is deleted, a new Leader must be configured immediately. Follow the steps in Procedure 49 to configure Voice Gateway Media Card properties. Procedure 49 Adding card and configuring Voice Gateway Media Card properties 1 Click Cards and then click the Add button. See Figure 107 on page 366. IP Line Description, Installation, and Operation Page 366 of 770 Configuration of IP Telephony nodes using Element Manager Figure 107 Configuration > Node Summary > Edit > Cards 2 553-3001-365 Enter the Card Properties data for Leader 0 and Follower cards. The fields with green asterisks are required fields: a. Role: The role is assigned based on the information that Element Manager reads from the card configuration. This is a read-only field. b. Management LAN (ELAN) IP address: This is the ELAN subnet IP address for the card. Element Manager and the system use this address to communicate with the card. c. Management LAN (ELAN) MAC address: This is the motherboard Ethernet address from the “Voice Gateway Media Card installation summary sheet” on page 199. d. Voice LAN (TLAN) IP address: This is the TLAN subnet IP address for the card. e. Voice LAN (TLAN) gateway IP address: This is the IP address of the router interface on the TLAN subnet. f. Hostname: This is the Host name. Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 367 of 770 g. Card TN: Enter the card slot number between 1 – 50. h. Card processor type: Choose either Pentium or Media Card. Select Pentium if using the ITG-P 24-port line card (dual-slot card). Select Media Card if using the Media Card 32-port or 8-port line card (single-slot card). i. H323 ID: The H323 ID within IP Line 4.0 is for the Virtual Office/ Media Gateway 1000B feature. Keep the H323 ID the same for all the elements within one node. j. Enable set TPS: Select the check box. k. System name: Enter the name of the system. l. System location: Enter the location where the system resides. m. System contact: Enter a contact name and telephone number. 3 To add additional cards to the node, click the Add button again and enter the new card information. Repeat this step for each card that is being added to the node. New cards appear under the Cards menu as they are added. See Figure 108. Figure 108 Cards added to the system End of Procedure IP Line Description, Installation, and Operation Page 368 of 770 Configuration of IP Telephony nodes using Element Manager Submit and transfer the node information To submit node changes and transfer the changes to the Call Server, follow the steps in Procedure 50. Procedure 50 Submitting and transferring the node information 1 Click the Save and Transfer button when all the node information is configured in the Edit window. Clicking the Save and Transfer button saves and transfers the data to the Call Server. The Edit window closes, and the Node Summary window opens with the new node added. See Figure 109 on page 369. Note 1: The Save and Transfer button can be clicked after each section is configured in the Edit window. However, each time the Save and Transfer button is clicked, the Edit window closes and the Node Summary window is displayed. To continue the node configuration, click the Edit button to return to the Edit window. Note 2: If the Cancel button is clicked, all information that has been configured is discarded. The Edit window closes and the Node Summary window opens. 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 369 of 770 Figure 109 Node added to Node Summary window 2 Click the Transfer/Status button for the node. The Transfer confirmation dialog box opens. 3 Click OK to confirm the transfer. See Figure 110. Figure 110 Transfer confirmation dialog box After a few seconds, the Transfer Progress window opens and displays each of the Voice Gateway Media Cards in the node. See Figure 111 on page 370. IP Line Description, Installation, and Operation Page 370 of 770 Configuration of IP Telephony nodes using Element Manager The Voice Gateway Media Cards retrieve the CONFIG.INI and BOOTP.TAB files from the Call Server. A check mark is added to each field as the card receives its CONFIG.INI and BOOTP.TAB files. When the transfer is complete, click OK in the Progress Check Complete dialog box. • If the transfer is successful for a card, the Status column displays “Complete” and a check mark is displayed. • If the transfer is unsuccessful, the Status column displays “Fail”. A failed transfer can be caused by several situations, including the following: — improper cabling. Check cable connections. — improper card configuration. Ensure all information is configured correctly. — the card running an older version of the software than the Signaling Server. Verify the software version on the card and upgrade the software if necessary. Refer to “Upgrade the Voice Gateway Media Card software and IP Phone firmware” on page 382. Figure 111 Transfer Progress window 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 371 of 770 Figure 112 Transfer Successful message box End of Procedure Transfer node configuration from Element Manager to the Voice Gateway Media Cards Before beginning, ensure the following: • The Voice Gateway Media Cards and cables have been installed. • The ELAN and TLAN network interfaces of all cards have access to the IP network. • To enable access to Element Manager through a web browser, a network PC must be able to access the node’s Signaling Server, either directly or remotely. The IP Telephony node and card properties are configured using Element Manager. The configuration data is saved to the Call Server and then transferred to the Voice Gateway Media Cards. Saving the configuration The configuration data is saved when the Save and Transfer button on the Edit window is clicked. The files are saved to the Call Server. After the data is saved, the configuration must be transferred to the Voice Gateway Media Card. When the Transfer/Status button on the Node Summary window is clicked, Element Manager instructs each card where to retrieve the files using IP Line Description, Installation, and Operation Page 372 of 770 Configuration of IP Telephony nodes using Element Manager FTP. The Voice Gateway Media Card then retrieves the CONFIG.INI and BOOTP.TAB files. Transferring the configuration - main node For a Signaling Server node, the process to transfer the node configuration to the cards consists of the following steps: 1 Transmit the node properties. See Procedure 52 on page 375. 2 Configure the Follower card. See Procedure 53 on page 379. Note: The following sequence of steps are applicable only to nodes that do not use the Signaling Server as the Leader card; that is, a second (or subsequent) node is being configured on the system – not the main node. The Signaling Server must be properly configured to use Element Manager, so that the steps of setting and rebooting the Leader are not needed. The Signaling Server requires a reboot only if the Signaling Server IP address information has been changed, such as the node IP address or Signaling Server TLAN subnet IP address. The Voice Gateway Media Cards require a reboot only if the card IP address information has been changed. Transferring the configuration - second node For a second (or subsequent) node, the process to transfer the node configuration to the cards consists of the following steps: 1 Set the Leader IP address. See Procedure 51 on page 373. 2 Transmit the node properties. Procedure 52 on page 375. 3 Configure the Follower card. See Procedure 53 on page 379. Setting the Leader IP address Follow the steps in Procedure 51 to set the IP address of the Leader Voice Gateway Media Card. 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 373 of 770 Procedure 51 Setting the Leader IP address for a second or subsequent node 1 Access the IPL> CLI by connecting the COM port of a PC to the RS-232 serial maintenance port on the faceplate of the Leader Voice Gateway Media Card with an NTAG81CA PC Maintenance cable. If required, use an NTAG81BA Maintenance Extender cable between the PC Maintenance cable and the PC. Alternatively, connect the NTAG81BA Maintenance Extender cable to the female DB-9 connector of the NTMF94EA ELAN, TLAN RS-232 Ports cable for a more permanent connection to the Voice Gateway Media Card serial maintenance port. Note: Never connect two terminals to the faceplate and I/O panel breakout cable serial maintenance port connectors at the same time. 2 3 Use the following communication parameters for the TTY terminal emulation on the PC: • 9600 baud • 8 bits • no parity • one stop bit Observe the Leader card faceplate maintenance display window. When the display reads “T:20”, the card begins to send BootP requests on the ELAN. A series of dots is printed on the TTY. 4 Type +++ to escape from the BootP request. 5 At the Login prompt, enter the user ID and password to access the IPL> CLI: • If the card is a new card (out of the box), then the user ID is itgadmin and the password is itgadmin. • If the card has been previously connected to the Call Server, then the user ID and password are the PWD1 of the Call Server. • If the user ID and password are forgotten, see Procedure 65 on page 439 to reset the IPL> CLI Shell username and password. IP Line Description, Installation, and Operation Page 374 of 770 Configuration of IP Telephony nodes using Element Manager 6 When the maintenance window displays “T:21”, login to the IPL> CLI. At the IPL> prompt, enter the setLeader command to set the Leader Management LAN (ELAN) subnet IP address, Management LAN gateway IP address and the Management LAN subnet mask: setLeader “xx.xx.xx.xx”,“yy.yy.yy.yy”,“zz.zz.zz.zz” Note 1: The three parameters must each be enclosed in double quotation marks. There must be a space after the command and before the first parameter. Put commas and no spaces between the following parameters: “xx.xx.xx.xx” = IP address. Enter the same IP address that was entered in the Management LAN IP address field for Leader in the Cards menu of the Edit window. “yy.yy.yy.yy” = Gateway IP address. Enter the same IP address that was entered in the Management LAN gateway IP address field in the Node menu of the Edit window. If there is none, enter the following: “0.0.0.0” “zz.zz.zz.zz” = Management LAN subnet mask. Enter the same address that was entered in the Management LAN subnet mask field Node menu of the Edit window. Note 2: This step assumes that the new IP Telephony node has already been configured in Element Manager. 7 Reboot the Leader Voice Gateway Media Card. At the IPL> prompt, enter: cardReset, or press the Reset button on the faceplate of the Leader Voice Gateway Media Card. WARNING Do not use a pencil to reset the Voice Gateway Media Card. The graphite carbon can create an electrical short circuit on the board. 8 Check the maintenance display for T:22 to confirm a successful reboot. 9 In Element Manager, click System Status > IP Telephony. The IP Telephony Information pages opens. 10 Expand the node. 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 375 of 770 11 Click the Leader card’s Status button to check the status of the card. Otherwise, verify LAN connections and IP configuration. End of Procedure Transmit node properties To transmit the node properties to the Leader, follow the steps in Procedure 52. Procedure 52 Transmitting node properties to Leader 1 If changes are made to the node or card configuration data, ensure the data is saved to the Call Server by clicking the Submit button. A confirmation dialog box opens. See Figure 113. Figure 113 Confirm Submit 2 Click OK to confirm the save of the node data. The Edit window closes, and the Node Summary window opens. 3 In the Node Summary window, click the Transfer/Status button associated with the node. See Figure 114 on page 376. IP Line Description, Installation, and Operation Page 376 of 770 Configuration of IP Telephony nodes using Element Manager Figure 114 Transfer Node The Transfer/Status window opens. See Figure 115. Figure 115 Transfer/Status window 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager 4 Select the desired type of transfer. 5 Click OK to confirm the transfer. See Figure 116. Page 377 of 770 Figure 116 Transfer confirmation dialog box Element Manager notifies the Leader and the Voice Gateway Media Cards which then retrieve the CONFIG.INI and BOOTP.TAB files from the Call Server. The Transfer Progress window opens and displays each of the Voice Gateway Media Cards in the node. The Voice Gateway Media Cards retrieve the CONFIG.INI and BOOTP.TAB files from the Call Server. 6 When the transfer is complete, click OK (see Figure 111 on page 370) in the Progress Check Complete dialog box. If the transfer is successful for a card, the Status column displays “Complete.” If the transfer is unsuccessful, the Status column displays “Fail.” 7 Reset the Leader card in the following situations: • if the Leader card is a new card (out of the box) • if the Leader card is a card that is being configured for the first time as a Leader card • if the Leader card’s IP address has changed In the navigation tree, click System Status > IP Telephony. The IP Telephony Information pages opens. Click the Reset button associated with the Leader card. IP Line Description, Installation, and Operation Page 378 of 770 Configuration of IP Telephony nodes using Element Manager Note 1: If any of the Signaling Server IP address information is changed, the Signaling Server must be rebooted. Note 2: Alternatively, restart the card by entering the cardReset command at the IPL> prompt or by pushing the Reset button on the card’s faceplate. WARNING Do not use a pencil to reset the Voice Gateway Media Card. The graphite carbon can create an electrical short circuit on the board. End of Procedure 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 379 of 770 Configure the Follower cards To configure a Follower card, follow the steps in Procedure 53. Procedure 53 Configuring the Follower cards 1 Check the displays on the card faceplate. • After successfully rebooting, the Leader card is now fully configured with the Node Properties of the node. The card enters a state of “active Leader”. The card faceplate display shows Lxxx, where xxx = the number of IP Phones registered with the LTPS on the Leader card. L000 shows that no IP Phones are registered. • The Follower cards receive their BOOTP configuration information from the Leader card. The Follower card faceplate display shows Fxxx, where xxx = the number of IP Phones registered with the Follower card’s LTPS. F000 shows that no IP Phones are registered. 2 Reboot the Follower card if the card’s faceplate does not display FXXX or F000. 3 Once all the Follower cards have the correct display on their faceplates, log into Element Manager. 4 In the Node Summary window, click the Transfer/Status button associated with the node. See Figure 117 on page 380. IP Line Description, Installation, and Operation Page 380 of 770 Configuration of IP Telephony nodes using Element Manager Figure 117 Transfer node information to the card The Transfer/Status window opens. See Figure 118. Figure 118 Transfer/Status window 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager 5 Select the desired type of transfer. 6 Click OK to confirm the transfer. Page 381 of 770 See Figure 119. Figure 119 Transfer confirmation dialog box The Transfer Progress window opens and displays each of the Voice Gateway Media Cards in the node. The Voice Gateway Media Cards retrieve the CONFIG.INI and BOOTP.TAB files from the Call Server. 7 When the transfer is complete, click OK in the Progress Check Complete dialog box. See Figure 111 on page 370. If the transfer is successful for a card, the Status column displays “Complete.” If the transfer is unsuccessful, the Status column displays “Fail.” 8 If the Follower card is a new card (never used before), then reboot the card. End of Procedure IP Line Description, Installation, and Operation Page 382 of 770 Configuration of IP Telephony nodes using Element Manager Upgrade the Voice Gateway Media Card software and IP Phone firmware WARNING Before beginning the upgrade, ensure that a PWD1 user name and password has been configured on the Call Server. If there is no PWD1 user name and password, configure them in LD 17. This is necessary to enable login to the Voice Gateway Media Cards and Signaling Server. Before beginning, ensure that the following software is installed on the PC: • Software to extract zipped files (WinZip or equivalent) • Microsoft Internet Explorer version 6.02 (or later). NetScape Navigator is not supported. Upgrade procedure steps The following steps are required to upgrade the Voice Gateway Media Card loadware and IP Phone firmware: 553-3001-365 1 Determine the version of the software currently installed on the Voice Gateway Media Card. See Procedure 54 on page 386. 2 Determine the version of the IP Phone firmware that is currently running on the Voice Gateway Media Card. See Procedure 55 on page 389. 3 Download the most up-to-date version of the software and firmware files from the Nortel Networks web site. See Appendix F: “Download IP Line 4.0 files from Nortel Networks web site” on page 763. 4 Upload the software and firmware files using the File Upload system utility in Element Manager. See Procedure 57 on page 394. 5 Upgrade the Voice Gateway Media Card software. See Procedure 58 on page 396. Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 383 of 770 6 Restart the Voice Gateway Media Card. See Procedure 59 on page 400. 7 Upgrade and distribute the IP Phones firmware on the Voice Gateway Media Card. See Procedure 60 on page 401. Note: To upgrade the Voice Gateway Media Card firmware, see Procedure 61 on page 407. Upgrade options Once the Voice Gateway Media Card loadware and IP Phone firmware has been verified, there are three upgrade options: 1 Upgrade the Voice Gateway Media Card software only. It may only be necessary to upgrade the Voice Gateway Media Card software. This option is used most frequently; however, verify if an IP Phone firmware upgrade is also required. 2 Upgrade both the Voice Gateway Media Card software and the IP Phone firmware. Note: Defer restarting the cards until the end of the firmware upgrade. If the IP Phones are registered to the Signaling Server, rebooting the Voice Gateway Media Card does not affect the telephones as long as they are not using a gateway channel on the rebooted card. However, if the IP Phones are registered to the Voice Gateway Media Card, resetting the card causes the IP Phone to reboot and reregister. 3 Upgrade only the IP Phone firmware. Note: In this case, restart all the IP Phones instead of the Voice Gateway Media Cards. To do this, select a single test IP Phone and reset the firmware only on that test IP Phone before completing the procedure on all IP Phones. If the upgrade works properly, use the umsUpgradeAll command to complete the upgrade on all the IP Phones. IP Phone 2001, IP Phone 2002, and IP Phone 2004 firmware requirements The IP Phone 2001, IP Phone 2002, and IP Phone 2004 firmware can be upgraded in the field. IP Line Description, Installation, and Operation Page 384 of 770 Configuration of IP Telephony nodes using Element Manager The file server can be a dedicated external file server, the Signaling Server, or a Voice Gateway Media Card. If a file server is used to store the firmware file, the following items are required to access the firmware: • IP address of the file server • routing table • file path to the file server • user name and password required to access the file server This information is configured in Element Manager under Firmware on the Edit window. See Figure 106 on page 363. • For a node using the Signaling Server as the Leader, no Firmware Server configuration is necessary since the files are stored on the Signaling Server and by default, the files are retrieved from the Signaling Server. • For nodes that are not using the Signaling Server as the Leader, configure the FTP access information for the Signaling Server or some other server as the Firmware server. UFTP IP Phones use UNIStim File Transfer Protocol (UFTP) to transfer the firmware; therefore, the customer’s network must support UFTP. The customer's network must open port 5105. Note: If the firmware cannot be transferred due to firewall restrictions (such as when the IP Phone is behind a firewall that has port 5105 blocked), then upgrade the IP Phone with the current firmware version before distributing the telephone. Default location of firmware files The default location of the firmware files is different depending on the system configuration, due to limitations of the various platforms: • Signaling Server: — The firmware file is stored on the Signaling Server in the “/u/fw” directory. 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager • Page 385 of 770 node using a Voice Gateway Media Card as the Leader card (the files can be located in any of the following locations): — The firmware files can be retrieved from the system's Signaling Server. — If the Voice Gateway Media Card is a Media Card, the files are placed in the /C:/fw directory on the card. — If the Voice Gateway Media Card is an ITG-P 24-port line card, the files attempt to store in the /C:/fw directory on the card. If there is not enough storage space, the files can be stored on a PC Card plugged into the card faceplate (/A: drive). — The files can be placed on an alternate file server. IP Phone Firmware upgrade from a new Voice Gateway Media Card Use Element Manager to upgrade the IP Phone firmware files to the new Voice Gateway Media Card. See Procedure 60 on page 401. IP Line Description, Installation, and Operation Page 386 of 770 Configuration of IP Telephony nodes using Element Manager Determine Voice Gateway Media Card software version To determine the version of software on the Voice Gateway Media Card, follow the steps in Procedure 54. Procedure 54 Determining card software version 1 Click Software Upgrade from the navigation tree. 2 Click Voice Gateway Media Card (LW). The Voice Gateway Media Card (LW) Upgrade window opens. See Figure 120. Figure 120 IP Telephony (LW) Upgrade 3 Expand a node and select a card in the node. See Figure 121 on page 387. 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 387 of 770 Figure 121 LW Version window IP Line Description, Installation, and Operation Page 388 of 770 Configuration of IP Telephony nodes using Element Manager 4 Click the LW Version button located to the right of the card information. The software version running on the card is displayed in the pane in the center of the Voice Gateway Media Card (LW) Upgrade window under the list of cards. See Figure 122. In this example, the software version displayed is for the ITG Pentium card. Figure 122 LW version for the ITG Pentium 5 Note the software version for the card. End of Procedure 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 389 of 770 Determine the IP Phone firmware version To determine the version of firmware on the Voice Gateway Media Card, follow the steps in Procedure 55. Procedure 55 Determining the IP Phone firmware version 1 Click Software Upgrade from the navigation tree. 2 Click IP Telephone (FW) from the expanded Software Upgrade menu. The IP Telephone (FW) Upgrade window opens. See Figure 123 on page 390. At the top of the screen, there are two radio buttons: i. Distribute to Nodes – disables all elements that are not Leaders. Distribute to Nodes is the default since IP Line is responsible for distributing from the Leader to all Followers in a node. ii. Distribute to Elements – enables all the elements in case it is necessary to distribute the firmware to some elements which have failed. IP Line Description, Installation, and Operation Page 390 of 770 Configuration of IP Telephony nodes using Element Manager Figure 123 IP Telephone (FW) Upgrade window 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager 3 Page 391 of 770 Expand a node and select a card. See Figure 124. Figure 124 FWVersionShow button 4 Click the fmVersionShow button located to the right of the card information. IP Line Description, Installation, and Operation Page 392 of 770 Configuration of IP Telephony nodes using Element Manager The firmware version running on the card is displayed in the pane in the center of the IP Telephone (FW) window. In the example displayed in Figure 124 on page 391, the firmware versions shown are for the ITG Pentium card. 5 Note the firmware version for the card. End of Procedure Download the current software and IP Phone firmware To check for the latest software and IP Phone firmware releases on the Nortel Networks Customer Support web site, follow the steps in Procedure 56. Procedure 56 Downloading loadware and firmware from the Nortel Networks web site 1 Check the Nortel Networks Customer Support web site for the latest IP Line 4.0 software and IP Phone firmware releases. See Appendix F: “Download IP Line 4.0 files from Nortel Networks web site” on page 763. Note: The IP Line 4.0 software and IP Phone firmware files are contained in the SSE-4.00.xx Signaling Server CD Image file in the “CS 1000” product list on the Nortel Networks web site. The file contains: • The IPL400xx.p2 and IPL400xx.sa software files. The IPL400xx.p2 file is the IP Line application for the ITG-P 24-port card and the IPL400xx.sa is the IP Line application for the Media Card. • The 0602Bxx.BIN (Phase I IP Phone 2004), 0603Bxx.BIN (Phase I IP Phone 2002), and 0604Dnn.BIN (Phase II IP Phone 2001, IP Phone 2002, and IP Phone 2004) firmware files. For example, a firmware version can be labelled 0602B38 or 0603B38. This means IP Phone firmware version 1.38. • 553-3001-365 — The 02 represents the IP Phone 2004 and 03 is the IP Phone 2002. — The letter B represents the version number 1. — 38 represents the release number .38. A readme.txt file. The readme.txt file explains important considerations for installing the new loadware and firmware versions. Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 393 of 770 The readme file also includes identifying information for the loadware and firmware files such as the date and time, size and checksum. 2 Compare the latest software and firmware versions available to the loadware and firmware versions currently installed on the Voice Gateway Media Card and the IP Phones. 3 If more recent files are available, download the SSE-4.00.xx Signaling Server CD Image file. End of Procedure Upload the software and firmware files to the file server The next step is to upload the files from the Element Manager PC to the file server. The “Centralized file upload” window enables software and firmware to be uploaded and stored on the Signaling Server. These files can then be downloaded to the IP Phones and the Voice Gateway Media Cards using the firmware and software upgrade functions available from the Software Upgrade menu. The Signaling Server can be used as a central distribution point to load and activate software, firmware and patches. To upload the files, follow the step in Procedure 57 on page 394. Note: For patches, Element Manager does not need to upload to Signaling Server first. The Signaling Server obtains the patch file from the Element Manager PC directly. IP Line Description, Installation, and Operation Page 394 of 770 Configuration of IP Telephony nodes using Element Manager Procedure 57 Uploading software and firmware files 1 Click Software Upgrade in the navigation tree. 2 Click File Upload. The Centralized file upload window opens. See Figure 125 on page 395. 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 395 of 770 Figure 125 System Utility > File Upload > Centralized file upload 3 Click the Browse button. In the Choose File dialog box, select the path and file to upload. Alternatively, enter the path and filename for the file to be uploaded. Note: Only one software or firmware file can be uploaded at a time. IP Line Description, Installation, and Operation Page 396 of 770 Configuration of IP Telephony nodes using Element Manager 4 Once selected, the path and file name appear in the text box to the left of the Browse button. See Figure 126. Figure 126 Firmware file text box 5 Click the File Upload button. 6 The firmware file appears in the list at the top of the window when it is uploaded. Note: To delete older versions of the firmware and software files, click the check box associated with the older file and then click the Delete button located at the top of the column of check boxes. End of Procedure Upgrade the Voice Gateway Media Card software Once the files are uploaded to the file server, the cards must be upgraded to the newest software version. To upgrade the card software, follow the steps in Procedure 58. Procedure 58 Upgrading the card software 1 Click Software Upgrade from the navigation tree. 2 Click Voice Gateway Media Card (LW) from the expanded Software Upgrade menu. The Voice Gateway Media Card (LW)) Upgrade window opens. See Figure 127 on page 397. 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 397 of 770 Figure 127 IP Telephone (FW) Upgrade window 3 Expand a node. 4 Select the card(s) to upgrade by selecting the check box to the left of the card information. Note: Element Manager supports upgrading the software on up to four cards at the same time. IP Line Description, Installation, and Operation Page 398 of 770 Configuration of IP Telephony nodes using Element Manager 5 In the lower part of the window, click the radio button of the most current software version. Note: If the card receiving the upgrade is an ITG-P 24-port line card, select the radio button next to the most current version of the ITG-P 24-port line card software (IPL400xx.p2). If the card receiving the upgrade is a Media Card, select the radio button next to the must current version of the Media Card software (IPL400xx.sa). 6 Click the Loadware Upgrade button at the bottom of the window. A confirmation dialog box appears similar to the dialog box in Figure 128. 7 Click OK to confirm the card upgrade. The upgrade begins. Figure 128 Loadware Upgrade confirmation dialog box The Loadware Upgrade Progress window opens. See Figure 129 on page 399. The status of the upgrade is shown for each of the cards selected to receive the software upgrade. This status of the upgrade can be Work in progress, Upgrading, Fail, or Finished. See Figure 129 on page 399 and Figure 130 on page 399. 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 399 of 770 Figure 129 Loadware Upgrade Progress – upgrade status Figure 130 Loadware Upgrade Progress – completion status 8 Click OK. 9 Repeat steps 4-8 for the other card(s) that have to be upgraded. End of Procedure IP Line Description, Installation, and Operation Page 400 of 770 Configuration of IP Telephony nodes using Element Manager Reboot the Voice Gateway Media Card Follow the steps in Procedure 59 to reboot a Voice Gateway Media Card. Procedure 59 Rebooting the Voice Gateway Media Card 1 Disable the Voice Gateway Media Card. 2 Click System Status and then IP Telephony. The IP Telephony Information window opens. 3 Expand the node containing the card to be rebooted. 4 Click the Reset button to reboot the card. Note 1: The cards remain in the “Disabled” state after the upgrade, so a “Reset” command can be used. The cards can also be reset by using a pointed object to press the Reset button on the card’s faceplate. Note 2: Reboot the Leader card only if the node is using the Voice Gateway Media Card as the Leader; that is, the Signaling Server is not the Leader. 5 Click the card’s Status button in the IP Telephony Information window to verify the status of the Voice Gateway Media Card. 6 Use the LD 32 ENLC command to re-enable the Voice Gateway Media Cards. 7 Repeat these steps for each Voice Gateway Media Card that received the software upgrade. End of Procedure Upgrade the IP Phone firmware When the IP Line 4.0 software has been upgraded on the Voice Gateway Media Cards, determine if an IP Phone firmware upgrade is also required. If an upgrade is required, the Voice Gateway Media Cards must be upgraded to the newest IP Phone firmware version. To upgrade the firmware required for 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 401 of 770 the IP Phones, follow the steps in Procedure 60 on page 401. This procedure has two major components: • loading the IP Phone firmware onto each Voice Gateway Media Card in the node • propagating the firmware from the Voice Gateway Media Card to each IP Phone registered on that card Note: A firmware download does not occur with IP Phones performing a Virtual Office login or Media Gateway 1000B (MG 1000B) login to a remote system. No firmware upgrade takes place during a Virtual Office Login or MG 1000B user registration with the LTPS. The registration is allowed because the IP Phone firmware version must be 1.33 or later to perform a Virtual Office login or MG 1000B user registration. The umsUpgradeAll command has no impact on Virtual Office Login IP Phones. These IP Phones are not reset. If the Virtual Office Login is on the same Call Server, then the IP Phone firmware is upgraded after the user logs out. If the Virtual office Login is between different Call Servers, then the IP Phone just registers back to its home LTPS and follows the normal firmware rules for regular registration. When the umsUpgradeAll command is executed, MG 1000B user IP Phones that are on active calls are flagged. After the IP Phones become idle, the IP Phones are switched by the Call Server back to the MG 1000B for the firmware upgrade. Follow the steps in Procedure 60 to upgrade IP Phone firmware Procedure 60 Upgrading the IP Phone firmware 1 Disable the Voice Gateway Media Cards before updating the firmware. Use the LD 32 DISI command to disable the card. 2 Verify that all Voice Gateway Media Cards that require a firmware upgrade have established a signaling link with the Call Server. IP Line Description, Installation, and Operation Page 402 of 770 Configuration of IP Telephony nodes using Element Manager To verify the link is available between the Call Server and the card, Telnet to each card and log into the card. From the command line, type pbxLinkShow. The status of the Call Server link appears. If the link is active the window displays the following: RUDPLinkState = Up 3 Click Software Upgrade on the navigation tree. 4 Click IP Telephone (FW) from the expanded Software Upgrade menu. The IP Telephone (FW) Upgrade window opens. See Figure 131. Figure 131 IP Telephone (FW) Upgrade window 5 553-3001-365 Expand the node containing the cards that are to receive the IP Phone firmware upgrade. Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 403 of 770 6 Click the Distribute to Elements radio button in the upper right of the window. 7 Select the card(s) to upgrade by selecting the check box to the left of the card information. See Figure 127 on page 397. Note: Element Manager can upgrade the firmware on a maximum of four cards at the same time. 8 In the lower part of the window, click the radio button next to the most current version of the firmware. Click the Firmware Distribute button. 9 Complete this step for each version of the firmware that must be distributed. CAUTION Downloading an incorrect version of the IP Phone firmware can result in extended service interruptions and can require special recovery procedures. A confirmation dialog box appears similar to the confirmation dialog box in Figure 132. 10 Click OK to confirm the firmware upgrade to the card. The upgrade begins. Figure 132 Firmware Upgrade confirmation dialog box The Firmware Upgrade Progress window opens. See Figure 133 on page 404. The status of the upgrade is shown for each of the cards selected to receive the firmware upgrade. IP Line Description, Installation, and Operation Page 404 of 770 Configuration of IP Telephony nodes using Element Manager Figure 133 Firmware Upgrade Progress 11 Repeat the preceding steps for all the card(s) that have to be upgraded. The IP Phones continue to run the old firmware until each IP Phone re-registers with a Voice Gateway Media Card containing the new IP Phone firmware. Note: Commands are available from the IPL> command line to upgrade a single IP Phone immediately, all IP Phones immediately, or schedule all IP Phones to be upgraded at a later time. Before doing this, verify that each Voice Gateway Media Card has the correct IP Phone firmware version. 12 Select an IP Phone for test purposes. 13 Telnet to the Voice Gateway Media Card and then log into the IPL> command line, and enter the following: isetReset “xxx.xxx.xxx.xxx” where xxx.xxx.xxx.xxx is the IP Address of the selected telephone. 14 Monitor the display on the test telephone. As the IP Phone upgrades the firmware, note the IP Address of the Voice Gateway Media Card from which the telephone is receiving its upgrade. 15 Press the Services key (key with globe with arrow pointing East and West on the IP Phone 2002/IP Phone 2004). The Services key enables access to the Telephone Options list. 553-3001-365 a. Press Select to select Telephone Options. b. Use the Navigation keys to scroll to Set Info. Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager c. Page 405 of 770 Press the Select softkey, then press the Navigation keys until it displays FW Version:. Select the appropriate firmware on the Voice Gateway Media Card Note: For example, a firmware version can be labelled 0602B38 or 0603B38, which means IP Phone firmware version 1.38. • 02 represents the IP Phone 2004 and 03 represents the IP Phone 2002. • B represents the version number 1. • 38 represents the release number .38. 16 Lift the handset of the IP Phone and make a call to verify the IP Phone works. 17 Before proceeding, ensure the time on the card is set correctly. Telnet to each Voice Gateway Media Card and log in. At the IPL> command line, enter the following: umsUpgradeAll “hh:mma/p” hh:mma/p specifies the time when the upgrade will occur, a represents A.M., and p represents P.M. The time is in Standard format. For example, umsUpgradeAll “11:30a” or umsUpgradeAll “2:45p”. At the time specified, all the IP Phones registered to the Voice Gateway Media Card go out of service. This can take several minutes. Upon completion of the firmware upgrade, the IP Phones are brought back online in groups of ten. CAUTION If the umsUpgradeAll command is used without the time parameter, all IP Phones registered on cards that are logged into are immediately taken out of service. Use the time parameter with the command to prevent this from happening. After the test telephone is working, the umsUpgradeAll command does not require the time parameter. However, if the time parameter is not used, the command immediately resets all the IP Phones currently registered on that line card. IP Line Description, Installation, and Operation Page 406 of 770 Configuration of IP Telephony nodes using Element Manager To schedule a specific reset time for the IP Phones, instead of resetting them immediately, check the time on all the cards. Reset the time, if necessary, to ensure all cards have the same time, and then issue the umsUpgradeAll “hh:mma/p”, where “hh:mma/p” represents the time the upgrade is scheduled to occur. 18 At the IPL> prompt, verify the IP Phones for each Voice Gateway Media Card are upgraded by entering the following: isetShow 19 Inspect the list to ensure all IP Phones have the correct firmware version. 20 For any IP Phones that did not upgrade successfully, try one of the following (in order): • Use the isetReset ''IP Address'' command. • Enter the following combination of key strokes at the telephone console: release, mute, up, down, up, down, up, mute, 9, release. • Power the telephone off and then on again. If the upgrade was unsuccessful on any of the IP Phones, the cause is probably due to one of the following: • One of the Voice Gateway Media Cards did not upgrade its software successfully. • An IP Phone’s firmware version was unable to be upgraded by the Voice Gateway Media Card in the normal manner. • The umsUpgradeAll command has not been issued. • One of the cards might not have been reset. If the upgrade was unsuccessful, re-do the appropriate procedure. If the upgrade is still unsuccessful, contact a technical support representative for further assistance. End of Procedure For additional information on configuring the IP Phones, refer to IP Phones: Description, Installation, and Operation (553-3001-368). 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 407 of 770 Upgrade the Voice Gateway Media Card firmware The minimum versions of IP Line 4.0 software for the Voice Gateway Media Card vintages earlier than NTVQ01BB and NTVQ01AB are: • Version 6.7 for the Media Card • Version 5.7 for the ITG-P 24-port card The minimum versions of IP Line 4.0 software for the Voice Gateway Media Cards NTVQ01BB and NTVQ01AB is Version 8.0. There is no need to download the Version 8.0 software for the Voice Gateway Media Cards NTVQ01BB and NTVQ01AB as the software is pre-loaded at the factory. To upgrade the card firmware, follow the steps in Procedure 61. Procedure 61 Upgrading the Voice Gateway Media Card firmware 1 Check the Nortel Networks web site for the most current versions of the firmware for the ITG-P 24-port line card and Media Cards. 2 Once the most current version of the firmware has been downloaded, follow the steps in: • Procedure 99 on page 639 to upgrade the firmware on the ITG-P 24-port line card • Procedure 100 on page 642 to upgrade the firmware on the Media Cards End of Procedure IP Line Description, Installation, and Operation Page 408 of 770 Configuration of IP Telephony nodes using Element Manager Configure Alarm Management to receive IP Line SNMP traps Alarm Management cannot be configured using Element Manager. OTM 2.2 must be used to configure the Alarm Management feature to receive IP Line SNMP traps. See Procedure 38 on page 322. Assemble and install an IP Phone To assemble and install an IP Phone, refer to IP Phones: Description, Installation, and Operation (553-3001-368). Change the default IPL> CLI Shell password The IPL> Command Line Interface (CLI) is password-protected to control Telnet access and access to the local maintenance port. The same user name and password also controls FTP access to the Voice Gateway Media Card. The IPL> CLI has a default user name of itgadmin and a default password of itgadmin. The default user name and password must be changed as a preventative security measure. See “IPL> CLI Shell user name and password” on page 421 and Procedure 63 on page 435. Configure the IP Phone Installer Passwords The IP Phone Installer Password, used when changing the TN on the telephone, controls registration with a virtual line TN on the Call Server. Refer to page 425 for more information about the IP Phone Installer Passwords. To enable and set the administrative IP Phone Installer Password, see Procedure 63 on page 435. If required, enable and set a temporary IP Phone Installer Password. See Procedure 64 on page 438. 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 409 of 770 Element Manager can also be used to configure the IP Phone Installer Passwords. See “Setting the IP Phone Installer Password” on page 558. Import node configuration from an existing node It is possible to import a node and its configuration data from an existing node into Element Manager. For example, if Node 151 exists, but does not exist on the Call Server, then Node 151 can be imported into Element Manager. Once imported, the node configuration data can be updated and edited. Procedure 62 Importing node files 1 In the navigation tree, click Configuration and then IP Telephony. 2 Click Node Summary. The Node Summary window opens. 3 Click the Import Node Files button. The Import Node Files window opens. See Figure 134 on page 410. IP Line Description, Installation, and Operation Page 410 of 770 Configuration of IP Telephony nodes using Element Manager Figure 134 Import node files 4 Enter the Management LAN (ELAN) subnet IP Address of the Leader in the text box. This address is used to retrieve the node files. 5 Click the Import button. If the node already exists on the Call Server, a message appears indicating that the node already exists on the Call Server. See Figure 135 on page 411. 553-3001-365 Standard 3.00 September 2004 Configuration of IP Telephony nodes using Element Manager Page 411 of 770 Figure 135 Duplicate node information If the node does not exist, Element Manager tries to write the configuration to the Call Server. If it succeeds, a message indicating the import was successful appears. See Figure 136 on page 412. If Element Manager cannot write the configuration to the Call Server, a fail reason appears in the text area of the Import Node Files window. If the import is successful, information appears in the text area of the Node Import Files screen. See Figure 136 on page 412. A message box also appears. In the message box, click the OK button to proceed to the Node Summary window. The node information can then be viewed and, if necessary, edited. If the node import is not successful, an error message appears in the text box area. IP Line Description, Installation, and Operation Page 412 of 770 Configuration of IP Telephony nodes using Element Manager Figure 136 Import Node Files – successfully imported node End of Procedure 553-3001-365 Standard 3.00 September 2004 452 Page 413 of 770 IP Line 4.0 administration Contents This section contains information on the following topics: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 IP Line feature administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Corporate Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Private Zone configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Virtual Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . e911 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802.1Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 415 416 416 419 420 Password security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SNMP community names strings . . . . . . . . . . . . . . . . . . . . . . . . . . . IPL> CLI Shell user name and password . . . . . . . . . . . . . . . . . . . . . Node password synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . IP Phone Installer Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Default user name and password . . . . . . . . . . . . . . . . . . . . . . . . . . . 420 421 421 423 425 439 IP configuration commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441 TLAN configuration commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441 Display the number of DSPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 Display IP Telephony node properties . . . . . . . . . . . . . . . . . . . . . . . . . 443 Display Voice Gateway Media Card parameters . . . . . . . . . . . . . . . . . 445 Packet loss monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448 Transfer files using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449 Download the IP Line 4.0 error log. . . . . . . . . . . . . . . . . . . . . . . . . . . . 451 IP Line Description, Installation, and Operation Page 414 of 770 IP Line 4.0 administration Reset the Operational Measurements file . . . . . . . . . . . . . . . . . . . . . . . 451 Introduction This chapter explains how to administer IP Line 4.0 and the Voice Gateway Media Cards on the Meridian 1 and CS 1000 systems. Administration procedures include activities such as monitoring the system status, operational reports, performing upgrades, changing configuration, and adding, changing, and removing cards. Administration does not include engineering, provisioning, initial installation and configuration, maintenance, or troubleshooting. The Voice Gateway Media Card provides four administration interfaces: • Optivity Telephony Manager (OTM) 2.2 OTM’s IP Line 4.0 application provides a GUI to the Voice Gateway Media Card. OTM 2.2 is used to Telnet to the card, install and upgrade software and firmware, configure alarm event reporting, view and update a card’s property and configuration data, add new cards to a node, schedule reports and other related tasks. • Element Manager Element Manager is a web server that provides a GUI using the Internet Explorer 6.0.2600 (or later) web browser. Element Manager is used to Telnet to the card, install and upgrade software and firmware, configure alarm event reporting, view and update card property and configuration data, add new cards to a node, schedule reports, and other related tasks. • IPL> Command Line Interface (CLI) Use the CLI to display card and node status, change passwords, check software versions, view channel states, and other card information. The CLI is also used for expert level support and debug. The prompt for the CLI on the Voice Gateway Media Card is IPL>. Access the CLI through a direct serial connection to the I/O panel serial port, the Maint Port on the faceplate, or through a Telnet session. Use a VT-100 terminal emulation program set to 9600 baud, 8 bits, no parity, one stop bit. 553-3001-365 Standard 3.00 September 2004 IP Line 4.0 administration • Page 415 of 770 Overlays Use the same LDs, commands, and messages for the Voice Gateway Media Card as for any other line card. IP Line feature administration Corporate Directory LD 11 accepts Class of Service (CLS) CRPA/CRPD for IP Phones. Table 58 Corporate Directory: LD 11 configuration Prompt Response Description REQ: NEW CHG Add new data or change existing data. TYPE: i2002 i2004 i2050 Enter terminal type. TN ls Enter IP Phone TN. CRPA CRPD Enable/Disable the Corporate Directory feature for this TN. ... CLS The Call Server service change does not affect Corporate Directory immediately. If a telephone is in Corporate Directory mode, and there is a service change to set CLS as CPRD, then the current display and key handling should not be affected. The changed CLS occurs only when the user quits the Corporate Directory application and enters again. For more information about the operation of the Corporate Directory feature, refer to Optivity Telephony Manager: Installation and Configuration (553-3001-230). Note: Corporate Directory is not supported on the IP Phone 2001. IP Line Description, Installation, and Operation Page 416 of 770 IP Line 4.0 administration Private Zone configuration DSP channels and IP Phones are set as Shared or Private based on zone configuration. This is accomplished through the parameter, zoneResourceType, in the zone configuration commands in LD 117. The parameter specifies the zone to be either shared or private. A zone is configured in LD 117 as follows: NEW ZONE [ ] CHG ZONE [ ] By default, a zone is configured as Shared (zoneResourceType=shared). Virtual Office The IP Phone Virtual Office feature uses the Station Control Password (SCPW) feature. The SCPW password can be maintained either through LD 11 administration or by the user if Flexible Feature Code (FFC) code access is configured. If the SCPW is not configured for a TN registering by means of the Virtual Office feature, the login is rejected. An appropriate error message is displayed to alert the user that a password must be configured. Enable the SCPW in the Customer Data Block (CDB) by setting the length of the SCPW (scpl). The SCPW must be at least four digits. To login using Virtual Office, the TN associated with the current IP Phone registration must be configured with the CLS VOLA (Virtual Office Login Allowed). The TN associated with the user ID for the login must be configured with the CLS VOUA (Virtual Office User Allowed). 553-3001-365 Standard 3.00 September 2004 IP Line 4.0 administration Page 417 of 770 Two CLSs restrict Virtual Office usage. The two classes of services are: • VOLA/VOLD – defines whether this TN (physical IP Phone) allows/disallows a Virtual Office login option. • VOUA/VOUD – defines if a specific remote user can log onto this TN (allows/disallows a particular user to login using Virtual Office). IP Line Description, Installation, and Operation Page 418 of 770 IP Line 4.0 administration Table 59 shows the CLS for LD 11. Table 59 LD 11 – Virtual Office Login for IP Phones Prompt Responses Description REQ: NEW CHG TYPE: i2001 i2002 i2004 i2050 For IP Phone 2001, IP Phone 2002, and IP Phone 2004, IP Softphone 2050, or MVC 2050. The system accepts this response if it is equipped with packages 88 and 170. The IP Phone 2001 and IP Phone 2002, IP Softphone 2050, and MVC 2050 are also restricted by the IP Phone License setting. CUST xx Customer number as defined in LD 15 BUID Dialable DN, main office user ID Enter X to delete. MOTN lscu Main Office Terminal Number Format for Large System and CS 1000E system, where l = loop, s = shelf, c = card, u = unit. Accept default for CS 1000S, Media Gateway 1000B, Media Gateway 1000T, or Small System Main Office ... CLS (VOLA VOLD Virtual Office login operation is allowed/denied on this TN CLS (VOLA) VOUD Allow/Disallow Virtual Office user on this TN using other IP Phone 553-3001-365 Standard 3.00 September 2004 IP Line 4.0 administration Page 419 of 770 e911 If 911 is dialed while logged into Virtual Office, the LTPS re-directs the 911 call to the local area 911 service (PSAP), not the remote Call Server 911 service. Table 60 describes the process. Table 60 e911 process Step Description 1 The LTPS aborts the call on the remote Call Server. 2 The LTPS displays Emergency Call on the IP Phone. 3 The LTPS logs the IP Phone out of Virtual Office. 4 The LTPS reconnects to the local Call Server. 5 The LTPS restarts the 911 call, thus reaching the correct PSAP. Note: The extra processing adds 5 seconds to the call setup time. 6 After the emergency call ends, the IP Phone remains registered to the Home LTPS as a normal telephone, in case the PSAP makes a call back to the originator of the emergency call. After the IP Phone is redirected to its Home Site, it is not allowed to initiate a new operation for five minutes. This prevents the user from accidentally dialing the emergency DN and hanging up. In this case, the emergency response personnel might call back to confirm the accidental call (and thus confirm that there is no emergency). If the IP Phone were allowed to immediately resume a Virtual Office login to another site, it could not receive the call back. If the local TN has another IP Phone Virtual Office logged into it when it comes back, the non-emergency IP Phone is pre-empted. Note: If this occurs, ESAxxx messages are generated on the system TTY. Configuration The Emergency Services Access (ESA) feature must be configured on all nodes participating in Virtual Office logins. No other special configuration is required. IP Line Description, Installation, and Operation Page 420 of 770 IP Line 4.0 administration For more information, refer to Emergency Services Access: Description and Administration (553-3001-313). 802.1Q The 802.1Q support for IP Phones is configured and controlled using the telephone’s user interface or DHCP. The DHCP approach eliminates the requirement to manually set the VLAN ID as part of the installation. The configuration is composed of two items: setting the “p” bits and setting the VLAN ID. OTM 2.2 and Element Manager have two fields for setting 802.1Q support: • Enable 802.1Q support: A checkbox that, when checked, sets the priority bits to the value specified by the next item. If the checkbox is unchecked, the IP Phone 2001/IP Phone 2002/IP Phone 2004 sends out the default priority of 6. • 802.1Q Bits value (802.1p): A 802.1Q priority bit value field that sets the value the IP Phone 2001, IP Phone 2002, and IP Phone 2004 sent out in the priority field. The range is 0 – 7. Password security The following password security features must be configured and administered in IP Line 4.0: 1 SNMP community name strings 2 IPL> CLI Shell password 3 Call Server’s Level 1 Password (PWD1) 4 IP Phone Installer Password The SNMP community name strings, IPL> CLI Shell password, and Call Server’s Level 1 Password (PWD1) operate at the card level. The IP Phone Installer Password works at the node level. 553-3001-365 • The SNMP community name strings are contained in the card properties that were transmitted to each card. • The IPL> CLI Shell password is set on each individual card. Standard 3.00 September 2004 IP Line 4.0 administration Page 421 of 770 • The Level 1 Password (PWD1) is set at the Call Server and is sent to all cards in the node. • The IP Phone Installer Password is first applied to one card in the node, and then is applied to all the cards in the node. SNMP community names strings SNMP community names strings are required to access the Voice Gateway Media Card. There are three community names: public, admingroup2, and admingroup3. OTM 2.2 stores the community names for Meridian 1 systems. See Figure 71 on page 285. Procedure 27 on page 285 explains how to change the SNMP community names to control access to the IP Telephony node. Element Manager stores the community names for CS 1000 systems. See Figure 98 on page 348. Procedure 43 on page 348 is used to change the SNMP community name to control access to the IP Telephony node. IPL> CLI Shell user name and password The IPL> Command Line Interface (CLI) is password-protected to control Telnet access and access to the local maintenance port. The same user name and password also controls FTP access to the Voice Gateway Media Cards. Login banner The IP Line 4.0 login banner information includes the IP 4.0 line card software version, ELAN IP address, card type, firmware version, current time and date, system name, system location, and system contact. IP Line Description, Installation, and Operation Page 422 of 770 IP Line 4.0 administration The following information is an example of the login banner displayed on the Media Card: Login: Password Welcome to the IP Line command line. Software Version: IPL-4.00.01 Management IP: 47.11.216.216 Host Type: Media Card Firmware Version: ITG Firmware Rls 5.7 SysName: ITG Line SysLocation: TN 10 0 SysContact: designer OS Time: Date (04/03/2004) Time (09:07:43) Use “logout” to logout. Idle session timeout = 20 minutes. IPL> Password Guessing Protection IP Line 4.0 provides protection against password guessing. This protection blocks a hacker from attempting to log into the Voice Gateway Media Card’s shell by making repeated attempts to guess the shell user ID and password. The password guessing protection is applicable to either a tip session (direct maintenance port-connected TTY session) or a Telnet session. The password guessing protection feature is described as follows: 553-3001-365 • There is a login failure threshold of 3 and a lockout period of 10 minutes. This is not user configurable. • Password guessing protection is enabled by default when the card starts the first time. The protection can be disabled and re-enabled at the VxWorks shell. Entering the shellLoginProtectSet 0 command disables the protection and shellLoginProtectSet 1 enables it. Standard 3.00 September 2004 IP Line 4.0 administration • Page 423 of 770 When the login failure threshold is exceeded (by 3 consecutive failed login attempts), the system raises an “ITG1038” critical alarm. This alarm is sent to indicate the card’s login has been locked due to too many incorrect password entries. Alarm value = ITG alarm 38 perceivedSeverity = Critical probableCause = Unauthorized maximum access attempts Alarm text = IPL login protection (login locked) When the 10 minute timer expires for the lockout period, the system raises an “ITG5038” cleared alarm. The clear message is sent after the lockout period expires. perceivedSeverity = Cleared probableCause = Unauthorized maximum access attempts Alarm text = IPL login protection (login available) • There is no online indication or warning during the failed login attempt lockout state. Everything appears the same to the user trying to login. The user is not informed that login blocking has been activated. The login is ignored for 10 minutes. Note: Both the “critical” and “cleared” alarms send an SNMP trap to the system administrator. For security reasons, these two alarms do not call the syslog function as the other itgAlarms do, so no syslog message is displayed on the console or written in the syslog file. • On the Voice Gateway Media Card, the faceplate displays GO38 (ITG1038) when the ITG1038 alarm is received, since it is a critical alarm. The ITG5038 clears GO38 from the faceplate when the 10 minute timer expires. Node password synchronization The BOOTP.TAB, CONFIG.INI, and IP Phone firmware files must be the same on all cards in the system. The cards that can be in the system are the ITG-P 24-port line card, the Media Card 8-port and 32-port line card, and the Signaling Server. To maintain a consistent configuration within the system, files are transferred from Leader 0 to the Follower cards using FTP. IP Line Description, Installation, and Operation Page 424 of 770 IP Line 4.0 administration In order for the FTP process to work correctly, all the cards in a node must be synchronized with the same user ID and password. Once the Voice Gateway Media Cards are synchronized with the Call Server, the user login is synchronized with the Call Server’s PWD1. The cards can then only be accessed by using the Call Server’s Level 1 Password (PWD1) user ID and password. A card uses its user ID and password when it tries to access another card to FTP files. The FTP fails unless all the cards have the same user ID and password, due to failed user authentication. Therefore, a unique user ID and password should be used within one system. Since most applications (except the Gatekeeper) communicate directly with the Call Server, the Call Server’s Level 1 PWD1 user ID and password is the unique password among all platforms. Level 1 Password (PWD1) The minimum password length on the Call Server is four characters. The minimum password on the Voice Gateway Media Card and the Signaling Server is eight characters. To make the passwords match, the PWD1 is padded at the end with spaces if the password is less than eight characters. For example, if the Call Server’s PWD1 is “0000”, it is padded to the right with the four space characters to become “0000 ”. This is done automatically by the software. It is not necessary to manually add the spaces. Password Updates The Call Server’s PWD1 user ID and password is sent to all cards at the following times: 553-3001-365 • when the cards initially establish a connection with the Call Server across the ELAN • when an EDD operation is performed on the Call Server Standard 3.00 September 2004 IP Line 4.0 administration Page 425 of 770 Once the PWD1 information is downloaded from the Call Server, it is saved in the card’s NVRAM. If a card has not yet established a link with the ELAN subnet, the user ID and password that are currently stored in the card’s NVRAM are used to log in. The user ID and password might not match the PWD1 on the Call Server because the Call Server has not yet downloaded the current PWD1 to the card. Once the ELAN subnet connection is established, the user ID and password are synchronized on all cards, and the new user ID and password are saved in the card’s NVRAM. Since all cards automatically receive the user ID and password from the Call Server, the password can be changed in a single location, the Call Server’s CLI. This eliminates the need to change the password on every card in the node (just change the password once on the Call Server). When the password is changed at the Call Server, the password is automatically sent to all the Voice Gateway Media Cards. A user can change the user ID and password login on any card using the shellPasswordSet CLI command. However, updates from the Call Server overwrite the cards’ user ID and password in the NVRAM. If the PWD1 is changed and an EDD operation is not performed, the cards can contain a mixture of old and new passwords. This could happen if a new card is plugged in, an existing card reboots or loses and reestablishes its ELAN subnet connection. Nortel Networks recommends that an EED be performed when the PWD1 password is changed on the Call Server. Performing an EDD ensures that all cards have the new PWD1 user ID and password. For more information on the PWD1 Level 1 password, see the “LD 17 Gate Opener PWD (Password)” section in Software Input/Output: Administration (553-3001-311). IP Phone Installer Password An IP Phone displays the node ID and Terminal Number (TN) of the IP Phone for five seconds as the IP Phone boots up. IP Line 4.0 password protection controls who can change the TN on the IP Phone. This feature is available on the IP Phone 2001, IP Phone 2002 and IP Phone 2004, IP Softphone 2050, and the MVC 2050. The IP Phone Installer Password protection controls registration with a virtual line TN on the Call Server. IP Line Description, Installation, and Operation Page 426 of 770 IP Line 4.0 administration Note: The IP Phone Installer Password can also set using the CLI commands in Element Manager. See “Setting the IP Phone Installer Password” on page 558. Administrator IP Phone Installer Password This feature adds basic IP Phone Installer Password protection on the IP Phones to control registration with a virtual line TN on the Call Server. This feature does not provide a user password or a Station Control Password for IP Phones. IP Phone 2004 When the password is configured, the IP Phone 2004 screen shows: 1 The four digit Node ID and a Password prompt (see Figure 139 on page 431), instead of the Node ID and TN fields (see Figure 137 on page 428). 2 When the user enters the password, an asterisk (*) is displayed for each digit entered. The password is not shown. 3 Once the Node ID and Password are entered, the user presses OK. If the password passes the Connect Server’s authentication, a screen is displayed with the TN field (see Figure 139 on page 431). IP Phone 2002 and IP Phone 2001 When the password is configured, the IP Phone screen shows: 553-3001-365 1 The four digit Node ID screen is displayed first (see Figure 140 on page 432). 2 The user is then prompted with the Password screen (see Figure 140 on page 432) instead of the TN field screen (see Figure 138 on page 429). 3 When the user enters the password, an asterisk (*) is displayed for each digit entered. The password is not shown. 4 Once the Password is entered, the user presses OK. If the password passes the Connect Server’s authentication, a screen is displayed with the TN field (see Figure 140 on page 432). Standard 3.00 September 2004 IP Line 4.0 administration Page 427 of 770 If the Node ID and Password are not entered, the registration continues after five seconds and the TN is not displayed. If an invalid Node ID password is entered, the Node ID and Password screen is displayed again. This screen is re-displayed a maximum of two times, giving the technician a total of three chances to enter the password. After three failed attempts, the registration continues as if there were no password entries. The technician can reboot the telephone and try again if more tries are needed. If the technician has entered a zero length (null) password, then the Node ID, TN, and Password screens are not displayed on the IP Phone during the registration process. This provides the most security as it prevents any entry of passwords or TNs from the IP Phone. Temporary IP Phone Installer Password A Temporary IP Phone Installer Password can be configured, which provides temporary user access to the TN for configuration. A temporary password removes the need to distribute the Node password and then change the password afterwards. The temporary password is automatically deleted after it has been used the defined number of times or when the duration expires, whichever comes first. The following are examples of situations where the Temporary IP Phone Installer Password can be used: • A department is installing an IP Softphone 2050. The technician creates a temporary password, sets an appropriate number of uses (such as allowing two logins for each IP Softphone 2050 in case a problem occurs the first time) and sets the duration to expire by the end of the weekend. The password access automatically ends before Monday morning (or sooner if the number of uses expires). • A telecommuter needs to install an IP Phone. The technician provides the temporary password that expires the next day or after two uses. When the IP Phone Installer Password protection is enabled, the Set TN is not displayed as part of the Set Info sub-menu of the Telephone Option menu. The IP Phone’s TN can be retrieved on the core CPU through the LD 20 PRT DNB and LD 32 IDU, or LD 80 TRAC, or PDT> rlmShow. It can also be found on the Voice Gateway Media Card through IPL> isetShowByIP. IP Line Description, Installation, and Operation Page 428 of 770 IP Line 4.0 administration Registration screens with TN password feature The following screens shows the existing TN entry screen that appears when the IP Phone registers: • Figure 137 displays the screen on the IP Phone 2004 if password protection is disabled or not configured. • Figure 138 on page 429 displays the screen on the IP Phone 2002 and IP Phone 2001 if password protection is disabled or not configured. Figure 137 IP Phone 2004 registration with no password checking 553-3001-365 Standard 3.00 September 2004 IP Line 4.0 administration Page 429 of 770 Figure 138 IP Phone 2002 and IP Phone 2001 registration with no password checking IP Line Description, Installation, and Operation Page 430 of 770 IP Line 4.0 administration When the TN password protection feature is configured with a non-zero length password and is enabled: • Figure 139 on page 431 shows the IP Phone 2004 TN entry screens. — Figure 139 on page 431 displays the Node ID and Password. Note the Password entry input field is blank (underscores are not displayed). Therefore, the maximum length of the password is not disclosed. — If the correct password is entered, the TN is displayed. • Figure 140 on page 432 shows the IP Phone 2002 and IP Phone 2001 TN entry screens. — Figure 140 displays the Node ID. The Node ID is entered and the user presses OK. — Figure 140 displays the Password entry window. Note the Password entry input field is blank (underscores are not displayed). Therefore, the maximum length of the password is not disclosed. — If the correct password is entered, the TN is displayed. 553-3001-365 Standard 3.00 September 2004 IP Line 4.0 administration Page 431 of 770 Figure 139 IP Phone 2004 registration with password checking IP Line Description, Installation, and Operation Page 432 of 770 IP Line 4.0 administration Figure 140 IP Phone 2002 and IP Phone 2001 registration with password checking 553-3001-365 Standard 3.00 September 2004 IP Line 4.0 administration Page 433 of 770 IP Line CLI commands for password control The IP Phone Installer Passwords are configured on any Voice Gateway Media Card in the node. The IP Phone Installer Password is configured and administered using a set of six IPL> CLI commands: • nodePwdSet “password” • nodePwdShow • nodePwdTempPwdSet “temppwd”, uses,