Troubleshooting guide

6-143
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
In the second message, which contains information on the affected CIC, the text that immediately
follows the word “point” identifies the following:
• MML name of the signaling service that is associated with the affected CIC (sigsrv1 in the example).
• Internal hexadecimal code that is associated with the identified signaling service (00130002 in the
example). This number appears in brackets.
• Affected span number, in hexadecimal (ffff in the example). This field for this type of message is
always set to “ffff”, because there is no correlation to span in SS7 networks.
• Affected CIC number, in hexadecimal (2 in the example).
Step 5 Convert the hexadecimal values for the span, bearer channel, and CIC into decimal values.
Step 6 Refer to the information gathered in Step 4 and Step 5 and stop the call on an affected CIC for its
associated signaling service. Use the procedure that is described in the “Stopping Calls on CICs” section
on page 6-147.
Step 7 Refer to the information gathered in Step 4and Step 5, stop the call on an affected span and bearer
channel for its associated media gateway destination, by using the procedure that is described in the
“Stopping Calls on Spans” section on page 6-146.
Step 8 Reset the affected CIC using the procedure in the “Resetting CICs” section on page 6-140.
Step 9 Repeat Step 3 through Step 8. Search for additional sets of affected CICs, spans, and bearer channels,
until you address all of the stuck CICs identified by the call state audit.
Step 10 Repeat Step 3 and Step 4. Perform a second 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 still stuck, proceed to Step 11. Otherwise, proceed to Step 14.
Step 11 Forcefully end the call on the signaling services and CICs identified in Step 4 by entering the
kill-call: sig_srv :cic= num ,confirm command.
Caution The kill-call MML command forcibly ends calls locally. It does not send any SS7 messages to the
far-end. Enter the Kill-call command only to clear stuck CICs that you cannot clear by issuing the
reset-cic or stp-call MML commands.
Where:
• sig_srv—MML name of the signaling service that is identified in Step 4.
• num—Number of the stuck CIC identified in Step 4.
For example, to forcefully stop a call on CIC 215, which is associated with a signaling service called
sigsrv1, enter the
kill-call:sigsrv1:cic=215,confirm command.
Repeat this step for each CIC you have identified as being stuck.
Step 12 Forcefully end the call on the signaling service, spans, and bearer channels that were identified in Step 4
by entering the
kill-call: sig_srv :span= span_num ,bc= bear_chan ,confirm command.
Where:
• sig_srv—MML name of the signaling service that is identified in Step 4.
• span_num—Number of the span that was identified in Step 4.
• bear_chan—Number of the stuck bearer channel that was identified in Step 4.
For example, to forcefully stop a call on bearer channel 2, which is on span 2, and is associated with a
signaling service called nassvc1, enter the
kill-call:nassvc1:span=2,bc=2,confirm command.