User manual
Table Of Contents
- 1. Introduction
- 2. Pre-Installation
- 3. Programming the VoWiFi Handset
- 4. Installation of VoWiFi Handsets
- 5. Maintenance
- 5.1 Handset
- 5.1.1 Configure Spare Handsets without a Number in Large Systems
- 5.1.2 Upgrade Handset Software
- 5.1.3 Upgrade Software OTA via TFTP
- 5.1.4 Upgrade Software via PDM
- 5.1.5 Upgrade Software Over the Air (OTA) via Centralized Device Management (IMS3)
- 5.1.6 Recapture the Earlier Software
- 5.1.7 Upgrade Handset Functionality using License
- 5.1.8 Perform a Factory reset
- 5.2 Replacement of Handsets
- 5.3 Change Number of a Handset
- 5.4 Update Parameters via IMS3
- 5.5 Perform a Security Upgrade via IMS3
- 5.6 Upgrade the Template
- 5.7 Create a Configuration Backup
- 5.1 Handset
- 6. Handset Configuration
- 6.1 Select Network
- 6.2 IP Address Settings
- 6.3 Network Settings
- 6.4 Security Settings
- 6.5 Handset Settings
- 6.5.1 Automatic key lock
- 6.5.2 Phone lock
- 6.5.3 Audio adjustment
- 6.5.4 Headset Configuration
- 6.5.5 In Charger Behavior
- 6.5.6 Configure Profiles
- 6.5.7 Hide Missed Call Window
- 6.5.8 Battery Warning
- 6.5.9 Shared Phone
- 6.5.10 Prevent Handset Switch off
- 6.5.11 Uploadable Language
- 6.5.12 Select Default Language
- 6.5.13 Short cuts
- 6.5.14 Soft Key Functions During Call
- 6.5.15 Import Contacts
- 6.5.16 Company Phonebook
- 6.5.17 Central Phonebook
- 6.6 Messaging and Alarm
- 6.7 Messaging Settings
- 6.8 Alarm Settings
- 6.9 Telephony
- 6.9.1 Endpoint ID and Endpoint number
- 6.9.2 VoIP Protocol
- 6.9.3 Codec
- 6.9.4 Offer Secure RTP
- 6.9.5 Internal Call Number Length
- 6.9.6 Emergency Number
- 6.9.7 Voice Mail Number
- 6.9.8 Message Centre Number
- 6.9.9 Max number of Call Completions
- 6.9.10 Dial Pause Time
- 6.9.11 Direct off Hook from Charger
- 6.9.12 Replace Call Rejected with User Busy
- 6.9.13 Busy on 1 / Disable call waiting
- 6.9.14 Calling Line Restriction
- 6.10 Regional Settings
- 6.11 Display
- 6.12 Menu Operation
- 6.13 Push-To-Talk (PTT) Group Call
- 6.14 Presence Management
- 6.15 Location
- 7. Use Handset to Verify the VoWiFi System Deployment
- 8. Handset Internal Web Administration Page
- 9. Administration
- 10. Troubleshooting
- 11. Related Documents
- 12. Document History
- Appendix A: Working with Templates
- Index
- Contents
TD 92675EN
20 June 2012 / Ver. E
Configuration Manual
Ascom i62 VoWiFi Handset
67
10. Troubleshooting
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.)
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 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.
Voice only The handset is configured
to use both a gatekeeper
and an IMS3, but has lost
contact with the IMS3.
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.
Display shows Probable cause Action or comment