Troubleshooting guide

6-86
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 11 Verify that the BDigitCCrm property for the associated trunk group is set to the correct number string.
Enter the prov-rtrv MML command that is shown in the following example:
prov-rtrv:trnkgrpprop:name=”trnkgrp1”
If the BDigitCCrm property in the associated trunk group is not set to the correct number string, enter
the prov-ed MML command to modify the value of the property as shown in the following example:
prov-ed:trnkgrp:name=”trnkgrp1”, BDigitCCrm=34
Otherwise, proceed to Step 12.
Step 12 Verify that the associated B-number analysis configuration allows removal of a country code digit. Enter
the numan-rtrv MML command that is shown in the following example:
numan-rtrv:digmodstring:custgrpid=”T002”
If the associated B-number analysis configuration does not allow removal of a for country code digit,
enter the numan-ed MML command to modify of the setting as shown in the following example:
numan-ed:digmodstring:custgrpid=”T002”, name=”ccspain”, digstring=”34”
Otherwise, proceed to Step 13.
Step 13 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.
If the dial plan was loaded correctly, the procedure is finished. Otherwise, proceed to Step 14.
Step 14 Perform a call trace, as described in “Performing a Call Trace” section on page 6-156.
Step 15 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.
UCM: MGCPDIALAuthFail
This alarm occurs when an MGCP dial call fails after an automatic switchover, because of the expiration
of a timer waiting for a Notify message from the associated media gateway.
Note This alarm is valid as of Release 9.3(1). There is a patch for Release 9.3(2) that retires this alarm.
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 the configuration of the associated media gateway. If there are no configuration problems, proceed
to Step 3. Otherwise, fix the identified configuration problems.
Step 3 Verify that the IP path between the media gateway and the Cisco PGW 2200 Softswitch is working
properly. If you find no problems in the IP path between the media gateway and the
Cisco PGW 2200 Softswitch, proceed to Step 4. Otherwise, fix the identified IP path problems.