Avaya 4600 IP Phone User Manual


 
Troubleshooting Guidelines
114 4600 Series IP Telephone Release 2.2 LAN Administrator Guide
Discovering... CAUSE: The telephone is seeking a gatekeeper on the
media server, using its administered gatekeeper list.
RESOLUTION: Wait for a valid registration to occur, or
press # to interrupt the search and re-initialize manual or
DHCP/script files procedures.
File too large
Cannot save 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 file server.
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.
Hardware failure CAUSE: Hardware failure prevented downloading of
application file,
RESOLUTION: Replace telephone.
IP Address in use by
another
CAUSE: The telephone has detected an IP Address
conflict.
RESOLUTION: Verify administration to identify duplicate
IP Address(es).
NAPT Error 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: Remove or re-administer the NAPT device
or move the telephone.
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, 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.
Table 12: Possible Error Messages During Installation or Operation of 4600 Series IP
Telephones (continued)
Error Message Cause/Resolution
2 of 5