Troubleshooting guide

6-144
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
Repeat this step for each bearer channel you have identified as being stuck.
Step 13 Repeat Step 3 and Step 4. Perform a third call state audit and search the active system log file to
determine whether the previously identified CICs are still stuck.
If the previously identified CICs are no longer stuck, proceed to Step 14. If these CICs are still stuck,
proceed to Step 15.
Step 14 Set the logging level of the call engine (eng-01) to err, by using the procedure that is described in the
“Changing the Log Level for Processes” section on page 6-91.
Step 15 Perform a call trace as described in the “Performing a Call Trace” section on page 6-156.
Step 16 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.
Auditing Call States
To run a call state audit, which compares the call states of the CICs on the Cisco PGW 2200 Softswitch
with the associated states of the spans and bearer channels on the media gateway, 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 Log in to the active Cisco PGW 2200 Softswitch, start an MML session, and enter the sta-aud command.
Note The Cisco PGW 2200 Softswitch does not indicate when the sta-aud MML command completes
its call state audit process. Wait a few minutes before proceeding to the next step.
The call state audit sends results to the active system log file.
Step 3 View the active system log file according to the instructions in the “Viewing System Logs” section on
page 6-90. If you see any call state mismatch logs in the active system log file, contact the Cisco TAC
for assistance in resolving the call state mismatch. See the “Obtaining Documentation and Submitting a
Service Request” section on page xviii for more information about contacting the Cisco TAC.
Step 4 When you finished auditing the call states, enter the stp-aud command:
Stopping Calls
Enter the stp-call MML command to stop calls gracefully on all traffic channels that are associated with
a specified system resource. The following sections describe the stp-call MML command:
• Stopping Calls on a Cisco PGW 2200 Softswitch, page 6-145
• Stopping Calls on a Media Gateway, page 6-145
• Stopping Calls on a Trunk Group, page 6-145
• Stopping Calls on a Signaling Service, page 6-145