Message
Cause/Resolution
supported on DEFINITY Release 8.4, you must upgrade to a release that
supports these phones.
Incompatible
CAUSE: This release of the call server does not support the current version of
the IP phone.
RESOLUTION: Upgrade to the current version of Communication Manager (3.0
or greater) software.
Invalid file
CAUSE: The phone does not have sufficient room to store the downloaded file.
RESOLUTION: Verify that the proper filename is administered in the script file,
and the correct application file is located in the appropriate location on the HTTP
or HTTPS server.
IP address Error
CAUSE: The gatekeeper reports an invalid IP address.
RESOLUTION: This must not happen. Contact Avaya support.
License Error
CAUSE: The call server does not support IP telephony.
RESOLUTION: Contact Avaya to upgrade your license.
Limit Error
CAUSE: The call server has reached its limit of IP stations.
RESOLUTION: Un-register phones that are not in use, or contact Avaya to
upgrade your license.
NAPT Error
CAUSE: A device between the phone and the call server is invoking Network
address Port Translation (NAPT), which the phone do not support.
RESOLUTION: Contact the System Administrator to remove or re-administer the
device.
No Ethernet
CAUSE: When first plugged in, the IP phone is unable to communicate with the
Ethernet.
RESOLUTION: Verify the connection to the Ethernet jack, verify if the jack is
Category 5, verify if power is applied on the LAN to that jack.
Packet Error
CAUSE: Protocol timeout error.
RESOLUTION: Reenter the correct extension and password. If the condition
persists, contact the system administrator.
Password Error
CAUSE: The call server does not recognize the password entered and displays
the
Login Error
screen.
RESOLUTION: Confirm whether the password is correct, then try registering
again, and enter the password accurately.
Request Error
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.
Restarting...
CAUSE: The phone is in the initial stage of rebooting.
RESOLUTION: Allow the phone boot process to continue.
Table continues…
Troubleshooting
May 2018
Installing and Administering Avaya J169/J179 IP Phone H.323
190