Avaya 1600 Series - Installation Error and Status Messages

Installation Error and Status Messages
Issue 1 April 2007 57
Installation Error and Status Messages
The 1600 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 1600 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 2
display only for about 30 seconds, and then the telephone
resets. The most common exception is Extension in Use, which requires manual
intervention.
Table 2: Possible Error and Status Messages During Installation of 1600 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).
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 1600 Series IP
Telephone 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.
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.
1 of 4