Avaya 4600 Series Installation Manual page 92

Troubleshooting Guidelines
Table 3: Possible Error and Status Messages During Installation of 4600 Series IP
Telephones (continued)
Message
Hardware
failure
Incompatible
IP address in
use by another
IP Address
Error
NAPT Error
No Call Server
Address -
Resetting
No Ethernet
No file server
address
92 4600 Series IP Telephone Installation Guide
Cause/Resolution
CAUSE: Hardware failure prevented downloading of application file.
RESOLUTION: Replace telephone.
CAUSE: This release of DEFINITY does not support the current version
of the IP telephone.
RESOLUTION: Upgrade to the current version of Avaya
Communication Manager software.
CAUSE: The telephone has detected an IP Address conflict.
RESOLUTION: Verify administration to identify duplicate IP
Address(es).
CAUSE: Unnamed registration attempted but unnamed registration
(UNR) is not enabled on Avaya Communication Manager for IP
Telephones.
RESOLUTION: Change CM settings to enable.
CAUSE: A device between the telephone and the call server is invoking
Network Address Port Translation, which the 4600 Series IP Telephones
do not support.
RESOLUTION: Contact the System Administrator to remove or
re-administer the device.
CAUSE: The system parameter MCIPADD does not contain at least one
non-zero IP Address or DNS Name, causing the telephone to reset.
RESOLUTION: Add the IP Address(es) using static addressing (manual
telephone setting), updating the settings file, or normally through DHCP
administration.
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. Note
that if the telephone is attached to a 30A switched hub, upon loss of
Ethernet connectivity the usual No Ethernet message is not
displayed.
CAUSE: The TFTP server IP Address in the IP telephone'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 TFTP server, or administer
the telephone locally using the ADDR option. The ADDR option is
explained in Chapter 3: Local Administrative Options.
3 of 5