![Cisco BTS 10200 Softswitch Troubleshooting Manual Download Page 469](http://html.mh-extra.com/html/cisco/bts-10200-softswitch/bts-10200-softswitch_troubleshooting-manual_67550469.webp)
10-101
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 10 Signaling Troubleshooting
Monitoring Signaling Events
Route Set Congested—Signaling (22)
The Route Set Congested alarm (minor) indicates that the specified route set is congested. To
troubleshoot and correct the cause of the Route Set Congested alarm, refer to the
Congested—Signaling (22)” section on page 10-135
Destination Point Code Unavailable—Signaling (23)
The Destination Point Code Unavailable alarm (major) indicates that the specified DPC is not available.
To troubleshoot and correct the cause of the Destination Point Code Unavailable alarm, refer to the
“Destination Point Code Unavailable—Signaling (23)” section on page 10-136
.
Destination Point Code Congested—Signaling (24)
The Destination Point Code Congested alarm (minor) alarm indicates that the specified DPC is
congested. To troubleshoot and correct the cause of the Destination Point Code Congested alarm, refer
to the
“Destination Point Code Congested—Signaling (24)” section on page 10-137
Unanswered Blocking Message—Signaling (25)
The Unanswered Blocking Message event serves as a warning that a BLO message was not answered.
The primary cause of the event is that a BLO message was not acknowledged before the T13 expired for
the associated CIC. To correct the primary cause of the event, verify that the SS7 signaling adapter
processes is running normally. Verify that the call agent platform is active. Verify that the SS7 interface
hardware is in service. Verify that the associated SS7 signaling link is available. Verify that the T13
timer is set to an appropriate level. Verify that the SS7 link is not congested.
Unanswered Unblocking Message—Signaling (26)
The Unanswered Unblocking Message event serves as a warning that an UBL message was not
answered. The primary cause of the event is that a UBL message was not acknowledged before the T15
expired for the associated CIC. To correct the primary cause of the event, verify that the SS7 signaling
adapter processes is running normally. Verify that the call agent platform is active. Verify that the SS7
interface hardware is in service. Verify that the associated SS7 signaling link is available. Verify that
the T13 timer is set to an appropriate level. Verify that the SS7 link is not congested.
Unanswered Circuit Group Blocking Message—Signaling (27)
The Unanswered Circuit Group Blocking Message event serves as a warning that a CGB message was
not answered. The primary cause of the event is that a CGB message was not acknowledged before the
T19 expired for the associated CIC. To correct the primary cause of the event, verify that the SS7
signaling adapter processes is running normally. Verify that the call agent platform is active. Verify that
the SS7 interface hardware is in service. Verify that the associated SS7 signaling link is available. Verify
that the T13 timer is set to an appropriate level. Verify that the SS7 link is not congested.