Installation Error And Status Messages - Avaya 1600 Series Installation And Maintenance Manual

Installation Error and Status Messages

The 1600 Series IP Telephones issue messages in English only. The IP deskphones 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 deskphone is logged off, in the language specified by the LANGSYS
parameter value. If English is not the selected language, the deskphone displays messages in
English only when they are associated with local procedures, for example, MUTE V I E W.
Most of the messages in
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
Deskphones
Message
802.1X Failure
Address
Conflict
Bad FileSv
Address
Bad Router?
Call Error
Contacting call
server...
http://ArtTel.ru
Table 2 display only for about 30 seconds, and then the deskphone
Cause/Resolution
CAUSE: Incorrect credentials provided for authentication or not
provided at all.
RESOLUTION: Follow the display prompts and reenter the 802.1X ID
and password.
CAUSE: The deskphone has detected an IP address conflict.
RESOLUTION: Verify administration to identify duplicate IP
address(es).
CAUSE: The HTTP/HTTPS server IP address in the IP deskphone'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 deskphone locally using the ADDR option. The ADDR
option is explained in Chapter 3: Local Administrative
CAUSE: The deskphone 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
Deskphone Administrator Guide.
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 deskphone 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 deskphone does not
automatically register, restart the deskphone.
CAUSE: The deskphone has rebooted successfully and is moving on to
attempt to register with the call server.
RESOLUTION: Allow the deskphone to continue.
Installation Error and Status Messages
Options.
Issue 5 April 2014
1 of 4
63