![Cisco BTS 10200 Softswitch Скачать руководство пользователя страница 478](http://html.mh-extra.com/html/cisco/bts-10200-softswitch/bts-10200-softswitch_troubleshooting-manual_67550478.webp)
10-110
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 10 Signaling Troubleshooting
Monitoring Signaling Events
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 troubleshoot and correct the cause of the Media Gateway
Unreachable alarm, refer to the
“Trunking Gateway Unreachable—Signaling (79)” section on
.
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. To troubleshoot and correct the cause of the Out of Bounds, Memory/Socket Error
alarm, refer to the
“Out of Bounds, Memory/Socket Error—Signaling (80)” section on page 10-139
.
Insufficient Heap Memory—Signaling (81)
The Insufficient Heap Memory alarm (critical) indicates that there is insufficient heap memory. To
troubleshoot and correct the cause of the Insufficient Heap Memory alarm, refer to the
Memory—Signaling (81)” section on page 10-140
Insufficient Shared Memory Pools—Signaling (82)
The Insufficient Shared Memory Pools alarm (critical) indicates that there is insufficient shared memory
pools. To troubleshoot and correct the cause of the Insufficient Shared Memory Pools alarm, refer to the
“Insufficient Shared Memory Pools—Signaling (82)” section on page 10-140
.
Error While Binding to Socket—Signaling (83)
The Error While Binding to Socket alarm (critical) indicates that an error occurred while binding to the
socket. To troubleshoot and correct the cause of the Error While Binding to Socket alarm, refer to the
“Error While Binding to Socket—Signaling (83)” section on page 10-140
Reached Maximum Socket Limit—Signaling (84)
The Reached Maximum Socket Limit alarm (critical) indicates that the BTS 10200 system has reached
the maximum socket limit. To troubleshoot and correct the cause of the Reached Maximum Socket Limit
alarm, refer to the
“Reached Maximum Socket Limit—Signaling (84)” section on page 10-140
.
Initialization Failure—Signaling (85)
The Initialization Failure alarm (critical) indicates that the BTS 10200 system failed to initialize. To
troubleshoot and correct the cause of the Initialization Failure alarm, refer to the
Failure—Signaling (85)” section on page 10-140
.