User guide

Installation Error and Status Messages
Issue 4 February 2010 65
Gatekeeper
Error
CAUSE: The gatekeeper rejects the registration attempt for an
unspecified reason.
RESOLUTION: Review gatekeeper/call server administrations,
including IP network parameters.
Gateway Error CAUSE: DEFINITY Release 8.4 does not have an H.323 station
extension for this telephone.
RESOLUTION: On the station administration screen, ensure the DCP
set being aliased for this IP telephone has an H.323 station extension
administered, in accordance with switch administration instructions.
Since the 1600 Series IP Telephones are not supported on DEFINITY
Release 8.4, you must upgrade to a release that does support these
telephones.
Incompatible CAUSE: This release of the call server does not support the current
version of the IP telephone.
RESOLUTION: Upgrade to the current version of Avaya Aura
Communication Manager (3.1 or later) software.
Invalid file CAUSE: The telephone does not have sufficient room to store the
downloaded file.
RESOLUTION: Verify the proper filename is administered in the script
file, and that the proper application file is located in the appropriate
location on the HTTP/HTTPS server.
IP Address
Error
CAUSE: The gatekeeper reports an invalid IP address.
RESOLUTION: This should never happen. Contact Avaya.
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: Unregister telephones not in use, or contact Avaya to
upgrade your license.
NAPT Error CAUSE: A device between the telephone and the call server is invoking
Network Address Port Translation, which the 1600 Series IP Telephones
do not support.
RESOLUTION: Contact the System Administrator to remove or
re-administer the device.
Network
connectivity
has been lost.
Trying to re-
establish...
CAUSE: The telephone has detected a loss of signal on the Ethernet
interface lasting longer than about one second.
RESOLUTION: Check power and cabling.
No Ethernet CAUSE: When first plugged in, the IP telephone is unable to
communicate with the Ethernet.
RESOLUTION: Verify the connection to the Ethernet jack, verify the jack
is Category 5, verify power is applied on the LAN to that jack, etc.
Table 2: Possible Error and Status Messages During Installation of 1600 Series IP
Telephones (continued)
Message Cause/Resolution
3 of 4