Avaya
4600 Series Administrator's Manual page 87

Table 5-3. Possible Error Messages During Installation or Operation of 4600 Series IP
Telephones—Continued
Error Message
No Ethernet
No file server
address
System busy
System Error
During Registration
Extension error
Extension in use
Cause/Resolution
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.
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 as detailed in
the 4600 Series IP Telephone Installation Guide.
CAUSE: Most likely, the number of IP endpoints on the Avaya media
server is already at maximum, Less likely, network resource is
unavailable.
RESOLUTION: The telephone was attempting to access a network
resource (DHCP server, TFTP server, or the Avaya media server) and
was not successful. The resource being called upon should be
checked for its availability. If it appears operational and properly linked
to the network, verify addressing is accurate and a communication
path exists in both directions between the telephone and the resource.
CAUSE: The Avaya media server has an unspecified problem.
RESOLUTION: Consult your Avaya media server administration and
troubleshooting documentation.
CAUSE: An invalid Avaya media server Registration extension has
been entered.
RESOLUTION: Re-enter the extension if mis-entered initially. If
appropriate, verify proper extension with respect to switch
administration.
CAUSE: The specified extension is already in use, according to the
Avaya media server.
RESOLUTION: Wait a few minutes, and try again. This will work for
the case when the extension is correctly administered, but service was
interrupted and the Avaya media server is not yet aware of that fact.
Otherwise, verify proper extension with respect to switch
administration.
Troubleshooting Guidelines
Error Messages
5-13