10-133
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 10 Signaling Troubleshooting
Troubleshooting Signaling Alarms
Signaling System 7 Signaling Link Down—Signaling (13)
The Signaling System 7 Signaling Link Down alarm (major) indicates the SS7 signaling link is down.
The primary cause of the alarm is that the SS7 trunk group may be out-of-service (OOS). To correct the
primary cause of the alarm, use the
control ss7-trunk-grp
command to place the trunk group in service
(INS). The secondary cause of the alarm is that the local Ulticom stack may be down. To correct the
secondary cause of the alarm, run the Ulticom
stack
command again. The ternary cause of the alarm is
that the SS7 link may be disconnected or faulty. To correct the ternary cause of the alarm, check the
Ulticom local configuration. The subsequent cause of the alarm is that the remote SS7 signaling site may
be down or incorrectly configured. To correct the subsequent cause of the alarm, check the Ulticom
remote configuration.
Signal System 7 and Call Agent Fail-over Interaction
When an ISUP SS7 signaling link goes into the link failure state, an Signaling System 7 Signaling Link
Down alarm (13) is activated and the call-agent will begin a 120 second timer. When the SS7 signaling
link is restored, in-progress calls are cleared if they were in a transient state, if an event occurred that
required the sending of an ISUP message during the link failure, or if the 120 second timer has expired.
Should the call-agent fail-over for any reason, the state of the 120 second timer or any indication of a
request for an outgoing message that could not be sent will not be preserved. If the signaling links are
in the failure state on the stand-by side, the 120 second timer will be re-started; however, if the links
should restore prior to that the timer expiry, any stable calls will NOT be cleared.
This applies should multiple fail-overs occur prior to eventual signaling link restoration. In these
situations, if a call clearing event has been missed, any calls remaining up will be cleared by the normal
ISUP network recovery and message retransmission mechanisms.
Link is Remotely Inhibited—Signaling (14)
The Link is Remotely Inhibited alarm (minor) indicates that the SS7 link is inhibited at the remote end.
The primary cause of the alarm is that the specified SS7 link is inhibited at the remote end. To correct
the primary cause of the alarm, monitor events and alarms at the network level for any related to the
specified SS7 link. Restorative actions need to be taken on the remote end.
Link is Locally Inhibited—Signaling (15)
The Link is Locally Inhibited alarm (minor) indicates that the SS7 link is inhibited at the local end. The
primary cause of the alarm is that the specified SS7 link is inhibited at the local end. To correct the
primary cause of the alarm, verify that the SS7 signaling adapter process is running and that the SS7
interface card(s) are in service. If a component is found to be non-operational, restore it to service.
