Filter
Top Products
Error Conditions
Issue 2.2 April 2005 101
The telephone 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 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
PBX switch.
RESOLUTION: Check LAN continuity from
the PBX to the telephone using ARP or
trace-route and from the telephone to the
PBX 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 codes, as described in
the 4600 Series IP Telephone Installation
Guide. Verify the telephone volume is set
high enough. Finally, conduct a self-test.
AND the telephone
was recently moved.
CAUSE: Loss of communication with the
PBX.
RESOLUTION: As above, but pay particular
attention to the possibility that the telephone
is being routed to a different DHCP server, or
even a different PBX switch. If so, the new
server or switch might need to be
administered to support the telephone.
AND the network was
recently changed to
upgrade or replace
servers, re-administer
the Avaya media
server, add or change
NAT, etc.
CAUSE: Loss of communication with the
PBX.
RESOLUTION: As above.
Table 10: Some Error Conditions in Operation of 4600 Series IP
Telephones (continued)
Condition Cause/Resolution
2 of 6