10-156
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 10 Signaling Troubleshooting
Troubleshooting Signaling Alarms
One Internet Protocol Interface to Signaling System 7 Signaling Gateway is
Down—Signaling (145)
The One Internet Protocol Interface to Signaling System 7 Signaling Gateway is Down alarm (minor)
indicates that one 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.
Stream Control Transmission Protocol Association Congested—Signaling (150)
The Stream Control Transmission Protocol Association Congested alarm (minor) indicates that the
SCTP association is congested. The primary cause of the alarm is that the network is congested. To
correct the primary cause of the alarm, clean off the network congestion caused by routing or switching
issues. The secondary cause of the alarm is that the CPU is throttled. To correct the secondary cause of
the alarm, upgrade to a more powerful platform or offload some traffic.
Subscriber Line Faulty—Signaling (151)
The Subscriber Line Faulty alarm (minor) indicates that the residential gateway returned an error code
in response to a command from the MGW. To correct the primary cause of the alarm, try controlling
subscriber termination to OOS and back into INS using the BTS 10200 CLI command. If the problem
persist after more calls, check the configuration in the BTS 10200 and the RGW. If the error codes
returned by MGW are harmless, it can be suppressed by adding a new entry in the
MGCP-RETCODE-ACTION table and change EP-ACTION to RESET/NONE.
Note
The following additional troubleshooting information is applicable to Release 5.0 MR2 and above.
If the VXSM is OOS at the GW side, a 501 error message for CRCX/AUEP may be transmitted. This
generally occurs if there is resource state mismatch between the BTS 10200 (ACTV IDLE) and the
VXSM (DOWN). For additional information on the 501 error message, refer to
“Recoverable and Nonrecoverable Error Codes.”
When the mismatch occurs the default behavior is UPDATE for both the create connection (CRCX) and
audit endpoint (AUEP) messages as follows:
CLI>add mgcp-retcode-action mgw-profile-id=<abc>; mgcp-msg=AUEP; mgcp-retcode=501;
call-action=RELEASE; ep-action=UPDATE
CLI>add mgcp-retcode-action mgw-profile-id=<abc>; mgcp-msg=AUEP; mgcp-retcode=501;
call-action=RELEASE; ep-action=UPDATE
If a 501 response is received for the CRCX message on execution of the EP-ACTION=UPDATE for
CRCX, the BTS 10200 will start auditing the endpoint by sending an AuditEndpoint message requesting
restart-method (rm parameter reported in the RSIP message, which indicates the service state at the
GW). If the restart-method information reported in AUEP message is different from the BTS 10200
termination state, the termination state will be updated accordingly (if rm=forced, DOWN is set in
termination oper-status; if rm=restart DOWN is cleared in termination oper-status).
If a 501 response is received for the AUEP message on execution of the EP-ACTION=UPDATE for
AUEP, the BTS will unconditionally mark the termination as DOWN.
To clear DOWN from the termination oper-status, you either need to control the
trunk/subscriber-termination OOS/INS mode=forced; or trigger RSIP rm=restart from the GW.
