Troubleshooting guide

6-20
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 specified application points in the result data are correct, using the numan-rtrv MML
command. See Cisco PGW 2200 Softswitch Release 9.8 Dial Plan Guide for more information.
If any of the application points are incorrect, modify their 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, using the procedure that is described in the “Verifying
Proper Loading of a Dial Plan” section on page 6-121.
ANAL: Cause_Rte_LoopDetected
This alarm occurs during cause analysis when a route or announcement result is encountered. In these
cases, the indicated route identifier is compared to a list of previously provided results. If the system
finds a match, it raises this alarm and returns an error to call processing. The system performs these
actions to prevent calls from being endlessly routed to a single route or series of routes because of cause
analysis interactions.
Corrective Action
To correct the problem that this alarm identifies, 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: CustId/StartIdx Missing
This alarm occurs when the property CustGrpId is not present on the identified trunk group. The property
CustGrpId must be present to enable the system to find the correct place to begin analysis.
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 Verify that the value of the CustGrpId property for the associated trunk group is correct by logging in to
the active Cisco PGW 2200 Softswitch, starting an MML session, and entering the
prov-rtrv:trnkgrpprop:name=“comp_name” command:
Where:
comp_name is the MML name for the affected trunk group.
For example, if you wanted to verify the properties of the trunk group that is called 1001, enter the
prov-rtrv:trnkgrpprop:name=“1001” command: