Call Agent Is Not Up Or Is Not Responding To The Feature Server—Signaling (69) - Cisco BTS 10200 Troubleshooting Manual

Chapter 10 Signaling Troubleshooting
Call Agent is not Up or is not Responding to the Feature Server—Signaling (69)
The Call Agent is not Up or is not Responding to the Feature Server alarm (critical) indicates that a CA
and FS communications message timed out. The primary cause of the alarm is that CA to FS
communication has failed due to wrong system configuration; -OR- CA or FS is down. To correct the
primary cause of the alarm, check the configuration related to the CA to FS communication. Also, check
the FS table entries and the CA entry.
Signaling System 7 Stack not Ready—Signaling (75)
The Signaling System 7 Stack not Ready alarm (critical) indicates that the SS7 stack in not ready. The
primary cause of the alarm that the SS7 stack not configured properly. To correct the primary cause of
the alarm, check SS7 stack configuration. The secondary cause of the alarm is that the SS7 stack is not
ready. To correct the secondary cause of the alarm, check the SS7 stack status. Do a platform start -i
omni command to bring up the SS7 stack.
Integrated Services Digital Network Single D-channel Down for Non-Facility
Associated Signaling—Signaling (78)
The Integrated Services Digital Network Single D-channel Down for Non-Facility Associated Signaling
alarm (minor) indicates that one of the ISDN D-channels in the PRI is down. The primary cause of the
alarm is that one of the ISDN D-channels in PRI is down. To correct the primary cause of the alarm,
check the gateway power and the gateway connection to the PBX.
Trunking Gateway Unreachable—Signaling (79)
The Trunking Gateway Unreachable alarm (major) indicates that the trunking gateway is not responding
to keep-alive Audit Endpoint messages. To correct the primary cause of the alarm, check the IP
connectivity status between BTS call agent and the trunking gateway.
Out of Bounds, Memory/Socket Error—Signaling (80)
The Out of Bounds, Memory/Socket Error alarm (critical) indicates that a memory socket out of bounds
error has occurred. The primary cause of the alarm is that the system is out of heap memory. To correct
the primary cause of the alarm, contact Cisco TAC and increase RAM memory. The secondary cause of
the alarm is that the system is out of IPC pool memory. To correct the secondary cause of the alarm,
resize the IPC pool size in Platform Configuration file. The ternary cause of the alarm is that a socket
error has occurred. An inappropriate or already bound socket may be in use. To correct the ternary cause
of the alarm, check the UDP port supplied with the MGA command-line for validity and prior use.
Refer to the
Note
detailed instructions on contacting Cisco TAC and opening a service request.
OL-8723-19
"Obtaining Documentation and Submitting a Service Request" section on page lvi
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
Troubleshooting Signaling Alarms
for
10-139