Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 .
Document status: Standard Document version: 02.01 Document date: 21 December 2007 Copyright © 2007, Nortel Networks All Rights Reserved. Sourced in Canada LEGAL NOTICE While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are subject to change without notice.
Contents New in this Release Other changes 15 15 How to Get Help 17 Getting help from the Nortel web site 17 Getting help over the telephone from a Nortel Solutions Center 17 Getting help from a specialist by using an Express Routing Code 17 Getting help through a Nortel distributor or re-seller 18 Overview of IP Trunk 3.01 Contents 19 Introduction 19 Startup and registration 23 IP Trunk 3.01 (and later) and CS 1000S/CS 1000M Loss plans and pad values 27 Codec selection 27 IP Trunk 3.
Contents Description 46 Faceplate indicators, controls, and interfaces 47 Backplane interfaces 50 Assembly description 50 Media Card 32-port trunk card (NTVQ01BB) 51 Description 51 NTVQ01BB Hardware 52 Assembly description 53 Faceplate indicators and interfaces 53 Backplane interfaces 54 Installation guidelines 55 Software delivery 55 Replacing a CompactFlash PC Card (C:/ drive) 56 Software upgrade 59 Media Card application identification labels 60 Interoperability with earlier versions of ITG Trunk 60 Fa
Contents 5 IP Trunk 3.01 (and later) SNMP agent Codec profiles 84 G.711 84 G.729AB 85 G.729B 85 G.723.1 (5.3 kbit/s or 6.3 kbit/s) 85 Security passwords 86 Administrator level 86 Technical support level 86 83 ITG engineering guidelines 87 Contents 87 Introduction 89 Audience 90 Equipment requirements 90 Scope 92 Network engineering guidelines overview 92 IP Trunk 3.01 (and later) traffic engineering 95 Estimate voice traffic calculations 95 Calculate the number of IP Trunk 3.
Contents IP Trunk 3.01 (and later) DiffServ support for IP QoS 128 Queue management 129 Use of Frame Relay and ATM services 129 Internet Protocols and ports used by IP Trunk 3.01 (and later) 130 QoS fallback thresholds and IP Trunk 3.
Contents 7 Jitter buffer parameters (voice playout delay) 162 Silence Suppression parameters (Voice Activity Detection) 163 Fallback threshold 164 Setting the QoS threshold for fallback routing 164 Post-installation network measurements 164 Set ITG QoS objectives 165 Intranet QoS monitoring 166 SNMP network management 167 IP Trunk 3.01 (and later) network inventory and configuration 167 User feedback 168 TM 3.1 management and configuration of IP Trunk 3.
Contents Install filter and NTND26 cable (for MSDL and DCHIP cards in same Large System equipment row) 200 Install filter and NTND26 cable (for MSDL and DCHIP cards in different Large System equipment rows) 202 Small System cable installation 203 Install the serial cable 204 Cabling for the Media Card 32-port trunk card 205 ELAN and TLAN network interfaces 205 ITG Card ELAN/TLAN Adapter (L-adapter) 207 RS-232 maintenance port 211 NTMF29BA DCHIP cable 212 DCHIP cable routing, Large Systems 213 DCHIP Cable
Contents 9 Create the IP Trunk 3.01 (and later) node dialing plan using TM 3.1 253 Retrieve the IP Trunk 3.01 (and later) node dialing plan using TM 3.1 258 Transmit IP trunk card configuration data from TM 3.1 to the IP trunk cards 260 Before configuration data is transmitted 260 Configure the Leader 0 IP address 260 Backup Leader installation for IP Trunk 3.
Contents ITG Card Properties Configuration window 349 DSP maintenance window 349 D-channel maintenance 350 Transmit configuration data 350 Add an IP Trunk 3.01 (and later) node on TM 3.1 by retrieving an existing node 353 Retrieve and add an IP Trunk 3.01 (and later) node for administration purposes 353 Retrieve and add an IP Trunk 3.01 (and later) node for maintenance and diagnostic purposes 355 Configuration audit 356 Retrieve IP Trunk 3.01 (and later) configuration information from the IP Trunk 3.
Contents 11 Disable the indicated IP trunk card 386 Disable the indicated IP trunk card when idle Enable an indicated IP trunk card 386 Disable an indicated IP trunk card port 386 Enable an indicated IP trunk card port 387 Display IP trunk card ID information 387 Display IP trunk card status 387 Display IP trunk card port status 387 386 Maintenance Contents 389 Introduction 390 IP Trunk 3.
Contents Media Card 32-port trunk card faceplate maintenance display codes 423 ITG-Pentium 24-port trunk card faceplate maintenance display codes 425 System performance under heavy load 428 Message: PRI241 428 Message: MSDL0304 429 Message: BUG4005 429 Message: BUG085 430 Appendix A Patches and advisements Contents 431 Introduction 431 IP Trunk 3.00.53 patches 431 MPLR17662 431 MPLR17346 431 IP Trunk 3.01.22 patches 432 MPLR18142 432 MPLR18157 432 Interoperability with IP Trunk 3.
Contents 13 Appendix D Subnet mask conversion from CIDR to dotted decimal format 457 Appendix E CLI commands 459 Appendix F Configure a Netgear RM356 modem router for remote access 461 Contents 461 Introduction 461 Security features of the RM356 modem router 462 Install the RM356 modem router 462 Configure the TM 3.
Contents Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
New in this Release There have been no updates to the document in this release. Other changes Revision History December 2007 Standard 02.01. This document has been up-issued to support Communication Server Release 5.5. May 2007 Standard 01.01. This document is issued to support Communication Server 1000 Release 5.0. This document contains information previously contained in the following legacy document, now retired: (IP Trunk 553-3001-363). August 2005 Standard 3.00.
New in this Release Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
How to Get Help This chapter explains how to get help for Nortel products and services. Getting help from the Nortel web site The best way to get technical support for Nortel products is from the Nortel Technical Support web site: http://www.nortel.com/support This site provides quick access to software, documentation, bulletins, and tools to address issues with Nortel products.
How to Get Help http://www.nortel.com/erc Getting help through a Nortel distributor or re-seller If you purchased a service contract for your Nortel product from a distributor or authorized re-seller, contact the technical support staff for that distributor or re-seller. Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
Overview of IP Trunk 3.01 Contents This section contains information on the following topics: "Introduction" (page 19) "Startup and registration" (page 23) "IP Trunk 3.01 (and later) and CS 1000S/CS 1000M" (page 25) "Codec selection" (page 27) "IP Trunk 3.01 (and later) requirements" (page 27) "Package requirements" (page 27) "TM 3.1" (page 28) "Interoperability with the ITG 8-port trunk card" (page 28) Introduction The IP Trunk 3.
Overview of IP Trunk 3.01 In addition to routing IP Telephony calls with locally configured call-routing options, IP Trunk 3.01 takes advantage of the centralized IP Telephony call routing of an H.323 Gatekeeper residing on a Signaling Server elsewhere on the network. The H.323 Gatekeeper allows or denies access to IP network gateways. It also provides address analysis to find the destination gateway or device. A gateway is a device that translates circuit-switched signaling into H.
Introduction • 21 handles the call based on the return message from the Gatekeeper IP Trunk 3.01 (and later) accesses additional devices through the Gatekeeper. It is no longer necessary to individually provision the entire mesh at each IP Trunk 3.01 (and later) node. Instead, the calls go to the Gatekeeper, which provides the IP Trunk 3.01 (and later) application with the correct destination for the call. See Figure 1 "IP Trunk 3.01 (and later) architecture" (page 21). Figure 1 IP Trunk 3.
Overview of IP Trunk 3.01 WARNING The only Gatekeeper that IP Trunk 3.01 (and later) officially supports is the CS 1000M Gatekeeper. Gatekeeper calls made between the CS 1000M system and IP Trunk 3.01 (and later) are directly-routed calls. Directly-routed calls In directly-routed calls, the Gatekeeper returns the IP address of the call’s actual destination. Figure 2 "Directly-routed call" (page 22) on Figure 2 "Directly-routed call" (page 22) represents a directly-routed call.
Startup and registration 23 Figure 3 "Gatekeeper-routed call" (page 23) represents a Gatekeeper-routed call. The destination IP address provided by the Gatekeeper is the Gatekeeper’s IP address. All messages are routed through the Gatekeeper. Figure 3 Gatekeeper-routed call Startup and registration On system startup, the IP Trunk 3.01 (and later) Leader card is established, based on whether the primary and backup Leaders come up, in what sequence, and how quickly.
Overview of IP Trunk 3.01 The flag value is ignored when the provisioned Gatekeeper is a CS 1000M Gatekeeper. On startup, if the IP Trunk 3.01 (and later) Leader is provisioned to use a Gatekeeper, it seeks out and locates the Gatekeeper using RAS signalling and then registers with the Gatekeeper using an RRQ. As part of the registration process, the IP Trunk 3.01 (and later) Leader registers using the registration handling flag to determine how to proceed. The Gatekeeper and IP Trunk 3.
IP Trunk 3.01 (and later) and CS 1000S/CS 1000M 25 CS 1000M do not require a Gatekeeper Request from IP Trunk 3.01 (and later); therefore, no Request or Confirm is sent. 2. Gatekeeper Confirm (GCF) – From the Gatekeeper to the Active Leader, with the functional Gatekeeper IP address. This address is used for all call control messaging and registration messages between the IP Trunk 3.01 (and later) cards and the Gatekeeper. 3.
Overview of IP Trunk 3.01 H.323 RAS, IP Trunk 3.01 (and later) uses RAS Messaging to register with the Gatekeeper if provisioned to do so. IP Trunk 3.01 (and later) then processes calls by scanning its Directory Number (DN) information. If the call is not resolved using the local Address Translation Protocol Module (ATPM) and IP Trunk 3.01 (and later) is registered with a Gatekeeper, then IP Trunk 3.01 (and later) routes the call to the Gatekeeper. The IP Trunk 3.
IP Trunk 3.01 (and later) requirements 27 There are no direct media paths between the Meridian 1 telephones and the CS 1000M telephones. There are direct paths between the IP Trunk 3.01 (and later) IP trunk cards and the CS 1000M telephones. Loss plans and pad values When the IP Trunk card is in a CS 1000 system, it can take advantage of the Dynamic Loss Plan developed for the IP Peer product. This allows the system core to inform the IP Trunk card of the correct pad levels to be used.
Overview of IP Trunk 3.01 Table 1 IP Trunk 3.01 (and later) package requirements Package Name Package Number BARS Package description Comments 57 Basic Alternate Route Selection Package 57 and/or 58 is required. NARS 58 Network Alternate Route Selection Package 57 and/or 58 is required. CDP 59 Coordinated Dialing Plan Required if Dialing Plan used. If the configuration restricts NARS, use CDP to obtain private network dialing. CDP can also co-exist with NARS.
System description Contents This section contains information on the following topics: "IP Trunk 3.01 (and later) application" (page 31) "System requirements" (page 32) "Hardware components for IP Trunk 3.01 (and later)" (page 33) "Ordering rules and guidelines" (page 36) "Ordering rules for an IP Trunk 3.01 (and later) node" (page 36) "Ordering rules for IP Trunk 3.01 (and later) node expansion" (page 37) "Sparing ratios for IP Trunk 3.
System description "Software upgrade" (page 59) "Interoperability with earlier versions of ITG Trunk" (page 60) "Fax Tone Detection Configuration" (page 61) "ISDN Signaling Link" (page 61) "ISDN Signaling Link" (page 61) "Inter-card signaling paths" (page 64) "Dialing plans" (page 65) "Multi-node configuration" (page 65) "North American dialing plan" (page 66) "Flexible Numbering Plan" (page 67) "Electronic Switched Network (ESN5) network signaling" (page 67) "Echo cancellation" (page 67) "Speech Activi
IP Trunk 3.01 (and later) application 31 "G.723.1 (5.3 kbit/s or 6.3 kbit/s)" (page 85) "Security passwords" (page 86) "Administrator level" (page 86) "Technical support level" (page 86) IP Trunk 3.01 (and later) application IP Trunk 3.01 (and later) supports ISDN Signaling Link (ISL) IP trunks on the Media Card 32-port trunk card and the ITG-Pentium 24-port trunk card. The NTCW80 8-port trunk card cannot be upgraded to IP Trunk 3.01 (and later).
System description Figure 4 "IP Trunk 3.01 (and later) connectivity" (page 32) shows an IP Trunk 3.01 (and later) configuration example. Figure 4 IP Trunk 3.01 (and later) connectivity In this document, TLAN subnet refers to the Telephony LAN subnet that transmits the ITG voice and fax traffic. ELAN (Embedded LAN) subnet refers to the management and signaling LAN subnet for the system site. IP Trunk 3.
Hardware components for IP Trunk 3.01 (and later) 33 cards to support ISDN functionality. Earlier vintages are not supported, as the level of MCDN functionality required to support ITG-compatible ISL is not available on earlier vintages. Install a modem router on the ELAN subnet to provide remote support access for IP Trunk 3.01 (and later) and other IP-enabled Nortel products. The Nortel Netgear RM356 modem router integrates the functions of a V.
System description Table 3 Hardware components for the Media Card 32-port trunk Component The package includes the following: • NTVQ90 – Media Card 32-port trunk card • NTVQ83 ITG EMC Shielding Kit • NTAG81 PC Maintenance cable • NTAK19 Shielded 4-port SDI/DCH cable for NTAK02 card • NTND26 DCHI Interface cable for MSDL • NTCW84 Meridian 1 Backplane to 50-pin I/O Panel Mounting connector with IP Trunk-specific filtering • 50-pin I/O connector – A0852632 • NTVQ80 DCHIP kit for Media Card 32
Hardware components for IP Trunk 3.01 (and later) 35 Inspect the IPE module to determine if it is equipped with non-removable Molded Filter Connectors on the I/O Panel. For Large Systems manufactured during the period of 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 Molded Filter Connector.
System description Component Product codes IP Trunk 3.01 (and later) NTP CD-ROM – Multilingual NTVQ61BA PC Cards C7LIU DCH PC Card with Layer 2 DCH Software NTWE07AA Ordering rules and guidelines IP Trunk 3.01 (and later) can be ordered as a VoIP trunk gateway with 32 ports, or as a software upgrade on an existing VoIP trunk gateway on the Media Card 32-port trunk card or ITG-Pentium 24-port trunk card. One IP Trunk card in the system must be equipped with a D-Channel PC Card kit.
Ordering rules and guidelines 37 For SDI/DCH and DCHIP cards that reside in different Small System cabinets, order: • NTWE04AC Inter-cabinet cable (NTCW84KA to SDI/DCH cable-10 ft) If IP trunk cards are being installed in IPE modules equipped with NT8D81BA Backplane to I/O Panel ribbon cable assembly with Molded Filter Connectors, on a 100BaseTX TLAN subnet connection, order: • NT8D81AA Backplane to I/O Panel ribbon cable assembly compatible with NTCW84JA Filter Connector Block with ITG-specific filter
System description IP trunk card description The Media Card 32-port trunk card and ITG-Pentium 24-port trunk card provide a cost-effective solution for high-quality voice and fax transmission over an IP network. The IP Trunk cards are an IPE-based assembly designed for installation in a Meridian 1/CS 1000M IPE shelf. A Media Card 32-port trunk card occupies one slot and can have a maximum of 32 ports. The ITG-Pentium 24-port trunk card is a two-slot trunk card and can have a maximum of 24 ports.
IP trunk card description 39 NTVQ01BB Media Card 32-port trunk cards are factory-programmed with Release 8.0 firmware. Any firmware feature upgrades are available on the Nortel website. Download this firmware from the Customer Support Software page. Go to www.nortel.com. Follow the links to Customer Support and Software Distribution or go to www.nortel.
System description The Leader, Backup Leader, Follower, and DCHIP cards communicate through their ELAN network interfaces. For more information, see "Internet Protocols and ports used by IP Trunk 3.01 (and later)" (page 130). Follower A Follower card is a Media Card 32-port trunk card and/or an ITG-Pentium 24-port trunk card which converts telephone signals into data packets and data packets into telephone signals. For outgoing calls, Follower cards provide dialed number-to-IP address translation.
IP trunk card description 41 Backup Leader The Backup Leader card steps in when the Leader is out-of-service. This minimizes service interruptions. D-channel IP gateway The ITG-Pentium 24-port or Media Card 32-port trunk card with D-channel IP gateway (DCHIP) functionality (DCHIP card) is connected by the RS-422 cable to the Multi-purpose Serial Data Link (MSDL) card on the Meridian 1/CS 1000M Large Systems. It connects to the SDI/DCH Card on Small Systems. The DCHIP Card is equipped with a DCH PC Card.
System description (and later) D-channel only controls IP trunk cards in the same IP Trunk 3.01 (and later) node. TM 3.1 administration relates the cards with trunks to the DCHIP IP trunk card. The IP trunk card uses ISDN messages for call control and communicates with the Meridian 1/CS 1000M through the PC Card, using the RS-422 link. On the Meridian 1, the MSDL provides the ISL DCH interface. The DCHIP IP trunk card software performs the tandeming of DCH call control to the H.323 protocol.
IP trunk card description 43 Card combinations The Leader and DCHIP, or Follower and DCHIP, functions can reside on a single IP trunk card or multiple IP trunk cards. If a Follower card is equipped with a DCH PC card, it can function as a DCHIP trunk card. As an IP Trunk 3.01 (and later) node becomes larger with more trunk traffic, load balancing should be configured. When load balancing is required, the Leader and DCHIP functionality are placed on separate cards which are assigned the least call traffic.
System description Each customer requires one or more dedicated IP Trunk 3.01 (and later) nodes. Trunks on the same IP Trunk 3.01 (and later) node share the same dialing plan and IP network connectivity. IP Trunk 3.01 (and later) trunks cannot be shared between customers that have independent numbering plans and IP networks. It is possible to configure multiple IP Trunk 3.01 (and later) nodes for one customer.
IP trunk card description 45 Active Leader and Backup Leader interaction When a Leader card reboots into service, it sends bootp requests to check whether an Active Leader card is present. If it receives a bootp response, this indicates the presence of an Active Leader card and the rebooting Leader becomes the Backup Leader. If it does not receive a bootp response, this indicates the absence of an Active Leader and the rebooting Leader becomes the Active Leader.
System description When a DCHIP trunk card failure occurs, the associated trunks’ states appear busy to the Meridian 1/CS 1000M, so the trunks will not be used for calls. This blocks the normal software action of reverting to analog signaling when an ISL DCH fails. If either end’s DCHIP or DCH connection fails, ISDN protocol features across the IP network do not function. When a DCHIP card fails, its associated Followers are also removed from service.
ITG-Pentium 24-port trunk card (NT0961AA) 47 Figure 7 ITG-Pentium 24-port trunk card system connectivity and messaging Faceplate indicators, controls, and interfaces The NT0961AA ITG-Pentium 24-port trunk card has a double width faceplate using the shortened lock latches, as shown in Figure 8 "NT0961AA ITG-Pentium 24-port trunk card" (page 48). Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
System description Figure 8 NT0961AA ITG-Pentium 24-port trunk card Card Status LED A single red, card status LED on the faceplate indicates the enabled/disabled status of the 24 ports on the card. The LED is lit (red) during the power-up or reset sequence. The LED remains lit until the card correctly boots and assumes its role (that is, Leader, Backup Leader, Follower or DCHIP).
ITG-Pentium 24-port trunk card (NT0961AA) 49 During configuration, the error message "F:10" can appear. This error indicates a missing Security Device. It occurs because Security Devices are not implemented on ITG Trunk 2.0. Ignore this message. See "ITG-Pentium 24-port trunk card faceplate maintenance display codes" (page 425) for a complete list of faceplate codes.
System description RS-232 maintenance port The ITG-Pentium 24-port card has a DIN-8 (RS-232) maintenance port (DCE) connection on the faceplate and an alternative connection to the same serial port on the I/O backplane. Do not connect two maintenance terminals to both the faceplate and I/O panel serial maintenance port connections at the same time. Ethernet TLAN network interface The faceplate Ethernet TLAN network interface is a 9-pin, sub-miniature D-type connector.
Media Card 32-port trunk card (NTVQ01BB) 51 CAUTION Service Interruption The ITG-Pentium 24-port trunk card is not user-serviceable. Figure 9 "Mechanical assembly" (page 51) is for information purposes only. Do not remove the daughterboard from the motherboard. Figure 9 Mechanical assembly Media Card 32-port trunk card (NTVQ01BB) The NTVQ01BB Media Card 32-port trunk card provides a single slot implementation in an IPE shelf for Large and Small Systems. During the installation of the IP Trunk 3.
System description Figure 10 Media Card 32-port trunk card The base hardware (known as the Media Card) enhances cabling arrangements for installation and maintenance. NTVQ01BB Hardware NTVQ01BB Media Card 32-port trunk card is an improved version of NTVQ01BA Media Card 32-port trunk card. The main hardware enhancements in NTVQ01BB Media Card 32-port trunk card are: • The DSP daughter board has been removed and the DSP design is implemented on the motherboard.
Media Card 32-port trunk card (NTVQ01BB) 53 • The onboard FPGAs are changed to the advanced family of device architecture. • A new Compact Flash Drive is used for onboard C: Drive. • The faceplate has been re-designed for better ergonomics. • New firmware is developed to implement the above design enhancements. Table 7 "Media Card 32-port trunk card comparison" (page 53) provides a comparison of the design features for the two versions of the Media Card 32-port trunk card.
System description PC Card slot This slot (designated as Slot A:) accepts a Type I or II PC Card. It also supports a DCHIP interface PC Card (D-Chip) to the system through the NTMF29Bx cable. Ethernet activity LEDs The LEDs indicate 100BaseT, 10BaseT, and activity on both the ELAN and TLAN network interfaces. Maintenance display The maintenance display is a 4-character LED-based dot-matrix display.
Software delivery 55 Installation guidelines Use the following guidelines when installing the Media Card 32-port trunk card: • Ensure CS 1000 Release 4.0 or later software is installed and running. • Ensure that the NTVQ01BB Media Card Firmware is version 8.0 (or later) • Order the Alarm and Notification application package separately. • For all MCDN features, the SDI/DCH NTAK02 card (Small Systems) or the MSDL NT6D80 card (Large Systems) is required. These cards must be ordered for each system.
System description The Media Card 32-port trunk card package is shipped with the following two major components, as well as other items: • Media Card 32-Port Assembly (NTVQ01BB) • CompactFlash card (NTM405AB) ATTENTION IMPORTANT! The CompactFlash card must be installed on the Media Card before installing the Media Card assembly in the IPE shelf.
Replacing a CompactFlash PC Card (C:/ drive) 57 WARNING Be sure to remove the Media Card 32-port trunk card from the system before replacing the CFlash ATA card. Procedure 1 Removing the CFlash card on NTVQ01BB Step Action 1 Gently pull the clip from its latched position. See Figure 11 "CFlash card with clip latched" (page 57). Figure 11 CFlash card with clip latched 2 Move the clip up. The CFlash card can now be removed from the drive.
System description 2 The metal clip should be pulled up and the new CFlash card should be kept in the right position (see Figure 13 "CFlash card with metal clip up" (page 58)). 3 Ensure that force is applied equally at both ends of the CFlash card before pushing it in (see Figure 13 "CFlash card with metal clip up" (page 58)). Figure 13 CFlash card with metal clip up 4 Gently insert the CFlash, so that the flash is fully in contact with the connectors on the drive.
Software upgrade 59 Software upgrade IP Trunk 3.01 (and later) software upgrades can be performed in three ways: • by FTP from TM 3.1 • by FTP from the CLI • from a PC Card The application (exec) file for the Media Card 32-port trunk card contains a different CPU type definition from other IP trunk card types.
System description "Transmit card properties and dialing plan" (page 419) or in "Transfer files through the Command Line Interface" (page 377). —End— Media Card application identification labels Media Card application identification labels (see Figure 15 "Media Card identification labels" (page 60)) are provided with every Media Card 32-port trunk card package. Affix the appropriate label to the Media Card’s faceplate (see Figure 16 "Labeled Media Card" (page 60)).
ISDN Signaling Link 61 If an upgrade from ITG Trunk 2.xx, Release 19 or earlier, is projected to take several days and fax support is needed during this time, first upgrade the individual nodes to ITG Trunk 2.xx Release 23. When the network is upgraded to ITG Trunk 2.xx Release 23, upgrade again to the latest software release. The interim upgrade step is only required if fax support is needed during the upgrade process. When the Media Card 32-port trunk cards are upgraded to or installed with IP Trunk 3.
System description Figure 17 ITG configuration ISDN signaling between the Meridian 1 and IP Trunk 3.01 (and later) supports the delivery of Calling Line Identification (CLID) and feature messaging. ISL DCH signaling provides the necessary signaling connection over which data, including CLID and feature-specific messaging, can be passed.
ISDN Signaling Link 63 because the NTAK02BB SDI/DCH card does not support QSIG protocols for ISL. The DCH interface uses these protocols and their variants, as they have the following advantages: • ISL configuration support • symmetry (incoming and outgoing call messaging is the same) • near H.323 standard QSIG GF Name Display is the only supported QSIG supplementary service. The ITG feature complies with H.323 Basic Call Q.931 signaling. This part of the H.323 standard (H.
System description For further information on ISDN Signaling Link (ISL), refer to System Management Reference (NN43001-600), ISDN Primary Rate Interface Installation and Commissioning (NN43001-301), and ISDN Primary Rate Interface Maintenance (NN43001-717). Inter-card signaling paths The Leader, DCHIP, and Follower cards communicate using their ELAN network interface IP addresses. Figure 19 "IP Trunk 3.
Dialing plans 65 Dialing plans Dialing plan configuration allows customers to set up routing tables to route calls to the appropriate destination, based on dialed digits. The dialing plan is configured through the Electronic Switched Network (ESN) feature, using TM 3.1 or overlays in the system. With ESN configuration, the system can route outgoing calls to the IP trunk card.
System description For example, Meridian 1/CS 1000M switch B node B1 has two entries for NPA 408 and 4085, which point to nodes A1 and A2 of Meridian 1/CS 1000M switch A, respectively. Calls from B1 with dialed digits 408-5xx-xxxx are routed to the IP Trunk 3.01 (and later) node A1 while all other 408-xxx-xxxx calls are routed to IP Trunk 3.01 (and later) node A2. North American dialing plan The North American dialing plan is used to make public network calls through the private IP network.
Dialing plans 67 Flexible Numbering Plan A Flexible Numbering Plan (FNP) allows the length of Location Codes (LOCs) to vary from node to node. As well, the total number of digits dialed to reach a station can vary from station to station. It also allows flexibility for the length of the location codes from node to node. An FNP can be used to support country-specific dialing plans. FNP also allows users to dial numbers of varying lengths to terminate at a destination.
System description default in TM 3.1 remained unchanged at 32 ms, even though the ECAN performance was significantly better with 128 ms. This problem has been resolved in TM 3.1, but ITG Trunk and IP Trunk nodes defined by customers with the original TM 3.1 software still use the incorrect default value. Recent releases of TM 3.1 that are properly configured, with all applicable patches and the fix integrated, have the default for new systems set to 128 ms.
Dialing plans Provisioned in TM 3.1 (in ms) Value used by IP Trunk 3.01 96 96 128 (default value in IP Trunk 3.01) 128 (default value in IP Trunk 3.01) 69 Speech Activity Detection Speech activity detection reduces the IP bandwidth used by typical voice conversations. When Speech Activity Detection is enabled, no voice samples are sent during periods of silence (from one side of the conversation or the other).
System description Callers can access traditional Voice Mail or IVR services (for example, "Press 1 for more information" or "Press 2 to be connected to our customer service department"). Services that depend on long DTMF bursts cannot be accessed. In order to ensure that DTMF tones are being transmitted properly, the DSP must be configured correctly in TM 3.1. If the IP Trunk 3.01 (and later) node is configured to use a voice codec other than G.
Quality of Service • latency • queuing delay in the intermediate nodes • packet loss • available bandwidth 71 The Type of Service (ToS) bits in the IP packet header can affect how efficiently data is routed through the network. For further information on ToS, see "Type of Service" (page 76). Packet jitter related to latency affects the quality of real-time IP transmissions.
System description than five percent, can be acceptable without too much degradation in voice quality. Sporadic loss of small packets can be more acceptable than infrequent loss of large packets. Packet delay Packet delay is the time between when a packet is sent and when it is received. The total packet delay time consists of fixed and variable delay. Variable delay is more manageable than fixed delay, as fixed delay is dependent on network technology.
Quality of Service 73 Packet InterNet Groper (PING) Packet InterNet Groper (PING) sends an Internet Control Message Protocol (ICMP) echo request message to a host, expecting an ICMP echo reply. This allows the measurement of the round-trip time to a selected host. By sending repeated ICMP echo request messages, the percentage of packet loss for a route can be measured. Traceroute Traceroute uses the IP Time-To-Live (TTL) field to forward router hops to a specific IP address.
System description MOS values are calculated based on the routing delay and frame duration and jitter buffer delay on the codec. These latencies must be taken into consideration during the engineering of the total network’s latency. If the end-to-end latency of the network is specified and the latency of the PSTN circuit-switched components is removed, the remainder is the latency available for the IP trunks. This latency value plays a large role when configuring IP Trunk 3.
Fallback to alternate facilities 75 The trigger for fallback to alternate trunk facilities is defined per call, per customer. The local Active Leader makes the decision to use the fallback feature. The selection of routes is based on the customer-configured database. The customer must configure the alternate routing to the PSTN in the Meridian 1/CS 1000M database. The fallback to alternate facilities uses an ISDN DCH mechanism.
System description Fallback in IP Trunk 3.01 (and later) In QoS monitoring, the local node queries the remote node and gets a response; the remote node queries the local node and gets a response. If the remote node cannot query the local node, QoS monitoring is not available. When an IP Trunk 3.01 (and later) node uses a Gatekeeper to resolve an address, IP Trunk 3.01 (and later) cannot monitor QoS and provide fallback. This function resides with the device resolving the address.
Type of Service 77 The TM 3.1 User Interface allows two ToS values to be configured: data and control. Data packets transmit the voice or fax call’s data, while control packets setup and maintain the call. Both can be configured for any value in the range of 0 – 255 (0 is the default). When an IP Trunk 3.01 (and later) node is configured, ToS bits are initially set to default values. The TM 3.1 IP Trunk 3.
System description The IP trunk card configures two route table entries for the local subnet if a different ToS is configured for the voice and control packets. Otherwise, a single entry is created. CAUTION Service Interruption Only technical personnel with detailed knowledge of router capabilities should make changes to ToS. Improper changes to ToS can degrade network performance. Fax support The IP trunk card transfers T.30 protocol (G3 Fax) implementations over the IP network.
Remote Access 79 Modules supporting facsimile transmission are responsible for the following: • fax speed detection and adjustment • protocol conversion from G3 Fax to RTP payload for fax data transfer • T.30 fax protocol support • T.38 fax-over-IP protocol • V.21 channel 2 binary signaling modulation and demodulation • High-level Data Link Control (HDLC) framing • V.27 term (2400/4800 bps) high speed data modulation and demodulation • V.
System description Alternatively, the PC application, pcANYWHERE©, can be installed in host mode on the TM 3.1 PC to provide remote access to any PC with a modem. The remote user dials the TM 3.1 PC which contains the required IP Trunk 3.01 (and later) data (whether stored locally or on an TM 3.1 server). Once connected, the remote user can perform any operation available to that PC. Remote Access Remote Access is supported on the MMCS IP Gateway.
Per-call statistics support using RADIUS Client 81 A RADIUS client on the IP trunk card allows per-call statistics of the IP network call to be sent from the cards to a network listener. The client is based on RFC2139, which defines the accounting portion of the RADIUS protocol. The IP trunk card uses the authentication algorithm based on RFC1321. Configuration Use TM 3.
System description • Codec used • Orig/Term call side indication • Snapshot of remote Gateway’s QoS at time of call connect The calling and called numbers (with their corresponding IP addresses) are just that, regardless of which end is doing the originating. So the Follower card on the originating side generates a RADIUS record with its own IP address as the originating IP address.
SNMP MIB 83 SNMP MIB SNMP is the protocol used to communicate TM 3.1 IP Trunk 3.01 (and later) alarms or events. Support for the SNMP Management Information Bases (MIB) on the IP trunk card is composed of two parts: the standard MIB-2 and extensions for the IP trunk card. MIB-2 support Support of MIB-2 is enabled by the use of the WindRiver SNMP agent, WindNet©.
System description — release — establish • Retrieval of DSP information, such as: — DSP firmware — DSP self-test status — card reset • SNMP configuration (that is, community names and trap subscription) — alarm generation through SNMP traps • File transfer, including configuration files, software upgrade, dialing plan files, bootp files, activity log, and call trace files Codec profiles Codec refers to the voice coding and compression algorithm used by the DSPs on the IP trunk card. The G.
Codec profiles 85 G.729AB The G.729AB codec is the default preferred codec when adding a new IP Trunk 3.01 (and later) node in TM 3.1. This codec provides near toll-quality voice at a low delay. The G.729AB codec uses compression at 8 kbit/s (8:1 compression rate). Optional B Voice Activity Detection/Silence Suppression is configurable through TM 3.1. An ITG-Pentium 24-port trunk card supports 24 channels per card with G.729AB. A Media Card 32-port trunk card supports 32 channels per card with G.729AB.
System description WARNING The Media Card 32-port trunk card does not support Profile 3. Security passwords When Telneting into the ELAN network interface or using the debug port, a password must be entered when prompted. Two levels of passwords are used to prevent unauthorized data access. Unauthorized data access occurs when an unauthorized individual is able to view or modify confidential data, such as employee lists, password lists, and electronic mail.
ITG engineering guidelines Contents This section contains information on the following topics: "Introduction" (page 89) "Audience" (page 90) "Equipment requirements" (page 90) "Scope" (page 92) "Network engineering guidelines overview" (page 92) "IP Trunk 3.01 (and later) traffic engineering" (page 95) "Estimate voice traffic calculations" (page 95) "Calculate the number of IP Trunk 3.
ITG engineering guidelines "TCP traffic behavior" (page 127) "IP Trunk 3.01 (and later) DiffServ support for IP QoS" (page 128) "Queue management" (page 129) "Use of Frame Relay and ATM services" (page 129) "Internet Protocols and ports used by IP Trunk 3.01 (and later)" (page 130) "QoS fallback thresholds and IP Trunk 3.
Introduction 89 "Multiple IP Trunk 3.01 (and later) nodes on the same ELAN and TLAN segments" (page 157) "General LAN considerations" (page 157) "ELAN and TLAN network interface half- or full-duplex operation" (page 157) "TLAN subnet design" (page 158) "Configure the TLAN subnet IP router" (page 158) "Setting up the ELAN subnet" (page 159) "How to avoid system interruption" (page 159) "IP Trunk 3.
ITG engineering guidelines IP Trunk 3.01 (and later) is targeted towards the Enterprise customer who has a Meridian 1/CS 1000M system installed for providing corporate voice services and an intranet for corporate data services. A customer is expected to use the IP Trunk 3.01 system to move traffic from a PSTN-based network to the intranet.
Introduction 91 system must be determined. If the intranet becomes overloaded, new calls to the IP Trunk 3.01 (and later) system fall back to normal circuit-switched voice facilities so that the Quality of Service (QoS) does not degrade for new calls. IP Trunk 3.01 (and later) is for intranet use only. IP Trunk 3.01 (and later) provides virtual analog ISL TIE trunks between two Meridian 1 systems in an ESN network, as shown in Figure 23 "The IP Trunk 3.01 (and later) intranet" (page 91). IP Trunk 3.
ITG engineering guidelines A maximum of 16 Media Card 32-port trunk cards can fit on one IPE shelf. Each IP trunk card takes up one slot on the IPE shelf. For Class B compliance to EMC regulations, only 10 Media Card 32-port trunk cards can be placed on an IPE shelf. For Class A compliance, there are no limitations on the Media Card 32-port trunk card. For more information, see Appendix "Environmental and electrical regulatory data" (page 451).
Network engineering guidelines overview 93 voice into fixed-length IP packets, provide ISDN signalling, and translate PSTN numbers into IP addresses. The IP packets are transported across the IP data network with a low latency that varies with strict limits. The term "voice services" also includes fax services. IP evolved from a protocol that allowed multi-vendor hosts to communicate.
ITG engineering guidelines Figure 24 IP Trunk 3.01 (and later) network engineering process Three preliminary steps must be undertaken. 1. Calculate IP Trunk 3.01 (and later) traffic. Estimate the amount of traffic that the system will route through the IP Trunk 3.01 (and later) network. This total must include the estimated traffic between the IP trunk cards and the Signaling Server. This in turn places a traffic load Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.
IP Trunk 3.01 (and later) traffic engineering 95 on the corporate intranet. This is described in "IP Trunk 3.01 (and later) traffic engineering" (page 95). 2. Assess WAN link resources. If resources in the corporate intranet are not sufficient to adequately support voice services, the cause is usually insufficient WAN resources. "Assess WAN link resources" (page 121) outlines how this assessment can be made. 3. Measure the existing intranet’s Quality of Service (QoS).
ITG engineering guidelines CCS/user=# of calls/ * Average Holding Time (in seconds)/100 Total voice CCS (Tv) = CCS/user x No. of VoIP users The number of VoIP users (telephones) is the potential population in the system that can generate/receive traffic through the IP Trunk 3.01 (and later) node. This number may be estimated for a new Meridian 1 customer.
IP Trunk 3.01 (and later) traffic engineering 5 97 Calculate bandwidth output. Refer to Table 17 "Silence Suppression disabled TLAN Ethernet and WAN IP bandwidth usage per IP Trunk 3.01 (and later) " (page 113) (Silence Suppression disabled). Tv/36 and Tx/36 indicate the average number of simultaneous callers. This calculation requires perfectly queued and perfectly smooth traffic.
ITG engineering guidelines Procedure 5 Calculating IP Trunk 3.01 (and later) port and bandwidth requirements Step Action 1 Calculate VoIP traffic during busy hour. CCS/user = 4*150/100 = 6 CCS Tv = 120*6 = 720 CCS 2 Calculate fax on IP traffic during busy hour. CCS/fax sent = 3*48/100 = 1.44 CCS CCS/fax received = 5*48/100 = 2.4 CCS Total fax CCS (Tx + Rx) = 1.44*25 + 2.4*20 = 36+ 48= 84 CCS 3 Calculate IP Trunk 3.01 (and later) traffic during busy hour.
IP Trunk 3.01 (and later) traffic engineering 99 This example is based on the G.729AB codec with 30 ms payload size and Silence Suppression enabled. For relations of user-selectable parameters such as payload size, codec type, packet size and QoS, refer to "Set QoS expectations" (page 139). Calculate the number of IP Trunk 3.01 (and later) ports required IP Trunk 3.
ITG engineering guidelines Trunks CCS Trunks CCS Trunks CCS Trunks CCS Trunks CCS 18 346 38 905 58 1504 78 2122 98 2752 19 373 39 935 59 1534 79 2153 99 2784 20 399 40 964 60 1565 80 2184 100 2816 101 2847 111 3166 121 3488 131 3810 141 4134 102 2879 112 3198 122 3520 132 3843 142 4167 103 2910 113 3230 123 3552 133 3875 143 4199 104 2942 114 3262 124 3594 134 3907 144 4231 105 2974 115 3294 125 3616 135 3939 145 4
IP Trunk 3.
ITG engineering guidelines supporting the other half of the Followers. This rule covers D-Channel redundancy with two IP Trunk 3.01 (and later) routes per node. 3. Leader 0 with DCHIP but no voice ports configured supporting Leader 1 and all Followers. This rule covers very large nodes and networks with multiple IP Trunk 3.01 (and later) routes per node. 4. Leader 0 with DCHIP and all voice ports configured supporting Leader 1 and all Followers.
IP Trunk 3.01 (and later) traffic engineering 103 (and later) TLAN subnet. IP Trunk 3.01 (and later) registers and re-registers with a Gatekeeper. Unless the Time To Live (TTL) value is extremely low (under 15 seconds), the TTL has a very minor effect on the Leader card. Single card role The role of the IP trunk card in a single card node should not be impacted by real-time limitations. The only consideration that limits the capacity of a single Card node is the number of QoS endpoints being monitored.
ITG engineering guidelines Factors that effect the real-time capacity The following factors affect real-time capacity: • host module type • the number of ports configured on the Leader card, codec selection, and voice sample size • size of the IP Trunk 3.
Factors that effect the real-time capacity 105 In a default QoS configuration, the Leader card must terminate and generate a total of 50 probe packets per QoS-enabled ITG Trunk 2.x/IP Trunk 3.01 (and later) node every 15 seconds. These extra packets generated and received use real-time capabilities that would otherwise be used for call processing. If the number of nodes in a network that is being monitored exceeds the capabilities of the Leader card, implement other VoIP QoS methods.
ITG engineering guidelines In this section, the following assumptions are made to project the Leader Card real-time capacity: • The number of probe packets per Leader Card is 25. • If the average hold time is 180 seconds, the number of calls per hour per port is 15.3 calls. • If the average hold time is 10 seconds, the number of calls per hour per port is 187.5 calls. • 50% of the calls are incoming and 50% are outgoing.
Factors that effect the real-time capacity 107 Nortel recommends that traffic on a single card ITG-Pentium 24-port trunk card node never exceed the following: • 5000 calls/hour – Gatekeeper-routed • 6000 calls/hour – non-Gatekeeper-routed In a multi-card node, the various roles necessary in processing calls, such as Leader card, DCHIP card, and Follower card, can be divided over multiple cards. This ensures that no IP trunk card exceeds its real-time capacity.
ITG engineering guidelines Table 12 Real-time capacity of a single card node with all 24 ports enabled Calls/hr CCS AHT Maximum number of nodes monitoring QoS 490 882 180s 96 1500 900 60 46 3000 900 30 30 6000 600 10 0 Comment Normal traffic Maximum capacity of card Table 13 Real-time capacity of an ITG-Pentium 24-port trunk card in the Leader or DCHIP role Number of QoS nodes in network 1 Calls/hr supported Voice ports enabled on Leader card At 1% blocking with x seconds of Av
Factors that effect the real-time capacity 109 Service) divided by the number of channels per card. The number of Follower cards required is affected by whether the Leader card has the voice channels enabled or not. 2. Peakedness factor for call processing is equal to 1.3. This implies that 30% fluctuation is allowed in voice traffic. 3. Calls can terminate or originate on the Leader card. Voice ports are allowed on the Leader card, depending on configuration for anticipated traffic.
ITG engineering guidelines A node has only one Leader card; however, more then one DCHIP card can be provisioned. If a DCHIP card fails, all IP trunk cards with channels that use that D-channel are out of service; the remaining IP trunk card channels, though, do remain in service. This configuration provides some redundancy and less work for each DCHIP card.
Factors that effect the real-time capacity 111 Table 15 Real-time capacity of a Media Card 32-port trunk card in the Leader role Number of QoS nodes in network Calls/hr supporte d Voice ports enabled on Leader card At 1% blocking with x seconds of Average Hold Time (AHT), the minimum number of Media Card 32-port trunk card Follower cards required at: AHT=10s AHT=30s AHT=60s AHT=120 s AHT=180 s 100 2615 32 1 2 2 4 5 50 3574 32 1 2 3 5 7 0 6000 32 1 3 4 8 11 100 3045 0 1
ITG engineering guidelines To calculate the bandwidth requirement of a route, divide the total route traffic by 36 CCS and multiply by the bandwidth use. All traffic data must be based on the busy hour of the busy day. To calculate resource requirements (IP Trunk 3.01 (and later) ports and TLAN subnet/WAN bandwidth), traffic parcels are summarized in different ways: 1. Add all sources of traffic for the IP Trunk 3.
Factors that effect the real-time capacity 113 Table 17 Silence Suppression disabled TLAN Ethernet and WAN IP bandwidth usage per IP Trunk 3.01 (and later) port IP header size (bytes) Ethern et header size (bytes) Full-du plex Ethern et Bandw idth (bps) PPP WAN Bandw idth (bps) See Note 9.
ITG engineering guidelines Silence Suppression engineering considerations Silence Suppression/Voice Activity Detection (VAD) results in average bandwidth savings over time, not in instantaneous bandwidth savings. For normal conversations, Silence Suppression creates a 40% savings in average bandwidth used. For example, a single G.729AB voice packet will still consume 30 Kbps of bandwidth but the average bandwidth used for the entire call would be approximately 23 Kbps.
Factors that effect the real-time capacity 115 Fax traffic is always one-way. Fax pages sent and fax pages received generate data traffic to the TLAN subnet. For WAN calculation, only the larger traffic parcel of the two must be considered. Trunk Anti-Tromboning (TAT) and Trunk Route Optimization (TRO) considerations Trunk Anti-Tromboning (TAT) was designed to remove tromboning trunks after a call was answered by a third party. Anti-Tromboning can occur in the following scenarios.
ITG engineering guidelines the two tromboned IP Trunks. There are three cases of direct media path connection between two tromboned IP Trunks (trunk channels) when interoperating with BCM and IP Peer: • Both IP Trunks are on the same Media Card 32-port trunk card running IP Trunk 3.01 (and later). The circuit-switched path between the tromboned trunks is connected by the time switch on the Media Card 32-port trunk card.
Factors that effect the real-time capacity 117 TAT call Scenario The following call scenario helps to understand TAT. 1. Site 1 and Site 2 both have an IP Trunk 3.01 (or later) node installed. IP Trunk 3.01 (and later) is used for trunking between the two sites. 2. Telephone A at Site 1 calls Telephone B at Site 2. Telephone B answers the call and decides to transfer the call to Phone C which is located at Site A. 3. Telephone C answers the call transferred from Telephone B at Site 2. 4.
ITG engineering guidelines TAT versus TRO Nortel recommends that both Trunk Route Optimization (TRO) and TAT be implemented with IP Trunk 3.01 (and later) nodes. TRO functions in a different manner than TAT. TRO is invoked before the call has been answered. TAT is invoked once the call has been answered. To reduce the number of trunks being used due to call redirection by CFNA, Hunt, or Forward all Calls, configure TRO in the RDB. TRO must be enabled at all sites.
Factors that effect the real-time capacity 119 Table 18 "Example: Traffic flow in a 4-node IP Trunk 3.01 (and later) network" (page 119) summarizes traffic flow of a 4-node IP Trunk 3.01 (and later) network. Table 18 Example: Traffic flow in a 4-node IP Trunk 3.01 (and later) network Destination Pair Traffic in CCS Santa Clara/Richardson 60 Santa Clara/Ottawa 45 Santa Clara/Tokyo 15 Richardson/Ottawa 35 Richardson/Tokyo 20 Ottawa/Tokyo 18 The codec selection is on a per-IP trunk card basis.
ITG engineering guidelines Table 20 "Example: Incremental WAN bandwidth requirement" (page 120) summarizes the WAN traffic in kbit/s for each route. The recommended incremental bandwidth requirement is included in the column adjusted for 30% traffic peaking in busy hour. This assumes no correlation and no synchronization of voice bursts in different simultaneous calls. This assumes some statistical model of granularity and distribution of voice message bursts due to Silence Suppression.
Assess WAN link resources 121 where 14 CCS is the larger of two fax traffic parcels (14 CCS as compared to 6 CCS). After adjusting for peaking, the incremental data rate on WAN for this route is 33.2 kbit/s. Compare this number with 24.3 kbit/s when all 60 CCS is voice traffic, it appears that the reduction in CCS due to one-way fax traffic (20 CCS as compared to 14 CCS) will not compensate for higher bandwidth requirement of a fax as compared to a voice call (33.7 kbit/s as compared to 11.
ITG engineering guidelines The third step is to assess how much spare capacity is available. Enterprise intranets are subject to capacity planning policies that ensure capacity use remains below some determined utilization level. For example, a planning policy might state that the utilization of a 56 kbit/s link during the peak hour must not exceed 50%; for a T1 link, the threshold is higher, for instance, 80%. The carrying capacity of the 56 kbit/s link would be 28 kbit/s and for the T1, 1.
Assess WAN link resources 123 Figure 25 Calculate network load with IP Trunk 3.01 (and later) traffic Suppose the intranet has a topology as shown in Figure 25 "Calculate network load with IP Trunk 3.01 (and later) traffic" (page 123) and a prediction on the amount of traffic on a specific link, R4-R5, is required. From the ""IP Trunk 3.
ITG engineering guidelines r6 (10.8.0.1) 1 ms 1 ms 1 ms r5 (10.18.0.2) 42 ms 44 ms 38 ms r4 (10.28.0.3) 78 ms 70 ms 81 ms r1 (10.3.0.1) 92 ms 90 ms 101 ms santa_clara_itg4 (10.3.2.7) 94 ms 97 ms 95 ms The Traceroute program can be used to check if routing in the intranet is symmetric for each source-destination pair.
Assess WAN link resources 125 Enough capacity For each link, Table 23 "Computation of link capacity as compared to ITG load" (page 125) compares the available link capacity to the additional IP Trunk 3.01 (and later) load. For example, on link R4-R5, there is plenty of available capacity (492 kbit/s) to accommodate the additional 24 kbit/s of IP Trunk 3.01 (and later) traffic.
ITG engineering guidelines Insufficient link capacity If there is not enough link capacity, implement one or more of the following options: • Use the G.723 codec series. Compared to the default G.729AB codec with 30 ms payload, the G.723 codecs use 9% to 14% less bandwidth. • Upgrade the link’s bandwidth. Other intranet resource considerations Bottlenecks caused by non-WAN resources are less frequent. For a more complete assessment, consider the impact of incremental IP Trunk 3.
Implement QoS in IP networks 127 Unless voice traffic has been configured to have higher priority, the data file download could use most of the available bandwidth. This would cause voice packet loss and therefore poor voice quality. Recommendation Nortel strongly recommends implementing suitable QoS mechanisms on any IP network carrying VoIP. This section outlines what QoS mechanisms can work in conjunction with the IP Trunk 3.
ITG engineering guidelines and ebb in traffic flows. WAN links appear to be congested at one period of time time and then are followed by a period of under-utilization. There are two consequences, as follows: • WAN link inefficiency • IP Trunk 3.01 (and later) traffic streams are unfairly affected IP Trunk 3.01 (and later) DiffServ support for IP QoS If the intranet provides differentiated services based on the DiffServ/TOS field, then the IP Trunk 3.
Implement QoS in IP networks 129 Queue management Queueing delay From "Queuing delay" (page 133), it can be seen that queueing delay is a major contributor to delay, especially on highly-utilized and low-bandwidth WAN links. Routers that are TOS-aware and support class-based queuing can help reduce queueing delay of voice packets when these packets are treated with preference over other packets.
ITG engineering guidelines Internet Protocols and ports used by IP Trunk 3.01 (and later) The following IP applications and protocols are used by IP Trunk 3.01 (and later) and must be transmitted across the customer’s intranet by all IP routers and other network equipment. This information should be validated and included in the IP Trunk 3.01 (and later) network engineering guidelines. Customers using firewalls must be aware of all UDP and TCP ports being used by IP Trunk 3.
Implement QoS in IP networks 131 Port numbers used by IP Trunk 3.01 (and later) Table 25 "Pre-defined TCP ports" (page 131) and Table 26 "Pre-defined UDP ports" (page 131) list the pre-defined ports used by IP Trunk 3.01 (and later). Table 25 Pre-defined TCP ports Network interface Port use Port number ELAN DCHIP inter-card messaging 6001 TLAN H.
ITG engineering guidelines • limiting the maximum frame size and fragmenting large frames on low-speed WAN links • limiting the quantity of voice traffic that is transmitted over low-speed WAN links Fine-tune network QoS Topics presented in this section deal with issues that impact the QoS of IP Trunk 3.01 traffic. They help to understand how to fine-tune a network to improve its QoS, but are not directly involved as a part of network engineering procedure.
Implement QoS in IP networks 133 Serialization delay Serialization delay is the time it takes to transmit the voice packet one bit at a time over a WAN link. The serialization delay depends on the voice packet size and the link bandwidth, and is calculated using the following formula: Serialization delay in ms = 8 * (IP packet size in bytes)/(link bandwidth in kbit/s) Table 27 "Serialization delay" (page 133) shows what the serialization delay for voice packets on a 64 kbit/s and 128 kbit/s link.
ITG engineering guidelines Figure 26 Queuing delay of various links As can be seen in Figure 26 "Queuing delay of various links" (page 134), queueing delays can be significant for links with bandwidth under 512 kbit/s. Higher speed links can tolerate much higher utilization levels. Routing and hop count Each site pair takes different routes over the intranet. The route taken determines the number and type of delay components that add to end-to-end delay.
Implement QoS in IP networks 135 Other delay components Other delay components, generally considered minor, are as follows. • Router processing delay The time it takes to forward a packet from one link to another on the router is the transit or router processing delay. In a healthy network, router processing delay is a few milliseconds. • LAN segment delay The transmission and processing delay of packets through a healthy LAN subnet is just one or two milliseconds.
ITG engineering guidelines The average rtt time on that link is about 40 ms; the one-way link delay is about 20 ms, of which the circuit transmission and serialization delay are just a few milliseconds. Most of this link’s delay is caused by queueing. Looking at Figure 26 "Queuing delay of various links" (page 134), if this link is upgraded to T1, approximately 19 ms is shaved off the delay budget.
Implement QoS in IP networks 137 • Overloaded CPU. This is another commonly-monitored statistic collected by network management systems. If a router is overloaded, it means that the router is constantly performing processing-intensive tasks, which impedes the router from forwarding packets. Determine what the threshold CPU utilization level is and check if any suspect router conforms to the threshold. The router might have to be re-configured or upgraded. • Saturation.
ITG engineering guidelines Time-of-Day voice routing Other important objectives associated with IP Trunk 3.01 (and later) network translations and route list blocks are as follows: 1. Make IP Trunk 3.01 (and later) the first-choice, least-cost entry in the Route List Block. 2. Use Time-of-Day (ToD) scheduling to block voice traffic to the IP Trunk 3.01 (and later) route during peak traffic periods on the IP data network when degraded QoS causes all destination IP Trunk 3.
Measure intranet QoS 139 Use the ESN TGAR, NCOS, and facility restriction levels to keep general modem traffic off the IP Trunk 3.01 (and later) route. Measure intranet QoS End-to-end delay and error characteristics of the current state of the intranet can be measured. These measurements help set acceptable QoS standards when using the corporate intranet to transmit voice services. QoS evaluation process overview There are two main objectives when dealing with the QoS issue in an IP Trunk 3.
ITG engineering guidelines In the context of a Meridian 1/CS 1000M system with IP Trunk 3.01 (and later), Figure 27 "Relationship between users and services" (page 140) shows the relationship between users and services. Figure 27 Relationship between users and services From the diagram, it can be seen that there are two interfaces to consider: • The Meridian 1/CS 1000M system, including the IP Trunk 3.
Measure intranet QoS 141 The QoS level is a user-oriented QoS metric which takes on one of these four settings: excellent, good, fair, and poor, indicating the quality of voice service. IP Trunk 3.01 (and later) periodically calculates the prevailing QoS level per site pair, based on its measurement of the following: • one-way delay • packet loss • Codec When the QoS level is below the fallback threshold, any new calls to that destination are routed over circuit-switched voice facilities.
ITG engineering guidelines Figure 28 QoS levels with G.729A/AB codec Figure 29 QoS level with G.711 codec Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
Measure intranet QoS 143 Figure 30 QoS level with G.723 codec Obtain QoS measurement tools PING and Traceroute are standard IP tools that are usually included with a network host’s TCP/IP stack. A survey of QoS measurement tools and packages, including commercial ones, can be found in the home page of the Cooperative Association for Internet Data Analysis (CAIDA) at www.caida.org These include delay monitoring tools that include features like timestamping, plotting, and computation of standard deviation.
ITG engineering guidelines time=94ms 68 bytes from (10.3.2.7): icmp_seq=0 ttl=225 time=112ms 68 bytes from (10.3.2.7): icmp_seq=0 ttl=225 time=97ms ^? --- Richardson3 PING Statistics --8 packets transmitted, 8 packets received, 0% packet loss round-trip (ms) min/avg/max = 94/96/112 The time field displays the round trip time (rtt). So that the delay sample results match what the IP Trunk 3.
Measure intranet QoS 145 Measure end-to-end packet loss The PING program also reports if the ICMP packet made its round trip correctly or not. Use the same PING host setup to measure end-to-end error. Use the same packet size parameter. Sampling error rate, however, requires taking multiple PING samples, at least 30 to be statistically significant. Therefore, obtaining an error distribution requires running PING over a greater period of time.
ITG engineering guidelines Network delay and packet loss evaluation example From PING data, calculate the average one-way delay (halved from PING output and adding 93 ms IP Trunk 3.01 (and later) processing delay) and standard deviation for latency. Do a similar calculation for packet loss without adjustment. Adding a standard deviation to the mean of both delay and loss is for planning purposes. A customer might want to know whether traffic fluctuation in their intranet reduces the user’s QoS.
Measure intranet QoS 147 In contrast, the site pair Santa Clara/Ottawa has both QoS levels of mean and mean+standard deviation falling in the excellent region. The customer has more confidence that during peak traffic period, the "excellent" service level is likely to be upheld (better than 84% chance under the assumption of Normal distribution). Other measurement considerations The PING statistics described above measure the intranet prior to IP Trunk 3.
ITG engineering guidelines This model already takes into account some characteristics of the IP Phone, and therefore the impairment factors are not identical to those shown in the ITU-T standards. Refer to Table 32 "R value translation" (page 149) for the translation of R values into user satisfaction levels. Table 29 Impairment factors of codecs Codec Codec Impairment (lc) (msec frames) G.711 0 G.729A/AB 11 - 20 or 30 G.729A/AB 16 - 40 or 50 G.723.1 (5.3 Kbps) 19 G.723.1 (6.
Measure intranet QoS 149 Table 32 R value translation R Value (lower limit) MOS User Satisfaction 90 4.5 Very satisfied 80 4.0 Satisfied 70 3.5 Some users dissatisfied 60 3.0 Many users dissatisfied 50 2.5 Nearly all users dissatisfied 0 1 Not recommended Use Table 33 "IP Trunk 3.01 (and later) QoS levels" (page 149) to estimate the IP Trunk 3.01 (and later) QoS level based on QoS measurements of the intranet.
ITG engineering guidelines QoS level Network delay (ms) Packet loss (%) G.711 20 G.729A/AB 30 G.723.1 (6.
Measure intranet QoS 151 • 0.5% packet loss: lp = 2 Then: R = 94 - 0 - 0 - 2 R = 92 Using Table 33 "IP Trunk 3.01 (and later) QoS levels" (page 149), a value of 92 means the users are very satisfied. Scenario 2 A campus network has the following characteristics: • G.711 codec • 50 msecs delay • 1.
ITG engineering guidelines • 0.5% packet loss: lp = 8 Then: R = 94 - 11 - 5 - 8 R = 70 Using Table 33 "IP Trunk 3.01 (and later) QoS levels" (page 149), a value of 70 means some users are dissatisfied. Does the intranet meet expected IP Trunk 3.01 (and later) QoS? At the end of this measurement and analysis, there should be a good indication if the corporate intranet in its present state can deliver adequate voice and fax services.
IP Trunk 3.01 (and later) LAN installation and configuration 153 Figure 31 Basic setup of the IP Trunk 3.01 (and later) system IP trunk card connections 10/100BaseT Ethernet ports The Media Card 32-port and ITG-Pentium 24-port trunk cards each have two Ethernet ports. The 10/100BaseT Ethernet port on the DSP daughterboard, with connectors located on the faceplate or on the I/O panel breakout cable, transmits Voice over IP (VoIP) traffic and connects to the Telephony LAN (TLAN) subnet.
ITG engineering guidelines The Media Card 32-port and ITG-Pentium 24-port trunk cards have two Ethernet ports per card, so the IP Trunk 3.01 (and later) system can support two different TLAN and ELAN subnet connections.
IP Trunk 3.01 (and later) LAN installation and configuration TLAN Node IP 10.0.0.56 TLAN Card IP 10.0.0.57 TLAN GW 10.0.0.1 TLAN Subnet Mask 255.255.255.0. 155 The ELAN subnet range of addresses – 10.0.0.129 to 10.0.0.160 – overlaps the TLAN subnet range of addresses – 10.0.0.1 to 10.0.0.255. This contravenes the IP addressing practices, as it is equally valid to route the IP packets over either interface. The resulting behavior from such a setup is undetermined.
ITG engineering guidelines Private IP addresses Private IP addresses are internal IP addresses that are not routed over the internet. They can be routed directly between separate intranets, provided that there are no duplicated subnets in the private IP addresses. Private IP addresses can be used to configure the TLAN and ELAN subnets, so that scarce public IP addresses are used efficiently. Three blocks of IP addresses have been reserved for private intranets: • 10.0.0.0 – 10.255.255.255 • 172.16.
IP Trunk 3.01 (and later) LAN installation and configuration 157 Multiple IP Trunk 3.01 (and later) nodes on the same ELAN and TLAN segments There are several configurations where it is acceptable to put multiple IP Trunk 3.01 nodes on the same dedicated ELAN and TLAN segments (separate subnets), or on a dedicated ELAN/TLAN segment (single subnet): 1. Several IP Trunk 3.
ITG engineering guidelines TLAN subnet design The IP Trunk 3.01 (and later) nodes must connect to the intranet to minimize the number of router hops between the systems if there is adequate bandwidth on the WAN links for the shorter route. This reduces the fixed and variable IP packet delay, and improves the voice QoS. If a mixed-codec IP Trunk 3.
IP Trunk 3.01 (and later) LAN installation and configuration 159 Priority routing for voice packets Routers having the capability to turn on priority for voice packets should have this feature enabled to improve QoS performance. If the Type of Service (TOS) field or Differentiated Services (DiffServ) is supported on the IP network, the decimal value of the DiffServ/TOS byte can be configured.
ITG engineering guidelines WARNING Configure the ports on Layer 2 or Layer 3 switching equipment as auto-negotiate. If one side is manually configured, and the other side is configured as auto-negotiate, the following situation occurs. The auto-negotiate side sets itself to the manually configured side’s speed, but always sets itself to half-duplex transmission. If the manually-configured side is full-duplex transmission, then a mismatch occurs and voice quality is unsatisfactory.
IP Trunk 3.01 (and later) DSP profile settings 161 • Always keep the TLAN UTP cabling to less than 50 meters for the ITG-Pentium 24-port trunk card. • As an interim measure, connect to each ITG-Pentium 24-port trunk card and log in to the ITG> shell. In the shell, use the commands tlanDuplexSet and tlanSpeedSet to configure the TLAN interface to operate at half-duplex 10BaseT.
ITG engineering guidelines • Profile 3: G.711, G.729B, Fax The Media Card 32-port trunk card does not support Profile 3. The DSP coding algorithm parameter sets the preferred codec of each IP trunk card. The recommendation is to use Profile 1, and to set the preferred codec to G.729AB with VAD/Silence Suppression with a payload setting of 30 ms. With this codec-payload combination, IP Trunk 3.01 (and later) can deliver good QoS but loads less than 10 kbit/s per port on the intranet.
IP Trunk 3.01 (and later) DSP profile settings 163 2. Voice playout maximum delay. 3. Fax playout nominal delay. This can range from 0 to 300 ms, with 100 ms as the default size. As discussed in "Adjust jitter buffer size" (page 136), lowering the jitter buffer size decreases the one-way delay of voice packets; however, setting the jitter buffer size too small causes unnecessary packet discard. If it is necessary to discard to downsize the jitter buffer, first check the delay variation statistics.
ITG engineering guidelines When a system equipped with an IP Trunk 3.01 (and later) node serves as a tandem switch in a network where some circuit-switched trunk facilities have an excessively low audio level, Silence Suppression, if enabled, degrades the quality of service by causing choppiness of speech. Under tandem switching conditions where loss level cannot compensate, disable Silence Suppression using the TM 3.1 ITG ISDN Trunk Node Properties DSP profile tab codec options sub-tab.
Post-installation network measurements 165 expectations and networking technology – can render a design obsolete or non-compliant with QoS objectives. Review the design periodically against prevailing and trended network conditions and traffic patterns, at least once every two to three weeks initially, then eventually on a quarterly basis.
ITG engineering guidelines In subsequent design cycles, review and refine the QoS objective, based on data collected from intranet QoS monitoring. Having decided on a set of QoS objectives, then determine the planning threshold. The planning thresholds are based on the QoS objectives. These thresholds are used to trigger network implementation decisions when the prevailing QoS is within range of the targeted values. This gives time for implementation processes to follow through.
Post-installation network measurements 167 SNMP network management Simple Network Management Protocol (SNMP)-based Network Management Systems (NMS) provide a useful way of monitoring a real-time network from end to end. This is important for networks using VoIP. User complaints of slow downloads are no longer enough to diagnose problems. An NMS can ensure that problems on a network running real-time traffic are solved quickly to maintain high-quality service.
ITG engineering guidelines — number of cards and ports, IP Trunk 3.01 (and later) node and card parameters — fallback threshold level — Codec image — voice and fax payload — voice and fax playout delay — audio gain, echo cancellor tail delay size, Silence Suppression threshold — software version User feedback Qualitative feedback from users helps confirm if the theoretical QoS settings match what end users perceive.
TM 3.1 management and configuration of IP Trunk 3.01 (and later) Contents This section contains information on the following topics: "Introduction" (page 169) "TM 3.1 ITG Engineering rules" (page 169) "TM 3.1 network setup guidelines" (page 170) "TM 3.1 remote access configuration" (page 170) "TM 3.1 PC description" (page 172) "TM 3.1 PC hardware and software requirements" (page 173) "Hard drive requirements" (page 174) Introduction The TM 3.1 PC application is designed to support both ITG 2.
TM 3.1 management and configuration of IP Trunk 3.01 (and later) 2. In theory, a single TM 3.1 installation can support up to 500 system’s. However, TM 3.1 applications requiring real-time, such as Traffic Analysis retrieval of traffic data, are limited to a much smaller number of systems. 3. TM 3.1 Alarm Notification can receive a maximum of 20 SNMP traps per second (based on the recommended PC configuration). In large networks, Nortel recommends that multiple TM 3.
TM 3.1 remote access configuration 171 Figure 32 Remote access with full access to customer LAN/WAN A single remote support and administration TM 3.1 PC can administer a local node through the ITG Management LAN or can administer a remote node through the WAN. The remote access capabilities are provided through a modem router that has access to any of the ITG Management LANs. The Remote TM 3.
TM 3.1 management and configuration of IP Trunk 3.01 (and later) Figure 33 Remote access with no access to customer LAN/WAN In this case, a local TM 3.1 PC on an IP Trunk 3.01 (and later) ELAN subnet has access to only the IP trunk cards on the local node. A private IP address can be used for the TM 3.1 PC since management and alarm traffic would only travel over the private IP Trunk 3.01 (and later) ELAN subnet. A modem can be used to connect the remote TM 3.1 PC to the local TM 3.
TM 3.1 PC hardware and software requirements 173 A single network drive location is chosen during the TM 3.1 client PC installation process. For multi-system configurations where large data store requirements exceed the capacity of a single drive, or where data integrity is highly valued, a Redundant Array of Inexpensive Disks (RAID) storage solution is recommended. Tape or other backup methods are highly recommended. When installing TM 3.
TM 3.1 management and configuration of IP Trunk 3.01 (and later) • printer port (required for the dongle) • dongle (for server or stand-alone only) • Windows-compatible mouse (PS/2 mouse preferred to free up a PC serial port) CAUTION Service Interruption Do not install TM 3.1 on a Windows NT or Windows 2000 system that is configured as a Primary Domain Controller (PDC). For detailed information on the software requirements and the supported platforms for TM 3.1, refer to Telephony Manager 3.
TM 3.1 PC hardware and software requirements TM 3.1 application Program store Data store Maintenance Windows 1 MB Negligible Alarm Management with Alarm Notification 1.5 MB Negligible Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
TM 3.1 management and configuration of IP Trunk 3.01 (and later) Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
Install and configure IP Trunk 3.01 (and later) node Contents This section contains information on the following topics: "Introduction" (page 179) "Before you begin" (page 180) "Installation procedure summary" (page 180) "ESN installation summary" (page 182) "Create the IP Trunk 3.01 (and later) Installation Summary Sheet" (page 183) "Channel Identifier planning" (page 184) "Preferred ISL channel numbering" (page 184) "Incorrect ISL channel numbering plans" (page 189) "Install and cable IP Trunk 3.
Install and configure IP Trunk 3.
Introduction 179 "Configure Network Connections" (page 239) "Configure card properties" (page 240) "Configure DSP profiles for the IP Trunk 3.01 (and later) node" (page 244) "Configure SNMP Traps/Routing and IP addresses tab" (page 247) "Configure Accounting server" (page 250) "Control node access with SNMP community name strings" (page 251) "Exit node property configuration session" (page 252) "Create the IP Trunk 3.01 (and later) node dialing plan using TM 3.1" (page 253) "Retrieve the IP Trunk 3.
Install and configure IP Trunk 3.01 (and later) node Before you begin Follow the steps in Procedure 6 "Meeting installation requirements" (page 180) to ensure that installation requirements are met. Procedure 6 Meeting installation requirements Step Action 1 Install TM 3.1 (and later). Make sure the ITG ISDN IP Trunk and Alarm Management applications are installed. 2 Upgrade the system software to CS 1000 Release 4.0 or later. IP Trunk 3.
Installation procedure summary Table 37 Installation procedures Step Procedure 1 "Create the IP Trunk 3.01 (and later) Installation Summary Sheet" (page 183). 2 "Install and cable IP Trunk 3.01 (and later) cards" (page 190). See page "Card installation procedure" (page 190) 3 "Configure IP Trunk 3.01 (and later) data" (page 218). "Configure the ISL D-channel on the system for the DCHIP card for IP Trunk 3.01 (and later)" (page 218). "Configure ISDN feature in Customer Data Block" (page 222).
Install and configure IP Trunk 3.01 (and later) node Step Procedure See page "Exit node property configuration session" (page 252). "Create the IP Trunk 3.01 (and later) node dialing plan using TM 3.1" (page 253). "Retrieve the IP Trunk 3.01 (and later) node dialing plan using TM 3.1" (page 258). 5 "Transmit IP trunk card configuration data from TM 3.1 to the IP trunk cards" (page 260). "Configure the Leader 0 IP address" (page 260).
Create the IP Trunk 3.01 (and later) Installation Summary Sheet • 183 In LD 86, provision the RLB (Route List Block) RLI (Route List Index) blocks. — Add the RLI entries. Do not skip entries, as ESN searches the table from entry zero until the full initial set of entries are scanned to find an available route. — Enter the RDB for the entry. — Enter the DMI (Digit Manipulation Index), if required. — After the last entry is entered, enter the number of entries in the Initial Set (ISET).
Install and configure IP Trunk 3.01 (and later) node address address address Leader 0 Leader 1 Follower Follower Follower Follower Follower Follower Follower Follower Follower Follower Follower Follower Channel Identifier planning The Channel ID must be in sequential order on a card (no gaps in the numbering like 1, 2, 4, 7) and they must increase in number. If this is not done, the card channels are unusable.
Channel Identifier planning 185 Table 39 Mapping of unit number to ISL Channel number one card in system Unit number (from TN) ISL Channel number 0 1 1 2 2 3 3 4 4 5 5 6 6 7 7 8 8 9 9 10 10 11 11 12 12 13 13 14 14 15 15 16 16 17 17 18 18 19 19 20 20 21 21 22 22 23 23 24 Single card, sequential numbering, no gaps Media Card 32 port trunk card This is an example using a Media Card 32-port trunk card.
Install and configure IP Trunk 3.01 (and later) node Table 40 Mapping of unit number to ISL Channel number, one card in system Unit number (from TN) ISL Channel number 0 1 1 2 2 3 3 4 4 5 5 6 6 7 7 8 8 9 9 10 10 11 11 12 12 13 13 14 14 15 15 16 16 17 17 18 18 19 19 20 20 21 21 22 22 23 23 24 24 25 25 26 26 27 27 28 28 29 29 30 30 31 31 32 Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.
Channel Identifier planning 187 Two cards, sequential numbering, gap left for expansion This example is for two ITG-Pentium 24-port trunk cards. To allow room for replacement by a Media Card 32-port trunk card at a later date, a gap of eight channels has been left between the cards.
Install and configure IP Trunk 3.01 (and later) node Unit number (from TN) ISL Channel number 18 19 19 20 20 21 21 22 22 23 23 24 Card 2 Card 2 ISL channel numbering starts at 33 (24 numbers from Card 1 + 8 numbers for expansion + first number for Card 2 = 24 + 8+ 1 = 33).
Channel Identifier planning 189 Incorrect ISL channel numbering plans This section describes numbering plan errors. Gaps in ISL channel numbering sequence Table 42 "Channel numbering error, gap on one card" (page 189) shows gaps in the ISL numbering plan sequence. A gap between channel numbers causes the IP trunk card to be unable to associate the ISL channel number with the B channel number. Therefore, only units 0 to 4 (loop shelf card 0 to loop shelf card 4) can be used.
Install and configure IP Trunk 3.01 (and later) node Overlapping channel numbers Do not provision the ISL channel numbers on both cards with the same channel numbers. For example, do not configure Channel 10 on both cards. The Meridian 1/CS 1000M rejects this numbering plan but the IP trunk card does not. Therefore, it is possible to implement the incorrect card numbering, making all channels above the first overlapping number unusable. Install and cable IP Trunk 3.
Install and cable IP Trunk 3.01 (and later) cards 191 The ITG-Pentium 24-port trunk card requires 24-pair tip and ring I/O cabling. NT8D37AA IPE modules have 24-pair tip and ring I/O cabling for card slots 0, 4, 8, and 12 only. Insert the left slot of the IP trunk card in NT8D37AA slots 0, 4, 8 or 12 only. NT8D37BA or later IPE modules have no such restriction. When multiple IP trunk cards are installed, distribute them between available IPE shelves.
Install and configure IP Trunk 3.01 (and later) node 2 Remove any existing I/O panel cables associated with any card previously installed in the selected card slot. 3 Install the NTWE07AA DCHIP PC Card into the internal PC Card slot on the IP trunk card that has been selected to provide the DCHIP function. (See Figure 34 "DCHIP PC Card and NTCW84EA pigtail cable" (page 192) on Figure 34 "DCHIP PC Card and NTCW84EA pigtail cable" (page 192).
Install NTCW84JA Large System I/O Panel 50-Pin filter adapter 193 When the IP trunk cards are installed, the red LED on the faceplate is lit if: the card has rebooted; the card is active, but there are no trunks configured on it; or the card is active and has trunks, but the trunks are disabled. If the LED does not follow the pattern described (such as remaining continuously flashing or weakly lit), replace the card.
Install and configure IP Trunk 3.01 (and later) node Remove existing I/O panel filter adapter The standard I/O filter adapter is shielded metal with a black plastic insert connector. The NTCW84JA adapter uses yellow warning labels to indicate EMC filtering modifications and which MDF connection points can support 100BaseT connection. Follow the steps in Procedure 8 "Removing the existing I/O panel filter adapter" (page 194) to remove the existing I/O panel filter adapter.
Install NTMF94EA and NTCW84KA cables 195 Figure 35 NTCW84JA 50 pin I/O Panel Filter Connector Block Even though the ITG-Pentium 24-port trunk card is a two-slot card, only the leftmost slot is counted for the card slot number. Example: for an ITG-Pentium 24-port trunk card installed in slots 2 and 3, the slot number is 2. For more detailed cabling information and procedures for replacing the NT8D81BA with the NT8D81AA, see Appendix "Patches and advisements" (page 431).
Install and configure IP Trunk 3.01 (and later) node Install the NTCW84KA cable (for DCHIP cards) Follow the steps in Procedure 9 "Installing the NTCW84KA cable" (page 196) to connect the NTCW84KA cable for DCHIP cards. Procedure 9 Installing the NTCW84KA cable Step Action 1 Connect the NTCW84KA cable see to the I/O panel connector (see Figure 36 "NTCW84KA ELAN, TLAN, DCH, and serial cable" (page 197)).
Install NTMF94EA and NTCW84KA cables 197 Figure 36 NTCW84KA ELAN, TLAN, DCH, and serial cable Install the NTMF94EA cable (for non-DCHIP cards) Follow the steps in Procedure 10 "Installing the NTMF94EA cable" (page 197) to install the NTMF94EA cable for non-DCHIP cards. Procedure 10 Installing the NTMF94EA cable Step Action 1 Connect the NTMF94EA cable (see Figure 37 "NTMF94EA ELAN, TLAN and serial port cable" (page 198)) to the I/O panel connector.
Install and configure IP Trunk 3.01 (and later) node order to tie the shield of the LAN cable to the frame ground for EMC compliance. Figure 37 NTMF94EA ELAN, TLAN and serial port cable —End— Install shielded TLAN network interface cable Use Shielded CAT5 cable to connect to the ELAN and TLAN network interfaces on the NTCW84KA cable. To conduct a ground loop test, refer to "Prevent ground loops on connection to external customer LAN equipment" (page 446) and follow the test procedure.
Configure NT6D80 MSDL switches 199 When connecting the Media Card 32-port trunk card and/or ITG-Pentium 24-port trunk card to the TLAN subnet, the link status LED on the card faceplate associated with the TLAN network interface lights green when the connection is made. The link status LED on the hub port also lights green when connected to the IP trunk card.
Install and configure IP Trunk 3.01 (and later) node Table 44 NT6D80 MSDL settings for ITG-Pentium 24-port trunk card DCHIP RS-422-A DTE RS-422-A DTE RS-422-A DTE RS-422-A DTE Port 0 – SW4 Port 0 – SW8 all off all on Port 1 – SW3 Port 1 – SW7 all off all on Port 2 – SW2 Port 2 – SW6 all off all on Port 3 – SW1 Port 3 – SW5 all off all on The device number for the MSDL card is configured in LD 17 at the prompt DNUM.
Install filter and NTND26 cable (for MSDL and DCHIP cards in same Large System equipment row) 201 4 • NTND26AB – 18 ft • NTND26AC – 35 ft • NTND26AD – 50 ft Connect the appropriate NTND26 cable assembly to the D-Channel port connector on the faceplate of the MSDL card and to the inward side of the 15-pin filter connector installed in the I/O panel of the IPE Module that contains the DCHIP card (see Figure 39 "NTND26 cable routing diagram" (page 202)).
Install and configure IP Trunk 3.01 (and later) node Figure 39 NTND26 cable routing diagram 5 Connect the DCH (P5) connector of the NTCW84KA to the outward side of the 15-pin I/O panel filter connector.
Install filter and NTND26 cable (for MSDL and DCHIP cards in different Large System equipment rows) 203 2 Install the 15-pin I/O panel filter connector on the inward side of the bracket. 3 Obtain the correct length of the NTND26 DCHI Interface Cable Assembly to reach from the D-Channel port connector on the faceplate of the MSDL card to the outward side of the 15-pin filter connector installed in the I/O panel of the IPE Module that contains the DCHIP card.
Install and configure IP Trunk 3.01 (and later) node Table 45 NTAK02 SDI/DCH switch settings for IP Trunk 3.01 (and later) DCHIP Port 1 SW 1-1 SW 1-2 DCH OFF OFF Port 3 SW 1-3 SW 1-4 DCH OFF OFF Table 46 NTAK02 SDI/DCH jumper settings for the IP Trunk 3.
Cabling for the Media Card 32-port trunk card 205 Procedure 14 Installing the serial cable Step Action 1 To make a temporary connection to the IP Trunk 3.01 (and later) maintenance port from a local RS-232 TTY terminal or a modem, use the NTAG81CA PC Maintenance cable. a. Connect the DIN-8 connector to the maintenance port on the faceplate of the IP trunk card. b. Connect the DB9 connector to the COM port of a local PC running TTY terminal emulation.
Install and configure IP Trunk 3.01 (and later) node The ELAN network interface supports 10BaseT operation. 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 connectors replace the standard connectors provided on the system.
Cabling for the Media Card 32-port trunk card 207 Figure 40 EMC kit deployment ITG Card ELAN/TLAN Adapter (L-adapter) The L-adapter routes the signals to the following network interfaces: • ELAN • TLAN • one RS-232 port On Large Systems, the NT8D81AA cable is used to bring all 24 Tip & Ring pairs to the I/O panel. The NTCW84JA I/O panel mounting block must be installed on Large Systems before the ITG Card ELAN/TLAN Adapter (L-adapter) is installed.
Install and configure IP Trunk 3.01 (and later) node Figure 41 ITG card ELAN/TLAN adapter (L-adapter) Figure 42 "ITG card ELAN/TLAN adapter (Large system)" (page 209) shows the adapter installed in a Large System with a securing screw and tie wrap. Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
Cabling for the Media Card 32-port trunk card 209 Figure 42 ITG card ELAN/TLAN adapter (Large system) To install the L-adapter in a Small System, use a securing screw and retaining bracket. See Figure 43 "ITG card ELAN/TLAN adapter fitted to a Meridian 1 Option 11C Cabinet/ CS 1000M Cabinet" (page 210). Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
Install and configure IP Trunk 3.01 (and later) node Figure 43 ITG card ELAN/TLAN adapter fitted to a Meridian 1 Option 11C Cabinet/ CS 1000M Cabinet To install an adapter in a Meridian 1 PBX 11C Chassis / CS 1000M Chassis, use a securing screw and hook&loop tape. See Figure 44 "ITG card ELAN/TLAN adapter fitted to a Meridian 1 PBX 11C Chassis/CS 1000M Chassis" (page 211). Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.
Cabling for the Media Card 32-port trunk card 211 Figure 44 ITG card ELAN/TLAN adapter fitted to a Meridian 1 PBX 11C Chassis/CS 1000M Chassis When Media Card 32-port trunk cards are used to replace ITG-Pentium 24-port trunk cards, the existing NTMF94EA or NTCW84KA cabling can be used. The DCHIP connection on the NTCW84KA cable does not function with the Media Card 32-port trunk card.
Install and configure IP Trunk 3.01 (and later) node • 8 data bits • 1 stop bit, no parity • no flow control NTMF29BA DCHIP cable The NTMF29BA DCHIP cable connects to port 0 of the DCHIP PC Card and the MSDL/SDI DCHIP cable. Port 1 on the DCHIP PC Card is not used. The DCHIP PC Card, which connects to NTMF04BA and NTND26AA Cable, is keyed to allow insertion only in the correct direction. Refer to Figure 45 "NTMF29BA PC Card DCHIP cable installation" (page 212).
Cabling for the Media Card 32-port trunk card 213 2 Fit the screw through the secondary side of the Media Card 32-port trunk card into the threaded hole in the bracket and tighten. 3 Fit the DCHIP PC Card NTMF29BA cable assembly through the faceplate slot and push it home into the header. 4 Fit the DCHIP PC Card connector of the NTMF29BA cable assembly into Port 0 (the upper socket) on the DCHIP card. 5 Fit the clamp over the PC Card connector and into the bracket.
Install and configure IP Trunk 3.01 (and later) node Figure 46 Large System DCHIP cabling setup: intra-column/cube NTMF04BA MSDL extension cable The NTMF04BA cable connects the NTND26AA MSDL cable and the NTMF29BA DCHIP cable, when the Common Equipment shelf and the IPE shelf are in separate columns and not connected by internal cabling channels. A 15-way mounting block (A03511331) is shipped with the NTMF04BA cable.
Cabling for the Media Card 32-port trunk card 215 Figure 47 Large system DCHIP cabling setup: inter-column When the Universal Equipment Modules (UEM) are stacked vertically, or the UEM columns are bolted together, they are cabled in an inter-column configuration. See Figure 47 "Large system DCHIP cabling setup: inter-column" (page 215). This applies when the UEM system columns are physically separated and the DCHIP must exit the systems through the I/O panel.
Install and configure IP Trunk 3.01 (and later) node Figure 48 Option 11C DCHIP system cabling NTWE04AC/AD SDI/DCH Meridian 1 Option 11C Cabinet/CS 1000M Cabinet extension cable The NTWE04AC and the NTWE04AD are 10-ft and 1-ft DCHIP extension cables, respectively. They connect Port 1 or Port 3 of the DCHIP SDI/DCH cable used on the Meridian 1 Option 11C Cabinet/CS 1000M Cabinet (NTAK19BA or equivalent) with the DCHIP NTMF29Bx face-plate cable.
Cabling for the Media Card 32-port trunk card 217 Install ITG EMC shielding kit NTVQ83 with Small and Large System types. Refer to "ELAN and TLAN network interfaces" (page 205) for additional information on the cabling requirements. Media Card 32-port trunk card modem connection To provide remote access to the CLI for support and remote maintenance, a modem can be connected to the serial port of the Media Card 32-port trunk card.
Install and configure IP Trunk 3.01 (and later) node Figure 49 Wiring specifications —End— Configure IP Trunk 3.01 (and later) data First, configure D-channels, Route Data Blocks, and trunks through the system TTY. Then configure the ESN data blocks to implement the network dialing plan and translations. Record the D-Channel, CHIDs, and TNs for the IP Trunk 3.01 (and later) trunks on the IP Trunk 3.01 (and later) Installation Summary Sheet.
Configure IP Trunk 3.01 (and later) data 219 Prompt Response Description GRP x Network Group number, where: x=0–4 DNUM x Device Number for I/O ports, where: x = 0 – 15 PORT x Port number for MSDL card, where: x=0–3 DES IP TRUNK 16 character designator is "IP TRUNK" Specific description if more than one IP Trunk 3.01 (and later) route exists. ... USR User. ISLD Dedicated Mode ISDN Signaling Link.
Install and configure IP Trunk 3.01 (and later) node Prompt Response Description SIDE (USR) MSDL acts as User side of ISL. The IP Trunk 3.01 (and later) DCHIP card acts as the Network side of ISL. RLS 25 Release ID of PBX at the far end of the D-Channel. If the far end has an incompatible release, it prevents sending of application messages. Use LD 17 to configure the ISL D-channel for the DCHIP card in Small Systems.
Configure IP Trunk 3.01 (and later) data Prompt Response Description SIDE (USR) Meridian 1 Option 11C Cabinet/CS 1000M Cabinet SDI/DCH card acts as User side of ISL. 221 The DCHIP card acts as the Network side of ISL. RLS 25 Release ID of PBX at the far end of the D-Channel. If the far end has an incompatible release, it prevents sending of application messages. RCAP ND2 Network Name Display type signalling. All nodes must use same RCAP. ...
Install and configure IP Trunk 3.01 (and later) node Prompt Response Description USR ISLD User IFC SL1 Interface type for D-channel ISLM 382 Maximum number of Integrated Service Signaling Links USR Meridian 1/CS 1000M node type ... ... SIDE The IFC response entry must have the protocol entered in TM 3.1’s ITG Node Properties – Card Configuration Protocol pull-down menu.
Configure IP Trunk 3.01 (and later) data 223 Prompt Response Description - PNI (0) – 32700 Private Network Identifier. Configure the PNI to 1 or other non-zero value to support Meridian Customer Defined Network (MCDN) features that use non-call-associated signaling, such as Network Ring Again (NRAG) Network Message Services (NMS), Network ACD (NACD). Each feature needs ISDN signaling to be sent across the Meridian 1/CS 1000M network in the absence of a call.
Install and configure IP Trunk 3.01 (and later) node Prompt Response TKTP SAT Description Trunk type. TIE The trunk type for IP Trunk 3.01 (and later) trunks must be set to TIE. (NO) YES Satellite control (SAT) must be set to NO to enable Trunk Optimization before answer (TRO) and Trunk Anti-Tromboning (TAT). For IP Trunk 3.01 (and later), fallback to circuit-switched trunks does not depend on SAT=YES. ... DTRK ISDN Digital trunk route. (NO) IP Trunk 3.01 (and later) trunks are analog only.
Configure IP Trunk 3.01 (and later) data Prompt Response Description NCNA (YES) NO Network Calling Name allowed. NCRD (NO) YES Network Call Redirection allowed. CTYP 225 Call type for outgoing call dialed with the route access code (ACOD). Set to appropriate call type for IP Trunk 3.01 (and later) node numbering plan in order to make test calls using ACOD.
Install and configure IP Trunk 3.01 (and later) node Table 48 LD 16 NEW/CHG/OUT Prompt Response Description req new/chg/out type rdb cust 0-99 tktp TIE Trunk Type. M911P (NO)/YES M911 Trunk Type for MCDN Network. M911_ABAN (NO)/YES Optional call abandon treatment: YES = abandoned call treatment for route. NO = no abandoned call treatment for route. M911_TONE YES/(NO) optional call abandon tone: YES = tone given on answer. NO = silence given on answer.
Configure IP Trunk 3.01 (and later) data 227 ABTR (15) Range 0-30 Timer (in minutes) blocks the disconnect from being tandemed across to the target node. Default value: 15 minutes. This timer value can be added in increments of 1 minute. VTRK (NO)YES YES = supports IP Peer facilities. NODE Node ID associated with the Signalling Server dedicated for 911P trunks. IFC SL1 IFC is set to SL1 by default if M911P is set to YES. This prompt is not configurable.
Install and configure IP Trunk 3.01 (and later) node Prompt Response Description cu Format for Small System and Media Gateway 1000B where c = card and u = unit DES 16 character descriptive designator for the IP trunk card. See Note 1 hhhh:hh:hh:hh:hh For unit 0. The IP trunk card ELAN network interface MAC address. xxx.xxx.xxx.xxx For units 1 – 23. The IP trunk card ELAN network interface IP address. XTRK MAXU Extended Trunk Type: IP trunk card (1-slot or 2-slot assembly).
Configure IP Trunk 3.01 (and later) data Prompt Response 229 Description For nodes containing a mixture of 24-port and 32-port IP trunk cards, determine the starting CHID by adding the number of channels (ports) on the previous card to the CHID of the previous card. Example: Leader 0: - 1 (24-port card) Leader 1: - 25 (1 + 24) (32-port card) Follower: - 57 (25 + 32) (32-port card) The same First CHID must be entered in TM 3.
Install and configure IP Trunk 3.01 (and later) node interface MAC address; for example: 00:60:38:01:06:C6. To find the ELAN network interface MAC address, refer to the IP Trunk 3.01 (and later) Installation Summary Sheet. The ELAN network interface MAC address is labeled on the IP trunk card faceplate as the "motherboard Ethernet address." Alternatively, use the ITG shell command "ifShow" to display the Ethernet address for lnIsa (unit number 0).
Configure dialing plans within the corporate network 231 The time schedule is a 24-hour clock which is divided up the same way for all 7 days. Basic steps to program Time of Day for IP Trunk 3.01 (and later) routes are as follows: 1. Go to LD 86 ESN data block to configure the Time of Day Schedule (TODS) for the required IP Trunk 3.01 (and later) control periods. 2. Go to LD 86 RLB and apply the TODS on/off toggle for that route list entry associated with an IP Trunk 3.01 (and later) trunk route.
Install and configure IP Trunk 3.01 (and later) node If ESN5 is provisioned for an IP Trunk 3.01 (or later) node (both in the RDB and on the node cards), you must configure that node as "SL1 ESN5" in the dialing plan for all other ITG 2.x and IP Trunk 3.01 (or later) nodes. If these other nodes are also ESN5-capable, when originating a call they will pass the ESN5 prefix that they receive in the messages from the Meridian 1 to the destination node.
Configure dialing plans within the corporate network 233 Use the traditional PSTN for general modem traffic General modem traffic (for example, V.36, V.90) cannot be supported on ITG. The Meridian 1/CS 1000M routing controls must be configured to route modem traffic over circuit-switched trunks instead of over IP Trunk 3.01 (and later). Use the ESN TGAR, NCOS, and facility restriction levels to keep general modem traffic off of the IP Trunk 3.01 (and later) route.
Install and configure IP Trunk 3.01 (and later) node LD 86 Configure Route List Block with Step Back on Congestion on ISDN Prompt Response Description REQ NEW Add new data. CUST xx Customer number as defined in LD 15. FEAT RLB Route List Data Block. RLI xxx Route List Index to be accessed, where xxx is: 0-127 for BARS 0-255 for NARS 0-999 for FNP ENTR xx Entry number for NARS/BARS Route List, where xx is: 0-63 for BARS/NARS ...
Configure dialing plans within the corporate network Prompt Response Description TYPE DSC TSC Distant Steering Code. Trunk Steering Code. xx Route List Entry created in LD 86. 235 ... RLB LD 90 Configure dialing plan Prompt Response Description REQ NEW Add new data. CUST xx Customer number as defined in LD 15. NET Feature. Network translation tables. FEAT TRAN AC1 AC2 TSC Translator. Access Code 1 (NARS/BARS). Access Code 2 (NARS). NPA NXX LOC SPN Type of data block.
Install and configure IP Trunk 3.01 (and later) node The IP trunk cards must be enabled later after the card properties and optionally, the IP Trunk 3.01 (and later) software, has been transmitted from TM 3.1 to the IP trunk cards. Configure IP Trunk 3.01 (and later) data in TM 3.1 Before the IP Trunk 3.01 (and later) data is configured in TM 3.1, obtain all the IP addresses for the new IP Trunk 3.01 (and later) node from the network administrator and add them to the installation summary sheet.
Configure IP Trunk 3.01 (and later) data in TM 3.1 237 Add an IP Trunk 3.01 (and later) node and configure general node properties Follow the steps in Procedure 17 "Adding a node and configuring general node properties" (page 237) to add an IP Trunk 3.01 (and later) node and configure general node properties. Procedure 17 Adding a node and configuring general node properties Step Action 1 Launch TM 3.1 (and later) on the TM 3.1 PC. 2 From the TM 3.
Install and configure IP Trunk 3.01 (and later) node Figure 51 General tab Configure node location properties 5 Define the Node Location properties: select the TM 3.1 site, TM 3.1 system, Customer, and Node number from the drop-down lists. The site name, system name, and Customer must exist in the TM 3.1 Navigator before a new IP Trunk 3.01 (and later) node can be added. —End— Single vs.
Configure IP Trunk 3.01 (and later) data in TM 3.1 239 For traffic reasons, use separate subnets for nodes consisting of multiple ITG-Pentium 24-port trunk cards and Media Card 32-port trunk cards. Refer to the Engineering Guidelines sections "Configure a system with separate subnets for voice and management" (page 153) and "Single subnet option for voice and management" (page 156).
Install and configure IP Trunk 3.01 (and later) node a. Enter the ELAN node IP address in the Management LAN Node IP field. b. Enter the ELAN network interface gateway IP address in the Management LAN gateway IP address field. The ELAN network interface gateway (router) also functions as the voice gateway (router). c. Enter the ELAN subnet mask in the Management LAN subnet mask field.
Configure IP Trunk 3.01 (and later) data in TM 3.1 241 When adding the first card, select the card role Leader 0. When adding the second card, select the card type Leader 1. When adding additional cards, select the card type Follower. Configure the DCHIP and D-Channel information. 3 If Use separate subnets in the General tab was checked earlier, perform steps a-d. a. Enter the Management IP address (ELAN network interface IP address). b.
Install and configure IP Trunk 3.01 (and later) node Each Follower card can optionally have its TLAN network interface IP address and TLAN network interface gateway IP address on a different TLAN subnet than Leader 0 and Leader 1. 4 If Use separate subnets in the General tab was unchecked earlier, perform steps a and b: a. Enter the Management IP address (ELAN network interface IP address). b. Enter the Management MAC address ELAN network interface MAC address). It is the motherboard Ethernet address.
Configure IP Trunk 3.01 (and later) data in TM 3.1 243 The choices are SL1, SL1 ESN5, ESIG and ISIG for networks consisting of Large Systems. For networks that include Small Systems, the choices are SL1 or SL1 ESN5. In addition to IP Trunk 3.01 (and later) nodes, the IP telephony trunk network might also contain ITG Trunk 1.0 Basic Trunk nodes or Nortel IP Telephony Connection Manager. Use H.323 V2 node capability for these nodes. Once a DCHIP for the IP Trunk 3.
Install and configure IP Trunk 3.01 (and later) node Configure DSP profiles for the IP Trunk 3.01 (and later) node Follow the steps in Procedure 20 "Configuring DSP profiles for the IP Trunk 3.01 (and later) node" (page 244) to select a DSP profile, set Profile Options and Codec Options and, if required, modify default DiffServ/TOS values from 0. Set these profiles once for the IP Trunk 3.01 (and later) node. In a later step, download the DSP profiles card properties to each card.
Configure IP Trunk 3.01 (and later) data in TM 3.1 3 245 Click the Profile Options tab. See Figure 54 "DSP Profile Profile Options tab" (page 245). This tab displays the default General and FAX options values according to the selected DSP profile. Figure 54 DSP Profile Profile Options tab 4 Change the General and FAX option parameters, if required. To revert to the default settings, click Reset Defaults.
Install and configure IP Trunk 3.01 (and later) node Figure 55 DSP Profile Codec Options tab 6 Perform steps 7 and 8 if required. To revert to the default settings, click Reset Defaults. CAUTION The default Codec Options are appropriate for most applications. Only an expert in VoIP should modify the Codec Options parameters. "IP Trunk 3.01 (and later) DSP profile settings" (page 161) 7 To turn off a codec, click the codec and uncheck the checkbox.
Configure IP Trunk 3.01 (and later) data in TM 3.1 247 Change default DiffServ/ToS value for Control and Voice Follow the steps in Procedure 21 "Changing the default DiffServ Codepoint (DSCP) value for Control and Voice" (page 247) to change the default DiffServ/ToS value for Control and Voice.
Install and configure IP Trunk 3.01 (and later) node Subnet mask = 255.255.255.0 Subnet = 23.11.42.0 IP Trunk card TLAN IP = 23.11.42.121 Subnet mask = 255.255.255.0 Subnet = 23.11.42.0 23.11.42.0 = 23.11.42.0. Therefore, the SNMP traps will be sent to the TLAN router. WARNING Nortel recommends the SNMP client (that is, the TM 3.1 PC) not be put on the TLAN subnet. Placing the TM 3.1 PC on the ELAN subnet is a more secure configuration.
Configure IP Trunk 3.01 (and later) data in TM 3.1 2 249 Check the Enable SNMP traps check box to enable sending of SNMP traps to the SNMP trap destinations that appear in the list. Enter at least one SNMP trap destination IP address if this option is checked. The SNMP trap destination IP addresses determine where event and alarm messages are sent Refer to "Configure TM 3.1 Alarm Management to receive SNMP traps from the IP trunk cards" (page 277) to configure TM 3.
Install and configure IP Trunk 3.01 (and later) node The IP trunk card uses the addresses in the routing table entries to route signaling packets over the ELAN network interface gateway (router) on the ELAN subnet. Without routing table entries, the IP trunk card routes signaling traffic over the TLAN network interface gateway. Sending signaling traffic over the TLAN subnet can affect voice quality. 7 Click Apply. 8 Click OK to exit the window.
Control node access with SNMP community name strings 251 Figure 57 Accounting Server tab 2 Click the Enable Radius accounting records checkbox. 3 Enter the Radius accounting server IP address. Add the same Accounting Server IP address that was configured in the Card Routing Table entries as discussed in "Configure SNMP Traps/Routing and IP addresses tab" (page 247). 4 Change the default port number from the default (1813), if required. 5 Enter the key.
Install and configure IP Trunk 3.01 (and later) node The community name strings are configured on the Security tab. These are not picked up from the System Properties – General tab. Figure 58 ITG Node Properties Security Tab Change the current System Mgmt Read and System Mgmt Read/Write community name strings as per the Card. TM 3.1 uses the previous read/write community name to transmit the card properties. The first time data is transmitted after changing the password, TM 3.
Control node access with SNMP community name strings 253 Create the IP Trunk 3.01 (and later) node dialing plan using TM 3.1 Follow the steps in Procedure 24 "Configure the ITG Dialing Plan General tab" (page 253) to configure the IP Trunk 3.01 (and later) node dialing plan in TM 3.1. Use this procedure to create the dialing plan for the first node in the network. This procedure also can be used to create a dialing plan for a new node in a very small network.
Install and configure IP Trunk 3.01 (and later) node Figure 59 ITG Dialing Plan Remote Node Properties window General tab 3 Select the destination Node to be added from the list. TM 3.1 provides the IP Trunk 3.01 (and later) Node IP address in a greyed-out box and fills in the node name in the Node Name field. 4 Define Node capability for the destination node. The default setting is SL1, which supports MCDN features.
Control node access with SNMP community name strings 255 In addition to IP Trunk 3.01 (and later) nodes, the IP telephony trunk network may contain ITG Trunk 1.0 Basic Trunk nodes or Nortel IP Telephony Connection Manager. Use H.323 V2 node capability for these nodes. Quality of Service section The default setting enables Quality of Service (QoS) monitoring. QoS monitoring allows new calls to fallback to alternate circuit-switched trunk routes when the IP network QoS falls below the configured threshold.
Install and configure IP Trunk 3.01 (and later) node 3 Enter the Called Number digits for the ESN translation type in the Dial plan digits field. See #2 in Figure 60 "ITG Dialing Plan Remote Node Properties window Digits dialed tab" (page 257). The digits must be leftwise unique within the ESN translation types that correspond to given pair of NPI and TON values. Every ESN translation type generates a unique pair of NPI and TON values by default.
Control node access with SNMP community name strings 257 Figure 60 ITG Dialing Plan Remote Node Properties window Digits dialed tab The digit manipulation defined in the Digits dialed tab of the ITG Dialing Plan – Remote Node Properties window does not apply to the Destination Number of the Facility messages for non-call-associated signalling for MCDN features. These features include: NRAG, NMS, NACD, and NAS.
Install and configure IP Trunk 3.01 (and later) node 6 Click Apply. 7 Repeat steps 7 through 11 until all the ESN translation Dial Plan digits for this destination node have been added. 8 Click OK. The Dialing Plan window appears with the added dialing plan entries. 9 Repeat steps 2 through 13 until dialing plan entries for all the destination nodes in the drop down list and all destination nodes Not Defined on this TM 3.1 PC have been added. —End— Retrieve the IP Trunk 3.
Control node access with SNMP community name strings 259 4 Click the Configuration tab. Record the Management IP address of Leader 0 on the new node. 5 On the Configuration tab, change the Management IP address of Leader 0 on the new node. Enter the Management IP address of the Leader 0 card on the existing node recorded in Step 2. 6 Click Change and then click OK. 7 Select the new node in the upper part of the IP Telephony Gateway - ISDN IP Trunk window.
Install and configure IP Trunk 3.01 (and later) node Transmit IP trunk card configuration data from TM 3.1 to the IP trunk cards IP Trunk 3.01 (and later) nodes and IP trunk cards are configured in the TM 3.1 ITG ISDN IP Trunk application and then transmitted to the IP trunk cards. The configuration data is converted by TM 3.1 to text files. The IP trunk cards then obtain the configuration files from TM 3.1 using an FTP server on TM 3.1. ATTENTION Important When TM 3.
Transmit IP trunk card configuration data from TM 3.1 to the IP trunk cards 261 NTAG81BA Maintenance Extender cable to provide an extension between the NTAG81CA PC Maintenance cable and the TM 3.1 PC.
Install and configure IP Trunk 3.01 (and later) node • "yyy.yyy.yyy.yyy" is the ELAN network interface gateway (router) IP address on the ELAN subnet. If the TM 3.1 PC is connected locally to the LAN and there is no ELAN gateway, then the gateway IP address is "0.0.0.0". • "zzz.zzz.zzz.zzz" is the subnet mask for the ELAN network interface IP address of Leader 0 on the ELAN subnet. All ITG shell commands are case-sensitive. A space separates the command from the first parameter.
Transmit IP trunk card configuration data from TM 3.1 to the IP trunk cards 263 Procedure 28 Installing a Backup Leader in IP Trunk 3.01 (and later) Step Action 1 Ensure both IP trunk cards are running the same version of software. The software version is displayed when logging into the IP trunk cards. The software version can also be displayed by typing the command swVersionShow at the ITG CLI interface. 2 If the software versions are different, follow the upgrade erase procedure.
Install and configure IP Trunk 3.01 (and later) node the IP trunk card from the system interface, see "System commands LD 32" (page 384). 8 From TM 3.1, transmit the NODE PROPERTY, CARD PROPERTY, and Dialing Plan to the active leader and to all disabled IP trunk cards. This action is successful to Leader 0, but fails to Leader 1, as Leader 1 does not yet have an IP address. 9 Remove Leader 1 from the system backplane. 10 Reboot Leader 0.
Transmit IP trunk card configuration data from TM 3.1 to the IP trunk cards 265 Disable IP trunk cards whenever transmitting card properties or new software. Use the TM 3.1 Maintenance Windows, the TM 3.1 System Passthru terminal, or a system management terminal directly connected to a TTY port. Use the LD 32 DISI command to disable the IP trunk cards when idle. In the TM 3.1 IP Telephony Gateway – ISDN IP Trunk window, select View > Refresh and verify that the card status is showing "Disabled".
Install and configure IP Trunk 3.01 (and later) node Verify installation and configuration To verify installation and configuration, check the IP trunk card faceplate displays. 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 faceplate display shows "LDR". The Leader 1 card is now autoconfigured as a Leader, reboots automatically, and enters the state of "Backup Leader".
Transmit IP trunk card configuration data from TM 3.1 to the IP trunk cards 267 Figure 61 IP trunk card status If the (a) IP Trunk 3.01 (and later) Node is being installed from an TM 3.1 PC on a remote subnet, and (b) communication with the Leader 1 and the Follower cards is not possible after transmitting the node properties, card properties and dialing plan to Leader 0 and rebooting the Leader 0 card, this means that the Leader 1 and the Follower cards are unable to communicate with the remote TM 3.1 PC.
Install and configure IP Trunk 3.01 (and later) node 2 Verify that the TN, ELAN network interface MAC addresses, and IP addresses are configured correctly for each IP trunk card. Select any card in the IP Trunk 3.01 (and later) node in the TM 3.1 ITG – ISDN IP Trunk window and select menu Configuration > Node > Properties from the drop-down lists. Compare the values displayed on the General tab and the Card Configuration tab with those on the IP Trunk 3.01 (and later) Installation Summary Sheet.
Configure date and time for the IP Trunk 3.01 (and later) node 269 5 Click the Start transmit button. 6 Monitor progress in the Transmit Control window. Confirm that the Card Properties and Dialing Plan are transmitted successfully to all the IP trunk cards, which are identified by TNs. 7 When the transmission is complete, click the Close button. 8 Use the LD 32 ENLC command to enable the IP trunk cards in the IP Trunk 3.01 (and later) node.
Install and configure IP Trunk 3.01 (and later) node 4 Set the correct date and time. 5 Click OK. The clock is updated immediately on the Active Leader card (Leader 0 or Leader 1), which in turn updates the other cards in the IP Trunk 3.01 (and later) node. —End— Change the default ITG shell password to maintain access security Follow the steps in Procedure 33 "Changing the default ITG shell password" (page 270) to change the default user name and password when installing the IP Trunk 3.
Change default ESN5 prefix for non-ESN5 IP telephony gateways 271 Enter new password again to confirm: new password 5 Record the new user name and password and transmit to authorized network security personnel. 6 Repeat procedure for all cards in the node. —End— If the entire sequence of commands is successfully entered, the system response value = 0 = 0x0 is displayed.
Install and configure IP Trunk 3.01 (and later) node Figure 62 esn5PrefixShow 4 At the ITG prompt, enter >esn5PrefixSet "1xx" where xx = the NCOS value. In Figure 63 "esn5PrefixSet" (page 272), the default value was changed from NCOS 00 to 03. Figure 63 esn5PrefixSet —End— Check and download IP trunk card software in TM 3.1 Follow the steps in Procedure 35 "Checking the IP trunk cards software version" (page 272) to check the software version of the IP trunk cards in a new IP Trunk 3. 0 node.
Check and download IP trunk card software in TM 3.1 3 273 Click the Configuration tab and record S/W version, Card density and Card TN for each card in the new node. See Figure 64 "ITG Card Properties Configuration tab" (page 273). Figure 64 ITG Card Properties Configuration tab 4 Check the Nortel website to find the latest recommended IP Trunk 3.01 (and later) software release. Go to www.nortel.com. Follow the links to Customer Support and Software Distribution or go to www.nortel.com/support.
Install and configure IP Trunk 3.01 (and later) node • 8 For ITG-Pentium 24-port trunk cards, download the Software Package for Release IP Trunk 3.01 (and later). When prompted, select Download. Record the file name and location of downloaded software on the TM 3.1 PC. —End— Now the new IP trunk card software is ready to be transmitted from TM 3.1 to the IP trunk cards. Transmit new software to the IP trunk cards Verify that the IP trunk cards are disabled before transmitting new card software.
Check and download IP trunk card software in TM 3.1 • If a mix of Media Card 32-port and ITG-Pentium 24-port trunk cards is in the same IP Trunk 3.01 (and later) node, then select all cards of the same density in the lower half of the window. Hold down the Ctrl key while making individual card selections. 4 Select menu Configuration/Synchronize/Transmit. The ITG Transmit Options dialog box appears. 5 If transmitting new software to a node, choose step a or b.
Install and configure IP Trunk 3.01 (and later) node 6 Reboot each IP trunk card that received transmitted software, so that the new software can be applied. Start the rebooting with Leader 0, then Leader 1, and finally the follower cards. Double-click the card in the lower part of the IP Telephony Gateway - ISDN IP Trunk window. The Card Properties Maintenance tab appears. Click Reset to reboot the card. Click OK.
Configure TM 3.1 Alarm Management to receive SNMP traps from the IP trunk cards 277 VxWorks login: itgadmin Password: itgadmin ITG> 4 Disable the ITG-Pentium 24-port or Media Card 32-port trunk card in LD 32 (DISI lsc). Wait for the NPRxx message. 5 Use the command DCHdisable to disable the D-channel function on the card. 6 Use the command loader 1, "/C:pcmv32.bin" to transfer the DCHIP PC Card software to the DCHIP PC Card. The ’1’ indicates the internal PC Card slot on the DCHIP Card.
Install and configure IP Trunk 3.01 (and later) node Procedure 38 Configuring TM 3.1 ALarm Management to receive SNMP traps from the IP trunk cards Step Action 1 In the TM 3.1 Navigator window select Utilities > Alarm Notification. The TM 3.1 Alarm Notification dialog box appears. 2 Select Configuration > Run Options. The "Alarm Notification Run Options" dialog box appears. 3 Click the Control Files tab. 4 Click Devices > Browse. The "Open" dialog box appears.
Configure TM 3.1 Alarm Management to receive SNMP traps from the IP trunk cards 279 Figure 66 Devices.txt file: 6 For each IP trunk card in each monitored IP Trunk 3.01 (and later) node, add a line consisting of three fields separated by spaces. See Table 50 "Format of Devices.txt file" (page 279). Enter the first line beginning underneath the last line that begins with a "#". Lines beginning with "#" are comments and not processed. Do not begin any of the lines defining IP Trunk 3.
Install and configure IP Trunk 3.01 (and later) node TM 3.1 Alarm Notification must be restarted whenever Control Files are changed. 9 If TM 3.1 Alarm Notification is running (a red traffic light is showing on the tool bar), stop it by clicking on the red traffic light on the tool bar. Restart it by clicking on the green traffic light. 10 If TM 3.
Provisioning IP Trunk 3.01 (and later) in TM 3.1 Contents This section contains information on the following topics: "Overview" (page 281) "Add a site and system" (page 282) "Add a site" (page 282) "Change an existing site" (page 284) "Delete a site" (page 286) "Add a system" (page 289) Enter system data Provision the system customer information "Change an existing system" (page 296) "Delete a system" (page 299) "Add an IP Trunk 3.
Provisioning IP Trunk 3.01 (and later) in TM 3.1 For detailed information on configuring a system in TM 3.1, see Telephony Manager 3.1 System Administration (NN43050-601). Add a site and system Before the IP Trunk 3.01 (and later) application can be used, a site, a system, and at least one node must be configured. ATTENTION IMPORTANT! When TM 3.1 is launched, it launches its own FTP service.
Add a site and system 283 2 Click Sites to highlight it. 3 On the menu bar, click Configuration > Add Site. See Figure 68 "Add a Site" (page 283). Figure 68 Add a Site An empty New Site Properties window opens. 4 The site is a single entity, usually in one location. Enter as much information as is required for proper site maintenance. This information typically includes all the information entered into the example shown in Figure 69 "New Site Properties Provisioning a new site" (page 284).
Provisioning IP Trunk 3.01 (and later) in TM 3.1 Figure 69 New Site Properties Provisioning a new site 5 Click OK to save the site information. The TM 3.1 Navigator window opens again, with the new site added. —End— For more information on how to add a site, see Telephony Manager 3.1 System Administration (NN43050-601). Change an existing site Follow the steps in Procedure 40 "Changing an existing site" (page 284) to make changes to an existing site.
Add a site and system 3 285 Right-click the site and from the drop-down list, select Properties. See Figure 70 "Change System Properties" (page 285). Figure 70 Change System Properties Alternatively, from the upper menu, click File > Properties. See Figure 71 "Alternate way to change System Properties" (page 285). Figure 71 Alternate way to change System Properties Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.
Provisioning IP Trunk 3.01 (and later) in TM 3.1 The Site Properties window opens. See Figure 72 "TM 3.1 Site Properties ready to change" (page 286). Figure 72 TM 3.1 Site Properties ready to change 4 Enter the information that is being changed. 5 Click OK to save the site information. —End— Delete a site Follow the steps in Procedure 41 "Deleting a site" (page 286) to delete a site. Procedure 41 Deleting a site Step Action 1 Log in to the TM 3.1 Navigator.
Add a site and system Figure 73 Deleting a site Alternatively, from the upper menu, click Edit > Delete. WARNING Deleting a site also deletes all of its systems. See Figure 74 "Alternative method of deleting a site" (page 288). Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
Provisioning IP Trunk 3.01 (and later) in TM 3.1 Figure 74 Alternative method of deleting a site 4 In the warning box that opens, click Yes to confirm the deletion. See Figure 75 "Confirm deletion" (page 288). Figure 75 Confirm deletion Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
Add a site and system 289 —End— Add a system Though the site has been added, no switches or nodes have been defined. A PBX, also called a system, must be added. For IP Trunk 3.01 (and later), the system usually corresponds to a single PBX. Procedure 42 Adding a system Step Action 1 There are two ways to add a new system in the TM 3.1 Navigator window, as follows: • Right-click the new site. A menu appears, as shown in Figure 76 "New system, add a system by right-clicking" (page 289).
Provisioning IP Trunk 3.01 (and later) in TM 3.1 Figure 77 New system menu bar 2 The system selections that apply to IP Trunk 3.01 (and later) are: • Meridian 1 The IP trunk cards are provisioned as part of the Meridian 1 system, as they are the trunk cards that provide access to the VoIP network and allow interworking with the IP Peer H.323 gateway. • Communication Server 1000M • Generic CS 1000M use IP Peer Networking to inter-operate with the IP Trunk 3.01 (and later) nodes.
Add a site and system 291 Figure 78 Select a system type The New System Properties window opens. This window enables system-wide values to be provisioned. 3 Click the General tab. An empty New System Properties window opens. See Figure 79 "Empty New System Properties window" (page 291).
Provisioning IP Trunk 3.01 (and later) in TM 3.1 is entered automatically. See Figure 80 "New system properties General tab" (page 292). 5 If the system and site are not in the same location, enter the system location and service personnel contact information. Figure 80 New system properties General tab Enter system data 6 Click the System Data tab. Enter the correct machine type, software release, and system parameters. Ensure the correct packages are provisioned.
Add a site and system 293 Figure 81 System Data tab Provision the system customer information 7 Click the Customers tab. An empty Customers window appears. See Figure 82 "Empty Customers window" (page 294). An IP trunk card cannot be provisioned unless it belongs to a system customer. Unless the system is to be administered through this interface, enter only the most basic customer number information. Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.
Provisioning IP Trunk 3.01 (and later) in TM 3.1 Figure 82 Empty Customers window 8 Click the Add button to add a customer. The Add Customer window opens. See Figure 83 "Add Customer window" (page 295). Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
Add a site and system 295 Figure 83 Add Customer window 9 Use the Customer Number drop-down (pull-down) list to select the customer number. Click OK. The New – (Customer x) Properties window opens. See Figure 84 "New (Customer x) Properties General tab" (page 296). Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
Provisioning IP Trunk 3.01 (and later) in TM 3.1 Figure 84 New (Customer x) Properties General tab 10 Enter the Directory Numbers and HLOC obtained from the system provisioning. The Features tab and the Numbering Plans tab are related to system provisioning. They are not used for IP Trunk 3.01 (and later). 11 Click OK. The New – (Customer x) Properties window closes. 12 Click OK in the System Properties window. The window closes and the TM 3.1 Navigator window is displayed.
Add a site and system 297 The window displays two sections – Services and Sites. See Figure 67 "TM 3.1 Navigator" (page 282). 2 In the Site where the system is located, click the system to be changed. 3 Right-click the system and from the drop-down list, select Properties. Alternatively, from the upper menu, click File > Properties. The System Properties window opens. See Figure 85 "System Properties window" (page 297).
Provisioning IP Trunk 3.01 (and later) in TM 3.1 Figure 86 System Properties Customers tab 7 Click Properties. Edit the customer’s information in the Customer Properties window – General, Features, and Numbering Plans tabs. See Figure 87 "Customer Properties window" (page 298). Figure 87 Customer Properties window Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
Add a site and system 8 Click OK to save the customer information. 9 Click OK to save the system information. 299 —End— Delete a system Follow the steps in Procedure 44 "Deleting a system" (page 299) to delete a system. Procedure 44 Deleting a system Step Action 1 Log in to the TM 3.1 Navigator. The window displays two sections – Services and Sites. See Figure 67 "TM 3.1 Navigator" (page 282). 2 In the Sites section, locate and click the system to be deleted.
Provisioning IP Trunk 3.01 (and later) in TM 3.1 Figure 89 Alternative method of deleting a system 4 In the warning box that opens, click Yes to confirm the deletion. See Figure 90 "Confirming the deletion" (page 300). Figure 90 Confirming the deletion —End— Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
Add an IP Trunk 3.01 (and later) node 301 Add an IP Trunk 3.01 (and later) node Follow the steps in Procedure 45 "Adding an IP Trunk 3.01 (and later) node" (page 301) to add an IP Trunk 3.01 (and later) node. Procedure 45 Adding an IP Trunk 3.01 (and later) node Step Action 1 In the TM 3.1 Navigator window, under Services, right-click ITG ISDN IP Trunks. A drop-down list appears. 2 Click Open. See Figure 91 "TM 3.1 Navigator ITG ISDN IP Trunks service" (page 301). Figure 91 TM 3.
Provisioning IP Trunk 3.01 (and later) in TM 3.1 Figure 92 ITG ISDN IP Trunk window 3 From the IP Telephony Gateway – ISDN IP Trunk window menu bar, select Configuration > Node > Add. The Add ITG Node dialog box shown in Figure 93 "Add ITG Node dialog box" (page 302) opens. Figure 93 Add ITG Node dialog box 4 The Add ITG Node window indicates the system type. For IP Trunk 3.01 (and later), select Meridian 1 or MMCS.
Add an IP Trunk 3.01 (and later) node 303 Figure 94 New ITG node General tab 7 8 On the General tab, on the left side of the window, define the following from the drop-down lists: • The TM 3.1 site – the name that was assigned when the site was created. See "Add a site and system" (page 282). • The TM 3.1 system name – the name of the system associated with this site. See "Add a system" (page 289). • The Customer number.
Provisioning IP Trunk 3.01 (and later) in TM 3.1 Figure 95 New ITG Node - Configuration tab A minimum of one IP trunk card, Leader 0, must be defined. This card acts as the leader card on startup and remains as leader until it suffers some sort of failure that would require changeover to the Backup Leader card. TM 3.1 requires that the second card that is provisioned be configured as Leader 1 (Backup Leader). Leader 1 must be configured before any Follower cards are provisioned.
Add an IP Trunk 3.01 (and later) node 305 • Voice LAN gateway IP – the lowest IP address on the TLAN subnet • Card TN – the first three numbers (loop/shelf/card). The exception is the Meridian 1 Option 11C Cabinet and CS 1000M Cabinet which is only "card". • Card density – 24- or 32-port IP trunk card • D-channel – the D-channel on the system. If the D-channel card resides on this IP trunk card, check the DCHIP box. • Protocol – the local protocol. For IP Trunk 3.
Provisioning IP Trunk 3.01 (and later) in TM 3.1 Figure 96 New ITG Node Configuration tab window with Leader 0 provisioned In the window, where the saved card data is displayed, the column width can be increased or decreased to see more or less information. Use the scroll bar slider to see more information hidden from view. If more than one card is listed in the window, selecting a card enables TM 3.1 to display that card’s configuration in the applicable fields in the data entry section.
Add an IP Trunk 3.01 (and later) node 307 Figure 97 New ITG Node, DSP Profile tab, General sub-tab Profile 1 13 Select the applicable DSP Profile information. There are three choices in the DSP Profile drop-down list, as seen in Figure 97 "New ITG Node, DSP Profile tab, General sub-tab Profile 1" (page 307).Click Apply. CAUTION Service Interruption The Media Card 32-port trunk card does not support Profile 3. If Profile 3 is provisioned, the card is unable to make or receive calls.
Provisioning IP Trunk 3.01 (and later) in TM 3.1 Figure 98 DSP Profile sub-tabs ,Profile 1 Options sub-tab TM 3.1 does not permit "V.25 Fax/Modem tone detection enabled" for IP Trunk 3.01 (and later) and ITG Trunk 2.x. This is because the IP trunk cards do not have a mechanism for properly handling modem calls. IP Trunk 3.01 (and later) does not officially support modem calls. The only way modem calls can be made is if G.711 is the first choice for both endpoints.
Add an IP Trunk 3.01 (and later) node 309 Figure 99 New ITG Node, DSP Profile tab, Codec sub-tab WARNING Do not turn off G.711, unless there is no other alternative. Some IP devices use G.723 and G.711, some devices use G.729 and G.711, and some devices support all three codecs. If this node were configured with only G.723, for example, and a device configured with G.729 and G.711 attempted to place a call to this node, the call would fail, because no matching codec exists. Always include G.
Provisioning IP Trunk 3.01 (and later) in TM 3.1 17 Click the Ports tab. See Figure 100 "New ITG Node Ports tab" (page 310). Figure 100 New ITG Node Ports tab 18 This tab is only present for IP Trunk 3.01 (and later) nodes. Use the drop-down list to select the RTP port starting value. There are two options, as follows: • 2300 – default value • 17300 – used for Cisco RTP header compression Alternatively, enter any even-numbered port starting value between 1024 and 65534.
Add an IP Trunk 3.01 (and later) node 19 311 Click OK to complete the node provisioning. The ITG Node Properties window closes. The node data is now displayed in the ITG – ISDN IP Trunk window. See Figure 101 "ITG, ISDN IP Trunk window with new node displayed" (page 311). Figure 101 ITG, ISDN IP Trunk window with new node displayed —End— Edit a node Follow the steps in Procedure 46 "Editing a node" (page 311) to edit a node’s information. Procedure 46 Editing a node Step Action 1 In the TM 3.
Provisioning IP Trunk 3.01 (and later) in TM 3.1 Figure 102 Change node properties 4 Alternatively, right-click the node to be edited, the select Properties from the pop-up menu. See Figure 103 "Alternative method of selecting node to be edited" (page 312). Figure 103 Alternative method of selecting node to be edited 5 The Node Properties window opens. The Node Properties window has six tabs. Select the applicable tab to change the data associated with that section of the node.
Add an IP Trunk 3.01 (and later) node Figure 104 ITG Node Properties General tab 6 To add a new IP trunk card, select the Configuration tab. Select the correct card role for the new IP trunk card. Leader 1 (Backup Leader) must be selected before Follower cards. See Figure 105 "ITG Node Properties Configuration tab" (page 313). Figure 105 ITG Node Properties Configuration tab Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.
Provisioning IP Trunk 3.01 (and later) in TM 3.1 7 Enter the required data. Note that, compared to the Leader 0 configuration • the Management (ELAN network interface) IP address, the Voice (TLAN network interface) IP address, and the Management (ELAN network interface) MAC address have changed • the TN is different (4-0-10) • the first channel ID has changed (1 to 33) See Figure 106 "Leader 1 (Backup Leader) sample configuration" (page 314). Click Add.
Add an IP Trunk 3.01 (and later) node 315 Figure 107 Editing an IP trunk card in a node 9 To delete an IP trunk card from the node, select the desired card and click Delete. The Delete button is greyed out if the card cannot be deleted; for example the Leader 0 card cannot be deleted from a node that still has other IP trunk cards in the node. See Figure 108 "When an IP trunk card cannot be deleted" (page 315).
Provisioning IP Trunk 3.01 (and later) in TM 3.1 If the IP trunk card can be deleted, the print on the Delete button is in black. See Figure 109 "Delete an IP trunk card from a node" (page 316). Figure 109 Delete an IP trunk card from a node Leader 0 and Leader 1 cannot be deleted if there is still a Follower card in the node. Leader 0 cannot be deleted if there is still a Leader 1 card in the node. —End— Delete a node Follow the steps in Procedure 47 "Deleting a node" (page 316) to delete a node.
Add an IP Trunk 3.01 (and later) node 317 Figure 110 Delete a node 2 Alternatively, right-click the node to be deleted, and from the pop-up menu, click Delete. See Figure 111 "Alternative method of deleting a node" (page 317). Figure 111 Alternative method of deleting a node 3 When prompted by the warning box to confirm the node deletion, click Yes to delete the node or click No to cancel the deletion. See Figure 112 "Confirm the node deletion" (page 318).
Provisioning IP Trunk 3.01 (and later) in TM 3.1 Figure 112 Confirm the node deletion If Yes is selected, the node is deleted. See Figure 113 "The node is deleted" (page 318). Figure 113 The node is deleted —End— Define the dialing plan information IP Trunk 3.01 (and later) retains the ability of locally resolving an outgoing dialed number to an IP address of the remote node, using an internally-stored dialing plan table. IP Trunk 3.
Define the dialing plan information 319 Follow the steps in Procedure 48 "Defining the local Dialing plan" (page 322) to define the local dialing plan. Non-Gatekeeper-resolved (local) dialing plan The local dialing plan consists of a number of VoIP destination nodes, such as IP Trunk 3.01 (and later) and ITG Trunk 2.x nodes, and one or more dialing plan entries for each destination node. If the destination node is also provisioned as a node in TM 3.
Provisioning IP Trunk 3.01 (and later) in TM 3.1 The QoS feature only works if the far end is an IP Trunk 3.01 (and later) or an ITG Trunk 2.x node. Additionally, there must be a fallback route for the IP Trunk 3.01 (and later) node to use to reach the far end, such as a PRI trunk. Otherwise, if the QoS level between the two nodes falls below the threshold, calls can no longer be made. If the far end is an IP Peer endpoint and QoS is turned on, calls cannot be made to that node.
Define the dialing plan information 321 5. DSC – Distance Steering Code, part of a Coordinated Dialing Plan (CDP) network. In a CDP network, all numbers must be leftwise-unique as all the systems in that network are viewed by the end user as part of one system. For example, Network ABC has half of the users on a Meridian 1 system and half on a CS 1000E system. The Meridian 1’s extensions start with 5; for example, 5xxxx.
Provisioning IP Trunk 3.01 (and later) in TM 3.1 NPI TON Dialing plan Private Unknown SPN DSC TSC LOC Unknown Unknown SPN DSC TSC LOC Procedure 48 Defining the local Dialing plan Step Action 1 From the IP Telephony Gateway – ISDN IP Trunk window (see Figure 114 "Access the Dialing Plan window" (page 322)), select a node. From the Menu, click Configuration > Dialing Plan. Figure 114 Access the Dialing Plan window The ITG Dialing Plan window opens.
Define the dialing plan information 323 Figure 115 ITG Dialing Plan window 2 To add a new remote node, click Configuration > Add Remote Node. A remote node is an entry in the dialing plan table that represents a device to be reached by provisioning on the IP trunk card. See Figure 115 "ITG Dialing Plan window" (page 323). In IP Trunk 3.01 (and later), an address that does not exist in this provisioning is routed to the Gatekeeper, which, at a minimum, resolves the destination.
Provisioning IP Trunk 3.01 (and later) in TM 3.1 Figure 116 ITG Dialing Plan, Remote Node Properties window, General tab Figure 117 ITG Dialing Plan, Remote Node Properties window, General tab with drop-down list open Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
Define the dialing plan information 325 An existing destination node can also have its properties changed from the drop-down list. See Figure 118 "Change properties on an existing destination node" (page 325). In that example, the properties are being changed for the Johnny Carson node. Figure 118 Change properties on an existing destination node 3 Before entering data (for example, number plan, type of number, digits) for a specific address, the destination node must be selected.
Provisioning IP Trunk 3.01 (and later) in TM 3.1 Figure 119 Selected Remote Node 5 Set the QoS parameter, if desired. Ensure that Fallback to the PBX is in place if QoS levels are not maintained. WARNING If a remote node has IP Peer H.323 Gateway capability, do not use QoS monitoring unless that node is also running IP Trunk 3.01 (and later). No other H.233 Gateways support IP Trunk 3.01 (and later)-formatted QoS. Unless both sides support IP Trunk 3.
Define the dialing plan information 327 Figure 120 Remote Node Properties, Digits dialed tab with no entries Figure 121 Select the destination node Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
Provisioning IP Trunk 3.01 (and later) in TM 3.1 Figure 122 Remote Node Properties, Digits dialed tab with a selected destination node In the example seen in Figure 122 "Remote Node Properties, Digits dialed tab with a selected destination node" (page 328), the dialing plan digits to be added are 613-961-xxxx. 7 Click the ADD button to add this dialing prefix to the list of previously-configured dialing plans displayed in the lower window.
Define the dialing plan information 329 Figure 123 Changing the destination node information Destination not in local TM 3.1 provisioning 9 Select Not Defined on this PC from the Node drop-down list on the ITG Dialing Plan – Remote Node Properties – General tab. See Figure 124 "Destination not in local TM 3.1 provisioning" (page 330). Select H.323 V2 from the Node capability drop-down list if selecting an IP Peer H.323 Gateway. See Figure 125 "Selecting an IP Peer H.323 Gateway" (page 330).
Provisioning IP Trunk 3.01 (and later) in TM 3.1 Figure 124 Destination not in local TM 3.1 provisioning Figure 125 Selecting an IP Peer H.323 Gateway Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
Define the dialing plan information 331 10 Enter the node IP address, select the node capability from the drop-down list, enter a name for the node (optional), set the QoS monitoring option, and enter comments if desired. WARNING If a remote node has IP Peer H.323 Gateway capability, do not use QoS monitoring unless that node is also running IP Trunk 3.01 (and later). No other IP Peer H.323 Gateways support IP Trunk 3.01 (and later)-formatted QoS. Unless both sides support IP Trunk 3.
Provisioning IP Trunk 3.01 (and later) in TM 3.1 Figure 127 Select the Dial Plan 14 Enter all of the numbers that must reach this node. 15 Enter all necessary data. The data includes the digits dialed, the number of digits to delete from the front, and the digit string to insert on the front. 16 Click Add to add the dialing plan to the list in the lower window. All data from the last entry remains in the fields until it is overwritten.
Define the dialing plan information 333 Figure 128 Node with two remote sites Complex dialing plans There is no limit to the number of digit patterns that can terminate on a node. Some dialing plans can be very complex. Figure 129 "Example of a complex dialing plan" (page 334) shows a sample dial plan with a much more complex set of access numbers. This remote node can be reached through LOC (Location codes – ESN UDP dialing), NPA/NXX, and DSC dialing from the local node.
Provisioning IP Trunk 3.01 (and later) in TM 3.1 Figure 129 Example of a complex dialing plan Gatekeeper-resolved endpoints The IP Trunk 3.01 (and later) application has two methods of resolving addresses. The IP Trunk 3.01 (and later) node first checks the dialing plan information using the Address Translation Protocol Module (ATPM). If no match exists, the IP Trunk 3.01 (and later) node checks to see if a Gatekeeper has been provisioned. If a Gatekeeper has been provisioned, the IP Trunk 3.
Define the dialing plan information 335 In the TM 3.1 Navigator window, the Gatekeeper zone can be found by left-clicking on the CS 1000M system, selecting Properties, and clicking on the Network tab. See Figure 130 "Making a Gatekeeper zone" (page 335). When provisioning the applicable devices in TM 3.1, use network zones to coordinate the Gatekeeper information. The Gatekeeper zones were defined on the CS 1000M.
Provisioning IP Trunk 3.01 (and later) in TM 3.1 • In the ITG – ISDN IP Trunk window, as seen in Figure 92 "ITG ISDN IP Trunk window" (page 302), from the menu select Configuration > Node > Gatekeeper. The ITG Node Gatekeeper properties window opens. See Figure 131 "ITG Node Gatekeeper Properties window" (page 336). Figure 131 ITG Node Gatekeeper Properties window • Alternatively, from the ITG Dialing PLan window, click Configuration > Gatekeeper.
Define the dialing plan information 337 Use Gatekeeper Zone from TM 3.1 Navigator option If "Use Gatekeeper zone from TM 3.1 Navigator" was selected from the Gatekeeper Option drop-down list, follow the steps in Procedure 50 "Using a Gatekeeper zone from TM 3.1 Navigator" (page 337). Procedure 50 Using a Gatekeeper zone from TM 3.1 Navigator Step Action 1 Select the "Use Gatekeeper Zone from TM 3.1 Navigator" option if the applicable Gatekeeper or Gatekeepers exist in a zone administered by the TM 3.
Provisioning IP Trunk 3.01 (and later) in TM 3.1 Figure 132 Node Properties Gatekeeper from TM 3.1 3 Click Apply. —End— Use Independent Gatekeeper option If "Use Independent Gatekeeper" was selected from the Gatekeeper Option drop-down list, follow the steps in Procedure 51 "Using the Independent Gatekeeper option" (page 338). Provisioning an independent Gatekeeper requires full manual provisioning.
Define the dialing plan information 339 Figure 133 Gatekeeper Type drop-down list Figure 134 "Properties defined for Primary Gatekeeper" (page 339) shows an example of an independent Gatekeeper that has been provisioned. Figure 134 Properties defined for Primary Gatekeeper Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
Provisioning IP Trunk 3.01 (and later) in TM 3.1 WARNING The H.323 endpoint ID is case-sensitive and alphanumeric string content-sensitive. The data entered in the H.323 ID field must be an exact match to what is provisioned on the Gatekeeper or calls to the Gatekeeper-controlled destinations fail. WARNING When using Gatekeeper zones instead of independent Gatekeepers, if the wrong zone is selected, calls fail because that zone’s Gatekeepers have not been provisioned to handle calls from this gateway.
Define the dialing plan information 341 —End— From the ITG Dialing Plan window, confirm that all required remote end-points have been provisioned. Download the dialing plan provisioning to the IP trunk cards. For more information on downloading the dialing plan, see "Transmit configuration data" (page 350). Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
Provisioning IP Trunk 3.01 (and later) in TM 3.1 Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
TM 3.1 OA and M using TM 3.1 applications Contents This section contains information on the following topics: "Introduction" (page 344) "TM 3.
TM 3.1 OA and M using TM 3.
TM 3.1 OA and M procedure summary 345 Delete a node To delete an IP Trunk 3.01 (and later) node, perform the following steps in Procedure 52 "Deleting an IP Trunk 3.01 (and later) node" (page 345). Procedure 52 Deleting an IP Trunk 3.01 (and later) node Step Action 1 Double-click the ITG ISDN IP Trunk icon from the Services folder in the TM 3.1 Navigator window. 2 Right-click the node to be deleted in the upper portion of the IP Telephony Gateway - ISDN IP Trunk window.
TM 3.1 OA and M using TM 3.1 applications 3 The ITG Node Properties window appears. 4 Select the Card Configuration tab. 5 Select the IP trunk card to delete from the list. 6 Click the Delete button. 7 Click OK. —End— Database locking All node and card properties are stored in a single TM 3.1 database. When Node or Card Properties are opened, the data for a given node (including card properties) is then locked.
TM 3.1 OA and M procedure summary 347 ITG Card Properties window To display the property sheet of an IP trunk card, double-click an IP trunk card in the ITG Main window. The property sheet has a tree control on the left-hand side of the window, enabling control of the IP trunk card or any of the DSPs. Different property sheets appear for IP trunk cards, DSPs, and D-channels by clicking on the required item in the tree. ITG determines the number of DSPs at run-time when the property sheet opens.
TM 3.1 OA and M using TM 3.1 applications • Use the Set Node Time to change the time and date on the node. The node time is updated every minute while the Card Properties is open. • Use the Open log file, Open trace file, and the Open OM file buttons to view the related files. These files are transferred from the card using FTP and displayed in Microsoft WordPad on the PC. • The trace file is for expert level debugging (trace must be turned on through the command line).
TM 3.1 OA and M procedure summary 349 ITG Card Properties Configuration window The Configuration window for the IP trunk card contains the information shown in Figure 139 "ITG Card Properties Configuration tab" (page 349). The ITG Card Properties Configuration window provides read-only information. Go to the Node Properties Card Configuration window to change this data. The Software version is retrieved from the card through the MIB. If the card is not responding, the value is set to "Unknown".
TM 3.1 OA and M using TM 3.1 applications D-channel maintenance If the IP trunk card has D-channel hardware, the tree on the left side of the window contains the D-channel. click the D-channel and the D-channel Maintenance window appears. This window allows D-channel maintenance operations to be performed. The commands are sent to the card through SNMP. The menu items are not context-sensitive. For example, it is possible to try to enable an enabled D-channel. Transmit configuration data TM 3.
TM 3.1 OA and M procedure summary 3 351 Click Start transmit. See Figure 140 "ITG Transmit Options window" (page 351). —End— TM 3.1 transfers the data to the appropriate cards using FTP. Figure 140 ITG Transmit Options window The following comments apply to the ITG Transmit Options: • To transmit Node Properties (BOOTP.1), select the node in the top window. • Node Properties (BOOTP.
TM 3.1 OA and M using TM 3.1 applications • For the Card Properties (CONFIG1.INI) to take effect, the IP trunk cards must be re-enabled. • To transmit the Dialing Plan (DPTABLE.1), select the node in the top window or select each individual card below. In either case, it is necessary to select to transmit to the entire node. • The Dialing Plan (DPTABLE.1) can be transmitted to the IP trunk cards while the cards are enabled and takes effect immediately. • The Dialing Plan (DPTABLE.
Add an IP Trunk 3.01 (and later) node on TM 3.1 by retrieving an existing node 353 Add an IP Trunk 3.01 (and later) node on TM 3.1 by retrieving an existing node After an IP Trunk 3.01 (and later) node is manually configured and installed, that node can be added to another TM 3.1 PC by retrieving the configuration data from the existing IP Trunk 3.01 (and later) node. Use this optional procedure to perform the following actions: • To combine existing IP Trunk 3.
TM 3.1 OA and M using TM 3.1 applications 2 In the IP Telephony Gateway - ISDN IP Trunk window, select the drop-down list Configuration > Node > Add. The ADD ITG Node dialog box appears. 3 Click the second option Retrieve the active configuration from an existing node. Leave "Meridian 1" as the default "System type". Click OK. The Retrieve ITG Node window appears. See Figure 142 "Retrieve ITG node window" (page 354).
Retrieve and add an IP Trunk 3.01 (and later) node for maintenance and diagnostic purposes 355 The Retrieve control dialog box displays the results of the retrieval. The node properties, card properties and dialing plan are retrieved from the Leader card. 8 Click Close when the download is complete. 9 Refresh the card status and check that the cards in the new node are responding.To determine the IP trunk card status, in the IP Telephony Gateway – ISDN IP Trunk window click View > Refresh > All.
TM 3.1 OA and M using TM 3.1 applications Add the dummy node manually or by retrieving the IP Trunk 3.01 (and later) node configuration data from an existing IP Trunk 3.01 (and later) node. The site name, Meridian 1 system name, and Meridian 1 customer number must exist in the TM 3.1 Navigator before a new IP Trunk 3.01 (and later) node can be added. The following is the recommended method to create the "dummy" IP Trunk 3.01 (and later) node. Procedure 57 Creating a dummy IP Trunk 3.
Retrieve and add an IP Trunk 3.01 (and later) node for maintenance and diagnostic purposes 357 Retrieve IP Trunk 3.01 (and later) configuration information from the IP Trunk 3.0 (and later) node Use the optional Procedure 58 "Retrieving the IP Trunk 3.01 (and later) configuration data from the IP Trunk 3.01 (and later) node" (page 357) in the following situations: • when adding an IP Trunk 3.01 (and later) node on TM 3.1 by retrieving an existing node • when it is known that the IP Trunk 3.
TM 3.1 OA and M using TM 3.1 applications 5 Select Prompt user for community name if required. 6 Click the Start retrieve button. —End— Monitor the status of the retrieval in the Retrieve control box. The retrieved Node Properties, Card Properties, and Dialing Plan over-writes the existing TM 3.1 IP Trunk 3.01 (and later) configuration data for the respective node or IP trunk card. When a dialing plan table is retrieved, TM 3.1 IP Trunk 3.
Retrieve and add an IP Trunk 3.01 (and later) node for maintenance and diagnostic purposes 359 Figure 144 Generate OM Report b. To generate a report immediately, click Generate OM Report. TM 3.1 prepares the report and displays the information in a .csv spreadsheet format. c. To schedule a report, click Schedule OM Report. A Scheduling window appears (see Figure 145 "OM Report scheduling window" (page 359)). Fill in the fields to schedule the report and define the times and information.
TM 3.1 OA and M using TM 3.1 applications —End— Additional administrative functions In addition to the administrative functions performed in MAT Navigator, there are other functions performed in MAT, including: • MAT Installation • MAT User Administration and Security • Alarm Notification • Back up and Restore operations MAT Installation To install the ITG application in MAT, use the Applications to Install window. The IP Telephony Gateway option must be selected.
Additional administrative functions 361 Figure 146 MAT user template Backup and restore operations The Media Card 32-port and ITG-Pentium 24-port trunk cards support backup and restore procedures for critical configuration data. If a failed IP trunk card is replaced with a spare, the dialing plan tables, DSP configuration, passwords, and other configuration data are restored from the TM 3.1 PC. The TM 3.1 application has a backup and restore procedure for all data downloaded to and from the IP trunk card.
TM 3.1 OA and M using TM 3.1 applications For more information about Alarm Notification, please refer to Alarm Management in Telephony Manager 3.1 System Administration (NN43050-601). System commands LD 32 The following system administration commands can be performed in LD 32: • "Disable the indicated IP trunk card" (page 363). The IP trunk card must be disabled before card properties can be transmitted from the TM 3.1 IP Trunk 3.01 (and later) application to the IP trunk card.
System commands LD 32 363 Table 52 LD 32 IP Trunk 3.01 (and later) maintenance commands Command Description DISC l s c Disable the indicated card, where: l = loop, s = shelf, c = card DISI l s c Disable the indicated card when idle, where: l = loop, s = shelf, c = card Use the DISI command to disable the IP trunk card instead of the DISC command. The disablement of the IP trunk card is indicated by the NPR011 message.
TM 3.1 OA and M using TM 3.
System commands LD 32 STAT l s c u Display the status of the indicated ITG port, where: l = loop, s = shelf, c = card, u = unit. Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
TM 3.1 OA and M using TM 3.1 applications Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
OA and M using the ITG shell CLI and overlays Contents This section contains information on the following topics: "Introduction" (page 368) "ITG Shell OA and M procedure summary" (page 368) "Access the ITG shell through a maintenance port or Telnet" (page 368) "Connect a PC to the card maintenance port" (page 369) "Telnet to an IP trunk card through the TM 3.
OA and M using the ITG shell CLI and overlays "Disable an indicated IP trunk card port" (page 364) "Enable an indicated IP trunk card" (page 364) "Enable an indicated IP trunk card port" (page 364) "Display IP trunk card ID information" (page 364) "Display IP trunk card status" (page 364) "Display IP trunk card port status" (page 364) Introduction This chapter explains how to perform IP Trunk 3.
Access the ITG shell through a maintenance port or Telnet 369 • Access the ITG shell from the TM 3.1 PC. Refer to "Telnet to an IP trunk card through the TM 3.1 PC" (page 370) for details. Connect a PC to the card maintenance port Follow the steps in Procedure 60 "Connecting a PC to the IP trunk card maintenance port" (page 369) to connect a PC to the IP trunk card maintenance port.
OA and M using the ITG shell CLI and overlays —End— Only one person can use the ITG shell at a time. Any session, local or Telnet, can be overridden by a second session. The second user receives a warning before the login and must confirm to complete the login. There is a 20-minute Telnet shell activity time-out limit. Telnet to an IP trunk card through the TM 3.1 PC Follow the steps in Procedure 61 "Telnetting to an IP trunk card through the TM 3.
Access the ITG shell through a maintenance port or Telnet 371 Figure 147 Select card and open Telnet session 4 Perform the following action to increase the Telnet terminal buffer size to capture multiple screens of data from the IP trunk card: From the Telnet "Terminal" menu, select "Preferences". Set the Buffer Size to a larger value, such as 1000, and click "OK". The Telnet buffer size has to be only once, because Telnet preferences are automatically saved.
OA and M using the ITG shell CLI and overlays Procedure 62 Changing the default ITG shell password Step Action 1 From the ITG shell use the command shellPasswordSet to change the default user name and password for Telnet to ITG shell and FTP to the IP trunk card file system. The default user name is itgadmin and the default password is itgadmin.
Access the ITG shell through a maintenance port or Telnet 373 Example of the Media Card 32-port trunk card prompt screen: Example of the ITG-Pentium 24-port trunk card prompt screen: If the prompt "vxWorks login:" appears, the BIOS ROM prompt has been lost and the card must be reset again. At the BIOS ROM shell prompt enter the following command: -> nvramClear This command clears the user configured password, the leader flag, and the IP configuration information from the NVRAM.
OA and M using the ITG shell CLI and overlays When prompted to login, enter the default username and password as: VxWorks login: itgadmin Password: itgadmin ITG> 6 If this card is Leader 0, use the setLeader command: ITG> setLeader xxx.xxx.xxx.xxx, yyy.yyy.yyy.yyy, zzz.zzz.zzz.zzz and press Enter. where • xxx.xxx.xxx.xxx is the IP address of the ELAN network interface on Leader 0. • yyy.yyy.yyy.yyy is the gateway IP address for the ELAN network interface on Leader 0. If the TM 3.
Access the ITG shell through a maintenance port or Telnet 375 Reset the operational measurements This command resets all operational measurement (OM) parameters collected after the last log dump. At the ITG shell prompt, type: resetOM Display the number of DSPs At the ITG shell prompt, type the following command to display the number of DSPs on the IP trunk card: DSPNumShow Display IP Trunk 3.
OA and M using the ITG shell CLI and overlays Card Mode: Normal Codecs: G.711 mu-law (default), G.711 a-law, G.729AB, G.729A EC Tail Length: Value from TM 3.1-32 DCHIP IP: 47.11.217.21 DCH Num: 10 DCH ON Card: YES (version 3.
Access the ITG shell through a maintenance port or Telnet 377 The time to re-register is based on the clock on the Leader 0 IP trunk card. If the clocks on the Leader 1 and Follower IP trunk cards are out of synchronization with the Leader 0 clock, the time to re-register might be incorrect. The time that the next re-register will occur is always correct on the Leader 0 IP trunk card. The following is an example of the output of the gkshow command when there is only a Primary Gatekeeper.
OA and M using the ITG shell CLI and overlays For security reasons, there is no generic FTP client on the IP trunk card. A DIR or PWD (Print Working Directory) command cannot be performed on the FTP host. The BOOTP.1 file (transferred by the "bootPFileGet" and "bootPFilePut" commands) contains node properties information. The DPTABLE.1 file (transferred by the "DPAddrTGet" and "DPAddrTPut" commands) contains the TM 3.1 IP Trunk 3.01 (and later) dialing plan information. The CONFIG1.
Access the ITG shell through a maintenance port or Telnet 379 Configuration file transfer Use these commands to backup and restore files when the preferred method, the TM 3.1 PC, is not available.
OA and M using the ITG shell CLI and overlays Obtain the new IP trunk card software from the Nortel web site, or obtain a PC Card containing the newest software. Follow the steps in Procedure 64 "Downloading IP trunk card software from the internet" (page 380) to download the IP trunk card software from the Nortel web site. Procedure 64 Downloading IP trunk card software from the internet Step Action 1 Download the IP trunk card software from the internet to a PC hard drive.
Access the ITG shell through a maintenance port or Telnet 381 3 Use the swDownload command to copy the software from the PC Card to the IP trunk card flash ROM device, using the FTP client and the FTP host on the IP trunk card. The host name parameter in this command is the ELAN network interface IP address of the IP trunk card. The user name and password are the same as those configured for the ITG shell.
OA and M using the ITG shell CLI and overlays 3 Press Enter. Monitor the status of the software upgrade and check that the upgrade correctly finishes. Observe any error messages that indicate problems with parameters or syntax. 4 When the new software has downloaded into the flash ROM device, reboot the IP trunk card to use it. Use the cardReset command or press the reset button on the IP trunk card faceplate.
Access the ITG shell through a maintenance port or Telnet 383 —End— Restore from the CLI To restore configuration when the TM 3.1 PC is not available to retransmit the IP Trunk 3.01 (and later) configuration data, use the appropriate "Put" commands. Follow the steps in Procedure 68 "Restoring from the CLI" (page 383) to perform a restore from the CLI.
OA and M using the ITG shell CLI and overlays The SNMP community names can be read from the IP trunk card in two ways: • Reset the IP trunk card and monitor the startup messages. Use the configFilePut command to backup the Card Properties file to an FTP host. Use a text editor to open the Card Properties file and read the community name. • Alternatively, use the SNMP client on the TM 3.1 PC to connect to the FTP host on the IP trunk card. Log in using the ITG shell user name and password.
System commands LD 32 385 The card reset button is only available in the TM 3.1 IP Trunk 3.01 (and later) application when the IP trunk card is disabled. Disabling the IP trunk card in LD 32 does not disable the Active Leader or Backup Leader functions. • "Disable the indicated IP trunk card when idle" (page 363). This temporarily prevents the IP Trunk 3.01 (and later) node from seizing the port from incoming calls. • "Disable an indicated IP trunk card port" (page 364).
OA and M using the ITG shell CLI and overlays Command Function ENLC l s c Enable the described IP trunk card, where: l = loop, s = shelf, c = card ENLU l s c u Enable the described unit, where: l = loop, s = shelf, c = card, u = unit IDC l s c Print the Card ID information for the described IP trunk card, where: l = loop, s = shelf, c = card STAT l s c Print the system software status of the indicated IP trunk card where: l = loop, s = shelf, c = card STAT l s c u Print the system software s
System commands LD 32 DISU l s c u 387 Disable the indicated IP Trunk 3.01 (and later) unit (port), where: l = loop, s = shelf, c = card, u = unit Enable an indicated IP trunk card port To enable an indicated IP trunk card port in LD 32, use the following command: ENLU l s c u Enable the indicated IP Trunk 3.
OA and M using the ITG shell CLI and overlays Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
Maintenance Contents This section contains information on the following topics: "Introduction" (page 390) "IP Trunk 3.01 (and later) IP trunk card alarms" (page 391) "System level maintenance" (page 396) "Access the IP trunk card" (page 396) "IP trunk card LD commands" (page 396) "TM 3.
Maintenance "IP trunk card" (page 420) "TM 3.
IP Trunk 3.01 (and later) IP trunk card alarms 391 • "Fault clearance procedures" (page 421) – potential system faults and how to correct them. IP Trunk 3.01 (and later) IP trunk card alarms This section describes the alarms, messages and codes output by the ITG-Pentium 24-port and Media Card 32-port trunk cards. All IP Trunk 3.01 (and later) IP trunk card alarms shown in Table 55 "IP Trunk 3.01 (and later) alarms" (page 392) on Table 55 "IP Trunk 3.
Maintenance Up to eight destination IP addresses can be configured to which these alarms can be sent. The same addresses must be configured for all cards on the same node. Table 55 "IP Trunk 3.01 (and later) alarms" (page 392) lists SNMP alarms by severity. Table 55 IP Trunk 3.01 (and later) alarms Alarm Description Fault Clearing Action Alarm Clearance – For information purposes These alarms indicate the clearance of an error condition. As such, no user intervention is required.
IP Trunk 3.01 (and later) IP trunk card alarms 393 Alarm Description Fault Clearing Action ITG0203 Fallback to PSTN activated. Bad network condition. This alarm indicates a QoS fallback. Recurrent QoS fallback and recovery can indicate network faults, far-end IP Trunk 3.01 (and later) node failure or network QoS configuration errors. ITG0204 DSP device reset. A DSP failed to respond and was reset. If this alarm occurs repeatedly on the same DSP, replace the card.
Maintenance Alarm Description ITG0301 DSP channel not responding. DSP These DSP errors are not cleared channel is disabled. Card sends automatically. If the occurs frequently, message to the system to busy the replace the card. trunk. This ensures that user’s calls go through on good DSPs. ITG0302 DSP device failure. Operating on reduced capacity. DSP failed to return to normal service. Hardware fault cleared by automatic trap. ITG0303 DSP subsystem failure. Initiating card reboot.
IP Trunk 3.01 (and later) IP trunk card alarms 395 Alarm Description ITG0402 Ethernet voice port failure. TLAN subnet problem or cable removed. ITG0403 ELAN network interface failure. ELAN subnet problem or cable removed. ITG0404 Cannot open address translation file. File does not exist or is corrupted. ITG0406 Startup memory allocation failure. Card reboot initiated. Indicates insufficient memory installed. ITG0407 Cannot get response from Leader card. ITG0408 Bad address translation file.
Maintenance Alarm Description ITG0451 D-channel hardware failure. Associated channels busied out. ITG0452 System messaging failure. Unable to process calls. ITG0453 Cannot open Gateway DN file ITG0454 Cannot open Gatekeeper password file. ITG0455 Bad Gatekeeper configuration file. Reverting to previous version, if any. ITG0456 Incorrect gateway password. Calls to/from gateway rejected by the Gatekeeper.
System level maintenance 397 Table 56 Supported LD 32 commands Command Function DISC l s c Disable the indicated IP trunk card, where: l = loop, s = shelf, and c = card. DISI l s c Disable the indicated IP trunk card when idle, where: l = loop, s = shelf, and c = card. DISU l s c u Disable the indicated unit, where: l = loop, s = shelf, c = card, and u = unit. ENLC l s c Enable the indicated IP trunk card, where: l = loop, s = shelf, and c = card.
Maintenance Command Function LDIC l s c u List the number of days since the last incoming call on the indicated trunk, where: l = loop, s = shelf, c = card, and u = unit. STAT l s c Print the system software status of the indicated IP trunk card, where: l = loop, s = shelf, and c = card. RSET l s c u Reset thresholds for the indicated trunk, where: l = loop, s = shelf, c = card, and u = unit.
System level maintenance 399 Table 58 MSDL commands Command Description ENL DCH num Enables the D-channel. DIS DCH num Disables the D-channel. STAT DCH num Displays the state of the D-channel application. RLS DCH num Releases the D-channel. EST DCH num Establishes multiple frame operation on the D-channel. Simple Network Management Protocol (SNMP) An SNMP stack sends appropriate traps to TM 3.1 or an SNMP manager.
Maintenance Command Function Card Enabled The card has been enabled by the system. Channel Enabled A given channel has been enabled by the system. D-channel Released The D-channel link has been released. Alternate Routing QoS prevents calls from being completed. Cause value "Temporary failure" is sent to the system for Fallback to PSTN. Normal Service Restored Network performance is confirmed as acceptable and IP telephony has been restarted.
ITG shell command set 401 Table 61 General purpose commands Command Description cardReset Perform a warm reboot of the IP trunk card. The card has to be in the OOS state to use this command. itgCardShow Show card information. ldrResTableShow Show Backup Leader and Followers for a given Leader. itgChanStateShow Show state of channels (for example, busy or idle). h323SessionShow Show H.323 session information for each channel. itgMemShow Show memory usage.
Maintenance Command Description displayClear Clear the maintenance display on the faceplate of the IP trunk card. shellPasswordSet Change the default ITG shell password. emodelSim Allow user to interactively determine QoS score. itgHelp Show the complete command list. "?" also shows the list. itgCallTrace Shows call trace log. tLanSpeedSet Set the speed of the TLAN network interface. tLANDuplexSet Set the duplex mode of the TLAN network interface. logout Exit the shell.
ITG shell command set Command Description routeDelete "IP address", "IP Gateway" Delete a route from the routing table. 403 Example: ITG> routeDelete "47.23.34.19", "47.23.34.1" mRouteDelete "IP address", "Subnet mask", , Delete a route matching the ToS value and flags. Currently, "flags" should be set to "0". Example: ITG> mRouteDelete "47.23.34.19", "255.255.255.0", 4, 0 routeShow Display the current host and network routing entries.
Maintenance Command Description bootPFileGet hostname, username, password, directory path, filename Update the bootptab file on the IP trunk card with the bootptab file on the indicated host, account, and path. The bootpFileGet task on the host starts an FTP session with the given parameters and downloads the file to the flash file system.
ITG shell command set 405 Command Description Example: ITG> currLogFilePut "ngals042", "anonymous", "guest", "/currDir", "logFile" prevLogFilePut hostname, username, password, directory path, filename The logFilePut task on the host starts an FTP session with the given parameters and downloads the IP trunk card’s previous log file to the indicated location on the host.
Maintenance Command Description setLeader IP address, IP gateway, subnet mask The one command that does all the necessary actions to make a Leader. Sets IP address, gateway, subnet mask, boot method to static, and Leader bit in NVRAM. Example: ITG> setLeader "47.23.45.67", "47.0.0.1", "255.255.240.0" clearLeader The one command that does all the necessary actions to clear the Leader information in NVRAM and set the boot method to use BOOTP, thus, making the card a Follower.
IP trunk card self-tests 407 Table 65 Operational Measurement command Command Description resetOM This command returns all Operational Measurement parameters collected since last log dump, including: • outgoing calls tried • outgoing calls completed • incoming calls tried • total voice time • total fax time • outgoing packets discarded • incoming packets out–of–sequence • average packet delay • average packet loss • number of Fallback-to-PSTN calls Table 66 DCHIP-only commands Comman
Maintenance Additionally, the IP trunk card has a four-character LED dot matrix display on the faceplate for the purpose of providing status information during maintenance operations. At power-up and during diagnostic tests, this display provides a visual indication of the status of the self-test and an indication of the first failure detected.
Outgoing calls attempted/completed mismatch 409 Base code self-test The IP trunk card base code performs the following tests: • flash integrity test • PGA read/write test • PC Card controller test (also tests the PCI bus) • timer and DMA tests • DSP test Field-Programmable Gate Array (FPGA) testing Before communicating with the system, the 8051XA controller downloads FPGA and performs tests to check correct programming of the FPGA.
Maintenance still takes finite time for messages to propagate. However, this is usually not a factor. The main reason for attempted call mismatches are: • The outgoing side records every SETUP message sent to it by the PBX. The incoming side records SETUP messages sent to the PBX by the ITG card. Every call that is cleared quickly or blocked by fallback skews the results. IP Trunk 3.01 (and later) upgrades Several different types of upgrades can be required for the IP Trunk 3.
IP Trunk 3.01 (and later) upgrades 411 using a modem, an FTP session, or TM 3.1. Patch files are stored in Flash memory and are loaded into DRAM memory. Once a patch is in DRAM memory, it can be activated, deactivated, and its status can be monitored. Perform the following tasks prior to loading a patch: 1. Check that the patch matches the platform’s CPU type. 2. Check the loadware version on the card. 3. Block the installation if there is a mismatch.
Maintenance Command Description pins Puts a patch that has been loaded into memory (using the pload command) into service. This command activates a patch. If issued successfully, the pins command indicates that global procedures, functions, or areas of memory are affected by the patch. The technician is then prompted and has the choice to proceed or not to proceed.
IP Trunk 3.01 (and later) upgrades Command Description pstat Gives summary status information for one or all loaded patches. 413 For each patch, the following information is displayed: patch handle, filename, reference number, whether the patch is in-service or out-of-service, the reason why the patch is out-of-service (if applicable), and whether the patch is marked for retention or not.
Maintenance Description Command pnew The pnew command has no parameter(s). Patch Directories There are two patch directories on an IP trunk card: 1. /C:/u/patch This is the default directory for patch files. Patch files should be copied to this directory. 2. /C:/u/patch/reten Use this directory to store patch retention control files. Do not use this directory to store patches and do not remove files from this directory.
IP Trunk 3.01 (and later) upgrades 415 click the Configuration tab. "S/W version" displays the current software version as read from the IP trunk card. 4 From the main card list view, select the cards to be upgraded. Upgrade all cards in the node together, unless installing a spare card that has older software. 5 To disable all IP trunk cards to be upgraded, use one of the following: • the LD 32 DISI command from the TM 3.1 Maintenance windows • the TM 3.
Maintenance the TM 3.1 IP Trunk 3.01 (and later) status refresh (that is, disabled: active; disabled: backup: disabled). 13 These cards should remain in the disabled state after the upgrade so the technician can issue a "Reset" command from the Maintenance menu or the Maintenance tab in the ITG Card Properties window to each card to reboot them. Alternatively, reset the cards by pressing the Reset button on the card faceplate using a pointed object.
Replace an IP trunk card 3 417 If the card to be replaced is an ITG 8-port trunk card, disconnect the TLAN Ethernet cable from the faceplate of the bad card. Label the cable to identify it as the TLAN Ethernet connection so it can later be reattached to the replacement card. If the card to be replaced is an ITG 8-port trunk card or a ITG-Pentium 24-port trunk card, disconnect the TLAN Ethernet cable from the I/O cable.
Maintenance When the IP trunk cards are installed, the red LED on the faceplate is lit if: the card has rebooted; the card is active but there are no trunks configured on it, or the card is active and has trunks, but the trunks are disabled. If the LED does not follow the pattern described (for example, remaining continuously flashing or weakly lit), replace the card. Observe the IP trunk card Faceplate Maintenance display to see startup self-test results and status messages.
Replace an IP trunk card 419 —End— Determine IP trunk card software release Follow the steps in Procedure 71 "Determining the IP trunk card software release" (page 419) to determine the current software release on the IP trunk card. Procedure 71 Determining the IP trunk card software release Step Action 1 In the IP Telephony Gateway window in TM 3.1, double-click the replacement IP trunk card to open the Card properties window.
Maintenance Click the Start Transmit button. The transmission status is displayed in the "Transmit control" box. Confirm the card properties and dialing plan are transmitted correctly. 4 When the transmission is complete, click the Close button. 5 Use the LD 32 ENLC command to re-enable the IP trunk card. 6 In the IP Telephony Gateway main window, select menu View > Refresh. The card status displays "Enabled.
Fault clearance procedures 421 Fault clearance procedures This section provides possible solutions to such faults as the following: • DSP failure • card failure • DCH failure • DCH link failure • PC Card failure • DCHIP card failure • power loss DSP failure If one of the DSPs does not respond, a DSP reset is automatically initiated by the host and an dspResetAttempted alarm is raised.
Maintenance Remove the card for two to three seconds and then re-seat it in the IPE shelf. If the failure continues, replace the card. DCH failure There are three types of DCH failure which can affect the IP trunk card: 1. DCH link failure (DCH releases) 2. PC Card failure 3. DCH card failure When the DCH fails (with no backup DCH), the following occurs: • Established calls are maintained. • Transient calls are dropped. • No new incoming calls are assigned to trunks associated with that DCH.
Media Card 32-port trunk card faceplate maintenance display codes 423 Socket Services are responsible for card insertion and removal. There is a single interruption shared for insertion and removal events and a single interruption for device-specific interruptions. Socket Services identify which socket originates the interruption and sends the interruption to the Card Services interruption handler.
Maintenance Table 68 Media Card 32-port trunk card faceplate maintenance display message summary Code Description T:00 Initialization T:01 Testing internal RAM T:02 Testing ALU T:03 Testing address modes T:04 Testing watchdog T:05 Testing 8051 co-processor T:06 Testing timers T:07 Testing external RAM T:08 Testing dongle T:09 Programming timeswitch FPGA T:10 Programming ISPDI FPGA T:11 Testing host dual port RAM T:12 Testing DS-30 dual port RAM T:13 Testing SEEPROM T:14 Bo
ITG-Pentium 24-port trunk card faceplate maintenance display codes 425 Code Description LDR Card is running active leader tasks. BLDR Card has detected existing Active Leader and is running Backup Leader tasks, or the card is configured as a Leader and is missing its node properties. Transmit node properties from TM 3.1. FLR Card has detected the Active Leader and is running Follower tasks. In addition, if the IXP encounters any failures during its initialization, an H:XX error code displays.
Maintenance If self-tests T:10-T:17 fail, the display contains the failure message for three seconds and the ITG-Pentium 24-port trunk card goes on to the next test. If more than one test fails, the message displayed indicates the last failure.
ITG-Pentium 24-port trunk card faceplate maintenance display codes Normal Code T:20 Fault Code 427 Description Card LAN enabled, waiting for Request Config Message. IP trunk card is looking for an active leader by sending BOOTP requests on the ELAN subnet. If no BOOTP response is received on the ELAN subnet, Leader 0 times out first and starts active leader tasks.
Maintenance System performance under heavy load When the system and IP Trunk 3.01 (and later) are carrying traffic approaching the maximum sustained levels, there can be short bursts of traffic exceeding the maximum threshold level. This is caused by the randomness of call starts. When the maximum threshold levels are exceeded, error messages are printed to the system screen. In extreme cases, it can cause call loss.
System performance under heavy load 429 over-tasked. To resolve this situation, separate the D-channel and IP functions; that is, have the DCHIP Leader reside on a Follower card. • If none of these apply, consider splitting the IP Trunk 3.01 (and later) node into two or more DCHIP Leader and Follower groups. This reduces the workload of the DCHIP Leader and allows the Leader to carry less of the signaling traffic.
Maintenance Message: BUG085 Description The system detected an invalid switchhook state when the call was in the RINGING state. The switch-hook state should be off-hook; if it is not, the error message is generated. Normal cause The causes can include debounce error and guard timer violation. Normal resolutions The problem is usually self-healing; the call recovers and proceeds. Occasionally, if the problem is related to high traffic levels, the specific call could fail.
Appendix A Patches and advisements Contents This section contains information on the following topics: "Introduction" (page 431) Introduction This appendix describes the following patches for IP Trunk 3.0 and IP Trunk 3.01: MPLR17662, MPLR17346, MPLR18142, and MPLR18157. IP Trunk 3.00.53 patches The patches applicable to IP Trunk 3.00.53 that are mandatory to interwork with IP Trunk 3.01 are: • MPLR17662 • MPLR17346 MPLR17662 When upgrading an existing network of IP Trunk 3.00.
Appendix A Patches and advisements IP Trunk 3.01.22 patches The patches applicable to IP Trunk 3.01.22 are: • MPLR18142 • MPLR18157 MPLR18142 FIN_WAIT_2 socket loss and related IXP restart avoidance. MPLR18157 TLAN subnet info not recognized if QSIG uses 7-bit channel address. Interoperability with IP Trunk 3.01 (MPLR17662 patch) When upgrading an existing network of IP Trunk 3.0 (3.00.53) nodes to IP Trunk 3.01 (3.01.22), calls from the IP Trunk 3.0 node to the IP Trunk 3.
Interoperability with IP Trunk 3.01 (MPLR17662 patch) 433 Since there is no adverse effect caused by installing the patch on IP Trunk 3.0, and upgrading a network on a node-by-node basis simplifies maintenance greatly, Nortel recommends that the second alternative be used. The nodes must use the Nortel H.323 Interoperability format or use a Gatekeeper to resolve destinations.
Appendix A Patches and advisements Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
Appendix B Cable description and NT8D81BA cable replacement Contents This section contains information on the following topics: "Introduction" (page 431) "NTMF94EA ELAN, TLAN and Serial Port cable" (page 436) "NTCW84KA ELAN, TLAN, DCH and serial cable" (page 437) "NTAG81CA Faceplate Maintenance cable" (page 439) "NTAG81BA Maintenance Extender cable" (page 440) "NTCW84EA DCH PC Card pigtail cable" (page 441) "NTMF04BA MSDL extension cable" (page 443) "NTCW84LA and NTCW84MA upgrade cables" (page 444) "Pr
Appendix B Cable description and NT8D81BA cable replacement NTMF94EA ELAN, TLAN and Serial Port cable The NTMF94EA cable connects the I/O connector on Meridian 1 Option 11C Cabinet, CS 1000M Cabinet, or Large Systems to the ELAN network interface, TLAN network interface, and one RS-232 port. See Figure 109 "Delete an IP trunk card from a node" (page 316) and Table 71 "NTMF94EA ELAN, TLAN, and Serial Port cable connections" (page 436).
NTCW84KA ELAN, TLAN, DCH and serial cable I/O Panel: P1 Signal Name P2, P3, P4 Color P1-48 RXDB- P3-6 Orange/White P1-49 TXDB- P3-2 White/Orange P1-18 RX+ P4-3 Green/White P1-43 RX- P4-6 White/Green P1-19 TX+ P4-1 Orange/White P1-44 TX- P4-2 White/Orange 437 NTCW84KA ELAN, TLAN, DCH and serial cable The NTCW84KA cable connects the I/O connector on Cabinet or Large systems to the ELAN and TLAN network interfaces with one RS-232 port and D-channel signalling.
Appendix B Cable description and NT8D81BA cable replacement Figure 149 NTCW84KA ELAN, TLAN, DCH, and serial cable Table 72 NTCW84KA ELAN, TLAN, DCH, and Serial I/O cable connections I/O Panel: P1 Signal Name P2, P3, P4, P5 Color P1-21 BSOUTB- P2-2 Red P1-22 BDTRB- P2-4 Green P1-25 SHLD GND P2-5 Brown P1-45 BSINB- P2-3 Blue P1-46 BDCDB- P2-1 Orange P1-47 BDSRB- P2-6 Yellow P1-5 P2 SHLD GRND P1-6 P2 SHLD GRND P1-8 P2 SHLD GRND P1-25 P2 SHLD GRND P1-30 P2 SHLD GRND No
NTAG81CA Faceplate Maintenance cable 439 P2, P3, P4, P5 Color RXDB+ P3-3 Green/White P1-48 RXDB- P3-6 White/Green P1-24 TXDB+ P3-1 Orange/White P1-49 TXDB- P4-2 White/Orange P1-18 RX+ P4-3 Green/White P1-43 RX- P4-6 White/Green P1-19 TX+ P4-1 Orange/White P1-44 TX- P4-2 White/Orange P1-10 P5-2 Black P1-13 P5-10 Red P1-11 P5-9 Black P1-14 P5-11 White P1-35 P5-4 Black P1-38 P5-12 Green P1-36 P5-5 Black P1-39 P5-13 Blue P1-12 P5-8 Black P1-37 P5-15
Appendix B Cable description and NT8D81BA cable replacement Figure 150 NTAG81CA PC maintenance cable Table 73 NTAG81CA Faceplate Maintenance cable connections Signals (IP Trunk 3.
NTCW84EA DCH PC Card pigtail cable 441 Table 74 NTAG81BA Maintenance Extender cable connections 9-pin D-Sub (Male) 9-pin D-Sub (Female) 1 1 2 2 3 3 4 4 5 5 6 6 7 7 8 8 9 9 NTCW84EA DCH PC Card pigtail cable The NTCW84EA pigtail cable connects port 0 of the DCH PC Card to the J14 pin header on the motherboard. The cable routes the D-Channel signals to the backplane and the I/O panel. The PC Card connector is keyed to allow insertion only in the correct direction.
Appendix B Cable description and NT8D81BA cable replacement Figure 152 NTCW84EA pigtail cable Table 75 NTCW84EA pigtail cable connections PC Card P1 Signal Name P2 Color P1-1 SDAI P2-1 Black P1-2 RDAI P2-2 White P1-3 STAI P2-3 Red P1-4 RTAI P2-4 Green P1-5 CTS P2-5 Brown P1-8 TRI P2-6 Yellow P1-9 SDBI P2-7 Violet Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
NTMF04BA MSDL extension cable PC Card P1 Signal Name P2 Color P1-10 RDBI P2-8 Grey P1-11 STBI P2-9 Tan P1-12 RTBI P2-10 Pink P1-15 GRND P2-11 Green/Yellow 443 NTMF04BA MSDL extension cable The NTMF04BA cable connects the MSDL (D-Channel) port of the NTCW84KA and the NTND26AA at the 15 pin I/O panel Filter Connector on the Network shelf. The male port of the NTMF04BA mates with the female 15-way D-sub port of the NTCW84KA.
Appendix B Cable description and NT8D81BA cable replacement NTCW84LA and NTCW84MA upgrade cables The following cables are required for the upgraded 8-Port ITG ISL Trunk DCHIP card: • NTCW84LA for upgraded NTCW80CA cards • NTCW84MA for upgraded NTCW80AA cards The NTCW84LA and NTCW84MA shielded cables are required on DCHIP cards for ITG Trunk 1.0 to ITG Trunk 2.0 in field upgrades.
NTCW84LA and NTCW84MA upgrade cables Figure 154 NTMF94LA upgrade cable Table 77 NTMF94LA cable connections I/O Panel: P1 Signal Name P2, P3,P4 Color P1-21 BSOUTB- P2-2 RED P1-22 BDTRB- P2-4 GREEN SGRND P2-5 BROWN P1-45 BSINB- P2-3 BLUE P1-46 BDCDB- P2-1 ORANGE P1-47 BDSRB- P2-6 YELLOW P1-25 SHLD GRND P1-50 SHLD GRND P1-18 RXDB+ P5-3 GRN/WHT P1-19 TXDB+ P5-1 ORG/WHT Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.
Appendix B Cable description and NT8D81BA cable replacement I/O Panel: P1 Signal Name P2, P3,P4 Color P1-43 RXDB- P5-6 WHT/GRN P1-44 TXDB- P5-2 WHT/ORG P1-23 RX+ P3-3 GRN/WHT P1-24 TX+ P3-1 ORG/WHT P1-48 RX- P3-6 WHT/GRN P1-49 TX- P3-2 WHT/ORG P1-10 SDAI P4-2 BLACK P1-13 SDBI P4-10 RED P1-11 STAI P4-9 BLACK P1-14 STBI P4-11 WHITE P1-35 RDAI P4-4 BLACK P1-38 RDBI P4-12 GREEN P1-36 RTAI P4-5 BLACK P1-39 RTBI P4-13 BLUE P1-12 CTS P4-8 BLACK P
Replace cable NT8D81BA with NT8D81AA 447 Procedure 73 Preventing ground loops on connection to external LAN equipment Step Action 1 Connect the customer-provided shielded CAT5 Ethernet cable to the external LAN equipment. Ensure that the external LAN equipment is powered-up. 2 Use an ohmmeter to measure resistance to ground between the free end of the shielded RJ-45 cable and the building ground.
Appendix B Cable description and NT8D81BA cable replacement Table 78 NT8D37 cable connections Backplane slots–shroud rows I/O panel/cable designation L0–1, 2, 3 A L1–1, 2, 3 B L2–1, 2, 3 C L3–1, 2, 3 D L4–1, 2, 3 E L5–1, 2, 3 F L6–1, 2, 3 G L7–1, 2, 3 H L8–1, 2, 3 K L9–1, 2, 3 L L10–1, 2, 3 M L11–1, 2, 3 N L12–1, 2, 3 R L13–1, 2, 3 S L14–1, 2, 3 T L15–1, 2, 3 U Figure 155 Backplane slot designations Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.
Remove the NT8D81BA cable 449 Tools list • Ty-wrap cutter • Ty-wraps • Needle-nose pliers • Slotted screwdriver Remove the NT8D81BA cable Follow the steps in Procedure 74 "Removing the NT8D81BA cable" (page 449) to remove the NT8D81BA cable.
Appendix B Cable description and NT8D81BA cable replacement Procedure 75 Installing the NTCW84JA filter and NT8D81AA cable Step Action 1 Install the NTCW84JA special IPE filter connector in the vacant I/O panel slot using retained hardware. 2 Install NT8D81AA ribbon cable connectors in the IPE module backplane shroud. Be sure to install the connector so the label is facing right with the arrow pointing up and the connector is fully engaged into the shroud: a.
Appendix C Environmental and electrical regulatory data Contents This section contains information on the following topics: "Environmental specifications" (page 451) "Mechanical conditions" (page 452) "Access the ITG shell through a maintenance port or Telnet" (page 368) "Safety" (page 452) "Electromagnetic Compatibility (EMC)" (page 453) Environmental specifications Table 79 "Media Card 32-port and ITG-Pentium 24-port trunk card temperature and humidity specifications" (page 451) lists measurements o
Appendix C Environmental and electrical regulatory data Specification Minimum Maximum Recommended –50 C +70 C Relative humidity 0% 95% (non-condensing) In three minutes –50 C 25 C In three minutes 70 C 25 C Temperature shock Mechanical conditions Refer to Table 80 "Media Card 32-port and ITG-Pentium 24-port trunk card mechanical specifications" (page 452) for Media Card 32-port and ITG-Pentium 24-port trunk card mechanical tolerance ranges.
Electrical regulatory standards 453 Table 81 Safety regulations for the ITG-Pentium 24-port trunk cards Regulation identifier Regulatory agency UL 1459 Safety, United States, CALA CSA 22.2 225 Safety, Canada EN 41003 Safety, International Telecom BAKOM SR 784.103.12/4.
Appendix C Environmental and electrical regulatory data Regulation identifier Regulatory agency BAKOM SR 784.103.12/4.1/1 EMC/Safety (Switzerland) SS-447-20-22 Sweden EMC standard AS/NZS 3548 EMC (Australia/New Zealand) NFC 98020 France EMC standard Electromagnetic emissions regulations met by the Media Card 32-port trunk card, along with the country’s regulation standards are listed in Table 84 "Electromagnetic emissions regulations for the Media Card 32-port trunk card" (page 454).
Electrical regulatory standards Regulation identifier Regulatory agency IEC 801-5 (level 4, preliminary) Surge Immunity (Basic Standard) IEC 801-6 (preliminary) Conducted Disturbances (Basic Standard) BAKOM SR 784.103.12/4.
Appendix C Environmental and electrical regulatory data Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
Appendix D Subnet mask conversion from CIDR to dotted decimal format Subnet masks can be expressed in Classless Inter Domain Routing (CIDR) format, appended to the IP address (for example, 10.1.1.1/20). The subnet mask must be converted from CIDR format to dotted decimal format to configure ITG IP addresses. CIDR format expresses the subnet mask as the number of bits counting from the most significant bit of the first IP address field. A complete IP address consists of 32 bits.
Appendix D Subnet mask conversion from CIDR to dotted decimal format In the example of /20 previously given, the remainder is 4. In Table 87 "CIDR format remainders" (page 458), a remainder of 4 is equal to a binary value of 1111 0000 and the dotted decimal format value of the next and last field is 240. The first 3 fields of the subnet mask are 255.255.240. 3 If there are any remaining fields in the dotted decimal format, they have a value of 0.
Appendix E CLI commands IP Trunk 3.01 (and later) supports the following CLI commands: • ectailDefault – configure IP Trunk 3.01 (and later) to use the default 128ms Echo Canceller Tail length. • ectailNonDefault – configure IP Trunk 3.01 (and later) to use the Echo Canceller Tail length specified in the TM 3.1 File. • dspFatalErrorCountShow – details the number of fatal errors per DSP since last boot-up.
Appendix E CLI commands Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
Appendix F Configure a Netgear RM356 modem router for remote access Contents This section contains information on the following topics: "Introduction" (page 461) "Security features of the RM356 modem router" (page 462) "Install the RM356 modem router" (page 462) "Configure the TM 3.
Appendix F Configure a Netgear RM356 modem router for remote access Security features of the RM356 modem router Security features of the RM356 modem router are as follows: • Password Authentication Protocol (PAP) for dial-in PPP connection • RM356 manager password • CLID for dial-in user authentication (requires CO line with Calling Line ID) • Callback for dial-in user authentication • Dial-in user profiles • Static IP routing • IP Packet Filtering • Idle time-out disconnect for dial-in
Install the RM356 modem router 3 463 Connect the RJ-45 plug end of the local manager cable to the RS-232 Manager port RJ-45 jack on the rear of the modem router. Connect the other end of the cable to an RS-232 terminal or PC COM port configured for the following communication parameters: • 9600 bps • 8 • none • 1 The local maintenance cable connects directly to data terminal equipment (DTE).
Appendix F Configure a Netgear RM356 modem router for remote access Follow the steps in Procedure 78 "Configure the RM356 modem router through the manager menu" (page 464) to configure the RM356 modem router through the manager menu. Procedure 78 Configure the RM356 modem router through the manager menu Step Action 1 Press the Enter key. The ’Enter Password:’ prompt is displayed for 10 seconds. 2 Enter the default RM356 manager password: 1234 The "RM356 Main Menu" appears.
Install the RM356 modem router 465 11 Toggle "RIP Direction=None". Press Enter to confirm and save data to ROM, then press Esc to return from the sub-menu to the main menu. 12 Enter menu selection number 12, "Static Routing Setup", under the "Advanced Applications" section. "Menu 12 – Static Route Setup" sub-menu is displayed. If firewall security is properly configured in the customer’s Management Gateway router, and if the modem router is permitted access over the TLAN subnet to other IP Trunk 3.
Appendix F Configure a Netgear RM356 modem router for remote access Under "PPP Options" toggle "Recv Authen=PAP". Windows 9x Dialup Networking (DUN) is not compatible with CHAP/PAP or CHAP on the modem route; calls are disconnected after a few minutes. Toggle "Compression=No". Windows 9x DUN is not compatible with software compression on the modem router: calls are randomly disconnected. Toggle "Mutual Authen=No". Under "IP Address Supplied By:", toggle "Dial-in User=No", "IP Pool=Yes".
RM356 modem router manager menu (application notes on the ELAN subnet installation) 467 Set "Rem CLID=" to the PSTN Calling Number that is displayed when the remote TM 3.1 PC dials up the modem router, if CLID authentication is required for the user profile. CLID depends on providing a CO line subscribed for CLID service for the modem router’s telephone line connection. Set "Idle Timeout=1200" seconds to provide 20 minutes idle timeout disconnect for Nortel remote support purposes.
Appendix F Configure a Netgear RM356 modem router for remote access Contact Person’s Name= John Smith, 972 555-1212 Press ENTER to Confirm or ESC to Cancel: Menu 2 - MODEM Setup Modem Name= MODEM Active= Yes Direction= Incoming Phone Number= Advanced Setup= No Press ENTER to Confirm or ESC to Cancel: Menu 3 - Ethernet Setup 1. General Setup 2. TCP/IP and DHCP Setup Enter Menu Selection Number: Menu 3.
RM356 modem router manager menu (application notes on the ELAN subnet installation) CLID Authen= None Dial-in User= No IP Pool= Yes IP Start 469 PPP Options: Addr= 47.177.16.253 Recv Authen= PAP Compression= No Session Options: Mutual Authen= No Input Filter Sets= PAP Login= N/A Output Filter Sets= PAP Password= N/A Idle Timeout= 1200 Callback Budget Management: Allocated Budget(min)= Period(hr)= Press ENTER to Confirm or ESC to Cancel: Press Space Bar to Toggle. Menu 14 - Dial-in User Setup 1.
Appendix F Configure a Netgear RM356 modem router for remote access 4 _______________ 10 _______________ 5 _______________ 11 _______________ 6 _______________ 12 _______________ Enter Filter Set Number to Configure= 0 Edit Comments= Press ENTER to Confirm or ESC to Cancel: Menu 21.1 - Filter Rules Summary # A Type Filter Rules M m n - - ---- ----------------------------------------------- - 1 Y IP Pr=17, SA=0.0.0.0, SP=137, DA=0.0.0.0 N D N 2 Y IP Pr=17, SA=0.0.0.0, SP=138, DA=0.0.0.
RM356 modem router manager menu (application notes on the ELAN subnet installation) 471 Status: 10M/Half Duplex RAS S/W Version: V2.13 | 9/25/98 TX Pkts: 135579 Ethernet Address:00:a0:c5:e0:5b:a6 RX Pkts: 662866 Collisions: 49 LAN Packet Which Triggered Last Call: Press Command: COMMANDS: 1-Drop Port 1 9-Reset Counters ESC-Exit Menu 24.2 -- System Maintenance - Change Terminal Baud Rate Terminal Baud Rate: 9600 Press ENTER to Confirm or ESC to Cancel: Press Space Bar to Toggle. Menu 24.
Appendix F Configure a Netgear RM356 modem router for remote access TCP/IP 11. Internet Setup Test 12. Ping Host Enter Menu Selection Number: Manual Call Remote Node= N/A Host IP Address= N/A Menu 24.7 -- System Maintenance - Upload Firmware 1. Load RAS Code 2. Load ROM File Enter Menu Selection Number: 1 Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
Appendix G Upgrade an ITG Trunk 1.0 node to support ISDN signaling trunks Contents This section contains information on the following topics: "Upgrade procedure summary" (page 474) "Before you begin" (page 474) "Install the DCHIP hardware upgrade kit" (page 476) "Install the DCHIP I/O Panel breakout cable from the upgrade kit" (page 477) "Upgrade the ITG 8-port trunk card ITG basic trunk software to ITG/ISL trunk software" (page 478) "Step 1 - Remove ITG Trunk 1.
Appendix G Upgrade an ITG Trunk 1.0 node to support ISDN signaling trunks IP Trunk 3.01 (and later) cannot be installed on an ITG 8-port trunk card. However, IP Trunk 3.01 (and later) can interwork with ITG Trunk 2.0 nodes. IP Trunk 3.01 (and later) does not interwork with ITG Trunk 1.0 nodes. Upgrade procedure summary Step Action 1 If required, select at least one ITG 8-port trunk card to support DCHIP functionality. In some cases, a new ITG-Pentium 24-port trunk card supports DCHIP functionality.
Before you begin 475 advanced ISDN features. Table 2 "Software packages for Meridian 1/CS 1000M IP Trunk 3.01 (and later)" (page 33) lists required software packages. 3 Check the Nortel website to find the latest ITG 8-port trunk card software. Go to www.nortel.com. Follow the links to Customer Support and Software Distribution or go to www.nortel.com/support. The file to download is for the ITG 2.8.xx.mms. "ITG 2" indicates it is ITG Trunk 2.
Appendix G Upgrade an ITG Trunk 1.0 node to support ISDN signaling trunks 8 Verify that the customer site has a Nortel Netgear RM356 Modem Router (or equivalent) on the ELAN subnet. The modem router provides remote support access to ITG Trunk and other IP-enabled Nortel products. 9 Identify the TNs of the ITG 8-port trunk cards that are to be upgraded. Open the TM 3.1 ITG Meridian 1 IP Trunk main window. The TNs are listed.
Install the DCHIP hardware upgrade kit 477 4 Connect the NTCW84EA pigtail cable from port 0 of the DCHIP PC Card to the J14 pin header on the motherboard of the DCHIP card (see Figure 34 "DCHIP PC Card and NTCW84EA pigtail cable" (page 192)). The cable routes the D-Channel signals to the backplane and the I/O panel. The PC Card connector is keyed to allow insertion only in the correct direction. The J14 pin header connector is not keyed. Be careful to align the connector with the pin header.
Appendix G Upgrade an ITG Trunk 1.0 node to support ISDN signaling trunks Procedure 81 Installing the DCHIP I/O Panel breakout cable from the upgrade kit Step Action 1 For the Large System, locate the I/O connector that corresponds to the leftmost card slot of the ITG 8-port trunk card that is undergoing the hardware upgrade. 2 Disconnect existing ELAN network interface and serial cables. Remove the existing I/O panel breakout cable. 3 Install the new cable (NTCW84LA or NTCW84MA).
Upgrade the ITG 8-port trunk card ITG basic trunk software to ITG/ISL trunk software 2 479 Login to the ITG shell. At the ITG> prompt, enter setLeader setLeader "xxx.xxx.xxx.xxx", "yyy.yyy.yyy.yyy", "zzz.zzz.zzz.zzz" where • "xxx.xxx.xxx.xxx" is the ELAN network interface IP address of Leader 0, • "yyy.yyy.yyy.yyy" is the ELAN network interface gateway (router) IP address. If the TM 3.
Appendix G Upgrade an ITG Trunk 1.0 node to support ISDN signaling trunks 7 Log into the ITG shell. At the ITG>prompt, enter clearLeader "xxx.xxx.xxx.xxx", "yyy.yyy.yyy.yyy", "zzz.zzz.zzz.zzz" (see notes in step 2). The ITG shell outputs value = 0 = 0 x 0 to indicate successful completion of the clearLeader command. Enter clearLeader command even when removing configuration files from Follower cards. —End— Step 2 - Transmit ITG Trunk 2.
Upgrade the ITG 8-port trunk card ITG basic trunk software to ITG/ISL trunk software 481 Transmit Control window open displaying the location of the software file on TM 3.1. If the trunk card can be reached by Telnet from TM 3.1, but TM 3.1 shows the card status as Not Responding, TM 3.1 ITG SNMP MIB is incompatible with the ITG 8-port trunk card software version.
Appendix G Upgrade an ITG Trunk 1.0 node to support ISDN signaling trunks Figure 157 Software download example 9 To verify the software upgrade on Leader 0, telnet to the IP address of the Leader 0 card. Leader 0 is the only card that has an IP address configured at this stage of the upgrade. Enter the following command: ITG> swVersionShow 10 Configure the ITG Trunk 2.0 data on the TM 3.1 ITG ISDN IP Trunk application. "Configure IP Trunk 3.01 (and later) data in TM 3.
Configure the Meridian 1 ITG/ISL trunk data 483 Procedure 84 Removing the ITG Trunk 1.0 configuration data from Meridian 1 Step Action 1 Out existing ITG basic trunks that are being upgraded to ITG ISL trunks: a. Identify TNs of trunks that are to be outed. Look in TM 3.1 ITG ISDN IP Trunks application for ITG trunks or, in LD 21, request an LTN of existing basic ITG TIE trunk route. The LTN gives a list of every single unit. Observe if there are 8 or 4 TNs on the same card.
Appendix G Upgrade an ITG Trunk 1.0 node to support ISDN signaling trunks Follow the steps in Procedure 85 "Configuring the Meridian 1 ITG/ISL trunk data" (page 484) to configure the Meridian 1 ITG/ISL trunk data. Procedure 85 Configuring the Meridian 1 ITG/ISL trunk data Step Action 1 Build a new route data block for the ITG/ISL trunks using the same route number. Set INAC=YES in the Route Data Blocks (RDB) for the ITG ISL routes at all Meridian 1 ESN nodes. See "LD 16 Configure the IP Trunk 3.
Upgrade Troubleshooting 485 Verify ROM-BIOS version When the ITG trunk card is reset, it displays a series of startup messages on the local TTY. Verify that the ROM-BIOS is 1.1 or greater. If not, contact Nortel technical support. Upgrade Troubleshooting This section provides two procedures to correct TM 3.1 upgrade problems. TM 3.1 cannot refresh view (card not responding) If TM 3.1 cannot see card status through refresh, but the card can be Telnetted from TM 3.1, the TM 3.
Appendix G Upgrade an ITG Trunk 1.0 node to support ISDN signaling trunks —End— Nortel Communication Server 1000 IP Trunk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nortel Networks .
Index Symbols/Numerics 10/100BaseT 46, 64 10/100BaseT Ethernet ports 153 100BaseT full-duplex 160 100BaseTX 31 10BaseT 31, 31, 46, 64 10BaseT Ethernet hub 33 A AAL5 112 Active Leader 39, 39, 40, 40, 40 active systems/standby systems 39 address translation 76 Adjust ping measurements 145 alarms 391 analog 91 analog facility 61 analog ISL TIE trunks 61 analog trunks 61 ARQ 24 auto-negotiate 160, 161 B backplanes connectors 447 I/O panel connections Backup Leader 39, 39, 40, 41 Baystack 450 161 BCM 2.
Index Delay variation 168 delay variation or 90 Delete a system 299 Dial Plan table 23 dialing plan 44, 65, 84 Dialing plan 65 DSP Profile 306 duplex mismatch 161 E edit node information 311 ELAN (management) subnet 159 ELAN subnet 32 endpointIdentifier 24 ESN TGAR 139 ESN5 67 Ethernet hub 33 Ethernet ports 153 F G.729B codec 85 G3 Fax 79 G3 Fax terminal 78 Gatekeeper 20, 21, 22, 23, 26, 27, 130 Gatekeeper-routed calls 22 GCF 25 Group 3 fax 91, 138 GRQ 24 H H.225 63, 130 H.
Index 489 J O jitter 71, 72, 90 jitter buffer 168 Jitter buffer parameters 162 jitter, and 90 Overlapping channel numbers 190 overlapping number 190 P package requirements 27, Packet delay 72 Large Systems 32 packet loss 71, 90 latency 67, 71, 71, 74, 74, 74, 74, 74, 77, 92Packet loss 71 Latency 72 packet loss evaluation 146 LDR 49, 54 Packet Loss Rate (PLR) 145 Leader 24, 40 Patching 410 Leader 0 39, 39, 39 PC Card socket 49 Leader 1 39, 39, 39 PCM encoding 161 LED 48, 49, 49 ping 166 LLC SNAP 112 pi
Index TM 3.1 26, 28, 31 TM 3.
Nortel Communication Server 1000 IP Trunk Fundamentals Copyright © 2007, Nortel Networks All Rights Reserved. Publication: NN43001-563 Document status: Standard Document version: 02.01 Document date: 21 December 2007 To provide feedback or to report a problem with this document, go to http://www.nortel.
