Troubleshooting guide

6-142
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
Note The Cisco PGW 2200 Softswitch does not run the audit cron job when the CPU load of the call engine
is greater than the limit set in the XECfgParm.dat file. For more information on XECfgParm.dat
configuration, see
Cisco PGW 2200 Softswitch Release 9 Software Installation and Configuration Guide.
Manually Resolving Stuck CICs
If you want to resolve stuck CICs manually, perform the follow 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 Set the logging level of the call engine process (eng-01) to info by using the procedure that is described
in the “Changing the Log Level for Processes” section on page 6-91.
Step 3 Perform a call state audit by using the procedure that is described in the “Auditing Call States” section
on page 6-144.
When you search the active system log file, look for a CP_INFO_CHAN_STATE message containing
the following text:
NAS is idle, SC is busy
The following example shows the log message:
Fri May 25 13:27:45:384 2001 | engine (PID 14217) <Info>
CP_INFO_CHAN_STATE:Mismatch in channel state, NAS is idle, SC is busy, span 0, channel 2
If you find this kind of CP_INFO_CHAN_STATE message in the active system log file, proceed to
Step 4. Otherwise, proceed to Step 16.
Step 4 There should be two associated CP_ERR_AUEP messages, one containing information on the affected
span and bearer channel and another containing information on the affected CIC.
Search the active system log file for a CP_ERR_AUEP message that contains the following text:
Audit:failed to audit end point
The following example shows these messages:
Fri May 25 13:27:45:384 2001 | engine (PID 14217) <Error>
CP_ERR_AUEP:Audit:failed to audit end point nassvc1[00140001]/0/2
Fri May 25 13:27:45:384 2001 | engine (PID 14217) <Error>
CP_ERR_AUEP:Audit:failed to audit end point sigsrv1[00130002]/ffff/2
In the first message, which contains information on the affected span and bearer channel, the text that
immediately follows the word “point” identifies the following:
• MML name of the media gateway destination that is associated with the affected span and bearer
channel (nasssvc1 in the example).
• Internal hexadecimal code that is associated with the identified media gateway destination
(00140001 in the example). This number appears in brackets.
• Affected span number, in hexadecimal (0 in the example).
• Affected bearer channel number, in hexadecimal (2 in the example).