![Cisco BTS 10200 Softswitch Troubleshooting Manual Download Page 486](http://html.mh-extra.com/html/cisco/bts-10200-softswitch/bts-10200-softswitch_troubleshooting-manual_67550486.webp)
10-118
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 10 Signaling Troubleshooting
Monitoring Signaling Events
Signaling System 7 Message Encoding Failure—Signaling (134)
The Signaling System 7 Message Encoding Failure event functions as an informational alert that a SS7
message encoding failed. The primary cause of the event is that there was an error in the ISUP stack or
the SAI message. To correct the primary cause of the event, capture a SS7 trace of the circuit for
examination by Cisco TAC.
Note
Refer to the
“Obtaining Documentation and Submitting a Service Request” section on page lvi
for
detailed instructions on contacting Cisco TAC and opening a service request.
Signaling System 7 Message Decoding Failure—Signaling (135)
The Signaling System 7 Message Decoding Failure event functions as an informational alert that the
decoding of a SS7 message failed. The primary cause of the event is that an error occurred in the ISUP
stack or the SAI message. To correct the primary cause of the event, capture a SS7 trace of the circuit
for examination by Cisco TAC.
Note
Refer to the
“Obtaining Documentation and Submitting a Service Request” section on page lvi
for
detailed instructions on contacting Cisco TAC and opening a service request.
Signaling System 7 Message Invalid Received—Signaling (136)
The Signaling System 7 Message Invalid Received event functions as an informational alert that an
invalid SS7 message was received. The primary cause of the event is that an invalid message was
received from the line in the ISUP stack. To correct the primary cause of the event, verify the SSP
sending the message to the CA is correctly configured. Capture a SS7 trace of the circuit for examination
by Cisco TAC.
Note
Refer to the
“Obtaining Documentation and Submitting a Service Request” section on page lvi
for
detailed instructions on contacting Cisco TAC and opening a service request.
Signaling System 7 Confusion Message Received—Signaling (137)
The Signaling System 7 Confusion Message Received event functions as an informational alert that the
received SS7 message was confused. The primary cause of the event is that an ISUP message or
parameter received was not recognized or understood. To correct the primary cause of the event, check
the log for more information (including CFN diagnostic output). Capture SS7 trace of affected circuits.
If diagnostic data indicates messages/parameters that must be supported are being dropped, refer the
captured data to Cisco TAC along with a description of the call scenario.
Note
Refer to the
“Obtaining Documentation and Submitting a Service Request” section on page lvi
for
detailed instructions on contacting Cisco TAC and opening a service request.