Avaya 4600 Series Administrator's Manual page 151

Ip telephone
Hide thumbs Also See for 4600 Series:
Table of Contents

Advertisement

Table 16: Possible Error Messages During Installation or Operation of 4600 Series IP
Telephones (continued)
Error Message
IP Address in use by
another
NAPT Error
No Ethernet
No file server or phone
IP address
No Socket
System busy
System Error
Cause/Resolution
CAUSE: The telephone has detected an IP Address
conflict.
RESOLUTION: Verify administration to identify duplicate
IP Address(es).
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.
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 IP Address of the Phone and file server 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 file server, or administer the telephone locally using
the ADDR option. The 4600 Series IP Telephone
Installation Guide explains the ADDR option.
CAUSE: The telephone has registered with the call server,
but network problems have prevented the telephone from
opening a TCP socket.
Note: This message only occurs on older software
versions. Telephones with newer software automatically
reset.
RESOLUTION: Investigate the network problem normally.
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. Check the
resource being called upon for its availability. If the
resource 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.
Error Messages
2 of 7
Issue 8 July 2008
151

Advertisement

Table of Contents
loading

Table of Contents