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
Loading...
+ 158 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.