0% found this document useful (0 votes)

903 views184 pages

OpenScape Desk Phone CP Phone Administration Guide HFA

This document provides information about installing and administering the OpenScape Desk Phone CP family of desk phones, including: - An overview of the CP110, CP210, CP410, and CP710 phone models. - Instructions for connecting the phones via LAN cable or USB Wi-Fi dongle, and accessing the web-based management interface. - Information on initial configuration options like the terminal number, network settings, date and time synchronization, and manual registration. - Details for settings like VLAN configuration, the HFA gateway, and configuring the DMS address via DHCP.

Uploaded by

tam do

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

903 views184 pages

OpenScape Desk Phone CP Phone Administration Guide HFA

Uploaded by

tam do

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 184

Unify OpenScape

Desk Phone CP

Atos Unify
OpenScape Desk Phone
CP Family
Administrator Documentation HFA

A31103-C1100-M102-13-76A9
2 Important information

Important information

For safety reasons, the telephone should only be supplied with power:

l using the original power supply unit.

l over a LAN with PoE (Power over Ethernet), which complies with the IEEE
802.3af standard.

Never open the telephone. Should you encounter any problems, consult your
administrator.

Use only original accessories.

The use of other accessories is hazardous and will render the warranty, extended
manufacturer's liability and the CE and other markings invalid.

Trademarks

The device conforms to the EU Directive as attested by the CE marking. The CE

Declaration of Conformity and, where applicable, other existing declarations of
conformity as well as further information on regulations that restrict the usage
of substances in products or affect the declaration of substances used in
products can be found in the Unify Expert WIKI at http://wiki.unify.com/
http://wiki.unify.com in the section "Declarations of Conformity".

The adjacent symbol indicates that any electrical and electronic products
installed and sold in countries of the European Union to which the WEEE2 Dir-
ective 2012/19/EU applies should be disposed of separately from the municipal
waste stream in appropriate collection systems.

Information concerning the proper disposal of your Unify product in the busi-
ness-to-business market segment is available from your local sales rep-
resentative in Unify or partner sales.

Software update
During a software update, the phone must not be disconnected from the power supply unit or the
LAN. An update action is indicated by messages on the display and by flashing LEDs.
Important information 3

Online documentation
This document along with additional information is available online at:
https://www.unify.com/ à Support.

Technical notes, current information about firmware updates, frequently asked questions and
lots more can be found on the Internet at: https://wiki.unify.com/.

Location of the telephone

l The telephone may only be operated using the LAN cabling internally in the building. The
device should be connected to the IP infrastructure using a shielded LAN cable: Cat-5 for
100 Mbps or Cat-6 for 1000 Mbps. Make sure in the building installation that this cable
shielding is earthed.
l When using the additional Wi-Fi dongle CP10 when connecting the phone to the network,
make sure that the network security standards (e.g. encryption) and availability are met
l The telephone is designed for operation in a protected environment within a temperature
range of 5 °C to 40 °C.
l Do not install the telephone in a room where large quantities of dust accumulate; this can
considerably reduce the service life of the telephone.
l Do not expose the telephone to direct sunlight or any other source of heat, as this is liable
to damage the electronic components and the casing.
l Do not install the telephone in bathrooms or shower rooms.

Product-oriented environmental protection

Unify is committed in terms of its product strategy to bringing environmentally friendly products
to market, taking account of the entire product life cycle. Unify strives to acquire the relevant
environmental labels for its products in the event that the environmental label programs permit
qualification for individual Unify products.

Special setting instructions for energy-efficient use of telephones can be found in

section "Energy saving" à page 86.
4 Important information

Energy Star

ENERGY STAR is a US Environmental Protection Agency voluntary program

that helps businesses and individuals Save money and protect our climate
through superior energy efficiency.

Products that earn the ENERGY STAR prevent greenhouse gas emissions by
meeting strict energy efficiency criteria or requirements set by the US Envir-
onmental Protection Agency.

Unify is an ENERGY STAR partner participating in the ENERGY STAR program for Enterprise Serv-
ers and Telephony.

The Unify products OpenScape Desk Phones have earned the ENERGY STAR. Learn more at
energystar.gov

License information
For further information about EULA (End User License Agreement) and Open Source licenses,
consult your administrator or the web-based management (WBM, see "How to access the web
interface (WBM)" à page 28).
Important information 5

Contents

Important information 2
Trademarks 2
Software update 2
Online documentation 3
Location of the telephone 3
Product-oriented environmental protection 3
License information 4

Overview 10
About this manual 10
Maintenance notes 10
Conventions for this document 10
The OpenScape Desk Phone CP family 11
OpenScape Desk Phone CP110 11
OpenScape Desk Phone CP210 13
OpenScape Desk Phone CP410 15
OpenScape Desk Phone CP710 17
Administration interfaces 18
Web-based management (WBM) 18
Local phone menu 19
DLS/DMS (OpenScape Deployment Service / Device Management Service) 19

Startup 20
Prerequisites 20
Assembling and installing the phone 20
Shipment 20
Connectors at the bottom side 21
Assembly 24
How to connect the phone via LAN cable 25
How to use LAN connections 26
How to connect the phone via USB Wi-Fi dongle 27
Key modules 27
Quick start 27
How to access the web interface (WBM) 28
6 Important information

Access via local phone 29

How to configure the Terminal number 30
Basic network configuration 30
DHCP resilience 31
Date and time / SNTP 31
Extended Network configuration 31
Vendor-specific VLAN discovery and DLS address 32
HFA gateway settings 41
Manual registration 41
Using the local menu 42
Setting the DMS address via DHCP 42
Cloud deployment 43

Administration 48
Bluetooth interface 48
LAN settings 49
LAN port settings 49
VLAN 51
IP Network parameters 55
Quality of Service (QoS) 55
Use DHCP 58
Manual configuration of the IP address 59
Default router / gateway 61
Specific IP routing 61
DNS 62
IP TTL 65
Configuration & update service 65
SNMP 68
OpenScape service menu 70
Wi-Fi settings 70
Setting up a WiFi connection 73
Disable LAN port 74
Advanced Wi-Fi settings 74
System 77
HFA gateway settings 78
HFA emergency gateway settings 80
Server and standby server ports 81
Important information 7

Redundancy 82
Emergency number 83
LIN 84
Not used timeout 84
Enable telephony settings 86
Energy saving 86
System 87
Date and time 90
Settings via SNTP 91
Dialing 92
Canonical dialing configuration 92
Canonical dial look-up 95
Distinctive ringing 97
User mobility 99
Free programmable keys 100
Enabling "Long Press" for FPKs 100
Selected dial action on calls 101
Transferring phone software, application, and media files 101
Linux file name issues 101
FTP / HTTPS server 102
Common FTP / HTTPS settings (defaults) 102
Phone application 104
Picture clips 108
LDAP template 111
Screen Saver 114
Ringer file 117
Company logo 120
UC server 122
Send request via HTTP / HTTPS 122
Settings of the corporate directory 125
LDAP 125
Contact details update 127
Picture via LDAP 128
Canonical dial settings 129
Speech 130
RTP base port 130
Codec preferences 131
8 Important information

Security and policies 132

Changing a password 132
Retrieve a lost password 134
Certificates 134
Restart phone 136
Factory reset 137
SSH — secure shell access 137
Display license information 138
HPT interface (for service staff) 139
AlertBar LED hint 140
Diagnostics 140
LLDP-MED 140
Fault trace configuration 142
EasyTrace profiles 146
Advanced audio traces 150
QoS reports 151
Miscellaneous 156
Remote tracing — syslog 158
Key modules 159

Examples and how-tos 161

Canonical dialing 161
Canonical dialing settings 161
Canonical dialing look-up 161
Conversion examples 162
How to set up the “Corporate directory” (LDAP) 164
Prerequisites 164
Create an LDAP template 164
Upload the LDAP template to the phone 168
Configure LDAP access 169
Mapping the LDAP fields 169
LLDP-Med example 170

Technical reference 172

Default port list 172
Troubleshooting error codes 173
Important information 9

Glossary 178
10 Overview

Overview

About this manual

The instructions within this manual will help you in administering and maintaining OpenScape
Desk Phone CP telephones. The instructions contain important information for safe and proper
operation of the phones. Follow them carefully to avoid improper operation and get the most out
of your multi-function telephone in a Network environment.

This guide is intended for service providers and Network administrators who administer VoIP
services using the OpenScape Desk Phone CP and who have a fundamental understanding of
VoIP, SIP, IP networking, and telephony. The tasks described in this guide are not intended for
end users.

These instructions are laid out in a user-oriented manner, which means that you are led through
the functions of the OpenScape Desk Phone CP step by step, wherever expedient. For the users,
a separate manual is provided.

You can find further information on the official Unify website (https://www.unify.com/) and on
the Unify Wiki (https://wiki.unify.com/).

Maintenance notes
Warning Do not perform maintenance work or servicing of the telephone in environments
where there is a danger of explosions.

Note Use only original accessories. Using other accessories may be dangerous and will
invalidate the warranty and the CE mark.

Note Never open the telephone or a key module. If you encounter any problems, contact
system support.

Conventions for this document

The terms for parameters and functions used in this document are derived from the web inter-
face (WBM). In some cases, the phone’s local menu uses shorter, less specific terms and abbre-
viations. In a few cases the terminologies differ in wording. If so, the local menu term is added
with a preceding "/".

For the parameters described in this document, a WBM screenshot and the path to the item in
the local phone menu is provided.
Overview 11

This document describes the software version 2.0.

The OpenScape Desk Phone CP family

OpenScape Desk Phone CP110

1 You can make and receive calls as normal using the handset.

2 The Notification LED (“AlertBar LED”) displays the phone connection status.
Incoming calls and new voice mails are visually signalled.
12 Overview

3 The display shows information during telephone operation (three lines with up to
32 characters each).

4 The programmable function keys can be set to various functions.

5 The function keys (non-programmable) are assigned to the following functions

during a call:

: Provides access to the user menu for locally controlling the phone set-
tings.

: Allows voicemails to be managed.

: Increases or decreases the speaker or headset volume.

: Activates or deactivates the microphone.

: Activate or deactivates the speakerphone during an active call.

: Activates or deactivates the headset.

6 The navigation keys help you navigating through the various phone functions,
applications and configuration menus.

7 The dialpad can be used to enter phone numbers and write text.

8 You can speak without the handset using the microphone.

Overview 13

OpenScape Desk Phone CP210

1 You can make and receive calls as normal using the handset.

2 The Notification LED (“AlertBar LED”) displays the phone connection status.
Incoming calls and new voice mails are visually signalled.D.

3 The display shows information during telephone operation (three lines with up to
32 characters each).

4 The programmable function keys can be set to various functions.

14 Overview

5 The function keys (non-programmable) are assigned to the following functions

during a call:

: Provides access to the user menu for locally controlling the phone set-
tings.

: Allows voice mails to be managed.

: Hold or retrieve the active call.

: Transfer a call to another contact.

: Enable access to the conference functions.

: Increases or decreases the speaker or headset volume.

: Activates or deactivates the microphone.

: Activate or deactivates the speakerphone during an active call.

: Activates or deactivates the headset.

6 The navigation keys help you navigating through the various phone functions,
applications and configuration menus.

7 The dialpad can be used to enter phone numbers and write text.

8 You can speak without the handset using the microphone.

Overview 15

OpenScape Desk Phone CP410

1 You can make and receive calls as normal using the handset.

2 The Notification LED (“AlertBar LED”) displays the phone connection status. Incoming
calls and new voice mails are visually signalled.

3 The display shows information during telephone operation.

4 The fixed function keys on the right of the display correspond to the fixed functions
on the display.
16 Overview

5 The function keys (non-programmable) are assigned to the following functions during
a call:

: Provides access to the user menu for locally controlling the phone settings.

: Allows voice mails to be managed.

: Hold or retrieve the active call.

: Transfer a call to another contact.

: Enable access to the conference functions.

: Increases or decreases the speaker or headset volume.

: Activates or deactivates the microphone.

: Activate or deactivates the speakerphone during an active call.

: Activates or deactivates the headset.

6 The navigation keys help you navigating through the various phone functions, applic-
ations and configuration menus.

7 The dialpad can be used to enter phone numbers and write text.

8 You can speak without the handset using the microphone.

Overview 17

OpenScape Desk Phone CP710

1 You can make and receive calls as normal using the handset.

2 The Notification LED (“AlertBar LED”) displays the phone connection status.
Incoming calls and new voice mails are visually signalled.

3 The display shows information during telephone operation.

4 The programmable function keys on the left of the display can be set to various
functions.

The fixed function keys on the right of the display correspond to the fixed func-
tions on the display.
18 Overview

5 The function keys (non-programmable) are assigned to the following functions

during a call:

: Provides access to the user menu for locally controlling the phone set-
tings.

: Allows voice mails to be managed.

: Hold or retrieve the active call.

: Transfer a call to another contact.

: Enable access to the conference functions.

: Increases or decreases the speaker or headset volume.

: Activates or deactivates the microphone.

: Activate or deactivates the speakerphone during an active call.

: Activates or deactivates the headset.

6 The navigation keys help you navigating through the various phone functions,
applications and configuration menus.

7 The dialpad can be used to enter phone numbers and write text.

8 You can speak without the handset using the microphone.

Administration interfaces
You can configure the OpenScape Desk Phone CP by using any of the methods described in this
section.

Web-based management (WBM)

This method employs a web browser for communication with the phone via HTTPS. It is applic-
able for remote configuration of individual IP phones in your Network. Direct access to the
phone is not required.

Note To use this method, the phone must first obtain IP connectivity.
Overview 19

Licenses
This area provides the user with the information about EULA (End User License Agreement) and
Open Source licenses. This section is on the main area within WBM, which is not password pro-
tected to allow access for the user (see "Manual registration" à page 41).

Local phone menu

This method provides direct configuration of the OpenScape Desk Phone CP via the local phone
menu. Direct access to the phone is required.

As long as the IP connection is not properly configured, use this method to set up the phone.

DLS/DMS (OpenScape Deployment Service / Device

Management Service)
The OpenScape Deployment Service (DLS) and Broadsoft Device Management Service (DMS)
are management applications for administering phones in both OpenScape and non-OpenScape
networks.

Note To use this method, the phone must first obtain IP connectivity.

For further information, refer to the DLS or DMS Administration Guide.

20 Startup

Startup

Prerequisites
The OpenScape Desk Phone CP acts as an endpoint client on an IP telephony Network, and has
the following Network requirements:

l An Ethernet connection to a Network with communication servers.

Note Only use switches in the LAN to which the OpenScape Desk Phone CP
phone is connected. An operation at hubs can cause serious malfunctions
in the hub and in the whole Network.

l OpenScape 4000, OpenScape Business, OpenScape Voice, or other SIP server.

l An FTP Server for file transfer, e. g. firmware, configuration data, application software
l A DHCP (Dynamic Host Configuration Protocol) server (recommended).
l DLS (OpenScape Deployment Service) for advanced configuration and software deploy-
ment (recommended).

Any secure interface, such as IEEE_802.1x, will require a reliable time source. Thus an SNTP server
is essential for these interfaces. For additional information see: https://wiki.unify.com/wiki/IEEE_
802.1x

Assembling and installing the phone

Shipment
l Phone
l Handset
l Handset cable
l Placement supports
l Sub-package: Document "Information and Important Operating Procedures"
Startup 21

Connectors at the bottom side

OpenScape Desk Phone CP110

1 Network LAN port 2 PC LAN port

3 Optional power supply 4 Headset port

5 Handset port
22 Startup

OpenScape Desk Phone CP210

1 Network LAN port 2 PC LAN port

3 USB-A port 4 Optional power supply

5 Headset port 6 Handset port

7 Key module port

Note The key module is not “hot-swappable”: Always switch off the phone before remov-
ing or connecting a key module.
Startup 23

OpenScape Desk Phone CP410

1 Network LAN port 2 PC LAN port

3 USB-A port 4 Optional power supply

5 Headset port 6 Handset port

7 Key module port

Note The key module is not “hot-swappable”: Always switch off the phone before remov-
ing or connecting a key module.
24 Startup

OpenScape Desk Phone CP710

1 Network LAN port 2 PC LAN port

3 USB-A port 4 Optional power supply

5 Headset port 6 Handset port

7 Key module port

Note The key module is not “hot-swappable”: Always switch off the phone before remov-
ing or connecting a key module.

Assembly
1. Insert the plug on the long end of the handset cable into the jack on the base of the
telephone.
Startup 25

2. Press the cable into the groove provided.

3. Insert the plug on the short end of the handset cable into the jack on the handset.

How to connect the phone via LAN cable

When using a CP10 connector, all phones can be connected to the network vie WiFi. They may
require a Power-over-Ethernet (PoE) connection to power them if not connected to a power
source via the power connection.

1. Plug the LAN cable into the connector at the bottom of the telephone and connect the
cable to the LAN or switch.

Note If PoE (Power over Ethernet) is used, the PSE (Power Sourcing Equipment) must
meet the IEEE 802.3af specification.

For details about the required power supply, see the following table:

Model Power supply

l PoE (Power Class 1)

OpenScape Desk Phone CP110
l Power chord

l PoE (Power Class 2)

OpenScape Desk Phone CP210
l Power chord

OpenScape Desk Phone CP410 l PoE (Power Class 2)

l Power chord
l Only 1 key module can be connected using PoE

OpenScape Desk Phone CP710

l When the power supply for the USB port is set to 120 mA, l PoE (Power Class 3)
up to 4 key modules can be connected. l Power chord
l When the power supply for the USB port is set to 500 mA,
only up to 2 key modules can be connected.

2. If Power over Ethernet (PoE) is not provided by the system, plug the power supply unit
into the mains.
3. Connect the power supply unit to the power connector at the bottom of the phone (see
"Connectors at the bottom side" à page 21). Up to 4 key modules can be connected to
CP710 or CP410 when using a mains power supply.

Plug-in power supply Order no.

Power supply, power cable and plug (Type E+F) for EU L30250-F600-C141
26 Startup

Plug-in power supply Order no.

Power supply, power cable and plug for Great Britain L30250-F600-C142

Power supply, power cable and plug for USA L30250-F600-C143

Power supply, power cable and plug for Switzerland L30250-F600-C182

Power supply, power cable and plug for Italy L30250-F600-C183

Power supply, power cable and plug for Australia L30250-F600-C184

Power supply, power cable and plug for South Africa L30250-F600-C185

Power supply without power cable L30250-F600-C148

4. If applicable, connect the following optional jacks:

l LAN connection to PC
l Headset (accessory)

How to use LAN connections

You may connect one additional network device (e. g. a PC) directly via the telephone to the
LAN. The direct connection functionality from phone to PC needs to be activated first. This type
of connection allows you to Save one network connection per switch with the advantage of less
network cables and shorter connection distances.

Note Do not use this connection to connect additional OpenScape Desk Phone CP
phones, OpenScape Desk Phone IP phones, or OpenStage phones!

Fig.: 4-1: LAN connections (example)

Startup 27

How to connect the phone via USB Wi-Fi dongle

Note Configuring the USB access is possible only for phones with a USB port (see "Con-
nectors at the bottom side" à page 21).

The phone can also be connected to a wireless network via the USB type A port with the Wi-Fi
USB dongle CP10 (see "The OpenScape Desk Phone CP family" à page 11).

Do not unplug the USB dongle during calls, as this disrupts the network connection.

1. Insert the USB Wi-Fi dongle into the USB port.

2. Check that USB is enabled (see "Configuring the USB access" à page 1).
3. Check that Wi-Fi is enabled (see "Wi-Fi settings" à page 70).
4. If applicable, connect the following optional jacks:
l Headset (accessory)

Key modules
A key module provides additional program keys. The following table shows which key modules
can be connected to the particular phone types.

Key module Number of key modules Additional keys per

Phone type
(KM) (max.) module

OpenScape Desk Phone

KM410 4 16
CP410

OpenScape Desk Phone

KM710 4 12
CP410

OpenScape Desk Phone

KM410 4 16
CP710

OpenScape Desk Phone

KM710 4 12
CP710

The configuration of a key on the key module is identical to the configuration of a phone key.

Quick start
This section describes the typical setup of an OpenScape Desk Phone CP endpoint in an envir-
onment using a DHCP server and the web interface. For different scenarios, cross-references to
28 Startup

the corresponding information of the administration sections are given.

Alternatively, the DLS (Deployment Service) administration tool can be used. Its Plug & Play func-
tionality allows to provide the phone with configuration data by assigning an existing data profile
to the phone’s MAC address or E.164 number. For further information, see the Deployment Service
Administration Manual.

Note Any settings made by a DHCP server are not configurable by other configuration
tools.

How to access the web interface (WBM)

Prerequisites

l The phone IP address or URL is required for accessing the phone web interface via a web
browser. By default, the phone will automatically search for a DHCP server on start-up
and try to obtain IP data and further configuration parameters from that central server.
l If no DHCP server is available in the IP network or if the DHCP parameter is disabled, the
IP address, subnet mask and default gateway /router must be defined manually.

Procedure

1. Access the local phone admin menu (see "Access via local phone" à page 29).
l If DHCP is enabled (default): In the admin menu, navigate to Network > IPv4 con-
figuration > IP address. The IP address is displayed.
l If DHCP is disabled or if no DHCP server is available in the IP Network, the IP
address, Subnet mask and default router or gateway must be defined (see "Basic
network configuration" à page 30).
2. Open a web browser and enter the IP address, e.g. https://192.168.1.15 or
https://myphone.phones.
(For configuring the phone DNS name, refer to "Terminal host name" à page 64).
3. If the browser displays a certificate notification, accept it.
4. Click the tab "Administrator settings".
5. Enter the admin password. The default password is “123456”.

The main page of the “Administrator settings” page is displayed. The left column contains the
menu tree.

l Clicking on an item printed in normal style opens the corresponding page.

l Clicking on an item printed in bold letters opens a sub-menu containing further items.
Startup 29

Access via local phone

OpenScape Desk Phone CP110

1. Press the key for “Settings” .

2. Enter the administrator password (default password is “123456”). It is highly recom-
mended to change the password after your first login (see section "Changing a password"
à page 132).
3. Confirm with the key OK .

OpenScape Desk Phone CP210

1. Press the key for “Settings” .

OpenScape Desk Phones CP410 / CP710

1. Access the administration menu:

l Press “1 3 0” simultaneously.
l Use the Up arrow, Down arrow and OK keys consecutively to select the admin-
istration menu.
2. Enter the administrator password. The default password is "123456". It is recommended
to change the password after first login.
For changing the mode, press “#” once or repeatedly, depending on the desired character.
The “#” key cycles around the input modes as follows: (Abc) -> (abc) -> (123) -> (ABC) ->
back to start.
3. Navigate within the administration menu.
4. Select a parameter. If a parameter is set by choosing a value from a selective list, an
arrow symbol is displayed in the selected parameter field.
5. Press OK to enter the selective list. Use the Up Arrow and Down Arrow keys to scroll up
and down in the selection list.
6. To select a list entry, press OK.
7. Enter the parameter value for selecting numbers and characters, use special keys.

Key function
Key Key function during text input when held
down

l 2 seconds:
Ringer off
Enter special characters.
l 3 seconds:
Beep sound
30 Startup

Key function
Key Key function during text input when held
down

instead of
ringer

Toggle between lowercase characters, uppercase char-

Phone lock on /
acters, and digits in the following order: (Abc) -> (abc) ->
off.
(123) -> (ABC) -> back to start.

1. Use the keypad for entering parameter values. Use the navigation keys or navigation
block to navigate and execute administrative actions in the administration menu.
2. Select Save & exit and click OK.

How to configure the Terminal number

Prerequisites

If the user and administrator menus are needed for setup, the terminal number must be con-
figured first. The Terminal number is by default identical with the phone number. When the
phone is in delivery status, the terminal number input form is presented to the user / admin-
istrator right after booting, unless the Plug & Play capability of the DLS is used.

Procedure

With the WBM, the terminal number is configured as follows:

1. Log on as administrator to the WBM by entering the access data for your phone.
2. In the Administrator menu (left column), select System > System Identity to open the "Sys-
tem Identity" dialog.
3. Enter the terminal number.

Basic network configuration

For basic functionality, DHCP must provide the following parameters:

l IP Address: IP Address for the phone.

l Subnet Mask (option #1): Subnet mask of the phone.
l Default Route (option #3 "Router"): IP Address of the default gateway which is used for
connections beyond the subnet.
l DNS IP Addresses (option #6 "Domain Server"): IP Addresses of the primary and sec-
ondary DNS servers.

If no DHCP server is present, see "Manual configuration of the IP address " à page 59 for IP
address and subnet mask, and "Default router / gateway" à page 61 for the default route.
Startup 31

DHCP resilience
Prerequisites

It is possible to sustain Network connectivity in case of DHCP server failure. If “DHCP reuse” is
activated, the phone will keep its DHCP-based IP address even if the lease expires. To prevent
address conflicts, the phone will send ARP requests in 5 second intervals. Additionally, it will
send discovery messages periodically to obtain a new DHCP lease.

Procedure

1. Open Network > Wired settings.

2. Select the checkbox to enable DHCP lease reuse.

Date and time / SNTP

A SNTP (Simple Network Time Protocol) server provides the current date and time for Network
clients. The IP address of a SNTP server can be given by DHCP or can be configured manually
(see "Settings via SNTP" à page 91).

Consistent time for peer entities is required to allow secure interfaces to operate correctly. To
provide the correct time, it is required to give the time zone offset, i.e. the shift in hours to be
added to the UTC time provided by the SNTP server.

The following DHCP options are required:

l SNTP IP Address (option #42 "NTP Servers"): IP Address or hostname of the SNTP server
to be used by the phone.
l Time zone offset (option #2 "Time Offset"): Offset in seconds in relationship to the UTC
time provided by the SNTP server. For manual configuration of date and time see "Date
and time" à page 90.

Extended Network configuration

To have constant access to other subnets, you can enter a total of two more Network des-
tinations. For each further domain / subnet you wish to use, first the IP address for the
32 Startup

destination, and then that of the router must be given. The option’s name and code are as fol-
lows:

l Static Routing Table (Option #33): For manual configuration of specific/static routing,
see "Specific IP routing" à page 61.

Also the DNS domain wherein the phone is located can be specified by DHCP. The option’s
name and code are as follows:

l Domain Name (Option #15): For manual configuration of the DNS domain name, see
"DNS domain name" à page 63.

Vendor-specific VLAN discovery and DLS address

Note The VLAN ID can also be configured by LLDP-MED (see "Automatic VLAN dis-
covery using LLDP-MED" à page 52).

If a DLS (Deployment Service) server is in use, its IP address must be provided. It is recom-
mended to configure the DLS server address by DCHP, as this method enables full Plug & Play:
having received the DLS address from DHCP, the phone will contact the DLS during start-up.
Provided that the DLS is configured appropriately, it will send all necessary configuration data to
the phone. Additionally, this method is relevant to security, as it ensures the authenticity of the
DLS server.

l For manual configuration of the DLS server address see "Configuration & update service"
à page 65.
l For the configuration of vendor-specific settings by DHCP, there are two alternative meth-
ods:
n Using a vendor class (see "Using vendor class" à page 36)
n Using the DHCP option #43 (see "Using option #43 "Vendor Specific"" à page 34)
l For DMS follow the instructions in "Setting the DMS address via DHCP" à page 42.

VLAN discovery
If the phone is located in a VLAN (Virtual LAN), a VLAN ID must be assigned, see "VLAN" à page
51.

If the VLAN is provided by DHCP, VLAN Discovery must be set to "DHCP". The corresponding
DHCP option is vendor-specific, thus a specific procedure is necessary.

l For automatic configuration via LLDP-MED see "Automatic VLAN discovery using LLDP-
MED" à page 52.
l For automatic configuration via DHCP see "Automatic VLAN discovery using DHCP" à
page 52.
l For manual configuration see "Manual configuration of a VLAN ID" à page 54.

For information on how to use a vendor class, refer to "Using vendor class" à page 36
Startup 33

Automatic VLAN discovery using LLDP-MED

This is the default setting. The VLAN ID is configured by the network switch using LLDP-MED
(Link Layer Discovery Protocol-Media Endpoint Discovery). If the switch provides an appropriate
TLV (Type-Length-Value) element containing the VLAN ID, this VLAN ID is used. If no appropriate
TLV is received, DHCP is used for VLAN discovery.

Administration via WBM

1. Open Network > Wired settings.

1. Enable “Use LLDP-MED”.

2. Select “LLDP-MED” in the option “VLAN discovery”.

Administration via local phone

Manual configuration of a VLAN ID

Note If you configure a phone to an incorrect VLAN, the phone may not connect to the
network.
34 Startup

Administration via WBM

1. Open Network > Wired settings.

2. In “LAN connection”, set “VLAN discovery” to “Manual”.

3. Click Submit.

4. Set a VLAN ID between 1 and 4095.

5. Click Submit.

Administration via local phone

Using option #43 "Vendor Specific"

Alternatively, option #43 can be used for setting up the VLAN ID. Two tags are required:

l Tag 001: Vendor name

l Tag 002: VLAN ID

The Vendor name tag is coded as follows (the first line indicates the ASCII values, the second
line contains the hexadecimal values):

Code Length Vendor name

1 7 S i e m e n s

01 07 53 69 65 6D 65 6E 73
Startup 35

The following example shows a VLAN ID with the decimal value "10":

Code Length VLAN ID

2 4 0 0 1 0

02 04 00 00 00 0A

DLS server address

This setting only applies if a DLS / DMS server is in use.

It is recommended to configure the DLS / DMS server address by DCHP, as this method enables
full Plug & Play and ensures the authenticity of the DLS server.

l For manual configuration of the DLS server address see "Configuration & update service"
à page 65.
l For configuration of the DMS, see "Setting the DMS address via DHCP" à page 42.
l For the configuration of vendor-specific settings by DHCP, there are two alternative meth-
ods:
n the use of DHCP option #43
n the use of a vendor class

For information on how to use a vendor class, refer to "Using vendor class" à page 36

Setting up the DLS Server

1. In the Windows Start menu, select Start > Programs > Administrative Tools > DHCP.
2. Select the DHCP server and the scope.
3. Select "Configure Options" in the context menu using the right mouse button.
36 Startup

4. Enter the IP address and port number of the DLS server.

5. Click Apply.
6. Click OK.

Using vendor class

It is recommended to define a vendor class on the DHCP server, thus enabling server and phone
to exchange vendor-specific data exclusively. The data is disclosed from other clients. If not
done already, create a vendor class by the name of "OptiIpPhone".

The following steps are required for the configuration of the Windows DHCP server.

Setup using the Windows DHCP Server

1. In the Windows Start menu, select Start > Programs > Administrative Tools > DHCP.
2. In the DHCP console menu, right-click the required DHCP server and select Define Vendor
Classes... in the context menu.
Startup 37

3. Click Add.

4. Define a new vendor class with the name OptiIpPhone and enter a description of this
class.

5. Click OK. The new vendor class now appears in the list.
6. Close the window.

Add options to the new vendor class

Two options or tags is added to the vendor class. Two passes are needed:

l In the first pass, tag #1 with the required value "Siemens" is entered.
l In the second pass, the DLS address is entered as tag #3.

Note For DHCP servers on a Windows 2003 Server (pre-SP2): Windows 2003 Server con-

tains a bug that prevents you from using the DHCP console to create an option
with the ID 1 for a user-defined vendor class. Instead, this entry must be created
with the netsh tool in the command line (DOS shell).

You can use the following command to configure the required option (without error message) so
that it also appears later in the DHCP console:

netsh dhcp server add optiondef 1

"Optipoint element 001" STRING 0
vendor=OptiIpPhone comment="Tag 001
for Optipoint"

The value SIEMENS for optiPoint Element 1 can then be re-assigned over the DHCP console.
38 Startup

This error was corrected in Windows 2003 Server SP2.

1. In the DHCP console menu, right-click the DHCP server in question and select Set Pre-
defined Options from the context menu.

2. In the dialogue, select the previously defined OptiIpPhone class and click on Add... to add
a new option.

3. Enter the following data for the new option:

l First Pass: Option 1
n Name: Free text, e. g. "OptiIpPhone element 01"
n Data type: "String"
n Code: "1"
n Description: Free text.
Startup 39

l Second Pass: Option 3

n Name: Free text, e. g. "OptiIpPhone element 03"
n Data type: "String"
n Code: "3"
n Description: Free text.

4. Enter the value for this option.

l First Pass: "Siemens"
l Second Pass: DLS address The DLS address has the following format:
PROTOCOL:://IP ADDRESS OF DLS SERVER:PORT NUMBER Example:
sdlp://192.168.3.30:18443

5. Click OK.
6. Repeat steps 2 to 5 for the second pass.
40 Startup

Defining the scope for the new vendor class

1. Select the DHCP server in question and the Scope and right-click Scope Options. Select
Configure Options... in the context menu.

2. Select the Advanced tab. Under Vendor class, select the class that you previously defined
(OptiIpPhone) and, under User class, select Default User Class.

3. Activate the options that you want to assign to the scope (in this example, 001 and 003).
4. The DHCP console shows the information that is transmitted for the corresponding work-
points. Information from the Standard vendor is transmitted to all clients, whereas inform-
ation from the OptiIpPhone vendor is transmitted only to the clients (workpoints) in this
vendor class.

Setup using a DHCP server on Unix/Linux

The following snippet from a DHCP configuration file (usually dhcpd.conf) shows how to set up
a configuration using a vendor class and the "vendor-encapsulated-options" option.
Startup 41

class "OptiIpPhone" {
   option vendor-encapsulated-options
   # The vendor encapsulated options consist of hexadecimal values for
the option number (for instance, 01), the length of the value (for in
stance, 07), and the value (for instance, 53:69:65:6D:65:6E:73). The
options can be written in separate lines; the last option must be fol
lowed by a ’;’ instead of a ’:’.
   # Tag/Option #1: Vendor "Siemens"
   #1 7 S i e m e n s
    01:07:53:69:65:6D:65:6E:73:
   # Tag/Option #3: DLS IP Address (here: sdlp://192.168.3.30:18443)
   #3 25 s d  l  p  :  / /  1 9  2 .  1  6  8  .  3 . ...etc.
    03:19:73:64:6C:70:3A:2F:2F:31:39:32:2E:31:36:38:2E:33:2E:33:30:
3A:31:38:34:34:33;
   match if substring (option vendor-class-identifier, 0, 11) =
   "OptiIpPhone";
}

HFA gateway settings

To connect the OpenScape Desk Phone CP phone to the OpenScape Business or OpenScape
4000 Communication System, the IP or DNS address of the gateway, a subscriber number and
the corresponding password is needed.

The subscriber number can be 1 to 24 characters long, and is used as the internal telephone
number.

Manual registration
1. Open the web interface of the phone using its IP address.
2. Open the tab “Administration” and enter the admin password.
3. Open System > Gateway.

4. Select the system type from the drop-down menu.

5. Enter the IP address and the name of the gateway server.
6. Enter the subscriber number.
7. Enter the user password of the subscriber.
8. Click Submit.
42 Startup

Using the local menu

2. Enter the IP or DNS address of the HFA gateway provided by the OpenScape Com-
munication System.
3. Enter the phone’s Gateway Id, which will also serve as internal phone number.
4. Enter the password associated with the Gateway ID.
5. Select Save & exit and click OK.

Setting the DMS address via DHCP

When an IP phone is booting, it first obtains an IP address via DHCP. The DHCP server can
provide the DMS address to the phone via Option #43 or Option #66.

Note The DMS address is mutually exclusive with a possibly provided DLS address. A
phone can either connect to a DLS or DMS server.

Using option #43

DHCP vendor specific option #43 can specify a voice VLAN ID and URL of a BroadSoft DMS
server. IP phones will recognize vendor specific options only, if vendor string (here: "Siemens")
matches correctly. All values are given in hexadecimal numbering format.

Example

Tag Length Content (Example)

01 07 5369656d656e73

02 04 00000065

03 1d 68747470733a2f2f3933 ... 3131342E39363a3434332f646d73

Each tag has an explicit length value and is closed by the ending “ff”.
Startup 43

l Tag 01 specifies the vendor (here: Siemens)

n Tag: 01; Length: 07; Value: Siemens
l Tag 02 specifies VLAN ID of Voice VLAN (here: 101)
n Tag: 02; Length: 04; Value: 65 (Hex)
l Tag 03 specifies IP address of Broadsoft DMS
n Tag: 03; Length: 1d; Value: https://93.122.114.96:443/dms (Hex)
l End of record
n End: ff (Hex)

Providing a VLAN ID is optional. You can find details for configuration of a VLAN ID here:
http://wiki.unify.com/wiki/VLAN_ID_Discovery_over_DHCP.

Using option #66

The DHCP server needs to be configured to provide the DMS server URL via Option 66. Here is a
detailed description of the Option 66 bytes.

Option Length Content (Example)

68747470733a2f2f39332e3132322e3131342e39363a3434332f646d7-
42 1d
3

Option #66 does not have specific tags, only a length and content field. The above example
provides the following URL in the content field.

l DHCP option field:

n 42(Hex)
n Length: 1d
n Content: https://93.122.114.96:443/dms (Hex)

Cloud deployment
This section describes how a phone progresses through the cloud deployment process from
factory start-up until the cloud service provider considers it to be ready for use by its user.

The phone determines that a cloud deployment process is to be used based on the IP settings it
receives from the DHCP at the customer site. The “Unify Redirect” server redirects the phone to
a DLS-WPI based management system operated by the cloud service provider. This man-
agement system completes the configuration of the phone with all the information required for it
to be usable and may also customize the phone for the cloud service provider's "house" style.

If zero touch deployment is available the phone is automatically connected to the management
system. However, if zero touch deployment is not possible, then a cloud deployment pin must be
entered at the phone. This PIN is a code that determines which cloud service provider is respons-
44 Startup

ible for the phone. The code is provided as part of a pin supplied from the cloud organization to
the user.

Process of cloud deployment

The following flow chart shows the way from a factory start-up until a user prepared OpenScape
Desk Phone CP family phone, deployed by a relevant DLS-WPI based management system.

Preconditions:

l The phone is not running

l The phone is set to factory default values
l The phone has a LAN connection
l The LAN connection provides access to the public internet

Start

Phone broadcasts a DHCP request The phone has all the information that it needs to
contact a DNS server. A DLS address is not
provided.

A DHCP server responds with IP addresses

The phone detects that a cloud deploy- l DHCP is available

ment is required l IP address allocated to the phone
l DNS address is available
l Subnet mask is available
l Router address is available
l No DLS address available
l No SIP addresses available

The phone starts the zero touch cloud The phone is locked so that the mode keys and
deployment process FPKs etc cannot be used

The phone obtains the IP address of the Unify Redirect server ("cloud-setup.com") from the
DNS
Startup 45

Phone contacts the Unify Redirect server using DLS-WPI

Phone displays the Progress prompt

Phone receives configuration items from l DLS address (set to the name of the Deploy-
the Unify Redirect server ment server)
l Language (optional)
l DLS port (optional)

Phone saves the configuration data If the language is changed the display is updated

Phone updates, and displays the progress prompt

The phone obtains the IP address of the The stored DLS address is not changed by the res-
deployment server from the DNS by look- ult of the DNS look-up.
ing up the DLS address if appropriate.
NOTE: For zero touch deployment, the redirect
server must already know the MAC address of the
phone and uses it to identify the DLS address to
provide to the phone. If the redirect server does not
recognize the phone by its MAC address then is
expects a pre-distributed pin to be provided by the
phone.

Phone contacts the deployment server The hash of the pin is provided as an inventory
using DLS-WPI item to the deployment server
46 Startup

Deployment server configures the phone and the phone saves the changes

Deployment server terminates the DLS-WPI session

The phone exits the cloud deployment process and enables the mode keys and FPKs etc. to
act as normal

Phone removes the progress prompt and displays a timed success pop-up, indicating that
cloud deployment is done

The phone verifies that it now has an e164 number

registered

Reducing deployment time with a deployment parameter

To reduce the installation time of a phone connected to a DLS, the administrator enters a deploy-
ment parameter and leaves the installation process to the DLS.

1. Press the key and connect the phone to the power supply or PoE.
2. When the phone displays the screen for entering the PIN, enter one of the following
numbers:
l The e164-number of the phone that enables the DLS to recognise it.
l The deployment pin of the redirect server to identify the appropriate DLS that can
provide the correct plug & play data for installation.
l A security pin if the DLS needs to bootstrap the phone into secure mode com-
munication with the DLS.
3. Conclude input with . The installation proceeds.

Aborting cloud deployment process by user

The phone detects that a cloud deployment is required and starts the cloud deployment process.
The phone expects the input of the PIN by the user. At this point the user has the option to can-
cel the process. If the user confirms his decision, the deployment process is aborted.
Startup 47

Re-trigger cloud deployment

Cloud deployment may be restarted by triggering a factory reset:

l The DLS-WPI requests a restart to factory defaults of the phone.

l The phone restart then triggers the cloud deployment process.

Deployment errors
During deployment the display will always show deployment specific information. A persistent
warning displays the information that is shown in an idle screen error after deployment failed.

l It is shown to notify the phone User that deployment failed to complete as expected.
l It is a non-timed warning popup
l It is non-dismissible by user action
l It is shown over the idle screen only
l It is shown/re-shown whenever the idle screen is displayed or redisplayed to the user
l It is formatted as the warning icon followed by a warning text which ends in a code dis-
played in round brackets.
l The warning text is = "Deployment incomplete"
l It displays only the highest priority error condition should more than one error condition
apply (note that priority 1 is the highest)

Code Priority Cause

AU 1 Abandoned by user Occurs when the pin prompt is dismissed

Unable to get the address for the Unify Redirect server DNS lookup
RS 1
failed

RN 3 Unable to establish contact with Unify Redirect server — no reply

RR 2 Unable to establish contact with Unify Redirect server — refused

DS 1 Unable to get the address for the Deployment server DNS lookup failed

DN 3 Unable to establish contact with Deployment server — no reply

DR 2 Unable to establish contact with Deployment server — refused

48 Administration

Administration

This chapter describes the configuration of every parameter available on the OpenScape Desk
Phone CP phones.

l For access via the local phone menu, see the following section.
l For access using the web interface (WBM), see "How to access the web interface (WBM)"
à page 28.

Bluetooth interface
Note This feature is available only on OpenScape Desk Phone CP710.

You can activate and deactivate the Bluetooth interface. If the Bluetooth interface is deactivated
no Bluetooth services are available.

Administration via WBM

1. Open Bluetooth.

2. Enable or disable the Bluetooth interface.

3. If the phone is used to detect BLE advertisements, enable the localization client.
4. Provide the server address and port number, as well as the zone.
5. Click Submit.

Administration via local phone

|--- Bluetooth
Administration 49

LAN settings

LAN port settings

The OpenScape Desk Phone CP phones provide an integrated switch that connects the LAN, the
phone and a PC port. By default, the switch will auto negotiate the transfer rate (10/100/1000
Mbps), autosensing, configurable, and duplex method (full or half duplex) with the equipment
connected. Optionally, the required transfer rate and duplex mode can be specified manually
using the LAN port speed parameter.

Note In the default configuration, the LAN port supports automatic detection of cable
configuration (pass through or crossover cable) and will reconfigure itself as
needed to connect to the network. If the phone is set up to manually configure the
switch port settings, the cable detection mechanism is disabled. In this case care
must be taken to use the correct cable type.

The PC Ethernet port (default setting: disabled) is controlled by the PC port mode parameter.

l If set to "Disabled", the PC port is inactive.

l If set to "Enabled", the PC port is active.
l If set to "Mirror", the data traffic at the LAN port is mirrored at the PC port. This setting is
for diagnostic purposes. If, for instance, a PC running Ethereal / Wireshark is connected
to the PC port, all network activities at the phone’s LAN port can be captured.

Note Do not use this connection for further phones!

Note Removing the power from the phone or a phone reset or reboot will result in the
temporary loss of the network connection to the PC port.

When PC port autoMDIX is enabled, the switch determines automatically whether a regular MDI
connector or a MDI-X (crossover) connector is needed, and configures the connector accord-
ingly.
50 Administration

Administration via WBM

1. Open Network > Wired settings.

l LAN port status: Represents the connected (i.e. negotiated) speed (or "Link down" if not
connected). This is read-only item.
l LAN port speed: Settings for the Ethernet port connected to a LAN switch.
n Value range: "Any," "10 Mbps half duplex", "10 Mbps full duplex", "100 Mbps half
duplex", "100 Mbps full duplex", "Gbps full duplex"
n Default: "Any"
l PC port status: Represents the connected (i.e. negotiated) speed (or "Link down" if not
connected). This is read-only item.
l PC port speed: Settings for the Ethernet port connected to a PC.
n Value range: "Any," "10 Mbps half duplex", "10 Mbps full duplex", "100 Mbps half
duplex", "100 Mbps full duplex", "Gbps full duplex"
n Default: "Any"
l PC port mode: Controls the PC port.
n Value range: "disabled", "enabled", "mirror".
n Default: "disabled"
l PC port autoMDIX: Switches between MDI and MDI-X automatically.
n Value range: "On", "Off"
n Default: "Off"
l LAN port disabled (only with CP10): You have the option to disable the LAN port con-
nection when a Wi-Fi network is configured.
Administration 51

Administration via local phone

VLAN
VLAN (Virtual Local Area Network) is a technology that allows Network administrators to par-
tition one physical Network into a set of virtual networks (or broadcast domains).

Partitioning a physical Network into separate VLANs allows a Network administrator to build a
more robust Network infrastructure. A good example is a separation of the data and voice net-
works into data and voice VLANs. This isolates the two networks and helps shield the endpoints
within the voice Network from disturbances in the data Network and vice versa.

Note The implementation of a voice Network based on VLANs requires the Network
infrastructure (the switch fabric) to support VLANs.

l In a layer-1 VLAN, the ports of a VLAN aware switch are assigned to a VLAN statically.
The switch only forwards traffic to a particular port if that port is a member of the VLAN
that the traffic is allocated to. Any device connected to a VLAN assigned port is auto-
matically a member of this VLAN, without being a VLAN aware device itself. If two or
more Network clients are connected to one port, they cannot be assigned to different
VLANs. When a Network client is moving from one switch to another, the switches’ ports
have to be updated accordingly by hand.
l With a layer-2 VLAN, the assignment of VLANs to Network clients is realized by the MAC
addresses of the Network devices. In some environments, the mapping of VLANs and
MAC addresses can be stored and managed by a central database. Alternatively, the
VLAN ID, which defines the VLAN whereof the device is a member, can be assigned dir-
ectly to the device, e. g. by DHCP. The task of determining the VLAN for which an Ethernet
packet is destined is carried out by VLAN tags within each Ethernet frame. As the MAC
addresses are (more or less) wired to the devices, mobility does not require any admin-
istrator action, as opposed to layer 1 VLAN.

The phone must be configured as a VLAN aware endpoint if the phone itself is a member of the
voice VLAN, and the PC connected to the phone’s PC port is a member of the data VLAN.

There are 3 ways for configuring the VLAN ID:

52 Administration

l By LLDP-MED (with fallback to DHCP)

l By DHCP
l Manually

Automatic VLAN discovery using LLDP-MED

Administration via WBM

1. Open Network > Wired settings.

2. Enable “Use LLDP-MED”.

3. Set “VLAN discovery” to “LLPD-MED”.
4. Select the “Time to live” (TTL) in seconds.
l Value range: 40…400 seconds
l Default: 120 seconds
5. Click Submit.

Administration via local phone

Automatic VLAN discovery using DHCP

To automatically discover a VLAN ID using DHCP (except LLDP-MED), the phone must be con-
figured as “DHCP”. The DHCP server is configured to supply the Vendor Unique Option in the cor-
rect VLAN over DHCP format (see "Using option #43 "Vendor Specific"" à page 53).
Administration 53

If a phone configured for VLAN discovery by DHCP fails to discover its VLAN, it will proceed to
configure itself from the DHCP within the non-tagged LAN. Under these circumstances, network
routing may not be correct.

Administration via WBM

1. Open Network > Wired settings.

2. Deselect “Use LLDP-MED”.

3. Select “DHCP” in the VLAN discovery option.
4. Click Submit.

Administration via local phone

Using option #43 "Vendor Specific"

Alternatively, option #43 can be used for setting up the VLAN ID. Two tags are required:

l Tag 001: Vendor name

l Tag 002: VLAN ID
l Tag 003: DLS IP address

Optionally, the DLS address can be given in an alternative way:

l Tag 004: DLS hostname

The Vendor name tag is coded as follows (the first line indicates the ASCII values, the second
line contains the hexadecimal values):
54 Administration

Code Length Vendor name

1 7 S i e m e n s

01 07 53 69 65 6D 65 6E 73

The following example shows a VLAN ID with the decimal value "10":

Code Length VLAN ID

2 4 0 0 1 0

02 04 00 00 00 0A

The DLS IP address tag consists of the protocol prefix "sdlp://", the IP address of the DLS server,
and the DLS port number, which is "18443" by default. The following example illustrates the syn-
tax:

Cod- Lengt- DLS IP address

e h
3 25 s d l p : / / 1 9 2 . 1 6 8 . 3 . 3 0 : 1 8 4 4 3

03 19 73 64 6C 70 3A 2F 2F 31 39 32 2E 31 36 38 2E 33 2E 33 30 3A 31 38 34 34 33

Manual configuration of a VLAN ID

To configure VLAN manually, the phone must be provided with a VLAN ID between 1 and 4095.

Note If you misconfigure a phone to an incorrect VLAN, the phone will not connect to
the network. If in static IP mode, no server connections is possible.

Administration via WBM

1. Open Network > Wired settings.

2. Deselect “Use LLDP-MED”.

3. Set “VLAN discovery” to “Manual”.
Administration 55

4. Click Submit.

5. Enter the VLAN ID.

6. Click Submit.

Administration via local phone

IP Network parameters

Quality of Service (QoS)

The QoS technology based on layer-2 and the two QoS technologies Diffserv and TOS / IP Pre-
cedence based on layer-3 are allowing the VoIP application to request and receive predictable
service levels in terms of data throughput capacity (bandwidth), latency variations (jitter), and
delay.

Note Layer-2 and -3 QoS for voice and signaling transmission can be set via LLDP-MED
(see "Automatic VLAN discovery using LLDP-MED" à page 52). The value cannot
be changed by another interface.

Layer 2 / 802.1p
QoS on layer-2 is using 3 Bits in the 802.1q/p 4-Byte VLAN tag which must be added in the Eth-
ernet header.

The CoS (class of service) value can be set from 0 to 7. 7 is describing the highest priority and is
reserved for Network management. 5 is used for voice (RTP-streams) by default. 3 is used for
signaling by default.
56 Administration

Administration via WBM

1. Open Network > QoS.

l Layer x: Activates or deactivates QoS on layer 2.

n Value range: "Yes", "No"
n Default: "Yes"
l Layer x voice: Sets the CoS (Class of Service) value for voice data (RTP streams).
n Value range: 0-7
n Default: 5
l Layer x signalling: Sets the CoS (Class of Service) value for signaling.
n Value range: 0-7
n Default: 3
l Layer x default: Sets the default CoS (Class of Service) value.
n Value range: 0-7
n Default: 0

Administration via local phone

Layer-3 / Diffserv
Diffserv assigns a class of service to an IP packet by adding an entry in the IP header.

Traffic flows are classified into 3 per-hop behavior groups:

Administration 57

l Default: Any traffic that does not meet the requirements of any of the other defined
classes is placed in the default per-hop behaviour group. Typically, the forwarding has
best-effort forwarding characteristics. The DSCP (Diffserv Codepoint) value for Default is
"0 0 0 0 0 0".
l Expedited Forwarding (EF referred to RFC 3246): Expedited Forwarding is used for voice
(RTP streams) by default. It effectively creates a special low-latency path in the Network.
The DSCP (Diffserv Codepoint) value for EF is "1 0 1 1 1 0".
l Assured Forwarding (AF referred to RFC 2597): Assured forwarding is used for signaling
messages by default (AF31). It is less stringent than EF in a multiple dropping system.
The AF values are containing two digits X and Y (AFXY), where X is describing the priority
class and Y the drop level.
Four classes X are reserved for AFXY: AF1Y (low priority), AF2Y, AF3Y and AF4Y (high pri-
ority).
Three drop levels Y are reserved for AFXY: AFX1 (low drop probability), AFX2 and AFX3
(High drop probability). In the case of low drop level, packets are buffered over an exten-
ded period in the case of high drop level, packets are promptly rejected if they cannot be
forwarded.

Administration via WBM

1. Open Network > QoS.

l Layer 3: Activates or deactivates QoS on layer 3.

n Value range: "Yes", "No"
n Default: "Yes"
l Layer 3 voice: Sets the CoS (Class of Service) value for voice data (RTP streams).
n Value range: "BE", "AF11", "AF12", "AF13", "AF21", "AF22", "AF23", "AF31", "AF32",
"AF33", "AF41", "AF42", "AF43", "EF", "CS7", "CS3", "CS4", "CS5", 0, 1, 2 ... through 63.
n Default: "EF"
l Layer 3 signaling: Sets the CoS (Class of Service) value for signaling.
n Value range: "BE", "AF11", "AF12", "AF13", "AF21", "AF22", "AF23", "AF31", "AF32",
"AF33", "AF41", "AF42", "AF43", "EF", "CS7", "CS3", "CS4", "CS5", 0, 1, 2 ... through 63.
n Default: "AF31"
58 Administration

Administration via local phone

Use DHCP
If this parameter is set to "Yes" (default), the phone will search for a DHCP server on start-up and
try to obtain IP data and further configuration parameters from that central server.

Note The data obtained via DHCP cannot be changed with DHCP enabled. Also, when
DHCP is enabled, the data read from the server overwrites current values on the
phone

If no DHCP server is available in the IP network, deactivate this option. In this case, the IP
address, subnet mask, and default gateway / route must be defined manually.

Note The change will only have effect if you restart the phone. The phone is able to
maintain its IP connection even in case of DHCP server failure.

DHCP parameters

The following parameters can be obtained by DHCP:

l Basic Configuration
n IP Address
n Subnet Mask
l Optional Configuration
n Default Route (Routers option 3)
n IP Routing / Route 1 & 2 (Static Routes option 33), Classless static route option 121,
Private / Classless Static Route (Microsoft) option 249
n SNTP IP Address (NTP Server option 42)
n Timezone offset (Time Server Offset option 2)
n Primary / Secondary DNS (DNS Server option 6)
n DNS Domain Name (DNS Domain option 15)
n SIP Addresses / SIP Server & Registrar (SIP Server option 120)
n VLAN ID, DLS address (Vendor specific Information option 43)
Administration 59

Administration via WBM

1. Open Network > Wired settings.

2. Select “Use DHCP”.

3. Click Submit.

Administration via Local Phone

|--- Admin
|--- Network
|--- Wired settings
|--- LAN connection

Manual configuration of the IP address

If not provided by DHCP dynamically, you must specify the phone IP address and subnet mask
manually.

IP addresses can be entered in the following formats:

l Decimal format. Example: 11.22.33.44 or 255.255.255.0 (no leading zeroes).

l Octal format. Example: 011.022.033.044 (leading zeroes must be used with every
address block)
l Hexadecimal format. Example: 0x11.0x22.0x33.0x44 (prefix 0x must be used with every
address block)

By default, IP configuration by DHCP and LLDP-MED is enabled. For manual IP configuration, pro-
ceed as follows:

Data required

l IP address: used for addressing the phone.

l Subnet mask: subnet mask that is needed for the subnet in use.
60 Administration

Administration via WBM

1. Open Network > Wired settings.

2. Deselect “Use LLDP-MED”, “Use DHCP”, and “DHCPv6 enabled”.

3. In the tab “IPv4 routing”, enter the IP address, the gateway, and the (subnet) mask for
Route 1.
4. If applicable, enter the data for route 2.
5. Click Submit.

Administration via local phone

Default router / gateway

If not provided by DHCP dynamically, enter the IP address of the router that links your IP network
to other networks. If the value was assigned by DHCP, it is read-only.

Note The change will only have effect if you restart the phone.

Administration via WBM - IPv4

1. Open Network > Wired settings.

2. Enter the default route, i.e. the IP address of the router that links your IP network to other
networks.
3. Click Submit.

Administration via local phone - IPv4

Specific IP routing
To have constant access to network subscribers of other domains, you can enter a total of two
more network destinations, in addition to the default route/gateway. This is useful if the LAN has
more than one router or if the LAN is divided into subnets.

IPv4 route configuration

l Route 1/2 IP address: IP address of the selected route.

l Route 1/2 gateway: IP address of the gateway for the selected route.
l Route 1/2 mask: network mask for the selected route.
62 Administration

Administration via WBM - IPv4 configuration

1. Open Network > IPv4 configuration.

2. Enter the required data:

l For Route 1: Route 1 IP address, Route 1 Gateway, and Route 1 mask.
l For Route 2: Route 2 IP address, Route 2 Gateway, and Route 2 mask.
3. Click Submit.

Administration via local phone

DNS
The main task of the domain name system (DNS) is to translate domain names to IP addresses.
For some features and functions of the OpenScape Desk Phone CP phone, it is necessary to con-
figure the DNS domain the phone belongs to, as well as the name servers needed for DNS resolv-
ing.
Administration 63

DNS domain name

This is the name of the phone’s local domain.

Administration via WBM

1. Open Network > Common settings.

2. Enter the DNS domain the phone belongs to.

3. Click Submit.

Administration via local phone

|--- Admin
       |--- Network
             |--- Common settings
                   |--- DNS domain

DNS servers
If not provided by DHCP, a primary and a secondary DNS server can be configured.

When DHCP is enabled, the DNS server is read-only.

Note Depending on the configuration chosen for survivability, DNS SRV is required. For
details, refer to "Resilience and survivability" à1.

Administration via WBM

1. Open Network > Common settings.

2. Enter the name of the DNS domain.

64 Administration

3. Enter the IP addresses of the Primary DNS and the Secondary DNS server.
l Primary DNS: IP address of the primary DNS server.
l Secondary DNS: IP address of the secondary DNS server.
4. Click Submit.

Administration via local phone

Terminal host name

The phone host name can be customized.

Note DHCP and DNS must be appropriately connected and configured at the customer
site.

Note It is recommended to inform the user about the DNS name of the phone. The com-
plete WBM address can be found under User menu > Network information > Web
address.

The DNS name is constructed from pre-defined parameters and free text. Its composition is
defined by the DNS name construction parameter Administration > System > System Identity >
DNS name construction. The following options are available:

Administration via WBM

1. Open System > System Identity.

2. Select the DNS name construction.

l None: No host name is send to the DHCP server during DHCP configuration.
l MAC based: The DNS name is built from the prefix "OIP" followed by the phone’s
MAC address.
l Web name: The DNS name is set to the string entered in Web name.
l Only number: The DNS name is set to the Terminal number, i.e. the phone’s call
number (E.164).
Administration 65

l Prefix number: The DNS name is constructed from the string entered in Web name,
followed by the Terminal number.
3. Click Submit.

Administration via local phone

IP TTL
Defines the “Time-To-Live” (TTL) value in seconds within the IP header for any packet being sent
by the phone. The default value is “64”.

Note This parameter can be set through the WBM interface, the local phone or DLS.

Administration via WBM

1. Open Network > Common settings.

2. Select the desired value for “IP TTL”.

l Values: 64 or 128 (seconds)
3. Click Submit.

Administration via local phone

|--- Admin
|--- Network
|--- Common settings
|--- IP Time to live

Configuration & update service

All items can be administered by management applications in both OpenScape and non
OpenScape networks. Among the most important features are:
66 Administration

l Security (e.g. PSS generation and distribution within an SRTP security domain)
l Mobility for OpenScape SIP phones
l Software deployment
l Plug & play support
l Error and activity logging.

OpenScape Deployment Service (DLS) address, i.e. the IP address or host name of the DLS
server, and default mode port, i.e. the port on which the DLS server is listening, are required to
enable proper communication between phone and DLS.

The mode (labeled “Mode” in the local phone administration menu) determines the security level
for the communication between the phone and the DLS. Mutual authentication establishes a
higher security level of the connection by mutually exchanging credentials between the DLS and
the phone. After this, the communication is encrypted, and a different port is used, thus ensuring
that the phone is unambiguously connected to the correct DLS server.

It is possible to operate the DLS server behind a firewall or NAT (Network Address Translation),
which prevents the DLS from sending “Contact-Me” messages directly to the phone:

l The DLS server requests the phone to contact it by sending a HTTP “Contact-Me” request
or by leaving a request at the DCMP poll server for the phone to check periodically.
l The phone always establishes the connection to the DLS server.

Only outbound connections from the phone are allowed. To overcome this restriction, a DLS
“Contact-Me” proxy (DCMP) can be deployed. The phone periodically polls the DCMP, which is
placed outside of the phone network, for pending contact requests from the DLS. If there are con-
tact requests, the phone will send a request to the DLS in order to obtain the update, just as with
a regular DLS connection.

Note The URI of the DCMP, as well as the polling interval, are configured by the DLS. For
this purpose, it is necessary that the phone establishes a first contact to the DLS,
e. g. by phone restart or local configuration change.

A security PIN can be provided which is used for decrypting data provided by the DLS during
bootstrap. For further information, refer to the DLS documentation.

Device management service (DMS)

The DMS is a configuration file based deployment service which can be used instead of a DLS.
The DMS address can be provided manually or via DHCP for a full plug & play installation (see
"Setting the DMS address via DHCP" à page 42).

The DMS is compatible to the Broadsoft DMS and the RingCentral provisioning server. A detailed
description can be found here: https://wiki.unify.com/wiki/Device_Management_System
Administration 67

Administration via WBM

1. Open Network > Update Service (DLS).

Deployment service (DLS)

l DLS address: IP address or host name of the server on which the Deployment Service is
running.
l Default mode port: Port on which the DLS Deployment Service is listening.
n Default: 18443.
l Revert to default security disables mutual authentication and returns to DEFAULT mode.
SECURE mode related settings are reset and certificates are removed.
l Revert to default security: When set, security mode is set to default. When using local
phone administration, this is set by selection option “Default security”.
l Mode: Determines whether the communication between the phone and the DLS is secure.
Value range: "Default", "Secure", "Secure PIN". This parameter is read-only.
n Default: "Default".
l Security PIN: Used for enhanced security.

Device management service (DMS)

l DMS address: IP address or host name of the server on which the DMS is running.
l Username: User name for authentication.
l Password: Password for authentication.
l Minimum update check (seconds): Time between two configuration requests to the DMS.
l Update check during working hours: Enables checking for updates during office hours,
which may decrease performance.
l Ignore SW update from config file: Any software link provided by the DMS will be ignored.
l Check for Update: Now forces the phone to an immediate check for a new configuration.
68 Administration

Administration via local phone

SNMP
The Simple Network Management Protocol is used by network management systems for mon-
itoring network-attached devices for conditions that warrant administrative attention. An SNMP
manager surveys and, if needed, configures several SNMP elements, e.g. VoIP phones.

Note OpenScape Desk Phone CP phones support SNMPv1.

Trap categories

There are currently 3 trap categories that can be sent by the phones:

l Standard SNMP traps: OpenScape Desk Phone CP phones support the following types of
standard SNMP traps, as defined in RFC 1157:
n coldStart: sent if the phone does a full restart.
n warmStart: sent if only the phone software is restarted.
n linkUp: sent when IP connectivity is restored.
l QoS Related traps: These traps are designed specifically for receipt and interpretation by
the QDC collection system. The traps are common to SIP phones, HFA phones, Gateways,
etc.
l Traps specific to OpenScape Desk Phone CP phones. Currently, the following traps are
defined:
n TraceEventFatal: sent if severe trace events occur; aimed at expert users.
n TraceEventError: sent if severe trace events occur; aimed at expert users.
Administration 69

Administration via WBM

1. Open System > SNMP.

l Trap sending enabled: Enables or disables the sending of a TRAP message to the SNMP
manager. Value range: "Yes", "No" Default: "No"
l Trap destination: IP address or host name of the SNMP manager that receives traps.
l Trap destination port: Port on which the SNMP manager is receiving TRAP messages.
Default: 162
l Trap community: SNMP community string for the SNMP manager receiving TRAP mes-
sages. Default: "snmp"
l Queries allowed: Allows or disallows queries by the SNMP manager.
l Query password: Password for the execution of a query by the SNMP manager.
l Diagnostic sending enabled: Enables or disables the sending of diagnostic data to the
SNMP manager. Value range: "Yes", "No" Default: "No"
l Diagnostic destination: IP address or host name of the SNMP manager receiving dia-
gnostic data.
l Diagnostic destination port: Port on which the SNMP manager is receiving diagnostic
data.
l Diagnostic community: SNMP community string for the SNMP manager receiving dia-
gnostic data.
l Diagnostic to generic destination: Enables or disables the sending of diagnostic data to a
generic destination. Value range: "Yes", "No" Default: "No"
l QoS traps to QCU: Enables or disables the sending of TRAP messages to the QCU server.
Value range: "Yes", "No" Default: "No"
70 Administration

l QCU address: IP address or host name of the QCU server.

l QCU port: Port on which the QCU server is listening for messages. Default: 12010.
l QCU community: QCU community string. Default: "QOSCD".
l QoS to generic destination: Enables or disables the sending of QoS traps to a generic des-
tination. Value range: "Yes", "No" Default: "No"

Administration via local phone

OpenScape service menu

The phone local menu allows for controlling functions provided the OpenScape system. For this
purpose, the phone must be logged on at the system.

For information on the available functions, see the phone's user manual.

Administration via local phone

|---Service Menu

Wi-Fi settings
Note Wi-Fi operation requires a CP10 to be plugged in to the USB port of CP710, CP410
and CP210, and the USB port must be enabled (see "Feature access" à page 1).

Wi-Fi parameters can be configured via WBM and local settings. You can activate or deactivate
Wi-Fi network access and set up new Wi-Fi networks that is added to Stored Wi-Fi networks, to
be used by the phone.
Administration 71

Wi-Fi connection with encryption type WPA2-PSK with pre-shared key using AES are char-
acterized as secure network. Only the EAP-TLS authentication protocol is supported.

Wi-Fi connections with no encryption type, WEP or WPA are characterized as non-secure networks.

The authorization by name and password is optional. User certificate and root certificate are
also optional. The administrator can upload both certificates to phone via DLS. If more than one
certificates are uploaded, the administrator can choose which certificate is used.

Certificates are uploaded to phone only via DLS. There is the option to upload common cer-
tificates to be used for all networks or SSID specific ones. Common sets of certificates will also
have common backup pair. For each SSID the administrator can use common or SSID specific
certificates.

Note If WPA-EAP Network is added common certificates are used as default, with no
option to choose SSID specific certificates.
72 Administration

Administration via WBM

1. Open Network > Wi-Fi settings.

2. Enable the Wi-Fi interface. If disabled or without an inserted CP10 USB dongle, the phone
can only connect via Ethernet cable.

l Wi-Fi MAC Address: MAC address of the Wi-Fi interface, normally the LAN MAC address
+ 2.
n Read from the device and read-only
l Last connected Wi-Fi network name: SSID of last connected WLAN network.
n Read-only
l Wi-Fi link status: "down", "up", "connected", "failure".
n Read-only
l Wi-Fi country settings: ISO 3166 2 letter country code used to customise the Wi-Fi oper-
ation (independent of the phone's country setting)
l For Advanced settings see "Advanced Wi-Fi settings" à page 74
Administration 73

Add new Wi-Fi network: Allows a WLAN network to be defined and saved

l Wi-Fi SSID: The Service Set Identifier that is your network's name.
l Hidden SSID: Enable this to not show the SSID in the list of saved networks.
l Wi-Fi password: The encryption type is either "None" or "EAP".
l IP settings: Sets the discovery mode as "DHCP" or "manual".
l IP address / Subnet mask / Default route: The discovery mode is "manual”.
l Authentication protocol: Either "None", PEAP", "TLS", "LEAP" or "FAST"(when the Encryp-
tion type is "EAP").
l EAP anonymous identity: Name to display rather than real identity, when authentication is
one of "PEAP", "TLS" or "FAST".
l EAP identity: Full user name when authentication is "NONE".
l EAP password: When authentication is one of "PEAP", "TLS" or "FAST" .
l Stored Wi-Fi networks: A summary list of saved WLAN networks.

Administration via local phone

|--- Admin
|--- Network
|--- Wi-Fi settings

Setting up a WiFi connection

When a WiFi-enabled phone is set up for the first time using only Wi-Fi to establish a LAN con-
nection, a temporary Wi-Fi connection is used. The device is connected to a predefined WiFi with
the following configuration:

l SSID: AWS-INIT
l Security key: WPA-PSK / WPA2-PSK
l WPA-PSK passphrase: AWS-INIT

All other Network parameters are at their default settings:

l DHCP mode: On
l 11 protocol: 802.11b/g/n
l 11b/g/n channels: 1,6,11
l World mode regulatory domain: World mode (802.11d)

If the phone is not successfully connected to this Wi-Fi within ten seconds, it will try to connect
to an unsecured Network for ten seconds. If this also fails, it will continue to try these two altern-
atives for ten seconds each until one succeeds. This process can also be interrupted by con-
figuring the phone either through the local phone menu or through the DLS using prestaging. As
soon as one of the Networks A-D has a SSID filled in, probing of AWS-INIT will stop.

Wi-Fi discovery requires that the DHCP server is configured to return a valid DLS IP address as
part of the DHCP response sent to the phone. The DLS IP address is sent using DHCP Option 43
(vendor specific data).
74 Administration

Once the phone has acquired a DLS address, it will open up a secure connection to DLS for down-
loading configuration parameters using the WPI protocol. Any certificates needed for Wi-Fi
authentication or SIP/TLS will also be downloaded as a part of this process. If a DLS address is
specified in the downloaded configuration, that DM is used subsequently. If not, the DLS dis-
covery procedure is used for each time the phone is started. The downloaded configuration
should also contain a new Network configuration, which will cause the phone to disconnect from
the AWS-INIT SSID.

Disable LAN port

The OpenScape Desk Phones CP210, CP410, and CP710 provide the option to disable the LAN
port connection when a Wi-Fi network is configured.

Administration via WBM

1. Open Network > Wired settings.

2. Enable or disable the LAN port.

l When the LAN port is disabled, the Ethernet connection is not supported.
l The LAN port may be disabled whether Wi-Fi LAN is enabled or disabled. When the
LAN port is disabled the Wi-Fi LAN is automatically enabled, if not already enabled,
and cannot be disabled.
3. Click Submit.

Administration via local phone

|--- Admin
|--- Network
|--- LAN port configuration

Advanced Wi-Fi settings

The OpenScape Desk Phones CP210, CP410, and CP710 provide advanced Wi-Fi options to
reduce downtime during Wi-Fi roaming process.

Advanced Wi-Fi options

1. Select one of the following options to set the frequency band:

l All (5 GHz + 2.4 GHz)
l 5 GHz
l 2.4 GHz
Administration 75

2. Select one of the following options to configure only a specific subset of allowed fre-
quencies during Network scan and Wi-Fi operation:
l All
l Non DFS
l UNII-1
l UNII-3
l UNII-1, UNII-2
l UNII-1, UNII-2, UNII-3
l UNII-1, UNII-2 Extended

Channel denomination for 5 GHz

Channel denomination Channels

Non DFS 36, 40, 44, 48, 149, 153, 157, 161, 165

UNII-1 36, 40, 44, 48

UNII-2 52, 56, 60, 64

UNII-2 Extended 100, 104, 108, 112, 116, 120, 124, 128, 132, 136, 140

UNII-3 149, 153, 157, 161, 165

Manual selection of allowed channels (5GHz)

Allowed channels can be specified as a comma separated list of channel numbers, i.e. you can
manually allow UNII-1 channels by a list "36, 40, 44, 48".

Invalid inputs are rejected:

l Allowed characters are numbers, comma and optional white space characters.
l Invalid channel numbers for 5 GHz. If selected list of allowed channels is in conflict with
active regulatory domain, then only channels valid for active regulatory domain are used.
l If new input is invalid but previous value of Manual selection of allowed channels (5 GHz)
was valid, then the new value is rejected and the previous value is kept (to prevent from
invalid configuration).
l If new input is invalid and previous value was empty, then value of field Allowed channels
(5 GHz) is automatically changed to All when user leaves the dialog and discards the
changes (to prevent from invalid configuration).

Allowed channels (2.4 GHz)

1. Select one of the following options to configure only a specific subset of allowed fre-
quencies during Network scan and Wi-Fi operation:
l All
l 1, 6, 11
76 Administration

Manual selection of allowed channels (2.4 GHz)

Allowed channels can be specified as a comma separated list of channel numbers, i.e. you can
manually allow channels by a list "1, 2, 3, 4".

Invalid inputs are rejected:

l Allowed characters are numbers, comma and optional white space characters.
l Invalid channel numbers for 2.4 GHz. If selected list of allowed channels is in conflict with
active regulatory domain, then only channels valid for active regulatory domain are used.
l If new input is invalid but previous value of “Manual selection of allowed channels (5
GHz)” is valid, the new value is rejected and the previous value is kept (to prevent from
invalid configuration).
l If new input is invalid and previous value is empty, then value of field “Allowed channels (5
GHz)” is automatically changed to “All” when user leaves the dialog and discards the
changes (to prevent from invalid configuration).

Enable 802.11r (Fast BSS Transition)

Select one of the following values:

l True
l False

Roaming RSSI threshold

1. Edit the text field to configure the roaming RSSI threshold. Value can be set as a negative
integer (RSSI value in dBm).

Invalid inputs is rejected:

l Valid input is negative integer from range -30 to -90. Any other input is considered invalid
(alphabetic characters except minus sign, positive integers or integers outside of the spe-
cified range).

Administration via WBM

1. Open Network > Wi-Fi settings > Advanced settings.

Fields are the same as in Local, except:

Administration 77

l “Manual selection of allowed channels (5 GHz)” and “Manual selection of allowed chan-
nels (2.4 GHz)” do not dynamically change their read-only status (they are always writ-
able).
l If “Allowed channels (5 GHz)” is not set to “Manual selection”, any input in “Manual selec-
tion of allowed channels (5 GHz)” is ignored.
l If field “Allowed channels (2.4 GHz)” is not set to “Manual selection”, any input in field
“Manual selection of allowed channels (2.4 GHz)” is ignored.

Administration via local phone

|--- Admin
|--- Network
|--- Wi-Fi settings
|--- Advanced settings

System
OpenScape Desk Phone CP phones support the following security option:

l PKI-based SPE (Signaling and Payload Encryption)

The security settings are be configured separately for the main gateway and for the fallback
gateway (standby) when using SRSR (Small Remote Site Redundancy).

The signalling transport main / standby parameter selects the protocol to use for signalling. TCP
and TLS are avaliable.

Certificate validation shows whether the phone certificate used for encrypted logon via TLS is
checked against the certificate on the server (and the level of checking). For configuration see
"Authentication policy" à page 135.

Note For further information on deploying SPE, refer to the manual of the OpenScape
system in use, and to the Deployment Service Administration manual.

Administration via WBM

1. Open System > Security > System.

l Validate SW upgrade: validates if the uploaded Phone software is compatible with the
phone.
l DoS protection: activates protection against “Denial-of-service” attacks that may cause
the network to overload.
78 Administration

Administration via local phone

|--- Administration

|--- System

|--- Security

|--- System

HFA gateway settings

To connect the OpenScape Desk Phone CP phone to the OpenScape system, the data described
in the following are required.

The Gateway address is the IP address of the communication platform or HFA server.

The Gateway port is the port used by the HFA server for signaling messages. Usually, the default
value "4060" is correct.

The Subscriber number is used as the internal extension number of the phone. It can be 1 to 24
characters long.

To log on to the HFA server, a subscriber password must be provided. A new subscriber pass-
word can be entered by the administrator.

The System type is provided by the system the phone is connected to and therefore read-only.

Administration via WBM

1. Open System > Gateway.

2. Select the system tape and provide the following information:

l IP address: IP or DNS address of the communication platform or HFA server.
l Subscriber number: The phone extension.
l Password: Password for logging on to the HFA server.
Administration 79

3. Click Submit.
4. Open Network > Port number configuration.

Optionally, a Gateway ID can be provided. The Gateway ID refers to the PBX / Gateway / Gate-
keeper to which the phone is connected. The value is the same as the "Globid" parameter in the
OpenScape 4000 or "H.323 ID" in the OpenScape Business.

Administration via local phone

|--- Admin

|--- System

|--- Gateway

|--- System type

|--- IP address

|--- Gateway ID

|--- Subscriber number

|--- Password

|--- Admin

|--- Network

|--- Port configuration

|--- Gateway
80 Administration

HFA emergency gateway settings

For enabling survivability, the phone switches to a backup communications system in case the
main system fails.

The settings are analog to those for the main system (see "HFA gateway settings" à page 78).

Administration via WBM

1. Open System > Standby gateway.

2. Enter the IP address and gataway ID.

3. Enter the subscriber number and password.
4. Click Submit.
5. Open Network > Port number configuration.

6. Enter the standby gateway ID.

7. Click Submit.

Administration via local phone

|--- Admin
Administration 81

|--- System

|--- Standby gateway

|--- System type

|--- IP address

|--- Gateway ID

|--- Subscriber number

|--- Password

|--- Admin

|--- Network

|--- Port configuration

|--- Standby gateway

Server and standby server ports

In this section, the server ports for signalization and speech data transfer are determined.

Administration via WBM

1. Open Network > Port number configuration.

l H.225.0 port determines the port used for non-secure H.225 signaling. Default: 1720.
l CorNet-TC TLS port determines the port used for secure communication by the HFA
server.
l H.225.0 TLS port determines the port used for secure H.225 signaling.

Administration via local phone

|--- Admin

|--- Network

|--- Port configuration

|--- Server port configuration

| |--- H.225.0 port

| |--- TC TLS port

| |--- H.225.0 TLS port

82 Administration

|--- Standby server port configuration

|--- H.225.0 port

|--- TC TLS port

|--- H.225.0 TLS port

Redundancy
This section controls the switching between main HFA server and standby HFA server.

Administration via WBM

1. Open System > Redundancy.

l When “Small remote side redundancy” is activated, the phone switches to the standby
HFA server if the connection to the main server is lost. By default, this is disabled.
l When “Auto switch back” is activated, the phone will switch back to the main server as
soon as the connection is re-established. By default, this is disabled.
l “Retry count main” sets the number of trials to establish a connection to the main server
before the phone switches over to the standby server. The default is 1.
l The “Timeout main” determines the time interval between the last try to get a connection
to the main server and the establishing of a connection to the standby server. The default
is 30.
l “Retry Count Standby” sets the number of trials to establish a connection to the standby
server before the phone switches back to the main server. The default is 3.
l “Timeout Standby” sets the timeout between two "Retry count standby". The default is 30.
l “Timeout main” sets the timeout between two "Retry count main". The default is 30.
l “TC test retry” determines the count of how many successful TC tests the main system
needs to answer before the phone switches back with Auto switchback enabled. The
default is 3.
l “TC Test Expiry” determines how long the Previous connection needs to timeout to actu-
ally trigger any further SRSR activities.
How much time to wait from one unsuccessful retry count main sequence until the next
happens and in which interval the phone will send itself a TC test message (in idle mode).
The default is 30.
Lowering this value will significantly increase Network load but the phone might detect
failures faster but at an increased risk of false positive detections due to short time Net-
work outage.
After a change of the timing values the SRSR need to be deactivated and re-activated
again to take effect.

Administration via local phone

|--- Admin

|--- System
Administration 83

|--- Redundancy

|--- Small remote site

|--- Auto switch back

|--- Retry count main

|--- Timeout main

|--- Retry count stdby

|--- Timeout standby

Emergency number
E.911 emergency number. This number establishes a connection to the PSAP (Publiy Safety
Answering Point). If a user dials this number, and an appropriate LIN (see "LIN" à page 84) is
configured, the user location is communicated to the PSAP. In the US, the number is 911.

Administration via WBM

1. Open System > Features > Configuration.

2. Enter the emergency number.

3. Click Submit.
84 Administration

Administration via local phone

|--- Admin

|--- System

|--- Features

|--- Configuration

|--- General

|--- Emergency number

LIN
The Location Identification Number (LIN) is a number code that provides detailed geographic
information about the phone, including the office room. On issuing an emergency call using the
E.911 emergency number (see "Emergency number" à page 83), this code is transferred to an
ALI (Automatic Location Information) system in the public Network. When the ALI has looked up
the location data in its database, it transmits the data along with the call to the PSAP. The emer-
gency operator is presented with the location data in readable form, so he can dispatch help as
appropriate.

Administration via WBM

1. Open System > Features > Configuration.

Administration via local phone

|--- Admin

|--- System

|--- Features

|--- Configuration

|--- General

|--- LIN

Not used timeout

Note This feature is available only on OpenScape Desk Phone CP410 and CP710
phones.
Administration 85

The timeout for the local user and admin menu is configurable. When the time interval is over,
the menu is closed and the administrator / user is logged out.

The timeout may be helpful in case a user does a long press on a line key unintentionally, and
thereby invokes the key configuration menu. The menu will close after the timeout, and the key
will return to normal line key operation.

Administration via WBM

1. Open System > Features > Configuration.

2. Set the interval for the "Not used timeout". The timeout ranges from 1 to 5 minutes.
l The default value is 2 (minutes).

3. Click Submit.

Administration via local phone

|--- Admin

|--- System

|--- Features

|--- Configuration

|--- General

|--- Not used timeout

86 Administration

Enable telephony settings

Note This feature is available only on OpenScape Desk Phone CP410 and CP710
phones.

Users can access limited menu options and set basic telephony settings without the need of a
password. Since the administrator enables the option "Enable telephony settings", the item "Con-
figure telephone" appears on the telephone screen while navigating from the idle menu to Ser-
vice/Settings.

The user password is not required to navigate to this option. The option is disabled by default.

Administration via WBM

1. Open System > Features > Configuration.

Administration via local phone

|--- Admin

|--- System

|--- Features

|--- Configuration

|--- Telephony settings

|--- Enable telephony settings

Energy saving

Backlight time setting

Note This feature is available only on OpenScape Desk Phone CP410 and CP710
phones.

After the phone has been inactive within the time span specified, the display backlight is
switched off to save energy.

This parameter can also be configured by the user.

Administration 87

Administration via WBM

1. Open User settings > Phone > Energy saving.

2. Set the backlight time interval.

l Value range: 1 minute, 5 minutes, 30 minutes, 60 minutes, 2 hours, 4 hours, or 8
hours.
l Default value: 1 minute.

Administration via local phone

|--- User settings
|--- Phone
|--- Energy saving

Energy efficient Ethernet

The OpenScape Desk Phone CP110 / CP210 / CP410 / CP710 phones support the standard IEEE
802.3az (Energy efficient Ethernet).

The energy saving benefit provided by this standard can only be received when the phone is con-
nected to a network component which also is able to support the IEEE 802.3az standard.

System
OpenScape Desk Phone CP phones support the following security option:

l PKI-based SPE (Signaling and Payload Encryption)

The security settings are be configured separately for the main gateway and for the fallback
gateway (standby) when using SRSR (Small Remote Site Redundancy).

The signalling transport main / standby parameter selects the protocol to use for signalling. TCP
and TLS are avaliable.

Note For further information on deploying SPE, refer to the manual of the OpenScape
system in use, and to the Deployment Service Administration manual.
88 Administration

Administration via WBM

1. Open System > Security > System.

Administration via local phone

|--- Administration

|--- System

|--- Security

|--- System

Access control

Administration via WBM

1. Open System > Security > Access control.

l The CCE access parameter controls TCP and UDP access for the CCE (CommsChannel
Extender). This affects the operation of the local CTI access, and HPT access. When Dis-
able is selected, both TCP and UDP are disabled. With Enable, there are no restrictions.
l With Factory reset claw, the “hooded claw” keypad mechanism to initiate a factory reset
without requiring an authenticated access can be enabled or disabled.
l The Serial port parameter controls access to the serial port.
n When set to “No password”, a terminal connected to the port can interact with the
phone operating system without restrictions.
n When “Passwd reqd” is selected, the serial port requires a password for access (root
user is not available). When Unavailable is chosen, the serial port is not accessible.
Administration 89

n As a prerequisite, the root user needs to create a user and to define a password via
Serial Access, so that access can be granted when the Password required prompt is
issued.
l WBM TLS interface allows the web server to support obsolete TLS versions (TLS 1.0 and
TLS 1.1) as well as the latest versions (current latest version is TLS 1.2). By default the
latest TLS version is allowed. Other interfaces are not affected by this setting.
l Server TLS interface allows the web server to support obsolete TLS versions (TLS 1.0
and TLS 1.1) as well as the latest versions (current latest version is TLS 1.2). By default
the latest TLS version is allowed.

Administration via local phone

Security log
A circular security log is used to capture important security specific events. It can be exported
as CSV data to an external application for analysis.

Note The security log cannot be disabled.

Administration via WBM

1. Open System > Security > Logging.

l The Max. lines parameter defines the maximum number of entry lines that can be kept in
the security log before old entries are overwritten by new entries.
l Automatic archive to DLS controls whether the log is sent to the DLS. When activated, the
DLS is used to automatically archive the security log so that no log entries is lost.
l Archive when at: This value sets the trigger for log archiving. Automatic archiving of new
security log entries will occur when the percentage of unarchived entries in the log is as
specified or more. The value may be set to 0% by both the phone and the DLS and this
value will prevent the phone from archiving or telling the DLS that it needs archiving.
90 Administration

l The security log upload may be accomplished in two ways:

n If "Automatic archive to DLS" is enabled, if the security log reaches the threshold %
for unachieved entries, the phone will initiate an upload.
n If "Automatic archive to DLS" is NOT enabled and the security log reaches the
threshold % for unachieved entries, the phone only sets the "archive-me" flag, it does
not initiate the archive.
It is up to the DLS to recognize the flag and initiate an upload.
l Last archived shows the date when the security log was last archived to the DLS.

Administration via local phone

|--- Administration

|--- System

|--- Security

|--- Logging

|--- Max. lines

|--- Automatic archive to DLS

|--- Archive when at

|--- Last archived

Date and time

If the DHCP server in the Network provides the IP address of the SNTP server, no manual con-
figuration is necessary. If not, you have to set the SNTP IP address parameter manually.

For correct display of the current time, the Timezone offset must be set appropriately. This is the
time offset from UTC (Universal Time Coordinated). If, for instance, the phone is located in
Munich, Germany, the offset is +1 (or simply 1); if it is located in Los Angeles, USA, the offset is -
8. For countries or areas with half-our time zones, like South Australia or India, non-integer val-
ues can be used, for example 10.5 for South Australia (UTC +10:30).

If the phone is located in a country with DST (Daylight Saving Time), you can choose whether
DST is toggled manually or automatically.

l For manual toggling, disable “Auto time change” and enable or disable “Daylight saving”;
the change is in effect immediately.
l For automatic toggling, enable “Auto time change”. Daylight saving is controlled by the
DST zone / time zone parameter. This parameter determines when DST starts or ends,
and must be set according to the location of the phone.
Administration 91

The difference (minutes) parameter defines how many minutes the clock is put forward for DST.
In Germany, for instance, the value is +60.

Note The Difference (minutes) must be specified both for manual and automatic DST
toggling.

Settings via SNTP

Administration via WBM

1. Open Date and time.

l SNTP primary: IP address or host name of the SNTP server

l SNTP backup: Secondary SNTP server
l Source: The time zone server. The DST settings do not apply when the source is set to
local ("System").
l Timezone offset (hours): Shift in hours corresponding to UTC.
l Daylight saving: Enables or disables DST in conjunction with "Auto time change".
n Value range: "Yes", "No".
l Difference (minutes): Time difference when DST is in effect.
l Auto time change / Auto DST: Enables or disables automatic control of daylight saving
time according to the DST zone.
n Value range: "Yes", "No".
n Default setting is Yes. After a factory reset, the system is reset to this value.
l DST zone: Area with common start and end date for daylight saving time.
n Value range: "Australia 2007 (ACT, South Australia, Tasmania, Victoria)", "Australia
2007 (New South Wales)", "Australia (Western Australia)", "Australia 2008+ (ACT,
New South Wales, South Australia, Tasmania, Victoria)", "Brazil", "Canada", "Canada
(Newfoundland)", "Europe (Portugal, United Kingdom)", "Europe (Finland)", "Europe
(Rest)", "Mexico", "United States", "New Zealand", "New Zealand (Chatham)".
n Default setting for US is "United States". After a factory reset, the system is reset to
this value.
92 Administration

Administration via Local Phone

Dialing

Canonical dialing configuration

Call numbers taken from a directory application, LDAP for instance, are mostly expressed in
canonical format. Moreover, call numbers entered or imported (e.g. from Outlook) into the local
phone book are automatically converted and stored in canonical format, thereby adding "+", local
country code, local national code, and local enterprise number as prefixes.

Example

The user enters the extension "1234", the local country code is "49", the local national code is
"89", and the local enterprise number is "722". The resulting number in canonical format is
"+49897221234".

Note To enable the number conversion, all parameters not marked as optional must be
provided, and the canonical lookup settings must be configured (see "Canonical
dialing look-up" à page 161).
Changes to these parameters can impact the phone's ability to match calls to con-
tacts.

Administration via WBM

For generating an appropriate dial string, a conversion from canonical format may be required.
The following parameters determine the local settings of the phone, like Local country code or
local national code, and define rules for converting from canonical format to the format required
by the PBX.
Administration 93

1. Open Local functions > Locality > Canonical dial settings.

l Local country code: E.164 country code, e.g. "49" for Germany, "44" for United King-
dom
n Maximum length: 5
l National prefix digit: prefix for national connections, e.g. "0" in Germany and United
Kingdom
n Maximum length: 5
l Local national code: local area code or city code, e.g. "89" for Munich, "20" for Lon-
don
n Maximum length: 6
l Minimal local number length: minimum number of digits in a local PSTN number,
e.g. 3335333 = 7 digits
l Local enterprise node: number of the company/PBX wherein the phone is residing
n Maximum length: 10 (optional)
l PSTN access code: access code used for dialing out from a PBX to a PSTN
n Maximum length: 10 (optional)
l International access code: international prefix used to dial to another country, e.g.
"00" in Germany and United Kingdom.
n Maximum length: 5
l Operator codes: List of extension numbers for a connection to the operator. The
numbers entered here are not converted to canonical format
n Maximum length: 50 (optional)
l Emergency numbers: List of emergency numbers to be used for the phone. If there
are more than one numbers, they must be separated by commas. The numbers
entered here are not converted to canonical format.
n Maximum length: 50 (optional)
94 Administration

l Initial extension digits: List of initial digits of all possible extensions in the local
enterprise network. When a call number could not be matched as a public network
number, the phone checks if it is part of the local enterprise network. This is done
by comparing the first digit of the call number to the value(s) given here. If it
matches, the call number is recognized as a local enterprise number and pro-
cessed accordingly.
For instance, the extensions 3000-5999 are configured in the OpenScape Desk
Phone, each number will start with 3, 4, or 5. Therefore, the digits to be entered are
3, 4, 5.
l Expect dial number: Indicates when PSTN access code and national prefix digit is
retained and not converted into the international access code
2. Open Local functions > Locality > Canonical dial.

l Internal numbers

Note To enable the phone to discern internal numbers from external numbers, it
is crucial that a canonical lookup table is provided ("Canonical dialing look-
up" à page 161).

n "Local enterprise form": Default value. Any extension number is dialed in its simplest
form. For an extension on the local enterprise node, the node ID is omitted. If the
extension is on a different enterprise node, then the appropriate node ID is prefixed to
the extension number. Numbers that do not correspond to an enterprise node exten-
sion are treated as external numbers.
n "Always add node": Numbers that correspond to an enterprise node extension are
always prefixed with the node ID, even those on the local node. Numbers that do not
correspond to an enterprise node extension are treated as external numbers.
n "Use external numbers": All numbers are dialed using the external number form.
l External numbers
n "Local public form": Default value. All external numbers are dialed in their simplest
form. Thus a number in the local public network region does not have the region code
prefix. Numbers in the same country but not in the local region are dialed as national
numbers. Numbers for a different country are dialed using the international format.
n "National public form": All numbers within the current country are dialed as national
numbers, thus even local numbers will have a region code prefix (as dialing from a
mobile). Numbers for a different country are dialed using the international format.
n "International form": All numbers are dialed using their full international number
format.
l External access code
n "Not required": The access code to allow a public network number to be dialed is not
required.
Administration 95

n "For external numbers": Default value. All public network numbers is prefixed with the
access code that allows a number a call to be routed outside the enterprise network.
However, international numbers that use the + prefix will not be given access code.
l International gateway code:
n "Use national code": Default value. All international formatted numbers is dialed expli-
citly by using the access code for the international gateway to replace the "+" prefix.
n "Leave as +": All international formatted numbers is prefixed with "+".

Administration via local phone

Canonical dial look-up

The parameters given here are important for establishing outgoing calls and for recognizing
incoming calls.

In the local phone book, and, mostly, in LDAP directories, numbers are stored in canonical
format. In order to generate an appropriate dial string according to the settings in Internal num-
bers and External numbers, internal numbers must be discerned from external numbers(see
"Canonical dialing configuration" à page 92). The canonical look-up table provides patterns
which allow for operation.

Furthermore, these patterns enable the phone to identify callers from different local or inter-
national telephone networks by looking up the caller’s number in the phone book. As incoming
numbers are not always in canonical format, their composition must be analyzed first. For this
96 Administration

purpose, an incoming number is matched against one or more patterns consisting of country
codes, national codes, and enterprise nodes. Then, the result of this operation is matched
against the entries in the local phone book.

Note To make sure that canonical dial look-up works properly, at least the following
parameters of the phone must be provided:

l Local country code

l Local area code
l Local enterprise code

You can view and edit the first five entries via the WBM. The Local code 1…5 parameters define
up to 5 different local enterprise nodes, whilst International code 1…5 define up to 5 international
codes, that is, fully qualified E.164 call numbers for use in a PSTN. The whole list of entries are
not visible on the phone but can be seen and handled using the DLS.

Administration via WBM

1. Open Locality > Canonical dial lookup.

l Local code 1…5: Local enterprise code for the node / PBX the phone is connected to.
n Example: "7007" for Unify office in Munich.
l International code 1…5: Sequence of "+", local country code, local area code, and local
enterprise node corresponding to one or more phone book entries.
n Example: "+49897007" for Unify office in Munich.
Administration 97

Administration via local phone

Distinctive ringing
The HFA server may provide information indicating a specific type of call within an incoming
call. The phone can use this information to choose a ring tone according to the call type. A list of
different ring types is maintained in the phone.

Any ringer sound may either be

l OpenScape specified tones

l Audio file (selected from the pool of ringer files on the phone)
l Constructed (from melody and tone sequence settings)

The ringer sounds are system controlled by default.

Note Once distinctive ringing is configured locally a system control of the ringer para-
meters is not possible. If system control of the ringer is desired the ringer mode
must be set to "OpenScape".

Even though the ringers are configured locally the behaviour of the ringers should be the same
as system controlled ones. In particular, cyclic ringers shall be played endlessly until the switch
commands to stop playing (and therefore repeated if necessary), whereas single shot ringers
should play for just a short period - the intention being to alert the phone user to a new state of
the phone but not to hinder the ongoing conversation. This short period is defined to be 3 sec
onds. It should be possible to interrupt the playing of the cyclic ringer to play the single shot
ringer and after timeout the cyclic ringing should resume. This behaviour is independent of
whether low or high quality ringer files are played or whether the ringer is pattern generated.

The value in Octet 12 in the CorNet AU_RINGER_START message is used as an index into ringers
configured on the phone. The indexed entry indicates the ringing to be used for the call.
98 Administration

In any cases if a distinctive ring is requested then the associated ring type is used instead of the
default ringer. The ringing is played immediately when requested. If distinctive ringing is not
requested or cannot be matched to a ringer then, the tone specified in the CorNet ringer mes-
sage by the OpenScape system will be used to construct the ring tone.

Distinctive ringer naming

There is no configuration necessary to set the names. CorNet specifies the ringer types and enu-
merations. Please be aware that the naming refers to the call type as sent in the CorNet mes-
sage, not to be confused with a feature or a call scenario. The mapping of call type to feture or
call scenario occurs in the system and this may be configurable. It is up to the administrator to
configure such that the user hears the required ring tones for the various features or call scen-
arios. Also note that only the set of call types actually implemented by the system should be
offered for configuration of the ringers.

Currently OpenScape Business only implements a subset of those in CorNet. It is assumed that
this set is relatively stable.

Ringer setting and preview

The configuration of distinctive ringers overlaps considerably with the general ringer con-
figuration feature and the ability to preview (manually and automatically) what a ringer sounds
like.

Administration via WBM

1. Open Ringer > Local ringers.

2. Select the ringer sound, pattern melody and sequence for each name.
l Ringer sound: "Pattern" or the name of the selected ring tone file. Sets the dis-
tinctive ringer to use the currently set pattern (melody and sequence). This is the
pattern that will be used if the configured ring tone file cannot be played for any
reason.
n Value range: "Pattern", "<audio file>"
n Default: "Pattern".
l Pattern melody: Selects the melody pattern that will be used if Ringer sound is set
to "Pattern".
n Value range: "1"... "8"
n Default: "2".
Administration 99

l Pattern sequence: Determines the length for the melody pattern, and the interval
between the repetitions of the pattern.
n Value range: "1": 1 sec ON, 4 sec OFF "2": 1 sec ON, 2 sec OFF "3": 0.7 sec ON,
0.7 sec OFF, 0.7 sec ON, 3 sec OFF
n Default: "2".
3. Click Submit.
4. Open Ringer >Ringer setting.

5. Select the ringer mode that determines the source of ringer tone.
l Value range: "OpenScape", "Local ringer"
l Default: "OpenScape".
6. Click Submit.

Administration via local phone

|--- Admin

|--- Settings

|--- Ringer

|--- Local ringer

| |--- Name

| |--- Ringer sound

| |--- Ringer melody

| |--- Ringer sequence

|--- Ringer Setting

|--- Options

|--- User changeable

|--- Ringer mode

|--- Emergency ringer mode

User mobility
The “Set Mobility Mode” parameter controls the behavior of the phone if mobile user logs on to
the phone.
100 Administration

1. Open User mobility > Set mobility mode.

2. Select the mobility type:

l Basic (Default): When a new user logs on at the phone, all user data of the pre-
cedent user is shown.
l Data Privacy: When a new user logs on at the phone, an empty conversation list is
presented to the mobile user. When the mobile user logs off, all conversation list
entries which have been created while he was using the phone, is deleted. No syn-
chronization to and from DLS will happen.
3. Select the number of log-on attempts from the drop-down menu.
4. Click Submit.

Free programmable keys

The key programming can be accessed via the local phone and via DLS / DMS.

l The OpenScape Desk Phone CP710 comes with 12 free programmable keys with LED
(red / green / amber), all of which can be programmed on two separate levels. The 6 first
programmable keys are permanently displayed on the left panel. The 6 last pro-
grammable keys are available in “Favorites”. The number of programmable keys can be
increased by attaching one or more OpenScape key modules to the phone, with up to four
KM710 providing 12 FPKs each or up to four KM410 providing 16 FPKs each.
l The OpenScape Desk Phone CP410 phone provides 16 free programmable keys (FPKs)
when a key module is not plugged in, which can be associated with special phone func-
tions. These are called „Phone keys“. Alternatively, the OpenScape Desk Phone CP410
can have up to four key modules KM410 providing 16 FPKs each, or up to four KM710
providing 12 FPKs each.
l The OpenScape Desk Phone CP210 phone provides four free programmable keys (FPKs).
This is called „Phone keys“.
l The OpenScape Desk Phone CP110 phone provides three free programmable keys
(FPKs). These are called „Phone keys“.

Enabling "Long Press" for FPKs

Note The long press feature is enhanced for the CP210.

Prerequisites

At the phone, the configuration menu for a specific programmable key is called by a long press
on the related key. However, the other methods for key programming remain enabled.
Administration 101

Selected dial action on calls

This feature allows the user to perform a certain action, while a selected dialing FPK is pressed
during an active or held call.

Administration via local phone

Transferring phone software, application, and media

files
New software images, hold music, picture clips for phone book entries, LDAP templates, com-
pany logos, screen Saver images, and ring tones can be uploaded to the phone via DLS (Deploy-
ment Service) or WBM (Web Based Management).

Note For all user data, which includes files as well as phone book content, the following
amounts of storage place are available:

l OpenScape Desk Phone CP710:100MB
l OpenScape Desk Phone CP410: 100 MB
l OpenScape Desk Phone CP210: 25 MB
l OpenScape Desk Phone CP110: 25MB

Linux file name issues

In Linux based file systems, the null character and the path separator "/" are prohibited. Other
characters may have an adverse effect during the creation or deletion of the particular file in the
Linux operating system.

Prevent invalid file names

Saving a file with an invalid file name on the phone could lead to operational or security issues.
To protect against this the phone will ensure that the file name for the file to be saved does not
contain non-allowed characters. The solution is to replace invalid characters in the names of
files to be downloaded onto the phone with a dummy character.
102 Administration

The set of allowed characters are:

l 0 to 9
l a to z
l A to Z
l "-" (hyphen)
l "_" (underscore)

A space character is explicitly not allowed in a Linux file name. Any non-allowed characters are
replaced with an "_" (underscore) character. The file name must not start with a "-" (hyphen) char-
acter.

This should cover any download mechanism:

l WBM download of user files (such as ringers)

l WBM download of binds
l FTP or HTTPS download of files to the phone

When a file is downloaded to the phone, sanity checks are carried out to ensure there are no
operational or security impacts on the phone.

WBM checks the file name and file extension entered in any FTP / HTTPS file transfer panel only
contains valid characters and that the file extensions (file type) are valid.

l If a file path character or file extension is detected in the file name then an error is dis-
played and the file transfer is not allowed.

FTP / HTTPS server

There are no specific requirements regarding the FTP server for transferring files to the
OpenScape Desk Phone. Any FTP server providing standard functionality will do.

Common FTP / HTTPS settings (defaults)

For each one of the various file types, e.g. phone application, or logos, specific FTP / HTTPS
access data can be defined. If some or all file types have the parameters “Download method”,
“FTP Server”, “FTP Server port”, “FTP Account”, “FTP Username”, “FTP path”, and “HTTPS base
URL” in common, they can be specified here. These settings is used for a specific file type if its
Use defaults parameter is set to "Yes".

Note If “Use defaults” is activated for a specific file type, any specific settings for this
file type are overridden by the defaults.

Additional log messages are issued for the following phone application download conditions:

l Update has been allowed due to override flag being set

l Whole part number is not recognized
Administration 103

l Block 4 of part number is not recognized

l Downloaded software does not have a hardware level included

Administration via WBM

1. Open File transfer > Defaults.

l Download method: Selects the protocol to be used. Value range: "FTP", "HTTPS"
Default: "FTP"
l FTP Server: IP address or hostname of the FTP server in use.
l FTP Server port: Port number of the FTP server in use. For HTTPS, port 443 is assumed,
unless a different port is specified in the HTTPS base URL
Default: 21
l FTP Account: Account at the server (if applicable).
l FTP Username: User name for accessing the server.
l FTP Password: Password corresponding to the user name.
l FTP path: Path of the directory containing the files.
l HTTPS base URL: IP address or hostname of the HTTPS server in use. If no port number
is specified here, port 443 is used. Only applicable if Download method is switched to
"HTTPS"

Administration via local phone

Phone application
The firmware for the phone can be updated by downloading a new software file to the phone.

If an incorrect software image is being attempted to be loaded onto the phone, the phone will
reject the request and return to normal operation without reboot. As part of this security mech-
anism, new software binds are identified by a "Supported Hardware Level" information built into
the header.

Prerequisite

The phone knows its own hardware level (from the part number and / or by a dynamical check of
its hardware level).

When a new software bind is downloaded to the phone, the following verification is performed:

l If new software bind has hardware level header included (in the bind header): Hardware
level of new bind is compared with phone’s hardware level.
n If compatible (or if Override is set): Proceed with update
n If NOT compatible: Abandon update and return to original application
l If new software bind does NOT have hardware level header included (in the bind header):
Software version of new bind is compared with minimum known supported SW level.
n If compatible (or if Override is set): Proceed with update
n If NOT compatible: Abandon update and return to original application

Note Do not disconnect the phone from the LAN or power unit during software update.
An active update process is indicated by blinking LEDs and / or in the display.

Upgrade using file

You can upgrade the phone application by navigating to a local file. This can be done only by
WBM administration.
Administration 105

Administration via WBM

1. Open File transfer > Phone application.

2. Click Browse…, and select the file you want to install.

3. Click Upgrade.
4. Wait until the upgrade process is finished.

Note The "Cancel" function will not work once the process is in burn state.

Upgrade using FTP / HTTPS

If the default FTP / HTTPS access settings (see "Common FTP / HTTPS settings (defaults)" à
page 102) are used, “Use defaults” must be set to "Yes", and only the file name must be spe-
cified.
106 Administration

Administration via WBM

1. Open File transfer > Phone application.

l Use defaults: Specifies whether the default FTP / HTTPS access settings shall be used.
Value range: "Yes", "No". If enabled, an abbreviated set of options is provided.
l File name: Specifies the file name of the phone software.
l After submit: Specifies actions after submit button is pressed. Value range: "do nothing",
"start download". Default: "do nothing".
The option "do nothing" allows changes to the set of options and submit the changes to
update the page (e.g. select between FTP and HTTPS).

Data required (if not derived from Defaults)

l Download method: Selects the protocol to be used. Value range: "FTP", "HTTPS". Default:
"FTP".
l Server: IP address or host name of the FTP / HTTPS server in use.
l Server port: Port number of the FTP / HTTPS server in use. Default: 21.
l Account: Account at the server (if applicable).
l Username: User name for accessing the server.
l Password: Password corresponding to the user name.
l FTP path: Path of the directory containing the files.
l HTTPS base URL: IP address or host name of the HTTPS server in use; only applicable if
Download method is switched to "HTTPS".
Administration 107

Administration via local phone

Download / update phone application

If applicable, phone software should be deployed using the Deployment Service (DLS). Altern-
atively, the download can be triggered from the WBM interface or from the Local phone menu.
When the download has been successful, the phone will restart using the new software.

Updating via FTP or HTTPS

1. Open File transfer > Phone application.

2. Select the transfer protocol.

3. Provide the address and the port number.
4. If required, provide the user name and password.
5. Enter the file name
108 Administration

6. Set “After submit” to "Start download".

7. Click Submit.

Start Download via Local Phone

|--- Admin
|--- File Transfer
|--- Phone app

1. Click OK.
2. Select Download. The download will start immediately.

Picture clips
Note The file size for a picture clip is limited to 300 KB.

Picture clips are small images used for displaying a picture of a person that is calling on a line.
The supported file formats for picture clips are JPEG, BMP and PNG. The file extensions sup-
ported for JPEG are “*.jpeg” and “*.jpg”.

FTP / HTTPS access data

If the default FTP /HTTPS access settings are used, “Use defaults” must be set to "Yes", and only
the file name must be specified (see "Common FTP / HTTPS settings (defaults)" à page 102).

Administration via WBM

1. Open File transfer > Picture clip.

l Use defaults: Specifies whether the default FTP / HTTPS access settings shall be used.
l File name: Specifies the file name of the image file
l Download method: Selects the protocol to be used. Value range: "FTP", "HTTPS".
n Default: "FTP"
l Server: IP address or host name of the FTP / HTTPS server in use
l Server port: Port number of the FTP / HTTPS server in use.
n Default: 21
l Account: Account at the server (if applicable)
l Username: User name for accessing the server
Administration 109

l Password: Password corresponding to the user name

l FTP path: Path of the directory containing the files
l HTTPS base URL: IP address or host name of the HTTPS server in use; only applicable if
Download method is switched to "HTTPS"
n After submit: Specifies actions after submit button is pressed.
Value range: "do nothing", "start download".
n Default: "do nothing"

Administration via local phone

1. On OpenScape Desk Phone CP410 and CP710 select Download. The download will start

immediately.

Download a picture clip

Note This feature is available for OpenScape Desk Phones CP410 and CP710.

If applicable, picture clips should be deployed using the Deployment Service (DLS). Alternatively,
the download can be triggered from the web interface or from the local phone menu (see "FTP /
HTTPS access data" à page 108).

Upload picture clips via LDAP

The LDAP template identifies if avatars are available for LDAP entries and how they are
accessed by the phone.

The LDAP directory must contain avatar pictures in JPEG / JIFF format (plain or base 64
encoded) or a URL that points to a web-server that can provide a picture for the contact.

Example: Plain JPEG picture attributes are "jpegPhoto" or "thumbnailPhoto". URL attribute can be
"photoURL".

For best display the square format is recommended.

Maximum picture size is 100 kB. The phone shows an avatar in two sizes:
110 Administration

l 32x32 px for conversation list and contact details (header)

l 64x64 px for conversation and call screens

If another size provided, the phone will automatically resize the picture to needed dimensions.

Until a JPEG image is available a default avatar is used for the LDAP contact.

The LDAP must be configured and a suitable LDAP template must be available on the phone.
The LDAP template must support a 13th attribute to allow access to a contact's picture (see
"Create an LDAP template" à page 164).

If the configured address of the web server (Avatar server) is not empty, the attribute content is
treated as the variable part of the URL to access the picture from a WEB server — see Con-
figuration via DLS and WBM in this chapter. The phone then constructs a full path to the picture
file on the web server, i.e. adds the attribute value to the Avatar server field value. The photoURL
atribute may be a direct URL which ends up with "filename.jpg". The address can include a HTTP
address or a HTTPS address. HTTPS is assumed by default.

If configured address of the web server (Avatar server) is empty, the attribute value is treated as
a LDAP DN and the LDAP server is asked for the content of the attribute. The content must be
plain JPEG or base64 encoded.

Example

Avatar server value is „https://my.image.server.com/internal“ . The photoURL atribute is „employ-

ee1.jpg“. Phone will sent http request for https://my.image.server.com/internal/employee1.jpg.

If the picture cannot be displayed (wrong format, download error, etc.) then a default avatar con-
tinues to be shown.

Configuration via Admin menu

1. Open Settings > Administrator > Local functions > LDAP > Avatar server.

Configuration via DLS

1. Open DeploymentService > IP Devices > IP Phone Configuration > Service Integrations >
LDAP Settings > Avatar Server.
Administration 111

Administration via WBM

1. Open Admin > Local functions > Directory settings.

2. Enter the Avatar server address.

3. Click Submit.

LDAP template
The LDAP template is an ASCII text file that allows attributes in an LDAP directory entry to be
mapped to the contact fields on the phone. The LDAP template must be modified correctly for
successful communication between the directory server and the LDAP client.

The OpenScape Desk Phone phones support LDAPv3.

FTP / HTTPS access data

If the default FTP / HTTPS access settings are used, “Use default” must be set to "Yes", and only
the file name must be specified (see "Common FTP / HTTPS settings (defaults)" à page 102).
112 Administration

Administration via WBM

1. Open File transfer > LDAP.

l Use default: Specifies whether the default FTP / HTTPS access settings shall be used.
Value range: "Yes", "No" Default: "No"
l File name: Specifies the file name of the LDAP template file.
l After submit: Specifies actions after submit button is pressed. Value range: "do nothing",
"start download". Default: "do nothing".

Data required (if not derived from Defaults)

l Download method: Selects the protocol to be used. Value range: "FTP", "HTTPS" Default:
"FTP"
l Server address: IP address or host name of the FTP / HTTPS server in use.
l Server port: Port number of the FTP / HTTPS server in use. Default: 21
l Account: Account at the server (if applicable).
l Username: User name for accessing the server.
l Password: Password corresponding to the user name.
l FTP path: Path of the directory containing the files.
l HTTPS base URL: IP address or host name of the HTTPS server in use; only applicable if
Download method is switched to "HTTPS".
Administration 113

Administration via local phone

Download LDAP template

If applicable, LDAP templates should be deployed using the DLS (Deployment Service). Altern-
atively, the download can be triggered from the web interface or from the local phone menu.

The OpenScape Desk Phones support LDAPv3.

Start Download via WBM

1. Open File transfer > LDAP.

2. Select the transfer protocol.

3. Provide the address and the port number.
4. If required, provide the user name and password.
5. Enter the file name.
6. Set “After submit” to "start download".
7. Click Submit.
114 Administration

Start Download via local phone

|--- Admin
|--- File Transfer
|--- LDAP

1. Click OK.
2. Select Download. The download will start immediately.

Screen Saver
The screen Saver can be configured to be displayed when the phone is in idle mode. It performs
a slide show consisting of images which can be uploaded using the web interface.

Screen Savers are available only on OpenScape Desk Phones CP410 and CP710.

Note The file size for a screen Saver image is limited to 300 KB. If the file is too large or
the contents of the file are not valid, the file will not be stored in the phone.

For screen Saver images, the following specifications are valid:

l Data format: JPEG, BMP or PNG. JPG is recommended. The file extensions supported for
JPEG are jpeg and jpg.
l Screen format: 4:3. The images are resized to fit in the screen, so that images with a
width / height ratio differing from 4:3 will appear with deviant proportions.
l Resolution: The phone’s screen resolution is the best choice for image
resolution: 320x240 px

FTP / HTTPS access data

If the default FTP / HTTPS access setting are used, Use default must be set to "Yes", and only
the file name must be specifieds (see "Common FTP / HTTPS settings (defaults)" à page 102).
Administration 115

Administration via WBM

1. Open File transfer > ScreenSaver.

l Use defaults: Specifies whether the default FTP / HTTPS access settings shall be used.
n Default: disabled
l Filename: Specifies the file name of the screensaver image file.
l After submit: Specifies actions after submit button is pressed.
n Value range: "do nothing", "start download"
n Default: "do nothing".

Data required (if not derived from Defaults)

l Download method: Selects the protocol to be used.

n Value range: "FTP", "HTTPS"
n Default: "FTP"
l Server address: IP address or host name of the FTP / HTTPS server in use.
l Server port: Port number of the FTP / HTTPS server in use.
n Default: 21
l Account: Account at the server (if applicable).
l Username: User name for accessing the server.
l Password: Password corresponding to the user name.
l FTP path: Path of the directory containing the files.
l HTTPS base URL: IP address or hostname of the HTTPS server in use; only applicable if
Download method is switched to "HTTPS".
116 Administration

Administration via local phone

Download screen saver

If applicable, screen savers should be deployed using the DLS (Deployment Service). Altern-
atively, the download can be triggered from the web interface or from the local phone menu.

Start Download via WBM

1. Open File transfer > Screensaver.

2. Set “After submit” to "start download".

3. Click Submit.

Start Download via local phone

|--- Admin
|--- File Transfer
|--- Screensaver
Administration 117

1. In the administration menu, select “Screensaver”.

2. Select Download. The download will start immediately.

Ringer file
Note The download of ringer files via WBM or local menu is possible for all CP phone
models.

Custom ring tones can be uploaded to the phone.

Note The file size for a ringer file is limited to 1 MB. If the file is too large or the con-
tents of the file are not valid, the file will not be stored in the phone. This limitation
is only enforced on WBM.

The following file formats are supported:

l WAV format. The recommended specifications are:

n Audio format: PCM
n Bit rate: 16 kB/s
n Sampling rate: 8 kHz
n Quantization level: 16 bit
l MIDI format
l MP3 format. The OpenScape Desk Phones CP410 and CP710 are able to play MP3 files
from 32 kbit/s up to 320 kbit/s. As the memory for user data is limited to 8 MB, a con-
stant bit rate of 48 kbit/s to 112 kbit/s and a length of max. 1 minute is recommended.
Although the phone software can play stereo files, mono files are recommended, as the
phone has only 1 loudspeaker. See the following table for estimated file size (mono files).

Length 64 kbit/s 80 kbit/s 96 kbit/s 112 kbit/s

0:15 min 0.12 MB 0.15 MB 0.18 MB 0.21 MB

0:30 min 0.23 MB 0.29 MB 0.35 MB 0.41 MB

0:45 min 0.35 MB 0.44 MB 0.53 MB 0.62 MB

1:00 min 0.47 MB 0.59 MB 0.70 MB 0.82 MB

FTP / HTTPS access data

Administration via WBM

1. Open File transfer > Ringer file.

l Use default: Specifies whether the default FTP / HTTPS access settings shall be used.
n Value range: "Yes", "No"
n Default: "No"
l File name: Specifies the file name of the ringer file.
l After submit: Specifies action after submit button is pressed.
n Value range: "do nothing", "start download"
n Default: "do nothing"

Data required (if not derived from Defaults)

l Download method: Selects the protocol to be used.

n Value range: "FTP", "HTTPS"
n Default: "FTP"
l Server address: IP address or host name of the FTP / HTTPS server in use.
l Server port: Port number of the FTP / HTTPS server in use.
n Default: 21
l Account: Account at the server (if applicable).
l Username: User name for accessing the server.
l Password: Password corresponding to the user name.
l FTP path: Path of the directory containing the files.
l HTTPS base URL: IP address or hostname of the HTTPS server in use; only applicable if
download method is switched to "HTTPS".
Administration 119

Administration via local phone

Download ringer file

If applicable, ring tone files should be deployed using the DLS (Deployment Service). Altern-
atively, the download can be triggered from the web interface or from the Local phone menu.

Start Download via WBM

1. Open File transfer > Ringer file.

2. Set “After submit” to "start download".

3. Click Submit.

Start Download via local phone

1. In the administration menu, select “Ringer”.

120 Administration

|--- Admin
|--- File Transfer
|--- Ringer

1. Press the key labeled Download. The download will start immediately.

Company logo
Note This feature is available only on OpenScape Desk Phone CP410 and CP710
phones.

Custom company logo can be uploaded to the phone.

Note There can only be a single logo image on the phone. When a new logo image is
uploaded, the old one is deleted if there is one existing.

By default, there is no logo image file on the phone. The administrator can upload a custom logo
image with appropriate file extension (JPEG, JPG, PNG or BMP), which would be displayed on
Menu and Phone Lock screens. The time and date information are shown in small format below
the status bar when the logo is being displayed.

Format of the logo image file

The logo image file is accepted by the phone in below formats:

l CP710 and CP410: PNG image 24-bit with alpha channel

The image file size must not exceed 10 MBytes.

Resizing logo image file

After successful transfer of the new logo file, the phone will check the image resolution size in
pixels and decide if it needs to be resized so that the image fits in the logo image placeholder.

The maximum size of logo image placeholder is as below:

l CP710: 440 x 220 px

l CP410: 216 x 68 px

Resizing is done by keeping the aspect ratio intact.

Administration 121

Administration via WBM

1. Open File transfer > Logo.

2. Select a file that conforms to the specifications.

3. Click Submit.

If a logo is uploaded, the option "delete logo file" is displayed beneath the option "After submit".

Administration via Local Phone

UC server
Administration via WBM

1. Open Local functions > Locality > UC Server.

2. Specify the following settings:
l UC Protocol: selects the protocol to be used.
n Value range: "HTTP", "HTTPS".
l UC Server address: IP address or host name of the UC server in use.
l UC Server port: port number of the UC server in use.
n Default: 8802.
l User configuration enabled: indicates whether the user configuration is enabled.
3. Click Submit.

Administration via local phone

|--- Admin

|--- Local functions

|--- UC Server

|--- UC Protocol

|--- UC server address

|--- UC Server port

|--- User configuration enabled

Send request via HTTP / HTTPS

With this function, the phone can send a specific HTTP or HTTPS request to a server. The func-
tion is available at any time, irrespective of registration and call state. Possible uses are HTTP-
controlled features on the system, or functions on a web server that can only be triggered by
HTTP / HTTPS request, e.g. login or logout for flexible working hours.

l The protocol parameter defines whether HTTP or HTTPS is used for sending the URL to
the server.
l The web server address is the IP address or DNS name of the remote server to which the
URL is sent.
l The port is the target port at the server to which the URL is sent.
l The path is the server-side path to the desired function, i.e. the part of the URL that fol-
lows the IP address or DNS name (example: web page/checkin.html).
Administration 123

l In the parameters field, one or more key/value pairs in the format "key=value" can be
added to the request, separated by an ampersand (&).

Example

phonenumber=3338&action=huntGroupLogon

The question mark is automatically added between the path and the parameters. If a question
mark has been entered at the start of the parameters, it is stripped off automatically.

The method parameter determines the HTTP method used, which can be either GET or POST. If
GET is selected, the additional parameters and the user id and password (web server user ID and
web server password) are part of the URL. If POST is selected, these data form the body of the
message.

If the web server requires user authentication, the parameters ”Web server user ID” and “Web
server password” can be used. If not null, the values are appended between the serverside path
(Path) and the additional parameters (Parameter).

Administration via WBM

1. Open System > Features > Send URL.

l Name defines or changes the name (label) of the key.

l Protocol: transfer protocol to be used.
n Value range: "HTTP", "HTTPS"
l Web server address: IP address or DNS name of the remote server.
l Port: target port at the server.
124 Administration

l Path: server-side path to the function.

l Parameters: optional parameters to be sent to the server.
l Method: HTTP method used for transfer.
n Value range: "GET", "POST"
l Web server user ID: user id for user authentication at the server.
l Web server password: password for user authentication.
Administration 125

Settings of the corporate directory

LDAP
The Lightweight Directory Access Protocol (LDAP) enables access to a directory server via an
LDAP client. Various personal information is stored there, e.g. the name, organization, and con-
tact data of persons working in an organization. When the LDAP client has found a person’s
data, e. g. by looking up the surname, the user can call this person directly using the displayed
number.

On an OpenScape Desk Phone CP410 or CP710, the use of the LDAP directory is integrated into
the conversations concept.

Example

If a call cannot be mapped to a contact on the phone, the phone can be configured to look up the
call contact details from the LDAP directory. In addition, a search for a contact will cover both
contacts on the phone and the LDAP directory. The LDAP template maps the LDAP fields to
those of the contacts on the phone.

On an OpenScape Desk Phone CP110 or CP210, the LDAP directory can be accessed using the
entry Directories > Corporate directory.

The entry is displayed only when a LDAP server is configured.

Note The OpenScape Desk Phone CP phones support LDAPv3.

For connecting the phone LDAP client to an LDAP server, the required access data must be con-
figured. The parameter “Server” address specifies the IP address of the LDAP server. The para-
meter “Transport” defines whether the phone must continue to use an unencrypted TCP
connection to the LDAP server, or to use an encrypted TLS connection to a separate LDAPS port
on the LDAP server, or to use an encrypted TLS connection to a separate LDAPS port on the
LDAP server. Depending on the setting of “Transport” the secure port (for TLS) or the server port
(for TCP) are defined. If the authentication is not set to "Anonymous", the user must authenticate
himself with the server by providing a user name and a corresponding password. The user name
and password are defined by the administrator. The user name is the string in the LDAP bind
request, e. g. "C=GB,O=SIEMENS COMM,OU=COM,L=NTH,CN=BAYLIS MICHAEL". The internal
structure will depend on the specific corporate directory.

For a guide on setting up LDAP on an OpenScape Desk Phone, refer to "How to set up the “Cor-
porate directory” (LDAP)" à page 164.
126 Administration

On an OpenScape Desk Phone CP110 or CP210, an explicit search field for LDAP requests is sup-
ported. The search string is submitted to the LDAP server as soon as OK is pressed or when the
search trigger timeout expires.

On an OpenScape Desk Phone CP410 or CP710, the search of the LDAP directory is integrated in
the conversations search function. The LDAP template allows for a 'nickname' field which allows
a search of any text in the field.

Administration via WBM

1. Open Local functions > Directory Settings.

l LDAP Server address: IP address or host name of the LDAP server

l Transport: defines transport mode, whether LDAP interface uses TCP and is unencrypted,
or uses TLS and is encrypted
n Value range: "TCP", "TLS"
n Default: "TCP"
l Secure Port: defines the port of the appropriate TLS interface on LDAP server when Trans-
port is set to TLS
n Default: "636"
l LDAP Server port: port on which the LDAP server is listening for requests, when Transport
is set to TCP
n Default: 389
l Authentication: authentication method used for connecting to the LDAP server
n Value range: "Anonymous", "Simple"
n Default: "Anonymous"
l User name: user name used for authentication with the LDAP server in the LDAP bind
request
l Password: password used for authentication with the LDAP server
l Contact details update: The update source for call party names can be set as one or more
of the following: Directory, Signaling or Local.
l Avatar server: HTTP or HTTPS address, where the pictures are located. The complete
HTTP or HTTPS address is built from "Avatar server" + "Avatar". "Avatar" is the attribute
name from the LDAP template field "Avatar". The specified LDAP attribute must contain
Administration 127

the file name of the picture contained in the URL specified in "Avatar Server".
Example: "Avatar Server" = "https://mypicture.server/picturepath" ("Avatar" = pic-
turename).
When the phone does an LDAP lookup for user A, the field “Picturename” returns pic-
turename = UserA.jpg. The phone will look for the picture at: https://myp-
icture.server/picturepath/UserA.jpg.

Administration via local phone

Contact details update

Note This option is only available for the OpenScape Desk Phone CP410 and CP710
phones. Not applicable for Broadsoft.

It is possible to update the source used to obtain call party names from one place.

l Existing contact names are updated for new calls (if one or more sources are specified
and matched)
l Existing contact names are not updated (if the local source is used, i.e. no sources set)

Source of the contact details

When an update source has been specified, the phone will try to match the call party number
signaled for a call to an entry in the update source(s). If more than one source is specified then
they is used in the following order:

l LDAP
l Signalling
128 Administration

Administration via WBM

1. Open Local functions > Name update sources.

The update source can be set as one or more of the following:

l Directory: LDAP (if an LDAP entry matches the call, the contact is update to match the
LDAP entry)
l Signalling: Via SIP (if set then the contact is updated based on the call party name in sig-
naling)

Administration via local phone

Picture via LDAP

Note This option is only available for the OpenScape Desk Phone CP410 and CP710
phones.

To display centrally stored contact data the OpenScape Desk Phone CP410 / CP710 will request
and retrieve the data from a server.

The OpenScape Desk Phone CP410 / CP710 requests the look-up for all numbers for which the
local phone book does not have a picture. In case the phone book contains names for the num-
ber but without picture the name and picture from the directory server are displayed. If there is
no entry for the number in the directory server the name from the local phone book is displayed,
so the directory server data overrides the local phone book.

Currently two different mechanisms for storage of the picture shall be supported, both requiring
a directory server for central storage:
Administration 129

l Direct retrieval of pictures stored within the LDAP directory (preferred mechanism)
l Indirect (two step) retrieval in case the directory server contains a reference (URL) to the
picture instead. In this case the picture is retrieved from another server via HTTP using
the URL.

Note The phones will only accept pictures encoded in jpg and max. 50 kB size.

Canonical dial settings

For contact data retrieval from the directory server, upon arrival of a call, the remote telephone
number is converted according to the canonical dial settings (see also "Canonical dialing set-
tings" à page 161). The format of the resulting number should match the format the numbers
are stored in the directory server. It is recommended to convert the numbers to fully qualified
format, i.e. adding country and area code to the subscriber number. This way it is ensured that
the number used for look-up is unique.

Below is an example of settings for a company in Munich.

Administration via WBM

1. Open Local functions > Locality > Canonical dial settings.

Administration via local phone

|--- Administration

|--- Local Functions

|--- Locality
130 Administration

|--- Canonical dial settings

|--- Local country code

|--- National prefix digit

|--- Local national code

|--- Minimum local number length

|--- Local enterprise node

|--- PSTN access code

|--- International code

|--- Operator code

|--- Emergency number

|--- Inital extension digits

Speech

RTP base port

The port used for RTP is negotiated during the establishment of a SIP connection.

The number of the port used for RTCP is the RTP port number increased by 1.

Administration via WBM

1. Open Network > Port number configuration.

2. Define the RTP base starting point from which the phone will count up when negotiating.
l Default value is 5010.
3. Click Submit.
Administration 131

Administration via local phone

|--- Admin
       |--- Network
             |--- Port configuration
                   |--- RTP base

Codec preferences
If “Silence suppression” is activated, the transmission of data packets is suppressed on no con-
versation, that is, if the user is silent.

The OpenScape Desk Phone CP phone provides the codecs

l G.722
l G.711
l G.729

When a connection is established between two endpoints, the phones negotiate the codec to be
used. The result of the negotiation is based on the general availability and ranking assigned to
each codec. The administrator can allow or disallow a codec as well as assign a ranking number
to it.

The Packet size, i. e. length in milliseconds, of the RTP packets for speech data, can be set to
10 ms, 20 ms, 30 ms, 40 ms, 60 ms or to automatic detection.

Administration via WBM

1. Open Speech > Codec preferences.

l Silence suppression: Suppression of data transmission on no conversation.

n Value range: "On", "Off"
n Default: "Off"
l Allow "HD" icon: If "On" an additional icon is shown when codec G.722 is used.
n Value range: "On", "Off"
n Default: "On"
132 Administration

l Packet size: Size of RTP packets in milliseconds.

n Value range: "10 ms", "20ms", "30ms", "40ms", "60ms", "Automatic"
n Default: "Automatic"
l G.722: Parameters for the G. 722 codec.
n Value Range: "Choice 1", "Choice 2", "Choice 3", "Choice 4", "Disabled", "Enabled"
n Default: "Disabled"
l G.711: Parameters for the G. 711 codec.
n Value Range: "Choice 1", "Choice 2", "Choice 3", "Choice 4", "Disabled", "Enabled"
n Default: "Choice 2"
l G.729: Parameters for the G. 729 codec.
n Value Range: "Choice 1", "Choice 2", "Choice 3", "Choice 4", "Disabled", "Enabled"
n Default: "Choice 3"

Administration via local phone

Security and policies

Changing a password
The passwords for user and administrator can be changed.

Note The administrator password should be changed after the first login.

The default password for the user is not set. The default password for the administrator is
"123456".

By default, password entry is in numeric mode and a minimum length of 6 characters.

Usable characters are 0-9 A-Z a-z ."*#,?!’+-()@/:_

Administration 133

Default passwords

l Admin menu: 123456

l User menu: no password
l Factory Reset: 124816
l Soft Restart: Press keys 1-4-7 simultaneously and enter Admin password.
l Factory Reset: Press keys 2-8-9 simultaneously and enter Reset password.

Changing the administrator password

1. Open Security and Policies > Password > Change admin password.

2. Enter the current admin password and the new password.

3. Confirm the new admin password and click Submit.

Changing the user password

1. Open Security and Policies > Password > Change user password.

2. Enter the admin password and the new user password.

3. Confirm the new user password and click Submit.

Administration via local phone

Retrieve a lost password

Lost user password

If a user password is lost, the administrator may reset the user password.

Lost administrator password

If the administration or user password is lost, and if no DLS is available, new passwords must be
provided.

In case of lost administration password, a factory reset is necessary.

1. On the phone, press the number keys 2-8-9 simultaneously. The factory reset menu
opens. If not, the key combination is deactivated due to security reason.
2. In the input field, enter the special password for factory reset "124816".
3. Confirm by pressing OK.

Certificates

Generic

Online Certificate Check

The Online Certificate Status Protocol (OCSP) is used to check if a certificate to be used has
been revoked. This protocol is used to query an Online Certificate Status Responder (OCSR) at
the point when the certificate is being validated. The address of an OCSR can be configured on
the phone and can also be obtained from the certificate to be checked (which will have the pri-
ority).

l When OCSP check is activated, the configured OCSR is requested to check if the cer-
tificate has been revoked.
l OCSR 1 address specifies the IP address (or FQDN) of a primary OCSP responder.
l OCSR 2 address specifies the IP address (or FQDN) of a secondary OCSP responder.
Administration 135

Administration via WBM

1. Open Security and Policies > Certificates > Generic.

2. Click Submit.

Administration via local phone

|--- Admin

|--- Security and policies

|--- Certificates

|--- Generic

|--- Secure file transfer

|--- Secure HFA gateway

|--- Secure 802.1x server

Authentication policy
For individual certificates provided by specific servers, the level of authentication can be con-
figured. When "None" is selected, no certificate check is performed. With "Trusted", the cer-
tificate is only checked against the signature credentials provided by the remote entity for
signature, and the expiry date is checked. When "Full" is selected, the certificate is fully checked
against the credentials provided by the remote entity for signature, the fields must match the
requested subject or usage, and the expiry date is checked.
136 Administration

Administration via WBM

1. Open Security and Policies > Certificates > Authentication policy.

l Secure file transfer sets the authentication level for the HTTPS server to be used (see
"Common FTP / HTTPS settings (defaults)" à page 102).
l Secure HFA gateway sets the authentication level for the HFA gateway connected to the
phone (see "HFA gateway settings" à page 78).
l Secure 802.1x server sets the authentication level for the 802.1x authentication server.

Administration via local phone

|--- Admin

|--- Security and policies

|--- Certificates

|--- Authentication policy

|--- Secure file transfer

|--- Secure HFA gateway

|--- Secure 802.1x server

Restart phone
If necessary, the phone can be restarted from the administration menu or via pressing number
keys 1-4-7 simultaneously.
Administration 137

Administration via WBM

1. Open Maintenance > Restart Phone.

2. Select “Confirm restart”.

Administration via Local Phone

|--- Admin
|--- Maintenance
|--- Restart

Factory reset
This function resets all parameters to their factory settings. A special reset password is required
for this operation: "124816".

Administration via WBM

1. Open Maintenance > Factory reset.

2. Enter the factory reset password.

3. If the certificates should be kept on the phone, enable “Keep certificates”.
4. Click “Reset”.

Administration via local phone

|--- Admin
|--- Maintenance
|--- Factory reset

SSH — secure shell access

The phone operating system can be accessed via SSH for special troubleshooting tasks. Hereby,
the administrator is enabled to use the built-in Linux commands. As soon as SSH access has
been enabled using the WBM, the system can be accessed by the user "admin" for a specified
time span. When this time span has expired, no connection is possible any more. The user
"admin" has the following permissions:
138 Administration

l Log folder and files: read only

l User data folder and files: read / write access
l Opera deploy folders and files: read only
l Version folder: read / write access; version files: read only

Note It is not possible to log-on as “root” via SSH.

By default, SSH access is disabled.

Administration via WBM

1. Open Maintenance > Secure shell.

l When “Enable access” is active, and the parameters are specified, SSH access is activ-
ated.
l With the “Session password” parameter, a required password for the "admin" user is cre-
ated. It is valid for the time span specified in the parameters.
l Access minutes defines the time span in minutes within which the SSH connection must
be established. After it has expired, a log-on via SSH is not possible.
n Value range: 1…10.
l Session minutes defines the maximum length in minutes for an SSH connection. After it
has expired, the "admin" user is logged out.
n Values: 5, 10, 20, 30, 60.

Display license information

The license information for the OpenScape Desk Phone CP phone software currently loaded can
be viewed via the local menu.
Administration 139

The license information can also be viewed by users with the user login if logging on as admin-
istrator is not permitted.

Administration via local phone

|--- Admin

|--- Licence information

HPT interface (for service staff)

For special diagnosis and maintenance tasks, the service staff may employ the HPT tool, which
is able to control and observe OpenScape Desk Phone CP110 / CP210 / CP410 phones
remotely.

There are 2 types of HPT sessions, control session and observation session.

l A control session allows for activating phone functions remotely. When a control session
is established, the following changes will occur:
n The display shows a message indicating that remote service is active.
n Handset, microphone, speaker, headset, and microphone are disabled.
l An observation session allows for supervising events on the phone, like, for instance,
pressing a key, incoming calls or navigating in the menus. Before an observation session
is started, the user is prompted for allowing the observation. During an observation ses-
sion, the phone operates normally, including loudspeaker, microphone and ringer. Thus,
the local user can demonstrate an error towards the service staff that is connected via
HPT.

The session data is written to a log file on the phone. It can be downloaded from the Diagnostics
> Fault trace configuration menu (see "Fault trace configuration" à page 142).

Administration via WBM

1. Open Maintenance > HPT interface.

2. Click Disable HPT to deactivate.

Administration via local phone

|--- Administration
|--- Maintenance
|--- Disable HPT / Enable HTP
140 Administration

AlertBar LED hint

Note This option is only available for the OpenScape Desk Phone CP410 and CP710
phones.

The administrator can control how the AlertBar LED is automatically turned off when it has been
used to indicate a missed call.

Administration via WBM

1. Open System > Features > Configuration.

2. Enable “AlertBar LED hint” to turn off the LED as soon as the user enters “Conversations”
or “Call log”. The conversations screen and the main menu screen will continue to indic-
ate the existence of a new missed call. This function is disabled by default.
3. Click Submit.

Diagnostics
Note Some of the diagnostic tools and functions may reveal personal data of the user,
such as caller lists. Thus, with regards to data privacy, it is recommended to
inform the user when diagnostic functions are executed.

LLDP-MED
When the phone is connected to a switch with LLDP-MED capabilities, it can receive a VLAN ID
and QoS parameters and advertise its own network-related properties. The data is exchanged in
TLV (Type-Length-Value) format.

Both sent and received LLDP-MED data can be monitored at the administrator interface.

Note For details on LLDP-MED, refer to the ANSI/TIA-1057 standard.

For a network configuration example that shows LLDP-MED in operation, refer to
"LLDP-Med example" à page 170.
Administration 141

View Data From WBM

1. Open Diagnostics > LLDP-MED TLVs.

l Extended Power: Power Consumption; relevant for PoE.

l Network policy (voice): VLAN ID and QoS (Quality of Service) parameters for voice trans-
port.
l Network policy (signalling): VLAN ID and QoS (Quality of Service) parameters for sig-
nalling.
l LLDP-MED capabilities: The LLDP-MED TLVs supported by the phone and the switch as
well as the specific device class they belong to.
l MAC_Phy configuration: Identifies the possible duplex and bit-rate capability of the send-
ing device, its current duplex and bit-rate capability, and whether theses settings are the
result of auto-negotiation during the initialization of the link, or of manual set override
actions.
l System capabilities: The devices advertise their potential and currently enabled functions,
e. g. "Bridge", "Telephone".
l TTL: Time To Live. This parameter determines how long the TLVs are valid. When expired,
the device will send a new set of TLVs.
l Inventory: Inventory information of a CP phone such as "Manufacturer Name", "Model
Name", "Hardware Revision", "Firmware Revision", "Software Revision", "Serial Number",
"Asset ID"

View Data From Local Menu

If both sent and received values are concordant, OK is appended to the parameter. If not, an
error message is displayed.
142 Administration

Fault trace configuration

Error tracing and logging can be configured separately for all components, i. e. the services and
applications running on the OpenScape Desk Phone CP. The resulting files can be viewed in the
WBM web pages over the download links.

Note The absolute maximum file size is 6,290,000 bytes. However, on OpenScape Desk
Phone CP phones, a maximum size not greater than 1,000,000 bytes is recom-
mended due to the amount of available memory.

Administration via WBM

1. Open Diagnostics > Fault trace configuration.

l The “File size (bytes)” parameter sets the maximum file size. When it is reached, the data
is saved as old file, and a new file is generated. From then on, the trace data is written to
Administration 143

the new file. When the maximum file size is reached again, the data is saved as old file
once more, thereby overwriting the previous old file. The default value is “1048576”.
l The “Trace timeout (minutes)” determines when to stop tracing. When the timeout is
reached, the trace settings for all components are set to OFF, but ERROR and STATUS
messages are still written to the trace file infinitely. When the trace file has reached its
maximum size, the data is saved, and a new file is created (for more information, see File
size (bytes) above). If the value is 0, the trace data is written without time limit.
l If “Automatic clear before start” is enabled, the existing trace file is deleted on clicking
Submit, and a new, empty trace file is generated. By default, it is unchecked.

Log files

You can read the log files by clicking on the appropriate hyperlinks (the hyperlinks work only if
the file in question has been created). The following logs can be viewed:

l Download trace file: The trace data according to the settings specified for the services.
l Download old trace file: The trace file is stored in permanent memory. When the file has
reached its size limit, it is saved as old trace file, and the current exception file is emptied
for future messages. The old trace file can be viewed here.
l Download saved trace file: Normally, the trace file is saved only in the phone RAM. When
the phone restarts in a controlled manner, the trace file is saved in permanent memory.
l Download syslog file: Messages from the phone’s operating system, including error and
exception messages.
l Download old syslog file: Old messages from the phone’s operating system.
l Download saved syslog file: Saved messages from the phone’s operating system.
l Download exception file: If an exceptions occurs in a process running on the phone, a
message is written to this file. These messages are incorporated in the syslog file.
l Download old exception file: The exception file is stored permanent memory. When the
file has reached its size limit, it is saved as old exception file, and the current exception
file is emptied for future messages. The old exception file can be viewed here.
l Download upgrade trace file: The trace log created during a software upgrade.
l Download upgrade error file: The error messages created during a software upgrade.
These messages are incorporated in the syslog file.
l Download dial plan file: If a dial plan has been uploaded to the phone, it is displayed here,
along with its status (enabled or disabled) and error status.
l Download Database file: Configuration parameters of the phone in SQLite format.
l Download HPT remote service log file: Log data from the HPT service.
l Download security log file: Log data from the Security Log Service. By pressing Submit,
the trace settings are submitted to the phone. With Reset, the recent changes can be can-
celed. The following trace levels can be selected:
n OFF: Default value. Only error messages are stored.
n FATAL: Only fatal error messages are stored.
n ERROR: Error messages are stored.
n WARNING: Warning messages are stored.
n LOG: Log messages are stored.
n TRACE: Trace messages are stored. These contain detailed information about the
processes taking place in the phone.
n DEBUG: All types of messages are stored.
144 Administration

Components / Services

l Bluetooth service (CP710 only)

l Broadsoft service
l ConversationAPI (CP710 and CP410 only)
l CPE Service
l Exchange service (CP710 and CP410 only)
l GPALAudio Core
l GPALAudio Framework
l OBEX service (CP710 only)
l OpenScape UC service (CP710 and CP410 only)
l RingCentral service
l SIP M5T stack
l vCard parser service
l Administration: Deals with the changing and setting of parameters within the phone data-
base, from both the user and the admin menus.
l Application framework: All applications within the phone, e.g. Call view, Call log, or dir-
ectory, are run within the application framework. It is responsible for the switching
between different applications and bringing them into and out of focus as appropriate.
l Application menu: This is where applications to be run on the phone can be started and
stopped.
l Call Log (CP110 / CP210): Displays the call history of the phone.
l Call View: Handles the representation of telephony calls on the phone screen.
l Certificate management: Handles the verification and exchange of certificates for secur-
ity and verification purposes.
l Clock Service: Handles the phone’s time and date, including daylight saving and NTP func-
tionality.
l Communications: Involved in the passing of call related information and signaling to and
from the CSTA service.
l Component registrar: Handles data relating to the type of phone.
l CSTA service: Any CSTA messages are handled by this service. CSTA messages are used
within the phone by all services as a common call progression and control protocol.
l Data Access service: Allows other services to access the data held within the phone data-
base.
l Desktop (CP110 / CP210): Responsible for the shared parts of the phone display. Primar-
ily these are the status bar at the top of the screen and the FPK labels.
l Digit analysis service: Analyzes and modifies digit streams which are sent to and
received by the phone, e.g. canonical conversion.
l Directory service: Performs a look up for data in the phone book, trying to match incom-
ing and outgoing numbers with entries in the phone book.
l DLS client management: Handles interactions with the DLS (Deployment Service).
l Health service: Monitors other components of the phone for diagnostic purposes and
provides a logging interface for the services in the phone.
l HTTP Service: Handles the HTTP service messages.
l Instrumentation service: Used by the HPT phone tester to exchange data with the phone
for remote control, testing and monitoring purposes.
Administration 145

l Journal service: Responsible for saving and retrieving call history information, which is
used by the Call log application.
l Media control service: Provides the control of media streams (voice, tones, ringing etc. )
within the phone.
l Media recording service: Logs the data flow generated with call recording.
l Mobility service: Handles the mobility feature whereby users can log onto different
phones and have them configured to their own profile.
l OpenStage client management: Provides a means by which other services within the
phone can interact with the database.
l Password management service: Verifies passwords used in the phone.
l Performance Marks: Aid for measuring the performance of the phone. For events
triggered by the user, a performance mark is written to the trace file, together with a
timestamp in the format “hh:mm:ss yyyy.milliseconds”, and information about the event.
The timespan between two performance marks is an indicator for the performance of the
phone.

Note The trace level must be set to "TRACE" or "DEBUG".

l Physical interface service: Handles any interactions with the phone via the keypad, mode
keys, fixed feature buttons, click wheel and slider.
l Security log service: Handles security log service messages.
l Service framework: This is the environment within which other phone services operate. It
is involved in the starting and stopping of services.
l Service registry: Keeps a record of all services currently running inside the phone.
l Sidecar service (CP710 and CP410 only): Handles interactions between the phone and
any attached sidecars.
l SIP call control: Contains the call model for the phone and is associated with telephony
and call handling.
l SIP messages: Traces the SIP messages exchanged by the phone.

Note After changing the level for the tracing of SIP messages, the phone must be
rebooted. Otherwise the changes would have no effect.

l SIP signaling: Involved in the creation and parsing of SIP messages. This service com-
municates directly with the SIP stack.
l Team service: Primarily concerned with keyset operation.
l Tone generation service: Handles the generation of the tones and ringers on the phone.
l Transport service: Provides the IP (LAN) interface between the phone and the outside
world.
l Video service engine (CP710 only): Handles the video functionality.
l Voice engine service: Provides a switching mechanism for voice streams within the
phone. This component is also involved in QDC, Music on hold and voice instrumentation.
l Voice mail (CP110 / CP210): Handles the voice mail functionality.
l Web server service: Provides access to the phone via web browser.
l 802.1x service: Provides authentication to devices attached to a LAN port, establishing a
point-to-point connection or preventing access from that port if authentication fails. The
service is used for certain closed wireless access points.
146 Administration

EasyTrace profiles
In order to simplify tracing for a specific problem, the tracing levels can be adjusted using pre-
defined settings. The “EasyTrace” profiles provide settings for a specific area, e. g. call con-
nection. On pressing Submit, those predefined settings are sent to the phone. If desired, the
settings can be modified anytime using the general mask for trace configuration under Dia-
gnostics > Fault Trace Configuration (see "Fault trace configuration" à page 142).

The following sections describe the EasyTrace profiles available for the phone.

Phone administration problems

The phone administration problems define a set of trace profiles that will help in investigating
problems in a specific area.

1. Open Diagnostics > EasyTrace Profiles > Phone administration problems.

Administration 147

Audio related problems

1. Open Diagnostics > EasyTrace Profiles > Audio related problems.

Note This EasyTrace profile contains the tracing of SIP messages. After changing the
level for the tracing of SIP messages, the phone must be rebooted.

Call proceeding problems

Open Diagnostics > EasyTrace Profiles > Call proceeding problems.

Note This EasyTrace profile contains the tracing of SIP messages. After changing the
level for the tracing of SIP messages, the phone must be rebooted.
148 Administration

Conversations / LDAP problems

1. Open Diagnostics > EasyTrace Profiles > Conversations / LDAP problems.

Keyset problems

1. Open Diagnostics > EasyTrace Profiles > Keyset problems.

Note This EasyTrace profile contains the tracing of SIP messages. After changing the
level for the tracing of SIP messages, the phone must be rebooted.
Administration 149

Mobility / DLS problems

1. Open Diagnostics > EasyTrace Profiles > Mobility / DLS problems.

Network problems

1. Open Diagnostics > EasyTrace Profiles > Network problems.

Security problems

1. Open Diagnostics > EasyTrace Profiles > Security problems.

150 Administration

Bluetooth problems

Note This option is only available for the OpenScape Desk Phone CP710.

1. Open Diagnostics > EasyTrace Profiles > Bluetooth problems.

Advanced audio traces

This feature allows the admin to turn on EPT (Broadcom EndPoint) traces, so that audio related
issues can be collected directly from the users’ phones. This helps to analyze those audio issues
faster and come to a solution.

The following information can be collected:

l EPT traces
l The status of the EPT component
l The existence of the eptMsg thread that processes the microphone packets

Administration via WBM

1. Open Diagnostics > Advanced audio traces.

l EPT trace level: can be configured from 0 (tracing disabled) up to 5 (maximum trace
level).
l Automatic clear before start: if checked, the ept file is cleared after pressing the Submit
button.
l Capture and stop:
n if checked, tracing will continue until the maximum number of lines is reached and
thenit will stop. Also, this feature will remain enabled after restart.
n if unchecked, the trace file will continuously wrap around, overwriting the older lines.
l Number of lines (Max 100000): the maximum number of lines in the eptlog file.
l Download eptlog file: opens a new web page presenting the contents of the trace file
"eptlog.txt".
l Download saved eptlog file: Saves the trace file "eptlog.txt.Save.gz" captured before the
last reboot, if there was any. To Save the flash memory space, this file is compressed.
Administration 151

l Download audio status: the current status of the audio devices, streams and the gain set-
ting. The origin of the information differs according to the platform:
n CP_LO phone models: information from /proc/ept filesystem and from pxcon tool.
n CP_HI phone models: information from mxcon tool.

QoS reports

Conditions and thresholds for report generation

Note For details about the functionality, refer to the Release Notes.

The generation of QoS (Quality of Service) reports which are sent to a QCU server is configured
here.

Administration via WBM

1. Open Diagnostics > QoS Reports > Generation.

l Report mode: Sets the conditions for generating a QoS report. Value range:
n "OFF": No reports are generated.
n "EOS Threshold exceeded": Default value. A report is created if a) a telephone con-
versation longer than the Minimum session length has just ended, and b) a threshold
value has been exceeded during the conversation.
n "EOR Threshold exceeded": A report is created if a) the report interval has just
passed, and b) a threshold value has been exceeded during the observation interval.
n "EOS (End of Session)": A report is created if a telephone conversation longer than
the Minimum session length has just ended.
n "EOR (End of Report Interval)": A report is created if the report interval has just
passed.
152 Administration

l Report interval (seconds): Time interval between the periodical observations.

n Default: 60
l Observation interval (seconds): During this time interval, the traffic is observed.
n Value: 10
l Minimum session length (100 millisecond units): When the Report mode is set to "EOS
Threshold exceeded" or "EOS (End of Session)", a report can be created only if the dur-
ation of the conversation exceeds this value.
n Default: 20
l Maximum jitter (milliseconds): When the jitter exceeds this value, a report is generated.
n Default: 20
l Average round trip delay (milliseconds): When the average round trip time exceeds this
value, a report is generated.
n Default: 100

Non-compressing codecs

The following threshold values apply to non-compressing codecs:

l Lost packets (per 1000 packets): When the number of lost packets exceeds this max-
imum value during the observation interval, a report is created.
n Default: 10.
l Consecutive lost packets: When the number of lost packets following one another
exceeds this maximum value during the observation interval, a report is created.
n Default: 2.
l Consecutive good packets: When the number of good packets following one another falls
below this minimum value, a report is created.
n Default: 8.

Compressing codecs

The following threshold values apply to compressing codecs:

General:

l Resend last report: If checked, the previous report is sent once again on pressing Submit.
By default, this is unchecked.
Administration 153

The transmission of report data can be triggered manually by pressing Send now in the local
menu.

Administration via local phone

View report
OpenScape Desk Phone CP phones generate QoS reports using a HiPath specific format, QDC
(QoS Data Collection). The reports created for the last 6 sessions, i. e. conversations, can be
viewed on the WBM.

To enable the generation of reports, ensure that:

l The switch QoS traps to QCU (System > SNMP) is activated (see "SNMP" à page 68);
l The conditions for the generation of reports are set adequately.

For details about QoS reports on OpenScape Desk Phone CP devices, see the HiPath QoS Data Col-
lection V 1.0 Service Manual.

Data viewing via WBM

1. Open Diagnostics > QoS reports > View Session Data.

154 Administration

2. Click Submit.

A QoS report contains the following data:

l Start of report period - seconds: NTP time in seconds for the start of the report period.
l Start of report period - fraction of seconds: Additional split seconds to be added to the
seconds for an exact start time.
l End of report period - seconds: NTP time in seconds for the end of the report period.
l End of report period - fraction of seconds: Additional split seconds to be added to the
seconds for an exact end time.
l SNMP specific trap type: The trap type is a 5 bit value calculated from a list of threshold-
exceeding bits. Every time a threshold is exceeded, the associated bit is set, otherwise it
is cleared. The trace type bits are defined as follows:
n Bit 0: Jitter threshold was exceeded.
n Bit 1: Delay threshold was exceeded.
n Bit 2: Threshold for lost packets was exceeded.
n Bit 3: Threshold for consecutive lost packets was exceeded.
n Bit 4: Threshold for consecutive good packets was exceeded.
l IP address (local): IP address of the local phone.
l Port number (local): RTP receiving port of the local phone.
l IP address (remote): IP address of the remote phone that took part in the session.
l Port number (remote): RTP sending port of the local phone.
l SSRC (receiving): RTP Source Synchronization Identifier of the local phone.
l SSRC (sending): RTP Source Synchronization Identifier of the remote phone.
l Codec: Number of the Payload Type applied in the session; see RFC 3551 (Table 4 and 5).
l Maximum packet size: Maximum size (in ms) of packets received during the report inter-
val.
l Silence suppression: Number of silence suppression activation objects found in the RTP
stream received. A silence suppression activation object is defined as a period of silence
when no encoded voice signals were transmitted by the sender.
l Count of good packets: Total amount of good packets.
l Maximum jitter: Maximum jitter (in ms) found during the report interval.
l Maximum inter-arrival jitter: Maximum of the interarrival jitter values (in ms). The interar-
rival jitter is the smoothed absolute value of the jitter measurements. It is calculated con-
tinuously. For details about the calulation, see RFC 3550.
l Periods jitter threshold exceeded: Number of observation intervals in which the threshold
for maximum jitter was exceeded.
l Round trip delay: Average value of delay calculated for each RTCP packet. The first value
is available after about 15 sec.
l Round trip delay threshold exceeded: Set to "true" if the average round trip delay
threshold value was exceeded in the report interval.
l Count of lost packets: Number of packets lost in the course of speech decoding.
l Count of discarded packets: Number of the packets discarded without transferring the
contents.
l Periods of lost packets: Number of observation intervals in which the threshold for lost
packets was exceeded.
Administration 155

l Consecutive packet loss (CPL): List of sequences consecutive packets that were all lost,
grouped according to the amount of packets per sequence. The first number in the list
counts single lost packets, the second number counts sequences of two lost packets, and
so on. The last number counts sequences of more than 10 lost packets.
l Periods of consecutive lost packets: Number of observation intervals in which the
threshold for consecutive lost packets was exceeded.
l Consecutive good packets (CGP): List of sequences consecutive packets that were all
processed, grouped according to the amount of packets per sequence. The first number
in the list counts single good packets, the second number counts sequences of two good
packets, and so on. The last number counts sequences of more than 10 good packets. All
values are reset to 0 after an interval without packet loss.
l Periods of consecutive good packets: Number of intervals in which the count of lost pack-
ets went below the threshold.
l Count of jitter buffer overruns: Number of packets rejected because the jitter buffer was
full.
l Count of jitter buffer under-runs: Increased by one whenever the decoder requests new
information on decoding and finds an empty jitter buffer.
l Codec change on the fly: The value is 1, if there has been a codec or SSRC change during
the observation period, and 0, if there has been no change.
l Periods with at least one threshold exceeded: Number of observation intervals with at
least one threshold exceedance. If there is no data, the value is 255. The threshold values
included are:
n maximum jitter;
n lost packets;
n consecutive lost packets;
n consecutive good packets.
l HiPath Switch ID: Unique number identifying the HiPath switch to which the endpoints are
assigned.
l LTU number: In HiPath 4000 only, the shelf identification is taken from the shelf con-
taining a gateway.
l Slot number: The slot number where the phone is connected in the shelf.
l Endpoint type : Type of the local phone.
l Version: Software version of the local phone.
l Subscriber number type: Type of subscriber number assigned to the local phone. The
possible types are:
n 1: local number, extension only
n 2: called number, network call
n 3: E.164 number of the local phone
l Subscriber number: Subscriber number of the local phone.
l Call ID: SIP call id.
l MAC address: MAC address of the local phone.
156 Administration

Miscellaneous

IP tests
For Network diagnostics, the OpenScape Desk Phone CP phone can ping any host or Network
device to determine whether it is reachable.

Administration via WBM

1. Open Diagnostics > Miscellaneous > IP tests.

l Pre Defined Ping tests: Pings a predefined IP address. Value range: "Ping DLS", "Ping
HiPath gatekeeper", "Ping standby HiPath gatekeeper"
l Ping tests: Pings the entered host IP address or hostname.
l Pre Defined Trace tests: Pings a predefined Traceroute IP address. Value range:
"Traceroute DLS", "Traceroute HiPath gatekeeper", "Traceroute standby HiPath gate-
keeper"
l Traceroute: Pings the entered host IP address or hostname.

Memory status information

The processes currently running on the phone operating system as well as their CPU and
memory usage can be monitored here. 100 processes are monitored on the web page. For fur-
ther information, refer to the manual of the "top" command for Unix / Linux systems, or to related
documentation.

The amount of free memory is checked on a regular basis in order to prevent problems caused
by low memory. This check determines whether a recovery is necessary.
Administration 157

Administration via WBM

1. Open Diagnostics > Miscellaneous > Memory information.

l When “Disable reboot” is checked, no reboot will take place when a memory problem has
been found. However, recovery requires a reboot. The recovery process is triggered when
the available main memory (RAM) falls below a given threshold value. As memory con-
sumption is assumed to be higher during working hours, two thresholds are configurable.
l The High Threshold (MBs) parameter defines the threshold for off-time:
n For OpenScape Desk Phone CP110/210, the default value is 10 MB.
n For OpenScape Desk Phone CP410/710, it is 30 MB.
l With Low Threshold (MBs), the threshold for off-time is defined:
n For OpenScape Desk Phone CP110/210, the default value is 8 MB.
n For OpenScape Desk Phone CP410/710, it is 20 MB.

l The beginning and end of the working hours are defined in 24 hours format with Working
Hour Start (Default: 5) and Working Hour End (Default: 24).

When memory shortage has occurred, information about the incident is written to a log file
which can be viewed via the “Download memory info” file link.

If there has been a previous case of memory shortage, the corresponding log file can be viewed
via “Download memory info” file.
158 Administration

Core dump

Administration via WBM

1. Open Diagnostics > Miscellaneous > Core Dump.

l If “Enable core dump” is enabled, a core dump is initiated in case of a severe error. The
core dump is saved to a file. By default, this function is active.
l If “Delete core dump” is activated, the current core dump file is deleted when clicking Sub-
mit.
n By default, this feature is not enabled.
l If one or more core dump file exist, hyperlinks for downloading are created automatically.

Remote tracing — syslog

All trace messages created by the components of the phone software can be sent to a remote
server using the syslog protocol. This is helpful especially for long-term observations with a
greater number of phones.

Administration via WBM

1. Open Diagnostics > Remote trace.

l To enable remote tracing, “Remote trace status” must be enabled. Furthermore, the IP
address of the server receiving the syslog messages must be entered as remote server,
and the corresponding server port must be given in remote port.
l With version V2, the user notification parameter controls whether the user is notified
about the remote tracing or not. If “Use notification” is enabled, a blinking icon will inform
the user when remote tracing is active, i.e. when “Remote trace status” is enabled.
Administration 159

Administration via local phone

Key modules
Note On an OpenScape Desk Phone CP110 / CP210 phone no key modules can be con-
nected.

l On an OpenScape Desk Phone CP410 phone the key module KM410 provides 16 addi-

tional free programmable keys. The names of the assigned keys can be printed on labels.
l On an OpenScape Desk Phone CP710 the key module KM710 provides 12 additional free
programmable keys. The names of the assigned keys are displayed digitally and can have
multiple functions ("shifted") invoked by pressing the key .
l The maximum number of key modules that can be attached depends on the phone model,
the key module type and whether Power over Ethernet (PoE) is used to power the phone.
However, up to 4 key modules can be attached if the phone is not powered by PoE.

The configuration of a key on the key module is exactly the same as the configuration of a phone
key.

Administration via WBM

1. Open System > Features > Key module X.

l The configured keys can be either be in “Normal” or “Shifted” level.
l When switching to the “Shifted” level, the phone switches automatically back to the
“Normal” level, unless configured otherwise.
160 Administration

2. Open System > Features > Configuration.

3. To configure the phone to automatically switch back to the normal level, enable Auto-
matic key module switchback. The phone will start a 15 seconds timer and then switch to
the non-shifted level on all the attached key modules.
4. Click Submit.
Examples and how-tos 161

Examples and how-tos

Canonical dialing

Canonical dialing settings

The following example shows settings suitable for the conversion of given dial strings to canon-
ical format.

Example
Parameter Explanation
value

Local country code 44 International country code for the UK.

Used in front of national codes when dialed without

National prefix digit 0
international prefix.

Local national code 115 Area code within the UK (here: Nottingham).

Minimum local num- Number of digits in a local PSTN number (e. g. 3335333
7
ber length = 7 digits).

Prefix to access Nottingham numbers from within the

Local enterprise node 780
company Network.

PSTN access code 9 Prefix to make an international call in the UK.

Operator codes 0, 7800 Set of numbers to access the local operators.

Emergency numbers 999, 555 Set of numbers to access emergency services.

2, 3, 4, 5, 6, 1st digits of numbers that are used for extension num-

Initial extension digits
8 bers on the local node.

Canonical dialing look-up

The following example shows settings suitable for recognizing incoming numbers and assigning
them to entries in the local phone-book, and for generating correct dial strings from phone book
entries, depending on whether the number is internal or external.
162 Examples and how-tos

Example
Parameter Explanation
value

Local code
780 Enterprise node prefix (here: Nottingham).
<1>

Equivalent prefix to access numbers on this node from the

International PSTN. Here, the prefix used by the PSTN (DID/DDI: direct
+44115943
code <1> inward dialing) is 943, which differs from the enterprise
node prefix used within the enterprise Network.

Local code
7007 Enterprise node prefix (here: Munich).
<2>

Equivalent prefix to access numbers on this node from the

International
+49897007 PSTN. Here, the prefix used by the PSTN for direct inward
code <2>
dialing is identical to the enterprise node prefix.

Conversion examples
In the following examples, numbers entered into the local Directory by the user are converted
according to the settings given above.

Example 1: Internal number, same node as the local phone

User entry 2345

External numbers Local public form

External access code Not required

International gateway code Use national code

Number stored in the Directory +441159432345

Internal numbers = Local enter-

1234
prise form

Dial string sent when dialing from the Internal numbers = Always add
7802345
Directory node

Internal numbers = Use external

9432345
numbers
Examples and how-tos 163

Example 2: Internal number, different node

User entry 70072345

External numbers Local public form

External access code Not required

International gateway code Use national code

Number stored in the Directory +498970072345

Internal numbers = Local enter-

2345
prise form

Dial string sent when dialing from the Internal numbers = Always add
7802345
Directory node

Internal numbers = Use external

9432345
numbers

Example 3: External number, same local national code as the local phone

User entry 011511234567

External numbers Local public form

External access code Not required

International gateway code Use national code

Number stored in the Directory +4411511234567

External numbers =
234567
Local public form

Dial string sent when dialing from the External numbers =

011511234567
Directory National public form

External numbers =
004411511234567
International form
164 Examples and how-tos

How to set up the “Corporate directory” (LDAP)

The “Corporate directory” function is based on an LDAP client that can be connected to the com-
pany’s LDAP service. A variety of LDAP servers can be used, for instance Microsoft Active Dir-
ectory, OpenLDAP, or Apache Directory Server.

Prerequisites
l An LDAP server is present and accessible to the phone’s network. The standard server
port for LDAP is 389, the standard transport for LDAP is TCP.
l Query access to the LDAP server must be provided. Unless anonymous access is used, a
user name and password must be provided. It might be feasible to use a single login and
password for all OpenScape Desk Phone CP phones.

Create an LDAP template

The task of an LDAP template is to map the phone’s contact fields to LDAP attributes that can
be delivered by the server. In the LDAP template, the fields are represented by hard-coded
names: ATTRIB01, ATTRIB02, and so on. These field names are assigned to LDAP attributes,
as appropriate.

The following examples show the relations between GUI field names, the attribute labels used in
the template, and exemplary mappings to LDAP attributes.

Note In an LDAP template for OpenScape Desk Phone CP, the entries must be sorted
according to the sequential number of the template labels, as shown in the
example underneath.
Examples and how-tos 165

Administration via WBM

1. Open Local functions > LDAP template.

2. Enter the field names and specify the usage type “read-only”).

l
"Nickname" does not correspond to a contact field but instead relates to a special
attribute that may be defined for LDAP entries. The attribute represents a free
format field which may be searched for sub-strings. It is only used for search
actions by the phone, not number lookups. If the Nickname attribute is defined in
the LDAP template, a phone search action will look for the search string as a sub-
string in this field and will ignore the other field attributes.

Generic example (standard attributes)

OpenScape Desk LDAP tem-

LDAP attribute Example value
Phone CP field plate lables

Last name ATTRIB01 surnameNational Doe

First name ATTRIB02 givenNameNational John

Work 1 ATTRIB03 telephoneNumber 9991234

Work 2 ATTRIB04 AlternatePhone 9992345

Mobile ATTRIB05 mobile 017711223344

166 Examples and how-tos

OpenScape Desk LDAP tem-

LDAP attribute Example value
Phone CP field plate lables

Home ATTRIB06 otherTelephone 441274333444

Company ATTRIB07 ou Example Inc.

Address 1 ATTRIB08 departmentText 0815

Address 2 ATTRIB09

Role ATTRIB10 mainFunction Product Manager

Email ATTRIB11 mail [email protected]

Nickname ATTRIB12 nickname

jpeg image or image name,

Avatar ATTRIB13 more information in the
à 109

Using the example above as the LDAP subtree to be searched, the LDAP template file looks like
this:

OpenScape Desk Phone CP LDAP TEMPLATE (v.1)

SEARCHBASE=“O=SIEMENS COMM, C=GB”
ATTRIB01=”surnameNational”
ATTRIB02=”givenNameNational”
ATTRIB03=”telephonenumber”
ATTRIB04=”AlternatePhone”
ATTRIB05=”mobile”
ATTRIB06=”otherTelephone”
ATTRIB07=”ou”, READONLY
ATTRIB08=”departmentText”, READONLY
ATTRIB09=””
ATTRIB10=”mainFunction”
ATTRIB11=”mail”
ATTRIB12=”nickname”
ATTRIB13=””
EOF
Examples and how-tos 167

Microsoft Active Directory specific example

OpenScape Desk LDAP template

LDAP attribute Example value
Phone CP field attribute

Last name ATTRIB01 sn Doe

First name ATTRIB02 givenName John

Business 1 ATTRIB03 ipPhone 9991234

Business 2 ATTRIB04 otherTelephone 9992345

Mobile ATTRIB05 mobile 017711223344

Private ATTRIB06 homePhone 441274333444

Company ATTRIB07 company Example Inc.

Address 1 ATTRIB08 department Administration

Address 2 ATTRIB09 l

Job function ATTRIB10 title Product Manager

Email ATTRIB11 mail [email protected]

Nickname ATTRIB12 nickname

Avatar ATTRIB13 jpeg image

Using the example above as the LDAP subtree to be searched, the LDAP template file looks like
this:
168 Examples and how-tos

OpenScape Desk Phone CP LDAP TEMPLATE (v.1)

SEARCHBASE="dc=example,dc=com"
ATTRIB01="sn"
ATTRIB02="givenName"
ATTRIB03="ipPhone"
ATTRIB04="otherTelephone"
ATTRIB05="mobile"
ATTRIB06="homePhone"
ATTRIB07="company"
ATTRIB08="department"
ATTRIB09="l"
ATTRIB10="title"
ATTRIB11="mail"
ATTRIB12=”nickname”
ATTRIB13=””
EOF

Upload the LDAP template to the phone

The administrator may edit the LDAP template on the phone via WBM, or via the DLS. After con-
figuring the LDAP template, it is uploaded to the phone:

1. Save the template under a suitable name, e.g. ldap-template.txt.

2. Copy the template file to the FTP server designated for deploying LDAP templates.
3. Upload the file using the WBM (see "LDAP template" à page 111).
4. Optionally, use the local menu or the DLS (see the Deployment Service Administration
Manual).

Administration via WBM

1. Open File transfer > LDAP.

2. Enable “Use defaults” to Save the settings as default values.

3. Select the download method.
Examples and how-tos 169

4. Enter the server information and user credentials.

5. Specify the file name.
6. Select the action after submitting the information (“do nothing”, “start download”).
7. Click Submit.

Configure LDAP access

Administration via WBM

1. Open Local Functions > Directory Settings.

2. Enter the following parameters:

l LDAP Server address: IP address or host name of the LDAP server
l Transport: allows the LDAP interface to be encrypted using TLS (via LDAPS) or
unencrypted using TCP, typically TCP
l Secure port: port used by the LDAP for encrypted (TLS) transport, typically 636
l LDAP Server port: port used by the LDAP for unencrypted (TCP) transport, typically
389
l Authentication: authentication method for the connection to the LDAP server
l User name: only required if simple authentication is selected
l Password: corresponding to the user name
l Permanent LDAP enabled
3. Click Submit.

Mapping the LDAP fields

The downloaded LDAP template can be edited on the phone via WBM.
170 Examples and how-tos

1. Open Local functions > LDAP template.

2. Map the field names to the usage types.

3. Click Submit.

LLDP-Med example
The following example illustrates the mode of operation of LLDP-MED. To evoke a reaction from
LLDP-MED, the LAN switch has been set to auto-negotiation, whereas the phone’s LAN port is
set to 100 Mbit/s, hence a fixed value (see "LAN port settings" à page 49). This configuration
error is discovered by LLDP-MED. The following screenshots from the phone local menu show
the error messages.

The WBM provides a list of the LLDP-MED TLV messages rather than the more limited LLDP-
MED operation menu in local settings. The TLV list is comprehensive whereas the local settings
indicate problems with the TLVs.

Note Note the status of MAC_Phy config.

When MAC_Phy config is selected, the details are displayed.

Examples and how-tos 171

1. Log in as administrator on the local phone’s admin menu.

2. In the Admin menu, open Network > LLDP-MED Operation.
3. Press OK.
4. In the LLDP-MED operation submenu, navigate to MAC_Phy config.
5. Note the status displayed.
6. Select the MAC_Phy config submenu by pressing OK.
7. Navigate to the parameters displayed by using the navigation keys. The following status
is displayed for the MAC_Phy config parameters:
l AutoSet enabled = Incompatible
l MAU = Incompatible
172 Technical reference

Technical reference

Default port list

The following table contains all default ports, resp. port ranges, and protocols used by the services
running on OpenScape Desk Phone CP110/210/410/710 phones.

Server Client Protocol

Service
Default Port Default Port Stack

Payload transport (VoIP) 5010 - 5059 5010 - 5059 RTP - RTCP

SRTP -
Payload transport (VoIP) 5010 - 5059 5010 - 5059
SRTCP

32786 -
SIP subscriber - TCP is used 5060 SIP / TCP
61000

32786 -
SIP subscriber - TLS is used 5061 SIP / TLS
61000

SIP subscriber - UDP is used 5060 5060 SIP / UDP

32786 -
Directory access via LDAP --- TCP
61000

32786 - TCP-
Directory access via LDAP ---
61000 SSL/TLS

DHCP /
DHCP Client --- 68
UDP

DNS / TCP_
DNS Client --- 1024 - 65535
UDP

HTTP /
DLS contact me service - workpoint side 8085 ---
TCP

HTTPS /
Default communication with the DLS work- TCP -
--- 18443
point interface
SSL / TLS

Secure communication with the DLS work- --- 18444 HTTPS /

Technical reference 173

Server Client Protocol

Service
Default Port Default Port Stack

TCP -
point interface
SSL / TLS

32786 -
Connection to the control port of FTP server 21 FTP / TCP
61000

32786 -
FTP client; uses the FTP server in active mode 20 FTP / TCP
61000

HTTPS /
32786 - TCP -
HTTPS file download server 443
61000
SSL/TLS

Client application which sends QDC data to 32786 - SNMP /

---
the QCU 61000 UDP

32786 - SNMP /
Part of SNMP-Agent - sending Traps ---
61000 UDP

Part of SNMP-Agent - receive Set/Get com- SNMP /

161 ---
mands UDP

SNTP client - queries time information in uni- SNTP /

--- 123
cast operation UDP

SNTP client - receives time information in SNTP /

123 ---
broadcast operation UDP

HTTP /
Web server for WBM access 8085 ---
TCP

HTTPS /
Secure Web Server for WBM access 443 --- TCP -

SSL / TLS

Troubleshooting error codes

For a set of error cases, specific error codes are defined. These error codes are shown in brack-
ets on the display, following a general error note.
174 Technical reference

Example

“No Telephony possible (LP)”

Network Errors

Error
Priority Problem Description
code

Unable to use LAN con-

LP 0 Physical connection error
nection

Unable to use LAN con-

LX 1 802.1x errors
nection

Unable to register HFA

L1 2 No IP address - Manual config mode
main line

Unable to register HFA

L2 3 No default route - Manual config mode
main line

Unable to register HFA

L3 4 No default route - Manual config mode
main line

Unable to use LAN con- Network Configuration Error â “ General IP

LI 5
nection error - Manual config mode

Unable to contact
D0 6 Network Configuration Error - DHCP failure
DHCP

Unable to establish a
TT 7 No SNTP server
TLS connection

HFA Configuration Errors

Error code Priority Problem Description

H4 8 Unable to register HFA main line No gateway IP address

H5 9 Unable to register HFA main line No subscriber number

RA 10 Unable to establish a TLS connection Certificate error

Technical reference 175

Communication Errors

Error
Priority Problem Description
code

Unable to register HFA

HA 11 Logon: Maintenance busy
main line

Unable to register HFA

HB 11 Logon: No port available
main line

Unable to register HFA

Hb 11 Logon: Rejected due to invalid LIN
main line

Unable to register HFA Logon: Rejected due to mobile terminal

Hc 11
main line blocked

Unable to register HFA

HD 11 Logon: No port available (Ext)
main line

Unable to register HFA Logon: Rejected due to incompatible security

Hd 11
main line profile

Unable to register HFA Logon: Rejected due to TCP usage while TLS
He 11
main line is required

Unable to register HFA

HE 11 Logon: Client not registered
main line

Unable to register HFA

HF 11 Logon: Rejected due to logoff
main line

Unable to register HFA Logon: Reject due to PBX version not suf-
Hf 11
main line ficient

Unable to register HFA

HG 11 Logon: Rejected due to logoff in progress
main line

Unable to register HFA

HH 11 Logon: Rejected due to shutdown
main line

Unable to register HFA

HI 11 Logon: Rejected due to duplicate Logon
main line

HJ 11 Unable to register HFA Logon: Rejected due to already logged on

176 Technical reference

Error
Priority Problem Description
code

main line

Unable to register HFA

HK 11 Logon: Rejected due to PIN not present
main line

Unable to register HFA

HL 11 Logon: Rejected due to password not present
main line

Unable to register HFA

HM 11 Logon: Rejected due to password not correct
main line

Unable to register HFA

HN 11 Logon: Rejected due to invalid license
main line

Unable to register HFA

Ha 11 Logoff: Rejected due to missing LN
main line

Unable to register HFA

HQ 11 Logoff: Normal Logoff
main line

Unable to register HFA

HR 11 Logoff: Client not logged on
main line

Unable to register HFA

HS 11 Logoff: Client logged off
main line

Unable to register HFA

HT 11 Logoff: Forced client logoff
main line

Unable to register HFA

HU 11 Logoff: Timeout expired
main line

Unable to register HFA

HV 11 Logoff: OMC action
main line

Unable to register HFA

HW 11 Logoff: Hfa mobile user logged on
main line

Unable to register HFA

HX 11 Logoff: Switch back to central system
main line

Unable to register HFA

HY 11 Logoff: No bearer channel
main line
Technical reference 177

Error
Priority Problem Description
code

Unable to register HFA

HZ 11 Logoff: New logon requested from the server
main line

Unable to register HFA Logoff: Forced client logoff due to an incor-

H[ 11
main line rect PreShared secret

Unable to register HFA

H0 12 General Error
main line

UC (WSI) server not

UC1 13 Invalid UC server access configuration
accessible

UC logon rejected/not
UC2 14 No access to UC service (UC mode)
available

l Exchange: check username and password

EX 15 Exchange failure l Exchange: untrusted server
l connection to Exchange server failed

l Circuit: check username and password

CI 16 Circuit failure l Circuit: untrusted server
l connection to Circuit server failed

SNTP server unavail-

NT 17 No SNTP connection
able
Glossary 178

Glossary
Address of Record (AoR)
A SIP URI that represents the "public address" of a SIP user resp. a phone or line The format is
similar to an E-mail address: "username@hostname".

ADPCM
Adaptive Differential Pulse Code Modulation. A compressed encoding method for audio signals
which are transmitted by a low bandwidth. A sample is coded as the difference between its pre-
dicted value and its real value. As this difference is usually smaller than the real, absolute value
itself, a lesser number of bits can be used to encode it.

BLE
Bluetooth Low Energy

CSTA
Computer Supported Telecommunications Applications. An abstraction layer for tele-
communications applications allowing for the interaction of computer applications with tele-
phony devices and networks.

CTI
Computer Telephony Integration. This term denotes the interaction of computer applications
with telephony devices and networks.

DFT
Digital Feature Telephone. A phone with no line keys.

DHCP
Dynamic Host Configuration Protocol. Allows for the automatic configuration of Network end-
points, like IP Phones and IP Clients.

DiffServ
Differentiated Services. Specifies a layer 3 mechanism for classifying and managing Network
traffic and providing quality of service guarantees on networks. DiffServ can be used to provide
low-latency, guaranteed service for e. g. voice communication.
179 Glossary

DLS
The Deployment Service (DLS) is a OpenScape management application for the administration
of workpoints, i. e. IP Phones and IP Clients, in both HiPath- and non-HiPath networks.

DNS
Domain Name System. Performs the translation of Network domain names and computer host-
names.

DTMF
Dual Tone Multi Frequency. A means of signaling between a phone and e. g. a voicemail facility.
The signals can be transmitted either in-band, i. e. within the speech band, or out-band, i. e. in a
separate signaling channel.

EAP
Extensible Authentication Protocol. An authentication framework that is frequently used in
WLAN networks. It is defined in RFC 3748.

FTP
File Transfer Protocol. Used for transferring files in networks, e. g., to update telephone soft-
ware.

G.711
ITU-T standard for audio encoding, used in e.g. ISDN. It requires a 64 kBit/s bandwidth.

G.722
ITU-T standard for audio encoding using split band Network. The audio bandwidth is 7 kHz at a
sampling rate of 16 kHz. There are several transfer rates ranging from 32 to 64 kBit/s, which cor-
respond to different compression degrees. The voice quality is very good.

G.729
ITU-T standard for audio encoding with low bandwidth requirements, mostly used in VoIP. The
standard bit rate is 8 kBit/s. Music or tones such as ring tones or fax tones cannot be trans-
ported reliably with this codec.

Gateway
Mediation components between two different Network types, e. g., WiFi Network and ISDN Net-
work.
Glossary 180

HTTP
Hypertext Transfer Protocol. A standard protocol for data transfer in internet networks.

IP
Internet Protocol. A data-oriented Network layer protocol used for transferring data across a
packet-switched Network. Within this Network layer, reliability is not guaranteed.

IP address
The unique address of a terminal device in the Network. It consists of four number blocks of 0 to
255 each, separated by a point.

Jitter
Latency fluctuations in the data transmission resulting in distorted sound.

LAN
Local Area Network. A computer Network covering a local area, like an office, or group of build-
ings.

Layer 2
2nd layer (Data Link Layer) of the 7-layer OSI model for describing data transmission interfaces.

Layer 3
3rd layer (Network Layer) of the 7-layer OSI model for describing the data transmission inter-
faces.

LCD
Liquid Crystal Display. Display of numbers, text or graphics with the help of liquid crystal tech-
nology.

LDAP
Lightweight Directory Access Protocol. Simplified protocol for accessing standardized directory
systems, e.g., a company telephone directory.

LED
Light Emitting Diode. Cold light illumination in different colours at low power consumption.

MAC Address
Media Access Control address. Unique 48-bit identifier attached to Network adapters.
181 Glossary

MDI-X
Media Dependent Interface crossover (X). The send and receive pins are inverted. This MDI
allows the connection of two endpoints without using a crossover cable. When Auto MDI-X is
available, the MDI can switch between regular MDI and MDI-X automatically, depending on the
connected device.

MIB
Management Information Base. A type of database used to manage the devices in a com-
munications Network.

MWI
Message Waiting Indicator. A signal, typically a LED, to notify the user that new mailbox mes-
sages have arrived.

PBX
Private Branch Exchange. Private telephone system that connects the internal devices to each
other and to the ISDN Network.

PCM
Pulse Code Modulation. A digital representation of an analog signal, e. g. audio data, which con-
sists of quantized samples taken in regular time intervals.

PING
Packet Internet Gro(u)per. A program to test whether a connection can be made to a defined IP
target. Data is sent to the target and returned from there during the test.

PoE
Power over Ethernet. The IEEE 802.3af standard specifies how to supply power to compliant
devices over Ethernet cabling (10/100Base-T).

Port
Ports are used in networks to permit several communication connections simultaneously. Dif-
ferent services often have different port numbers.

PSTN
Public Switched Telephone Network. The Network of the world's public circuit-switched tele-
phone networks.
Glossary 182

QoS
Quality of Service. The term refers to control mechanisms that can provide different priority to
different users or data flows, or guarantee a certain level of performance to a data flow in
accordance with requests from the application program. The OpenScape Desk Phone CP phone
allows for the setting of QoS parameters on layer 2 and layer 3 (DiffServ).

RAM
Random Access Memory. Memory with read / write access.

ROM
Read Only Memory. Memory with read only access.

RTCP
Realtime Transport Control Protocol. Controls the à 178 stream and provides information about
the status of the transmission, like QoS parameters.

RTP
Realtime Transport Protocol. This application layer protocol has been designed for audio com-
munication.

SDP
Session Description Protocol. Describes and initiates multimedia sessions, like web con-
ferences.

SNMP
Simple Network Management Protocol. Used for monitoring, controlling, and administration of
Network and Network devices.

SNTP
Simple Network Time Protocol. Used to synchronize the time of a terminal device with a
timeserver.

Subnet Mask
To discern the Network part from the host, a device performs an AND operation on the IP
address and the Network mask. The Network classes A, B, and C each have a subnet mask that
demasks the relevant bits: 255.0.0.0 for Class A, 255.255.0.0 for Class B and 255.255.255.0 for
Class C. In a Class C Network, for instance, 254 IP addresses are available.
183 Glossary

Switch
Network device that connects multiple Network segments and terminal devices. The forwarding
of data packets is based on switches: data targeted to a specific device is directed to the switch
port that device is attached to.

TCP
Transfer Control Protocol. The protocol belongs to the transport layer and establishes a con-
nection between two entities on the application layer. It guarantees reliable and in-order delivery
of data from sender to receiver.

TLS
Transport Layer Security. Ensures privacy between communicating applications. Typically, the
server is authenticated, but mutual authentication is also possible.

URI
Uniform Resource Identifier. A compact string of characters used to identify or name a resource.

URL
Uniform Resource Locator. A special type Network address that provides means of acting upon
or obtaining a representation of the resource by describing its primary access mechanism or Net-
work location.

VLAN
Virtual Local Area Network. A method of creating several independent logical networks within a
physical Network. For example, an existing Network can be separated into a data and a voice
VLAN.

VoIP
Voice over IP. A term for the protocols and technologies enabling the routing of voice con-
versations over the internet or through any other Network

WBM
Web Based Management. A web interface which enables configuration of the device using a
standard web browser.
Provide feedback to further optimize this document to [email protected].

As reseller please address further presales related questions to the responsible presales organization at Unify or at
your distributor. For specific technical inquiries you may use the support knowledge base, raise - if a software support
contract is in place - a ticket via our partner portal or contact your distributor.

Our Quality and Environmental Management Systems are implemented

according to the requirements of the ISO 9001 and ISO 14001 standards
and are certified by an external certification company.

All rights reserved.
Reference No.: A31103-C1100-M102-13-76A9
The information provided in this document contains merely general descriptions or
characteristics of performance which in case of actual use do not always apply as
described or which may change as a result of further development of the products.
An obligation to provide the respective characteristics shall only exist if expressly
agreed in the terms of contract.
Availability and technical specifications are subject to change without notice.
Unify, OpenScape, OpenStage and HiPath are registered trademarks of Unify
Software and Solutions GmbH & Co. KG. All other company, brand, product and
service names are trademarks or registered trademarks of their respective holders.
atos.net

Common questions

When configuring a SNTP server via DHCP, it is crucial to consider the IP address or hostname of the server and the required time zone offset. The SNTP IP address must be specified using DHCP option #42, while the time zone offset is configured with option #2. Correct configuration ensures synchronized time across network devices .

Canonical dialing settings play a critical role in supporting international communication by ensuring numbers are parsed and formatted according to international standards. This involves adding necessary country and area codes, which standardizes call setup and enhances interoperability across diverse telecommunication networks .

When DHCP lease reuse is activated, the phone maintains its DHCP-assigned IP address despite the lease expiration, which enhances network stability during DHCP server outages. This is achieved by the phone periodically sending ARP requests to prevent address conflicts and discovery messages to obtain a new lease .

Storing contacts and pictures using LDAP for phones involves configuring the LDAP server to interface with the phone for accessing and updating contact details securely and efficiently. LDAP allows phones to access a directory server for retrieving contact information and pictures either directly from LDAP attributes like "jpegPhoto" or indirectly via URLs stored in "photoURL" attributes . This setup supports retrieval and display of contact avatars in specified formats (32x32 px and 64x64 px) and can update contact information dynamically based on LDAP entries . Security is maintained through options like encrypted TLS connections and authentication requirements, while the configuration of LDAP templates is necessary to map server attributes to phone contact fields for seamless integration .

The LLDP-MED protocol offers several advantages for VLAN discovery over DHCP-based methods. Firstly, LLDP-MED provides automatic VLAN configuration through the network switch, using LLDP-MED TLV elements to convey VLAN IDs directly to devices, reducing manual provisioning and configuration errors . Unlike DHCP, which requires the configuration of vendor-specific options, LLDP-MED directly communicates VLAN information as part of its network advertisement capabilities, making the process simpler and less error-prone . It also allows for the consistent exchange of other network policies and Quality of Service (QoS) parameters, supporting more integrated network management . Additionally, LLDP-MED can operate over existing network infrastructure without the need for DHCP server configurations, providing a more flexible and dynamic approach to VLAN management .

Configuring vendor-specific settings via DHCP is advantageous because it allows for full Plug & Play functionality while ensuring security and authenticity of network components like DLS servers. DHCP automatically provides essential configuration data to devices during start-up, reducing manual configuration errors and ensuring network settings such as IP addresses, VLAN IDs, and necessary security protocols are consistently applied across devices . Furthermore, using DHCP for network setup can simplify the management of changes across multiple devices by centralizing configuration tasks on a server, rather than requiring individual device configuration .

Converting phone numbers to a fully qualified E.164 format in LDAP directories ensures that the numbers are globally unique and consistent, providing a standardized dialing format that can be used across different geographic locations and networks. This standardization simplifies call routing and recognition of numbers, especially in systems that integrate with various telecommunications networks. Additionally, using E.164 format allows the LDAP directory to store numbers in a consistent format that matches international dialing requirements, facilitating easier integration and interoperability with external systems and ensuring accurate lookup and retrieval of contact information .

The canonical dial look-up feature ensures that incoming call numbers are accurately matched to directory entries by converting them into a fully qualified format. This process includes adding country and area codes to the subscriber number, making sure that each number is unique and can be reliably looked up in the directory server . This standardized format facilitates the recognition of incoming calls and the correct display of contact details sourced from centralized directories like LDAP, allowing proper handling of incoming calls without confusion caused by different number formats . Additionally, this capability is crucial for phones to consistently identify callers from various local and international networks, by accurately analyzing and matching incoming numbers against predefined patterns ."}

The Deployment Service (DLS) server enhances network security for phones by enforcing that connections from the phone to the DLS server are outbound only, thereby preventing unauthorized inbound connections from reaching the phone. Furthermore, the DLS server can configure a "Contact-Me" proxy (DCMP) that allows the phone to periodically check for updates without direct inbound requests from the server, adding another layer of security by leveraging controlled outbound communication . Additionally, mutual authentication can be configured which ensures that both the DLS server and the phone exchange credentials to verify each other's identity before securing communication, thereby preventing man-in-the-middle attacks . A security PIN can also be utilized for decrypting data during initial communication set-up, ensuring secure data exchange during the bootstrap phase .

If a phone is configured to an incorrect VLAN, it may not be able to connect to the network . Additionally, if the phone is set in static IP mode within an incorrect VLAN, it may prevent server connections . This misconfiguration can lead to improper network routing and a failure in establishing essential communications, impacting the phone's operational capabilities .

OS4k Linux Commands PDF
No ratings yet
OS4k Linux Commands PDF
17 pages
OpenScape 4000 V8 Softgate MOH
No ratings yet
OpenScape 4000 V8 Softgate MOH
6 pages
Recovery HD Procedure for HiPath 4000
No ratings yet
Recovery HD Procedure for HiPath 4000
7 pages
OpenScape 4000 V8OpenScape 4000 V8 Volume 4 IP Solutions Service Documentation Issue 40
No ratings yet
OpenScape 4000 V8OpenScape 4000 V8 Volume 4 IP Solutions Service Documentation Issue 40
1,543 pages
OpenScape 4000 V7, Section 4 - IP Solutions, Service Documentation, Issue 2 PDF
No ratings yet
OpenScape 4000 V7, Section 4 - IP Solutions, Service Documentation, Issue 2 PDF
1,256 pages
OpenScape Cordless Enterprise V7 Overview
No ratings yet
OpenScape Cordless Enterprise V7 Overview
4 pages
OpenScape 4000 Assistant V11, HG3550 Manager and STMI - NCUI Manager, Administrator Documentation, Issue 1 - Addfiles
No ratings yet
OpenScape 4000 Assistant V11, HG3550 Manager and STMI - NCUI Manager, Administrator Documentation, Issue 1 - Addfiles
14 pages
OpenScape 4000 V7, Security Checklist For OpenScape 4000 V7 and Affiliated Products, Planning Guide, PDF
No ratings yet
OpenScape 4000 V7, Security Checklist For OpenScape 4000 V7 and Affiliated Products, Planning Guide, PDF
53 pages
OpenScape 4000 V7, VHG 3500 HFA For OpenScape 4000 SoftGate, Administrator Documentation, Issue 2 PDF
No ratings yet
OpenScape 4000 V7, VHG 3500 HFA For OpenScape 4000 SoftGate, Administrator Documentation, Issue 2 PDF
56 pages
Alcatel-Lucent 300 400 Dect Manual Omnipcx Office
No ratings yet
Alcatel-Lucent 300 400 Dect Manual Omnipcx Office
63 pages
OpenScape Voice V7 - Service Manual - Installation and Upgrades - Installation Guide - Issue 16 PDF
100% (3)
OpenScape Voice V7 - Service Manual - Installation and Upgrades - Installation Guide - Issue 16 PDF
837 pages
4000 Built-In SBC
No ratings yet
4000 Built-In SBC
47 pages
OpenScape 4000 V10, Volume 4 - IP Solutions, Service Documentation, Issue 4 - Addfiles
No ratings yet
OpenScape 4000 V10, Volume 4 - IP Solutions, Service Documentation, Issue 4 - Addfiles
1,269 pages
Administration Manual OpenStage OpenScape Voice
No ratings yet
Administration Manual OpenStage OpenScape Voice
378 pages
Unify OpenScape 4000 V8 & V10 - SIP - en
No ratings yet
Unify OpenScape 4000 V8 & V10 - SIP - en
36 pages
OpenScape Voice V7, Service Manual - Installation and Upgrades, Installation Guide, Issue 25
No ratings yet
OpenScape Voice V7, Service Manual - Installation and Upgrades, Installation Guide, Issue 25
963 pages
OSCCE System Management Guide
No ratings yet
OSCCE System Management Guide
94 pages
OpenScape Branch V10
No ratings yet
OpenScape Branch V10
12 pages
Manual FSX GrandStream
No ratings yet
Manual FSX GrandStream
62 pages
OpenScape SBC V7, Installation Guide, Issue 16
100% (1)
OpenScape SBC V7, Installation Guide, Issue 16
174 pages
OpenScape 4000 V7, Volume 3 - Feature Usage Examples, Service Documentation, Issue 6.
No ratings yet
OpenScape 4000 V7, Volume 3 - Feature Usage Examples, Service Documentation, Issue 6.
2,037 pages
OpenScape 4000 V11, Enterprise Gateway, Service Documentation, Issue 5 - Addfiles
No ratings yet
OpenScape 4000 V11, Enterprise Gateway, Service Documentation, Issue 5 - Addfiles
29 pages
Automatic Route Selection (ARS) : Student Manual P. 365
No ratings yet
Automatic Route Selection (ARS) : Student Manual P. 365
2 pages
HiPath 4000 Configuration Guide
No ratings yet
HiPath 4000 Configuration Guide
10 pages
RBR-ITG-Unify OpenScape Voice Integration Guide V1.4
No ratings yet
RBR-ITG-Unify OpenScape Voice Integration Guide V1.4
28 pages
Samsung SKP308 User Guide PDF
No ratings yet
Samsung SKP308 User Guide PDF
50 pages
HiPath Xpressions Compact V3.0 Installation Administration Guide
No ratings yet
HiPath Xpressions Compact V3.0 Installation Administration Guide
194 pages
OpenScape 4000 Assistant V8 Loadware Update Manager Administrator Documentation Issue 1
100% (1)
OpenScape 4000 Assistant V8 Loadware Update Manager Administrator Documentation Issue 1
50 pages
Siemens HiPath 4000 AMO Guide
No ratings yet
Siemens HiPath 4000 AMO Guide
5 pages
Alcatel Temporis 32 User Guide
100% (2)
Alcatel Temporis 32 User Guide
25 pages
OpenScape Business V2, OpenScape Business X3 - X5 - X8, Service Documentation, Issue 5
No ratings yet
OpenScape Business V2, OpenScape Business X3 - X5 - X8, Service Documentation, Issue 5
348 pages
SV9100 SV8100 WebPro Admin Guide
No ratings yet
SV9100 SV8100 WebPro Admin Guide
3 pages
Ascom d83 DECT Handset: Configuration Manual
No ratings yet
Ascom d83 DECT Handset: Configuration Manual
80 pages
Cisco MDS 9000 Family Quick Configuration Guide: Corporate Headquarters
No ratings yet
Cisco MDS 9000 Family Quick Configuration Guide: Corporate Headquarters
52 pages
Im 8158s 8168s VoWifi System Planning 8AL90073ENAA 2 en
No ratings yet
Im 8158s 8168s VoWifi System Planning 8AL90073ENAA 2 en
27 pages
Installing MiVoice MX ONE Hardware
No ratings yet
Installing MiVoice MX ONE Hardware
17 pages
Aruba AP Comparison Sheet 2021
No ratings yet
Aruba AP Comparison Sheet 2021
3 pages
OpenScape Business V3 OpenScape Business X3X5X8 Installation Guide Issue 5
No ratings yet
OpenScape Business V3 OpenScape Business X3X5X8 Installation Guide Issue 5
283 pages
Avaya G430 PDF
No ratings yet
Avaya G430 PDF
56 pages
OV2500 NMS-E 4 2 1 R01 User Guide
No ratings yet
OV2500 NMS-E 4 2 1 R01 User Guide
418 pages
OpenScape Contact Center Enterprise V10 R3 OpenScape Contact Media Service Installation Guide Issue 5
No ratings yet
OpenScape Contact Center Enterprise V10 R3 OpenScape Contact Media Service Installation Guide Issue 5
38 pages
vg350 SCG
No ratings yet
vg350 SCG
74 pages
Elastix & DAG1000 Setup Guide
No ratings yet
Elastix & DAG1000 Setup Guide
16 pages
Vsphere Esxi Vcenter Server 50 Command Line Interface Solutions and Examples Guide
No ratings yet
Vsphere Esxi Vcenter Server 50 Command Line Interface Solutions and Examples Guide
144 pages
Os4k DTMF
No ratings yet
Os4k DTMF
8 pages
Cisco Unified SIP Phone 3905 Quick Start Guide
No ratings yet
Cisco Unified SIP Phone 3905 Quick Start Guide
1 page
OpenScape Desk Phone CP Phone Administration Guide HFA
No ratings yet
OpenScape Desk Phone CP Phone Administration Guide HFA
241 pages
OpenScape Desk Phone CP SIP Administrator Documentation, Issue 1
No ratings yet
OpenScape Desk Phone CP SIP Administrator Documentation, Issue 1
304 pages
Unify Openscape cp710
No ratings yet
Unify Openscape cp710
200 pages
OpenScape Desk Phone CP210 HFA (OpenScape 4000), User Guide, Issue 1
No ratings yet
OpenScape Desk Phone CP210 HFA (OpenScape 4000), User Guide, Issue 1
127 pages
OpenScape Desk Phone CP100 SIP, User Guide, Issue 1
No ratings yet
OpenScape Desk Phone CP100 SIP, User Guide, Issue 1
160 pages
OpenScape Desk Phone CP200 SIP, User Guide, Issue 2
No ratings yet
OpenScape Desk Phone CP200 SIP, User Guide, Issue 2
161 pages
OpenScape Desk Phone CP110 SIP User Guide
No ratings yet
OpenScape Desk Phone CP110 SIP User Guide
168 pages
OpenScape Desk Phone CP110 HFA (OpenScape 4000) User Guide
No ratings yet
OpenScape Desk Phone CP110 HFA (OpenScape 4000) User Guide
116 pages
OpenScape Desk Phone CP200 SIP, User Guide, Issue 2
No ratings yet
OpenScape Desk Phone CP200 SIP, User Guide, Issue 2
165 pages
OpenScape Desk Phone CP200 400 600 SIP, Administrator Documentation, Issue 1
No ratings yet
OpenScape Desk Phone CP200 400 600 SIP, Administrator Documentation, Issue 1
343 pages
CP2 Hfa Osb Ug en 161201
No ratings yet
CP2 Hfa Osb Ug en 161201
95 pages
CP2 Hfa Osb Ug en 161201
No ratings yet
CP2 Hfa Osb Ug en 161201
105 pages
OpenScape Desk Phone CP100200205400600600E Phone Administration HFA Version V1R4
No ratings yet
OpenScape Desk Phone CP100200205400600600E Phone Administration HFA Version V1R4
203 pages
Cominco Reff (2019)
No ratings yet
Cominco Reff (2019)
3 pages
Longchamp Trademark Infringement Case
No ratings yet
Longchamp Trademark Infringement Case
43 pages
Tsseg-Culture and Geography-Syllabus Ay 24-25
No ratings yet
Tsseg-Culture and Geography-Syllabus Ay 24-25
15 pages
11th Computer Science Lesson 14 15 Study Materials English Medium PDF
No ratings yet
11th Computer Science Lesson 14 15 Study Materials English Medium PDF
32 pages
2023-KHIHOK ING-PROCEEDING-back Analysis Pile Foundation Thailand
No ratings yet
2023-KHIHOK ING-PROCEEDING-back Analysis Pile Foundation Thailand
10 pages
Content Handbook of Energy and Economic Statistics of Indonesia 2018 Final Edition PDF
No ratings yet
Content Handbook of Energy and Economic Statistics of Indonesia 2018 Final Edition PDF
107 pages
Tractor Wheel Trends and Traction Terminology
No ratings yet
Tractor Wheel Trends and Traction Terminology
16 pages
Serato ITCH 2.2.2 User Manual
No ratings yet
Serato ITCH 2.2.2 User Manual
61 pages
Guruvayur Devaswom-Guruvayur (Official Website)
No ratings yet
Guruvayur Devaswom-Guruvayur (Official Website)
2 pages
Katharine Gibbs School (Incorporated) v. Federal Trade Commission, 612 F.2d 658, 2d Cir. (1979)
No ratings yet
Katharine Gibbs School (Incorporated) v. Federal Trade Commission, 612 F.2d 658, 2d Cir. (1979)
37 pages
Belize Registered Land Act 2020
No ratings yet
Belize Registered Land Act 2020
91 pages
Mine Rehabilitation
No ratings yet
Mine Rehabilitation
84 pages
Ergonomics Chapter 6
No ratings yet
Ergonomics Chapter 6
19 pages
Role of Human Resource Management
No ratings yet
Role of Human Resource Management
6 pages
Hazardous Waste Strategy in Romania
No ratings yet
Hazardous Waste Strategy in Romania
33 pages
F08 - Transactional Memory in Clojure and C
No ratings yet
F08 - Transactional Memory in Clojure and C
44 pages
Problems: 7.1 Through 7.4
No ratings yet
Problems: 7.1 Through 7.4
4 pages
Jotafloor PU Top Coat PDF
No ratings yet
Jotafloor PU Top Coat PDF
6 pages
Economics Notes
No ratings yet
Economics Notes
5 pages
Achievement Test EPP Grade 5
100% (1)
Achievement Test EPP Grade 5
3 pages
Smu All Courses Domestic Brochure
No ratings yet
Smu All Courses Domestic Brochure
29 pages
A Study On Consumer Preference & Satisfaction Towards Organic Shampoo in Salem City
No ratings yet
A Study On Consumer Preference & Satisfaction Towards Organic Shampoo in Salem City
2 pages
Haier l26f6 l32f6 l42f6 Chassis Rtd2674s
No ratings yet
Haier l26f6 l32f6 l42f6 Chassis Rtd2674s
67 pages
CAA v. Range
No ratings yet
CAA v. Range
26 pages
Evaluating SPCT BSBA Club Effectiveness
No ratings yet
Evaluating SPCT BSBA Club Effectiveness
53 pages
Measure of Variability
No ratings yet
Measure of Variability
32 pages
Wiseman
No ratings yet
Wiseman
3 pages
Safety Data for Chlorine Tabs
No ratings yet
Safety Data for Chlorine Tabs
7 pages