![Cisco BTS 10200 Softswitch Troubleshooting Manual Download Page 500](http://html.mh-extra.com/html/cisco/bts-10200-softswitch/bts-10200-softswitch_troubleshooting-manual_67550500.webp)
10-132
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 10 Signaling Troubleshooting
Troubleshooting Signaling Alarms
Failed to Send Complete Session Initiation Protocol Message—Signaling (10)
The Failed to Send Complete Session Initiation Protocol Message alarm (minor) indicates that a SIP
message failure has occurred. The primary cause of the alarm is that the SIP stack failed to send an SIP
message due to it exceeding the maximum length of a UDP packet. To correct the primary cause of the
alarm, the message should be captured on passive testing equipment and sent to Cisco TAC for
evaluation if that alarm occurred during normal network operations.
Note
Refer to the
“Obtaining Documentation and Submitting a Service Request” section on page lvi
for
detailed instructions on contacting Cisco TAC and opening a service request.
Failed to Allocate Session Initiation Protocol Control Block—Signaling (11)
The Failed to Allocate Session Initiation Protocol Control Block alarm (major) indicates that a SIP
control block allocation failed. The primary cause of the alarm is that there is not enough memory to
allocate a SIP Call Control Block. To correct the primary cause of the alarm, Increase the SIP CCB count
specified in mem.cfg file and restart the Call Agent for the changes to take effect.
Feature Server is not Up or is not Responding to Call Agent—Signaling (12)
The Feature Server is not Up or is not Responding to Call Agent alarm (critical) indicates that the feature
server is not up or is not responding to the call agent server. The primary cause of the alarm is that the
feature server platform is down or is not operating properly. To correct the primary cause of the alarm,
restart the applicable feature server.