Table 20: Operational error conditions
Condition
Cause/Resolution
The phone continually reboots, or reboots
continuously about every 15 minutes.
CAUSE: The phone cannot find the HTTP/HTTPS
server and/or call server.
RESOLUTION: Ensure that MCIPADD is administered
either manually or through DHCP or HTTP, as
appropriate. Alternately, this might be a firmware fault
because the MAC address in memory is corrupted; in
this case, you must return the phone to Avaya for
repair.
The message light on the phone turns on and off
intermittently, but the phone never registers.
CAUSE: This is a hardware fault.
RESOLUTION: You must return the phone to Avaya
for repair.
The phone stops
working in the middle
of a call,
AND no lights are lit on
the phone and the
display is not lit.
CAUSE: Loss of power.
RESOLUTION: Check the connections between the
phone, the power supply, and the power jack. For
example, verify whether static addressing was not
used or that any changes to static addresses were
entered correctly. Follow POE guidelines to
troubleshoot POE related problems.
AND power to the phone
is normal and the phone
might have gone through
the restarting sequence.
Loss of path to the Avaya call server, expiry of DHCP
lease, or unavailable DHCP server when telephone
attempts to renegotiate DHCP lease.
RESOLUTION: As above.
The phone was
working, but does not
work now,
AND no lights are lit on
the phone and the
display is not lit.
CAUSE: Loss of power.
RESOLUTION: Check the connections between the
phone, the power supply, and the power jack. Follow
POE guidelines to troubleshoot POE related
problems.
AND power to the phone
is normal, but there is no
dial tone. The display
might show “System
Busy.”
CAUSE: Loss of communication with the call server.
RESOLUTION: Check LAN continuity from the call
server to the phone using ARP or trace-route and
from the phone to the call server by invoking a
Feature button. Verify that LAN administration has not
changed for the Gatekeeper, TN 2302AP boards, or
the LAN equipment (routers, servers, etc.) between
the switch and the phone.
Verify that telephone settings are not changed locally
using VIEW and ADDR information, as described
earlier in this guide. Verify that the telephone volume
is set high. Finally, conduct a self-test.
Table continues…
Troubleshooting
May 2018
Installing and Administering Avaya J169/J179 IP Phone H.323
192
