Gebruiksaanwijzing /service van het product NN43001-563 van de fabrikant Nortel Networks
Ga naar pagina of 492
Nor tel Communication Ser v er 1000 IP T r unk Fundamentals NN43001-563 ..
Document status: Standard Document version: 02.01 Document date: 21 December 2007 Copyright © 2007, Nor tel Networks All Rights Reser v ed. Sourced in Canada LEGAL NO TICE While the information in th.
3 Contents New in this Release 15 Other changes 15 How to Get Help 17 Getting help from the Nor tel web site 17 Getting help over the telephone from a Nor tel Solutions Center 17 Getting help from a specialist by using an Express Routing Code 17 Getting help through a Nor tel distributor or re-seller 18 Overview of IP T runk 3.
4 Contents Description 46 F aceplate indicators, controls, and interfaces 47 Backplane interf aces 50 Assembly description 50 Media Card 32-por t trunk card (NTVQ01BB) 51 Description 51 NTVQ01BB Hardw.
Contents 5 IP T runk 3.01 (and later) SNMP agent 83 Codec profiles 84 G.711 84 G.729AB 85 G.729B 85 G.723.1 (5.3 kbit/s or 6.3 kbit/s) 85 Security passwords 86 Administrator le vel 86 T echnical supp.
6 Contents IP T runk 3.01 (and later) DiffSer v suppor t f or IP QoS 128 Queue management 129 Use of F rame Relay and A TM services 129 Internet Protocols and por ts used by IP T runk 3.
Contents 7 Jitter buff er parameters (voice play out delay) 162 Silence Suppression parameters (V oice Activity Detection) 163 F allback threshold 164 Setting the QoS threshold for f allback routing 164 P ost-installation network measurements 164 Set ITG QoS objectives 165 Intranet QoS monitoring 166 SNMP network management 167 IP T runk 3.
8 Contents Install filter and NTND26 cable (f or MSDL and DCHIP cards in same Large System equipment row) 200 Install filter and NTND26 cable (f or MSDL and DCHIP cards in diff erent Large System eq.
Contents 9 Create the IP T runk 3.01 (and later) node dialing plan using TM 3.1 253 Retriev e the IP T runk 3.01 (and later) node dialing plan using TM 3.
10 Contents ITG Card Proper ties Configuration window 349 DSP maintenance window 349 D-channel maintenance 350 T ransmit configur ation data 350 Add an IP T r unk 3.01 (and later) node on TM 3.1 by retrieving an e xisting node 353 Retriev e and add an IP T runk 3.
Contents 11 Disable the indicated IP trunk card 386 Disable the indicated IP trunk card when idle 386 Enable an indicated IP trunk card 386 Disable an indicated IP trunk card por t 386 Enable an indic.
12 Contents Media Card 32-por t tr unk card faceplate maintenance displa y codes 423 ITG-P entium 24-por t trunk card f aceplate maintenance display codes 425 System performance under heavy load 428 M.
Contents 13 Appendix D Subnet mask con version from CIDR to dotted decimal format 457 Appendix E CLI commands 459 Appendix F Configure a Netg ear RM356 modem router for remote access 461 Contents 461 Introduction 461 Security features of the RM356 modem router 462 Install the RM356 modem router 462 Configure the TM 3.
14 Contents Nor tel Communication Ser v er 1000 IP T r unk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nor tel Networks .
15 Ne w in this Release There hav e been no updates to the document in this release. Other changes Revision History December 2007 Standard 02.01. This document has been up-issued to support Communication Server Release 5.5. May 2007 Standard 01.01. This document is issued to support Communication Server 1000 Release 5.
16 New in this Release Nor tel Communication Ser v er 1000 IP T r unk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nor tel Networks .
17 Ho w to Get Help This chapter explains how to get help for Nor tel products and ser vices. Getting help from the Nor tel web site The best wa y to get technical suppor t for Nor tel products is from the Nor tel T echnical Suppor t web site: h ttp://www .
18 How to Get Help http://www .nor tel.com/erc Getting help through a Nor tel distributor or re-seller If you purchased a service contract f or your Nor tel product from a distr ibutor or authorized re-seller , contact the technical suppor t staff f or that distributor or re-seller .
19 Overview of IP T runk 3.01 Contents This section contains information on the follo wing topics: "Introduction" (page 19) "Startup and registration" (page 23) "IP Trunk 3.01 (and later) and CS 1000S/CS 1000M" (page 25) "Codec selection" (page 27) "IP Trunk 3.
20 Overview of IP T runk 3.01 In addition to routing IP T elephony calls with locally configured call-routing options, IP T r unk 3.01 takes advantage of the centr alized IP T elephony call routing of an H.323 Gatekeeper residing on a Signaling Ser v er elsewhere on the network.
Introduction 21 • handles the call based on the retur n message from the Gatek eeper IP T runk 3.01 (and later) accesses additional devices through the Gatekeeper . It is no longer necessar y to individually provision the entire mesh at each IP T r unk 3.
22 Overview of IP T r unk 3.01 W ARNING The only Gatek eeper that IP T runk 3.01 (and later) officially suppor ts is the CS 1000M Gatekeeper . Gatekeeper calls made between the CS 1000M system and IP T runk 3.01 (and later) are directly-routed calls.
Star tup and registration 23 Figure 3 "Gatekeeper-routed call" (page 23) represents a Gatekeeper-routed call. The destination IP address provided b y the Gatek eeper is the Gatekeeper’s IP address. All messages are routed through the Gatekeeper .
24 Overview of IP T r unk 3.01 The flag value is ignored when the provisioned Gatek eeper is a CS 1000M Gatekeeper . On star tup, if the IP T runk 3.01 (and later) Leader is provisioned to use a Gatekeeper , it seeks out and locates the Gatekeeper using RAS signalling and then registers with the Gatek eeper using an RRQ.
IP T runk 3.01 (and later) and CS 1000S/CS 1000M 25 CS 1000M do not require a Gatek eeper Request from IP T r unk 3.01 (and later); therefore , no Request or Confir m is sent. 2. Gatekeeper Confirm (GCF) – F rom the Gatek eeper to the Active Leader , with the functional Gatekeeper IP address.
26 Overview of IP T r unk 3.01 H.323 RAS, IP T r unk 3.01 (and later) uses RAS Messaging to register with the Gatekeeper if provisioned to do so . IP T r unk 3.
IP T runk 3.01 (and later) requirements 27 There are no direct media paths between the Meridian 1 telephones and the CS 1000M telephones. There are direct paths between the IP T r unk 3.
28 Overview of IP T r unk 3.01 Ta b l e 1 IP T runk 3.01 (and later) packa g e requirements Package Name Package Number Package description Comments BARS 57 Basic Alternate Route Selection Package 57 and/or 58 is required. NARS 58 Network Alternate Route Selection Package 57 and/or 58 is required.
29 System description Contents This section contains information on the follo wing topics: "IP Trunk 3.01 (and later) application" (page 31) "System requirements" (page 32) "Hardware components for IP Trunk 3.
30 System description "Software upgrade" (page 59) "Interoperability with earlier versions of ITG Trunk" (page 60) "Fax Tone Detection Configuration" (page 61) "ISDN.
IP T runk 3.01 (and later) application 31 "G.723.1 (5.3 kbit/s or 6.3 kbit/s)" (page 85) "Security passwords" (page 86) "Administrator level" (page 86) "Technical support level" (page 86) IP T runk 3.01 (and later) application IP T r unk 3.
32 System description Figure 4 "IP T r unk 3.01 (and later) connectivity" (page 32) shows an IP T r unk 3.01 (and later) configuration e xample. Figure 4 IP T runk 3.01 (and later) connectivity In this document, TLAN subnet ref ers to the T elephony LAN subnet that transmits the ITG voice and f ax traffic.
Hardware components for IP T runk 3.01 (and later) 33 cards to suppor t ISDN functionality . Earlier vintages are not suppor ted, as the le vel of MCDN functionality required to suppor t ITG-compatible ISL is not av ailable on earlier vintages. Install a modem router on the ELAN subnet to provide remote suppor t access for IP T runk 3.
34 System description Ta b l e 3 Hard ware components for the Media Card 32-port trunk Component Product code The package includes the following: • NTVQ90 – Media Card 32-port trunk card • NTVQ8.
Hardware components for IP T runk 3.01 (and later) 35 Inspect the IPE module to deter mine if it is equipped with non-removab le Molded Filter Connectors on the I/O P anel.
36 System description Component Product codes IP Trunk 3.01 (and later) NTP CD-ROM – Multilingual NTVQ61BA PC Cards C7LIU DCH PC Card with Layer 2 DCH Software NTWE07AA Ordering rules and guidelines IP T runk 3.
Ordering r ules and guidelines 37 F or SDI/DCH and DCHIP cards that reside in different Small System cabinets, order: • NTWE04A C Inter-cabinet cable (NTCW84KA to SDI/DCH cable-10 ft) If IP tr unk c.
38 System description IP trunk card description The Media Card 32-por t tr unk card and ITG-P entium 24-por t tr unk card provide a cost-eff ective solution f or high-quality voice and f ax transmission ov er an IP network. The IP T runk cards are an IPE-based assembly designed for installation in a Meridian 1/CS 1000M IPE shelf.
IP tr unk card description 39 NTVQ01BB Media Card 32-por t trunk cards are factory-programmed with Release 8.0 fir mware. Any firmware feature upgr ades are av ailable on the Nor tel website. Download this fir mware from the Customer Suppor t Software page.
40 System description The Leader , Backup Leader , F ollower , and DCHIP cards communicate through their ELAN network interf aces. For more inf or mation, see "Inter net Protocols and por ts used by IP T r unk 3.
IP tr unk card description 41 Backup Leader The Backup Leader card steps in when the Leader is out-of-ser vice. This minimizes service interr uptions. D-channel IP gatewa y The ITG-P entium 24-por t o.
42 System description (and later) D-channel only controls IP trunk cards in the same IP T runk 3.01 (and later) node. TM 3.1 administration relates the cards with trunks to the DCHIP IP trunk card. The IP tr unk card uses ISDN messages for call control and communicates with the Meridian 1/CS 1000M through the PC Card, using the RS-422 link.
IP tr unk card description 43 Card combinations The Leader and DCHIP , or Follo wer and DCHIP , functions can reside on a single IP trunk card or multiple IP tr unk cards. If a F ollower card is equipped with a DCH PC card, it can function as a DCHIP trunk card.
44 System description Each customer requires one or more dedicated IP T runk 3.01 (and later) nodes. T runks on the same IP T r unk 3.01 (and later) node share the same dialing plan and IP network connectivity . IP T r unk 3.01 (and later) trunks cannot be shared between customers that hav e independent numbering plans and IP networks.
IP tr unk card description 45 Active Leader and Backup Leader interaction When a Leader card reboots into service, it sends bootp requests to check whether an Active Leader card is present. If it receives a bootp response, this indicates the presence of an Active Leader card and the rebooting Leader becomes the Backup Leader .
46 System description When a DCHIP tr unk card f ailure occurs, the associated tr unks’ states appear b usy to the Mer idian 1/CS 1000M, so the trunks will not be used f or calls. This b locks the nor mal software action of rev er ting to analog signaling when an ISL DCH f ails.
ITG-P entium 24-por t tr unk card (NT0961AA) 47 Figure 7 ITG-Pentium 24-port trunk card system connectivity and messaging Faceplate indicator s, contr ols, and interfaces The NT0961AA ITG-P entium 24-.
48 System description Figure 8 NT0961AA ITG-Pentium 24-port trunk card Card Status LED A single red, card status LED on the faceplate indicates the enabled/disab led status of the 24 por ts on the card. The LED is lit (red) dur ing the power-up or reset sequence.
ITG-P entium 24-por t tr unk card (NT0961AA) 49 During configuration, the error message "F:10" can appear . This error indicates a missing Secur ity De vice. It occurs because Secur ity Devices are not implemented on ITG T r unk 2.0. Ignore this message.
50 System description RS-232 maintenance por t The ITG-P entium 24-por t card has a DIN-8 (RS-232) maintenance por t (DCE) connection on the f aceplate and an alter native connection to the same serial por t on the I/O bac kplane.
Media Card 32-por t trunk card (NTVQ01BB) 51 CA UTION Service Interruption The ITG-P entium 24-por t trunk card is not user-ser viceable. Figure 9 "Mechanical assembly" (page 51) is for inf or mation pur poses only . Do not remov e the daughterboard from the motherboard.
52 System description Figure 10 Media Card 32-port trunk card The base hardware (known as the Media Card) enhances cabling arrangements f or installation and maintenance. NTVQ01BB Hard ware NTVQ01BB Media Card 32-por t trunk card is an improved v ersion of NTVQ01BA Media Card 32-por t trunk card.
Media Card 32-por t trunk card (NTVQ01BB) 53 • The onboard FPGAs are changed to the advanced f amily of device architecture. • A new Compact Flash Dr ive is used for onboard C: Drive. • The f aceplate has been re-designed for better ergonomics. • New fir mware is de veloped to implement the abo ve design enhancements.
54 System description PC Card slot This slot (designated as Slot A:) accepts a T ype I or II PC Card. It also suppor ts a DCHIP interf ace PC Card (D-Chip) to the system through the NTMF29Bx cable . Ethernet activity LEDs The LEDs indicate 100BaseT , 10BaseT , and activity on both the ELAN and TLAN network interf aces.
Software deliv er y 55 Installation guidelines Use the f ollowing guidelines when installing the Media Card 32-por t trunk card: • Ensure CS 1000 Release 4.0 or later software is installed and r unning. • Ensure that the NTVQ01BB Media Card Fir mware is v ersion 8.
56 System description The Media Card 32-por t trunk card package is shipped with the f ollowing two major components, as w ell as other items: • Media Card 32-P or t Assembly (NTVQ01BB) • CompactF.
Replacing a CompactFlash PC Card (C:/ dr ive) 57 W ARNING Be sure to remov e the Media Card 32-por t tr unk card from the system before replacing the CFlash A T A card. Procedure 1 Removing the CFlash car d on NTVQ01BB Step Action 1 Gently pull the clip from its latched position.
58 System description 2 The metal clip should be pulled up and the new CFlash card should be kept in the right position (see Figure 13 "CFlash card with metal clip up" (page 58) ).
Software upgr ade 59 Software upgrade IP T runk 3.01 (and later) software upgr ades can be performed in three wa ys: • by FTP from TM 3.1 • by FTP from the CLI • from a PC Card The application (ex ec) file for the Media Card 32-por t trunk card contains a different CPU type definition from other IP tr unk card types.
60 System description "T ransmit card proper ties and dialing plan" (page 419) or in "T ransf er files through the Command Line Interface" (page 377) .
ISDN Signaling Link 61 If an upgrade from ITG T runk 2.xx, Release 19 or earlier , is projected to take se v eral days and f ax suppor t is needed dur ing this time, first upgrade the individual nodes to ITG T runk 2.xx Release 23. When the netw or k is upgraded to ITG T runk 2.
62 System description Figure 17 ITG configuration ISDN signaling between the Meridian 1 and IP T r unk 3.01 (and later) suppor ts the deliver y of Calling Line Identification (CLID) and f eature messaging. ISL DCH signaling provides the necessary signaling connection ov er which data, including CLID and feature-specific messaging, can be passed.
ISDN Signaling Link 63 because the NT AK02BB SDI/DCH card does not suppor t QSIG protocols f or ISL. The DCH interf ace uses these protocols and their variants, as they hav e the follo wing advantages: • ISL configuration suppor t • symmetr y (incoming and outgoing call messaging is the same) • near H.
64 System description F or fur ther inf or mation on ISDN Signaling Link (ISL), refer to System Management Ref erence (NN43001-600) , ISDN Pr imar y Rate Interface Installation and Commissioning (NN43001-301) , and ISDN Primar y Rate Interf ace Maintenance (NN43001-717) .
Dialing plans 65 Dialing plans Dialing plan configuration allows customers to set up routing tables to route calls to the appropr iate destination, based on dialed digits. The dialing plan is configured through the Electronic Switched Network (ESN) feature , using TM 3.
66 System description F or example, Meridian 1/CS 1000M switch B node B1 has two entr ies for NP A 408 and 4085, which point to nodes A1 and A2 of Mer idian 1/CS 1000M s witch A, respectively . Calls from B1 with dialed digits 408-5xx-xxxx are routed to the IP T r unk 3.
Dialing plans 67 Flexible Numbering Plan A Fle xible Numbering Plan (FNP) allows the length of Location Codes (LOCs) to vary from node to node. As well, the total number of digits dialed to reach a station can var y from station to station. It also allows fle xibility for the length of the location codes from node to node.
68 System description def ault in TM 3.1 remained unchanged at 32 ms, e ven though the ECAN perf or mance was significantly better with 128 ms. This prob lem has been resolved in TM 3.1, b ut ITG T r unk and IP T runk nodes defined by customers with the original TM 3.
Dialing plans 69 Provisioned in TM 3.1 (in ms) Value used by IP Trunk 3.01 96 96 128 (default value in IP Trunk 3.01) 128 (default value in IP Trunk 3.01) Speech Activity Detection Speech activity detection reduces the IP bandwidth used by typical voice con versations.
70 System description Callers can access traditional V oice Mail or IVR ser vices (f or example, "Press 1 f or more information" or "Press 2 to be connected to our customer ser vice depar tment"). Ser vices that depend on long DTMF bursts cannot be accessed.
Quality of Ser vice 71 • latency • queuing dela y in the inter mediate nodes • pack et loss • av ailable bandwidth The T ype of Service (T oS) bits in the IP pack et header can affect how efficiently data is routed through the netw or k. For fur ther inf or mation on T oS, see "T ype of Ser vice" (page 76) .
72 System description than five percent, can be acceptable without too much degradation in voice quality . Sporadic loss of small packets can be more acceptable than infrequent loss of large pack ets. P acket dela y P ack et delay is the time between when a pack et is sent and when it is received.
Quality of Ser vice 73 P acket InterNet Groper (PING) P ack et InterNet Groper (PING) sends an Internet Control Message Protocol (ICMP) echo request message to a host, e xpecting an ICMP echo reply . This allows the measurement of the round-trip time to a selected host.
74 System description MOS values are calculated based on the routing delay and frame duration and jitter buff er delay on the codec. These latencies must be taken into consideration during the engineering of the total network’s latency .
F allback to alternate facilities 75 The trigger for f allback to alter nate trunk facilities is defined per call, per customer . The local Active Leader makes the decision to use the f allback f eature. The selection of routes is based on the customer-configured database.
76 System description Fallbac k in IP T runk 3.01 (and later) In QoS monitoring, the local node queries the remote node and gets a response; the remote node quer ies the local node and gets a response . If the remote node cannot quer y the local node, QoS monitor ing is not av ailable .
T ype of Ser vice 77 The TM 3.1 User Interface allows two T oS values to be configured: data and control. Data pack ets transmit the voice or f ax call’s data, while control pack ets setup and maintain the call. Both can be configured for an y value in the range of 0 – 255 (0 is the def ault).
78 System description The IP tr unk card configures two route table entries f or the local subnet if a diff erent T oS is configured for the voice and control pack ets. Otherwise, a single entr y is created. CA UTION Service Interruption Only technical personnel with detailed knowledge of router capabilities should mak e changes to T oS.
Remote Access 79 Modules suppor ting f acsimile transmission are responsible f or the f ollowing: • f ax speed detection and adjustment • protocol con version from G3 F ax to R TP payload f or fax data tr ansfer • T .30 fax protocol suppor t • T .
80 System description Alternatively , the PC application, pcANYWHERE©, can be installed in host mode on the TM 3.1 PC to provide remote access to any PC with a modem. The remote user dials the TM 3.1 PC which contains the required IP T runk 3.01 (and later) data (whether stored locally or on an TM 3.
P er-call statistics suppor t using RADIUS Client 81 A RADIUS client on the IP tr unk card allows per-call statistics of the IP network call to be sent from the cards to a network listener . The client is based on RFC2139, which defines the accounting por tion of the RADIUS protocol.
82 System description • Codec used • Orig/T er m call side indication • Snapshot of remote Gatewa y’s QoS at time of call connect The calling and called numbers (with their corresponding IP addresses) are just that, regardless of which end is doing the originating.
SNMP MIB 83 SNMP MIB SNMP is the protocol used to comm unicate TM 3.1 IP T r unk 3.01 (and later) alarms or e vents. Suppor t f or the SNMP Management Inf or mation Bases (MIB) on the IP trunk card is composed of two par ts: the standard MIB-2 and e xtensions f or the IP tr unk card.
84 System description — release — establish • Retriev al of DSP inf ormation, such as: — DSP firmware — DSP self-test status — card reset • SNMP configuration (that is, community names.
Codec profiles 85 G.729AB The G.729AB codec is the default pref erred codec when adding a ne w IP T r unk 3.01 (and later) node in TM 3.1. This codec provides near toll-quality voice at a low dela y . The G.729AB codec uses compression at 8 kbit/s (8:1 compression rate).
86 System description W ARNING The Media Card 32-por t tr unk card does not suppor t Profile 3. Security passw ords When T elneting into the ELAN network interf ace or using the deb ug por t, a pass word must be entered when prompted. T wo lev els of passw ords are used to prev ent unauthor ized data access.
87 ITG engineering guidelines Contents This section contains information on the follo wing topics: "Introduction" (page 89) "Audience" (page 90) "Equipment requirements" (page 90) "Scope" (page 92) "Network engineering guidelines overview" (page 92) "IP Trunk 3.
88 ITG engineering guidelines "TCP traffic behavior" (page 127) "IP Trunk 3.01 (and later) DiffServ support for IP QoS" (page 128) "Queue management" (page 129) "Use of Frame Relay and ATM services" (page 129) "Internet Protocols and ports used by IP Trunk 3.
Introduction 89 "Multiple IP Trunk 3.01 (and later) nodes on the same ELAN and TLAN segments" (page 157) "General LAN considerations" (page 157) "ELAN and TLAN network interfa.
90 ITG engineering guidelines IP T runk 3.01 (and later) is targeted towards the Enter pr ise customer who has a Mer idian 1/CS 1000M system installed f or providing corporate voice ser vices and an intranet f or cor porate data ser vices. A customer is e xpected to use the IP T r unk 3.
Introduction 91 system must be deter mined. If the intranet becomes ov er loaded, new calls to the IP T runk 3.01 (and later) system f all back to normal circuit-switched voice f acilities so that the Quality of Ser vice (QoS) does not degrade f or new calls .
92 ITG engineering guidelines A maximum of 16 Media Card 32-por t trunk cards can fit on one IPE shelf . Each IP tr unk card takes up one slot on the IPE shelf . For Class B compliance to EMC regulations, only 10 Media Card 32-por t trunk cards can be placed on an IPE shelf.
Network engineering guidelines ov er view 93 voice into fix ed-length IP packets , provide ISDN signalling, and translate PSTN numbers into IP addresses. The IP pack ets are transpor ted across the IP data network with a low latency that varies with strict limits.
94 ITG engineering guidelines Figure 24 IP T runk 3.01 (and later) network engineering process Three preliminar y steps must be under tak en. 1. Calculate IP T runk 3.01 (and later) traffic. Estimate the amount of traffic that the system will route through the IP T r unk 3.
IP T runk 3.01 (and later) traffic engineer ing 95 on the cor porate intranet. This is descr ibed in "IP T runk 3.01 (and later) traffic engineering" (page 95) .
96 ITG engineering guidelines CCS/user=# of calls/ * A ver age Holding Time (in seconds)/100 T otal voice CCS (Tv) = CCS/user x No . of V oIP users The number of V oIP users (telephones) is the potential population in the system that can generate/receiv e traffic through the IP T runk 3.
IP T runk 3.01 (and later) traffic engineer ing 97 5 Calculate bandwidth output. Refer to T able 17 "Silence Suppression disabled TLAN Ethernet and W AN IP bandwidth usage per IP T runk 3.01 (and later) " (page 113) (Silence Suppression disabled).
98 ITG engineering guidelines Procedure 5 Calculating IP T runk 3.01 (and later) por t and bandwidth requirements Step Action 1 Calculate V oIP traffic during busy hour . CCS/user = 4*150/100 = 6 CCS Tv = 120*6 = 720 CCS 2 Calculate f ax on IP traffic dur ing busy hour .
IP T runk 3.01 (and later) traffic engineer ing 99 This e xample is based on the G.729AB codec with 30 ms payload siz e and Silence Suppression enabled. For relations of user-selectable parameters such as payload size , codec type, pack et size and QoS, ref er to "Set QoS e xpectations" (page 139) .
100 ITG engineering guidelines Trunks CCS Trunks CCS Trunks CCS Trunks CCS Trunks CCS 18 346 38 905 58 1504 78 2122 98 2752 19 373 39 935 59 1534 79 2153 99 2784 20 399 40 964 60 1565 80 2184 100 2816.
IP T runk 3.01 (and later) traffic engineer ing 101 Trunks CCS Trunks CCS Trunks CCS Trunks CCS Trunks CCS 17 431 34 964 51 1515 68 2076 85 2644 86 2678 99 3116 112 3552 125 3992 138 4434 87 2711 100.
102 ITG engineering guidelines suppor ting the other half of the Follo wers. This rule covers D-Channel redundancy with two IP T runk 3.01 (and later) routes per node. 3. Leader 0 with DCHIP but no voice por ts configured suppor ting Leader 1 and all Follo wers.
IP T runk 3.01 (and later) traffic engineer ing 103 (and later) TLAN subnet. IP T runk 3.01 (and later) registers and re-registers with a Gatekeeper . Unless the Time T o Live (TTL) value is e xtremely low (under 15 seconds), the TTL has a ver y minor eff ect on the Leader card.
104 ITG engineering guidelines Factor s that effect the real-time capacity The f ollowing f actors affect real-time capacity: • host module type • the number of por ts configured on the Leader card, codec selection, and voice sample size • size of the IP T runk 3.
F actors that eff ect the real-time capacity 105 In a default QoS configuration, the Leader card must terminate and generate a total of 50 probe pack ets per QoS-enabled ITG T runk 2.
106 ITG engineering guidelines In this section, the f ollowing assumptions are made to project the Leader Card real-time capacity: • The number of probe pack ets per Leader Card is 25. • If the av erage hold time is 180 seconds, the number of calls per hour per por t is 15.
F actors that eff ect the real-time capacity 107 Nor tel recommends that traffic on a single card ITG-P entium 24-por t trunk card node ne ver e xceed the f ollowing: • 5000 calls/hour – Gatek ee.
108 ITG engineering guidelines Ta b l e 1 2 Real-time capacity of a single card node with all 24 ports enabled Calls/hr CCS AHT Maximum number of nodes monitoring QoS Comment 490 882 180s 96 Normal tr.
F actors that eff ect the real-time capacity 109 Ser vice) divided b y the number of channels per card. The number of F ollower cards required is affected b y whether the Leader card has the voice channels enab led or not. 2. P eakedness f actor for call processing is equal to 1.
110 ITG engineering guidelines A node has only one Leader card; howe v er , more then one DCHIP card can be provisioned. If a DCHIP card f ails, all IP tr unk cards with channels that use that D-channel are out of ser vice; the remaining IP trunk card channels, though, do remain in ser vice.
F actors that eff ect the real-time capacity 111 Ta b l e 1 5 Real-time capacity of a Media Card 32-por t trunk card in the Leader role Number of QoS nodes in network Calls/hr supporte d Voice ports e.
112 ITG engineering guidelines T o calculate the bandwidth requirement of a route, divide the total route traffic b y 36 CCS and multiply by the bandwidth use . All traffic data must be based on the busy hour of the b usy da y . T o calculate resource requirements (IP T r unk 3.
F actors that eff ect the real-time capacity 113 Ta b l e 1 7 Silence Suppression disabled TLAN Ethernet and W AN IP bandwidth usa g e per IP T runk 3.
114 ITG engineering guidelines Silence Suppression engineering considerations Silence Suppression/V oice Activity Detection (V AD) results in av erage bandwidth savings o ver time, not in instantaneous bandwidth savings . F or nor mal conv ersations, Silence Suppression creates a 40% sa vings in av erage bandwidth used.
F actors that eff ect the real-time capacity 115 F ax traffic is alwa ys one-wa y . F ax pages sent and f ax pages received generate data traffic to the TLAN subnet. F or W AN calculation, only the larger traffic parcel of the two must be considered.
116 ITG engineering guidelines the two tromboned IP T r unks. There are three cases of direct media path connection between two tromboned IP T r unks (trunk channels) when interoperating with BCM and IP P eer : • Both IP T runks are on the same Media Card 32-por t trunk card running IP T runk 3.
F actors that eff ect the real-time capacity 117 T A T call Scenario The f ollowing call scenario helps to understand T A T . 1. Site 1 and Site 2 both hav e an IP T runk 3.01 (or later) node installed. IP T runk 3.01 (and later) is used for trunking between the tw o sites.
118 ITG engineering guidelines T A T versus TR O Nor tel recommends that both T runk Route Optimization (TRO) and T A T be implemented with IP T r unk 3.01 (and later) nodes. TRO functions in a diff erent manner than T A T . TRO is in vok ed before the call has been ans wered.
F actors that eff ect the real-time capacity 119 T able 18 "Example: T raffic flow in a 4-node IP T r unk 3.01 (and later) network" (page 119) summar izes traffic flo w of a 4-node IP T runk 3.01 (and later) network. Ta b l e 1 8 Example: T raffic flow in a 4-node IP T runk 3.
120 ITG engineering guidelines T able 20 "Example: Incremental W AN bandwidth requirement" (page 120) summarizes the W AN traffic in kbit/s for each route. The recommended incremental bandwidth requirement is included in the column adjusted f or 30% traffic peaking in busy hour .
Assess W AN link resources 121 where 14 CCS is the larger of two f ax traffic parcels (14 CCS as compared to 6 CCS). After adjusting for peaking, the incremental data rate on W AN f or this route is 33.
122 ITG engineering guidelines The third step is to assess ho w much spare capacity is a vailab le. Enterpr ise intranets are subject to capacity planning policies that ensure capacity use remains below some deter mined utilization lev el.
Assess W AN link resources 123 Figure 25 Calculate network load with IP T runk 3.01 (and later) traffic Suppose the intranet has a topology as shown in Figure 25 "Calculate network load with IP T runk 3.01 (and later) traffic" (page 123) and a prediction on the amount of traffic on a specific link, R4-R5, is required.
124 ITG engineering guidelines r6 (10.8.0.1) 1 ms 1 ms 1 ms r5 (10.18.0.2) 42 ms 44 ms 38 ms r4 (10.28.0.3) 78 ms 70 ms 81 ms r1 (10.3.0.1) 92 ms 90 ms 101 ms santa_clara_itg4 (10.3.2.7) 94 ms 97 ms 95 ms The T raceroute progr am can be used to check if routing in the intranet is symmetric for each source-destination pair .
Assess W AN link resources 125 Enough capacity F or each link, T able 23 "Computation of link capacity as compared to ITG load" (page 125) compares the av ailable link capacity to the additional IP T r unk 3.
126 ITG engineering guidelines Insufficient link capacity If there is not enough link capacity , implement one or more of the f ollowing options: • Use the G.723 codec ser ies. Compared to the def ault G.729AB codec with 30 ms pa yload, the G.723 codecs use 9% to 14% less bandwidth.
Implement QoS in IP networks 127 Unless voice traffic has been configured to hav e higher prior ity , the data file download could use most of the av ailable bandwidth.
128 ITG engineering guidelines and ebb in traffic flows . W AN links appear to be congested at one per iod of time time and then are f ollowed b y a period of under-utilization. There are two consequences, as f ollows: • W AN link inefficiency • IP T r unk 3.
Implement QoS in IP networks 129 Queue management Queueing delay F rom "Queuing dela y" (page 133) , it can be seen that queueing delay is a major contributor to dela y , especially on highly-utilized and low-bandwidth W AN links.
130 ITG engineering guidelines Internet Protocols and por ts used by IP T runk 3.01 (and later) The follo wing IP applications and protocols are used by IP T r unk 3.01 (and later) and must be transmitted across the customer’s intranet by all IP routers and other network equipment.
Implement QoS in IP networks 131 P or t numbers used by IP T runk 3.01 (and later) T able 25 "Pre-defined TCP por ts" (page 131) and T able 26 "Pre-defined UDP por ts" (page 131) list the pre-defined por ts used by IP T r unk 3.
132 ITG engineering guidelines • limiting the maximum frame size and fragmenting large frames on low-speed W AN links • limiting the quantity of voice tr affic that is transmitted ov er low-speed W AN links Fine-tune network QoS T opics presented in this section deal with issues that impact the QoS of IP T r unk 3.
Implement QoS in IP networks 133 Serialization delay Serialization delay is the time it takes to tr ansmit the voice pac ket one bit at a time ov er a W AN link.
134 ITG engineering guidelines Figure 26 Queuing delay of v arious links As can be seen in Figure 26 "Queuing delay of various links" (page 134) , queueing dela ys can be significant for links with bandwidth under 512 kbit/s. Higher speed links can tolerate much higher utilization le vels.
Implement QoS in IP networks 135 Other delay components Other dela y components, generally considered minor , are as follo ws. • Router processing dela y The time it tak es to forw ard a pack et from one link to another on the router is the transit or router processing dela y .
136 ITG engineering guidelines The a verage r tt time on that link is about 40 ms; the one-wa y link dela y is about 20 ms, of which the circuit transmission and ser ialization delay are just a f e w milliseconds. Most of this link’s dela y is caused b y queueing.
Implement QoS in IP networks 137 • Overloaded CPU . This is another commonly-monitored statistic collected by network management systems. If a router is ov er loaded, it means that the router is constantly perf or ming processing-intensive tasks, which impedes the router from f orwarding pack ets.
138 ITG engineering guidelines Time-of-Day v oice routing Other impor tant objectives associated with IP T r unk 3.01 (and later) network translations and route list bloc ks are as follo ws: 1. Make IP T runk 3.01 (and later) the first-choice, least-cost entr y in the Route List Block.
Measure intranet QoS 139 Use the ESN TGAR, NCOS, and facility restriction lev els to keep general modem traffic off the IP T runk 3.01 (and later) route. Measure intranet QoS End-to-end dela y and error char acter istics of the current state of the intranet can be measured.
140 ITG engineering guidelines In the context of a Meridian 1/CS 1000M system with IP T r unk 3.01 (and later), Figure 27 "Relationship between users and ser vices" (page 140) shows the relationship between users and ser vices.
Measure intranet QoS 141 The QoS lev el is a user-or iented QoS metr ic which takes on one of these f our settings: excellent, good, f air , and poor , indicating the quality of v oice ser vice.
142 ITG engineering guidelines Figure 28 QoS levels with G.729A/AB codec Figure 29 QoS level with G.711 codec Nor tel Communication Ser v er 1000 IP T r unk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nor tel Networks .
Measure intranet QoS 143 Figure 30 QoS level with G.723 codec Obtain QoS measurement tools PING and T raceroute are standard IP tools that are usually included with a network host’s TCP/IP stac k.
144 ITG engineering guidelines time=94ms 68 bytes from (10.3.2.7): icmp_seq=0 ttl=225 time=112ms 68 bytes from (10.3.2.7): icmp_seq=0 ttl=225 time=97ms ^? --- Richardson3 PING Statistics --- 8 packets transmitted, 8 packets received, 0% packet loss round-trip (ms) min/avg/max = 94/96/112 The time field displa ys the round trip time ( rt t ).
Measure intranet QoS 145 Measure end-to-end packet loss The PING program also repor ts if the ICMP pack et made its round tr ip correctly or not. Use the same PING host setup to measure end-to-end error .
146 ITG engineering guidelines Network dela y and packet loss ev aluation example F rom PING data, calculate the av erage one-wa y delay (halved from PING output and adding 93 ms IP T runk 3.01 (and later) processing dela y) and standard de viation for latency .
Measure intranet QoS 147 In contrast, the site pair Santa Clara/Ottawa has both QoS le vels of mean and mean+standard deviation f alling in the excellent region.
148 ITG engineering guidelines This model already takes into account some characteristics of the IP Phone, and theref ore the impair ment factors are not identical to those shown in the ITU-T standards. Ref er to T able 32 "R value translation" (page 149) f or the translation of R values into user satisf action le vels.
Measure intranet QoS 149 Ta b l e 3 2 R value translation R Value (lower limit) MOS User Satisfaction 90 4.5 Very satisfied 80 4.0 Satisfied 70 3.5 Some users dissatisfied 60 3.0 Many users dissatisfied 50 2.5 Nearly all users dissatisfied 01 Not recommended Use T able 33 "IP T runk 3.
150 ITG engineering guidelines QoS level Network delay (ms) Packet loss (%) G.711 20 G.729A/AB 30 G.723.1 (6.3 Kbps) 30 199 1 fair poor good 199 2 fair poor fair 199 4 poor not recommended not recomme.
Measure intranet QoS 151 • 0.5% pack et loss: lp = 2 Then: R=9 4-0 -0-2 R=9 2 Using T able 33 "IP T runk 3.01 (and later) QoS le vels" (page 149) , a value of 92 means the users are ver y satisfied. Scenario 2 A campus network has the f ollowing characteristics: • G.
152 ITG engineering guidelines • 0.5% pack et loss: lp = 8 Then: R = 94 - 11 - 5 - 8 R=7 0 Using T able 33 "IP T runk 3.01 (and later) QoS le vels" (page 149) , a value of 70 means some users are dissatisfied. Does the intranet meet expected IP T runk 3.
IP T runk 3.01 (and later) LAN installation and configuration 153 Figure 31 Basic setup of the IP T runk 3.01 (and later) system IP trunk card connections 10/100BaseT Ethernet por ts The Media Card 32-por t and ITG-P entium 24-por t trunk cards each hav e two Ethernet por ts.
154 ITG engineering guidelines The Media Card 32-por t and ITG-P entium 24-por t trunk cards have tw o Ethernet por ts per card, so the IP T runk 3.01 (and later) system can suppor t two diff erent TLAN and ELAN subnet connections.
IP T runk 3.01 (and later) LAN installation and configuration 155 TLAN Node IP 10.0.0.56 TLAN Card IP 10.0.0.57 TLAN GW 10.0.0.1 TLAN Subnet Mask 255.255.255.0. The ELAN subnet range of addresses – 10.0.0.129 to 10.0.0.160 – o verlaps the TLAN subnet range of addresses – 10.
156 ITG engineering guidelines Private IP ad dresses Private IP addresses are inter nal IP addresses that are not routed over the internet. They can be routed directly between separate intranets, provided that there are no duplicated subnets in the private IP addresses.
IP T runk 3.01 (and later) LAN installation and configuration 157 Multiple IP T runk 3.01 (and later) nodes on the same ELAN and TLAN segments There are sev eral configurations where it is acceptable to put multiple IP T runk 3.
158 ITG engineering guidelines TLAN subnet design The IP T runk 3.01 (and later) nodes must connect to the intranet to minimize the number of router hops betw een the systems if there is adequate bandwidth on the W AN links for the shor ter route. This reduces the fixed and variab le IP pack et dela y , and improv es the voice QoS .
IP T runk 3.01 (and later) LAN installation and configuration 159 Priority routing f or v oice packets Routers having the capability to tur n on pr iority f or voice pac kets should hav e this feature enabled to improv e QoS performance.
160 ITG engineering guidelines W ARNING Configure the por ts on Lay er 2 or Lay er 3 switching equipment as auto-negotiate . If one side is manually configured, and the other side is configured as auto-negotiate, the follo wing situation occurs.
IP T runk 3.01 (and later) DSP profile settings 161 • Alwa ys keep the TLAN UTP cabling to less than 50 meters for the ITG-P entium 24-por t tr unk card. • As an inter im measure, connect to each ITG-P entium 24-por t trunk card and log in to the ITG> shell.
162 ITG engineering guidelines • Profile 3: G.711, G.729B, F ax The Media Card 32-por t trunk card does not suppor t Profile 3. The DSP coding algorithm parameter sets the pref erred codec of each IP trunk card. The recommendation is to use Profile 1, and to set the pref erred codec to G.
IP T runk 3.01 (and later) DSP profile settings 163 2. V oice pla yout maximum dela y . 3. F ax play out nominal delay . This can range from 0 to 300 ms, with 100 ms as the default size .
164 ITG engineering guidelines When a system equipped with an IP T runk 3.01 (and later) node ser v es as a tandem s witch in a network where some circuit-s witched tr unk facilities ha ve an e xcessively low audio le vel, Silence Suppression, if enabled, degrades the quality of ser vice by causing choppiness of speech.
P ost-installation network measurements 165 e xpectations and networking technology – can render a design obsolete or non-compliant with QoS objectives.
166 ITG engineering guidelines In subsequent design cycles, re view and refine the QoS objective, based on data collected from intranet QoS monitoring. Having decided on a set of QoS objectives, then deter mine the planning threshold. The planning thresholds are based on the QoS objectives.
P ost-installation network measurements 167 SNMP network management Simple Network Management Protocol (SNMP)-based Network Management Systems (NMS) provide a useful wa y of monitoring a real-time network from end to end. This is impor tant for networks using V oIP .
168 ITG engineering guidelines — number of cards and por ts, IP T runk 3.01 (and later) node and card parameters — f allback threshold le vel — Codec image — v oice and fax pa yload — v oice.
169 TM 3.1 management and configuration of IP T runk 3.01 (and later) Contents This section contains information on the follo wing topics: "Introduction" (page 169) "TM 3.1 ITG Engineering rules" (page 169) "TM 3.1 network setup guidelines" (page 170) "TM 3.
170 TM 3.1 management and configuration of IP T runk 3.01 (and later) 2. In theor y , a single TM 3.1 installation can suppor t up to 500 system’s. Howe ver , TM 3.1 applications requir ing real-time, such as T raffic Analysis retrie val of tr affic data, are limited to a m uch smaller number of systems.
TM 3.1 remote access configuration 171 Figure 32 Remote access with full access to customer LAN/W AN A single remote suppor t and administration TM 3.1 PC can administer a local node through the ITG Management LAN or can administer a remote node through the W AN.
172 TM 3.1 management and configuration of IP T runk 3.01 (and later) Figure 33 Remote access with no access to customer LAN/W AN In this case, a local TM 3.1 PC on an IP T r unk 3.01 (and later) ELAN subnet has access to only the IP trunk cards on the local node.
TM 3.1 PC hardware and software requirements 173 A single network dr ive location is chosen during the TM 3.1 client PC installation process. For multi-system configurations where large data store re.
174 TM 3.1 management and configuration of IP T runk 3.01 (and later) • printer por t (required for the dongle) • dongle (f or ser ver or stand-alone only) • Windows-compatib le mouse (PS/2 mouse preferred to free up a PC serial por t) CA UTION Service Interruption Do not install TM 3.
TM 3.1 PC hardware and software requirements 175 TM 3.1 application Program store Data store Maintenance Windows 1 MB Negligible Alarm Management with Alarm Notification 1.5 MB Negligible Nor tel Communication Ser v er 1000 IP T r unk Fundamentals NN43001-563 02.
176 TM 3.1 management and configuration of IP T runk 3.01 (and later) Nor tel Communication Ser v er 1000 IP T r unk Fundamentals NN43001-563 02.01 Standard Release 5.
177 Install and configure IP T runk 3.01 (and later) node Contents This section contains information on the follo wing topics: "Introduction" (page 179) "Before you begin" (page 180) "Installation procedure summary" (page 180) "ESN installation summary" (page 182) "Create the IP Trunk 3.
178 Install and configure IP T runk 3.01 (and later) node "Install filter and NTND26 cable (for MSDL and DCHIP cards in different Large System equipment rows)" (page 202) "Small System.
Introduction 179 "Configure Network Connections" (page 239) "Configure card properties" (page 240) "Configure DSP profiles for the IP Trunk 3.
180 Install and configure IP T runk 3.01 (and later) node Before y ou begin F ollow the steps in Procedure 6 "Meeting installation requirements" (page 180) to ensure that installation requirements are met. Procedure 6 Meeting installation requirements Step Action 1 Install TM 3.
Installation procedure summar y 181 Ta b l e 3 7 Installation procedures Step Procedure See page 1 "Create the IP Trunk 3.01 (and later) Installation Summary Sheet" (page 183) . 2 "Install and cable IP Trunk 3.01 (and later) cards" (page 190) .
182 Install and configure IP T runk 3.01 (and later) node Step Procedure See page "Exit node property configuration session" (page 252) . "Create the IP Trunk 3.01 (and later) node dialing plan using TM 3.1" (page 253) . "Retrieve the IP Trunk 3.
Create the IP T runk 3.01 (and later) Installation Summary Sheet 183 • In LD 86, provision the RLB (Route List Block) RLI (Route List Inde x) bloc ks. — Add the RLI entries. Do not skip entries, as ESN searches the tab le from entr y zero until the full initial set of entries are scanned to find an av ailable route .
184 Install and configure IP T runk 3.01 (and later) node address address address Leader 0 Leader 1 Follower Follower Follower Follower Follower Follower Follower Follower Follower Follower Follower .
Channel Identifier planning 185 Ta b l e 3 9 Mapping of unit number to ISL Channel number one card in system Unit number (from TN) ISL Channel number 01 12 23 34 4 5 5 6 6 7 7 8 89 91 0 10 11 11 12 1.
186 Install and configure IP T runk 3.01 (and later) node Ta b l e 4 0 Mapping of unit number to ISL Channel number , one card in system Unit number (from TN) ISL Channel number 01 12 23 34 4 5 5 6 6.
Channel Identifier planning 187 T wo car ds, sequential numbering, gap left for expansion This e xample is for two ITG-P entium 24-por t trunk cards. T o allow room f or replacement by a Media Card 32-por t trunk card at a later date, a gap of eight channels has been left between the cards.
188 Install and configure IP T runk 3.01 (and later) node Unit number (from TN) ISL Channel number 18 19 19 20 20 21 21 22 22 23 23 24 Card 2 Card 2 ISL channel numbering starts at 33 (24 numbers from Card 1 + 8 numbers for expansion + first number for Card 2 = 24 + 8+ 1 = 33).
Channel Identifier planning 189 Incorrect ISL channel numbering plans This section describes numbering plan errors. Gaps in ISL channel numbering sequence T able 42 "Channel numbering error , gap on one card" (page 189) shows gaps in the ISL numbering plan sequence.
190 Install and configure IP T runk 3.01 (and later) node Overlapping channel number s Do not provision the ISL channel n umbers on both cards with the same channel numbers . For e xample, do not configure Channel 10 on both cards. The Meridian 1/CS 1000M rejects this numbering plan but the IP trunk card does not.
Install and cab le IP T runk 3.01 (and later) cards 191 The ITG-P entium 24-por t tr unk card requires 24-pair tip and r ing I/O cabling. NT8D37AA IPE modules ha ve 24-pair tip and ring I/O cab ling for card slots 0, 4, 8, and 12 only . Inser t the left slot of the IP tr unk card in NT8D37AA slots 0, 4, 8 or 12 only .
192 Install and configure IP T runk 3.01 (and later) node 2 Remov e any e xisting I/O panel cables associated with an y card pre viously installed in the selected card slot. 3 Install the NTWE07AA DCHIP PC Card into the inter nal PC Card slot on the IP trunk card that has been selected to provide the DCHIP function.
Install NTCW84J A Large System I/O Panel 50-Pin filter adapter 193 When the IP trunk cards are installed, the red LED on the faceplate is lit if: the card has rebooted; the card is activ e, but there are no trunks configured on it; or the card is active and has trunks, but the trunks are disabled.
194 Install and configure IP T runk 3.01 (and later) node Remove e xisting I/O panel filter adapter The standard I/O filter adapter is shielded metal with a blac k plastic inser t connector . The NTCW84JA adapter uses yellow warning labels to indicate EMC filtering modifications and which MDF connection points can suppor t 100BaseT connection.
Install NTMF94EA and NTCW84KA cables 195 Figure 35 NTCW84JA 50 pin I/O Panel Filter Connector Block Even though the ITG-P entium 24-por t tr unk card is a two-slot card, only the leftmost slot is counted for the card slot n umber . Example: for an ITG-P entium 24-por t trunk card installed in slots 2 and 3, the slot number is 2.
196 Install and configure IP T runk 3.01 (and later) node Install the NTCW84KA cable (for DCHIP cards) F ollow the steps in Procedure 9 "Installing the NTCW84KA cable" (page 196) to connect the NTCW84KA cable f or DCHIP cards.
Install NTMF94EA and NTCW84KA cables 197 Figure 36 NTCW84KA ELAN, TLAN, DCH, and serial cable Install the NTMF94EA cable (for non-DCHIP cards) F ollow the steps in Procedure 10 "Installing the NTMF94EA cable" (page 197) to install the NTMF94EA cable f or non-DCHIP cards.
198 Install and configure IP T runk 3.01 (and later) node order to tie the shield of the LAN cab le to the frame ground f or EMC compliance. Figure 37 NTMF94EA ELAN, TLAN and serial por t cable —End— Install shielded TLAN network interface cable Use Shielded CA T5 cable to connect to the ELAN and TLAN network interf aces on the NTCW84KA cable.
Configure NT6D80 MSDL switches 199 When connecting the Media Card 32-por t trunk card and/or ITG-P entium 24-por t trunk card to the TLAN subnet, the link status LED on the card f aceplate associated with the TLAN network interface lights green when the connection is made.
200 Install and configure IP T runk 3.01 (and later) node Ta b l e 4 4 NT6D80 MSDL settings for ITG-Pentium 24-por t trunk card DCHIP Port 0 – SW4 Port 0 – SW8 RS-422-A DTE all off all on Port 1 .
Install filter and NTND26 cable (f or MSDL and DCHIP cards in same Large System equipment row) 201 • NTND26AB – 18 ft • NTND26A C – 35 ft • NTND26AD – 50 ft 4 Connect the appropriate NTND.
202 Install and configure IP T runk 3.01 (and later) node Figure 39 NTND26 cable r outing diagram 5 Connect the DCH (P5) connector of the NTCW84KA to the outward side of the 15-pin I/O panel filter connector .
Install filter and NTND26 cab le (for MSDL and DCHIP cards in diff erent Large System equipment rows) 203 2 Install the 15-pin I/O panel filter connector on the inward side of the brac ket.
204 Install and configure IP T runk 3.01 (and later) node Ta b l e 4 5 NT AK02 SDI/DCH switch settings f or IP T runk 3.01 (and later) DCHIP Port 1 SW 1-1 SW 1-2 DCH OFF OFF Port 3 SW 1-3 SW 1-4 DCH OFF OFF Ta b l e 4 6 NT AK02 SDI/DCH jumper settings for the IP T runk 3.
Cabling f or the Media Card 32-por t trunk card 205 Procedure 14 Installing the serial cable Step Action 1 T o make a temporary connection to the IP T r unk 3.01 (and later) maintenance por t from a local RS-232 TTY ter minal or a modem, use the NT A G81CA PC Maintenance cable.
206 Install and configure IP T runk 3.01 (and later) node The ELAN network interface suppor ts 10BaseT operation. The TLAN network interf ace suppor ts 10/100BaseT operation. T o suppor t the 100BaseT operation on Large Systems, the TLAN network interf ace requires specialized I/O panel mounting connectors.
Cabling f or the Media Card 32-por t trunk card 207 Figure 40 EMC kit deployment ITG Card ELAN/TLAN Adapter (L-adapter) The L-adapter routes the signals to the f ollowing network interf aces: • ELAN • TLAN • one RS-232 por t On Large Systems, the NT8D81AA cab le is used to br ing all 24 Tip & Ring pairs to the I/O panel.
208 Install and configure IP T runk 3.01 (and later) node Figure 41 ITG card ELAN/TLAN adapter (L-adapter) Figure 42 "ITG card ELAN/TLAN adapter (Large system)" (page 209) shows the adapter installed in a Large System with a secur ing screw and tie wrap.
Cabling f or the Media Card 32-por t trunk card 209 Figure 42 ITG card ELAN/TLAN adapter (Large system) T o install the L-adapter in a Small System, use a securing screw and retaining brac ket. See Figure 43 "ITG card ELAN/TLAN adapter fitted to a Meridian 1 Option 11C Cabinet/ CS 1000M Cabinet" (page 210) .
210 Install and configure IP T runk 3.01 (and later) node Figure 43 ITG card ELAN/TLAN adapter fitted to a Meridian 1 Option 11C Cabinet/ CS 1000M Cabinet T o install an adapter in a Mer idian 1 PBX 11C Chassis / CS 1000M Chassis, use a securing scre w and hook&loop tape.
Cabling f or the Media Card 32-por t trunk card 211 Figure 44 ITG car d ELAN/TLAN adapter fitted to a Meridian 1 PBX 11C Chassis/CS 1000M Chassis When Media Card 32-por t trunk cards are used to replace ITG-P entium 24-por t tr unk cards, the e xisting NTMF94EA or NTCW84KA cabling can be used.
212 Install and configure IP T runk 3.01 (and later) node • 8 data bits • 1 stop bit, no par ity • no flow control NTMF29B A DCHIP cable The NTMF29BA DCHIP cab le connects to por t 0 of the DCHIP PC Card and the MSDL/SDI DCHIP cab le. P or t 1 on the DCHIP PC Card is not used.
Cabling f or the Media Card 32-por t trunk card 213 2 Fit the screw through the secondary side of the Media Card 32-por t trunk card into the threaded hole in the brack et and tighten. 3 Fit the DCHIP PC Card NTMF29BA cable assemb ly through the f aceplate slot and push it home into the header .
214 Install and configure IP T runk 3.01 (and later) node Figure 46 Large System DCHIP cabling setup: intra-column/cube NTMF04B A MSDL extension cab le The NTMF04BA cable connects the NTND26AA MSDL c.
Cabling f or the Media Card 32-por t trunk card 215 Figure 47 Large system DCHIP cabling setup: inter-column When the Universal Equipment Modules (UEM) are stack ed ver tically , or the UEM columns are bolted together , they are cabled in an inter-column configuration.
216 Install and configure IP T runk 3.01 (and later) node Figure 48 Option 11C DCHIP system cabling NTWE04A C/AD SDI/DCH Meridian 1 Option 11C Cabinet/CS 1000M Cabinet e xtension cable The NTWE04A C and the NTWE04AD are 10-ft and 1-ft DCHIP extension cables , respectively .
Cabling f or the Media Card 32-por t trunk card 217 Install ITG EMC shielding kit NTVQ83 with Small and Large System types. Ref er to "ELAN and TLAN network interfaces" (page 205) f or additional inf or mation on the cabling requirements.
218 Install and configure IP T runk 3.01 (and later) node Figure 49 Wiring specifications —End— Configure IP T runk 3.01 (and later) data First, configure D-channels, Route Data Blocks , and tr unks through the system TTY . Then configure the ESN data bloc ks to implement the network dialing plan and translations.
Configure IP T r unk 3.01 (and later) data 219 Prompt Response Description GRP x Network Group number, where: x=0–4 DNUM x Device Number for I/O ports, where: x=0–1 5 PORT x Port number for MSDL card, where: x=0–3 DES IP TRUNK 16 character designator is "IP TRUNK" Specific description if more than one IP Trunk 3.
220 Install and configure IP T runk 3.01 (and later) node Prompt Response Description SIDE (USR) MSDL acts as User side of ISL. The IP Trunk 3.01 (and later) DCHIP card acts as the Network side of ISL. RLS 25 Release ID of PBX at the far end of the D-Channel.
Configure IP T r unk 3.01 (and later) data 221 Prompt Response Description SIDE (USR) Meridian 1 Option 11C Cabinet/CS 1000M Cabinet SDI/DCH card acts as User side of ISL. The DCHIP card acts as the Network side of ISL. RLS 25 Release ID of PBX at the far end of the D-Channel.
222 Install and configure IP T runk 3.01 (and later) node Prompt Response Description ... USR ISLD User IFC SL1 Interface type for D-channel ISLM 382 Maximum number of Integrated Service Signaling Links ... SIDE USR Meridian 1/CS 1000M node type The IFC response entr y must hav e the protocol entered in TM 3.
Configure IP T r unk 3.01 (and later) data 223 Prompt Response Description - PNI (0) – 32700 Private Network Identifier. Configure the PNI to 1 or other non-zero value to support Meridian Customer .
224 Install and configure IP T runk 3.01 (and later) node Prompt Response Description TKTP Trunk type. TIE The trunk type for IP Trunk 3.01 (and later) trunks must be set to TIE. SAT (NO) YES Satellite control (SAT) must be set to NO to enable Trunk Optimization before answer (TRO) and Trunk Anti-Tromboning (TAT).
Configure IP T r unk 3.01 (and later) data 225 Prompt Response Description NCNA (YES) NO Network Calling Name allowed. NCRD (NO) YES Network Call Redirection allowed. CTYP Call type for outgoing call dialed with the route access code (ACOD). Set to appropriate call type for IP Trunk 3.
226 Install and configure IP T runk 3.01 (and later) node Ta b l e 4 8 LD 16 NEW/CHG/OUT Prompt Response Description req new/chg/out type rdb Route Data Block. cust 0-99 tktp TIE Trunk Type. M911P (NO)/YES M911 Trunk Type for MCDN Network. M911_ABAN (NO)/YES Optional call abandon treatment: YES = abandoned call treatment for route.
Configure IP T r unk 3.01 (and later) data 227 ABTR (15) Range 0-30 Timer (in minutes) blocks the disconnect from being tandemed across to the target node. Default value: 15 minutes. This timer value can be added in increments of 1 minute. VTRK (NO)YES YES = supports IP Peer facilities.
228 Install and configure IP T runk 3.01 (and later) node Prompt Response Description cu Format for Small System and Media Gateway 1000B where c = card and u = unit DES 16 character descriptive designator for the IP trunk card. See Note 1 hhhh:hh:hh:hh:hh For unit 0.
Configure IP T r unk 3.01 (and later) data 229 Prompt Response Description For nodes containing a mixture of 24-port and 32-port IP trunk cards, determine the starting CHID by adding the number of channels (ports) on the previous card to the CHID of the previous card.
230 Install and configure IP T runk 3.01 (and later) node interf ace MAC address; for e xample: 00:60:38:01:06:C6. T o find the ELAN network interf ace MAC address, ref er to the IP T runk 3.
Configure dialing plans within the cor porate network 231 The time schedule is a 24-hour cloc k which is divided up the same wa y f or all 7 days . Basic steps to progr am Time of Day f or IP T runk 3.01 (and later) routes are as follo ws: 1. Go to LD 86 ESN data bloc k to configure the Time of Da y Schedule (T ODS) f or the required IP T runk 3.
232 Install and configure IP T runk 3.01 (and later) node If ESN5 is provisioned f or an IP T runk 3.01 (or later) node (both in the RDB and on the node cards), y ou must configure that node as "SL1 ESN5" in the dialing plan f or all other ITG 2.
Configure dialing plans within the cor porate network 233 Use the traditional PSTN for general modem traffic General modem traffic (f or example , V .36, V .90) cannot be suppor ted on ITG. The Mer idian 1/CS 1000M routing controls must be configured to route modem traffic o ver circuit-s witched trunks instead of over IP T runk 3.
234 Install and configure IP T runk 3.01 (and later) node LD 86 Configure Route List Bloc k with Step Back on Congestion on ISDN Prompt Response Description REQ NEW Add new data. CUST xx Customer number as defined in LD 15. FEAT RLB Route List Data Block.
Configure dialing plans within the cor porate network 235 Prompt Response Description TYPE DSC TSC Distant Steering Code. Trunk Steering Code. ... RLB xx Route List Entry created in LD 86. LD 90 Configure dialing plan Prompt Response Description REQ NEW Add new data.
236 Install and configure IP T runk 3.01 (and later) node The IP tr unk cards must be enabled later after the card proper ties and optionally , the IP T runk 3.01 (and later) software, has been transmitted from TM 3.1 to the IP trunk cards. Configure IP T runk 3.
Configure IP T runk 3.01 (and later) data in TM 3.1 237 Add an IP T runk 3.01 (and later) node and configure general node properties F ollow the steps in Procedure 17 "Adding a node and configur ing general node proper ties" (page 237) to add an IP T r unk 3.
238 Install and configure IP T runk 3.01 (and later) node Figure 51 General tab Configure node location properties 5 Define the Node Location proper ties: select the TM 3.1 site , TM 3.1 system , Customer , and Node number from the drop-down lists.
Configure IP T runk 3.01 (and later) data in TM 3.1 239 F or traffic reasons , use separate subnets f or nodes consisting of multiple ITG-P entium 24-por t trunk cards and Media Card 32-por t trunk cards.
240 Install and configure IP T runk 3.01 (and later) node a. Enter the ELAN node IP address in the Management LAN Node IP field. b . Enter the ELAN network interface gate wa y IP address in the Management LAN gateway IP address field. The ELAN network interface gatew ay (router) also functions as the voice gatew ay (router).
Configure IP T runk 3.01 (and later) data in TM 3.1 241 When adding the first card, select the card role Leader 0 . When adding the second card, select the card type Leader 1 . When adding additional cards, select the card type Follower . Configure the DCHIP and D-Channel information.
242 Install and configure IP T runk 3.01 (and later) node Each F ollower card can optionally hav e its TLAN network interface IP address and TLAN network interf ace gatewa y IP address on a diff erent TLAN subnet than Leader 0 and Leader 1. 4 If Use separate subnets in the General tab was unchec ked ear lier , perf or m steps a and b: a.
Configure IP T runk 3.01 (and later) data in TM 3.1 243 The choices are SL1, SL1 ESN5, ESIG and ISIG for netw orks consisting of Large Systems. F or networks that include Small Systems, the choices are SL1 or SL1 ESN5. In addition to IP T runk 3.01 (and later) nodes, the IP telephony trunk network might also contain ITG T runk 1.
244 Install and configure IP T runk 3.01 (and later) node Configure DSP profiles for the IP T runk 3.01 (and later) node F ollow the steps in Procedure 20 "Configuring DSP profiles for the IP T runk 3.
Configure IP T runk 3.01 (and later) data in TM 3.1 245 3 Click the Pr ofile Options tab. See Figure 54 "DSP Profile Profile Options tab" (page 245) . This tab displays the def ault General and F AX options values according to the selected DSP profile.
246 Install and configure IP T runk 3.01 (and later) node Figure 55 DSP Profile Codec Options tab 6 P erform steps 7 and 8 if required. T o re ver t to the def ault settings, click Reset Defaults . CA UTION The default Codec Options are appropriate for most applications.
Configure IP T runk 3.01 (and later) data in TM 3.1 247 Change default DiffServ/T oS value for Contr ol and V oice F ollow the steps in Procedure 21 "Changing the def ault DiffSer v Codepoint (DSCP) value f or Control and V oice" (page 247) to change the default DiffSer v/T oS value f or Control and V oice.
248 Install and configure IP T runk 3.01 (and later) node Subnet mask = 255.255.255.0 Subnet = 23.11.42.0 IP T runk card TLAN IP = 23.11.42.121 Subnet mask = 255.255.255.0 Subnet = 23.11.42.0 23.11.42.0 = 23.11.42.0. Theref ore, the SNMP traps will be sent to the TLAN router .
Configure IP T runk 3.01 (and later) data in TM 3.1 249 2 Check the Enable SNMP traps chec k box to enab le sending of SNMP traps to the SNMP trap destinations that appear in the list. Enter at least one SNMP trap destination IP address if this option is check ed.
250 Install and configure IP T runk 3.01 (and later) node The IP trunk card uses the addresses in the routing table entries to route signaling pack ets over the ELAN network interf ace gatew ay (router) on the ELAN subnet. Without routing table entries, the IP trunk card routes signaling traffic ov er the TLAN network interface gatew ay .
Control node access with SNMP community name str ings 251 Figure 57 Accounting Server tab 2 Click the Enab le Radius accounting records chec kbox. 3 Enter the Radius accounting ser v er IP address.
252 Install and configure IP T runk 3.01 (and later) node The community name strings are configured on the Security tab . These are not pick ed up from the System Proper ties – General tab . Figure 58 ITG Node Properties Security T ab Change the current System Mgmt Read and System Mgmt Read/Write community name strings as per the Card.
Control node access with SNMP community name str ings 253 Create the IP T runk 3.01 (and later) node dialing plan using TM 3.1 F ollow the steps in Procedure 24 "Configure the ITG Dialing Plan General tab" (page 253) to configure the IP T r unk 3.
254 Install and configure IP T runk 3.01 (and later) node Figure 59 ITG Dialing Plan Remote Node Properties window General tab 3 Select the destination Node to be added from the list. TM 3.1 provides the IP T runk 3.01 (and later) Node IP address in a gre yed-out bo x and fills in the node name in the Node Name field.
Control node access with SNMP community name str ings 255 In addition to IP T r unk 3.01 (and later) nodes, the IP telephony trunk network may contain ITG T r unk 1.0 Basic T runk nodes or Nor tel IP T elephony Connection Manager . Use H.323 V2 node capability f or these nodes.
256 Install and configure IP T runk 3.01 (and later) node 3 Enter the Called Number digits for the ESN translation type in the Dial plan digits field. See #2 in Figure 60 "ITG Dialing Plan Remote Node Proper ties window Digits dialed tab" (page 257) .
Control node access with SNMP community name str ings 257 Figure 60 ITG Dialing Plan Remote Node Properties window Digits dialed tab The digit manipulation defined in the Digits dialed tab of the ITG.
258 Install and configure IP T runk 3.01 (and later) node 6 Click Appl y . 7 Repeat steps 7 through 11 until all the ESN translation Dial Plan digits f or this destination node have been added. 8 Click OK . The Dialing Plan window appears with the added dialing plan entries.
Control node access with SNMP community name str ings 259 4 Click the Configuration tab . Record the Management IP address of Leader 0 on the new node. 5 On the Configuration tab , change the Management IP address of Leader 0 on the new node . Enter the Management IP address of the Leader 0 card on the existing node recorded in Step 2.
260 Install and configure IP T runk 3.01 (and later) node T ransmit IP trunk car d configuration data from TM 3.1 to the IP trunk cards IP T r unk 3.01 (and later) nodes and IP trunk cards are configured in the TM 3.1 ITG ISDN IP T runk application and then transmitted to the IP trunk cards.
T ransmit IP trunk card configuration data from TM 3.1 to the IP tr unk cards 261 NT AG81BA Maintenance Extender cab le to provide an e xtension between the NT AG81CA PC Maintenance cab le and the TM 3.
262 Install and configure IP T runk 3.01 (and later) node • "yyy .yyy .yyy .yyy" is the ELAN network interf ace gatewa y (router) IP address on the ELAN subnet. If the TM 3.1 PC is connected locally to the LAN and there is no ELAN gatew ay , then the gatew ay IP address is "0.
T ransmit IP trunk card configuration data from TM 3.1 to the IP tr unk cards 263 Procedure 28 Installing a Backup Leader in IP T runk 3.01 (and later) Step Action 1 Ensure both IP trunk cards are running the same version of software . The software v ersion is display ed when logging into the IP trunk cards.
264 Install and configure IP T runk 3.01 (and later) node the IP tr unk card from the system interf ace, see "System commands LD 32" (page 384) . 8 F rom TM 3.1, transmit the NODE PROPER TY , CARD PROPER TY , and Dialing Plan to the activ e leader and to all disab led IP trunk cards.
T ransmit IP trunk card configuration data from TM 3.1 to the IP tr unk cards 265 Disable IP trunk cards whene ver tr ansmitting card proper ties or new software. Use the TM 3.1 Maintenance Windo ws, the TM 3.1 System P assthr u terminal, or a system management ter minal directly connected to a TTY por t.
266 Install and configure IP T runk 3.01 (and later) node V erify installation and configuration T o verify installation and configuration, check the IP trunk card faceplate displa ys. After successfully rebooting, the Leader 0 card is now fully configured with the Node Proper ties of the node and enters a state of "Active Leader".
T ransmit IP trunk card configuration data from TM 3.1 to the IP tr unk cards 267 Figure 61 IP trunk card status If the (a) IP T runk 3.01 (and later) Node is being installed from an TM 3.
268 Install and configure IP T runk 3.01 (and later) node 2 V erify that the TN, ELAN network interface MA C addresses, and IP addresses are configured correctly f or each IP trunk card. Select any card in the IP T runk 3.01 (and later) node in the TM 3.
Configure date and time for the IP T runk 3.01 (and later) node 269 5 Click the Start transmit button. 6 Monitor progress in the T ransmit Control window . Confir m that the Card Proper ties and Dialing Plan are transmitted successfully to all the IP tr unk cards, which are identified by TNs.
270 Install and configure IP T runk 3.01 (and later) node 4 Set the correct date and time. 5 Click OK . The clock is updated immediately on the Active Leader card (Leader 0 or Leader 1), which in turn updates the other cards in the IP T runk 3.01 (and later) node.
Change default ESN5 prefix for non-ESN5 IP telephony gate ways 271 Enter new pass word again to confir m: new pass word 5 Record the new user name and pass word and transmit to authorized network security personnel. 6 Repeat procedure for all cards in the node.
272 Install and configure IP T runk 3.01 (and later) node Figure 62 esn5PrefixShow 4 At the ITG prompt, enter >esn5PrefixSet "1xx" where xx = the NCOS value . In Figure 63 "esn5PrefixSet" (page 272) , the def ault value was changed from NCOS 00 to 03.
Check and download IP trunk card software in TM 3.1 273 3 Click the Configuration tab and record S/W version, Car d density and Card TN f or each card in the new node .
274 Install and configure IP T runk 3.01 (and later) node • F or ITG-P entium 24-por t trunk cards, download the Software P ackage for Release IP T runk 3.01 (and later) . 8 When prompted, select Download . Record the file name and location of downloaded software on the TM 3.
Check and download IP trunk card software in TM 3.1 275 • If a mix of Media Card 32-por t and ITG-P entium 24-por t trunk cards is in the same IP T runk 3.01 (and later) node, then select all cards of the same density in the lower half of the window .
276 Install and configure IP T runk 3.01 (and later) node 6 Reboot each IP tr unk card that received tr ansmitted software, so that the new softw are can be applied. Star t the rebooting with Leader 0, then Leader 1, and finally the follo wer cards.
Configure TM 3.1 Alarm Management to receive SNMP tr aps from the IP trunk cards 277 VxW or ks login: itgadmin P ass word: itgadmin ITG> 4 Disable the ITG-P entium 24-por t or Media Card 32-por t trunk card in LD 32 (DISI lsc). W ait f or the NPRxx message.
278 Install and configure IP T runk 3.01 (and later) node Procedure 38 Configuring TM 3.1 ALarm Management to receive SNMP traps from the IP trunk cards Step Action 1 In the TM 3.1 Navigator window select Utilities > Alarm Notification . The TM 3.
Configure TM 3.1 Alarm Management to receive SNMP tr aps from the IP trunk cards 279 Figure 66 Devices.txt file: 6 F or each IP trunk card in each monitored IP T r unk 3.01 (and later) node, add a line consisting of three fields separated by spaces .
280 Install and configure IP T runk 3.01 (and later) node TM 3.1 Alar m Notification must be restar ted whenev er Control Files are changed. 9 If TM 3.1 Alar m Notification is r unning (a red traffic light is showing on the tool bar), stop it by clic king on the red traffic light on the tool bar .
281 Pr o visioning IP T runk 3.01 (and later) in TM 3.1 Contents This section contains information on the follo wing topics: "Overview" (page 281) "Add a site and system" (page 282.
282 Provisioning IP T runk 3.01 (and later) in TM 3.1 F or detailed information on configur ing a system in TM 3.1, see T elephony Manager 3.1 System Administration (NN43050-601) . Add a site and system Bef ore the IP T runk 3.01 (and later) application can be used, a site, a system, and at least one node must be configured.
Add a site and system 283 2 Click Sites to highlight it. 3 On the menu bar , click Configuration > Add Site . See Figure 68 "Add a Site" (page 283) . Figure 68 Add a Site An empty New Site Properties window opens. 4 The site is a single entity , usually in one location.
284 Provisioning IP T runk 3.01 (and later) in TM 3.1 Figure 69 New Site Properties Pro visioning a new site 5 Click OK to sa ve the site inf or mation. The TM 3.1 Navigator window opens again, with the new site added. —End— F or more information on how to add a site, see T elephony Manager 3.
Add a site and system 285 3 Right-click the site and from the drop-do wn list, select Properties . See Figure 70 "Change System Proper ties" (page 285) . Figure 70 Change System Properties Alternatively , from the upper menu, click File > Properties .
286 Provisioning IP T runk 3.01 (and later) in TM 3.1 The Site Properties window opens. See Figure 72 "TM 3.1 Site Proper ties ready to change" (page 286) . Figure 72 TM 3.1 Site Properties ready to change 4 Enter the information that is being changed.
Add a site and system 287 Figure 73 Deleting a site Alternatively , from the upper menu, click Edit > Delete . W ARNING Deleting a site also deletes all of its systems. See Figure 74 "Alter native method of deleting a site" (page 288) . Nor tel Communication Ser v er 1000 IP T r unk Fundamentals NN43001-563 02.
288 Provisioning IP T runk 3.01 (and later) in TM 3.1 Figure 74 Alternative method of deleting a site 4 In the war ning bo x that opens, click Ye s to confir m the deletion. See Figure 75 "Confir m deletion" (page 288) . Figure 75 Confirm deletion Nor tel Communication Ser v er 1000 IP T r unk Fundamentals NN43001-563 02.
Add a site and system 289 —End— Add a system Though the site has been added, no s witches or nodes hav e been defined. A PBX, also called a system, must be added. F or IP T runk 3.01 (and later), the system usually corresponds to a single PBX. Procedure 42 Adding a system Step Action 1 There are two w ays to add a ne w system in the TM 3.
290 Provisioning IP T runk 3.01 (and later) in TM 3.1 Figure 77 New system menu bar 2 The system selections that apply to IP T runk 3.01 (and later) are: • Meridian 1 The IP tr unk cards are provisi.
Add a site and system 291 Figure 78 Select a system type The New System Properties window opens. This window enables system-wide values to be provisioned. 3 Click the General tab . An empty New System Properties window opens. See Figure 79 "Empty New System Proper ties window" (page 291) .
292 Provisioning IP T runk 3.01 (and later) in TM 3.1 is entered automatically . See Figure 80 "New system proper ties General tab" (page 292) . 5 If the system and site are not in the same location, enter the system location and ser vice personnel contact information.
Add a site and system 293 Figure 81 System Data tab Pro vision the system customer information 7 Click the Customer s tab . An empty Customers window appears . See Figure 82 "Empty Customers window" (page 294) . An IP trunk card cannot be provisioned unless it belongs to a system customer .
294 Provisioning IP T runk 3.01 (and later) in TM 3.1 Figure 82 Empty Customers window 8 Click the Ad d button to add a customer . The Add Customer window opens. See Figure 83 "Add Customer window" (page 295) . Nor tel Communication Ser v er 1000 IP T r unk Fundamentals NN43001-563 02.
Add a site and system 295 Figure 83 Add Customer window 9 Use the Customer Number drop-down (pull-down) list to select the customer number . Click OK . The New – (Customer x) Properties window opens. See Figure 84 "New (Customer x) Proper ties General tab" (page 296) .
296 Provisioning IP T runk 3.01 (and later) in TM 3.1 Figure 84 New (Customer x) Properties General tab 10 Enter the Director y Numbers and HLOC obtained from the system provisioning. The Features tab and the Numbering Plans tab are related to system provisioning.
Add a site and system 297 The window displa ys two sections – Ser vices and Sites. See Figure 67 "TM 3.1 Navigator" (page 282) . 2 In the Site where the system is located, clic k the system to be changed. 3 Right-click the system and from the drop-down list, select Properties .
298 Provisioning IP T runk 3.01 (and later) in TM 3.1 Figure 86 System Pr oper ties Customers tab 7 Click Pr oper ties . Edit the customer’s information in the Customer Properties window – General, F eatures, and Number ing Plans tabs. See Figure 87 "Customer Proper ties window" (page 298) .
Add a site and system 299 8 Click OK to sa ve the customer inf or mation. 9 Click OK to sa ve the system inf or mation. —End— Delete a system F ollow the steps in Procedure 44 "Deleting a system" (page 299) to delete a system. Procedure 44 Deleting a system Step Action 1 Log in to the TM 3.
300 Provisioning IP T runk 3.01 (and later) in TM 3.1 Figure 89 Alternative method of deleting a system 4 In the war ning bo x that opens, click Ye s to confir m the deletion.
Add an IP T runk 3.01 (and later) node 301 Add an IP T runk 3.01 (and later) node F ollow the steps in Procedure 45 "Adding an IP T runk 3.01 (and later) node" (page 301) to add an IP T runk 3.01 (and later) node. Procedure 45 Adding an IP T runk 3.
302 Provisioning IP T runk 3.01 (and later) in TM 3.1 Figure 92 ITG ISDN IP T runk window 3 F rom the IP T elephony Gatewa y – ISDN IP T runk window menu bar , select Configuration > Node > Add . The Add ITG Node dialog bo x shown in Figure 93 "Add ITG Node dialog bo x" (page 302) opens.
Add an IP T runk 3.01 (and later) node 303 Figure 94 New ITG node General tab 7 On the General tab , on the left side of the windo w , define the f ollowing from the drop-down lists: • The TM 3.1 site – the name that was assigned when the site was created.
304 Provisioning IP T runk 3.01 (and later) in TM 3.1 Figure 95 New ITG Node - Configuration tab A minimum of one IP tr unk card, Leader 0, must be defined. This card acts as the leader card on star tup and remains as leader until it suff ers some sor t of failure that would require changeo ver to the Backup Leader card.
Add an IP T runk 3.01 (and later) node 305 • V oice LAN gate wa y IP – the lowest IP address on the TLAN subnet • Card TN – the first three numbers (loop/shelf/card). The e xception is the Mer idian 1 Option 11C Cabinet and CS 1000M Cabinet which is only "card".
306 Provisioning IP T runk 3.01 (and later) in TM 3.1 Figure 96 New ITG Node Configuration tab window with Leader 0 pro visioned In the window , where the sa ved card data is displa yed, the column width can be increased or decreased to see more or less information.
Add an IP T runk 3.01 (and later) node 307 Figure 97 New ITG Node, DSP Profile tab, General sub-tab Profile 1 13 Select the applicable DSP Profile inf or mation. There are three choices in the DSP Profile drop-down list, as seen in Figure 97 "New ITG Node, DSP Profile tab , General sub-tab Profile 1" (page 307) .
308 Provisioning IP T runk 3.01 (and later) in TM 3.1 Figure 98 DSP Profile sub-tabs ,Profile 1 Options sub-tab TM 3.1 does not permit "V .25 F ax/Modem tone detection enab led" for IP T r unk 3.01 (and later) and ITG T r unk 2.x. This is because the IP trunk cards do not hav e a mechanism for properly handling modem calls.
Add an IP T runk 3.01 (and later) node 309 Figure 99 New ITG Node, DSP Profile tab, Codec sub-tab W ARNING Do not tur n off G.711, unless there is no other alter native. Some IP devices use G.723 and G.711, some devices use G.729 and G.711, and some devices support all three codecs.
310 Provisioning IP T runk 3.01 (and later) in TM 3.1 17 Click the Po r t s tab . See Figure 100 "Ne w ITG Node P or ts tab" (page 310) . Figure 100 New ITG Node Ports tab 18 This tab is only present f or IP T runk 3.01 (and later) nodes. Use the drop-down list to select the R TP por t star ting v alue.
Add an IP T runk 3.01 (and later) node 311 19 Click OK to complete the node provisioning. The ITG Node Properties window closes. The node data is now displa yed in the ITG – ISDN IP T runk window . See Figure 101 "ITG, ISDN IP T runk window with new node displa yed" (page 311) .
312 Provisioning IP T runk 3.01 (and later) in TM 3.1 Figure 102 Change node properties 4 Alternatively , right-click the node to be edited, the select Properties from the pop-up menu. See Figure 103 "Alter native method of selecting node to be edited" (page 312) .
Add an IP T runk 3.01 (and later) node 313 Figure 104 ITG Node Properties General tab 6 T o 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 bef ore Follo wer cards.
314 Provisioning IP T runk 3.01 (and later) in TM 3.1 7 Enter the required data. Note that, compared to the Leader 0 configuration • the Management (ELAN network interf ace) IP address, the V oice .
Add an IP T runk 3.01 (and later) node 315 Figure 107 Editing an IP trunk card in a node 9 T o delete an IP trunk card from the node, select the desired card and click Delete .
316 Provisioning IP T runk 3.01 (and later) in TM 3.1 If the IP tr unk card can be deleted, the pr int on the Delete button is in black. See Figure 109 "Delete an IP tr unk card from a node" (page 316) . Figure 109 Delete an IP trunk card from a node Leader 0 and Leader 1 cannot be deleted if there is still a Follo wer card in the node.
Add an IP T runk 3.01 (and later) node 317 Figure 110 Delete a node 2 Alternatively , r ight-click the node to be deleted, and from the pop-up menu, clic k Delete .
318 Provisioning IP T runk 3.01 (and later) in TM 3.1 Figure 112 Confirm the node deletion If Ye s is selected, the node is deleted. See Figure 113 "The node is deleted" (page 318) . Figure 113 The node is deleted —End— Define the dialing plan information IP T runk 3.
Define the dialing plan information 319 F ollow the steps in Procedure 48 "Defining the local Dialing plan" (page 322) to define the local dialing plan. Non-Gatekeeper-resolved (local) dialing plan The local dialing plan consists of a number of V oIP destination nodes , such as IP T r unk 3.
320 Provisioning IP T runk 3.01 (and later) in TM 3.1 The QoS f eature only works if the far end is an IP T runk 3.01 (and later) or an ITG T runk 2.x node. Additionally , there must be a fallbac k route for the IP T r unk 3.01 (and later) node to use to reach the f ar end, such as a PRI trunk.
Define the dialing plan information 321 5. DSC – Distance Steering Code, par t 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 b y the end user as par t of one system.
322 Provisioning IP T runk 3.01 (and later) in TM 3.1 NPI TON Dialing plan Private Unknown SPN DSC TSC LOC Unknown Unknown SPN DSC TSC LOC Procedure 48 Defining the local Dialing plan Step Action 1 F rom the IP T elephony Gatewa y – ISDN IP T runk window (see Figure 114 "Access the Dialing Plan window" (page 322) ), select a node.
Define the dialing plan information 323 Figure 115 ITG Dialing Plan window 2 T o add a new remote node , click Configuration > Add Remote Node. A remote node is an entr y in the dialing plan tab le that represents a de vice to be reached by pro visioning on the IP trunk card.
324 Provisioning IP T runk 3.01 (and later) in TM 3.1 Figure 116 ITG Dialing Plan, Remote Node Properties window, General tab Figure 117 ITG Dialing Plan, Remote Node Properties window , General tab with drop-down list open Nor tel Communication Ser v er 1000 IP T r unk Fundamentals NN43001-563 02.
Define the dialing plan information 325 An existing destination node can also hav e its proper ties changed from the drop-down list. See Figure 118 "Change proper ties on an e xisting destination node" (page 325) . In that e xample, the proper ties are being changed f or the Johnny Carson node.
326 Provisioning IP T runk 3.01 (and later) in TM 3.1 Figure 119 Selected Remote Node 5 Set the QoS parameter , if desired. Ensure that F allback to the PBX is in place if QoS lev els are not maintained. W ARNING If a remote node has IP P eer H.323 Gatew ay capability , do not use QoS monitoring unless that node is also running IP T runk 3.
Define the dialing plan information 327 Figure 120 Remote Node Properties, Digits dialed tab with no entries Figure 121 Select the destination node Nor tel Communication Ser v er 1000 IP T r unk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nor tel Networks .
328 Provisioning IP T runk 3.01 (and later) in TM 3.1 Figure 122 Remote Node Properties, Digits dialed tab with a selected destination node In the e xample seen in Figure 122 "Remote Node Proper ties, Digits dialed tab with a selected destination node" (page 328) , the dialing plan digits to be added are 613-961-xxxx.
Define the dialing plan information 329 Figure 123 Changing the destination node information Destination not in local TM 3.1 pro visioning 9 Select Not Defined on this PC from the Node drop-down list on the ITG Dialing Plan – Remote Node Proper ties – General tab .
330 Provisioning IP T runk 3.01 (and later) in TM 3.1 Figure 124 Destination not in local TM 3.1 pro visioning Figure 125 Selecting an IP Peer H.323 Gatewa y Nor tel Communication Ser v er 1000 IP T r unk Fundamentals NN43001-563 02.01 Standard Release 5.
Define the dialing plan information 331 10 Enter the node IP address, select the node capability from the drop-down list, enter a name for the node (optional), set the QoS monitoring option, and enter comments if desired. W ARNING If a remote node has IP P eer H.
332 Provisioning IP T runk 3.01 (and later) in TM 3.1 Figure 127 Select the Dial Plan 14 Enter all of the numbers that must reach this node. 15 Enter all necessar y data. The data includes the digits dialed, the number of digits to delete from the front, and the digit string to inser t on the front.
Define the dialing plan information 333 Figure 128 Node with two remote sites Complex dialing plans There is no limit to the number of digit patter ns that can ter minate on a node.
334 Provisioning IP T runk 3.01 (and later) in TM 3.1 Figure 129 Example of a complex dialing plan Gatekeeper-resolved endpoints The IP T runk 3.01 (and later) application has two methods of resolving addresses. The IP T runk 3.01 (and later) node first checks the dialing plan inf or mation using the Address T ranslation Protocol Module (A TPM).
Define the dialing plan information 335 In the TM 3.1 Navigator window , the Gatekeeper z one can be found b y left-clicking on the CS 1000M system, selecting Properties, and clicking on the Network tab . See Figure 130 "Making a Gatekeeper zone" (page 335) .
336 Provisioning IP T runk 3.01 (and later) in TM 3.1 • In the ITG – ISDN IP T runk window , as seen in Figure 92 "ITG ISDN IP T runk window" (page 302) , from the menu select Configuration > Node > Gatekeeper . The ITG Node Gatekeeper properties window opens.
Define the dialing plan information 337 Use Gatekeeper Zone from TM 3.1 Navigator option If "Use Gatekeeper zone from TM 3.1 Navigator" was selected from the Gatekeeper Option drop-down list, f ollow the steps in Procedure 50 "Using a Gatekeeper zone from TM 3.
338 Provisioning IP T runk 3.01 (and later) in TM 3.1 Figure 132 Node Properties Gatekeeper from TM 3.1 3 Click Appl y . —End— Use Independent Gatekeeper option If "Use Independent Gatekeeper.
Define the dialing plan information 339 Figure 133 Gatekeeper T ype drop-down list Figure 134 "Proper ties defined for Primar y Gatekeeper" (page 339) shows an e xample of an independent Gatek eeper that has been provisioned.
340 Provisioning IP T runk 3.01 (and later) in TM 3.1 W ARNING The H.323 endpoint ID is case-sensitiv e and alphanumeric string content-sensitive. The data entered in the H.323 ID field must be an e xact match to what is provisioned on the Gatekeeper or calls to the Gatek eeper-controlled destinations fail.
Define the dialing plan information 341 —End— F rom the ITG Dialing Plan window , confir m that all required remote end-points hav e been provisioned. Download the dialing plan provisioning to the IP tr unk cards. For more inf or mation on downloading the dialing plan, see "T ransmit configuration data" (page 350) .
342 Provisioning IP T runk 3.01 (and later) in TM 3.1 Nor tel Communication Ser v er 1000 IP T r unk Fundamentals NN43001-563 02.01 Standard Release 5.
343 TM 3.1 O A and M using TM 3.1 applications Contents This section contains information on the follo wing topics: "Introduction" (page 344) "TM 3.
344 TM 3.1 OA and M using TM 3.1 applications "System commands LD 32" (page 362) "Disable the indicated IP trunk card" (page 363) "Disable the indicated IP trunk card when idl.
TM 3.1 OA and M procedure summar y 345 Delete a node T o delete an IP T runk 3.01 (and later) node, perf or m the follo wing steps in Procedure 52 "Deleting an IP T runk 3.01 (and later) node" (page 345) . Procedure 52 Deleting an IP T runk 3.
346 TM 3.1 OA and M using TM 3.1 applications 3 The ITG Node Properties window appears. 4 Select the Card Configuration tab . 5 Select the IP trunk card to delete from the list. 6 Click the Delete b utton. 7 Click OK . —End— Database locking All node and card proper ties are stored in a single TM 3.
TM 3.1 OA and M procedure summar y 347 ITG Card Pr oper ties window T o display the proper ty sheet of an IP tr unk card, double-clic k an IP trunk card in the ITG Main window . The proper ty 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.
348 TM 3.1 OA and M using TM 3.1 applications • Use the Set Node Time to change the time and date on the node. The node time is updated e ver y minute while the Card Proper ties is open. • Use the Open log file , Open trace file , and the Open OM file buttons to vie w the related files.
TM 3.1 OA and M procedure summar y 349 ITG Card Pr oper ties Configuration window The Configuration window for the IP trunk card contains the inf or mation shown in Figure 139 "ITG Card Proper ties Configuration tab" (page 349) . The ITG Card Proper ties Configuration window provides read-only inf or mation.
350 TM 3.1 OA and M using TM 3.1 applications D-channel maintenance If the IP trunk card has D-channel hardware, the tree on the left side of the window contains the D-channel. click the D-channel and the D-channel Maintenance window appears. This window allo ws D-channel maintenance operations to be performed.
TM 3.1 OA and M procedure summar y 351 3 Click Start transmit . See Figure 140 "ITG T ransmit Options window" (page 351) . —End— TM 3.1 transf ers the data to the appropriate cards using FTP . Figure 140 ITG T ransmit Options window The f ollowing comments apply to the ITG T ransmit Options: • T o transmit Node Proper ties (BOO TP .
352 TM 3.1 OA and M using TM 3.1 applications • F or the Card Proper ties (CONFIG1.INI) to tak e effect, the IP trunk cards must be re-enab led. • T o transmit the Dialing Plan (DPT ABLE.1), select the node in the top window or select each individual card below .
Add an IP T runk 3.01 (and later) node on TM 3.1 by retrieving an e xisting node 353 Add an IP T runk 3.01 (and later) node on TM 3.1 b y retrieving an existing node After an IP T runk 3.01 (and later) node is manually configured and installed, that node can be added to another TM 3.
354 TM 3.1 OA and M using TM 3.1 applications 2 In the IP T elephony Gatewa y - ISDN IP T runk window , select the drop-down list Configuration > Node > Add . The ADD ITG Node dialog bo x appears. 3 Click the second option Retrieve the active configuration from an existing node .
Retriev e and add an IP T r unk 3.01 (and later) node for maintenance and diagnostic purposes 355 The Retrie ve control dialog bo x displa ys the results of the retrie val. The node proper ties, card proper ties and dialing plan are retr ie ved from the Leader card.
356 TM 3.1 OA and M using TM 3.1 applications Add the dummy node manually or b y retrieving the IP T runk 3.01 (and later) node configuration data from an existing IP T runk 3.01 (and later) node. The site name, Meridian 1 system name, and Mer idian 1 customer number must e xist in the TM 3.
Retriev e and add an IP T r unk 3.01 (and later) node for maintenance and diagnostic purposes 357 Retrieve IP T runk 3.01 (and later) configuration information from the IP T runk 3.0 (and later) node Use the optional Procedure 58 "Retr ie ving the IP T runk 3.
358 TM 3.1 OA and M using TM 3.1 applications 5 Select Prompt user f or community name if required. 6 Click the Start retrieve button. —End— Monitor the status of the retr ie val in the Retrieve control bo x. The retr ie ved Node Properties , Card Pr oper ties , and Dialing Plan over-writes the e xisting TM 3.
Retriev e and add an IP T r unk 3.01 (and later) node for maintenance and diagnostic purposes 359 Figure 144 Generate OM Repor t b . T o generate a repor t immediately , click Generate OM Repor t . TM 3.1 prepares the repor t and displays the inf or mation in a .
360 TM 3.1 OA and M using TM 3.1 applications —End— Additional administrative functions In addition to the administrativ e functions perf or med in MA T Navigator , there are other functions perfo.
Additional administrativ e functions 361 Figure 146 MA T user template Backup and restore operations The Media Card 32-por t and ITG-P entium 24-por t tr unk cards suppor t backup and restore procedures for critical configuration data.
362 TM 3.1 OA and M using TM 3.1 applications F or more information about Alar m Notification, please ref er to Alar m Management in T elephony Manager 3.
System commands LD 32 363 Ta b l e 5 2 LD 32 IP T runk 3.01 (and later) maintenance commands Command Description DISC l s c Disable the indicated card, where: l = loop, s = shelf, c = card DISI l s c .
364 TM 3.1 OA and M using TM 3.1 applications DISI l s c Disable the indicated IP trunk card when idle, where: l = loop, s = shelf, c = card Enable an indicated IP trunk card T o enable an indicated I.
System commands LD 32 365 STAT l s c u Display the status of the indicated ITG port, where: l = loop, s = shelf, c = card, u = unit. Nor tel Communication Ser v er 1000 IP T r unk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nor tel Networks .
366 TM 3.1 OA and M using TM 3.1 applications Nor tel Communication Ser v er 1000 IP T r unk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nor tel Networks .
367 O A and M using the ITG shell CLI and o verla ys Contents This section contains information on the follo wing topics: "Introduction" (page 368) "ITG Shell OA and M procedure summary.
368 OA and M using the ITG shell CLI and o verlays "Disable an indicated IP trunk card port" (page 364) "Enable an indicated IP trunk card" (page 364) "Enable an indicated IP .
Access the ITG shell through a maintenance por t or T elnet 369 • Access the ITG shell from the TM 3.1 PC . Ref er to "T elnet to an IP trunk card through the TM 3.
370 OA and M using the ITG shell CLI and o verlays —End— Only one person can use the ITG shell at a time. Any session, local or T elnet, can be overridden by a second session. The second user receives a war ning bef ore the login and must confir m to complete the login.
Access the ITG shell through a maintenance por t or T elnet 371 Figure 147 Select card and open T elnet session 4 P erform the follo wing action to increase the T elnet terminal buff er size to capture m ultiple screens of data from the IP tr unk card: F rom the T elnet "T er minal" menu, select "Preferences".
372 OA and M using the ITG shell CLI and o verlays Procedure 62 Changing the default ITG shell passwor d Step Action 1 F rom the ITG shell use the command shellPasswordSet to change the def ault user name and passw ord for T elnet to ITG shell and FTP to the IP tr unk card file system.
Access the ITG shell through a maintenance por t or T elnet 373 Example of the Media Card 32-por t trunk card prompt screen: Example of the ITG-Pentium 24-port trunk card pr ompt screen: If the prompt " vxWorks login: " appears, the BIOS ROM prompt has been lost and the card must be reset again.
374 OA and M using the ITG shell CLI and o verlays When prompted to login, enter the default username and passw ord as: VxW or ks login: itgadmin P ass word: itgadmin ITG> 6 If this card is Leader 0, use the setLeader command: ITG> setLeader xxx.
Access the ITG shell through a maintenance por t or T elnet 375 Reset the operational measurements This command resets all operational measurement (OM) par ameters collected after the last log dump .
376 OA and M using the ITG shell CLI and o verlays Card Mode: Normal Codecs: G.711 mu-law (default), G.711 a-law, G.729AB, G.729A EC Tail Length: Value from TM 3.
Access the ITG shell through a maintenance por t or T elnet 377 The time to re-register is based on the clock on the Leader 0 IP tr unk card. If the clocks on the Leader 1 and F ollower IP trunk cards are out of synchronization with the Leader 0 clock, the time to re-register might be incorrect.
378 OA and M using the ITG shell CLI and o verlays F or security reasons, there is no generic FTP client on the IP trunk card. A DIR or PWD (Print W or king Director y) command cannot be perf or med on the FTP host.
Access the ITG shell through a maintenance por t or T elnet 379 Configuration file transfer Use these commands to backup and restore files when the pref erred method, the TM 3.
380 OA and M using the ITG shell CLI and o verlays Obtain the ne w IP tr unk card software from the Nor tel web site, or obtain a PC Card containing the newest softw are. F ollow the steps in Procedure 64 "Downloading IP trunk card software from the inter net" (page 380) to download the IP tr unk card software from the Nor tel web site.
Access the ITG shell through a maintenance por t or T elnet 381 3 Use the swDownload command to cop y the software from the PC Card to the IP trunk card flash ROM de vice, using the FTP client and the FTP host on the IP trunk card. The host name parameter in this command is the ELAN network interf ace IP address of the IP trunk card.
382 OA and M using the ITG shell CLI and o verlays 3 Press Enter . Monitor the status of the software upgrade and chec k that the upgrade correctly finishes. Obser ve any error messages that indicate problems with parameters or syntax. 4 When the new softw are has downloaded into the flash ROM de vice, reboot the IP tr unk card to use it.
Access the ITG shell through a maintenance por t or T elnet 383 —End— Restore from the CLI T o restore configuration when the TM 3.1 PC is not av ailable to retransmit the IP T r unk 3.01 (and later) configuration data, use the appropriate "Put" commands.
384 OA and M using the ITG shell CLI and o verlays The SNMP community names can be read from the IP trunk card in two wa ys: • Reset the IP trunk card and monitor the star tup messages. Use the configFilePut command to bac kup the Card Proper ties file to an FTP host.
System commands LD 32 385 The card reset b utton is only a vailab le in the TM 3.1 IP T runk 3.01 (and later) application when the IP tr unk card is disabled. Disabling the IP tr unk card in LD 32 does not disable the Activ e Leader or Backup Leader functions .
386 OA and M using the ITG shell CLI and o verlays Command Function ENLC l s c Enable the described IP trunk card, where: l = loop, s = shelf, c = card ENLU l s c u Enable the described unit, where: l.
System commands LD 32 387 DISU l s c u Disable the indicated IP Trunk 3.01 (and later) unit (port), where: l = loop, s = shelf, c = card, u = unit Enable an indicated IP trunk card port T o enab le an indicated IP tr unk card por t in LD 32, use the f ollowing command: ENLU l s c u Enable the indicated IP Trunk 3.
388 OA and M using the ITG shell CLI and o verlays Nor tel Communication Ser v er 1000 IP T r unk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nor tel Networks .
389 Maintenance Contents This section contains information on the follo wing topics: "Introduction" (page 390) "IP Trunk 3.01 (and later) IP trunk card alarms" (page 391) "System level maintenance" (page 396) "Access the IP trunk card" (page 396) "IP trunk card LD commands" (page 396) "TM 3.
390 Maintenance "IP trunk card" (page 420) "TM 3.1" (page 420) "Command Line Interface" (page 420) "Fault clearance procedures" (page 421) "DSP failure&quo.
IP T runk 3.01 (and later) IP trunk card alar ms 391 • "F ault clearance procedures" (page 421) – potential system faults and how to correct them. IP T runk 3.01 (and later) IP trunk card alarms This section describes the alar ms, messages and codes output by the ITG-P entium 24-por t and Media Card 32-por t tr unk cards.
392 Maintenance Up to eight destination IP addresses can be configured to which these alarms can be sent. The same addresses must be configured f or all cards on the same node. T able 55 "IP T r unk 3.01 (and later) alar ms" (page 392) lists SNMP alar ms by se verity .
IP T runk 3.01 (and later) IP trunk card alar ms 393 Alarm Description Fault Clearing Action ITG0203 Fallback to PSTN activated. Bad network condition. This alarm indicates a QoS fallback. Recurrent QoS fallback and recovery can indicate network faults, far-end IP Trunk 3.
394 Maintenance Alarm Description Fault Clearing Action ITG0301 DSP channel not responding. DSP channel is disabled. Card sends message to the system to busy the trunk. This ensures that user’s calls go through on good DSPs. These DSP errors are not cleared automatically.
IP T runk 3.01 (and later) IP trunk card alar ms 395 Alarm Description Fault Clearing Action ITG0402 Ethernet voice port failure. TLAN subnet problem or cable removed. ITG0403 ELAN network interface failure. ELAN subnet problem or cable removed. ITG0404 Cannot open address translation file.
396 Maintenance Alarm Description Fault Clearing Action ITG0451 D-channel hardware failure. Associated channels busied out. ITG0452 System messaging failure. Unable to process calls. ITG0453 Cannot open Gateway DN file ITG0454 Cannot open Gatekeeper password file.
System lev el maintenance 397 Ta b l e 5 6 Supported LD 32 commands Command Function DISC l s c Disable the indicated IP trunk card, where: l = loop, s = shelf, and c = card. DISI l s c Disable the indicated IP trunk card when idle, where: l = loop, s = shelf, and c = card.
398 Maintenance Command Function LDIC l s c u List the number of days since the last incoming call on the indicated trunk, where: l = loop, s = shelf, c = card, and u = unit. STAT l s c Print the system software status of the indicated IP trunk card, where: l = loop, s = shelf, and c = card.
System lev el maintenance 399 Ta b l e 5 8 MSDL commands Command Description ENL DCH num Enables the D-channel. DIS DCH num Disables the D-channel. STAT DCH num Displays the state of the D-channel application. RLS DCH num Releases the D-channel. EST DCH num Establishes multiple frame operation on the D-channel.
400 Maintenance Command Function Card Enabled The card has been enabled by the system. Channel Enabled A given channel has been enabled by the system. D-channel Released The D-channel link has been released. Alternate Routing QoS prevents calls from being completed.
ITG shell command set 401 Ta b l e 6 1 General purpose commands Command Description cardReset Perform a warm reboot of the IP trunk card. The card has to be in the OOS state to use this command. itgCardShow Show card information. ldrResTableShow Show Backup Leader and Followers for a given Leader.
402 Maintenance Command Description displayClear Clear the maintenance display on the faceplate of the IP trunk card. shellPasswordSet Change the default ITG shell password. emodelSim Allow user to interactively determine QoS score. itgHelp Show the complete command list.
ITG shell command set 403 Command Description routeDelete "IP address", "IP Gateway" Delete a route from the routing table. Example: ITG> routeDelete "47.
404 Maintenance Command Description bootPFileGet hostname, username, password, directory path, filename Update the bootptab file on the IP trunk card with the bootptab file on the indicated host, account, and path. The bootpFileGet task on the host starts an FTP session with the given parameters and downloads the file to the flash file system.
ITG shell command set 405 Command Description Example: ITG> currLogFilePut "ngals042", "anonymous", "guest", "/currDir", "logFile" prevLogFilePut h.
406 Maintenance Command Description setLeader IP address, IP gateway, subnet mask The one command that does all the necessary actions to make a Leader. Sets IP address, gateway, subnet mask, boot method to static, and Leader bit in NVRAM. Example: ITG> setLeader "47.
IP trunk card self-tests 407 Ta b l e 6 5 Operational Measurement command Command Description resetOM This command returns all Operational Measurement parameters collected since last log dump, includi.
408 Maintenance Additionally , the IP tr unk card has a four-char acter LED dot matr ix display on the faceplate f or the pur pose of providing status information dur ing maintenance operations.
Outgoing calls attempted/completed mismatch 409 Base code self-test The IP tr unk card base code perf or ms the follo wing tests: • flash integrity test • PGA read/write test • PC Card controll.
410 Maintenance still takes finite time f or messages to propagate. Howe ver , this is usually not a f actor . The main reason for attempted call mismatches are: • The outgoing side records e very SETUP message sent to it by the PBX. The incoming side records SETUP messages sent to the PBX by the ITG card.
IP T runk 3.01 (and later) upgrades 411 using a modem, an FTP session, or TM 3.1. P atch files are stored in Flash memor y and are loaded into DRAM memor y . Once a patch is in DRAM memor y , it can be activated, deactiv ated, and its status can be monitored.
412 Maintenance Command Description pins Puts a patch that has been loaded into memory (using the pload command) into service. This command activates a patch. If issued successfully, the pins command indicates that global procedures, functions, or areas of memory are affected by the patch.
IP T runk 3.01 (and later) upgrades 413 Command Description pstat Gives summary status information for one or all loaded patches. For each patch, the following information is displayed: patch handle, .
414 Maintenance Command Description pnew The pnew command has no parameter(s). P atch Directories There are two patch director ies on an IP tr unk card: 1. /C:/u/patch This is the def ault director y for patch files. P atch files should be copied to this director y .
IP T runk 3.01 (and later) upgrades 415 click the Configuration tab . "S/W version" displa ys the current software v ersion as read from the IP tr unk card. 4 F rom the main card list view , select the cards to be upgraded. Upgrade all cards in the node together , unless installing a spare card that has older software.
416 Maintenance the TM 3.1 IP T runk 3.01 (and later) status refresh (that is, disab led: active; disab led: backup: disabled). 13 These cards should remain in the disabled state after the upgrade so .
Replace an IP trunk card 417 3 If the card to be replaced is an ITG 8-por t trunk card, disconnect the TLAN Ether net cable from the faceplate of the bad card. Label the cable to identify it as the TLAN Ethernet connection so it can later be reattached to the replacement card.
418 Maintenance When the IP trunk cards are installed, the red LED on the f aceplate is lit if: the card has rebooted; the card is active but there are no trunks configured on it, or the card is activ e and has trunks, but the trunks are disabled.
Replace an IP trunk card 419 —End— Determine IP trunk card software release F ollow the steps in Procedure 71 "Deter mining the IP tr unk card software release" (page 419) to deter mine the current software release on the IP trunk card.
420 Maintenance Click the Start T ransmit button. The transmission status is display ed in the "T ransmit control" bo x. Confirm the card proper ties and dialing plan are transmitted correctly . 4 When the transmission is complete, clic k the Close button.
F ault clearance procedures 421 Fault c learance procedures This section provides possib le solutions to such f aults as the f ollowing: • DSP f ailure • card f ailure • DCH f ailure • DCH lin.
422 Maintenance Remov e the card f or two to three seconds and then re-seat it in the IPE shelf . If the failure continues, replace the card. DCH failure There are three types of DCH failure which can affect the IP trunk card: 1. DCH link failure (DCH releases) 2.
Media Card 32-por t tr unk card faceplate maintenance displa y codes 423 Sock et Ser vices are responsible f or card inser tion and removal. There is a single interruption shared f or inser tion and remov al e vents and a single interruption for de vice-specific interruptions.
424 Maintenance Ta b l e 6 8 Media Card 32-por t trunk card faceplate maintenance display message summary Code Description T:00 Initialization T:01 Testing internal RAM T:02 Testing ALU T:03 Testing a.
ITG-P entium 24-por t tr unk card faceplate maintenance display codes 425 Code Description LDR Card is running active leader tasks. BLDR Card has detected existing Active Leader and is running Backup Leader tasks, or the card is configured as a Leader and is missing its node properties.
426 Maintenance If self-tests T:10-T :17 f ail, the display contains the f ailure message for three seconds and the ITG-P entium 24-por t tr unk card goes on to the ne xt test. If more than one test f ails, the message displa yed indicates the last failure.
ITG-P entium 24-por t tr unk card faceplate maintenance display codes 427 Normal Code Fault Code Description T:20 Card LAN enabled, waiting for Request Config Message. IP trunk card is looking for an active leader by sending BOOTP requests on the ELAN subnet.
428 Maintenance System performance under hea vy load When the system and IP T r unk 3.01 (and later) are carr ying traffic approaching the maximum sustained lev els, there can be shor t bursts of traffic e xceeding the maximum threshold le vel. This is caused by the randomness of call star ts.
System performance under heavy load 429 ov er-tasked. T o resolve this situation, separate the D-channel and IP functions; that is, hav e the DCHIP Leader reside on a F ollower card. • If none of these apply , consider splitting the IP T runk 3.01 (and later) node into two or more DCHIP Leader and F ollower groups .
430 Maintenance Message: BUG085 Description The system detected an in valid s witchhook state when the call was in the RINGING state. The s witch-hook state should be off-hook; if it is not, the error message is generated. Normal cause The causes can include debounce error and guard timer violation.
431 Appendix A P atches and ad visements Contents This section contains information on the follo wing topics: "Introduction" (page 431) Introduction This appendix descr ibes the f ollowing patches f or IP T r unk 3.0 and IP T r unk 3.01: MPLR17662, MPLR17346, MPLR18142, and MPLR18157.
432 Appendix A P atches and advisements IP T runk 3.01.22 patches The patches applicable to IP T runk 3.01.22 are: • MPLR18142 • MPLR18157 MPLR18142 FIN_W AIT_2 sock et loss and related IXP restar t av oidance. MPLR18157 TLAN subnet info not recognized if QSIG uses 7-bit channel address.
Interoperability with IP T r unk 3.01 (MPLR17662 patch) 433 Since there is no adv erse effect caused b y installing the patch on IP T r unk 3.0, and upgrading a network on a node-b y-node basis simplifies maintenance greatly , Nor tel recommends that the second alter native be used.
434 Appendix A P atches and advisements Nor tel Communication Ser v er 1000 IP T r unk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nor tel Networks .
435 Appendix B Cable description and NT8D81B A cable replacement Contents This section contains information on the follo wing topics: "Introduction" (page 431) "NTMF94EA ELAN, TLAN and .
436 Appendix B Cable description and NT8D81BA cable replacement NTMF94EA ELAN, TLAN and Serial P or t cable The NTMF94EA cable connects the I/O connector on Mer idian 1 Option 11C Cabinet, CS 1000M Cabinet, or Large Systems to the ELAN network interf ace, TLAN network interf ace, and one RS-232 por t.
NTCW84KA ELAN, TLAN, DCH and serial cable 437 I/O Panel: P1 Signal Name P2, P3, P4 Color P1-48 RXDB- P3-6 Orange/White P1-49 TXDB- P3-2 White/Orange P1-18 RX+ P4-3 Green/White P1-43 RX- P4-6 White/Gre.
438 Appendix B Cable description and NT8D81BA cable replacement Figure 149 NTCW84KA ELAN, TLAN, DCH, and serial cable Ta b l e 7 2 NTCW84KA ELAN, TLAN, DCH, and Serial I/O cable connections I/O Panel:.
NT AG81CA F aceplate Maintenance cable 439 I/O Panel: P1 Signal Name P2, P3, P4, P5 Color P1-31 P2 SHLD GRND P1-50 P2 SHLD GRND P1-23 RXDB+ P3-3 Green/White P1-48 RXDB- P3-6 White/Green P1-24 TXDB+ P3.
440 Appendix B Cable description and NT8D81BA cable replacement Figure 150 NT A G81CA PC maintenance cable Ta b l e 7 3 NT A G81CA Faceplate Maintenance cable connections Signals (IP Trunk 3.
NTCW84EA DCH PC Card pigtail cable 441 Ta b l e 7 4 NT A G81BA Maintenance Extender cable connections 9-pin D-Sub (Male) 9-pin D-Sub (Female) 11 22 33 44 55 66 77 88 99 NTCW84EA DCH PC Card pigtail cable The NTCW84EA pigtail cable connects por t 0 of the DCH PC Card to the J14 pin header on the motherboard.
442 Appendix B Cable description and NT8D81BA cable replacement Figure 152 NTCW84EA pigtail cable Ta b l e 7 5 NTCW84EA pigtail cable connections PC Card P1 Signal Name P2 Color P1-1 SDAI P2-1 Black P.
NTMF04BA MSDL extension cab le 443 PC Card P1 Signal Name P2 Color P1-10 RDBI P2-8 Grey P1-11 STBI P2-9 Tan P1-12 RTBI P2-10 Pink P1-15 GRND P2-11 Green/Yellow NTMF04B A MSDL extension cable The NTMF04BA cable connects the MSDL (D-Channel) por t of the NTCW84KA and the NTND26AA at the 15 pin I/O panel Filter Connector on the Network shelf.
444 Appendix B Cable description and NT8D81BA cable replacement NTCW84LA and NTCW84MA upgrade cables The f ollowing cables are required f or the upgraded 8-P or t ITG ISL T r unk DCHIP card: • NTCW8.
NTCW84LA and NTCW84MA upgrade cab les 445 Figure 154 NTMF94LA upgrade cable Ta b l e 7 7 NTMF94LA cable connections I/O Panel: P1 Signal Name P2, P3,P4 Color P1-21 BSOUTB- P2-2 RED P1-22 BDTRB- P2-4 G.
446 Appendix B Cable description and NT8D81BA cable replacement I/O Panel: P1 Signal Name P2, P3,P4 Color P1-43 RXDB- P5-6 WHT/GRN P1-44 TXDB- P5-2 WHT/ORG P1-23 RX+ P3-3 GRN/WHT P1-24 TX+ P3-1 ORG/WH.
Replace cable NT8D81BA with NT8D81AA 447 Procedure 73 Preventing gr ound loops on connection to external LAN equipment Step Action 1 Connect the customer-provided shielded CA T5 Ether net cable to the e xter nal LAN equipment. Ensure that the e xter nal LAN equipment is powered-up .
448 Appendix B Cable description and NT8D81BA cable replacement Ta b l e 7 8 NT8D37 cable connections Backplane slots–shroud rows I/O panel/cable designation L0–1, 2, 3 A L1–1, 2, 3 B L2–1, 2,.
Remov e the NT8D81BA cable 449 T ools list • T y-wrap cutter • T y-wraps • Needle-nose pliers • Slotted screwdriv er Remove the NT8D81B A cable F ollow the steps in Procedure 74 "Removing the NT8D81BA cable" (page 449) to remov e the NT8D81BA cable.
450 Appendix B Cable description and NT8D81BA cable replacement Procedure 75 Installing the NTCW84JA filter and NT8D81AA cable Step Action 1 Install the NTCW84JA special IPE filter connector in the vacant I/O panel slot using retained hardware. 2 Install NT8D81AA r ibbon cab le connectors in the IPE module backplane shroud.
451 Appendix C En vir onmental and electrical regulator y data Contents This section contains information on the follo wing topics: "Environmental specifications" (page 451) "Mechanical.
452 Appendix C Environmental and electrical regulator y data Specification Minimum Maximum Recommended Relative humidity –50 C 0% +70 C 95% (non-condensing) Temperature shock In three minutes In thr.
Electrical regulator y standards 453 Ta b l e 8 1 Safety regulations for the ITG-Pentium 24-port trunk cards Regulation identifier Regulatory agency UL 1459 Safety, United States, CALA CSA 22.2 225 Safety, Canada EN 41003 Safety, International Telecom BAKOM SR 784.
454 Appendix C Environmental and electrical regulator y data Regulation identifier Regulatory agency BAKOM SR 784.103.12/4.1/1 EMC/Safety (Switzerland) SS-447-20-22 Sweden EMC standard AS/NZS 3548 EMC.
Electrical regulator y standards 455 Regulation identifier Regulatory agency IEC 801-5 (level 4, preliminary) Surge Immunity (Basic Standard) IEC 801-6 (preliminary) Conducted Disturbances (Basic Standard) BAKOM SR 784.
456 Appendix C Environmental and electrical regulator y data Nor tel Communication Ser v er 1000 IP T r unk Fundamentals NN43001-563 02.01 Standard Release 5.
457 Appendix D Subnet mask con ver sion fr om CIDR to dotted decimal f ormat Subnet masks can be expressed in Classless Inter Domain Routing (CIDR) f or mat, appended to the IP address (for e xample, 10.1.1.1/20). The subnet mask must be conv er ted from CIDR format to dotted decimal f or mat to configure ITG IP addresses.
458 Appendix D Subnet mask conv ersion from CIDR to dotted decimal format In the e xample of /20 previously giv en, the remainder is 4. In Ta b l e 87 "CIDR format remainders" (page 458) , a remainder of 4 is equal to a binar y value of 1111 0000 and the dotted decimal format value of the ne xt and last field is 240.
459 Appendix E CLI commands IP T runk 3.01 (and later) suppor ts the following CLI commands: • ectailDefault – configure IP T runk 3.01 (and later) to use the default 128ms Echo Canceller T ail length. • ectailNonDefault – configure IP T runk 3.
460 Appendix E CLI commands Nor tel Communication Ser v er 1000 IP T r unk Fundamentals NN43001-563 02.01 Standard Release 5.5 21 December 2007 Copyright © 2007, Nor tel Networks .
461 Appendix F Configure a Netg ear RM356 modem r outer f or remote access Contents This section contains information on the follo wing topics: "Introduction" (page 461) "Security features of the RM356 modem router" (page 462) "Install the RM356 modem router" (page 462) "Configure the TM 3.
462 Appendix F Configure a Netgear RM356 modem router for remote access Security features of the RM356 modem router Security features of the RM356 modem router are as follo ws: • P ass word Authent.
Install the RM356 modem router 463 3 Connect the RJ-45 plug end of the local manager cable to the RS-232 Manager por t RJ-45 jac k on the rear of the modem router .
464 Appendix F Configure a Netgear RM356 modem router for remote access F ollow the steps in Procedure 78 "Configure the RM356 modem router through the manager menu" (page 464) to configure the RM356 modem router through the manager menu.
Install the RM356 modem router 465 11 T oggle "RIP Direction=None". Press Enter to confirm and sav e data to ROM, then press Esc to retur n from the sub-menu to the main menu. 12 Enter menu selection number 12, "Static Routing Setup", under the "Advanced Applications" section.
466 Appendix F Configure a Netgear RM356 modem router for remote access Under "PPP Options" toggle "Recv Authen=P AP". Windows 9x Dialup Networking (DUN) is not compatible with CHAP/P AP or CHAP on the modem route; calls are disconnected after a f ew minutes.
RM356 modem router manager menu (application notes on the ELAN subnet installation) 467 Set "Rem CLID=" to the PSTN Calling Number that is display ed when the remote TM 3.1 PC dials up the modem router , if CLID authentication is required for the user profile.
468 Appendix F Configure a Netgear RM356 modem router for remote access Contact Person’s Name= John Smith, 972 555-1212 Press ENTER to Confirm or ESC to Cancel: Menu 2 - MODEM Setup Modem Name= MODEM Active= Yes Direction= Incoming Phone Number= Advanced Setup= No Press ENTER to Confirm or ESC to Cancel: Menu 3 - Ethernet Setup 1.
RM356 modem router manager menu (application notes on the ELAN subnet installation) 469 CLID Authen= None Dial-in User= No IP Pool= Yes PPP Options: IP Start Addr= 47.
470 Appendix F Configure a Netgear RM356 modem router for remote access 4 _______________ 10 _______________ 5 _______________ 11 _______________ 6 _______________ 12 _______________ Enter Filter Set Number to Configure= 0 Edit Comments= Press ENTER to Confirm or ESC to Cancel: Menu 21.
RM356 modem router manager menu (application notes on the ELAN subnet installation) 471 Status: 10M/Half Duplex RAS S/W Version: V2.13 | 9/25/98 TX Pkts: 135579 Ethernet Address:00:a0:c5:e0:5b:a6 RX Pkts: 662866 Collisions: 49 LAN Packet Which Triggered Last Call: Press Command: COMMANDS: 1-Drop Port 1 9-Reset Counters ESC-Exit Menu 24.
472 Appendix F Configure a Netgear RM356 modem router for remote access TCP/IP 11. Internet Setup Test 12. Ping Host Enter Menu Selection Number: Manual Call Remote Node= N/A Host IP Address= N/A Menu 24.7 -- System Maintenance - Upload Firmware 1. Load RAS Code 2.
473 Appendix G Upgrade an ITG T runk 1.0 node to suppor t ISDN signaling trunks Contents This section contains information on the follo wing topics: "Upgrade procedure summary" (page 474) &q.
474 Appendix G Upgrade an ITG T r unk 1.0 node to suppor t ISDN signaling tr unks IP T runk 3.01 (and later) cannot be installed on an ITG 8-por t trunk card. Howe ver , IP T runk 3.01 (and later) can interwork with ITG T runk 2.0 nodes. IP T runk 3.01 (and later) does not interwork with ITG T runk 1.
Before y ou begin 475 advanced ISDN f eatures. T able 2 "Software pac kages for Meridian 1/CS 1000M IP T r unk 3.01 (and later)" (page 33) lists required software pac kages. 3 Check the Nor tel w ebsite to find the latest ITG 8-por t trunk card software.
476 Appendix G Upgrade an ITG T r unk 1.0 node to suppor t ISDN signaling tr unks 8 V erify that the customer site has a Nor tel Netgear RM356 Modem Router (or equivalent) on the ELAN subnet. The modem router provides remote suppor t access to ITG T runk and other IP-enabled Nor tel products.
Install the DCHIP hardware upgrade kit 477 4 Connect the NTCW84EA pigtail cable from por t 0 of the DCHIP PC Card to the J14 pin header on the motherboard of the DCHIP card (see Figure 34 "DCHIP PC Card and NTCW84EA pigtail cable" (page 192) ).
478 Appendix G Upgrade an ITG T r unk 1.0 node to suppor t ISDN signaling tr unks Procedure 81 Installing the DCHIP I/O P anel break out cable fr om the upgrade kit Step Action 1 F or the Large System, locate the I/O connector that corresponds to the leftmost card slot of the ITG 8-por t trunk card that is undergoing the hardware upgr ade.
Upgrade the ITG 8-por t trunk card ITG basic tr unk software to ITG/ISL trunk software 479 2 Login to the ITG shell. At the ITG> prompt, enter setLeader setLeader " xxx.xxx.xxx.xxx", "yyy.yyy.yyy.yyy", "zzz.zzz.zzz.zzz " where • "xxx.
480 Appendix G Upgrade an ITG T r unk 1.0 node to suppor t ISDN signaling tr unks 7 Log into the ITG shell. At the ITG>prompt, enter clearLeader "xxx.xxx.xxx.xxx", "yyy.yyy.yyy.yyy", "zzz.zzz.zzz.zzz" (see notes in step 2).
Upgrade the ITG 8-por t trunk card ITG basic tr unk software to ITG/ISL trunk software 481 T ransmit Control windo w open displaying the location of the software file on TM 3.1. If the tr unk card can be reached by T elnet from TM 3.1, but TM 3.1 shows the card status as Not Responding, TM 3.
482 Appendix G Upgrade an ITG T r unk 1.0 node to suppor t ISDN signaling tr unks Figure 157 Software download example 9 T o verify the software upg rade on Leader 0, telnet to the IP address of the Leader 0 card. Leader 0 is the only card that has an IP address configured at this stage of the upgrade .
Configure the Meridian 1 ITG/ISL tr unk data 483 Procedure 84 Removing the ITG T runk 1.0 configuration data from Meridian 1 Step Action 1 Out existing ITG basic trunks that are being upgraded to ITG ISL trunks: a. Identify TNs of trunks that are to be outed.
484 Appendix G Upgrade an ITG T r unk 1.0 node to suppor t ISDN signaling tr unks F ollow the steps in Procedure 85 "Configur ing the Mer idian 1 ITG/ISL tr unk data" (page 484) to configure the Mer idian 1 ITG/ISL tr unk data.
Upgrade T roubleshooting 485 V erify ROM-BIOS ver sion When the ITG tr unk card is reset, it displays a series of star tup messages on the local TTY . V er ify that the ROM-BIOS is 1.1 or g reater . If not, contact Nor tel technical suppor t. Upgrade T roubleshooting This section provides two procedures to correct TM 3.
486 Appendix G Upgrade an ITG T r unk 1.0 node to suppor t ISDN signaling tr unks —End— Nor tel Communication Ser v er 1000 IP T r unk Fundamentals NN43001-563 02.
487 Inde x Symbols/Numerics 10/100BaseT 46, 64 10/100BaseT Ethernet por ts 153 100BaseT full-duple x 160 100BaseTX 31 10BaseT 31, 31, 46, 64 10BaseT Ethernet hub 33 A AAL5 112 Active Leader 39, 39, 40.
488 Index Dela y variation 168 dela y variation or 90 Delete a system 299 Dial Plan table 23 dialing plan 44, 65, 84 Dialing plan 65 DSP Profile 306 duple x mismatch 161 E edit node inf or mation 311.
Index 489 J jitter 71, 72, 90 jitter buff er 168 Jitter buff er parameters 162 jitter , and 90 L Large Systems 32 latency 67, 71, 71, 74, 74, 74, 74, 74, 77, 92 Latency 72 LDR 49, 54 Leader 24, 40 Lea.
490 Index routing table entry 267 RRQ 25 RS-232 serial por ts 153 RS-422 42, 64 R TP 130 S SDI/DCH card 32 self-test 48 serial maintenance por t 50, 50, 50, 50, 54, 54 shell 161 Signaling Ser ver 26 s.
.
Nor tel Communication Ser ver 1000 IP T r unk Fundamentals Copyright © 2007, Nor tel Networks All Rights Reser ved. Publication: NN43001-563 Document status: Standard Document version: 02.01 Document date: 21 December 2007 T o provide f eedback or to repor t a problem with this document, go to h ttp://www .
Een belangrijk punt na aankoop van elk apparaat Nortel Networks NN43001-563 (of zelfs voordat je het koopt) is om de handleiding te lezen. Dit moeten wij doen vanwege een paar simpele redenen:
Als u nog geen Nortel Networks NN43001-563 heb gekocht dan nu is een goed moment om kennis te maken met de basisgegevens van het product. Eerst kijk dan naar de eerste pagina\'s van de handleiding, die je hierboven vindt. Je moet daar de belangrijkste technische gegevens Nortel Networks NN43001-563 vinden. Op dit manier kan je controleren of het apparaat aan jouw behoeften voldoet. Op de volgende pagina's van de handleiding Nortel Networks NN43001-563 leer je over alle kenmerken van het product en krijg je informatie over de werking. De informatie die je over Nortel Networks NN43001-563 krijgt, zal je zeker helpen om een besluit over de aankoop te nemen.
In een situatie waarin je al een beziter van Nortel Networks NN43001-563 bent, maar toch heb je de instructies niet gelezen, moet je het doen voor de hierboven beschreven redenen. Je zult dan weten of je goed de alle beschikbare functies heb gebruikt, en of je fouten heb gemaakt die het leven van de Nortel Networks NN43001-563 kunnen verkorten.
Maar de belangrijkste taak van de handleiding is om de gebruiker bij het oplossen van problemen te helpen met Nortel Networks NN43001-563 . Bijna altijd, zal je daar het vinden Troubleshooting met de meest voorkomende storingen en defecten #MANUAl# samen met de instructies over hun opplosinge. Zelfs als je zelf niet kan om het probleem op te lossen, zal de instructie je de weg wijzen naar verdere andere procedure, bijv. door contact met de klantenservice of het dichtstbijzijnde servicecentrum.
