Ipt3 Expert Level Support Guide

nd

still

Expert Info

IP Trunk 3.0 Expert Level Support Guide

Author: Pat Hession Dept. 8047 GALMark Whitney Dept. 8047 GALShuang Chen Dept. 9P84 BVWL Patrick Findlay Dept. 9T42 BVW

Manager: Dave O’Connell Dept. 8047 GALMonica Patel Dept. 9P84 BVWGwen Clarke Dept. 9T42 BVW

Date: 05 May 03

Issue: Issue 1.5.4

System: Meridian 1 X11

Release: IP Trunk 3.0

Project Name: ITG

Sub-Feature: IP Trunk 3.0

Target Market: Global

Activity Id:

Keywords: ITG, ITG-P, SMC, Trunk, IPT 3.0, IP Trunk 3.0, VoIP,Troubleshoot

Abstract: Troubleshooting the IP Trunk feature requires insight into IP atraditional M1 telephony. This document describes tools andtechniques that can help.

Warning: users debugging ITGT 2.x.26G and lower should use the ITGTExpert Guide version 1.4 or lower. The commands from that vintage thatapply to IP Trunk 3.0 are included in this document, but many extracommands are also included that are unsupported in prior releases.

PROPRIETARY INFORMATION

The information contained in this document is the property of Nortel Networks. Except as specifically authorizedin writing by Nortel Networks, the holder of this document shall: (1) keep all information contained hereinconfidential and shall protect same in whole or in part from disclosure and dissemination to all third parties, and (2)use same for operating and maintenance purposes only.

NORTEL NETWORKS CONFIDENTIAL

Nortel Networks Confidential

Issue 1.5.4 IP Trunk 3.0 Expert Level Support Guide05 May 03 Page 2


6

2

7

6

1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.2 Resolving IP Trunk problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.3 Use of a Network Sniffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.4 IP Trunk and VxWorks shell access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

1.4.1 Connecting to the card’s RS232 Maintenance port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.4.1.1 Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.4.1.2 Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

1.4.2 VxWorks shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2 IP Trunk 3.0 module descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.2 Modules key to call related problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.3 Modules key to QoS related problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.4 Modules key to Leader / Follower communication problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.5 Modules key to T-LAN / E-LAN and inter-task messaging problem . . . . . . . . . . . . . . . . . . . . . . . . . . 222.6 Modules key to OTM to card communication and configuration problems . . . . . . . . . . . . . . . . . . . . . 232.7 Modules key to DCH problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242.8 Modules key to SSD / A07 related problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.9 Modules key to DSP related problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

3 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.1 Using a Network Sniffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

3.1.1 Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.1.2 Sniffer Pro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

3.2 General card commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.3 Disk and Directory Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.4 Network Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3.4.1 General troubleshooting suggestions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.4.2 RMD errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.4.3 QoS Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363.4.4 BandWidth Optimization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373.4.5 Network Interface - Speed and Mode Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.4.6 Broadcast storms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383.4.7 Port numbers used by the IP Trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

3.4.7.1 TCP Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393.4.7.2 UDP Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

3.4.8 SNMP traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403.5 Call Related Problem Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

3.5.1 Channel selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.5.2 Gatekeeper problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

3.6 Audio Quality Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423.7 Address Translation Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433.8 D-Channel Related Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.8.1 DCHmenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443.9 Backup Leader start-up issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

4 Potentail provisioning problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464.1 Creating trunks for ESN5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464.2 Problems with downloading provisioning - ContactSet error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44.3 Echo cancellation tail delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Issue 1.5.4 IP Trunk 3.0 Expert Level Support Guide Section: Table of Contents05 May 03 Page 3


9

9

4

5

2

64

7

5 Debugging the shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495.2 Password operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

5.2.1 Recovering from a corrupted password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.2.2 Password modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

5.3 General card commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505.3.1 Hardware and software queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505.3.2 Memory and tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515.3.3 Operational data and timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

5.4 Disk and directory commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515.4.1 Navigating the file system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515.4.2 Verifying and sanitizing the file system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525.4.3 Download/upload of files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

6 Debugging the node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56.1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546.2 General card commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546.3 Configuration and startup file checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

6.3.1 Verify provisioning on the card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546.3.2 Corrupted leader data, but ELAN IP address is correct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56.3.3 ELAN information corrupted but provisioning valid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566.3.4 ELAN and configuration information corrupted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

6.4 Remote node status checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586.5 Memory fault diagnostic commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586.6 Node commissioning commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596.7 Disk and directory debugging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

7 Call processing debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617.1 Identifying the issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617.2 Message tracing commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

7.2.1 Eliminate the PBX or Call Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617.2.2 Ensure that the originating side card accepted the call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67.2.3 Ensure that the call traversed the network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647.2.4 Ensure gatekeeper ARQ succeeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.5 Ensure that the call left the destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

8 Debugging audio issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68.1 Echo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

8.1.1 Provisioning advisory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678.1.2 “The echo checklist” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

8.2 Debugging, other problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

9 BIOS / BootROM functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759.2 Accessing the /C: drive file system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799.3 Viewing NVRAM contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809.4 BootROM compatibility levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809.5 BIOS / BootROM Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

10 Maintenance Task (Task Monitor Function) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8410.1 audit.ini file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8410.2 audit.his history file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Section: Table of Contents IP Trunk 3.0 Expert Level Support Guide Issue 1.5.4Page 4 05 May 03


1

0

10.3 CLI commands for Audit/Maintenance task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

11 Patcher Tool Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8611.1 On Switch Patch Tool CLI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

12 Installation and upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8712.1 Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

12.1.1 FTP server and file transfer options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8712.1.2 Setting NVRAM parameters from the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8812.1.3 Setting NVRAM parameters from the BIOS / BootROM. . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

12.1.3.1 IPT-P, SMC with BIOS version 5.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8812.1.3.2 SMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

12.2 Software Upgrade Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8912.2.1 Software upgrades from the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9012.2.2 Software upgrades from the ROM BIOS v1.2 CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9012.2.3 Software upgrades from the BootROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 912.2.4 FTP upgrade on SMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9112.2.5 SMC BIOS Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

12.3 Transmit Node and Card Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

13 VxWorks Startup Script Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

14 Exception Trace Decoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

15 Formatting the /C: Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9615.1 Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9615.2 Symptoms of /C: Drive Corruption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9615.3 Out of File Descriptors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9615.4 Using chkdsk to Identify Corruption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9715.5 Formatting the /C: Drive on Pentium platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9815.6 Recovering the /C: Drive on Media Card platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

16 Card Startup Log Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10016.1 Pentium captures - Leader bootup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10016.2 Pentium captures - Follower bootup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10416.3 Succession Media Card captures - Leader bootup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Appendix A Configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111A.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111A.2 CONFIG1.INI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

A.2.1 Downloading / parsing from TTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112A.2.1.1 configFileGet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

A.2.2 Example file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112A.3 DPTABLE.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

A.3.1 Downloading / parsing from TTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114A.3.1.1 nmmAtpmTranTblDnld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

A.3.2 Example file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114A.4 BOOTP.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

A.4.1 Example file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Appendix B IP Trunk Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119B.1 Commands accessible from the ITG> or -> prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

B.1.1 auditRebootSet 0/1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120



B.1.2 auditRebootTimeSet hh:mm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120B.1.3 auditShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121B.1.4 auditTaskSet [tname|tid],level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121B.1.5 cardReset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122B.1.6 cd “dirPath” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122B.1.7 clearLeader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122B.1.8 copy “sourceFilename”, “destFilename” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123B.1.9 dchipResTableShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124B.1.10 DCHmenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126B.1.11 dosFsConfigShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134B.1.12 firmwareVersionShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135B.1.13 gkShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135B.1.14 h323CallTrace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140B.1.15 h323SessionShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143B.1.16 i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145B.1.17 ifShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146B.1.18 IPInfoShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148B.1.19 iptSessionShow [level] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150B.1.20 itgCardShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152B.1.21 itgChanStateShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155B.1.22 itgMemShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156B.1.23 itgMsgCtrShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157B.1.24 ldrResTableShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158B.1.25 ll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159B.1.26 numNodesInFallbackShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160B.1.27 NVRClear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160B.1.28 NVRGWSet “gwIPaddr” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161B.1.29 NVRIPSet “IPaddr” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162B.1.30 NVRIPShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162B.1.31 NVRSMSet “subnetMask” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162B.1.32 ping “IPaddr”, numPings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163B.1.33 pwd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163B.1.34 resetOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163B.1.35 routeAdd “destIPaddr”, “gwIPaddr” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164B.1.36 routeDelete “destIPaddr”, “gwIPaddr” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164B.1.37 routeShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164B.1.38 serialNumShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165B.1.39 setLeader “IPaddr”,”gwIPaddr”,”subnetMask” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165B.1.40 shellPasswordSet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165B.1.41 swDownload “srvrIP”, “uid”, “passwd”, “path”, “fname” . . . . . . . . . . . . . . . . . . . . . . . . . . 166B.1.42 swVersionShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166B.1.43 tsmChanShow [level[,channel]] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167B.1.44 useIPTForRingBack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169B.1.45 useM1ForRingBack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169B.1.46 vxWorksShell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

B.2 Commands only accessible from the -> prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171B.2.1 arpFlush . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171B.2.2 arpShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171B.2.3 attrib “filename”,“protection” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172B.2.4 chkdsk “dev”, repairLevel, entryLevelType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173B.2.5 devs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174



8

77

9

8

2

B.2.6 DimECStat = 1/0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175B.2.7 dimPrintChannelInfo TCID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176B.2.8 dspFatalErrorCountClear dspnum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17B.2.9 dummy_trap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178B.2.10 exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178B.2.11 flashConfigShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179B.2.12 h and command history handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180B.2.13 icmpstatShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181B.2.14 igccAddTrace, igccNoTrace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

B.2.14.1 igccAddTrace channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182B.2.14.2 igccNoTrace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

B.2.15 inetstatShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182B.2.16 iosFdShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184B.2.17 ipstatShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185B.2.18 itgExcpCountClear - Pentium card only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185B.2.19 itgExcpCountShow - Pentium card only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185B.2.20 itgShell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186B.2.21 lkup “string” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186B.2.22 lnIsaBroadcastShow - not applicable, SMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18B.2.23 lnIsaBroadcastThreshold = threshold - not applicable, SMC . . . . . . . . . . . . . . . . . . . . . . . . 18B.2.24 lnIsaShowLostBroadcast = 1/0 - not applicable, SMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188B.2.25 lnPciBcastFilterOff - not applicable, SMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188B.2.26 lnPciBcastFilterOn - not applicable, SMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188B.2.27 lnPciBroadcastShow - not applicable, SMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18B.2.28 lnPciBroadcastThreshold = threshold - not applicable, SMC . . . . . . . . . . . . . . . . . . . . . . . 189B.2.29 lnPciShowLostBroadcast = 1/0 - not applicable, SMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190B.2.30 ls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190B.2.31 mac21440BroadcastShow - only applicable for SMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191B.2.32 mac21440BroadcastThreshold = threshold - only applicable for SMC . . . . . . . . . . . . . . . . 191B.2.33 mbufShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192B.2.34 mixLevelOn module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193B.2.35 mixMemFindAll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193B.2.36 mixOptionOn module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195B.2.37 mixSetLogOpt module, option, level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195B.2.38 mkdir “dirName” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197B.2.39 monIPDebugSet “IP.ad.dr.ess”, on_off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19B.2.40 monUtility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199B.2.41 mRouteAdd “destIPaddr”, “gwIPaddr”, 0xdestNetMask, To, 0 . . . . . . . . . . . . . . . . . . . . . 202B.2.42 mRouteDelete “destIPaddr”, 0xdestNetMask, ToS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20B.2.43 mRouteShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202B.2.44 netHelp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203B.2.45 nmmAtpmTranTblDnld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203B.2.46 Patch commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

B.2.46.1 pins “patchNumber” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204B.2.46.2 plis, or plis “patchNumber” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205B.2.46.3 pload, or pload “patchName” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207B.2.46.4 poos “patchNumber” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207B.2.46.5 pout, or pout “patchNumber” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208B.2.46.6 pstat, or pstat “patchNumber” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

B.2.47 print_ip_table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210B.2.48 Printing dial plan data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211



0

B.2.48.1 Caveat - serious danger from provisioning errors within the DPTABLE.1 . . . . . . 212B.2.48.2 print_npa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212B.2.48.3 print_nxx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213B.2.48.4 print_spn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213B.2.48.5 print_loc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214B.2.48.6 print_cdp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214B.2.48.7 print_dsc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215B.2.48.8 print_tsc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

B.2.49 rm “filename” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216B.2.50 rmdir “dirName” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217B.2.51 rtpPortCompress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218B.2.52 rtpPortNonCompress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218B.2.53 set_time yy, mm, dd, hh, mm, ss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219B.2.54 setTraceOption channel,outputLocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22B.2.55 shellPasswordNvramClear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222B.2.56 shellTimeoutGet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222B.2.57 shellTimeoutSet timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222B.2.58 showMemConfig - Pentium only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222B.2.59 tcpstatShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223B.2.60 tlanDuplexSet duplexMode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224B.2.61 tlanSpeedSet speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225B.2.62 TsmDspStat = 1/0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226B.2.63 tsmSetTraceOption TCID,[0 or !0] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227B.2.64 tsm_stat_req commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

B.2.64.1 tsm_stat_req_ecdbg TCID or reqECDbg TCID . . . . . . . . . . . . . . . . . . . . . . . . . . 229B.2.64.2 tsm_stat_req_error TCID or reqError TCID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232B.2.64.3 tsm_stat_req_rx_tx TCID or reqRxTx TCID . . . . . . . . . . . . . . . . . . . . . . . . . . . 234B.2.64.4 tsm_stat_req_tele_levels TCID or reqTeleLevel TCID . . . . . . . . . . . . . . . . . . . . 236B.2.64.5 tsm_stat_req_vp_delay TCID or reqVpDelay TCID . . . . . . . . . . . . . . . . . . . . . . 238

B.2.65 udpstatShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240B.2.66 upgradeErase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

B.3 Disk commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241B.3.1 reformatAdrive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241B.3.2 reformatCdrive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241B.3.3 SMC: formatAtaCard 0/1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

B.4 Software download commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242B.4.1 Download over the IP network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242B.4.2 Download from the PCMCIA software delivery card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

Appendix C Annex 1 - BCM 2.x - IP Trunk Interoperability . . . . . . . . . . . . . . . . . . . . . . 243C.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

C.1.1 BCM Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243C.1.2 M1 Requirements: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

C.2 BCM Configuration Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245C.2.1 Basic Set to Set Calling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245C.2.2 Calling Line ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252C.2.3 Tandem Calling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253C.2.4 Private Network Identifier (PNI) - . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254C.2.5 Uniform Dial Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254C.2.6 Coordinated Dial Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256C.2.7 Message Waiting Indicator (MWI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257



C.2.8 Network Call Redirection (NCRD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257C.2.9 Trunk Route Optimization (TRO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259C.2.10 Trunk Anti Tromboning (TAT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

Index of commands.................................................................................................................. 263





.

ets

tion

ets. a

Abbreviations

APB - Audio Parameters BankAPI - Application Process InterfaceARP - Address Resolution ProtocolBIOS - Basic Input/Output System. A set of permanently stored program routinesBOOTP - BOOTstrap ProtocolCodec - COder DECoder. A DSP function that converts the PCM stream to pack

and back.CPU - Central Processing UnitDN - Directory NumberDSP - Digital Signal ProcessorEC - Echo CancellerELAN - Embedded LAN (10 BaseT LAN connection for internal signalling)EXUT - Enhanced Extended Universal TrunkFTP - File Transfer ProtocolIP - Internet ProtocolIPT - IP Trunk (basically, IP Trunk 3.0 as displayed on the login screen)ISDN - Integrated Services Digital NetworkingITG - Meridian Integrated IP Telephony GatewayITG-P - Meridian Integrated IP Telephony Gateway 24 port cardLAN - Local Area NetworkMAT - Meridian Administration Terminal - Window application for configuring the

Meridian-1 PBX and the ITGL application.MCDN - Meridian Customer Defined NetworkingOM - Operational MeasurementOS - Operating SystemOTM - Optivity Telephony Manager - replacement for MAT.PC Card - Current name used for PCMCIA style cards.PCMCIA - Personal Computer Memory Card International Association. This organiza

has defined a credit card sized plug in board for use in PCs.QoS - Quality of ServiceRTC - Real Time ClockRTP - Real Time Protocol. A layer above UDP for synchronization of voice packRTCP - Real Time Control Protocol. Used to exchange end point statistics about

voice packet stream.

Issue 1.5.4 IP Trunk 3.0 Expert Level Support Guide Section:05 May 03 Page 11


uni-

.

S/W - SoftwareSMC - Succession Media Card - 32 port ITG cardSNMP - Simple Network Management Protocol. Used to raise alarms and comm

cate OA&M between MAT/OTM and the ITG card.SNTP - Simple Network Time Protocol. Used to synchronize time between cardsTCID - Telephony Channel IDentifierTCP - Transmission Control ProtocolTFFS - True Flash File SystemTFTP - Trivial File Transfer ProtocolTLAN - Telephony LAN (10/100 BaseT LAN connection for ITG’s RTP packets)ToS - Type of ServiceTPS - Terminal Proxy ServerUDP - User Datagram ProtocolVoIP - Voice over IPWAN - Wide Area NetworkXUT - Universal Trunk Card (Analog Trunk)

Section: IP Trunk 3.0 Expert Level Support Guide Issue 1.5.4Page 12 05 May 03

Introduction Nortel Networks Confidential

re- thate

cardssssionfully.

andngnt on

y

ady

ut;) or on a

testh

suallyde

thes

1 Introduction

1.1 General

Warning: If the reader wishes to debug ITGT 2.x.24, 2.x.25, 2.x.26G or other pIP Trunk 3.0 releases, the reader should refer to the Expert Guide applicable torelease. This guide contains information that is completely not applicable to thearlier software versions.

Warning: Misuse of the commands in this reference document may make the unusable. Personnel that have not been trained in the use of the CLI can accecommands via this reference that render the ITG-Pentium (ITG-P) card or SucceMedia Card (SMC, or MC) unable to place calls, or even unable to reboot success

This document contains commands and techniques that can be used whentroubleshooting problems with the IP Trunk 3.0 application on the ITG-Pentium Succession Media Card platforms. IP Trunk 3.0 is the “next generation” followiInternet Telephony Gateway Trunk (ITGT) Release 25 and 26 applications, residethe ITG 2.0 (Pentium) and 2.1 (Media Card).

The information provided here is intended for an audience made up of NortelNetworks field support staff, distributors, and on-site technicians who are alreadfamiliar with the information provided in the relevant NTPs. The intent of thisdocument is to go to the next level and provide additional information for those alrecomfortable working directly at the VxWorks shell on the SMC or ITG-P card.

Note:Many of these commands can get you into trouble if incorrect information is inpthe SMC or ITG-P card may become inoperable (requiring a reboot to recovereven reboot on its own. Care is recommended when using these commandslive card.All commands in the appendices are listed with a “level of safety”. This indicawhether a command is “use whenever you want”, “use in off hours”, or “use wiextreme caution”.

Command syntax and examples are deferred to the appendices. Since a user uneeds to know the answer to the question “What command should I use?”, it mamore sense to describe scenarios where a command could be useful and deferdetails to the appendices, rather than providing a list of commands and variablewithout enough of an idea of when to use them.

Issue 1.5.4 IP Trunk 3.0 Expert Level Support Guide Section: 105 May 03 Page 13

Nortel Networks Confidential Introduction

and thein> or->).ds)

thehort

ay”n IP

s as

the

ge

nd/

ckets

Each section describing a command typically contains a description of the commsyntax, an example of the information printed (as appropriate) and tips on usingcommand and interpreting the results. If a command will work from the base logprompt (the IP Trunk shell), the example shows the command entered at the ITGIPT> prompt; otherwise the command is only accessible from the VxWorks shell (Once at the VxWorks shell, all commands (including the IP Trunk shell’s commanare available.

Note that a general convention is used in this document. Whenever referring tosoftware application the expression “IP Trunks” or a short form is used, with the sforms including “IPT 3.0" or “IPT”. “IPT” is the norm in the login windows, so it willbe included when applicable in this document as well, to minimize confusion.However, at times the text refers to the hardware, the “Internet Telephony Gatewcard (Pentium or Media Card). As this card can be used for more applications thaTrunk, whenever the card itself is discussed the short form may be “ITG”. (Forexample, “log in to the ITG-P card” could apply to any application residing on the 24port card; if the intent is to use a base level command used by other applicationwell, then strictly speaking we are not logging in to the IP Trunk application.VxWorks commands belong in this group; they are not IP Trunk commands. Onother hand, “log in to IPT” can only apply to the IP Trunk application.)

1.2 Resolving IP Trunk problems

In most problem/error condition some type of alarm is generated or error messaprinted.

• Check Alarms in CURRLOG.1/PREVLOG.1 files or at the OTM console.

• Check the SMC/ITG-P telnet or Maintenance port session display and theMeridian 1 TTY for any error messages being printed.

• Retrieve the CURRLOG.1/PREVLOG.1 files from the card and scan for error aor warning messages.

• Check card sanity from the SMC/ITG-P debug / telnet session.

• Start any appropriate monitoring tools and try to duplicate the scenario.

1.3 Use of a Network Sniffer

For network related problems, a network sniffer comes in handy to see what paare being sent and received by the SMC or ITG-P card on the TLAN and ELANinterfaces. Support staff (including Nortel employees) supporting the IP Trunkproduct on site should have access to a sniffer and be versed on its use.

Section: 1.2 IP Trunk 3.0 Expert Level Support Guide Issue 1.5.4Page 14 05 May 03


splay

ost

the

n the

s or to

M,

onor

portigh

neral,gin

are

anserial, butet

Stand-alone sniffers exist but the most cost effective are those that are just a PCapplication. These applications monitor the subnet the PC is connected to and diinformation about the network traffic. They usually include the capability ofmonitoring only specific port numbers or protocols and displaying and decoding mof the packet contents.

The following three programs are recommended:

• SnifferPro (current version 4.0)

• The shareware program LANExplorer. It can be used for 30 days before payingfull price to purchase it. Go tohttp://www.zdnet.com/downloads/ and search forLANExplorer.

• The free software program ethereal may be used (and is the sniffer of choice iITGT/IP Trunk design community). Go tohttp://www.ethereal.com/download.html and download either the binary package or the software.

Connect a sniffer to the ELAN when debugging IP Trunk BOOTP set-up problemIP Trunk to OTM problems. Connect the sniffer to the TLAN to debug IP Trunkother supported gateway Call Set-Up problems. Note that the list of supportedgateways includes IP Trunk nodes, ITGT nodes (ITG Trunk 2.x.25 and 2.x.26), BCand nodes within the CSE 1000 Release 2 set of end-points.

Refer to section 3.1 on page 27 for tips using a sniffer.

1.4 IP Trunk and VxWorks shell access

Note:TTY login to the SMC or ITG-P card is recommended via ELAN Telnet sessiinstead of direct serial port connection if you are logging large amounts of datacopying large SYSLOG or OMREPORT files to the console. Using the serialcan result in call loss or worse during periods where the node experiences htraffic levels.

The following access sequence controls logging in to the IPT shell access in geand specifically apply to the IP Trunk application. That is, the majority of the losequences (and many commands) are generic to SMC and ITG-P supportedapplications; however, within this document only IP Trunk application commandsconsidered.

To log in to the IP Trunk shell on the card, the user first connects to the card viaELAN telnet session (telnet to the management IP address) or connects to the debug port. The ELAN has peak speeds in the multi-megabit per second rangethe port has a 9600 bit per second range, and chews card real-time, so use telnwhenever possible.

Issue 1.5.4 IP Trunk 3.0 Expert Level Support Guide Section: 1.405 May 03 Page 15


gin.hichto the>”n this

mpt

rd todhell

leted;sk

re

tor on. The

l-

• Login to ITG> prompt1

Having connected to the application (telnet or faceplate), the card requests a loThe normal administrative login is via a standard username and password (wis not included here for system security reasons). This gives the user accesscard level and the IP Trunk application. The user can identify this by the “ITGprompt. Note that the user can change the passwords using commands withidocument.

• Login to -> prompt

While some of the commands in the remaining sections of this document areaccepted at the ITG> shell prompt, all are accepted at the VxWorks shell pro(->). Use the commandvxWorksShell to access that shell interface. (See thefollowing subsection for more details.)

1.4.1 Connecting to the card’s RS232 Maintenance port

1.4.1.1 Warning

Improper connection of a modem to an IP Trunk capable card can cause the calock up access (i.e. the card CLI cannot be reached by telnet or TTY). The carcontinues to function as expected (i.e. most applications are still running), but the STask stops working correctly. The Shell Task does not become suspended or deif it did, the Task Audit would catch this and reboot the card at the “non-critical tareboot time” (typically, 2 AM is the default time).

The problem can be avoided by ensuring the correct modem configuration befoconnecting to the card. The modem should be configured as below.

Use AT commands (or DIP switches) to:

1. Set the echo off (AT E0)

2. Suppress the result code or select quiet mode (AT Q1)

3. Enable DTR

4. Put the modem in answering mode (AT s0=1)

1.4.1.2 Procedure

For the Pentium card, connect a serial cable either to the (faceplate) P2 connecthe backplane octopus cable or to the faceplate connector, but not both at oncecard’s hardware cannot support two devices connected at once.

1. Development to re-label this as “IPT” is under way, and the prompt could change without notice. If the deveopment is merged prior to an up-issue of the Expert Guide, “ITG>” implies “IPT>”.

Section: 1.4.1 IP Trunk 3.0 Expert Level Support Guide Issue 1.5.4Page 16 05 May 03


or orather,.

ouhehing to

thend

tely

Similarly, for the Media Card the user can connect to either the faceplate connectto a connector on the adaptor (there is no cable pre-connected to the adaptor; rthere is a port to connect a cable to). Again, use one or the other, but not both

The terminal device should be set to 9600, 8, N, 1. Set flow control to “None”(Hyperterm terminology) or a similar setting. If hardware flow control is enabled, ywill experience the condition of being able to see information from the card but tcard won’t respond to any keystrokes; the condition eventually deteriorates to notprinting and no response. If this happens, change the flow control setting back“None”, close the session and reopen it. The card should then respond.

1.4.2 VxWorks shell

As was stated above, many of the commands in this document are only valid fromVxWorks shell. The following example shows how to go from the IP Trunk shell aback.

ITG> vxWorksShell

login: *******password: *******Welcome to the VxWorks ShellWARNING: Data entry errors in this shell could cause loss of service.Use itgShell to return to the ITG shell.value = 3382232 = 0x339bd8 = _shellHistSize + 0x4-> itgShellITG>

ITG> vxWorksShell

login: *******password: *******Welcome to the VxWorks ShellWARNING: Data entry errors in this shell could cause loss of service.Use itgShell to return to the ITG shell.value = 3382232 = 0x339bd8 = _shellHistSize + 0x4-> exitITG>

It is also possible to go from the login shell to the VxWorks shell, and then compleexit the VxWorks and login shell using “Control-C”.

Issue 1.5.4 IP Trunk 3.0 Expert Level Support Guide Section: 1.4.205 May 03 Page 17


e thegr,

ITG> vxWorksShell

login: *******password: *******Welcome to the VxWorks ShellWARNING: Data entry errors in this shell could cause loss of service.Use itgShell to return to the ITG shell.value = 3382232 = 0x339bd8 = _shellHistSize + 0x4-> Ctrl-CVxWorks login:

The appropriate Nortel development and Global Customer Care Service staff havlogin information; it is not included here for security reasons. Note that the strin“*******” was used to indicate user entry, but the real string may be longer or shorteand the password does not echo back to the user.


IP Trunk 3.0 module descriptions Nortel Networks Confidential

cardt

fore,

nesry

m thethead adules

all

yer 2sing the

d toerdleshele Dy of

theet DIP

2 IP Trunk 3.0 module descriptions

This section provides a description of the application modules involved in main functions. The task name, and index, are shown to aid in turning on the relevanlogging.

Note that the modules are not necessarily only of interest when debugging. Therea brief description (the overview) precedes debugging sections to this chapter.

2.1 Overview

The following modules exist within the IP Trunk application. These are the key oonly; a few others exist, but are typically of little or no interest unless looking at vespecific issues.

The modules are listed in “the order of processing messages when received froPBX. That is, the first module to be involved is listed first; the one involved last inmessage flow is listed last. This has no bearing on the task index, which has hnumber of tasks added to the flow as time progressed. This means that newer mohave higher task numbers, even if they are the first module to see a message.

As an example, ISDN did not exist on the ITGT application until 1.5. Therefore,ISDN related modules are higher in index than all modules that existed before.

• Link Access Protocol-D (task name LAPD, index 12)

This task provides the messaging and maintenance interface for the ISDN Laprocessing. The layer 2 function is on the D channel PC card, a small card ua PCMCIA connector and inserted into the front of the Media Card, or insidePentium card.

The SMC or ITG-P card carrying the D channel PC card is sometimes referreas the DCHIP card. This is incorrect, as “DCHIP” stands for “D CHannel ovIP”. The PC card provides the layer 2, and the card provides layer 3, so it hanthe DCH part of the DCHIP, but the IP side is handled by the card “owning” ttimeslot used for the call. That is, if three cards exist in a node that has a singchannel, the D channel will be on one card only, but the IP side may be on anthe three.

Therefore, it is more accurate to say that for the SMC or ITG-P cards that useD Channel on another SMC or ITG-P card, the card with the D channel is th“DCHIP Leader”, and the “DCHIP Leader” and all other cards serviced by thachannel are the DCHIP. However, calling the “DCHIP Leader card” the “DCHcard” is in wide use, and so has to be considered as a “sloppy but acceptedabbreviation” of “DCHIP Leader”. It isn’t quite right, but without the DCHIPLeader there won’t be a DCHIP...


Nortel Networks Confidential IP Trunk 3.0 module descriptions

e Dia thePD

annel

DN the

salyM on

ges to

tateDSP

der;

DNIGCC.

ISDN messages received from the Meridian 1 receive layer 2 handling on thchannel PC card. The messages are passed from the card to the main card vLAPD module. Messages in the reverse direction (IP to PBX) also use the LAmodule, but in this case the message is sent from the main card to the D chPC card via LAPD.

NOTE: LAPD is present only on a DCHIP Leader card.

• Universal ISDN Protocol Control (task name UIPC, index 11)

Provides ISDN Layer 3 processing and encoding/decoding of specific Q.931 ISmessages to the Universal ISDN Protocol messages. Passes messages toIGCC. NOTE: UIPC is present only on a DCHIP Leader card.

• ISDN Gateways Call Control (IGCC – index 13)

Performs tandemming and call control functions. It receives the UUM (UniverUIPE Message) from the LAPD task, extracts the calling number, called partnumber, maps the channel Id to a Follower and passes the message to the TSthe follower card. NOTE: IGCC is present only on a DCHIP Leader card.

• Telephony Signalling Module (TSM – index 0)

Performs H.323 call setup based on digits passed by IGCC. Passes messaNPM.

This module is the core state machine for the IP Trunk 3.0 application. Other smachines exist for the call across a specific transmission medium and for theresources, but this state machine ties all of the other sections together.

• Network Protocol Module (NPM – index 1)

Provides interface to the Radvision H.323 stack API.

• Address Translation Module (ATPM – index 14)

Provides mapping between the called number and the remote IP address.

2.2 Modules key to call related problems

The following modules must be debugged on the card functioning as DCHIP Leathat is, the card with the D channel PC card residing on it.

• Link Access Protocol-D (LAPD – index 12)

Provides the messaging and maintenance interface for the ISDN Layer 2processing (which is on the DCHIP PC Card).NOTE: LAPD is present only ona DCHIP Leader card.

• Universal ISDN Protocol Control (UIPC – index 11)

Provides ISDN Layer 3 processing and encoding/decoding of specific Q.931 ISmessages to the Universal ISDN Protocol messages. Passes messages to theNOTE: UIPC is present only on a DCHIP Leader card.



salyM on

path

ges to

tateDSP

ng”card.

tive

idesthe

es totreatimum

to the

tions.

• ISDN Gateways Call Control (IGCC – index 13)

Performs tandemming and call control functions. It receives the UUM (UniverUIPE Message) from the LAPD task, extracts the calling number, called partnumber, maps the channel Id to a Follower and passes the message to the TSthe follower card.NOTE: IGCC is present only on a DCHIP Leader card.

The following modules must be debugged on the card actually carrying the speechfrom the Meridian 1 to the IP network.


Performs H.323 call setup based on digits passed by IGCC. Passes messaNPM.


• Network Protocol Module (NPM – index 1)

Provides interface to the Radvision H.323 stack API.


Provides mapping between the called number and the remote IP address.

2.3 Modules key to QoS related problems

QoS monitoring is entirely carried out by the Leader card currently active. The “pigoes from the leader to the remote node IP, and the response returns to the leaderSimilarly, the remote node also pings the local node IP, which resides on the acleader.

Since the QoS is determined on a “2 ended” model where the pings from both sare used to calculate the MOS score, only the leader could have information fromremote node pings, so therefore only the leader can do any QoS monitoring.

There is one exception, though. The Leader informs the follower cards of changthe QoS capabilities of a given node, allowing the local ATPMs on those cards tothe remote node as though it was in fall-back when service degrades past the minacceptable threshold.

• Monitor TimeServer (MTS – index 5)

Receives QoS probe packets from remote nodes in the network and passes itMSM for further processing.

• Monitor Server Module (MSM – index 6)

Process the QoS probe packets and emulates the E-model for MOS calcula



des in

ned

r for

lsoave toHIP

le

ly

TP

• Monitor Client Module (MCM – index 7)

Sends the QoS probe packets and the sender/receiver packets to remote nothe ITG Trunk and/or IP Trunk network.


Maps the called number to the remote IP address.

2.4 Modules key to Leader / Follower communication problems

The Resource Manager has leader and follower function. The master table is owby the leader, but the follower RMM handles the queries.

• Resource Manager (RMM – index 2)

Provides resource management. Examples include channel assignment forincoming / outgoing calls, memory management functions, hosts UDP serveinter-card communication, probing/maintenance/recovery of E-LAN / T-LANconnections.

• Common Task (COM – index 16)

Works in conjunction with the RMM.

The IP Socket Server is predominantly DCHIP Leader to DCHIP Follower, but it adoes signalling to the node Leader. Depending on the issue, debugging may hbe done on the leader (scanning the D channel registration table), or on the DCLeader and Follower cards (IP sessions carrying ISDN messages).

• IP Socket Server (IPSS - index 18)

Provides inter-card communication path between DCHIP and Followers.

Note: if this list does not lead to the issue, it may be in the call processing moducalling this function.

2.5 Modules key to T-LAN / E-LAN and inter-task messaging problem

Users need to know which LAN to sniff for which messaging. In general, the onapplications using the TLAN are:

• Real Time Protocol transport

• Real Time Control Protocol transport

• Quality of Service monitoring across the network (on the TLAN, because the Ris also on the TLAN)

• MCDN connectionless message transport



aN

r for

le

ed atill

Its nots the

etion, thatd and

byonly;

p

• Inter-card communications for ISDN are normally over the TLAN, but there isfail-over capability on IP Trunk 3.0 allowing the signalling to switch to the ELAwhen the TLAN fails.

The following tasks are frequently involved in LAN issues.

• Resource Manager (RMM – index 2)

Provides resource management. Examples include channel assignment forincoming / outgoing calls, memory management functions, hosts UDP serveinter-card communication, probing/maintenance/recovery of E-LAN / T-LANconnections.

• Common Task (COM – index 16)

Works in conjunction with the RMM.



Note: if this list does not lead to the issue, it may be in the call processing moducalling this function.

2.6 Modules key to OTM to card communication and configuration problems

When the CONFIG1 and BOOTP files are downloaded, the card must be disablthe Meridian 1 (LD 32, DISC <tn>). These files may be downloaded then, but wnot take effect until the card reboots.

The dial plan information in the DPTABLE may be downloaded to a running card.may be activated either as a function of the download, or manually. The card doeneed to be disabled, although the new data is only used after the application loadnew table.

The software image may be downloaded without disabling the card. On complof the download, the card must reboot for the software to upgrade. Note, thoughan unexpected reboot while in the middle of the download may have unexpectevery destructive effects.

Some of the following modules function fully on all cards and are queried on a cardcard basis. Others are “leader(s) only”. The BOOP file downloads to leaders the other files download to all cards. It is best to assume “debug the module onwhatever card has the issues.”

• Maintenance Administration Module (MAM – index 4)

Provides configuration support by parsing the configuration file and setting uroutes, DSP parameters etc.



e via

so

ard.

ebug

DN

salyM on

es to

• Network Management Module (NMM – index 3)

Provides communication between the card and the craftsperson. This can bOTM or telnet session.

• Operational Measurements Module (OMM – index 8)

Collects the OMM measurements for the card and logs them to the file. It alperforms the trace and logging functionality for the card.

• Simple Network Management Protocol (SNMP – index 15)

Support OA&M via OTM.

2.7 Modules key to DCH problems

D channel problems come in a couple of distinct types.

• ISDN signalling errors. Debug on the DCHIP Leader card.

• Mis-mapping into the correct internal channel. Debug on the DCHIP Leader c

• Intercard messaging errors. Debug on the DCHIP Leader first, and if the IPmessage leaves the application, confirm it reached the destination. Then, don that card.

Note: the first 3 modules are only present on the DCHIP Leader card.

• Link Access Protocol-D (LAPD – index 12)

Provides the messaging and maintenance interface for the ISDN Layer 2processing (which is on the D channel PC card).

• Universal ISDN Protocol Control (UIPC – index 11)

Provides ISDN Layer 3 processing and encoding/decoding of specific Q.931 ISmessages to the Universal ISDN Protocol messages.

• ISDN Gateway Call Control (IGCC – index 13)

Performs tandemming and call control functions. It receives the UUM (UniverUIPE Message) from the LAPD task, extracts the calling number, called partnumber, maps the channel Id to a Follower and passes the message to the TSthe follower card.




Performs H.323 call setup based on digits passed by IGCC. Passes messagNPM.



tateDSP

of

t

ndeis

gged

es to

ives

es to

ives


2.8 Modules key to SSD / A07 related problems

SSD messages (processed by the A07 module) provide signalling that is mostlylittle meaning to the card, unless the D channel fails.

The messages include signals for an analog format seize, acknowledgements,indication that the call has connected, and indication of clearing, as well as faulreporting. These are redundant, given the ISDN signalling.

However, SSD messages also provide signalling about pad levels for transmit areceived, as determined by the Meridian 1 core. The Meridian 1 determines thcorrect pad settings based on the other termination on the switch, and sends thinformation to the card via the SSD message and A07 module.

SSD messaging is often easier to debug from the Meridian 1, but it can be debufrom the card where the channel resides.

• A07 (index 9)

Provides an SSD interface to the M1 via the DS30X Signalling protocol.



This module is the core state machine for the IP Trunk 3.0 application. It drthe SSD interface module, and therefore drives the A07.

2.9 Modules key to DSP related problems

Debug these on the SMC or ITG-P card experiencing the problem.

• DSP Interface Module (DIM – index 10)

Provides the interface to the Telogy DSP API.



This module is the core state machine for the IP Trunk 3.0 application. It drthe DSP interface module and DSPs.


Nortel Networks Confidential Troubleshooting

ing aps

. (Ifhapter,

r

ems

ems

e alled

sues

g

3 Troubleshooting

The following sections contains tips and suggested commands for troubleshootnumber of different types of problems. They also include a small number of steusually key to resolving a problem to try associated with the section problem areathe user needs more detailed debugging, the user should use the appropriate clisted in the section.)

• “3.1 - Using a Network Sniffer” - tips on setting up and using a network sniffe

• “3.2 - General card commands”

• “3.3 - Disk and Directory Commands”

• “3.4 - Network Troubleshooting” - tips and commands related to networkproblems

• “3.5 - Call Related Problem Troubleshooting” - commands related to call probl

• “3.7 - Address Translation Troubleshooting” - commands related to call probl

• “3.8 - D-Channel Related Troubleshooting”

• “3.9 - Backup Leader start-up issues” - issues with prior releases, which havsolution in IP Trunk 3.0 and have not been duplicated since the fix was insta

The following chapters contain more detailed tips and suggested commands fortroubleshooting a number of different types of problems.

• “5 - Debugging the shell”

• “6 - Debugging the node”

• “7 - Call processing debug commands”, including task and message tracing

• “8 - Debugging audio issues” - tips and commands related to voice quality is

• “9 - BIOS / BootROM functionality” - tips and commands related to recoverinfrom boot failure

• “10 - Maintenance Task (Task Monitor Function)”, including task prioritization

• “11 - Patcher Tool Support”

• “12 - Installation and upgrades”

For command details, refer to the applicable appendix.

Section: 3 IP Trunk 3.0 Expert Level Support Guide Issue 1.5.4Page 26 05 May 03

Troubleshooting Nortel Networks Confidential

and/he

IPed ofN,

(ory of

esssired

overP

ce,orate a IPally,

ss; you

3.1 Using a Network Sniffer

A network sniffer is an excellent tool for troubleshooting network devices. Bycapturing exactly what’s sent on the wire and providing decoders for the variousprotocol levels, capture traces often provide solid answers as to why ITG Trunkor IP Trunk cards aren’t communicating, or the source of voice QoS problems. Tfollowing are some tips on using a sniffer with the IPT product.

3.1.1 Connectivity

• A passive hub is helpful when connecting the sniffer at the device beinginvestigated. A passive hub means the sniffer will see the same traffic as theTrunk node since all ports receive the same data. It is best to match the spethe hub to the speed of the SMC/ITG-P network interface - 10BT for the E-LA10/100BT for the TLAN.

• When an active hub or switch is used, you need to configure “port mirroring”a similarly named feature - product dependent) so the switch will send a copall packets on the port of interest to the port with the sniffer connected.

• If the active hub or switch doesn’t support port mirroring or you don’t have accto its management interface, you can insert a passive hub in line with the deport and connect the sniffer to it.

• It can be useful to connect a sniffer at both ends of an IPT to “other device”1

connection that is having problems. Comparing the two capture files may uncnetwork problems such as a router discarding signalling messages or old ARcache addresses in packets.

3.1.2 Sniffer Pro

• Use the capture filters to reduce the amount of captured information (unlesscapturing everything can provide clues to the root of the problem). For instancreate a filter with the relevant card’s TLAN interface (Voice LAN Node IP and/Voice IP) and the IP address of the remote device being debugged. First crenew Profile, then modify the Profile’s Address parameters to the ITG’s TLANaddress and the IP address of the Node IP if the card is the Leader Card. Finselect the filter before starting the capture.

Note:Be sure to select “IP” for the Address Type. If set to “Hardware”, the MAC addreof the endpoints is expected but the program allows you to enter an IP addresswon’t get any indication there’s a problem until you get an “Invalid HardwareAddress” error when you try to capture using the filter.

1. This other device could be IPT, ITGT, IP Peer, IP Lines, BCM, or third party.



ter

for

hich

erd.

the

usinglese files

• Similarly, use the display filters to filter information from a capture file whilenarrowing in on a problem. A new window is created each time an applied filchanges the contents. You can then save just those windows with usefulinformation. The process for creating the filter and selecting it is the same asthe capture.

• After stopping the capture, display it. Select theDecodetab on the expert windowto see the packet decode.

• It is possible to set filters to capture and/or display on certain port addresses wcan be useful when filtering out H.323 Call-Set-Up messages or QoS Probepackets or for tracing both directions of the RTP Voice packets.

• The Matrix tab gives a graphical view of who’s talking to who. Change the uppleft hand pull down menu to “IP” to have the IP address/host names displaye

• TheHost Table tab gives a list of statistics for each host in the capture, while Statistics tab gives overall statistics.

• Ping andTraceroute are available under theTools menu.

• When host names aren’t assigned to network devices, you can create namestheAddress Bookunder theToolsmenu. The names then appear in the capture fiwhere ever the IP address would have appeared. This makes reading the tracfaster than looking at IP addresses. This address book is saved under theDatabasemenu’sAddress Bookentry.



or

r, notlete a

t-up

ful

ity

and

inger

rd)7 or

3.2 General card commands

Refer also to chapters “5 - Debugging the shell” and “6 - Debugging the node” fmore comprehensive debugging information.

Some commands can be used to verify the general sanity of the card. Howeveall can be used in all scenarios. This is especially true if the card cannot compboot-up of the IP Trunk application.

In the event of a failed boot, the user can investigate via the BIOS/BootROM boosequence. For details, refer to chapter 9 - BIOS / BootROM functionality.

Assuming that the card booted, a number of basic sanity items may provide useinformation. The user can typically debug as follows:

• Fail-safe: chapter 5 - Debugging the shell.This includes commands used to debug the shell itself, as well as basic sancommands.

• Follower to leader registration -ldrResTableShow (section B.1.24, pg 158)Verify all the Follower cards have registered with the Ldr. For each missingFollower, check its card state (using itgCardShow), the TLAN cabling and hubthat an entry exists for it in the bootp.1 table.

• Card to DCHIP leader registration -dchipResTableShow (section B.1.9, pg 124)Verify that the Follower cards have registered with the DCHIP. For each missFollower, check the ELAN cabling and hub and verify the correct DCH numbwas configured in OTM for it.

• numNodesInFallbackShow (section B.1.26, pg 160)Prints all the remote IP that are in fallback at a given time.

• swVersionShow (section B.1.42, pg 166)Displays the version of the IPT application running on the card.

• firmwareVersionShow (section B.1.12, pg 135)Displays the version of SMC or ITG-P card firmware. Should be (Media Cabase card version 6.4 and XA version 4.8 or higher, and firmware release 5.higher on the Pentium card.

• set_time yy, mm, dd, hh, mm, ss (section B.2.53, pg 219)Sets the time for both the RTC chip (H/W clock) and the O/S (S/W clock).

• i (section B.1.16, pg 145)Displays a list of all tasks running in the O/S.

• lkup “string” (section B.2.21, pg 186)Displays anything in the symbol table matchingstring (is case sensitive).

• serialNumShow (section B.1.38, pg 165)Displays the card’s serial number.



by

e of

• itgMemShow (section B.1.22, pg 156)Displays the allocated and free DRAM memory on the card.

• mixMemFindAll (section B.2.35, pg 193)Prints information about each buffer from the buffer pool that is currently in usethe application.

• flashConfigShow (section B.2.11, pg 179)Displays the card’s Flash memory configuration.

• showMemConfig - Pentium only (section B.2.58, pg 222)Displays the card’s DRAM memory configuration.

• setLeader “IPaddr”,”gwIPaddr”,”subnetMask” (section B.1.39, pg 165)Configures the card as a Leader and saves it in the NVRAM.

• clearLeader (section B.1.7, pg 122)Configures the card as a Follower and saves it in the NVRAM.

• NVRClear (section B.1.27, pg 160)Erases data from the card’s NVRAM.

• NVRIPSet “IPaddr” (section B.1.29, pg 162)Configures and saves only the card’s ELAN IP address in NVRAM.

• NVRSMSet “subnetMask” (section B.1.31, pg 162)Configures and saves only the ELAN subnet mask in NVRAM.

• NVRIPShow (section B.1.30, pg 162)Displays the ELAN configuration data as stored in the NVRAM.

• resetOM (section B.1.34, pg 163)Writes the current OM counters to disk and resets them to zero.

• Task audit related commands -

— auditRebootSet 0/1 (section B.1.1, pg 120)

— auditRebootTimeSet hh:mm (section B.1.2, pg 120)

— auditShow (section B.1.3, pg 121)

— auditTaskSet [tname|tid],level (section B.1.4, pg 121)

Administration for the card sanity audit task. This requires the highest releasITG-P firmware and at least version 6.4 of SMC firmware.

3.3 Disk and Directory Commands

The following commands are applicable to the card’s file system.

• cd “dirPath” (section B.1.6, pg 122)Change the current working directory.



oingss

e

tatus

d

st.

Note:The VxWorks file system allows you to enter a non-existent directory when dthecdcommand and won’t return an error code. It is only when you try to accea file that you’ll get a -1 returned.

• copy “sourceFilename”, “destFilename” (section B.1.8, pg 123)Copies a file. IfdestFilenameisn’t entered, outputs file contents to TTY display.If the “sourceFilename” is 0, the command takes input from the command lininterface until the user types a “control-d”.

• chkdsk “dev”, repairLevel, entryLevelType (section B.2.4, pg 173)Checks the /C: drive for corruption and can be set to correct errors found. For sonly, repairLevel and entryLenType parameters can be omitted.

• dosFsConfigShow (section B.1.11, pg 134)Displays details about the /C: drive configuration.

• ll (section B.1.25, pg 159)Displays a long format listing of the directory’s contents.

• iosFdShow (section B.2.16, pg 184)Displays all active file descriptors.

• pwd (section B.1.33, pg 163)Displays the current working device/directory.

• mkdir “dirName” (section B.2.38, pg 197)Creates subdirectorydirName in the current directory.

• rm “filename” (section B.2.49, pg 216)Deletesfilename from the current directory.

• rmdir “dirName” (section B.2.50, pg 217)Deletes subdirectorydirName from the directory.

• swDownload “srvrIP”, “uid”, “passwd”, “path”, “fname” (section B.1.41, pg166)FTPs the application binary to the card.

3.4 Network Troubleshooting

The following commands can be useful for debugging ethernet or network relateproblems.

• ping “IPaddr”, numPings (section B.1.32, pg 163)Executes theping command for checking network connectivity to a remote ho

• ifShow (section B.1.17, pg 146)Displays details about the active ethernet interfaces.



• IPInfoShow (section B.1.18, pg 148)Displays the card’s IP configuration information.

• NVRIPShow (section B.1.30, pg 162)Displays the ELAN configuration data as stored in the NVRAM.

• routeShow (section B.1.37, pg 164)Displays the ITG’s host and network routing tables.

• routeAdd “destIPaddr”, “gwIPaddr” (section B.1.35, pg 164)Add a route to the ITG’s route table.

• routeDelete “destIPaddr”, “gwIPaddr” (section B.1.36, pg 164)Delete a route from the ITG’s route table.

• mRouteShow (section B.2.43, pg 202)Displays the routing table’s entries with the ToS and net mask information.

• mRouteAdd “destIPaddr”, “gwIPaddr”, 0xdestNetMask, To, 0(section B.2.41, pg202)Allows adding multiple routes to a location to the ITG’s route table.

• mRouteDelete “destIPaddr”, 0xdestNetMask, ToS (section B.2.42, pg 202)Deletes one of the multiple routes to a location from the ITG’s route table.

• arpShow (section B.2.2, pg 171)Displays the current ARP table.

• arpFlush (section B.2.1, pg 171)Flushes the ITG’s ARP cache.

• icmpstatShow (section B.2.13, pg 181)Displays statistics for the ICMP protocol.

• inetstatShow (section B.2.15, pg 182)Displays all active connections for IP sockets.


• ipstatShow (section B.2.17, pg 185)Displays statistics for the IP protocol.

• tcpstatShow (section B.2.59, pg 223)Displays statistics for the TCP protocol.

• udpstatShow (section B.2.65, pg 240)Displays statistics for the UDP protocol.

• lnIsaBroadcastShow - not applicable, SMC (section B.2.22, pg 187)Shows count of ELAN broadcast messages for each of the last 60 seconds.

• lnIsaShowLostBroadcast = 1/0 - not applicable, SMC (section B.2.24, pg 188)



off).

ages.

off).

This

ofn

. is

also

Enables/Disables the display of ELAN broadcast count messages (default is

• lnIsaBroadcastThreshold = threshold - not applicable, SMC (section B.2.23, pg187)Sets the threshold (default is 40 pkts/sec) for display of ELAN broadcast mess

• lnPciBroadcastShow - not applicable, SMC (section B.2.27, pg 189)Shows count of TLAN broadcast messages for each of the last 60 seconds.

• lnPciShowLostBroadcast = 1/0 - not applicable, SMC (section B.2.29, pg 190)Enables/Disables the display of TLAN broadcast count messages (default isThis value is reset on Power-Down/Reboot.

• lnPciBroadcastThreshold = threshold - not applicable, SMC (section B.2.28, pg189)Sets the threshold (default is 40 pkts/sec) for acceptance of TLAN broadcasts.value is reset on Power-Down/Reboot.

• mbufShow (section B.2.33, pg 192)Displays distribution of mbufs in the IP protocol stack.

• netHelp (section B.2.44, pg 203)Displays VxWorks help screen for most common network commands.

• tlanSpeedSet speed (section B.2.61, pg 225)Forces speed setting (10 or 100BT) for the TLAN interface.

• tlanDuplexSet duplexMode (section B.2.60, pg 224)Forces duplex setting (half or full) for the TLAN interface.

• dummy_trap (section B.2.9, pg 178)Sends dummy SNMP alarm message for one or more ITGnnnn alarms.

3.4.1 General troubleshooting suggestions

Problems on the LAN/WAN can cause issues from basic call set-up to a variety voice quality and user satisfaction issues. The following are some suggestions othings to do to determine if the network is causing problems.

• Make sure the ELAN, TLAN and Node IP addresses are properly configuredEvery card has unique ELAN and TLAN interface IP addresses. The Node IPshared amongst the cards and is programmed for the TLAN interface.

Important: Separate subnets for the ELAN and TLAN interfaces is therecommended configuration for the ITG Trunk release 2.0 or 2.1 card. It is recommended for IP Trunk 3.0. It is possible to define a single subnetconfiguration by un-checking the “Use separate subnets for voice andmanagement” checkbox in the MAT/OTM General Node Properties screen.



the to

nende.t.

the

’son

eired

-P

)?e’t

?

d

Ask

ble.cks

Note that the intention for this configuration is to leave the TLAN cablingdisconnected from the network and all network communication to occur overELAN. Using this mode automatically reduces the trunk network bandwidththe maximum 10BT configuration supported by the ELAN.

— ELAN: (Embedded LAN) - carries maintenance/admin/alarm data betweeOTM and SMC or ITG-P cards and ISL D Channel signalling traffic betwethe M1 CPU (via the configured DCHIP Leader card) and the cards in the noAll ELAN addresses for all cards in the node must be on the same subne

— TLAN: (Telephony or Voice LAN) - carries H.323 (H.225 and H.245) andRTP packet data between IP Trunk nodes. All TLAN addresses must be onsame subnet for cards in the same node.

— CLAN: (Customer LAN) - regular customer LAN for their PCs, etc. The ITGTLAN must be protected from the broadcast traffic that can regularly occurthe CLAN.

— Node IP: on the TLAN subnet; used for Inter-Node communication. Thisaddress is shared by the cards; it is assigned to the TLAN interface of thcurrent Leader and is held by the current Back-Up Leader in case it is requto become the Leader.

• Check the configuration of the router/hub ports connected to the SMC or ITG(see section 3.4.3).

• Check the faceplate indicators on the card and make sure everything is OK:

— For ITG-Pentium:

— Is the green carrier detect LED on (indicating TLAN port detect CarrierSome early ITG-P octopus cables reversed the ELAN and TLAN cabllabels. Unplug both and plug in the TLAN cable; if the green LED doesnlight, try the cable marked ELAN. Correct the cable labels if they arereversed.

— Does the yellow activity LED flash when there’s TLAN traffic to the card

— For SMC (originally called the ITG Trunk 2.1):

— Is the E LED set to 10 Mbps (indicating ELAN is connected to a hub)?

— Is the T LED set to either 10 or 100 Mbps (indicating TLAN is connecteto a hub)?

— Does the A (activity) LED flash when there’s TLAN traffic to the card?

• Get a network diagram of the cards, and all other data devices on the network.the customer how much traffic is on their network, do router statistics showdropped packets, etc. Try to understand which devices are experiencing trouAll? Just a specific subnet? All the time or intermittently? Define the bottlenein the network and understand the routing and QoS policy for the network.



ard)uters,toutes IP

actsmore

t with

ms.ANest

ffic.

toffer.f the

mine

ating.

le inbe

on

ror

• Replacing an SMC or ITG-P card means a new MAC address (from the new cis associated with the existing card’s IP address. Sometimes, with some royou must ping the router interface from the recenhtly replaced card in order speed up the updating of the router’s ARP table. Some routers take tens of minto time out entries in their ARP table, during which time packets to the card’saddress will not arrive on the new card.

• The simplest trunk configuration is to have a single card node where the cardsimultaneously as the Leader and DCHIP Leader card. Errors can occur as cards are introduced in terms of BOOTP file mis-configuration, inter-cardcommunicatoin issues etc., so establishing a single card node first can assisdebugging more involved network issues.

• Run a ping test between the two IP Trunk nodes which are experiencing probleYou can do this from card to card directly, or perhaps configure P.C.s on the TLsubnets at both nodes to remove the Ip Trunk application from the network tcompletely. Log the output. Were any packets lost? Was the delay highlyvariable? These indicate the network may not be suitable for carrying voice tra

• Connect a sniffer to the LAN, close to the card (preferably on the same hub)capture packets going to/from the card. When a problem occurs, stop the sniIf the traces as well as other appropriate information such as the IP address odevices involved are provided to Technology, they can be examined to deterif there is a network problem or a problem with the card itself.

Note:Note, there are potential privacy concerns with this approach since the RTPpackets can be reassembled into audio files (a necessary step when investigvoice QoS problems); you may want to notify users of the packet monitoring

• If after running tests there appears to be a LAN (rather than SMC or ITG-P)problem, ask the customer if there are any QoS mechanisms they can enabtheir network. If it appears to be an IP Ttunk (or trunk card) problem, it shouldescalated following the normal problem escalation process.

3.4.2 RMD errors

Note: RMD errors are only applicable for the ITG-P application as the MAC devicethe Media Card does not report packet errors.

Error messages with the formattLogTask: Info lnPci: lnPci1 RMD error: RMD1 =xxxx indicates a problem on the TLAN interface. The upper byte contains the erinformation and can be decoded as follows:

Bit 15 (MSB): Ownership - 0 = host, 1 = Ethernet ControllerBit 14: ERR - if set there is an error in the packet, bits 13-10 indicate the specificerror type:Bit 13: FRAM - Framing Error - non integer multiple of eight bits in frame.Bit 12: OFLO - Overflow error on DMA or internal FIFOBit 11: CRC - CRC error on frame.



hichtively.d be

See

ble?

ctlyuggedtoe ande

etersng toted if

forrobe to

onork

Bit 10: BUFF - Ethernet Controller could not get a new buffer before FIFO overflowoccurred.

The lower byte can be ignored. Typical values seen for xxxx are 4b05 and 6b04 windicate a received packet(s) with a CRC and Frame error was detected, respecThis error message is usually due to cabling or hub problems. The following shoulchecked:

• Is the hub configured correctly? Ideally the hub is left in autonegotiation mode.section 3.4.3 for details.

• If it's a large system (Opt 51/61/81), is the correct backplane filter installed?

• Is the octopus cable OK? Try swapping with another known good cable.

• Is the ethernet cable connecting the card to the TLAN a known good CAT 5 caTry swapping it with another CAT 5 cable.

• Is the cable between the card and the hub too long?

• Is the hub the IPT's TLAN cable plugged into OK? Try a different port.

One way to isolate the problem is to plug a known good CAT 5 ethernet cable direinto the RJ-45 socket on the ITG's DSP daughterboard (or use an adapter cable plinto the ITG's faceplate TLAN jack (labelled NWK), with the other end plugged ina known good port on the hub. This bypasses the backplane filter, octopus cablexisting LAN cabling. If the RMD error messages stop, then the problem is in thexisting TLAN wiring or backplane filter.

3.4.3 QoS Troubleshooting

The quality of the speech path across the IP network is dependent on many parambut one of the most key is packet loss. The IP Trunk node performs QoS probiand from port 5000 of the IPT Leader card. SNMP alarm messages are generathe pre-defined QoS threshold is not met.

The QoS probes use a weighted average of the round trip delay and packet lossmultiple probe bursts (inter-gap delay of 15 seconds between each new set of ppackets). The result of the QoS probes are maintained for one and half minutesmaintain a constant sliding window for weighted averaging.

Falling below the QoS probe threshold will result in a fallback (on the next call, notthe current active calls) to alternate routing for calls to the node experiencing netwdifficulty. The fallback status of a node can be checked using the“numNodesInFallbackShow” command:

-> numNodesInFallbackShowNodes In Fallback = 1

47.85.2.75value = 1 = 0x1



n the

are

orkview

ross

licks, to a

T/ QoS

re can

If the customers configuration does not support an alternate routing method, theQoS probing should be disabled in MAT/OTM.

If the far end happens to be in fallback and the QoS statistics printed in the alarmquestionable, then the monitor utility can be used.NOTE: Its primary purpose is todebug the network monitor itself and in some cases maybe helpful to view the netwcharacteristics. In general, one should not have to use this in the field except tothe details of the network QoS statistics.

The Network Monitor consists of the following commands.

— monUtility (section B.2.40, pg 199) - for determining what the QoS levelshould be based on measured performance of the network.

— monIPDebugSet “IP.ad.dr.ess”, on_off(section B.2.39, pg 198) - for checkingremote nodes.

Furthermore, detailed analysis of the network must be performed to establish arealistic target for the QoS level (e.g. a QoS level of 4 allows for 0% packet loss aca network). Refer to the NTP.

The impact of packet loss varies, but even single lost packets can cause audible cwhile higher packet loss sounds like choppy speech. Packet loss is usually duerouter discarding the RTP packets when the network is busy.

3.4.4 BandWidth Optimization

Careful note should be taken of the best use of available Bandwidth.

A level of DiffServ is provided by the card by configuring the TOS settings in MAOTM. Note that the TOS value is applied to both the RTP voice packets and theprobe packets (which must follow the same network path as the RTP packets).

Some routers also support RTP header compression across the WAN. This featube enabled on the ITG Trunk card (running ITG2.xx.25 and 26G) by using thefollowing commands:

— rtpPortCompress (section B.2.51, pg 218)

— rtpPortNonCompress (section B.2.52, pg 218)

For IP Trunk 3.0, the commands are still available, but OTM allows the user toprovision the RTP port numbers in much the same manner.

3.4.5 Network Interface - Speed and Mode Settings.

The following should be checked:



er):

sible

e

lexens”

t and

x ords

cket

r the

d to of

• Verify the ports of the hubs/switches they are connected to are configuredcorrectly. They should be one of the following (in highest to least desirable ord

Note:The trunk card’s TLAN interface supports 10BT and 100BT half and fullduplex. The ELAN supports only 10BT half duplex.

— Auto-negotiation - this is the recommended setting. The card’s TLANinterface will autosense the speed and autonegotiate the half/full duplexsetting. Setting the hub or router port to do the same means the fastest posconnection will negotiate without intervention.

— Manual setting: 10BT, half duplex

You cannot manually configure a port on the router/hub to 10BT or 100BT fullduplex and have an error-free connection to the ITG-P or SMC card.

Manual configuration turns off auto-negotiation in nearly every product on thmarket. By definition of the standards, without auto-negotiation, the card willrevert to half duplex operation. This means the router/hub will be in a full dupmode while the card is in a half duplex mode, a situation guaranteed to causpacket loss. If the switch port is set to half duplex and sees lots of “late collisioand “duplicate collisions” or if it's in full duplex mode and sees lots of “CRCErrors” or “runt frames” then odds are it's a mismatch.

• Check the router's statistics to see how much network traffic is on each subneto see the number of packets being discarded.

• Check if there are differences in subnet configurations (i.e. full vs. half duple10BT vs 100BT) if the problem is only happening for some ITG-P or SMC carand not others.

• Check what QoS mechanism is enabled on the router to give priority to the patraffic from the IP Trunk node.

• Try setting the hub/switch for 10BT half duplex operation and check if thateliminates the packet loss messages. If it does, there may be wiring problem osite doesn’t have CAT-5 cable.

3.4.6 Broadcast storms

Broadcast storms on the TLAN or ELAN network the IP Trunk node is connecteeat up resources on the card. The card performs best in a network without a lotbroadcast traffic.



ormn theholdctedfor

f the

o dobe

s co-

o theif they the

For ITG Trunk 2.0 and an ITG-P running IP Trunk 3.0, if you suspect broadcast stproblems, there is a broadcast monitor which can be enabled (independently) oELAN and TLAN interfaces. The monitor prints a message when the defined thresis exceeded. This provides a simple way to monitor a network without being conneto the card at all times: enable the monitor and then review the CURRLOG.1 filesthe threshold messages. The messages have the form:

FEB 12 12:23:27 tLogTask: Info Time 332140 lanais: 1 broadcasts in last secondFEB 12 12:23:27 tLogTask: Info Time 332140 lnPci: 1 broadcasts in last second

The threshold and status of printing variables are reset on power cycle or reboot oITG-P or SMC. See thelnIsaBroadcastShow - not applicable, SMC (section B.2.22,pg 187),lnPciBroadcastShow - not applicable, SMC (section B.2.27, pg 189) andrelated commands for details.

Note that the ITG Pentium card (running ITG2.24.25 and greater) has the ability tphysical level filtering of Broadcasts. This facility is enabled by default and can confirmed by using theitgCardShow command.

The facility can be turned on/off using the following commands:

- lnPciBcastFilterOn - not applicable, SMC (section B.2.26, pg 188)

- lnPciBcastFilterOff - not applicable, SMC (section B.2.25, pg 188)

For the ITG Trunk 2.1 and SMC, Broadcast filtering is done by the microEngineprocessors. The microEngines interrogate every broadcast packet for the 4 IPaddresses that are applicable to the card and if they are, then they will be sent tCore processor for processing. As in ITG-P, a threshold value can be set so thatnumber of broadcasts on the network exceeds this value, they will be dropped bmicroEngines.

3.4.7 Port numbers used by the IP Trunk

3.4.7.1 TCP Ports

Table 1: Predefined TCP Ports

Interface Port use Port Number

ELAN DCHIP Inter-card messaging 6001

TLAN H.225 TCP Port 1720(* Destination port only)



me

ging

3.4.7.2 UDP Ports

The following UDP ports are predefined.

3.4.8 SNMP traps

You can use thedummy_trap (section B.2.9, pg 178) command to verify that theSNMP traps are configured correctly and the receiving device (MAT, OTM or soother trap alarm manager) is receiving the alarms. This sends the alarm withoutcausing any of the side effects that triggering the real alarm may do (e.g. unplugthe TLAN to generate the TLAN loss of carrier alarm impacts call processing).Remember to configure all of the cards in the MAT/OTM Alarm Notificationapplication so the SNMP traps are shown when they occur.

3.5 Call Related Problem Troubleshooting

For “hints”, refer to chapter “7 - Call processing debug commands”.

The following commands can be useful for debugging call related problems.

• itgChanStateShow (section B.1.21, pg 155)Displays the state of the card’s channels.

• h323SessionShow (section B.1.15, pg 143)

Table 2: Predefined UDP Ports

Interface Port use Port Number

ELAN BOOTP Server 67 (on Leader card)

ELAN SNMP 161

TLAN RTP Ports and usage:

* default port range 2300-2362 (2300 + TCID*2)

* compatible with CISCO RTP header compres-sion

17300-17362 (17300 + TCID*2)

TLAN RTCP Ports:

* default port range 2301-2363 (2301 + TCID*2)

* compatible with CISCO RTP header compres-sion

17301-17363 (17301 + TCID*2)

TLAN MCDN Call Independent Messaging: 15000

TLAN Inter-Card Communication: 2001/2002

TLAN Network QoS Monitor Port: 5000



ress,

s of

his

yle

.

s

SM.

using

e

/W

Lists the details of the h323Session for all active channels – originating IP adddestination IP address, call state, codec used etc.

• iptSessionShow [level] (section B.1.19, pg 150)Lists the details of the h323Session for all active channels, with different leveldisplay.

• h323CallTrace (section B.1.14, pg 140)This will print the NPM call trace and help enable the IGCC trace. Note that tis the “polite” access function used to callsetTraceOption channel,outputLocation(section B.2.54, pg 220). Note also the IGCC minimal trace is accessible bfunctionigccAddTrace channel(section B.2.14.1, pg 182). This does NOT enabTSM tracing, though.

• igccAddTrace channel (section B.2.14.1, pg 182)This VxWorks shell command will print the IGCC “message received” trace,provided the user usedh323CallTrace(section B.1.14, pg 140) orsetTraceOptionchannel,outputLocation (section B.2.54, pg 220) to enable the NPM trace first

• tsmSetTraceOption TCID,[0 or !0] (section B.2.63, pg 227)This VxWorks shell command will print the TSM call trace, provided the VxWorkshell commandmixSetLogOpt module, option, level (section B.2.37, pg 195) isused for the TSM first.

• tsmChanShow [level[,channel]] (section B.1.43, pg 167)This login shell command prints basic data about the call as viewed by the T

• itgMsgCtrShow (section B.1.23, pg 157)Various message counters kept by the TSM task on the card can be displayedthis command


• mixSetLogOpt module, option, level (section B.2.37, pg 195)This VxWorks shell command is the “general purpose” state change/messagmonitoring tool.

• Meridian 1 overlays:

— Overlay 32, STAT <card TN>to check the status of a card.

— Overlay 96to enable or disable message tracing.

3.5.1 Channel selection

Note:The following description is included to give a general view of how the M1 Sselects a call’s channel.



onf as

in its toos

is inxist.ple.

d.hendvia

e a

f the

.1.per.can

43.

P

The M1 S/W selects the channel used for outgoing calls through the card basedlinear route selection. As a result it will attempt to use the uppermost member odefined route for outgoing calls. For this reason Leader and DCHIP Leader card(which have additional processing responsibilities over and above normal call-processing) should be configured as the lowest members of the IP Trunk route.

The IP Trunk Leader card uses a Resource Management Module S/W layer todetermine how incoming calls are re-directed to available channels on cards withnode. It emulates the linear mechanism used by the Meridian 1 and will attemptallocate incoming calls to the uppermost channels down to the lowest. It will alsattempt to use up available channels on Followers, followed by Back-up Leaderfollowed by the DCHIP Leader card, before using channels on the Leader itself.

3.5.2 Gatekeeper problems

The majority of problems related to gatekeepers are call processing based, whichsection 7.2.4 on page 64. However, gatekeeper registration issues also may eUnder normal circumstances debugging gatekeeper registration is relatively sim

• UsegkShow (section B.1.13, pg 135) to verify that the gatekeeper is registereThis also prints out much of the provisioning data as it was loaded. Check tH.323 ID, and the IP address (or addresses) of the gatekeeper (or primary aalternate gatekeeper). Corruption in the image on RAM may be recovered nmmAtpmTranTblDnld (section B.2.45, pg 203).

• If the provisioning is correct but the gatekeeper is unregistered, there may bLAN issue. Useping “IPaddr”, numPings(section B.1.32, pg 163) to determinewhether the gatekeeper is reachable.

• If “ping” did not work, trouble-shoot the network.

• If “ping succeeded”, turn on the NPM task tracing (mixSetLogOpt module, option,level(section B.2.37, pg 195) with module 1 - NPM) and look for error messages.If the NPM failed to send a Register Request, the timer may have stopped. IRegister Request was sent, either no response occurred (investigate at thegatekeeper) or a reject came back. Investigate the failure cause.

• Check to be sure that the address is not mistakenly provisioned in the DPTABLEOnly calls to destinations not included in static provisioning use the gatekeeTherefore, including a digit string that preempts gatekeeper resolution of callscause call failure. See “3.7 Address Translation Troubleshooting” on page

• If all else fails, even when the data on-switch is correct sometimesnmmAtpmTranTblDnld (section B.2.45, pg 203) will bring this back, too.

3.6 Audio Quality Troubleshooting

In general, an audio quality problem is one of three things - a DSP issue, an RTsession issue, or a network QoS issue.



r a

sted

a is

that

.1

ed;

pt

For DSP issues, refer to “8 - Debugging audio issues”.

For RTP issues, refer to “7 - Call processing debug commands”.

For network QoS issues, refer to “3.4 - Network Troubleshooting”.

3.7 Address Translation Troubleshooting

An Address Translation Problem indicates either a bad dialing plan table entry omissing IP entry; the latter should be a rare case if the entry is configured anddownloaded to the card, unless there is a bigger problem. The following is a suggesequence of steps to investigate an address translation problem.

• First, check the configuration in OTM to ensure the correct dialplan table datconfigured.

• Check DPTABLE.1 files exists on the card

• /C:/TABLE/DPTABLE.1 - list and make sure the size is non-zero

• copy “dptable.1”,0 – to list the file on the ITG-P or SMC TTY

• Use the following commands to print the various dialing plan tables to checkthey are OK.

— print_ip_table (section B.2.47, pg 210)

— print_npa (section B.2.48.2, pg 212)

— print_nxx (section B.2.48.3, pg 213)

— print_spn (section B.2.48.4, pg 213)

— print_loc (section B.2.48.5, pg 214)

— print_cdp (section B.2.48.6, pg 214)

— print_dsc (section B.2.48.7, pg 215)

— print_tsc (section B.2.48.8, pg 215)

See alsoCaveat - serious danger from provisioning errors within the DPTABLE(section B.2.48.1, pg 212) for some warnings in this area.

• At this point the provisioning (both in the file and in memory) has been validataddress this as a call rpcessing call, usingmixSetLogOpt module, option, level(section B.2.37, pg 195). The correct syntax for tracing at the ATPM is:

mixSetLogOpt 14,1,1

(The support engineer may also need to use the TSM logging - mixSetLogO0,1,1 andtsmSetTraceOption TCID,[0 or !0](section B.2.63, pg 227) where TCIDis the specific channel on the card.)



ishehetion,thatat

n then fort

f thehus the

notver asers the

reeitch

onds

3.8 D-Channel Related Troubleshooting

3.8.1 DCHmenu

The ITG’s DCH Handler is the UIPE application ported from the MSDL card. Thisa menu based debug tool nearly identical to that on the MSDL card. It enables tprinting of info / error messages from the UIPC task and displays the status of tDCH, protocol used, etc. Note that the Enable/Disable functions toggle for a selecso if the menu prints “Enable ….” For an item, then that item is disabled. Enteringmenu item will enable it; the next time the menu prints it shows “Disable …” for thitem.

TheDCHmenu (section B.1.10, pg 126) command will activate the DCHMenu.

3.9 Backup Leader start-up issues

The IP Trunk 3.0 includes an enhancement that stops an apparent cycle reboot obackup leader card. This issue should be resolved. However, it is not unknowsymptoms to be caused by two or more problems, but a fix resolve only the mosprevalent.

Therefore, the following is included.

Problem statement

During power up or reboot IP Trunk card resets the TLAN interface near the end oreset cycle, which momentarily stops transmitting link pulse to the layer 2 switch, ttriggering Spanning Tree Protocol standard learning mode. This interferes withcommunication between Leader 0 and Leader 1 in the IP Trunk node.

While the layer 2 switch carries out the learning, the Leader 1 (backup leader)completes its start-up, and looks for the active leader. Since the layer 2 switch isforwarding packets, the backup leader does not receive a response and takes oleader. However, as soon as the switch comes back, the backup leader discoverror and reboots to clear it.

The basic problem is that intelligent Layer 2 switches default to having Spanning TProtocol (or Cisco equivalent) standard learning mode enabled on all Layer 2 swports. Spanning Tree Protocol is in standard learning mode for at least 20 secafter the Layer 2 switch port is reset, or after the switch port momentarily stopsreceiving link pulse from the IP Trunk card TLAN or ELAN interface.



be

itchaster 2andrds.

r IP

Scope of the problem

The problem affects the interworking of ITG Trunks up to and including release2.x.26G with as a minimum:

• Nortel Networks Baystack 450,

• BPS 2000,

• Baystack 460 Layer 2 switches, as well as

• Cisco L2 switches.

It should not affect IP Trunk interworking with these switches, but is something toaware of “in case of need”.

Non-IP Trunk solution and IP Trunk impact

The solution for ITG Trunk is to disable Spanning Tree Protocol on the Layer 2 swports that belong to the TLAN and ELAN, or to select the Spanning Tree Protocol FLearning Mode (or its Cisco equivalent). In general you must configure the Layswitch ports to allow immediate transmission of traffic between IP Trunk Leader 0Leader 1 TLAN and ELAN interfaces after a powerup or reboot of the IP Trunk ca

As a rough form of robustness exercise, it is worth maintaining this procedure foTrunk 3.0 as well, but should not be required.


Nortel Networks Confidential Potentail provisioning problems

ens,

inkide

goms

toIGO

esento

theve

ing

4 Potentail provisioning problems

4.1 Creating trunks for ESN5

This problem is “erratic” in that it occurs only with certain as yet to be confirmedpackaging combinations; it does not apply to all systems. However, when it happit happens all the time.

IP Trunk 3.0 supports ESN5 capability for the trunk cards. It also allows either wstart or immediate start. This capability applies equally to both the Meridian 1 sand the ITG-P or SMC side.

However, provisioning on certain releases of the Meridian 1 with some packagincombinations blocks adding IT Trunk units to an ESN5 capable route. The symptseen are blockage at a prompt when entering a valid response.

There is a relatively simple work-around. If the user changes “SIGO” in the RDBSTD (standard and not ESN5 signalling), adds the trunks, and changes back to SESN5, the provisioning succeeds. This should be done during off-hours, as themismatch between the Meridian 1 and IP Trunk provisioning will cause any callsduring the period that the SIGO has been changed to fail.

4.2 Problems with downloading provisioning - ContactSet error

When one of several operations leaves a card with the card information “blank”,downloading the data (transmitting data to synchronize, from OTM) may fail. Thoperations include but are not limited to uploading one site provisioning to copy it ianother.

At this time, the user may attempt synchronize the data. However, sometimes transmit indicates “success” in the OTM window but the provisioning may not hasucceeded; typically, the new provisioning was discarded.

The most common sypmtom of this is output on the login screen such as the followexcerpt:

2040 1 1 00:14:12 (SNMP) :services_set: Setting file Lock2040 1 1 00:14:12 (NMM) :Module 4 setting file system lock2040 1 1 00:14:12 (NMM) :itgFileXfer: transfer type: TYPE I2040 1 1 00:14:12 (NMM) :itgFileXfer returning with status OK2040 1 1 00:14:12 (NMM) :fileSize: 9552040 1 1 00:14:12 (NMM) :hostFileGet exiting with status OK2040 1 1 00:14:12 (NMM) :sending fileXferOk message to task 42040 1 1 00:14:12 (NMM) :hostFileGet returning with status 02040 1 1 00:14:12 (SNMP) :ContactSet: The SNMP Value is Invalid2040 1 1 00:14:12 (DIM) :Download codec image completed -DSP# 0, Image Id = 02040 1 1 00:14:12 (NMM) :NMM received file data OK message from MAM


Potentail provisioning problems Nortel Networks Confidential

tion

2040 1 1 00:14:13 (DIM) :Download codec image completed -DSP# 1, Image Id = 02040 1 1 00:14:13 (SNMP) :services_set: Clear file Lock

It is not apparent from this capture, but the system discarded the new configuradata.

One line in particular is key:

2040 1 1 00:14:12 (SNMP) :ContactSet: The SNMP Value is Invalid

This particular error came from the “

The following capture shows the “parent” window for this particular error.

Figure 1 Node configuration window


Nortel Networks Confidential Potentail provisioning problems

sage

us

tot the

nd

ec.t thesec.

Under this window, at the indicated button, is a data entry screen. The error meslisted above occurs when the circled line is left empty.

Figure 2 Contact name entry line

Not all vintages will have this problem; some vintages of IP Trunk are more rigorothan others. However, if this problem occurs in the field, look in all the “contactname” fields of OTM provisioning. There are three areas (four, if gatekeeperprovisioning is used):

• Site provisioning

• System provisioning

• Configuration of the node, provisioning a card (as seen here)

• Gatekeeper provisioning

4.3 Echo cancellation tail delay

One of the design requirements for IP Trunk 3.0 was to allow the OTM applicationset the echo canceller length. This made it mandatory to read the OTM file and secancellation length appropriately.

However, in OTM the default level is 32 msec tail delay. The intended default arecommended length is 128 msec.

OTM for IP Trunk 3.0 allows this value to be set to various lengths including 128 msIt just is not the default. It is recommended that whenever echo is suspected thaservice staff check this parameter in OTM and reset it to 128 msec if it is not 128 m

Note that ITG-Trunk software versions did not use the OTM to set this value.Therefore, this specific issue could not occur.


Debugging the shell Nortel Networks Confidential

ndany

IP thempt,

irectgelt inels.

de:

ble.

5 Debugging the shell

5.1 Introduction

The following commands control aspects of the ITG> shell access in general, aspecifically apply to the IP Trunk application. That is, the login sequence and mcommands are generic to ITG applications; however, within this document only Trunk application commands are considered. While some of the commands inremaining sections of this document are accepted at the ITG> or IPT> shell proall are accepted at the VxWorks shell prompt (->). Use the commandvxWorksShellto access that shell interface.

Note:TTY login to the card is recommended via ELAN Telnet session instead of dserial port connection if you are logging large amounts of data or copying larSYSLOG or OMREPORT files to the console. Using the serial port can resucall loss or worse during periods where the node experiences high traffic lev

Several commands are “generally useful” during the login session. These inclu

• h and command history handling (section B.2.12, pg 180)Displays the last 20 commands entered at the VxWorks shell. Editing is availa

• shellTimeoutGet (section B.2.56, pg 222)Displays the current idle shell timeout value.

• shellTimeoutSet timeout (section B.2.57, pg 222)Changes the idle shell timeout value.

• vxWorksShell (section B.1.46, pg 170)Provides access to the OS (designer debug) shell.

• itgShell (section B.2.20, pg 186)Exit the OS (designer debug) shell and return to the login shell.

• Ctrl-C will return from the vxWorksShell to the card login prompt.

5.2 Password operations

5.2.1 Recovering from a corrupted password

Command:

• shellPasswordNvramClear (section B.2.55, pg 222)


Nortel Networks Confidential Debugging the shell

gingthe

he

ystemd

are.andnal

aard,

eral

Resets the userid and password to the factory default.

In the event the NVRAM becomes corrupted or some other problem prevents login to the card (IP Trunk application) shell, you can reset the password. Break intoBIOS as the card boots up (enterjkl when prompted). Then enter the commandshellPasswordNvramClear(section B.2.55, pg 222). This resets the password to tfactory default. You can then log in and change the password.

This command can also be used from the normal login prompt.

5.2.2 Password modification

Command:

• shellPasswordSet (section B.1.40, pg 165)Changes the ITG> or IPT> shell userid and password.

If the user needs to change the login prompt (recommended for end users for ssecurity reasons) the commandshellPasswordSet(section B.1.40, pg 165) can be useto change the user name and password. This increases node security.


The user may need to query the card status regarding hardware, and loaded softwAlternatively, the user may want to carry out operations dealing with memory use,tasks. Finally, the user may want to look up functions or variables, clear operatiostatistics, and set timers.

These commands are relatively “problem generic”. For example, if a user has problem with signalling, it is useful to be able to query the software loaded on the cetc.

5.3.1 Hardware and software queries

The following commands (in this suggested order) are useful in verifying the genstatus or sanity of the card.

• swVersionShow (section B.1.42, pg 166)Displays the version of IPT application running on the card.

• firmwareVersionShow (section B.1.12, pg 135)Displays the version of card firmware. Should be either 3.2 or 4.0 or higher.

• serialNumShow (section B.1.38, pg 165)Displays the card’s serial number.

• flashConfigShow (section B.2.11, pg 179)Displays the card’s Flash memory configuration.



e

ory

by

onal

ry to

oingss

5.3.2 Memory and tasks

Frequently, tasks may need to be queried. The user may want to determine thmemory usage, to determine the state of memory (or buffer availability).

The following commands (in this suggested order) are useful in verifying the memallocation, and querying task states of the card.

• i (section B.1.16, pg 145)Displays a list of all tasks running in the O/S.

• itgMemShow (section B.1.22, pg 156)Displays the allocated and free DRAM memory on the card.

• mixMemFindAll (section B.2.35, pg 193)Prints information about each buffer from the buffer pool that is currently in usethe application.

• showMemConfig - Pentium only (section B.2.58, pg 222)Displays the card’s DRAM memory configuration.

5.3.3 Operational data and timers

The following commands (in this suggested order) are useful in clearing operatimeasurements or setting the timer clock of the card.

• set_time yy, mm, dd, hh, mm, ss (section B.2.53, pg 219)Sets the time for both the RTC chip (H/W clock) and the O/S (S/W clock).


5.4 Disk and directory commands

The disk directory system should not require repair. However, it is often necessaaccess files on the disk for debugging purposes.

5.4.1 Navigating the file system


• cd “dirPath” (section B.1.6, pg 122)Change the current working directory.

Note:The VxWorks file system allows you to enter a non-existent directory when dthecdcommand and won’t return an error code. It is only when you try to accea file that you’ll get a -1 returned.


Nortel Networks Confidential Debugging the shell

.

ell.

tatus

ion.

• copy “sourceFilename”, “destFilename” (section B.1.8, pg 123)Copies a file. IfdestFilename isn’t entered, outputs file contents to TTY display


• ll (section B.1.25, pg 159)Displays a long format listing of the directory’s contents.

• ls (section B.2.30, pg 190)Displays a listing of the directory’s contents. Only available in the VxWorks sh

• pwd (section B.1.33, pg 163)Displays the current working device/directory.

• mkdir “dirName” (section B.2.38, pg 197)Creates subdirectorydirName in the current directory.

• rm “filename” (section B.2.49, pg 216)Deletesfilename from the current directory.

• rmdir “dirName” (section B.2.50, pg 217)Deletes subdirectorydirName from the directory.

5.4.2 Verifying and sanitizing the file system

The following commands are applicable to verifying the card’s file system, andrecovering from problems.

• chkdsk “dev”, repairLevel, entryLevelType (section B.2.4, pg 173)Checks the /C: drive for corruption and can be set to correct errors found. For sonly, repairLevel and entryLenType parameters can be omitted.



• rm “filename” (section B.2.49, pg 216)Deletesfilename from the current directory. Useful when recovering fromcorruption.

• rmdir “dirName” (section B.2.50, pg 217)Deletes subdirectorydirName from the directory. Useful when recovering fromcorruption.

• swDownload “srvrIP”, “uid”, “passwd”, “path”, “fname” (section B.1.41, pg166)FTPs the application binary to the card. Useful when recovering from corrupt

• cd, rm, copy, ll, ls, pwd, mkdir as needed



, the

ard,ions

5.4.3 Download/upload of files

The user may need to upload trace and log files for user handling. Alternativelyuser may need to download provisioning or control files.


• attrib “filename”,“protection” (section B.2.3, pg 172)This command allows the user to “un-protect” a file on a Media Card prior todownloading to the card.

• ftp from a computer or workstation or OTM server.

If the user needs to send or receive files between a computer or SMC/ITG-P cthe user may ftp in to the card. The ftp commands are “generic”; no extensare needed. However, the user may need to execute theattrib command first toun-protect it,

• swDownload “srvrIP”, “uid”, “passwd”, “path”, “fname” (section B.1.41, pg166)FTPs the application binary to the card.

• cd, rm, copy, ll, ls, pwd, mkdir as needed


Nortel Networks Confidential Debugging the node

This

irectgelt inels.

isted

is stillasedr by

eral

ory.

r,

ny

6 Debugging the node

6.1 Introduction

The following commands provide ways to debug problems in the node status. includes recovering from corruption of the system software stored in RAM.

Note:TTY login to the card is recommended via ELAN Telnet session instead of dserial port connection if you are logging large amounts of data or copying larSYSLOG or OMREPORT files to the console. Using the serial port can resucall loss or worse during periods where the node experiences high traffic lev

Several commands are “generally useful” during the login session. These were lin “5.1 Introduction” on page 49.


The commands are listed in “5.2 Password operations” on page 49.

6.3 Configuration and startup file checking

Sometimes a user needs to ensure that the data based on the provisioning filesvalid. There are files on the hard drive that store the “correct” data, but the data bon this resident in RAM may be changed - either deliberately by user command, oundesired event.

6.3.1 Verify provisioning on the card

The following commands (in this suggested order) are useful in verifying the gensanity of provisioned data based memory on the card.

• itgCardShow (section B.1.20, pg 152).The user may be concerned about the configuration data as loaded into memThe user may verify general configuration data for the card, e.g:

— IP addresses

— whether a card is Leader, Backup Leader, D-channel Leader, or Followe

— whether the D channel PC Card was detected on DCHIP Leader

— the state of ethernet interfaces.

Normally, the user will start with the Leader card and use the command on aother cards that fail to come into service.


Debugging the node Nortel Networks Confidential

il to

e

ave

and

”

m

• ldrResTableShow (section B.1.24, pg 158)The cards, when they come up, must register with the Leader card. If they fado so, the user may use this command to verify all the Follower cards haveregistered with the Leader.For each missing Follower, check:

— its card state (using itgCardShow),

— the TLAN cabling and hub, and

— that an entry exists for it in the bootp.1 table.

• dchipResTableShow (section B.1.9, pg 124)The D channel controls ISDN signalling between the Meridian 1 CPU and thnode. The cards register with the D channel leader, which keeps its activeregistration table on the Leader. The user may verify that the Follower cards hregistered with the DCHIP Leader by using this command.For each missing Follower, check:

— the ELAN cabling and hub and

— verify the correct DCH number was configured in OTM for it.

If carrying out these steps indicates all is well, proceed to checking the memoryremote node status. Else, use the following to recover the node.

6.3.2 Corrupted leader data, but ELAN IP address is correct

This recovery is relatively simple.

• If the provisioning is correct, a simple reboot can revive the card.

— cd into the /C:/BOOTP directory.

— copythe BOOTP file to screen; verify that it looks valid. See “A.4 BOOTP.1on page 117 for format details.

— cd into the /C:/CONFIG directory.

— copy the CONFIG1.INI file to screen; verify that it looks valid. See “A.2CONFIG1.INI” on page 111 for format details.

— cd into the /C:/TABLE directory.

— copy the DPTABLE.1 file to screen; verify that it looks valid. See “A.3DPTABLE.1” on page 114 for format details.

— Use theprint_nxx, print_npa, print_loc, print_spn, print_cdp commands toensure that the information as loaded is valid.

— If all of the provisioning files look correct, the card should recover onreloading.

• If the provisioning files are corrupted, the user may download correct files froOTM. Then a reboot should revive the card correctly.



theress

ds,

s,

t

ackup

ive

r;uent

e

er, a

ince

6.3.3 ELAN information corrupted but provisioning valid

Since the applicable files are valid, the user may be able to recover by rebootingcard. However, for sanity purposes it may be advisable to set the ELAN IP addinformation.

If a straight reboot fails, set the IP address data using the following two commanthen reboot.

• UseNVRIPSet “IPaddr” (section B.1.29, pg 162) to set up the card IP addresallowing the OTM server to access the card (once it is “live”).

• UseNVRSMSet “subnetMask”(section B.1.31, pg 162) to set up the ELAN subnemask data.

6.3.4 ELAN and configuration information corrupted

This is less “pleasant”. The actions vary based on whether there is a leader and bleader, or only a single leader card.

• Single leader card, possibly with followers; leader corrupted.The node is effectively dead. Only a recovery “from the ground up” can revthis node.

— Clear the current provisioning data.UseclearLeader (section B.1.7, pg 122) to configure the card as a Followethis command saves the new status in the NVRAM. Note that the subseqreboot will ignore all of the data.Alternatively, useNVRClear (section B.1.27, pg 160) to erase data from thcard’s NVRAM.

— Delete the provisioning files.

— UsesetLeader “IPaddr”,”gwIPaddr”,”subnetMask”(section B.1.39, pg 165)to reconfigure the card as a Leader. Or, useNVRIPSet “IPaddr” (sectionB.1.29, pg 162) andNVRSMSet “subnetMask”(section B.1.31, pg 162) to setup the ELAN data.

— UseNVRIPShow (section B.1.30, pg 162) to confirm the data.

— Reboot the card.

— Download provisioning from OTM. Reboot again.

• Single leader card, possibly with followers; DCHIP Leader card corrupted.As far as call processing is concerned, the node is effectively dead. Howevrecovery “from the ground up” may be avoidable.Without a DCHIP Leader, no ISN messages can be received from the PBX. Scall establishment is exclusively via ISDN, the node cannot process calls.




der

ed

r;uent

e

se

r

M.

ain.

— UseNVRIPSet “IPaddr” (section B.1.29, pg 162) andNVRSMSet“subnetMask” (section B.1.31, pg 162) to set up the ELAN data.




• Leader and backup leader card, possibly with followers; leader or backup leacorrupted.The card is effectively dead, but the node is still running. “Repair” the damagcard. ALL COMMANDS ARE EXECUTED ON THE FAILED CARD.

— Clear the current provisioning data.UseclearLeader (section B.1.7, pg 122) to configure the card as a Followethis command saves the new status in the NVRAM. Note that the subseqreboot will ignore all of the data.Alternatively, useNVRClear (section B.1.27, pg 160) to erase data from thcard’s NVRAM.


— UseNVRIPSet “IPaddr” (section B.1.29, pg 162) andNVRSMSet“subnetMask”(section B.1.31, pg 162) to set up the ELAN data. Do not uthesetLeader command; it could cause node contention.




• Follower corrupted.The node is slightly less effective, as fewer channels are available. No otheproblems are visible unless the Follower also has the D channel on it. ALLCOMMANDS ARE EXECUTED ON THE FAILED CARD.

— Clear the current provisioning data.UseNVRClear(section B.1.27, pg 160) to erase data from the card’s NVRA

— If the provisioning files are also corrupted, delete the provisioning files.

— UseNVRIPSet “IPaddr” (section B.1.29, pg 162) andNVRSMSet“subnetMask” (section B.1.31, pg 162) to set up the ELAN data.



— Download provisioning from OTM if the data had to be deleted. Reboot ag



vice”, To

ing;de.

ech as:

theat

igate

buffereful

onbeefore

is

e

opsstic

6.4 Remote node status checking

On occasion, calls to a remote node fail because the remote node is “out of serunavailable, an intervening LAN connection has failed, or other similar reasons.investigate this type of issue, the following commands may be used.

• Useping “IPaddr”, numPings (section B.1.32, pg 163) to verify whether the IPaddress is assigned. If the ping fails but the node should exist, check provisionthe IP address may be wrong. If it is correct, check the status of the remote noIf the node is live, proceed to the next command.

• UsenumNodesInFallbackShow(section B.1.26, pg 160) to determine whether thremote node is reachable. If, for example, the command returns an output su


44.11.223.221value = 1 = 0x1->

then there is a fallback case of some sort. If “ping” failed and the node is live,problem is probably in the IP network. If “ping” succeeded, the probability is thsome other error on the card is causing the node to be out of service. Investon that node.

6.5 Memory fault diagnostic commands

Sometimes the memory develops problems such as loss of memory due to leaks,corruption, and so forth. The following commands (in this suggested order) are usin verifying the general sanity of the memory.

• UseitgMemShow (section B.1.22, pg 156) to confirm that the memory allocatiis satisfactory. Typically, the majority of the buffers of a certain size should free. Note that even an idle card has some buffers reserved for use, and thernot idle.

• UsemixMemFindAll (section B.2.35, pg 193) to ensure that all the buffers areactually in the pool. A list of messages in use (and what task “owns” them) provided, allowing the user to validate the buffer allocation.

• UseflashConfigShow(section B.2.11, pg 179) to confirm the overall health of thflash memory. Failure to process the command indicates a faulty flash.Displays the card’s Flash memory configuration.

If the memory is flawed, it may be necessary to “rebuild”. Frequently, the user “drback to square one”. The following sequence can be used, although it is a draprocedure.

• Display the card information:

— itgCardShow (section B.1.20, pg 152).



cardss)r,N

st.

eral

— NVRIPShow (section B.1.30, pg 162)

Displays the ELAN configuration data as stored in the NVRAM.If the data is corrupt, it may be necessary to go to drastic measures. When theis a single node and the boot-up files (including ELAN address for OTM acceare bad, or the card is a Leader and there is a backup card that can take oveclearing the leader role is necessary first. Otherwise, simply setting the ELAdata will suffice, provided the NVRAM (non-volatile RAM) has been cleared fir

• clearLeader (section B.1.7, pg 122)If the IP data is unrecoverable, and the user must clear the leader role, thiscommand is used. It configures the card as a Follower and saves the newprovisioning in the NVRAM, removing all Leader provisioning.

• setLeader “IPaddr”,”gwIPaddr”,”subnetMask” (section B.1.39, pg 165)Configures the card as a Leader and saves it in the NVRAM.

6.6 Node commissioning commands

See alsoInstallation and upgrades (section 12, pg 87).

The following commands (in this suggested order) are useful in verifying the gensanity of the card.

• Boot the card. Log in through the debug port.

• Validate the memory:

— itgMemShow (section B.1.22, pg 156)

— mixMemFindAll (section B.2.35, pg 193)

— flashConfigShow (section B.2.11, pg 179)

• Initialize as leader:

— (Optional:clearLeader (section B.1.7, pg 122) orNVRClear (section B.1.27,pg 160) - card should already be clear)

— setLeader “IPaddr”,”gwIPaddr”,”subnetMask” (section B.1.39, pg 165), orfor a follower:

— NVRIPSet “IPaddr” (section B.1.29, pg 162)

— NVRSMSet “subnetMask” (section B.1.31, pg 162)

• NVRIPShow (section B.1.30, pg 162)

• Reboot.

• Ensure LAN connection up. Telnet in from OTM.

• Provision from the OTM server.

• Reboot.



the

6.7 Disk and directory debugging

The most common fault is a missing file or directory. To discover this, log in to card and use “cd” and “ls” or “ll” to verify directory contents.

The following commands are applicable when debugging the card’s file system.

• chkdsk “dev”, repairLevel, entryLevelType (section B.2.4, pg 173)

• dosFsConfigShow (section B.1.11, pg 134)

• iosFdShow (section B.2.16, pg 184)

• cd “dirPath” (section B.1.6, pg 122),copy “sourceFilename”, “destFilename”(section B.1.8, pg 123),ll (section B.1.25, pg 159),pwd(section B.1.33, pg 163),mkdir “dirName” (section B.2.38, pg 197),rm “filename” (section B.2.49, pg216),rmdir “dirName” (section B.2.50, pg 217)

And, should the software image be missing, use:.

• swDownload “srvrIP”, “uid”, “passwd”, “path”, “fname” (section B.1.41, pg166)

to recover the file.


Call processing debug commands Nortel Networks Confidential

ilityror.

is.M isd thatide totally

emusing

vice.

odethe

sage.

is

7 Call processing debug commands

7.1 Identifying the issue

For audio related issues, refer toDebugging audio issues (section 8, pg 67).

Call processing may fail for a lot of different reasons. These range from compatibissues, to provisioning issues, to resource issues, to software issues, to user erUnfortunately, the problem rarely shows which it really is.

Therefore, the debugging involved usually involves a “divide and conquer” analysAs an example, until the call reaches the “IPT to IP” NPM, debugging at the NPrarely of value, unless the specific test is used to ensure that the call flow reachepoint. On the other hand, since what appears to be a failure at the destination shandle a call may really be an issue at the originating side, it should never be toruled out.

The debugging “recipe” most frequently used to quickly identify at least the problarea involves checking the messaging, and when the area of the fault is found, focon the functional path through the software for a specific event.

7.2 Message tracing commands

To “divide and conquer”, it is mandatory to have a quick “divide” mechanism.Messaging can easily provide this tool.

At all times, this procedure assumes both ends are IP Trunk 3.0. Any otherassumption requires use of the Expert Guide for that device to debug on that de

7.2.1 Eliminate the PBX or Call Server

It is a generally safe procedure to start by assuming that the origination IP Trunk nwould have a quick turn-around if it fails the call. Therefore, look at the tracing ofISDN messages on the Meridian 1, and ask the following trigger questions:

1. Did the SETUP even leave the PBX? (Confirm this; if it did not, continuedebugging on the Meridian 1.)

2. Was the response to the SETUP a RELEASE COMPLETE?

a. If not, it is quite possible that the message reached the IP network.

b. Else, check the cause code. Compare the cause code to the SETUP mes

i. If it indicated “mandatory IE missing” (96 or 0x60; if the extension bit set, 0xE0), check to see which IE is missing.


Nortel Networks Confidential Call processing debug commands

h

gsee

n

on

e

ller.

er

lt.o be

ii. If it indicated “IE content error” (100, 0x64, or 0xE4), check to see whicIE had “strange” contents.

iii. If it indicated “no route to destination” (3 or 0x83), check the provisioninfor the requested number (using print_... as applicable; for example, tothe CDP provisioning type print_cdp).

iv. If it indicated a failure within the IP network and IP Trunk 3.0 applicatiovia “network congestion” (38, 0x26, or 0xA26), “switched equipmentcongestion” (42, 0x2A, or 0xAA), or “temporary failure” (41, 0x29, or0xA9), this may be an IP Trunk problem; if you can rule out the destinaticall server or Meridian 1, look for a failure within the IP Trunk 3.0 toremote gateway area.

3. If a CALL PROCEEDING was received before call clearing, check the remotPBX or Call Server. If it rejected the SETUP, investigate why. If the SETUPnever arrived, investigate the IP Trunk and IP network.

7.2.2 Ensure that the originating side card accepted the call

This presupposes that the call reached the IP Trunk 3.0 application. If a “quickfailure” (SETUP followed by RELEASE COMPLETE) occurred, this is a strongpossibility. If a SETUP was followed by a CALL PROCEEDING and then the cacleared, this may be anywhere from the local card to the remote PBX or Call ServIn that case, it may be better to skip to section 7.2.3 on page 64 first.

Note that whenever debugging a call and the messaging reaches the TSM, thecommandtsmChanShow [level[,channel]] (section B.1.43, pg 167) can be used toverify call data.

1. Did the call get rejected by the layer 3 task?Use theDCHmenu (section B.1.10, pg 126) command and its options to verifymessage flow. If the message reached the layer 3, it should generate anothmessage into the application (a SETUP triggers a CC Setup Indication, forexample). If it triggered a RELEASE COMPLETE instead, determine the fau(Message info is probably more than adequate, although error tracing may alsuseful.)If the message was sent to higher layers, disable this trace and proceed.



PM,

.

ta

ress

le to

erery to

e

the

h.SM

g

2. If the call reached the ISDN handlers and succeeded, or failed to reach the ATthe Telephony State Machine (TSM) is the key suspect.UsemixSetLogOpt module, option, level(section B.2.37, pg 195) to enable tracingThe module to trace is “TSM”, which has an identifier value of “0”. UsetsmSetTraceOption TCID,[0 or !0] (section B.2.63, pg 227) for the specificchannel to get the details in the TSM state machine.If the TSM was not triggered, check D channel to Follower signalling(dchipResTableShow (section B.1.9, pg 124)).Disable tracing when completed by usingmixSetLogOpt module, option, level(section B.2.37, pg 195).tsmSetTraceOption TCID,[0 or !0](section B.2.63, pg227) does not work without the TSM module trace.To ensure the data was valid and transmitted to the TSM, check the TSM dausing “B.1.43 tsmChanShow [level[,channel]]” on page 167.

3. If the message reached the main state machine, did it get processed for addvalidity?Assuming the call proceeded to the ATPM, usemixSetLogOpt module, option,level(section B.2.37, pg 195) to enable tracing address handling. The modutrace is “ATPM”, which has an identifier value of “14”.This trace allows you to determine whether the address translation protocolmodule even received the digits. If it did, it allows you to see whether they waccepted or rejected (and if so, why they were rejected). It may be necessacheck for fallback conditions; the ATPM will not send a call where the QOSprobing forbids it to go.Disable ATPM tracing when completed.

4. If the call reached the ATPM and succeeded, but failed to reach the NPM, thTelephony State Machine (TSM) is the key suspect.Again, usemixSetLogOpt module, option, level(section B.2.37, pg 195) to enabletracing, andtsmSetTraceOption TCID,[0 or !0](section B.2.63, pg 227) to get thedetails in the TSM state machine.The key question is, did the TSM send a message to the NPM? If it did, checkmessaging to see whether it reached the H.323 stack.mixSetLogOpt module,option, level(section B.2.37, pg 195) for either TSM or NPM should show enougAgain, to ensure the data was valid and transmitted to the TSM, check the Tdata using “B.1.43 tsmChanShow [level[,channel]]” on page 167.

5. If the message did not reach the stack, turn on tracing. Useh323CallTrace(section B.1.14, pg 140), for the NPM messaging, andsetTraceOptionchannel,outputLocation(section B.2.54, pg 220), for the TSM messaging, trackinon the specific channel being requested to get more information.

6. If the call reached the NPM, trace it there (see section 7.2.3 on page 64).



. IfP butge 64.

sagete.

is ard.

ereage

retry

e

bugation,on.

n

ed”,

data

7.2.3 Ensure that the call traversed the network

Sometimes the call fails at the destination; other times, it did not even get that farthere is a gatekeeper, the call may stop “after the NPM was asked to send a SETUbefore the SETUP occurred”. For gatekeeper issues, refer to section 7.2.4 on pa

Ideally, the best place to validate the ability to cross the network is to trace the mesarrival at the destination. This may not be possible, if the destinations are remoTherefore, the user may feel free to debug at the originator too.

There are many ways to check messaging at this point. The most authoritativesniffer trace. If this is unavailable, a trace may be generated at the IP Trunk ca

Note:Tracing using on-switch tools can result in output that is difficult to read. This a threshold where the card will provide an indication about the state of messbuffers (including “print to screen” buffers). This level is easily hit on a card,when doing tracing of H.323 messages. If it happens, the user can usually the debugging call.Do this during off hours unless you have no choice.

UsemixSetLogOpt module, option, level (section B.2.37, pg 195) to enable tracing.(Note that you can usemixOptionOn module(section B.2.36, pg 195) to confirm thattracing has been enabled (0 is off, 1 is “to TTY”,...), andmixLevelOn module(sectionB.2.34, pg 193) to check that the trace is showing “all” (1) or “errors only” (0).) Thmodule to trace is “NPM”, which has an identifier value of “1”.

If the message reached the destination device, the best place to continue the deprocess is there. If the message left the originator and did not reach the destincheck within the network. If it left the NPM but not the card, check the RADVisistack. Otherwise, it is on the originator. Look back to section 7.2.2 on page 62

7.2.4 Ensure gatekeeper ARQ succeeded

A SETUP request from the TSM to the NPM may be asking for a gatekeepercontrolled end point. If so, the IP Trunk 3.0 node must send an ARQ (AdmissioReQuest) and receive an ACF (Admission ConFirmed) first.

This is very simple to confirm. Use thegkShow(section B.1.13, pg 135) command toverify that the gatekeeper is running and registered. If this indicates “not registeryou may re-attempt registration by issuing the commandnmmAtpmTranTblDnld(section B.2.45, pg 203), to reload the dial plan file, and especially the gatekeeperwithin it.



theat the

pointhich to

ation

uallyvel.

has

d,

SEt

e IPer 3.

. use

un-

If gkShowstill does not show registration, there is a problem in the provisioning ornetwork. Ensure that the IP address is correct, that the gatekeeper is live, and thgatekeeper is supposed to support this gateway.

Assuming that the gatekeeper and node are registered, an ARQ for a valid end should succeed. It may fail in normal use for a very small number of reasons, wcan be identified by the responses (ARJ - Admission ReJect - to NPM, clearingTSM, cause code in ISDN):

• Remote end point has failed to register with the gatekeeper, or has lost registr(investigate the remote node).

• Invalid number (not provisioned on the gatekeeper).

• Incompatibility detected by gatekeeper (determined exclusively by thegatekeeper).

For most or all other reasons for call failure, a more detailed analysis is needed, usby Nortel GNTS or Field Support staff, but sometimes all the way to the designer le

7.2.5 Ensure that the call left the destination

The call not only has to reach the destination, but for ITGT and IP Trunk nodes itto succeed at call redirection (a SETUP received, CALL PROCEEDING sent,FACILITY with the new IP address sent, and call clearing). If the redirection failethe call failed too.

Note that redirection is not mandatory. A call from an IP Trunk 3.0 node to a C1000 release 2 gateway will not redirect; the remote end point does not use thacapability.

No ATPM handling occurs at the destination. No gatekeeper ARQ is done by thTrunk 3.0. The primary areas to check are the NPM, the TSM, and the ISDN lay

As with the origination side, a mix of the commands:

• h323CallTrace (section B.1.14, pg 140),

• tsmSetTraceOption TCID,[0 or !0] (section B.2.63, pg 227), and

• mixSetLogOpt module, option, level (section B.2.37, pg 195)

provides the ability to monitor the TSM (0) or NPM (1). Turn these off after useLook for any indications of failure (such as calls not reaching the TSM). (Note:h323CallTraceinstead ofmixSetLogOptfor the NPM if possible; it focuses on specificchannels.)

If the call reached the NPM one of two cases is true. Either this is the original,redirected call, or the call was redirected.



n a

atoryloadrk to

, and

may

BX.

For an un-redirected call, this call is to the node IP. The call goes to the RMM(Resource Management Module) for “approval”. The RMM reserves bandwidth ofollower, and accepts the call. Failure to accept the call should only occur if nochannels remain available.

For a redirected call, the call may fail due to codec mismatches. Unless the originand destination can compromise on a codec algorithm (such as G.729) and a pasize (such as 30 msec), the call is rejected. If this happens, reprovision the netwomake codecs compatible.

If codecs are okay, the call should succeed. The messages must reach the TSMbe passed to the ISDN layer 3. If they reach the TSM, turn off themixSetLogOptmodule, option, level monitoring and enableDCHmenu (section B.1.10, pg 126)tracing. (Message info is probably more than adequate, although error tracing also be useful.)

If the message left the DCH, it must have been rejected in some manner by the PInvestigate there.


Debugging audio issues Nortel Networks Confidential

tot the

nd

ec.t thesec.

ysis.

after

8 Debugging audio issues

8.1 Echo

8.1.1 Provisioning advisory

One of the design requirements for IP Trunk 3.0 was to allow the OTM applicationset the echo canceller length. This made it mandatory to read the OTM file and secancellation length appropriately.

However, in OTM the default level is 32 msec tail delay. The intended default arecommended length is 128 msec.

OTM for IP Trunk 3.0 allows this value to be set to various lengths including 128 msIt just is not the default. It is recommended that whenever echo is suspected thaservice staff check this parameter in OTM and reset it to 128 msec if it is not 128 m

Note that ITG-Trunk software versions did not use the OTM to set this value.Therefore, this specific issue could not occur.

8.1.2 “The echo checklist”

This is being discussed as a “step by step” procedure for data collection and analThe procedure involves querying the end user who experienced the problem fordetails. The steps are:

1. Is the tail length set to 128 msec in OTM? If not, does the problem remain setting it to 128 msec?

2. What changed just before echo was noticeable? Record all responses.

3. Collect characteristics of the echo.

— Is it every call or intermittent?

— What are the echo characteristics (noticeable, artifacts, double-talk, etc.)

— Was it consistent throughout the speech or intermittent during the call(approximate duration)?

— If it is intermittent during the call, then is it observed in the beginning of asentence or in the middle?

— Does it happen only at the beginning of a call? If so, for how long?

— What is the perceived volume of echo?

— Does the echo happen on the handset, headset or speaker?


Nortel Networks Confidential Debugging audio issues

still

set?

he

thatnd

lls?

lity

SEd.

us.

the

inet

n to

e

— If the call is transferred to another set type (analog, digital), does the echoappear?

— What happens to the echo when the receiver of the call unplugs the hand

4. Is it one user or many users? If one user, list any specific characteristics of tvoice.

5. Call scenario with network diagram - capture exact call flow for the scenariosreport echo, i.e. the path including the interim hops between the originating aterminating parties.

— What units are involved in the call (e.g. etherset, TDM set, trunk, PSTN)?

— What kind of set is involved at the far end?

— Is it calls in both directions or one direction?

— Is the echo occurring on local, internal, long distance calls or all types of ca

6. Collect other symptoms. This is anything out of the ordinary such as bad quaof sound, bug messages, call drops, one-way speech...

7. Check clocking status. This may be needed on both the Meridian 1 and a Cserver, as echo can be caused at any point in the call; all should be confirmeLoad overlay 60.On CSE system or small system check status on SCSK:

SCSK 0

This must be locked to the IP daughterboard port for correct performance.On a large system: SCSK nLocked to primary reference listed for “n” (if n > 0).On large system similar commands from ld 60 can be used to check clock statAlso, check the log for slippage messages:

DTA0028 <loop> DTA0026 <loop>

Use the following command sequence on a large system to lock the clock toappropriate source, if required:

ld 60 TRCK PCK n

Where n is 0, 1, 2... This will lock the clock to the primary reference.For CSE1K systems, the command is different. use:

TRCK PLLn

Where n is 0, 1, 2, 3, 4, corresponding to the media gateway expansion cabcontaining the IP daughterboard currently locked to the primary reference.

If set to free run, confirm that the network is isolated (i.e. there is no connectioPSTN). If two switches are in the private network then one side has clockcontroller set to FREE RUN and the clock on the other switch is locked to thPrimary Reference. The clock that is in FREE RUN in an isolated networkbehaves like a Central Office for that Network.



.

server

re

the

15.

or the

tup.

8. Check the Call Server and/or Meridian 1 s/w load for every endpoint involved

9. Are all the necessary patches loaded? On CSE 1000 Rls 2.0 systems the callrequires the following patches:

— MPLR17320 only for customers other than North America

— MPLR17320+MPLR17313 for North America

10.Check the codec configuration for each endpoint.

11.Get the IP Trunk, IP Peer, IP Line s/w load for all trunk or line units involved.

12.For both IPT and IPL, is the node one or more ITG-Pentium card, one or moSMC card or both?

13.Check with component primes for echo or loss-plan related patches.

14. Is the system using dynamic loss plan (this should be “yes” for endpoints onCSE1K 2.0 and IP Trunk on Succession 1000 release 3 only)?

15. If using the dynamic loss plan and the site is not in North America, check tableNTP number: 553-3023-102Prompt order in LD73:

>ld 73 REQ prt TYPE dti FEAT pad PDCA 15 TNLS (enter) DTI/PRI PDCA ONP 8 17 DSET 8 18 OPX 6 20 DTT 0 20 SDTT 0 20 DCO 4 19 DTO 3 19 VNL 0 20 SATT 3 19 ACO 3 20 ATO 3 19 PRI 0 20 PRI2 0 20 XUT 3 20 XEM 4 20 BRIL 0 0 BRIT 0 20 WRLS 3 19

Please note that these values will be changed after the echo patch is installedsame changes get submitted to Project 26 stream.

16. If the echo can be duplicated, check DSP settings on the host during call se



n the

ario, the

ndand

Type XspySetLevel 0,2 from the vxWorks prompt on IPL cards. Look at gainsettings first:

OCT 07 20:21:22 tMVX_XSPY: Info 0024617570 - DIM: 7:3, Tx=’SET_RX_GAIN’(43) gain=0xFFF8 OCT 07 20:21:22 tMVX_XSPY: Info 0024617571 - DIM: 7:3, Tx=’SET_TX_GAIN’(42) gain=+4, inGain=+0

Check the values against the Dynamic or Static Loss Plan tables depending oCS load. To turn traces off type XspySetLevel 0,6

17.Tandems are a major source of echo. If there is an analog trunk in the scenthen check overlay 14 TIMP & BIMP prompts. Characteristic impedance ofanalog trunks may not have been provisioned correctly.

18.Check Table 1 from the loss plan NTP, if PRI is involved. The NTP number aname: 553-2201-181, Meridian 1 International Loss and Level Plan, Planningengineering.

Table 3: Table 1 default values for NA customers:

Prompt Entered value (Tx) Entered value (Rx)

REQ prt

TYPE dti

FEAT pad

PDCA 1

TNLS

DTI/PRI PDCA

ONP 6 0

DSET 6 0

OPX 6 0

DTT 0 0

SDTT 3 0

DCO 3 0

DTO 0 0

VNL 6 0

SATT 6 0

ACO 6 0

ATO 6 0

PRI 0 0

PRI2 0 0



t

it isges.

r the

itale,will

19.To check what values are written to the DTI/PRI card:

a. PDT> crg <tn> (This provides the address of unprotected line block) SLOOP TN SLOOP 2 0 0 0 * 000008 EQPD CUST 0 PBLK 00066CA4 UBLK 001A95A8

b. pdt> p 001A95A8, 20 View the content of the first 32 words. 001A95A8 : 001A7673 0000EAD0 00000000 00000000 0000000000000200 00000008 00000000 001A95B0 : 00000000 00002000 00000000 000003000 0000000000000000 00000016 00000000 001A95B8 : 00000000 00000001 00000001 00000000 0000000000000000 00000000 00000000 001A95C0 : 00000000 00000000 00000000 00000000 0000000000000000 00000000 00000000

c. Decode the 11th word using the following format: DTI_PAD_SEND (11,6,5) DTI_PAD_RECV (11,11,5)

This word will be set only for the digital trunk involved in the call. It will nobe set for IP sets or VGWs or analog trunks.In order to check the pad values received by the VGMCs (IPL application)possible to turn on syslog messages for tVGW task and look for pad messa

20.There may be another point worth checking in case it was a new installation, ocustomer happened not to have configured any digital trunks on their systemalready. In this case it is necessary to go to LD73 and manually create DigData Block (DDB) first. It will create tables 1 and 15 automatically. Otherwisthere will be no table 15 on the system and each call involving DSP resourcescause an error message BUG5369 being printed.To create the DDB block in LD73:

REQ new TYPE ddb TRSH 0

(enter <CR> for all other prompts to accept the defaults)

21.Does turning off the sidetone on the internet telephone (if involved) have anyeffect?

XUT 6 0

XEM 3 0

BRIL 0 0

BRIT 0 0

WRLS 0 0

Table 3: Table 1 default values for NA customers:

Prompt Entered value (Tx) Entered value (Rx)



ling

P.

nd

P.

-> DsetSideToneEnable = 0

(resets to 1 on card reboot)

22. If the echo is happening mainly with long distance calls, make a call using a calcard for a different carrier and see if the problem disappears.

8.2 Debugging, other problems

If the signalling succeeded, the most probable issues are with the speech path.Normally, these can be either DSP issues or session issues.

• Do I have a session?

— Confirm that the NPM really set up a call. Useful commands includeh323SessionShow (section B.1.15, pg 143), andiptSessionShow [level](section B.1.19, pg 150).

— Confirm that the TSM agrees. Useful commands includetsmChanShow[level[,channel]] (section B.1.43, pg 167).

• Is there a one way speech path?

— Repeat the call and monitor messages to and from the DSPs. Usefulcommands are:dimPrintChannelInfo TCID (section B.2.7, pg 176) to confirm the channelsreceived the right information,TsmDspStat = 1/0 (section B.2.62, pg 226) to turn on and off additionalmessage flow tracing (for the DSPs), and the assortedtsm_stat_req commands (section B.2.64, pg 228) to investigatefurther.

— Confirm that the TSM is actually requesting the right actions from the DSUseful commands includemixSetLogOpt module, option, level (section B.2.37, pg 195), andh323CallTrace (section B.1.14, pg 140).

• Do we have a session but NO speech path?

— Repeat the call and monitor messages to and from the DSPs. Usefulcommands are:dimPrintChannelInfo TCID(section B.2.7, pg 176) to confirmthe channels received the right information,TsmDspStat = 1/0(section B.2.62,pg 226) to turn on and off additional message flow tracing (for the DSPs), athe assortedtsm_stat_req commands (section B.2.64, pg 228) to investigatefurther.

— Confirm that the TSM is actually requesting the right actions from the DSUseful commands includemixSetLogOpt module, option, level(section B.2.37,pg 195), andh323CallTrace (section B.1.14, pg 140).



useit wasthisuser

oughmanyoads,has

for

t all

tard

t all

tard

— Check that we are not in fax mode for a voice call. Fax tone can briefly caa loss of speech path, but the call recovers once the card determines thatnot really fax. However, during the interim, there is no speech path. If is the case, consider relocating any fax or modem devices from close to thewho suffered the fax switch-over.

Assuming that the session is available, the tracing must be at the DSP level. Alththe commands applicable have been made available for the user, there are too variables (card types and releases, IP Trunk software application vintages, DSP letc.) to make it practical for first line support to directly use them. Unless the userhad experience with these commands as directed by Nortel personnel (GNTS, example) it is advisable to request help.

With that said, several commands can help a user debug problems.

• For echo cancellation issues, the user may wish to use:

— DimECStat = 1/0 (section B.2.6, pg 175) to capture performancecharacteristics when a call completes

— one or more of thetsm_stat_req commands(section B.2.64, pg 228) to captureperformance characteristics mid-call. The first two are the most useful, bu5 have value. Note:TsmDspStat = 1 is required.

- tsm_stat_req_rx_tx TCID or reqRxTx TCID (section B.2.64.3, pg 234)This command is very useful for tracking data about a specific call. Iincludes most information, although the quantity of data may be awkwfor a person not specializing in the data stream.

- tsm_stat_req_error TCID or reqError TCID (section B.2.64.2, pg 232)This displays whatever errors are currently being detected.

- tsm_stat_req_ecdbg TCID or reqECDbg TCID(section B.2.64.1, pg 229)This displays current echo canceller parameters.

• For other audio issues, the user may wish to use:

— dimPrintChannelInfo TCID (section B.2.7, pg 176) to capture configurationdata and current values used

— TsmDspStat = 1/0 (section B.2.62, pg 226) to capture performancecharacteristics when a call completes

— one or more of thetsm_stat_req commands(section B.2.64, pg 228) to captureperformance characteristics mid-call. The first two are the most useful, bu5 have value. Note:TsmDspStat = 1 is required.

- tsm_stat_req_rx_tx TCID or reqRxTx TCID (section B.2.64.3, pg 234)This command is very useful for tracking data about a specific call. Iincludes most information, although the quantity of data may be awkwfor a person not specializing in the data stream.



- tsm_stat_req_error TCID or reqError TCID (section B.2.64.2, pg 232)This displays whatever errors are currently being detected.

- tsm_stat_req_ecdbg TCID or reqECDbg TCID (section B.2.64.1, pg 229)

- tsm_stat_req_tele_levels TCID or reqTeleLevel TCID(section B.2.64.4, pg236)

- tsm_stat_req_vp_delay TCID or reqVpDelay TCID (section B.2.64.5, pg238)


BIOS / BootROM functionality Nortel Networks Confidential

usent.

g thening

ted,

eee IPok at

9 BIOS / BootROM functionality

9.1 Overview

Note:The minimum ITG-P firmware release for IP Trunk 3.0 is 5.7. The minimumrelease for the SMC is 6.4, and 6.5 is recommended.

Sometimes the user is unable even to enter the shells. At this time, the ability toBIOS (Pentium) and BootROM (Media Card) capabilities can be critically importa

The Pentium cards boot using the card’s BIOS code. The Media Card boots usinBootROM code. During the boot sequence of the Pentium or a Media Card runversion 5.0 of the BootROM, the message“Enter jkl to force boot from BIOS ROM”prints. For the Media Card at release 5.2 of the BootROM the following is prin“Enter jkl to force boot from BootROM vxWorks prompt.”.

Typing jkl at that point causes the card to load the ROM’d version of VxWorks (sbelow). The IP Trunk application is not loaded, so commands implemented in thTrunk code are not available, but the basic VxWorks commands can be used to lothe /C: drive, etc.

Figure 3 Aborting the boot procedure to log in from BIOS (Pentium example)

ITG Firmware Rls 4.08051XA Firmware Ver 9.0(Pentium) 9th June 1999(C) Nortel Networks Inc., 1996-199932K External RAM detectedAll FPGAs are configuredNo dongle detected8K DPRAM detected

Bank 0 Checksum - AFBEHSuspend Power Signals O.K.¸Pentium(R) II Processor. L2 Cache EnabledJumping to vxWorks...ZYXWVURMemory Test Completed OK

BIOS ROM Pentium (PC BIOS) Version 1.2Copyright: Nortel Inc., 1999-2000

Memory Config: 08080808Memory Size: 0x04000000PCI Chipset Init DoneEnter jkl to force boot from BIOS ROMBooting from BIOS ROM

Loading code from address: FFF80000

Enter jkl now


Nortel Networks Confidential BIOS / BootROM functionality

Figure 4 Aborting the boot procedure to log in from BootROM (Media Card example)

MC Firmware Rls 6.48051XA Firmware Version 4.8 26 May 2002(C) Nortel Inc. 2001EPLD Version: 3.032K External RAM detected8K DPRAM detectedAll FPGAs are configuredNo dongle detected

Bank 0 Checksum - A6FBHSRAM test okaySDRAM Addr test okaySDRAM blank overEarly serial debug initialized

VxWorks System Boot

Copyright 1984-1998 Wind River Systems, Inc.

CPU: IXP1200Version: 5.4BSP version: 5.0Creation date: Nov 22 2001, 18:21:11

Enter jkl to force boot to BootROM vxWorks promptjklUncompressing Default vxWorks image .... Complete

Enter jkl now

BSP version 5.0: BootROM 5.0



Jumping to 0x1000Early serial debug initializedSetting tLogTask priority to 150Found device : Cirrus CL-PD672xcisGet : pcCard recognized0x3affe64 (tRootTask): PC Card Detected: Socket 0PC Card Detected: Socket 1cisGet : pcCard recognizedipMethodInit, gIPMethod = 2IP Address from NVRAM: 47.11.217.55IP Data in NVRAM Valid, Boot Line updated IP Address:47.11.217.55 Gateway Address:47.11.217.1 Subnet Mask::fffffe00Host Name: bootHostTarget Name: vxTargetUser: target

MAC Address for Port 0 is : 00:60:38:bd:fb:31

Initializing SemaphoreSysConf: uEng_intConnect to pktHandlingIsr.0 symbols bound.Load uCode from buffer Status : Return SuccessStarting Microengines.0x3affe64 (tRootTask): Loading MAC_21440...0x3affe64 (tRootTask): mac21440Load: Init String[0] NULL: ixpMac0x3affe64 (tRootTask): Loading MAC_21440...0x3affe64 (tRootTask): MAC 21440 String : Processed all arugments0x3affe64 (tRootTask): mac21440InitMem: Net Pool ID is 532084960x3affe64 (tRootTask): Done loading mac21440...0x3affe64 (tRootTask): mac21440Start: Starting port 0interrupt: ixpMac0 carrier upinterrupt: ixpMac1 carrier up0x3affe64 (tRootTask): TLAN set to 10BaseT Operation0x3affe64 (tRootTask): TLAN set to Half Duplex Operation0x3affe64 (tRootTask): ELAN set to 10BaseT Operation0x3affe64 (tRootTask): ELAN set to Half Duplex Operationinterrupt: ixpMac0 carrier downinterrupt: ixpMac0 carrier up



lly
This can be useful when a problem on the card prevents the application from fubooting. Examining the state of the NVRAM or /C: drive configuration files mayprovide clues as to why the application isn’t booting.
MAC Address for Port 1 is : 00:60:38:bd:fb:320x3affe64 (tRootTask): Loading MAC_21440...0x3affe64 (tRootTask): mac21440Load: Init String[0] NULL: ixpMac0x3affe64 (tRootTask): Loading MAC_21440...0x3affe64 (tRootTask): MAC 21440 String : Processed all arugments0x3affe64 (tRootTask): mac21440InitMem: Net Pool ID is 521089080x3affe64 (tRootTask): Done loading mac21440...0x3affe64 (tRootTask): mac21440Start: Starting port 10x3affe64 (tRootTask): TLAN set to 10BaseT Operation0x3affe64 (tRootTask): TLAN set to Half Duplex Operation0x3affe64 (tRootTask): ELAN set to 10BaseT Operation0x3affe64 (tRootTask): ELAN set to Half Duplex Operationinterrupt: ixpMac1 carrier downinterrupt: ixpMac1 carrier upAttached TCP/IP interface to ixpMac unit 1Attaching network interface lo0... done.0x3affe64 (tRootTask): WARNING: mac21440MCastAddrAdd called. addr=0x3aff558NFS client support not included.

Adding 4664 symbols for standalone.

]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] (R) ] ]]]]]]]]] ]]]]]] ]]]]]]]] ]] ]]]] ]] ]]]]]]] ]]]]]]]] ]]]]]] ] ]] ]]]] ]]] ]]]]] ] ]]] ] ]]]] ]]] ]]]]]]]]] ]]]] ]] ]]]] ]] ]]]]] ]]]] ]]] ]] ] ]]] ]] ]]]]] ]]]]]] ]] ]]]]]]] ]]]] ]] ]]]] ]]]]] ] ]]]] ]]]]] ]]]]]]]] ]]]] ]] ]]]] ]]]]]]] ]]]] ]]]]]] ]]]]] ]]]]]] ] ]]]]] ]]]] ]] ]]]] ]]]]]]]] ]]]] ]]]]]]] ]]]]] ] ]]]]]] ] ]]] ]]]] ]] ]]]] ]]]] ]]]] ]]]] ]]]]]]]] ]]]]] ]]] ]]]]]]] ] ]]]]]]] ]]]] ]]]] ]]]] ]]]]] ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]]]]]]]]]]]]]]]]]]]]]]]]]]] Development System ]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]]]]]]]]]]]]]]]]]]]]]]]]] VxWorks version 5.4 ]]]]]]]]]]]]]]]]]]]]]]]]]] KERNEL: WIND version 2.5 ]]]]]]]]]]]]]]]]]]]]]]]]] Copyright Wind River Systems, Inc., 1984-2000

CPU: IXP1200. Processor #0. Memory Size: 0x3b00000. BSP version 5.0.

->



C:file

s can

wille a

’t

9.2 Accessing the /C: drive file system

For IP Trunk 3.0 on the Pentium card, the card boots into the BIOS before the /driver Flash file system is mounted. This is not the case for the Media Card. Thesystem must be initialized and mounted before any of the file system commandbe used. To check if the file system is available, use the commanddevs. Notice thatthe BIOS prompt in IP Trunk 3.0 for the Media Card is “->” instead of “BIOS”.

BIOS> devsdrv name 0 /null 1 /tyCo/0 1 /tyCo/1 5 host: 6 /pty/telnet.S 7 /pty/telnet.Mvalue = 25 = 0x19

The Pentium card may or may not have the /C: drive mounted; the Media Card mount the drive without user intervention. Therefore, un-mounted /C: drives arPentium specific issue.

If the entry /C: isn’t shown when thedevscommand is issued, then the /C: drive isnmounted. To mount it, enter the commanddosFsCdriveTffsDrv thencd to the drive.Commands likedosFsConfigShow will then work as demonstrated below:

BIOS> dosFsConfigShowNot a dosFs device.value = -1 = 0xffffffff = __func_taskRegsShowRtn + 0xffe2c6ab

BIOS> dosFsCdriveTffsDrv/C: drive (Flash Chip) is TrueFFS formatted/C: drive (Flash Chip) is an available dosFs file systemvalue = 57 = 0x39 = '9'

BIOS> cd “/C:”value = 0 = 0x0

BIOS> dosFsConfigShowdevice name: /C:total number of sectors: 7695bytes per sector: 512media byte: 0xf8# of sectors per cluster: 4# of reserved sectors: 1# of FAT tables: 2# of sectors per FAT: 6max # of root dir entries: 240# of hidden sectors: 1removable medium: falsedisk change w/out warning: not enabledauto-sync mode: not enabledlong file names: not enabledexportable file system: not enabledlowercase-only filenames: not enabledvolume mode: O_RDWR (read/write)



the

the

ver,with

the

available space: 2854912 bytesmax avail. contig space: 1935360 bytesvalue = 0 = 0x0BIOS>

It can also be useful to go into the /C:/CONFIG directory and view the contents ofCONFIG1.INI and BOOTP.1 files via the copy command.

9.3 Viewing NVRAM contents

Some card bootup problems are caused by invalid data in the NVRAM. To viewcontents from the BIOS, use the commandNVRIPShow.

-> NVRIPShowIP Address from NVRAM: 47.11.217.54IP address : 47.11.217.54Gateway : 47.11.216.1Subnet Mask: 255.255.254.0Set as Leader.Set to use IP address parameters in NVRAM.value = 43 = 0x2b = ’+’->

9.4 BootROM compatibility levels

The BootROM and BIOS on the SMC is not fieldupgradeable.

Users are required to upgrade to “Media Card Firmware Release 6.4” and it isrecommended that they upgrade to “Media Card Firmware Release 6.5”. Howealthough cards with MC release 6.5 are being shipped with SMC BIOS 5.2, usersBIOS version 5.0 do not need to upgrade.

At boot time, the system prints a line indicating the BSP version. This indicatesBIOS level. The following pairings are supported for IP Trunk 3.0:

• Firmware Release 6.4 with

— SMC BIOS 5.0

— SMC BIOS 5.2

• Firmware Release 6.5

— SMC BIOS 5.0

— SMC BIOS 5.2



s list.

OS

ard,

ame

9.5 BIOS / BootROM Commands

Most of the low-level VxWorks commands are available at the BIOS prompt, plusome IP Trunk application or card specific commands. The following is a partialUse thelkup command to verify if a command you need is available.

For command details of all IP Trunk specific commands, refer to the appropriateappendix.

1. Set the Network connection in the ELAN interface port.

If the leader information has been corrupted, the card can be “revived” from BIor BootROM in much the same way as in the ITG> or -> shell.

a. Media Card and Pentium card

-> nvramLeaderClr -> setLeader “ELAN Port Ip Addr”, “ELAN Port GW”, “ELAN Port SM”

b. Media card onlyFor the Media Card card, there is an alternate procedure, listed here.

-> ixpMac1_eraseIP - erase the ixpMac1 (ELAN) IP information stored in NVRAM. -> ixpMac1_IPMethodSet <n>

Note: n=1. Network interface always get IP addr from BOOTP, Follower Role n=2. Network interface always get IP addr from EEPROM, Leader Role

-> ixpMac1_progIP “ELAN Port Ip Addr” -> ixpMac1_progGW “ELAN Port GW” -> ixpMac1_progSubnetMask “ELAN Port SM” -> nvramLeaderSet

Note that the four commands {ixpMac1_progIP, ixpMac1_progGW,ixpMac1_progSubnetMask, nvramLeaderSet} combined is the same assetLeader command.

c. Pentium card onlyFor the Pentium card, there is an alternate procedure parallelling the Media Clisted here.

-> lnIsa_IPMethodSet <n> Note: n=1. Network interface always get IP addr from BOOTP, Follower Role n=2. Network interface always get IP addr from EEPROM, Leader Role

-> lnIsa_progIP “ELAN Port Ip Addr” -> lnIsa_progGW “ELAN Port GW” -> lnIsa_progSubnetMask “ELAN Port SM” -> nvramLeaderSet

Note that as with the Media Card the four commands {lnIsa_progIP,lnIsa_progGW, lnIsa_progSubnetMask, nvramLeaderSet} combined is the sas setLeader command.

2. Disk commands



ad

ion)

tory

the

um

If the disk is seriously corrupted, you can reformat the drive and then downlofresh software.

-> reformatCdrive -> reformatAdrive

Note:“/C:” referred to internal PCMCIA disk“/A:” is PCMCIA card inserted into the face plate slot.

3. Software download commands

Different requirements (such as upgrading the software, recovery from corruptmay require re-loading software on the card.

To load from a remote IP server, use:

-> swDownload “<server IP>”,”<userId>”,”<passwd>”,”<dir-path>”,”<file>”

For example, if user fred, password derf, wanted to get IPT30052.sa from direc/C:/images on the server at 11.22.33.44, the command would be:

-> swDownload “11.22.33.44”,”fred”,”derf”,”/C:/images”,”IPT30052.sa”

To load from the PCMCIA card faceplate port, use:

-> swCopy “/A:/<file>”

For example, if the user wanted to get IPT30052.p2 from the PCMCIA card, command would be:

-> swCopy “/A:/IPT30052.p2”

Note that commands used for the A: drive check the file format, CRC checksand file size for the Media card.

A partial listing of other useful OS and OS available commands includes:

• cd

• pwd

• ll

• copy

• ifShow

• routeShow

• routeAdd

• ping

• i



• lkup

• upgradeErase

• reboot


Nortel Networks Confidential Maintenance Task (Task Monitor Function)

tors

kly

-ed to-

sd butnon-ot.

.

10 Maintenance Task (Task Monitor Function)

The “tMonTask” introduced in Release 2.x.26 software running in the system moniall tasks in the Trunk application software.

“Critical” tasks are those without which the application will not operate properly,impacting service. If such a task is suspended or disappears, register and stacinformation will be dumped to the current log file and the card will be immediaterebooted.

“Non-Critical” tasks are those which do not impact basic call processing. If noncritical tasks are suspended or disappear, register and stack information is dumpthe current log file and the card is scheduled for automatic reboot in the next preconfigured service window (e.g.: 2:00 am).

The reason for delaying recovery of non-critical tasks is simple. If such a task isuspended or disappears, some services may be degraded and/or un-supportethere is no impact to basic call processing. Missing non-Critical tasks (that is, acritical task that had never been spawned on this card) will not trigger card rebo

10.1 audit.ini file

This file contains control information for the Audit/Maintenance task includingReboot Parameters and the Critical Task List. It survives system reboot soMaintenance Task operation setting will remain consistence across reboot.

This file is maintained and updated by the Monitor task, andshould not be modifiedmanually. If the audit.ini file becomes corrupted, delete it and reboot the systemThe Monitor task will rebuild the file from scratch with default settings.

The following is a sample audit.ini file that specifies

• Disabled auto-reboot

• Suspended non-critical task reboot time is 2:00am

• Total of 18 tasks are identified as Critical Tasks.

-> copy < audit.ini[Reboot Parameters]RebtOps=0RebtTOD=2:0RebtTPR=5[Critical Tasks List]TaskList1=tExcTask tNetTask tTelnetd tFtpdTask tShell tBootpdTask tMAM tRmm tNpm baseM-MintTask tA07 tNMMTask tMVX_DIM tATPM tIpss tTSM tMcciMsgMgr tRCMTaskList2=;


Maintenance Task (Task Monitor Function) Nortel Networks Confidential

.cing

tes),

er adure.

eoot?

of the

a full

e

by

less

s is

10.2 audit.his history file

The file “/C:/LOG/audit.his” contains a history of Audit/Maintenance task activityEach record contains a record index, log time, record id, name of the task experiena problem and a short description of the problem. The file is a fixed size (4096 byand when it is full, new records will overwrite the oldest ones in the file.

To view the content of the audit.his on switch, use:

-> copy < audit.his

10.3 CLI commands for Audit/Maintenance task

Typically, if the audit history lists an anomaly, the user may need to adjust whethtask is critical or non-critical, and may want to enable or disable the reboot proce

TheauditShow (section B.1.3, pg 121) command allows the user to determine thcurrent status. Is reboot enabled? For non-critical tasks, when does the card rebAnd which tasks are critical or non-critical?

Sometimes, when debugging an issue requires access to the memory at the timefault the user may choose to block the reboot. TheauditRebootSet 0/1(section B.1.1,pg 120) command allows the user to set the reboot status. This is followed by printout of the information as though theauditShow command was issued.

The traffic shape of a node varies from the shape on another node, often by largamounts. As a result, the non-critical task reboot time for one site may beunsatisfactory at another. TheauditRebootTimeSet hh:mm (section B.1.2, pg 120)command allows the user to set the non-critical task reboot time. This is followeda full printout of the information as though theauditShow command was issued.

Different sites may use different capabilities. This may make some tasks moreimportant than on the “average” site”, or make a task normally flagged as criticalimportant. TheauditTaskSet [tname|tid],level (section B.1.4, pg 121) commandallows the user to define which tasks are the critical and non-critical tasks. Thifollowed by a full printout of the information as though theauditShowcommand wasissued.


Nortel Networks Confidential Patcher Tool Support

teng

ilable

ith ay

atchusing

l is

es tochn bepleing isvatedthe

the

el.

11 Patcher Tool Support

The new Patcher utility introduced in Release 2.x.26 software allows softwaremodification in the field for many problems without any interruption in service. Nothat it may not be available for all problems, based on technical limitations dealiwith data structure definitions.

The patcher tool uses the same interface as the M1 CPP patcher tool and is avaon both the Pentium and SA platforms. The tool builds a patch file which is thenloaded and put into service on a running system, replacing an existing function wnew one without requiring a software reload. Memory patches can be created bNortel support personnel in the Unix environment or on the switch, although the pshould never be created on a customer switch. Source code patches are createdthe build environment for a given software version. The Unix patch creation toothen used to extract the patch from the source code modification.

The patch file contains control information about the patch, the memory addressbe patched, and the patch object code itself. It should only be loaded on a switrunning the release of software for which it was created. “Aggregate patches” cacreated by merging multiple individual patches. The resulting file contains multi“patch elements” which can be loaded and activated as a unit. Aggregate patchuseful when there are various inter-dependent patch elements that must be actisimultaneously. Patch files should be located in the “/C:/U/PATCH/” directory oncard. The retention file used to re-insert patches on system startup is in “/C:/U/PATCH/RETEN”

The patch tool implementation on the SMC and ITG-P platforms only supports theresretention level. Patches are reloaded during the system startup sequence, afterVxWorks kernel bootup finishes but before the application starts.

11.1 On Switch Patch Tool CLI Commands

The patcher commands are executed either from CLI or under vxWorksShell lev

1. pload Loads a patch file from C: drive into memory.

2. pout Remove a patch from memory.

3. pins Activate a pload’ed patch, put it in-service.

4. poos Deactivate an in-service patch, take it out-of-service.

5. pstat Display summary status of all loaded patches.

6. plis Gives detailed information about one patch in the system.


Installation and upgrades Nortel Networks Confidential

al, the

eadere’s

dsir IPtepither

de

ele’tss to an

theP toirect

’ss

12 Installation and upgrades

12.1 Installation Overview

The NTP describes the commands and process for installing a new card. In generprocedure is:

1. Setup the ELAN’s subnet mask, IP address and gateway IP address, set the Lflag and a flag to get data from a local BOOTP table in the NVRAM of the NodLeader 0 card. This enables the ELAN interface to be used by MAT/OTM fordownloads or from the BIOS/VxWorks shell CLI for file transfers. This only neeto be done for the Leader - all of the remaining cards in the node retrieve thedata from the Leader 0 via the BOOTP request/response mechanism. This s(and step 2) requires you to connect a terminal directly to the Leader 0 card, ethrough the faceplate or the octopus cable connection.

2. Download the application software to the card.

3. Download the Node and Card properties from MAT/OTM to the card. The Noproperties are downloaded in the BOOTP.1 file. The Card properties aredownloaded in the CONFIG1.INI file.

12.1.1 FTP server and file transfer options

Normally, the application S/W and configuration files can be downloaded from thMAT/OTM PC. However, in some support situations, it may be difficult or impossibto access the MAT/OTM PC and initiate the download. The SMC and ITG-P donsupport PPP, so you need to have either a PC card in the faceplate or have accedevice on the ELAN from which to provide a new load or update the configuratiofiles.

One option is to create a directory on the M1 CPU’s drive (e.g. c:/u/itg) and put files in it. You could either remotely PPP the files through the M1 to it or use FTcopy the files to it when you have access to the MAT/OTM PC. You can then dtheswDownload function to that directory for the S/W upgrade. Likewise, you canFTP the CONFIG1.INI and BOOTP.1 files to the cards from it. If you use the M1drive, care must be taken that the files do not cause the disk to become full, thuimpacting the M1’s operation.

Useful commands for transferring the files are:

• swDownload “srvrIP”, “uid”, “passwd”, “path”, “fname” (section B.1.41, pg166)FTPs the application to the card.


Nortel Networks Confidential Installation and upgrades

ady

(e.g.p

TP

12.1.2 Setting NVRAM parameters from the CLI

The necessary NVRAM parameters for the Leader 0 card can be set using thecommandsetLeader “IPaddr”,”gwIPaddr”,”subnetMask” (section B.1.39, pg 165)from the ITG’s CLI. This works in the case where you are installing a card that alrehas a load of S/W on it. When the card boots up, press “+++” when the “....” areprinting during the BOOTP query time. The card will then load the existingapplication load. Login and enter the command.

12.1.3 Setting NVRAM parameters from the BIOS / BootROM

If there’s a situation where the application on the card is corrupted or not presentthe card rebooted just after theupgradeErasecommand was executed), you can setuthe ELAN IP data from the BIOS using the following command sequence.

12.1.3.1 IPT-P, SMC with BIOS version 5.0

1. Configure the ELAN interface’s IP data in NVRAM:

BIOS> lnIsa_progSubnetMask “<ELAN subnet mask>”BIOS> lnIsa_progIP “<ELAN IP Address>”BIOS> lnIsa_progGW “<ELAN subnet mask>”

2. Set the leader flag.

BIOS> nvramLeaderSet

3. Set the flag so data is read from the local BOOTP.1 file instead of doing a BOOquery.

BIOS> lnIsaIPMethodSet 2

4. Confirm everything was programmed correctly.

BIOS> NVRIPShowIP Address from NVRAM: 47.11.217.54IP address : 47.11.217.54Gateway : 47.11.216.1Subnet Mask: 255.255.254.0Set as Leader.Set to use IP address parameters in NVRAM.value = 43 = 0x2b = ’+’BIOS>

12.1.3.2 SMC

Use “setLeader” (documented undersetLeader “IPaddr”,”gwIPaddr”,”subnetMask”(section B.1.39, pg 165), but in reality a function appended to the base), or:

1. Configure the ELAN interface’s IP data in NVRAM:



TP

ione

from

rsionare

e the the

-> ixpMac1_progSubnetMask “<ELAN subnet mask>”-> ixpMac1_progIP “<ELAN IP Address>”-> ixpMac1_progGW “<Gateway IP address>”

-> ixpMac1_progSubnetMask "255.255.255.0"-> ixpMac1_progIP "44.55.66.77"

2. Set the leader flag.

-> nvramLeaderSet

3. Set the flag so data is read from the local BOOTP.1 file instead of doing a BOOquery.

-> ixpMac1_IPMethodSet 2

4. Confirm everything was programmed correctly.

-> NVRIPShowIP Address from NVRAM: 47.11.217.54IP address : 47.11.217.54Gateway : 47.11.216.1Subnet Mask: 255.255.254.0Set as Leader.Set to use IP address parameters in NVRAM.value = 43 = 0x2b = ’+’->

12.2 Software Upgrade Overview

Software upgrades are normally done via the MAT/OTM software download funct(synchronize > transmit > card software). However, they can be initiated from thITG’s CLIs if the situation requires.

Although the commands are different depending on whether they are carried outthe CLI prompt or the BIOS interface, the basic sequence of the download is:

1. Erase the program store area of Flash memory. This guarantees any older veof software is removed from the card. Normally the card saves the current softwload when a new one is downloaded from MAT/OTM. If the new load fails tobootup, the old load is used. But this increases the card bootup time becauschecksum must be calculated for both binaries. Erasing the Flash speeds upreboot time because after the download, only one binary is in Flash.

2. If necessary, setup the FTP server or card to be ready for the download.

3. If necessary, setup the IP address info on the card (see section 12.1).

4. Execute the download command which FTP’s the software from the server.

5. Reboot the card to activate the new load.



ver,mittheTP

emand

asn’t

file.

can

lize it.

12.2.1 Software upgrades from the CLI

1. Erase the program store area (upgradeErase (section B.2.66, pg 240)).

2. Setup the FTP server (optional). You’ll need to know the IP address of the serthe filename and path. If FTPing the file from the MAT/OTM PC, open the transdialogue (synchronize > transmit), check the “card software” box, browse to file to be downloaded and click “Open”. Leave the transmit dialogue open, the Fserver will be ready for the FTP request from the card.

3. If necessary, configure the ELAN IP data by entering the commandsetLeader“IPaddr”,”gwIPaddr”,”subnetMask” (section B.1.39, pg 165).

4. Initiate the S/W download:swDownload “srvrIP”, “uid”, “passwd”, “path”,“fname” (section B.1.41, pg 166).

5. Reset the card (cardReset (section B.1.5, pg 122)).

12.2.2 Software upgrades from the ROM BIOS v1.2 CLI

In the case where there is no application on the card (e.g. card reboots after theupgradeErase command but before a download is completed), when there is somother application on the card, or when there is a problem preventing the card frocoming up using the application image stored in Flash, you can boot into the BIOSdownload a new version of software from there.


2. Setup the FTP server (optional). Follow directions in section 12.2.1.

3. Execute the command sequence shown in section 12.1.3 if the ITG’s IP data hbeen configured before.

4. Initiate the S/W download. The syntax varies depending on the location of the

— File is on the ITG's /C: drive, MAT/OTM PC or a network FTP server:swDownload “srvrIP”, “uid”, “passwd”, “path”, “fname” (section B.1.41,pg 166).

— File is on the ITG’s /A: drive (PC card in faceplate):

BIOS> swCopy “/A:filename”

5. Reset the card:

BIOS> reboot

If you have problems accessing the MAT/OTM PC or the remote FTP server, youuse the ping command to debug the access (same syntax in section B.1.32).

You can also FTP files to the card. Follow the instructions in section 9.2 to initiathe ITG’s file system and cd to the drive. After that, you can FTP files to and from



em

OM

asn’t

file.

can

lizem it.

nto /C:/een

12.2.3 Software upgrades from the BootROM

In the case where there is no application on the card (e.g. card reboots after theupgradeErase command but before a download is completed), when there is somother application on the card, or when there is a problem preventing the card frocoming up using the application image stored in /C:/, you can boot into the BootRand download a new version of software from there.


2. Setup the FTP server (optional). Follow directions in section 12.2.1.

3. Execute the command sequence shown in section 12.1.3 if the ITG’s IP data hbeen configured before.

4. Initiate the S/W download. The syntax varies depending on the location of the

— File is on the ITG's /C: drive, MAT/OTM PC or a network FTP server:-> upgrade “IP Address”,”user”,”passwd”,”directory”,”filename”

— File is on the ITG’s /A: drive (PC card in faceplate):

-> upgradePCMCIA “/A:filename”

5. Reset the card:

— for the IPT-P:-> reboot

— for the IPT-P:-> sysReboot

If you have problems accessing the MAT/OTM PC or the remote FTP server, youuse the ping command to debug the access (same syntax in section B.1.32).

You can also FTP files to the card. Follow the instructions in section 9.2 to initiathe ITG’s file system and cd to the drive. After that, you can FTP files to and fro

12.2.4 FTP upgrade on SMC

The application code is loaded from a file on the /C:/ drive for SMC and not burnt iflash as for ITG-P. Because of this we can directly ftp the application file to thedrive. To do this you must first remove the file protection on the /C:/exec file (sattrib “filename”,“protection” (section B.2.3, pg 172)) and then copy the applicatiofile onto the /C:/ drive and renaming it /C:/exec.



rtel

6.4nal

ThePectione

, etc.

card.

12.2.5 SMC BIOS Upgrade

The SMC BIOS is not field upgradeable. If the BIOS requires upgrade, contact NoNetworks to have it upgraded.

Upgrade is superfluous if the BIOS is version 5.0 or higher. Firmware versionsand 6.5 will both work on BSP (BIOS) version 5.0 or 5.2. (Version 5.1 was an interissue not released to the field.)

12.3 Transmit Node and Card Properties

The Node and Card properties must be downloaded from OTM to the new card.Node properties file (BOOTP.1) is used by Leader 0 to configure its own TLAN Iaddress and all the IP address information on the other cards in its node (see sA.4). MAT/OTM downloads the file to Leader 0, which FTPs a copy of the file to thcurrently registered Followers.

The Card properties (CONFIG1.INI) is used by each card to configure the codecs(see section A.2). A card gets its TLAN IP address from the BOOTP.1 (usuallyindirectly via a BOOTP response).

Certain parts (like the codec parameters) can be changed without rebooting theHowever, the card must be rebooted to read CONFIG1.INI file and processall changeswhich may have been made. So if at all possible, just reboot the card.


VxWorks Startup Script Support Nortel Networks Confidential

ute agingt

ions

nd

bes

13 VxWorks Startup Script Support

During the card bootup sequence, a built-in VxWorks function can read and execstartup script before the trunk application starts. This script can contain debugcommands for execution on laboratory or customer switches. The startup scripshould be used with caution, and only for debug support or for work-around solutfor problems not otherwise correctable.

The file is in “/C:/etc/startup” on the card. It can contain any valid VxWorks shell aCLI commands, but the results may be overridden during software startup. Forexample, the startup file may initialize a global variable to one value, but it may overridden with a different value during software initialization. In such cases, it ibetter to use the patch function as described in the previous section.


Nortel Networks Confidential Exception Trace Decoding

oes).U’s

itionion to

od

ountent.

mp.

tion

t

t

14 Exception Trace Decoding

The ITGT and IP Trunk 3.0 application software includes an exception handler tprocess fatal software problems (such as divide by zero or invalid memory accessThis handler outputs information about the error, the current status of the card CPregisters and the stack for the task executing at the time of the exception. Theinformation is output to the console and the CURRLOG.1 file. If the error isdetermined to be fatal, the card is automatically rebooted. If an exception condarises, the card will dump data detailing the nature and route cause of the exceptthe CLI output and to the CURRLOG.1 file.

The Pentium card has two maximum error counters for exception handling.

The first will allow a maximum number of exceptions (fixed at 5) in a 1 hour periabove which the card will auto-reboot.

The second will auto-reboot if the card reaches a maximum allowable exception ccondition (total of 20 exceptions). This maximum error count is not time depend

Notification of which exception counter has overflowed is detailed in the output du

Two new CLI commands have been included to allow interrogation of the excepstatus of the card:

• itgExcpCountShow - Pentium card only(section B.2.19, pg 185) Details the counfor both the number of exceptions in the last hour and the total number ofexceptions since the last boot-up.

• itgExcpCountClear - Pentium card only(section B.2.18, pg 185) Clears the counfor both the number of exceptions in the last hour and the total number ofexceptions since the last boot-up.

An example of the output from the exception handler is as follows:ITG Exception HandlerException: 14Task : “tSyslogd” (01881bd0)Program Counter: 0012ad20Status Register: 00010202Error Code : 00000002Valid Flag : 00000003Address (CR2) : 55040044

x86 registers:edi = 00000000 esi = 00000000ebp = 01881660 esp = 01881650ebx = 55040044 edx = 00000004ecx = 00000004 eax = 00000002eflags = 00000002pc = 0012ad20

Stack dump (in hex):


Exception Trace Decoding Nortel Networks Confidential

ld be

01881650: 55040044 018816d0 00000000 00000002 01881680 0012b6d1 003b8188 018816d001881670: 55040044 00000004 003b8188 00000004 018816a4 00113dfb 003b8188 018816d001881690: 55040044 00000004 5b840000 003d7d8c 00000000 018816d4 002d112c 003d7dec018816b0: 5b840044 018816d0 00000004 00000001 000036c2 003d7d8c 00200000 00000000018816d0: 00000000 018816ec 002d1163 003d7d8c 00001000 00000000 00000001 0188171c018816f0: 002d151c 003d7d8c 00001000 00000000 001d9040 003d7d8c 003d7dec 0000012001881710: 00000048 0000001d 00000000 01881744 002d1266 003d7d8c 00000f05 000036c301881730: ffffffff 000036c1 003d7d8c 000036c3 00000039 01881768 002d1858 003d7d8c01881750: 00000f05 013c3480 00000000 00000ec8 003da6c0 013c3480 0188178c 0032105201881770: 003d7d8c 00000f05 013c3480 018817e8 003da6c0 018817e8 00000004 018817a801881790: 0032165f 003da6c0 018817e8 018817e8 01f94d14 00000000 018817fc 002d2289018817b0: 00000013 018817e8 01f94458 01f94d14 013c2e80 00000000 0031f658 0031f6f4018817d0: 01fbcb20 01fbcc94 00000000 018817fc 002ca99d 01fbcb20 00000000 00000003018817f0: 00000000 013c2e80 00000ec4 01881820 0011d2ff 01f94d14 00000ec4 0000000401881810: 013c2e80 013c2e80 01f94458 01f9b7e4 0188183c 001182bd 01f94458 00000ec401881830: 00000004 013c2e80 01f9b7e4 01881858 0011b461 01f94458 000003ac 0000000101881850: 013c2e80 00000000 01881870 0011bc1e 01f9b7e4 00000000 01f9b7e4 0000000201881870: 018818ac 0011bf7e 01f9b7e4 00000002 00000000 01881924 01c3eed8 01b9099401881890: 00000076 00000000 00000000 01c3eed8 000004f3 00070030 01881de0 018818c8018818b0: 002c93ec 01f9b7e4 00000002 00000000 0000006a 0000006b 018818dc 002d2978

If an exception occurs, the syslog, containing the exception handler output shouforwarded to Technology via the Global Customer Care Services staff.


Nortel Networks Confidential Formatting the /C: Drive

orosterd

w one.

orin,

he

n a

ors.e /C:

hanf the

t was

15 Formatting the /C: Drive

15.1 Warning

Never reformat a PCMCIA software delivery card to be used in an ITG card (ITG-PSMC) on a PC running Windows 2000. If you do, you have all but permanently lthe card for use in ITG-P or SMC cards. The time and effort to revive it, and thcomplexity of the procedure which involves manually modifying sectors of the canot allowed as direct access, makes recovery more expensive then buying a ne

If you wish to delete files, use “rm” on the ITG-P or SMC card instead.

If you plan to use the card for both ITG-P and SMC, do not reformat it on an ITG-PSMC (reformatAdrive). That would make it usable for only one card type. Agause “rm”.

15.2 Symptoms of /C: Drive Corruption

The following are symptoms that corruption may exist on the C: drive.

• Cannot list the /C: drive or its content (e.g.cd “/C:” , ll produces nothing).

• BOOTP, CONFIG, TABLE, etc. directories appear truncated or corrupted(showing non-related info).

• MAT/OTM cannot transmit or retrieve files from the card.

• The output of the commanddosFsConfigShow (section B.1.11, pg 134) indicatesthe drive is full when it shouldn’t be.

Note: Thechkdskcommand should be used to confirm /C: drive corruption before tactions are taken to reformat the drive.

It is recommended that the /C: drive be reformatted if the application is loaded ocard that currently has the IP Trunk application on it.

15.3 Out of File Descriptors

It is possible that the /C: drive is actually OK but the OS has run out of file descriptWhen this happens, you cannot access the /A: or /C: drive and it may appear to bdrive corruption. Enter the commandiosFdShow(section B.2.16, pg 184) to check forthis condition. Less than 50 file descriptors should print. But if there are a lot more tthat, the card may have run out. Capture the output. Then manually free some odescriptors named “socket” using the commandclosewith the file descriptor number(start with the highest numbered sockets). If you can then access the /C: drive, thathe problem. Forward all captured logs to the technology team for investigation.


Formatting the /C: Drive Nortel Networks Confidential

lly,

cted

und

15.4 Usingchkdsk to Identify Corruption

It may be necessary to run thechkdsk “dev”, repairLevel, entryLevelType (sectionB.2.4, pg 173) command when investigating possible /C: drive corruption. Normathe command is first run to look for corruption, using the formatchkdsk “/C:”, 0,0. Itwill check the disk and print a report of the results. If corruption is reported, thecommand can be run again to clean it up. This allows more information to be colleand passed back to the technology group.

The following are some examples. The first is a clean run: no disk corruption is fo(bad allocation units = 0) and no error message is printed.

-> chkdsk “/C:”,0,0Copyright (c) 1993-1996 RST Software Industries Ltd. Israel. All rights reservedver: 2.6 FCS

Disk Check In Progress ...

total disk space (bytes) : 3,923,968 bytes in each allocation unit : 2,048 total allocation units on disk : 1,916 bad allocation units : 0 available bytes on disk : 2,658,304 available clusters on disk : 1,298 maximum available contiguous chain (bytes) : 2,654,208 available space fragmentation (%) : 1 clusters allocated : 618Done Checking Disk.value = 0 = 0x0

This next example shows a few disk problems found and corrected.

Disk Check In Progress ...

/C:/LOG/SYSLOG.3 Allocation error, size adjusted/C:/BOOTP/BOOTP.1 Start cluster number is invalid. Entry will be erased without saving, if dosFsChk has been called with <repairLevel> >= 1/C:/BOOTP/BOOTP.2 Start cluster number is invalid. Entry will be erased without saving, if dosFsChk has been called with <repairLevel> >= 1

ERRORS FOUND !!!

3 lost allocation units in 1 chains 6144 bytes disk space would be freed.

All lost chains have been made available

Corrections have been written to disk.

total disk space (bytes) : 3,923,968 bytes in each allocation unit : 2,048 total allocation units on disk : 1,916 bad allocation units : 0


Nortel Networks Confidential Formatting the /C: Drive

card

g the

available bytes on disk : 1,828,864 available clusters on disk : 893 maximum available contiguous chain (bytes) : 1,089,536 available space fragmentation (%) : 41 clusters allocated : 1,023Done Checking Disk.

15.5 Formatting the /C: Drive on Pentium platform

If disk corruption is found by the chkdsk utility, the drive requires reformatting torecover. This procedure will erase the first sector on the /C: drive; when the reboots, the TFFS software formats the drive. After reformatting the drive, theconfiguration files must be downloaded from OTM.

— from BIOS:reformatCdriveBIOS> reformatCdrive

— from the VxWorks shell:reformatCdriveITG> reformatCDrive

On reboot the /C: drive will be fully reformatted with the following messagesdisplayed:

TrueFFS formatting /C: drive (flashChip) please wait... /C: drive (flashChip) TrueFFS formatting completed ... /C: drive (flashChip) is an available dosFs file system

All directories are created upon rebooting and the application running. NVRAMsettings and the binary stored on the Flash memory are not affected by reformattin/C: drive.


Formatting the /C: Drive Nortel Networks Confidential

t.

g the

15.6 Recovering the /C: Drive on Media Card platform

Formatting thecard will removeall software. Besureto have software available to reload.

To format a PC Card on a Media Card, first boot to the BootROM vxWorks prompTwo options are available for the SMC card.

At this prompt the support person may use the commandformatAtaCard:

-> formatAtaCard “Slot Number”: 0 for faceplate, 1 for internal slot.

Alternatively, the procedure used for the Pentium card applies.

— from BIOS:reformatCdriveBIOS> reformatCdrive

— from the VxWorks shell:reformatCdriveITG> reformatCDrive

On reboot the /C: drive will be fully reformatted with the following messagesdisplayed:

TrueFFS formatting /C: drive (flashChip) please wait... /C: drive (flashChip) TrueFFS formatting completed ... /C: drive (flashChip) is an available dosFs file system

All directories are created upon rebooting and the application running. NVRAMsettings and the binary stored on the Flash memory are not affected by reformattin/C: drive.


Nortel Networks Confidential Card Startup Log Messages

Twer

16 Card Startup Log Messages

16.1 Pentium captures - Leader bootup

The following is a capture of a “clean” ITG-Pentium Leader 0 startup, running IPxxxxx. The card was rebooted while enabled. See the next section for the FolloBOOTP messages.

ITG Firmware Rls 4.08051XA Firmware Ver 9.0(Pentium) 9th June 1999(C) Nortel Networks Inc., 1996-199932K External RAM detectedAll FPGAs are configuredNo dongle detected8K DPRAM detected

Bank 0 Checksum - AFBEHSuspend Power Signals O.K.¯Pentium(R) II Processor. L2 Cache EnabledJumping to vxWorks...ZYXWVURMemory Test Completed OK

BIOS ROM Pentium (PC BIOS) Version 1.2Copyright: Nortel Inc., 1999-2000

Memory Config: 08080808Memory Size: 0x04000000PCI Chipset Init DoneEnter jkl to force boot from BIOS ROM00000015Flash Size: 0x0040000011 0xF850000000 0xF980000011 0xF990000000 0xF9A0000011 0xF9B00000

Cookie array value: 0x11001100

Checksum Validation at Bank Address: 0xF9800000Checksum in ROM = 1338FDD2Length of bank = 00138DC0Calculated Checksum = 1338FDD2

Checksum Validation at Bank Address: 0xF9A00000Checksum in ROM = 569B458BLength of bank = 00139630Calculated Checksum = 569B458B

Checksum array value: 0x11001100

Loading code from address: F9A00010

Cookie Address : 0xF9A00010Cookie Value : 0x90909090

Indicates Bank 1 binary loaded(latest S/W image with validchecksum is chosen)

5 second window to enter jklfor booting into BIOS

Checksum identifies version

Amount of Flash memory on card(4 Meg 16 bit words = 8 Meg)


Card Startup Log Messages Nortel Networks Confidential

Jumping to VxWorks at 0x00E00000EIP = 0x00E0011EJumping to romStart at 0x00E00300Uncompress Passed OKsysHwInit startsysHwInit Disable PIIX4E IDEsysHwInit Enable PCI Bus Arbitration limit to PCI Clocks:00000040sysHwInit Enable PIIX Passive Release of PHOLDsysHwInit: sysIntInitPIC - Interrupt ControllersysHwInit: PIIX4E Interrupt steering setupsysHwInit: PCMCIA device Misc Control 3 setupsysHwInit: sysSerialHWInit

Memory Configuration:

Bank 0: 64MB

sysMemTop: configuring GDT with RAM informationsysHwInit2: Connecting PIT0 (sysClk) Interrupt VectorsysHwInit2: Connecting RTC (sysAuxClk) Interrupt VectorsysHwInit2: Calling sysSerialHwInit2sysHwInit2: Connecting stray interrupt handlersysHwInit2: Connect task-level exception handlerEnter xxx to force boot from BIOS ROMSetting tLogTask priority to 255Found device : Cirrus CL-PD672x/C: drive (Flash Chip) is TrueFFS formatted/C: drive (Flash Chip) is an available dosFs file systemipMethodInit, gIPMethod = 2IP Data in NVRAM Valid, Boot Line updated IP Address:192.168.1.14 Gateway Address:192.168.1.1 Subnet Mask::ffffff80Target Name: vxTargetUser: gijxs03lnIsa0 MAC Address: 00:60:38:01:09:falnIsa: lnIsa0 ResetlnIsa: lnIsa0 Resetln79970 - IRQ INTC steered to IRQ15ln79970HwInit: Device Type 0x2624 - LN79972 10/100BaseTlnPci1 MAC Address: 00:60:38:01:a1:46Leader Pack: Using IP info from nvramAttached TCP/IP interface to lnIsa unit 0Attaching network interface lo0... done.NFS client support not included.


]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] (R) ] ]]]]]]]]] ]]]]]] ]]]]]]]] ]] ]]]] ]] ]]]]]]] ]]]]]]]] ]]]]]] ] ]] ]]]] ]]] ]]]]] ] ]]] ] ]]]] ]]] ]]]]]]]]] ]]]] ]] ]]]] ]] ]]]]] ]]]] ]]] ]] ] ]]] ]] ]]]]] ]]]]]] ]] ]]]]]]] ]]]] ]] ]]]] ]]]]] ] ]]]] ]]]]] ]]]]]]]] ]]]] ]] ]]]] ]]]]]]] ]]]] ]]]]]] ]]]]] ]]]]]] ] ]]]]] ]]]] ]] ]]]] ]]]]]]]] ]]]]

Ignore: bogus prompt

Flash file systeminit’d, /C: drive ready

NVRAM data set viasetLeader or BIOS commands

lnIsa configuration

Card’s ELAN MAC address - mustmatch entry in BOOTP.1

Card is Leader, uses NVRAM data.If Flr, BOOTP request would bedone at this point.

Amount of DRAM on card



]]]]]]] ]]]]] ] ]]]]]] ] ]]] ]]]] ]] ]]]] ]]]] ]]]] ]]]] ]]]]]]]] ]]]]] ]]] ]]]]]]] ] ]]]]]]] ]]]] ]]]] ]]]] ]]]]] ]]]]]]]]]]

ITG Login: Copyright (c) 1993-1996 RST Software Industries Ltd. Israel. All rightsreservedDeleted old File (/C:/H323/CONFIG1.VAL)File (/C:/H323/CONFIG1.VAL) Created.Deleted old File (/C:/H323/MSG1.CFG)File (/C:/H323/MSG1.CFG) Created.

VxWorks login: 1970 1 1 00:00:00 (SNMP) :Completed addition of ITG MIB tree 1.3.6.1.4.1.5622040 6 21 23:07:58 (COM) :Set defaultRouteGW: 0.0.0.02040 6 21 23:07:58 (COM) :NVRAM leader: BOOTP file present2040 6 21 23:07:58 (COM) :Sending BOOTP request: timeout 9200

VxWorks login: 2040 6 21 23:08:16 (COM) :No BOOTP response: set as Leader2040 6 21 23:08:16 (COM) : ~~~~~~~~~~~~~~~ STARTING LEADER TASKS ~~~~~~~~~2040 6 21 23:08:16 (COM) :tBootpdTask spawned2040 6 21 23:08:16 (COM) :tSntpsTask spawned204 leaderIP 192.168.81.30 are in the same subnet2040 6 21 23:08:16 (COM) :setting Leader IP address 192.168.81.302040 6 21 23:08:16 (COM) :tHSRecvTask (Leader listening task) spawned2040 6 21 23:08:16 (COM) :0xDCH composite info = |6.135.0.33|1c5ddac2040 6 21 23:08:16 (COM) : (DCHIP card 1: DCH num 6: protocol 0x7: ESN5 0: 1st BCH ID 332040 6 21 23:08:16 (RMM) :tNetTask***LDR send back GK status:0): 2040 6 21 23:08:17 (RMM) :duplicate ***FL card update GK status: 0IP addres2040 6 21 23:08:17 (A07) :s Waiting for XA firmware version reply...2040 6 21 23:08:19 (A07) :Received firmware version reply

2040 6 21 23:08:19 (NMM) :tNMM running: Software version ITG2.24.25 ITG SW Version2040 6 21 23:08:20 (DIM) :DSP memory tests passed on DSP 02040 6 21 23:08:20 (DIM) :DSP memory tests passed on DSP 12040 6 21 23:08:21 (DIM) :DSP memory tests passed on DSP 22040 6 21 23:08:21 (DIM) :DSP memory tests passed on DSP 32040 6 21 23:08:22 (DIM) :DSP memory tests passed on DSP 42040 6 21 23:08:22 (DIM) :DSP memory tests passed on DSP 52040 6 21 23:08:23 (DIM) :DSP memory tests passed on DSP 62040 6 21 23:08:23 (DIM) :DSP memory tests passed on DSP 72040 6 21 23:08:23 (DIM) :Found 8 DSP devices in sys-tem2040 6 21 23:08:23 (DIM) :MXP environment is created2040 6 21 23:08:23 (SNMP) :DSP temp string isR7.01(Build 1)2040 6 21 23:08:23 (SNMP) :DSP str is R7.01(Build 1)2040 6 21 23:08:23 (NMM) :sending Module Status message: module 15: status 02040 6 21 23:08:23 (NMM) :Task # 15 : status = 02040 6 21 23:08:23 (SNMP) :dummy: setting up alarm struc2040 6 21 23:08:23 (SNMP) :Calling snmpTrap2040 6 21 23:08:24 (DIM) :0000015944 - ROOT: gg_perm_malloc: 256 bytes at 0x004FEF80

2040 6 21 23:08:24 (DIM) :0000015944 - ROOT: gg_perm_malloc: 18400 bytes at 0x004FF080

2040 6 21 23:08:24 (DIM) :0000015944 - ROOT: gg_perm_malloc: 2784 bytes at 0x00503860

and passed selftest8 DSPs detected



1996 3 17 17:42:07 (DIM) :Download codec image completed -DSP# 0, Image Id = 01996 3 17 17:42:07 (DIM) :Download codec image completed -DSP# 1, Image Id = 01996 3 17 17:42:09 (DIM) :Download codec image completed -DSP# 2, Image Id = 01996 3 17 17:42:12 (DIM) :Download codec image completed -DSP# 3, Image Id = 01996 3 17 17:42:14 (DIM) :Download codec image completed -DSP# 4, Image Id = 01996 3 17 17:42:17 (DIM) :Download codec image completed -DSP# 5, Image Id = 01996 3 17 17:42:19 (DIM) :Download codec image completed -DSP# 6, Image Id = 01996 3 17 17:42:22 (DIM) :Download codec image completed -DSP# 7, Image Id = 02040 6 21 23:08:24 (NMM) :NMM received file data OK message from ATPM2040 6 21 23:08:24 (COM) :ITG0100, ITG card bootup is successful2040 6 21 23:08:33 (NPM) :RADVision H.323 payload update complete.2040 6 21 23:08:33 (COM) :Current ESN5 Prefix is set to |100|

VxWorks login:

DSP image downloadedto each DSP



16.2 Pentium captures - Follower bootup

When a Follower boots and receives its IP data from the BOOTP response, thehighlighted section below is printed out differently than on the Leader card:

sysHwInit: sysSerialHWInit

Memory Configuration:

Bank 0: 64MB

sysMemTop: configuring GDT with RAM informationsysHwInit2: Connecting PIT0 (sysClk) Interrupt VectorsysHwInit2: Connecting RTC (sysAuxClk) Interrupt VectorsysHwInit2: Calling sysSerialHwInit2sysHwInit2: Connecting stray interrupt handlersysHwInit2: Connect task-level exception handlerEnter xxx to force boot from BIOS ROMSetting tLogTask priority to 255Found device : Cirrus CL-PD672x/C: drive (Flash Chip) is TrueFFS formatted/C: drive (Flash Chip) is an available dosFs file systemipMethodInit, gIPMethod = 1lnIsaNvramInfoGet: ipMethod = 1, Boot Line not updatedTarget Name: vxTargetUser: gijxs03lnIsa0 MAC Address: 00:60:38:01:19:4flnIsa: lnIsa0 ResetlnIsa: lnIsa0 Resetln79970 - IRQ INTC steered to IRQ15ln79970HwInit: Device Type 0x2624 - LN79972 10/100BaseTlnPci1 MAC Address: 00:60:38:01:a1:b8Getting IP over BOOTP via network interface lnIsa0Enter +++ to escape to Shell for manual configuration

lnPci1 IP: 192.168.1.150 ifAuxSubnetMask: 0xffffff80 Secondary Gateway: 192.168.1.200 Bootp Server: 192.168.1.14 Default Gateway: 192.168.1.1 lnIsa0 IP: 192.168.1.15 Subnet mask: 255.255.255.128Attached TCP/IP interface to lnIsa unit 0Attached TCP/IP interface to lnPci unit 1Attaching network interface lo0... done.NFS client support not included.


Retrieving IP data viaBOOTP request

BOOTP responseConfig data extracted from



,

16.3 Succession Media Card captures - Leader bootup

The following is a capture of a “clean” Succession Media Card Leader 0 startuprunning IPT30052. The card was rebooted while enabled.

MC Firmware Rls 6.48051XA Firmware Version 4.8 26 May 2002(C) Nortel Inc. 2001EPLD Version: 3.032K External RAM detected8K DPRAM detectedAll FPGAs are configuredNo dongle detected

Bank 0 Checksum - A6FBHSRAM test okaySDRAM Addr test okaySDRAM blank overEarly serial debug initialized

VxWorks System Boot

Copyright 1984-1998 Wind River Systems, Inc.

CPU: IXP1200Version: 5.4BSP version: 5.0Creation date: Nov 22 2001, 18:21:11

Enter jkl to force boot to BootROM vxWorks prompt

5 second window to enter jklfor booting into BIOS

VxWorks version 5.4

card firmware version 6.4



auto-booting...

boot device : ata=unit number : 1processor number : 0file name : /C:/execflags (f) : 0x0other (o) : ixpMac

Attaching to ATA disk device... Found device : Cirrus CL-PD672x0x3af7934 (tBoot): PC Card Detected: Socket 0cisGet : pcCard recognizedPC Card Detected: Socket 1cisGet : pcCard recognized/C:/ - Volume is OK3510564 + 594412 + 4566428Starting at 0x1000...

Early serial debug initializedsysHwInit2: Connect task-level exception handlerSetting tLogTask priority to 150Found device : Cirrus CL-PD672xcisGet : pcCard recognized0x3affe64 (tRootTask): PC Card Detected: Socket 0logTask: 2 log messages lost.PC Card Detected: Socket 1cisGet : pcCard recognizedipMethodInit, gIPMethod = 2IP Address from NVRAM: 47.11.217.55IP Data in NVRAM Valid, Boot Line updated IP Address:47.11.217.55 Gateway Address:47.11.217.1 Subnet Mask::fffffe00Host Name: bootHostTarget Name: vxTargetUser: targetStartUp Script: /C:/etc/startup

MAC Address for Port 0 is : 00:60:38:bd:fb:31SysConf: uEng_intConnect to pktHandlingIsr.0 symbols bound.Load uCode from buffer Status : Return SuccessStarting Microengines.0x3affe64 (tRootTask): Loading MAC_21440...0x3affe64 (tRootTask): mac21440Load: Init String[0] NULL: ixpMac0x3affe64 (tRootTask): Loading MAC_21440...0x3affe64 (tRootTask): MAC 21440 String : Processed all arugments0x3affe64 (tRootTask): mac21440InitMem: Net Pool ID is 513210120x3affe64 (tRootTask): Done loading mac21440...0x3affe64 (tRootTask): mac21440Start: Starting port 0TLAN Port set to Auto-Negotiate Speed and Duplex SettingsWaiting For Carrier link to Return

ELAN port initialization

ELAN data from non-volatile RAM

Found ATA flash(4 Meg 16 bit words = 8 Meg)

(survives reboot)



MAC Address for Port 1 is : 00:60:38:bd:fb:320x3affe64 (tRootTask): Loading MAC_21440...0x3affe64 (tRootTask): mac21440Load: Init String[0] NULL: ixpMac0x3affe64 (tRootTask): Loading MAC_21440...0x3affe64 (tRootTask): MAC 21440 String : Processed all arugments0x3affe64 (tRootTask): mac21440InitMem: Net Pool ID is 494684400x3affe64 (tRootTask): Done loading mac21440...0x3affe64 (tRootTask): mac21440Start: Starting port 1ELAN set to 10BaseT OperationELAN set to Half Duplex OperationWaiting For Carrier link to ReturnAttached TCP/IP interface to ixpMac unit 1Attaching network interface lo0... done.0x3affe64 (tRootTask): WARNING: mac21440MCastAddrAdd called. addr=0x3aff564NFS client support not included.


]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] (R) ] ]]]]]]]]] ]]]]]] ]]]]]]]] ]] ]]]] ]] ]]]]]]] ]]]]]]]] ]]]]]] ] ]] ]]]] ]]] ]]]]] ] ]]] ] ]]]] ]]] ]]]]]]]]] ]]]] ]] ]]]] ]] ]]]]] ]]]] ]]] ]] ] ]]] ]] ]]]]] ]]]]]] ]] ]]]]]]] ]]]] ]] ]]]] ]]]]] ] ]]]] ]]]]] ]]]]]]]] ]]]] ]] ]]]] ]]]]]]] ]]]] ]]]]]] ]]]]] ]]]]]] ] ]]]]] ]]]] ]] ]]]] ]]]]]]]] ]]]]

]]]]]]] ]]]]] ] ]]]]]] ] ]]] ]]]] ]] ]]]] ]]]] ]]]] ]]]] ]]]]]]]] ]]]]] ]]] ]]]]]]] ] ]]]]]]] ]]]] ]]]] ]]]] ]]]]] ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]]]]]]]]]]]]]]]]]]]]]]]]]]] Development System ]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]]]]]]]]]]]]]]]]]]]]]]]]] VxWorks version 5.4 ]]]]]]]]]]]]]]]]]]]]]]]]]] KERNEL: WIND version 2.5

]]]]]]]]]]]]]]]]]]]]]]]]] Copyright Wind River Systems, Inc., 1984-2000

CPU: IXP1200 . Processor #0. Memory Size: 0x3b00000. BSP version IPT3.0/0.

/C:/ - Volume is OK

(ItgPatch): 3145728 byte memory partition created for patches

Creating File System ...

2001 4 6 05:39:25

TLAN port initialization



VxWorks login: 2001 4 6 05:39:25 (COM) :Sending BOOTP request: timeout 8602001 4 6 05:39:34 (COM) :No BOOTP response: set as Leader2001 4 6 05:39:34 (COM) : ~~~~~~~~~~~~~~~ STARTING LEADER TASKS ~~~~~~~~~2001 4 6 05:39:34 (COM) :tBootpdTask spawned2001 4 6 05:39:34 (COM) :tSntpsTask spawnedAttached TCP/IP interface to ixpMac unit 00x3affe64 (tRootTask): WARNING: mac21440MCastAddrAdd called. addr=0x3aff7382001 4 6 05:39:35 (COM) :DCH composite info = |6.135.0.1|2001 4 6 05:39:35 (COM) :DCHIP card 1: DCH num 6: protocol 0x7: ESN5 0: 1st BCHID 12001 4 6 05:39:35 (COM) :Set defaultRouteGW: 0.0.0.02001 4 6 05:39:35 (COM) :Set voiceIPAddr: 47.11.214.02001 4 6 05:39:35 (COM) :Set defaultRouteGW: 47.11.215.12001 4 6 05:39:35 (COM) :leaderIP 47.11.215.211: cardIP 47.11.215.212: sm S2001 4 6 05:39:35 (COM) :cardIP 47.11.215.212 and leaderIP 47.11.215.211 are inthe same subnet0x3affe64 (tRootTask): Setting dosFS Cache Update Interval to 0200 Secs1 4 6 05:39:35 (COM) :setting Leader IP address 47.11.215.2112001 4 6 05:39:35 (COM) :tHSRecvTask (Leader listening task) spawned2001 4 6 05:39:35 (COM) :Card IP[0]: 47.11.215.2112001 4 6 05:39:35 (COM) :Card IP[1]: 47.11.215.2122001 4 6 05:39:35 (COM) : getting mgt lan ip for the card...2001 4 6 05:39:35 (RMM) :rmmLeaderInit: set Leader Mng IP address to47.11.217.552001 4 6 05:39:35 (RMM) :***LDR send back GK status:02001 4 6 05:39:35 (RMM) :***FL card update GK status: 02001 4 6 05:39:35 (RMM) :ERROR ! Ignored request from 0.0.0.0 to override own-Resource Entry index 12001 4 6 05:39:35 (A07) : XA : - Spawn xaTask()2001 4 6 05:39:35 (A07) : XA : - xaTask Spawned OK2001 4 6 05:39:35 (A07) :Waiting for XA firmware version reply...Telogy Software Version 8.1

DIM created successfully...2001 4 6 05:39:38 (A07) :Received firmware version reply2001 4 6 05:39:38 (DIM) :MXP environment is created2001 4 6 05:39:38 (DIM) :From Eeprom information, number of DSPs = 82001 4 6 05:39:38 (DIM) :dimhw_init : DSP Type = C54212001 4 6 05:39:38 (NMM) :tNMM running: Software version IPT3.0.522001 4 6 05:39:38 (SNMP) :DSP str is R8.012001 4 6 05:39:38 (NMM) :sending Module Status message: module 15: status 02001 4 6 05:39:38 (NMM) :Task # 15 : status = 02001 4 6 05:39:38 (SNMP) :dummy: setting up alarm struc2001 4 6 05:39:38 (SNMP) :Calling snmpTrap2001 4 6 05:39:38 (A07) :Last Reset Reason: Manual reset

2001 4 6 05:39:38 (NMM) :NMM received file data OK message from ATPM2001 4 6 05:39:38 (COM) :Task tSockReuse initialised okay

ATPM table built okay

D channel data fromBOOTP file decoded...



2001 4 6 05:39:38 (COM) :ITG0100, ITG card bootup is successful2001 4 6 05:39:38 (UIPC) :ITG0150 - D-channel (6) restored. Channels will bereturned to service.IP Address from NVRAM: 47.11.217.552001 4 6 05:39:42 (A07) :Board Enabled - LED OFF2001 4 6 05:39:43 (SNMP) :ContactSet: The SNMP Value is Invalid2001 4 6 05:39:43 (DIM) :Number of DSPs = 82001 4 6 05:39:43 (DIM) :DSP memory test passed on dsp 02001 4 6 05:39:43 (DIM) :DSP memory test passed on dsp 12001 4 6 05:39:43 (DIM) :DSP memory test passed on dsp 22001 4 6 05:39:43 (DIM) :DSP memory test passed on dsp 32001 4 6 05:39:43 (DIM) :DSP memory test passed on dsp 42001 4 6 05:39:43 (DIM) :DSP memory test passed on dsp 52001 4 6 05:39:43 (DIM) :DSP memory test passed on dsp 62001 4 6 05:39:43 (DIM) :DSP memory test passed on dsp 72001 4 6 05:39:43 (NMM) :NMM received file data OK message from MAM

Download codec image completed -DSP# 0, Image Id = 0Download codec image completed -DSP# 1, Image Id = 0Download codec image completed -DSP# 2, Image Id = 0Download codec image completed -DSP# 3, Image Id = 0Download codec image completed -DSP# 4, Image Id = 0Download codec image completed -DSP# 5, Image Id = 0Download codec image completed -DSP# 6, Image Id = 0Download codec image completed -DSP# 7, Image Id = 0Signalling DSP Tx UEngine to Initiate Polling2001 4 6 05:39:47 (NPM) :RADVision H.323 payload update complete.2001 4 6 05:39:47 (COM) :Current ESN5 Prefix is set to |100|

DSPs found; booting

Card up

DSPs done booting





ve

ffixthective

e that,

s,cally

theorkstchesidian

eenually.

Appendix A Configuration files

A.1 Introduction

The active configuration files have a “.1” suffix; e.g. BOOTP.1, DPTABLE.1, or haa “1” before the “.xxx”; e.g. CONFIG1.INI.

The backup files have a “.2” suffix; e.g. BOOTP.2, DPTABLE.2, or precede the suby “1”; e.g. CONFIG2.INI. The system automatically copies a “good” version of file to this. In case of bad file download or file corruption the system replaces the acopy with this version of the file.

The contents of each file can be printed using the following command:

->copy “<path/filename>”

You can change the content of the file1 using the following command:

->copy 0, “<path/filename>”Ctrl-d to return.

The copy command has other syntaxes to allow you to create a new file; be awarthese may not (and for most cases, do not) work on the Media Card. However‘copy 0,”filename”’ does work for all cards.

A.2 CONFIG1.INI

This file is parsed by the MAM task to configure the routes, the DSP, SNMP trapRADIUS client and TOS bits. The file is parsed on card reset and also automatiwhen downloaded from OTM.

Note that the ITG card can only generate North American ring-back tone. Shoulduser need other tones (for example, British ring-back) and the IPT 3.0 node interwwith a CSE 1000 gatekeeper, the user must install the applicable work-around paon the CSE 1000 signalling and call servers and/or the corrective patch on the Mer1.

Having done that, the user is advised to manually add

[LocalRingBack]M1GeneratesRingBack=1

to the end of the CONFIG1.INI file. This is a safety measure and should not beneeded, but it is highly recommended by IPT 3.0 design. An OTM patch has brequested to provide this, but until it is available, the flag needs to be entered man

1. Use this command to create these files only when OTM is unavailable.

Issue 1.5.4 IP Trunk 3.0 Expert Level Support GuideMay 20, 2003 Page 111


willrson

and

ifier

(The user can also use theuseIPTForRingBack (section B.1.44, pg 169) oruseM1ForRingBack (section B.1.45, pg 169) to toggle between ITG card and M1ring-back.)

After making this change, the user should use OTM to retrieve theb data, so that itremain after the next provisioning change through OTM. Otherwise, the craftspemust repeat this oiperation every time the provisioning changes.

A.2.1 Downloading / parsing from TTY

A.2.1.1 configFileGet

This command FTP’s the file from the specified server, renames it to config1.iniparses the file.

A.2.2 Example file

The config file is pretty self explanatory. Each section begins with a section identin [].

Note that the [routes] are routes for the ELAN only. TLAN routes are set up byDPTABLE or live traffic.

#version=2.0

[keycode]keycodeId=12345678-78654321-23434324

[snmp]rdCommunityName=publicwrCommunityName=privatetrapsEnabled=1trapsub=129.15.3.131,129.15.19.23ts1=129.15.3.131,255.255.255.224,ts2=129.15.19.23,255.255.255.0,

CardIP=129.15.3.136sysHostName=TEST SITEsysLocation=TN 148 1 12 Management IP: 129.15.3.136sysContact=Nortel Networks

[routes]re1=129.15.3.131,255.255.255.224,re2=129.15.19.23,255.255.255.0,

[dsp0]DspImage=1DtmfToneDetect=1EchoCancel=1DspEchoTail=32TxGain= 0RxGain= 0IdleNoise=-65VadThreshold=-17

IP Trunk 3.0 Expert Level Support Guide Issue 1.5.4Page 112 May 20, 2003


ModemDetect=1FaxDetect=1FaxRate=14400FaxPlayoutNomD=100FaxActiveTimeout=20FaxPacketSize=30

Codec=0VxPayload=10VxPlayoutNomD=40VxPlayoutMaxD=100VadEnabled=1

Codec=5VxPayload=30VxPlayoutNomD=60VxPlayoutMaxD=120VadEnabled=1

[tos]controlPrio=0voicePrio=0

[accounting]acSvrEnabled=0acSvrAddr=0.0.0.0:1813acSvrKey=

[LocalRingBack]

M1GeneratesRingBack=1 1

1. Added manually if required. Intended for non-North American sites with the Meridian 1 patch installed.



ss tohen

arening

the

A.3 DPTABLE.1

The dialling plan table is parsed by the ATPM module and contains the IP addredialplan digit mapping. The file is parsed on card reset and also automatically wdownloaded from OTM.

A.3.1 Downloading / parsing from TTY

A.3.1.1 nmmAtpmTranTblDnld

This forces parsing of the dialling plan table (dptable.1).

A.3.2 Example file

The dialplan file contains a list of the IP to dialplan mappings. The first two linesnot used by the ITG2.0 application (they have historical significance). Each remailine in the file represents a comma delimited dial plan entry from OTM. In thisexample, there are no digits to insert, so that field is blank.

#version=2.00,1,1,1,10,1,1,1,1LOC,300,0,0,3,,10.1.1.18,1,2.2,3.3,7,1,”GK”DSC,3,0,0,0,,10.1.1.18,1,2.2,3.3,7,0,”RICH”DSC,88, 0,0, 0,, 10.1.1.18 ,1, 2.2 ,3.3, 7,0, ”MLV”

#version=2.0 (OTM application)0,1,1,1,1 (dummy line)0,1,1,1,1 (dummy line)LOC,300,0,0,3,,10.1.1.18,1,2.2,3.3,7,1,”GK”DSC,3,0,0,0,,10.1.1.18,1,2.2,3.3,7,0,”RICH”DSC,88, 0,0, 0,, 10.1.1.18 ,1, 2.2 ,3.3, 7,0, ”MLV”

Remember: leave “insert digits” blank; putting in a “0” means a “0” is inserted asnew leading digit...

Type OfNumber-ing Plan

DialedDigits

AccessCode

# Digitsto Com-pleteCall

# Lead-ing DigitDelete

InsertDigit

RemoteIP address

QoSEnabled

SendQoS

ReceiveQoS

Node Capa-bility

GKFlag

RemoteLocName



l for

eeper

eeper

The file can be much more complex, but the format of dial plan entries is identicaall dialable numbers. However, it is also possible to have gatekeeper data.

There are three gatekeeper entry types - registration data (GKR), primary gatek(GKP) and alternate gatekeeper (GKA).

#version=2.00,1,1,1,10,1,1,1,1#Gatekeeper Registration InformationGKR,Shane_IPT_cust1,0,0#Primary GatekeeperGKP,47.11.215.253,1000,"GK1||||"#Alternate GatekeeperGKA,47.11.215.251,1000,"GK2||||"#NodeIP=47.11.215.182NPA,1416,0,0,0, ,47.11.215.182,0,3.0,3.0,7,0,""NXX,969,0,0,0, ,47.11.215.182,0,3.0,3.0,7,0,""LOC,395,0,0,0, ,47.11.215.182,0,3.0,3.0,7,0,""#LOC,034,0,0,0, ,47.11.215.182,0,3.0,3.0,7,0,""LOC,002,0,0,0, ,47.11.215.182,0,3.0,3.0,7,0,""LOC,000,0,0,0, ,47.11.215.182,0,3.0,3.0,7,0,""DSC,77,0,0,2, ,47.11.215.182,0,3.0,3.0,7,0,""#NodeIP=191.11.22.33SPN,0119999,0,0,0, ,191.11.22.33,0,3.0,3.0,8,0,""#Node=47.11.240.87DSC,27,0,0,0, ,47.11.240.37,0,3.0,3.0,7,""#Node=44.33.22.11 - Fake NodeNPA,301320,0,0,0, ,44.33.22.11,0,3.0,3.0,7,""NPA,301321,0,0,0, ,44.33.22.11,0,3.0,3.0,7,""NPA,301322,0,0,0, ,44.33.22.11,0,3.0,3.0,7,""NPA,301323,0,0,0, ,44.33.22.11,0,3.0,3.0,7,""NPA,301324,0,0,0, ,44.33.22.11,0,3.0,3.0,7,""NPA,301325,0,0,0, ,44.33.22.11,0,3.0,3.0,7,""NPA,301326,0,0,0, ,44.33.22.11,0,3.0,3.0,7,""NPA,301327,0,0,0, ,44.33.22.11,0,3.0,3.0,7,""NPA,301328,0,0,0, ,44.33.22.11,0,3.0,3.0,7,""NPA,301329,0,0,0, ,44.33.22.11,0,3.0,3.0,7,""NPA,301429,0,0,0, ,44.33.22.11,0,3.0,3.0,7,""

There are three gatekeeper entry types - registration data (GKR), primary gatek(GKP) and alternate gatekeeper (GKA).

#version=2.00,1,1,1,10,1,1,1,1#Gatekeeper Registration InformationGKR,Shane_IPT_cust1,0,0#Primary GatekeeperGKP,47.11.215.253,1000,"GK1||||"#Alternate GatekeeperGKA,47.11.215.251,1000,"GK2||||"



Translating the key bits, we get:

Comment only; makes it easier to tell that the

GKR: gatekeeper Registration

Comment only

GKP: primary gatekeeper

Comment only

GKA: alternate gatekeeper

next line is for registration info

Shane_IPT_cust1: H.323 ID

47.11.215.253: IP address of GKP1000: GK is CSE 1000 R2"GK1||||": Gatekeeper info from OTM

47.11.215.251: IP address of GKA1000: GK is CSE 1000 R2"GK2||||" Gatekeeper info from OTM

#Gatekeeper Registration Information

GKR,Shane_IPT_cust1,0,0

#Primary Gatekeeper

GKP,47.11.215.253,1000,"GK1||||"

#Alternate Gatekeeper

GKA,47.11.215.251,1000,"GK2||||"



s filebes anyrotocol

Gfile

A.4 BOOTP.1

The BOOTP.1 file is only present on the ITG leader and backup leader cards. Thicontains the Node Properties. It is parsed only on card reset. The card has to rebooted after downloading the node properties for the changes to take effect. Thuchanges to the card IP addresses or subnet masks, associated DCH number or pwill only take effect on card reset.

A.4.1 Example file

The following is a BOOTP.1 file for a single card ITG node.NOTE:Even though thefirst two lines appear as comment within the bootp file – they are used by the ITapplication and should not be modified. Comments elsewhere within the BOOTP(designated by a leading #) are ignored by the BOOTP server.

#47.11.215.211#47.11.217.55#version=2.0

.subnet1 :sm=255.255.254.0:gw=47.11.217.55:ts=47.11.215.211:hn:

1:tc=.subnet1:ha="00:60:38:BD:FB:31":ip=47.11.217.55:lp=47.11.215.212 255.255.255.047.11.215.1:dn=6 0:nt=6.135.0.1:#cardDensity=32

The lines are “colon delimited”, meaning a “:” separates fields. The key datatranslates as per the next page:

— nt=6.135.0.1 - D channel info:6 -> DCH 6135 -> 128 + 7 = (128) D channel on this card plus DCH protocol SL10.1 -> 0x00 01 - first channel is 1 (may be over 255...)



ardch.

es 7

01

The BOOTP.1 elements are broken down as follows. Note this is a single cnode; when there are multiple cards, there is a card index entry line for ea

#47.11.215.211 Node IP (Leader Alias IP)#47.11.217.55 Leader ELAN IP#version=2.0 OTM versionELAN Subnet Mask ELAN Gateway IP TLAN Node IP

.subnet1:sm=255.255.254.0:gw=47.11.217.55:ts=47.11.215.211:hn:

Card Index # ELAN MAC Address ELAN IP TLAN Voice IP

1:tc=.subnet1:ha="00:60:38:BD:FB:31":ip=47.11.217.55:lp=47.11.215.212255.255.255.0 47.11.215.1:dn=6 0:nt=6.135.0.1:

Card TN D channel info

TLAN Subnet Mask TLAN Gateway IP

TheCard TN field contains the Card’s TN plus the card type:

Large Systemdn=100 0 0 0

where:100 = Loop0 = Shelf0 = Card0 = Card Type

0 - EXUT1 - XFEM (not used)

Small Systemdn=6 0

where:003 = Card slot 30 = Card Type

0 - EXUT1 - XFEM (not used)

nt=6.135.0.1 - D channel information. 6 means DCH 6. 135 decomposas 128 + 7. “128” means that there is a D channel on this card, plus themeans that the DCH protocol is “SL1”. The 0.1 is a 16 bit integer; 0x00means that the first channel is 1 (it may be over 255...).

one entryper ITGcard



y

n

with

s them.

cantions.

le,chebe

canthe

tomsnghes as

ausellyy be

s ared are

ndsare aret of

ecauseing,

re.

Appendix B IP Trunk Command Reference

“IP Trunk” is used very rarely in these sections. The screen typicallresponds with an IPT or displays IPT when it means “IP Trunk” asthere is a real-time cost to print-outs. Therefore, the shortest versiopossible was used, and therefore it was decided to use IPT here.

The commands and variables in this section are listed in alphabetical order.

All entries include a “safety level”, used to indicate the degree of risk associateda command. The levels are (in order of increasing risk):

• Normal - will not cause events visible to the end user. Includes events such aoriginal card provisioning, which are a normal part of administering the syste

• Safe - will not cause events visible to the end user. Although the commandbe issued at any time, it is intended for system debug and not normal opera

• Safe/xxx - as per Safe, but it is possible to have a small impact. For examparpFlush will remove non-permanent entries from the ARP cache, but the cawill refill over time. As a result, calls to an address not found in the cache willslightly slower, although the difference should not be visible to a caller.

• Debug - can be used for debugging, but under exceptional circumstances it cause side effects. Normally, using these commands during off hours allowsuser to treat as “Safe”, but under moderate to heavy traffic there may be sympsuch as minor increase in post dial delay (the time between the last digit beidialled and hearing ring-back) Note, though, that this will normally be within tnorm of post dial delays, since different destinations may have different delaywell, based on network topology and distance between nodes.

• Debug/xxx - can be used for debugging, but under some circumstances it can cside effects. As per “Debug”, using these commands during off hours typicaallows the user to treat as “Safe”, but under moderate to heavy traffic there masymptoms such as loss of calls, call delays, and so forth. These commandusually very CPU intensive and CPU resources used to process this commanunavailable for call processing.

• Destructive Normal - although a regular part of the operations, these commacause severe events on the system. Commands used to upgrade the softw“Destructive Normal”, since the reboot to run the new load takes the card ouservice for the duration of the reboot.

• Destructive Debug - these commands must be used with extreme care, sincmisuse can cause service interruption. Note that no command is expected toservice interruption, but to allow a user to do the most comprehensive debuggthey need the flexibility to do things such as writing to data and program stoUsed correctly, there should be no adverse effects, but misuse is severe.



call

nitor c:/

it tog or

B.1 Commands accessible from the ITG> or -> prompt

B.1.1 auditRebootSet 0/1

Safety level: Debug. Suspended tasks can cause the card to lock up, blockingprocessing.

The user may use this to Enable(1) or Disable(0) the card reboot due to task modetect suspended/Missing task. This command will change the contents of fileconfig/audit.ini

ITG> auditRebootSet 0Audit task set auto reboot -- DisabledReboot when detect a suspended task --- DisabledReboot Time hh:mm:03:00Critical Task list : tExcTask tNetTask tTelnetd tFtpdTask ....

Non-Critical Task List: tLogTask tAioWait tAioIoTask1 tAioIoTask0 ....value = 0 = 0x0ITG>

B.1.2 auditRebootTimeSet hh:mm

Safety level: Safe.

This command expects the parameter hh:mm based on the 24 hour clock. Useset the scheduled reboot time when the task monitoring function detects a missinsuspended non-critical task.

ITG> auditRebootTimeSet “03:00”Reboot when detect a suspended task --- EnabledReboot Time hh:mm:03:00Critical Task list : tExcTask tNetTask tTelnetd tFtpdTask ...

Non-Critical Task List: tLogTask tAioWait tAioIoTask1 tAioIoTask0 ...value = 0 = 0x0ITG>



ed in

userl, or

how

ill

B.1.3 auditShow

Safety level: Safe.

This command can be used to display task monitoring setup information as storaudit.ini file, which includes the following:

• Suspended task reboot status

• Reboot time for recovery from non-critical task that failed

• Critical task list

• Non-critical task list

The following example shows the output of this command.

ITG> auditShowReboot when detect a suspended task --- DisabledReboot Time hh:mm:02:00Critical Task list : tExcTask tNetTask tTelnetd tFtpdTask ...Non-Critical Task List: tLogTask tPcmciad tTffsPTask tPortmapd ...ITG>

B.1.4 auditTaskSet[tname|tid],level

Safety level: Debug.

The user uses this command to set a task's monitor priority. This is useful if thewants to force a reboot on a suspension of a task with a default level of non-criticato block reboot on a critical task.

Use either the task name or task ID (tid). Printing the current status using auditSwill list the task names, so the task name option is usually much easier.

Level is either 1 or 0. A value of 1 will set the task to be a Critical task, while 0 wset the task to be a Non-Critical task.

ITG> auditTaskSet “tMAM”,0Reboot when detect a suspended task --- DisabledReboot Time hh:mm:03:00Critical Task list : tExcTask tNetTask tTelnetd tFtpdTask ... tShell tRmm tNpm baseMMintTask tA07 tNMMTask tMVX_DIM tATPM tIpss tTSM tMcciMsgMgrNon-Critical Task List: tLogTask tAioWait tAioIoTask1 tAioIoTask0 ... tHSRecvTask tMAM tXA tMVX_XSPY ...

value = 0 = 0x0ITG>



is is

s).

noader,in

datauestting

B.1.5 cardReset

Safety level: Destructive Normal. Used as part of software upgrade process.

Reboots the ITG card. Can be executed from the IPT and VxWorks shells. Ththe preferred way to reboot the card since it allows the application to reboot in acontrolled manner (e.g. the OM file is written and closed before the card reboot

B.1.6 cd “dirPath”

Safety level: Safe.

Change directory to the directory path specified bydirPath. Drive “/A:” is thefaceplate PC Card, while drive “/C:” is the internal Flash drive.

From the ITG> prompt:

ITG> cd “/C:”value = 0 = 0x0ITG> cd “TRACE”value = 0 = 0x0ITG> pwd/C:/TRACEvalue = 10 = 0xaITG> cd “/C:”value = 0 = 0x0ITG> pwd/C:value = 4 = 0x4

From the -> prompt:-> cd “/C:”value = 0 = 0x0-> pwd/C:value = 4 = 0x4->

B.1.7 clearLeader

Safety level: Destructive Normal. After the user reboots the card, the card canlonger be used as a leader, and if there is no other card acting as lethe node is effectively out of service. However, the card will remain service as a leader until the reboot.

This command sets up the card as a Follower by deleting the ELAN IP addressfrom the NVRAM, clearing the Leader flag and setting a flag so the BOOTP reqis sent on reboot instead of reading the IP parameters from the NVRAM. Reboocompletes the clearing of the leader data.



ied

TYNI,

ntry

aine

ITG> clearLeaderThis card will be a follower on reboot.value = 41 = 0x29 = ')'ITG> NVRIPShowIP address : 255.255.255.255Gateway : 0.0.0.0Subnet Mask: 0.0.0.0Set as Follower.Using bootp to acquire IP address.value = 37 = 0x25 = '%'

B.1.8 copy“sourceFilename”, “destFilename”

Safety level: Debug. Consumes CPU real time, but unless a very large file is cop(or printed to screen) there should be no significant impact.

This command copies a file from thesourceFilename to thedestFilename. IfdestFilenameisn’t entered, this copies the file to the standard output device (the Tdisplay), providing an easy way to look at the contents of the text files (CONFIG1.IBOOTP.TAB, SYSLOG.n, OMREPORT.nnn).

Note that this can also be used to edit a file on switch. Usingcopy 0,“filename.ext”,the user can start typing in data. The keyboard input “control-d” terminates data eand saves the data to file.

ITG> copy “dptable.1”#version=3.00,1,1,1,10,1,1,1,1#NodeIP=47.11.215.209DSC,3,0,0,0, ,47.11.215.209,0,3.0,3.0,8,”Central_Light_and_Power - Bat Cave - Customer0 - Node 1"value = 0 = 0x0ITG>.....-> copy “bootp.1”#47.11.215.211#47.11.217.55#version=2.0

.subnet1 :sm=255.255.254.0:gw=47.11.217.55:ts=47.11.215.211:hn:

1:tc=.subnet1:ha=”00:60:38:BD:FB:31”:ip=47.11.217.55:lp=47.11.215.212 255.255.255.047.11.215.1:dn=6 0:nt=6.135.0.1:#cardDensity=32value = 0 = 0x0->

Note that the line “#version=2.0 ” in the BOOTP file indicates the OTM versionand not the IP trunk version. However, in a very contradictory manner theDPTABLE.1 uses the IPT 3.0 version.1

1. The DPTABLE shows the software release of the IPT application because that is crucial to understanding certfields in the file. On the other hand, it was decided that it was more important to know the OTM server releaswhen looking at the CONFIG1.INI.



ax is(It the

er”,the

eeader

wer

iptor

Do not trust these files to tell you the software version. UseswVersionShowinstead.

The user may also edit a file on switch using the copy command. Here, the synt‘copy 0,“destfilename”’. Start with the command; end entry using a “control-d”.is usually better to edit files on a PC or workstation, and FTP up and down fromswitch. This tool provides users an alternative only.)

-> copy 0,"trash.txt"In the seventh centuryof the Roman Empire^Dvalue = 0 = 0x0-> ls...PATCHTMPtrash.txtvalue = 0 = 0x0-> copy "trash.txt"In the seventh centuryof the Roman Empirevalue = 0 = 0x0->

B.1.9 dchipResTableShow

Safety level: Safe/conditional. Consumes CPU real time, but minimal.

Note that a DCHIP (D Channel over IP) is a node and not an IPT card with the Dchannel PC card on board. A card with the D Channel PC card is a “DCHIP Leadbut that card may be - and usually is - a Follower card within the IPT node. SinceDCHIP leader has additional signalling requirements, the norm is to not have thDCHIP Leader role on the Leader card, since the Leader card also has the H323 lrole.

When entered on a Leader card, this command shows all the followers currentlyassociated with the DCH resident on this card. The craftsperson may use thiscommand to verify that all of the expected Followers are listed. Note: each Follothat has successfully registeredwith the DCHIP card is listed, displaying the followinginformation:

• Follower card’s index number in the D Channel resource table

• Follower card’s ELAN IP address

• Follower card’s starting B-channel number

• The DCHIP Leader socket descriptor for the TCP connection to the Follower

• Whether the Follower is also configured as the DCHIP Leader (socketDescr== -1)



ere is

(thetput

o

Unregistered followers are not seen.

As shown in the example, if a listed Follower is also the DCHIP Leader, thesocketDecriptor is set to -1 since the DCH messaging is passed internally and thno TCP connection.

The following example shows output for a single card node:

ITG> dchipResTableShowThe Follower (index:1) data are: Follower IP address (47.11.217.55), initBchNUm (1), socketDescriptor (-1), isDCHIPcard (YES)value = 144 = 0x90

Note that there is a distinct difference between the output on the DCHIP Leadercard with the D channel PC card inserted) and the node leader. The following ouwas seen when issuing the command on the DCHIP leader card:

ITG> dchipResTableShowThe Follower (index:1) data are: Follower IP address (47.11.254.50), initBchNUm (1), socketDescriptor (-1), isDCHIPcard (YES)The Follower (index:2) data are: Follower IP address (47.11.255.175), initBchNUm (49), socketDescriptor (26), isDCHIPcard (NO)value = 131 = 0x83ITG>

On the other hand, the following output was seen on a DCHIP Follower that alshappened to be the node leader card:

-> dchipResTableShow Card is not DCHIP,dchipResTableShow command ignored!value = 57 = 0x39 = '9'->



nthegin

are

Ld.

aat

f they the

enuy 96).

ersng

he call

B.1.10 DCHmenu

Safety level: Debug/output load. Normally, if the command is used for any optioother than 6 through 9, the command is relatively safe. Under load,options 6 through 9 can result in heavy message printout on the lowindow, at the extreme resulting in call loss and delays in calls thatnot lost.

The IPT application’s DCH Handler is the UIPE application ported from the MSDcard. This is a menu based debug tool nearly identical to that on the MSDL car

Debugging the output requires extensive practice. The output is typically rawhexadecimal. Identifying an IE and determining whether it is valid or not can bepainful exercise. Many IEs (such as the Facility and Display IEs) are similar in formto ITU-T IEs of the same name, but there are proprietary extensions, and many ofields (such as the specific operation requested in the Facility IE) are not defined bITU-T. Other IEs are Nortel Networks proprietary in the entirety. As a result,decoding a message is usually difficult. However, the primary use of the DCHmtrace is to get a message to compare with the Meridian 1 D channel trace (overla

ITG> DCHmenu

Please select one of the DCHmenu options:0 - print menu (default)1 - print current DCH state and configuration2 - print application error log3 - print link error log4 - print protocol log5 - print message log6 - ENABLE error printing7 - ENABLE info printing8 - ENABLE incoming primitive9 - ENABLE outgoing primitive10 - enter message mode11 - print b channel control blocks99 - exit menu

Please enter your DCHmenu choice:

After the menu is displayed, any carriage return without data or “0” entered triggthe reprint of the menu. Entering invalid data (not in the list) triggers the followioutput:

Please enter your DCHmenu choice: 43

Menu selection not recognized!


Several of the options print current stats and data. These are independent of tcontrol operations under way.



nothef the

at

validt, orare

• To print the D channel information, enter “1”:

Please enter your DCHmenu choice: 1STATE INFORMATION FOR PORT 0:

Port 0: Link State DataState: installed. DCH State: EstablishedAble to Establish: Yes

CONFIGURATION INFORMATION FOR PORT 0:

Port 0: Link Configuration DataNetwork side. SAPI = 0. TEI = 0. L2 Protocol = LAPD Version = 3.1L3 Protocol = 7 (table id: SL1)Port: RS-422 DCE Int ClockMDL Error Reporting: OnMonitor Mode: OffCREF Length = 2 (Not Checked) Max B Chn = 480State Masks: SL1 Init = 0x0340 DL Failure = 0x0040 INIT Tmr Exp = 0x0040In Service


• To print the application error log information (layer 3 errors), enter “2”:

Please enter your DCHmenu choice: 2APPLICATION ERROR LOG FOR PORT 0:

Application Error LogError Count


The supported error counters are only listed if the error happened; that is, if protocol discriminator errors occurred, that error will not be displayed. Fromexample shown here, there were no errors to report. Note that the source omessage error is shown by “PRI” (for “from the PBX”) and “UNIV” (for “from theIPT 3.0 or remote PBX”).

The supported error types are:

— Short messages. If the message is too short, it is rejected outright.- PRI_MSG_TOO_SHORT- UNIV_MSG_TOO_SHORT

— Invalid protocol discriminator. If unsupported, the rest of the message formis unknown.- PRI_PROTOCOL_DISCRIM_ERROR- UNIV_PROTOCOL_DISCRIM_ERROR

— Call reference errors. Invalid formats mean that the data is useless. Inflags means that the call associated with this call reference does not existhe call reference value is corrupted. Also, only certain specific messages



the

e isse,

s still

is be.

; in allivedud,

allowed to use the global call reference.- PRI_INVALID_CALL_REF_FORMAT- UNIV_INVALID_CALL_REF_FORMAT- PRI_INVALID_CALL_REF_FLAG_0- UNIV_INVALID_CALL_REF_FLAG_0- PRI_INVALID_CALL_REF_FLAG_1- UNIV_INVALID_CALL_REF_FLAG_1- PRI_INVALID_GLOBAL_CALL_REF- UNIV_INVALID_GLOBAL_CALL_REF

— Unrecognized message types. If not in the list of supported messages, message must be rejected.- PRI_UNRECOGNIZED_MSG_TYPE- UNIV_UNRECOGNIZED_MSG_TYPE

— Mandatory IE errors. The IE may be missing (in which case the messagrejected as per the applicable standards) or defective (with similar responalthough the cause value differs).- PRI_MAND_IE_CONTENT_ERROR- UNIV_MAND_IE_CONTENT_ERROR- PRI_MAND_IE_MISSING- UNIV_MAND_IE_MISSING

— Optional IE errors. These may trigger error messages, but the message iprocessed.- PRI_NON_MAND_IE_CONTENT_ERROR- UNIV_NON_MAND_IE_CONTENT_ERROR

— Undefined IEs. An IE must be legitimately defined, but if it was not, the IErejected. A “comprehension required” IE was coded to indicate it shouldtreated as a mandatory IE error. The rest are treated as non-fatal errors- PRI_UNRECOGNIZED_COMP_REQ_IE- UNIV_UNRECOGNIZED_COMP_REQ_IE- PRI_NON_MAND_UNRECOGNIZED_IE- UNIV_NON_MAND_UNRECOGNIZED_IE

— Unexpected messages. In certain states certain messages are supportedothers, they are unexpected. This catch-all event tracks messages recewhen they are out of sequence. They may be from the PBX, from the IP cloor from local timers (that should have been stopped).- PRI_EVENT_UNEXPECTED- UNIV_EVENT_UNEXPECTED- TIMER_EVENT_UNEXPECTED



as

rare.

ted

“5”.ningFor

• To print the link error log information (in theory layer 2 errors, but some layer 3well), enter “3”:

Please enter your DCHmenu choice: 3ERROR LOG FOR PORT 0:

Port 0: Link Error LogError Count 59 1


There are a large number of possible errors - over 60, but they are typically

• To print the protocol error log information (layer 3 errors), enter “4”:

Please enter your DCHmenu choice: 4PROTOCOL ERROR LOG FOR PORT 0:

Port 0: Protocol LogError Count


The most likely to apply deal with failure to establish or maintain layer 3 (indicaby the presence of the “SABME” in the error type name.

• To print the message log information (layer 3 and 4 message counter), enterMessages from the higher levels of IPT 3.0 software are prefixed “CC”, mea“from Call Control”. Requests initiate a sequence; responses complete it. example, a SETUP REQUEST is a request to send a SETUP; a SETUPRESPONSE is a request to sent a CONNECT message.

Please enter your DCHmenu choice: 5MESSAGE LOG FOR PORT 0:

Port 0: Message LogMessage CountCC Alert Request 2CC Disconnect Request 2CC Facility Request 4CC Notify Request 8CC Proceeding Request 2CC Release Request 6CC Setup Request 6CC Setup Response 2CC Restart Response 1ALERTING 6CONNECT 5CONNECT ACK 2DISCONNECT 6FACILTY 4NOTIFY 9RELEASE 2RELEASE COMPLETE 6RESTART 1SETUP 2




k

een

anport

The

• To trace message flow “on the fly” the user can enter “6” (errors only), “7” (linonly), “8” (primitives from call control) and “9” (primitives to call control).

It is difficult to use “6” to generate examples. It is best used if a problem has bidentified, to get details.

“7” produces similar output to the following. Note that only the SETUP wasprovided here; other messages followed, but the procedure is identical.

Please enter your DCHmenu choice: 7ENABLE INFO PRINTING FOR PORT 0:

Please enter your DCHmenu choice:UIPE L3 EVENT: PORT 0x00: 02/17/101 05:18:26 9232853Hdr -> 00 2F 00 00 52 00Data -> 08 02 01 A0 05 04 03 80 90 A2 18 04 E9 A0 83 20 1C 1A 11 FD A1 16 02 01 01 02 01 A1 30 0E 81 02 01 05 82 01 01 84 02 00 00 85 01 04 1C 11 11 FA A1 0D 02 01 01 02 02 01 00 CC 04 46 06 AB 00 1E 02 81 83 6C 06 69 80 34 35 30 30 70 05 E9 33 35 30 30L2->L3: SETUP: CR = 0x81A0: Proc 0x01: New CB: State = U0: CALL RELATEDEvent 0x2A: Parse MsgProc 0x47L3->SL1: CC Setup Ind: MappedHdr -> 00 2F 00 00 72 00Data -> 08 02 01 A0 2E 00 01 07 13 00 81 90 00 00 A2 00 09 09 0F 00 E9 A0 83 00 01 00 20 00 13 1E 07 00 11 FD 18 00 A1 16 02 01 01 02 01 A1 30 0E 81 02 01 05 82 01 01 84 02 00 00 85 01 04 13 15 07 00 11 FA 0F 00 A1 0D 02 01 01 02 02 01 00 CC 04 46 06 AB 00 00 1E 04 03 00 81 83 05 0A 07 00 62 80 04 00 04 05 0A 0A 03 0A 03 00 E2 00 04 00 03 05 0A 0AStart T_SETUP for 10 secondsState => U6

All messages provide similar output. First is the “record header”, indicatingevent on port 0, at a given timestamp. This is followed by the “message transheader”.

In the following example, there are 6 bytes to the message transport header.5th byte is the length of the message following; all others are “details”.

Hdr -> 00 2F 00 00 52 00



ple,get

re ofssed.

The next 0x52 bytes are the message. It is printed in rows of 10 octets.

Data -> 08 02 01 A0 05 04 03 80 90 A2 18 04 E9 A0 83 20 1C 1A 11 FD A1 16 02 01 01 02 01 A1 30 0E 81 02 01 05 82 01 01 84 02 00 00 85 01 04 1C 11 11 FA A1 0D 02 01 01 02 02 01 00 CC 04 46 06 AB 00 1E 02 81 83 6C 06 69 80 34 35 30 30 70 05 E9 33 35 30 30

This is followed by the analysis of the Q.931 or UIPE header. For this examit indicates direction (L2->L3 means from LAPD to UIPC layer 3), the messatype and call reference, and the received state (U0), plus other less importaninformation.

L2->L3: SETUP: CR = 0x81A0: Proc 0x01: New CB: State = U0: CALL RELATED

The next few lines are of little interest to any except the actual code writer.However, the line indicating the layer 4 message and the message following ainterest to design, as designers can confirm whether IEs actually were proce

At the end, timer changes and state changes are listed.

• “8” and “9” provide more terse tracing. To compare a SETUP received withoption 7 and one with option 8, refer to the following:

Figure 5 “Option 8” SETUPPlease enter your DCHmenu choice: 8ENABLE INCOMING PRIMITIVE MONITOR FOR PORT: 0

Please enter your DCHmenu choice:LAPD -->>> UIPC 8 2 1 a0 5 4 3 80 90 a2 18 4 e9 a0 83 20 1c 1a 11 fd a1 16 2 1 1 2 1 a1 30 e 81 2 1 5 82 1 1 84 2 0 0 85 1 4 1c 11 11 fa a1 d 2 1 1 2 2 1 0 cc 4 46 6 a9 0 1e 2 81 83 6c 6 69 80 34 35 30 30 70 5 e9 33 35 30 300x33a5d3c (tPcmciad): <DL_DATA_IN>

Figure 6 Same SETUP using option 7UIPE L3 EVENT: PORT 0x00: 02/17/101 05:31:05 9308768Hdr -> 00 2F 00 00 52 00Data -> 08 02 01 A0 05 04 03 80 90 A2 18 04 E9 A0 83 20 1C 1A 11 FD A1 16 02 01 01 02 01 A1 30 0E 81 02 01 05 82 01 01 84 02 00 00 85 01 04 1C 11 11 FA A1 0D 02 01 01 02 02 01 00 CC 04 46 06 A7 00 1E 02 81 83 6C 06 69 80 34 35 30 30 70 05 E9 33 35 30 30L2->L3: SETUP: CR = 0x81A0: Proc 0x01: New CB: State = U0: CALL RELATED



le in

Event 0x2A: Parse MsgProc 0x47L3->SL1: CC Setup Ind: MappedHdr -> 00 2F 00 00 72 00Data -> 08 02 01 A0 2E 00 01 07 13 00 81 90 00 00 A2 00 09 09 0F 00 E9 A0 83 00 01 00 20 00 13 1E 07 00 11 FD 18 00 A1 16 02 01 01 02 01 A1 30 0E 81 02 01 05 82 01 01 84 02 00 00 85 01 04 13 15 07 00 11 FA 0F 00 A1 0D 02 01 01 02 02 01 00 CC 04 46 06 A7 00 00 1E 04 03 00 81 83 05 0A 07 00 62 80 04 00 04 05 0A 0A 03 0A 03 00 E2 00 04 00 03 05 0A 0AStart T_SETUP for 10 secondsState => U6

It can be seen easily that the information from the received SETUP is availabboth cases, but the level “8” was less complete.



Figure 7 Sample of an option 8 message trace, and how to interpret itLAPD -->>> UIPC 8 2 1 a0 5 4 3 80 90 a2 18 4 e9 a0 83 20 1c 1a 11 fd a1 16 2 1 1 2 1 a1 30 e 81 2 1 5 82 1 1 84 2 0 0 85 1 4 1c 11 11 fa a1 d 2 1 1 2 2 1 0 cc 4 46 6 a9 0 1e 2 81 83 6c 6 69 80 34 35 30 30 70 5 e9 33 35 30 30 0x33a5d3c (tPcmciad): <DL_DATA_IN>LAPD -->>> UIPC ----------- SETUP received from the M1HEADER BCAP{8 2 1 a0 5} {4 3 80 90 a2}CHID FAC{18 4 e9 a0 83 20} {1c 1a 11 fdFAC (continued)a1 16 2 1 1 2 1 a1 30 eFAC (end) FAC0 85 1 4) (1c 11 11 fa a1 dFAC (continued)2 1 1 2 2 1 0 cc 4 46FAC (end) PROG CLNG6 a9 0) (1e 2 81 83) (6c 6 69CLNG CLED80 34 35 30 30) (70 5 e9 33 35CLED30 30)

Use the same procedure for the other traces.

NOTE:

Incoming: All messages sent to the PC Card by UIPCOutgoing: All messages sent to the PC Card via Layer 1 Driver



is

B.1.11 dosFsConfigShow


This command prints information about the DOS file system on the /C: drive. It useful to determine how much free space remains on the disk.

The following is a sample of the output for an SMC card:

ITG> dosFsConfigShow

volume descriptor ptr (pVolDesc): 0x338089ccache block I/O descriptor ptr (pCbio): 0x3380b68auto disk check on mount: DOS_CHK_REPAIR | DOS_CHK_VERB_2max # of simultaneously open files: 22file descriptors in use: 2# of different files in use: 2# of descriptors for deleted files: 0# of obsolete descriptors: 0

current volume configuration: - volume label: NO NAME ; (in boot sector: NO NAME ) - volume Id: 0x65b10ef - total number of sectors: 31,264 - bytes per sector: 512 - # of sectors per cluster: 8 - # of reserved sectors: 1 - FAT entry size: FAT12 - # of sectors per FAT copy: 12 - # of FAT table copies: 2 - # of hidden sectors: 32 - first cluster is in sector # 57 - directory structure: VFAT - root dir start sector: 25 - # of sectors per root: 32 - max # of entries in root: 512

FAT handler information:------------------------ - allocation group size: 1 clusters - free space on volume: 8,511,488 bytesvalue = 0 = 0x0ITG>



andple

rrentonse

For the Pentium card, the output looks like this:

ITG> dosFsConfigShowdevice name: /C:total number of sectors: 7695bytes per sector: 512media byte: 0xf8# of sectors per cluster: 4# of reserved sectors: 1# of FAT tables: 2# of sectors per FAT: 6max # of root dir entries: 240# of hidden sectors: 1removable medium: falsedisk change w/out warning: not enabledauto-sync mode: not enabledlong file names: not enabledexportable file system: not enabledlowercase-only filenames: not enabledvolume mode: O_RDWR (read/write)available space: 3481600 bytesmax avail. contig space: 3440640 bytesvalue = 0 = 0x0ITG>

B.1.12 firmwareVersionShow


Print the card’s firmware version. It should be Rls 5.7 or higher for Pentium card,should be Rls 6.4 (media card) and 4.8 (XA) or higher for the SMC card. The examshows the command and reply as per a Succession Media Card.

ITG> firmwareVersionShowFirmware Version : MC Firmware Rls 6.4value = 40 = 0x28 = ’(’ITG>

B.1.13 gkShow

Safety level: Debug; safe except under heavy traffic.

This command prints the gatekeeper provisioning, operational status, and the cuinformation from the gatekeeper. If there is no gatekeeper provisioned, the respis:

ITG> gkShow

There are no Gatekeepers.

value = 2 = 0x2

If there is gatekeeper provisioning, the response is similar to the following:



If an

ITG> gkShow

There is a Primary Gatekeeper only.

---------------------------------------<<PROVISIONED>>The H.323 ID of this gateway is : [Lab_switch1_IPT_cust1]First place dialed numbers are resolved: ATPMSecond place numbers are resolved : GatekeeperCards that register with the Gatekeeper: All

<<OPERATIONAL>>The Current Gatekeeper is : PrimaryThe Current Gatekeeper status is : Registered

<<From the Gatekeeper>>The Time To Live (TTL) for the node is : 30 secondsThe remaining time to Re-Register is : 9 secondsThe Gateway End Point ID is : .0.2.6.1.2.a.e.0.2.0.0.3.0.2.0.6.1.4.0.4.0.7.0.0.0.2.b.3.8.6.2.6.a.7The Gatekeeper has Pre-Granted ARQ : Not Granted - direct calls possible---------------------------------------

Primary Gatekeeper information <<PROVISIONED>>------------------------------Primary Gatekeeper type is : CSE1000Primary Gatekeeper IP information is :*Gatekeeper IP : 47.11.249.140*QoS Enabled : 0*Node Capability : 9 - CSE - Interop Format---------------------------------------

value = 2 = 0x2ITG>

Note, though, that in this example there was only one gatekeeper - the primary.alternate existed, it would have been shown separately.



The following explains the fields:

ITG> gkShow

There is a Primary Gatekeeper only.

---------------------------------------<<PROVISIONED>>

The H.323 ID of this gateway is : [Lab_switch1_IPT_cust1]

First place dialed numbers are resolved: ATPMSecond place numbers are resolved : Gatekeeper

Cards that register with the Gatekeeper: All

<<OPERATIONAL>>

The Current Gatekeeper is : Primary

The Current Gatekeeper status is : Registered

Line indicating that (a) a gatekeeperwas provisioned and (b) only theprimary gatekeeper exists.

Line indicating the start ofprovisioning based data.

Order of looking for places to resolvethe addresses.

Do all cards register as one (possiblywithout indicating the IP addresses)or does each register independently?

Start of operational data - states,etc.

Is the node registered with the primaryor the alternate gatekeeper?

Is it registered, was it registered butthe re-registration failed, or was itnever registered?

registration with the gatekeeper.The provisioned H.323 ID as used for

There must be a 100% match (absolutelyidentical text strings).



<<From the Gatekeeper>>

The Time To Live (TTL) for the node is : 30 seconds

The remaining time to Re-Register is : 9 seconds

The Gateway End Point ID is :.0.2.6.1.2.a.e.0.2.0.0.3.0.2.0.6.1.4.0.4.0.7.0.0.0.2.b.3.8.6.2.6.a.7

The Gatekeeper has Pre-Granted ARQ : Not Granted - direct callspossible

---------------------------------------

Primary Gatekeeper information <<PROVISIONED>>------------------------------Primary Gatekeeper type is : CSE1000Primary Gatekeeper IP information is :*Gatekeeper IP : 47.11.249.140*QoS Enabled : 0*Node Capability : 9 - CSE - Interop Format---------------------------------------

value = 2 = 0x2ITG>

Information received from the GK,or operational information based onthe gatekeeper responses.

The time to live interval; usually,this is as provisioned by the mediagateway, but the gatekeeper canover-rule and “tell” the gatewaywhat value to use.

In 9 seconds, the card will re-senda registration request.

A unique end-point identifier whichwas assigned by the gatekeeper.

The gateway has to request admissionvia the ARQ before using the SETUP.



Caution: If there is not a 100% match between the H.323 IDas provisioned on the IP Trunk 3.0 node and thegatekeeper, the IP Trunk node can never register;therefore, the node cannot use the gatekeeper toplace calls. If there is ever a problem withgatekeeper call resolution, check the H.323 IDimmediately.

Primary Gatekeeper information <<PROVISIONED>>------------------------------

Primary Gatekeeper type is : CSE1000

Primary Gatekeeper IP information is :*Gatekeeper IP : 47.11.249.140

*QoS Enabled : 0

*Node Capability : 9 - CSE - Interop Format

Provisioning information about thegatekeeper assigned as the primarygatekeeper (default gatekeeper).

Type of gatekeeper; for IPT 3.0,only gatekeepers performing as perthe CSE 1000 release 2 are supported.

IP address of primary gatekeeper.

Quality of Service “pings” as perIPT/ITGT enabled - not possible atthis time.

Default remote D channel capability(Interop format means that the ISDNmessage is packaged in the non-standard data of the H.323 User-User Information Element as per theNortel Interoperability standard.



naleitch.

racerwise

ingsage

B.1.14 h323CallTrace


This command was formerly itgCallTrace.

The h323CallTrace is the replacement for 2.x.25 routine itgCallTrace, with additiointerface control. The old itgCallTrace function turned on debug tracing for all thH323 channels on the card. This caused a significant real time impact on a busy swThe new command and improved interface permits enabling and disabling call ton a range of channels. The h323CallTrace and its predecessor itgCallTrace otheprovide the same functionality.

Syntax:

h323CallTrace Option, startChannel, endChannel

where:Option -1 = Turn off all channels call tracing

0 = Call tracing off1 = Call trace output sent to TTY2 = Call trace output sent to TRCFILE.1 file3 = Call trace output sent to TTY & TRCFILE.1 file6 = Call trace output sent to CURRLOG.1 & TRCFILE.1

startChannel: 0-23 for Pentium and 0-31 for SAendChannel: 0-23 for Pentium and 0-31 for SA

- startChannel <= endChannel- if the entered endChannel = 0 or the user omits the

endChannel input, the operation applies to only thestartChannel.

ITG> h323CallTrace -1,0,31Setting ALL channels to OFFvalue = 0 = 0x0ITG>

ITG> h323CallTrace 1,3,7Setting CHANNEL 3 to 7 to OPT 1value = 0 = 0x0ITG>

Example of output: incoming call set-up trace

The following gives the results of the h323CallTrace command for a normal incomcall (with near end auto-answer) followed by a far-end release. Note that the meslist has changed significantly since 2.x.25, which was when the last sample wasprovided.



Initialize trace channels: 0 to 5, log to screenITG> h323CallTrace 1,0,5Setting CHANNEL 0 to 5 to OPT 1value = 0 = 0x0

Receive incoming SETUP (to ALERTING)ITG> 2001 3 18 08:41:49 (NPM) :CH#:0 partnerChannelsNum 12001 3 18 08:41:49 (NPM) :CH#:0 partner[0]: transmit[0]: g729AnnexAwAnnexB2001 3 18 08:41:49 (NPM) :CH#:0 partner[0]: transmit[1]: g729AnnexA2001 3 18 08:41:49 (NPM) :CH#:0 partner[0]: transmit[2]: g729wAnnexB2001 3 18 08:41:49 (NPM) :CH#:0 partner[0]: transmit[3]: g7292001 3 18 08:41:49 (NPM) :CH#:0 partner[0]: transmit[4]: g711Ulaw64k2001 3 18 08:41:49 (NPM) :CH#:0 partner[0]: transmit[5]: g711Alaw64k2001 3 18 08:41:49 (NPM) :CH#:0 partner[0]: receive[0]: g729AnnexAwAnnexB2001 3 18 08:41:49 (NPM) :CH#:0 partner[0]: receive[1]: g729AnnexA2001 3 18 08:41:49 (NPM) :CH#:0 partner[0]: receive[2]: g729wAnnexB2001 3 18 08:41:49 (NPM) :CH#:0 partner[0]: receive[3]: g7292001 3 18 08:41:49 (NPM) :CH#:0 partner[0]: receive[4]: g711Ulaw64k2001 3 18 08:41:49 (NPM) :CH#:0 partner[0]: receive[5]: g711Alaw64k2001 3 18 08:41:49 (NPM) :CH#:0 RTP OPEN: hRtp:0x1e25614, socket:35, port:2300.2001 3 18 08:41:49 (NPM) :CH#:0 cmEvChannelParameters,chanName=g729AnnexAwAnnexB,co-dec=72001 3 18 08:41:49 (NPM) :CH#:0 hsChan 0x229f104 haChan 0x3f64902001 3 18 08:41:49 (NPM) :CH#:0 txPayload: 3: vifSize 2402001 3 18 08:41:49 (NPM) :CH#:0 cmEvChannelSetAddress: isOrigin 0 47.11.215.209:23622001 3 18 08:41:49 (NPM) :CH#:0 cmEvChannelParameters,chanName=g729AnnexAwAnnexB,co-dec=72001 3 18 08:41:49 (NPM) :CH#:0 hsChan 0x229f13c haChan 0x3f655c2001 3 18 08:41:49 (NPM) :CH#:0 rxPayload: 3: vifSize 2402001 3 18 08:41:49 (NPM) :CH#:0 *** InterOpt: using H323 codec payload negotation2001 3 18 08:41:49 (NPM) :CH#:0 Call Setup to TSM: g729AnnexAwAnnexB(7): vifSize 2402001 3 18 08:41:49 (NPM) :CH#:0 hsChan 0x229f13c haChan 0x3f655c2001 3 18 08:41:49 (NPM) :CH#:0 cmEvChannelSetAddress: isOrigin 1 47.11.215.209:23622001 3 18 08:41:49 (NPM) :CH#:0 hsChan 0x229f104 haChan 0x3f64902001 3 18 08:41:49 (NPM) :CH#:0 Initiating terminal capability set negotation2001 3 18 08:41:49 (NPM) :CH#:0 codec 0: g729AnnexAwAnnexB(7)2001 3 18 08:41:49 (NPM) :CH#:0 codec 1: g729AnnexA(5)2001 3 18 08:41:49 (NPM) :CH#:0 codec 2: g729wAnnexB(6)2001 3 18 08:41:49 (NPM) :CH#:0 codec 3: g729(4)2001 3 18 08:41:49 (NPM) :CH#:0 codec 4: t38fax(-1)2001 3 18 08:41:49 (NPM) :CH#:0 [1] g729AnnexAwAnnexB: packetSize 3: cmCapAudio: cm-CapReceiveAndTransmit2001 3 18 08:41:49 (NPM) :CH#:0 [2] g729AnnexA: packetSize 3: cmCapAudio: cmCapReceive-AndTransmit2001 3 18 08:41:49 (NPM) :CH#:0 [3] g729wAnnexB: packetSize 3: cmCapAudio: cmCapRe-ceiveAndTransmit2001 3 18 08:41:49 (NPM) :CH#:0 [4] g729: packetSize 3: cmCapAudio: cmCapReceiveAn-dTransmit2001 3 18 08:41:49 (NPM) :CH#:0 [5] g711Ulaw64k: packetSize 10: cmCapAudio: cmCapRe-ceiveAndTransmit2001 3 18 08:41:49 (NPM) :CH#:0 [6] g711Alaw64k: packetSize 10: cmCapAudio: cmCapRe-ceiveAndTransmit2001 3 18 08:41:49 (NPM) :CH#:0 [7] t38fax: packetSize -1: cmCapData: cmCapReceiveAn-dTransmit2001 3 18 08:41:49 (NPM) :CH#:0 Initiating Master/Slave negotation2001 3 18 08:41:49 (NPM) :CH#:0 {g729AnnexAwAnnexB, g729AnnexA, g729wAnnexB, g729,g711Ulaw64k, g711Alaw64k}2001 3 18 08:41:49 (NPM) :CH#:0 {t38fax}



Connect the call2001 3 18 08:42:17 (NPM) :CH#:0 Q931 call setup phase complete2001 3 18 08:42:17 (NPM) :CH#:0 StateMode: cmCallStateModeCallSetupConnected2001 3 18 08:42:17 (NPM) :CH#:0 StateMode: cmCallStateModeCallConnected

Receive incoming RELEASE COMPLETE2001 3 18 08:42:33 (NPM) :CH#:0 hsChan 0x229f13c haChan 0x3f655c2001 3 18 08:42:33 (NPM) :CH#:0 hsChan 0x229f13c haChan 0x3f655c2001 3 18 08:42:33 (NPM) :CH#:0 hsChan 0x229f104 haChan 0x3f64902001 3 18 08:42:33 (NPM) :CH#:0 hsChan 0x229f104 haChan 0x3f64902001 3 18 08:42:33 (NPM) :CH#:0 dch_cap 5: cause 16: reason 32001 3 18 08:42:33 (NPM) :CH#:0 Closing RTP session(0x1e25614).



ess,

asedble

h IP

e

el

sts

ks

B.1.15 h323SessionShow


Lists the details of the h323Session for all active channels – originating IP addrdestination IP address, call state, codec used etc.

Note that by default, ITG will attempt to accept incoming calls in Round RobinFashion starting from the lowest available channel up. Outgoing calls (this time bon the Meridian 1 Round Robin Configuration) will be set-up on the highest availachannels first.

The output includes:

• the call direction (Originating side to Terminating side)

• the remote node IP, which is the signalling IP (which is equal to the media pataddress for IPT to IPT or ITGT)

• the Dest number, which is the transmitted number (and may include ESN5prefixes; the Session 31 in the example does)

• the codec selected

• the Call Handle (possibly useful for design level debugging depending on thproblem, but of little or no use to field support personnel)

• the D channel capability of the remote node:

— 1 - use only standardized H.323; no remote D channel

— 2 - “legacy format” for ITGT 1.0 and non-MCDN BCM; no remote D chann

— 3 - “legacy” format for ITGT 2.x and BCM 2.5 FP1; remote D channel exi

— 4 - not currently used

— 5 - Nortel Networks cross product Interoperability Standard format (IP Trun3.0, SCSE 1000 R2, etc.)

• the “far end software version” data, for fax handling (etc.):

— 1 - third party end-point

— 2 - BCM end-point (all)

— 3 - ITGT 1.0

— 4 - ITGT 2.x.23 and lower

— 5 - ITGT 2.c.24, 2.x.25, and 2.x.26

— 6 - all interoperability format except BCM

ITG> h323SessionShow

Session 0 : ACTIVE



Direction : Terminating Remote IP : 47.11.215.209 Dest Number : 4500 Codec : g729AnnexAwAnnexB Call State : Connected Call Handle : 0x229f2c4 dch_capability: 5 farEndSWVer : 6

Session 1 : IDLE Session 2 : IDLE Session 3 : IDLE Session 4 : IDLE Session 5 : IDLE Session 6 : IDLE Session 7 : IDLE Session 8 : IDLE Session 9 : IDLE Session 10 : IDLE Session 11 : IDLE Session 12 : IDLE Session 13 : IDLE Session 14 : IDLE Session 15 : IDLE Session 16 : IDLE Session 17 : IDLE Session 18 : IDLE Session 19 : IDLE Session 20 : IDLE Session 21 : IDLE Session 22 : IDLE Session 23 : IDLE Session 24 : IDLE Session 25 : IDLE Session 26 : IDLE Session 27 : IDLE Session 28 : IDLE Session 29 : IDLE Session 30 : IDLE Session 31 : ACTIVE Direction : Originating Remote IP : 47.11.215.209 Dest Number : 1003600 Codec : g729AnnexAwAnnexB Call State : Connected Call Handle : 0x229f44c dch_capability: 3 farEndSWVer : 5

value = 1 = 0x1ITG>



d tooccur

ensure

B.1.16 i

Safety level: Debug/recovery.

This command lists all the tasks and task IDs. The user executes this commanmake sure that no task is suspended. (Note that temporary task suspension canwhen the user executes various debug commands; this command helps the userthat no tasks are still suspended.)

ITG> i

NAME ENTRY TID PRI STATUS PC SP ERRNO DELAY---------- ------------ -------- --- ---------- -------- -------- ------- -----tExcTask _excTask 33c8acc 0 PEND 7711c 33c8a00 3006b 0tShell _shell 2eb7558 1 READY 2ad934 2eb71ec c0002 0tPcmciad _pcmciad 33a5d3c 2 PEND 7711c 33a5c70 0 0tTelnetd _telnetd 2ec81a4 2 PEND 4fd38 2ec809c 0 0tTelnetOutT_telnetOutTa 1e296ec 2 READY 4fd38 1e29434 3006b 0tTelnetInTa_telnetInTas 1e281b8 2 READY 2ad450 1e27eb8 0 0tyLstnr _tyListener 1e26c84 2 PEND 4fd38 1e26bc8 0 0tMVX_XSPY _XSpyTaskMai 1e89204 7 PEND 7711c 1e8913c 0 0tNetTask _netTask 30f49f4 20 READY 58080 30f4958 3d 0tRmm _rmmMain 2be7644 40 PEND 4fd38 2be74bc 0 0tAioIoTask1_aioIoTask 33b4694 50 PEND 4fd38 33b4614 0 0tAioIoTask0_aioIoTask 33ad4e8 50 PEND 4fd38 33ad468 0 0tAioWait _aioWaitTask 33bb840 51 PEND 4fd38 33bb718 0 0tMVX_DIM _dim_main 1e86698 51 READY 4fd38 1e86604 3d0002 0tFtpdTask 2c286c 2ec549c 55 PEND 4fd38 2ec5370 0 0tSntpsTask 2b0b80 2bec93c 56 PEND 4fd38 2bec73c 0 0baseMMintTa_baseMMintTa 2ae3c94 60 PEND 4fd38 2ae3c0c 0 0tA07 _a07Task 2ae0674 80 PEND 7711c 2ae05b4 0 0tIpss _ipssMain 1e71c10 80 PEND 4fd38 1e71ad0 0 0tNpm _npmMain 2bd8080 90 PEND 4fd38 2bd7e74 46 0tPortmapd _portmapd 2ec6c70 100 PEND 4fd38 2ec6b04 16 0tXA _xaTask 2abf10c 100 PEND 7711c 2abf034 0 0tATPM _atpmTaskSta 1e744cc 100 PEND 7711c 1e743f4 0 0tTSM _tsmStart 1e6cc44 100 PEND 7711c 1e6cb5c 0 0tMONTimeSer_monTimeServ 1e52770 100 PEND 4fd38 1e525ec 0 0tIGCC _igccMain 2adecec 100 PEND 7711c 2adec14 0 0tUIPC _uipcMain 1e2e154 100 READY 7711c 1e2e090 0 0tMcciMsgMgr_mcciMain 1e3a650 120 PEND 4fd38 1e3a2fc 0 0tLogTask _logTask 33c61b0 150 PEND 7711c 33c60e4 0 0tSnmpd 40f70 2ec23ec 150 PEND 4fd38 2ec1a2c 3d0001 0tSockReuse _finwait 1e4d7a4 150 DELAY 4ba20 1e4d73c 0 17568tRCM _rcmMain 2bf42b4 150 PEND 7711c 2bf41dc 0 0tBootpdTask_vxBootpd 2bede70 199 PEND 4fd38 2bedd00 23 0tMAM _mamMain 2be9f00 200 PEND 7711c 2be9e40 11 0tNMMTask _tNMM 1e8d050 200 PEND 7711c 1e8cf8c 0 0midnightTas_midnightTas 2ea7150 240 DELAY 4ba20 2ea70e8 4 5297143tMONServer _monServerMa 1e5c708 245 PEND 7711c 1e5c644 0 0tHSRecvTask_oobHandShak 2beaf04 249 PEND 4fd38 2bead34 0 0tDcacheUpd _dcacheUpd 3382a9c 250 READY 4ba20 3382a1c 3d0002 0tOMM _ommMain 2bf25b0 250 PEND 7711c 2bf24f0 0 0tMONClient _monClientMa 1e5773c 250 PEND 7711c 1e57678 0 0tMonTask _itgMonitorT 1e2b898 252 DELAY 4ba20 1e2b35c 0 352value = 0 = 0x0ITG>



Onrst isleachcastataere’sdresse

de IP

B.1.17 ifShow

Safety level: Safe/delays in heavy traffic.

This command displays information about the attached network interfaces. Thecurrent parameters configured on the ELAN (lnIsa) and TLAN (lnPci) are printed.the current Master card, two Internet addresses print for the lnPci interface: the fithe card’s TLAN interface IP, the second is the Node IP. Note: “lo” is the internasoftware loopback interface. The ethernet address (MAC address) is printed forinterface. A large number of multicast packets received indicates a lot of broadtraffic on the interface - not a good thing for the ITG card! If no lnPci interface dprints, the card did not boot up correctly and the interface is not configured. Tha good chance the card’s management MAC address doesn’t match the MAC adconfigured in MAT/OTM; if that’s true, correct it in MAT/OTM, download the Nodproperties and reboot the card.

The example below is from a Succession Media Card, Node Leader - note the Noaddress on the ixpMac unit 0 interface.

ITG> ifShowixpMac (unit number 1): Flags: (0x8863) UP BROADCAST MULTICAST ARP RUNNING Type: ETHERNET_CSMACD Internet address: 47.11.217.55 Broadcast address: 47.11.217.255 Netmask 0xff000000 Subnetmask 0xfffffe00 Ethernet address is 00:60:38:bd:fb:32 Metric is 0 Maximum Transfer Unit size is 1500 810168 packets received; 7115 packets sent 799843 multicast packets received 0 multicast packets sent 0 input errors; 0 output errors 0 collisions; 0 droppedlo (unit number 0): Flags: (0x8069) UP LOOPBACK MULTICAST ARP RUNNING Type: SOFTWARE_LOOPBACK Internet address: 127.0.0.1 Netmask 0xff000000 Subnetmask 0xff000000 Metric is 0 Maximum Transfer Unit size is 32768 6577 packets received; 6577 packets sent 0 multicast packets received 0 multicast packets sent 0 input errors; 0 output errors 0 collisions; 0 droppedixpMac (unit number 0): Flags: (0x8863) UP BROADCAST MULTICAST ARP RUNNING Type: ETHERNET_CSMACD Internet address: 47.11.215.212 Broadcast address: 47.11.215.255 Internet address: 47.11.215.211 Broadcast address: 47.11.215.255 Netmask 0xff000000 Subnetmask 0xffffff00 Ethernet address is 00:60:38:bd:fb:31



dress

Metric is 0 Maximum Transfer Unit size is 1500 801318 packets received; 11289 packets sent 799746 multicast packets received 5 multicast packets sent 0 input errors; 0 output errors 0 collisions; 0 droppedvalue = 29 = 0x1dITG>

The example below is from a Pentium card, Node Leader - note the Node IP adon the lnIsa unit 0 interface.

ITG> ifShowlnIsa (unit number 0): Flags: (0x863) UP BROADCAST ARP RUNNING Type: ETHERNET_CSMACD Internet address: 47.11.254.50 Broadcast address: 47.11.255.255 Netmask 0xff000000 Subnetmask 0xfffffe00 Ethernet address is 00:60:38:8e:15:b7 Metric is 0 Maximum Transfer Unit size is 1500 1942016 packets received; 101561 packets sent 1742551 multicast packets received 0 multicast packets sent 0 input errors; 0 output errors 0 collisions; 0 droppedlo (unit number 0): Flags: (0x8069) UP LOOPBACK MULTICAST ARP RUNNING Type: SOFTWARE_LOOPBACK Internet address: 127.0.0.1 Netmask 0xff000000 Subnetmask 0xff000000 Metric is 0 Maximum Transfer Unit size is 32768 43395 packets received; 43395 packets sent 0 multicast packets received 0 multicast packets sent 0 input errors; 0 output errors 0 collisions; 0 droppedlnPci (unit number 1): Flags: (0x863) UP BROADCAST ARP RUNNING Type: ETHERNET_CSMACD Internet address: 47.11.249.44 Broadcast address: 47.11.249.255 Internet address: 47.11.249.43 Broadcast address: 47.11.249.255 Netmask 0xff000000 Subnetmask 0xffffff00 Ethernet address is 00:60:38:bd:06:d8 Metric is 0 Maximum Transfer Unit size is 1500 3332461 packets received; 1077458 packets sent 2306340 multicast packets received 0 multicast packets sent 0 input errors; 0 output errors 0 collisions; 0 droppedvalue = 29 = 0x1dITG>



GT

ed.

B.1.18 IPInfoShow

Safety level: Safe.

This command displays a summary of the ITG card’s IP configuration from the ITprompt.

The difference between the SMC and Pentium card output is in the “Interface” listFor the SMC card, the following output is seen:

ITG> IPInfoShowSeparate Subnet Configuration.Maintenance IP address : 47.11.217.55Voice IP address : 47.11.215.212

Maintenance subnet mask : 255.255.254.0Voice subnet mask : 255.255.255.0

ROUTE NET TABLEdestination gateway flags Refcnt Use Interface----------------------------------------------------------------------------0.0.0.0 47.11.215.1 3 4 10163 ixpMac047.11.215.0 47.11.215.212 101 0 0 ixpMac047.11.216.0 47.11.217.55 101 0 0 ixpMac147.11.215.0 47.11.215.212 101 0 0 ixpMac0----------------------------------------------------------------------------

ROUTE HOST TABLEdestination gateway flags Refcnt Use Interface----------------------------------------------------------------------------127.0.0.1 127.0.0.1 5 0 0 lo0----------------------------------------------------------------------------value = 77 = 0x4d = ’M’ITG>



For the Pentium card, the following is seen instead:

ITG> IPInfoShowMaintenance IP address : 47.11.254.50Voice IP address : 47.11.249.44

Maintenance subnet mask : 255.255.254.0Voice subnet mask : 255.255.255.0

ROUTE NET TABLEdestination gateway flags Refcnt Use Interface----------------------------------------------------------------------------0.0.0.0 47.11.249.1 3 1 177 lnPci147.11.249.0 47.11.249.44 101 0 0 lnPci147.11.254.0 47.11.254.50 101 0 0 lnIsa047.11.249.0 47.11.249.44 101 0 0 lnPci1----------------------------------------------------------------------------

ROUTE HOST TABLEdestination gateway flags Refcnt Use Interface----------------------------------------------------------------------------127.0.0.1 127.0.0.1 5 0 0 lo0----------------------------------------------------------------------------value = 77 = 0x4d = 'M'ITG>



Itther

lingle

B.1.19 iptSessionShow [level]


This command is analogous to h323SessionShow, with somewhat differentcapabilities. It has either more information (level 1) or less (level 0, or default).also provides an “options” display, used by entering the command with a level othan 0 or 1.

Example: “what are my options?”

ITG> iptSessionShow 44iptSessionShow parameter errorThe Options are:* For basic information, Specify 0 or leave blank* For debug information, Specify 1* For this message, Specify anything elsevalue = 50 = 0x32 = ’2’ITG>

Example: “show me the basics only”. This shows the direction, remote call signalIP address, and destination number for the currently active calls, with a list of idchannels following.

ITG> iptSessionShow

- - - - - - - - - - - - - - - - - - - - - - - - - - -iptSessionShow basic only

Ses 0 : ACTIVE Direction : Terminating Remote IP : 47.11.215.209 Dest Number : 4500

Ses 31 : ACTIVE Direction : Originating Remote IP : 47.11.215.209 Dest Number : 1003600

IDLE: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23- - - - - - - - - - - - - - - - - - - - - - - - - - -value = 55 = 0x37 = ’7’ITG>



ing323

ility.

Example: “show me the full details”. This shows the direction, remote call signallIP address, destination number (with type and plan), “outpulsed number” (if the H.stack had to manipulate the number), originating number (with type and plan),selected (or negotiated) codec, H.323 call state, call handle, and the remote capabIt also includes a list of the idle channels.

ITG> iptSessionShow 1

- - - - - - - - - - - - - - - - - - - - - - - - - - -iptSessionShow - 2001 3 19 05:40:26 (NPM) :

Ses 0 : ACTIVE Direction : Terminating Remote IP : 47.11.215.209 Dest Number : 4500 Plan: Unknown; Type Unknown Orig Number : 3500 Plan: Unknown; Type Unknown Codec : g729AnnexAwAnnexB Call State : Connected Call Handle : 0x229d1b8 Remote capability: legacy ISDN gateway

Ses 31 : ACTIVE Direction : Originating Remote IP : 47.11.215.209 Dest Number : 1003600 Plan: Private; Type CDP Orig Number : 4600 Plan: Private; Type CDP Codec : g729AnnexAwAnnexB Call State : Connected Call Handle : 0x229ce38 Remote capability: legacy ISDN gateway

IDLE: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23- - - - - - - - - - - - - - - - - - - - - - - - - - -value = 55 = 0x37 = ’7’ITG>



nd theata

s.

B.1.20 itgCardShow


Check the Leader, Card and Management IP, codecs configured, protocol used astatus of the ELAN and TLAN connections. The following is an example of the dprinted, followed by an explanation of the fields.

Note that the output is slightly different when comparing Pentium and SMC card

Pentium card output

-> itgCardShow

Index : 1 Type : ITG2 Role : Backup Leader Leader IP : 47.11.249.43 RTP Base Port: 2300,:2300=>Default,17300=>CISCO RTPHeader Compression Card IP : 47.11.249.44 Card MgntIP : 47.11.254.50 Ldr MgntIP : 47.11.255.175 Card TN : 5 0 0 Card State : ENBL Card Mode : Normal Codecs : G711Ulaw(default), G711Alaw EC Tail Length: Value from OTM - 32ms Local RingBack: IP Trunk Card Dchip IP : 47.11.254.50 Dch Num : 3 Dch On Card: YES (version 3.1) Dch Status : ENBL Protocol : SL1 initBchNum : 1 esn5Prefix : |100| Accounting : 47.11.217.39:1813 lnPci stat : 100 Mbps (Carrier OK) lnPci set to Auto-Negotiate Speed and Duplex Settings lnPci BCast Filter: On lnIsa stat : Carrier OKvalue = 38 = 0x26 = ’&’

SMC card output

ITG> itgCardShow

Index : 1 Type : ITG2 Role : Leader Leader IP : 47.11.215.211 RTP Base Port : 2300,2300=>Default, 17300=>CISCO RTPHeader Compression Card IP : 47.11.215.212 Card MgntIP : 47.11.217.55 Ldr MgntIP : 47.11.217.55 Card TN : 6 0 0



beenP

itsthet is onif

heportbled

onh theted,

ptop

ifiess or

Card State : ENBL Card Mode : Normal Codecs : G729AB(default), G729A EC Tail Length: Value from OTM - 32ms Local RingBack: IP Trunk card Dchip IP : 47.11.217.24 Dch Num : 5 Dch On Card : YES (version 3.1) Dch Status : ENBL Protocol : SL1 ESN5 initBchNum : 1 esn5Prefix : |100| Accounting : 47.11.217.39:1813 TLAN set to Auto-Negotiate Speed and Duplex Settings TLAN currently operate at: 100 Mbps (Carrier OK) ELAN set to 10BaseT Operation ELAN set to Half Duplex Operationvalue = 38 = 0x26 = ’&’ITG> Dch On Card: YES (version 3.1)

NOTEs:

1. If the Card IP address is 0.0.0.0:

a. Leader card: this indicates either the BOOTP.1 file is missing or has not parsed properly. Check to make sure that the bootp.1 file is in the BOOTdirectory. Look for alarms / error messages on the TTY console.

b. Follower or Backup Leader card: this indicates the card could not locate BOOTP server/Leader card or could not communicate with it. Ensure thatLeader card has the Follower/Backup Leader entry in its bootp.1 file. If thaok, check all the cable connections (TLAN). Next check for error/alarmsthe TTY console and MAT. May need to log the RMM and MAM modulesthe problem persists.

2. RTP Port Range:

Identifies what the IP port range is on the T-LAN interface for RTP packets. Tdefault uses port ranges from 2300 to 2346. It can be optionally configured forranges from 17300 to 17346 which will support RTP Header Compression enarouters.

3. DCHIP is YES and Version is 0.0: DCHIP YES indicates that it is configuredthe card. Version 0.0 indicates that the card cannot establish connection witDCH PC Card. It indicates either the PC Card is missing, is not properly seahas no software load on it or is bad. The PC Card can be inserted into any lato verify the software on the card.

4. EC Tail Length:

This is applicable only to ITG2.0 Pentium and 80486 based Products. It identthe currently configured Echo Canceller Tail Length (either a default of 128ma value as presented by the OTM/MAT configuration).

5. Ethernet interface carrier status:



that

nelr

ing

ied:

e

as

liedadednd

IP

lnPci Stat – interface speed and carrier status of the TLAN interface.

lnPci BCast Filter - only refers to ITG2.0 Pentium cards. This identifies thatphysical layer Broadcast filtering is enabled on the card, to be activated inBroadcast storm conditions.

lnIsa Stat – the status of the carrier of the ELAN interface.

If the carrier is not OK for an interface, check the cable and hub connected tointerface.

6. initBchNum: Is the first B channel number on the card. The rest of the B channumbers are consecutive. This number should match the B channel numbeconfigured on M1.

7. Card State:

ENBL : The card is configured and operational

DSBL : The card is configured but out of service. Enable from M1.

UNEQ : The card is not configured in M1.

MBSY : The card is busy / no channels available as some system utility is runnin the background.

FALLBACK : The card is out of service as all the available channels are busout. All calls are routed via PSTN. The reason could be one of the following

a. The card has lost communication with the Leader card (TLAN or ELAN).Check the physical connections and alarm logs.

b. The network cannot support the requested quality of service for all remotnodes. Check the network conditions/ traffic.

8. In IP Trunk 3.0 there is now the additional field of “Local RingBack”. In priorversions of ITG Trunk, if local ringback was required (out of band ringback), it walways generated on ITG Trunk card. In IP Trunk 3.0, the locally generatedringback on the IP Trunk card can be turned off and the Meridian 1 can be reupon to generate local ringback. The Meridian 1 needs to be patched or upgrto Release 26 to allow this to happen. By relying on the Meridian 1 for out of baringback the correct local ringback will be used instead of the default NorthAmerican ringback. For more information about disabling local ringback on theTrunk card see commandsuseIPTForRingBack (section B.1.44, pg 169) anduseM1ForRingBack (section B.1.45, pg 169).



n thenel is

4

the

d by

d by

B.1.21 itgChanStateShow

Safety level: Safe.

This command lists the state – busy / idle / mbsy / uneq – for all the channels ocard. This helps the user see if there are active calls on the card or which chanbeing used by the call etc. The user can ensure the IPT trunk is being seized.

The states translate as:

• Busy - channel in use

• Idle - channel available for a new call

• Mbsy - maintenance busy - channel is unavailable for use

• Uneq - unequipped - not provisioned

Note that a channel can be marked busy when:

• the channel has an active call,

• for the Succession Media Card, if image 2 (G.723) is configured, then everyth

unit will always be busy1,

• for the ITG-P (Pentium) card, if image 3 (G.729) is configured, then every 3rd unitwill always be busy2, or

• the DCH is down, then all units on the associated Followers will be busy.

The following example shows a Pentium card application of this command. OnSMC card the operation and result are the same, except that more channels aredisplayed.

ITG> itgChanStateShow

Channel 0 : Busy Channel 1 : Idle Channel 2 : Idle Channel 3 : Idle Channel 4 : Idle Channel 5 : Idle Channel 6 : Idle Channel 7 : Idle Channel 8 : Idle Channel 9 : Idle Channel 10 : Idle Channel 11 : Idle Channel 12 : Idle Channel 13 : Idle Channel 14 : Idle Channel 15 : Idle

1. Due to codec support on DSP processing, MIPS requirement, the max supported channels per DSP is reduceone.

2. Due to codec support on DSP processing, MIPS requirement, the max supported channels per DSP is reduceone.



G

Channel 16 : Idle Channel 17 : Idle Channel 18 : Idle Channel 19 : Idle Channel 20 : Idle Channel 21 : Idle Channel 22 : Idle Channel 23 : Idle

value = 1 = 0x1

B.1.22 itgMemShow


This command prints general information on the Mix memory available on the ITcard.• total amount of Mix memory blocks configured.• amount of memory blocks available.

ITG> itgMemShow

+--------------------------------------------------+ | PID STATE UNIT TOTAL FREE LOWEST | +--------------------------------------------------+ | 0x7228d8 Active 64 800 789 701 | +--------------------------------------------------+ | 0x722900 Active 256 800 794 790 | +--------------------------------------------------+ | 0x722928 Active 512 3200 3198 3179 | +--------------------------------------------------+ | 0x722950 Active 1024 100 100 100 | +--------------------------------------------------+

value = 1 = 0x1



layed

he IP

he IP

byhe

anslate

B.1.23 itgMsgCtrShow


Various message counters kept by the different tasks on the ITG card can be dispusing this command. Note:

Number of hooksend ISDN messages:

indicates the number of messages of the listed types sent by H.323 to the IPnetwork

Number of hookrecv ISDN messages:

indicates the number of messages of the listed types received by H.323 from tnetwork

Number of corrupted messages:

indicates the number of messages of the listed types received by H.323 from tnetwork that were invalid due to message corruption

Port 0: Message Log

indicates the number of messages of the listed types transmitted or receivedthe ISDN layer 3 application. “CC” is from the application; the rest are from tPBX. See example:

CC Disconnect Request 34223

indicates 34223 DISCONNECT messages sent to the PBX

DISCONNECT 4

indicates 4 DISCONNECT messages received from the PBX

The balance of the messages are internal to the application. The messages tras “From task” “To task” “Message type”. Or, to use an example,

IgccTsmCallSetup = “IGCC” “TSM” “Call Setup”

or a Call Setup from the IGCC to the TSM.



nodets all ofss

eenigate

ave

B.1.24 ldrResTableShow


Most nodes have either one or a small number of cards per node. If an IPT 3.0has more than one card in the system, then this table (on the Leader card only) lisof the ITG cards in the node with their IP address, associated DCH and numbertrunks. If a card doesn’t appear that should be there, then the registration procebetween the Follower and Leader was not successful.

(An explanation of the fields follows the examples below.)

The following is an example displaying a single card node; if there should have bmore, then the specific “missing” card is unregistered, and the user should investfurther.

ITG> ldrResTableShow

+---+-------+----------------+----------------+-----+-----+----+-------+-------+ |idx| role | ipAddr | ipDCHIP |#Prvs|#Idle|DCH#| Dstat | DCAP | +---+-------+----------------+----------------+-----+-----+----+-------+-------+ |1 |L/DCH |47.11.215.212 |47.11.217.55 |32 |30 |6 |ENBL |DCH/ON | +---+-------+----------------+----------------+-----+-----+----+-------+-------+

value = 1 = 0x1ITG>

The following is an example showing a two card node. Again, if there should hbeen more, then the specific “missing” card is unregistered, and the user shouldinvestigate further.

ITG> ldrResTableShow

+---+-------+----------------+----------------+-----+-----+----+-------+-------+ |idx| role | ipAddr | ipDCHIP |#Prvs|#Idle|DCH#| Dstat | DCAP | +---+-------+----------------+----------------+-----+-----+----+-------+-------+ |1 |BL/DCH |47.11.249.44 |47.11.254.50 |24 |24 |3 |ENBL |DCH/ON | +---+-------+----------------+----------------+-----+-----+----+-------+-------+ |2 |L |47.11.239.29 |47.11.254.50 |32 |32 |3 |ENBL |DCH/OFF| +---+-------+----------------+----------------+-----+-----+----+-------+-------+

value = 1 = 0x1ITG>



e

ew

The following provides a description of the headers and row contents:

B.1.25 ll


This command lists the contents of the current directory, with timestamp and sizinformation. Besides allowing comparison of a file’s timestamp to another, thiscommand is useful in checking for zero length files which may indicate diskcorruption (see section “15 Formatting the /C: Drive” on page 96 for details) or a nsystem (for example, DPTABLE.1 is zero length until the dial pan information isdownloaded to the system).

The example shows a list of the BOOTP directory.

ITG> pwd/C:/bootpvalue = 10 = 0xaITG> lldrwxrwxrwx 1 0 0 4096 Feb 10 12:00 ./drwxrwxrwx 1 0 0 4096 Mar 16 03:40 ../-rwxrwxrwx 1 0 0 241 Feb 10 12:00 BOOTP.1-rwxrwxrwx 1 0 0 249 Feb 10 11:56 BOOTP.2value = 0 = 0x0ITG>

Table 4: Explanation of information in the ldrresTableShow output

Field Description

idx Card index

role Card role (Ldr, D-channel leader, Flr)

ipAddr Card’s voice interface IP address

ipDCHIP IP address for card’s DCHIP leader (ELAN)

#Prvs Number of provisioned channels

#Idle Number of channels idle

DCH# DCH number this card is associated with

Dstat Status of that DCH

DCAP Configured DCH capability



first

Also,

g a

ut tor as a

and

.

B.1.26 numNodesInFallbackShow


This command prints all the remote IP that are in fallback at a given time. The example shows the command issued when there are no nodes in fallback.

ITG> numNodesInFallbackShowNodes In Fallback = 0

value = 1 = 0x1ITG>

This example shows the command issued when there is one node in fallback. for the sake of illustrating it in the VxWorks shell, it is shown at the -> prompt.


44.11.223.221value = 1 = 0x1->

B.1.27 NVRClear

Safety level: Destructive/Debug. May be used as part of the process of makincard into a leader; recommended not to use this, though.

Erases the ELAN IP data, Leader flag and returns the shell login and shell timeotheir default values. Be careful when using this because it makes the card appeaFollower but won’t do a BOOTP request. It is better to use theclearLeader (sectionB.1.7, pg 122) command if returning a Leader card to Follower status or the commshellPasswordNvramClear (section B.2.55, pg 222) if trying to reset the shellpassword. If it is used to cleanup the NVRAM, follow it with theclearLeader orsetLeader “IPaddr”,”gwIPaddr”,”subnetMask” (section B.1.39, pg 165) command

ITG> NVRIPShowIP address : 192.168.1.14Gateway : 192.168.1.1Subnet Mask: 255.255.255.128Set as Leader.Set to use IP address parameters in NVRAM.value = 43 = 0x2b = '+'

ITG> NVRClearvalue = 0 = 0x0

ITG> NVRIPShowIP address : 255.255.255.255Gateway : 0.0.0.0Subnet Mask: 0.0.0.0Set as Follower.Warning : Set as Follower, but will boot using IP parameters in NVRAM instead of bootp.



to

value = 88 = 0x58 = 'X'

B.1.28 NVRGWSet “gwIPaddr”

Safety level: Destructive/Debug.

Sets the card’s ELAN gateway IP address in the NVRAM. It may cause cards become unavailable if invalid addresses are entered.

By preference, usesetLeader “IPaddr”,”gwIPaddr”,”subnetMask” (section B.1.39,pg 165) instead.



e

ng.

me

B.1.29 NVRIPSet “IPaddr”


Sets the card’s ELAN IP address in the NVRAM. It may cause cards to becomunavailable if invalid addresses are entered.


B.1.30 NVRIPShow


Prints the information programmed in the card’s NVRAM. This is useful when tryito determine if the data configured via thesetLeadercommand is correct on the card

ITG> NVRIPShowIP Address from NVRAM: 47.11.217.55IP address : 47.11.217.55Gateway : 47.11.217.1Subnet Mask: 255.255.254.0Set as Leader.Set to use IP address parameters in NVRAM.value = 43 = 0x2b = ’+’ITG>

B.1.31 NVRSMSet “subnetMask”


Sets the card’s ELAN subnet mask in the NVRAM. It may cause cards to becounavailable if invalid masks are entered.




cifiedess 5

sts or

dd from

only

and

B.1.32 ping“IPaddr”, numPings

Safety level: Safe.

This command sends an ICMP ECHO_REQUEST packets to a network host, speby the parameterIPaddr in dotted notation. The host matching the destination addrin the packets responds to the request. If a response is not returned in less thanseconds, the sender times out. This command is useful to determine if other hoITG cards are properly communicating with the sender card.

The parameternumPings specifies how many packets to receive; if omitted, pingscontinue until stopped by enteringCtrl-C. Otherwise, pings are sent until the specifienumber of responses are received. The percentage packet loss is then calculatethe ratio of received to sent messages.

ITG> ping “10.0.0.2”,5PING 10.0.0.2: 56 data bytes64 bytes from 10.0.0.2: icmp_seq=0. time=0. ms64 bytes from 10.0.0.2: icmp_seq=1. time=0. ms64 bytes from 10.0.0.2: icmp_seq=2. time=0. ms64 bytes from 10.0.0.2: icmp_seq=3. time=0. ms64 bytes from 10.0.0.2: icmp_seq=4. time=0. ms----10.0.0.2 PING Statistics----5 packets transmitted, 5 packets received, 0% packet lossround-trip (ms) min/avg/max = 0/0/0value = 0 = 0x0

B.1.33 pwd


This command shows the current directory path. Note that if the path shown is host: you’ll need tocd “/C:” to make the other directories visible.

ITG> pwd/C:/bootpvalue = 10 = 0xaITG>

B.1.34 resetOM


This command writes the current OM counter values to the OMREPORT.nnn fileresets the counters to zero.

ITG> resetOMvalue = 0 = 0x0ITG>



dableo a

cane

uilds

theic

B.1.35 routeAdd “destIPaddr”, “ gwIPaddr”

Safety level: Safe.

Adds a route to the network routing tables. The parameterdestIPaddr is thedestination IP address in dotted notation;gwIPaddris the gateway IP address in dottenotation. This change is not permanent; rebooting the card rebuilds the routing tfrom the data in the CONFIG1.INI file. However, if necessary it can be added tstartup file.

ITG> routeAdd “192.168.1.128”,”192.168.1.140”value = 0 = 0x0

B.1.36 routeDelete “destIPaddr”, “ gwIPaddr”

Safety level: Destructive/Debug. This has an immediate, permanent effect, andlead to call processing and/or system administration problems if thwrong route entries are deleted.

This command deletes a route from the network routing tables. The parameterdestIPaddris the destination IP address in dotted notation;gwIPaddris the gateway IPaddress in dotted notation. This change is not permanent; rebooting the card rebthe routing table from the data in the CONFIG.INI file.

ITG> routeDelete “192.168.1.128”,”192.168.1.140”value = 0 = 0x0

B.1.37 routeShow


This command prints the card's IP network and host routing tables. By readingoutput the user may verify that all of the configured routes as well as the dynamroutes are in the table.

ITG> routeShow

ROUTE NET TABLEdestination gateway flags Refcnt Use Interface----------------------------------------------------------------------------0.0.0.0 47.11.215.1 3 4 10895 ixpMac047.11.215.0 47.11.215.212 101 0 0 ixpMac047.11.216.0 47.11.217.55 101 0 0 ixpMac147.11.215.0 47.11.215.212 101 0 0 ixpMac0----------------------------------------------------------------------------

ROUTE HOST TABLEdestination gateway flags Refcnt Use Interface----------------------------------------------------------------------------127.0.0.1 127.0.0.1 5 0 0 lo0----------------------------------------------------------------------------value = 77 = 0x4d = ’M’



ard

id andAM.

B.1.38 serialNumShow

Safety level: Safe.

Displays the ITG card’s serial number data.

ITG> serialNumShowSerial Number : NNTMEJ00BFA5 200250

value = 39 = 0x27 = ’’“ITG>

B.1.39 setLeader “IPaddr”,”gwIPaddr”,”subnetMask”

Safety level: Normal for a new installation; otherwise, Destructive.

Stores all the necessary information in the card’s NVRAM so that on reboot the ccomes up as a Leader 0. The parameterIPaddr is the card’s ELAN IP address,gwIPaddris the ELAN gateway IP address andsubnetMaskis the ELAN subnet mask.This command also sets the Leader flag and the BOOTP flag such that the IPinformation is retrieved from the NVRAM instead of sending a BOOTP request.

ITG> setLeader “47.11.217.183”,”47.11.216.1”,”255.255.254.0”IP Address from NVRAM: 47.11.217.183IP address : 47.11.217.183Gateway : 47.11.216.1Subnet Mask: 255.255.254.0Set as Leader.Set to use IP address parameters in NVRAM./C:/ - Volume is OKSettings will take effect on card reboot.value = 43 = 0x2b = ’+’

B.1.40 shellPasswordSet

Safety level: Debug; implications at user login.

This command sets the ITGT shell access userid and password. The new userpassword must be between 8 and 10 characters. They are both stored in the NVRThe new userid and password take effect the next time you login.

See VxWorks shell commandshellPasswordNvramClear (section B.2.55, pg 222).

ITG> shellPasswordSetEnter current username:itgadminEnter current password:Enter new username:itgadmin1Enter new password:Enter new password again to confirm:value = 0 = 0x0ITG>



rde to

ver,

he

PTe 3d

B.1.41 swDownload “srvrIP”, “ uid”, “ passwd”, “ path”, “ fname”

Safety level: Destructive/Normal. Normal means of placing software on the cawhen not using OTM server; however, it leaves the card vulnerabla reboot in mid-download.

This command downloads the IPT application binary from the specified FTP sercompresses it and stores it in the ITG card’s Flash memory. The parametersrvrIP isthe FTP server’s IP address, the parametersuid andpasswd are used to login to theserver,pathandfnameare the path and name of the file on the server to retrieve. Tcommand executes from the IPT, VxWorks and BIOS CLIs.

— File is on the ITG's /C: drive (previously FTP’d there):ITG> swDownload “127.0.0.1”,”itgadmin”,”itgadmin”,”<path>”,”<fname>”

— File is on another ITG's /C: drive (previously FTP’d there):ITG> swDownload “<ITG ELAN IPaddr>”,”itgadmin”,”itgadmin”,”<path>”,”<fname>”

— File is on the MAT/OTM PC:ITG> swDownload “<PC’s IP addr>”,”itguser”,”itguser”,”addr>”,”itguser”,”itgus-er”,””,”<fname>”

— File is on a network FTP server:ITG> swDownload “<server’s IP addr>”,”<uid>”,”<pswd>”,”<path>”,”<fname>”

B.1.42 swVersionShow

Safety level: Safe.

This command prints the card’s ITGT application software version. Note that for I3.0, the issue includes the date built. In the example, the load was compiled on thof March, 2003.

ITG> swVersionShowInstalled Image: IPT IPT-3.00.52_03_06_2003.522 (ITG SA) - Thursday March 615:54:40 EST 2003value = 99 = 0x63 = ’c’ITG>



t isside

B.1.43 tsmChanShow [level[,channel]]

Safety level: Debug; may slow traffic under heavy load.

This command prints the TSM (Telephony Signalling Module) view of the calls. Ianalogous to h323SessionShow, but for the call states and information on the PBXof the IPT 3.0 application.

level:

• 0, default - basic level only, all channels

• 1 - detailed, all channels

• 2,channel - detailed, for the indicated channel only

• other value: “help”

ITG> tsmChanShow 22tsmChanShow ErrorFormat: tsmChanShow <option> [<channel>]The Options are: For this message, specify h or any invalid option For non-idle channels, specify 0 or leave blank To include a list of idle channels, specify 1 For a specific channel, specify 2 and add the channel

Examples of valid input: tsmChanShow<CR> tsmChanShow 0<CR> tsmChanShow 1<CR> tsmChanShow 2,7<CR> (print index 7, channel 8)value = 50 = 0x32 = ’2’ITG>ITG>ITG> tsmChanShow

===== TSM Channel Info - tsmChanShow =====Ch 0: IP originated call, state: SPU_CALL_CONN Called: Unknown plan, Unknown type, digits: 4500 Calling: Unknown plan, Unknown type, digits: 3500 CodecUsed: G711 AlawCh 31: M1 originated call, state: SPU_CALL_CONN Called: Private plan, (null) type, digits: 3600 Outpulsed: digits: 1003600 Calling: Private plan, (null) type, digits: 4600 CodecUsed: G711 Alaw

===========================value = 29 = 0x1dITG>ITG>ITG>



ITG> tsmChanShow 1

===== TSM Channel Info - tsmChanShow =====Ch 0, tcid 0, IP originated call; state: SPU_CALL_CONN Called: Unknown plan, Unknown type, digits: 4500 Calling: Unknown plan, Unknown type, digits: 3500 CodecUsed: G711 AlawCh 31, tcid 31, M1 originated call; state: SPU_CALL_CONN Called: Private plan, (null) type, digits: 3600 Outpulsed: digits: 1003600 Calling: Private plan, (null) type, digits: 4600 CodecUsed: G711 Alaw

===========================No undefined channels

No disabled channels

Idle channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 2728 29 30

value = 2 = 0x2ITG>ITG>ITG> tsmChanShow 2,31

===== TSM Channel Info - tsmChanShow =====Ch 335852 (tcid 31:) is in state: SPU_CALL_CONN Called: Private plan, (null) type, digits: 3600 Outpulsed: digits: 1003600 Calling: Private plan, (null) type, digits: 4600 CodecUsed: G711 Alaw DSP mode 5, Tx gain: 0; Rx gain fffffffa (db)

===========================value = 29 = 0x1dITG>



d.

dcarde.

ted.

.hen

By

ring

that

.hen

B.1.44 useIPTForRingBack

Safety level: Safe.

This command is used to turn on local ring back generation on the IP Trunk car

By default, the IP Trunk card will continue generate local ringback for out of banringback. This command is only of use if local ringback has been turned off on theby the command “useM1ForRingBack” or by an attribute in the CONFIG1.INI fil

The issue with using the IP Trunk card is that North American ringback is generaIf this is an issue, the customer needs to patch the Meridian 1 to generate localringback and use the command “useM1ForRingBack”.

Although, it should be noted that ITG Trunk and IP Trunk use “in band” ringbackThat is, the ringback comes from the destination side in the voice path. It is only winteroperating with other endpoints that out of band ring back may be used.

Another important point, is this command only is in effect until the card resets.

B.1.45 useM1ForRingBack

Safety level: Safe.

This command is used to turn off local ring back generation on the IP Trunk card.default, the IP Trunk card will generate local ringback for out of band ringback.

This command will only be in effect until the card resets. Another method of ensuthat the M1 is used for local ringback is to add to CONFIG1.INI the lines:

[LocalRingBack]M1GeneratesRingBack=1

The need to rely upon the Meridian 1 to generate local ring back is due to the issuethe IP Trunk card only generates North American ringback.

If this is an issue, the customer needs to patch the Meridian 1 to generate localringback and use this command.

Although, it should be noted that ITG Trunk and IP Trunk use “in band” ringbackThat is, the ringback comes from the destination side in the voice path. It is only winteroperating with other endpoints that out of band ring back may be used.



B.1.46 vxWorksShell


Use this command to login and access the OS shell when doing debugging ofcommands that require this shell.

ITG> vxWorksShell

login:<login user name>password:<login password>Welcome to the VxWorks ShellWARNING: Data entry errors in this shell could cause loss of service.Use itgShell to return to the ITG shell.value = 3382232 = 0x339bd8 = _shellHistSize + 0x4



yed

tries

B.2 Commands only accessible from the -> prompt

B.2.1 arpFlush

Safety level: Safe/delay. calls to addresses flushed from the memory will be delaslightly, but the table rebuilds itself.

Flushes all non-permanent entries from the card’s ARP cache. “Permanent” enare added via provisioning operations; all others are non-permanent.

-> arpShow

LINK LEVEL ARP TABLEdestination gateway flags Refcnt Use Interface--------------------------------------------------------------------------192.168.1.10 00:00:75:45:38:aa 405 1 1081508 lnIsa0192.168.1.14 00:60:38:01:09:fa 405 2 1836 lo0192.168.1.102 00:c0:4f:ae:a8:39 405 1 3 lnIsa0192.168.1.140 00:60:38:01:a1:46 405 0 6 lo0192.168.1.141 00:60:38:76:21:af 405 0 201 lnPci1192.168.1.142 00:60:38:76:21:a9 405 3 136956 lnPci1--------------------------------------------------------------------------value = 75 = 0x4b = 'K'->-> arpFlushvalue = 0 = 0x0-> arpShow

LINK LEVEL ARP TABLEdestination gateway flags Refcnt Use Interface--------------------------------------------------------------------------192.168.1.14 00:60:38:01:09:fa 405 2 1936 lo0192.168.1.140 00:60:38:01:a1:46 405 0 6 lo0--------------------------------------------------------------------------value = 75 = 0x4b = 'K'->

B.2.2 arpShow

Safety level: Safe

Displays the current entries in card’s system ARP table.-> arpShow

LINK LEVEL ARP TABLEdestination gateway flags Refcnt Use Interface--------------------------------------------------------------------------192.168.1.10 00:00:75:45:38:aa 405 1 1081508 lnIsa0192.168.1.14 00:60:38:01:09:fa 405 2 1836 lo0192.168.1.102 00:c0:4f:ae:a8:39 405 1 3 lnIsa0192.168.1.140 00:60:38:01:a1:46 405 0 6 lo0192.168.1.141 00:60:38:76:21:af 405 0 201 lnPci1192.168.1.142 00:60:38:76:21:a9 405 3 136956 lnPci1--------------------------------------------------------------------------value = 75 = 0x4b = 'K'->



tedne.

rson.

B.2.3 attrib “filename”,“protection”

Safety level: Destructive Debug. The user can make a file that should be protecunprotected, allowing it to be edited, or to protect an unprotected o

This command is only available on the Succession Media Card.

This command changes the file protection of a file. This is used so that a craftspecan either enable or disable write protection on a file on the ITG card DOS drive

The level of protection is:

• +Radd write protection to the file

• -Rremove write protection from the file

-> ll-rwxrwxrwx 1 0 0 6603692 Feb 18 10:25 exec-rwxrwxrwx 1 0 0 8 Jan 1 2001 ataTest.txtdrwxrwxrwx 1 0 0 4096 Feb 12 08:12 LOG/drwxrwxrwx 1 0 0 4096 Jan 1 2001 TRACE/drwxrwxrwx 1 0 0 4096 Feb 17 09:29 TABLE/drwxrwxrwx 1 0 0 4096 Feb 18 00:00 OM/drwxrwxrwx 1 0 0 4096 Jan 1 2001 DSP/drwxrwxrwx 1 0 0 4096 Jan 1 2001 KEYCODE/drwxrwxrwx 1 0 0 4096 Feb 11 10:13 BOOTP/drwxrwxrwx 1 0 0 4096 Feb 17 09:29 CONFIG/drwxrwxrwx 1 0 0 4096 Feb 19 09:29 H323/value = 0 = 0x0-> attrib “/C:/exec”,”+R”value = 0 = 0x0-> ll-r-xr-xr-x 1 0 0 6603692 Feb 18 10:25 exec-rwxrwxrwx 1 0 0 8 Jan 1 2001 ataTest.txtdrwxrwxrwx 1 0 0 4096 Feb 12 08:12 LOG/drwxrwxrwx 1 0 0 4096 Jan 1 2001 TRACE/drwxrwxrwx 1 0 0 4096 Feb 17 09:29 TABLE/drwxrwxrwx 1 0 0 4096 Feb 18 00:00 OM/drwxrwxrwx 1 0 0 4096 Jan 1 2001 DSP/drwxrwxrwx 1 0 0 4096 Jan 1 2001 KEYCODE/drwxrwxrwx 1 0 0 4096 Feb 11 10:13 BOOTP/drwxrwxrwx 1 0 0 4096 Feb 17 09:29 CONFIG/drwxrwxrwx 1 0 0 4096 Feb 19 09:29 H323/value = 0 = 0x0->



ers,

n

can

Itrectss

k,

ated

d or

g

B.2.4 chkdsk “dev”, repairLevel, entryLevelType

Safety level: Destructive Debug. If repairing damage or freeing damaged clustnecessary information may be lost, resulting in unpredictablebehaviour. However, if corruption exists, it is usually safer to fix it thato leave it corrupted. Note: this command may have severeconsequences if run during traffic, as it makes the partition under sunavailable.

Thechkdskutility can be used to identify if there is any corruption on the C: drive.checks the disk and prints a report of the results. An option allows the utility to corany problems found. Whilechkdskis running, other routines and tasks cannot accethe partition.

The parameter“dev” specifies the drive to check and should be set to“/C:” whenchecking the ITG card’s internal Flash disk.

The parameterrepairLevelspecifies the action to be taken. All options check the disreport statistics and report any errors found. Valid values forrepairLevel are:

0 - do not write to disk, only report errors found (default)

1 - repair any damages, preserving or salvaging information in special files creautomatically under the root directory ofdev

2 - do not attempt to salvage any information, return any clusters with damagepartial information to the pool of free space

The parameterentryLevelTypespecifies the condition of the disk. It has the followinvalues (“0” is the normal value used):

0 - disk not fully used or average file is more than 16 clusters

1 - average file is about 4 clusters in size

2 - disk is full, small files about 1 cluster in size on the average

-> chkdsk “/C:”,0,0Copyright (c) 1993-1996 RST Software Industries Ltd. Israel. All rights reservedver: 2.6 FCSDisk Check In Progress ...

total disk space (bytes) : 3,923,968 bytes in each allocation unit : 2,048 total allocation units on disk : 1,916 bad allocation units : 0 available bytes on disk : 2,037,760 available clusters on disk : 995 maximum available contiguous chain (bytes) : 1,935,360 available space fragmentation (%) : 6 clusters allocated : 921Done Checking Disk.value = 0 = 0x0->



n thes the

B.2.5 devs


This command provides a listing of the assorted devices and systems mounted oITG card. This allows the user to determine whether necessary devices such afile system have been correctly mounted.

In the following example, the file system has not been mounted.

BIOS> devsdrv name 0 /null 1 /tyCo/0 1 /tyCo/1 5 host: 6 /pty/telnet.S 7 /pty/telnet.Mvalue = 25 = 0x19

Typically, this command is most useful on the Pentium card.

-> devsdrv name 0 /null 1 /tyCo/0 2 /tyCo/1 3 /aioPipe 4 /C: 6 bootHost: 7 /pty/telnet.S 8 /pty/telnet.M 3 mixSelRMM 3 mixSelNPM 3 /pipe/ipssSig 3 mixSelMTSvalue = 25 = 0x19->

However, it can also be used on an SMC card.

-> devsdrv name 0 /null 1 /tyCo/0 2 /tyCo/1 3 /aioPipe 4 /C: 6 bootHost: 7 /pty/telnet.S 8 /pty/telnet.M 3 mixSelRMM 3 mixSelNPM 3 /pipe/ipssSig 3 mixSelMTSvalue = 25 = 0x19->



the

eful. Noen,

B.2.6 DimECStat =1/0

This is a variable. Setting this to 1 causes the DSP statistics normally printed bytsm_stat_req_ecdbg TCID or reqECDbg TCID(section B.2.64.1, pg 229) commandto be printed at the end of any call using a gateway channel. This provides a usmeans to collect information about the echo canceller’s performance during a callidentifying information about the call (other than the TCID and timestamp) are givso if information about a particular call is needed, usetsmChanShow[level[,channel]] (section B.1.43, pg 167) while the call is active to identify thechannel being used.

This is cleared by setting the variable to 0. The default isoff; the state is not savedand returns tooff if the card is reset or reboots.

An example of the information output when this command is entered follows.

-> DimECStat=1_DimECStat = 0x34f27c: value = 1 = 0x1->SEP 27 08:28:41 tMVX_DIM: Info TSG: 0 Echo Canceller Debug StatsSEP 27 08:28:41 tMVX_DIM: Info CNV state = 1SEP 27 08:28:41 tMVX_DIM: Info Px level = 697226SEP 27 08:28:41 tMVX_DIM: Info Py level = 0SEP 27 08:28:41 tMVX_DIM: Info Pe level = 340SEP 27 08:28:41 tMVX_DIM: Info Post update cnt = 836SEP 27 08:28:41 tMVX_DIM: Info Attempt update cnt = 836SEP 27 08:28:41 tMVX_DIM: Info Divergence cnt = 0SEP 27 08:28:41 tMVX_DIM: Info ERLE bypass cnt = 328SEP 27 08:28:41 tMVX_DIM: Info XTONE count = 6SEP 27 08:28:41 tMVX_DIM: Info Fore switch cnt = 12SEP 27 08:28:41 tMVX_DIM: Info Back switch cnt = 10SEP 27 08:28:41 tMVX_DIM: Info Xidle count = 2825SEP 27 08:28:41 tMVX_DIM: Info Other bypass cnt = 48



ave

terd).is

B.2.7 dimPrintChannelInfo TCID

Safety level: Debug/output load. This may cause messaging delays but should hminimal effect.

This query displays the data configured for the channel specified in the parameTCID (valid values in the range 0 - 23 for the 24 port card, or 0-31 for the 32 port carThe data printed should match the data configured in the OTM application for thcard.

Below is an example of the information printed for a Pentium card.

-> dimPrintChannelInfo 23 rx_coding type: 9 tx_coding type: 9 rx vif size: 1280 tx vif size: 1280 encapsulation: 3 companding: 1 vad enable: FALSE vad threshold: -17 vox nom delay: 40 vox max delay: 80 fax rate: 144 fax nom delay: 100 fax pkt size: 30 fax tx level: -13 fax cd thresh: 2 fax_encap: 7 fax nat: 20 fax_ls_redun: 2 fax_hs_redun: 0 fax_TCF_method:1 idle noise: -6500 in gain: 0 out gain: 0 ec tail delay: 32 rtp.SSRC: AABBCCDD rx rtp.payload: 0 tx rtp.payload: 0value = 23 = 0x17->

Thecoding type indicates the codec used. It has the following values:

8 - G.711 A-law 9 - G.711 mu-law68 - G.729A70 - G.729AB

Thevif size indicates the number of bits to pack per packet. This is related to thepacket time and the codec type. The equations are:• G.711: vif size = packet time(msec) * 64



his

• G.729: vif size = packet time(msec) * 8

As was stated above, this command is useful on the Pentium card. However, tcommand also applies to the SMC card.

-> dimPrintChannelInfo 31 rx_coding type: 9 tx_coding type: 9 rx vif size: 1280 tx vif size: 1280 encapsulation: 3 companding: 1 vad enable: FALSE vad threshold: -17 vox nom delay: 40 vox max delay: 80 fax rate: 144 fax nom delay: 100 fax pkt size: 30 fax tx level: -13 fax cd thresh: 2 fax_encap: 7 fax nat: 20 fax_TCF_method:1 fax_ls_redun: 2 fax_hs_redun: 0 idle noise: -6500 in gain: 0 out gain: 0 ec tail delay: 32 rtp.SSRC rx: AABBCCDD rtp.SSRC tx: AABBCCDD rx rtp.payload: 0 tx rtp.payload: 0value = 23 = 0x17->



thend

B.2.8 dspFatalErrorCountClear dspnum

Safety level: Debug/recovery. This can help return a DSP to service.

This function returns a currently Out of Service DSP back to service.dspnum is 0-1for ITG Trunk 486 product and 0-7 for ITG Trunk Pentium product.

-> dspFatalErrorCountClear 1DSP 1 fatal error count cleareddsp_is: dsp_no 1, mask ffffffbf1996 1 5 21:09:12 (TSM) :DSP# 1 returned to servicevalue = 6 = 0x6

B.2.9 dummy_trap


This command sends an SNMP test message to the server. It helps to prove inconfiguration by sending a message for SNMP, ensuring that the provisioning anetwork are able to transmit SNMP traps.

-> dummy_trapvalue = 0 = 0x0-> 1996 1 5 20:00:03 (SNMP) :dummy: setting up alarm struc1996 1 5 20:00:03 (SNMP) :Calling snmpTrap

B.2.10 exit

Safety level: Safe.

Exit the VxWorks shell and re-enter the ITG shell.

ITG> vxWorksShelllogin:<login user name>password:<login password>Welcome to the VxWorks ShellWARNING: Data entry errors in this shell could cause loss of service.Enter “itgShell” to return to the ITG shell.value = 3542528 = 0x360e00 = shellHistSize + 0x4-> exitITG>



ut is

B.2.11 flashConfigShow


This command allows the user to display information about the ITG card’s Flashmemory configuration. It can be executed from either the BIOS or the VxWorksshells.

The output varies based on card type. For the Pentium card, the following outpreceived.

-> flashConfigShowEntered flashDrvInit() with parameters: Base Address : 08000000 Max length : 00200000flash_supported[10] match Flash Vendor ID : 0x89 Flash device ID : 0x18 Flash device type : i28f128j3a Flash base addr : 0x8000000 Flash sector count : 32 Flash device width : 2 Flash chip count : 1 Flash device size : 16MBvalue = 0 = 0x0->

For the SMC card, the following output is received.

-> flashConfigShow Flash Vendor ID : 0x89 Flash device ID : 0x15 Flash device type : i28f640j5 Flash base addr : 0xf9800000 Flash sector count : 64 Flash device width : 2 Flash chip count : 1 Flash device size : 8MBvalue = 0 = 0x0->



pt.oren the

. Aault

ast

e)

B.2.12 h and command history handling


This command displays the last 20 commands entered at the VxWorks shell promThis shell history mechanism is similar to the UNIX Korn shell history function. Pricommands can be recalled, edited and executed using it, speeding debugging whsame or similar commands must be entered repeatedly.

An ESCkey entered at the VxWorks shell switches the shell to edit history modeRETURN key always gives the line to the shell and exits edit mode. Note the defvalue forn is 1. The following are a few of the more useful editing commands.

Movement and searching• nG - go to commandn• nk - get thenth previous shell command in history. Just entering k returns the l

command entered.• /s - search for strings backward in history• ?s - search for strings forward in history• nh - move leftn characters.• nl (or nSPACE) - move rightn characters.• nw - moven words forward• nb - moven words back• fc - find characterc, searching forward• Fc - find characterc, searching backward• $ - go to end of line• 0 - go to start of line

Insertion (input is expected until anESC is pressed)• a - append• A - append at end of line• cl (or c SPACE) - change character (deletes character and enters input mod• cw - change word (deletes word and enters input mode)• cc (or S) - change entire line• c$ (or C) - change everything from cursor to end of line• i - insert• I - insert at beginning of line• R - type over characters

Editing commands• nrc - replace the following n characters with c.• nx - deleten characters starting at the cursor• nX - deleten characters to the left of the cursor• dl - delete character• dw - delete word• dd - delete entire line• d$ (or D) - delete everything from cursor to end of line



• p - put last deletion after the cursor• P - put last deletion before the cursor• u - undo last command• Special commands:

CTRL-U - delete line and exit edit modeCTRL+L - redraw lineCTRL+D - complete symbol nameRETURN - give line to shell and exit edit mode

The following is an example of the command.

-> h 2 arpFlush 3 ls 4 ll 5 attrib “/c:/exec”,”+R” 6 cd “TRACE” 7 ll 8 cd “/c:” 9 cd “/C” 10 cd “..” 11 cd “TRACE” 12 cd “/C:” 13 cd “TRACE” 14 pwd 15 cd “/C:” 16 pwd 17 chkdsk “/C:”,0,0 18 vxWorksShell 19 h 20 flashConfigShow 21 hvalue = 0 = 0x0->

B.2.13 icmpstatShow

Safety level: Safe.

Displays statistics for the ICMP protocol.

-> icmpstatShowICMP: 10 calls to icmp_error 0 error not generated because old message was icmp Output histogram: echo reply: 434 destination unreachable: 10 0 message with bad code fields 0 message < minimum length 0 bad checksum 0 message with bad length Input histogram: echo reply: 1 destination unreachable: 7104



nd

nnelnot

.

echo: 434 434 message responses generatedvalue = 33 = 0x21 = ’!’->

B.2.14 igccAddTrace, igccNoTrace

B.2.14.1 igccAddTracechannel


This command, used with“B.2.54 setTraceOption channel,outputLocation” on page220, enables limited tracing in the IGCC module. Tracing is limited to “receive abuild”, indicating the function, the message type, and the ISL channel ID.

The command uses its own capabilities to define the channel ID, as the ISL chanumber is in the range 1-382. The TSM and NPM use the TCID is 0-31, and maybe co-resident with the IGCC.

Setting the channel to any other channel disables tracing the current channel ID

-> igccAddTrace 32-> ...2001 4 25 08:46:16 (IGCC) :CH#:0 rcvTsmIgcMsg: msgType=42, chid=322001 4 25 08:46:16 (IGCC) :CH#:0 buildUipeMsg: msgType=9, chid=32...

B.2.14.2 igccNoTrace


Use this command to turn off tracing the IGCC channel.

B.2.15 inetstatShow


This command displays information on all of the active IP sockets.

-> inetstatShowActive Internet connections (including servers)PCB Proto Recv-Q Send-Q Local Address Foreign Address (state)-------- ----- ------ ------ ------------------ ------------------ -------3157898 TCP 0 0 47.11.215.209.1077 47.11.215.212.1074 ESTABLISHED3157580 TCP 0 0 47.11.215.209.1720 47.11.215.212.1072 ESTABLISHED31573f4 TCP 0 0 47.11.215.209.1075 47.11.215.212.1069 ESTABLISHED3157790 TCP 0 0 0.0.0.0.1074 0.0.0.0.0 LISTEN3157604 TCP 0 0 47.11.215.209.1073 47.11.215.212.1720 ESTABLISHED3157370 TCP 0 0 47.11.217.54.23 47.11.181.36.34223 ESTABLISHED31570dc TCP 0 0 0.0.0.0.6001 0.0.0.0.0 LISTEN3156fd4 TCP 0 0 0.0.0.0.1720 0.0.0.0.0 LISTEN3156a28 TCP 0 0 0.0.0.0.111 0.0.0.0.0 LISTEN



3156920 TCP 0 0 0.0.0.0.23 0.0.0.0.0 LISTEN3156818 TCP 0 0 0.0.0.0.21 0.0.0.0.0 LISTEN31574fc UDP 0 0 0.0.0.0.2300 0.0.0.0.03157688 UDP 0 0 0.0.0.0.2362 0.0.0.0.031572ec UDP 0 0 0.0.0.0.0 0.0.0.0.03157268 UDP 0 0 0.0.0.0.0 0.0.0.0.031571e4 UDP 0 0 0.0.0.0.0 0.0.0.0.03157160 UDP 0 0 0.0.0.0.15000 0.0.0.0.03157058 UDP 0 0 0.0.0.0.5000 0.0.0.0.03156f50 UDP 0 0 0.0.0.0.1719 0.0.0.0.03156ecc UDP 0 0 0.0.0.0.2002 0.0.0.0.03156e48 UDP 0 0 0.0.0.0.2001 0.0.0.0.03156cbc UDP 0 0 0.0.0.0.7043 0.0.0.0.03156bb4 UDP 0 0 0.0.0.0.67 0.0.0.0.03156b30 UDP 0 0 0.0.0.0.123 0.0.0.0.03156aac UDP 0 0 47.11.217.54.161 0.0.0.0.031569a4 UDP 0 0 0.0.0.0.111 0.0.0.0.0value = 1 = 0x1->



B.2.16 iosFdShow


Displays all of the file descriptors in use.

-> iosFdShow fd name drv 3 /tyCo/0 1 4 /tyCo/1 2 5 /aioPipe 3 6 (socket) 5 7 (socket) 5 8 (socket) 5 9 (socket) 5 10 (socket) 5 11 (socket) 5 12 /C:/LOG/CURRLOG.1 4 13 (socket) 5 14 mixSelRMM 3 15 (socket) 5 16 (socket) 5 17 (socket) 5 18 (socket) 5 19 (socket) 5 20 mixSelNPM 3 21 /pipe/ipssSig 3 22 mixSelMTS 3 23 (socket) 5 24 (socket) 5 25 (socket) 5 26 (socket) 5 27 (socket) 5 28 (socket) 5 29 /C:/LOG/AUDIT.HIS 4 30 (socket) 5 31 /pty/telnet.M 8 32 /pty/telnet.S 7 in out err 33 (socket) 5 34 (socket) 5 35 (socket) 5 36 (socket) 5 38 (socket) 5 39 (socket) 5 40 (socket) 5value = 32 = 0x20 = ’ ’->



r and

ts ofr of

B.2.17 ipstatShow


Displays the IP protocol statistics.

-> ipstatShow total 1365243 badsum 0 tooshort 0 toosmall 0 badhlen 0 badlen 0 infragments 0 fragdropped 0 fragtimeout 0 forward 0 cantforward 911 redirectsent 0 unknownprotocol 918 nobuffers 0 reassembled 0 outfragments 0 noroute 0

value = 1 = 0x1

B.2.18 itgExcpCountClear - Pentium card only


This command clears the count for both the number of exceptions in the last houthe total number of exceptions since the last boot-up.

--> itgExcpCountClearITG exception counters clearedvalue = 31 = 0x1f

B.2.19 itgExcpCountShow - Pentium card only


This command prints the details regarding exceptions on the card. This consisthe count for both the number of exceptions in the last hour and the total numbeexceptions since the last boot-up.

-> itgExcpCountShow

Total number of task level exceptions since bootup : 0 Number of task level exceptions in the last hour : 0

value = 1 = 0x1



the

B.2.20 itgShell


Exit the VxWorks shell and re-enter the ITG shell.

ITG> vxWorksShelllogin:<login user name>password:<login password>Welcome to the VxWorks ShellWARNING: Data entry errors in this shell could cause loss of service.Enter “itgShell” to return to the ITG shell.value = 3542528 = 0x360e00 = shellHistSize + 0x4-> itgShellITG>

B.2.21 lkup “string”


This VxWorks command (accessible from the VxWorks shell only) searches thesymbol table and lists any symbol found containingstring. This command is usefulwhen looking for a command, global variable, or function but you can’t rememberexact spelling.

The search string is case-sensitive, so try the various upper and lower casecombinations if the first search fails.

The following is an example of a search for the commandnumNodesInFallbackShowusing “numn” as the search string. As nothing was found, the user re-enters thecommand with the case changed from “numn” to “numN”.

-> lkup “numn”value = 0 = 0x0-> lkup “numN”numNodesInFallback 0x007dd630 bssnumNodesInFallbackShow 0x000f746c textrtcpGetEnumNext 0x001e05d8 textgetEnumNameId 0x0020649c textvalue = 0 = 0x0->



the

sacast.

hold

sage

B.2.22 lnIsaBroadcastShow - not applicable, SMC

See also mac21440BroadcastShow for the SMC, and lnPciBroadcastShow for TLAN.


This command displays the number of broadcast IP packets received on the lnI(ELAN) interface every second for the past 60 seconds. The total number of broadmessages received on the interface since the card was booted is also displayed

This can help identify the presence of broadcast storms on the ELAN segment.

-> lnIsaBroadcastShowBroadcasts per second, last 60 seconds: lnIsa0 -0: 0 -1: 0 -2: 0 -3: 1 -4: 0 -5: 0 -6: 0 -7: 3 -8: 0 -9: 0... one line printed for each of the last 60 seconds -54: 0 -55: 0 -56: 20 -57: 0 -58: 0 -59: 0Total number of broadcasts: 6209value = 33 = 0x21 = '!'

B.2.23 lnIsaBroadcastThreshold =threshold - not applicable, SMC

See also mac21440BroadcastThreshold for the SMC, and lnPciBroadcastThresfor the TLAN.


This is a variable. Setting it controls the threshold (in packets/sec) at which a mesis printed when thelnIsaShowLostBroadcast is set. The default threshold is 40.

-> lnIsaBroadcastThreshold = 20_lnIsaBroadcastThreshold = 0x34aeb0: value = 20 = 0x14



shold

w

itherandands

er ased

B.2.24 lnIsaShowLostBroadcast =1/0 - not applicable, SMC

See also lnPciShowLostBroadcast for the TLAN.


This is a variable. Setting it to 1 prints a message whenever the broadcast thre(set via thelnIsaBroadcastThreshold variable) is exceeded on the lnIsa (ELAN)interface. This is useful for debugging broadcast storms. The default isoff (0); thestate is not saved and returns tooff if the card is reset or reboots. The example belowas generated when the threshold was set to 0 (not a normal setup!)

-> lnIsaShowLostBroadcast = 1_lnIsaShowLostBroadcast = 0x34aec8: value = 1 = 0x1

FEB 12 12:23:27 tLogTask: Info Time 332140 lnIsa: 1 broadcasts in last second

B.2.25 lnPciBcastFilterOff - not applicable, SMC


This command disables physical level broadcast filtering as configured by thelnPciBcastFilterOn - not applicable, SMC (section B.2.26, pg 188) command.

B.2.26 lnPciBcastFilterOn - not applicable, SMC


This command enables enhanced Broadcast filtering on the T-LAN interface onPentium cards. This is enabled by default.

When this is not enable, if we receive more than 40 Broadcasts of any sort on ethe T-LAN or the E-LAN we do not process them any more (but we do count themthis can be verified with the lnIsaBroadcastShow or lnPciBroadcastShow commfrom the vxWorksShell).

With this enabled, we filter out at a H/W level receipt of any more broadcasts ovmaximum limit of 401 on the T-LAN. The lnPciBroadcastShow command can be uto view this in operation.

-> lnPciBroadcastShow

Broadcasts per second, last 60 seconds: lnPci0

0: 401 0 0 401 0 0 401 6: 0401etc.



cast

cicast.

sage

Note also, that a message is written to the CURRLOG.1 file every time the Broadfilter threshold is reached:

1996 1 7 09:39:53 (COM) :PCI Broadcast Filter Enabled

B.2.27 lnPciBroadcastShow - not applicable, SMC


This command displays the number of broadcast IP packets received on the lnP(TLAN) interface every second for the past 60 seconds. The total number of broadmessages received on the interface since the card was booted is also displayed

-> lnPciBroadcastShowBroadcasts per second, last 60 seconds: lnPci0 -0: 0 -1: 10 -2: 0 -3: 0 -4: 0 -5: 0 -6: 0 -7: 0 -8: 8 -9: 0... one line printed for each of the last 60 seconds -54: 0 -55: 0 -56: 0 -57: 0 -58: 0 -59: 0Total number of broadcasts: 4518value = 33 = 0x21 = '!'

B.2.28 lnPciBroadcastThreshold =threshold - not applicable, SMC


This is a variable. Setting it controls the threshold (in packets/sec) at which a mesis printed when thelnPciShowLostBroadcast is set. The default threshold is 40.

-> lnPciBroadcastThreshold = 200_lnPciBroadcastThreshold = 0x34b008: value = 200 = 0xc8



shold

w

file

, the

B.2.29 lnPciShowLostBroadcast =1/0 - not applicable, SMC


This is a variable. Setting it to 1 prints a message whenever the broadcast thre(set via thelnPciBroadcastThreshold variable) is exceeded on the lnPci (TLAN)interface. This is useful for debugging broadcast storms. The default isoff (0); thestate is not saved and returns tooff if the card is reset or reboots. The example belowas generated when the threshold was set to 0 (not a normal setup!)

-> lnPciShowLostBroadcast = 1_lnPciShowLostBroadcast = 0x34b020: value = 1 = 0x1

FEB 12 12:23:27 tLogTask: Info Time 332140 lnPci: 1 broadcasts in last second

B.2.30 ls


This command lists the contents of the current directory, with only the directory ornames.

The example shows a list of the root directory on a Media Card. For comparison“ll” is also shown.

-> lsexecULOGTRACETABLEOMDSPKEYCODEBOOTPCONFIGH323ETCvalue = 0 = 0x0->-> ll-r-xr-xr-x 1 0 0 7249248 Mar 14 2001 execdrwxrwxrwx 1 0 0 4096 Feb 5 2001 U/drwxrwxrwx 1 0 0 4096 Mar 7 2001 LOG/drwxrwxrwx 1 0 0 4096 Feb 5 2001 TRACE/drwxrwxrwx 1 0 0 4096 Mar 12 12:06 TABLE/drwxrwxrwx 1 0 0 4096 Mar 12 00:01 OM/drwxrwxrwx 1 0 0 4096 Feb 5 2001 DSP/drwxrwxrwx 1 0 0 4096 Feb 5 2001 KEYCODE/drwxrwxrwx 1 0 0 4096 Mar 9 16:12 BOOTP/drwxrwxrwx 1 0 0 4096 Mar 12 12:06 CONFIG/drwxrwxrwx 1 0 0 4096 Mar 12 12:06 H323/drwxrwxrwx 1 0 0 4096 Feb 10 2001 ETC/value = 0 = 0x0



sfaces

tware the

linghet

B.2.31 mac21440BroadcastShow - only applicable for SMC

See also lnIsaBroadcastShow for the other cards.


For the SMC, broadcast filtering is done by the microengine co-processors. Thifunction prints the number of broadcasts that the card has received on both interevery second for the past 60 seconds.

The number of broadcasts is the number that was returned to the IPT 3.0 core sofby the microengines. If this value exceeds the threshold per second, then that isnumber of packets that will be reported by this function.

-> mac21440BroadcastShowBroadcasts per second, last 60 seconds: mac21440 -0: 0 -1: 0 -2: 0 -3: 1 -4: 0 -5: 0 -6: 0 -7: 3 -8: 0 -9: 0... one line printed for each of the last 60 seconds -54: 0 -55: 0 -56: 20 -57: 0 -58: 0 -59: 0Total number of broadcasts: 6209value = 33 = 0x21 = '!'

B.2.32 mac21440BroadcastThreshold =threshold -only applicable for SMC

See also lnIsaBroadcastThreshold for the other cards.


This is a variable. Setting it controls the threshold (in packets/sec) at which throttof broadcast messages occurs. When the number of broadcasts received by tmicroEngines exceeds this value, the microEngines will start dropping broadcaspackets. The default threshold is 40.

-> mac21440BroadcastThreshold = 20_mac21440BroadcastThreshold = 0x34aeb0: value = 20 = 0x14



by

B.2.33 mbufShow


This command displays statistics and the distribution of the low-level buffers usedthe IP stack.

-> mbufShowtype number--------- ------FREE : 6395DATA : 0HEADER : 5SOCKET : 0PCB : 0RTABLE : 0HTABLE : 0ATABLE : 0SONAME : 0ZOMBIE : 0SOOPTS : 0FTABLE : 0RIGHTS : 0IFADDR : 0CONTROL : 0OOBDATA : 0IPMOPTS : 0IPMADDR : 0IFMADDR : 0MRTABLE : 0TOTAL : 6400number of mbufs: 6400number of times failed to find space: 0number of times waited for space: 0number of times drained protocols for space: 0__________________CLUSTER POOL TABLE_______________________________________________________________________________size clusters free usage-------------------------------------------------------------------------------64 1024 1019 2276128 1024 1024 187290256 512 512 775512 512 512 291024 256 256 342048 256 256 0-------------------------------------------------------------------------------value = 80 = 0x50 = ’P’->



t on”

gtherted

thatg theery

ighing.

erple,deple,

ner

e

B.2.34 mixLevelOnmodule


This command has a deceptive name. It translates as “mix level as currently sea module. It prints the current print level set formodule.

In the example, executing the command initially resulted in a result of “0”; the lolevel was “error only”. After enabling the trace to screen (mixSetLogOpt 0,1,1),command resulted in a return value of “all”, or 1. After a further change, it reveto “error only”, even though the option was still “to screen”.

-> mixLevelOn 0value = 0 = 0x0-> mixSetLogOpt 0,1,1value = 0 = 0x0-> mixLevelOn 0value = 1 = 0x1-> mixSetLogOpt 0,1,0value = 0 = 0x0-> mixLevelOn 0value = 0 = 0x0->

B.2.35 mixMemFindAll


This command prints information about each buffer from an IPT 3.0 buffer pool is currently in use by the application. The address of the buffer and the task usinbuffer is printed. This information can be useful if a buffer pool runs out (or runs vlow) of buffers to see what task is holding on to them.

Note that running this command when the buffers are very low and traffic is fairly his somewhat risky, as it can end up in contention for resources with call process

Note: in the table, “marker” actually stands for the task indication within the buffdata space reserved to indicate the task that mixMalloc’ed the buffer. For exam“tNpm” would mean that the NPM task seized the buffer. And “Instance” is a coused by designers to locate the place where the mixMalloc occurred. As an examif the NPM mixMalloc’ed a block and the instance shown was “0x8001”, the desigcan look for mixMalloc in the NPM module code and the function where themixmalloc occurred. Using the example for line 002 of the pool “buf size (64)”, wfind:

if ( (timerMsg = mixMalloc( sizeof(MIX_MSG_Q_HDR_MSG), M_BUF_NPM | 1 )) == NULL )



its;
This is the line that seized the buffer shown here. “M_BUF_NPM” set the high bthe low 3 nybbles are the location within that task.
-> mixMemFindAll

+------------------------------------------+| POOL BUF SIZE (64) |+------------------------------------------+| Buffer State Marker Instance |+------------------------------------------+001. 0x2e94244 good tRmm 0xb020002. 0x2e945b4 good tNpm 0x8001003. 0x2e946a4 good (null) 0xc022004. 0x2e94f64 good tRCM 0xa000005. 0x2e96724 good tRmm 0xb01d006. 0x2e985c4 good tMONServer 0x6005007. 0x2e9cad4 good tRmm 0xb000008. 0x2e9cdf4 good tOMM 0x9000009. 0x2ea0bd4 good tMONClient 0x6000010. 0x2ea2074 good tOMM 0x9001011. 0x2ea2164 good tRmm 0xb000

+------------------------------------------+| POOL BUF SIZE (256) |+------------------------------------------+| Buffer State Marker Instance |+------------------------------------------+001. 0x2e5cc48 good (null) 0xe001002. 0x2e5d0a8 good tUIPC 0xd00e003. 0x2e71e40 good tUIPC 0xd00e004. 0x2e71f58 good tIGCC 0x300d005. 0x2e73420 good tIGCC 0x3008006. 0x2e73538 good tUIPC 0xd00e007. 0x2e73ab0 good tNpm 0x1009

+------------------------------------------+| POOL BUF SIZE (512) |+------------------------------------------+| Buffer State Marker Instance |+------------------------------------------+001. 0x2cbb3d8 good (null) 0xe000002. 0x2cbc4b8 good tUIPC 0xd007

+------------------------------------------+| POOL BUF SIZE (1024) |+------------------------------------------+| Buffer State Marker Instance |+------------------------------------------+ ******All buffers in pool******value = 34 = 0x22 = ’“’->



t on”

gpt

dere, itilelle

letoon tourth,

of

the

B.2.36 mixOptionOnmodule


This command has a deceptive name. It translates as “mix option as currently sea module. It prints the current option set formodule.

In the example, executing the command initially resulted in a result of “0”; the looption for the module was “off”. After enabling the trace to screen (mixSetLogO0,1,1), the command resulted in a return value of “to screen”, or 1.

-> mixOptionOn 0value = 0 = 0x0-> mixSetLogOpt 0,1,1value = 0 = 0x0-> mixOptionOn 0value = 1 = 0x1->

B.2.37 mixSetLogOptmodule, option, level

Safety level: Debug/possible resource shortage. If the user enables tracing unload, the output can exhaust necessary resources. At the extremcan even lead to cards resetting spontaneously, as tasks block whwaiting for resources. Low level traffic in the order of single digit caper minute rates will to be an issue unless all possible modules arenabled.

This command controls the printing of detailed information from a task. To enabinformation for multiple tasks, the command is entered multiple times. Having much at once can result in being unable to locate key information, so it is commohave up to three on at once, but to turn off some and turn on others to get the fofifth,...

The parametermodulespecifies the module for this entry of the command. Detailswhat each module does is included inIP Trunk 3.0 module descriptions (section 2,pg 19). The next section details which modules are involved in what functions ofITG 2.0 Trunk application.

Table 5: Modules and values used for mixSetLogOpt command

ValueModule

Module functionAcronym Name

0 TSM Telephony Signalling Central call control module for the application

1 NPM Network Protocol H.323 signalling module

2 RMM Resource Manager Allocation and reservation of channels



The parameteroption sets where the data is printed:

0 = off1= log to TTY2= log to file3= log to both TTY and file

3 NMM Network Manager Administration - especially dial plan tables

4 MAM Maintenance Module Accept and propagate provisioning from OTM

5 MTS Network MonitorTimestamp Server

Quality of service monitoring6 MSM Network Monitor Server

7 MCM Network Monitor Client

8 OMM Operation Measurement Statistics

9 A07 A07 Manager SSD messages to and from the Meridian 1

10 DIM DSP Interface Module Interface to software resident on the DSPs

11 UIPC UIPC L3 Module State machine and parser for layer 3 ISDNmessages

12 LAPD Omnitel LAPD Driver Layer 2 D channel PC card interface

13 IGCC Internet Gateway CallControl

Interface between TSM and UIPC

14 ATPM Address TranslationProtocol Module

Resolving addresses to IP addresses

15 SNMP SNMP agent module Network management interface

16 COM Common Utilities

17 SMM System Monitor

18 IPSS IP Socket Server Drives all intercard communications

19 RCM RADIUS Client Module

20 MonTask Task monitor Ensures tasks are still running

21 ItgPatch Patcher function Tracking installing (etc.) of patches

Table 5: Modules and values used for mixSetLogOpt command

ValueModule

Module functionAcronym Name



tion

and

ory,

Entering the command without the option is equivalent to entering it with the op“0”, or “off”.

The parameterlevel sets what kind of information is printed:

0 = error only1 = info and error

The level cannot be entered without the option being selected; entering an optionnot entering a level defaults to “error only”.

B.2.38 mkdir “dirName”

Safety level: Safe/memory constrained. If the system has used up all of the memthis can have unpredictable results.

This creates a new subdirectory under (within) the current directory.

-> ll size date time name-------- ------ ------ -------- 512 JUN-06-2000 08:28:44 LOG <DIR> 512 JUN-06-2000 08:28:46 OM <DIR> 512 JUN-06-2000 08:28:50 CONFIG <DIR> 512 JUN-06-2000 08:33:34 FW <DIR> 512 JAN-01-1996 12:00:22 DATA <DIR> 512 JAN-01-1996 12:00:22 ETC <DIR> 512 JAN-01-1996 12:00:22 LOCALE <DIR>value = 0 = 0x0-> mkdir “temp”value = 0 = 0x0-> ll size date time name-------- ------ ------ -------- 512 JUN-06-2000 08:28:44 LOG <DIR> 512 JUN-06-2000 08:28:46 OM <DIR> 512 JUN-06-2000 08:28:50 CONFIG <DIR> 512 JUN-06-2000 08:33:34 FW <DIR> 512 JAN-01-1996 12:00:22 DATA <DIR> 512 JAN-01-1996 12:00:22 ETC <DIR> 512 JAN-01-1996 12:00:22 LOCALE <DIR> 512 FEB-22-2001 15:10:00 TEMP <DIR>value = 0 = 0x0



ress.ing

B.2.39 monIPDebugSet “IP.ad.dr.ess”, on_off


This command enables detail network monitor debugging for the selected IP addThe address is entered in dotted notation. The parameter on_off has the followvalues:

0 - turn off detailed information1 - turn on detailed information

An example follows:

-> monIPDebugSet “10.0.0.2”, 1value = 1 = 0x1-> 1996 2 4 21:27:32 (MSM) :No packets received from IP: 10.0.0.2, Freq: 235661996 2 4 21:27:32 (MSM) :No packets returned by IP: 10.0.0.21996 2 4 21:27:52 (MSM) :No packets received from IP: 10.0.0.2, Freq: 235671996 2 4 21:27:52 (MSM) :No packets returned by IP: 10.0.0.21996 2 4 21:28:12 (MSM) :No packets received from IP: 10.0.0.2, Freq: 235681996 2 4 21:28:12 (MSM) :No packets returned by IP: 10.0.0.2

-> monIPDebugSet “10.0.0.2”,0value = 1 = 0x1->



ing

tings. as a

B.2.40 monUtility


This menu driven utility provides a way to print the IP table for the QoS monitorfunction and to print the QoS statistics for a remote node.

An example of the data provided by monUtility follows.NOTE: Options 1,2,3,4,8,9are intended as designer tools only. Please do not use these to change any setThe original settings can be restored by resetting the card. Option 0 is availableseparate command: emodelSim.

-> monUtility

******Monitor Utility******

Run Emodel Simulator ............0Set Monitor Probing Constants ...1Print Monitor Constants .........2Set Monitor Debug Options .......3Print Monitor Debug Setting .....4Print IP Table ..................5Print IP Entry ..................6Print IP Entry QoS Data .........7Set Configured QoS Parms ........8Set Network QoS Parms ...........9End Utility .................EnterPlease Enter Your Choice -> 5

Number of blocks = 1 Number of entry = 2

Block number : 0Entry : 0Node IP : 47.11.215.211Reference count : 11Qos Enabled : 1Send QoS : 3.000000Receive QoS : 3.000000Node Capability : 7





Run Emodel Simulator ............0Set Monitor Probing Constants ...1Print Monitor Constants .........2Set Monitor Debug Options .......3Print Monitor Debug Setting .....4Print IP Table ..................5Print IP Entry ..................6Print IP Entry QoS Data .........7Set Configured QoS Parms ........8Set Network QoS Parms ...........9End Utility .................EnterPlease Enter Your Choice -> 6,0

******IP ENTRY DATA******

IP ADDRESS -> 47.11.215.211

IP ADDRESS : 47.11.215.211CONFIGURED QOS QOS ENABLED : 1 TRANSMIT QOS : 3.00 RECEIVE QOS : 3.00NETWORK QOS

CODEC TYPE TRANSMIT QOS RECEIVE QOS FALLBACK STATE

G711Alaw 4.43 4.43 0 G711Ulaw 4.43 4.43 0 G723_5 3.99 3.99 0 G723_6 3.99 3.99 0 G729 4.07 4.07 0 G729A 4.07 4.07 0 G729B 4.07 4.07 0 G729AB 4.07 4.07 0


Run Emodel Simulator ............0Set Monitor Probing Constants ...1Print Monitor Constants .........2Set Monitor Debug Options .......3Print Monitor Debug Setting .....4Print IP Table ..................5Print IP Entry ..................6Print IP Entry QoS Data .........7Set Configured QoS Parms ........8Set Network QoS Parms ...........9End Utility .................EnterPlease Enter Your Choice -> 7 Please Enter Your Choice -> 7,0

******PRINT IP QOS DATA******

IP ADDRESS (Enter to End) -> 47.11.215.211

******SAMPLE BURST STATISTICS******

RECEIVED PACKETS



Base Seq = 0 Max Seq = 23 Bad Seq = 24 Currently Received = 24 Max Expected = 24 Last Total Received = 24 Consecutive 100% Packet Loss = 0

TRANSMIT PACKETS Total Send RTT = -30.00 Samples Returned = 24

Sample# Send Side Send Side Receive Side Receive Side Delay Pkt Loss Delay Pkt Loss

0 90.40 0.00 93.00 0.001 89.46 0.00 93.00 0.002 92.79 0.00 93.00 0.003 91.96 0.00 93.00 0.004 91.75 0.00 93.00 0.00

Transmit DataCurrent Sample Number = 1Average End-To-End Delay = 91.27 msAverage Packet Loss = 0.00 %

Receive DataCurrent Sample Number = 1Average End-To-End Delay = 93.00 msAverage Packet Loss = 0.00 %

IP ADDRESS : 47.11.215.211CONFIGURED QOS QOS ENABLED : 1 TRANSMIT QOS : 3.00 RECEIVE QOS : 3.00NETWORK QOS

CODEC TYPE TRANSMIT QOS RECEIVE QOS FALLBACK STATE

G711Alaw 4.43 4.43 0 G711Ulaw 4.43 4.43 0 G723_5 3.99 3.99 0 G723_6 3.99 3.99 0 G729 4.07 4.07 0 G729A 4.07 4.07 0 G729B 4.07 4.07 0 G729AB 4.07 4.07 0


Run Emodel Simulator ............0Set Monitor Probing Constants ...1Print Monitor Constants .........2Set Monitor Debug Options .......3Print Monitor Debug Setting .....4Print IP Table ..................5Print IP Entry ..................6Print IP Entry QoS Data .........7Set Configured QoS Parms ........8



ed

n;

s the

ask;

s the

Set Network QoS Parms ...........9End Utility .................EnterPlease Enter Your Choice ->value = 10 = 0xa->

B.2.41 mRouteAdd “destIPaddr”, “ gwIPaddr”, 0xdestNetMask, To, 0


Similar torouteAdd, but allows multiple routes to the same destination, differentiatby the ToS field and/or the gateway field. The parameterdestIPaddris the destinationIP address in dotted notation;gwIPaddr is the gateway IP address in dotted notatio0xdestNetMask is the destination’s net mask in hexadecimal;ToS is the Type ofService for this route. This change is not permanent; rebooting the card rebuildrouting table from the data in the CONFIG.INI file.

-> mRouteAdd “192.168.1.128”,”192.168.1.140”,0xffffff80,0,0value = 0 = 0x0

B.2.42 mRouteDelete “destIPaddr”, 0xdestNetMask, ToS


Similar torouteDelete, but specifies the route using the destination address, netmand ToS. The parameterdestIPaddr is the destination IP address in dotted notation0xdestNetMask is the destination’s net mask in hexadecimal;ToS is the Type ofService for this route. This change is not permanent; rebooting the card rebuildrouting table from the data in the CONFIG.INI file.

-> mRouteDelete “192.168.1.128”,0xffffff80,0value = 0 = 0x0

B.2.43 mRouteShow


Similar torouteShow, but also displays the ToS bit and mask settings.

-> mRouteShowDestination Mask TOS Gateway Flags RefCnt Use Interface Proto

0.0.0.0 0 0 192.168.1.200 3 0 0 lnPci1 0127.0.0.1 0 0 127.0.0.1 5 0 0 lo0 0192.168.1.0 ffffff80 0 192.168.1.14 101 0 0 lnIsa0 0192.168.1.128 ffffff80 0 192.168.1.140 101 0 0 lnPci1 0192.168.1.128 ffffff80 18 192.168.1.140 101 0 0 lnPci1 1value = 0 = 0x0



l toe dial

uingcific

patch

B.2.44 netHelp


Displays a help screen synopsis of often used network routines.

-> netHelp

hostAdd “hostname”,”inetaddr” - add a host to remote host table; “inetaddr” must be in standard Internet address format e.g. “90.0.0.4”hostShow - print current remote host tablenetDevCreate “devname”,”hostname”,protocol - create an I/O device to access files on the specified host (protocol 0=rsh, 1=ftp)routeAdd “destaddr”,”gateaddr” - add route to route tablerouteDelete “destaddr”,”gateaddr” - delete route from route table

routeShow - print current route tableiam “usr”[,”passwd”] - specify the user name by which you will be known to remote hosts (and optional password)whoami - print the current remote IDrlogin “host” - log in to a remote host; “host” can be inet address or host name in remote host table

Type <CR> to continue, Q<CR> to stop: Q

value = 1 = 0x1->

B.2.45 nmmAtpmTranTblDnld

Safety level: Debug. Low risk.

This command reloads the dial plan information on a card. It can be very usefurecover a card that is no longer able to place calls, as often the problem is that thplan table has had an entry - sometimes the gatekeeper data! - corrupted.

-> nmmAtpmTranTblDnldvalue = 0 = 0x0-> 2001 3 17 23:00:27 (NMM) :NMM received file data OK message from ATPM

B.2.46 Patch commands

Commands are listed here alphabetically, not in order of execution. Note that issa command without the patch name or number may result in prompting for the spedetails. When these details are already known, this can result in getting more options.



d theen

g

meaned

gingbuildf the

hing

ewasily

B.2.46.1 pins “patchNumber”

Safety level: Debug. Low risk, provided the patch is correct for the load.

This command puts the patch indicated by the patchNumber into service, providepatch is compatible with the current software version. That is, if a patch has beloaded successfully, it can be enabled.

-> pins “0”function at 0xb3cac will be patched to jump to 0x71a8f0 (_npmNSDataProcess)Proceed with patch activation (y/n)? [y]Patch 0 has been activated successfully.value = 0 = 0x0-> 2003 3 19 14:29:38 (ItgPatch) :PATCH 0 ACTIVATED. Name=”Non_NA_Ringback_Q00632470”,Ref#=”12345”, PRS#=”Q00632470”, File=”/C:/U/PATCH/ringback.tsa”

->

Attempting to put an undefined or unloaded patch into service yields the followinoutput:

-> pins “3”Patch with handle 3 doesn’t exist. Cannot activate.value = -1 = 0xffffffff = _func_taskRegsShowRtn + 0xff7b8bff->

Unfortunately, just because a patch is created for the appropriate load does notit will go into service on a specific switch. For example, the following output occurrwhen a patch providing a single line code change attempted to enable:

-> pins “0”PCH1221: Unexpected code at start of function _npmNSDataProcess at 0xb3cac. The patch might not match the release that is loaded.PCH1115: Error activating patch 0.Activation of patch 0 aborted.value = -1 = 0xffffffff = _func_taskRegsShowRtn + 0xff7ba547-> 2003 3 19 11:00:19 (ItgPatch) :Unexpected code at start of C function_npmNSDataProcess at 0xb3cac The patch might not match the release that is loaded2003 3 19 11:00:19 (ItgPatch) :Error activating patch 0. buildMemLists call failed

->

Usually, this is a sign that either a patch is already loaded on this card and chanthis function, or that the software on the card is a field service up-issue - a customprovided to an end user. In that case, the patch must be rebuilt in the context ofield service up-issue.

Note that in general field service up-issues are not needed in releases with patccapabilities, because of the patching function. Field service up-issues can onlyinclude the exact set of fixes identified, and if another fix is needed a complete nload is required. However, a small patch can be loaded and put in service very eon sites that need it and left out of all others.



fileludes

B.2.46.2 plis, or plis “patchNumber”


This command prints the header information about a specific patch, including thename, patch name, version, PRS information, engineer, and release. It also incsome statistical information - in or out of service, time in service, and so forth.

To determine which patches can be viewed, runpstat first.

-> plis “0”Handle: 0*Filename: /C:/U/PATCH/ringback.tsaVersion: 1.3Patch name: Non_NA_Ringback_Q00632470Ref. num.: 12345PRS number: Q00632470Engineer: John DoeRelease: IPT-3.00.52 SACreated: Wed Mar 19 10:57:02 2003Patch is in-serviceIn-service date: Wed Mar 19 14:29:38 2003In-service for less than 1 dayIn-service number of reset(s): 0Patch is retainedPatch retain level: RESIn-service reset threshold: 5In-service days to watch for resets: 7Number of patch element(s): 1Patch info of element #1: Patch element type: C function Procedure/function name: _npmNSDataProcess Address to patch: 0xb3cac Patch element address: 0x71a8f0value = 0 = 0x0->

or

-> plisPatch handle? 0Handle: 0Filename: /C:/U/PATCH/ringback.tsaVersion: 1.3Patch name: Non_NA_Ringback_Q00632470Ref. num.: 12345PRS number: Q00632470Engineer: John DoeRelease: IPT-3.00.52 SACreated: Wed Mar 19 10:49:26 2003Patch is out-of-serviceOut-of-service reason: Never activatedPatch is retainedPatch retain level: RESIn-service reset threshold: 5In-service days to watch for resets: 7Number of patch element(s): 1



Patch info of element #1: Patch element type: C function Procedure/function name: _npmNSDataProcess Address to patch: 0xb3cacvalue = 0 = 0x0->

Attempting to list an undefined or unloaded patch yields the following output:

-> plis “3”Patch 3 doesn’t exist. Cannot get patch info.value = -1 = 0xffffffff = _func_taskRegsShowRtn + 0xff7b8bff->



mustd.

d foro betch is

all

B.2.46.3 pload, or pload “patchName”

Safety level: Debug. Low risk, provided the patch is correct for the load.

This command loads a patch with the name “patchname” on the card. The patchfirst have been ftp’ed to the card directory “/C:/U/PATCH” before it can be loade

Note that using pload without specifying the patch name results in being promptethe patch name, followed by being prompted for options - whether the patch is tretained, how many times the card can reset in a specified interval before the pataken out of service, and how long the interval is (in days).

-> ploadPatch filename? ringback.tsaRetain patch (y/n)? [y]In-service reset threshold? [5]In-service days to monitor resets? [7]Loading patch from “/C:/U/PATCH/ringback.tsa”Patch handle is: 0value = 0 = 0x0->

or

-> pload “ringback.tsa”Loading patch from “/C:/U/PATCH/ringback.tsa”Patch handle is: 0value = 0 = 0x0->

Attempting to load a non-existent patch yields the following output:

-> pload “invPatch.tsa”Loading patch from “/C:/U/PATCH/invPatch.tsa”PCH1203: Unable to open file “/C:/U/PATCH/invPatch.tsa”.PCH1140: Error while reading in patch. Patch load aborted.Error loading patch from “/C:/U/PATCH/invPatch.tsa”.value = -1 = 0xffffffff = _func_taskRegsShowRtn + 0xff7b8bff-> 2001 3 30 23:32:41 (ItgPatch) :Unable to open patch file “/C:/U/PATCH/invPatch.tsa”2001 3 30 23:32:41 (ItgPatch) :Error reading in patch file during patchLoad2001 3 30 23:32:41 (ItgPatch) :Error loading patch from “/C:/U/PATCH/invPatch.tsa”

->

B.2.46.4 poos “patchNumber”

Safety level: Debug. Low risk, provided the patch is not mandatory for correct chandling (or other operations) in the load.

This command puts a patch out of service but does not unload it.



ut:

ing

ove it

-> poos “0”Are you sure (y/n)? [y]Patch 0 has been deactivated successfully.value = 0 = 0x0-> 2003 3 19 14:46:16 (ItgPatch) :PATCH 0 DEACTIVATED.Name=”Non_NA_Ringback_Q00632470”, Ref#=”12345”, PRS#=”Q00632470”, File=”/C:/U/PATCH/ringback.tsa”

->

Attempting to put an out of service patch out of service yields the following outp

-> poos “0”Cannot deactivate patch 0. It is not in-service.Deactivation of patch 0 aborted.value = -1 = 0xffffffff = _func_taskRegsShowRtn + 0xff7b8bff->-> pstatPatch handle: 0 Filename: /C:/U/PATCH/ringback.tsa Patch version: 1.3 Reference number: 12345 Patch is out-of-service Out-of-service reason: User requested Out-of-service date: Fri Mar 30 23:21:35 2001 Last in-service date: Fri Mar 30 23:21:17 2001 Patch is retained Patch retain level: RESPatch handle: 1* Filename: /C:/U/PATCH/ringbak2.tsa Patch version: 1.3 Reference number: 12345 Patch is in-service In-service date: Fri Mar 30 23:21:41 2001 Patch is retained Patch retain level: RESvalue = 0 = 0x0->

Attempting to put an undefined or unloaded patch out of service yields the followoutput:

-> poos “3”Patch 3 does not exist. Cannot deactivate.Deactivation of patch 3 aborted.value = -1 = 0xffffffff = _func_taskRegsShowRtn + 0xff7b8bff->

B.2.46.5 pout, or pout “patchNumber”

Safety level: Debug. Low risk, provided the patch is no longer needed.

This command removes a patch from the list of loaded patches, but does not remfrom the C: drive.

-> poutPatch handle? 0



t:

singining

Patch 0 has been removed successfully.value = 0 = 0x0->

or

-> pout “0”Patch 0 has been removed successfully.value = 0 = 0x0->

Attempting to remove an in service patch yields the following output:

-> pout “1”Cannot remove patch 1, it is in-service.Could not remove patch 1.value = -1 = 0xffffffff = _func_taskRegsShowRtn + 0xff7b8bff->

Attempting to remove an undefined or unloaded patch yields the following outpu

-> pout “3”Patch 3 doesn’t exist. Cannot remove.Could not remove patch 3.value = -1 = 0xffffffff = _func_taskRegsShowRtn + 0xff7b8bff->

B.2.46.6 pstat, or pstat “patchNumber”


This command prints the key operational and provisioning data about a patch. Uthe patch number makes no difference in the printout for that patch, but the remapatches are ignored. pstat with no parameters prints all patches.

-> pstatPatch handle: 0 Filename: /C:/U/PATCH/ringback.tsa Patch version: 1.3 Reference number: 12345 Patch is out-of-service Out-of-service reason: Never activated Patch is retained Patch retain level: RESPatch handle: 1 Filename: /C:/U/PATCH/ringbak2.tsa Patch version: 1.3 Reference number: 12345 Patch is out-of-service Out-of-service reason: Never activated Patch is retained Patch retain level: RESvalue = 0 = 0x0->



n is

or to view a single patch,

-> pstat “0”Patch handle: 0 Filename: /C:/U/PATCH/ringback.tsa Patch version: 1.3 Reference number: 12345 Patch is out-of-service Out-of-service reason: Never activated Patch is retained Patch retain level: RESvalue = 0 = 0x0->

B.2.47 print_ip_table


This command allows you to check if the IP table used by the address translatiobuilt in memory.

-> print_ip_table

Number of blocks = 1 Number of entry = 2


Block number : 0Entry : 1Node IP : 44.11.223.221Reference count : 5Qos Enabled : 1Send QoS : 3.000000Receive QoS : 3.000000Node Capability : 8value = 20 = 0x14->



the

s to

t

l

TM.lows:

B.2.48 Printing dial plan data


These commands allow the user to identify invalid provisioning, printing to screendata associated with each plan/type pair provisioned. Note that the output haschanged from prior releases; it is now tabular.

The enterprise applicable remote node capability (Node Cap) value correspondendpoint protocol selected in OTM. The values are as follows:

• 0 = H323V2 - no D channel capability

• 1 = ESGF - Nortel based transport of ETSI QSIG Generic Function transpor

• 6 = ISGF - Nortel based transport of ISO QSIG GF.

• 7 = SL1 - Nortel proprietary enterprise ISDN, without ESN5 prefix to diallednumbers

• 8 = SL1ESN5 - SL1 with ESN5 prefixes

• 9 = CSE - Succession Call Server for Enterprise compatible - uses the NorteInteroperability format for non-standard data

The carrier Node Cap values also correspond to endpoint protocol selected in OHowever, they have no use in the enterprise at this time. The values are as fol

• 2 = BELL, 3 = 7SGF_ETSI_V1, 4 = 7SGF_ETSI_V2, 5 = 7SGF_FTUP - forMultimedia Communications Switch; not supported with Meridian 1



dsthat

g

B.2.48.1 Caveat - serious danger from provisioning errors within the DPTABLE.1

In the following displays are “(null) entries for “Digits to Insert”. This corresponto a blank space between two commas in the DPTABLE.1. Putting a zero (“0”) inplace actually gets the ATPM to insert the digit 0.

The following line taken as an excerpt from a DPTABLE shows a blank.

DSC,27,0,0,0, ,47.11.240.37,0,3.0,3.0,7,""

This line prints out as:

Dialed Digits Digits Digits I.P. QoS Send Receive NodeDigits to to to Enabled QoS Qos Cap. Compl. Delete Insert------- ------- ------- ------- --------------- ------- ------- ------- -------27 0 0 (null) 47.11.215.211 Yes 3.000 3.000 7

when printed. Change this to:

DSC,27,0,0,0,0,47.11.240.37,0,3.0,3.0,7,""

and this line prints out as:

Dialed Digits Digits Digits I.P. QoS Send Receive NodeDigits to to to Enabled QoS Qos Cap. Compl. Delete Insert------- ------- ------- ------- --------------- ------- ------- ------- -------27 0 0 0 47.11.215.211 Yes 3.000 3.000 7

when printed. This will insert the 0 in front of the dialled digits prior to transmittinto the remote node.

B.2.48.2 print_npa

This command prints the NPA entries in the dialling plan table.

-> print_npa

NPA Entries-----------

Dialed Digits Digits Digits I.P. QoS Send Receive NodeDigits to to to Enabled QoS Qos Cap. Compl. Delete Insert------- ------- ------- ------- --------------- ------- ------- ------- -------613 765 0 3 (null) 47.11.215.211 Yes 3.000 3.000 7613 769 0 3 (null) 47.11.215.211 Yes 3.000 3.000 7613 778 0 3 (null) 47.11.215.211 Yes 3.000 3.000 7613 961 0 0 (null) 44.11.223.221 Yes 3.000 3.000 8613 967 0 0 (null) 44.11.223.221 Yes 3.000 3.000 8value = 1 = 0x1->



n

B.2.48.3 print_nxx

This command prints the NXX entries in the dialling plan table.

-> print_nxx

NXX Entries-----------

Dialed Digits Digits Digits I.P. QoS Send Receive NodeDigits to to to Enabled QoS Qos Cap. Compl. Delete Insert------- ------- ------- ------- --------------- ------- ------- ------- -------765 0 0 (null) 47.11.215.211 Yes 3.000 3.000 7769 0 0 (null) 47.11.215.211 Yes 3.000 3.000 7778 0 0 (null) 47.11.215.211 Yes 3.000 3.000 7value = 1 = 0x1->

B.2.48.4 print_spn

This command prints the SPN (international, normally) entries in the dialling platable.

-> print_spn

SPN Entries-----------There are [2] entries.There are [1] blocks.-----------------------

Block [0]Dialed Digits Digits Digits I.P. QoS Send Receive NodeDigits to to to Enabled QoS Qos Cap. Compl. Delete Insert------- ------- ------- ------- --------------- ------- ------- ------- -------1613967 0 0 (null) 44.11.223.221 Yes 3.000 3.000 81613961 0 0 (null) 44.11.223.221 Yes 3.000 3.000 8

value = 1 = 0x1->



.

B.2.48.5 print_loc

This command prints the LOC entries in the dialling plan table.

-> print_loc

LOC Entries-----------

Dialed Digits Digits Digits I.P. QoS Send Receive NodeDigits to to to Enabled QoS Qos Cap. Compl. Delete Insert------- ------- ------- ------- --------------- ------- ------- ------- -------343 0 0 (null) 44.11.223.221 Yes 3.000 3.000 8393 0 0 (null) 47.11.215.211 Yes 3.000 3.000 7395 0 0 (null) 47.11.215.211 Yes 3.000 3.000 7396 0 0 (null) 47.11.215.211 Yes 3.000 3.000 7397 0 0 (null) 47.11.215.211 Yes 3.000 3.000 7value = 1 = 0x1->

B.2.48.6 print_cdp

This command prints all of the CDP entries (TSC, DSC) in the dialling plan table

-> print_cdp

TSC Entries-----------There are [0] entries.There are [0] blocks.-----------------------

DSC Entries-----------There are [1] entries.There are [1] blocks.-----------------------

Block [0]Dialed Digits Digits Digits I.P. QoS Send Receive NodeDigits to to to Enabled QoS Qos Cap. Compl. Delete Insert------- ------- ------- ------- --------------- ------- ------- ------- -------4 0 0 (null) 47.11.215.211 Yes 3.000 3.000 7

value = 1 = 0x1->



plan

lanay

can

B.2.48.7 print_dsc

This command prints the CDP Distant Steering Code (DSC) entries in the diallingtable.

-> print_dsc

DSC Entries-----------There are [1] entries.There are [1] blocks.-----------------------

Block [0]Dialed Digits Digits Digits I.P. QoS Send Receive NodeDigits to to to Enabled QoS Qos Cap. Compl. Delete Insert------- ------- ------- ------- --------------- ------- ------- ------- -------4 0 0 (null) 47.11.215.211 Yes 3.000 3.000 7

value = 1 = 0x1->

B.2.48.8 print_tsc

This command prints the CDP Trunk Steering Code (TSC) entries in the dialling ptable. The printout looks identical in format to the DSC entries. Note that there mnot be any entries provisioned for one or more of the dial plan types; since this happen, it was decided to make the TSC the example.

-> print_tsc

TSC Entries-----------There are [0] entries.There are [0] blocks.-----------------------value = 1 = 0x1->



can

B.2.49 rm “filename”

Safety level: Destructive/Debug. This has an immediate, permanent effect, andlead to severe problems if the wrong files are deleted.

Delete a file from the /A: or /C: drive.

-> ll size date time name-------- ------ ------ -------- 512 JUN-06-2000 08:28:50 . <DIR> 512 JUN-06-2000 08:28:50 .. <DIR> 840 JAN-26-2001 13:00:38 CONFIG.INI 840 JAN-26-2001 13:17:40 CONFIG.BAK 238 JAN-23-2001 12:55:12 BOOTP.TAB 238 FEB-12-2001 17:26:12 BOOTP.BAK 205 FEB-12-2001 17:48:02 UMS.INI 21 NOV-14-2000 09:35:16 ITG.INIvalue = 0 = 0x0-> rm “ITG.INI”value = 0 = 0x0-> ll size date time name-------- ------ ------ -------- 512 JUN-06-2000 08:28:50 . <DIR> 512 JUN-06-2000 08:28:50 .. <DIR> 840 JAN-26-2001 13:00:38 CONFIG.INI 840 JAN-26-2001 13:17:40 CONFIG.BAK 238 JAN-23-2001 12:55:12 BOOTP.TAB 238 FEB-12-2001 17:26:12 BOOTP.BAK 205 FEB-12-2001 17:48:02 UMS.INIvalue = 0 = 0x0



can

B.2.50 rmdir “ dirName”

Safety level: Destructive/Debug. This has an immediate, permanent effect, andlead to severe problems if the wrong directories are deleted.

Deletes the specified directory.

-> ll size date time name-------- ------ ------ -------- 512 JUN-06-2000 08:28:44 LOG <DIR> 512 JUN-06-2000 08:28:46 OM <DIR> 512 JUN-06-2000 08:28:50 CONFIG <DIR> 512 JUN-06-2000 08:33:34 FW <DIR> 512 JAN-01-1996 12:00:22 DATA <DIR> 512 JAN-01-1996 12:00:22 ETC <DIR> 512 JAN-01-1996 12:00:22 LOCALE <DIR> 512 FEB-22-2001 15:10:00 TEMP <DIR>value = 0 = 0x0-> rmdir “temp”value = 0 = 0x0-> ll size date time name-------- ------ ------ -------- 512 JUN-06-2000 08:28:44 LOG <DIR> 512 JUN-06-2000 08:28:46 OM <DIR> 512 JUN-06-2000 08:28:50 CONFIG <DIR> 512 JUN-06-2000 08:33:34 FW <DIR> 512 JAN-01-1996 12:00:22 DATA <DIR> 512 JAN-01-1996 12:00:22 ETC <DIR> 512 JAN-01-1996 12:00:22 LOCALE <DIR>value = 0 = 0x0



nate

rmedn

nate

rmedn

B.2.51 rtpPortCompress

Safety level: Debug. Use OTM to set this value.

The user may use this command to set up the card such that RTP packets origifrom ports 17300 to 17350, within the Cisco RTP Header Compression Range.

Note that the card must be disabled to run this command. The setting can be confiusing the itgCardShow (section B.1.20, pg 152) command. The setting will remaiafter a power-down or reset. This is not the default configuration.

B.2.52 rtpPortNonCompress

Safety level: Debug. Use OTM to set this value.

The user may use this command to set up the card such that RTP packets origifrom ports 2300 to 2350 non RTP Header Compression Range.

Note that the card must be disabled to run this command. The setting can be confiusing the itgCardShow (section B.1.20, pg 152) command. The setting will remaiafter a power-down or reset. This is the default configuration.



ed.8”e

1”

the

timeion

ckthe

ia the

B.2.53 set_timeyy, mm, dd, hh, mm, ss

Safety level: Safe. Includes internal error checking to handle mis-typing.

Caution: This command takes its parameter types according to the syntax usFor example, if you use “08”, the command tries to use octal, and “does not exist in octal. “010” is “8” in octal. The ITG card rejects thcommand.Therefore, do not use leading “0” characters unless using octal (“01is “9”) or hexadecimal (“0x12” is “18”).

This command sets the time for both the ITG card’s realtime clock chip (RTC) andVxWorks OS clock. Normally the time and date is downloaded from MAT/OTM;however, this command can be useful when remotely logging into a card and theand date needs to be set to a given value to make synchronizing trace informatpossible.

The IPT application takes its time from the VxWorks OS clock. Normally that clois initialized from the RTC when the card boots up, when MAT/OTM downloads time (on the Leader card) or when the SNMP response returns the time (on theFollower card). This command updates them both to the date and time entered vparametersyy, mm, dd, hh, mm, ss.

-> set_time 1,12,1,16,38,30value = 0 = 0x0->

Note that invalid data is rejected:

-> set_time 3,3,09,16,3,0invalid number: 09->



ding

cificore

tion

tLt oneded.

usedwas

Theing at

B.2.54 setTraceOptionchannel,outputLocation

Safety level: Debug, but misuse can have severe repercussions up to and inclureboot.

This command enables tracing calls within a limited number of modules for a spechannel. Note that the command may be repeated to allow monitoring two or mchannels.

Enabling tracing via this command always enables NPM tracing, and - in conjuncwith other commands - limited IGCC tracing.

To enable IGCC tracing, the user must also enter “igccAddTrace channel”, from“ igccAddTrace, igccNoTrace” (appendix B.2.14 on page 182). Note, though, thaigccAddTrace by itself will not turn on the IGCC trace. IGCC tracing uses the ISchannel ID; the other traces use the local TCID. Since the IGCC traces only existhe D channel card, and the others exist on the card carrying the call, both are ne

The channel number is 0-23 for Pentium and 0-31 for SA. The options foroutputLocation are:

• 0 - disable tracing

• 1 - trace to the logged in terminal shell (or debug port)

• 2 - store in a local file

• 3 - output the trace to the shell and the file

• 6 - output the file to both the trace file and the log file

The following example shows the output when the setTraceOption command is on a single channel. This trace is without any other command (in fact, the sampletaken deliberately after a card reboot, to ensure nothing could possibly be set). message flow starts at the receipt of the SETUP request from the TSM and endthe ALERTING and completion of Fast Start operations.

-> setTraceOption 31,1value = 31 = 0x1f-> 2001 4 25 09:12:04 (NPM) :CH#:31 RTP OPEN: hRtp:0x2ea7340, socket:30, port:2362.2001 4 25 09:12:04 (NPM) :CH#:31 Dest Address: 47.11.215.209:17202001 4 25 09:12:04 (NPM) :CH#:31 npmCallFastStart: 4 codecs to encode2001 4 25 09:12:04 (NPM) :CH#:31 codec 0: g729AnnexAwAnnexB(7)2001 4 25 09:12:04 (NPM) :CH#:31 codec 1: g729AnnexA(5)2001 4 25 09:12:04 (NPM) :CH#:31 codec 2: g729wAnnexB(6)2001 4 25 09:12:04 (NPM) :CH#:31 codec 3: g729(4)2001 4 25 09:12:04 (NPM) :CH#:31 npmCallFastStart: 4 codecs to encode2001 4 25 09:12:04 (NPM) :CH#:31 codec 0: g729AnnexAwAnnexB(7)2001 4 25 09:12:04 (NPM) :CH#:31 codec 1: g729AnnexA(5)2001 4 25 09:12:04 (NPM) :CH#:31 codec 2: g729wAnnexB(6)2001 4 25 09:12:04 (NPM) :CH#:31 codec 3: g729(4)2001 4 25 09:12:04 (NPM) :CH#:31 cmEvChannelParameters,chanName=g729AnnexAwAnnexB,co-dec=7



tselfre

2001 4 25 09:12:04 (NPM) :CH#:31 hsChan 0x229d248 haChan 0x4007d02001 4 25 09:12:04 (NPM) :CH#:31 txPayload: 3: vifSize 2402001 4 25 09:12:04 (NPM) :CH#:31 cmEvChannelSetAddress: isOrigin 1 47.11.215.210:23002001 4 25 09:12:04 (NPM) :CH#:31 hsChan 0x229d248 haChan 0x4007d02001 4 25 09:12:04 (NPM) :CH#:31 cmEvChannelParameters,chanName=g729AnnexAwAnnexB,co-dec=72001 4 25 09:12:04 (NPM) :CH#:31 hsChan 0x229d280 haChan 0x40089c2001 4 25 09:12:04 (NPM) :CH#:31 rxPayload: 3: vifSize 2402001 4 25 09:12:04 (NPM) :CH#:31 farEndSWVer = 12001 4 25 09:12:04 (NPM) :CH#:31 ***Legacy: but using H323 codec payload negotation2001 4 25 09:12:04 (NPM) :CH#:31 FS present in H323 ALERT so sending ALERT to TSM2001 4 25 09:12:04 (NPM) :CH#:31 Sending NpmTsmCallAccept: g729AnnexAwAnnexB(7): vif-Size 2402001 4 25 09:12:04 (NPM) :CH#:31 hsChan 0x229d280 haChan 0x40089c2001 4 25 09:12:04 (NPM) :CH#:31 Initiating terminal capability set negotation2001 4 25 09:12:04 (NPM) :CH#:31 codec 0: g729AnnexAwAnnexB(7)2001 4 25 09:12:04 (NPM) :CH#:31 codec 1: g729AnnexA(5)2001 4 25 09:12:04 (NPM) :CH#:31 codec 2: g729wAnnexB(6)2001 4 25 09:12:04 (NPM) :CH#:31 codec 3: g729(4)2001 4 25 09:12:04 (NPM) :CH#:31 codec 4: t38fax(-1)2001 4 25 09:12:04 (NPM) :CH#:31 [1] g711Ulaw64k: packetSize 10: cmCapAudio: cmCapRe-ceiveAndTransmit2001 4 25 09:12:04 (NPM) :CH#:31 [2] g711Alaw64k: packetSize 10: cmCapAudio: cmCapRe-ceiveAndTransmit2001 4 25 09:12:04 (NPM) :CH#:31 [3] g729AnnexAwAnnexB: packetSize 3: cmCapAudio: cm-CapReceiveAndTransmit2001 4 25 09:12:04 (NPM) :CH#:31 [4] g729AnnexA: packetSize 3: cmCapAudio: cmCapRe-ceiveAndTransmit2001 4 25 09:12:04 (NPM) :CH#:31 [5] g729wAnnexB: packetSize 3: cmCapAudio: cmCapRe-ceiveAndTransmit2001 4 25 09:12:04 (NPM) :CH#:31 [6] g729: packetSize 3: cmCapAudio: cmCapReceiveAn-dTransmit2001 4 25 09:12:04 (NPM) :CH#:31 [7] t38fax: packetSize -1: cmCapData: cmCapReceive-AndTransmit2001 4 25 09:12:04 (NPM) :CH#:31 Initiating Master/Slave negotation2001 4 25 09:12:04 (NPM) :CH#:31 {g711Ulaw64k, g711Alaw64k, g729AnnexAwAnnexB,g729AnnexA, g729wAnnexB, g729}2001 4 25 09:12:04 (NPM) :CH#:31 {t38fax}

Note:To enable TSM tracing, the user must enter “tsmSetTraceOption TCID,[0 or !0]”(appendix B.2.63 on page 227). Note, though, that tsmSetTraceOption by iwill not turn on the TSM trace; both this command and “mixSetLogOpt 0,1,1” aneeded.



king

t is

ted

B.2.55 shellPasswordNvramClear

Safety level: Debug; implications at user login.

This command resets the current userid/password back to the factory default, taeffect after the card is rebooted.

See ITG shell commandshellPasswordSet (section B.1.40, pg 165).

-> shellPasswordNvramClearvalue = 0 = 0x0

B.2.56 shellTimeoutGet

Safety level: Safe.

Displays the currently configured idle shell timeout value in seconds.

-> shellTimeoutGetvalue = 1200 = 0x4b0

B.2.57 shellTimeoutSettimeout

Safety level: Debug. May prevent user login sessions from ending.

This command sets the idle shell timeout value in seconds. Valid range fortimeoutis30 to 4095. The default timeout is 1200 (20 minutes). The value is persistent: istored in NVRAM. The new timeout value takes effect immediately.

-> shellTimeoutSet 30value = 0 = 0x0

B.2.58 showMemConfig - Pentium only


This command displays the size of the ITG card’s DRAM memory. Can be execufrom the BIOS or VxWorks shells.

-> showMemConfig

Memory Configuration:Bank0: 64MB

value = 0 = 0x0



B.2.59 tcpstatShow


This command displays the TCP protocol statistics.

-> tcpstatShowTCP: 11329 packets sent 819 data packets (57979 bytes) 0 data packet (0 byte) retransmitted 10428 ack-only packets (28 delayed) 0 URG only packet 0 window probe packet 0 window update packet 82 control packets 33649 packets received 866 acks (for 58045 bytes) 31925 duplicate acks 0 ack for unsent data 817 packets (20868 bytes) received in-sequence 9642 completely duplicate packets (0 byte) 0 packet with some dup. data (0 byte duped) 20 out-of-order packets (45 bytes) 0 packet (0 byte) of data after window 0 window probe 11 window update packets 0 packet received after close 0 discarded for bad checksum 0 discarded for bad header offset field 0 discarded because packet too short 25 connection requests 23 connection accepts 48 connections established (including accepts) 73 connections closed (including 14 drops) 0 embryonic connection dropped 890 segments updated rtt (of 890 attempts) 0 retransmit timeout 0 connection dropped by rexmit timeout 0 persist timeout 22258 keepalive timeouts 22258 keepalive probes sent 0 connection dropped by keepalive 54 pcb cache lookups failedvalue = 29 = 0x1d



e is

se T.

B.2.60 tlanDuplexSetduplexMode


This command sets the duplex mode of the TLAN interface while operating in th10BT mode. The command takes effect immediately. The duplex mode settingsaved in NVRAM and read at startup. The parameterduplexMode is set as follows:

0 - enables full duplex mode1 - enables half duplex mode

Note that “1” has no real effect unless the TLAN speed was already set to 10 ba

-> tlanDuplexSet 0

Forcing TLAN Interface to Full-Duplex OperationNote: tlanDuplexSet only required when TLAN not in AUTO-NEGOTIATION modeUse itgCardShow to view the Configuration of the TLAN InterfacePort on network switch may require manual configuration for full-duplex modeChanges will take effect Immediatelyvalue = 0 = 0x0-> itgCardShow

Index : 1 Type : ITG2..... esn5Prefix : |100| TLAN set to 10BaseT Operation TLAN set to Full Duplex Operation ELAN set to 10BaseT Operation ELAN set to Half Duplex Operationvalue = 38 = 0x26 = ’&’->->->-> tlanDuplexSet 1

Forcing TLAN Interface to Half-Duplex OperationNote: tlanDuplexSet only required when TLAN not in AUTO-NEGOTIATION modeUse itgCardShow to view the Configuration of the TLAN InterfacePort on network switch may require manual configuration for full-duplex modeChanges will take effect Immediatelyvalue = 0 = 0x0->

-> itgCardShow

Index : 1 Type : ITG2..... esn5Prefix : |100| TLAN set to 10BaseT Operation TLAN set to Half Duplex Operation ELAN set to 10BaseT Operation ELAN set to Half Duplex Operationvalue = 38 = 0x26 = ’&’->



therfacelated

takestup.

e) andatingfail.

Card

fullyt canurs.

B.2.61 tlanSpeedSetspeed

Safety level: Debug, potentially destructive.

Sets the speed of the TLAN interface. By default, this interface auto-negotiates tohighest speed supported by the hub or switch; with a 10/100BT switch, the intenegotiates to 100BT. This command is useful when debugging ethernet speed reproblems and you want to force the interface to 10BT operation; the command effect immediately. The duplex mode setting is saved in NVRAM and read at starThe parameterspeed is set as follows:

10 - To enable 10MB only operation.10100 - To enable auto-negotiation.

Note that changing the speed may result in some instability (as the speeds changpossibly even loss of calls. While the change occurs (and especially when negotithe speed) the card may go into local fall-back mode. If it does, new calls will

The following example occurred when setting the speed to 10 base T on a Mediaalready running at 10 base T.

-> tlanSpeedSet 10

Forcing TLAN Interface to 10BaseT OperationFull/Half Duplex must be set with tlanDuplexSetUse itgCardShow to view the Configuration of the TLAN InterfaceChanges will take effect Immediatelyvalue = 0 = 0x0->

Changing the speed to autonegotiate when the hub is 10 base T only is less thaneffective; if the fastest you have is 10 base T, you cannot get more. However, ibe done. Note that auto negotiation may cause call failures as negotiation occ

-> tlanSpeedSet 10100

Setting TLAN Interface to AUTO-NEGOTIATE Speed and Duplex ParametersUse itgCardShow to view the Configuration of the TLAN InterfaceChanges take effect Immediatelyvalue = 0 = 0x0-> 2001 4 14 00:04:32 (IGCC) :ITG0402 - Voice ethernet port disconnected2001 4 14 00:04:32 (COM) :mixFree: instance b005:mark (tRmm) instance b029 0x2e9a9d8already free2001 4 14 00:04:32 (COM) :SNMP ALARM: Card is recovered from FALLBACK mode. Communi-cation between Leader and the card is up.2001 4 14 00:04:34 (IGCC) :ITG0102 - Voice ethernet port Reconnected2001 4 14 00:04:34 (RMM) :rmmLeaderInit: set Leader Mng IP address to 47.11.217.552001 4 14 00:04:34 (RMM) :***LDR send back GK status:12001 4 14 00:04:34 (RMM) :***FL card update GK status: 1

->



c,nds

nd.

yred at

IDe

B.2.62 TsmDspStat =1/0

Safety level: Debug/output load. Under heavy call origination/call clearing traffithis may slow the system. It should be set, the necessary commarun or test calls made, and then cleared.

To observe DSP statistics, the user sets a variable rather than issuing a commaSetting this to 1 causes the DSP statistics printed by thetsm_stat_req_vp_delay,tsm_stat_req_errorandtsm_stat_req_rx_txcommands to be printed at the end of ancall. This also needs to be set to 1 if these commands are asynchronously entethe VxWorks shell; if set to 0 nothing will print when they are entered.

This “end of call” mechanism provides a useful means to see if DSP errors areoccurring during calls. No identifying information about the call (other than the TCand timestamp) are given, so if information about a particular call is needed, ush323SessionShow (section B.1.15, pg 143) while the call is active to identify thechannel being used.

This is cleared by setting the variable to 0. The default isoff; the state is not savedand returns tooff if the card is reset or reboots.

-> TsmDspStat = 1_TsmDspStat = 0x346298: value = 1 = 0x1->SEP 06 11:39:08 tMVX_DIM: Info TCID 0, avg_playout_delay = 59SEP 06 11:39:08 tMVX_DIM: Info TCID 0, lost_packet_count = 0SEP 06 11:39:08 tMVX_DIM: Info TCID 0, replay_packet_count = 0SEP 06 11:39:08 tMVX_DIM: Info TCID 0, idle_packet_count = 14SEP 06 11:39:08 tMVX_DIM: Info TCID 0, dropped_packet_count = 0SEP 06 11:39:08 tMVX_DIM: Info TCID 0, rx_packet_count = 156SEP 06 11:39:08 tMVX_DIM: Info TCID 0, invalid_header_count = 0SEP 06 11:39:08 tMVX_DIM: Info TCID 0, to_micro_overflow_count = 0SEP 06 11:39:08 tMVX_DIM: Info TCID 0, lost_enh_packet_count = 0SEP 06 11:39:08 tMVX_DIM: Info TCID 0, no_core_packet_count = 0SEP 06 11:39:08 tMVX_DIM: Info TCID 0, rx_packet_count = 78SEP 06 11:39:08 tMVX_DIM: Info TCID 0, tx_packet_count = 81SEP 06 11:39:08 tMVX_DIM: Info TCID 0, silence_packet_count = 0SEP 06 11:39:08 tMVX_DIM: Info TCID 0, min_jitter = 20SEP 06 11:39:08 tMVX_DIM: Info TCID 0, max_jitter = 20->



the

and

B.2.63 tsmSetTraceOptionTCID,[0 or !0]


This command turns on well, but does not turn off as well. The difficulty is thatcommand does not work in isolation; you need to turn on TSM tracing usingmixSetLogOptas well. However, after turning ontsmSetTraceOptionand debugging,simply turning offtsmSetTraceOption is incomplete; themixSetLogOpt remainsenabled.

The parameters TCID is in the legitimate range for the card - 0 to 23 for Pentium0-31 for SMC. The “on/off” parameter is “0 is off, any other is on”.

The following shows the difference between tracing with and withouttsmSetTraceOption. The first trace shows themixSetLogOpt command alone; thesecond adds the TSM trace in red, bold.

-> mixSetLogOpt 0,1,1value = 0 = 0x0-> 2001 4 25 09:26:30 (TSM) :IgccTsmCallSetup(34) from IGCC: tcid 31: SPU_IDLE(1):0xd95f02001 4 25 09:26:30 (TSM) :message size (setup): 1142001 4 25 09:26:30 (TSM) :AtpmTsmAddTranOK(27) from ATPM: tcid 31: SPU_REQ_O_CALL(8):0xdbf842001 4 25 09:26:30 (TSM) :Num_dig_delete=0 NumOfCodecs=2 nodeCap=8 dig_insert=0esn5LocEnable=0 esn5LocDigit=|| remoteIP 47.11.215.2092001 4 25 09:26:30 (TSM) :tsm_REQ_O_CALL_PROC: remote nodeCap = 82001 4 25 09:26:30 (TSM) :---> but src node doesn’t have esn5 signalling: pad w/ esn5digs2001 4 25 09:26:30 (TSM) :final digit translation result=|1003500|, startDig=3, orig-startDig=02001 4 25 09:26:30 (TSM) :DimTsmReportChOpened(24) from DIM: tcid 31: SPU_SETUP_REQ(9):0xd7e342001 4 25 09:26:30 (TSM) :NpmTsmCallAccept(4) from NPM: tcid 31: SPU_SETUP_REQ(9):0xdcbf02001 4 25 09:26:30 (TSM) :useInBandTone 1: msg g729AnnexAwAnnexB(7):240 currentg729AnnexAwAnnexB(7):2402001 4 25 09:26:30 (TSM) :Requesting DSP to stop local busy tone generation.2001 4 25 09:26:30 (TSM) :Accept msg from NPM, Change DSP to voice mode

-> tsmSetTraceOption 31,1value = 31 = 0x1f-> 2001 4 25 09:31:12 (TSM) :IgccTsmCallSetup(34) from IGCC: tcid 31: SPU_IDLE(1):0xd95f02001 4 25 09:31:12 (TSM) :TsmMsgSendToIGCC: tcid 31: TsmIgccCallProceeding(42)2001 4 25 09:31:12 (TSM) :message size (setup): 1142001 4 25 09:31:12 (TSM) :tsm_dsp_open2001 4 25 09:31:12 (TSM) :Addr Trans Req to ATPM: TON: 6 NPI: 2 digits: 35002001 4 25 09:31:12 (TSM) :AtpmTsmAddTranOK(27) from ATPM: tcid 31: SPU_REQ_O_CALL(8):0xdbf842001 4 25 09:31:12 (TSM) :Num_dig_delete=0 NumOfCodecs=2 nodeCap=8 dig_insert=0esn5LocEnable=0 esn5LocDigit=|| remoteIP 47.11.215.2092001 4 25 09:31:12 (TSM) :tsm_REQ_O_CALL_PROC: remote nodeCap = 82001 4 25 09:31:12 (TSM) :---> but src node doesn’t have esn5 signalling: pad w/ esn5digs



creen

rate

2001 4 25 09:31:12 (TSM) :final digit translation result=|1003500|, startDig=3, orig-startDig=02001 4 25 09:31:12 (TSM) :DCH_CAP 8: freeBufferPtr 0x2e68408: uumPtr 0x2e684302001 4 25 09:31:12 (TSM) :sizeOfUUM 118: tsmData 0x2e684a62001 4 25 09:31:12 (TSM) :NpmMsgSPUtoNPM: tcid 31: TsmNpmCallSetup(44)2001 4 25 09:31:12 (TSM) :DimTsmReportChOpened(24) from DIM: tcid 31: SPU_SETUP_REQ(9):0xd7e342001 4 25 09:31:12 (TSM) :tsm_invalid: type=24, tcid=31 (state=9)2001 4 25 09:31:12 (TSM) :tsm_save_pad_value: set=0, rx_pad=5, tx_pad=02001 4 25 09:31:12 (TSM) :tsm_save_pad_value: rx=0-6(dB), tx=0-0(dB)2001 4 25 09:31:12 (TSM) :channel 31 DSP mode is: 2 when it receive this pad value2001 4 25 09:31:13 (TSM) :NpmTsmCallAccept(4) from NPM: tcid 31: SPU_SETUP_REQ(9):0xdcbf02001 4 25 09:31:13 (TSM) :useInBandTone 1: msg g729AnnexAwAnnexB(7):240 currentg729AnnexAwAnnexB(7):2402001 4 25 09:31:13 (TSM) :Requesting DSP to stop local busy tone generation.2001 4 25 09:31:13 (TSM) :Accept msg from NPM, Change DSP to voice mode2001 4 25 09:31:13 (TSM) :tsm_dsp_voice2001 4 25 09:31:13 (TSM) :TsmMsgSendToIGCC: tcid 31: TsmIgccCallAccept(37)

One note of caution: the TSM mix trace does all channels; these may keep the sscrolling when no messages are being carried for the monitored channels.

B.2.64 tsm_stat_req commands

Note:You must use “mixSetLogOpt 10,1,1” before any of these commands will geneoutput.

Use these commands to query the DSP for information regarding the call.



hee 0 -

on.r an

B.2.64.1 tsm_stat_req_ecdbgTCID or reqECDbg TCID


This commands return the echo canceller debug statistics for a given channel. TparameterTCID specifies a channel on the ITG card; valid values are in the rang31 (Media Card), 0 - 23(Pentium),0 - 7 (486). If theDivergence cntvalue is high (20or higher), the EC is having difficulty converging on the echo and the users willprobably hear echo during the call.

The output format depends on the DSP load, which actually executes the functiTherefore, examples of the current loads are given. The following is the output foapplication load with Telogy 5.0.

The following is the output for an application load with Telogy 7.01.

-> tsm_stat_req_ecdbg 2value = 0 = 0x0->SEP 06 09:01:06 tMVX_DIM: Info TSG: 2 Echo Canceller Debug StatsSEP 06 09:01:06 tMVX_DIM: Info CNV state = 0SEP 06 09:01:06 tMVX_DIM: Info Px level = 290SEP 06 09:01:06 tMVX_DIM: Info Py level = 132SEP 06 09:01:06 tMVX_DIM: Info Pe level = 131SEP 06 09:01:06 tMVX_DIM: Info Post update cnt = 370SEP 06 09:01:06 tMVX_DIM: Info Attempt update cnt = 370SEP 06 09:01:06 tMVX_DIM: Info Divergence cnt = 0SEP 06 09:01:06 tMVX_DIM: Info ERLE bypass cnt = 0SEP 06 09:01:06 tMVX_DIM: Info XTONE count = 0SEP 06 09:01:06 tMVX_DIM: Info Fore switch cnt = 0SEP 06 09:01:06 tMVX_DIM: Info Back switch cnt = 0SEP 06 09:01:06 tMVX_DIM: Info Xidle count = 34614SEP 06 09:01:06 tMVX_DIM: Info Other bypass cnt = 2

Should be small ifEC working OK

JAN 01 13:54:18 tMVX_DIM: Info TSG: 0 Echo Canceller Debug StatsJAN 01 13:54:18 tMVX_DIM: Info CNV state = 1JAN 01 13:54:18 tMVX_DIM: Info Px level = 72JAN 01 13:54:18 tMVX_DIM: Info Py level = 57JAN 01 13:54:18 tMVX_DIM: Info Pe level = 58JAN 01 13:54:18 tMVX_DIM: Info Post update cnt = 1718JAN 01 13:54:18 tMVX_DIM: Info Attempt update cnt = 1718JAN 01 13:54:18 tMVX_DIM: Info Divergence cnt = 0JAN 01 13:54:18 tMVX_DIM: Info ERLE bypass cnt = 1515JAN 01 13:54:18 tMVX_DIM: Info XTONE count = 19JAN 01 13:54:18 tMVX_DIM: Info Foregrnd switch cnt = 4JAN 01 13:54:18 tMVX_DIM: Info Backgrnd switch cnt = 2JAN 01 13:54:18 tMVX_DIM: Info Xidle count = 26075JAN 01 13:54:18 tMVX_DIM: Info Other bypass cnt = 47JAN 01 13:54:18 tMVX_DIM: Info Search bypass cnt = 126617680JAN 01 13:54:18 tMVX_DIM: Info ERLE estimate = 500JAN 01 13:54:18 tMVX_DIM: Info OpnLpDet switch cnt = 0

Should be small ifEC working OK



6
The following is the output for an application load with Telogy 8.1 (ITG Trunk 2.x.2and IPT 3.0)
-> tsm_stat_req_ecdbg 31value = 0 = 0x0-> 2003 3 12 10:08:18 (DIM) :TSG: 31 Echo Canceller Debug Stats

2003 3 12 10:08:18 (DIM) : Px level = -946

2003 3 12 10:08:18 (DIM) : Py level = -1273

2003 3 12 10:08:18 (DIM) : Pe level = -1273

2003 3 12 10:08:18 (DIM) : acom_estimate = 728

2003 3 12 10:08:18 (DIM) : len = 25

2003 3 12 10:08:18 (DIM) : ERLE estimate = 728

2003 3 12 10:08:18 (DIM) :TCID 31, internal_use[0] = 0x02003 3 12 10:08:18 (DIM) :TCID 31, internal_use[1] = 0xf62003 3 12 10:08:18 (DIM) :TCID 31, internal_use[2] = 0x02003 3 12 10:08:18 (DIM) :TCID 31, internal_use[3] = 0x02003 3 12 10:08:18 (DIM) :TCID 31, internal_use[4] = 0x02003 3 12 10:08:18 (DIM) :TCID 31, internal_use[5] = 0x02003 3 12 10:08:18 (DIM) :TCID 31, internal_use[6] = 0x02003 3 12 10:08:18 (DIM) :TCID 31, internal_use[7] = 0x7d2003 3 12 10:08:18 (DIM) :TCID 31, internal_use[8] = 0x02003 3 12 10:08:18 (DIM) :TCID 31, internal_use[9] = 0xb72003 3 12 10:08:18 (DIM) :TCID 31, internal_use[10] = 0x5982003 3 12 10:08:18 (DIM) :TCID 31, internal_use[11] = 0x1d392003 3 12 10:08:18 (DIM) :TCID 31, internal_use[12] = 0x02003 3 12 10:08:18 (DIM) :TCID 31, internal_use[13] = 0x02003 3 12 10:08:18 (DIM) :TCID 31, internal_use[14] = 0x02003 3 12 10:08:18 (DIM) :TCID 31, internal_use[15] = 0x02003 3 12 10:08:18 (DIM) :TCID 31, internal_use[16] = 0x12003 3 12 10:08:18 (DIM) :TCID 31, internal_use[17] = 0x02003 3 12 10:08:18 (DIM) :TCID 31, internal_use[18] = 0x02003 3 12 10:08:18 (DIM) :TCID 31, internal_use[19] = 0xb36c2003 3 12 10:08:18 (DIM) :TCID 31, internal_use[20] = 0x02003 3 12 10:08:18 (DIM) :TCID 31, internal_use[21] = 0x92003 3 12 10:08:18 (DIM) :TCID 31, internal_use[22] = 0x92003 3 12 10:08:18 (DIM) :TCID 31, internal_use[23] = 0x112003 3 12 10:08:18 (DIM) :TCID 31, internal_use[24] = 0x1

->



.1
The following is the an example of the output for an application load with Telogy 8(ITG Trunk 2.1 and IPT 3.0), usingreqECDbg instead oftsm_stat_req_ecdbg:
-> reqECDbg 31value = 0 = 0x0-> 2003 3 12 10:20:07 (DIM) :TSG: 31 Echo Canceller Debug Stats

2003 3 12 10:20:07 (DIM) : Px level = -946

2003 3 12 10:20:07 (DIM) : Py level = -1273

2003 3 12 10:20:07 (DIM) : Pe level = -1273

2003 3 12 10:20:07 (DIM) : acom_estimate = 728

2003 3 12 10:20:07 (DIM) : len = 25

2003 3 12 10:20:07 (DIM) : ERLE estimate = 728

2003 3 12 10:20:07 (DIM) :TCID 31, internal_use[0] = 0x02003 3 12 10:20:07 (DIM) :TCID 31, internal_use[1] = 0xf62003 3 12 10:20:07 (DIM) :TCID 31, internal_use[2] = 0x02003 3 12 10:20:07 (DIM) :TCID 31, internal_use[3] = 0x02003 3 12 10:20:07 (DIM) :TCID 31, internal_use[4] = 0x02003 3 12 10:20:07 (DIM) :TCID 31, internal_use[5] = 0x02003 3 12 10:20:07 (DIM) :TCID 31, internal_use[6] = 0x02003 3 12 10:20:07 (DIM) :TCID 31, internal_use[7] = 0x7d2003 3 12 10:20:07 (DIM) :TCID 31, internal_use[8] = 0x02003 3 12 10:20:07 (DIM) :TCID 31, internal_use[9] = 0xb72003 3 12 10:20:07 (DIM) :TCID 31, internal_use[10] = 0x59c2003 3 12 10:20:07 (DIM) :TCID 31, internal_use[11] = 0x71412003 3 12 10:20:07 (DIM) :TCID 31, internal_use[12] = 0x02003 3 12 10:20:07 (DIM) :TCID 31, internal_use[13] = 0x02003 3 12 10:20:07 (DIM) :TCID 31, internal_use[14] = 0x02003 3 12 10:20:07 (DIM) :TCID 31, internal_use[15] = 0x02003 3 12 10:20:07 (DIM) :TCID 31, internal_use[16] = 0x12003 3 12 10:20:07 (DIM) :TCID 31, internal_use[17] = 0x02003 3 12 10:20:07 (DIM) :TCID 31, internal_use[18] = 0x02003 3 12 10:20:07 (DIM) :TCID 31, internal_use[19] = 0xb36c2003 3 12 10:20:07 (DIM) :TCID 31, internal_use[20] = 0x02003 3 12 10:20:07 (DIM) :TCID 31, internal_use[21] = 0x92003 3 12 10:20:07 (DIM) :TCID 31, internal_use[22] = 0x92003 3 12 10:20:07 (DIM) :TCID 31, internal_use[23] = 0x112003 3 12 10:20:07 (DIM) :TCID 31, internal_use[24] = 0x1

->

The key fields decode as follows:Px level Instantaneous power level of far end userPy level Instantaneous power level of near end userPe level Error level (echo residual before NLP)

Maximum values: 2^28, or 268,435,456, or +3 dbm0

acom_estimateEstimated ACOM in Q4

ERLE estimateEstimated ERL in Q4 (hybrid loss); /4 = ERL in dB



l. Belreta

ic

r to

kets

core

nce

t reseting

B.2.64.2 tsm_stat_req_errorTCID or reqError TCID


This query returns the current errors detected by the DSP for the specified channesure the variableTsmDspStat = 1/0(section B.2.62, pg 226) is set to 1 or nothing wilbe output. The parameterTCID specifies a channel on the ITG card; valid values ain the range of 0 - 31 for Media Card, 0 - 23 for the 24 port card. The following dais displayed:

• Number of incoming voice packets dropped by the DSP due to invalid genervoice header syntax.

• Number of transmit voice packets dropped due to voice buffer overflow (buffemicro was busy when DSP attempted to send packet).

• Estimated number of lost incoming enhancement voice packets (two core pacreceived without intervening enhancement). This is only for E-ADPCM.

• Number of dropped incoming enhancement voice packets due to absence of apacket. This is only for E-ADPCM.

• Number of packets lost by the network, i.e. from missing incoming RTP sequenumbers (in Telogy 7.01 output only).

This command can be entered repeatedly during a call, the counter values are nountil a new call is made. The following is the output for an application load containTelogy 5.0:

-> tsm_stat_req_error 0value = 0 = 0x0->JAN 17 14:44:48 tMVX_DIM: Info TCID 0, invalid_header_count = 0JAN 17 14:44:48 tMVX_DIM: Info TCID 0, to_micro_overflow_count = 0JAN 17 14:44:48 tMVX_DIM: Info TCID 0, lost_enh_packet_count = 0JAN 17 14:44:48 tMVX_DIM: Info TCID 0, no_core_packet_count = 0->

The following is the output for an application load containing Telogy 7.0.6.23:

-> tsm_stat_req_error 0value = 0 = 0x0->JAN 01 14:33:55 tMVX_DIM: Info TCID 0, invalid_header_count = 0JAN 01 14:33:55 tMVX_DIM: Info TCID 0, to_micro_overflow_count = 0JAN 01 14:33:55 tMVX_DIM: Info TCID 0, lost_enh_packet_count = 0JAN 01 14:33:55 tMVX_DIM: Info TCID 0, no_core_packet_count = 0JAN 01 14:33:55 tMVX_DIM: Info TCID 0, pkt_lost_by_network = 0->

The following is the output for an application load containing Telogy 8.1:

tsm_stat_req_error 0value = 0 = 0x0-> 2040 2 16 00:12:21 (DIM) :TCID 0, invalid_header_count = 0



2040 2 16 00:12:21 (DIM) :TCID 0, to_micro_overflow_count = 02040 2 16 00:12:21 (DIM) :TCID 0, lost_enh_packet_count = 02040 2 16 00:12:21 (DIM) :TCID 0, no_core_packet_count = 02040 2 16 00:12:21 (DIM) :TCID 0, pkt_lost_by_network = 02040 2 16 00:12:21 (DIM) :TCID 0, rc4key_update_lost_pkt_count = 02040 2 16 00:12:21 (DIM) :TCID 0, invalid_mac_header_count = 02040 2 16 00:12:21 (DIM) :TCID 0, invalid_ssrc_count = 02040 2 16 00:12:21 (DIM) :TCID 0, invalid_payload_count = 0



the

eset

ort

ue.

B.2.64.3 tsm_stat_req_rx_txTCID or reqRxTx TCID


This query returns the following data for the current call on the channel. Be surevariableTsmDspStat = 1/0 (section B.2.62, pg 226) is set to 1 or nothing will beoutput. The query can be repeated for the duration of the call, the counts will be rat the beginning of the next call. The parameterTCID specifies a channel on the ITGcard; valid values are in the range of 0 - 31 for Media Card, and 0 - 23 for the 24 pcard.

• Number of Rx packets sent for playout

• Number of Tx packets the DSP has written to the voice data buffer

• Number of voice frames on Tx side classified as silence

• Minimum jitter

• Maximum jitter

When VAD is disabled, the Rx and Tx packet counts should be very close in valThe following is the output for an application load containing Telogy 5.0:

-> tsm_stat_req_rx_tx 0value = 0 = 0x0->JAN 17 14:44:36 tMVX_DIM: Info TCID 0, rx_packet_count = 7884JAN 17 14:44:36 tMVX_DIM: Info TCID 0, tx_packet_count = 7887JAN 17 14:44:36 tMVX_DIM: Info TCID 0, silence_packet_count = 0JAN 17 14:44:36 tMVX_DIM: Info TCID 0, min_jitter = 20JAN 17 14:44:36 tMVX_DIM: Info TCID 0, max_jitter = 20->

The following is the output for an application load containing Telogy 7.0.6.23:

-> tsm_stat_req_rx_tx 0value = 0 = 0x0->JAN 01 14:33:39 tMVX_DIM: Info TCID 0, rx_packet_count = 2979JAN 01 14:33:39 tMVX_DIM: Info TCID 0, tx_packet_count = 2983JAN 01 14:33:39 tMVX_DIM: Info TCID 0, silence_packet_count = 0JAN 01 14:33:39 tMVX_DIM: Info TCID 0, min_jitter = 18JAN 01 14:33:39 tMVX_DIM: Info TCID 0, max_jitter = 22JAN 01 14:33:39 tMVX_DIM: Info TCID 0, rtp_average_jitter = 0JAN 01 14:33:39 tMVX_DIM: Info TCID 0, tx_grant_sync_drop = 0JAN 01 14:33:39 tMVX_DIM: Info TCID 0, tx_octets = 477280JAN 01 14:33:39 tMVX_DIM: Info TCID 0, rx_octets = 476640JAN 01 14:33:39 tMVX_DIM: Info TCID 0, aal2_cod_prof_chgs = 0JAN 01 14:33:39 tMVX_DIM: Info TCID 0, dtmf_tx_octets = 0JAN 01 14:33:39 tMVX_DIM: Info TCID 0, dtmf_rx_octets = 0->




-> tsm_stat_req_rx_tx 31value = 0 = 0x0-> 2003 3 12 10:28:46 (DIM) :TCID 31, rx_packet_count = 19732003 3 12 10:28:46 (DIM) :TCID 31, tx_packet_count = 10082003 3 12 10:28:46 (DIM) :TCID 31, silence_packet_count = 158512212003 3 12 10:28:46 (DIM) :TCID 31, min_jitter = 02003 3 12 10:28:46 (DIM) :TCID 31, max_jitter = 302003 3 12 10:28:46 (DIM) :TCID 31, rtp_average_jitter = 302003 3 12 10:28:46 (DIM) :TCID 31, pkt_lost_by_network = 02003 3 12 10:28:46 (DIM) :TCID 31, tx_grant_sync_drop = 02003 3 12 10:28:46 (DIM) :TCID 31, tx_octets = 309613602003 3 12 10:28:46 (DIM) :TCID 31, rx_octets = 627882003 3 12 10:28:46 (DIM) :TCID 31, aal2_cod_prof_chgs = 02003 3 12 10:28:46 (DIM) :TCID 31, dtmf_tx_packets = 02003 3 12 10:28:46 (DIM) :TCID 31, dtmf_rx_packets = 02003 3 12 10:28:46 (DIM) :TCID 31, sid_tx_packet_count = 77325222003 3 12 10:28:46 (DIM) :TCID 31, sid_rx_packet_count = 2332003 3 12 10:28:46 (DIM) :TCID 31, tx_last_timestamp = 18869336802003 3 12 10:28:46 (DIM) :TCID 31, rx_last_timestamp = 18869347202003 3 12 10:28:46 (DIM) :TCID 31, tx_ext_seq_num = 1182003 3 12 10:28:46 (DIM) :TCID 31, rx_ext_seq_num = 02003 3 12 10:28:46 (DIM) :TCID 31, tx_last_seq_num = 2812003 3 12 10:28:46 (DIM) :TCID 31, rx_last_seq_num = 22092003 3 12 10:28:46 (DIM) :TCID 31, tx_last_pkt_type = 02003 3 12 10:28:46 (DIM) :TCID 31, rx_last_pkt_type = 02003 3 12 10:28:46 (DIM) :TCID 31, tx_net_pkts = 02003 3 12 10:28:46 (DIM) :TCID 31, rx_net_pkts = 02003 3 12 10:28:46 (DIM) :TCID 31, rx_last_ssrc = -14305328992003 3 12 10:28:46 (DIM) :TCID 31, rx_out_of_order_pkts = 02003 3 12 10:28:46 (DIM) :TCID 31, rx_late_packets = 02003 3 12 10:28:46 (DIM) :TCID 31, rx_early_packets = 0

->



d

t resetata00 -

B.2.64.4 tsm_stat_req_tele_levelsTCID or reqTeleLevelTCID


This query returns the current audio levels measured in the DSP for the specifiegateway channel. The parameterTCID specifies a channel on the ITG card; validvalues are in the range of 0 - 31 for Media Card, 0 - 23 for Pentium Card. Thefollowing data is displayed:• Rx power in 0.1 dBm units.• Tx power in 0.1 dBm units.• Rx mean in 0.1 linear PCM units (ignore, apparently isn’t accurate).• Tx mean in 0.1 linear PCM units (ignore, apparently isn’t accurate).

This command can be entered repeatedly during a call, the counter values are nountil a new call is made. If a call is active but there is a problem with the PCM dtransfer (see PRS MP08354), the rx_level and tx_levels will both be very large (6800) even when a DTMF digit is being pressed on the TDM set.

-> tsm_stat_req_tele_levels 0value = 0 = 0x0->JAN 17 14:44:59 tMVX_DIM: Info TCID =0 rx_level = -610JAN 17 14:44:59 tMVX_DIM: Info TCID =0 tx_level = -610JAN 17 14:44:59 tMVX_DIM: Info TCID =0 rx_mean = -40JAN 17 14:44:59 tMVX_DIM: Info TCID =0 tx_mean = -20->

For Telogy 8.1, the output is:

-> reqTeleLevel 31value = 0 = 0x0-> 2003 3 12 10:33:16 (DIM) :TCID =31 rx_level = -6102003 3 12 10:33:16 (DIM) :TCID =31 tx_level = -4402003 3 12 10:33:16 (DIM) :TCID =31 rx_mean = 02003 3 12 10:33:16 (DIM) :TCID =31 tx_mean = -302003 3 12 10:33:16 (DIM) :TCID =31 background_noise_level = 260242003 3 12 10:33:16 (DIM) :TCID =31 rx_level = -6102003 3 12 10:33:16 (DIM) :TCID =31 tx_level = -4402003 3 12 10:33:16 (DIM) :TCID =31 rx_mean = 02003 3 12 10:33:16 (DIM) :TCID =31 tx_mean = -302003 3 12 10:33:16 (DIM) :TCID =31 background_noise_level = 26024reqTeleLevel 31value = 0 = 0x0-> 2003 3 12 10:33:39 (DIM) :TCID =31 rx_level = -6102003 3 12 10:33:39 (DIM) :TCID =31 tx_level = -2502003 3 12 10:33:39 (DIM) :TCID =31 rx_mean = 02003 3 12 10:33:39 (DIM) :TCID =31 tx_mean = -4702003 3 12 10:33:39 (DIM) :TCID =31 background_noise_level = 260242003 3 12 10:33:39 (DIM) :TCID =31 rx_level = -6102003 3 12 10:33:39 (DIM) :TCID =31 tx_level = -2502003 3 12 10:33:39 (DIM) :TCID =31 rx_mean = 02003 3 12 10:33:39 (DIM) :TCID =31 tx_mean = -4702003 3 12 10:33:39 (DIM) :TCID =31 background_noise_level = 26024reqTeleLevel 31value = 0 = 0x0



therk.0,

-> 2003 3 12 10:33:43 (DIM) :TCID =31 rx_level = -6102003 3 12 10:33:43 (DIM) :TCID =31 tx_level = -3202003 3 12 10:33:43 (DIM) :TCID =31 rx_mean = 02003 3 12 10:33:43 (DIM) :TCID =31 tx_mean = 502003 3 12 10:33:43 (DIM) :TCID =31 background_noise_level = 260242003 3 12 10:33:43 (DIM) :TCID =31 rx_level = -6102003 3 12 10:33:43 (DIM) :TCID =31 tx_level = -3202003 3 12 10:33:43 (DIM) :TCID =31 rx_mean = 02003 3 12 10:33:43 (DIM) :TCID =31 tx_mean = 502003 3 12 10:33:43 (DIM) :TCID =31 background_noise_level = 26024reqTeleLevel 31value = 0 = 0x0-> 2003 3 12 10:33:46 (DIM) :TCID =31 rx_level = -6102003 3 12 10:33:46 (DIM) :TCID =31 tx_level = -2602003 3 12 10:33:46 (DIM) :TCID =31 rx_mean = 02003 3 12 10:33:46 (DIM) :TCID =31 tx_mean = -902003 3 12 10:33:46 (DIM) :TCID =31 background_noise_level = 260242003 3 12 10:33:46 (DIM) :TCID =31 rx_level = -6102003 3 12 10:33:46 (DIM) :TCID =31 tx_level = -2602003 3 12 10:33:46 (DIM) :TCID =31 rx_mean = 02003 3 12 10:33:46 (DIM) :TCID =31 tx_mean = -202003 3 12 10:33:46 (DIM) :TCID =31 background_noise_level = 26024

Note that the tx_level changed during the samples. For the sake of illustrating response during traffic, a voice sample was provided one way across the netwoThis resulted in a constant rx_level (-610) and varying tx_level (from 1440 to -25with a mean level ranging from -470 to +50.



he

ice.ge

mber

or

-run

t reseting

B.2.64.5 tsm_stat_req_vp_delayTCID or reqVpDelay TCID


This query returns the DSP's VPU (Voice Playout Unit) statistics for the call on tchannel specified. Be sure the variableTsmDspStat = 1/0(section B.2.62, pg 226) isset to 1 or nothing will be output. The VPU operates on segments of 10 msec of voThe parameterTCID specifies a channel on the ITG card; valid values are in the ranof 0-31 for the SMC, 0 - 23 for the 24 port card. The following data is printed:

• Number of lost segments during the call based on the missing sequence nu

• Number of segments replayed due to the lost packets

• Number of idle (noise) segments being played out due to either lost packetsvoice playout FIFO buffer under-run

• Number of voice segments dropped due to the voice playout FIFO buffer over

• Total number of segments submitted by packetization unit for playout.

• Average frame jitter seen from network (in Telogy 7.01 output only).

This command can be entered repeatedly during a call, the counter values are nountil a new call is made. The following is the output for an application load containTelogy 5.0:

-> tsm_stat_req_vp_delay 0value = 0 = 0x0->JAN 17 14:45:22 tMVX_DIM: Info TCID 0, avg_playout_delay = 60JAN 17 14:45:22 tMVX_DIM: Info TCID 0, lost_packet_count = 0JAN 17 14:45:22 tMVX_DIM: Info TCID 0, replay_packet_count = 0JAN 17 14:45:22 tMVX_DIM: Info TCID 0, idle_packet_count = 14JAN 17 14:45:22 tMVX_DIM: Info TCID 0, dropped_packet_count = 0JAN 17 14:45:22 tMVX_DIM: Info TCID 0, rx_packet_count = 20382->


-> tsm_stat_req_vp_delay 0value = 0 = 0x0->JAN 01 14:33:21 tMVX_DIM: Info TCID 0, avg_playout_delay = 60JAN 01 14:33:21 tMVX_DIM: Info TCID 0, lost_packet_count = 0JAN 01 14:33:21 tMVX_DIM: Info TCID 0, replay_packet_count = 0JAN 01 14:33:21 tMVX_DIM: Info TCID 0, idle_packet_count = 0JAN 01 14:33:21 tMVX_DIM: Info TCID 0, dropped_packet_count = 0JAN 01 14:33:21 tMVX_DIM: Info TCID 0, rx_packet_count = 4140JAN 01 14:33:21 tMVX_DIM: Info TCID 0, avg_frame_jitter = 0->


-> 2003 3 12 10:37:50 (DIM) :TCID 31, avg_playout_delay = 572003 3 12 10:37:50 (DIM) :TCID 31, lost_packet_count = 0



2003 3 12 10:37:50 (DIM) :TCID 31, replay_packet_count = 02003 3 12 10:37:50 (DIM) :TCID 31, idle_packet_count = 236311802003 3 12 10:37:50 (DIM) :TCID 31, dropped_packet_count = 02003 3 12 10:37:50 (DIM) :TCID 31, rx_packet_count = 98742003 3 12 10:37:50 (DIM) :TCID 31, avg_frame_jitter = 02003 3 12 10:37:50 (DIM) :TCID 31, adpt_po_buf_delay_inc= 02003 3 12 10:37:50 (DIM) :TCID 31, adpt_po_buf_delay_dec= 02003 3 12 10:37:50 (DIM) :TCID 31, po_buf_underflow_cnt = 02003 3 12 10:37:50 (DIM) :TCID 31, cell_starve_evt_cnt = 0

->



Can

B.2.65 udpstatShow


This command displays the UDP protocol statistics.

-> udpstatShowUDP: 1176800 total packets 843866 input packets 332934 output packets 0 incomplete header 0 bad data length field 0 bad checksum 436369 broadcasts received with no ports 0 full socket 218868 pcb cache lookups failed 10 pcb hash lookups failedvalue = 28 = 0x1c->

B.2.66 upgradeErase

Safety level: Destructive/Semi-Normal. Often used before downloading a newimage or provisioning to ensure a clean load. A reboot after thiscommand but before the new software is loaded or provisioningdownloaded cannot complete.

Caution: For the Media Card, this function will delete the file/C:/execso that onreboot the card will boot to the BootROM prompt.

This command erases the application binaries from the ITG card’s Flash memory.be executed from the BIOS or VxWorks prompt.

-> upgradeErasevalue = 0 = 0x0-> Erasing....Bank 1...0xf9800000, sector 0.Bank 2...0xf9900000, sector 8.Bank 3...0xf9a00000, sector 16.Bank 4...0xf9b00000, sector 24.A restart will boot from the BIOS ROMs



verytting

hter-theallows

(0)mand

B.3 Disk commands

B.3.1 reformatAdrive

Safety level: Extremely destructive recovery.

Caution: DO NOT ISSUE THIS COMMAND with the D channel card in anSMC face-plate slot.

Caution: NEVER reformat a PCMCIA card used for ITG cards on a PC.

This command basically clears the entire contents of the PCMCIA software delicard inserted in the faceplate. This is the only way to reformat this card; formaon a PC makes the card effectively scrap as far as the ITG cards is concerned.

-> reformatAdrive

B.3.2 reformatCdrive


Caution: DO NOT ISSUE THIS COMMAND unless you want to completelyclear the on-card drive.

This command basically clears the entire contents of the internal PCMCIA daugboard memory card. This is the only way to reformat this card; extracting it fromsystem can destroy it unless extreme care is taken, and because this commandthe user to reformat it on location, extraction is pointless.

-> reformatCdrive

B.3.3 SMC: formatAtaCard 0/1


Caution: DO NOT ISSUE THIS COMMAND unless you want to completelyclear the on-card drive.

This command basically clears the entire contents of the internal (1) or externalPCMCIA memory card. This is the only way to reformat this card; extracting it frothe system can destroy it unless extreme care is taken, and because this commallows the user to reformat it on location, extraction is pointless.

-> formatAtaCard 0-> formatAtaCard 1



B.4 Software download commands

When downloading software to the card, three commands and two methods areavailable.

B.4.1 Download over the IP network

The user may use theswDownloadcommand (B.1.41, page 166) to obtain the softwarefrom a remote destination, once the IP addresses are set up.

-> swDownload “xx.xx.xx.xx”,”usrId”,”passwd”,”dir-path”,”IPT30045.sa”

B.4.2 Download from the PCMCIA software delivery card

The user may use theswCopycommand (the VxWorks utility) to obtain the softwareload, but this command is not as reliable asupgradePCMCIA. TheupgradePCMCIAis the only supported IPL and IPT sa exec file download command;swCopy is aVxWorks command that “may or may not work”.

These two commands check the file format, CRC checksum and file size.

-> swCopy “/A:/IPT30053.sa”-> upgradePCMCIA “/A:/IPT30053.sa” (fix for Q00511514)



Appendix C Annex 1 - BCM 2.x - IP Trunk Interoperability

C.1 Requirements

C.1.1 BCM Requirements

Applicable Markets: MCDN Supported in all Market ProfilesHardware: Supported on all 2.0 and 2.5 hardware configurationsKeycodes: The following keycodes are required:

Note: MCDN authorization keycode is bundled with the Q.Sig keycode, which is onlysupported in international market profiles (not North America) and isn’t supportedover an IP link.

Dependencies:Software: MCDN over IP requires VoIP Trunks and BCM Release 2.5 FP1Hardware: MCDN over PRI requires a Digital Trunk MBM (DTM)

Interoperability Notes

• Supported Features:

— Uniform Dial Plan (UDP)

— Coordinated Dial Plan (CDP)

— Message Waiting Indication (MWI)

— Network Call Redirection (NCRD)

— Trunk Route Optimization (TRO)

— Trunk Anti Tromboning (TAT)

Item Description Part Numbers

BCM MCDN & Q.SIG Voice Networking Authorization Code NTKC0002 A0805827

A minimum of 2 IP trunks are required to user MCDN over IP. The following part numbers represent all thepossible keycodes to meet your customer’s needs.

Item Description Part Numbers

BCM VoIP gateway - 2 Trunks Authorization Code NTAB3116 A0792743

BCM VoIP gateway - 4 Trunks Authorization Code NTKC0060 A0843712






rise

/

rise

— Camp-on

— Break-in

— ICCL

Note:

FAX over IP is not currently supported between M1 and BCM.

C.1.2 M1 Requirements:

X11 Release 21 to Release 24.24 and Release 25.30 software or above (EnterpFeature Set)

• End-to-End Signaling (Option 10)

• Message Center (Option 46)

• IVMS Link (Option 35)

• Meridian Mail Link (Option 77, 85)

• Basic ACD features (Options 40, 45, 83)

• ISDN Primary Rate Interface or ISDN Signaling Link (Option 145/146 or 145147) and associated prerequisites

• Advanced ISDN Features (Option 148)

• Network Message Services (Option 175)

For a new Meridian 1 (Option 81C, 61C or 51C) on X11 Rel. 24, the followingsoftware packages should be ordered (in addition to the base software):

• SW0059B

• SW0052D

• SW0221C

• SW0051B

These packages will provide the required features listed above.

For a new Meridian 1 Option 11C or 11C Mini on X11 Rel. 24, either the Enterpor NAS/VNS software package should be ordered.

For Centralized Voicemail the following is required:

• M1 based Call Pilot software:Any Call Pilot configuration is supported.

• Meridian Mail software:Meridian Mail Rel. 7 (MM7) or above - currently shipping MM13.



h to

onytion

red.

• The appropriate number of PRI/ITG cards and D-channel handlers in the switcsupport the PRI/IP links to the BCMs are also needed.

C.2 BCM Configuration Tips

For more Information on BCM Configuration Tips refer to the:

• BCM IP Telephony Guide , Chapter 6 – Typical Network Applications usingMCDN

• BCM IP Telephony Guide , Appendix D – Interoperability

• BCM Programming and Operations Guide, Chapter 14 – Configuring PrivateNetworks.

C.2.1 Basic Set to Set Calling

This section is a configuration tip based on a combination of the BCM IP TelephGuide and BCM Programming and Operations Guide. For more detailed informarefer to either of those documents.

BCM programming for Basic Set to Set Calling

Ensure Keycodes are entered:

• System – Licensing – Applied Keycodes:

— Ensure Keycodes for VoIP Gateway Ports and MCDN are applied.

— Add if necessary.

— Note: If VoIP Gateway keycodes are added a reboot of the BCM is requi



ine

–

ess.

• Verify core telephony dialing plan:

Services – Telephony Services – Lines – VoIP Lines – Enabled VoIP Lines – L0XX – Trunk/line data:

— Ensure all enabled VoIP lines are in a line pool.

— This is used to group trunks together for outgoing calls.

Services – Telephony Services – System DNs – Active set DNs – DN XXXXLine access – Line pool access:

— Ensure all DNs that you want to access the VoIP trunks have line pool acc



the

t of

Services – Telephony Services – Call routing – Routes – Route XXX

— Ensure the VoIP trunks are assigned to a route for outbound calling. Verifyroute in question is using the linepool for the VoIP trunks.

— The External # field is for inserting digits before anything that is dialed.

— The DN Type field is either public/private and this sets the type of call outhe BCM.

— Note: Typically the DN Type is set to private for BCM-ITG calls.



M to maylp:

lans

ncedide

the

Services – Telephony Services – Call routing – Destination codes

Destination codes are numbers that are dialed from the intercom path of BCgain access to a route. Since these values are dialed from the intercom theynot conflict with other dialing feature prefixes in the BCM. This table should he

— Ensure the destination codes have been added. Typically for CDP dialing pthis is a 1 digit value and for UDP this is a 4 digit value.

— Under schedules use the normal mode. The other modes are for more advafall back routing. Please refer to the BCM programming and operation gufor more info.

— On the destination code in question make sure it is using the route built forVoIP trunks.

— The absorb length value will absorb X digits from your destination code ifset.Typically this is set to none. Default value is all.

Item Description Default Value

Park Prefix The Park prefix is the first digit of the call park retrieval code that you enter toretrieve a parked call.

1

External Code The External code setting allows you to assign the external line access codefor T7100 telephones and ATA 2s to access external lines.

None

Direct Dial Digit The Direct dial digit setting allows you to specify a single system-wide digit tocall a direct dial telephone.

0

Auto DN Calls answered without DISA require no password to access theBCM. This is the DN used for this scenario.

None

DISA DN For calls answered with DISA, the system presents a stuttered dial tone toprompt a caller to enter a valid password. This is the DN used for this scenario.

None

Line Pool Code A simple access code used to access the line pools from the intercom. 9 for Pool A

Other Destination Codes As stated. None

Any valid DN in the BCM Any valid B1 DN in the system or B2 DN in the system. Varies



work

gits

work

gits

Services – Telephony Services – General settings – Dialing plan – Private Net

— If a private route is used ensure the private DN length is set accordingly.Typically for CDP this is 4 and UDP 8.

— Note: The private DN length is the number of digits the BCM will look forbefore attempting to place the call. If this value is set to short some of the dimay not be sent.

Services – Telephony Services – General settings – Dialing plan – Public Net

— If a public route is used ensure the public DN length is set accordingly.Typically this is not used for set to set calls.

— Note: The public DN length is the number of digits the BCM will look forbefore attempting to place the call. If this value is set to short some of the dimay not be sent.



CM

e

sign

–

N

.

allsled

Services – Telephony Services – General settings – Access codes

— If you are using UDP dialing then ensure the private access code on the Bis set to your AC1 value corresponding on the M1.

• Verify Target Line settings for inbound calls:

Services – Telephony Services – Lines – Target lines – Line XXX – Trunk/lindata – Received number

— Ensure the public number is set to match the DN of the set you wish to asthis line to.

• Verify Target Line Assignment to DNs:

Services – Telephony Services – System DNs – Active set DNs – DN XXXXLine access – Line assignment

— Ensure the appropriate target line is assigned to the DN.

• Verify MCDN settings:

Services – Telephony Services – General settings – NetworkServices – MCD

— In order to use MCDN features ensure that TAT and/or TRO are set to Y

• Verify IP Telephony remote gateway table:

Services – IP Telephony – H.323 Trunks – Remote Gateway

— Ensure the Destination IP of the remote gateway is the T-LAN leader IPaddress of the ITG card.

— The QoS monitor should be disabled for initial call testing as it can cause cto fail. After basic set to set calling is functioning QoS monitor can be enabbut it MUST be enabled on both the ITG and BCM for it to function on theBCM.



this

ey

or

ITG.

— Ensure the Gateway type is set to ITG.

— Ensure the Gateway Protocol is set to SL1.

— The destination digits are the 1st X amount of digits sent over the IP trunkswhich are then used to direct the call to the appropriate gateway. Typicallyvalue is 1 digit for CDP and 4 digits for UDP.

— The destination digits are NOT stripped off or added to the dialed digits. Thare just for filtering.

— Note: The destination digits field is a space delimited field which allows fmultiple entries.

• Verify IP Telephony codec preferences:

Services – IP Telephony – H.323 Trunks – Media Parameters

— Verify the codec preferences on the BCM match what is being used on the

— Note: By default the BCM uses G.729 for all outgoing VoIP trunks.



neral

n

s the

erly

n

–

self.

–

the

M1 Programming for Basic Set to Set Calling

For more detailed programming information on CDP/UDP dialing see thecorresponding sections below or refer to the appropriate NTP’s. Here are some geprogramming hints:

— ITG payload sizes should be set to 30 ms.

— Voice Activity Detection (VAD) should be configured to the same value oboth BCM and ITG (i.e. both on or both off).

— The profile on the ITG must be set to have the same first preferred codec aBCM’s

C.2.2 Calling Line ID

BCM programming for Calling Line ID

BCM must have a few parameters configured to ensure Calling Line ID is sent propto the M1.

Services – Telephony Services – General settings:

— Ensure the business name is configured. In order to format the CLID in aeasier to read format place a space after the business name.

Services – Telephony Services – System DNs – Active set DNs – DN XXXXGeneral

— Ensure the Name is configured for the DN. The default value is the DN it

Services – Telephony Services – System DNs – Active set DNs – DN XXXXLine access

— Ensure the OLI number is configured for each DN. This value is phonenumber that will be sent out as your CLID when calling into the network.Typically this is either your DID number or the main business telephonenumber.

The BCM will then send the CLID as “Business name|DN Name” as the name andOLI number as the number.

M1 Programming for Calling Line ID

For more detailed programming information on Calling Line ID see theappropriate NTP’s.



M to

r

em

ine

es –

PSTN

C.2.3 Tandem Calling

BCM programming for Tandem Calls

• Verify programming of BCM Dialing Plan:

— Ensure basic set to set calling works and calls can be made from the BCthe PSTN using the number desired to tandem.

— Ensure Destination Codes are built for any dialed number combination fotandem calls.

— Ensure public/private DN lengths are of sufficient length to handle the tandcalls.

• Verify programming of Remote Access Packages on Lines:

Services – Telephony Services – Lines – VoIP lines – Enabled VoIP lines – L0XX - General

— Verify all VoIP lines have a remote package assigned to them.


• Verify programming of Remote Access Packages:

Services – Telephony Services – General settings – Remote access packagPackage XX

— Ensure the remote access package has line pool access to the outgoingtrunks desired to be used in the tandem call.



ave

al/

on

gth


M1 Programming for Tandem Calls

For more detailed programming information on tandem calls see the appropriateNTP’s. Here are some general programming hints

• For tandem calls from the M1 to the BCM and out to the PSTN the M1 must hthe call configured for a Called Party Number TON/NPI value of Unknown/Private. The BCM cannot tandem a Called Party Number TON/NPI of NationE.164.

• Note: For calls from the BCM to the M1 and then out to the PSTN this restrictidoesn’t apply.

C.2.4 Private Network Identifier (PNI) -

BCM requires PNI numbers to be in the range of 1-128 for the whole network.

C.2.5 Uniform Dial Plan

BCM programming for UDP

• General Setting – Dialing Plan – Private Network:

— Set type to UDP

— Location Code : set to an appropriate 3 digit prefix

• Private DN length:

— Set to at least the total of Private Access Code + Location Code + DN Len( if the dialing string is 6 393 2222. This Private DN Length is 8. )

• Private Access Code:



priate

ed.

— General Settings – Access Code – Private Access Code. set to an approcode. This value corresponds to the AC1 value in the M1.

— General Settings – Access Code – Destination Code.

— Services – Call Routing – Destination Codes, build destination code thatmatches the Private Access Code with absorb length of 0.

M1 Programming for UDP

• Private Access Code

— Overlay 86, LD 86

o REQ : PRTo CUST : <as applicable>o FEAT : ESNo Make note of the AC1 code

• To change Private Access Code


o REQ : CHGo CUST : <as applicable>o FEAT : ESN, keep pressing enter until you reach the AC1 prompto At the AC1 prompt make your choice

• To check UDP Programming


o REQ : PRTo CUST : <as applicable>o FEAT : NETo TYPE : LOCo LOC : press enter, this will list all the location codes that are programmo HLOC is the home location of the M1 itself.

• To program new UDP values to route


o REQ : CHGo CUST : <as applicable>o FEAT : NETo TYPE : AC1o LOC : (enter a number)o RLI : ( enter the RLI corresponding to the route)



-1

ering

C.2.6 Coordinated Dial Plan

BCM programming for CDP

General Setting – Dialing Plan – Private Network

• Set type to CDP

• Set Private DN Length to the BCM DN Length

• Set PNI to the number assigned from the M1

• Note: This is the number defined in LD 16 - RDB – PNI in M1 programmingResources - Media Bay Modules - Bus XX – Cdx – KSU: PRI – Protocol: SL

• Set PrivNetId to the PNI of the switch on the other end

Note: This is the number defined in LD 15 – Net – PNI in M1 programming.Set Destination Code (Services – Routing – Des Code) to the corresponding SteCodes of the Neighboring nodes.

M1 Programming for CDP

• Distant Steering Codes


o REQ : PRTo CUST : <as applicable>o FEAT : CDPo TYPE : DSC (Distant Steering Code)o DSC : press enter, this will list all the DSC programmed

• To check RLI (Route Line Index)


o REQ : PRTo CUST : <as applicable>o FEAT : RLBo RLI : (press enter) this will display all the RLI’s

• To program new CDP value to route


o REQ : CHGo CUST : <as applicable>o FEAT : CDPo TYPE : DSPo DSC : (enter number) if this is for a BCM with DNs 44xx enter 44



t line

o FLEN : ( enter BCM DN length)o RLI : (enter the RLI that corresponds to the route)

C.2.7 Message Waiting Indicator (MWI)

BCM programming for MWI

• Telco Features – VMsg Ctr Tel Numbers – Voice Message Center 1

— Set to DES Code + M1 voice mail DN

• Lines – Telco Features

— Set to Voice Message Center 1

— Terminals and Sets- Show Set – Telco Features – Feature Assign for targeappearing on each

— Set External VMsg to Y

M1 Programming for MWI

• RCAP should be set to MWI and ND2

• RLS ID should be set to 36

C.2.8 Network Call Redirection (NCRD)

BCM programming for NCRD

No programming required

M1 Programming for NCRD

• Programming Parameters (D channel must be disabled)

— LD 17

o NASA set to yeso NCRD set to yes

• Verifying NASA is Active


o REQ : PRTo TYPE : ADAN DCH (slot number)o NASA should be set to yes

If NASA is not on:

• disable the D channel




z"

ne

o Assume D channel is "12"; it may be any provisioend numbero STAT DCH

displays the status of all provisioned D channels.o DIS DCH 12

disables the D channel

• Disable the card to avoid receiving extraneous input


o STAT x y zDisplays the status of loop x, shelf y, card z (for Option 11, use "STATonly)

o DIS x y z

• Program the D channel


o REQ : CHGo TYPE : ADANo ADAN : CHG DCH xo Keep pressing enter until you get to NASAo NASA yeso Keep pressing enter until you get to REQ

• Verifying NCRD

— Find the correct route for this D channel and card.Overlay 20, LD 20

o REQ : PRTo TYPE : TIEo CUST : <as applicable>o TN (slot number) [space] 1o Keep pressing enter until your TIE block is displayed, and look for the li

where RTMB (RouTe and MemBer) is displayed. This will be in the form(route number) [space] (member number)


o REQ : PRTo TYPE : RDBo CUST : <as applicable>o Route : Enter the route defined in LD 20o Keep pressing enter until all values are displayed.o Check if NCRD is yes.

• If NCRD is set to no




o REQ : CHGo TYPE : RDBo CUST : <as applicable>o ROUT : (route number) from LD 20o Keep pressing enter until you get NCRD and type Yeso Keep pressing enter until you get the REQ prompt againo REQ : end

C.2.9 Trunk Route Optimization (TRO)

BCM programming for TRO

General Settings – Network Services – MCDN

• Set TRO to yes.

M1 Programming for TRO

On M1 TRO should be set to yes for the BCM route.

• LD 16

— TYPE : RDB

— CUST : <as applicable>

— ROUT : 0-511

— Keep pressing enter until you get TRO

— TRO : Yes

— Keep pressing enter until you get the REQ prompt again

C.2.10 Trunk Anti Tromboning (TAT)

BCM programming for TAT

General Settings – Network Services – MCDN

• Set TAT to yes.

M1 Programming for TAT

On M1 TAT needs to be set on each D-Channel and on the routes.

• Overlay 17, LD 17

— REQ : CHG



— TYPE : ADAN

— ADAN : CHG DCH (slot number)

— Keep pressing enter until you get to RCAP

— RCAP TAT


— REQ end

• Overlay 16, LD 16 (if tou want the tromboning enhancement)

— REQ : CHG

— TYPE : RDB

— CUST : <as applicable>

— ROUT : (route number) from LD 20

— Keep pressing enter until you get TRMB

— TRMB Yes


— REQ end



Last Page of The Document





7

Index of commandsA

arpFlush ................................................................................................................................. 171arpShow ................................................................................................................................ 171attrib ...................................................................................................................................... 172auditRebootSet ...................................................................................................................... 120auditRebootTimeSet .............................................................................................................. 120auditShow .............................................................................................................................. 121auditTaskSet .......................................................................................................................... 121

CcardReset ............................................................................................................................... 122cd ........................................................................................................................................... 122chkdsk ................................................................................................................................... 173clearLeader ............................................................................................................................ 122copy ....................................................................................................................................... 123

DdchipResTableShow ..............................................................................................................124DCHmenu ............................................................................................................................. 126devs ....................................................................................................................................... 174DimECStat ............................................................................................................................ 175dimPrintChannelInfo ............................................................................................................. 176dosFsConfigShow ................................................................................................................. 134dspFatalErrorCountClear ...................................................................................................... 18dummy_trap .......................................................................................................................... 178

Eexit ......................................................................................................................................... 178

FfirmwareVersionShow .......................................................................................................... 135flashConfigShow ................................................................................................................... 179formatAtaCard ...................................................................................................................... 241

GgkShow .................................................................................................................................. 135

Hh ............................................................................................................................................. 180h323CallTrace ....................................................................................................................... 140h323SessionShow ................................................................................................................. 143



8

80

9191

Ii .............................................................................................................................................. 145icmpstatShow ........................................................................................................................ 181ifShow ................................................................................................................................... 146igccAddTrace ........................................................................................................................ 182igccNoTrace .......................................................................................................................... 182inetstatShow .......................................................................................................................... 182iosFdShow ............................................................................................................................. 184IPInfoShow ............................................................................................................................ 148ipstatShow ............................................................................................................................. 185iptSessionShow ..................................................................................................................... 150itgCardShow .......................................................................................................................... 152itgChanStateShow ................................................................................................................. 155itgExcpCountClear ................................................................................................................ 185itgExcpCountShow ................................................................................................................ 185itgMemShow ......................................................................................................................... 156itgMsgCtrShow ..................................................................................................................... 157itgShell .................................................................................................................................. 186

LldrResTableShow .................................................................................................................. 158lkup ........................................................................................................................................ 186ll ............................................................................................................................................. 159lnIsaBroadcastShow .............................................................................................................. 187lnIsaBroadcastThreshold ....................................................................................................... 187lnIsaShowLostBroadcast ....................................................................................................... 18lnPciBcastFilterOff ................................................................................................................ 188lnPciBcastFilterOn ................................................................................................................ 188lnPciBroadcastShow .............................................................................................................. 189lnPciBroadcastThreshold ...................................................................................................... 19lnPciShowLostBroadcast ...................................................................................................... 19ls ............................................................................................................................................ 190

Mmac21440BroadcastShow ..................................................................................................... 1mac21440BroadcastThreshold .............................................................................................. 1mbufShow ............................................................................................................................. 192mixLevelOn ........................................................................................................................... 193mixMemFindAll .................................................................................................................... 193mixOptionOn ......................................................................................................................... 195mixSetLogOpt ....................................................................................................................... 195mkdir ..................................................................................................................................... 197monIPDebugSet .................................................................................................................... 198monUtility ............................................................................................................................. 199

IP Trunk 3.0 Expert Level Support Guide Issue 1.5.4Page 264 05 May 03


30

1

mRouteAdd ........................................................................................................................... 202mRouteDelete ........................................................................................................................ 202mRouteShow ......................................................................................................................... 202

NnetHelp .................................................................................................................................. 203nmmAtpmTranTblDnld ........................................................................................................ 20numNodesInFallbackShow ................................................................................................... 16NVRClear .............................................................................................................................. 160NVRGWSet .......................................................................................................................... 161NVRIPSet .............................................................................................................................. 162NVRIPShow .......................................................................................................................... 162NVRSMSet ........................................................................................................................... 162

Pping ........................................................................................................................................ 163pins - patch in service ............................................................................................................ 204plis - patch list ....................................................................................................................... 205pload - patch load .................................................................................................................. 207PMSI, seeProperty Management System Interfacepoos - patch out of service ....................................................................................................207pout - patch out, or unload ....................................................................................................208print_cdp ............................................................................................................................... 214print_dsc ................................................................................................................................ 215print_ip_table ........................................................................................................................ 210print_loc ................................................................................................................................ 214print_npa ............................................................................................................................... 212print_nxx ............................................................................................................................... 213print_spn ................................................................................................................................ 213print_tsc ................................................................................................................................. 215pstat - patch status ................................................................................................................. 209pwd ........................................................................................................................................ 163

RreformatAdrive - VxWorks shell .......................................................................................... 241reformatCdrive - VxWorks shell ........................................................................................... 24reqECDbg .............................................................................................................................. 229reqError ................................................................................................................................. 232reqTeleLevel ......................................................................................................................... 236reqVpDelay ........................................................................................................................... 238resetOM ................................................................................................................................. 163rm .......................................................................................................................................... 216rmdir ...................................................................................................................................... 217routeAdd ................................................................................................................................ 164



22

routeDelete ............................................................................................................................ 164routeShow .............................................................................................................................. 164rtpPortCompress .................................................................................................................... 218rtpPortNonCompress .............................................................................................................218

SserialNumShow ..................................................................................................................... 165set_time ................................................................................................................................. 219setLeader - login window ...................................................................................................... 165setTraceOption ...................................................................................................................... 220shellPasswordNvramClear .................................................................................................... 2shellPasswordSet ................................................................................................................... 165shellTimeoutGet .................................................................................................................... 222shellTimeoutSet ..................................................................................................................... 222showMemConfig ................................................................................................................... 222swDownload .......................................................................................................................... 166swVersionShow ..................................................................................................................... 166

TtcpstatShow ........................................................................................................................... 223tlanDuplexSet ........................................................................................................................ 224tlanSpeedSet .......................................................................................................................... 225tsm_stat_req_ecdbg ............................................................................................................... 229tsm_stat_req_error ................................................................................................................. 232tsm_stat_req_rx_tx ................................................................................................................ 234tsm_stat_req_tele_levels .......................................................................................................236tsm_stat_req_vp_delay ..........................................................................................................238tsmChanShow ........................................................................................................................ 167TsmDspStat ........................................................................................................................... 226tsmSetTraceOption ................................................................................................................ 227

UudpstatShow .......................................................................................................................... 240upgradeErase ......................................................................................................................... 240useIPTForRingBack ..............................................................................................................169useM1ForRingBack .............................................................................................................. 169

VvxWorksShell ........................................................................................................................ 170

IP Trunk 3.0 Expert Level Support Guide Issue 1.5.4Page 266 05 May 03

Ipt3 Expert Level Support Guide

Documents

nortel networks

2003nortel

irq intc steered

2003nortel

texctask tnettask

nortel networks

a6fbh sram

pccard recognized