10-155
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 10 Signaling Troubleshooting
Troubleshooting Signaling Alarms
Signaling Connection Control Part Binding Failure—Signaling (126)
The Signaling Connection Control Part Binding Failure alarm (major) indicates that the SCCP binding
failed. The primary cause of the SCCP Binding Failure alarm is that the Trillium stack binding failed.
To correct the primary cause of the alarm, re-initialize the TSA process or remove the subsystem from
the EMS table and add it again.
Transaction Capabilities Application Part Binding Failure—Signaling (127)
The Transaction Capabilities Application Part Binding Failure alarm (major) indicates that the TCAP
binding failed. This alarm is raised when the TCAP layer does not have enough service access point
(SAP) to bind for the subsystem. Currently only 16 subsystems are allowed on the same platform. Check
the Subsystem table to see if you have more than 16 subsystems on the same platform, Feature Server
for POTS, Tandem, and Centrex services (FSPTC) or Feature Server for AIN services (FSAIN). The
primary cause of the TCAP Binding Failure alarm is that the Trillium stack binding failed. To correct
the primary cause of the alarm, re-initialize the TSA process or remove the subsystem from the EMS
table and add it again.
Session Initiation Protocol Trunk Operationally Out-of-Service—Signaling
(142)
The Session Initiation Protocol Trunk Operationally Out-of-Service alarm (critical) indicates that the
SIP trunk is operationally out-of-service. 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 or SIP-T trunk. To correct the
primary cause of the alarm, verify that the 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 Trunk TSAP address
from the alarm event report. If the same alarm is reported on all the softswitch trunk groups, then verify
that the network connection is operational. If the ping is not successful, then diagnose the issue that
prevents the TSAP address from being reached. Verify the SIP application is running on the remote host
and listening on the port specified in the TSAP address.
Internet Protocol Interface Link to the Signaling System 7 Signaling Gateway is
Down—Signaling (143)
The Internet Protocol Interface Link to the Signaling System 7 Signaling Gateway is Down alarm
(minor) indicates that an IP interface link to the SS7 signaling gateway is down. The primary cause of
the alarm is an interface hardware problem. To correct the primary cause of the alarm, check the link
interfaces.
All Internet Protocol Interface Links to Signaling System 7 Signaling Gateway
are Down—Signaling (144)
The All Internet Protocol Interface Links to Signaling System 7 Signaling Gateway are Down alarm
(critical) indicates that all IP interface links to the SS7 signaling gateway are down. The primary cause
of the alarm is an interface hardware problem. To correct the primary cause of the alarm, check the link
interfaces.
