Wireless Handset Status Messages - Avaya Communication Server 1000 Installation And Commissioning Manual

Wireless handset status messages

Wireless handset status messages provide information about the handset communication with
the AP and Call Server.
the status messages, in alphabetical order.
Table 44: Wireless handset status messages
Message
3 chirps
Address Mismatch
ASSERT xxx.c Line yyy
(For WLAN Handsets
2210/2211/2212 only.)
Assoc Failed xxxxxxxxxxxx x...x = AP MAC address
Assoc Timeout
xxxxxxxxxxxx
Auth Failed xxxxxxxxxxxx
Auth Timeout xxxxxxxxxxxx x...x = AP MAC address
Avaya WLAN IP Telephony Installation and Commissioning
Table 44: Wireless handset status messages
Description
Wireless handset is not able to
communicate with the best AP,
probably because that AP has
no bandwidth available.
Wireless handset software
download files are incorrect or
corrupted.
The handset has detected a
fault from which it cannot
recover.
Handset association is refused
by the AP; displays the MAC of
the failing AP.
x...x = AP MAC address
Handset did not receive an
association response from the
AP; displays the MAC of the
failing AP.
x...x = AP MAC address
Handset authentication is
refused by the AP; displays the
MAC of the failing AP.
Handset did not receive an
on page 167 summarizes
Action
None. This is only a warning.
The call is handed-off to the
best AP after it becomes
available.
Download new software
from the Avaya site. See
Software updates on
page 155.
Record the error information
so that it can be reported.
Turn the handset off, and
then on again.
If the error persists, try
registering a different
handset to this telephone
port.
If the error still persists,
contact Avaya Technical
Support and report the error.
Check the handset and AP
security settings. Ensure
that the AP is configured per
the Configuration Note. Try
another AP.
Check the handset and AP
security settings. Ensure
that the AP is configured per
the Configuration Note. Try
another AP.
Check the handset and AP
security settings. Ensure
that the AP is configured per
the Configuration Note. Try
another AP.
Check the handset and AP
security settings. Ensure
November 2010
Dropped calls
167