Logging Information For Troubleshooting; Using A System Log Server; Using The Trace Logs On The Unified Ip Phone - Cisco 7921G - Unified Wireless IP Phone VoIP Administration Manual

Chapter 10 Troubleshooting the Cisco Unified Wireless IP Phone 7921G
Table 10-3 Cisco Unified Wireless IP Phone Troubleshooting Tips (continued)
Summary
Call established with the iLBC protocol does
not show that the iLBC codec is being used
Related Topics
•
•

Logging Information for Troubleshooting

The following options can help you gather troubleshooting information:
•
•

Using a System Log Server

To gather information about problems with the wired network that can cause roaming delays or no
connectivity, set up a system log server. Enable "syslog" on the network switches and access points that
is logged to the system log server. Also enable Network Time Protocol (NTP) so that all access points
and switches use the same times.
For information about setting up a system log server, see
page

Using the Trace Logs on the Unified IP Phone

When you are experiencing problems with registering with Cisco Unified Communications Manager, or
call connections, you can use this function to trace the path of a packet from the phone to
Cisco Unified Communications Manager. The result shows the number of hops and the IP address of
each hop to reach the Cisco Unified Communications Manager server. You can use this information to
check connectivity between the phone, Cisco Unified Communications Manager servers and gateways
during a call.
Cisco Unified Wireless IP Phone 7921G Administration Guide for Cisco Unified Communications Manager Release 7.0
OL-15985-01
Explanation
Call statistics display does not show iLBC as the receiver/sender codec.
Check the following using the Cisco Unified Communications Manager
1.
administration pages:
2. Capture a sniffer trace between the phone and Cisco Unified
Communications Manager and verify that SCCP messages,
OpenReceiveChannel, and StationMediaTransmit messages have media
payload type value equal to 86. If so, the problem is with the phone;
otherwise the problem is with the Cisco Unified Communications
Manager configuration.
3. Enable audio server debug and capture logs from both phones. If needed,
enable Java debug.
Logging Information for Troubleshooting, page 10-17
General Troubleshooting Information, page 10-14
Using a System Log Server, page 10-17
Using the Trace Logs on the Unified IP Phone, page 10-17
4-29.
Both phones are in the iLBC device pool.
–
The iLBC device pool is configured with the iLBC region.
–
The iLBC region is configured with the iLBC codec.
–
General Troubleshooting Information
"Configuring Trace Settings" section on
10-17