Troubleshooting Guide - Chapter 15 - Diagnostic Tests [Cisco BTS 10200 Softswitch]

Table Of Contents

Diagnostic Tests

Introduction

Media Gateway Tests

Subscriber Termination Tests

Signaling System 7 Trunk Termination Tests

Integrated Services Digital Network Trunk Termination Tests

Channel-Associated Signaling Trunk Termination Tests

Announcement Trunk Termination Tests

Troubleshooting Using Snoop

Query Verification Tool and Translation Verification Tool

Tool Requirements

Query Verification Tool

Overview

Command Format

Response Format

Query Errors

Query Verification Tool Measurements

Translation Verification Tool

Overview

Command Format

Response Format

Translation Verification Tool Measurements

Using Query Verification Tool and Translation Verification Tool Together

LNP Examples

Example 1

Example 2

Example 3

Example 4

Example 5

Network Loopback Test for Network-based Call Signaling/Media Gateway Control Protocol Endpoints

Overview

Restrictions

Installing

Configuring

Configuration Examples

Using/Operating the Network Loopback Test for Network-based Call Signaling/Media Gateway Control Protocol Endpoints

Dedicated Test Trunk Group

Shared Test Trunk Group

Configuring the Originating Trunk Group

Session Initiation Protocol Subscriber Registration Status Check

System Health Report

Fast Audit and Sync Tool

Restrictions and Limitations

Using the bts_audit Tool

Using the bts_sync Tool

Command Parameters

Command Responses

Database Out of Synchronization

ISDN Network Loopback Test

Configuring

Originating Trunk Group

Call Agent Configuration Table

Dial Plan

Sample Configurations

Line Loopback Tests over an ISDN Trunks

Trunk Loopback Tests over an ISDN Trunk

Enhanced Traffic Measurement

Measurement Data Transport and Access

Measurement Data Event Reports

Operating

Provisioning Measurement Report Types

Measurement Report Summaries

Reporting Current Interval Counts

Clearing Current Interval Counts

Measurements

ISDN Protocol Counters

Call Processing Counters

MGCP Adapter Counters

Session Initiation Protocol Counters

PSTN Trunk Testing

Test Overview

Cisco BTS 10200 Originating Test Line

Function

Test Equipment

Test Line

Trunk Access

Trunk Access and Test Termination Number Format

Trunk Under Test Outpulsing

Cisco BTS 10200 Terminating Test Line

Function

Test Equipment

Test Line

TTL Dial Plan

Near End Test Origination Test Line

Far End Originating Test Line

Function

Test Equipment

Test Line

Trunk Access

Trunk Access and Test Termination Number Format

Trunk Under Test Outpulsing

Far End Terminating Test Line

Function

Test Equipment

Test Line

TTL Dial Plan

1xx Test Lines

1xx Test Line Support

100 Test-Balance

101 Test-Communications and Test

102 Test-Milliwatt

103 Test-Signaling and Supervisory

104 Test-2-Way Test

105 Test-ROTL/Responder

107 Test Line-Data Transmission

108 Test-Digital Loopback

109 Test-Echo

Diagnostic Tests

Revised: December 2, 2008, OL-8000-30

Introduction

This chapter describes diagnostic tests that can be performed on media gateways, subscriber terminations, and trunk terminations. All media gateways, subscriber and trunk terminations must be in the MAINT state for testing. The following tests are described in this section:

•Media Gateway Tests

•Subscriber Termination Tests

•Signaling System 7 Trunk Termination Tests

•Integrated Services Digital Network Trunk Termination Tests

•Channel-Associated Signaling Trunk Termination Tests

•Announcement Trunk Termination Tests

•Troubleshooting Using Snoop

•Query Verification Tool and Translation Verification Tool

•Network Loopback Test for Network-based Call Signaling/Media Gateway Control Protocol Endpoints

•Session Initiation Protocol Subscriber Registration Status Check

•System Health Report

•Fast Audit and Sync Tool

•ISDN Network Loopback Test

•Enhanced Traffic Measurement

•PSTN Trunk Testing

Caution The use of the UNIX ifconfig down command on any signaling interface to test or troubleshoot network or interface failures of the Cisco BTS 10200 Softswitch Signaling Interface may lead to undesirable consequences or conditions.

Media Gateway Tests

This section describes the tests that can be performed on media gateways. A gateway must be in the MAINT state.

Step 1 Force the media gateway into MAINT state:

control mgw id=c2421.65; mode=forced; target-state=maint;

Reply Example:
Reply : Success: CLI change successful
MGW ID -> c2421.65
INITIAL STATE -> ADMIN_INS
REQUEST STATE -> ADMIN_MAINT
RESULT STATE -> ADMIN_MAINT
FAIL REASON -> ADM found no failure
REASON -> ADM executed successful
RESULT -> ADM configure result in success
Step 2 Display the Test Menu.

diag mgw

Reply Example:
Reply: Diagnostic MGW Menu.
===
(1) MGW Network Connectivity Test
(2) MGW MGCP Connectivity Test
(3) ALL 
Note Test #1 tests if there is a path to the device (ping).
Test #2 tests if Media Gateway Control Protocol (MGCP) has access to the device.
Test #3 performs tests 1 and 2.

Step 3 To perform a specific test, use the following examples as a guide.

diag mgw id=ubr-03; test=1;

Reply Example:
MEDIA GATEWAY LINE DIAGNOSTIC TEST EXECUTED -> diag mgw
ID -> ubr-03
TEST-TYPE -> ADM-MGW-NETW-CONNECTIVITY-TEST
TEST-DURATION -> 0
RESULT -> TEST-SUCCESS
REASON -> PASSED
Reply: Diagnostic command executed.
diag mgw id=ubr-03; test=2;

Reply Example:
MEDIA GATEWAY LINE DIAGNOSTIC TEST EXECUTED -> diag mgw
ID -> ubr-03
TEST-TYPE -> ADM-MGW-MGCP-CONNECTIVITY-TEST
TEST-DURATION -> 0
RESULT -> TEST-SUCCESS
REASON -> PASSED
Reply: Diagnostic command executed. 
diag mgw id=ubr-03; test=3;

Reply Example:
MEDIA GATEWAY LINE DIAGNOSTIC TEST EXECUTED -> diag mgw
ID -> ubr-03
TEST-TYPE -> ADM-MGW-NETW-CONNECTIVITY-TEST
TEST-DURATION -> 11
RESULT -> TEST-SUCCESS
REASON -> PASSED
MEDIA GATEWAY LINE DIAGNOSTIC TEST EXECUTED -> diag mgw
ID -> ubr-03
TEST-TYPE -> ADM-MGW-MGCP-CONNECTIVITY-TEST
TEST-DURATION -> 0
RESULT -> TEST-SUCCESS
REASON -> PASSED
Reply: Diagnostic command executed.
Step 4 Force the media gateway into INS state:

control mgw id=c2421.65; mode=forced; target-state=ins;

Reply Example:
Reply : Success: CLI change successful
MGW ID -> c2421.65
INITIAL STATE -> ADMIN_MAINT
REQUEST STATE -> ADMIN_INS
RESULT STATE -> ADMIN_INS
FAIL REASON -> ADM found no failure
REASON -> ADM executed successful
RESULT -> ADM configure result in success
Subscriber Termination Tests

This section describes the tests that can be performed on subscriber terminations. All terminations must be in the MAINT state.

Step 1 Force the subscriber termination into MAINT state:

control subscriber-termination id=sub2-ctx2; mode=forced; target-state=maint;

Step 2 Display the Test Menu.

diag subscriber-termination;

Reply Example:
Reply: Diagnostic Subscriber Menu.
===
(1) Subscriber MGCP Connectivity Test
(2) Subscriber Termination Connection Test
(3) Subscriber Termination Ring Test
(4) ALL
Note Test #1 tests if MGCP has access to the termination.
Test #2 tests if there is a path to the device (ping).
Test #3 tests if the subscriber can be rung. The Ring parameter must be specified in seconds for this test. The default is 5 seconds.
Test #4 performs tests 1 through 3.

Step 3 To perform a specific test, use the following examples as a guide.

diag subscriber-termination id=sub2-ctx2; test=1;

Reply Example:
SUBSCRIBER LINE DIAGNOSTIC TEST EXECUTED -> diag subscriber-termination
ID -> sub2-ctx2
TEST-TYPE -> ADM-MGW-MGCP-CONNECTIVITY-TEST
TEST-DURATION -> 10
RESULT -> TEST-SUCCESS
REASON -> PASSED: Reason: AUEP-NACK received with RespCode = 510
Reply: Diagnostic command executed.
diag subscriber-termination id=sub-ubr3-1@cisco.com; test=2;

Reply Example:
SUBSCRIBER LINE DIAGNOSTIC TEST EXECUTED -> diag subscriber-termination
ID -> sub-ubr3-1@Cisco.com
TEST-TYPE -> ADM-TERM-CONNECTION-TEST
TEST-DURATION -> 55
RESULT -> TEST-SUCCESS
REASON -> PASS successfully.
Reply: Diagnostic command executed.
diag subscriber-termination id=sub-ubr3-1@cisco.com; test=3; ring-duration=10;

Reply Example:
SUBSCRIBER LINE DIAGNOSTIC TEST EXECUTED -> diag subscriber-termination
ID -> sub-ubr3-1@Cisco.com
TEST-TYPE -> ADM-TERM-RING-TEST
TEST-DURATION -> 9989
RESULT -> TEST-SUCCESS
REASON -> PASSED
Reply: Diagnostic command executed. 
Note Ring-duration values are 0-999 (Default = 5). Maximum ring time is 30 seconds regardless of whether the duration is set higher than or equal to 31.

Step 4 Force the subscriber termination into INS state:

control subscriber-termination id=sub2-ctx2; mode=forced; target-state=ins;

Signaling System 7 Trunk Termination Tests

This section describes the tests that can be performed on Signaling System 7 (SS7) trunk terminations. All terminations must be in the MAINT state for testing.

Step 1 Force the SS7 trunk termination into MAINT state:

control ss7-trunk-termination tgn-id=103; mode=forced; target-state=maint;

Note Set customer-originated trace (COT), circuit verification message (CVM), and circuit query message (CQM) on the terminating gateway or switch to perform these tests. Otherwise, the test or tests will fail.

Step 2 Display the Test Menu.

diag ss7-trunk-termination

Reply Example:
Reply: Diagnostic SS7 Trunk Group Menu.
===
Test=1: SS7 MGCP Connectivity
Test=2: SS7 Termination Connection Test
Test=3: COT
Test=4: CQM
Test=5: CVT
Test=6: CIC
Test=7: All
Note Test #1 tests if MGCP has access to the SS7 trunk termination.
Test #2 tests if there is a path to the device (ping).
Test #3 tests the integrity of the SS7 Bearer Path.
Test #4 queries the SS7 circuit (or group of circuits) status. A range of CICs can be specified (to a maximum of 24). Both remote and local trunk states are displayed in the results.
Test #5 tests to ensure that each end of the circuit has sufficient and consistent information for using the circuit in call connections. Common language location identifier (CLLI) names are included.
Test #6 tests to ensure the CIC connections.
Test #7 performs tests 1 through 6.

Step 3 To perform a specific test, use the following examples as a guide:

diag ss7-trunk-termination tgn-id=103; cic=13; test=1;

Reply Example:
TRUNK DIAGNOSTIC TEST EXECUTED -> diag trunk
TG-NUM -> 103
CIC -> 13
TEST-TYPE -> ADM-MGW-MGCP-CONNECTIVITY-TEST
TEST-DURATION -> 0
RESULT -> TEST-SUCCESS
REASON -> PASSED: Reason: AUEP-NACK received with RespCode = 510
Reply: Diagnostic command executed.
diag ss7-trunk-termination tgn-id=103; cic=13; test=2;

Reply Example:
TRUNK DIAGNOSTIC TEST EXECUTED -> diag trunk
TG-NUM -> 103
CIC -> 13
TEST-TYPE -> ADM-TERM-CONNECTION-TEST
TEST-DURATION -> 33
RESULT -> TEST-SUCCESS
REASON -> PASS successfully.
Reply: Diagnostic command executed.
diag ss7-trunk-termination tgn-id=103; cic=14; test=3;

Reply Example:
TRUNK DIAGNOSTIC TEST EXECUTED -> diag trunk
TG-NUM -> 103
CIC -> 14
TEST-TYPE -> ADM-SS7-COT-TEST
TEST-DURATION -> 0
RESULT -> TEST-FAILURE
REASON -> ADM-MAINT-STATE-REQUIRED
Reply: Diagnostic command executed.
diag ss7-trunk-termination tgn-id=2;cic=1-24;test=4

Reply Example:
Reply : Success: 
TGN ID -> 2
START CIC -> 1
END CIC -> 24
TEST TYPE -> ADM running SS7 circuit query message test
TEST DURATION -> 0
RESULT -> ADM ran test successfully
REASON -> CQM test pass
CIC COUNT -> 24
CIC STATES -> 
Remote State
Local State
CIC 1 -> CS_IDLE
ACTV
IDLE
CIC 2 -> CS_IDLE
ACTV
IDLE
CIC 3 -> CS_IDLE
ACTV
IDLE
CIC 4 -> CS_IDLE
ACTV
IDLE
CIC 5 -> CS_IDLE
ACTV
IDLE
CIC 6 -> CS_IDLE
ACTV
IDLE
CIC 7 -> CS_IDLE
ACTV
IDLE
CIC 8 -> CS_IDLE
ACTV
IDLE
CIC 9 -> CS_IDLE
ACTV
IDLE
CIC 10 -> CS_IDLE
ACTV
IDLE
CIC 11 -> CS_IDLE
ACTV
IDLE
CIC 12 -> CS_IDLE
ACTV
IDLE
CIC 13 -> CS_IDLE
ACTV
IDLE
CIC 14 -> CS_IDLE
ACTV
IDLE
CIC 15 -> CS_IDLE
ACTV
IDLE
CIC 16 -> CS_IDLE
ACTV
IDLE
CIC 17 -> CS_IDLE
ACTV
IDLE
CIC 18 -> CS_IDLE
ACTV
IDLE
CIC 19 -> CS_IDLE
ACTV
IDLE
CIC 20 -> CS_IDLE
ACTV
IDLE
CIC 21 -> CS_IDLE
ACTV
IDLE
CIC 22 -> CS_IDLE
ACTV
IDLE
CIC 23 -> CS_IDLE
ACTV
IDLE
CIC 24 -> CS_IDLE 
ACTV 
IDLE
Note Table 15-1 lists the responses that can be returned for the CQM test:

diag ss7-trunk-termination tgn-id=2;cic=1;test=5

Reply Example:
Reply : Success: 
TGN ID -> 2
START CIC -> 1
END CIC -> 1
TEST TYPE -> ADM running SS7 circuit validation test 
TEST DURATION -> 0
RESULT -> ADM ran test successfully
REASON -> CVT test pass
CLLI -> DALLTXRCDN5
Step 4 Force the SS7 trunk termination into INS state:

control ss7-trunk-termination tgn-id=103; mode=forced; target-state=ins;

Table 15-1 CQM Responses

Response

Description

CS_TRANSIENT

Transient

CS_UNEQUIPPED

Unequipped

CS_IC_BUSY

Incoming Busy

CS_IC_BUSY_LOCBLOC

Incoming Busy and Locally Maintenance Blocked

CS_IC_BUSY_REMBLOC

Incoming Busy and Remotely Maintenance Blocked

CS_IC_BUSY_BOTH_BLOC

Incoming Busy and Remotely and Locally Maintenance Blocked

CS_OG_BUSY

Outgoing Busy

CS_OG_BUSY_LOCBLOC

Outgoing Busy and Locally Maintenance Blocked

CS_OG_BUSY_REMBLOC

Outgoing Busy and Remotely Maintenance Blocked

CS_OG_BUSY_BOTH_BLOC

Outgoing Busy and Remotely and Locally Maintenance Blocked

CS_IDLE

Idle

CS_IDLE_LOCBLOC

Idle and Locally Maintenance Blocked

CS_IDLE_REMBLOC

Idle and remotely maintenance blocked

CS_IDLE_BOTH_BLOC

Idle and Remotely and Locally Maintenance Blocked

CS_HW_LOCBLOC

Locally Hardware Blocked

CS_HW_LOCBLOC_LOCBLOC

Locally Hardware and Locally Maintenance Blocked

CS_HW_LOCBLOC_REMBLOC

Locally Hardware and Remotely Maintenance Blocked

CS_HW_LOCBLOC_BOTHBLOC

Locally Hardware and Remotely and Locally Maintenance Blocked

CS_HW_REMBLOC

Remotely Hardware Blocked

CS_HW_REMBLOC_LOCBLOC

Remotely Hardware and Locally Maintenance Blocked

CS_HW_REMBLOC_REMBLOC

Remotely Hardware and Remotely Maintenance Blocked

CS_HW_REMBLOC_BOTHBLOC

Remotely Hardware and Remotely and Locally Maintenance Blocked

CS_HW_BOTHBLOC

Remotely and Locally Hardware Blocked

CS_HW_BOTHBLOC_LOCBLOC

Remotely and Locally Hardware and Locally Maintenance Blocked

CS_HW_BOTHBLOC_REMBLOC

Remotely and Locally Hardware and Remotely Maintenance Blocked

CS_HW_BOTHBLOC_BOTHBLOC

Remotely and Locally Hardware and Remotely and Locally Maintenance Blocked

Integrated Services Digital Network Trunk Termination Tests

This section describes the tests that can be performed on Integrated Services Digital Network (ISDN) trunk terminations. All terminations must be in the MAINT state for testing.

Step 1 Force the ISDN trunk termination into MAINT state:

control isdn-trunk-termination tgn-id=17; mode=forced; target-state=maint;

Step 2 Display the Test Menu.

diag isdn-trunk-termination

Reply Example:
Reply: Diagnostic ISDN Trunk Group Menu.
=== 
(1) ISDN MGCP Connectivity Test
(2) ISDN Termination Connection Test
(3) ALL
Note Test #1 tests if MGCP has access to the ISDN termination.
Test #2 tests if there is a path to the device (ping).
Test #3 performs tests 1 and 2.

Step 3 To perform a specific test, use the following examples as a guide.

diag isdn-trunk-termination test=1; tgn-id=17; cic=1;

Reply Example:
TRUNK DIAGNOSTIC TEST EXECUTED -> diag trunk
TG-NUM -> 17
CIC -> 1
TEST-TYPE -> ADM-MGW-MGCP-CONNECTIVITY-TEST
TEST-DURATION -> 0
RESULT -> TEST-SUCCESS
REASON -> PASSED: Reason: AUEP-NACK received with RespCode = 510
Reply: Diagnostic command executed.
diag isdn-trunk-termination test=2; tgn-id=17; cic=1;

Reply Example:
TRUNK DIAGNOSTIC TEST EXECUTED -> diag trunk
TG-NUM -> 17
CIC -> 1
TEST-TYPE -> ADM-TERM-CONNECTION-TEST
TEST-DURATION -> 0
RESULT -> TEST-SUCCESS
REASON -> PASSED: Reason: AUEP-NACK received with RespCode = 510
Reply: Diagnostic command executed.
Step 4 Force the ISDN trunk termination into INS state:

control isdn-trunk-termination tgn-id=17; mode=forced; target-state=ins;

Channel-Associated Signaling Trunk Termination Tests

This section describes the tests that can be performed on channel-associated signaling (CAS) trunk terminations. All terminations must be in the MAINT state for testing.

Step 1 Force the CAS trunk termination into MAINT state:

control cas-trunk-termination tgn-id=64; mode=forced; target-state=maint;

Step 2 Display the Test Menu.

diag cas-trunk-termination

Reply Example:
Reply: Diagnostic CAS Trunk Group Menu.
===
(1) CAS MGCP Connectivity Test
(2) CAS Termination Connection Test
(3) ALL
Note Test #1 tests if MGCP has access to the CAS termination.
Test #2 tests if there is a path to the device (ping).
Test #3 performs tests 1 and 2.

Step 3 To perform a specific test, use the following examples as a guide:

diag cas-trunk-termination tgn-id=64;cic=1;test=1;

Reply Example:
TRUNK DIAGNOSTIC TEST EXECUTED -> diag trunk
TG-NUM -> 64
CIC -> 1
TEST-TYPE -> ADM-MGW-MGCP-CONNECTIVITY-TEST
TEST-DURATION -> 0
RESULT -> TEST-SUCCESS
REASON -> PASSED: Reason: AUEP-NACK received with RespCode = 510
Reply: Diagnostic command executed.
diag cas-trunk-termination tgn-id=64;cic=1;test=2;

Reply Example:
TRUNK DIAGNOSTIC TEST EXECUTED -> diag trunk
TG-NUM -> 64
CIC -> 1
TEST-TYPE -> ADM-TERM-CONNECTION-TEST
TEST-DURATION -> 32
RESULT -> TEST-SUCCESS
REASON -> PASS successfully.
Reply: Diagnostic command executed.
diag cas-trunk-termination tgn-id=64;cic=1;test=3;

Reply Example:
TRUNK DIAGNOSTIC TEST EXECUTED -> diag trunk
TG-NUM -> 64
CIC -> 1
TEST-TYPE -> ADM-MGW-MGCP-CONNECTIVITY-TEST
TEST-DURATION -> 11
RESULT -> TEST-SUCCESS
REASON -> PASSED: Reason: AUEP-NACK received with RespCode = 510
TRUNK DIAGNOSTIC TEST EXECUTED -> diag trunk
TG-NUM -> 64
CIC -> 1
TEST-TYPE -> ADM-TERM-CONNECTION-TEST
TEST-DURATION -> 32
RESULT -> TEST-SUCCESS
REASON -> PASS successfully.
Reply: Diagnostic command executed.
Step 4 Force the CAS trunk termination into INS state:

control cas-trunk-termination tgn-id=64; mode=forced; target-state=ins;

Announcement Trunk Termination Tests

This section describes the tests that can be performed on Announcement trunk terminations. All terminations must be in the MAINT state for testing.

Step 1 Force the Announcement trunk termination into MAINT state:

control annc-trunk-termination tgn-id=13; mode=forced; target-state=maint;

Step 2 Display the Test Menu.

diag annc-trunk-termination:

Reply Example:
Reply: Diagnostic ANC Trunk Group Menu.
===
(1) ANC MGCP Connectivity Test
(2) ANC Termination Connection Test
(3) ALL
Note Test #1 tests if MGCP has access to the announcements module (ANC) termination.
Test #2, tests if there is a path to the device (ping).
Test #3 performs tests 1 and 2.

Step 3 To perform a specific test, use the following examples as a guide.

diag annc-trunk-termination;test=1;tgn-id=13;cic=1

Reply Example:
TRUNK DIAGNOSTIC TEST EXECUTED -> diag trunk
TG-NUM -> 13
CIC -> 1
TEST-TYPE -> ADM-MGW-MGCP-CONNECTIVITY-TEST
TEST-DURATION -> 0
RESULT -> TEST-SUCCESS
REASON -> PASSED: Reason: AUEP-NACK received with RespCode = 510
Reply: Diagnostic command executed.
diag annc-trunk-termination;test=2;tgn-id=13;cic=1

Reply Example:
TRUNK DIAGNOSTIC TEST EXECUTED -> diag trunk
TG-NUM -> 13
CIC -> 1
TEST-TYPE -> ADM-TERM-CONNECTION-TEST
TEST-DURATION -> 33
RESULT -> TEST-SUCCESS
REASON -> PASS successfully.
Reply: Diagnostic command executed.
diag annc-trunk-termination;test=3;tgn-id=13;cic=1

Reply Example:
TRUNK DIAGNOSTIC TEST EXECUTED -> diag trunk
TG-NUM -> 13
CIC -> 1
TEST-TYPE -> ADM-MGW-MGCP-CONNECTIVITY-TEST
TEST-DURATION -> 11
RESULT -> TEST-SUCCESS
REASON -> PASSED: Reason: AUEP-NACK received with RespCode = 510
TRUNK DIAGNOSTIC TEST EXECUTED -> diag trunk
TG-NUM -> 13
CIC -> 1
TEST-TYPE -> ADM-TERM-CONNECTION-TEST
TEST-DURATION -> 33
RESULT -> TEST-SUCCESS
REASON -> PASS successfully.
Reply: Diagnostic command executed.
Step 4 Force the Announcement trunk termination into INS state:

control annc-trunk-termination tgn-id=13; mode=forced; target-state=ins;

Troubleshooting Using Snoop

Caution Snoop should NOT be used on the Cisco BTS 10200 Softswitch call agent itself in a Production Network. It can cause performance degradation.

Snoop can be used on the Cisco BTS 10200 Softswitch call agent during test and turn-up phase during very low call volume periods. Snoop can always be used on a separate UNIX machine connected to a switch that has been properly setup for port span/mirroring. You must be logged in as "root" user to run snoop. Snoop can be used to decode text protocols or can be saved to a file and opened with Ethereal when binary protocols are used. Ethereal is open source software and can be downloaded from http://www.ethereal.com. To use Snoop to diagnose network problems, take the following steps:

Step 1 Find all routes to the destination in question. Most likely there will be multiple routes therefore multiple interfaces will need to be snooped. (Skip this step if you are snooping from a separate Unix machine - you will just snoop the span destination interface in that case.) In this example, destination Internet Protocol (IP) 10.0.0.1 is in question. The fully qualified domain name (FQDN) can be used if it is resolvable by domain name system (DNS). Issue the command several times as there may be redundant routes.
mssol-ca0-a# route get 10.0.0.1
   route to: 10.0.0.1
destination: default
       mask: default
    gateway: 10.0.0.253
  interface: qfe4
      flags: <UP,GATEWAY,DONE>
 recvpipe  sendpipe  ssthresh    rtt,ms rttvar,ms  hopcount      mtu     expire
       0         0         0         0         0         0      1500         0 
mssol-ca0-a# route get 10.0.0.1
   route to: 10.0.0.1
destination: default
       mask: default
    gateway: 10.0.0.253
  interface: qfe4
      flags: <UP,GATEWAY,DONE>
 recvpipe  sendpipe  ssthresh    rtt,ms rttvar,ms  hopcount      mtu     expire
       0         0         0         0         0         0      1500         0 
mssol-ca0-a# route get 10.0.0.1
   route to: 10.0.0.1
destination: default
       mask: default
    gateway: 10.20.0.253
  interface: qfe0
      flags: <UP,GATEWAY,DONE>
 recvpipe  sendpipe  ssthresh    rtt,ms rttvar,ms  hopcount      mtu     expire
       0         0         0         0         0         0      1500         0 
mssol-ca0-a# route get 10.0.0.1
   route to: 10.0.0.1
destination: default
       mask: default
    gateway: 10.20.0.253
  interface: qfe0
      flags: <UP,GATEWAY,DONE>
 recvpipe  sendpipe  ssthresh    rtt,ms rttvar,ms  hopcount      mtu     expire
       0         0         0         0         0         0      1500         0 
Note Each interface reported above must be snooped to catch all packets across redundant routes. In the given example interface qfe0 as well as qfe4 must be snooped.

Step 2 Issue the snoop command. It may differ in syntax depending on protocol(s) that are being analyzed.

Session Initiation Protocol (SIP) example:

10.0.0.1 is a SIP Phone. The goal is to monitor the SIP traffic between the Cisco BTS 10200 Softswitch and the SIP phone.
# snoop -d qfe0 -x 42 host 10.0.0.1 and port 5060 and udp &
# snoop -d qfe4 -x 42 host 10.0.0.1 and port 5060 and udp &
MGCP/network-based call signaling (NCS) example:

10.0.0.1 is an integrated access device (IAD) running MGCP. The goal is to monitor MGCP traffic between the Cisco BTS 10200 Softswitch and the IAD.
# snoop -d qfe0 -x 42 host 10.0.0.1 and port 2427 and udp &
# snoop -d qfe4 -x 42 host 10.0.0.1 and port 2427 and udp &
Stream Control Transmission Protocol (SCTP)/MTP3 user adaptation (M3UA)/ISDN user part (ISUP) example:

Since these protocols are not TEXT based as the ones mentioned above, use the -o option with snoop to capture packets in an Ethereal readable format. Ethereal can decode SCTP/M3UA/ISUP or SCTP/SCCP user adapter (SUA)/Transaction Capabilities Application Part (TCAP). 10.0.0.1 is a Signaling Gateway acting as an M3UA peer with the Cisco BTS 10200 Softswitch.
# snoop -d qfe0 -o sctp.cap host 10.0.0.1  (this will capture all traffic)
Step 3 Use Control-C to stop the packet capture. Open the file in Ethereal and inspect. To capture sctp packets that contain M3UA information:

a. First, find the port M3UA will use to communicate with the signaling gateway (SG).
CLI>show sctp-assoc platform-id=CA146
ID=sgp1-itpa
SGP_ID=sgp1
SCTP_ASSOC_PROFILE_ID=sctp-prof1
REMOTE_PORT=2905  <-------------------this port
REMOTE_TSAP_ADDR1=10.0.0.1
PLATFORM_ID=CA146
DSCP=NONE
IP_TOS_PRECEDENCE=CRITICAL
LOCAL_RCVWIN=3000
MAX_INIT_RETRANS=3
MAX_INIT_RTO=500
STATUS=INS
ULP=XUA
# snoop -d qfe0 -o m3ua.cap host 10.0.0.1 and port 2905
b. Use Control-C to stop the packet capture. Open the file in Ethereal and inspect.

SCTP/SUA/TCAP example 1:

10.0.0.1 is a Signaling Gateway acting as an SUA peer with the Cisco BTS 10200 Softswitch. The goal is to capture all 800/local number portability (LNP) queries.

a. Follow the same syntax as for the M3UA case, except find which port SUA communicates with the SG for Advanced Intelligent Network (AIN) features:
CLI>show sctp-assoc platform-id=FSAIN205
ID=sctp-ain-itpa
SGP_ID=sgp1
SCTP_ASSOC_PROFILE_ID=sctp-prof1
REMOTE_PORT=2907  <-------------------this port
REMOTE_TSAP_ADDR1=10.0.0.1
PLATFORM_ID=FSAIN205
DSCP=NONE
IP_TOS_PRECEDENCE=CRITICAL
LOCAL_RCVWIN=3000
MAX_INIT_RETRANS=3
MAX_INIT_RTO=500
STATUS=INS
ULP=XUA
# snoop -d qfe0 -o suaain.cap host 10.0.0.1 and port 2907
b. Use Control-C to stop the packet capture. Open the file in Ethereal and inspect.

SCTP/SUA/TCAP example 2:

10.0.0.1 is a Signaling Gateway acting as an SUA peer with the Cisco BTS 10200 Softswitch. The goal is to capture all offnet automatic callback and automatic rollback (ACAR) queries.

a. Follow the same syntax as for the M3UA case, except find the port SUA communicates with the SG for plain old telephone service (POTS) features:
CLI>show sctp-assoc platform-id=FSPTC235
ID=sctp-ptc-itpa
SGP_ID=sgp2
SCTP_ASSOC_PROFILE_ID=sctp-prof1
REMOTE_PORT=2906  <------------------this port
REMOTE_TSAP_ADDR1=10.0.0.1
PLATFORM_ID=FSPTC235
DSCP=NONE
IP_TOS_PRECEDENCE=FLASH
LOCAL_RCVWIN=64000
MAX_INIT_RETRANS=5
MAX_INIT_RTO=1000
STATUS=INS
ULP=XUA
# snoop -d qfe0 -o suapots.cap host 10.0.0.1 and port 2906
b. Use Control-C to stop the packet capture. Open the file in Ethereal and inspect.

H.323 Protocol (H323) example:

10.0.0.1 is an H323 gateway. 10.0.0.129 is an H323 gatekeeper. Our goal is to monitor both Registration, Admissions, and Status (RAS) and H.225 messaging.

a. First, find the RAS port number and the H.225 port number.
CLI>show h323-gw
ID=ccm3_gw1
STATUS=INS
OPER_STATUS=NF
GW_H225_PORT=1720  <----------- this port
TGN_ID=4441
SECURITY=N
H245_TUNNELING=DEFAULT
TCP_MAX_LIMIT=5
TCP_MAX_AGE=30
MAX_VOIP_CALLS=65535
HIGH_WATER_MARK=0
LOW_WATER_MARK=0
IRR_BANDWIDTH_SUPP=N
IPTOS_SIG_LOWDELAY=Y
IPTOS_SIG_THROUGHPUT=N
IPTOS_SIG_RELIABILITY=N
IPTOS_SIG_PRECEDENCE=FLASH
BRQ_SUPP=Y
ANNEXE_RETRANSMIT_TIMER=500
ANNEXE_RETRANSMIT_MULTIPLIER=2
ANNEXE_RETRANSMIT_ATTEMPTS=8
CALL_START_MODE=FAST_START
ANNEXE_SUPP=N
ANNEXR_SUPP=N
STATUS_ENQ_TIMER=4
CODEC_NEG_TIMER=200
CODEC_NEG_ATTEMPTS=4
SOURCE_BASED_ROUTING=NONE 
CLI>show h323-gw2gk
H323_GW_ID=ccm3_gw1
GK_ID=Metro-GK
PRIORITY=0
GK_IP_ADDR=10.0.0.129
GK_RAS_PORT=1719  <------------ this port
MULTICAST=N
TIME_TO_LIVE=60
# snoop -d qfe0 -o h323.cap host 10.0.0.1 and port 1720 or host 10.0.0.129 and port 
1719
b. Use Control-C to stop the packet capture. Open the file in Ethereal and inspect.

COPs example:

10.0.0.1 is a cable modem termination system (CMTS) and is configured as an aggregation identification (AGGR-ID) in the Cisco BTS 10200 Softswitch. The goal is to monitor all Common Open Policy Service Protocol (COPS) messaging to and from the CMTS.

a. Issue the following command:
# snoop -d qfe0 -o cops.cap host 10.0.0.1 and port 2126 and tcp
b. Use Control-C to stop the packet capture. Open the file in Ethereal and inspect.

Step 4 Packets can be redirected to a file (not readable by Ethereal) at follows:
# snoop -d qfe0 -x 42 host 10.0.0.1 and port 2427 and udp > mycapt.cap
Step 5 Stop the snoop processes.
# pkill snoop
# pgrep snoop (should not report any process ids)
Query Verification Tool and Translation Verification Tool

This section describes the Query Verification Tool (QVT) and the Translation Verification Tool (TVT) and is organized into the following sub-sections:

•Tool Requirements

•Query Verification Tool

•Translation Verification Tool

•Using Query Verification Tool and Translation Verification Tool Together

Tool Requirements

The following requirements are supported in the QVT and TVT:

•TVT—Provide a tool to find, diagnose, and trace call flow path decisions.

•Query Local Routing Number (QLRN) Tool—Provide the ability to enter a ten digit directory number and launch a query to the service control point (SCP) as though it was a called number from the signal switching point (SSP).

•Query Tool E800VER Command—Send a database query to the SCP as if it was an 800 called number from the SSP without initiating a call.

•Query Tool CNAMDVER and TESTSS CNAMD Commands—Provide the ability to query the SCP database for the calling name delivery (CNAM) display and privacy status associated with the name without initiating a call.

Query Verification Tool

This section describes the QVT and includes the following sections:

•Overview

•Command Format

•Response Format

•Query Errors

•Query Verification Tool Measurements

Overview

The QVT enables a user to generate TCAP queries to external databases through the command line interface (CLI) interface. The types of queries supported are:

•Line information database (LIDB)—Generated by the POTS Feature Server

•Toll-Free—Generated by the AIN Feature Server

•LNP—Generated by the AIN Feature Server

Command Format

The QVT command uses the following format:
query <lidb|toll-free|lnp> parameter=value;
Examples

query lidb calling-dn=8002550002; opc-id=opc;

Syntax Description

* OPC-Id

Origination Point Code ID

* Calling-DN

The caller's directory number.

Table-Info

Specifies whether or not you want to see the tables accessed when processing the query. Y/N; default=N

Examples

query toll-free

Syntax Description

* OPC-Id

Origination Point Code ID

* Calling-DN

The caller's directory number.

* User-Type

Specifies whether the User-ID is a Trunk-Group-ID or the Calling-DN. Mandatory for AIN0.1 queries; not used in intelligent network (IN)/1 queries.

* User-ID

Specifies either the Trunk-Group-ID or Calling-DN, depending upon what you have specified in User-Type. Mandatory for AIN0.1 queries; not used in IN/1 queries.

* Called-DN

* LATA

Local access and transport area. VARCHAR (5)

Originating Line Information (OLI)

Optional parameter used if the message-type is IN/1. 0 (default) = POTS.

Bearer-Capability

Valid values are: Speech, f31KhzAudio, b56kbps, or b64kbps.

Trigger-Criteria

Valid values are: 3, 6, 7, 8, 9, or 10.

Table-Info

Specifies whether or not you want to see the tables accessed when processing the query. Y/N; default=N

Examples

query lnp;

Syntax Description

* OPC-Id

Origination Point Code ID

* Calling-DN

The caller's directory number. VARCHAR(10): 10 digits in the format npaxxxxxxx.

* User-Type

Specifies whether the User-ID is a Trunk-Group-ID or the Calling-DN.

* User-ID

Specifies either the Trunk-Group-ID or Calling-DN, depending upon what you have specified in User-Type. Values are POTS DN NPA-NXX-XXXX (Calling-DN) or numeric number nomenclature (NNN) (Trunk-Group-ID).

* Called-DN

* LATA

Local access and transport area. VARCHAR (5)

Bearer-Capability

Valid values are: Speech, f31KhzAudio, b56kbps, or b64kbps.

Trigger-Criteria

Table-Info

Specifies whether or not you want to see the tables accessed when processing the query. Y/N; default=N

Response Format

The system response to a query is in the following format:
Reply: <success|failure>; parameter=value;
Common Response Parameters

Successful response parameters include the following:

•OPC—Originating Point Code

•