10-157
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 10 Signaling Troubleshooting
Troubleshooting Signaling Alarms
Emergency Trunks Become Locally Blocked—Signaling (153)
The Emergency Trunks Become Locally Blocked alarm (critical) is issued when an emergency trunk
(CAS, SS7, or ISDN) becomes locally blocked. No further action is required.
Emergency Trunks Become Remotely Blocked—Signaling (154)
The Emergency Trunks Become Remotely Blocked alarm (critical) is issued when when an emergency
trunk (CAS, SS7, or ISDN) becomes remotely blocked. No further action is required.
Integrated Services Digital Network Signaling Gateway Down—Signaling
(156)
The Integrated Services Digital Network Signaling Gateway Down alarm (major) is issued when the
BTS 10200 cannot communicate to the ISDN gateway. The primary cause of the alarm is that the BTS
10200 cannot communicate to the ISDN gateway due to a failure in the gateway. Additionally, the SCTP
association may also be down. To correct the primary cause of the alarm, verify the whether or not the
SCTP association is down and restore the SCTP association. The secondary cause of the alarm is that
the IUA layer may be down in the gateway. If the IUA layer is down, it will be automatically recovered
no further action is required.
Integrated Services Digital Network Signaling Gateway Inactive—Signaling
(157)
The Integrated Services Digital Network Signaling Gateway Inactive alarm (major) indicates that a
shutdown
command has been executed in the application server on the ISDN gateway side. No action
needed. The application server will be automatically recovered.
Session Initiation Protocol Server Group Element Operationally Out of
Service—Signaling (162)
The Session Initiation Protocol Server Group Element Operationally Out of Service alarm (critical) is
issued when the BTS 10200 is unable to communicate with a remote SIP party. The primary cause of the
alarm is that the BTS 10200 is unable to communicate with a remote SIP party (call-agent or proxy) over
a SIP server group element. To correct the primary cause of the alarm, verify DNS resolution exists if
TSAP address of the remote entity is a domain name. Verify the remote entity is reachable by ICMP
ping, using the TSAP address from the Event Report. If the same alarm is reported for other TSAP
addresses on several softswitch trunk groups and/or server-group elements, then verify that the network
connection is operational. The secondary cause of the alarm is that the remote SIP party is not
operational. To correct the secondary cause of the alarm, diagnose the issue that prevents the TSAP
address from being reached if a ping is not successful. Verify that the SIP application is running on the
remote host and listening on the port specified in the TSAP address.
