Avaya H.323 9608 Installation And Management Manual page 80

Troubleshooting
Message
Request Error
Restarting...
Subnet
conflict * to
program
System busy
System Error
Undefined
Error
Updating: DO
NOT UNPLUG THE
phone
Waiting for
LLDP
Wrong Set Type
80 Installing and maintaining Avaya IP Deskphone H.323 9608, 9608G, 9611G, 9621G, and 9641GJanuary 2014
RESOLUTION: Confirm whether the password is correct, then try
registering again, and enter the password accurately.
CAUSE: The gatekeeper does not accept the registration request sent
by the phone as the request is not formatted properly.
RESOLUTION: The phone will automatically attempt to register with
the next gatekeeper on its list. If the problem persists, reboot the
phone.
CAUSE: The phone is in the initial stage of rebooting.
RESOLUTION: Allow the phone boot process to continue.
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
IP address information on page 47, or administer network equipment
to administer the phone appropriately.
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.
CAUSE: The call server has an unspecified problem.
RESOLUTION: Consult your Avaya Media Server administration and
troubleshooting documentation.
CAUSE: The call server has rejected registration for an unspecified
reason.
RESOLUTION: Consult your Avaya Media Server administration and
troubleshooting documentation.
CAUSE: The phone is updating its software image.
RESOLUTION: The phone update process must be continued.
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. For more information, see
Troubleshooting on page 86.
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.
Comments? infodev@avaya.com
Cause/Resolution
Changing
LLDP