![Cisco BTS 10200 Softswitch Скачать руководство пользователя страница 186](http://html.mh-extra.com/html/cisco/bts-10200-softswitch/bts-10200-softswitch_troubleshooting-manual_67550186.webp)
4-36
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 4 Call Processing Troubleshooting
Troubleshooting Call Processing Alarms
Step 7
Check statistics for ethernet interface(s) on the call agent side while looking for any abnormal
queue/input/output errors/collisions. For example, to check stats on bge0 interface:
# netstat -i -I bge0
Ipkts Ierrs Opkts Oerrs Collis Queue
Note
The packets queued (Queue) that cannot be transmitted should be 0. If not, it is possible that a cable or
ethernet interface is defective.
Note
The input errors (Ierrs) and the output errors (Oerrs) should be close to 0. High input errors could
indicate that the network is saturated, host overload, or physical network problem. High output errors
could indicate a saturated local network or a bad physical connection.
Step 8
Check statistics for ethernet interface(s) on the switch side. Look for abnormal input/output errors, CRC,
frame errors. For a description of the output of “show interface fast ethernet”, refer to:
http://www.cisco.com/en/US/customer/docs/ios/12_2/interface/command/reference/irfshoin.html
Step 9
Paste the output of “show interfaces” to the Cisco output interpreter for further analysis of the interfaces.
https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl
Step 10
Check the physical cable, the cable connectors, and the cable connections.
Release Cause 25 Exchange Routing Error Received—Call Processing (38)
The Release Cause 25 Exchange Routing Error Received alarm (minor) indicates that a release with
cause number 25 occurred because an exchange routing error was received. The primary cause of the
alarm is that a REL message with cause number 25 was received. To correct the primary cause of the
alarm, log and map the cause. Refer to
“Call Authorization Failure—Call Processing (31)” section on
for additional troubleshooting information.
INVITE Message From Unauthorized Call Agent—Call Processing (41)
The INVITE Message From Unauthorized Call Agent alarm (minor) indicates that a INVITE message
was received from an unauthorized CA. The primary cause of the alarm is that the Call-Agent Table is
not configured properly. To correct the primary cause of the alarm, reconfigure the Call-Agent table to
have the authorized CA listed. The secondary cause of the alarm is that a potential intrusion occurred if
the Network-ID mismatch is from the local-network. To correct the secondary cause of the alarm,
configure the network to block this unauthorized Network-ID.