
specific deskphone model also contains troubleshooting for users having problems with
specific IP deskphone applications. Most of the problems reported by deskphone users are
LAN-based, where Quality of Service, server administration, and other issues can impact end-
user perception of IP deskphone performance.
Table 4: Operational error conditions for 9600 Series IP deskphones
Condition
Cause/Resolution
The deskphone 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, you must
return the deskphone to Avaya for repair.
The message light on the deskphone turns
on and off intermittently, but the deskphone
never registers.
CAUSE: This is a hardware fault.
RESOLUTION: You must return the
deskphone to Avaya for repair.
The deskphone
stops working in
the middle of a
call,
AND no lights are lit
on the deskphone
and the display is not
lit.
CAUSE: Loss of power.
RESOLUTION: Check the connections
between the deskphone, 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.
AND power to the
deskphone is normal
and the deskphone
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 deskphone
was working, but
does not work
now,
AND no lights are lit
on the deskphone
and the display is not
lit.
CAUSE: Loss of power.
RESOLUTION: Check the connections
between the deskphone, the power supply,
and the power jack.
AND power to the
deskphone 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 deskphone using ARP or
trace-route and from the deskphone 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 deskphone.
Operational errors and status messages
Installing and Maintaining Avaya IP Deskphone H.323 9608, 9611G, 9621G, and 9641G
August 2013 81