![Cisco BTS 10200 Softswitch Скачать руководство пользователя страница 466](http://html.mh-extra.com/html/cisco/bts-10200-softswitch/bts-10200-softswitch_troubleshooting-manual_67550466.webp)
10-98
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 10 Signaling Troubleshooting
Monitoring Signaling Events
Test Report—Signaling (1)
The Test Report event is for testing the signaling event category. The event is informational and no
further action is required.
Invalid Message Received—Signaling (4)
The Invalid Message Received event serves as a warning that an invalid message has been received. The
primary cause of the event is that a signaling adapter has received an invalid message from the specified
endpoint. To correct the primary cause of the event, monitor the associated signaling link to see if there
is an interruption of service on the link. If there is a communication problem, restart the link. Verify that
the version of the protocol used by the device at the endpoint is consistent with the version expected by
the call agent. If there is a mismatch, then either the endpoint or call agent must be re-provisioned.
Database Module Function Call Failure—Signaling (6)
The Database Module Function Call Failure event serves as a warning that a database module function
call has failed. The primary cause of the event is that a signaling adapter has detected an error while
accessing a database interface. To correct the primary cause of the event, restart the associated process
if the database that the adapter attempted to access is not available. If incompatible versions of the
signaling adapter process and the database processes are present on the system, correct the error and
restart the processes.
Socket Failure—Signaling (7)
The Socket Failure alarm (major) indicates that there is a failure in creating/binding to the UDP socket.
To troubleshoot and correct the cause of the Socket Failure alarm, refer to the
Failure—Signaling (7)” section on page 10-130
SIGNALING(172)
MAJOR
SIGNALING(173)
ENUM Server Domain Cannot be Resolved Into Any IP Address —Signaling (173)
CRITICAL
SIGNALING(174)
ENUM Server Unavailable—Signaling (174)
CRITICAL
SIGNALING(175)
ENUM Server Farm Unavailable—Signaling (175)
CRITICAL
SIGNALING(176)
No Resources Available to Launch ENUM Query—Signaling (176)
CRITICAL
SIGNALING(177)
ISDN Unable to Restore D-Channel Into In-Service Active State—Signaling (177)
WARNING
Table 10-2
BTS 10200 Signaling Events (continued)
Event Type
Event Name
Event Severity