Avaya 3616 Installation And Configuration Manual page 42

3616/26 Wireless IP Telephone
Installation and Configuration Guide
Message
Multiple GW Res
Network Busy
No Call Server IP
or
No Call Server
(when apparently
valid IP, but no
response to the
GRQ/RRQ
process)
The No Call Server
message may
include an error
indication
No Host IP
No IP Address
No Net Access
No Net Found
42
Description
More than one SVP Server has
responded
All APs are full or busy
Wireless Telephone not administered
on the Avaya Call Server
The Avaya Call Server is not working
No LAN connection at the AP or the
Avaya Call Server
Wireless Telephone can't locate the
Avaya Call Server
The Wireless Telephone is configured
for "static IP" (as opposed to "use
DHCP") and no valid host IP address
(the Wireless Telephone's IP
address) has been entered.
Invalid IP
•
Cannot authenticate / associate
with AP
•
Incorrect WEP settings
This indicates any of the following:
•
No radio link
•
No ESSID – Autolearn not
supported (or)
Incorrect ESSID
Action
Caused by two or more Wireless
Telephones sharing the same IP
address. Assign unique IP
addresses to each Wireless
Telephone.
Try call again later.
Wireless Telephone not properly
configured. Verify that extension
and password in the Wireless
Telephone match those
administered in the Avaya Call
Server.
Verify that the Avaya Call Server is
operational. If so, follow standard
troubleshooting procedures for the
Avaya Call Server.
Verify the Avaya Call Server
connection to LAN and all APs.
IP address configuration of the
Avaya Call Server is wrong or
missing.
Enter a valid IP address in the
configuration settings or change to
"use DHCP".
Check the IP address of the
Wireless Telephone and re-
configure if required.
Verify the AP configuration.
Verify that all the WEP settings in
the Wireless Telephone 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.
555-301-107, Issue 3
May 2004