Avaya 3600 - Manual (Page 61)

Avaya, Inc. Configuration and Administration—AVAYA 3616/3620/3626 WT
Avaya CCMS IP, Avaya Call Server, with Avaya 4612 IP Telephone Emulation
21-300352, Issue 2, July 2005 Page 61
Message Description Action
Resource
Unavailable Gatekeeper rejected registration
request from the WT Check the H.323 gatekeeper
configuration in the WT.
Verify the gatekeeper or PBX’s
configuration
Retarting… The WT is in the process of
rebooting. There will be a 20 second
delay in an attempt to let potential
network/system errors clear. None
Retry / Restart The Wireless Telephone is waiting
for user input prior to retrying the
registration process, or restarting
after a delay. See Avaya Call Server Integration
Factors section.
Select License The correct protocol has not been
selected from the license set. Using the administrative menus,
select one license from the set to
allow the WT to download the
appropriate software.
Server Busy WT is attempting to download from a
TFTP Server that is busy
downloading other devices and
refusing additional downloads. None, the WT will automatically
retry the download every few
seconds.
SKT Open Failed Socket open fail. Occurs when the
WT tries to connect to the PBX but
there is no response. If resiliency is
active, the WT will keep trying. If the PBX is inoperative and
resiliency is not active or the WT
cannot locate a backup PBX, turn
off the WT and repair the primary
PBX. Note that it may be advisable
to reconfigure the backup PBX to
be the primary PBX if the repair is
more time-consuming than the
reconfiguration.
Socket Failure WT cannot communicate with the AP
or the AVPP This message may display with
another diagnostic message.
Follow diagnostic actions for the
second message (such as No Net
Found).
Storing Config WT is storing changes to handset
configuration. None. Informational only. The
handset may display this briefly
following a configuration change or
software download.
AVPP Service Rej. The AVAYA AVPP has rejected a
request from the WT The WT will restart and attempt to
re-register with the AVPP, which
should fix the problem. Report to
your administrator if it keeps
happening.
System Busy
yyy.yyy.yyy.yyy y…y = AVPP IP Address
AVPP has reached call capacity. All call paths are in use, try the call
again in a few minutes.
System Busy
Avaya Voice Priority Processor is
busy or out of resources All call paths are in use, try call
again in a few minutes.
System Error An internal failure has occurred in
the Avaya Call Server. If this condition persists, contact
the Avaya system administrator.