![Cisco BTS 10200 Softswitch Скачать руководство пользователя страница 481](http://html.mh-extra.com/html/cisco/bts-10200-softswitch/bts-10200-softswitch_troubleshooting-manual_67550481.webp)
10-113
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 10 Signaling Troubleshooting
Monitoring Signaling Events
Codec Negotiation Failed—Signaling (100)
The Codec Negotiation Failed alarm (minor) indicates that the codec negotiation has failed. To
troubleshoot and correct the cause of the Codec Negotiation Failed alarm, refer to the
Negotiation Failed—Signaling (100)” section on page 10-144
Per Call Security Violation—Signaling (101)
The Per Call Security Violation alarm (minor) indicates that a call security violation has occurred. To
troubleshoot and correct the cause of the Per Call Security Violation alarm, refer to the
Violation—Signaling (101)” section on page 10-144
.
H323 Network Congested—Signaling (102)
The H323 Network Congested alarm indicates (minor) that the H323 application process has depleted
its resources and no more calls can be completed. To troubleshoot and correct the cause of the H323
Network Congested alarm, refer to the
“H323 Network Congested—Signaling (102)” section on
Aggregation Connection Down—Signaling (103)
The Aggregation Connection Down alarm (major) indicates that the aggregation (AGGR) TCP
connection is down. To troubleshoot and correct the cause of the Aggregation Connection Down alarm,
refer to the
“Aggregation Connection Down—Signaling (103)” section on page 10-144
.
Aggregation Unable To Establish Connection—Signaling (104)
The Aggregation Unable To Establish Connection event functions as an informational alert that the
AGGR is unable to establish a connection. The primary cause of the event is that the TCP connection
failed to establish. To correct the primary cause of the event, check the IP Connectivity of CA and
CMTS.
Aggregation Gate Set Failed—Signaling (105)
The Aggregation Gate Set Failed event functions as an informational alert that the AGGR gate set failed.
The primary cause of the event is that the gate set acknowledgement never came from the CMTS. The
event is informational and no further action is required.