Troubleshooting guide

6-19
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, 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_MdfyBFail_AnnounceID
This alarm occurs during cause analysis when an announcement result is encountered and analysis is
unable to replace the last four digits of the B-number with the announcement ID. An out-of-range
announcement ID (it should be 0 to 9999) or a B-number less than four digits long usually causes this
problem.
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 affected announcement ID is within the range 0 through 9999, using the numan-rtrv
MML command. See Cisco PGW 2200 Softswitch Release 9.8 Dial Plan Guide for more information.
If the announcement ID is outside of the range, modify its value using the numan-ed MML command
and proceed to Step 3. See Cisco PGW 2200 Softswitch Release 9.8 Dial Plan Guide for more
information. Otherwise, proceed to Step 3.
Step 3 Verify that the affected B-number is at least four digits long, using the numan-rtrv MML command. See
Cisco PGW 2200 Softswitch Release 9.8 Dial Plan Guide for more information.
If the affected B-number is less than four digits long, modify its value using the numan-ed MML
command. See Cisco PGW 2200 Softswitch Release 9.8 Dial Plan Guide for more information.
Otherwise, proceed to Step 4.
Step 4 If you modified your dial plan, 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 5.
Step 5 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_MdfyBFail_AppPtInvld
This alarm occurs during cause analysis when a B-number modification result is encountered and the
application point (where digits are inserted) specified is beyond the end of the digit string. This problem
can occur if an incorrect application point is specified in the result data, a result table is corrupted, or
cause analysis values are incorrectly constructed.
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.