TD 92685EN
28 June 2012 / Ver. A
Troubleshooting Guide
Ascom i62 VoWiFi Handset
52
7. VoWiFi Handset
scanning process. See section 3.7 DFS Channel Probing on page 19.
7.1.3 No Access
A “No access” message indicates a Layer 3 fault.
The handset has successfully associated
with an AP but it cannot connect to either the IP-PBX or the Unite system. This may be
because the application services are not running or the services are running but the handset
is unable to connect to the services due to faulty IP address configuration.
Tip: A s
upport engineer will often need to check for problems on the wired side of the
installation as well as the wireless side and should be equipped with adequate tools for
troubleshooting wired LANs.
1 Check IP address. From the handset Device in
fo > Network info menu described in
Appendix B and inspect the value of the Phone IP param
eter to see if the handset has
an IP address.
- If using static IP addresses: Check that the
settings are correct and that there is no
IP conflict with another device. Pay special attention to the value of “Default
gateway” if the IP PBX is on another subnet or VLAN.
- If using DHCP-server delivered IP addresses: Check that the
re is connection to the
DHCP server.
2 DHCP problems may also be the case if the there is no a
ccess to the DCHP server in a
LAN that is segmented using subnets or VLANs.
To test DHCP problem perform one or m
ore of the following steps:
- Try to set the IP-address parameters manual
ly. If access is restored it clearly
indicates a DHCP problem.
Tip: To excl
ude TCP/IP stack problems in the handset, ping the handset from a laptop
and also browse to the handset's web interface.
- Use a laptop with a wireless card to see if the
laptop receives an IP address.
- Use a wired connection to the same switched network/VLAN as t
he AP (or
controller) is connected to, to test if it receives an IP address over DHCP.
- It is also possible to take help of a network adm
inistrator and try to ping to or from
an AP or other device to the DHCP server. If this is successful the DHCP problem is in
the wireless part of the site.
Tip: If a wirel
ess sniffer is available, configure it for the correct encryption key and try
to decode packets both from and to the handset.
If the handset initiates the DHCP handshake function, the
problem is that the AP isn’t
forwarding DHCP offers or the wrong address is sent out. Check for the possibility
that the WLAN internal DHCP server does not work.
A common cause is that the VLAN/SSID/USER
CLASS mapping is wrong and that the
DHCP server cannot be reached from the wireless side.
3 If the handset has an IP-address the problem is either in the Services setup,
or the IP-
PBX and Unite services are not reachable.
Major causes can be:
• Wrong IP address parameter settings for VoIP a
nd Unite.
• Login credentials to the services a
re wrong.
• The handset is not registered in the services.
• Services are on another (sub) network and routing to that LAN is not functioning.
Test the access for VoIP and Unite (fo
r Messaging and Alarm functions) individually
as follows:
To Next Page
Loading...
Need help?
General
