Table 4: Operational Error Conditions for 9600 Series IP Deskphones
Condition Cause/Resolution
The telephone continually reboots, or
reboots continuously about every 15
minutes.
CAUSE: The deskphone 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, 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 the Avaya call server,
DHCP Lease expired, or DHCP server not
available when telephone attempts to
renegotiate DHCP lease.
RESOLUTION: As above.
The telephone was
working, but does
not work now,
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.
AND power to the
telephone is fine, 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 telephone using ARP or trace-
route and from the telephone 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 telephone. Verify no one
changed the telephone settings locally using
the VIEW and ADDR Craft codes, as described
earlier in this guide. Verify the telephone
volume is set high enough. Finally, conduct a
self-test.
Operational errors and status messages
H.323 Installation & Maintenance Guide R6.1 May 2011 75