Logging Information For Troubleshooting - Cisco 7925G - Unified Wireless IP Phone VoIP Administration Manual

For cisco unified communications manager 7.0(1)
Hide thumbs Also See for 7925G - Unified Wireless IP Phone VoIP:
Table of Contents

Advertisement

Chapter 10
Troubleshooting the Cisco Unified Wireless IP Phone 7925G
Table 10-3
Cisco Unified Wireless IP Phone Troubleshooting Tips (continued)
Summary
Battery life is shorter than specified
Phone call cannot be established
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:
Cisco Unified Wireless IP Phone 7925G Administration Guide for Cisco Unified Communications Manager 7.0(1)
OL-15984-01
Explanation
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.
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.
Both phones are registered to the same Cisco Unified Communications
2.
Manager.
Audio server debug and capture logs are enabled for both phones. If
3.
needed, enable Java debug.
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.
Enable audio server debug and capture logs from both phones. If needed,
3.
enable Java debug.
Logging Information for Troubleshooting, page 10-17
General Troubleshooting Information, page 10-14
Using a System Log Server, page 10-18
Using the Trace Logs on the Unified IP Phone, page 10-18
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
10-17

Advertisement

Table of Contents
loading

Table of Contents