Troubleshooting guide

6-23
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
Corrective Action
To correct the problem, perform the following steps:
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 Display the valid trunk group types using the prov-rtrv MML command that is described in the
“Retrieving Provisioning Data” section on page 3-69.
Step 3 Correct the invalid trunk group type in the route analysis table 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.
If the alarm clears, the procedure is complete. Otherwise, proceed to Step 4.
Step 4 Contact the Cisco TAC to analyze the problem further and to determine a solution. For more information
about contacting the Cisco TAC, see the “Obtaining Documentation and Submitting a Service Request”
section on page xviii.
ANAL: Prof_GetFail_DigModTbl
This alarm occurs during profile 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 an incorrect digit modification index is stored in the B-number modification results data.
Corrective Action
To correct the problem, verify that the dial plan file was loaded correctly, using the procedure that is
described in the “Verifying Proper Loading of a Dial Plan” section on page 6-121.
ANAL: Prof_GetFail_InvldRslt
This alarm occurs during profile analysis when the Cisco PGW 2200 Softswitch encounters a result that
is not supported in profile analysis. Corruption of either the NOA or NPI tables, or the result table, causes
this problem.
Corrective Action
To correct the problem, verify that the dial plan file was loaded correctly, using the procedure that is
described in the “Verifying Proper Loading of a Dial Plan” section on page 6-121.
ANAL: Prof_GetFail_NOATbl
This alarm occurs during profile analysis when the NOA table is unreadable. This problem can occur if
the NOA table is corrupted, the underlying software fails, or the NOA table is built without all the
existing call context NOA values.