Table of Contents
Advertisement
Table 5-1. Some Error Conditions in Operation of 4600 Series IP Telephones—Continued
Condition
The user indicates a 4620-specific or 4630/4630SW-
specific application is not accessible.
There are three areas where installers can troubleshoot problems before seeking assistance from
the system or LAN administrator:
1. Check the wiring (power and Ethernet) for the following:
Whether all components are plugged in correctly.
Check LAN connectivity in both directions to all servers (DHCP, TFTP, Call Server). 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.
If the telephone is supposed to be powered from the LAN, ensure the LAN is properly
administered and is compliant with IEEE 802.3af.
2. If you are using static addressing, do the following:
Use the View command to find the names of the files being used and verify that these
filenames match those on the TFTP server. Check on the Avaya website to verify whether
the correct files are being used.
Use the ADDR option to verify IP addresses.
Use the QOS option to verify QoS parameters.
Refer to Chapter 3 of the 4600 Series IP Telephone Installation Guide.
3. If the 4600 Series IP Telephone is not communicating with the system (DHCP, TFTP, or Call
Server), make a note of the last message that was displayed and consult the system
administrator.
Troubleshooting Guidelines
Cause/Resolution
CAUSE: The 46xxsettings script file is
not pointed to accurately, or is not
properly administered to allow the
application.
RESOLUTION: Assuming the user is
meant to have that application, verify the
46xxsettings script file is properly
specified for your system, including case
(if your TFTP server is UNIX or LINUX)
and extension. Then, verify all the
relevant parameters (as indicated in
Table 4-6, on page 4-34
on page
4-39, as appropriate) are
accurately specified in the 46xxsettings
file.
and
Table 4-7,
Error Conditions
5-7
Advertisement
Table of Contents
