![Cisco BTS 10200 Softswitch Troubleshooting Manual Download Page 485](http://html.mh-extra.com/html/cisco/bts-10200-softswitch/bts-10200-softswitch_troubleshooting-manual_67550485.webp)
10-117
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 10 Signaling Troubleshooting
Monitoring Signaling Events
Signaling Connection Control Part Routing Error—Signaling (125)
The Signaling Connection Control Part Routing Error alarm (major) indicates that the SCCP route was
invalid or not available. To troubleshoot and correct the cause of the Signaling Connection Control Part
Routing Error alarm, refer to the
“Signaling Connection Control Part Routing Error—Signaling (125)”
.
Signaling Connection Control Binding Failure—Signaling (126)
The Signaling Connection Control Binding Failure alarm (major) indicates that the SCCP binding failed.
To troubleshoot and correct the cause of the Signaling Connection Control Binding Failure alarm, refer
to the
“Signaling Connection Control Part Binding Failure—Signaling (126)” section on page 10-155
.
Transaction Capabilities Application Part Binding Failure—Signaling (127)
The Transaction Capabilities Application Part Binding Failure alarm (major) indicates that the TCAP
binding failed. To troubleshoot and correct the cause of the Transaction Capabilities Application Part
Binding Failure alarm, refer to the
“Transaction Capabilities Application Part Binding
Failure—Signaling (127)” section on page 10-155
Transaction Capabilities Application Part Reaches the Provisioned Resource
Limit—Signaling (132)
The Transaction Capabilities Application Part Reaches the Provisioned Resource Limit event serves as
a warning that the TCAP process has reached or reaches the provisioned resource limit. The primary
cause of the event is that the TCAP process runs out of all of the pre-configured dialogue IDs or invoke
IDs. To correct the primary cause of the event, increase the number pre-configured dialogue IDs or
invoke IDs.
Unable to Decode Generic Transport Descriptor Message—Signaling (133)
The Unable to Decode Generic Transport Descriptor Message event functions as an informational alert
that a GTD message could not be decoded. The primary cause of the event is that the GTD parser failed
to decode a GTD message received from the specified endpoint. To correct the primary cause of the
event, verify that the version of the GTD protocol used by the device at the remote endpoint is consistent
with the version expected by the call agent. Examine the associated signaling link to see if there is any
interruption of the supplementary services on the link.