You will often need additional information about the state of the network, such as router and switch port statistics or router access control lists. You can get this information by directly logging into the IP network or by using a protocol analyzer to monitor traffic.
Several commands that are helpful in troubleshooting IP Telephony problems are listed in the table along with their usage.
Table 1: Troubleshooting commands and description
Command |
Description |
list trace station |
This command traces the behavior of a particular station. It shows off-hook status, call setup and teardown messages, call routing, and call performance (for IP sets only). Every 10 seconds it displays packet loss and jitter statistics for the previous 10 seconds to assist in voice-quality troubleshooting or calls that fail to set up properly. |
list trace tac |
This command operates similar to list trace station, but it operates on trunks. In addition to call setup, teardown, and routing, it also lists voice-quality statistics in 10-second increments. This is useful for troubleshooting call routing problems or voice-quality problems across IP trunks. |
list trace ras |
Using this command, an administrator can watch the state of the RAS messages that Communication Manager is processing. This can either be limited to a single station or expanded to the whole system. It shows registration, keep alive, and unregistration requests. This is useful when IP Telephones are rebooting spontaneously or fail to register. |
status station |
This command shows a snapshot of the state of an individual station. It lists registration status, the procr and media processor or IP endpoint that is connected to an IP station, and lists 10 seconds of voice-quality (packet loss and jitter) information. |
status trunk |
This command shows a snapshot of the state of an individual trunk. It lists the far-end procr and media processor or IP endpoint that is connected to an IP trunk, and lists 10 seconds of voice-quality (packet loss and jitter) information. |
