Avaya 3600 - Manual (Page 59)

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 59
Message Description Action
No Gatekeeper The WT has not received a response
from the gatekeeper Verify gatekeeper is running and
has network connectivity to WLAN
infrastructure.
No Gatekeeper IP The WT is configured for static IP
addresses and no valid unicast IP
address is assigned for gatekeeper
configuration Configure a valid IP address in
Admin menus.
No Gateway IP The WT is configured for static IP
addresses and no valid unicast IP
address is assigned for gateway
configuration Configure a valid IP address in
Admin menus.
No Host IP (Addr) The WT is configured for “static IP”
(as opposed to “use DHCP”) and no
valid host IP address (the WT’s IP
address) has been entered. Enter a valid IP address in the
configuration settings or change to
“use DHCP”.
No IP Address Invalid IP Check the IP address of the WT
and re-configure if required.
No Net Access Cannot authenticate / associate with
AP Verify the AP configuration.
Verify that all the WEP settings in
the WT match those in the APs.
No Net Found
No APs WT cannot find any Access Points
This indicates any of the following:
No radio link Verify that the AP is turned on.
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 Note for AP.
Out of range Try getting closer to an AP. Check
to see if other WTs are working
within the same range of an AP. If
so, check the ESSID of this WT.
Incorrect Security settings Verify that all the Security settings
in the WT match those in the APs
No Net Found
xxxxxxxxxxxx yy x…x = AP MAC address
yy = AP signal strength
WT cannot find a suitable access
point; 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
Configuration Note.
Try Site Survey mode to determine
more specific cause.
No Reg Domain Regulatory Domain Not Set Configure the Regulatory Domain
of the WT
No AVPP IP The WT is configured for “static IP”
(as opposed to “use DHCP”) and no
valid AVAYA AVPP address has
been entered. Enter a valid AVAYA AVPP IP
address in the configuration setting
or change to “use DHCP.”