Handset Status Messages - Polycom SpectraLink 1725-36038-001 Administration Manual

Handset Status Messages

Message Description
Download failure icon
3 chirps (audio) Handset is not able to communicate
with the best AP, probably because
that AP has no bandwidth available.
802.1X Failure
When WPA2-Enterprise or Cisco FSR
is selected, the handset failed to
Xxxxxxxxxxxx
connect because the user credentials
XXX
are restricted based on the user
account properties. In the case of
EAP-FAST, the PAC ID may not match
the username.
The second line of the error message
contains the twelve digits of the AP
MAC address and three digits that
indicate the error code as defined in
RFC2759.
Address Mismatch Handset software download files are
incorrect or corrupted.
Assoc Failed x...x = AP MAC address.
xxxxxxxxxxxx Handset association was refused by
AP; displays MAC of failing AP.
Assoc Timeout x...x = AP MAC address.
xxxxxxxxxxxx Handset did not receive association
response from AP; displays MAC of
failing AP.
Auth Failed x...x = AP MAC address.
xxxxxxxxxxxx Handset authentication was refused by
AP; displays MAC of failing AP.
PN: 1725-36038-001_N.docx
SpectraLink 8020/8030 Wireless Telephone status messages provide
information about the SpectraLink 8020/8030 Wireless Telephone's
communication with the AP and host telephone system. The
following table summarizes, in alphabetical order, the status
messages.
Action
Update handset code in the
provisioning server and power cycle the
handset.
None. This is only a warning, the call
will hand off to the best AP once it
becomes available.
Verify and resolve if the user account
has any restrictions such password
expired, account restricted/ disabled, or
in case of EAP-FAST, the handset PAC
and username matching the
authentication server.
Download new software from the
Polycom website per Chapter 10:
Software Maintenance.
Check handset and AP security
settings.
Ensure AP is configured per VIEW
Configuration Guide.
Try another AP.
Check handset and AP security
settings.
Ensure AP is configured per VIEW
Configuration Guide.
Try another AP.
Check handset and AP security
settings.
Ensure AP is configured per VIEW
Configuration Guide.
Try another AP.
Troubleshooting
121