|
|
|
|
| Troubleshooting |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Message |
| Description |
| Action |
|
| Checking DHCP IP |
| The handset is retrieving DHCP |
| None. This is informational only. |
|
|
|
| information from the DHCP server. |
|
|
|
| CRC Code Error |
| The software which has been TFTP |
| Try the download again; it is possible the |
|
|
|
| downloaded has a bad redundancy |
| software was corrupted during download. If |
|
|
|
| code check. |
| the error repeats, check that the download |
|
|
|
|
|
| image on the TFTP server is not corrupted. |
|
| Code Mismatch! |
| The software loaded into the |
| Verify the License option value is correct. |
|
|
|
| handset is incorrect for this model |
| Replace the software image on the TFTP |
|
|
|
| handset. |
| server with software that is correct for the |
|
|
|
|
|
| handset model. |
|
| DCA Timeout |
| The handset has detected a fault |
| Turn the handset off, then on again. If error |
|
|
|
| for which it cannot recover, possibly |
| persists, contact Polycom Technical |
|
|
|
| due to a failure to acquire any |
| Support and report the error. |
|
|
|
| network. |
|
|
|
| DHCP Error | DHCP Error 1. |
| The handset cannot locate a DHCP server. |
| |
|
|
|
|
| It will try every four seconds until a server |
|
|
|
|
|
| is located. |
|
|
|
| DHCP Error 2. |
| The handset has not received a response |
|
|
|
|
|
| from the server for a request to an IP |
|
|
|
|
|
| address. It will retry until a server is found. |
|
|
|
| DHCP Error 3. |
| The server refuses to lease the handset an |
|
|
|
|
|
| IP address. It will keep trying. |
|
|
|
| DHCP Error 4. |
| The server offered the handset a lease that |
|
|
|
|
|
| is too short. The minimum lease time is 10 |
|
|
|
|
|
| minutes but Polycom recommends at least |
|
|
|
|
|
|
| |
|
|
|
|
| handset will stop trying. Reconfigure the |
|
|
|
|
|
| server and power cycle the handset. |
|
|
|
| DHCP Error 5. |
| Failure during WEP Key rotation process |
|
|
|
|
|
| (proprietary feature). |
|
| DHCP Lease Exp |
| y…y = DHCP server IP address. |
| The handset failed to renew its DHCP |
|
| yyy.yyy.yyy.yyy |
| DHCP is not responding to renewal |
| lease, either because the DHCP server is |
|
|
|
|
| not running, or because the configuration |
| |
|
|
| attempts . |
|
| |
|
|
|
| has been changed by the administrator. |
| |
|
|
|
|
|
| |
|
|
|
|
| The handset will attempt to negotiate a |
|
|
|
|
|
| new lease, which will either work, or it will |
|
|
|
|
|
| change to one of the above DHCP errors |
|
|
|
|
|
| (1 through 4). |
|
| DHCP NACK error |
| y…y = DHCP server IP address. |
| The DHCP lease currently in use by the |
|
| yyy.yyy.yyy.yyy |
| DHCP server explicitly refused |
| handset is no longer valid, which forces the |
|
|
|
| renewal. |
| handset to restart. This problem should |
|
|
|
|
|
| resolve itself on the restart. If it does not, |
|
|
|
|
|
| the problem is in the DHCP server. |
|
| DL Not On Sector |
| Handset software download files |
| Obtain new software per Software |
|
|
|
| are incorrect or corrupted. |
| Maintenance. |
|
PN: | 91 |
