Troubleshooting guide

6-15
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 Verify that all the configured announcement IDs are within the range 0 through 9999, by using the
numan-rtrv MML command. See Cisco PGW 2200 Softswitch Release 9.8 Dial Plan Guide for more
information.
If any of the announcement IDs are outside of the range, modify its 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: BTableFail_GetDigTree
This alarm occurs if you specified an invalid path for B-number analysis or if the B-number analysis
table is not loaded.
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: BTableFail_GetDigMod
This alarm occurs when an attempt to retrieve a modification string during B-number analysis fails. The
problem occurs if the modification table is not loaded or the system provides a pointer to a nonexistent
location in the modification table.
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: BTableFail_GetResult
This alarm occurs when access to the result table failed during B-number analysis. The problem occurs
if the result table is not loaded or the system provides a pointer to a nonexistent location in the result
table.
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.