Troubleshooting guide

6-133
Cisco PGW 2200 Softswitch Release 9.8 Operations, Maintenance, and Troubleshooting Guide
OL-0800-14
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform
Resolving Bearer Channel Connection Problems
• COT—Continuity check requirements indicator. The values in these fields should be the same in the
LOC and REM lines. The following values are valid for this field:
– UNK—Unknown continuity check requirements
– NONE—No continuity check requirements
– STAT—Statistical continuity check requirements
– PERC—Per call continuity check requirements
• TRK—Trunk number. This field is always displayed in the LOC line. It is only displayed in the REM
line when the circuit identification names for the Cisco PGW 2200 Softswitch and the far-end
exchange do not match.
• A_CLLI—Common language location identifier (CLLI) code for either the far-end exchange or the
Cisco PGW 2200 Softswitch. The CLLIs for each are sorted alphabetically, and the A_CLLI field
is populated with the CLLI that is found to be first. This field is always displayed in the LOC line.
It is displayed in the REM line only when the CLLIs for the Cisco PGW 2200 Softswitch and the
far-end exchange do not match.
• Z_CLLI—CLLI code for either the far-end exchange or the Cisco PGW 2200 Softswitch. The CLLIs
for each are sorted alphabetically, and the Z_CLLI field is populated with the CLLI that is found to
be second. This field is always displayed in the LOC line. It is displayed in the REM line only when
the CLLIs for the Cisco PGW 2200 Softswitch and the far-end exchange do not match.
If the circuit validation test passes, proceed to Step 14.
If the circuit validation test fails, proceed to Step 2.
Step 2 Determine which settings are not correct by comparing the values that are displayed in the LOC field
(from the Cisco PGW 2200 Softswitch) to values displayed in the REM field (from the associated far-end
exchange), based on the field descriptions (previously described).
Step 3 Consult your provisioning records to determine whether the settings on the Cisco PGW 2200 Softswitch
or the associated far-end exchange need to be modified to resolve the error.
To modify the settings on the Cisco PGW 2200 Softswitch to resolve the error, proceed to Step 4.
If the settings on the associated far-end exchange need to be modified to resolve the error, contact the
provider that operates the switch and work with them to resolve the configuration error.
Step 4 Identify the signaling service that is associated with the affected DPC by issuing the
prov-rtrv:ss7path:"all" command:
The system returns a message like the following:
mgc-01 - Media Gateway Controller 2000-09-26 15:55:17
M RTRV
"session=active:ss7path"
/*
NAME DPC MDO CUSTGRPIDCUSTGRPTBLSIDE
---- --- --- -----------------------
ss7am401aam401a-pcANSISS7_STANDARD00000101network
ss7am702bam702b-pcANSISS7_STANDARD00000101network
ss7inet1inetsp1-pcANSISS7_STANDARD00000101network
ss7am408aam408a-pcANSISS7_STANDARD00000101network
ss7am408bam408b-pcANSISS7_STANDARD00000101network
ss7inet2inetsp2-pcANSISS7_STANDARD00000101network
ss7dmsdms100-pcANSISS7_STANDARD00000101network
ss7am401bam401b-pcANSISS7_STANDARD00000101network
ss7am608bam608b-pcANSISS7_STANDARD00000101network
ss7sc2200sc2200-pcANSISS7_STANDARD00000101network