Troubleshooting guide

6-17
Cisco PGW 2200 Softswitch Release 9.8 Operations, Maintenance, and Troubleshooting Guide
OL-0800-14
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform
Troubleshooting Using Cisco PGW 2200 Softswitch Alarms
Step 2 Verify that the associated cause table contains all of the existing call context cause values, by using the
numan-rtrv MML command. See Cisco PGW 2200 Softswitch Release 9.8 Dial Plan Guide for more
information.
If the cause table is incomplete, modify its value using the numan-ed MML command. See Cisco PGW
2200 Softswitch Release 9.8 Dial Plan Guide for more information. Save and activate your dial plan
changes as described in the “Saving and Activating your Provisioning Changes” section on page 3-65.
Otherwise, proceed to Step 3.
Step 3 Verify that the dial plan file was loaded correctly, by using the procedure that is described in “Verifying
Proper Loading of a Dial Plan” section on page 6-121.
ANAL:Cause_GetFail_DigModTbl
This alarm occurs during cause analysis when a B-number modification result is encountered and the
digit modification string is unreadable. This problem can occur if the digit modification table is
corrupted or if an incorrect digit modification index was stored in the B-number modification results
data.
Corrective Action
Step 1 To collect system data, see the method that is described in the “Collecting System Data for Cisco TAC”
section on page 6-93.
Step 2 Verify that the associated B-number digit modification table is correct, by using the numan-rtrv MML
command. See Cisco PGW 2200 Softswitch Release 9.8 Dial Plan Guide for more information.
If the information in the B-number digit modification table is incorrect, modify its value using the
numan-ed MML command. See Cisco PGW 2200 Softswitch Release 9.8 Dial Plan Guide for more
information. Save and activate your dial plan changes as described in the “Saving and Activating your
Provisioning Changes” section on page 3-65. Otherwise, proceed to Step 3.
Step 3 Verify that the dial plan file was loaded correctly, as is described in the “Verifying Proper Loading of a
Dial Plan” section on page 6-121.
ANAL: Cause_GetFail_InvldRsltType
This alarm occurs during cause analysis when a result is encountered that is not supported in cause
analysis. This problem is due to corruption of the cause or location tables or the result table.
Corrective Action
To correct the problem, verify that the dial plan file was loaded correctly, by using the procedure that is
described in the “Verifying Proper Loading of a Dial Plan” section on page 6-121.
ANAL:Cause_GetFail_LocTbl
This alarm occurs during cause analysis when the location table is unreadable. This problem can occur
if the location table is corrupted, the underlying software fails, or the location table is not fully populated
with all possible references from the cause table.