Avaya Communication Server 1000 Installation And Commissioning Manual page 176

Troubleshooting
Message
No Net Found
xxxxxxxxxxxx yy
No PBX Response
No Proposal
No Reg Domain
No SVP IP
No SVP Response
yyy.yyy.yyy.yyy
176 Avaya WLAN IP Telephony Installation and Commissioning
Description
incorrect WEP settings
Incorrect Security settings
x...x = AP MAC address yy =
AP signal strength Handset
cannot find a suitable AP;
displays the MAC address and
signal strength of the best
nonsuitable AP found.
The wireless handset tried to
send a message to the Call
Server and failed to get a
response.
The handset and the VPN
server cannot agree on a set of
configuration parameters.
Regulatory Domain not set
The wireless handset is
configured for static IP (as
opposed to use DHCP) and no
valid WLAN IP Telephony
Manager 2245 address is
entered.
y...y = WLAN IP Telephony
Manager 2245 IP address The
handset has lost contact with
the WLAN IP Telephony
Manager 2245.
Action
handsets are working within
the same range of an AP. If
so, check the SSID of the
handset.
Verify that all the WEP
settings in the handset
match those in the APs.
Verify that all the Security
setting in the AP.
Check the AP and handset
network settings, such as
ESSID, (for the WLAN
Handsets 2210/ 2211/2212),
SSID (for Avaya 6120/6140
WLAN Handsets ), Security,
Reg. domain and Tx power.
Ensure that the APs are
configured per the
Configuration Note. Try Site
Survey mode to determine a
more specific cause.
Verify the Call Server is
operational and connected
to the network.
Check that the Diffie-
Hellman group, phase 1 and
phase 2 hashes, and the
encryption algorithms
configured on the handset
are acceptable to the VPN
server.
Configure the Regulatory
Domain of the handset.
Enter a valid WLAN IP
Telephony Manager 2245 IP
address in the wireless
handset configuration
setting or change to use
DHCP.
This can be caused by bad
radio reception or a problem
with the WLAN IP Telephony
Manager 2245. The handset
keeps trying to fix the
November 2010