10-130
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 10 Signaling Troubleshooting
Troubleshooting Signaling Alarms
Socket Failure—Signaling (7)
The Socket Failure alarm (major) indicates that there is a failure in creating/binding to the UDP socket.
The primary cause of the alarm is that there is a failure in creating or binding to the UDP socket. To
correct the primary cause of the alarm, verify that there is no conflict in port assignment with other
processes in the system and ensure no previous instance of the same process is still running. The
secondary cause of the alarm is that a software logic problem has occurred. To correct the secondary
cause of the alarm, contact Cisco TAC.
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.
Media Gateway Control Protocol
The Socket Failure alarm is issued when there is a failure in creating the UDP port used by the MGCP
stacks. Some other application may already be active on the same UDP port and IP address to which the
Call Agent MGCP stack is assigned. Reconfigure the MGCP stack to use a free UDP port.
Session Initiation Protocol
The Socket Failure alarm is issued when there is a failure in creating the UDP port used by the SIA
process. Some other application may already be active on the same UDP port and IP address to which
the SIA process is assigned. Reconfigure the SIA port to use a free port or the SIP default port 5060.
SIGNALING(175)
ENUM Server Farm Unavailable—Signaling (175)
CRITICAL
SIGNALING(176)
No Resources Available to Launch ENUM Query—Signaling (176)
CRITICAL
Table 10-3
BTS 10200 Signaling Alarms (continued)
Alarm Type
Alarm Name
Alarm Severity
