266
VoIP Debugging
Software Configuration Guide, Revision 1.03
Reply from 172.16.40.122: Time <10ms
Reply from 172.16.40.122: Time <10ms
27.3 Warning
Enabling some or all debug monitors may degrade system performance (IP routing, call signaling).
To avoid inadvertent permanent system performance degradation make sure all monitors are
switched off once the configuration is debugged and running.
27.4 Debugging Task List
Depending on problem that has occurred one or more of the following debugging tasks should be
performed. First verify IP and CS connectivity. The next three tasks describe the debugging of ISDN
and VoIP protocols. The session control data task describes debugging of the data between the ISDN
and VoIP protocols, and in the voice over IP data task it is explained how to debug tones and codecs.
Finally check event logs, which could help you to find out the cause of a problem.
•
Verify IP Connectivity
•
Verify Circuit Switch Connectivity
•
Debug ISDN Data (Advanced)
•
Debug H.323 Data (Advanced)
•
Debug ISoIP Data (Advanced)
•
Debug Session Control Data (Advanced)
•
Debug Voice Over IP Data (Advanced)
•
Check Event Logs
27.5 Verify IP Connectivity
With the following command you can verify that an IP packet can be sent to and received from the
destination host.
Procedure
Test connectivity by verifying IP accessibility of hosts
Mode
Administrator execution
Command
Purpose
Step 1
node
#ping
ipaddress
[
number-of-packets
]
[timeout
seconds
]
Verify whether an IP host is reachable
or not
Example: Verify IP Connectivity
The following example shows how to test the connectivity to a remote host by verifying the
accessibility by the ping command. Furthermore it shows the output if host 192.195.23.1 is not, and
host 172.16.40.122 is reachable.
SN#
ping 192.195.23.1 10 timeout 5
Sending 10 ICMP echo requests to 192.195.23.1, timeout is 5 seconds:
% No route to host
SN#
SN#
ping 172.16.40.122
Sending 5 ICMP echo requests to 172.16.40.122, timeout is 1 seconds:
Reply from 172.16.40.122: Time <10ms