Our Quality and Environmental Management Systems are
implemented according to the requirements of the ISO9001 and
ISO14001 standards and are certified by an external certification
company.
The information provided in this document contains merely general descriptions or
characteristics of perfo rmance which in case of actua l use do not always apply as
described or which may change as a result of further development of the products.
An obligation to provide the respective cha racteristics shall only exist if expressly agreed in
the terms of contract.
Availability and technical specifications are subject to change without notice.
Unify, OpenScape, OpenStage and HiPat h are registered trademarks of Unify Software and
Solutions GmbH & Co. KG. All other company, brand, product and service names are
trademarks or registered trademarks of their respective holders.
C.5.9 Troubleshooting Easy Deployment in an MS 2003/2008 DHCP Server . . . . . . . . . . . . . . . . . . . . . . 185
A31003-M2000-S100-2-7620, 10/2018
6WLAN Handset, Configuration Manual
1 Introduction
WL3_CM_Ch1.fm
Introduction
This document is a guide for installing, configuring, and maintaining the
functionality of the WLAN Handset.
The OpenStage WL3 Voice over WiFi system provides wireless IP-telephony,
messaging, and alarm functions to enterprise LANs. Using third-party WLAN
products and hardware and software developed in-house, the system enables
data and voice transmission together with seamless roaming.
Figure 1OpenStage WL3 VoWiFi System
WinPDM
Device Manager
in WSG
Switch to IP Backbone/LAN/Internet
AP
AP
IP-PBX
OpenStage WL3
This document provides guidelines to install the WLAN Handset in a VoWiFi
system. The document describes the settings needed to make the handset
function in a VoWiFi system, and is targeted at the following personnel:
•System Administrator
•Service Technician
The handset is first configured using Easy Deployment, or using the Portable
Device Manager (WinPDM). In small systems where it is possible to collect all
handsets to update settings, daily maintenance is also done by using the
WinPDM.OpenStage WL3 WSG Server (WSG) supports managing the handsets
centrally using a web interface, without the need to collect the handsets.
The handset behavior can be customized to suite each user profile.
It is recommended that the reader has basic knowledge of the VoWiFi system and
basic knowledge of handset registration in the PBX.
802.11aIEEE 802.11 standard for transmission rate of up to 54Mbps,
operates in the 5GHz spectrum.
802.11bIEEE 802.11 standard for transmission rate of up to 11Mbps,
operates in the 2.4GHz spectrum.
802.11gIEEE 802.11 standard for transmission rate of up to 54Mbps,
operates in the 2.4GHz spectrum.
802.11dIEEE 802.11 standard for regulatory domains.
802.11eIEEE 802.11 standard that defines Quality of Service (QoS) for
WLAN.
802.11iStandard for security improvements for 802.11.
802.11nIEEE 802.11 standard for transmission rate of up to 100 Mbps,
operates in the 2.4GHz and 5GHz bands.
802.1DIEEE MAC Bridges standard (interworking for 802.11 among
others).
802.1XIEEE standard for port-based Network Access Control
(authentication).
Ad-hoc WLANA WLAN between two wireless capable devices (normally PCs),
where no Access Point (AP) is involved.
AESAdvanced Encryption Standard.
ALSAcoustic Location Signal
APAccess Point
BSSBasic Service Set. A WLAN with at least one AP that is configured
for it.
BSSIDBasic Service Set Identifier. Hard-coded name of an ad-hoc WLAN,
usually the MAC address of the radio. One type of SSID (the other
being ESSID).
CCXCisco Compatible eXtension
Device ManagerApplication for managing devices, editing parameters, and updating
devices with new software, without an administrator manually
needing to collect the devices, as it is done by Centralized
Management over the air (OTA). The Device Manager application
runs on an WSG hardware.
DHCPDynamic Host Configuration Protocol. Used to send config
parameters to TCP/IP clients.
DNSDomain Name System
DSCPDifferentiated Services Code Point. QoS on the Network Layer.
Used both for WLANS and LANs.
DTIMDelivery Traffic Indication Message
EAPExtensible Authentication Protocol.
EAP-FASTFlexible Authentication using secure tunneling.
EAP-TLSEAP-Transport Layer Security.
ELISEEmbedded LInux SErver:
A hardware platform used for WSG modules
ESSExtended Service Set. WLAN with multiple APs sharing the same
SSID.
A31003-M2000-S100-2-7620, 10/2018
8WLAN Handset, Configuration Manual
WL3_CM_Ch1.fm
Abbreviations and Glossary
ESSIDExtended Service Set Identifier. The identifying name of a WLAN. It
identifies an AP and distinguishes WLANS from one another. An
ESSID is one type of SSID (BSSID is the other).
IMInteractive Messaging makes it possible to access information from
an application, and controlling the information, by selecting a choice
received in a message.
LicenseAn authorization to use a licensed function.
MACMedium Access Control.
MWIMessage Waiting Indication
NTPNetwork Time Protocol
OTAOver The Air
PBXPrivate Branch Exchange:
Telephone system within an enterprise that switches calls between
local lines, and allows all users to share a certain number of
external lines.
PEAPProtected Extensible Authentication Protocol.
PRIPrimary Rate Interfaces
RSSIReceived Signal Strength Indication.
RTLSReal-Time Location System
RTSRequest-To-Send.
PTTPush-To-Talk
ServicesServices are predefined functions such as Phone Call, Send Data,
Send Message etc. that are accessible from the Service menu.
SIPSession Initiation Protocol
SSIDService Set Identifier. User friendly name of a WLAN. Identifier
attached to packets sent over a WLAN that acts as a password.
Daily used term for ESSID in an ESS wireless topology.
STAStation. Client in a WiFi network.
QoSQuality of Service: Defines to what extent transmission rates, error
rates, etc. are guaranteed in advance.
UP 6User Presence (value between 0-7). Wireless QoS at the MAC
Layer.
VoIPVoice over IP.
VoWiFiWireless version of VoIP. Refers to an IEEE 802.11a, b, g, n
network.
VoWLANVoice over WL AN.
WEPWired Equivalent Privacy.
WiFiThe commonly understood name for wireless LAN networks.
WinPDMPortable Device Manager (Windows version):
Used for managing devices, editing parameters, and updating
devices with new software.
WLANWireless Local Area Network. Refers to an IEEE 802.11a, b, g, n
network.
WMMWi-Fi Multimedia. A Wi-Fi Alliance interoperability certification,
based on the IEEE 802.11e standard. Provides basic QoS features
WPA/WPA2Wi-Fi Protected Access 2. Security method based on 802.11i
WSGOpenStage WL3 Wireless Service Gateway:
standard for wireless networks (data protection and network access
control).
Module that enables wireless services to and from the handsets in
a WLAN system. It also includes the Device Manager.
A31003-M2000-S100-2-7620, 10/2018
10WLAN Handset, Configuration Manual
1.2 Functionality matrix
The following matrix shows the functionality that currently can be used by the
different versions. These functions require configuration in the WinPDM.
WL3_CM_Ch1.fm
Introduction
Functionality matrix
WL3WL3
Messenger
Company PhonebookYesYesYes
Central PhonebookYesYesYes
Centralized ManagementYesYesYes
Customized GUIYesYesYes
System profilesNoNoYes
Interactive Messaging (IM)NoYesYes
LocationNoNoYes
Push to Talk (PTT)NoNoYes
Multifunction buttonYesYesNo
Push Button AlarmNoNoYes
Man-down and No-movement alarmNoNoYes
Acoustic Location Signal (ALS)NoNoYes
ServicesNoNoYes
Message TemplatesNoYesYes
Voice MailYesYesYes
Upload LanguageYesYesYes
Clear lists in chargerYesYesYes
The three versions WL3,WL3 Messenger Upgrade, and WL3 Plus use the same
hardware and software (except WL3 Plus, which uses a different hardware), and
features are enabled by licensing. The WL3 version is an unlicensed WLAN
Handset with basic functionality, and the WL3 Messenger UpgradeWL3 Plus
versions are licensed WLAN Handsets with additional functionalities such as
messaging and alarm, respectively.
Before installing handsets in a VoWiFi system, ensure that the following
equipment is available:
•Set up chargers and charge the handset batteries before installation.
•Have a number plan available for the handsets.
•Check that the IP addressing plan is set up to support the amount of handsets
We assume that the VoWiFi system is installed, including some or all of the
following components (depending on system configuration):
•DHCP Server. A DHCP server allows devices to request and obtain an IP
WL3_CM_Ch2.fm
Pre-Installation
to be deployed.
address from a server that has a list of addresses available for assignment. If
the WLAN does not have access to a DHCP server, a list of static IP
addresses is necessary.
•Portable Device Manager. The WinPDM is used for administration and
programming of the handsets. All settings and updates are in this case done
using the DP1 Desktop Programmer cradle connected over USB.
•WSG. The WSG handles all communication between the WLAN and its built-
in Device Manager. Before installing the handset, make sure the WSG IP
address is available.
For effective administration of a VoWiFi system with several handsets, it is
required to have both a WinPDM and a Device Manager included in the WSG. In
this case, the WinPDM is only used to allow the handset to access the WLAN
system. All other settings and updates are done with theDevice Manager in the
WSG.
To configure the handsets, enter the IP addresses in the table below.
Table 1
DeviceIP address/Number/
Required
Port
IP-PBXIf used
WSGIf used
Subnet Mask
*
If used
Number plan N/AYes
NTP Server address
DNS Server address
VoIP settings
****
**
***
Yes
Central PhonebookIf used
Syslog serverIf used
TFTP serverIf used
Ekahau RTLS
*****
If used
DHCP range
*Only required if no DHCP is used, that is, static IP is used.
**Depending on system configuration
***Only required if no DHCP is used, that is, static IP is used.
****Gatekeeper IP address or SIP proxy IP address used to access the PBX.
*****The IP address and port to the location server.
A31003-M2000-S100-2-7620, 10/2018
14WLAN Handset, Configuration Manual
3 Programming the WLAN Handset
This section describes how to configure handsets in three different ways:
•By inserting it into a DP1 Desktop Programmer cradle connected using USB
to the WinPDM.
•Over-The-Air (OTA) using the Device Manager in the WSG.
NOTE: This requires that the IP address to the WSG has been configured in the
handset. The IP address is configured using WinPDM or using the handset’s
Admin menu.
•Using the Admin menu, it is possible to configure the basic network settings.
See Chapter 9: Administration on page 143 for more information about the
settings that can be configured.
WL3_CM_Ch3.fm
Programming the WLAN Handset
It is recommended to use the Device Manager application in the WSG to
configure handsets in a large system. The Device Manager can install, upgrade,
and configure a large amount of handsets simultaneously. Another benefit is that
the collection of the handsets from users is not needed.
The WinPDM configures one handset at a time. The handset is inserted in the
DP1 Desktop Programmer, connected to the administrator’s computer using
USB.
TIP: It is recommended to use templates when configuring handsets. By using a
template, the same configuration can easily be applied to many handsets (of the
same handset version), simultaneously.
The WinPDM runs on a PC and is used to configure the handset as follows:
•Connect a DP1 Desktop Programmer cradle through a USB port, to the
•Start WinPDM.
•Place the handset in this cradle connected to WinPDM.
For instructions on how to install and use the WinPDM, see Installation and
Operation Manual, Portable Device Manager, Windows version, TD 92712EN.
Figure 2Configuration of handsets using WinPDM
computer running WinPDM.
A31003-M2000-S100-2-7620, 10/2018
16WLAN Handset, Configuration Manual
3.2 WSG
Client
Device Manager
in WSG
Access Point
VoW iFi
System
IP
AP
WL3_CM_Ch3.fm
Programming the WLAN Handset
WSG
WSG runs on an ELISE3 module.
For instructions on how to use the WSG, see Installation and Operation Manual,
OpenStage Wireless Service Gateway (WSG), TD 92442EN.
3.2.1 Over-the-Air
There is no external equipment required, besides the Device Manager application
in the WSG and the VoWiFi system. Proceed with Chapter 4: Installation of
WLAN Handsets on page 19.
Figure 3Configuration of handsets using Over-the-Air (OTA)
This section describes the recommended procedure to install and configure
handsets. There are several ways to install a handset, but the procedures
described here ensures minimal effort for the administrator.
There are two ways of configuring the handsets:
•Local management
•Centralized management (Over-the-air (OTA))
Local management of handsets
NOTE: In larger installations local management is not recommended, since it
requires physical access to all handsets.
WL3_CM_Ch4.fm
Installation of WLAN Handsets
Either the keypad on the handset, or the WinPDM is used to configure the
handsets. It is only recommended to use the keypad, if a quick change of a
parameter value is needed, for example, in a lab environment, or in a test
installation. It is tedious to enter all parameters using the keypad. Access from the
keypad is only available to a limited set of parameters, and to get access to all
parameters, the WinPDM must be used.
The WinPDM is aimed for smaller sites where the handsets are near to hand. One
handset at a time is configured, when inserted in a Desktop Programmer (DP1)
connected to the administrators computer over USB. See Chapter 4: Installation
steps in small VoWiFi Systems using WinPDM on page 21.
Centralized management of handsets
NOTE: This is also referred to as Over-The-Air (OTA) management, where
parameters changes are updated over the WLAN.
A WLAN connection and the Device Manager application (WSG) is used to
configure the handsets.
Prerequisites for Centralized management are as follows:
•The handset has a functional WLAN association.
•WLAN parameters are set correctly, to be able to connect to the Messaging
system.The handset has the correct settings to access the Device Manager
application as follows: - A configured number to be used as identity to login
to the Messaging system.
The WLAN and Messaging parameters are set manually, using the keypad or the
WinPDM. Then the handset logs into the Messaging system, and downloads the
intended handset profile, which contains all other needed parameters for a site.
See Chapter 4.2: Installation with Central Device Management (WSG) on page
23.
It is recommended to use the Easy Deployment process, where the needed
WLAN parameters and the Messaging system information is distributed
automatically to the handset, using a DHCP server (and optionally the Ascom
Service Discovery Protocol).
See Appendix C: Easy Deployment on page 163.
NOTE: If the WLAN system uses a 802.1x security protocol that requires certificates for authentication/encryption to the WLAN, the certificates must be
prepared and stored individually in the Device Manager for each number, before
starting the Easy Deployment process, see Chapter 4.2: Installation with Central
Device Management (WSG) on page 23.
See Chapter 4.1: Handset Installation in the WLAN System using Easy
Deployment on page 22.
Installation steps in large VoWiFi Systems using WSG and WinPDM
NOTE: If the handset to be installed must use a certificate to access a WLAN,
follow the instructions in section Chapter 4.3: Installation with WinPDM on page
29.
NOTE: The handset settings are unexchangeable between handset (license)
versions. For example, a number or template exported from a basic handset
version, can only be used on a basic handset, and not on a WL3 Messenger
Upgrade License, and vice versa.
These WLAN settings are common network settings for all handsets.
1. Create templates in the Device Manager in WSG, one with network settings
and another with common settings.
2. Create Numbers and apply the templates.
3. Use either the Easy Deployment procedure, or create a template with
identical network settings in the WinPDM.
A31003-M2000-S100-2-7620, 10/2018
20WLAN Handset, Configuration Manual
WL3_CM_Ch4.fm
Installation of WLAN Handsets
See Chapter 4.1: Handset Installation in the WLAN System using Easy
Deployment on page 22 or Chapter 4.2: Installation with Central Device
Management (WSG) on page 23 for more information.
Installation steps in small VoWiFi Systems using WinPDM
NOTE: The handset settings are unexchangeable between handset (license)
versions. For example, a number or template exported from a basic handset
version, can only be used on a basic handset, and not on a different handset
version, and vice versa.
1. Create Numbers.
2. Create one template for all settings in the WinPDM.
See Chapter 4.3: Installation with WinPDM on page 29 for more information.
Handset Installation in the WLAN System using Easy Deployment
4.1 Handset Installation in the WLAN System using Easy Deployment
With the Easy Deployment procedure, handsets are installed without the need for
the WinPDM.
Handsets are automatically installed if the following is fulfilled:
•The LAN and WLAN system is configured for Easy Deployment, see
Appendix C: Easy Deployment on page 163.
•The handset is not associated to any network (SSID)
•The handset software is version 5.1.18 or higher
•The Call ID (endpoint number), that is, the phone number of the handset is
decided
For further details, see Appendix C: Easy Deployment on page 163.
A31003-M2000-S100-2-7620, 10/2018
22WLAN Handset, Configuration Manual
Installation of WLAN Handsets
Installation with Central Device Management (WSG)
4.2 Installation with Central Device Management (WSG)
Easy Deployment is the recommended procedure of using the Central Device
Management (WSG) for deployment, as the WLAN and Messaging parameters
now are configured without the WinPDM.
Easy Deployment uses, in most parts, the same procedure, as the standard
Central Device Management (WSG) procedure. Special notes marked “(ED)”
show where the procedure is unique for Easy Deployment.
NOTE: (ED): With Easy Deployment, it is very important that the building of the
number plan and the parameters are correct, since the aim is to avoid using the
WinPDM.
WL3_CM_Ch4.fm
4.2.1 Create a Network Template in the Device
Manager in the WSG
Create one template that contains the network parameters (also include the
security settings). Besides the network parameters, additional parameters can
also be set, for example VoIP settings and IP address to WSG.
The template must be created, and applied, to prevent the
restoring the parameters to default during the first synchronization.
NOTE: (ED): If using Easy Deployment, the IP-address to the Device manager
in the template, can either be set, or left blank, in which case the server discovery
process is used at every startup, see Appendix C.3: WSG server discovery on
page 166.
NOTE: Only select the parameters that are modified, if all parameters are
selected, the system performance decreases.
WSG from
1. Open a web browser and enter the IP address or NetBIOS name to the WSG.
TIP: Be sure to configure all needed parameters for 802.1x security, but
installing trusted CA certificate(s) and/or application Certificate can not be
done using a template. This must be done individually on each Number, see
2. Click “Device Manager“. You might be prompted to log on the Device
Manager.
3. Select the Templates tab and click “New“. The New template window is
opened.
4. In the Device type and Parameter version drop-down lists, select the
corresponding device type and parameter version to use, respectively.
5. In the Name field, enter a descriptive name for the template.
6. Click “OK“.
Set the following network parameters:
1. Network settings (located under Network > Network A, B, C, or D):
All required system settings for the WLAN. For example SSID and Security
mode. If using a security mode that requires certificates, also use an NTP
server, to assure the correct time in the handset, as certificates only are valid
within a certain time.
2. VoIP settings (located under VoIP):
For example VoIP protocol, Gatekeeper IP address or SIP proxy IP address
used to access the PBX.
3. Syslog settings (if any) (located under Device > General):
The parameter “Syslog“ must be enabled in order to set the “Syslog IP
address“.
4. WSG settings (located under Device > WSG):
IP address and password (if any) to the WSG.
5. Click “OK“ to save the template.
TIP: See Appendix A for tip on how to work with templates when using both
WinPDM and WSG.
A31003-M2000-S100-2-7620, 10/2018
24WLAN Handset, Configuration Manual
WL3_CM_Ch4.fm
Installation of WLAN Handsets
Installation with Central Device Management (WSG)
4.2.2 Create a Common Template in the Device
Manager in the
Create another template with the common handset settings applicable to all
handsets (exclude the parameters and security settings configured in the
Network template). This template contains for example, hidden menu items in the
display, certain level of ring signals and vibrators.
NOTE: Only select the parameters that are modified, if all parameters are
selected, the system performance decreases.
1. Open a web browser and enter the IP address or NetBIOS name to the WSG.
2. Click “Device Manager“.
3. Select the Templates tab and click “New“.
WSG
4. In the Device Type and Parameter version drop-down lists, select the
corresponding device type and parameter version to use, respectively.
5. In the Name field, enter a descriptive name for the template.
6. Set the specific parameters. See section Chapter 4.5: Configure a Handset
with a Template on page 32 for more information.
4.2.3 Create Numbers in the WSG
Create a range of Numbers and apply the templates previously created in the
WSG.
NOTE: Do not add numbers for handsets that are already configured and
functional, because these handsets already exist in the system, though they are
not saved in the Device Manager application in WSG. The Device Manager application overwrites the existing parameters in the handset.
NOTE: The parameter version of the template must be equal to or less than the
selected parameter version.
1. Open a web browser and enter the address to the WSG.
3. Select the Numbers tab and click “New“. The New numbers window is
opened.
4. In the Device Type and Parameter version drop-down lists, select the device
type and the parameter version to use, respectively.
NOTE: The device type and parameter version must match the handsets to
be used to apply the template.
5. In the Prefix field, enter the numbers’ prefix (if needed).
6. Create a range of numbers by selecting the “Range“ option. Enter the start
call number and the end call number in the fields, respectively. Click “OK”.
NOTE: The maximum range that can be added at a time are 100 numbers.
7. Apply the network settings template to the selected handsets. See Chapter
4.5.2: Apply a Template to a Handset with a Number on page 33.
8. Apply the common settings template to the selected handsets. See Chapter
4.5.2: Apply a Template to a Handset with a Number on page 33.
NOTE: (ED): If the 802.1x security protocol with EAP-TLS or EAP-PEAP/
MSCHAPv2 is used, also include the include trusted CA certificate(s), select
which Application certificate to use. The Application certificates must be
installed first by editing each Number. Application certificates cannot be
distributed using a template, as they are individual.
9. Close the WSG.
A31003-M2000-S100-2-7620, 10/2018
26WLAN Handset, Configuration Manual
WL3_CM_Ch4.fm
Installation of WLAN Handsets
Installation with Central Device Management (WSG)
4.2.4 Create a Network Template with Initial
Configuration in the WinPDM
In a factory delivered handset, the WLAN settings are not configured as required
to access the WSG. Using the WinPDM allows the handset to be primed with the
WLAN parameters and allows the handset to log in to the Device Manager in
WSG for future management over the air.
Create a template with the basic network settings and IP address to WSG. This
template is only used once for each handset because it must access the WLAN
and then log on the Device Manager. After log in, the settings in the handset are
changed according to the templates, that were applied to the Numbers, in the
Device Manager application in WSG.
NOTE: If using Easy Deployment, only perform step 6) below.
1. Open the WinPDM.
2. Do one of the following:
•If a network template was created in the Device Manager in WSG, export
this template and import it to WinPDM. See Appendix A for more
information. (Recommended)
•Create a template (see Chapter 4.5.1: Create a template on page 32) with
the following network parameters:
–Network settings (located under Network > Network A, B, C, or D):
All required system settings for the WLAN. For example SSID and
Security mode.
NOTE: If the production system is using 802.1x security, this method is
not the best option, since the certificates must be manually installed in the
handset before they login for the first time (before step 6). The Easy
Deployment process overcomes this problem by using a staging WLAN,
which does not use 802.1x.
–-WSG settings (located under Device > WSG):
IP address and password (if any) to the WSG.
3. Place the handset in the Desktop Programmer (DP1) cradle.
4. Run the template. See Chapter 4.5.3: .Apply a Template to a Handset without
a Number on page 33.
5. Remove the handset when synchronization is finished.
6. Enter the Number and the password (if any). The password is only required if
the “Password“ parameter is set. Press “Login“.
7. Repeat step 3 – 6 for all handsets.
Settings that were stored for the handset in the Device Manager in WSG are
now downloaded to the handset. This can, for example, be unique soft- or hot
keys that have been prepared earlier. When the settings have been
downloaded to the handset, the handset can restart, depending on the
parameter changes.
The handset synchronizes with the WSG at startup, and also immediately
after any handset parameter change. (The change is done either using the
handset keypad, or when editing parameters in the Device Manager in the ).
Depending on what is changed, and where the change is done, the
parameters are synchronized to, or from, the handset.
Those changes are not stored in the WinPDM, as there is no connection
between the WinPDM and the WSG Device Management database. The
database in the WinPDM synchronizes with the handset, when the handset
is placed in the Desktop Programmer (DP1) cradle (online via USB).
NOTE: As there is no connection between the WinPDM and the WSG
Device Management databases, except over the handset, the WLAN and
WSG settings can differ in the WinPDM and the WSG. Parameters can
inadvertently be reverted with old values, when first, the WinPDM synchronization process runs, (when the handset is placed in the Desktop Programmer
(DP1) cradle), and after that, (when the handset is removed from the Desktop
Programmer (DP1) cradle), the handset goes online with the Messaging
system, and the synchronization process with the WSG runs, and vice versa.
The solution for this, is to avoid storing handset numbers in the WinPDM.
A31003-M2000-S100-2-7620, 10/2018
28WLAN Handset, Configuration Manual
4.3 Installation with WinPDM
In a small VoWiFi system, the administration can be handled using only the
WinPDM.
The synchronization is in this case not handled automatically by the system when
a handset’s parameters are changed in the WinPDM. When the parameters have
been changed in WinPDM, each handset must be placed in the Desktop
Programmer (DP1) cradle connected to the administrator’s computer in order to
synchronize the parameters with the handset.
1. Open the WinPDM.
2. In the Numbers tab, click “New“. The New numbers window is opened.
3. In the Device Type and Parameter version drop-down lists, select the
matching device type and the parameter version for the handset to be used,
respectively.
WL3_CM_Ch4.fm
Installation of WLAN Handsets
Installation with WinPDM
4. In the Prefix field, enter the numbers’ prefix (if needed).
5. Create a range of numbers by selecting the “Range“ option. Enter the start
call number and the end call number in the fields, respectively.
6. Click “OK”.
7. Create a network settings template (see Chapter 4.5.1: Create a template on
page 32) with the following network parameters:
•Network settings (located under Network > Network A, B, C, or D):
All required system settings for the WLAN. For example SSID and Security
mode, and if used, any certificates for 802.11x.
8. Create another template (see Chapter 4.5.1: Create a template on page 32)
with the common handset settings applicable to all handsets (exclude the
network parameters and used security settings). Example of parameters
settings:
•VoIP settings (located under VoIP):
VoIP protocol, Gatekeeper IP address or SIP proxy IP address used to
access the PBX.
•Software TFTP IP address (if any) (located under Device > General)
•Syslog settings (if any) (located under Device > Log):
The parameter “Syslog“ must be enabled in order to set the “Syslog IP
address“.
In addition, settings for hiding menu items in the display, certain level of ring
signal and vibrators etc. can also be configured.
9. Apply the network settings template to the handset, see Chapter 4.5.2: Apply
a Template to a Handset with a Number on page 33.
10. Apply the common settings template to the handset, see Chapter 4.5.2: Apply
a Template to a Handset with a Number on page 33.
11. Place the handset in the Desktop Programmer (DP1) cradle.
12. In the Device Wizard window, select “Associate with number“ and press “OK“.
13. Select the handset to associate with. Press “OK“.
The number and parameter settings saved in the WinPDM are now
synchronized with the handset. In addition, the handset’s Device ID is also
synchronized with the number in the WinPDM.
If certificates must be used to access a VoWiFi system, also perform the steps
14 - 19.
14. In the Numbers tab, right-click the handset’s number and select “Manage
certificates“. A manage certificate window opens.
15. In the Trust list tab and Application certificates tab, click “Browse“ and select
the certificates to import. Click “Close“.
16. In the Numbers tab, right-click the handset’s number and select “Edit
parameters“.
17. Select “Network X“ (X represents A, B, C, or D).
18. In the Security mode drop-down list, select “EAP-TLS“.
19. In the EAP application certificate drop-down list, select the application
certificate to be used. Click “OK“.
20. Remove the handset when synchronization is finished.
Repeat the steps 11-13, 20 (if needed, perform the steps 14-19) for all
handsets.
A31003-M2000-S100-2-7620, 10/2018
30WLAN Handset, Configuration Manual
Installation using the Handset’s Admin Menu
4.4 Installation using the Handset’s Admin Menu
It is possible to install a handset using its Admin menu. This is useful when no
WinPDM or WSG is available and the handset needs to be installed quickly.
NOTE: It is only possible to configure the basic settings through the Admin
menu.
There are two options to access the Admin menu:
•If the handset has been factory reset or not been configured; in idle mode,
enter 40022.
•If the handset has been configured; press “Menu“, select “Settings“ and enter
40022.
Set the following parameters:
WL3_CM_Ch4.fm
Installation of WLAN Handsets
1. Network settings (located under Network setup):
All required system settings for the WLAN. For example SSID and Security
mode. Note that the certificates cannot be entered, nor referred to, using the
keypad.
2. VoIP settings (located under VoIP):
VoIP protocol, Gatekeeper IP address or SIP proxy IP address used to
access the PBX.
3. WSG settings (if any) (located under WSG)
IP address and password (if any) to the WSG.
4. Syslog settings (if any) (located under Syslog)
The parameter “Syslog“ must be enabled in order to set the “Syslog IP
address“.
5. Add license key (if any) (located under Enter license key)
It is possible to select a handset in the WinPDM and directly change one or more
configuration parameters. By using a template, the same configuration can easily
be applied to many handsets simultaneously. Templates are also an efficient way
to control the changes applied to each handset.
Templates enables configuration of all aspects of a handset from sound volume
to keypad shortcuts.
Your supplier can provide example templates for different PBX:s. The handset
has full functionality towards the PBX even without such a template. By using
such a template, though, the handset is customized for that PBX with menu
options for PBX specific functions.
4.5.1 Create a template
1. Open the WinPDM or the Device Manager in the WSG.
2. Select the Templates tab and open the menu “Template > New...“. The New
Template window is opened.
3. Select the device type and parameter version that matches the software
version installed on the handset. Give the template a descriptive name.
The parameters that are not part of the template are left unchanged on the
handset. The parameter version of an installed handset is visible under the
Numbers tab or the Devices tab.
4. Click “OK“.
5. Select the check box of each parameter that you want to be part of this
template and enter the proper value.
6. Click “OK“ to save the template.
A31003-M2000-S100-2-7620, 10/2018
32WLAN Handset, Configuration Manual
WL3_CM_Ch4.fm
Installation of WLAN Handsets
Configure a Handset with a Template
4.5.2 Apply a Template to a Handset with a Number
1. Open the WinPDM or the Device Manager in the WSG.
2. In the Numbers tab, select the handset(s) you want to apply the template to.
NOTE: If several handsets are selected, they must be of the same device
type and have the same parameter version.
3. Right-click and select “Run template...“.
Only templates with a parameters version matching the selected handsets
are shown. Select the template you want to apply and click “OK“.
The template is applied. The number of parameters in the template affects the
time it takes to apply the template to the selected handsets.
When looking at a handset under the Numbers tab, the column “Last run
template“ shows the name of the most recently applied template.
4.5.3 .Apply a Template to a Handset without a
Number
This feature is only applicable for the WinPDM. It is possible to apply a template
to a handset without a number in the WinPDM.
1. Place the handset in the Desktop Programmer (DP1) cradle.
2. In the Found Device Wizard window, select the “Run template“ option.
3. Click “Next >“.
Only templates with a parameter version matching the selected handset are
shown.
4. Select the desired template and click “OK“.
The template is applied. The number of parameters in the template affects the
time it takes to apply the template to the selected handset.
It is possible to save all settings of a handset as template. Note that this does not
include contacts, certificates and other personal data. The template will only
contain configuration data.
This template can be used as a backup if you want to restore the configuration of
the handset at a later stage or as a template that can be applied to a number of
handsets.
1. Open WinPDM or the Device Manager in the WSG.
2. In the Numbers tab, select the handset you want to save as a template.
3. Make a right-click and select “Use as a template...“. Enter a descriptive name
4. The Edit template window is opened. By default, all parameters are selected
for the template.
and are saved when clicking “OK“.
If one or more parameters should be excluded, remove them by clearing the
check box next to the parameter.
Some parameters are user specific. If it is decided to apply this type of
template to several handsets, it is recommended to exclude the following
parameters:
•User display text - A text string displayed in idle mode. The parameter is
located directly under “Settings“.
•Phone lock PIN code - The security code used to unlock the keypad. The
parameter is located under Settings > Locks.
•Endpoint ID - The identity/name of the user registered in the PBX. The
parameter is located under VoIP > General.
5. Click “OK“.
A31003-M2000-S100-2-7620, 10/2018
34WLAN Handset, Configuration Manual
WL3_CM_Ch4.fm
Installation of WLAN Handsets
Configure a Handset with a Template
4.5.5 Synchronizing a Handset with WinPDM
After installing and saving a handset, it is synchronized each time it is connected
to the WinPDM. The synchronization transfers parameter changes between the
handset and the WinPDM and vice versa as follows:
•If a parameter has been changed in the handset, it is transferred to the
WinPDM/WSG.
•If a parameter has been changed in the WinPDM/WSG while the handset was
disconnected, it is transferred to the handset.
If the same parameter has been changed in both the WinPDM/WSG and the
handset, the value in WinPDM/WSG will be transferred to the handset.
4.5.6 Configure Handset without Saving It in WinPDM
It is possible to configure a handset without saving it in the WinPDM. An unsaved
handset does not have the symbolin the Saved column. The settings in the
handset can be synchronized and saved in the WinPDM later on. However, it is
recommended to save the handset in WinPDM, if backup is required. For
example when a handset needs to be replaced.
1. Place the handset in the Desktop Programmer (DP1) cradle.
2. Open WinPDM.
3. In the Numbers tab, select the unsaved handset you want to configure.
4. Select Number > Edit parameters.
5. The Edit parameters window is opened. Edit the parameters of the handset
and click “OK“.
6. Remove the handset from the Desktop Programmer (DP1) cradle. The
handset is no longer visible in the WinPDM and the settings are only saved in
the handset.
In an existing VoWiFi system, it is important to be able to replace handsets, install
new handsets, and exchange faulty handsets. The recommended procedure is to
use a template with basic network settings for log in, created in the WinPDM, and
then import the rest of the settings that were created by the templates in Device
Manager in WSG
It is also important to be able to upgrade system parameters and security settings
in the handsets. These upgrades are preferably done in the WSG, if available.
If you use WinPDM and WSG, do one of the following:
•If you want to install new handset, see Chapter 4.2: Installation with Central
Device Management (WSG) on page 23.
•If you want to create spare handsets to be used when broken handsets need
to be replaced later on, see 5.1.1 Configure Spare Handsets without a
Number in Large Systems.
•If only WinPDM is used, do one of the following:
•If you want to install new handset, see Chapter 4.3: Installation with WinPDM
on page 29.
•If you want to replace a broken handset, see Chapter 5.2.4: Replacement of
5.1.1 Configure Spare Handsets without a Number in
Large Systems
In large systems where WSG is used, it is recommended to configure a few spare
handsets without a number to quickly replace a broken handset later on.
Create a Template
1. Open WinPDM.
2. Select the Templates tab and click “New“. The New template window is
opened.
3. In the Device type and Parameter version drop-down lists, select the
matching device type and parameter version respectively, for the spare
handset to use.
4. In the Name field, enter a descriptive name of the template.
5. Click “OK“.
6. Set the following network parameters:
•Network settings (located under Network > Network A, B, C, or D):
All required system settings for the WLAN. For example SSID and Security
mode.
•VoIP settings (located under VoIP):
For example VoIP protocol, Gatekeeper IP address or SIP proxy IP address
used to access the PBX.
•Syslog settings (if any) (located under Device > General):
The parameter “Syslog“ must be enabled in order to set the “Syslog IP
address“.
•WSG settings (if any) (located under Device > WSG):
7. IP address and password (if any) to the WSG.
8. Click “OK“ to save the template.
Apply Template to a Handset without a Number
1. Place the handset in the Desktop Programmer (DP1) cradle.
2. In the Found Device Wizard window, select the “Run template“ option.
3. Click “Next >“.
A31003-M2000-S100-2-7620, 10/2018
38WLAN Handset, Configuration Manual
WL3_CM_Ch5.fm
Handset
Handset
Only templates with a parameter version matching the selected handset are
shown.
4. Select the desired template and click “OK“.
The template is applied. The number of parameters in the template affects the
time it takes to apply the template to the selected handset.
5. Switch off the handset when User name and Password are displayed.
TIP: If the handset replaces a broken handset, continue with Chapter 5.2.2:
Replacement of Handset with WSG on page 47.
5.1.2 Upgrade Handset Software
NOTE: Read the software Release Notes before changing the software.
The handset software can be upgraded over the air using Centralized Device
Management (WSG) or a TFTP server, or by cable using WinPDM.
Upgrade Handset Parameter
A parameter upgrade can restart the handset, for example, when upgrading the
NTP server. The text “Remotely updated” is shown in the handset display when
the handset restarts after an upgrade.
5.1.3 Upgrade Software OTA using TFTP
If no WSG is available, it is recommended to use software upgrade OTA using
TFTP, which is used in small VoWifi systems.
The benefit is that the handsets do not need to be collected by the administrator
since the software upgrade is performed over the air.
To upgrade the software using TFTP, perform the following:
1. If needed, configure the handset in WinPDM to access a TFTP server, see
Configure Access to the TFTP Server.
TIP: It is recommended to configure the TFTP server’s IP address when
installing the handsets. See Chapter 4.3: Installation with WinPDM on page
2. If needed, upload a new software information file (packageinfo.inf) and a
software (.bin) file to the TFTP server. These files are provided by your
supplier. First rename the .pkg file to .zip and then unzip the files. Then the
needed .inf and .bin files are available.
See the manual for the TFTP server used, for more information on how to
upload files.
3. Restart the handset. After the handset restarts, it connects to the TFTP server
and downloads the software information file (.inf) that contains information
about the software version. If the software version differs from the handset’s
software version, the handset downloads the software file (.bin) from the
TFTP server. The handset restarts when the software upgrade is performed.
Configure Access to the TFTP Server
1. Place the handset in the Desktop Programmer (DP1) cradle.
2. Open the WinPDM.
3. Open the Numbers tab and select the handset.
4. Right-click and click “Edit parameters“.
5. Select Device > General.
6. In the Software TFTP IP address field, enter the IP address to the TFTP
server.
7. Click “OK“.
5.1.4 Upgrade Software using WinPDM
Software upgrade using WinPDM is performed in small VoWiFi systems. The
handsets need to be collected by the administrator because the software is
upgraded using the connected to WinPDM.
1. Open the WinPDM.
2. In the Devices tab, right-click the handset to be upgraded. Select “Upgrade
software...“.
3. In the Available files drop-down list, select the desired software file (.bin).
4. If needed, import the software file to be used by clicking “Import“. Locate the
software file (.bin or .pkg) and click “Open“.
5. Click “OK“. The dialog window “Shutting down” followed by “Remotely
updated” is shown in the handset display.
A31003-M2000-S100-2-7620, 10/2018
40WLAN Handset, Configuration Manual
WL3_CM_Ch5.fm
Handset
Handset
5.1.5 Upgrade Software Over the Air (OTA) through
Centralized Device Management (WSG)
Software upgrade using WSG is performed in large VoWiFi systems. The benefit
is that the handsets do not need to be collected by the administrator because the
software upgrade is performed over the air (OTA).
1. Open the Device Manager in the WSG.
2. Open the Devices tab and select the handsets to be upgraded.
3. Right-click and click “Upgrade software...”.
4. In the Available software drop-down list, select the desired software file (.bin).
5. If needed, import the software file to be used by clicking “Import“. Locate the
software file (.bin or .pkg) and click “Open“.
6. In the Upgrade section and Activate new software section, select when the
software is upgraded and activated on the handset, respectively.
7. Click “OK“.
TIP: It is also possible to upgrade several handsets of the same device type
simultaneously using the Baseline function in the WSG. See Installation and
Operation Manual, OpenStage Wireless Service Gateway (WSG), TD 92442EN.
5.1.6 Recapture the Earlier Software
The handset stores two software versions which makes it possible to force the
handset to jump back to the earlier software. This feature is used if the current
software does not work properly.
NOTE: The handset must be switched off to be able to load the earlier software.
Press and hold the keys “7” and “8” and press On/Off key at the same time. The
handset loads the earlier software and keeps it, if the handset is not restarted.
Users can upgrade a handset by downloading a license. The following license is
available:
•WL3 Messenger Upgrade License
There are three alternatives to upgrade a handset:
•Automatic upgrade, see Automatic license upgrade.
•License upgrade using import/export, see License upgrade using import/
export.
•Manual upgrade, see Manual license upgrade.
NOTE: A license move, from one handset to another, requires internet access
from either the PC (with WinPDM), or the WSG server.
NOTE: A handset can be re-licensed up to 99 times.
Automatic license upgrade
Use this option if the WinPDM has an internet connection to the License Server.
1. Open the WinPDM.
2. Place the handset in the Desktop Programmer (DP1) cradle.
irst time the handset logs on the WinPDM, the license key is automatically
downloaded to the handset, go to step 4.
3. If the handset is logged on to the WinPDM after the first time, no automatic
check for licenses is done. Synchronize the WinPDM and license server as
follows:
•Select the “Licences“ tab.
•Right-click the handset in the list.
•Select “Refresh“.
The license key is downloaded to the handset.
4. The handset restarts. See also Chapter 5.1.7: Upgrade Handset
Functionality using License on page 42 to view the handset’s license
option(s).
A31003-M2000-S100-2-7620, 10/2018
42WLAN Handset, Configuration Manual
WL3_CM_Ch5.fm
Handset
Handset
If the handset is updated to a new device type (to WL3 Messenger Upgrade
License), both the new device and the old device is displayed in WinPDM.
The old device has to be manually removed.
License upgrade using import/export
Use this option if the WinPDM has no internet connection to the License Server.
A product information file (.XML) must first be exported from the WinPDM, and
then imported to the License Web.
1. Place the handset in the Desktop Programmer (DP1)cradle.
2. Open the WinPDM.
•Select the “Licences“ tab.
•Right-click the handset(s) in the list.
•Select “Export“.
•Save the file on a computer with an internet connection to access the
License Web later on.
3. In a web browser, enter the address to the License Web:
“https://www.xxxxxxxxxx“
The License Web is used for;
•Importing the product information file
•Viewing/Purchasing the license(s) for the handset(s)
•Downloading the license file containing the license key(s) for the
handset(s)
See the online help on the License Web for information on how to use the
License Web.
4. When the license file (.XML) containing the license key(s) is downloaded from
the License Web, select File > Import > Licences in the WinPDM to import the
file.
5. When the file is imported, the license key(s) is downloaded to the handset(s),
and the handset restarts. See also Chapter 5.1.7: Upgrade Handset
Functionality using License on page 42 to view the handset’s license
option(s).
If the handset is updated to a new device type (to WL3 Messenger Upgrade
License), both the new device and the old device are displayed in WinPDM.
The old device has to be manually removed.
Use this option if the serial numbers of the handset cannot be exported to a file
because a WinPDM is not in use. The serial number(s) must be manually entered
in the License Web to get the corresponding license key for the handset. The
license key must also be manually entered in the handset. See the online help on
the License Web for information on how to get a license key.
TIP: If several handsets are upgraded, it is recommended to use Chapter 5.1.7:
License upgrade using import/export on page 43.
The license key is added using the Admin menu in the handset, see Chapter 9.1:
Admin Menu Tree on page 143 for information on how to activate the Admin
menu.
TIP: It is also possible to press *#35# in idle mode for quick access to the “Enter
license key“ menu.
1. Press the soft key “Menu“.
2. Select “Calls“.
3. Select “Admin menu“.
4. Select “Enter license key“.
5. Enter license key without blanks.
6. Press “OK“.
If the license key is valid, a dialog window “License key accepted“ is shown. The
handset restarts.
If the handset has been updated to a new device type (to WL3 Messenger
Upgrade License), both the new device and the old device are displayed in
WinPDM. The old device has to be manually removed.
Move License
It is possible to move a product license (WL3 Messenger Upgrade License) to an
unlicensed handset. Any optional licenses follow. For example, aWL3
Messenger Upgrade license can be moved from a handset with a broken display
to an unlicensed handset. The broken handsetcan then be sent for repairs.
Prerequisites: A WinPDM that supports the move license function, and a
connection to the license server.
To move a license using the WinPDM:
1. Place the licensed handset in the desktop programmer.
2. On the Licenses tab, select the handset online.
3. On the License menu, click “Move license...”.
A31003-M2000-S100-2-7620, 10/2018
44WLAN Handset, Configuration Manual
WL3_CM_Ch5.fm
Handset
Handset
4. In the Move license dialog, select the unlicensed handset and click “OK”.
The handset in the desktop programmer is restarted.
5. Place the unlicensed handset in the desktop programmer.
6. On the Licenses tab, select the handset online.
7. On the License menu, click “Refresh”.
8. The handset in the desktop programmer is restarted.
5.1.8 Perform a Factory reset
When a factory reset is done on a handset, all configuration settings are restored
to default values; PBX subscriptions, contacts, messages, downloaded
language, certificate etc. are removed. The software and licensesare left intact.
Factory Reset using WinPDM or Device Manager (WSG)
1. Open the WinPDM.
2. Place the handset in the Desktop Programmer (DP1) cradle.
3. In the Device tab, mark the handset to be factory reset. Note that the handset
must be online.
4. In the Device menu, select “Factory reset“. Alternatively, right-click the
handset and select “Factory reset“.
5. A Reset devices window appears, click “Yes“. The handset is restarted.
Factory Reset using Handset
It is possible to factory reset a handset from its Admin menu.
1. To activate the Admin menu, select Menu > Settings and enter 40022.
2. Select “Factory Reset“.
3. A Reset portable? window appears, press “Yes“. The handset is restarted.
A handset can be replaced with a spare handset if it is broken. The handset
registered in WinPDM or WSG, is associated with its device type, device ID, and
extension. During the replacement procedure, the broken handset’s device type
and extension are associated with the spare handset’s device ID.
5.2.1 Replacement Procedure Choice
•If you have WSG and already have applied the network template to the spare
handset(s) to log on later, see Chapter 5.2.2: Replacement of Handset with
WSG on page 47.
•If you have both WinPDM and WSG, and need to apply the network template
to the spare handset(s) to log on later, see 5.2.3 Replacement of the Handset
with WinPDM and WSG.
•If you only have WinPDM, see 5.2.4 Replacement of Handset with WinPDM
Only.
Data included in a replacement transfer
The following data is replaced during a replacement:
•User parameters
•Contacts (entered by the user)
Note that the following data is not replaced:
•Call list
•Messages
•Company phonebook
•Downloaded language
•Certificates
•Licenses
TIP: A handset’s license(s) can be moved to an unlicensed handset (WL3) if
following the replacement instructions in Chapter 5.2.2: Replace and Move
Licenses in WSG on page 47.
A31003-M2000-S100-2-7620, 10/2018
46WLAN Handset, Configuration Manual
WL3_CM_Ch5.fm
Handset
Replacement of Handsets
5.2.2 Replacement of Handset with WSG
There are two different replacement procedures as follows:
•If the broken handset and the spare handset have the same device type and
functionality license, see Replace without Move Licenses in WSG.
•If the broken handset and the spare handset do not have the same device
type and/or functionality license, the license must be moved to the spare
handset, see Chapter 5.2.2: Replace and Move Licenses in WSG on page
47.
Replace without Move Licenses in WSG
Both the broken handset and the spare handset must be of the same device type
and have same functionality license.
1. In both handsets, press *#34# in idle mode and select “License“ to check that
they have same device type and licenses.
If the login screen is displayed in the spare handset, press “Info“, and select
“License“.
2. If the broken handset is online in the Device Manager, switch off the handset
to make it offline.
3. Take a spare handset prepared with the network settings (including the IPaddress to the WSG).
4. Enter the number and leave the password blank. Press “Login“.
The spare handset is automatically updated from the WSG and might be
restarted depending on the changed settings. The last stored settings for the
broken handset in the WSG are transferred to the spare handset.
Replace and Move Licenses in WSG
The broken handset and the spare handset do not have the same device type
and/or have the same functionality license.
The spare handset must be an unlicensed WL3 to move the licenses to the spare
handset. To check that the handset is unlicensed, press *#34# in idle mode and
select “License“. Only WL3 must be displayed here.
1. Make sure that the broken handset is saved in the Device Manager (indicated
by a in the Saved column. If not, in the Numbers tab, right-click the broken
handset and select “Save“.
2. Switch the broken handset off. The handset appears as offline in the Device
Manager.
3. Take an unlicensed spare handset (WL3) prepared with the network settings
(including the IP-address to the WSG).
4. Enter the number and leave the password blank. Press “Login”. The handset
is now online in the Device Manager.
5. Make sure that the spare handset is saved in the Device Manager (indicated
by a in the Saved column. If not, in the Numbers tab, right-click the spare
handset and select “Save“.
6. Switch the spare handset off. The handset appears as offline in the Device
Manager.
7. Switch the broken handset on. The handset appears as online in the Device
Manager.
8. In the Device Manager, select the “Licenses“ tab.
9. Right-click the broken handset and select “Move license...“.
10. In the Move license window, select the WL3 that should receive the license.
Press “OK“.
11. The broken handset restarts and has now become a WL3. Switch the broken
handset off. The handset appears as offline in the Device Manager.
12. Switch the spare handset on. The handset appears as online in the Device
Manager.
13. In the Device Manager, select the “Licenses“ tab. Right-click the spare
handset and select “Refresh“.
The spare handset is automatically updated from the WSG and restarted. The
last stored settings and licenses for the broken handset in the WSG are
transferred to the spare handset.
A31003-M2000-S100-2-7620, 10/2018
48WLAN Handset, Configuration Manual
WL3_CM_Ch5.fm
Handset
Replacement of Handsets
5.2.3 Replacement of the Handset with WinPDM and
WSG
If the spare handset to be used must be factory reset or no network template has
been applied, a WinPDM is needed to apply the network template to the spare
handset. When the network template is added, the handset can log on to the
Device Manager.
There are two different replacement procedures:
•If the broken handset and the spare handset have the same device type and
functionality license, see Replace without Move Licenses using WinPDM and
WSG.
•If the broken handset and the spare handset do not have the same device
type and/or functionality license. The license must be moved to the spare
handset, see Chapter 5.2.3: Replace and Move License using WinPDM and
WSG on page 50.
Replace without Move Licenses using WinPDM and WSG
Both the broken handset and the spare handset must be of the same device type
and have same functionality license.
1. In the handset, press *#34# in idle mode, and select “License“ to check that
both handsets have same device type and licenses.
2. Make sure that the broken handset is saved in the Device Manager (indicated
by a in the Saved column. If not, in the Numbers tab, right-click the broken
handset and select “Save“.
3. Switch the broken handset off. The handset appears as offline in the Device
Manager.
If the spare handset is not prepared with the basic network settings, also
perform the steps 4 - 7.
4. Open the WinPDM.
5. Place the spare handset in the Desktop Programmer (DP1) cradle.
6. Run the template with the basic network settings containing (see Chapter 4.5:
Configure a Handset with a Template on page 32):
•Network settings (located under Network > Network A, B, C, or D):
All required system settings for the WLAN. For example SSID and
Security mode.
VoIP protocol, Gatekeeper IP address or SIP Proxy IP address used to
access the PBX.
•WSG settings (located under Device > WSG):
IP address and password (if any) to the WSG.
7. Remove the handset from the Desktop Programmer (DP1) cradle. The
handset restarts, depending upon parameter changes.
8. Enter the number and the password (if any). The password is only required if
the “Password“ parameter is set. Press “Login”.
The spare handset is automatically updated from the WSG and restarts,
depending upon parameter changes. The last stored settings for the broken
handset in the WSG are transferred to the new handset.
Replace and Move License using WinPDM and WSG
The broken handset and the spare handset do not have the same device type
and/or have the same functionality license.
The spare handset must be an unlicensed WL3 to move the licenses to the spare
handset. To check that the handset is unlicensed, press *#34# in idle mode, and
select “License“. Only WL3 must be displayed here.
1. Make sure that the broken handset is saved in the Device Manager (indicated
by a in the Saved column. If not, in the Numbers tab, right-click the broken
handset and select “Save“.
2. Switch the broken handset off, to take the handset offline.
3. Open the WinPDM.
4. Place the unlicensed spare handset (WL3) in the Desktop Programmer (DP1)
cradle.
5. Run the template with the basic network settings containing (see Chapter 4.5:
Configure a Handset with a Template on page 32):
•Network settings (located under Network > Network A, B, C, or D):
All required system settings for the WLAN. For example SSID and
Security mode.
•VoIP settings (located under VoIP):
VoIP protocol, Gatekeeper IP address or SIP Proxy IP address used to
access the PBX.
•WSG settings (located under Device > WSG)
IP address and password (if any) to the WSG.
A31003-M2000-S100-2-7620, 10/2018
50WLAN Handset, Configuration Manual
WL3_CM_Ch5.fm
Handset
Replacement of Handsets
6. Remove the handset from the Desktop Programmer (DP1) cradle. The
handset restarts.
7. Enter the number and the password (if any). The password is only required if
the “Password“ parameter is set. Press “Login”.
8. Make sure that the spare handset is saved in the Device Manager (indicated
by a in the Saved column. If not, in the Numbers tab, right-click the spare
handset and select “Save“.
9. Switch the spare handset off, to take the handset offline.
10. Switch the broken handset on, to take the handset online.
11. In the Device Manager, select the “Licenses“ tab.
12. Right-click the broken handset and select “Move license...“.
13. In the Move license window, select the WL3 that should receive the license.
Press “OK“.
14. The broken handset restarts and has now become a WL3. Switch the broken
handset off. The handset appears as offline in the Device Manager.
15. Switch the spare handset on. The handset appears as online in the Device
Manager.
16. In the Device Manager, select the “Licenses“ tab. Right-click the spare
handset and select “Refresh“.
The spare handset is automatically updated from the WSGand restarted. The last
stored settings and licenses for the broken handset in the WSG are transferred
to the spare handset.
Replacement through WinPDM is used in small VoWiFi systems or when WSG is
not available.
•If the broken handset and the spare handset have the same device type and
functionality license, see Replace without Move Licenses using WinPDM.
•If the broken handset and the spare handset do not have the same device
type and/or functionality license. The license must be moved to the spare
handset, see Replace and Move Licenses using WinPDM.
Replace without Move Licenses using WinPDM
Both the broken handset and the spare handset must be of the same device type
and have same functionality license.
1. In both handset, press *#34# in idle mode and select “License“ to check that
they have same device type and licenses.
Alternatively, if the spare handset has been factory reset, press “Info“ and
select “License“.
2. Place the broken handset in the Desktop Programmer (DP1) cradle.
3. Open the WinPDM.
4. Make sure that the handset is saved in the WinPDM. In the Numbers tab, a
saved handset has the symbolin the Saved column. If not, right-click the
handset and select “Save“ to transfer the settings to the spare handset later
on.
5. If the spare handset has been previously used, perform a factory reset, see
Chapter 5.1.8: Perform a Factory reset on page 45.
6. Place the spare handset in the Desktop Programmer (DP1) cradle.
7. A Found Device Wizard window appears. Select “Associate with Number“
and click “Next >“.
8. In the list, select the broken handset to be replaced with the spare handset.
Click “OK“.
The broken handset is replaced and its settings are transferred to the spare
handset.
Replace and Move Licenses using WinPDM
The broken handset and the spare handset do not have the same device type
and/or have the same functionality license.
A31003-M2000-S100-2-7620, 10/2018
52WLAN Handset, Configuration Manual
WL3_CM_Ch5.fm
Handset
Replacement of Handsets
The spare handset must be an unlicensed WL3 to move the licenses to the spare
handset. To check that the handset is unlicensed, press *#34# in idle mode and
select “License“. Only WL3 must be displayed here.
1. Place the broken handset in the Desktop Programmer (DP1) cradle.
2. Open the WinPDM.
3. Make sure that the broken handset is saved in the WinPDM. In the Numbers
tab, a saved handset has the symbolin the Saved column. If not, right-click
the handset and select “Save“ in order to transfer the settings to the spare
handset later on.
4. Place an unlicensed spare handset () in the Desktop Programmer (DP1)
cradle.
5. Run the template with the basic network settings containing (see Chapter 4.5:
Configure a Handset with a Template on page 32):
•Network settings (located under Network > Network A, B, C, or D):
All required system settings for the WLAN. For example SSID and Security
mode.
•VoIP settings (located under VoIP):
VoIP protocol, Gatekeeper IP address or SIP Proxy IP address used to
access the PBX.
The handset can be restarted depending on parameter changes.
6. Place the broken handset in the Desktop Programmer (DP1) cradle.
7. In the WinPDM, select the “Licenses“ tab.
8. Right-click the broken handset and select “Move license...“.
9. In the Move license window, select the WL3 that should receive the license.
Select “Do Nothing”. The broken handset restarts and has now become a
WL3.
10. Place the spare handset in the Desktop Programmer (DP1) cradle. The spare
handset is restarted and the licenses for the broken handset in the WinPDM
has been transferred to the spare handset.
11. A Found Device Wizard window appears. Select “Associate with Number“
and click “Next >“.
12. In the list, select the broken handset to be replaced with the spare handset.
Click “OK“.
The spare handset can be restarted and the settings for the broken handset in the
WinPDM are transferred to the spare handset.
It is possible to change the number of a handset, but keep all other settings in the
handset.
1. Open WinPDMor the Device ManagerWSG.
2. Open the Numbers tab, and select the handset to be updated with a new
number.
3. In the Number menu, select “Rename...“. Alternatively, right-click the handset
and select “Rename...” from the menu that appears.
4. In the New prefix field, enter the new prefix (if needed).
5. In the New number field, enter the new number.
NOTE: Make sure that the new number does not exist in another system. If
several handsets have the same number, their settings overwrite each other
when synchronizing with WSG/ or WinPDM.
6. Click “OK“.
The new number is synchronized with the handset when it is connected to
WinPDM or WSG.
A31003-M2000-S100-2-7620, 10/2018
54WLAN Handset, Configuration Manual
5.4 Update Parameters using WSG
This section describes the general procedure to change/update parameters using
the WSG. The update starts when the handset is idle and does not interrupt an
ongoing call.
NOTE: Only select the parameters that are changed, if all parameters are
selected, the system performance decreases.
1. Open the WSG.
2. Create a new template with only the parameters to be changed.
3. Select the numbers that should be updated and apply the template.
The handsets are automatically updated from the WSGand can be restarted
depending on which parameters are changed.
This section describes how to perform an update/change of the WLAN password/
authentication using the WSG.
Change settings in the handset before change settings in the AP. Else,
synchronization of new settings to the handset settings cannot be
performed.
TIP: Leave one access point with the old configuration to allow switched off
handsets to receive the updates when they are turned on. Bring the handset to
that APs coverage area.
1. Open the WSG.
2. Create a new template with the new security settings.
•Security mode:
All required settings for the WLAN. For example User name, Password,
Regulatory domain etc.
3. Apply the new template to the handsets.
The handsets are automatically updated from the WSG and restarted.
NOTE: At this time, the handsets have no access to the WLAN system.
4. Change the security settings for the APs.
The handsets are now able to access the WLAN.
A31003-M2000-S100-2-7620, 10/2018
56WLAN Handset, Configuration Manual
5.6 Upgrade the Template
The upgrade procedure of the templates definition version is described in the
Installation and Operation Manual, Portable Device Manager, Windows version,
TD 92712ENInstallation and Operation Manual, OpenStage Wireless Service
Gateway (WSG), TD 92442EN.
5.7 Create a Configuration Backup
It is recommended to have a backup of the configuration in the handsets and the
site.
The backup procedure is described in the Installation and Operation Manual,
OpenStage Wireless Service Gateway (WSG), TD 92442EN.
NOTE: This section describes settings in parameter definition files (.def). These
files are regularly updated and settings can change slightly. For example "On" to
"Enable" or a parameter can be moved to another directory.
The handset requires some settings to function in the VoWiFi system. All settings
are done in the WinPDM/WSG. This section describes the available settings for
the handset. The first part explains network settings and the second part explains
the handset settings.
For more information, see the WinPDM Online Help that is accessible for each
parameter by clicking the icon in the Edit parameters view, or the Installation
and Operation Manual, OpenStage Wireless Service Gateway (WSG),
TD 92442EN.
WL3_CM_Ch6.fm
Handset Configuration
Select Network
6.1 Select Network
The handset can switch between four different WLAN system configurations
called Network A, Network B, Network C, and Network D. The name can be
changed (using WinPDM or WSG) and is visible in the handset, see Chapter
6.1.2: Change Name of Network on page 60.
A handset can be configured for up to four different WLANs but only for oneWSG
and one VoIP System.
The configured networks in WinPDM must have a SSID value to view them in the
handset.
Network A is the default system and used throughout this manual.
1. Select Network > General.
2. In the Active network drop-down list, select “Network A”.
6.1.1 Change Active Network
1. Select Network > General.
2. In the Active network drop-down list, select “Network A“, “Network B“,
“Network C“, or “Network D“.
The name is shown when selecting network in the handset.
1. Select Network > Network A (or B, C, or D).
2. In the Network name field, enter the name of the network.
6.1.3 Enable Switch between Networks
The handset can be configured to switch between networks on the site.
1. Find parameter Network > General > Auto-switch network, and select
“Enable”.
Parameter Auto-switch network time-out appears. This parameter defines the
time before the handset tries to connect with the next included network.
2. Enter a value in seconds for parameter Auto-switch network time-out.
3. For the networks that should be included in the auto-switch network:
Find parameter Network > Network A (B, C, D) > Include in auto-switch
network, and select “Yes” to enable switch to Network A (B, C, D).
A31003-M2000-S100-2-7620, 10/2018
60WLAN Handset, Configuration Manual
6.2 IP Address Settings
The IP address settings can be configured in two ways.
•The handset can configured to receive an IP address automatically from a
•If no DHCP server is used, a unique IP address must be entered manually for
6.2.1 Automatic IP Address Settings
1. Select Network > Network A (or B, C, D).
WL3_CM_Ch6.fm
Handset Configuration
IP Address Settings
DHCP server, see Chapter 6.2.1: Automatic IP Address Settings on page 61.
each handset, see Chapter 6.2.2: Static IP Address (Manual) Settings on
page 61.
2. In the DHCP mode drop-down list, select “Enable”.
The Phone IP address, Subnet mask, and Default gateway are automatically
set up.
6.2.2 Static IP Address (Manual) Settings
1. Select Network > Network A (or B, C, D).
2. In the DHCP mode drop-down list, select “Disable (static mode)”. Additional
parameters will be displayed.
3. In the Phone IP address field, enter the unique IP address for the handset.
4. In the Subnet mask field, enter the subnet mask.
5. In the Default gateway field, enter the IP address for the default gateway.
DNS Server Settings
It is possible to configure the DNS server that the handset uses. If the primary
DNS server is available, it is always used. Otherwise, the secondary DNS server
is used.
NOTE: The DNS parameters are only visible if the DHCP mode is set to “Disable
(static mode)”, see Chapter 6.2.2: Static IP Address (Manual) Settings on page
2. In the Primary DNS field, enter the IP address for the primary DNS server.
Secondary DNS Server
1. Select Network > Network A (B, C, or D).
2. In the Secondary DNS field, enter the IP address for the secondary DNS
server.
A31003-M2000-S100-2-7620, 10/2018
62WLAN Handset, Configuration Manual
6.3 Network Settings
WL3_CM_Ch6.fm
Handset Configuration
Network Settings
6.3.1 SSID
The SSID is the name of the network that the handset associates with.
1. Select Network > Network A (B, C, or D).
2. In the SSID field, enter system SSID.
Note that the SSID is case-sensitive.
6.3.2 Voice Power Save Mode
The voice power save mode is used during calls. NONE is recommended to
obtain optimal voice quality. U-APSD uses less power but is more sensitive to
network disturbances.
If supported by the infrastructure, U-APSD is the preferred choice and multiples
the talk time by more than 4 times compared to the NONE mode.
1. Select Network > Network A (B, C, or D).
2. In the Voice power save mode drop-down list, select one of following:
•NONE
•U-APSD
6.3.3 World Mode Regulatory Domain
There is a set of regional rules for the world mode settings and the a-band that
the handset complies with. The preferred and the default setting is “World mode
(802.11d)”. The handset gets its regulatory settings from the AP. If this is not
supported by the AP, then this has to be set in the handset as follows:
1. Select Network > Network A (B, C, or D).
2. In the World mode regulatory domain drop-down list, select one of the
following:
The handset supports the 802.11a/n radio and 802.11b/g/n radio, but it cannot
use the 802.11a/n radio and the 802.11b/g/n radio simultaneously. The radio
defines the channels that can be used.
802.11 a/n Channels
Defines which 802.11a/n channels to use. It is recommended to use the value
“UNII-1“.
Select “Advanced“ only if the channels are to be set in the Advanced: 802.11
channels parameter, see Appendix : Advanced: 802.11 Channels on page 65.
1. Select Network > Network A (B, C, or D).
2. In the 802.11 protocol drop-down list, select “802.11a/n“.
3. In the 802.11a/n channels drop-down list, select one of the following:
NOTE: The selected World Mode Regulatory Domain defines which channels to
be used. SeeChapter 6.3.4: Bands and Channels used by WiFi a-radio on page
Defines the 802.11b/g/n channels to use. It is recommended to use the default
value “1,6,11“. If set to “All”, all channels are scanned for APs, which decreases
the WLAN performance. Select “Advanced“ only if the channels are to be set in
the parameter Advanced: 802.11 channels.
1. Select Network > Network A (B, C, or D).
2. In the 802.11 protocol drop-down list, select “802.11b/g/n“.
3. In the 802.11b/g/n channels drop-down list, select one of the following:
•All
•1,6,11
•Advanced
Advanced: 802.11 Channels
Defines which 802.11 channels to use. Only used if the parameter in the 802.11b/
g/n channels, or 802.11a/n channels is set to “Advanced“.
NOTE: It is not possible to scan channels in 802.11b/g/n and 802.11a/n simultaneously.
NOTE: If “Advanced” is selected in the WinPDM or Device Manager, it is
indicated in the handset display by having all options unchecked in the “Settings”
>“Admin menu” > “Network setup” > “b/g/n channels”, or “a/n channels” menu. If
any of these unchecked channels are selected using the handset Admin menu,
the only way to reselect “Advanced”, is to reconfigure it in the WinPDM or Device
Manager.
1. Select Network > Network A (B, C, or D).
2. Enter channels to scan in a comma-separated list, for example 1,6,11 (the
order has no impact; 11,6,1 will give the same result).
6.3.5 Transmission Power
This is the transmission power the handset uses when transmitting data to the
WLAN system. If “Automatic” (default) is used, the transmission power is adapted
according to 802.11h, CCX or maximum possible.
1. Select Network > Network A (B, C, or D).
2. In the Transmission power drop-down list, select one of the following:
Differentiated Services Code Point (DSCP) defines the value to use for outgoing
voice and signaling traffic. The DSCP value is used for QoS on the LAN. The
settings in the handset must agree with the settings in the system, otherwise it
results in bad voice quality.
1. Select Network > Network A (B, C, or D).
2. In the IP DSCP for voice and/or IP DSCP for signaling drop-down list, select
one of the following:
•0x38 (56) - Class selector 7
•0x30 (48) - Class selector 6
•0x2E (46) - Expedited Forwarding (default for voice)
•0x28 (40) - Class selector 5
•0x20 (32) - Class selector 4
•0x1A (26) - Assured forwarding 31 (default for signaling)
•0x18 (24) - Class selector 3
•0x10 (16) - Class selector 2
•0x08 (8) - Class selector 1
•0x00 (0) - Default
A31003-M2000-S100-2-7620, 10/2018
66WLAN Handset, Configuration Manual
6.4 Security Settings
WL3_CM_Ch6.fm
Handset Configuration
Security Settings
The WLAN system can be configured to use various encryption and/or
authentication schemes. The use of extensive encryption/authentication
schemes can cause incidents of dropped speech during handover due to the time
to process the authentication.
The most used encryption and authentication modes are directly available from
the Security mode drop-down menu. The most required parameters per mode are
shown.
TIP: To view all available security parameters, use the “Advanced” menu.
6.4.1 Open
Select Open if no encryption/authentication is required. To select Open as the
security mode, do the following:
1. Select Network > Network A (B, C, or D).
2. In the Security mode drop-down list, select “Open”.
6.4.2 WEP 64/128-bit Key
To use WEP64/128-bit Key as the security mode. Do the following:
1. Select Network > Network A (B, C, or D).
2. In the Security mode drop-down list, select “WEP64/128-bit Key”. Additional
parameters can now be set. See below.
3. In the WEP key 1 field, enter the WEP key to be used.
4. In the WEP transmit key drop-down list, select “WEP key 1“.
6.4.3 WPA-PSK & WPA2-PSK
To select WPA-PSK & WPA2-PSK as the security mode. Do the following:
1. Select Network > Network A (B, C, or D).
2. In the Security mode drop-down list, select “WPA-PSK & WPA2-PSK”.
3. In the WPA-PSK passphrase field, enter the passphrase for WPA-PSK/&
WPA2-PSK.
To select EAP-FAST as the authentication method. Do the following:
1. Select Network > Network A (B, C, or D).
2. In the Security mode drop-down list., select “EAP-FAST”.
3. In the EAP authentication identity field, enter the user name for EAP
authentication.
4. In the EAP authentication password field, enter the password for EAP
authentication.
6.4.5 802.1X with PEAP-MSCHAPv2
PEAP-MSCHAPv2 requires the use of trusted certificates for authentication of the
WLAN. To select PEAP-MSCHAPv2 as the authentication method, do the
following:
1. Ensure that the handset is online in WinPDM.
2. For server validation, import the trusted certificate by performing the following
steps:
•In the Numbers tab, right-click the handset’s number and select “Manage
certificates“. A manage certificate window opens.
•In the Trust list tab, click “Browse“ and select the trusted certificates to
import. Click “Close“.
3. Select Network > Network A (B, C, or D)
4. In the Security mode drop-down list, select “PEAP-MSCHAPv2”.
5. In the EAP authentication identity field, enter the user name for EAP
authentication.
6. In the EAP authentication password field, enter the password for EAP
authentication.
In the Validate server certificate field, select if validation of server certificate
during authentication is to be disabled.
WARNING: By disabling the validation, the server is not authenticated and
may be a rouge one.
Needed condition: The server must send its complete certificate chain.
A31003-M2000-S100-2-7620, 10/2018
68WLAN Handset, Configuration Manual
WL3_CM_Ch6.fm
7
CAUTION
Handset Configuration
Security Settings
6.4.6 EAP-TLS
EAP-TLS requires the use of trusted certificates to authenticate the WLAN, and
application certificates to present to the WLAN for client authentication. To select
EAP-TLS as the authentication method, do the following:
1. Ensure that the handset is online in WinPDM.
2. Import the application certificate, and for server validation import the trusted
certificate, by performing the following steps:
•In the Numbers tab, right-click the handset’s number and select “Manage
certificates“. A manage certificate window opens.
•In the Trusted tab and Application tab, click “Browse“ and select the
certificates to import. Click “Close“.
3. Select Network > Network A (B, C, or D).
4. In the Security mode drop-down list, select “EAP-TLS”.
5. In the EAP application certificate drop-down list, select the application
certificate (in PKCS#12 format).
6. In the Validate server certificate field, select if validation of server certificate
during authentication is to be disabled.
By disabling the validation, the server is not authenticated and may be a
rouge one.
Needed condition: The server must send its complete certificate chain.
This section describes specific settings for the handset that can be changed using
the keypad on the handset, and/or can be set in the WinPDM/WSG to assist the
user, or to set the initial value when the handset is commissioned.
NOTE: Some parameter settings for audio adjustments, messaging settings,
and actions when the handset is placed in the charger, cannot be changed when
using the keypad.
General SettingsKeypad
Appendix : Automatic key lock on page 71xx
Appendix : Phone lock on page 71xx
Appendix : Headset type on page 73xx
Appendix : Audio adjustment on page 72xx
Appendix : Shortcuts on page 81xx
Appendix : Profiles on page 86xx
Appendix : Battery Warning on page 77xx
Appendix : No network and No access Warning on page 77x
Appendix : Actions when the Handset is Placed in the Charger
on page 74
Appendix : Shared Phone on page 79x
Telephony
Appendix : Message Centre Number on page 119x
Appendix : Max number of Call Completions on page 119x
Appendix : Dial Pause Time on page 120x
Appendix : Direct off Hook from Charger on page 120xx
Appendix : Replace Call Rejected with User Busy on page 120x
Appendix : Emergency Call Numbers on page 118x
Appendix : Import Contacts on page 83x
Appendix : Company Phonebook on page 84x
Appendix : Central Phonebook on page 85x
Appendix : Voice Mail Number on page 119x
Regional Settings
Appendix : Set Time & Date on page 122xx
Appendix : Select Default Language on page 80xx
Appendix : Dialing Tone Pattern on page 124x
Customize Menu
Appendix : Uploadable Language on page 79x
Appendix : Hide Menu Items on page 127x
Appendix : Services on page 127xx
Display
Appendix : User Display Text on page 125xx
Appendix : Font style on page 125xx
xx
*
WinPDM
A31003-M2000-S100-2-7620, 10/2018
70WLAN Handset, Configuration Manual
Handset Configuration
Appendix : Backlight Timeout on page 126x
Appendix : Brightness on page 126xx
Appendix : Screen Saver on page 126xx
Messaging
Appendix : Messaging Settings on page 97xx
Alarm
Appendix : Alarm Settings on page 109x
*Refer to the User Manual for more information on how the user can change the settings using the
handset´s keypad.
6.5.1 Automatic key lock
Turn on the automatic key lock to avoid unintentional key presses.
WL3_CM_Ch6.fm
Handset Settings
NOTE: If configured, it is possible to dial any of up to five predefined emergency
numbers when the keypad is locked, see Appendix : Emergency Call Numbers
on page 118.
1. Select Device > Settings.
2. In the Automatic key lock drop-down list, select one of the following:
•On - activates the automatic key lock, also during an ongoing call.
•Off - deactivates automatic key lock
6.5.2 Phone lock
Activate the phone lock to prevent unauthorized usage of the handset. A
password is required to unlock the handset in order to access its functions.
NOTE: If configured, it is possible to dial any of up to five predefined emergency
numbers when the handset is locked, see Appendix : Emergency Call Numbers
on page 118. It is not recommended to use Phone Lock when using the Shared
Phone feature, see Appendix : Shared Phone on page 79
1. Select Device > Settings.
2. In the Phone lock drop-down list, select one of the following:
•On - the handset will be locked after a few seconds when it is not used
•On in charger - the handset is be locked when placed in charger.
•Off - the phone lock is not activated.
6.5.3 Automatic lock time
When either the key lock or the phone lock is set to On, the lock is activated after
the specified time. It is possible to change the default time of 20 seconds.
1. Select Device > Settings.
2. In the Automatic lock time drop-down list, select desired time:
•5, 10, 20, 30 seconds, 1, or 3 minutes.
6.5.4 Automatic key unlock
1. Select Device > Settings.
2. In the Automatic key unlock drop-down list, select one of the following:
•On - the handset keypad is locked up automatically at incoming calls and
messages.
•Off - the handset is not locked up automatically to avoid unintentional key
press
6.5.5 Audio adjustment
Select the volumes for the different audio signals in the handset.
1. Select Audio > Volume.
2. Select the appropriate volume type from the drop-down lists:
•Handsfree volume
•Headset volume
•Speaker volume
3. In the Persistent volume drop-down list, select “Enable” to automatically store
volume changes in the handset for future calls.
A31003-M2000-S100-2-7620, 10/2018
72WLAN Handset, Configuration Manual
WL3_CM_Ch6.fm
7
CAUTION
Handset Configuration
Handset Settings
The parameter affects the “Normal”, “Headset“, “Loudspeaking“ mode.
For selection of headset, see Appendix : Headset type on page 73.
NOTE: Changing this parameter can result in lower sound quality and high
sound level. Evaluate carefully before applying.
6.5.6 Headset Configuration
Headset type
Select the headset model that is used.
1. Select Headset > General.
2. Select the applicable item from the drop-down list:
Do not select “Hearing protection” unless a Peltor headset is used.
•Hearing protection
•Mic on boom
•Mic on cable
•User model (If none of the headsets above are selected, this option can
be used to configure an own headset profile. If selected, additional
configuration is required, seeChapter 6.5.6: Headset user model on page
73)
Headset user model
These settings are required if User model is selected under Headset > General.
1. Select Headset > User model.
2. In the Name of headset field, enter a descriptive name. For example the
headset model to be used.
3. In the following drop-down lists, select the applicable values for the headset:
NOTE: Changing the parameters can result in lower sound quality and high
sound level. Evaluate carefully before applying.
Corded headset button
1. Select Headset > General.
2. In the Call with headset button list, select one of the following:
•Not activated – it is only possible to answer/end a call.
•Last called number – the last called number is dialled.
•Predefined number – a predefined number is called (if selected, continue
with step 3)
3. If needed, in the Predefined number field, enter the number to be dialled
when the headset button is pressed.
6.5.7 Actions when the Handset is Placed in the
Charger
The behavior of the handset when it is placed in a charger can be configured.
In-charger action when not in call
1. Select Device > Settings.
2. In the In charger action drop-down list, select one of the following:
•No action - no action is performed when handset is placed in charger
•Switch off - the handset is switched off when placed in charger
•Sound off - the handset is silenced when placed in charger (except for
messages with set “Break through” parameter, for example, “Prio 1”
messages.)
NOTE: Messages with breakthrough (for example with high/alarm
priority) are not muted. If you want to mute all messages (regardless of
priority) also set the Device > Messaging > Show and indicate messages
in charger > Off.
A31003-M2000-S100-2-7620, 10/2018
74WLAN Handset, Configuration Manual
WL3_CM_Ch6.fm
Handset Configuration
Handset Settings
•Change profile (WL3 Plus only) - the handset changes profile when
placed in charger.
- In the Change profile in charger drop-down list, select the profile to be
used.
- If needed, configure the selected profile, see Chapter 6.6: Profiles on
page 86.
3. In the In charger Message absent drop-down list, select one of the following:
NOTE: This function is applicable for WL3 Messenger UpgradeWL3 Plus
versions only.
•No - messages are saved in the handset’s messaging inbox while the
handset is placed in a charger (default).
•Yes - if a message is sent from a system it is notified that the handset is
absent. Messages are not sent to the handset.
Clear lists in charger
1. Select Device > General.
2. In the Clear lists in charger drop-down list, select one of the following:
•Yes - message lists and call lists are deleted when the handset is placed
in the charger.
•No - no action is performed when the handset is placed in the charger.
Show and indicate messages in charger
Defines how incoming messages are displayed/indicated when the handset is
placed in the charger.
NOTE: All incoming messages are affected by this setting: that is PTT invitation
received as a message, and all other messages regardless of priority (even
messages with breakthrough such as high/alarm priority). If you only want to
silence messages without breakthrough (low/normal priority), set the Sound off
parameter instead (in Device Settings > In charger action > Sound off).
1. Select Device > Messaging.
2. In the Show and indicate messages in charger drop-down list, select one of
the following:
•On - Messages are shown and indicated (by beep) when the handset is
placed in the charger (default)
•Off - The message alert (if any) is muted and only the New message icon
is displayed. The messages are stored as unread messages in the
Message inbox.
6.5.8 Hide Missed Call Window
By default, a Missed call window indicates a missed call. It is possible to hide this
window, for example, if both a handset and a mobile is used. If the user answers
the call using the mobile, the Missed call window is not displayed in the handset.
1. Select Device > Call.
2. In the Show missed calls popup drop-down list, select “No” to hide the Missed
call window.
6.5.9 Prevent Mute function
It is possible to prevent that the handset is muted/set to silent by a user.
1. Select Audio > General.
2. In the Prevent silent drop-down list, select one of the following:
•On - The user cannot set the handset to silent by using mute or
decreasing the volume.
•Off - The user can mute/reduce the volume to silent in the handset
(default).
6.5.10 Prevent Calls from being saved in the Call list
It is possible to prevent that the handset stores outgoing and incoming calls in the
Call list. This can be useful to prevent that an unauthorized person views the call
list.
1. Select Device > Call.
2. In the Enable call list drop-down list, select “Off” to prevent all calls being
saved.
A31003-M2000-S100-2-7620, 10/2018
76WLAN Handset, Configuration Manual
WL3_CM_Ch6.fm
Handset Configuration
Handset Settings
6.5.11 Battery Warning
1. Select Device > Settings
2. In the Battery warning drop-down list, select one of the following:
•Sound repeatedly
•Sound once
•Sound off
6.5.12 No network and No access Warning
No network warning
The handset’s indication of out of coverage, is to show the text “No network” in
the handset display in idle mode. It also indicates with a simultaneous (red) LED,
vibrator (if enabled), beep signal (if enabled) and a dialog window (if enabled by
the system administrator), as follows:
1. Select Device > General.
2. In the No network warning drop-down list, select one of the following:
•Indicate repeatedly - The beep is on, “No network” in the display in idle
mode is on, the (red) LED is on, the vibrator is on (if enabled), the dialog
window (popup) is on (if enabled). This simultaneous indication is
repeated every minute for 30 minutes.
•Indicate once - The beep is on, “No network” in the display in idle mode
is on, the (red) LED is on, the vibrator is on (if enabled), the dialog window
(popup) is on (if enabled). This simultaneous indication is made only
once.
•Indication off - The beep is off, “No network” in the display in idle mode is
on, the (red) LED is on, the vibrator is off (if enabled), the dialog window
(popup) is either on or off, dependent on the parameter settings in the
below note.
NOTE: Even if “Indication off” is set, the dialog window (popup) still appears
when “Dialog window for no network and no access warnings” (in Device >
General) is set to “Yes”.
The handset’s indication of “No access”, at the loss of messaging connection and/
or voice connection, is to show the text “No access” in the handset display in idle
mode. By default, the “No access” warning is set to off. It also can be set to
indicate repeatedly, or only once as follows:
1. Select Device > General.
2. In the No access warning drop-down list, select one of the following:
•Indicate repeatedly - The beep is on, “No access” in the display in idle
mode is on, the (red) LED is on, the vibrator is on (if enabled), the dialog
window (popup) is on (if enabled). This simultaneous indication is
repeated every minute for 30 minutes.
•Indicate once - The beep is on, “No access” in the display in idle mode is
on, the (red) LED is on, the vibrator is on (if enabled), the dialog window
(popup) is on (if enabled). This simultaneous indication is made only
once.
•Indication off - The beep is off, “No access” in the display in idle mode is
on, the (red) LED is on, the vibrator is off (if enabled), the dialog window
(popup) is either on or off, dependent on the parameter settings in the
below note.
NOTE: Even if “Indication off” is set, the dialog window (popup) still appears
when “Dialog window for no network and no access warnings” (in Device >
General) is set to “Yes”.
Dialog window for no network/no access warnings
This parameter defines if the dialog window (popup) for the warning states “No
network”, “Voice only”, “Messaging only” and “No access” is visible or not, in the
handset display.
NOTE: “No access” means that there’s neither voice nor messaging connection.
1. Select Device > General.
2. In the Dialog window for no network/no access warnings drop-down list,
select one of the following:
•Yes - The dialog window for “No network” or “No access” appears in the
handset display.
NOTE: When set to “Yes” (default), it overrides the “Indication off” setting
(in Device > General > No network warning, and/or No access warning),
that is, the dialog window (popup) is still shown.
A31003-M2000-S100-2-7620, 10/2018
78WLAN Handset, Configuration Manual
WL3_CM_Ch6.fm
Handset Configuration
Handset Settings
•No - The dialog window “No network” or “No access” doesn’t appear in
the handset display.
6.5.13 Shared Phone
This setting defines if the handset is personal or shared. The default setting is
“No” but if “Yes” is selected, the handset can be used by several users. Each user
can still have their individual settings and access them using personal login and
a password (the password can be a common password for all users or the call
number). To use the Shared phone functionality, the following is required:
•The handset does not use certificate.
•WSG
A handset that is personal can also use a shared password (empty or specific)
from the WSG.
NOTE: If you accidentally enter a personal phone number in the shared handset,
the handset becomes personal and cannot be used as a shared phone any
longer. The handset must be configured to act as a shared phone again.
1. Select Device > General.
2. In the Phone mode drop-down list, select one of the following:
•Personal
•Shared
NOTE: When the setting is changed, the handset is automatically restarted.
6.5.14 Uploadable Language
It is possible to upload one additional language to the handset. The language file
is generated through an Excel file. The Excel file used to generate language files
is delivered from your supplier.
TIP: It is also possible to upload a language on several handsets of the same
device type simultaneously using the Baseline function in the Installation and
Operation Manual, OpenStage Wireless Service Gateway (WSG), TD 92442EN.
If another language file is uploaded, the first additional language is overwritten.
Certain special characters are allowed when generating the language file, see
information in the Excel file.
To upload an additional language, do as follows:
1. In the Devices tab, select the device(s) to be uploaded with additional
language.
2. In the Device menu, select “Upload language...“.
3. If the uploaded language is to be used in the handset, see Chapter 6.5.15:
Select Default Language on page 80 for more information.
6.5.15 Select Default Language
Defines the default operating language for the handset. This setting can later be
changed by the user.
1. Select Device > Settings.
2. In the Language drop-down list, select the language to be used.
3. If the downloaded language is selected, it might be needed to select matching
characters as text input language, and the sort order in the phonebook
In the Input Language drop-down list, select the text input language to be
used.
NOTE: This parameter is only applicable for the downloaded language and
cannot be changed by the user.
A31003-M2000-S100-2-7620, 10/2018
80WLAN Handset, Configuration Manual
WL3_CM_Ch6.fm
Handset Configuration
Handset Settings
6.5.16 Shortcuts
One click access to predefined functions can be configured for the Soft keys, Hot
keys, Navigation keys, and the Multifunction button. For example a Soft key can
be configured to make a call.
Shortcuts are configured using parameters in the “Shortcuts” folder, except Soft
keys, which are configured in the “User Profiles” folder.
NOTE: The Multifunction button is only applicable for WL3, and WL3 Messenger
Upgrade.
NOTE: A hot key configured to Services with the function “Data send” is also
available during a call.
TIP: It is also possible to configure shortcuts using the handset menu. See the
User Manual of the handset.
Configure a Hot Key
A hot key is activated by pressing a preprogrammed button “0”, “2“ - “9” for more
than 1 second in idle mode. For example, the hot key function is used, to change
the profile, send a message, or make a phone call to a specific number.
1. Select Shortcuts > Hot keys X (where X is 0, 2 - 9).
2. Continue withAppendix : Additional Shortcut Settings on page 82.
Configure a Soft Key
NOTE: When programming Soft keys, both name and function must be set.
1. Select User Profiles > Normal/Profile X > Soft keys > Soft key X (where X is
Left, Middle, or Right)
2. In the Soft key name field, enter the name of the soft key shortcut to be
displayed in the handset.
3. Continue withAppendix : Additional Shortcut Settings on page 82.
Configure a Navigation Key
1. Select Shortcuts > Navigation Key X (where X is Up, Down, Left, or Right)
2. Continue withAppendix : Additional Shortcut Settings on page 82.
NOTE: The Multifunction button is only applicable for WL3, and WL3 Messenger
Upgrade.
1. Select Shortcuts > Multifunction Button X (where X is Longpress or
Multipress)
2. Continue withAppendix : Additional Shortcut Settings on page 82.
Additional Shortcut Settings
1. In the Function drop-down list, select the function to be used:
•Phone call
•Phone call “Loudspeaker mode”
•Call List
•Contact list
•Central phonebook (system dependent feature)
•Message inbox
•Send Message
•Change Profile Normal
•Change Profile X (1- 4). (If selecting profile 1-4, the profile must first be
configured, see Appendix : Profiles on page 86.)
•Open Menu (Main menu, Calls, Call Services, Connections, Contacts,
Messaging, Services, Profiles, Settings.)
•Executive Service X (1- 10) Services (Not applicable for WL3 Messaging)
•Logout (applicable for the Shared Phone feature)Call Diversions
•RSSI Measure
2. In the Value field, enter the applicable value. This is mandatory when using
Phone call function.
3. In the Control Question drop-down list, select “Yes“ if the Proceed? window is
displayed after the key is pressed. This is used to prevent a function being
accessed by mistake.
4. In the Read Only drop-down list, select “True“ if the user is not able to change
the shortcut.
A31003-M2000-S100-2-7620, 10/2018
82WLAN Handset, Configuration Manual
WL3_CM_Ch6.fm
Handset Configuration
Handset Settings
6.5.17 Soft Key Functions During Call
It is possible to configure the In Call functions for the left and right soft keys. The
In Call functions are accessed by pressing the left or right soft key during a call.
1. Select Device > Call.
2. In the Left in call soft key name or Right in call soft key name field, enter the
name of the soft key to be displayed during a call.
3. In the Left in call soft key action or Right in call soft key action drop-down list,
select one of the following functions:
•Conference
•Contacts
•Messaging (if applicable)
•Disabled
•End Call
•Hold
•Loudspeaker
•New call (put active on hold)
•Retrieve
•Switch
•Transfer (to held call)
•Transfer to new call (blind transfer)
4. Select OK
6.5.18 Import Contacts
It is possible to import a phonebook file (that is, local phonebook) to a handset.
The phonebook file is a tab-separated .txt file, and contains two items per row;
number and name. The WinPDM/WSG is used to import the phonebook file to the
handset. See Import Contacts in Installation and Operation Manual, Portable
Device Manager, Windows version, TD 92712EN,Installation and Operation
Manual, OpenStage Wireless Service Gateway (WSG), TD 92442EN.
It is possible to create a phonebook that is administered centrally and uploaded
to the handset from WinPDM/WSG. If this feature is used, entries from Contacts
and Company Phonebook are merged. The Company Phonebook entries are
locked and cannot be edited in the handset.
Perform the following steps:
1. Create a Company phonebook file, see Chapter 6.5.19: Create a Company
Phonebook File on page 84.
Import the Company phonebook file to WinPDM/WSG, see Installation and
Operation Manual, Portable Device Manager, Windows version, TD 92712EN, or
Installation and Operation Manual, OpenStage Wireless Service Gateway
(WSG), TD 92442EN.
Upload the company phonebook file to the handset(s), see Installation and
Operation Manual, Portable Device Manager, Windows version, TD 92712EN, or
Installation and Operation Manual, OpenStage Wireless Service Gateway
(WSG), TD 92442EN.
Create a Company Phonebook File
The company phonebook file (.cpb) is normally created from an Excel file using a
script to extract the information and create the phonebook file (.cpb). The Excel
file, “Company Phonebook.xls“ is delivered from your supplier.
The format of the rows in the phonebook file is:
<Name><tab><phone number><carriage return>
followed by additional rows for each entry.
The handset supports a maximum length of 24 characters in each field, additional
characters are truncated when the phonebook file is created. The following
characters are accepted in the handset number field in the phonebook file, but are
ignored when the phonebook file is created: “(“, “)“, “-“ and “ “(space).
A31003-M2000-S100-2-7620, 10/2018
84WLAN Handset, Configuration Manual
WL3_CM_Ch6.fm
Handset Configuration
Handset Settings
6.5.20 Central Phonebook
NOTE: This is a system dependent feature.
If the network is equipped with a messaging server with a phonebook service, the
Central Phonebook on that server can be accessed from the handset.
1. Select Device > Message centre.
2. In the Central phonebook field, enter the number to the Central phonebook
The number to be used is set to default 999999. If the system is not equipped with
a Central Phonebook, this menu option can be removed from the handset by
entering an empty value.
It is possible to set up an own profile for incoming calls, message alerts, vibrating
alerts, key sound etc. This can be useful when there are many users on the same
handset, and they want different sound profiles. It can also be used for temporary
settings, for example while in a meeting, incoming calls should be silent.
Profiles are configured through parameters in the “User Profiles“ folder.
1. Select User Profiles > User Profiles X (where X represents the Norma profile
(default) or Profile 1- 4).
2. The following settings for the profile can configured:
•Profile name
•Internal/External/Callback ring signal
•Ring volume
•Vibrator
•Key sound
•Message alert signal
•Diversion settings
•Answering settings
•Alarm settings
6.6.1 User Profiles
It is possible to set up an own profile for incoming calls, message alerts, message
volume, vibrating alerts, key sound etc. This can be useful when there are many
users on the same handset, who want different sound profiles. It can also be used
for temporary settings. For example while in a meeting, incoming calls are set to
silent.
1. Select User Profiles > User Profile X (where X represents the Normal profile
(default) or Profile 1 - 4).
2. In the Name text field, enter the name of the profile.
The name is visible in the handset and is also a selectable option in Profiles.
3. Select desired settings to edit:
•Sound and Alerts
•Presence and diversion
A31003-M2000-S100-2-7620, 10/2018
86WLAN Handset, Configuration Manual
WL3_CM_Ch6.fm
Handset Configuration
Profiles
•Answering
•Alarm settings
•Soft keys
•Call service
NOTE: The Call service is applicable to Profile X only (not profile “Normal”)
4. If desired, select the profile to be active, by selecting User Profiles and
change the default Active Profile “Normal” to desired profile.
TIP: It is also possible to configure profiles through the handset menu. See the
User Manual of the handset.
6.6.2 System Profiles
NOTE: This feature is applicable to WL3 Plus only.
NOTE: A system profile overrides all profile “Normal” or Profile X settings, on all
parameters in the group, for example, Soft Keys.
A system profile can be used when certain settings in a handset are required that
the user is not allowed to change. The system profile is created in two steps:
1. Create the System Profile sub-group(s).
The following sub-groups are available:
- Presence groups, containing presence settings, and message absent.
- Answering groups, containing settings for how incoming calls are answered.
- Sound and alerts groups, containing sound and alert settings for calls and
messages.
- Soft key groups, containing shortcut settings to predefined functions using
key press.
- Alarm settings groups, containing settings for which alarm type is used and
9. In the Message alert drop-down list, select one of the following:
The message sound for incoming messages can be either a melody or a
single beep.
TIP: Any of the default handset beeps (Beeps and Enhanced beeps) are
customizable, see Appendix B.1: Customize the default handset beeps on
page 160.
•Message X (1 - 7)- Defines the message sound for incoming messages
as a certain melody.
•Beeps according to beep code - Defines the message sound for incoming
messages according to the melody or beep coming from an application.
•High beeps according to beep code - The same type as “Beeps according
to beep code”, but with a higher pitch.
•Enhanced beeps according to beep code - The same type as “Beeps
according to beep code”, but in the form of a melody.
•Custom sounds according to beep code - Proprietary melody coming
from an application.
10. In the Message volume drop-down list, select one of the following:
•Silent - There is no message indication for incoming messages.
•Volume X (1 - 8) - Different message indication volumes, from lowest (1),
to highest (8) volume.
•Follow ring volume - The message indication volume follows the ring
volume.
Configure Soft key groups (sub-group)
1. Select System Profiles > System Profiles Sub Groups > Soft key groups >
Soft key group X.
2. In the Name of group field, enter a descriptive name.
3. Select Soft key group X > Soft key X (left/middle/right), (in System Profiles >
System Profiles Sub Groups > Soft key groups > Soft key group X) and edit
required settings.
•Soft key name - Defines the text that is shown in the handset display
above the soft key.
NOTE: A maximum number of 6 characters fits in the soft key name.
•Function - Defines the function to be connected to the soft key.
•Value - Defines a value (for example, a phone number) for a function.
NOTE: The value is only needed for some functions.
A31003-M2000-S100-2-7620, 10/2018
90WLAN Handset, Configuration Manual
WL3_CM_Ch6.fm
Handset Configuration
Profiles
•Control Question - Defines if a Proceed? dialog window appears when
pressing a soft key.
Configure Alarm settings group (sub-group)
1. Select System Profiles > System Profiles Sub Groups > Alarm settings
groups > Alarm settings group X.
2. In the Name of group field, enter a descriptive name.
3. Select Alarm settings group X > Common (in System Profiles > System
Profiles Sub Groups > Alarm settings groups) and edit required settings.
•Stored alarm data - Predefined information that is sent with the alarm (for
example a room number)
•Indicate triggered alarm with LED
•Indicate triggered alarm with vibrator
•Indicate triggered alarm with beep signal
NOTE: If the parameter "Silent alarm" is set, no indication will be shown that an
alarm has been sent or received, that is, there is no beep, vibrator, LED or dialog
window.
4. Select System Profiles > System Profiles Sub Groups > Alarm settings
groups > Alarm settings X > Alarm on long press
•Alarm type for long press - Defines the type of alarm that is sent by a long
press (press and hold) on the alarm button. If Not used is selected, a
predefined number can still be called automatically after an alarm (see
Chapter 6.10.3: Call Predefined Number without Sending Alarm on page
111), without sending an alarm.
•ALS - Defines if a ramped up Acoustic Location Signal (ALS) sounds,
after pressing the alarm button.
NOTE: The ALS is not triggered if automatic call after alarm is active (see
Chapter 6.10.3: Call Predefined Number without Sending Alarm on page
111) .
5. Select System Profiles > System Profiles Sub Groups > Alarm settings group
> Alarm settings X > Alarm on multiple press
•Alarm type for multiple press - Defines the type of alarm that is sent when
pressing the alarm button twice or more. If Not used is selected, a
predefined number can still be called automatically after an alarm (see
Chapter 6.10.3: Call Predefined Number without Sending Alarm on page
111) without sending an alarm.
•ALS - Defines if a ramped up Acoustic Location Signal (ALS) sounds after
pressing the alarm button.
NOTE: The ALS is not triggered if automatic call after alarm is active (see
Chapter 6.10.3: Call Predefined Number without Sending Alarm on page 111).
Configure Idle display groups (sub-group)
NOTE: By default, the name of a system profile is displayed in the handset. It is
only needed to configure an idle display group, if the system profile name not
shall be displayed in the handset.
1. Select System Profiles > System Profiles Sub Groups > Idle display groups >
Idle display group X.
2. In the Name of group field, enter a descriptive name.
3. In the Show name of system profile drop-down list, select one of the following:
•Yes - The system profile name is shown in the handset display in idle
mode.
•No - The system profile name is not shown in the handset display in idle
mode.
Create System Profile using Predefined Sub-groups
In order to create a system profile, it must be connected to the desired predefined
sub-groups.
NOTE: “Not Used” keeps “Normal” profile settings.
Select System Profiles > System Profile X.
•Profile name - Enter a descriptive name to identify this system profile.
•Presence groups - Defines which predefined presence group (sub-group)
is used in this system profile.
A31003-M2000-S100-2-7620, 10/2018
92WLAN Handset, Configuration Manual
WL3_CM_Ch6.fm
Handset Configuration
Profiles
•Sound and alerts groups - Defines which predefined sound and alerts
group (sub-group) is used in this system profile.
•Soft keys groups - Defines which predefined soft key group (sub-group)
is used in this system profile.
•Answering groups - Defines which predefined answering group (sub-
group) is used in this system profile.
•Alarm settings groups - Defines which predefined alarm settings group
(sub-group) is used in this system profile.
NOTE: “Not Used” keeps the normal alarm settings defined under “Alarm”.
•Idle display groups - Defines which predefined idle display group (sub-
group) is used in this system profile.
NOTE: “Not Used” is not used.
Activate/Deactivate System Profile
When a system profile is created, it can be activated on the handset using
WinPDM/Device Manager or using an Unite application. For example, the
application could be triggered by a positioning beacon. However, this section
describes how to activate the system profile using WinPDM.
By default, when the system profile is activated, its name is displayed in the
handset’s idle screen.
TIP: If a certain system profile always needs to be active on a handset, it is
recommended to hide the settings/menus the user cannot change.
A System profile overrides all “User Profile X” and “Normal” (profile) settings on
all parameters in the group, see the two examples below.
1. Select "System profiles".
2. In the Active system profile drop-down list, select one of the following:
Figure 4A System profile affects a complete group of parameters, like all Soft
keys.
On the left of the image above (1), the User Profile X (or the profile “Normal”) is
configured with a shortcut to open the menu on the left Soft key. Next, a System
Profile shortcut to make a call to the administrator Susan, is configured for the
free middle Soft key, see (2). When activating the System profile “Call to Susan”,
the left Soft key “Menu” disappears, because the System profile overrides the
complete group of the Soft key parameters.
TIP: How parameters groups are arranged is seen under System Profiles >
System Profiles Sub Groups.
94WLAN Handset, Configuration Manual
Example 2:
If the user changes any settings that are specified in the System profile, the
settings are not applied. In this case, the alarm settings have been configured in
the system profile Alarm. Then the user cannot change any alarm settings using
the handset, although the Alarm menu is visible. It is recommended to hide the
Alarm menu to avoid misunderstanding.
System Profile Activation and Deactivation Audible Alert
The administrator may configure the handset to play a sound if the system profile
is activated or deactivated. This provides the user with an audible alert when the
system profile changes from inactive to active or vice versa. The feature can be
triggered by several kinds of events, such as moving between different parts of a
building where a system profile might be appropriate in one location, but not
required in another.
To configure the handset to play a sound when a system profile is activated or
deactivated, perform the following steps:
A31003-M2000-S100-2-7620, 10/2018
WL3_CM_Ch6.fm
Handset Configuration
Profiles
1. Select "System profiles".
2. From the "System Profile X" list select the system profile where the audible
alert is to be applied.
Set the "Activation and deactivation sound" parameter to the required customized
sound.
The messaging and alarm functions are provided through the WSG and
described in the document Installation and Operation Manual, OpenStage
Wireless Service Gateway (WSG), TD 92442EN.
6.7.1 IP Address to the WSG
The WSG handles all communication between the WLAN and its built-in
Centralized Device Manager. It is possible to send messages from a web browser
to a handset, handle messages to groups, send simple messages from handset
to handset (and to groups), search for telephone numbers in a central database
(on PC), have a central telephone book on the WSG (not PC-based), and to
provide absence handling in the system.
1. Select Device > WSG.
2. In the IP address field, enter the IP address of the WSG. If empty, no
messaging or alarm function is available.
A31003-M2000-S100-2-7620, 10/2018
96WLAN Handset, Configuration Manual
6.8 Messaging Settings
NOTE: Applicable to WL3 MessagingWL3 Plus only.
It is possible to configure how incoming messages are indicated and displayed in
handset.
Profiles > Normal, Profile 1- 4
WL3_CM_Ch6.fm
Handset Configuration
Messaging Settings
•Vibrator
Defines if the handset vibrates when receiving incoming calls and messages.
•Message alert
Defines the message sound for incoming messages.
•Message volume
Defines the message volume for incoming messages. By default, the
message volume follows the ringer volume, but a different message volume
can be set with this parameter.
Device > Messaging
•Message list representation
•Can be set to text or number.
•Message text size
•Time to read (TTR)
Defines if the user needs to close a message manually, or if the message
automatically closes when the TTR expires. Regardless of how a message is
closed, it is removed from the message queue and stored in the Messaging
Inbox. TTR starts when a message is displayed and continues to run when
the message is placed in the messaging queue. If a user presses any key
when a message is displayed, the TTR is reset. See also Appendix :
Examples of TTR/TTP settings on page 102.
•Time to prioritize (TTP)
Defines how long time messages keep their priority status. The TTP starts
when a message is displayed. If a user presses any key when a message is
displayed, the TTP is reset. If receiving a message with higher priority than
the displayed message, the message with lower priority is placed in queue
and its TTP is paused. When the TTP elapses for a message, it is put last in
the queue. See also Appendix : Examples of TTR/TTP settings on page 102.
This parameter enables/disables message indications. It sets whether a
message indication is repeated until confirmed by the user or not. The current
repetition rate is 7 seconds. If the message itself contains a repetition, it
overrides this setting.
•Vibrator for message during call
Defines if the handset vibrates when receiving messages during an ongoing
call.
•Message alert during call
Defines if a message alert should be played when receiving a message
during a call.
•IM option mode
This parameter is used for older applications and sets that three soft keys are
placed automatically, i.e. on soft keys or in an option menu (list).
•Call priority
This parameter defines:
–whether call information presented on the display during an incoming,
ongoing, and outgoing call is suppressed when viewing a message
–whether an ongoing call is disconnected when receiving a PTT
invitation with Answer mode set to “Automatically”.
0 = Call indication overrides all messages and the ongoing call is never
disconnected (default).
1-9 = Comparison with message priority; highest priority is shown, and a PTT
invitation with higher priority causes disconnection of ongoing call.
10 = Call indication on the display is always suppressed and the ongoing call is
always disconnected by a PTT invitation.
The tables below show examples of priority settings and how they affect the
handset’s behavior.
Call prioPTT invitation (prio)
*
Disconnection of ongoing call?
01No, since this call priority setting overrides all
PTT invitations regardless of priority.
66No, an ongoing call is not disconnected when
the priority is equal.
21Yes, immediately since the PTT priority is set
to 1 and is also higher than Call priority.
A31003-M2000-S100-2-7620, 10/2018
98WLAN Handset, Configuration Manual
WL3_CM_Ch6.fm
Handset Configuration
Messaging Settings
32Yes, after 10 seconds since the PTT priority
is higher than Call priority.
101Yes, immediately since the PTT priority is set
to 1 and also is higher than Call priority.
102Yes, after 10 seconds since the PTT priority
is higher than Call priority.
*PTT invitation received as incoming call has always priority 6, while PTT invitation received as
message can have priority 1 - 9 depending on configuration.
Table 2Call prio vs PTT prio
Call prioDisplayed Message
Call information suppressed?
(prio)
01No, since this call priority setting overrides
all messages regardless of priority.
76Yes, since the priority of the displayed
message is higher than the incoming call.
66Yes, since the message is considered as
most important when the priority is equal.
13No, since the priority of the incoming call is
higher than the displayed message.
101Yes, the call information is always
suppressed regardless of the message
priority.
Table 3Call prio vs Message prio
•Show and indicate messages in charger
Defines if incoming messages are shown and indicated by a beep when the
handset is placed in the charger.
NOTE: This affects all messages and priority levels (PTT invitation received
as a message and messages with breakthrough such as high/alarm priority)
including remote call setup. Messages are stored in the Messaging inbox.
TIP: If you only want to silence messages without breakthrough (low/normal
priority), set the Sound off parameter instead (in Device > Settings > In
charger action > Sound off).
Defines if incoming messages are displayed upside down. This can be useful
if you wear the handset in a belt and want to read the message without
rotating the handset. When pressing any key, the messages are displayed in
the normal way.
NOTE:
NOTE: This setting also affects how incoming calls are displayed.
6.8.1 Configure Message Alerts with Beep Codes
The handset can map beep codes sent from a system/an application to different
message alerts. There are several ways to treat the beep codes:
TIP: To configure the same message alert for a group, make the settings in the
WinPDM in Profiles > Normal/Profile X > Message alert. Save the settings as a
template and add it to desired handsets.
TIP: Any of the default handset beeps (Beeps and Enhanced beeps) are
customizable, see Appendix B.1: Customize the default handset beeps on page
160.
Beeps according to beep code
Beep code sent from a system/applicationThe handset plays:
Beep code 0No message alert is played
Beep codes 1- 61 - 5, and 10 beeps
Beep code 7Siren
The handset plays the original message alerts that are mapped to the beep
codes.
1. Select Settings > Sound and Alert.
2. In the Message alert drop-down list, select "Beeps".
High beeps according to beep code
Beep code sent from a system/applicationThe handset plays:
Beep code 0No message alert is played
Beep codes 1- 61 - 5, and 10 beeps
Beep code 7Siren
The handset plays the message alerts that are mapped to beep codes, but with
a higher pitch.
A31003-M2000-S100-2-7620, 10/2018
100WLAN Handset, Configuration Manual
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.