| Error Message |
Cause/Resolution |
| During Installation |
|
| Checksum error |
CAUSE: Downloaded application file was not downloaded or saved correctly. RESOLUTION: The telephone automatically resets and attempts to re-initialize. |
| DHCP: CONFLICT
* to program |
CAUSE: At least one of the IP address offered by the DHCP server conflicts with another address. RESOLUTION: Review DHCP server administration to identify duplicate IP address(es) |
| Discovering... |
CAUSE: The telephone is seeking a gatekeeper on the media server, using its administered gatekeeper list. RESOLUTION: Wait for a valid registration to occur, or press # to interrupt the search and re-initialize manual or DHCP/TFTP procedures. |
| File too large Cannot save file |
CAUSE: The telephone does not have sufficient room to store the downloaded file. RESOLUTION: Verify the proper filename is administered in the TFTP script file, and that the proper application file is located in the appropriate location on the TFTP server. |
| Gateway Error |
CAUSE: DEFINITY Release 8.4 does not have an H.323 station extension for this telephone. RESOLUTION: On the station administration screen, ensure the DCP set being aliased for this IP telephone has an H.323 station extension administered, in accordance with switch administration instructions. |
| Hardware failure |
CAUSE: Hardware failure prevented downloading of application file, RESOLUTION: Replace telephone. |
| IP Address in use by another |
CAUSE: The telephone has detected an IP address conflict. RESOLUTION: Verify administration to identify duplicate IP address(es). |
| No Ethernet |
CAUSE: When first plugged in, the IP Telephone is unable to communicate with the Ethernet. RESOLUTION: Verify the connection to the Ethernet jack, verify the jack is Category 5, etc. Note that if the telephone is attached to a 30A switched hub, upon loss of Ethernet connectivity, the usual “No Ethernet” message is not displayed. |
| No file server address |
CAUSE: The TFTP server IP address in the IP telephone’s memory is all zeroes. RESOLUTION: Depending on the specific requirements of your network, this may not be an error. If appropriate, either administer the DHCP server with the proper address of the TFTP server, or administer the telephone locally using the ADDR option as detailed in the 4600 Series IP Telephone Installation Guide. |
| System busy |
CAUSE: Most likely, the number of IP endpoints on the Avaya media server is already at maximum, Less likely, network resource is unavailable. RESOLUTION: The telephone was attempting to access a network resource (DHCP server, TFTP server, or the Avaya media server) and was not successful. The resource being called upon should be checked for its availability. If it appears operational and properly linked to the network, verify addressing is accurate and a communication path exists in both directions between the telephone and the resource. |
| System Error |
CAUSE: The Avaya media server has an unspecified problem. RESOLUTION: Consult your Avaya media server administration and troubleshooting documentation. |
| During Registration |
| Extension error |
CAUSE: An invalid Avaya media server Registration extension has been entered. RESOLUTION: Re-enter the extension if mis-entered initially. If appropriate, verify proper extension with respect to switch administration. |
| Extension in use |
CAUSE: The specified extension is already in use, according to the Avaya media server. RESOLUTION: Wait a few minutes, and try again. This will work for the case when the extension is correctly administered, but service was interrupted and the Avaya media server is not yet aware of that fact. Otherwise, verify proper extension with respect to switch administration. |
| Failed to set phone IP address |
CAUSE: The 4600 Series Telephone was originally installed on one switch with Static Addressing, and has subsequently been installed on another switch with an active DHCP server assigning dynamic IP addresses. RESOLUTION: Reset the telephone. |
| Incompatible |
CAUSE: This release of the Avaya media server does not support the current version of the IP Telephone. RESOLUTION: Upgrade to the current version of Avaya media server software. |
| Message light blinks on and off, and the telephone did not complete registration. |
CAUSE: The telephone has a hardware fault. RESOLUTION: Replace the telephone. |
| Password Error |
CAUSE: An invalid PBX Registration password has been entered. RESOLUTION: Re-enter the password if mis-entered initially. If appropriate, verify proper password with respect to switch administration. |
| Resource Error |
CAUSE: The Avaya media server rejects the registration request. RESOLUTION: Verify your Avaya media server administration to ensure the telephone’s proper IP address, extension, and password are being used. |
| Timeout Error |
CAUSE: Protocol timeout error. RESOLUTION: Retry. If failure continues, check network congestion, addresses, etc. to identify cause of timeout. |
| Undefined Error |
CAUSE: An error has occurred without an identifiable cause. RESOLUTION: Conduct self-test, restart the telephone, and if no other cause becomes evident, replace the telephone. |
| Wrong Set Type |
CAUSE: The Avaya media server does not recognize the set type. RESOLUTION: Ensure the Avaya media server is properly administered to expect the appropriate telephones for the IP address and extension. |
