802.1X Failure

CAUSE: Incorrect credentials provided for authentication or not provided at all.

Bad Router

CAUSE: The telephone cannot find a router based on the information in the DHCP file for GIPADD.

RESOLUTION: Change administration on DHCP, as indicated in the 4600 Series IP Telephone LAN Administrator Guide.

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).

Discover aaa.bbb.ccc.ddd

CAUSE: The 46xx telephone is attempting to discover (and register with) the gatekeeper at IP Address aaa.bbb.ccc.ddd.

RESOLUTION: If this message appears for more than a few seconds, especially if the IP Address keeps changing, the telephone is unable to contact the gatekeeper. Have the LAN Administrator verify network connectivity between the telephone and the gatekeeper. Alternately, revise the gatekeeper addresses in the DHCP/TFTP files in accordance with the 4600 Series IP Telephone LAN Administrator Guide to point to different gatekeepers.

Discovering...

CAUSE: The 46xx telephone is attempting to find a DHCP server.

RESOLUTION: If this message appears for more than a few seconds, verify with the LAN Administrator that a DHCP server is appropriately administered on the network. If there is not supposed to be a DHCP server, you must “break into” the Discovering process and use static addressing. See Static Addressing Installation. To break into the Discovering process, press the # button, and when you see the “100Mbs” or “10Mbs” message, quickly press the * (asterisk) button.

Extension Error

CAUSE: The PBX does not recognize the extension entered.

RESOLUTION: Confirm the extension is correct and is correctly administered on the switch. Then try registration again, taking particular care to enter the extension accurately.

Extension in Use

CAUSE: The PBX detects an extension conflict with an existing set or Softphone.

RESOLUTION: You will be told if the telephone using the same extension is on a call or not. Regardless, you can proceed to take over the extension or to login using a different extension. Telephones with large displays, such as the 4610SW or 4625SW, and Release 2.7 software provide detailed messages and specially labeled softkeys to guide you through either alternative. If the telephone has a two-line display, or does not support Release 2.7, you can either press the # key twice to take over the extension and log the other telephone off or you can press #, then * to enter a different extension.

Extension/Password Error (SIP only)

CAUSE: The extension and password do not match what is administered on the Registration Server.

RESOLUTION: Enter another extension and/or password.

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.

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.

Incompatible

CAUSE: This release of DEFINITY does not support the current version of the IP telephone.

RESOLUTION: Upgrade to the current version of Avaya Communication Manager software.

IP address in use by another

CAUSE: The telephone has detected an IP Address conflict.

RESOLUTION: Verify administration to identify duplicate IP Address(es).

IP Address Error

CAUSE: Unnamed registration attempted but unnamed registration (UNR) is not enabled on Avaya Communication Manager for IP Telephones.

RESOLUTION: Change CM settings to enable.

NAPT Error

CAUSE: A device between the telephone and the call server is invoking Network Address Port Translation, which the 4600 Series IP Telephones do not support.

RESOLUTION: Contact the System Administrator to remove or re-administer the device.

No Call Server Address - Resetting

CAUSE: The system parameter MCIPADD does not contain at least one non-zero IP Address or DNS Name, causing the telephone to reset.

RESOLUTION: Add the IP Address(es) using static addressing (manual telephone setting), updating the settings file, or normally through DHCP administration.

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, verify power is applied on the LAN to that jack, 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. The ADDR option is explained in Chapter 3: Local Administrative Options.

No proxy found (SIP only)

CAUSE: There is a problem with the SIP registration server and proxy server list.

RESOLUTION: Review the server administration to ensure that the correct addresses are specified. Verify the proper operation of the registration server(s) and the intervening network.

No Socket

CAUSE: The telephone has registered with the call server, but network problems have prevented the telephone from opening a TCP socket. Note: This message only occurs on older software versions; telephones with newer software automatically reset.

RESOLUTION: Press the # button to have the telephone reset, and contact the System Administrator to report the network problem.

Password Error

CAUSE: The PBX does not recognize the password entered.

RESOLUTION: Confirm the password is correct, then try registration again, taking particular care to enter the password accurately.

(SIP only)

CAUSE: It is normal for this message to appear for a short time period.

RESOLUTION: If this message appears for an extended period of time, the telephone is unable to register. Verify the proper operation of the registration server(s) and the intervening network.

Registration Failed

(SIP only)

CAUSE: The registration process failed.

RESOLUTION: Verify the proper administration and operation of the registration server(s) and the intervening network.

System busy

CAUSE: Most likely, the number of IP endpoints on the PBX is already at maximum, Less likely, network resource is unavailable.

RESOLUTION: The telephone was attempting to access a network resource (DHCP server, TFTP server, HTTP server, or the PBX) and was not successful. Check the resource being called upon for its availability. If the resource appears operational and properly linked to the network, verify that addressing is accurate and that a communication path exists in both directions between the telephone and the resource.

System Error

CAUSE: The PBX has an unspecified problem.

RESOLUTION: Consult your Avaya Media Server administration and troubleshooting documentation.

Timeout Error

CAUSE: Protocol timeout error.

RESOLUTION: Reenter the correct extension and password. If the condition persists, contact the System Administrator.

Unauthorized (SIP only)

CAUSE: The registration server does not recognize the extension and password.

RESOLUTION: Reenter the extension and password. If the condition persists, contact the System Administrator for assistance.

Undefined Error

CAUSE: The PBX has rejected registration for an unspecified reason.

RESOLUTION: Consult your Avaya Media Server administration and troubleshooting documentation.

Resource Error

CAUSE: The PBX rejects the registration request.

RESOLUTION: Verify administration to ensure the telephone’s proper IP Address, extension, and password are being used.

Wrong Set Type

CAUSE: The PBX does not recognize the set type.

RESOLUTION: Ensure the PBX is properly administered to expect the appropriate telephone for the IP Address and extension.