Page 1 All Rights Reserved Produced in Canada Information is subject to change without notice. Nortel Networks reserves the right to make changes in design or components as progress in engineering and manufacturing may warrant. SL-1, Meridian 1, and Succession are trademarks of Nortel Networks.
Page 3 Page 3 of 644 Revision history September 2004 Standard 2.00. This document is up-issued for Communication Server 1000 Release 4.0. October 2003 Standard 1.00. This document is a new NTP for Succession 3.0. It was created to support a restructuring of the Documentation Library. This document...
Page 4 Page 4 of 644 Revision history 553-3001-363 Standard 2.00 September 2004...
Page 5: Table Of Contents
Page 5 of 644 Contents About this document ..... . . Subject ..........Applicable systems .
Page 6 Page 6 of 644 Contents Ordering rules for an IP Trunk 3.01 (and later) node ... Ordering rules for IP Trunk 3.01 (and later) node expansion ..Sparing ratios for IP Trunk 3.01 (and later) components .
Page 7 Contents Page 7 of 644 Speech Activity Detection ....... . DTMF Through Dial .
Page 8 Page 8 of 644 Contents Network engineering guidelines overview ..... . IP Trunk 3.01 (and later) traffic engineering ....Estimate voice traffic calculations .
Page 9 Contents Page 9 of 644 Components of delay ........Reduce link delay .
Page 10 Page 10 of 644 Contents Payload size ......... . . Jitter buffer parameters (voice playout delay) .
Page 11 Contents Page 11 of 644 Incorrect ISL channel numbering plans ..... . Install and cable IP Trunk 3.01 (and later) cards ....Card installation procedure ..
Page 12 Page 12 of 644 Contents Configure ISDN feature in Customer Data Block ....Configure IP Trunk 3.01 (and later) TIE trunk routes ... Configure Media Card 32-port and ITG-Pentium 24- port trunk cards and units for IP Trunk Route .
Page 13 Contents Page 13 of 644 Transmit the node properties, card properties and dialing plan to Leader 0 ........Verify installation and configuration .
Page 14 Page 14 of 644 Contents Edit a node ..........Delete a node .
Page 15 Contents Page 15 of 644 Disable the indicated IP trunk card when idle ....Enable an indicated IP trunk card ......Disable an indicated IP trunk card port .
Page 16 Page 16 of 644 Contents Display IP trunk card status ....... Display IP trunk card port status .
Page 17 Contents Page 17 of 644 Fault clearance procedures ........DSP failure .
Page 18 Page 18 of 644 Contents NTMF04BA MSDL extension cable ......NTCW84LA and NTCW84MA upgrade cables ....Prevent ground loops on connection to external customer LAN equipment ..
Page 19 Contents Page 19 of 644 Appendix G: Upgrade an ITG Trunk 1.0 node to support ISDN signaling trunks ....623 Contents ..........Upgrade procedure summary .
Page 20 Page 20 of 644 Contents 553-3001-363 Standard 2.00 September 2004...
Page 21: About This Document
IP Trunk 3.01 also enables networking with CS 1000/1000M systems running CS 1000 Release 4.0. (A CS 1000 system is a server-based, full-featured IP PBX, fully distributed over IP LAN\MAN\WAN networks.) The IP Trunk 3.01 application, building on the approach in IP Trunk 3.0,...
Page 22: Applicable Systems
This NTP contains information about systems, components, and features that are compatible with Nortel Networks Communication Server 1000 Release 4.0 software. For more information on legacy products and releases, click the Technical Documentation link under Support on the Nortel Networks home page: http://www.nortelnetworks.com/...
Page 23 Signaling Server, the Call Server, or both. System migration When particular Meridian 1 systems are upgraded to run CS 1000 Release 4.0 software and configured to include a Signaling Server, they become CS 1000M systems. Table 1 lists each Meridian 1 system that supports an upgrade path to a CS 1000M system.
Page 24: Conventions
Page 24 of 644 About this document Conventions Terminology In this document, the following systems are referred to generically as “system”: • Communication Server 1000S (CS 1000S) • Communication Server 1000M (CS 1000M) • Communication Server 1000E (CS 1000E) • Meridian 1 The following systems are referred to generically as “Small System”: •...
Page 25: Related Information
• Communication Server 1000S: Planning and Engineering (553-3031-120) Online To access Nortel Networks documentation online, click the Technical Documentation link under Support on the Nortel Networks home page: http://www.nortelnetworks.com/ CD-ROM To obtain Nortel Networks documentation on CD-ROM, contact your Nortel Networks customer representative.
Page 26 Page 26 of 644 About this document 553-3001-363 Standard 2.00 September 2004...
Page 27: Overview Of Ip Trunk 3.01
ITG Trunk 2.x using Integrated Services Digital Network (ISDN). IP Trunk 3.01 (and later) allows networks with Meridian 1 IP-enabled systems to add a CS 1000 system to the existing IP Telephony network. This increases the range of system options to provide enterprise-wide telephony services.
Page 28 Page 28 of 644 Overview of IP Trunk 3.01 Telephone calls, IP Trunk can make some call-routing decisions locally. This can be done for one of the following reasons: • It can maintain at least a minimum level of service in the unlikely event that all Signaling Servers on the network are unreachable.
Page 29 Overview of IP Trunk 3.01 Page 29 of 644 For a Meridian 1 system to interwork with a CS 1000S or CS 1000M system, the following requirements must be met: • The ITG-Pentium 24-port trunk card and the Media Card 32-port trunk card must be upgraded to IP Trunk 3.01 (and later) software.
Page 30 Page 30 of 644 Overview of IP Trunk 3.01 Figure 1 IP Trunk 3.01 (and later) architecture IP Trunk BCM 2.0.1 BCM 2.0.2 BCM 2.0.3 IP Trunk BCM 2.5 GA BCM 2.5 FP1 ITG Trunk 2.x hardware IP Network Leader, DCHIP, + Followers ATPM Gatekeeper H.323...
Page 31 Overview of IP Trunk 3.01 Page 31 of 644 IP Trunk 3.01 (and later) uses the Meridian 1/CS 1000M core switch as the primary driver, which sends ISDN messages through the ISDN Signaling Link (ISL) to the IP trunk card for IP Trunk 3.01 (and later) processing. IP Trunk 3.01 (and later) tandems the Meridian 1/CS 1000M core switch to the IP network, providing point-to-multipoint connection.
Page 32 Page 32 of 644 Overview of IP Trunk 3.01 Figure 2 Directly-routed call 553-3001-363 Standard 2.00 September 2004...
Page 33 Overview of IP Trunk 3.01 Page 33 of 644 Gatekeeper-routed calls In Gatekeeper-routed calls, the Gatekeeper returns the Gatekeeper’s IP address and port as both the destination for the originating call and the originator for the destination, rather than the end-point address and port. Figure 3 represents a Gatekeeper-routed call.
Page 34: Startup And Registration
Page 34 of 644 Overview of IP Trunk 3.01 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. This operation remains unchanged from prior releases.
Page 35 Overview of IP Trunk 3.01 Page 35 of 644 Depending on the Gatekeeper type (for example, Gatekeepers other than CS 1000S or CS 1000M), if the Gatekeeper flag in the dial plan file indicates the need for multiple IP Trunk 3.01 card IP addresses (flag value = 0), the RRQ includes all IP addresses for the node.
Page 36: Ip Trunk 3.01 (And Later) And Cs 1000S/Cs 1000M
The standards allow seconds from 1 to (2 ) –1. Recommendation Nortel Networks recommends that the TTL be provisioned in the 30- to 60- second range. The IP Trunk 3.01 (and later) node must perform a “keep-alive” re-registration prior to the expiry of the timer on the Gatekeeper. When the Gatekeeper timer expires, a full registration is needed.
Page 37 Overview of IP Trunk 3.01 Page 37 of 644 IP Trunk 3.01 (and later) supports Gatekeeper Registration and Admission Signaling (RAS) and Call Admission Signaling. IP Trunk 3.01 (and later) interworks with CS 1000S or CS 1000M, which fulfills the role of a Gatekeeper.
Page 38: Loss Plans And Pad Values
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. As with IP Peer, it also allows the creation of a custom table when the environment requires one.
Page 39: Codec Selection
CS 1000M. IP Trunk 3.01 (and later) requirements IP Trunk 3.01 requires a minimum of Release 25.15 software. To interwork with the CS 1000S/CS 1000M Gatekeeper, CS 1000 Release 3.0 software (or later) is required. Package requirements Table 2 on page 40 lists the package requirements for the IP Trunk 3.01...
Page 40 Page 40 of 644 Overview of IP Trunk 3.01 transport. If both QSIG and MSDL are configured on the network, this can cause the loss of features such as Name Display, Ring Again, and Transfer Notification and subsequent path simplification operations. Table 2 IP Trunk 3.01 (and later) package requirements Package...
Page 41: Otm 2.1
Overview of IP Trunk 3.01 Page 41 of 644 OTM 2.1 OTM 2.1 (or later) is required to configure and maintain IP Trunk 3.01 (and later). Interoperability with the ITG 8-port trunk card Telephone calls can be made between IP Trunk 3.01 (and later) and ITG Trunk 2.x.
Page 42 Page 42 of 644 Overview of IP Trunk 3.01 553-3001-363 Standard 2.00 September 2004...
Page 43: System Description
Page 43 of 644 System description Contents This section contains information on the following topics: IP Trunk 3.01 (and later) application ......System requirements .
Page 44 Page 44 of 644 System description Software delivery ......... Replacing a CompactFlash PC Card (C:/ drive) .
Page 45: Ip Trunk 3.01 (And Later) Application
System description Page 45 of 644 Codec profiles ..........G.711 .
Page 46 Page 46 of 644 System description To install IP Trunk 3.01 (and later), the customer must have a corporate IP network with managed bandwidth capacity, and routers available for WAN connectivity between networked Meridian 1/CS 1000M systems. The best VoIP performance is obtained with a QoS-managed network. The LAN connection of IP Trunk 3.01 (and later) requires 10BaseT or 100BaseTX Ethernet interfaces for VoIP and 10BaseT for management and D-Channel signaling.
Page 47: System Requirements
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 Networks products. The Nortel Networks Netgear RM356 modem router integrates the functions of a V.90 modem, a PPP remote access server, an IP router, and a 4-port 10BaseT Ethernet hub, and provides a range of security features that must be configured to comply with the customer's data network security policy.
Page 48 Coordinated Dialing Plan (CDP). Optional Flexible Numbering Plan (FNP) Optional Note: Nortel Networks recommends that MCDN, not QSIG, be used on all IP Trunk 3.01 (and later) systems. Only MCDN is supported for interworking with CS 1000S and CS 1000M 553-3001-363 Standard 2.00...
Page 49: Hardware Components For Ip Trunk 3.01 (And Later)
System description Page 49 of 644 Hardware components for IP Trunk 3.01 (and later) New installations use the Media Card 32-port trunk card. Table 4 lists the hardware components required for new installations. Table 4 Hardware components for the Media Card 32-port trunk Component Product code The package includes the following:...
Page 50 Note 1: OTM 2.1 (and later) is a prerequisite and must be ordered separately. Note 2: Nortel Networks Netgear RM356 Modem Router or equivalent is required for remote support and must be ordered separately from retail outlets.
Page 51 System description Page 51 of 644 Table 5 lists the extra components used by both the Media Card 32-port trunk card and the ITG-Pentium 24-port trunk cards. Table 5 Extra components for IP Trunk 3.01 (and later) trunk cards (Part 1 of 2) Component Product codes MSDL DCH cable (included in Large System package):...
Page 52: Ordering Rules And Guidelines
Page 52 of 644 System description Table 5 Extra components for IP Trunk 3.01 (and later) trunk cards (Part 2 of 2) Component Product codes Documentation 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...
Page 53: Ordering Rules For Ip Trunk 3.01 (And Later) Node Expansion
System description Page 53 of 644 For MSDL and DCHIP cards that reside in the same Large System UEM equipment row, order: • NTND26 MSDL DCH cable in sufficient length to reach from the MSDL to the I/O Panel of the IPE module that contains the DCHIP For MSDL and DCHIP cards that reside in different Large System Universal Equipment Modules (UEM) equipment rows in a multi-row Large System, order:...
Page 54: Sparing Ratios For Ip Trunk 3.01 (And Later) Components
Page 54 of 644 System description — one IP Trunk 3.01 (and later) Small and Large Systems 32-port package with DCHIP Sparing ratios for IP Trunk 3.01 (and later) components Sparing ratios for selected components are listed in Table 6. Table 6 Sparing ratios Component...
Page 55: 8051 Xacontroller Firmware
NTVQ01BB Media Card 32-port trunk cards are factory-programmed with Release 8.0 firmware. Any firmware feature upgrades are available on the Nortel Networks website. Download this firmware from the Customer Support Software page. Go to www.nortelnetworks.com. Follow the links to Customer Support and Software Distribution or go to www.nortelnetworks.com./support.
Page 56: Card Roles
Page 56 of 644 System description Card roles The Media Card 32-port trunk card and ITG-Pentium 24-port trunk card can have one or more of the following roles: • Follower • Active Leader • Backup Leader • D-channel IP gateway (DCHIP) The card roles identify which systems are active systems/standby systems and which are client systems.
Page 57 System description Page 57 of 644 The Leader, Backup Leader, Follower, and DCHIP cards communicate through their ELAN subnet connections. For more information, see “Internet Protocols and ports used by IP Trunk 3.01 (and later)” on page 174. Follower A Follower card is an ITG-Pentium 24-port trunk card and/or Media Card 32-port trunk card which converts telephone signals into data packets and data packets into telephone signals.
Page 58 Page 58 of 644 System description After a channel on a card has been selected, the Active Leader sends a message to the selected IP trunk card telling it to reserve a channel for the new call. The Active Leader redirects the call to the selected IP trunk card. All subsequent messages are sent directly from the remote VoIP gateway node to the selected card.
Page 59 System description Page 59 of 644 Figure 5 IP Trunk 3.01 (and later) architecture Core Switch Core Switch I T G Core Switch DCHIP + Followers H.323 IP Network I T G Core Switch I T G 553-9481 The ISL connection to the Meridian 1/CS 1000M functions as it does in a normal ISDN network.
Page 60 Page 60 of 644 System description Each DCHIP trunk card can be associated with up to 382 trunks. The trunks reside on all IP Trunk 3.01 (and later) IP trunk cards (ITG-Pentium 24-port trunk cards and Media Card 32-port trunk cards) in the node. This creates a functional grouping of IP trunk cards with the DCHIP trunk card providing the DCH connectivity.
Page 61: Card Combinations
System description Page 61 of 644 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.
Page 62: Interactions Among Card Functions
Page 62 of 644 System description Note: All DCHIPs in an IP Trunk 3.01 (and later) node must be configured with the same DCH protocol. If the user wants to use multiple DCH protocols, the user must configure multiple IP Trunk 3.01 (and later) nodes.
Page 63 System description Page 63 of 644 Follower cards continuously send Update messages to the Active Leader card. These messages inform the Active Leader card of the Followers’ most recent status and resources. The Active Leader sends Update messages to the Follower cards, informing them of the updated dialing number to IP address translation information.
Page 64 Page 64 of 644 System description Critical synchronized data includes the following: • the card index: – index 1 indicates Leader 0 – index 2 indicates Leader 1 – index 3 or greater indicates Follower • the Management MAC address (motherboard Ethernet address) •...
Page 65: Itg-Pentium 24-Port Trunk Card (Nt0961Aa)
System description Page 65 of 644 ITG-Pentium 24-port trunk card (NT0961AA) The ITG-Pentium 24-port trunk card was introduced as part of ITG Trunk 2.0. During the installation of the IP Trunk 3.01 loadware, the application on the ITG-P 24-port card(s) (ITG-P) must be upgraded. It is essential to ensure the latest software is loaded on the ITG-P card(s).
Page 66 Page 66 of 644 System description Figure 7 ITG-Pentium 24-port trunk card system connectivity and messaging (ISL DCH) RS-422 SSD Trunk e l f Signaling Messages I P E D S - 3 H I P X P E I T G 10/100BaseT (Voice/fax) OTM PC...
Page 67: Faceplate Indicators, Controls, And Interfaces
System description Page 67 of 644 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. Figure 8 NT0961AA ITG-Pentium 24-port trunk card Ethernet Voice Port Card Status LED Reset switch Reset...
Page 68 Page 68 of 644 System description reset sequence. The LED remains lit until the card correctly boots and assumes its role (that is, Leader, Backup Leader, Follower or DCHIP). If the LED remains on, one of the following has occurred: •...
Page 69 System description Page 69 of 644 PC Card socket There are two PC Card sockets. The faceplate socket accepts either a Type I, a Type II, or a Type III PC Card and is designated ATA device A:. The internal socket is reserved for the NTWE07AA C7LIU DCH PC Card on the DCHIP.
Page 70: Backplane Interfaces
Page 70 of 644 System description Backplane interfaces The following interfaces are provided on the backplane connector: DS-30X voice/signaling This carries PCM voice and proprietary signaling on the IPE backplane between the IP trunk card and the Intelligent Peripheral Equipment Controller (XPEC).
Page 71: Media Card 32-Port Trunk Card (Ntvq01Bb)
System description Page 71 of 644 Figure 9 Mechanical assembly PCI Connectors Two-Slot Faceplate Board I T G Motherboard Daughterboard G200402 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.01 loadware, the application on the Media Card(s) must be upgraded.
Page 72: Description
Page 72 of 644 System description Description The Media Card 32-port trunk card is based on an integrated hardware platform that delivers a single-slot ITG solution, with an increase in port density from 24 ports to 32 ports. The Media Card 32-port trunk card faceplate is shown in Figure 10.
Page 73: Ntvq01Bb Hardware
System description Page 73 of 644 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: •...
Page 74: Assembly Description
Page 74 of 644 System description Assembly description The Media Card 32-port trunk card assembly comes with a pre-installed SDRAM Module. The IP Trunk Application is installed on the C:/ drive. Faceplate indicators and interfaces The Media Card 32-port trunk card has a single slot faceplate. It uses shortened lock latches to lock it in place.
Page 75: Backplane Interfaces
RS-232 serial COM port for the Command Line Interface (CLI) • 10BaseT ELAN and 10/100BaseT TLAN Ethernet ports Installation guidelines Use the following guidelines when installing the Media Card 32-port trunk card: • Ensure CS 1000 Release 4.0 software is installed and running. IP Trunk Description, Installation, and Operation...
Page 76: Software Delivery
Page 76 of 644 System description • 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.
Page 77 System description Page 77 of 644 IMPORTANT! The software is downloadable from the Nortel Networks website and is available to IP Trunk customers free of charge. The Media Card 32-port trunk card package is shipped with the following two major components, as well as other items: •...
Page 78: Replacing A Compactflash Pc Card (C:/ Drive)
A:/ drive for normal operation. If a CFlash ATA card is to be used for file transfers to or from the A:/ drive, to C:/ drive, Nortel Networks recommends that the CFlash ATA card be formatted on the Media Card 32-port trunk card before use.
Page 79 System description Page 79 of 644 Procedure 1 Removing the CFlash card on NTVQ01BB Gently pull the clip from its latched position. See Figure 11. Figure 11 CFlash card with clip latched Move the clip up. The CFlash card can now be removed from the drive. Figure 12 CFlash card with clip up End of Procedure...
Page 80 Page 80 of 644 System description Procedure 2 Installing the CFlash card Follow ESD precautions to protect the card. Place the Media Card 32-port trunk card horizontally on a clean bench. The metal clip should be pulled up and the new CFlash card should be kept in the right position (see Figure 13).
Page 81: Software Upgrade
System description Page 81 of 644 Figure 14 CFlash card with metal clip down End of Procedure WARNING The Media Card 32-port trunk card requires the IP Trunk 3.01 (and later) application software (exec file) to be present on the C:/ drive (CFlash card) in order to run the IP Trunk 3.01 (and later) application.
Page 82 502 information on how to upgrade the software by FTP from the CLI. A CompactFlash PC Card containing the latest software version can be obtained from Nortel Networks. See “Upgrade IP trunk card software by PC Card” on page 503 for information on how to perform the upgrade.
Page 83: Media Card Application Identification Labels
System description Page 83 of 644 Media Card application identification labels Media Card application identification labels (see Figure 15) are provided with every Media Card 32-port trunk card package. Affix the appropriate label to the Media Card's faceplate (see Figure 16). Figure 15 Media Card identification labels Figure 16...
Page 84: Interoperability With Earlier Versions Of Itg Trunk
Page 84 of 644 System description Interoperability with earlier versions of ITG Trunk When Media Card 32-port trunk cards are implemented in existing networks with nodes comprised of ITG Trunk 2.xx, Release 19 or earlier, fax calls do not work because of protocol incompatibility. Voice calls between ITG Trunk 2.1 and ITG Trunk 2.0 or ITG Trunk 1.0 operate without restrictions.
Page 85 System description Page 85 of 644 The ISL interface makes available the flexibility of using ISDN signaling to analog facilities. When no Primary Rate Interface (PRI) exists between two Meridian 1/CS 1000M systems, ISL operates in dedicated mode. A dedicated point-to-point signaling link is established between the two systems.
Page 86 Page 86 of 644 System description Figure 17 ITG configuration H I P d e r L e a l o w F o l Router IP Network H I P Router d e r L e a l o w F o l Router 553-9472...
Page 87 System description Page 87 of 644 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) •...
Page 88: Inter-Card Signaling Paths
Page 88 of 644 System description Figure 18 Signal flow from the DCH to the H.323 stack DCHIP FOLLOWER Meridian 1 H.323 Processor Processor Backplane VxWorks VxWorks TCP/IP TCP/IP Intercard Signaling H.323 Signaling/Voice 10BaseT Ethernet (ELAN subnet) 10/100BaseT Ethernet (TLAN subnet) 553-9475 Note: For further information on ISDN Signaling Link (ISL), refer to System Management (553-3001-300), ISDN Primary Rate Interface:...
Page 89 System description Page 89 of 644 Figure 19 IP Trunk 3.01 (and later) card signaling paths Meridian 1 Leader/Follower DS-30X IP Messages Leader DCHIP/Follower ISL DCH IP Messages DCHIP DS-30X Timeslot port connection (SSD) DS-30X ISL DCH Follower connection DS-30X Follower 553-9476 In Figure 19, the DS-30X connection is part of the Meridian 1/CS 1000M IPE...
Page 90: Dialing Plans
Page 90 of 644 System description 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 OTM or overlays in the Meridian 1/CS 1000M.
Page 91: North American Dialing Plan
System description Page 91 of 644 Meridian 1/CS 1000M switch A has two IP Trunk 3.01 (and later) nodes, A1 and A2, for the destination NPA 613. A Route List Block (RLB) is created, in order to have two route entries (one for each IP Trunk 3.01 (and later) node).
Page 92: Flexible Numbering Plan
Page 92 of 644 System description Figure 20 North American dialing plan — call flow COT/ Meridian 1 Meridian 1 HOLD DN 7000 47.82.32.124 47.82.32.123 Translation Table IP Address 47.82.32.123 Outgoing call path 553-9474 Flexible Numbering Plan A Flexible Numbering Plan (FNP) allows the length of Location Codes (LOCs) to vary from node to node.
Page 93: Echo Cancellation
System description Page 93 of 644 ESN5 inserts the Network Class of Service (NCOS) prefix ahead of the dialed numbers. Make sure that, if ESN5 is to be used, it is provisioned on both the IP trunk cards and the Route Data Block (RDB) for that node. If ESN5 is provisioned for an IP Trunk 3.01 (and later) node, all remote ITG 2.x and IP Trunk 3.01 (and later) node must have that node provisioned as “SL1ESN5”...
Page 94 Page 94 of 644 System description Recent releases of OTM that are properly set up, with all applicable patches and the fix integrated, have the default for new systems set to 128 ms. This results in all new nodes being given the correct default value. However, it will not change the value on systems that are already configured unless the user deliberately changes the value.
Page 95: Speech Activity Detection
System description Page 95 of 644 Table 9 Echo canceller tail delay mapping from OTM to IP Trunk 3.01 (Part 2 of 2) Provisioned in OTM (in ms) Value used by IP Trunk 3.01 32 (default value in IP Trunk 3.01 128 (default value in IP Trunk 3.01) and earlier) 128 (default value in IP Trunk 3.01)
Page 96: Dtmf Through Dial
Page 96 of 644 System description For applications that send no packets during silence, the first packet after a silence period is distinguished by setting a marker bit in the Real Time Protocol (RTP) data header. Applications without Speech Activity Detection set the bit to zero.
Page 97 System description Page 97 of 644 Figure 21 DTMF tone detection IP Trunk Description, Installation, and Operation...
Page 98: Quality Of Service
Page 98 of 644 System description Quality of Service Quality of Service (QoS) is the gauge of quality of the IP network between two nodes. As QoS degrades, existing calls suffer from poor voice and fax quality. New calls will not be initiated if transmissions degrade below an acceptable level.
Page 99: Quality Of Service Parameters
System description Page 99 of 644 Since IP trunks use the same port for both voice and fax, the same QoS thresholds apply for both voice and fax calls. Network requirements for fax are more stringent than for voice. Fax protocols, such as T.30, are more sensitive to transmission errors than the human ear.
Page 100: Network Performance Utilities
Page 100 of 644 System description Latency Latency is the amount of time it takes for a discrete event to occur. Bandwidth Bandwidth is a measure of information carrying capacity available for a transmission medium. The greater the bandwidth the more information that can be sent in a given amount of time.
Page 101: E-Model
System description Page 101 of 644 Traceroute Traceroute uses the IP Time-To-Live (TTL) field to forward router hops to a specific IP address. A router must not forward an IP packet with a TTL field of 0 or 1. It must, instead, discard the packet and return an ICMP “time exceeded”...
Page 102: Fallback To Alternate Facilities
Page 102 of 644 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.
Page 103: Triggering Fallback To Alternate Trunk Facilities
System description Page 103 of 644 Triggering fallback to alternate trunk facilities A key background activity of IP Trunk 3.01 (and later) is to monitor the network’s QoS between itself and each remote IP gateway configured in the dialing plan. When the QoS is below the defined acceptable level for a given IP Trunk 3.01 (and later) destination node, all outgoing calls from the near-end Meridian 1/CS 1000M to the far end Leader are re-routed through alternate circuit-switched trunk facilities.
Page 104: Fallback In Ip Trunk 3.01 (And Later)
Page 104 of 644 System description Figure 22 Example of a fallback to alternate facilities situation Originating IPE Terminating IPE MMCS MMCS IP Trunk Gateway IP Trunk Gateway IP Trunk network QoS falls below customer-defined level Network Call is routed PSTN through the PSTN IP Trunk card recognizes...
Page 105: Return To The Ip Network
System description Page 105 of 644 As a result, for all calls going to the Gatekeeper, such as in IP Peer Networking, no fallback can occur. The call either goes through with possibly a lower QoS, or the call clears instead of falling back. All QoS control is in the hands of the Gatekeeper.
Page 106 Page 106 of 644 System description The OTM 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 –...
Page 107: Fax Support
System description Page 107 of 644 If both table entries are not present, a condition occurs where packets for voice, control, or both can be sent to the default route because the ToS does not match the local subnet entry. These packets go to the router and then back on the subnet, wasting router resources and increasing traffic on the subnet.
Page 108 Page 108 of 644 System description All T.30 session establishment and capabilities negotiation are carried out between the telephones through the IP trunk cards over the IP Trunk 3.01 (and later) network using the T.38 protocol. In terms of the internet fax service roles, the IP trunk card acts as both the fax on-ramp gateway and the fax off-ramp gateway, depending on the call direction.
Page 109: Remote Access
Remote Access Remote Access is supported on IP Trunk 3.01 (and later). Remote Access allows an OTM user with no IP Trunk 3.01 (and later) data, including Nortel Networks support personnel, to manage the IP trunk card remotely. Management and support of the IP Trunk 3.01 (and later) network depend on IP networking protocols including SNMP, FTP, and Telnet.
Page 110: Configuration
Page 110 of 644 System description IP Trunk 3.01 (and later) uses a Remote Authentication Dial In User Service (RADIUS) client to transmit these statistics from the IP trunk card to a network device: • The IP trunk card sends a Start record when a call begins. •...
Page 111: Messaging
System description Page 111 of 644 Messaging The RADIUS client sends two records to the network listener: one when the call is answered and one at the end of the call. The messages are sent by the Follower card which processes the voice call (not the DCHIP or Leader if they are not handling the voice data).
Page 112: Snmp Mib
Page 112 of 644 System description If the call is not answered or is rejected, only an End record is generated. End record The End record is sent when the call is released. It contains the following fields: • Calling party number •...
Page 113: Mib-2 Support
System description Page 113 of 644 MIB-2 support Support of MIB-2 is enabled by the use of the WindRiver SNMP agent, © © WindNet . The WindNet agent supports the following MIB-2 groups: • system • interfaces • • • Internet Control Message Protocol (ICMP) •...
Page 114: Codec Profiles
Page 114 of 644 System description • Control of D-channel state, such as: — enable — disable — 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) —...
Page 115: G.729Ab
System description Page 115 of 644 • G.729B • G.723.1 G.711 The G.711 codec delivers “toll quality” audio at 64 kbit/s. This codec is optimal for speech quality, as it has the smallest delay and is resilient to channel errors. However, it uses the largest bandwidth. The G.711 codec is the default codec if the preferred codec of the originating node is not available on the destination IP Trunk 3.01 (and later) node.
Page 116: 5.3 Kbit/S Or 6.3 Kbit/S)
Page 116 of 644 System description G.723.1 (5.3 kbit/s or 6.3 kbit/s) The G.723.1 codec provides the greatest compression. Voice Activity Detection/Silence Suppression is configurable through OTM 2.1 (and later). An ITG-Pentium 24-port trunk card supports 24 channels per card with G.723.1.
Page 117: Security Passwords
IP trunk card level administration options. It does not, however, allow any type of low-level diagnostics to be performed. Technical support level The Technical support level is for use by Nortel Networks personnel only. It allows low-level message monitoring and factory testing. IP Trunk...
Page 118 Page 118 of 644 System description 553-3001-363 Standard 2.00 September 2004...
Page 119: Itg Engineering Guidelines
Page 119 of 644 ITG engineering guidelines Contents This section contains information on the following topics: Introduction ..........Audience.
Page 120 Page 120 of 644 ITG engineering guidelines Traffic mix ..........TCP traffic behavior.
Page 121: Introduction
ISDN Signalling Link (ISL) TIE trunks between Meridian 1 ESN nodes • enables interworking with other Nortel Networks VoIP products such as CS 1000S, CS 1000M, and Business Communication Manager (BCM) IP Trunk 3.01 (and later) routes voice traffic over existing private IP network facilities with available under-used bandwidth on the private WAN backbone.
Page 122: Audience
Note: Pre-installation analysis of the data network enables IP Trunk 3.0 (and later) to be provisioned correctly. For proper analysis and deployment, obtain a network diagram or a description of the network topology and hierarchy. Nortel Networks recommends using a data network analyzer (for example, Sniffer™) for evaluation and troubleshooting.
Page 123: Equipment Requirements
Voice Trunks Network (traditional) (circuit-switched) 553-IPT9146 IP Trunk 3.01 (and later) is available for the following systems running CS 1000 Release 4.0 software: • Meridian 1 PBX 61C CP PII • Meridian 1 PBX 81C CP PII IP Trunk Description, Installation, and Operation...
Page 124 Page 124 of 644 ITG engineering guidelines • Meridian 1 PBX 11C Chassis • CS 1000M SG • CS 1000M MG • CS 1000M Cabinet • CS 1000M Chassis The IPE trunk cards plug into the Meridian 1/CS 1000M IPE shelf. A maximum of eight ITG-Pentium 24-port trunk cards can fit on one IPE shelf.
Page 125: Scope
ITG engineering guidelines Page 125 of 644 Scope These engineering guidelines address the design of the IP Trunk 3.01 (and later) network, which consists of the following: • IP Trunk 3.01 (and later) nodes • Telephony LAN (TLAN) subnets to which the IP Trunk 3.01 (and later) nodes are connected •...
Page 126 Page 126 of 644 ITG engineering guidelines New considerations come into play now when the same corporate network is expected to deliver voice traffic. The intranet introduces impairments, delay, delay variation, and data packet loss, at levels that are higher than those delivered by voice networks.
Page 127 ITG engineering guidelines Page 127 of 644 Figure 24 IP Trunk 3.01 (and later) network engineering process IP Trunk Network Engineering Process Start Forecast IP Trunk traffic Assess WAN resources Capacity available? Measure intranet QoS Within QoS expectation? Implement Further network IP Trunk analysis/design network...
Page 128: Ip Trunk 3.01 (And Later) Traffic Engineering
Page 128 of 644 ITG engineering guidelines Three preliminary steps must be undertaken. 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.
Page 129: Estimate Voice Traffic Calculations
ITG engineering guidelines Page 129 of 644 Traffic forecasting is a process that often requires several tries to achieve satisfactory results. For example, a WAN might not have enough bandwidth to support all the IP trunks required; therefore the codec choice or the number of trunks provisioned must be adjusted.
Page 130 Page 130 of 644 ITG engineering guidelines Refer to Poisson P.01 table to find IP Trunk 3.01 (and later) ports required to provide a blocking Grade of Service of 1% assuming Poisson random distribution of call origination and zero correlation among calls. Note: A lower Grade of Service, such as P.10, may be preferred if overflow routing is available through the PSTN, circuit-switched VPN, or ITG ISL TIE trunks.
Page 131 ITG engineering guidelines Page 131 of 644 Example 1: IP Trunk 3.01 (and later) ports and bandwidth engineering (Silence Suppression enabled) In this configuration example of 120 VoIP users, each user generates four calls using the IP network (originating and terminating) with an average holding time of 150 seconds in the busy hour.
Page 132 Peak hour bandwidth requirement = 722*1.3 = 939 kbit/s This is the spare bandwidth a TLAN subnet requires to transmit the VoIP and fax traffic. Nortel Networks recommends that the TLAN subnet handle IP Trunk 3.01 (and later) traffic exclusively.
Page 133: Calculate The Number Of Ip Trunk 3.01 (And Later) Ports Required
ITG engineering guidelines Page 133 of 644 Calculate the number of IP Trunk 3.01 (and later) ports required IP Trunk 3.01 (and later) TIE trunks are provisioned based on average busy-hour traffic tables, using the calculated amount of voice and fax traffic between IP Trunk 3.01 (and later) nodes.
Page 134 Page 134 of 644 ITG engineering guidelines Table 11 Trunk traffic – Poisson 1% blocking Grade of Service (Part 2 of 2) Trunks Trunks Trunks Trunks Trunks 1565 2184 2816 2847 3166 3488 3810 4134 2879 3198 3520 3843 4167 2910 3230 3552...
Page 135: Calculate Number Of Ip Trunk Cards Required
ITG engineering guidelines Page 135 of 644 Table 12 Trunk traffic – Poisson 10% blocking Grade of Service (Part 2 of 2) Trunks Trunks Trunks Trunks Trunks 1450 2009 2577 1482 2042 2610 1515 2076 2644 2678 3116 3552 3992 4434 2711 3149...
Page 136 30 QoS endpoints, the CPU capacity (real-time capacity) must be considered. Recommendation Nortel Networks strongly recommends implementing suitable QoS mechanisms on any IP network carrying VoIP. Leader and DCHIP card standard configuration rules Leader 0 with no DCHIP and all voice ports configured. Leader 1 with DCHIP supporting all Followers.
Page 137 ITG engineering guidelines Page 137 of 644 Additionally, the DCHIP card sends and receives all D-channel messages from the system to all Follower cards. In a multi-card node, the DCHIP card CPU real-time must be engineered to reserve enough capacity to successfully transmit and receive D-channel messages.
Page 138 Page 138 of 644 ITG engineering guidelines Backup Leader/Follower role The Backup Leader/Follower card roles have no additional real-time impacts over normal call processing, which is primarily governed by the customer traffic profile. If the IP Trunk 3.01 (and later) node is making mostly Gatekeeper-routed calls, there is an increase in call processing, but the effects on the Follower card are minimal.
Page 139: Factors That Effect The Real-Time Capacity
ITG engineering guidelines Page 139 of 644 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.01 (and later) network •...
Page 140: Size Of The Ip Trunk 3.01 (And Later) Network
Page 140 of 644 ITG engineering guidelines Size of the IP Trunk 3.01 (and later) network If QoS is enabled on an IP Trunk 3.01 (and later) network, the size of the network has a direct impact on the real-time capabilities of an IP trunk Leader card and on single card nodes.
Page 141: The Average Hold Time (Aht) And Distribution Of
0% less overhead. Recommendation Nortel Networks recommends that if an IP Trunk 3.01 (and later) node has a mixture of Media Card 32-port trunk cards and ITG-Pentium 24-port trunk cards, ensure that the Leader 0 card is an ITG-Pentium 24-port trunk card.
Page 142 Page 142 of 644 ITG engineering guidelines • 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.
Page 143 Cards 32-port or 16 ITG-Pentium 24-port trunk cards can be supported by one DCHIP card. Recommendation Nortel Networks recommends a node never exceed the ratio of 12 Media Card 32-port trunk cards or 16 ITG-Pentium 24-port trunk cards to one Leader card.
Page 144 Page 144 of 644 ITG engineering guidelines In a multi-card node, do not have the Leader function and DCHIP function on the same IP trunk card, unless all voice channels are disabled on that card. A Leader card needs to have voice channels provisioned on the IP trunk card to receive provisioning for the Gatekeeper, but disabling the voice channels allows the Leader card to handle a significantly higher number of calls/hour.
Page 145 ITG engineering guidelines Page 145 of 644 Table 14 Real-time capacity of an ITG-Pentium 24-port trunk card in the Leader or DCHIP role Voice Number ports of QoS enabled nodes At 1% blocking with x seconds of Average Hold Time Calls/hr Leader (AHT), the minimum number of ITG-Pentium 24-port...
Page 146 Page 146 of 644 ITG engineering guidelines Media Card 32-port trunk card Leader 0 and DCHIP card real-time capacity The Media Card 32-port trunk card is based on the Intel StrongARM CPU. The real-time capacity analysis of the Media Card 32-port Leader 0 card is as follows.
Page 147 The values in the tables are valid for all Voice codecs and voice sample size including G.711, 10 ms voice sample. Recommendation Nortel Networks recommends that traffic on a single card Media Card 32-port trunk card node never exceed the following: •...
Page 148 Page 148 of 644 ITG engineering guidelines In a multi-card node, do not have the Leader function and DCHIP function on the same IP trunk card, unless all voice channels are disabled on that card. A Leader card must have voice channels provisioned on the IP trunk card to receive provisioning for the Gatekeeper, but disabling the voice channels allows the Leader card to handle a significantly higher number of calls/hour.
Page 149 ITG engineering guidelines Page 149 of 644 Table 16 Real-time capacity of a Media Card 32-port trunk card in the Leader role Voice Number ports of QoS enabled nodes At 1% blocking with x seconds of Average Hold Time Calls/hr Leader (AHT), the minimum number of Media Card 32-port network...
Page 150: Calculate Ethernet And Wan Bandwidth Usage
Page 150 of 644 ITG engineering guidelines In order to achieve successful VoIP, a minimum amount of bandwidth must be reserved. Bandwidth is not guaranteed unless QoS mechanisms are implemented. Calculate Ethernet and WAN bandwidth usage Table 18 on page 152 lists the Ethernet and WAN bandwidth use of IP Trunk 3.01 (and later) ports with different codecs with Silence Suppression Disabled.
Page 151 ITG engineering guidelines Page 151 of 644 The engineering procedures for the TLAN subnet and WAN are different. The following calculation procedure is for the TLAN subnet. The modification required for WAN engineering is included in these procedures. IMPORTANT! Voice packets must have priority over data packets. When the WAN route prioritizes voice traffic over data traffic, the route bandwidth can be engineered to 90% loading level;...
Page 152 Page 152 of 644 ITG engineering guidelines Table 18 Silence Suppression disabled TLAN Ethernet and WAN IP bandwidth usage per IP Trunk 3.01 (and later) port (Part 1 of 2) Codec Multi - frame PPP WAN Frame duration Voice/fax Ethernet Full-duplex Bandwidth Relay...
Page 153: Silence Suppression Engineering Considerations
ITG engineering guidelines Page 153 of 644 Table 18 Silence Suppression disabled TLAN Ethernet and WAN IP bandwidth usage per IP Trunk 3.01 (and later) port (Part 2 of 2) Codec Multi - frame PPP WAN Frame duration Voice/fax Ethernet Full-duplex Bandwidth Relay...
Page 154: Fax Engineering Considerations
In those cases, even when Silence Suppression is enabled on the IP trunk card, Nortel Networks recommends using the more conservative bandwidth calculations of Table 18 on page 152...
Page 155: Trunk Anti-Tromboning (Tat) And Trunk Route Optimization (Tro) Considerations
As a fallback TAT validation mechanism, IP Trunk 3.01 (and later) uses the IP Trunk 3.01 validation check of comparing called and calling numbers. IP Peer in CS 1000 Release 2.0, IP Trunk 3.01, BCM 3.0.1, and BCM 3.5 do not support the new TAT validation check comparing EPIDs. Therefore, when interoperating with these systems, IP Trunk 3.01 (and later) falls back to the...
Page 156 When tromboning of IP Trunks occurs due to limited TAT operation with CS 1000 Release 2.0 and BCM 3.5, BCM and IP Peer use H.245 signaling to the IP Trunk 3.01 (and later) node to establish a direct media path between the two tromboned IP Trunks.
Page 157 ITG engineering guidelines Page 157 of 644 In a VoIP network, there are three primary benefits of TAT. As in a TDM network, TAT eliminates tromboning of trunks and frees up valuable trunking resources. TAT provides a method of reducing bandwidth requirements, which can be crucial over a slow WAN link.
Page 158 Telephone B transferring the call to Telephone C. TAT versus TRO Nortel Networks 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.
Page 159: Wan Route Bandwidth Engineering
Site A. If a caller at Site A dials 4000, this can lead to the call orbiting between the two sites. This is commonly referred to as the “Ping-Pong” effect. Therefore, Nortel Networks recommends setting TRMB to NO. WAN route bandwidth engineering After the TLAN subnet traffic is calculated, determine the bandwidth requirement for the WAN.
Page 160 When no agreeable codec is available at both ends, the default codec G.711 is used. Note: Nortel Networks recommends that all cards in an IP Trunk 3.01 (and later) system have the same image. If multiple codec images are used in an IP Trunk 3.01 (and later) network, the calls default to the G.711 group when the originating and destination codecs are different.
Page 161 ITG engineering guidelines Page 161 of 644 Table 20 Example: Determine IP trunk card requirements ITG Site Traffic in CCS ITG Ports IP trunk cards Santa Clara Richardson Ottawa Tokyo Assume that the preferred codec to handle VoIP calls in this network is G.729AB.
Page 162 Page 162 of 644 ITG engineering guidelines The following example illustrates the calculation procedure for Santa Clara and Richardson. The total traffic on this route is 60 CCS. To use the preferred codec of G.729AB with a 30 ms payload, the bandwidth on the WAN is 11.2 kbit/s.
Page 163: Assess Wan Link Resources
ITG engineering guidelines Page 163 of 644 Assess WAN link resources For most installations, IP Trunk 3.01 (and later) traffic will probably be routed over WAN links within the intranet. WAN links are the highest repeating expenses in the network and they often cause capacity problems in the network.
Page 164: Estimate Network Loading Caused By Ip Trunk 3.01 (And Later) Traffic
Page 164 of 644 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%;...
Page 165 ITG engineering guidelines Page 165 of 644 Figure 25 Calculate network load with IP Trunk 3.01 (and later) traffic Ottawa Tokyo Santa Clara Santa Clara/Richardson traffic 60 CCS Ottawa/Tokyo traffic 18 CCS Santa Clara/Tokyo 15 CCS Richardson IP Trunk Node Router 553-IPT9178 Suppose the intranet has a topology as shown in Figure 25 and a prediction...
Page 166: Route Link Traffic Estimation
Page 166 of 644 ITG engineering guidelines To complete this exercise, total the traffic flow for every site pair to calculate the load at each IP Trunk 3.01 (and later) endpoint. Route Link Traffic Estimation Routing information for all source-destination pairs must be recorded as part of the network assessment.
Page 167 ITG engineering guidelines Page 167 of 644 The Traceroute program identifies the intranet links that transmit IP Trunk 3.01 (and later) traffic. For example, if Traceroute of four site pairs yield the results shown in Table 22, then the load of IP Trunk 3.01 (and later) traffic per link can be computed as shown in Table 23.
Page 168: Enough Capacity
Page 168 of 644 ITG engineering guidelines Enough capacity For each link, Table 24 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.
Page 169: Insufficient Link Capacity
ITG engineering guidelines Page 169 of 644 Some network management systems have network planning modules that compute network flows in the manner just described. These modules provide more detailed and accurate analysis, as they can take into account actual node, link, and routing information.
Page 170 This would cause voice packet loss and therefore poor voice quality. Recommendation Nortel Networks 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.01 (and later) node and the intranet-wide consequences if the...
Page 171: Traffic Mix
ITG engineering guidelines Page 171 of 644 Traffic mix Before implementing QoS mechanisms in the network, assess the traffic mix of the network. QoS mechanisms depend on the process and ability to distinguish traffic by class to provide differentiated services. If an intranet is designed to deliver only IP Trunk 3.01 (and later) traffic, and all traffic flows are of equal priority, then there is no need to consider QoS mechanisms.
Page 172: Ip Trunk 3.01 (And Later) Diffserv Support For Ip Qos
Page 172 of 644 ITG engineering guidelines 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.01 (and later) traffic and other traffic marked with this DiffServ/TOS value can be delivered with the goal of meeting this class of traffic’s QoS objectives.
Page 173: Queue Management
ITG engineering guidelines Page 173 of 644 Queue management Queueing delay From “Queuing delay” on page 179, 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.
Page 174: Use Of Frame Relay And Atm Services
Page 174 of 644 ITG engineering guidelines Use of Frame Relay and ATM services IP can be transported over Frame Relay and ATM services, both of which provide QoS-based delivery mechanisms. If the router can discern IP Trunk 3.01 (and later) traffic by inspecting the TOS field or observing the UDP port numbers, it can forward the traffic to the appropriate Permanent Virtual Circuit (PVC) or Switched Virtual Circuit (SVC).
Page 175 2002 for inter-card communication. When using the dialing plan tables to resolve an address for non-call associated signaling, Nortel MCDN messages use UDP port 15000 on the TLAN subnet to communicate with cards on the far end of the network.
Page 176: Qos Fallback Thresholds And Ip Trunk 3.01 (And Later)
Gatekeeper-routed endpoints) is not possible. This is because the calls routed by the Gatekeeper can be directed to a variety of endpoints, some of which might not have direct PSTN connectivity such as a Nortel Networks IP Phone 2004 on a CS 1000S system.
Page 177: Fine-Tune Network Qos
ITG engineering guidelines Page 177 of 644 A well engineered network greatly reduces the need for QoS fallback to PSTN. A well engineered network includes the following features: • implementing network QoS features such as DiffServ and 802.1Q/p to give priority to real-time voice traffic •...
Page 178 Page 178 of 644 ITG engineering guidelines • serialization delay • queuing delay • routing and hop count • IP Trunk 3.01 (and later) system delay Propagation delay Propagation delay is affected by the mileage and medium of links traversed. Within an average-size country, the one-way propagation delay over terrestrial lines is under 18 ms;...
Page 179 ITG engineering guidelines Page 179 of 644 Table 28 shows what the serialization delay for voice packets on a 64 kbit/s and 128 kbit/s link. The serialization delay on higher speed links are considered negligible. Table 28 Serialization delay Serialization Serialization delay over delay over...
Page 180 Page 180 of 644 ITG engineering guidelines The average size of intranet packets carried over WAN links generally is between 250 and 500 bytes. Figure 26 displays the average queueing delay of the network based on a 300-byte average packet size. Figure 26 Queuing delay of various links Queueing delay of various links...
Page 181: Reduce Link Delay
ITG engineering guidelines Page 181 of 644 IP Trunk 3.01 (and later) system delay Together, the transmitting and receiving IP Trunk 3.01 (and later) nodes contribute a processing delay of about 33 ms to the end-to-end delay. This is the amount of time required for the encoder to analyze and packetize speech, and is required by the decoder to reconstruct and de-packetize the voice packets.
Page 182 Page 182 of 644 ITG engineering guidelines Link delay is defined as the time it takes for a voice packet to be queued on the transmission buffer of a link until it is received at the next hop router. Link delay can be reduced by the following: •...
Page 183: Reduce Hop Count
ITG engineering guidelines Page 183 of 644 santa_clara_itg4 (10.3.2.7) 94 ms 97 ms 95 ms 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.
Page 184: Reduce Packet Loss
Page 184 of 644 ITG engineering guidelines Reduce packet loss Packet loss in intranets is generally related to congestion somewhere in the network. Bottlenecks in links are where the packet loss is high because packets get dropped, as the packets are arriving faster than the link can transmit them.
Page 185: Routing Issues
ITG engineering guidelines Page 185 of 644 Routing issues Unnecessary delay can be introduced by routing irregularities. A routing implementation might overlook a substantially better route. A high delay variation can be caused by routing instability, misconfigured routing, inappropriate load splitting, or frequent changes to the intranet. Severe asymmetrical routing results in one site perceiving a poorer QoS than the other site.
Page 186 Page 186 of 644 ITG engineering guidelines The proper time to implement either setting is described as follows: Make the IP Trunk 3.01 (and later) the first-choice, least-cost entry in the route list block. An IP Trunk 3.01 (and later) route should be configured with a higher priority (lower entry number) than the fallback route in the LD 86 Route List Blocks (RLB) of the ESN configuration.
Page 187: Measure Intranet Qos
ITG engineering guidelines Page 187 of 644 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.01 (and later) network:...
Page 188: Set Qos Expectations
Page 188 of 644 ITG engineering guidelines Set QoS expectations The users of corporate voice and data services expect these services to meet some perceived QoS, which in turn influences network design. The goal is to design and allocate enough resources in the network to meet users’ needs. QoS metrics or parameters are what quantifies the needs of the “user”...
Page 189 ITG engineering guidelines Page 189 of 644 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.01 (and later) nodes, interfaces with the end users; voice services offered by the system must meet user-oriented QoS objectives.
Page 190 Fax is more susceptible to packet loss than the human ear is; quality starts to degrade when packet loss exceeds 4%. Nortel Networks recommends that fax services be supported with IP Trunk 3.01 (and later) operating in either the Excellent or Good QoS level.
Page 191 ITG engineering guidelines Page 191 of 644 Figure 29 QoS level with G.711 codec QoS levels with G.711 Poor Fair Good Excellent Packet Loss (%) IP Trunk Description, Installation, and Operation...
Page 192: Obtain Qos Measurement Tools
Page 192 of 644 ITG engineering guidelines Figure 30 QoS level with G.723 codec QoS levels with G.723.1 (6.3 kbps) Very Poor Poor Fair Packet Loss (%) Obtain QoS measurement tools PING and Traceroute are standard IP tools that are usually included with a network host's TCP/IP stack.
Page 193 ITG engineering guidelines Page 193 of 644 PING santa_clara4 (10.3.2.7): 60 data bytes 68 bytes from (10.3.2.7): icmp_seq=0 ttl=225 time=97ms 68 bytes from (10.3.2.7): icmp_seq=0 ttl=225 time=100ms 68 bytes from (10.3.2.7): icmp_seq=0 ttl=225 time=102ms 68 bytes from (10.3.2.7): icmp_seq=0 ttl=225 time=97ms 68 bytes from (10.3.2.7): icmp_seq=0 ttl=225 time=95ms...
Page 194 Page 194 of 644 ITG engineering guidelines So that the delay sample results match what the IP Trunk 3.01 (and later) node can experience, the PING host must be on a working LAN segment attached to the router supporting the IP Trunk 3.01 (and later) node. The selection of destination host is just as important, following these same guidelines for the source host.
Page 195: Measure End-To-End Packet Loss
ITG engineering guidelines Page 195 of 644 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.
Page 196: Network Delay And Packet Loss Evaluation Example
Page 196 of 644 ITG engineering guidelines Late packets Packets that arrived outside of the window allowed by the jitter buffer are discarded by IP Trunk 3.01 (and later). To determine which PING samples to ignore, first calculate the average one-way delay based on all the samples. Add 500 ms to the average.
Page 197: Other Measurement Considerations
ITG engineering guidelines Page 197 of 644 Table 29 Sample measurement results for G.729A codec (Part 2 of 2) Measured Measured one-way Packet loss Expected QoS level delay (ms) (See page 201) Destination pair Mean Mean+σ Mean Mean+σ Mean Mean+σ Santa Clara/ Good Good...
Page 198: Estimate Voice Quality
Page 198 of 644 ITG engineering guidelines If the intranet capacity is tight and the IP Trunk 3.01 (and later) traffic significant, consider making intranet measurements under load. Load can be applied using traffic generator tools. The amount of load should match the IP Trunk 3.01 (and later)-offered traffic estimated in “IP Trunk 3.01 (and later) traffic engineering”...
Page 199 ITG engineering guidelines Page 199 of 644 Refer to Table 33 on page 200 for the translation of R values into user satisfaction levels. Table 30 Impairment factors of codecs Codec Impairment (lc) Codec (msec frames) G.711 G.729A/AB 11 - 20 or 30 G.729A/AB 16 - 40 or 50 G.723.1 (5.3 Kbps)
Page 200 Page 200 of 644 ITG engineering guidelines Table 32 Impairment factors due to packet loss Packet loss (%) Packet Lose Impairment (lp) Table 33 R value translation R Value (lower limit) User Satisfaction Very satisfied Satisfied Some users dissatisfied Many users dissatisfied Nearly all users dissatisfied Not recommended 553-3001-363...
Page 201 1% and 10 ms respectively. The techniques used to determine and apply the information in this table are Nortel Networks proprietary. Table 34 IP Trunk 3.01 (and later) QoS levels (Part 1 of 3)
Page 202 Page 202 of 644 ITG engineering guidelines Table 34 IP Trunk 3.01 (and later) QoS levels (Part 2 of 3) QoS level Network Packet G.711 G.729A/AB G.723.1 (6.3 Kbps) delay (ms) loss (%) 100 – 149 good fair fair good fair poor fair...
Page 203 ITG engineering guidelines Page 203 of 644 Table 34 IP Trunk 3.01 (and later) QoS levels (Part 3 of 3) QoS level Network Packet G.711 G.729A/AB G.723.1 (6.3 Kbps) delay (ms) loss (%) 200 – 249 poor not recommended not recommended poor not recommended not recommended...
Page 204 Page 204 of 644 ITG engineering guidelines Sample scenarios Scenario 1 A local LAN has the following characteristics: • G.711 codec • 20 msec network delay • 0.5% packet loss To calculate R = 94 - lc - ld - lp, use Table 30, Table 31, and Table 32: •...
Page 205: Does The Intranet Meet Expected Ip Trunk 3.01 (And Later) Qos
ITG engineering guidelines Page 205 of 644 Then: R = 94 - 0 - 5 - 4 R = 85 Using Table 34 on page 201, a value of 85 means that the users are satisfied. Scenario 3 A WAN has the following characteristics: •...
Page 206: Ip Trunk 3.01 (And Later) Lan Installation And Configuration
Page 206 of 644 ITG engineering guidelines In order to offer voice and fax services over the intranet, keep the network within a “Good” or “Excellent” QoS level at the Mean+s operating region. Fax services should not be offered on routes that have only “Fair” or “Poor” QoS levels.
Page 207: Ip Trunk Card Connections
ITG engineering guidelines Page 207 of 644 Figure 31 Basic setup of the IP Trunk 3.01 (and later) system IP Trunk node with one Leader, one Backup Leader, and six Follower cards OTM client with IP Trunk management software Router ELAN TLAN subnet Management...
Page 208: Set Up A System With Separate Subnets For Voice And Management
Set up a system with separate subnets for voice and management Recommendation Nortel Networks recommends using separate dedicated VLANs and ELAN and TLAN subnets, separated by a router/Layer 3 switch. Refer to “Set up a system with separate subnets for voice and management” on page 208.
Page 209: Subnet Configurations
ITG engineering guidelines Page 209 of 644 Subnet configurations The following restrictions apply: • The Leader 0 and Leader 1 cards must co-reside on a single TLAN subnet with the Node IP Address. • Follower cards can reside on separate TLAN subnets. •...
Page 210: Selecting Public Or Private Ip Addresses
Page 210 of 644 ITG engineering guidelines Example 2 Valid configuration The following configuration is valid, as the ELAN and TLAN subnets do not overlap. The IP addresses can be split as follows. ELAN IP 10.0.0.136 ELAN GW 10.0.0.129 ELAN Subnet Mask 255.255.255.224 TLAN Node IP 10.0.0.56...
Page 211: Single Subnet Option For Voice And Management
ITG engineering guidelines Page 211 of 644 Some routers and firewalls provide a Network Address Translation (NAT) function that allows the customer to map a registered globally unique public IP address to a private IP address without re-numbering an existing private IP address autonomous domain.
Page 212: Multiple Ip Trunk 3.01 (And Later) Nodes On The Same Elan And Tlan Segments
In test labs, training centers, and trade shows, it is common for destination nodes to be located on the same LAN segment and subnet. IMPORTANT! Do not place other IP devices, either Nortel Networks’ or other vendors’ products, on the same TLAN subnet as the IP Trunk 3.01 (and later) nodes.
Page 213: General Lan Considerations
ITG engineering guidelines Page 213 of 644 General LAN considerations Although the TLAN subnet traffic capacity does not limit IP Trunk 3.01 (and later) network engineering, the IP Trunk 3.01 (and later) network design must take into consideration the limitations of the existing LAN and WAN equipment.
Page 214: Configure The Tlan Subnet Ip Router
Page 214 of 644 ITG engineering guidelines The TLAN subnet must connect to a 10/100BaseT switch. The uplink from the TLAN subnet to the router should be at least 100 Mbps. If the uplink is 100 Mbps, then the maximum number of IP trunk cards allowed on the switch is subject to the limits described in “Calculate Ethernet and WAN bandwidth usage”...
Page 215: Setting Up The Elan Or Management Subnet
ITG engineering guidelines Page 215 of 644 Priority routing for VoIP 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.
Page 216 Recommendation Nortel Networks recommends that any network equipment connected to the ELAN or TLAN subnet be set to Auto-Negotiate for correct operation I/O filter connector The other major TLAN subnet operation problem arises from the standard I/O filter connector in IPE modules on Large Systems.
Page 217 ITG engineering guidelines Page 217 of 644 • The TLAN UTP cabling must meet the UTP CAT5 termination and impedance uniformity standards. • The TLAN UTP cabling must not exceed 50 meters for the ITG-Pentium 24-port trunk card. The TLAN interface can auto-negotiate to 100BaseT full-duplex. To ensure the TLAN subnet can be used for VoIP, do the following: •...
Page 218: Ip Trunk 3.01 (And Later) Dsp Profile Settings
Page 218 of 644 ITG engineering guidelines With standard PCM encoding (G.711 codec), a two-way conversation channel has a rate of 128 kbit/s (64 kbit/s in each direction). The same conversation on WAN, such as T1, only requires a 64 kbit/s channel, because a WAN channel is a full-duplex channel.
Page 219: Payload Size
3.01 (and later) can deliver good QoS but loads less than 10 kbit/s per port on the intranet. Nortel Networks recommends that all the nodes in the IP Trunk 3.01 (and later) network have a common preferred codec. From a network planning perspective, this provides a predictable load on the intranet since all calls will negotiated on one codec.
Page 220: Jitter Buffer Parameters (Voice Playout Delay)
Page 220 of 644 ITG engineering guidelines Jitter buffer parameters (voice playout delay) There are three parameters that control the size of the jitter buffer in the destination IP Trunk 3.01 (and later) node. Voice playout nominal delay. This can range from twice the payload size to 10 times, subject to a maximum of 320 ms.
Page 221 ITG engineering guidelines Page 221 of 644 voice packets are sent until the silence period is broken. There are two parameters that control Silence Suppression, as follows: Idle noise level. This is set at a default level of –65 dBm0. Voice activity detection threshold.
Page 222: Fallback Threshold
Page 222 of 644 ITG engineering guidelines Fallback threshold There are two parameters, the receive fallback threshold and the transmit fallback threshold, which can be set on a per site pair basis. “Set QoS expectations” on page 188 and “Measure intranet QoS” on page 187 sections describe the process of determining the appropriate QoS level for operating the IP Trunk 3.01 (and later) network.
Page 223: Set Itg Qos Objectives
ITG engineering guidelines Page 223 of 644 When operating VoIP services, the customer’s organization needs to incorporate additional monitoring and planing processes, as follows: • Collect, analyze, and trend IP Trunk 3.01 (and later) traffic patterns. • Monitor and trend one-way delay and packet loss. •...
Page 224: Intranet Qos Monitoring
Page 224 of 644 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.
Page 225: Snmp Network Management
ITG engineering guidelines Page 225 of 644 At the end of the month, analyze each site’s QoS information. Table 36 provides a sample. Table 36 QoS monitoring One-way delay Packet loss Mean+σ (ms) Mean+σ (%) Last Current Last Current Last Current Site pair period...
Page 226: Ip Trunk 3.01 (And Later) Network Inventory And Configuration
3.01 (and later) SNMP traps and structure of management information is provided within the IP Trunk 3.01 (and later) Management Information Base (MIB). To obtain the IP Trunk 3.01 (and later) MIB, contact the Nortel Networks representative. SNMP Agent support is provided in OTM 2.1 (and later). This integrates OTM with existing NMS software, which allows alarms collected from an IP Trunk 3.01 (and later) node and the system to be forwarded to the NMS from...
Page 227: User Feedback
ITG engineering guidelines Page 227 of 644 — 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.
Page 228 Page 228 of 644 ITG engineering guidelines 553-3001-363 Standard 2.00 September 2004...
Page 229: Otm 2.1 (And Later) Management And Configuration Of Ip Trunk 3.01 (And Later)
Page 229 of 644 OTM 2.1 (and later) management and configuration of IP Trunk 3.01 (and later) Contents This section contains information on the following topics: Introduction ..........OTM 2.1 (and later) ITG Engineering rules .
Page 230: Otm 2.1 (And Later) Itg Engineering Rules
OTM 2.1 (and later) Alarm Notification can receive a maximum of 20 SNMP traps per second (based on the recommended PC configuration). In large networks, Nortel Networks recommends that multiple OTM 2.1 (and later) PCs be used to collect traps from the IP trunk cards, each PC supporting one or more IP Trunk 3.01 (and later) nodes.
Page 231: Otm 2.1 (And Later) Remote Access Configuration
OTM 2.1 (and later) management and configuration of IP Trunk 3.01 (and later) Page 231 of 644 OTM 2.1 (and later) with Windows 98, Windows NT 4.0, and Windows 2000 clients are supported on the following platforms: • Windows 2000 •...
Page 232 OTM 2.1 (and later) PC on the IP Trunk 3.01 (and later) Management LAN. The IP address provided by the modem router (for example, Nortel Networks Netgear RM356 Modem Router) to the remote OTM 2.1 (and later) PC is configured in the modem router and in the SNMP Manager’s list of the IP trunk cards.
Page 233: Otm 2.1 (And Later) Pc Description
OTM 2.1 (and later) management and configuration of IP Trunk 3.01 (and later) Page 233 of 644 In this case, a local OTM 2.1 (and later) 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 OTM 2.1 (and later) PC since management and alarm traffic would only travel over the private IP Trunk 3.01 (and later) Management LAN.
Page 234: Otm 2.1 (And Later) Pc Hardware And Software Requirements
Intel Pentium II Processor 400 MHz CPU minimum; Intel Pentium III Processor 600 MHz CPU recommended • 2 GB or larger hard disk drive with 1000 MB or more free space. Refer to the system datastore column in the hard drive requirements in Table 37 page 235.
Page 235: Hard Drive Requirements
OTM 2.1 (and later) management and configuration of IP Trunk 3.01 (and later) Page 235 of 644 • dongle (for server or stand-alone only) • Windows-compatible mouse (PS/2 mouse preferred to free up a PC serial port) CAUTION Do not install OTM 2.1 (and later) on a Windows NT or Windows 2000 system that is configured as a Primary Domain Controller (PDC).
Page 236 Page 236 of 644 OTM 2.1 (and later) management and configuration of IP Trunk 3.01 (and later) Table 37 Hard drive capacity for OTM 2.1 (and later) applications (Part 2 of 2) OTM 2.1 (and later) application Program store Data store Traffic Analysis 5 MB System dependent:...
Page 237: Install And Configure Ip Trunk 3.01
Page 237 of 644 Install and configure IP Trunk 3.01 (and later) node Contents This section contains information on the following topics: Introduction ..........Before you begin .
Page 238 Page 238 of 644 Install and configure IP Trunk 3.01 (and later) node Install filter and NTND26 cable (for MSDL and DCHIP cards in same Large System equipment row) ....Install filter and NTND26 cable (for MSDL and DCHIP cards in different Large System equipment rows) .
Page 239: Introduction
Install and configure IP Trunk 3.01 (and later) node Page 239 of 644 Add an IP Trunk 3.01 (and later) node and configure general node properties ..........Single vs.
Page 240: Before You Begin
Install OTM 2.1 (and later). Make sure the ITG ISDN IP Trunk and Alarm Management applications are installed. Upgrade the system software to CS 1000 Release 4.0. IP Trunk 3.01 (and later) requires packages 145 (ISDN) and 147 (ISL). Install additional software packages, such as Package 148 NTWK, as required for advanced ISDN features.
Page 241: Installation Procedure Summary
Install and configure IP Trunk 3.01 (and later) node Page 241 of 644 Installation procedure summary Table 38 lists the procedures required to install and configure an IP Trunk 3.01 (and later) node. Complete all installation and configuration tasks before transmitting the configuration data to the IP trunk cards.
Page 242 Page 242 of 644 Install and configure IP Trunk 3.01 (and later) node Table 38 Installation procedures (Part 2 of 3) Step Procedure See page Configure IP Trunk 3.01 (and later) data in OTM 2.1 (and later). Add an IP Trunk 3.01 (and later) node in OTM 2.1 (and later) manually.
Page 243: Esn Installation Summary
Install and configure IP Trunk 3.01 (and later) node Page 243 of 644 Table 38 Installation procedures (Part 3 of 3) Step Procedure See page Check and download IP trunk card software in OTM 2.1 (and later). Transmit new software to the IP trunk cards. Upgrade the DCHIP PC Card.
Page 244: Create The Ip Trunk 3.01 (And Later) Installation Summary Sheet
Page 244 of 644 Install and configure IP Trunk 3.01 (and later) node • In LD 87, provision the CDP (Coordinated Dialing Plan) entries, as required – LSC, DSC, and TSC. Enter the RLI intended for this code. • In LD 90, provision the NPA, NXX, LOC, SPN, or other entries as required.
Page 245 Install and configure IP Trunk 3.01 (and later) node Page 245 of 644 Table 39 IP Trunk 3.01 (and later) Installation Summary Sheet Site_________________ System_________________ Customer_________ Node Number_________ TLAN Node IP address_____________________________________________ TLAN gateway (router)________________TLAN subnet mask__________________ ELAN gateway (router)________________ELAN subnet mask__________________ DCHIP Mgmt.
Page 246: Channel Identifier Planning
Page 246 of 644 Install and configure IP Trunk 3.01 (and later) node 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.
Page 247 Install and configure IP Trunk 3.01 (and later) node Page 247 of 644 Table 40 Mapping of unit number to ISL Channel number – one card in system (Part 2 of 2) Unit number (from TN) ISL Channel number IP Trunk Description, Installation, and Operation...
Page 248 Page 248 of 644 Install and configure IP Trunk 3.01 (and later) node Single card, sequential numbering, no gaps – Media Card 32-port trunk card This is an example using a Media Card 32-port trunk card. The first channel number can be any value, as long as the maximum is less than or equal to the maximum value of the ISL channel –...
Page 249 Install and configure IP Trunk 3.01 (and later) node Page 249 of 644 Table 41 Mapping of unit number to ISL Channel number – one card in system (Part 2 of 2) Unit number (from TN) ISL Channel number Two cards, sequential numbering, gap left for expansion This example is for two ITG-Pentium 24-port trunk cards.
Page 250 Table 42 maps the unit number to the ISL channel number for a two ITG-Pentium 24-port trunk cards with an eight channel gap between cards. Nortel Networks recommends this configuration as it makes it easy to replace an ITG-Pentium 24-port trunk card with a Media Card 32-port trunk card, without affecting the other card.
Page 251 Install and configure IP Trunk 3.01 (and later) node Page 251 of 644 Table 42 Mapping of unit number to ISL Channel number – two cards in system and expansion gap (Part 2 of 3) Unit number (from TN) ISL Channel number 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).
Page 252 Page 252 of 644 Install and configure IP Trunk 3.01 (and later) node Table 42 Mapping of unit number to ISL Channel number – two cards in system and expansion gap (Part 3 of 3) Unit number (from TN) ISL Channel number 553-3001-363 Standard 2.00 September 2004...
Page 253: Incorrect Isl Channel Numbering Plans
Install and configure IP Trunk 3.01 (and later) node Page 253 of 644 Incorrect ISL channel numbering plans This section describes numbering plan errors. Gaps in ISL channel numbering sequence Table 43 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.
Page 254 Page 254 of 644 Install and configure IP Trunk 3.01 (and later) node Table 44 Channel numbering error – decreasing channel number sequence Unit number (from TN) ISL Channel number Overlapping channel numbers Do not provision the ISL channel numbers on both cards with the same channel numbers.
Page 255: Install And Cable Ip Trunk 3.01 (And Later) Cards
Install and configure IP Trunk 3.01 (and later) node Page 255 of 644 Install and cable IP Trunk 3.01 (and later) cards Card installation procedure CAUTION WITH ESDS DEVICES Use ESD precautions when unpacking the hardware and unpacking the cards. Place each IP trunk card is placed in the Meridian 1 or CS 1000M system and record the TN, management MAC address and the card density on the IP Trunk 3.01 (and later) Installation Summary Sheet.
Page 256 Page 256 of 644 Install and configure IP Trunk 3.01 (and later) node Note 1: 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.
Page 257 Install and configure IP Trunk 3.01 (and later) node Page 257 of 644 Procedure 7 Installing and cabling the ITG-Pentium 24-port trunk card Identify the IPE card slots selected for the IP trunk card(s). Use the recorded information from the IP Trunk 3.01 (and later) Installation Summary Sheet (Table 39 on page 245).
Page 258 Page 258 of 644 Install and configure IP Trunk 3.01 (and later) node Figure 34 DCHIP PC Card and NTCW84EA pigtail cable 24-port Daughterboard NTCW84EA Pigtail Cable DCHIP PC Card Pin header Pull the top and bottom locking devices away from the IP trunk card faceplate.
Page 259: Install Ntcw84Ja Large System I/O Panel 50-Pin Filter Adapter
Install and configure IP Trunk 3.01 (and later) node Page 259 of 644 Note 2: Observe the IP trunk card Faceplate Maintenance display to see startup self-test results and status messages. A display of the type “F:xx” indicates a failure. Some failures indicate that the card must be replaced. “F:10”...
Page 260: Remove Existing I/O Panel Filter Adapter
Page 260 of 644 Install and configure IP Trunk 3.01 (and later) node For Cabinet systems, the standard I/O filter connector already supports 100BaseTX. CAUTION For Large Systems manufactured during 1998-1999 and shipped in North America, the IPE modules have the NT8D81BA Backplane to I/O Panel ribbon cable assembly with a non-removable Filter Connector.
Page 261 Install and configure IP Trunk 3.01 (and later) node Page 261 of 644 Unscrew the existing filter adapter from the I/O panel. There is one screw on the lower front of the adapter and one screw on the upper back of the adapter.
Page 262: Install Ntmf94Ea And Ntcw84Ka Cables
Page 262 of 644 Install and configure IP Trunk 3.01 (and later) node For more detailed cabling information and procedures for replacing the NT8D81BA with the NT8D81AA, see “Patches and advisements” on page 569. Install NTMF94EA and NTCW84KA cables The Media Card 32-port and ITG-Pentium 24-port trunk card supports a one-cable solution for access to the TLAN subnet, ELAN subnet, and serial ELAN Ethernet Ports.
Page 263 Install and configure IP Trunk 3.01 (and later) node Page 263 of 644 Figure 36 NTCW84KA ELAN, TLAN, DCH, and serial cable Mounting Screw Shielded RJ-45 Cable Shielded 25-Pair Amphenol Connector Shielded RJ-45 Mating Coupler To Hub Ferrite To Hub 9 Pin D-Sub Female 15 Pin D-Sub...
Page 264: Install The Ntmf94Ea Cable (For Non-Dchip Cards)
Page 264 of 644 Install and configure IP Trunk 3.01 (and later) node Install the NTMF94EA cable (for non-DCHIP cards) Follow the steps in Procedure 10 to install the NTMF94EA cable for non-DCHIP cards. Procedure 10 Installing the NTMF94EA cable Connect the NTMF94EA cable (see Figure 37 on page 265) to the I/O...
Page 265: Install Shielded Voice Interface (Tlan Subnet) Cable
Install and configure IP Trunk 3.01 (and later) node Page 265 of 644 Figure 37 NTMF94EA ELAN, TLAN and serial port cable Mounting Screw Shielded 25-pair Amphenol connector Shielded RJ-45 Mating Coupler To Hub Ferrite Shielded RJ45 Cable To Hub 9 Pin D-Sub Female 553-ITG0006...
Page 266: Install Shielded Management Interface (Elan Subnet) Cable
Page 266 of 644 Install and configure IP Trunk 3.01 (and later) node For DCHIP cards Connect a shielded CAT 5 LAN cable from the TLAN hub to the R-J45 coupler on the NTCW84KA TLAN connector. For non-DCHIP cards Connect a shielded CAT 5 LAN cable from the TLAN hub to the RJ-45 coupler on the NTMF94EA TLAN connector.
Page 267: D-Channel Cabling For The Nt0961Aa Itg-Pentium 24-Port Trunk Card
Install and configure IP Trunk 3.01 (and later) node Page 267 of 644 D-channel cabling for the NT0961AA ITG-Pentium 24-Port trunk card In this section, check, and reset if necessary, MSDL switch settings, install a filter (if required for the installation) and install the cable that connects the MSDL or SDI/DCH card to the IP trunk card that provides the DCH interface.
Page 268: Install Filter And Ntnd26 Cable (For Msdl And Dchip Cards In Same Large System Equipment Row)
Page 268 of 644 Install and configure IP Trunk 3.01 (and later) node Install filter and NTND26 cable (for MSDL and DCHIP cards in same Large System equipment row) Follow the steps in Procedure 11 to install the filter and NTND26 cable for MSDL and DCHIP cards in same Large System equipment row.
Page 269 Install and configure IP Trunk 3.01 (and later) node Page 269 of 644 Figure 38 15-pin filter connector installation System I/O Panel NTND26AA Cable insertion Mounting screw NTMF04BA insertion System Backplane Side (Inside I/O Panel) Exterior side of system (to MDF, and so on) 553-IPT0010 IP Trunk Description, Installation, and Operation...
Page 270: Install Filter And Ntnd26 Cable (For Msdl And Dchip Cards In Different Large System Equipment Rows)
Page 270 of 644 Install and configure IP Trunk 3.01 (and later) node Figure 39 NTND26 cable routing diagram Cable Channel Cover Bracket Card Power MSDL NTND26AA XNET Network Shelf Supply Card Cable Routing Channel 553-IPT0011 Connect the DCH (P5) connector of the NTCW84KA to the outward side of the 15-pin I/O panel filter connector.
Page 271: Small System Cable Installation
Install and configure IP Trunk 3.01 (and later) node Page 271 of 644 Procedure 12 Installing the filter and NTND26 cable for MSDL and DCHIP cards in different Large System equipment rows Install the bracket for the 15-pin I/O panel filter connector in the J16, J17, J37 or J38 I/O panel opening of the I/O panel of the Network Module or Core/Net Module that contains the MSDL card.
Page 272 Page 272 of 644 Install and configure IP Trunk 3.01 (and later) node Procedure 13 Installing cables on Small Systems Set the switches and jumper plugs in the NTAK02 SDI/DCH card as shown. See Table 46 and Table 47. Table 46 NTAK02 SDI/DCH switch settings for IP Trunk 3.01 (and later) DCHIP Port 1 SW 1-1...
Page 273: Install The Serial Cable
Install and configure IP Trunk 3.01 (and later) node Page 273 of 644 If the DCHIP card is installed in the expansion cabinet, then use NTWE04AC SDI/DCH Extension Cable (10 ft) from the NTCW84KA DCH (P5) connector to the NTAK19FB D-Channel port connector for Port 1 or Port 3.
Page 274: Cabling For The Media Card 32-Port Trunk Card
Page 274 of 644 Install and configure IP Trunk 3.01 (and later) node Cabling for the Media Card 32-port trunk card This section describes the cabling necessary to install the Media Card 32-port trunk card. ELAN and TLAN interfaces The Media Card 32-port trunk card supports a single connector solution for access to the TLAN and ELAN Ethernet Ports.
Page 275: Itg Card Adapter Elan/Tlan (L-Adapter)
Install and configure IP Trunk 3.01 (and later) node Page 275 of 644 Figure 40 EMC kit deployment ITG Card Adapter ELAN/TLAN Serial/maintenance cable ELAN cable To LAN/hub cable tie TLAN 3 in cable snap-on ferrite EMC Kit Deployment ITG Card Adapter ELAN/TLAN (L-adapter) The L-adapter routes the signals to the following ports: •...
Page 276 Page 276 of 644 Install and configure IP Trunk 3.01 (and later) node Install the adapter securely to ensure an active connection. Figure 41 ITG card adapter ELAN/TLAN (L-adapter) TLAN RJ-45 ELAN RJ-45 LAN socket LAN socket RS-232 Connector Identification Label 50-pin connector 553-3001-363 Standard 2.00...
Page 277 Install and configure IP Trunk 3.01 (and later) node Page 277 of 644 Figure 42 shows the adapter installed in a Large System with a securing screw and tie wrap. Figure 42 ITG card adapter ELAN/TLAN (Large system) I/O Panel Filtered connector Tip &...
Page 278 Page 278 of 644 Install and configure IP Trunk 3.01 (and later) node To install the adapter in a Small System, use a securing screw and retaining bracket. See Figure 43. Figure 43 ITG card adapter ELAN/TLAN fitted to a Meridian 1 Option 11C Cabinet/ CS 1000M Cabinet Retaining bracket 553-3001-363 Standard 2.00...
Page 279 Install and configure IP Trunk 3.01 (and later) node Page 279 of 644 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. Figure 44 ITG card adapter ELAN/TLAN fitted to a Meridian 1 PBX 11C Chassis/CS 1000M Chassis Securing screw Hook&loop tape...
Page 280: Rs-232 Maintenance Port
Page 280 of 644 Install and configure IP Trunk 3.01 (and later) node RS-232 maintenance port The RS-232 maintenance port provides access to the Media Card 32-port trunk card command prompt for monitoring and maintenance purposes, such as upgrades and debugging. This port is available at the 9-pin connector on the ITG Card Adapter ELAN/TLAN (L-adapter) subnet and at the mini-DIN socket on the faceplate.
Page 281 Install and configure IP Trunk 3.01 (and later) node Page 281 of 644 Figure 45 NTMF29BA PC Card DCHIP cable installation DSP Module Media Card 32 Port Port 0 of trunk card DCHIP Card screw assembly DCHIP bracket DCHIP Card DCHIP Cable CFlash Card Assembly...
Page 282: Dchip Cable Routing - Large Systems
Page 282 of 644 Install and configure IP Trunk 3.01 (and later) node Fit the clamp over the PC Card connector and into the bracket. Ensure that the cable is fitted through the clamp, then secure it to the bracket with the attached screw.
Page 283 Install and configure IP Trunk 3.01 (and later) node Page 283 of 644 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.
Page 284: Dchip Cable Routing Meridian 1 Option 11C Cabinet/Cs 1000M Cabinet
Page 284 of 644 Install and configure IP Trunk 3.01 (and later) node DCHIP Cable Routing Meridian 1 Option 11C Cabinet/CS 1000M Cabinet The following cables are specific to Meridian 1 Option 11C Cabinet/CS 1000M Cabinets. Cable connection details are shown in Figure 48.
Page 285: Other Components
Install and configure IP Trunk 3.01 (and later) node Page 285 of 644 NTAK19BA four-port SDI/DCH cable The NTAK 19BA cable is an Option 11C MDF cable for interfacing to the 4-port NTAK02 SDI/DCH card. Other components For Large Systems, I/O panel 50-pin filtered adapters NTCW84JA are required for 100BaseT TLAN subnet operation.
Page 286 Page 286 of 644 Install and configure IP Trunk 3.01 (and later) node Procedure 16 Connecting the Media Card 32-port trunk card modem Use a standard serial cable and establish communication with the modem from a PC. Use the following settings: •...
Page 287 Install and configure IP Trunk 3.01 (and later) node Page 287 of 644 Figure 49 Wiring specifications 25-way male 9-way male (modem) (to media card) SGND [7] SGND [20] End of Procedure IP Trunk Description, Installation, and Operation...
Page 288: Configure Ip Trunk 3.01 (And Later) Data
Page 288 of 644 Install and configure IP Trunk 3.01 (and later) node 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.
Page 289 Install and configure IP Trunk 3.01 (and later) node Page 289 of 644 LD 17 – Configure the ISL D-channel for the DCHIP card (Large Systems) (Part 2 of 3) Prompt Response Description PORT Port number for MSDL card, where: x = 0 –...
Page 290 Page 290 of 644 Install and configure IP Trunk 3.01 (and later) node LD 17 – Configure the ISL D-channel for the DCHIP card (Large Systems) (Part 3 of 3) Prompt Response Description PARM (RS422 DTE) The RS-422 parameters are established with switch settings on the MSDL card.
Page 291 Install and configure IP Trunk 3.01 (and later) node Page 291 of 644 LD 17 – Configure the ISL D-channel for the DCHIP card (Small Systems) (Part 2 of 3) Prompt Response Description CTYP Card Type. DCHI SDI/DCH card (configure the option switches and jumper straps on the SDI/DCH for RS422 DTE mode operation.
Page 292: Configure The Isl D-Channel On The Meridian 1/Cs 1000M For The Dchip Card For Ip Trunk 3.01 (And Later)
Page 292 of 644 Install and configure IP Trunk 3.01 (and later) node LD 17 – Configure the ISL D-channel for the DCHIP card (Small Systems) (Part 3 of 3) Prompt Response Description Release ID of PBX at the far end of the D-Channel.
Page 293 Install and configure IP Trunk 3.01 (and later) node Page 293 of 644 LD 17 – Configure the ISL D-channel for the DCHIP card (Large and Small Systems) (Part 2 of 2) Prompt Response Description Network Group number = 0 – 4. Applies to Meridian 1 PBX 81C CP PII/CS 1000M MG without Fiber Network Fabric (FNF) only.
Page 294: Configure Isdn Feature In Customer Data Block
Page 294 of 644 Install and configure IP Trunk 3.01 (and later) node Configure ISDN feature in Customer Data Block Use LD 15 to configure the ISDN feature in the Customer Data Block. LD 15 – Configure ISDN feature in Customer Data Block (Part 1 of 2) Prompt Response Description...
Page 295: Configure Ip Trunk 3.01 (And Later) Tie Trunk Routes
Install and configure IP Trunk 3.01 (and later) node Page 295 of 644 LD 15 – Configure ISDN feature in Customer Data Block (Part 2 of 2) 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...
Page 296 Page 296 of 644 Install and configure IP Trunk 3.01 (and later) node LD 16 – Configure the IP Trunk 3.01 (and later) TIE Trunk Route Data Block (Part 2 of 5) Prompt Response Description IP TRUNK 16-character designator is “IP TRUNK” Specific description if more than one IP Trunk 3.01 (and later) route exists.
Page 297 Install and configure IP Trunk 3.01 (and later) node Page 297 of 644 LD 16 – Configure the IP Trunk 3.01 (and later) TIE Trunk Route Data Block (Part 3 of 5) Prompt Response Description Meridian Customer Defined Network (MCDN) is required for Small systems.
Page 298 Page 298 of 644 Install and configure IP Trunk 3.01 (and later) node LD 16 – Configure the IP Trunk 3.01 (and later) TIE Trunk Route Data Block (Part 4 of 5) Prompt Response Description INAC (NO) YES INAC stands for automatic insertion of the ESN access code on incoming calls, according to ISDN call types corresponding to NPA NXX INTL SPN LOC, for example.
Page 299 Install and configure IP Trunk 3.01 (and later) node Page 299 of 644 LD 16 – Configure the IP Trunk 3.01 (and later) TIE Trunk Route Data Block (Part 5 of 5) Prompt Response Description CNTL NEDC Near End Disconnect Control from either originating or terminating side.
Page 300: Configure Media Card 32-Port And Itg-Pentium 24-Port Trunk Cards And Units For Ip Trunk Route
Page 300 of 644 Install and configure IP Trunk 3.01 (and later) node Configure Media Card 32-port and ITG-Pentium 24-port trunk cards and units for IP Trunk Route Use LD 14 to configure the Media Card 32-port and ITG-Pentium 24-port trunk cards and units.
Page 301 Install and configure IP Trunk 3.01 (and later) node Page 301 of 644 LD 14 – Configure Media Card 32-port and ITG-Pentium 24-port trunk cards and units (Part 2 of 5) Prompt Response Description Terminal number l s c u Format for Large System, Call Server 1000E, and Media Gateway 1000E, where l = loop, s = shelf, c = card, u = unit...
Page 302 Page 302 of 644 Install and configure IP Trunk 3.01 (and later) node LD 14 – Configure Media Card 32-port and ITG-Pentium 24-port trunk cards and units (Part 3 of 5) Prompt Response Description CUST Customer number as defined in LD 15. RTMB Route number and Member Number 0-511 1-4000...
Page 303 Install and configure IP Trunk 3.01 (and later) node Page 303 of 644 LD 14 – Configure Media Card 32-port and ITG-Pentium 24-port trunk cards and units (Part 4 of 5) Prompt Response Description CHID First Channel ID for unit 0 on this IP trunk card, where: xxx = 1 - 382 for the ITG-Pentium 24-port trunk card and the Media Card 32-port trunk card...
Page 304 Page 304 of 644 Install and configure IP Trunk 3.01 (and later) node LD 14 – Configure Media Card 32-port and ITG-Pentium 24-port trunk cards and units (Part 5 of 5) Prompt Response Description STRI Start Arrangement Incoming. Wink Start is preferred for IP Trunk 3.01 (and later).
Page 305: Configure Dialing Plans Within The Corporate Network
Install and configure IP Trunk 3.01 (and later) node Page 305 of 644 Configure dialing plans within the corporate network Configure the dialing plan by programming LDs 86, 87, and 90 as required. Configure the Meridian 1/CS 1000M ESN by creating or modifying data blocks in LDs 86, 87, and 90, as required.
Page 306: Periods On The Ip Data Network
Page 306 of 644 Install and configure IP Trunk 3.01 (and later) node Turn off IP Trunk 3.01 (and later) route during peak traffic periods on the IP data network Based on site data, if fallback routing occurs frequently and consistently for a data network during specific busy hours (for example, every Monday 10-11am, Tuesday 2-3pm), these hours should be excluded from the RLB to maintain a high QoS for voice services.
Page 307 ESN5 inserts the NCOS prefix ahead of the dialed numbers. If ESN5 signaling is to be used, it must be provisioned on both the IP Trunk cards and the Meridian 1/CS 1000 M Route Data Block (RDB) for that node. However, this does not guarantee a satisfactory NCOS value. For example, the network may contain some ITG Trunk 1.0 basic trunk signaling nodes or...
Page 308 SL1 ESN5. In this case, the originator inserts the ESN5 prefix. Remote nodes calling an ESN5 IP Trunk 3.01 (or later) node using the Nortel Networks interoperability non-standard data format, if the originating call does not use ESN5. In this case, the destination (IP Trunk or IP Peer) inserts the ESN5 prefix.
Page 309 Install and configure IP Trunk 3.01 (and later) node Page 309 of 644 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).
Page 310 Page 310 of 644 Install and configure IP Trunk 3.01 (and later) node LD 86 – Configure Electronic Switched Network (ESN) (Part 2 of 2) Prompt Response Description One-or-two digit NARS/BARS Access Code 1. One-or-two digit NARS Access Code 2. TGAR (NO) YES Check for Trunk Group Access Restrictions on...
Page 311 Install and configure IP Trunk 3.01 (and later) node Page 311 of 644 LD 86 – Configure Route List Block with Step Back on Congestion on ISDN (Part 2 of 2) Prompt Response Description 0-511 Range for Large System, Call Server 1000E, and Media Gateway 1000E 0-127 Range for Small System, CS 1000S system,...
Page 312 Page 312 of 644 Install and configure IP Trunk 3.01 (and later) node LD 87 – Configure the Co-ordinated Dialing Plan (CDP) Prompt Response Description Add new data. CUST Customer number as defined in LD 15. FEAT Coordinated Dialing Plan. TYPE Distant Steering Code.
Page 313: Disable The Media Card 32-Port And Itg-Pentium
Install and configure IP Trunk 3.01 (and later) node Page 313 of 644 LD 90 – Configure dialing plan (Part 2 of 2) Prompt Response Description Route List Index created in LD 86. Disable the Media Card 32-port and ITG-Pentium 24-port trunk cards In order to transmit the card properties from OTM 2.1 (and later) to the Media Card 32-port and ITG-Pentium 24-port trunk cards, the IP Trunk 3.01 (and...
Page 314: Configure Ip Trunk 3.01 (And Later) Data In Otm 2.1 (And Later)
Page 314 of 644 Install and configure IP Trunk 3.01 (and later) node Configure IP Trunk 3.01 (and later) data in OTM 2.1 (and later) Before the IP Trunk 3.01 (and later) data is configured in OTM, 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.
Page 315: Add An Ip Trunk 3.01 (And Later) Node And Configure General Node Properties
Install and configure IP Trunk 3.01 (and later) node Page 315 of 644 After adding a new IP Trunk 3.01 (and later) node on the OTM PC, the dialing plans for all existing IP Trunk 3.01 (and later) nodes must be manually updated to include the destination node dial plan digits entries for the new IP Trunk 3.01 (and later) node.
Page 316 Page 316 of 644 Install and configure IP Trunk 3.01 (and later) node Figure 50 Add ITG Node window In the Add ITG Node window, keep the default selections Meridian 1 and Define the node configuration manually. Click OK. The New ITG Node –...
Page 317 Install and configure IP Trunk 3.01 (and later) node Page 317 of 644 Figure 51 General tab Set node location properties Define the Node Location properties: select the OTM site, OTM system, Customer, and Node number from the drop-down lists. Note: The site name, system name, and Customer must exist in the OTM Navigator before a new IP Trunk 3.01 (and later) node can be added.
Page 318: Single Vs. Separate Tlan And Elan Subnets
Install and configure IP Trunk 3.01 (and later) node Single vs. separate TLAN and ELAN subnets Recommendation Nortel Networks recommends that separate TLAN and ELAN subnets be used for the IP Trunk 3.01 (and later) voice and management networks (TLAN and ELAN subnets).
Page 319: Configure Network Connections
Install and configure IP Trunk 3.01 (and later) node Page 319 of 644 Configure Network Connections Follow the steps in Procedure 18 to configure the network connections. Procedure 18 Configuring network connections Decide subnet settings: If using separate subnets for the voice (TLAN subnet) and management (ELAN subnet) networks, accept the default setting Use separate subnets for voice and management check box.
Page 320: Configure Card Properties
Page 320 of 644 Install and configure IP Trunk 3.01 (and later) node Configure card properties Procedure 19 explains how to configure the IP trunk card roles, IP addresses, TN, card density and D-Channel settings. Each IP Trunk 3.01 (and later) node requires a Leader 0 card and one DCHIP card (which can be Leader 0) and can have a Leader 1 card, one or more Follower cards, and additional DCHIP cards (which can be Leader 1 or Follower cards).
Page 321 Install and configure IP Trunk 3.01 (and later) node Page 321 of 644 Figure 52 Configuration tab Note 1: The TLAN Node IP address on the General tab and the TLAN IP and TLAN gateway IP addresses for Leader 0 and Leader 1 on the Card Configuration tab must be on the same TLAN (voice) subnet.
Page 322 Page 322 of 644 Install and configure IP Trunk 3.01 (and later) node If Use separate subnets in the General tab was unchecked earlier, perform steps a and b: Enter the Management IP address. Enter the Management MAC address. It is the motherboard Ethernet address.
Page 323 Page 323 of 644 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 Networks IP Telephony Connection Manager. Use H.323 V2 node capability for these nodes.
Page 324: Configure Dsp Profiles For The Ip Trunk 3.01 (And Later) Node
Page 324 of 644 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 to select a DSP profile, set Profile Options and Codec Options and, if required, modify default DiffServ/TOS values from 0.
Page 325 Install and configure IP Trunk 3.01 (and later) node Page 325 of 644 Figure 53 DSP Profile – General tab Click the Profile Options tab. See Figure 54 on page 326. This tab displays the default General and FAX options values according to the selected DSP profile.
Page 326 Page 326 of 644 Install and configure IP Trunk 3.01 (and later) node Figure 54 DSP Profile – Profile Options tab Change the General and FAX option parameters, if required. To revert to the default settings, click Reset Defaults. CAUTION The default DSP Profile Option settings for each codec are appropriate for most applications.
Page 327 Install and configure IP Trunk 3.01 (and later) node Page 327 of 644 Figure 55 DSP Profile – Codec Options tab 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.
Page 328 Page 328 of 644 Install and configure IP Trunk 3.01 (and later) node To turn off a codec, click the codec and uncheck the checkbox. To change the preferred order of codec selection, for outgoing calls, if required, select the codec and click the Move Up and Move Down buttons.
Page 329: Configure Snmp Traps/Routing And Ip Addresses Tab
Install and configure IP Trunk 3.01 (and later) node Page 329 of 644 Configure SNMP Traps/Routing and IP addresses tab In this procedure, a maximum of eight SNMP Trap destination IP addresses and subnet masks and a maximum of eight Card Routing Table Entry IP addresses and subnet masks can be defined.
Page 330 23.11.42.0 = 23.11.42.0. Therefore, the SNMP traps will be sent to the TLAN router. WARNING Nortel Networks recommends the SNMP client (that is, the OTM 2.1 [and later] PC) not be put on the TLAN subnet. Placing the OTM PC on the ELAN subnet is a more secure configuration.
Page 331 Install and configure IP Trunk 3.01 (and later) node Page 331 of 644 Procedure 22 Configuring SNMP Traps/Routing and IP addresses tab Click SNMP Traps/Routing and IPs tab. See Figure 56. Figure 56 SNMP trap addresses/Routing table IP addresses tab Check the Enable SNMP traps check box to enable sending of SNMP traps to the SNMP managers that appear in the list.
Page 332: Configure Accounting Server
The OTM PC on the local subnet or ELAN subnet. • OTM PC on a remote subnet on the customer’s IP network. • Remote support OTM PC PPP IP address configured in the Nortel Networks Netgear RM356 Modem Router, or equivalent. • Any SNMP managers for remote alarm monitoring.
Page 333 Install and configure IP Trunk 3.01 (and later) node Page 333 of 644 Procedure 23 Configuring a Radius Accounting Server Click the Accounting Server tab. See Figure 57. Figure 57 Accounting Server tab Click the Enable Radius accounting records checkbox. Enter the Radius accounting server IP address.
Page 334: Set Security For Otm Snmp Access
Page 334 of 644 Install and configure IP Trunk 3.01 (and later) node Click Apply. End of Procedure Set Security for OTM SNMP access Procedure 24 on page 335 explains how to change the SNMP community names to provide better security for the IP Trunk 3.01 (and later) node. OTM uses the community name password to refresh the IP Trunk 3.01 (and later) node and card status and to control the transmitting and retrieving of files for database synchronization.
Page 335 Install and configure IP Trunk 3.01 (and later) node Page 335 of 644 Procedure 24 Change SNMP Community Names setting Click the Security tab. See Figure 58. Figure 58 Security tab Change the default Read only and Read/Write default community names. OTM uses the previous read/write community name to transmit the card properties.
Page 336: Exit Node Property Configuration Session
Page 336 of 644 Install and configure IP Trunk 3.01 (and later) node Exit node property configuration session The procedure to add an IP Trunk 3.01 (and later) node manually in OTM is complete. Click OK to save the node and card properties configuration and exit.
Page 337 Install and configure IP Trunk 3.01 (and later) node Page 337 of 644 Procedure 25 Configure the ITG Dialing Plan – General tab In the IP Telephony Gateway – ISDN IP Trunk window, select the new IP Trunk 3.01 (and later) node for which a dialing plan is to be built. Select menu Configuration >...
Page 338 CS 1000S endpoint. 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 Networks IP Telephony Connection Manager. Use H.323 V2 node capability for these nodes.
Page 339 Install and configure IP Trunk 3.01 (and later) node Page 339 of 644 Slide the Quality of Service control bar to set the QoS level. The default setting is 3 (=Good). See “E-Model” on page 101 and Table 34 on page 201 for more details on QoS levels and MOS values.
Page 340 Page 340 of 644 Install and configure IP Trunk 3.01 (and later) node Figure 60 ITG Dialing Plan Remote Node Properties window – Digits dialed tab Dial Plan – Click the pull-down list to display ESN translation types/ISDN call types. 2.
Page 341 Install and configure IP Trunk 3.01 (and later) node Page 341 of 644 Note 1: 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.
Page 342: Retrieve The Ip Trunk 3.01 (And Later) Node Dialing Plan Using Otm
Page 342 of 644 Install and configure IP Trunk 3.01 (and later) node Retrieve the IP Trunk 3.01 (and later) node dialing plan using OTM If adding a new node to a large existing network, it is more efficient to retrieve the IP Trunk 3.01 (and later) node dialing plan from an existing node.
Page 343 Install and configure IP Trunk 3.01 (and later) node Page 343 of 644 Check only the Dialing Plan check box if the community name for both the existing and new nodes is the same. Check the Dialing Plan check box and the Prompt user for community name check box if the community name for both the existing and new nodes are different.
Page 344: Transmit Ip Trunk Card Configuration Data From Otm 2.1 (And Later) To The Ip Trunk Cards
Page 344 of 644 Install and configure IP Trunk 3.01 (and later) node Transmit IP trunk card configuration data from OTM 2.1 (and later) to the IP trunk cards IP Trunk 3.01 (and later) nodes and IP trunk cards are configured in the OTM ITG ISDN IP Trunk application and then transmitted to the IP trunk cards.
Page 345: Set The Leader 0 Ip Address
Install and configure IP Trunk 3.01 (and later) node Page 345 of 644 Set the Leader 0 IP address Follow the steps in Procedure 28 to configure the IP address of the Leader 0 IP trunk card, using the ITG shell Command Line Interface (CLI). Procedure 28 Setting the Leader 0 IP address To access the ITG shell, connect an OTM 2.1 (and later) PC to the...
Page 346 Page 346 of 644 Install and configure IP Trunk 3.01 (and later) node Type +++ to bring up the ITG shell CLI prompt: ...+++ When prompted to login, enter the default username and password as: VxWorks login: itgadmin Password: itgadmin ITG>...
Page 347: Backup Leader Installation For Ip Trunk 3.01 (And Later)
Install and configure IP Trunk 3.01 (and later) node Page 347 of 644 Note 4: If the network administrator has provided the subnet mask in CIDR format, convert it to dotted decimal format before entering it. For example: 10.1.1.1/20 must be converted to IP address 10.1.1.1 with subnet mask 255.255.240.0.
Page 348 Page 348 of 644 Install and configure IP Trunk 3.01 (and later) node Use an A0852632 L-adapter for Media Card 32-port trunk cards. If the Media Card 32-port trunk card has a DCHIP card installed, use the DCHIP cable assembly NTMF29BA along with the L-adapter. In OTM, in the same Node as Leader 0, configure Leader 1.
Page 349: Transmit The Node Properties, Card Properties And Dialing Plan To Leader 0
Install and configure IP Trunk 3.01 (and later) node Page 349 of 644 15 When fully rebooted, enable Leader 1. If D-channel messaging is enabled, all the channels associated with this card give a Restart message. All channels should now be IDLE on the LDR and BLDR in the system. 16 If both IP trunk cards become the LDR, then a network problem has occurred, as BLDR is not receiving/responding to a PING message.
Page 350: Verify Installation And Configuration
Page 350 of 644 Install and configure IP Trunk 3.01 (and later) node To transmit the node properties, card properties, and dialing plan to Leader 0, follow the steps in Procedure 30. Procedure 30 Transmitting the node properties, card properties and dialing plan to Leader 0 From the OTM Navigator window, double-click the ITG ISDN IP Trunks icon from the Services folder.
Page 351: Observe Ip Trunk 3.01 (And Later) Status In Otm 2.1 (And Later)
Install and configure IP Trunk 3.01 (and later) node Page 351 of 644 The Leader 1 card is now autoconfigured as a Leader, reboots automatically, and enters the state of “Backup Leader”. The faceplate display shows “BLDR”. Any Follower cards are now auto-configured with their IP addresses and their display shows “FLR”.
Page 352 Page 352 of 644 Install and configure IP Trunk 3.01 (and later) node Figure 61 IP trunk card status Note: If the (a) IP Trunk 3.01 (and later) Node is being installed from an OTM 2.1 (and later) 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...
Page 353: Transmit Card Properties And Dialing Plan To Leader 1
Install and configure IP Trunk 3.01 (and later) node Page 353 of 644 Verify that the TN, management 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 OTM ITG – ISDN IP Trunk window and select menu Configuration >...
Page 354: Set Date And Time For The Ip Trunk 3.01 (And Later) Node
Page 354 of 644 Install and configure IP Trunk 3.01 (and later) node In the IP Telephony Gateway - ISDN IP Trunk window, select Configuration > Synchronize > Transmit. Keep the radio button default setting of Transmit to selected nodes. Check the Card Properties and Dialing plan check boxes.
Page 355: Change The Default Itg Shell Password To Maintain Access Security
Install and configure IP Trunk 3.01 (and later) node Page 355 of 644 Procedure 33 Setting the date and time for the IP Trunk 3.01 (and later) node Select the IP Trunk 3.01 (and later) node for which the date and time is to be set from the list in the upper part of the IP Telephony Gateway - ISDN IP Trunk window.
Page 356 Page 356 of 644 Install and configure IP Trunk 3.01 (and later) node When prompted to login, enter the default username and password as: VxWorks login: itgadmin Password: itgadmin ITG> 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.
Page 357: Change Default Esn5 Prefix For Non-Esn5 Ip Telephony Gateways
Install and configure IP Trunk 3.01 (and later) node Page 357 of 644 Change default ESN5 prefix for non-ESN5 IP telephony gateways Follow the steps in Procedure 35 to configure an ESN5 prefix for the non-ESN5 IP telephony gateways by using the “esn5PrefixSet” command from the ITG shell CLI.
Page 358: Check And Download Ip Trunk Card Software In Otm 2.1 (And Later)
Verify that the software release on each card is the latest recommended software release for IP Trunk 3.01 (and later) by connecting to a Nortel Networks website that contains the latest software versions for the Media Card 32-port and the ITG-Pentium 24-port trunk card.
Page 359 Page 359 of 644 Figure 64 ITG Card Properties – Configuration tab Check the Nortel Networks website to find the latest recommended IP Trunk 3.01 (and later) software release. Go to www.nortelnetworks.com. Follow the links to Customer Support and Software Distribution or go to www.nortelnetowrks,com./support.
Page 360: Transmit New Software To The Ip Trunk Cards
Page 360 of 644 Install and configure IP Trunk 3.01 (and later) node Download software packages and associated release notes as follows: For Media Card 32-port trunk cards, download the Software Package for Release IP Trunk 3.01 (and later). For ITG-Pentium 24-port trunk cards, download the Software Package for Release IP Trunk 3.01 (and later).
Page 361 Install and configure IP Trunk 3.01 (and later) node Page 361 of 644 Procedure 37 Transmitting new software to the IP trunk cards Open OTM 2.1 (and later). Click Services and launch the ITG ISDN IP Trunks application. Select the node to upgrade from the list in the upper half of the IP Telephony Gateway - ISDN IP Trunk window.
Page 362 Page 362 of 644 Install and configure IP Trunk 3.01 (and later) node that the transmission was successful for all card TNs. The cards continue to run the old software until rebooted. Click the Close button and go to step 6. If transmitting new software to a node containing a mix of card densities, ensure the following: Make sure Transmit to selected cards is selected.
Page 363: Upgrade The Dchip Pc Card
Install and configure IP Trunk 3.01 (and later) node Page 363 of 644 10 Use the LD 32 ENLC command to re-enable the IP trunk cards. End of Procedure The software upgrade procedure is complete. Upgrade the DCHIP PC Card Follow the steps in Procedure 38 to upgrade the DCHIP card.
Page 364: Configure Otm Alarm Management To Receive Snmp Traps
Page 364 of 644 Install and configure IP Trunk 3.01 (and later) node protected, enter the login and password when prompted. If correct, the upgrade of the DCHIP PC Card begins. End of Procedure Once the upgrade is complete, the DCHIP card reboots automatically. Configure OTM Alarm Management to receive SNMP traps from the IP trunk cards Follow the steps in Procedure 39 to configure OTM Alarm Management to...
Page 365 Install and configure IP Trunk 3.01 (and later) node Page 365 of 644 Figure 65 “Open” dialog box Select the Devices file from the Control Files folder and click Open. The Devices.txt file opens. See Figure 66 on page 366. IP Trunk Description, Installation, and Operation...
Page 366 Page 366 of 644 Install and configure IP Trunk 3.01 (and later) node Figure 66 Devices.txt file: 553-3001-363 Standard 2.00 September 2004...
Page 367 Install and configure IP Trunk 3.01 (and later) node Page 367 of 644 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 49. Enter the first line beginning underneath the last line that begins with a “#”.
Page 368: Make Test Calls To The Remote Nodes (Itg Trunk Or Ip Trunk)
Page 368 of 644 Install and configure IP Trunk 3.01 (and later) node Make test calls to the remote nodes (ITG Trunk or IP Trunk) Make test calls to ensure the following: • The IP Trunk 3.01 (and later) system can process calls from each node to a remote node.
Page 369: Provisioning Ip Trunk 3.01 (And Later) In Otm 2.1 (And Later)
Page 369 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Contents This section contains information on the following topics: Overview ..........Add a site and system .
Page 370: Overview
Page 370 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Overview This chapter describes the provisioning in OTM 2.1 (and later) required to operate the IP Trunk 3.01 (and later) application. For detailed information on configuring a system in OTM 2.1 (and later), see Optivity Telephony Manager: System Administration (553-3001-330).
Page 371 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 371 of 644 Figure 67 OTM Navigator Click Sites to highlight it. On the menu bar, click Configuration > Add Site. See Figure 68 on page 372. IP Trunk Description, Installation, and Operation...
Page 372 Page 372 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Figure 68 Add a Site An empty New Site Properties window opens. The site is a single entity, usually in one location. Enter as much information as is required for proper site maintenance.
Page 373 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 373 of 644 Figure 69 New Site Properties – Provisioning a new site Click OK to save the site information. The OTM Navigator window opens again, with the new site added. End of Procedure IP Trunk Description, Installation, and Operation...
Page 374: Change An Existing Site
Page 374 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) For more information on how to add a site, see Optivity Telephony Manager: System Administration (553-3001-330). Change an existing site Follow the steps in Procedure 41 to make changes to an existing site. Procedure 41 Changing an existing site Log in to the OTM Navigator.
Page 375 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 375 of 644 Figure 70 Change System Properties Alternatively, from the upper menu, click File > Properties. See Figure 71 on page 376 IP Trunk Description, Installation, and Operation...
Page 376 Page 376 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Figure 71 Alternate way to change System Properties The Site Properties window opens. See Figure 72 on page 377. 553-3001-363 Standard 2.00 September 2004...
Page 377 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 377 of 644 Figure 72 OTM Site Properties ready to change Enter the information that is being changed. Click OK to save the site information. End of Procedure IP Trunk Description, Installation, and Operation...
Page 378: Delete A Site
Page 378 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Delete a site Follow the steps in Procedure 42 to delete a site. Procedure 42 Deleting a site Log in to the OTM Navigator. The window displays two sections – Services and Sites. See Figure 67 on page 371.
Page 379 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 379 of 644 Alternatively, from the upper menu, click Edit > Delete. WARNING Deleting a site also deletes all of its systems. See Figure 74. Figure 74 Alternative method of deleting a site In the warning box that opens, click Yes to confirm the deletion.
Page 380: Add A System
Page 380 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Figure 75 Confirm deletion End of Procedure 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.
Page 381 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 381 of 644 Procedure 43 Adding a system There are two ways to add a new system in the OTM Navigator window, as follows: Right-click the new site. A menu appears, as shown in Figure 76. Click Add System.
Page 382 Page 382 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Figure 77 New system – menu bar 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.
Page 383 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 383 of 644 also be provisioned in OTM 2.1 (and later). The CS 1000S/1000M Gatekeeper enables interworking between IP Peer and IP Trunk 3.01 (and later). By provisioning the CS 1000S/1000M system on the same OTM 2.1 (and later) PC, the Gatekeeper information is stored in OTM 2.1 (and later), making it easier to provision IP Trunk 3.01 (and later) to use the Gatekeeper.
Page 384 Page 384 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Figure 79 Empty New System Properties window The General properties must be provisioned before any other site properties, as the information on the General tab pertains to the entire system and all IP Trunk nodes on the system.
Page 385 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 385 of 644 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 IP Trunk Description, Installation, and Operation...
Page 386: Enter System Data
Page 386 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Enter system data Click the System Data tab. Enter the correct machine type, software release, and system parameters. Ensure the correct packages are provisioned. See Figure 81 on page 387.
Page 387: Provision The System Customer Information
Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 387 of 644 Figure 81 System Data tab Provision the system customer information Click the Customers tab. An empty Customers window appears. See Figure 82 on page 388. An IP trunk card cannot be provisioned unless it belongs to a system customer.
Page 388 Page 388 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Figure 82 Empty Customers window Click the Add button to add a customer. The Add Customer window opens. See Figure 83 on page 389. 553-3001-363 Standard 2.00 September 2004...
Page 389 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 389 of 644 Figure 83 Add Customer window 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 on page 390.
Page 390 Page 390 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Figure 84 New – (Customer x) Properties – General tab 10 Enter the Directory Numbers and HLOC obtained from the system provisioning. Note: The Features tab and the Numbering Plans tab are related to system provisioning.
Page 391: Change An Existing System
Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 391 of 644 12 Click OK in the System Properties window. The window closes and the OTM Navigator window is displayed. End of Procedure Change an existing system Follow the steps in Procedure 44 to make changes to an existing system.
Page 392 Page 392 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Figure 85 System Properties window Enter the information that is being changed. 553-3001-363 Standard 2.00 September 2004...
Page 393 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 393 of 644 Change customer properties To change a customer’s properties, click the Customers tab of the System Properties window, as seen in Figure 85. Select the customer. See Figure 86. Figure 86 System Properties –...
Page 394 Page 394 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Edit the customer’s information in the Customer Properties window – General, Features, and Numbering Plans tabs. See Figure 87. Figure 87 Customer Properties window Click OK to save the customer information. Click OK to save the system information.
Page 395: Delete A System
Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 395 of 644 Delete a system Follow the steps in Procedure 45 to delete a system. Procedure 45 Deleting a system Log in to the OTM Navigator. The window displays two sections – Services and Sites. See Figure 67 on page 371.
Page 396 Page 396 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Alternatively, from the upper menu, click Edit > Delete. See Figure 89. Figure 89 Alternative method of deleting a system In the warning box that opens, click Yes to confirm the deletion. See Figure 90 on page 397.
Page 397: Add An Ip Trunk 3.01 (And Later) Node
Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 397 of 644 Figure 90 Confirming the deletion End of Procedure Add an IP Trunk 3.01 (and later) node Follow the steps in Procedure 46 to add an IP Trunk 3.01 (and later) node. Procedure 46 Adding an IP Trunk 3.01 (and later) node In the OTM Navigator window, under Services, right-click...
Page 398 Page 398 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Figure 91 OTM Navigator – ITG ISDN IP Trunks service The IP Telephony Gateway – ISDN IP Trunk window opens, as seen in Figure 92 on page 399.
Page 399 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 399 of 644 Figure 92 ITG – ISDN IP Trunk window 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 opens.
Page 400 (and later), select Meridian 1 or MMCS. Click a radio button to indicate whether to retrieve the information from an existing remote node, or to define the node configuration manually. Nortel Networks recommends selecting the “Define the node configuration manually” radio button, as OTM generates comprehensive provisioning files, including the BOOTP.1 file, the CONFIG1.INI file, and all address...
Page 401 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 401 of 644 On the General tab, on the left side of the window, define the following from the drop-down lists: • The OTM site – the name that was assigned when the site was created.
Page 402: Provision The Ip Trunk Cards
Page 402 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Provision the IP trunk cards Click the Configuration tab. This is where the IP trunk cards are provisioned. See Figure 95. Figure 95 New ITG Node - Configuration tab A minimum of one IP trunk card, Leader 0, must be defined.
Page 403 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 403 of 644 10 Enter the appropriate data in the following fields: • Card role – the default is Leader 0, indicating that this is the primary leader. Other options include Leader 1 (Backup) and Follower. •...
Page 404: Provision The Dsp Data
Page 404 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) When Add is clicked, the lower card information window displays the saved card information. See Figure 96. 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.
Page 405 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 405 of 644 The Control packets and Voice packets can be assigned a different DIFFSERV/TOS value to assist in QoS in the IP network. Only change these values if it is found to be necessary and ensure that all network routers have been updated with the new TOS value.
Page 406 Page 406 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) The DSP Profile values appear. See Figure 98. Some of the values that can be changed are: • DTMF tone detection – for voice mail access and IVR, for example. Allows DTMF tones to be reliably transmitted across the network.
Page 407 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 407 of 644 Note: OTM 2.1 (and later) 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.
Page 408 Page 408 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) 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.
Page 409: Select An Rtp Port
Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 409 of 644 Figure 99 on page 408 shows a DSP Profile with VAD enabled for the G.711. This is the default setting for OTM 2.1 (and later). 16 When G.711 is selected as the codec option and the only remote device on the network is an ITG 2.x trunk or an IP 3.0 trunk, then the VAD setting can be left enabled.
Page 410: Add The Node
Page 410 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) 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: •...
Page 411: Edit A Node
Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 411 of 644 Figure 101 ITG – ISDN IP Trunk window with new node displayed End of Procedure Edit a node Follow the steps in Procedure 47 to edit a node’s information. Procedure 47 Editing a node In the OTM Navigator window, under Services, right-click...
Page 412 Page 412 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Figure 102 Change node properties Alternatively, right-click the node to be edited, the select Properties from the pop-up menu. See Figure 103 on page 413. 553-3001-363 Standard 2.00 September 2004...
Page 413 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 413 of 644 Figure 103 Alternative method of selecting node to be edited 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.
Page 414 Page 414 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Figure 104 ITG Node Properties – General tab 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.
Page 415 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 415 of 644 Figure 105 ITG Node Properties – Configuration tab Enter the required data. Note that, compared to the Leader 0 configuration • the Management (ELAN subnet) IP address, the Voice (TLAN subnet) IP address, and the Management MAC IP address have changed •...
Page 416 Page 416 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Figure 106 Leader 1 (Backup Leader) sample configuration To edit an IP trunk card, select the Configuration tab. Select the desired IP trunk card in the lower window. In the example shown in Figure 107 on page 417, the Follower card is...
Page 417 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 417 of 644 Figure 107 Editing an IP trunk card in a node To delete an IP trunk card from the node, select the desired card and click Delete.
Page 418 Page 418 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Figure 108 When an IP trunk card cannot be deleted If the IP trunk card can be deleted, the print on the Delete button is in black.
Page 419 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 419 of 644 Figure 109 Delete an IP trunk card from a node Note: Leader 0 and Leader 1 cannot be deleted if there is still a Follower card in the node.
Page 420: Delete A Node
Page 420 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Delete a node Follow the steps in Procedure 48 to delete a node. Procedure 48 Deleting a node In the ITG -ISDN IP Trunk window, select the node to be deleted. From the upper menu, click Configuration >...
Page 421 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 421 of 644 Figure 111 Alternative method of deleting a node 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. Figure 112 Confirm the node deletion If Yes is selected, the node is deleted.
Page 422: Define The Dialing Plan Information
Page 422 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Figure 113 The node is deleted End of Procedure 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.
Page 423: Non-Gatekeeper-Resolved (Local) Dialing Plan
Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 423 of 644 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.
Page 424 Page 424 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) In IP Trunk 3.01 (and later), the capability of “CS 1000S” has been added as a destination node protocol. The CS 1000S destination protocol can be used for making calls to IP Trunk 3.01 (and later) and CS 1000S endpoints, although this is strictly for initial setup.
Page 425 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 425 of 644 Another concern when using QoS monitoring is the effect of the additional traffic generated by QoS messages being sent between nodes. If all nodes have QoS enabled, the effect of adding one additional node nearly doubles the number of QoS messages being sent.
Page 426 Page 426 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) 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.
Page 427 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 427 of 644 Table 50 Mapping of dialing plan with TON and NPI (Part 2 of 2) Dialing plan Private Private Unknown Unknown Unknown IP Trunk Description, Installation, and Operation...
Page 428 Page 428 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Procedure 49 Defining the local Dialing plan From the IP Telephony Gateway – ISDN IP Trunk window (see Figure 114), select a node. From the Menu, click Configuration > Dialing Plan.
Page 429 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 429 of 644 Figure 115 ITG Dialing Plan window 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.
Page 430 Page 430 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Figure 116 ITG Dialing Plan – Remote Node Properties window – General tab 553-3001-363 Standard 2.00 September 2004...
Page 431 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 431 of 644 Figure 117 ITG Dialing Plan – Remote Node Properties window – General tab with drop-down list open An existing destination node can also have its properties changed from the drop-down list.
Page 432 Page 432 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Figure 118 Change properties on an existing destination node Before entering data (for example, number plan, type of number, digits) for a specific address, the destination node must be selected. The destination node can be selected in one of the following ways: •...
Page 433 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 433 of 644 Figure 119 Selected Remote Node IP Trunk Description, Installation, and Operation...
Page 434 Page 434 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) 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).
Page 435 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 435 of 644 Figure 120 Remote Node Properties – Digits dialed tab with no entries IP Trunk Description, Installation, and Operation...
Page 436 Page 436 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Figure 121 Select the destination node 553-3001-363 Standard 2.00 September 2004...
Page 437 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 437 of 644 Figure 122 Remote Node Properties – Digits dialed tab with a selected destination node In the example seen in Figure 122, the dialing plan digits to be added are 613-961-xxxx.
Page 438 Page 438 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) To delete a destination node from the lower window, select the desired node and click Delete. Although there is no warning box to request confirmation of the deletion, the destination can immediately be re-added if deleted in error.
Page 439 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 439 of 644 Destination not in local OTM provisioning 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. Select H.323 V2 from the Node capability drop-down list if selecting an IP Peer H.323 Gateway.
Page 440 Page 440 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Figure 125 Selecting an IP Peer H.323 Gateway 553-3001-363 Standard 2.00 September 2004...
Page 441 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 441 of 644 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.
Page 442 Page 442 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) 12 Click the Digits dialed tab. The Add button is inactive until values are entered in the Dial plan digits field. On the Digits dialed tab, enter the dial plan information for this node. 13 From the Dial Plan drop-down list, select the correct dial plan/type of number selection.
Page 443 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 443 of 644 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.
Page 444 Page 444 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) 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 shows a sample dial plan with a much more complex set of access numbers.
Page 445: Gatekeeper-Resolved Endpoints
Recommendation Though not mandatory, Nortel Networks recommends that zones be used for IP Trunk 3.01 (and later). In the OTM Navigator window, the Gatekeeper zone can be found by left-clicking on the CS 1000S or CS 1000M system, selecting Properties, and clicking on the Network tab.
Page 446 Page 446 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Figure 130 Making a Gatekeeper zone All nodes within a network are configured with the IP addresses of the Primary and Alternate Gatekeepers in that network zone. Follow the steps in Procedure 50 on page 447 to configure the correct...
Page 447 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 447 of 644 Procedure 50 Provisioning the IP Trunk 3.01 (and later) node to register with the Gatekeeper Configure The IP Trunk 3.01 (and later) node to register with the IP Peer H.323 Gateway Gatekeeper.
Page 448 Page 448 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) No matter which method was used, the ITG Node Gatekeeper Properties window opens. Select the correct Gatekeeper option from the Gatekeeper Option drop-down list. The options are as follows: •...
Page 449 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 449 of 644 See Figure 132. Figure 132 Node Properties Gatekeeper from OTM Click Apply. End of Procedure IP Trunk Description, Installation, and Operation...
Page 450 Page 450 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Use Independent Gatekeeper option If “Use Independent Gatekeeper” was selected from the Gatekeeper Option drop-down list, follow the steps in Procedure 52. Provisioning an independent Gatekeeper requires full manual provisioning. Procedure 52 Using the Independent Gatekeeper option Select CS 1000S/CS 1000M as the remote Gatekeeper type.
Page 451 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 451 of 644 Figure 134 shows an example of an independent Gatekeeper that has been provisioned. Figure 134 Properties defined for Primary Gatekeeper WARNING The H.323 endpoint ID is case-sensitive and alphanumeric string content-sensitive.
Page 452 Page 452 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) 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. The Gatekeeper registration option in the circled check box, as seen in Figure 134 on page...
Page 453 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) Page 453 of 644 Click OK. End of Procedure 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 454 Page 454 of 644 Provisioning IP Trunk 3.01 (and later) in OTM 2.1 (and later) 553-3001-363 Standard 2.00 September 2004...
Page 455: Otm 2.1 (And Later) Oa&M Using Otm 2.1 (And Later) Applications
Page 455 of 644 OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications Contents This section contains information on the following topics: Introduction ..........OTM OA&M procedure summary .
Page 456: Introduction
Page 456 of 644 OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications System commands – LD 32 ....... . . Disable the indicated IP trunk card .
Page 457: Delete A Node
OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications Page 457 of 644 • “Schedule and generate and view IP Trunk 3.01 (and later) OM reports” page 475 • “Backup and restore operations” on page 477 • “Alarm Notification” on page 478 Delete a node To delete an IP Trunk 3.01 (and later) node, perform the following steps in...
Page 458: Delete An Ip Trunk Card
Page 458 of 644 OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications The dialog box in Figure 136 appears. Click the Yes button to confirm the deletion of the IP Trunk 3.01 (and later) node. The IP Trunk 3.01 (and later) node and all related IP trunk cards are deleted.
Page 459: Database Locking
OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications Page 459 of 644 Click OK. End of Procedure Database locking All node and card properties are stored in a single OTM database. When Node or Card Properties are opened, the data for a given node (including card properties) is then locked.
Page 460: Itg Card Properties Window
Page 460 of 644 OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications Figure 137 Database lock message 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.
Page 461: Itg Card Properties - Maintenance Window
OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications Page 461 of 644 ITG Card Properties – Maintenance window Click the Maintenance tab to perform maintenance operations. See Figure 138. click the appropriate button in the Maintenance window to perform the required operation.
Page 462 Page 462 of 644 OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications • 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.
Page 463: Itg Card Properties - Configuration Window
OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications Page 463 of 644 ITG Card Properties – Configuration window The Configuration window for the IP trunk card contains the information shown in Figure 139. The ITG Card Properties Configuration window provides read-only information.
Page 464: Dsp Maintenance Window
Page 464 of 644 OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications DSP maintenance window Note: If the IP trunk card is not responding, no DSP icons appear in the tree on the left-hand side of the ITG Card Properties window. click the required DSP icon in the tree on the left-hand side of the ITG Card Properties window.
Page 465 OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications Page 465 of 644 The ITG Main window displays the synchronization status of each of these fields. Changes to the first two tabs (General and Card Configuration) in the Node Properties sheet affect the Node Synchronization Status.
Page 466 Page 466 of 644 OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications 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.
Page 467 OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications Page 467 of 644 • To transmit Card Properties (CONFIG1.INI), the entire node in the top window or an individual card can be selected, but in either case it is necessary to select to transmit to the entire node.
Page 468: Retrieving An Existing Node
Page 468 of 644 OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications When transmitting to an IP trunk card which is locked by another user, the second user is provided with the option to override the lock. See Figure 141. The lock is only checked during the Transmit operation.
Page 469: Administration Purposes
OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications Page 469 of 644 • To restore the IP Trunk 3.01 (and later) configuration database to an OTM 2.1 (and later) PC whose hard drive had failed. (The OTM IP Trunk 3.01 (and later) nodes can also be restored from the Full OTM Backup.) •...
Page 470 Page 470 of 644 OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications 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. Figure 142 Retrieve ITG node window 553-3001-363...
Page 471 OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications Page 471 of 644 In the Retrieve ITG node window, select the OTM Site and Meridian 1 System fields. Select the Meridian 1 Customer number. Note: The site name, Meridian 1 system name, and Meridian 1 customer number must exist in the OTM Navigator before a new IP Trunk 3.01 (and later) node can be added.
Page 472: And Diagnostic Purposes
Page 472 of 644 OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications Retrieve and add an IP Trunk 3.01 (and later) node for maintenance and diagnostic purposes Follow the steps in Procedure 58 to create a “dummy” IP Trunk 3.01 (and later) node for retrieving and viewing the real IP Trunk 3.01 (and later) node configuration, without overwriting the existing IP Trunk 3.01 (and later) configuration data for an existing node in the OTM IP Trunk 3.01 (and later)
Page 473: Configuration Audit
OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications Page 473 of 644 To view the data of a real IP Trunk 3.01 (and later) node, select the “dummy” node and change the management IP address in the node properties to access Configuration >...
Page 474 Page 474 of 644 OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications Procedure 59 Retrieving the IP Trunk 3.01 (and later) configuration data from the IP Trunk 3.01 (and later) node Launch OTM and double-click the ITG ISDN IP Trunks icon from the Services folder.
Page 475: Schedule And Generate And View Ip Trunk 3.01 (And Later) Om Reports
OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications Page 475 of 644 Schedule and generate and view IP Trunk 3.01 (and later) OM reports Operational Measurement (OM) reports are a collection of OM data from all the IP trunk cards defined on the OTM PC or server. A report can be generated on request or the report scheduled to generate at a selected time.
Page 476 Page 476 of 644 OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications Figure 144 Generate OM Report To generate a report immediately, click Generate OM Report. OTM 2.1 prepares the report and displays the information in a .csv spreadsheet format.
Page 477: Backup And Restore Operations
OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications Page 477 of 644 Figure 145 OM Report scheduling window End of Procedure 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 OTM 2.1 (and later) PC.
Page 478: Alarm Notification
Page 478 of 644 OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications IP Trunk 3.01 (and later) data is stored in an Access database file on the OTM 2.1 (and later) PC or server, or in the OM files. These files are only backed up when the “Full OTM Backup”...
Page 479 OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications Page 479 of 644 • “Enable an indicated IP trunk card” on page 482. • “Enable an indicated IP trunk card port” on page 482. • “Display IP trunk card ID information” on page 482.
Page 480 Page 480 of 644 OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications A summary list of IP Trunk 3.01 (and later) system commands available in LD 32 is shown in Table 51. Table 51 LD 32 – IP Trunk 3.01 (and later) maintenance commands (Part 1 of 2) Command Description DISC l s c...
Page 481: Disable The Indicated Ip Trunk Card
OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications Page 481 of 644 Table 51 LD 32 – IP Trunk 3.01 (and later) maintenance commands (Part 2 of 2) Command Description STAT l s c Print the system software status of the indicated card.
Page 482: Enable An Indicated Ip Trunk Card
Page 482 of 644 OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications Enable an indicated IP trunk card To enable an indicated IP trunk card in LD 32, use the following command: ENLC l s c Enable the indicated IP trunk card, where: l = loop, s = shelf, c = card Disable an indicated IP trunk card port...
Page 483: Display Ip Trunk Card Status
OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications Page 483 of 644 Display IP trunk card status To display the status of a indicated IP trunk card in LD 32, use the following command: STAT l s c Display the status of the indicated IP trunk card, where: l = loop, s = shelf, c = card...
Page 484 Page 484 of 644 OTM 2.1 (and later) OA&M using OTM 2.1 (and later) applications 553-3001-363 Standard 2.00 September 2004...
Page 485: Oa&M Using The Itg Shell Cli And Overlays
Page 485 of 644 OA&M using the ITG shell CLI and overlays Contents This section contains information on the following topics: Introduction ..........ITG Shell OA&M procedure summary.
Page 486: Introduction
Page 486 of 644 OA&M using the ITG shell CLI and overlays Disable an indicated IP trunk card port ..... . Enable an indicated IP trunk card .
Page 487: Access The Itg Shell Through A Maintenance Port Or Telnet
OA&M using the ITG shell CLI and overlays Page 487 of 644 • “IP Trunk 3.01 (and later) configuration commands” on page 507. • “Download the IP Trunk 3.01 (and later) error log” on page 507. Access the ITG shell through a maintenance port or Telnet The ITG shell administration and maintenance commands can be accessed in two ways: Log in through a direct cable connection between the IP trunk card...
Page 488: Telnet To An Ip Trunk Card Through The Otm Pc
Page 488 of 644 OA&M using the ITG shell CLI and overlays Use the following communication parameters for the TTY terminal emulation on the PC: • 9600 baud • 8 bits • no parity bit • one stop bit When prompted to login, enter current username and password. Default VxWorks login: itgadmin Password: itgadmin ITG>...
Page 489 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 set only once, because Telnet preferences are automatically saved.
Page 490: Change The Default Itg Shell Password To Maintain Access Security
Page 490 of 644 OA&M using the ITG shell CLI and overlays To prevent the loss of diagnostic data from the IP trunk card if the Telnet session terminates unexpectedly, enable logging of Telnet sessions on the OTM PC: From the Telnet “Terminal” menu, select “Start Logging”. Use the “Browse”...
Page 491: Reset The Default Itg Shell Password
OA&M using the ITG shell CLI and overlays Page 491 of 644 Reset the default ITG shell password If the ITG shell password is lost, the ITG shell user name and password can be reset to the default: itgadmin. This procedure requires physical access to the IP trunk card.
Page 492 24-port trunk card asks for xxx to get into the BIOS, the firmware on that IP trunk card must be upgraded. Contact Nortel Networks Technical Support for more information. Press the reset button on the card again. The IP trunk card starts up and displays “T:20” on the 4-character display.
Page 493: Download The Itg Operational Measurements Through The Itg Shell
OA&M using the ITG shell CLI and overlays Page 493 of 644 Type +++ to bring up the ITG shell command line prompt: ....+++ When prompted to login, enter the default username and password as: VxWorks login: itgadmin Password: itgadmin ITG>...
Page 494: Reset The Operational Measurements
Page 494 of 644 OA&M using the ITG shell CLI and overlays and fax calls. To download this file from the OTM PC to the IP trunk card, at the ITG shell prompt, type the following: currOMFilePut <hostname, username, password, directory path, filename >...
Page 495 OA&M using the ITG shell CLI and overlays Page 495 of 644 At the ITG shell prompt, type the following command to display information about an IP trunk card: itgCardShow The command itgCardShow prints out the information that was provisioned in OTM 2.1 (and later), such as the IP trunk card TN, protocol used, card role, IP addresses, and whether the DCH PC Card is on board.
Page 496 Page 496 of 644 OA&M using the ITG shell CLI and overlays The following is an example of the itgCardShow command: Index: 1 Type: ITG2 Role: Leader Leader IP: 47.11.215.182 RTP Base Port: 2300,2300=>Default 173300+>Cisco RTPHeaderCpmpresssion Card IP: 47.11.215.186 Card MgtIP: 47.11.217.21 Ldr MgtIP: 47.11.217.21 Card TN: 9 0 0 Card State: ENBL...
Page 497: Display Ip Trunk 3.01 (And Later) Gatekeeper Status
OA&M using the ITG shell CLI and overlays Page 497 of 644 • serialNumShow • firmwareVersionShow • swVersionShow • emodelSim Display IP Trunk 3.01 (and later) Gatekeeper status At the ITG shell prompt, type the following command to display information about the IP Trunk 3.01 (and later) registration with a Gatekeeper: gkShow The following information appears on the TTY:...
Page 498 Page 498 of 644 OA&M using the ITG shell CLI and overlays The following is an example of the output of the gkshow command when there is only a Primary Gatekeeper. --------------------------------------- <<PROVISIONED>> The H.323 ID of this gateway is : [Shane_IPT_cust0] First place dialed numbers are resolved: ATPM Second place numbers are resolved : Gatekeeper Cards that register with the Gatekeeper: All...
Page 499: Transfer Files Through The Command Line Interface
OA&M using the ITG shell CLI and overlays Page 499 of 644 Transfer files through the Command Line Interface Type one of the following commands at the ITG shell Command Line Interface (CLI) to enable these actions: • transfer a file from the IP trunk card to an FTP host •...
Page 500 IP trunk card. To avoid damaging the configuration files and the IP trunk card, only use the “hostFileGet” command under the direction of Nortel Networks support personnel.
Page 501 OA&M using the ITG shell CLI and overlays Page 501 of 644 Configuration file transfer Use these commands to backup and restore files when the preferred method, the OTM PC, is not available. DPAddrTGet "hostname","username","password", "directory path","filename" DPAddrTPut "hostname","username","password", "directory path","filename" configFileGet "hostname","username","password", "directory path","filename"...
Page 502: Upgrade Ip Trunk Card Software Using Ftp
When the new software version is correctly downloaded, reboot the IP trunk card with cardReset to run the new software. Obtain the new IP trunk card software from the Nortel Networks web site, or obtain a PC Card containing the newest software.
Page 503 Card. Upgrade IP trunk card software by PC Card The PC Card can be obtained from Nortel Networks with the latest IP trunk card software version. Update the IP trunk card software version on the PC Card by copying the file from the PC hard drive to the PC Card, which is inserted in a PC Card slot on the PC.
Page 504: Backup And Restore From The Cli
Procedure 67 Upgrading IP trunk card software through an FTP host Make the latest IP trunk card software, obtained from the Nortel Networks web page, available to an FTP host. This can be an FTP host on the PC. As a special case, the FTP host can be the IP trunk card.
Page 505 OA&M using the ITG shell CLI and overlays Page 505 of 644 First, use the ‘Put’ commands to back up the IP trunk card configuration files. Restore the files later using the “Get” commands. However, the “DPAddrTGet” file can be used to restore the dialing plan file from another IP trunk card in the same node.
Page 506: Recover The Snmp Community Names
Page 506 of 644 OA&M using the ITG shell CLI and overlays Procedure 69 Restoring from the CLI Use the BootPFileGet command with the appropriate parameters, to restore the Node Properties file from the FTP host to the IP trunk card. Log in to the ITG shell for each IP trunk card that requires a dialing plan restore.
Page 507: Ip Trunk 3.01 (And Later) Configuration Commands
OA&M using the ITG shell CLI and overlays Page 507 of 644 IP Trunk 3.01 (and later) configuration commands Table 52 lists the IP Trunk 3.01 (and later) configuration commands. Table 52 IP Trunk 3.01 (and later) configuration commands Command Description setLeader The one command that performs all the necessary actions to...
Page 508 Page 508 of 644 OA&M using the ITG shell CLI and overlays Note 1: Disable the IP trunk card before card properties are transmitted from the OTM IP Trunk 3.01 (and later) application to the IP trunk card. Note 2: The card reset button is only available in the OTM IP Trunk 3.01 (and later) application when the IP trunk card is disabled.
Page 509 OA&M using the ITG shell CLI and overlays Page 509 of 644 Table 53 shows a summary of the system administration commands available in LD 32. Table 53 LD 32 – IP Trunk 3.01 (and later) maintenance commands Command Function DISC l s c Disable the indicated card, where: l = loop, s = shelf, c = card...
Page 510: Disable The Indicated Ip Trunk Card
Page 510 of 644 OA&M using the ITG shell CLI and overlays Disable the indicated IP trunk card To disable the indicated IP trunk card in LD 32, use the following command: DISC l s c Disable the indicated IP trunk card, where: l = loop, s = shelf, c = card Disable the indicated IP trunk card when idle...
Page 511: Enable An Indicated Ip Trunk Card Port
OA&M using the ITG shell CLI and overlays Page 511 of 644 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.01 (and later) unit (port), where: l = loop, s = shelf, c = card Display IP trunk card ID information...
Page 512 Page 512 of 644 OA&M using the ITG shell CLI and overlays 553-3001-363 Standard 2.00 September 2004...
Page 513: Maintenance
Page 513 of 644 Maintenance Contents This section contains information on the following topics: Introduction ..........IP Trunk 3.01 (and later) IP trunk card alarms .
Page 514: Introduction
Page 514 of 644 Maintenance Transmit card properties and dialing plan ....Backup and restore procedures ....... IP trunk card.
Page 515: Ip Trunk 3.01 (And Later) Ip Trunk Card Alarms
Maintenance Page 515 of 644 • – how to perform diagnostic tests on the IP trunk card to Diagnostics check correct operation. • – the different upgrade options IP Trunk 3.01 (and later) upgrades available for IP Trunk 3.01 (and later). •...
Page 516 If this happens due to something other than cleared. a known power-on event or a user-invoked card reset, the causes of recurring bootup must be investigated. Contact Nortel Networks technical support. ITG0101 Exit from QoS fallback. Normal Indicates recovery from ITG0203. Recurrent operation restored.
Page 517 Maintenance Page 517 of 644 Table 54 IP Trunk 3.01 (and later) alarms (Part 2 of 7) Alarm Description Fault Clearing Action ITG0103 Ethernet management port Indicates recovery from ITG0403. restored to normal operation. ITG0104 DSP successfully reset. Indicates recovery from ITG0204. ITG0105 Exit from card fallback.
Page 518 If the problem occurs frequently the IP trunk card requires manual intervention; for example, upgrade to an enhanced software version or replace the IP trunk card. ITG0300 Memory allocation failure. Check If this occurs frequently, contact Nortel configuration. Indicates a dynamic Networks technical support. memory allocation problem.
Page 519 Maintenance Page 519 of 644 Table 54 IP Trunk 3.01 (and later) alarms (Part 4 of 7) Alarm Description Fault Clearing Action 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.
Page 520 Page 520 of 644 Maintenance Table 54 IP Trunk 3.01 (and later) alarms (Part 5 of 7) Alarm Description Fault Clearing Action ITG0350 Gatekeeper RAS reject threshold exceeded. ITG0351 Cannot open Gatekeeper configuration file. Using default settings. Major Alarms – Immediate intervention required These alarms indicate an irrecoverable failure of the IP trunk card.
Page 521 Maintenance Page 521 of 644 Table 54 IP Trunk 3.01 (and later) alarms (Part 6 of 7) Alarm Description Fault Clearing Action ITG0408 Bad address translation file. Reverting to previous version (if any). ITG0409 Bad configuration file. Reverting to previous version (if any). ITG0410 Remote leader not responding.
Page 522: System Level Maintenance
Page 522 of 644 Maintenance Table 54 IP Trunk 3.01 (and later) alarms (Part 7 of 7) Alarm Description Fault Clearing Action ITG0430 Software image not compatible with Target processor. Software upgrade aborted. ITG0450 D-channel loss of signal. Associated channels busied out. ITG0451 D-channel hardware failure.
Page 523: Access The Ip Trunk Card
Maintenance Page 523 of 644 Access the IP trunk card The IP trunk card can be accessed in two ways: by Telnet and through a physical connection to the serial port. Telnet access Connect to the IP trunk card using Telnet. This provides access to the ITG shell.
Page 524 Page 524 of 644 Maintenance Table 55 Supported LD 32 commands (Part 2 of 2) Command Function ENLU l s c u Enable the indicated unit, where: l = loop, s = shelf, c = card, and u = unit. IDC l s c Print the Card ID information for the specific IP trunk card, where:...
Page 525 Maintenance Page 525 of 644 Table 56 Supported LD 36 commands (Part 2 of 2) 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:...
Page 526: Otm 2.1 (And Later) Maintenance Commands
Page 526 of 644 Maintenance OTM 2.1 (and later) maintenance commands When changing DSP parameters in OTM 2.1 (and later), disable the IP trunk card’s ports before downloading the new parameters. Modifications to node parameters require the affected cards to be rebooted. A dialing plan can be modified without rebooting or disabling the cards.
Page 527 Maintenance Page 527 of 644 Error traps Table 58 shows the error events that cause the SNMP agent to issue a trap. Table 58 Error events Event Description Loss of Voice Port connectivity Failure in the Ethernet voice port. QoS Minor Threshold Exceeded The QoS minor alarm threshold has been exceeded.
Page 528: Trace And Alarm/Log
Page 528 of 644 Maintenance Table 59 SNMP trap causing events (Part 2 of 2) Command Function 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.
Page 529: Itg Shell Command Set
Maintenance Page 529 of 644 ITG shell command set ITG shell commands are designed to supplement overlay commands and to introduce new features specific to IP Trunk 3.01 (and later). To access ITG shell commands, connect an OTM PC or a TTY to the RS-232 Maintenance port on the IP trunk card faceplate.
Page 530 Page 530 of 644 Maintenance Table 60 General purpose commands (Part 2 of 4) Command Description IPInfoShow This command will return the following IP information: • IP addresses (for both management and voice networks) • default router (for both management and voice networks) •...
Page 531 Maintenance Page 531 of 644 Table 60 General purpose commands (Part 3 of 4) Command Description 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 subnet.
Page 532 Page 532 of 644 Maintenance Table 60 General purpose commands (Part 4 of 4) Command Description mRouteAdd “host/ network This command adds multiple routes to the same destination in IP address”, “IP Gateway”, the routing table. The route is added to the network portion of “Subnet mask”, “ToS value”, the routing table.
Page 533 Maintenance Page 533 of 644 Table 61 File transfer commands (Part 1 of 3) Command Description swDownload hostname, Update the software on the IP trunk card with the binary file username, password, received from an FTP server corresponding to the hostname IP directory path, filename address.
Page 534 Page 534 of 644 Maintenance Table 61 File transfer commands (Part 2 of 3) Command Description Example: ITG> bootpFileGet “ngals042”, “anonymous”, “guest”, “/bootpDir”, “bootptab” SNMPConfFileGet Update the SNMP configuration file on the IP trunk card with the hostname, username, SNMP configuration file on the indicated host, account and password, directory path, path.
Page 535 Maintenance Page 535 of 644 Table 61 File transfer commands (Part 3 of 3) Command Description traceFilePut hostname, The traceFilePut task on the host starts an FTP session with the username, password, given parameters and downloads the IP trunk card’s call trace directory path, filename file to the indicated location on the host.
Page 536 Page 536 of 644 Maintenance Table 62 NVRAM IP configuration commands Command Description NVRIPSet IP address Set the IP address in NVRAM. Example: ITG> NVRRIPSet “47.23.34.19” NVRGWSet IP gateway Set the default gateway address in NVRAM. Example: ITG> NVRRGWSet “47.0.0.1” NVRSMSet subnet mask Set the subnet mask in NVRAM.
Page 537 Maintenance Page 537 of 644 Table 63 DSP commands Command Description DSPReset DSP Number Reset the indicated DSP. Example: ITG>DSPReset 0 DSPSelfTest DSP Number Run self-test on the DSP. Example: ITG>DSPSelfTest 0 DSPNumShow Print number of DSPs on IP trunk card. Example: ITG>DSPNumShow DSPPcmLpbkTestOn...
Page 538 Page 538 of 644 Maintenance Table 64 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 •...
Page 539: Ip Trunk Card Self-Tests
Maintenance Page 539 of 644 Table 65 DCHIP-only commands (Part 2 of 2) Command Description DCHmenu This command allows the user to access the UIPC Debug Menu. Once in passthru mode, the user has to “exit” the Debug Menu, before issuing any other ITG Shell Commands. dchipResTableShow Available from ITG shell.
Page 540: Card Lan
Page 540 of 644 Maintenance Following the successful completion of these tests, the 8051XA controller attempts to bring up the processor by clearing the reset state and entering a timing loop in the anticipation of receiving a message from the processor. If this loop times out, it outputs an error to the RS-232 port.
Page 541: Field-Programmable Gate Array (Fpga) Testing
Maintenance Page 541 of 644 Field-Programmable Gate Array (FPGA) testing Before communicating with the system, the 8051XA controller downloads FPGA data files and performs tests to check correct programming of the FPGA. Outgoing calls attempted/completed mismatch The difference between the attempted and completed outgoing call numbers should never be less than the sum of the QoS Fallback, Address Translation fallback, and Calls Rejected fallback (totaled as “Outgoing Fallback”).
Page 542: Ip Trunk 3.01 (And Later) Upgrades
All upgrades are accomplished by updating the on-board application flash memory with the application. Software upgrades are performed from the OTM 2.1 (and later) PC. Nortel Networks recommends loading the application from the network, rather than the faceplate PC Card. Application upgrade On occasion, a field up-issue is done over the network.
Page 543 Maintenance Page 543 of 644 All patch commands on the Media Card 32-port and ITG-Pentium 24-port trunk cards are accessible at the ITG> shell prompt. These commands are summarized in Table 66 on page 544. The parameter string supplied to the command must be enclosed with double quotes.
Page 544 Page 544 of 644 Maintenance Table 66 lists the patch commands. Table 66 Patch commands (Part 1 of 3) Command Description pload Loads a patch file from the file system in Flash memory into DRAM memory. The loaded patch is inactive until it is put into service using the pins command. When a patch is successfully loaded, the pload command returns a patch handle number.
Page 545 Maintenance Page 545 of 644 Table 66 Patch commands (Part 2 of 3) Command Description poos Deactivates a patch (takes it out-of-service) by restoring the patched procedure to its original state. Syntax: poos “[handle]” If the poos command is issued without a parameter, the technician is prompted to enter a handle.
Page 546 Page 546 of 644 Maintenance Table 66 Patch commands (Part 3 of 3) Command Description plis Gives detailed patch status information for a loaded patch. Syntax: plis “[handle]” If the pout command is issued without a parameter, the technician is prompted to enter a handle.
Page 547: Flash Storage Upgrades
Procedure 70 Upgrading software using OTM 2.1 (and later) Download the latest IP Trunk 3.01 (and later) software version from Nortel Networks. Determine the location on the OTM 2.1 (and later) PC hard drive where it is to be loaded. Record the OTM PC hard drive location for use later in this procedure.
Page 548 Page 548 of 644 Maintenance Check the current software version of the IP trunk cards to be upgraded. To check the software version, double-click a card and click the Configuration tab. “S/W version” displays the current software version as read from the IP trunk card. From the main card list view, select the cards to be upgraded.
Page 549: Replace An Ip Trunk Card
Maintenance Page 549 of 644 12 Reboot each IP trunk card that received transmitted software, so that the new software can take effect. Start the rebooting with Leader 0, then Leader 1, and lastly the Follower cards. After all the IP trunk cards have been reset and have correctly rebooted, they respond to the OTM IP Trunk 3.01 (and later) status refresh (that is, disabled: active;...
Page 550 Page 550 of 644 Maintenance Procedure 71 Replacing an IP trunk card Locate the node of the defective IP trunk card: Open the ITG ISDN IP Trunks application in OTM. In the upper part of the IP Telephony Gateway - ISDN IP Trunk window, click the site name.
Page 551 Maintenance Page 551 of 644 11 Select menu Configuration > Synchronize > Transmit to transmit the Node Properties from OTM to the Active Leader card of the IP Trunk 3.01 (and later) node. Click the “Node Properties” box and then click “Start Transmit.”...
Page 552: Determine Ip Trunk Card Software Release
Page 552 of 644 Maintenance Disconnect the ELAN Ethernet cable and label it as the ELAN subnet connection. If connected, disconnect the DCH and maintenance cable from the NTCW84MA. Connect the new NTCW84LA cable to the I/O panel. Connect the ELAN, TLAN, DCH and Maintenance cables (if previously connected) to the I/O cable.
Page 553 Maintenance Page 553 of 644 Follow the steps in Procedure 73 to transmit IP trunk card properties and the dialing plan. Procedure 73 Transmitting IP trunk card properties and dialing plan In the IP Telephony Gateway window, select the replacement IP trunk card.
Page 554: Backup And Restore Procedures
Page 554 of 644 Maintenance Backup and restore procedures IP trunk card Data configured on the OTM 2.1 (and later) PC (for example, address translation tables and DSP configuration) is locally saved on the OTM PC. The data is also downloaded to the IP trunk cards. The IP trunk card stores this data in its internal Flash File volume (Flash EPROM, which acts as a disk drive).
Page 555: Fault Clearance Procedures
Maintenance Page 555 of 644 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 •...
Page 556: Card Failure
Page 556 of 644 Maintenance When the DSP recovers, all the associated channels are put into the “IDLE” state. “REStart” messages for all channels are sent to the system to reset the trunks to the “IDLE” state. The leader card is informed and incoming calls can be assigned to those channels.
Page 557 Maintenance Page 557 of 644 DCH link failure The DCH link can change to the RLS (Release) state due to technician action in LD 96, MSDL or SDI/DCH card failure, or cable failure. This condition is detected on the DCHIP card by the PC Card signaling that the L2 connection has failed.
Page 558: Media Card 32-Port Trunk Card Faceplate Maintenance Display Codes
Page 558 of 644 Maintenance Power loss Since the IP trunk card is based on Flash EPROM technology, all configuration data is preserved for 10 years. There is no requirement for a battery backup for the card. The IP trunk card can be removed from the IPE shelf indefinitely and still retain all configuration data.
Page 559 Maintenance Page 559 of 644 Table 67 Media Card 32-port trunk card faceplate maintenance display message summary (Part 2 of 3) Code Description 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...
Page 560 Page 560 of 644 Maintenance Table 67 Media Card 32-port trunk card faceplate maintenance display message summary (Part 3 of 3) Code Description T:22 CardLAN operational, A07 enabled, display now under host control BIOS Card is running the ROM BIOS. The card detected no valid IP Trunk 3.01 (and later) software image or the JKL escape sequence was entered during startup from the keyboard of a terminal...
Page 561: Itg-Pentium 24-Port Trunk Card Faceplate Maintenance Display Codes
Maintenance Page 561 of 644 In addition, if the IXP encounters any failures during its initialization, an H:XX error code displays. The list of error codes is listed in Table 68. Table 68 List of error codes Code Description H:00 Host Processor not booting H:01 SDRAM test failure...
Page 562 Page 562 of 644 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. Table 69 ITG-Pentium 24-port trunk card faceplate maintenance display message summary (Part 1 of 3)
Page 563 Maintenance Page 563 of 644 Table 69 ITG-Pentium 24-port trunk card faceplate maintenance display message summary (Part 2 of 3) Normal Fault Code Code Description T:16 F:16 Testing CEMUX interface T:17 F;17 Testing EEPROM T:18 F:18 Booting host, waiting for response with self-test information PT:0 PF:0...
Page 564 Page 564 of 644 Maintenance Table 69 ITG-Pentium 24-port trunk card faceplate maintenance display message summary (Part 3 of 3) Normal Fault Code Code Description BIOS Card is running the ROM BIOS. The card detected no valid IP Trunk 3.01 (and later) software image or the JKL escape sequence was entered during startup from the keyboard of a terminal connected to the local...
Page 565: System Performance Under Heavy Load
Maintenance Page 565 of 644 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.
Page 566: Message: Msdl0304
Page 566 of 644 Maintenance Normal resolutions The following are possible resolutions: • If the D-channel pack (such as MSDL) has multiple D-channels on it, the D-channel CPU might be unable to sustain the maximum traffic, especially if both or all D-channels peak at the same time. If this traffic level is sustained long enough, it can result in an MSDL0304 error message.
Page 567: Message: Bug4005
Maintenance Page 567 of 644 • If the MSDL card is an older vintage, it might be possible to upgrade the MSDL pack. This is the exception, rather than the rule; lower-capability MSDL packs have usually already been removed from service. Message: BUG4005 Description The system has lost a time slot, idling the applicable Call Register.
Page 568 Page 568 of 644 Maintenance 553-3001-363 Standard 2.00 September 2004...
Page 569: Appendix A: Patches And Advisements
Page 569 of 644 Appendix A: Patches and advisements Contents This section contains information on the following topics: Introduction ..........Introduction This appendix describes the following patches for IP Trunk 3.0 and IP Trunk 3.01: MPLR17662, MPLR17346, MPLR18142, and MPLR18157.
Page 570: Mplr17346
MPLR17346 Fax calls fail due to the wrong TCF method used for T.38 UDP Fax channel setup. The application on the CS 1000 and the BCM 3.5 use method 2 and IP Trunk 3.0 uses method 1. IP Trunk 3.01.22 patches The patches applicable to IP Trunk 3.01.22 are:...
Page 571 Nortel Networks recommends that the second alternative be used. Note: The nodes must use the Nortel H.323 Interoperability format or use a Gatekeeper to resolve destinations. The applicability of MPLR17662 is limited in certain situations: •...
Page 572 Page 572 of 644 Appendix A: Patches and advisements • The patch is not required for ITG Trunk 2.x.26G or ITG Trunk 2.x.25 interworking with IP Trunk 3.01.22, as these older versions of ITG Trunks do not support the CSE format. •...
Page 573: Appendix B: Cable Description And
Page 573 of 644 Appendix B: Cable description and NT8D81BA cable replacement Contents This section contains information on the following topics: Introduction ..........NTMF94EA ELAN, TLAN and Serial Port cable .
Page 574: Introduction
Page 574 of 644 Appendix B: Cable description and NT8D81BA cable replacement Introduction This appendix describes the NTMF94EA, NTCW84KA, NTAG81CA, NTAG81BA, NTCW84LA, and NTCW84MA cables. This appendix also explains how to replace the NT8D81BA ribbon cable with the NT8D81AA ribbon cable. Replace the NT8D81BA ribbon cable, with a NT8D81AA cable if the a network uses 100-Base-T.
Page 575 Appendix B: Cable description and NT8D81BA cable replacement Page 575 of 644 Table 70 NTMF94EA ELAN, TLAN and Serial Port cable connections I/O Panel: P1 Signal Name P2, P3, P4 Color P1-21 BSOUTB- P2-2 P1-22 BDTRB- P2-4 Green P1-25 SGND P2-5 Brown P1-45...
Page 576: Ntcw84Ka Elan, Tlan, Dch & Serial Cable
Page 576 of 644 Appendix B: Cable description and NT8D81BA cable replacement NTCW84KA ELAN, TLAN, DCH & serial cable The NTCW84KA cable connects the I/O connector on Cabinet or Large systems to the Ethernet management and telephony voice ports with one RS-232 port and D-channel signalling.
Page 577 Appendix B: Cable description and NT8D81BA cable replacement Page 577 of 644 Table 71 NTCW84KA ELAN, TLAN, DCH & Serial I/O cable connections (Part 1 of 2) I/O Panel: P1 Signal Name P2, P3, P4, P5 Color P1-21 BSOUTB- P2-2 P1-22 BDTRB- P2-4...
Page 578: Ntag81Ca Faceplate Maintenance Cable
Page 578 of 644 Appendix B: Cable description and NT8D81BA cable replacement Table 71 NTCW84KA ELAN, TLAN, DCH & Serial I/O cable connections (Part 2 of 2) I/O Panel: P1 Signal Name P2, P3, P4, P5 Color P1-10 P5-2 Black P1-13 P5-10 P1-11...
Page 579 Appendix B: Cable description and NT8D81BA cable replacement Page 579 of 644 Figure 149 NTAG81CA PC maintenance cable Table 72 NTAG81CA Faceplate Maintenance cable connections 8-pin 9-pin Signals Mini-DIN D-sub (IP Trunk 3.01 (ITG Side) (PC Side) Signals (and later) Side) Male Female (PC Side)
Page 580: Ntag81Ba Maintenance Extender Cable
Page 580 of 644 Appendix B: Cable description and NT8D81BA cable replacement NTAG81BA Maintenance Extender cable The 3m NTAG81BA cable connects the NTAG81CA cable to a PC or terminal. It has a 9-pin D-type connector at both ends: one male, one female. (See Figure 150 and Table 73.) Figure 150 NTAG81CA Maintenance Extender cable...
Page 581: Ntcw84Ea Dch Pc Card Pigtail Cable
Appendix B: Cable description and NT8D81BA cable replacement Page 581 of 644 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.
Page 582 Page 582 of 644 Appendix B: Cable description and NT8D81BA cable replacement Figure 151 NTCW84EA pigtail cable I T G Header PCMCIA NTCW84EA Pigtail cable G200X15 553-3001-363 Standard 2.00 September 2004...
Page 583: Ntmf04Ba Msdl Extension Cable
Appendix B: Cable description and NT8D81BA cable replacement Page 583 of 644 Table 74 NTCW84EA pigtail cable connections PC Card P1 Signal Name Color P1-1 SDAI P2-1 Black P1-2 RDAI P2-2 White P1-3 STAI P2-3 P1-4 RTAI P2-4 Green P1-5 P2-5 Brown P1-8...
Page 584 Page 584 of 644 Appendix B: Cable description and NT8D81BA cable replacement Figure 152 NTMF04BA MSDL extension cable 15-way Male D-Sub 15-way Female D-Sub Table 75 NTMF04BA MSDL extension cable connections P1 – Male P2 – Female Color Signal P1-2 P2-2 Black SDA+...
Page 585: Ntcw84La And Ntcw84Ma Upgrade Cables
Appendix B: Cable description and NT8D81BA cable replacement Page 585 of 644 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.
Page 586 Page 586 of 644 Appendix B: Cable description and NT8D81BA cable replacement Figure 153 NTMF94LA upgrade cable Mounting Screw Shielded RJ-45 Cable Shielded 25-Pair Amphenol Connector Shielded RJ-45 Mating Coupler To Hub Ferrite To Hub 9-Pin D-Sub Female 15-Pin D-Sub Female 553-3001-363 Standard 2.00...
Page 587 Appendix B: Cable description and NT8D81BA cable replacement Page 587 of 644 Table 76 NTMF94LA cable connections (Part 1 of 2) I/O Panel: P1 Signal Name P2, P3,P4 Color P1-21 BSOUTB- P2-2 P1-22 BDTRB- P2-4 GREEN SGRND P2-5 BROWN P1-45 BSINB- P2-3 BLUE...
Page 588 Page 588 of 644 Appendix B: Cable description and NT8D81BA cable replacement Table 76 NTMF94LA cable connections (Part 2 of 2) I/O Panel: P1 Signal Name P2, P3,P4 Color P1-11 STAI P4-9 BLACK P1-14 STBI P4-11 WHITE P1-35 RDAI P4-4 BLACK P1-38 RDBI...
Page 589: Prevent Ground Loops On Connection To External Customer Lan Equipment
Appendix B: Cable description and NT8D81BA cable replacement Page 589 of 644 Prevent ground loops on connection to external customer LAN equipment The shielded RJ-45 coupler is the connection point for the customer’s shielded CAT 5 LAN cable to the hub, switch, or router supporting the TLAN subnet and ELAN subnet.
Page 590: Replace Cable Nt8D81Ba With Nt8D81Aa
Page 590 of 644 Appendix B: Cable description and NT8D81BA cable replacement Replace cable NT8D81BA with NT8D81AA This section explains how to replace the NT8D81BA cable with the NT8D81AA cable and how to install the NTCW84JA special IPE filter. Cables are designated by the letter of the I/O panel cutout (A, B, C, and so on) where the 50-pin cable connector is attached.
Page 591 Appendix B: Cable description and NT8D81BA cable replacement Page 591 of 644 Table 77 NT8D37 cable connections Backplane slots–shroud rows I/O panel/cable designation L0–1, 2, 3 L1–1, 2, 3 L2–1, 2, 3 L3–1, 2, 3 L4–1, 2, 3 L5–1, 2, 3 L6–1, 2, 3 L7–1, 2, 3 L8–1, 2, 3...
Page 592: Tools List
Page 592 of 644 Appendix B: Cable description and NT8D81BA cable replacement Figure 154 Backplane slot designations Segment 3 Segment 2 Segment 1 Segment 0 L15 L14 L13 L12 L11 L10 L9 553-5391 Tools list • Ty-wrap cutter • Ty-wraps •...
Page 593: Remove The Nt8D81Ba Cable
Appendix B: Cable description and NT8D81BA cable replacement Page 593 of 644 Remove the NT8D81BA cable Follow the steps in Procedure 75 to remove the NT8D81BA cable. Procedure 75 Removing the NT8D81BA cable Identify the I/O panel and backplane designation that corresponds to the LEFT slot of the pair of card slots, viewed from the front, in which the Media Card 32-port or ITG-Pentium 24-port trunk card was installed.
Page 594 Page 594 of 644 Appendix B: Cable description and NT8D81BA cable replacement Install connector 3, (labeled UP3^) into backplane shroud 3. Dress ribbon cables back individually inside the rear of the IPE module and restore the original arrangement. Start with the cables that are going to be underneath.
Page 595: Appendix C: Environmental And Electrical Regulatory Data
Page 595 of 644 Appendix C: Environmental and electrical regulatory data Contents This section contains information on the following topics: Environmental specifications ....... . Mechanical conditions .
Page 596: Environmental Specifications
Page 596 of 644 Appendix C: Environmental and electrical regulatory data Environmental specifications Table 78 lists measurements of performance under test conditions of temperature and shock. Table 78 Media Card 32-port and ITG-Pentium 24-port trunk card temperature and humidity specifications Specification Minimum Maximum...
Page 597: Mechanical Conditions
Appendix C: Environmental and electrical regulatory data Page 597 of 644 Mechanical conditions Refer to Table 79 for Media Card 32-port and ITG-Pentium 24-port trunk card mechanical tolerance ranges. Table 79 Media Card 32-port and ITG-Pentium 24-port trunk card mechanical specifications Specification Minimum Maximum...
Page 598: Safety
Page 598 of 644 Appendix C: Environmental and electrical regulatory data Safety Table 80 provides a list of safety regulations met by the ITP-P 24-port trunk card, with the type of regulation and the country or area covered by each regulation.
Page 599: Electromagnetic Compatibility (Emc)
Appendix C: Environmental and electrical regulatory data Page 599 of 644 Electromagnetic Compatibility (EMC) Electromagnetic emissions regulations met by the ITP-P 24-port trunk card, along with the country’s regulation standards, are listed in Table 82. Table 82 Electromagnetic emissions regulations met by the ITG-Pentium 24-port trunk cards Regulation identifier Regulatory agency FCC part 15 Class A...
Page 600 Page 600 of 644 Appendix C: Environmental and electrical regulatory data There are no limitations on the number of Media Card 32-port trunk cards that can be installed in any Meridian 1/CS 1000M system, with one exception. The number of Media Card 32-port trunk cards that can be installed in an IPE Cabinet (Large System) for Class B compliance (EN55022:1998 and EN55024:1998) is limited to 10.
Page 601 Appendix C: Environmental and electrical regulatory data Page 601 of 644 Table 84 Electromagnetic immunity regulations met by the ITG-P 24-port trunk card (Part 2 of 2) Regulation identifier Regulatory agency SS-447-20-22 Sweden EMC standard AS/NZS 3528 EMC (Australia/New Zealand) NFC 98020 France EMC standard Electromagnetic immunity regulations met by the Media Card 32-port trunk...
Page 602 Page 602 of 644 Appendix C: Environmental and electrical regulatory data 553-3001-363 Standard 2.00 September 2004...
Page 603: Appendix D: Subnet Mask Conversion From Cidr To Dotted Decimal Format
Page 603 of 644 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.
Page 604 0. The complete subnet mask in dotted decimal format is 255.255.240.0. Table 86 CIDR format remainders Remainder of CIDR format value divided by 8 Binary value Dotted decimal value 1000 0000 1100 0000 1110 0000 1111 0000 1111 1000 1111 1100 1111 1110 553-3001-363 Standard 2.00...
Page 605: Appendix E: Cli Commands
Page 605 of 644 Appendix E: CLI commands IP Trunk 3.01 (and later) supports the following CLI commands: • ectailDefault – set IP Trunk 3.01 (and later) to use the default 128ms Echo Canceller Tail length. • ectailNonDefault – set IP Trunk 3.01 (and later) to use the Echo Canceller Tail length specified in the OTM File.
Page 606 Page 606 of 644 Appendix E: CLI commands 553-3001-363 Standard 2.00 September 2004...
Page 607: Appendix F: Configure A Netgear Rm356
Meridian 1/CS 1000M site management and signalling LAN (called the Embedded LAN or ELAN subnet) to provide remote support access for ITG and other IP-enabled Nortel Networks products. The Nortel Networks Netgear RM356 modem router integrates the functions of a V.90 modem, a PPP remote access server, an IP router, and a...
Page 608: Security Features Of The Rm356 Modem Router
Page 608 of 644 Appendix F: Configure a Netgear RM356 modem router for remote access Note: Do not install a modem router on the ELAN subnet without the explicit approval of the customer's IP network manager. The RM356 modem router is not secure unless it is configured correctly, according to the customer's network security policy and practices.
Page 609 CAT 5 10BaseT Ethernet cables to connect the modem router to the Management interface of a maximum of four IP trunk cards. Other IP-enabled Nortel Networks products on the ELAN subnet can be connected to the RM356 modem router, including the Meridian 1/CS 1000M, a local OTM PC, Symposium Call Center Server, and CallPilot.
Page 610: Configure The Otm Pc To Communicate With A Remote System
Page 610 of 644 Appendix F: Configure a Netgear RM356 modem router for remote access Configure the OTM PC to communicate with a remote system site through a modem router If the customer’s version of OTM does not support the modem router communication profile for Meridian 1/CS 1000M system types, work around the limitation by configuring a Dial-up Networking (DUN) session under Windows to connect to the modem router at a particular system site.
Page 611 Appendix F: Configure a Netgear RM356 modem router for remote access Page 611 of 644 Enter the default RM356 manager password: 1234 The "RM356 Main Menu" appears. Enter menu selection number 1 to access "General Setup" under the "Getting Started" section of the "RM356 Main Menu." “Menu 1 –...
Page 612 Page 612 of 644 Appendix F: Configure a Netgear RM356 modem router for remote access Note 1: 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.01 (and later) nodes on remote ELAN subnets, define a default network route pointing to the Management Gateway IP address on the local ELAN subnet.
Page 613 Set “Callbacks/No” according to the customer's network security policy and practices. Nortel Networks Customer Technical Services (CTS), does not currently accept callback security calls from the modem router. Set “Rem CLID=” to the PSTN Calling Number that is displayed when the remote OTM PC dials up the modem router, if CLID authentication is required for the user profile.
Page 614: Rm356 Modem Router Manager Menu (Application Notes On The Elan Installation)
Page 614 of 644 Appendix F: Configure a Netgear RM356 modem router for remote access Press Enter to confirm and save data to ROM, then press Esc to return from the sub-menu to the main menu. 20 Enter menu selection number 23 to access "System Password" under the "Advanced Management"...
Page 615 Appendix F: Configure a Netgear RM356 modem router for remote access Page 615 of 644 Menu 1 - General Setup System Name= Room_304_RCH_Training_Center Location= Sherman Ave., Richardson, TX 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...
Page 616 Page 616 of 644 Appendix F: Configure a Netgear RM356 modem router for remote access Size of Client IP Pool= N/A Primary DNS Server= N/A Secondary DNS Server= N/A TCP/IP Setup: IP Address= 47.177.16.254 IP Subnet Mask= 255.255.255.0 RIP Direction= None Version= RIP-2B Press ENTER to Confirm or ESC to Cancel: Press Space Bar to Toggle.
Page 617 Appendix F: Configure a Netgear RM356 modem router for remote access Page 617 of 644 Menu 13 - Default Dial-in Setup Telco Options: IP Address Supplied By: CLID Authen= None Dial-in User= No IP Pool= Yes PPP Options: IP Start Addr= 47.177.16.253 Recv Authen= PAP Compression= No Session Options:...
Page 618 Page 618 of 644 Appendix F: Configure a Netgear RM356 modem router for remote access User Name= itgadmin Active= Yes Password= ******** Callback= No Phone # Supplied by Caller= N/A Callback Phone #= N/A Rem CLID= Idle Timeout= 500 Press ENTER to Confirm or ESC to Cancel: Menu 21 - Filter Set Configuration Filter Filter...
Page 619 Appendix F: Configure a Netgear RM356 modem router for remote access Page 619 of 644 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.0...
Page 620 Page 620 of 644 Appendix F: Configure a Netgear RM356 modem router for remote access Menu 24.1 -- System Maintenance - Status Port Status Speed TXPkts RXPkts Errs Tx B/s Rx B/s Up Time Idle 0Kbps 16206 12790 0:00:00 Total Outcall Time: 0:00:00 Ethernet: Name: Room_304_RCH_Traini...
Page 621 Appendix F: Configure a Netgear RM356 modem router for remote access Page 621 of 644 179763 PINI INFO SMT Session End 179772 PP09 INFO Password pass 179772 PINI INFO SMT Session Begin 179775 PINI INFO SMT Session End 179783 PP09 INFO Password pass 179783 PINI...
Page 622 Page 622 of 644 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.
Page 623: Contents
Page 623 of 644 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 ....... . Before you begin .
Page 624: Upgrade Procedure Summary
Page 624 of 644 Appendix G: Upgrade an ITG Trunk 1.0 node to support ISDN signaling trunks This Appendix is included as a reference for ITG Trunk 1.0 customers who wish to upgrade their systems to ITG Trunk 2.0 to include ISDN Signaling Link (ISL) capabilities.
Page 625 Table 3 on page 48 lists required software packages. Check the Nortel Networks website to find the latest ITG 8-port trunk card software. Go to www.nortelnetworks.com. Follow the links to Customer Support and Software Distribution or go to www.nortelnetworks.com/support.
Page 626: Install The Dchip Hardware Upgrade Kit
SDI/DCH card. If cards are in place, make sure each card has an available port. Verify that the customer site has a Nortel Networks 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 Networks products.
Page 627 Appendix G: Upgrade an ITG Trunk 1.0 node to support ISDN signaling trunks Page 627 of 644 Procedure 81 Installing the DCHIP hardware upgrade kit Disable all ITG 8-port trunk cards in the node to be upgraded. Disable the cards in LD 32 (DISI l s c for Large systems, DISI c for Cabinet systems). Wait for the NPR0011 message, which indicates that all units on each card are disabled.
Page 628: Install The Dchip I/O Panel Breakout Cable From The Upgrade Kit
Page 628 of 644 Appendix G: Upgrade an ITG Trunk 1.0 node to support ISDN signaling trunks Figure 155 DCHIP PC Card and NTCW84EA pigtail cable 8 port DaughterBoard NTCW84EA Pigtail Cable DCHIP PC Card Pin header Pull the top and bottom locking devices away from the trunk card faceplate.
Page 629: Isl Trunk Software
Appendix G: Upgrade an ITG Trunk 1.0 node to support ISDN signaling trunks Page 629 of 644 If installing the DCHIP upgrade kit for the NTCW80CA ITG 8-port trunk card, use the NTCW84LA I/O Panel breakout cable. Procedure 82 Installing the DCHIP I/O Panel breakout cable from the upgrade kit 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.
Page 630 Page 630 of 644 Appendix G: Upgrade an ITG Trunk 1.0 node to support ISDN signaling trunks Procedure 83 Removing the ITG Trunk 1.0 configuration files From the OTM IP Telephony Gateway - ISDN IP Trunk Main window, select the card from the lower half of the window and right-click. A context menu appears.
Page 631: Step 2 - Transmit Itg Trunk 2.0 Software To The Itg 8-Port Trunk Cards
If the ITG shell displays command not found, check the spelling of the command. If the ITG shell displays a value of –1, contact Nortel Networks customer technical support. Return to the OTM IP Telephony Gateway - ISDN IP Trunk Main window.
Page 632 Page 632 of 644 Appendix G: Upgrade an ITG Trunk 1.0 node to support ISDN signaling trunks Locate the ITG28xx.mms software file on the OTM PC. If the path to the ITG28xx.mms software file is known, type the path information in the Software field.
Page 633 Appendix G: Upgrade an ITG Trunk 1.0 node to support ISDN signaling trunks Page 633 of 644 At this point, the trunk cards have ITG 2.0 ISDN functionality and are in the state of new ITG 8-port trunk cards that need to be configured. Refer to “Configure IP Trunk 3.01 (and later) data”...
Page 634: Remove Itg Trunk 1.0 Configuration Data From Meridian 1
Page 634 of 644 Appendix G: Upgrade an ITG Trunk 1.0 node to support ISDN signaling trunks Remove ITG Trunk 1.0 configuration data from Meridian 1 Follow the steps in Procedure 85 to remove the ITG Trunk 1.0 configuration data from Meridian 1. Procedure 85 Removing the ITG Trunk 1.0 configuration data from Meridian 1 Out existing ITG basic trunks that are being upgraded to ITG ISL trunks:...
Page 635 Appendix G: Upgrade an ITG Trunk 1.0 node to support ISDN signaling trunks Page 635 of 644 Remember to make certain changes to the RLB entry in LD 86. For the ITG/ISL TIE Trunk Route, configure SBOC = RRA to enable Fallback routing to circuit-switched trunks.
Page 636: 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 Networks technical support. Upgrade Troubleshooting This section provides two procedures to correct OTM upgrade problems.
Page 637 Appendix G: Upgrade an ITG Trunk 1.0 node to support ISDN signaling trunks Page 637 of 644 Procedure 87 Upgrading software using the ITG shell Prepare the OTM ITG FTP server to find the software image file when it is requested from the ITG card BIOS shell using the upgrade or swDownload command.
Page 638 Page 638 of 644 Appendix G: Upgrade an ITG Trunk 1.0 node to support ISDN signaling trunks 553-3001-363 Standard 2.00 September 2004...
Page 639 Page 639 of 644 Index Symbols "Ping-Pong" effect 159 backplanes connectors 590 Numerics I/O panel connections 591 Backup Leader 56 10/100BaseT 65 Baystack 450 218 10/100BaseT Ethernet ports 207 BCM 2.5 FP1 38 100BaseT full-duplex 217 BLDR 69 100BaseTX 46 10BaseT 46 10BaseT Ethernet hub 47 Call Server 37...
Page 640 Page 640 of 644 Index Codecs 46 Ethernet ports 207 codecs 114 compression algorithm 114 FACILITY redirect 37 connectors 590 facility restriction levels 186 control packets 106 fall back threshold algorithm 227 CPND 45 Fallback 103 CS 1000M 29 Fallback to alternate facilities functionality 103 CS 1000S 29 Fallback to alternate trunk facilities 103 far end Leader 103...
Page 641 Index Page 641 of 644 GRQ 35 ITG-Pentium 24-port trunk card 47 ITU-T Recommendation G.107 101 H.225 87 H.323 45 jitter 98 H.323 identifier 34 jitter buffer 227 H.323 protocol 87 Jitter buffer parameters 220 H.323 V.2 108 half-duplex 217 Large Systems 47 half-duplex 10BaseT 217 Latency 100...
Page 642 Page 642 of 644 Index NT0966AA 65 NT8D37 IPE Modules QoS 99 cable connections 591 QoS-managed network 46 NT8D37BA IPE Modules 590 QSIG support 39 NT8D37EC IPE Modules 590 Quality of Service 105 NTAK02BB 47 queuing 98 NTAK02BB SDI/DCH 87 NTCW80 8-port trunk card 45 NTCW84KB 70 RADIUS client 110...
Page 643 Index Page 643 of 644 silence suppression 150 Type of Service 105 Silence Suppression parameters 220 Small Systems 47 UDP port 1719 174 SNMP manager 63 UDP port 2300-2363 175 SNMP trap 63 UDP port 5000 175 starting port value 410 unable to communicate after transmitting properties Step Back on Congestion over ISDN 103 Stepback on Congestion over ISDN 102...
Page 644: Contents
Page 644 of 644 Index 553-3001-363 Standard 2.00 September 2004...
Page 646 Copyright © 2003—2004 Nortel Networks All Rights Reserved Information is subject to change without notice. Nortel Networks reserves the right to make changes in design or components as progress in engineering and manufacturing may warrant. SL-1, Meridian 1, and Succession are trademarks of Nortel Networks.

Nortel 1000 Description, Installation And Operation Manual

About this Document

Overview of IP Trunk 3.01

System Description

ITG Engineering Guidelines

OTM 2.1 (and Later) Management and Configuration of IP Trunk 3.01 (and Later)

Install and Configure IP Trunk 3.01

(And Later) Node

Provisioning IP Trunk 3.01 (and Later) in OTM 2.1 (and Later)

OTM 2.1 (and Later) OA&M Using OTM 2.1 (and Later) Applications

Quick Links

Related Manuals for Nortel 1000

Summary of Contents for Nortel 1000