Cisco 7925G - Unified Wireless IP Phone VoIP - Logging Information for Troubleshooting

10-17
Cisco Unified Wireless IP Phone 7925G Administration Guide for Cisco Unified Communications Manager 7.0(1)
OL-15984-01
Chapter 10 Troubleshooting the Cisco Unified Wireless IP Phone 7925G
General Troubleshooting Information
Related Topics
• Logging Information for Troubleshooting, page 10-17
• General Troubleshooting Information, page 10-14
Logging Information for Troubleshooting
The following options can help you gather troubleshooting information:
• Using a System Log Server, page 10-18
• Using the Trace Logs on the Unified IP Phone, page 10-18
Battery life is shorter than specified An unstable RF environment can cause the phone to remain in active mode
because it is constantly seeking an AP. This reduces the battery life
considerably. When leaving an area of coverage, shut down the phone.
Higher phone transmit power can affect battery life.
To maximize idle time on the phone and conserve battery life, you need to
optimize the registration time so the phone can go into power save mode more
often.
Phone call cannot be established The phone does not have a DHCP IP address, is unable to register to Cisco
Unified Communications Manager, and shows a Configuring IP or
Registering message.
Verify the following:
1. The Cisco Unified Communications Manager service is running on the
Cisco Unified Communications Manager server.
2. Both phones are registered to the same Cisco Unified Communications
Manager.
3. Audio server debug and capture logs are enabled for both phones. If
needed, enable Java debug.
Call established with the iLBC protocol does
not show that the iLBC codec is being used
Call statistics display does not show iLBC as the receiver/sender codec.
1. Check the following using the Cisco Unified Communications Manager
administration pages:
– 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.
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.
Table 10-3 Cisco Unified Wireless IP Phone Troubleshooting Tips (continued)
Summary Explanation