Avaya 9601 - Page 79

Operational errors and status messages
Issue 5 August 2014 79
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 fine, but
there is no dial tone or
the call appearances
or feature buttons do
not work.
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
administration has not changed for the LAN
equipment (routers, servers, etc.) between the
call server and the deskphone. Verify no one
changed the deskphone settings locally using
the VIEW and ADDR craft procedures, as
described earlier in this guide.
AND the deskphone
was recently moved.
CAUSE: Loss of communication with the call
server.
RESOLUTION: As above, but pay particular
attention to the possibility that the deskphone is
being routed to a different DHCP server, or even
a different proxy server. If so, the new server
might need to be administered to support the
deskphone.
AND the network was
recently changed to
upgrade or replace
servers, re-administer
the Communication
Manager call server,
add or change NAT,
etc.
CAUSE: Loss of communication with Session
Manager.
RESOLUTION: As above.
Table 4: Operational error conditions for 9601, 9608, 9608G, 9611G, 9621G, or 9641G IP
deskphones (continued)
Condition Cause/Resolution
2 of 6