Previous page Next page

Installation Error and Status Messages

The 9600 Series IP Telephones issue messages in English only. The IP telephones also display messages from the switch, which can issue messages in the local language outside the United States. The 9600 Series IP Telephones issue messages in the currently selected language, or if the telephone is logged off, in the language specified by the LANGSYS parameter value. If English is not the selected language, the telephone displays messages in English only when they are associated with local procedures, for example, MUTE V I E W.

Most of the messages in Table 3 display only for about 30 seconds, and then the telephone resets. The most common exception is Extension in Use, which requires manual intervention.

Table 3:  Possible Error and Status Messages During Installation of 9600 Series IP
Telephones  
Message
Cause/Resolution
802.1X Failure
CAUSE: Incorrect credentials provided for authentication or not provided at all.
RESOLUTION: Follow the display prompts and reenter the 802.1X ID and password.
Address Conflict
CAUSE: The telephone has detected an IP Address conflict.
RESOLUTION: Verify administration to identify duplicate IP Address(es).
Authentication Error
CAUSE: The call server 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.
Bad FileSv Address
CAUSE: The HTTP/HTTPS 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 HTTP/HTTPS server, or administer the telephone locally using the ADDR option. The ADDR option is explained in Chapter 3: Local Administrative Options.
Bad Router?
CAUSE: The telephone cannot find a router based on the information in the DHCP file for GIPADD.
RESOLUTION: Use static addressing to specify a router address, or change administration on DHCP, as indicated in the Avaya one-X Deskphone Edition for 9600 Series IP Telephones Administrator Guide.
Call Error
CAUSE: The user was on a call when the connection to the gatekeeper went down, perhaps due to a network outage or a gatekeeper problem. The telephone attempted to automatically register with the same, or another, gatekeeper, but the responding gatekeeper had no record of the call.
RESOLUTION: Wait for the call to end, and if the telephone does not automatically register, restart the telephone.
Connecting...
CAUSE: The telephone is attempting to establish a TCP connection with the call server. A resource needed to establish the connection might not be available or the 10 second buffer on switch-related actions might have expired.
RESOLUTION: Allow the telephone to continue TCP connect attempts.
Contacting call server...
CAUSE: The telephone has rebooted successfully and is moving on to attempt to register with the call server.
RESOLUTION: Allow the telephone to continue.
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 telephone is attempting to find a DHCP server, and the user is allowed to view IP Addresses.
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.
Discovering...
CAUSE: The 96xx telephone is attempting to find a DHCP server and the user is not allowed to view IP Addresses.
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 “1000Mbps”, “100Mbps” or “10Mbps” message, quickly press the * (asterisk) button.
EEPROM error, repair required
CAUSE: Downloaded application file was not downloaded or saved correctly.
RESOLUTION: The telephone automatically resets and attempts to re-initialize.
Emergency Option
CAUSE: Incompatible emergency option.
RESOLUTION: This should never happen. Contact Avaya.
Extension in Use
Extension in use: <NNNN> Press continue to take over this extension

Login|Continue
CAUSE: The call server detects an extension conflict with an existing set or Softphone.
RESOLUTION: You can force the current telephone to register and thereby disconnect the other user by pressing Continue. When Login is selected instead, the 9600 Series IP Telephone re-prompts for entry of (a different) extension and password.
Finding router...
CAUSE: The telephone is proceeding through boot-up.
RESOLUTION: Allow the telephone to continue.
Gatekeeper Error
CAUSE: The gatekeeper rejects the registration attempt for an unspecified reason.
RESOLUTION: Review gatekeeper/call server administrations, including IP network parameters.
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. Since the 9600 Series IP Telephones are not supported on DEFINITY Release 8.4, you must upgrade to a release that does support these telephones.
Incompatible
CAUSE: This release of the call server does not support the current version of the IP telephone.
RESOLUTION: Upgrade to the current version of Avaya Communication Manager (3.0 or greater) software.
Invalid file
CAUSE: The telephone does not have sufficient room to store the downloaded file.
RESOLUTION: Verify the proper filename is administered in the script file, and that the proper application file is located in the appropriate location on the HTTP/HTTPS server.
IP Address Error
CAUSE: The gatekeeper reports an invalid IP Address.
RESOLUTION: This should never happen. Contact Avaya.
License Error
CAUSE: The call server does not support IP telephony.
RESOLUTION: Contact Avaya to upgrade your license.
Limit Error
CAUSE: The call server has reached its limit of IP stations.
RESOLUTION: Unregister telephones not in use, or contact Avaya to upgrade your license.
NAPT Error
CAUSE: A device between the telephone and the call server is invoking Network Address Port Translation, which the 9600 Series IP Telephones do not support.
RESOLUTION: Contact the System Administrator to remove or re-administer the device.
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.
Packet Error
CAUSE: Protocol timeout error.
RESOLUTION: Reenter the correct extension and password. If the condition persists, contact the System Administrator.
Password Error
CAUSE: The call server does not recognize the password entered and displays the Login Error screen.
RESOLUTION: Confirm the password is correct, then try registration again, taking particular care to enter the password accurately.
Request Error
CAUSE: The gatekeeper believes the telephone’s registration request is improperly formatted.
RESOLUTION: The telephone will automatically attempt to register with the next gatekeeper on its list. If the problem persists, reboot the telephone.
Restarting...
CAUSE: The telephone is in the initial stage of rebooting.
RESOLUTION: Allow the telephone to continue.
Subnet conflict * to program
CAUSE: The telephone is not on the same VLAN subnet as the router.
RESOLUTION: Press * to administer an IP Address on the telephone using Static Addressing Installation, or administer network equipment to administer the telephone appropriately.
System busy
CAUSE: Most likely, the number of IP endpoints on the call server is already at maximum, Less likely, network resource is unavailable.
RESOLUTION: The telephone was attempting to access a network resource (DHCP server, HTTP server, or the call server) 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 call server has an unspecified problem.
RESOLUTION: Consult your Avaya Media Server administration and troubleshooting documentation.
Undefined Error
CAUSE: The call server has rejected registration for an unspecified reason.
RESOLUTION: Consult your Avaya Media Server administration and troubleshooting documentation.
Updating: DO NOT UNPLUG THE TELEPHONE
CAUSE: The telephone is updating its software image.
RESOLUTION: Allow the telephone to continue.
Waiting for LLDP
CAUSE: No File Server and/or Call Server has been administered, so the telephone is expecting to get the missing data via LLDP.
RESOLUTION: Administer the missing data by one of the following methods: statically, dynamically in DHCP, in the 46xxsettings file (for Call Server addresses), or by LLDP. For more information, see LLDP Troubleshooting.
Wrong Set Type
CAUSE: The call server does not recognize the set type.
RESOLUTION: Ensure the call server is properly administered to expect the appropriate telephone for the IP Address and extension.

Previous page Next page