8168s WLAN Handset

8158s WLAN Handset

Configuration guide

8AL90392ENAAed02
11/2020
Configuration guide

Table of Contents

About this Document 6

Abbreviations and Glossary 6
1 Introduction 8
1.1 GDPR Considerations 8
2 Handset Deployment 9
2.1 Prerequisites 9
2.2 Handset Deployment into the VoWiFi System 9
2.2.1 Deploy the Handset Using the IMS3 DM 10
2.2.2 Deploy the Handset Using WinPDM 13
2.2.3 Deploy the Handset Using the Admin Menu 15
2.2.4 Set the Handset to SIP or NOE Mode 15
2.3 Handset Configuration 16
2.3.1 Configure Handsets Using WinPDM/IMS3 DM 16
2.3.2 Configure the Handset Using the Admin Menu 16
2.4 Handset Synchronization 17
3 Parameter Configuration 18
3.1 Networks 18
3.1.1 Change Active Network 18
3.1.2 Change Name of Network 18
3.1.3 Enable Switch Between Networks 18
3.2 Handset IP Address Settings 19
3.2.1 Automatic IP Address Settings 19
3.2.2 Static IP Address (Manual) Settings 19
3.3 Network Settings 20
3.3.1 Radio and Channel Selection 20
3.3.2 SSID 21
3.3.3 Security Settings 22
3.3.4 World Mode Regulatory Domain 23
3.3.5 IP DSCP for Voice/Signaling 24
3.3.6 TSPEC Call Admission Control 24
3.3.7 Roaming Method 24
3.3.8 IP Connectivity after Roaming 24
3.3.9 A-MPDU Packet Aggregation 25
3.3.10 Use DCHP User Class 25
3.3.11 Configure TFTP in NOE Mode 25
3.4 Handset Settings 25
3.4.1 Automatic Key Lock 25
3.4.2 Automatic Key Unlock 26
3.4.3 Phone Lock 26
3.4.4 Automatic Lock Time 26
3.4.5 Multifunction Button 27
3.4.6 Audio Settings 28
3.4.7 Headset Configuration 29
3.4.8 Actions when the Handset is Placed in the Charger 29
3.4.9 Transfer Unlock File 31
3.4.10 Hide Missed Call Window 31
3.4.11 Prevent the Handset to Switch off 31
3.4.12 Disable Mute Function 31
3.4.13 Prevent Calls from Being Saved in the Call List 32
3.4.14 Battery Warning 32
3.4.15 No Network and No Access Warning 32
3.4.16 Shared Phone 33
3.4.17 Shortcuts 34
3.4.18 Import Contacts 36
3.4.19 Company Phone Book 36
8AL90392ENAAed02 2 /113
Configuration guide

3.4.20 Central Phone Book 37

3.4.21 System Administration in the Handset 37
3.4.22 Change Admin Access Code 39
3.4.23 Block Access to the Admin Menu 39
3.5 Profiles 40
3.5.1 User Profiles 40
3.5.2 System Profiles 43
3.6 Telephony 48
3.6.1 Endpoint ID and Endpoint Number 48
3.6.2 Endpoint Number Display Length 48
3.6.3 VoIP Protocol 48
3.6.4 Codec 50
3.6.5 Offer Secure RTP 51
3.6.6 Internal Call Number Length 51
3.6.7 ICE Negotation 51
3.6.8 Emergency Call Numbers 52
3.6.9 Voice Mail Number 52
3.6.10 Message Center Number 52
3.6.11 Voice Mail Call Clears MWI 52
3.6.12 Dial Pause Time 52
3.6.13 Quick Answer 52
3.6.14 Replace Call Rejected with User Busy 53
3.6.15 Call Waiting Behavior 53
3.6.16 Call Waiting Sound 53
3.6.17 PTT Call Disconnect Warning 53
3.6.18 Configure In Call Functions 54
3.6.19 Hide In Call Function for PTT Calls 54
3.6.20 Calling Line Identification Restriction (CLIR) 54
3.6.21 Allow Blind Transfer 55
3.6.22 Call Services 55
3.6.23 Call Using a Bluetooth Headset 55
3.7 Messaging Settings 56
3.7.1 Configure Message Alerts with Beep Codes 59
3.7.2 Message Retransmit Limit 61
3.7.3 Examples of TTR and TTP Settings 61
3.8 Message Templates 65
3.8.1 Configure the Handset for Message Templates 65
3.8.2 Create Message Templates 65
3.9 Regional Settings 66
3.9.1 Set Time & Date 66
3.9.2 Select Default Language and Writing Language 67
3.9.3 Dialing Tone Pattern 67
3.10 Display 67
3.10.1 Hide Menu Items 67
3.10.2 User Display Text 67
3.10.3 User Display Number 68
3.10.4 Rotate Display Text 68
3.10.5 Font Style 68
3.10.6 Backlight Timeout 68
3.10.7 Brightness 68
3.10.8 Screen Saver 69
3.10.9 Screen Saver Icons 69
3.10.10 Idle Information Text 69
3.11 Services 70
3.12 Push-to-Talk Group Call 70
3.13 Location 71
3.13.1 Configure Handset for Cisco MSE or AiRISTA Flow RTLS Solution 72

8AL90392ENAAed02 3 /113
Configuration guide

4 System Deployment Planning 73

4.1 Site Survey Tool 73
4.2 Scan the Channels 73
4.2.1 Scan All Channels 73
4.2.2 Scan a Specific Channel 73
4.3 Range Beep 74
4.3.1 Configurable RSSI Threshold 74
4.3.2 Range Beep on a Configurable RSSI Threshold 74
4.4 Location Survey 74
5 Maintenance 75
5.1 Maintaining the Handset 75
5.1.1 Configure Spare Handsets without a Number in Large Systems 75
5.1.2 Handset Software Upgrade 75
5.1.3 Perform a Factory Reset 76
5.2 Handset Replacement 77
5.2.1 Parameter Migration 77
5.2.2 Replace the Handset using IMS3 DM 77
5.2.3 Replace the Handset using WinPDM and IMS3 DM 78
5.2.4 Replace the Handset using WinPDM 79
5.3 Change the Number of a Handset 79
5.4 Update Parameters Using WinPDM/IMS3 DM 79
5.5 Perform a Security Upgrade Using IMS3 DM 80
5.6 Upgrade the Template 80
5.7 Create a Configuration Backup 80
5.8 Logging 80
5.8.1 Syslog 80
5.8.2 PCAP Capturing 80
5.8.3 Save Logs 81
5.8.4 Enable Sending Logs over SFTP 82
5.8.5 SFTP Server Settings 82
5.8.6 Trace Configuration 82
5.8.7 Low Level WLAN debug 83
5.8.8 SNMP 83
6 Troubleshooting 84
6.1 Fault Symptoms 84
6.2 Display Information 86
7 Related Documents 90
Appendix A Templates 91
A.1 Save Handset Configuration as a Template 91
A.2 Manage Templates using WinPDM and IMS3 DM 91
A.2.1 Import a Parameter File 92
A.2.2 Import a Template 92
Appendix B Configure Custom Sounds 93
Appendix C Easy Deployment 97
C.1 Prerequisites 97
C.2 WLAN Discovery 98
C.3 IMS3 Discovery 99
C.3.1 Server Discovery Using the DHCP Option 43 99
C.3.2 Server Discovery Using the Ascom Service Discovery Protocol (ASDP) 100
C.4 Parameter Download 100
C.5 SCEP 101

8AL90392ENAAed02 4 /113
Configuration guide

Appendix D Complementary Information for Easy Deployment 103

D.1 DHCP Related 103
D.1.1 DHCP Vendor Options Explained 103
D.1.2 Configuration Example of a Linux Server Using DHCP Option 43 106
D.1.3 Configuration Example of an MS Windows 2003 Server 106
D.1.4 Configure DHCP Options in a Cisco Device Running the Cisco IOS DHCP Server 109
D.2 Easy Deployment and VLAN 110
D.3 Easy Deployment and Certificates 110
Appendix E Interactive Messaging in Handsets 112

www.al-enterprise.com The Alcatel-Lucent name and logo are trademarks of Nokia used under
license by ALE. To view other trademarks used by affiliated companies of ALE Holding, visit: www.al-
enterprise.com/en/legal/trademarks-copyright. All other trademarks are the property of their respective
owners. The information presented is subject to change without notice. Neither ALE Holding nor any
of its affiliates assumes any responsibility for inaccuracies contained herein.
© Copyright 2020 ALE International, ALE USA Inc.

8AL90392ENAAed02 5 /113
Configuration guide

About this Document

This document describes how to configure, maintain, and troubleshoot the Alcatel-Lucent Enterprise
(ALE) 8158s and 8168s WLAN Handsets.

Abbreviations and Glossary

ALE Alcatel-Lucent Enterprise

AP Access Point

DHCP Dynamic Host Configuration Protocol

A protocol for automating the configuration of computers and handsets that use
TCP/IP.

DNS Domain Name Server

DSCP Differentiated Services Code Point

QoS on the Internet Layer used both for WLANs and LANs.

DTIM Delivery Traffic Indication Message

EAP Extensible Authentication Protocol

EAP-TLS EAP-Transport Layer Security

GDPR General Data Protection Regulation

GUI Graphical User Interface

The interface between a user and a computer application.

ICE Interactive Connectivity Establishment

IM Interactive Messaging
Makes it possible to access information from an application and control the
information by selecting an option received in a message.

IMS3 Integrated Wireless Messaging and Services

A gateway that handles communication interfaces for DECT- and VoWiFi handsets
and other basic messaging services, such as, web messaging and messaging
handset to handset (SMS). It is installed on the Elise3 hardware.

IP Internet Protocol
Global standard that specifies the format of datagrams and the addressing
scheme. This is the principal communications protocol in the Internet Protocol
suite.

LAN Local Area Network

MAC Medium Access Control

In IEEE 802 LAN/MAN standards, the MAC sublayer is the layer that controls the
hardware responsible for interaction with the wired, optical, or wireless
transmission medium.

NAT Network Address Translator

NOE New Office Environment

An ALE stimuli protocol for telephony and other services.

NTP Network Time Protocol

OTA Over-the-Air

8AL90392ENAAed02 6 /113
Configuration guide

Parameter A handset setting that can be configured using WinPDM/IMS3 DM.

PBX Private Branch Exchange

A telephone system within an enterprise that switches calls between local lines,
and allows all users to share a certain number of external lines.
Also referred to as Call Manager.

PEAP Protected Extensible Authentication Protocol

A protocol that encapsulates the Extensible Authentication Protocol (EAP) within
an encrypted and authenticated Transport Layer Security (TLS) tunnel, correcting
deficiencies in EAP.

PEAP- PEAPv0/EAP-MSCHAPv2
MSCHAPv2 The most common form of PEAP in use, and often referred to as only “PEAP”. It
allows authentication to databases that support the MS-CHAPv2 format, including
Microsoft NT and Microsoft Active Directory.

Production It includes the applications, systems, and protocols the handset uses after
System deployment, for example, IMS3, PBX, and WiFi.

PTT Push-To-Talk

QoS Quality of Service

Defines to what extent transmission rates, error rates, and so on are guaranteed in
advance.

RSSI Received Signal Strength Indication

RTLS Real Time Locating System

Services Predefined functions such as Phone Call, Send Data, Send Message, and so on,
that are accessible from the Service menu.

SIP Session Initiation Protocol

SIP is a signaling protocol used for initiating, maintaining, and terminating real-time
sessions that include voice, video, and messaging applications. SIP is used for
applications of Internet telephony for voice and video calls, in private IP telephone
systems, in instant messaging over IP networks, and in mobile phones calling over
LTE, Voice over LTE (VoLTE).

SSID Service Set Identifier

STUN Session Traversal Utilities for NAT

TURN Traversal Using Relay NAT

Unite Name of Ascom IP-based protocol for handling events and messages.

Unite The IMS3 handles all communication between the WLAN and its built-in device
Module manager.

8AL90392ENAAed02 7 /113
Configuration guide

1 Introduction

This document provides guidelines for deploying, configuring, maintaining, and troubleshooting the
(ALE) 8158s and 8168s WLAN Handsets.

The VoWiFi system provides wireless IP telephony, and messaging functions. Using third-party
WLAN products, hardware, and software developed in-house, the system enables data and voice
transmission together with seamless roaming.

This document describes how to configure handsets in a VoWiFi system using Session
Initiation Protocol (SIP) towards the PBX/Call manager. For systems using the ALE
protocol New Office Environment (NOE), there could be some differences.

The document is targeted at the following personnel:

• System administrators
• Service technicians

It is recommended to have a basic knowledge of the ALE VoWiFi system and handset registration in
the PBX.

1.1 GDPR Considerations

The handset provides data protection. To comply with the GDPR by default, the Auto phone lock
and Clear lists in charger parameters must be enabled in the handset. For more information, see
User Manual, ALE 8158s and 8168s WLAN Handsets, 8AL90391ENAA.

These settings can also be configured by applying the provided GDPR template.

8AL90392ENAAed02 8 /113
Configuration guide

2 Handset Deployment

This section describes how to deploy handsets to a VoWiFi system.

2.1 Prerequisites

Deploying handsets to a VoWiFi system requires the following prerequisites:

• The handset batteries are charged.
• Chargers are set up in case WinPDM is used.
• A phone number plan is available for the handsets.
• The IP address plan is set up to support the number of handsets to be deployed.
• A VoWiFi system where some or all of the following components (depending on the system
configuration) are available:
• DHCP Server – It allows devices to request and obtain IP addresses from the server that has
a list of addresses available for assignment. If the WLAN does not have access to a DHCP
server, it is necessary to have a list of static IP addresses.
• WinPDM – It is a stand-alone device management system used for administering and
configuring handsets. All settings and updates are performed using the DP1 Desktop
Programmer cradle connected over USB.
• IMS3 – It handles all communication between the WLAN and its built-in IMS3 DM. Before
installing the handset, make sure the IMS3 DM address is available.
• NTP server – It ensures network time synchronization.

2.2 Handset Deployment into the VoWiFi System

The Alcatel-Lucent Enterprise (ALE) 8158s and 8168s WLAN Handsets can be deployed to a VoWiFi
system in the following ways:
• Over the Air (OTA) using the Integrated Message Server (IMS3) — This is the recommended
option to deploy handsets in a large VoWiFi system. The IMS3 DM can install, upgrade, and
configure a large amount of handsets simultaneously without collecting them from the users.
For more information, see 2.2.1 Deploy the Handset Using the IMS3 DM, page 10 and 2.2.1.1
Configure the Handset Using Easy Deployment, page 11 .
• Using Portable Device Manager (WinPDM) — WinPDM can configure only one handset at a
time, which is feasible in small VoWiFi systems. The handsets need to be collected from the
users.
For more information, see 2.2.2 Deploy the Handset Using WinPDM, page 13 .
• Using the Admin menu of the handset — This option can be used in case only a quick change
of a parameter value is needed, for example, in a lab environment or in a test installation.
For more information, see 2.2.3 Deploy the Handset Using the Admin Menu, page 15 .

When deploying handsets using WinPDM/IMS3 DM, it is recommended to create templates to be able
to apply the same configuration to several handsets simultaneously. For more information, see 2.2.1.2
Create a Template in WinPDM/IMS3 DM, page 12 , 2.2.1.4 Apply a Template to a Handset without a
Number, page 13 , and 2.2.1.5 Apply a Template to a Handset with a Number, page 13 .

8AL90392ENAAed02 9 /113
Configuration guide

2.2.1 Deploy the Handset Using the IMS3 DM

For OTA device management, the handset needs to have a WLAN association that can be IP routed
to IMS3 DM.

It is recommended to use Easy Deployment, where the handset first obtains the Unite IP address
using a DHCP server or the Ascom Service Discovery Protocol (ASDP), then the WLAN parameters
and the device manager information is distributed automatically to the handset from the IMS3.

If Easy Deployment is not used, the WLAN and IMS3 DM parameters can be set manually using the
Admin menu in the handset or WinPDM.

Then the handset logs into the IMS3 DM, and downloads the intended handset profile, which contains
all other needed parameters for a site.

For more information, see 2.3.2 Configure the Handset Using the Admin Menu, page 16 and
Appendix C Easy Deployment, page 97 .

If the WLAN system uses an 802.1X security protocol that requires certificates for
authentication/encryption to the WLAN, the certificates must be prepared and stored
individually in the IMS3 DM for each number before starting the Easy Deployment
process. Alternatively, if a SCEP server is available, this can be accomplished by
following the steps in C.5 SCEP, page 101 to have the necessary certificates
automatically generated and downloaded to the handset.

If the handset must use a certificate to access a WLAN, follow the instructions in 2.2.2
Deploy the Handset Using WinPDM, page 13 .

Figure 1. Configuration of Handsets Over-the-Air (OTA)

To deploy handsets to the VoWiFi system using the IMS3 DM, perform the following steps:

This section includes only the main steps of the deployment procedure. For details, see
the corresponding sections.

8AL90392ENAAed02 10 /113
Configuration guide

1. Open a web browser and enter the address of the IMS3.

2. Open the IMS3 DM and log in if necessary.
3. If User class needs to be used to identify the handset in a DHCP server, see 3.3.10 Use
DCHP User Class, page 25 .
4. Create a template with the following network parameters:
• Network settings in Network → General:

Under the respective network (Network A, Network B, Network C, or Network D), set the
required parameters, for example, system settings for WLAN, such as SSID, Security mode, and
any certificates for 802.1X. If using a security mode that requires certificates, also use an NTP
server to assure the correct time in the handset, as certificates are only valid within a certain time.
• VoIP settings in the VoIP menu:

Configure, for example, VoIP information, SIP proxy ID and address.

• Syslog settings in Device → Log:

To be able to set the Syslog server IP address, the parameter Syslog must be enabled by
selecting On.
• Unite settings in Device → Unite:

Enter the IP address and password (if any) to the IMS3.

For details, see 2.2.1.2 Create a Template in WinPDM/IMS3 DM, page 12 .
Include only non-default parameters to minimize network traffic when applying the template.

If using Easy Deployment, the IP address of the IMS3 DM in the template can either
be set or it can be left blank in which case the server discovery process is used at
every startup. For more information, see C.3 IMS3 Discovery, page 99 .

5. Create numbers for the handsets.

For details, see 2.2.1.3 Create Numbers in WinPDM/IMS3 DM, page 12 .
6. Apply the network template to the handsets.
For details, see 2.2.1.5 Apply a Template to a Handset with a Number, page 13 and 2.2.1.1
Configure the Handset Using Easy Deployment, page 11 .
2.2.1.1 Configure the Handset Using Easy Deployment

With the Easy Deployment procedure, handsets can be installed using a (staging) WLAN with a
predefined SSID and security profile and a Unite module with IMS3 DM.

The handsets are automatically installed if the following requirements are met:
• The LAN and VoWiFi system is configured for Easy Deployment.
• No network (SSID) is configured in the handset.
• The Call ID (endpoint number), that is, the phone number of the handset is configured.

When using Easy Deployment, make sure that the phone number plan and the
parameters are correct. Inaccurate configuration can only be corrected in the IMS3 DM.

For further details, see Appendix C Easy Deployment, page 97 .

8AL90392ENAAed02 11 /113
Configuration guide

2.2.1.2 Create a Template in WinPDM/IMS3 DM

Select only the modified parameters. If all parameters are selected, the system
performance decreases.

To create a template, perform the following steps:

1. In WinPDM/IMS3 DM, select the Templates tab and click Template → New… or CTRL + N.
The New template window is opened.
2. In the Device type and Parameter definition drop-down lists, select the corresponding
device type and parameter definition to use.
3. In the Name field, enter a descriptive name for the template.
4. Click OK. The Edit template window is opened.
5. Set the required parameters.
6. Click OK to save the template.

2.2.1.3 Create Numbers in WinPDM/IMS3 DM

Create a range of numbers and apply the templates previously created in WinPDM/IMS3 DM.
Important

When adding numbers to handsets that already exist in the system, WinPDM/IMS3
DM overwrites the existing parameters in the handset, since these handsets are
not saved in WinPDM/IMS3 DM.
Do not add numbers to handsets that are already configured and functional.

The parameter version of the template must be equal to or less than the selected
parameter version.

1. Open WinPDM/IMS3 DM.

2. Select the Numbers tab and click Number → New… or CTRL + N. The New numbers
window is opened.
3. In the Device type and Parameter definition drop-down lists, select the corresponding
device type and parameter definition to use.
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. Click OK.

The maximum range that can be added at a time is 100 numbers.

6. Apply the network settings template to the selected handsets. See 2.2.1.5 Apply a Template
to a Handset with a Number, page 13 .
7. Apply the common settings template to the selected handsets. See 2.2.1.5 Apply a Template
to a Handset with a Number, page 13 .

If the 802.1X security protocol with EAP-TLS or EAP-PEAP/MSCHAPv2 is used,

also include the trusted CA certificate(s) and select the required application
certificate.

Application certificates cannot be distributed using a template, as they are

individual. The application certificates must be installed first by editing each number.
See D.3 Easy Deployment and Certificates, page 110 .

8AL90392ENAAed02 12 /113
Configuration guide

2.2.1.4 Apply a Template to a Handset without a Number

Applying a template to a handset without a number is possible only in WinPDM.

1. Place the handset in the DP1 Desktop Programmer cradle.

2. In the Found Device Wizard window, select Apply template.
3. Click Next. Only templates with a parameter version matching the selected handset are
shown.
4. Select the template to apply and click OK.
The number of parameters in the template affects the time it takes to apply the template to the
selected handset.

2.2.1.5 Apply a Template to a Handset with a Number

To apply a template to a handset with a number in WinPDM/IMS3 DM, perform the following steps:
1. Open WinPDM/IMS3 DM.
2. In the Numbers tab, select the handset(s) you want to apply the template to.

If several handsets are selected, they must be of the same device type and have
the same parameter version.

3. Right-click and select Apply template.

Only templates with a parameters version matching the selected handsets are shown.
4. Select the template to apply and click OK.
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 on the Numbers tab, the column Last run template shows the name of
the most recently applied template.

2.2.2 Deploy the Handset Using WinPDM

Using WinPDM only one handset can be deployed at a time. After configuring the WLAN parameters,
it is possible to log in to the IMS3 DM for future OTA management.

To deploy a handset using WinPDM, perform the following steps:

Figure 2. Connecting Handsets to the computer

1. Open WinPDM.
2. Create numbers for the handsets.

8AL90392ENAAed02 13 /113
Configuration guide

For details, see 2.2.1.3 Create Numbers in WinPDM/IMS3 DM, page 12 .

3. Create a template with the following network parameters:
• Network settings in Network → General:

Under the respective network (Network A, Network B, Network C, or Network D), set the
required parameters, for example, system settings for WLAN, such as SSID, Security mode, and
any certificates for 802.1X. If using a security mode that requires certificates, also use an NTP
server to assure the correct time in the handset, as certificates are only valid within a certain time.
• VoIP settings in the VoIP menu:

Configure, for example, VoIP information, SIP proxy ID and address.

• Syslog settings in Device → Log:

To be able to set the Syslog server IP address, the parameter Syslog must be enabled by
selecting On.
• Unite settings in Device → Unite:

Enter the IP address and password (if any) to the IMS3.

For details, see 2.2.1.2 Create a Template in WinPDM/IMS3 DM, page 12 .

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 the first login.
The Easy Deployment process overcomes this problem by using a staging WLAN,
which does not use 802.1X.
If a network template has already been created in IMS3 DM, it can be exported and imported to
WinPDM. For more information, see A.2 Manage Templates using WinPDM and IMS3 DM, page
91 .
4. Place the handset into the DP1 Desktop Programmer cradle via a USB port. In the dialog
window that appears after connecting the handset, select WinPDM. For more information,
see 3.4.8.4 USB Behavior, page 30 .
5. In the Device Wizard window, select Associate with number and press OK.
6. Select the handset to associate with and 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 Item , page 14 –Item , page 14
.
7. Apply the network settings template to the handset. See 2.2.1.5 Apply a Template to a
Handset with a Number, page 13 .
8. In the Numbers tab, right-click the handset’s number and select Manage certificates. A
manage certificate window opens.
9. In the Trust list tab and Application certificates tab, click Browse and select the
certificates to import. Click Close.
10. In the Numbers tab, right-click the handset’s number and select Edit parameters.
11. Select the active network (Network A, Network B, Network C, or Network D).
12. In the Security mode drop-down list, select EAP-TLS or PEAP-MSCHAPv2.
13. In the EAP application certificate drop-down list, select the application certificate to be
used. Click OK.
14. Remove the handset when the synchronization is finished.

8AL90392ENAAed02 14 /113
Configuration guide

Repeat Item , page 14 –Item , page 14 for every handset.

2.2.3 Deploy the Handset Using the Admin Menu

It is possible to configure a handset using the Admin menu. This can be useful when neither WinPDM
nor IMS3 DM is available and only a few handsets need to be configured.

Only a limited set of settings can be configured using the Admin menu. WPA2
Enterprise authentication, for example, cannot be configured.

To deploy a handset using the Admin menu, perform the following steps:
1. Enter the Admin access code 40022 while the handset displays No network..

40022 is the default Admin access code that can be configured in WinPDM/IMS3
DM. In case none of them is available, contact the system administrator. For more
information, see 3.4.22 Change Admin Access Code, page 39 .

2. Set the following parameters:

• In the Network setup menu, set all the required system settings for the WLAN, for
example SSID and Security mode. No certificates can be entered, or referred to using
the Admin menu.
• In the Unite menu, set the IP address and password (if any) to the IMS3.
• In the VoIP menu, set VoIP protocol and SIP proxy IP address to access the PBX.

Applicable to SIP mode only.

• In the Syslog menu, the parameter Syslog mode must be enabled by selecting On to
be able to set the Syslog server IP.

2.2.4 Set the Handset to SIP or NOE Mode

By default, the handset runs in NOE mode. It can be set to SIP mode in the handset and the IMS3
DM as well.

Set SIP Mode in the Handset

1. Go to the Admin menu:
• If the handset has been factory reset or not been configured, in the Connecting/No
network screen at start-up enter the Admin access code.
• If the handset has been configured, press Menu, select Settings, and enter the Admin
access code.

2. Select NOE mode → Off.

The handset restarts after the configuration.

Set SIP Mode in the IMS3 DM

1. Select VoIP → General.
2. In the NOE mode drop-down list, select Off.
The handset restarts after the configuration.

8AL90392ENAAed02 15 /113
Configuration guide

2.3 Handset Configuration

Handsets can be configured in the following ways:

• Using WinPDM/IMS3 DM
For more information, see 2.3.1 Configure Handsets Using WinPDM/IMS3 DM, page 16 .
• Using the Admin menu of the handset
For more information, see 2.3.2 Configure the Handset Using the Admin Menu, page 16 .
2.3.1 Configure Handsets Using WinPDM/IMS3 DM

This requires that handsets have been deployed to the VoWiFi system with access to WinPDM/IMS3
DM. For more information, see 2.2 Handset Deployment into the VoWiFi System, page 9 . The
recommended procedure for configuring handsets is to create a template to be able to apply the same
configuration to several handsets simultaneously.

To configure handsets, perform the following steps:

1. Open the WinPDM/IMS3 DM.
2. Create a template with the required settings.
For details, see 2.2.1.2 Create a Template in WinPDM/IMS3 DM, page 12 .
3. Apply the template to the handsets.
For details, see 2.2.1.5 Apply a Template to a Handset with a Number, page 13 or 2.2.1.4 Apply
a Template to a Handset without a Number, page 13 .
2.3.2 Configure the Handset Using the Admin Menu

The Admin menu of the handset can be used to perform quick changes in the handset.

For more information, see 3.4.21 System Administration in the Handset, page 37 .

8AL90392ENAAed02 16 /113
Configuration guide

2.4 Handset Synchronization

Handset synchronization transfers parameter changes between the handset and the WinPDM/IMS3
DM and vice versa as follows:
• The handset synchronizes with the IMS3 DM at startup and immediately after every handset
parameter change. (The change is done either by using the handset keypad or by editing
parameters in the IMS3 DM.)
If a parameter has been changed in the handset, it is transferred to the WinPDM/IMS3 DM.
• If a parameter has been changed in the WinPDM/IMS3 DM while the handset was offline, the
changes are transferred when the handset is online.
• If a parameter has been changed in the WinPDM/IMS3 DM, it is transferred to the handset.
• If the same parameter has been changed in both the WinPDM/IMS3 DM and the handset, the
value in the WinPDM/IMS3 DM overrides the value in the handset.
• Changes made in the IMS3 DM are not stored in the WinPDM as there is no connection between
the two systems. The database of the WinPDM synchronizes with the handset when the handset
is placed in the DP1 Desktop Programmer cradle via USB.

Since there is no connection between the WinPDM and IMS3 DM except over the
handset, the WLAN and device manager settings can differ in the WinPDM and IMS3
DM. Parameters can revert to old values when the WinPDM synchronization process
runs, that is, when the handset is placed in the DP1 Desktop Programmer cradle.

When the handset is removed from the DP1 Desktop Programmer cradle, the
handset goes online with the Unite system, and the synchronization process with the
IMS3 DM starts. The solution for this is to avoid storing handset numbers in the
WinPDM.

8AL90392ENAAed02 17 /113
Configuration guide

3 Parameter Configuration

This section describes how to configure handset parameters using WinPDM/IMS3 DM.

The parameters are defined in .def files that are regularly updated. For example,
parameters are added or removed, or their values are changed.

Parameter configuration can restart the handset. The text Remotely updated is shown in
the handset display when the handset restarts after the update.

For more information, see the help text that is accessible for each parameter by clicking the Help icon
in the Edit parameters view.

3.1 Networks

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 the Admin menu in the
handset or the WinPDM/IMS3 DM) and is visible in the handset. For more information, see 3.1.2
Change Name of Network, page 18 .

A handset can be configured for up to four different WLANs but only for one IMS3 and one VoIP
System.

Network A is the default system that is used throughout this manual.

3.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.

3.1.2 Change Name of Network

The name is shown when selecting network in the handset.

1. Select Network → Network A (Network B, Network C, or Network D).
2. In the Network name field, enter the name of the network.

3.1.3 Enable Switch Between Networks

The handset can be configured to switch between networks on the site.

1. Select Network → General.
2. In the Auto-switch network drop-down list, select On.
The parameter Auto-switch network timeout appears, which defines the time before the
handset tries to connect with the next included network.
3. Enter a value in seconds for Auto-switch network timeout.
4. For the networks that should be included in the auto-switch network:
Select Network → Network A Network B, Network C, or Network D. In the Include in auto-
switch network drop-down list, select Yes to enable the switch to Network A → Network B →
Network C → Network D.

8AL90392ENAAed02 18 /113
Configuration guide

3.2 Handset IP Address Settings

Applicable to SIP mode only.

The handset IP address settings can be configured in two ways:

• The handset can be configured to receive an IP address automatically from a DHCP server, see
3.2.1 Automatic IP Address Settings, page 19 .
• If no DHCP server is used, a unique IP address must be entered manually for each handset, see
3.2.2 Static IP Address (Manual) Settings, page 19 .

3.2.1 Automatic IP Address Settings

1. Select Network → Network A Network B, Network C, or Network D.
2. In the DHCP mode drop-down list, select one of the following:
• Off (static mode)
• Use any DHCP
• Favour Alcatel DHCP — Applicable to NOE mode only.
• Only use Alcatel DHCP — Applicable to NOE mode only.

The phone IP address, subnet mask, and default gateway are automatically set up.

3.2.2 Static IP Address (Manual) Settings

1. Select Network → Network A Network B, Network C, or Network D.
2. In the DHCP mode drop-down list, select Off (static). 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.

3.2.2.1 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.

Primary DNS Server

1. Select Network → Network A Network B, Network C, or Network D.
2. In the Primary DNS field, enter the IP address for the primary DNS server.

Secondary DNS Server

1. Select Network → Network A Network B, Network C, or Network D.
2. In the Secondary DNS field, enter the IP address for the secondary DNS server.

8AL90392ENAAed02 19 /113
Configuration guide

3.3 Network Settings

3.3.1 Radio and Channel Selection

The handset supports both 5 GHz radio and 2.4 GHz radio, but 5 GHz radio and 2.4 GHz radio
cannot be used simultaneously. The radio defines the channels that can be used.

5 GHz Channels

It defines which 5 GHz channels to use. It is recommended to use the value UNII-1.

Select Advanced only if the channels are to be set in the 802.11 channels parameter, see
Advanced: 802.11 Channels, page 21 .

To select a 5 GHz channel, perform the following steps:

1. Select Network → Network A Network B, Network C, or Network D.
2. In the Frequency band drop-down list, select 5 GHz.
3. In the 5 GHz channels drop-down list, select one of the following:
• All
• Non DFS
• UNII-1
• UNII-3
• UNII-1, UNII-2
• UNII-1, UNII-2, UNII-3
• UNII-1, UNII-2 Extended
• Advanced
• 802.11k

8158s and 8168s WLAN Handsets has optional support for roaming based on 802.11k neighbor
lists. To enable it, set this parameter to 802.11k. If 802.11k is enabled, only a subset of the 2.4/5
GHz channels that are enabled are scanned for a new AP candidate when roaming. It is decided
by a 802.11k neighbor list which channels to scan, which must be sent by the current AP. If this
partial scan fails to find a roaming candidate, a full scan of all channels is performed as if the
parameter had been set to All.

The selected World Mode Regulatory Domain defines which channels to use. For
more information, see table below.

Table 1 Bands and Channels Used by WiFi A-radio

Channel denomination Frequency band Channels

Non DFS 5.150–5.250 GHz, 5.725– 36, 40, 44, 48 149, 153,
5.845 GHz 157, 161, 165

UNII-1 5.150–5.250 GHz 36, 40, 44, 48

UNII-2 5.250–5.350 GHz 52, 56, 60, 64

8AL90392ENAAed02 20 /113
Configuration guide

Channel denomination Frequency band Channels

UNII-2 Extended 5.470–5.725 GHz 100, 104, 108, 112,116,

120, 124, 128, 132, 126,
140

UNII-3 5.725–5.850 GHz 149, 153, 157, 161, 165

2.4 GHz Channels

It defines which 2.4 GHz 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 WLAN performance. Select
Advanced only if the channels are to be set in the parameter 802.11 channels. For more information,
see Advanced: 802.11 Channels, page 21 .

To select a 2,4 GHz channel, perform the following steps:

1. Select Network → Network A Network B, Network C, or Network D.
2. In the Frequency band drop-down list, select 2.4 GHz.
3. In the 2.4 GHz channels drop-down list, select one of the following:
• All
• 1, 6, 11
• Advanced

Advanced: 802.11 Channels

It defines which 802.11 channels to use. It is only used if the parameter in 2.4 GHz channels or 5
GHz channels is set to Advanced.

1. Select Network → Network A Network B, Network C, or Network D.

2. Enter channels to scan in a comma-separated list, for example 1, 6, 11. The order has no
impact, that is, 11, 6, 1 gives the same result.

It is not possible to scan channels in 2.4 GHz and 5 GHz simultaneously.

If Advanced is selected in WinPDM/IMS3 DM, it is indicated in the handset display

by having all options unchecked in the Settings → Admin menu → Network setup
→ 2.4 GHz channels, or 5 GHz channels menu. If any of these unchecked
channels are selected using the handset’s Admin menu, the only way to reselect
Advanced, is to reconfigure it in WinPDM/IMS3 DM.

3.3.2 SSID

Service Set Identifier (SSID) is the name of the network that the handset associates with.

1. Select Network → Network A Network B, Network C, or Network D.

2. In the SSID field, enter system SSID.

SSID is case-sensitive.

8AL90392ENAAed02 21 /113
Configuration guide

3.3.3 Security Settings

The WLAN can be configured in WinPDM/IMS3 DM to use various encryption and authentication
schemes. The most frequently used encryption and authentication modes are directly available in the
Security mode drop-down list of Network → Network A Network B, Network C, or Network D.

The use of extensive authentication schemes without any fast roaming method can
cause incidents of dropped speech during handover due to the time to process the
authentication.

3.3.3.1 Open

If no encryption or authentication is required, perform the following steps:

1. Select Network → Network A Network B, Network C, or Network D.
2. In the Security mode drop-down list, select Open.
3.3.3.2 WPA/WPA2-PSK

To select WPA/WPA2-PSK as the security mode, perform the following steps:

1. Select Network → Network A Network B, Network C, or Network D.
2. In the Security mode drop-down list, select WPA/WPA2-PSK.
3. In the WPA/WPA2-PSK passphrase field, enter the passphrase for WPA/WPA2-PSK.

3.3.3.3 PEAP-MSCHAPv2

PEAP-MSCHAPv2 (PEAPv0/EAP-MSCHAPv2) recommends the use of trusted certificates for

authentication of the WLAN.

To select PEAP-MSCHAPv2 as the authentication method, perform the following steps:

1. 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.
• In the Trust list tab of the Manage Certificates window, click Browse and select the trusted
certificates to import. Click Close.

This is not needed if validation is disabled in Item , page 22 .

Skip this step, if SCEP is used to automatically download trusted certificates to the
handset. For more information, see C.5 SCEP, page 101 .

2. Select Network → Network A Network B, Network C, or Network D.

3. In the Security mode drop-down list, select PEAP-MSCHAPv2.
4. In the EAP authentication identity field, enter the user name for EAP authentication.
5. In the EAP authentication password field, enter the password for EAP authentication.
6. The EAP anonymous identity is an optional parameter. This field is used for unencrypted
use with EAP types that support different tunnelled identity, such as EAP-PEAP/MSCHAPv2,
in order to reveal the real identity only to the authentication server.
7. In the Validate server certificate field, select No to disable the validation of server
certificate during authentication.

By disabling the validation, the server is not authenticated and may be a rouge one.

The server must send its complete certificate chain.

8AL90392ENAAed02 22 /113
Configuration guide

3.3.3.4 EAP-TLS

It is recommended to use trusted certificates to authenticate the WLAN, and it is required to use
application certificates to present to the WLAN for client authentication.

To select EAP-TLS as the authentication method, perform the following steps:

1. For server validation, import the trusted certificate:
• In the Numbers tab, right-click the handset’s number and select Manage certificates.
• In the Trusted list and the Application certificates tabs of the Manage Certificates
window, click Browse and select the certificates to import. Click Close.

This is not needed if validation is disabled in Item , page 23 .

2. Select Network → Network A Network B, Network C, or Network D.
3. In the Security mode drop-down list, select EAP-TLS.
4. In the EAP authentication identity field, enter the user name for EAP authentication.
5. EAP anonymous identity is an optional parameter. This field is used for unencrypted use
with EAP types that support different tunnelled identity, such as EAP-PEAP/MSCHAPv2, in
order to reveal the real identity only to the authentication server.
6. In the EAP client certificate drop-down list, select the application certificate (in PKCS#12
format).
7. In the Validate server certificate field, select No to disable the validation of server
certificate during authentication.

By disabling the validation, the server is not authenticated and may be a rouge one.

The server must send its complete certificate chain.

3.3.3.5 WinPDM Authentication

When this parameter is enabled, it is required to enter the Admin access code to the handset before
connecting to WinPDM.

This parameter is only visible if USB behavior is set to Ask or WinPDM in Device →
General.

To enable WinPDM authentication, perform the following steps:

1. Select Device → General.
2. In the WinPDM authentication drop-down list, select On.

3.3.4 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 setting is World mode (802.11d). The handset gets its regulatory settings from
the AP. If it is not supported by the AP, perform the following steps:

1. Select Network → Network A Network B, Network C, or Network D.

2. In the World mode regulatory domain drop-down list, select one of the following:
• World mode (802.11d) (default)
• USA
• Canada

8AL90392ENAAed02 23 /113
Configuration guide

3.3.5 IP DSCP for Voice/Signaling

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 Network B, Network C, or Network 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 in SIP mode)
• 0x28 (40) - Class selector 5
• 0x20 (32) - Class selector 4
• 0x1A (26) - Assured forwarding 31 (default for signaling in SIP mode)
• 0x18 (24) - Class selector 3
• 0x10 (16) - Class selector 2
• 0x08 (8) - Class selector 1
• 0x00 (0) - Default
• 0x00 (0) - Use system value (default for voice and signaling in NOE mode)

3.3.6 TSPEC Call Admission Control

This parameter defines if Call Admission Control via WMM TSPECs (Traffic Specifications) is to be
used or not on the WLAN.

To configure TSPEC Call Admission Control, perform the following steps:

1. Select Network → Network A Network B, Network C, or Network D.
2. In the TSPEC Call Admission Control drop-down list, select one of the following:
• Off to disable traffic streams allocation for each call.
• Automatic to enable traffic streams allocation for each call if required by the system.
Even if the system does not require admission control the call will be set up.
• Required if the system must require admission control to set up a call.

3.3.7 Roaming Method

To select a roaming method, perform the following steps:

1. Select Network → Network A Network B, Network C, or Network D.

2. In the Roaming method drop-down list, select one of the following:
• PMKSA Caching — Use it in systems that do not support FT or OKC.
• Fast BSS Transition (FT) — Use FT if supported by the system, otherwise OKC.
• OKC — Select this option to use Opportunistic Key Caching instead of FT on an AP
that supports both.

3.3.8 IP Connectivity after Roaming

If the Check IP connectivity after roaming is set to Yes, it sends ICMP pings to the default gateway
after each roam to verify that the local IP address is still valid.

8AL90392ENAAed02 24 /113
Configuration guide

3.3.9 A-MPDU Packet Aggregation

During interoperability testing there has been issues with the Aruba controllers when the A-MPDU
aggregation was enabled in the handset. Therefore, it is recommended to set this parameter to Off
when connecting to Aruba or Stellar Wi-Fi and On when connecting to other networks.
3.3.10 Use DCHP User Class

When Use DHCP user class is enabled, the handset adds USER CLASS to the DHCP request.

To enable DHCP user class, perform the following steps:

1. Select Network → Network A Network B, Network C, or Network D.
2. In the Use DHCP user class drop-down list, select one of the following formats:
• RFC3004 format
• Microsoft format

If the wrong format is used, the handset might not get any IP connection.

3. In the DHCP user class field, enter the user class to be used for identifying the handset in
the DHCP server.
3.3.11 Configure TFTP in NOE Mode

To configure TFTP parameters in NOE mode, perform the following steps:

1. Select VoIP → NOE.

2. The following NOE parameters are available::
• Config file TFTP IP address — Defines the static IP address of the NOE TFTP server
for the PBX configuration file.
• Config file redundancy TFTP IP address — Defines the static IP address for the PBX
configuration file.
• Config file TFTP port number — Defines the port number of the NOE redundancy
TFTP server for the PBX configuration file for static mode.

3.4 Handset Settings

Parameters described in this section can be changed using the handset and/or the WinPDM/IMS3
DM to assist the user or set the initial value when the handset is deployed.

For more information, see the User Manual, ALE 8158s and 8168s WLAN Handsets,
8AL90391ENAA.

When the handset is placed in the charger, some settings for audio adjustments and
actions cannot be changed using the keypad.
3.4.1 Automatic Key Lock

Automatic key lock is used to avoid unintentional key presses. It can also be configured using the
handset.

To activate or deactivate Automatic key lock, perform the following steps:

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.

8AL90392ENAAed02 25 /113
Configuration guide

3.4.2 Automatic Key Unlock

To enable or disable the Automatic key unlock, perform the followings steps:
1. Select Device → Settings.
2. In the Automatic key unlock drop-down list, select one of the following:
• On – The handset keypad is unlocked automatically at incoming calls and messages.
• Off – The handset is not unlocked automatically.

3.4.3 Phone Lock

Applicable to SIP mode only.

Phone lock is used to prevent unauthorized usage of the handset. A phone lock code is required to
unlock the handset and access its functions.

If configured, it is possible to dial any of up to five predefined emergency numbers when

the handset is locked. For more information, see 3.6.8 Emergency Call Numbers, page
52 .

It is not recommended to use phone lock when using the shared phone feature. For
more information, see 3.4.16 Shared Phone, page 33 .

To activate or deactivate Phone lock, perform the following steps:

1. Select Device → Settings.
2. In the Phone lock drop-down list, select one of the following:
• On – The handset is locked after a specified time when it is not used. For more
information, see 3.4.4 Automatic Lock Time, page 26 .
• On in charger – The handset is locked when placed in a charger.
• Off – The handset is not locked.

When Phone lock is activated, define a password in the Phone lock code field.

3.4.4 Automatic Lock Time

When either the key lock or the phone lock is set to On, the lock is activated after a specified period of
time. It is possible to change the default time (20 seconds).

To change the Automatic lock time, perform the following steps:

1. Select Device → Settings.
2. In the Automatic lock time drop-down list, select one of the following:
• 5 seconds
• 10 seconds
• 20 seconds
• 30 seconds
• 1 minute
• 3 minutes

8AL90392ENAAed02 26 /113
Configuration guide

3.4.5 Multifunction Button

Configure the Multifunction Button as a Shortcut

Applicable to SIP mode only.

The Multifunction button can be defined for different functions on long press and multi press by
performing the following steps:

1. Select Shortcuts → Multifunction Button Long press (or Multi press).

2. Continue with 3.4.17.4 Shortcut Settings, page 34 .

Configure the Multifunction Button to be a PTT button

Applicable to 8168s only.

Applicable to SIP mode only.

By default, the Mute button is used as a Push-to-Talk (PTT) button. Although, for users who are
required to wear gloves, it is more practical to configure the Multifunction button for the PTT function.

To set the Multifunction button as a PTT button, perform the following steps:

1. Select Device → Call.

2. In the Multi func button for PTT drop-down list, select On.

Multifunction Button Mode

Applicable to NOE mode only.

In NOE mode, Multifunction button mode defines what function the top button has. To configure
this parameter, perform the following steps:

1. Select Device → Settings.

2. In the Multifunction button mode drop-down list, select one of the following:
• Display Profiles menu — Opens the menu on short press.
• NOE Prog Key message — Sends NOE message ProgKey 10 to the PBX on long
press. If configured in the PBX, this may be used to set up calls to an alarm server, for
example.

Applicable to 8168s only.

8AL90392ENAAed02 27 /113
Configuration guide

3.4.6 Audio Settings

To set the volumes for the different audio signals of the handset, perform the following steps:

1. Select Audio → Volume.

2. Select the appropriate volume type from the drop-down lists:
• Handsfree volume — Sets the volume used in an active call in loudspeaking mode.
• Headset volume — Sets the volume used in an active call when a headset is
connected.
• Speaker volume — Sets the volume used in an active call in speaker mode (normal
call mode).

3. In the Persistent volumes drop-down list, select Enable to automatically store volume
changes in the handset for future calls.
The parameter affects the Normal, Headset, and Loudspeaking mode.

For selection of headset, see 3.4.7.1 Headset Type, page 29 .

Changing volume parameters can result in lower sound quality and high sound level.
Evaluate carefully before applying.

3.4.6.1 Hearing Aid

When Hearing aid is enabled, the volume is changed so that the magnetic signal fulfill the
requirements for a hearing aid with telecoil.

To enable this parameter, perform the following steps:

1. Select Audio → General.

2. In the Hearing aid drop-down list, select On to enable it.

3.4.6.2 Ring Signal in Handset

To define if the ring signal should be available in both the headset and the loudspeaker or only in the
loudspeaker, perform the following steps:

1. Select Audio → General.

2. In the Ring signal in headset drop-down list, select Both headset and loudspeaker or Only
loudspeaker.

3.4.6.3 Gain Offset Calibration

To optimize audio quality, perform the following steps:

1. Select Audio → Handset, Audio → Headset, Audio → Loudspeaker (Applicable to 8168s

only.), and/or Audio → Bluetooth (Applicable to 8168s only.).
2. Change the values of the following as necessary:
• Michrophone gain offset
• Speaker gain offset
• Microphone side-tone gain offset

8AL90392ENAAed02 28 /113
Configuration guide

Changing the parameters can result in lower sound quality and high sound level.
Evaluate carefully before applying.

3.4.7 Headset Configuration

3.4.7.1 Headset Type

To select the headset model that is used, perform the following:

1. Select Headset → General.

2. Select the applicable item from the Headset type drop-down list:
• Mic on boom
• Mic on cable
• User model

If selected, additional configuration is required, see 3.4.7.2 Headset User Model, page 29 .

3.4.7.2 Headset User Model

The following 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:
• Microphone gain
• Speaker gain
• Side tone

Changing the parameters can result in lower sound quality and high sound level.
Evaluate carefully before applying.

3.4.8 Actions when the Handset is Placed in the Charger

The behavior of the handset can be configured when placed in a charger.

3.4.8.1 In charger Call Behavior

Applicable to SIP mode only.

To configure In charger call behavior, perform the following steps:

1. Select Device → Call.
2. In the In charger call behavior drop-down list, select one of the following:
• No action
• End – The handset ends an ongoing call when placed in a charger.
• Put on Loudspeaker – The handset turns on the loudspeaker when placed in a
charger during a call.

Applicable to 8168s only.

8AL90392ENAAed02 29 /113
Configuration guide

3.4.8.2 In Charger Action when Not in Call

To configure the In charger action when not in call parameter, perform the following steps:
3. Select Device → Settings.
4. In the In charger action drop-down list, select one of the following:
• No action – No action is performed when handset is placed in the charger.
• Switch off1 – The handset is switched off when placed in the charger.
• Sound off2 – The handset is muted when placed in the charger (except for messages
with set Break through parameter, for example, Prio 1 messages).

To mute all messages (regardless of priority), set the Device → Messaging → Show and
indicate messages in charger to Off.
• Change profile – The handset changes profile when placed in the charger.
• In the Change profile in charger drop-down list, select the profile to be used.
• If needed, configure the selected profile, see 3.5 Profiles, page 40 .

3.4.8.3 Clear Lists in Charger

Applicable to SIP mode only.

If Clear lists in charger is set to Yes, message and call lists are deleted when the handset is placed
in the charger. To configure this parameter, perform the following steps:
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.

3.4.8.4 USB Behavior

When set to Ask, a dialog window is displayed every time the phone is connected to a PC over USB.
Otherwise, it behaves as defined.

1. Select Device → General.

2. In the USB Behavior drop-down list, select one of the following:
• Ask — A dialog window is displayed every time the handset is connected to a PC over
USB where one of the below modes may be chosen.
• WinPDM — This mode allows the handset to communicate to the application WinPDM
on a PC.
• MTP — This mode shows the handset as a media device and allows transferring and
viewing log files from the handset.
• Charge — This option sets the handset to charge only mode.

If Ask or WinPDM is selected, it is possible to configure the WinPDM authentication parameter

to restrict access to WinPDM. For more information, see 3.3.3.5 WinPDM Authentication, page 23
.

1
Applicable to SIP mode only.
2
Applicable to SIP mode only.

8AL90392ENAAed02 30 /113
Configuration guide

3.4.9 Transfer Unlock File

1. Select Device → General.

2. In the Transfer Unlock File drop-down list, enter the unlock file as a string.

Unlocking is performed for debugging purposes. Due to security reasons, the handset
needs to be factory-reset after debugging is finished.
3.4.10 Hide Missed Call Window

Applicable to SIP mode only.

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.

To hide the Missed call window, perform the following steps:

1. Select Device → Call.
2. In the Show missed calls dialog window drop-down list, select No.

3.4.11 Prevent the Handset to Switch off

Applicable to SIP mode only.

It is possible to prevent the user from switching off the handset when holding down the End key .
When Block switch off is activated and the End key is held down, the Switch off? dialog window
does not appear in the handset.

1. Select Device → General.

2. In the Block switch off drop-down list, select one of the following:
• No – The user can switch off the handset.
• Yes – The user cannot switch off the handset.

3.4.12 Disable Mute Function

To prevent the user from muting the handset, perform the following steps:

1. Select Audio → General.

2. In the Prevent silent drop-down list, select one of the following:
• On – The handset cannot be set to silent by using mute or by decreasing the volume.
• Off – The handset can be set to silent by using mute or by decreasing the volume
(default).

8AL90392ENAAed02 31 /113
Configuration guide

3.4.13 Prevent Calls from Being Saved in the Call List

Applicable to SIP mode only.

It is possible to disable storing outgoing and incoming calls in the Call list, which can be useful to
prevent unauthorized access to the Call list.

To prevent all calls from being saved, perform the following steps:
1. Select Device → Call.
2. In the Enable call list drop-down list, select Off.

3.4.14 Battery Warning

The warning when the battery is low can be set to different modes.

1. Select Device → Settings.

2. In the Battery warning drop-down list, select one of the following:
• Sound repeatedly
• Sound once
• Sound off

3.4.15 No Network and No Access Warning

3.4.15.1 No Network Warning

If the handset has no coverage, it shows No network in the handset display in idle mode. It also gives
a vibrating alert (if enabled), a beep signal (if enabled), and displays a dialog window (if enabled by
the system administrator).

To configure the No network warning, perform the following steps:

1. Select Device → General.
2. In the No network warning drop-down list, select one of the following:
• Indicate repeatedly – The beep is on (if enabled), No network is displayed in idle
mode, the vibrating alert is on (if enabled), the dialog window is on (if enabled). This
simultaneous indication is repeated every minute for 30 minutes.
• Indicate once – The beep is on (if enabled), No network is displayed in idle mode, the
vibrating alert is on (if enabled), the dialog window is on (if enabled). This simultaneous
indication is made only once.
• Indication off – The beep is off (even if enabled), No network is displayed in idle
mode, the vibrating alert is off (even if enabled), the dialog window is either on or off,
depending on the parameter settings.

Even if Indication off is set, the dialog window still appears when Dialog window
for no network and no access warnings (in Device → General) is set to Yes.

8AL90392ENAAed02 32 /113
Configuration guide

3.4.15.2 No Access Warning

Applicable to SIP mode only.

If the handset has no access, has lost messaging and/or voice connection, it shows No access, Voice
only, or Messaging only in the handset display in idle mode. It also gives a vibrating alert (if enabled),
a beep signal (if enabled), and a dialog window (if enabled by the system administrator).

No access means that there is neither voice nor messaging connection.

To configure the No access warning, perform the following steps:

1. Select Device → General.
2. In the No access warning drop-down list, select one of the following:
• Indicate repeatedly – This is the default and recommended setting for any handset
used with medical devices. The beep is on, No access/Voice only/Messaging only is
displayed in idle mode, the vibrating alert is on (if enabled). This simultaneous
indication is repeated every minute for 30 minutes.
• Indicate once – The beep is on, No access is displayed in idle mode, the vibrating
alert is on (if enabled). This simultaneous indication is made only once.
• Indication off – The beep is off, No access is displayed in idle mode, the vibrating alert
is off (if enabled) depending on the parameter settings.

Even if Indication off is set, the dialog window still appears when Dialog window
for no network and no access warnings (in Device → General) is set to Yes.

3.4.15.3 Dialog Window for No Network/No Access Warnings

Applicable to SIP mode only.

This parameter defines if the dialog windows No network, No access, Voice only, and Messaging only
are visible or not on the handset display.
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 No network/No access/Voice only/Messaging only appears
on the handset display.
• No – The dialog window No network/No access/Voice only/Messaging only does not
appear on the handset display.

3.4.16 Shared Phone

Applicable to SIP mode only.

It is possible to use the handset as a shared phone. When sharing a phone with multiple users, each
user has their individual settings that are accessible using a personal user name and 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:

• A handset without certificates
• A IMS3

8AL90392ENAAed02 33 /113
Configuration guide

It is possible to set the same password on multiple personal handsets.

If a personal phone number is accidentally entered into the shared handset, the handset
becomes personal and cannot be used as a shared phone any longer. The handset
must be configured to be a shared phone again.

By default, the handset is in Personal mode. To set it to Shared, perform the following steps in
WinPDM/IMS3 DM:
1. Select Device → General.
2. In the Phone mode drop-down list, select one of the following:
• Personal
• Shared

3.4.17 Shortcuts

Applicable to SIP mode only.

One-click access to predefined functions can be configured for soft keys, hot keys, navigation keys,
and the Multifunction button. For example, a soft key can be configured to make a call. Generally,
shortcuts are only available when not in a call and in idle mode. Although, a hot key configured to
Services with, for example, Send data, is available during calls in case of 8168s.

Shortcuts can be configured in Shortcuts in WinPDM/IMS3 DM, except for soft keys that can be
configured in the User Profiles folder.

3.4.17.1 Configure a Hot Key

A hot key is activated by pressing a pre-programmed button 0, 2–9 for more than 1 second in idle
mode. For example, the hot key function can be used to change the profile, send a message, or make
a phone call to a specific number.
1. Select Shortcuts → Hot keys 0 (or 2–9).
2. Continue with 3.4.17.4 Shortcut Settings, page 34 .
3.4.17.2 Configure a Soft Key

When configuring soft keys, both name and function must be set.
1. Select User Profiles → Normal/Profile X → Soft keys → Soft key left, Soft key middle, or
Soft key right.
2. In the Soft key name field, enter the name of the soft key shortcut to be displayed in the
handset.
3. Continue with 3.4.17.4 Shortcut Settings, page 34 .
3.4.17.3 Configure a Navigation Key
5. Select Shortcuts → Navigation Key Up (or Down, Left, or Right).
6. Continue with 3.4.17.4 Shortcut Settings, page 34 .
3.4.17.4 Shortcut Settings
7. In the Function drop-down list, select the required function:
• Not used
• Phone call
• Phone call loudspeaker3

3
Applicable to 8168s only.

8AL90392ENAAed02 34 /113
Configuration guide

• Call list
• Contact list
• Central phone book (system-dependent feature)
• Message inbox4
• Send message5
• Change profile normal
• Change profile 1–3 for 8158s, Change profile 1–9 for 8168s (when selecting one of
these options, the profile must first be configured, see 3.5 Profiles, page 40 .)
• Open menu (Main menu, Calls, Call services, Connections, Contacts,
Messaging6, Services7, Profiles, Settings.)
• Executive service X (1–10)8
• Logout9
• Call diversions
• RSSI measure
• Execute call service X (1–16)
8. In the Value field, enter the applicable value. This is mandatory when using the Phone call
function.
9. In the Control question drop-down list, select Yes to display the Proceed? window after the
key is pressed. This is used to prevent a function from being accessed by mistake.

3.4.17.5 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.

To configure the soft key functions, perform the following steps:

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
• Messaging10
• No action
• End call
• Hold
• Loudspeaker11
• New call (Put active on hold)
• Retrieve
• Switch
• Transfer (To held call)
• Transfer to new call (Blind transfer)

4
Applicable to 8168s only.
5
Applicable to 8168s only.
6
Applicable to 8168s only.
7
Applicable to 8168s only.
8
Applicable to 8168s only.
9
Applicable to Share phone feature only.
10
Applicable to 8168s only.
11
Applicable to 8168s only.

8AL90392ENAAed02 35 /113
Configuration guide

In case No action is selected, soft keys are hidden during a call. Instead, the default soft keys
Loudspeaker and End call are displayed.
3.4.18 Import Contacts

Applicable to SIP mode only.

Phone book files (local phone book) can be imported to the handset using WinPDM/IMS3 DM. The
phone book file is a tab-separated .txt file that contains two items per row, number and name.

For more information, see the Installation and Operation Manual, Portable Device Manager for
Windows (WinPDM), 8AL90832ENAB.

3.4.19 Company Phone Book

Applicable to SIP mode only.

It is possible to create a phone book that is administered centrally and uploaded to the handset from
WinPDM/IMS3 DM. If this feature is used, the entries from Contacts and Company Phone Book are
merged. The Company Phone Book entries are locked and cannot be edited in the handset.

Perform the following steps:

1. Create a Company phone book file. For more information, see Create a Company Phone
Book File, page 36 .
2. Import the Company phone book file to the WinPDM/IMS3 DM. For more information, see
the Installation and Operation Manual, Portable Device Manager for Windows (WinPDM),
8AL90832ENAB.
3. Upload the Company phone book file to the handset(s), see the Installation and Operation
Manual, Portable Device Manager for Windows (WinPDM), 8AL90832ENAB.

Create a Company Phone Book File

The company phone book file (.cpb) is normally created from an Excel file using a script to extract the
information and create the phone book file (.cpb). The Excel file, Company Phonebook.xls, is
delivered by the supplier.

The format of the rows in the phone book file is as follows: <Name><tab><phone number><carriage
return>, followed by additional rows for each entry.

The following characters are accepted in the handset number field in the phone book file, but are
ignored when the phone book file is created:
• Left parenthesis: (
• Right parenthesis: )
• Hyphen: -
• Space: “”

8AL90392ENAAed02 36 /113
Configuration guide

3.4.20 Central Phone Book

Applicable to SIP mode only.

If the system is equipped with a messaging server with a phone book service, the Central phone book
on that server can be accessed from the handset.

1. Select Device → Unite.

2. In the Central phone book number field, enter the number to the Central phone book.
The number to be used is set to 999999 by default. If the system is not equipped with a Central
phone book, this menu option can be removed from the handset by entering an empty value.

3.4.21 System Administration in the Handset

The handset has a hidden menu for system administrators that contains the following information:
• Device information including software, hardware, WLAN, network, and TFTP information
• NOE mode
• Site survey tool
• Network setup menus
• IP address and endpoint number options for Unite, VoIP, SIP, and Syslog server
• Logging options
• Factory reset option
• USB behavior
• Time and date (Applicable to NOE mode only.)

To access the Admin menu, select Menu → Settings, and enter the Admin access code. The default
code is 40022, which is configurable in WinPDM/IMS3 DM.

If the handset has been factory reset or not been configured, in the Connecting/No
network screen at start-up enter the Admin access code.

8AL90392ENAAed02 37 /113
Configuration guide

3.4.21.1 Admin Menu Tree in the Handset

8AL90392ENAAed02 38 /113
Configuration guide

3.4.21.2 Quick Access to Admin Menu Functions and Device Information

Applicable to SIP mode only.

For quick access to device information and certain functions, the following codes can be used in idle
mode.

Code Information

*#34#
To access Device info in the Admin
menu.
Select either of the following menus:
Software, Hardware, WLAN info,
Network info, User ID, TFTP info.

*#76# To view RSSI information.

*#77#
To access Site survey tool in the Admin
menu.
Select either of the following menus:
Show RSSI, Scan all channels, Scan
selected channels, Range beep, Range
beep level.

3.4.22 Change Admin Access Code

In case of a forgotten Admin access code, it is possible to reset it by performing the following steps:
1. Open WinPDM/IMS3 DM.
2. Select Device → General.
3. In the Admin access code field, enter a new password.

3.4.23 Block Access to the Admin Menu

By default, it is possible to access the Admin menu from the handset. To prevent users from
accessing the Admin menu, perform the following steps:

1. Open WinPDM/IMS3 DM.

2. Select Device → General.
3. In the Admin menu access drop-down list, select Off.

8AL90392ENAAed02 39 /113
Configuration guide

3.5 Profiles
3.5.1 User Profiles

User profiles are used to set up customized profiles for incoming calls, vibrating alerts, key sound,
and so on. This can be useful when more users use the same handset, who want different sound
profiles. It can also be used for temporary settings, for example, while in a meeting, incoming calls
can be set to silent.

To create a user profile, perform the following steps:

1. Select User Profiles → Normal or Profile X (where X represents Profile 1–3 for 8158s,
Profile 1–9 for 8168s).
2. In the Profile name field, enter the name of the profile.
3. Configure the following parameters:
• Sound and Alerts — Contains sound and alert settings for calls and messages. See
3.5.1.1 Configure Sound and Alerts, page 40 .
• Presence and diversion — Contains settings for message absent and call diversion.
See 3.5.1.2 Configure Presence and Diversion, page 41 .
• Answering — Contains settings for how incoming calls are answered. See 3.5.1.3
Configure Answering, page 42 .
• Soft keys — Contains shortcut settings to predefined functions using key press. See
3.5.1.4 Configure Soft Keys, page 42 .
• Call service — Enables call services, for example Do not disturb. See 3.5.1.5
Configure Call Service, page 43 .

4. If required, select the profile to be active, by selecting User Profiles and change the default
Active Profile to the desired profile.

It is possible to configure profiles through the handset menu as well. See the User
Manual, ALE 8158s and 8168s WLAN Handsets, 8AL90391ENAA

To exclude a parameter from Profile X, use the option Not used.

3.5.1.1 Configure Sound and Alerts

To configure sounds and alerts, perform the following steps:

1. Select User Profiles → Profile X → Sound and Alerts.
2. In the Ring volume mode drop-down list, select one of the following:
• Silent – There is no ring signal.
• Volume X (1–8) – Different ring signal volumes from lowest (1) to highest (8).

3. In the Vibrator drop-down list, select one of the following:

• On – The vibrating alert is active for incoming calls and messages.
• On if silent – The vibrating alert is active for incoming calls and messages only if the
handset is muted or the volume is set to Silent.
• Off – The vibrating alert is off.

4. In the Key sound drop-down list, select one of the following:

• Click – A click is heard when a key is pressed on the handset.
• Tone – A tone is heard when a key is pressed on the handset.
• Silent – There is no sound when a key is pressed on the handset.

5. In the Message alert drop-down list, select one of the following:

8AL90392ENAAed02 40 /113
Configuration guide

Applicable to 8168s only.

The message sound for incoming messages can be either a melody or a single
beep.

Only the parameter Custom sounds according to beep code can be customized.
For more information, see Customize the Default Handset Beeps, page 95 .

• 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 the system.
• 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 – Melody coming from defined custom
sounds.

6. In the Message volume drop-down list, select one of the following:

Applicable to 8168s only.

• Silent – There is no audible message indication for incoming messages.

• Volume X (1–8) – Different message indication volumes from lowest (1) to highest (8).
• Follow ring volume – The message indication volume follows the ring volume.

7. In the Call type (1–6) drop-down list, select the ring signal for incoming calls.

Applicable to NOE mode only.

3.5.1.2 Configure Presence and Diversion

Applicable to SIP mode only.

To configure message absent and call diversion parameters, perform the following steps:
1. Select User Profiles → Profile X → Presence and diversion.
2. In the Message absent drop-down list, select one of the following:

Applicable to 8168s only.

• On – When a handset receives a message, it indicates that it is absent. The message

can be redirected to another destination.
• Off – Message absence is disabled.

3. In the Diversion settings used in profile drop-down list, select Yes to use the configured
diversion settings for the profile.
4. In the Diversion for all calls drop-down list, select Off or On. When enabled, all calls are
diverted to the number specified by the All calls diversion number parameter.

8AL90392ENAAed02 41 /113
Configuration guide

5. In the Diversion on user busy drop-down list, select Off or On. When enabled, calls are
diverted to the number specified by the On busy diversion number parameter if the user is
busy.
6. In the No answer diversion drop-down list, select Off or On. When enabled, calls are
diverted to the number specified by the No answer diversion number parameter if the user
does not answer an incoming call.

3.5.1.3 Configure Answering

Applicable to SIP mode only.

To configure how to answer incoming calls, perform the following steps:

1. Select User Profiles → Profile X → Answering.
2. In the Answering used in profile drop-down list, select Yes to use the configured answering
behavior for the profile.
3. In the Answering key drop-down list, select one of the following:
• Call key — Incoming calls are answered by pressing the Call key.
• Any key — Incoming calls are answered by pressing any key.

4. In the Answer mode drop-down list, select one of the following:

• Normal – The Call key needs to be pressed to answer the call.
• Automatically – The call is automatically answered after 1 second.
• Loudspeaking – The call is answered in loudspeaking mode by pressing the Call key.
• Automatically loudspeaking – The call is automatically answered in loudspeaking
mode after 1 second.

Loudspeaking and Automatically loudspeaking is applicable to 8168s only.

5. In the Can reply with a message template when rejecting a call drop-down list, select
Yes. The dialog window Reply with a message template? appears when rejecting an
incoming call.

Applicable to 8168s only.

If no message templates are defined, the dialog window is not shown.

For more information, see 3.8 Message Templates, page 65 .

3.5.1.4 Configure Soft Keys

Applicable to SIP mode only.

To configure soft key functions, perform the following steps:

1. Select User Profiles → Profile X → Soft keys.
2. In the Soft keys used in profile drop-down list, select Yes to enable soft keys for the profile.
3. In the Soft keys configurable from handset drop-down list, select Yes to be able to
configure soft keys for the profile from the handset.
4. Select Soft Key X (where X represents the left, middle, or right soft key).

5. The following parameters can be configured:

8AL90392ENAAed02 42 /113
Configuration guide

Soft key name – Defines the text that is shown in the handset display above the soft key.

A maximum number of 6 characters fits in the soft key name.

Function – Defines the function to be connected to the soft key. For the list of functions, see
3.4.17.4 Shortcut Settings, page 34 .
Value – Defines a value (for example, a phone number) for a function.

Only certain functions require a value.

Control Question – Defines if a Proceed? dialog window appears when pressing a soft key.
3.5.1.5 Configure Call Service

To configure call services, perform the following steps:

1. Select User Profiles → Profile X → Call service.

The Call service must first be configured in Device Call services.

2. The following parameters can be configured:

• When activated — Select the Call service to be used when this profile is activated.
• When deactivated — Select the Call service to be used when this profile is
deactivated.

Call service is not available for Normal profile.

3.5.2 System Profiles

Applicable to 8168s only.

Applicable to SIP mode only.

A system profile can be used when there are certain settings in a handset that the user is not allowed
to change.

A system profile overrides all profile settings, on all parameters in the group, for
example, soft keys.

To create a system profile, perform the following steps:

1. Create a System Profiles Sub-Group.

The following sub-groups are available:

• Presence groups — Contains settings for message absent and call diversion. See
3.5.2.1 Configure Presence Groups (Sub-group), page 44 .
• Answering groups — Contains settings for how incoming calls are answered. See
3.5.2.2 Configure Answering Groups (Sub-group), page 44 .
• Sound and alerts groups — Contains sound and alert settings for calls and
messages. See 3.5.2.3 Configure Sounds and Alerts Groups (Sub-group), page 44 .
• Soft key groups — Contains shortcut settings to predefined functions using soft keys.
See 3.5.2.4 Configure Soft Key Groups (Sub-group), page 45 .
• Idle display groups — Contains settings to show the system profile name during idle
mode.

8AL90392ENAAed02 43 /113
Configuration guide

For more information, see 3.5.2.6 Create System Profile Using Predefined Sub-Groups, page 46 .
2. Connect the system profile to the created sub-group(s).
Once a system profile is created, it can be used whenever desired and can be turned off and on
again. For more information, see 3.5.2.7 Activate and Deactivate System Profile, page 46 .

3.5.2.1 Configure Presence Groups (Sub-group)

To configure presence groups, perform the following steps:

1. Select System Profiles → System Profiles Sub Groups → Presence groups → Presence
group X.
2. In the Name of group field, enter a descriptive name.
3. In the Message absent drop-down list, select one of the following:

Applicable to 8168s only.

• On – When a handset receives a message, it indicates that it is absent. The message can
be redirected to another destination.
• Off – Message absence is disabled.

3.5.2.2 Configure Answering Groups (Sub-group)

To configure answering groups, perform the following steps:

1. Select System Profiles → System Profiles Sub Groups → Answering groups → Answering
group X.
2. In the Name of group field, enter a descriptive name.
3. In the Answer mode drop-down list, select one of the following:
• Normal – The Call key needs to be pressed to answer the call.
• Automatically – The call is automatically answered after 1 second.
• Loudspeaking – The call is answered in loudspeaking mode by pressing the Call key.
• Automatically loudspeaking – The call is automatically answered in loudspeaking mode
after 1 second.

3.5.2.3 Configure Sounds and Alerts Groups (Sub-group)

To configure sounds and alerts groups, perform the following steps:

1. Select System Profiles → System Profiles Sub Groups → Sound and alerts groups → Sound
and alerts group X.
2. In the Name of group field, enter a descriptive name.
3. In the Ring volume mode drop-down list, select one of the following:
• Silent – There is no ring signal.
• Volume X (1–8) – Different ring signal volumes from lowest (1) to highest (8).

4. In the Vibrator drop-down list, select one of the following:

• On – The vibrating alert is active for incoming calls and messages.
• On if silent – The vibrating alert is active for incoming calls and messages only if the
handset is muted or the volume is set to Silent.
• Off – The vibrating alert is off.

5. In the Internal ring signal, External ring signal, and Callback ring signal drop-down lists,
select one of the following signals:
• Ring signal X – Defines one of the 15 different predefined melodies.
• Beep X — Defines one of the 7 beeps.

8AL90392ENAAed02 44 /113
Configuration guide

• Custom sound X (Custom sound 8–10) – Defines one of the 3 proprietary melodies
made by coding with the help of a specific code table.

6. In the Key sound drop-down list, select one of the following:

• Click – A click is heard when a key is pressed on the handset.
• Tone – A tone is heard when a key is pressed on the handset.
• Silent – There is no sound when a key is pressed on the handset.

7. 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.

Only the parameter Custom sounds according to beep code can be customized.
For more information, see Customize the Default Handset Beeps, page 95 .

• 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 the system.
• 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 – Melody coming from defined custom
sounds.

8. In the Message volume drop-down list, select one of the following:

• Silent – There is no audible message indication for incoming messages.
• Volume X (1–8) – Different message indication volumes from lowest (1) to highest (8).
• Follow ring volume – The message indication volume follows the ring volume.

3.5.2.4 Configure Soft Key Groups (Sub-group)

To configure soft key groups, perform the following steps:

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), and edit the required settings.
• Soft key name – Defines the text that is shown in the handset display above the soft key.

A maximum number of 6 characters fits in the soft key name.

• Function – Defines the function to be connected to the soft key. For the list of functions,
see 3.4.17.4 Shortcut Settings, page 34 .
• Value – Defines a value (for example, a phone number) for a function.

Only certain functions require a value.

Control Question – Defines if a Proceed? dialog window appears when pressing a soft key.

8AL90392ENAAed02 45 /113
Configuration guide

3.5.2.5 Configure Idle Display Groups (Sub-group)

By default, the system profile name is displayed in the handset. In case it is not needed
to show the system profile name, perform the following steps:

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.

3.5.2.6 Create System Profile Using Predefined Sub-Groups

To create a system profile, it must be connected to the desired predefined sub-groups.

If Not Used is selected, user profile settings are used if set.

To create a system profile using predefined sub-groups, perform the following steps:
1. Select System Profiles → System Profile X.
2. Configure the required parameters:
• In the Profile name field, enter a descriptive name to identify this system profile.
• Activation and deactivation sound — Defines the sound that is heard when the profile
is activated or deactivated.
• Presence group – Defines which predefined presence group (sub-group) is used in this
system profile.
• Sound and alerts group – Defines which predefined sound and alerts group (sub-group)
is used in this system profile.
• Soft keys group – Defines which predefined soft key group (sub-group) is used in this
system profile.
• Answering group – Defines which predefined answering group (sub-group) is used in
this system profile.
• Idle display group – Defines which predefined idle display group (sub-group) is used in
this system profile.

3.5.2.7 Activate and Deactivate System Profile

When a system profile is created, it can be activated using IMS3 DM or a Unite application. For
example, the application could be triggered by a positioning beacon.

If a certain system profile always needs to be active on a handset, it is recommended to

hide the settings/menus that the user cannot change.

To activate a system profile, perform the following steps:

1. Select System profiles.
2. In the Active system profile drop-down list, select one of the following:
• Normal – No system profile is used.
• System profile 1–System profile 5

A system profile overrides all User Profile X and Normal (profile) settings on all parameters in the
group, see the following two examples.

8AL90392ENAAed02 46 /113
Configuration guide

Example 1
Figure 3. User Profile X/Normal — Soft Key Settings

Figure 4. System Profile — Soft Key Settings

8AL90392ENAAed02 47 /113
Configuration guide

In Figure 3. User Profile X/Normal — Soft Key Settings, page 47 , the User Profile X (or the profile
Normal) is configured with a shortcut to open the menu on the left soft key.

In Figure 4. System Profile — Soft Key Settings, page 47 , a system profile shortcut to make a call to
the administrator Susan, is configured for the free middle soft key (2). When activating the system
profile Susan, the left soft key Menu disappears, because the system profile overrides the complete
group of the soft key parameters.

The way parameter groups are arranged is seen under System Profiles → System
Profiles Sub Groups.

3.6 Telephony

Applicable to SIP mode only.

3.6.1 Endpoint ID and Endpoint Number

The Endpoint ID and Endpoint number are automatically received when registering the handset in
the VoWiFi system. The Endpoint ID is normally the user’s name registered in the PBX and it is
displayed in the handset in idle mode. To change the displayed name, see 3.10.2 User Display Text,
page 67 . The Endpoint number cannot be changed.

If the Endpoint ID needs to be changed, inWinPDM/IMS3 DM select VoIP → General,

and enter a new ID in the Endpoint ID field.

If required, shorten the Endpoint number. For more information, see 3.6.2 Endpoint
Number Display Length, page 48 .

3.6.2 Endpoint Number Display Length

It defines the total number of digits to be displayed on the handset display in idle mode when the
Endpoint number is shown. From 1 up to 6 digits (starting from the end of the number), or all, can be
displayed.
1. Select Device → Settings.
2. In the Endpoint number display length text field, enter the number length to be displayed.

3.6.3 VoIP Protocol

A protocol is a set of standard rules for data traffic required to send information over a communication
channel. The supported protocols are SIP and NOE. For more information on NOE network settings,
see 3.3.11 Configure TFTP in NOE Mode, page 25 .

To configure SIP parameters, perform the following steps:

1. Select VoIP → SIP.
2. The following SIP parameters are available:
• SIP Transport – Defines the protocol (UDP, TCP or TLS) to be used for SIP signaling.
The TLS setting requires the Root certificate of the PBX certificate (The server must
send its complete certificate chain.) to be uploaded as a trusted certificate. It is also
possible to turn off the validation of the server certificate by setting Validate server
certificate to No. In the SIP TLS client certificate drop-down list, select a certificate to
be used for TLS applications, for example. secured VoIP signaling.

8AL90392ENAAed02 48 /113
Configuration guide

• Outbound proxy mode – Select Yes if the handsets are to connect with the SIP proxy
through an outbound proxy. Set to No if the handsets are to connect directly with the
SIP proxy (there may be two).
• Primary SIP proxy – Defines the primary SIP proxy by either an IP address, a domain
name, or an IP address together with a port number.

Examples of valid formats are the following:

• 192.168.1.1
• proxy1.mydomain.com
• 192.168.1.1:5060

Domain names are resolved using DNS records, and refer either to a DNS A record (address
record) or a DNS SRV record (service record). While an A record is a single IP address, a SRV
record originates from multiple A records, of which the handset tries the two highest prioritized IP
addresses it receives in the DNS response when it registers with the primary SIP proxy.

Only a plain IP address is shown in the handset’s Admin menu (under VoIP →
SIP → SIP proxy IP address).

If the handset fails to register with the primary SIP proxy, it can register with the optional
secondary SIP proxy.

The parameter is only visible if Outbound Proxy mode is set to No.

• Secondary SIP proxy – Defines the optional secondary SIP proxy, which is used if the
handset fails to register with the primary SIP proxy. See definition examples in Primary
SIP proxy above.

When the handset has connected to the Secondary SIP proxy, it continuously tries to reconnect
to the Primary SIP proxy.
• Outbound proxy – Defines the primary outbound proxy by a domain name, an IP
address, or an IP address with a port number.

The parameter is only visible if Outbound Proxy mode is set to Yes.

• Listening port – Defines the port that the handset listens to for incoming SIP traffic.
• SIP proxy ID – Defines the SIP proxy by a domain name.

This parameter is only needed when an outbound proxy is defined. It can also be
used to specify a domain name when parameters Primary SIP proxy and
Secondary SIP proxy have assigned IP addresses.

• SIP proxy password — Defines the password to be used when the handset registers
at the SIP proxy.
• Send DTMF using RFC 2833 or SIP INFO – Defines the path the DTMF signaling
should take. If set to RFC 2833, the DTMF signaling is sent in the RTP stream, that is,
from handset to handset. If set to SIP INFO, the DTMF signaling is sent using SIP
signaling, that is, through the PBX.
• Hold type – Defines the type of hold that is sent when the handset puts a call on hold.
The selection depends on what types of hold the PBX support. For more information

8AL90392ENAAed02 49 /113
Configuration guide

about what types of hold the PBX support, see the applicable documentation for the
PBX.
• Registration identity – Defines if the endpoint uses its number, ID, or MAC address
for the registration with the SIP proxy.
• Authentication identity – Defines if the endpoint uses its number, ID, or MAC address
for the authentication with the SIP proxy.
• Call forward locally – When enabled, the call forwarding is handled locally by the
handset instead of updating the PBX.

The handset must be switched on and must have coverage to handle the Call
forward locally functionality.

• MOH locally (Music on Hold) – If supported by the PBX, the handset plays music when
a call is on hold. If the PBX does not support MOH, the handset plays a tone when the
call is on hold.
• Hold on transfer – Puts a second call on hold before transfer, which is required by
some SIP proxy servers.
• Direct signaling – Defines whether calls originating from other sources than the
configured SIP Proxy should be accepted or redirected using USE PROXY message.
• SIP Register Expiration – Defines the number of seconds for register expiration to the
PBX.
• SIP Messages Behavior — Defines how the received SIP messages should be
handled. If set to Ignore, the received text in the SIP message is ignored. If set to
Display Management, the received text in the SIP message is shown on the display.
• Disable PRACK — Disables sending provisional ACK message.
• Far-End NAT Traversal — Used when the SIP server is not local and the phones are
behind a NAT. Enabling it allows phone communications to traverse a NAT device that
is farthest away from the SIP server and near the handsets.

3.6.4 Codec

A codec encodes a stream or signal for transmission, which is often used in streaming media
applications. This setting defines how to packetize and compress the sound in a voice call.

1. Select VoIP → General.

2. In the Codec configuration drop-down list, select the applicable codec.
• Opus Wideband
• G.711 A-law (EU)
• G.711 u-law (US)
• G.722
• G.729
• G.729A

Opus Wideband and G.722 are applicable to 8168s only.

3. In the Codec packetization time configuration drop-down list, select the packetization time
to use for speech (value 20–60 ms).

Applicable to SIP mode only.

8AL90392ENAAed02 50 /113
Configuration guide

3.6.5 Offer Secure RTP

When enabled, voice is sent over Secure RTP, if the other party also supports Secure RTP.

SIP Protocol
1. Go to VoIP → SIP
2. In the SIP Transport drop-down list, select TLS.
3. Go to VoIP → General
4. In the Offer Secure RTP drop-down list, select Yes.
5. Select the preferred SRTP encryption by assigning a value to VoIP → General → Secure
RTP Crypto, which appears when enabling Offer Secure RTP.
3.6.6 Internal Call Number Length

Defines the maximum number of digits to be interpreted as an internal call. 0 means the same
number of digits as in the endpoint number.

1. Select VoIP → General.

2. In the Internal call number length field, enter the number of digits.

3.6.7 ICE Negotation

Applicable to SIP mode only.

ICE negotiation can be used during call setup to enable NAT traversal and WebRTC interoperability.
NAT traversal allows data traffic to get to a specified destination when a device does not have a
public IP address. The handset supports the ICE, STUN and TURN protocols for NAT traversal.
1. Go to VoIP → General.
2. In the ICE Negotiation drop-down list, select Yes.
3. Set the STUN and TURN parameters depending on the protocol used.

The following parameters are available when ICE negotiation is enabled:

• STUN server address – Defines the STUN server to use for NAT traversal. Up to two STUN
servers can be configured which should be queried in parallel. The STUN server addresses to
the different servers should be separated by a semi-colon (;).

The server address must be entered in one of the following formats:

• A single DNS name and an optional port (for example, stun.example.com:1234)
• A comma-separated list of one or two IP addresses and optional ports (for example,
172.16.13.1:1234, 172.16.13.2)
• TURN server address – Defines the TURN server to use for NAT traversal.

A TURN server can be configured and the server address must be entered in one of the
following formats:
• A single DNS name and an optional port (for example, turn.example.com:1234)
• A comma-separated list of one or two IP addresses and optional ports (for example,
172.16.13.1:1234, 172.16.13.2)

A TURN server configuration can optionally be followed by a protocol specification such as

turn.company.tld?protocol=prot, where prot can be either tcp or udp.

8AL90392ENAAed02 51 /113
Configuration guide

• TURN server user name – Defines the user name for accessing the TURN server.
• TURN server password – Defines the password for accessing the TURN server.

3.6.8 Emergency Call Numbers

Applicable to SIP mode only.

Up to five different phone numbers can be reserved for emergency calls. These numbers can always
be called even when the phone or key locks are active.

1. Select Device → Emergency call numbers.

2. In the Emergency call numbers field, enter the desired emergency number(s).

For more information, see _5FATI_5FFile_5FNot__116814312.

3.6.9 Voice Mail Number

In some systems it is needed to assign the handset number of the voice mail service.

1. Select Device → Message center.

2. In the Voice mail number field, enter the number to the handset’s voice mail inbox.

3.6.10 Message Center Number

Specifies the number for the server responsible for Message Waiting Indication (MWI), if included in
the system.
1. Select Device → Message center.
2. In the Message Center number field, enter the number for the server.

3.6.11 Voice Mail Call Clears MWI

If enabled, the handset deactivates voice mail message waiting indications in the Message Center
when calling the defined voice mail number.

To enable Voice mail call clears MWI, perform the following steps:
1. Select Device → Message center
2. In the Voice mail call clears MWI drop-down list, select Yes.

3.6.12 Dial Pause Time

By adding a P to a phone number, a pause is added and is activated when dialing.

To configure the duration of the pause, perform the following steps:

1. Select Device → Call.
2. In the Dial pause time field, enter a pause time in the interval 1–3 s.

3.6.13 Quick Answer

The handset automatically answers a call (quick answer) when removed from the charger.

To enable Quick answer, perform the following steps:

1. Select Device → Call.
2. In the Quick answer drop-down list, select Yes.

8AL90392ENAAed02 52 /113
Configuration guide

3.6.14 Replace Call Rejected with User Busy

It is used if the system does not support call rejected.

To configure this function, perform the following steps:

1. Select VoIP → General.
2. In the Replace Call Rejected with User Busy drop-down list, select Yes or No.

3.6.15 Call Waiting Behavior

The default behavior is to indicate call waiting to the user. It is possible to change this behavior so that
the next incoming call is rejected, and a busy indication is sent back to the SIP proxy.

To configure Call waiting behavior, perform the following steps:

1. Select Device → Call.
2. In the Call waiting behavior drop-down list, select one of the following:
• Call waiting indication – The call is usually indicated by a short two-beep tone and an
Incoming call dialog window in the handset display.
• Reject call – The call is automatically rejected (No beep tone or dialog window
occurs).
• Reject call and show as missed – The call is automatically rejected and directed to
the Missed calls list. (No beep tone or dialog window occurs).

3.6.16 Call Waiting Sound

This parameter defines the sound of the call waiting indication, that is, how the user hears that a
second call is waiting, while already in a call. The call waiting sound is either a short two-beep tone, or
if the user is located in a noisy environment, a louder melody.

To enable the Call waiting sound, perform the following steps:

1. Select Device → Call.
2. In the Call waiting sound drop-down list, select one of the following:
• Beep – The call waiting sound is a short two-beep tone.
• Melody – The call waiting sound is a melody suitable for noisy environments.

Warning

Changing to the parameter Melody may result in a high sound level as the Call
waiting sound follows the volume of the active call, and can cause hearing
damage.

3.6.17 PTT Call Disconnect Warning

Applicable to 8168s only.

To enable a warning sound if the PTT session is terminated for any other reason than the user ending
the call, perform the following steps:
1. Select Device → Call.
2. In the PTT Call disconnect warning drop-down list, select Yes.

8AL90392ENAAed02 53 /113
Configuration guide

3.6.18 Configure In Call Functions

It is possible to define 10 extra system specific call services by codes. The codes can be configured
using any character. Use \U to make the handset prompt for user input with numerical characters.

1. Select Device → In call functionality → General purpose <number>.

2. In the Name field, enter the name to be displayed in the In call menu.
3. In the Data field, enter the access code to be used for the function.
4. In the Send as field, select one of the following:
• New call to send data as a new call.
• DTMF to send data in the current call.
• Transfer to send data as a call transfer.

5. In the Auto disconnect field, select Yes to automatically disconnect when the PBX has
received the command.

Ask the PBX supplier for example templates to configure the relevant menu of the PBX.

3.6.19 Hide In Call Function for PTT Calls

Applicable to 8168s only.

To hide the In Call function menu for PTT calls, perform the following steps:
1. Select Device → Call.
2. In the Hide In Call function for PTT calls drop-down list, select Yes.
3.6.20 Calling Line Identification Restriction (CLIR)

The handset can be configured to hide the caller’s number and name from the callee.

Even if CLIR is enabled, there is an override function available to authorities, such as

the police, that allows the caller’s identity to be seen.

To hide the caller’s number and name, perform the following steps:
1. Select Device → Call.
2. In the CLIR (Calling Line Identification Restriction) drop-down list, select On.

Always Show Name (Semi-CLIR)

The handset can be configured to show the name of the caller when this function is available by the
system. This parameter must be set in the callee’s handset.

This feature only functions correctly when used together with a PBX that supports it.

It is not possible to call or send a message using the displayed name shown, for
example, in the Call list, as the number is still restricted.

To enable the callee to see the name of the caller, perform the following steps:
1. Select Device → Call.
2. In the Always show name of incoming party (semi-CLIR) drop-down list, select Show name.

8AL90392ENAAed02 54 /113
Configuration guide

3.6.21 Allow Blind Transfer

1. Select Device → Call.
2. In the Allow blind transfer drop-down list, select No to disable the option to do a blind
transfer. By default, it is set to Yes.

Allowing blind transfer enables New call in the In-call menu.

3.6.22 Call Services

The Call services menu provides access to PBX-dependent functionality when not in call, such as
absence handling and call diversion. It is possible to use a call service when the handset starts up or
when it shuts down.

Up to 16 call services can be configured in WinPDM/IMS3 DM.

1. Select Device → Call Services.

2. Select a General service in the range of 1–16.
3. In the Name field, enter a name to be displayed in the Call services menu.
4. In the Data field, enter a PBX-specific code for the command.
5. In the Auto disconnect field, select Yes to automatically disconnect when the PBX has
received the command. Otherwise, select No.

The access codes are PBX-dependent.

Ask the PBX supplier for example templates to configure the relevant menu of the PBX.

Call Service on Startup

To execute a call service when the handset starts up, perform the following steps.

1. Select Device → Call services.

2. In the Call service on startup drop-down list, select a predefined call service.

Call Service on Shutdown

To execute a call service when the handset shuts down, perform the following steps.

1. Select Device → Call services.

2. In the Call service on shutdown drop-down list, select a predefined call service.
3.6.23 Call Using a Bluetooth Headset

Applicable to 8168s only.

To enable and configure Bluetooth behavior on outgoing calls, perform the following steps:

1. Select Bluetooth → General.

2. In the Bluetooth enabled drop-down list, select Yes to enable it.
3. In the Call with Bluetooth headset button drop-down list, select Last called number or
Predefined number to define what number the headset button should call when the handset
is not in a call or not ringing.

8AL90392ENAAed02 55 /113
Configuration guide

If the Predefined number is selected, type in the required number in the Predefined number
field that appears.

Applicable to SIP mode only.

4. In the Show audio transfer question on outgoing calls drop-down list, select Yes to have
the option to route the audio to the handset when starting a new outgoing call with a
connected Bluetooth headset. In this case, the user is informed that the audio is routed
through the headset and can choose to route it back to the handset. Otherwise, no dialog
window is displayed.

Applicable to SIP mode only.

3.7 Messaging Settings

Applicable to 8168s only.

Applicable to SIP mode only.

It is possible to configure how incoming messages are indicated and displayed in the handset.

1. In System Profiles → System Profiles Sub Groups → Sound and alerts groups → Sound and
alerts group 1–5, the following parameters can be configured:
• Vibrator — Defines if the handset vibrates when receiving incoming calls and
messages. For more information, see 3.5.1.1 Configure Sound and Alerts, page 40 .
• Message alert — Defines the message sound for incoming messages. For more
information, see 3.5.1.1 Configure Sound and Alerts, page 40 .
• Message volume — Defines the message volume for incoming messages. By default,
the message volume follows the ring volume, but a different message volume can be
set with this parameter. For more information, see 3.5.1.1 Configure Sound and Alerts,
page 40 .

2. In Device → Messaging, the following parameters can be configured:

• Message list representation — Can be set to number/name or message text.
• Message text size — Defines the text size used when displaying messages.
• 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 3.7.3 Examples of TTR and TTP Settings, page 61 .

The following options can be selected:

• Close manually
• 10/20/30 seconds
• 1/2/5/10 minutes
• 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
8AL90392ENAAed02 56 /113
Configuration guide

is paused. When the TTP elapses for a message, it is put last in the queue. See also
3.7.3 Examples of TTR and TTP Settings, page 61 .

The following options can be selected:

• No prioritization
• Prioritize 10/20/30 seconds
• Prioritize 1/2/5/10 minutes
• Prioritize forever
• Repeat message indication — This parameter enables/disables message indications. It sets
whether a message indication is repeated until confirmed by the user or not. The 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. The following options are available:
• Never activated
• Only for urgent messages
• Always activated
• Message alert during call — Defines if a message alert should be played when receiving a
message during a call. The following options are available:
• Never activated
• Only for urgent messages
• Always activated
• IM option mode — This parameter is used for customer-specific applications and sets that
three soft keys are placed automatically, that is on soft keys or in an option menu (list).
• Call priority

This parameter defines the following:

• 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.

Table 2 Call Priority vs PTT Priority

Call priority PTT invitation Disconnection of ongoing call?

(priority)1

0 1 No, since this call priority setting

overrides all PTT invitations
regardless of priority.

6 6 No, an ongoing call is not

disconnected when the priority is
equal.

8AL90392ENAAed02 57 /113
Configuration guide

Call priority PTT invitation Disconnection of ongoing call?

(priority)1

2 1 Yes, immediately since the PTT

priority is set to 1 and is also higher
than Call priority.

3 2 Yes, after 10 seconds since the PTT

priority is higher than Call priority.

10 1 Yes, immediately since the PTT

priority is set to 1 and also is higher
than Call priority.

10 2 Yes, after 10 seconds since the PTT

priority is higher than Call priority.

1 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 3 Call Priority vs Message Priority

Call priority Displayed Call information suppressed?

message (priority)

0 1 No, since this call priority setting

overrides all messages regardless of
priority.

7 6 Yes, since the priority of the

displayed message is higher than the
incoming call.

6 6 Yes, since the message is

considered as most important when
the priority is equal.

1 3 No, since the priority of the incoming

call is higher than the displayed
message.

10 1 Yes, the call information is always

suppressed regardless of the
message priority.

• Show and indicate messages in charger — Defines how incoming messages are
displayed/indicated when the handset is placed in the charger.

8AL90392ENAAed02 58 /113
Configuration guide

All incoming messages are affected by this setting including PTT invitations
received as messages and all other messages regardless of priority (even
messages with breakthrough such as high/alarm priority).

To silence only messages without breakthrough (low/normal priority), enable the

Sound off parameter instead in Device → Settings → In charger action.

To silence only messages without breakthrough (low/normal priority), enable the Sound off
parameter instead in Device → Settings → In charger action.
• Receive messages in charger — Defines if received messages are saved or discarded when
the handset is placed in the charger.

For more information, see 3.10.4 Rotate Display Text, page 68 .

3.7.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.

Message alerts can be configured in WinPDM/IMS3 DM in System Profiles → System

Profiles Sub Groups → Sound and alerts group 1–5 → Message alert.

Only the parameter Custom sounds according to beep code can be customized. For
more information, see Customize the Default Handset Beeps, page 95 .

3.7.1.1 Configure Beeps or High Beeps According to Beep Code

Beep code sent from a system or Corresponding sound from the handset
application

Beep code 0 No message alert is played

Beep codes 1–6 1–5, and 10 beeps, respectively

Beep code 7 Siren

In case of regular beeps, the handset plays the original message alerts that are mapped to the beep
codes. In case of high beep codes, the handset plays the original message alerts that are mapped to
the beep codes with a higher pitch than the regular beeps.

To configure Beeps or High beeps, perform the following steps:

1. Select System profiles → System profiles sub groups → Sound and alerts sub groups →
Sound and alerts group 1–5
2. In the Message alert drop-down list, select Beeps according to beep code or High beeps
according to beep code.

8AL90392ENAAed02 59 /113
Configuration guide

3.7.1.2 Enhanced Beeps According to Beep Code

Beep code sent from a system or Corresponding sound from the handset
application

Beep code 0 No message alert is played

Beep codes 1–3 1–3 beeps, respectively

Beep code 4 3 tones chime

Beep code 5 10 beeps

Beep code 6 Alarm sweep

Beep code 7 Siren

The handset plays the extended message alerts that are mapped to the beep codes, but in the form
of melodies.

1. Select System profiles → System profiles sub groups → Sound and alerts groups → Sound
and alerts group 1–5.
2. In the Message alert drop-down list, select Enhanced beeps according to beep code.

3.7.1.3 Custom Sounds According to Beep Code

Beep code sent from a system or Corresponding sound from the handset
application

Beep code 0 No message alert is played

Beep codes 1–7 Corresponding customized sound

The handset can play customized message alerts that are mapped to beep codes. The message
alerts must first be customized and then mapped to the beep codes.

It is recommended to use this feature to create a message alert that sounds like the
equipment (for example a respirator) that generates an alarm. Also use custom sound, if
it is desired to customize any of the default handset beeps (Beeps and Enhanced
beeps), see Appendix B Configure Custom Sounds, page 93 .

Create Customized Sound

1. Select Audio → Custom sounds → Custom sound X (where X represent 1–10).
2. Set the following parameters:
• Label – The name of the custom sound (required). The name is visible when mapping
the custom sound to a beep code later on.
• Melody – The text string represents a non-polyphonic sound. By default, example of
melodies, which are based on Enhanced beeps, are set for Custom Sound 1–7, see
Appendix B Configure Custom Sounds, page 93 .
• Beat – The tempo in beats per minute to be used when playing the sound.
• Style – The ratio of note to rest period to be used when playing the sound.
• Instrument – The instrument to be used when playing the sound.

8AL90392ENAAed02 60 /113
Configuration guide

Map Beep Codes to Customized Sounds

1. Select Audio → Custom message alert.
2. In the Beep code drop-down lists, select the customized sounds (8–10 available) to be used
for respective beep codes.

Enable Customized Sound

1. Select System profiles → System profiles sub groups → Sounds and alerts groups → Sound
and alerts group 1–5.
2. In the Message alert drop-down list, select Custom sounds according to beep code.
3.7.2 Message Retransmit Limit

This parameter defines the number of retransmissions before the transmission of the message is
considered as failed. The retransmission procedure begins if a sent message is not acknowledged
within 15 seconds.
1. Select Device → Unite.
2. In the Message Retransmit Limit, set the maximum number of retransmissions.
3.7.3 Examples of TTR and TTP Settings

Example 1
This example describes the message handling with the following message settings:

TTP – Prioritize forever

TTR – Close manually

It is recommended to use these settings if messages with the highest priority are always
displayed until the user closes the current message.

Figure 5. Queuing and Prioritizing for Messages with Equal Priorities

8AL90392ENAAed02 61 /113
Configuration guide

In Figure 5. Queuing and Prioritizing for Messages with Equal Priorities, page 61 , a message with
priority 2 is received at 13:59 and is displayed in the handset. Another message with equal priority is
received at 14:02 and is placed in the queue. If no messages with higher priority are received, the
user needs to close the currently displayed message to show the next message in the queue, in this
case, the message received at 14:02. The closed message is indicated as a read message in the
Messaging inbox.

Example 2
This example describes the message handling with the following message settings:
TTP – 20 seconds
TTR – Close manually

It is recommended to use these settings in case the user needs not to be interrupted for
20 seconds while reading a message, unless a message with a higher priority is
received. After the user has read a message, its priority is no longer important, and the
TTP expires.

Figure 6. Queuing and Prioritizing for Messages with Different Priorities

In Figure 6. Queuing and Prioritizing for Messages with Different Priorities, page 62 , a message with
priority 2 is received and displayed in the handset, and the TTP for the message is started.
After 10 seconds, a second message with priority 1 is received and displayed while the message with
priority 2 is put in the queue. TTP for the message with priority 2 is paused, and TTP for the message
with priority 1 is started.

After 20 seconds, TTP expires for the message with prio 1 and the message is placed in the queue.
The message with priority 2 is shown again and its TTP continues.

TTP expires after 10 seconds for the message with priority 2. In this case, all messages have been
shown for 20 seconds each, and the oldest shown message with the highest priority is displayed, in
this case, the message with priority 1. The handset does not indicate when it shows the message
again, since it already has been shown and indicated once. The message with priority 2 is placed in
the queue.

8AL90392ENAAed02 62 /113
Configuration guide

Example 3
This example describes the message handling with the following message settings:

TTP – 20 seconds

TTR – 2 minutes

It is recommended to use these settings in case the user needs not to be interrupted for
20 seconds while reading a message, unless a message with a higher priority is
received. After the user has read a message, its priority is no longer important, and the
TTP expires.

In addition, if a message is not shown again within the TTR interval, it is considered as
not important and is removed from the queue.

Figure 7. Message Handling without Manually Closing a Message

In Figure 7. Message Handling without Manually Closing a Message, page 63 , a message with
priority 2 is received and displayed in the handset. TTP and TTR for the message is started.

After 10 seconds, a second message with priority 1 is received and displayed while the message with
priority 2 is put in the queue. TTP for the message with priority 2 is paused, but TTR continues. TTP
and TTR for the message with priority 1 is started.

After 20 seconds, TTP expires but TTR continues for the message with prio 1 and the message is
placed in the queue. The message with priority 2 is shown again and its TTP continues.

TTP expires after 10 seconds but TTR continues for the message with priority 2. In this case, all
messages have been shown 20 seconds each, and the oldest shown message with the highest
priority is displayed, in this case, the message with priority 1. The handset does not indicate when it
shows the message again, since it already has been shown and indicated once. The message with
priority 2 is placed in the queue.

After 80 seconds, the TTR expires for the message with priority 2, and it is removed from the queue
and is indicated as an unread message in the Messaging inbox. When TTR expires for the message
with priority 1, it is also indicated as an unread message in the Messaging inbox.

If no messages have been read/closed manually and TTP expires for each message, a dialog window
New message(s): [number of messages]. View now? is displayed. All messages are indicated as
unread messages in the Messaging inbox.

8AL90392ENAAed02 63 /113
Configuration guide

Example 4
This example describes the message handling with the following message settings:

TTP – No prioritization

TTR – Close manually

It is recommended to use these settings if messages regardless of priority are read in

chronological order, that is, the newest message is displayed first.

Figure 8. Messages Displayed in Chronological Order Regardless of Priority

In Figure 8. Messages Displayed in Chronological Order Regardless of Priority, page 64 , a message

with priority 1 is received at 13:59. Another message with priority 2 is received at 14:02 and is
displayed. The message with priority 1 is put in the message queue. The user needs to close the
current message with priority 2 to show the message with priority 1 in the queue. When closing the
message with priority 2 it is indicated as a read message in the Messaging inbox.

8AL90392ENAAed02 64 /113
Configuration guide

3.8 Message Templates

Applicable to 8168s only.

Applicable to SIP mode only.

Handsets can be configured with predefined messages using the message template function.

A predefined message can be used in the following ways:

• The user can decline the call but still acknowledge the receipt of the call by selecting a predefined
message and sending it to the caller (requires a parameter setting, see 3.8.1 Configure the
Handset for Message Templates, page 65 below).
• The user replies to an incoming text message by selecting a predefined message and sending it
to the message sender (works by default).
• The user can construct a text message from a predefined message (works by default).

For additional information about how the message template function is used, see the User Manual,
ALE 8158s and 8168s WLAN Handsets, 8AL90391ENAA.

3.8.1 Configure the Handset for Message Templates

To activate the message template function in the handset so that a user can decline a call with a
predefined message, perform the following steps using WinPDM/IMS3 DM:
1. Select User Profiles → Profile X → Answering.
2. In the Can reply with a message template when rejecting a call drop-down list, select
Yes. The dialog window Reply with a message template? appears when rejecting an
incoming call.

Applicable to 8168s only.

If no message templates are defined, the dialog window is not shown.

3.8.2 Create Message Templates

A handset can be configured with up to five predefined messages. A message cannot exceed 50
characters.

To create a message, perform the following steps in WinPDM/IMS3 DM:

1. Select Device → Messaging → Message Template X (where X is 1–5).
2. In the Message text field, write a message, then click OK.

If a system uses a character set other than UTF-8 for SMS, make sure that the
characters entered into the message strings are compatible with the character set used
by the system. Entering characters that cannot be encoded by the system may cause a
type conversion error, the failure of the message to arrive at the intended recipient, and
a Message failed dialog window appears in the sender handset.

8AL90392ENAAed02 65 /113
Configuration guide

3.9 Regional Settings

3.9.1 Set Time & Date

Applicable to SIP mode only.

To set the time and date, perform the following steps:

1. Select Device → General.
2. In the Time zone drop-down list, select the applicable time zone.
3. If the time zone Other is selected, a string must be entered in the Time zone string field to
define the time zone.
For time zones, see http://www.timeanddate.com.

Only unquoted format is supported.

Enter the time zone string to automatically update for daylight saving time: <String = StdOffset
[Dst[Offset], Date/Time, Date/Time]>
• Std – Time zone (for example EST for Eastern Standard Time).
• Offset – Time difference between the time zone and the UTC (Universal Time
Coordinator).
• Dst – Daylight saving time zone (for example EDT for Eastern Daylight Time).
• Second Offset – Time difference between the daylight saving time and the UTC.
• Date/ Time, Date/ Time – The beginning and end of daylight saving time.
• Date format – Mm.n.d (d day of n week in the m month)
• Time format – hh:mm:ss in 24-hour format

A week always starts on a Sunday and the number for Sunday is 0.

Example:
North Carolina is located in the Eastern Time Zone. Eastern Standard Time (EST) is 5 hours
behind UTC (StdOffset = EST5), the Eastern Daylight Time (EDT) is 4 hours behind UTC
(DstOffset = EDT4). The daylight saving time for the year 2013 begins at two a clock, on a
Sunday, the second week in March (M3.2.0/2). The daylight saving time ends at two a clock, on a
Sunday, the first week in November (M11.1.0/2).
<String = EST5EDT4,M3.2.0/2,M11.1.0/2>
4. In the NTP server field, enter the address of the time server. If it is not set, the IP PBX
address is used.
5. Select Device → Settings.
6. In the Time format drop-down list, select one of the following time formats.
• 12:00 (AM/PM)
• 24:00

7. In the Date format drop-down list, select the required date format.

8AL90392ENAAed02 66 /113
Configuration guide

3.9.2 Select Default Language and Writing Language

The Language option defines the default language of the handset. This setting can later be changed
by the user.

The Writing language option defines the language used when writing in text fields.

1. Select Device → Settings.

2. In the Language and the Writing Language drop-down lists, select the languages to be
used.

3.9.3 Dialing Tone Pattern

Applicable to SIP mode only.

To define the tone pattern to use when dialing, perform the following steps:

1. Select Audio → General.

2. In the Dialing tones pattern drop-down list, select the applicable region.

3.10 Display
3.10.1 Hide Menu Items

Applicable to 8168s only.

It is possible to hide certain menu items in the handset.

To configure Visibility, perform the following steps:

1. Select Customization → Visibility.
2. Select Hide, Show, or Read only for the applicable menu items in the drop-down lists. If
Read only is selected, the menu item is visible in the handset, but cannot be edited by the
user.

Several menu items of the following categories can be hidden:

• Connections
• Messaging (Applicable to 8168s only.)
• Profiles
• Settings

3.10.2 User Display Text

Applicable to SIP mode only.

It defines the text to be shown on the display in idle mode. If nothing is entered in this text field, the
endpoint ID is displayed.

1. Select Device → Settings.

2. In the User display text field, enter the text to be displayed.

8AL90392ENAAed02 67 /113
Configuration guide

3.10.3 User Display Number

Applicable to SIP mode only.

It defines the number to be shown on the display in idle mode. If this parameter is empty, the
Endpoint number is shown.

1. Select Device → Settings.

2. In the User display number field, enter the number to be displayed.

3.10.4 Rotate Display Text

Applicable to SIP mode only.

The handset can be configured to show the contents of the display (except the soft key bar) upside-
down at incoming calls or messages. It can also be configured in the handset menu.

1. Select Device → Settings.

2. In the Rotate display text list, select Off or On.
3.10.5 Font Style

Applicable to SIP mode only.

The display font style can be changed to bold for improved readability. It can also be configured in the
handset menu.

1. Select Device → Settings.

2. In the Font style list, select Normal or Bold.
3.10.6 Backlight Timeout

The Backlight timeout option defines the number of seconds before the backlight of the handset is
turned off in idle mode.

To set the time that passes before the backlight is turned off, perform the following steps:
1. Select Device → General.
2. In the Backlight timeout field, enter the number of seconds (1–60 s).
3.10.7 Brightness

To configure the brightness of the handset, perform the following steps:

1. Select Device → Settings.
2. In the Brightness drop-down list, select one of the following:
• Normal – Maximum backlight is used.
• Power save – Reduced backlight is used.

8AL90392ENAAed02 68 /113
Configuration guide

3.10.8 Screen Saver

This parameter is configurable only in 8168s. Black also in call is available in 8158s
too, but it is not configurable.

The handset can be configured to display some or no information when it is not in use and when it is
placed in a charger.

To configure the screen saver, perform the following steps:

1. Select Device → Settings.
2. In the Screen saver drop-down list, select one of the following:
• Information – Time and status is shown on the screen saver in SIP mode. In NOE
mode, different icons can be displayed (Message, Appointment, Notification, Keylock,
or Terminal lock).
• Black – No information is shown on the screen saver.
• Black also in call – The Black screen saver (with no information) is shown also during
phone calls.

It is recommended to use the screen saver setting Black also in call to extend battery
life.

The screen saver can also be configured in the handset menu.

3.10.9 Screen Saver Icons

Applicable to 8168s only.

Applicable to NOE mode only.

To configure which functions appear on the handset display, perform the following steps:
1. Select Device → General.
2. In the Screen saver icon 1–4 drop-down list, select the required function:
• Message
• Appointment
• Notification
• Terminal lock
• Keypad lock
• Not used

3.10.10 Idle Information Text

Applicable to 8168s only.

Applicable to NOE mode only.

To customize the text that appears on the handset screen in idle mode, perform the following steps:
1. Select Customization → Idle info.
2. In the Idle info text, row 1–4, enter the text to be shown in idle mode.

Setting this parameter prevents any system texts to be shown on that specific row.

8AL90392ENAAed02 69 /113
Configuration guide

3.11 Services

Applicable to 8168s only.

Applicable to SIP mode only.

It is possible to configure up to 10 services that can be accessed from the handset’s Services menu.

1. Select Services.
2. Select in the range of 1–10.
3. In the Service name field, enter the name of the service to be displayed in the handset’s
Services menu.
4. Under Service function, select the service to be used:
• Phone Call
• Send data (predefined data and/or prompt for the data)
• Send a message (prompt for the message text)
• Push-to-Talk

5. In the Service user data field, enter the data to be sent/dialed when using the service.

This field is not applicable for PTT.

6. In the Service prefix for user data field, enter the prefix for the service user data (if
needed).
7. In the Service index field, enter the corresponding index used for PTT. For example, if PTT
group 1 is configured (located under Push-To-Talk → 1), the service index must be set to 1.

This field is only applicable for PTT.

If the PTT is not configured, continue, with 3.12 Push-to-Talk Group Call, page 70 .

It is also possible to configure soft keys to reach services quickly, see 3.4.17 Shortcuts,
page 34 .

3.12 Push-to-Talk Group Call

Configure PTT in NOE Mode

Applicable to 8168s only.

To configure PTT parameters in NOE mode, perform the following steps:

1. Select VoIP → NOE.

2. The following NOE parameters are available:
• PTT prefix — Defines the prefix number to be called for a PTT conference.
• PTT list number — Defines the list number in the group to be used for a PTT
conference.

8AL90392ENAAed02 70 /113
Configuration guide

Configure PTT in SIP Mode

Applicable to 8168s only.

To be able to configure a PTT session, the following data is required:

• The group number of the PTT group defined in WinPDM/IMS3 DM
• The phone number to the conference bridge

For more information, see User Manual, ALE 8158s and 8168s WLAN Handsets, 8AL90391ENAA.

If Music on hold (MOH) is used in the system, it can affect an ongoing PTT group call. If
someone in the group conference answers another incoming call, MOH is played for the
whole group.

To configure a PTT group call, perform the following steps:

1. Select Push-To-Talk → X (where X represents 1–10).
2. The following parameters can be configured:
• Session name — Defines the name of the PTT session.
• Group number — Defines the group number to which the call setup for this PTT
session is sent.
• Display text — Defines the text shown on the display during the PTT session.
• PTT session signal — Defines how the PTT session is indicated.
• Conference number — Defines the call number to the conference bridge. The call
number is sent when a PTT session is initiated from or accepted by the handset.
• Answer mode — Defines which answer mode the handset has for the PTT session.
Select Manual if the user must accept the session. Select Auto to set up the session
automatically.
• Speaker mode — Defines which speaker mode the handset has for the PTT session.
Select Normal to start session with the speaker turned on. Select Loud to start the
session with the loudspeaker turned on.

3. If it is desired to have the automatic key lock on during an ongoing call, select Device →
Settings. In the Automatic key lock drop-down list, change the automatic key lock setting
to On. For more information, see 3.4.1 Automatic Key Lock, page 25 and 3.4.4 Automatic
Lock Time, page 26 .
4. A Service can be configured to access the PTT session from the handset. If not configured,
continue with 3.11 Services, page 70 .

The In call menu can be hidden for PTT calls. For more information, see 3.6.19 Hide In Call Function
for PTT Calls, page 54 .

3.13 Location

Applicable to 8168s only.

There are two types of supported locations, a basic location solution that gives an approximate
location using Access Point (AP) location and a personal security solution that gives a more accurate
location using a third-party Real-Time Location System (RTLS) solution.

The following RTLS solutions are supported:

• Cisco MSE — The handset must be configured to use this option.
• AiRISTA Flow RTLS — The handset must be configured to use this option.

8AL90392ENAAed02 71 /113
Configuration guide

3.13.1 Configure Handset for Cisco MSE or AiRISTA Flow RTLS Solution

1. Select Location → Common.

2. In the WLAN location scanning drop-down list, select On.
3. In the WLAN scanning interval field, set the time between the scanning periods.
Close scanning periods and frequent scans per period shorten the battery time.
4. In the WLAN scans per scanning period drop-down list, select how many scans should be
performed during each scanning period.
Close scanning periods and frequent scans per period shorten the battery time.
If the AiRISTA Flow RTLS solution is used, also perform the following step.
5. Select Location → AiRISTA Flow, and configure the following parameters:
• AiRISTA Flow Location Scanning — If enabled, location information is sent to the
specified AiRISTA Flow RTLS.
• IP address — Defines the IP address of the AiRISTA Flow RTLS server, to which the
handset reports locations.
• Listening port — Defines the port the AiRISTA Flow RTLS server is listening to.

8AL90392ENAAed02 72 /113
Configuration guide

4 System Deployment Planning

4.1 Site Survey Tool

It is recommended to do site surveys with the built-in tools in the handset.

The built-in tools provide a true measurement of the RF environment based upon the radio of the
handset. Wireless analyzers can be used to provide additional assistance during a site survey.

4.2 Scan the Channels

To be able to use the site survey functions in the handset, configure the site survey functions
correctly.

The default configuration for the handset is to use channels 1, 6, and 11 on the 2.4 GHz frequency
band. To perform a site survey, it is important to configure the handset to use the frequency band and
channels on which the site survey will be performed.

For instance, it is possible to scan all 2.4 GHz or 5 GHz channels by setting the frequency band
parameter accordingly and then setting parameter 2.4 GHz channels or 5 GHz channels to All,
respectively.

It is important to remember to revert back to the original settings after the site survey is finished.

The regulatory domain also affects the channels that can be used. For instance, channels 12 and 13
are only possible to scan if the handset is configured to operate in World mode.

The channel information is upgraded regularly, starting with scanning channel 1, then 6, and finally
11. In between, the handset is in sleep mode. The handset consults this information when making
roaming decisions.

For 2.4 GHz channels, it is strongly recommended to set back the handset to 1,6,11 before normal
use. For 5 GHz channels, it is strongly recommended to set back the handset to UNII-1 before normal
use.

There are two ways of scanning channels:

• Scan all channels
See 4.2.1 Scan All Channels, page 73 .
• Scan a specific channel
See 4.2.2 Scan a Specific Channel, page 73 .
4.2.1 Scan All Channels

This function gives a filtered list of the channels in the SSID found during the scan.

1. In the Admin menu of the handset, select Site survey tool → Scan all channels.
2. Select the SSID to display the associated AP.
3. Select an AP to display information on SSID, Channel, and MAC address.

4.2.2 Scan a Specific Channel

This option gives a list of all the APs found on that channel in the specified SSID.

1. In the Admin menu of the handset, select Site survey tool → Scan selected channel.
2. Enter the channel to be scanned.
3. Select an AP to display information on SSID, Channel, and MAC address.

8AL90392ENAAed02 73 /113
Configuration guide

4.3 Range Beep

The range beep function enables a beep to be played whenever the handset experiences a filtered
field strength of below the configured value (default −70 dBm) from the currently associated AP.

Sudden drops in field strength caused by the environment are delayed because the value of field
strength is filtered, for example when walking through a door into a room. Therefore it is important to
walk slowly through the site to cover all weak spots.

4.3.1 Configurable RSSI Threshold

The RSSI threshold of the handset is set to −70 dBm by default. In the site survey menu it is possible
to change the RSSI threshold. This is useful if a specific area is designed to have a coverage level
other than −70 dBm.

1. In the Admin menu of the handset, select Site survey tool → Range beep level.
2. Enter the new RSSI threshold and press OK.

4.3.2 Range Beep on a Configurable RSSI Threshold

By enabling Range beep, the handset gives a beep sound when the signal goes below the selected
threshold. To configure this parameter, perform the following steps:

1. Go to the Site Survey Tool menu using one of the followings ways:
• Select Menu → Settings → Sound & Alerts → Range beep.
• In the Admin menu, select Site survey tool → Range beep.

2. Select one of the following:

• On – Activates the range beeps.
• Off – Deactivates the range beeps.

For more information, see 2.2.3 Deploy the Handset Using the Admin Menu, page 15 .

4.4 Location Survey

The location survey function makes it possible to use Site survey mode for AiRISTA Flow that causes
location scanning to be performed at intervals of 1 s.

8AL90392ENAAed02 74 /113
Configuration guide

5 Maintenance

5.1 Maintaining the Handset

In an existing VoWiFi system, it is important to be able to replace handsets, install new handsets, and
replace faulty handsets. The recommended procedure is to use a template with basic network
settings created in the WinPDM/IMS3 DM, and then import the rest of the settings that were created
by the templates.

It is also important to be able to upgrade system parameters and security settings in the handsets.
These upgrades are preferably done in IMS3 DM, if available.

If WinPDM/IMS3 DM is used, perform one of the following:

• To install a new handset, see 2.3.2 Configure the Handset Using the Admin Menu, page 16 .
• 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, page 75 .

If only WinPDM is used, perform one of the following:

• To install a new handset, see 2.2.2 Deploy the Handset Using WinPDM, page 13 .
• To replace a broken handset, see 5.2.4 Replace the Handset using WinPDM, page 79 .

5.1.1 Configure Spare Handsets without a Number in Large Systems

In VoWiFi systems where WinPDM/IMS3 DM is used, it is recommended to configure a few spare

handsets without a number to be able to quickly replace a broken handset later on.

For more information, see _5FATI_5FFile_5FNot__3259849085 and 2.2.1.4 Apply a Template to a

Handset without a Number, page 13 .
5.1.2 Handset Software Upgrade

Read the software release notes before changing the software.

The handset software can be upgraded using WinPDM/IMS3 DM.

5.1.2.1 Upgrade Software using IMS3 DM

The handset software can be upgraded using IMS3 DM. Perform the following steps:
1. Open the Devices tab and select the handsets to be upgraded.
2. Right-click and click Upgrade software….
3. In the Available software drop-down list, select the desired software file (.bin).
If needed, import the software file to be used by clicking Import. Locate the software file (.bin or
.pkg) and click Open.
4. In the Upgrade section and Activate new software section, select when the software is
upgraded and activated on the handset, respectively.
5. Click OK. The dialog window Shutting down followed by Remotely updated is shown in the
handset display.

It is also possible to upgrade several handsets of the same device type simultaneously
using the Baseline function in the IMS3 DM.

8AL90392ENAAed02 75 /113
Configuration guide

5.1.2.2 Upgrade Software Using TFTP

The firmware of the handset can be automatically upgraded using TFTP. At startup, the handset
checks if there is any new firmware on the TFTP server. The upgrade is performed in the background
after the handset started up.

It is also possible to regularly let the handset check for new firmware.

The following five parameters can be configured in the Device → Upgrade menu of the IMS3 DM:
• New firmware activation — Determines when a handset must be restarted to activate the new
firmware.
• Firmware polling frequency — Defines how often the handset should check for new firmware (in
addition to checking it at startup).
• Firmware polling time — Defines at what time of day the polling should be performed.
• Firmware polling time delta — It is possible to add a random delta time when to perform the
upgrade. This can be used to spread the network load of distributing the firmware if a large
number of headsets is updated at the same time.
• TFTP block size — It is possible to set a higher block size that can generate faster downloads,
but the network settings and TFTP server must support the block size.

OXO supports maximum 1428.

Higher block size increases the risk of retransmission and results in bigger blocks to
retransmit.

At block size 512, the downloaded file size is limited to 32MB and the firmware might
be larger.
• Firmware TFTP IP address — Specifies the TFTP server address. If the address is 0.0.0.0
(default), in NOE mode the same address is used as for getting the PBX configuration file, in SIP
mode no firmware upgrade is performed. If the address is 255.255.255.255 in both SIP and NOE
modes, no firmware upgrade is performed.
5.1.3 Perform a Factory Reset

The factory reset of a handset can be performed using WinPDM/IMS3 DM or the handset. A factory
reset restores all configuration settings to their default values. For example, PBX subscriptions,
contacts, certificate, and so on are removed. The software is left intact.

To perform a factory reset using WinPDM/IMS3 DM, perform the following steps:
1. In the Devices tab, mark the handset to be factory reset. Note that the handset must be
online.
2. In the Device menu, select Factory reset. Alternatively, right-click the handset and select
Factory reset.
3. In the Reset devices window that appears, click Yes. The handset restarts.

To perform a factory reset using the handset, perform the following steps:
1. In the handset menu, select Settings.
2. Enter the Admin access code to access the Admin menu.
3. Select Factory Reset.
4. In the Reset portable? window that appears, click Yes. The handset restarts.

8AL90392ENAAed02 76 /113
Configuration guide

5.2 Handset Replacement

It is possible to replace an 8118 or 8128 with an 8158s or 8168s, or a broken handset with a spare
handset. Handsets registered in WinPDM/IMS3 DM are associated with a device type, device ID, and
extension. During the replacement procedure, the broken/old handset’s device type and extension are
associated with the spare handset’s device ID.

If the spare handset has been previously used, perform a factory reset. For more
information, see 5.1.3 Perform a Factory Reset, page 76 .

Handsets can be replaced in the following ways:

• Using the WinPDM/IMS3 DM with the network template already applied to the spare handset(s) to
log in later. For more information, see 5.2.2 Replace the Handset using IMS3 DM, page 77 .
• Using both WinPDM and the IMS3 DM with the network template not yet applied to the spare
handset(s) to log in later. For more information, see 5.2.3 Replace the Handset using WinPDM
and IMS3 DM, page 78 .
• Using only WinPDM. For more information, see 5.2.4 Replace the Handset using WinPDM, page
79 .

The following data is replaced during a replacement:

• User parameters

The following data is not replaced during a replacement:

• Certificates

5.2.1 Parameter Migration

The parameter migration feature allows templates and numbers of a certain handset variant to be
applied to any compatible handset. Every 8118, 8128, 8158s, and 8168s handset variant is
compatible with each other, which means that it is possible to replace an 8118 or 8128 with an 8158s
or 8168s.

The same template can be used for the 8158s and 8168s variants. 8168s-specific parameters are
ignored by the 8158s.

It is not guaranteed that parameter migration results in the optimal configuration of the
destination handset. For example, parameters related to features not present in the
source handset are left at their default values in the destination handset. That is why, it
is recommended to check the configuration of the destination handset after parameter
migration and make sure that the configuration is correct.
5.2.2 Replace the Handset using IMS3 DM
1. In both handsets, go to the Admin menu and select Device info → Hardware to check that
the new handset is of the correct variant. For example, if you need messaging functionality,
make sure that the new handset is an 8128 or an 8168s.
2. If the broken/old handset is online in the IMS3 DM, switch off the handset to make it offline.
3. Take a spare handset prepared with the network settings (including the IP address to the
IMS3).
4. The handset tries to log in to the IMS3 DM. Enter the broken/old handset's number in the
login screen on the new handset and press Login.
The spare handset is automatically updated from the IMS3 DM and might be restarted depending
on the changed settings. The last stored settings for the broken/old handset in the IMS3 DM are
transferred to the spare handset.

8AL90392ENAAed02 77 /113
Configuration guide

5.2.3 Replace the Handset using WinPDM and IMS3 DM

If the spare handset to be used must be factory reset or no network template has been applied, the
network template needs to be applied to the spare handset in WinPDM. When the network template is
added, the handset can log in to the IMS3 DM.

1. In both handsets, go to the Admin menu and select Device info → Hardware to check that
the new handset is of the correct variant. For example, if you need messaging functionality,
make sure that the new handset is an 8128 or an 8168s.
2. Make sure that the broken/old handset is saved (indicated by a ) in the Saved column of
the IMS3 DM. If not, right-click the broken/old handset in the Numbers tab and select Save.
3. Switch off the broken/old handset. The handset appears as offline in the IMS3 DM.
If the spare handset is not prepared with the basic network settings, also perform step Item , page
78 – step Item , page 78 .
4. Open WinPDM.
5. Place the spare handset in the DP1 Desktop Programmer cradle.
6. Run the template with the basic network settings as follows (see 2.2.1.2 Create a Template
in WinPDM/IMS3 DM, page 12 ):
• Network settings in Network → General:

Under the respective network (Network A, Network B, Network C, or Network D), set the
required parameters, for example, system settings for WLAN, such as SSID, Security mode, and
any certificates for 802.1X. If using a security mode that requires certificates, also use an NTP
server to assure the correct time in the handset, as certificates are only valid within a certain time.
• VoIP settings in the VoIP menu:

Configure, for example, VoIP information, SIP proxy ID and address.

• Syslog settings in Device → Log:

To be able to set the Syslog server IP address, the parameter Syslog must be enabled by
selecting On.
• Unite settings in Device → Unite:

Enter the IP address and password (if any) to the IMS3.

7. Remove the handset from the DP1 Desktop Programmer cradle. The handset restarts,
depending on the parameter changes.
8. Enter the broken/old handset’s number and leave the password field blank. Press Login.
The spare handset is automatically updated from the IMS3 DM and might be restarted depending
on the changed settings. The last stored settings for the broken/old handset in the IMS3 DM are
transferred to the spare handset.

8AL90392ENAAed02 78 /113
Configuration guide

5.2.4 Replace the Handset using WinPDM

1. In both handsets, go to the Admin menu and select Device info → Hardware to check that
the new handset is of the correct variant. For example, if you need messaging functionality,
make sure that the new handset is an 8128 or an 8168s.
2. Place the broken/old handset in the DP1 Desktop Programmer cradle.
3. Open the WinPDM.
4. Make sure that the broken/old handset is saved in the WinPDM (indicated by a ) in the
Saved column. If not, right-click the broken/old handset in the Numbers tab and select
Save.
5. Place the spare handset in the DP1 Desktop Programmer cradle.
6. A Found Device Wizard window appears. Select Associate with Number and click Next >.
7. In the list, select the broken/old handset to be replaced with the spare handset and click OK.

5.3 Change the Number of a Handset

It is possible to change the number of a handset, but keep all other settings in the handset.

1. Open WinPDM/IMS3 DM.

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.

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 WinPDM/IMS3 DM.

6. Click OK.
The new number is synchronized with the handset when it is connected to WinPDM/IMS3 DM.

5.4 Update Parameters Using WinPDM/IMS3 DM

The parameter update in WinPDM/IMS3 DM starts when the handset is idle and does not interrupt an
ongoing call.

Select only the parameters that are changed, if all parameters are selected, the system
performance decreases.

1. Open WinPDM/IMS3 DM.

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 IMS3 DM and can be restarted depending on
which parameters are changed.

Templates can be applied for several handsets under the Templates tab . Parameters
or templates can be set on individual handsets under the Numbers tab.

8AL90392ENAAed02 79 /113
Configuration guide

5.5 Perform a Security Upgrade Using IMS3 DM

Important

The synchronization of new settings to the handset settings cannot be performed

if the settings in the AP is changed before the settings in the handset.
Change settings in the handset before change settings in the AP.

It is recommended to 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.

To change the WLAN password/authentication, perform the following steps:

1. Open the IMS3 DM.
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, and
so on.
3. Apply the new template to the handsets.
The handsets are automatically updated from IMS3 DM and restarted.

During the update and restart, 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.

5.6 Upgrade the Template

The upgrade procedure of the templates definition version is described in the Installation and
Operation Manual, Portable Device Manager for Windows (WinPDM), 8AL90832ENAB.

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, Portable Device
Manager for Windows (WinPDM), 8AL90832ENAB.

5.8 Logging
5.8.1 Syslog

Enables logging of system events to a syslog server.

1. Select Device → Log.

2. In the Syslog drop-down list, select On to enable logging.
5.8.2 PCAP Capturing

If enabled, the selected data is sent as PCAP logs to the indicated output.

PCAP to file

PCAP logging is started by performing the following steps:

1. Select Device → Log.
2. In the PCAP Capturing drop-down list, select PCAP to file.

8AL90392ENAAed02 80 /113
Configuration guide

When the necessary logs have been collected, stop PCAP logging by preforming the following steps:

1. Select Device → Log.

2. In the PCAP Capturing drop-down list, select Off.

The PCAP files are not encrypted and can be extracted with USB or SFTP, and can be viewed using,
for example, Wireshark. To reduce the size of the generated files, RTP packets are not included.

Remote PCAP

Configure a PC that receives the logs (for example with Wireshark) and start PCAP logging by
performing the following steps:
1. Select Device → Log.
2. In the PCAP Capturing drop-down list, select RPCAP.

When the necessary logs have been collected, stop PCAP logging by performing the following steps:
1. Select Device → Log.
2. In the PCAP Capturing drop-down list, select Off.

5.8.3 Save Logs

The handset continuously generates encrypted logs that can be sent for investigation to Ascom
support in case any issue occurs. The following procedure explains how to collect these logs.

Logs are normally kept in volatile memory for a short period before they are deleted.

When this function is enabled, all logs that are collected for the defined period of time are also saved
to persistent storage.

Logs already stored in volatile memory when the function is enabled are also written to persistent
storage. This means that the function Save once now can be used to store logs of a problem that has
occurred a short while ago.

If the persistent storage becomes full, the oldest logs are overwritten by newer ones.

Use SFTP or USB transfer to retrieve the saved logs and send them to Ascom support.

Depending on the nature of the issue, it may be required to change the default log levels
as described in 5.8.6 Trace Configuration, page 82 . This controls which logs are
generated and must be set before the problem occurs.

Save Logs after a Problem Has Occurred

Right after a problem has occurred, it is possible to save the logs that show the problem even if Save
logs was not previously enabled.
1. Select Device → Log.
2. In the Save logs drop-down list, select Save once now.

Continuously Save Logs from Memory to Flash

To continuously save logs while trying to reproduce the problem, use one of the time-limited variants:
1. Select Device → Log.
2. In the Save logs drop-down list, select Save for X time.

8AL90392ENAAed02 81 /113
Configuration guide

5.8.4 Enable Sending Logs over SFTP

Continuously transferring logs over SFTP makes it possible to have logging enabled for a long period
of time without the risk of running out of storage space on the handset. There is a delay before a file is
transferred from the handset.

To enable sending saved logs to the remote server over SFTP, perform the following steps:
1. Select Device → Log.
2. In the Enable Sending Logs over SFTP drop-down list, select On.

5.8.5 SFTP Server Settings

1. Select Device → Log.
2. The following SFTP parameters can be configured:
• SFTP server IP address — Defines the IP address of the remote server, which the
handset sends logs to over SFTP.
• SFTP server authentication identity — The name is used when logs is about to be
sent to a remote server using SFTP.
• SFTP remote server authentication password — The password is used when the
SFTP remote server requires a password.

5.8.6 Trace Configuration

In normal operation, all extended trace levels should be set to Normal since excessive logging can
affect handset performance. When logs are enabled, it is indicated by the text Trace active on the idle
screen.
1. Select Device → Log.
2. The trace level can be set on the following parameters:
• Set WLAN Trace
• Set NOE Trace
• Set Configuration Trace Level
• Set GUI Trace Level
• Set GLI Trace
• Set Unite Trace
• Set VoIP Trace
• Set System Trace
• Set SAS Trace
• Set Bluetooth Trace

3. Select one of the following logging levels:

• Normal
• Verbose
• Extreme

These settings only affect the encrypted internal handset logs, not the remote syslog functionality.

Restore the handset to Normal logging after logs are captured, since extra logging can
affect handset performance.

8AL90392ENAAed02 82 /113
Configuration guide

Extended logging for specific cases

• Issues with telephony, select Verbose in the Set NOE Trace drop-down list. (Applicable to NOE
mode only.)
• Issues with network, select Verbose in the Set WLAN Trace drop-down list and PCAP to file in
PCAP capturing.
• Issues with firmware upgrade, select Verbose in the Set Unite Trace drop-down list.

5.8.7 Low Level WLAN debug

This parameter can be used to enable even more verbose WLAN debug information. It must be
enabled only when requested by a support contact.

1. Select Device → Log.

2. In the Low Level WLAN debug field, enter the required string.

5.8.8 SNMP

Simple Network Management Protocol (SNMP) with version 1.0 is supported using the standard port
for SNMP: UDP port 161.

There is no server functionality, so the handset status cannot be requested.

To enable SNMP, perform the following steps:

1. Select Device → Log.
2. In the SNMP drop-down list, select On.
3. The standard SNMP community name public, can be changed to a specific name to
enhance the security of the device. Enter the new name in the SNMP community name
field.

8AL90392ENAAed02 83 /113
Configuration guide

6 Troubleshooting

This section offers possible solutions for common operational errors. In case you need further
assistance, contact Ascom support.

If other users experience similar issues, there may be a system error.

6.1 Fault Symptoms

Fault Probable cause Action or comment

It is not possible A handset restriction Change the parameter Prevent silent in

to mute the prevents the user to Audio → General.
handset by long- silence the handset.
pressing the
Sound off
key/Mute button.

It is not possible
to set the ring
volume to Silent.

Connected call IP addressing fault, or

but no sound or muted or bad 1. Make a note of the IP address of
one way sound speaker/microphone the handset. Turn the handset off
and ping the IP address. If
something is found, the problem
is an IP address conflict.
2. Check if the handsets are muted.
3. Use a headset to eliminate bad
speakers/microphone.

Voice quality is Increased traffic load or

bad. interference. 1. Check if QoS is working in both
directions. Voice traffic should be
prioritized on both the LAN and
the WLAN.
2. Connect to other phones (wired,
analogue or external) to define if it
is the other end that may cause
bad quality.
3. Do a site survey and check for
areas with too low or too high
coverage and other interfering
802.11 systems.
4. Do a network performance test to
ensure the wired LAN/backbone
has adequate capacity.
5. Use a spectrum analyzer and look
for non–802.11 interference.

8AL90392ENAAed02 84 /113
Configuration guide

Fault Probable cause Action or comment

Battery life is DTIM might not be set

short. correctly. 1. Check the Beacon interval and
U-APSD is not used. DTIM settings in the AP.
Cisco MSE or AiRISTA 2. Verify the coverage, since low
Flow location client
signal strength will make the
settings need to be
changed. handset to constantly search for
other APs and thereby consuming
more power.
3. Use a sniffer and check the
amount of broadcast traffic that is
transmitted on the WLAN.
4. Check if correct models of the
chargers are used.
5. Verify with another battery.
6. If using Cisco MSE or AiRISTA
Flow location client, change the
settings.

The handset has There might be a bug in The handset stores two software versions,
operational the handset software. which makes it possible to revert back to
issues. the earlier software. Restore the earlier
version of the software by performing the
following steps:

1. Switch off the handset.

2. Press and hold keys 7 and 8, and
press On/Off at the same time.
The handset loads the earlier
software and keeps it until the
handset is restarted.
After a handset has started up correctly,
using this procedure is not possible for
security reasons.

8AL90392ENAAed02 85 /113
Configuration guide

6.2 Display Information

The following table contains errors that are shown on the handset display.

Table 4 Error Messages, Probable Cause, and Recommended Action

Display message Probable cause Action or comment

No access The handset has found Acknowledge the dialog window (if
and associated to the enabled) or press the mute button (the
WLAN (a wireless later keeps the dialog window visible).
network with the The No access warning can also be set to
configured SSID and indicate repeatedly, or only once. See
Applicable to SIP mode only. correct security 3.4.15 No Network and No Access
settings), but cannot Warning, page 32 .
connect to the SIP proxy
Displayed in idle mode or the IMS3.
and indicated by 1. Check if the handset is connected
simultaneous vibration to the correct SSID by entering
(if enabled), beep signal, the WLAN info screen. (An
and a dialog window (if unconfigured handset might
enabled by the system connect to an open or staging
administrator). network instead of the required
one.)
If the handset is not connected to the
correct SSID, configure the WLAN
parameters in the handset.
2. Check if the handset has the
correct network settings, for
example, IP address (either static
or received by the DHCP) by
entering the Network info screen.
If not, correct the handset network
parameters and/or the DHCP
server configuration.
3. Check if it is possible to ping the
handset, IMS3, and SIP proxy
from another PC.
4. Check the VoIP settings in the
handset and SIP proxy. For a
Messenger and Protector
handset, also check the Unite
settings in the handset and IMS3.
5. Restart the handset.

Connecting The handset has found

and associated to the 1. Check if the handset is connected
WLAN (a wireless to the correct SSID by entering

8AL90392ENAAed02 86 /113
Configuration guide

Display message Probable cause Action or comment

network with the the WLAN info screen. (An

configured SSID and unconfigured handset might
correct security connect to an open or staging
Applicable to NOE mode settings), but cannot network instead of the required
only. connect to the NOE one.)
server. If the handset is not connected to the
correct SSID, configure the WLAN
parameters in the handset.
2. Check if the handset has the
correct network settings, for
example, IP address (either static
or received by the DHCP) by
entering the Network info screen.
If not, correct the handset network
parameters and/or the DHCP
server configuration.
3. Check if it is possible to ping the
handset and NOE server from
another PC.
4. Restart the handset.

8AL90392ENAAed02 87 /113
Configuration guide

Display message Probable cause Action or comment

No network The handset has lost Acknowledge the dialog window (if
Displayed in idle mode and WLAN connection. enabled) or press the mute button (the
indicated with a short beep latter keeps the dialog window visible).
repeated every minute for
30 minutes.
It is also indicated by
simultaneous vibration When leaving a bad state for another bad
(if enabled) and a dialog state, the dialog window reopens, and the
window (if enabled by beep sounds again (if enabled).
the system
administrator).

No network (continued) The handset is out of The beeps can be stopped with the mute
coverage, or faulty button. Then go into range.
handset.
The handset cannot find
the wireless When re-entering the coverage area it
infrastructure with can take a couple of minutes before the
settings matching those handset automatically has registered into the
configured in the system.
handset. 1. Check the SSID. The SSID
configured in the handset must be
identical to the SSID configured in
the system infrastructure.
2. Check the security settings. The
security settings, that is,
authentication and encryption
must match the settings in the
system infrastructure.
3. Check for 802.11d multi
regulatory domain settings. The
handset must be able to detect in
which country it is located to use
the correct channel and transmit
power settings.
4. Check which channels are used.
By default, the handset uses
channels 1, 6, and 11 in the 2.4
GHz range and UNII-1 in the 5
GHz range. If the infrastructure is
configured to use any other
channel, change it to use only 1,
6, and 11 or UNII-1 as these are
the recommended settings.
5. Check that the correct Network
(A, B, C or D) setting is selected.

8AL90392ENAAed02 88 /113
Configuration guide

Display message Probable cause Action or comment

Voice only The handset is

configured to use both 1. Check the IMS3 address. Try to
SIP proxy and the IMS3, ping the IMS3 from another PC.
but has lost contact with 2. Remove the handset from the
the IMS3. DP1 Desktop Programmer. When
Applicable to SIP mode only. connected to the WinPDM
through USB on the DP1 Desktop
Programmer, the handset cannot
connect to the IMS3 and may
show Voice only.
3. If messaging is not used in the
system, verify that the IMS3
address is configured to 0.0.0.0.

Messaging only The handset is

configured to use both a 1. Check the SIP proxy address. Try
SIP proxy and the IMS3 to ping the SIP proxy from
but has lost contact with another wireless client.
the SIP proxy. 2. Try to send a message. The idle
Applicable to SIP mode only. connection check interval to the
IMS3 is much longer than to the
SIP proxy. Sometimes when all
network connection is lost, the
handset shows Messaging only
for quite some time, because it
discovers it has lost connection to
the SIP proxy much faster than it
discovers the loss of connection
to the IMS3. In this case the
handset will eventually change to
No access.
3. If the handset is supposed to use
SIP proxy discovery, verify that
the configured SIP proxy IP
address is 0.0.0.0.
4. Check the Endpoint number and
the Endpoint ID. If both are
configured, they must match with
the Endpoint ID and Endpoint
number registered in the IP PBX.
Clear the Endpoint ID.

8AL90392ENAAed02 89 /113
Configuration guide

Display message Probable cause Action or comment

SERVICE NEEDED Faulty handset.

An additional message is 1. Select the Reboot option on the
also displayed describing left soft key.
the cause of the error. 2.
3. If the problem persists, try one of
the following:
• Power off the handset using the
Off soft key in the middle and send
This message is only shown
the handset for service.
in English.
• Perform a factory reset by
selecting theFactory soft key on the
right.

Enter PIN code Phone lock is activated. Enter the required PIN code. If the PIN
code has been lost, enter a new PIN
code or do a factory reset using
WinPDM/IMS3 DM.

Battery low, charge now The battery level is low. Charge the handset, or replace or
charge the battery.

7 Related Documents
8158s/8168s WLAN Handset Data Sheet
8158s/8168s WLAN Handset User Manual, 8AL90391ENAA
Installation and Operation Manual, Portable Device Manager for Windows (WinPDM),8AL90832ENAB

8AL90392ENAAed02 90 /113
Configuration guide

Appendix A Templates

Templates enable the configuration of all parameters of a handset from sound volume to keypad
shortcuts.

Your supplier can provide example templates for different PBX/Call Managers. The handset has full
functionality towards the PBX/Call Manager even without a template. However, by using a template,
the handset is customized for that PBX/Call Manager with menu options for functions specific to
PBX/Call Manager.

A.1 Save Handset Configuration as a Template

It is possible to save the settings of a handset as a template. The template will only contain
configuration data, it does not include contacts, certificates, and other personal data.

This template can be used as a backup if you want to restore the configuration of a handset at a later
stage or as a template that can be applied to a number of handsets.

To save the handset configuration as a template, perform the following steps:

1. Open the WinPDM/IMS3 DM.
2. In the Numbers tab, right-click on the required handset.
3. Select Use as template… and enter a descriptive name for it.
4. In the Edit template window, all handset parameters are selected by default. If one or more
parameters are not required, clear the check box next to the parameter.

Some parameters are user-specific, and if this type of template needs to be applied 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 in
Device → Settings.
• Phone lock PIN code — The security code used to unlock the keypad. The parameter
is located in Device → Settings → Locks.
• Endpoint ID — The identity/name of the user registered in the PBX. The parameter is
located in VoIP → General.
• Admin access code — The password used to enter the Admin menu of the handset.
The parameter is located in Device → General.

5. Click OK.

A.2 Manage Templates using WinPDM and IMS3 DM

When creating a template in both WinPDM and the IMS3 DM, the templates must be identical to avoid
that the parameters override each other when synchronizing the handset.

It is possible to export templates from one device manager and import them to the other. For more
information, see Export a Template, , A.2.1 Import a Parameter File, page 92 , and A.2.2 Import a
Template, page 92 .

8AL90392ENAAed02 91 /113
Configuration guide

A.2.1 Import a Parameter File

If the parameter file (*.def) is not already included, it needs to be added to WinPDM/IMS3 DM before
importing the template.

To import the parameter file, perform the following steps:

1. Open WinPDM/IMS3 DM.
2. Select File → File management.
3. On the Parameter definition tab, click Add. The Import files window is opened.
4. Locate the parameter file (*.def), or the package file (*.pkg) where the parameter file is
included. For more information, ask the supplier.
5. Click Open to import the file.
A.2.2 Import a Template

1. Open WinPDM/IMS3 DM.

2. Select File → Import → Templates…. The Import templates window is opened.
3. Locate the template to be imported.
4. Click Open to import the template.

8AL90392ENAAed02 92 /113
Configuration guide

Appendix B Configure Custom Sounds

Applicable to 8168s only.

Applicable to SIP mode only.

Before configuring custom sounds, it is recommended to have a basic knowledge on notes.

The Melody in a custom sound is represented by a text string consisting of several elements. See
below.

Table 5 Elements, Melody Strings, and Parameters for Melodies

Element Sub element Values

Note > Octave-prefix *0 (A=55 Hz)

*1 (A=110 Hz)
*2
*3
*4 (default)
*5
*6
*7
*8 (A=14080 Hz)
If no octave prefix is added, the
prefix *4 will be used.

Basic notes c
d
e
f
g
a
b

Ess notes (flat &d

notes) &e
&g
&a
&b

Iss notes (sharp #c

notes) #d
#f
#g
#a

8AL90392ENAAed02 93 /113
Configuration guide

Element Sub element Values

Duration 0 (Full-note)
1 (1/2-note)
2 (1/4-note)
3 (1/8-note)
4 (1/16-note)
5 (1/32-note)

Silence > Rest r

Duration 1 to 5 (1 = long pause, 5= short

pause)

Duration specifier . (Dotted note)

: (Double dotted note)
; (2/3 length)

Vibration N/A Vibeon

Vibeoff

Repeat N/A @0 (repeat forever)

@<number of repetitions>, for
example: “@2” repeats the melody
string 2 times.

Figure 9. Example of a Melody String, page 94 and Table 6 Explanation of the Melody String
Example, page 94 illustrates how to program a melody.

Figure 9. Example of a Melody String

Table 6 Explanation of the Melody String Example

1 Octave-prefix

2 Vibration is turned on. The handset vibrates

continuously.

3 Basic note with 1/8 duration

4 Iss note with 1/8 duration

8AL90392ENAAed02 94 /113
Configuration guide

5 Vibration is turned off

6 Short pause

7 The melody within brackets is repeated 3

times before the handset plays the rest of
the melody.

8 Long pause

Customize the Default Handset Beeps

If it is required to create a custom sound out of any of the default handset beeps (Beep 1–7 and
Enhanced beeps 1–7), the default definition of each beep can be used as a starting point for further
customizing the sound.

The default definitions are described below.

Table 7 Definitions of Beeps

Beeps Definition (default)

Custom sound 1: 1 beep *5b4r4

Custom sound 2: 2 beeps (*5b4r4@2)

Custom sound 3: 3 beeps (*5b4r4@3)

Custom sound 4: 3 tone chime (*5b4r4@4)

Custom sound 5: 10 beeps (*5b4r4@5)

Custom sound 6: Alarm sweep (*5b4r4@10)

Custom sound 7: Alarm siren (*6e4*6a4*6e4*6a4r4@10)

Custom sound 8 Not predefined

Custom sound 9 Not predefined

Custom sound 10 Not predefined

8AL90392ENAAed02 95 /113
Configuration guide

Table 8 Definitions of Enhanced Beeps

Enhanced beeps Definition (default)

Enhanced beep 1 *6e2r2r1

Enhanced beep 2 *6e3r3e3r3r1

Enhanced beep 3 *6e4r4e4r4e4r4r1

Enhanced beep 4 *6c2r5:d2r5:e2r5r1

Enhanced beep 5 *6e4r4e4r4e4r3.e4r4e4r2e4r4e4r4e4r3.e4r

4e4r4r1

Enhanced beep 6 Beat 500,

(*5#f3g3#g3a3#a3b3*6c3#c3d3#d3e3r3@9
)

Enhanced beep 7 *6(c4e4@52)

8AL90392ENAAed02 96 /113
Configuration guide

Appendix C Easy Deployment

Easy deployment is done using a (staging) WLAN with a predefined SSID and security profile and a
IMS3.

C.1 Prerequisites
• The VoWiFi network needs at least one AP that allows access to the IMS3.
The following default configuration is used, which cannot be changed:

SSID AWS-INIT

Security mode WPA/WPA2-PSK

WPA/WPA2 AWS-INIT
passphrase

• In the handset, all other network parameters must be at their default settings. See, for example,
the following:
DHCP mode On

802.11 protocol 2.4 GHz or 5 GHz

2.4 GHz channels 1, 6, 11

5 GHz channels UNII-1

World mode regulatory World mode (802.11d)

domain

• If it is used in the IMS3, the password is needed to log in.

• The IMS3 port must be open and not blocked.
• No SSID for any of the networks A-D is configured in the handset.
• The DHCP offer for the AWS-INIT network must include an IP address of an NTP server to
provide the handset with the correct system time (needed for the certificate validations).

The number to be used by a handset is entered using the handset’s keypad, after a
successful first access to the IMS3.

Easy Deployment consists of the following three phases:

1. WLAN discovery
For more information, see C.2 WLAN Discovery, page 98 .
2. IMS3 discovery
For more information, see C.3 IMS3 Discovery, page 99 .
3. Parameter download
For more information, see C.4 Parameter Download, page 100 .

8AL90392ENAAed02 97 /113
Configuration guide

Figure 10. Easy Deployment

C.2 WLAN Discovery

The WLAN discovery starts when the new handset starts up. An already configured handset uses an
entry stored in Network A, B, C, or D, and tries to associate with a WLAN that uses the SSID that
once was configured in the Network A–D.

If there is no WLAN network (SSID) configured in the handset, the handset tries to associate with a
predefined default WLAN with SSID AWS-INIT, alternately on the 2.4 GHz frequency band and on the
5 GHz frequency band. See (1) in Figure Easy Deployment, page 98 .

If the AWS-INIT is not connected on any frequency band within some seconds, the handset tries to
connect to an open network. If it also fails, the alternatives are tried again, until succeeded.
Caution

Due to security reasons, it is not recommended to use an open network for

staging.
The staging network (AWS-INIT) should be set up to only allow traffic to/from the IMS3
DM, and services for Easy Deployment (like DHCP, NTP, ASDP). It prevents
unauthorized access to the network.

During this connection, a dialog window No network is displayed in the handset.

The WLAN discovery process stops if any SSID for Network A–D is manually filled in,
either by using the handset’s Admin menu or WinPDM/IMS3 DM.

8AL90392ENAAed02 98 /113
Configuration guide

The SSID can be accessed from the handset’s Admin menu in Device info → WLAN info. The SSID
(channel): field shows the SSID (network name). For more information, see 2.2.3 Deploy the Handset
Using the Admin Menu, page 15 .

If the wireless network connection bars (up in the left of the handset display) come and
go alternately, the pre-shared key (PSK) on the AP is probably wrongly configured, and
the handset cannot connect to the AP. After a timeout, No network is shown on the
handset display.

C.3 IMS3 Discovery

Once the handset has a WLAN connection, the second step is to automatically get the IP address to
the IMS3, which runs the IMS3 DM, see (2) in Figure Easy Deployment, page 98 .

There are two ways of getting the IP address automatically:

• Using the vendor option functionality, Option 43 of a DHCP server. For more information, see
C.3.1 Server Discovery Using the DHCP Option 43, page 99 .
• Using the Ascom Service Discovery Protocol (ASDP) implemented in the handset. For more
information, see C.3.2 Server Discovery Using the Ascom Service Discovery Protocol (ASDP),
page 100 .

In both cases, the received IP address is not saved, so this process is repeated on the next startup,
unless a IMS3 IP address is set.

C.3.1 Server Discovery Using the DHCP Option 43

A DHCP server can be configured to return a IMS3 IP address, as part of the DHCP response to the
handset, with other needed DHCP parameters. The IMS3 IP address is sent using Option 43 (Vendor-
Specific Data).

A DHCP request from a handset uses the Option 60 Vendor Class Identifier (VCI) to identify itself to
the DHCP server. The VCI string alcatel.mipt.1 (in NOE mode) or ictouch.0 (in SIP mode) is the
Object Identifier (OID) for the handset.

In this way, a DHCP server can be configured to return a IMS3 IP address only to those clients that
expect it. Option 60 also allows different clients to use different settings in Option 43, if there are
multiple clients in the network.

After the handset receives the IP address to the Unite module, it tries to log in to the IMS3 DM. The
DHCP Option 43 is ignored once the IMS3 IP address is configured in the handset.

There are many types of clients that can use this feature, for example, Cisco is using it for its LWAP
APs to find a WLAN controller to attach to.

Examples on how to configure and troubleshoot Option 43 on a Linux and Microsoft Windows server,
is found in D.1.2 Configuration Example of a Linux Server Using DHCP Option 43, page 106 and
D.1.3 Configuration Example of an MS Windows 2003 Server, page 106 , respectively.

8AL90392ENAAed02 99 /113
Configuration guide

C.3.2 Server Discovery Using the Ascom Service Discovery Protocol (ASDP)

If the DHCP response does not contain a valid IMS3 IP address, the handset tries to find a IMS3
using the Ascom Service Discovery Protocol (ASDP) instead. An ASDP discovery message is sent to
the broadcast IP address using UDP, which contains the MAC address of the handset.

A IMS3, configured to respond to ASDP discovery messages, responds with an ASDP offer as a
unicast UDP message sent to the handset.

The protocol allows each IMS3 support different client services, and can separate different types of
handsets (VoWiFi and DECT) to be serviced by different modules. If there are multiple Unite Modules
set up to support ASDP for WLAN, more than one response is received by the handset. A single
response is randomly selected, normally the modules that respond fastest.

If no response is received, a new ASDP request is retransmitted periodically, and the IP address
remains unconfigured.

Configure the IMS3 to Support WLAN Service Discovery Clients

For each module, the ASDP must be configured to support WLAN clients.

1. Log in to the module and select Configuration → Other → Advanced configuration.

2. Select WLAN System and enable Service Discovery.

C.4 Parameter Download

After successfully receiving the IMS3 IP address, the handset tries to log in to the Unite system.

The handset has, at this stage, no number stored internally, and does not know its identity in the Unite
system. When the dialog window Login: is displayed in the handset, enter the intended endpoint
number (that is, preferably the phone number of the handset) that the handset uses to log in to the
Unite system.

Once a valid endpoint number is stored in the handset, the handset tries to log in.

After a successful login, the handset is synchronized with the parameters stored in the Numbers tab
of the IMS3 DM.

It is vital that, especially the WLAN network settings, are configured correctly as the handset receives
a new set of parameters that contains the WLAN parameters for the production WLAN. If using a
WLAN security protocol that uses certificates, make sure that the certificates (server/client) are saved
to each handset number in the IMS3 DM. If the WLAN parameters are wrong, the handset cannot
associate with neither the staging nor the production WLAN again.

If the wrong number is entered when the dialog window Login: is displayed, make a
factory reset and start again. For more information, see 5.1.3 Perform a Factory Reset,
page 76 .

If there are no Number records already configured in the IMS3 DM before the handset logs in for the
first time, perform the following steps:
1. In the IMS3 DM, check and save the automatically created Numbers record by right-clicking
on the number’s entry.
2. In the created record under Device → Unite → IP address, check that the IP address for
the Unite system is correct. Then the handset can log in to the same IMS3 DM again.

The IMS3 DM’s IP address can also be checked using the Admin menu of the handset
(in Device Info → Network info → Device manager).

8AL90392ENAAed02 100 /113

Configuration guide

C.5 SCEP

Simple Certificate Enrollment Protocol (SCEP) is used for handling certificates in large VoWiFi
systems. It can be configured using DHCP.

The handset implements the client-side SCEP functionality. A third-party SCEP server is
required to get a working SCEP solution. An example of a SCEP server is Microsoft
Network Device Enrollment Service (NDES).

Configure SCEP Using WinPDM/IMS3 DM

To configure SCEP using WinPDM/IMS3 DM, perform the following steps:

1. In the Numbers tab, right-click the handset’s number and select Edit parameters.
2. Select Device → SCEP.
3. Set the following:
• Validate server certificate — Enables or disables the validation of the SCEP CA certificate.

Configure SCEP Using DHCP Option 43

A DHCP server can be configured to return a SCEP URL, a password, and CSR customization
options, as part of the DHCP response to the handset, with other needed DHCP parameters. The
SCEP configuration is sent using Option 43 (Vendor-Specific Data).

A DHCP request from a handset uses the Option 60 Vendor Class Identifier (VCI) to identify itself to
the DHCP server. The VCI string alcatel.mipt.1 or ictouch.0 is the Object Identifier (OID) for the
handset.

This way, a DHCP server can be configured to return SCEP options only to those clients that accept
it. Option 60 also allows different clients to use different settings in the Option 43 if there are multiple
clients in the network.

After the handset receives SCEP configuration, it tries to request a certificate from the supplied URL
using the supplied configuration. The configuration is stored in the handset and the DHCP Option 43
is ignored until a new valid configuration is set.

The following sub-options are used with Option 43:

• Sub–option 70: SCEP URL
For example: http://myscepserver.example.com/certsrv/mscep/mscep.dll
• Sub–option 71: Challenge password (optional)
For example: MYCHALLENGEPASSWORD
• Sub–option 72: CSR customization (optional)
For example:
K:2048;C:SE;ST:State;O:Organization;OU:Unit;CN:AABBCCDDEEFF;SAN:127.0.0.1;
CSR Custom format: <key>:<value>;

8AL90392ENAAed02 101 /113

Configuration guide

Table 9 Possible Key Value Pairs

Key Value Description

K 1024/2048 (4 characters) Key length of the generated

key pair.

C 2 characters Country name to be used in

the generated certificate. It
must be followed by the
country code listed in
https://www.ssl.com/csrs/co
untry_codes/

O String (max 16 characters) Organization name to be

used in the generated
certificate.

OU String (max 16 characters) Unit name to be used in the

generated certificate.

ST String (max 16 characters) State or province name to

be used in the generated
certificate.

CN String (max 32 characters) Common name to be used

in the generated certificate.
Different formats are
allowed. MAC address in
XXYYZZAABBCC format,
or IPv4 address in
abc.abc.abc.abc format, or
a string of printable
characters. If left empty,
the handset MAC address
is used.

SAN String (max 32 characters) Subject alternative name

extension to be used in the
generated certificate.

For examples on how to configure and troubleshoot Option 43 on a Linux and Microsoft Windows
2003/2008 server, see D.1.2 Configuration Example of a Linux Server Using DHCP Option 43, page
106 and D.1.3 Configuration Example of an MS Windows 2003 Server, page 106 , respectively.

8AL90392ENAAed02 102 /113

Configuration guide

Appendix D Complementary Information for Easy Deployment

D.1 DHCP Related

D.1.1 DHCP Vendor Options Explained

The DHCP is described in the Request for Comment (RFC) No. 2131 and 2132. (The RFC is a
publication of the Internet Engineering Task Force (IETF) and the Internet Society, which are the
principal technical development and standards-setting bodies for the Internet.)

The DHCP options described in the RFC 2132, can also, besides a DHCP server, be used by a client.

The Vendor Option 43 Field Explained According to the RFC

A DHCP server is configured with options prepared to supply clients with networking information that
is requested by the clients. The options are entered either in the IP address scope or for all scopes.

A selected set of options based on the client type can be sent to clients. This allows a DHCP server to
override the standard scope settings with other settings that are unique for a specific client type, or
transmit dedicated values that are not part of the DHCP standard. These are called vendor options
and they are sent to the client using Option 43.

Adding vendor-specific information to Option 43 requires the use of tags (named fields) in the Option
43 record. Such options are called sub-options, and they are included in the DHCP offer as type-
length-value (TLV) blocks, embedded within Option 43. The definition of the sub-option codes and
their related message format is left to the vendors.

Option 43 is used in WLAN by several vendors. Handset vendors use it to send specific values to
their family of handsets, and WLAN vendors use it to identify APs and find controllers (by distributing
IP addresses using Option 43). A dedicated tag for a specific client is only identified by a client that
asks for it and has a dedicated use for the tag. For example, the IP address to a WLAN controller that
can be probably used only by the APs.

To avoid having to send all Option 43 codes with useless tags to all clients, the use of Option 60
creates a client identity itself as a specific client type. This type is then mapped to an entry in the
DHCP server, which contains the vendor 43 options for that type.

Option 60 is normally coded as an ASCII string, but can also be binary. Option 60 is called Vendor
Class Identifier (VCI), and is defined by the manufacturer and programmed into the DHCP client of
their devices.

Table 10 Option 60 String Values, page 103 lists some examples of Option 60 string values.

Table 10 Option 60 String Values

Vendor Device String Option 43 returned

value

Aruba Aruba AP ArubaAP Loopback address of

the Aruba master
controller

Cisco Cisco AP Cisco AP c1250 IP address of the

WLAN controller

8AL90392ENAAed02 103 /113

Configuration guide

Option 43 Field Definition

The information in Option 43 is an opaque object of n octets, and the definition of this information is
vendor specific.

Table 11 Option 43

Vendor- Vendor- Vendor-

specific specific specific
information information information
Code Length element element element

43 (2b) n i1 i2 i3,…

The code for the option is 43, and its minimum length is 1. The numbers i1, i2, i3…, and so on, refer
to information bytes. The length value n refers to the amount of information bytes in the field.

The value of the length octet does not include the two octets specifying the tag and length.
Option 43 with Encapsulated Vendor-specific Information

Normally a vendor needs to use multiple parameters for the configuration of the clients. Then the
options are encoded using the Encapsulated vendor-specific extensions. This format uses the TLV
syntax (type length value) and is described in RFC 2152. When Encapsulated vendor-specific
extensions are used, the information bytes 1–n have a format described in Table 12 Information
Bytes Format when Using Encapsulated Vendor-specific Extensions, page 104 .

Table 12 Information Bytes Format when Using Encapsulated Vendor-specific Extensions

Length

Length

Length
items

items
Code

Code

Code
(tag)

Data

Data

T1 n D1 D2 … T2 n D1 D … … …
2

The different information bytes, sub-options are called tags.

The tags codes are numbered options created by the vendor, like 01, 02, 83, 243, etc.

In the table above, the code for the option and the total length are omitted.

Depending on the system that is used to configure the DHCP options, an administrator can enter
each sub-option separately, or enter all values in a single concatenated string. Since each value
contains a header, a length field, and the parameter itself, this can be difficult to enter correctly. Some
servers require the entry of values in the hexadecimal format, while others use ASCII strings.

For the handset, the Option 43 sub-fields are defined according to Table 13 Option 43 Sub-fields,
page 105 .

8AL90392ENAAed02 104 /113

Configuration guide

Table 13 Option 43 Sub-fields

(optiona
Length

Length
items

items
Code

Code

Code
(tag)

Data

Data

l)
01 7 Alcatel 2 7–15 IPv4 255
address
to IMS3
(dot-
decimal)

The code 255 is used as an optional marker of the end of the vendor field. SCEP parameters can also
be sent in option 43. For more information, see C.5 SCEP, page 101 .

When entering this information in a DHCP server, the administrator must observe that the field length
of the IP address can vary, depending on the amount of digits used. If, for example, using the address
10.30.5.7, the length is 6 numbers plus 3 dot separators in all 9 bytes. If using an IP address like
192.168.100.101, the length is 15 bytes. Some server interfaces can assist in calculating the length.

Example of Sent Data with Option 43

To deploy a handset with the IMS3 DM with IP address 10.30.4.120, data is sent as Option 43 as
follows:
Hexadecimal 01:07:41:6C:63:61:74:65:6C:02:0B:31:30:2E:33:30:2E:34:2E:31:3
2:30

Printable text \x01\x07Alcatel\x02\x1210.30.4.120

Hexadecimal 01:07:58:2D:62:72:61:6E:64:02:0B:31:30:2E:33:30:2E:34:2E:31:3
2:30

Printable text \x01\x07X-brand\x02\x1210.30.4.120

The first option in the OEM string (made bold in the table above) is used to verify that
the data received in the client is for the WLAN handset. This is called a magic number.

Search the internet for a tool that can assist in creating this string in hexadecimal
format.

Table 14 Vendor Class Identifier (VCI)

Vendor/OEM Value

Alcatel (NOE) alcatel.mipt.1

Alcatel (SIP) ictouch.0

8AL90392ENAAed02 105 /113

Configuration guide

D.1.2 Configuration Example of a Linux Server Using DHCP Option 43

The Code Example, page 106 is from a Ubuntu Linux server. Enter the information in the
/etc/ltsp/dhcpd.conf file.

Code Example

# Defining the option 43 with the proprietary sub-opcodes.

option space easy;
option easy.oem code 1 = string;
option easy.ims code 2 = string;
class “vendors” {
match option vendor-class-identifier;
vendor-option-space easy;
}
subclass “vendors” “alcatel.mipt.1” {
option easy.oem “Alcatel”;
option easy.ims “10.30.4.120”;
}
There are two options configured as code 1 and code 2, and both are defined as strings.

The server maps the string “alcatel.mipt.1” that was received from the handset using Option 60, as
defined in the subclass paragraph.

There is no need to describe the length of the fields.

D.1.3 Configuration Example of an MS Windows 2003 Server

Adding Option 60 and 43 to the standard set of DHCP, at least in a lab environment, is a simple and
fast solution, but has its drawbacks.

There can only be one set of options configured per scope, so having different vendor's equipment in
the system requires different scopes. For example, lightweight APs and handsets may not use the
same scope.

Option 43 should then contain a complete data set with all needed sub-options stored in a TLV
format. This is, in some literature, described as using the RAW format of Option 43. The TLV format is
best entered using a data type of binary.

By configuring Option 43 directly on the standard scope, any DHCP client is offered this
value, independent of the Vendor Class ID that is used by the client. Only clients who
understand the received string benefit from this value. Trying to solve this problem by
manually setting Option 60 to a specific Vendor Class ID on the standard scope has no
effect. On a Microsoft DHCP server, the Vendor class IDs are entered using a dedicated
procedure, which allows the usage of Multiple Vendor Classes. This is why Option 60 is
not listed as an option in the default standard DHCP class. Therefore, there is no need
to enter Option 60 values directly on a scope by creating a new option.

There are several documents on the internet that get this process wrong.

8AL90392ENAAed02 106 /113

Configuration guide

If set, option 43 is also offered to client computers.

Configure Option 43

This example illustrates how to set a vendor 43 option on the standard DHCP class, which is feasible
if only vendor Option 43 is needed.
1. On the DHCP server, click the scope that the handsets should use, then right-click on Scope
Options and select Configure Options.
2. On the General tab (the default Standard DHCP class), scroll down, and select 043 Vendor
Specific Info.
3. In the data entry field, there are two ways of entering the information. Click to the left in the
box to enter the string in binary, and to the right to enter the string in ASCII. It is possible to
switch between binary and ASCII.
Enter the values, as described in previous sections. Remember to get the length values in the
TLV string correct.

If the length value is unknown, enter the TLV value as follows, as everything inside
the parenthesis is auto-calculated using the Auto-len feature:

01 (“Alcatel”)02(192.168.5.1)

Click OK and save the new Option 43.

4. Check that the options are entered correctly. Note that the Vendor class is Standard, which
means that no specific class is used, and that the User class is None, which means that it is
the default user class. The handset does not send any request with a user class filled in.

Do not enter the value 2b 14 (43 20), which is the option class and the total length.
This is added by the DHCP server, when this option is presented to the client.

5. Test the configuration. If Option 43 is not working as expected, verify the behavior with a
packet-capturing tool.

Advanced Configuration of Option 60 and 43 Using a New Vendor Class

The recommended way of setting up Vendor options is to use Vendor classes instead of the Global
standard Default DHCP class. With this solution, Option 60 is not configured as an option in a scope,
but instead, a Vendor class is created.

Microsoft uses a method that allows the administrator to set up the sub-options that will be part of the
vendor options, as a complete set of sub-options, which then are concatenated to the 43 option string
by the server. Each sub-option (called a code) is defined with the sub-option numbers as described by
the vendor. In the case of the VoWiFi handset, the sub-options are 01 and 0203.

The DHCP server automatically calculates the length of each sub-option and the total
length of the whole string, and attaches the option ID of 43 to the beginning of the string.

If Option 43 is configured using code 43, the code 43 option is added to the
concatenated string. Then double headers are added (one created by you, and one
created by the system), and the string is not functioning as intended.

Instead, fill in the created sub-options with correct values. The sub-options are then automatically
concatenated to the string, which creates an Option 43 on the fly.

8AL90392ENAAed02 107 /113

Configuration guide

Define New Vendor Class to Support Multiple Types of Clients

To include the needed information for a handset, an administrator has to define a new vendor class
as follows:
1. Right-click on the DHCP server object, select Define Vendor Classes, and click Add.
2. In the New Class dialog box, enter a descriptive name for the Vendor class. For example, in
the Display name field, enter ALE 8158s and 8168s WLAN Handsets, and in the
Description field, enter Option 43 for Easy Deployment. These fields are only used for
displaying information for the administrator.
In the ID field, enter the VCI string seen in the table in D.1.1 DHCP Vendor Options Explained,
page 103 (alcatel.mipt.1). Then click OK.

Click on the right side of the field to be able to write in ASCII.

The VCI string has to exactly match with the vendor specification, since it is used in the
mapping of the information sent from the handset in Option 60 (case-sensitive).

Configure Sub-options for a Vendor Class in an MS Windows 2003 DHCP Server

The current sub-option string for the handset contains two codes (which in some documentation from
vendors are referred to as tags). To build these two codes, one has to be defined with the value of
AlcatelX-brand and one with the IP-address of the IMS3 DM.

1. Right-click on the DHCP server and select Set Predefined Options.

2. Select the vendor class created earlier (in section ? Define New Vendor Class to Support
Multiple Types of Clients, page 108 ) in Option class and click Add. The Option type
window opens.
3. Enter a descriptive name for the first sub-option in the Name: field, for example, VoWiFi
Vendor, and in the Description: field, enter, for example, Vendor Magic ID.
4. In the Data type: field, select Binary to allow entering more than one byte.
5. In the Code: field, enter 001, then click OK.

A predefined value (by selecting Edit Array) is not needed to be entered here. It
can be preferred to be set per scope instead (explained below).

6. For the second sub-option, repeat Item , page 108 –Item , page 108 .
7. Enter a descriptive name for the second sub-option in the Name: field, for example, IP
address, and copy it to the Description: field.
8. In the Data type: field, select Binary to allow entering more than one byte.
9. In the Code: field, enter 002003, then click OK.
10. Add the two sub-options to a scope and assign the values needed as follows:
Right-click on your scope, then select Scope Options → Configure Options.
11. Select the Advanced tab. In the Vendor class: field, select the new vendor class that was
created in section ? Define New Vendor Class to Support Multiple Types of Clients, page
108 (AlcatelX-brand handset). Check the two sub-options that appear (001 VoWiFi Vendor
and 002 Unite module IP address.

In the User class: field, leave the Default User Class.

8AL90392ENAAed02 108 /113

Configuration guide

12. Select the first sub-option 001 VoWiFi Vendor and enter the Vendor magic ID (Alcatel or in
Binary/Hex: 41:6C:63:61:74:65:6C). Click to the left of the box for binary and to the right for
ASCII code.

Remove 00 that is displayed by default.

A length value (in the Data: field) is not needed to be entered here (as normally
done, when entering a TLV record). Click OK.
13. Select the second sub-option 002003 Unite IP address and enter the Unite IP address in
binary/hexadecimal or ASCII. Click OK.
14. Test the configuration by factory-resetting a handset. If the configuration does not work, do a
trace with a sniffer to see why.

Install Wireshark on the DHCP server and filter on the bootp protocol to view the
packet exchange when a handset is started up.

Troubleshooting Easy Deployment in an MS 2003/2008 DHCP Server

If a predefined DCHP option has been created by mistake and it needs to be deleted, the server might
deny the operation (even if you have created the DHCP option). This is indicated by a grey Delete
button. In this case, open a command prompt and use the netsh command as follows:

netsh dhcp server \\servername delete optiondef xx

where xx is the option number.

D.1.4 Configure DHCP Options in a Cisco Device Running the Cisco IOS DHCP Server

The Cisco IOS DHCP server only allows Option 43 definitions for one device type for each DHCP
address pool, so only one device type can be supported for each DHCP address pool.

To configure DHCP Option 43 for VoWiFi handsets, perform the following steps:
1. Enter the configuration mode at the Cisco IOS command line interface (CLI).
2. Create the DHCP pool, which includes the necessary parameters, such as the default router
and the server name. This is an example DHCP scope:
ip dhcp pool <pool name>
network <ip network> <netmask>
default-router <default-router IP address>
dns-server <dns server IP address>
3. Add the Option 60 line with the following syntax:
option 60 ascii “VCI string of the handset”

Avoid raw DHCP Option 43 without the specification of a VCI. Raw DHCP Option 43
limits the DHCP server to support a single device type for vendor-specific
information for each DHCP scope. Besides, every DHCP client receives the Option
43 values in a DHCP Offer, whether the values are relevant to the device or not.

4. For the VCI string, use the value above. The quotation marks must be included.
Add the Option 43 line with the following syntax:
option 43 hex <hexadecimal string>
This hexadecimal string is assembled as a sequence of the TLV values for the Option 43 sub-
option: Type + Length + Value, as described in ? Configure Sub-options for a Vendor Class in an
MS Windows 2003 DHCP Server, page 108 .

8AL90392ENAAed02 109 /113

Configuration guide

D.2 Easy Deployment and VLAN

In a VoWiFi system, the IMS3 DM used for configuration must be positioned in the Voice VLAN, even
if it is actually a data device (since the Voice and the Unite Messaging services cannot be separated
to two different SSIDs and thus not simply mapped to different VLAN in the AP/Controller.

Although, a mapping rule can be created that uses TCP/UDP port mapping and connects the two
services to different VLANs instead of mapping SSIDs.

VLANS are not defined in the 802.11 standard. To achieve the same traffic separation, for example,
between a Data and a Voice VLAN (and maybe including even a Deployment/Management VLAN),
different SSIDs are used which are mapped to different VLAN IDs in the AP/Controller. The WLAN
system must, therefore, be set up to support multiple SSIDs.

If using the AWS-INIT SSID on a single AP, make sure that the handset can also associate with the
production SSID after it has received its full configuration from the IMS3 DM used for Easy
Deployment.

When getting the production WLAN SSID, it may be mapped to another VLAN. In this
case, the IP address is changed. The DHCP server options are also served by another
scope or eventually another DHCP server.

If using a deployment VLAN, it may be required to have two IMS3 DM or it is possible to set up a
restrictive routing between VLANs.

A direct configuration of Option 60 and Option 43 may also be used on a scope-by-scope basis if the
system allows the separation of DHCP client devices to use independent scope ranges.

D.3 Easy Deployment and Certificates

If SCEP is used, it is not necessary to perform this procedure.

If using a security model that requires certificates use an NTP server as well to assure
the correct time in the handset as certificates are only valid within a certain time.

Application Certificate

If the production network is using individual application certificates, which, for example, are required
for using EAP-TLS, first associate the certificates with the predefined number in the IMS3 DM used
for Easy Deployment, and then select the required application certificate. Perform the steps, as
described below in this section.

If there is no application certificate in the IMS3 DM used for Easy Deployment, the
handset is disconnected from the WLAN. To recover from this, first do a factory reset,
and make sure that the application certificates are associated with the correct Number.
You can also use the WinPDM to install the correct application certificate. Then try
again.

8AL90392ENAAed02 110 /113

Configuration guide

Trusted Certificate
1. Upload at least one Self-signed certificate and up to seven Intermediate certificates,
which are used to establish the trust chain of the server certificate. The commonly
understood name of these certificate types is Trusted certificate.
2. Perform the steps of association according to Item , page 111 and Item , page 111 .

For more information on certificates, see Installation and Operation Manual,

Portable Device Manager for Windows (WinPDM), 8AL90832ENAB and User
Manual, Device Manager in , 8AL90832ENAB.

3. In the Numbers tab, right-click the handset’s number and select Manage certificates. The
Manage certificates window opens.
4. In the Trust list tab and Application certificates tab, click Browse and select the
certificates to import. Click Close.
5. In the Numbers tab, right-click the handset’s number and select Edit parameters.
6. Select Network X (X represents A, B, C, or D).
7. In the Security mode drop-down list, select EAP-TLS.
8. In the EAP application certificate drop-down list, select the application certificate to be
used. Click OK.

8AL90392ENAAed02 111 /113

Configuration guide

Appendix E Interactive Messaging in Handsets

Applicable to SIP mode only.

Applicable to 8168s only.

The interactiveMessage service in the Open Access Protocol (OAP) client application is used to
send an IM to the handset. OAP is an XML-based protocol that enables the exchange of data
between external applications or systems and the IMS3.

The following list contains the XML tags for interactive messaging supported by the handsets:
• Messaging
• Subject
• Body
• Break through of silent mode
• Beep characteristics/Number of beeps
• Number of indications
• Time between indications
• Message priority used by handset
• Message ID
• Time to live in handset
• Allow later erase of message

• IM-specific
• Update existing IM
• Sticky mode
• Time between indications before option selection
• Time between indications after option selection

• Options
• Option text
• Option ID
• Assigned soft key
• Requested call number
• Display layer

• On option selection
• Number to call
• Request for call number
• Disconnect ongoing call
• Data to send when call is disconnected
• Data to send
• Erase specified option
• Erase message
• Update message time to live
• Show prompt text and request data from user
• Destination address for sent response
• Enable Option ID

8AL90392ENAAed02 112 /113

Configuration guide

• Display specified layer

• Close message
• Sticky mode
• Change message priority
• Feedback on selection

• IM response
• Data received from handset
• Data entered by user
• Device ID from handset

8AL90392ENAAed02 113 /113