General Troubleshooting Information
The following table provides general troubleshooting information for the wireless IP phone.
Summary |
Explanation |
---|---|
Phone is resetting |
The phone resets when it loses contact with the CiscoUnifiedCommunications Manager software. This lost connection can be due to any network connectivity disruption, including access point problems, switch outages, and switch reboots. See Phone Reset Problems. |
Time on the phone is incorrect |
Sometimes the time or date on the phone is incorrect. The phone gets its time and date when it registers with Cisco Unified Communications Manager. Power cycle the phone to reset the time or date. The time shows in either 12 hour or 24 hour format. |
Phone firmware downgrades |
After applying a Cisco Unified Communications Manager upgrade or patch, that is older than the current phone firmware, the phones could automatically downgrade to the load contained in the patch. Check the phone default image in the TFTP folder to fix this problem. |
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:
|
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.
|
For additional troubleshooting information, see the Cisco Unified Communications Manager Troubleshooting Guide.