Alcatel-Lucent OmniPCX Enterprise

Communication Server
OXE System: Dedicated Sets

Release 12 - April 2017

8AL91024USAG Ed. 01
Legal notice
The information presented is subject to change without notice.
ALE International assumes no responsibility for inaccuracies contained herein.
Copyright © ALE International, 2017

Disclaimer
While efforts were made to verify the completeness and accuracy of the information contained in this
documentation, this document is provided “as is”. To get more accurate content concerning Cross
Compatibilities, Product Limits, Software Policy and Feature Lists, please refer to the accurate
documents published on the Business Partner Web Site.
In the interest of continued product development, ALE International reserves the right to make
improvements to this documentation and the products it describes at any time, without notice or
obligation.

The CE mark indicates that this product conforms to the following Council Directives:
• 2014/53/EU for radio equipment
• 2014/35/EU and 2014/30/EU for non radio equipment (including wired Telecom Terminal
Equipment)
• 2014/34/EU for ATEX equipment
• 2011/65/EU (RoHS)
 Table of
contents OXE System: Dedicated Sets

Chapter 1
Reference documents

Chapter 2
IP deskphones

2.1 IP deskphones (common features).......................................................................... 15

2.1.1 Overview..................................................................................................................................................15
2.1.2 Detailed description........................................................................................................................... 15
2.1.3 Configuration procedure.................................................................................................................. 27
2.1.4 Additional configuration operations............................................................................................37
2.1.5 Configuration examples................................................................................................................... 53
2.1.6 Maintenance.......................................................................................................................................... 56
2.1.7 Relocation and Replacement of an IP-Phone.......................................................................59
2.1.8 VoIP Technical Characteristics for 8 series............................................................................ 66
2.2 8018 DeskPhone......................................................................................................................... 73
2.2.1 Ergonomics of the 8018 DeskPhone set................................................................................. 73
2.2.2 Commissioning the 8018 DeskPhone.......................................................................................75
2.3 8028/8038/8068 Premium DeskPhones................................................................ 77
2.3.1 Ergonomics of IP Premium DeskPhone sets........................................................................ 77
2.3.2 Commissioning IP Premium DeskPhone sets...................................................................... 85
2.3.3 Maintenance.......................................................................................................................................... 90
2.4 8088 Smart DeskPhone (IP deskphones)...........................................................92
2.4.1 Overview..................................................................................................................................................92
2.4.2 About this section................................................................................................................................93
2.4.3 Set description......................................................................................................................................93
2.4.4 Set configuration file description..................................................................................................93
2.4.5 Set binary file description................................................................................................................94
2.4.6 Generalities on set initialization................................................................................................... 94
2.4.7 Set configuration and deployment.............................................................................................. 96
2.4.8 Maintenance.......................................................................................................................................... 98
2.5 IP Touch 4028/4038/4068 Phone (8 series)....................................................... 98

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 3/382

 Table of
contents OXE System: Dedicated Sets

2.5.1 Ergonomics of 8/9 Series sets......................................................................................................98

2.5.2 Commissioning...................................................................................................................................107
2.5.3 Maintenance........................................................................................................................................ 112
2.5.4 Bluetooth - Basic description....................................................................................................... 116
2.5.5 Bluetooth - Installation.................................................................................................................... 117
2.6 IP Touch 4008/4018 Phone (8 series)....................................................................119
2.6.1 Ergonomics of 8/9 Series sets.................................................................................................... 119
2.6.2 Commissioning...................................................................................................................................128
2.6.3 Commissioning in NOE Mode.....................................................................................................131
2.6.4 Commissioning in SIP Stand-Alone Mode............................................................................134
2.6.5 Managing Certificates..................................................................................................................... 146
2.6.6 Maintenance........................................................................................................................................ 148

Chapter 3
TDM deskphones

3.1 8029/8039 Premium DeskPhone................................................................................152

3.1.1 Overview................................................................................................................................................152
3.1.2 Ergonomics of 8029/8039 Premium DeskPhone sets.................................................... 152
3.1.3 Commissioning 8029/8039 Premium DeskPhone sets.................................................. 157
3.1.4 Additional configuration operations..........................................................................................159
3.1.5 Maintenance........................................................................................................................................ 175
3.2 4019/4029/4039 Digital Phone (9 series)............................................................178
3.2.1 Overview................................................................................................................................................178
3.2.2 Ergonomics of 8/9 Series sets....................................................................................................178
3.2.3 Detailed description......................................................................................................................... 187
3.2.4 Configuration procedure................................................................................................................ 192
3.2.5 Additional configuration operations..........................................................................................194
3.2.6 Commissioning 4019 Digital Phone sets...............................................................................210
3.2.7 Commissioning 4029/4039 Digital Phone sets...................................................................212
3.2.8 Maintenance........................................................................................................................................ 213

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 4/382

 Table of
contents OXE System: Dedicated Sets

Chapter 4
SIP deskphones

4.1 8001/8001G DeskPhone.....................................................................................................217

4.1.1 Overview................................................................................................................................................217
4.1.2 Set description....................................................................................................................................218
4.1.3 Generalities on set initialization................................................................................................. 219
4.1.4 DHCP server configuration examples.....................................................................................221
4.1.5 Set configuration and deployment............................................................................................ 222
4.1.6 SIP survivability..................................................................................................................................230
4.2 8012 DeskPhone....................................................................................................................... 231
4.2.1 Overview................................................................................................................................................231
4.2.2 Set description....................................................................................................................................236
4.2.3 Set configuration and deployment............................................................................................ 238
4.2.4 Resetting sets to factory settings.............................................................................................. 247
4.2.5 8012 list of features..........................................................................................................................248
4.2.6 Troubleshooting................................................................................................................................. 253
4.3 8082 My IC Phone/8088 Smart DeskPhone (SIP deskphones).... 256
4.3.1 Overview................................................................................................................................................256
4.3.2 Set ergonomics.................................................................................................................................. 257
4.3.3 Generalities on set initialization................................................................................................. 260
4.3.4 Generalities on configuration parameters.............................................................................262
4.3.5 DHCP server configuration examples.....................................................................................264
4.3.6 Set configuration and deployment overview........................................................................265
4.3.7 Configuring the 8088 Smart DeskPhone as hotel set.....................................................266
4.3.8 Configuring the 8088 Smart DeskPhone as video SIP device................................... 273
4.3.9 Deploying set binaries.................................................................................................................... 295
4.3.10 Deploying a customization file.................................................................................................... 297
4.3.11 Commissioning sets.........................................................................................................................298
4.3.12 Reset to factory..................................................................................................................................299
4.3.13 Redundancy.........................................................................................................................................301
4.3.14 Compliant standards........................................................................................................................302
4.3.15 Environmental constraints............................................................................................................ 303
4.3.16 Set power supply...............................................................................................................................304
4.3.17 Protocols................................................................................................................................................305

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 5/382

 Table of
contents OXE System: Dedicated Sets

4.3.18 Bluetooth............................................................................................................................................... 306

4.3.19 Set customization..............................................................................................................................310
4.3.20 Set parameters in a hotel or business configuration....................................................... 324

Chapter 5
Additional Key Modules

5.1 Overview...........................................................................................................................................337
5.1.1 Overview................................................................................................................................................337
5.1.2 Personal home page key (AOMV)............................................................................................337
5.1.3 Additional key modules with paper labels.............................................................................338
5.1.4 Smart Display Module.....................................................................................................................338
5.1.5 Display mode...................................................................................................................................... 339
5.2 Configuration procedure..................................................................................................340
5.2.1 Overview................................................................................................................................................340
5.2.2 Configuring system options..........................................................................................................341
5.2.3 Declaring additional key modules............................................................................................. 342
5.2.4 Configuring programmable keys................................................................................................342
5.2.5 Controls and explicit errors.......................................................................................................... 344
5.3 External connections...........................................................................................................344
5.3.1 Overview................................................................................................................................................344
5.3.2 Prerequisite..........................................................................................................................................344
5.3.3 Installation.............................................................................................................................................344

Chapter 6
DECT handsets

6.1 8212/8232/8242/8262 DECT handsets.................................................................. 346

6.1.1 Overview................................................................................................................................................346
6.1.2 Key features.........................................................................................................................................347
6.1.3 Location................................................................................................................................................. 347

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 6/382

 Table of
contents OXE System: Dedicated Sets

6.1.4 Key benefits......................................................................................................................................... 348

6.1.5 Technical Specifications.................................................................................................................348
6.1.6 Regulatory compliances................................................................................................................ 351
6.1.7 Accessories ........................................................................................................................................ 354
6.2 500 DECT handset.................................................................................................................. 354
6.2.1 Hardware description...................................................................................................................... 354
6.3 Ascom 9d24 handset............................................................................................................360
6.3.1 Overview................................................................................................................................................360
6.3.2 Detailed description......................................................................................................................... 361
6.3.3 Operation.............................................................................................................................................. 365

Chapter 7
Generic GAP sets

7.1 General...............................................................................................................................................375
7.2 Operation remarks..................................................................................................................376
7.3 Compatibility................................................................................................................................ 376

Chapter 8
OT Connection for 8082

8.1 Overview...........................................................................................................................................377
8.1.1 Commissionning operations........................................................................................................ 377
8.2 Binary files..................................................................................................................................... 378
8.3 Checking the software version of the set........................................................ 378
8.4 Configuring the DHCP server...................................................................................... 378
8.5 Declaring the set on the OmniPCX Enterprise........................................... 379

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 7/382

 Table of
contents OXE System: Dedicated Sets

8.6 Starting the set in NOE mode in an OpenTouch environment.... 379

8.6.1 Resetting the phone to its out-of-the-box default settings............................................ 379
8.6.2 Dissociating set and user from the OmniVista 8770........................................................379
8.7 Starting the set in NOE mode in an OmniPCX Enterprise
environment.................................................................................................................................. 380
8.8 Switching the set back to SIP mode..................................................................... 381
8.9 Specific maintenance.......................................................................................................... 381
8.9.1 Set identification................................................................................................................................ 381
8.9.2 Firmware upgrade.............................................................................................................................381
8.9.3 Retrieving logs....................................................................................................................................382

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 8/382

 Chapter

1 Reference documents

The OmniPCX Enterprise documentation includes the documents listed in the following table:

table 1.1: OmniPCX Enterprise Documentation

Documentation title Part number

[1] System Services 8AL91000xxyy

Summary: this document provides an overview of system architecture,
topologies, as well as server duplication. It describes how to implement
synchronization and specific connections, as well as licenses, timers,
voice guides (and music-on-hold), languages and date and time.

[2] Management Tools 8AL91002xxyy

Summary: this document describes how to configure access rights to
the system by the management application, how to implement a config-
uration by domains and how to translate the strings displayed on tele-
phone sets and specific OmniPCX Enterprise applications.

[3] User Services 8AL91003xxyy

Summary: this document describes how to implement basic telephone
features such as broker call and transfer, as well as more advanced
collaboration features such as call pick-up, conferences and twin sets.
Each feature is presented in a separated chapter providing a descrip-
tion, the necessary configuration and, if need be, how to operate it.

[4] Attendant Services 8AL91004xxyy

Summary: this document describes how to implement attendant con-
soles. It also details the integrated automated attendant feature and
specific configurations for attendant consoles.

[5] Public Networks 8AL91005xxyy

Summary: this document describes the available features to configure
and implement accesses to public networks

[6] Private Networks 8AL91006xxyy

Summary: this document describes the available features to configure
and implement networks of OmniPCX Enterprises, including QSIG and
PCX synchronization.

[7] IP-PCX Networks 8AL91007xxyy

Summary: this document describes the available features to configure
and implement IP networks. It covers IP redundancy, quality supervi-
sion, SNMP, security and authentications.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 9/382

Chapter 1 Reference documents

Documentation title Part number

[8] Voice Mail 8AL91008xxyy

Summary: this document describes how to implement and configure the
native 4645 voice mail service in IMAP or VPIM. It also describes how
to centralize voice mail for several nodes and how to implement an ex-
ternal voice mail system.

[9] Mobility 8AL91009xxyy

Summary: this document describes the available features for DECT
sets and how to implement and configure every service. This document
also covers the various ways for GSM sets to rely on OmniPCX Enter-
prise services and the implementation of paging for authorized users.

[10] General Applications 8AL91010xxyy

Summary: this document describes how users can access external ap-
plications via a Presentation server. It also details how call distribution
can be precisely controlled or temporarily restricted for external calls or
within a specific group of users. The configuration to filtering of incom-
ing calls is also presented. Finally, this document covers how to share
an OmniPCX Enterprise between distinct companies and how to imple-
ment metering features, in order to monitor and control call costs.

[11] Hotel/Hospital 8AL91016xxyy

Summary: this document describes the operations and configuration of
the hospitality feature integrated to the OmniPCX Enterprise. It details
the different configurations, by room or by guest and how to connect
the system to an external hospitality application.

[13] Maintenance 8AL91011xxyy

Summary: this document details the syntax and result of the most com-
mon maintenance commands. It also details the management of inci-
dents and alarms, as well as SNMP. It covers remote maintenance fea-
tures and the operations of sets dedicated to alarms.

[14] Security 8AL91012xxyy

Summary: this document includes a detailed description on the neces-
sary measures to ensure the highest system security. Guidelines and
configuration details are provided to cover every level of this highly sen-
sitive issue.

[15] PWT 8AL91019xxyy

Summary: this document describes the implementation and configura-
tion of mobile sets relying on the PWT protocol in an OmniPCX Enter-
prise environment.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 10/382

Chapter 1 Reference documents

Documentation title Part number

[16] Crystal Hardware System Boards 8AL91020xxyy

Summary: this document provides a detailed description of the different
system boards available in the Crystal hardware package. A visual
guidance of the default and specific positions of straps, as well as con-
nections are included.

[17] Crystal Hardware Interface Boards 8AL91021xxyy

Summary: this document provides a detailed description of the different
interface boards available in the Crystal hardware package. These
boards allow the implementation of T0/S0 interfaces, DECT, analog ter-
minals, accesses to the public network, the implementation of different
OmniPCX Enterprise nodes and IP communications. A visual guidance
of the default and specific positions of straps, as well as connections
are included.

[18] Common Hardware Boards 8AL91022xxyy

Summary: this document provides a detailed description of the different
boards available in the Common hardware package. Each board is de-
scribed individually. A visual guidance of connections is included for
each board.

[19] Cables 8AL91023xxyy

Summary: this document provides a detailed description of the different
cables available for Crystal hardware interface boards. Maximum length
are indicated for each type of cables.

[20] Dedicated sets 8AL91024xxyy

Summary: this document provides a detailed description of the propriet-
ary sets and generic sets (including heavy-duty sets), available for the
OmniPCX Enterprise. These telephones sets can be TDM, IP or mo-
bile. Ergonomics, environmental constraints, power supply, initialization
and configuration are explained for each set.

[21] TA and TSC Adapters 8AL91025xxyy

Summary: this document provides a detailed description of the availa-
ble adapters for V24, CTI, S0 and analog peripheral. A visual guidance
of the default and specific positions of straps, as well as connections
are included.

[22] Complementary Equipment 8AL91026xxyy

Summary: this document describes the available connecting devices for
external devices, as well as V24 interfaces, tie line filter box and IBS
base stations for DECT roaming.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 11/382

Chapter 1 Reference documents

Documentation title Part number

[23] Common Hardware Installation Manual 8AL91027xxyy

Summary: this document details what is necessary to install a Common
hardware system. Recommendations on the best environmental situa-
tions are included along with system specificities. The installation pro-
cedure details assembling, internal connections, external connections,
power supplies and first level maintenance operations.

[24] Crystal Hardware Installation Manual 8AL91028xxyy

Summary: this document provides separate chapters for each available
Crystal hardware rack. Recommendations on the best environmental
situations are included along with system specificities and cabling dia-
grams, with visual guidance to implement connections.

[25] Appliance Server Installation Manual 8AL91029xxyy

Summary: this document provides all the necessary information to com-
mission an appliance server, with or without uninterruptible power sup-
ply. Technical specifications and software version compatibilities are
provided for each available piece of hardware.

[26] Blade Center Installation Manual 8AL91030xxyy

Summary: this document provides all the necessary information to com-
mission a blade center, replacing up to fourteen separate servers, in an
OmniPCX Enterprise network, offering maintenance and redundancy
facilities. A precise installation procedure is included. It details how to
download a system software and how to update firmware.

[27] PCX on Standard Racks Installation Manual 8AL91031xxyy

Summary: this document provides all the necessary information to com-
mission a Crystal hardware OmniPCX Enterprise on industry-standard
racks. It details wiring, power supply and fixing kit recommendations

[28] Software Installation Manual 8AL91032xxyy

Summary: this document details the partitions and directories, along
with their contents necessary for system operations. It describes the dif-
ferent procedures available to deploy the software, on site or from a re-
mote location, on a physical or virtual environment.

[29] ALEDS 8AL90508xxyy

Summary: this document describes the implementation of this deploy-
ment tool in the various compatible topologies. This documents in-
cludes requirements and procedures to install each software, among
which the OmniPCX Enterprise. Software deployments and updates are
explained for physical and virtual machines.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 12/382

Chapter 1 Reference documents

Documentation title Part number

[30] Customer Management via mgr 3EU19871xxyy

Summary: this administration manual describes how to connect, set
menus and navigate with this text interface management tools. It pro-
vides information on basic configurations, such as creating users,
speed dialing numbers, directory, telephone class of service or modify-
ing metering costs.

[31] Customer Management via 8770 8AL90615xxyy

Summary: this administration manual describes how to connect to the
OmniVista 8770 client and navigate in this GUI application. It lists the
available configurations for the OmniPCX Enterprise and provides infor-
mation on basic configurations, such as creating users, speed dialing
numbers, telephone services, alarm sets and phone book.

[32] Alcatel-Lucent 4645 - Administrator Manual 3EU19873xxyy

Summary: this administration manual describes how to configure and
implement the voice mail system embedded in the OmniPCX Enter-
prise. It also details the procedure to rely on distribution lists, how to
create mail boxes (including temporary mail boxes in hotel/hospital en-
vironments), set up an automated attendant for incoming calls, as well
as record and implement customized announcements.

[33] Internal Accounting - Administrator Manual 3EU19833xxyy

Summary: this administration manual describes how to configure and
implement the cost metering system embedded in the OmniPCX Enter-
prise. Procedures explain how to set up the different communication
types (normal, business and personal) and process the records. This
document also details how to monitor call costs from a telephone set.

[36] Alcatel-Lucent 4059 IP Attendant Console 3EU19877xxyy

Summary: this user manual describes the various features available for
attendants using a 4059 IP set. Configuration procedures are also de-
tailed.

[37] Alcatel-Lucent IP Touch 4068 Attendant Set 8AL90607xxyy

Summary: this user manual describes the various features available for
attendants using a 4068 IP set configured for this particular usage. Ba-
sic configuration procedures are also detailed.

[38] Alcatel-Lucent 4645 VMS - User Manual 3EU19583xxyy

Summary: this user manual describes the various features available for
system users wishing to make the most of this voice mail and custom-
ize their announcements.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 13/382

Chapter 1 Reference documents

Documentation title Part number

[39] Hotel - Hospital - User Manual 3EU19837xxyy

Summary: this user manual describes the various features available for
hotel/hospital staff to configure and modify and retrieve metering re-
cords for the guests on their facility. Room service management and
basic configuration procedures are also detailed.

[40] Dongle IP / Raspberry for OpenTouch Suite 8AL90617xxyy

Summary: this document covers the deployment of USB over an IP
dongle with OmniPCX Enterprise systems to support FlexLM server de-
ployments. Procedures explain how to install the dongle, obtain the
firmware and boot the system.

[41] NFC Extended OXE Mobility Administration Manual 8AL90614xxyy

Summary: this administration manual describes the implementation of
transparent call shifts from a device to the other via NFC tags. NFC tag
generation is detailed with screenshots from the application.

[42] NFC Extended OXE Mobility User Manual 8AL90613xxyy

Summary: this user manual describes the implementation of transpar-
ent call shifts from a device to the other via NFC tags. Procedures to
read NFC tags and shift calls are provided, and the necessary mobile
phone settings are detailed.

[43] OmniVista 8770 Administrator Manual 8AL90703xxyy

In the present document, cross-references are identified by the number in the first column of the above
table.
Part numbers are given in the last column, where xx corresponds to the language code of the
document, and yy to the incremented edition of the document.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 14/382

 Chapter

2 IP deskphones

2.1 IP deskphones (common features)

2.1.1 Overview
2.1.1.1 Overview
The OmniPCX Enterprise supports different types of IP deskphones:
• IP DeskPhones sets:
• 8088 Smart DeskPhone (as of R12)
• 8078s Premium DeskPhone (as of R12)
• 8068 Premium DeskPhone (as of R11.0)/8068s Premium DeskPhone (as of R12)
• 8058s Premium DeskPhone (as of R12)
• 8038 Premium DeskPhone (as of R11.0)
• 8028 Premium DeskPhone (as of R11.0)/8028s Premium DeskPhone (as of R12)
• 8018 DeskPhone (as of R11.2 MD2)
• IP Touch 40x8 phone Extended Edition sets (also called Alcatel-Lucent 8 series sets) (available as
of R8.0.1):
• Alcatel-Lucent IP Touch 4068 phone Extended Edition
• Alcatel-Lucent IP Touch 4038 phone Extended Edition
• Alcatel-Lucent IP Touch 4028 phone Extended Edition
• Alcatel-Lucent IP Touch 4018 phone Extended Edition
• Alcatel-Lucent IP Touch 4008 phone Extended Edition
The purpose of this document is to describe IP deskphone operation with the OmniPCX Enterprise,
and in particular, the initialization procedure and necessary configuration.

2.1.2 Detailed description

Note:
IP DeskPhones and Alcatel-Lucent 8 series sets are very similar in their features and capabilities. In the following
paragraphs all mentions to IP DeskPhones apply to Alcatel-Lucent 8 series sets, unless specified otherwise.

2.1.2.1 Binary Files

To operate correctly, an IP phone needs to download binary files that will be stored in its flash memory.
These binary files must comply with the OmniPCX Enterprise version and configuration. Binary files
contain a header indicating a version number. After system upgrade and at each set initialization,
version numbers are checked to determine whether an update of the files is necessary.
The software delivery of IP phones consists of:
• A bootloader file
• A code binary
• A data (or resources) binary
Two more files are likely to be downloaded on IP phones:
• A localization file
• A customization file

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 15/382

Chapter 2 IP deskphones

The content of the software package differs for 8088 Smart DeskPhone sets. For more information,
see: Set binary file description on page 94.
2.1.2.1.1 Code and Data
The code file contains boot software, downloader software and application software.
The data file contains ringing melodies, beeps, icons, fonts and images.
Code and data files must be downloaded when the versions of the files in the flash memory of the set
do not match the versions of the files on the Communication Server.
2.1.2.1.2 Localization
IP phones can display fonts for languages with non-Latin characters.
Some of these fonts are not included in the data binary file (Chinese, Japanese and Korean) and need
a specific localization file to be stored on the set. This feature does not apply to 8088 Smart
DeskPhone sets where all available fonts are included in the binary file.
Localization files are named according to the following pattern: [ISO639-2 lang id]-[model],
where:
• [ISO639-2 lang id] is a three-character string referring to the language according to the
ISO639-2 standard
• [model] is a four-character string referring to the type of set. If the localization file is dedicated to
a specific type of sets, it takes the name of the set, i.e. 8028, 8038 or 8068. If the localization file is
not dedicated to one type of set, it takes the value 80x8.
For example, localization files for Korean can be:
• kor-8068
• kor-80x8
The kor-8068 file is downloaded on 8068 Premium DeskPhone sets. The kor-80x8 file is
downloaded on 8028 Premium DeskPhone and 8038 Premium DeskPhone sets, since there is no
dedicated file for these two sets.
A localization file must be downloaded when:
• The language selected for the set requires a localization file (for example, Korean or Japanese
selected)
• A localization file for this language - and this type of set - exists on the Communication Server
• The file is not stored in the flash memory of the set, or is of a different version on the
Communication Server
The localization file upgrade can occur at global system initialization. In this case, it is done in the same
way as with other binary files.
A localization file download can also be needed due to a change of the set language.
If the change is done via configuration on the Communication Server (MAO), the set resets (whatever
the language selected). If the change is done directly on the set, the set resets only when downloading
a localization file is needed.
If a file is changed or added to the Communication Server, the update of all impacted sets can be
started manually, using the same tools as for binary files update:
• downstat i resetauto
• ippstat
The sets which reset after a localization file has been changed or added are then upgraded with the
new version of the file.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 16/382

Chapter 2 IP deskphones

Caution:
In a "Fast Init" process, binaries are not downloaded at set initialization. This implies that a set can start
without its localization file and show faulty display until it is upgraded.
2.1.2.1.3 Customization
Ringing tones and beeps can be customized on the IP phones.
The customized ringing tones and beeps are stored in a customization file, which must be downloaded
on the set.
A customization file is named according to the following pattern: cust-[melody file name]-
[model] where
• [melody file name] is the name configured in the Alcatel-Lucent 8/9 series Phone COS
parameters (see: Configuring Phone COS on page 40)
• [model] is a four-character string referring to the type of set. When the customization file is
dedicated to a specific type of sets, it takes the name of the set, i.e. 8018, 8028, 8038, or 8068. If
the customization file is not dedicated to a particular type of set, it takes the value 80x8.
For example, if "mycompany" is configured in the Alcatel-Lucent 8/9 series Phone COS parameters,
the customization file name will be cust-mycompany-80x8.
A customization file must be downloaded when:
• The set belongs to a category for which a melody file name has been configured
• A customization file exists on the Communication Server
• The customization file is not stored on the set, or is of a different version on the Communication
Server
Ringing tones and melodies cannot be customized for 8088 Smart DeskPhone sets.
Caution:
In a "Fast Init" process, binaries are not downloaded at set initialization. This implies that a set can start
with a wrong version of this file.
Note:
If the name of the file is not the same as the one on the Communication Server, the set does not use this file.

2.1.2.2 IP Phone Initialization

IP phone initialization is performed in five steps, described in the following sections:
• Step 1: Network Initialization on page 17
• Step 2: Acquisition of IP Parameters on page 17
• Step 3: lanpbx.cfg File Download on page 19
• Step 4: Software Download on page 19
• Step 5: Start File Download on page 20
2.1.2.2.1 Step 1: Network Initialization
The network initialization step consists in:
• Ethernet link initialization
• Network stack initialization
• If used on the client network, 802.1x authentication (for more information on 802.1x authentication,
refer to the document [7])
2.1.2.2.2 Step 2: Acquisition of IP Parameters
IP parameters can be assigned by static or dynamic configuration:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 17/382

Chapter 2 IP deskphones

• Static initialization: IP parameters are manually configured on the IP phone. Static initialization is
mandatory when there is no DHCP server.
• Dynamic initialization (factory-fitted default process): IP parameters are automatically sent by a
DHCP server to the IP phone.
2.1.2.2.2.1 Dynamic IP Configuration
1. The set sends an "AVA enabled" DHCPDISCOVER message to acquire a VLAN ID (refer to the
document [7])
2. If a VLAN ID is received, the IP phone sends a second "standard" DHCP request using this
acquired VLAN.
3. The DHCP server replies with:
• IP phone address
• IP subnetwork mask
• Router address
• TFTP server address or HTTP/HTTPS server address, port number and path
The DHCP server can also provide the following information to IP phone operating in SIP
standalone mode:
• Domain Name Server (DNS primary and secondary)
• Domain name
• Host name
• NTP servers
DHCP server operation is described in the document [7]. This server may be hosted by a machine on
the client network or a PCX.
Note:
If the DHCP initialization of an IP phone fails, and if there is a TFTP backup address stored in the IP phone flash
memory, the set switches to "survivability" mode: see Survivability on page 21
2.1.2.2.2.2 Static IP Configuration
The user configures IP data directly on the set. A specific menu, accessed via the set keypad and
display, is used to enter this data. Static IP initialization can prove time consuming and tedious when
there is a number of sets to install.
The IP parameters to enter are:
• IP phone address
• IP subnetwork mask
• Router address
• TFTP server 1 IP address
• TFTP server 2 IP address
Note:
In a duplicated Communication Server configuration, the addresses to enter in the TFTP server 1 and 2 fields
are the main IP addresses of the Communication Servers, as follows:
• When the two Communication Servers are on the same IP subnetwork, the same main IP address can be
used for both Communication Servers. This main IP address must be entered in the TFTP1 server field.
• When the two Communication Servers are on different IP subnetworks, the two Communication Servers
have different main addresses. These two addresses must be entered respectively in the TFTP1 and
TFTP2 fields.
• VLAN ID
• Strict VLAN
• TFTP port

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 18/382

Chapter 2 IP deskphones

2.1.2.2.3 Step 3: lanpbx.cfg File Download

The IP phone requests the lanpbx.cfg file from the TFTP address(es) received at step 2 (and stored in
the IP phone flash memory).
Note:
To create the lanpbx.cfg file, refer to the document [13].
This file contains one or more line. Each line corresponds to one node of the network and contains the
main IP address(es) of the Communication Server(s) on which IP phones are declared.
• At first initialization (no maincpu address stored in flash), the set selects the first line of the
lanpbx.cfg file
• On subsequent initialization (one or two maincpu address(es) stored in flash), the set controls that
the maincpu address(es) stored in flash corresponds to one line of the lanpbx.cfg file:
• if this is the case, the set goes on to step 4 with this address(es)
• if this is not the case, the set erases this address(es) (along with the TFTP backup address) and
goes on as if it was its first initialization.
Note:
If the lanpbx.cfg file cannot be downloaded, the set checks whether a maincpu address is stored in flash:
• If this is the case, the set goes on to step 4
• If this is not the case, the set resets
2.1.2.2.4 Step 4: Software Download
Each time the IP phone is initialized, its binary version is checked to see whether more recent binaries
need downloading. This is detailed in the following sections.
2.1.2.2.4.1 Fast Init
At first initialization or in a migration, the set requests an update of binaries. If TFTPD is available to
proceed with updating, it is done, otherwise the set is put in service and will be updated later.
When an IP phone has initialized at least once with an OmniPCX Enterprise R6.1 or higher, on
subsequent startup, it does not request a binary header and goes directly to step 5 (fast init).
If the software version is upgraded, the IP phone does not request binaries at startup. The set is put in
service, and after starting, because code or data need updating, the system resets the IP phone. At
startup, the set proceeds with binaries updating.
2.1.2.2.4.2 Binary Download and Flashing
Except in case of fast init, the set requests binary. The binary request is sent to:
• The maincpu address(es) stored in flash when it exists
• The addresses of the first line of the lanpbx.cfg file when there are no maincpu addresses stored in
flash
First, only the header of the binary file is sent, in order to check if a full download is needed.
If the downloaded version is different from the running one and if the new binary is compatible with the
hardware/software, the entire binary file is downloaded and flashed. Then the set resets.
If an IP phone belongs to a domain for which SIP survivability is enabled, the SIP binary is also
checked and downloaded if needed.
Note:
If the binary cannot be downloaded, the set goes on to step 5.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 19/382

Chapter 2 IP deskphones

2.1.2.2.4.3 Deny of Download

If the downloaded version is different from the running one and if the new binary is incompatible with
the hardware/software, the terminal denies it and signals the problem to the Communication Server.
Fast init does not apply to a terminal in "deny of download" mode: the terminal requests binary at each
reset until a compatible binary is found.
Deny of download also applies to SIP binary.
2.1.2.2.5 Step 5: Start File Download
• At first initialization (no maincpu stored in flash), the set requests the start file from the address(es)
given in the first line of the lanpbx.cfg file. If this is not successful, the set requests the start file from
the address(es) given in the second line of the lanpbx.cfg file, and so on and so forth.
• If it is successful and the system knows the MAC address of the set, the set is put in service
• If the system does not know the MAC address of the set, a signaling link is established and the
user is asked to enter their directory number (and secret code/password as a precaution). A
search for the host PCX is then performed via the translator, using the set's directory number.
The Ethernet address of the set is registered with the user's data on the host PCX. The PCX with
which the signaling link is established sends the IP address of the host PCX to the set, which
stores it in its flash memory. The set restarts.
• If there is no answer (no PCX has recognized the set), the set restarts.
• At subsequent initialization, the set requests the start file from the maincpu address(es) stored in
flash. The host PCX sends the start file and the set starts.
If there is no response from the maincpu address(es) stored in flash, the set goes on as though it
was its first initialization.
Note:
When an IP phone does not receive the requested start file, it enters "survivability" mode: see Survivability on
page 21.
2.1.2.2.6 Transparent Set Reboot
The Transparent reboot configuration parameter, disabled by default, allows to make the reboot of IP
phone transparent to users.
• If the Transparent reboot option is enabled, users are not informed that their set is being reset.
The set screen displays a screenshot of the home page until the genuine home page is available
again. The set's MMI remains available.
Note:
Reboot takes between thirty to sixty seconds, depending on the implemented survival mode.
• If the Transparent reboot option is disabled, Users can see on their display that their set is being
reset. The set's MMI is available.
For more information on the Transparent reboot option, see: Configuring Phone COS on page 40.

2.1.2.3 Signaling distribution

IP phones in "normal" mode connect to iplink (i.e. to the Com Server), whatever the type of Com Server
and the domain where they are.
In survivability mode, an IP phone of a rescued domain connects to the GD of this domain or to the
Passive Communication Server (PCS) associated to this domain: see Survivability on page 21.
In SIP survivability mode, an IP phone set connects to the SIP server associated to this domain.
The Keep RTP flow configuration parameter, disabled by default, allows to maintain ongoing voice
communications, when possible. This parameter applies to IP phones, regardless of the survivability
mode of the set (see: Survivability on page 21).

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 20/382

Chapter 2 IP deskphones

Reboot takes between thirty to sixty seconds, depending on the implemented survival mode.
Expiration of the DHCP lease has no impact on the communication.
If in a conference via the OmniPCX Enterprise media gateway, the call is released and reboot of the set
is immediate.
When the connection with the CS (or PCS) is lost:
• If the Keep RTP flow option is enabled:
• Idle sets reset immediately
• For sets in communication:
• Calls between IP-phones are maintained if the IP network is still up between the call parties.
• Calls between an IP phone and a GD (or an INT-IP) board fail. When GD (or INT-IP) boards
lose the signaling link with the communication server, these boards restart and associated
calls fail.
• Calls between an IP phone and a SIP gateway are maintained if the gateway supports the
lost of the signaling link.
When the call is maintained, softkeys or hardkeys do not work anymore, except for the
Loudspeaker, Mute/unmute, Volume and Release keys.
At the end of the communication, or when no incoming RTCP traffic gets to the set, the set
reboots. Reboot is mandatory to get back to normal operations, even if the connection with the
CS (or PCS) is available again.
• If the Keep RTP flow option is disabled, all sets reset immediately, even if in communication.
For more information on the Keep RTP flow option, see: Configuring Phone COS on page 40.

2.1.2.4 Survivability
2.1.2.4.1 Survivability Context
Survivability applies for IP phones:
• Situated in a domain which has been configured to be rescued by a Passive Communication Server,
or
• Situated in a branch office with a rescuable Media Gateway, and configured in dynamic mode,
whether the DHCP Server is external or integrated to the Communication Server
Survivability operates when:
• The external DHCP Server is out of service or not reachable
• The Communication Server is not reachable via the IP network
IP phones use the Rescue IP address stored in flash.
SIP survivability applies to IP phone situated in domains for which SIP survivability is enabled and
where there is a router implementing SIP proxy features: see SIP Survivability on page 23. SIP
survivability operates when the Communication Server is not reachable via the IP network.
2.1.2.4.2 IP phones in a Domain Rescued by a Passive Communication Server
When the IP link to the Communication Server is lost, the IP phone restarts and changes to
“survivability” mode. It connects to the Passive Communication Server using the rescue IP address
sent by the Communication Server at initialization, thus enabling a Start_Noe.
IP phones in SIP stand-alone mode can be rescued by a Passive Communication Server.
For more information about the operation and configuration of a Passive Communication Server, refer
to the document [1].

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 21/382

Chapter 2 IP deskphones

2.1.2.4.3 IP phones in a Branch Office with a Rescuable Media Gateway

IP phones located in a branch office with a rescuable Media Gateway can be initialized in dynamic
mode. This entails that:
• They can start even if the Media Gateway has not started yet
• They can operate even if the Media Gateway is out of service
IP phones can switch to "survivability" mode, where they can operate in degraded conditions (IP link
broken with the Communication Server).
When the IP link to the Communication Server is lost, IP phones switch to "survivability" mode and
request the startNOE file from the TFTP backup address (i.e. the GD board IP address). IP phones
communicates with the Communication Server via the backup signaling link.
Communication
Server
Rescued Media IP phone
Gateway

Download
STARTNOE
WAN
Download IP
parameters

Domain 0 DHCP

Signaling link PSTN

Domain X

Figure 2.1: Survivability mode with the Communication Server unreachable via IP

When the signaling link between the Communication Server and the GD board switches back to normal
mode, the signaling link is established directly with the Communication Server again. The switchover is
transparent for IP phones.
For survivability to operate:
• The set must belong to the same domain as the Media Gateway's GD board
• A backup IP address (TFTP backup address) must be entered in the parameters for the IP domain:
this address corresponds to the GD address: refer to the document [7].
• The set must have initialized at least once in "normal" mode and during this first initialization, the
Communication Server transmitted the backup address (TFTP backup address)
2.1.2.4.4 DHCP Survivability
When it receives no reply from the DHCP server, the set initializes with the parameters stored in the
flash memory (if these are valid).
• If the signaling link with the Communication Server is valid. The set establishes its signaling link with
the Communication Server (this occurs when the DHCP server is external to the Communication
Server)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 22/382

Chapter 2 IP deskphones

Communication IP phone
Server
Media Gateway

WAN
Signaling link DHCP Request

DHCP
Domain 0

Domain X

Figure 2.2: Survivability mode with external DHCP server unreachable

• If the signaling link with the Communication Server is not valid. The set establishes its signaling link
with the GD board, rescuable Media Gateway, or Passive Communication Server (this occurs when
the DHCP server is internal to the Communication Server)

Communication
Server IP phone
Rescued Media
Gateway

WAN
DHCP request

Domain 0

Domain X
Signaling link PSTN

Figure 2.3: Survivability mode with integrated DHCP server unreachable

In this mode, the set tries, every minute, to recover an IP address from the DHCP server. It sends a
DHCPDISCOVER message containing its current IP address (stored in flash). When the set receives
an answer from the DHCP server, it checks the IP address received:
• If the address received is the same as the one stored in flash, it keeps using it
• If the address is different, the set resets
2.1.2.4.5 SIP Survivability
SIP survivability allows an IP phone to operate in SIP mode when the link with the Communication
Server is down.
SIP survivability is available for IP phones operating in NOE proprietary mode or SIP standalone mode.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 23/382

Chapter 2 IP deskphones

Communication
Server PSTN
IP phone
SIP
proxy

WAN

Domain 0 Domain X

SIP registration to the local SIP proxy

SIP signaling

Figure 2.4: Set in SIP Survivability Mode

A set switches back to NOE proprietary mode or SIP standalone mode when the link with the
Communication Server is reestablished.
In SIP survivability mode, the set interacts with a SIP proxy located in the branch office and benefits
from a limited set of phone features.
SIP features available on a set in SIP survivability mode are the same as those available for sets in SIP
"stand-alone" mode. Calls to the central office (domain 0) and other branch offices can be established
by the SIP proxy server through the PSTN.
For SIP survivability to operate:
• The set must belong to a domain where a SIP proxy server is present
• The IP domain must not be rescued by a Passive Communication Server or a backup signaling link
• The SIP survivability mode of the IP domain must be enabled and SIP parameters must be provided
• The set must have initialized at least once in NOE proprietary mode and during this first
initialization, the Communication Server transmitted the SIP binary and SIP parameters

Communication
Server PSTN
IP phone
SIP
proxy

WAN

Domain 0 Domain X

TFTP downloading of SIP binary

Transmission of SIP parameteres through NOE Signaling

Figure 2.5: IP phone in NOE Mode

More information on SIP survivability configuration can be found in the document [7].

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 24/382

Chapter 2 IP deskphones

2.1.2.4.6 Interaction with IP Touch Security (Encryption)

When in survivability mode with an active Passive Communication Server, the Passive Communication
Server, which is configured for encryption in the same way as the Communication Server, ensures
encryption of calls.
After initialization, the Communication Server sends a flag to indicate whether the Media Gateway is
secured by an IP Touch security module.
When in "survivability" mode with signaling link established with the GD board:
• If the Media Gateway is secured, an IP phone remains secured
• If the Media Gateway is not secured, an IP phone is not secured
SIP survivability applies to secured sets, but sets are secured only in NOE mode. In SIP survivability
mode, sets are not secured.

2.1.2.5 IP phones in a Duplicated Configuration

IP phones can operate in a Communication Server duplicated configuration where the two
Communication Servers are on different subnetworks.
In most breakdown scenarios, switchover is transparent for IP phones. However, in cases of double
main, when normal service is resumed, the pseudo-main Communication Server (the Communication
Server which could not reach the reference Media Gateway) reboots to take on its role as stand-by and
all its related IP phones reboot. The calls managed by this Communication Server are lost.

2.1.2.6 LLDP-MED
All IP phones (extended edition or not, whether operating in NOE or SIP mode) comply with LLDP-
MED.
The LLDP / LLDP-MED allows information exchange between end devices and adjacent LAN switches.
This mechanism is based on IEEE 802.1AB and ANSI TIA 1057 (LLDP-MED) standards.
By default, LLDP-MED is activated on IP phones and allows:
• Automatic VLAN assignment
• Power consumption negotiation with more accurate values than the PoE class information
• To send inventory information of terminal to adjacent LAN switch.
Inventory information sent by an IP phone includes:
• Hardware revision
• Software version
• Firmware version
• Serial number
• Manufacture name (set to ALE International)
• Model name (set to NOE 4008 EE or NOE 4018 EE)
• Asset ID (set with the SIP configuration file to the set MAC address)

2.1.2.7 Quality of Service (QoS)

Calls from an IP phone contain QoS information (diffserv or 802.1Q priority level, VLAN number).
Priority level is configured on the PCX and is assigned to the terminal at initialization.
VLAN number can be:
• Configured directly on the terminal
• As of OmniPCX Enterprise, Release R9.1, assigned by the switch through LLDP-MED

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 25/382

Chapter 2 IP deskphones

• Assigned by the PCX internal DHCP server or an external AVA server at initialization (refer to the
document [7])
For more information on IP QoS management, refer to the document [7]).

2.1.2.8 Protection against Intruders

Several mechanisms exist on IP phones to prevent intruders from masquerading as legitimate network
users:
• Connect messages filtering: The Communication Server activates message filtering in the sets.
This enables the sets to reject connection requests from IP addresses not defined in the LAN
configuration file (lanpbx.cfg).
• MAC address spoofing defense: During set initialization, the Communication Server requests the
MAC address from the set. If the MAC address is the same as the one received in the start request,
initialization continues. Otherwise, the Communication Server restarts the set.
• ARP spoofing defense: Sets broadcast Address Resolution Protocol (ARP) requests in order to
link IP addresses with MAC addresses for each IP user on the LAN. To be aware of any intrusion,
you can configure sets to detect ARP Spoofing. The Communication Server sends a timer value to
the sets. When a set receives two or more ARP replies for the same ARP request during the time
indicated by the timer, the set considers this an ARP spoof and sends an incident the
Communication Server. To configure sets for ARP spoofing defense, refer to the document [7].

2.1.2.9 Set Power Supply

IP phones can be powered in two ways:
• Locally, from the mains socket via the adapter.
• Via Ethernet, using PoE (Power over Ethernet) technology.
PoE offers the advantage of simplified wiring. It also allows the system to be secured more easily. A
single backup power supply can be used for all devices connected to a switch.
PoE can be performed:
• Via the Power Patch Panel A4098 PP, refer to the document [22].
• Via a switch compatible with the 802.3af standard, for example 7000 Series Data Switches
delivered by ALE International.
• Via the 3 Port PoE Gigabit Adapter, a switch which transmits electrical power and data to Alcatel-
Lucent 8 series sets over standard twisted-pair cables in an Ethernet network, and also provides a
separate 1 GB connection for the PC associated with the set. For more information, refer to the
document [22].
IP phones support LLDP-MED PoE management. LLDP-MED optimizes power feeding by providing
some more accurate information than the class number. The power value provided includes the
consumption of three additional key modules (even if not present on the set). Equipment connected to
the PC port is not taken into account and requires separate power feeding.

table 2.1: IP phone Power Supply

IP phone

Power Patch Panel Yes

802.3af compatible Yes

3 Port PoE Gigabit Adapter Yes

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 26/382

Chapter 2 IP deskphones

IP phone

Power class information Yes:

• Alcatel-Lucent IP Touch 4068 phone Extended
Edition set: class 3
• Other IP phones: class 2

LLDP-MED PoE Yes

table 2.2: IP phone Power Consumption

Set Type Measured Power Consumption (W)

Idle On Max

Alcatel-Lucent IP Touch 4008 phone Extended Edition 2.6 2.65 2.65

Alcatel-Lucent IP Touch 4018 phone Extended Edition 2.7 2.75 2.75

Alcatel-Lucent IP Touch 4028 phone Extended Edition 3.5 3.55 3.55

Alcatel-Lucent IP Touch 4038 phone Extended Edition 3.5 3.55 3.55

Alcatel-Lucent IP Touch 4068 phone Extended Edition 3.8 4.45 4.45

Power consumption presented in the Table 2 have been measured in the following configuration:
• The Local Area Network is connected. The network speed is the maximal speed allowed by the set:
100 Mbps or 1 Gbps.
• There is no computer connected on the PC port.
• There are no additional module connected to the set.
• The Alcatel-Lucent IP Touch 4068 phone Extended Edition sets have a wired handset: Bluetooth is
not used.
• The set is supplied locally via the AC/DC adapter (PoE would lead to a slightly higher consumption).
• Power loss on the external AC/DC adapter is not taken into account.
• Measurements have been performed in three different states:
• Idle: the set is initialized, there is no audio communication, the backlight of Alcatel-Lucent IP
Touch 4068 phone Extended Edition sets is switched off.
• On: the set is in communication, the sound volume is set to the nominal value, there is no
injected audio signal.
• Max: the set is in communication, the sound volume is set at the maximal value as well as the
injected audio signal.

2.1.3 Configuration procedure

2.1.3.1 Requirements
• For set initialization in dynamic mode:
• A DHCP server must be configured, refer to the document [7].
• If the DHCP server serves IP phones on different nodes, the "lanpbx.cfg" file must be created
manually, refer to the document [13]

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 27/382

Chapter 2 IP deskphones

• For set operation: for the IP phones to be able to communicate with the Media Gateways, the
Media Gateways must be equipped with an IP board (GA, GD, INT-IP).

2.1.3.2 Software locks

Two software locks are available to enable or limit the use of IP phones:
• Lock no.176 Advanced IP users determines the maximum of IP phones without service restriction
• Lock no. 317 Standard IP users determines the maximum of IP phones with the following
restrictions:
• No more than two multilines
• No supervision
• No Manager/Assistant configuration
• No MLA keys

2.1.3.3 Declaring an IP phone

1. Select: Users
2. Review/modify the following attributes:

Directory Number Enter the IP phone user's directory number.

Shelf Address Enter 255 (255 means not connected). The IP phone is
not physically connected to the PCX.

Board Address Enter 255. The IP phone is not physically connected to

the PCX.

Equipment Address Enter 255. The IP phone is not physically connected to

the PCX.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 28/382

Chapter 2 IP deskphones

Set Type Select the type of IP phone used:

• IPTouch 4008: : to declare an Alcatel-Lucent IP Touch
4008 Phone
• IPTouch 4018: to declare an Alcatel-Lucent IP Touch
4018 Phone
• IPTouch 4028: to declare an Alcatel-Lucent IP Touch
4028 Phone
• IPTouch 4038: to declare an Alcatel-Lucent IP Touch
4038 Phone
• IPTouch 4068: to declare an Alcatel-Lucent IP Touch
4068 Phone
• IPTouch 8018: to declare a 8018 DeskPhone
• IPTouch 8028: to declare a 8028 Premium
DeskPhone
• IPTouch 8038: to declare a 8038 Premium
DeskPhone
• IPTouch 8068: to declare a 8068 Premium
DeskPhone
• IPTouch 8088: to declare a 8088 Smart DeskPhone
• IPTouch 8028s: to declare a 8028s Premium
DeskPhone
• IPTouch 8058s: to declare a 8058s Premium
DeskPhone
• IPTouch 8068s: to declare a 8068s Premium
DeskPhone
• IPTouch 8078s: to declare a 8078s Premium
DeskPhone
3. Confirm your entries
The other attributes are not specific to IP phones.
Once the IP phone has been declared, it can be put into service. See:
• Commissioning on page 128
• Commissioning on page 107
• Commissioning IP Premium DeskPhone sets on page 85
• Set configuration and deployment on page 96

2.1.3.4 Configuring Programmable Keys

The keys may be programmed:
• Directly on the set.
• On the PCX.
For details about configuring the keys, see: Configuring programmable keys on page 342.

2.1.3.5 TSC IP User Parameters

When a user with an IP phone is created, a hierarchically dependent TSC IP User object is
automatically created. This contains specific IP phone operating data.
Note:
The TSC IP User parameters do not have to be configured to put the set into service. The default values can be
used.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 29/382

Chapter 2 IP deskphones

1. Select Users > TSC IP User

2. Review/modify the following attributes

Directory Number Displays IP phone user's directory number.

Set Type Displays the type of IP phone used.

Voice Coding Algorithm • Default: the IP Domain object parameter is used.

• With Compression: the type of compression specified in
the system parameters is used.
• Without Compression: no compression, coding
complies with the G711 standard.
Refer to the document [7].

Terminal Ethernet Address This field contains the Ethernet address (MAC address) of
the IP phone.
This field is automatically completed when the set is initial-
ized, but can also be completed manually. In this case, the
user does not have to go through the identification sequence
(i.e. enter his directory number and secret code) when initial-
izing his set.
The Ethernet address has to be deleted in order to deselect
the set (e.g. when the user changes sets). This can be done:
• In management, by replacing it with ”“ (double inverted
commas).
• Directly on the set, by entering the de-commissioning (out
of service) prefix.

IP Address Displays the IP address assigned to the terminal. This field is

completed when the IP phone is initialized.
If the field is set to Unused, no IP address is assigned to the
IP phone and it is not operational.

IP Domain Number Displays terminal domain number.

Use of volume in system Reserved for ALE International support.

• Yes (default value): the user uses the volume specified in
TSC/IP Parameters.
• No: Volume is configured on the set.

Local Volume (dB) Parameter to be entered only if the previous parameter is set
to "No". Enter volume in dB (for ALE International support
only).
Default value: 0.

Reset For Update Authorized • Yes (default value): authorizes the Communication Server
to update binaries on the set
• No: prohibits the Communication Server from updating
binaries on the set

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 30/382

Chapter 2 IP deskphones

3. Confirm your entries

2.1.3.6 Configuring the Backup Address for IP Touch Survivability

1. Select: IP > IP domain
2. Review/modify the following attributes

Backup IP address Depending on the backup type enter either the:

• IP address of the GD board to which the IP phones of the
domain much attach when in backup mode, or
• IP address of the Passive Communication Server to
which the IP phones of the domain much attach when in
backup mode
3. Confirm your entries

2.1.3.7 Configuring SIP Survivability

SIP survivability does not require any configuration to be performed directly on Alcatel-Lucent IP Touch
8 series phone Extended Edition sets. The IP parameters (static or dynamic IP parameters) used are
the same as for the NOE mode. All necessary parameters for SIP survivability are sent by the
Communication Server during the set initialization.
Note:
If a mandatory parameter is missing on the PCX, an incident is triggered at set initialization and the SIP
parameters are not sent: see Error 438 on page 59.
To configure SIP survivability, you must:
1. Enable SIP survivability for an IP domain and configure SIP parameters: see Enabling SIP
Survivability for an IP Domain on page 31
2. Configure parameters allowing IP phones to download their SIP binary: see Configuring IP Phones
Parameters Required for SIP Binary Download on page 32
3. Configure parameters allowing IP phones to continue receiving calls from Alcatel-Lucent OmniPCX
Enterprise Communication Server when they switch to survivability mode: see Configuring
Parameters Required for Call Rerouting to IP phones in Survivability Mode on page 32
4. Configure other parameters which are sent by the PCX to the IP phones: see Configuring the Other
Parameters Used for SIP Survivability on page 34
2.1.3.7.1 Enabling SIP Survivability for an IP Domain
1. Select: IP > IP domain
2. Review/modify the following attributes:

SIP survivability mode Select Yes to enable the survivability for this domain.
Default value: No
Note:
The activation or deactivation of the SIP survivability mode is
taken into account immediately by the sets belonging to this
domain.
Note:
The SIP survivability mode cannot be enabled if the domain is
rescued by a Passive Communication Server or a backup signaling
link.

SIP DNS Address Enter the IP address of the DNS (optional).

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 31/382

Chapter 2 IP deskphones

SIP Domain Name Enter the domain name, if different from the proxy address
(optional).

SIP Authentication Realm If authentication is used, enter the authentication realm (op-
tional).

Proxy IP Address Enter the IP address or the name of the proxy (mandatory).

Proxy Port Number Enter the port number (optional).

Default value: 5060

SIP Transport Mode Select UDP or TCP (optional).

3. Confirm your entries
Note:
The modification of the SIP survivability mode is taken into account immediately. For other parameters, the
update occurs once a day.
4. To force an immediate update of the SIP parameters modified since the last update, select Activate
SIP Survivability.
2.1.3.7.2 Configuring IP Phones Parameters Required for SIP Binary Download
The following parameters allow IP phones to download their SIP binary at initialization. If this operation
is not carried out, the IP phones reset permanently at initialization.
1. Select Users
2. Review/modify the following attributes:

URL UserName Enter, for example, the directory number of the set or user
name

URL Domain Leave this field blank

SIP Passwd Enter a password (10 characters maximum)

Note:
The SIP authentication password is set by default at the same
value as the default password (secret code).

Confirm Confirm password

3. Confirm your entries
2.1.3.7.3 Configuring Parameters Required for Call Rerouting to IP phones in Survivability Mode
Call rerouting involves the association of virtual sets to IP phones. When IP phones switch to
survivability mode, incoming calls to these IP phones (seen as out of service sets by the
Communication Server) overflow to their associated set (i.e. virtual set). These associated sets are
configured in immediate forward. The forward number is: the prefix to reach the public network followed
by the IP phone directory number. Calls are routed (through the PSTN) to the SIP proxy server to which
these IP phones are connected.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 32/382

Chapter 2 IP deskphones

IP set in SIP
Caller survivability mode
IP link with
the Com Server is down

IP Network

SIP Proxy Server

OmniPCX
Enterprise PSTN

Virtual set associated

to the IP set

: Incoming call to an IP set in SIP survivability mode

Figure 2.6: Example of Call Rerouting to an IP Set in Survivability Mode

To allow call rerouting to IP phones operating in survivability mode, proceed as follows:

• Create virtual sets
1. Select Users
2. Review/modify the following attributes:

Directory Number Enter the directory number of the virtual set

Shelf Address Leave the default value: 255

Board Address Leave the default value: 255

Equipment Address Leave the default value: 255

Set type Select Analog

3. Confirm your entries
• Associate the virtual sets to the target IP phones and authorize the overflow to associate
1. Select Users > Dynamic State User
2. Review/modify the following attributes:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 33/382

Chapter 2 IP deskphones

Directory Number Enter the directory number of the IP phone

Overflow on associate Select True

Associated Set No. Enter the directory number of the virtual set
3. Confirm your entries
• Authorize the overflow to associate when the IP phones are out of service
1. Select Classes of Service > Phone Features COS
2. Review/modify the following attribute:

Forward if MIPT/IP out of serv- Select 1 to authorize call rerouting to the virtual set associ-
ice ated to out of service IP phone
3. Confirm your entry
• Configure virtual sets to immediately forward calls to IP phones in survivability mode
1. Select Users > Dynamic State User
2. Review/modify the following attributes:

Directory Number Enter the virtual set directory number

Forward Select Immediate Forward

Associated Set No. Enter the prefix to reach the public network, followed by
the IP phone directory number
3. Confirm your entries
2.1.3.7.4 Configuring the Other Parameters Used for SIP Survivability
Other parameters sent by the PCX at initialization of sets and used for SIP survivability are:

Parameter Access Path Default Value Comments

Directory Name Users Empty Concatenation of the Directory

Name and Directory First Name in
Directory First Users Empty Latin characters is used as display
Name name

SIP Authentication Users Empty Authentication name

SIP Passwd Users Empty Authentication password

Time Zone Name IP > IP domain System Default

TOS/diffServ IP > IP Quality Of 46 This value is used for media

Service COS streams. For more information, see:
Configuration procedure

SIP Diff. Service IP > IP Quality Of 40 This value is used for SIP signaling.
Service COS For more information, see: Configu-
ration procedure

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 34/382

Chapter 2 IP deskphones

Parameter Access Path Default Value Comments

Country for exter- System English

nal signaling

Local Feedback IP > TSC/IP Pa- False

tone On Ipp rameters

Timer No. System 60 seconds Timer No. 370 (Communication

Server polling timer)

For the following parameters, the PCX sends default values to IP phones. These default values can be
configured locally on IP phones:
• Language (default value: English)
• Ringing melody (default value: 4)
• Melody level (default value: 7)
• Headset level (default value: depends on the country)
• Handset level (default value: 3 for numeric mode, 5 for analog mode)
• Display contrast (default value: 8)
• Loudspeaker level (default value: 8)
• Home page tab (default value: personal)
• Time format (default value: 24 hour)

2.1.3.8 Declaring the Administrator Password for IP phones

The access to the administration menu of IP phones can be protected by a password. Password
protection is mandatory if IP Touch Security is used.
1. Select Alcatel-Lucent 8&9 Series > IPTouch sets generic parameters
2. Enter the following attributes:

Noe password Enter the password (between 6 and 12 characters). It may

contain digits (0 to 9) and/or lower case letters (a to z).

Confirm Confirm the password entered previously.

3. Confirm your entries

2.1.3.9 Activating ARP spoofing defense

With the ARP spoofing defense activated, when the IP phone broadcasts an ARP request, the
Communication Server sends a timer value (in milliseconds) to the set. If the set receives two ARP
replies during this timeout period for the same ARP request, the set considers one reply as an attack.
The set sends an incident to the Communcation Server.
To activate the ARP spoofing defense:
1. Select Alcatel-Lucent 8&9 Series > IPTouch sets generic parameters
2. Enter the following attribute:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 35/382

Chapter 2 IP deskphones

ARP spoofing defense Enter the value in milliseconds for the ARP
spoofing defense timer.
The default value is 0 (no defense).
Maximum recommended value is 1000 ms.
3. Confirm your entry

2.1.3.10 TSC/IP Parameters

TSC/IP Parameters are system parameters valid for all IP phones on the node.
2.1.3.10.1 Default Voice Coding Algorithm
Refer to the coding configuration in the document [7].
2.1.3.10.2 MTU
1. Select: IP > TSC/IP Parameters
2. Review/modify the following attribute

Parameter Select: MTU.

MTU Maximum Transmit Unit on the IP network: this parameter indicates

the maximum size (in bytes) of a packet than can be transmitted on
the IP network.
Default value 1024 (reserved for ALE International support).
Note:
For IP phones, 1024 is the mandatory value.

3. Confirm your entry

2.1.3.10.3 Window Size
1. Select: IP > TSC/IP Parameters
2. Review/modify the following attribute

Parameter Select: Window Size.

Window Size Default value 1 (reserved for ALE International support).

3. Confirm your entry
2.1.3.10.4 Volume in dB for IP phones
1. Select: IP > TSC/IP Parameters
2. Review/modify the following attribute

Parameter Select: Volume in dB for IP phones.

Volume in dB for IP This parameter defines the volume for IP phones with the Use of
phones volume in system parameter set to "Yes".
Default value 0 (reserved for ALE International support).
3. Confirm your entry
2.1.3.10.5 Local Feedback Tone on Ipp
1. Select: IP > TSC/IP Parameters

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 36/382

Chapter 2 IP deskphones

2. Review/modify the following attribute

Parameter Select: Local Feedback tone On Ipp.

Local Feedback tone On Ipp Specifies feedback tone generation mode on integrated IP
phones.
• Yes: the IP phone generates the tones.
• No: the PCX sends tones to the IP phone.
3. Confirm your entry

2.1.4 Additional configuration operations

2.1.4.1 Configuration additional operations for sets
When a user with a Premium DeskPhone set is created, a hierarchically dependent 8&9 Series
Parameters object is automatically created. This contains specific data on display options, access
rights to external applications, user rights to customize the home page.
Note:
Additional configuration on Premium DeskPhone and Alcatel-Lucent 8/9 series sets are very similar. In the
following paragraphs all mentions to Premium DeskPhone apply to Alcatel-Lucent 8/9 series sets, unless specified
otherwise
2.1.4.1.1 Configuring Alcatel-Lucent 8/9 series parameters
1. Select: Users > 8&9 Series Parameters
2. Review/modify the following attributes

Directory Number Enter the set directory number

Application COS ID Enter application COS number (between 0 and 31)

Default value: 0

Phone COS Enter the phone COS number (between 0 and 31)
Default value: 0

Default Home Page Select the home page to be displayed when the set returns
to idle:
• Home Menu
• Home Perso
• Home Info
• Home Appli
• Home CCD
• None: the set displays the page viewed when the set
was last idle.
Default value: Home Perso
Notes:
IP Touch set users can configure their own default page from the
Menu page of their set.
Other Home pages may be available (e.g. Ccd) according to
system configuration.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 37/382

Chapter 2 IP deskphones

Default IME A display-only value that shows the last input method char-
acter type used. Default value is No input.

Serial number Displays the set serial number. This value cannot be modi-
fied.

4059 Directory Number Displays the 4059 IP Attendant directory number, where
applicable.
3. Confirm your entries
2.1.4.1.2 Enabling external called number display
A parameter enables to select whether the dialed number or the trunk group name is displayed on the
display of phones. This parameter applies to external outgoing communications.
1. Select System > Other System Param. > Attendant Parameters
2. Review/modify the following attribute:

Display number during conversation • True (default value): the called number is
displayed on the display
• False: the trunk group name is displayed on
the display
3. Confirm your entries
2.1.4.1.3 Defining external applications
The system can recognize up to seventeen external applications that can be accessed by phones. An
identifier must be assigned to each concerned external application.
1. Select Alcatel-Lucent 8&9 Series > 8&9 Series applications > Access to restricted
applications
2. Review/Modify the following attributes:

Application Id Enter an ID number: possible values 0 to 16

Application name Enter a name for this application (up to 16 characters)

3. Confirm your entries
2.1.4.1.4 Configuring application COS
There are three (or more) home pages: MENU, PERSO, INFO, (APPLICATIONS). The different
applications (internal and external) are displayed in the MENU tab (whatever the home page
configured in administration).
Application COSs are used to:
• Specify the order in which the different applications (internal and external) are displayed on the set's
MENU home page.
• For each external application, give or limit access to all users in this COS.
Thirty two COSs are created by default. A COS is assigned to a set in the user's Series 8&9 classes
of service. By default, COS 0 is assigned.
1. Select: Alcatel-Lucent 8&9 Series > 8&9 Series COS > Applications COS
2. Review/modify the following attributes

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 38/382

Chapter 2 IP deskphones

Application COS ID Enter the number of the COS to be viewed or modified (be-
tween 0 and 31)

Application COS name Enter a name for this COS (20 characters at the most)

When a COS number has been selected, fields are displayed as shown below, as many times as
there are applications (internal applications are displayed first, followed by external applications).

Application Name

Priority Enter priority (between 0 and 255):

• 0: not presented, select 0 to bar use of an external
application.
• 1 (highest priority): presented at the top left
• 2: presented at the top right
• and so on...
Default value for external applications: 0
Default value for internal applications: see Table 1.

table 2.3: Default priority for internal applications

Internal application Default priority

Settings 1

Redial 2

Appointment 3

Lock 4

Text mail 5

Forward 6

No reply 7

Who am I 8

Repertory 9

Manager/Assistant 10

External application No 1 11
When they exist, other exter-
nal applications follow this
first one in the priority list.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 39/382

Chapter 2 IP deskphones

Notes:
For internal applications, the level of priority only defines the desired location on the home page menu and not
user rights for application use. User rights are configured in the user's phone features COS.
Other applications, such as e.g. Ccd, can appear in this list, according to system configuration.
3. Confirm your entries
2.1.4.1.5 Configuring Phone COS
Note:
The phone classes of service described here are specific to Premium DeskPhone and Alcatel-Lucent 8/9 series
sets.
Do not confuse these phone COSs with phone features COSs that apply to all sets (including Premium
DeskPhone and Alcatel-Lucent 8/9 series sets), and that are used to configure user access rights to phone
features (forwarding, conference calls, etc.).The phone features COS applying to all users is configured via:
Classes of Service > Phone Features COS
Phone COSs are used to define graphical user interface (GUI) and to grant or limit user rights to
customize home page.
Phone COSs are created by default. There are 32 COSs. A COS is assigned to the set in the user's
8&9 Series Parameters. By default, COS 0 is assigned to newly declared sets. This specific phone
COS is assigned to the concerned users via: Users > 8&9 Series Parameters.
1. Select: Alcatel-Lucent 8&9 Series > 8&9 Series COS > Phone COS
2. Review/modify the following attributes

Phone COS Enter the number of the COS to be viewed or modified (be-
tween 0 and 31)

Phone COS Name Enter a name for the COS

Right to Modify Default Home Page • Yes: users in this COS have the right to modify their set
home page
• No: users in this COS do not have the right to modify
their set home page
Default value: Yes

Home bar • Yes: the home bar changes to inform the user of set
forwarding status
• No: the home bar does not change and displays only
date information
Default value: No

Ringing Cadence • Yes: each ringing sound is followed by a short silence

• No: ringing sound is continuous
Default value: Yes

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 40/382

Chapter 2 IP deskphones

State LED Message Determines the behavior of the LED message according to
received messages.
• State - ON (default value): when at least a message
(alarm, voice, text, callback, unanswered call) has not
been heard/viewed, the LED blinks red.
After message consultation, the Message LED is lit red.
If there is no message left in the message memory, the
Message LED is off.
• State - OFF: when at least a message (alarm, voice,
text, callback, unanswered call) has not been heard/
viewed, the LED blinks red.
After message consultation, the Message LED is off.
• State - Blinking: when at least a message (alarm,
voice, text, callback, unanswered call) has not been
heard/viewed, the LED blinks red.
After message consultation, the Message LED blinks
red.
If there is no message left in the message memory, the
Message LED is off.
• State - UA Equivalent (as per USA standard
behavior): when there is at least one new message the
LED blinks slowly
When at least one message has been archived and/or
there is at least one unanswered call, the LED is lit red.
If there is no message left in the message memory, the
Message LED is off.

Authorized IME The list of additional input method character types author-
ized.
Possible values:
• No input (meaning only the default, Latin, is
authorized)
• Cyrillic
• Pin Yin
• Jamo
• Stroke
• Zhu Yin

CBN : Display Name without Pho- • Yes: when available, displays only the name of the
neNb calling/called party
• No: displays number and name (when available) of the
calling/called party
Default value: Yes

Display Encrypted Communication • Yes: when the current call is secured with encryption,
displays the secured icon on the set screen
• No: no indication of encryption is displayed on the set

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 41/382

Chapter 2 IP deskphones

Display Supervision State • Yes: displays the status of supervised set (the icon
depends on the status of this set) next to the
supervising key
• No: no indication of status of supervised set is
displayed on the set

Show on top update of Info Page • Yes: In idle state, displays the Info page when new
messages or new unanswered calls are recorded
• No: The page displayed remains the same when new
messages or new unanswered calls are recorded

Main page at Top Level • Yes: Every new display of the Main (Perso) page
shows the first keys of the page
• No: Every new display of the Main (Perso) page goes
back to the position it was previously

Displ. unans calls if Homepage app On sets with the external application My Homepage, by
default unanswered calls are not displayed on the Info
page. To display unanswered call information on the Info
page on sets with My Homepage, set this attribute to True.
Default value is False.

Hide Key Forward to MV/Text When value is True, the set hides the softkeys Immediate
Fwd to VM and Fwd to text. Default value is False (the
set displays the softkeys).

Display Main Page on off-hook • Yes: allows to display automatically the Main (Perso)
page on off-hook
Default value: No.

State PC port • Cascad. not filt. (IP-Phone or PC): the set PC port is
enabled. Packets are transmitted without filtering.
• PC port disabled: the set PC port is disabled. This
option is used to prevent daisy chaining of a PC behind
a terminal.
• Cascading with filtering (PC only): the set PC port is
enabled and packets are filtered:
• Frames coming from the LAN to the PC: 802.1q tags
are removed
• Frames coming from the PC to the LAN: 802.1q tags
are replaced by the default VLAN tag (VLAN=0).
This option ensures that no Voice VLAN traffic can be
sent from illegitimate sources.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 42/382

Chapter 2 IP deskphones

Main Page Auto Display Enable • Yes: allows to display automatically the Main (Perso)
page if no action is done after a timeout: Timer No. 371
(see Timers on page 51).
• No: The page displayed remains the same.
Default value: No.
Note:
This option is useful when the emergency keys (keys
programmed with emergency numbers) are configured on the
first keys of the Main (Perso) page. It allows these keys to remain
always visible.

Second Call Ring Type Select any of the following:

• Beep (default value)
• Long Ring
• Short Ring

8&9 Series Handsfree Mode Select YES to enable echo robustness in handsfree mode.

Customization File Name Enter the customization file name for sets needing special
ringing melodies
Example:
Enter mycompany if the customization file names are as
follows:cust-mycompany-80x8 cust-
mycompany-80x9cust-mycompany-8029 cust-
mycompany-8039

Keep RTP flow This parameter controls the reboot of sets when the con-
nection with CS or PCS is lost:
As of R10.1
• True:
• Idle sets reset immediately.
• Ongoing communications are maintained, but
operations are limited: no softkey or hardkey work,
except for the Loudspeaker, Mute/unmute, volume
and Release keys. Sets reboot at the end of the
communication, or when no incoming RCTP traffic
gets to the set.
• False (default value): all sets reboot immediately, even
if in communication.
Notes:
• It is necessary to reset sets after the modification of this
parameter.
• This feature is not available on 8088 Smart DeskPhone and
80x8s Premium DeskPhonesets.
For more information, see Signaling distribution on page
20 and document [1].

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 43/382

Chapter 2 IP deskphones

Bluetooth enabled • Yes: Bluetooth will be enabled on corresponding set

• No: Bluetooth is disabled on corresponding set
Default value: Yes
Note:
It is necessary to reset sets after the modification of this
parameter (sets will reboot twice).

Transparent reboot This parameter controls the reboot of sets:

• True: users are not informed that their set is being
reset. The set screen displays a screenshot of the
home page until the genuine home page is available
again. The set's MMI remains available.
• False: Users can see on their display that their set is
being reset. The set's MMI is available.
This feature is not available on 8088 Smart DeskPhone
sets.

Hide Services Lists • Yes: The Services softkey is not displayed on the
screen but the services are still available
• No: The list of services is available in menus
Default value: No

Voice Mail PRS application ID Enter the four-character string, which is the application ID
configured in the PRS application, to access the SIP voice
mail from the set voice mail key. Example: MY_M (Default
value: NULL).
The set screen displays a menu when pressing the voice
mail key.
When the string is empty, pressing the voice mail key
starts the TUI application, which displays no menu on the
screen but plays interactive voice guides allowing access
to the SIP voice mail.

Skin Number Skin selection is available on 8058s Premium DeskPhone,

8068s Premium DeskPhone, and 8078s Premium Desk-
Phone sets. 4 types of skins are available. Default value is
0.
1. Configure the parameter to one of the following
number: 1, 2, 3, 4
2. Reboot the set to validate your modifications
The configuration is registered and sent to the terminal.
When the parameter is set to a value other than 0, skin se-
lection is not available from the phone set user menu.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 44/382

Chapter 2 IP deskphones

Backlight Timer Determines for how long the screen is fully lit when it goes
back to idle.
Default and minimum value: 300 (in seconds).
Maximum value: 14400.
It is necessary to reset sets after the modification of this
parameter.

Hide IP Parameters menu As of R11.2, this parameter determines whether the set IP
address is hidden for the end user consulting the set
menu: Settings > Options
Default value: False

USB Boost Charging As of R12.0, this parameter is available for 8018 Desk-
Phone sets and 80x8s Premium DeskPhone sets only.
These sets provide a USB connector which allows charg-
ing of devices such as smartphones. A boost enables a
quicker charging of phones and tablets. But boost charging
requires more power consumption than normal USB charg-
ing in case of PoE.
• Disable: Normal USB charging (default value)
• Enable: Boosted USB charging
• AUTO: Reserved for future use (=disable if set)
Reboot the set to validate your modifications.

USB Connectivity 80x8s Premium DeskPhone sets have a provision of USB

Connectivity (for peripherals such as headsets and head-
phones, for instance).
• NO: USB Connectivity is disabled
• YES: USB Connectivity is enabled
The device can be connected on USB device.
Reboot the set to validate your modifications.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 45/382

Chapter 2 IP deskphones

Ambient Light Sensor Forced Ac- The Ambient Light Sensor is available on 8088 Smart
tive DeskPhone and 80x8s Premium DeskPhone sets. It is
mainly used for energy saving. When this parameter is
configured in OmniPCX Enterprise, it cannot be disabled
by the end user.
Configure the parameter to one of the following:
• Modifiable by ULM: the default value defined in the set
for brightness is used. This value can be modified using
the User Local Menu (ULM) on the set.
• Disable: the brightness is modulated in manual way by
user setting. All light emitting devices brightness are
synchronized.
• Enable: the brightness of the LEDs are adapted
according to the current ambient brightness. The user
can change the brightness manually even if the
parameter is activated.

Back Logo LED The ALE International logo on the back of the 8058s Pre-
mium DeskPhone, 8068s Premium DeskPhone and 8078s
Premium DeskPhone sets includes a LED indicating the
call status:
• The LED is lit white: the phone set is idle
• The LED blinks blue: the phone set is ringing
• The LED is lit blue: the phone set is in communication
This parameter enables to turn on or off the LED:
• Modifiable by ULM: the LED can be turned on or off
from the User Local Menu (ULM) of the phone set
• Disable: the LED is turned off
• Enable: the LED is turned on
When this parameter is configured in OmniPCX Enterprise,
it cannot be enabled or disabled from the phone set (ULM).

Private store URL For future use. Format is either:

• The server name, port and access path
• The server IP address, port and access path

Proxy for software update Depending on client configuration, a proxy may be

necessary for software upgrade.
• The server name, port and access path
• The server IP address, port and access path
3. Confirm your entries
Note:
If Alcatel-Lucent 8&9 Series > 8&9 Series COS > Phone COS > Display Main Page on off-hook option is set,
the Speed dial screen is displayed when going off hook from idle state.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 46/382

Chapter 2 IP deskphones

2.1.4.1.6 Configuring names in non-Latin characters

Up to 8 languages can be managed. These languages correspond to the languages configured for the
whole system (for more information, refer to the Voice guides and music-on-hold section of the
document [1]).
Every set in the system has a Language ID (configured in system administration and/or the set user)
which corresponds one of the languages available in the system.
Note:
There is no control at system management level on the languages available for each set. All languages are
authorized, but not all character types are available on all sets. For example, the system allows the Language ID
attribute of the User object for a 4018 set to refer to Chinese, although this set cannot display Chinese characters.
The set display will use one of its available character types instead.
To allow input of non-Latin characters on a set, authorize the appropriate input method in the Phone
Class of Service (see Configuring Phone COS on page 40).
Note:
You must use the OmniVista 8770 application to configure UTF-8 names. Non-Latin characters are displayed
as ??? in mgr.
2.1.4.1.6.1 Configuring language compatibility
The compatibility configuration below determines whether a set in a language using one set of fonts
(e.g. Latin for English) can view other fonts (e.g. Greek).
Example:
English speaking users may not be familiar with Greek fonts and would rather see Greek user's name in Latin
characters. The system administrator determines, per available set types, whether sets in English will display
Greek fonts.
1. Select: Alcatel-Lucent 8&9 Series > Language Type Compatibility
2. Review/modify the following attributes

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 47/382

Chapter 2 IP deskphones

Set Type Select the desired option among:

• 401x: for Alcatel-Lucent IP Touch 4018
phone Extended Edition and Alcatel-Lucent
4019 Digital Phone sets
• Others: for Alcatel-Lucent IP Touch
4028/4038/4068, Alcatel-Lucent 4029/4039
Digital Phone, 8028/8038/8068, 8088 Smart
DeskPhone , 8028s/8058s/8068s/8078s or
8029/8039 sets

Language type According to the set type selected above, select

the type of fonts among:
• Latin
• Cyrillic
• Chinese (where available)
• Japanese (where available)
• Korean (where available)
• Greek (where available)
• Arabic (where available)
• Hebrew (where available)
• Thai (8028/8038/8068, 8088 Smart
DeskPhone, 8028s/8058s/8068s/8078s and
8029/8039 sets only)
• All

Display Language 0 Displays the first language available in the sys-

tem

Compatibility Select YES to make the set compatible with oth-

er fonts.
Example:
If the selected instance is Cyrillic, on user sets where
the display language is English, names in Cyrillic
(configured Configuring long or non-Latin character
user names on page 48) are displayed in Cyrillic
fonts.

Display Language x Proceed with the other languages to use as per

Language 0 above
Compatibility
Note:
If your system is in an ABC-F network, ensure system
languages are defined identically for each network
node.

3. Confirm your entries

2.1.4.1.6.2 Configuring long or non-Latin character user names
1. Select: Users
2. Review/modify the following attributes

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 48/382

Chapter 2 IP deskphones

Directory name Enter the user name in standard Latin charac-

ters

Directory First name Enter the user first name in standard Latin char-
acters

UTF-8 Directory Name Enter the user name in specific fonts (other than
Latin), or Latin long name
Reminder:
No font other than Latin can be entered via the mgr
tool. Use the OmniVista 8770 applications instead

UTF-8 Directory First Name Enter the user first name in specific fonts (other
than Latin), or Latin long name
Reminder:
No font other than Latin can be entered via the mgr
tool. Use the OmniVista 8770 applications instead

3. Confirm your entries

2.1.4.1.6.3 Configuring long or non-Latin character speed dialing names
1. Depending on the type of speed dialing number, select on of the following:
• Speed Dialing > Direct Speed Dialing Numbers > Direct SpdDl No. Pref.
• Speed Dialing > Spd Dl Numbers by Range > Speed Dialing Number
2. Review/modify the following attributes

Direct Speed Dial No. Prefix (or Speed Dial- Enter the speed dialing number to create (or
ing No. if speed dialing number by range modify)

Call Number Enter the actual number to dial

Directory name Enter the user name in standard Latin charac-

ters

Directory First Name Enter the user first name in standard Latin char-
acters

UTF-8 Directory Name Enter the user name in specific fonts (other than
Latin), or Latin long name
Reminder:
No font other than Latin can be entered via the mgr
tool. Use the OmniVista 8770 applications instead

UTF-8 Directory First Name Enter the user first name in specific fonts (other
than Latin), or Latin long name
Reminder:
No font other than Latin can be entered via the mgr
tool. Use the OmniVista 8770 applications instead

3. Confirm your entries

2.1.4.1.6.4 Configuring long or non-Latin character entity Names
1. Select: Entities

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 49/382

Chapter 2 IP deskphones

2. Review/modify the following attributes

Entity Number Enter the entity number to create or modify

Name Enter the entity name in standard Latin charac-

ters

UTF-8 Name Enter the entity name in specific fonts (other

than Latin), or Latin long name
Reminder:
No font other than Latin can be entered via the mgr
tool. Use the OmniVista 8770 applications instead

3. Confirm your entries

2.1.4.1.6.5 Configuring long or non-Latin character trunk group names
1. Select: Trunk Groups
2. Review/modify the following attributes

Trunk Group ID Enter the ID number for this trunk group

Trunk Group Name Enter the standard name for this trunk group (up
to 10 characters)

UTF-8 Trunk Group Name Enter the name in specific other than Latin font,
or up to 20 characters if in Latin font
Reminder:
No font other than Latin can be entered via the mgr
tool. Use the OmniVista 8770 applications instead

3. Confirm your entries

2.1.4.1.6.6 Configuring non-Latin character programmed key names
You can enter names when you program keys on the set. You can also configure long or non-Latin
character names for programmed keys using the OmniVista 8770 application.
1. Select Users > Progr.Keys
2. Review/modify the following attributes:

Directory Number Enter the directory number of the set.

Key No. Enter the number of the key to be configured.

Function Select Programmed

Mnemo (Pocket,Mobile,4040,8&9) Enter a description for the function to be dis-

played next to the key in Latin characters.

UTF-8 Mnemo (8&9 Series) Enter a description for the function to be dis-
played in non-Latin characters next to the key.
Note:
You must use the OmniVista 8770 application to enter
or display non- Latin characters for this attribute. Non-
Latin characters are displayed as ??? in mgr.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 50/382

Chapter 2 IP deskphones

3. Confirm your entries

2.1.4.1.6.7 Configuring non-Latin character manager/assistant key names
You can configure non-Latin character names for the manager key, the assistant key, and a secondary
assistant. For more information, refer to the section Manager/assistant sets section of the document
[3].
2.1.4.1.6.8 UTF–8 resolution in an ABC-F network
1. Select System > Other System Param > Network Parameters > Enable UTF8 in ABCF network
2. Review/modify the following attribute

System Option Select Enable UTF8 in ABCF network

Enable UTF8 in ABCF network • True (default value): UTF8 names are
transmitted to other nodes of the ABCF
network
• False: UTF8 names are not transmitted to
other nodes of the ABCF network
3. Confirm your entry
4. To allow UTF-8 resolution between subnetworks, select Translator > Network Routing Table
5. Review/modify the following attribute

Network number Select the appropriate network number

Enable UTF8 name sending Select True to enable UTF-8 resolution

6. Confirm your entry
2.1.4.1.7 Timers
There are specific timers for Premium DeskPhone and Alcatel-Lucent 8/9 series sets:
• Timer No. 325: display of audio and internal application confirmation:
This popup is displayed in the following cases:
• Activation/deactivation of an internal application (forward, mail, appointment, redial, dial by
name, programming, etc.)
• Activation of audio modification (headset (except when starting or answering a call), hands free
(except when starting or answering a call), group listening, mute)
• Timer No. 331: display of the popup window indicating an incoming call
• Timer No. 332: display of the confirmation popup
• Timers No. 356 (default value 20 seconds) and No. 357 (default value 60 seconds): used by the
Input Method Editor (IME) for input of non-Latin characters in Dial by name. Both timers close the
IME due to no user activity. When Timer No. 356 expires, the previous input is saved. When Timer
No. 357 expires, the previous input is cleared. The value of Timer No. 356 should be less than the
value of Timer No. 357.
• Timer No. 371: automatic display of the Perso page if no action is done during this timer.
To modify the duration of these timers:
1. Select System > Timers
2. Review/modify the following attributes:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 51/382

Chapter 2 IP deskphones

Timer No. Enter the No. of the timer to modify

Timer units Modify as needed.

3. Confirm your entry

2.1.4.2 Prefixes and suffixes

Most telephone services, such as for example call transfer or conferences, can be activated by a prefix
(or suffix).
The rights for users to access services is determined in their class of service.
On sets, services are easily accessible via programmed keys and menu options (softkeys).
Some prefixes cannot be dialed on set because they are available by settings menu or by direct keys
(language, contrast programming, no ringing ) or because they have no meaning for sets (personal
directory programming on analog station, personal directory use on analog station).
Note:
To display the list of available prefixes in the system, use the LISTRAD command.

2.1.4.3 Configuring keys

System configuration for Premium DeskPhone additional key modules is very similar to the
configuration of additional key modules for Alcatel-Lucent IP Touch 4028/4038/4068, or Alcatel-Lucent
4029/4039 Digital Phone sets.
However, additional modules for these sets are not compatible with 3G sets and 3G additional modules
are not compatible with sets of the previous generation.
Note:
8088 Smart DeskPhone sets running in NOE mode do not support additional key modules. They include a virtual
key module available on screen (equivalent to a Smart Display Module).
2.1.4.3.1 Declaring an additional key module
1. Select: Users
2. Review/Modify the following attributes:

Directory Number Enter the directory number of the set

Add On Module 1 Select the appropriate additional key module

Add On Module 2
Add On Module 3
3. Confirm your entries
2.1.4.3.2 Key mapping and programming
Piano sensitive keys are numbered G1 to G9, from left to right.
Keys can be programmed directly on the set or in system configuration.
They are numbered as follows:
• Personal home page keys: 1 to 7
• F1 and F2 keys: 73 and 74
• Additional module keys: from 75 onwards
Keys are numbered in pairs from left to right, then from top to bottom (except for 10-key and Smart
Display Module, which are numbered from top to bottom).

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 52/382

Chapter 2 IP deskphones

To program a key from the system:

1. Select Users > Progr.Keys
2. Review/Modify the following attributes:

Directory Number Enter the directory number of the set

Progr.Keys Enter the number of the key

Function Select the function of your choice (select Programmed to manually enter
the number dialed when the key is pressed)

Mnemo(Pocket,Mo- Enter the name to display next to the key on the LCD display (for keys on
bile,4040,IPTouch) the Perso tab or on a Smart Display Module)

UTF-8 Mnemo ( Al- If desired, enter the name in non-Latin characters to display next to the key
catel-Lucent 8&9) on the LCD display (for keys on the Perso tab or on a Smart Display Mod-
ule)

Locked Select YES to prevent users from modifying the contents of this key from
their set
3. Confirm your entries

2.1.5 Configuration examples

2.1.5.1 Overview
For the following IP network:

GD

IP-PHONE Call Server Router

10.253.253.3 10.253.253.5 10.253.253.99

The client IP network manager has provided the following information:

• The number of the subnetwork and its mask (10.253.253.0 and 255.255.255.0).
• The addresses available for the Com Server and the GD (10.253.253.3 and 10.253.253.5).
• Router address 10.253.253.99.
• The range of free numbers for IP phones (10.253.253.50 to 10.253.253.69).
The IP phone directory number is 6853.
In addition, we want the PCX to act as DHCP server and transmit the lanpbx.cfg file.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 53/382

Chapter 2 IP deskphones

2.1.5.2 Declaring a user

1. Select: Users
2. Review/modify the following attributes:

Directory Number 6853

Shelf Address 255

Board Address 255

Equipment Address 255

Set Type IP Touch 4038

Leave the other parameters at their default values

3. Confirm your entries
4. Select: Users > TSC IP User
5. Review/modify the following attributes:

Directory Number 6853

Set Type IP Touch 4038 (display)

Voice Coding Algorithm Default

Terminal Ethernet Address Entered automatically after IP phone initialization

IP Address Entered automatically after IP phone initialization

IP Domain Number 0 (display)

Use of volume in system Yes

6. Confirm your entries

2.1.5.3 Configuring the DHCP Server

Configuring the DHCP Server on the OmniPCX Enterprise is performed via PCX management tools.
2.1.5.3.1 Enable the DHCP Server:
1. Select: DHCP Configuration
2. Review/modify the following attributes:

Configuration DHCP Server

Terminals delivered by ALE Yes (the devices handled are delivered by ALE International)
International only
3. Confirm your entries
2.1.5.3.2 Declaring the Local Subnetwork
1. Select: DHCP Configuration > CPU Main Subnetwork
2. Review/modify the following attributes:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 54/382

Chapter 2 IP deskphones

Subnet address 10.253.253.0

Subnet mask 255.255.255.0

Broadcast address 10.253.253.255

Default router address 10.253.253.99

TFTP Server address 10.253.253.3

3. Confirm your entries
2.1.5.3.3 Adding a Range of Free Numbers for IP Phones
1. Select: DHCP Configuration > CPU Main Subnetwork > IP Address Range (local subnet)
2. Review/modify the following attributes:

First address in range 10.253.253.50

End of address range 10.253.253.69

3. Confirm your entries
2.1.5.3.4 Configuring Classes
IP Phones use two classes.
• TSC-IP for V1, V1S, and V2 (e-Reflexes) sets.
• NOE for IP Touch sets.
The classes are created by default. A TFTP server address must be entered.
1. Select: DHCP Configuration > Classes
2. Review/modify the following attributes (this example is for NOE class):

Name NOE

Vendor ID alcatel.noe.0

TFTP Server address This section can be left empty

Default lease time (mn) 60

Max lease time (mn) 1440

Configuration file This section can be left empty

3. Confirm your entries
2.1.5.3.5 Applying Modifications
Confirm the modifications by selecting DHCP Configuration > Apply modifications.
Note:
If netadmin -m is running, you must exit netadmin before applying the modifications. In this case a warning
message is displayed.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 55/382

Chapter 2 IP deskphones

2.1.5.4 Declaring the TFTP Server for the lanpbx.cfg file

In this case, no declaration is required: by default, the PCX declares itself as TFTP server for the
lanpbx.cfg file.

2.1.5.5 Registering the Set

Perform the following operations:
1. Connect the IP phone to the network.
2. Power up the IP phone (connect the power supply).
3. In response to the question "directory number?", enter the directory number of the set.
4. In response to the question "secret code?", enter the secret code of the set (the default secret code
is "0000").

2.1.6 Maintenance
2.1.6.1 “ippstat” Command
For the ippstat command, see: Operation.

2.1.6.2 lanpbxbuild and lanpbxmipt commands

These commands are used to create, modify or delete the lanpbx.cfg and lanpbx_mipt.cfg files.
These commands are described: Operation.

2.1.6.3 “termstat” command

The command is run either by specifying the directory number or equipment number.
Example:
(1)PCX56> termstat d 3017

+COUPLER_INFORMATIONS -------------------------------------------------------+
| Logic coupler type : CPL_UA |
| MAO coupler type : UA_FICTIF |
| Coupler state : IN SERVICE |
+-------------------------------------------------(PRESS ANY KEY TO CONTINUE)+

[1] : Device features.

[2] : Forward informations.
[3] : Subdevice informations.
[4] : Demi-com informations.
[5] : Reset the device.
Your choice [1-5, q for quit]: 1

+UA TERMINAL ----------------------------------------------------------------+

| Device: 19-3-8-0 Neqt: 270 |
| Logic number: 0 |
| Terminal type: NOE_C:IP PHONE Locked: No |
| State: IN_SERV |
| Directory number: 13005 Set type: NOE_C |
| Associate directory: 13005 PIN: 0000 |
| Overflow validate: No Multiline set: No |
| PBX group number: none PBX state: OUTSIDE |
+-------------------------------------------------(PRESS ANY KEY TO CONTINUE)+

This command gives information similar to that given for a standard UA set.

2.1.6.4 “getnoeversion” command

The "getnoeversion" command returns information about all the Alcatel-Lucent 8 series sets that are
declared on the node.
This information includes:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 56/382

Chapter 2 IP deskphones

• Status (in service or out of service)

• Type of set
• IP domain number (for Alcatel-Lucent 8 series sets)
• Serial number
• Hardware version
• Software version
As of R6.1.1, the presence (or absence) of Bluetooth and additional key modules is detailed, as well as
the RAM/ROM of the set.
As of R7.0, localization and customization information is listed in the command result.
This command can be applied:
• To a specific set by using the set directory number. For example (in R7.0):
The command results are displayed directly on the maintenance console.

• To all the Alcatel-Lucent 8 series sets of the node. The results for the getnoeversion command are
stored in the file:
/DHS3dyn/mao/getnoeversion.txt
As of R6.1.1 the stored file is in .csv or .xml format, according to user choice.

2.1.6.5 “tradna” or ”tradeq” Commands

These commands give the match between directory number and device number.
> tradna 3017
Logic coupler type : CPL_UA
MAO coupler type : UA_FICTIF
Coupler state : IN SERVICE
Terminal state : IN SERVICE
Terminal type : IP PHONE
+----------------------------------------------------------------------------+
| Cry:Cpl:ac:term | neqt |nulog| typ term | dir nb | Out of service cause |
+----------------------------------------------------------------------------+
| 19 3 0 8 | 0270 | 0| NOE_C| 13005 | . . . . . . . . . . |
+----------------------------------------------------------------------------+
|A: att_mserv, C: hs_defich, I: hs_isolauto, X: hs_isolman, T: hs_terdef |
|U: hs_usdef, P: hs_errparite, B: hs_bascul, Y: hs_cristisol, N: hs_inex |
+----------------------------------------------------------------------------+

2.1.6.6 “rstcpl” Command

This command is used to reset (reinitialize) a coupler. The specific IP phone feature of this command is
that virtual devices cannot be reset.

2.1.6.7 Reboot on Flashing Problem (only on TSC-IP)

If a problem occurs in certain phases of binary loading, the IP phone refuses to start and cannot be
called. To resolve this blockage, the TSC-IP can be rebooted from its backup partition.
To do this, press the reset button of the TSC-IP during power up.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 57/382

Chapter 2 IP deskphones

-> -> -> -> -> -> -> -> -> -> -> -> -> -> -> -> -> -> -> ->

Figure 2.7: Set Display During Flashing Reset

2.1.6.8 SIP Survivability Supervision

• The ippstat dualsip command displays the list of SIP compatible IP Touch sets:
• Which are in IP domains where SIP survivability is not enabled
• Which are in IP domains where SIP survivability is enabled
• The ippstat d <mcdu> command displays the list of SIP parameters of a set.
• To display the operating mode of a set as regards SIP survivability:
1. Select Users > Dynamic State User
2. Consult the SIP Survivability Mode value

2.1.6.9 Incidents (Error Messages)

2.1.6.9.1 Error 377
This error is transmitted following an initialization failure. The additional information gives details on the
type of error:
• 0 Initialization timeout expired.
• 1 Lack of resources.
• 2 Incorrect set type.
• 3 MAC address table saturation.
• 4 Impossible to establish signaling.
• 5 Signaling error.
This error concerns the IP phone designated by its MAC address and its directory number.
For further information on this error, enter incinfo FR0 377
2.1.6.9.2 Error 378
This error is transmitted to advise of signaling status:
• 0 IP coupler not initialized.
• 1 MAC address already assigned.
• 2 IPv6 signaling not supported.
• 3 Lack of coupler resources.
• 4 No link.
• 5 Link already established.
• 6 Network congestion or remote user not connected.
• 7 IP coupler internal error.
• 8 Link established.
• 9 Network error.
• 10 Access point not connected.
• 11 Access point disconnection, on access point request.
• 12 Disconnection on CPU request.
• 13 INT-IP internal error.
• 14 INT-IP not connected or reinitializing (reset in progress).
This error concerns the IP phone designated by its MAC address and its directory number.
For further information on this error, enter incinfo FR0 378

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 58/382

Chapter 2 IP deskphones

2.1.6.9.3 Error 380

Error 380 is sent to the PCX by an IP phone.
This error indicates that the IP phone designated by its MAC address and its directory number has not
obtained renewal of its IP address. It will reinitialize to obtain a new one.
2.1.6.9.4 Error 438
Incident 438 occurs when a parameter mandatory for SIP survivability is missing for a set initialization.
The incident indicates the involved set and the missing parameter.
2.1.6.9.5 Error 743
This error is transmitted at the start of a download operation to the IP phone designated by its IP
address.
2.1.6.9.6 Error 744
This error is transmitted at the end of a download operation to the IP phone designated by its IP
address.
2.1.6.9.7 Error 745
This error is transmitted following a download error to an IP phone designated by its IP address.

2.1.7 Relocation and Replacement of an IP-Phone

2.1.7.1 Overview
The aim of this document is to provide a summary of the operations to be carried out to replace or
relocate an IP phone.
The difference between an IP phone and a standard wired set is that the IP phone is not connected to
PCX equipment. An IP phone is not recognized by its physical position, but by an identifier, its MAC
address (Ethernet). The association between the user (directory number, name, first name, etc.) and
the IP phone (Ethernet MAC address) is made when initializing the set. The advantage is that this
makes it easier to move the IP phone on the network.
Like all IP equipment, an IP phone has an IP address and may belong to a VLAN. Like all telephone
equipment, an IP phone is connected to a node.
The examples given in the first paragraphs assume that the following conditions are met:
• There is a DHCP server, internal or external, on which the IP address ranges are configured for the
IP phones.
• There is no VLAN configured on the network.
• The host node for the user remains the same.
The following paragraphs describe the operations to carry out in the event that these conditions are not
met.
If there is no DHCP server, see Registering the IP Address Manually on page 61.
If the VLANs are configured, see Configuring the VLAN Number on page 62.
If the host node changes, see Changing the Host Node on page 65.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 59/382

Chapter 2 IP deskphones

2.1.7.2 Relocating, Retaining the Same Set

Reminder (check with the system administrator)

The following conditions must be met:
• IP addresses are assigned by DHCP server.
• There is no VLAN to be configured.

1. Unplug the set.

2. Plug the set in (in its new location).
The set is automatically brought back into service.
Note:
If there is no DHCP server but the relocation is within the subnetwork, no action is necessary when the set is
brought back into service.
However, if you wish to change the IP telephony domain assigned to the set, the IP address for the set needs to be
modified. See the Overview.
If there is a change of subnetwork, see the Registering the IP Address Manually.

2.1.7.3 Relocating, with the Set Being Replaced by another of the Same Type

Reminder (check with the system administrator)

The following conditions must be met:
• IP addresses are assigned by DHCP server.
• There is no VLAN to be configured.

1. On the old set, enter the Set In/Out of service prefix, followed by the secret code.
2. There are two possible cases:
• The new set is not plugged in:
1. Plug the set in.
2. Let the set initialize. When requested on the set display, enter the directory number followed
by the secret code.
• The new set is already plugged in and displays Extn out of service:
1. Off-hook.
2. Enter the directory number followed by the secret code.

2.1.7.4 Replacing a Non-Operational Set with another Set of the Same Type

Reminder (check with the system administrator)

The following conditions must be met:
• IP addresses are assigned by DHCP server.
• There is no VLAN to be configured.

1. If the set to be replaced is no longer operational, the prefix to put the set out of service cannot be
entered. In this case, an MAO management operation is necessary:
a. On the configuration tool, select: Users > TSC IP User
b. Review/Modify the following attribute:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 60/382

Chapter 2 IP deskphones

Terminal Ethernet Address Delete the Ethernet address, replacing it with ”“ (double in-
verted commas).
c. Confirm your entry
This puts the old set out of service.
2. Plug in the new set.
3. Let the set initialize. When requested on the set display, enter the directory number followed by the
secret code.

2.1.7.5 Relocating, with the Set being Replaced by a Different Type of Set

Reminder (check with the system administrator)

The following conditions must be met:
• IP addresses are assigned by DHCP server.
• There is no VLAN to be configured.

1. Put the old set out of service using one of the following two methods:
• If it is still operational, enter the Set In/Out of service prefix, followed by the secret code.
• If it is no longer operational,
1. On the configuration tool, select: Users > TSC IP User
2. Review/Modify the following attribute:

Terminal Ethernet Address Delete the Ethernet address, replacing it with ”“ (double
inverted commas).
3. Confirm your entry
2. On the configuration tool:
a. Select: Users
b. Review/Modify the following attribute:

Set Type Select the new set type.

c. Confirm your entry
3. Plug in the new set.
4. Let the set initialize. When requested on the set display, enter the directory number followed by the
secret code.

2.1.7.6 Registering the IP Address Manually

2.1.7.6.1 When Must the IP Address Be Configured Manually?
By default, an IP phone requests its IP parameters via a DHCP request (initialization in dynamic mode).
If there is no DHCP server, the set initialization stops at step 2.
In this case, the set must be configured in static mode, in other words, IP parameters must be
registered manually directly on the set.
Note:
Before configuring the set, an IP address for the set must be obtained from the network administrator. However, if
it is for a replacement or relocation on the same subnetwork, the old IP address can be retained.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 61/382

Chapter 2 IP deskphones

2.1.7.6.2 Consulting the IP Address on the Old Set

If you want to reuse the IP address of the old set, you can consult its IP parameters before putting it out
of service:
• Example for an Alcatel-Lucent IP Touch 4018 Phone or Alcatel-Lucent IP Touch 4068 Phone set:
1. Select the Menu page
2. Select Settings > Parameters > IP Parameters
3. View the information
2.1.7.6.3 Configuring the IP Address on the New Set
Static configuration is carried out using the set's supervisor menu. This menu can be accessed during
the set initialization phase.
• Alcatel-Lucent IP Touch 4008 Phone, Alcatel-Lucent IP Touch 4018 Phone, Alcatel-Lucent IP Touch
4028 Phone, Alcatel-Lucent IP Touch 4038 Phone,Alcatel-Lucent IP Touch 4068 Phone, 80x8
Premium DeskPhone and 80x8s Premium DeskPhone sets:
1. Plug in the IP phone.
2. Successively press the [i] and # keys.
Note:
For 80x8s Premium DeskPhone sets, you can press either * and # keys, or [i] and # keys to access the IP
parameters menu.
3. Select IP Parameters.
4. If the screen displays IP Mode Dynamic, press the corresponding dynamic key. the screen
should then display IP Mode Static.
5. Enter the following parameters:
• IP addr: Set IP address
• Subnet: Subnetwork mask
• Router: Router IP address
• TFTP1: TFTP server IP address (Call Server A in a duplicated Call Server configuration)
• TFTP2: TFTP server for Call Server B, in a duplicated configuration where the two Call
Servers are on different subnetworks
• VLAN information (see Configuring the VLAN Number on page 62)
6. Confirm by pressing the key (or the # key on an Alcatel-Lucent IP Touch 4008 Phone and
Alcatel-Lucent IP Touch 4018 Phone).
• 8088 Smart DeskPhone:
1. After startup, wait until the settings menu is available (from step 2 of initialization) and press the
Settings icon available at the bottom left of the set screen
2. Press Admin and enter an administrator password
3. Go to: Network > IP
4. Select the Static mode and configure the set IP parameters (for more information, see:
Commissioning the set)
5. Press the Home soft key to validate and exit settings

2.1.7.7 Configuring the VLAN Number

2.1.7.7.1 When Does the VLAN Number Need to Be Configured?
VLANs (Virtual Local Area Networks) are used to segment the IP network, in particular to limit
interactions between voice equipment and data equipment.
Check with the system administrator to find out whether they are used.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 62/382

Chapter 2 IP deskphones

If VLANs are used, the AVA (Automatic VLAN Assignment) function of the OmniPCX Enterprise DHCP
server is used to automatically assign a VLAN number to the IP phones during initialization. If this
function is implemented, no action concerning the VLAN number needs to be carried out. The VLAN
number is automatically sent to the IP phone during the initialization phase, see: Automatic VLAN
Assignment (AVA).
If the AVA function is not implemented:
1. For a relocation within the same subnetwork while retaining the same set, no action is necessary.
2. For a relocation to another subnetwork or to change set, the VLAN number must be configured
manually on the set.
As of R6.1, strict VLAN can be configured on IP Touch sets (see: Strict VLAN).
2.1.7.7.2 Configuring the VLAN Number
The VLAN number is configured using the set's supervisor menu. This menu can be accessed during
the set initialization phase.
• To configure VLAN number on an Alcatel-Lucent IP Touch 4018 Phone or Alcatel-Lucent IP Touch
4068 Phone set:
1. At set initialization, successively press the [i] and # keys to access the supervisor menu.
2. Select IP Parameters, then scroll down the list using the navigation key.
A screen as the example below is displayed:

IP Parameters

CPU2

Use VLAN

VLAN ID

Strict VLAN

3. Select the Use VLAN box by pressing the corresponding dynamic key.
4. Enter the VLAN number below it.
5. If required, select the Strict VLAN box by pressing the corresponding dynamic key.
6. Confirm by pressing the key at the top left.
Note:
In all cases, ensure that the port of the switch on which the IP phone is connected is configured correctly.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 63/382

Chapter 2 IP deskphones

2.1.7.8 Summary Diagrams

Putting the old set out of

yes Is old set no

operational?
service

Dial set in/out of Delete Ethernet

service prefix + address in the user
secret code parameters
Disconnection/

Disconnect the old set

Connection

Connect the new set

no
DHCP server?
IP configuration

yes
Manually configure the IP
parameters

no VLANs configured on the

network?
VLAN configuration

yes
no
AVA implemented ?

yes
Manually configure the
VLAN number
Set recognition
through secret
code

Dial directory number +

secret code

Set operational

Figure 2.8: Replacing an IP Phone

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 64/382

Chapter 2 IP deskphones

Disconnect the set

Disconnection/Connection

Connect the set in its new

position

Relocation to another no
subnetwork?
yes

no
DHCP server?
IP configuration

yes
Manually configure the IP
parameters

no VLANs configured on the

network?
VLAN configuration

yes
no
AVA implemented?

yes
Manually configure the
VLAN number

Set operational

Figure 2.9: Relocating an IP Phone

2.1.7.9 Changing the Host Node

If you want to modify the host node for the set, MAO management operations are necessary.
1. Put the old set out of service using one of the following two methods:
• If it is still operational, enter the Set In/Out of service prefix, followed by the secret code.
• If it is no longer operational, on the configuration tool:
1. Select: Users > TSC IP User
2. Review/Modify the following attribute:

Terminal Ethernet Address Delete the Ethernet address, replacing it with ”“ (double
inverted commas).
3. Confirm your entry
2. Modify the host name.
a. Select: Users

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 65/382

Chapter 2 IP deskphones

b. Review/Modify the following attribute:

Host Node (Location Node) Enter the number of the new node.
c. Confirm your entry
This operation transfers the subscription data for the set to the new node via the distribution service,
which therefore needs to be enabled.
3. Plug the set in.
4. Let the set initialization phases take place, then, when the request is displayed, enter the directory
number followed by the secret code.

2.1.7.10 Links
• Overview
• Overview
• Detailed description
• Overview

2.1.8 VoIP Technical Characteristics for 8 series

2.1.8.1 Physical Characteristics

table 2.4: Physical Characteristics

Alcatel-Lucent IP Alcatel-Lucent IP Comments

Touch 4028/4038/4068 Touch 4028/4038/4068
phone Extended Edi-
tion

Ethernet Interface 10/100Mb Half/Full Du- 10/100/1000Mb Half/ Auto-sensing: adapta-

plex auto-sensing + au- Full Duplex auto-sens- tion to the equipment to
to-negotiation ing + auto-negotiation which the IP phone is
connected
Auto-negotiation: nego-
tiation 10/100/1000 and
Half/Full

IP phone built on inte- Yes Yes

grated LAN switch

Additional Ethernet In- Yes Yes

terface (for IP phone
cascading PC)

Maximum number of 1 1 Number of sets which

cascading can be connected be-
hind an IP-Phone

Compatibility with Om- Yes Yes

niPower Patch Panel

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 66/382

Chapter 2 IP deskphones

Alcatel-Lucent IP Alcatel-Lucent IP Comments

Touch 4028/4038/4068 Touch 4028/4038/4068
phone Extended Edi-
tion

Compatibility with Pow- Yes Yes

er hub 802.3af for re-
mote feeding

Power Classification Class 2 IP Touch 4068 phone Class 2: 3,84-6,49 W

extended edition: class
Class 3: 6,49 to 12,95
3
W
Other IP Touch sets:
class 2

LLDP-MED PoE Man- Yes Yes

agement

Ethernet Protocol Ethernet (RFC 894), Ethernet (RFC 894), Be careful if PC Novell
802.3 802.3 e.g. is connected which
by default uses an other
protocol

2.1.8.2 Call Control Protocol

table 2.5: Call Control Protocol

Alcatel-Lucent IP Alcatel-Lucent IP Comments

Touch 4028/4038/4068 Touch 4028/4038/4068
phone Extended Edi-
tion

NOE proprietary proto- Yes Yes

col encapsulated into IP

Signalling protocol En- Yes Yes From IP Touch Release

cryption 3.x

SIP protocol Yes Yes SIP survivability on IP

Touch extended edition
sets as ofOmniPCX En-
terprise R9.0.
* SIP stand-alone on Al-
catel-Lucent IP Touch
4008/4018 phone Ex-
tended Edition as of
OmniPCX Enterprise
R9.1.

Compatibility with Net- No No Use preferably VPN

work Address Transla- tunneling
tion (NAT)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 67/382

Chapter 2 IP deskphones

Alcatel-Lucent IP Alcatel-Lucent IP Comments

Touch 4028/4038/4068 Touch 4028/4038/4068
phone Extended Edi-
tion

UDP port range 0-65535 0-65535

2.1.8.3 Voice Processing and Management

table 2.6: Voice Processing/Management

IP Touch 4028/4038/ IP Touch 4028/4038/ Comments

4068 4068 phone Extended
Edition

RTP/RTCP support Yes Yes

SRTP Encryption Yes Yes From IP Touch Release 3.x

RTP Port range 0-65535 0-65535 Configurable

Codec G711 Yes Yes Minimum framing = 10 ms

(but depends on the capa-
bilities of the IP-PCX)

- A-Law Yes Yes

- µ-Law Yes Yes

Codec G722 No Yes Minimum framing = 20 ms

(but depends on the capa-
bilities of the IP-PCX)

Codec G723.1 Yes Yes Minimum framing = 30 ms

(but depends on the capa-
bilities of the IP-PCX)

Codec G729A Yes Yes Minimum framing = 10 ms

(but depends on the capa-
bilities of the IP-PCX)

Jitter compensation mech- Yes Yes Dynamic buffer of 12 pack-

anism ets maximum
The maximum size of the
dynamic (i.e. adaptive) jitter
buffer is 300 ms

Voice Activity Detection

(VAD)

Silence suppression (in

transmission)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 68/382

Chapter 2 IP deskphones

IP Touch 4028/4038/ IP Touch 4028/4038/ Comments

4068 4068 phone Extended
Edition

- G711 No No

- G722 No No

- G723.1 Yes Yes

- G729A Yes Yes

Comfort Noise Generation

(in reception)

- G711 Yes Yes

- G722 No Yes

- G723.1 Yes Yes

- G729A Yes Yes

Echo cancellation Yes Yes

Echo cancellation maxi- 100ms 100ms

mum depth

Gain switching Yes Yes

Support of direct RTP Yes Yes

flows

Tone generation All tones generated All tones generated by By configuration, can be
by the set the set managed by the IP-PCX

DTMF via UA/NOE signal- Yes Yes

ling

DTMF via RFC 2198 Yes Yes

DTMF via RFC 2833 Yes Yes

Voice guides and music By the IP interface By the IP interface

generation board board

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 69/382

Chapter 2 IP deskphones

2.1.8.4 Quality of Service (QoS)

table 2.7: Quality of Service

IP Touch IP Touch Comments

4028/4038/ 4068 4028/4038/ 4068
phone Exten-
ded Edition

Level 3 QoS: IP TOS/Diff-

Serv

- Tagging RTP/RTCP pack- Yes Yes Tagging occurs only after

ets the initialization of the IP-
Phone when the tagging in-
formation has been re-
ceived by the system.

- Tagging signalling pack- Yes Yes Traffic like SNMP, DHCP,

ets TFTP, telnet etc. is not tag-
ged.

Level 2 QoS: Vlan-Id

(802.1Q)

- Tagging RTP/RTCP pack- Yes Yes

ets

- Tagging signalling pack- Yes Yes

ets

- Static Vlan-ID configura- Yes Yes Through the MMI of the set
tion in the Phone

Level 2 QoS: Priority

(802.1P)

- Tagging RTP/RTCP pack- Yes Yes Tagging occurs only after

ets the initialization of the IP-
Phone when the tagging in-
formation has been re-
ceived by the system.

- Tagging signalling pack- Yes Yes Traffic like SNMP, DHCP,

ets TFTP, telnet etc. is not tag-
ged.

Tagging of frames from PC No No

Priority to voice frames Yes Yes Through adequate VLAN

against PC frames management

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 70/382

Chapter 2 IP deskphones

IP Touch IP Touch Comments

4028/4038/ 4068 4028/4038/ 4068
phone Exten-
ded Edition

Priority modification of PC No No
tagged frames

PC does not receive uni- Yes Yes

cast traffic (voice,…) from
IP-Phone

IP-Phone does not receive No No

broadcast and multicast
traffic from PC

IP-Phone does not receive Yes Yes

unicast data from PC

Broadcast/multicast storm Yes Yes

protection

2.1.8.5 Support Functions

table 2.8: Support Functions

IP Touch IP Touch Comments

4028/4038/ 4068 4028/4038/ 4068
phone Exten-
ded Edition

Configuration of the Ether- Yes Yes * Through the MMI of the IP-
net Interfaces (IP-Phone Phone
port and PC port): 10/100,
* The 1000 Mbit/s rate is
Half/Full, Autosensing
available on Alcatel-Lucent
IP Touch 4028/4038/4068
phone Extended Edition
sets in auto-negotiation
mode and cannot be forced
through the MMI.

Static IP address manage- Yes Yes Through the MMI of the set
ment (IP@, Netmask, de-
fault Gateway,…)

Integrated DHCP client for Yes Yes

dynamic IP address alloca-
tion (IP@, Netmask, de-
fault gateway,…)

Authentication 802.1x Yes Yes From version 4.0

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 71/382

Chapter 2 IP deskphones

IP Touch IP Touch Comments

4028/4038/ 4068 4028/4038/ 4068
phone Exten-
ded Edition

Automatic VLAN Assign- Yes Yes

ment through DHCP

Automatic VLAN Assign- Yes Yes From OmniPCX Enterprise

ment through LLDP R9.1.

Integrated TFTP client for Yes Yes

software download of the
set

Keep-alive mechanism Yes Yes Can be deactivated for re-

with IP-PCX mote IP-Phones e.g. in
case of IP connectivity es-
tablished on demand, e.g.
over ISDN links

Integrated SNMP agent No No

(MIB2)

SNMP traps No No

Support of DNS name Yes Yes In IP Touch Release 1.1

QoS tickets generation Yes Yes With some limitations (con-

secutive BFI,…) fixed in IP
Touch Release 1.1

Embedded HTTP server No No

Failure signalling to end Yes Yes message or beep to signal

user data network failure or con-
nection problem

Binaries download through Yes Yes

an external TFTP server

Spatial redundancy Yes Yes From IP Touch Release 2.x

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 72/382

Chapter 2 IP deskphones

2.2 8018 DeskPhone

2.2.1 Ergonomics of the 8018 DeskPhone set
2.2.1.1 Set description
2.2.1.1.1 Phone layout
Set screen Soft keys

Fixed keys

Programmable
Dialing keypad keys

Piano sensitive keys

Headset port

Figure 2.10: 8018 DeskPhone set layout

2.2.1.1.2 Audio, handsets, hands free and headset

The 8018 DeskPhone is equipped with a USB headset
It offers narrow band audio qualities.
It comes in its standard version with a comfortable corded handset.
It works in hands free mode at the user request.
2.2.1.1.3 Screens
The 8018 DeskPhone display is a black and white graphical display of 50 by 128 pixels with white
backlight.
2.2.1.1.4 Keys
2.2.1.1.4.1 Dialing keypad
On 8018 DeskPhone, this dialing keypad is also used as alphabetical keyboard.
The selected character is changed with a short press on the key:

Press To input any of (in this order):

1 1 space | -

2 2abcABC

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 73/382

Chapter 2 IP deskphones

Press To input any of (in this order):

3 3defDEF

4 4ghIGHI

5 5jklJKL

6 6mnoMNO

7 7pqrsPQRS

8 8tuvTUV

9 9wxyzWXYZ

0 0.,;:“?!

* *+%$/~&()[]=

# #@

2.2.1.1.4.2 Fixed keys

On all sets:

• Two fixed keys below the keypad (start call key): and stop call key: ) allow
to perform several actions
The start call key operates as follows:
• In SIP survivability mode (applicable for IP phones):
• When the terminal is idle, a short press triggers the display of a dial out list on the screen
(same action as a long press on the redial key)
• When there is an incoming call, pressing the start call key puts the set in hands free mode
• In NOE mode the start call key puts the set in hands free mode
The stop call key allows to end a call and ignore an incoming call
• A four-direction set of navigation keys (left, right, up, down) allows to select the different options
available on the screen. The OK button in the center of the navigation validates the selection.
• The c key to the left of the navigation allows to cancel the current action.
• Sensitive (piano) keys are located above the black grid of the lower part of the set.
Starting from the left to the right, they provide access to the following features:

• mute sound

• decrease sound volume

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 74/382

Chapter 2 IP deskphones

• increase sound volume

• put loudspeaker in service

• hold call. This is the default feature for F1 keys (but can be programmed with
another feature)

• transfer call. This is the default feature for F2 keys (but can be programmed with
another feature)

redial information

• information page (displayed on screen)

• messaging services
2.2.1.1.4.3 Integrated additional programmable keys
On 8018 DeskPhone sets, seven add-on keys are available with a digital label next to each one. The
first key triggers switching between numeric and alphabetical characters. The second key corresponds
to the F1 key on other sets and the third key corresponds to the F2 key on other sets.

2.2.2 Commissioning the 8018 DeskPhone

2.2.2.1 Declaring the set
Before commissioning an 8018 DeskPhone, ensure that the corresponding user has been declared in
the OmniPCX Enterprise.
To create a set and its corresponding user, refer to: Declaring an IP phone on page 28

2.2.2.2 Connecting the set

2.2.2.2.1 Physical connection
To connect the set to the OmniPCX Enterprise:
1. Plug the RJ45 cable into the set LAN connector, see: External interfaces on page 83
2. Connect the RJ45 cable to the LAN itself
3. If your set is not powered by PoE, plug the AC/DC external adapter to the set power supply
connector and connect the plug to the power supply
Once the set is connected and powered up, it automatically starts initializing.
2.2.2.2.2 Set initialization
By default, 80x8 Premium DeskPhone sets initialize dynamically and retrieve IP information
automatically.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 75/382

Chapter 2 IP deskphones

You can change this initialization mode. Static initialization is mandatory when the system does not use
a DHCP server.
To switch from dynamic initialization to static initialization and modify IP parameters:
1. Wait for the set to initialize and reach the end of the Network setup process, displayed on screen
2. Press simultaneously the star and pound keys
This displays IP settings
3. Use the soft key next to an option to modify the selection
4. Validate your modifications with the soft key next to the tick symbol
If 802.1x is used, additional configuration must be done on the phone at startup. For more information,
see: 802.1X Authentication - Configuring 802.1x on IP Touch Sets.
2.2.2.2.2.1 Requested IP parameters for static initialization
The following information must be provided for static initialization:
• IP address (set's address)
• Subnetwork mask
• Router address
• TFTP1 server address (see below for special configurations)
• TFTP2 server address (if needed, see below)
• Use VLAN: this box must be checked to enter a VLAN number
• VLAN number if necessary
• Strict VLAN if necessary (for more information, see: 802.1p/Q and VLAN - VLAN descriptionStrict
VLAN)
• TFTP port
The TFTP address(es) to enter may differ according to system configuration.
Please contact your system administrator for details on the configuration of your system.

Duplication Conditions TFTP1 Address TFTP2 Address

The Com Server is not duplicated Com Server main IP N/A

address (or Com Serv-
er physical address if
no main IP address has
been configured)

In a duplicated Com Server configuration where Com Server main IP N/A

the two Com Servers are on the same subnetwork address

In a duplicated Com Server configuration where Com Server A main IP Com Server B main IP
the two Com Servers are on different subnetworks address address

The TFTPb Address is used for the survivability mode (as of R12.0). It cannot be modified by the user.
It is automatically filled in with the backup IP address, i.e. the IP address of the rescuable Media
Gateway or the Passive Communication Server.
2.2.2.2.2.2 Requested parameters for dynamic initialization
With dynamic initialization, IP parameters are automatically sent by a DHCP server to the phone.
The following information must be provided for initial startup:
1. From the Registration window, enter:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 76/382

Chapter 2 IP deskphones

a. The set directory number

b. The set Password
If the set has already been initialized in the same configuration, there is no need to enter the directory
number and password again.
2.2.2.2.2.3 Deny of download
If the downloaded version is different from the version installed on the set (if, for instance a 80x8
Premium DeskPhone set is connected to an OmniPCX Enterprise before R10.1.1) and if the
downloaded binary is incompatible with the hardware/software, the terminal denies it and signals the
problem to the Communication Server.
The terminal requests binary files at each reset until a compatible binary is found. In the meantime, the
set operates as a 40x8 set.
Deny of download also applies to SIP binary.
2.2.2.2.2.4 lanpbx.cfg file download
When connected to the LAN, the set requests the lanpbx.cfg file from the configured TFTP
address(es).
This file contains one or more line. Each line corresponds to one node of the network and contains the
main IP address(es) of the Com Server(s) on which phones are declared.
At first initialization (no maincpu address stored in flash), the set selects the first line of the lanpbx.cfg
file.
On subsequent initialization (one or two maincpu address(es) stored in flash), the set controls that the
maincpu address(es) stored in flash corresponds to one line of the lanpbx.cfg file. If the address is
not the same, the set restarts as if it was its first initalization.
2.2.2.2.3 Binary file
Binary upgrade is silent and takes place in the background, once the OmniPCX Enterprise has
detected that an upgrade is required. Once the file is downloaded by the set and when the terminal is
idle, it resets and implements the new software.

2.2.2.3 Accessing the set from a console

8018 DeskPhones do not support telnet. Access must be via SSH.
At set initialization, the OmniPCX Enterprise sends a SET_PARAM_REQ message that contain the MMI
and the SSH passwords.

2.3 8028/8038/8068 Premium DeskPhones

2.3.1 Ergonomics of IP Premium DeskPhone sets
2.3.1.1 Set description
There are two types of Premium DeskPhone sets.
The available IP Premium DeskPhones are:
• 8078s Premium DeskPhone (delivered with a Bluetooth handset)
• 8068s Premium DeskPhone (delivered with a Bluetooth handset)
• 8068 Premium DeskPhone (delivered with a Bluetooth or corded handset)
• 8058s Premium DeskPhone
• 8038 Premium DeskPhone

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 77/382

Chapter 2 IP deskphones

• 8028 Premium DeskPhone/8028s Premium DeskPhone

80x8s Premium DeskPhone sets come with VPN support.
80x8s Premium DeskPhone provide enhanced services.
8028 Premium DeskPhone and 8028s Premium DeskPhone sets are very similar in their features and
capabilities.
8068 Premium DeskPhone and 8068s Premium DeskPhone sets are very similar in their features and
capabilities.
In the following paragraphs, all mentions to 8028s Premium DeskPhone and 8068s Premium
DeskPhone sets apply respectively to 8028 Premium DeskPhone and 8068 Premium DeskPhone sets
unless specified otherwise.
2.3.1.1.1 Phone layouts
Although there are differences in the aspect and operation of these sets, their layout is identical, but for
the screen and number of available soft keys.
Alarm LED

Touch screen

Dialing keypad

Bluetooth handset

Headset jack

Piano sensitive keys

Adjustable foot stand

Alt key
Space bar

Magnetic alphabetic keyboard

Figure 2.11: 8078s Premium DeskPhone set layout

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 78/382

Chapter 2 IP deskphones

Alarm LED
Soft keys
Set screen

Dialing keypad

Bluetooth handset

Headset jack Fixed keys

Piano sensitive keys

Adjustable foot stand

Alt key

Space bar

Magnetic alphabetic keyboard

Figure 2.12: 8068s Premium DeskPhone set layout

Alarm LED

Set screen Soft keys

Dialing keypad

Handset (corded)

Add-on modules

Fixed keys
Headset jack

Piano sensitive keys

Adjustable foot stand

Alt key

Space bar

Magnetic alphabetic keyboard

Figure 2.13: 8058s Premium DeskPhone set layout

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 79/382

Chapter 2 IP deskphones

Alarm LED

Set screen Soft keys

Dialing keypad

Handset (Bluetooth
or corded)

Fixed keys

Headset jack Piano sensitive keys

Adjustable foot
stand (0° to 60°)

Alphabetic keyboard
Alt key
Space bar

Figure 2.14: 8068 Premium DeskPhone set layout

Alarm LED

Set screen Soft keys

Dialing keypad

Corded handset

Fixed keys

Headset jack Piano sensitive keys

Adjustable foot
stand (0° to 60°)

Alphabetic keyboard
Alt key
Space bar

Figure 2.15: 8038 Premium DeskPhone

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 80/382

Chapter 2 IP deskphones

Alarm LED

Set screen Soft keys

Dialing keypad

Corded handset

Fixed keys

Headset jack Piano sensitive keys

Adjustable foot
stand (0° to 60°)

Alphabetic keyboard
Alt key
Space bar

Figure 2.16: 8028 Premium DeskPhone

2.3.1.1.2 Foot stand

All sets come with a 0° to 60° adjustable foot stand.
2.3.1.1.3 Audio, handsets, hands free and headset
All sets come with a standard 3.5 mm jack to plug a headset.
All sets offer narrow band audio qualities.
80x8s Premium DeskPhone sets with corded handsets offer super wide band audio qualities (except
for 8028s Premium DeskPhone).
G722 codec is set as the default codec for 80x8 Premium DeskPhone and 80x8s Premium DeskPhone
sets.
All sets come in their standard version with a comfortable corded handset.
They all work in hands free mode at the user's request. Refer to Configuring Phone COS on page 40
The 8068 Premium DeskPhone set can be equipped with a Bluetooth handset. When this is the case, a
Bluetooth charger interface is embedded in the set itself.
Note:
The Bluetooth handset with reference BTHS-2, also available for Alcatel-Lucent IP Touch 4068 Phone sets, is
compatible with the 8068 Premium DeskPhone set.
For a full description of the Bluetooth handset, see: Bluetooth - Basic description on page 116.
For information on the commissioning of this handset, see: Bluetooth - Installation on page 117
2.3.1.1.4 Screens
Characteristics of set displays are:
• 8078s Premium DeskPhone: capacitive Touch Panel, 480x800 color graphical display
• 8068s Premium DeskPhone: 320x240 color graphical display, in 256K color (4096 colors), with
Liquid Crystal Displays (LCD) Modules (LCM).
• 8058s Premium DeskPhone: 320x240 color graphical display

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 81/382

Chapter 2 IP deskphones

• 8038 Premium DeskPhone/8039 Premium DeskPhone: black and white graphical display of 160 by
100 dots, with white backlight
• 8028s Premium DeskPhone/8029 Premium DeskPhone: 64x128 black and white graphical display
with white backlight
All 80x8s Premium DeskPhone have an Ambient Light Sensor used for energy saving. This parameter
can be enabled or disabled in the phone COS menu. Refer to Configuring Phone COS on page 40
80x8s Premium DeskPhone have a Back Logo Light which glows at the end of the set. This logo light
can be handled in the ULM settings in Logo LED option.
80x8s Premium DeskPhone sets come with Customized Skin (except for 8028s Premium DeskPhone).
Skin selection is available in the phone COS menu. Refer to Configuring Phone COS on page 40
2.3.1.1.5 Keys
2.3.1.1.5.1 Dialing keypad
All sets come with a standard 12-key dialing keypad.
2.3.1.1.5.2 Fixed keys
On all sets:

• Two fixed keys below the keypad (start call key): and stop call key: ) allow
to perform several actions
The start call key operates as follows:
• In SIP survivability mode (applicable for IP phones):
• When the terminal is idle, a short press triggers the display of a dial out list on the screen
(same action as a long press on the redial key)
• When there is an incoming call, pressing the start call key puts the set in hands free mode
• In NOE mode the start call key puts the set in hands free mode
The stop call key allows to end a call and ignore an incoming call
• A four-direction set of navigation keys (left, right, up, down) allows to select the different options
available on the screen. The OK button in the center of the navigation validates the selection.
• The C key to the left of the navigation allows to cancel the current action.
• Sensitive (piano) keys are located above the black grid of the lower part of the set.
Starting from the left to the right, they provide access to the following features:

• mute sound

• decrease sound volume

• increase sound volume

• put loudspeaker in service

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 82/382

Chapter 2 IP deskphones

• hold call. This is the default feature for F1 keys (but can be programmed with
another feature)

• transfer call. This is the default feature for F2 keys (but can be programmed with
another feature)

redial information

• information page (displayed on screen)

• messaging services
Note:
The set of four navigation keys, OK key, and C key are not available on 8078s Premium DeskPhone sets.
2.3.1.1.5.3 Integrated additional programmable keys
On 8028s Premium DeskPhone sets, four add-on keys, each with a LED, allow to customize each set
according to the user's needs. A paper label at the right of these keys allows to write down a brief
description of the feature programmed on the key.

2.3.1.2 Connecting optional equipment

2.3.1.2.1 Alphabetic keyboard
A standard (hot pluggable) optional keyboard is available for all sets, in the following layouts:
• Azerty (FR)
• Qwertz (DE)
• Qwerty (international)
• Qwerty (Nordic)
Input Method Editor (IME) stickers are available for the following non-Latin characters:
• Cyrillic
• Zhuyin (Chinese, Taiwan)
• Jamo (Korean)
If you change keyboard types, ensure it is plugged in before restarting the set.
A magnetic external alphabetic keyboard is available on 80x8s Premium DeskPhone sets.
2.3.1.2.2 External interfaces
On all sets, a 3.5 mm jack (4 poles) connector allows to plug a headset to the phone.
80x8s Premium DeskPhone sets have a USB connector which allows USB Connectivity. Refer to
Configuring Phone COS on page 40
The 8068 Premium DeskPhone with Bluetooth handset includes a Bluetooth charger interface.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 83/382

Chapter 2 IP deskphones

RJ9 connector RJ45 10/100/1000BASE-T (PC

(alphabetic keyboard) access or cascaded IP phone)

RJ11 connector
(external ringing
and audio active
envelope indicator)

SATA connector
(for add-on modules 10, 40
keys or Smart module)
RJ9 connector
RJ45 connector (10/100/ (corded handset)
1000Base-T) for LAN
access (IEEE802.3af)
2.0mm jack
(external main
power adapter)

Figure 2.17: External interfaces on the back of 80x8 Premium DeskPhone sets

RJ45 10/100/1000BASE- 3.5mm jack

T (PC access or (external main
cascaded IP phone) power adapter)
RJ11 connector
(external ringing
and audio active
envelope indicator)

SATA connector (for add-on modules, RJ9 connector (corded

10, 40 keys ir Smart module) handset)
USB RJ45 connector (10/100/
1000Base-T) for LAN
access (IEEE802.3af)

Figure 2.18: External interface on the back of 8028s Premium DeskPhone sets

3.5mm jack
RJ45 10/100/1000BASE- (external main
T (PC access or power adapter)
RJ11 connector cascaded IP phone)
(external ringing
and audio active
envelope indicator)
Microphone connector

SATA connector (for add-on modules,

10, 40 keys ir Smart module)
RJ45 connector (10/100/ RJ9 connector (corded
USB
1000Base-T) for LAN handset)
access (IEEE802.3af)

Figure 2.19: External interface on the back of 8058s Premium DeskPhone, 8068s Premium
DeskPhone and 8078s Premium DeskPhone sets

2.3.1.2.3 Additional key modules

On all sets, several add-on modules, connected via SATA (see: External interfaces on page 83), can
complete the standard number of programmed keys.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 84/382

Chapter 2 IP deskphones

Note:
• These add-on modules are not compatible with 40x8 phone sets.
• Add-on key modules designed for 40x8 phone sets are not compatible with 80x8 Premium DeskPhone sets.
• On 8058s Premium DeskPhone sets, the last four softkeys of add-on module are displayed on the last two
lines of the set screen.
The available modules are:
• 10-key module (can be fastened to the set):

• 40-key module (on its own foot stand, placed next to the set)

• Smart-key module (on its own foot stand, placed next to the set)

2.3.2 Commissioning IP Premium DeskPhone sets

2.3.2.1 Declaring the set
Before commissioning an 80x8 Premium DeskPhone or 80x8s Premium DeskPhoneset, ensure that
the corresponding user has been declared in the OmniPCX Enterprise.
To create a set and its corresponding user, refer to: Declaring an IP phone on page 28

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 85/382

Chapter 2 IP deskphones

2.3.2.2 Connecting the 80x8 Premium DeskPhone/80x8s Premium DeskPhone set

2.3.2.2.1 Physical connection
To connect the set to the OmniPCX Enterprise:
1. Plug the RJ45 cable into the set LAN connector, see: External interfaces on page 83
2. Connect the RJ45 cable to the LAN itself
3. If your set is not powered by PoE, plug the AC/DC external adapter to the set power supply
connector and connect the plug to the power supply
Once the set is connected and powered up, it automatically starts initializing.
2.3.2.2.2 Set initialization
By default, 80x8 Premium DeskPhone and 80x8s Premium DeskPhone sets initialize dynamically and
retrieve IP information automatically.
If you want to change initialization mode or configure IP settings:
1. Press the * key and the # key simultaneously when the set is powered up
Note:
Press the i key and the # key simultaneously is still possible from 80x8 Premium DeskPhone/80x8s Premium
DeskPhone sets, except for the 8018 DeskPhone which does not include the i key.
2. Enter your password (if needed) and validate
The configuration menu is displayed
3. Get to IP parameters
4. Click on the icon on the left to validate (or on the icon on the right to cancel)
5. Reset the phone to validate your modifications
Static initialization is mandatory when the system does not use a DHCP server.
If 802.1x is used, additional configuration must be done on the phone at startup. For more information,
see: Configuring 802.1x on IP Touch Sets.
2.3.2.2.2.1 Requested IP parameters for static initialization
The following information must be provided for static initialization:
• IP address (set's address)
• Subnetwork mask
• Router address
• TFTP1 server address (see below for special configurations)
• TFTP2 server address (if needed, see below)
• Use VLAN: this box must be checked to enter a VLAN number
• VLAN number if necessary
• Strict VLAN if necessary (for more information, see: Strict VLAN)
• TFTP port
The TFTP address(es) to enter may differ according to system configuration.
Please contact your system administrator for details on the configuration of your system.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 86/382

Chapter 2 IP deskphones

Duplication Conditions TFTP1 Address TFTP2 Address

The Com Server is not duplicated Com Server main IP N/A

address (or Com Serv-
er physical address if
no main IP address has
been configured)

In a duplicated Com Server configuration where Com Server main IP N/A

the two Com Servers are on the same subnetwork address

In a duplicated Com Server configuration where Com Server A main IP Com Server B main IP
the two Com Servers are on different subnetworks address address

The TFTPb Address is used for the survivability mode. It cannot be modified by the user. It is
automatically filled in with the backup IP address, i.e. the IP address of the rescuable Media Gateway
or the Passive Communication Server.
2.3.2.2.2.2 Requested parameters for dynamic initialization
With dynamic initialization, IP parameters are automatically sent by a DHCP server to the phone.
The following information must be provided for initial startup:
1. From the Registration window, enter:
a. The set directory number
b. The set Password
If the set has already been initialized in the same configuration, there is no need to enter the directory
number and password again.
2.3.2.2.2.3 Deny of download
If the downloaded version is different from the version installed on the set (if, for instance a 80x8
Premium DeskPhone set is connected to an OmniPCX Enterprise before R10.1.1) and if the
downloaded binary is incompatible with the hardware/software, the terminal denies it and signals the
problem to the Communication Server.
The terminal requests binary files at each reset until a compatible binary is found. In the meantime, the
set operates as a 40x8 set.
Deny of download also applies to SIP binary.
2.3.2.2.2.4 lanpbx.cfg file download
When connected to the LAN, the set requests the lanpbx.cfg file from the configured TFTP
address(es).
This file contains one or more line. Each line corresponds to one node of the network and contains the
main IP address(es) of the Com Server(s) on which phones are declared.
At first initialization (no maincpu address stored in flash), the set selects the first line of the lanpbx.cfg
file.
On subsequent initialization (one or two maincpu address(es) stored in flash), the set controls that the
maincpu address(es) stored in flash corresponds to one line of the lanpbx.cfg file. If the address is
not the same, the set restarts as if it was its first initialization.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 87/382

Chapter 2 IP deskphones

2.3.2.2.3 Binary files

To operate correctly, 80x8 Premium DeskPhone and 80x8s Premium DeskPhonesets require binary
files, automatically downloaded at set initialization. These files must comply with the PCX version and
configuration. After system upgrade and each time a set initializes, version numbers of binary files are
verified to determine whether an update of these files is necessary.
When a file is downloaded to the set, it overwrites any previously existing file.
Each time the IP phone is initialized, its binary version is checked to see whether more recent binaries
need downloading.
When a set has initialized at least once with an OmniPCX Enterprise, on subsequent startup, it does
not request a binary header and switches to fast initialization.
The version of binary files for Premium DeskPhones starts with 4.50.YY
Binary files consist of:
• Boot loader file and code file (containing the boot software, downloader software and application
software)
80x8 Premium DeskPhone sets
bin80x8N: bootloader binary (rescue software)
noe80x8N: noe binary
80x8s Premium DeskPhone sets
bin80x8S: bootloader binary (rescue software)
noe80x8S: noe binary
• Data file (contains ringing melodies, beeps, icons, fonts and images)
80x8 Premium DeskPhone sets
dat80x8N: noe data binary
noesip80x8N: SIP binary
datsip80x8N: SIP data binary
80x8s Premium DeskPhone sets
dat80x8S: noe data binary
sip80x8S: SIP binary
• Localization files (providing non Latin characters)
<lang*>-80x8: Localization binary of 8028 Premium DeskPhone/8038 Premium DeskPhone sets
<lang>-8068: Localization binary of 8068 Premium DeskPhone set
<lang>-8068S: Localization binary of 8068s Premium DeskPhone set
<lang*>-80x8S: Localization binary of 80x8s Premium DeskPhone sets
• Customization files (for ringing and tone beeps)
cust-<customer**>-8028: Customization binary of 8028 Premium DeskPhone set
cust-<customer>-8028S: Customization binary of 8028s Premium DeskPhone set
cust-<customer**>-80x8S: Customization binary of 80x8s Premium DeskPhone sets

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 88/382

Chapter 2 IP deskphones

2.3.2.3 LLDP-MED configuration

The LLDP / LLDP-MED protocol allows information exchange between end devices and adjacent LAN
switches. This mechanism is based on IEEE 802.1AB and ANSI TIA 1057 (LLDP-MED) standards.
IP Premium DeskPhones sets comply with the LLDP-MED protocol.
By default, LLDP-MED is activated and allows:
• Automatic VLAN assignment from LLDP message advertised by LAN switch
• Power over Ethernet negotiation. The LLDP POE negotiation is used at initialization in addition to
the 802.3af protocol or 802.3az protocol
• Inventory information of terminal to be sent regularly to adjacent LAN switch.
Inventory information sent by a set includes:
• Hardware revision
• Firmware version
• Software version
• Serial number
• Manufacture name (set to Alcatel-Lucent Enterprise)
• Model name
• Asset ID (set with the SIP configuration file to the set MAC address)
The three sub functions (Automatic VLAN assignment/Power Management/Inventory Publication) can
be enabled/disabled through Local MMI.

2.3.2.4 VLAN configuration with LLDP

IP Premium DeskPhones sets can obtain VLAN information via static configuration. Alternatively:
Automatic VLAN Assignment (AVA) or Link Layer Discovery Protocol (LDDP) / Link Layer Discovery
Protocol - Media Endpoint (LLDP-MED) can be used.
LLDP/LLDP-MED allows the retrieval of the VLAN identifier of the end device (the terminal’s “voice”
VLAN) from the LAN switch. VLAN information is acquired only from the LLDP-MED network policy
item containing the “voice” application type. Multi-network policy is supported. The LLDP/LLDP-MED
client is activated by default in the terminal during initialization, but is non-blocking in case the LAN
Switch does not respond. To keep compatibility with other network connective devices and considering
the network load, the set sends LLDP packets each second during the first 30 seconds, then every two
minutes.
There are two phases involved in VLAN acquisition:
1. VLAN acquirement:
This happens at the beginning of the LLDP procedure. The terminal waits for a certain time to get
the LLDP/LLDP_MED response, after the first LLDP/LLDP_MED advertise packet has been sent
out. At this stage, the terminal only accepts valid VLAN information, and ignores invalid VLAN
information (e.g VLAN 0 or VLAN 4095). If valid VLAN information is obtained, the set enters a
VLAN_acquired state; if not, it enters a VLAN_no_acquired state
2. VLAN update:
This happens after VLAN acquirement, and is used for possible VLAN updating. The IP Phone
resets if new VLAN information is detected. Behavior differs according to the state of the set after
VLAN acquirement. In a VLAN_acquired state, the IP Phone resets to detect VLAN modification
(from a valid VLAN to an invalid VLAN). In VLAN_no_acquired state, the set ignores this invalid
VLAN information
By default, this feature is active. The set must be connected to a switch supporting LLDP to obtain
VLAN information.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 89/382

Chapter 2 IP deskphones

The priority orders of VLAN ID acquirement in dynamic mode is: LLDP > AVA > Static

2.3.3 Maintenance
The following paragraphs detail the most common and useful command lines for Premium DeskPhone
sets.
Maintenance commands allow to distinguish between 80xx sets and 40xx sets. Configuration
parameters (available from mgr and the OmniVista 8770) are the same.
The OmniPCX Enterprise versions R11.0.1 and R10.1.1 J2.603.27 fully support Premium DeskPhones.
On previous versions, Premium DeskPhones operate normally as if they were 40xx sets.

2.3.3.1 Detecting set types

To detect Premium Deskphones on an OmniPCX Enterprise version that does not fully support
Premium DeskPhones:
• For TDM 80x9 phones :
Enter: Zdpost d <phone number> | grep “IPTOUCH TDM”
If the result is: IPTOUCH TDM hard version = 167, the set is a Premium Deskphone
If the result is: IPTOUCH TDM hard version = 160, the set is a 40x9 set
• For IP 80x8 and 80x8s phones
Enter: Zdpost d <phone number> | grep “version”
If the result for the firmware version is 4.50.xx, the set is a Premium Deskphone
Example:
Firmware version Data : 4.50.30
Bootloader version : 4.50.30
SIP version : 2.11.83

2.3.3.2 downstat t
The downstat t command displays information on download for 9 series sets.
Example:
(1)cs80> downstat t
*** IPTOUCH-A(4019) TDM : soft : 3.81.00
*** IPTOUCH-B(4029) IPTOUCH-C(4039) TDM : soft : 3.81.70 - data : 3.81.70
***/DHS3bin/downbin/data80x9*** file does not exist
*** IPTOUCH-B(8029) IPTOUCH-C(8039) TDM : soft : *** - data : ***
*** Download time optimization: FOR EACH SET
** 3 IPTOUCH TDM phones are declared on this node !!
** 0 IPTOUCH TDM phones are not updated with the right binary!
** 0IPTOUCH TDM phones can be reseted for update!!
IPTOUCH TDM phone downloaded informations :
-------------------------------------
1 Display up to date IPTOUCH TDM phones
2 Display IPTOUCH TDM phones not yet updated
3 Display download in progress
4 Display out of order IPTOUCH TDM phones
5 Display all IPTOUCH TDM phones
0 Quit
Your choice ?

2.3.3.3 getnoeversion
The getnoeversion command returns information about all Premium DeskPhone sets that are
declared and in service on the node.
This information includes:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 90/382

Chapter 2 IP deskphones

• Status (in service or out of service)

• Type of set
• IP domain number (IP DeskPhones sets)
• Serial number
• Hardware version
• Software version
The presence (or absence) of Bluetooth and additional key modules is detailed, as well as the
RAM/ROM of the set.
Localization and customization information is listed in the command result.
This command can be applied:
• To a specific set by using the set directory number.
The command results can be displayed directly on the maintenance console.
Example:
(1)cs80> getnoeversion d 17002
+------------------------------------------------------------------------------------------+
|dir numb |in |typ term |dom |serial number|hardware version|code vers |data vers|rom |ram |
+------------------------------------------------------------------------------------------+
|17002 |OK |8029 |n/a | | | 4.50.30 |4.50.30 | 2 | 0 |
+------------------------------------------------------------------------------------------+
• To all the Premium DeskPhone sets of the node. The results for the getnoeversion command are
stored in the file:
/DHS3dyn/mao/getnoeversion.xxx
where xxx corresponds to .csv or .xml format, according to user choice.

2.3.3.4 ippstat
The ippstat command returns information on all the IP phones of a node.
Example:
(1)cs80> ippstat
IPP (IP Phone) information :
-------------------------------------
Display the IP Address of the local node : 1
Display IP Phone data of a set : 2
Display all IP Phone on local node : 3
Display registration terminaisons(short info): 4
Display registration terminaisons (long info): 5
Display an IP Phone Board structure : 6
Display all IP Phone Board structure : 7
Display all Mac Address Used : 8
Display all Mac Address Unused : 9
Display Ip phone by adr mac/adr adr ip/mcdu : 10
Display number of IP Phones connected : 11
Display all IP Phones connected on a board : 12
Display all IP Phones connected with boards : 13
Ip Phone download Menu : 14
Timeout for telnet session of IP Touch set : 15
INT IP Menu : 16
Domain Menu : 17
IPlink Menu : 18
Status Menu : 19
Display boards encryption parameters : 20
Enable telnet session of GD/GA/OMS : 21
Quit this tool : 0
Enter your choice :

2.3.3.5 listerm
The listerm command lists all the terminals belonging to a node.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 91/382

Chapter 2 IP deskphones

2.3.3.6 termstat
The termstat command provides information on the board to which the set is connected, call
forwarding as well as other information.
Example:
(1)cs80> termstat d 13002
Tue Nov 12 15:16:11 CET 2013
+COUPLER_INFORMATION --------------------------------------------------------+
| Logic coupler type : CPL_UA
|
| MAO coupler type : UAI 8
|
| Coupler state : IN SERVICE
|
+--------------------------------------(PRESS ANY KEY TO CONTINUE)+
[1] : Device features.
[2] : Forward information.
[3] : Subdevice information.
[4] : Demi-com information.
[5] : Reset the device.

2.3.3.7 eqstat/tradna
The eqstat and tradna commands provide information on the status of a set and reason why a set
is out of service.
The two commands return the same results.
Example:
(1)cs80> tradna 13002
Tue Nov 12 15:22:06 CET 2013
Logic coupler type : CPL_UA
MAO coupler type : UAI 8
Coupler state : IN SERVICE
Terminal state : IN SERVICE
+-----------------------------------------------------------------------------+
| Cry:Cpl:ac:term | neqt |nulog| typ term | dir nb | Out of service cause |
+-----------------------------------------------------------------------------+
| 001 5 0 6 | 00418 | 29| 4029| 13002 | |
+-----------------------------------------------------------------------------+
| A: att_mserv, C: hs_defich, I: hs_isolauto, X: hs_isolman, T: hs_terdef |
| U: hs_usdef, P: hs_errparite, B: hs_bascul, Y: hs_cristisol, N: hs_inex |
+-----------------------------------------------------------------------------+

2.3.3.8 zdpost
The zdpost command provides information on configuration of the set and the latest activity of the set.

2.4 8088 Smart DeskPhone (IP deskphones)

2.4.1 Overview
As of R12.0, 8088 Smart DeskPhone sets can be configured on the OmniPCX Enterprise as business
sets. In this configuration, 8088 Smart DeskPhone sets operate in NOE mode and share many features
and capabilities with other IP deskphones (see: Overview on page 15).
8088 Smart DeskPhone sets include a Linux software and boot in SIP mode at first initialization. To run
as business sets, 8088 Smart DeskPhone sets must migrate to an Android software and boot in NOE
mode.
Migration to Android is possible from 8088 Smart DeskPhone sets running with Linux version R300 or
higher. During their deployment on the OmniPCX Enterprise (static or dynamic initialization), 8088
Smart DeskPhone sets receive information on the Android version to download, and on the address of

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 92/382

Chapter 2 IP deskphones

the HTTP server where the Android software is available. An HTTP server is required to download
Android. It must be deployed at the customer premises or in the Cloud infrastructure. The OmniPCX
Enterprise does not include HTTP server properties and cannot be used to download Android.

2.4.2 About this section

The following paragraphs provide:
• A description of the sets, including adescription of the files necessary to commission the sets
(configuration and binary files):
• Details on ergonomics (see: Set description on page 93)
• A description of the files necessary to commission the sets (configuration and binary files):
• Set configuration file description on page 93
• Set binary file description on page 94
• Generalities on set initialization on page 94
• Set configuration and deployment on page 96
• Maintenance on page 98

2.4.3 Set description

Set ergonomics is identical, irrespective of the running mode (SIP or NOE). For more information, see:
Set ergonomics on page 257. 8088 Smart DeskPhone sets can be delivered with a Bluetooth handset,
or corded handset.
8088 Smart DeskPhone sets have an Ambient Light Sensor (ALS) used to save energy. ALS activation
is performed using the 8&9 Series phone COS (see: Configuring Phone COS on page 40).
8088 Smart DeskPhone sets include a virtual key module available on screen (equivalent to a Smart
Display Module).
8088 Smart DeskPhone sets running in NOE mode do not support:
• Additional key modules
• Backward compatibility (NOE is not supported in prior versions)
• Dial pad rotation (feature available from the 8&9 Series phone COS)
• USB boost charging (feature available from the 8&9 Series phone COS)
• Encryption and IPv6 addressing

2.4.4 Set configuration file description

Each time the 8088 Smart DeskPhone set initializes, it requests its configuration file (lanpbx.cfg)
from the TFTP address(es), available either on a DHCP server (dynamic initialization) or in the set
settings (static initialization).
The lanpbx.cfg file contains one or more line. Each line corresponds to one node of the network and
contains the main IP address(es) of the communication server(s) on which the set is declared.
At first initialization (no main Communication Server IP address stored in flash), the set selects the first
line of the lanpbx.cfg file.
On subsequent initializations (one or two main Communication Server IP address(es) stored in flash),
the set controls that the main Communication Server IP address(es) stored in flash corresponds to one
line of the lanpbx.cfg file. If the IP address is not the same, the set restarts as if it was its first
initialization.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 93/382

Chapter 2 IP deskphones

2.4.5 Set binary file description

To operate as business set (NOE mode), the 8088 Smart DeskPhone set requires binary files,
automatically downloaded at set initialization. These files must comply with the Communication Server
version and configuration. After Communication Server upgrade and each time a set initializes, version
numbers of binary files are verified to determine whether an update of these files is necessary.
When a file is downloaded to the set, it overwrites any previously existing file. Each time the set is
initialized, its binary version is checked to see whether more recent binaries need downloading. When
a set has initialized at least once with a Communication Server, on subsequent startup, it does not
request a binary header and switches to fast initialization.
There are three files deployed on the OmniPCX Enterprise using the NOE standard method for
downloading:
• A migration deployment file (bin8088s)
• The patch upgrade file (dat8088s)
• A binary file, including ALEapps (noe8088s)
The bin8088s and dat8088s provide the binary version (to verify) and the URL of the default HTTP
server on which the Android binary must be deployed, if it is not defined in the lanpbx.cfg file.
The Android software package must be registered on the HTTP server used for downloading. It
consists of:
• A RPM file (8088_bin_<version>.rpm) including the Android binary
• A zip file (8088_ota_<version>.zip) including the Android upgrade patch
Note:
If the downloaded version is different from the version installed on the set (if, for instance an 8088 Smart
DeskPhone set is connected to an OmniPCX Enterprise before R10.1.1) and if the downloaded binary is
incompatible with the hardware/software, the set denies it and signals the problem to the Communication Server.
The terminal requests binary files at each reset, until a compatible binary is found. In the meantime, the set
operates as a 40x8 set.

2.4.6 Generalities on set initialization

2.4.6.1 Overview
By default, 8088 Smart DeskPhone sets initialize in dynamic mode and automatically retrieve network
the parameters and the URL, so as to download configuration and binary files from a DHCP server
(see: DHCP configuration (dynamic initialization) on page 94).
If the set initialization mode is static, the set uses its internal parameters. All necessary configuration,
such as network parameters, must be made manually on the set itself (see: Requested IP parameters
(static initialization) on page 95).

2.4.6.2 DHCP configuration (dynamic initialization)

If the 8088 Smart DeskPhone set initializes in dynamic mode, IP parameters are automatically sent by
a DHCP server to the set.
At startup, the set requests information to the DHCP server for its initialization. The DHCP server must
provide the following information to the set:
• Set initialization in NOE mode (option 67 set of the configuration file lanpbx.cfg)
This option enables to switch the set from a Linux version (SIP mode) to an Android version (NOE
mode). The set must be configured with its factory settings. If it is not the case, a flash reset is
necessary to return the set to its factory state (for "out of the box" sets, this is already done).
• Set IP address

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 94/382

Chapter 2 IP deskphones

• IP subnetwork mask (option 1)

• Router IP address (option 3)
• TFTP IP addresses:
• If the set connects to only one Communication Server (no duplication), the TFTP address of the
Communication Server must be entered in the siaddr field (this entry is also called Next-
Server).
• If the set can connect to one or two Communication Servers (duplication), the TFTP addresses
of the Communication Servers must be entered in option 43. This option includes sub-options 64
and 65 to enter TFTP addresses.
The table below displays TFTP addressing according to the Communication Server duplication
deployed at the customer site. Please contact your system administrator for details on the
configuration of your system.

Duplication Conditions TFTP1 Address TFTP2 Address

Communication Server running standalone (no Communication Server N/A

duplication) main IP address (or
physical address if no
main IP address has
been configured)

Communication Server duplication where the Communication Serverr N/A

two Communication Servers are on the same main IP address
subnetwork

Communication Server duplication where the Communication Server Communication server

two Communication Servers are on different A main IP address B main IP address
subnetworks
• If requested, VLAN number (option 43 / sub-option 58)
DHCP server configuration is described document [7]. This server may be hosted by a machine on the
Cloud infrastructure or client premises.

2.4.6.3 Requested IP parameters (static initialization)

If the 8088 Smart DeskPhone set must initialize in static mode, the following information must be
provided to the set during its initialization:
• Set IP address
• IP subnetwork mask
• Router IP address
• TFTP IP addresses
The table below displays TFTP addressing according to the communication server duplication
deployed on customer site. Please contact your system administrator for details on the configuration
of your system.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 95/382

Chapter 2 IP deskphones

Duplication Conditions TFTP1 Address TFTP2 Address

Communication Server running in standalone Communication Server N/A

(no duplication) main IP address (or
physical address if no
main IP address has
been configured)

Communication Server duplication where the Communication Server N/A

twoCommunication Servers are on the same main IP address
subnetwork

Communication Server duplication where the Communication Server Communication Serv-

two Communication Servers are on different A main IP address er B main IP address
subnetworks
• VLAN number (if VLAN is required)
• Strict VLAN if necessary (for more information, refer to section 802.1p/Q and VLAN of document
[7])
Set initialization in NOE mode is enabled via a menu in the settings of the set. This menu enables to
switch the set from a Linux version (SIP mode) to an Android version (NOE mode). The set must be
configured with its factory settings. If it is not the case, a flash reset is required to return to factory state
(for "out of the box" sets, this is already done).

2.4.7 Set configuration and deployment

2.4.7.1 Configuring the set
The 8088 Smart DeskPhone set running as business set (NOE mode) must be declared as IPTouch
8088 on the OmniPCX Enterprise. For more information, see: Declaring an IP phone on page 28.
The 8088 Smart DeskPhone set running in NOE mode has dedicated Android settings and an external
numbering plan (prefixes) that must be configured in the 8&9 Series phone COS (see: Configuring
Phone COS on page 40).
This concerns the following Android parameters:
• Private store URL
• Proxy for Software upgrade
Note:
The bluetooth, ringing level and contrast settings cannot be controlled by the OmniPCX Enterprise. They can only
be adjusted from the local settings on the set.

2.4.7.2 Commissioning the set

2.4.7.2.1 Prerequisites
Before commissioning a 8088 Smart DeskPhone set as a business set, ensure that:
• The set runs on Linux version R300 or higher (information available in the Software version menu
of the set settings). If it is not the case, you must update set binaries with the appropriate version
(see: 8082 My IC Phone/8088 Smart DeskPhone (SIP deskphones) on page 256).
• The minimum hardware version must be P4T4 (information available in the Software version menu
of the set settings).
• The set must start with factory default settings (after flash reset or a restoration to the “Out of the
box” initial status). If it is not the case, reset to factory (see: Reset to factory on page 299). This is
required to switch the set from a Linux version (SIP mode) to an Android version (NOE mode).

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 96/382

Chapter 2 IP deskphones

• If dynamic initialization is used, a DHCP server must be configured (see: DHCP configuration
(dynamic initialization) on page 94).
• If static initialization is used, a free IP address must be available for the set.
• The set is declared on the OmniPCX Enterprise (see: Configuring the set on page 96).
• The Android software package is registered on the HTTP server used for downloading.
2.4.7.2.2 Plugging the set
To connect the set to the LAN:
• If the set is powered by PoE:
1. Turn the set over
2. Plug the RJ45 cable into the set LAN connector
3. Connect the RJ45 cable to the LAN itself via a PoE hub/switch
• If the set is not powered by PoE, plug the AC/DC external adapter to the set power supply
connector and connect the plug to the power supply.

Power over Ethernet (PoE)

connector (LAN)

Power adapter
connector (DSCV)

Figure 2.20: Set power connectors

Once the set is connected and powered up, it automatically starts initializing.
The initialization process consists in:
1. Network initialization and setup
2. Configuration file download (lanpbx.cfg file)
3. Android package download (Android OS, patches, and applications)
4. Set registration on the OmniPCX Enterprise (user directory number and password)
2.4.7.2.3 Configuring set parameters (static initialization only)
By default, the set starts in dynamic mode and operates in NOE mode (factory settings). Skip this
section if using dynamic mode with DHCP.
To configure set parameters in static mode:
1. After startup, wait until the settings menu is available (from step 2 of the initialization process) and
press the Settings icon available at the bottom left of the set screen
2. Press Admin and enter an administrator password
Note:
The default administrator password (after flash reset and before configuration file download) is *tx8000#.
3. Go to: Network > IP

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 97/382

Chapter 2 IP deskphones

4. Select the Static mode and configure the set IP parameters (see: Requested IP parameters (static
initialization) on page 95)
5. Go to: Device > Running mode
6. Enable the NOE protocol
This option enables to switch the set from a Linux version (SIP mode) to an Android version (NOE
mode).
7. Press the Home soft key
The set starts initializing
If 802.1x is used, additional configuration must be done on the set at startup. For more information, see
section Configuring 802.1x on IP Touch Sets of document [7].
2.4.7.2.4 Registering the set on the OmniPCX Enterprise
When the set initialization is finished, you are prompted to enter its directory number and password.
Note:
If the set has already been initialized in the same configuration, there is no need to enter the directory number and
password again.
2.4.7.2.5 Upgrading set binaries
Binary upgrade is silent and takes place in the background, once the OmniPCX Enterprise has
detected that an upgrade is required. Once the file is downloaded by the set and when the set is idle, it
resets and implements the new software.

2.4.8 Maintenance
The most common and useful command lines available for IP deskphones also apply to 8088 Smart
DeskPhone sets configured as business sets (NOE mode). For more information, see: Maintenance on
page 56.

2.5 IP Touch 4028/4038/4068 Phone (8 series)

2.5.1 Ergonomics of 8/9 Series sets
2.5.1.1 Alcatel-Lucent IP Touch 4028/4038/4068 and Alcatel-Lucent 4029/4039 Digital Phone set
description
Although there are differences in the aspect and operation of these sets, their layout is identical but for
the screen and number of available soft keys.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 98/382

Chapter 2 IP deskphones

Screen Inclination
Set Screen Adjustment Alarm LED

Soft Keys

Dialing Keypad Fixed keys

Headset jack
Alphabetic Keyboard

Alt Key Space Bar

Figure 2.21: Alcatel-Lucent IP Touch 4068 Phone set layout

Set Screen Screen Inclination

Alarm LED
Adjustment

Soft Keys

Dialing Keypad Fixed keys

Headset jack Alphabetic Keyboard

Alt Key Space Bar

Figure 2.22: Alcatel-Lucent IP Touch 4038 Phone and Alcatel-Lucent 4039 Digital Phone set layout

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 99/382

Chapter 2 IP deskphones

Screen Inclination
Set Screen Adjustment Alarm LED

Soft Keys

Dialing Keypad Fixed keys

Headset jack Alphabetic Keyboard

Alt Key Space Bar

Figure 2.23: Alcatel-Lucent IP Touch 4028 Phone and Alcatel-Lucent 4029 Digital Phone set layout

2.5.1.1.1 Set equipment

The Alcatel-Lucent IP Touch 4028/4038/4068 and Alcatel-Lucent 4029/4039 Digital Phone sets all
include the following items:
• Corded comfort handset
• Hands-free station speaker
• A number of keys
• A number of LEDs
• A set screen
• Additional key module (optional)
• Wall mounting kit (optional)
• "Big Foot" Foot stand 60° (optional)
• Bluetooth headset (available on Alcatel-Lucent IP Touch 4068 Phone set only)
2.5.1.1.2 Connecting optional equipment
2.5.1.1.2.1 External station speakers
The headset jack is located on the left side of the Alcatel-Lucent IP Touch 4028/4038/4068 sets
The 3.5 mm female jack can receive an external speakers' jack.
Customize your set to take the external station speaker into account:
1. From the Menu tab, select Settings
2. In the next screen, select My extension on an Alcatel-Lucent IP Touch 4068 Phone or Alcatel-
Lucent IP Touch 4038 Phone set, My phone on an Alcatel-Lucent IP Touch 4028 Phone set
3. In the next screen, select Jack plug
Enter your password and press Apply
4. Select Loudspeaker and press the OK button.
5. Plug the external station speaker jack into the associated set connector.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 100/382

Chapter 2 IP deskphones

2.5.1.1.2.2 Plugging a PC or an IP phone set to an IP Touch set

The Alcatel-Lucent 8 series set includes a internal LAN switch.
This switch allows to connect:
• A PC
• A cascaded Alcatel-Lucent 8 series set

IP Touch Set PC

OR
LAN Port
PC Port

LAN
Cascaded Set

Figure 2.24: Ip Touch set connections

The internal switch has three ports:

• A LAN port
• An internal port
• A PC port, to connect a PC or another set to the LAN via the Alcatel-Lucent 8 series set
The PC port can be disabled and can be configured to force PC packets to get the default VLAN
tag. For configuration, see: Phone COS on page 40.
The internal switch privileges VoIP traffic over PC port traffic.
This switch has two waiting queues:
• The HPQ (High Priority Queue) to proceed all packets from the terminal
• The LPQ (Low Priority Queue) to proceed packets from the PC port
The switch proceeds seven HPQ packets for an LPQ packet.
Exception: packets from the PC port use the HPQ when they are tagged with a 802.1p tag and when
the tag value is superior or equal to 4.
The 802.1p tag is an IEEE standard tag which specifies the priority of the packet.
Restrictions:
• Only one additional set of equipment can be connected to the PC port
• The main IP Touch set must be locally powered to accept a cascaded IP phone
• The PC port is not available on Alcatel-Lucent IP Touch 4008 Phone sets
2.5.1.1.3 Set keys
The Alcatel-Lucent IP Touch 4028/4038/4068 and Alcatel-Lucent 4029/4039 Digital Phone sets include:
• A dialing keypad

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 101/382

Chapter 2 IP deskphones

• An alphabetic keyboard with 34 keys

Five versions are available: French, German, International, Scandinavian and American.
• Fixed function keys
• A navigator consisting of 4 directional navigation keys
• Programmable keys (72 keys on the Perso tab and 2 personal keys)

2.5.1.2 Alcatel-Lucent 8/9 series and Alcatel-Lucent 4019 Digital Phone set description
Dialing Keypad Set Screen

Fixed Function Keys

Programmable Keys

Fixed Function Keys

Figure 2.25: Alcatel-Lucent IP Touch 4018 phone Extended Edition and Alcatel-Lucent 4019
Digital Phone Set Layout

2.5.1.2.1 Set equipment

The Alcatel-Lucent IP Touch 4018 phone Extended Edition and Alcatel-Lucent 4019 Digital Phone sets
include the following items:
• Corded comfort handset
• Hands-free station loudspeaker (basic station loudspeaker, no hands-free feature on Alcatel-Lucent
4019 Digital Phone set)
• A number of keys
• A number of LEDs
• A set screen
• Wall mounting kit (optional)
• "Big Foot" Foot stand 60° (optional)
2.5.1.2.2 Set keys
The Alcatel-Lucent IP Touch 4018 phone Extended Edition and Alcatel-Lucent 4019 Digital Phone sets
include:
• A dialing keypad with 12 keys
• Fixed function keys
• Fixed navigation keys consisting of:
• A bidirectional navigation key (up and down)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 102/382

Chapter 2 IP deskphones

• A back key
• An OK key
• Six programmable keys

2.5.1.3 Support for long names and non-Latin characters

The OmniPCX Enterprise provides the following support for long names and non-Latin characters on
Alcatel-Lucent 8/9 series sets:
As of R7.0:
• Display of long names and names in non-Latin characters for callers, trunk groups, speed dialing
numbers, and entities
As of R8.0:
• Display of programmed key and directory key names in non-Latin characters
• Dial by name using non-Latin characters
• Input of programmed key names using non-Latin characters
• Conservation of key names in non-Latin characters when changing sets, changing an additional key
module, or migrating a user between nodes, provided the new set device supports non-Latin
characters.
Note:
Display of long names and names in non-Latin characters is not available in the Hotel/Hospital application.
Note:
Dial by name and input of non-Latin characters is available on Alcatel-Lucent 4029/4039 Digital Phone sets as of
R8.0 and on Alcatel-Lucent IP Touch 4028/4038/4068 sets as of R8.0.1.
2.5.1.3.1 Display of long names and non-Latin characters
The system allows for Alcatel-Lucent 8/9 series sets to display:
• Names up to 30 characters long in full (as of R7.0)
• Cyrillic, Greek, Chinese, Japanese, and Korean characters (as of R7.0)
• Hebrew characters (on Alcatel-Lucent IP Touch 4028/4038/4068, as of R9.1 and Alcatel-Lucent
4029/4039 Digital Phone, as of R10.0)
This includes names for:
• The caller when set is ringing
• The last caller and last number dialed (on the set's Info and Events pages)
• Trunk groups
• Speed dialing numbers
• Entities
Note:
User and trunk group names are displayed for internal calls and after a transfer. By default names display for calls
to and from other nodes in an ABC-F network. This feature is configurable. See: UTF8 resolution in an ABC-F
network on page 51.
As of Release 8.0, the system allows for Alcatel-Lucent 8/9 series sets to display:
• Programmed key names on the Perso Pages (Alcatel-Lucent IP Touch 4028/4038/4068 and Alcatel-
Lucent 4029/4039 Digital Phone sets)
• Directory key names (Alcatel-Lucent 8/9 series, Alcatel-Lucent 4019 Digital Phone, and MIPT sets)
A configuration attribute has been created for each name that can be displayed in non-Latin
characters. These configuration attributes encode characters in 8-bit Unicode Transformation Format
(UTF-8), which allows any character to be represented in the Unicode standard.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 103/382

Chapter 2 IP deskphones

A set displays a name in non-Latin characters if:

• The node is at the appropriate software release for the feature
• The set allows for the type of characters used
• The set's Language ID is compatible with the character type of the name to display
• The UTF-8 name attribute has been configured
If any of these criteria are not met, the set displays the standard (non-UTF-8) name in Latin characters.
To configure UTF-8 name attributes, see: Configuring names in non-Latin characters on page 47
The following table shows the types of characters, in addition to Latin, that are available for each set.
The number of characters displayed depends on the type of characters. The table shows the
approximate maximum number of characters displayed for each set.

table 2.9: Available character types on set displays

Set Max Cyrillic Greek Chinese Japa- Korean Hebrew Thai

charac- nese
ters dis-
played
(approx.)

4008,401 20 Yes Yes No No No No No

8, 4019

4028,402 24 Yes Yes Yes Yes Yes Yes No

9

4038,403 30 Yes Yes Yes Yes Yes Yes No

9, 4068

MIPT 18 Yes Yes No No No No No

8028/803 Yes Yes Yes Yes Yes Yes Yes

8/8068,
80x8s
Premium
Desk-
Phone
and
8029/803
9

The following figure shows a 4068 set screen display of names of the last numbers called. The set's
Language ID is Russian.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 104/382

Chapter 2 IP deskphones

Figure 2.26: Example display of a 4068 Set with Russian as Language ID

Since the set's Language ID is Russian, the first name is displayed in Latin characters (rather than
Chinese), the second name is in Latin characters and the third name is in Cyrillic characters.
2.5.1.3.2 Input of non-Latin characters
Starting with Release 8.0, an Input Method Editor (IME) is available on Alcatel-Lucent 8/9 series sets,
enabling input of non-Latin characters, that is, Cyrillic characters and CJK (China, Japan, Korea)
characters.
The IME enables the following features:
• Dial by name using non-Latin characters
• Input of names for programmed keys (Perso Pages) using non-Latin characters
The type of characters currently in use on a telephone set is associated with an input method: Latin
(default), Cyrillic, Pinyin, Jamo, Stroke, or Zhuyin. To make an input method other than Latin available
on a set, configure it in the Phone Class of Service (see Configuring Phone COS on page 40).
Note:
Japanese is not supported by the IME on Alcatel-Lucent 8/9 series.
Note:
The IME is available on Alcatel-Lucent 4029/4039 Digital Phone sets as of R8.0 and on Alcatel-Lucent IP Touch
4028/4038/4068 sets as of R8.0.1.
Note:
For information on the operation of the IME, refer to the document [3].
For more information on the operation and configuration of Dial by name, refer to the document [3].

2.5.1.4 Display of external called number

According to a system option, when dialing an external number the set display either shows the trunk
group name or the number entered by the user on the keypad (see: Enabling external called number
display on page 38).

2.5.1.5 Access to external applications

8 series (IP Touch) users can have direct access to external applications from their set via a soft key.
This is available on:
• 4028 IP Touch sets
• 4038 IP Touch sets
• 4068 IP Touch sets
External applications are interfaced to IP Touch sets and the OmniPCX Enterprise with the
Presentation Server, refer to the document [10].

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 105/382

Chapter 2 IP deskphones

This feature proves particularly useful for video conference implementation.

The soft key dedicated to an application is always available from the Menu page, where application soft
keys are displayed systematically displayed under telephone feature keys.

Thu 16
09/23/03 May 2006 9:58
9:58
AM

MENU PERSO INFO

Laura
Settings JACKSON
Outgoing calls
Ir 7
Appointment
Carol SMITHForward
Textmail
New is calling Lock
Call

Events
Record Video
No camp on

Figure 2.27: Example of access to a video application from a 4068 IP Touch set

When several applications can be accessed, the system determines their priority on the set screen,
see: Defining external applications on page 38.
As of R7.1, application soft keys can be displayed when the set is being used for its telephone
capabilities.

Thu 18 May 2006 10:43

Graziella Moreno
Conversation 1:04

Enquiry call Malicious call

Forbid camp on Video

Figure 2.28: Example of access to an external application when the set is in conversation

Application soft keys are displayed according to:

• Set type (see above)
• Application status:
• Public vs. restricted
• Configured to appear according to telephone call status
• Telephone call status:
• Incoming call
• Initiated call
• Delivered call (sent to the other party)
• Established call (in conversation)
• Conference call (in conversation with several parties)
• On hold call
• Disconnected call
Soft key labels are sent to the sets when the external application is launched. They cannot be modified
while the application is running.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 106/382

Chapter 2 IP deskphones

Application soft keys are displayed regardless of feature availability. If, for example, an IP Touch set is
in conversation with a Reflexes set, the Video soft key of the above example is available even though
no video conference can take place on a Reflexes set.

2.5.1.6 Before mounting an Alcatel-Lucent 8/9 series set on a wall

The set must be prepared to ensure the handset does not fall off the set when fixed on a wall.
1. Locate the position of the dowel to adjust on the set.

2. Move the dowel up to extract it

3. Turn it upside down.

4. Push the upside down dowel back into its slot

Once the set is fixed on the wall, the dowel hook will maintain the handset in place.
To screw the set to the wall kit, proceed as described in the wall kit documentation.

2.5.2 Commissioning
2.5.2.1 Overview
This module presents the actions required for commissioning Alcatel-Lucent IP Touch 4028/4038/4068
sets.

2.5.2.2 Commissioning Alcatel-Lucent IP Touch 4028/4038/4068 Sets

2.5.2.2.1 Prerequisites
Before commissioning 4028/4038/4068 IP Touch sets, you must check that the user is declared in the
OmniPCX Enterprise, see: Declaring an IP Phone on page 28.
2.5.2.2.2 Before You Start
To ensure correct set operation, check the following before plugging the set in.
2.5.2.2.2.1 Which Power Supply to Use?
The IP Touch set can be supplied from two sources:
• An AC/DC external adapter which is a 42V power supply
A female jack is used to connect the power adapter. The AC/DC external adapter is the same for IP
Touch and e-Reflexes sets.
• Power over Ethernet (PoE)
For more information on connecting an IP Touch set to PoE, see: IP-Phones - e-Reflexes
OperationsSet Power Supply

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 107/382

Chapter 2 IP deskphones

To supply power via PoE, please refer to the used device documentation, for example:
• see Power Patch Panels - Hardware description.
• see 3 Port PoE Gigabit Adapter - Introduction
2.5.2.2.2.2 Which Initialization (Static or Dynamic) to Opt for?
There are two possible initialization modes:
• Dynamic initialization (default mode on new sets): as soon as it is powered up, the set retrieves IP
parameters from a DHCP server. The user only needs to enter the set directory number and the set
password at the end of the process.
• Static initialization: the user enters manually all necessary information regarding IP address,
subnetwork mask , router address, TFTP server address and VLAN.
By default, set initialization is dynamic. But the user can change this default configuration before the
set has finished initializing, see: Selecting the Initialization Mode on page 110.

table 2.10: Initialization modes

Condition Initialization Process to Opt for

The system uses a DHCP server Dynamic mode

The system does not use a DHCP server Static mode

Your set is in a branch office with a rescua- Before R6.2, static mode is mandatory
ble Media Gateway
As of R6.2, dynamic mode is possible
Note:
For more information on such configuration, see:
IP-Phones - e-Reflexes Operations -
Survivability.

2.5.2.2.2.3 Requested IP Parameters for a Static Initialization

The following data must be entered for IP Touch set static initialization:
• IP address (set's address)
• Subnetwork mask
• Router address
• TFTP1 server address (see below for special configurations)
• TFTP2 server address (if needed, see below)
• Use VLAN: this box must be checked to enter a VLAN number
• VLAN number if necessary
• Strict VLAN if necessary (for more information, see: 802.1p/Q and VLAN - VLAN description - Strict
VLAN)
• TFTP port
The TFTP address(es) to enter may differ according to system configuration.
Please contact your system administrator for details on the configuration of your system.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 108/382

Chapter 2 IP deskphones

Duplication Conditions TFTP1 Address TFTP2 Address

The Com Server is not duplicated Com Server main IP N/A

address (or Com Serv-
er physical address if
no main IP address has
been configured)

In a duplicated Com Server configuration where Com Server main IP N/A

the two Com Servers are on the same subnetwork address

In a duplicated Com Server configuration where Com Server A main IP Com Server B main IP
the two Com Servers are on different subnetworks address address

The field TFTP2 Address is available as of R6.1.

The TFTPb Address is used for the survivability mode. It cannot be modified by the user. It is
automatically filled in with the backup IP address, i.e. the IP address of the rescuable Media Gateway
or the Passive Communication Server.
2.5.2.2.3 Connecting the Alcatel-Lucent IP Touch 4028/4038/4068 Sets
The following figure illustrates Alcatel-Lucent IP Touch 4028/4038/4068 set connectors.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 109/382

Chapter 2 IP deskphones

LAN
PC Connector
Connector
Power Supply

Additional Key
Module
Attachment

External Ringing
Signal Connector
Headset
Additional Key Jack
Module Connector

Handset Connector

Figure 2.29: 4028/4038/4068 IP Touch Set Connectors

2.5.2.2.3.1 Connecting the IP Touch Set to the LAN

To connect the set to the LAN:
1. Turn the set over.
2. Plug the RJ45 cable into the set LAN connector.
3. Connect the RJ45 cable to the LAN itself.
2.5.2.2.3.2 Connecting Power Supply
The following procedure does not apply when power supply is provided via PoE.
To supply power via an AC/DC external adapter:
1. Plug the appropriate cable into the set power supply connector
2. Connect the plug to the power supply
Initialization starts.
2.5.2.2.4 Selecting the Initialization Mode
By default, an IP Touch set is configured to initialize in dynamic mode.
To modify the initializing mode:
1. Connect power supply.
2. Before initialization phase 5 starts, press i, then # key.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 110/382

Chapter 2 IP deskphones

The Main menu appears.

3. From the Main menu, choose IP Parameters.
The IP Par menu appears
4. Select your preferred initialization mode: Static or Dynamic.
5. Confirm your entry (press the soft key).
If the initialization mode selected is different from the one previously recorded for the set, the set
initializes again.
2.5.2.2.5 Configuring 802.1x MD5 Authentication
If 802.1x is used, some configuration must be done on the phone at startup. For more information, see:
802.1X Authentication - Configuring 802.1x on IP Touch Sets.
2.5.2.2.6 Initializing the Alcatel-Lucent IP Touch 4028/4038/4068 Sets
By default, set initialization is dynamic. To modify this, see: Selecting the Initialization Mode on page
110.
2.5.2.2.6.1 Dynamic Initialization
1. From the Registration window, enter:
a. Directory number
b. Password
Note:
If the set has already been initialized in the same configuration, there is no need to enter the directory number and
password again.
2.5.2.2.6.2 Static Initialization
1. Connect the set to the LAN and power supply
The Main menu appears.
2. Before initialization phase 5 starts, press i, then # key.
3. From the Main menu, choose IP Parameters.
The IP Parameters menu appears
4. If the current initialization mode is Dynamic, select Static.
5. Enter:
a. IP address
b. Subnetwork mask
c. Router address
d. TFTP1 server address
e. TFTP2 server address (if needed, see: Requested IP Parameters for a Static Initialization on
page 108)
f. TFTP Back server address (cannot be modified)
g. TFTP port
h. Com Server A address (cannot be modified)
i. Com Server B address (cannot be modified)
j. Select Use VLAN
k. VLAN number, if necessary
l. Select Strict VLAN, if necessary
m. DHCP UserClass (as of R8.0.1, cannot be modified)
n. Class (as of R8.0.1, cannot be modified)
6. Press the soft key to save.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 111/382

Chapter 2 IP deskphones

7. Press the soft key to exit the IP Parameters menu.

The set restarts from phase 1 with the new parameters.
The Registration window appears after the set is completely started.
8. Enter:
a. Directory number
b. Password
Note:
Default password is “0000”.
The system completes initialization.
Note:
If the set has already been initialized in the same configuration, there is no need to enter the directory number and
password again.
2.5.2.2.6.3 Restarting Initialization
If you want to change a parameter value, restart initialization.
To restart initialization:
1. Disconnect the IP Touch set.
2. Plug it in again.
3. Execute the initialization procedure as presented above.

2.5.2.3 Connecting Optional Equipment

This is described: Connecting optional equipment on page 100.

2.5.2.4 Programming Personal F1/F2 and Perso Tab Keys

This is described: Key mapping and programming on page 52.

2.5.3 Maintenance
2.5.3.1 Overview
This module describes:
• How to view the IP Touch software version (in OmniPCX Enterprise only).
• The error and information messages that appear during the starting phase.
• The Ethernet link table.

2.5.3.2 Viewing the IP Touch Software Version (in OmniPCX Enterprise Only)
To view the IP Touch software version:
1. From the set home page, select the MENU tab.
2. From the Settings menu, select Settings.
3. Select Parameters.
4. Select Version.
The set software version appears.

2.5.3.3 Error and Information Messages

The table below lists the error and information messages. It has the following format:
Short text = text displayed on the screen, in case of real error or for information.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 112/382

Chapter 2 IP deskphones

Description = status/error description

table 2.11: Starting Phase Information and Error Messages

Short text Description

END Starting phase is terminated (successful or un-

successful)

STARTED Step started

SUCCESS Step successful

FAIL Step failed

RETRYING Retrying step

NO MAC ADDRESS No Ethernet MAC address stored in flash

DHCP NOT RESPONDING Server is not responding

BAD IP ADDRESS IP address is incorrect

BAD ROUTER ADDRESS Router address is incorrect

ROUTER PING FAILED Router not responding to ping

BAD TFTP ADDRESS TFTP server address is incorrect

ADDRESSES MISMATCH Address, mask and router do not match

TFTP NOT RESPONDING TFTP server is not responding

TFTP SERVER ERROR TFTP server error

BAD FILE CONTENT Error found in downloaded file

FILE TOO LARGE File is too large (cannot be downloaded)

SAME VERSION FOUND The version retrieved is the same as the version
running

NEW VERSION FOUND New IP Touch software version found (download)

FLASHING SUCCESS Flashing successful

FLASHING FAILED Failed to flash downloaded binary

TRYING ANOTHER CPU Trying next address from configuration file

NO ETHERNET LINK Ethernet link not connected (LAN port only)

RESOURCES NOT FOUND Resources file not found in flash

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 113/382

Chapter 2 IP deskphones

Short text Description

DOWNLOAD FORCED Download was forced because resources are

missing

NOT COMPATIBLE Downloaded version not compatible with the ter-

minal hardware

initializing First text message after hardware reset and

copyright information

1/5 network start phase 1 is running: the set is starting its network
interface

2/5 network setup Phase 2 is running: the set is looking for IP ad-
dresses

3/5 config download Phase 3 is running: the set is trying to get a

lanpbx file

4/5 binary download Phase 4 is running: the set is downloading a new

binary

5/5 connecting Phase 5 is running: the set is trying to set up the

signaling link with the system

Authentication failure: authentication denied 802.1x authentication has failed: RADIUS server
is unreachable, access is refused to the terminal
on the RADIUS server or the terminal has an in-
correct identity (bad login and/or password).

Authentication success: access granted 802.1x authentication process is complete. The

RADIUS server grants access to the terminal, the
authenticator opens its port.

2.5.3.4 Ethernet Link

By default, IP Touch sets are configured to perform auto-negotiation on both ports (LAN and PC).
Provided that the PC and the LAN switch are also configured to perform auto-negotiation, this is the
best configuration for QoS improvement.
However, depending on the network configuration, it may not always be possible to leave the terminal
in auto-negotiation: link speed and duplex of both ports can be forced to determined values using the
supervisor menu:
• Plug in the set
• Once the set displays initialization, press i, then #
• Select Ethernet Links
• Modify data as requested
The 1000 Mbit/s rate is available on Alcatel-Lucent IP Touch 4028/4038/4068 phone Extended Edition
sets configured in auto-negotiation mode and cannot be forced through the MMI.
A configuration mismatch between the terminal and PC/LAN switch can lead to nasty effects on the
voice quality:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 114/382

Chapter 2 IP deskphones

• No link (or speed mismatch): 8, 9, 11 and 12

• Packet loss (or duplex mismatch): 2, 4, 7 and 14
Note:
Collisions are not detected by the device operating in full-duplex mode: packets from this device are never re-
transmitted if a collision occurs on them.
The following table lists all possible Ethernet port configuration combinations when connecting an IP
Touch set to an external device (switch on LAN side, PC on PC side). For each combination, the table
shows the link status: valid or invalid (duplex or speed mismatch), as described above.

table 2.12: Ethernet Link Combinations

Terminal Port External Device Port Link Status

1 auto-negotiation auto-negotiation Valid

2 auto-negotiation 100-FULL Invalid (packet loss)

3 auto-negotiation 100-HALF Valid

4 auto-negotiation 10-FULL Invalid (packet loss)

5 auto-negotiation 10-HALF Valid

6 100-FULL 100-FULL Valid

7 100-FULL 100-HALF Invalid (packet loss)

8 100-FULL 10-FULL Invalid (no link)

9 100-FULL 10-HALF Invalid (no link)

10 100-HALF 100-HALF Valid

11 100-HALF 10-FULL Invalid (no link)

12 100-HALF 10-HALF Invalid (no link)

13 10-FULL 10-FULL Valid

14 10-FULL 10-HALF Invalid (packet loss)

15 10-HALF 10-HALF Valid

It is not necessary to reset the terminal after changing the configuration.

Note:
To prevent slowness problem on PC when the two ports of an Alcatel-Lucent IP Touch 4028/4038/4068 set are
configured in auto-negotiation mode, if the negotiation has led to a 10 Mbps rate on the PC port and a 100 Mbps
rate on the LAN port, the IP Touch set automatically tries to renegotiate a 10 Mbps rate on the LAN port. This does
not apply to Alcatel-Lucent IP Touch 4028/4038/4068 phone Extended Edition sets.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 115/382

Chapter 2 IP deskphones

2.5.4 Bluetooth - Basic description

2.5.4.1 Overview
The Alcatel-Lucent IP Touch 4068 Phone features Bluetooth® class 3 (1mW) wireless technology. This
technology uses the ISM 2.4 GHz radio frequency band.
Wireless audio accessory Bluetooth® 1.1, 1.2 and 2.0 with headset profile operates with Alcatel-Lucent
IP Touch 4068 Phone.
Optimum audio quality is obtained at up to 3 meters line of sight from the IP touch 4068 terminal. The
range of a Bluetooth® device class 3 is around 10 meters.
The ISM 2.4 GHz radio frequency spectrum may be shared with other applications. Bluetooth® 1.2
version is more robust to the interference caused by Wifi 802.11b and 802.11g devices.
IP Touch Bluetooth® wireless handset reference 3GV27007xx delivered by ALE International is 1.2
enabled and operates with Alcatel-Lucent IP Touch 4068 Phone reference 3GV27043xx from Alcatel-
Lucent OmniPCX Enterprise Communication Server R6.2.
IP Touch Bluetooth® wireless handset reference 3GV27059xx delivered by ALE International is 1.2
enabled and operates with Alcatel-Lucent IP Touch 4068 phone Extended Edition reference
(3GV27062xx) from Alcatel-Lucent OmniPCX Enterprise Communication Server R8.0.1.
Caution:
• The Bluetooth wireless handset 3GV27059xx does not operate with the Alcatel-Lucent IP Touch
4068 Phone (3GV27043xx) set
• The Bluetooth wireless handset 3GV27007xx does not operate with the Alcatel-Lucent IP Touch 4068
phone Extended Edition (3GV27062xx) set
Bluetooth® 1.2 headset accessories operate in 1.2 with Alcatel-Lucent IP Touch 4068 Phone reference
3GV27043xx from Alcatel-Lucent OmniPCX Enterprise Communication Server R6.2.
The Alcatel-Lucent IP Touch 4068 Phone is compliant with the essential requirements of directive
2014/53/EU of the European Parliament and Council (EC member states), and with section 15 of the
Federal Communications Commission (United States) regulations. The set is designed and
manufactured to remain within the SAR (Specific Absorption Rate) radio transmission limits established
by the different countries concerned (FCC for the USA). The set must not be used with Bluetooth®
wireless accessories in countries in which this technology is not authorized.

2.5.4.2 Characteristics of the Bluetooth® wireless technology accessory

The audio quality obtained by accessory users depends on the technical characteristics of the
accessory, notably acoustic coupling.
ALE International recommends the use of Bluetooth® 1.2 headsets complying with recommendation
TIA/EIA-810-A - that specifies a minimum TCLw attenuation of 52 dB.
A headset that does not comply with the recommendation generates an unpleasant echo for the
remote party. To obtain technical information on your accessory, please contact your supplier.

2.5.4.3 Safety rules

Using a Bluetooth® wireless accessory may result in perceptible noise for persons with a hearing aid.
Accessories must not be used in areas with warning signs indicating that electrical devices or products
using radio frequencies must be switched off. Such areas commonly include hospitals, areas where
explosive products are stored or handled, and areas where flammable gases or vapors may be
present.
To limit any risk of interference, ALE International recommends that persons with a pacemaker do not
remain in the proximity of the Alcatel-Lucent IP Touch 4068 Phone set when it is connected to a
wireless accessory.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 116/382

Chapter 2 IP deskphones

2.5.5 Bluetooth - Installation

2.5.5.1 Bluetooth enabling/disabling
In some cases, Bluetooth can be considered a security risk. The Bluetooth feature can be disabled or
enabled.
These configuration details are described in Configuration operations for sets on page 37

2.5.5.2 Commissioning a Bluetooth® Handset

Audio Key

On/Off Hook
Battery Compartment
Handset LED

Figure 2.30: Alcatel-Lucent IP Touch 4068 Phone Bluetooth® Handset

2.5.5.2.1 Connecting the Battery

The battery pack is housed in the battery compartment located in the handset.
The battery pack is reloaded when the handset is placed on its socket. A complete battery load
requires 16 hours.
The autonomy of the battery is of 10 hours in conversation and 33 hours in standby.
The handset Led indicates the battery load state (when the handset is on its socket):
• Led off: the battery is loaded
• Led green steady: the battery is loading
2.5.5.2.2 Binding the Handset
Before a Bluetooth® handset can be used, it must be bound correctly to the Alcatel-Lucent IP Touch
4068 Phone set:
1. On the Alcatel-Lucent IP Touch 4068 Phone set, select the Menu page and navigate to: Settings ->
My phone -> Bluetooth -> Add device
2. On the Bluetooth® handset make a simultaneous long press on the On/Off Hook key and the Audio

key
A sound made of a beep followed by three different tones is audible and the led flashes alternatively
green and orange. The Bluetooth® handset enters in pairing mode for about one minute and then
goes off. The Alcatel-Lucent IP Touch 4068 Phone searches for Bluetooth® equipment, waits until
the type of equipment is detected and displays its address.
3. On the Alcatel-Lucent IP Touch 4068 Phone set, select the relevant equipment and press the Add
key.
A sound made of three different tones confirms the correct installation of the handset. The handset
led flashes green or orange depending on the battery charge.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 117/382

Chapter 2 IP deskphones

2.5.5.2.3 Adjusting Audio Level

There are two ways to adjust the audio level:

• On the Alcatel-Lucent IP Touch 4068 Phone set with the keys

• On the Bluetooth® handset with the key

Consecutive presses adjust the handset volume (3 levels).
2.5.5.2.4 Activating Mute Feature
When the mute feature is enabled your correspondent can no longer hear you.
There are two ways to activate the mute feature:

• On the Alcatel-Lucent IP Touch 4068 Phone set with the mute key

• On the Bluetooth® handset with a long press on the key

2.5.5.3 Commissioning a Bluetooth® Headset

2.5.5.3.1 Binding the Headset
Before a Bluetooth® headset can be used, it must be correctly bound to the Alcatel-Lucent IP Touch
4068 Phone set.
Prerequiste: the headset must be in detectable mode (Refer to the user documentation supplied with
the headset).
1. On the Alcatel-Lucent IP Touch 4068 Phone set, select the Menu page and navigate to: Settings ->
My phone -> Bluetooth -> Add device
The Alcatel-Lucent IP Touch 4068 Phone set searches for Bluetooth® equipment. When the type of
equipment is detected, its address is displayed.
2. Select the relevant equipment and press the Add key. Press the OK key to validate.
3. Enter the headset PIN code by dialing the code on the numeric keypad of the Alcatel-Lucent IP
Touch 4068 Phone. Press the OK key to validate.
An acknowledgement message and the headset icon are displayed on the Alcatel-Lucent IP Touch
4068 Phone set screen.
2.5.5.3.2 Adjusting Audio Level
There are two ways to adjust the audio level:

• On the Alcatel-Lucent IP Touch 4068 Phone set with the keys

• On the Bluetooth® headset (Refer to the user documentation supplied with the headset)

2.5.5.4 Removing a Bluetooth® Equipment (Headset or Handset)

1. On the Alcatel-Lucent IP Touch 4068 Phone set select the Menu page and navigate to Settings ->
My phone -> Bluetooth -> My devices
The Alcatel-Lucent IP Touch 4068 Phone set displays the bound Bluetooth® equipment.
2. Select the equipment to be removed and press the Remove dvc key. Press the OK key to validate.
The equipment is removed and a acknowledgement message is displayed.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 118/382

Chapter 2 IP deskphones

2.6 IP Touch 4008/4018 Phone (8 series)

2.6.1 Ergonomics of 8/9 Series sets
2.6.1.1 Alcatel-Lucent IP Touch 4028/4038/4068 and Alcatel-Lucent 4029/4039 Digital Phone set
description
Although there are differences in the aspect and operation of these sets, their layout is identical but for
the screen and number of available soft keys.
Screen Inclination
Set Screen Adjustment Alarm LED

Soft Keys

Dialing Keypad Fixed keys

Headset jack
Alphabetic Keyboard

Alt Key Space Bar

Figure 2.31: Alcatel-Lucent IP Touch 4068 Phone set layout

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 119/382

Chapter 2 IP deskphones

Set Screen Screen Inclination

Alarm LED
Adjustment

Soft Keys

Dialing Keypad Fixed keys

Headset jack Alphabetic Keyboard

Alt Key Space Bar

Figure 2.32: Alcatel-Lucent IP Touch 4038 Phone and Alcatel-Lucent 4039 Digital Phone set layout

Screen Inclination
Set Screen Adjustment Alarm LED

Soft Keys

Dialing Keypad Fixed keys

Headset jack Alphabetic Keyboard

Alt Key Space Bar

Figure 2.33: Alcatel-Lucent IP Touch 4028 Phone and Alcatel-Lucent 4029 Digital Phone set layout

2.6.1.1.1 Set equipment

The Alcatel-Lucent IP Touch 4028/4038/4068 and Alcatel-Lucent 4029/4039 Digital Phone sets all
include the following items:
• Corded comfort handset
• Hands-free station speaker

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 120/382

Chapter 2 IP deskphones

• A number of keys
• A number of LEDs
• A set screen
• Additional key module (optional)
• Wall mounting kit (optional)
• "Big Foot" Foot stand 60° (optional)
• Bluetooth headset (available on Alcatel-Lucent IP Touch 4068 Phone set only)
2.6.1.1.2 Connecting optional equipment
2.6.1.1.2.1 External station speakers
The headset jack is located on the left side of the Alcatel-Lucent IP Touch 4028/4038/4068 sets
The 3.5 mm female jack can receive an external speakers' jack.
Customize your set to take the external station speaker into account:
1. From the Menu tab, select Settings
2. In the next screen, select My extension on an Alcatel-Lucent IP Touch 4068 Phone or Alcatel-
Lucent IP Touch 4038 Phone set, My phone on an Alcatel-Lucent IP Touch 4028 Phone set
3. In the next screen, select Jack plug
Enter your password and press Apply
4. Select Loudspeaker and press the OK button.
5. Plug the external station speaker jack into the associated set connector.
2.6.1.1.2.2 Plugging a PC or an IP phone set to an IP Touch set
The Alcatel-Lucent 8 series set includes a internal LAN switch.
This switch allows to connect:
• A PC
• A cascaded Alcatel-Lucent 8 series set

IP Touch Set PC

OR
LAN Port
PC Port

LAN
Cascaded Set

Figure 2.34: Ip Touch set connections

The internal switch has three ports:

• A LAN port
• An internal port

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 121/382

Chapter 2 IP deskphones

• A PC port, to connect a PC or another set to the LAN via the Alcatel-Lucent 8 series set
The PC port can be disabled and can be configured to force PC packets to get the default VLAN
tag. For configuration, see: Phone COS on page 40.
The internal switch privileges VoIP traffic over PC port traffic.
This switch has two waiting queues:
• The HPQ (High Priority Queue) to proceed all packets from the terminal
• The LPQ (Low Priority Queue) to proceed packets from the PC port
The switch proceeds seven HPQ packets for an LPQ packet.
Exception: packets from the PC port use the HPQ when they are tagged with a 802.1p tag and when
the tag value is superior or equal to 4.
The 802.1p tag is an IEEE standard tag which specifies the priority of the packet.
Restrictions:
• Only one additional set of equipment can be connected to the PC port
• The main IP Touch set must be locally powered to accept a cascaded IP phone
• The PC port is not available on Alcatel-Lucent IP Touch 4008 Phone sets
2.6.1.1.3 Set keys
The Alcatel-Lucent IP Touch 4028/4038/4068 and Alcatel-Lucent 4029/4039 Digital Phone sets include:
• A dialing keypad
• An alphabetic keyboard with 34 keys
Five versions are available: French, German, International, Scandinavian and American.
• Fixed function keys
• A navigator consisting of 4 directional navigation keys
• Programmable keys (72 keys on the Perso tab and 2 personal keys)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 122/382

Chapter 2 IP deskphones

2.6.1.2 Alcatel-Lucent 8/9 series and Alcatel-Lucent 4019 Digital Phone set description
Dialing Keypad Set Screen

Fixed Function Keys

Programmable Keys

Fixed Function Keys

Figure 2.35: Alcatel-Lucent IP Touch 4018 phone Extended Edition and Alcatel-Lucent 4019
Digital Phone Set Layout

2.6.1.2.1 Set equipment

The Alcatel-Lucent IP Touch 4018 phone Extended Edition and Alcatel-Lucent 4019 Digital Phone sets
include the following items:
• Corded comfort handset
• Hands-free station loudspeaker (basic station loudspeaker, no hands-free feature on Alcatel-Lucent
4019 Digital Phone set)
• A number of keys
• A number of LEDs
• A set screen
• Wall mounting kit (optional)
• "Big Foot" Foot stand 60° (optional)
2.6.1.2.2 Set keys
The Alcatel-Lucent IP Touch 4018 phone Extended Edition and Alcatel-Lucent 4019 Digital Phone sets
include:
• A dialing keypad with 12 keys
• Fixed function keys
• Fixed navigation keys consisting of:
• A bidirectional navigation key (up and down)
• A back key
• An OK key
• Six programmable keys

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 123/382

Chapter 2 IP deskphones

2.6.1.3 Support for long names and non-Latin characters

The OmniPCX Enterprise provides the following support for long names and non-Latin characters on
Alcatel-Lucent 8/9 series sets:
As of R7.0:
• Display of long names and names in non-Latin characters for callers, trunk groups, speed dialing
numbers, and entities
As of R8.0:
• Display of programmed key and directory key names in non-Latin characters
• Dial by name using non-Latin characters
• Input of programmed key names using non-Latin characters
• Conservation of key names in non-Latin characters when changing sets, changing an additional key
module, or migrating a user between nodes, provided the new set device supports non-Latin
characters.
Note:
Display of long names and names in non-Latin characters is not available in the Hotel/Hospital application.
Note:
Dial by name and input of non-Latin characters is available on Alcatel-Lucent 4029/4039 Digital Phone sets as of
R8.0 and on Alcatel-Lucent IP Touch 4028/4038/4068 sets as of R8.0.1.
2.6.1.3.1 Display of long names and non-Latin characters
The system allows for Alcatel-Lucent 8/9 series sets to display:
• Names up to 30 characters long in full (as of R7.0)
• Cyrillic, Greek, Chinese, Japanese, and Korean characters (as of R7.0)
• Hebrew characters (on Alcatel-Lucent IP Touch 4028/4038/4068, as of R9.1 and Alcatel-Lucent
4029/4039 Digital Phone, as of R10.0)
This includes names for:
• The caller when set is ringing
• The last caller and last number dialed (on the set's Info and Events pages)
• Trunk groups
• Speed dialing numbers
• Entities
Note:
User and trunk group names are displayed for internal calls and after a transfer. By default names display for calls
to and from other nodes in an ABC-F network. This feature is configurable. See: UTF8 resolution in an ABC-F
network on page 51.
As of Release 8.0, the system allows for Alcatel-Lucent 8/9 series sets to display:
• Programmed key names on the Perso Pages (Alcatel-Lucent IP Touch 4028/4038/4068 and Alcatel-
Lucent 4029/4039 Digital Phone sets)
• Directory key names (Alcatel-Lucent 8/9 series, Alcatel-Lucent 4019 Digital Phone, and MIPT sets)
A configuration attribute has been created for each name that can be displayed in non-Latin
characters. These configuration attributes encode characters in 8-bit Unicode Transformation Format
(UTF-8), which allows any character to be represented in the Unicode standard.
A set displays a name in non-Latin characters if:
• The node is at the appropriate software release for the feature
• The set allows for the type of characters used
• The set's Language ID is compatible with the character type of the name to display

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 124/382

Chapter 2 IP deskphones

• The UTF-8 name attribute has been configured

If any of these criteria are not met, the set displays the standard (non-UTF-8) name in Latin characters.
To configure UTF-8 name attributes, see: Configuring names in non-Latin characters on page 47
The following table shows the types of characters, in addition to Latin, that are available for each set.
The number of characters displayed depends on the type of characters. The table shows the
approximate maximum number of characters displayed for each set.

table 2.13: Available character types on set displays

Set Max Cyrillic Greek Chinese Japa- Korean Hebrew Thai

charac- nese
ters dis-
played
(approx.)

4008,401 20 Yes Yes No No No No No

8, 4019

4028,402 24 Yes Yes Yes Yes Yes Yes No

9

4038,403 30 Yes Yes Yes Yes Yes Yes No

9, 4068

MIPT 18 Yes Yes No No No No No

8028/803 Yes Yes Yes Yes Yes Yes Yes

8/8068,
80x8s
Premium
Desk-
Phone
and
8029/803
9

The following figure shows a 4068 set screen display of names of the last numbers called. The set's
Language ID is Russian.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 125/382

Chapter 2 IP deskphones

Figure 2.36: Example display of a 4068 Set with Russian as Language ID

Since the set's Language ID is Russian, the first name is displayed in Latin characters (rather than
Chinese), the second name is in Latin characters and the third name is in Cyrillic characters.
2.6.1.3.2 Input of non-Latin characters
Starting with Release 8.0, an Input Method Editor (IME) is available on Alcatel-Lucent 8/9 series sets,
enabling input of non-Latin characters, that is, Cyrillic characters and CJK (China, Japan, Korea)
characters.
The IME enables the following features:
• Dial by name using non-Latin characters
• Input of names for programmed keys (Perso Pages) using non-Latin characters
The type of characters currently in use on a telephone set is associated with an input method: Latin
(default), Cyrillic, Pinyin, Jamo, Stroke, or Zhuyin. To make an input method other than Latin available
on a set, configure it in the Phone Class of Service (see Configuring Phone COS on page 40).
Note:
Japanese is not supported by the IME on Alcatel-Lucent 8/9 series.
Note:
The IME is available on Alcatel-Lucent 4029/4039 Digital Phone sets as of R8.0 and on Alcatel-Lucent IP Touch
4028/4038/4068 sets as of R8.0.1.
Note:
For information on the operation of the IME, refer to the document [3].
For more information on the operation and configuration of Dial by name, refer to the document [3].

2.6.1.4 Display of external called number

According to a system option, when dialing an external number the set display either shows the trunk
group name or the number entered by the user on the keypad (see: Enabling external called number
display on page 38).

2.6.1.5 Access to external applications

8 series (IP Touch) users can have direct access to external applications from their set via a soft key.
This is available on:
• 4028 IP Touch sets
• 4038 IP Touch sets
• 4068 IP Touch sets
External applications are interfaced to IP Touch sets and the OmniPCX Enterprise with the
Presentation Server, refer to the document [10].

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 126/382

Chapter 2 IP deskphones

This feature proves particularly useful for video conference implementation.

The soft key dedicated to an application is always available from the Menu page, where application soft
keys are displayed systematically displayed under telephone feature keys.

Thu 16
09/23/03 May 2006 9:58
9:58
AM

MENU PERSO INFO

Laura
Settings JACKSON
Outgoing calls
Ir 7
Appointment
Carol SMITHForward
Textmail
New is calling Lock
Call

Events
Record Video
No camp on

Figure 2.37: Example of access to a video application from a 4068 IP Touch set

When several applications can be accessed, the system determines their priority on the set screen,
see: Defining external applications on page 38.
As of R7.1, application soft keys can be displayed when the set is being used for its telephone
capabilities.

Thu 18 May 2006 10:43

Graziella Moreno
Conversation 1:04

Enquiry call Malicious call

Forbid camp on Video

Figure 2.38: Example of access to an external application when the set is in conversation

Application soft keys are displayed according to:

• Set type (see above)
• Application status:
• Public vs. restricted
• Configured to appear according to telephone call status
• Telephone call status:
• Incoming call
• Initiated call
• Delivered call (sent to the other party)
• Established call (in conversation)
• Conference call (in conversation with several parties)
• On hold call
• Disconnected call
Soft key labels are sent to the sets when the external application is launched. They cannot be modified
while the application is running.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 127/382

Chapter 2 IP deskphones

Application soft keys are displayed regardless of feature availability. If, for example, an IP Touch set is
in conversation with a Reflexes set, the Video soft key of the above example is available even though
no video conference can take place on a Reflexes set.

2.6.1.6 Before mounting an Alcatel-Lucent 8/9 series set on a wall

The set must be prepared to ensure the handset does not fall off the set when fixed on a wall.
1. Locate the position of the dowel to adjust on the set.

2. Move the dowel up to extract it

3. Turn it upside down.

4. Push the upside down dowel back into its slot

Once the set is fixed on the wall, the dowel hook will maintain the handset in place.
To screw the set to the wall kit, proceed as described in the wall kit documentation.

2.6.2 Commissioning
2.6.2.1 Foreword
Operations described in this chapter apply to Alcatel-Lucent IP Touch 4018 phone Extended Edition
sets operating in NOE and SIP modes.

2.6.2.2 Connecting a Set

The following figure illustrates Alcatel-Lucent IP Touch 4018 phone Extended Edition connectors.
Alcatel-Lucent IP Touch 4008 Phone connectors are identical, with the difference that there is no PC
connector.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 128/382

Chapter 2 IP deskphones

LAN
PC Connector
Connector
Power Supply

External Ringing
Signal Connector

Handset Connector

Figure 2.39: Alcatel-Lucent IP Touch 4018 phone Extended Edition Connectors

2.6.2.2.1 Connecting the IP Touch Set to the LAN

To connect the set to the LAN:
1. Turn the set over
2. Plug the RJ45 cable into the set LAN connector
3. Connect the RJ45 cable to the LAN itself
2.6.2.2.2 Connecting Power Supply
The following procedure does not apply when power supply is provided via PoE.
To supply power via an AC/DC external adapter:
1. Plug the appropriate cable into the set power supply connector
2. Connect the plug to the power supply
Initialization starts.
2.6.2.2.3 Plugging a PC or an IP Phone Set to an IP Touch Set
Only one additional item of equipment can be connected to the set connector labeled PC on an IP
Touch set.
Notes:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 129/382

Chapter 2 IP deskphones

• Such a piece of equipment cannot be connected to Alcatel-Lucent IP Touch 4008 Phone sets.
• If the main IP Touch set is not powered, the cascading device does not work properly.
• If 802.1x authentication is used, the PC port cannot be used until the IP Touch set authentication is completed.

2.6.2.3 Initializing or Reinitializing a Set

A set reinitialization (or reboot) is required to take into account new parameters or changes.
To restart initialization:
1. Disconnect the IP Touch set.
2. Plug it in again, the set boots.
When configuration is modified from the set, the set automatically reboots.

2.6.2.4 Accessing the Admin Menu (MMI)

• Connect the set to the LAN and power supply
For more information, see: Connecting a Set on page 128
• During set initialization (phase 1/5 to 5/5) , press the i, then # keys.
If the set password is required, enter the set password and press #
As these sets do not come with an alphabetic keyboard, to type the password, use the numeric
keypad:
1. For each letter, press the key on which the corresponding letter is printed (in orange characters)
For example: for alcatellucent enter: 2522835582368
2. Once the full password is entered, press the # key
Note:
For sets without an alphabetic keypad, you may use a password limited to digits.
The set administration menu is displayed.

2.6.2.5 Configuring 802.1x

If 802.1x is used, some configuration must be done on the phone at startup. For more information, see:
802.1X Authentication - Configuring 802.1x on IP Touch Sets.

2.6.2.6 Configuring the VLAN

VLAN can be configured in three different ways:
• Manually on each set
• Automatically through DHCP
• Automatically through LLDP (as of Alcatel-Lucent OmniPCX Enterprise Communication Server
R9.1)
In case of conflict between methods, the priority is the following:
1. LLDP-MED (highest priority)
2. DHCP
3. Set
2.6.2.6.1 Selecting VLAN from the Set
To configure manually the VLAN on the set, see: 802.1p/Q and VLAN - Configuration procedure -
Configuring 802.1Q Tagging.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 130/382

Chapter 2 IP deskphones

2.6.2.6.2 Selecting VLAN Assignment via DHCP

To enable automatic VLAN assignment through DHCP, see: DHCP server - Detailed description -
Automatic VLAN Assignment (AVA).
2.6.2.6.3 Selecting VLAN Assignment via LLDP-MED
In this case, the set must be connected to a switch providing LLDP-MED messages. The VLAN
acquirement option must be validated from the set.
To validate the LLDP_MED VLAN option, see: 802.1p/Q and VLAN - Configuration procedure -
Configuring 802.1Q Tagging

2.6.2.7 Sending Set Information via LLDP-MED

Set information can be sent to the nearby LAN switch to optimize its configuration. Set information is
set via LLDP-MED.
Set information is sent only when the switch requests it and when sets are allowed to send their
information.
The set information sent is:
• Power Management
The set sends its electric power consumption to the LAN switch. This information allows a feeding
switch (POE according to RFC 802.1af) to adjust its configuration.
• Inventory Publication
The set sends information relating to itself, i.e.
• Hardware revision
• Software version
• Firmware version
• Serial number
• Manufacture name (set to ALE International)
• Model name (set to NOE 4008 EE or NOE 4018 EE)
• Asset ID (set with the SIP configuration file to the set MAC address)
The set must be configured to sent Power Management and Inventory Publication information:
1. From the set administration menu, scroll up/down to display LLDP and press OK
2. Scroll up/down to display Power Manage and press OK to set the value to Yes
3. Scroll up/down to display Inventory Pub and press OK to set the value to Yes
4. Press # to apply changes
5. Press the back/exit key

2.6.3 Commissioning in NOE Mode

2.6.3.1 Overview
This chapter presents the actions required for commissioning Alcatel-Lucent 8 series sets in NOE
mode.
For readability purposes, the term "set" is used in the rest of this document to refer to Alcatel-Lucent IP
Touch 4008/4018 phone Extended Edition sets.
As soon as a set is powered up:
1. If the set initialization mode is dynamic (default option): the set connects to a DHCP server to
acquire its IP parameters and the PCX address used to download configuration files and binaries
(TFTP mode)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 131/382

Chapter 2 IP deskphones

For more information, see: Commissioning the Set in Dynamic Mode on page 132
2. If the set initialization mode is static: the set uses its internal parameters. All necessary information
must be manually configured on the set itself such as IP parameters and PCX address
For more information, see: Commissioning the Set in Static Mode on page 133
3. The set retrieves the lanpbx.cfg configuration file (TFTP) and checks that the line:
APPLICATION_TYPE =APPL_NOE|APPL_SIP indicates the NOE run mode.
4. The set retrieves the binary files from the PCX (TFTP mode). The available binary files are:
• bin40x8 (bootloader)
• noe40x8 (application)
• dat40x8 (resources, such as ringing melodies)
5. The set requests a directory number and password at the end of the process
Note:
In case of conflict between static and dynamic operating modes, the dynamic mode takes priority.

2.6.3.2 Prerequisites
Before commissioning a set, you must check:
• The set is declared as IPTouch 40x8 in the OmniPCX Enterprise, see: Declaring an IP Phone on
page 28.
• The lanpbx.cfg configuration file is registered in the download server
The set requests the lanpbx.cfg file for its commissioning. This file contains one or more line.
Each line corresponds to one node of the network and contains the main IP address(es) of the Com
Server(s) on which sets are declared.
The lanpbx.cfg file is built with the lanpbxbuild tool. For more information, see: lanpbxbuild -
Operation.
• When the set initializing mode is dynamic, the DHCP server must be adequately configured. The
following parameters must be configured:
• Set IP address
• IP subnetwork mask
• Router IP address
• TFTP server address. This parameter must be entered in the siaddr field (this entry is also
called Next server) or in option 66.
• If necessary, VLAN parameters
To configure the DHCP server, see: DHCP server - Detailed description

2.6.3.3 Commissioning the Set in Dynamic Mode

By default, the set starts in dynamic mode and operates in NOE mode (factory settings).
To check that the set initialization mode is dynamic and the operating mode is set to NOE:
1. From the set administration menu, scroll up/down to display IP Parameters and press OK
2. Scroll up/down to display IP mode: xxxx
The available initialization modes are:
• Static: the IP parameters to use are manually configured on the set
• Dynamic (default option): IP parameters are acquired from a DHCP server
• Alcatel Dyn: IP parameters are acquired from a DHCP server delivered by ALE International
3. If necessary, press successively OK to change the initialization mode to Dynamic or Alcatel Dyn
4. Press # to apply changes

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 132/382

Chapter 2 IP deskphones

5. From the set administration menu, scroll up/down to display Soft Info and press OK
6. Scroll up/down to display RunMode: xxxx
The available run modes are: NOE (default option) or SIP
7. If necessary, press the OK button to change the run mode to NOE
Note:
It is not possible to modify the run mode for Alcatel-Lucent 8 series sets. This option is only available for
Alcatel-Lucent IP Touch 8 series phone Extended Edition.
8. Press # to apply changes
9. Press the back/exit key

2.6.3.4 Commissioning the Set in Static Mode

2.6.3.4.1 Selecting the Set Initialization Mode (Static)
By default, a set is configured to initialize in dynamic mode.
To modify the initialization mode:
1. From the set administration menu, scroll up/down to display IP Parameters and press OK
2. Scroll up/down to display IP mode: xxxx
The available initialization modes are: Dynamic (default option), Alcatel Dyn or Static
If the desired mode is displayed, you can skip IP mode selection
3. If Dynamic is displayed, press successively OK to change the initialization mode in Static
4. Press # to apply changes
2.6.3.4.2 Configuring the Set IP Parameters
1. From the set administration menu, scroll up/down to display IP Parameters and press OK.
2. Scroll up/down to display and modify set IP parameters:
• IP @: Set IP address
• Subnet: IP subnetwork mask
• Router: Router IP address
3. Press # to apply changes
2.6.3.4.3 Configuring the Download Server Parameters
1. From the set administration menu, scroll up/down to display IP Parameters and press OK
2. Scroll up/down to display and modify download server parameters:
• TFTP1: enter the download server IP address
• TFTP2: enter a second download server IP address (if necessary)
• TFTPb: this option cannot be modified
• TFTP port: 69 (default option)
3. Press # to apply changes
2.6.3.4.4 Selecting the NOE Operating Mode
By default, a set is configured to operate in NOE mode.
1. From the set administration menu, scroll up/down to display Soft Info and press OK
2. Scroll up/down to display RunMode: xxxx
The available run modes are: NOE (default option) or SIP
If the desired run mode is displayed, you can skip run mode selection
3. If necessary, press the OK button to change the run mode in NOE

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 133/382

Chapter 2 IP deskphones

Note:
It is not possible to modify the run mode for Alcatel-Lucent 8 series sets. This option is only available for
Alcatel-Lucent IP Touch 8 series phone Extended Edition.
4. Press # to apply changes
5. Press the back/exit key

2.6.4 Commissioning in SIP Stand-Alone Mode

2.6.4.1 Overview
This chapter presents the actions required for commissioning Alcatel-Lucent IP Touch 4008/4018
phone Extended Edition sets in SIP standalone mode.
For readability purposes, the term "set" is used in the rest of this document to refer to Alcatel-Lucent IP
Touch 4008/4018 phone Extended Edition sets.
As soon as it is powered up:
1. Depending on the initialization mode:
• If the set initialization mode is dynamic (default option): the set connects to a DHCP server to
acquire its IP parameters and the download server parameters.
For more information, see: Commissioning the Set in Dynamic Mode on page 135
• If the set initialization mode is static: the set uses its internal parameters. All necessary
information must be manually configured on the set itself such as:
• IP parameters
• Download server parameters (TFTP, HTTP or HTTPS mode)
• Operating mode (SIP)
For more information, see: Commissioning the Set in Static Mode on page 136
2. Depending on the operating mode:
• If the operating mode is NOE (factory settings), the set retrieves the lanpbx.cfg (TFTP) and
checks the line: APPLICATION_TYPE = APPL_NOE|APPL_SIP.
If the parameter is set to APPL_SIP, the set switches in SIP mode and automatically reboots. It
requests the DHCP server to obtain the access parameters to the download server (TFTP, HTTP
or HTTPS mode) using the vendor class alcatel.sip.0.
• If the operating mode is SIP, the set retrieves the configuration files from the download server. In
SIP mode, the downloaded configuration files are:
• sipconfig.txt
• sipconfig-MacAddress.txt
3. The set retrieves the SIP binary files from the download server. The available binary files for Alcatel-
Lucent IP Touch 4018 phone Extended Edition sets are:
• bin4018 (bootloader)
• noesip4018 (application)
• datsip4018 (resources including the ringing melodies)
Except for their name, Alcatel-Lucent IP Touch 4008 phone Extended Edition set binary files are
identical.
4. The set requests a directory number and password at the end of the process
Note:
In case of conflict between static and dynamic operating modes, the dynamic mode takes priority.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 134/382

Chapter 2 IP deskphones

2.6.4.2 Prerequisites
Before commissioning a set, you must check that:
• The set is declared as SIP extension in the OmniPCX Enterprise, see: Declaring an IP Phone on
page 28.
• When the set initializing mode is dynamic, the DHCP server must be adequately configured. The
following parameters must be configured:
• Set IP address
• IP subnetwork mask
• Router IP address
• Download server parameters (HTTPS, HTTP or TFTP).
• For TFTP server: DHCP option is 66: siaddr field (this entry is also called Next server)
• For HTTP (or HTTPS) server: DHCP option is 43. This option includes a sub-option 67 in
which the download URL must be entered for the vendor class "alcatel.sip.0"
• If necessary, VLAN parameters
To configure the DHCP server, see: DHCP server - Detailed description
• If needed, the lanpbx.cfg file is configured with the parameter APPLICATION_TYPE set to
APPL_SIP (SIP mode).
The lanpbx.cfg file is built with the lanpbxbuild tool. For more information, see: lanpbxbuild -
Operation.
• The sipconfig.txt and sipconfig-MacAddress.txt configuration files are registered in the
download server
• The set binary files are registered in the download server in the same location as the configuration
files

2.6.4.3 Commissioning the Set in Dynamic Mode

By default, the set starts in dynamic mode and operates in NOE mode (factory settings).
Start the set and check that the set initialization mode is dynamic and the operating mode is set to SIP.
Procedure:
1. From the set administration menu, scroll up/down to display IP Parameters and press OK
2. Scroll up/down to display IP mode: xxxx
The available initialization modes are:
• Static: the IP parameters to use are manually configured on the set
• Dynamic (default option): IP parameters are acquired from a DHCP server
• Alcatel Dyn: IP parameters are acquired from a DHCP server delivered by ALE International
3. If necessary, press successively OK to change the initialization mode in Dynamic or Alcatel Dyn
4. Press # to apply change
5. From the set administration menu, scroll up/down to display Soft Infos and press OK
6. Scroll up/down to display RunMode: xxxx
The available run modes are: NOE (default option) or SIP
7. If necessary, press the OK button to change the run mode in SIP
8. Press # to apply change
9. Press the back/exit key

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 135/382

Chapter 2 IP deskphones

2.6.4.4 Commissioning the Set in Static Mode

2.6.4.4.1 Selecting the Set Initialization Mode (Static)
By default, a set is configured to initialize in dynamic mode.
To modify the initialization mode:
1. From the set administration menu, scroll up/down to display IP Parameters and press OK
2. Scroll up/down to display IP mode: xxxx
The available initialization modes are: Dynamic (default option), Alcatel Dyn or Static
If the desired mode is displayed, you can skip IP mode selection
3. If Dynamic is displayed, press successively OK to change the initialization mode in Static
4. Press # to apply changes
2.6.4.4.2 Configuring the Set IP Parameters
1. From the set administration menu, scroll up/down to display IP Parameters and press OK.
2. Scroll up/down to display and modify set IP parameters:
• IP @: Set IP address
• Subnet: IP subnetwork mask
• Router: Router IP address
3. Press # to apply changes
2.6.4.4.3 Configuring the Download Server Parameters
1. From the set administration menu, scroll up/down to display SIP Download and press OK
2. Scroll up/down to select the transfer mode (TFTP, HTTP, or HTTPS)
• For TFTP mode: the download server parameters are configured in the IP Parameters menu as
follows:
1. From the set administration menu, scroll up/down to display IP Parameters and press OK
2. Scroll up/down to display and modify download server parameters:
• TFTP1: enter the download server IP address
• TFTP2: enter a second download server IP address (if necessary)
• TFTPb: this option cannot be modified
• TFTP port: 69 (default option)
• For HTTP mode: enter the IP address, port number and access path
• For HTTPS mode: enter the IP address, port number and access path
Note:
To guarantee the authentication and the confidentiality of the files, the file download via HTTPS requires
certificates. For more information on certificates, see: Managing Certificates on page 146
3. Press # to apply changes
2.6.4.4.4 Selecting the SIP Operating Mode
By default, a set is configured to operate in NOE mode.
1. From the set administration menu, scroll up/down to display Soft Info and press OK
2. Scroll up/down to display RunMode: xxxx
The available run modes are: NOE (default option) or SIP
If the desired run mode is displayed, you can skip the run mode selection
3. If necessary, press the OK button to change the run mode in SIP
4. Press # to apply changes
5. Press the back/exit key

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 136/382

Chapter 2 IP deskphones

2.6.4.5 Configuring SIP Servers Parameters

2.6.4.5.1 SIP Server Overview
The set sends a registration request to the SIP registrar server when starting in SIP mode. The
registrar server transmits data including the name and IP address of the SIP set to the location server.
In SIP mode, a set communicates with a SIP Proxy server. The SIP proxy server is an intermediate
entity that operates as a client or a server by receiving or transmitting requests from the sets. A SIP
outbound proxy can be used for outgoing calls
The Alcatel-Lucent OmniPCX Enterprise Communication Server embeds a SIP proxy and SIP registrar.
For more information, see: SIP - Detailed description - PCX SIP components
To send requests to SIP servers, the set uses parameters defined in the configuration files
(sipconfig.txt or sipconfig-MacAddress.txt files) and registered in its flash memory. Each
SIP server is identified by an IP address and a port number.
2.6.4.5.2 SIP Server Redundancy
To improve system operating reliability, Alcatel-Lucent IP Touch 4008/4018 phone Extended Edition
sets support SIP server redundancy. For each SIP server, the configuration files include two sets of SIP
server parameters (main and backup).
When the set cannot reach the main SIP server, the backup SIP server is used. If the main and backup
SIP servers cannot be reached, the set turns to SIP or PCS survivability mode, according to
configuration (see: IP-Phones - e-Reflexes OperationsSIP Survivability). In SIP survivability mode, the
set checks periodically the availability of SIP servers. When they can be reached, the set reboots and
returns to SIP mode. To check the availability of SIP servers, the set periodically sends an option
message to these SIP servers.
Which redundancy applies?
Two types of SIP server redundancy can apply:
• A SIP outbound proxy redundancy (called type 1 in the rest of this paragraph).
The SIP outbound proxy servers (main and backup) must be specified in the configuration files.
• A SIP registrar/proxy redundancy (called type 2 in the rest of this paragraph).
The SIP proxy servers (main and backup) or SIP registrar servers (main and backup) must be
specified in the configuration files
When the two types of SIP server redundancy are configured, type 1 overrides type 2.
2.6.4.5.3 Configuring SIP Server IP Address and Port Number
The SIP servers (proxy, registrar, and outbound proxy) must be configured in sipconfig file.
1. Edit the sipconfig.txt or sipconfig-MacAddress.txt files.
This operation can be performed via the SIP Manager application of the OmniVista 4760 or a text
editor (configuration files are text files).
2. To configure type 1 redundancy, configure the following parameters:
• outbound_proxy_addr= and outbound_proxy_port=: Enter the IP address and port
number of the first outbound proxy server
• outbound_proxy2_addr= and outbound_proxy2_port=. Enter the IP address and port
number of the second outbound proxy server
3. To configure type 2 redundancy, configure the following parameters:
• proxy_addr= and proxy_port=. Enter the IP address and port number of the first proxy
server

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 137/382

Chapter 2 IP deskphones

•registrar_addr= and registrar_port=. Enter the IP address and port number of the
second registrar server
• proxy2_addr= and proxy2_port=. Enter the IP address and port number of the second
proxy server
• registrar2_addr= and registrar2_port=. Enter the IP address and port number of the
second registrar server
4. When these configuration files are modified, reboot the set
Note:
For PCS survivability, the pcs-addr= and pcs_port= parameters must also be configured in sipconfig file.

2.6.4.6 Updating SIP Binaries on a Set

To update SIP binaries on a set, SIP binaries must be made available on the download server
(bin40x8, noesip40x8, and datsip40x8), and the set must reset. This can be done in the following ways:
• Manually by disconnecting the set and plugging it in again (see: Initializing or Reinitializing a Set on
page 130)
• Automatically after a polling timer defined in the configuration file (field Binary polling timer)
registered in the set at first initialization. The set monitors the server to check if new binary files are
available. When there are new binary files, the set automatically restarts and proceeds with a binary
update.

2.6.4.7 Phone Features in SIP Standalone Mode

Alcatel-Lucent IP Touch 4008/4018 phone Extended Edition sets in SIP standalone mode benefit from
the same PCX features as SIP extensions (SEPLOS mode).
PCX features can be activated by dialing PCX prefixes.
For some features, the user does not need to know the prefix and can use a direct key. In this case,
corresponding prefixes are defined in the configuration file and sent to the terminal at initialization.
2.6.4.7.1 Direct Key Management
In SIP mode, Alcatel-Lucent IP Touch 4008/4018 phone Extended Edition keys have a specific
meaning.

table 2.14: Keys Meaning in SIP Standalone Mode

0 Line 1

1 Line 2

2 Speed dialing

3 Speed dialing

4 Speed dialing

5 Speed dialing

2.6.4.7.2 Multilines
The sets allow to set two calls simultaneously.
The Line 1 key and the Line 2 key are used to speak with two parties alternatively.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 138/382

Chapter 2 IP deskphones

2.6.4.7.3 Three-Party Conference

A three-party conference can be performed locally on a set in SIP mode.
When two calls are set, the conference is available. The word Conference is displayed on the set.
Press the OK key to start the conference. Press the OK key (or hang up) to end the conference.
2.6.4.7.4 Speed Dialing Keys
The user can make a call by pressing one of the speed dialing key. The set automatically dials the
content of the key.
A speed dialing key is configured with:
• The first name and the last name of remote party
• The URI or the call number of the remote party
Speed dialing keys can be programmed:
• Locally on the set
• Via the set configuration file
If a speed dialing key is configured via the configuration file, it cannot be modified from the set.
2.6.4.7.5 Voice Mail
In SIP mode, the set can access voice mail via the voice mail key.
The voice mail key is configured with the voice mail URI or voice mail call number in the SIP
configuration file.
To access voice mail press the voice mail key. When connected, voice guides are played to help you
select options from the set keypad. Digits are transmitted via DTMF coding.
When a new message has been received, the voice mail LED is on.
Note:
In conversation, a SIP set switches automatically to DTMF mode.

2.6.4.8 SIP Configuration Files Description

2.6.4.8.1 Overview
The sipconfig.txt and sipconfig-MacAddress.txt files are built with the SIP Device
Management application (SDM). The SDM application is a part of the Alcatel-Lucent OmniVista 4760
Network Management System. For more information on this application, see the OmniVista 4760
technical documentation. These files are text files and can be modified with a text editor.
Configuration files are:
• sipconfig.txt: this file is optional and contains all parameters required for operation. This file
configures all SIP sets of the system with the same parameters.
If this file does not exist, only the parameters contained in the sipconfig-MacAddress.txt file
are used.
• sipconfig-MacAddress.txt: this file is mandatory and allows to configure specific parameters
for a set defined with its MAC address. For example, the sipconfig-00809F5607AE.txt file
contains specific parameters for a set with the 00:80:9F:56:07:AE physical address.
The two files have the same list of parameters. When the set is registered with success, all parameters
are saved in the non volatile memory (flash memory) of the set.
The parameter value from the sipconfig-MacAddress.txt file overrides parameter of the
sipconfig.txt file when a parameter has been assigned a value in the sipconfig-
MacAddress.txt file.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 139/382

Chapter 2 IP deskphones

Examples:

• user name parameter

In the file sipconfig.txt the parameter user name is set to Alcatel-Lucent. As a result, all sets of
the system have the same name: Alcatel-Lucent.
For the set with MAC address 00:80:9F:56:07:AE, the file sipconfig-00809F5607AE.txt exists and
contains the parameter user name = Smith. As a result, this set is called: Smith and not: Alcatel-
Lucent.
• proxy_addr parameter
In the file sipconfig.txt the parameter proxy_addr is set to 192.168.110.80. As a result, all sets
share the same proxy.
For the set with MAC address 00:80:9F:56:07:AE, the file sipconfig-00809F5607AE.txt contains the
parameter proxy_addr. This parameter has no assigned value. As a result, this set uses the proxy defined
in the sipconfig.txt file.

2.6.4.8.2 sipconfig File

The sipconfig.txt and sipconfig-MacAddress.txt files have the same structure and contain
the following items:

Parameter Comment

###########################

# Configuration of SIP R7.1 Terminal

###########################

[basic]

[dns]

dns_addr= Enter the address of the DNS server

dns2_addr= Enter the address of the DNS backup server

hostname=noe_sip

[sip]

domain_name= Enter the IP address, FQDN or domain name

proxy_addr= Enter the address of the proxy server (PCX ad-

dress)

proxy_port= Enter the proxy port number

registrar_addr= Enter the address of the registrar server (PCX

address)

registrar_port= Enter the registrar port number

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 140/382

Chapter 2 IP deskphones

Parameter Comment

outbound_proxy_addr= Enter the outbound proxy server address

outbound_proxy_port= Enter the port used by the outbound proxy server

proxy2_addr= Enter the backup proxy server address

proxy2_port= Enter the port number used by the backup proxy

server

registrar2_addr= Enter the backup registrar server address

registrar2_port= Enter the port number used by the backup regis-

trar server

outbound_proxy2_addr= Enter the outbound proxy server address

outbound_proxy2_port= Enter the port used by the outbound proxy server

pcs_addr= Enter the PCS server address

pcs_port= Enter the port number used by the PCS server

sip_transport_mode=survi Enter the transport mode in PCS mode:

• 0 = UDP or TCP
• 1 = UDP
• 2 = TCP

option_timer=120

register_expire=3600 Enter the lifetime (in seconds) of a registration

register_retry=30 Enter the number of retry to connect the registra-

tion server

local_sip_port= Enter the port number used by the SIP set

local_sips_port= Enter the port number used by the SIP set used
in secured mode

sip_transport_mode=0 Enter level transport mode in PCS mode:

• 0 for UDP or TCP
• 1 for UDP only
• 2 for TCP only

local_rtp_port=42000 Leave the default value

local_rtcp_port=42001 Leave the default value

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 141/382

Chapter 2 IP deskphones

Parameter Comment

prack_type=0 Enter the PRACK type:

• 0 = PRACK supported
• 1 = PRACK required
• 2 = PRACK disabled

preferred_vocoder=0,4,8,18 Enter the preferred voice coder:

• 0 for PCMU
• 8 for PCMA
• 4 for G723.1
• 18 for G729A

authentication_realm= If no authentication, leave this field empty

authentication_name= If no authentication, enter a value like none

authentication_password= If no authentication, leave this field empty

user_name= Enter the name of the user

display_name= Enter the name to be displayed on the set

voice_mail_uri= Enter the URI or the call number of the voice

mail

message_waiting_indication_uri= Complete the SIP URI of the voice mail

[qos]

sip_diffserv=0

sip_diffserv=0

sip_qos_tickets_enable=0 • 0: disable
• 1: enable

sip_qos_tickets_target= Enter the domain name

[sntp]

sntp_addr= Enter the IP adress of the SNTP server

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 142/382

Chapter 2 IP deskphones

Parameter Comment

timezone= Enter the delta time between UTC and local time
Local time = UTC - timezone
Example:
UT::60:032902:102503

[telnet]

telnet_password=111111 Password to access the telnet session

[arp]

arp_spoofing_enable=1 • 0: ARP spoofing disabled

• 1: ARP spoofing enabled

arp_spoofing_timer=30

[init]

application_mode=1 Enter the operating mode of the set:

• 0 for NOE mode
• 1 for SIP mode

[audio]

tone_country=0 Enter the country language of the user:

• 0 for English
• 1 for French
• 2 for German
• 3 for Italian
• 4 for Spanish
• 5 for Dutch
• 6 for Portuguese

dtmf_type=2 Enter the DTMF type:

• 0 for DTMF according to RFC2833
• 1 for DTMF in band
• 2 for SIP INFO

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 143/382

Chapter 2 IP deskphones

Parameter Comment

dtmf_level=0 Enter the audio level for DTMF:

• 0 for 0db
• 1 or +3db
• 2 for +6db
• 3 for -3db
• 4 for -6db

dtmf_avt_payload_type=96

vad=1 Voice Activity Detection:

• 0 = VAD out of service
• 1 = VAD in service

dtmf_feedback_enable=1 • 0 = VAD not used

• 1 = VAD used

rlr_handset=10

slr_handset=10

sidetone_handset=2

hearing_aid_enable=1 • 0 = VAD not used

• 1 = VAD used

[appl]

admin_password=111111 Enter the set password in SIP mode

bluetooth_parameters=

remote_forward_code= Enter the forwarding activation code. This code

must be identical with the immediate forward
prefix defined in the PCX.

remote_forward_deactive_code= Enter the forwarding deactivation code. This

code must be identical with the forward cancella-
tion prefix defined in the PCX.

power_priority=0
• 1 for critical
• 2 for high
• 3 for low

asset_id=

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 144/382

Chapter 2 IP deskphones

Parameter Comment

time_format=0 Enter the time format for set display:

• 0 for 24 hours format
• 1 for AM and PM format

speed_dial_1_first_name= Enter the first name to display when key 3 is acti-

vated

speed_dial_1_last_name= Enter the last name to display when key 3 is acti-

vated

speed_dial_1_uri= Enter the URI or the call number locally dialed by

the set when key 3 is activated

speed_dial_2_first_name= Enter the first name to display when key 4 is acti-

vated

speed_dial_2_last_name= Enter the last name to display when key 4 is acti-

vated

speed_dial_2_uri= Enter the URI or the call number locally dialed by

the set when key 4 is activated

speed_dial_3_first_name= Enter the first name to display when key 5 is acti-

vated

speed_dial_3_last_name= Enter the last name to display when key 5 is acti-

vated

speed_dial_3_uri= Enter the URI or the call number locally dialed by

the set when key 5 is activated

speed_dial_4_first_name= Enter the first name to display when key 6 is acti-

vated

speed_dial_4_last_name= Enter the last name to display when key 6 is acti-

vated

speed_dial_4_uri= Enter the URI or the call number locally dialed by

the set when key 6 is activated

[admin]

binary_polling_timer=10

config_polling_timer=10

disable_pc_port=

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 145/382

Chapter 2 IP deskphones

Parameter Comment

activate_vlan_filter=

2.6.5 Managing Certificates

2.6.5.1 Overview
Certificates are used for:
• 802.1x TLS Authentication
• HTTPS downloading encryption and authentication
If a certificate delivered by ALE International is present on the set, it can be used for 802.1x TLS and
HTTPS.
It is also possible to download one or two customer certificates on a set.
The table below indicates which certificate is used for each usage according to the certificates present
on the set.

Certificates present on the set 802.1x TLS HTTPS

Certificate delivered by ALE In- Certificate delivered by ALE In- Certificate delivered by ALE In-
ternational only ternational ternational

One customer certificate Customer certificate 1 Customer certificate 1

Customer certificate 2 Customer certificate 1 Customer certificate 2

Customer certificates must be downloaded on terminals from a machine of the customer LAN.
The URL for download can be:
• Written in the lanpbx.cfg file: in this case, it is not possible to indicate a specific certificate file
name for each terminal. Certificate names must correspond to the MAC addresses of terminals
• Filled in directly on the set via the configuration menu at set initialization
Important:
For IP Touch sets operating in SIP mode (e.g. SIP survivability), the entire EAP-TLS configuration must
be done through the configuration menu of IP Touch sets (the lanpbx.cfg file, sent by the system
during IP Touch set initialization, is not used). This EAP-TLS configuration starts with the entry of the
download URL on the configuration menu of the IP Touch set.
After download, the customer certificate must be activated by a pass phrase. This pass phrase can
contain the following characters:
• Digits
• Upper case and lower case letters
• Special characters: @, $, +, -, _, %, ., /
Note:
For Alcatel-Lucent IP Touch 4018 phone Extended Edition, the pass phrase can only contain digits. Upper case
and lower case letters, and the special characters presented above are not authorized.

2.6.5.2 Configuring the lanpbx.cfg File

The lanpbx.cfg file must contain the following line:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 146/382

Chapter 2 IP deskphones

CERTSRV_IP=192.168.001.001 CERTSRV_PORT=8080 CERTSRV_PATH=/certserv where:

• CERTSRV_IP is the IP address of the machine on which the certificates are located. This field is
mandatory and must be an IP address, as there is no DNS on IP Touch sets
• CERTSRV_PORT indicates the port number to be used (optional, 80 is used as default port number)
• CERTSRV_PATH indicates the directory where the certificates are located (optional, certsrv is used
as default path)

2.6.5.3 Activating a Customer Certificate

1. Connect the set
2. If the download URL is indicated in the lanpbx.cfg file, the certificate is automatically
downloaded.
If the download URL is not indicated in the lanpbx.cfg file, it must be filled in manually on the set:
Reminder:
For IP Touch sets operating in SIP mode (e.g. SIP survivability), this operation is mandatory to configure EAP-
TLS on IP Touch sets.
a. From the main menu, use the navigation button to select Certificate
The certificate main menu is displayed
b. Use the navigation button to select Get Certificate
The Get certificate menu is displayed
c. In the HTTP field, enter the IP address of the server
d. If necessary, modify the Port number value (default is 80)
e. If necessary, modify the Path (31 characters maximum, default value is certserv)
f. According to the pattern of certificate files names:
•Either set the Use Mac@ File option to Yes if the certificate files are named according the
following pattern: <MacAddress>.pfx, where <MacAddress> is the Mac address of the
terminal without dots, for example ef0203c4c555.pfx
• Or leave the Use Mac@ File option to No and enter the file name in the following option File
(31 characters maximum)
g. Press the # key to save your modifications
The screen displays getting file...wait while the terminal is retrieving the certificate.
Once the certificate has been successfully downloaded, the screen displays the Certificate Get
Validation menu.
3. Enter the pass phrase and press the # key to confirm
The terminal checks the certificate and displays check...please wait.
If the pass phrase is right, the new certificate is displayed and stored in the flash memory as new
customer certificate.

2.6.5.4 Deleting a Customer Certificate

1. Connect the phone
2. When the set displays initializing, press i, then # key. If necessary, enter the password
3. From the main menu, use the navigation button to select Certificate
The Certificate main menu is displayed.
4. Use the navigation button to select Erase Certificate
The Erase Certificate menu is displayed.
5. Press the # key to confirm certificate deletion

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 147/382

Chapter 2 IP deskphones

The screen comes back to the Certificate main menu

2.6.5.5 Displaying the Active Certificate

1. Connect the phone
2. When the set displays initializing, press i, then # key. If necessary, enter the password
3. From the main menu, use the navigation button to select Certificate
The Certificate main menu is displayed.
4. Select View Certificate
The View Certificate menu is accessible if there is at least one certificate available.
The screen displays load...please wait while the certificate is decompressing. Once the certificate
has been successfully decompressed, the screen displays the Certificate View menu.
The certificate data displayed are the owner and issuer identifiers, serial number and expiration
date. There are accessible by using the navigation button.
5. Press the * key to exit and come back to the Certificate main menu

2.6.6 Maintenance
2.6.6.1 Overview
This module describes:
• How to view the IP Touch software version (in OmniPCX Enterprise only).
• The error and information messages that appear during the starting phase.
• The Ethernet link table.

2.6.6.2 Viewing the IP Touch Software Version (in OmniPCX Enterprise Only)
To view the IP Touch software version:
1. Press the navigation key and select Settings.
2. Select Options.
3. Select Version,
The set software version appears.

2.6.6.3 Error and Information Messages

The table below lists the error and information messages. It has the following format:
Short text = text displayed on the screen, in case of real error or for information.
Description = status/error description

table 2.15: Starting Phase Information and Error Messages

Short text Description

END Starting phase is terminated (successful or un-

successful)

STARTED Step started

SUCCESS Step successful

FAIL Step failed

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 148/382

Chapter 2 IP deskphones

Short text Description

RETRYING Retrying step

NO MAC ADDRESS No Ethernet MAC address stored in flash

DHCP NOT RESPONDING Server is not responding

BAD IP ADDRESS IP address is incorrect

BAD ROUTER ADDRESS Router address is incorrect

ROUTER PING FAILED Router not responding to ping

BAD TFTP ADDRESS TFTP server address is incorrect

ADDRESSES MISMATCH Address, mask and router do not match

TFTP NOT RESPONDING TFTP server is not responding

TFTP SERVER ERROR TFTP server error

BAD FILE CONTENT Error found in downloaded file

FILE TOO LARGE File is too large (cannot be downloaded)

SAME VERSION FOUND The version retrieved is the same as the version
running

NEW VERSION FOUND New IP Touch software version found (download)

FLASHING SUCCESS Flashing successful

FLASHING FAILED Failed to flash downloaded binary

TRYING ANOTHER CPU Trying next address from configuration file

NO ETHERNET LINK Ethernet link not connected (LAN port only)

RESOURCES NOT FOUND Resources file not found in flash

DOWNLOAD FORCED Download was forced because resources are

missing

NOT COMPATIBLE Downloaded version not compatible with the ter-

minal hardware

initializing First text message after hardware reset and

copyright information

1/5 network start phase 1 is running: the set is starting its network
interface

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 149/382

Chapter 2 IP deskphones

Short text Description

2/5 network setup Phase 2 is running: the set is looking for IP ad-
dresses

3/5 config download Phase 3 is running: the set is trying to get a

lanpbx file

4/5 binary download Phase 4 is running: the set is downloading a new

binary

5/5 connecting Phase 5 is running: the set is trying to set up the

signaling link with the system

Authentication failure: authentication denied 802.1x authentication has failed: RADIUS server
is unreachable, access is refused to the terminal
on the RADIUS server or the terminal has an in-
correct identity (bad login and/or password).

Authentication success: access granted 802.1x authentication process is complete. The

RADIUS server grants access to the terminal, the
authenticator opens its port.

2.6.6.4 Ethernet Link

By default, IP Touch sets are configured to perform auto-negotiation on both ports (LAN and PC).
Provided that the PC and the LAN switch are also configured to perform auto-negotiation, this is the
best configuration for QoS improvement.
However, depending on the network configuration, it may not always be possible to leave the terminal
in auto-negotiation: link speed and duplex of both ports can be forced to determined values using the
supervisor menu:
• Plug in the set, as described: Commissioning the 4008 or 4018 IP Touch Set.
• When the set starts initializing (after it has displayed Alcatel_Lucent), press i, before the # key. If
necessary, enter the password, as explained: Accessing the Admin Menu (MMI) on page 130.
• Use the navigation key to select Ethernet Links
• Modify data as requested
A configuration mismatch between the terminal and PC/LAN switch can lead to nasty effects on the
voice quality:
• No link (or speed mismatch): 8, 9, 11 and 12
• Packet loss (or duplex mismatch): 2, 4, 7 and 14
Note:
Collisions are not detected by the device operating in full-duplex mode: packets from this device are never re-
transmitted if a collision occurs on them.
The following table lists all possible Ethernet port configuration combinations when connecting an IP
Touch set to an external device (switch on LAN side, PC on PC side). For each combination, the table
shows the link status: valid or invalid (duplex or speed mismatch), as described above.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 150/382

Chapter 2 IP deskphones

table 2.16: Ethernet Link Combinations

Terminal Port External Device Port Link Status

1 auto-negotiation auto-negotiation Valid

2 auto-negotiation 100-FULL Invalid (packet loss)

3 auto-negotiation 100-HALF Valid

4 auto-negotiation 10-FULL Invalid (packet loss)

5 auto-negotiation 10-HALF Valid

6 100-FULL 100-FULL Valid

7 100-FULL 100-HALF Invalid (packet loss)

8 100-FULL 10-FULL Invalid (no link)

9 100-FULL 10-HALF Invalid (no link)

10 100-HALF 100-HALF Valid

11 100-HALF 10-FULL Invalid (no link)

12 100-HALF 10-HALF Invalid (no link)

13 10-FULL 10-FULL Valid

14 10-FULL 10-HALF Invalid (packet loss)

15 10-HALF 10-HALF Valid

Note:
To prevent slowness problem on PC when the two ports of an Alcatel-Lucent IP Touch 4018 phone Extended
Edition or Alcatel-Lucent IP Touch 4008/4018 phone Extended Edition set are configured in auto-negotiation
mode, if the negotiation has led to a 10 Mbps rate on the PC port and a 100 Mbps rate on the LAN port, the IP
Touch set automatically tries to renegotiate a 10 Mbps rate on the LAN port.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 151/382

 Chapter

3 TDM deskphones

3.1 8029/8039 Premium DeskPhone

3.1.1 Overview
3.1.1.1 Overview
The following section is intended for administrators in charge of installing and commissioning 8029
Premium DeskPhone and 8039 Premium DeskPhone sets for users declared on OmniPCX Enterprise
nodes.
These sets are part of the Alcatel-Lucent 9 series range and operates as Digital Premium DeskPhones
(TDM sets). They share many features with the previously available Alcatel-Lucent 4029/4039 Digital
Phone.
Note:
Digital Premium DeskPhones are fully compatible with older OmniPCX Enterprise versions (R10.1.1, as of patch
j2.603.27, and R11.0. If connected to previous PCX versions, they operate as 8 and 9 series sets of the previous
generation (40x8 and 40x9 sets).

3.1.1.2 About this section

This section contains:
• A description of the sets and their physical characteristics, audio quality and optional equipment:
Ergonomics of 8029/8039 Premium DeskPhone sets on page 152
• Commissioning and configuration information for these sets: Commissioning 8029/8039 Premium
DeskPhone sets on page 157
• An overview of the configuration specific for these sets: Additional configuration operations on page
37
• A description of the most common maintenance commands relating to these sets: Maintenance on
page 90

3.1.2 Ergonomics of 8029/8039 Premium DeskPhone sets

3.1.2.1 Set description
3.1.2.1.1 Phone layouts
Although there are differences in the aspect and operation of these sets, their layout is identical, but for
the screen and number of available soft keys.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 152/382

Chapter 3 TDM deskphones

Alarm LED

Set screen Soft keys

Dialing keypad

Corded handset

Fixed keys

Headset jack Piano sensitive keys

Adjustable foot
stand (0° to 60°)

Alphabetic keyboard
Alt key
Space bar

Figure 3.1: 8039 Premium DeskPhone set layout

Alarm LED

Set screen Soft keys

Dialing keypad

Corded handset

Fixed keys

Headset jack Piano sensitive keys

Adjustable foot
stand (0° to 60°)

Alphabetic keyboard
Alt key
Space bar

Figure 3.2: 8029 Premium DeskPhone set layout

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 153/382

Chapter 3 TDM deskphones

3.1.2.1.2 Embedded hardware

An IVANOE2 Chip with ARM7TDMI RISC processor is included in sets, associated with external SRAM
(256Kx16) and NOR Flash (512Kx16) memories.
3.1.2.1.3 Foot stand
All sets come with a 0° to 60° adjustable foot stand.
3.1.2.1.4 Audio, handsets, hands free and headset
All sets come with a standard 3.5 mm jack to plug a headset.
All sets offer narrow band audio qualities.
All sets come in their standard version with a comfortable corded handset.
They all work in hands free mode at the user's request.
3.1.2.1.5 Keys
3.1.2.1.5.1 Dialing keypad
All sets come with a standard 12-key dialing keypad.
3.1.2.1.5.2 Fixed keys
On all sets:

• Two fixed keys below the keypad (start call key: and stop call key: ) allow
to perform several actions
The start call key puts the set in hands free mode
The stop call key allows to end a call and ignore an incoming call
• A four-direction set of navigation keys (left, right, up, down) allows to select the different options
available on the screen. The OK button in the center of the navigation validates the selection.
• The c key to the left of the navigation allows to cancel the current action.
• Sensitive (piano) keys are located above the black grid of the lower part of the set.
Starting from the left to the right, they provide access to the following features:

• mute sound

• decrease sound volume

• increase sound volume

• put loudspeaker in service

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 154/382

Chapter 3 TDM deskphones

• hold call. This is the default feature for F1 keys (but can be programmed with
another feature)

• transfer call. This is the default feature for F2 keys (but can be programmed with
another feature)

• redial information

• information page (displayed on screen)

• messaging services
3.1.2.1.5.3 Integrated additional programmable keys
On 8029 Premium DeskPhone sets, four add-on keys, each with a LED, allow to customize each set
according to the user's needs. A paper label at the right of these keys allows to write down a brief
description of the feature programmed on the key.

3.1.2.2 Connecting optional equipment

3.1.2.2.1 Alphabetic keyboard
A standard (hot pluggable) optional keyboard is available for all sets:
• Azerty (FR)
• Qwertz (DE)
• Qwerty (international)
• Qwerty (Nordic)
Input Method Editor (IME) stickers are available for the following non-Latin characters:
• Cyrillic
• Zhuyin (Chinese, Taiwan)
• Jamo (Korean)
If you change keyboard types, ensure it is plugged in before restarting the set.
3.1.2.2.2 External interfaces
On all sets, a 3.5 mm jack connector allows to plug a headset to the phone.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 155/382

Chapter 3 TDM deskphones

RJ9 connector
RJ11 connector for UA (alphabetic
link (to the PCX) keyboard)

SATA connector RJ9 connector

(for add-on modules 10, 40-keys or (corded handset)
Smart module)
Figure 3.3: External interfaces on the back of 80x9 sets

3.1.2.2.3 Additional key modules

On all sets, several add-on modules, connected via SATA (see: External interfaces on page 155), can
complete the standard number of programmed keys.
Note:
• These add-on modules are not compatible with 40x9 phone sets.
• Add-on key modules designed for 40x9 phone sets are not compatible with 80x9 sets.
The available modules are:
• 10-key module (can be fastened to the set):

• 40-key module (on its own foot stand, placed next to the set)

• Smart-key module (on its own foot stand, placed next to the set)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 156/382

Chapter 3 TDM deskphones

3.1.3 Commissioning 8029/8039 Premium DeskPhone sets

3.1.3.1 Declaring the set
Before commissioning a 8029 Premium DeskPhone or 8039 Premium DeskPhone set, ensure that the
adequate hardware board has been configured and that the corresponding user has been declared in
the OmniPCX Enterprise.
To create a set and its corresponding user:
Note:
This procedure is provided as a minimum guideline. The other attributes for this parameter are described in other
parts of the OmniPCX Enterprise documentation.
1. Select: Users
2. Review/modify the following attributes:

Shelf Address Enter the shelf number

Board Address Enter the position of the UA board

Equipment Address Enter the position of the set connector on the board

Set Type Select the appropriate option: 8029 or 8039

Phone Features COS Enter the number for the adequate phone feature class
of service
3. Confirm your entries

3.1.3.2 Connecting the set

3.1.3.2.1 Physical connection
To connect the set:
1. Plug the RJ11 cable in the corresponding set connector on the back of the set (see: External
interfaces on page 83)
2. Plug the other end of the cable onto the UA board on which the set has been declared
The set starts initializing automatically.
If this is the first set initialization, or when there has been an upgrade of the PCX software version,
the set downloads binary and data files.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 157/382

Chapter 3 TDM deskphones

3.1.3.2.2 Binary file download

To operate correctly, 9 series sets require binary files which must comply with the PCX version and
configuration. After system upgrade and each time a set initializes, version numbers of binary files are
verified to determine whether an update of these files is necessary.
When a file is downloaded to set, it overwrites any previously existing file.
Note:
Should you plug a 8029 Premium DeskPhone/8039 Premium DeskPhone set to an OmniPCX Enterprise that does
not support it, when the terminal receives a download request with a 40x9 binary, It downloads the binary file but
does not flash it. The set saves this binary as "pseudo" soft version. After system reset request, it sends back this
"pseudo" soft version.
Application download to a terminal can be heavy in terms of bandwidth and CPU resources. It is not
possible to upgrade all the terminals during initialization of the system.
To optimize the telephone system upgrading and minimize inconvenience to users:
1. Define the appropriate download priority for the entire system
a. Select: System > Other System Param. > System Parameters > 9 Series download time
optimization
b. Review/modify the following attribute

9 Series download time optimiza- Determine download priority by select any of the fol-
tion lowing
• Min. download time for each set (default value).
When this value is selected, the four files (code,
data, localization, customization) are downloaded in
the shortest possible time on each set. After
downloading the code and data files, the set resets.
Then localization and customization files (if
available) are downloaded as soon as resources
are available.
Note:
There can be a certain amount of time between code/
data files download and localization/customization files
download. During set resetting, resources are assigned
to another terminal, and download on the first terminal
can resume once resources are free again.
• Min. download time for all sets. Select this value
when terminals can be out of service for a longer
time (e.g. at night) and when it is important that the
system is upgraded in the shortest possible time.
When this value is selected, data and code files are
downloaded on all the sets of the system in the
shortest possible time.
Localization and customization files are
downloaded only once the code and data files have
been downloaded on all the sets of the installation.

Note:
On one board, the maximum number of sets that can be downloaded at the same time depends on the type
of UA board and the download time optimization parameter:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 158/382

Chapter 3 TDM deskphones

• When the download time optimization value Min. download time for all sets is selected, the number of
sets is limited to 32
• When the download time optimization value Min. download time for each set is selected, the limit
depends on the type of board (for an eUA board, the limit is 4)
A terminal connected to a rescuable Media Gateway cannot be downloaded when this Media Gateway is in
backup mode.
c. Confirm your entry
2. If needed, determine the sets which must be downloaded before the others:
a. Select: Classes of Service > Phone Features COS
b. Review/modify the following attributes

Phone Features COS Enter the ID of the phone features class of service for
the sets to configure

Download policy Select the download policy:

• As soon as possible: Download starts as soon as
there are available resources, and the terminal is
free.
• Delayed (default value). Terminals are upgraded
during the time interval specified in the Download
Start and Download Stop parameters.
• Only on demand: This value is used when
download must be managed manually.
• Before start of application: This is for priority
download.

Start of download This attribute is valid or applicable only for the Delayed
download policy.
Hour
Enter the download start time in hours and minutes
Minute
(applies to every day of the week)

Stop of download This attribute is valid or applicable only for the Delayed
download policy.
Hour
Enter the download stop time in hours and minutes
Minute
(applies to every day of the week)
c. Confirm your entries

3.1.4 Additional configuration operations

3.1.4.1 Configuration additional operations for sets
When a user with a Premium DeskPhone set is created, a hierarchically dependent 8&9 Series
Parameters object is automatically created. This contains specific data on display options, access
rights to external applications, user rights to customize the home page.
Note:
Additional configuration on Premium DeskPhone and Alcatel-Lucent 8/9 series sets are very similar. In the
following paragraphs all mentions to Premium DeskPhone apply to Alcatel-Lucent 8/9 series sets, unless specified
otherwise
3.1.4.1.1 Configuring Alcatel-Lucent 8/9 series parameters
1. Select: Users > 8&9 Series Parameters

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 159/382

Chapter 3 TDM deskphones

2. Review/modify the following attributes

Directory Number Enter the set directory number

Application COS ID Enter application COS number (between 0 and 31)

Default value: 0

Phone COS Enter the phone COS number (between 0 and 31)
Default value: 0

Default Home Page Select the home page to be displayed when the set returns
to idle:
• Home Menu
• Home Perso
• Home Info
• Home Appli
• Home CCD
• None: the set displays the page viewed when the set
was last idle.
Default value: Home Perso
Notes:
IP Touch set users can configure their own default page from the
Menu page of their set.
Other Home pages may be available (e.g. Ccd) according to
system configuration.

Default IME A display-only value that shows the last input method char-
acter type used. Default value is No input.

Serial number Displays the set serial number. This value cannot be modi-
fied.

4059 Directory Number Displays the 4059 IP Attendant directory number, where
applicable.
3. Confirm your entries
3.1.4.1.2 Enabling external called number display
A parameter enables to select whether the dialed number or the trunk group name is displayed on the
display of phones. This parameter applies to external outgoing communications.
1. Select System > Other System Param. > Attendant Parameters
2. Review/modify the following attribute:

Display number during conversation • True (default value): the called number is
displayed on the display
• False: the trunk group name is displayed on
the display
3. Confirm your entries

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 160/382

Chapter 3 TDM deskphones

3.1.4.1.3 Defining external applications

The system can recognize up to seventeen external applications that can be accessed by phones. An
identifier must be assigned to each concerned external application.
1. Select Alcatel-Lucent 8&9 Series > 8&9 Series applications > Access to restricted
applications
2. Review/Modify the following attributes:

Application Id Enter an ID number: possible values 0 to 16

Application name Enter a name for this application (up to 16 characters)

3. Confirm your entries
3.1.4.1.4 Configuring application COS
There are three (or more) home pages: MENU, PERSO, INFO, (APPLICATIONS). The different
applications (internal and external) are displayed in the MENU tab (whatever the home page
configured in administration).
Application COSs are used to:
• Specify the order in which the different applications (internal and external) are displayed on the set's
MENU home page.
• For each external application, give or limit access to all users in this COS.
Thirty two COSs are created by default. A COS is assigned to a set in the user's Series 8&9 classes
of service. By default, COS 0 is assigned.
1. Select: Alcatel-Lucent 8&9 Series > 8&9 Series COS > Applications COS
2. Review/modify the following attributes

Application COS ID Enter the number of the COS to be viewed or modified (be-
tween 0 and 31)

Application COS name Enter a name for this COS (20 characters at the most)

When a COS number has been selected, fields are displayed as shown below, as many times as
there are applications (internal applications are displayed first, followed by external applications).

Application Name

Priority Enter priority (between 0 and 255):

• 0: not presented, select 0 to bar use of an external
application.
• 1 (highest priority): presented at the top left
• 2: presented at the top right
• and so on...
Default value for external applications: 0
Default value for internal applications: see Table 1.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 161/382

Chapter 3 TDM deskphones

table 3.1: Default priority for internal applications

Internal application Default priority

Settings 1

Redial 2

Appointment 3

Lock 4

Text mail 5

Forward 6

No reply 7

Who am I 8

Repertory 9

Manager/Assistant 10

External application No 1 11
When they exist, other exter-
nal applications follow this
first one in the priority list.

Notes:
For internal applications, the level of priority only defines the desired location on the home page menu and not
user rights for application use. User rights are configured in the user's phone features COS.
Other applications, such as e.g. Ccd, can appear in this list, according to system configuration.
3. Confirm your entries
3.1.4.1.5 Configuring Phone COS
Note:
The phone classes of service described here are specific to Premium DeskPhone and Alcatel-Lucent 8/9 series
sets.
Do not confuse these phone COSs with phone features COSs that apply to all sets (including Premium
DeskPhone and Alcatel-Lucent 8/9 series sets), and that are used to configure user access rights to phone
features (forwarding, conference calls, etc.).The phone features COS applying to all users is configured via:
Classes of Service > Phone Features COS
Phone COSs are used to define graphical user interface (GUI) and to grant or limit user rights to
customize home page.
Phone COSs are created by default. There are 32 COSs. A COS is assigned to the set in the user's
8&9 Series Parameters. By default, COS 0 is assigned to newly declared sets. This specific phone
COS is assigned to the concerned users via: Users > 8&9 Series Parameters.
1. Select: Alcatel-Lucent 8&9 Series > 8&9 Series COS > Phone COS
2. Review/modify the following attributes

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 162/382

Chapter 3 TDM deskphones

Phone COS Enter the number of the COS to be viewed or modified (be-
tween 0 and 31)

Phone COS Name Enter a name for the COS

Right to Modify Default Home Page • Yes: users in this COS have the right to modify their set
home page
• No: users in this COS do not have the right to modify
their set home page
Default value: Yes

Home bar • Yes: the home bar changes to inform the user of set
forwarding status
• No: the home bar does not change and displays only
date information
Default value: No

Ringing Cadence • Yes: each ringing sound is followed by a short silence

• No: ringing sound is continuous
Default value: Yes

State LED Message Determines the behavior of the LED message according to
received messages.
• State - ON (default value): when at least a message
(alarm, voice, text, callback, unanswered call) has not
been heard/viewed, the LED blinks red.
After message consultation, the Message LED is lit red.
If there is no message left in the message memory, the
Message LED is off.
• State - OFF: when at least a message (alarm, voice,
text, callback, unanswered call) has not been heard/
viewed, the LED blinks red.
After message consultation, the Message LED is off.
• State - Blinking: when at least a message (alarm,
voice, text, callback, unanswered call) has not been
heard/viewed, the LED blinks red.
After message consultation, the Message LED blinks
red.
If there is no message left in the message memory, the
Message LED is off.
• State - UA Equivalent (as per USA standard
behavior): when there is at least one new message the
LED blinks slowly
When at least one message has been archived and/or
there is at least one unanswered call, the LED is lit red.
If there is no message left in the message memory, the
Message LED is off.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 163/382

Chapter 3 TDM deskphones

Authorized IME The list of additional input method character types author-
ized.
Possible values:
• No input (meaning only the default, Latin, is
authorized)
• Cyrillic
• Pin Yin
• Jamo
• Stroke
• Zhu Yin

CBN : Display Name without Pho- • Yes: when available, displays only the name of the
neNb calling/called party
• No: displays number and name (when available) of the
calling/called party
Default value: Yes

Display Encrypted Communication • Yes: when the current call is secured with encryption,
displays the secured icon on the set screen
• No: no indication of encryption is displayed on the set

Display Supervision State • Yes: displays the status of supervised set (the icon
depends on the status of this set) next to the
supervising key
• No: no indication of status of supervised set is
displayed on the set

Show on top update of Info Page • Yes: In idle state, displays the Info page when new
messages or new unanswered calls are recorded
• No: The page displayed remains the same when new
messages or new unanswered calls are recorded

Main page at Top Level • Yes: Every new display of the Main (Perso) page
shows the first keys of the page
• No: Every new display of the Main (Perso) page goes
back to the position it was previously

Displ. unans calls if Homepage app On sets with the external application My Homepage, by
default unanswered calls are not displayed on the Info
page. To display unanswered call information on the Info
page on sets with My Homepage, set this attribute to True.
Default value is False.

Hide Key Forward to MV/Text When value is True, the set hides the softkeys Immediate
Fwd to VM and Fwd to text. Default value is False (the
set displays the softkeys).

Display Main Page on off-hook • Yes: allows to display automatically the Main (Perso)
page on off-hook
Default value: No.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 164/382

Chapter 3 TDM deskphones

State PC port • Cascad. not filt. (IP-Phone or PC): the set PC port is
enabled. Packets are transmitted without filtering.
• PC port disabled: the set PC port is disabled. This
option is used to prevent daisy chaining of a PC behind
a terminal.
• Cascading with filtering (PC only): the set PC port is
enabled and packets are filtered:
• Frames coming from the LAN to the PC: 802.1q tags
are removed
• Frames coming from the PC to the LAN: 802.1q tags
are replaced by the default VLAN tag (VLAN=0).
This option ensures that no Voice VLAN traffic can be
sent from illegitimate sources.

Main Page Auto Display Enable • Yes: allows to display automatically the Main (Perso)
page if no action is done after a timeout: Timer No. 371
(see Timers on page 51).
• No: The page displayed remains the same.
Default value: No.
Note:
This option is useful when the emergency keys (keys
programmed with emergency numbers) are configured on the
first keys of the Main (Perso) page. It allows these keys to remain
always visible.

Second Call Ring Type Select any of the following:

• Beep (default value)
• Long Ring
• Short Ring

8&9 Series Handsfree Mode Select YES to enable echo robustness in handsfree mode.

Customization File Name Enter the customization file name for sets needing special
ringing melodies
Example:
Enter mycompany if the customization file names are as
follows:cust-mycompany-80x8 cust-
mycompany-80x9cust-mycompany-8029 cust-
mycompany-8039

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 165/382

Chapter 3 TDM deskphones

Keep RTP flow This parameter controls the reboot of sets when the con-
nection with CS or PCS is lost:
As of R10.1
• True:
• Idle sets reset immediately.
• Ongoing communications are maintained, but
operations are limited: no softkey or hardkey work,
except for the Loudspeaker, Mute/unmute, volume
and Release keys. Sets reboot at the end of the
communication, or when no incoming RCTP traffic
gets to the set.
• False (default value): all sets reboot immediately, even
if in communication.
Notes:
• It is necessary to reset sets after the modification of this
parameter.
• This feature is not available on 8088 Smart DeskPhone and
80x8s Premium DeskPhonesets.
For more information, see Signaling distribution on page
20 and document [1].

Bluetooth enabled • Yes: Bluetooth will be enabled on corresponding set

• No: Bluetooth is disabled on corresponding set
Default value: Yes
Note:
It is necessary to reset sets after the modification of this
parameter (sets will reboot twice).

Transparent reboot This parameter controls the reboot of sets:

• True: users are not informed that their set is being
reset. The set screen displays a screenshot of the
home page until the genuine home page is available
again. The set's MMI remains available.
• False: Users can see on their display that their set is
being reset. The set's MMI is available.
This feature is not available on 8088 Smart DeskPhone
sets.

Hide Services Lists • Yes: The Services softkey is not displayed on the
screen but the services are still available
• No: The list of services is available in menus
Default value: No

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 166/382

Chapter 3 TDM deskphones

Voice Mail PRS application ID Enter the four-character string, which is the application ID
configured in the PRS application, to access the SIP voice
mail from the set voice mail key. Example: MY_M (Default
value: NULL).
The set screen displays a menu when pressing the voice
mail key.
When the string is empty, pressing the voice mail key
starts the TUI application, which displays no menu on the
screen but plays interactive voice guides allowing access
to the SIP voice mail.

Skin Number Skin selection is available on 8058s Premium DeskPhone,

8068s Premium DeskPhone, and 8078s Premium Desk-
Phone sets. 4 types of skins are available. Default value is
0.
1. Configure the parameter to one of the following
number: 1, 2, 3, 4
2. Reboot the set to validate your modifications
The configuration is registered and sent to the terminal.
When the parameter is set to a value other than 0, skin se-
lection is not available from the phone set user menu.

Backlight Timer Determines for how long the screen is fully lit when it goes
back to idle.
Default and minimum value: 300 (in seconds).
Maximum value: 14400.
It is necessary to reset sets after the modification of this
parameter.

Hide IP Parameters menu As of R11.2, this parameter determines whether the set IP
address is hidden for the end user consulting the set
menu: Settings > Options
Default value: False

USB Boost Charging As of R12.0, this parameter is available for 8018 Desk-
Phone sets and 80x8s Premium DeskPhone sets only.
These sets provide a USB connector which allows charg-
ing of devices such as smartphones. A boost enables a
quicker charging of phones and tablets. But boost charging
requires more power consumption than normal USB charg-
ing in case of PoE.
• Disable: Normal USB charging (default value)
• Enable: Boosted USB charging
• AUTO: Reserved for future use (=disable if set)
Reboot the set to validate your modifications.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 167/382

Chapter 3 TDM deskphones

USB Connectivity 80x8s Premium DeskPhone sets have a provision of USB

Connectivity (for peripherals such as headsets and head-
phones, for instance).
• NO: USB Connectivity is disabled
• YES: USB Connectivity is enabled
The device can be connected on USB device.
Reboot the set to validate your modifications.

Ambient Light Sensor Forced Ac- The Ambient Light Sensor is available on 8088 Smart
tive DeskPhone and 80x8s Premium DeskPhone sets. It is
mainly used for energy saving. When this parameter is
configured in OmniPCX Enterprise, it cannot be disabled
by the end user.
Configure the parameter to one of the following:
• Modifiable by ULM: the default value defined in the set
for brightness is used. This value can be modified using
the User Local Menu (ULM) on the set.
• Disable: the brightness is modulated in manual way by
user setting. All light emitting devices brightness are
synchronized.
• Enable: the brightness of the LEDs are adapted
according to the current ambient brightness. The user
can change the brightness manually even if the
parameter is activated.

Back Logo LED The ALE International logo on the back of the 8058s Pre-
mium DeskPhone, 8068s Premium DeskPhone and 8078s
Premium DeskPhone sets includes a LED indicating the
call status:
• The LED is lit white: the phone set is idle
• The LED blinks blue: the phone set is ringing
• The LED is lit blue: the phone set is in communication
This parameter enables to turn on or off the LED:
• Modifiable by ULM: the LED can be turned on or off
from the User Local Menu (ULM) of the phone set
• Disable: the LED is turned off
• Enable: the LED is turned on
When this parameter is configured in OmniPCX Enterprise,
it cannot be enabled or disabled from the phone set (ULM).

Private store URL For future use. Format is either:

• The server name, port and access path
• The server IP address, port and access path

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 168/382

Chapter 3 TDM deskphones

Proxy for software update Depending on client configuration, a proxy may be

necessary for software upgrade.
• The server name, port and access path
• The server IP address, port and access path
3. Confirm your entries
Note:
If Alcatel-Lucent 8&9 Series > 8&9 Series COS > Phone COS > Display Main Page on off-hook option is set,
the Speed dial screen is displayed when going off hook from idle state.
3.1.4.1.6 Configuring names in non-Latin characters
Up to 8 languages can be managed. These languages correspond to the languages configured for the
whole system (for more information, refer to the Voice guides and music-on-hold section of the
document [1]).
Every set in the system has a Language ID (configured in system administration and/or the set user)
which corresponds one of the languages available in the system.
Note:
There is no control at system management level on the languages available for each set. All languages are
authorized, but not all character types are available on all sets. For example, the system allows the Language ID
attribute of the User object for a 4018 set to refer to Chinese, although this set cannot display Chinese characters.
The set display will use one of its available character types instead.
To allow input of non-Latin characters on a set, authorize the appropriate input method in the Phone
Class of Service (see Configuring Phone COS on page 40).
Note:
You must use the OmniVista 8770 application to configure UTF-8 names. Non-Latin characters are displayed
as ??? in mgr.
3.1.4.1.6.1 Configuring language compatibility
The compatibility configuration below determines whether a set in a language using one set of fonts
(e.g. Latin for English) can view other fonts (e.g. Greek).
Example:
English speaking users may not be familiar with Greek fonts and would rather see Greek user's name in Latin
characters. The system administrator determines, per available set types, whether sets in English will display
Greek fonts.
1. Select: Alcatel-Lucent 8&9 Series > Language Type Compatibility
2. Review/modify the following attributes

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 169/382

Chapter 3 TDM deskphones

Set Type Select the desired option among:

• 401x: for Alcatel-Lucent IP Touch 4018
phone Extended Edition and Alcatel-Lucent
4019 Digital Phone sets
• Others: for Alcatel-Lucent IP Touch
4028/4038/4068, Alcatel-Lucent 4029/4039
Digital Phone, 8028/8038/8068, 8088 Smart
DeskPhone , 8028s/8058s/8068s/8078s or
8029/8039 sets

Language type According to the set type selected above, select

the type of fonts among:
• Latin
• Cyrillic
• Chinese (where available)
• Japanese (where available)
• Korean (where available)
• Greek (where available)
• Arabic (where available)
• Hebrew (where available)
• Thai (8028/8038/8068, 8088 Smart
DeskPhone, 8028s/8058s/8068s/8078s and
8029/8039 sets only)
• All

Display Language 0 Displays the first language available in the sys-

tem

Compatibility Select YES to make the set compatible with oth-

er fonts.
Example:
If the selected instance is Cyrillic, on user sets where
the display language is English, names in Cyrillic
(configured Configuring long or non-Latin character
user names on page 48) are displayed in Cyrillic
fonts.

Display Language x Proceed with the other languages to use as per

Language 0 above
Compatibility
Note:
If your system is in an ABC-F network, ensure system
languages are defined identically for each network
node.

3. Confirm your entries

3.1.4.1.6.2 Configuring long or non-Latin character user names
1. Select: Users
2. Review/modify the following attributes

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 170/382

Chapter 3 TDM deskphones

Directory name Enter the user name in standard Latin charac-

ters

Directory First name Enter the user first name in standard Latin char-
acters

UTF-8 Directory Name Enter the user name in specific fonts (other than
Latin), or Latin long name
Reminder:
No font other than Latin can be entered via the mgr
tool. Use the OmniVista 8770 applications instead

UTF-8 Directory First Name Enter the user first name in specific fonts (other
than Latin), or Latin long name
Reminder:
No font other than Latin can be entered via the mgr
tool. Use the OmniVista 8770 applications instead

3. Confirm your entries

3.1.4.1.6.3 Configuring long or non-Latin character speed dialing names
1. Depending on the type of speed dialing number, select on of the following:
• Speed Dialing > Direct Speed Dialing Numbers > Direct SpdDl No. Pref.
• Speed Dialing > Spd Dl Numbers by Range > Speed Dialing Number
2. Review/modify the following attributes

Direct Speed Dial No. Prefix (or Speed Dial- Enter the speed dialing number to create (or
ing No. if speed dialing number by range modify)

Call Number Enter the actual number to dial

Directory name Enter the user name in standard Latin charac-

ters

Directory First Name Enter the user first name in standard Latin char-
acters

UTF-8 Directory Name Enter the user name in specific fonts (other than
Latin), or Latin long name
Reminder:
No font other than Latin can be entered via the mgr
tool. Use the OmniVista 8770 applications instead

UTF-8 Directory First Name Enter the user first name in specific fonts (other
than Latin), or Latin long name
Reminder:
No font other than Latin can be entered via the mgr
tool. Use the OmniVista 8770 applications instead

3. Confirm your entries

3.1.4.1.6.4 Configuring long or non-Latin character entity Names
1. Select: Entities

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 171/382

Chapter 3 TDM deskphones

2. Review/modify the following attributes

Entity Number Enter the entity number to create or modify

Name Enter the entity name in standard Latin charac-

ters

UTF-8 Name Enter the entity name in specific fonts (other

than Latin), or Latin long name
Reminder:
No font other than Latin can be entered via the mgr
tool. Use the OmniVista 8770 applications instead

3. Confirm your entries

3.1.4.1.6.5 Configuring long or non-Latin character trunk group names
1. Select: Trunk Groups
2. Review/modify the following attributes

Trunk Group ID Enter the ID number for this trunk group

Trunk Group Name Enter the standard name for this trunk group (up
to 10 characters)

UTF-8 Trunk Group Name Enter the name in specific other than Latin font,
or up to 20 characters if in Latin font
Reminder:
No font other than Latin can be entered via the mgr
tool. Use the OmniVista 8770 applications instead

3. Confirm your entries

3.1.4.1.6.6 Configuring non-Latin character programmed key names
You can enter names when you program keys on the set. You can also configure long or non-Latin
character names for programmed keys using the OmniVista 8770 application.
1. Select Users > Progr.Keys
2. Review/modify the following attributes:

Directory Number Enter the directory number of the set.

Key No. Enter the number of the key to be configured.

Function Select Programmed

Mnemo (Pocket,Mobile,4040,8&9) Enter a description for the function to be dis-

played next to the key in Latin characters.

UTF-8 Mnemo (8&9 Series) Enter a description for the function to be dis-
played in non-Latin characters next to the key.
Note:
You must use the OmniVista 8770 application to enter
or display non- Latin characters for this attribute. Non-
Latin characters are displayed as ??? in mgr.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 172/382

Chapter 3 TDM deskphones

3. Confirm your entries

3.1.4.1.6.7 Configuring non-Latin character manager/assistant key names
You can configure non-Latin character names for the manager key, the assistant key, and a secondary
assistant. For more information, refer to the section Manager/assistant sets section of the document
[3].
3.1.4.1.6.8 UTF–8 resolution in an ABC-F network
1. Select System > Other System Param > Network Parameters > Enable UTF8 in ABCF network
2. Review/modify the following attribute

System Option Select Enable UTF8 in ABCF network

Enable UTF8 in ABCF network • True (default value): UTF8 names are
transmitted to other nodes of the ABCF
network
• False: UTF8 names are not transmitted to
other nodes of the ABCF network
3. Confirm your entry
4. To allow UTF-8 resolution between subnetworks, select Translator > Network Routing Table
5. Review/modify the following attribute

Network number Select the appropriate network number

Enable UTF8 name sending Select True to enable UTF-8 resolution

6. Confirm your entry
3.1.4.1.7 Timers
There are specific timers for Premium DeskPhone and Alcatel-Lucent 8/9 series sets:
• Timer No. 325: display of audio and internal application confirmation:
This popup is displayed in the following cases:
• Activation/deactivation of an internal application (forward, mail, appointment, redial, dial by
name, programming, etc.)
• Activation of audio modification (headset (except when starting or answering a call), hands free
(except when starting or answering a call), group listening, mute)
• Timer No. 331: display of the popup window indicating an incoming call
• Timer No. 332: display of the confirmation popup
• Timers No. 356 (default value 20 seconds) and No. 357 (default value 60 seconds): used by the
Input Method Editor (IME) for input of non-Latin characters in Dial by name. Both timers close the
IME due to no user activity. When Timer No. 356 expires, the previous input is saved. When Timer
No. 357 expires, the previous input is cleared. The value of Timer No. 356 should be less than the
value of Timer No. 357.
• Timer No. 371: automatic display of the Perso page if no action is done during this timer.
To modify the duration of these timers:
1. Select System > Timers
2. Review/modify the following attributes:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 173/382

Chapter 3 TDM deskphones

Timer No. Enter the No. of the timer to modify

Timer units Modify as needed.

3. Confirm your entry

3.1.4.2 Prefixes and suffixes

Most telephone services, such as for example call transfer or conferences, can be activated by a prefix
(or suffix).
The rights for users to access services is determined in their class of service.
On sets, services are easily accessible via programmed keys and menu options (softkeys).
Some prefixes cannot be dialed on set because they are available by settings menu or by direct keys
(language, contrast programming, no ringing ) or because they have no meaning for sets (personal
directory programming on analog station, personal directory use on analog station).
Note:
To display the list of available prefixes in the system, use the LISTRAD command.

3.1.4.3 Configuring keys

System configuration for Premium DeskPhone additional key modules is very similar to the
configuration of additional key modules for Alcatel-Lucent IP Touch 4028/4038/4068, or Alcatel-Lucent
4029/4039 Digital Phone sets.
However, additional modules for these sets are not compatible with 3G sets and 3G additional modules
are not compatible with sets of the previous generation.
Note:
8088 Smart DeskPhone sets running in NOE mode do not support additional key modules. They include a virtual
key module available on screen (equivalent to a Smart Display Module).
3.1.4.3.1 Declaring an additional key module
1. Select: Users
2. Review/Modify the following attributes:

Directory Number Enter the directory number of the set

Add On Module 1 Select the appropriate additional key module

Add On Module 2
Add On Module 3
3. Confirm your entries
3.1.4.3.2 Key mapping and programming
Piano sensitive keys are numbered G1 to G9, from left to right.
Keys can be programmed directly on the set or in system configuration.
They are numbered as follows:
• Personal home page keys: 1 to 7
• F1 and F2 keys: 73 and 74
• Additional module keys: from 75 onwards
Keys are numbered in pairs from left to right, then from top to bottom (except for 10-key and Smart
Display Module, which are numbered from top to bottom).

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 174/382

Chapter 3 TDM deskphones

To program a key from the system:

1. Select Users > Progr.Keys
2. Review/Modify the following attributes:

Directory Number Enter the directory number of the set

Progr.Keys Enter the number of the key

Function Select the function of your choice (select Programmed to manually enter
the number dialed when the key is pressed)

Mnemo(Pocket,Mo- Enter the name to display next to the key on the LCD display (for keys on
bile,4040,IPTouch) the Perso tab or on a Smart Display Module)

UTF-8 Mnemo ( Al- If desired, enter the name in non-Latin characters to display next to the key
catel-Lucent 8&9) on the LCD display (for keys on the Perso tab or on a Smart Display Mod-
ule)

Locked Select YES to prevent users from modifying the contents of this key from
their set
3. Confirm your entries

3.1.5 Maintenance
The following paragraphs detail the most common and useful command lines for Premium DeskPhone
sets.
Maintenance commands allow to distinguish between 80xx sets and 40xx sets. Configuration
parameters (available from mgr and the OmniVista 8770) are the same.
The OmniPCX Enterprise versions R11.0.1 and R10.1.1 J2.603.27 fully support Premium DeskPhones.
On previous versions, Premium DeskPhones operate normally as if they were 40xx sets.

3.1.5.1 Detecting set types

To detect Premium Deskphones on an OmniPCX Enterprise version that does not fully support
Premium DeskPhones:
• For TDM 80x9 phones :
Enter: Zdpost d <phone number> | grep “IPTOUCH TDM”
If the result is: IPTOUCH TDM hard version = 167, the set is a Premium Deskphone
If the result is: IPTOUCH TDM hard version = 160, the set is a 40x9 set
• For IP 80x8 and 80x8s phones
Enter: Zdpost d <phone number> | grep “version”
If the result for the firmware version is 4.50.xx, the set is a Premium Deskphone
Example:
Firmware version Data : 4.50.30
Bootloader version : 4.50.30
SIP version : 2.11.83

3.1.5.2 downstat t
The downstat t command displays information on download for 9 series sets.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 175/382

Chapter 3 TDM deskphones

Example:
(1)cs80> downstat t
*** IPTOUCH-A(4019) TDM : soft : 3.81.00
*** IPTOUCH-B(4029) IPTOUCH-C(4039) TDM : soft : 3.81.70 - data : 3.81.70
***/DHS3bin/downbin/data80x9*** file does not exist
*** IPTOUCH-B(8029) IPTOUCH-C(8039) TDM : soft : *** - data : ***
*** Download time optimization: FOR EACH SET
** 3 IPTOUCH TDM phones are declared on this node !!
** 0 IPTOUCH TDM phones are not updated with the right binary!
** 0IPTOUCH TDM phones can be reseted for update!!
IPTOUCH TDM phone downloaded informations :
-------------------------------------
1 Display up to date IPTOUCH TDM phones
2 Display IPTOUCH TDM phones not yet updated
3 Display download in progress
4 Display out of order IPTOUCH TDM phones
5 Display all IPTOUCH TDM phones
0 Quit
Your choice ?

3.1.5.3 getnoeversion
The getnoeversion command returns information about all Premium DeskPhone sets that are
declared and in service on the node.
This information includes:
• Status (in service or out of service)
• Type of set
• IP domain number (IP DeskPhones sets)
• Serial number
• Hardware version
• Software version
The presence (or absence) of Bluetooth and additional key modules is detailed, as well as the
RAM/ROM of the set.
Localization and customization information is listed in the command result.
This command can be applied:
• To a specific set by using the set directory number.
The command results can be displayed directly on the maintenance console.
Example:
(1)cs80> getnoeversion d 17002
+------------------------------------------------------------------------------------------+
|dir numb |in |typ term |dom |serial number|hardware version|code vers |data vers|rom |ram |
+------------------------------------------------------------------------------------------+
|17002 |OK |8029 |n/a | | | 4.50.30 |4.50.30 | 2 | 0 |
+------------------------------------------------------------------------------------------+
• To all the Premium DeskPhone sets of the node. The results for the getnoeversion command are
stored in the file:
/DHS3dyn/mao/getnoeversion.xxx
where xxx corresponds to .csv or .xml format, according to user choice.

3.1.5.4 ippstat
The ippstat command returns information on all the IP phones of a node.
Example:
(1)cs80> ippstat
IPP (IP Phone) information :

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 176/382

Chapter 3 TDM deskphones

-------------------------------------
Display the IP Address of the local node : 1
Display IP Phone data of a set : 2
Display all IP Phone on local node : 3
Display registration terminaisons(short info): 4
Display registration terminaisons (long info): 5
Display an IP Phone Board structure : 6
Display all IP Phone Board structure : 7
Display all Mac Address Used : 8
Display all Mac Address Unused : 9
Display Ip phone by adr mac/adr adr ip/mcdu : 10
Display number of IP Phones connected : 11
Display all IP Phones connected on a board : 12
Display all IP Phones connected with boards : 13
Ip Phone download Menu : 14
Timeout for telnet session of IP Touch set : 15
INT IP Menu : 16
Domain Menu : 17
IPlink Menu : 18
Status Menu : 19
Display boards encryption parameters : 20
Enable telnet session of GD/GA/OMS : 21
Quit this tool : 0
Enter your choice :

3.1.5.5 listerm
The listerm command lists all the terminals belonging to a node.

3.1.5.6 termstat
The termstat command provides information on the board to which the set is connected, call
forwarding as well as other information.
Example:
(1)cs80> termstat d 13002
Tue Nov 12 15:16:11 CET 2013
+COUPLER_INFORMATION --------------------------------------------------------+
| Logic coupler type : CPL_UA
|
| MAO coupler type : UAI 8
|
| Coupler state : IN SERVICE
|
+--------------------------------------(PRESS ANY KEY TO CONTINUE)+
[1] : Device features.
[2] : Forward information.
[3] : Subdevice information.
[4] : Demi-com information.
[5] : Reset the device.

3.1.5.7 eqstat/tradna
The eqstat and tradna commands provide information on the status of a set and reason why a set
is out of service.
The two commands return the same results.
Example:
(1)cs80> tradna 13002
Tue Nov 12 15:22:06 CET 2013
Logic coupler type : CPL_UA
MAO coupler type : UAI 8
Coupler state : IN SERVICE
Terminal state : IN SERVICE
+-----------------------------------------------------------------------------+
| Cry:Cpl:ac:term | neqt |nulog| typ term | dir nb | Out of service cause |
+-----------------------------------------------------------------------------+
| 001 5 0 6 | 00418 | 29| 4029| 13002 | |
+-----------------------------------------------------------------------------+

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 177/382

Chapter 3 TDM deskphones

| A: att_mserv, C: hs_defich, I: hs_isolauto, X: hs_isolman, T: hs_terdef |

| U: hs_usdef, P: hs_errparite, B: hs_bascul, Y: hs_cristisol, N: hs_inex |
+-----------------------------------------------------------------------------+

3.1.5.8 zdpost
The zdpost command provides information on configuration of the set and the latest activity of the set.

3.2 4019/4029/4039 Digital Phone (9 series)

3.2.1 Overview
3.2.1.1 Overview
The Alcatel-Lucent 9 series sets are TDM (Time Division Multiplex) sets and are supported on the
OmniPCX Enterprise from R6.1. The Alcatel-Lucent 9 series is composed of three sets:
• Alcatel-Lucent 4019 Digital Phone (from R.6.1.1)
• Alcatel-Lucent 4029 Digital Phone
• Alcatel-Lucent 4039 Digital Phone
The features offered by these sets are the same as that of the Alcatel-Lucent IP Touch 4018 Phone,
Alcatel-Lucent IP Touch 4028 Phone, Alcatel-Lucent IP Touch 4038 Phone sets. However, the
application openness through the Presentation Server (PRS) is not available on Alcatel-Lucent 9 series
sets.
In the "8" series, downloads can be requested individually from each set. In the "9" series, downloading
is initiated centrally from the OmniPCX Enterprise for the telephone network. Downloads are required
for:
• Software correction
• Saving set features
• Application update
The system administrator can configure OmniPCX Enterprise parameters to minimize inconvenience
for the telephone system and the users.
The purpose of this document is to describe Alcatel-Lucent 9 series sets operation with the OmniPCX
Enterprise, in particular, the initialization process and declarations to be made.
For a description of set appearance and characteristics common to all the Alcatel-Lucent 8/9 series
sets, see: Ergonomics of 8/9 Series sets on page 98.
For information on how to put Alcatel-Lucent 9 series sets into service, refer to:
• Commissioning 4019 Digital Phone sets on page 210
• Commissioning 4029/4039 Digital Phone sets on page 212

3.2.2 Ergonomics of 8/9 Series sets

3.2.2.1 Alcatel-Lucent IP Touch 4028/4038/4068 and Alcatel-Lucent 4029/4039 Digital Phone set
description
Although there are differences in the aspect and operation of these sets, their layout is identical but for
the screen and number of available soft keys.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 178/382

Chapter 3 TDM deskphones

Screen Inclination
Set Screen Adjustment Alarm LED

Soft Keys

Dialing Keypad Fixed keys

Headset jack
Alphabetic Keyboard

Alt Key Space Bar

Figure 3.4: Alcatel-Lucent IP Touch 4068 Phone set layout

Set Screen Screen Inclination

Alarm LED
Adjustment

Soft Keys

Dialing Keypad Fixed keys

Headset jack Alphabetic Keyboard

Alt Key Space Bar

Figure 3.5: Alcatel-Lucent IP Touch 4038 Phone and Alcatel-Lucent 4039 Digital Phone set layout

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 179/382

Chapter 3 TDM deskphones

Screen Inclination
Set Screen Adjustment Alarm LED

Soft Keys

Dialing Keypad Fixed keys

Headset jack Alphabetic Keyboard

Alt Key Space Bar

Figure 3.6: Alcatel-Lucent IP Touch 4028 Phone and Alcatel-Lucent 4029 Digital Phone set layout

3.2.2.1.1 Set equipment

The Alcatel-Lucent IP Touch 4028/4038/4068 and Alcatel-Lucent 4029/4039 Digital Phone sets all
include the following items:
• Corded comfort handset
• Hands-free station speaker
• A number of keys
• A number of LEDs
• A set screen
• Additional key module (optional)
• Wall mounting kit (optional)
• "Big Foot" Foot stand 60° (optional)
• Bluetooth headset (available on Alcatel-Lucent IP Touch 4068 Phone set only)
3.2.2.1.2 Connecting optional equipment
3.2.2.1.2.1 External station speakers
The headset jack is located on the left side of the Alcatel-Lucent IP Touch 4028/4038/4068 sets
The 3.5 mm female jack can receive an external speakers' jack.
Customize your set to take the external station speaker into account:
1. From the Menu tab, select Settings
2. In the next screen, select My extension on an Alcatel-Lucent IP Touch 4068 Phone or Alcatel-
Lucent IP Touch 4038 Phone set, My phone on an Alcatel-Lucent IP Touch 4028 Phone set
3. In the next screen, select Jack plug
Enter your password and press Apply
4. Select Loudspeaker and press the OK button.
5. Plug the external station speaker jack into the associated set connector.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 180/382

Chapter 3 TDM deskphones

3.2.2.1.2.2 Plugging a PC or an IP phone set to an IP Touch set

The Alcatel-Lucent 8 series set includes a internal LAN switch.
This switch allows to connect:
• A PC
• A cascaded Alcatel-Lucent 8 series set

IP Touch Set PC

OR
LAN Port
PC Port

LAN
Cascaded Set

Figure 3.7: Ip Touch set connections

The internal switch has three ports:

• A LAN port
• An internal port
• A PC port, to connect a PC or another set to the LAN via the Alcatel-Lucent 8 series set
The PC port can be disabled and can be configured to force PC packets to get the default VLAN
tag. For configuration, see: Phone COS on page 40.
The internal switch privileges VoIP traffic over PC port traffic.
This switch has two waiting queues:
• The HPQ (High Priority Queue) to proceed all packets from the terminal
• The LPQ (Low Priority Queue) to proceed packets from the PC port
The switch proceeds seven HPQ packets for an LPQ packet.
Exception: packets from the PC port use the HPQ when they are tagged with a 802.1p tag and when
the tag value is superior or equal to 4.
The 802.1p tag is an IEEE standard tag which specifies the priority of the packet.
Restrictions:
• Only one additional set of equipment can be connected to the PC port
• The main IP Touch set must be locally powered to accept a cascaded IP phone
• The PC port is not available on Alcatel-Lucent IP Touch 4008 Phone sets
3.2.2.1.3 Set keys
The Alcatel-Lucent IP Touch 4028/4038/4068 and Alcatel-Lucent 4029/4039 Digital Phone sets include:
• A dialing keypad

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 181/382

Chapter 3 TDM deskphones

• An alphabetic keyboard with 34 keys

Five versions are available: French, German, International, Scandinavian and American.
• Fixed function keys
• A navigator consisting of 4 directional navigation keys
• Programmable keys (72 keys on the Perso tab and 2 personal keys)

3.2.2.2 Alcatel-Lucent 8/9 series and Alcatel-Lucent 4019 Digital Phone set description
Dialing Keypad Set Screen

Fixed Function Keys

Programmable Keys

Fixed Function Keys

Figure 3.8: Alcatel-Lucent IP Touch 4018 phone Extended Edition and Alcatel-Lucent 4019
Digital Phone Set Layout

3.2.2.2.1 Set equipment

The Alcatel-Lucent IP Touch 4018 phone Extended Edition and Alcatel-Lucent 4019 Digital Phone sets
include the following items:
• Corded comfort handset
• Hands-free station loudspeaker (basic station loudspeaker, no hands-free feature on Alcatel-Lucent
4019 Digital Phone set)
• A number of keys
• A number of LEDs
• A set screen
• Wall mounting kit (optional)
• "Big Foot" Foot stand 60° (optional)
3.2.2.2.2 Set keys
The Alcatel-Lucent IP Touch 4018 phone Extended Edition and Alcatel-Lucent 4019 Digital Phone sets
include:
• A dialing keypad with 12 keys
• Fixed function keys
• Fixed navigation keys consisting of:
• A bidirectional navigation key (up and down)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 182/382

Chapter 3 TDM deskphones

• A back key
• An OK key
• Six programmable keys

3.2.2.3 Support for long names and non-Latin characters

The OmniPCX Enterprise provides the following support for long names and non-Latin characters on
Alcatel-Lucent 8/9 series sets:
As of R7.0:
• Display of long names and names in non-Latin characters for callers, trunk groups, speed dialing
numbers, and entities
As of R8.0:
• Display of programmed key and directory key names in non-Latin characters
• Dial by name using non-Latin characters
• Input of programmed key names using non-Latin characters
• Conservation of key names in non-Latin characters when changing sets, changing an additional key
module, or migrating a user between nodes, provided the new set device supports non-Latin
characters.
Note:
Display of long names and names in non-Latin characters is not available in the Hotel/Hospital application.
Note:
Dial by name and input of non-Latin characters is available on Alcatel-Lucent 4029/4039 Digital Phone sets as of
R8.0 and on Alcatel-Lucent IP Touch 4028/4038/4068 sets as of R8.0.1.
3.2.2.3.1 Display of long names and non-Latin characters
The system allows for Alcatel-Lucent 8/9 series sets to display:
• Names up to 30 characters long in full (as of R7.0)
• Cyrillic, Greek, Chinese, Japanese, and Korean characters (as of R7.0)
• Hebrew characters (on Alcatel-Lucent IP Touch 4028/4038/4068, as of R9.1 and Alcatel-Lucent
4029/4039 Digital Phone, as of R10.0)
This includes names for:
• The caller when set is ringing
• The last caller and last number dialed (on the set's Info and Events pages)
• Trunk groups
• Speed dialing numbers
• Entities
Note:
User and trunk group names are displayed for internal calls and after a transfer. By default names display for calls
to and from other nodes in an ABC-F network. This feature is configurable. See: UTF8 resolution in an ABC-F
network on page 51.
As of Release 8.0, the system allows for Alcatel-Lucent 8/9 series sets to display:
• Programmed key names on the Perso Pages (Alcatel-Lucent IP Touch 4028/4038/4068 and Alcatel-
Lucent 4029/4039 Digital Phone sets)
• Directory key names (Alcatel-Lucent 8/9 series, Alcatel-Lucent 4019 Digital Phone, and MIPT sets)
A configuration attribute has been created for each name that can be displayed in non-Latin
characters. These configuration attributes encode characters in 8-bit Unicode Transformation Format
(UTF-8), which allows any character to be represented in the Unicode standard.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 183/382

Chapter 3 TDM deskphones

A set displays a name in non-Latin characters if:

• The node is at the appropriate software release for the feature
• The set allows for the type of characters used
• The set's Language ID is compatible with the character type of the name to display
• The UTF-8 name attribute has been configured
If any of these criteria are not met, the set displays the standard (non-UTF-8) name in Latin characters.
To configure UTF-8 name attributes, see: Configuring names in non-Latin characters on page 47
The following table shows the types of characters, in addition to Latin, that are available for each set.
The number of characters displayed depends on the type of characters. The table shows the
approximate maximum number of characters displayed for each set.

table 3.2: Available character types on set displays

Set Max Cyrillic Greek Chinese Japa- Korean Hebrew Thai

charac- nese
ters dis-
played
(approx.)

4008,401 20 Yes Yes No No No No No

8, 4019

4028,402 24 Yes Yes Yes Yes Yes Yes No

9

4038,403 30 Yes Yes Yes Yes Yes Yes No

9, 4068

MIPT 18 Yes Yes No No No No No

8028/803 Yes Yes Yes Yes Yes Yes Yes

8/8068,
80x8s
Premium
Desk-
Phone
and
8029/803
9

The following figure shows a 4068 set screen display of names of the last numbers called. The set's
Language ID is Russian.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 184/382

Chapter 3 TDM deskphones

Figure 3.9: Example display of a 4068 Set with Russian as Language ID

Since the set's Language ID is Russian, the first name is displayed in Latin characters (rather than
Chinese), the second name is in Latin characters and the third name is in Cyrillic characters.
3.2.2.3.2 Input of non-Latin characters
Starting with Release 8.0, an Input Method Editor (IME) is available on Alcatel-Lucent 8/9 series sets,
enabling input of non-Latin characters, that is, Cyrillic characters and CJK (China, Japan, Korea)
characters.
The IME enables the following features:
• Dial by name using non-Latin characters
• Input of names for programmed keys (Perso Pages) using non-Latin characters
The type of characters currently in use on a telephone set is associated with an input method: Latin
(default), Cyrillic, Pinyin, Jamo, Stroke, or Zhuyin. To make an input method other than Latin available
on a set, configure it in the Phone Class of Service (see Configuring Phone COS on page 40).
Note:
Japanese is not supported by the IME on Alcatel-Lucent 8/9 series.
Note:
The IME is available on Alcatel-Lucent 4029/4039 Digital Phone sets as of R8.0 and on Alcatel-Lucent IP Touch
4028/4038/4068 sets as of R8.0.1.
Note:
For information on the operation of the IME, refer to the document [3].
For more information on the operation and configuration of Dial by name, refer to the document [3].

3.2.2.4 Display of external called number

According to a system option, when dialing an external number the set display either shows the trunk
group name or the number entered by the user on the keypad (see: Enabling external called number
display on page 38).

3.2.2.5 Access to external applications

8 series (IP Touch) users can have direct access to external applications from their set via a soft key.
This is available on:
• 4028 IP Touch sets
• 4038 IP Touch sets
• 4068 IP Touch sets
External applications are interfaced to IP Touch sets and the OmniPCX Enterprise with the
Presentation Server, refer to the document [10].

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 185/382

Chapter 3 TDM deskphones

This feature proves particularly useful for video conference implementation.

The soft key dedicated to an application is always available from the Menu page, where application soft
keys are displayed systematically displayed under telephone feature keys.

Thu 16
09/23/03 May 2006 9:58
9:58
AM

MENU PERSO INFO

Laura
Settings JACKSON
Outgoing calls
Ir 7
Appointment
Carol SMITHForward
Textmail
New is calling Lock
Call

Events
Record Video
No camp on

Figure 3.10: Example of access to a video application from a 4068 IP Touch set

When several applications can be accessed, the system determines their priority on the set screen,
see: Defining external applications on page 38.
As of R7.1, application soft keys can be displayed when the set is being used for its telephone
capabilities.

Thu 18 May 2006 10:43

Graziella Moreno
Conversation 1:04

Enquiry call Malicious call

Forbid camp on Video

Figure 3.11: Example of access to an external application when the set is in conversation

Application soft keys are displayed according to:

• Set type (see above)
• Application status:
• Public vs. restricted
• Configured to appear according to telephone call status
• Telephone call status:
• Incoming call
• Initiated call
• Delivered call (sent to the other party)
• Established call (in conversation)
• Conference call (in conversation with several parties)
• On hold call
• Disconnected call
Soft key labels are sent to the sets when the external application is launched. They cannot be modified
while the application is running.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 186/382

Chapter 3 TDM deskphones

Application soft keys are displayed regardless of feature availability. If, for example, an IP Touch set is
in conversation with a Reflexes set, the Video soft key of the above example is available even though
no video conference can take place on a Reflexes set.

3.2.2.6 Before mounting an Alcatel-Lucent 8/9 series set on a wall

The set must be prepared to ensure the handset does not fall off the set when fixed on a wall.
1. Locate the position of the dowel to adjust on the set.

2. Move the dowel up to extract it

3. Turn it upside down.

4. Push the upside down dowel back into its slot

Once the set is fixed on the wall, the dowel hook will maintain the handset in place.
To screw the set to the wall kit, proceed as described in the wall kit documentation.

3.2.3 Detailed description

3.2.3.1 Set Connection
The Alcatel-Lucent 9 series sets are connected to a UA board.
• On a Crystal shelf, sets can be connected to a UA16, UA32 or eUA32 board. This board can be
located on the main ACT or a peripheral ACT connected via INTOF (or INTOF2) or INT-IP.
It is not possible to connect an Alcatel-Lucent 9 series set:
• On a remote ACT connected via LIO or RT2
• Behind a remote UA
• On common hardware, sets can be connected to a UAI8 or UAI16 board or a MIX type board.
These boards can either be on the main rack or on an extension rack.
Additional key modules can be connected to Alcatel-Lucent 4029 Digital Phone and Alcatel-
Lucent 4039 Digital Phone. Alcatel-Lucent 4019 Digital Phone cannot receive any additional key
module. For more details on the hardware description and the configuration procedure of the add-on
modules for the Alcatel-Lucent 9 series sets, refer to the Overview on page 337 and Configuration
procedure on page 340.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 187/382

Chapter 3 TDM deskphones

3.2.3.2 Download Characteristics

3.2.3.2.1 Binary Files
To operate correctly, Alcatel-Lucent 9 series sets need some binary files to be downloaded and stored.
These binary files must comply with the OmniPCX Enterprise version and configuration. After system
upgrade and each time a set initializes, version numbers of binary files are checked to determine
whether an update of these files is necessary.
When a file is downloaded to an Alcatel-Lucent 4019 Digital Phone, Alcatel-Lucent 4029 Digital Phone
or Alcatel-Lucent 4039 Digital Phone terminal, it overwrites any previously existing file.
3.2.3.2.1.1 Binary Files on Alcatel-Lucent 4029 Digital Phone and Alcatel-Lucent 4039 Digital Phone
Sets
A software delivery is composed of two files:
• A code binary (also named APPBIN)
• A data (or resources) binary (also named APPDATA)
As of R7.0, two more files are likely to be downloaded on Alcatel-Lucent 4029 Digital Phone and
Alcatel-Lucent 4039 Digital Phone sets:
• A localization file (also named APPL10N)
• A customization file (also name APPCUST)
Note:
Files are downloaded in the following order:
1. APPBIN
2. APPDATA
3. APPL10N
4. APPCUST
The APPL10N file, for example, cannot be downloaded if the APPBIN and APPDATA files are not up-to-date.
After downloading the code and data files, the set resets.
After downloading a localization and/or customization file, the set resets.
Code and Data
The code file contains boot software, downloader software and application software.
Its absolute file name on the Com Server is: /usr2/downbin/binnoeuabc (also accessible via /
DHS3bin/downbin/binnoeuabc)
The data file contains ringing melodies, beeps, icons, fonts and images.
Its absolute file name on the Com Server is: /usr2/downbin/datanoeuabc (also accessible via /
DHS3bin/downbin/datanoeuabc)
Code and data files must be downloaded when the versions of the files in the flash memory of the set
do not match the versions of the files on the Com Server.
Localization
As of R7.0, Alcatel-Lucent 4029 Digital Phone, Alcatel-Lucent 4039 Digital Phone sets can display
fonts for languages with non-Latin characters.
Some of these fonts are not included in the APPDATA file (Chinese, Japanese and Korean) and need a
specific localization file to be stored on the set.
Localization files are named according to the following pattern: [ISO639-2 lang id]-[40x9],
where

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 188/382

Chapter 3 TDM deskphones

• [ISO639-2 lang id] is a three-character string referring to the language according to the
ISO639-2 standard
• [40x9] means that the file applies for Alcatel-Lucent 4029 Digital Phone and Alcatel-Lucent 4039
Digital Phone sets
For example, chi-40x9, jpn-40x9, kor-40x9 are localization file names for Chinese, Japanese and
Korean fonts.
The localization files location directory on the Com Server is: /usr2/downbin/ (also accessible via /
DHS3bin/downbin/)
A localization file must be downloaded when :
• The language selected for the set requires a localization file (for example, Chinese, Korean or
Japanese selected)
• A localization file for this language - and this type of set - exists on the Com Server
• The file is not stored in the flash memory of the set, or is of a different version on the Com Server
The localization file upgrade can occur at global system initialization. In this case, it is done in the same
way as with other binary files.
A localization file download can also be needed due to a change of the set language.
If the change is done via configuration on the Com Server (MAO), the set resets (whatever the
language selected). If the change is done directly on the set, the set resets only if downloading a
localization file is needed.
Customization
As of R7.0, ringing tones and beeps can be customized on Alcatel-Lucent 4029 Digital Phone and
Alcatel-Lucent 4039 Digital Phone sets.
The customized ringing tones and beeps are stored in a customization file, which must be downloaded
on the set.
A customization file is named cust-[melody file name]-[set type] where:
• [melody file name] is the name configured in the Alcatel-Lucent 8 series and Alcatel-Lucent 9
series Phone COS Customization File Name attribute (see: Configuring Phone COS on page 40)
• [set type] is Alcatel-Lucent 4029 Digital Phone, Alcatel-Lucent 4039 Digital Phone, or 40x9
For example, if "mycompany" is configured, for a Alcatel-Lucent 4039 Digital Phone set, the system
searches for the customization file named cust-mycompany-4039. If this file is not found, the file
named cust-mycompany-40x9 is downloaded.
A customization file must be downloaded when:
• The set belongs to a category for which a melody file name has been configured
• A customization file exists on the Com Server
• The customization file is not stored on the set, or is of a different version on the Com Server
Note:
Downloading a new file may be required as a consequence of a modification of the set Phone COS or
customization file name. Thanks to a polling mechanism, the OmniPCX Enterprise will detect those changes up to
two minutes later. The sets concerned will then be updated according to their download policy (see Terminal
Download Policy on page 191).
The customization file location directory on the Com Server must be: /usr7/client/bin/ (also
accessible via /DHS3ext/client/bin/)
3.2.3.2.1.2 Binary File on Alcatel-Lucent 4019 Digital Phone Sets
One file is downloaded on Alcatel-Lucent 4019 Digital Phone terminals:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 189/382

Chapter 3 TDM deskphones

• Binary file:
Absolute file name: /usr2/downbin/binnoeuaa (also accessible via /DHS3bin/downbin/
binnoeuaa)
3.2.3.2.2 Download Duration
Download duration depends on the number of terminals, the boards used and the system architecture.
With a signalization channel on UA–link rating at 8 KBps, the lowest theoretical time for downloading
code and data files (559 KB) is 70 seconds. For Alcatel-Lucent 4029 Digital Phone and Alcatel-
Lucent 4039 Digital Phone sets, the download duration for a single terminal is about 2 minutes.
As an example, for 32 terminals on a fully equipped UA board, the download duration is approximately
50 minutes.
Using the same 32 terminals on an eUA32 board, the download duration is approximately 13 minutes.

3.2.3.3 Download Policies

Application download to a terminal is heavy in terms of bandwidth and CPU resources. It is not
possible to upgrade all the terminals during initialization of the system. Some rules can be applied, in
order to start the terminals without downloading the new software, and then, program their download
when possible.
Note:
During download, a terminal is completely out of service.
To optimize the telephone system upgrading and minimize inconvenience to users, configurable
parameters include:
• A general parameter to choose between optimizing download duration for the entire system or
optimizing download duration for individual sets, see System Download Time Optimization on page
190.
• Set parameters to define the order, priority and time of downloading, see Terminal Download Policy
on page 191
Several sets can be downloaded at the same time: see Parallel Download on page 191.
3.2.3.3.1 System Download Time Optimization
The system administrator decides whether to optimize download duration for each set or the entire
system.
The choice between these two options is determined by the parameter Download time optimization.
It depends on the time available for the download of all the sets. Possible values are:
• Minimum download duration for each set: default value
Select this value when it is important that terminals are out of service for the shortest possible time
When this value is selected, the four files (code, data, localization, customization) are downloaded
in the shortest possible time on each set. After downloading the code and data files, the set resets.
Then localization and customization files are downloaded as soon as resources are available.
Note:
There can be a certain amount of time between the code/data files download and the localization/customization
files download. During set resetting, resources are assigned to another terminal, and download on the first
terminal can resume once resources are free again.
• Minimum duration for the complete installation of all terminals
Select this value when terminals can be out of service for a longer time (e.g. at night) and when it is
important that the system is upgraded in the shortest possible time

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 190/382

Chapter 3 TDM deskphones

When this value is selected, data and code files are downloaded on all the sets of the installation in
the shortest possible time.
Localization and customization files are downloaded only once the code and data files have been
downloaded on all the sets of the installation.
3.2.3.3.2 Terminal Download Policy
Each terminal belongs to a Phone Features Classes Of Service (COS).
This Phone Features COS includes a Download policy parameter that defines the individual
download priority for the sets belonging to this class of service.
Possible values for this attribute are:
• Asap (as soon as possible): download starts as soon as possible, provided the terminal is free
• Priority download: this value is used e.g. for administrator's or VIP terminals. A COS, with this
value selected, must be reserved for a small number of terminals
• Delayed: download starts in the period defined by the values of the attributes Download start and
Download stop. This period applies every day of the week.
Note:
A change in the set language may trigger the download of a localization file for accurate display on the set. The
localization file can be downloaded outside the download period defined.
The customization file can also be downloaded outside the download period defined.
• Only on demand: download starts when triggered by the system administrator, via the downstat t
command (see: Maintenance on page 213). This protects for example, a test terminal from losing
test software.
Note:
This applies for all files, including the localization and customization files.
Note:
In all cases, whatever the COS of the set, download will not start if the terminal is in use.
3.2.3.3.3 Parallel Download
The global download duration of the entire system can be reduced by downloading several sets
simultaneously (in parallel).
In order not to exceed the system capacity, the number of sets that can be downloaded at the same
time is limited.
To avoid saturation of links on a peripheral ACT (INTOF/INT-IP) or an IP Media Gateway, the maximum
number of UA boards in one shelf that can be addressed at the same time is limited to 1.
On one board, the maximum number of sets that can be downloaded at the same time depends on the
type of UA board and the download time optimization parameter:
• When the download time optimization value Min. download dur. for install is selected, the number
of sets is limited to 32
• When the download time optimization value Min. download dur. for each set is selected, the limit
depends on the type of board:
• For an eUA board, the limit is 4
• For other boards (UA, UAI, MIX), the limit is 1
A terminal connected to a rescuable Media Gateway cannot be downloaded when this Media Gateway
is in back-up mode.

3.2.3.4 Download Interruption

Downloading can be interrupted in the following cases:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 191/382

Chapter 3 TDM deskphones

• Communication Server switchover in a duplicated Communication Server configuration

• The download application on the Communication Server crashes
After an interruption, downloading starts again (the stand-by Communication Server has become main
or the download application is restarted by the main Communication Server). All terminals that were
downloading are reset.
The concerned terminals are downloaded before all others in the next download session.

3.2.4 Configuration procedure

3.2.4.1 General
Data and binary files must be downloaded to all Alcatel-Lucent 9 series sets. According to your network
configuration, this may take some time. To minimize loss of service during the upgrade of the sets, the
initialization method and the download duration optimization can be configured via the OmniPCX
Enterprise management tools.
1. Declare the UA board in the system
2. Declare the set
3. Configure the download policy for the set
4. Configure download optimization

3.2.4.2 Declaring the UA Board

1. Select: Shelf > Board
2. Review/modify the following attributes:

Shelf Address Enter the shelf number

Board Address Enter the position of the board in the shelf

Interface Type According to the hardware configuration select:

• Crystal Hardware: UA16, UA32 or eUA32
• Common Hardware: MG-UAI 8, MG-UAI 16 or MG-
MIX type board
3. Confirm your entries

3.2.4.3 Declaring an Alcatel-Lucent 9 series Set

1. Select: Users
2. Review/modify the following attributes:

Shelf Address Enter the shelf number

Board Address Enter the position of the board

Equipment Address Enter the number of the equipment that supports the Al-
catel-Lucent 9 series set

Set Type Select the type of set:

• Alcatel-Lucent 4039 Digital Phone
• Alcatel-Lucent 4029 Digital Phone
• Alcatel-Lucent 4019 Digital Phone

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 192/382

Chapter 3 TDM deskphones

Phone Features COS Enter the number of the corresponding Phone Features
COS ID.
3. Confirm your entries

3.2.4.4 Configuring the Download Policy

1. Select: Classes of Service > Phone Features COS
2. Review/modify the following attributes:

Phone Features COS Enter the Phone Features COS ID

Download policy Select the download policy:

• Asap: Download starts as soon as there are available
resources, and the terminal is free.
• Delayed (default value). Terminals are upgraded
during the time interval specified in the Download
Start and Download Stop parameters.
• Only on demand: This value is used when download
must be managed manually.
• Priority download: This is for priority download.

Download start Enter the download start time in hours and minutes (ap-
plies to every day of the week)
Hour
This is valid or applicable only for the Delayed download
Minute
policy.

Download stop Enter the download stop time in hours and minutes (ap-
plies to every day of the week)
Hour
This is valid or applicable only for the Delayed download
Minute
policy.
3. Confirm your entries

3.2.4.5 Configuring Download Time Optimization

1. Select: System > Other System Param.> System Parameters> Alc. 9 download time
optimization
2. Review/modify the following attributes:

Alc. 9 download time optimization Select one of the two types of download duration
• Min. download dur. for each set.: default value (for
minimum downtime of each terminal)
• Min. download dur. for install. (for upgrading a large
number of terminals in a short time)
3. Confirm your entries

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 193/382

Chapter 3 TDM deskphones

3.2.5 Additional configuration operations

3.2.5.1 Configuration additional operations for sets
When a user with a Premium DeskPhone set is created, a hierarchically dependent 8&9 Series
Parameters object is automatically created. This contains specific data on display options, access
rights to external applications, user rights to customize the home page.
Note:
Additional configuration on Premium DeskPhone and Alcatel-Lucent 8/9 series sets are very similar. In the
following paragraphs all mentions to Premium DeskPhone apply to Alcatel-Lucent 8/9 series sets, unless specified
otherwise
3.2.5.1.1 Configuring Alcatel-Lucent 8/9 series parameters
1. Select: Users > 8&9 Series Parameters
2. Review/modify the following attributes

Directory Number Enter the set directory number

Application COS ID Enter application COS number (between 0 and 31)

Default value: 0

Phone COS Enter the phone COS number (between 0 and 31)
Default value: 0

Default Home Page Select the home page to be displayed when the set returns
to idle:
• Home Menu
• Home Perso
• Home Info
• Home Appli
• Home CCD
• None: the set displays the page viewed when the set
was last idle.
Default value: Home Perso
Notes:
IP Touch set users can configure their own default page from the
Menu page of their set.
Other Home pages may be available (e.g. Ccd) according to
system configuration.

Default IME A display-only value that shows the last input method char-
acter type used. Default value is No input.

Serial number Displays the set serial number. This value cannot be modi-
fied.

4059 Directory Number Displays the 4059 IP Attendant directory number, where
applicable.
3. Confirm your entries

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 194/382

Chapter 3 TDM deskphones

3.2.5.1.2 Enabling external called number display

A parameter enables to select whether the dialed number or the trunk group name is displayed on the
display of phones. This parameter applies to external outgoing communications.
1. Select System > Other System Param. > Attendant Parameters
2. Review/modify the following attribute:

Display number during conversation • True (default value): the called number is
displayed on the display
• False: the trunk group name is displayed on
the display
3. Confirm your entries
3.2.5.1.3 Defining external applications
The system can recognize up to seventeen external applications that can be accessed by phones. An
identifier must be assigned to each concerned external application.
1. Select Alcatel-Lucent 8&9 Series > 8&9 Series applications > Access to restricted
applications
2. Review/Modify the following attributes:

Application Id Enter an ID number: possible values 0 to 16

Application name Enter a name for this application (up to 16 characters)

3. Confirm your entries
3.2.5.1.4 Configuring application COS
There are three (or more) home pages: MENU, PERSO, INFO, (APPLICATIONS). The different
applications (internal and external) are displayed in the MENU tab (whatever the home page
configured in administration).
Application COSs are used to:
• Specify the order in which the different applications (internal and external) are displayed on the set's
MENU home page.
• For each external application, give or limit access to all users in this COS.
Thirty two COSs are created by default. A COS is assigned to a set in the user's Series 8&9 classes
of service. By default, COS 0 is assigned.
1. Select: Alcatel-Lucent 8&9 Series > 8&9 Series COS > Applications COS
2. Review/modify the following attributes

Application COS ID Enter the number of the COS to be viewed or modified (be-
tween 0 and 31)

Application COS name Enter a name for this COS (20 characters at the most)

When a COS number has been selected, fields are displayed as shown below, as many times as
there are applications (internal applications are displayed first, followed by external applications).

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 195/382

Chapter 3 TDM deskphones

Application Name

Priority Enter priority (between 0 and 255):

• 0: not presented, select 0 to bar use of an external
application.
• 1 (highest priority): presented at the top left
• 2: presented at the top right
• and so on...
Default value for external applications: 0
Default value for internal applications: see Table 1.

table 3.3: Default priority for internal applications

Internal application Default priority

Settings 1

Redial 2

Appointment 3

Lock 4

Text mail 5

Forward 6

No reply 7

Who am I 8

Repertory 9

Manager/Assistant 10

External application No 1 11
When they exist, other exter-
nal applications follow this
first one in the priority list.

Notes:
For internal applications, the level of priority only defines the desired location on the home page menu and not
user rights for application use. User rights are configured in the user's phone features COS.
Other applications, such as e.g. Ccd, can appear in this list, according to system configuration.
3. Confirm your entries

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 196/382

Chapter 3 TDM deskphones

3.2.5.1.5 Configuring Phone COS

Note:
The phone classes of service described here are specific to Premium DeskPhone and Alcatel-Lucent 8/9 series
sets.
Do not confuse these phone COSs with phone features COSs that apply to all sets (including Premium
DeskPhone and Alcatel-Lucent 8/9 series sets), and that are used to configure user access rights to phone
features (forwarding, conference calls, etc.).The phone features COS applying to all users is configured via:
Classes of Service > Phone Features COS
Phone COSs are used to define graphical user interface (GUI) and to grant or limit user rights to
customize home page.
Phone COSs are created by default. There are 32 COSs. A COS is assigned to the set in the user's
8&9 Series Parameters. By default, COS 0 is assigned to newly declared sets. This specific phone
COS is assigned to the concerned users via: Users > 8&9 Series Parameters.
1. Select: Alcatel-Lucent 8&9 Series > 8&9 Series COS > Phone COS
2. Review/modify the following attributes

Phone COS Enter the number of the COS to be viewed or modified (be-
tween 0 and 31)

Phone COS Name Enter a name for the COS

Right to Modify Default Home Page • Yes: users in this COS have the right to modify their set
home page
• No: users in this COS do not have the right to modify
their set home page
Default value: Yes

Home bar • Yes: the home bar changes to inform the user of set
forwarding status
• No: the home bar does not change and displays only
date information
Default value: No

Ringing Cadence • Yes: each ringing sound is followed by a short silence

• No: ringing sound is continuous
Default value: Yes

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 197/382

Chapter 3 TDM deskphones

State LED Message Determines the behavior of the LED message according to
received messages.
• State - ON (default value): when at least a message
(alarm, voice, text, callback, unanswered call) has not
been heard/viewed, the LED blinks red.
After message consultation, the Message LED is lit red.
If there is no message left in the message memory, the
Message LED is off.
• State - OFF: when at least a message (alarm, voice,
text, callback, unanswered call) has not been heard/
viewed, the LED blinks red.
After message consultation, the Message LED is off.
• State - Blinking: when at least a message (alarm,
voice, text, callback, unanswered call) has not been
heard/viewed, the LED blinks red.
After message consultation, the Message LED blinks
red.
If there is no message left in the message memory, the
Message LED is off.
• State - UA Equivalent (as per USA standard
behavior): when there is at least one new message the
LED blinks slowly
When at least one message has been archived and/or
there is at least one unanswered call, the LED is lit red.
If there is no message left in the message memory, the
Message LED is off.

Authorized IME The list of additional input method character types author-
ized.
Possible values:
• No input (meaning only the default, Latin, is
authorized)
• Cyrillic
• Pin Yin
• Jamo
• Stroke
• Zhu Yin

CBN : Display Name without Pho- • Yes: when available, displays only the name of the
neNb calling/called party
• No: displays number and name (when available) of the
calling/called party
Default value: Yes

Display Encrypted Communication • Yes: when the current call is secured with encryption,
displays the secured icon on the set screen
• No: no indication of encryption is displayed on the set

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 198/382

Chapter 3 TDM deskphones

Display Supervision State • Yes: displays the status of supervised set (the icon
depends on the status of this set) next to the
supervising key
• No: no indication of status of supervised set is
displayed on the set

Show on top update of Info Page • Yes: In idle state, displays the Info page when new
messages or new unanswered calls are recorded
• No: The page displayed remains the same when new
messages or new unanswered calls are recorded

Main page at Top Level • Yes: Every new display of the Main (Perso) page
shows the first keys of the page
• No: Every new display of the Main (Perso) page goes
back to the position it was previously

Displ. unans calls if Homepage app On sets with the external application My Homepage, by
default unanswered calls are not displayed on the Info
page. To display unanswered call information on the Info
page on sets with My Homepage, set this attribute to True.
Default value is False.

Hide Key Forward to MV/Text When value is True, the set hides the softkeys Immediate
Fwd to VM and Fwd to text. Default value is False (the
set displays the softkeys).

Display Main Page on off-hook • Yes: allows to display automatically the Main (Perso)
page on off-hook
Default value: No.

State PC port • Cascad. not filt. (IP-Phone or PC): the set PC port is
enabled. Packets are transmitted without filtering.
• PC port disabled: the set PC port is disabled. This
option is used to prevent daisy chaining of a PC behind
a terminal.
• Cascading with filtering (PC only): the set PC port is
enabled and packets are filtered:
• Frames coming from the LAN to the PC: 802.1q tags
are removed
• Frames coming from the PC to the LAN: 802.1q tags
are replaced by the default VLAN tag (VLAN=0).
This option ensures that no Voice VLAN traffic can be
sent from illegitimate sources.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 199/382

Chapter 3 TDM deskphones

Main Page Auto Display Enable • Yes: allows to display automatically the Main (Perso)
page if no action is done after a timeout: Timer No. 371
(see Timers on page 51).
• No: The page displayed remains the same.
Default value: No.
Note:
This option is useful when the emergency keys (keys
programmed with emergency numbers) are configured on the
first keys of the Main (Perso) page. It allows these keys to remain
always visible.

Second Call Ring Type Select any of the following:

• Beep (default value)
• Long Ring
• Short Ring

8&9 Series Handsfree Mode Select YES to enable echo robustness in handsfree mode.

Customization File Name Enter the customization file name for sets needing special
ringing melodies
Example:
Enter mycompany if the customization file names are as
follows:cust-mycompany-80x8 cust-
mycompany-80x9cust-mycompany-8029 cust-
mycompany-8039

Keep RTP flow This parameter controls the reboot of sets when the con-
nection with CS or PCS is lost:
As of R10.1
• True:
• Idle sets reset immediately.
• Ongoing communications are maintained, but
operations are limited: no softkey or hardkey work,
except for the Loudspeaker, Mute/unmute, volume
and Release keys. Sets reboot at the end of the
communication, or when no incoming RCTP traffic
gets to the set.
• False (default value): all sets reboot immediately, even
if in communication.
Notes:
• It is necessary to reset sets after the modification of this
parameter.
• This feature is not available on 8088 Smart DeskPhone and
80x8s Premium DeskPhonesets.
For more information, see Signaling distribution on page
20 and document [1].

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 200/382

Chapter 3 TDM deskphones

Bluetooth enabled • Yes: Bluetooth will be enabled on corresponding set

• No: Bluetooth is disabled on corresponding set
Default value: Yes
Note:
It is necessary to reset sets after the modification of this
parameter (sets will reboot twice).

Transparent reboot This parameter controls the reboot of sets:

• True: users are not informed that their set is being
reset. The set screen displays a screenshot of the
home page until the genuine home page is available
again. The set's MMI remains available.
• False: Users can see on their display that their set is
being reset. The set's MMI is available.
This feature is not available on 8088 Smart DeskPhone
sets.

Hide Services Lists • Yes: The Services softkey is not displayed on the
screen but the services are still available
• No: The list of services is available in menus
Default value: No

Voice Mail PRS application ID Enter the four-character string, which is the application ID
configured in the PRS application, to access the SIP voice
mail from the set voice mail key. Example: MY_M (Default
value: NULL).
The set screen displays a menu when pressing the voice
mail key.
When the string is empty, pressing the voice mail key
starts the TUI application, which displays no menu on the
screen but plays interactive voice guides allowing access
to the SIP voice mail.

Skin Number Skin selection is available on 8058s Premium DeskPhone,

8068s Premium DeskPhone, and 8078s Premium Desk-
Phone sets. 4 types of skins are available. Default value is
0.
1. Configure the parameter to one of the following
number: 1, 2, 3, 4
2. Reboot the set to validate your modifications
The configuration is registered and sent to the terminal.
When the parameter is set to a value other than 0, skin se-
lection is not available from the phone set user menu.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 201/382

Chapter 3 TDM deskphones

Backlight Timer Determines for how long the screen is fully lit when it goes
back to idle.
Default and minimum value: 300 (in seconds).
Maximum value: 14400.
It is necessary to reset sets after the modification of this
parameter.

Hide IP Parameters menu As of R11.2, this parameter determines whether the set IP
address is hidden for the end user consulting the set
menu: Settings > Options
Default value: False

USB Boost Charging As of R12.0, this parameter is available for 8018 Desk-
Phone sets and 80x8s Premium DeskPhone sets only.
These sets provide a USB connector which allows charg-
ing of devices such as smartphones. A boost enables a
quicker charging of phones and tablets. But boost charging
requires more power consumption than normal USB charg-
ing in case of PoE.
• Disable: Normal USB charging (default value)
• Enable: Boosted USB charging
• AUTO: Reserved for future use (=disable if set)
Reboot the set to validate your modifications.

USB Connectivity 80x8s Premium DeskPhone sets have a provision of USB

Connectivity (for peripherals such as headsets and head-
phones, for instance).
• NO: USB Connectivity is disabled
• YES: USB Connectivity is enabled
The device can be connected on USB device.
Reboot the set to validate your modifications.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 202/382

Chapter 3 TDM deskphones

Ambient Light Sensor Forced Ac- The Ambient Light Sensor is available on 8088 Smart
tive DeskPhone and 80x8s Premium DeskPhone sets. It is
mainly used for energy saving. When this parameter is
configured in OmniPCX Enterprise, it cannot be disabled
by the end user.
Configure the parameter to one of the following:
• Modifiable by ULM: the default value defined in the set
for brightness is used. This value can be modified using
the User Local Menu (ULM) on the set.
• Disable: the brightness is modulated in manual way by
user setting. All light emitting devices brightness are
synchronized.
• Enable: the brightness of the LEDs are adapted
according to the current ambient brightness. The user
can change the brightness manually even if the
parameter is activated.

Back Logo LED The ALE International logo on the back of the 8058s Pre-
mium DeskPhone, 8068s Premium DeskPhone and 8078s
Premium DeskPhone sets includes a LED indicating the
call status:
• The LED is lit white: the phone set is idle
• The LED blinks blue: the phone set is ringing
• The LED is lit blue: the phone set is in communication
This parameter enables to turn on or off the LED:
• Modifiable by ULM: the LED can be turned on or off
from the User Local Menu (ULM) of the phone set
• Disable: the LED is turned off
• Enable: the LED is turned on
When this parameter is configured in OmniPCX Enterprise,
it cannot be enabled or disabled from the phone set (ULM).

Private store URL For future use. Format is either:

• The server name, port and access path
• The server IP address, port and access path

Proxy for software update Depending on client configuration, a proxy may be

necessary for software upgrade.
• The server name, port and access path
• The server IP address, port and access path
3. Confirm your entries
Note:
If Alcatel-Lucent 8&9 Series > 8&9 Series COS > Phone COS > Display Main Page on off-hook option is set,
the Speed dial screen is displayed when going off hook from idle state.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 203/382

Chapter 3 TDM deskphones

3.2.5.1.6 Configuring names in non-Latin characters

Up to 8 languages can be managed. These languages correspond to the languages configured for the
whole system (for more information, refer to the Voice guides and music-on-hold section of the
document [1]).
Every set in the system has a Language ID (configured in system administration and/or the set user)
which corresponds one of the languages available in the system.
Note:
There is no control at system management level on the languages available for each set. All languages are
authorized, but not all character types are available on all sets. For example, the system allows the Language ID
attribute of the User object for a 4018 set to refer to Chinese, although this set cannot display Chinese characters.
The set display will use one of its available character types instead.
To allow input of non-Latin characters on a set, authorize the appropriate input method in the Phone
Class of Service (see Configuring Phone COS on page 40).
Note:
You must use the OmniVista 8770 application to configure UTF-8 names. Non-Latin characters are displayed
as ??? in mgr.
3.2.5.1.6.1 Configuring language compatibility
The compatibility configuration below determines whether a set in a language using one set of fonts
(e.g. Latin for English) can view other fonts (e.g. Greek).
Example:
English speaking users may not be familiar with Greek fonts and would rather see Greek user's name in Latin
characters. The system administrator determines, per available set types, whether sets in English will display
Greek fonts.
1. Select: Alcatel-Lucent 8&9 Series > Language Type Compatibility
2. Review/modify the following attributes

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 204/382

Chapter 3 TDM deskphones

Set Type Select the desired option among:

• 401x: for Alcatel-Lucent IP Touch 4018
phone Extended Edition and Alcatel-Lucent
4019 Digital Phone sets
• Others: for Alcatel-Lucent IP Touch
4028/4038/4068, Alcatel-Lucent 4029/4039
Digital Phone, 8028/8038/8068, 8088 Smart
DeskPhone , 8028s/8058s/8068s/8078s or
8029/8039 sets

Language type According to the set type selected above, select

the type of fonts among:
• Latin
• Cyrillic
• Chinese (where available)
• Japanese (where available)
• Korean (where available)
• Greek (where available)
• Arabic (where available)
• Hebrew (where available)
• Thai (8028/8038/8068, 8088 Smart
DeskPhone, 8028s/8058s/8068s/8078s and
8029/8039 sets only)
• All

Display Language 0 Displays the first language available in the sys-

tem

Compatibility Select YES to make the set compatible with oth-

er fonts.
Example:
If the selected instance is Cyrillic, on user sets where
the display language is English, names in Cyrillic
(configured Configuring long or non-Latin character
user names on page 48) are displayed in Cyrillic
fonts.

Display Language x Proceed with the other languages to use as per

Language 0 above
Compatibility
Note:
If your system is in an ABC-F network, ensure system
languages are defined identically for each network
node.

3. Confirm your entries

3.2.5.1.6.2 Configuring long or non-Latin character user names
1. Select: Users
2. Review/modify the following attributes

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 205/382

Chapter 3 TDM deskphones

Directory name Enter the user name in standard Latin charac-

ters

Directory First name Enter the user first name in standard Latin char-
acters

UTF-8 Directory Name Enter the user name in specific fonts (other than
Latin), or Latin long name
Reminder:
No font other than Latin can be entered via the mgr
tool. Use the OmniVista 8770 applications instead

UTF-8 Directory First Name Enter the user first name in specific fonts (other
than Latin), or Latin long name
Reminder:
No font other than Latin can be entered via the mgr
tool. Use the OmniVista 8770 applications instead

3. Confirm your entries

3.2.5.1.6.3 Configuring long or non-Latin character speed dialing names
1. Depending on the type of speed dialing number, select on of the following:
• Speed Dialing > Direct Speed Dialing Numbers > Direct SpdDl No. Pref.
• Speed Dialing > Spd Dl Numbers by Range > Speed Dialing Number
2. Review/modify the following attributes

Direct Speed Dial No. Prefix (or Speed Dial- Enter the speed dialing number to create (or
ing No. if speed dialing number by range modify)

Call Number Enter the actual number to dial

Directory name Enter the user name in standard Latin charac-

ters

Directory First Name Enter the user first name in standard Latin char-
acters

UTF-8 Directory Name Enter the user name in specific fonts (other than
Latin), or Latin long name
Reminder:
No font other than Latin can be entered via the mgr
tool. Use the OmniVista 8770 applications instead

UTF-8 Directory First Name Enter the user first name in specific fonts (other
than Latin), or Latin long name
Reminder:
No font other than Latin can be entered via the mgr
tool. Use the OmniVista 8770 applications instead

3. Confirm your entries

3.2.5.1.6.4 Configuring long or non-Latin character entity Names
1. Select: Entities

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 206/382

Chapter 3 TDM deskphones

2. Review/modify the following attributes

Entity Number Enter the entity number to create or modify

Name Enter the entity name in standard Latin charac-

ters

UTF-8 Name Enter the entity name in specific fonts (other

than Latin), or Latin long name
Reminder:
No font other than Latin can be entered via the mgr
tool. Use the OmniVista 8770 applications instead

3. Confirm your entries

3.2.5.1.6.5 Configuring long or non-Latin character trunk group names
1. Select: Trunk Groups
2. Review/modify the following attributes

Trunk Group ID Enter the ID number for this trunk group

Trunk Group Name Enter the standard name for this trunk group (up
to 10 characters)

UTF-8 Trunk Group Name Enter the name in specific other than Latin font,
or up to 20 characters if in Latin font
Reminder:
No font other than Latin can be entered via the mgr
tool. Use the OmniVista 8770 applications instead

3. Confirm your entries

3.2.5.1.6.6 Configuring non-Latin character programmed key names
You can enter names when you program keys on the set. You can also configure long or non-Latin
character names for programmed keys using the OmniVista 8770 application.
1. Select Users > Progr.Keys
2. Review/modify the following attributes:

Directory Number Enter the directory number of the set.

Key No. Enter the number of the key to be configured.

Function Select Programmed

Mnemo (Pocket,Mobile,4040,8&9) Enter a description for the function to be dis-

played next to the key in Latin characters.

UTF-8 Mnemo (8&9 Series) Enter a description for the function to be dis-
played in non-Latin characters next to the key.
Note:
You must use the OmniVista 8770 application to enter
or display non- Latin characters for this attribute. Non-
Latin characters are displayed as ??? in mgr.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 207/382

Chapter 3 TDM deskphones

3. Confirm your entries

3.2.5.1.6.7 Configuring non-Latin character manager/assistant key names
You can configure non-Latin character names for the manager key, the assistant key, and a secondary
assistant. For more information, refer to the section Manager/assistant sets section of the document
[3].
3.2.5.1.6.8 UTF–8 resolution in an ABC-F network
1. Select System > Other System Param > Network Parameters > Enable UTF8 in ABCF network
2. Review/modify the following attribute

System Option Select Enable UTF8 in ABCF network

Enable UTF8 in ABCF network • True (default value): UTF8 names are
transmitted to other nodes of the ABCF
network
• False: UTF8 names are not transmitted to
other nodes of the ABCF network
3. Confirm your entry
4. To allow UTF-8 resolution between subnetworks, select Translator > Network Routing Table
5. Review/modify the following attribute

Network number Select the appropriate network number

Enable UTF8 name sending Select True to enable UTF-8 resolution

6. Confirm your entry
3.2.5.1.7 Timers
There are specific timers for Premium DeskPhone and Alcatel-Lucent 8/9 series sets:
• Timer No. 325: display of audio and internal application confirmation:
This popup is displayed in the following cases:
• Activation/deactivation of an internal application (forward, mail, appointment, redial, dial by
name, programming, etc.)
• Activation of audio modification (headset (except when starting or answering a call), hands free
(except when starting or answering a call), group listening, mute)
• Timer No. 331: display of the popup window indicating an incoming call
• Timer No. 332: display of the confirmation popup
• Timers No. 356 (default value 20 seconds) and No. 357 (default value 60 seconds): used by the
Input Method Editor (IME) for input of non-Latin characters in Dial by name. Both timers close the
IME due to no user activity. When Timer No. 356 expires, the previous input is saved. When Timer
No. 357 expires, the previous input is cleared. The value of Timer No. 356 should be less than the
value of Timer No. 357.
• Timer No. 371: automatic display of the Perso page if no action is done during this timer.
To modify the duration of these timers:
1. Select System > Timers
2. Review/modify the following attributes:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 208/382

Chapter 3 TDM deskphones

Timer No. Enter the No. of the timer to modify

Timer units Modify as needed.

3. Confirm your entry

3.2.5.2 Prefixes and suffixes

Most telephone services, such as for example call transfer or conferences, can be activated by a prefix
(or suffix).
The rights for users to access services is determined in their class of service.
On sets, services are easily accessible via programmed keys and menu options (softkeys).
Some prefixes cannot be dialed on set because they are available by settings menu or by direct keys
(language, contrast programming, no ringing ) or because they have no meaning for sets (personal
directory programming on analog station, personal directory use on analog station).
Note:
To display the list of available prefixes in the system, use the LISTRAD command.

3.2.5.3 Configuring keys

System configuration for Premium DeskPhone additional key modules is very similar to the
configuration of additional key modules for Alcatel-Lucent IP Touch 4028/4038/4068, or Alcatel-Lucent
4029/4039 Digital Phone sets.
However, additional modules for these sets are not compatible with 3G sets and 3G additional modules
are not compatible with sets of the previous generation.
Note:
8088 Smart DeskPhone sets running in NOE mode do not support additional key modules. They include a virtual
key module available on screen (equivalent to a Smart Display Module).
3.2.5.3.1 Declaring an additional key module
1. Select: Users
2. Review/Modify the following attributes:

Directory Number Enter the directory number of the set

Add On Module 1 Select the appropriate additional key module

Add On Module 2
Add On Module 3
3. Confirm your entries
3.2.5.3.2 Key mapping and programming
Piano sensitive keys are numbered G1 to G9, from left to right.
Keys can be programmed directly on the set or in system configuration.
They are numbered as follows:
• Personal home page keys: 1 to 7
• F1 and F2 keys: 73 and 74
• Additional module keys: from 75 onwards
Keys are numbered in pairs from left to right, then from top to bottom (except for 10-key and Smart
Display Module, which are numbered from top to bottom).

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 209/382

Chapter 3 TDM deskphones

To program a key from the system:

1. Select Users > Progr.Keys
2. Review/Modify the following attributes:

Directory Number Enter the directory number of the set

Progr.Keys Enter the number of the key

Function Select the function of your choice (select Programmed to manually enter
the number dialed when the key is pressed)

Mnemo(Pocket,Mo- Enter the name to display next to the key on the LCD display (for keys on
bile,4040,IPTouch) the Perso tab or on a Smart Display Module)

UTF-8 Mnemo ( Al- If desired, enter the name in non-Latin characters to display next to the key
catel-Lucent 8&9) on the LCD display (for keys on the Perso tab or on a Smart Display Mod-
ule)

Locked Select YES to prevent users from modifying the contents of this key from
their set
3. Confirm your entries

3.2.6 Commissioning 4019 Digital Phone sets

3.2.6.1 Overview
This module presents all the actions required for commissioning Alcatel-Lucent 4019 Digital Phone
sets.

3.2.6.2 Commissionning the Alcatel-Lucent 4019 Digital Phone Set

3.2.6.2.1 Prerequisite
Before commissioning the Alcatel-Lucent 4019 Digital Phone set, you must check that the user is
declared in the OmniPCX Enterprise.
For more information, see: Configuration procedure on page 192
3.2.6.2.2 Connecting the Alcatel-Lucent 4019 Digital Phone Set
The following figure illustrates Alcatel-Lucent 4019 Digital Phone connectors.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 210/382

Chapter 3 TDM deskphones

PCX connector

Handset connector

To connect the set to the OmniPCX Enterprise:

• Turn the set over
• Plug the RJ11 cable in the corresponding set connector
• To ensure the cable is not damaged once the set is in operation, place the cable in the cable guides
provided
• Plug the other end of the cable onto the UA board on which the set has been declared
The set starts initializing automatically.
If this is the first set initialization or when there has been an upgrade of the OmniPCX Enterprise
software version, the Alcatel-Lucent 4019 Digital Phone set downloads binary and data files, and
the display indicates the progress of the initialization process.
Note:
The set can be used prior to binary and data file download. As this download may take some time, it can be
delayed by the system administrator to start when users are not at their desk, see: Configuration procedure on
page 192.
Once initialization is over, the set displays the current date and time:

Thu 12 May 10:43

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 211/382

Chapter 3 TDM deskphones

3.2.7 Commissioning 4029/4039 Digital Phone sets

3.2.7.1 Overview
This module presents all the actions required for commissioning Alcatel-Lucent 4029/4039 Digital
Phone sets.
The following figure illustrates Alcatel-Lucent 4029/4039 Digital Phone connectors.

Additional Key
Module
Attachment

Link to UA Board

Additional Key Headset

Module Jack
connector

Handset Connector

3.2.7.2 Commissionning the Alcatel-Lucent 4029/4039 Digital Phone set

3.2.7.2.1 Prerequisite
Before commissioning the Alcatel-Lucent 4029/4039 Digital Phone set, you must check that the user is
declared in the OmniPCX Enterprise.
For more information, see: Configuration procedure on page 192.
3.2.7.2.2 Connecting the Alcatel-Lucent 4029/4039 Digital Phone set
To connect the set to the OmniPCX Enterprise:
1. Turn the set over
2. Plug the RJ11 cable in the corresponding set connector
3. Plug the other end of the cable onto the UA board on which the set has been declared
The set starts initializing automatically.
If this is the first set initialization or when there has been an upgrade of the OmniPCX Enterprise
software version, the Alcatel-Lucent 4029/4039 Digital Phone set downloads binary and data files.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 212/382

Chapter 3 TDM deskphones

Note:
Both sets can be used prior to binary and data file download. As this download may take some time, it can be
delayed by the system administrator to start when users are not at their desk, see: Configuration procedure on
page 192

FLASHING...
soft: 57%

FLASHING...
soft: 100%
data: 36%

Figure 3.12: Alcatel-Lucent 4029 Digital Phone Initialization Example

The alarm, message and hands-free LEDs flash until download and initialization are over.

10/01/05 14:49
menu perso info
No new message
No non replied call
No forward activated
No associate is defined

Figure 3.13: Initialized Alcatel-Lucent 4029 Digital Phone Example

3.2.7.3 Connecting Optional Equipment

This is described:Connecting optional equipment on page 100.

3.2.8 Maintenance
This chapter describes the downstat t and getnoeversion commands and incidents relating to set
download.

3.2.8.1 getnoeversion command

As of R6.1, the getnoeversion command returns information about all the Alcatel-Lucent 9 series
sets that are declared on the node. This information includes:
• Status (in service or out of service)
• Type of set
• IP domain number (for Alcatel-Lucent 8 series sets)
• Serial number

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 213/382

Chapter 3 TDM deskphones

• Hardware version
• Software version
As of R6.1.1, the presence (or absence) of Bluetooth and additional key modules is detailed, as well as
the RAM/ROM of the set.
As of R7.0, localization and customization information is listed in the command result.
This command can be applied:
• To a specific set by using the set directory number. For example (in R7.0):
The command results are displayed directly on the maintenance console.

• To all the Alcatel-Lucent 9 series sets of the node. The results for the getnoeversion command
are stored in the file:
/DHS3dyn/mao/getnoeversion.txt
As of R6.1.1 the stored file is in .csv or .xml format, according to user choice.

3.2.8.2 downstat t Command

The downstat t command is used:
• to display the download status information for Alcatel-Lucent 9 Series sets
• to start downloads on sets configured with the Only on Demand policy
When the command is entered, information on the current version numbers of all connected terminals
is displayed. This is followed by the list of available options.
Note:
Options 6 and 7 are only displayed when the system detects sets that have not been updated, configured with the
COS download policy: Only on demand.
Example
>downstat t
*** NOE-A TDM : soft : *** - data : ***
*** NOE-BC TDM : soft : 2.10.01 - data : 2.09.01
*** NOE-BC TDM : customization file version for default : problem
*** Download time optimization: FOR EACH SET
** 2 NOE TDM phones are declared on this node !!
** 1 NOE TDM phones are not updated with the right binary !!
** 0 NOE TDM phones can be reseted for update !!

NOE TDM phone downloaded information :

-------------------------------------
1 Display up to date NOE TDM phones
2 Display NOE TDM phones not yet updated
3 Display download in progress
4 Display out of order NOE TDM phones
5 Display all NOE TDM phones
6 Update all allowed NOE TDM phones
7 Update one allowed NOE TDM phone
0 Quit

Your choice ?

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 214/382

Chapter 3 TDM deskphones

3.2.8.3 Displaying up to Date Phones

Your choice ? 1
| NOE TDM with up to date version
+------+----------+-------+-------+-----------------+--------+--------------+-------------------+------------+
| Index| QMCDU | Neqt | Nulog | Name | Type | Dw Policy | Custo | Local |
+------+----------+-------+-------+-----------------+--------+--------------+-------------------+------------+
| 0001 | 13004 | 00321 | 00005 | Yves ETROCHO | NOE-C | ASAP | | chi1.03.00 |
| 0002 | 13013 | 00445 | 00013 | MAROLEX Eléonor | NOE-A | ASAP | | |
| 0003 | 13003 | 00322 | 00021 | Alice | NOE-B | ASAP | | |
+------+----------+-------+-------+-----------------+--------+--------------+-------------------+------------+

3.2.8.4 Displaying Phones not Yet Updated

Your choice ? 2
No NOE TDM to be updated with download policy ON DEMAND

| NOE TDM firmware to be updated - Download policy : ASAP

+------+----------+-------+-------+-----------------+--------+---------+---------+-------------------+------------+
| Index| QMCDU | Neqt | Nulog | Name | Type | Soft | Data | Custo | Local |
+------+----------+-------+-------+-----------------+--------+---------+---------+-------------------+------------+
| 0001 | 13013 | 00445 | 00013 | MAROLEX Eléonor | NOE-A | 3.07.00 | N/R | N/R | N/R |
+------+----------+-------+-------+-----------------+--------+---------+---------+-------------------+------------+

No NOE TDM to be updated with download policy PRIORITARY

No download delayed

3.2.8.5 Displaying Download in Progress

Your choice ? 3
| Download in progress
+------+----------+-------+-------+-----------------+--------+--------------+-------------------+------------+
| Index| QMCDU | Neqt | Nulog | Name | Type | Dw Policy | Custo | Local |
+------+----------+-------+-------+-----------------+--------+--------------+-------------------+------------+
| 0001 | 13013 | 00445 | 00013 | MAROLEX Elonor | NOE-A | ON_DEMAND | N/R | N/R |
+------+----------+-------+-------+-----------------+--------+--------------+-------------------+------------+

3.2.8.6 Displaying out of Order Phones

Your choice ? 4
| NOE TDM out of order
+------+----------+-------+-------+-----------------+--------+--------------+-------------------+------------+
| Index| QMCDU | Neqt | Nulog | Name | Type | Dw Policy | Custo | Local |
+------+----------+-------+-------+-----------------+--------+--------------+-------------------+------------+
| 0001 | 13003 | 00322 | 00021 | Alice | NOE-B | ASAP | | |
+------+----------+-------+-------+-----------------+--------+--------------+-------------------+------------+

3.2.8.7 Displaying all TDM Phones

Your choice ? 5
| NOE TDM with up to date version
+------+----------+-------+-------+-----------------+--------+--------------+-------------------+------------+
| Index| QMCDU | Neqt | Nulog | Name | Type | Dw Policy | Custo | Local |
+------+----------+-------+-------+-----------------+--------+--------------+-------------------+------------+
| 0001 | 13004 | 00321 | 00005 | Yves ETROCHO | NOE-C | ASAP | | chi1.03.00 |
| 0002 | 13013 | 00445 | 00013 | MAROLEX Eléonor | NOE-A | ASAP | | |
+------+----------+-------+-------+-----------------+--------+--------------+-------------------+------------+

No NOE TDM to be updated with download policy ON DEMAND

No NOE TDM to be updated with download policy ASAP
No NOE TDM to be updated with download policy PRIORITARY
No download delayed

| NOE TDM out of order

+------+----------+-------+-------+-----------------+--------+--------------+-------------------+------------+
| Index| QMCDU | Neqt | Nulog | Name | Type | Dw Policy | Custo | Local |
+------+----------+-------+-------+-----------------+--------+--------------+-------------------+------------+
| 0001 | 13003 | 00322 | 00021 | Alice | NOE-B | ASAP | | |
+------+----------+-------+-------+-----------------+--------+--------------+-------------------+------------+

3.2.8.8 Incidents
The following table details incidents related to the download process.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 215/382

Chapter 3 TDM deskphones

Incident Number Meaning

0260 Beginning of downloading of a file: the file name and

terminal concerned are indicated

0261 End of downloading of a file: the file name and termi-

nal concerned are indicated

2520 Dow: 29285 downloading error

For more details about system messages , see Management of system messages - Overview

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 216/382

 Chapter

4 SIP deskphones

4.1 8001/8001G DeskPhone

4.1.1 Overview
4.1.1.1 Introduction
The following section is intended for administrators in charge of installing and commissioning
8001/8001G Deskphone sets for users declared on OmniPCX Enterprise nodes.
8001/8001G Deskphone sets are SIP sets, based on IETF standards (RFCs).
Note:
For readability purposes, in the following paragraphs, the term "set" is used to refer to 8001/8001G Deskphone
sets.

4.1.1.2 About this section

The following paragraphs provide:
• A description of the sets (see: Set description on page 218), including:
• Details on ergonomics
• A description of the files necessary to commission the sets (configuration and binary files)
• Generalities on set initialization on page 219
• Examples of DHCP server configuration when the set initialization mode is dynamic (see: DHCP
server configuration examples on page 221)
• Set configuration and deployment on page 222
• Information on set survivability (see: SIP survivability on page 230)
User operations are described in a dedicated user guide, see: document reference 8AL90895xxAA
(where xx refers to the language code of the document: US, DE, FR, etc.).

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 217/382

Chapter 4 SIP deskphones

4.1.2 Set description

4.1.2.1 Set ergonomics
4.1.2.1.1 Set overview
LCD screen (5 lines)

Call status LED

Volume keys
Line keys
Soft keys
Message and
headset keys Navigation keys

Application keys

Loudspeaker key

Keypad

Figure 4.1: Set layout

Note:
For more information on set overview, refer to the document 8001 DeskPhone user manual 8AL90895xxAA (where
xx refers to the code language of the document : US, DE, FR, etc.).
4.1.2.1.2 Set technical specifications
Physical characteristics:
• Corded handset (or headset). In its standard version, the set comes with a corded comfort handset.
• Two-level adjustable foot stand: 40° or 60°
• Wall-mountable
• Operating temperature: 0°C to 45°C
• Operating humidity: 10% to 90%
Audio characteristics:
• Audio codec: G711 (A-law and μ-law), G723.1, G.729AB
Power characteristics:
• Power over Ethernet (IEE 802.3af)
• Power adapter (DC 5V/1A output)
Connectivity:
• 8001 DeskPhone: LAN: 2 x RJ45 10/100M Ethernet ports
• 8001G Deskphone: LAN: 2 x RJ45 10/100/1000M Ethernet ports
• 1 x 3.5 mm Jack port (headset connection)
• 1 x RJ9 port (handset connection)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 218/382

Chapter 4 SIP deskphones

• 1 x RJ9 port (headset connection 4-Pin (CTIA, stereo))

• 1 x power supply port (AC/DC power adapter connection)
This supply port is reserved for future use (no power adapter available with the current version).
Note:
For a complete view of the set technical specifications, refer to the 8001 DeskPhone data sheet available on the
business portal (BPWS).

4.1.2.2 Set configuration file description

There are two configuration files:
• The first file, named public.xml, is the global configuration file. It contains parameters applying to
all sets defined in the OmniVista 8770 server, such as: proxy IP address, registrar server IP
address, preferred codecs, SNTP server IP address. This file is downloaded only when the
download server address has been specified and the specified download protocol (HTTP or
HTTPS) is used.
This file is optional. The set always tries to download this file. If it is not available from the download
server (the OmniVista 8770) when downloading files, it receives a file not found error and carries
on with downloading the next file seamlessly.
• The second file, named <MAC address>.xml, is specific to each set, defined in the OmniVista
8770 server, and only contains the parameters dedicated to a given phone. The name of this file is
constructed by inserting the physical address of the set (in hexadecimal without columns) before
the .xml extension.
Example:
If the set’s MAC address is 00:80:9F:56:07:AE, the configuration file name is 00809f5607ae.xml

This file is mandatory. The set always tries to download this file. If it is not available from the server
when downloading files, but if sets already have several parameters stored in their FLASH memory,
they carry on with initialization with these flashed parameters. If this file exists, the parameters,
provisioned using the public.xml configuration file, are overwritten.

4.1.2.3 Set binary file description

There are two binary files:
• A software binary file (for example: S2_AL8001_MD5_versionx.x.x.x-xxxx)
• A kernel binary file (for example: K2_uImage_100N_versionx.x.x)
Binary files must be deployed on the OmniVista 8770 server at the same location as the set
configuration files (see: Deploying set binaries on page 225). They are downloaded by sets after
startup or a polling timer.

4.1.3 Generalities on set initialization

4.1.3.1 Overview
By default, sets initialize in dynamic mode and retrieve automatically network parameters and the URL
to download configuration and binary files from a DHCP server (see: DHCP configuration (dynamic
initialization) on page 220). If DHCP initialization fails, the set falls to survivability mode.
If the set initialization mode is static, the set uses its internal parameters. All necessary configuration,
such as network parameters, must be manually done on the set itself (see: Configuring set network
parameters (static initialization) on page 228).

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 219/382

Chapter 4 SIP deskphones

4.1.3.2 DHCP configuration (dynamic initialization)

When initializing in dynamic mode, the set provides the following information in the DHCP Discover
message:
• Option 60: (vendor class identifier): alcatel.sip.0
• Option 55: list of requested options: subnet mask, router option, broadcast address, option 43
vendor specific info, server ID, renewal time, rebinding time and vendor class ID
Note:
Option 43 is vendor specific information, meaning that this option is defined for a specific client vendor ID. In
the DHCP offer, the data within Option 43 corresponds to the client vendor ID specified in the request.
The DHCP offer provides the following parameters:
• IP address
• Option 1: subnet mask
• Option 3: router IP address
• Option 66: IP address of the download server (that is OmniVista 8770 server)
Notes:

• The set uses the following URL to download files: https://[value of option 66]/
dmictouch/
• When the OmniPCX Enterprise DHCP is used, Option 66 is replaced by the Next Server option.
Optionally, the DHCP offer can include the following parameters, which can also be configured locally
on the set or on the OmniVista 8770 server:
• Option 6: Domain Name Server (DNS primary and secondary)
• Option 15: Domain name
• Option 12: Host name
• Option 43 with sub-option 67: this option combined with the option 66 defines the URL for file
download (see: DHCP options and combinations to define the URL for file download on page 220)
Notes:

• The URL returned to the set by the DHCP server specifies the download scheme (that is HTTPS), otherwise
the set tries to get the URL from local configuration (MMI). If the two solutions fail, the set is blocked and
resets.
• HTTPS is supported with device authentication: the set embeds the requested certificates for its authentication.

4.1.3.3 DHCP options and combinations to define the URL for file download
The following table displays the DHCP options and the possible combinations to define the URL for file
download.

Next-server Option 66 Option 43- Option 43- Download path

>sub option 67 >sub option 67
(FULL Path) (relative path)

x https://next-server/dmictouch/

x x https://next-server/sub-option
67/

x https://option 66/dmictouch/

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 220/382

Chapter 4 SIP deskphones

Next-server Option 66 Option 43- Option 43- Download path

>sub option 67 >sub option 67
(FULL Path) (relative path)

x x https://option 66/sub-option 67/

x x https://option 66/dmictouch/

x x x https://option 66/sub-option 67/

x Invalid combination

x Sub-option 67

x x x Sub-option 67

x x Sub-option 67

x x Sub-option 67

4.1.4 DHCP server configuration examples

4.1.4.1 OmniPCX Enterprise DHCP configuration
The recommended DHCP server is the DHCP server of the OmniPCX Enterprise. It must be configured
before the set downloads its files.
Configuration consists in entering the IP address of the OmniVista 8770 server in standard option 66.
You may enter the FQDN if the DNS server is specified in the configuration file.
To configure the OmniPCX Enterprise DHCP server:
1. In the OmniPCX Enterprise configuration tool, select DHCP Configuration > Classes
2. Create a new class with the following parameters:

Name Enter a name for this class

Vendor ID Enter alcatel.sip.0

TFTP Server address Enter the IP address of the OmniVista 8770 server

Default lease time (mn) Enter 60

Max lease time (mn) Enter 1440

Configuration file Leave this field blank

3. Confirm your entries
4. Select DHCP Configuration > Apply modifications

4.1.4.2 Windows 2003 DHCP configuration

The following sections describe configuration example with Windows DHCP server.
This configuration consists in:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 221/382

Chapter 4 SIP deskphones

1. Defining a range of IP addresses (not described here)

2. Defining standard parameters, such as subnet mask, router option, broadcast address, renewal
time, rebinding time (not described here)
3. Configuring option 66 on page 222
4. Defining a vendor class for sets on page 222
5. Activating the scope of IP addresses on page 222
To access Windows DHCP configuration, go to: Start > All Programs > Administrative Tools >
DHCP
4.1.4.2.1 Configuring option 66
1. In the DHCP configuration window, right click the range of IP addresses and select Configure
Options...
2. In the General tab, check the 066 Boot Server Host Name
3. In the String value field, enter the IP address of the OmniVista 8770 server
4. Click OK
4.1.4.2.2 Defining a vendor class for sets
1. In the DHCP configuration window, right click the DHCP server name and select Define Vendor
Class
2. Click Add to define a new DHCP Vendor Class
3. Enter a Display name for the Vendor Class
4. To specify the Vendor Class Identifier string, click the ASCII field and type alcatel.sip.0
5. Click OK
The new vendor class is created
6. Click Close
4.1.4.2.3 Activating the scope of IP addresses
In the DHCP configuration window, right click Scope Options under the range of IP addresses and
select Activate.

4.1.5 Set configuration and deployment

4.1.5.1 Deployment procedure overview
The 8001 DeskPhone set deployment consists in:
• Configuring the set on page 222
Note:
It is recommended to use the Users application of OmniVista 8770 (rather than the OmniPCX Enterprise
configuration window) for set configuration. The only procedure presented here applies to he Users
application.
• Deploying set binaries on page 225
• Commissioning the set on page 227
If the set is already in operation, you may be requested to update set binaries later. In this case, refer
to: Updating set binaries on page 229.

4.1.5.2 Configuring the set

4.1.5.2.1 Creating users as SIP extension
Before configuring the set, the user must be declared as SIP extension in the Users application of the
OmniVista 8770:
1. From the Users application of the OmniVista 8770, click the Users tab

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 222/382

Chapter 4 SIP deskphones

2. Access the contextual menu and select Create User

3. In the Common Attributes frame, complete the following fields:

User type Click and use the drop-down menu to select the OXE type, which allows
to create a user on the OmniPCX Enterprise

Salutation Use the drop-down menu to select the user title

Last Name Enter the user name

First Name Enter the user first name

User ID Modify if necessary the displayed user identifier

The user identifier is built from the name and first name

A new frame appears in the properties area to configure user parameters

4. To enter manually the OmniPCX Enterprise parameters, leave the OXE Meta-Profile field blank and
complete the following fields:

OXE ID Click and use the browser to select the desired OmniPCX Enterprise

OXE directory number Enter the user directory number

Device Type Click and use the drop-down menu to select SIP extension
5. Click the validate icon to apply your modifications

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 223/382

Chapter 4 SIP deskphones

The user is declared in the database of the OmniVista 8770 and the corresponding OmniPCX
Enterprise
Note:
For more information on user creation from the OmniVista 8770, refer to the section Users of the OmniVista 8770
Online Help.
4.1.5.2.2 Creating and associating a set to a user
Set configuration for a user consists in creating and associating a set to a user from the OmniVista
8770 application. This operation automatically creates a configuration file, required for set
commissioning, on the OmniVista 8770 server.
To create and associate a new set to a user in one step:
1. From the Users application of the OmniVista 8770, click the Users tab
2. Expand the tree structure and select the user to which the set must be associated
3. Access the contextual menu and select Associate SIP device > New, then select 8001
DeskPhone

4. In the General tab, review/modify the following attribute:

MAC address Enter the set MAC address. This MAC address can be entered with or
without the colon separator
5. In the Network tab, review/modify the following attributes:

First DNS and/or Sec- Double click and use the drop-down menu to select the DNS server
ond DNS
6. In the Phone settings tab, review/modify the following attributes:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 224/382

Chapter 4 SIP deskphones

Set time mode If an STP server is configured, double click and use the drop-down menu
to select SNTP
Note:
An SNTP server allows to display the date and time on the set home page
instead of the user first name and last name.

SNTP server Enter the IP address of the SNTP server

Timezone Select the corresponding time zone

7. Click the validate icon to save your modifications
The new set is created in the corresponding OmniPCX Enterprise and associated to the
corresponding user. This set is displayed below the user in the tree structure of Users application
When the set is created and associated to a user, a configuration file with the <MAC address>.xml
format is automatically created on the OmniVista 8770 server for this set. It is copied on the OmniVista
8770 in the directory: /<8770 path>/Data/DM/Deploy/VHE8082.
Note:
The sets can also be declared from the Devices application of the OmniVista 8770 and associated to the user
later, using the same application.

4.1.5.3 Configuring sets via mass provisioning

To configure sets via mass provisioning, refer to the sections Configuring a list of new users and
Configuring devices via mass provisioning of the document [43].

4.1.5.4 Deploying set binaries

4.1.5.4.1 Creating the deployment package including set binaries
Prerequisite: A synchronization between the OmniVista 8770 and the corresponding OmniPCX
Enterprise is required before configuring a deployment package for set binaries.
This operation consists in associating set binary files to a device type:
1. Download the set binaries from the Enterprise Business Portal (zip file including Kernel and/or
software files)
Note:
For more information on the available binary files, refer to: Set binary file description on page 219.
2. Save the set binaries on the OmniVista 8770 server (the file must be unzipped in the selected
folder)
3. From the Devices application, click the Applications tab
4. Expand the tree structure to the OmniPCX Enterprise to which sets are attached

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 225/382

Chapter 4 SIP deskphones

5. There are two cases:

• If no package is associated to the 8001 DeskPhone type:
1. Right-click the set type and select Add Package
2. In the Deployment Package window, enter the deployment package name in the
Application name field
Note:
Ensure that the deployment package name matches the required format.
• If a package has already been created, select this package
Caution:
It is necessary to use the same package when upgrading sets. This allows to use the access path
declared in the set configuration file for the deployment package and the binary upgrade process.
6. Click the Kernel line
A browser opens
7. Select the kernel file you downloaded and click OK
8. Click the Tel. application file line
A browser opens
9. Select the software file you downloaded and click OK
10.Click the validate icon to save your modifications
11.Repeat the procedure for other binary files to associate to the set type
4.1.5.4.2 Deploying the binary package
Deploying the binary package consists in making it available for download on the OmniVista 8770
server. Deploying the binary package is necessary after a package has been created or modified (see:
Creating the deployment package including set binaries on page 225).

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 226/382

Chapter 4 SIP deskphones

To deploy a package:
1. From the Devices application, click the Applications tab
2. Expand the tree structure to display the package to deploy
3. Right-click the package to deploy and select Deploy Package
The Task Type window opens
4. Select Simple job
A scheduler window opens.
5. Leave values unchanged to deploy immediately, or schedule the exact time and date for
deployment and click OK
Note:
Set binary deployment can be verified from the Scheduler application: select the corresponding task and
select the Status tab to the right of the window.
Results:
• The OmniVista 8770 decompresses the rar file, and copies the file in the OmniVista 8770
deployment repository, where configuration files are located.
• The OmniVista 8770 generates the KD00000290.cfg and/or FD00000290.cfg files, according to
the files selected in the deployment package. cfg file names are hardcoded in the set. If a kernel or
software binary is not selected, the latest corresponding cfg file (created with the last package) is
retained and remains active.
If the kernel *.rar file is only selected in the deployment package, the OmniVista 8770 updates the
KD00000290.cfg and the FD00000290.cfg does not change (no deletion or update).
If the software *.rar file is only selected in the deployment package, the OmniVista 8770 updates
the FD00000290.cfg and the KD00000290.cfg does not change (no deletion or update).
Note:
All 8001 DeskPhone sets configured in the OmniVista 8770 server are updated (same phone set binaries for all
OmniPCX Enterprise instances declared on the OmniVista 8770).

4.1.5.5 Commissioning the set

4.1.5.5.1 Prerequisites
Before commissioning a set, ensure that:
• If dynamic initialization is used, a DHCP server is configured (see: DHCP server configuration
examples on page 221)
• If static initialization is used, a free IP address is available for the set
• The set is created and associated to a user in the OmniVista 8770 (see: Creating and associating a
set to a user on page 224)
• The set configuration, cfg and binary files are registered in the OmniVista 8770 server (same
access path) (see: Deploying set binaries on page 225)
4.1.5.5.2 Plugging the set
To connect the set to the LAN:
• If the set is powered by PoE:
1. Turn the set over
2. Plug the RJ45 cable into the set LAN connector
3. Connect the RJ45 cable to the LAN itself via a PoE hub/switch (IEEE802.3af compliant)
• If the set is not powered by PoE, plug the AC/DC external adapter to the set power supply
connector (DCSV) and connect the plug to the power supply.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 227/382

Chapter 4 SIP deskphones

Power adapter or Power over Ethernet

connector (PoE) connector
(DSCV) (LAN)

Figure 4.2: Set power connectors

Once the set is connected and powered up, it automatically starts initializing.
The initialization process consists in:
1. Network initialization and setup
After initialization, the home screen is displayed for a few seconds.
2. Configuration file download
3. Software upgrade
4. Kernel upgrade
4.1.5.5.3 Configuring set network parameters (static initialization)
By default the set starts in dynamic mode. Skip this section if using dynamic mode with DHCP.
To configure set network parameters in static mode:
1. After startup, press the OK button or Menu soft key, and go to System Settings > Advanced
Settings > Advanced
2. Select Network > LAN Port
3. Select the Static mode
Note:
The available initialization modes are: Static, DHCP (default option), or PPPoE
4. Configure the set IP parameters (IP address, IP subnetwork mask, and gateway (that is router))
5. Configure DNS settings
6. Configure port management settings
7. Press the Save soft key
4.1.5.5.4 Configuring the file download URL (static initialization)
The file download URL must be declared on the set. This URL is used by the set to download
configuration, cfg and binary files registered in the OmniVista 8770 server.
1. From the home screen, press the OK button or Menu soft key, and go to System Settings >
Advanced Settings > Advanced
2. Select Auto Provision
3. In the URL field, enter the access path to download the file : https/<OmniVista 8770 IP
address>/DM/dmictouch/
4. In the Protocol field, use the soft keys to select HTTPS
5. Press the Save soft key
6. Restart the set to apply modifications

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 228/382

Chapter 4 SIP deskphones

4.1.5.6 Updating set binaries

To update set binaries, on the OmniVista 8770, create and deploy a package including the new set
binaries (see: Deploying set binaries on page 225). The set binary and cfg files are registered in the
OmniVista 8770 server in the same location as the configuration file.
The set must restart to proceed with a binary update (transfer is performed via HTTPS).
This can be done:
• Manually, by disconnecting the set and plugging it in again
• Automatically, after a polling timer. The set monitors the OmniVista 8770 server to check if new
binary files are available. When there are new binary files, the set automatically restarts and
proceeds with update
All 8001 DeskPhone sets configured in the OmniVista 8770 server are updated (same phone set binary
for all OmniPCX Enterprise instances declared on the OmniVista 8770).

4.1.5.7 Configuring LDAP

If the user has access to an LDAP directory, configure the LDAP settings in the 8001 DeskPhone using
its web interface:
1. From a computer, open a web browser and enter the IP address of the 8001 DeskPhone (for
example: http://192.168.201.98)
Note:
To obtain the IP address, press the C key on the phone.
2. Enter the credentials (login/password) required to access the web interface of 8001 DeskPhone
By default the values are root (login) and root (password).
The home page is displayed
3. Go to Phonebook > LDAP

Figure 4.3: LDAP configuration page example

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 229/382

Chapter 4 SIP deskphones

4. According to your needs, complete the LDAP settings

Example:
LDAP: on
LDAP Name Filter:(sn=%s)
LDAP Number Filter:(telephoneNumber=%s)
Server Address: 192.168.201.98
BASE:DC=ldap,DC=MY_COMPANY,DC=com
Username：[email protected]_company.com
Password：65432159
LDAP Name Attributes 1: sn
LDAP Name Attributes 2: cn
LDAP Number Attributes 1: telephoneNumber
Note:
For the meaning of each field, point the mouse over the corresponding question mark icon: this displays a
hover help window.
5. Click Submit to validate your modifications

4.1.6 SIP survivability

4.1.6.1 Overview
A set switches to "survivability" in the following cases:
• When the DHCP server is out of service or not reachable (see: DHCP survivability on page 230)
• When the connection with the main SIP server is lost (see: SIP survivability on page 230)
• When the Device Manager (that is the OmniVista 8770) is not reachable (see: DM survivability on
page 230)

4.1.6.2 DHCP survivability

At initial start in dynamic mode, if no DHCP server is reachable, the set sends periodic DHCP requests
until it gets an answer from a DHCP server.
At the next start in dynamic mode, if no DHCP server is reachable but a previous configuration is found
in the set flash memory, the set enters in ”DHCP survivability” and uses this configuration.
In DHCP survivability mode, every minute, the set tries to recover an IP address from the DHCP server.
It sends a DHCPDISCOVER message containing its current IP address (stored in the flash memory).
When the set receives an answer from the DHCP server, it checks the IP address received:
• If the address received is the same as the one stored in the flash memory, this address is used
• If the address is different, the set resets

4.1.6.3 SIP survivability

When connection with the OmniPCX Enterprise is lost, the set switches to SIP survivability on a PCS.
According to configuration, the set exits survivability:
• As soon as the OmniPCX Enterprise is available again: transient configuration
• When the survivability server fails or becomes unavailable (provided the OmniPCX Enterprise is
available again): persistent configuration

4.1.6.4 DM survivability
At first start, If the DM server is unreachable, the set reboots periodically until it gets its configuration
file from the DM server.
At the next start, if the DM server is unreachable, the terminal enters in “DM survivability” mode and
uses the last configuration file flashed in memory.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 230/382

Chapter 4 SIP deskphones

4.2 8012 DeskPhone

4.2.1 Overview
4.2.1.1 Introduction
8012 Deskphone sets are entry level SIP terminals intended for use in business mode and hotel mode
on the OmniPCX Enterprise.
The following paragraphs are intended for administrators in charge of installing and commissioning
8012 Deskphone sets on the OmniPCX Enterprise. For readability purposes, the term "set" is used in
the rest of this document to refer to 8012 Deskphone sets.

4.2.1.2 About this section

The following paragraphs detail:
• General information on set characteristics:
• Standards compliant with the sets on page 231
• Environmental constraints on page 232
• Set power supply on page 232
• Applicable protocols on page 233
• A description of the sets (Set description on page 236), including:
• Details on ergonomics
• A quick view of set features
• A description of the SIP files necessary to commission the sets
• Information on security
• Information on set survivability
• Commissioning and configuration procedures: Set configuration and deployment on page 238
• A complete list of set parameters, available on the OmniVista 8770 for business and hotel
configuration: 8012 list of features on page 248
• Information on troubleshooting: Troubleshooting on page 253

4.2.1.3 Standards compliant with the sets

4.2.1.3.1 Hearing aid compatibility
The Hearing Aid Compatibility (HAC) feature consists in providing audio assistance for hearing
impaired people.
The set handset is compliant with the following standards:
• TIA/EIA-504 standard: telecommunication telephone terminal equipment magnetics fields and
acoustic gain requirement for handset telephone intended for use by the hard of hearing
• ETS 300 381 : inductive coupling of telephone earphones to hearing aids
4.2.1.3.2 Narrowband audio
The 8012 Deskphone audio quality complies with the following narrowband VoIP standards:
• TIA/EIA810B: acoustic performance for narrowband digital wireline transmission for VoIP
• ETSI ES 202 737: speech processing, transmission and quality aspects, transmission requirements
for narrowband VoIP terminals (handset and headset)
• ETSI ES 202 738: speech processing, transmission and quality aspects, transmission requirements
for narrowband VoIP terminals (loudspeaker and handsfree)
The codecs available for narrow band communication interoperability are the following:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 231/382

Chapter 4 SIP deskphones

• G.711 A and µ law 64 kbit/s with packets loss concealment G.711. Minimum framing for G.711
payload packet: 20 ms for packet emission, 10 ms supported for packet reception
• G.729A 8 kbit/s with annex B
4.2.1.3.3 Noise and acoustic shock
8012 Deskphone sets comply with the European standard (TBR8 - annex C), US standard (UL/CSA
60950), and Australia standard (AS/ACIF S004) for noise and acoustic shock, as shown in the table
below.

Standard Short duration peak acoustic Long duration acoustic pres-

pressure (short duration im- sure (steady state input)
pulses)

Europe: TBR8 - annex C 130 dBspl 118 dBspl (rms)

US: UL/CSA 60950 136 dBspl 125 dB(A)

Australia: AS/ACIF S004 123 dBspl 120 dB(A)

4.2.1.4 Environmental constraints

Storage, transportation and sets environment comply with the following standards:
• ETS 300 019 1.1, Storage, Class 1.2: Weather protected, Not temperature controlled locations
• ETS 300 019 1.2, Transportation, Class 2.3: Public transportation
• ETS 300 019 1.3, In Use, Class 3.2: Stationary use, Partly Temperature controlled locations
4.2.1.4.1 When in use
• Temperature: to achieve optimum reliability, the ambient temperature must be between -5°C and
+45°C. In degree Fahrenheit, the ambient temperature must be between 23°F and 113°F
• Relative humidity: relative humidity must be between 5% and 95% (without condensation)
4.2.1.4.2 Storage
• Temperature: temperature must be between -25°C (-13°F) and +55°C (131°F)
• Relative humidity: relative humidity must be between 10% and 100% (without condensation)
4.2.1.4.3 Transportation
• Temperature: temperature must be between -40°C (-40°F) and +70°C (158°F)
• Relative humidity: relative humidity must not exceed 95% (without condensation)

4.2.1.5 Set power supply

The set can be powered in two ways:
• Locally, from the main socket via an AC/DC external adapter.
• Via Ethernet, using PoE (Power over Ethernet) technology.
PoE offers the advantage of simplified wiring. It also allows the system to be secured more easily. A
single backup power supply can be used for all devices connected to a switch.
PoE can be performed:
• Via the Power Patch Panel A4098 PP.
• Via a switch compatible with the 802.3af standard
Sets send power information to the switch they are connected to. This information consists of:
• The class number

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 232/382

Chapter 4 SIP deskphones

• The power value negotiated through LLDP

LLDP POE negotiation is used at initialization in addition to 802.3af to provide some more accurate
information than the class number. The power value negotiated depends on USB devices connected
on the set, according to the following formula:
PLLDP negociated = Pmaxterminal +PUSB devices + 1.5W
Equipment connected to the PC port is not taken into account and requires separate power feeding.

table 4.1: Power supply summary

Power Patch Panel Yes

802.3af compatible Yes

PoE class 3 max

Power reduction LLDP-MED

Power consumption is indicated: Table 2.

table 4.2: Set power consumption

Backlight is on X X X X X X X X

LAN Ethernet link is X X X X X X X X X

connected (1 Gbps)

PC Ethernet link is X X X X X X X
connected (1 Gbps)

USB 5V 600mA X X X X X

The phone is ringing at X

maximum volume

Handsfree communica- X
tion (nominal volume)

The phone is idle X X X X X X

Measured PoE Con- 10.93 10.01 10.70 10.28 9.91 6.69 4.94 4.55 3.88
sumption (W) (RMS
values)

4.2.1.6 Applicable protocols

4.2.1.6.1 LLDP-MED
The LLDP / LLDP-MED protocol allows information exchange between end devices and adjacent LAN
switches. This mechanism is based on IEEE 802.1AB and ANSI TIA 1057 (LLDP-MED) standards.
Sets comply with the LLDP-MED protocol.
By default, LLDP-MED is activated and allows:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 233/382

Chapter 4 SIP deskphones

• Automatic VLAN assignment

• Power over Ethernet negotiation. The LLDP POE negotiation is used at initialization in addition to
the 802.3af protocol or 802.3az protocol
• Auto discovery geolocalization information
Note:
Not available in an OmniPCX Enterprise hotel configuration.
• To send inventory information of terminal to adjacent LAN switch.
Note:
Not available in an OmniPCX Enterprise hotel configuration.
Inventory information sent by a set includes:
• Hardware revision
• Software version
• Firmware version
• Serial number
• Manufacture name (set to ALE International)
• Model name
• Asset ID (set with the SIP configuration file to the set MAC address)
4.2.1.6.2 SNTP
The Simple Network Time Protocol (SNTP) Version 4 is an adaptation of the Network Time Protocol
(NTP) used to synchronize computer clocks in the Internet.
The set complies with SNTP. An SNTP server provides the universal time (UTC) to the set at
initialization and periodically when in operation.
SNTP allows to provide universal time (UTC) to the set and to avoid the internal clock drift.
The Communication Server can be used as SNTP server.
The SNTP address can be provided to the set through DHCP or can be configured in OmniVista 8770
(as of R2.0) and sent in configuration files.
Note:
In case of an SNTP server failure:
• The terminal runs with the local clock, based on the oscillator that may lead long term drift
• If the terminal has a hardware reset while the SNTP server is down, at restart the clock is set to the value it had
at the last software reset. In other words, when a hardware reset occurs, and the phone restarts, the Time/Date
is set to an approximate value, enabling certificates to work.
4.2.1.6.3 Obtaining VLAN information
8012 Deskphone sets can obtain VLAN information via static configuration. Alternatively: Automatic
VLAN Assignment (AVA) or Link Layer Discovery Protocol (LDDP) / Link Layer Discovery Protocol -
Media Endpoint (LLDP-MED) can be used.
LLDP/LLDP-MED allows the retrieval of the end device’s VLAN identifier (the terminal’s “voice” VLAN)
from the LAN switch. VLAN information is acquired only from the LLDP-MED network policy item
containing the “voice” application type. Multi-network policy is supported. The LLDP/LLDP-MED client
is activated by default in the terminal during initialization, but must be non-blocking in case the LAN
Switch does not respond. To keep compatibility with other network connective devices and considering
the network load, the set sends three LLDP packets at the most, to make sure the adjacent network
connective device can receive such packets.
There are two phases involved in VLAN acquisition:
1. VLAN acquirement:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 234/382

Chapter 4 SIP deskphones

This happens at the beginning of the LLDP procedure. The terminal waits for a certain time to get
the LLDP/LLDP_MED response, after the first LLDP/LLDP_MED advertise packet has been sent
out. At this stage, the terminal only accepts valid VLAN information, and ignores invalid VLAN
information (e.g VLAN 0 or VLAN 4095). If valid VLAN information is obtained, the set enters a
VLAN_acquired state; if not, it enters a VLAN_no_acquired state
2. VLAN update:
This happens after VLAN acquirement, and is used for possible VLAN updating. The IP Phone
resets if new VLAN information is detected. Behavior differs according to the state of the set after
VLAN acquirement. In a VLAN_acquired state, the IP Phone resets to detect VLAN modification
(from a valid VLAN to an invalid VLAN). In VLAN_no_acquired state, the set ignores this invalid
VLAN information
By default, this feature is active. The set must be connected to a switch supporting LLDP to obtain
VLAN information.
The priority orders of VLAN ID acquirement in dynamic mode is: LLDP > AVA > Static
For more information, see: 8002/8012 Deskphone - Windows 2003 server DHCP configuration
exampleAutomatic VLAN Acquisition (AVA).
4.2.1.6.4 DSCP/DiffServ/802.1p
A VLAN number can be configured. This VLAN number is used by all outgoing traffic.
The VLAN identifier can be configured in three different ways (which are mutually exclusive):
• Statically, by using the Settings menu
• Dynamically, by using the AVA mechanism
• Through LLDP/LLDP-MED, if enabled on the terminal
Note:
• VLAN acquisition through LLDP-MED takes precedence over AVA through DHCP.
• Automatic VLAN id distribution via a RADIUS server is also possible, but this is fully transparent to the terminal
(nothing operation requested on the terminal).
802.1Q tagging is enabled when a VLAN id is configured, that is:
• In static mode, a VLAN identifier has been configured via MMI
• In dynamic mode, a VLAN identifier has been received through AVA or LLDP
The DSCP/diffServ protocol allows to differentiate the priority to associate to each traffic type: voice,
video, SIP signaling application and default priority.
The 802.1.p (layer 2 priority) and DSCP/Diffser (layer 3 priority) priority values for SIP and audio traffic
can be configured in the configuration file. If no value is configured, a default value is used.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 235/382

Chapter 4 SIP deskphones

4.2.2 Set description

4.2.2.1 Set ergonomics
4.2.2.1.1 Set overview
Ringing LED

Set Screen

Navigation Keys
Dialing
Keypad
Fixed Function keys with
or without LED Indication

Figure 4.4: 8012 Deskphone set layout

Note:
For more information on set overview, refer to the document 8012 Deskphone user manual 8AL90878xxAA (where
xx refers to the code language of the document: US, DE, FR, etc.).
4.2.2.1.2 Set equipment
The sets include the following items:
• Corded comfort handset
• Hands-free station speaker
• An LCD set screen
• A ringing LED

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 236/382

Chapter 4 SIP deskphones

• A dialing keypad
• Navigation keys
• Fixed function keys with or without LED indication
• Connectors including:
• 10/100M/1000Mb/s Ethernet LAN (POE supported, 1000Mb/s available)
• PC port management (Gigabit speed)
• 3.5 mm female jack for headset connection
• Mini-B USB connector for connection to the specific Power Adapter

4.2.2.2 SIP files

The download server is typically the OmniVista 8770, but can be another server (for an example of
download server configuration, see: 8002/8012 Deskphone - Apache in HTTPS configuration
example).
4.2.2.2.1 SIP configuration files
There are two configuration files. For more information on their deployment and syntax, see:
8002/8012 Deskphone - Manual installationConfiguring SIP configuration files.
The first file, named: sipconfig.txt, is the global SIP configuration file and contains parameters
applying to all SIP phones found in the system. This file is downloaded only when the download server
address has been specified and uses the download protocol indicated in the corresponding parameter
(HTTP or HTTPS).
This file is optional, that is to say: all 8012 Deskphone parameters can be configured in the specific
configuration file. It is optional from an administrator point of view: in other words, the phone always
tries to download this file. If the file is not available from the download server when sets download their
files, the sets receive a file not found error and carry on downloading the next file seamlessly.
The second file, named: sipconfig-MacAddress.txt, is specific to each SIP phone found in the
system and as such, only contains the parameters dedicated to a given phone (user name…). The
name of this file is constructed by inserting the physical address of the phone (in hexadecimal without
columns) before the .txt extension.
Example:
If the phone physical address is: 00:80:9F:56:07:AE, the specific SIP file name is:
sipconfig-00809F5607AE.txt.
This file is mandatory since it contains configuration parameters specific to each phone. Again, it is
mandatory from an administrator point of view: the phone always tries to download this file, but if the
file is not available from the OmniPCX Enterprise when sets download their files, and if phones already
have several parameters stored in their FLASH memory, they carry on with initialization with these
flashed parameters. The parameters, provisioned using the global SIP configuration file, are
overwritten by specific configuration file parameters if both exist.
4.2.2.2.2 SIP binary files
SIP binary files must be stored on the download server at the same location as the sipconfig.txt
and sipconfig-MacAddress.txt configuration files. For more information on how to update them,
see: Updating binaries on page 243.
These binary files are downloaded from the server whose IP address is either retrieved from a DHCP
server (dynamic configuration) or defined in the set itself (static configuration).
The available binary files are:
• app8012 (application)
• bin8012

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 237/382

Chapter 4 SIP deskphones

• dat8012

4.2.2.3 Security
The sets support the 802.1x MD5 and 802.1x TLS authentication protocols.

4.2.2.4 Survivability
A set switches to "survivability" in the following cases:
• When the DHCP server is out of service or not reachable (see: DHCP survivability on page 238)
• When the connection with the main SIP server is lost (see SIP survivability on page 238 for more
details).
• When the Device Manager (that is the OmniVista 8770) is not reachable (see DM survivability on
page 238)
4.2.2.4.1 DHCP survivability
At first start in dynamic mode, if no DHCP server is reachable, the set sends periodic DHCP Requests
until it gets an answer from a DHCP server.
At the next start in dynamic mode, if no DHCP server is reachable but a previous configuration is found
in the set flash memory, the set enters in ”DHCP survivability” and uses this configuration.
In DHCP survivability mode, every minute, the set tries to recover an IP address from the DHCP server.
It sends a DHCPDISCOVER message containing its current IP address (stored in the flash memory).
When the set receives an answer from the DHCP server, it checks the IP address received:
• If the address received is the same as the one stored in the flash memory, this address is used
• If the address is different, the set resets
4.2.2.4.2 SIP survivability
When the connection with the OmniPCX Enterprise server is lost, the set switches to SIP survivability
on a PCS.
According to configuration, the set exits survivability:
• As soon as the server is available again: transient configuration
• When the survivability server fails or becomes unavailable (provided the server available again):
persistent configuration
For more information on configuration, see: Configuring SIP Survivability on page 31.
4.2.2.4.3 DM survivability
At first start, If the DM server is unreachable, the set reboots periodically until it gets its configuration
file from the DM server.
At the next start, if the DM server is unreachable, the terminal enters in “DM survivability” mode and
uses the last configuration file flashed in memory.

4.2.3 Set configuration and deployment

The following procedure requests that the OmniVista 8770 version is at least R.2.0.07.01.d.

4.2.3.1 Overview
Before commissioning a set, verify that a free IP address is available for the set.
4.2.3.1.1 Management tools
The OmniPCX Enterprise users can be created either from the Users application of the OmniVista
8770 or from the Communication Server standard interfaces.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 238/382

Chapter 4 SIP deskphones

Caution:
If using the OmniVista 8770 application, ensure your version is at least R.2.0.07.01.d.
In an existing OmniPCX Enterprise database, SIP Extension users may already be declared in the
Communication Server database. An initial synchronization of OmniVista 8770 and OmniPCX
Enterprise databases is mandatory for these users to be registered in the in OmniVista 8770 database.
If they are not registered, they cannot be configured in the Users application nor associated to 8012
Deskphones.
4.2.3.1.2 Commissioning overview
An installation of 8012 Deskphone sets, using the OmniVista 8770 (as of R2.0) consists in:
1. Ensuring SIP attributes are configured on the OmniPCX Enterprise, see: Preliminary SIP
configuration on the OmniPCX Enterprise on page 239, namely:
a. Ensuring a DHCP server is configured, see: DHCP configuration example on page 239
b. Verifying the software lock dedicated to SIP service on page 240
c. Configuring SIP set specific parameters on page 240
2. Deploying or updating set binaries on page 242
3. Creating users on page 243
4. Commissioning the set on page 245

4.2.3.2 Preliminary SIP configuration on the OmniPCX Enterprise

• The codec list definition. It is recommended to build the codecs list respecting the following order:
1. The codec corresponding to the PCX compression algorithm (PCX option System > Other
system param. > Compression parameters > Compression type)
2. The G.711 corresponding to the PCX law (PCX option System > Other system param. >
System parameters > Law)
• The phone settings with:
• Voice mail server address (Communication Server IP address) and its directory number
4.2.3.2.1 DHCP configuration example
The recommended DHCP server is the DHCP server of the OmniPCX Enterprise, which must be
configured before the set downloads its files.
To configure the OmniPCX Enterprise DHCP server: An external server, such as the DHCP server of
Windows 2003 may also be used ( see: 8002/8012 Deskphone - Windows 2003 server DHCP
configuration example8002/8012 Deskphone / Windows 2003 server DHCP configuration example).
Configuration consists in entering the IP address of the server in standard option 66. You may enter the
FQDN if the DNS server is specified in the configuration file.
1. In the OmniPCX Enterprise configuration tool, select DHCP Configuration > Classes
2. Verify the class with the following parameters:

Name Enter a name for this class

Vendor ID Enter alcatel.ictouch.0

TFTP Server address Enter the IP address of the OmniVista 8770 server.

Default lease time (mn) Enter 60

Max lease time (mn) Enter 1440

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 239/382

Chapter 4 SIP deskphones

Configuration file Leave this field blank

3. Confirm your entries
4. Select DHCP Configuration > Apply modifications
4.2.3.2.2 Verifying the software lock dedicated to SIP service
The number of SIP sets operating in SEPLOS mode is controlled by the existing 177-SIP set user
software lock. This software lock is dedicated to all SIP devices operating in both SEPLOS and SIP
device modes.
To display the software lock state, enter the spadmin command from the Communication Server
prompt.
4.2.3.2.3 Configuring SIP set specific parameters
Configuring the SIP set specific parameters is a two step process:
1. Assign a phone Class Of Service (COS) to the SIP set. The phone COS used is exclusively
dedicated to SIP service (do not confuse with the phone COS that apply to all PCX sets and which
are defined in Classes of service > Phone feature COS).
a. Select: Users > SIP Extension Parameters
b. Review/modify the following attributes:

Directory number Enter the directory number of the selected SIP set

Phone COS Select a phone COS number between 0 to 31. Up to 32

phone COS are available
Default value: 0
c. Confirm your entry
2. In the phone class of service, configure the SIP set parameters:
a. Select: SIP Extension > Phone classes of service
b. Review/modify the following attributes:

Phone COS Enter the phone COS number associated to the selec-
ted SIP set

Display UTF-8 Yes: the caller name displayed on the SIP set is the
UTF-8 name
No: the caller name displayed on the SIP set is the
standard name in Latin characters
Default value: No

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 240/382

Chapter 4 SIP deskphones

Display call server information Yes: at SIP set registration or Communication Server
settings update, a message is sent to the SIP set pro-
viding information on Communication Server settings,
such as forward activation. The complete list of Com-
munication Server settings is provided: SIP End Point
Level Of Service - Call Flows Description - Com Server
Information Display
No: no message is sent to the SIP set following the set
registration or when the Communication Server settings
are updated
Default value: yes

Keep-Alive Yes: a keep-alive dialog (i.e. periodic exchange of mes-

sages) is established between the SIP set and PCX
No: no keep-alive dialog is established between the SIP
set and PCX
Default value: No

Send NOTIFY instead of MESSAGE Select Yes for sets which can parse the NOTIFY mes-
sage.
Select No for sets which cannot parse the NOTIFY
message with event user-profile.
For more information about this parameter, see SIP End
Point Level Of Service - Detailed description - Phone
Features Provided by Dialing a Prefix and SIP End
Point Level Of Service - Call Flows Description - Call
Type Identification
c. Confirm your entries
Additional parameters must be configured when the Keep_Alive parameter is set to yes.
1. Select: IP > IP Quality of Service COS
2. Review/modify the following attributes:

IP QoS COS Select the desired IP Quality of Service COS. This COS
must correspond to the COS defined in the IP domain of
the set

SIP Lost This delay added to the SIP Keep Alive timer (configured
below) is used to define when a SIP set is considered out
of service (absence of keep-alive dialog). When the SIP
set does not send an OPTION request before the timer
elapses (sum of SIP Keep Alive timer and SIP Lost de-
lay), the SIP set is seen as out of service
Default value: 5 (in seconds)

SIP Keep Alive Enter the time interval expected between two OPTION re-
quests from the SIP set
Default value: 30 (in seconds)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 241/382

Chapter 4 SIP deskphones

3. Confirm your entries

4.2.3.2.4 Configuring the value of dynamic payload type for DTMF
For DTMF sending method: select the Out of Band method (RFC 4733) and in-band (SIP INFO is
supported).
1. Select: SIP > SIP Gateway
2. Review/modify the following attribute:

Dynamic Payload Type for DTMF Enter a number between 96 and 127
This value is suggested by the PCX for outgoing calls
"negotiation value".
Default value: 97
3. Confirm your entry

4.2.3.3 Deploying or updating set binaries

4.2.3.3.1 Deploying the set binary file
Caution:
This section is applicable only to deploy a new software on the sets. Skip this section in case of addition
of sets with no need of upgrading the software.
Deploying the set binaries consists in making them available for download on the OmniVista 8770
server.
4.2.3.3.1.1 Adding the set binaries
1. Download the firmware binary zip file from the Enterprise Business Portal
Note:
The name given to the firmware binary zip file must follow a naming rule.
2. Save the firmware binary zip file on the OmniVista 8770 server
3. From the Devices application, click the Deployment Package tab
4. Expand the tree to the node to which sets are attached
5. If a package has already been created, select this package
6. If no package is associated to 8002/8012 My IC Phone:
•
Right click 8002/8012 My IC Phone and select Add Package
•
In the Deployment Package window, enter the deployment package name in the Application
name field
7. Double click the Tel. Application file line
A browser window opens.
8. Select the firmware binary zip file you downloaded and click OK
9. Click the Devices line and click the selection button
A search window opens.
10.Click the Magnify icon to display the list of devices and select the devices to which the package
must be applied, then click OK
11.Click the validate icon to save your modifications
4.2.3.3.1.2 Deploying a new set binary file
To deploy the software:
1. From the Devices application, click the Deployment Package tab
2. Expand the tree structure to display the package to deploy
3. Right click the package to deploy and select Deploy Package

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 242/382

Chapter 4 SIP deskphones

The Task Type window opens

4. Select Simple job
A scheduler window opens.
5. Leave values unchanged to deploy immediately, or schedule the exact time and date to deploy and
click OK
Note:
The set binary deployment can be verified from the Scheduler application: select the corresponding task and
select the Status tab to the right of the window.
4.2.3.3.2 Updating binaries
To update SIP binaries on a set, SIP binaries must be made available on the download server
(bin8012, app8012 and dat8012), and the set must reset. This can be done in the following ways:
• Manually by disconnecting the set and plugging it in again
• Automatically after a polling timer defined in the configuration file (field Binary polling timer)
registered in the set at first initialization. The set monitors the server to check if new binary files are
available. When there are new binary files, the set automatically restarts and proceeds with a binary
update.

4.2.3.4 Creating users

4.2.3.4.1 Creating users as SIP extension
Before configuring the set, the user must be declared as SIP extension in the Users application of the
OmniVista 8770:
1. From the Users application, click the Users tab
2. Access the contextual menu and select Create user
3. In the Common Attributes frame, complete the following fields:

User type Select OXE

Last name Enter the last name of the user to create

User ID Enter the user ID of the user to create

A new frame appears in the properties area to configure user parameters

4. To enter manually the OmniPCX Enterprise parameters, leave the OXE Meta-Profile field blank and
complete the following fields:

OXE ID Click and use the browser to select the desired OmniPCX Enterprise

OXE directory num- Enter the user directory number

ber

Device Type Click and use the drop-down menu to select SIP extension
5. Click the validate icon to save your modifications
The user is declared in the database of the OmniVista 8770 and the corresponding OmniPCX
Enterprise
4.2.3.4.2 Configuring Hotel specificities
All the declared users, including guests in check-in state associated to real customer names are loaded
in the OmniVista 8770 database. In the OmniVista 8770 database, these users appear with the real

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 243/382

Chapter 4 SIP deskphones

name of the guest. At check-out, the association between a 8012 Deskphone and the guest profile is
removed, but the guest entry remains in the OmniVista 8770 database and must be removed manually.
After the initial synchronization of databases, the automatic creation of the users in the Users
application must be disabled. This is necessary to prevent guest users from being created in the
OmniVista 8770 database any time a check-in is performed.
After the initial synchronization of databases, it is recommended to use the OmniVista 8770 Users
application for the creation of new OmniVista 8770 users as detailed below.
When using the Users application, the new user is created at the same time in the two databases:
OmniVista 8770 and OmniPCX Enterprise.
Because all user parameters from the Communication Server are not available in the Users application,
it is mandatory to create a hotel profile on the Communication Server and associate it to the User in the
Users application at user creation.
To create this hotel profile, create a new user on the Communication server as follows:
1. Go to an OmniPCX Enterprise configuration tool and select Users
2. Create a new user, making sure that the following attributes are set with the indicated values:

Set Function Select: Profile

Profile Name Enter a string of characters made of capital let-

ters and/or numbers, excluding any special char-
acter

Hotel-Set Operation Select: Room

Use Type Of Dir. No. Select: Multi occupancy if your configuration in-
cludes this feature

After the next database synchronization, this profile will be downloaded by the Users application
and displayed in the list of OmniPCX Enterprise profiles

4.2.3.5 Creating and associating a set to a user

Set configuration for a user consists in creating and associating a set to a user from the OmniVista
8770 application. This operation automatically creates a configuration file, required for set
commissioning, on the OmniVista 8770 server.
1. From the OmniVista 8770 Users application, click the Users tab
2. Expand the tree structure and select the user to which the set must be associated
3. Access the contextual menu and select Associate SIP device > New
4. Select the appropriate set type in the device list
5. In the General tab, review/modify the following attributes:
• Device identity (or MAC address):
If the device is deployed with its MAC address, enter the set MAC address. The MAC address
can be entered with or without the colon separator
If the device is deployed with its directory number, leave this attribute blank and complete the
Identification key and Identification password attributes
6. In the Network tab:
• Configure DNS address(es)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 244/382

Chapter 4 SIP deskphones

• In an OmniPCX Enterprise in duplicated configuration where the two Communication Servers are
on two different subnetworks (spatial redundancy), enter the second Communication Server
address in Secondary Sip Server > Server address
• Enter the SNTP Server address
7. In the Telephony tab:
• In the Message waiting indication URI field, enter the main role IP address(es) of the
Communication Server to subscribe the set to voice mail notifications.
Note:
• In a local redundancy configuration, enter the single main role IP address.
• In a spatial redundancy configuration, enter both main role IP Addresses, separated by semicolon “ ;”
• Fill in prefixes as defined on the OmniPCX Enterprise
8. In the Advanced tab:
• Verify the attributes config polling timer (default 60) and binary config timer (default 480s)
• Enter the Admin password: this password is used to access administration settings on the set.
The password configured here replaces the password on the set after configuration files are
downloaded
• Validate the option Telnet for remote connection
Note:
It is possible to authorize telnet connections later but the set only recovers the change of configuration of
this setting after the next polling of the configuration files, which depends on the Config Update Polling
timer value (one day by default).
• If desired, enable the option: PC port on 8012
9. Click the validate icon to save your modifications
The new set is created in the corresponding OmniPCX Enterprise and associated to the
corresponding user. This set is displayed below the user in the tree structure of Users application

4.2.3.6 Commissioning the set

4.2.3.6.1 Selecting the download mode: static or dynamic
Network parameters can be configured:
• Dynamically through DHCP: see Commissioning the set in dynamic mode on page 245
See: DHCP configuration example on page 239
• Statically on the set: see Commissioning the set in static mode on page 246
By default the set starts in dynamic mode. You can use the set administration menu to check and/or
modify the initialization mode.
To access the administration menu: if the set is not started:
1. Connect the set to the LAN and power supply
2. During set initialization (steps 2/5 to 5/5) , press the *, then # keys
If the set password is required, enter digits of the set password and press OK
The set administration menu is displayed.
If the set is started:
1. Go to the Settings > Admin Settings menu
2. Enter digits of the set password and press OK
4.2.3.6.2 Commissioning the set in dynamic mode
By default (factory settings), the set automatically starts in dynamic mode without any configuration on
the set.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 245/382

Chapter 4 SIP deskphones

If you wish to check the initialization mode (or switch it from static to dynamic):
1. Open the set administration menu (see: Selecting the download mode: static or dynamic on page
245)
2. From the set administration menu, scroll up/down to display IP parameters and press OK
3. Scroll up/down to display IP mode: xxxx
The available initialization modes are:
• Static: the IP parameters to use are manually configured on the set
• Dynamic (default option): IP parameters are acquired from a DHCP server
• Alcatel Dyn: IP parameters are acquired from a DHCP server delivered by ALE International
4. If necessary, press successively OK to change the initialization mode in Dynamic or Alcatel Dyn
5. Press OK to apply change
6. Scroll up/down to display Save and press OK
4.2.3.6.3 Commissioning the set in static mode
4.2.3.6.3.1 Selecting the Set Initialization Mode (Static)
By default, a set is configured to initialize in dynamic mode.
To modify the initialization mode:
1. Open the set administration menu (see: Selecting the download mode: static or dynamic on page
245)
2. From the set administration menu, scroll up/down to display IP parameters and press OK
3. Scroll up/down to display IP mode: xxxx
The available initialization modes are: Dynamic (default option), Alcatel Dyn or Static
If the desired mode is displayed, you can skip IP mode selection
4. If Dynamic is displayed, press successively OK to change the initialization mode in Static
5. Scroll up/down to display Save and press OK
4.2.3.6.3.2 Configuring the set IP parameters
1. Open the set administration menu (see: Selecting the download mode: static or dynamic on page
245)
2. From the set administration menu, scroll up/down to display IP Parameters and press OK.
3. Scroll up/down to display and modify set IP parameters:
• IP @: Set IP address
• Subnet: IP subnetwork mask
• Router: Router IP address
4. If VLAN is used and is not provisioned via AVA:
• Scroll up/down to display Use VLAN
• Press OK to enable Use VLAN
• Press OK to configure the VLAN ID (use the phone keypad to enter digits and the C key to
delete digits)
• Press the up or down key to go back to the IP Parameters menu
5. Scroll up/down to display Save and press OK
4.2.3.6.3.3 Configuring the Device Management parameters
1. Open the set administration menu (see: Selecting the download mode: static or dynamic on page
245)
2. From the set administration menu, scroll up/down to display IP parameters and press OK
3. Scroll up/down to display and configure the Device Management parameters (OpenTouch server) :

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 246/382

Chapter 4 SIP deskphones

• DL Scheme: press several times the OK button to specify the transfer mode: HTTPS or HTTP
• Use Default Port: click the OK button to confirm that the default port value (443) is retained for
HTTPS
• DL Addr: press the OK button and enter IP address of the OmniVista 8770 server
• DL Port: parameter not used
• DL Path: press the OK button and enter the access path where the set binary and configuration
files are located (/DM/dmictouch)
4. After the DL Path parameter, scroll up/down to display Save and press OK
4.2.3.6.4 Verifying and modifying download parameters
1. Open the set administration menu (see: Selecting the download mode: static or dynamic on page
245)
2. From the set administration menu, scroll up/down to display IP Parameters and press OK
3. Scroll up/down to display and modify download parameters of the set binary and configuration files
(OpenTouch server):
• DL Scheme: set to HTTPS
• Use Default Port: parameter activated
• DL Addr: set to the IP address of an OpenTouch server
• DL Port: parameter not used
• DL Path: access path where the set binary and configuration files are located (/DM/
dmictouch)
Note:
Use the OK button to enter in edit mode.
4. After the DL Path parameter, scroll down and select Save to apply changes
Note:
From the set administration menu, scroll up/down to display Soft Infos and press OK to display the version.

4.2.4 Resetting sets to factory settings

4.2.4.1 Overview
The reset to factory is intended to cope with situations in which the administrator can no longer access
the set configuration because the set administrator password has been lost, and the set is configured
in static mode or uses a specific VLAN on the previous installation. Reset to factory is not needed
when a set is configured in dynamic mode: in this case, the set administrator password can be
changed through the OpenTouch configuration window of OmniVista 8770, by modifying the password
for SSH in the advanced parameters of the target set.
The reset to factory enables to restore the set to the “Out of the box” initial status, except that the
software version remains unchanged on the set. It works during the set initialization. If initialization is
done, there is no other solution to reset sets to their factory settings.
The reset to factory performs the following actions:
• Restore the set administrator password to its default value
• Clean all user personal data
• Restore the configuration and settings to their default values
• Remove certificate data such as customer certificates and CTL, except ALE International default
certificate stored during manufacturing
• Store a message into defense log to indicate a reset to factory has been done
• Reboot the set
By using the reset to factory, there is no need to return sets for repair.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 247/382

Chapter 4 SIP deskphones

Note:
Although the feature is not intended for end-users, it is available in user mode, as this feature is used when the set
administrator password has been lost, and therefore the administrator mode cannot be reached.

4.2.4.2 Restoring the set to factory settings

To perform the reset to factory on a set:
1. Restart the set
2. During set initialization (steps 2/5 to 5/5) , press the *, then # keys
The message Password: is displayed on screen
3. Enter the administrator password required for the reset to factory
The default administrator password is *8000#.
The message Reset to factory is displayed on screen
4. Press OK to validate the reset to factory, or press C to cancel the reset
A confirmation message is displayed on screen
5. Press OK to confirm the reset to factory
The set restarts immediately and the reset to factory is performed

4.2.5 8012 list of features

4.2.5.1 List of 8002/8012 Deskphone features
4.2.5.1.1 Hardware

Feature description Comments

Display Black and white: one line of twenty characters.

Fixed viewing angle at 50°.
To set up the 50° angle on a new set out of the box: pull the foot stand with a
significant force until a noise indicates the set has reached its position.

External audio jack Connection of a audio headset. The headset is automatically detected when
connector 3.5mm connected to the jack connector.

2-port Ethernet (8012) 8002 : Ethernet 10/100 Mbps connection to the LAN (LAN port)
1-port Ethernet (8002) 8012 : Ethernet 10/100/1000 Mbps for connection to the LAN (LAN port) and
Ethernet 10/100/1000 Mbps for connection to a PC (PC port)
The LAN port is PoE 802.3af compliant.
The 8002 Deskphone is Class 1 PD (Powered Device consuming not more
than 3.84 W).
8012 Deskphone is Class 2 PD (Powered Device consuming not more than
6.49 W).

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 248/382

Chapter 4 SIP deskphones

4.2.5.1.2 Accessories

Feature description Comments

Power injector over Powering of the terminal via the Ethernet link in case the Ethernet switch,
Ethernet interface connected to a 8002/8012 Deskphone does not provide PoE.

Power jack adaptor Powering of the terminal in via a power jack, in case the Ethernet switch, con-
nected to a 8002/8012 Deskphone does not provide PoE and no power injec-
tor is used.

Headsets Use a headset approved by ALE International

Display Black and white: one line of twenty characters.

Fixed viewing angle at 50°.
To set up the 50° angle on a new set out of the box: pull the foot stand with a
significant force until a noise indicates the set has reached its position.

4.2.5.1.3 Protocols

Feature description Comments

Network TCP / IP

802.1 P/Q

Automatic VLAN As- Available for sets belonging to an OpenTouch system only
signment (AVA)

DHCP

SNTP + time zone

management

LLDP / LLDP-MED Compatibility with 802.3af and 802.3az

Quality of Service QoS tags for audio (RTP) and SIP signaling packets:
(QoS)
• Layer 3: Differentiated Services (DiffServ)
• layer 2: IEEE 802.1.p

SIP User Agent

Support of RTP/RTCP

4.2.5.1.4 Security

Feature description Comments

http/https client

User password Provides voice mail access

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 249/382

Chapter 4 SIP deskphones

Feature description Comments

2-port Ethernet switch On 8012 sets, the PC port can be deactivated for security reasons
management

802.1x MD5/TLS Au-

thentication

Certificate download

4.2.5.1.5 Audio

Feature description Comments

Ringing melodies (nor- Several ringing melodies are embedded in the terminal. Selection of the pre-
mal, progressive, ferred melody is performed in the phone settings : Settings > Phone > Ring-
beep) ing

Handset mode Narrowband codecs (300Hz – 3400Hz) :

• G711 (64kbit/s): A law and μ law
Headset mode
• G729 Annex A and B
Handsfree mode

Muting the micro- Available for all audio modes (handset, handsfree, headset)
phone

Tone management Dial tone, ringback tone, busy tone, call waiting tone, call hold tone
Configuration available from the set and from the OmniVista 8770

DTMF / feedback tone

management

Hearing aids compati-

bility

Hearing aids compati-

bility

Audio volume man- Volume -/+ for all audio modes (handset, handsfree, headset)
agement

4.2.5.1.6 Telephony
The following features are available, provided the set user was granted rights to use them.

Feature description Comments

Manual dialing

Make Call

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 250/382

Chapter 4 SIP deskphones

Feature description Comments

Call Transfer

Receive Call

Receive Call (auto-an-

swer)

Call Forwarding (Rout-

ing)

Reject Call The set stops ringing. The call is released at calling party's end

Call Deflection

Call Hold / Resume

Consultation Call
(make a second call,
while in conversation)

Conference Call (lo-

cal, with 3 parties in
all)

Redial from the Call

Log

Busy Call A set can manage two lines simultaneously, at the most

Call failure notification

management

Phone state notifica- Displayed on phone screen (one line of twenty characters)
tion

Voice mail (consulta-

tion with DTMF, de-
posit, notification)

CLIR (Caller ID Hid- Activate or deactivate CLIR in the phone settings : Settings > Phone > ID
den) hidden > Activate/Deactivate

Multiline and Broker A set can manage two lines simultaneously, at the most
Call (toggle between
two calls)

Automatic Answer Applies to internal and external calls

This feature is activated by pressing the “Mute” key when the phone is in idle
(not in a communication).

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 251/382

Chapter 4 SIP deskphones

4.2.5.1.7 High availability

Feature description Comments

Survivability Available for OpenTouch only

4.2.5.1.8 Serviceability

Feature description Comments

Provisioning from the

OmniVista 8770

Telnet Used to access logs and troubleshooting commands

Migration Do not migrate a terminal from a communication server to another communi-

cation server without a flash reset

Device auto-discovery When the end user first connects the device, he/she is asked to manually en-
(OpenTouch) ter login information. Then the DM server automatically creates DM configu-
ration files for the device according to login information, and links the device
phone number to the hardware (MAC) device.

4.2.5.1.9 Applications

Feature description Comments

Local directory The maximum number of Contacts is 100. They are entered by the set users.
External numbers must include the trunk prefix (trunk line access code)

Call Log (Call history) Three types of calls are recorded: incoming calls, outgoing calls, missed calls
Restriction: only the called/calling number is stored, not the name.

Auto-answer / receive Click to answer

third party call for re-
When a user receives a call, her/his set rings and displays the call. An “an-
mote control by soft-
swer call” button appears on the OTC client. The user clicks this button to an-
phone (OpenTouch
swer the call and the8002/8012 Deskphone takes the call
only)

Phone Settings Available from the menu: Settings > Phone

Admin Settings Available from the menu: Settings > Admin settings (the password must be
entered)

User Interface (GUI) Available in 22 languages, see: Available languages on page 253
The Admin settings menu is in English only

Documentation (User Available in pdf format in 29 languages, see: Available languages on page
Manual and User 253
Guide)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 252/382

Chapter 4 SIP deskphones

4.2.5.1.10 Available languages

US English FR French

ES Spanish IT Italian

TR Turkish NL Dutch

NV Norwegian SU Swedish

EL Greek DE German

SL Slovenian PT Portuguese

LT Lithanian HU Hungarian

CS Czech DK Danish

FI Finnish PL Polish

LV Latvian IS Icelandic

4.2.6 Troubleshooting
4.2.6.1 Troubleshooting
The following paragraphs describe:
• Error and information messages on page 253
• Ethernet link on page 255
4.2.6.1.1 Error and information messages
In the following table:
• Short text stands for the text displayed on screen, whether as error or information message
• Description stands for status and/or error description

Short text Description

END Starting phase terminated (successful or unsuccess-

ful)

STARTED Step started

SUCCESS Step successful

FAIL Step failed

RETRYING Retrying step

NO MAC ADDRESS No Ethernet MAC address stored in flash

DHCP NOT RESPONDING Server not responding

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 253/382

Chapter 4 SIP deskphones

Short text Description

BAD IP ADDRESS Incorrect IP address

BAD ROUTER ADDRESS Incorrect router address

ROUTER PING FAILED Router not responding to ping

BAD TFTP ADDRESS Incorrect TFTP server address

ADDRESSES MISMATCH Address, mask and router do not match

TFTP NOT RESPONDING TFTP server not responding

TFTP SERVER ERROR TFTP server error

BAD FILE CONTENT Error found in downloaded file

FILE TOO LARGE File too large (cannot be downloaded)

SAME VERSION FOUND Retrieved version same as running version

NEW VERSION FOUND New IP Touch software version found

(download)

FLASHING SUCCESS Flashing successful

FLASHING FAILED Failed to flash downloaded binary

TRYING ANOTHER CPU Trying next address from configuration file

NO ETHERNET LINK Ethernet link not connected (LAN port only)

RESOURCES NOT FOUND Resources file not found in flash

DOWNLOAD FORCED Download was forced because resources are missing

NOT COMPATIBLE Downloaded version not compatible with the terminal

hardware

initializing First text message after hardware reset and copyright

information

1/5 network start Phase 1 is running: the set is starting its network in-
terface

2/5 network setup Phase 2 is running: the set is looking for IP informa-
tion

(addresses)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 254/382

Chapter 4 SIP deskphones

Short text Description

3/5 config download Phase 3 is running: the set is trying to get a lanpbx
file

4/5 binary download Phase 4 is running: the set is downloading a new bi-
nary

5/5 connecting Phase 5 is running: the set is trying to set up the sig-
naling link with the system

802.1x Auth Failed 802.1x authentication has failed: RADIUS server is

unreachable, access is refused to the terminal on the
RADIUS server or the terminal has an incorrect iden-
tity (bad login and/or password).

802.1x Auth Success 802.1x authentication process is complete. The RA-

DIUS server grants access to the terminal, the au-
thenticator opens its port.

4.2.6.1.2 Ethernet link

By default, the 8012 phone is configured to perform auto-negotiation on the two ports (LAN and PC).
Provided that the PC and the LAN switch are also configured to perform auto- negotiation, this is the
best configuration for QoS improvement.
However, depending on network configuration, it may not always be possible to leave the terminal in
auto-negotiation: link speed and duplex of both ports can be forced to specified values using the
supervisor menu:
1. Plug the set in
2. Once the set displays initialization, press the i key, then the # key or enter the administration
settings while the phone is in idle status
3. Use the navigation key to select Ethernet Links
4. Modify data as requested
A configuration mismatch between the terminal and PC/LAN switch can lead to nasty effects on voice
quality (see: Table 1):
• No link (or speed mismatch): 8, 9, 11 and 12
• Packet loss (or duplex mismatch): 2, 4, 7 and 14
Note:
Collisions are not detected by the device operating in full-duplex mode: packets from this device are never
retransmitted in case of a collision.
The following table lists all possible Ethernet port configuration combinations when connecting an IP
Touch set to an external device (switch on LAN side, PC on PC side). For each combination, the table
shows the link status: valid or invalid (duplex or speed mismatch), as described above.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 255/382

Chapter 4 SIP deskphones

table 4.3: Ethernet link combinations

Terminal Port External Device Port Link Status

1 auto-negotiation auto-negotiation Valid

2 auto-negotiation 100-FULL Invalid (packet loss)

3 auto-negotiation 100-HALF Valid

4 auto-negotiation 10-FULL Invalid (packet loss)

5 auto-negotiation 10-HALF Valid

6 100-FULL 100-FULL Valid

7 100-FULL 100-FULL Invalid (packet loss)

8 100-FULL 10-FULL Invalid (no link)

9 100-FULL 10-HALF Invalid (no link)

10 100-HALF 100-HALF Valid

11 100-HALF 10-FULL Invalid (no link)

12 100-HALF 10-HALF Invalid (no link)

13 10-FULL 10-FULL Valid

14 10-FULL 10-HALF Invalid (packet loss)

15 10-HALF 10-HALF Valid

Note:
To prevent slowness problem on the PC when the two ports of the 8012 phone are configured in auto-negotiation
mode, if the negotiation has led to a 10 Mbps rate on the PC port and a 100 Mbps rate on the LAN port, the set
automatically tries to renegotiate a 10 Mbps rate on the LAN port.

4.3 8082 My IC Phone/8088 Smart DeskPhone (SIP deskphones)

4.3.1 Overview
8082 My IC Phone and 8088 Smart DeskPhone sets can be configured on the OmniPCX Enterprise as
hotel sets. In hotel mode, these sets are very similar in their features and capabilities.
The 8082 My IC Phone sets can also be configured as business sets, in which case, they operate in
NOE mode and emulate Alcatel-Lucent IP Touch 4068 Phone sets.
As of R11.2, 8088 Smart DeskPhone sets can be configured as SIP devices with basic audio and video
capabilities. They can operate as video SIP device in a meeting or conference room.
This chapter is intended for people in charge of installing and commissioning:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 256/382

Chapter 4 SIP deskphones

• 8082 My IC Phone and 8088 Smart DeskPhone as hotel sets

• 8088 Smart DeskPhone as video SIP devices
For 8082 My IC Phone configuration as business sets, refer to: OT Connection for 8082 on page 377
This chapter provides:
• An overview of the sets in their hardware specifications, as well as details on the set ergonomics
• The commissioning procedure, including DHCP configuration for dynamic initialization, local
network configuration for static initialization, set configuration using either OmniVista 8770 or 8088
Web Management, Bluetooth® pairing
Note:
In the following paragraphs all mentions to 8088 Smart DeskPhone apply to 8082 My IC Phone sets, unless
specified otherwise.

4.3.2 Set ergonomics

4.3.2.1 Set description
Contextual Sensitive
Touch Screen

Bluetooth
Handset

Microphone Quick Loudspeaker

Access Pad

Figure 4.5: 8088 Smart DeskPhone set layout

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 257/382

Chapter 4 SIP deskphones

HDMI connector PC port LAN port

USB connectors Power connector

Additional key
module connector RJ9, handset connector

Figure 4.6: 8088 Smart DeskPhone set connectors

Contextual Sensitive
Touch Screen

Bluetooth
Handset Quick Loudspeaker
Access Pad
Microphones

Figure 4.7: 8082 My IC Phone set layout

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 258/382

Chapter 4 SIP deskphones

Power connector
Alphabetic keyboard connector (VHE-2 only)
PC connector Handset connector
USB connectors
LAN
connector
Additional key module
connector

Headset jack

Figure 4.8: 8082 My IC Phone set connectors

4.3.2.2 Set equipment

The 8082 My IC Phone/8088 Smart DeskPhone set includes the following items:
• Corded comfort handset or Bluetooth® Handset with a front LED
• Hands-free station speaker
• A quick access pad (which includes LEDs)
• A set screen, which is adjustable from the typical angle of 60° relative to the table surface, to a near
horizontal position
• Embedded video camera (8088 Smart DeskPhone only)
Note:
8082 My IC Phone has no embedded video camera. Video is available on VHE-2 sets (8082 My IC Phone
second generation) via a USB camera. VHE-1 (8082 My IC Phone first generation) does not support video.

4.3.2.3 Set features

The 8082 My IC Phone/8088 Smart DeskPhone set fully operates with:
• SIP basic telephony
• Local applications with a focus on communication
• Openness to other applications (SDK)
Note:
No SDK is delivered for 8088 Smart DeskPhone.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 259/382

Chapter 4 SIP deskphones

Standard and typical telephone features, such as call transfer or call forwarding are included. Contacts
can be managed from the set, which includes indications of presence as well as instant messaging, or
access to external applications. Generally speaking, 8088 Smart DeskPhone sets make all the
advanced features offered by OmniPCX Enterprise systems easy to access and implement.
Note:
For 8088 Smart DeskPhone operating as video SIP device, see: Available features on page 274.

4.3.3 Generalities on set initialization

4.3.3.1 Initialization process overview
The initialization process consists of the following steps:
• Step 1: Kernel initialization
• Step 2: Network initialization and setup
• Step 3: Configuration file download
• Step 4: Software upgrade
• Step 5: Application launch
• Step 6: User interface launch
A digit indicating initialization progress is displayed on the set screen.
The initialization process without software upgrade takes several minutes.
The initialization process with software upgrade can take up to 40 minutes and involves several
consecutive startups of the set.
4.3.3.1.1 Step 1: Kernel initialization
At the end of the boot process, the Linux kernel starts running. It calls the startup functions of all
defined kernel components.
4.3.3.1.2 Step 2: network initialization and setup
The network initialization consists of:
1. Ethernet Interface initialization: the speed and duplex are set by default to auto-negotiation.
Different values can be configured through MMI.
2. If enabled on the terminal, 802.1X authentication (for more information, refer to the document [7])
3. LLDP/LLDP-MED protocol initialization
4. If the terminal is configured in dynamic mode (default value), DHCP initialization.
Note:
If the DHCP initialization fails, the terminal falls in survivability mode.
During step 2 and step 3 a settings button is available on the set screen. Touch this button to modify
configuration and network parameters.
4.3.3.1.3 Step 3: configuration file download
Configurations files are downloaded from the OmniVista 8770 server, using the HTTPS protocol.
They consist in a collection of settings. Settings are variables used by the terminal software. They are
mainly defined by a name (id), a type (BOOLEAN, NUMERIC, STRING, other), a value and a default
value.
Settings are provisioned during the initialization of the terminal by downloading two or three
configuration files (XML format).
The first two files are created by the OmniVista 8770 application.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 260/382

Chapter 4 SIP deskphones

The first file: config.<MAC>.xml is device oriented. If this file fails to download after three attempts,
the terminal resets and enters survivability mode.
The second file: <Directory_number>@<server_FQDN>.xml relates to SIP configuration. It is user
oriented and downloaded immediately after the config.<MAC>.xml file.
As an option, if referenced in the config.<MAC>.xml file, a third file, consisting in customization
settings is downloaded. See: Set customization on page 310.

2 1

config.<MA sipdata.<M
C>.xml AC>.xml

User data Device config.

Customization

Customization file

Figure 4.9: Configuration file download

4.3.3.1.4 Step 4: software download

Step 4 consists in downloading the software delivery.
A software delivery is composed of the release modules and, in option, additional application modules.
Each software module contains a key file, an index file and several RPM files packed into a zip archive.
The software delivery must be deployed on the OmniVista 8770 server, which generates a root index
file containing:
• The component of the release module: its name, its version, the URL of the release index file and
associated checksum
• One component per application module added: its name, its version, the URL of the application
index file, and associated checksum
• Possibly, other data as UUIDs or version IDs
Software download is performed as follows:
1. The terminal checks if a software version is available: if no software version is available, the
terminal jumps to Step 5: application start on page 262
2. If a software version is available, the terminal downloads the root index file using the URL given in
the config.<MAC>.xml file.
3. If the profile identifier contained in the file is different from the one of the installed version, the
terminal enters the download process, if not, it jumps to Step 5: application start on page 262.
4. The terminal downloads new RPMs via HTTP
5. The terminal checks signatures
Note:
If a signature is bad or missing, the terminal does not install the package and the upgrade process is aborted.
The terminal resets.
6. The terminal installs new packages and removes useless packages
7. At the end of the process, the terminal resets to take into account the new version and, if necessary,
installs external packages or web applications.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 261/382

Chapter 4 SIP deskphones

4.3.3.1.5 Step 5: application start

Applications and services are launched.
If needed, you can access the Settings menus to bind the Bluetooth® handset during this initialization
step.
Note:
Bluetooth® handset pairing can only be performed during this initialization step. Bluetooth® handset pairing cannot
be carried out via MMI once the set has initialized.
If needed, the firmware upgrade of the Bluetooth® handset takes place during this initialization step. Do
not hook off the handset during the firmware upgrade.
4.3.3.1.6 Step 6: user interface launch
The set enters into service and the user interface is available.

4.3.4 Generalities on configuration parameters

Configuration parameters can be provided to the terminal in various ways:
• Locally on the set
• Through LLDP
• Through DHCP
• Through xml configuration files downloaded via HTTP from the OmniVista 8770 server at
initialization
The settings configured locally have a lower priority than the ones received from the OmniVista 8770
server, which in turn have a lower priority than the settings received through DHCP or LLDP.
Note:
The settings modified locally by users can have a higher priority than the ones received from the OmniVista 8770
server. This occurs when the settings received from the OmniVista 8770 server have their override field set to
false.

4.3.4.1 Local configuration (static initialization)

MMI allows to access and configure the following parameters, using the admin account:
• In the Network menu:
• DM (OmniVista 8770 server) URL
• DNS addresses
• Ethernet parameters: the LAN and PC Ethernet interfaces are by default configured in auto-
negotiation mode
• IP parameters
• Log parameters, allowing to define a syslog server for log reception
• Network parameters, allowing to:
• Enable and configure a DHCP User Class: this makes the set send the standard DHCP
option 77 (User Class, RFC2132) within the DISCOVER and REQUEST DHCP messages.
Using this option allows to define groups of terminals, and to attach these groups to different
and independent Communication Servers.
• Define an SNTP Server address and refresh period
• Proxy host and port
• SIP parameters (read only)
• In Security menu:
• 802.1x parameters
• Certificates: only used for the CTL signing process

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 262/382

Chapter 4 SIP deskphones

MMI can be accessed:

• During initialization step 2 and 3: this allows to configure network parameters
• During initialization step 5: this allows to bind the Bluetooth® handset
• After the set has initialized

4.3.4.2 DHCP configuration (dynamic initialization)

Two types of dynamic initialization are available:
• Dynamic (default value): the set selects in priority DHCP offers, with a Vendor Specific option
corresponding to a server from ALE International.
• Dynamic Alcatel: the set accepts only DHCP offers with a Vendor Specific option corresponding to
a server from ALE International (alcatel.int-ip.0, alcatel.a4400.0, alcatel.a4200.0).
When initializing in dynamic mode, the set provides the following information in the DHCP Discover
message
• Option 60: (vendor class identifier): alcatel.ictouch.0
• Option 55: list of requested options: subnet mask, router option, broadcast address, option 43
vendor specific info, server ID, renewal time, rebinding time and vendor class ID
Option 43 is vendor specific information, meaning that this option is defined for a specific client vendor
ID. In the DHCP offer, the data within Option 43 corresponds to the client vendor ID specified in the
request.
The DHCP offer provides the following parameters:
• IP address
• Option 1: subnet mask
• Option 3: router IP address
• Option 66: IP address or name of the OmniVista 8770 server, for example 192.168.12.34
Note:
When the OmniPCX Enterprise DHCP is used, Option 66 is replaced by the Next Server option.
Note:
The set uses the following URL to download files: https://[value of option 66]/dmictouch/

Optionally, the DHCP offer can include the following parameters, which can also be configured locally
on the terminal or on the OmniVista 8770 server:
• Option 6: Domain Name Server (DNS primary and secondary)
• Option 15: Domain name
• Option 42: SNTP server
• Option 43 with suboption 58: VLAN ID provided with AVA mode

4.3.4.3 Configuration on OmniVista 8770

The OmniVista 8770 application provides the interface to configure the device.
The configuration files consist of the following xml files:
• config.<MAC>.xml (referred to as config file in the rest of the document) where <MAC> is the
physical address of the set in hexadecimal without colons
As an example, if the terminal’s MAC address is 00:80:9F:56:07:AE, the config file name is
config.00809f5607ae.xml
• <Directory_number>@<server_FQDN>.xml
• As an option, a customization file

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 263/382

Chapter 4 SIP deskphones

The config.<MAC>.xml and <Directory_number>@<server_FQDN>.xml files are created via

the OmniVista 8770.
The customization file is created via the Smart Custo (8088 Smart DeskPhone) or My IC Phone
Customizer (8082 My IC Phone) application. For more information on customization, see Set
customization on page 310.
Configuration files are downloaded at initialization step 3 from the OmniVista 8770 server.
The URL used to download the config file is:
• The URL retrieved from the DHCP offer: the DM URL is constructed using option 66 received in the
DHCP offer (dynamic initialization), or
• The URL configured locally (static initialization)

4.3.5 DHCP server configuration examples

4.3.5.1 OmniPCX Enterprise DHCP configuration
To configure the OmniPCX Enterprise DHCP server:
1. In the OmniPCX Enterprise configuration tool, select DHCP Configuration > Classes
2. Create a new class with the following parameters:

Name Enter MyICPhone

Vendor ID Enter alcatel.ictouch.0

TFTP Server address Enter the IP address of the OmniVista 8770 server

Default lease time (mn) Enter 360

Max lease time (mn) Enter 720

Configuration file Leave this field blank

3. Confirm your entries
4. Select DHCP Configuration > Apply modifications
Caution:
The DHCP server cannot be used simultaneously for the deployment of 8088 Smart DeskPhone sets on
OmniPCX Enterprise nodes and the deployment of 8088 Smart DeskPhone sets on OpenTouch nodes.

4.3.5.2 Windows 2003 DHCP configuration

The following sections describe configuration example with Windows DHCP server. The configuration
consists in:
1. Defining a scope of IP address (not described here)
2. Defining standard parameters, such as subnet mask, router option, broadcast address, renewal
time, rebinding time (not described here)
3. Configuring option 66 on page 265
4. Defining a vendor class for 8088 Smart DeskPhone sets on page 265
5. Activating the scope of IP addresses on page 265
To access Windows DHCP configuration: Start > All Programs > Administrative Tools > DHCP

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 264/382

Chapter 4 SIP deskphones

4.3.5.2.1 Configuring option 66

Note:
As Option 66 is also used for Mobile IPTouch sets to provide the TFTP server address, do not deploy MIPT and
8088 Smart DeskPhone sets on the same scope of addresses
1. In the DHCP configuration window, right click on the scope of IP addresses and select Configure
Options...
2. In the General tab, check the 066 Boot Server Host Name
3. In the String value field, enter the IP address of the OmniVista 8770 server
4. Click OK
4.3.5.2.2 Defining a vendor class for 8088 Smart DeskPhone sets
1. In the DHCP configuration window, right click on the DHCP server name and select Define Vendor
Class
2. Click Add to define a new DHCP Vendor Class
3. Enter a Display name for the Vendor Class, for example 8088 Smart DeskPhone. Enter a
Description.
4. To specify the Vendor Class Identifier string, click the ASCII field and type in alcatel.ictouch.
0.
5. Click OK.
The new vendor class is created.
6. Click Close
4.3.5.2.3 Activating the scope of IP addresses
In the DHCP configuration window, right click Scope Options under the scope of IP addresses and
select Activate

4.3.6 Set configuration and deployment overview

Prerequisites:
• For 8082 My IC Phone in hotel mode, the OmniPCX Enterprise must be R10.0 or higher
• For 8088 Smart DeskPhone in hotel mode, the OmniPCX Enterprise must be R11.1 or higher
• For 8088 Smart DeskPhone in video mode, the OmniPCX Enterprise must be R11.2 or higher
• The OmniPCX Enterprise must be operational
• The OmniVista 8770 must be operational
• For network configuration, any of the following must be implemented:
• A DHCP server must be configured for the sets: see DHCP server configuration examples on
page 264
• A free IP address is available for the set
• If the hardware does not provide a standard power plug, a port with PoE must be available on a
switch. If none is available, a PoE injector or an external power adapter must be used
Configuration and deployment consist in:
1. Configuring the set as hotel set or video SIP device:
• Configuring the 8088 Smart DeskPhone as hotel set on page 266
Caution:
The 8088 Web Management cannot be used to configure a 8088 Smart DeskPhone as hotel set. You
must use the OmniVista 8770.
• Configuring the 8088 Smart DeskPhone as video SIP device on page 273
2. Deploying set binaries on page 295
3. If needed, Deploying a customization file on page 297

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 265/382

Chapter 4 SIP deskphones

4. Commissioning sets on page 298

5. If static initialization is used, when the Settings menu is available, configure network parameters:
see Configuring network parameters through MMI (static configuration) on page 298.
6. At initialization step 5, bind the Bluetooth® handset, if for some reason the handset did not bind
automatically: see Commissioning a Bluetooth handset on page 307.
7. If asked at the end of initialization, enter the Device Key (by default, the directory number) and the
Device password (see Entering device key and password on page 299 for more information on
these parameters).

4.3.7 Configuring the 8088 Smart DeskPhone as hotel set

4.3.7.1 Overview
In a hotel configuration, the 8088 Smart DeskPhone is declared as a user in the OmniVista 8770
database. The OmniVista 8770 generates configuration files. In the Communication Server database
the set is declared as a SIP Extension user.
The set is created either in the Users application of the OmniVista 8770, or in the Communication
Server standard interfaces.
By default, a user created in the Communication Server is not automatically created in the Users
application of the OmniVista 8770. An initial synchronization of the two databases is mandatory.
For this initial step only, authorize user creation in the OmniVista 8770 database during synchronization
of the system.
In an existing database, SIP Extension users can be already declared in the Communication Server
database.
Synchronization:
• Automatically creates the corresponding users in the OmniVista 8770 database
• Makes them accessible from the Users application
• Associates them to 8088 Smart DeskPhone devices
Note:
All the declared users, including guests in a check-in state associated to actual customer names are loaded to the
OmniVista 8770 database. In the OmniVista 8770 database, these users appear with the actual name of the guest.
At checkout; the association between the 8088 Smart DeskPhone device and the guest profile is removed, but the
guest entry remains in the OmniVista 8770 database and must be removed manually.
After initial synchronization of databases, the automatic creation of the Users in the Users application
must be disabled.
Note:
This is necessary to prevent guest users from being created in the OmniVista 8770 database any time a check-in
is performed.
After initial synchronization of databases, use OmniVista 8770 Users application for the creation of new OmniVista
8770 users, as detailed below.
When using the Users application, the new user is created simultaneously in the databases of the OmniVista 8770
and Communication Server.
As all the user parameters of the Communication Server are not available in the Users application, you must
create a hotel profile on the Communication Server and associate it to the user in the Users application at user
creation.
Note:
To create the Hotel profile, create a new user on the Communication Server with the following parameters:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 266/382

Chapter 4 SIP deskphones

• Set Function set to Profile

• Profile Name filled with a name in capital letters or numbers without space nor other special characters.
• Hotel-Set Operation set to Room
• Use Type Of Dir. No. set to Multi occupancy (if used)
After the next synchronization, the profile is downloaded by the Users application and displayed in the list of
OmniPCX Enterprise profiles.
The 8088 Smart DeskPhone configuration as hotel set consists in:
• Declaring the user on page 267
• Creating and associating a set to the user on page 268
• Configuring the general parameters of the set on page 270
• Configuring the set parameters on OmniPCX Enterprise on page 271
Caution:
The 8088 Web Management cannot be used to configure a 8088 Smart DeskPhone as hotel set.

4.3.7.2 Declaring the user

Users can be configured:
• From the Users application of the OmniVista 8770
• From the OmniPCX Enterprise configuration window (access path: Users)
The following paragraph presents the configuration from the Users application.
To create a user:
1. From the Users application, click the Users tab
2. Select a level in the tree structure (for example: country, city, company, department)
3. Access the contextual menu and select Create User

User parameters are displayed in the properties area. Only General tab is displayed. The other tabs
are grayed and are only available after user creation
4. From the Common Attributes frame, complete the following mandatory fields:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 267/382

Chapter 4 SIP deskphones

User type Click and select OXE

Salutation Click and select the user title

Last name Enter the user name

First name Enter the user first name

User ID Modify if necessary identifier displayed for the user

The user identifier is built with the name and first name

A new frame appears in the properties area to configure OmniPCX Enterprise parameters
5. If you want automatic entries for OmniPCX Enterprise parameters, click the OXE Meta-Profile field
and use the drop-down menu to select the corresponding OmniPCX Enterprise meta profile.
OmniPCX Enterprise parameters are completed with the values defined in the selected OmniPCX
Enterprise meta profile. Some parameters can be modified later.
Note:
The OmniPCX Enterprise meta profile can also contain parameters for Connection users with OpenTouch
properties. In this case, the definition of attributes for the applications detailed below can be skipped.
6. If you want to manually enter the OmniPCX Enterprise parameters, leave the OXE Meta-Profile
field blank and complete the following fields:

OXE ID Click and use the browser to select the desired OmniPCX En-
terprise

OXE directory number Enter the directory number of the 8088 Smart DeskPhone set

Device type Click and select SIP extension

OXE profile Click and select the generic Hotel Profile created initially in
the Communication Server database

SIP password Enter the SIP password. Available characters are letters of
the alphabet or digits (six digits minimum).
7. Click the validate icon to save your modifications
Note:
If the directory number is already used in the Communication Server database, the consistency check detects
it and the creation of the user is cancelled. You can either remove the existing user on the Communication
Server Database or perform a database synchronization with the automatic creation of the user in the Users
application. If none of these operations is possible, you cannot manage the user directly in the Users
application, but you can still associate and manage the 8088 Smart DeskPhone device to the Communication
Server User through the Devices application as detailed in the following steps.
After user creation, all parameters related to this user are available for modification in the properties
area.

4.3.7.3 Creating and associating a set to the user

An 8088 Smart DeskPhone set can be created and associated to a user:
• From the Users application of the OmniVista 8770
• From the Devices application of the OmniVista 8770

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 268/382

Chapter 4 SIP deskphones

The following paragraph presents the procedure from the Users application.
To create and associate a new device to a user:
1. From the Users application, click the Users tab
2. Expand the tree structure and select the user to which the set must be associated
3. Access the contextual menu and select Associate SIP device > New, then select the type, for
example 8088 Smart DeskPhone

4. In the General tab, review/modify the following attribute:

Device identity (MAC address) If the device is deployed with its MAC address, enter the set
MAC address. The MAC address can be entered with or with-
out the colon separator
If the device is deployed with its directory number, leave this
attribute blank and complete the Identification key and Iden-
tification password attributes
5. In the Network tab, review/modify the following attributes:

DNS Enter the DNS address(es)

SNTP Server Enter the SNTP server

6. Click the validate icon to save your modifications
The set is displayed under the user in the tree structure of Users application

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 269/382

Chapter 4 SIP deskphones

4.3.7.4 Configuring the general parameters of the set

This section describes the configuration of general parameters. Refer to Set parameters in a hotel or
business configuration on page 324 for a complete list.
1. From the Users application, click the Users tab
2. Expand the tree structure and select the 8088 Smart DeskPhone set to configure

3. In the Network tab:

• In an OmniPCX Enterprise duplicated configuration, where the two Communication Servers are
on two different subnetworks (spatial redundancy), enter the second Communication Server
address in Secondary Sip Server > Server address
4. In the Telephony tab:
• In the Message waiting indication URI field, enter the physical address of the Communication
Server where the voice mail application is installed, to subscribe the set to voice mail
notifications.
• Enter Prefixes as defined on the OmniPCX Enterprise
5. In the Applications tab:
• For set customization, complete the Customization file (URL) field with the access path to the
customization file, copied on the OmniVista 8770 server
6. In the Advanced tab:
• DM Server:
• Adapt the Binary Update parameters to the maintenance time window, authorized at the
customer site, to proceed with firmware upgrade. By default, the upgrade sequence starts at
11h30 pm for all 8088 Smart DeskPhone sets. During the polling period (180 minutes by
default), each set checks whether a new firmware has been deployed on the Device Manager
and each 8088 Smart DeskPhone set resets and upgrades.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 270/382

Chapter 4 SIP deskphones

• Adapt the Config Update Polling timer to configure the delay before a change of value for
the settings can be applied on the set. The default value is 86400 seconds, which
corresponds to one day.
Note:
During the installation and customization period, to take into account modification of customization
quickly, decrease the timer value to a minimum of 120 seconds.
Once customization is stabilized, to limit traffic on the network, you can switch back to the default value.
• Security:
• Enter the Administrator password: this password is used to access administration settings
on the set. The password configured here replaces the previous password on the set, after
configuration files are downloaded.
• Validate SSH for remote connection
Note:
It is possible to authorize SSH connection later but the set can only recover the change of the
configuration for this setting after the next polling of the configuration files, which depends on the
Config Update Polling timer value.
• If desired, enable the PC Port Protection
Caution:
When this parameter is disabled, the PC port is blocked.

4.3.7.5 Configuring the set parameters on OmniPCX Enterprise

When the 8088 Smart DeskPhone set is used as hotel set, check that the Send NOTIFY instead of
MESSAGE parameter is enabled in its Phone class of service.
1. From the OmniPCX Enterprise configuration window, select: User/<8088 Smart DeskPhone
set>/SIP Extension Parameters

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 271/382

Chapter 4 SIP deskphones

2. Verify the following attribute:

Phone COS The Phone COS number of the set is displayed

3. Select: SIP Extension > Phone classes of service

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 272/382

Chapter 4 SIP deskphones

4. Review/modify the following attribute:

Phone COS Select the phone COS number associated to the 8088
Smart DeskPhone set

Send NOTIFY instead of MESSAGE Select Yes

5. Confirm your entry

4.3.8 Configuring the 8088 Smart DeskPhone as video SIP device

4.3.8.1 Overview
As of R11.2, the 8088 Smart DeskPhone can operate as video SIP device, provided it is associated to
a user declared as SIP device with unrestricted rights to video in configuration. The set can be used for
video communications in meetings or conference rooms. Via its HDMI connector, the 8088 Smart
DeskPhone can be connected to an external HD monitor. This enables the displays of video on a large
screen.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 273/382

Chapter 4 SIP deskphones

Figure 4.10: 8088 Smart DeskPhone video SIP device connected to an external monitor

In video mode:
• The 8088 Smart DeskPhone video SIP device operates with restricted telephone features. The set
cannot initiate a conference (three-party conference, meet-me conference, or casual conference),
but can be included in a conference.
All the existing restrictions for OmniPCX Enterprise sets configured as SIP devices apply to 8088
Smart DeskPhone video SIP devices. For more information on the available features, see: Available
features on page 274.
• The 8088 Smart DeskPhone video SIP device can handle peer to peer video communications
locally (on the same node) or in a network (see: Use cases on page 275).
A peer to peer video communication can only be established during an audio call. When a user
adds video, the current audio communication is escalated to video, provided that the other party
also supports video. On the 8088 Smart DeskPhone video SIP device, a video icon allows to
escalate the audio call to video.
Notes:
Video communications can be performed:
• Between several OmniPCX Enterprises connected through the network (via ABC-F links)
• Between an OmniPCX Enterprise and OpenTouch server (via SIP trunking)
• Between the 8088 Smart DeskPhone video SIP device and a video conferencing bridge (MCU)

4.3.8.2 Available features

Telephonic services allowed (the list is not exhaustive):
• Call by name via LDAP connector
• Session establishment
• Audio call hold
• Audio call consultation hold
• Audio Enquiry call/Audio Broker call
• CLIP/CLIR/COLP/CLOR

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 274/382

Chapter 4 SIP deskphones

• Music on hold
• Call waiting indication
• Transfer unattended
• Audio communication transfer attended
• Call forwarding types (managed by the set):
• Call forward unconditionally
• Call forward on busy
• Call forward on no answer
• Incoming call screening
• Outgoing call screening
• Local auto-answer (interphony)
• DTMF (RFC 2833)
• Redial
• Message waiting indication
• Call Log (incoming, outgoing, missed calls)
• Voice mail access (TUI)
• Voice mail deposit
• Local Appointment Reminder
• Local Programmable Keys
• Local Settings
• Device management from OmniVista 8770
• Video session with 3rd party MCU
• Peer to peer video communication

4.3.8.3 Use cases

The following use cases only display video communications to or from 8088 Smart DeskPhone video
SIP device. For more information on video communications across the OmniPCX Enterprise, see the
Video on public and private SIP trunking section of document [7].
Video
OXE user 1 communication OXE user 2

8088 video 8088 video

SIP device SIP device

OmniPCX Enterprise

Figure 4.11: Video communication on the same node

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 275/382

Chapter 4 SIP deskphones

Video
OXE user 1 communication OXE user 2

8088 video 8088 video

SIP device SIP device
Node 1 ABC-F Node 2
network

OmniPCX Enterprise OmniPCX Enterprise

Figure 4.12: Video communication in an ABC network

Video
OXE user communication Conversation user

8088 video Video

SIP device SIP device (*)

IP network

OmniPCX Enterprise OpenTouch server

Figure 4.13: Video communication between an 8088 Smart DeskPhone SIP video device on OmniPCX
Enterprise and a video device on OpenTouch

(*): The video SIP device can be an 8088 Smart DeskPhone, a third party video device from LifeSize,
or an OpenTouch Conversation application (PC or tablet).

4.3.8.4 Set configuration using OmniVista 8770

4.3.8.4.1 Overview
The 8088 Smart DeskPhone configuration as video SIP device consists in:
• Creating a user as SIP device on page 277
• Creating and associating an 8088 Smart DeskPhone set to a user on page 278
• Validating user rights to video on page 280
• Configuring video settings on OmniPCX Enterprise on page 281
8088 Smart DeskPhone configuration must be completed with:
• Commissioning the 8088 Smart DeskPhone (see: Commissioning sets on page 298)
• Updating the 8088 Smart DeskPhone with the SIP binary including video capabilities. The SIP
binary must be made available on the download server (see: Deploying set binaries on page 295)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 276/382

Chapter 4 SIP deskphones

4.3.8.4.2 Creating a user as SIP device

Note:
User configuration can be performed with the Users application of OmniVista 8770 (recommended) or the
OmniPCX Enterprise configuration window. In the following paragraphs, only the configuration with the Users
application is described.
Before configuring an 8088 Smart DeskPhone set, a user must be declared as SIP device in the
Users application of OmniVista 8770:
1. From the Users application of the OmniVista 8770, click the Users tab
2. Access the contextual menu and select Create User

3. In the Common Attributes frame, complete the following fields:

User type Select OXE

Last Name Enter the user name

First Name Enter the user first name

User ID Modify if necessary the displayed user identifier

A default user identifier is built from the name and first name and can be
modified if needed.
4. In the OXE attributes frame, complete the following fields:

OXE ID Click and use the browser to select the desired OmniPCX Enterprise

OXE directory number Enter the user directory number

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 277/382

Chapter 4 SIP deskphones

Device Type Click and use the drop-down menu to select SIP device
5. Click the validate icon to apply your modifications
The user is declared in the database of the OmniVista 8770 and the corresponding OmniPCX
Enterprise
Note:
For more information on user creation from the OmniVista 8770, refer to the section Users of the OmniVista 8770
Online Help.
4.3.8.4.3 Creating and associating an 8088 Smart DeskPhone set to a user
Notes:

• The sets can also be declared from the Devices application of the OmniVista 8770 and associated to the user
later, using the same application. In the following, only the configuration with the Users application is
described.
• This section describes only the configuration of main parameters. Refer to Set parameters in a hotel or
business configuration on page 324 for a complete list.
The 8088 Smart DeskPhone set configuration for a user consists in creating and associating a set to a
user from the OmniVista 8770 application. This operation automatically creates a configuration file,
required for set commissioning, on the OmniVista 8770 server.
To create and associate a new 8088 Smart DeskPhone set to a user in one step:
1. From the Users application of the OmniVista 8770, click the Users tab
2. Expand the tree structure and select the user to which the 8088 Smart DeskPhone set must be
associated
3. Access the contextual menu and select Associate SIP device > New, then select 8088 Smart
DeskPhone

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 278/382

Chapter 4 SIP deskphones

4. In the General tab, review/modify the following attribute:

Device identity (MAC If the 8088 Smart DeskPhone set is deployed with its MAC address, en-
address) ter the set MAC address. The MAC address can be entered with or with-
out the colon separator.
If the 8088 Smart DeskPhone set is deployed with its directory number,
leave this attribute blank and complete the Identification key and Identi-
fication password attributes required during set initialization
5. In the Network tab, review/modify the following attributes:

DNS1 to DNS3 Enter the DNS IP address(es)

Secondary SIP server In an OmniPCX Enterprise duplicated configuration, where the two com-
munication servers are on two different subnetworks (spatial redundan-
cy), enter the second communication server IP address (Server address
attribute)

SNTP server Enter the SNTP server IP address (if configured)

6. In the Telephony tab, review/modify the following attributes:

Interphony Select the check box

Transfer Select the check box

7. In the Applications tab, review/modify the following attribute:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 279/382

Chapter 4 SIP deskphones

Customization file For set customization, complete this attribute with the access path to the
(URL) customization file, copied on the OmniVista 8770 server
8. In the Call by name tab, review/modify the following attribute and its descendants:

Directory search Select the check box and configure the LDAP settings used to search for
contacts in an LDAP directory
Note:
The Photo field is not used.

9. In the Device tab, review/modify the following attribute:

Display to HDMI Select the check box to allow an external screen or TV to be able to play
video
10.Click the validate icon to save your modifications
The new 8088 Smart DeskPhone set set is created in the corresponding OmniPCX Enterprise and
associated to the corresponding user. This set is displayed below the user in the tree structure of
Users application
When a 8088 Smart DeskPhone set is created and associated to a user with its MAC address, a
configuration file with the <MAC address>.xml format is automatically created on the OmniVista
8770 server and copied in the directory: /<8770 path>/Data/DM/Deploy/VHE8082.
When a 8088 Smart DeskPhone set is created and associated to a user without its MAC address, the
configuration file is not created immediately. It is created only when the Identification key and
Identification password configured above are entered on the set.
4.3.8.4.4 Validating user rights to video
To use the 8088 Smart DeskPhone set as SIP video device, validate user rights to video:
1. From the Users application of the OmniVista 8770, click the Users tab
2. Expand the tree structure and select the user to which the 8088 Smart DeskPhone set is associated
3. Select the OXE configuration tab, then the ALL tab

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 280/382

Chapter 4 SIP deskphones

4. Review/modify the following attribute:

Video support profile Select Un Restricted

5. Click the validate icon to apply modification
4.3.8.4.5 Configuring video settings on OmniPCX Enterprise
The following configuration interacts with the configuration of video transit for public and private SIP
trunking. For more details on configuration, refer to the Video on public and private SIP trunking section
of document [7].
From the OmniPCX Enterprise configuration window:
1. Select System > Other System Param. > SIP parameters
2. Review/modify the following attributes:

SIP video transit According to your needs, select:

mode
• Not available (default value): No video is offered on this node
• Local type: Video can be negotiated locally on this node
• Network type: Video can be negotiated locally and in an ABC-F
network (provided all nodes are in R11.2 or later version)
Caution:
Any modification of this value requires a reboot to create or update the
internal table used to store video information.

Enhanced codec ne- This attribute interacts with the SIP video transit mode attribute, as de-
gotiation tailed in Table 1

Private SIP transit Select Full call handling mode.

mode
In this configuration, direct and on demand video calls are available
through Call Handling

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 281/382

Chapter 4 SIP deskphones

table 4.4: Video/multi-codec compatibility table

Enhanced codec negotiation

SIP Video transit mode Not available Local type Network type

Not available No Multi-codec Multi-codec: local Multi-codec: network + local

No video No video No video

Local type Not allowed Multi-codec: local Multi-codec: network + local

Video: local Video: local

Network type Not allowed Not allowed Multi-codec: network + local

Video: network + local
3. Confirm your entries
4. Select SIP > SIP Ext Gateway
5. Review/modify the following attribute:

Video Support Profile According to your needs, select:

• Not supported (default value): No video is offered on this gateway
• On demand: Video is negotiated after establishment of the call (in the
RE-INVITE). The INVITE does not contain video
• Unrestricted: Video can be negotiated in basic call as well as after
call evolution
6. Confirm your entry
7. Select SIP > SIP Proxy
8. Review/modify the following attribute:

TCP when long mes- Do not select the check box

sages
Note:
Reset of SIPMotor is required to take into account the change.

9. Confirm your entry

10.Reboot the OmniPCX Enterprise server to take the new values into account

4.3.8.5 Set configuration using 8088 Web Management

4.3.8.5.1 Overview
8088 Web Management allows you to access 8088 Smart DeskPhone configuration from a web
browser (HTTPS connection). This application offers remote configuration of individual 8088 Smart
DeskPhone sets on the network (LAN).

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 282/382

Chapter 4 SIP deskphones

8088 Web
Management tool

Administration 8088 Premium

Computer DeskPhone
(web browser) HTTPS connection

LAN

From the 8088 Web Management, you can:

• Deploy the set on an OmniPCX Enterprise, or other generic SIP server without Device Manager
(OmniVista 8770)
• Configure the set settings, with the same level of features as on the 8088 Smart DeskPhone itself
• Connect in administrator mode and load a new binary on the set to upgrade its current version
• Export set information in the form of a file that can be read in text format
This can be useful for maintenance purposes (for example: set replacement)
• Consult all set settings (read only)
Caution:
The 8088 Web Management cannot be used to configure a 8088 Smart DeskPhone as hotel set.
4.3.8.5.2 Prerequisite and information required
• The 8088 Smart DeskPhone phone set must be connected to the LAN via a PoE switch or AC/DC
external adapter. For more information, refer to: Plugging the set on page 298
Consult and modify settings when connected in administrator mode
• The minimum 8088 Smart DeskPhone software version must be R200.02.016.2
• The set IP address is required to access 8088 Web Management. To obtain the set IP address,
proceed as follows:
1. Press Settings on the set screen (local phone menu)
The Settings page is displayed
2. Press the Admin icon and enter the administration password
3. Select Network > IP in the tree structure
The IP address is displayed

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 283/382

Chapter 4 SIP deskphones

Figure 4.14: IP setting page example

Note:
Access to the setting menu is also available at set initialization (Settings icon available at the bottom of the
screen). Entering setting menu at initialization stops the automatic reboot process and enables you to configure
set settings.
• If the set must be deployed on an OmniPCX Enterprise, first declare the set on the OmniPCX
Enterprise with the type set to SIP device.
• You need an up to date browser (Google Chrome or Mozilla Firefox). Internet Explorer and Microsoft
Edge are not fully supported by the 8088 Web Management.
4.3.8.5.3 Accessing the 8088 Web Management
To access 8088 Web Management:
1. From the administration computer, open a web browser (for example: Google Chrome or Mozilla
Firefox), and enter the set IP address: https://<set IP address> (for example: https://
172.25.41.192)
Note:
Before accessing the login page of 8088 Web Management, you must accept the security exception by
pressing Advanced and Proceed to …… in Chrome or Advanced in Mozilla Firefox where an exception is
added. The security exception is due to the fact the we use a self-signed certificate while browsers do not
accept self-signed certificates as safe certificates.
A login page is displayed

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 284/382

Chapter 4 SIP deskphones

Figure 4.15: Login page example

2. Enter the login admin and the administration password for the set
At first startup, you are prompted to change your password. After modification, this password is
synchronized with the password on the set.
The password must comply with the following rules:
• 8 characters minimum
• At least one lower and upper case letters, one number and one special character
• No special characters such as: " ' ( ) ` < > | & or a space
3. Click Connect
The 8088 Web Management home page is displayed
4.3.8.5.4 8088 Web Management overview
The 8088 Web Management home page opens immediately after login.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 285/382

Chapter 4 SIP deskphones

Figure 4.16: 8088 Web Management home page example

The 8088 Web Management home page consists of a menu bar:

Menu Select, to:

WIZARD Deploy the set on an OmniPCX Enterprise, or other generic SIP server
(see: Deploying the 8088 Smart DeskPhone phone set on a SIP server on
page 287)

STATUS View all set settings in read-only mode

A search tool is provided to sort settings with a predictive search
Edition is possible from the Settings menu.

SETTINGS Configure the set settings that are already available on the physical set in-
terface (see: Modifying the phone set settings on page 292)

MAINTENANCE • Load a new binary on the set (see: Updating phone set binaries on page
293)
• Export/import set information to or from a file (see: Exporting/importing
set information to or from a file on page 293)
The file is exported in a transparent way to the computer (no encryption).
It is available in a modifiable file (*.txt format)
• Change the current administrator password

LOGOUT Log out

Note:
Automatic logout redirects to the login page after an inactivity period.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 286/382

Chapter 4 SIP deskphones

Menu Select, to:

REBOOT Reboot the set

This operation enables to take into account new parameters or changes

4.3.8.5.5 Deployment procedure overview

The 8088 Web Management provides a wizard for the 8088 Smart DeskPhone deployment on a SIP
server (see: Prerequisite and information required on page 283). After deployment, you can modify the
current values found on the set (see: Modifying the phone set settings on page 292).
The 8088 Smart DeskPhone deployment must be completed with:
• Commissioning the 8088 Smart DeskPhone (see: Commissioning sets on page 298)
• Updating the 8088 Smart DeskPhone with the SIP binary including video capabilities. You can:
• Directly load the new SIP binary on the 8088 Smart DeskPhone (see: Updating phone set
binaries on page 293)
• Deploy the new SIP binary on a download server, before loading into the 8088 Smart
DeskPhone (see: Deploying set binaries on page 295)
4.3.8.5.6 Deploying the 8088 Smart DeskPhone phone set on a SIP server
From the 8088 Web Management home page:
1. Click the WIZARD menu

Figure 4.17: WIZARD starting window example

The 8088 Web Management provides a set of profiles used to simplify the 8088 Smart DeskPhone
phone set deployment on a SIP server:
• The OXE Business profile contains a list of predefined parameters enabling to deploy a 8088
Smart DeskPhone phone set on an OmniPCX Enterprise
• The Custom profile enables to select a profile configured offline and stored on the computer on
which 8088 Web Management is running. This profile enables to configure a list of parameters
specific to a SIP server.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 287/382

Chapter 4 SIP deskphones

The custom profile is a JSON file with the following characteristics:

Example:
{"display":[
(start of JSON file)
{"name":"Contacts Info",
(name of the menu addressing a set of settings)
"enable":true,
(indicates if you can directly access this tab)
"index":0,
(position of settings on the wizard)
"data": [
(set of settings of Contacts Info menu)
{"id":" DirMaxContact",
(Id of the first setting)
"value":"",
(value of the first setting. If not defined, takes the
phone value)
"optional":true}
(indicates if the setting is required or not)
]
}
]}

2. Use the drop-down menu to select the profile that must be applied for the 8088 Smart DeskPhone
phone set deployment. If the profile is a Custom profile, use the browse button to select the profile
on the computer (JSON file)
3. After profile selection, click Submit to launch the configuration

Figure 4.18: WIZARD configuration window example

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 288/382

Chapter 4 SIP deskphones

The deployment wizard is displayed with several fields to complete in the frames: Network, SIP,
LDAP and User. Each frame provides the minimum settings to configure for set deployment on the
SIP server
4. In the Network frame, complete the following fields:
The following table presents the parameters of Network frame when the OXE Business profile is
selected.

SNTP Server Enter the IP address of the SNTP server used to synchronize com-
puter clocks on the internet

DHCP Mode Select the set initialization mode (Static or DHCP)

DNS 1 Enter the IP address of the DNS server able to resolve private
FQDNs

IP address Enter the IP address of the set (Static mode only)

Subnet Mask Enter the IP address of the subnetwork mask (Static mode only)

Gateway Enter the IP address of the default gateway (Static mode only)

VLAN number If VLAN is enabled, enter the VLAN number (default value: 4095)

Vlan Enable Click the field to select 1 (VLAN enabled) or 0 (VLAN disabled)
5. Click Next, and complete the following fields in the SIP frame:
The following table presents the parameters of SIP frame when the OXE Business profile is
selected.

Group1 authentication If authentication is used, enter the ID used for set authentication with
name the OmniPCX Enterprise SIP proxy

Group1 authentication If authentication is used, enter the password used for set authentica-
password tion with the OmniPCX Enterprise SIP proxy

Group1 authentication If authentication is used, enter the name of the OmniPCX Enterprise
realm proxy realm

Group1 user name Enter the username or directory number

Group1 display name Enter the name displayed as Caller ID when the user makes a phone
call

Group1 domain name Enter the domain name of the OmniPCX Enterprise SIP proxy

Local RTCP port Enter the local RTCP port number (default value: 6001)

Local RTP port Enter the local RTP port number (default value: 6000)

Local SIP port Enter the local SIP service port number (default value: 5060)

Local video port Enter the SIP local video port (default value: 7000)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 289/382

Chapter 4 SIP deskphones

Server 1 address Enter the IP address of the OmniPCX Enterprise

Server 1 port Enter the port number used on the OmniPCX Enterprise

Server 2 address Enter the main address of a second OmniPCX Enterprise (spatial re-
dundancy configuration). When the main communication server is not
available, the set can register to this secondary communication serv-
er.

Server 2 port Enter the port number used on the secondary OmniPCX Enterprise

Voice Mail number Enter the mailbox directory number of the user (can be modified from
an OmniPCX Enterprise configuration tool only)
6. Click Next, and complete the following fields in the LDAP frame:
The following table presents the parameters of LDAP frame when the OXE Business profile is
selected.

LDAP enabled Click the field to select 1 (LDAP enabled) or 0 (LDAP disabled)

LDAP Server URL Enter the IP address of the LDAP server

LDAP Search Base Enter data allowing a more precise search in the requested directory.
This is a string of characters, as shown below:
Example:
o=ALE International corresponds to the following syntax: o (organization) =
company.

LDAP Fields Mapping

LDAP Login Enter the name used for connection to the LDAP server

LDAP Password Enter the password used for connection to the LDAP server
7. Click Next, and complete the following fields in the User frame:
The following table presents the parameters of User frame when the OXE Business profile is
selected.

First name First name of the user (can be modified from an OmniPCX Enter-
prise configuration tool)

Last name Enter the last name of the user (can be modified from an OmniPCX
Enterprise configuration tool)

Video telephony power Select the vertical scan frequency which is needed to avoid flickering
line frequency value of the video. This corresponds to the main power frequency of the
country. The parameter value is country dependent (default value: 50
Hz)

Video support Click the field to select Enabled (video capabilities activated on set)
or Disabled (default value)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 290/382

Chapter 4 SIP deskphones

DialingRuleExternalPrefix Enter the external call prefix to access the public network (default
value: 0)

Time Zone Enter the time zone of the set (default value: (UTC) Universal)

Language Enter the language of the set display (default value: English)
8. Click Next
A summary is displayed
9. Click Confirm
Notes:

• Some fields of the selected profile can have a predefined value displayed on the wizard. If there is no
predefined value, the field is completed with the current value found on the set (if it exists).
• The wizard can modify a specific list of settings according to the selected profile. There are two types of
settings:
• Visible settings always displayed on the wizard. You can configure them as described above
• Hidden settings automatically defined by other selections in the wizard such as desired country (see: Table
2)
List of settings that 8088 Web Management automatically modifies for set deployment on the OmniPCX
Enterprise:

table 4.5: Hidden settings

Name Proposed value

ConferenceAlwaysLocal false

DialingRuleAreaCode

DialingRuleCountryCode

DialingRuleExternalPrefixExceptions

DialingRuleMinNumberLength 6

DmSecucfgPcPort false

SIPLocalConfEnable false

SIPMaxCall 2

SIPPhoneStateNotifyType

SIPServer1GroupNumber 1

SIPServer2GroupNumber 2

SIPUseSeplos

TelephonyLockRemote

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 291/382

Chapter 4 SIP deskphones

Name Proposed value

VideoCallAsymmetric false

VideoCallPacketizationMode 1

4.3.8.5.7 Modifying the phone set settings

If necessary, you can modify the set settings that are already available on the physical set interface.
1. From the 8088 Web Management home page, click the SETTINGS menu

Figure 4.19: Settings window example

This page provides all user and administration settings that are available on the physical phone
interface. Settings are classified in several frames: Application, Device, Network, and Security.
For the parameter meaning, refer to Deploying the 8088 Smart DeskPhone phone set on a SIP
server on page 287.
2. According to your needs, select a frame and modify the parameters on screen
3. Click Apply to validate your modifications
A message indicates if all the modified settings have been successfully applied to the phone set. If it
is not the case, an error message is displayed. If you must reboot the phone set, a warning pop-up
is displayed at the top left of the home page to inform you that your phone set must be restarted. In
addition, a blinking icon in front of the REBOOT menu reminds you that you must reboot the phone
set.
Note:
To search the value of a specific setting, use the Status menu. This page lists all settings available for an
administrator.
A search tool is provided to sort settings with a predictive search.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 292/382

Chapter 4 SIP deskphones

4.3.8.5.8 Updating phone set binaries

1. From the 8088 Web Management home page, click the MAINTENANCE menu

Figure 4.20: Binary update configuration window example

2. Click Update, then click the Browse... button
A browser window opens
3. Select the target binary file (*.zip format) and validate
The name of the selected binary file is displayed on screen
4. Click Submit
A message indicates that you can no longer perform configuration from the 8088 Web Management
tool during the upload process. If the binary file size cannot be processed by the 8088 Smart
DeskPhone (for example: not enough disk space), the 8088 Web Management displays an error
and forbids binary upload.
If the upload process is in progress, you can cancel the process by pressing the Cancel button.
Once the file uploaded, you are disconnected from the 8088 Web Management tool. As long as the
update process is running in background, you cannot log in to the phone set. If there is no error, the
update process starts. The icon appears on the top right of the phone set screen to inform the
user that an update process is ongoing.
Once the update finished, the phone set reboots to complete the update process.
4.3.8.5.9 Exporting/importing set information to or from a file
The file export/import operations allow you to retrieve a configuration from another phone set or
duplicate a configuration from one of your phone set. When a configuration is moved from your phone
set to another set, be aware that you may have a conflict between the 2 phone sets (for example, if
they have the same IP address).
To export set information to a file:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 293/382

Chapter 4 SIP deskphones

1. From the 8088 Web Management home page, click the MAINTENANCE menu
2. Go to: Save/Restore > Export configuration

Figure 4.21: Export configuration window example

3. Click the Generate configuration file button
The file is created and a download button is displayed
4. Click the Save configuration file to my PC button
An export window is displayed
5. Select any of the following operations:
• Edit the file with a text editor
• Register the file on the computer
6. Click OK
To import set information from a file:
1. From the 8088 Web Management home page, click the MAINTENANCE menu
2. Go to: Save/Restore > Import configuration

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 294/382

Chapter 4 SIP deskphones

Figure 4.22: Import configuration window

3. Click the Browse... button, then select the file to upload (*.txt format) and validate
The name of the file is displayed on screen
4. Click the Import button

4.3.8.6 Maintenance
Several maintenance commands are available:
• sipauth: displays authentication information on 8088 Smart DeskPhone video SIP devices (user
name and corresponding password)
• sipdict: displays the contents of dictionary, that is the correspondence between the directory
numbers and URLs of the 8088 Smart DeskPhone video SIP devices
• sipregister: displays the list of SIP users registered on the system, including those who are
associated to 8088 Smart DeskPhone video SIP devices
The following traces can be activated when SIP is active:
• motortrace 3
• Call Handling traces:
• tuner cpl cpu at hybrid=on
• atcdbg sip=on
• mtracer -a

4.3.9 Deploying set binaries

4.3.9.1 Adding the software
Prerequisite: A synchronization between the OmniVista 8770 and the corresponding Communication
Server is necessary, before configuring a software deployment package.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 295/382

Chapter 4 SIP deskphones

1. Download the firmware binary from the Enterprise Business Portal

2. Save the firmware binary zip file on the OmniVista 8770 server
3. From the Devices application, click the Applications tab
4. Expand the tree to the node to which sets are attached

5. There are two cases:

• If no package is associated to the device type:
1. Right-click the device type and select Add Package
2. In the Deployment Package window, enter the deployment package name in the
Application name field
Note:
Ensure that the deployment package name matches the required format.
• If a package has already been created, select this package
Caution:
It is necessary to use the same package when upgrading handsets. This allows to use the access
path declared in the set configuration file for the deployment package and the binary upgrade
process.
6. Click the Tel. Application Files line
A Browse window opens.
7. Select the file you downloaded and click OK
8. If external applications are available, click the External Appli. files line
A Browse window opens.
9. Select the file(s) you downloaded and click OK
10.Click the Devices line and click the selection button
A search window opens.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 296/382

Chapter 4 SIP deskphones

11.Click the Magnify icon to display the list of devices and select the list of devices to update or to add,
then click OK
12.Click the validate icon to save your modifications

4.3.9.2 Deploying the software

Deploying the software consists in making it available for download on the OmniVista 8770 server.
Deploying the software is necessary after a package has been created or modified (see Adding the
software on page 295).
To deploy the software:
1. From the Devices application, click the Applications tab
2. Expand the tree structure to display the package to deploy

Figure 4.23: Package deployment window example

3. Right-click the package to deploy and select Deploy Package
The Task Type window opens
4. Select Simple job
A scheduler window opens.
5. Leave values unchanged to deploy immediately, or schedule the exact time and date to deploy and
click OK
6. Check that index.xml.signed, key.xml and rpm files are extracted on the OmniVista 8770
server In the directory:
8770/data/DM/deploy/VHE8082

4.3.10 Deploying a customization file

The customization file is an xml file downloaded by the set at startup. For more information, see: Set
customization on page 310.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 297/382

Chapter 4 SIP deskphones

To deploy a customization file:

1. Copy the customization file on the OmniVista 8770 server in the directory where set configuration
files are placed: \8770\data\DM\Deploy\<device type>
2. Enter the access path to the customization file in the 8088 Smart DeskPhone set parameters. The
field to complete is: Customization file (URL). For more information, see: Configuring the general
parameters of the set on page 270

4.3.11 Commissioning sets

4.3.11.1 Plugging the set
• If using the 8082 Power Over Ethernet Injector Kit:
1. Plug an RJ45 cable between the data in port of the kit and the LAN
2. Plug an RJ45 cable between the data and power out port of the kit and the set LAN connector
3. Plug the kit to the mains
• If not using the 8082 Power Over Ethernet Injector Kit, plug an RJ45 cable between the set LAN
connector and a port of the switch
• If not using a PoE switch or the 8082 Power Over Ethernet Injector Kit, connect the AC/DC external
adapter:
1. Plug the appropriate cable from the adapter into the set's power supply connector.
2. Connect the plug from the adapter to the mains power supply.

4.3.11.2 Configuring network parameters through MMI (static configuration)

To configure network parameters statically:
1. If necessary, start the set and wait until the Settings menu is available
2. Press Settings on the set screen
3. Press Admin and enter the password
Note:
The admin password is configured on the OmniVista 8770 and obtained by the set at initialization via the
configuration file. The default Admin password (after flash reset and before configuration file download) is
*tx8000#.
4. Select Network > IP in the tree structure
5. Review/modify the following parameters:

DHCP mode Select Static

Domain

VLAN Enable Select true or false according to your needs.

Default value: false

Vlan Number If VLAN is enabled, enter the VLAN number

IP Address Enter the IP address

Subnet mask Enter the subnet mask

Gateway Enter the gateway IP address

6. Select Network > DM in the tree structure

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 298/382

Chapter 4 SIP deskphones

7. Enter the DM URL: this can be either the IP address or the FQDN (associated to DNS) of the
OmniVista 8770 server, for example:
https://192.168.12.34/DM/VHE8082/ or
https://server8770.mycompany.com/DM/VHE8082/
8. Select Network > DNS in the tree structure
Note:
DNS address(es) can also be configured on OmniVista 8770. The values configured locally on the set are used
at first initialization to recover the configuration files. At subsequent startups, the values configured in the
Devices application and provided in the config<MAC>.xml are used in priority.
9. Enter the DNS address(es)
Note:
In a hotel or business configuration, DNS entries are optional, as the configuration files generated by
OmniVista 8770 provide URLs with IP addresses. DNS entries are only useful when the local DM URL is
configured with an FQDN.
10.Press Back
The set resets to take into account new parameters.

4.3.11.3 Entering device key and password

If asked during initialization, enter the Device Key (by default, the directory number) and the Device
password (see Creating and associating a set to the user on page 268 for more information on these
parameters).

4.3.12 Reset to factory

4.3.12.1 Overview
The reset to factory is intended to cope with situations in which the administrator can no longer access
the set configuration because the set administrator password has been lost, and the set is configured
in static mode or uses a specific VLAN on the previous installation. Reset to factory is not needed
when a set is configured in dynamic mode: in this case, the set administrator password can be
changed through the OpenTouch configuration window of OmniVista 8770, by modifying the password
for SSH in the advanced parameters of the target set.
The reset to factory enables to restore the set to the “Out of the box” initial status, except that the
software version remains unchanged on the set. It works during the set initialization. If initialization is
done, there is no other solution to reset sets to their factory settings.
The reset to factory performs the following actions:
• Restore the set administrator password to its default value
• Clean all user personal data and webapps
• Restore the configuration and settings to their default values
• Remove certificate data such as customer certificates and CTL, except ALE International default
certificate stored during manufacturing
• Store a message into defense log to indicate a reset to factory has been done
• Reboot the set
By using the reset to factory, there is no need to return sets for repair.
Note:
Although the feature is not intended for end-users, it is available in user mode, as this feature is used when the set
administrator password has been lost, and therefore the administrator mode cannot be reached.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 299/382

Chapter 4 SIP deskphones

It is not possible to limit the availability of the feature for users and/or administrators by setting the appropriate
display-rights to the setting EnableResetFactory in the third configuration files, generated by the
Customizer.

4.3.12.2 Restoring the set to factory settings

To perform the reset to factory on a set:
1. Restart the set
2. During set initialization (steps 2 or 3) , press Settings
3. Select Device > Reset

Figure 4.24: Reset to factory menu example on 8082 My IC Phone

4. Set the Reset to factory option to Yes
Your are prompted to enter the administrator password required for the reset to factory. The default
administrator password is *tx8000#.

5. Enter the administrator password, then press OK to confirm the reset to factory, or press Cancel to
cancel the reset to factory
• If the password is WRONG or Cancel is pressed; the set displays again the reset screen, the
choice selector is set to NO: without further action, the set goes on with normal startup.
• If the password is VALID, you are prompted to confirm the action:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 300/382

Chapter 4 SIP deskphones

6. Press Yes to confirm the reset to factory: reset to factory is performed and the set restarts
immediately.
Press No to cancel: the set displays again the reset screen, the choice selector is set to NO: without
further action, the set goes on with normal startup.

4.3.13 Redundancy
To improve system operating reliability, 8088 Smart DeskPhone sets in a hotel or business
configuration support SIP server redundancy. This implies compatibility with OmniPCX Enterprise
Communication Server redundancy.
The two Communication Servers can be in different IP subnetworks (spatial redundancy).
For each Communication Server, the configurations files include two sets of SIP server parameters
(main and secondary).
SIP server redundancy allows the continuity of service with the same level of feature: when the main
server fails, a switchover to the secondary server occurs.
Redundancy SIP proxy switchover occurs in the following circumstances:
• At phone initialization: if the phone device is unable to register itself on the SIP main registrar server
(usually the SIP proxy)
• When in operation, redundancy switchover is activated in case of no response from the main SIP
proxy to SIP messages sent by the phone
The SIP secondary server proxy address may be defined in any of the following manners:
• The two redundant OmniPCX Enterprises must have:
• The same node name
• Different IP addresses
The internal name resolver activated option must be set to yes
The two OmniPCX Enterprises correspond to DNS1 and DNS2. The OmniPCX Enterprise that
answers is the one that is alive.
The SIP server being always synchronized, SIP registration is not required after SIP proxy
switchover.
• Specifying the two SIP proxy addresses. In this case the 8088 Smart DeskPhone is in charge of
checking both IP addresses alternatively.
Redundancy switchover does not require a device reset.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 301/382

Chapter 4 SIP deskphones

4.3.14 Compliant standards

4.3.14.1 Hearing aid compatibility
The Hearing Aid Compatibility (HAC) feature consists in providing audio assistance for hearing
impaired people.
The 8088 Smart DeskPhone handset is compliant with the following standards:
• FCC47 C.F.R Part 68 Sections 68.316 and 68.317
• Industry Canada CS 03 Part V , Issue 9 ( 2009)
• AS/ACIF S040:2011
The 8088 Smart DeskPhone handset is compliant with the following standards:
• TIA/EIA-504 standard: telecommunication telephone terminal equipment magnetics fields and
acoustic gain requirement for handset telephone intended for use by the hard of hearing
• ETS 300 381 : inductive coupling of telephone earphones to hearing aids

4.3.14.2 Narrowband audio

The audio quality complies with the following narrowband VoIP standards:
• TIA/EIA810B: acoustic performance for narrowband digital wireline transmission for VoIP
• For 8082 My IC Phone handsets only: ETSI ES 202 737: speech processing, transmission and
quality aspects, transmission requirements for narrowband VoIP terminals (handset and headset)
• For 8082 My IC Phone handsets only: ETSI ES 202 738: speech processing, transmission and
quality aspects, transmission requirements for narrowband VoIP terminals (loudspeaker and
handsfree)
The codecs available for narrow band communication interoperability are the following:
• G.711 A and µ law 64 kbit/s with packets loss concealment G.711. Minimum framing for G.711
payload packet: 20 ms for packet emission, 10 ms supported for packet reception
• G.729A 8 kbit/s with annex B

4.3.14.3 Wideband audio

Wideband audio provides an acoustic frequency response over the range 200-6300 Hz.
The 8088 Smart DeskPhone audio quality complies with the following wideband VoIP standards:
• TIA/EIA920A : acoustic performance for wideband digital wireline transmission for VoIP
• 110-A (01/02/2011) + ERTA (01/02/2012) in handset
• 120-A (2012) in speakerphones
• 130-A (01/02/2011)+Addendum1 ( 01/07/2012) in headset
The 8082 My IC Phone audio quality complies with the following wideband VoIP standards:
• TIA/EIA920A : acoustic performance for wideband digital wireline transmission for VoIP
• ETSI ES 202 739: speech processing, transmission and quality aspects transmission requirements
for wideband VoIP terminals (handset and headset)
• ETSI ES 202 740: speech processing, transmission and quality aspects transmission requirements
for wideband VoIP (loudspeaker and handsfree)
The wideband audio coding of 8088 Smart DeskPhone and 8082 My IC Phone sets is based on two
codecs to support a wide range of SIP devices:
• G.722.2 / AMR-WB
• ITU G.722 5SB ADPCM WB at 64 kbit/s

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 302/382

Chapter 4 SIP deskphones

4.3.14.4 Noise and acoustic shock

8088 Smart DeskPhone sets comply with the European standard ETSI EG 202 518 V1.4.1 (2014- 01),
US standard Annex NAD2 CAN/CSA-C22.2 N 60950-1-07, and Australia standard AS/ACIF S004:2013
for noise and acoustic shock, as shown in the table below.
8082 My IC Phone sets comply with the European standard (TBR8 - annex C), US standard (UL/CSA
60950), and Australia standard (AS/ACIF S004) for noise and acoustic shock, as shown in the table
below.

Standard Short duration peak acoustic Long duration acoustic pres-

pressure (short duration im- sure (steady state input)
pulses)

• 8088 Smart DeskPhone: 130 dBspl 118 dBspl (rms)

Europe: ETSI EG 202 518
V1.4.1 (2014- 01)
• 8082 My IC Phone: Europe:
TBR8 - annex C

• 8088 Smart DeskPhone: 136 dBspl 125 dB(A)

USA/Canada Annex NAD2
CAN/CSA-C22.2 N
60950-1-07
• 8082 My IC Phone: US:
UL/CSA 60950

Australia: AS/ACIF S004 123 dBspl 120 dB(A)

4.3.15 Environmental constraints

Storage, transportation and sets environment comply with the following standards:
• ETS 300 019 1.1 V2.1.8 (2013-12) Storage, Class 1.2: Weather protected, Not temperature
controlled locations
• ETS 300 019 1.2 V2.1.7 (2013-12) Transportation, Class 2.3: Public transportation
• ETS 300 019 1.3 V2.3.7 (2013-12) In Use, Class 3.2: Stationary use, Partly Temperature controlled
locations

4.3.15.1 When in use

• Temperature: to achieve optimum reliability, the ambient temperature must be between -5°C and
+45°C. In degree Fahrenheit, the ambient temperature must be between 23°F and 113°F
• Relative humidity: relative humidity must be between 5% and 95% (without condensation)

4.3.15.2 Storage
• Temperature: temperature must be between -25°C (-13°F) and +55°C (131°F)
• Relative humidity: relative humidity must be between 10% and 100% (without condensation)

4.3.15.3 Transportation
• Temperature: temperature must be between -40°C (-40°F) and +70°C (158°F)
• Relative humidity: relative humidity must not exceed 95% (without condensation)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 303/382

Chapter 4 SIP deskphones

4.3.16 Set power supply

The 8088 Smart DeskPhone set can be powered in two ways:
• Locally, from the main socket via an AC/DC external adapter.
• Via Ethernet, using PoE (Power over Ethernet) technology.
PoE offers the advantage of simplified wiring. It also allows the system to be secured more easily. A
single backup power supply can be used for all devices connected to a switch.
PoE can be performed:
• Via the Power Patch Panel A4098 PP.
• Via a switch compatible with the 802.3af standard
• Via the 8082 Power Over Ethernet Injector Kit
8088 Smart DeskPhone sets send power information to the switch they are connected to. This
information consists of:
• The class number
• The power value negotiated through LLDP
At initialization, LLDP POE negotiation is used in with 802.3af to provide more accurate information
than just the class number. The power value negotiated depends on USB devices connected on the
set, according to the following formula:

PLLDP negociated = Pmaxterminal +PUSB devices + 1.5W

Equipment connected to the PC port is not taken into account and requires separate power feeding.

table 4.6: 8082 My IC Phone power supply summary

Power Patch Panel Yes

802.3af compatible Yes

PoE class 3 max

Power reduction LLDP-MED

table 4.7: 8082 My IC Phone set power consumption

Backlight is on X X X X X X X X

Bluetooth® handset is X X X
loading

LAN Ethernet link is X X X X X X X X X

connected (1 Gbps)

PC Ethernet link is X X X X X X X
connected (1 Gbps)

Mini keyboard X X X X X X

USB 5V 600mA X X X X X

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 304/382

Chapter 4 SIP deskphones

The phone is ringing at X

maximum volume

Bluetooth® handset X
communication (max
volume)

Handsfree communica- X
tion (nominal volume)

The phone is idle X X X X X X

Measured PoE Con- 10.93 10.01 10.70 10.28 9.91 6.69 4.94 4.55 3.88
sumption (W) (RMS
values)

table 4.8: 8088 Smart DeskPhone estimated power supply consumption

Scenario Proc Camera USB AOM Phone Phone+ ac-

cessories

STANDBY Min No 300mA No 0.5W 2.9W

IDLE Idle No 500+100mA Yes 3x 2.8W 4.6W

MAX USB Max Yes 500+100mA No 9.4W 12.7W

MAX AOM Max Yes 300mA Yes 3x 9.4W 12.1W

Extreme Max Yes 500+100mA Yes 3x 13.7W

4.3.17 Protocols
4.3.17.1 LLDP-MED
The LLDP / LLDP-MED protocol allows information exchange between end devices and adjacent LAN
switches. This mechanism is based on IEEE 802.1AB and ANSI TIA 1057 (LLDP-MED) standards.
8088 Smart DeskPhone sets comply with the LLDP-MED protocol.
By default, LLDP-MED is activated on the 8088 Smart DeskPhone sets and allows:
• Automatic VLAN assignment
• Power over Ethernet negotiation. The LLDP POE negotiation is used at initialization in addition to
802.3af protocol
• Auto discovery geolocalization information
• To send inventory information of terminal to adjacent LAN switch.
Inventory information sent by an 8088 Smart DeskPhone set includes:
• Hardware revision
• Software version
• Firmware version
• Serial number
• Manufacture name (set to ALE International)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 305/382

Chapter 4 SIP deskphones

• Model name
• Asset ID (set with the SIP configuration file to the set MAC address)

4.3.17.2 SNTP
The Simple Network Time Protocol (SNTP) Version 4 is an adaptation of the Network Time Protocol
(NTP) used to synchronize computer clocks in the Internet.
The 8088 Smart DeskPhone set complies with SNTP. An SNTP server provides the universal time
(UTC) to the set at initialization and periodically when in operation.
SNTP allows to provide universal time (UTC) to the set and to avoid the internal clock drift.
The Communication Server can be used as SNTP server.
The SNTP address can be provided to the set through DHCP or can be configured in OmniVista 8770
and sent in configuration files.
Note:
In case of an SNTP server failure:
• The terminal runs with the local clock, based on the oscillator that may lead long term drift
• If the terminal has a hardware reset while the SNTP server is down, at restart the clock is set to the value it had
at the last software reset. In other words, when a hardware reset occurs, and the phone restarts, the Time/Date
is set to an approximate value, enabling certificates to work.

4.3.17.3 DSCP/DiffServ/802.1p
A VLAN number can be configured. This VLAN number is used by all outgoing traffic.
The VLAN identifier can be configured in three different ways (which are mutually exclusive):
• Statically, by using the Settings menu
• Dynamically, by using the AVA mechanism
• Through LLDP/LLDP-MED, if enabled on the terminal
Note:
• VLAN acquisition through LLDP-MED takes precedence over AVA through DHCP.
• Automatic VLAN id distribution via a RADIUS server is also possible, but this is fully transparent to the terminal
(nothing operation requested on the terminal).
802.1Q tagging is enabled when a VLAN id is configured, that is:
• In static mode, a VLAN identifier has been configured via MMI
• In dynamic mode, a VLAN identifier has been received through AVA or LLDP
The DSCP/diffServ protocol allows to differentiate the priority to associate to each traffic type: voice,
video, SIP signaling application and default priority.
The 802.1.p (layer 2 priority) and DSCP/Diffser (layer 3 priority) priority values for SIP and audio traffic
can be configured in the configuration file. If no value is configured, a default value is used.

4.3.18 Bluetooth
4.3.18.1 Overview
The 8088 Smart DeskPhone sets feature Bluetooth® class 3 (1mW) wireless technology. They support
BT2.1 and are BT4.0 ready.
The 8088 Smart DeskPhone sets operate with wireless audio accessory Bluetooth® 2.1 with headset
profile.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 306/382

Chapter 4 SIP deskphones

Optimum audio quality is obtained at up to 3 meters line of sight from the terminal. The range of a
Bluetooth® device class 3 is around 10 meters.

4.3.18.2 Characteristics of the Bluetooth® wireless technology accessory

The audio quality obtained by accessory users depends on the technical characteristics of the
accessory, notably acoustic coupling.
ALE International recommends the use of Bluetooth® 1.2 headsets complying with recommendation
TIA/EIA-810-A - that specifies a minimum TCLw attenuation of 52 dB.
A headset that does not comply with the recommendation generates an unpleasant echo for the
remote party. To obtain technical information on your accessory, please contact your supplier.

4.3.18.3 Safety rules

Using a Bluetooth® wireless accessory may result in perceptible noise for persons with a hearing aid.
Accessories must not be used in areas with warning signs indicating that electrical devices or products
using radio frequencies must be switched off. Such areas commonly include hospitals, areas where
explosive products are stored or handled, and areas where flammable gases or vapors may be
present.
To limit any risk of interference, ALE International recommends that persons with a pacemaker do not
remain in the proximity of the 8088 Smart DeskPhone set when it is connected to a wireless accessory.

4.3.18.4 Enabling the Bluetooth® feature

For security reasons, the Bluetooth® feature can be disabled. This means that the Bluetooth® devices
including the handset cannot be used.
By default, the Bluetooth® feature is enabled on the 8082 My IC Phone set.
To verify the state of the Enable Bluetooth Radio parameter, open the OmniVista 8770.
1. From the Devices application, select the device,
2. Click the Advanced tab.
3. In the parameter list, under the Security subsection, the Enable Bluetooth Radio parameter
checkbox is selected (enabled by default).
4. Click to validate any modifications.

4.3.18.5 Commissioning a Bluetooth® handset

Audio Key

On/Off Hook
Battery Compartment
Handset LED

Figure 4.25: 8082 My IC Phone Bluetooth® handset

4.3.18.5.1 Connecting the battery

The reference of the Bluetooth® handset is: 3MG26109AAAA.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 307/382

Chapter 4 SIP deskphones

Note:
3MG26022AAAA (used with the 8082 My IC Phone set) is not compatible with the 8088 Smart DeskPhone set.
The battery pack is housed in the battery compartment located in the handset.
The battery pack is reloaded when the handset is placed on its socket. A complete battery load
requires 16 hours.
The autonomy of the battery is of 10 hours in conversation and 33 hours in standby.
The handset Led indicates the battery load state (when the handset is on its socket):
• Led off: the battery is loaded
• Led green steady: the battery is loading
4.3.18.5.2 Binding the handset
Before a Bluetooth® handset can be used, it must be bound correctly to the set:
Note:
The Bluetooth® provided with the set has been bound to it before being delivered.
Note:
In hotel or business configuration, binding can be performed during initialization step 5 only.
Caution:
Ensure the battery is fully charged before binding the set.
1. If the Bluetooth® handset is switched on, switch it off
2. On the set, navigate to:
• 8088 Smart DeskPhone: Settings > Device > Bluetooth
• 8068 Premium DeskPhone: Settings > Phone > Bluetooth
3. Press Add device
4. Press Scan
5. On the Bluetooth® handset make a simultaneous long press on the On/Off Hook key and the Audio

key
A sound made of a beep followed by three different tones is audible and the led flashes alternatively
green and orange. The Bluetooth® handset enters in pairing mode for about one minute and then
goes off.
The set searches for Bluetooth® devices, detects and displays their addresses
6. On the set, select the relevant equipment and press Add.
The set prompts to enter the device PIN code
7. Enter the PIN code (0000 by default) and validate your entry
A popup confirms correct installation of the handset. The handset led flashes green or orange
depending on the battery charge.
If an upgrade of the Bluetooth® handset firmware is needed, the set resets. The upgrade takes
place during initialization step 5.
8. Do not hook off while this process is running
4.3.18.5.3 Adjusting the audio level
There are two ways to adjust the audio level:

• On the set with the keys

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 308/382

Chapter 4 SIP deskphones

• On the Bluetooth® handset with the key

Consecutive presses adjust the handset volume (3 levels).
4.3.18.5.4 Activating the mute feature
When the mute feature is enabled your correspondent can no longer hear you.
There are two ways to activate the mute feature:

• On the set with the mute key

• On the Bluetooth® handset with a long press on the key

4.3.18.6 Commissioning a Bluetooth® headset

4.3.18.6.1 Binding the headset
Before a Bluetooth® headset can be used, it must be bound correctly to the set.
Prerequiste: the headset must be in detectable mode (refer to the user documentation supplied with
the headset).
1. On the set, navigate to:
• 8088 Smart DeskPhone: Settings > Device > Bluetooth
• 8068 Premium DeskPhone: Settings > Phone > Bluetooth
2. Press Add device
3. Press Scan
A list of available devices is displayed
4. Press the name of the device of your choice and press Add
The set prompts to enter the device PIN code
5. Enter the PIN code on the keypad of the phone set and press OK to validate your entry
An acknowledgement message and the headset icon are displayed on the set screen.
4.3.18.6.2 Adjusting the audio level
There are two ways to adjust the audio level:

• On the set with the keys

• On the Bluetooth® headset (refer to the user documentation supplied with the set)
Consecutive presses adjust the handset volume.
4.3.18.6.3 Activating the mute feature
When the mute feature is enabled your correspondent can no longer hear you.
There are two ways to activate the mute feature:

• On the set with the mute key

• On the Bluetooth® headset (refer to the user documentation supplied with the set)

4.3.18.7 Removing a Bluetooth® equipment (headset or handset)

1. On the set, navigate to: Settings > Device > Bluetooth
The set displays the bound Bluetooth® equipment.
2. Select the equipment to be removed and press Remove device. Press OK to validate.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 309/382

Chapter 4 SIP deskphones

The equipment is removed and a acknowledgement message is displayed.

4.3.18.8 LED meaning

The two green LEDs are always lit at the same time and the two orange LEDs are always lit at the
same time. Green and orange LEDs are never lit together. They can be considered as one bicolor LED.

Off
unlit

On

Not bound Binding

Green/Orange On charger
unlit
Charging Not charging In range
Orange Orange Not on charger
(continuous) (continuous) Idle Green
(slow blinking)
Bound
Not charging Bat. OK Out of range
Orange
Charging (fast blinking)

Bat. low
In range Out of range In range
Green Orange In comm.
Green
(continuous) (fast blinking) (blinking)
Idle In comm.

Out of range
In range Out of range In range Out of range Orange
Orange Orange Orange Orange (fast blinking)
(slow blinking) (fast blinking) (slow blinking) (fast blinking)

Figure 4.26: Default meaning of LEDs according to set status

Note:
The default meaning of LEDs can be changed using the CSR Software Development Kit (SDK).

4.3.19 Set customization

4.3.19.1 Customization overview
Depending on company needs, 8082 My IC Phone and 8088 Smart DeskPhone sets can be
customized as follows:
• Using the Software Development Kit (SDK) to generate RPM files.
A software release consists of a set of RPM files, which are the basic unit of installation. Some
RPMs are provided by default, others can be specifically created via the Software Development Kit
(SDK) before being added and modified in a customization file generated by the customization
application: My IC Phone Customizer (8082 My IC Phone).
RPM files created by SDK can include:
• Webapps
A webapp is a software application integrated in the set.
• Skins
A skin defines the graphical appearance of the user interface.
Note:
Seven different skins are embedded by default in the set software.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 310/382

Chapter 4 SIP deskphones

• Data files
A data file is a resource, such as an image (used to represent the user for instance) and/or audio
file (used for ringing melody for instance) enabled by specific settings.
Data files must be installed:
• In the /data/resources directory when they are not meant to be visible in the FileManager
webapp
Note:
The /data/resources physical path is aliased: /datarsc in Apache configuration
• In the /data/resources/system directory when they are meant to be visible in the
FileManager webapp
• The definition of user access to applications, features, files and ergonomics
Note:
RPM file creation and operations are detailed in another document. See the Enterprise Business Portal for
more information.
• Using the customization application: My IC Phone Customizer (8082 My IC Phone)
The customization application can integrate specifically created RPM files (including skins, icons,
applications, images and/or audio files) developed with the SDK available for sets.
The customization application generates a project which corresponds to the customization file
deployed and downloaded by the set.
In this project the different configuration settings, determining set behavior and appearance, are
either enabled or disabled for the set.
• Directly on the set by users.
Note:
The extent of user control over customization can be specified in the customization application. Additional data
files located on a USB key can be copied on the phone via the FileManager webapp.

Software Development My IC Phone Customizer

Kit

Additional rpm file(s)

User
interventions

3rd configuration file

All configuration files

Figure 4.27: Overview of customization options

Customization is not mandatory. When implemented, it can include any or all the customization options
detailed above.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 311/382

Chapter 4 SIP deskphones

4.3.19.2 Operations on the My IC Phone Customizer application

4.3.19.2.1 My IC Phone Customizer overview
The 8082 My IC Phone set is configured:
• In the OmniVista 8770 application, for generic parameters (see: Configuration on OmniVista 8770
on page 263)
• In the My IC Phone Customizer application for customization
The My IC Phone Customizer application allows to generate a customization file. This customization
file is an xml file downloaded by the set at startup along with other configuration files (see: Step 3:
configuration file download on page 260) and allows to:
• Define over five hundred 8082 My IC Phone settings, relating to telephone features and GUI
• Define which settings the user/admin can see and/or modify
My IC Phone Customizer uses various inputs to generate an output file which can configure all the sets
corresponding to a given 8082 My IC Phone hardware version. The output file corresponds to a
"project" which is created and edited in My IC Phone Customizer
4.3.19.2.1.1 My IC Phone Customizer inputs
My IC Phone Customizer includes an SQLite database which contains all project data. It provides a link
to the AAPP Factory website. My IC Phone Customizer automatically connects to this site to retrieve
update information and offer for edition.
Caution:
A My IC Phone Customizer must have a valid account on the AAPP factory website, as access requires
authentication.
Possible My IC Phone Customizer inputs are:
• Reference files provided with each software version, corresponding to the existing telephone
software releases. No project can be created without such a file.
• Existing customization files. This input is not mandatory, but a new project can be created from
existing customization files. In case of minor modification needs, this allows to reuse existing
settings, avoiding the long process of creating a file from scratch.
• Existing external rpm files. This input is not mandatory, but rpm files, including webapps or skin
configurations may be used.
• Libraries. Libraries for icons and settings are included in the software by default:
• The default icon library contains all available CSS classes representing icons. It can be
complemented with external rpm files.
• This default settings library is constructed with the settings reference file provided for each
project creation. This library can be updated with an external rpm containing a settings.xml
file. The options included in this settings.xml are clearly distinguished from default settings in
their GUI representation.
4.3.19.2.1.2 My IC Phone Customizer output
The output file is the customization file. It is automatically generated when saving the project, or on
demand by the My IC Phone Customizer user.
The customization file must be uploaded on the OmniVista 8770 server. For more information, see:
Deploying a customization file on page 297.
4.3.19.2.2 Installing the My IC Phone Customizer software
1. Select the interface language and click Next
2. Read and accept the terms of the license and click Next

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 312/382

Chapter 4 SIP deskphones

3. If desired browse to change the software directory or keep the default application location, and click
Next
4. Click Next
5. Decide whether shortcuts to the application must be for the current users or all users and click Next
6. Validate the check box to launch the application and click Finish
4.3.19.2.3 Updating the My IC Phone Customizer software
An icon to the right of the toolbar indicates when software updates or new reference files are available.
Click this icon to open the AAPP Factory Updates status window. Select the tab of your choice to
update reference files or software version.
You can also manually check for updates via the Tools > Check for updates... menu.
4.3.19.2.4 My IC Phone Customizer operations
4.3.19.2.4.1 Creating a project
1. Launch the My IC Phone Customizer software
2. Click the Create project icon
The project information window is displayed

Figure 4.28: Project information window example

3. Enter the requested general project information
4. Cick the Data tab
5. Select a Home directory (mandatory)
6. Enter a name for the Generated XML filename (mandatory). The default name is custom.xml
7. Select the Setting reference file (mandatory) corresponding to your 8082 My IC Phone version. If
the file corresponding to your 8082 My IC Phone version is not available in the list, perform an
update from the AAPP factory web site.
8. If you wish to retrieve settings with their values and rights from an existing customization file, select
this file in the Custom settings (optional) field

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 313/382

Chapter 4 SIP deskphones

9. Add or remove an RPM from the Additional packages list (optional). All selected RPMs will be
extracted, and the related library will be updated with the RPMs content. The following types or rpm
are supported:
• WebApp RPM
• Skin RPM (Partial & Full)
• Data RPM (Screensaver images & melodies)
Note:
At any time after project creation, an RPM can be managed via the Data tab of the Project Properties window,
accessible via the Edition menu.
10.Click OK
This opens the project window
4.3.19.2.4.2 Opening a project
To open a project, click the Open project icon and select the project of your choice.
4.3.19.2.4.3 Modifying a project
GUI presentation
The project configuration window presents the customized settings on the left hand side and reference
view on the right hand side.
Both views can be presented as a list or as a tree: click desired button at the bottom of the view to
modify its presentation.

Figure 4.29: Project contents example for set contact pages

Note:
To view the project in xml format, click the XML Preview icon. This automatically exports the output file.
Enter characters in the applicable fields to filter settings in any of the two lists.
Operations
1. Create or modify views:
Select the view to modify or click New to create a new view. Click Delete to delete the current view.
Add a setting from the reference list to the view to customize by clicking the arrow button.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 314/382

Chapter 4 SIP deskphones

Remove a setting from the current view setting list by clicking the red cross button.
Note:
The current view and the reference view may not be always synchronized. Click the OK button to synchronize.
2. Once all your settings in all your views are set, click OK.
The edition window is displayed

3. Select the Visibility tab to specify access to the setting from the set.
• In the Export column, validate the checkbox to include the corresponding setting to the output
file
• In the Admin and User columns, modify if required the rights to modify this setting.
Note:

• R stands for Read (setting is displayed but cannot be modified)

• W stands for Write (setting is displayed and can be modified)
• 0 stands for no right (setting is not displayed)
Display rights must be less or equal to access rights. As an example, if a setting is defined to be R_R,
display rights cannot be R_RW or RW_R or RW_RW.
4. Select the Edition tab to modify the default value of settings in the list
Note:
When upgrading a file from a previous version, edit all settings to ensure full compliance of setting names with
the new version.
Determine options for the settings of the view
5. Click the View Manager icon to go back to the previous window and modify other views
6. Once all modifications are made, click the Save icon to save your project
4.3.19.2.4.4 Viewing libraries
At any point in time, click the Packages menu and select the library of your choice to view the settings,
icons, and data referenced in the project.
4.3.19.2.4.5 Saving a project
At any point in time, click the Save icon to save your project.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 315/382

Chapter 4 SIP deskphones

4.3.19.2.4.6 Modifying project properties

At any point in time, click the Edition menu and select the Project properties... options.
This displays the project information window, see: Figure 24.
4.3.19.2.4.7 Exporting a project
At any point in time, click the Export icon to generate your customized xml file.
Note:
The exported parameters are not limited to the parameters selected for export in the current view. They
correspond to the parameters selected for export in the All view.

4.3.19.3 Presentation of modifiable settings

4.3.19.3.1 User password change
To allow set users to modify their own password from the set, modify the corresponding configuration
file:
1. On the OpenTouch server, go to /opt/Alcatel-Lucent/oamp/cms/DevicesDeployment/
dmic touch/
Create the file if it does not exist
2. Add the following line in the file before saving it:
<setting id="ChangePassword" override="true" rights="0_RW" value="*****"
/>

where ***** is a free text to emulate an encrypted password, and can be replaced by any other
string of characters
3. On the OmniVista 8770, go to the Devices application
4. In the Optional file URL field of the General tab, enter the path for the dmic touch file
5. Click the validate icon
4.3.19.3.2 Home page customization
Name of the setting: HomepagePreviewMode (boolean).
The home page is the first page displayed after initialization of the terminal. It is the main screen of the
set GUI. It provides access to all installed and enabled webapps.
4.3.19.3.2.1 Standard home page definition
The Standard home page is selected when the HomepagePreviewMode setting is set to false. A
maximum of three pages can be defined. A single page may contain a maximum of twelve buttons.
When more than one page is defined for a home page, a left or right arrow allows to navigate from one
page to the next or previous page.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 316/382

Chapter 4 SIP deskphones

Top bar

Application
buttons

Figure 4.30: Example of standard home page

The position of each button is determined by the HomepageKeys setting.

The format of this setting is a list of identifiers separated by semicolons (;). it may contain a maximum
of thirty-six entries (which corresponds to twelve buttons displayed per page, on three different pages).
An empty entry (;;) denotes an empty position in the corresponding page.
Buttons can either be standard predefined buttons, or additional buttons (created by the customization
manager for a specific purpose, see: Additional buttons on page 318).

table 4.9: Standard buttons available for a home page

Identifier Webapp

DIALER_BTN Communication (Dialpad)

BYNAME_BTN Dial by name

COMMUNICATION_BTN Communication

CONTACT_BTN Address book

WAKEUP_BTN Wake-up

IM_BTN Instant Messaging

FILESMANAGER_BTN Files manager

LOCK_BTN Lock

SETTINGS_BTN Settings

SYNCHRO_BTN PIM Synchronization

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 317/382

Chapter 4 SIP deskphones

The setting HomepageStandardAutoFill (boolean) defines whether software predefined buttons

(Table 6) are included in the home page:
• When set to false, the content of the home page is built with the setting HomepageProgKeys (see:
Additional buttons on page 318)
• When set to true, the predefined buttons not already available in the HomepageProgKeys setting
(see: Additional buttons on page 318) are added to the page, provided the associated webapp is
enabled.
4.3.19.3.2.2 Background picture
Name of the setting: UserBackgroundPicture (string).
The preferred image size is 800x480 pixels to avoid automatic resizing. Recommended image formats
are JPG (smaller size) and PNG. A logo or any other information (such as address, phone number,
etc.) must be part of the image. There is no dedicated area for text entries.
The background image is placed at absolute position 0x0 (left-up corner of the screen). When the
home page preview is selected, the topbar and the application bar partially hide the background image,
unless transparency is enabled on this image.
The background image is loaded at the end of terminal initialization. This means that until this moment,
the background image defined in the selected skin is used. This also implies that the background
image can be provided as part of a skin.
Image files can be installed:
• Locally, as for instance:
/datarsc/backgrounds/Alcatel-Lucent/background.jpg or /datarsc/system/
backgrounds/VirtualHotel/default.jpg
• On a remote server, as for instance:
http://www.myserver.com/backgrounds/1.jpg
4.3.19.3.2.3 Additional buttons
Name of the setting that controls the list of additional buttons: HomepageProgKeys (string).
Additional buttons can be created on any home page, whether Standard or Preview.
An additional button is basically defined by:
• A unique identifier
• An icon (partial CSS class name)
The icon size must be 64x64 pixels (the -64 suffix is automatically added by the software). Icons
can be selected from the embedded icon library or from any additional applications installed on the
terminal.
• A label (in English)
• An action to execute, defined by the following elements:
• Application (webapp) name: webAppName field
• Feature name: action field
• Parameters: arguments field
Example of a button allowing to show the DTMF dialpad when pressing a direct call button (call
to the voice mail for example)
<setting id="D1" value="$DTMF$" override="true"/>

Example of two additional buttons for a hotel environment home page:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 318/382

Chapter 4 SIP deskphones

Note:
The first button defined below launches a call to reception (extension no. 20200) , the second to room service
(extension no. 20400):

[
{
'id' : 'homepage_button1',
'icon' : 'sdk-reception',
'action' : 'call',
'webAppName': 'communication',
'arguments' : '20200',
'label' : 'Reception'
},
{
'id' : 'homepage_button2',
'icon' : 'sdk-roomservice',
'action' : 'call',
'webAppName': 'communication',
'arguments' : '20400',
'label' : 'Room service'
},
]

table 4.10: Possible actions for additional buttons

Definition Process Comments

Application name communica- Initiates a call to the Can be prefixed with a DTMF string
tion, action = call specified destination ( $DTMF$ controlled by the DTMFpat-
and displays in the tern setting) which determines if the
Feature name webAppName:
Communication we- dialpad must be displayed when the
communication
bapp. call is connected.
Parameters arguments: a tele-
phone number

Application name filesmanag- Displays the Filesman-

er, action = category ager webapp at the
specified category page.
Feature name webAppName:
category
Parameters arguments: a cate-
gory name, such as Other, Au-
dio or Picture

Application name contacts, Displays the Contacts The contact identifier must be defined
action = display-card) webapp at the specified by the setting DefaultDirectory-
contact page. Contacts
Feature name webAppName:
display-card
Parameters arguments: a con-
tact identifier

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 319/382

Chapter 4 SIP deskphones

Definition Process Comments

Application name userservi- Programs the specified Routing types are:

ces, action = routing) call routing for incoming
• Immediate forward:
calls
Feature name webAppName: FWD_UNCONDITIONAL
routing • Forward if busy: FWD_ON_BUSY
Parameters arguments: • Forward if no reply:
FWD_ON_NO_REPLY
• Forward if busy or no reply:
FWD_ON_BUSY_OR_NO_REPLY
Destinations can be:
• Associate: DST_ASSOCIATE
• Attendant: DST_ATTENDANT
• Mobile: DST_MOBILE
• Voice mail: DST_VOICE_MAIL
• Phone number: Other

Note:
The format of the argument for call routing is as follows:
If destination is Other then
Format = type;destination;<phone number>;true;type;<phone number>
Else
Format = type;destination;;;type;destination
4.3.19.3.2.4 Language localization
Name of the setting: HomepageProgKeysLocalisation
The labels defined for additional buttons on the home page can be localized in one of the twenty-nine
different languages supported by the terminal.

table 4.11: Available languages for additional button localization

Code Language Code Language

cs Czech nl Dutch

da Danish pl Polish

de German pt Portuguese

el Greek sk Slovak

en English sl Slovenian

es Spanish sv Swedish

et Estonian tr Turkish

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 320/382

Chapter 4 SIP deskphones

Code Language Code Language

fi Finnish ar Arabic

fr French he Hebrew

hu Hungarian ja Japanese

is Icelandic ko Korean

it Italian ru Russian

lt Lithuanian zh-cn Chinese (simplified)

lv Latvian zh-tw Chinese (traditional)

no Norwegian

The format of the setting is as follows:

{
‘code’ : { ‘id’ : ‘string’,
…, ‘id’ : ‘string’ },
‘code’ : { ‘id’ : ‘string’,
…, ‘id’ : ‘string’ },
...
‘code’ : { ‘id’ : ‘string’,
…, ‘id’ : ‘string’ },
}
4.3.19.3.3 Skin customization
Name of the setting: SkinsListChoice (choice)
This setting allows to limit the number of skin choices available to users (via the Settings webapp) and
select between the seven different skins embedded in the set software. These seven skins bear the
names:
• Challenger (default skin) identified as Default
• Aero identified as aero-Default
• GreenUp identified as greenup-Default
• Softer identified as softer-Default
• Harmony identified as harmony-Default
• Pep's identified as peps-Default
• Classic identified as classic-Default
Additional skins may be created using the SDK and added to the SkinsList setting.
In this setting, a skin is defined by an id (directory name where the skin is installed), a name (user-
friendly to be displayed in the Settings webapp) and a flag indicating if this skin is the default skin
(true) or not (false). The format of the setting is the following:

id,name,flag#id,name,flag#...#id,name,flag
4.3.19.3.4 Screensaver customization
The Screensaver webapp is divided into two modules: the screensaver core and the image slideshow.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 321/382

Chapter 4 SIP deskphones

4.3.19.3.4.1 Screensaver core

The core module implements the basic features of a screensaver (start screensaver, stop
screensaver). The start operation consists in showing the webapp specified in the
ScreenSaverListChoice setting.
When additional screensaver webapps are created using the 8082 My IC Phone SDK, they must be
added to the ScreenSaverList setting. This TEXT_CHOICE setting is used internally by the software
to populate the list of values for the ScreenSaverListChoice setting.
In this setting, a skin is defined by an id (directory name where the skin is installed), a name (user-
friendly to be displayed in the Settings webapp) and a flag indicating if this skin is the default skin
(true) or not (false). The format of the setting is the following:

id,name,flag#id,name,flag#...#id,name,flag

The default value is webapp.screensaver.defaultScreensaver which is the image slideshow webapp.

Using the 8082 My IC Phone SDK, it is possible to create a full-screen webapp that can replace the
default screensaver.
The screensaver can be enabled or disabled dynamically (ScreenSaverEnabled setting). If the
screensaver is not desired at all, the corresponding webapp must be disabled
(EnableWebappScreensaver setting). See: Backlight on page 322 for complementary configuration.
The activation delay (i.e. user idle time in seconds) can be configured (ScreenSaverDelay setting,
default value is 300 seconds).
4.3.19.3.4.2 Screensaver slideshow
The slideshow webapp is the default screensaver. It consists in the successive display of a list of
images. The delay (seconds) between each image can be configured (ScreensaverSlideshowDelay
setting, default value: 4).
The slideshow automatically resizes images to fit screen size.
The list of images is defined by the ScreensaverSlideshowList setting.
Set the ScreensaverSlideshowLocked setting to true to prevent modifications from the set (via the
Settings or FileManager webapps).
The images used for a slideshow must abide by the same characteristics as background pictures (see:
Background picture on page 318). They can be located on a remote server (http and https are
supported) and/or installed in the terminal (in /datarsc for instance).
The preferred image size is 800x480 pixels, to avoid automatic resizing. The recommended image
formats are JPG (smaller size) and PNG.
Example of slideshow with two images: the first is located on the terminal (in /datarsc/system/
screensaver/vhotel), the second on a server (www.vhotel.com):
/datarsc/system/screensaver/vhotel/default.jpg;
http://www.vhotel.com/screensaver/season.jpg
4.3.19.3.4.3 Voice mail screensaver
Unread voice mails and messages are presented in the topbar. This topbar is always displayed except
when the screensaver is active, which implies that notifications can be hidden when the set is idle.
The EnableVoicemailScreensaver setting must be used to enable or disable the voice mail
screensaver. This screensaver consists in displaying two dedicated images instead of the usual
screensaver when there are unread voice mails or messages:
4.3.19.3.5 Backlight
The BacklightDelay setting corresponds to the user idle time in seconds before the backlight state
changes from ON to OFF.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 322/382

Chapter 4 SIP deskphones

Backlight intensity can be configured for these two states, with the ScreenSaverBrightnessOn setting
(default value: 31) and ScreenSaverBrightnessOff (default value: 8).
4.3.19.3.6 Contacts
The DefaultDirectoryContacts setting must be used to provision a predefined list of contacts. A
contact is represented by a list of fields separated by commas (,). The field order is as follows:
• Identifier
• Salutation
• FirstName
• LastName
• PhoneNumber
• Preview
• Photo
• Fax
• MobilePhone
• HomePhone
• HomeFax
• IM
• Company
• Job
• Address
• ZIP
• City
• Country
Contacts are separated by a hash sign (#). When a field is not used, it must be left empty (,,). When a
field contains a hash sign or a comma, the backslash sign (\) must be used.
To display the contact in the Contact preview, set the Preview field to 1.
The Photo field can be a URL or a local file. The preferred size is 200x200 pixels, when the terminal is
running in a hotel environment.
4.3.19.3.7 Communication log
The communication log size (outgoing, incoming and missed calls) is set by default to eighty entries.
The ComLogSize setting can be used to reduce or increase this number of entries.
Note:
ALE International recommends to limit this value to the default value.
4.3.19.3.8 Outgoing call process
The NewCallDefaultMethod setting controls the default method used to initiate an outgoing call. When
set to 0, the dialpad is displayed. When set to 1, the keyboard is displayed to facilitate call by name.
4.3.19.3.9 Dialpad display
When the end-user puts the phone off the hook, the default set behavior is to display the dialpad (or the
keyboard for call by name). To display the alphabetical keyboard, set the ShowKeyboardOnHookOff
setting to true.
The ShowPlusButtonOnDialpad setting determines the presence of the button used to indicate an
international phone number (+ sign).
The dialpad also provides an action button. The ActionButtonInDialpad setting controls which action
is available from the dialpad. It can be: None, Dial-by-name or Contacts.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 323/382

Chapter 4 SIP deskphones

4.3.19.3.10 Ringing volume control

The AudioRingLock setting defines whether the user can modify the volume of the ringing melody.
The default value is false (unlocked).
4.3.19.3.11 User photo
The UserPhoto setting specifies the picture displayed in the topbar of the page. The image path can
be a URL or a local file. The preferred size is 64x64 pixels and JPG and PNG formats are supported.
To remove a user photo, add the following lines in the customization file:
<setting id="UserPhoto" define="default" override="true"/>
<setting id="EnableUserPicture" value="false" override="true"/>
4.3.19.3.12 Screen touch sensitive vibrations
The setting HapticEnabled enables the touch sensitive feedback (haptics). The default value is true.
4.3.19.3.13 Webapps
Webapps installed on the terminal can be individually enabled or disabled. The EnableWebapp<name
of the setting> setting is associated to each webapp to control their availability. This setting is
implemented at set initialization, which means that a webapp cannot be enabled or disabled
dynamically.
Note:
The following webapps are always enabled:
• EnableWebappCommunication
• EnableWebappHomepage
• EnableWebappInitialization

4.3.20 Set parameters in a hotel or business configuration

The following tables present the complete list of parameters that can be consulted/modified from the
OmniVista 8770 when sets are used in a hotel or business configuration.
Parameters which cannot be modified are indicated in the table.

4.3.20.1 General tab

table 4.12: General tab

Parameter name Description Default

value
(Id in configuration file)

Device identity (MAC address) Displays the set MAC address (cannot be
modified).

Type Indicates the device type (cannot be modi-

fied).

Comment Free comment.

Directory Number Directory number on the OmniPCX Enterprise

(cannot be modified).

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 324/382

Chapter 4 SIP deskphones

Parameter name Description Default

value
(Id in configuration file)

OXE fqdn FQDN of the OmniPCX Enterprise node (can-

not be modified).

Deployment date Deployment date (cannot be modified).

Deployment status Current status of the set (cannot be modified).

User attributes frame

Last name Last name of the user (can be modified from

an OmniPCX Enterprise configuration tool and
the UUM application, User attributes tab).

First name First name of the user (can be modified from

an OmniPCX Enterprise configuration tool and
the UUM application, User attributes tab).

OXE directory number Directory number on the OmniPCX Enterprise

(cannot be modified).

User ID By default, concatenation of user first name

and last name (can be modified from an Om-
niPCX Enterprise configuration tool and the
UUM application, User attributes tab).

Email address E-mail address of the user (cannot be modi-

fied).

Cost Center Cost Center of the user (can be modified from

an OmniPCX Enterprise configuration tool on-
ly).

OXE mailbox directory number Mailbox directory number of the user (can be
modified from an OmniPCX Enterprise config-
uration tool only).

4.3.20.2 Network tab

table 4.13: Network tab

Parameter name Description Default

value
(Id in configuration file)

DNS frame

DNS1 DNS1 IP address.

(DmEnetcfgDns1)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 325/382

Chapter 4 SIP deskphones

Parameter name Description Default

value
(Id in configuration file)

DNS2 DNS2 IP address.

(DmEnetcfgDns2)

DNS3 DNS3 IP address.

(DmEnetcfgDns3)

HTTP proxy frame

Active True: there is a customer proxy. false

(HTTPProxyActivated)

Host Customer LAN proxy. ""

(HTTPProxyHost)

Port Customer LAN proxy port. 80

(HTTPProxyPort)

Main SIP server frame

Server address Main address of the Communication Server

(cannot be modified).
(SIPServer1Address)

Server port Port number used on the main SIP server 5060
(cannot be modified).
(SIPServer1Port)

Keep alive Time between two Keep Alive SIP OPTIONS 60

messages with the main SIP server.

Secondary SIP server frame

Server address Main address of the second Communication

Server (spatial redundancy).
(SIPServer2Address)

Server port Port number used on the secondary SIP serv- 5060
er (secondary Communication Server).
(SIPServer2Port)

Keep alive Time between two Keep Alive SIP OPTIONS 60

messages with the secondary SIP server.

SIP parameters frame

Domain name Domain name (not modifiable after creation).

(SIPDomainName)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 326/382

Chapter 4 SIP deskphones

Parameter name Description Default

value
(Id in configuration file)

Authentication realm Not modifiable.

(SIPAuthenticationRealm)

Authentication name Not modifiable.

(SIPAuthenticationName)

Authentication password Not modifiable.

(SIPAuthenticationPassword)

Display name Not modifiable.

(SIPDisplayName)

SIP URI SIP URI of the device (not modifiable).

(SIPDeviceUri)

Transport mode SIP transport mode (UDP or TCP). UDP

(SIPSipTransportMode)

DTMF mode DTMF mode: RFC 4733

(SIPDtmfMode) • None
• InBand
• RFC 2833
• RFC 4733
• SIP_INFO

SIP frame

Outbound proxy address Outbound proxy address.

(SIPOutboundProxyAddress)

Outbound proxy port Outbound proxy service port. 5060

(SIPOutboundProxyPort)

Allowed keepalive failure Number of keep alive failures before the link is 5
considered lost.
(SIPKeepAliveFailureTimes)

Register expire time Expiry time on register (in seconds). 3600

(SIPRegisterExpire)

Register retries Register retry time (in seconds). 300

(SIPRegisterRetry)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 327/382

Chapter 4 SIP deskphones

Parameter name Description Default

value
(Id in configuration file)

Local SIP port Local SIP service port. 5060

(SIPLocalSipPort)

Local SIPs port Local SIP security service port. 5061

(SIPLocalSipsPort)

SRTP mode SRTP working mode (SRTP is not available). SRTP dis-
abled
(SIPSrtpWorkingMode)

SRTP authentication SIP SRTP Authentication Mode. Disable

SRTP Au-
(SIPSrtpAuthentication)
thentica-
tion

Local SRTP port Local SRTP port. 30000

(SIPLocalSrtpPort)

Local RTP port Local RTP begin port. 6000

(SIPLocalRtpPort)

802.1 user priority 802.1P User priority for SIP. 5

Maximum calls Maximum number of calls that the phone set 5

can support.
(SIPMaxCall)

Forward duration no reply Time in seconds before the call is forwarded 10

on no reply.
(SIPForwardDurationNoreply)

SIP DSCP field SIP DSCP field in IP header. 40

(SIPDSCP)

AMR-WB OA mode AMR WB codec in OA mode

Preferred vocoders [ ] Preferred vocoder sequence. To add a codec,

right-click, select Add and select the value in
(SIPPreferredVocoder)
the SIPPreferredVocoder field:
• 8 : G.711 A law
• 0: G.711 µ law
• 9: G.722
• 18: G.729AB
• 119: G.722.2

SNTP frame

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 328/382

Chapter 4 SIP deskphones

Parameter name Description Default

value
(Id in configuration file)

SNTP server SNTP server address.

(DmEnetcfgSntp)

Refresh period Refresh period for SNTP. 3600

(DmEnetcfgSntpRefreshPeriod)

Telephony tab

Enable lock Enable/disable the webapp lock. true

(EnableWebappLock)

User frame

Associate phone number Phone number of the associated set (cannot

be modified).
(TelephonyAssociateNumber)

Voice mail phone number Voice mail phone number (cannot be modi-
fied).
(TelephonyVmNumber)

Message waiting indication URI Message waiting indication server address

(FQDN of OmniPCX Enterprise).

Rights frame

Interphony Indicates whether the user has the right to use false
the interphony feature.
(TelephonyInterphonyAllowed)

Direct custom forward Enables a custom call forwarding. true

(AllowDirectCustomForward)

Enable routing Add/remove the routing button. true

(EnableRouting)

Enable voice mail edition Add/remove the voice mail button. true
(EnableVoicemailEdition)

Prefixes frame

Attendant Attendant phone number.

(TelephonyAttendantNumber)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 329/382

Chapter 4 SIP deskphones

Parameter name Description Default

value
(Id in configuration file)

Immediate forward Immediate forward activate SEPLOS code.

(SIPImmediateForwardActivate-
Code)

Immediate forward on busy Immediate forward on busy activate SEPLOS

code.
(SIPImmediateForwardOnBusyActi-
vateCode)

Forward on no reply Forward on no answer activate SEPLOS

code.
(SIPForwardOnNoAnswerActivate-
Code)

Forward on busy or no reply Forward on busy or no answer activate SE-

PLOS code.
(SIPForwardOnBusyOrNoAnswerAc-
tivateCod)

Forward: cancel by destinatation SEPLOS forward deactivate by destination

SEPLOS code.
(SIPSEPLOSForwardDeactivateBy-
DestCode)

Forward cancellation SEPLOS forward deactivate SEPLOS code.

(SIPSEPLOSForwardDeactivate-
Code)

Do not disturb DND activate SEPLOS code.

(SIPDNDActivateCode)

Cancel: Do not disturb DND deactivate SEPLOS code.

(SIPDNDDeactivateCode)

Lock Lock activate SEPLOS code.

(SIPLockActivateCode)

Unlock Lock deactivate SEPLOS code.

(SIPLockDeactivateCode)

Wake-up Wake up activate SEPLOS code.

(SIPWakeupActivateCode)

Cancel wake-up Wake up deactivate SEPLOS code.

(SIPWakeupDeactivateCode)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 330/382

Chapter 4 SIP deskphones

Parameter name Description Default

value
(Id in configuration file)

Emergency numbers frame

1 : number Call number to the emergency button 1.

(EmergencyNumber1)

1 : label Label used for the emergency button 1.

(EmergencyLabel1)

2 : number Call number to the emergency button 2.

(EmergencyNumber2)

2 : label Label used for the emergency button 2.

(EmergencyLabel2)

3 : number Call number to the emergency button 3.

(EmergencyNumber3)

3 : label Label used for the emergency button 3.

(EmergencyLabel3)

Applications tab

Url applicative server URL of non ICS applicative server.

(ApplicativeServerUrl)

Contacts Enables webapp Contacts. true

(EnableWebappContacts)

Contacts preview Enables webapp Contacts's preview. true

(EnableContactsPreview)

Search Enables webapp Search. true

(EnableWebappSearch)

File manager Enables webapp File Manager. true

(EnableWebappFilesManager)

Magnify Enables webapp Magnify. true

(EnableWebappMagnify)

Screensaver Enables webapp Screensaver. true

(EnableWebappScreensaver)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 331/382

Chapter 4 SIP deskphones

Parameter name Description Default

value
(Id in configuration file)

User services Enables webapp Userservices. true

(EnableWebappUserservices)

Voice mail Enables webapp Voicemail. true

(EnableWebappVoicemail)

Wake up Enables webapp Wakeup. true

(EnableWebappWakeup)

4.3.20.3 Device tab

table 4.14: Device tab

Parameter name Description Default

value
(Id in configuration file)

Phone configuration frame

Date format Selection of the date format. DD/MM/

YYYY
(DateFormat)

Time format Time Format: true (24 h)

(TimeFormat) • True: 24 h
• False: 12 h

Language Language used on set display (cannot be 0

modified).
(Language)

Default keyboard Selection of keyboard type: AZERTY

(Defaultkeyboard) • AZERTY
• QWERTY
• QWERTZ

Low level beep Enable low level beep feedback. true

(BeepEnabled)

Audio frame

802.1 Priority PRIORITY: Audio 802.1p priority 5

(Audio8021p)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 332/382

Chapter 4 SIP deskphones

Parameter name Description Default

value
(Id in configuration file)

DiffServ TOS/Diffserv:Field to be included in the IP 46

headers of the RTP/RTCP packets
(Audiodiffserv)

AMR bit rate Rate of AMR WB codec (preferred rate for the AMR BR
caller when initiating an outgoing call). 12D65
(AudioAMRBitRate)

Custom tone Enables to use the five tones defined in the false
settings.
(AudioUseCustomTone)

Noise reduction Enables Noise reduction. false

(AudioNoiseReduction)

Breath reduction Enables breath reduction. false

(AudioBreathReduction)

Beam forming handsfree enhance- Enables beam forming hands free enhance- false
ment ment.
(AudioBeamformingHandsfreeEn-
hance)

Signal reduction Enables to limit voice signal. false

Country Tone Country standard for call progress tone. 0

(AudioToneCountry)

DTMF duration DTMF Duration. Follow

key
(AudioDtmfDuration)

DTMF level Bias value of DTMF tone. 0

(AudioDtmfLevel)

DTMF feedback Enable/disable DTMF feedback. true

(AudioDtmfFeedbackEnable)

VAD Enables/disables audio VAD (Voice Activity false

Detection).
(AudioVad)

RLR handset Handset RLR bias for tuning. 0

(AudioRlrHandset)

SLR handset Handset SLR bias for tuning. 0

(AudioSlrHandset)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 333/382

Chapter 4 SIP deskphones

Parameter name Description Default

value
(Id in configuration file)

Sidetone handset Audio sidetone bias for tuning. 0

(AudioSidetoneHandset)

Enable hearing aid Enables/disables Hearing Aid. false

(AudioHearingAidEnable)

Payload types [ ] Selection of payload type(s).

(AudioPayloadTypes) To add a payload, right-click Payload types [ ]
and select Add
• 101: dtmf pt
• 96: red pt
• 117: amr pt

Packet sizes [ ] Selection of Packet time.

(AudioPacketTime) To add a packet time, right-click Packet sizes
[ ] and select Add.

4.3.20.4 Advanced tab

table 4.15: Advanced tab

Parameter name Description Default

value
(Id in configuration file)

DM Server frame

Binary update time control True: the set carries out a periodic polling to true
check whether binary files have been updated
on the DM server and must be downloaded.

Binary update start time Time at which a check on binary update starts. 11:30

Binary update period (in mn) Period between two binary update checks. 180

Binary update polling timer Polling timer in seconds. 86400

Config update polling True: the set carries out a periodic polling to true
check whether configuration files have been
(CurrentAdmcfgUpdatePollingEna-
updated on the DM server and must be down-
ble)
loaded

Config update polling timer Polling timer in seconds. 86400

(CurrentAdmcfgUpdatePollingTi-
meout)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 334/382

Chapter 4 SIP deskphones

Parameter name Description Default

value
(Id in configuration file)

Timezone Time zone of the set. Etc/

Universal
(DmAdmcfgTimeZone)

Security frame

Administrator password Admin password to access administration me- 0

nus on the set.
(DmAdminPasswd)

PC port Enables/disables the PC port. This option is false

used to prevent daisy chaining of a PC behind
(DmSecucfgPcPort)
a terminal.

VLAN filtering Packets are filtered: false

(DmSecucfgPcPortVlanFilter) • Frames coming from the LAN to the PC:
802.1q tags are removed
• Frames coming from the PC to the LAN:
802.1q tags are replaced by the default
VLAN tag (VLAN=0)
This option ensures that no Voice VLAN traffic
can be sent from illegitimate sources.

SSH Enables SSH connections. false

User name User name (cannot be modified).

User first name User first name (cannot be modified).

Deployment mode • open open

(DmWebappDeploymentMode) • lock
• secure

802.1 authentication mode Select the 802.1x authentication mode: Off

• MD5
• TLS
• MD5_TLS

Enable Bluetooth Radio Selected

LAN SBC for encryption Indicates, where applicable, which is the LAN
SBC used for video encryption

Application frame

Auto answer Authorizes auto answer for incoming calls true

(SIPAutoAnsweredAllowed)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 335/382

Chapter 4 SIP deskphones

Parameter name Description Default

value
(Id in configuration file)

Password for DND DND activation requires a password false

(DndRequiresPassword)

Local Conference Whether local conference is enabled. true

(SIPLocalConfEnable)

Log frame

Syslog Server Link to previously created Syslog Server (if

applicable)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 336/382

 Chapter

5 Additional Key Modules

5.1 Overview
5.1.1 Overview
This document describes the additional key modules (also called add-on modules) that can be used for
programmable keys on Alcatel-Lucent 8/9 series sets.
Additional key modules compatible with Alcatel-Lucent 8/9 series sets are not compatible with Premium
DeskPhone sets.
Similarly additional key modules designed for 80x8 Premium DeskPhone, 80x8s Premium DeskPhone
and 80x9 sets are not compatible with 40x8 and 40x9 sets.
However, the configuration of all additional modules is identical, because it always is a subfeature of
the set itself.
Programmable key can be configured on:
• The personal home page (AOMV)
• F1 and F2 keys
• Physical additional key modules connected to the set (AOM)
Note:
On 8058s Premium DeskPhone sets, the last four softkeys of additional key module are displayed on the last two
lines of the set screen.
Additional key modules can be connected to the following sets:
• Alcatel-Lucent 8 series: Alcatel-Lucent IP Touch 4008 Phone, Alcatel-Lucent IP Touch 4028 Phone,
Alcatel-Lucent IP Touch 4038 Phone and Alcatel-Lucent IP Touch 4068 Phone
• Alcatel-Lucent 9 series: Alcatel-Lucent 4029 Digital Phone and Alcatel-Lucent 4039 Digital Phone
Alcatel-Lucent IP Touch 4018 Phone and Alcatel-Lucent 4019 Digital Phone cannot receive any
additional key module.
8088 Smart DeskPhone do not support additional key modules. They include a virtual key module
available on screen, and equivalent to a Smart Display Module.
There are two types of additional key modules:
• Additional key modules with an electronic icon and paper labels. There are 10-key and 40-key
modules
• Smart Display Module with an electronic icon and label
It is not possible to mix Smart Display Module with 10-key and 40-key module.
Note:
The 10-key module is not supported by the 8078s Premium DeskPhone.

5.1.2 Personal home page key (AOMV)

According to key distribution configuration (see: Modifying the key distribution on page 341), AOMV
allows to configure:
• Up to 72 keys: in this case, a maximum of 50 keys can be configured on additional key modules
• Up to 40 keys: in this case, a maximum of 80 keys (on 40x8 and 80x8 Premium DeskPhone sets) )
and 50 keys (on 40x9 and 80x9 sets) can be configured on additional key modules

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 337/382

Chapter 5 Additional Key Modules

5.1.3 Additional key modules with paper labels

Two models are available:
• 10-key module
• 40-key module

Figure 5.1: 10–Key and 40–Key Modules

Each phone can have a maximum of 50 additional keys.

Possible configurations are:
• One 10-key module
• One 40-key module
• One 40-key module and one 10-key module
• Two 40 key modules (with Alcatel-Lucent 8 series sets and when the configuration allows it)
Additional keys can be used for direct station selection, busy lamp field, additional programmable line
appearance or as function keys.
Icons display the call or function status associated with the programmed key.
Note:
The 60° phone stand and wall-mounted capability are not compatible with the 40-key module.

5.1.4 Smart Display Module

The Smart Display Module provides 14 keys associated to an electronic icon and label.
A large LCD display allows a quick and easy "paperless" identification of associated buttons.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 338/382

Chapter 5 Additional Key Modules

Figure 5.2: Smart Display Module

A set can receive one, two or three Smart Display Module.

The call state or function state is indicated by an icon. When a key contents corresponds to another
user or e.g. call supervision, the label indicates the number of the correspondent (or their name when
possible).
The label is 14 characters long maximum, depending on character sizes.

John Laughan
Oni Carapoulos
Steve Ballmer

Pedro Lamosa

Steve Laughan

Figure 5.3: Example of Display

In this example, 5 keys are managed:

• Key one is a multiline key with a correspondent on hold
• Key two is a multiline with a correspondent in conversation
• Key three and key five are multiline keys supporting incoming calls
• Key seven is a speed dial key

5.1.5 Display mode

According to configuration, when a call is received on a Smart Display Module key, the calling party
name can be displayed on the display next the key.
The figures below show examples of display with and without calling party name on the add-on
module.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 339/382

Chapter 5 Additional Key Modules

Line 1
Line 2
Thu 9 Feb 2006 16:52

1: User1
3001
Calling

Ok Menu

Smart Display

Figure 5.4: Smart Display Module: No Display of Calling Party Name

User 1
Line 2
Thu 9 Feb 2006 16:52

1: User1
3001
Calling

Ok Menu

Smart Display

Figure 5.5: Smart Display Module: Display of Calling Party Name

In the examples above the set is configured with a multiline key (key 1). This key has been assigned a
specific call number.
According to configuration , when User1 calls the set via this specific call number, the Smart Display
Module displays the calling party name. For more information on configuration, see: Configuring the
display mode on page 341.

5.2 Configuration procedure

5.2.1 Overview
This chapter describes how to:
• Modify the display on the Smart Display Module, see: Configuring the display mode on page 341
• Define the distribution between soft keys and additional module keys, see: Modifying the key
distribution on page 341
• Declare additional key modules on a set, see: Declaring additional key modules on page 342

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 340/382

Chapter 5 Additional Key Modules

• Configure keys on a key module, see: Configuring programmable keys on page 342
Errors and incidents are listed: Controls and explicit errors on page 344

5.2.2 Configuring system options

5.2.2.1 Configuring the display mode
As of R9.1, it is possible to select the display mode on Smart Display Module keys.
1. Select System > Others System Param. > System Parameters
2. Review/modify the following attributes

System Option Select: Static Electronic AOM 14 Keys

Static Electronic AOM 14 Keys Select the display mode:

• False: the calling party name is displayed on the Smart
Display Module when a call is received on a Smart
Display Module key (default value)
• True: the name of the key is always displayed whatever
the status of the key
3. Confirm your entries

5.2.2.2 Modifying the key distribution

As of R11.0, it is possible to modify the distribution of keys between the personal home page (AOMV)
and additional modules (AOM).
1. Select System > Others System Param. > Spec. Customer Features Parameters > x89 40 keys
AOMV
2. Review/modify the following attributes:

System Option Select: x89 40 keys AOMV

x89 40 keys AOMV Select the distribution type for keys:

• False (default value): a maximum of 72 keys can be
programmed on the personal home page (AOMV).
A maximum of 50 keys can be programmed on additional
key modules.
• True: a maximum of 40 keys can be programmed on the
personal home page (AOMV).
A maximum of:
• 80 keys can be configured on additional key modules
with Alcatel-Lucent IP Touch 4028/4038/4068 sets
• 50 keys can be configured on additional key modules
with Alcatel-Lucent 4029/4039 Digital Phone sets
3. Confirm your entries
4. If the value for this parameter has changed, reboot the sets for this configuration to be taken into
account
When the x89 40 keys AOMV system option is changed from False to True:
• For all existing sets, if keys 41 to 72 are already configured, an error is generated. These keys must
be deleted manually before enabling the x89 40 keys AOMV system option.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 341/382

Chapter 5 Additional Key Modules

• For all existing sets and according to configured modules, up to 30 keys are created
When the x89 40 keys AOMV system option is changed from True to False:
• For all existing sets, if more than 50 additional module keys are already configured, an error is
generated. These keys must be deleted manually before disabling the system option.
• For all existing sets, 32 keys are added in the range 40-72.
Key range of additional modules are shifted from 43-93 to 75-125
If a remote set is configured as Manager, Assistant or supervising set for an Alcatel-Lucent 8/9 series
set, this option cannot be set to False. These keys must be deleted manually before.

5.2.3 Declaring additional key modules

5.2.3.1 Overview
Additional key modules must be declared in the user's configuration data. This can be done when the
user is being created or by modifying user data. Smart Display Module is managed like other additional
key module.

5.2.3.2 Additional key modules configuration

To declare an additional key module:
1. Select: Users
2. Review/Modify the following attributes:

Directory Number Enter the directory number of the user set

Add On Module 1 Select keyboard type:

• None
• 10 Keys
• 40 Keys
• Electronic 14 Keys (Smart Display Module)

Add On Module 2 Select either:

• None
• 10 Keys
• 40 Keys
• Electronic 14 Keys (Smart Display Module)

Add On Module 3 Select either:

• None
• Electronic 14 Keys (Smart Display Module)
3. Confirm your entries
4. Reboot the set for this configuration to be taken into account

5.2.4 Configuring programmable keys

5.2.4.1 Overview
The keys may be programmed:
• Directly on the set

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 342/382

Chapter 5 Additional Key Modules

• On the PCX
There are several type of keys:
• Personal home page keys:
• F1 and F2 keys
• Additional keys on modules
There are two distributions for key identifiers.
The table below gives the key identifiers according to the distribution:

table 5.1: Key identifiers

X89 40 keys Key type

AOMV
Personal home F1 key F2 key Additional mod-
parameter page keys ule keys
(AOMV keys) (AOM keys)

False 1 to 72 73 74 75 to 125

True 1 to 40 41 42 43 to 123 (forAlca-

tel-Lucent IP
Touch
4028/4038/4068)
43 to 93 (for Alca-
tel-Lucent
4029/4039 Digital
Phone)

The keys are numbered in pairs from left to right, then from top to bottom (except for AOM 10 and
Smart Display Module, which are numbered from top to bottom).

5.2.4.2 Configuring a key directly on the set

Proceed in the same way as for personal keys or Perso Tab keys: see Commissioning 4029/4039
Digital Phone sets - Programming Personal F1/F2 and Perso Tab Keys.

5.2.4.3 Configuring a key on the communication server

To configure a key:
1. Select Users >Progr.Keys
2. Review/Modify the following attributes:

Directory Number Enter the directory number of the user set

Progr.Keys Enter the identifier of the key

Function Select function

Mnemo(Pocket,Mobile,4040,IPTouch) Enter the name to be displayed next to the key on

the LCD display (for keys on the Perso tab or on a
Smart Display Module)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 343/382

Chapter 5 Additional Key Modules

UTF-8 Mnemo ( Alcatel-Lucent 8&9) Enter the name in non-Latin characters to be dis-
played next to the key on the LCD display (for keys
on the Perso tab or on a Smart Display Module)
Note:
You must use the 4760 or 4760i application to enter or
display non- Latin characters for this attribute. Non-Latin
characters are displayed as ??? in mgr.

Locked Select YES to prevent users from modifying the con-

tents of this key from their set
3. Confirm your entries
4. If necessary, complete the other attributes according to the selected function (e.g. for set
supervision, enter the extension number of the set to supervise)
5. Confirm your entries

5.2.5 Controls and explicit errors

• One incident is emitted in case of extension unit loss
• One incident is emitted in case of plugging an extension unit that has not been previously declared
in system administration
• An error message is displayed if the type of the plugged extension unit differs from system
administration
• An error message is displayed when trying to configure a paper label extension unit setting
connected to a Smart Display Module (and vice versa)

5.3 External connections

5.3.1 Overview
This chapter describes how to connect an additional key module on a set.

5.3.2 Prerequisite
The additional key module must be declared in the user's configuration data.

5.3.3 Installation
To connect additional key modules:
1. Remove the rubber tab located on the right side of the set.
2. Plug the RJ45 connector (right hand side) of the additional key module into the RJ45 connector
(bottom) of the set, as shown below.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 344/382

Chapter 5 Additional Key Modules

3. Insert the attachments of the additional key module into the appropriate holes located on the left
hand side of the set.
4. Screw the additional key module to the set.
5. If necessary, repeat the same operations for the next additional key module (up to 3 Smart Display
Module devices can be supported on the same set).
6. Start (or restart) the set.
Note:
If the set is on when you plug in an additional key module, you must restart the set after connection.
Note:
Any exchange of the additional key module requires a reboot of the set to be taken into account.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 345/382

 Chapter

6 DECT handsets

6.1 8212/8232/8242/8262 DECT handsets

6.1.1 Overview
The 8212 DECT, 8232 DECT, 8242 DECT and 8262 DECT handsets offer easy-to-use, cost effective
and reliable voice communication solutions that address the mobility needs of evolving business
environments. 8262 DECT handsets exist in a toughened version: 8262 DECT EX, developed to meet
safety standards for sensitive environments.
These handsets provide a convenient and practical solution for the basic personal mobility needs of
most business environments. They offer simple and efficient voice communications, enhanced usability
and compatibility with the existing base station portfolio from ALE International. They also offer all of
the OmniPCX Enterprise value-added voice services (such as dial-by-name and multi-line
management) that fixed desk phones delivered by ALE International support.
8212 DECT and 8232 DECT sets offer similar menus, but 8232 DECT sets offer more advanced
features, as well as side keys and key backlight.

8212 8232
DECT DECT

Figure 6.1: 8212 DECT/8232 DECT handset

8242 DECT and 8262 DECT sets are very much alike in their appearance, but 8262 DECT sets offer
more advanced features.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 346/382

Chapter 6 DECT handsets

8242 DECT 8262 DECT

Figure 6.2: 8242 DECT/8262 DECT handsets

6.1.2 Key features

The key features for the 8212 DECT/8232 DECT/8242 DECT/8262 DECT sets include:
• GAP protocol
• CAT-iq
• DECT Security (identity, authentication, encryption)
• Lightweight, ergonomic design and intuitive operation
• Color display, Backlight, vibrator
• Speakerphone and mute
• Headset connection
• Bluetooth 3.0 support (8242 DECT/8262 DECT)
• Loudspeaker/mute during call
• Status led (missed calls, Battery status)
• Received messages audio notification
• Headset jack (3.5 mm)

6.1.3 Location
Designed as a high-end business terminal, the 8242 DECT/8262 DECT terminals provide notification
and location capabilities in addition to a one-button alarm function. With these features, the 8242
DECT/8262 DECT terminals meet the needs for hospitality, healthcare and any other professional
environments:
• Triangulation with up to four DECT base stations
• Data transmitted with Notification messages
• External server required

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 347/382

Chapter 6 DECT handsets

• Location Audio signal

6.1.4 Key benefits

The key benefits of these handsets include:
• Infrastructure investment protection (compatibility with deployed base stations delivered by ALE
International)
• IP-DECT connectivity
• Excellent voice quality and business telephony features throughout the workplace contributing to
improved user responsiveness and productivity
• One Worldwide product
• Automatic band switching for cruise ship application
• Green friendly:
• Economy mode with automatic low radio emission power (25 mW)
• Energy StarTM compliant
• Low power mode (50mW) for environments such as nuclear facilities
• Long battery life

6.1.5 Technical Specifications

6.1.5.1 Mechanical characteristics

8212 DECT 8232 DECT 8242 DECT 8262 DECT

Dimensions H*W*D 5,31 x 1,61 x 0.98 5,19 x 2.00 x 0.90 5.59 x 2.00 x 0.90 5,71 x 2,17 x 0,91
in in (132 x 51 x 23 in. (142 x 52 x 23 in. (145.21 x 55.15
mm) mm) x 23.2 mm
(135.3 x 41.9 x 25
mm)

Weight 6.06 oz (172g) 3.88 oz (110g) 4.76 oz (135g) 6.06 oz (172g)

Color Black Black Black Black

Graphic display screen size 1,44' screen size 1,44' screen size 2.4 in. screen size 2.4 in.
(36.5 mm) (36.5 mm) (60,95 mm) (60,95 mm)
resolution 128 x resolution 128 x resolution: 320 x resolution: 320 x
128 pixels 128 pixels 240 pixels 240 pixels
64k colors 65k colors 65k colors 65k colors

Display backlight White White White White

Keypad backlight Blue Blue Blue Blue

Loudspeaker Yes Yes Yes Yes

Mute Yes Yes Yes Yes

Vibrator No Yes Yes Yes

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 348/382

Chapter 6 DECT handsets

8212 DECT 8232 DECT 8242 DECT 8262 DECT

Headset connection 3.5 mm (standard 3.5 mm (standard 3.5 mm (standard 3.5 mm (standard
jack) TRSS com- jack) TRSS com- jack) TRSS com- jack) TRSS com-
pliant pliant pliant pliant

LED status indica- 3 colors; Red/ 3 colors; Red/ 4 colors: Red/ 4 colors: Red/
tion Orange/Green Orange/Green Yellow/Blue/Green Yellow/Blue/Green

Ring tones 6 user selectable 6 user selectable 6 user selectable 6 user selectable
polyphonic with 4 polyphonic with 4 polyphonic with 4 polyphonic with 4
steps volume con- steps volume con- steps volume con- steps volume con-
trol, meeting mode trol, meeting mode trol, meeting mode trol, meeting mode

Belt clip standard clip standard clip standard clip standard clip
swivel (option) swivel (option)

Charger Charging on desk- Charging on desk- Charging on desk- Charging on desk-

top charger or Mi- top charger or Mi- top charger or Mi- top charger or Mi-
cro USB type B cro USB type B cro USB type B cro USB type B
plug plug plug plug

Handset MMI lan- English, French, English, French, English, French, English, French,
guages German, Spanish, German, Spanish, German, Spanish, German, Spanish,
Italian, Dutch, Por- Italian, Dutch, Por- Italian, Dutch, Por- Italian, Dutch, Por-
tuguese, Danish, tuguese, Danish, tuguese, Danish, tuguese, Danish,
Swedish, Norwe- Swedish, Norwe- Swedish, Norwe- Swedish, Norwe-
gian, Finnish, gian, Finnish, gian, Finnish gian, Finnish
Turkish Turkish

System languages Communication Communication Communication Communication

server dependant, server dependant, server dependant, server dependant,
11 languages in 11 languages in 11 languages in 11 languages in
GAP mode GAP mode GAP/CAT-iq mode GAP/CAT-iq mode

6.1.5.2 Power
These sets can be charged on a desktop charger or Micro USB type B plug.
Battery pack:
• Li-Ion, easily replaceable, 1100 mAh
• Talk time: up to 11 hours for the 8212 DECT set, up to 20 hours on all other sets
• Standby time:
• 8212 DECT: up to 113 hours
• 8232 DECT: up to 200 hours
• 8242 DECT/8262 DECT: up to 160 hours
• Charging time: less than 9 hours for the 8212 DECT set, less than 3 hours for all other sets

6.1.5.3 Radio specifications

• DECT
• Frequency range:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 349/382

Chapter 6 DECT handsets

• DECT Europe – 1880-1900 MHz

• DECT 6.0 (NA) – 1920-1930 MHz
• DECT Latam – 1910-1930 MHz
except Brazil 1910-1920 Mhz
• DECT Asia - 1900 MHz – 1906 MHz
• Hand-over: Bearer, Connection HO
• Out of coverage signaling
• Antenna diversity
• Automatic band switching for cruise ship applications (requires IP-DECT)

6.1.5.4 Wireless security

Wireless security is provided for:
• Identity
• Authentication
• Encryption

6.1.5.5 Registration
Registration can support:
• Up to four systems
• Manual selection
• Automatic selection
• Automatic Band switching, cruise ship (requires IP-DECT)

6.1.5.6 Audio codecs

8212 DECT 8232 DECT 8242 DECT 8262 DECT

G726 X X X X

G722 Wide Band Ready X X

6.1.5.7 Features
All AGAP features on the OmniPCX Enterprise are supported:
• Call by name:
• Local and system directory
• Call log (GAP mode/CAT-iq mode):
• All, Answered, Dialed, Missed
Note:
As of R11.2, according to a system option, a long press on the Off Hook green key allows to redial the last
number or to display the outgoing calls list: see [9] DECT - DECT - Configuration procedure - Declaring
system DECT parameters.
• Up to 50 call logs
• Contacts (GAP mode/CAT-iq mode):
• Name, up to four numbers per contact
• Up to 50 contacts without SD card
• Hands-free
• Microphone mute

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 350/382

Chapter 6 DECT handsets

6.1.5.8 Environmental constraints

For all sets:
Operating temperature: -10°C to +45°C, (14 to 113°F) ETS 300 019 part 1-7 class 7.2 (class 7.3 for
8242 DECT/8262 DECT sets)
Storage temperature: -25°C (-13°F) and +55°C (131°F) ETS 300 019 part 1-1 class 1.2
Transportation: ETS 300 019 part 1-2 class 2.3
IP Class: IP40 (EN 60529)

6.1.5.9 Serviceability
For all sets:
• Site survey tool
• Diagnostic mode
• Syslog mode
• Download tool
• SUOTA (Software update over the air),
Note:
This requires IP-DECT

6.1.5.10 Software management tool

Management software includes:
• Download tool
• Flash loader (PC application) - 8232 DECT only
• Parallel FW Update (PFWU tool) - 8242 DECT/8262 DECT only

6.1.6 Regulatory compliances

Requirements or norms 8212 DECT 8232 DECT 8242 DECT 8262 DECT

EU Directive

2014/53/EU (R&TTE) X X X X

2014/35/EU Low Voltage Directive (LVD) X X X X

2014/30/EU Electromagnetic Compatibility X X X X

Directive

2014/35/EU (Eco Design) X

2009/125/EC (Eco design) X X

RoHS 2011/65/EU X X X X

Safety

IEC 60950-1 X X X X

EN 60950-1 X X X X

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 351/382

Chapter 6 DECT handsets

Requirements or norms 8212 DECT 8232 DECT 8242 DECT 8262 DECT

UL 60950-1 X X X X

CAN/CSA-22.2 No 60950-1 X X X X

EMC & Radio

EN 301 489-1 X X X X

EN 301 489-6 X X X X

IEC/EN61000-4-2 X X X
Level3 criteria B

IEC/EN61000-4-3 X X X X
Level3 criteria A

FCC 47CFR part 15 subpart D X X X X

IC RSS-213 X X X X

DECT

EN 301 406 (TBR6) X X X X

CAT-iq 2.0 Audio Specification 1.18 X X

EN 300 175-8 (DECT audio) X X

TBR22 X X

ETSI TS 102 841 (security) X X

DECT security certification program stepA X X

DECT security certification program stepB X X

Bluetooth : (Q4 2014) Headset profile

V3.0

EN 301 489-17 X X

EN 300 328 Radio X X

RF AS/NZS4268 X X

FCC part15-C X X

RSS-210 X X

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 352/382

Chapter 6 DECT handsets

Requirements or norms 8212 DECT 8232 DECT 8242 DECT 8262 DECT

SAR

EN 50360 X X X

EN 50361 X

FCC OET Bulletin 65 X X

SAR value: 0,102W/kg X

IEE 1528 X X X X

RSS-102 X X X

Audio, Hearing Aid

47CFR Part 68 X X X X

Canada CS-03 X X X X

ANSI/TIA/EIA-504 X X

Australia: ACIF S040 X X

Telecom

EN 301 406 (TBR6) X X X

FCC 47CFR part 15 subpart D X X

IC RSS-213 X X

EN 300 176-2 (TBR10) X X

EN 300 175-8 (DECT audio) X X

ETS 300 245-2 X X

TBR22 X X

ETSI TS 102 841 (security) X X

ES 202 738 (Group listening) X X

Local regulations

Australia: ACIF S004 X X X X

USA/Canada: FCC 47 part 68 X X X X

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 353/382

Chapter 6 DECT handsets

Requirements or norms 8212 DECT 8232 DECT 8242 DECT 8262 DECT

New Zealand: PTC200 X X X

Acoustic shocks

UL 1950, ETS 300 245-2 X X

UL 60950-1 Annex NAD X X

EG 202 518 X X

6.1.7 Accessories
The available accessories include:
• Desktop charger: Charges one handset (with USB cable)
• Power supply: Europe AR, US, UK, Australia plugs
• Spare battery
• Spare belt clip
• Swivel clip
• Vertical pouch
• Horizontal pouch
• Download tool
• Wired headset
• Bluetooth headset (up to four audio devices) - 8242 DECT/8262 DECT sets

6.2 500 DECT handset

6.2.1 Hardware description
6.2.1.1 Overview
The 500 DECT just as the other DECT handsets, is particularly useful for users moving within the
workplace.
The 500 DECT offers:
• Access to most of the added value Alcatel-Lucent OmniPCX Enterprise Communication Server
telephone features.
• Enhanced usability with:
• Robust design with inductive charging
• IP 54 compliance (water and dust resistant)
• DECT handset for PWI (alarm button, man down alarm, no movement detector, shock detector)
• Improved ergonomics
• Integrated bi-antenna
• Backlight display
• Improved quality of audio reception
• Vibrating feature
• MWI (Message Waiting Indication)
• Good autonomy (Li-Ion technology)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 354/382

Chapter 6 DECT handsets

• Belt clip
The 500 DECT operates with Standard GAP
The 500 DECT offers:
• A large clear screen accepting images, icons and text
• A simplified functional organization that allows the user to quickly access each of the mobile's
functions
All main operations can be performed on the mobile by use of a single key for navigation (four
directions) and confirmation.
You can take advantage of special DECT features, such as:
• "Roaming", which allows the user to receive or make a call no matter where he/she is relating to the
base station radio coverage zone
• Change of the transmission channel on the base station to portable link during a conversation due
to a change in propagation conditions
• "No-break transfer" from one base station to another when moving during a conversation. This shift
is completely transparent for the user
The set implements specific DECT features, such as:
• Continuous evaluation of different base station levels in order to select the most appropriate base
station for call setup
• Selection of radio transmission channel during call setup
• Continuous listening for paging messages, transmitted by all base stations, when an incoming call
arrives. The set establishes a radio communication with the most appropriate base station (as it
does for an outgoing call)
• Support of the alarm feature, allowing isolated workers to be located with specific alarm server
Note:
When the 500 DECT is switched off, date and time information is lost.

6.2.1.2 Physical Characteristics

Features 500 DECT

Loudspeaker Yes

Multiline management Yes

Dial-by-name Yes (only local directory)

Headset connection Yes

(standard wiring)

Backlight display Yes

Backlight Keypad Yes

Vibrator Yes

Navigation/confirm dual-function key Yes

Battery pack Yes

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 355/382

Chapter 6 DECT handsets

Features 500 DECT

Color Black

Explosion proof No

Belt clip Yes

Talk time Up to 8 hours

Standby time Up to 100 hours

Charging time Less than 6 hours

6.2.1.2.1 Environmental Constraints

Storage, transportation and DECT Reflexes environment comply with the following standards:
• ETS 300 019 1.1, Storage, Class 1.2: Weather protected, Not temperature controlled locations
• ETS 300 019 1.2, Transportation, Class 2.3: Public transportation
• ETS 300 019 1.3, In Use, Class 7.2: Portable use, Partly Temperature controlled locations
6.2.1.2.1.1 Operation
• Temperature: to achieve optimum reliability, the ambient temperature must be between -10°C and
+45°C.
• Relative humidity: relative humidity must be between 5% and 95% (without condensation)
6.2.1.2.1.2 Storage
• Temperature: temperature must be between -25°C and +55°C
• Relative humidity: relative humidity must be between 10% and 100% (without condensation)

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 356/382

Chapter 6 DECT handsets

6.2.1.3 Description of a Set

Figure 6.3: 500 DECT Presentation

This set provides:

1. A colored LED indicator:
• This LED indicator can be customized by the user and can indicate any of the following:
• Missed call
• Man down
• Low battery
• Alarms, etc...
• The available colors are:
• Red
• Green
• Orange
2. Display screen with status and call icon
3. Volume adjustment keys
4. Alarm Call

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 357/382

Chapter 6 DECT handsets

5. Call management Key (softkey)

6. Answer the call
7. Headset socket
8. Back light screen: the screen switches automatically after a few seconds of inactivity
9. Navigation/confirm dual-function key
10.Call management key (softkey)
11.Call management key
12.Silent mode key
13.Microphone

6.2.1.4 Keypad
6.2.1.4.1 Main keys

KEY USE

Allows to
• Activate/deactivate the loudspeaker
• Redial from the call log
• Lock/unlock the keypad

Allows to select a function in the Menu and provides access to all available
functions:
• Personal directory
• Call log
• Handset settings menu

Erase a character

Allows to:
• Validate an action
• Access to shortcuts for navigation
• Activate/deactivate the loudspeaker
• Access the personal directory
• Switch the screen back on
Note:
the four navigator keys are programmable.

Allows to:
• Answer an incoming call
• Start a call
• Switch between two calls (broker call)

Allows to:
• Switch the set on/off
• Hang up
• Return to first screen/to previous menu
• Switch off ringer

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 358/382

Chapter 6 DECT handsets

KEY USE

Silent mode (long pressing)

6.2.1.4.2 Call Icon Display

ICON USE ICON STATUS

Incoming call Icon displayed: Indicates an incoming call.

Outgoing call Icon displayed: Indicates an outgoing call.

Loudspeaker ac- Icon displayed: Indicates the loudspeaker activation.

tivated

Silent mode acti- Icon displayed: Indicates the silent mode activation (loudspeaker off)
vated

Silent micro- Icon displayed: Indicates that the microphone is muted.

phone activated

6.2.1.4.3 Status Icon

ICON USE ICON STATUS

Battery fully charged (75% - 100%)

Battery Battery half charged (33% - 75%)
Status Indi-
cator Low battery (0% - 33%)

Battery completely discharged (0%)

Icon displayed: Indicates the presence of unread text messages.

New text
Message Note:
Text messages are not supported on IBS/RBS

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 359/382

Chapter 6 DECT handsets

New fil- Icon displayed: Indicates the presence of filtered calls.

tered mes-
sage

Icon displayed: Indicates the silent mode activation.

Silent
mode acti-
vated

Radio re- Indicates the received radio signal level.

ception in-
dicator

Icon displayed: Indicates that an appointments reminder is programmed.

Appointe-
ment re-
minder

icon displayed: Indicates the keypad is locked.

Keylock ac-
tivation

icon displayed: Indicates a missed incoming call.

Missed call

6.3 Ascom 9d24 handset

6.3.1 Overview
6.3.1.1 Overview
From R5.1.1, Ascom 9d24 mobiles, like other DECT mobiles, are intended to be carried by a user
moving around within the company and to offer OmniPCX Enterprise telephone features. Depending on
the system in which they are installed, Ascom 9d24 mobiles can operate in GAP or AGAP (GAP+ in
system configuration) mode.
Ascom 9d24 mobiles offer:
• A large and clear screen with icons and text.
• A back-lit display and keys, allowing the mobile to be used in poor lighting conditions.
• A simplified functional organization, that allows the user to quickly access each of the mobile's
functions.
• Access to all the main operations available on the mobile from a single key.
• Alarm sending on voluntary or automatic call (adapted AGAP mode only).
• The capability to make calls when the mobile is placed on its charging base.
The user can also benefits from specific DECT features, such as:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 360/382

Chapter 6 DECT handsets

• "Roaming", allowing the user to make or receive calls no matter where he/she is in the base station
radio coverage zone.
• Change of transmission channel on the base station to mobile link during conversation due to a
change in propagation conditions.
• "No-break transfer" from one base station to another when moving during conversation. This
transfer is completely transparent for the user.

6.3.2 Detailed description

6.3.2.1 Overview
This module gives the characteristics of the mobile and a description of the keys, icons, etc. available
on the mobile. This module is provided to complement the mobile user manual (issued by Ascom). It
describes how to use some of the keys and icons available on the mobile when the mobile is operating
in adapted AGAP mode (GAP+ in system configuration).

6.3.2.2 Mobile characteristics

The Ascom 9d24 range of mobiles includes two models, the 9d24 Messenger and 9d24 Protector. The
difference between these two models is that the 9d24 Protector mobile also provides alarm functions.
Both models have the following characteristics:

Functions Ascom 9d24

Large LCD screen 128 x 64

Back-lit Screen and keypad

Buzzer Yes

Headset jack Yes (*)

Loudspeaker Yes

SIM card with pho- Yes

nebook

Battery Ni-MH

Dimensions (mm) 134x60x127

Weight (g) 140

(*): Optional.
Ascom 9d24 mobiles have a range of specially designed accessories including headsets, chargers,
etc. For more information, refer to the Ascom brochure.
Note:
In order to use adapted AGAP mode (GAP+ in system configuration), Ascom 9d24 mobiles must be version v2.16
or higher.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 361/382

Chapter 6 DECT handsets

6.3.2.3 Description of the mobile

6.3.2.3.1 General view
2
1

4
4

6
7

The mobile has:

1. An alarm button
2. A headset jack on the rear face (optional)
3. A LED
4. Settings keys for the mobile and the alarm
5. A clock, icons (status and communication), and text menus
6. Dynamic function keys
7. Fixed function keys
8. A keypad with 12 keys (with letters)
9. A microphone
6.3.2.3.2 Description of the mobile's keys

The functions of the keys presented below are for an Ascom 9d24 mobile operating in
adapted AGAP mode. The functions of these keys may differ from those described in the
mobile user manual.

6.3.2.3.2.1 Fixed function keys

The function(s) of these keys are always the same, whatever the status of the mobile (idle or in
communication).

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 362/382

Chapter 6 DECT handsets

KEY USE

Single press: to seize or release the line (make a call or

ring off).

Long press: to redial the last number (redial).

Long press (mobile off): to switch the mobile on.

Single press (mobile idle): to access the OmniPCX En-

terprise “Services” menu.

Long press (mobile idle): to access the mobile's local (in-

ternal) menu.

Up cursor: to move upwards in the menu proposed.

Left cursor: to return to the previous screen.

Right cursor: to go to the next screen.

Down cursor: to move downwards in the menu pro-

posed.

6.3.2.3.2.2 Dynamic function keys

The functions of these dynamic keys differ depending on the status of the mobile.
Mobile idle: the functions of these keys are defined by the OmniPCX Enterprise.
Mobile active: the functions of these keys depend on the action in progress.
Note:
A text label is displayed on the screen above each key to identify it.

Valid Single press: to validate selection in a menu or the func-

tion proposed.

Single or long press: to access the "voice mail" function

Message to consult any message left on absence (voice messag-
es, text messages, alarm messages, Call Back, fax, list
of internal and external calls).

Single press: to access the "Dial by name" function.

Ph.Book
Long press: to access the "Personal phonebook” func-
tion.

Note:
In the rest of this document, these keys will always be accompanied by the name indicating their function (as
presented in the table above) in order to identify them.
6.3.2.3.2.3 Variable ("soft") function keys
The key described below is not dedicated, i.e. is not used for one type of operation only, but is also
used as a dialing keypad key (in edit mode).

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 363/382

Chapter 6 DECT handsets

KEY USE

Single press: to dial.

0
Long press: to switch the mobile off.

Single press: to dial.

Long press: to activate a programmable key when it is

combined with any keypad key (0 to 9).

Single press: to dial.

Long press: to switch to DTMF.

6.3.2.3.3 Description of the status and communication icons

The following list of status and communication icons is not an exhaustive list. It only lists
icons displayed on the mobile screen as covered in the description of phone features in the
Operation on page 365.
Refer to the mobile user manual for a complete list of icons.

6.3.2.3.3.1 Status icons

ICON USE

Battery status indicator. The different states of this icon indi-

cate the battery charge level.
Note:
When icon status changes, a text message is displayed and a
reminder beep is emitted.

Radio reception indicator. The different states of this icon in-

dicate whether radio reception is good or bad, or that the mo-
bile is outside the radio coverage area.

6.3.2.3.3.2 Communication icons

ICON USE ICON STATUS

Mobile status in- Icon displayed: indicates that the mobile is

dicator calling or that a service or function is be-
ing accessed.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 364/382

Chapter 6 DECT handsets

Voice mail acti- Icon displayed: indicates that there are un-
vation indicator acknowledged or unread voice or text
messages (voice mail), or unanswered
calls.
Note:
The icon flashes to indicate that new
messages have arrived and the number
displayed behind the icon indicates the number
of new messages.

Phonebook ac- Icon displayed: indicates that the personal

cess indicator phonebook is being accessed.

6.3.2.4 Special features of the mobile

The Ascom 9d24 mobile can operate:
• In authentication mode (see the Security in DECT - Overview).
• In a Multi-PARI system (see the Multi-PARI DECT - Detailed description).
The Ascom 9d24 mobile can perform external handover between two ACTs with different PARIs.
Note:
For more information, refer to the Notification server - Overview.

6.3.3 Operation
6.3.3.1 Overview
This module only deals with or describes the services (menus and functions) available with the Ascom
9d24 mobile in adapted AGAP mode. The procedure for use of some of these services is also
described as it is not described in the mobile user manual.
This module should be considered as a mini user manual complementing that issued by Ascom.

Services Function Section

Default Allow mobile operating mode to be See Default services

configured (settings, installation, etc.) on page 365

Ad- Allow certain advanced Alcatel-Lucent See Advanced serv-

vanced PCX phone functions to be performed ices on page 366

Alarm Allow an alarm to be generated on See Alarm services

voluntary or automatic call on page 374

The following sections do not cover standard use of the Ascom 9d24 mobile, i.e. call setup,
features available during a call, etc. These operations are described in the mobile user
manual.

6.3.3.2 Default services

Default services can be accessed from the Ascom 9d24 mobile local menu (with the mobile idle).
These include:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 365/382

Chapter 6 DECT handsets

Ring signals

Volume
Normal Vibrator

Modes In charger Key beep

Mode 2, 3..9 Alarm settings

Manual absent

Answer
Local menu Name

Alert signals

Alarm settings
Clock
Settings Hot key
Auto key lock
General
Quick answer
System
Owner ID

An Ascom 9d24 mobile operating in adapted AGAP mode cannot be used to access all de-
fault services and functions. Only two services can be accessed: “Modes” and “Settings”.
This is also the case for the “General” function, that only proposes the 4 options listed in
the figure above.

Information on using these services (access, navigation, operation, etc.) is provided in the mobile user
manual.

6.3.3.3 Advanced services

The advanced services (menus and functions) offered by the Ascom 9d24 mobile are:

Services Section

“Dial by name” See Dial by name on page 367

“Personal phonebook” See Personal phonebook on

page 367

“Services” menu with consulta- See “Services” menu on page

tion/programming of the personal 368
phonebook, secret code (pass-
word), language, etc.

“Redial last number” See Redial last number on page

372

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 366/382

Chapter 6 DECT handsets

Services Section

“Voice mail” See Voice mail on page 372

6.3.3.3.1 Dial by name

Ph.Book
With the mobile idle, make a single press on the key to access the “Dial by name” function.
15 : 37

Select the search option:

Display 1 Name=1 Initia=2 - Press 1 to search by name
- Press 2 to search by the correspondent's initials
ABC

Ph.Book Message Valider

15 : 37 Enter the first two digits or initials (first name, then last
name) or your correspondent
Display 2 Name : Sm_ To erase a digit, press
Valid
Ph.Book Message Valid Press to confirm your selection

15 : 37

This is displayed when the search yields too many answers

Display 3
Over 48 answers Valid
Press .
Ph.Book Message Valid

15 : 37
To show the different answers, press
Display 4 Valid
Smith John Once the desired name is displayed, press to call
your correspondent
Ph.Book Message Valid

6.3.3.3.2 Personal phonebook

Ph.Book
With the mobile idle, make a long press on the key to access the “Personal phonebook”
function. This function allows the list of persons in the phonebook to be consulted (name and phone
number) and a person to be called if desired.
15 : 37 Select one of the twelve entries of the set's phone book.

Smith Either press or a number key

Valid
Ph.Book Message Valid Press to start the call

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 367/382

Chapter 6 DECT handsets

To exit the personal phonebook without making a call, press the key again (single press).
Note:
Phonebook entry programming is described in Phonebook on page 370.
6.3.3.3.3 “Services” menu

With the mobile idle, make a single press on the key to access the “Services” menu.
The “Services” menu includes the following submenus:

Menu Services Consul=1 key=1

call=2

pref=3

suff=4

Who=2

Prog=3 key=1

repert=2

passwd=3

assoc=4

oflw=5

Lang=4

Test=5

The first submenu Consul=1 is accessed by pressing the key again. To navigate through these
submenus, use:

• The key to browse up or down in a submenu.

Valid
• The key to select the submenu or to access the next submenu.
6.3.3.3.3.1 Consultation
Keys
The content of the fixed and programmable function keys is displayed. The display shows:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 368/382

Chapter 6 DECT handsets

15 : 37
Press the desired key to display its use. This applies to the keys:
Select a key Message
Ph.Book
(short or long press)
Ph.Book Message Valid (long press)
* (long press)

# (long press) + key 0 to 9

Call
The list of attendant and external call prefixes is displayed. To browse this list, use:

• The key to move up or down.

Valid
• The key to select a call or attendant prefix.
Valid
When the prefix is displayed, it can be activated by pressing the key again.
Prefixes/Suffixes
The list of prefixes or suffixes available for the mobile is displayed. To browse this list, use:

• The key to move up or down.

Valid
• The key to select a prefix or a suffix.
Valid
When the prefix is displayed, it can be activated by pressing the key again.
Note:
A suffix cannot be activated from this menu.
6.3.3.3.3.2 Identity
The mobile's directory name and number are displayed. The display shows:
Example:

15 : 37

Display 1 Smith John Name of the correspondent

Ph.Book Message Valid

15 : 37

To display the number associated, press

Display 2 <76230

Ph.Book Message Valid

6.3.3.3.3.3 Programming
Keys
This submenu allows a function to be programmed on any of the mobile's 10 programmable keys. The
display shows:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 369/382

Chapter 6 DECT handsets

15 : 37 Select one of the keys. Press # followed by the

desired key number
Select a Key Select the desired data type: number, prefix or suffix
Enter the desired number or select the desired function (if a
Ph.Book Message Valid prefix or suffix has been selected
Valid
Press to confirm. The screen shows the chosen
function.

Caution:
Remember that keys 6 to 9 are reserved for the alarm functions described in Overview on page 374. They
cannot be used for any other function.
Note:
The list of prefixes and suffixes can first be consulted as described in Prefixes/Suffixes on page 369.
Phonebook
This submenu allows the mobile's personal phonebook to be configured. The display shows the first of
the twelve phonebook positions:
15 : 37

Display 1 Empty 01/12 > Select one of the 12 entries with the key

Ph.Book Message Valid

15 : 37 Enter the name with the keypad

Display 2 Du_ 01/12 > To erase a digit, press

Valid
Ph.Book Message Valid Press to confirm your choice

15 : 37
Dial the number related to the chosen
name
Display 3 Please dial :
Valid
Ph.Book Valid
Press to confirm your choice
Message

Password
This submenu allows the password for the mobile to be modified. The display shows:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 370/382

Chapter 6 DECT handsets

15 : 37

Valid
Display 1 Old password : Dial your former password. Press to confirm

Ph.Book Message Valid

15 : 37
Dial your new password twice
Valid
Display 2 New password : Press to confirm
Ph.Book Message Valid

15 : 37

Display 3 For checking :

Ph.Book Message Valid

15 : 37

Display 4 Modification ok Your new password is now recorded

Ph.Book Message Valid

Associated set
The associated set (internal set, voice mail, etc.) number is displayed. If no number has been
programmed, the display shows:
15 : 37

Assoc undefined

Ph.Book Message Valid

Valid
To enter (or modify) the associated set number, directly dial its number and press to validate.
Overflow
The overflow set number is displayed. If no number has been programmed, the display shows:
15 : 37

Ovflw undefined

Ph.Book Message Valid

Valid
To enter (or modify) the overflow set number, directly dial its number and press to validate.
6.3.3.3.3.4 Language
The list of languages available for the set is displayed. To browse this list, use:

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 371/382

Chapter 6 DECT handsets

• The key to move up or down.

Valid
• The key to validate your selection.
6.3.3.3.3.5 Test
To test the mobile's display only.
15 : 37

Display 1 Selftest mode

Ph.Book Message Valid

15 : 37

Display 2 ****************
Ph.Book Message Valid

The display returns to idle status when a timeout elapses.

6.3.3.3.4 Redial last number

From the mobile's welcome screen (with the mobile idle), press the key (long press) to redial the
last number dialed.
6.3.3.3.5 Voice mail
Message
From the mobile's welcome screen (with the mobile idle), press the key to access voice mail.
If there are new messages, the LED flashes and the display shows:
3 15 : 37

03 new Msg >

Ph.Book Message Valid

Valid
Then, press the key to access the main menu. This menu offers the following options:
• Consult voice messages
• Consult text messages and/or alarm messages1.
• Consult Call Backs, faxes and/or internal and external unanswered calls1.
• Send text messages.
To browse the menu, use:

• The key to move up or down.

1 The number of messages is indicated.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 372/382

Chapter 6 DECT handsets

Valid
• The key to select the desired submenu.
6.3.3.3.5.1 Listening to voice messages
The system connects the mobile to its voice mail box to listen to new voice messages.
6.3.3.3.5.2 Reading text messages or alarm messages
The list of text messages and/or alarm messages is displayed. To browse this list, use:

• The key to move up or down.

Valid
• The key to validate your selection.
The display shows:
Example:
3 15 : 37

Press several times to display in turn: the name of the

Display 1 Smith John > text message sender, the incident (alarm), the date and time
of reception, and the message content
Ph.Book Message Valid

3 15 : 37
Valid
Press to call the text message sender or
Display 4 Call me back > acknowledge the incident

Ph.Book Message Valid

Note:
Alarm message reception date and time may not be displayed on the set. Display of alarm message reception date
and time is governed by a system setting.
6.3.3.3.5.3 Consulting Call backs, faxes or unanswered calls
The list of Call backs, faxes or unanswered calls is displayed. To browse this list, use:

• The key to move up or down.

Valid
• The key to validate your selection.
After validating, the display shows the content of the selected message.
6.3.3.3.5.4 Sending text messages

In the main menu, press . The display shows:

Valid
3 15 : 37 Press and enter the correspondent's number.
You can send:
Send text > - A fixed message
- A message to complete
Ph.Book Message Valid - A free message

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 373/382

Chapter 6 DECT handsets

6.3.3.4 Alarm services

6.3.3.4.1 Overview
The Ascom 9d24 mobile includes alarm functions allowing the user to call an emergency number when
working in a hazardous environment. The alarm functions available to the user to trigger an emergency
call from his mobile are:
• Voluntary alarm: the alarm is triggered when the user voluntarily presses a dedicated button.
• Loss of mobility: the alarm is triggered if the mobile has not moved after a certain delay.
• Loss of verticality: the alarm is triggered if the mobile is is not maintained vertical.
• Loss of connection: the alarm is triggered if the physical link between the user and the mobile is
broken.
When the alarm is triggered from the mobile, a preprogrammed emergency number is called. If the
mobile is idle, the preprogrammed number is called immediately when the alarm is triggered. If the
mobile is not idle, the current action (communication, mobile programming, etc.) is first interrupted.
Then, as soon as the mobile returns to idle (less than 10s), it automatically triggers the call to the
preprogrammed number.
Depending on system configuration, the call to the preprogrammed number may be directly transmitted
to its destination or undergo special processing by an alarm server.
6.3.3.4.2 Equipment required
To use the alarm functions, the following items are required:
• An Ascom 9d24 Protector mobile (version v2.16 or higher) running in adapted AGAP mode.
• An alarm server, for example OpenTouch® Notification Service
6.3.3.4.3 Use
The alarm functions proposed to the user can be activated from the mobile's local menu except for the
first function (voluntary alarm), that is always available to the user. The emergency number and alarm
settings (timeout, etc.) are programmed in the mobile's SIM card phonebook.
An alarm test function allowing correct operation to be checked is available to the user.

Detailed information on these alarm functions and their use is provided in the mobile user
manual.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 374/382

 Chapter

7 Generic GAP sets

7.1 General
As the GAP protocol allows the use of handsets from different manufacturers, several types of
handsets are likely to be used. However it is possible to list the essential and optional features for all
these handsets. The following figure illustrates a possible GAP handset.

M BI
P F S

1 2 3
4 5 6
7 8 9

* 0 #
R

Figure 7.1: GAP handset

The mandatory functions are:

Off-hook / On-hook.

12 key number keypad.

R register recall key.
M
F Q23 numbering.
the pause function is not compulsory.
P Numbering pause (used to wait for the dial tone in case of bundle seize for example, this
resulting in the inhibition of the end of numbering timer).
In addition to these last keys, the handset can include, for example:
• a display,
• a redial key.
10 function keys, programmable by the administrator, can be activated on the handset.
Example:
To activate the programmable key "0", the administrator enters the following sequence on the keypad
R then 0 . It is therefore possible to program pseudo multi-line keys for a GAP set.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 375/382

Chapter 7 Generic GAP sets

7.2 Operation remarks

The GAP sets do not have a service level equivalent to that of the DECT 4074 sets. This is partly due
to the fact that they do not have dynamic function keys and they do not always have a display. Thus all
the functions requiring specific or alphabetic keys will not be available on a GAP set.
A GAP set will not be able to:
• be multi-line,
• use the call by name function,
• send SMS,
• have a manager/assistant function.
A GAP set can access all the services provided to an analog set without LED, i.e. accessible by
numbering.

7.3 Compatibility
RBS 2G and IBS base stations are GAP compatible.
All ALE International proprietary DECT handsets are GAP compatible

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 376/382

 Chapter

8 OT Connection for 8082

8.1 Overview
As of R11. 0, OpenTouch Connection for 8082 My IC Phone is a physical phone set that operates with
the OmniPCX Enterprise.
For readability purposes, OpenTouch Connection for 8082 My IC Phone is called OT Connection for
8082 in the rest of the document.
Note:
OT Connection for 8082 is also compatible with R10.1.1, provided the OmniPCX Enterprise version is at least
J2.603.26.
This physical set can also be used as advanced phone set for OpenTouch systems and as advanced
set in a hospitality configuration for the OmniPCX Enterprise. For more information, see: 8082 My IC
Phone/8088 Smart DeskPhone (SIP deskphones) on page 256.

Figure 8.1: OT Connection for 8082 appearance

OT Connection for 8082 emulates the behavior and most of the features of the Alcatel-Lucent IP Touch
4068 Phone business set.
See the OmniPCX Enterprise feature list for a full list of the features available on OT Connection for
8082.
The operating system, as well as the IP layer used by OT Connection for 8082, are the same as for the
8082 My IC Phone set for the OpenTouch.
If OT Connection for 8082 needs to be relocated, replace another type of set, or must be replaced by
another type of set, its behavior is identical to that of Alcatel-Lucent IP Touch 4068 Phone business
sets (for more information, see: Relocation and Replacement of an IP-Phone on page 59).

8.1.1 Commissionning operations

• Binary files on page 378
• Checking the software version of the set on page 378
• Configuring the DHCP server on page 378

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 377/382

Chapter 8 OT Connection for 8082

• Declaring the set on the OmniPCX Enterprise on page 379

• Starting the set in NOE mode in an OpenTouch environment on page 379

8.2 Binary files

The software delivery of OT Connection for 8082 phones consists of the following files:
• noe8082v
• key.xml
They are located in the /usr2/downbin/ directory of the system.
The binaries of OT Connection for 8082 phones are updated in a background task when the sets are in
service. They must be reset to implement the new binaries.
Localization and customization files are identical for Alcatel-Lucent IP Touch 4068 Phone and OT
Connection for 8082 telephone sets. For more information, see: Binary Files on page 15

8.3 Checking the software version of the set

The 8082 My IC Phone set version must be:
• R260.01.012.1 or higher
• R300 01.006.0 or higher
You can check the set version in the Settings > Device > Software version menu.
If the version is lower than these versions, upgrade the set to allow the NOE mode.
See the related OmniPCX Enterprise technical communication available from the Business Partner
website for more information.

8.4 Configuring the DHCP server

The OmniPCX Enterprise DHCP server can be used: a class exists by default for OT Connection for
8082. For more information on the OmniPCX Enterprise DHCP server, see DHCP server - Detailed
description.
If using an external DHCP server, it must be configured so that the OmniPCX Enterprise address is
sent as a TFTP server address to OT Connection for 8082 sets. Two methods can be used to offer the
TFTP address:
• Option 43 (0x2B) Vendor Specific Information + Opcode 64 (0x40) for TFTP1 and Opcode 65 (0x41)
for TFTP2
• Next Server. can only be used to configure the main TFTP address
Note:
• If TFTP1 is received, it takes precedence over the Next Server field address
• If TFTP2 is received, it is used as the second TFTP server, in combination with TFTP1, or Next Server if
TFTP1 was not received
The vendor class IDs are:
• OT Connection for 8082: alcatel.ictouch.noe.0
• 8082 My IC Phone: alcatel.ictouch.0

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 378/382

Chapter 8 OT Connection for 8082

8.5 Declaring the set on the OmniPCX Enterprise

OT Connection for 8082 does not support the compression algorithm G723 available in OmniPCX
Enterprise systems.
1. Select: System > Other System Param. > Compression Parameters > Compression Type
2. Review/modify the following attribute:

System Option Compression Type

Compression Type Select G729

3. Select: Users
4. Create a user with the following attributes:

Directory Number Enter the IP phone user's directory number

Shelf Address Enter 255

Board Address Enter 255

Equipment Address Enter 255

Set Type To select the appropriate option, refer to: Dedicated

Sets - Premium DeskPhones and 8082 My IC Phone
identification in configuration tools
5. Confirm your entries

8.6 Starting the set in NOE mode in an OpenTouch environment

If, on a given system, 8082 My IC Phone sets run on another system and must be used as OT
Connection for 8082 in NOE mode, they must be manually configured before being put into service.
This is achieved either from the sets themselves or from the OmniVista 8770.

8.6.1 Resetting the phone to its out-of-the-box default settings

1. Connect to the phone using ssh
2. If the phone software is not of a recent release, delete the Certificate Trusted List (CTL)
3. Enter the reset flash command to reset the phone set to its out-of-the-box default settings
Example:

$ CTL erase

...

$ reset flash

8.6.2 Dissociating set and user from the OmniVista 8770

The following procedure applies when the set was previously used as 8082 My IC Phone set, running
on an OpenTouch.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 379/382

Chapter 8 OT Connection for 8082

1. Dissociate the device from the OpenTouch user in the OmniVista 8770 application. Manually power
the set off.
2. Start the 8082 My IC Phone set and wait until the Settings menu is available
3. Press Settings on the 8082 My IC Phone screen
4. Press Admin and enter the password
5. Select Network > TFTP to configure the OmniPCX Enterprise main IP addresses
6. Select Device > Running mode

7. Enable the NOE protocol

8. Confirm your entries
The set resets automatically and connect to the OmniPCX Enterprise for upgrading. After the NOE
binary are flashed, the set resets.
9. Enter the directory number and password when requested (default password is 0000)

8.7 Starting the set in NOE mode in an OmniPCX Enterprise

environment
If the deployment is performed on an OmniPCX Enterprise without OpenTouch, the NOE mode can be
automatically implemented.
As of R11.0, the Vendor Class for the OT Connection for 8082 is automatically created in the internal
DHCP of OmniPCX Enterprise. The corresponding class is named VHE. To make the switch from SIP
to NOE protocol automatic the field BOOT FILE NAME must be completed by the name lanpbx.cfg
for the Vendor Class Id: alcatel.ictouch.0 (for more details on this configuration, see: DHCP
server - Configuration procedure)
Once this configuration is made, new 8082 My IC Phone sets, out-of-the-box, connected to IP network
automatically initialize in NOE mode and download the lanpbx.cfg file and NOE binary, at first
startup.
Older devices previously connected to an OpenTouch system can be used, provided the set is
configured back to default settings, see: Resetting the phone to its out-of-the-box default settings on
page 379.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 380/382

Chapter 8 OT Connection for 8082

8.8 Switching the set back to SIP mode

1. Switch off the phone
2. Restart the phone and press the Settings key, available when the set reaches step 2 of its
initialization
3. Access the SoftInfo menu
4. Set the Run Mode option to SIP
5. Enter the DM URL
6. Restart the phone
The phone downloads the SIP packages and starts as a typical SIP phone.

8.9 Specific maintenance

For more information, see: Maintenance on page 56.

8.9.1 Set identification

Tools such as: listerm, tradna, tradeq, ippstat and ftp_check-c indicate 8082 in their typ
term/type column.
ippstat and ftp_check-c provide technical characteristics, such as firmware version, IP domain,
coding algorhythm among others.
Use the command downstat t to verify whether telephone sets are in a downloading process.

8.9.2 Firmware upgrade

Firmware upgrade takes place in background mode. Once it is over, the user is warned by the
displayed countdown, after which the set reboots.

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 381/382

Chapter 8 OT Connection for 8082

If the set is being used in navigation or for a phone call, firmware upgrade is delayed until the set
returns in unused state.

8.9.3 Retrieving logs

This may be necessary after a crash or another unexpected issue.
1. Authorize the remote session using the ippstat tool indicating the directory number of the device:
Example:
ippstat telnet d <directory number>t 1440
2. Connect to the set, using the admin login. From the communication server, type ssh -2 -l
admin <ip adress>
where <ip adress> corresponds to the IP address of the set
The default password is: *tx8000#
3. Copy and print all files in the directories /log, /data/core and /var/log

8AL91024USAG - Ed. 01 - April 2017 - OXE System: Dedicated Sets 382/382