Troubleshooting guide

6-14
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 5 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: BLoopCtrExceeded
The alarm occurs when a B-number analysis operation has gone into an infinite loop. The purpose of the
alarm is to limit the number of passes spent in the analysis tree to 30.
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 Validate that there are no infinite loops in the B-number dial plan, as described in the “Verifying a Dial
Plan Translation” section on page 3-135.
If there are infinite loops in your B-number dial plan, modify the settings in your B-number dial plan to
remove the infinite loops, by 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 there are no infinite loops in your B-number dial plan, then proceed to Step 3.
Step 3 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: BNum_GetFail_SrvcTbl
This alarm occurs during B-number analysis when a screening result is encountered and an attempt to
read the service table to determine the name of the service performing the screening fails. This failure
is because of corruption of either the result table or the service table.
Corrective Action
To correct the problem, verify that the dial plan file was loaded correctly, using the procedure that is
described in “Verifying Proper Loading of a Dial Plan” section on page 6-121.
ANAL: BNum_MdfyBFail_ AnnounceID
This alarm occurs during B-number 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–9999) or a B-number less than four digits long commonly causes this
replacement failure.