Avaya 3641 - Page 104

104 Avaya 3641/3645/6120/6140 IP Wireless Handset SIP Administration Guide June 2012
Message Description Action
No ESSID: Auto-learn not supported
(or) incorrect ESSID.
Verify the ESSID of the wireless LAN
and enter or Autolearn it again if
required.
AP does not support appropriate data
rates.
Check the AP configuration against
Configuration Guide for AP.
Out of range.
Try getting closer to an AP. Check to
see if other handsets are working within
the same range of an AP. If so, check
the ESSID of this handset.
Incorrect Security settings.
Verify that all the Security settings in the
handset match those in the APs.
No Net Found
xxxxxxxxxxxx yy
x…x = AP MAC address.
yy = AP signal strength.
Handset cannot find a suitable AP;
displays MAC and signal strength of
“best” non-suitable AP found.
Check AP and handset network settings
such as ESSID, Security, Reg domain
and Tx power.
Ensure APs are configured per VIEW
Configuration Guide for AP.
Try Site Survey mode to determine a
more specific cause.
No Net Found
No CCX APs
The Wireless Telephone is configured
for CCX compatible operation, but
cannot find an access point that is
advertising CCX capability.
Check the AP configuration against
VIEW Configuration Guide for AP.
No Net Found
No CCKM APs
The Wireless Telephone is configured
to use CCKM for fast and secure
handoffs, but cannot find an access
point that is configured appropriately.
Check the AP configuration against
VIEW Configuration Guide for AP.
No Net Found
No WMM APs
The Wireless Telephone is configured
to use Wi-Fi Standard QoS, but cannot
find an AP configured appropriately.
Check the AP configuration against
VIEW Configuration Guide.
No PBX Response
The handset has exceeded its
retransmission limit with no ACK
response from proxy server.
Verify that proxy server IP address and
port are properly configured.
No Reg Domain Regulatory Domain Not Set.
Configure the Regulatory Domain of the
handset.
No Server IP
In the case of static IP configuration,
the handset failed to find the call
server IP.
Verify that call server info is properly
configured on the handset.
No SVP IP
The handset is configured for “Static
IP” (as opposed to “use DHCP”), and
no valid Avaya SVP Server address
has been entered.
Enter a valid Avaya SVP Server IP
address in the configuration setting or
change to “use DHCP.”