Avaya 3600 Series Configuration And Administration Manual page 59

Avaya, Inc.
Message
No Gatekeeper The WT has not received a response
from the gatekeeper
No Gatekeeper IP The WT is configured for static IP
addresses and no valid unicast IP
address is assigned for gatekeeper
configuration
No Gateway IP The WT is configured for static IP
addresses and no valid unicast IP
address is assigned for gateway
configuration
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.
No IP Address Invalid IP
No Net Access Cannot authenticate / associate with
AP
No Net Found WT cannot find any Access Points
No APs This indicates any of the following:
No radio link
No ESSID – Auto-learn not
supported (or) incorrect ESSID
AP does not support appropriate
data rates
Out of range
Incorrect Security settings
No Net Found x...x = AP MAC address
xxxxxxxxxxxx yy yy = AP signal strength
WT cannot find a suitable access
point; displays MAC and signal
strength of "best" non-suitable AP
found.
No Reg Domain Regulatory Domain Not Set
No AVPP IP The WT is configured for "static IP"
(as opposed to "use DHCP") and no
valid AVAYA AVPP address has
been entered.
21-300352, Issue 2, July 2005
Configuration and Administration—AVAYA 3616/3620/3626 WT
Avaya CCMS IP, Avaya Call Server, with Avaya 4612 IP Telephone Emulation
Description Action
Verify gatekeeper is running and
has network connectivity to WLAN
infrastructure.
Configure a valid IP address in
Admin menus.
Configure a valid IP address in
Admin menus.
Enter a valid IP address in the
configuration settings or change to
"use DHCP".
Check the IP address of the WT
and re-configure if required.
Verify the AP configuration.
Verify that all the WEP settings in
the WT match those in the APs.
Verify that the AP is turned on.
Verify the ESSID of the wireless
LAN and enter or Autolearn it
again if required.
Check the AP configuration against
Configuration Note for AP.
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.
Verify that all the Security settings
in the WT match those in the APs
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.
Configure the Regulatory Domain
of the WT
Enter a valid AVAYA AVPP IP
address in the configuration setting
or change to "use DHCP."
Page 59