Avaya B189 - Installation Error and Status Messages

Installation error and status messages
Avaya B189 Conference IP Phones display messages in the currently selected language or in
the language specified by the LANGSYS parameter value, if the phone is logged off. If English
is not the selected language, the phone displays messages in English only when the message
are associated with local procedures, for example, MUTE VIEW.
The phone displays most of the messages for only about 30 seconds, and then the phone is
reset. The most common exception is Extension in Use, display more than 30 seconds and
which remains until you perform any further action on the phone.
Table 4: Possible error and status messages during installation of B189 phones
Message Cause/Resolution
802.1X Failure
CAUSE: Incorrect credentials provided for authentication or
credentials not provided at all.
RESOLUTION: Follow the display prompts and reenter the 802.1X ID
and password.
IPv4 or IPv6
address
Conflict
CAUSE: The phone has detected an IP address conflict.
RESOLUTION: Verify administration settings to identify duplicate IP
addresses.
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, and enter the
extension accurately.
Bad FileSv
address
CAUSE: The HTTP/HTTPS server IP address in the IP phone’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 phone locally using the ADDR option. For details on
the ADDR option, see
Using Local Administrative (Craft) Options on
page 25.
Bad Router?
CAUSE: The phone 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.
For deails, seeAdministering Avaya B189 Conference IP Phone.
Call Error
CAUSE: The user was on a call when the connection to the
gatekeeper went down due to a network outage or a gatekeeper
problem. The phone attempted to automatically register with the same
or another gatekeeper, but the responding gatekeeper had no record
of the call.
Installation error and status messages
Installing and maintaining Avaya B189 Conference IP Phone January 2014 43