Filter
Top Products
Troubleshooting Guidelines
128 4600 Series IP Telephone LAN Administrator Guide
Table 14: Some Error Conditions in Operation of 4600 Series IP Telephones
Condition Cause/Resolution
The telephone continually reboots, or reboots
continuously about every 15 minutes.
CAUSE: The telephone cannot find the call
server.
RESOLUTION: Ensure that MCIPADD is
administered either manually or through
DHCP, TFTP, or HTTP, as appropriate.
CAUSE: This might be a firmware fault
because the MAC address in memory is
corrupted.
RESOLUTION: Return the telephone to Avaya
for repair.
The message light on the telephone turns on
and off intermittently, but the telephone never
registers.
CAUSE: This is a hardware fault.
RESOLUTION: The telephone must be
returned to Avaya for repair.
The telephone
stops working in
the middle of a call,
AND no lights are lit on
the telephone and the
display is not lit.
CAUSE: Loss of power.
RESOLUTION: Check the connections
between the telephone, the power supply, and
the power jack. For example, verify that either
static addressing was not used or that any
changes to static addresses were entered
correctly.
AND power to the
telephone is fine (and
the telephone might
have gone through the
restarting sequence).
CAUSE: Loss of path to Avaya Media Server,
DHCP Lease expired, or DHCP server not
available when telephone attempts to
renegotiate DHCP lease.
RESOLUTION: As above. 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.
1 of 6