Ipt3 Expert Level Support Guide

Expert Info
IP Trunk 3.0 Expert Level Support Guide

Author: Pat Hession Mark Whitney Shuang Chen L Patrick Findlay Dave OConnell Monica Patel Gwen Clarke 05 May 03 Issue 1.5.4 Meridian 1 X11 IP Trunk 3.0 ITG IP Trunk 3.0 Global ITG, ITG-P, SMC, Trunk, IPT 3.0, IP Trunk 3.0, VoIP, Troubleshoot Troubleshooting the IP Trunk feature requires insight into IP and traditional M1 telephony. This document describes tools and techniques that can help. Dept. 8047 Dept. 8047 Dept. 9P84 Dept. 9T42 Dept. 8047 Dept. 9P84 Dept. 9T42 GAL GAL BVW BVW GAL BVW BVW
Manager:
Date: Issue: System: Release: Project Name: Sub-Feature: Target Market: Activity Id: Keywords: Abstract:
Warning: users debugging ITGT 2.x.26G and lower should use the ITGT Expert Guide version 1.4 or lower. The commands from that vintage that still apply to IP Trunk 3.0 are included in this document, but many extra commands 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 authorized in writing by Nortel Networks, the holder of this document shall: (1) keep all information contained herein confidential 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 Condential
Issue 1.5.4 05 May 03
IP Trunk 3.0 Expert Level Support Guide Page 2
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.1 1.2 1.3 1.4 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resolving IP Trunk problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Use of a Network Sniffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IP Trunk and VxWorks shell access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4.1 Connecting to the cards RS232 Maintenance port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4.1.1 Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4.1.2 Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4.2 VxWorks shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modules key to call related problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modules key to QoS related problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modules key to Leader / Follower communication problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modules key to T-LAN / E-LAN and inter-task messaging problem . . . . . . . . . . . . . . . . . . . . . . . . . . Modules key to OTM to card communication and conguration problems . . . . . . . . . . . . . . . . . . . . . Modules key to DCH problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modules key to SSD / A07 related problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modules key to DSP related problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using a Network Sniffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.1 Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.2 Sniffer Pro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General card commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disk and Directory Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.1 General troubleshooting suggestions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.2 RMD errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.3 QoS Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.4 BandWidth Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.5 Network Interface - Speed and Mode Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.6 Broadcast storms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.7 Port numbers used by the IP Trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.7.1 TCP Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.7.2 UDP Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.8 SNMP traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Related Problem Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.1 Channel selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.2 Gatekeeper problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audio Quality Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Address Translation Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-Channel Related Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8.1 DCHmenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup Leader start-up issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 14 14 15 16 16 16 17 19 20 21 22 22 23 24 25 25 27 27 27 29 30 31 33 35 36 37 37 38 39 39 40 40 40 41 42 42 43 44 44 44
IP Trunk 3.0 module descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.1
3.2 3.3 3.4
3.5
3.6 3.7 3.8 3.9
Potentail provisioning problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

4.1 4.2 4.3 Creating trunks for ESN5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Problems with downloading provisioning - ContactSet error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Echo cancellation tail delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Issue 1.5.4 05 May 03
Section: Table of Contents Page 3
Debugging the shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

5.1 5.2 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Password operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2.1 Recovering from a corrupted password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2.2 Password modication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General card commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.1 Hardware and software queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.2 Memory and tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.3 Operational data and timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disk and directory commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.1 Navigating the le system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.2 Verifying and sanitizing the le system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.3 Download/upload of les . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General card commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conguration and startup le checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.1 Verify provisioning on the card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.2 Corrupted leader data, but ELAN IP address is correct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.3 ELAN information corrupted but provisioning valid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.4 ELAN and conguration information corrupted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote node status checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Memory fault diagnostic commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Node commissioning commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disk and directory debugging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identifying the issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message tracing commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.1 Eliminate the PBX or Call Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.2 Ensure that the originating side card accepted the call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.3 Ensure that the call traversed the network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.4 Ensure gatekeeper ARQ succeeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.5 Ensure that the call left the destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Echo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.1 Provisioning advisory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.2 The echo checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Debugging, other problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing the /C: drive le system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing NVRAM contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BootROM compatibility levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BIOS / BootROM Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 49 49 50 50 50 51 51 51 51 52 53 54 54 54 54 55 56 56 58 58 59 60 61 61 61 62 64 64 65 67 67 67 72 75 79 80 80 81
5.3
5.4
Debugging the node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

6.1 6.2 6.3
6.4 6.5 6.6 6.7
Call processing debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

7.1 7.2
Debugging audio issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

8.1
8.2
BIOS / BootROM functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

9.1 9.2 9.3 9.4 9.5
10
Maintenance Task (Task Monitor Function) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

10.1 audit.ini le . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 10.2 audit.his history le . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Issue 1.5.4 05 May 03
Nortel Networks Condential 10.3 CLI commands for Audit/Maintenance task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
11 12
Patcher Tool Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

11.1 On Switch Patch Tool CLI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Installation and upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

12.1 Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.1 FTP server and le transfer options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.2 Setting NVRAM parameters from the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.3 Setting NVRAM parameters from the BIOS / BootROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.3.1 IPT-P, SMC with BIOS version 5.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.3.2 SMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2 Software Upgrade Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.1 Software upgrades from the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2 Software upgrades from the ROM BIOS v1.2 CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.3 Software upgrades from the BootROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.4 FTP upgrade on SMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.5 SMC BIOS Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.3 Transmit Node and Card Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 87 88 88 88 88 89 90 90 91 91 92 92
13 14 15
VxWorks Startup Script Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Exception Trace Decoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Formatting the /C: Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
15.1 15.2 15.3 15.4 15.5 15.6 Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Symptoms of /C: Drive Corruption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Out of File Descriptors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using chkdsk to Identify Corruption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Formatting the /C: Drive on Pentium platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recovering the /C: Drive on Media Card platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 96 96 97 98 99
16
Card Startup Log Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

16.1 Pentium captures - Leader bootup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 16.2 Pentium captures - Follower bootup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 16.3 Succession Media Card captures - Leader bootup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Appendix A Configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

A.1 A.2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CONFIG1.INI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.2.1 Downloading / parsing from TTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.2.1.1 configFileGet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.2.2 Example file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DPTABLE.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.3.1 Downloading / parsing from TTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.3.1.1 nmmAtpmTranTblDnld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.3.2 Example file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BOOTP.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.4.1 Example file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 111 112 112 112 114 114 114 114 117 117
A.3
A.4
Appendix B IP Trunk Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

B.1 Commands accessible from the ITG> or -> prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 B.1.1 auditRebootSet 0/1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Issue 1.5.4 05 May 03
Nortel Networks Condential B.1.2 auditRebootTimeSet hh:mm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 B.1.3 auditShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 B.1.4 auditTaskSet [tname|tid],level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 B.1.5 cardReset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 B.1.6 cd dirPath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 B.1.7 clearLeader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 B.1.8 copy sourceFilename, destFilename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 B.1.9 dchipResTableShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 B.1.10 DCHmenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 B.1.11 dosFsConfigShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 B.1.12 firmwareVersionShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 B.1.13 gkShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 B.1.14 h323CallTrace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 B.1.15 h323SessionShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 B.1.16 i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 B.1.17 ifShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 B.1.18 IPInfoShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 B.1.19 iptSessionShow [level] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 B.1.20 itgCardShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 B.1.21 itgChanStateShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 B.1.22 itgMemShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 B.1.23 itgMsgCtrShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 B.1.24 ldrResTableShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 B.1.25 ll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 B.1.26 numNodesInFallbackShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 B.1.27 NVRClear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 B.1.28 NVRGWSet gwIPaddr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 B.1.29 NVRIPSet IPaddr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 B.1.30 NVRIPShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 B.1.31 NVRSMSet subnetMask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 B.1.32 ping IPaddr, numPings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 B.1.33 pwd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 B.1.34 resetOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 B.1.35 routeAdd destIPaddr, gwIPaddr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 B.1.36 routeDelete destIPaddr, gwIPaddr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 B.1.37 routeShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 B.1.38 serialNumShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 B.1.39 setLeader IPaddr,gwIPaddr,subnetMask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 B.1.40 shellPasswordSet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 B.1.41 swDownload srvrIP, uid, passwd, path, fname . . . . . . . . . . . . . . . . . . . . . . . . . . 166 B.1.42 swVersionShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 B.1.43 tsmChanShow [level[,channel]] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 B.1.44 useIPTForRingBack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 B.1.45 useM1ForRingBack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 B.1.46 vxWorksShell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Commands only accessible from the -> prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 B.2.1 arpFlush . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 B.2.2 arpShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 B.2.3 attrib filename,protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 B.2.4 chkdsk dev, repairLevel, entryLevelType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 B.2.5 devs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
B.2
Issue 1.5.4 05 May 03
Nortel Networks Condential B.2.6 B.2.7 B.2.8 B.2.9 B.2.10 B.2.11 B.2.12 B.2.13 B.2.14 DimECStat = 1/0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . dimPrintChannelInfo TCID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . dspFatalErrorCountClear dspnum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . dummy_trap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . flashConfigShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . h and command history handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . icmpstatShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . igccAddTrace, igccNoTrace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.14.1 igccAddTrace channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.14.2 igccNoTrace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.15 inetstatShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.16 iosFdShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.17 ipstatShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.18 itgExcpCountClear - Pentium card only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.19 itgExcpCountShow - Pentium card only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.20 itgShell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.21 lkup string . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.22 lnIsaBroadcastShow - not applicable, SMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.23 lnIsaBroadcastThreshold = threshold - not applicable, SMC . . . . . . . . . . . . . . . . . . . . . . . . B.2.24 lnIsaShowLostBroadcast = 1/0 - not applicable, SMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.25 lnPciBcastFilterOff - not applicable, SMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.26 lnPciBcastFilterOn - not applicable, SMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.27 lnPciBroadcastShow - not applicable, SMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.28 lnPciBroadcastThreshold = threshold - not applicable, SMC . . . . . . . . . . . . . . . . . . . . . . . B.2.29 lnPciShowLostBroadcast = 1/0 - not applicable, SMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.30 ls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.31 mac21440BroadcastShow - only applicable for SMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.32 mac21440BroadcastThreshold = threshold - only applicable for SMC . . . . . . . . . . . . . . . . B.2.33 mbufShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.34 mixLevelOn module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.35 mixMemFindAll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.36 mixOptionOn module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.37 mixSetLogOpt module, option, level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.38 mkdir dirName . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.39 monIPDebugSet IP.ad.dr.ess, on_off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.40 monUtility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.41 mRouteAdd destIPaddr, gwIPaddr, 0xdestNetMask, To, 0 . . . . . . . . . . . . . . . . . . . . . B.2.42 mRouteDelete destIPaddr, 0xdestNetMask, ToS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.43 mRouteShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.44 netHelp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.45 nmmAtpmTranTblDnld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.46 Patch commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.46.1 pins patchNumber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.46.2 plis, or plis patchNumber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.46.3 pload, or pload patchName . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.46.4 poos patchNumber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.46.5 pout, or pout patchNumber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.46.6 pstat, or pstat patchNumber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.47 print_ip_table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.2.48 Printing dial plan data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 176 178 178 178 179 180 181 182 182 182 182 184 185 185 185 186 186 187 187 188 188 188 189 189 190 190 191 191 192 193 193 195 195 197 198 199 202 202 202 203 203 203 204 205 207 207 208 209 210 211
Issue 1.5.4 05 May 03
Nortel Networks Condential B.2.48.1 Caveat - serious danger from provisioning errors within the DPTABLE.1 . . . . . . 212 B.2.48.2 print_npa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 B.2.48.3 print_nxx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 B.2.48.4 print_spn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 B.2.48.5 print_loc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 B.2.48.6 print_cdp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 B.2.48.7 print_dsc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 B.2.48.8 print_tsc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 B.2.49 rm filename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 B.2.50 rmdir dirName . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 B.2.51 rtpPortCompress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 B.2.52 rtpPortNonCompress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 B.2.53 set_time yy, mm, dd, hh, mm, ss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 B.2.54 setTraceOption channel,outputLocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 B.2.55 shellPasswordNvramClear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 B.2.56 shellTimeoutGet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 B.2.57 shellTimeoutSet timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 B.2.58 showMemConfig - Pentium only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 B.2.59 tcpstatShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 B.2.60 tlanDuplexSet duplexMode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 B.2.61 tlanSpeedSet speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 B.2.62 TsmDspStat = 1/0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 B.2.63 tsmSetTraceOption TCID,[0 or !0] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 B.2.64 tsm_stat_req commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 B.2.64.1 tsm_stat_req_ecdbg TCID or reqECDbg TCID . . . . . . . . . . . . . . . . . . . . . . . . . . 229 B.2.64.2 tsm_stat_req_error TCID or reqError TCID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 B.2.64.3 tsm_stat_req_rx_tx TCID or reqRxTx TCID . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 B.2.64.4 tsm_stat_req_tele_levels TCID or reqTeleLevel TCID . . . . . . . . . . . . . . . . . . . . 236 B.2.64.5 tsm_stat_req_vp_delay TCID or reqVpDelay TCID . . . . . . . . . . . . . . . . . . . . . . 238 B.2.65 udpstatShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 B.2.66 upgradeErase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Disk commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 B.3.1 reformatAdrive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 B.3.2 reformatCdrive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 B.3.3 SMC: formatAtaCard 0/1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 Software download commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 B.4.1 Download over the IP network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 B.4.2 Download from the PCMCIA software delivery card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 C.1.1 BCM Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 C.1.2 M1 Requirements: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 BCM Conguration Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 C.2.1 Basic Set to Set Calling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 C.2.2 Calling Line ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 C.2.3 Tandem Calling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 C.2.4 Private Network Identifier (PNI) - . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 C.2.5 Uniform Dial Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 C.2.6 Coordinated Dial Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 C.2.7 Message Waiting Indicator (MWI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
B.3
B.4
Appendix C Annex 1 - BCM 2.x - IP Trunk Interoperability . . . . . . . . . . . . . . . . . . . . . . 243

C.1
C.2
Issue 1.5.4 05 May 03
Nortel Networks Condential C.2.8 Network Call Redirection (NCRD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 C.2.9 Trunk Route Optimization (TRO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 C.2.10 Trunk Anti Tromboning (TAT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Index of commands .................................................................................................................. 263
Issue 1.5.4 05 May 03
Issue 1.5.4 05 May 03
Abbreviations
APB API ARP BIOS BOOTP Codec CPU DN DSP EC ELAN EXUT FTP IP IPT ISDN ITG ITG-P LAN MAT MCDN OM OS OTM PC Card PCMCIA QoS RTC RTP RTCP Audio Parameters Bank Application Process Interface Address Resolution Protocol Basic Input/Output System. A set of permanently stored program routines. BOOTstrap Protocol COder DECoder. A DSP function that converts the PCM stream to packets and back. Central Processing Unit Directory Number Digital Signal Processor Echo Canceller Embedded LAN (10 BaseT LAN connection for internal signalling) Enhanced Extended Universal Trunk File Transfer Protocol Internet Protocol IP Trunk (basically, IP Trunk 3.0 as displayed on the login screen) Integrated Services Digital Networking Meridian Integrated IP Telephony Gateway Meridian Integrated IP Telephony Gateway 24 port card Local Area Network Meridian Administration Terminal - Window application for conguring the Meridian-1 PBX and the ITGL application. Meridian Customer Dened Networking Operational Measurement Operating System Optivity Telephony Manager - replacement for MAT. Current name used for PCMCIA style cards. Personal Computer Memory Card International Association. This organization has dened a credit card sized plug in board for use in PCs. Quality of Service Real Time Clock Real Time Protocol. A layer above UDP for synchronization of voice packets. Real Time Control Protocol. Used to exchange end point statistics about a voice packet stream.
Issue 1.5.4 05 May 03
Section: Page 11
S/W SMC SNMP SNTP TCID TCP TFFS TFTP TLAN ToS TPS UDP VoIP WAN XUT
- Software - Succession Media Card - 32 port ITG card - Simple Network Management Protocol. Used to raise alarms and communicate OA&M between MAT/OTM and the ITG card. - Simple Network Time Protocol. Used to synchronize time between cards. - Telephony Channel IDentier - Transmission Control Protocol - True Flash File System - Trivial File Transfer Protocol - Telephony LAN (10/100 BaseT LAN connection for ITGs RTP packets) - Type of Service - Terminal Proxy Server - User Datagram Protocol - Voice over IP - Wide Area Network - Universal Trunk Card (Analog Trunk)
Section: Page 12
Issue 1.5.4 05 May 03
Introduction
1
1.1
Introduction
General
Warning: If the reader wishes to debug ITGT 2.x.24, 2.x.25, 2.x.26G or other preIP Trunk 3.0 releases, the reader should refer to the Expert Guide applicable to that release. This guide contains information that is completely not applicable to the earlier software versions. Warning: Misuse of the commands in this reference document may make the card unusable. Personnel that have not been trained in the use of the CLI can access commands via this reference that render the ITG-Pentium (ITG-P) card or Succession Media Card (SMC, or MC) unable to place calls, or even unable to reboot successfully. This document contains commands and techniques that can be used when troubleshooting problems with the IP Trunk 3.0 application on the ITG-Pentium and Succession Media Card platforms. IP Trunk 3.0 is the next generation following Internet Telephony Gateway Trunk (ITGT) Release 25 and 26 applications, resident on the ITG 2.0 (Pentium) and 2.1 (Media Card). The information provided here is intended for an audience made up of Nortel Networks eld support staff, distributors, and on-site technicians who are already familiar with the information provided in the relevant NTPs. The intent of this document is to go to the next level and provide additional information for those already comfortable 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 input; the SMC or ITG-P card may become inoperable (requiring a reboot to recover) or even reboot on its own. Care is recommended when using these commands on a live card. All commands in the appendices are listed with a level of safety. This indicates whether a command is use whenever you want, use in off hours, or use with extreme caution. Command syntax and examples are deferred to the appendices. Since a user usually needs to know the answer to the question What command should I use?, it made more sense to describe scenarios where a command could be useful and defer the details to the appendices, rather than providing a list of commands and variables without enough of an idea of when to use them.
Issue 1.5.4 05 May 03
Section: 1 Page 13
Introduction
Each section describing a command typically contains a description of the command syntax, an example of the information printed (as appropriate) and tips on using the command and interpreting the results. If a command will work from the base login prompt (the IP Trunk shell), the example shows the command entered at the ITG> or IPT> prompt; otherwise the command is only accessible from the VxWorks shell (->). Once at the VxWorks shell, all commands (including the IP Trunk shells commands) are available. Note that a general convention is used in this document. Whenever referring to the software application the expression IP Trunks or a short form is used, with the short forms including IPT 3.0" or IPT. IPT is the norm in the login windows, so it will be included when applicable in this document as well, to minimize confusion. However, at times the text refers to the hardware, the Internet Telephony Gateway card (Pentium or Media Card). As this card can be used for more applications than IP Trunk, whenever the card itself is discussed the short form may be ITG. (For example, log in to the ITG-P card could apply to any application residing on the 24 port card; if the intent is to use a base level command used by other applications as well, 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. On the other 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 message printed. Check Alarms in CURRLOG.1/PREVLOG.1 les or at the OTM console. Check the SMC/ITG-P telnet or Maintenance port session display and the Meridian 1 TTY for any error messages being printed. Retrieve the CURRLOG.1/PREVLOG.1 les from the card and scan for error and/ or 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 packets are being sent and received by the SMC or ITG-P card on the TLAN and ELAN interfaces. Support staff (including Nortel employees) supporting the IP Trunk product on site should have access to a sniffer and be versed on its use.
Section: 1.2 Page 14
Issue 1.5.4 05 May 03
Introduction
Stand-alone sniffers exist but the most cost effective are those that are just a PC application. These applications monitor the subnet the PC is connected to and display information about the network trafc. They usually include the capability of monitoring only specic port numbers or protocols and displaying and decoding most of 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 paying the full price to purchase it. Go to http://www.zdnet.com/downloads/ and search for LANExplorer. The free software program ethereal may be used (and is the sniffer of choice in the ITGT/IP Trunk design community). Go to http://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 problems or IP Trunk to OTM problems. Connect the sniffer to the TLAN to debug IP Trunk to other supported gateway Call Set-Up problems. Note that the list of supported gateways includes IP Trunk nodes, ITGT nodes (ITG Trunk 2.x.25 and 2.x.26), BCM, and 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 session instead of direct serial port connection if you are logging large amounts of data or copying large SYSLOG or OMREPORT les to the console. Using the serial port can result in call loss or worse during periods where the node experiences high trafc levels. The following access sequence controls logging in to the IPT shell access in general, and specically apply to the IP Trunk application. That is, the majority of the login sequences (and many commands) are generic to SMC and ITG-P supported applications; however, within this document only IP Trunk application commands are considered. To log in to the IP Trunk shell on the card, the user rst connects to the card via an ELAN telnet session (telnet to the management IP address) or connects to the serial debug port. The ELAN has peak speeds in the multi-megabit per second range, but the port has a 9600 bit per second range, and chews card real-time, so use telnet whenever possible.
Issue 1.5.4 05 May 03
Introduction
Login to ITG> prompt1 Having connected to the application (telnet or faceplate), the card requests a login. The normal administrative login is via a standard username and password (which is not included here for system security reasons). This gives the user access to the card level and the IP Trunk application. The user can identify this by the ITG> prompt. Note that the user can change the passwords using commands within this document.
Login to -> prompt While some of the commands in the remaining sections of this document are accepted at the ITG> shell prompt, all are accepted at the VxWorks shell prompt (->). Use the command vxWorksShell to access that shell interface. (See the following subsection for more details.)
1.4.1
Connecting to the cards RS232 Maintenance port 1.4.1.1 Warning Improper connection of a modem to an IP Trunk capable card can cause the card to lock up access (i.e. the card CLI cannot be reached by telnet or TTY). The card continues to function as expected (i.e. most applications are still running), but the Shell Task stops working correctly. The Shell Task does not become suspended or deleted; if it did, the Task Audit would catch this and reboot the card at the non-critical task reboot time (typically, 2 AM is the default time). The problem can be avoided by ensuring the correct modem conguration before connecting to the card. The modem should be congured 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 connector on the backplane octopus cable or to the faceplate connector, but not both at once. The cards 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 development is merged prior to an up-issue of the Expert Guide, ITG> implies IPT>.
Section: 1.4.1 Page 16
Issue 1.5.4 05 May 03
Introduction
Similarly, for the Media Card the user can connect to either the faceplate connector or to a connector on the adaptor (there is no cable pre-connected to the adaptor; rather, there 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 ow control to None (Hyperterm terminology) or a similar setting. If hardware ow control is enabled, you will experience the condition of being able to see information from the card but the card wont respond to any keystrokes; the condition eventually deteriorates to nothing printing and no response. If this happens, change the ow control setting back to 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 from the VxWorks shell. The following example shows how to go from the IP Trunk shell and back.
ITG> vxWorksShell login: ******* password: ******* Welcome to the VxWorks Shell WARNING: Data entry errors in this shell could cause loss of service. Use itgShell to return to the ITG shell. value = 3382232 = 0x339bd8 = _shellHistSize + 0x4 -> itgShell ITG>
ITG> vxWorksShell login: ******* password: ******* Welcome to the VxWorks Shell WARNING: Data entry errors in this shell could cause loss of service. Use itgShell to return to the ITG shell. value = 3382232 = 0x339bd8 = _shellHistSize + 0x4 -> exit ITG>
It is also possible to go from the login shell to the VxWorks shell, and then completely exit the VxWorks and login shell using Control-C.
Issue 1.5.4 05 May 03

ITG> vxWorksShell
Introduction
login: ******* password: ******* Welcome to the VxWorks Shell WARNING: 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-C VxWorks login:
The appropriate Nortel development and Global Customer Care Service staff have the login information; it is not included here for security reasons. Note that the string ******* was used to indicate user entry, but the real string may be longer or shorter, and the password does not echo back to the user.
Issue 1.5.4 05 May 03
IP Trunk 3.0 module descriptions

This section provides a description of the application modules involved in main card functions. The task name, and index, are shown to aid in turning on the relevant logging. Note that the modules are not necessarily only of interest when debugging. Therefore, a 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 ones only; a few others exist, but are typically of little or no interest unless looking at very specic issues. The modules are listed in the order of processing messages when received from the PBX. That is, the rst module to be involved is listed rst; the one involved last in the message ow is listed last. This has no bearing on the task index, which has had a number of tasks added to the ow as time progressed. This means that newer modules have higher task numbers, even if they are the rst module to see a message. As an example, ISDN did not exist on the ITGT application until 1.5. Therefore, all 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 Layer 2 processing. The layer 2 function is on the D channel PC card, a small card using a PCMCIA connector and inserted into the front of the Media Card, or inside the Pentium card. The SMC or ITG-P card carrying the D channel PC card is sometimes referred to as the DCHIP card. This is incorrect, as DCHIP stands for D CHannel over IP. The PC card provides the layer 2, and the card provides layer 3, so it handles the DCH part of the DCHIP, but the IP side is handled by the card owning the timeslot used for the call. That is, if three cards exist in a node that has a single D channel, the D channel will be on one card only, but the IP side may be on any of the three. Therefore, it is more accurate to say that for the SMC or ITG-P cards that use the D Channel on another SMC or ITG-P card, the card with the D channel is the DCHIP Leader, and the DCHIP Leader and all other cards serviced by that D channel are the DCHIP. However, calling the DCHIP Leader card the DCHIP card is in wide use, and so has to be considered as a sloppy but accepted abbreviation of DCHIP Leader. It isnt quite right, but without the DCHIP Leader there wont be a DCHIP...
Issue 1.5.4 05 May 03
Section: 2 Page 19
ISDN messages received from the Meridian 1 receive layer 2 handling on the D channel PC card. The messages are passed from the card to the main card via the LAPD module. Messages in the reverse direction (IP to PBX) also use the LAPD module, but in this case the message is sent from the main card to the D channel PC 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 specic Q.931 ISDN messages to the Universal ISDN Protocol messages. Passes messages to the IGCC. 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 (Universal UIPE Message) from the LAPD task, extracts the calling number, called party number, maps the channel Id to a Follower and passes the message to the TSM on the 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 messages to NPM. This module is the core state machine for the IP Trunk 3.0 application. Other state machines exist for the call across a specic transmission medium and for the DSP resources, 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 Leader; that 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 2 processing (which is on the DCHIP PC Card). NOTE: LAPD is present only on a DCHIP Leader card. Universal ISDN Protocol Control (UIPC index 11) Provides ISDN Layer 3 processing and encoding/decoding of specic Q.931 ISDN messages to the Universal ISDN Protocol messages. Passes messages to the IGCC. NOTE: UIPC is present only on a DCHIP Leader card.
Issue 1.5.4 05 May 03
ISDN Gateways Call Control (IGCC index 13) Performs tandemming and call control functions. It receives the UUM (Universal UIPE Message) from the LAPD task, extracts the calling number, called party number, maps the channel Id to a Follower and passes the message to the TSM on the follower card. NOTE: IGCC is present only on a DCHIP Leader card.
The following modules must be debugged on the card actually carrying the speech path from the Meridian 1 to the IP network. Telephony Signalling Module (TSM index 0) Performs H.323 call setup based on digits passed by IGCC. Passes messages to NPM. This module is the core state machine for the IP Trunk 3.0 application. Other state machines exist for the call across a specic transmission medium and for the DSP resources, 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.3
Modules key to QoS related problems

QoS monitoring is entirely carried out by the Leader card currently active. The ping goes from the leader to the remote node IP, and the response returns to the leader card. Similarly, the remote node also pings the local node IP, which resides on the active leader. Since the QoS is determined on a 2 ended model where the pings from both sides are used to calculate the MOS score, only the leader could have information from the remote node pings, so therefore only the leader can do any QoS monitoring. There is one exception, though. The Leader informs the follower cards of changes to the QoS capabilities of a given node, allowing the local ATPMs on those cards to treat the remote node as though it was in fall-back when service degrades past the minimum acceptable threshold. Monitor TimeServer (MTS index 5) Receives QoS probe packets from remote nodes in the network and passes it to the MSM for further processing. Monitor Server Module (MSM index 6) Process the QoS probe packets and emulates the E-model for MOS calculations.
Issue 1.5.4 05 May 03
Monitor Client Module (MCM index 7) Sends the QoS probe packets and the sender/receiver packets to remote nodes in the ITG Trunk and/or IP Trunk network.
Address Translation Module (ATPM index 14) 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 owned by the leader, but the follower RMM handles the queries. Resource Manager (RMM index 2) Provides resource management. Examples include channel assignment for incoming / outgoing calls, memory management functions, hosts UDP server for inter-card communication, probing/maintenance/recovery of E-LAN / T-LAN connections. Common Task (COM index 16) Works in conjunction with the RMM. The IP Socket Server is predominantly DCHIP Leader to DCHIP Follower, but it also does signalling to the node Leader. Depending on the issue, debugging may have to be done on the leader (scanning the D channel registration table), or on the DCHIP Leader 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 module calling 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 only applications 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 RTP is also on the TLAN) MCDN connectionless message transport
Issue 1.5.4 05 May 03
Inter-card communications for ISDN are normally over the TLAN, but there is a fail-over capability on IP Trunk 3.0 allowing the signalling to switch to the ELAN when the TLAN fails.
The following tasks are frequently involved in LAN issues. Resource Manager (RMM index 2) Provides resource management. Examples include channel assignment for incoming / outgoing calls, memory management functions, hosts UDP server for inter-card communication, probing/maintenance/recovery of E-LAN / T-LAN connections. Common Task (COM index 16) Works in conjunction with the RMM. 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 module calling this function.
2.6
Modules key to OTM to card communication and conguration problems

When the CONFIG1 and BOOTP les are downloaded, the card must be disabled at the Meridian 1 (LD 32, DISC <tn>). These les may be downloaded then, but will not take effect until the card reboots. The dial plan information in the DPTABLE may be downloaded to a running card. It may be activated either as a function of the download, or manually. The card does not need to be disabled, although the new data is only used after the application loads the new table. The software image may be downloaded without disabling the card. On completion of the download, the card must reboot for the software to upgrade. Note, though, that an unexpected reboot while in the middle of the download may have unexpected and very destructive effects. Some of the following modules function fully on all cards and are queried on a card by card basis. Others are leader(s) only. The BOOP le downloads to leaders only; the other les download to all cards. It is best to assume debug the module on whatever card has the issues. Maintenance Administration Module (MAM index 4) Provides conguration support by parsing the conguration le and setting up routes, DSP parameters etc.
Issue 1.5.4 05 May 03
Network Management Module (NMM index 3) Provides communication between the card and the craftsperson. This can be via OTM or telnet session.
Operational Measurements Module (OMM index 8) Collects the OMM measurements for the card and logs them to the le. It also performs 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 card. Intercard messaging errors. Debug on the DCHIP Leader rst, and if the IP message leaves the application, conrm it reached the destination. Then, debug on that card.
Note: the rst 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 2 processing (which is on the D channel PC card). Universal ISDN Protocol Control (UIPC index 11) Provides ISDN Layer 3 processing and encoding/decoding of specic Q.931 ISDN messages to the Universal ISDN Protocol messages. ISDN Gateway Call Control (IGCC index 13) Performs tandemming and call control functions. It receives the UUM (Universal UIPE Message) from the LAPD task, extracts the calling number, called party number, maps the channel Id to a Follower and passes the message to the TSM on the follower card. IP Socket Server (IPSS - index 18) Provides inter-card communication path between DCHIP and Followers. Telephony Signalling Module (TSM index 0) Performs H.323 call setup based on digits passed by IGCC. Passes messages to NPM.
Issue 1.5.4 05 May 03
This module is the core state machine for the IP Trunk 3.0 application. Other state machines exist for the call across a specic transmission medium and for the DSP resources, but this state machine ties all of the other sections together.
2.8
Modules key to SSD / A07 related problems

SSD messages (processed by the A07 module) provide signalling that is mostly of little 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 fault reporting. These are redundant, given the ISDN signalling. However, SSD messages also provide signalling about pad levels for transmit and received, as determined by the Meridian 1 core. The Meridian 1 determines the correct pad settings based on the other termination on the switch, and sends this information 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 debugged from the card where the channel resides. A07 (index 9) Provides an SSD interface to the M1 via the DS30X Signalling protocol. Telephony Signalling Module (TSM index 0) Performs H.323 call setup based on digits passed by IGCC. Passes messages to NPM. This module is the core state machine for the IP Trunk 3.0 application. It drives the 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. Telephony Signalling Module (TSM index 0) Performs H.323 call setup based on digits passed by IGCC. Passes messages to NPM. This module is the core state machine for the IP Trunk 3.0 application. It drives the DSP interface module and DSPs.
Issue 1.5.4 05 May 03
Troubleshooting
Troubleshooting
The following sections contains tips and suggested commands for troubleshooting a number of different types of problems. They also include a small number of steps usually key to resolving a problem to try associated with the section problem area. (If the user needs more detailed debugging, the user should use the appropriate chapter, listed in the section.) 3.1 - Using a Network Sniffer - tips on setting up and using a network sniffer 3.2 - General card commands 3.3 - Disk and Directory Commands 3.4 - Network Troubleshooting - tips and commands related to network problems 3.5 - Call Related Problem Troubleshooting - commands related to call problems 3.7 - Address Translation Troubleshooting - commands related to call problems 3.8 - D-Channel Related Troubleshooting 3.9 - Backup Leader start-up issues - issues with prior releases, which have a solution in IP Trunk 3.0 and have not been duplicated since the x was installed
The following chapters contain more detailed tips and suggested commands for troubleshooting 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 issues 9 - BIOS / BootROM functionality - tips and commands related to recovering from 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 Page 26
Issue 1.5.4 05 May 03
Troubleshooting
3.1
Using a Network Sniffer

A network sniffer is an excellent tool for troubleshooting network devices. By capturing exactly whats sent on the wire and providing decoders for the various protocol levels, capture traces often provide solid answers as to why ITG Trunk and/ or IP Trunk cards arent communicating, or the source of voice QoS problems. The following 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 being investigated. A passive hub means the sniffer will see the same trafc as the IP Trunk node since all ports receive the same data. It is best to match the speed of the hub to the speed of the SMC/ITG-P network interface - 10BT for the E-LAN, 10/100BT for the TLAN. When an active hub or switch is used, you need to congure port mirroring (or a similarly named feature - product dependent) so the switch will send a copy of all packets on the port of interest to the port with the sniffer connected. If the active hub or switch doesnt support port mirroring or you dont have access to its management interface, you can insert a passive hub in line with the desired port and connect the sniffer to it. It can be useful to connect a sniffer at both ends of an IPT to other device1 connection that is having problems. Comparing the two capture les may uncover network problems such as a router discarding signalling messages or old ARP cache addresses in packets.
3.1.2
Sniffer Pro Use the capture lters to reduce the amount of captured information (unless capturing everything can provide clues to the root of the problem). For instance, create a lter with the relevant cards TLAN interface (Voice LAN Node IP and/or Voice IP) and the IP address of the remote device being debugged. First create a new Prole, then modify the Proles Address parameters to the ITGs TLAN IP address and the IP address of the Node IP if the card is the Leader Card. Finally, select the lter before starting the capture. Note: Be sure to select IP for the Address Type. If set to Hardware, the MAC address of the endpoints is expected but the program allows you to enter an IP address; you wont get any indication theres a problem until you get an Invalid Hardware Address error when you try to capture using the lter.
1. This other device could be IPT, ITGT, IP Peer, IP Lines, BCM, or third party.
Issue 1.5.4 05 May 03
Troubleshooting
Similarly, use the display lters to lter information from a capture le while narrowing in on a problem. A new window is created each time an applied lter changes the contents. You can then save just those windows with useful information. The process for creating the lter and selecting it is the same as for the capture. After stopping the capture, display it. Select the Decode tab on the expert window to see the packet decode. It is possible to set lters to capture and/or display on certain port addresses which can be useful when ltering out H.323 Call-Set-Up messages or QoS Probe packets or for tracing both directions of the RTP Voice packets. The Matrix tab gives a graphical view of whos talking to who. Change the upper left hand pull down menu to IP to have the IP address/host names displayed. The Host Table tab gives a list of statistics for each host in the capture, while the Statistics tab gives overall statistics. Ping and Traceroute are available under the Tools menu. When host names arent assigned to network devices, you can create names using the Address Book under the Tools menu. The names then appear in the capture les where ever the IP address would have appeared. This makes reading the trace les faster than looking at IP addresses. This address book is saved under the Database menus Address Book entry.
Issue 1.5.4 05 May 03
Troubleshooting
3.2
General card commands

Refer also to chapters 5 - Debugging the shell and 6 - Debugging the node for more comprehensive debugging information. Some commands can be used to verify the general sanity of the card. However, not all can be used in all scenarios. This is especially true if the card cannot complete a boot-up of the IP Trunk application. In the event of a failed boot, the user can investigate via the BIOS/BootROM boot-up sequence. For details, refer to chapter 9 - BIOS / BootROM functionality. Assuming that the card booted, a number of basic sanity items may provide useful information. 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 sanity commands. Follower to leader registration - ldrResTableShow (section B.1.24, pg 158) Verify all the Follower cards have registered with the Ldr. 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. Card to DCHIP leader registration - dchipResTableShow (section B.1.9, pg 124) Verify that the Follower cards have registered with the DCHIP. For each missing Follower, check the ELAN cabling and hub and verify the correct DCH number was congured 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. rmwareVersionShow (section B.1.12, pg 135) Displays the version of SMC or ITG-P card rmware. Should be (Media Card) base card version 6.4 and XA version 4.8 or higher, and rmware release 5.7 or 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 matching string (is case sensitive). serialNumShow (section B.1.38, pg 165) Displays the cards serial number.
Issue 1.5.4 05 May 03
Troubleshooting
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 use by the application. ashCongShow (section B.2.11, pg 179) Displays the cards Flash memory conguration. showMemCong - Pentium only (section B.2.58, pg 222) Displays the cards DRAM memory conguration. setLeader IPaddr,gwIPaddr,subnetMask (section B.1.39, pg 165) Congures the card as a Leader and saves it in the NVRAM. clearLeader (section B.1.7, pg 122) Congures the card as a Follower and saves it in the NVRAM. NVRClear (section B.1.27, pg 160) Erases data from the cards NVRAM. NVRIPSet IPaddr (section B.1.29, pg 162) Congures and saves only the cards ELAN IP address in NVRAM. NVRSMSet subnetMask (section B.1.31, pg 162) Congures and saves only the ELAN subnet mask in NVRAM. NVRIPShow (section B.1.30, pg 162) Displays the ELAN conguration 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 release of ITG-P rmware and at least version 6.4 of SMC rmware.
3.3
Disk and Directory Commands

The following commands are applicable to the cards le system. cd dirPath (section B.1.6, pg 122) Change the current working directory.
Issue 1.5.4 05 May 03
Troubleshooting
Note: The VxWorks le system allows you to enter a non-existent directory when doing the cd command and wont return an error code. It is only when you try to access a le that youll get a -1 returned. copy sourceFilename, destFilename (section B.1.8, pg 123) Copies a le. If destFilename isnt entered, outputs le contents to TTY display. If the sourceFilename is 0, the command takes input from the command line interface 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 status only, repairLevel and entryLenType parameters can be omitted. dosFsCongShow (section B.1.11, pg 134) Displays details about the /C: drive conguration. ll (section B.1.25, pg 159) Displays a long format listing of the directorys contents. iosFdShow (section B.2.16, pg 184) Displays all active le descriptors. pwd (section B.1.33, pg 163) Displays the current working device/directory. mkdir dirName (section B.2.38, pg 197) Creates subdirectory dirName in the current directory. rm lename (section B.2.49, pg 216) Deletes lename from the current directory. rmdir dirName (section B.2.50, pg 217) Deletes subdirectory dirName from the directory. swDownload srvrIP, uid, passwd, path, fname (section B.1.41, pg 166) FTPs the application binary to the card.
3.4
Network Troubleshooting
The following commands can be useful for debugging ethernet or network related problems. ping IPaddr, numPings (section B.1.32, pg 163) Executes the ping command for checking network connectivity to a remote host. ifShow (section B.1.17, pg 146) Displays details about the active ethernet interfaces.
Issue 1.5.4 05 May 03
Troubleshooting
IPInfoShow (section B.1.18, pg 148) Displays the cards IP conguration information. NVRIPShow (section B.1.30, pg 162) Displays the ELAN conguration data as stored in the NVRAM. routeShow (section B.1.37, pg 164) Displays the ITGs host and network routing tables. routeAdd destIPaddr, gwIPaddr (section B.1.35, pg 164) Add a route to the ITGs route table. routeDelete destIPaddr, gwIPaddr (section B.1.36, pg 164) Delete a route from the ITGs route table. mRouteShow (section B.2.43, pg 202) Displays the routing tables entries with the ToS and net mask information. mRouteAdd destIPaddr, gwIPaddr, 0xdestNetMask, To, 0 (section B.2.41, pg 202) Allows adding multiple routes to a location to the ITGs route table. mRouteDelete destIPaddr, 0xdestNetMask, ToS (section B.2.42, pg 202) Deletes one of the multiple routes to a location from the ITGs route table. arpShow (section B.2.2, pg 171) Displays the current ARP table. arpFlush (section B.2.1, pg 171) Flushes the ITGs 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. iosFdShow (section B.2.16, pg 184) Displays all active le descriptors. 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)
Issue 1.5.4 05 May 03
Troubleshooting
Enables/Disables the display of ELAN broadcast count messages (default is off). lnIsaBroadcastThreshold = threshold - not applicable, SMC (section B.2.23, pg 187) Sets the threshold (default is 40 pkts/sec) for display of ELAN broadcast messages. 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 is off). This value is reset on Power-Down/Reboot. lnPciBroadcastThreshold = threshold - not applicable, SMC (section B.2.28, pg 189) Sets the threshold (default is 40 pkts/sec) for acceptance of TLAN broadcasts. This 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 of voice quality and user satisfaction issues. The following are some suggestions on things to do to determine if the network is causing problems. Make sure the ELAN, TLAN and Node IP addresses are properly congured. Every card has unique ELAN and TLAN interface IP addresses. The Node IP is shared amongst the cards and is programmed for the TLAN interface. Important: Separate subnets for the ELAN and TLAN interfaces is the recommended conguration for the ITG Trunk release 2.0 or 2.1 card. It is also recommended for IP Trunk 3.0. It is possible to dene a single subnet conguration by un-checking the Use separate subnets for voice and management checkbox in the MAT/OTM General Node Properties screen.
Issue 1.5.4 05 May 03
Troubleshooting
Note that the intention for this conguration is to leave the TLAN cabling disconnected from the network and all network communication to occur over the ELAN. Using this mode automatically reduces the trunk network bandwidth to the maximum 10BT conguration supported by the ELAN. ELAN: (Embedded LAN) - carries maintenance/admin/alarm data between OTM and SMC or ITG-P cards and ISL D Channel signalling traffic between the M1 CPU (via the configured DCHIP Leader card) and the cards in the node. All ELAN addresses for all cards in the node must be on the same subnet. TLAN: (Telephony or Voice LAN) - carries H.323 (H.225 and H.245) and RTP packet data between IP Trunk nodes. All TLAN addresses must be on the same subnet for cards in the same node. CLAN: (Customer LAN) - regular customer LAN for their PCs, etc. The ITGs TLAN must be protected from the broadcast traffic that can regularly occur on the CLAN. Node IP: on the TLAN subnet; used for Inter-Node communication. This address is shared by the cards; it is assigned to the TLAN interface of the current Leader and is held by the current Back-Up Leader in case it is required to become the Leader. Check the conguration of the router/hub ports connected to the SMC or ITG-P (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 Carrier)? Some early ITG-P octopus cables reversed the ELAN and TLAN cable labels. Unplug both and plug in the TLAN cable; if the green LED doesnt light, try the cable marked ELAN. Correct the cable labels if they are reversed. Does the yellow activity LED flash when theres 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 connected to a hub)? Does the A (activity) LED flash when theres TLAN traffic to the card? Get a network diagram of the cards, and all other data devices on the network. Ask the customer how much trafc is on their network, do router statistics show dropped packets, etc. Try to understand which devices are experiencing trouble. All? Just a specic subnet? All the time or intermittently? Dene the bottlenecks in the network and understand the routing and QoS policy for the network.
Issue 1.5.4 05 May 03
Troubleshooting
Replacing an SMC or ITG-P card means a new MAC address (from the new card) is associated with the existing cards IP address. Sometimes, with some routers, you must ping the router interface from the recenhtly replaced card in order to speed up the updating of the routers ARP table. Some routers take tens of minutes to time out entries in their ARP table, during which time packets to the cards IP address will not arrive on the new card. The simplest trunk conguration is to have a single card node where the card acts simultaneously as the Leader and DCHIP Leader card. Errors can occur as more cards are introduced in terms of BOOTP le mis-conguration, inter-card communicatoin issues etc., so establishing a single card node rst can assist with debugging more involved network issues. Run a ping test between the two IP Trunk nodes which are experiencing problems. You can do this from card to card directly, or perhaps congure P.C.s on the TLAN subnets at both nodes to remove the Ip Trunk application from the network test completely. Log the output. Were any packets lost? Was the delay highly variable? These indicate the network may not be suitable for carrying voice trafc. Connect a sniffer to the LAN, close to the card (preferably on the same hub) to capture packets going to/from the card. When a problem occurs, stop the sniffer. If the traces as well as other appropriate information such as the IP address of the devices involved are provided to Technology, they can be examined to determine if there is a network problem or a problem with the card itself. Note: Note, there are potential privacy concerns with this approach since the RTP packets can be reassembled into audio les (a necessary step when investigating voice 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 enable in their network. If it appears to be an IP Ttunk (or trunk card) problem, it should be escalated 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 device on the Media Card does not report packet errors. Error messages with the format tLogTask: Info lnPci: lnPci1 RMD error: RMD1 = xxxx indicates a problem on the TLAN interface. The upper byte contains the error information and can be decoded as follows:
Bit 15 (MSB): Ownership - 0 = host, 1 = Ethernet Controller Bit 14: ERR - if set there is an error in the packet, bits 13-10 indicate the specific error type: Bit 13: FRAM - Framing Error - non integer multiple of eight bits in frame. Bit 12: OFLO - Overflow error on DMA or internal FIFO Bit 11: CRC - CRC error on frame.
Issue 1.5.4 05 May 03
Troubleshooting
Bit 10: BUFF - Ethernet Controller could not get a new buffer before FIFO overflow occurred.
The lower byte can be ignored. Typical values seen for xxxx are 4b05 and 6b04 which indicate a received packet(s) with a CRC and Frame error was detected, respectively. This error message is usually due to cabling or hub problems. The following should be checked: Is the hub congured correctly? Ideally the hub is left in autonegotiation mode. See section 3.4.3 for details. If it's a large system (Opt 51/61/81), is the correct backplane lter 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 cable? Try 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 directly into the RJ-45 socket on the ITG's DSP daughterboard (or use an adapter cable plugged into the ITG's faceplate TLAN jack (labelled NWK), with the other end plugged into a known good port on the hub. This bypasses the backplane lter, octopus cable and existing LAN cabling. If the RMD error messages stop, then the problem is in the existing TLAN wiring or backplane lter. 3.4.3 QoS Troubleshooting The quality of the speech path across the IP network is dependent on many parameters but one of the most key is packet loss. The IP Trunk node performs QoS probing to and from port 5000 of the IPT Leader card. SNMP alarm messages are generated if the pre-dened QoS threshold is not met. The QoS probes use a weighted average of the round trip delay and packet loss for multiple probe bursts (inter-gap delay of 15 seconds between each new set of probe packets). The result of the QoS probes are maintained for one and half minutes to maintain a constant sliding window for weighted averaging. Falling below the QoS probe threshold will result in a fallback (on the next call, not on the current active calls) to alternate routing for calls to the node experiencing network difculty. The fallback status of a node can be checked using the numNodesInFallbackShow command:
-> numNodesInFallbackShow Nodes In Fallback = 1 47.85.2.75 value = 1 = 0x1
Issue 1.5.4 05 May 03
Troubleshooting
If the customers conguration does not support an alternate routing method, then the QoS probing should be disabled in MAT/OTM. If the far end happens to be in fallback and the QoS statistics printed in the alarm are questionable, then the monitor utility can be used. NOTE: Its primary purpose is to debug the network monitor itself and in some cases maybe helpful to view the network characteristics. In general, one should not have to use this in the eld except to view the 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 level should be based on measured performance of the network. monIPDebugSet IP.ad.dr.ess, on_off (section B.2.39, pg 198) - for checking remote nodes. Furthermore, detailed analysis of the network must be performed to establish a realistic target for the QoS level (e.g. a QoS level of 4 allows for 0% packet loss across a network). Refer to the NTP. The impact of packet loss varies, but even single lost packets can cause audible clicks, while higher packet loss sounds like choppy speech. Packet loss is usually due to a router 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 conguring the TOS settings in MAT/ OTM. Note that the TOS value is applied to both the RTP voice packets and the QoS probe packets (which must follow the same network path as the RTP packets). Some routers also support RTP header compression across the WAN. This feature can be enabled on the ITG Trunk card (running ITG2.xx.25 and 26G) by using the following 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 to provision the RTP port numbers in much the same manner. 3.4.5 Network Interface - Speed and Mode Settings. The following should be checked:
Issue 1.5.4 05 May 03
Troubleshooting
Verify the ports of the hubs/switches they are connected to are congured correctly. They should be one of the following (in highest to least desirable order): Note: The trunk cards TLAN interface supports 10BT and 100BT half and full duplex. The ELAN supports only 10BT half duplex. Auto-negotiation - this is the recommended setting. The cards TLAN interface will autosense the speed and autonegotiate the half/full duplex setting. Setting the hub or router port to do the same means the fastest possible connection will negotiate without intervention. Manual setting: 10BT, half duplex You cannot manually congure a port on the router/hub to 10BT or 100BT full duplex and have an error-free connection to the ITG-P or SMC card. Manual conguration turns off auto-negotiation in nearly every product on the market. By denition of the standards, without auto-negotiation, the card will revert to half duplex operation. This means the router/hub will be in a full duplex mode while the card is in a half duplex mode, a situation guaranteed to cause packet loss. If the switch port is set to half duplex and sees lots of late collisions and duplicate collisions or if it's in full duplex mode and sees lots of CRC Errors or runt frames then odds are it's a mismatch.
Check the router's statistics to see how much network trafc is on each subnet and to see the number of packets being discarded. Check if there are differences in subnet congurations (i.e. full vs. half duplex or 10BT vs 100BT) if the problem is only happening for some ITG-P or SMC cards and not others. Check what QoS mechanism is enabled on the router to give priority to the packet trafc from the IP Trunk node. Try setting the hub/switch for 10BT half duplex operation and check if that eliminates the packet loss messages. If it does, there may be wiring problem or the site doesnt have CAT-5 cable.
3.4.6
Broadcast storms Broadcast storms on the TLAN or ELAN network the IP Trunk node is connected to eat up resources on the card. The card performs best in a network without a lot of broadcast trafc.
Issue 1.5.4 05 May 03
Troubleshooting
For ITG Trunk 2.0 and an ITG-P running IP Trunk 3.0, if you suspect broadcast storm problems, there is a broadcast monitor which can be enabled (independently) on the ELAN and TLAN interfaces. The monitor prints a message when the dened threshold is exceeded. This provides a simple way to monitor a network without being connected to the card at all times: enable the monitor and then review the CURRLOG.1 les for the threshold messages. The messages have the form:
FEB 12 12:23:27 tLogTask: Info Time 332140 lanais: 1 broadcasts in last second FEB 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 of the ITG-P or SMC. See thelnIsaBroadcastShow - not applicable, SMC (section B.2.22, pg 187),lnPciBroadcastShow - not applicable, SMC (section B.2.27, pg 189) and related commands for details. Note that the ITG Pentium card (running ITG2.24.25 and greater) has the ability to do physical level ltering of Broadcasts. This facility is enabled by default and can be conrmed by using the itgCardShow 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 ltering is done by the microEngines coprocessors. The microEngines interrogate every broadcast packet for the 4 IP addresses that are applicable to the card and if they are, then they will be sent to the Core processor for processing. As in ITG-P, a threshold value can be set so that if the number of broadcasts on the network exceeds this value, they will be dropped by the microEngines. 3.4.7 Port numbers used by the IP Trunk 3.4.7.1 TCP Ports Table 1: Predened TCP Ports
Interface
ELAN TLAN
Port use
DCHIP Inter-card messaging H.225 TCP Port 6001
Port Number
1720 (* Destination port only)
Issue 1.5.4 05 May 03
Troubleshooting
3.4.7.2 UDP Ports The following UDP ports are predened. Table 2: Predened UDP Ports
Interface
ELAN ELAN TLAN BOOTP Server SNMP RTP Ports and usage: * default port range * compatible with CISCO RTP header compression TLAN RTCP Ports: * default port range * compatible with CISCO RTP header compression TLAN TLAN TLAN MCDN Call Independent Messaging: Inter-Card Communication: Network QoS Monitor Port: 2301-2363 (2301 + TCID*2) 17301-17363 (17301 + TCID*2) 15000 2001/2002 5000 2300-2362 (2300 + TCID*2) 17300-17362 (17300 + TCID*2)
Port use
Port Number
67 (on Leader card) 161
3.4.8
SNMP traps You can use the dummy_trap (section B.2.9, pg 178) command to verify that the SNMP traps are congured correctly and the receiving device (MAT, OTM or some other trap alarm manager) is receiving the alarms. This sends the alarm without causing any of the side effects that triggering the real alarm may do (e.g. unplugging the TLAN to generate the TLAN loss of carrier alarm impacts call processing). Remember to congure all of the cards in the MAT/OTM Alarm Notication application 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 cards channels. h323SessionShow (section B.1.15, pg 143)
Issue 1.5.4 05 May 03
Troubleshooting
Lists the details of the h323Session for all active channels originating IP address, destination 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 levels of display. h323CallTrace (section B.1.14, pg 140) This will print the NPM call trace and help enable the IGCC trace. Note that this is the polite access function used to call setTraceOption channel,outputLocation (section B.2.54, pg 220). Note also the IGCC minimal trace is accessible by function igccAddTrace channel (section B.2.14.1, pg 182). This does NOT enable TSM 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 used h323CallTrace (section B.1.14, pg 140) or setTraceOption channel,outputLocation (section B.2.54, pg 220) to enable the NPM trace rst. tsmSetTraceOption TCID,[0 or !0] (section B.2.63, pg 227) This VxWorks shell command will print the TSM call trace, provided the VxWorks shell command mixSetLogOpt module, option, level (section B.2.37, pg 195) is used for the TSM rst. tsmChanShow [level[,channel]] (section B.1.43, pg 167) This login shell command prints basic data about the call as viewed by the TSM. itgMsgCtrShow (section B.1.23, pg 157) Various message counters kept by the TSM task on the card can be displayed using this command resetOM (section B.1.34, pg 163) Writes the current OM counters to disk and resets them to zero. mixSetLogOpt module, option, level (section B.2.37, pg 195) This VxWorks shell command is the general purpose state change/message monitoring tool. Meridian 1 overlays: Overlay 32, STAT <card TN> to check the status of a card. Overlay 96 to 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 S/W selects a calls channel.
Issue 1.5.4 05 May 03
Troubleshooting
The M1 S/W selects the channel used for outgoing calls through the card based on linear route selection. As a result it will attempt to use the uppermost member of a dened route for outgoing calls. For this reason Leader and DCHIP Leader cards (which have additional processing responsibilities over and above normal callprocessing) should be congured as the lowest members of the IP Trunk route. The IP Trunk Leader card uses a Resource Management Module S/W layer to determine how incoming calls are re-directed to available channels on cards within its node. It emulates the linear mechanism used by the Meridian 1 and will attempt to allocate incoming calls to the uppermost channels down to the lowest. It will also attempt to use up available channels on Followers, followed by Back-up Leaders followed 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, which is in section 7.2.4 on page 64. However, gatekeeper registration issues also may exist. Under normal circumstances debugging gatekeeper registration is relatively simple. Use gkShow (section B.1.13, pg 135) to verify that the gatekeeper is registered. This also prints out much of the provisioning data as it was loaded. Check the H.323 ID, and the IP address (or addresses) of the gatekeeper (or primary and alternate gatekeeper). Corruption in the image on RAM may be recovered via nmmAtpmTranTblDnld (section B.2.45, pg 203). If the provisioning is correct but the gatekeeper is unregistered, there may be a LAN issue. Use ping IPaddr, numPings (section B.1.32, pg 163) to determine whether 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. If the Register Request was sent, either no response occurred (investigate at the gatekeeper) or a reject came back. Investigate the failure cause. Check to be sure that the address is not mistakenly provisioned in the DPTABLE.1. Only calls to destinations not included in static provisioning use the gatekeeper. Therefore, including a digit string that preempts gatekeeper resolution of calls can cause call failure. See 3.7 Address Translation Troubleshooting on page 43. If all else fails, even when the data on-switch is correct sometimes nmmAtpmTranTblDnld (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 RTP session issue, or a network QoS issue.
Issue 1.5.4 05 May 03
Troubleshooting
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 or a missing IP entry; the latter should be a rare case if the entry is congured and downloaded to the card, unless there is a bigger problem. The following is a suggested sequence of steps to investigate an address translation problem. First, check the conguration in OTM to ensure the correct dialplan table data is congured. Check DPTABLE.1 les exists on the card /C:/TABLE/DPTABLE.1 - list and make sure the size is non-zero copy dptable.1,0 to list the le on the ITG-P or SMC TTY Use the following commands to print the various dialing plan tables to check that they 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 also Caveat - serious danger from provisioning errors within the DPTABLE.1 (section B.2.48.1, pg 212) for some warnings in this area. At this point the provisioning (both in the le and in memory) has been validated; address this as a call rpcessing call, using mixSetLogOpt 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 - mixSetLogOpt 0,1,1 and tsmSetTraceOption TCID,[0 or !0] (section B.2.63, pg 227) where TCID is the specic channel on the card.)
Issue 1.5.4 05 May 03
Troubleshooting
3.8
D-Channel Related Troubleshooting

3.8.1 DCHmenu The ITGs DCH Handler is the UIPE application ported from the MSDL card. This is a menu based debug tool nearly identical to that on the MSDL card. It enables the printing of info / error messages from the UIPC task and displays the status of the DCH, protocol used, etc. Note that the Enable/Disable functions toggle for a selection, so if the menu prints Enable . For an item, then that item is disabled. Entering that menu item will enable it; the next time the menu prints it shows Disable for that item. The DCHmenu (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 on the backup leader card. This issue should be resolved. However, it is not unknown for symptoms to be caused by two or more problems, but a x resolve only the most prevalent. Therefore, the following is included. Problem statement During power up or reboot IP Trunk card resets the TLAN interface near the end of the reset cycle, which momentarily stops transmitting link pulse to the layer 2 switch, thus triggering Spanning Tree Protocol standard learning mode. This interferes with the communication 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 is not forwarding packets, the backup leader does not receive a response and takes over as leader. However, as soon as the switch comes back, the backup leader discovers the error and reboots to clear it. The basic problem is that intelligent Layer 2 switches default to having Spanning Tree Protocol (or Cisco equivalent) standard learning mode enabled on all Layer 2 switch ports. Spanning Tree Protocol is in standard learning mode for at least 20 seconds after the Layer 2 switch port is reset, or after the switch port momentarily stops receiving link pulse from the IP Trunk card TLAN or ELAN interface.
Issue 1.5.4 05 May 03
Troubleshooting
Scope of the problem The problem affects the interworking of ITG Trunks up to and including release 2.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 to be aware 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 switch ports that belong to the TLAN and ELAN, or to select the Spanning Tree Protocol Fast Learning Mode (or its Cisco equivalent). In general you must congure the Layer 2 switch ports to allow immediate transmission of trafc between IP Trunk Leader 0 and Leader 1 TLAN and ELAN interfaces after a powerup or reboot of the IP Trunk cards. As a rough form of robustness exercise, it is worth maintaining this procedure for IP Trunk 3.0 as well, but should not be required.
Issue 1.5.4 05 May 03
Potentail provisioning problems
4
4.1

Creating trunks for ESN5
This problem is erratic in that it occurs only with certain as yet to be conrmed packaging combinations; it does not apply to all systems. However, when it happens, it happens all the time. IP Trunk 3.0 supports ESN5 capability for the trunk cards. It also allows either wink start or immediate start. This capability applies equally to both the Meridian 1 side and the ITG-P or SMC side. However, provisioning on certain releases of the Meridian 1 with some packaging combinations blocks adding IT Trunk units to an ESN5 capable route. The symptoms seen are blockage at a prompt when entering a valid response. There is a relatively simple work-around. If the user changes SIGO in the RDB to STD (standard and not ESN5 signalling), adds the trunks, and changes back to SIGO ESN5, the provisioning succeeds. This should be done during off-hours, as the mismatch between the Meridian 1 and IP Trunk provisioning will cause any calls during 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. These operations include but are not limited to uploading one site provisioning to copy it into another. At this time, the user may attempt synchronize the data. However, sometimes the transmit indicates success in the OTM window but the provisioning may not have succeeded; typically, the new provisioning was discarded. The most common sypmtom of this is output on the login screen such as the following excerpt:
2040 2040 2040 2040 2040 2040 2040 2040 2040 2040 2040 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 00:14:12 00:14:12 00:14:12 00:14:12 00:14:12 00:14:12 00:14:12 00:14:12 00:14:12 00:14:12 00:14:12 (SNMP) :services_set: Setting file Lock (NMM) :Module 4 setting file system lock (NMM) :itgFileXfer: transfer type: TYPE I (NMM) :itgFileXfer returning with status OK (NMM) :fileSize: 955 (NMM) :hostFileGet exiting with status OK (NMM) :sending fileXferOk message to task 4 (NMM) :hostFileGet returning with status 0 (SNMP) :ContactSet: The SNMP Value is Invalid (DIM) :Download codec image completed -DSP# 0, Image Id = 0 (NMM) :NMM received file data OK message from MAM
Section: 4 Page 46
Issue 1.5.4 05 May 03
2040 1 1 00:14:13 (DIM) :Download codec image completed -DSP# 1, Image Id = 0 2040 1 1 00:14:13 (SNMP) :services_set: Clear file Lock
It is not apparent from this capture, but the system discarded the new conguration data. 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 conguration window
Issue 1.5.4 05 May 03
Under this window, at the indicated button, is a data entry screen. The error message listed 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 rigorous than others. However, if this problem occurs in the eld, look in all the contact name elds of OTM provisioning. There are three areas (four, if gatekeeper provisioning is used): Site provisioning System provisioning Conguration 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 application to set the echo canceller length. This made it mandatory to read the OTM le and set the cancellation length appropriately. However, in OTM the default level is 32 msec tail delay. The intended default and recommended length is 128 msec. OTM for IP Trunk 3.0 allows this value to be set to various lengths including 128 msec. It just is not the default. It is recommended that whenever echo is suspected that the service staff check this parameter in OTM and reset it to 128 msec if it is not 128 msec. Note that ITG-Trunk software versions did not use the OTM to set this value. Therefore, this specic issue could not occur.
Issue 1.5.4 05 May 03
Debugging the shell
5
5.1
Debugging the shell

Introduction
The following commands control aspects of the ITG> shell access in general, and specically apply to the IP Trunk application. That is, the login sequence and many commands are generic to ITG applications; however, within this document only IP Trunk application commands are considered. While some of the commands in the remaining sections of this document are accepted at the ITG> or IPT> shell prompt, all are accepted at the VxWorks shell prompt (->). Use the command vxWorksShell to access that shell interface. Note: TTY login to the card is recommended via ELAN Telnet session instead of direct serial port connection if you are logging large amounts of data or copying large SYSLOG or OMREPORT les to the console. Using the serial port can result in call loss or worse during periods where the node experiences high trafc levels. Several commands are generally useful during the login session. These include: h and command history handling (section B.2.12, pg 180) Displays the last 20 commands entered at the VxWorks shell. Editing is available. 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)
Issue 1.5.4 05 May 03
Section: 5 Page 49
Debugging the shell
Resets the userid and password to the factory default. In the event the NVRAM becomes corrupted or some other problem prevents logging in to the card (IP Trunk application) shell, you can reset the password. Break into the BIOS as the card boots up (enter jkl when prompted). Then enter the command shellPasswordNvramClear (section B.2.55, pg 222). This resets the password to the factory 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 modication 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 system security reasons) the command shellPasswordSet (section B.1.40, pg 165) can be used to change the user name and password. This increases node security.
5.3

The user may need to query the card status regarding hardware, and loaded software. Alternatively, the user may want to carry out operations dealing with memory use, and tasks. Finally, the user may want to look up functions or variables, clear operational statistics, and set timers. These commands are relatively problem generic. For example, if a user has a problem with signalling, it is useful to be able to query the software loaded on the card, etc. 5.3.1 Hardware and software queries The following commands (in this suggested order) are useful in verifying the general status or sanity of the card. swVersionShow (section B.1.42, pg 166) Displays the version of IPT application running on the card. rmwareVersionShow (section B.1.12, pg 135) Displays the version of card rmware. Should be either 3.2 or 4.0 or higher. serialNumShow (section B.1.38, pg 165) Displays the cards serial number. ashCongShow (section B.2.11, pg 179) Displays the cards Flash memory conguration.
Issue 1.5.4 05 May 03
Debugging the shell
5.3.2
Memory and tasks Frequently, tasks may need to be queried. The user may want to determine the memory usage, to determine the state of memory (or buffer availability). The following commands (in this suggested order) are useful in verifying the memory allocation, 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 use by the application. showMemCong - Pentium only (section B.2.58, pg 222) Displays the cards DRAM memory conguration.
5.3.3
Operational data and timers The following commands (in this suggested order) are useful in clearing operational measurements 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). resetOM (section B.1.34, pg 163) Writes the current OM counters to disk and resets them to zero.
5.4
Disk and directory commands

The disk directory system should not require repair. However, it is often necessary to access les on the disk for debugging purposes. 5.4.1 Navigating the le system The following commands are applicable to the cards le system. cd dirPath (section B.1.6, pg 122) Change the current working directory. Note: The VxWorks le system allows you to enter a non-existent directory when doing the cd command and wont return an error code. It is only when you try to access a le that youll get a -1 returned.
Issue 1.5.4 05 May 03
Debugging the shell
copy sourceFilename, destFilename (section B.1.8, pg 123) Copies a le. If destFilename isnt entered, outputs le contents to TTY display. dosFsCongShow (section B.1.11, pg 134) Displays details about the /C: drive conguration. ll (section B.1.25, pg 159) Displays a long format listing of the directorys contents. ls (section B.2.30, pg 190) Displays a listing of the directorys contents. Only available in the VxWorks shell. pwd (section B.1.33, pg 163) Displays the current working device/directory. mkdir dirName (section B.2.38, pg 197) Creates subdirectory dirName in the current directory. rm lename (section B.2.49, pg 216) Deletes lename from the current directory. rmdir dirName (section B.2.50, pg 217) Deletes subdirectory dirName from the directory.
5.4.2
Verifying and sanitizing the le system The following commands are applicable to verifying the cards le system, and recovering 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 status only, repairLevel and entryLenType parameters can be omitted. dosFsCongShow (section B.1.11, pg 134) Displays details about the /C: drive conguration. iosFdShow (section B.2.16, pg 184) Displays all active le descriptors. rm lename (section B.2.49, pg 216) Deletes lename from the current directory. Useful when recovering from corruption. rmdir dirName (section B.2.50, pg 217) Deletes subdirectory dirName from the directory. Useful when recovering from corruption. swDownload srvrIP, uid, passwd, path, fname (section B.1.41, pg 166) FTPs the application binary to the card. Useful when recovering from corruption. cd, rm, copy, ll, ls, pwd, mkdir as needed
Issue 1.5.4 05 May 03
Debugging the shell
5.4.3
Download/upload of les The user may need to upload trace and log les for user handling. Alternatively, the user may need to download provisioning or control les. The following commands are applicable to the cards le system. attrib lename,protection (section B.2.3, pg 172) This command allows the user to un-protect a le on a Media Card prior to downloading to the card. ftp from a computer or workstation or OTM server. If the user needs to send or receive les between a computer or SMC/ITG-P card, the user may ftp in to the card. The ftp commands are generic; no extensions are needed. However, the user may need to execute the attrib command rst to un-protect it, swDownload srvrIP, uid, passwd, path, fname (section B.1.41, pg 166) FTPs the application binary to the card. cd, rm, copy, ll, ls, pwd, mkdir as needed
Issue 1.5.4 05 May 03
Debugging the node
6
6.1
Debugging the node

Introduction
The following commands provide ways to debug problems in the node status. This 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 direct serial port connection if you are logging large amounts of data or copying large SYSLOG or OMREPORT les to the console. Using the serial port can result in call loss or worse during periods where the node experiences high trafc levels. Several commands are generally useful during the login session. These were listed in 5.1 Introduction on page 49.
6.2

The commands are listed in 5.2 Password operations on page 49.
6.3
Conguration and startup le checking

Sometimes a user needs to ensure that the data based on the provisioning les is still valid. There are les on the hard drive that store the correct data, but the data based on this resident in RAM may be changed - either deliberately by user command, or by undesired event. 6.3.1 Verify provisioning on the card The following commands (in this suggested order) are useful in verifying the general sanity of provisioned data based memory on the card. itgCardShow (section B.1.20, pg 152). The user may be concerned about the conguration data as loaded into memory. The user may verify general conguration data for the card, e.g: IP addresses whether a card is Leader, Backup Leader, D-channel Leader, or Follower, 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 any other cards that fail to come into service.
Section: 6 Page 54
Issue 1.5.4 05 May 03
Debugging the node
ldrResTableShow (section B.1.24, pg 158) The cards, when they come up, must register with the Leader card. If they fail to do so, the user may use this command to verify all the Follower cards have registered 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 the node. The cards register with the D channel leader, which keeps its active registration table on the Leader. The user may verify that the Follower cards have registered 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 memory and remote 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. copy the BOOTP file to screen; verify that it looks valid. See A.4 BOOTP.1 on 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.2 CONFIG1.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.3 DPTABLE.1 on page 114 for format details. Use the print_nxx, print_npa, print_loc, print_spn, print_cdp commands to ensure that the information as loaded is valid. If all of the provisioning files look correct, the card should recover on reloading. If the provisioning les are corrupted, the user may download correct les from OTM. Then a reboot should revive the card correctly.
Issue 1.5.4 05 May 03
Debugging the node
6.3.3
ELAN information corrupted but provisioning valid Since the applicable les are valid, the user may be able to recover by rebooting the card. However, for sanity purposes it may be advisable to set the ELAN IP address information. If a straight reboot fails, set the IP address data using the following two commands, then reboot. Use NVRIPSet IPaddr (section B.1.29, pg 162) to set up the card IP address, allowing the OTM server to access the card (once it is live). Use NVRSMSet subnetMask (section B.1.31, pg 162) to set up the ELAN subnet mask data.
6.3.4
ELAN and conguration information corrupted This is less pleasant. The actions vary based on whether there is a leader and backup leader, 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 revive this node. Clear the current provisioning data. Use clearLeader (section B.1.7, pg 122) to configure the card as a Follower; this command saves the new status in the NVRAM. Note that the subsequent reboot will ignore all of the data. Alternatively, use NVRClear (section B.1.27, pg 160) to erase data from the cards NVRAM. Delete the provisioning files. Use setLeader IPaddr,gwIPaddr,subnetMask (section B.1.39, pg 165) to reconfigure the card as a Leader. Or, use NVRIPSet IPaddr (section B.1.29, pg 162) and NVRSMSet subnetMask (section B.1.31, pg 162) to set up the ELAN data. Use NVRIPShow (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. However, a recovery from the ground up may be avoidable. Without a DCHIP Leader, no ISN messages can be received from the PBX. Since call establishment is exclusively via ISDN, the node cannot process calls. Delete the provisioning files.
Issue 1.5.4 05 May 03
Debugging the node
Use NVRIPSet IPaddr (section B.1.29, pg 162) and NVRSMSet subnetMask (section B.1.31, pg 162) to set up the ELAN data. Use NVRIPShow (section B.1.30, pg 162) to confirm the data. Reboot the card. Download provisioning from OTM. Reboot again. Leader and backup leader card, possibly with followers; leader or backup leader corrupted. The card is effectively dead, but the node is still running. Repair the damaged card. ALL COMMANDS ARE EXECUTED ON THE FAILED CARD. Clear the current provisioning data. Use clearLeader (section B.1.7, pg 122) to configure the card as a Follower; this command saves the new status in the NVRAM. Note that the subsequent reboot will ignore all of the data. Alternatively, use NVRClear (section B.1.27, pg 160) to erase data from the cards NVRAM. Delete the provisioning files. Use NVRIPSet IPaddr (section B.1.29, pg 162) and NVRSMSet subnetMask (section B.1.31, pg 162) to set up the ELAN data. Do not use the setLeader command; it could cause node contention. Use NVRIPShow (section B.1.30, pg 162) to confirm the data. Reboot the card. Download provisioning from OTM. Reboot again. Follower corrupted. The node is slightly less effective, as fewer channels are available. No other problems are visible unless the Follower also has the D channel on it. ALL COMMANDS ARE EXECUTED ON THE FAILED CARD. Clear the current provisioning data. Use NVRClear (section B.1.27, pg 160) to erase data from the cards NVRAM. If the provisioning files are also corrupted, delete the provisioning files. Use NVRIPSet IPaddr (section B.1.29, pg 162) and NVRSMSet subnetMask (section B.1.31, pg 162) to set up the ELAN data. Use NVRIPShow (section B.1.30, pg 162) to confirm the data. Reboot the card. Download provisioning from OTM if the data had to be deleted. Reboot again.
Issue 1.5.4 05 May 03
Debugging the node
6.4
Remote node status checking

On occasion, calls to a remote node fail because the remote node is out of service, unavailable, an intervening LAN connection has failed, or other similar reasons. To investigate this type of issue, the following commands may be used. Use ping IPaddr, numPings (section B.1.32, pg 163) to verify whether the IP address is assigned. If the ping fails but the node should exist, check provisioning; the IP address may be wrong. If it is correct, check the status of the remote node. If the node is live, proceed to the next command. Use numNodesInFallbackShow (section B.1.26, pg 160) to determine whether the remote node is reachable. If, for example, the command returns an output such as:
-> numNodesInFallbackShow Nodes In Fallback = 1 44.11.223.221 value = 1 = 0x1 ->
then there is a fallback case of some sort. If ping failed and the node is live, the problem is probably in the IP network. If ping succeeded, the probability is that some other error on the card is causing the node to be out of service. Investigate on that node.
6.5
Memory fault diagnostic commands

Sometimes the memory develops problems such as loss of memory due to leaks, buffer corruption, and so forth. The following commands (in this suggested order) are useful in verifying the general sanity of the memory. Use itgMemShow (section B.1.22, pg 156) to conrm that the memory allocation is satisfactory. Typically, the majority of the buffers of a certain size should be free. Note that even an idle card has some buffers reserved for use, and therefore not idle. Use mixMemFindAll (section B.2.35, pg 193) to ensure that all the buffers are actually in the pool. A list of messages in use (and what task owns them) is provided, allowing the user to validate the buffer allocation. Use ashCongShow (section B.2.11, pg 179) to conrm the overall health of the ash memory. Failure to process the command indicates a faulty ash. Displays the cards Flash memory conguration.
If the memory is awed, it may be necessary to rebuild. Frequently, the user drops back to square one. The following sequence can be used, although it is a drastic procedure. Display the card information: itgCardShow (section B.1.20, pg 152).
Issue 1.5.4 05 May 03
Debugging the node
NVRIPShow (section B.1.30, pg 162) Displays the ELAN conguration data as stored in the NVRAM. If the data is corrupt, it may be necessary to go to drastic measures. When the card is a single node and the boot-up les (including ELAN address for OTM access) are bad, or the card is a Leader and there is a backup card that can take over, clearing the leader role is necessary rst. Otherwise, simply setting the ELAN data will sufce, provided the NVRAM (non-volatile RAM) has been cleared rst. clearLeader (section B.1.7, pg 122) If the IP data is unrecoverable, and the user must clear the leader role, this command is used. It congures the card as a Follower and saves the new provisioning in the NVRAM, removing all Leader provisioning. setLeader IPaddr,gwIPaddr,subnetMask (section B.1.39, pg 165) Congures the card as a Leader and saves it in the NVRAM.
6.6
Node commissioning commands

See also Installation and upgrades (section 12, pg 87). The following commands (in this suggested order) are useful in verifying the general sanity 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) ashCongShow (section B.2.11, pg 179) Initialize as leader: (Optional: clearLeader (section B.1.7, pg 122) or NVRClear (section B.1.27, pg 160) - card should already be clear) setLeader IPaddr,gwIPaddr,subnetMask (section B.1.39, pg 165), or for 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.
Issue 1.5.4 05 May 03
Debugging the node
6.7
Disk and directory debugging

The most common fault is a missing le or directory. To discover this, log in to the card and use cd and ls or ll to verify directory contents. The following commands are applicable when debugging the cards le system. chkdsk dev, repairLevel, entryLevelType (section B.2.4, pg 173) dosFsCongShow (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 lename (section B.2.49, pg 216), 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, pg 166)
to recover the le.
Issue 1.5.4 05 May 03
Call processing debug commands
7
7.1

Identifying the issue
For audio related issues, refer to Debugging audio issues (section 8, pg 67). Call processing may fail for a lot of different reasons. These range from compatibility issues, to provisioning issues, to resource issues, to software issues, to user error. Unfortunately, the problem rarely shows which it really is. Therefore, the debugging involved usually involves a divide and conquer analysis. As an example, until the call reaches the IPT to IP NPM, debugging at the NPM is rarely of value, unless the specic test is used to ensure that the call ow reached that point. On the other hand, since what appears to be a failure at the destination side to handle a call may really be an issue at the originating side, it should never be totally ruled out. The debugging recipe most frequently used to quickly identify at least the problem area involves checking the messaging, and when the area of the fault is found, focusing on the functional path through the software for a specic 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 other assumption requires use of the Expert Guide for that device to debug on that device. 7.2.1 Eliminate the PBX or Call Server It is a generally safe procedure to start by assuming that the origination IP Trunk node would have a quick turn-around if it fails the call. Therefore, look at the tracing of the ISDN messages on the Meridian 1, and ask the following trigger questions: 1. Did the SETUP even leave the PBX? (Conrm this; if it did not, continue debugging 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 message. i. If it indicated mandatory IE missing (96 or 0x60; if the extension bit is set, 0xE0), check to see which IE is missing.
Issue 1.5.4 05 May 03
Section: 7 Page 61
ii. If it indicated IE content error (100, 0x64, or 0xE4), check to see which IE had strange contents. iii. If it indicated no route to destination (3 or 0x83), check the provisioning for the requested number (using print_... as applicable; for example, to see the CDP provisioning type print_cdp). iv. If it indicated a failure within the IP network and IP Trunk 3.0 application via network congestion (38, 0x26, or 0xA26), switched equipment congestion (42, 0x2A, or 0xAA), or temporary failure (41, 0x29, or 0xA9), this may be an IP Trunk problem; if you can rule out the destination call server or Meridian 1, look for a failure within the IP Trunk 3.0 to remote gateway area. 3. If a CALL PROCEEDING was received before call clearing, check the remote PBX or Call Server. If it rejected the SETUP, investigate why. If the SETUP never 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 quick failure (SETUP followed by RELEASE COMPLETE) occurred, this is a strong possibility. If a SETUP was followed by a CALL PROCEEDING and then the call cleared, this may be anywhere from the local card to the remote PBX or Call Server. In that case, it may be better to skip to section 7.2.3 on page 64 rst. Note that whenever debugging a call and the messaging reaches the TSM, the command tsmChanShow [level[,channel]] (section B.1.43, pg 167) can be used to verify call data. 1. Did the call get rejected by the layer 3 task? Use the DCHmenu (section B.1.10, pg 126) command and its options to verify message ow. If the message reached the layer 3, it should generate another message into the application (a SETUP triggers a CC Setup Indication, for example). If it triggered a RELEASE COMPLETE instead, determine the fault. (Message info is probably more than adequate, although error tracing may also be useful.) If the message was sent to higher layers, disable this trace and proceed.
Issue 1.5.4 05 May 03
2. If the call reached the ISDN handlers and succeeded, or failed to reach the ATPM, the Telephony State Machine (TSM) is the key suspect. Use mixSetLogOpt module, option, level (section B.2.37, pg 195) to enable tracing. The module to trace is TSM, which has an identier value of 0. Use tsmSetTraceOption TCID,[0 or !0] (section B.2.63, pg 227) for the specic channel 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 using mixSetLogOpt module, option, level (section B.2.37, pg 195). tsmSetTraceOption TCID,[0 or !0] (section B.2.63, pg 227) does not work without the TSM module trace. To ensure the data was valid and transmitted to the TSM, check the TSM data using B.1.43 tsmChanShow [level[,channel]] on page 167. 3. If the message reached the main state machine, did it get processed for address validity? Assuming the call proceeded to the ATPM, use mixSetLogOpt module, option, level (section B.2.37, pg 195) to enable tracing address handling. The module to trace is ATPM, which has an identier value of 14. This trace allows you to determine whether the address translation protocol module even received the digits. If it did, it allows you to see whether they were accepted or rejected (and if so, why they were rejected). It may be necessary to check for fallback conditions; the ATPM will not send a call where the QOS probing forbids it to go. Disable ATPM tracing when completed. 4. If the call reached the ATPM and succeeded, but failed to reach the NPM, the Telephony State Machine (TSM) is the key suspect. Again, use mixSetLogOpt module, option, level (section B.2.37, pg 195) to enable tracing, and tsmSetTraceOption TCID,[0 or !0] (section B.2.63, pg 227) to get the details in the TSM state machine. The key question is, did the TSM send a message to the NPM? If it did, check the messaging 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 enough. Again, to ensure the data was valid and transmitted to the TSM, check the TSM data using B.1.43 tsmChanShow [level[,channel]] on page 167. 5. If the message did not reach the stack, turn on tracing. Use h323CallTrace (section B.1.14, pg 140), for the NPM messaging, and setTraceOption channel,outputLocation (section B.2.54, pg 220), for the TSM messaging, tracking on the specic 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).
Issue 1.5.4 05 May 03
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 far. If there is a gatekeeper, the call may stop after the NPM was asked to send a SETUP but before the SETUP occurred. For gatekeeper issues, refer to section 7.2.4 on page 64. Ideally, the best place to validate the ability to cross the network is to trace the message arrival at the destination. This may not be possible, if the destinations are remote. Therefore, the user may feel free to debug at the originator too. There are many ways to check messaging at this point. The most authoritative is a sniffer trace. If this is unavailable, a trace may be generated at the IP Trunk card. Note: Tracing using on-switch tools can result in output that is difcult to read. There is a threshold where the card will provide an indication about the state of message buffers (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 retry the debugging call.
Do this during off hours unless you have no choice.

Use mixSetLogOpt module, option, level (section B.2.37, pg 195) to enable tracing. (Note that you can use mixOptionOn module (section B.2.36, pg 195) to conrm that tracing has been enabled (0 is off, 1 is to TTY,...), and mixLevelOn module (section B.2.34, pg 193) to check that the trace is showing all (1) or errors only (0).) The module to trace is NPM, which has an identier value of 1. If the message reached the destination device, the best place to continue the debug process is there. If the message left the originator and did not reach the destination, check within the network. If it left the NPM but not the card, check the RADVision stack. 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 gatekeeper controlled end point. If so, the IP Trunk 3.0 node must send an ARQ (Admission ReQuest) and receive an ACF (Admission ConFirmed) rst. This is very simple to conrm. Use the gkShow (section B.1.13, pg 135) command to verify that the gatekeeper is running and registered. If this indicates not registered, you may re-attempt registration by issuing the command nmmAtpmTranTblDnld (section B.2.45, pg 203), to reload the dial plan le, and especially the gatekeeper data within it.
Issue 1.5.4 05 May 03
If gkShow still does not show registration, there is a problem in the provisioning or the network. Ensure that the IP address is correct, that the gatekeeper is live, and that the gatekeeper is supposed to support this gateway. Assuming that the gatekeeper and node are registered, an ARQ for a valid end point should succeed. It may fail in normal use for a very small number of reasons, which can be identied by the responses (ARJ - Admission ReJect - to NPM, clearing to TSM, cause code in ISDN): Remote end point has failed to register with the gatekeeper, or has lost registration (investigate the remote node). Invalid number (not provisioned on the gatekeeper). Incompatibility detected by gatekeeper (determined exclusively by the gatekeeper).
For most or all other reasons for call failure, a more detailed analysis is needed, usually by Nortel GNTS or Field Support staff, but sometimes all the way to the designer level. 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 it has to succeed at call redirection (a SETUP received, CALL PROCEEDING sent, FACILITY with the new IP address sent, and call clearing). If the redirection failed, the call failed too. Note that redirection is not mandatory. A call from an IP Trunk 3.0 node to a CSE 1000 release 2 gateway will not redirect; the remote end point does not use that capability. No ATPM handling occurs at the destination. No gatekeeper ARQ is done by the IP Trunk 3.0. The primary areas to check are the NPM, the TSM, and the ISDN layer 3. 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 use. Look for any indications of failure (such as calls not reaching the TSM). (Note: use h323CallTrace instead of mixSetLogOpt for the NPM if possible; it focuses on specic channels.) If the call reached the NPM one of two cases is true. Either this is the original, unredirected call, or the call was redirected.
Issue 1.5.4 05 May 03
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 on a follower, and accepts the call. Failure to accept the call should only occur if no channels remain available. For a redirected call, the call may fail due to codec mismatches. Unless the originator and destination can compromise on a codec algorithm (such as G.729) and a payload size (such as 30 msec), the call is rejected. If this happens, reprovision the network to make codecs compatible. If codecs are okay, the call should succeed. The messages must reach the TSM, and be passed to the ISDN layer 3. If they reach the TSM, turn off the mixSetLogOpt module, option, level monitoring and enable DCHmenu (section B.1.10, pg 126) tracing. (Message info is probably more than adequate, although error tracing may also be useful.) If the message left the DCH, it must have been rejected in some manner by the PBX. Investigate there.
Issue 1.5.4 05 May 03
Debugging audio issues
8
8.1

Echo
8.1.1 Provisioning advisory One of the design requirements for IP Trunk 3.0 was to allow the OTM application to set the echo canceller length. This made it mandatory to read the OTM le and set the cancellation length appropriately. However, in OTM the default level is 32 msec tail delay. The intended default and recommended length is 128 msec. OTM for IP Trunk 3.0 allows this value to be set to various lengths including 128 msec. It just is not the default. It is recommended that whenever echo is suspected that the service staff check this parameter in OTM and reset it to 128 msec if it is not 128 msec. Note that ITG-Trunk software versions did not use the OTM to set this value. Therefore, this specic issue could not occur. 8.1.2 The echo checklist This is being discussed as a step by step procedure for data collection and analysis. The procedure involves querying the end user who experienced the problem for details. The steps are: 1. Is the tail length set to 128 msec in OTM? If not, does the problem remain after 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 a sentence 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?
Issue 1.5.4 05 May 03
Section: 8 Page 67
If the call is transferred to another set type (analog, digital), does the echo still appear? What happens to the echo when the receiver of the call unplugs the handset? 4. Is it one user or many users? If one user, list any specic characteristics of the voice. 5. Call scenario with network diagram - capture exact call ow for the scenarios that report echo, i.e. the path including the interim hops between the originating and terminating 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 calls? 6. Collect other symptoms. This is anything out of the ordinary such as bad quality of sound, bug messages, call drops, one-way speech... 7. Check clocking status. This may be needed on both the Meridian 1 and a CSE server, as echo can be caused at any point in the call; all should be conrmed. Load 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 n Locked to primary reference listed for n (if n > 0). On large system similar commands from ld 60 can be used to check clock status. Also, check the log for slippage messages:
DTA0028 <loop> DTA0026 <loop>
Use the following command sequence on a large system to lock the clock to the appropriate 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 cabinet containing the IP daughterboard currently locked to the primary reference. If set to free run, conrm that the network is isolated (i.e. there is no connection to PSTN). If two switches are in the private network then one side has clock controller set to FREE RUN and the clock on the other switch is locked to the Primary Reference. The clock that is in FREE RUN in an isolated network behaves like a Central Ofce for that Network.
Issue 1.5.4 05 May 03
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 call server requires the following patches: MPLR17320 only for customers other than North America MPLR17320+MPLR17313 for North America 10. Check the codec conguration 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 more SMC 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 on the CSE1K 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 table 15. NTP number: 553-3023-102 Prompt 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 installed or the same changes get submitted to Project 26 stream. 16. If the echo can be duplicated, check DSP settings on the host during call setup.
Issue 1.5.4 05 May 03
Type XspySetLevel 0,2 from the vxWorks prompt on IPL cards. Look at gain settings rst:
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 on the CS 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 scenario, then check overlay 14 TIMP & BIMP prompts. Characteristic impedance of the analog trunks may not have been provisioned correctly. 18. Check Table 1 from the loss plan NTP, if PRI is involved. The NTP number and name: 553-2201-181, Meridian 1 International Loss and Level Plan, Planning and engineering. Table 3: Table 1 default values for NA customers:
Prompt
REQ TYPE FEAT PDCA TNLS DTI/PRI ONP DSET OPX DTT SDTT DCO DTO VNL SATT ACO ATO PRI PRI2 PDCA 6 6 6 0 3 3 0 6 6 6 6 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Entered value (Tx)

prt dti pad 1
Entered value (Rx)
Issue 1.5.4 05 May 03
Table 3: Table 1 default values for NA customers:

Prompt
XUT XEM BRIL BRIT WRLS 6 3 0 0 0
Entered value (Tx)

0 0 0 0 0
Entered value (Rx)
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 rst 32 words.

001A95A8 : 001A7673 00000200 00000008 00000000 001A95B0 : 00000000 00000000 00000016 00000000 001A95B8 : 00000000 00000000 00000000 00000000 001A95C0 : 00000000 00000000 00000000 00000000 0000EAD0 00000000 00000000 00000000 00002000 00000000 000003000 00000000 00000001 00000001 00000000 00000000 00000000 00000000 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 not be set for IP sets or VGWs or analog trunks. In order to check the pad values received by the VGMCs (IPL application) it is possible to turn on syslog messages for tVGW task and look for pad messages. 20. There may be another point worth checking in case it was a new installation, or the customer happened not to have congured any digital trunks on their system already. In this case it is necessary to go to LD73 and manually create Digital Data Block (DDB) rst. It will create tables 1 and 15 automatically. Otherwise, there will be no table 15 on the system and each call involving DSP resources will cause 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 any effect?
Issue 1.5.4 05 May 03
Debugging audio issues -> DsetSideToneEnable = 0 (resets to 1 on card reboot)
22. If the echo is happening mainly with long distance calls, make a call using a calling card 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 include h323SessionShow (section B.1.15, pg 143), and iptSessionShow [level] (section B.1.19, pg 150). Confirm that the TSM agrees. Useful commands include tsmChanShow [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. Useful commands are: dimPrintChannelInfo TCID (section B.2.7, pg 176) to confirm the 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), and the assorted tsm_stat_req commands (section B.2.64, pg 228) to investigate further. Confirm that the TSM is actually requesting the right actions from the DSP. Useful commands include mixSetLogOpt module, option, level (section B.2.37, pg 195), and h323CallTrace (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. Useful commands are: dimPrintChannelInfo TCID (section B.2.7, pg 176) to confirm the 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), and the assorted tsm_stat_req commands (section B.2.64, pg 228) to investigate further. Confirm that the TSM is actually requesting the right actions from the DSP. Useful commands include mixSetLogOpt module, option, level (section B.2.37, pg 195), and h323CallTrace (section B.1.14, pg 140).
Issue 1.5.4 05 May 03
Check that we are not in fax mode for a voice call. Fax tone can briefly cause a loss of speech path, but the call recovers once the card determines that it was not really fax. However, during the interim, there is no speech path. If this is the case, consider relocating any fax or modem devices from close to the user who suffered the fax switch-over. Assuming that the session is available, the tracing must be at the DSP level. Although the commands applicable have been made available for the user, there are too many variables (card types and releases, IP Trunk software application vintages, DSP loads, etc.) to make it practical for rst line support to directly use them. Unless the user has had experience with these commands as directed by Nortel personnel (GNTS, for 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 performance characteristics when a call completes one or more of the tsm_stat_req commands (section B.2.64, pg 228) to capture performance characteristics mid-call. The first two are the most useful, but all 5 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. It includes most information, although the quantity of data may be awkward for 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 configuration data and current values used TsmDspStat = 1/0 (section B.2.62, pg 226) to capture performance characteristics when a call completes one or more of the tsm_stat_req commands (section B.2.64, pg 228) to capture performance characteristics mid-call. The first two are the most useful, but all 5 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. It includes most information, although the quantity of data may be awkward for a person not specializing in the data stream.
Issue 1.5.4 05 May 03
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, pg 236) tsm_stat_req_vp_delay TCID or reqVpDelay TCID (section B.2.64.5, pg 238)
Issue 1.5.4 05 May 03
BIOS / BootROM functionality
9
9.1

Overview
Note: The minimum ITG-P rmware release for IP Trunk 3.0 is 5.7. The minimum release 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 to use BIOS (Pentium) and BootROM (Media Card) capabilities can be critically important. The Pentium cards boot using the cards BIOS code. The Media Card boots using the BootROM code. During the boot sequence of the Pentium or a Media Card running version 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 printed, Enter jkl to force boot from BootROM vxWorks prompt.. Typing jkl at that point causes the card to load the ROMd version of VxWorks (see below). The IP Trunk application is not loaded, so commands implemented in the IP Trunk code are not available, but the basic VxWorks commands can be used to look at the /C: drive, etc.
Figure 3 Aborting the boot procedure to log in from BIOS (Pentium example)
ITG Firmware Rls 4.0 8051XA Firmware Ver 9.0(Pentium) 9th June 1999 (C) Nortel Networks Inc., 1996-1999 32K External RAM detected All FPGAs are configured No dongle detected 8K DPRAM detected Bank 0 Checksum - AFBEH Suspend Power Signals O.K. Pentium(R) II Processor. Jumping to vxWorks... ZYXWVUR Memory Test Completed OK
L2 Cache Enabled
BIOS ROM Pentium (PC BIOS) Version 1.2 Copyright: Nortel Inc., 1999-2000 Memory Config: 08080808 Memory Size: 0x04000000 PCI Chipset Init Done Enter jkl to force boot from BIOS ROM Booting from BIOS ROM Loading code from address: FFF80000
Enter jkl now
Issue 1.5.4 05 May 03
Section: 9 Page 75
Figure 4 Aborting the boot procedure to log in from BootROM (Media Card example)
MC Firmware Rls 6.4 8051XA Firmware Version 4.8 26 May 2002 (C) Nortel Inc. 2001 EPLD Version: 3.0 32K External RAM detected 8K DPRAM detected All FPGAs are configured No dongle detected Bank 0 Checksum - A6FBH SRAM test okay SDRAM Addr test okay SDRAM blank over Early serial debug initialized
VxWorks System Boot
Copyright 1984-1998
Wind River Systems, Inc.
BSP version 5.0: BootROM 5.0 CPU: IXP1200 Version: 5.4 BSP version: 5.0 Creation date: Nov 22 2001, 18:21:11 Enter jkl now
Enter jkl to force boot to BootROM vxWorks prompt jkl Uncompressing Default vxWorks image .... Complete
Issue 1.5.4 05 May 03
Jumping to 0x1000 Early serial debug initialized Setting tLogTask priority to 150 Found device : Cirrus CL-PD672x cisGet : pcCard recognized 0x3affe64 (tRootTask): PC Card Detected: Socket 0 PC Card Detected: Socket 1 cisGet : pcCard recognized ipMethodInit, gIPMethod = 2 IP Address from NVRAM: 47.11.217.55 IP Data in NVRAM Valid, Boot Line updated IP Address:47.11.217.55 Gateway Address:47.11.217.1 Subnet Mask::fffffe00 Host Name: bootHost Target Name: vxTarget User: target MAC Address for Port 0 is : 00:60:38:bd:fb:31 Initializing Semaphore SysConf: uEng_intConnect to pktHandlingIsr. 0 symbols bound. Load uCode from buffer Status : Return Success Starting Microengines. 0x3affe64 (tRootTask): Loading MAC_21440... 0x3affe64 (tRootTask): mac21440Load: Init String[0] NULL: ixpMac 0x3affe64 (tRootTask): Loading MAC_21440... 0x3affe64 (tRootTask): MAC 21440 String : Processed all arugments 0x3affe64 (tRootTask): mac21440InitMem: Net Pool ID is 53208496 0x3affe64 (tRootTask): Done loading mac21440... 0x3affe64 (tRootTask): mac21440Start: Starting port 0 interrupt: ixpMac0 carrier up interrupt: ixpMac1 carrier up 0x3affe64 (tRootTask): TLAN set to 10BaseT Operation 0x3affe64 (tRootTask): TLAN set to Half Duplex Operation 0x3affe64 (tRootTask): ELAN set to 10BaseT Operation 0x3affe64 (tRootTask): ELAN set to Half Duplex Operation interrupt: ixpMac0 carrier down interrupt: ixpMac0 carrier up
Issue 1.5.4 05 May 03
MAC Address for Port 1 is : 00:60:38:bd:fb:32 0x3affe64 (tRootTask): Loading MAC_21440... 0x3affe64 (tRootTask): mac21440Load: Init String[0] NULL: ixpMac 0x3affe64 (tRootTask): Loading MAC_21440... 0x3affe64 (tRootTask): MAC 21440 String : Processed all arugments 0x3affe64 (tRootTask): mac21440InitMem: Net Pool ID is 52108908 0x3affe64 (tRootTask): Done loading mac21440... 0x3affe64 (tRootTask): mac21440Start: Starting port 1 0x3affe64 (tRootTask): TLAN set to 10BaseT Operation 0x3affe64 (tRootTask): TLAN set to Half Duplex Operation 0x3affe64 (tRootTask): ELAN set to 10BaseT Operation 0x3affe64 (tRootTask): ELAN set to Half Duplex Operation interrupt: ixpMac1 carrier down interrupt: ixpMac1 carrier up Attached TCP/IP interface to ixpMac unit 1 Attaching network interface lo0... done. 0x3affe64 (tRootTask): WARNING: mac21440MCastAddrAdd called. addr=0x3aff558 NFS 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.
->
This can be useful when a problem on the card prevents the application from fully booting. Examining the state of the NVRAM or /C: drive conguration les may provide clues as to why the application isnt booting.
Issue 1.5.4 05 May 03
9.2
Accessing the /C: drive le system

For IP Trunk 3.0 on the Pentium card, the card boots into the BIOS before the /C: driver Flash le system is mounted. This is not the case for the Media Card. The le system must be initialized and mounted before any of the le system commands can be used. To check if the le system is available, use the command devs. Notice that the BIOS prompt in IP Trunk 3.0 for the Media Card is -> instead of BIOS.
BIOS> devs drv name 0 /null 1 /tyCo/0 1 /tyCo/1 5 host: 6 /pty/telnet.S 7 /pty/telnet.M value = 25 = 0x19
The Pentium card may or may not have the /C: drive mounted; the Media Card will mount the drive without user intervention. Therefore, un-mounted /C: drives are a Pentium specic issue. If the entry /C: isnt shown when the devs command is issued, then the /C: drive isnt mounted. To mount it, enter the command dosFsCdriveTffsDrv then cd to the drive. Commands like dosFsCongShow will then work as demonstrated below:
BIOS> dosFsConfigShow Not 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 system value = 57 = 0x39 = '9' BIOS> cd /C: value = 0 = 0x0 BIOS> dosFsConfigShow device name: /C: total number of sectors: 7695 bytes per sector: 512 media byte: 0xf8 # of sectors per cluster: 4 # of reserved sectors: 1 # of FAT tables: 2 # of sectors per FAT: 6 max # of root dir entries: 240 # of hidden sectors: 1 removable medium: false disk change w/out warning: not enabled auto-sync mode: not enabled long file names: not enabled exportable file system: not enabled lowercase-only filenames: not enabled volume mode: O_RDWR (read/write)
Issue 1.5.4 05 May 03

2854912 bytes 1935360 bytes
available space: max avail. contig space: value = 0 = 0x0 BIOS>
It can also be useful to go into the /C:/CONFIG directory and view the contents of the CONFIG1.INI and BOOTP.1 les via the copy command.
9.3
Viewing NVRAM contents

Some card bootup problems are caused by invalid data in the NVRAM. To view the contents from the BIOS, use the command NVRIPShow.
-> NVRIPShow IP Address from NVRAM: 47.11.217.54 IP address : 47.11.217.54 Gateway : 47.11.216.1 Subnet Mask: 255.255.254.0 Set 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 eld upgradeable.

Users are required to upgrade to Media Card Firmware Release 6.4 and it is recommended that they upgrade to Media Card Firmware Release 6.5. However, although cards with MC release 6.5 are being shipped with SMC BIOS 5.2, users with BIOS version 5.0 do not need to upgrade. At boot time, the system prints a line indicating the BSP version. This indicates the BIOS 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
Issue 1.5.4 05 May 03
9.5
BIOS / BootROM Commands

Most of the low-level VxWorks commands are available at the BIOS prompt, plus some IP Trunk application or card specic commands. The following is a partial list. Use the lkup command to verify if a command you need is available. For command details of all IP Trunk specic commands, refer to the appropriate appendix. 1. Set the Network connection in the ELAN interface port. If the leader information has been corrupted, the card can be revived from BIOS or 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 only For 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 as setLeader command. c. Pentium card only For the Pentium card, there is an alternate procedure parallelling the Media Card, listed 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 same as setLeader command. 2. Disk commands
Issue 1.5.4 05 May 03
If the disk is seriously corrupted, you can reformat the drive and then download fresh 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 corruption) may 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 directory /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, the command would be:
-> swCopy /A:/IPT30052.p2
Note that commands used for the A: drive check the le format, CRC checksum and le 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
Issue 1.5.4 05 May 03
lkup upgradeErase reboot
Issue 1.5.4 05 May 03
Maintenance Task (Task Monitor Function)
10 Maintenance Task (Task Monitor Function)

The tMonTask introduced in Release 2.x.26 software running in the system monitors all 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 stack information will be dumped to the current log le and the card will be immediately rebooted. Non-Critical tasks are those which do not impact basic call processing. If noncritical tasks are suspended or disappear, register and stack information is dumped to the current log le and the card is scheduled for automatic reboot in the next precongured service window (e.g.: 2:00 am). The reason for delaying recovery of non-critical tasks is simple. If such a task is suspended or disappears, some services may be degraded and/or un-supported but there is no impact to basic call processing. Missing non-Critical tasks (that is, a noncritical task that had never been spawned on this card) will not trigger card reboot.
10.1
audit.ini le
This le contains control information for the Audit/Maintenance task including Reboot Parameters and the Critical Task List. It survives system reboot so Maintenance Task operation setting will remain consistence across reboot. This le is maintained and updated by the Monitor task, and should not be modied manually. If the audit.ini le becomes corrupted, delete it and reboot the system. The Monitor task will rebuild the le from scratch with default settings. The following is a sample audit.ini le that species Disabled auto-reboot Suspended non-critical task reboot time is 2:00am Total of 18 tasks are identied as Critical Tasks.
-> copy < audit.ini [Reboot Parameters] RebtOps=0 RebtTOD=2:0 RebtTPR=5 [Critical Tasks List] TaskList1=tExcTask tNetTask tTelnetd tFtpdTask tShell tBootpdTask tMAM tRmm tNpm baseMMintTask tA07 tNMMTask tMVX_DIM tATPM tIpss tTSM tMcciMsgMgr tRCM TaskList2=;
Section: 10 Page 84
Issue 1.5.4 05 May 03
Maintenance Task (Task Monitor Function)
10.2
audit.his history le
The le /C:/LOG/audit.his contains a history of Audit/Maintenance task activity. Each record contains a record index, log time, record id, name of the task experiencing a problem and a short description of the problem. The le is a xed size (4096 bytes), and when it is full, new records will overwrite the oldest ones in the le. 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 whether a task is critical or non-critical, and may want to enable or disable the reboot procedure. The auditShow (section B.1.3, pg 121) command allows the user to determine the current status. Is reboot enabled? For non-critical tasks, when does the card reboot? And which tasks are critical or non-critical? Sometimes, when debugging an issue requires access to the memory at the time of the fault the user may choose to block the reboot. The auditRebootSet 0/1 (section B.1.1, pg 120) command allows the user to set the reboot status. This is followed by a full printout of the information as though the auditShow command was issued. The trafc shape of a node varies from the shape on another node, often by large amounts. As a result, the non-critical task reboot time for one site may be unsatisfactory at another. The auditRebootTimeSet hh:mm (section B.1.2, pg 120) command allows the user to set the non-critical task reboot time. This is followed by a full printout of the information as though the auditShow command was issued. Different sites may use different capabilities. This may make some tasks more important than on the average site, or make a task normally agged as critical less important. The auditTaskSet [tname|tid],level (section B.1.4, pg 121) command allows the user to dene which tasks are the critical and non-critical tasks. This is followed by a full printout of the information as though the auditShow command was issued.
Issue 1.5.4 05 May 03
Patcher Tool Support
11 Patcher Tool Support

The new Patcher utility introduced in Release 2.x.26 software allows software modication in the eld for many problems without any interruption in service. Note that it may not be available for all problems, based on technical limitations dealing with data structure denitions. The patcher tool uses the same interface as the M1 CPP patcher tool and is available on both the Pentium and SA platforms. The tool builds a patch le which is then loaded and put into service on a running system, replacing an existing function with a new one without requiring a software reload. Memory patches can be created by Nortel support personnel in the Unix environment or on the switch, although the patch should never be created on a customer switch. Source code patches are created using the build environment for a given software version. The Unix patch creation tool is then used to extract the patch from the source code modication. The patch le contains control information about the patch, the memory addresses to be patched, and the patch object code itself. It should only be loaded on a switch running the release of software for which it was created. Aggregate patches can be created by merging multiple individual patches. The resulting le contains multiple patch elements which can be loaded and activated as a unit. Aggregate patching is useful when there are various inter-dependent patch elements that must be activated simultaneously. Patch les should be located in the /C:/U/PATCH/ directory on the card. The retention le 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 the res retention level. Patches are reloaded during the system startup sequence, after the VxWorks kernel bootup nishes but before the application starts.
11.1
On Switch Patch Tool CLI Commands

The patcher commands are executed either from CLI or under vxWorksShell level. 1. pload Loads a patch le from C: drive into memory. 2. pout 3. pins 4. poos 5. pstat 6. plis Remove a patch from memory. Activate a ploaded patch, put it in-service. Deactivate an in-service patch, take it out-of-service. Display summary status of all loaded patches. Gives detailed information about one patch in the system.
Section: 11 Page 86
Issue 1.5.4 05 May 03
Installation and upgrades
12 Installation and upgrades

12.1 Installation Overview
The NTP describes the commands and process for installing a new card. In general, the procedure is: 1. Setup the ELANs subnet mask, IP address and gateway IP address, set the Leader ag and a ag to get data from a local BOOTP table in the NVRAM of the Nodes Leader 0 card. This enables the ELAN interface to be used by MAT/OTM for downloads or from the BIOS/VxWorks shell CLI for le transfers. This only needs to be done for the Leader - all of the remaining cards in the node retrieve their IP data from the Leader 0 via the BOOTP request/response mechanism. This step (and step 2) requires you to connect a terminal directly to the Leader 0 card, either through 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 Node properties are downloaded in the BOOTP.1 le. The Card properties are downloaded in the CONFIG1.INI le. 12.1.1 FTP server and le transfer options Normally, the application S/W and conguration les can be downloaded from the MAT/OTM PC. However, in some support situations, it may be difcult or impossible to access the MAT/OTM PC and initiate the download. The SMC and ITG-P dont support PPP, so you need to have either a PC card in the faceplate or have access to a device on the ELAN from which to provide a new load or update the conguration les. One option is to create a directory on the M1 CPUs drive (e.g. c:/u/itg) and put the les in it. You could either remotely PPP the les through the M1 to it or use FTP to copy the les to it when you have access to the MAT/OTM PC. You can then direct the swDownload function to that directory for the S/W upgrade. Likewise, you can FTP the CONFIG1.INI and BOOTP.1 les to the cards from it. If you use the M1s drive, care must be taken that the les do not cause the disk to become full, thus impacting the M1s operation. Useful commands for transferring the les are: swDownload srvrIP, uid, passwd, path, fname (section B.1.41, pg 166) FTPs the application to the card.
Issue 1.5.4 05 May 03
Section: 12 Page 87
12.1.2 Setting NVRAM parameters from the CLI The necessary NVRAM parameters for the Leader 0 card can be set using the command setLeader IPaddr,gwIPaddr,subnetMask (section B.1.39, pg 165) from the ITGs CLI. This works in the case where you are installing a card that already has a load of S/W on it. When the card boots up, press +++ when the .... are printing during the BOOTP query time. The card will then load the existing application load. Login and enter the command. 12.1.3 Setting NVRAM parameters from the BIOS / BootROM If theres a situation where the application on the card is corrupted or not present (e.g. the card rebooted just after the upgradeErase command was executed), you can setup the ELAN IP data from the BIOS using the following command sequence. 12.1.3.1 IPT-P, SMC with BIOS version 5.0 1. Congure the ELAN interfaces 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 ag.

BIOS> nvramLeaderSet
3. Set the ag so data is read from the local BOOTP.1 le instead of doing a BOOTP query.
BIOS> lnIsaIPMethodSet 2
4. Conrm everything was programmed correctly.

BIOS> NVRIPShow IP Address from NVRAM: 47.11.217.54 IP address : 47.11.217.54 Gateway : 47.11.216.1 Subnet Mask: 255.255.254.0 Set as Leader. Set to use IP address parameters in NVRAM. value = 43 = 0x2b = + BIOS>
12.1.3.2 SMC Use setLeader (documented under setLeader IPaddr,gwIPaddr,subnetMask (section B.1.39, pg 165), but in reality a function appended to the base), or: 1. Congure the ELAN interfaces IP data in NVRAM:
Issue 1.5.4 05 May 03

-> 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 ag.

-> nvramLeaderSet
3. Set the ag so data is read from the local BOOTP.1 le instead of doing a BOOTP query.
-> ixpMac1_IPMethodSet 2
4. Conrm everything was programmed correctly.

-> NVRIPShow IP Address from NVRAM: 47.11.217.54 IP address : 47.11.217.54 Gateway : 47.11.216.1 Subnet Mask: 255.255.254.0 Set 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 function (synchronize > transmit > card software). However, they can be initiated from the ITGs CLIs if the situation requires. Although the commands are different depending on whether they are carried out from the 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 version of software is removed from the card. Normally the card saves the current software load when a new one is downloaded from MAT/OTM. If the new load fails to bootup, the old load is used. But this increases the card bootup time because the checksum must be calculated for both binaries. Erasing the Flash speeds up the reboot 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 FTPs the software from the server. 5. Reboot the card to activate the new load.
Issue 1.5.4 05 May 03
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). Youll need to know the IP address of the server, the lename and path. If FTPing the le from the MAT/OTM PC, open the transmit dialogue (synchronize > transmit), check the card software box, browse to the le to be downloaded and click Open. Leave the transmit dialogue open, the FTP server will be ready for the FTP request from the card. 3. If necessary, congure the ELAN IP data by entering the command setLeader 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 the upgradeErase command but before a download is completed), when there is some other application on the card, or when there is a problem preventing the card from coming up using the application image stored in Flash, you can boot into the BIOS and download a new version of software from there. 1. Erase the program store area (upgradeErase (section B.2.66, pg 240)). 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 ITGs IP data hasnt been congured before. 4. Initiate the S/W download. The syntax varies depending on the location of the le. 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 ITGs /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, you can use the ping command to debug the access (same syntax in section B.1.32). You can also FTP les to the card. Follow the instructions in section 9.2 to initialize the ITGs le system and cd to the drive. After that, you can FTP les to and from it.
Issue 1.5.4 05 May 03
12.2.3 Software upgrades from the BootROM In the case where there is no application on the card (e.g. card reboots after the upgradeErase command but before a download is completed), when there is some other application on the card, or when there is a problem preventing the card from coming up using the application image stored in /C:/, you can boot into the BootROM and download a new version of software from there. 1. Erase the program store area (upgradeErase (section B.2.66, pg 240)). 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 ITGs IP data hasnt been congured before. 4. Initiate the S/W download. The syntax varies depending on the location of the le. 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 ITGs /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, you can use the ping command to debug the access (same syntax in section B.1.32). You can also FTP les to the card. Follow the instructions in section 9.2 to initialize the ITGs le system and cd to the drive. After that, you can FTP les to and from it. 12.2.4 FTP upgrade on SMC The application code is loaded from a le on the /C:/ drive for SMC and not burnt into ash as for ITG-P. Because of this we can directly ftp the application le to the /C:/ drive. To do this you must rst remove the le protection on the /C:/exec le (see attrib lename,protection (section B.2.3, pg 172)) and then copy the application le onto the /C:/ drive and renaming it /C:/exec.
Issue 1.5.4 05 May 03
12.2.5 SMC BIOS Upgrade The SMC BIOS is not eld upgradeable. If the BIOS requires upgrade, contact Nortel Networks to have it upgraded. Upgrade is superuous if the BIOS is version 5.0 or higher. Firmware versions 6.4 and 6.5 will both work on BSP (BIOS) version 5.0 or 5.2. (Version 5.1 was an internal issue not released to the eld.)
12.3
Transmit Node and Card Properties

The Node and Card properties must be downloaded from OTM to the new card. The Node properties le (BOOTP.1) is used by Leader 0 to congure its own TLAN IP address and all the IP address information on the other cards in its node (see section A.4). MAT/OTM downloads the le to Leader 0, which FTPs a copy of the le to the currently registered Followers. The Card properties (CONFIG1.INI) is used by each card to congure the codecs, etc. (see section A.2). A card gets its TLAN IP address from the BOOTP.1 (usually indirectly via a BOOTP response). Certain parts (like the codec parameters) can be changed without rebooting the card. However, the card must be rebooted to read CONFIG1.INI le and process all changes which may have been made. So if at all possible, just reboot the card.
Issue 1.5.4 05 May 03
VxWorks Startup Script Support
13 VxWorks Startup Script Support

During the card bootup sequence, a built-in VxWorks function can read and execute a startup script before the trunk application starts. This script can contain debugging commands for execution on laboratory or customer switches. The startup script should be used with caution, and only for debug support or for work-around solutions for problems not otherwise correctable. The le is in /C:/etc/startup on the card. It can contain any valid VxWorks shell and CLI commands, but the results may be overridden during software startup. For example, the startup le may initialize a global variable to one value, but it may be overridden with a different value during software initialization. In such cases, it is better to use the patch function as described in the previous section.
Issue 1.5.4 05 May 03
Section: 13 Page 93
Exception Trace Decoding
14 Exception Trace Decoding

The ITGT and IP Trunk 3.0 application software includes an exception handler to process fatal software problems (such as divide by zero or invalid memory accesses). This handler outputs information about the error, the current status of the card CPUs registers and the stack for the task executing at the time of the exception. The information is output to the console and the CURRLOG.1 le. If the error is determined to be fatal, the card is automatically rebooted. If an exception condition arises, the card will dump data detailing the nature and route cause of the exception to the CLI output and to the CURRLOG.1 le. The Pentium card has two maximum error counters for exception handling. The rst will allow a maximum number of exceptions (xed at 5) in a 1 hour period above which the card will auto-reboot. The second will auto-reboot if the card reaches a maximum allowable exception count condition (total of 20 exceptions). This maximum error count is not time dependent. Notication of which exception counter has overowed is detailed in the output dump. Two new CLI commands have been included to allow interrogation of the exception status of the card: itgExcpCountShow - Pentium card only (section B.2.19, pg 185) Details the count for both the number of exceptions in the last hour and the total number of exceptions since the last boot-up. itgExcpCountClear - Pentium card only (section B.2.18, pg 185) Clears the count for both the number of exceptions in the last hour and the total number of exceptions since the last boot-up.
An example of the output from the exception handler is as follows:

ITG Exception Handler Exception: 14 Task : tSyslogd (01881bd0) Program Counter: 0012ad20 Status Register: 00010202 Error Code : 00000002 Valid Flag : 00000003 Address (CR2) : 55040044 x86 registers: edi = 00000000 esi ebp = 01881660 esp ebx = 55040044 edx ecx = 00000004 eax eflags = 00000002 pc = 0012ad20
= = = =
00000000 01881650 00000004 00000002
Stack dump (in hex):
Section: 14 Page 94
Issue 1.5.4 05 May 03
Exception Trace Decoding

01881650: 01881670: 01881690: 018816b0: 018816d0: 018816f0: 01881710: 01881730: 01881750: 01881770: 01881790: 018817b0: 018817d0: 018817f0: 01881810: 01881830: 01881850: 01881870: 01881890: 018818b0: 55040044 55040044 55040044 5b840044 00000000 002d151c 00000048 ffffffff 00000f05 003d7d8c 0032165f 00000013 01fbcb20 00000000 013c2e80 00000004 013c2e80 018818ac 00000076 002c93ec 018816d0 00000004 00000004 018816d0 018816ec 003d7d8c 0000001d 000036c1 013c3480 00000f05 003da6c0 018817e8 01fbcc94 013c2e80 013c2e80 013c2e80 00000000 0011bf7e 00000000 01f9b7e4 00000000 003b8188 5b840000 00000004 002d1163 00001000 00000000 003d7d8c 00000000 013c3480 018817e8 01f94458 00000000 00000ec4 01f94458 01f9b7e4 01881870 01f9b7e4 00000000 00000002 00000002 00000004 003d7d8c 00000001 003d7d8c 00000000 01881744 000036c3 00000ec8 018817e8 018817e8 01f94d14 018817fc 01881820 01f9b7e4 01881858 0011bc1e 00000002 01c3eed8 00000000 01881680 018816a4 00000000 000036c2 00001000 001d9040 002d1266 00000039 003da6c0 003da6c0 01f94d14 013c2e80 002ca99d 0011d2ff 0188183c 0011b461 01f9b7e4 00000000 000004f3 0000006a

0012b6d1 00113dfb 018816d4 003d7d8c 00000000 003d7d8c 003d7d8c 01881768 013c3480 018817e8 00000000 00000000 01fbcb20 01f94d14 001182bd 01f94458 00000000 01881924 00070030 0000006b 003b8188 003b8188 002d112c 00200000 00000001 003d7dec 00000f05 002d1858 0188178c 00000004 018817fc 0031f658 00000000 00000ec4 01f94458 000003ac 01f9b7e4 01c3eed8 01881de0 018818dc 018816d0 018816d0 003d7dec 00000000 0188171c 00000120 000036c3 003d7d8c 00321052 018817a8 002d2289 0031f6f4 00000003 00000004 00000ec4 00000001 00000002 01b90994 018818c8 002d2978
If an exception occurs, the syslog, containing the exception handler output should be forwarded to Technology via the Global Customer Care Services staff.
Issue 1.5.4 05 May 03
Section: 14 Page 95
Formatting the /C: Drive
15 Formatting the /C: Drive

15.1 Warning
Never reformat a PCMCIA software delivery card to be used in an ITG card (ITG-P or SMC) on a PC running Windows 2000. If you do, you have all but permanently lost the card for use in ITG-P or SMC cards. The time and effort to revive it, and the complexity of the procedure which involves manually modifying sectors of the card not allowed as direct access, makes recovery more expensive then buying a new one. If you wish to delete les, 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-P or SMC (reformatAdrive). That would make it usable for only one card type. Again, use 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 les from the card. The output of the command dosFsCongShow (section B.1.11, pg 134) indicates the drive is full when it shouldnt be.
Note: The chkdsk command should be used to conrm /C: drive corruption before the actions are taken to reformat the drive. It is recommended that the /C: drive be reformatted if the application is loaded on a card 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 le descriptors. When this happens, you cannot access the /A: or /C: drive and it may appear to be /C: drive corruption. Enter the command iosFdShow (section B.2.16, pg 184) to check for this condition. Less than 50 le descriptors should print. But if there are a lot more than that, the card may have run out. Capture the output. Then manually free some of the descriptors named socket using the command close with the le descriptor number (start with the highest numbered sockets). If you can then access the /C: drive, that was the problem. Forward all captured logs to the technology team for investigation.
Section: 15 Page 96
Issue 1.5.4 05 May 03
15.4
Using chkdsk to Identify Corruption

It may be necessary to run the chkdsk dev, repairLevel, entryLevelType (section B.2.4, pg 173) command when investigating possible /C: drive corruption. Normally, the command is rst run to look for corruption, using the format chkdsk /C:, 0,0. It will check the disk and print a report of the results. If corruption is reported, the command can be run again to clean it up. This allows more information to be collected and passed back to the technology group. The following are some examples. The rst is a clean run: no disk corruption is found (bad allocation units = 0) and no error message is printed.
-> chkdsk /C:,0,0 Copyright (c) 1993-1996 RST Software Industries Ltd. Israel. All rights reserved ver: 2.6 FCS Disk Check In Progress ...
total disk space (bytes) : bytes in each allocation unit : total allocation units on disk : bad allocation units : available bytes on disk : available clusters on disk : maximum available contiguous chain (bytes) : available space fragmentation (%) : clusters allocated : Done Checking Disk. value = 0 = 0x0
3,923,968 2,048 1,916 0 2,658,304 1,298 2,654,208 1 618
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) : bytes in each allocation unit : total allocation units on disk : bad allocation units : 3,923,968 2,048 1,916 0
Issue 1.5.4 05 May 03
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,023 Done Checking Disk.
15.5
Formatting the /C: Drive on Pentium platform

If disk corruption is found by the chkdsk utility, the drive requires reformatting to recover. This procedure will erase the rst sector on the /C: drive; when the card reboots, the TFFS software formats the drive. After reformatting the drive, the conguration les must be downloaded from OTM. from BIOS: reformatCdrive
BIOS> reformatCdrive
from the VxWorks shell: reformatCdrive

ITG> reformatCDrive
On reboot the /C: drive will be fully reformatted with the following messages displayed:
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. NVRAM settings and the binary stored on the Flash memory are not affected by reformatting the /C: drive.
Issue 1.5.4 05 May 03
15.6
Recovering the /C: Drive on Media Card platform
Formatting the card will remove all software. Be sure to have software available to reload.
To format a PC Card on a Media Card, rst boot to the BootROM vxWorks prompt. Two options are available for the SMC card. At this prompt the support person may use the command formatAtaCard: -> formatAtaCard Slot Number: 0 for faceplate, 1 for internal slot. Alternatively, the procedure used for the Pentium card applies. from BIOS: reformatCdrive
BIOS> reformatCdrive
from the VxWorks shell: reformatCdrive

ITG> reformatCDrive
On reboot the /C: drive will be fully reformatted with the following messages displayed:
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. NVRAM settings and the binary stored on the Flash memory are not affected by reformatting the /C: drive.
Issue 1.5.4 05 May 03
Card Startup Log Messages
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 IPT xxxxx. The card was rebooted while enabled. See the next section for the Follower BOOTP messages.
ITG Firmware Rls 4.0 8051XA Firmware Ver 9.0(Pentium) 9th June 1999 (C) Nortel Networks Inc., 1996-1999 32K External RAM detected All FPGAs are configured No dongle detected 8K DPRAM detected Bank 0 Checksum - AFBEH Suspend Power Signals O.K. Pentium(R) II Processor. Jumping to vxWorks... ZYXWVUR Memory Test Completed OK
L2 Cache Enabled
BIOS ROM Pentium (PC BIOS) Version 1.2 Copyright: Nortel Inc., 1999-2000 Memory Config: 08080808 Memory Size: 0x04000000 PCI Chipset Init Done Enter jkl to force boot from BIOS ROM 00000015 Flash Size: 0x00400000 11 0xF8500000 00 0xF9800000 11 0xF9900000 00 0xF9A00000 11 0xF9B00000 Cookie array value: 0x11001100
5 second window to enter jkl for booting into BIOS Amount of Flash memory on card (4 Meg 16 bit words = 8 Meg)
Checksum Validation at Bank Address: 0xF9800000 Checksum in ROM = 1338FDD2 Length of bank = 00138DC0 Checksum identifies version Calculated Checksum = 1338FDD2 Checksum Validation at Bank Address: 0xF9A00000 Checksum in ROM = 569B458B Length of bank = 00139630 Calculated Checksum = 569B458B Checksum array value: 0x11001100
Loading code from address: F9A00010 Cookie Address : 0xF9A00010 Cookie Value : 0x90909090
Indicates Bank 1 binary loaded (latest S/W image with valid checksum is chosen)
Section: 16 Page 100
Issue 1.5.4 05 May 03
Jumping to VxWorks at 0x00E00000 EIP = 0x00E0011E Jumping to romStart at 0x00E00300 Uncompress Passed OK sysHwInit start sysHwInit Disable PIIX4E IDE sysHwInit Enable PCI Bus Arbitration limit to PCI Clocks:00000040 sysHwInit Enable PIIX Passive Release of PHOLD sysHwInit: sysIntInitPIC - Interrupt Controller sysHwInit: PIIX4E Interrupt steering setup sysHwInit: PCMCIA device Misc Control 3 setup sysHwInit: sysSerialHWInit Memory Configuration:
Amount of DRAM on card

Bank 0: 64MB sysMemTop: configuring GDT with RAM information sysHwInit2: Connecting PIT0 (sysClk) Interrupt Vector sysHwInit2: Connecting RTC (sysAuxClk) Interrupt Vector sysHwInit2: Calling sysSerialHwInit2 sysHwInit2: Connecting stray interrupt handler sysHwInit2: Connect task-level exception handler Ignore: bogus prompt Enter xxx to force boot from BIOS ROM Setting tLogTask priority to 255 Found device : Cirrus CL-PD672x Flash file system /C: drive (Flash Chip) is TrueFFS formatted initd, /C: drive ready /C: drive (Flash Chip) is an available dosFs file system ipMethodInit, gIPMethod = 2 lnIsa configuration IP Data in NVRAM Valid, Boot Line updated NVRAM data set via IP Address:192.168.1.14 setLeader or BIOS commands Gateway Address:192.168.1.1 Subnet Mask::ffffff80 Target Name: vxTarget User: gijxs03 Cards ELAN MAC address - must lnIsa0 MAC Address: 00:60:38:01:09:fa match entry in BOOTP.1 lnIsa: lnIsa0 Reset lnIsa: lnIsa0 Reset ln79970 - IRQ INTC steered to IRQ15 ln79970HwInit: Device Type 0x2624 - LN79972 10/100BaseT lnPci1 MAC Address: 00:60:38:01:a1:46 Card is Leader, uses NVRAM data. Leader Pack: Using IP info from nvram Attached TCP/IP interface to lnIsa unit 0 If Flr, BOOTP request would be Attaching network interface lo0... done. done at this point. NFS client support not included. Adding 6064 symbols for standalone. ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] (R) ] ]]]]]]]]] ]]]]]] ]]]]]]]] ]] ]]]] ]] ]]]]]]] ]]]]]]]] ]]]]]] ] ]] ]]]] ]]] ]]]]] ] ]]] ] ]]]] ]]] ]]]]]]]]] ]]]] ]] ]]]] ]] ]]]]] ]]]] ]]] ]] ] ]]] ]] ]]]]] ]]]]]] ]] ]]]]]]] ]]]] ]] ]]]] ]]]]] ] ]]]] ]]]]] ]]]]]]]] ]]]] ]] ]]]] ]]]]]]] ]]]] ]]]]]] ]]]]] ]]]]]] ] ]]]]] ]]]] ]] ]]]] ]]]]]]]] ]]]]
Issue 1.5.4 05 May 03
]]]]]]] ]]]]] ] ]]]]]]]] ]]]]] ]]] ]]]]]]]]]]
]]]]]] ] ]]]]]]]
]]] ]
]]]] ]] ]]]] ]]]]]]] ]]]]
]]]] ]]]] ]]]] ]]]] ]]]] ]]]]]
ITG Login: Copyright (c) 1993-1996 RST Software Industries Ltd. Israel. All rights reserved Deleted 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.562 2040 6 21 23:07:58 (COM) :Set defaultRouteGW: 0.0.0.0 2040 6 21 23:07:58 (COM) :NVRAM leader: BOOTP file present 2040 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 Leader 2040 6 21 23:08:16 (COM) : ~~~~~~~~~~~~~~~ STARTING LEADER TASKS ~~~~~~~~~ 2040 6 21 23:08:16 (COM) :tBootpdTask spawned 2040 6 21 23:08:16 (COM) :tSntpsTask spawned 204 leaderIP 192.168.81.30 are in the same subnet 2040 6 21 23:08:16 (COM) :setting Leader IP address 192.168.81.30 2040 6 21 23:08:16 (COM) :tHSRecvTask (Leader listening task) spawned 2040 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 33 2040 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: 0 IP 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 Version 2040 6 21 23:08:20 (DIM) :DSP memory tests passed on DSP 0 2040 6 21 23:08:20 (DIM) :DSP memory tests passed on DSP 1 2040 6 21 23:08:21 (DIM) :DSP memory tests passed on DSP 2 2040 6 21 23:08:21 (DIM) :DSP memory tests passed on DSP 3 2040 6 21 23:08:22 (DIM) :DSP memory tests passed on DSP 4 2040 6 21 23:08:22 (DIM) :DSP memory tests passed on DSP 5 2040 6 21 23:08:23 (DIM) :DSP memory tests passed on DSP 6 2040 6 21 23:08:23 (DIM) :DSP memory tests passed on DSP 7 2040 6 21 23:08:23 (DIM) :Found 8 DSP devices in system 8 DSPs detected 2040 6 21 23:08:23 (DIM) :MXP environment is created and passed selftest 2040 6 21 23:08:23 (SNMP) :DSP temp string is R7.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 0 2040 6 21 23:08:23 (NMM) :Task # 15 : status = 0 2040 6 21 23:08:23 (SNMP) :dummy: setting up alarm struc 2040 6 21 23:08:23 (SNMP) :Calling snmpTrap 2040 6 21 23:08:24 (DIM) :0000015944 - ROOT: gg_perm_malloc: 256 bytes at 0 x004FEF80 2040 6 21 23:08:24 (DIM) :0000015944 - ROOT: gg_perm_malloc: x004FF080 2040 6 21 23:08:24 (DIM) :0000015944 - ROOT: gg_perm_malloc: x00503860 18400 bytes at 0
2784 bytes at 0
Issue 1.5.4 05 May 03
DSP image downloaded to each DSP

1996 1996 1996 1996 1996 1996 1996 1996 2040 2040 2040 2040 3 3 3 3 3 3 3 3 6 6 6 6 17 17 17 17 17 17 17 17 21 21 21 21 17:42:07 17:42:07 17:42:09 17:42:12 17:42:14 17:42:17 17:42:19 17:42:22 23:08:24 23:08:24 23:08:33 23:08:33 (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (NMM) (COM) (NPM) (COM) :Download codec image completed -DSP# 0, Image :Download codec image completed -DSP# 1, Image :Download codec image completed -DSP# 2, Image :Download codec image completed -DSP# 3, Image :Download codec image completed -DSP# 4, Image :Download codec image completed -DSP# 5, Image :Download codec image completed -DSP# 6, Image :Download codec image completed -DSP# 7, Image :NMM received file data OK message from ATPM :ITG0100, ITG card bootup is successful :RADVision H.323 payload update complete. :Current ESN5 Prefix is set to |100| Id Id Id Id Id Id Id Id = = = = = = = = 0 0 0 0 0 0 0 0
VxWorks login:
Issue 1.5.4 05 May 03
16.2
Pentium captures - Follower bootup

When a Follower boots and receives its IP data from the BOOTP response, the highlighted section below is printed out differently than on the Leader card:
sysHwInit: sysSerialHWInit Memory Configuration: Bank 0: 64MB sysMemTop: configuring GDT with RAM information sysHwInit2: Connecting PIT0 (sysClk) Interrupt Vector sysHwInit2: Connecting RTC (sysAuxClk) Interrupt Vector sysHwInit2: Calling sysSerialHwInit2 sysHwInit2: Connecting stray interrupt handler sysHwInit2: Connect task-level exception handler Enter xxx to force boot from BIOS ROM Setting tLogTask priority to 255 Found device : Cirrus CL-PD672x /C: drive (Flash Chip) is TrueFFS formatted /C: drive (Flash Chip) is an available dosFs file system ipMethodInit, gIPMethod = 1 lnIsaNvramInfoGet: ipMethod = 1, Boot Line not updated Target Name: vxTarget User: gijxs03 lnIsa0 MAC Address: 00:60:38:01:19:4f lnIsa: lnIsa0 Reset lnIsa: lnIsa0 Reset ln79970 - IRQ INTC steered to IRQ15 ln79970HwInit: Device Type 0x2624 - LN79972 10/100BaseT Retrieving IP data via lnPci1 MAC Address: 00:60:38:01:a1:b8 BOOTP request Getting IP over BOOTP via network interface lnIsa0 Enter +++ 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.128 Attached TCP/IP interface to lnIsa unit 0 Attached TCP/IP interface to lnPci unit 1 Attaching network interface lo0... done. NFS client support not included. Adding 6064 symbols for standalone.
Config data extracted from BOOTP response
Issue 1.5.4 05 May 03
16.3
Succession Media Card captures - Leader bootup

The following is a capture of a clean Succession Media Card Leader 0 startup, running IPT30052. The card was rebooted while enabled.
MC Firmware Rls 6.4 8051XA Firmware Version 4.8 26 May 2002 (C) Nortel Inc. 2001 EPLD Version: 3.0 32K External RAM detected 8K DPRAM detected All FPGAs are configured No dongle detected Bank 0 Checksum - A6FBH SRAM test okay SDRAM Addr test okay SDRAM blank over Early serial debug initialized
card firmware version 6.4
VxWorks System Boot
Copyright 1984-1998
Wind River Systems, Inc.
VxWorks version 5.4

CPU: IXP1200 Version: 5.4 BSP version: 5.0 Creation date: Nov 22 2001, 18:21:11
5 second window to enter jkl for booting into BIOS
Enter jkl to force boot to BootROM vxWorks prompt
Issue 1.5.4 05 May 03
auto-booting...
boot device unit number processor number file name flags (f) other (o)
: : : : : :
ata= 1 0 /C:/exec 0x0 ixpMac
Attaching to ATA disk device... Found device : Cirrus CL-PD672x 0x3af7934 (tBoot): PC Card Detected: Socket 0 cisGet : pcCard recognized Found ATA flash PC Card Detected: Socket 1 (4 Meg 16 bit words = 8 Meg) cisGet : pcCard recognized /C:/ - Volume is OK 3510564 + 594412 + 4566428 Starting at 0x1000... Early serial debug initialized sysHwInit2: Connect task-level exception handler Setting tLogTask priority to 150 Found device : Cirrus CL-PD672x cisGet : pcCard recognized 0x3affe64 (tRootTask): PC Card Detected: Socket 0 logTask: 2 log messages lost. PC Card Detected: Socket 1 cisGet : pcCard recognized ipMethodInit, gIPMethod = 2 IP Address from NVRAM: 47.11.217.55 IP Data in NVRAM Valid, Boot Line updated IP Address:47.11.217.55 Gateway Address:47.11.217.1 Subnet Mask::fffffe00 Host Name: bootHost Target Name: vxTarget User: target StartUp Script: /C:/etc/startup
ELAN data from non-volatile RAM (survives reboot)
ELAN port initialization

MAC Address for Port 0 is : 00:60:38:bd:fb:31 SysConf: uEng_intConnect to pktHandlingIsr. 0 symbols bound. Load uCode from buffer Status : Return Success Starting Microengines. 0x3affe64 (tRootTask): Loading MAC_21440... 0x3affe64 (tRootTask): mac21440Load: Init String[0] NULL: ixpMac 0x3affe64 (tRootTask): Loading MAC_21440... 0x3affe64 (tRootTask): MAC 21440 String : Processed all arugments 0x3affe64 (tRootTask): mac21440InitMem: Net Pool ID is 51321012 0x3affe64 (tRootTask): Done loading mac21440... 0x3affe64 (tRootTask): mac21440Start: Starting port 0 TLAN Port set to Auto-Negotiate Speed and Duplex Settings Waiting For Carrier link to Return
Issue 1.5.4 05 May 03
MAC Address for Port 1 is : 00:60:38:bd:fb:32 0x3affe64 (tRootTask): Loading MAC_21440... 0x3affe64 (tRootTask): mac21440Load: Init String[0] NULL: ixpMac 0x3affe64 (tRootTask): Loading MAC_21440... 0x3affe64 (tRootTask): MAC 21440 String : Processed all arugments 0x3affe64 (tRootTask): mac21440InitMem: Net Pool ID is 49468440 0x3affe64 (tRootTask): Done loading mac21440... 0x3affe64 (tRootTask): mac21440Start: Starting port 1 ELAN set to 10BaseT Operation ELAN set to Half Duplex Operation Waiting For Carrier link to Return Attached TCP/IP interface to ixpMac unit 1 Attaching network interface lo0... done. 0x3affe64 (tRootTask): WARNING: mac21440MCastAddrAdd called. addr=0x3aff564 NFS client support not included. Adding 10120 symbols for standalone.
TLAN port initialization
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]] ]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] (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
Issue 1.5.4 05 May 03
VxWorks login: 2001 4 6 05:39:25 (COM) :Sending BOOTP request: timeout 860 2001 4 6 05:39:34 (COM) :No BOOTP response: set as Leader 2001 4 6 05:39:34 (COM) : ~~~~~~~~~~~~~~~ STARTING LEADER TASKS ~~~~~~~~~ 2001 4 6 05:39:34 (COM) :tBootpdTask spawned 2001 4 6 05:39:34 (COM) :tSntpsTask spawned Attached TCP/IP interface to ixpMac unit 0 0x3affe64 (tRootTask): WARNING: mac21440MCastAddrAdd called. addr=0x3aff738 2001 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 BCH ID 1 2001 4 6 05:39:35 (COM) :Set defaultRouteGW: 0.0.0.0 D channel data from 2001 4 6 05:39:35 (COM) :Set voiceIPAddr: 47.11.214.0 BOOTP file decoded... 2001 4 6 05:39:35 (COM) :Set defaultRouteGW: 47.11.215.1 2001 4 6 05:39:35 (COM) :leaderIP 47.11.215.211: cardIP 47.11.215.212: sm S 2001 4 6 05:39:35 (COM) :cardIP 47.11.215.212 and leaderIP 47.11.215.211 are in the same subnet 0x3affe64 (tRootTask): Setting dosFS Cache Update Interval to 0200 Secs 1 4 6 05:39:35 (COM) :setting Leader IP address 47.11.215.211 2001 4 6 05:39:35 (COM) :tHSRecvTask (Leader listening task) spawned 2001 4 6 05:39:35 (COM) :Card IP[0]: 47.11.215.211 2001 4 6 05:39:35 (COM) :Card IP[1]: 47.11.215.212 2001 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 to 47.11.217.55 2001 4 6 05:39:35 (RMM) :***LDR send back GK status:0 2001 4 6 05:39:35 (RMM) :***FL card update GK status: 0 2001 4 6 05:39:35 (RMM) :ERROR ! Ignored request from 0.0.0.0 to override ownResource Entry index 1 2001 4 6 05:39:35 (A07) : XA : - Spawn xaTask() 2001 4 6 05:39:35 (A07) : XA : - xaTask Spawned OK 2001 4 6 05:39:35 (A07) :Waiting for XA firmware version reply... Telogy Software Version 8.1 DIM 2001 2001 2001 2001 2001 2001 2001 2001 2001 2001 2001 created successfully... 4 6 05:39:38 (A07) :Received firmware version reply 4 6 05:39:38 (DIM) :MXP environment is created 4 6 05:39:38 (DIM) :From Eeprom information, number of DSPs = 8 4 6 05:39:38 (DIM) :dimhw_init : DSP Type = C5421 4 6 05:39:38 (NMM) :tNMM running: Software version IPT3.0.52 4 6 05:39:38 (SNMP) :DSP str is R8.01 4 6 05:39:38 (NMM) :sending Module Status message: module 15: status 0 4 6 05:39:38 (NMM) :Task # 15 : status = 0 4 6 05:39:38 (SNMP) :dummy: setting up alarm struc 4 6 05:39:38 (SNMP) :Calling snmpTrap ATPM table built okay 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 ATPM 2001 4 6 05:39:38 (COM) :Task tSockReuse initialised okay
Issue 1.5.4 05 May 03
2001 4 6 05:39:38 (COM) :ITG0100, ITG card bootup is successful 2001 4 6 05:39:38 (UIPC) :ITG0150 - D-channel (6) restored. Channels will be returned to service. IP Address from NVRAM: 47.11.217.55 2001 4 6 05:39:42 (A07) :Board Enabled - LED OFF 2001 4 6 05:39:43 (SNMP) :ContactSet: The SNMP Value is Invalid Card up 2001 4 6 05:39:43 (DIM) :Number of DSPs = 8 2001 4 6 05:39:43 (DIM) :DSP memory test passed on dsp 0 DSPs found; booting 2001 4 6 05:39:43 (DIM) :DSP memory test passed on dsp 1 2001 4 6 05:39:43 (DIM) :DSP memory test passed on dsp 2 2001 4 6 05:39:43 (DIM) :DSP memory test passed on dsp 3 2001 4 6 05:39:43 (DIM) :DSP memory test passed on dsp 4 2001 4 6 05:39:43 (DIM) :DSP memory test passed on dsp 5 2001 4 6 05:39:43 (DIM) :DSP memory test passed on dsp 6 2001 4 6 05:39:43 (DIM) :DSP memory test passed on dsp 7 2001 4 6 05:39:43 (NMM) :NMM received file data OK message from MAM Download codec image completed -DSP# 0, Image Id = 0 Download codec image completed -DSP# 1, Image Id = 0 Download codec image completed -DSP# 2, Image Id = 0 Download codec image completed -DSP# 3, Image Id = 0 Download codec image completed -DSP# 4, Image Id = 0 Download codec image completed -DSP# 5, Image Id = 0 Download codec image completed -DSP# 6, Image Id = 0 Download codec image completed -DSP# 7, Image Id = 0 DSPs done booting Signalling DSP Tx UEngine to Initiate Polling 2001 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|
Issue 1.5.4 05 May 03
Issue 1.5.4 05 May 03
Appendix A
A.1 Introduction
Configuration files
The active conguration les have a .1 sufx; e.g. BOOTP.1, DPTABLE.1, or have a 1 before the .xxx; e.g. CONFIG1.INI. The backup les have a .2 sufx; e.g. BOOTP.2, DPTABLE.2, or precede the sufx by 1; e.g. CONFIG2.INI. The system automatically copies a good version of the le to this. In case of bad le download or le corruption the system replaces the active copy with this version of the le. The contents of each le can be printed using the following command:
->copy <path/filename>
You can change the content of the le1 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 le; be aware that these may not (and for most cases, do not) work on the Media Card. However, copy 0,lename does work for all cards.
A.2
CONFIG1.INI
This le is parsed by the MAM task to congure the routes, the DSP, SNMP traps, RADIUS client and TOS bits. The le is parsed on card reset and also automatically when downloaded from OTM. Note that the ITG card can only generate North American ring-back tone. Should the user need other tones (for example, British ring-back) and the IPT 3.0 node interworks with a CSE 1000 gatekeeper, the user must install the applicable work-around patches on the CSE 1000 signalling and call servers and/or the corrective patch on the Meridian 1. Having done that, the user is advised to manually add
[LocalRingBack] M1GeneratesRingBack=1
to the end of the CONFIG1.INI le. This is a safety measure and should not be needed, but it is highly recommended by IPT 3.0 design. An OTM patch has been requested to provide this, but until it is available, the ag needs to be entered manually.
1. Use this command to create these les only when OTM is unavailable.
Issue 1.5.4 May 20, 2003
(The user can also use the useIPTForRingBack (section B.1.44, pg 169) or useM1ForRingBack (section B.1.45, pg 169) to toggle between ITG card and M1 ring-back.) After making this change, the user should use OTM to retrieve theb data, so that it will remain after the next provisioning change through OTM. Otherwise, the craftsperson must repeat this oiperation every time the provisioning changes. A.2.1 A.2.1.1 Downloading / parsing from TTY congFileGet This command FTPs the le from the specied server, renames it to cong1.ini and parses the le. A.2.2 Example le The cong le is pretty self explanatory. Each section begins with a section identier in []. Note that the [routes] are routes for the ELAN only. TLAN routes are set up by DPTABLE or live trafc.
#version=2.0 [keycode] keycodeId=12345678-78654321-23434324 [snmp] rdCommunityName=public wrCommunityName=private trapsEnabled=1 trapsub=129.15.3.131,129.15.19.23 ts1=129.15.3.131,255.255.255.224, ts2=129.15.19.23,255.255.255.0, CardIP=129.15.3.136 sysHostName=TEST SITE sysLocation=TN 148 1 12 Management IP: 129.15.3.136 sysContact=Nortel Networks [routes] re1=129.15.3.131,255.255.255.224, re2=129.15.19.23,255.255.255.0, [dsp0] DspImage=1 DtmfToneDetect=1 EchoCancel=1 DspEchoTail=32 TxGain= 0 RxGain= 0 IdleNoise=-65 VadThreshold=-17
Issue 1.5.4 May 20, 2003

ModemDetect=1 FaxDetect=1 FaxRate=14400 FaxPlayoutNomD=100 FaxActiveTimeout=20 FaxPacketSize=30 Codec=0 VxPayload=10 VxPlayoutNomD=40 VxPlayoutMaxD=100 VadEnabled=1 Codec=5 VxPayload=30 VxPlayoutNomD=60 VxPlayoutMaxD=120 VadEnabled=1 [tos] controlPrio=0 voicePrio=0 [accounting] acSvrEnabled=0 acSvrAddr=0.0.0.0:1813 acSvrKey=
1. Added manually if required. Intended for non-North American sites with the Meridian 1 patch installed.
Issue 1.5.4 May 20, 2003
A.3
DPTABLE.1
The dialling plan table is parsed by the ATPM module and contains the IP address to dialplan digit mapping. The le is parsed on card reset and also automatically when downloaded from OTM. A.3.1 A.3.1.1 Downloading / parsing from TTY nmmAtpmTranTblDnld This forces parsing of the dialling plan table (dptable.1). A.3.2 Example le The dialplan le contains a list of the IP to dialplan mappings. The rst two lines are not used by the ITG2.0 application (they have historical signicance). Each remaining line in the le represents a comma delimited dial plan entry from OTM. In this example, there are no digits to insert, so that eld is blank.
#version=2.0 0,1,1,1,1 0,1,1,1,1 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
#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
Type Of Numbering Plan
Dialed Digits
Access Code
# Digits to Complete Call
# Leading Digit Delete
Insert Digit
Remote IP address
QoS Enable d
Send QoS
Receive QoS
Node Capability
GK Flag
Remote Loc Name
Remember: leave insert digits blank; putting in a 0 means a 0 is inserted as the new leading digit...
Issue 1.5.4 May 20, 2003
The le can be much more complex, but the format of dial plan entries is identical for all dialable numbers. However, it is also possible to have gatekeeper data. There are three gatekeeper entry types - registration data (GKR), primary gatekeeper (GKP) and alternate gatekeeper (GKA).
#version=2.0 0,1,1,1,1 0,1,1,1,1 #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||||" #NodeIP=47.11.215.182 NPA,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.33 SPN,0119999,0,0,0, ,191.11.22.33,0,3.0,3.0,8,0,"" #Node=47.11.240.87 DSC,27,0,0,0, ,47.11.240.37,0,3.0,3.0,7,"" #Node=44.33.22.11 - Fake Node NPA,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 gatekeeper (GKP) and alternate gatekeeper (GKA).
#version=2.0 0,1,1,1,1 0,1,1,1,1 #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||||"
Issue 1.5.4 May 20, 2003
Translating the key bits, we get:

#Gatekeeper Registration Information
Comment only; makes it easier to tell that the next line is for registration info
GKR,Shane_IPT_cust1,0,0
GKR: gatekeeper Registration Shane_IPT_cust1: H.323 ID
#Primary Gatekeeper
Comment only
GKP,47.11.215.253,1000,"GK1||||"
GKP: primary gatekeeper 47.11.215.253: IP address of GKP 1000: GK is CSE 1000 R2 "GK1||||": Gatekeeper info from OTM Comment only
#Alternate Gatekeeper
GKA,47.11.215.251,1000,"GK2||||"
GKA: alternate gatekeeper 47.11.215.251: IP address of GKA 1000: GK is CSE 1000 R2 "GK2||||" Gatekeeper info from OTM
Issue 1.5.4 May 20, 2003
A.4
BOOTP.1
The BOOTP.1 le is only present on the ITG leader and backup leader cards. This le contains the Node Properties. It is parsed only on card reset. The card has to be rebooted after downloading the node properties for the changes to take effect. Thus any changes to the card IP addresses or subnet masks, associated DCH number or protocol will only take effect on card reset. A.4.1 Example le The following is a BOOTP.1 le for a single card ITG node. NOTE: Even though the rst two lines appear as comment within the bootp le they are used by the ITG application and should not be modied. Comments elsewhere within the BOOTP le (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.0 47.11.215.1:dn=6 0:nt=6.135.0.1: #cardDensity=32
The lines are colon delimited, meaning a : separates elds. The key data translates as per the next page: nt=6.135.0.1 - D channel info: 6 -> DCH 6 135 -> 128 + 7 = (128) D channel on this card plus DCH protocol SL1 0.1 -> 0x00 01 - first channel is 1 (may be over 255...)
Issue 1.5.4 May 20, 2003
The BOOTP.1 elements are broken down as follows. Note this is a single card node; when there are multiple cards, there is a card index entry line for each.
Node IP (Leader Alias IP) Leader ELAN IP OTM version ELAN Subnet Mask ELAN Gateway IP TLAN Node IP
#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: Card Index # ELAN MAC Address one entry per ITG card ELAN IP TLAN Voice IP
1:tc=.subnet1:ha="00:60:38:BD:FB:31":ip=47.11.217.55:lp=47.11.215.212 255.255.255.0 47.11.215.1:dn=6 0:nt=6.135.0.1:
Card TN TLAN Subnet Mask TLAN Gateway IP
D channel info
The Card TN eld contains the Cards TN plus the card type: Large System
dn=100 0 0 0
where: 100 0 0 0 = = = = Loop Shelf Card Card Type 0 - EXUT 1 - XFEM (not used)
Small System
dn=6 0
where: 003 0 = Card slot 3 = Card Type 0 - EXUT 1 - XFEM (not used)
nt=6.135.0.1 - D channel information. 6 means DCH 6. 135 decomposes as 128 + 7. 128 means that there is a D channel on this card, plus the 7 means that the DCH protocol is SL1. The 0.1 is a 16 bit integer; 0x00 01 means that the rst channel is 1 (it may be over 255...).
Issue 1.5.4 May 20, 2003
Appendix B
IP Trunk Command Reference
IP Trunk is used very rarely in these sections. The screen typically responds with an IPT or displays IPT when it means IP Trunk as there is a real-time cost to print-outs. Therefore, the shortest version possible 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 associated with a command. The levels are (in order of increasing risk): Normal - will not cause events visible to the end user. Includes events such as the original card provisioning, which are a normal part of administering the system. Safe - will not cause events visible to the end user. Although the command can be issued at any time, it is intended for system debug and not normal operations. Safe/xxx - as per Safe, but it is possible to have a small impact. For example, arpFlush will remove non-permanent entries from the ARP cache, but the cache will rell over time. As a result, calls to an address not found in the cache will be slightly slower, although the difference should not be visible to a caller. Debug - can be used for debugging, but under exceptional circumstances it can cause side effects. Normally, using these commands during off hours allows the user to treat as Safe, but under moderate to heavy trafc there may be symptoms such as minor increase in post dial delay (the time between the last digit being dialled and hearing ring-back) Note, though, that this will normally be within the norm of post dial delays, since different destinations may have different delays as well, based on network topology and distance between nodes. Debug/xxx - can be used for debugging, but under some circumstances it can cause side effects. As per Debug, using these commands during off hours typically allows the user to treat as Safe, but under moderate to heavy trafc there may be symptoms such as loss of calls, call delays, and so forth. These commands are usually very CPU intensive and CPU resources used to process this command are unavailable for call processing. Destructive Normal - although a regular part of the operations, these commands cause severe events on the system. Commands used to upgrade the software are Destructive Normal, since the reboot to run the new load takes the card out of service for the duration of the reboot. Destructive Debug - these commands must be used with extreme care, since misuse can cause service interruption. Note that no command is expected to cause service interruption, but to allow a user to do the most comprehensive debugging, they need the exibility to do things such as writing to data and program store. Used correctly, there should be no adverse effects, but misuse is severe.
Issue 1.5.4 May 20, 2003
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, blocking call processing. The user may use this to Enable(1) or Disable(0) the card reboot due to task monitor detect suspended/Missing task. This command will change the contents of le c:/ cong/audit.ini
ITG> auditRebootSet 0 Audit task set auto reboot -- Disabled Reboot when detect a suspended task --- Disabled Reboot Time hh:mm:03:00 Critical Task list : tExcTask tNetTask tTelnetd Non-Critical Task List: tLogTask tAioWait value = 0 = 0x0 ITG>
tFtpdTask
....
tAioIoTask1
tAioIoTask0
....
B.1.2
auditRebootTimeSet hh:mm Safety level: Safe. This command expects the parameter hh:mm based on the 24 hour clock. Use it to set the scheduled reboot time when the task monitoring function detects a missing or suspended non-critical task.
ITG> auditRebootTimeSet 03:00 Reboot when detect a suspended task --- Enabled Reboot Time hh:mm:03:00 Critical Task list : tExcTask tNetTask tTelnetd Non-Critical Task List: tLogTask tAioWait value = 0 = 0x0 ITG>
tFtpdTask
...
tAioIoTask1
tAioIoTask0
...
Issue 1.5.4 May 20, 2003
B.1.3
auditShow Safety level: Safe. This command can be used to display task monitoring setup information as stored in audit.ini le, 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> auditShow Reboot when detect a suspended task --- Disabled Reboot Time hh:mm:02:00 Critical Task list : tExcTask tNetTask tTelnetd Non-Critical Task List: tLogTask tPcmciad tTffsPTask ITG>
tFtpdTask tPortmapd
... ...
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 the user wants to force a reboot on a suspension of a task with a default level of non-critical, or to block reboot on a critical task. Use either the task name or task ID (tid). Printing the current status using auditShow will 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 will set the task to be a Non-Critical task.
ITG> auditTaskSet tMAM,0 Reboot when detect a suspended task --- Disabled Reboot Time hh:mm:03:00 Critical Task list : tExcTask tNetTask tTelnetd tShell tRmm tNpm tA07 tNMMTask tMVX_DIM tIpss tTSM tMcciMsgMgr Non-Critical Task List: tLogTask tAioWait tAioIoTask1 tHSRecvTask tMAM tXA value = 0 = 0x0 ITG>
tFtpdTask baseMMintTask tATPM
...
tAioIoTask0 tMVX_XSPY
... ...
Issue 1.5.4 May 20, 2003
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. This is the preferred way to reboot the card since it allows the application to reboot in a controlled manner (e.g. the OM le is written and closed before the card reboots).
B.1.6
cd dirPath Safety level: Safe. Change directory to the directory path specied by dirPath. Drive /A: is the faceplate PC Card, while drive /C: is the internal Flash drive. From the ITG> prompt:
ITG> cd /C: value = 0 = 0x0 ITG> cd TRACE value = 0 = 0x0 ITG> pwd /C:/TRACE value = 10 = 0xa ITG> cd /C: value = 0 = 0x0 ITG> 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 can no longer be used as a leader, and if there is no other card acting as leader, the node is effectively out of service. However, the card will remain in service as a leader until the reboot. This command sets up the card as a Follower by deleting the ELAN IP address data from the NVRAM, clearing the Leader ag and setting a ag so the BOOTP request is sent on reboot instead of reading the IP parameters from the NVRAM. Rebooting completes the clearing of the leader data.
Issue 1.5.4 May 20, 2003

ITG> clearLeader This card will be a follower on reboot. value = 41 = 0x29 = ')' ITG> NVRIPShow IP address : 255.255.255.255 Gateway : 0.0.0.0 Subnet Mask: 0.0.0.0 Set 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 le is copied (or printed to screen) there should be no signicant impact. This command copies a le from the sourceFilename to the destFilename. If destFilename isnt entered, this copies the le to the standard output device (the TTY display), providing an easy way to look at the contents of the text les (CONFIG1.INI, BOOTP.TAB, SYSLOG.n, OMREPORT.nnn). Note that this can also be used to edit a le on switch. Using copy 0,filename.ext, the user can start typing in data. The keyboard input control-d terminates data entry and saves the data to le.
ITG> copy dptable.1 #version=3.0 0,1,1,1,1 0,1,1,1,1 #NodeIP=47.11.215.209 DSC,3,0,0,0, ,47.11.215.209,0,3.0,3.0,8,Central_Light_and_Power - Bat Cave - Customer 0 - Node 1" value = 0 = 0x0 ITG> ..... -> 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.0 47.11.215.1:dn=6 0:nt=6.135.0.1: #cardDensity=32 value = 0 = 0x0 ->
Note that the line #version=2.0 in the BOOTP le indicates the OTM version and not the IP trunk version. However, in a very contradictory manner the DPTABLE.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 certain elds in the le. On the other hand, it was decided that it was more important to know the OTM server release when looking at the CONFIG1.INI.
Issue 1.5.4 May 20, 2003
Do not trust these les to tell you the software version. Use swVersionShow instead. The user may also edit a le on switch using the copy command. Here, the syntax is copy 0,destlename. Start with the command; end entry using a control-d. (It is usually better to edit les on a PC or workstation, and FTP up and down from the switch. This tool provides users an alternative only.)
-> copy 0,"trash.txt" In the seventh century of the Roman Empire ^Dvalue = 0 = 0x0 -> ls . .. PATCH TMP trash.txt value = 0 = 0x0 -> copy "trash.txt" In the seventh century of the Roman Empire value = 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 D channel PC card on board. A card with the D Channel PC card is a DCHIP Leader, but that card may be - and usually is - a Follower card within the IPT node. Since the DCHIP leader has additional signalling requirements, the norm is to not have the DCHIP Leader role on the Leader card, since the Leader card also has the H323 leader role. When entered on a Leader card, this command shows all the followers currently associated with the DCH resident on this card. The craftsperson may use this command to verify that all of the expected Followers are listed. Note: each Follower that has successfully registered with the DCHIP card is listed, displaying the following information: Follower cards index number in the D Channel resource table Follower cards ELAN IP address Follower cards starting B-channel number The DCHIP Leader socket descriptor for the TCP connection to the Follower Whether the Follower is also congured as the DCHIP Leader (socketDescriptor == -1)
Issue 1.5.4 May 20, 2003
Unregistered followers are not seen. As shown in the example, if a listed Follower is also the DCHIP Leader, the socketDecriptor is set to -1 since the DCH messaging is passed internally and there is no TCP connection. The following example shows output for a single card node:
ITG> dchipResTableShow The 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 Leader (the card with the D channel PC card inserted) and the node leader. The following output was seen when issuing the command on the DCHIP leader card:
ITG> dchipResTableShow The 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 = 0x83 ITG>
On the other hand, the following output was seen on a DCHIP Follower that also happened to be the node leader card:
-> dchipResTableShow Card is not DCHIP,dchipResTableShow command ignored! value = 57 = 0x39 = '9' ->
Issue 1.5.4 May 20, 2003
B.1.10
DCHmenu Safety level: Debug/output load. Normally, if the command is used for any option other than 6 through 9, the command is relatively safe. Under load, the options 6 through 9 can result in heavy message printout on the login window, at the extreme resulting in call loss and delays in calls that are not lost. The IPT applications DCH Handler is the UIPE application ported from the MSDL card. This is a menu based debug tool nearly identical to that on the MSDL card. Debugging the output requires extensive practice. The output is typically raw hexadecimal. Identifying an IE and determining whether it is valid or not can be a painful exercise. Many IEs (such as the Facility and Display IEs) are similar in format to ITU-T IEs of the same name, but there are proprietary extensions, and many of the elds (such as the specic operation requested in the Facility IE) are not dened by the ITU-T. Other IEs are Nortel Networks proprietary in the entirety. As a result, decoding a message is usually difcult. However, the primary use of the DCHmenu trace is to get a message to compare with the Meridian 1 D channel trace (overlay 96).
ITG> DCHmenu Please select one of the DCHmenu options: 0 - print menu (default) 1 - print current DCH state and configuration 2 - print application error log 3 - print link error log 4 - print protocol log 5 - print message log 6 - ENABLE error printing 7 - ENABLE info printing 8 - ENABLE incoming primitive 9 - ENABLE outgoing primitive 10 - enter message mode 11 - print b channel control blocks 99 - exit menu Please enter your DCHmenu choice:
After the menu is displayed, any carriage return without data or 0 entered triggers the reprint of the menu. Entering invalid data (not in the list) triggers the following output:
Please enter your DCHmenu choice: 43 Menu selection not recognized! Please enter your DCHmenu choice:
Several of the options print current stats and data. These are independent of the call control operations under way.
Issue 1.5.4 May 20, 2003
To print the D channel information, enter 1:

Please enter your DCHmenu choice: 1 STATE INFORMATION FOR PORT 0: Port 0: Link State Data State: installed. DCH State: Established Able to Establish: Yes CONFIGURATION INFORMATION FOR PORT 0: Port 0: Link Configuration Data Network side. SAPI = 0. TEI = 0. L2 Protocol = LAPD Version = 3.1 L3 Protocol = 7 (table id: SL1) Port: RS-422 DCE Int Clock MDL Error Reporting: On Monitor Mode: Off CREF Length = 2 (Not Checked) Max B Chn = 480 State Masks: SL1 Init = 0x0340 DL Failure = 0x0040 INIT Tmr Exp = 0x0040 In Service
Please enter your DCHmenu choice:
To print the application error log information (layer 3 errors), enter 2:

Please enter your DCHmenu choice: 2 APPLICATION ERROR LOG FOR PORT 0: Application Error Log Error
Count
Please enter your DCHmenu choice:
The supported error counters are only listed if the error happened; that is, if no protocol discriminator errors occurred, that error will not be displayed. From the example shown here, there were no errors to report. Note that the source of the message error is shown by PRI (for from the PBX) and UNIV (for from the IPT 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 format is unknown. - PRI_PROTOCOL_DISCRIM_ERROR - UNIV_PROTOCOL_DISCRIM_ERROR Call reference errors. Invalid formats mean that the data is useless. Invalid flags means that the call associated with this call reference does not exist, or the call reference value is corrupted. Also, only certain specific messages are
Issue 1.5.4 May 20, 2003
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, the message must be rejected. - PRI_UNRECOGNIZED_MSG_TYPE - UNIV_UNRECOGNIZED_MSG_TYPE Mandatory IE errors. The IE may be missing (in which case the message is rejected as per the applicable standards) or defective (with similar response, although 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 is still processed. - 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 IE is rejected. A comprehension required IE was coded to indicate it should be treated 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 supported; in all others, they are unexpected. This catch-all event tracks messages received when they are out of sequence. They may be from the PBX, from the IP cloud, or from local timers (that should have been stopped). - PRI_EVENT_UNEXPECTED - UNIV_EVENT_UNEXPECTED - TIMER_EVENT_UNEXPECTED
Issue 1.5.4 May 20, 2003
To print the link error log information (in theory layer 2 errors, but some layer 3 as well), enter 3:
Please enter your DCHmenu choice: 3 ERROR LOG FOR PORT 0: Port 0: Link Error Log Error Count 59 1 Please enter your DCHmenu choice:
There are a large number of possible errors - over 60, but they are typically rare. To print the protocol error log information (layer 3 errors), enter 4:
Please enter your DCHmenu choice: 4 PROTOCOL ERROR LOG FOR PORT 0: Port 0: Protocol Log Error Please enter your DCHmenu choice:
Count
The most likely to apply deal with failure to establish or maintain layer 3 (indicated by the presence of the SABME in the error type name. To print the message log information (layer 3 and 4 message counter), enter 5. Messages from the higher levels of IPT 3.0 software are prexed CC, meaning from Call Control. Requests initiate a sequence; responses complete it. For example, a SETUP REQUEST is a request to send a SETUP; a SETUP RESPONSE is a request to sent a CONNECT message.
Please enter your DCHmenu choice: 5 MESSAGE LOG FOR PORT 0: Port 0: Message Log Message Count CC Alert Request CC Disconnect Request CC Facility Request CC Notify Request CC Proceeding Request CC Release Request CC Setup Request CC Setup Response CC Restart Response ALERTING CONNECT CONNECT ACK DISCONNECT FACILTY NOTIFY RELEASE RELEASE COMPLETE RESTART SETUP Please enter your DCHmenu choice:
2 2 4 8 2 6 6 2 1 6 5 2 6 4 9 2 6 1 2
Issue 1.5.4 May 20, 2003
To trace message ow on the y the user can enter 6 (errors only), 7 (link only), 8 (primitives from call control) and 9 (primitives to call control). It is difcult to use 6 to generate examples. It is best used if a problem has been identied, to get details. 7 produces similar output to the following. Note that only the SETUP was provided here; other messages followed, but the procedure is identical.
Please enter your DCHmenu choice: 7 ENABLE INFO PRINTING FOR PORT 0:
Please enter your DCHmenu choice: UIPE L3 EVENT: PORT 0x00: 02/17/101 05:18:26 9232853 Hdr -> 00 2F 00 00 52 00 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 L2->L3: SETUP: CR = 0x81A0: Proc 0x01: New CB: State = U0: CALL RELATED Event 0x2A: Parse Msg Proc 0x47 L3->SL1: CC Setup Ind: Mapped Hdr -> 00 2F 00 00 72 00 Data -> 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 0A Start T_SETUP for 10 seconds State => U6
All messages provide similar output. First is the record header, indicating an event on port 0, at a given timestamp. This is followed by the message transport header. In the following example, there are 6 bytes to the message transport header. The 5th byte is the length of the message following; all others are details.
Hdr -> 00 2F 00 00 52 00
Issue 1.5.4 May 20, 2003
The next 0x52 bytes are the message. It is printed in rows of 10 octets.
Data -> 08 18 A1 81 00 02 06 80 30 02 04 16 02 85 01 AB 34 30 01 E9 02 01 01 01 00 35 A0 A0 01 05 04 02 1E 30 05 83 01 82 1C 02 02 30 04 20 02 01 11 01 81 70 03 1C 01 01 11 00 83 05 80 1A A1 84 FA CC 6C E9 90 11 30 02 A1 04 06 33 A2 FD 0E 00 0D 46 69 35
This is followed by the analysis of the Q.931 or UIPE header. For this example, it indicates direction (L2->L3 means from LAPD to UIPC layer 3), the message type and call reference, and the received state (U0), plus other less important information.
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 are of interest to design, as designers can conrm whether IEs actually were processed. At the end, timer changes and state changes are listed. 8 and 9 provide more terse tracing. To compare a SETUP received with option 7 and one with option 8, refer to the following:
Please enter your DCHmenu choice: 8 ENABLE INCOMING PRIMITIVE MONITOR FOR PORT: 0
Figure 5 Option 8 SETUP
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 7

UIPE L3 EVENT: PORT Hdr -> 00 2F 00 00 Data -> 08 02 01 A0 18 04 E9 A0 A1 16 02 01 81 02 01 05 00 85 01 04 02 01 01 02 06 A7 00 1E 80 34 35 30 30 30 L2->L3: SETUP: CR = 0x00: 52 00 05 04 83 20 01 02 82 01 1C 11 02 01 02 81 30 70 02/17/101 03 1C 01 01 11 00 83 05 80 1A A1 84 FA CC 6C E9 90 11 30 02 A1 04 06 33 A2 FD 0E 00 0D 46 69 35 05:31:05 9308768
0x81A0: Proc 0x01: New CB: State = U0: CALL RELATED
Issue 1.5.4 May 20, 2003

Event 0x2A: Parse Msg Proc 0x47 L3->SL1: CC Setup Ind: Mapped Hdr -> 00 2F 00 00 72 00 Data -> 08 02 01 A0 2E 00 01 07 81 90 00 00 A2 00 09 09 E9 A0 83 00 01 00 20 00 07 00 11 FD 18 00 A1 16 01 02 01 A1 30 0E 81 02 82 01 01 84 02 00 00 85 13 15 07 00 11 FA 0F 00 02 01 01 02 02 01 00 CC 06 A7 00 00 1E 04 03 00 05 0A 07 00 62 80 04 00 0A 0A 03 0A 03 00 E2 00 03 05 0A 0A Start T_SETUP for 10 seconds State => U6
13 0F 13 02 01 01 A1 04 81 04 04
00 00 1E 01 05 04 0D 46 83 05 00
It can be seen easily that the information from the received SETUP is available in both cases, but the level 8 was less complete.
Issue 1.5.4 May 20, 2003
Nortel Networks Condential Figure 7 Sample of an option 8 message trace, and how to interpret it
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 30 0x33a5d3c (tPcmciad): <DL_DATA_IN> LAPD -->>> UIPC----------- SETUP received from the M1 HEADER BCAP {8 2 1 a0 5} {4 3 80 90 a2} CHID FAC {18 4 e9 a0 83 20} {1c 1a 11 fd FAC (continued) a1 16 2 1 1 2 1 a1 30 e FAC (end) FAC 0 85 1 4) (1c 11 11 fa a1 d FAC (continued) 2 1 1 2 2 1 0 cc 4 46 FAC (end) PROG CLNG 6 a9 0) (1e 2 81 83) (6c 6 69 CLNG CLED 80 34 35 30 30) (70 5 e9 33 35 CLED 30 30)
Use the same procedure for the other traces. NOTE: Incoming: All messages sent to the PC Card by UIPC Outgoing: All messages sent to the PC Card via Layer 1 Driver
Issue 1.5.4 May 20, 2003
B.1.11
dosFsCongShow Safety level: Debug. This command prints information about the DOS le system on the /C: drive. It is 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): cache block I/O descriptor ptr (pCbio): auto disk check on mount: max # of simultaneously open files: file descriptors in use: # of different files in use: # of descriptors for deleted files: # of obsolete descriptors: 0x338089c 0x3380b68 DOS_CHK_REPAIR | DOS_CHK_VERB_2 22 2 2 0 0
current volume configuration: - volume label: NO NAME ; (in boot sector: - 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: - free space on volume: value = 0 = 0x0 ITG>
NO NAME
1 clusters 8,511,488 bytes
Issue 1.5.4 May 20, 2003
For the Pentium card, the output looks like this:

ITG> dosFsConfigShow device name: total number of sectors: bytes per sector: media byte: # of sectors per cluster: # of reserved sectors: # of FAT tables: # of sectors per FAT: max # of root dir entries: # of hidden sectors: removable medium: disk change w/out warning: auto-sync mode: long file names: exportable file system: lowercase-only filenames: volume mode: available space: max avail. contig space: value = 0 = 0x0 ITG> /C: 7695 512 0xf8 4 1 2 6 240 1 false not enabled not enabled not enabled not enabled not enabled O_RDWR (read/write) 3481600 bytes 3440640 bytes
B.1.12
firmwareVersionShow Safety level: Debug. Print the cards rmware version. It should be Rls 5.7 or higher for Pentium card, and should be Rls 6.4 (media card) and 4.8 (XA) or higher for the SMC card. The example shows the command and reply as per a Succession Media Card.
ITG> firmwareVersionShow Firmware Version : MC Firmware Rls 6.4 value = 40 = 0x28 = ( ITG>
B.1.13
gkShow Safety level: Debug; safe except under heavy trafc. This command prints the gatekeeper provisioning, operational status, and the current information from the gatekeeper. If there is no gatekeeper provisioned, the response is:
ITG> gkShow There are no Gatekeepers. value = 2 = 0x2
If there is gatekeeper provisioning, the response is similar to the following:
Issue 1.5.4 May 20, 2003

ITG> gkShow There is a Primary Gatekeeper only. --------------------------------------<<PROVISIONED>> The H.323 ID of this gateway is : First place dialed numbers are resolved: Second place numbers are resolved : Cards that register with the Gatekeeper: <<OPERATIONAL>> The Current Gatekeeper is The Current Gatekeeper status is
[Lab_switch1_IPT_cust1] ATPM Gatekeeper All
: Primary : Registered
<<From the Gatekeeper>> The Time To Live (TTL) for the node is : The remaining time to Re-Register is : The Gateway End Point ID is : 4.0.7.0.0.0.2.b.3.8.6.2.6.a.7 The Gatekeeper has Pre-Granted ARQ : ---------------------------------------
30 seconds 9 seconds .0.2.6.1.2.a.e.0.2.0.0.3.0.2.0.6.1.4.0. Not Granted - direct calls possible
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 --------------------------------------value = 2 = 0x2 ITG>
Note, though, that in this example there was only one gatekeeper - the primary. If an alternate existed, it would have been shown separately.
Issue 1.5.4 May 20, 2003
The following explains the elds:

ITG> gkShow There is a Primary Gatekeeper only.
Line indicating that (a) a gatekeeper was provisioned and (b) only the primary gatekeeper exists.
--------------------------------------<<PROVISIONED>>
Line indicating the start of provisioning based data.

: [Lab_switch1_IPT_cust1]
The H.323 ID of this gateway is
The provisioned H.323 ID as used for registration with the gatekeeper. There must be a 100% match (absolutely identical text strings).
First place dialed numbers are resolved: ATPM Second place numbers are resolved : Gatekeeper
Order of looking for places to resolve the addresses.

Cards that register with the Gatekeeper: All
Do all cards register as one (possibly without indicating the IP addresses) or does each register independently?
<<OPERATIONAL>>
Start of operational data - states, etc.

The Current Gatekeeper is : Primary
Is the node registered with the primary or the alternate gatekeeper?

The Current Gatekeeper status is : Registered
Is it registered, was it registered but the re-registration failed, or was it never registered?
Issue 1.5.4 May 20, 2003
<<From the Gatekeeper>>
Information received from the GK, or operational information based on the gatekeeper responses.
The Time To Live (TTL) for the node is : 30 seconds
The time to live interval; usually, this is as provisioned by the media gateway, but the gatekeeper can over-rule and tell the gateway what value to use.
The remaining time to Re-Register is : 9 seconds
In 9 seconds, the card will re-send a registration request.

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
A unique end-point identifier which was assigned by the gatekeeper.

The Gatekeeper has Pre-Granted ARQ possible : Not Granted - direct calls
The gateway has to request admission via the ARQ before using the SETUP.
--------------------------------------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 --------------------------------------value = 2 = 0x2 ITG>
Issue 1.5.4 May 20, 2003
Primary Gatekeeper information ------------------------------
<<PROVISIONED>>
Provisioning information about the gatekeeper assigned as the primary gatekeeper (default gatekeeper).
: CSE1000
Primary Gatekeeper type is
Type of gatekeeper; for IPT 3.0, only gatekeepers performing as per the CSE 1000 release 2 are supported.
Primary Gatekeeper IP information is *Gatekeeper IP : 47.11.249.140
IP address of primary gatekeeper.
*QoS Enabled
: 0
Quality of Service pings as per IPT/ITGT enabled - not possible at this time.
*Node Capability : 9 - CSE - Interop Format
Default remote D channel capability (Interop format means that the ISDN message is packaged in the nonstandard data of the H.323 UserUser Information Element as per the Nortel Interoperability standard.
Caution:
If there is not a 100% match between the H.323 ID as provisioned on the IP Trunk 3.0 node and the gatekeeper, the IP Trunk node can never register; therefore, the node cannot use the gatekeeper to place calls. If there is ever a problem with gatekeeper call resolution, check the H.323 ID immediately.
Issue 1.5.4 May 20, 2003
B.1.14
h323CallTrace Safety level: Debug. This command was formerly itgCallTrace. The h323CallTrace is the replacement for 2.x.25 routine itgCallTrace, with additional interface control. The old itgCallTrace function turned on debug tracing for all the H323 channels on the card. This caused a signicant real time impact on a busy switch. The new command and improved interface permits enabling and disabling call trace on a range of channels. The h323CallTrace and its predecessor itgCallTrace otherwise provide the same functionality. Syntax: h323CallTrace where:
Option -1 0 1 2 3 6 = = = = = = Turn Call Call Call Call Call off all channels call tracing tracing off trace output sent to TTY trace output sent to TRCFILE.1 file trace output sent to TTY & TRCFILE.1 file trace output sent to CURRLOG.1 & TRCFILE.1
Option, startChannel, endChannel
startChannel: 0-23 for Pentium and 0-31 for SA endChannel: 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 the startChannel.
ITG> h323CallTrace -1,0,31 Setting ALL channels to OFF value = 0 = 0x0 ITG> ITG> h323CallTrace 1,3,7 Setting CHANNEL 3 to 7 to OPT 1 value = 0 = 0x0 ITG>
Example of output: incoming call set-up trace The following gives the results of the h323CallTrace command for a normal incoming call (with near end auto-answer) followed by a far-end release. Note that the message list has changed signicantly since 2.x.25, which was when the last sample was provided.
Issue 1.5.4 May 20, 2003
Initialize trace channels: 0 to 5, log to screen

ITG> h323CallTrace 1,0,5 Setting CHANNEL 0 to 5 to OPT 1 value = 0 = 0x0
Receive incoming SETUP (to ALERTING)

ITG> 2001 3 18 08:41:49 (NPM) :CH#:0 partnerChannelsNum 1 2001 3 18 08:41:49 (NPM) :CH#:0 partner[0]: transmit[0]: g729AnnexAwAnnexB 2001 3 18 08:41:49 (NPM) :CH#:0 partner[0]: transmit[1]: g729AnnexA 2001 3 18 08:41:49 (NPM) :CH#:0 partner[0]: transmit[2]: g729wAnnexB 2001 3 18 08:41:49 (NPM) :CH#:0 partner[0]: transmit[3]: g729 2001 3 18 08:41:49 (NPM) :CH#:0 partner[0]: transmit[4]: g711Ulaw64k 2001 3 18 08:41:49 (NPM) :CH#:0 partner[0]: transmit[5]: g711Alaw64k 2001 3 18 08:41:49 (NPM) :CH#:0 partner[0]: receive[0]: g729AnnexAwAnnexB 2001 3 18 08:41:49 (NPM) :CH#:0 partner[0]: receive[1]: g729AnnexA 2001 3 18 08:41:49 (NPM) :CH#:0 partner[0]: receive[2]: g729wAnnexB 2001 3 18 08:41:49 (NPM) :CH#:0 partner[0]: receive[3]: g729 2001 3 18 08:41:49 (NPM) :CH#:0 partner[0]: receive[4]: g711Ulaw64k 2001 3 18 08:41:49 (NPM) :CH#:0 partner[0]: receive[5]: g711Alaw64k 2001 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,codec=7 2001 3 18 08:41:49 (NPM) :CH#:0 hsChan 0x229f104 haChan 0x3f6490 2001 3 18 08:41:49 (NPM) :CH#:0 txPayload: 3: vifSize 240 2001 3 18 08:41:49 (NPM) :CH#:0 cmEvChannelSetAddress: isOrigin 0 47.11.215.209:2362 2001 3 18 08:41:49 (NPM) :CH#:0 cmEvChannelParameters,chanName=g729AnnexAwAnnexB,codec=7 2001 3 18 08:41:49 (NPM) :CH#:0 hsChan 0x229f13c haChan 0x3f655c 2001 3 18 08:41:49 (NPM) :CH#:0 rxPayload: 3: vifSize 240 2001 3 18 08:41:49 (NPM) :CH#:0 *** InterOpt: using H323 codec payload negotation 2001 3 18 08:41:49 (NPM) :CH#:0 Call Setup to TSM: g729AnnexAwAnnexB(7): vifSize 240 2001 3 18 08:41:49 (NPM) :CH#:0 hsChan 0x229f13c haChan 0x3f655c 2001 3 18 08:41:49 (NPM) :CH#:0 cmEvChannelSetAddress: isOrigin 1 47.11.215.209:2362 2001 3 18 08:41:49 (NPM) :CH#:0 hsChan 0x229f104 haChan 0x3f6490 2001 3 18 08:41:49 (NPM) :CH#:0 Initiating terminal capability set negotation 2001 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: cmCapReceiveAndTransmit 2001 3 18 08:41:49 (NPM) :CH#:0 [2] g729AnnexA: packetSize 3: cmCapAudio: cmCapReceiveAndTransmit 2001 3 18 08:41:49 (NPM) :CH#:0 [3] g729wAnnexB: packetSize 3: cmCapAudio: cmCapReceiveAndTransmit 2001 3 18 08:41:49 (NPM) :CH#:0 [4] g729: packetSize 3: cmCapAudio: cmCapReceiveAndTransmit 2001 3 18 08:41:49 (NPM) :CH#:0 [5] g711Ulaw64k: packetSize 10: cmCapAudio: cmCapReceiveAndTransmit 2001 3 18 08:41:49 (NPM) :CH#:0 [6] g711Alaw64k: packetSize 10: cmCapAudio: cmCapReceiveAndTransmit 2001 3 18 08:41:49 (NPM) :CH#:0 [7] t38fax: packetSize -1: cmCapData: cmCapReceiveAndTransmit 2001 3 18 08:41:49 (NPM) :CH#:0 Initiating Master/Slave negotation 2001 3 18 08:41:49 (NPM) :CH#:0 {g729AnnexAwAnnexB, g729AnnexA, g729wAnnexB, g729, g711Ulaw64k, g711Alaw64k} 2001 3 18 08:41:49 (NPM) :CH#:0 {t38fax}
Issue 1.5.4 May 20, 2003
Connect the call

2001 3 18 08:42:17 (NPM) :CH#:0 Q931 call setup phase complete 2001 3 18 08:42:17 (NPM) :CH#:0 StateMode: cmCallStateModeCallSetupConnected 2001 3 18 08:42:17 (NPM) :CH#:0 StateMode: cmCallStateModeCallConnected
Receive incoming RELEASE COMPLETE

2001 2001 2001 2001 2001 2001 3 3 3 3 3 3 18 18 18 18 18 18 08:42:33 08:42:33 08:42:33 08:42:33 08:42:33 08:42:33 (NPM) (NPM) (NPM) (NPM) (NPM) (NPM) :CH#:0 :CH#:0 :CH#:0 :CH#:0 :CH#:0 :CH#:0 hsChan 0x229f13c haChan 0x3f655c hsChan 0x229f13c haChan 0x3f655c hsChan 0x229f104 haChan 0x3f6490 hsChan 0x229f104 haChan 0x3f6490 dch_cap 5: cause 16: reason 3 Closing RTP session(0x1e25614).
Issue 1.5.4 May 20, 2003
B.1.15
h323SessionShow Safety level: Debug. Lists the details of the h323Session for all active channels originating IP address, destination IP address, call state, codec used etc. Note that by default, ITG will attempt to accept incoming calls in Round Robin Fashion starting from the lowest available channel up. Outgoing calls (this time based on the Meridian 1 Round Robin Conguration) will be set-up on the highest available channels rst. 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 path IP address for IPT to IPT or ITGT) the Dest number, which is the transmitted number (and may include ESN5 prexes; the Session 31 in the example does) the codec selected the Call Handle (possibly useful for design level debugging depending on the problem, but of little or no use to eld 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 channel 3 - legacy format for ITGT 2.x and BCM 2.5 FP1; remote D channel exists 4 - not currently used 5 - Nortel Networks cross product Interoperability Standard format (IP Trunks 3.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
Issue 1.5.4 May 20, 2003

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 = 0x1 ITG>
Issue 1.5.4 May 20, 2003
B.1.16
i Safety level: Debug/recovery. This command lists all the tasks and task IDs. The user executes this command to make sure that no task is suspended. (Note that temporary task suspension can occur when the user executes various debug commands; this command helps the user ensure that no tasks are still suspended.)
ITG> i NAME ENTRY TID PRI STATUS PC SP ERRNO DELAY ---------- ------------ -------- --- ---------- -------- -------- ------- ----tExcTask _excTask 33c8acc 0 PEND 7711c 33c8a00 3006b 0 tShell _shell 2eb7558 1 READY 2ad934 2eb71ec c0002 0 tPcmciad _pcmciad 33a5d3c 2 PEND 7711c 33a5c70 0 0 tTelnetd _telnetd 2ec81a4 2 PEND 4fd38 2ec809c 0 0 tTelnetOutT_telnetOutTa 1e296ec 2 READY 4fd38 1e29434 3006b 0 tTelnetInTa_telnetInTas 1e281b8 2 READY 2ad450 1e27eb8 0 0 tyLstnr _tyListener 1e26c84 2 PEND 4fd38 1e26bc8 0 0 tMVX_XSPY _XSpyTaskMai 1e89204 7 PEND 7711c 1e8913c 0 0 tNetTask _netTask 30f49f4 20 READY 58080 30f4958 3d 0 tRmm _rmmMain 2be7644 40 PEND 4fd38 2be74bc 0 0 tAioIoTask1_aioIoTask 33b4694 50 PEND 4fd38 33b4614 0 0 tAioIoTask0_aioIoTask 33ad4e8 50 PEND 4fd38 33ad468 0 0 tAioWait _aioWaitTask 33bb840 51 PEND 4fd38 33bb718 0 0 tMVX_DIM _dim_main 1e86698 51 READY 4fd38 1e86604 3d0002 0 tFtpdTask 2c286c 2ec549c 55 PEND 4fd38 2ec5370 0 0 tSntpsTask 2b0b80 2bec93c 56 PEND 4fd38 2bec73c 0 0 baseMMintTa_baseMMintTa 2ae3c94 60 PEND 4fd38 2ae3c0c 0 0 tA07 _a07Task 2ae0674 80 PEND 7711c 2ae05b4 0 0 tIpss _ipssMain 1e71c10 80 PEND 4fd38 1e71ad0 0 0 tNpm _npmMain 2bd8080 90 PEND 4fd38 2bd7e74 46 0 tPortmapd _portmapd 2ec6c70 100 PEND 4fd38 2ec6b04 16 0 tXA _xaTask 2abf10c 100 PEND 7711c 2abf034 0 0 tATPM _atpmTaskSta 1e744cc 100 PEND 7711c 1e743f4 0 0 tTSM _tsmStart 1e6cc44 100 PEND 7711c 1e6cb5c 0 0 tMONTimeSer_monTimeServ 1e52770 100 PEND 4fd38 1e525ec 0 0 tIGCC _igccMain 2adecec 100 PEND 7711c 2adec14 0 0 tUIPC _uipcMain 1e2e154 100 READY 7711c 1e2e090 0 0 tMcciMsgMgr_mcciMain 1e3a650 120 PEND 4fd38 1e3a2fc 0 0 tLogTask _logTask 33c61b0 150 PEND 7711c 33c60e4 0 0 tSnmpd 40f70 2ec23ec 150 PEND 4fd38 2ec1a2c 3d0001 0 tSockReuse _finwait 1e4d7a4 150 DELAY 4ba20 1e4d73c 0 17568 tRCM _rcmMain 2bf42b4 150 PEND 7711c 2bf41dc 0 0 tBootpdTask_vxBootpd 2bede70 199 PEND 4fd38 2bedd00 23 0 tMAM _mamMain 2be9f00 200 PEND 7711c 2be9e40 11 0 tNMMTask _tNMM 1e8d050 200 PEND 7711c 1e8cf8c 0 0 midnightTas_midnightTas 2ea7150 240 DELAY 4ba20 2ea70e8 4 5297143 tMONServer _monServerMa 1e5c708 245 PEND 7711c 1e5c644 0 0 tHSRecvTask_oobHandShak 2beaf04 249 PEND 4fd38 2bead34 0 0 tDcacheUpd _dcacheUpd 3382a9c 250 READY 4ba20 3382a1c 3d0002 0 tOMM _ommMain 2bf25b0 250 PEND 7711c 2bf24f0 0 0 tMONClient _monClientMa 1e5773c 250 PEND 7711c 1e57678 0 0 tMonTask _itgMonitorT 1e2b898 252 DELAY 4ba20 1e2b35c 0 352 value = 0 = 0x0 ITG>
Issue 1.5.4 May 20, 2003
B.1.17
ifShow Safety level: Safe/delays in heavy trafc. This command displays information about the attached network interfaces. The current parameters congured on the ELAN (lnIsa) and TLAN (lnPci) are printed. On the current Master card, two Internet addresses print for the lnPci interface: the rst is the cards TLAN interface IP, the second is the Node IP. Note: lo is the internal software loopback interface. The ethernet address (MAC address) is printed for each interface. A large number of multicast packets received indicates a lot of broadcast trafc on the interface - not a good thing for the ITG card! If no lnPci interface data prints, the card did not boot up correctly and the interface is not congured. Theres a good chance the cards management MAC address doesnt match the MAC address congured in MAT/OTM; if thats true, correct it in MAT/OTM, download the Node properties and reboot the card. The example below is from a Succession Media Card, Node Leader - note the Node IP address on the ixpMac unit 0 interface.
ITG> ifShow ixpMac (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 dropped lo (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 dropped ixpMac (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
Issue 1.5.4 May 20, 2003

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 dropped value = 29 = 0x1d ITG>
The example below is from a Pentium card, Node Leader - note the Node IP address on the lnIsa unit 0 interface.
ITG> ifShow lnIsa (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 dropped lo (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 dropped lnPci (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 dropped value = 29 = 0x1d ITG>
Issue 1.5.4 May 20, 2003
B.1.18
IPInfoShow Safety level: Safe. This command displays a summary of the ITG cards IP conguration from the ITGT prompt. The difference between the SMC and Pentium card output is in the Interface listed. For the SMC card, the following output is seen:
ITG> IPInfoShow Separate Subnet Configuration. Maintenance IP address : 47.11.217.55 Voice IP address : 47.11.215.212 Maintenance subnet mask : 255.255.254.0 Voice subnet mask : 255.255.255.0
ROUTE NET TABLE destination gateway flags Refcnt Use Interface ---------------------------------------------------------------------------0.0.0.0 47.11.215.1 3 4 10163 ixpMac0 47.11.215.0 47.11.215.212 101 0 0 ixpMac0 47.11.216.0 47.11.217.55 101 0 0 ixpMac1 47.11.215.0 47.11.215.212 101 0 0 ixpMac0 ---------------------------------------------------------------------------ROUTE HOST TABLE destination gateway flags Refcnt Use Interface ---------------------------------------------------------------------------127.0.0.1 127.0.0.1 5 0 0 lo0 ---------------------------------------------------------------------------value = 77 = 0x4d = M ITG>
Issue 1.5.4 May 20, 2003
For the Pentium card, the following is seen instead:

ITG> IPInfoShow Maintenance IP address Voice IP address : 47.11.254.50 : 47.11.249.44
Maintenance subnet mask : 255.255.254.0 Voice subnet mask : 255.255.255.0
ROUTE NET TABLE destination gateway flags Refcnt Use Interface ---------------------------------------------------------------------------0.0.0.0 47.11.249.1 3 1 177 lnPci1 47.11.249.0 47.11.249.44 101 0 0 lnPci1 47.11.254.0 47.11.254.50 101 0 0 lnIsa0 47.11.249.0 47.11.249.44 101 0 0 lnPci1 ---------------------------------------------------------------------------ROUTE HOST TABLE destination gateway flags Refcnt Use Interface ---------------------------------------------------------------------------127.0.0.1 127.0.0.1 5 0 0 lo0 ---------------------------------------------------------------------------value = 77 = 0x4d = 'M' ITG>
Issue 1.5.4 May 20, 2003
B.1.19
iptSessionShow [level] Safety level: Debug. This command is analogous to h323SessionShow, with somewhat different capabilities. It has either more information (level 1) or less (level 0, or default). It also provides an options display, used by entering the command with a level other than 0 or 1. Example: what are my options?
ITG> iptSessionShow 44 iptSessionShow parameter error The Options are: * For basic information, Specify 0 or leave blank * For debug information, Specify 1 * For this message, Specify anything else value = 50 = 0x32 = 2 ITG>
Example: show me the basics only. This shows the direction, remote call signalling IP address, and destination number for the currently active calls, with a list of idle channels 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>
Issue 1.5.4 May 20, 2003
Example: show me the full details. This shows the direction, remote call signalling IP address, destination number (with type and plan), outpulsed number (if the H.323 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 capability. It 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>
Issue 1.5.4 May 20, 2003
B.1.20
itgCardShow Safety level: Debug. Check the Leader, Card and Management IP, codecs congured, protocol used and the status of the ELAN and TLAN connections. The following is an example of the data printed, followed by an explanation of the elds. Note that the output is slightly different when comparing Pentium and SMC cards.
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 OK value = 38 = 0x26 = &
SMC card output

ITG> itgCardShow Index Type Role Leader IP RTP Base Port Card IP Card MgntIP Ldr MgntIP Card TN : : : : : : : : : 1 ITG2 Leader 47.11.215.211 2300,2300=>Default, 17300=>CISCO RTPHeader Compression 47.11.215.212 47.11.217.55 47.11.217.55 6 0 0
Issue 1.5.4 May 20, 2003

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 Operation value = 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 le is missing or has not been parsed properly. Check to make sure that the bootp.1 le is in the BOOTP directory. Look for alarms / error messages on the TTY console. b. Follower or Backup Leader card: this indicates the card could not locate its BOOTP server/Leader card or could not communicate with it. Ensure that the Leader card has the Follower/Backup Leader entry in its bootp.1 le. If that is ok, check all the cable connections (TLAN). Next check for error/alarms on the TTY console and MAT. May need to log the RMM and MAM modules if the problem persists. 2. RTP Port Range: Identies what the IP port range is on the T-LAN interface for RTP packets. The default uses port ranges from 2300 to 2346. It can be optionally congured for port ranges from 17300 to 17346 which will support RTP Header Compression enabled routers. 3. DCHIP is YES and Version is 0.0: DCHIP YES indicates that it is congured on the card. Version 0.0 indicates that the card cannot establish connection with the DCH PC Card. It indicates either the PC Card is missing, is not properly seated, has no software load on it or is bad. The PC Card can be inserted into any laptop to verify the software on the card. 4. EC Tail Length: This is applicable only to ITG2.0 Pentium and 80486 based Products. It identies the currently congured Echo Canceller Tail Length (either a default of 128ms or a value as presented by the OTM/MAT conguration). 5. Ethernet interface carrier status:
Issue 1.5.4 May 20, 2003
lnPci Stat interface speed and carrier status of the TLAN interface. lnPci BCast Filter - only refers to ITG2.0 Pentium cards. This identies that physical layer Broadcast ltering is enabled on the card, to be activated in Broadcast 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 to that interface. 6. initBchNum: Is the rst B channel number on the card. The rest of the B channel numbers are consecutive. This number should match the B channel number congured on M1. 7. Card State: ENBL : The card is congured and operational DSBL : The card is congured but out of service. Enable from M1. UNEQ : The card is not congured in M1. MBSY : The card is busy / no channels available as some system utility is running in the background. FALLBACK : The card is out of service as all the available channels are busied out. 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 remote nodes. Check the network conditions/ trafc. 8. In IP Trunk 3.0 there is now the additional eld of Local RingBack. In prior versions of ITG Trunk, if local ringback was required (out of band ringback), it was always generated on ITG Trunk card. In IP Trunk 3.0, the locally generated ringback on the IP Trunk card can be turned off and the Meridian 1 can be relied upon to generate local ringback. The Meridian 1 needs to be patched or upgraded to Release 26 to allow this to happen. By relying on the Meridian 1 for out of band ringback the correct local ringback will be used instead of the default North American ringback. For more information about disabling local ringback on the IP Trunk card see commands useIPTForRingBack (section B.1.44, pg 169) and useM1ForRingBack (section B.1.45, pg 169).
Issue 1.5.4 May 20, 2003
B.1.21
itgChanStateShow Safety level: Safe. This command lists the state busy / idle / mbsy / uneq for all the channels on the card. This helps the user see if there are active calls on the card or which channel is being 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 congured, then every 4th unit will always be busy1, for the ITG-P (Pentium) card, if image 3 (G.729) is congured, then every 3rd unit will 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. On the SMC card the operation and result are the same, except that more channels are displayed.
ITG> itgChanStateShow Channel Channel Channel Channel Channel Channel Channel Channel Channel Channel Channel Channel Channel Channel Channel Channel 0 : Busy 1 : Idle 2 : Idle 3 : Idle 4 : Idle 5 : Idle 6 : Idle 7 : Idle 8 : Idle 9 : Idle 10 : Idle 11 : Idle 12 : Idle 13 : Idle 14 : Idle 15 : Idle
1. Due to codec support on DSP processing, MIPS requirement, the max supported channels per DSP is reduced by one. 2. Due to codec support on DSP processing, MIPS requirement, the max supported channels per DSP is reduced by one.
Issue 1.5.4 May 20, 2003

Channel Channel Channel Channel Channel Channel Channel Channel 16 17 18 19 20 21 22 23 : : : : : : : : Idle Idle Idle Idle Idle Idle Idle Idle
value = 1 = 0x1
B.1.22
itgMemShow Safety level: Debug. This command prints general information on the Mix memory available on the ITG card. total amount of Mix memory blocks congured. 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
Issue 1.5.4 May 20, 2003
B.1.23
itgMsgCtrShow Safety level: Debug. Various message counters kept by the different tasks on the ITG card can be displayed using this command. Note:
Number of hooksend ISDN messages:
indicates the number of messages of the listed types sent by H.323 to the IP network
Number of hookrecv ISDN messages:
indicates the number of messages of the listed types received by H.323 from the IP network
Number of corrupted messages:
indicates the number of messages of the listed types received by H.323 from the IP network that were invalid due to message corruption
Port 0: Message Log
indicates the number of messages of the listed types transmitted or received by the ISDN layer 3 application. CC is from the application; the rest are from the PBX. 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 translate as 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.
Issue 1.5.4 May 20, 2003
B.1.24
ldrResTableShow Safety level: Debug. Most nodes have either one or a small number of cards per node. If an IPT 3.0 node has more than one card in the system, then this table (on the Leader card only) lists all of the ITG cards in the node with their IP address, associated DCH and number of trunks. If a card doesnt appear that should be there, then the registration process between the Follower and Leader was not successful. (An explanation of the elds follows the examples below.) The following is an example displaying a single card node; if there should have been more, then the specic missing card is unregistered, and the user should investigate further.
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 = 0x1 ITG>
The following is an example showing a two card node. Again, if there should have been more, then the specic missing card is unregistered, and the user should investigate 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 = 0x1 ITG>
Issue 1.5.4 May 20, 2003
The following provides a description of the headers and row contents: Table 4: Explanation of information in the ldrresTableShow output
Field idx role ipAddr ipDCHIP #Prvs #Idle DCH# Dstat DCAP Description Card index Card role (Ldr, D-channel leader, Flr) Cards voice interface IP address IP address for cards DCHIP leader (ELAN) Number of provisioned channels Number of channels idle DCH number this card is associated with Status of that DCH Congured DCH capability
B.1.25
ll Safety level: Debug. This command lists the contents of the current directory, with timestamp and size information. Besides allowing comparison of a les timestamp to another, this command is useful in checking for zero length les which may indicate disk corruption (see section 15 Formatting the /C: Drive on page 96 for details) or a new system (for example, DPTABLE.1 is zero length until the dial pan information is downloaded to the system). The example shows a list of the BOOTP directory.
ITG> pwd /C:/bootp value = 10 = 0xa ITG> ll drwxrwxrwx 1 0 drwxrwxrwx 1 0 -rwxrwxrwx 1 0 -rwxrwxrwx 1 0 value = 0 = 0x0 ITG>
0 0 0 0
4096 4096 241 249
Feb Mar Feb Feb
10 16 10 10
12:00 03:40 12:00 11:56
./ ../ BOOTP.1 BOOTP.2
Issue 1.5.4 May 20, 2003
B.1.26
numNodesInFallbackShow Safety level: Debug. This command prints all the remote IP that are in fallback at a given time. The rst example shows the command issued when there are no nodes in fallback.
ITG> numNodesInFallbackShow Nodes In Fallback = 0 value = 1 = 0x1 ITG>
This example shows the command issued when there is one node in fallback. Also, for the sake of illustrating it in the VxWorks shell, it is shown at the -> prompt.
-> numNodesInFallbackShow Nodes In Fallback = 1 44.11.223.221 value = 1 = 0x1 ->
B.1.27
NVRClear Safety level: Destructive/Debug. May be used as part of the process of making a card into a leader; recommended not to use this, though. Erases the ELAN IP data, Leader ag and returns the shell login and shell timeout to their default values. Be careful when using this because it makes the card appear as a Follower but wont do a BOOTP request. It is better to use the clearLeader (section B.1.7, pg 122) command if returning a Leader card to Follower status or the command shellPasswordNvramClear (section B.2.55, pg 222) if trying to reset the shell password. If it is used to cleanup the NVRAM, follow it with the clearLeader or setLeader IPaddr,gwIPaddr,subnetMask (section B.1.39, pg 165) command.
ITG> NVRIPShow IP address : 192.168.1.14 Gateway : 192.168.1.1 Subnet Mask: 255.255.255.128 Set as Leader. Set to use IP address parameters in NVRAM. value = 43 = 0x2b = '+' ITG> NVRClear value = 0 = 0x0 ITG> NVRIPShow IP address : 255.255.255.255 Gateway : 0.0.0.0 Subnet Mask: 0.0.0.0 Set as Follower. Warning : Set as Follower, but will boot using IP parameters in NVRAM instead of bootp.
Issue 1.5.4 May 20, 2003

value = 88 = 0x58 = 'X'
B.1.28
NVRGWSet gwIPaddr Safety level: Destructive/Debug. Sets the cards ELAN gateway IP address in the NVRAM. It may cause cards to become unavailable if invalid addresses are entered. By preference, use setLeader IPaddr,gwIPaddr,subnetMask (section B.1.39, pg 165) instead.
Issue 1.5.4 May 20, 2003
B.1.29
NVRIPSet IPaddr Safety level: Destructive/Debug. Sets the cards ELAN IP address in the NVRAM. It may cause cards to become unavailable if invalid addresses are entered. By preference, use setLeader IPaddr,gwIPaddr,subnetMask (section B.1.39, pg 165) instead.
B.1.30
NVRIPShow Safety level: Debug. Prints the information programmed in the cards NVRAM. This is useful when trying to determine if the data congured via the setLeader command is correct on the card.
ITG> NVRIPShow IP Address from NVRAM: 47.11.217.55 IP address : 47.11.217.55 Gateway : 47.11.217.1 Subnet Mask: 255.255.254.0 Set as Leader. Set to use IP address parameters in NVRAM. value = 43 = 0x2b = + ITG>
B.1.31
NVRSMSet subnetMask Safety level: Destructive/Debug. Sets the cards ELAN subnet mask in the NVRAM. It may cause cards to become unavailable if invalid masks are entered. By preference, use setLeader IPaddr,gwIPaddr,subnetMask (section B.1.39, pg 165) instead.
Issue 1.5.4 May 20, 2003
B.1.32
ping IPaddr, numPings Safety level: Safe. This command sends an ICMP ECHO_REQUEST packets to a network host, specied by the parameter IPaddr in dotted notation. The host matching the destination address in the packets responds to the request. If a response is not returned in less than 5 seconds, the sender times out. This command is useful to determine if other hosts or ITG cards are properly communicating with the sender card. The parameter numPings species how many packets to receive; if omitted, pings continue until stopped by entering Ctrl-C. Otherwise, pings are sent until the specied number of responses are received. The percentage packet loss is then calculated from the ratio of received to sent messages.
ITG> ping 10.0.0.2,5 PING 10.0.0.2: 56 data bytes 64 bytes from 10.0.0.2: icmp_seq=0. time=0. ms 64 bytes from 10.0.0.2: icmp_seq=1. time=0. ms 64 bytes from 10.0.0.2: icmp_seq=2. time=0. ms 64 bytes from 10.0.0.2: icmp_seq=3. time=0. ms 64 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 loss round-trip (ms) min/avg/max = 0/0/0 value = 0 = 0x0
B.1.33
pwd Safety level: Debug. This command shows the current directory path. Note that if the path shown is only host: youll need to cd /C: to make the other directories visible.
ITG> pwd /C:/bootp value = 10 = 0xa ITG>
B.1.34
resetOM Safety level: Debug. This command writes the current OM counter values to the OMREPORT.nnn le and resets the counters to zero.
ITG> resetOM value = 0 = 0x0 ITG>
Issue 1.5.4 May 20, 2003
B.1.35
routeAdd destIPaddr, gwIPaddr Safety level: Safe. Adds a route to the network routing tables. The parameter destIPaddr is the destination IP address in dotted notation; gwIPaddr is the gateway IP address in dotted notation. This change is not permanent; rebooting the card rebuilds the routing table from the data in the CONFIG1.INI le. However, if necessary it can be added to a startup le.
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, and can lead to call processing and/or system administration problems if the wrong route entries are deleted. This command deletes a route from the network routing tables. The parameter destIPaddr is the destination IP address in dotted notation; gwIPaddr is the gateway IP address in dotted notation. This change is not permanent; rebooting the card rebuilds the routing table from the data in the CONFIG.INI le.
ITG> routeDelete 192.168.1.128,192.168.1.140 value = 0 = 0x0
B.1.37
routeShow Safety level: Debug. This command prints the card's IP network and host routing tables. By reading the output the user may verify that all of the congured routes as well as the dynamic routes are in the table.
ITG> routeShow ROUTE NET TABLE destination gateway flags Refcnt Use Interface ---------------------------------------------------------------------------0.0.0.0 47.11.215.1 3 4 10895 ixpMac0 47.11.215.0 47.11.215.212 101 0 0 ixpMac0 47.11.216.0 47.11.217.55 101 0 0 ixpMac1 47.11.215.0 47.11.215.212 101 0 0 ixpMac0 ---------------------------------------------------------------------------ROUTE HOST TABLE destination gateway flags Refcnt Use Interface ---------------------------------------------------------------------------127.0.0.1 127.0.0.1 5 0 0 lo0 ---------------------------------------------------------------------------value = 77 = 0x4d = M
Issue 1.5.4 May 20, 2003
B.1.38
serialNumShow Safety level: Safe. Displays the ITG cards serial number data.
ITG> serialNumShow Serial 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 cards NVRAM so that on reboot the card comes up as a Leader 0. The parameter IPaddr is the cards ELAN IP address, gwIPaddr is the ELAN gateway IP address and subnetMask is the ELAN subnet mask. This command also sets the Leader ag and the BOOTP ag such that the IP information 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.183 IP address : 47.11.217.183 Gateway : 47.11.216.1 Subnet Mask: 255.255.254.0 Set as Leader. Set to use IP address parameters in NVRAM. /C:/ - Volume is OK Settings 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 userid and password must be between 8 and 10 characters. They are both stored in the NVRAM. The new userid and password take effect the next time you login. See VxWorks shell command shellPasswordNvramClear (section B.2.55, pg 222).
ITG> shellPasswordSet Enter current username:itgadmin Enter current password: Enter new username:itgadmin1 Enter new password: Enter new password again to confirm:value = 0 = 0x0 ITG>
Issue 1.5.4 May 20, 2003
B.1.41
swDownload srvrIP, uid, passwd, path, fname Safety level: Destructive/Normal. Normal means of placing software on the card when not using OTM server; however, it leaves the card vulnerable to a reboot in mid-download. This command downloads the IPT application binary from the specied FTP server, compresses it and stores it in the ITG cards Flash memory. The parameter srvrIP is the FTP servers IP address, the parameters uid and passwd are used to login to the server, path and fname are the path and name of the le on the server to retrieve. The command executes from the IPT, VxWorks and BIOS CLIs. File is on the ITG's /C: drive (previously FTPd there):
ITG> swDownload 127.0.0.1,itgadmin,itgadmin,<path>,<fname>
File is on another ITG's /C: drive (previously FTPd there):

ITG> swDownload <ITG ELAN IPaddr>,itgadmin,itgadmin,<path>,<fname>
File is on the MAT/OTM PC:

ITG> swDownload <PCs IP addr>,itguser,itguser,addr>,itguser,itguser,,<fname>
File is on a network FTP server:

ITG> swDownload <servers IP addr>,<uid>,<pswd>,<path>,<fname>
B.1.42
swVersionShow Safety level: Safe. This command prints the cards ITGT application software version. Note that for IPT 3.0, the issue includes the date built. In the example, the load was compiled on the 3d of March, 2003.
ITG> swVersionShow Installed Image: IPT IPT-3.00.52_03_06_2003.522 (ITG SA) - Thursday March 15:54:40 EST 2003 value = 99 = 0x63 = c ITG> 6
Issue 1.5.4 May 20, 2003
B.1.43
tsmChanShow [level[,channel]] Safety level: Debug; may slow trafc under heavy load. This command prints the TSM (Telephony Signalling Module) view of the calls. It is analogous to h323SessionShow, but for the call states and information on the PBX side of 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 22 tsmChanShow Error Format: 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 Alaw Ch 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 = 0x1d ITG> ITG> ITG>
Issue 1.5.4 May 20, 2003

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 Alaw Ch 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 27 28 29 30 value = 2 = 0x2 ITG> 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 = 0x1d ITG>
Issue 1.5.4 May 20, 2003
B.1.44
useIPTForRingBack Safety level: Safe. This command is used to turn on local ring back generation on the IP Trunk card. By default, the IP Trunk card will continue generate local ringback for out of band ringback. This command is only of use if local ringback has been turned off on the card by the command useM1ForRingBack or by an attribute in the CONFIG1.INI le. The issue with using the IP Trunk card is that North American ringback is generated. If this is an issue, the customer needs to patch the Meridian 1 to generate local ringback and use the command useM1ForRingBack.
Although, it should be noted that ITG Trunk and IP Trunk use in band ringback. That is, the ringback comes from the destination side in the voice path. It is only when interoperating 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. By 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 ensuring that the M1 is used for local ringback is to add to CONFIG1.INI the lines:
The need to rely upon the Meridian 1 to generate local ring back is due to the issue that the IP Trunk card only generates North American ringback. If this is an issue, the customer needs to patch the Meridian 1 to generate local ringback and use this command. Although, it should be noted that ITG Trunk and IP Trunk use in band ringback. That is, the ringback comes from the destination side in the voice path. It is only when interoperating with other endpoints that out of band ring back may be used.
Issue 1.5.4 May 20, 2003
B.1.46
vxWorksShell Safety level: Debug. Use this command to login and access the OS shell when doing debugging of commands that require this shell.
ITG> vxWorksShell login:<login user name> password:<login password> Welcome to the VxWorks Shell WARNING: Data entry errors in this shell could cause loss of service. Use itgShell to return to the ITG shell. value = 3382232 = 0x339bd8 = _shellHistSize + 0x4
Issue 1.5.4 May 20, 2003
B.2
Commands only accessible from the -> prompt

B.2.1 arpFlush Safety level: Safe/delay. calls to addresses ushed from the memory will be delayed slightly, but the table rebuilds itself. Flushes all non-permanent entries from the cards ARP cache. Permanent entries are added via provisioning operations; all others are non-permanent.
-> arpShow LINK LEVEL ARP TABLE destination gateway flags Refcnt Use Interface -------------------------------------------------------------------------192.168.1.10 00:00:75:45:38:aa 405 1 1081508 lnIsa0 192.168.1.14 00:60:38:01:09:fa 405 2 1836 lo0 192.168.1.102 00:c0:4f:ae:a8:39 405 1 3 lnIsa0 192.168.1.140 00:60:38:01:a1:46 405 0 6 lo0 192.168.1.141 00:60:38:76:21:af 405 0 201 lnPci1 192.168.1.142 00:60:38:76:21:a9 405 3 136956 lnPci1 -------------------------------------------------------------------------value = 75 = 0x4b = 'K' -> -> arpFlush value = 0 = 0x0 -> arpShow LINK LEVEL ARP TABLE destination gateway flags Refcnt Use Interface -------------------------------------------------------------------------192.168.1.14 00:60:38:01:09:fa 405 2 1936 lo0 192.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 cards system ARP table.
-> arpShow LINK LEVEL ARP TABLE destination gateway flags Refcnt Use Interface -------------------------------------------------------------------------192.168.1.10 00:00:75:45:38:aa 405 1 1081508 lnIsa0 192.168.1.14 00:60:38:01:09:fa 405 2 1836 lo0 192.168.1.102 00:c0:4f:ae:a8:39 405 1 3 lnIsa0 192.168.1.140 00:60:38:01:a1:46 405 0 6 lo0 192.168.1.141 00:60:38:76:21:af 405 0 201 lnPci1 192.168.1.142 00:60:38:76:21:a9 405 3 136956 lnPci1 -------------------------------------------------------------------------value = 75 = 0x4b = 'K' ->
Issue 1.5.4 May 20, 2003
B.2.3
attrib lename,protection Safety level: Destructive Debug. The user can make a le that should be protected unprotected, allowing it to be edited, or to protect an unprotected one. This command is only available on the Succession Media Card. This command changes the le protection of a le. This is used so that a craftsperson can either enable or disable write protection on a le on the ITG card DOS drive. The level of protection is: +Radd write protection to the le -Rremove write protection from the le
-> ll -rwxrwxrwx 1 0 0 -rwxrwxrwx 1 0 0 drwxrwxrwx 1 0 0 drwxrwxrwx 1 0 0 drwxrwxrwx 1 0 0 drwxrwxrwx 1 0 0 drwxrwxrwx 1 0 0 drwxrwxrwx 1 0 0 drwxrwxrwx 1 0 0 drwxrwxrwx 1 0 0 drwxrwxrwx 1 0 0 value = 0 = 0x0 -> attrib /C:/exec,+R value = 0 = 0x0 -> ll -r-xr-xr-x 1 0 0 -rwxrwxrwx 1 0 0 drwxrwxrwx 1 0 0 drwxrwxrwx 1 0 0 drwxrwxrwx 1 0 0 drwxrwxrwx 1 0 0 drwxrwxrwx 1 0 0 drwxrwxrwx 1 0 0 drwxrwxrwx 1 0 0 drwxrwxrwx 1 0 0 drwxrwxrwx 1 0 0 value = 0 = 0x0 ->
6603692 Feb 18 10:25 exec 8 Jan 1 2001 ataTest.txt 4096 Feb 12 08:12 LOG/ 4096 Jan 1 2001 TRACE/ 4096 Feb 17 09:29 TABLE/ 4096 Feb 18 00:00 OM/ 4096 Jan 1 2001 DSP/ 4096 Jan 1 2001 KEYCODE/ 4096 Feb 11 10:13 BOOTP/ 4096 Feb 17 09:29 CONFIG/ 4096 Feb 19 09:29 H323/
6603692 Feb 18 10:25 exec 8 Jan 1 2001 ataTest.txt 4096 Feb 12 08:12 LOG/ 4096 Jan 1 2001 TRACE/ 4096 Feb 17 09:29 TABLE/ 4096 Feb 18 00:00 OM/ 4096 Jan 1 2001 DSP/ 4096 Jan 1 2001 KEYCODE/ 4096 Feb 11 10:13 BOOTP/ 4096 Feb 17 09:29 CONFIG/ 4096 Feb 19 09:29 H323/
Issue 1.5.4 May 20, 2003
B.2.4
chkdsk dev, repairLevel, entryLevelType Safety level: Destructive Debug. If repairing damage or freeing damaged clusters, necessary information may be lost, resulting in unpredictable behaviour. However, if corruption exists, it is usually safer to x it than to leave it corrupted. Note: this command may have severe consequences if run during trafc, as it makes the partition under scan unavailable. The chkdsk utility can be used to identify if there is any corruption on the C: drive. It checks the disk and prints a report of the results. An option allows the utility to correct any problems found. While chkdsk is running, other routines and tasks cannot access the partition. The parameter dev species the drive to check and should be set to /C: when checking the ITG cards internal Flash disk. The parameter repairLevel species the action to be taken. All options check the disk, report statistics and report any errors found. Valid values for repairLevel are: 0 - do not write to disk, only report errors found (default) 1 - repair any damages, preserving or salvaging information in special les created automatically under the root directory of dev 2 - do not attempt to salvage any information, return any clusters with damaged or partial information to the pool of free space The parameter entryLevelType species the condition of the disk. It has the following values (0 is the normal value used): 0 - disk not fully used or average le is more than 16 clusters 1 - average le is about 4 clusters in size 2 - disk is full, small les about 1 cluster in size on the average
-> chkdsk /C:,0,0 Copyright (c) 1993-1996 RST Software Industries Ltd. Israel. All rights reserved ver: 2.6 FCS Disk Check In Progress ... total disk space (bytes) : bytes in each allocation unit : total allocation units on disk : bad allocation units : available bytes on disk : available clusters on disk : maximum available contiguous chain (bytes) : available space fragmentation (%) : clusters allocated : Done Checking Disk. value = 0 = 0x0 -> 3,923,968 2,048 1,916 0 2,037,760 995 1,935,360 6 921
Issue 1.5.4 May 20, 2003
B.2.5
devs Safety level: Debug. This command provides a listing of the assorted devices and systems mounted on the ITG card. This allows the user to determine whether necessary devices such as the le system have been correctly mounted. In the following example, the le system has not been mounted.
BIOS> devs drv name 0 /null 1 /tyCo/0 1 /tyCo/1 5 host: 6 /pty/telnet.S 7 /pty/telnet.M value = 25 = 0x19
Typically, this command is most useful on the Pentium card.

-> devs drv 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 mixSelMTS value = 25 = 0x19 ->
However, it can also be used on an SMC card.

-> devs drv 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 mixSelMTS value = 25 = 0x19 ->
Issue 1.5.4 May 20, 2003
B.2.6
DimECStat = 1/0 This is a variable. Setting this to 1 causes the DSP statistics normally printed by the tsm_stat_req_ecdbg TCID or reqECDbg TCID (section B.2.64.1, pg 229) command to be printed at the end of any call using a gateway channel. This provides a useful means to collect information about the echo cancellers performance during a call. No identifying information about the call (other than the TCID and timestamp) are given, so if information about a particular call is needed, use tsmChanShow [level[,channel]] (section B.1.43, pg 167) while the call is active to identify the channel being used. This is cleared by setting the variable to 0. The default is off; the state is not saved and returns to off 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 Stats SEP 27 08:28:41 tMVX_DIM: Info CNV state = 1 SEP 27 08:28:41 tMVX_DIM: Info Px level = 697226 SEP 27 08:28:41 tMVX_DIM: Info Py level = 0 SEP 27 08:28:41 tMVX_DIM: Info Pe level = 340 SEP 27 08:28:41 tMVX_DIM: Info Post update cnt = 836 SEP 27 08:28:41 tMVX_DIM: Info Attempt update cnt = 836 SEP 27 08:28:41 tMVX_DIM: Info Divergence cnt = 0 SEP 27 08:28:41 tMVX_DIM: Info ERLE bypass cnt = 328 SEP 27 08:28:41 tMVX_DIM: Info XTONE count = 6 SEP 27 08:28:41 tMVX_DIM: Info Fore switch cnt = 12 SEP 27 08:28:41 tMVX_DIM: Info Back switch cnt = 10 SEP 27 08:28:41 tMVX_DIM: Info Xidle count = 2825 SEP 27 08:28:41 tMVX_DIM: Info Other bypass cnt = 48
Issue 1.5.4 May 20, 2003
B.2.7
dimPrintChannelInfo TCID Safety level: Debug/output load. This may cause messaging delays but should have minimal effect. This query displays the data congured for the channel specied in the parameter TCID (valid values in the range 0 - 23 for the 24 port card, or 0-31 for the 32 port card). The data printed should match the data congured in the OTM application for this card. 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: 0 value = 23 = 0x17 ->
The coding type indicates the codec used. It has the following values: 8 - G.711 A-law 9 - G.711 mu-law 68 - G.729A 70 - G.729AB The vif size indicates the number of bits to pack per packet. This is related to the packet time and the codec type. The equations are: G.711: vif size = packet time(msec) * 64
Issue 1.5.4 May 20, 2003
G.729: vif size = packet time(msec) * 8
As was stated above, this command is useful on the Pentium card. However, this command 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: 0 value = 23 = 0x17 ->
Issue 1.5.4 May 20, 2003
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-1 for ITG Trunk 486 product and 0-7 for ITG Trunk Pentium product.
-> dspFatalErrorCountClear 1 DSP 1 fatal error count cleared dsp_is: dsp_no 1, mask ffffffbf 1996 1 5 21:09:12 (TSM) :DSP# 1 returned to service value = 6 = 0x6
B.2.9
dummy_trap Safety level: Debug. This command sends an SNMP test message to the server. It helps to prove in the conguration by sending a message for SNMP, ensuring that the provisioning and network are able to transmit SNMP traps.
-> dummy_trap value = 0 = 0x0 -> 1996 1 5 20:00:03 (SNMP) :dummy: setting up alarm struc 1996 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> vxWorksShell login:<login user name> password:<login password> Welcome to the VxWorks Shell WARNING: Data entry errors in this shell could cause loss of service. Enter itgShell to return to the ITG shell. value = 3542528 = 0x360e00 = shellHistSize + 0x4 -> exit ITG>
Issue 1.5.4 May 20, 2003
B.2.11
flashCongShow Safety level: Debug. This command allows the user to display information about the ITG cards Flash memory conguration. It can be executed from either the BIOS or the VxWorks shells. The output varies based on card type. For the Pentium card, the following output is received.
-> flashConfigShow Entered flashDrvInit() with parameters: Base Address : 08000000 Max length : 00200000 flash_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 : 16MB value = 0 = 0x0 ->
For the SMC card, the following output is received.

-> flashConfigShow Flash Vendor ID Flash device ID Flash device type Flash base addr Flash sector count Flash device width Flash chip count Flash device size value = 0 = 0x0 -> : : : : : : : : 0x89 0x15 i28f640j5 0xf9800000 64 2 1 8MB
Issue 1.5.4 May 20, 2003
B.2.12
h and command history handling Safety level: Debug. This command displays the last 20 commands entered at the VxWorks shell prompt. This shell history mechanism is similar to the UNIX Korn shell history function. Prior commands can be recalled, edited and executed using it, speeding debugging when the same or similar commands must be entered repeatedly. An ESC key entered at the VxWorks shell switches the shell to edit history mode. A RETURN key always gives the line to the shell and exits edit mode. Note the default value for n is 1. The following are a few of the more useful editing commands. Movement and searching nG - go to command n nk - get the nth previous shell command in history. Just entering k returns the last command entered. /s - search for string s backward in history ?s - search for string s forward in history nh - move left n characters. nl (or nSPACE) - move right n characters. nw - move n words forward nb - move n words back fc - nd character c, searching forward Fc - nd character c, searching backward $ - go to end of line 0 - go to start of line Insertion (input is expected until an ESC is pressed) a - append A - append at end of line cl (or c SPACE) - change character (deletes character and enters input mode) 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 - delete n characters starting at the cursor nX - delete n 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
Issue 1.5.4 May 20, 2003
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 mode CTRL+L - redraw line CTRL+D - complete symbol name RETURN - 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 h value = 0 = 0x0 ->
B.2.13
icmpstatShow Safety level: Safe. Displays statistics for the ICMP protocol.
-> icmpstatShow ICMP: 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
Issue 1.5.4 May 20, 2003

echo: 434 434 message responses generated value = 33 = 0x21 = ! ->
B.2.14 B.2.14.1
igccAddTrace, igccNoTrace igccAddTrace channel Safety level: Debug. This command, used with B.2.54 setTraceOption channel,outputLocation on page 220, enables limited tracing in the IGCC module. Tracing is limited to receive and build, indicating the function, the message type, and the ISL channel ID. The command uses its own capabilities to dene the channel ID, as the ISL channel number is in the range 1-382. The TSM and NPM use the TCID is 0-31, and may not be 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=32 2001 4 25 08:46:16 (IGCC) :CH#:0 buildUipeMsg: msgType=9, chid=32 ...
B.2.14.2
igccNoTrace Safety level: Debug. Use this command to turn off tracing the IGCC channel.
B.2.15
inetstatShow Safety level: Debug. This command displays information on all of the active IP sockets.
-> inetstatShow Active Internet connections (including servers) PCB Proto Recv-Q Send-Q Local Address -------- ----- ------ ------ -----------------3157898 TCP 0 0 47.11.215.209.1077 3157580 TCP 0 0 47.11.215.209.1720 31573f4 TCP 0 0 47.11.215.209.1075 3157790 TCP 0 0 0.0.0.0.1074 3157604 TCP 0 0 47.11.215.209.1073 3157370 TCP 0 0 47.11.217.54.23 31570dc TCP 0 0 0.0.0.0.6001 3156fd4 TCP 0 0 0.0.0.0.1720 3156a28 TCP 0 0 0.0.0.0.111
Foreign Address -----------------47.11.215.212.1074 47.11.215.212.1072 47.11.215.212.1069 0.0.0.0.0 47.11.215.212.1720 47.11.181.36.34223 0.0.0.0.0 0.0.0.0.0 0.0.0.0.0
(state) ------ESTABLISHED ESTABLISHED ESTABLISHED LISTEN ESTABLISHED ESTABLISHED LISTEN LISTEN LISTEN
Issue 1.5.4 May 20, 2003

3156920 TCP 3156818 TCP 31574fc UDP 3157688 UDP 31572ec UDP 3157268 UDP 31571e4 UDP 3157160 UDP 3157058 UDP 3156f50 UDP 3156ecc UDP 3156e48 UDP 3156cbc UDP 3156bb4 UDP 3156b30 UDP 3156aac UDP 31569a4 UDP value = 1 = 0x1 -> 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0.0.0.0.23 0.0.0.0.21 0.0.0.0.2300 0.0.0.0.2362 0.0.0.0.0 0.0.0.0.0 0.0.0.0.0 0.0.0.0.15000 0.0.0.0.5000 0.0.0.0.1719 0.0.0.0.2002 0.0.0.0.2001 0.0.0.0.7043 0.0.0.0.67 0.0.0.0.123 47.11.217.54.161 0.0.0.0.111 0.0.0.0.0 0.0.0.0.0 0.0.0.0.0 0.0.0.0.0 0.0.0.0.0 0.0.0.0.0 0.0.0.0.0 0.0.0.0.0 0.0.0.0.0 0.0.0.0.0 0.0.0.0.0 0.0.0.0.0 0.0.0.0.0 0.0.0.0.0 0.0.0.0.0 0.0.0.0.0 0.0.0.0.0 LISTEN LISTEN
Issue 1.5.4 May 20, 2003
B.2.16
iosFdShow Safety level: Debug. Displays all of the le descriptors in use.

-> iosFdShow fd name 3 /tyCo/0 4 /tyCo/1 5 /aioPipe 6 (socket) 7 (socket) 8 (socket) 9 (socket) 10 (socket) 11 (socket) 12 /C:/LOG/CURRLOG.1 13 (socket) 14 mixSelRMM 15 (socket) 16 (socket) 17 (socket) 18 (socket) 19 (socket) 20 mixSelNPM 21 /pipe/ipssSig 22 mixSelMTS 23 (socket) 24 (socket) 25 (socket) 26 (socket) 27 (socket) 28 (socket) 29 /C:/LOG/AUDIT.HIS 30 (socket) 31 /pty/telnet.M 32 /pty/telnet.S 33 (socket) 34 (socket) 35 (socket) 36 (socket) 38 (socket) 39 (socket) 40 (socket) value = 32 = 0x20 = -> drv 1 2 3 5 5 5 5 5 5 4 5 3 5 5 5 5 5 3 3 3 5 5 5 5 5 5 4 5 8 7 in out err 5 5 5 5 5 5 5
Issue 1.5.4 May 20, 2003
B.2.17
ipstatShow Safety level: Debug. 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 Safety level: Debug. This command clears the count for both the number of exceptions in the last hour and the total number of exceptions since the last boot-up.
--> itgExcpCountClear ITG exception counters cleared value = 31 = 0x1f
B.2.19
itgExcpCountShow - Pentium card only Safety level: Debug. This command prints the details regarding exceptions on the card. This consists of the count for both the number of exceptions in the last hour and the total number of exceptions 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
Issue 1.5.4 May 20, 2003
B.2.20
itgShell Safety level: Debug. Exit the VxWorks shell and re-enter the ITG shell.
ITG> vxWorksShell login:<login user name> password:<login password> Welcome to the VxWorks Shell WARNING: Data entry errors in this shell could cause loss of service. Enter itgShell to return to the ITG shell. value = 3542528 = 0x360e00 = shellHistSize + 0x4 -> itgShell ITG>
B.2.21
lkup string Safety level: Debug. This VxWorks command (accessible from the VxWorks shell only) searches the symbol table and lists any symbol found containing string. This command is useful when looking for a command, global variable, or function but you cant remember the exact spelling. The search string is case-sensitive, so try the various upper and lower case combinations if the rst search fails. The following is an example of a search for the command numNodesInFallbackShow using numn as the search string. As nothing was found, the user re-enters the command with the case changed from numn to numN.
-> lkup numn value = 0 = 0x0 -> lkup numN numNodesInFallback numNodesInFallbackShow rtcpGetEnumNext getEnumNameId value = 0 = 0x0 ->
0x007dd630 0x000f746c 0x001e05d8 0x0020649c
bss text text text
Issue 1.5.4 May 20, 2003
B.2.22
lnIsaBroadcastShow - not applicable, SMC See also mac21440BroadcastShow for the SMC, and lnPciBroadcastShow for the TLAN. Safety level: Debug. This command displays the number of broadcast IP packets received on the lnIsa (ELAN) interface every second for the past 60 seconds. The total number of broadcast messages 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.
-> lnIsaBroadcastShow Broadcasts 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: 0 Total number of broadcasts: 6209 value = 33 = 0x21 = '!'
B.2.23
lnIsaBroadcastThreshold = threshold - not applicable, SMC See also mac21440BroadcastThreshold for the SMC, and lnPciBroadcastThreshold for the TLAN. Safety level: Debug. This is a variable. Setting it controls the threshold (in packets/sec) at which a message is printed when the lnIsaShowLostBroadcast is set. The default threshold is 40.
-> lnIsaBroadcastThreshold = 20 _lnIsaBroadcastThreshold = 0x34aeb0: value = 20 = 0x14
Issue 1.5.4 May 20, 2003
B.2.24
lnIsaShowLostBroadcast = 1/0 - not applicable, SMC See also lnPciShowLostBroadcast for the TLAN. Safety level: Debug. This is a variable. Setting it to 1 prints a message whenever the broadcast threshold (set via the lnIsaBroadcastThreshold variable) is exceeded on the lnIsa (ELAN) interface. This is useful for debugging broadcast storms. The default is off (0); the state is not saved and returns to off if the card is reset or reboots. The example below was 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 Safety level: Debug. This command disables physical level broadcast ltering as congured by the lnPciBcastFilterOn - not applicable, SMC (section B.2.26, pg 188) command.
B.2.26
lnPciBcastFilterOn - not applicable, SMC Safety level: Debug. This command enables enhanced Broadcast ltering on the T-LAN interface on Pentium cards. This is enabled by default. When this is not enable, if we receive more than 40 Broadcasts of any sort on either the T-LAN or the E-LAN we do not process them any more (but we do count them and this can be veried with the lnIsaBroadcastShow or lnPciBroadcastShow commands from the vxWorksShell). With this enabled, we lter out at a H/W level receipt of any more broadcasts over a maximum limit of 401 on the T-LAN. The lnPciBroadcastShow command can be used to view this in operation.
-> lnPciBroadcastShow Broadcasts per second, last 60 seconds: lnPci0 0: 6: etc. 401 0401 0 0 401 0 0 401
Issue 1.5.4 May 20, 2003
Note also, that a message is written to the CURRLOG.1 le every time the Broadcast lter threshold is reached:
1996 1 7 09:39:53 (COM) :PCI Broadcast Filter Enabled
B.2.27
lnPciBroadcastShow - not applicable, SMC Safety level: Debug. This command displays the number of broadcast IP packets received on the lnPci (TLAN) interface every second for the past 60 seconds. The total number of broadcast messages received on the interface since the card was booted is also displayed.
-> lnPciBroadcastShow Broadcasts 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: 0 Total number of broadcasts: 4518 value = 33 = 0x21 = '!'
B.2.28
lnPciBroadcastThreshold = threshold - not applicable, SMC Safety level: Debug. This is a variable. Setting it controls the threshold (in packets/sec) at which a message is printed when the lnPciShowLostBroadcast is set. The default threshold is 40.
-> lnPciBroadcastThreshold = 200 _lnPciBroadcastThreshold = 0x34b008: value = 200 = 0xc8
Issue 1.5.4 May 20, 2003
B.2.29
lnPciShowLostBroadcast = 1/0 - not applicable, SMC Safety level: Debug. This is a variable. Setting it to 1 prints a message whenever the broadcast threshold (set via the lnPciBroadcastThreshold variable) is exceeded on the lnPci (TLAN) interface. This is useful for debugging broadcast storms. The default is off (0); the state is not saved and returns to off if the card is reset or reboots. The example below was 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 Safety level: Debug. This command lists the contents of the current directory, with only the directory or le names. The example shows a list of the root directory on a Media Card. For comparison, the ll is also shown.
-> ls exec U LOG TRACE TABLE OM DSP KEYCODE BOOTP CONFIG H323 ETC value = 0 = -> -> ll -r-xr-xr-x drwxrwxrwx drwxrwxrwx drwxrwxrwx drwxrwxrwx drwxrwxrwx drwxrwxrwx drwxrwxrwx drwxrwxrwx drwxrwxrwx drwxrwxrwx drwxrwxrwx value = 0 =
0x0
1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 0x0
0 0 0 0 0 0 0 0 0 0 0 0
7249248 4096 4096 4096 4096 4096 4096 4096 4096 4096 4096 4096
Mar Feb Mar Feb Mar Mar Feb Feb Mar Mar Mar Feb
14 5 7 5 12 12 5 5 9 12 12 10
2001 2001 2001 2001 12:06 00:01 2001 2001 16:12 12:06 12:06 2001
exec U/ LOG/ TRACE/ TABLE/ OM/ DSP/ KEYCODE/ BOOTP/ CONFIG/ H323/ ETC/
Issue 1.5.4 May 20, 2003
B.2.31
mac21440BroadcastShow - only applicable for SMC See also lnIsaBroadcastShow for the other cards. Safety level: Debug. For the SMC, broadcast ltering is done by the microengine co-processors. This function prints the number of broadcasts that the card has received on both interfaces every second for the past 60 seconds. The number of broadcasts is the number that was returned to the IPT 3.0 core software by the microengines. If this value exceeds the threshold per second, then that is the number of packets that will be reported by this function.
-> mac21440BroadcastShow Broadcasts 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: 0 Total number of broadcasts: 6209 value = 33 = 0x21 = '!'
B.2.32
mac21440BroadcastThreshold = threshold - only applicable for SMC See also lnIsaBroadcastThreshold for the other cards. Safety level: Debug. This is a variable. Setting it controls the threshold (in packets/sec) at which throttling of broadcast messages occurs. When the number of broadcasts received by the microEngines exceeds this value, the microEngines will start dropping broadcast packets. The default threshold is 40.
-> mac21440BroadcastThreshold = 20 _mac21440BroadcastThreshold = 0x34aeb0: value = 20 = 0x14
Issue 1.5.4 May 20, 2003
B.2.33
mbufShow Safety level: Debug. This command displays statistics and the distribution of the low-level buffers used by the IP stack.
-> mbufShow type number -------------FREE : 6395 DATA : 0 HEADER : 5 SOCKET : 0 PCB : 0 RTABLE : 0 HTABLE : 0 ATABLE : 0 SONAME : 0 ZOMBIE : 0 SOOPTS : 0 FTABLE : 0 RIGHTS : 0 IFADDR : 0 CONTROL : 0 OOBDATA : 0 IPMOPTS : 0 IPMADDR : 0 IFMADDR : 0 MRTABLE : 0 TOTAL : 6400 number of mbufs: 6400 number of times failed to find space: 0 number of times waited for space: 0 number of times drained protocols for space: 0 __________________ CLUSTER POOL TABLE _______________________________________________________________________________ size clusters free usage ------------------------------------------------------------------------------64 1024 1019 2276 128 1024 1024 187290 256 512 512 775 512 512 512 29 1024 256 256 34 2048 256 256 0 ------------------------------------------------------------------------------value = 80 = 0x50 = P ->
Issue 1.5.4 May 20, 2003
B.2.34
mixLevelOn module Safety level: Debug. This command has a deceptive name. It translates as mix level as currently set on a module. It prints the current print level set for module. In the example, executing the command initially resulted in a result of 0; the log level was error only. After enabling the trace to screen (mixSetLogOpt 0,1,1), the command resulted in a return value of all, or 1. After a further change, it reverted to error only, even though the option was still to screen.
-> mixLevelOn 0 value = 0 = 0x0 -> mixSetLogOpt 0,1,1 value = 0 = 0x0 -> mixLevelOn 0 value = 1 = 0x1 -> mixSetLogOpt 0,1,0 value = 0 = 0x0 -> mixLevelOn 0 value = 0 = 0x0 ->
B.2.35
mixMemFindAll Safety level: Debug. This command prints information about each buffer from an IPT 3.0 buffer pool that is currently in use by the application. The address of the buffer and the task using the buffer is printed. This information can be useful if a buffer pool runs out (or runs very low) of buffers to see what task is holding on to them. Note that running this command when the buffers are very low and trafc is fairly high is somewhat risky, as it can end up in contention for resources with call processing. Note: in the table, marker actually stands for the task indication within the buffer data space reserved to indicate the task that mixMalloced the buffer. For example, tNpm would mean that the NPM task seized the buffer. And Instance is a code used by designers to locate the place where the mixMalloc occurred. As an example, if the NPM mixMalloced a block and the instance shown was 0x8001, the designer can look for mixMalloc in the NPM module code and the function where the mixmalloc occurred. Using the example for line 002 of the pool buf size (64), we nd:
if ( (timerMsg = mixMalloc( sizeof(MIX_MSG_Q_HDR_MSG), M_BUF_NPM | 1 )) == NULL )
Issue 1.5.4 May 20, 2003
This is the line that seized the buffer shown here. M_BUF_NPM set the high bits; the low 3 nybbles are the location within that task.
-> mixMemFindAll +------------------------------------------+ | POOL BUF SIZE (64) | +------------------------------------------+ | Buffer State Marker Instance | +------------------------------------------+ 001. 0x2e94244 good tRmm 0xb020 002. 0x2e945b4 good tNpm 0x8001 003. 0x2e946a4 good (null) 0xc022 004. 0x2e94f64 good tRCM 0xa000 005. 0x2e96724 good tRmm 0xb01d 006. 0x2e985c4 good tMONServer 0x6005 007. 0x2e9cad4 good tRmm 0xb000 008. 0x2e9cdf4 good tOMM 0x9000 009. 0x2ea0bd4 good tMONClient 0x6000 010. 0x2ea2074 good tOMM 0x9001 011. 0x2ea2164 good tRmm 0xb000 +------------------------------------------+ | POOL BUF SIZE (256) | +------------------------------------------+ | Buffer State Marker Instance | +------------------------------------------+ 001. 0x2e5cc48 good (null) 0xe001 002. 0x2e5d0a8 good tUIPC 0xd00e 003. 0x2e71e40 good tUIPC 0xd00e 004. 0x2e71f58 good tIGCC 0x300d 005. 0x2e73420 good tIGCC 0x3008 006. 0x2e73538 good tUIPC 0xd00e 007. 0x2e73ab0 good tNpm 0x1009 +------------------------------------------+ | POOL BUF SIZE (512) | +------------------------------------------+ | Buffer State Marker Instance | +------------------------------------------+ 001. 0x2cbb3d8 good (null) 0xe000 002. 0x2cbc4b8 good tUIPC 0xd007 +------------------------------------------+ | POOL BUF SIZE (1024) | +------------------------------------------+ | Buffer State Marker Instance | +------------------------------------------+ ******All buffers in pool****** value = 34 = 0x22 = ->
Issue 1.5.4 May 20, 2003
B.2.36
mixOptionOn module Safety level: Debug. This command has a deceptive name. It translates as mix option as currently set on a module. It prints the current option set for module. In the example, executing the command initially resulted in a result of 0; the log option for the module was off. After enabling the trace to screen (mixSetLogOpt 0,1,1), the command resulted in a return value of to screen, or 1.
-> mixOptionOn 0 value = 0 = 0x0 -> mixSetLogOpt 0,1,1 value = 0 = 0x0 -> mixOptionOn 0 value = 1 = 0x1 ->
B.2.37
mixSetLogOpt module, option, level Safety level: Debug/possible resource shortage. If the user enables tracing under load, the output can exhaust necessary resources. At the extreme, it can even lead to cards resetting spontaneously, as tasks block while waiting for resources. Low level trafc in the order of single digit call per minute rates will to be an issue unless all possible modules are enabled. This command controls the printing of detailed information from a task. To enable information for multiple tasks, the command is entered multiple times. Having too much at once can result in being unable to locate key information, so it is common to have up to three on at once, but to turn off some and turn on others to get the fourth, fth,... The parameter module species the module for this entry of the command. Details of what each module does is included in IP Trunk 3.0 module descriptions (section 2, pg 19). The next section details which modules are involved in what functions of the ITG 2.0 Trunk application. Table 5: Modules and values used for mixSetLogOpt command
Module
Value Acronym 0 1 2 TSM NPM RMM Name Telephony Signalling Network Protocol Resource Manager
Module function Central call control module for the application H.323 signalling module Allocation and reservation of channels
Issue 1.5.4 May 20, 2003
Table 5: Modules and values used for mixSetLogOpt command

Module Value Acronym 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 NMM MAM MTS MSM MCM OMM A07 DIM UIPC LAPD IGCC ATPM SNMP COM SMM IPSS RCM MonTask ItgPatch Name Network Manager Maintenance Module Network Monitor Timestamp Server Network Monitor Server Network Monitor Client Operation Measurement A07 Manager DSP Interface Module UIPC L3 Module Omnitel LAPD Driver Internet Gateway Call Control Address Translation Protocol Module SNMP agent module Common Utilities System Monitor IP Socket Server RADIUS Client Module Task monitor Patcher function Ensures tasks are still running Tracking installing (etc.) of patches Drives all intercard communications Statistics SSD messages to and from the Meridian 1 Interface to software resident on the DSPs State machine and parser for layer 3 ISDN messages Layer 2 D channel PC card interface Interface between TSM and UIPC Resolving addresses to IP addresses Network management interface Quality of service monitoring Administration - especially dial plan tables Accept and propagate provisioning from OTM Module function
The parameter option sets where the data is printed: 0 = off 1= log to TTY 2= log to le 3= log to both TTY and le
Issue 1.5.4 May 20, 2003
Entering the command without the option is equivalent to entering it with the option 0, or off. The parameter level sets what kind of information is printed: 0 = error only 1 = info and error The level cannot be entered without the option being selected; entering an option and not 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 memory, this can have unpredictable results. This creates a new subdirectory under (within) the current directory.
-> ll size date ------------512 JUN-06-2000 512 JUN-06-2000 512 JUN-06-2000 512 JUN-06-2000 512 JAN-01-1996 512 JAN-01-1996 512 JAN-01-1996 value = 0 = 0x0 -> mkdir temp value = 0 = 0x0 -> ll size date ------------512 JUN-06-2000 512 JUN-06-2000 512 JUN-06-2000 512 JUN-06-2000 512 JAN-01-1996 512 JAN-01-1996 512 JAN-01-1996 512 FEB-22-2001 value = 0 = 0x0 time -----08:28:44 08:28:46 08:28:50 08:33:34 12:00:22 12:00:22 12:00:22 name -------LOG OM CONFIG FW DATA ETC LOCALE
<DIR> <DIR> <DIR> <DIR> <DIR> <DIR> <DIR>
time -----08:28:44 08:28:46 08:28:50 08:33:34 12:00:22 12:00:22 12:00:22 15:10:00
name -------LOG OM CONFIG FW DATA ETC LOCALE TEMP
<DIR> <DIR> <DIR> <DIR> <DIR> <DIR> <DIR> <DIR>
Issue 1.5.4 May 20, 2003
B.2.39
monIPDebugSet IP.ad.dr.ess, on_off Safety level: Debug. This command enables detail network monitor debugging for the selected IP address. The address is entered in dotted notation. The parameter on_off has the following values: 0 - turn off detailed information 1 - turn on detailed information An example follows:
-> monIPDebugSet 10.0.0.2, 1 value = 1 = 0x1 -> 1996 2 4 21:27:32 (MSM) :No packets received from IP: 10.0.0.2, Freq: 23566 1996 2 4 21:27:32 (MSM) :No packets returned by IP: 10.0.0.2 1996 2 4 21:27:52 (MSM) :No packets received from IP: 10.0.0.2, Freq: 23567 1996 2 4 21:27:52 (MSM) :No packets returned by IP: 10.0.0.2 1996 2 4 21:28:12 (MSM) :No packets received from IP: 10.0.0.2, Freq: 23568 1996 2 4 21:28:12 (MSM) :No packets returned by IP: 10.0.0.2 -> monIPDebugSet 10.0.0.2,0 value = 1 = 0x1 ->
Issue 1.5.4 May 20, 2003
B.2.40
monUtility Safety level: Debug. This menu driven utility provides a way to print the IP table for the QoS monitoring function 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,9 are intended as designer tools only. Please do not use these to change any settings. The original settings can be restored by resetting the card. Option 0 is available as a separate command: emodelSim.
-> monUtility
******Monitor Utility****** Run Emodel Simulator ............0 Set Monitor Probing Constants ...1 Print Monitor Constants .........2 Set Monitor Debug Options .......3 Print Monitor Debug Setting .....4 Print IP Table ..................5 Print IP Entry ..................6 Print IP Entry QoS Data .........7 Set Configured QoS Parms ........8 Set Network QoS Parms ...........9 End Utility .................Enter Please Enter Your Choice -> 5 Number of blocks = 1 Number of entry = 2 Block number : 0 Entry : 0 Node IP : 47.11.215.211 Reference count : 11 Qos Enabled : 1 Send QoS : 3.000000 Receive QoS : 3.000000 Node Capability : 7 Block number : 0 Entry : 1 Node IP : 44.11.223.221 Reference count : 5 Qos Enabled : 1 Send QoS : 3.000000 Receive QoS : 3.000000 Node Capability : 8
Issue 1.5.4 May 20, 2003

******Monitor Utility****** Run Emodel Simulator ............0 Set Monitor Probing Constants ...1 Print Monitor Constants .........2 Set Monitor Debug Options .......3 Print Monitor Debug Setting .....4 Print IP Table ..................5 Print IP Entry ..................6 Print IP Entry QoS Data .........7 Set Configured QoS Parms ........8 Set Network QoS Parms ...........9 End Utility .................Enter Please Enter Your Choice -> 6,0 ******IP ENTRY DATA****** IP ADDRESS -> 47.11.215.211
IP ADDRESS : 47.11.215.211 CONFIGURED QOS QOS ENABLED : 1 TRANSMIT QOS : 3.00 RECEIVE QOS : 3.00 NETWORK QOS CODEC TYPE TRANSMIT QOS G711Alaw G711Ulaw G723_5 G723_6 G729 G729A G729B G729AB 4.43 4.43 3.99 3.99 4.07 4.07 4.07 4.07
RECEIVE QOS 4.43 4.43 3.99 3.99 4.07 4.07 4.07 4.07
FALLBACK STATE 0 0 0 0 0 0 0 0
******Monitor Utility****** Run Emodel Simulator ............0 Set Monitor Probing Constants ...1 Print Monitor Constants .........2 Set Monitor Debug Options .......3 Print Monitor Debug Setting .....4 Print IP Table ..................5 Print IP Entry ..................6 Print IP Entry QoS Data .........7 Set Configured QoS Parms ........8 Set Network QoS Parms ...........9 End Utility .................Enter Please 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
Issue 1.5.4 May 20, 2003

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 Delay 0 1 2 3 4 90.40 89.46 92.79 91.96 91.75 Send Side Pkt Loss 0.00 0.00 0.00 0.00 0.00 Receive Side Delay 93.00 93.00 93.00 93.00 93.00 0.00 0.00 0.00 0.00 0.00 Receive Side Pkt Loss
Transmit Data Current Sample Number = 1 Average End-To-End Delay = 91.27 ms Average Packet Loss = 0.00 % Receive Current Average Average Data Sample Number = 1 End-To-End Delay = 93.00 ms Packet Loss = 0.00 %
IP ADDRESS : 47.11.215.211 CONFIGURED QOS QOS ENABLED : 1 TRANSMIT QOS : 3.00 RECEIVE QOS : 3.00 NETWORK QOS CODEC TYPE TRANSMIT QOS G711Alaw G711Ulaw G723_5 G723_6 G729 G729A G729B G729AB 4.43 4.43 3.99 3.99 4.07 4.07 4.07 4.07
RECEIVE QOS 4.43 4.43 3.99 3.99 4.07 4.07 4.07 4.07
FALLBACK STATE 0 0 0 0 0 0 0 0
******Monitor Utility****** Run Emodel Simulator ............0 Set Monitor Probing Constants ...1 Print Monitor Constants .........2 Set Monitor Debug Options .......3 Print Monitor Debug Setting .....4 Print IP Table ..................5 Print IP Entry ..................6 Print IP Entry QoS Data .........7 Set Configured QoS Parms ........8
Issue 1.5.4 May 20, 2003

Set Network QoS Parms ...........9 End Utility .................Enter Please Enter Your Choice -> value = 10 = 0xa ->
B.2.41
mRouteAdd destIPaddr, gwIPaddr, 0xdestNetMask, To, 0 Safety level: Debug. Similar to routeAdd, but allows multiple routes to the same destination, differentiated by the ToS eld and/or the gateway eld. The parameter destIPaddr is the destination IP address in dotted notation; gwIPaddr is the gateway IP address in dotted notation; 0xdestNetMask is the destinations net mask in hexadecimal; ToS is the Type of Service for this route. This change is not permanent; rebooting the card rebuilds the routing table from the data in the CONFIG.INI le.
-> mRouteAdd 192.168.1.128,192.168.1.140,0xffffff80,0,0 value = 0 = 0x0
B.2.42
mRouteDelete destIPaddr, 0xdestNetMask, ToS Safety level: Debug. Similar to routeDelete, but species the route using the destination address, netmask and ToS. The parameter destIPaddr is the destination IP address in dotted notation; 0xdestNetMask is the destinations net mask in hexadecimal; ToS is the Type of Service for this route. This change is not permanent; rebooting the card rebuilds the routing table from the data in the CONFIG.INI le.
-> mRouteDelete 192.168.1.128,0xffffff80,0 value = 0 = 0x0
B.2.43
mRouteShow Safety level: Debug. Similar to routeShow, but also displays the ToS bit and mask settings.
-> mRouteShow Destination Mask TOS Gateway 192.168.1.200 127.0.0.1 192.168.1.14 192.168.1.140 192.168.1.140 Flags RefCnt Use 3 5 101 101 101 0 0 0 0 0 0 0 0 0 0 Interface Proto lnPci1 lo0 lnIsa0 lnPci1 lnPci1 0 0 0 0 1
0.0.0.0 0 0 127.0.0.1 0 0 192.168.1.0 ffffff80 0 192.168.1.128 ffffff80 0 192.168.1.128 ffffff80 18 value = 0 = 0x0
Issue 1.5.4 May 20, 2003
B.2.44
netHelp Safety level: Debug. Displays a help screen synopsis of often used network routines.
-> netHelp
hostAdd
- 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 table netDevCreate 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 table routeDelete destaddr,gateaddr - delete route from route table routeShow iam - print current route table - specify the user name by which you will be known to remote hosts (and optional password) - print the current remote ID - log in to a remote host; host can be inet address or host name in remote host table
hostname,inetaddr
usr[,passwd]
whoami rlogin
host
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 useful to recover a card that is no longer able to place calls, as often the problem is that the dial plan table has had an entry - sometimes the gatekeeper data! - corrupted.
-> nmmAtpmTranTblDnld value = 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 issuing a command without the patch name or number may result in prompting for the specic details. When these details are already known, this can result in getting more patch options.
Issue 1.5.4 May 20, 2003
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, provided the patch is compatible with the current software version. That is, if a patch has been loaded 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 undened or unloaded patch into service yields the following output:
-> pins 3 Patch with handle 3 doesnt exist. Cannot activate. value = -1 = 0xffffffff = _func_taskRegsShowRtn + 0xff7b8bff ->
Unfortunately, just because a patch is created for the appropriate load does not mean it will go into service on a specic switch. For example, the following output occurred when 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 loaded 2003 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 changing this function, or that the software on the card is a eld service up-issue - a custom build provided to an end user. In that case, the patch must be rebuilt in the context of the eld service up-issue. Note that in general eld service up-issues are not needed in releases with patching capabilities, because of the patching function. Field service up-issues can only include the exact set of xes identied, and if another x is needed a complete new load is required. However, a small patch can be loaded and put in service very easily on sites that need it and left out of all others.
Issue 1.5.4 May 20, 2003
B.2.46.2
plis, or plis patchNumber Safety level: Debug. Low risk. This command prints the header information about a specic patch, including the le name, patch name, version, PRS information, engineer, and release. It also includes some statistical information - in or out of service, time in service, and so forth. To determine which patches can be viewed, run pstat rst.
-> plis 0 Handle: 0* Filename: /C:/U/PATCH/ringback.tsa Version: 1.3 Patch name: Non_NA_Ringback_Q00632470 Ref. num.: 12345 PRS number: Q00632470 Engineer: John Doe Release: IPT-3.00.52 SA Created: Wed Mar 19 10:57:02 2003 Patch is in-service In-service date: Wed Mar 19 14:29:38 2003 In-service for less than 1 day In-service number of reset(s): 0 Patch is retained Patch retain level: RES In-service reset threshold: 5 In-service days to watch for resets: 7 Number of patch element(s): 1 Patch info of element #1: Patch element type: C function Procedure/function name: _npmNSDataProcess Address to patch: 0xb3cac Patch element address: 0x71a8f0 value = 0 = 0x0 ->
or
-> plis Patch handle? 0 Handle: 0 Filename: /C:/U/PATCH/ringback.tsa Version: 1.3 Patch name: Non_NA_Ringback_Q00632470 Ref. num.: 12345 PRS number: Q00632470 Engineer: John Doe Release: IPT-3.00.52 SA Created: Wed Mar 19 10:49:26 2003 Patch is out-of-service Out-of-service reason: Never activated Patch is retained Patch retain level: RES In-service reset threshold: 5 In-service days to watch for resets: Number of patch element(s): 1
Issue 1.5.4 May 20, 2003

Patch info of element #1: Patch element type: C function Procedure/function name: _npmNSDataProcess Address to patch: 0xb3cac value = 0 = 0x0 ->
Attempting to list an undened or unloaded patch yields the following output:

-> plis 3 Patch 3 doesnt exist. Cannot get patch info. value = -1 = 0xffffffff = _func_taskRegsShowRtn + 0xff7b8bff ->
Issue 1.5.4 May 20, 2003
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 patch must rst have been ftped to the card directory /C:/U/PATCH before it can be loaded. Note that using pload without specifying the patch name results in being prompted for the patch name, followed by being prompted for options - whether the patch is to be retained, how many times the card can reset in a specied interval before the patch is taken out of service, and how long the interval is (in days).
-> pload Patch filename? ringback.tsa Retain 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: 0 value = 0 = 0x0 ->
or
-> pload ringback.tsa Loading patch from /C:/U/PATCH/ringback.tsa Patch handle is: 0 value = 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 patchLoad 2001 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 call handling (or other operations) in the load. This command puts a patch out of service but does not unload it.
Issue 1.5.4 May 20, 2003

-> 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 output:
-> poos 0 Cannot deactivate patch 0. It is not in-service. Deactivation of patch 0 aborted. value = -1 = 0xffffffff = _func_taskRegsShowRtn + 0xff7b8bff -> -> pstat 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: 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: RES Patch 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: RES value = 0 = 0x0 ->
Attempting to put an undened or unloaded patch out of service yields the following output:
-> 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 remove it from the C: drive.
-> pout Patch handle? 0
Issue 1.5.4 May 20, 2003

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 undened or unloaded patch yields the following output:

-> pout 3 Patch 3 doesnt exist. Cannot remove. Could not remove patch 3. value = -1 = 0xffffffff = _func_taskRegsShowRtn + 0xff7b8bff ->
B.2.46.6
pstat, or pstat patchNumber Safety level: Debug. Low risk. This command prints the key operational and provisioning data about a patch. Using the patch number makes no difference in the printout for that patch, but the remaining patches are ignored. pstat with no parameters prints all patches.
-> pstat 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: RES Patch 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: RES value = 0 = 0x0 ->
Issue 1.5.4 May 20, 2003
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: RES value = 0 = 0x0 ->
B.2.47
print_ip_table Safety level: Debug. This command allows you to check if the IP table used by the address translation is built in memory.
-> print_ip_table Number of blocks = 1 Number of entry = 2 Block number : 0 Entry : 0 Node IP : 47.11.215.211 Reference count : 11 Qos Enabled : 1 Send QoS : 3.000000 Receive QoS : 3.000000 Node Capability : 7 Block number : 0 Entry : 1 Node IP : 44.11.223.221 Reference count : 5 Qos Enabled : 1 Send QoS : 3.000000 Receive QoS : 3.000000 Node Capability : 8 value = 20 = 0x14 ->
Issue 1.5.4 May 20, 2003
B.2.48
Printing dial plan data Safety level: Debug. These commands allow the user to identify invalid provisioning, printing to screen the data associated with each plan/type pair provisioned. Note that the output has changed from prior releases; it is now tabular. The enterprise applicable remote node capability (Node Cap) value corresponds to endpoint 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 transport 6 = ISGF - Nortel based transport of ISO QSIG GF. 7 = SL1 - Nortel proprietary enterprise ISDN, without ESN5 prex to dialled numbers 8 = SL1ESN5 - SL1 with ESN5 prexes 9 = CSE - Succession Call Server for Enterprise compatible - uses the Nortel Interoperability format for non-standard data
The carrier Node Cap values also correspond to endpoint protocol selected in OTM. However, they have no use in the enterprise at this time. The values are as follows: 2 = BELL, 3 = 7SGF_ETSI_V1, 4 = 7SGF_ETSI_V2, 5 = 7SGF_FTUP - for Multimedia Communications Switch; not supported with Meridian 1
Issue 1.5.4 May 20, 2003
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 corresponds to a blank space between two commas in the DPTABLE.1. Putting a zero (0) in that place 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 to Compl. ------- ------27 0 Digits to Delete ------0 Digits I.P. to Insert ------- --------------(null) 47.11.215.211 QoS Send Enabled QoS Receive Node Qos Cap.
------- ------- ------- ------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 to Compl. ------- ------27 0 Digits to Delete ------0 Digits I.P. to Insert ------- --------------0 47.11.215.211 QoS Send Enabled QoS Receive Node Qos Cap.
------- ------- ------- ------Yes 3.000 3.000 7
when printed. This will insert the 0 in front of the dialled digits prior to transmitting to 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 ------613 765 613 769 613 778 613 961 613 967 value = ->
Digits to Compl. ------0 0 0 0 0 1 = 0x1
Digits to Delete ------3 3 3 0 0
Digits to Insert ------(null) (null) (null) (null) (null)
I.P.
QoS Send Enabled QoS ------Yes Yes Yes Yes Yes ------3.000 3.000 3.000 3.000 3.000
Receive Node Qos Cap. ------- ------3.000 7 3.000 7 3.000 7 3.000 8 3.000 8
--------------47.11.215.211 47.11.215.211 47.11.215.211 44.11.223.221 44.11.223.221
Issue 1.5.4 May 20, 2003
B.2.48.3
print_nxx This command prints the NXX entries in the dialling plan table.
-> print_nxx NXX Entries ----------Dialed Digits Digits to Compl. ------- ------765 0 769 0 778 0 value = 1 = 0x1 -> Digits to Delete ------0 0 0 Digits to Insert ------(null) (null) (null) I.P. QoS Send Enabled QoS ------Yes Yes Yes ------3.000 3.000 3.000 Receive Node Qos Cap. ------- ------3.000 7 3.000 7 3.000 7
--------------47.11.215.211 47.11.215.211 47.11.215.211
B.2.48.4
print_spn This command prints the SPN (international, normally) entries in the dialling plan table.
-> print_spn SPN Entries ----------There are [2] entries. There are [1] blocks. ----------------------Block [0] Dialed Digits Digits to Compl. ------- ------1613967 0 1613961 0 value = 1 = 0x1 ->
Digits to Delete ------0 0
Digits to Insert ------(null) (null)
I.P.
QoS Send Enabled QoS
Receive Node Qos Cap.
--------------- ------- ------- ------- ------44.11.223.221 Yes 3.000 3.000 8 44.11.223.221 Yes 3.000 3.000 8
Issue 1.5.4 May 20, 2003
B.2.48.5
print_loc This command prints the LOC entries in the dialling plan table.
-> print_loc LOC Entries ----------Dialed Digits Digits to Compl. ------- ------343 0 393 0 395 0 396 0 397 0 value = 1 = 0x1 -> Digits to Delete ------0 0 0 0 0 Digits to Insert ------(null) (null) (null) (null) (null) I.P. QoS Send Enabled QoS ------Yes Yes Yes Yes Yes ------3.000 3.000 3.000 3.000 3.000 Receive Node Qos Cap. ------- ------3.000 8 3.000 7 3.000 7 3.000 7 3.000 7
--------------44.11.223.221 47.11.215.211 47.11.215.211 47.11.215.211 47.11.215.211
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 to Compl. ------- ------4 0 value = 1 = 0x1 ->
Digits to Delete ------0
Digits I.P. to Insert ------- --------------(null) 47.11.215.211
------- ------- ------- ------Yes 3.000 3.000 7
Issue 1.5.4 May 20, 2003
B.2.48.7
print_dsc This command prints the CDP Distant Steering Code (DSC) entries in the dialling plan table.
-> print_dsc DSC Entries ----------There are [1] entries. There are [1] blocks. ----------------------Block [0] Dialed Digits Digits to Compl. ------- ------4 0 value = 1 = 0x1 ->
Digits to Delete ------0
Digits I.P. to Insert ------- --------------(null) 47.11.215.211
------- ------- ------- ------Yes 3.000 3.000 7
B.2.48.8
print_tsc This command prints the CDP Trunk Steering Code (TSC) entries in the dialling plan table. The printout looks identical in format to the DSC entries. Note that there may not be any entries provisioned for one or more of the dial plan types; since this can 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 ->
Issue 1.5.4 May 20, 2003
B.2.49
rm lename Safety level: Destructive/Debug. This has an immediate, permanent effect, and can lead to severe problems if the wrong les are deleted. Delete a le from the /A: or /C: drive.
-> ll size date ------------512 JUN-06-2000 512 JUN-06-2000 840 JAN-26-2001 840 JAN-26-2001 238 JAN-23-2001 238 FEB-12-2001 205 FEB-12-2001 21 NOV-14-2000 value = 0 = 0x0 -> rm ITG.INI value = 0 = 0x0 -> ll size date ------------512 JUN-06-2000 512 JUN-06-2000 840 JAN-26-2001 840 JAN-26-2001 238 JAN-23-2001 238 FEB-12-2001 205 FEB-12-2001 value = 0 = 0x0 time -----08:28:50 08:28:50 13:00:38 13:17:40 12:55:12 17:26:12 17:48:02 09:35:16 name -------. .. CONFIG.INI CONFIG.BAK BOOTP.TAB BOOTP.BAK UMS.INI ITG.INI
<DIR> <DIR>
time -----08:28:50 08:28:50 13:00:38 13:17:40 12:55:12 17:26:12 17:48:02
name -------. .. CONFIG.INI CONFIG.BAK BOOTP.TAB BOOTP.BAK UMS.INI
<DIR> <DIR>
Issue 1.5.4 May 20, 2003
B.2.50
rmdir dirName Safety level: Destructive/Debug. This has an immediate, permanent effect, and can lead to severe problems if the wrong directories are deleted. Deletes the specied directory.
-> ll size date ------------512 JUN-06-2000 512 JUN-06-2000 512 JUN-06-2000 512 JUN-06-2000 512 JAN-01-1996 512 JAN-01-1996 512 JAN-01-1996 512 FEB-22-2001 value = 0 = 0x0 -> rmdir temp value = 0 = 0x0 -> ll size date ------------512 JUN-06-2000 512 JUN-06-2000 512 JUN-06-2000 512 JUN-06-2000 512 JAN-01-1996 512 JAN-01-1996 512 JAN-01-1996 value = 0 = 0x0 time -----08:28:44 08:28:46 08:28:50 08:33:34 12:00:22 12:00:22 12:00:22 15:10:00 name -------LOG OM CONFIG FW DATA ETC LOCALE TEMP
<DIR> <DIR> <DIR> <DIR> <DIR> <DIR> <DIR> <DIR>
time -----08:28:44 08:28:46 08:28:50 08:33:34 12:00:22 12:00:22 12:00:22
name -------LOG OM CONFIG FW DATA ETC LOCALE
<DIR> <DIR> <DIR> <DIR> <DIR> <DIR> <DIR>
Issue 1.5.4 May 20, 2003
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 originate from 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 conrmed using the itgCardShow (section B.1.20, pg 152) command. The setting will remain after a power-down or reset. This is not the default conguration.
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 originate from ports 2300 to 2350 non RTP Header Compression Range. Note that the card must be disabled to run this command. The setting can be conrmed using the itgCardShow (section B.1.20, pg 152) command. The setting will remain after a power-down or reset. This is the default conguration.
Issue 1.5.4 May 20, 2003
B.2.53
set_time yy, 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 used. For example, if you use 08, the command tries to use octal, and 8 does not exist in octal. 010 is 8 in octal. The ITG card rejects the command. Therefore, do not use leading 0 characters unless using octal (011 is 9) or hexadecimal (0x12 is 18).
This command sets the time for both the ITG cards realtime clock chip (RTC) and the VxWorks 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 the time and date needs to be set to a given value to make synchronizing trace information possible. The IPT application takes its time from the VxWorks OS clock. Normally that clock is initialized from the RTC when the card boots up, when MAT/OTM downloads the time (on the Leader card) or when the SNMP response returns the time (on the Follower card). This command updates them both to the date and time entered via the parameters yy, mm, dd, hh, mm, ss.
-> set_time 1,12,1,16,38,30 value = 0 = 0x0 ->
Note that invalid data is rejected:

-> set_time 3,3,09,16,3,0 invalid number: 09 ->
Issue 1.5.4 May 20, 2003
B.2.54
setTraceOption channel,outputLocation Safety level: Debug, but misuse can have severe repercussions up to and including reboot. This command enables tracing calls within a limited number of modules for a specic channel. Note that the command may be repeated to allow monitoring two or more channels. Enabling tracing via this command always enables NPM tracing, and - in conjunction with 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, that igccAddTrace by itself will not turn on the IGCC trace. IGCC tracing uses the ISL channel ID; the other traces use the local TCID. Since the IGCC traces only exist on the D channel card, and the others exist on the card carrying the call, both are needed. The channel number is 0-23 for Pentium and 0-31 for SA. The options for outputLocation are: 0 - disable tracing 1 - trace to the logged in terminal shell (or debug port) 2 - store in a local le 3 - output the trace to the shell and the le 6 - output the le to both the trace le and the log le
The following example shows the output when the setTraceOption command is used on a single channel. This trace is without any other command (in fact, the sample was taken deliberately after a card reboot, to ensure nothing could possibly be set). The message ow starts at the receipt of the SETUP request from the TSM and ending at the ALERTING and completion of Fast Start operations.
-> setTraceOption 31,1 value = 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:1720 2001 4 25 09:12:04 (NPM) :CH#:31 npmCallFastStart: 4 codecs to encode 2001 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 encode 2001 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,codec=7
Issue 1.5.4 May 20, 2003

2001 4 25 09:12:04 (NPM) 2001 4 25 09:12:04 (NPM) 2001 4 25 09:12:04 (NPM) 2001 4 25 09:12:04 (NPM) 2001 4 25 09:12:04 (NPM) dec=7 2001 4 25 09:12:04 (NPM) 2001 4 25 09:12:04 (NPM) 2001 4 25 09:12:04 (NPM) 2001 4 25 09:12:04 (NPM) 2001 4 25 09:12:04 (NPM) 2001 4 25 09:12:04 (NPM) Size 240 2001 4 25 09:12:04 (NPM) 2001 4 25 09:12:04 (NPM) 2001 4 25 09:12:04 (NPM) 2001 4 25 09:12:04 (NPM) 2001 4 25 09:12:04 (NPM) 2001 4 25 09:12:04 (NPM) 2001 4 25 09:12:04 (NPM) 2001 4 25 09:12:04 (NPM) ceiveAndTransmit 2001 4 25 09:12:04 (NPM) ceiveAndTransmit 2001 4 25 09:12:04 (NPM) CapReceiveAndTransmit 2001 4 25 09:12:04 (NPM) ceiveAndTransmit 2001 4 25 09:12:04 (NPM) ceiveAndTransmit 2001 4 25 09:12:04 (NPM) dTransmit 2001 4 25 09:12:04 (NPM) AndTransmit 2001 4 25 09:12:04 (NPM) 2001 4 25 09:12:04 (NPM) g729AnnexA, g729wAnnexB, 2001 4 25 09:12:04 (NPM) :CH#:31 :CH#:31 :CH#:31 :CH#:31 :CH#:31 :CH#:31 :CH#:31 :CH#:31 :CH#:31 :CH#:31 :CH#:31 :CH#:31 :CH#:31 :CH#:31 :CH#:31 :CH#:31 :CH#:31 :CH#:31 :CH#:31 hsChan 0x229d248 haChan 0x4007d0 txPayload: 3: vifSize 240 cmEvChannelSetAddress: isOrigin 1 47.11.215.210:2300 hsChan 0x229d248 haChan 0x4007d0 cmEvChannelParameters,chanName=g729AnnexAwAnnexB,cohsChan 0x229d280 haChan 0x40089c rxPayload: 3: vifSize 240 farEndSWVer = 1 ***Legacy: but using H323 codec payload negotation FS present in H323 ALERT so sending ALERT to TSM Sending NpmTsmCallAccept: g729AnnexAwAnnexB(7): vifhsChan 0x229d280 haChan 0x40089c Initiating terminal capability set negotation codec 0: g729AnnexAwAnnexB(7) codec 1: g729AnnexA(5) codec 2: g729wAnnexB(6) codec 3: g729(4) codec 4: t38fax(-1) [1] g711Ulaw64k: packetSize 10: cmCapAudio: cmCapRe-
:CH#:31 [2] g711Alaw64k: packetSize 10: cmCapAudio: cmCapRe:CH#:31 [3] g729AnnexAwAnnexB: packetSize 3: cmCapAudio: cm:CH#:31 [4] g729AnnexA: packetSize 3: cmCapAudio: cmCapRe:CH#:31 [5] g729wAnnexB: packetSize 3: cmCapAudio: cmCapRe:CH#:31 [6] g729: packetSize 3: cmCapAudio: cmCapReceiveAn:CH#:31 [7] t38fax: packetSize -1: cmCapData: cmCapReceive:CH#:31 Initiating Master/Slave negotation :CH#:31 {g711Ulaw64k, g711Alaw64k, g729AnnexAwAnnexB, g729} :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 itself will not turn on the TSM trace; both this command and mixSetLogOpt 0,1,1 are needed.
Issue 1.5.4 May 20, 2003
B.2.55
shellPasswordNvramClear Safety level: Debug; implications at user login. This command resets the current userid/password back to the factory default, taking effect after the card is rebooted. See ITG shell command shellPasswordSet (section B.1.40, pg 165).
-> shellPasswordNvramClear value = 0 = 0x0
B.2.56
shellTimeoutGet Safety level: Safe. Displays the currently congured idle shell timeout value in seconds.
-> shellTimeoutGet value = 1200 = 0x4b0
B.2.57
shellTimeoutSet timeout Safety level: Debug. May prevent user login sessions from ending. This command sets the idle shell timeout value in seconds. Valid range for timeout is 30 to 4095. The default timeout is 1200 (20 minutes). The value is persistent: it is stored in NVRAM. The new timeout value takes effect immediately.
-> shellTimeoutSet 30 value = 0 = 0x0
B.2.58
showMemCong - Pentium only Safety level: Debug. This command displays the size of the ITG cards DRAM memory. Can be executed from the BIOS or VxWorks shells.
-> showMemConfig Memory Configuration: Bank0: 64MB value = 0 = 0x0
Issue 1.5.4 May 20, 2003
B.2.59
tcpstatShow Safety level: Debug. This command displays the TCP protocol statistics.
-> tcpstatShow TCP: 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 failed value = 29 = 0x1d
Issue 1.5.4 May 20, 2003
B.2.60
tlanDuplexSet duplexMode Safety level: Debug. This command sets the duplex mode of the TLAN interface while operating in the 10BT mode. The command takes effect immediately. The duplex mode setting is saved in NVRAM and read at startup. The parameter duplexMode is set as follows: 0 - enables full duplex mode 1 - enables half duplex mode Note that 1 has no real effect unless the TLAN speed was already set to 10 base T.
-> tlanDuplexSet 0 Forcing TLAN Interface to Full-Duplex Operation Note: tlanDuplexSet only required when TLAN not in AUTO-NEGOTIATION mode Use itgCardShow to view the Configuration of the TLAN Interface Port on network switch may require manual configuration for full-duplex mode Changes will take effect Immediately value = 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 Operation value = 38 = 0x26 = & -> -> -> -> tlanDuplexSet 1 Forcing TLAN Interface to Half-Duplex Operation Note: tlanDuplexSet only required when TLAN not in AUTO-NEGOTIATION mode Use itgCardShow to view the Configuration of the TLAN Interface Port on network switch may require manual configuration for full-duplex mode Changes will take effect Immediately value = 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 Operation value = 38 = 0x26 = & ->
Issue 1.5.4 May 20, 2003
B.2.61
tlanSpeedSet speed Safety level: Debug, potentially destructive. Sets the speed of the TLAN interface. By default, this interface auto-negotiates to the highest speed supported by the hub or switch; with a 10/100BT switch, the interface negotiates to 100BT. This command is useful when debugging ethernet speed related problems and you want to force the interface to 10BT operation; the command takes effect immediately. The duplex mode setting is saved in NVRAM and read at startup. The parameter speed 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 change) and possibly even loss of calls. While the change occurs (and especially when negotiating the speed) the card may go into local fall-back mode. If it does, new calls will fail. The following example occurred when setting the speed to 10 base T on a Media Card already running at 10 base T.
-> tlanSpeedSet 10 Forcing TLAN Interface to 10BaseT Operation Full/Half Duplex must be set with tlanDuplexSet Use itgCardShow to view the Configuration of the TLAN Interface Changes will take effect Immediately value = 0 = 0x0 ->
Changing the speed to autonegotiate when the hub is 10 base T only is less than fully effective; if the fastest you have is 10 base T, you cannot get more. However, it can be done. Note that auto negotiation may cause call failures as negotiation occurs.
-> tlanSpeedSet 10100 Setting TLAN Interface to AUTO-NEGOTIATE Speed and Duplex Parameters Use itgCardShow to view the Configuration of the TLAN Interface Changes take effect Immediately value = 0 = 0x0 -> 2001 4 14 00:04:32 (IGCC) :ITG0402 - Voice ethernet port disconnected 2001 4 14 00:04:32 (COM) :mixFree: instance b005:mark (tRmm) instance b029 0x2e9a9d8 already free 2001 4 14 00:04:32 (COM) :SNMP ALARM: Card is recovered from FALLBACK mode. Communication between Leader and the card is up. 2001 4 14 00:04:34 (IGCC) :ITG0102 - Voice ethernet port Reconnected 2001 4 14 00:04:34 (RMM) :rmmLeaderInit: set Leader Mng IP address to 47.11.217.55 2001 4 14 00:04:34 (RMM) :***LDR send back GK status:1 2001 4 14 00:04:34 (RMM) :***FL card update GK status: 1 ->
Issue 1.5.4 May 20, 2003
B.2.62
TsmDspStat = 1/0 Safety level: Debug/output load. Under heavy call origination/call clearing trafc, this may slow the system. It should be set, the necessary commands run or test calls made, and then cleared. To observe DSP statistics, the user sets a variable rather than issuing a command. Setting this to 1 causes the DSP statistics printed by the tsm_stat_req_vp_delay, tsm_stat_req_error and tsm_stat_req_rx_tx commands to be printed at the end of any call. This also needs to be set to 1 if these commands are asynchronously entered at the 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 are occurring during calls. No identifying information about the call (other than the TCID and timestamp) are given, so if information about a particular call is needed, use h323SessionShow (section B.1.15, pg 143) while the call is active to identify the channel being used. This is cleared by setting the variable to 0. The default is off; the state is not saved and returns to off if the card is reset or reboots.
-> TsmDspStat = 1 _TsmDspStat = 0x346298: value = 1 = -> SEP 06 11:39:08 tMVX_DIM: Info TCID SEP 06 11:39:08 tMVX_DIM: Info TCID SEP 06 11:39:08 tMVX_DIM: Info TCID SEP 06 11:39:08 tMVX_DIM: Info TCID SEP 06 11:39:08 tMVX_DIM: Info TCID SEP 06 11:39:08 tMVX_DIM: Info TCID SEP 06 11:39:08 tMVX_DIM: Info TCID SEP 06 11:39:08 tMVX_DIM: Info TCID SEP 06 11:39:08 tMVX_DIM: Info TCID SEP 06 11:39:08 tMVX_DIM: Info TCID SEP 06 11:39:08 tMVX_DIM: Info TCID SEP 06 11:39:08 tMVX_DIM: Info TCID SEP 06 11:39:08 tMVX_DIM: Info TCID SEP 06 11:39:08 tMVX_DIM: Info TCID SEP 06 11:39:08 tMVX_DIM: Info TCID -> 0x1 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, avg_playout_delay = 59 lost_packet_count = 0 replay_packet_count = 0 idle_packet_count = 14 dropped_packet_count = 0 rx_packet_count = 156 invalid_header_count = 0 to_micro_overflow_count = 0 lost_enh_packet_count = 0 no_core_packet_count = 0 rx_packet_count = 78 tx_packet_count = 81 silence_packet_count = 0 min_jitter = 20 max_jitter = 20
Issue 1.5.4 May 20, 2003
B.2.63
tsmSetTraceOption TCID,[0 or !0] Safety level: Debug. This command turns on well, but does not turn off as well. The difculty is that the command does not work in isolation; you need to turn on TSM tracing using mixSetLogOpt as well. However, after turning on tsmSetTraceOption and debugging, simply turning off tsmSetTraceOption is incomplete; the mixSetLogOpt remains enabled. The parameters TCID is in the legitimate range for the card - 0 to 23 for Pentium and 0-31 for SMC. The on/off parameter is 0 is off, any other is on. The following shows the difference between tracing with and without tsmSetTraceOption. The rst trace shows the mixSetLogOpt command alone; the second adds the TSM trace in red, bold.
-> mixSetLogOpt 0,1,1 value = 0 = 0x0 -> 2001 4 25 09:26:30 (TSM) :IgccTsmCallSetup(34) from IGCC: tcid 31: SPU_IDLE(1): 0xd95f0 2001 4 25 09:26:30 (TSM) :message size (setup): 114 2001 4 25 09:26:30 (TSM) :AtpmTsmAddTranOK(27) from ATPM: tcid 31: SPU_REQ_O_CALL(8): 0xdbf84 2001 4 25 09:26:30 (TSM) :Num_dig_delete=0 NumOfCodecs=2 nodeCap=8 dig_insert=0 esn5LocEnable=0 esn5LocDigit=|| remoteIP 47.11.215.209 2001 4 25 09:26:30 (TSM) :tsm_REQ_O_CALL_PROC: remote nodeCap = 8 2001 4 25 09:26:30 (TSM) :---> but src node doesnt have esn5 signalling: pad w/ esn5 digs 2001 4 25 09:26:30 (TSM) :final digit translation result=|1003500|, startDig=3, origstartDig=0 2001 4 25 09:26:30 (TSM) :DimTsmReportChOpened(24) from DIM: tcid 31: SPU_SETUP_REQ(9): 0xd7e34 2001 4 25 09:26:30 (TSM) :NpmTsmCallAccept(4) from NPM: tcid 31: SPU_SETUP_REQ(9): 0xdcbf0 2001 4 25 09:26:30 (TSM) :useInBandTone 1: msg g729AnnexAwAnnexB(7):240 current g729AnnexAwAnnexB(7):240 2001 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,1 value = 31 = 0x1f -> 2001 4 25 09:31:12 (TSM) :IgccTsmCallSetup(34) from IGCC: tcid 31: SPU_IDLE(1): 0xd95f0 2001 4 25 09:31:12 (TSM) :TsmMsgSendToIGCC: tcid 31: TsmIgccCallProceeding(42) 2001 4 25 09:31:12 (TSM) :message size (setup): 114 2001 4 25 09:31:12 (TSM) :tsm_dsp_open 2001 4 25 09:31:12 (TSM) :Addr Trans Req to ATPM: TON: 6 NPI: 2 digits: 3500 2001 4 25 09:31:12 (TSM) :AtpmTsmAddTranOK(27) from ATPM: tcid 31: SPU_REQ_O_CALL(8): 0xdbf84 2001 4 25 09:31:12 (TSM) :Num_dig_delete=0 NumOfCodecs=2 nodeCap=8 dig_insert=0 esn5LocEnable=0 esn5LocDigit=|| remoteIP 47.11.215.209 2001 4 25 09:31:12 (TSM) :tsm_REQ_O_CALL_PROC: remote nodeCap = 8 2001 4 25 09:31:12 (TSM) :---> but src node doesnt have esn5 signalling: pad w/ esn5 digs
Issue 1.5.4 May 20, 2003

2001 4 25 09:31:12 (TSM) :final digit translation result=|1003500|, startDig=3, origstartDig=0 2001 4 25 09:31:12 (TSM) :DCH_CAP 8: freeBufferPtr 0x2e68408: uumPtr 0x2e68430 2001 4 25 09:31:12 (TSM) :sizeOfUUM 118: tsmData 0x2e684a6 2001 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): 0xd7e34 2001 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=0 2001 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 value 2001 4 25 09:31:13 (TSM) :NpmTsmCallAccept(4) from NPM: tcid 31: SPU_SETUP_REQ(9): 0xdcbf0 2001 4 25 09:31:13 (TSM) :useInBandTone 1: msg g729AnnexAwAnnexB(7):240 current g729AnnexAwAnnexB(7):240 2001 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 mode 2001 4 25 09:31:13 (TSM) :tsm_dsp_voice 2001 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 screen scrolling 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 generate output. Use these commands to query the DSP for information regarding the call.
Issue 1.5.4 May 20, 2003
B.2.64.1
tsm_stat_req_ecdbg TCID or reqECDbg TCID Safety level: Debug. This commands return the echo canceller debug statistics for a given channel. The parameter TCID species a channel on the ITG card; valid values are in the range 0 31 (Media Card), 0 - 23 (Pentium), 0 - 7 (486). If the Divergence cnt value is high (20 or higher), the EC is having difculty converging on the echo and the users will probably hear echo during the call. The output format depends on the DSP load, which actually executes the function. Therefore, examples of the current loads are given. The following is the output for an application load with Telogy 5.0.
-> tsm_stat_req_ecdbg 2 value = 0 = 0x0 -> SEP 06 09:01:06 tMVX_DIM: SEP 06 09:01:06 tMVX_DIM: SEP 06 09:01:06 tMVX_DIM: SEP 06 09:01:06 tMVX_DIM: SEP 06 09:01:06 tMVX_DIM: SEP 06 09:01:06 tMVX_DIM: SEP 06 09:01:06 tMVX_DIM: SEP 06 09:01:06 tMVX_DIM: SEP 06 09:01:06 tMVX_DIM: SEP 06 09:01:06 tMVX_DIM: SEP 06 09:01:06 tMVX_DIM: SEP 06 09:01:06 tMVX_DIM: SEP 06 09:01:06 tMVX_DIM: SEP 06 09:01:06 tMVX_DIM:
Info TSG: 2 Echo Canceller Debug Stats Info CNV state = 0 Info Px level = 290 Info Py level = 132 Info Pe level = 131 Info Post update cnt = 370 Info Attempt update cnt = 370 Should be small if Info Divergence cnt = 0 EC working OK Info ERLE bypass cnt = 0 Info XTONE count = 0 Info Fore switch cnt = 0 Info Back switch cnt = 0 Info Xidle count = 34614 Info Other bypass cnt = 2
The following is the output for an application load with Telogy 7.01.
JAN JAN JAN JAN JAN JAN JAN JAN JAN JAN JAN JAN JAN JAN JAN JAN JAN 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 13:54:18 13:54:18 13:54:18 13:54:18 13:54:18 13:54:18 13:54:18 13:54:18 13:54:18 13:54:18 13:54:18 13:54:18 13:54:18 13:54:18 13:54:18 13:54:18 13:54:18 tMVX_DIM: tMVX_DIM: tMVX_DIM: tMVX_DIM: tMVX_DIM: tMVX_DIM: tMVX_DIM: tMVX_DIM: tMVX_DIM: tMVX_DIM: tMVX_DIM: tMVX_DIM: tMVX_DIM: tMVX_DIM: tMVX_DIM: tMVX_DIM: tMVX_DIM: Info TSG: 0 Echo Canceller Info CNV state Info Px level Info Py level Info Pe level Info Post update cnt Info Attempt update cnt Info Divergence cnt Info ERLE bypass cnt Info XTONE count Info Foregrnd switch cnt Info Backgrnd switch cnt Info Xidle count Info Other bypass cnt Info Search bypass cnt Info ERLE estimate Info OpnLpDet switch cnt Debug Stats = 1 = 72 = 57 = 58 = 1718 = 1718 Should be small if = 0 EC working OK = 1515 = 19 = 4 = 2 = 26075 = 47 = 126617680 = 500 = 0
Issue 1.5.4 May 20, 2003
The following is the output for an application load with Telogy 8.1 (ITG Trunk 2.x.26 and IPT 3.0)
-> tsm_stat_req_ecdbg 31 value = 0 = 0x0 -> 2003 3 12 10:08:18 (DIM) :TSG: 31 Echo Canceller Debug Stats 2003 3 12 10:08:18 (DIM) : 2003 3 12 10:08:18 (DIM) : 2003 3 12 10:08:18 (DIM) : 2003 3 12 10:08:18 (DIM) : 2003 3 12 10:08:18 (DIM) : 2003 3 12 10:08:18 (DIM) : 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 -> 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 10:08:18 10:08:18 10:08:18 10:08:18 10:08:18 10:08:18 10:08:18 10:08:18 10:08:18 10:08:18 10:08:18 10:08:18 10:08:18 10:08:18 10:08:18 10:08:18 10:08:18 10:08:18 10:08:18 10:08:18 10:08:18 10:08:18 10:08:18 10:08:18 10:08:18 (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) Px level Py level Pe level acom_estimate len ERLE estimate 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, = -946 = -1273 = -1273 = 728 = 25 = 728 = = = = = = = = = = 0x0 0xf6 0x0 0x0 0x0 0x0 0x0 0x7d 0x0 0xb7 = 0x598 = 0x1d39 = 0x0 = 0x0 = 0x0 = 0x0 = 0x1 = 0x0 = 0x0 = 0xb36c = 0x0 = 0x9 = 0x9 = 0x11 = 0x1
:TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID
internal_use[0] internal_use[1] internal_use[2] internal_use[3] internal_use[4] internal_use[5] internal_use[6] internal_use[7] internal_use[8] internal_use[9] internal_use[10] internal_use[11] internal_use[12] internal_use[13] internal_use[14] internal_use[15] internal_use[16] internal_use[17] internal_use[18] internal_use[19] internal_use[20] internal_use[21] internal_use[22] internal_use[23] internal_use[24]
Issue 1.5.4 May 20, 2003
The following is the an example of the output for an application load with Telogy 8.1 (ITG Trunk 2.1 and IPT 3.0), using reqECDbg instead of tsm_stat_req_ecdbg:
-> reqECDbg 31 value = 0 = 0x0 -> 2003 3 12 10:20:07 (DIM) :TSG: 31 Echo Canceller Debug Stats 2003 3 12 10:20:07 (DIM) : 2003 3 12 10:20:07 (DIM) : 2003 3 12 10:20:07 (DIM) : 2003 3 12 10:20:07 (DIM) : 2003 3 12 10:20:07 (DIM) : 2003 3 12 10:20:07 (DIM) : 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 2003 -> 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 10:20:07 10:20:07 10:20:07 10:20:07 10:20:07 10:20:07 10:20:07 10:20:07 10:20:07 10:20:07 10:20:07 10:20:07 10:20:07 10:20:07 10:20:07 10:20:07 10:20:07 10:20:07 10:20:07 10:20:07 10:20:07 10:20:07 10:20:07 10:20:07 10:20:07 (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) Px level Py level Pe level acom_estimate len ERLE estimate 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, 31, = -946 = -1273 = -1273 = 728 = 25 = 728 = = = = = = = = = = 0x0 0xf6 0x0 0x0 0x0 0x0 0x0 0x7d 0x0 0xb7 = 0x59c = 0x7141 = 0x0 = 0x0 = 0x0 = 0x0 = 0x1 = 0x0 = 0x0 = 0xb36c = 0x0 = 0x9 = 0x9 = 0x11 = 0x1
:TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID
internal_use[0] internal_use[1] internal_use[2] internal_use[3] internal_use[4] internal_use[5] internal_use[6] internal_use[7] internal_use[8] internal_use[9] internal_use[10] internal_use[11] internal_use[12] internal_use[13] internal_use[14] internal_use[15] internal_use[16] internal_use[17] internal_use[18] internal_use[19] internal_use[20] internal_use[21] internal_use[22] internal_use[23] internal_use[24]
The key elds decode as follows: Px level Instantaneous power level of far end user Py level Instantaneous power level of near end user Pe level Error level (echo residual before NLP) Maximum values: 2^28, or 268,435,456, or +3 dbm0 acom_estimate Estimated ACOM in Q4 ERLE estimate Estimated ERL in Q4 (hybrid loss); /4 = ERL in dB
Issue 1.5.4 May 20, 2003
B.2.64.2
tsm_stat_req_error TCID or reqError TCID Safety level: Debug. This query returns the current errors detected by the DSP for the specied channel. Be sure the variable TsmDspStat = 1/0 (section B.2.62, pg 226) is set to 1 or nothing will be output. The parameter TCID species a channel on the ITG card; valid values are in the range of 0 - 31 for Media Card, 0 - 23 for the 24 port card. The following data is displayed: Number of incoming voice packets dropped by the DSP due to invalid generic voice header syntax. Number of transmit voice packets dropped due to voice buffer overow (buffer to micro was busy when DSP attempted to send packet). Estimated number of lost incoming enhancement voice packets (two core packets received without intervening enhancement). This is only for E-ADPCM. Number of dropped incoming enhancement voice packets due to absence of a core packet. This is only for E-ADPCM. Number of packets lost by the network, i.e. from missing incoming RTP sequence numbers (in Telogy 7.01 output only).
This command can be entered repeatedly during a call, the counter values are not reset until a new call is made. The following is the output for an application load containing Telogy 5.0:
-> tsm_stat_req_error 0 value = 0 = 0x0 -> JAN 17 14:44:48 tMVX_DIM: JAN 17 14:44:48 tMVX_DIM: JAN 17 14:44:48 tMVX_DIM: JAN 17 14:44:48 tMVX_DIM: ->
Info Info Info Info
TCID TCID TCID TCID
0, 0, 0, 0,
invalid_header_count to_micro_overflow_count lost_enh_packet_count no_core_packet_count
= = = =
0 0 0 0
The following is the output for an application load containing Telogy 7.0.6.23:
-> tsm_stat_req_error 0 value = 0 = 0x0 -> JAN 01 14:33:55 tMVX_DIM: JAN 01 14:33:55 tMVX_DIM: JAN 01 14:33:55 tMVX_DIM: JAN 01 14:33:55 tMVX_DIM: JAN 01 14:33:55 tMVX_DIM: ->
Info Info Info Info Info
TCID TCID TCID TCID TCID
0, 0, 0, 0, 0,
invalid_header_count to_micro_overflow_count lost_enh_packet_count no_core_packet_count pkt_lost_by_network
= = = = =
0 0 0 0 0
The following is the output for an application load containing Telogy 8.1:
tsm_stat_req_error 0 value = 0 = 0x0 -> 2040 2 16 00:12:21 (DIM) :TCID 0, invalid_header_count
= 0
Issue 1.5.4 May 20, 2003

2040 2040 2040 2040 2040 2040 2040 2040 2 2 2 2 2 2 2 2 16 16 16 16 16 16 16 16 00:12:21 00:12:21 00:12:21 00:12:21 00:12:21 00:12:21 00:12:21 00:12:21 (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID 0, 0, 0, 0, 0, 0, 0, 0, to_micro_overflow_count lost_enh_packet_count no_core_packet_count pkt_lost_by_network rc4key_update_lost_pkt_count invalid_mac_header_count invalid_ssrc_count invalid_payload_count = = = = = = = = 0 0 0 0 0 0 0 0
Issue 1.5.4 May 20, 2003
B.2.64.3
tsm_stat_req_rx_tx TCID Safety level: Debug.
or reqRxTx TCID
This query returns the following data for the current call on the channel. Be sure the variable TsmDspStat = 1/0 (section B.2.62, pg 226) is set to 1 or nothing will be output. The query can be repeated for the duration of the call, the counts will be reset at the beginning of the next call. The parameter TCID species a channel on the ITG card; valid values are in the range of 0 - 31 for Media Card, and 0 - 23 for the 24 port card. 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 classied as silence Minimum jitter Maximum jitter
When VAD is disabled, the Rx and Tx packet counts should be very close in value. The following is the output for an application load containing Telogy 5.0:
-> tsm_stat_req_rx_tx 0 value = 0 = 0x0 -> JAN 17 14:44:36 tMVX_DIM: JAN 17 14:44:36 tMVX_DIM: JAN 17 14:44:36 tMVX_DIM: JAN 17 14:44:36 tMVX_DIM: JAN 17 14:44:36 tMVX_DIM: ->
Info Info Info Info Info
TCID TCID TCID TCID TCID
0, 0, 0, 0, 0,
rx_packet_count tx_packet_count silence_packet_count min_jitter max_jitter
= = = = =
7884 7887 0 20 20
The following is the output for an application load containing Telogy 7.0.6.23:
-> tsm_stat_req_rx_tx 0 value = 0 = 0x0 -> JAN 01 14:33:39 tMVX_DIM: JAN 01 14:33:39 tMVX_DIM: JAN 01 14:33:39 tMVX_DIM: JAN 01 14:33:39 tMVX_DIM: JAN 01 14:33:39 tMVX_DIM: JAN 01 14:33:39 tMVX_DIM: JAN 01 14:33:39 tMVX_DIM: JAN 01 14:33:39 tMVX_DIM: JAN 01 14:33:39 tMVX_DIM: JAN 01 14:33:39 tMVX_DIM: JAN 01 14:33:39 tMVX_DIM: JAN 01 14:33:39 tMVX_DIM: ->
Info Info Info Info Info Info Info Info Info Info Info Info
TCID TCID TCID TCID TCID TCID TCID TCID TCID TCID TCID TCID
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
rx_packet_count tx_packet_count silence_packet_count min_jitter max_jitter rtp_average_jitter tx_grant_sync_drop tx_octets rx_octets aal2_cod_prof_chgs dtmf_tx_octets dtmf_rx_octets
= = = = = = = = = = = =
2979 2983 0 18 22 0 0 477280 476640 0 0 0
Issue 1.5.4 May 20, 2003
-> tsm_stat_req_rx_tx 31 value = 0 = 0x0 -> 2003 3 12 10:28:46 (DIM) :TCID 31, rx_packet_count 2003 3 12 10:28:46 (DIM) :TCID 31, tx_packet_count 2003 3 12 10:28:46 (DIM) :TCID 31, silence_packet_count 2003 3 12 10:28:46 (DIM) :TCID 31, min_jitter 2003 3 12 10:28:46 (DIM) :TCID 31, max_jitter 2003 3 12 10:28:46 (DIM) :TCID 31, rtp_average_jitter 2003 3 12 10:28:46 (DIM) :TCID 31, pkt_lost_by_network 2003 3 12 10:28:46 (DIM) :TCID 31, tx_grant_sync_drop 2003 3 12 10:28:46 (DIM) :TCID 31, tx_octets 2003 3 12 10:28:46 (DIM) :TCID 31, rx_octets 2003 3 12 10:28:46 (DIM) :TCID 31, aal2_cod_prof_chgs 2003 3 12 10:28:46 (DIM) :TCID 31, dtmf_tx_packets 2003 3 12 10:28:46 (DIM) :TCID 31, dtmf_rx_packets 2003 3 12 10:28:46 (DIM) :TCID 31, sid_tx_packet_count 2003 3 12 10:28:46 (DIM) :TCID 31, sid_rx_packet_count 2003 3 12 10:28:46 (DIM) :TCID 31, tx_last_timestamp 2003 3 12 10:28:46 (DIM) :TCID 31, rx_last_timestamp 2003 3 12 10:28:46 (DIM) :TCID 31, tx_ext_seq_num 2003 3 12 10:28:46 (DIM) :TCID 31, rx_ext_seq_num 2003 3 12 10:28:46 (DIM) :TCID 31, tx_last_seq_num 2003 3 12 10:28:46 (DIM) :TCID 31, rx_last_seq_num 2003 3 12 10:28:46 (DIM) :TCID 31, tx_last_pkt_type 2003 3 12 10:28:46 (DIM) :TCID 31, rx_last_pkt_type 2003 3 12 10:28:46 (DIM) :TCID 31, tx_net_pkts 2003 3 12 10:28:46 (DIM) :TCID 31, rx_net_pkts 2003 3 12 10:28:46 (DIM) :TCID 31, rx_last_ssrc 2003 3 12 10:28:46 (DIM) :TCID 31, rx_out_of_order_pkts 2003 3 12 10:28:46 (DIM) :TCID 31, rx_late_packets 2003 3 12 10:28:46 (DIM) :TCID 31, rx_early_packets ->
= = = = = = = = = = = = = = = = = = = = = = = = = = =
= 1973 1008 15851221 0 30 30 0 0 30961360 62788 0 0 0 7732522 233 1886933680 1886934720 118 0 281 2209 0 0 0 0 -1430532899 0 0 = 0
Issue 1.5.4 May 20, 2003
B.2.64.4
tsm_stat_req_tele_levels TCID or reqTeleLevel TCID Safety level: Debug. This query returns the current audio levels measured in the DSP for the specied gateway channel. The parameter TCID species a channel on the ITG card; valid values are in the range of 0 - 31 for Media Card, 0 - 23 for Pentium Card. The following 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 isnt accurate). Tx mean in 0.1 linear PCM units (ignore, apparently isnt accurate). This command can be entered repeatedly during a call, the counter values are not reset until a new call is made. If a call is active but there is a problem with the PCM data transfer (see PRS MP08354), the rx_level and tx_levels will both be very large (600 800) even when a DTMF digit is being pressed on the TDM set.
-> tsm_stat_req_tele_levels 0 value = 0 = 0x0 -> JAN 17 14:44:59 tMVX_DIM: Info JAN 17 14:44:59 tMVX_DIM: Info JAN 17 14:44:59 tMVX_DIM: Info JAN 17 14:44:59 tMVX_DIM: Info ->
TCID TCID TCID TCID
=0 =0 =0 =0
rx_level tx_level rx_mean tx_mean
= = = =
-610 -610 -40 -20
For Telogy 8.1, the output is:

-> reqTeleLevel 31 value = 0 = 0x0 -> 2003 3 12 10:33:16 (DIM) :TCID =31 rx_level = -610 2003 3 12 10:33:16 (DIM) :TCID =31 tx_level = -440 2003 3 12 10:33:16 (DIM) :TCID =31 rx_mean = 0 2003 3 12 10:33:16 (DIM) :TCID =31 tx_mean = -30 2003 3 12 10:33:16 (DIM) :TCID =31 background_noise_level 2003 3 12 10:33:16 (DIM) :TCID =31 rx_level = -610 2003 3 12 10:33:16 (DIM) :TCID =31 tx_level = -440 2003 3 12 10:33:16 (DIM) :TCID =31 rx_mean = 0 2003 3 12 10:33:16 (DIM) :TCID =31 tx_mean = -30 2003 3 12 10:33:16 (DIM) :TCID =31 background_noise_level reqTeleLevel 31 value = 0 = 0x0 -> 2003 3 12 10:33:39 (DIM) :TCID =31 rx_level = -610 2003 3 12 10:33:39 (DIM) :TCID =31 tx_level = -250 2003 3 12 10:33:39 (DIM) :TCID =31 rx_mean = 0 2003 3 12 10:33:39 (DIM) :TCID =31 tx_mean = -470 2003 3 12 10:33:39 (DIM) :TCID =31 background_noise_level 2003 3 12 10:33:39 (DIM) :TCID =31 rx_level = -610 2003 3 12 10:33:39 (DIM) :TCID =31 tx_level = -250 2003 3 12 10:33:39 (DIM) :TCID =31 rx_mean = 0 2003 3 12 10:33:39 (DIM) :TCID =31 tx_mean = -470 2003 3 12 10:33:39 (DIM) :TCID =31 background_noise_level reqTeleLevel 31 value = 0 = 0x0
= 26024
= 26024
= 26024
= 26024
Issue 1.5.4 May 20, 2003

-> 2003 3 12 10:33:43 (DIM) :TCID =31 rx_level = -610 2003 3 12 10:33:43 (DIM) :TCID =31 tx_level = -320 2003 3 12 10:33:43 (DIM) :TCID =31 rx_mean = 0 2003 3 12 10:33:43 (DIM) :TCID =31 tx_mean = 50 2003 3 12 10:33:43 (DIM) :TCID =31 background_noise_level 2003 3 12 10:33:43 (DIM) :TCID =31 rx_level = -610 2003 3 12 10:33:43 (DIM) :TCID =31 tx_level = -320 2003 3 12 10:33:43 (DIM) :TCID =31 rx_mean = 0 2003 3 12 10:33:43 (DIM) :TCID =31 tx_mean = 50 2003 3 12 10:33:43 (DIM) :TCID =31 background_noise_level reqTeleLevel 31 value = 0 = 0x0 -> 2003 3 12 10:33:46 (DIM) :TCID =31 rx_level = -610 2003 3 12 10:33:46 (DIM) :TCID =31 tx_level = -260 2003 3 12 10:33:46 (DIM) :TCID =31 rx_mean = 0 2003 3 12 10:33:46 (DIM) :TCID =31 tx_mean = -90 2003 3 12 10:33:46 (DIM) :TCID =31 background_noise_level 2003 3 12 10:33:46 (DIM) :TCID =31 rx_level = -610 2003 3 12 10:33:46 (DIM) :TCID =31 tx_level = -260 2003 3 12 10:33:46 (DIM) :TCID =31 rx_mean = 0 2003 3 12 10:33:46 (DIM) :TCID =31 tx_mean = -20 2003 3 12 10:33:46 (DIM) :TCID =31 background_noise_level
= 26024
= 26024
= 26024
= 26024
Note that the tx_level changed during the samples. For the sake of illustrating the response during trafc, a voice sample was provided one way across the network. This resulted in a constant rx_level (-610) and varying tx_level (from 1440 to -250, with a mean level ranging from -470 to +50.
Issue 1.5.4 May 20, 2003
B.2.64.5
tsm_stat_req_vp_delay TCID or reqVpDelay TCID Safety level: Debug. This query returns the DSP's VPU (Voice Playout Unit) statistics for the call on the channel specied. Be sure the variable TsmDspStat = 1/0 (section B.2.62, pg 226) is set to 1 or nothing will be output. The VPU operates on segments of 10 msec of voice. The parameter TCID species a channel on the ITG card; valid values are in the range of 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 number Number of segments replayed due to the lost packets Number of idle (noise) segments being played out due to either lost packets or voice playout FIFO buffer under-run Number of voice segments dropped due to the voice playout FIFO buffer over-run 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 not reset until a new call is made. The following is the output for an application load containing Telogy 5.0:
-> tsm_stat_req_vp_delay 0 value = 0 = 0x0 -> JAN 17 14:45:22 tMVX_DIM: Info JAN 17 14:45:22 tMVX_DIM: Info JAN 17 14:45:22 tMVX_DIM: Info JAN 17 14:45:22 tMVX_DIM: Info JAN 17 14:45:22 tMVX_DIM: Info JAN 17 14:45:22 tMVX_DIM: Info ->
TCID TCID TCID TCID TCID TCID
0, 0, 0, 0, 0, 0,
avg_playout_delay lost_packet_count replay_packet_count idle_packet_count dropped_packet_count rx_packet_count
= = = = = =
60 0 0 14 0 20382
-> tsm_stat_req_vp_delay 0 value = 0 = 0x0 -> JAN 01 14:33:21 tMVX_DIM: Info JAN 01 14:33:21 tMVX_DIM: Info JAN 01 14:33:21 tMVX_DIM: Info JAN 01 14:33:21 tMVX_DIM: Info JAN 01 14:33:21 tMVX_DIM: Info JAN 01 14:33:21 tMVX_DIM: Info JAN 01 14:33:21 tMVX_DIM: Info ->
TCID TCID TCID TCID TCID TCID TCID
0, 0, 0, 0, 0, 0, 0,
avg_playout_delay lost_packet_count replay_packet_count idle_packet_count dropped_packet_count rx_packet_count avg_frame_jitter
= = = = = = =
60 0 0 0 0 4140 0
-> 2003 3 12 10:37:50 (DIM) :TCID 31, avg_playout_delay = 57 2003 3 12 10:37:50 (DIM) :TCID 31, lost_packet_count = 0
Issue 1.5.4 May 20, 2003

2003 2003 2003 2003 2003 2003 2003 2003 2003 -> 3 3 3 3 3 3 3 3 3 12 12 12 12 12 12 12 12 12 10:37:50 10:37:50 10:37:50 10:37:50 10:37:50 10:37:50 10:37:50 10:37:50 10:37:50 (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) (DIM) :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID :TCID 31, 31, 31, 31, 31, 31, 31, 31, 31, replay_packet_count = idle_packet_count = dropped_packet_count = rx_packet_count = avg_frame_jitter = adpt_po_buf_delay_inc= adpt_po_buf_delay_dec= po_buf_underflow_cnt = cell_starve_evt_cnt = 0 23631180 0 9874 0 0 0 0 0
Issue 1.5.4 May 20, 2003
B.2.65
udpstatShow Safety level: Debug. This command displays the UDP protocol statistics.
-> udpstatShow UDP: 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 failed value = 28 = 0x1c ->
B.2.66
upgradeErase Safety level: Destructive/Semi-Normal. Often used before downloading a new image or provisioning to ensure a clean load. A reboot after this command but before the new software is loaded or provisioning downloaded cannot complete.
Caution:
For the Media Card, this function will delete the le /C:/exec so that on reboot the card will boot to the BootROM prompt.
This command erases the application binaries from the ITG cards Flash memory. Can be executed from the BIOS or VxWorks prompt.
-> upgradeErase value = 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
Issue 1.5.4 May 20, 2003
B.3
Disk commands
B.3.1 reformatAdrive Safety level: Extremely destructive recovery.
Caution: Caution:
DO NOT ISSUE THIS COMMAND with the D channel card in an SMC face-plate slot. NEVER reformat a PCMCIA card used for ITG cards on a PC.
This command basically clears the entire contents of the PCMCIA software delivery card inserted in the faceplate. This is the only way to reformat this card; formatting on a PC makes the card effectively scrap as far as the ITG cards is concerned.
-> reformatAdrive
B.3.2
reformatCdrive Safety level: Extremely destructive recovery.
Caution:
DO NOT ISSUE THIS COMMAND unless you want to completely clear the on-card drive.
This command basically clears the entire contents of the internal PCMCIA daughterboard memory card. This is the only way to reformat this card; extracting it from the system can destroy it unless extreme care is taken, and because this command allows the user to reformat it on location, extraction is pointless.
-> reformatCdrive
B.3.3
SMC: formatAtaCard 0/1 Safety level: Extremely destructive recovery.
Caution:
DO NOT ISSUE THIS COMMAND unless you want to completely clear the on-card drive.
This command basically clears the entire contents of the internal (1) or external (0) PCMCIA memory card. This is the only way to reformat this card; extracting it from the system can destroy it unless extreme care is taken, and because this command allows the user to reformat it on location, extraction is pointless.
-> formatAtaCard 0 -> formatAtaCard 1
Issue 1.5.4 May 20, 2003
B.4
Software download commands

When downloading software to the card, three commands and two methods are available. B.4.1 Download over the IP network The user may use the swDownload command (B.1.41, page 166) to obtain the software from 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 the swCopy command (the VxWorks utility) to obtain the software load, but this command is not as reliable as upgradePCMCIA. The upgradePCMCIA is the only supported IPL and IPT sa exec le download command; swCopy is a VxWorks command that may or may not work. These two commands check the le format, CRC checksum and le size.
-> swCopy /A:/IPT30053.sa -> upgradePCMCIA /A:/IPT30053.sa (fix for Q00511514)
Issue 1.5.4 May 20, 2003
Appendix C
C.1 Requirements
C.1.1
Annex 1 - BCM 2.x - IP Trunk Interoperability
BCM Requirements MCDN Supported in all Market Proles Supported on all 2.0 and 2.5 hardware congurations The following keycodes are required:
Part Numbers
NTKC0002 A0805827
Applicable Markets: Hardware: Keycodes:

Item Description
BCM MCDN & Q.SIG Voice Networking Authorization Code
A minimum of 2 IP trunks are required to user MCDN over IP. The following part numbers represent all the possible keycodes to meet your customers needs.
Item Description
BCM VoIP gateway - 2 Trunks Authorization Code BCM VoIP gateway - 4 Trunks Authorization Code BCM VoIP gateway - 8 Trunks Authorization Code BCM VoIP gateway - 16 Trunks Authorization Code BCM VoIP gateway - 32 Trunks Authorization Code
Part Numbers
NTAB3116 NTKC0060 NTKC0061 NTKC0062 NTKC0063 A0792743 A0843712 A0843713 A0843714 A0843715
Note: MCDN authorization keycode is bundled with the Q.Sig keycode, which is only supported in international market proles (not North America) and isnt supported over an IP link. Dependencies: Software: Hardware: MCDN over IP requires VoIP Trunks and BCM Release 2.5 FP1 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)
Issue 1.5.4 05 May 03
Section: Page 243
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 (Enterprise Feature 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 145/ 147) 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 following software 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 Enterprise or NAS/VNS software package should be ordered. For Centralized Voicemail the following is required: M1 based Call Pilot software: Any Call Pilot conguration is supported. Meridian Mail software: Meridian Mail Rel. 7 (MM7) or above - currently shipping MM13.
Section: Page 244
Issue 1.5.4 05 May 03
The appropriate number of PRI/ITG cards and D-channel handlers in the switch to support the PRI/IP links to the BCMs are also needed.
C.2
BCM Configuration Tips

For more Information on BCM Conguration Tips refer to the: C.2.1 BCM IP Telephony Guide , Chapter 6 Typical Network Applications using MCDN BCM IP Telephony Guide , Appendix D Interoperability BCM Programming and Operations Guide, Chapter 14 Conguring Private Networks.
Basic Set to Set Calling This section is a conguration tip based on a combination of the BCM IP Telephony Guide and BCM Programming and Operations Guide. For more detailed information refer 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 required.
Issue 1.5.4 05 May 03
Section: Page 245
Verify core telephony dialing plan: Services Telephony Services Lines VoIP Lines Enabled VoIP Lines Line 0XX 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 XXXX Line access Line pool access: Ensure all DNs that you want to access the VoIP trunks have line pool access.
Section: Page 246
Issue 1.5.4 05 May 03
Services Telephony Services Call routing Routes Route XXX Ensure the VoIP trunks are assigned to a route for outbound calling. Verify the route 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 out of the BCM. Note: Typically the DN Type is set to private for BCM-ITG calls.
Issue 1.5.4 05 May 03
Section: Page 247
Services Telephony Services Call routing Destination codes Destination codes are numbers that are dialed from the intercom path of BCM to gain access to a route. Since these values are dialed from the intercom they may not conict with other dialing feature prexes in the BCM. This table should help:
Item Park Prex Description The Park prex is the rst digit of the call park retrieval code that you enter to retrieve a parked call. The External code setting allows you to assign the external line access code for T7100 telephones and ATA 2s to access external lines. The Direct dial digit setting allows you to specify a single system-wide digit to call a direct dial telephone. Calls answered without DISA require no password to access the BCM. This is the DN used for this scenario. For calls answered with DISA, the system presents a stuttered dial tone to prompt a caller to enter a valid password. This is the DN used for this scenario. A simple access code used to access the line pools from the intercom. As stated. Any valid B1 DN in the system or B2 DN in the system. Default Value 1
External Code
None
Direct Dial Digit
Auto DN
None
DISA DN
None
Line Pool Code Other Destination Codes Any valid DN in the BCM
9 for Pool A None Varies
Ensure the destination codes have been added. Typically for CDP dialing plans this 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 advanced fall back routing. Please refer to the BCM programming and operation guide for more info. On the destination code in question make sure it is using the route built for the VoIP trunks. The absorb length value will absorb X digits from your destination code if set.Typically this is set to none. Default value is all.
Section: Page 248
Issue 1.5.4 05 May 03
Services Telephony Services General settings Dialing plan Private Network 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 for before attempting to place the call. If this value is set to short some of the digits may not be sent.
Services Telephony Services General settings Dialing plan Public Network 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 for before attempting to place the call. If this value is set to short some of the digits may not be sent.
Issue 1.5.4 05 May 03
Section: Page 249
Services Telephony Services General settings Access codes If you are using UDP dialing then ensure the private access code on the BCM is 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/line data Received number Ensure the public number is set to match the DN of the set you wish to assign this line to.
Verify Target Line Assignment to DNs: Services Telephony Services System DNs Active set DNs DN XXXX Line access Line assignment Ensure the appropriate target line is assigned to the DN.
Verify MCDN settings: Services Telephony Services General settings NetworkServices MCDN 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 IP address of the ITG card. The QoS monitor should be disabled for initial call testing as it can cause calls to fail. After basic set to set calling is functioning QoS monitor can be enabled but it MUST be enabled on both the ITG and BCM for it to function on the BCM.
Section: Page 250
Issue 1.5.4 05 May 03
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 trunks which are then used to direct the call to the appropriate gateway. Typically this value is 1 digit for CDP and 4 digits for UDP. The destination digits are NOT stripped off or added to the dialed digits. They are just for filtering. Note: The destination digits field is a space delimited field which allows for multiple 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 ITG. Note: By default the BCM uses G.729 for all outgoing VoIP trunks.
Issue 1.5.4 05 May 03
Section: Page 251
M1 Programming for Basic Set to Set Calling For more detailed programming information on CDP/UDP dialing see the corresponding sections below or refer to the appropriate NTPs. Here are some general programming hints: ITG payload sizes should be set to 30 ms. Voice Activity Detection (VAD) should be configured to the same value on both 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 as the BCMs C.2.2 Calling Line ID BCM programming for Calling Line ID BCM must have a few parameters congured to ensure Calling Line ID is sent properly to the M1. Services Telephony Services General settings: Ensure the business name is configured. In order to format the CLID in an easier to read format place a space after the business name. Services Telephony Services System DNs Active set DNs DN XXXX General Ensure the Name is configured for the DN. The default value is the DN itself. Services Telephony Services System DNs Active set DNs DN XXXX Line access Ensure the OLI number is configured for each DN. This value is phone number that will be sent out as your CLID when calling into the network. Typically this is either your DID number or the main business telephone number. The BCM will then send the CLID as Business name|DN Name as the name and the OLI number as the number. M1 Programming for Calling Line ID For more detailed programming information on Calling Line ID see the appropriate NTPs.
Section: Page 252
Issue 1.5.4 05 May 03
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 BCM to the PSTN using the number desired to tandem. Ensure Destination Codes are built for any dialed number combination for tandem calls. Ensure public/private DN lengths are of sufficient length to handle the tandem calls. Verify programming of Remote Access Packages on Lines: Services Telephony Services Lines VoIP lines Enabled VoIP lines Line 0XX - General Verify all VoIP lines have a remote package assigned to them. Add if necessary.
Verify programming of Remote Access Packages: Services Telephony Services General settings Remote access packages Package XX Ensure the remote access package has line pool access to the outgoing PSTN trunks desired to be used in the tandem call.
Issue 1.5.4 05 May 03
Section: Page 253
Add if necessary.
M1 Programming for Tandem Calls For more detailed programming information on tandem calls see the appropriate NTPs. Here are some general programming hints For tandem calls from the M1 to the BCM and out to the PSTN the M1 must have the call congured for a Called Party Number TON/NPI value of Unknown/ Private. The BCM cannot tandem a Called Party Number TON/NPI of National/ E.164. Note: For calls from the BCM to the M1 and then out to the PSTN this restriction doesnt apply.
C.2.4
Private Network Identier (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 Length ( if the dialing string is 6 393 2222. This Private DN Length is 8. ) Private Access Code:
Section: Page 254
Issue 1.5.4 05 May 03
General Settings Access Code Private Access Code. set to an appropriate code. This value corresponds to the AC1 value in the M1. General Settings Access Code Destination Code. Services Call Routing Destination Codes, build destination code that matches the Private Access Code with absorb length of 0. M1 Programming for UDP Private Access Code Overlay 86, LD 86 o o o o REQ : PRT CUST : <as applicable> FEAT : ESN Make note of the AC1 code
To change Private Access Code Overlay 86, LD 86 o o o o REQ : CHG CUST : <as applicable> FEAT : ESN, keep pressing enter until you reach the AC1 prompt At the AC1 prompt make your choice
To check UDP Programming Overlay 90, LD 90 o o o o o o REQ : PRT CUST : <as applicable> FEAT : NET TYPE : LOC LOC : press enter, this will list all the location codes that are programmed. HLOC is the home location of the M1 itself.
To program new UDP values to route Overlay 90, LD 90 o o o o o o REQ : CHG CUST : <as applicable> FEAT : NET TYPE : AC1 LOC : (enter a number) RLI : ( enter the RLI corresponding to the route)
Issue 1.5.4 05 May 03
Section: Page 255
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 dened in LD 16 - RDB PNI in M1 programming Resources - Media Bay Modules - Bus XX Cdx KSU: PRI Protocol: SL-1 Set PrivNetId to the PNI of the switch on the other end
Note: This is the number dened in LD 15 Net PNI in M1 programming. Set Destination Code (Services Routing Des Code) to the corresponding Steering Codes of the Neighboring nodes. M1 Programming for CDP Distant Steering Codes Overlay 87, LD 87 o o o o o REQ : PRT CUST : <as applicable> FEAT : CDP TYPE : DSC (Distant Steering Code) DSC : press enter, this will list all the DSC programmed
To check RLI (Route Line Index) Overlay 86, LD 86 o o o o REQ : PRT CUST : <as applicable> FEAT : RLB RLI : (press enter) this will display all the RLIs
To program new CDP value to route Overlay 87, LD 87 o o o o o REQ : CHG CUST : <as applicable> FEAT : CDP TYPE : DSP DSC : (enter number) if this is for a BCM with DNs 44xx enter 44
Section: Page 256
Issue 1.5.4 05 May 03
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 target line appearing on each Set External VMsg to Y M1 Programming for MWI C.2.8 RCAP should be set to MWI and ND2 RLS ID should be set to 36
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 yes o NCRD set to yes Verifying NASA is Active Overlay 22, LD 22 o REQ : PRT o TYPE : ADAN DCH (slot number) o NASA should be set to yes If NASA is not on: disable the D channel Overlay 96, LD 96
Issue 1.5.4 05 May 03
Section: Page 257
o Assume D channel is "12"; it may be any provisioend number o 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 Overlay 32, LD 32 o STAT x y z Displays the status of loop x, shelf y, card z (for Option 11, use "STAT z" only) o DIS x y z Program the D channel Overlay 17, LD 17 o o o o o o REQ : CHG TYPE : ADAN ADAN : CHG DCH x Keep pressing enter until you get to NASA NASA yes 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 o o o o REQ : PRT TYPE : TIE CUST : <as applicable> TN (slot number) [space] 1 Keep pressing enter until your TIE block is displayed, and look for the line where RTMB (RouTe and MemBer) is displayed. This will be in the form (route number) [space] (member number) REQ : PRT TYPE : RDB CUST : <as applicable> Route : Enter the route defined in LD 20 Keep pressing enter until all values are displayed. Check if NCRD is yes.
Overlay 21, LD 21 o o o o o o
If NCRD is set to no
Section: Page 258
Issue 1.5.4 05 May 03
Overlay 16, LD 16 o o o o o o o C.2.9 REQ : CHG TYPE : RDB CUST : <as applicable> ROUT : (route number) from LD 20 Keep pressing enter until you get NCRD and type Yes Keep pressing enter until you get the REQ prompt again REQ : end
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
Issue 1.5.4 05 May 03
Section: Page 259
TYPE : ADAN ADAN : CHG DCH (slot number) Keep pressing enter until you get to RCAP RCAP TAT Keep pressing enter until you get the REQ prompt again 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 Keep pressing enter until you get the REQ prompt again REQ end
Section: Page 260
Issue 1.5.4 05 May 03
Last Page of The Document
Issue 1.5.4 05 May 03
Section: Page 261
Section: Page 262
Issue 1.5.4 05 May 03
Index of commands
A arpFlush ................................................................................................................................. 171 arpShow ................................................................................................................................ 171 attrib ...................................................................................................................................... 172 auditRebootSet ...................................................................................................................... 120 auditRebootTimeSet .............................................................................................................. 120 auditShow .............................................................................................................................. 121 auditTaskSet .......................................................................................................................... 121 C cardReset ............................................................................................................................... 122 cd ........................................................................................................................................... 122 chkdsk ................................................................................................................................... 173 clearLeader ............................................................................................................................ 122 copy ....................................................................................................................................... 123 D dchipResTableShow .............................................................................................................. 124 DCHmenu ............................................................................................................................. 126 devs ....................................................................................................................................... 174 DimECStat ............................................................................................................................ 175 dimPrintChannelInfo ............................................................................................................. 176 dosFsConfigShow ................................................................................................................. 134 dspFatalErrorCountClear ...................................................................................................... 178 dummy_trap .......................................................................................................................... 178 E exit ......................................................................................................................................... 178 F firmwareVersionShow .......................................................................................................... 135 flashConfigShow ................................................................................................................... 179 formatAtaCard ...................................................................................................................... 241 G gkShow .................................................................................................................................. 135 H h ............................................................................................................................................. 180 h323CallTrace ....................................................................................................................... 140 h323SessionShow ................................................................................................................. 143
Issue 1.5.4 05 May 03
I i .............................................................................................................................................. 145 icmpstatShow ........................................................................................................................ 181 ifShow ................................................................................................................................... 146 igccAddTrace ........................................................................................................................ 182 igccNoTrace .......................................................................................................................... 182 inetstatShow .......................................................................................................................... 182 iosFdShow ............................................................................................................................. 184 IPInfoShow ............................................................................................................................ 148 ipstatShow ............................................................................................................................. 185 iptSessionShow ..................................................................................................................... 150 itgCardShow .......................................................................................................................... 152 itgChanStateShow ................................................................................................................. 155 itgExcpCountClear ................................................................................................................ 185 itgExcpCountShow ................................................................................................................ 185 itgMemShow ......................................................................................................................... 156 itgMsgCtrShow ..................................................................................................................... 157 itgShell .................................................................................................................................. 186 L ldrResTableShow .................................................................................................................. 158 lkup ........................................................................................................................................ 186 ll ............................................................................................................................................. 159 lnIsaBroadcastShow .............................................................................................................. 187 lnIsaBroadcastThreshold ....................................................................................................... 187 lnIsaShowLostBroadcast ....................................................................................................... 188 lnPciBcastFilterOff ................................................................................................................ 188 lnPciBcastFilterOn ................................................................................................................ 188 lnPciBroadcastShow .............................................................................................................. 189 lnPciBroadcastThreshold ...................................................................................................... 189 lnPciShowLostBroadcast ...................................................................................................... 190 ls ............................................................................................................................................ 190 M mac21440BroadcastShow ..................................................................................................... 191 mac21440BroadcastThreshold .............................................................................................. 191 mbufShow ............................................................................................................................. 192 mixLevelOn ........................................................................................................................... 193 mixMemFindAll .................................................................................................................... 193 mixOptionOn ......................................................................................................................... 195 mixSetLogOpt ....................................................................................................................... 195 mkdir ..................................................................................................................................... 197 monIPDebugSet .................................................................................................................... 198 monUtility ............................................................................................................................. 199
Issue 1.5.4 05 May 03
mRouteAdd ........................................................................................................................... 202 mRouteDelete ........................................................................................................................ 202 mRouteShow ......................................................................................................................... 202 N netHelp .................................................................................................................................. 203 nmmAtpmTranTblDnld ........................................................................................................ 203 numNodesInFallbackShow ................................................................................................... 160 NVRClear .............................................................................................................................. 160 NVRGWSet .......................................................................................................................... 161 NVRIPSet .............................................................................................................................. 162 NVRIPShow .......................................................................................................................... 162 NVRSMSet ........................................................................................................................... 162 P ping ........................................................................................................................................ 163 pins - patch in service ............................................................................................................ 204 plis - patch list ....................................................................................................................... 205 pload - patch load .................................................................................................................. 207 PMSI, see Property Management System Interface poos - patch out of service .................................................................................................... 207 pout - patch out, or unload .................................................................................................... 208 print_cdp ............................................................................................................................... 214 print_dsc ................................................................................................................................ 215 print_ip_table ........................................................................................................................ 210 print_loc ................................................................................................................................ 214 print_npa ............................................................................................................................... 212 print_nxx ............................................................................................................................... 213 print_spn ................................................................................................................................ 213 print_tsc ................................................................................................................................. 215 pstat - patch status ................................................................................................................. 209 pwd ........................................................................................................................................ 163 R reformatAdrive - VxWorks shell .......................................................................................... 241 reformatCdrive - VxWorks shell ........................................................................................... 241 reqECDbg .............................................................................................................................. 229 reqError ................................................................................................................................. 232 reqTeleLevel ......................................................................................................................... 236 reqVpDelay ........................................................................................................................... 238 resetOM ................................................................................................................................. 163 rm .......................................................................................................................................... 216 rmdir ...................................................................................................................................... 217 routeAdd ................................................................................................................................ 164
Issue 1.5.4 05 May 03
routeDelete ............................................................................................................................ 164 routeShow .............................................................................................................................. 164 rtpPortCompress .................................................................................................................... 218 rtpPortNonCompress ............................................................................................................. 218 S serialNumShow ..................................................................................................................... 165 set_time ................................................................................................................................. 219 setLeader - login window ...................................................................................................... 165 setTraceOption ...................................................................................................................... 220 shellPasswordNvramClear .................................................................................................... 222 shellPasswordSet ................................................................................................................... 165 shellTimeoutGet .................................................................................................................... 222 shellTimeoutSet ..................................................................................................................... 222 showMemConfig ................................................................................................................... 222 swDownload .......................................................................................................................... 166 swVersionShow ..................................................................................................................... 166 T tcpstatShow ........................................................................................................................... 223 tlanDuplexSet ........................................................................................................................ 224 tlanSpeedSet .......................................................................................................................... 225 tsm_stat_req_ecdbg ............................................................................................................... 229 tsm_stat_req_error ................................................................................................................. 232 tsm_stat_req_rx_tx ................................................................................................................ 234 tsm_stat_req_tele_levels ....................................................................................................... 236 tsm_stat_req_vp_delay .......................................................................................................... 238 tsmChanShow ........................................................................................................................ 167 TsmDspStat ........................................................................................................................... 226 tsmSetTraceOption ................................................................................................................ 227 U udpstatShow .......................................................................................................................... 240 upgradeErase ......................................................................................................................... 240 useIPTForRingBack .............................................................................................................. 169 useM1ForRingBack .............................................................................................................. 169 V vxWorksShell ........................................................................................................................ 170
Issue 1.5.4 05 May 03

Ipt3 Expert Level Support Guide

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Ipt3 Expert Level Support Guide

Загружено:

Авторское право:

Доступные форматы

Expert Info

IP Trunk 3.0 Expert Level Support Guide

NORTEL NETWORKS CONFIDENTIAL

Nortel Networks Condential

Issue 1.5.4 05 May 03

IP Trunk 3.0 Expert Level Support Guide Page 2

Nortel Networks Condential

IP Trunk 3.0 module descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.2 3.3 3.4

3.6 3.7 3.8 3.9

Potentail provisioning problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Issue 1.5.4 05 May 03

IP Trunk 3.0 Expert Level Support Guide

Section: Table of Contents Page 3

Nortel Networks Condential

Debugging the shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Debugging the node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

6.4 6.5 6.6 6.7

Call processing debug commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Debugging audio issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

BIOS / BootROM functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Maintenance Task (Task Monitor Function) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Section: Table of Contents Page 4

IP Trunk 3.0 Expert Level Support Guide

Issue 1.5.4 05 May 03

Nortel Networks Condential 10.3 CLI commands for Audit/Maintenance task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Patcher Tool Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Installation and upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Card Startup Log Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Appendix A Configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Appendix B IP Trunk Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Issue 1.5.4 05 May 03

IP Trunk 3.0 Expert Level Support Guide

Section: Table of Contents Page 5

Section: Table of Contents Page 6

IP Trunk 3.0 Expert Level Support Guide

Issue 1.5.4 05 May 03

Issue 1.5.4 05 May 03

IP Trunk 3.0 Expert Level Support Guide

Section: Table of Contents Page 7

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

Section: Table of Contents Page 8

IP Trunk 3.0 Expert Level Support Guide

Issue 1.5.4 05 May 03

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

Issue 1.5.4 05 May 03

IP Trunk 3.0 Expert Level Support Guide

Section: Table of Contents Page 9

Nortel Networks Condential

Section: Table of Contents Page 10

IP Trunk 3.0 Expert Level Support Guide

Issue 1.5.4 05 May 03

Nortel Networks Condential

Issue 1.5.4 05 May 03

IP Trunk 3.0 Expert Level Support Guide

Nortel Networks Condential

IP Trunk 3.0 Expert Level Support Guide

Issue 1.5.4 05 May 03

Nortel Networks Condential

Issue 1.5.4 05 May 03

IP Trunk 3.0 Expert Level Support Guide

Nortel Networks Condential

Resolving IP Trunk problems