Troubleshooting guide

6-13
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 that this alarm identifies, 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.
ANAL: ATableFail_GetResult
This alarm occurs when access to the result table failed during A-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, using the procedure that is
described in “Verifying Proper Loading of a Dial Plan” section on page 6-121.
ANAL: ATableFlt_DgtRangeError
This alarm occurs when the A-number analysis digit tree has been accessed with a digit that is out of
range for the digit tree table. This alarm could occur if the system was incorrectly configured to support
a base 10 dial plan, and an overdecadic digit was received from the line and passed to 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 parameter, *.OverdecadicDigitsEnabled, is set correctly in the XECfgParm.dat file on
each host.
Note The setting of this parameter should reflect the dial plan restrictions for the protocol in use. If
the configured protocol supports the use of overdecadic digits, you should set the parameter to
true. If the configured protocol does not support the use of overdecadic digits, you should set the
parameter to false.
If the setting for the parameter is correct, proceed to Step 3. Otherwise, reboot your software using the
procedure that is described in the “Rebooting Software to Modify Configuration Parameters” section on
page 6-183.
Step 3 If the setting for the parameter is false, check the received digit string for presence of an overdecadic
digit. If the digit string does not have an overdecadic digit, proceed to Step 5. If the digit string does have
an overdecadic digit, proceed to Step 4.
If the setting for the parameter is true, proceed to Step 5.
Step 4 Check the compliancy documentation for the configured protocol.
If the documentation indicates that overdecadic digits are supported, change the setting for the
*.OverdecadicDigitsEnabled XECfgParm.dat parameter to true on both hosts, by using the procedure in
the “Rebooting Software to Modify Configuration Parameters” section on page 6-183.
If the documentation indicates that overdecadic digits are not supported, proceed to Step 5.