Message
Cause/Resolution
Subnet conflict
* to program
CAUSE: The phone is not on the same VLAN subnet as the router.
RESOLUTION: Press star (*) to administer an IP address on the phone. For
information on configuring an IP address, see administer network equipment to
administer the phone appropriately.
System busy
CAUSE: Most likely, the number of IP endpoints on the call server is already at
maximum capacity. Network resource may not be unavailable.
RESOLUTION: The phone attempted to access a network resource such as
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 is properly linked to the network, verify that the addressing is accurate and
that a communication path exists in both directions between the phone 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 phone
CAUSE: The phone is updating its software image.
RESOLUTION: The phone update process must be continued.
Waiting for LLDP
CAUSE: No File Server or Call Server has been administered, so the phone is
expecting to get the missing data through 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.
Wrong Set Type
CAUSE: The call server does not recognize the set type.
RESOLUTION: Ensure the call server is properly administered to register a
compatible phone for the IP address and extension.
Operational errors and status messages
The following table identifies some of the possible operational problems that might be encountered
after successful phone installation. The user guide for a specific phone model also contains
troubleshooting for users having problems with specific IP phone applications. Most of the
problems reported by phone users are LAN-based, where Quality of Service, server
administration, and other issues can impact end-user perception of IP phone performance.
Operational errors and status messages
May 2018
Installing and Administering Avaya J169/J179 IP Phone H.323
191