Troubleshooting guide

6-154
Cisco PGW 2200 Softswitch Release 9.8 Operations, Maintenance, and Troubleshooting Guide
OL-0800-14
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform
Resolving Bearer Channel Connection Problems
Step 7 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.
Calls are Misrouting
If calls are misrouting, you might have a problem with your dial plan or routing data. To identify the
source of the problem and resolve it, perform the following steps:
Step 1 If you have not already collected system data, refer to the method that is described in the “Collecting
System Data for Cisco TAC” section on page 6-93.
Step 2 Perform a diagnostic trace of the dial plan and routing data using the translation verification viewer, as
described in the “Using the Translation Verification Viewer” section on page 3-134.
If the diagnostic trace does not reveal any configuration errors in your dial plan or routing data, proceed
to Step 8. Otherwise, proceed to Step 3 to correct the configuration errors.
Step 3 Correct your dial plan or routing data that is indicated in the output of the translation verification viewer
and proceed to Step 7.
Note Use the appropriate MML commands to correct the data based on the elements of the
configuration that you must change. For more information on the appropriate MML commands
for changing the configuration of individual dial plan and routing data elements, see the Cisco
PGW 2200 Softswitch Release 9.8 Dial Plan Guide.
If the call that is misrouting is an MGCP dial call, the value for the MGCPDIALPKG result type could
be incorrect. To correct the value of the MGCPDIALPKG result type, proceed to Step 4.
Step 4 Verify the current setting of the MGCPDIALPKG result type by using the
numan-rtrv:resulttable:custgrpid=” group_number ”,name=” result_name ”,resulttype=”MGCPDIALPKG
”,SETNAME=”
set_name ” MML command:
Where:
• group_number—Customer group identification number that is associated with the affected dial plan.
• result_name—Result name that is associated with the affected dial plan.
• set_name—Name of the set that is associated with the affected MGCP dial plan.
If the setting is not correct, proceed to Step 5. Otherwise, proceed to Step 8.
Step 5 Change the MGCPDIALPKG settings by issuing the
numan-ed:resulttable:custgrpid=” group_number ”,name=” result_name ”,resulttype=”MGCPDIALPKG”,
SETNAME=”
set_name ” DW1=” call_type ” DW2=” x ” MML command:
Where:
• group_number—Customer group identification number that is associated with the affected dial plan.
• result_name—Result name that is associated with the affected dial plan.
• set_name—Name of the set that is associated with the affected MGCP dial plan.
• call_type—Call type for the MGCP calls. Valid values are digital, analog, and dynamic.
• x—Value for data word 2. Valid values are 0 and 1.