Configuration Manual
Ascom i62 VoWiFi Handset
Display shows
No network.
(The handset beeps once
a minute with a low tone
followed by a high tone
(during max 30 minutes).
If the vibrator is enabled,
it vibrates after the last
beep.)
Voice only
20 June 2012 / Ver. E
10. Troubleshooting
Probable cause
The handset is out of
coverage,
or faulty handset.
The handset cannot find
the wireless infrastructure
with settings matching
those configured in the
handset.
The handset is configured
to use both a gatekeeper
and an IMS3, but has lost
contact with the IMS3.
TD 92675EN
Action or comment
The beeps can be stopped with the
mute button. Then go into range.
Note: When re-entering the
coverage area it can take a couple of
minutes before the handset
automatically has registered into
the system.
If this does not work, contact the
system administrator.
1) Check the SSID. The SSID
configured in the handset must be
identical to the SSID configured in
the system infrastructure.
2) Check the security settings. The
security settings, that is,
authentication and encryption must
match the settings in the system
infrastructure.
3) Check for 802.11d multi
regulatory domain settings. The
handset (software version 2.x.x)
must be able to detect in which
country it is located to use the
correct channel and transmit power
settings. Later versions have a
parameter specifying if 802.11d
should be used or not. This is
provided by the infrastructure
according to the 802.11d standard.
4) Check which channels are used.
The handset uses by default channel
1, 6 and 11. If the infrastructure is
configured to use any other channel,
change it to use only 1, 6 and 11 as
this is the recommended setting.
5) Check that the correct Network
(A, B, C or D) setting is selected.
1) Check the IMS3 address. Try to
ping the IMS3 from another PC.
2) Remove handset from DP1. When
connected to the PDM via USB on
the Desktop Programmer (DP1), the
handset cannot connect to the IMS3
and may then show "Voice only".
3) If messaging is not used in the
system, verify that the IMS3 address
is configured to 0.0.0.0.
67
Need help?
Do you have a question about the i62 and is the answer not in the manual?
Questions and answers
no access solving
To solve access issues with the Ascom i62, follow these steps:
1. Login to the Device:
- Enter the phone's IP address in the browser.
- Click the login link in the top right corner.
- Enter the username “admin” and password “changeme”.
- Click OK.
2. Check Logs and Errors:
- Navigate to the Troubleshoot tab.
- Review the Syslog for real-time handset actions.
- Check the Errorlog for stored errors and download it if needed.
3. Review WLAN and Voice Statistics:
- Open the Statistics tab to check call and WLAN connectivity details.
4. Wi-Fi Configuration Adjustments:
- Ensure consistent transmission power across all APs.
- Avoid large power variations set by ARM.
- Match AP channels with the i62 configuration.
- If connectivity is intermittent, test with one AP first, then expand.
5. SSID Profile Optimization:
- Use a clean SSID profile and apply optimizations step by step.
- Observe behavior after each change to identify potential issues.
If the issue persists, provide logs to Ascom support for further analysis.
This answer is automatically generated