![Cisco BTS 10200 Softswitch Troubleshooting Manual Download Page 452](http://html.mh-extra.com/html/cisco/bts-10200-softswitch/bts-10200-softswitch_troubleshooting-manual_67550452.webp)
10-84
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 10 Signaling Troubleshooting
Signaling Events and Alarms
SIGNALING (161)
To monitor and correct the cause of the event, refer to the
“Session Initiation Protocol Update not
Allowed for Operator Service Position System Calls—Signaling (161)” section on page 10-123
SIGNALING (162)
To troubleshoot and correct the cause of the alarm, refer to the
“Session Initiation Protocol Server Group
Element Operationally Out of Service—Signaling (162)” section on page 10-157
.
DESCRIPTION
Session Initiation Protocol Update not Allowed for Operator Service Position System Calls (SIP
Update not Allowed for OSPS Calls)
SEVERITY
WARNING
THRESHOLD
100
THROTTLE
0
DATAWORDS
Trunk Group Description–STRING [21]
TSAP Address–STRING [65]
PRIMARY
CAUSE
The remote switch does not allow the BTS 10200 to send SIP UPDATE messages. The UPDATE
message is mandatory in CMSS and is used exclusively by the BTS 10200 for operator service calls
over SIP including BLV, emergency interrupt, and 911 ringback calls.
PRIMARY
ACTION
Upgrade or re-provision the remote switch so it can process incoming SIP UPDATE messages.
DESCRIPTION
Session Initiation Protocol Server Group Element Operationally Out of Service (SIP Server Group
Element Operationally out of Service)
SEVERITY
CRITICAL
THRESHOLD
100
THROTTLE
0
DATAWORDS
Server Group Description–STRING [64]
TSAP Address of the SIP-Element.–STRING [64]
PRIMARY
CAUSE
Issued when the BTS 10200 is unable to communicate with a remote SIP party (Call-Agent or Proxy)
over a SIP server group element.
PRIMARY
ACTION
If the TSAP address of the remote entity is a domain name, verify that the DNS resolution exists.
Verify that 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.
SECONDARY
CAUSE
The remote SIP party is not operational.
SECONDARY
ACTION
If the ping is not successful, then diagnose the issue that prevents the TSAP address from being
reached. Verify that the SIP application is running on the remote host and listening on the port
specified in the TSAP address.