Operational Errors and Status Messages
Issue 1 August 2010 69
with the telephone itself. Problems are more likely LAN-based, where Quality of Service, server
administration, and other issues can impact end-user perception of IP telephone performance.
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 telephone 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.
CAUSE: This might be a firmware fault because
the MAC address in memory is corrupted.
RESOLUTION: 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 Avaya Media Server,
DHCP Lease expired, or DHCP server not
available when telephone attempts to
renegotiate DHCP lease.
RESOLUTION: As above.
1 of 6
To Next Page
Loading...
Need help?
General
