Hipath 40000 Deployment-Service V7 en
Hipath 40000 Deployment-Service V7 en
Hipath 40000 Deployment-Service V7 en
Deployment Service V7
Administration & Installation Manual
P31003-S2370-M107-28-76A9
unify.com
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bktoc.fm
For internal use only
Contents
Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Target Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Conventions Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Constraint Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 DLS and file naming schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-1
1-1
1-1
1-2
1-2
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
0-1
bktoc.fm
Contents
3-16
3-16
3-17
3-19
3-19
0-2
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bktoc.fm
For internal use only
Contents
4-46
4-48
4-49
4-59
4-59
4-59
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
0-3
bktoc.fm
Contents
0-4
6-142
6-143
6-144
6-148
6-152
6-153
6-156
6-158
6-161
6-164
6-165
6-167
6-168
6-170
6-172
6-174
6-178
6-179
6-181
6-183
6-186
6-188
6-196
6-199
6-200
6-205
6-207
6-212
6-214
6-216
6-221
6-224
6-226
6-227
6-228
6-230
6-233
6-234
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bktoc.fm
For internal use only
Contents
6-240
6-242
6-244
6-245
6-246
6-247
6-248
6-251
6-258
7 IP Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
7.1 IP Phone Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
7.1.1 Gateway/Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
7.1.2 IP Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27
7.1.3 Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-39
7.1.4 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-46
7.1.5 Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-82
7.1.6 QoS Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-93
7.1.7 Security Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-99
7.1.8 Telephony . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-124
7.1.9 Small Remote Site Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-126
7.1.10 Dialing Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-129
7.1.11 Time Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-135
7.1.12 Audio Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-139
7.1.13 SNMP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-152
7.1.14 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-156
7.1.15 LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-169
7.1.16 User Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-175
7.1.17 SIP Mobility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-189
7.1.18 HFA Mobility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-193
7.1.19 Keysets/Keylayout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-195
7.1.20 WLAN Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-214
7.1.21 Signaling and Payload Encryption (SPE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-226
7.1.22 IEEE 802.1x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-236
7.1.23 Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-249
7.1.24 Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-272
7.1.25 File Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-289
7.2 IP Client Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-293
7.2.1 CTI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-297
7.2.2 Gateway/Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-311
7.2.3 Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-335
7.2.4 Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-339
7.2.5 Telephony . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-345
7.2.6 Small Remote Site Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-348
7.2.7 Dialing Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-350
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
0-5
bktoc.fm
Contents
7-360
7-374
7-385
7-392
7-403
7-410
7-417
7-422
7-423
7-432
7-437
7-447
7-456
7-457
7-463
7-467
7-470
7-473
7-480
7-492
7-493
7-506
7-508
7-511
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bktoc.fm
For internal use only
Contents
8-147
8-155
8-158
8-160
8-164
8-168
8-170
8-172
8-176
8-179
9 Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
9.1 Gateway Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
9.1.1 "Gateway Connection" Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
9.2 QoS Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8
9.2.1 "Server Data" Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
9.2.2 "Report Settings" Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14
9.2.3 "Threshold Values" Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16
10 Software Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
10.1 Workpoint Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
10.1.1 "Software Deployment" Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7
10.1.2 "File Deployment" Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
10.1.3 "Software Inventory" Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11
10.1.4 "LDAP Inventory" Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12
10.1.5 "MOH Inventory" Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13
10.1.6 "INCA Inventory" Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-14
10.1.7 "Java Midlet Inventory" Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-15
10.1.8 "Logo File Inventory" Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16
10.1.9 "SYSTEM/RINGTONE Inventory" Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17
10.1.10 "APM Inventory" Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-18
10.1.11 "NETBOOT Inventory" Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19
10.2 Manage Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-20
11 Element Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
11.1 Element Manager Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
11.1.1 "OpenScape Voice" Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9
11.1.2 "OpenScape Voice Assistant" Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-14
11.1.3 "HiPath 4000 Assistant" Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-17
11.1.4 "HiPath 3000/5000" Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-20
11.1.5 "Protocol" Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-21
11.2 Element Manager Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-23
12 Profile Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
12.1 Device Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
12.1.1 "Templates" Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
0-7
bktoc.fm
Contents
0-8
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bktoc.fm
For internal use only
Contents
0-9
bktoc.fm
Contents
16.7 Replacing an Old Workpoint (TDM) with a New One (IP) . . . . . . . . . . . . . . . . . . . . 16-30
16.8 Replacing HFA with SIP Software and Vice Versa with Identical Device IDs . . . . . 16-31
16.8.1 Replacing HFA with SIP Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-31
16.8.2 Replacing SIP with HFA Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-32
16.9 Configuring an IP Client 130 in the DLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-33
16.9.1 Creating Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-33
16.9.2 Creating a Profile from the Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-34
16.9.3 Settings at the optiClient 130 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-34
16.9.4 OptiClient in Call Centers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-36
16.10 Changing the IP Address and/or Port Number of the DLS . . . . . . . . . . . . . . . . . . 16-37
16.11 Using an EWS with DLS in a Customer Network Without Permanent DLS . . . . . 16-38
16.11.1 Installation and Initial Configuration of DLS on the EWS . . . . . . . . . . . . . . . . 16-38
16.11.2 Manipulating the DLS Database for Using the TAP at Different Customer Facilities
16-39
16.12 Operating the DLS via the Program Interface (DlsAPI). . . . . . . . . . . . . . . . . . . . . 16-40
16.12.1 DLS API Web Service Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-40
16.13 Security: Administering Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-42
16.13.1 Importing WBM Server Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-43
16.13.2 Importing Phone and RADIUS Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . 16-44
16.13.3 Importing SPE CA Certificates for IP Phones. . . . . . . . . . . . . . . . . . . . . . . . . 16-46
16.13.4 Importing SPE CA Certificates for IP Clients . . . . . . . . . . . . . . . . . . . . . . . . . 16-48
16.13.5 Importing SPE Certificates and SPE CA Certificates for IP Gateways. . . . . . 16-49
16.13.6 Remove Certificate (IEEE 802.1x Phone as an example) . . . . . . . . . . . . . . . 16-51
16.13.7 Replace IP Phone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-52
16.14 Configuring and Administrating Mobility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-53
16.14.1 Configuring the Mobility Function on the Device . . . . . . . . . . . . . . . . . . . . . . 16-53
16.14.2 Programming the "Mobility" Button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-53
16.14.3 Creating a Mobile User Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-54
16.14.4 Creating Mobile Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-54
16.14.5 Create a Home Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-56
16.14.6 Logging On Mobile Users (Forced Logon) . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-57
16.14.7 Logging Off Mobile Users (Forced Logoff) . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-57
16.14.8 Troubleshooting for Mobile User Logon/Logoff . . . . . . . . . . . . . . . . . . . . . . . 16-57
16.14.9 Default Setting for the Key Layout in Mobility Telephones . . . . . . . . . . . . . . . 16-58
16.14.10 Data Backup to a .zip Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-60
16.14.11 Import Mobile User Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-65
16.14.12 Mobility between optiPoint and OpenStage . . . . . . . . . . . . . . . . . . . . . . . . . 16-67
16.15 HFA Mobility with HiPath 3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-68
16.15.1 HiPath 3000 Configuration Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-68
16.15.2 DLS Configuration for Network-wide HFA Mobility. . . . . . . . . . . . . . . . . . . . . 16-68
16.15.3 Operating procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-68
16.16 Data Structures for DLS-hosted XML applications . . . . . . . . . . . . . . . . . . . . . . . . 16-70
16.16.1 Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-70
16.16.2 Directories at Upgrade Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-70
0-10
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bktoc.fm
For internal use only
Contents
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
0-11
bktoc.fm
Contents
0-12
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
einleitung.fm
For internal use only
Introduction
Target Group
1 Introduction
The document describes the OpenScape OpenScape Deployment Service V7 (DLS) client in version V7 R2 (HIDLS7.2xx) and contains information about initial DLS server configuration.
This manual is also available as online help on the DLS clients interface, see Section 5.3, "Opening the ContextSensitive Help Function".
NOTE: For a quick start guide, please read the same-titled Chapter 2.
Example
courier
Italics
Variable
Example: Name can be up to eight characters long
Bold
Bold
Special emphasis
Example: You are not permitted to delete this name
Element
<Courier>
Key combinations
Example: <CTRL>+<ALT>+<ESC>
>
Menu sequence
Example: File > End
NOTE :
Additional information
IMPORTANT :
Table 1
Typographic conventions
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
1-1
einleitung.fm
Introduction
Constraint Notes
Try as much as possible to use the following naming schemes for your files:
A dash - or underscore _ may be allowed by some applications but characters such as: ( ) { } @ # $ %
^ & ! ' / ~ have special meaning and should not be used.
Keep filenames all lowercase, no CAPITAL letters (some applications may allow caps).
Use lowercase even when it is grammatically incorrect.
Never use spaces in a filename or its extension. They are extremely troublesome.
1-2
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
einleitung.fm
For internal use only
Introduction
DLS and file naming schemes
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
1-3
einleitung.fm
Introduction
1-4
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
gettingstarted.fm
For internal use only
Getting Started
2 Getting Started
This brief guide should enable administrators to quickly start the OpenScape Deployment Service V7, perform
basic configuration, and connect new telephones, without detailed background knowledge.
NOTE: In order to keep this chapter as short as possible, we have intentionally left the following information out:
- Various application scenarios
Here only one standard scenario is provided as an example.
- Parameter descriptions
Here we will only explain what you need to do, not why.
- Background information
Only the most important information is summarized here.
Detailed information is provided in the rest of the manual, in particular in the chapters:
- Chapter 3: Concept and feature overview
- Chapter 4: Installation of the DLS and additional software components
- Chapter 5: General information about the user interface
- Chapter 6 to Chapter 14: Information on individual parameters
- Chapter 15 and Chapter 16: Practical examples with process descriptions.
The following processes are described here:
Section 2.2, "Starting the DLS for the First Time (Single Mode)"
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
2-1
gettingstarted.fm
Getting Started
DLS Installation
JRE 1.7 (Client); Browser: Any browser that supports Java plug-in, e.g. Internet Explorer, Firefox, Chrome,
Opera, Safari
NOTE: Internet Explorer has to get 512 MB in case of large networks,with an additional 1024
MB for the heap size of JRE.
Please allow adequate RAM available for the Operating System and the remaining applications
in use.
1. In the Windows Start menu, open Start > Settings > Control Panel & select the Java icon.
2. In the Java Control Panel window, select the Java tab, click on the View button. Select your
primary (or only) Java environment from the list and double-click in the cell labeled "Runtime
Parameters."
3. Enter the initial and maximum heap sizes as necessary, using the parameters used in the
first section above. Set a maximum heap size of 1024MB, fill in the box with the following:
-Xmx1024m
4. Click OK to close the runtime environments window, and once again to close the Java
control panel.
NOTE: It is also recommended that you configure the following in case the cache is full:
1. In the Windows Start menu, open Start > Settings > Control Panel & select the Java icon.
2. In the Java Control Panel window, select the General tab, click on the Settings button
under Temporary Internet Files.
3. Disable the Keep temporary files on my computer checkbox.
2-2
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
gettingstarted.fm
For internal use only
Getting Started
DLS Installation
CPU
RAM
8 GB
Ethernet
Disk Space
80 GB
CPU
RAM
8 GB
Ethernet
Disk Space
300 GB
CPU
RAM
8 GB
Ethernet
Disk Space
80 GB
CPU
RAM
2 GB
Ethernet
Disk Space
20 GB
Database Requirements
Microsoft SQL Server 2008 Enterprise Edition can be used, but requires 4 GB. This database must be
provided by the customer.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
2-3
gettingstarted.fm
Getting Started
DLS Installation
Since V6R1, DLS supports Microsoft SQL Server 2008 R2 Datacenter Edition
NOTE: For usage of Microsoft SQL 2008 R2 Enterprise or Datacenter Edition, appropriate Microsoft
licences are needed. As a rule CPU licenses should be used, usage of device CAL (Client Access
License) is possible as well where one device CAL is needed for each supported device.
The provision of hardware and Microsoft licenses is not part of the DLS order items and need to be
considered separately.
All servers (DLS, Witness, Mirror) must be installed with Windows 2008 R2 / 2012(64-bit) Standard,
Enterprise or Datacenter Edition
SUSE Linux Enterprise Edition (Only for the Integrated Simplex Deployment)
NOTE: Make sure that the free disk space requirements are met prior to any upgrade installations.
IMPORTANT: In Multi-Node installations, Network Interface card drivers for the virtual IP address of
NLB should support dymanic changes of MAC address, therefore must support Unicast.
When you use the Unicast method, all cluster hosts share an identical unicast MAC address. Network
Load Balancing overwrites the original MAC address of the cluster adapter with the unicast MAC
address that is assigned to all the cluster hosts.
For further information, please refer to Section 4.3, "Configure the Network Load Balancer".
2-4
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
gettingstarted.fm
For internal use only
Getting Started
DLS Installation
Scenario
Max.number of :
Maximum
Total Number
(devices &
mobile users)
Generic scenario
for the
OpenScape
Deployment
Service
Devices
100,000
200,000
Mobile Users
100,000
The following tables show the recommended maximum number of devices that can be controlled by a Single Node
DLS :
Scenario
Max.number of :
Maximum
HFA only
HFA Devices
50,000
SIP only
SIP Devices
40,000
DLS Mobility
Mobile Users
20,000
DLS Mobility
20,000
DlsAPI
DlsAPI Sessions
100
100
Scenario
Max.number of :
Maximum
HFA only
HFA Devices +
SIP Devices
+Mobile Users
200,000
DLS Mobility
20,000
DlsAPI
DlsAPI Sessions
100
SIP only
DLS Mobility
100
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
2-5
gettingstarted.fm
Getting Started
DLS Installation
If used with Microsoft SQL Server 2008 R2 Enterprise or DataCenter Edition in a Multi-Node Deployment with
two DLS nodes including synchronous database mirroring and automatic failover (Redundancy Scenario)
Scenario
Number of
Maximum
Number of Nodes : 2
DLS Mobility
20,000
Number of Nodes : 3
DLS Mobility
22,000
Number of Nodes : 4
DLS Mobility
24,000
NOTE: Uniform request arrivals within the 1 hour time window is assumed.
For instance, 20000 /hour is equivalent to 330/min or even 5.5/sec.
NOTE: In the case of Multi-Node environments, actual system capacities may differ dependent on
the server hardware. Higher figures might be possible with higher hardware performance.
The following table illustrates the Maximum Log-on Request rate for DLS Deployments:
2-6
Deployment
Logon
requests/sec
Single Node DLS with remote Microsoft SQL Server 2008 R2 Enterprise or DataCenter
5.5
6.5
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
gettingstarted.fm
For internal use only
Getting Started
DLS Installation
2.1.3 Licensing
For configuring base software, basic devices, mobile users, and PKI users, using DLS-Nodes in a cluster,
database mirroring, the XML push functionality, or the location service (IP infrastructure), licenses must be
purchased. All further DLS functions are free of cost.
You can use HiPath License Management to load the relevant licenses for this onto the license agent. The license
agent can be specified when you install the DLS or later under Administration > Server Licenses.
The license agent and HiPath License Management are available for download on C-SWS.
Demo licenses are available for test installations and include:
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
2-7
gettingstarted.fm
Getting Started
DLS Installation
Re-assigning Licenses
In the case of re-assigning licenses to DLS (another DLS or the same DLS on another/previous snapshot) the
following instructions should take place :
1. Activate the same (.lic) license file on CLA you own.
2. Restart CLA service (On windows, you can use service manager)
3. On CLM synchronize with CLA
4. Restart DLS to contact CLA and load the available/required licenses (or wait for DLS to contact CLA - which
happens approximately every 4 hours).
2-8
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
gettingstarted.fm
For internal use only
Getting Started
Starting the DLS for the First Time (Single Mode)
2.2 Starting the DLS for the First Time (Single Mode)
1. Starting the program
To start the DLS client, use the following URL syntax :
NOTE: For Integrated Simplex, when generating a Device Management connection, the connection
port for Internal DLS is 443 and NOT 10443.
If the client is on the same (Windows) machine as DLS server:
http://localhost:18080/DeploymentService/
(default)
NOTE: <DLS Server IP> is the IP of the Windows server. For MultiNode configurations this is the
virtual IP address in the cluster setup of the MultiNode configuration.
IPv6 requires either brackets, e.g. http://[2000.1..100]:18080/DeploymentService/
or as it is strongly reccomended,the use of Host Names,DNS names,e.g.
http://MyDlsServer:18080/DeploymentService/
or
http://MyDlsServer.myDomain.com:18080/DeploymentService/
NOTE: DLS Security checklist recommends using secure access methods.
2. Logging on
Log on under the "admin" account with the password set during installation.
The default credentials for logging on to DLS are as follows:
Account : admin
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
2-9
gettingstarted.fm
Getting Started
Password : Asd123!.
NOTE: Notice the capital 'A' since passwords are case sensitive.
3. Modifying passwords/configuring accounts
You must create a separate account in the DLS for each DLS administrator. This is only possible with the
default "admin" account. To do this, select Administration > Account Management in the menu bar. Click
Search. If you switch to Table view, information is provided on all user IDs in a table overview. You can create
a new account with New.
4. Location configuration
You can use the location criterion to define groups for terminals that share the same range of IP addresses
and/or are connected to certain systems. Proceed as follows for basic configuration of the location:
Define the IP address range for the location in Administration > Server Configuration > Location > "IP
Ranges" Tab.
Enter the IP addresses or host names of the systems (PBX/gateway or SIP server) for the location in
Administration > Server Configuration > Location > "Reg-Addresses" Tab.
Additional configuration options are provided under Administration > Server Configuration > Location.
If you do not define a location, the "Default Location" is assigned for all location-specific parameters.
2-10
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
gettingstarted.fm
For internal use only
Getting Started
Starting the DLS for the First Time (Single Mode)
5. FTP configuration
To load IP phone software and other files to the devices, you will need an FTP server that provides the
software images. The DLS supports the configuration and use of unlimited numbers of FTP servers. To enter
the access data for an FTP server, go to Administration > Server Configuration > Configure FTP Server.
Click the action button New to create a new FTP server.
In the Server ID field, enter a name for the FTP server you wish to use to transfer IP phone software.
In the Hostname field, enter the network name or the IP address of the FTP server.
In the field SW Image Path, the path to the directory containing the software image files is specified. This path
is relative to the root directory of the FTP user ID used by the DLS. If the image files are contained directly in
the root directory, enter "./" as your path.
In the User field, enter the user ID that the DLS should use to log on to the FTP server. In the Password field,
enter the corresponding password.
You can use Test to check if the settings are correct using an FTP connection test. Apply your entries by
clicking Save.
You can find a description of all fields and additional information in Section 6.3.4, "FTP Server Configuration".
6. HTTPS configuration (for OpenStage terminals)
OpenStage phones can alternatively use an HTTPS server for downloading files.
In the HTTPS Server ID field, enter a name for the HTTPS server you wish to use to transfer files.
In the HTTPS Server URL field, enter the network name or the IP address of the HTTPS server.
You can find a description of all fields and additional information in Section 6.3.5, "HTTPS Server
Configuration".
7. Plug & Play/Autoconfiguration
DLS provides an option for preconfiguring IP devices to go into operation as soon as they are connected to
the network. To do this, the DLS transfers the necessary configuration parameters to the IP device. In the case
of IP Devices (IP phones, IP clients, IP Gateways), these parameters include, in particular, phone-numberdependent data for registration at the telephone system. The DLS must receive the system access data before
it can incorporate the necessary data from the telephone system in the DLS database. Enter this under
Element Manager > Element Manager Configuration.
Using profiles, you can create standard configurations for multiple devices. Device profiles are created from
templates composed of a collection of settings from individual masks plus information about the devices,
gatekeepers, and IP ranges supported by each profile. To perform configuration, select Profile Management
> Device Profile.
If you want to create individual parameters for a particular device, you can create what is known as a virtual
device. To do this, go to IP Device Management > IP Device Configuration and click New. The virtual device
is assigned a placeholder beginning with "@" instead of the device ID and the IP address and E.164 number
are set to 0. To assign a physical device, enter either an E.164 number or a real device ID (generally, the MAC
address). The
icon beside the Device Type field indicates that the IP device is not yet registered at the
DLS. Otherwise, configuration is the same as for a connected, registered device.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
2-11
gettingstarted.fm
Getting Started
NOTE: DLS records a device on the basis of the device ID/E.164 number value pair. In all
configuration masks, this information is provided in the upper half of the user interface. Make
sure that the data displayed here refers to the IP device you wish to configure so that the configuration data can be assigned to the correct IP device.
2-12
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
gettingstarted.fm
For internal use only
Getting Started
Required Workpoint Firmware Installation
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
2-13
gettingstarted.fm
Getting Started
3. As the key function Mobility is on the first level, select "1st Level " in the Level column.
4. In the Key number column, select the key to which the new function should be assigned. For more
information, see Section 7.1.19.2, ""Destinations" Tab".
5. Select "Mobility" in the Key function column.
6. You can now enter a key label in the final column. This is only displayed with optiPoint 420 telephones that
provide automatic key labeling.
Complete the action by pressing Save.
2-14
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
gettingstarted.fm
For internal use only
Getting Started
Using the Mobility Function
2.4.3 Jobs
All actions that can be performed on IP Devices using DLS, such as, configuring the key layout, are managed by
the DLS as jobs.
Using job control, you can view information on individual jobs, and cancel, delete or reactivate jobs. To do so, go
to Job Coordination > Job Control.
Essentially jobs can be started either immediately or later at a specific, predefined time. For example, in order to
perform the actions described in Section 2.4.2, "Configuring Parameters: Example Key Layout" at a specific time,
perform all the steps described except the final Save action. Then, in the top right field Job ID, enter an arbitrary
job ID and click the
icon beside the field Execution Time to define when the action should be executed. Once
this has been completed, activate the job with Save.
For further information on job coordination, see Section 14, "Job Coordination".
2-15
gettingstarted.fm
Getting Started
2-16
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
gettingstarted.fm
For internal use only
Getting Started
Security
2.6 Security
2.6.1 Certificates
Certificates enable secure authentication between servers and clients. They can be implemented for the following
server-client scenarios:
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
2-17
gettingstarted.fm
Getting Started
Security
2-18
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
konzept.fm
For internal use only
NOTE: We recommend that you use a DHCP server in the DLS environment to
Setting up the DHCP server should be one of the first tasks you perform, if possible, even before you
install the workpoints.
Only one DLS server is allowed per DHCP domain at the customer facility.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
3-1
konzept.fm
Concept and Features
Web application
Deployment Service
Client
application
Web server
Tomcat
Server
applications
Database
MS SQL server
Service
DeploymentService
The client applications can be executed both on a client PC that can be reached in the IP network and on the
server PC itself.
NOTE: When server and client are being used separately, ensure that the operating system times
are synchronized.
3-2
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
konzept.fm
For internal use only
scanning the IP Devices with DLS, see Section 7.4.6, "Scan IP Devices"
(recommended if there are already a number of IP Devices operating after the initial DLS startup)
or by
All actions performed with the DLS, for example, an IP Device software update or a modification of the
configuration data, are logged in the DLS.
Job coordination helps you in this process. This allows you to see the status of each action and to determine the
cause if there is an error. For more information, see Section 14, "Job Coordination".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
3-3
konzept.fm
Concept and Features
Area of Application
IP Device
HFA Version
SIP Version
AC-Win 2Q IP
all versions
all versions
AC-Win MQ IP
all versions
all versions
all versions
all versions
from V1.0
from V1.0
HP2K V2.0
from V2.0
from V2.0
optiClient 130
V2.0
all versions
all versions
all versions
V1.0 (50/70)
V1.0 (50)
OpenStage 5
all versions
all versions
OpenStage 15
all versions
all versions
OpenStage 20E
all versions
all versions
OpenStage 20
all versions
all versions
OpenStage 40
all versions
all versions
OpenStage 60
all versions
all versions
HG1500
HG3500
HG3575
Table 2
3-4
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
konzept.fm
For internal use only
IP Device
HFA Version
SIP Version
OpenStage 80
all versions
all versions
all versions
V3R3
V3R3
Wave Evolution Lo
V3R3
all versions
V3R3
Table 2
NOTE: On the following device types, the mobility function is available in SIP V6.0 or later: optiPoint
410 economy, optiPoint 410 economy plus, optiPoint 410 standard, optiPoint 410 advance, optiPoint
420 economy, optiPoint 420 economy plus, optiPoint 420 standard, optiPoint 420 advance.
On the following device types, the mobility function is available in all versions: OpenStage 20E, OpenStage 20,
OpenStage 40, OpenStage 60, OpenStage 80.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
3-5
konzept.fm
Concept and Features
Area of Application
Administration is possible for various communication platforms. Both HiPath and non-HiPath platforms are
supported:
Platform
P&P
connection
Plug&Pl QDC
ay
connection
QDC
SRTP
connection
SRTP
OpenOffice EE V1.0
standalone
no
no
no
no
no
standalone
no
no
no
no
no
standalone
no
no
no
no
no
HG1500
yes
HG1500
yes
no
no
HG1500
yes
HG1500
yes
HG1500
yes
HG1500
yes
HG1500
yes
HG1500
yes
Assistant
yes
no
no
no
no
Assistant
yes
HG3530/50/70/
75
yes
no
no
Assistant
yes
HG3530/50/70/
75
yes
HG3530/50
yes
Assistant
yes
HG3500/75
yes
HG3500/75
yes
Assistant
yes
HG3500/75
yes
HG3500/75
yes
HiPath 4000
V61
no
no
no
no
Assistant
yes
no
no
no
no
no
no
no
no
Assistant
yes
no
no
no
no
Assistant
yes
no
no
no
no
HiPath DX V9
DX WebPro
yes
no
no
no
no
not relevant
no
RG2700
yes
no
no
Table 3
1 Parameter settings for HiPath 4000 are also valid for HiPath 4000 V6, except as noted otherwise.
NOTE: If SIP IP phones are connected to the platforms HiPath 3000 and HiPath 4000, some
features are not available. Please deactivate these at the IP Device, so that they are not visible resp.
selectable by the user.
3-6
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
konzept.fm
For internal use only
Object type
(name in the
DLS)
File extension
NOTE: The administrator can define the extensions as desired in the file_map.xml file found
under
DeploymentService\Tomcat5\webapps\DeploymentService\
WEB-INF\classes.
To return to the standard configuration copy and rename default_file_map.xml to
file_map.xml.
Example
Contents
opera_bind.img
OpenStage firmware
Software objects
Software image *.img
setup.exe
PC software installation
Firmware
(Netboot)
vxWorks.fli
netboot308.fli
Netboot firmware
*.fli
File objects
LDAP
Template
*.ldap ldap_temp.ldap
*.txt
ldap_temp.txt
Table 4
*.wav music.wav
*.mp3 music.mp3
*.mid
music.mid
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
3-7
konzept.fm
Concept and Features
Screen Saver2
*.jpg
screenPic1.jpg
*.png screenPic1.png
INCA
Firmware
*.h86 inca.h86
JAVA Midlet
*.jad
Java application
Java archive
*.jar
Logo file2
*.jpg
*.png
System and
Ringtone1
-
*.xml
*.wav ?
*.mp3 ?
*.mid
*.app bootrom.app
New/other applications
DSM firmware
*.csv
Dongle Keys
*.key
dongle.key
Table 4
3-8
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
konzept.fm
For internal use only
In the case of LDAP,an LDAP template is deployed to the phone in order for the phone to have access to a
Corporate Directory. The template file is a simple and short list of attributes in the form of a text file.This file is
employed by the phone in order to communicate with an LDAP server (usually located in DNS) and make a
directory query (for example search for a company contact and find its telephone number).The template serves
as a mapping between the phones and the LDAP servers items. The attributes contained in the template depend
on the phone Corporate Directory menu items and the type of the LDAP (e.g. Microsoft 2008 R2 LDAP).
Please refer to the following example template of a Microsoft 2008 R2 LDAP server for OpenStages & DPIPs.
It shall provide useful info not to mention the time saving process each time an LDAP Corporate directory is set
up for the fisrt time:
OpenStage LDAP TEMPLATE (v.1)
SEARCHBASE="CN=Users,DC=opera,DC=local"
ATTRIB01="sn"
ATTRIB02="givenName"
ATTRIB03="telephoneNumber"
ATTRIB04="otherTelephone"
ATTRIB05="mobile"
ATTRIB06="homePhone"
ATTRIB07="company"
ATTRIB08="department"
ATTRIB09="l"
ATTRIB10="title"
ATTRIB11="mail"
EOF
NOTE: The correct SEARCHBASE should be entered by the admin for each LDAP directory. It can
be seen as a tree where the contact will be searched in the directory. The left column of numbered
attributes depend on the phone menu. Their equivalents (the right column) depend on the type of the
LDAP server.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
3-9
konzept.fm
Concept and Features
PSS generation and distribution within an SRTP security domain (password identification).
Secure mode can be configured for mutual authentication between the workpoint and the DLS.
Area: IP Devices > IP Device Management > IP Device Configuration > "DLS Connectivity" Tab.
Minimum password length specification for user, administration, and screenlock passwords as well as for the
SNMP community string.
Area: IP Devices > IP Phone Configuration > Security Settings > "Passwords" Tab.
3-10
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
konzept.fm
For internal use only
Software deployment:
DLS is a user-friendly tool for upgrading software on all workpoints available or on a definable number of
workpoints.
For more information, see Section 10, "Software Deployment".
Inventory data management:
The DLS is the central inventory data manager. Inventory data describes the hardware configuration and capacity
of the workpoint and includes information on items, such as, add-on devices or adapters available.
Inventory data can be exported over the CSV interface.
Plug&Play function:
The DLS supports Plug&Play. Plug&Play means that the IP phone is ready to work as soon as it is plugged into
the network - no user intervention required. Ideally, the workpoint automatically downloads all necessary software
and configuration data and can be used after a few minutes.
For more information, see Section 15.6, "Workpoint Autoconfiguration (Plug&Play)".
User interface:
The DLS has a Java-supported, Web-based user interface, and runs on an Internet browser.
Configuration Management:
Configuration Management is the DLSs central tool for displaying and administering workpoint parameters in a
HiPath environment. It can be operated either at the customer facility or by Service (via remote administration).
Workpoints can also be restarted with the Reset function.
Additional functions:
The following basic functions are supported:
Import/Export:
This function is particularly useful during the initial configuration of the DLS, and can also be used in later
operation for backing up configuration data.
The Import/Export function is a user-friendly tool for transmitting a DLS configuration from one DLS installation
to another.
Access protection:
Access to the DLS is password-protected.
Support for the configuration of QDC features for HG3550 V2.0, HG1500, RG2700, and HiPath HG3530/70/
75 (over SNMP proxy).
The SNMP proxy is installed together with the DLS during startup and start automatically (runs as a local
"DeploymentServiceSNMPProxy" service).
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
3-11
konzept.fm
Concept and Features
You can only use the plug&play functionality in DLS if there is a DHCP/DNS infrastructure in the network and
this has been configured for working with the DLS (see Section 15.6, "Workpoint Autoconfiguration
(Plug&Play)").
You can only install one DLS per domain in the network.
3-12
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
konzept.fm
For internal use only
Database1
DLS deployments
DCMP service can optionally be installed as part of the DLS Server or in a seperate server
DCMP service can optionally be installed as part of the DLS Server or in a seperate server
DCMP service can optionally be installed as part of the DLS Server or in a seperate server
DLS Service included as a component in the OpenScape Voice Entry Server
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
3-13
konzept.fm
Concept and Features
For additional information on operation, refer to Section 16.14, "Configuring and Administrating Mobility".
Definition
Mobility Function
This function enables Mobile Users to log on to a Mobility Phone and operate it with their
personal settings.
Mobility Phone
A phone that supports the Mobility Function. In other words, Mobile Users can log on to this
kind of phone and operate it with their personal settings.
Mobility ID
Phone number of the Mobile User. The Mobility ID and password are used for authentication
when logging on to a Mobility Phone.
Basic User
Phone number and user data of a Mobility Phone if there are no mobile users logged on.
Mobile User
A user who can log on to a random Mobility Phone and operate it with his or her personal
settings.
This is a configurable user data (sub)set, depending on the scope of the associated templates.
The parameters are not device-specific.
Device Profile
Table 6
3-14
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
konzept.fm
For internal use only
To use this function, just press the "Mobility" function key on a Mobility Phone (or use the corresponding telephone
menu), and log on as a Mobile User with your call number (Mobility ID) and user password.
After logging on, Mobile Users can make and receive calls via Mobility Phones and can always be reached at their
personal number. Outgoing calls are also made using these numbers.
Mobile Users can log off a phone either locally at the phone or remotely via Web-based Management (WBM) or
DLS ("forced logoff").
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
3-15
konzept.fm
Concept and Features
3.8.3 Mobility ID
These two call numbers are displayed as E.164 and Basic E.164 in the area IP Devices > IP Phone
Configuration in the DLS client.
E.164 is the Mobile Users call number (Mobility ID) and Basic E.164 is the Mobility Phone call number when no
Mobile Users are currently logged on.
The smiley to the right of the E.164 field indicates that a Mobile User is currently logged on.
For more information on configuring the Mobility Function for SIP IP phones, see Section 16.14, "Configuring and
Administrating Mobility".
3-16
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
konzept.fm
For internal use only
Definition
Standard Profiles
Profiles generated under Main Menu > Administration > Server Configuration >
P&P Settings > "Standard Profile" Tab
This refers to a Profile that points to a Location that has been configured under
Administration > Server Configuration > Location as a Parent one.
This refers to a Profile that points to a Location that has been configured under
Administration > Server Configuration > Location to be a Child Location.
IP Device Configuration
Profile
Profile
Definition
IP address
Device Profile
Layout
The Mobile User should be able to use a telephones key layout with any
Mobility Phone. This makes it part of the User Data Profile.
QoS parameters
Device Profile
Language
Table 7
A User Data Profile can be either a Basic Profile or a Mobile Profile, Section 3.8.5.2, "Parameter Configuration
Availability".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
3-17
konzept.fm
Concept and Features
Parameters under:
IP Phone Configuration
Parameters under:
SIP Mobile User Configuration
No Mobility Phone
Not available
Mobility Phone,
Mobile User is not logged on
Mobility Phone,
Mobile User is logged on
Table 8
Please note the different parameter displays in the IP Phone Configuration and SIP Mobile User Configuration
areas:
In the IP Phone Configuration area, a single object (displayed in Object view or as a row in Table view)
always corresponds to a physical SIP IP phone (mobility-enabled or standard).
In the SIP Mobile User Configuration area, two different object types exist:
3-18
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
konzept.fm
For internal use only
patching
hardware repair
This tool eliminates the need to manually perform the system interrogation required to verify system health, which
reduces human error and escalations. As a result, maintenance activities are reduced and potential service
impacts (outages) can be avoided.
In the case of an existing problem with the DLS service, RapidStat can help in two ways:
Provide the support team with valuable information about the system and help identify possible causes
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
3-19
konzept.fm
Concept and Features
Hardware Information
CPU type
Total Memory
Paged memory
Storage
Physical disks
Total space
Used space
Network interfaces
Operating system
Java version
Antivirus check
Check for the presence of an Antivirus software.If an Antivirus exists, DLS RapidStat displays the product
name of the software.
3-20
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
konzept.fm
For internal use only
Installation
Version
Deployment type
Single-Node
Multi-Node
Custom Database
Service Status
Service Registration
Running / stopped
Check & Report of any services that are not needed or cannot be identified. Report with a warning if
unexpected processes are found running
Process check
Check & Report of any processes that are not needed or cannot be identified. Report with a warning
if unexpected processes are found running
Database status
Running / stopped
Connection to Database
Availability of DlsDB
If RapidStat runs as part of a DLS upgrade (during installer startup) , check if the upgrade that is about to
happen can proceed (upgrade path check) & verify if all migration scripts are available.
SNMP Proxy
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
3-21
konzept.fm
Concept and Features
3-22
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
konzept.fm
For internal use only
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
3-23
konzept.fm
Concept and Features
3-24
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
Single node operation with local database: DLS server and DLS database are located on the same
machine.
Single node operation with remote database: The DLS database is located on another machine.
Multi node operation (cluster): The DLS server is running in a distributed way on multiple machines. The
DLS database is hosted on another machine or on one of the DLS node machines.
In addition, if a remote database is used, database mirroring is possible (mode for enhanced data security / high
availability). Mirroring can be carried out in a synchronous manner, that is, main database and mirror database
are refreshed simultaneously, or in an asynchronous manner. With asynchronous mirroring, the mirror database
is updated after the transaction on the main database has occured.
The following chapters are arranged in order of their relevance for a particular DLS installation variant.
Variant
Chapter
4.1 Requirements
4.1.1 General Server Requirements
For information on the hardware needed, see Section 2.1.1, "System Requirements".
The DLS server runs on the German or English version of one of the following operating systems:
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
4-1
instadminserver.fm
Installation and Initial Configuration
Requirements
NOTE: In order to avoid high CPU usage issues,proceed with the following :
1. Click on Control Panel > Power Options> Change Advance Power Settings.
2. Switch to High Performance".
This is applicable only to 64-bit Operating System variants post Windows 2008.
The DLS client runs as Java applet in a web browser. Required are:
Java PlugIn
Any browser that supports Java plug-in, e.g. Internet Explorer, Firefox,Chrome, Opera, Safari
NOTE: If a 64-bit browser is installed in the client then a 64-bit JRE should be also installed.
Screen resolution: at least 1024 768 pixels with at least 16-bit color depth.
4-2
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
Sound knowledge of the IP Devices supported by the DLS (see Section 3.4).
For multi node (cluster): sound knowledge of Microsoft operating systems and MS SQL Server 2008/2008 R2/
2012.
Sound knowledge of the IP Devices supported by the DLS (see Section 3.4).
Basic knowledge of LAN technology, IP networks, and the operating systems supported.
For multi node (cluster): sound knowledge of Microsoft operating systems and MS SQL Server 2008/2008 R2/
2012.
For DLS installation at the customer facility (for example, HiPath SPA Server), the software can be acquired
from BE1 using RCC.
In the international market, you can also use the BE1 for installation on the service laptop.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
4-3
instadminserver.fm
Installation and Initial Configuration
Requirements
NOTE: The network cards for SQL communication (internal network) at each node should not have
a default gateway configured.
The DLS database operates as a remote database on one or more machines, depending on whether database
mirroring is desired or not. However, the DLS will connect to only one machine. It is also possible to operate both
DLS server and database server on one and the same machine.
4-4
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
4-5
instadminserver.fm
Installation and Initial Configuration
4-6
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
Install DCMP
Configure DCMP
Test DCMP
4-7
instadminserver.fm
Installation and Initial Configuration
Set Up DCMP
During the installation, you will be asked for the password for the DCMP.
4-8
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
2. Proceed with a fake DLS upgrade over Node 2,3 and 4 in order for the updated installation configuration
file located over Node 1 gets acknowledged and as such DCMP is transparently installed over the remaining
nodes.
NOTE: You have to re-run the installer on the second (or further) node(s) for DCMP to be installed,
since the installer of the remaining nodes will have to trigger the updated installation configuration file
in the common data of the environment (which is resident on the first node), and as such transparently
install DCMP over the remaining nodes.
3. Navigate to http://<IP Address>:18080/dcmp to login at the DCMP server. Proceed with the DCMP
clustering configuration if required (see Section 4.4.2, "Configure DCMP"), and connect to the DCMP via the
virtual IP address of the DLS clustering. Proceed with the DCMP clustering configuration if required (and of
course within the DLS UI accordingly).
When the DCMP server is ready, DLS can be configured for DCMP operation.
4. In Administration > Workpoint Interface Configuration > "DCMP" Tab, click the Toggle DCMP button to
activate the DCMP. A message is displayed that the DCMP server contact is successful. (see Section 4.4.3,
"Configure DLS for DCMP")
5. To verify that the job is running, look in Job Coordination > Job Control and click on the Search button. Then
click on the specific entry and select the "Object" view. In the "Basic Data" Tab you can see that the job will
be handled via DCMP.
6. Navigate to IP Devices > IP Device Management > IP Device Configuration > "DCMP" Tab. The DCMP
active switch should be checked, and the settings should be as set for this IP address in Administration >
Workpoint Interface Configuration > "DCMP" Tab.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
4-9
instadminserver.fm
Installation and Initial Configuration
Set Up DCMP
2. After login, the initial configuration screen opens up. If desired, you can change the password with Change
admin password and Re-type admin password.
In the Allowed remote addresses field, you enter the addresses of the DLS servers as a comma-separated
list, or as a single address, if there is only one DLS server. If the DCMP is installed on the DLS machine, the
value is 127.0.0.1.
If Require DLS to authenticate is checked, the DLS must authenticate to communicate with the DCMP. For
this option, a DLS password must be entered; the DLS must present this password to authenticate with the
DCMP.
3. In the Cluster Setup screen, you can check or configure the appropriate addresses and ports for one or more
DLS machines. If a DLS cluster is to be used, check Use cluster mode.
The Local Host field contains the IP address of the DCMP server.
When operating the DLS as a cluster, the IP addresses of each machine in the cluster must be entered in Host
1 ... 4.
In the List Entries screen, you can view all Contact-Me messages from the DLS.
4-10
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
For testing purposes, a very short Poll interval can be chosen; however, in a live environment, longer intervals
are recommended.
5. Define one or more Device IP Ranges. Any IP Devices within the IP ranges defined by IP address from and
IP address to will be updated via DCMP. Hence, whenever a change is made to an IP device within an IP
range listed here, the DLS will send a message to the DCMP to set the Contact-Me entry for that phone.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
4-11
instadminserver.fm
Installation and Initial Configuration
Set Up DCMP
2. Navigate to Profile Management > Device Profile and create a device profile using the newly created "DCMP
Miscellaneous" template.
3. Navigate to IP Devices > IP Device Management > IP Device Configuration. Use the Search function, the
"Table" view, and the "Object" view to select the subscriber number for the phone to be configured. In the
"Profile" Tab, select the profile you just created, and assign it to the phone.
4-12
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
Completed configuration as described in the DLS documentation (section 4.4, " Configure Phone for DCMP ")
Configured network firewall for the required ports 18443,18080 and 21.
IMPORTANT: The supported IP clients - ODC (WE/PE/FC) dont support DCMP. Therefore IP
Clients are not supported for a DCMP integration.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
4-13
instadminserver.fm
Installation and Initial Configuration
Set Up DCMP
4. As a test case for a configuration change, modify the display name on the phone. Navigate to IP Devices >
IP Phone Configuration > Gateway/Server > "SIP Terminal Settings" Tab. Activate Use Display ID (or
Use Display ID (Unicode characters)) and set the Display ID to "Its Working!", for instance. Save the
change in DLS.
5. To verify that the job is running, look in Job Coordination > Job Control and click on the Search button. Then
click on the specific entry and select the "Object" view. In the "Basic Data" Tab you can see that the job will
be handled via DCMP.
6. In the "Configuration Data" Tab you can see the specific change that was requested.
4-14
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
7. In the DCMP GUI, click on the List Entries menu. You should see the Contact Me setting in the list. The
Device ID should be the MAC address of the phone.
8. In the DLS GUI, in Job Coordination > Job Control > "Basic Data" Tab, you will see an "End Time" once
the change is made.
9. In the DCMP GUI, you will see the Contact Me entry is removed.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
4-15
instadminserver.fm
Installation and Initial Configuration
IMPORTANT: Do NOT install a hotfix directly. Instead first install the base version of the hotfix and
then upgrade to the hotfix (e.g. the base version of V7R2 408.05 is the V7R2 408.00).
NOTE: Hotfixes deliver the complete DLS package & theyre also cumulative, e.g CV408.03 contains
all the fixes delivered in CV408.01 & CV408.02.
4-16
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
4-17
instadminserver.fm
Installation and Initial Configuration
IMPORTANT: Microsoft .NET v3.51 must be installed in both Nodes first, in order for RapidStat to
operate ( please refer to Section 4.5.1.2, "Install Microsoft .NET v3.51 / v4" )
Click on Next.
2. Click on I Agree to accept the license agreement.
4-18
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
4-19
instadminserver.fm
Installation and Initial Configuration
3. In the Installation Configuration screen, under DLS Installation Type, select the option One Node of a
Multinode Installation.
Click on Next.
4. In the Choose Install Location screen, choose the target directory in which the DLS shall be installed.
NOTE: The directory path must not contain blanks, as in "Program Files", for instance.
Click on Next.
4-20
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
5. In the Default Data Path screen, enter the path of a directory, to which all nodes must have access. Here,
configuration data common to all DLS nodes are stored. This directory must exist, and writing access for this
directory must be granted to the DLS, also for installation purposes. The IP address must be the one of the
1st DLS node (NLB cluster oriented).
NOTE: In case a notification window appears here, asking whether another node shall be
installed, in addition to existing ones, click on "No". The notification window will appear if the file
common_dls.properties exists in the specified directory.
NOTE: To avoid any kind of problems with backup/restore actions when DLS Node 1 is down/
unreachable for any reason, you need to modify the default path for common Openscape
Deployment Service Data to be on different server (i.e. File Server), on the same domain like the
rest of the Multinode servers i.e.
\\POSTM3-FileServer\MultinodeShare\CommonDlsData
or
\\10.10.170.100\MultinodeShare\CommonDlsData
NOTE: CommonDLSData should be in the witness server if one exists (in the case of
synchronous mirroring). If a witness doesnt exist then the folder should be located on an
external server other that that of CLA. Any other option could obstruct multinode migration
scenarios (see Section 16.18, "Migration Scenarios" ) with minimum outage.
IMPORTANT: The Common Data Path should not be used to store files outside the scope of DLS's
own node clustering purposes and DLS administrative tasks (e.g. csv/archive exports, Profile/
Template exports etc).
Click on Next.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
4-21
instadminserver.fm
Installation and Initial Configuration
6. In the Database Settings screen provide the necessary specifications for the database. If you wish to deploy
a mirrored database for maximum reliability, select the option MSSQL + Mirroring under Database Type.
Under Database Server, in the field DB Hostname (Principal), specify the "Principal" database server, and
in the field Failover Server (Mirror), specify the backup database server, which will fill in in case the Principal
fails.
Under MSSQL specific entries, in the field Data Directory on Server, enter the directory on the database
server in which the DLS database is located. This directory must exist already. It should have been created
before theSQL server installation (see Section 4.2, "Install MS SQL Server for Remote Database", step 2).
NOTE: It is recommended to use the same directory path both on the Mirror and on the
Principal.
Under DB Instance, enter the instance under which the DLS database is to operate (see Section 4.2, "Install
MS SQL Server for Remote Database", step 4 resp. Section 4.2.1, "How to install Microsoft SQL Server", step
9).
Click on Next.
4-22
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
7. In the Account Configuration screen, in the fields Account and Password, enter the access data of the user
the DLS shall run under. The user must be a member of the administrator group, and it must exist already.
NOTE: In case of a DLS installation in DNS environment you have to enter the full FQDN
account i.e., [email protected] or multimode.local\testuser. If you use plain testuser it
denotes a local machine (Workgroup environment) user and not a domain user.
Click on Next.
8. Now, in the Choose Components screen, select the desired DLS components.
Click on Next.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
4-23
instadminserver.fm
Installation and Initial Configuration
9. In the Cluster Configuration screen, under Current Node, you see the node machine on which you are
currently installing the DLS. Under Other Nodes, in the Host Name fields, enter the names of the
corresponding node machines, and in the Port fields, enter the port used by the DLS running on the
corresponding machine for communication with the other nodes. If you have selected the DCMP in step 8, you
must specify the port on which the DLS receives data from the DCMP in the field DCMP-Port.
NOTE: In case of a workgroup or DNS with no FQDN orientation,an IP address will be added
instead.
Click on Next.
10. In the Licensing Configuration field, you provide the specifications required for licensing. Under Customer
License Agent - CLA, in the field CLA Hostname, you enter the IP address of the CLA server, and in the field
CLA Port, you enter the corresponding port. Under Customer License Manager - CLM, in the field CLM
Hostname, enter the IP address of the CLM server, and in the field CLM Port, you enter the corresponding
port.
NOTE: CLA and CommonDLSData folders should be located on different servers. In any other
option, Mirroring is not possible and could also obstruct multinode migration scenarios (see
Section 16.18, "Migration Scenarios" ) with minimum outage.
4-24
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
Click on Next.
11. In the Administration Account Password screen, in the fields Password/Repeat Password, enter the
password for the DLS user "admin".
Click on Next.
12. In the next screen, you see a brief overview on the installation settings. To start the installation, click on Install;
to revise settings, click on Back.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
4-25
instadminserver.fm
Installation and Initial Configuration
4-26
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
13. If you have clicked on Install previously, you will be presented with messages about the installation process.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
4-27
instadminserver.fm
Installation and Initial Configuration
Click on Next.
2. Click I Agree to accept the license agreement.
4-28
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
3. In the Installation Configuration screen, under DLS Installation Type, select the option One Node of a
Multinode Installation.
Click on Next.
4. In the Choose Install Location screen, choose the target directory, wherein the DLS is to be be installed.
NOTE: The directory path must not contain blanks, as in "Program Files", for instance.
Click on Next.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
4-29
instadminserver.fm
Installation and Initial Configuration
5. In the Default Data Path screen, specify the path of the directory for common DLS configuration data. This
path has been specified in Section 4.5.3.1, "First Node", step 5.
Click on Next.
6. As the first DLS node is already installed and has stored the file common_dls.properties in the
appropriate directory, you will be presented with a notification:
Click on Yes.
4-30
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
7. In the Database Settings screen provide the necessary specifications for the database. If you wish to deploy
a mirrored database for maximum reliability, select the option MSSQL + Mirroring under Database type.
Under MSSQL specific entries, in the field Data Directory on Server, enter the directory on the database
server, in which the DLS database resides. This directory must exist already. It should have been created
before the SQL Server installation.
NOTE: It is recommended to use the same directory path both on the Mirror and on the Principal
Server.
Under DB Instance, enter the instance under which the DLS database is to operate.
Click on Next.
8. In the Account Configuration screen, in the fields Account and Password, enter the access data of the user
the DLS shall run under. The user must be a member of the administrator group, and it must exist already.
NOTE: In case of a DLS installation in DNS environment you have to enter the full FQDN
account i.e., [email protected] or multimode.local\testuser. If you use plain testuser it
denotes a local machine (Workgroup environment) user and not a domain user.
Click on Next.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
4-31
instadminserver.fm
Installation and Initial Configuration
9. In the Cluster Configuration screen, under Current Node, you see the node machine on which you are
currently installing the DLS. Under Other Nodes, in the Host name fields, enter the names of the
corresponding node machines, and in the Port fields, enter the port used by the DLS running on the
corresponding machine for communication with the other nodes. If you have selected the DCMP in step 8, you
must specify the port on which the DLS receives data from the DCMP in the field DCMP-Port. If the data have
already been input at the first node, they can be checked, modified, or extended once more.
Click on Next.
10. In the next screen, you see a brief overview on the installation settings. To start the installation, click on Install;
to revise settings, click on Back.
4-32
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
11. If you have clicked on Install previously, you will be presented with messages about the installation process.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
4-33
instadminserver.fm
Installation and Initial Configuration
stop database mirroring on SQL server Principal by means of "MS SQL Management Studio",
set up mirroring following the instructions in Section 4.6, "SQL Database Mirroring Setup", except the SQL
statements for configuring endpoints.
4-34
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
4-35
instadminserver.fm
Installation and Initial Configuration
Start DLS
4-36
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
4-37
instadminserver.fm
Installation and Initial Configuration
Initial Configuration
6. Import Templates
Call: Main Menu > Profile Management > Template Overview > "Template data" Tab
You have the option to load existing DLS templates stored in ZIP files.
Please refer to Section 15.5, "Editing Templates" for more information on templates.
7. Element Manager
Call: Main Menu > Element Manager > Element Manager Configuration
Select the element manager type you want to configure under Element Manager type. For configuration
options, see Section , "Element Manager".
4-38
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
Using the Windows Start menu Start > Programs > Deployment Service > DeploymentService.
You can find information on operating the DLS client from Chapter 5 onwards.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
4-39
instadminserver.fm
Installation and Initial Configuration
FTP Server
HTTPS Server
4-40
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
4-41
instadminserver.fm
Installation and Initial Configuration
To assign the new user a directory, select Shared Folders in the Page area and click Add. In the subsequent
window, select the directory where you want to store the software subdirectories. To assign read access to the
DLS, activate the Read option in the Files area.
Click OK. The FTP server is now available. Current connections are displayed in the servers status window.
4-42
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
4-43
instadminserver.fm
Installation and Initial Configuration
IP addresses for the SIP server and SIP registrar (option 120))
In Unify IP phones, the DLS IP address and the VLAN ID can be communicated via vendor-specific parameters.
VLAN ID assignment via DHCP works as follows on optiPoint 410/420 phones:
If the "DHCP" VLAN method is set on the phone and QoS is active on layer 2, the VLAN ID is assigned by a DHCP
server. This procedure is made up of two steps. The phone starts by issuing a discovery message with the
"OptiPoint" vendor class to try to obtain an IP address for a DHCP server. In the second step, the phone sends a
tagged discovery message in the VLAN whose ID it received in the first step. This time, the "OptiIpPhone" vendor
class is used.
If the VLAN method is set to "manual", only a lease with the "OptiIpPhone" vendor class is obtained from the
phone.
4-44
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
4-45
instadminserver.fm
Installation and Initial Configuration
Line
Contents
default-lease-time 864000;
max-lease-time 8640000;
ddns-update-style ad-hoc;
9
10
class "OptiIpPhone" {
11
option vendor-encapsulated-options
12
01:07:53:69:65:6D:65:6E:73:
13
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;
14
15
16
17
class "VLAN-discovery-OptiPoint" {
18
option vendor-encapsulated-options
19
01:07:53:69:65:6D:65:6E:73:
20
02:04:00:00:00:0A;
21
22
23
24
25
4-46
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
The instructions in lines 10 to 15 transfers DLS addresses to workpoints. Lines 12 and 13 contain two hexadecimal
values consisting of:
Option - Length - Value.
The first of the two lines contains the value "Siemens". The second line contains
"sdlp://192.168.3.6:18443" (DLS address).
Line 10 contains a freely selectable name and line 14 determines the vendor class to which the configuration
applies.
Lines 17 to 21 contains the allocation of the VLAN ID. The VLAN ID is handed over in line 20 with the option 2,
the length 4 and the value as a hexadecimal number (here 0A = 10). In contrast to the other options, the decimal
VLAN ID is converted into a hexadecimal number.
NOTE: For information on converting ASCII characters to hexadecimal values, see "ASCII Table
(Standard)" and "ASCII Table (Enhanced)" on page 17-2 and on page 17-3.
Restart the DHCP service once you have modified the configuration. Use the rcdhcpd restart or alternatively
the etc/init.d/dhcp stop command and then /etc/init.d/dhcp start to do this. To check syntax,
enter rcdhcp check-syntax via the console.
If the configuration is correct, terminals should register independently on the DLS after a restart. If the
configuration is not correct, you can use a "network sniffer", for example, Ethereal (V 0.10.11 or higher), to locate
any errors.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
4-47
instadminserver.fm
Installation and Initial Configuration
4-48
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
DNS
NTP
FTP
TFTP
The following screenshot shows the dashboard of an Infoblox 550 appliance, here configured as DHCP, DNS, and
NTP server for an OpenScape Voice environment:
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
4-49
instadminserver.fm
Installation and Initial Configuration
4.12.7.1 Installation
After the Infoblox appliance is cabled to the network (please refer to the installation guide shipped with your
appliance) you can access the device remotely across your Ethernet network.
You can administrate and configure the appliance via HTTPS or via command line interface (CLI) using SSH. If
you wish to use SSH, you have to login via HTTPS once and enable SSH first.
This manual describes the adminstration via HTTPS; for detailed information on administration via CLI, please
refer to the "Infoblox CLI Guide".
Access via HTTPS
To log in, proceed as follows:
1. Open a web browser and enter
https://<IP address or hostname of your Infoblox appliance>
2. Enter user name and password.
The default user name is "admin", and the corresponding password is "infoblox". Please change the password
after the first login.
Access for CLI via SSH
To enable access for the CLI, you must be logged in via HTTPS (see Access via HTTPS).
1. Select Grid > Grid Manager and expand the toolbar. In the Edit menu, select Grid Properties.
4-50
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
2. The Grid Properties Editor opens up. In the Security tab, check the Enable Remote Console Access field.
3. Now you can administrate and configure your Infobox appliance using the CLI via SSH. For this purpose, every
SSH v2 client can be used, for instance, PuTTY for Windows.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
4-51
instadminserver.fm
Installation and Initial Configuration
Basic Configuration
1. Open a web browser and establish an HTTPS connection with the IP address of the LAN1 port. To reach the
default address, enter https://<192.168.1.2>.
NOTE: During the login process, several certificate warnings may appear, but they can be
ignored at this stage of configuration. To stop these warning messages, a new self-signed certificate or an import of a third-party certificate is necessary. For more information on how to
implement certificates, see the Infoblox Administration Guide.
2. Log in as "admin" with the default password "infoblox".
3. Read the license agreement and accept it.
4. The Grid Setup Wizard appears. Select Configure a Grid Master > Next.
5. Set the grid properties:
Grid Name
This name (text string) is used by the grid master and by appliances joining the grid to authenticate each
other when establishing a VPN tunnel between them. The default grid name is "Infoblox".
Shared Secret
This text string is used as a shared secret by the grid master and by appliances joining the grid to
authenticate each other when establishing a VPN tunnel between them.
Show Password
Activate the switch to have the password displayed, or deactivate it to have the password hidden.
Hostname
Specify a valid DNS host name for the Infoblox appliance.
4-52
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
Host Name
Specify a valid DNS host name for the Infoblox appliance.
IP Address
Shows the IP address of the LAN port.
Subnet Mask
Shows the subnet mask of the LAN port.
Gateway
Shows the IP address of the gateway resp. router for the subnet in which the LAN port is located.
Port Settings
Select the appropriate settings for the port from the list.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
4-53
instadminserver.fm
Installation and Initial Configuration
4.12.7.2 Configuration
General DHCP Configuration
First, you must specify a network and a range of IP addresses to be leased.
NOTE: For enabling active DNS forwarding over DHCP, a working DNS must be present in your
network. You can check this by means of the following CLI commands:
- Determine the IP address of the DNS server which has been configured for your network. Under
Windows, this is done using the command:
ipconfig /all
- With nslookup and a random IP address or a random host name, you can determine if the DNS
server is working correctly:
nslookup 172.21.101.15 or
nslookup wsname.domain.net
Adding a Network
1. Select Data Management > IPAM and in the toolbar under Add, click Add IPv4 Network.
Adress:
Address of the network. Example: 172.21.101.0
Netmask:
By means of the netmask slider, select the netmask /24 (255.255.255.0) .
3. Click Save&Close.
4-54
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
Start:
Beginning of the address range. Example: 172.21.101.100
End:
End of the address range. Example: 172.21.101.199
3. Click Save&Close.
NOTE: Please note that every DHCP server in your environment should have at least one range
which does not overlap with a range of another DHCP server in the same environment.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
4-55
instadminserver.fm
Installation and Initial Configuration
4-56
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
Add a new option with the properties Name="Vendor-ID", Code= "1" and Type="String".
Add another option with the properties Name="Vendor-ID", Code="1" and Type="String".
If a virtual LAN (VLAN) is used: Add another option with the properties
Name="VLAN-ID", Code="2" and Type="16-bit unsigned integer".
3. Navigate to Data Management > DHCP > Networks, select your network (e.g. 172.21.101.0/24) and in the
toolbar, click Edit.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
4-57
instadminserver.fm
Installation and Initial Configuration
If a virtual LAN (VLAN) is used, the VLAN ID must be specified in a similar way.
5. Navigate to Grid > Grid Manager > DHCP > Services. Check your network and click the play button. The
DHCP service starts.
4-58
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
instadminserver.fm
For internal use only
IMPORTANT: The Uninstaller removes any rollback related directories except the rollback database
backup for remote database deployments since it does not know the user supplied directory for the
database backup during an upgrade installation.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
4-59
instadminserver.fm
Installation and Initial Configuration
4-60
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bof.fm
For internal use only
Enter "admin" for Account and the password set during installation for Password.
If applicable, select your language and confirm with Login.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
5-1
bof.fm
The DLS User Interface
Ending
NOTE: Communication between the DLS server and DLS client is set up using the port number
18080 or 10443 (secured connection).
Note that communication between the DLS server and IP device takes place over port 18443
(default mode) or 18444 (secure mode).
For more information, refer to Section 7.5.4.4, ""DLS Connectivity" Tab".
5.2 Ending
1. In the main menu (see Section 5.4.1), select Logoff <account>.
2. Confirm the security prompt with Yes.
The login window reappears in readiness for a new account to log on.
3. Close the browser window.
5-2
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bof.fm
For internal use only
Main Menu
Work Area
Status Area
You can change the position of the division between the main menu and the working area by clicking and dragging
the separator. Clicking one of the arrow icons in the upper area of the separator moves the division all the way to
the right or left, so that the working area or main menu is removed from the display.
NOTE: You can also use the operating sequence in Section 15.1, "First Steps: Changing IP Device
Parameters" to get to know the interface better.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
5-3
bof.fm
The DLS User Interface
Application Interface
5-4
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bof.fm
For internal use only
You can use the structured main menu to reach all DLS components. Simply click the "+" or "-" in front of a
directory symbol (or double-click the directory name) to open or close the directory. Click a contents icon to display
the contents in the work area.
The contents icons may look like this:
Directory with further subdirectories or pages.
Page in normal mode (action completed without encountering error or not yet completed).
Page where an action is currently running, for example, when scanning IP Devices.
Page with an action that ended incorrectly.
Page not accessible due to missing account rights.
In addition, the main menu features these special functions:
Help
Opens the online help.
Logoff <account>
Logs off the user indicated in <account>.
For information on other icons, see Section 5.4.2.4, "Icons beside entry fields".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
5-5
bof.fm
The DLS User Interface
Application Interface
Content Area
Action Buttons
Message Windows
5-6
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bof.fm
For internal use only
5.4.2.1 Toolbar
The component currently open in the main menu is displayed on the left.
On the right hand side, elements for
Tenants
Job ID
Exec Time
are displayed.
Tenant
All tenants associated with the current account are shown. Additionally, for the admin account,
are shown.
Job ID
A job is a combination of deployment actions that should be executed at a fixed time.
NOTE: Switching from daylight saving time to regular time (one hour back) will not lead to a second
execution of a job that has been started in the time interval hereby doubled. When switching from
regular time to daylight saving time (one hour advance), a job which is scheduled for this skipped time
will not be executed.
For more information, see the interface description in Chapter 14, "Job Coordination" and sequence descriptions
in Section 15.8, "Using Job Coordination".
Exec Time
Specify the execution time for the job. The defaut is asap, that is, the job is executed immediately. By clicking on
the calendar symbol
, you can define a point in time and conditions for job execution with the aid of a separate
calendar dialog.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
5-7
bof.fm
The DLS User Interface
Application Interface
NOTE: In many cases, different options are available for executing a function.
Sample function: Search: this can be performed using the Object entry in the menu bar, the button
of the same name, or the <F3> function key.
The following lists all entries that can be found in the menu bar:
Object
Edit
5-8
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bof.fm
For internal use only
View
Go To
Action
Generate All Templates (templates are generated for all objects or masks associated with the selected
IP Device type)
Save Selected Mobile User to Archive (save mobile user data in a ZIP archive; see Section 16.14.10.2,
"Saving Mobile User Data")
Load Mobile User from Archive (retrieve mobile user data from a ZIP archive; see Section 16.14.10.3,
"Loading Mobile User Data")
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
5-9
bof.fm
The DLS User Interface
Application Interface
Copy IP Device (Copy data of an IP Device, see also Section 16.6, "Replacing an IP Device", Section
16.8, "Replacing HFA with SIP Software and Vice Versa with Identical Device IDs", Section 16.13.7,
"Replace IP Phone")
Save Selected IP Device to Archive (Selected IP Devices are written into .zip archive.)
Load IP Device from Archive (Loads data of IP Devices from .zip archive.)
Simulate Plug&Play (Test of location and default profile configuration. Location data are entered and after
clicking Simulate Plug&Play, the data sent to the phone which might register with the DLS can be
checked. )
Import Certificate (Imports a certificate for the selected IP Device (only available in Certificate
Management). For more information, see Section 16.13, "Security: Administering Certificates".)
Remove Certificate (Deletes a certificate for the selected IP device (only available in Certificate
Management). For more information, see Section 16.13, "Security: Administering Certificates".)
Help
5-10
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bof.fm
For internal use only
Search
Shows a search mask in the content area for filtering individual IP Devices from the total set of registered
IP Devices. See Section 5.5, "Search Functionality".
Object
Shows an individual data record for an IP Device in the content area.
Table
Shows a list of all available data records in the content area.
New
Creates a new data record.
Template
Shows a template in the content area that you can save and then use later for searches.
NOTE: If you are in the Search view, you can change all elements (for example, by entering values
in fields or activating check boxes) in order to define the search criteria or enter data.
In the Template and New views, only data that can be edited and saved in the DLS database is
visible. All other fields are dimmed. General data from the content area cannot be saved as a
template.
Frequently, when the search result contains data from existing IP Devices (Object or Table view),
some elements are uneditable and therefore also dimmed.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
5-11
bof.fm
The DLS User Interface
Application Interface
Click the tab containing the contents you want to view or edit. Information on the various tab interfaces can be
found in Chapter 6, "Administration" to Chapter 14, "Job Coordination".
The most important control elements
Text field
For displaying / entering freely selected alphanumerical characters as well as allowing the data reset for text
items.The boolean data items already provide this option. At DLS GUI level, when creating DLS templates,
the boolean items support the following options:
5-12
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bof.fm
For internal use only
For selecting an item from a list and for entering freely selected text.
If available, the Find in Table dialog opens with several entries when you click the list button at the right of the
field.
Choice field
Click a value (for example, 17) and increase or decrease the value by clicking the appropriate arrow.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
5-13
bof.fm
The DLS User Interface
Application Interface
Options
Check box
For activating or deactivating a property. There is also a third status for a check box in the Search view, which
is known as "undefined" (half-tone display).
This button provides you with a separate calendar dialog for selecting a point in time and conditions for job
execution.
5-14
Immediately: The job is executed immediately. If the IP Device should be unreachable, the job will be
cancelled.
Immediately or after registration: The job is executed immediately. If the IP Device should be
unreachable, the job will be started anew when the IP Device is registered.
At selected time: The job is started at the point in time selected in the calender field.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bof.fm
For internal use only
At selected IP Device time: The job is started at the point in time selected in the calender field.
However, here, not the system time on the DLS server is valid, but the local time in the IP Device. This
option is expedient when the DLS server and the IP Devices are in separate time zones.
At selected time or after registration: The job is started at the point in time selected in the calender
field. If the IP Device should be unreachable, the job will be started anew when the IP Device is
registered.
At selected IP Device time or after registration: The job is started at the point in time selected in the
calender field. However, here, not the system time on the DLS server is valid, but the local time in the
IP Device. This option is expedient when the DLS server and the IP Devices are in separate time
zones. If the IP Device should be unreachable, the job will be started anew when the IP Device is
registered.
OK accepts the value in the time field, Cancel closes the calendar without accepting the data.
NOTE: Please note that no new execution time will be calculated when the IP Device is moved
to another timezone meanwhile.
The button is only active if the field contains an IP address. For information on how to operate the WBM, refer
to the Workpoint Administration Manual.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
5-15
bof.fm
The DLS User Interface
Application Interface
Click the underlined link (shown in bright green when the mouse hovers over it).
A dialog window opens with a list of all additional topics involving IP Devices.
Select an entry from the list and click OK. The display then shows the interface that you selected with the value
that was transferred, and a search is performed automatically.
Entry field display
Elements that do not allow direct input are dimmed on the screen). Fields that are not relevant to the current
configuration are also dimmed, for example, an SIP parameter in a HFA workpoint.
Mandatory fields are shown with a black frame.
Elements that contain an invalid value are shown with a red frame after you leave the field or when an action is
executed.
If this is the case, correct the value and perform the action again.
Often when you hover the mouse over elements, information known as "ToolTips" appears at the mouse pointer
(example).
5-16
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bof.fm
For internal use only
Icon
Area
Meaning
Field
IP Phone Configuration
IP Client Configuration
Device Type
IP Phone Configuration
IP Client Configuration
Device ID
IP Phone Configuration
IP Client Configuration
Device Type
Title Bar
Pending Alarms
IP Phone Configuration
E.164
IP Phone Configuration
E.164
IP Phone Configuration
Device Type
IP Phone Configuration
IP Client Configuration
IP Gateway Configuration
Device Type
Table 9
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
5-17
bof.fm
The DLS User Interface
Application Interface
Icon
Area
Meaning
Field
IP Phone Configuration
IP Client Configuration
Device Type
Table 9
Some icons are also displayed in a separate column in Table view. This means that workpoints with particular
properties (error messages) can be easily sorted and filtered out. Icons are also displayed in the main menu
(Section 5.4.1, "Main Menu") and in the message window (Section 5.4.2.6, "Message Windows").
5-18
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bof.fm
For internal use only
Hold the <SHIFT> button down and click the top and bottom rows to mark all the rows in between (including
the selected rows).
Hold the <CTRL> button down and click individual entries to add or remove them from the selection.
If you select Edit - Select All in the menu bar, you can add all selection entries.
If you click Stop, the changes to the current workpoint are completed, but no additional data is transferred. To
proceed, start the entire procedure anew.
After the data has been successfully transferred, a green check mark appears beside each updated entry. A note
icon is displayed for entries where the job is not yet complete.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
5-19
bof.fm
The DLS User Interface
Application Interface
Selecting additional sort columns as sub sort columns may be useful if the main sort column contains multiple
identical values.
Selecting additional sort columns is available only in the table view of objects. It is not available for embedded
tables in the content area. For those tables, only the sort direction can be changed.
5-20
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bof.fm
For internal use only
Multiple objects
Certain objects, on the other hand, allow you to create and display several different entries per object (for example,
with Profile Management > Device Profile > "Templates" Tab).
* (asterisk): The entry has been changed but the changes have not yet been saved.
+ (Plus): The entry has been added to but the additions have not yet been saved.
- (Minus): The entry has been deleted but the deletion has not yet been saved.
If any of these symbols is displayed, you can undo the change with
The following applies when transferring data from one row to another:
Data is moved from the current row (the row with the cursor).
Hold the <SHIFT> button down and click the top and bottom rows to mark all the rows in between (including
the selected rows).
Hold the <CTRL> button down and click individual rows to add or remove them from the selection.
Click the
changes).
button to transfer the data (all target rows are marked with an * (asterisk) until you save the
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
5-21
bof.fm
The DLS User Interface
Application Interface
In Object and Table view, navigation buttons are shown for selecting data records. If one element is selected, the
number of the selected data record is shown in the field to the left. In the window to the right, the total number of
data records in the table is shown. If several elements are selected, the highest number of the selected data
records is shown in the field to the left. In the field to the right, the total number of data records in the table is shown,
followed by the number of selected data records in brackets.
For additional information on operating the DLS interface, refer to Section 15.1, "First Steps: Changing IP Device
Parameters".
5-22
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bof.fm
For internal use only
the number of requests is lesser than 50% of the maximum number, and
the difference between the maximum and the actual request count is greater than 10.
Server is set to inactive.
In this example, the DLS node "valluga3" has been integrated in the cluster, but is currently not active:
Extended View
To arrive at the extended view, click on a server symbol with the right mouse key. The DLS cluster menu opens
up; select Switch Layout.
The extended view displays detailed informations, e.g. the names of DLS nodes and number of requests.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
5-23
bof.fm
The DLS User Interface
Application Interface
In the following example, one node is running at half capacity, one at full capacity, and one node is set to inactive.
5-24
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bof.fm
For internal use only
Cluster Menu
In basic view or extended view, click on a server symbol with the right mouse key to get the DLS cluster menu.
Refresh Cluster Status: Refreshes the data (symbol, request count) for all nodes.
Show Cluster Data: Forwards to Administration > Cluster Configuration > Deployment Server.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
5-25
bof.fm
The DLS User Interface
Search Functionality
* (asterisk): Stands for any sequence of characters. It may be combined with other wildcards. Partial inputs,
such as, 192.168.*, are consequently possible for an IP address range from 192.168.0.0 to 192.168.255.255.
? (Question mark): Stands for exactly one character. It may be combined with other wildcards. For example:
ab??c finds all records where the field has 5 chars starting with ab and ending with c
^ (Circumflex): Stands for an empty field. It cannot be combined with wildcards. For example: ^ finds records
with empty field, a^a finds records with field containing the string "a^a"
! (Exclamation mark): As first character of a string, the search string will be inverted. Therefore "!search string"
finds all records where the regarding field contains anything else than search string. The exclamation mark
may be combined with *,? and |. The ! must be marked with a leading \ when itself is the first character of
the search string. It may be combined with other wildcards. For example: !a* finds records with field not starting
with a
< (Lower than): As first character of a string "<search string" all values lower than the search string will be
found. The < must be marked with a leading \ when itself is the first character of the search string. It cannot
be combined with other wildcards. For example: <100 finds all records with field value lower than 100
> (Greater than): As first character of a string ">search string" all values greater than the search string will
be found. The > must be marked with a leading \ when itself is the first character of the search string. It
cannot be combined with other wildcards. For example: >Munich finds all records with field value greater than
Munich, that means Paris, Oslo but not Berlin and Athens
| (Vertical bar): Different search strings are separated from each other and are used for OR search. All
elements containing "search string1|search string2| search string3" are found. The combination with wildcards
is not allowed, but the search can be inverted ('!'). Therefore all elements not containing "search string1|search
string2| search string3" are found. The | must be marked with a leading \ when itself is to be searched. For
example: abc|def|ghi finds all records where the field contains abc, def, OR ghi !abc|def|ghi finds all records
where the field contains anything but abc, def, OR ghi.
5-26
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
6 Administration
Call: Main Menu > Administration
Basic settings for operating the DLS are made in the Administration area.
This menu contains the following submenus:
Account Management
PKI
Server Configuration
Cluster Configuration
Alarm Configuration
Backup/Restore
File Server
Automatic Archiving
Trace Configuration
Server Licenses
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-1
administration.fm
Administration
Account Management
Account Configuration
Policy Settings
For maintenance issues it is helpful to delegate tasks to multiple persons. These may obtain different accounts.
For security reasons it is not wanted that each account has access to every area of the DLS. Hence, the several
areas can be allowed or disallowed individually.
To each administrative function, an access right is assigned, and only accounts with this access right are allowed
to call this function. In some cases, multiple functions are combined in a single right, for instance, the right to create
jobs comprehends the right to edit jobs, like, e. g., update the job status or reset the job.
There is no right which disallows an access explicitly.
The DLS offers a role concept. Each role groups bundles a number of rights. It is possible to define as much roles
as necessary.
Some important roles are preconfigured and cannot be changed or deleted, only the default description text can
be modified. These system roles are primarily used as patterns for self-defined roles. Not each of these roles
makes sense when used all by themselves.
To each account, as many roles as needed can be assigned. The resulting right is the sum of all rights of all
assigned roles.
After a new installation of the DLS, an 'admin' account exists, which has all rights based on system defined roles.
This account remains undeletable and it's name remains unchangeable, and the system roles cannot be removed
from it.
When logging with the admin account on DLS user interface via Assistant for the first time after the installation,
the default password must be changed for security reasons. The password must be updated in Assistant too.
With an update installation from a DLS without Account Management to a DLS with Account Management, an
'admin' account with all system defined roles is created. Therefore, the admin account has all rights. To all other
accounts, the INFO role is assigned. This enables them to open all screens and to search for all data, but all other
functions are disabled. All other roles and rights have to be set manually.
With future DLS upgrades, new functions and new masks will be accessible by system roles only. New rights must
be added to user defined roles manually. Therefore it is recommended to set rights by combination of system roles
and small user defined roles, rather than copying and modifying system roles.
6-2
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Account Management
Example
Goal: An account shall receive editing rights (except bulk-change and create-template) for gateways only.
Variant B: Define a new role based on EDIT_ONE and additionally set the 'Search' right in every relevant mask
(Gateway Configuration, QoS Data Collection).
Variant C: Define a new role with 'Search' right for all gateway masks (Gateway Configuration, QoS Data
Collection) PLUS system role EDIT_ONE.
Only in variant C, the account automatically obtains the right to use newly added functions in the three gateway
masks.
NOTE: Changes on currently used roles will take effect after next login.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-3
administration.fm
Administration
Account Management
General Data
"Roles" Tab
"Rights" Tab
"Tenants" Tab
6-4
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Account Management
General Data
Account:
Name of the account.
disabled
This checkbox is activated if this account is disabled.
Password:
New (modified) password for this account.
The password should contain at least six characters and should be non-trivial. Unsuitable entries include words
that can be found in dictionaries and lexica. Ideally, you should choose a combination of numbers, special
characters, and letters that do not contain a personal reference.
Access Type:
Select the allowed interfaces to the DLS server.
Possible options:
DLS-GUI
Access to the DLS server is exclusively permitted via the DLS user interface.
NOTE: For information on using the DLS program interface (DLS API), see Section 16.12,
"Operating the DLS via the Program Interface (DlsAPI)"
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-5
administration.fm
Administration
Account Management
Safety Mode
If this checkbox is activated, configuration changes which may cause an IP Device malfunction must be
acknowledged in an additional dialog window.
Remark:
Field for general information.
Last Login
Shows the date and time of the last successful login.
Unsuccessful Logins
Number of unsuccessful logins since last successful login.
reset
Resets the number of unsuccessful logins in order to unlock this account.
Current Sessions
Shows the number of current sessions.
6-6
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Account Management
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
New
Creates a new account.
Save
Saves the data entered/modified.
Discard
Discards any unsaved changes.
Delete
Deletes one or more accounts (multiple selections possible in Table view) except 'admin' account.
Refresh
Refreshes the content of the relevant page.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-7
administration.fm
Administration
Account Management
Role
Name of roles which are assigned to this account. System defined roles cannot be removed from the 'admin'
account.
Description
Detailed description of this role.
6-8
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Account Management
Here, the sum of all rights from the different roles is displayed for each account.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-9
administration.fm
Administration
Account Management
Tenant
Name of tenants which are assigned to this account.
Remark
Information on the tenant.
6-10
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Account Management
Windows Users
Name of Windows Users which are assigned to this DLS account. Different Windows Users can be mapped to the
same DLS account, but a certain Windows User cannot be mapped to more than one DLS account.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-11
administration.fm
Administration
Account Management
General Data
6-12
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Account Management
General Data
Access Type:
Shows the interface to the DLS server that is relevant for these policy settings. To switch to another access type,
use the navigation in the action button area:
Possible valuse:
no access
This user account is disabled.
DLS-GUI
Access to the DLS server is exclusively permitted via the DLS user interface.
NOTE: For information on using the DLS program interface (DLS API), see Section 16.12,
"Operating the DLS via the Program Interface (DlsAPI)"
Possible Action Buttons
Discard
Discards any unsaved changes.
Save
Saves the data entered/modified.
Refresh
Refreshes the content of this mask from the database.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-13
administration.fm
Administration
Account Management
6-14
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Account Management
Digits Quorum
Minimum count of numeric characters in the password.
Value range: 0 - 20
Default: 0 (= no check)
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-15
administration.fm
Administration
Account Management
Default: 0 (= no check)
Minimum changes
Minimum number of characters that must be altered at password change.
Value range: 0 - 20
Notification time
Period before password expiration within which the users are notified of a password change that will become due.
Value must be less than the Maximum Validity Period value.
Value range: 0 - 30
6-16
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Account Management
Deny time
Interval in days during which a password my not be selected again as a new password by the same account.
Value range: 0 - 180
Default: 0 (=no check)
6-17
administration.fm
Administration
Account Management
Black List
String
List of customer defined strings which may not be contained in new defined passwords (Black list). The check will
be case insensitive.
6-18
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Account Management
IMPORTANT: The following policy settings apply to all users except for administrator user admin.
in case of a user with name "admin" ( the user that is automatically created from dls and cannot be
deleted in any case) the "lock out" policy setting is not taken into consideration.
Allowed failed logins
Allowed number of consecutive failed logins. When this number is exceeded, the account is locked for the time
specified in Account lock.
Value range: 2 - 5
Account lock
When the allowed number of failed logins (Allowed failed logins) has been exceeded, the account will be locked
for the time span specified here.
Value range: 0 - 300
Disabling time
When an account has not been used for the number of days specified here, it will be disabled.
Value range: 0 - 180
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-19
administration.fm
Administration
Account Management
6-20
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Account Management
Session Timeout
In case of inactivity, sessions will be closed after the time span specified here (in minutes).
This time interval is not configurable.It is greyed out & set to 5.
Session Count
Allowed number of sessions for an account at the same time.
(0 = no limit)
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-21
administration.fm
Administration
Account Management
Rights
Weight
ACCOUNT_MGM
90
EDIT_BULK
All editing rights (new, delete, and edit) for all masks, except:
60
Account Configuration
All editing rights for non system related screens without the bulk change 20
possibility. As a rule, this role is not usable in a self-contained way, but
must be combined with another role, or serves as a base for defining a new
role.
EDIT_ONE
EDIT_PKI
All editing rights for PKI related screens. As a rule, this role is not usable 98
in a self-contained way, but must be combined with another role, or serves
as a base for defining a new role.
EDIT_SYSTEM
All editing rights for system related screens (like Backup/Restore) except: 30
Account Configuration
40
Right to view and search data in all available masks, no editing right.
10
INFO_GENERAL
Right to view and search all non-system related screens (like Backup/
Restore), no editing rights.
INFO_PKI
15
INFO_SYSTEM
Right to view and search all system related screens (like Backup/Restore), 5
no editing rights.
ROLE_MGM
6-22
99
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Account Management
Role
Rights
Weight
SECURITY_MGM
TEMPLATE_MGM
Right to edit templates. Valid in all areas in which templates are available. 50
As a rule, this role is not usable in a self-contained way, but must be
combined with another role, or serves as a base for defining a new role.
To be able to create roles, you need an account that contains the role ROLE_MGM. You can assign a user defined
name and a random combination of rights to any new role.
As soon as a role is displayed in the Roles and Rights mask, you can copy it by clicking New, providing a new
name under Role name and subsequently clicking on Save.
To add roles to accounts or remove roles from accounts, you need an account which contains the role
ACCOUNT_MGM.
This area features the following components:
General Data
"Rights" Tab
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-23
administration.fm
Administration
Account Management
General Data
Role name:
Name of role, to which rights will be assigned.
Description:
Detailed description of the role.
Displayed in object view only.
Role Weight
If at least one of the roles assigned to the account has password policy settings of its own, the settings of the role
with the highest weight are valid and overwrite the equivalent global policy settings for that account. For weight
values of system defined roles see the Roles-Weight-Rights table above. These values cannot be changed.
All weights of customer defined roles can be changed by those accounts which have the ROLE_MGM role. The
default weight for customer defined roles is 0.
Displayed in table view only.
Value range: 0 - 100
6-24
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Account Management
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
New
Creates a new account.
Save
Saves the data entered/modified.
Discard
Discards any unsaved changes.
Delete
Deletes one or more rights (multiple selections possible in Table view).
Refresh
Refreshes the content of the relevant page.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-25
administration.fm
Administration
Account Management
Rights:
The rights will be defined on function level.
Possible options:
Area: Right is active for this area. Submenu: Rights is active in all areas of this submenu.
Area: Right is not active for this area. Submenu: Right is not active in any area of this submenu.
Submenu: Right is active in at least one area of this submenu.
Right is undefined.
Reset
Clicking this button resets all fields to inactive.
6-26
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Account Management
Role Weight
The extensive the rights of a role are, the higher its weight should be. Role dependent settings will be passed on
to accounts.
Value range: 1 - 100
Password Policy
Minimum Password Length
Minimum length of a valid password.
Value range: 1 - 20
Default: 1
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-27
administration.fm
Administration
Account Management
Digits Quorum
Number of digits the password must contain.
Value range: 0 - 20
Default: 0 (= no check)
Session Policy
Session Timeout
When there has been no activity for the period (in minutes) specified here, the session will be closed. If the value
is 0, there will be no check.
6-28
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Account Management
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-29
administration.fm
Administration
PKI
6.2 PKI
This menu item consists of the following areas:
Plug-In Configuration
Connector Configuration
Internal CA
Renewal
6-30
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
PKI
General Data
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-31
administration.fm
Administration
PKI
General Data
Description
Description of the PKI connector plug-in configuration
Plug-In Type
The plug-in module used for this configuration
Possible values:
enable Plug-In
Enables this plug-in configuration. A PKI connector license may be required to be able to use an external PKI.
Before plug-in configuration can be enabled, a synchronization with the PKI must be executed via the
Synchronize Button.
6-32
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
PKI
Search
Searches the database for PKI plug-in configurations that match the search criteria.
Clear Window
Deletes the contents of all fields in this view. Thus, existing entries can be deleted in the Search view before new
search criteria are entered.
New
Creates a new data record for PKI plug-in configuration.
Save
Saves the field contents to the database.
Discard
Discards any changes entered.
Refresh
Updates the window using the database.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-33
administration.fm
Administration
PKI
Revocation supported
Indicates if this plug-in configuration supports revocation requests.
6-34
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
PKI
Serial Number
Serial number of the certificate (display only).
Owner
Owner of the certificate (display only).
Issuer:
Issuer of the certificate (display only).
Valid from:
Start of validity for the certificate (display only).
Valid to:
End of validity for the certificate (display only).
Key Algorithm:
Key Algorithm for certificate (display only).
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-35
administration.fm
Administration
PKI
Key Size:
Key Size for certificate (display only).
Fingerprint (SHA-1):
Test algorithm SHA1 (160 bits/20 characters) for certificate (display only)
6-36
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
PKI
Property Name
Property Name.
Value
Value.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-37
administration.fm
Administration
PKI
choose an issuing CA to request certificates from and to be able to verify relationship with the configured trust
anchor,
define high level parameters used in the certificate request sent to the CA,
define and import the trust anchor to be deployed to devices when using this configuration.
A connector configuration can be dedicated to a certificate type (e.g. SPE, 802.1x, WBM ) or can be used as a
global configuration for all / some types of certificates to be deployed.
This area features the following components:
General Data
6-38
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
PKI
General Data
Configuration Name
Configuration Name.
Description
Description.
Plug-In Configuration
Corresponding plug-in configuration.
Issuing CA Name
Issuing CA Name.
enable Connector
Before enabling the plug-in configuration, synchronization with the PKI must be executed.
Clear Window
Deletes the contents of all fields in this view. Thus, existing entries can be deleted in the Search view before new
search criteria are entered.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-39
administration.fm
Administration
PKI
New
Creates a new data record for PKI connector configuration.
Save
Saves the field contents to the database.
Discard
Discards any changes entered.
Refresh
Updates the window using the database.
Import Certificate
Import trust anchor or user certificate into DLS. A dialog window will ask for the current settings.
The Trust Anchor certificate is used when a Server CA certificate is requested from this connector.
At the time user certificates are imported to the connector, the following data are stored in the DLS database:
6-40
administration.fm
For internal use only
Administration
PKI
The Certificate ID. This is the Subject or the Subject Alternative Name of the certificate. The combination
of the PKI Connector ID and the Certificate must be unique.Its up to the administer to select at the tome
of the import whether the Subject or the subject Alternative Name must be used for Certificate ID
The Certificate
IMPORTANT: HiPath 4000 oriented Certificates can only be imported for Trust Anchor through a file
and not PKI.
For further information on CA certificates please refer to Section 16.5, "Configuring Certificates in DLS".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-41
administration.fm
Administration
PKI
Common Name
Common Name.
Possible values:
MAC Address
DNS Name
IP Address
NOTE: Default & only available Common Name value for OpenScape 4000.
None
MAC Address
DNS Name
IP Address
Key Algorithm
Key Algorithm.
Possible values:
DSA
RSA
6-42
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
PKI
Key Size
Key Size.
Possible values:
512
1024
2048
Test
Test the PKI Connector Configuration.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-43
administration.fm
Administration
PKI
6-44
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
PKI
Serial Number
Serial number of the certificate (display only).
Owner
Owner of the certificate (display only).
Issuer:
Issuer of the certificate (display only).
Valid from:
Start of validity for the certificate (display only).
Valid to:
End of validity for the certificate (display only).
Key Algorithm:
Key Algorithm for certificate (display only).
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-45
administration.fm
Administration
PKI
Key Size:
Key Size for certificate (display only).
Fingerprint (SHA-1):
Test algorithm SHA1 (160 bits/20 characters) for certificate (display only)
Serial Number
Serial number of the certificate (display only).
6-46
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
PKI
Owner
Owner of the certificate (display only).
Issuer:
Issuer of the certificate (display only).
Valid from:
Start of validity for the certificate (display only).
Valid to:
End of validity for the certificate (display only).
Key Algorithm:
Key Algorithm for certificate (display only).
Key Size:
Key Size for active certificate (display only).
Fingerprint (SHA-1):
Test algorithm SHA1 (160 bits/20 characters) for certificate (display only)
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-47
administration.fm
Administration
PKI
Alarm Status
Alarm Status of the certificate
Possible values:
valid
expired
Delete
By clicking this button the certificate will be deleted.
Flush
By clicking this button the certificate will be send.
6-48
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
PKI
6.2.3 Internal CA
This area features the following components:
General Data
"Info" Tab
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-49
administration.fm
Administration
PKI
General Data
CA Name
Name of CA.
Description
Description of CA.
enable Internal CA
Switch to enable the internal CA. For this purpose, a CA must have been created, either via Import CA or Create
CA.
Clear Window
Deletes the contents of all fields in this view. Thus, existing entries can be deleted in the Search view before new
search criteria are entered.
New
Creates a new data record for PKI connector configuration.
Save
Saves the field contents to the database.
6-50
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
PKI
Discard
Discards any changes entered.
Refresh
Updates the window using the database.
Import CA
Import CA from .zip file.
Export CA
Export CA to a .zip file.
Create CA
Create CA from a DLS data record.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-51
administration.fm
Administration
PKI
Serial Number
Serial number of the certificate (display only).
Owner
Owner of the certificate (display only).
Issuer:
Issuer of the certificate (display only).
Valid from:
Start of validity for the certificate (display only).
Valid to:
End of validity for the certificate (display only).
Key Algorithm:
Key Algorithm for certificate (display only).
6-52
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
PKI
Key Size:
Key Size for certificate (display only).
Fingerprint (SHA-1):
Test algorithm SHA1 (160 bits/20 characters) for certificate (display only)
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-53
administration.fm
Administration
PKI
6.2.4 Renewal
Call: Administration > PKI > Renewal
With this function, general renewal settings for all certificates of a type can be made.
Name
Name of renewal configuration.
Description
Description for renewal configuration.
enable
Activates configuration. Enable (disable) all global certificate renewal settings.
Certificate
Issuer:
Issuer of the certificate,required to match.
Type of Certificate
Type of certificate.
Possible values:
ALL
Phone Certificate
6-54
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
PKI
SPE Certificate
Connector Configuration
The connector configuration to be used if issuer and type of certificate matches.
When certificates are reaching their end of lifetime period, a renewal may be initiated automatically. As there may
be various connector configurations and external PKIs available to send renewal requests to, it has to be
determined which configuration (thus which plug-in and which external PKI) must be used. There are also
situations where the origin configuration used to create the present certificate has been lost or cannot be
determined.
For such occasions, a global configuration is required to link a certificate by its issuer to a connector configuration
used to request a new certificate and replace the old one.
The process uses a predefined order for searching a connector configuration:
1. lookup a connector configuration matching the issuer and the type of certificate using the global certificate
renewal configuration, otherwise
2. find and use the original configuration used to request the present certificate, otherwise
3. rise an alarm because no renewal configuration can be found using global alarm settings
The process checking the remaining certificate validity period runs in the interval specified in Alarm
ConfigurationSettings Tab (see also Section 6.6.7 "Settings" Tab) .
NOTE: This process is required to run once per day
NOTE: Renewal of certificates will always result in requesting a new certificate. Extending the
validity of an already deployed certificate is not supported.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-55
administration.fm
Administration
Server Configuration
Tenants
Location
P&P Settings
Infrastructure Policy
API Notifications
XML Applications
Options
6-56
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
6.3.1 Tenants
Call: Main Menu > Administration > Server Configuration > Tenants
NOTE: This screen is visible only if multi tenancy is installed (see also Section 16.17.1, "Install/
Deinstall Multi-Tenancy").
This area features the following components:
General Data
"Locations" Tab
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-57
administration.fm
Administration
Server Configuration
General Data
Tenant Name
Unique name of the tenant.
Remark
Information on the tenant.
Used (%)
Indicates how many percent of existant basic device licenses are used currently.
Alarm threshold
When this threshold is exceeded, a license alarm will be generated
6-58
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
Used (%)
Indicates how many percent of existant Mobile User licenses are used currently.
Alarm threshold
Specify the percentage of used mobile user licenses that should generate a license alarm.
Used (%)
Percentage of PKI user licenses used.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-59
administration.fm
Administration
Server Configuration
Used (%)
Indicates how many percent of existant location service licenses are used currently.
Clear Window
Deletes the contents of all fields in this view. Thus, existing entries can be deleted in the Search view before new
search criteria are entered.
New
Creates a new data record for a tenant.
Save
Saves the field contents to the database.
6-60
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
Discard
Discards any changes entered.
Refresh
Updates the window using the database.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-61
administration.fm
Administration
Server Configuration
Location
Name of the location.
Remark
Description of the location.
6-62
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
6.3.2 Location
In this area, you can define locations to group end devices that share common properties, for example, range of
IP addresses, registrar addresses, or E.164 number pattern.
IP address ranges are configured via Administration > Server Configuration > Location > "IP Ranges" Tab.
IP addresses or host names of systems (PBX/gateway or SIP server) for a location can be specified under
Administration > Server Configuration > Location > "Reg-Addresses" Tab.
You can find further configuration possibilities under Administration > Server Configuration > Location.
If no location is defined, all location specific parameters are specified in the Default location.
To enable the reuse of existing templates or device profiles when client networks are to be divided up into affiliates,
hierarchical location definitions are available. For instance, the parent location can be defined by business groups,
and divided up into child locations by E.164 patterns. Those standard profiles which are defined for child locations
extend or overwrite the data of the parent locations standard profiles.
To check a location or profile configuration, the administrator has the possibility to simulate Plug&Play with location
specific data for a device. The determined parameter values are stored temporarily and can be displayed under
IP Devices > IP Device Management > IP Device Configuration.
To prevent overlapping locations, the following restrictions have been devised:
The property which defines a child location must be different from the property that defines a parent location.
Therefore, if a parent location has been defined by a E.164 pattern, the child location must be defined by a
different property.
Per level, only one certain property is allowed for defining a location. Example: All parent locations are defined
by registration addresses. The child locations of one certain parent location are defined by business groups,
while the child locations of another parent locations are defined by E.164 pattern.
To establish a child location, create a new location and assign an already existing location as parent location to it.
This location may not function as child location by itself.
The properties of the parent location are visible in the child locations; only subsets of the parent locations
properties can be configured. However, the restrictions for software and certificate deployment ("SW Deployment
Restrictions" Tab and "Certificate Deployment Restrictions" Tab) in a child location are independent of the
settings of the parent location.
Automatic jobs which are started for a parent location affect all end devices residing in this location resp. in a child
location of this location. In detail, the following applies:
With automatic software deployment, rules in child locations take priority over rules in the corresponding
parent locations.
With automatic certificate deployment, the requested certificates are distributed to all IP Devices, both those
in the parent locations and those in all child locations.
With automatic archiving, all IP Devices are archived, both those in parent locations and those in child
locations.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-63
administration.fm
Administration
Server Configuration
Automatic Mobile User Logoff: Mobile Users belonging to the parent location including all its sub locations are
logged off.
With Plug&Play, virtual devices within a number pool are assigned to a location appropriate to their E.164
number.
With Plug&Play and multi tenancy, virtual devices within a number pool are assigned to a tenant appropriate
to their E.164 number.
For a location, the following items can be defined: FTP server, temporal software deployment restrictions, and an
infrastructure policy.
This area features the following components:
General Data
"Reg-Addresses" Tab
"Tenants" Tab
6-64
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
General Data
Name:
Location name.
Parent Location
Shows the parent location, if existant.
FTP Server:
FTP server for the location.
HTTPS Server:
HTTPS server for the location.
Network Drive:
Network drive for the location.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-65
administration.fm
Administration
Server Configuration
OSBranch path:
The path to the directory containing the phone software images provided by the OSBranch.
OSBranch port:
Port number for software deployment communication (phone software images) with the OSBranch.
Remark:
Remark.
Timezone:
Defines timezone for location. For possible values, please consult the choice list.
Info 1:
Additional optional Information of location, e.g. address information.
Info 2:
Additional optional Information of location, e.g. address information.
Info 3:
Additional optional Information of location, e.g. address information.
6-66
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
Remark:
Remark
FTP Server:
FTP server for the location.
HTTPS Server:
HTTPS server for the location.
Network Drive:
Network drive for the location.
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-67
administration.fm
Administration
Server Configuration
New
Creates a new data record for a location.
Save
Saves the field contents to the database.
Discard
Discards any changes entered.
Refresh
Updates the window using the database.
Export Location
Export the selected locations to a file in .zip format.
Import Location
Import locations from a file in .zip format.
6-68
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
IP Address from
Lowest value for the IP range associated with this location.
IP Address to
Highest value for the IP range associated with this location.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-69
administration.fm
Administration
Server Configuration
Reg-Address
IP addresses or host names of the PBX, gateway, or SIP server associated with this location.
6-70
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
E.164 Pattern
E.164 number pattern corresponding to this location. Regular expressions with the symbol * can be used.
Example: 4989722*.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-71
administration.fm
Administration
Server Configuration
Switch
Name of the switch at which the business group is configured.
BG Name
Name of the business group.
6-72
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
Infrastructure Policy
Location will be considered on infrastructure policy change for a device via DLSAPI or by means of the XML
application "Location Services".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-73
administration.fm
Administration
Server Configuration
Number Pool
Band of successive fully qualified E.164 numbers, which is defined by entering the first and last number.
Free Numbers
Number of E.164 call numbers from the pool which have not been assigned yet.
6-74
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
Whole day
Check box for activating the option to prevent software distribution on the specific day.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-75
administration.fm
Administration
Server Configuration
For parameter descriptions, see Section 6.3.2.7, ""SW Deployment Restrictions" Tab".
6-76
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
Tenant
Name of the tenant.
Remark
Information on the tenant.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-77
administration.fm
Administration
Server Configuration
General Data
6-78
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
General Data
Plug&Play enabled
When activated, Plug&Play is enabled for all devices.
Save
Saves the changes.
Refresh
Refreshes the screen contents from the database.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-79
administration.fm
Administration
Server Configuration
NOTE: When assigning templates to P&P profiles,all P&P profiles MUST have a SW version
assigned in order to have the respective masks available.
NOTE: For instance,under IP Devices > IP Phone Configuration > IP Routing> -"IPv6
Settings" Tab the IPv4 / IPv6 Protocol Mode can only be available in case the Device Type is
OpenStage and the SW version is V3 onward (please refer to Section 7.1.2.2, ""IPv6 Settings"
Tab")
NOTE: This also applies to all masks that are filtered by SW Version..
6-80
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
Windows account names are mapped to E.164 numbers to allow windows account / telephony number
association. DLS configuration of this mapping should be implemented through manual DLS UI configuration as
well as import & export of mapping data through .csv files in order to trigger DLS Plug & Play accordingly.
Import and export mapping data
Import
Mapping data are imported through a .csv formatted file.
Export
Mapping data are exported into a .csv formatted file.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-81
administration.fm
Administration
Server Configuration
General Data
"Tenants" Tab
6-82
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
General Data
Call: Main Menu > Administration > Server Configuration > FTP Server Configuration.
In this area, you can configure access data for one or more FTP servers. All FTP servers detected by the Search
routine are listed in Table view. Moreover, you can read all files which are existant on the FTP server and relevant
for IP devices into the DLS database. After this, the data are available for deployment.
For each file on the FTP server, one object per possible usage is created. For instance, a WAV file may be used
as ringtone or as hold music. If there is, for instance, a file named "notify.wav", the objects "notify.wav
(OpenStage,RINGTONE)" and "notify.wav (OpenStage,MOH)" would be created.
NOTE: The entries depend on the configuration of the FTP server in use at the time.
For more information on configuring FTP servers, see Section 4.12.1, "FTP Server".
An FTP server is necessary to load files to a device - phone software images or on-hold music, for example. You
must also configure at least one FTP server for the DLS to register the available phone software images.
NOTE: In contrast to IP phone software and files (which must be present on an FTP server), software
and files for IP clients are provided on a network drive and configured as described in Network Drive
Configuration.
6-83
administration.fm
Administration
Server Configuration
Hostname:
Host name or IP address of the FTP server (accessible by IP Devices).
Internal Hostname
If specified, this host name or IP address will be used for scan and SW check by the DLS.
Find the configuration files in which IP addresses and workgroup names are assigned to each other in:
C:\Windows\system32\drivers\etc\hosts
and add the IP address as well as the Internal Hostname of FTP Server to file (Host).
NOTE: Apply in all nodes of a Multi Node environment.
IP Protocol Mode
The FTP server is supporting this IP protocol version.
Possible options:
IPv4
IPv6
SW Image Path:
Path to the software image relative to the directory root of the FTP server. If the data is located directly in the
directory root, enter / (slash).
Port:
The default port number for FTP is 21 and cannot be changed.
User:
User name for read-only access to the FTP server. Read-only access is used by the IP Device to access the
software.
6-84
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
Password:
Password for read-only access to the FTP server. This entry is optional.
Status:
Status of s server action.
Possible values:
Scanning...
Finished
Stopped
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-85
administration.fm
Administration
Server Configuration
Start Scan
Start a search for software and data files on the FTP server. Entries concerning files which are not available on
the server will be deleted in the DLS database.
Stop Scan
Stop scanning the FTP Server for software and data files.
SW Path:
Directory path and file name.
Object Type:
Type of file.
Examples: Software Image, Logo File, Screen Saver.
Device Type:
Device type, for which the file is appropriate.
Examples: optiPoint 410, OpenStage Hi,OpenStage Lo, Wave Evolution Lo.
NOTE: OpenStage15 & OpenStage 40 devices are tagged commonly as 'OpenStage Lo'.
OpenStage 15 devices use the 'LO' device software category and have common firmware for OS15,
OS20 and OS40 devices.
NOTE: OpenScape Desk Phone IP 35G Eco devices are tagged commonly as 'Wave Evolution Lo'.
6-86
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
NOTE: During automatic Software (SW) deployment, DLS finds the matching firmware based on
family (HI or LO) and desired SW version. DLS will scan through the FTP list for the first available
firmware that meets the criteria and a valid match gets deployed. DLS deploys the correct firmware
(as far as OS15 and OS40 belong in the same family and have the same firmaware data) but the
shown used filename for the SW update may be misleading.
At manual SW deployment you get prompted to explicitly choose the firmware file to be deployed.
SW Type:
Type of the phone software.
Examples: Unify HFA, Unify SIP.
SW Version:
Version ot the phone software.
Status:
Status of the phone software.
Example: version info missing.
Valid
Activated if the file is valid.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-87
administration.fm
Administration
Server Configuration
Clear Window
Deletes the data entered in the window.
Save
Saves the data entered/modified.
Discard
Discards any changes made.
New
Creates a new FTP server.
Delete
Deletes the FTP server currently listed in Object view.
Refresh
Updates the field content using the database.
6-88
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
Scan all
All assigned FTP servers will be scanned. A progress bar shows the status of the current server scan. This scan
can be cancelled like a single scan by clicking the button Stop Scan.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-89
administration.fm
Administration
Server Configuration
Tenant
Name of the tenant.
Remark
Information on the tenant.
6-90
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
General Data
"Tenants" Tab
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-91
administration.fm
Administration
Server Configuration
General Data
Call: Main Menu > Administration > Server Configuration > HTTPS Server Configuration.
In this area, you can configure access data for one or more HTTPS servers. All HTTPS servers detected by the
search routine are listed in Table view.
An HTTPS server can be used instead of an FTP server to load data, such as, on-hold music or phone software
images onto an OpenStage device. You must also configure at least one HTTPS server for the DLS to register the
available phone software images.
NOTE: The entries depend on the configuration of the HTTPS server in use at a time.
NOTE: In contrast to the IP phone software that must be loaded on an HTTPS server, the software
for IP clients is provided on a network drive as described under Windows Network Drive Configuration.
HTTPS Server ID
Unique name used to address each HTTPS server configured.
Internal Hostname
If specified, this host name or IP address will be used for scan and SW check by the DLS.
Find the configuration files in which IP addresses and workgroup names are assigned to each other in:
6-92
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
C:\Windows\system32\drivers\etc\hosts
and add the IP address as well as the Internal Hostname of FTP Server to file (Host).
NOTE: Apply in all nodes of a Multi Node environment.
IP Protocol Mode
The HTTPS server is supporting this IP protocol version.
Possible options:
IPv4
IPv6
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-93
administration.fm
Administration
Server Configuration
Status:
Status of s server action.
Possible values:
Scanning...
Finished
Stopped
Start Scan
Start a search for software and data files on the HTTPS server. Entries concerning files which are not available on
the server will be deleted in the DLS database.
Stop Scan
Stops scanning the HTTPS Server for software and data files.
Clear Window
Deletes the data entered in the window.
New
Creates a new HTTPS server.
Save
Saves any unsaved changes.
6-94
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
Discard
Discards any unsaved changes.
Test
Tests the connection to the current HTTPS server configured. The result is displayed in the status window.
Scan all
All assigned HTTP servers will be scanned. A progress bar shows the status of the current server scan. This scan
can be cancelled like a single scan by clicking the button Stop Scan.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-95
administration.fm
Administration
Server Configuration
SW Name:
Name of the file.
SW Path:
Directory path and file name.
Object Type:
Type of file.
Examples: Software Image, Logo File, Screen Saver.
Device Type:
Device type, for which the file is appropriate.
Examples: optiPoint 410, OpenStage Hi.
SW Type:
Type of the phone software.
Examples: Unify HFA, Unify SIP.
6-96
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
SW Version:
Version ot the phone software.
Status:
Status of the phone software.
Example: version info missing.
Valid
Activated if the file is valid.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-97
administration.fm
Administration
Server Configuration
None
No authentification of server. Invalid certificates, which are received before by server or has been loaded by
IP Phone, will be ignored. HTTPS connections to server are setup without authentications allways.
Trusted
Certificates are checked for "expired", "not valid", "signed by trusted CA", and "revoked". Therefore one or two
list of "trusted CAs" are required. The same list will be used for "trusted" and "full". As "trusted CAs" may be
used RootCAs, temporary created CAs, or even the server-certificate itself. Additional values, such as owner
or issuer are not checked. HTTPS connections to server are setup even if some values of the certificate are
incorrect.
Full
Certificates are checked for "expired", "not valid", "signed by trusted CA", "revoked", matching owner and so
on. Therefore one or two list of "trusted CAs" are required. The same list will be used for "trusted" and "full".
As "trusted CAs" may be used RootCAs, temporary created CAs, or even the server-certificate itself. HTTPS
connections to server are setup only, if valid and correct certificates are available.
Index
Index of certicate.
6-98
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
Serial Number:
Serial number of the certificate (display only).
Owner:
Owner of the certificate (display only).
Issuer:
Issuer of the certificate (display only).
Valid from:
Start of validity for the certificate (display only).
Valid to:
End of validity for the certificate (display only).
Key Algorithm
Key Algorithm of the certificate (display only).
Key Size
Key Size of the certificate (display only).
Fingerprint (SHA-1):
Test algorithm SHA-1 (160 bits/20 characters) of the certificate (display only).
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-99
administration.fm
Administration
Server Configuration
NOTE: The value of the imported certificate is updated periodically dependent on the settings in
Administration > Alarm Configuration > "Settings" Tab > Alarm Configuration for Expiring
Certificates > Interval. Therefore it might be greater than the value of the active certificate until the
next update.
Alarm Status
Current alarm status of the certificate (display only).
Possible values:
valid
expired
6-100
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
Serial Number
Serial number of the certificate (display only).
Owner
Owner of the certificate (display only).
Issuer:
Issuer of the certificate (display only).
Valid from:
Start of validity for the certificate (display only).
Valid to:
End of validity for the certificate (display only).
Key Algorithm:
Key Algorithm for certificate (display only).
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-101
administration.fm
Administration
Server Configuration
Key Size:
Key Size for certificate (display only).
Fingerprint (SHA-1):
Test algorithm SHA1 (160 bits/20 characters) for certificate (display only)
6-102
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
Tenant
Name of the tenant.
Remark
Information on the tenant.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-103
administration.fm
Administration
Server Configuration
General Data
6-104
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
General Data
Call: Main Menu > Administration > Server Configuration > HTTPS Client Configuration.
This item allows to import and display certificates of the HTTPS Client Configuration.
Serial Number:
Serial number of the certificate (display only).
Owner:
Owner of the certificate (display only).
Issuer:
Issuer of the certificate (display only).
Valid from:
Start of validity for the certificate (display only).
Valid to:
End of validity for the certificate (display only).
Key Algorithm
Key Algorithm of the certificate (display only).
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-105
administration.fm
Administration
Server Configuration
Key Size
Key Size of the certificate (display only).
Fingerprint (SHA-1):
Test algorithm SHA-1 (160 bits/20 characters) of the certificate (display only).
Alarm Status
Current alarm status of the certificate (display only).
Possible values:
valid
expired
Search
Searches the database for HTTPS servers already configured.
Clear Window
Deletes the data entered in the window.
6-106
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
Import Certificate
Starts the import of HTTPS Client Certificate.
Synchronize Keystore
Starts synchronization of keystore.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-107
administration.fm
Administration
Server Configuration
General Data
"Tenants" Tab
6-108
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
General Data
In this area, you can configure one or more network drives.
NOTE: Deployment via a network drive is not available in the onboard variants of DLS on
OpenScape Voice systems.
NOTE: The information here is only necessary for the distribution of IP client software. Access to the
software for IP phones is via FTP/HTTPS. The server is configured in the FTP Server Configuration
or HTTPS Server Configuration area.
Authorizations for accessing the network release must be set on the [DLS server name]\system to
guarantee access for the DLS Web server running by default as the service.
If these authorizations cannot be extended or if the authorizations for access to the network releases
are limited to a user group, then you must ensure that the DLS runs in the user context that is also
included in this user group or that can access this network release.
The user context can be modified as follows (Windows XP, for example):
Start > Settings > Control Panel > Administrative Tools > Services > DeploymentService >
[right-click] Properties > Log On tab.
Enter the data necessary for the Windows network drive.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-109
administration.fm
Administration
Server Configuration
Internal Path
If specified, this path will be used for scan by the DLS.
Status:
Status of s server action.
Possible values:
Scanning...
Finished
Stopped
Start Scan
Start a search for software and data files on the network drive. Entries concerning files which are not available on
the server will be deleted in the DLS database.
Stop Scan
Stops scanning the network drive for software and data files.
SW Path:
Directory path and file name.
6-110
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
Object Type:
Type of file.
Examples: Software Image, Logo File, Screen Saver.
Device Type:
Device type, for which the file is appropriate.
Examples: optiPoint 410, OpenStage Hi.
SW Type:
Type of the phone software.
Examples: Unify HFA, Unify SIP.
SW Version:
Version ot the phone software.
Status:
Status of the phone software.
Example: version info missing.
Valid
Activated if the file is valid.
Discard
Discards any changes made.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-111
administration.fm
Administration
Server Configuration
New
Creates a new network drive.
Delete
Deletes the network path currently listed in Object view.
Refresh
Updates the field content using the database.
Scan all
All assigned network drives will be scanned. A progress bar shows the status of the current scan.
This scan can be cancelled like a single scan by clicking the button Stop Scan.
6-112
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
Tenant
Name of the tenant.
Remark
Information on the tenant.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-113
administration.fm
Administration
Server Configuration
General Data
6-114
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
General Data
Infrastructure Policy:
Name of the infrastructure policy.
Description:
Description of the infrastracture policy.
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
New
Creates a new data record for IP infrastructure policies.
Save
Saves the field contents to the database.
Discard
Discards any changes entered.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-115
administration.fm
Administration
Server Configuration
Refresh
Updates the window using the database.
Apply
Applies IP infrastructure table to already existing IP Devices.
6-116
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
Priority:
The matching policy will be assigned according to the priority entered here.
Switch IP address:
IP address of the switch where the IP Phone is plugged in.
Regular Expressions may be used.
Switch Port:
Port number of the switch where the IP Phone is plugged in.
Regular Expressions may be used.
Network Policy:
Network Policy assigned to IP Phone.
Regular Expressions may be used.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-117
administration.fm
Administration
Server Configuration
Notification Type
Type of notification.
Possible values:
inventoryInfo
New IP Phones and E.164 changes will be notified.
serverStart
Notification on DLS server start.
Address
Target IP address for notification.
6-118
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
Port
Target port for notification.
Protocol
Protocol used for notification: UDP.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-119
administration.fm
Administration
Server Configuration
General Data
"MakeCall" Tab
6-120
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
General Data
DLS Address
IP address of the DLS, or, in a Multinode installation, the IP address of the DLS cluster.
Trace Level
Trace Level for XML Applications which are running as self-contained web applications. The trace data are stored
under
<Installation directory>\Tomcat5\webapps\XMLApplications\log\
dlsXMLAppsLog.txt
Possible Options:
ERROR
INFO
DEBUG
Save
Saves the field contents to the database.
Refresh
Updates the window using the database.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-121
administration.fm
Administration
Server Configuration
6-122
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-123
administration.fm
Administration
Server Configuration
Authentication
Select a password to execute this XML application.
Possible options:
6-124
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
Display Name:
This name is shown on the end device display for the XML application NewsService if it has been automatically
deployed.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-125
administration.fm
Administration
Server Configuration
Display Name:
This name is shown on the end device display for the XML application MakeCall if it has been automatically
deployed.
6-126
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
6.3.11 Options
Call: Main Menu > Administration > Server Configuration > Options
Search
Limit of Search Results
Maximum number of records displayed when a search is done.
NOTE: Changed values first will be used not until the DLS Client has been restarted.
IP Device Trash
Delete IP Devices from Trash after Days
Number of days after which IP Devices marked to be deleted will be deleted completely from the DLS database.
Default value : 31 days
Value range: 1 ... 365
NOTE: If you set it to zero ( 0 ), it changes the value to default as soon as you hit the save button
or mark another field.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-127
administration.fm
Administration
Server Configuration
NOTE: In OpenStage v3 onward, the password for mobile users is send using hash values.Therefore
the DLS is not able to display anything in the password field when the Refresh button is used.
The password is not lost,is just not visible in the DLS graphic user interface.
Save
Saves the changes.
6-128
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
Refresh
Refreshes the screen contents from the database.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-129
administration.fm
Administration
Server Configuration
6-130
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
Remove Certificate
Removes certificate. When clicking the button, a window pops up to select certificate type.
Refresh
Updates the window using the database.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-131
administration.fm
Administration
Server Configuration
Serial Number:
Serial number of the certificate (display only).
Owner:
Owner of the certificate (display only).
Issuer:
Issuer of the certificate (display only).
Valid from:
Start of validity for the certificate (display only).
Valid to:
End of validity for the certificate (display only).
Key Algorithm
Key Algorithm.
6-132
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
Key Size
Key Size.
Fingerprint (SHA-1):
Test algorithm SHA-1 (160 bits/20 characters) for the security certificate.
Alarm Status
Current alarm status.
Possible values:
valid
expired
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-133
administration.fm
Administration
Server Configuration
Index
Index of the TLS connector.
For further parameter description, see chapter Section 6.3.12.1, ""DLS Client GUI" Tab".
6-134
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Configuration
For further parameter description, see chapter Section 6.3.12.1, ""DLS Client GUI" Tab".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-135
administration.fm
Administration
Server Configuration
Index
Index of TLS Connector.
For further parameter description, see chapter Section 6.3.12.1, ""DLS Client GUI" Tab".
6-136
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Cluster Configuration
Deployment Server
Cluster Settings
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-137
administration.fm
Administration
Cluster Configuration
General Data
"Info" Tab
6-138
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Cluster Configuration
General Data
Hostname:
Name of the node within the cluster.
Address:
IP address, domain, or host name of the DLS.
Remark:
Field for general information.
Port:
Port of the DLS.
DCMP-Port:
Port of the DCMP (DLS Communication Management Proxy).
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-139
administration.fm
Administration
Cluster Configuration
Save
Saves the field contents to the database.
Discard
Discards any changes entered.
Refresh
Updates the window using the database.
New
Creates a new cluster node.
Delete
Deletes one or more nodes (multiple selections possible in Table view).
Deployment Service
Opens a dialog window to start, stop or restart the Deployment Service at the selected node.
6-140
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Cluster Configuration
Last Registration
Last time the node registered at the cluster.
Status
Status of the node within the cluster.
Possible values:
Active
The node is active.
Inactive
The node has either logged itself on as inactive or was recognized as inactive by other nodes in the cluster.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-141
administration.fm
Administration
Cluster Configuration
Failover Partner
IP address of the mirroring instance for the DLS database.
6-142
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Display Logging Data
Alarm Protocol
Alarm List
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-143
administration.fm
Administration
"Configuration" Tab
"Protocol" Tab
6-144
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Display Logging Data
Discard
Discards any changes entered.
Refresh
Updates the window using the database.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-145
administration.fm
Administration
Logging-Level
Check box for activating logging.
Logging off
Check box for deactivating logging.
Activities
All DLS activities must be logged in the Activities log.
Account Activities
All account activities must be logged in the Account Activities log.
Errors
The Errors log only records failed actions and internal errors, such as, license violations or SQL database errors.
6-146
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Display Logging Data
Logging-Level
Activities
All DLS activities must be logged in the Activities log.
Account Activities
All account activities must be logged in the Account Activities log.
Error
The Errors log only records failed actions and internal errors, such as, license violations or SQL database errors.
Date:
Period of time during which the log data should be displayed (for a calendar, see Section 5.4.2.4, "Time field with
calendar button").
Protocol
Starts outputting logging data. The filtered data is displayed in a separate browser window.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-147
administration.fm
Administration
"Configuration" Tab
"Protocol" Tab
6-148
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Display Logging Data
Save
Saves all settings made. Not applicable for the "Protocol" Tab.
Refresh
Updates the window using the database.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-149
administration.fm
Administration
6-150
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Display Logging Data
Date
Log data that has been created in the time period specified here will be displayed.
Audit Log
Button to start the display of DLS audit log data.
Security Log
Button to start the display of DLS security log data.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-151
administration.fm
Administration
For information on general interface operation, see Section 5.4.2, "Work Area".
NOTE: The Object view is only available per tennant.Therefore the ALL option shall not bring any
results.
Maximum number of Protocols:
The maximum number of protocols created when importing Plug&Play data.
Value range: 1 ... 40.
Date
Protocol creation date.
Protocol
Plug&Play import protocol.
6-152
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Display Logging Data
Date/Time
Date/Time at which the action has started.
Alarm Class
Alarm class of the alarm.
Type
Type of alarm.
State
State of the action.
Possible Options:
running
pending
finished
failed
timeout
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-153
administration.fm
Administration
Protocol
Protocol of the execution.
6-154
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Display Logging Data
Discard
Discards any unsaved changes.
Refresh
Refreshes the content of the relevant page.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-155
administration.fm
Administration
DLS shall display a list with the DLS alarms that are stored in DLS Database. When an alarm condition occurs
(log event), a new entry shall be added in the Database.
Date/Time
Date/Time at which the action has started.
Alarm Class
Alarm class of the alarm.
State
State of the action.
Possible Options:
active
The state is active when the alarm condition exists.
cleared
The state is cleared when the alarm condition is disappeared.
Protocol
Protocol of the execution.
6-156
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Display Logging Data
Delete
Offers the capability to remove an alarm from the list. DLS shall clear the alarm and then shall remove it from the
Database.
Clear Alarm
Offers the capability to change the status of an alarm from active to cleared.
DLS shall update the alarm status in the Database and also send clear trap for this alarm in the configured SNMP
destinations.
If an alarm is raised (and displayed) more than once and you press the Clear Alarm option then the Alarm Status
should go from active to cleared in all rows.
Refresh
Refreshes the content of the alarm list.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-157
administration.fm
Administration
Alarm Configuration
General Data
"Notification" Tab
"SNMP" Tab
"Email" Tab
Syslog Tab
"Settings" Tab
For information on general interface operation, see Section 5.4.2, "Work Area".
6-158
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Alarm Configuration
General Data
SNMP Trap
When active, an SMNP trap is sent to the server determined in the "SNMP" Tab, depending on the individual
settings in the "Alarm Classes" Tab.
Email:
When active, an Email is sent using data specified in the "Email" Tab, depending on the individual settings in the
"Alarm Classes" Tab.
Syslog:
When active, the alarm will be added to systemlog file, depending on the individual settings in the "Alarm Classes"
Tab.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-159
administration.fm
Administration
Alarm Configuration
Discard
Discards any unsaved changes.
Refresh
Refreshes the content of the relevant page.
6-160
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Alarm Configuration
Index
Index for the alarm action to be triggered (notification, batch file, SNMP trap, or Email).
Notification
If this check box and the Notification to DLS Users check box in the General Data area are activated, the DLS
users listed in the "Notification" Tab are notified according to this alarm class.
SNMP Trap
If this check box as well as the check box SNMP Trap under General Data is active, the SNMP trap will be sent
to the receiver configured for this alarm class.
Batch File
If this check box and the Batch file execution check box in the General Data area are activated, the configured
command file for this alarm class is executed.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-161
administration.fm
Administration
Alarm Configuration
Email
If this check box and the Email check box in the General Data area are activated, the configured e-mail for this
alarm class is executed.
Alarm Class
Functional area within which an alarm shall be triggered in case of an error. The list cannot be modified; it depends
on the startup settings of the DLS.
Possible values:
DLS Service
DLS Cluster
License Alarm
SIP Mobility
Certificate Expiration
Policy Alarm
An alarm is triggered when an error occurs in policy settings, please refer to Section 6.1.2, "Policy Settings" .
Resource Alarm
Corresponds with the threshold Minimum free space under Administration > File Server.
DCMP
i.e,dcmp configuration error, DLS or phone wise.
DLS Cluster
Resource Alarm
Corresponds with the threshold Minimum free space under Administration > File Server.
IP Device Communication
An alarm is triggered when an error occurs in IP Device interaction / management
6-162
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Alarm Configuration
PKI
i.e,PKI configuration error.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-163
administration.fm
Administration
Alarm Configuration
Language
The language of the text in the notification alarm.
Possible options:
German
English
Account
The DLS user accounts which shall be notified by the alarms selected in the "Alarm Classes" Tab are entered here.
Test
Tests the notification. The result of the test can be checked under Administration > Display Logging Data >
Alarm Protocol.
6-164
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Alarm Configuration
Language
Language of the description text for the SNMP trap.
Possible Options:
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-165
administration.fm
Administration
Alarm Configuration
German
English
Test
Sends a test SNMP trap. The result of the test can be checked under Administration > Display Logging Data
> Alarm Protocol.
SNMP Host
Name of the SNMP Server (manager).
Port
Port of the SNMP server (manager).
Default: 162
Community
Community / password for the SNMP server (manager).
6-166
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Alarm Configuration
Language
The language of the alarm message text.
Possible options:
German
English
Batch File:
Path and name of the batch file which is executed when an alarm is triggered. After DLS installation, the path and
file name reference a sample file which also contains rules for creating a command.
Test
Tests the execution of the batch file. The result of the test can be checked under Administration > Display
Logging Data > Alarm Protocol.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-167
administration.fm
Administration
Alarm Configuration
Language
The language of the alarm message text.
Possible options:
German
English
Test
Tests the Email send operation using the account data entered. The result of the test can be checked under
Administration > Display Logging Data > Alarm Protocol.
Account:
Name of the Email account.
Password:
Password for this Email account.
6-168
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Alarm Configuration
Email Server:
Name of the SMTP server that is to be used for alarm Emails.
Port:
Port number of the SMTP server. If no value is entered, port 25 is used by default.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-169
administration.fm
Administration
Alarm Configuration
Port
Portnumber of Syslog Server
Facility
Possible options:
local0
local1
local2
local3
local4
local5
local6
local7
Severity
Setting of Trace Level
Possible options:
6-170
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Alarm Configuration
emerg
alert
crit
error
warning
notice
info
debug
none
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-171
administration.fm
Administration
Alarm Configuration
Interval: [hours]
The remaining certificate validity period is checked in the interval specified here.
Value range: 1 - 60.
Default value: 6
6-172
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Alarm Configuration
Notification Settings
Alarm Icon:
Choice list of icons for notifying the DLS user of alarms which are not closed yet. The icon is displayed in the title
bar of the DLS window.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-173
administration.fm
Administration
Backup/Restore
6.7 Backup/Restore
Call: Main Menu > Administration > Backup/Restore
NOTE: This function is not available in the onboard variants of DLS on OpenScape Voice systems.
In this case, the DLS file is backed up using the comprehensive OpenScape Voice Backup/Restore
function.
This area features the following components:
General Data
"Backup" Tab
"Restore" Tab
"Protocol" Tab
For information on general interface operation, see Section 5.4.2, "Work Area".
Refer to Section 15.9.1, "Automatic Data Backups" for more information on Backup/Restore.
6-174
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Backup/Restore
General Data
Backup Path:
File path where the backup is saved on the DLS server. If the DLS uses a remote database for its data, a directory
path on the database server must be entered. It must be reachable by the DLS server. The format must also be
usable locally on the database server, e. g.
\\<IP-Address DB Server>\C$\<Backup Pfad on DB Server on drive C>
Browse...
Click this button to open a dialog window that you can use to select an existing backup directory. To navigate to
the subdirectories of a directory, double click on the directory name. To navigate up to the next higher directory
level, double click on "..\". In order to select a directory, highlight it with a single click and, afterwards, click Open.
Test
Click Test to verify that the path is valid (accessible).
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-175
administration.fm
Administration
Backup/Restore
NOTE: The .trn files are the backup transaction log files,useful when the recovery transaction model
of the database is either full or bulk-logged.The backup of the transaction logs is different than the
backup of the database.Transaction logs not only contain all the transaction SQL command requests
issued to the database but also differences in data (i.e. tables,indexes).
NOTE: Since the transaction logs contain data changes,it is reasonable to see big differences in the
transaction log backup file sizes, even in small time frames.Also,when a transaction log is backed up
the backed up transaction log entries are deleted.That is why, if after a transaction log backup you
attempt another one,the backup file size will be very small compared to the first one.
6-176
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Backup/Restore
Discard
Discards any unsaved changes.
Refresh
Refreshes the content of the relevant page.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-177
administration.fm
Administration
Backup/Restore
6-178
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Backup/Restore
Backup File:
Path and file name for restoring a backup on the DLS server. If backups have already been successfully restored,
you can enter them using the choice list.
Browse...
Click this button to open a window where you can select an existing backup file. The path and file name are
entered in Backup File.
NOTE: In a Multi Node environment,if you press this button and browse for a backup path that is
situated locally in Node 1 or Node 2 then the selected path is connected to the IP address of the 1st
Ethernet Interface of the DLS server.
If the 1st interface happens to be that of the external (or frontend network), the DB restore will fail as
DLS cannot contact SQL server through that interface.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-179
administration.fm
Administration
Backup/Restore
NOTE: DLS can contact SQL server only through the internal (backend) network interface and this
cannot stated explicitly if the path is chosen by the 'Browse...' button.
Test
Click this button to verify that the backup file is valid (accessible).
Restore
When you click this button, a restore is executed. A dialog window will ask whether Plug&Play is to be switched
off after restore or not. If Plug&Play has been switched off, it is possible to switch it on again via Administration
> Server Configuration > P&P Settings > Plug&Play enabled. Beforehand, it must be ensured that all
IP devices are registered in the DLS database.
This does not use the backup file stored in the database, but the current backup file as it appears in the mask
(which may have changed and not yet been saved).
NOTE: When database mirroring (see Section 4.6, "SQL Database Mirroring Setup") is active, no
restore of backups is possible.
NOTE: There are some basic server configuration data which will never be restored as e.g.
- the base configuration
- the license settings
in order to guarantee a proper operation after any restore.
NOTE: During a restore, all users are momentarily disconnected from the DLS database as the
restore process requires exclusive access to the database. These users must log on again.
6-180
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Backup/Restore
Date/Time
Backup time.
Backup File
Backup file name.
Duration
Duration of the backup process in hours, minutes, and seconds.
Size
Size of the backup file in bytes.
Status
Status of the backup/restore.
Possible values:
Backup OK
Backup failed
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-181
administration.fm
Administration
Backup/Restore
deleted
Restore OK
Restore failed
6-182
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
File Server
IP Devices
Mobile Users
Profile Management
Backup/Restore
Protocol Files
Credentials
Mobility Statistics
XML Applications
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-183
administration.fm
Administration
File Server
Database File
Shows the path where the DLS database is stored. The network name is relative to the SQL server and cannot
be changed by means of this mask. Available only on systems with Microsoft SQL Server as database.
HD 01 / Mount 01
Shows either necessary devices with system data (on Linux based systems) or all available or mounted
devices (on Windows based systems). The network path cannot be changed by means of this mask.
...
HD 20 / Mount 20
Shows either necessary devices with system data (on Linux based systems) or all available or mounted
devices (on Windows based systems). The network path cannot be changed by means of this mask.
Network Path
Network path or local folder for saving DLS data.
Example: \\MyFileServer\DlsFiles\Protocols
Remark
Field for general information.
Memory Capacity
Displays the overall memory capacity of this network drive in gigabytes.
Free Space
Displays the available space on this network drive in megabyte. If this value is lower than the Minimum Free
Space, this field is marked with a yellow border.
6-184
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
File Server
Acquisition Time
Date and time of acquisition of the additional information about Memory Capacity [GB] and Free Space [MB].
These values are stored once a week; the entries cannot be deleted.
Only available in object view, cannot be changed or deleted.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-185
administration.fm
Administration
"DCMP" Tab
"HTTP-Proxy" Tab
For information on general interface operation, see Section 5.4.2, "Work Area".
6-186
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Workpoint Interface Configuration
Discard
Discards any unsaved changes.
Refresh
Refreshes the content of the relevant page.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-187
administration.fm
Administration
NOTE: For smooth secure mode operation, please ensure that the time and date on the OpenStage
phone conforms with that on the DLS.
NOTE: Factory Reset with Plug&Play data stored is not possible in Secure Mode. The according IP
Devices must be revert to Default Mode first.
PIN
Default PIN:
PIN created automatically by DLS to allow encrypted transfer of server credentials to the IP Device. This PIN is
used by IP Devices with the "Default PIN" mode.
Generate PIN
If this check box is activated and you click Save, DLS creates a new default PIN. This PIN or, optionally, an
individual PIN must be entered at the IP Device to decrypt the server credentials delivered by DLS. The PIN is
used by IP Devices with Insecure security status.
6-188
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Workpoint Interface Configuration
TAN Verification:
TAN (Targets Authentication Number) is the last 3 characters of PIN to be used by provisioning service to
authenticate the target device in Secure Mode.
Possible Options:
False
True
TAN Verification can only be performed if TAN is required. If the IP Device has sent a TAN, but the current
configuration does not require one, then the TAN cannot be verified.
Trusted
Full
Server Credentials
PKI Configuration
Selects the PKI Configuration for the server credentials to be activated. See also Section 6.2, "PKI".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-189
administration.fm
Administration
NOTE: WPI credentials cannot be created if PKI connector defines "Common Name or "Subject
Alternative Name" with MAC. This is not supported.
Number of devices:
In Security state SECURE:
Number of devices in the SECURE security status.
Active
Displays whether a server credential is active or inactive. The DLS always authenticates itself on a device in
secure mode using the active server credential.
A maximum of one additional server credential can be created in preparation for exchanging the active server
credential.
PKI Configuration
Shows name of the active PKI configuration.
Valid From
Credential start of validity.
Valid To
Credential end of validity.
6-190
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Workpoint Interface Configuration
Serial Number
Corresponding CA certificate serial number.
Owner
Credential's owner.
Issuer
Credential's issuer.
Fingerprint (SHA-1)
This fingerprint (hash value) uniquely identifies the credential (also in different DLS entities).
The fingerprint is part of the name of the export file (see also the Export field).
Key Algorithm
Credential's key algorithm.
Key Size
Credential's key size.
Create
Creates an additional (inactive) server credential. Only one additional server credential may be created.
A PKI configuration has to be enabled and selected (an internal connector is by default enabled). If an MS PKI
connector shall be used, then an activation of PKI Configuration is needed). After selecting PKI configuration to
be used, a new trust anchor is imported from the trust anchor configuration. The DLS will also request a new server
certificate for its own TLS connector used for WPI communication.
Deploy
Deploys the additional server credential to all devices already in secure state.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-191
administration.fm
Administration
The new trust anchor used by WPI clients to authenticate the DLS, will be deployed to them. One job for each
device in secure state will be initiated.
Activate
Activates the additional (inactive) server credential in the DLS (thus the TLS connector may perform a restart using
the new additional credential). When activation is complete, DLS queries are denied by all devices to which trust
anchor relative to this credential has not yet been sent.
Delete
Deletes the additional (inactive) server credential.
Client credentials
PKI Configuration
Shows the PKI configuration of client credentials.
Number of devices:
Using ACTIVE client credential:
Number of (secure) devices that identify themselves using the active client credential.
6-192
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Workpoint Interface Configuration
Active
Displays whether a client credential is active or outdated.
There is always exactly one active client credential. DLS also accepts devices that authenticate themselves using
an outdated client credential. In this case, the device is automatically sent the current active client credential. The
next time, it authenticates itself using the active client credential.
PKI Configuration
Shows name of the active PKI configuration.
Valid From
Credential start of validity.
Valid To
Credential end of validity.
Serial Number
Corresponding CA certificate serial number.
Owner
Credential's owner.
Issuer
Credential's issuer.
Fingerprint (SHA-1)
This fingerprint (hash value) uniquely identifies the credential (also in different DLS entities).
The fingerprint is part of the name of the export file (see also the Export field).
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-193
administration.fm
Administration
Key Algorithm
Credential's key algorithm.
Key Size
Credential's key size.
Create
Creates a new client credential. This new client credential is automatically activated and the client credential
previously active is deactivated and becomes outdated. When a new client credential is created, it is sent to all
devices.
NOTE: The Create button does not trigger a deployment to all devices. Devices in secure state
will get new client credentials, as soon as they contact DLS.
IMPORTANT: In the case where the phone is unplugged from the network,then if the re-plugging is
done quick enough, the job finishes successfully. If the time gap exceeds the job expiration frame
(default value is 300 sec), the job for sending the credentials expires. In any case, the phone is
deployed with new wpi certificates (as indicated in Section 7.5.4, "IP Device Configuration")
Even if the job is manually cancelled, the phone will still get the certificate if it gets to contact DLS for
other reason (e.g. reboot).
Delete
Deletes all inactive (outdated) client credentials. When the outdated client credentials have been deleted, DLS no
longer accepts devices that identify themselves using an outdated client credential.
6-194
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Workpoint Interface Configuration
Export
Exports client and server credentials to a password-protected file.
NOTE: The password is not intended for the zip archive format file but for the files contained in the
zip file( WPI credentials).
NOTE: Import & Export functionality on WPI shall be used only in order to contact phones already in
secure mode
IMPORTANT: in the case of an upgrade of a past DLS version that did not have the present PKI
implementation in place (for credentials older than v6.0 version) the fields are empty.That occurs
since these files were not existing and as a result stay empty. This display information was not
provided in older versions.PKI Configuration is not an applicable field for older credentials.Some of
the display info is not applicable.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-195
administration.fm
Administration
Toggle DCMP
Switches DCMP activation and creates jobs for affected devices.
DLS-DCMP connection
DLS-DCMP Host:
Host name or IP address of the DCMP server. The DCMP server host must be reachable for DLS.
6-196
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Workpoint Interface Configuration
DLS-DCMP HTTP-Port:
DCMP servers HTTP port for connecting DLS and DCMP.
Password:
Password for DLS access to the DCMP server.
Test
Tests the connection between DLS and the DCMP server using the current values stored for host, port, and
password. When you change these values, you must save the changes before testing the DLS connection.
Device-DCMP connection
Device-DCMP Host:
Host name or IP address of the DCMP server. The DCMP server host must be reachable for devices activated by
DCMP. In contrast to the DCMP-DLS connection, do not use "localhost" or "127.0.0.1" as the DCMP server host
when both are running on the same host.
Device-DCMP HTTP-Port
DCMP servers HTTP port for connecting telephones and DCMP.
Device IP Ranges
IP Address from:
Lower limit of IP addresses that are administered by DCMP.
IP Address to:
Upper limit of IP addresses that are administered by DCMP
Poll Interval:
The time between two consecutive polls at DCMP (in minutes).
The entered value must be lower than the value for Section 7.4.6.2, "Timeout (sec)"
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-197
administration.fm
Administration
Possible options:
0 - 1440, default: 60 minutes
6-198
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Workpoint Interface Configuration
DLS-Device Connection
HTTP-Proxy active (to send HTTP-Requests to IP Devices)
If this checkbox is active, an HTTP proxy is used to send HTTP requests from the DLS to IP Devices.
Autocorrection of Device-IP
Automatic correction of the devices IP address with the request address (only if HTTP-Proxy is enabled). In case
an HTTP proxy is used, this option is deactivated at first in order to avoid that the IP address of the devices is
replaced with the IP address of the HTTP proxy. It is recommended not to activate this switch.
HTTP-Proxy Host
IP address or DNS name of the HTTP proxy to be used for sending HTTP requests from the DLS to the IP Devices.
HTTP-Proxy Port
Port of the HTTP proxy used to send HTTP requests from the DLS to IP Devices.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-199
administration.fm
Administration
DLS Client Certificate for TLS connections with Contact Me Notify Servers
Serial Number
Serial number of the certificate (display only).
Owner
Owner of the certificate (display only).
6-200
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Workpoint Interface Configuration
Issuer
Issuer of the certificate (display only).
Create Certificate
Create automatically a client certificate using the internal root CA of DLS.
Import Certificate
Import a PKCS #12 file that will be used by DLS as client certificate.
Export Certificate
Export the public certificate of the installed client certificate that has to be configured as trusted in OSV.
Address of node 1
IP address or FQDN of the admin interface of the first node.
The IP address must be unique.
Address of node 2
IP address or FQDN of the admin interface of the first node.
The IP address must be unique.
Transport Type
Specify the transport type.
Possible values:
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-201
administration.fm
Administration
TCP
TLS
Port
Specify the SOAP server port.
Possible values (Transport Type :TCP)
8767
8768
8769 (default)
8770
8757
8758
8759 (default)
8760
Serial Number
Serial number of the certificate.
Owner
Owner of the certificate.
Issuer
Issuer of the certificate.
Valid from:
Start of the validity for the certificate.
6-202
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Workpoint Interface Configuration
Valid to:
End of validity for the certificate.
Fingerprint
Test algorithm SHA-1 (160 bits/20 characters) of the certificate.
Key algorithm
Key algorithm of the certificate.
Key size
key size of the certificate.
Expires in...[days]
Certificate will expire in ... days of the certificate.
Alarm Status
Current alarm status of the certificate.
Possible values:
Valid
Expired
Test Connection
Test the connection between DLS and the configured OSV servers.
A Test Connection dialog shall appear via which you will be allowed to select one Contact Me Notify server to test
the connection. A simple GetVersion request will be sent as a connection test.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-203
administration.fm
Administration
Import Certificate
Import a server certificate that will be used by DLS for the server authentication of the OSV during TLS handshake.
NOTE: When DLS receives the server certificate from OSV, DLS must validate the server certificate
that has been received against the server certificate that has been imported into DLS database as
trusted.
Remove Certificate
Remove an installed certificate from a configured Contact Me Notify server. Note that if there is not installed
certificate, this operation will fail because there is no installed certificate to remove.
NOTE: If there is no installed certificate, the operation will fail.
Device IP Ranges
IP Address from:
Lowest value for the IP range (IPV4 or IPV6) associated with this location.
IP Address to:
Highest value for the IP range (IPV4 or IPV6) associated with this location.
NOTE: Any IP devices within the IP ranges defined by IP Address from and IP Address to will be
updated via the associated Contact Me Notify SIP server. The device IP ranges must not overlap with
the other device IP ranges that are defined to use the Contact Me Notify mechanism or DCMP.
Contact Me Notify Server Name
The mnemonic name of a configured Contact me Notify server that will be used as intermediate node whenever
a changed is made to an IP device within the configured IP range.
6-204
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Automatic SPE Configuration
General Data
"Settings" Tab
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-205
administration.fm
Administration
General Data
PKI Configuration
Select PKI configuration.
Possible Options:
6-206
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Automatic SPE Configuration
autoSPE Jobs
Job ID (Deploy CA)
For the deployment of CAs, a job is started. A unique job ID is assigned to this job in order to identify it. Via this
field, it is possible to jump to the job control (see Section 14.1, "Job Control") to control the status of the job.
Job ID (Activate)
For the activation of CAs, a job is started. A unique job ID is assigned to this job in order to identify it. Via this field,
it is possible to jump to the job control (see Section 14.1, "Job Control") to control the status of the job.
Cancel Job
With this button, the particular job can be canceled.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-207
administration.fm
Administration
autoSPE Credentials
Status
Displays the status of the credential.
Possible values:
created
deployed
activated
phase-out
PKI Configuration
PKI configuration.
Valid from
Start date of credential validity.
Valid to
Expiry date for new autoSPE credentials (possible maximum duration until 12/31/2037).
Serial number
Serial number for the CA certificate.
Owner
Owner of the credential.
Issuer
Issuer of the credential.
6-208
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Automatic SPE Configuration
Key Algorithm
Key Algorithm.
Key Size
Key Size.
Fingerprint (SHA-1)
The fingerprint of CA certificate is unique and identifies the credential, also over disparate DLS instances. The
fingerprint is also used as a part of the file name for export (see the Export button).
Create CA
Creates a new credential for SPE, i. e. first, a new CA certificate, and then, a certificate with this CA signature is
created. the status of the new credential is "created".
Deploy CA
Deploys a new credential for SPE, that is, the CA certificate is distributed to the corresponding IP devices. The
table is updated, and the status for the credential is changed to "deployed".
Activate
Activates a new credential for SPE, that is, the Ca certificate is distributed to the gateways. The table is update,
and the status for the new credential is changed to "acitvated", while the status of the previously active credential
is changed to "phase-out".
Delete
Deletes a credential that is no longer necessary, i. e. a credential in "created" or "deployed" status, or or the
activated credential (in case only one credential exists) or the phase-out credential (in case more than one
credential exist). After this, the table is updated.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-209
administration.fm
Administration
autoSPE Info: Gateways and number of enddevices that use/accept new/phase-out credential
Device ID
Displays the device ID of the gateway.
GW uses ACT
Indicates whether the gateway uses the active credential.
Possible values:
yes
no
GW accepts NEW
Indicates whether the gateway accepts the new credential.
Possible values:
yes
no
GW accepts OLD
Indicates whether the gateway accepts the phased-out credential.
Possible values:
yes
no
6-210
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Automatic SPE Configuration
Export
Writes the current autoSPE configuration to a file. This can be used for backup purposes and for a migration to a
different DLS.
NOTE: The password is not intended for the zip archive format file but for the files contained inside
the zip file( WPI credentials).
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-211
administration.fm
Administration
CN=
Common Name of the issuer.
Example: Unify Security Office.
OU=
Organizational Unit of the issuer.
Example: Unify Systems.
O=
Organization of the issuer.
6-212
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Automatic SPE Configuration
L=
Location of the issuer.
Example: Mnchen.
C=
Country of the issuer.
Example: DE.
Valid to
Maximum validity for new autoSPE credentials.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-213
administration.fm
Administration
6-214
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Automatic SPE Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-215
administration.fm
Administration
Job ID:
For the activation of certificates, a job is started. A unique job ID is assigned to this job in order to identify it. Via
this field, it is possible to jump to the job control (see Section 14.1, "Job Control") to control the status of the job.
6-216
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Automatic Certificate Deployment
Cancel Job
With this button, all jobs belonging to this certificate deployment task with active or running status will be cancelled.
Location:
Location where the certificate deployment will be executed. Locations can be assigned as described under
Section 6.3.2, "Location".
Certificate Type:
Type of certificate.
Possible options:
Phone Certificate
Deploy Date:
Date when certificate deployment will be started.
Remark:
Remark (free text).
Certificate:
The following certificate parameters are displayed only.
PKI Configuration
PKI configuration.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-217
administration.fm
Administration
Serial Number:
Serial number of the certificate.
Owner:
Owner of the certificate.
Issuer:
Issuer of the certificate.
Valid from:
The certificate will be valid from this point in time.
Valid to:
The certificate will be valid until this point in time.
Key Algorithm
Key algorithm.
Key Size
Key size.
Fingerprint (SHA-1):
Test algorithm SHA-1 (160 bits/20 characters) for the security certificate.
Expires in [days]:
The certificate expires in ... days.
6-218
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Automatic Certificate Deployment
Alarm Status:
Current alarm status of imported certificate.
Possible values:
valid
expired
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-219
administration.fm
Administration
Save
Saves the data entered/modified.
New
Creates a new entry, i.e. a new certificate deployment task.
Delete
Deletes an entry.
Import Certificate
Import either a specific certificate to be automatically deployed to devices or a PKI configuration that will be used
to automatically request certificates for all devices.
NOTE: If you dont proceed with the Import Certificate button,then an empty certificate shall be
deployed thus all respective certificates shall be removed
Refresh
Refreshes the content of the relevant page.
6-220
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Automatic Archiving
General Data
"Settings" Tab
"Protocol" Tab
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-221
administration.fm
Administration
Automatic Archiving
General Data
Archive Task
Name of the archive task.
Archive File
Filename and directory path for the archive file on the DLS Server. If the file is not present, it will be created during
the first archiving of data; if it is already present, the archive data will be added to the existing .zip-archive.
Remark
Remark on archive task.
Browse...
Select excisting archive path. Path name and filename will be written to the archive file. Only directories can be
searched, not particular files.
Test
Test if the file is accessible.
6-222
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Automatic Archiving
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
Save
Starts a job for distributing the configuration changes. For more information, see Section 15.1,
"First Steps: Changing IP Device Parameters".
Discard
The modifications carried out in the mask are discarded.
Export File
The inventory data are exported into a csv formatted file.
Refresh
Refreshes the window contents from the database.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-223
administration.fm
Administration
Automatic Archiving
General Settings
Maximum Number of Backup Archive Files
Contains the number of backup files to be created for file history, if the original archive file is overwritten.
Time Settings
Enable daily Archiving
Activates daily archiving of IP Devices .
6-224
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Automatic Archiving
Archive now
Starts archiving immediately without any regards to settings for automatic archive. The archive will be saved to
the Archive File currently displayed.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-225
administration.fm
Administration
Automatic Archiving
IP Device Selection
E.164 based
Selection of IP Devices to be archived by E.164 number.
Location based
Selection of IP Devices to archive by location.
E.164
E.164 /E.164 Pattern
Entire E.164 number or a range of E.164 numbers partly qualified with '*', e.g. 31* (= all E.164 numbers, starting
with 31... ).
Location
Location
Select a defined location. Default Location cannot be selected.
6-226
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Automatic Archiving
E.164
E.164 / E.164 Pattern:
A complete E.164 number or a range of numbers partly qualified with * can be entered here.
Example: 31* = all E.164 numbers that begin with 31.
NOTE: In the case of mobile users, Auto-archiving is enabled and achieved, regardless of their
logon/logoff status.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-227
administration.fm
Administration
Automatic Archiving
Protocol
Maximum Number of Protocols:
Each protocol entry can be deleted manually or will be deleted automatically according to the number entered
here.
Start Time
Start Time of archiving.
End Time
End Time of archiving.
Created
Displays whether it is an automatic or a manual archive task.
Manual
Timer triggered
Status
Status of archiving.
Possible values:
6-228
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Automatic Archiving
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-229
administration.fm
Administration
General Data
"Protocol" Tab
6-230
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Automatic Upload Diagnosis- and Security Log Files
General Data
10
20
30
40
50
60
90
120
240
Default value: 60
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-231
administration.fm
Administration
10
20
30
40
50
60
90
120
240
Default value: 60
Discard
Discards any changes entered.
Refresh
Updates the window using the database.
6-232
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Automatic Upload Diagnosis- and Security Log Files
Start of Upload
Displays the upload's starting time.
Number of Devices
Displays the number of handled IP Devices.
Remark
Remark on the upload.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-233
administration.fm
Administration
Trace Configuration
General Data
6-234
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Trace Configuration
General Data
Call: Main Menu > Administration > Trace Configuration
You can use this menu item to configure trace operations. The settings are stored in the DLS database. A timer
monitors if there are any new entries in the database. If so, the trace is modified accordingly; where applicable,
changes are also transferred to the other servers in a cluster.
NOTE: The changes take effect after approximately two minutes.
NOTE: Individual settings can restrict the options available in the menu Administration > Display
Logging Data.
For information on general interface operation, see Section 5.4.2, "Work Area".
Trace Mode
Option for selecting the trace mode.
Possible values:
Off
No special traces are performed. All error messages will be written to a default tracefile. This is the default
setting after installation.
DLS Server
The trace is performed in the DLS server with the assigned Level for local Trace.
DLS Communication
Communication between IP devices and DLS server is traced with the assigned Level for local Trace.
Additionally all error messages will be written to the default tracefile.
Log4j Template
The trace is performed with the predefined trace template selected under Trace Template.
Trace Directory
Directory in which the trace files are stored.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-235
administration.fm
Administration
Trace Configuration
Trace Template
Option for selecting predefined trace settings. The trace templates are stored in the file directory
<drive>:\Program Files\DeploymentService\Tomcat5\webapps\
DeploymentService\log\templates.
The settings in the templates are only effective if the Trace Mode "Log4j Template" is set.
Possible values:
01.all.debug.template
Log all DLS activities with DEBUG logging level.
NOTE: In the case where a SOAP based element manager (H8K, H8K Ass, H4K(WebService)) or a
dlsAPI client (H8K Assistant, OSILA) needs to send the payload encryption, they just have to activate
the '01.all.debug.template'
02.all.info.template
Log all DLS activities with INFO logging level.
03.default.template
Default setting. Log all DLS activities with ERROR logging level.
04.gateway.template
Log all gateway activities with DEBUG logging level.
05.gateway.wpcomm.details.template
Log all gateway activities including communication between workpoint and DLS with DEBUG logging level.
06.gateway.wpcomm.info.template
Log all gateway activities including communication between workpoint and DLS with DEBUG logging level.
07.keyexchange.template
Log all gateway and key distribution activities with DEBUG logging level.
08.keyexchange.wpcomm.details.template
Log all gateway and key distribution activities including communication between workpoint and DLS with
DEBUG logging level.
09.keyexchange.wpcomm.info.template
Log all gateway and key distribution activities including communication between workpoint with DEBUG
logging level.
10.wpcomm.details.template
Log communication between workpoint and DLS with DEBUG logging level.
11.wpcomm.short.template
Log communication between workpoint and DLS with INFO logging level.
6-236
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Trace Configuration
12.wpscan.wpcomm.details.template
Log all workpoint-based scan activities including communication between workpoint and DLS with DEBUG
logging level.
13.wpscan.wpcomm.short.template
Log all workpoint-based scan activities including communication between workpoint and DLS with INFO
logging level.
14.dlsapi.template
Log all DLS API methods with DEBUG logging level.
15.auth.debug.template
Log all authentication activities including communication between workpoint and DLS with DEBUG logging
level.
16.nodb.debug.template
Log all DLS activities with the exception of database activities including communication between workpoint
and DLS with DEBUG logging level.
17.pp.em.debug.template
Log all Plug&Play and element manager related activities with DEBUG logging level.
18.pki.details.template
Log all PKI activities with DEBUG logging level.
DEBUG
Comprehensive trace of processes.
INFO
Selected process information.
WARN
Displays potential problems.
ERROR
Displays problems that do not cause the deployment service to fail.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-237
administration.fm
Administration
Trace Configuration
Trace Server
Server where the common trace files are stored.
DEBUG
Comprehensive trace of processes.
INFO
Selected process information.
WARN
Displays potential problems.
ERROR
Displays problems that do not cause the deployment service to fail.
FATAL
Displays problems that cause the deployment service to fail.
INFO
Selected process information.
WARN
Displays potential problems.
ERROR
Displays problems that do not cause the deployment service to fail.
6-238
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Trace Configuration
FATAL
Displays problems that cause the deployment service to fail.
Discard
Discards any unsaved changes.
Refresh
Refreshes the content of the relevant page.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-239
administration.fm
Administration
Trace Configuration
6-240
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Trace Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-241
administration.fm
Administration
Trace Configuration
Error trace
Activate repeat filter
When activated, repetitions of messages in the error trace are filtered out. The context range, within which
repetitions are searched, is specified in the Number of messages to check parameter.
Standard trace
Activate repeat filter
When activated, repetitions of messages in the standard trace are filtered out. The context range, within which
repetitions are searched, is specified in the Number of messages to check parameter.
6-242
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Trace Configuration
Communication trace
Activate repeat filter
When activated, repetitions of messages in the communication trace are filtered out. The context range, within
which repetitions are searched, is specified in the Number of messages to check parameter.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-243
administration.fm
Administration
Trace Configuration
active
Filter is switch off and on.
Error trace
If active, this string is valid for error trace filtering.
Standard trace
If active, this string is valid for standard trace filtering.
Communication trace
If active, this string is valid for communcation trace filtering.
6-244
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Trace Configuration
Start Test
The test messages are generated and filtered. The results appear in the traces.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-245
administration.fm
Administration
Trace Configuration
OSVTM IP address
Specification of the OSVTM IP address.
User ID
User ID for OSVTM file transfer.
Password
Password for OSVTM file transfer.
Connection Retries
If the file transfer fails, the DLS stored trace file is kept for at least a number of Connection Retries.
Default value is set to 6.
6-246
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Trace Configuration
NOTE: In order to enable Thread Monitoring, you must first set Trace Mode to Log4j Template.
Please refer to Section 6.14, "Trace Configuration".
Monitoring Period (minimum: 600 seconds)
The time period interval in which thread monitoring takes place.
Default value is set to 3600 sec.
Take Snapshot
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-247
administration.fm
Administration
Server Licenses
General Data
6-248
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Licenses
General Data
Call: Main Menu > Administration > Server Licenses
Licenseagent
IP address or host name of license agent (CLA).
Port
Port number for access to the license server.
License Management
URL of the license server. Press the adjacent License Management action button to open the License
Management Web interface in a separate window.
Discard
Discards any changes entered.
Refresh
Updates the window using the database.
Read Licenses
Requests available licenses from license agent.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-249
administration.fm
Administration
Server Licenses
NOTE: Once you install a valid DLS license file at LinuxCLM tool, the licenses are not found
straightaway from LinuxDLS after you set the corresponding License Agent IP,since DLS :
6-250
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Licenses
Status:
Status of the connection to the CLA.
Possible Options:
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-251
administration.fm
Administration
Server Licenses
Expiration date
Date of license expiration. After this date no further DLS logon will be possible. Please contact your license
administrator.
Activation Period
If checkbox is active, V7 Base SW and V7 Basic Device Licenses are granted, although they are not part of your
V7 licenses. Please, order an upgrade for your license file.
Expiration date
An expiration date is displayed when working with a demo license. A license awarded by the CLA is not limited in
time.
Registration of IP Devices is not possible any more after this date. Please contact your license administrator.
6-252
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Licenses
Used (%)
Indicates the percentage of licenses already in use.
Reduced functionality
This check box is automatically selected if the number of licenses has been exceeded. The expiration date is set,
and after exceeding the registration of IP Devices is blocked until the surplus IP Devices have been deleted by
the administrator.
Please contact your license administrator.
Expiration date
An expiration date is displayed when working with a demo license (activation period). A license awarded by the
CLA (license agent) is not limited in time.
No more DLS administration is possible after this date. Please contact your license administrator.
Used (%)
Indicates the percentage of licenses already in use.
6-253
administration.fm
Administration
Server Licenses
Reduced functionality
This check box is automatically selected if the number of licenses has been exceeded. In this case, the only option
available is to delete mobile users.
Please contact your license administrator.
Expiration date
An expiration date is displayed when working with a demo license. A license awarded by the CLA (license agent)
is not limited in time.
After this date, PKI support is not possible any more. Please contact your license administrator.
Number of devices
Indicates the number of IP Devices supplied by PKI service licenses already in use for IP Devices.
Used (%)
Indicates the number of licenses already in use as a percentage.
6-254
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Licenses
Reduced functionality
This check box is automatically selected when the number of licenses has been exceeded. After activation period
expiry, the PKI service for IP Devices is blocked. Please contact your license administrator.
Number of devices
Number of IP Devices, supplied with IP Infrastructure data by means of Location Service.
Used (%)
Percentage of used Location Service Licenses.
Expiration date
An expiration date is displayed when working with a demo license (activation period). This is the case, for example,
when the CLA (license agent) is not or no longer available. A license awarded by the CLA is not limited in time.
After this date IP Devices will not be supplied with IP Infrastructure data, except emergency Call, by means of
Location Service. Please contact you license administrator.
Activation Period
Checked if the CLA is unreachable. The licenses determined last are then used. If the CLA has not yet been
reached, 1 DLS node license will be available for the activation period. The DLS tries to contact the CLA every 45
minutes. When the term specified in the Expiration date field expires, the IP Devices will not be supplied with IP
Infrastructure data, except Emergency Call, by means of Location Service. Please contact your license
administrator.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-255
administration.fm
Administration
Server Licenses
Reduced functionality
This check box is automatically selected if the number of licenses has exceeded. In this case, the only option
available is to delete IP Devices.
Please contact your license administrator
Expiration date
An expiration date is displayed when working with a demo license (activation period). A license awarded by the
CLA (license agent) is not limited in time.
After this date, DLS operation in cluster mode will no longer be possible. Please contact your license administrator.
Expiration date
An expiration date is displayed when working with a demo license (activation period). A license awarded by the
CLA (license agent) is not limited in time.
6-256
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administration.fm
For internal use only
Administration
Server Licenses
After this date, database mirroring will no longer take place. Please contact your license administrator.
Reduced functionality
This check box is automatically selected if the number of licenses has been exceeded. In this case, no database
mirroring will be performed.
Please contact your license administrator
Expiration date
An expiration date is displayed when working with a demo license (activation period). A license awarded by the
CLA (license agent) is not limited in time.
After this date, XML Push will no longer be available. Please contact you license administrator.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
6-257
administration.fm
Administration
Server Licenses
Multinode licenses
If activated, DLS requests licenses for DLS Nodes and DB Mirroring from the CLA.
6-258
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
7 IP Devices
Call: Main Menu > IP Devices
This menu item consists of the following areas:
IP Phone Configuration
IP Client Configuration
IP Gateway Configuration
IP Device Interaction
IP Device Management
Use this area to display and change the configuration data of IP devices.
NOTE: If changes are made in data records that have been generated using templates, these
changes are not automatically applied to the templates.
These changes must be manually saved to the template (Section 15.5, "Editing Templates").
NOTE: You can enter parameters for both SIP and HFA for every IP client in the IP Client
Configuration area.
NOTE: An IP device can only be configured at the DLS after its successful registration. For registration, the IP device must be familiar with the relevant DLS address. Registration at the DLS is
achieved by:
- reading out IP device data via the DLS, see Section 7.4.6, "Scan IP Devices" and by
- plugging the LAN connector or power supply into the IP device.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-1
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Gateway/Server
IP Routing
Ports
Features
Quality of Service
Security Settings
Telephony
Dialing Properties
Time Parameters
Audio Settings
SNMP Settings
Applications
LDAP
User Settings
SIP Mobility
HFA Mobility
Keysets/Keylayout
WLAN Settings
IEEE 802.1x
Diagnosis
Miscellaneous
File Deployment
7-2
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
General Data
This part of the contents area is used for entering parameters in Search view to find a specific group of IP phones.
The base data associated with the IP phones found is displayed in Object view (no changes possible except
under Remarks).
NOTE: The Search view fetches only the attributes of the specific mask that is currently displayed
for the selected device(s) and not the attributes of all the masks under IP Phone Configuration for
that device(s) as in previous DLS/phone versions.
For further information on the Search view, please refer to Section 5.5, "Search Functionality".
IP Address:
IP address of the IP phone. For OpenStage, an IPv4 or IPv6 address is displayed here. See also the description
of the IP Protocol Mode parameter.
Example: 192.117.1.193
The value is read-only if it was dynamically assigned with DHCP.
Device ID:
ID for unique identification of the IP device. In IP phones, this is generally the MAC address.
Example: 00:0E:A6:85:71:80
Device Type:
IP phone device type. The icon
All IP phone types supported by DLS can be found in Section 3.4, "Area of Application".
Example: optiPoint 410 standard, OpenScape Desk Phone IP 35G, OpenScape Desk Phone IP 35G Eco
E.164:
Complete E.164 subscriber number (Basic Profile or Mobile Profile).
Example: 498972212345
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-3
workpoint-configuration.fm
IP Devices
IP Phone Configuration
For information on the meaning of the E.164 station number in relation to mobility, see Section 3.8.3, "Mobility ID".
Basic E.164:
Complete E.164 phone number (Mobility Phone).
Example: 498972212345
For information on the meaning of the E.164 station number in relation to mobility, see Section 3.8.3, "Mobility ID".
IP Address 2:
Second IP address of the IP phone, if it has an IPv6 address.
Available for OpenStage only.
SW Version:
Software version of the IP phone.
Example: 5.0.12
Information on the difference between the software and license version can be found in Section 15.7, "Distribution
of Workpoint Software".
SW Type:
IP phone software type.
Examples: Unify HFA, Unify SIP.
Reg-Address
IP address or DNS name of the HFA or SIP server at which the device is registered.
Last Registration:
Time of last IP phone registration.
For information on selecting a time segment for a search, see Section 5.4.2.4, "Content Area".
7-4
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Remarks:
Fields for general information.
IP Protocol Mode
Indicates which IP version is used by the phone. If both versions are used, IP Address contains the IPv4 address,
and IP Address 2 contains the IPv6 address.
Only available for openStage.
Possible options:
IPv4
IPv6
Location
Current location of the IP Device. The value is set during registration and is displayed only herein. (For meaning
and configuration of the location, see Section 6.3.2, "Location".)
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-5
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
Get
Loads a template that has already been saved. For more information, see Section 15.5, "Editing Templates".
Save
Saves configuration entries as a template. For more information, see Section 15.5, "Editing Templates".
Discard
Discards any changes made and new entries.
Read
The parameters displayed on the new mask are read in again by the IP device.
Rename
Changes the name of a saved template. For more information, see Section 15.5, "Editing Templates".
Delete
Deletes a saved template. For more information, see Section 15.5, "Editing Templates".
7-6
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Import Certificate
Imports a certificate for the selected IP device (only available in Certificate Management). For more information,
see Section 16.13, "Security: Administering Certificates".
Remove Certificate
Deletes a certificate for the selected IP device (only available in Certificate Management). For more information,
see Section 16.13, "Security: Administering Certificates".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-7
workpoint-configuration.fm
IP Devices
IP Phone Configuration
7.1.1 Gateway/Server
Call: Main Menu > IP Devices > IP Phone Configuration > Gateway/Server
This area features the following components:
General Data
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
7-8
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
General Data
This part of the contents area is used for entering parameters in Search view to find a specific group of IP phones.
The base data associated with the IP phones found is displayed in Object view (no changes possible except
under Remarks).
NOTE: For further information about the Search view, please see Section 5.5, "Search Functionality".
IP Address:
IP address of the IP phone. For OpenStage, an IPv4 or IPv6 address is displayed here. See also the description
of the IP Protocol Mode parameter.
Example: 192.117.1.193
The value is read-only if it was dynamically assigned with DHCP.
Device ID:
ID for unique identification of the IP device. In IP phones, this is generally the MAC address.
Example: 00:0E:A6:85:71:80
Device Type:
IP phone device type.
All IP phone types supported by DLS can be found in Section 3.4, "Area of Application".
Example: optiPoint 410 standard
E.164:
Complete E.164 subscriber number (Basic Profile or Mobile Profile).
Example: 498972212345
For information on the meaning of the E.164 station number in relation to mobility, see Section 3.8.3, "Mobility ID".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-9
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Basic E.164:
Complete E.164 phone number (Mobility Phone).
Example: 498972212345
For information on the meaning of the E.164 station number in relation to mobility, see Section 3.8.3, "Mobility ID".
IP Address 2:
Second IP address of the IP phone, if it has an IPv6 address.
Available for OpenStage only.
SW Version:
Software version of the IP phone.
Example: 5.0.12
Information on the difference between the software and license version can be found in Section 15.7, "Distribution
of Workpoint Software".
SW Type:
IP phone software type.
Examples: Unify HFA, Unify SIP.
Last Registration:
Time of last IP phone registration.
For information on selecting a time segment for a search, see Section 5.4.2.4, "Content Area".
Remarks:
Fields for general information.
IP Protocol Mode
Indicates which IP version is used by the phone. If both versions are used, IP address contains the IPv4 address,
and IP address 2 contains the IPv6 address.
7-10
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
IPv4
IPv6
Location
Current location of the IP Device. The value is set during registration and is displayed only herein. (For meaning
and configuration of the location, see Section 6.3.2, "Location".)
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-11
workpoint-configuration.fm
IP Devices
IP Phone Configuration
System Type:
Type and version of the communication platform at which the workpoint is operated.
Possible options:
Unknown
OpenScape Business V1
OpenScape Business V2
OpenScape Business V3
OpenScape Business V4
7-12
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Gatekeeper ID:
ID of the PBX, gateway or gatekeeper used for operating the workpoint.
NOTE: This ID corresponds to the "Globid" parameter in AMO HFAB for the HiPath 4000 resp. the
H.323 ID with the HiPath 3000.
None
No voice encryption.
Reduced
One-way voice encryption (gatekeeper data not sent in encrypted form).
Full
Voice encryption both ways (workpoint and gatekeeper data both sent in encrypted form).
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-13
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Subscriber Password:
Password of the workpoint at the PBX.
Only available in HFA workpoints.
7-14
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
System Type:
Type and version of the communication platform at which the workpoint is operated.
Possible options:
Unknown
OpenScape Business V1
OpenScape Business V2
OpenScape Business V3
OpenScape Business V4
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-15
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Reg-Address:
IP address or host name of the PBX or gateway provided as standby for the workpoint.
Reg-Port:
Port number of the PBX or gateway provided as standby for the workpoint.
Gatekeeper ID:
ID of the PBX, gateway or gatekeeper provided as standby for the workpoint.
NOTE: This ID corresponds to the "Globid" parameter in AMO HFAB for the HiPath 4000 resp. the
H.323 ID with the HiPath 3000.
None
No voice encryption.
7-16
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Reduced
One-way voice encryption (gatekeeper data not sent in encrypted form).
Full
Voice encryption both ways (workpoint and gatekeeper data both sent in encrypted form).
Subscriber Password:
Password of the workpoint at the standby PBX.
Only available in HFA workpoints.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-17
workpoint-configuration.fm
IP Devices
IP Phone Configuration
SIP URL:
SIP address of the IP phone.
Format: <SIP user ID>@<Domain>.
Terminal Details
Terminal Name:
Name of the IP phone used as a synonym for the phone number during registration.
Only necessary if the Register by Name checkbox is selected and the registrar server is appropriately configured.
Register by Name
If this checkbox is activated, the phone logs on using the Terminal Name.
Display ID:
Name of the IP phone, as displayed on the telephone.
Value range: max. 24 alphanumeric characters.
7-18
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Use Display ID
If this checkbox is activated, the display ID is displayed on the devices status bar.
System Name:
Random name that appears in the lower right-hand corner of the IP phones display (in two-line display).
Example: HiPath
Value range: max. 10 alphanumeric characters.
System Description:
Used to display a system description at the workpoint (for three- or four-line display).
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-19
workpoint-configuration.fm
IP Devices
IP Phone Configuration
SIP Routing:
Possible options:
Direct
For test purposes only.
Gateway
If a gateway is used.
Server
If an SIP proxy is used.
If Direct or Gateway is selected, no registration messages are sent during registration. Registration messages are
sent to the registrar server for the Server routing mode.
7-20
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-21
workpoint-configuration.fm
IP Devices
IP Phone Configuration
7-22
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Outbound Proxy
Checkbox for activating an SIP proxy for outbound calls.
Together with SIP Default OBP Domain, this checkbox controls outbound call routing on the basis of the number
dialed or the user ID.
For more information, see Chapter 17, "Outbound Proxy".
Sequence
CRLF
SIP Realm:
Naming range where the user ID and password are valid. This SIP realm must be entered in the system and on
the SIP server.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-23
workpoint-configuration.fm
IP Devices
IP Phone Configuration
SIP Password:
Password associated with the user ID, required to access the SIP server.
MLPP Settings
MLPP Base
Possible options:
Local
Server
dsn
dsn-000000
uc
uc-000000
dsn+uc
Other domain
Broadsoft
OpenScape Voice
7-24
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Sylantro
Other
HiQ 8000
Genesys
Authentication Required
Activate this checkbox if you have to enter your SIP user ID in addition to the standard access data to log on to
the SIP provider.
Only applies to WLAN phones.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-25
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Backup Registration
Checkbox for activating the backup registration.
7-26
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
7.1.2 IP Routing
Call: Main Menu > IP Devices > IP Phone Configuration > IP Routing
This area features the following components:
General Data
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-27
workpoint-configuration.fm
IP Devices
IP Phone Configuration
IP Address
IP address of the IP phone.
IPv4
IPv6
7-28
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
IP Configuration
Determines how the IP settings are to be configured; valid from OpenStage version 1.5. With versions < 1.5, this
field is greyed out, like the remaining LLDP-MED parameters.
NOTE: Please note that the writing and reading procedures for this parameter differ from one
another. When the DLS user select a particular option (e.g. "LLDP-MED with DHCP Configuration"),
the IP configuration parameters are set and sent to the end device. When reading from the device,
however, "Please select an option for IP Configuration" is displayed in any case. This is due to the
possibility that the parameter may not have been detected unambigously; for instance, the value of
the VLAN method parameter can depend on whether the VLAN ID has been determined over DHCP
or over LLDP-MED.
The field is predefined with 'Please select an option for IP Configuration'.
Possible Values:
Use DHCP
Manual Settings
DHCP IP Assign
This checkbox can be activated if a DHCP server is present. The workpoint then obtains the IP address data
dynamically from the DHCP server.
This checkbox must not be activated if there is no DHCP server available. Instead, the IP address data (IP
Address, Terminal Mask and Default Route) must be manually set for this workpoint.
DHCP Broadcast
This checkbox can be activated if a DHCP server is present. With this entry the user can change the DHCP
protocol element "flags". If the broadcast flag is enabled, the DHCP server will broadcast its responses to the
phone's requests; otherwise unicast responses will be used.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-29
workpoint-configuration.fm
IP Devices
IP Phone Configuration
VLAN
VLAN ID:
VLAN ID when using virtual LANs. Can only be changed if QoS layer 2 is active. The value is read-only if it has
been dynamically assigned with DHCP.
Value range: 0 ... 4095.
VLAN Method:
Determines how the VLAN ID is assigned to the end device. Can only be changed when QoS layer 2 has been
activated.
Possible options:
Manually
The VLAN ID is entered manually.
DHCP
The VLAN ID supplied by the DHCP server is used.
None
(For WLAN only)
LLDP-MED
The VLAN ID supplied by LLDP-MED (Link Layer Discovery Protocol - Media Endpoint Discovery) is used.
Available for OpenStage from V1R5 onwards.
LLDP-MED
LLDP-MED enabled:
Enables sending and receiving LLDP data.
LLDP-MED Time-to-Live
Possible Values:
40
60
80
100
110
7-30
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
120
140
180
240
320
400
Terminal Mask:
Subnet mask for the IP address.
The value is read-only if it was dynamically assigned with DHCP.
Default Route:
IP address or host name of the default router/gateway.
The value is read-only if it was assigned with DHCP.
Route 1:
IP address or host name of the first static route (optional).
Gateway 1:
IP address or host name of the router/gateway of the first static route (optional).
Mask 1:
Subnet mask of the first static route (optional).
Route 2:
IP address or host name of the second static route (optional).
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-31
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Gateway 2:
IP address or host name of the router/gateway of the second static route (optional).
Mask 2:
Subnet mask of the second static route (optional).
10 Mbps half-duplex
10 Mbps full-duplex
Auto
Default: Auto
10 Mbps half-duplex
10 Mbps full-duplex
Auto
Default: Auto
7-32
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Disabled
The LAN port is inactive.
Enabled
The LAN port is active.
Mirror
All data traffic on LAN port 1 is mirrored to port 2.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-33
workpoint-configuration.fm
IP Devices
IP Phone Configuration
IPv6 Address
IPv6 address of the IP phone.
IPv6 DHCP
IPv6 DHCP
7-34
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-35
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Single IP
ANAT
Media IP Mode
Selects the media IP mode.
Possible options:
IPv4
IPv6
IPv4 / IPv6
IPv6 / IPv4
7-36
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Hostname
Terminal Hostname / WEB Name:
Host name of the terminal.
Permitted characters: letters, digits, hyphens, underscores, and periods; case-sensitive; maximum length: 63
characters.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-37
workpoint-configuration.fm
IP Devices
IP Phone Configuration
No DDNS Hostname
Only Number
Prefix Number
MAC based
7-38
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
7.1.3 Ports
Call: Main Menu > IP Devices > IP Phone Configuration > Ports
This area features the following components:
General Data
"Ports" Tab
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-39
workpoint-configuration.fm
IP Devices
IP Phone Configuration
H.225.0 RAS:
Port number for H.225 RAS.
Purpose: Registration and approval in the case of VoIP.
For communication with the following clients: Netmeeting, AP1120.
Port used: 1719
7-40
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
JAVA Gateway:
Port number for gateways used by Java applications.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-41
workpoint-configuration.fm
IP Devices
IP Phone Configuration
7-42
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
H.225.0 RAS:
Port number for H.225 RAS.
Purpose: Registration and approval in the case of VoIP.
For communication with the following clients: Netmeeting, AP1120.
Port used: 1719
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-43
workpoint-configuration.fm
IP Devices
IP Phone Configuration
JAVA Gateway:
Port number for the Java gatekeeper.
7-44
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-45
workpoint-configuration.fm
IP Devices
IP Phone Configuration
7.1.4 Features
Call: Main Menu > IP Devices > IP Phone Configuration > Features
This area features the following components:
General Data
"Availability" Tab
"Dialplan" Tab
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
7-46
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Group pickup
Group Pickup URI:
URI of the group pickup.
Only available in SIP workpoints.
Station-controlled Conference
Conference Factory URI:
URI for setting up conference calls.
Only available in SIP workpoints.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-47
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Callback
Callback-busy URI:
URI of the server that controls the "Callback-busy" feature.
Only available for optiPoint and OpenStage V1 and V2.
Callback FAC
URI to be used for stimulus callback call requests.
Only available for OpenStage V3.0 onwards.
Deflection
Deflect Destination
Destination number for call forwarding.
7-48
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
BLF
BLF Pickup Code:
Feature code for BLF Pickup Code with Asterisk.
Only available in SIP workpoints.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-49
workpoint-configuration.fm
IP Devices
IP Phone Configuration
7-50
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Ordinary
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-51
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Hotline
Warmline
Open Listening
Configures switching to Open Listening mode.
Possible options:
Standard Mode
To switch to Open Listening mode, the user must press and hold the Open Listening key while returning the
handset to the cradle.
US Mode
To switch to Open Listening mode, the user must press the Open Listening key and then return the handset
to the cradle.
Call Recorder
The central voice recorder records the entire voice flow of two or more participants.
7-52
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Call recording
Switch on/off call recording.
Recording Mode
Determines the behaviour of the call recording.
Possible options:
Manual
Auto Start
All Calls
Disabled
(Display only)
Audible Notification
Select the tone for audible notification.
Possible options:
Off
On / Single Shot
Repeated
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-53
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Transfer on Ring
Checkbox for activating the "Transfer on Ring" feature
If this option is activated, you can activate call transfer by replacing the handset even before the called party
answers.
Only available in SIP workpoints.
Transfer on Hangup
Checkbox for activating the "Transfer on Hangup" feature.
Only available in SIP workpoints.
Bridging enabled
When active, call bridging is enabled.
Only available in SIP workpoints.
uaCSTA allowed
Checkbox to activate the "uaCSTA" feature.
Only available in SIP workpoints.
Phonebook lookup
Checkbox for activating the "Phonebook lookup" feature.
Callback
The user can request a callback if the station called is busy or if nobody answers. The user receives a callback
when the other partys line becomes free.
Callback: Busy
Checkbox for activating the "Callback-busy" feature.
7-54
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Callback: No reply
Checkbox for activating the "Callback-no reply" feature.
Only available in SIP workpoints.
Callback: Cancel
When active, the user can cancel callback requests.
Callback
Activates Callback.
Only available for OpenStage V3 onwards.
On
Off
Max. Callbacks
Maximum number of callback requests allowed to be pending at the same time.
Possible values: 1 ... 10
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-55
workpoint-configuration.fm
IP Devices
IP Phone Configuration
unlimited
10
15
20
30
40
50
60
90
120
Callback Ringer
Sets the ringertone to be used to announce the availability of a callback call.
Call Logging
Enable Call Log
Checkbox that indicates whether Call logging is enabled.
Missed Logging
Indicates whether calls completed elsewhere will be logged on phone.
Possible options:
7-56
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Delete Entry
Indicates whether calls log entries are deleted in case there is a call to an entry in Missed calls list.
Possible options:
Outgoing calls that are made to entries in Missed calls tab of call log and that are connected will not be deleted
from call log.
Outgoing calls that are made to entries in Missed calls tab of call log and that are connected will be deleted from
call log.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-57
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Video Calls
Allow Video Calls
Checkbox for activating Video Calls.
If the Allow Video Calls checkbox is activated ,then video calls will be allowed.
Incoming Calls
Allow Deflection
Checkbox for activating Call Deflection.
If the user wants to deflect an incoming call, he is prompted to enter a destination phone number if there is none
stored.
7-58
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
The user can accept a second incoming call in the course of an ongoing call. The caller hears the on-hook signal
while the user hears a call-waiting signal tone. The user can reject or accept the second call. Before he accepts
the second call, he can end the first call or place it on hold for subsequent retrieval.
CTI Calls
Auto answer
Checkbox for activating Auto Answer.
Speakerphone mode activates automatically on the phone if a CTI application (such as Outlook) is used to dial a
number when Auto Answer is active. If Auto Answer is not active, the phone rings first and the user must press
the loudspeaker key or lift the handset to set up the call. This setting also defines whether or not incoming calls
are automatically accepted. If the function is active, an alert beep sounds when a call is automatically accepted.
Only available in SIP workpoints.
Auto reconnect
Checkbox for activating automatic reconnection of a parked call.
Only available in SIP workpoints (optiPoint).
7-59
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Outgoing calls
Autodial delay (sec):
Delay for Automatic Dialing in seconds.
A number is automatically dialed after a set delay starting from the entry of the numbers last digit.
Immediate Dialing
If this check box is active, immediate dialing is executed as soon as the entered string matches a dial plan entry.
Only available in SIP workpoints.
Callback
The user can request a callback if the station called is busy or if nobody answers. He will receive a callback when
the other partys line becomes free.
Allow Callback Busy
Checkbox for activating Callback on Busy.
Only available for OpenStage V1 and V2.
7-60
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Callback Option
Callback Option.
Only available for OpenStage starting with V3.
Established Connections
Allow Call Transfer
Checkbox for activating Call Transfer.
Allow Conferences
Checkbox for activating Conferences.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-61
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Toggle associate
When this feature is activated, the following procedure will ensue: The user has accepted a second call, whereby
the first call is put to hold. As soon as the user has alternated back to the first call, and then again to the second
call, he/she can connect both calling parties by going on-hook.
7-62
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
-Auto answer
-Call deflection
-Call forwarding
-Auto answer
-Call waiting
-Log forwarded calls
-Music on hold
-Call park
-Call transfer
-Local conference
-Message waiting
-Video Call
-
-See also "Feature Settings 2" Tab.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-63
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Call hold
Checkbox for activating the function for placing calls on hold.
Only available in SIP workpoints.
Call deflection
Checkbox for activating manual forwarding for incoming calls (CD).
Only available in SIP workpoints.
Call forwarding
Checkbox for activating automatic call forwarding (CF).
Only available in SIP workpoints.
Call duration
Checkbox for activating the function for displaying the call duration.
Only available in SIP workpoints.
Call waiting
Checkbox for activating visual and/or acoustic alerting for waiting calls (CW).
Only available in SIP workpoints.
Call transfer
Checkbox for activating the function for transferring calls (ECT).
Only available in SIP workpoints.
7-64
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Call pickup
Checkbox for activating the function for picking up parked calls.
Only available in SIP workpoints.
Auto reconnect
Checkbox for activating the auto reconnect feature.
Only available in SIP workpoints.
Music on hold
Checkbox for activating music on hold for held and parked calls.
Only available in SIP workpoints.
Do not disturb
Checkbox for activating the do-not-disturb function (optical alerting and ring only).
Only available in SIP workpoints.
Message waiting
Checkbox for activating alerting for waiting messages (MWI).
Only available in SIP workpoints.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-65
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Local conference
Checkbox for activating the function for setting up a local conference.
Only available in SIP workpoints.
Auto answer
Checkbox for activating auto answer.
Only available in SIP workpoints.
Phone Lock
Checkbox for activating phone lock function.
Only available in SIP workpoints.
NOTE: The default setting of this function on the OpenStage phone is set to true.
For SW Version< V3,the phone lock function is not available (nor visible),as opposed to versions V3
onwards,where it is possible to control the features availability (can also be controlled by WBM).
If the phone lock option is unchecked in the phones Web Based Management (WBM) it' s impossible
to lock the phone.
NOTE: Please refer to Phone lock function at Section 7.1.16.3, ""Locked Local Functions" Tab".Keep
in mind the following options:
- If the Phone lock function is enabled at both tabs,the phone lock is not possible and the option is
grayed out.
- If both checkboxes are unchecked,the phone lock is not possible nor visible in the menu.
- If the function is enabled for the Mobile user but unchecked at the Availability tab,the phone lock
is not possible nor visible in the menu.
- Finally, the phone lock is possible only if the function is checked solely at the Availability tab.
PC Interface
Checkbox for enabling the interface between the PC and the device.
7-66
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
LDAP on APM/DSM
Checkbox for activating the LDAP function on the optiPoint application module/display module.
Only available in SIP workpoints.
Telephony on APM/DSM
Checkbox for activating the telephony function on the optiPoint application module/display module.
Only available in SIP workpoints.
ENB on APM/DSM
Checkbox for activating the electronic notebook on the optiPoint application module/display module.
Only available in SIP workpoints.
Call park
Checkbox for activating the function for parking calls.
Only available in SIP workpoints.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-67
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Call join
Checkbox for activating the function for joining calls.
The user can join the first party with the party he consulted, clearing down his own connection to both parties in
the process.
Only available in SIP workpoints.
Blind Transfer
Checkbox for activating the feature "Blind Transfer".
The user can transfer the current call to another party without consultation.
Repertory Dial
Checkbox for activating the feature "Repertory Dial".
The user can select and insert special characters in the dialing sequence for to disconnect the call or activate a
consultation hold or insert a pause.
7-68
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
CTI
Checkbox for activating the CTI interface.
Speakerphone mode activates automatically on the phone if the a CTI application (such as Outlook) is used to dial
a number when Auto Answer is active. If Auto Answer is not active, the phone rings first and the user must press
the loudspeaker key or lift the handset to set up the call. This setting also defines whether or not incoming calls
are automatically accepted.
Line Overview
Checkbox for activating the line Ooverview.
To view the status of the lines, the user must change from the "My phone" tab to the "Overview" tab on the phone
screen.
Feature Toggle
Checkbox for activating the feature "Feature Toggle".
The user can pick a programmable sensor key and program it as a feature toggle key for activating the "make line
busy" and "stop hunt" functions. He can then use the programmable key to activate or deactivate the relevant
OpenScape Voice function on the server for this phone.
Group Pickup
Checkbox for activating the feature "Group Pickup".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-69
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Ext/Int Forwarding
Checkbox for enabling / disabling the External/Internal Forwarding.
7-70
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-71
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Dialplan
Checkbox for activating the dial plan. The entries in this tab are interpreted if this checkbox is active.
Only available in SIP workpoints.
Dialplan ID
Name of the dial plan - must begin with a "!".
Value range: max. 14 alphanumeric characters.
Only available in SIP workpoints.
Dialplan Error
Specifies the dial plan entry that is faulty in the event of an error.
Value range: 1 ... 48
Only available in SIP workpoints.
Digit String
Digit String Digit string for executing this action.
Only available in SIP workpoints.
7-72
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Action
Action executed for this digit string.
Possible options:
Min Length
Minimum digit string length for digit string interpretation.
Only available in SIP workpoints.
Max Length
Maximum digit string length for digit string interpretation.
Only available in SIP workpoints.
Timer
Delay before the action is performed.
Value range: 1 ... 9 seconds.
Only available in SIP workpoints.
Terminating Character
Character that ends the digit string entered.
Possible options:
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-73
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Special Indication
Possible options:
-b- bypass
Comment
Field for general information.
Only available in SIP workpoints.
Terminator sent
Displays whether the terminating character is included in the digit string.
Import File
Imports a dialplan from a file in CSV format.
Export File
Exports a dialplan from a file in CSV format.
7-74
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
NOTE: A template for Ringer Melody / Tone can be created by searching for an IP Device with
entries in Ringer Melody / Tone (empty entries are allowed as well). Use the action Copy to
Template to create a template. There must be 15 entries, which may be empty.
This template can be modified, saved, and applied.
Special Ringers
Internal call
Default value : Bellcore-dr1
External call
Default value : Bellcore-dr2
Recall
Default value : Bellcore-dr3
Emergency
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-75
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Special 3
Index
Automatically generated index for the particular distinctive ringtones.
Alert Info
If the string specified here is identical with a special string which is sent to the phone in the SIP alert info header,
the corresponding ringtone is used.
Only available in SIP workpoints.
Melody
Type of ring melody.
Possible options: Melody 1 ... Melody 8, Melody off
Only available in SIP workpoints.
Tone
Ringtone sequence.
Possible options:
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
7-76
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Tone Duration
Duration of the ringtone.
Value range: 1 ... 300 seconds.
Default: 60 seconds.
Only available in SIP workpoints.
Ringer File
Name of the audio file containing the ringtone.
These two configurations (special ringers & ringer melody table) cannot be performed in a single
step.A new Alert Info and Special Ringer cannot be added at the same time in the Special Ringers
table & the Distinctive Ringers table.Before a Special Ringer is configured, make sure its Alert Info is
already configured,
i.e. first configure Bellcore-dr1 in lower table, press Save and then configure this Alert Info in Special
Ringers Internal Call & press Save again.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-77
workpoint-configuration.fm
IP Devices
IP Phone Configuration
NOTE: The additional Call Forwarding settings (for external/internal) shall be available if the option
"Support of Server Based Features" is enabled under IP Devices>IP Phone Configuration >
Features> "Server based features" Tab.
If that option is enabled, the CFNR delay timer is not configurable (greyed out).
Call Forwarding Unconditional
Forward Any Call
Checkbox for activating unconditional Call Forwarding.
Destination:
Call number of the Call Forwarding destination.
7-78
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Destination:
Call number of the External Call Forwarding destination.
Destination:
Call number of the Internal Call Forwarding destination.
Call Forwarding on Busy
Forward Any Call
Checkbox for activating unconditional Call Forwarding.
Destination:
Call number of the Call Forwarding destination.
Destination:
Call number of the External Call Forwarding destination.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-79
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Destination:
Call number of the Internal Call Forwarding destination.
Destination:
Call number of the Call Forwarding destination.
Destination:
Call number of the Call Forwarding destination.
Destination:
Call number of the Call Forwarding destination.
Delay (sec):
As soon as this time span has expired without the call being accepted, the call is forwarded.
7-80
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Visual
Checkbox for activating a visible alert on the forwarding phone.
Forwarding Party:
Select which forwarding party will be displayed when multiple forwarding is active.
Possible options:
Display first
Display last
Favorites
Forwarding 1:
Forwarding 2:
Forwarding 3:
Forwarding 4:
Forwarding 5:
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-81
workpoint-configuration.fm
IP Devices
IP Phone Configuration
General Data
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
7-82
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Layer 3 Select
Checkbox for activating the QoS layer 3 configuration.
Layer 3 Signaling:
Layer 3 value for call signaling.
Value range fo optiPoint HFA workpoints (lower than optiPoint HFA V5R5) and optiPoint SIP workpoints in SIP5
or lower: 0 .... 63
Possible values for optiPoint SIP6 or higher and optiPoint HFA V5R5 or higher:
10 - AF11
12 - AF12
14 - AF13
18 - AF21
20 - AF22
22 - AF23
26 - AF31
28 - AF32
30 - AF33
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-83
workpoint-configuration.fm
IP Devices
IP Phone Configuration
34 - AF41
36 - AF42
38 - AF43
46 - EF
10 - AF11
12 - AF12
14 - AF13
18 - AF21
20 - AF22
22 - AF23
26 - AF31
28 - AF32
30 - AF33
34 - AF41
36 - AF42
38 - AF43
46 - EF
0 - BE
56 - CS7
0 - BE
10 - AF11
12 - AF12
14 - AF13
18 - AF21
20 - AF22
22 - AF23
26 - AF31
28 - AF32
7-84
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
30 - AF33
34 - AF41
36 - AF42
38 - AF43
46 - EF
Layer 3 Voice:
Layer 3 value for voice transmission.
NOTE: QoS Layer 3 voice transmission can also be set via LLDP-MED (Link Layer Discovery
Protocol). If so, the value can not be changed via DLS.
Value range for optiPoint HFA workpoints (except optiPoint HFA V5R5 and higher) and optiPoint SIP workpoints
with SIP5 or lower: 0 .... 63
Possible values for optiPoint HFA from V5R5 and optiPoint SIP6 or higher:
10 - AF11
12 - AF12
14 - AF13
18 - AF21
20 - AF22
22 - AF23
26 - AF31
28 - AF32
30 - AF33
34 - AF41
36 - AF42
38 - AF43
46 - EF
10 - AF11
12 - AF12
14 - AF13
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-85
workpoint-configuration.fm
IP Devices
IP Phone Configuration
18 - AF21
20 - AF22
22 - AF23
26 - AF31
28 - AF32
30 - AF33
34 - AF41
36 - AF42
38 - AF43
46 - EF
0 - BE
56 - CS7
0 - BE
10 - AF11
12 - AF12
14 - AF13
18 - AF21
20 - AF22
22 - AF23
26 - AF31
28 - AF32
30 - AF33
34 - AF41
36 - AF42
38 - AF43
46 - EF
7-86
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Layer 3 Video:
Layer 3 value for video.
Possible values
0=BE
10=AF11
12=AF12
14=AF13
18=AF21
20=AF22
22=AF23
26=AF31
28=AF32
30=AF33
36=AF42
38=AF43
46=EF
56=CS7
24=CS3
32=CS4
40=CS5
Layer 2 Select
Checkbox for activating the QoS layer 2 configuration.
Layer 2 Signaling:
Layer 2 value for call signaling.
Value range: 0 ... 7
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-87
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Layer 2 Voice:
NOTE: QoS Layer 2 voice transmission can also be set via LLDP-MED (Link Layer Discovery
Protocol). If so, the value can not be changed via DLS.
Layer 2 value for voice transmission.
Value range: 0 ... 7
Layer 2 Default:
Default for the layer 2 value.
Value range: 0 ... 7
Layer 2 video:
Default for the layer 2 value.
Value range: 0 ... 7
Priority Calls
Layer 3 Voice Priority 2
Layer 3 value for voice at priority calls.
Value range: DSCP00 ... DSCP63
7-88
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-89
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Layer 3 Signaling:
Layer 3 value for call signaling.
Value range for optiPoint HFA workpoints (lower than optiPoint HFA V5R5) and optiPoint SIP workpoints in SIP5
or lower: 0 .... 63
Possible values for optiPoint SIP6 or higher and optiPoint HFA V5R5 or higher:
10 - AF11
12 - AF12
14 - AF13
18 - AF21
20 - AF22
22 - AF23
26 - AF31
28 - AF32
30 - AF33
34 - AF41
36 - AF42
38 - AF43
46 - EF
7-90
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Layer 3 Voice:
NOTE: QoS Layer 3 voice transmission can also be set via LLDP-MED (Link Layer Discovery
Protocol). If so, the value can not be changed via DLS.
Layer 3 value for voice transmission.
Value range for HFA workpoints and SIP workpoints in SIP5 or lower: 0 .... 63
Possible values for optiPoint SIP6 or higher and optiPoint HFA V5R5 or higher:
10 - AF11
12 - AF12
14 - AF13
18 - AF21
20 - AF22
22 - AF23
26 - AF31
28 - AF32
30 - AF33
34 - AF41
36 - AF42
38 - AF43
46 - EF
0 - BE
10 - AF11
12 - AF12
14 - AF13
18 - AF21
20 - AF22
22 - AF23
26 - AF31
28 - AF32
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-91
workpoint-configuration.fm
IP Devices
IP Phone Configuration
30 -AF33
34 - AF41
36 - AF42
38 - AF43
46 - EF
Layer 2 Signaling:
Layer 2 value for call signaling.
Value range: 0 ... 7
Layer 2 Voice:
NOTE: QoS Layer 2 voice transmission can also be set via LLDP-MED (Link Layer Discovery
Protocol). If so, the value can not be changed via DLS.
Layer 2 value for voice transmission.
Value range: 0 ... 7
Layer 2 Default:
Default for the layer 2 value.
Value range: 0 ... 7
7-92
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
General Data
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-93
workpoint-configuration.fm
IP Devices
IP Phone Configuration
7-94
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Report Mode:
Specifies when a report should be generated.
Possible options:
Report Interval:
Time interval in which a QoS report is sent.
Value range: 0 ... 3600 seconds.
Observation Interval:
Time interval in which threshold violation is checked.
Value range: 0 ... 5000 seconds.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-95
workpoint-configuration.fm
IP Devices
IP Phone Configuration
7-96
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Non-Compressing Codecs
Maximum Lost Packets Threshold:
Maximum number of total packets lost during uncompressed transmission.
Value range: 0 ... 255
7-97
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Compressing Codecs
Maximum Lost Packets Threshold:
Maximum number of total packets lost during compressed transmission.
Value range: 0 ... 255
7-98
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
General Data
"Passwords" Tab
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-99
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Admin Password:
Password for access to the workpoints administration area.
The admin password cannot be read from a device.
NOTE: UI does not intend to indicate the existence of the password but only to set it up.
.When you set it to the device, the device sets it in its database but DLS cannot know that since an
error message is displayed when you try to read it for confirmation.
You can set the admin password but you cannot be aware of the admin password that the device has.
User Password:
Password for access to the workpoints user area.
The user password for an OpenStage V3.0 or higher,can be forced to be changed by the phone user on its next
use.
The user password cannot be read from a device.
NOTE: Although it can be managed by DLS there is no possibility to know the user password value
or acknowledge password changes realized over WBM pages or directly over the physical device
itself.
7-100
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Directory Guard
Directory Screen Password Guard required
This checkbox activates password protection for the directory screen. To use the screen, you must enter the
standard user password.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-101
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Password Policy
Password change required at next Login
When activated, the user will be required to change the password on its next use in order to access the user menu
(including web pages) or to disengage phone lock.The setting will remain as active until the phone user changes
the password or the change password request is cancelled.
Password Setup
Minimum Number of Characters present in a password
Uppercase Chars required
Number of capital letters the password must contain.
Value range: 0 ... 24
0 = no check
7-102
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Digits required
Number of digits the password must contain.
Value range: 0 ... 24
0 = no check
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-103
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Password Status
Status Admin Password
Status of the admin password.
Possible Options:
Active
Suspended
Disabled
Active
Suspended
Disabled
7-104
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Password History
Admin Password History Count:
Minimum number of admin passwords to store in the history file. New passwords must not match any password
in the history file.
Value range: 0 99
User Password
Time and date of user password expiry.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-105
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Service Agent
Checkbox for activating and deactivating the service agent.
Probe Interface
Checkbox for activating and deactivating the probe interface.
Test Interface
Checkbox for activating and deactivating the test interface.
CTI Interface
Checkbox for activating and deactivating the CTI interface.
Bluetooth Interface
This checkbox is activated if you want to activate the Bluetooth interface on OpenStage telephones.
7-106
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Phone Manager
This checkbox is activated if you want to enable the interface between OpenStage telephones and Phone
Manager.
Phone Manager is a PC application for managing particular phone data.
USB Interface
If this checkbox is activated, the USB interface on the IP device can be accessed (OpenStage 60 and OpenStage
80 only).
Debug Interface
Checkbox for activating and deactivating the debug interface.
WBM Interface
Checkbox for activating and deactivating the WBM interface.
NOTE: Please note that if you deactivate the WBM interface, you can only reactivate it via DLS as
the WBM is no longer available for this.
SNMP Interface
Checkbox for activating and deactivating the SNMP interface (network management function).
Resource Sharing
Checkbox for activating and deactivating resource sharing (shared use of mouse and keyboard).
PC Interface
This checkbox is activated if you want to use the PC interface.
FTP
This checkbox is activated if you want to enable the FTP interface on the OpenStage telephone.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-107
workpoint-configuration.fm
IP Devices
IP Phone Configuration
USB Backup/Restore
If this checkbox is activated, IP device data (such as, the screensaver) can be backed up/restored over the USB
interface. Codecs Backup/Restore feature must be called directly on the relevant IP device (OpenStage 60 and
OpenStage 80 only).
FIPS
Checkbox for enabling / disabling workpoint-booting in FIPS mode.
Checkbox is disabled by default.
NOTE: A phone restart is required.
CEE Ports
Enable or disable the Comms Channel Extender (CCE) ports for both TCP (port 65531) and UDP (port 65530)
access.
Possible Options:
Disable all
Enable all
TCP only
UDP only
Password required
No Password
Unavailable
7-108
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
This tab allows to import or remove the Web Based Management (WBM) SSL Server Certificate. This certificate
is used for the device WBM interface (e.g. for device administration via a web browser). When no certificate is
present, the factory default WBM SSL Certificate is used.
Status Active/Import:
Content is automatically specified after import depending on whether active and/or imported certificates exist and
whether these are different or identical.
Possible options:
no certificate
different
equal
no active certificate
no imported certificate
Activate certificate
The imported certificate will be activated with the next saving. By activating an empty certificate, the certificate at
the end device will be deleted.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-109
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Serial Number:
Serial number of the active or imported certificate (display only).
Owner:
Owner of the active or imported certificate (display only).
Issuer:
Issuer of the active or imported certificate (display only).
Valid from:
Start of validity for the active or imported certificate (display only).
Valid to:
End of validity for the active or imported certificate (display only).
Key Algorithm
Key algorithm for the active or imported certificate (display only).
Key Size
Key size for the active or imported certificate (display only).
Fingerprint (SHA-1):
Test algorithm SHA-1 (160 bits/20 characters) for the active or imported certificate (display only).
7-110
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Alarm Status:
Current alarm status for the active or imported certificate (display only).
Possible values:
valid
expired
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-111
workpoint-configuration.fm
IP Devices
IP Phone Configuration
This tab allows to import or remove server CA (Certificate Authority) Certificates to authenticate the HTTPS server
used for file transfer. Up to two certificates can be imported to the device. See Section 6.3.5, "HTTPS Server
Configuration". For further configuration, see Section 7.1.7.10, ""Authentication Policy" Tab".
Index
Index of the certificate.
Status Active/Import:
Content is automatically specified after import depending on whether active and/or imported certificates exist and
whether these are different or identical.
Possible options:
no certificate
different
equal
no active certificate
no imported certificate
7-112
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Activate certificate
The imported certificate will be activated with the next saving. By activating an empty certificate, the certificate at
the end device will be deleted.
Owner:
Owner of the active or imported certificate (display only).
Issuer:
Issuer of the active or imported certificate (display only).
Valid from:
Start of validity for the active or imported certificate (display only).
Valid to:
End of validity for the active or imported certificate (display only).
Key Algorithm
Key algorithm .
Key Size
Key size.
Fingerprint (SHA-1):
Test algorithm SHA-1 (160 bits/20 characters) for the security certificate.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-113
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Alarm Status:
Current alarm status.
Possible values:
valid
expired
7-114
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
For parameter descriptions, please see Section 7.1.7.5, ""HTTPS Server CA Certificates" Tab".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-115
workpoint-configuration.fm
IP Devices
IP Phone Configuration
For parameter descriptions, please see Section 7.1.7.5, ""HTTPS Server CA Certificates" Tab".
7-116
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
For parameter descriptions, please see Section 7.1.7.5, ""HTTPS Server CA Certificates" Tab"
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-117
workpoint-configuration.fm
IP Devices
IP Phone Configuration
For parameter descriptions, please see Section 7.1.7.5, ""HTTPS Server CA Certificates" Tab"
7-118
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
This tab allows to define how secure connections are authenticated by the device.
Send URL Authentication Policy:
Authentication of the Send URL HTTPS Server is defined here, please see Section 7.1.19.3, ""Send URL Server
CA Certificate" Tab".
Possible values:
None
Trusted
Full
None
Trusted
Full
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-119
workpoint-configuration.fm
IP Devices
IP Phone Configuration
None
Trusted
Full
None
Trusted
Full
None
Trusted
Full
Trusted
Full
7-120
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
True
False
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-121
workpoint-configuration.fm
IP Devices
IP Phone Configuration
This tab allows to import or remove one client certificate for authentication of the device against the HTTPS server
used for file transfer. This is required if the HTTPS server is configured for mutual authentication.
For parameter descriptions, please see Section 7.1.7.4, ""WBM Server Certificate" Tab"
7-122
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
PIN Mode:
Possible options:
No PIN
Access data is sent unencrypted to the IP Device.
Default PIN
A standard PIN is used for several IP Devices. This is generated automatically by the DLS (see Section 6.9.1,
""Secure mode" Tab").
Individual PIN
An individual PIN is created for the selected IP Device.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-123
workpoint-configuration.fm
IP Devices
IP Phone Configuration
7.1.8 Telephony
Call: Main Menu > IP Devices > IP Phone Configuration > Telephony
This area features the following components:
General Data
"Telephony" Tab
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
7-124
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Emergency Number:
Contains the phone number that can be dialed in an emergency.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-125
workpoint-configuration.fm
IP Devices
IP Phone Configuration
General Data
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
7-126
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
SRSR enabled:
Checkbox for activating small remote site redundancy.
Only available in HFA workpoints.
Automated Switchback:
Checkbox for activating the option for automatic switchback to the main system.
Only available in HFA workpoints.
7-127
workpoint-configuration.fm
IP Devices
IP Phone Configuration
TC_Test
TC_TEST Retry Count:
Specifies the number of positive attempts permitted when switching back to the main system.
Value range: 1 ... 255
Only available in HFA workpoints.
7-128
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
General Data
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-129
workpoint-configuration.fm
IP Devices
IP Phone Configuration
7-130
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Operator Code(s):
Number/code for connection to the operator.
Only available for devices in the OpenStage family.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-131
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Emergency number(s):
One or more emergency numbers can be entered here.
Only available for devices in the OpenStage family.
Not used
7-132
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Unchanged
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-133
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Local Code
Digit or short digit string for dialing a particular prefix, for example.
International Code
Digit string, such as, a prefix, that is dialed at the beginning of the dialing operation using a particular digit.
7-134
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
General Data
"Time" Tab
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-135
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Date / Time:
Enter current date and time. Manual entry is only necessary if this information is not automatically transmitted
(for example, PBX or DHCP server).
Format Settings
Date Format:
Format for date entry. Manual entry is only necessary if this information is not automatically transmitted by the
communications system (for example, OpenScape Voice).
Possible options:
DD.MM.YY
Example: 05.10.06 for 5.10.2006
YY-MM-DD
Example: 04-10-06 for 5.10.2006
MM/DD/YY
Example: 10/05/06 for 5.10.2006
Time Format:
Time format.
Possible options:
7-136
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
24 hours
12 hours
Timezone Offset
Timezone Offset:
Time offset from UTC (Coordinated Universal Time) in minutes.
Value range: -720 ... 720
Examples: 60 (phone residing in Munich); -480 (phone residing in Los Angeles, USA).
Not set
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-137
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Australien 2008+ (ACT, New South Wales, South Australia, Tasmania, Victoria)
Brasilia
Canada
Canada (Newfoundland)
Europe (AT, BE, HR, DK, FR, DE, HU, IT, LU, NL, NO, PL, SK, ES, SE, CH)
Europe (FI)
Mexico
United States
NTP Settings
Time Source:
Source from where time information is adopted.
Possible options:
System
The time information is obtained from the communication platform.
SNTP
The time information comes from the SNTP server (if available).
NTP Password:
If required, a password is entered here for the SNTP server. This parameter is only available for OpenStage
telephones.
7-138
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
General Data
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-139
workpoint-configuration.fm
IP Devices
IP Phone Configuration
The settings in the table are made for devices in the OpenStage family because the specification of multiple
alternative codecs in these telephones is performed via a list of individual codecs.
Codec Configuration:
Set Codec for WLAN-Phones.
Possible options:
7-140
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Codec:
Audio transmission principle (codec) used.
Possible options:
G.711 Preferred
For the optiPoint 400 family.
G.723 Preferred
For the optiPoint 400 family.
G.723 Always
For the optiPoint 400 family.
Compression:
Compression procedure when the "LoBand" codec is selected.
Possible options:
G.723
G.729
Jitter Buffer:
Buffering duration (number of data packets).
Possible options:
Short
two packets
Long
six packets
Normal
four packets
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-141
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Packet Size:
Possible options:
10mS
20mS
30mS
Automatic
G.722 Codec:
Checkbox for activating the G.722 codec.
Allow HD Icon:
Checkbox for activating the HD Audio icon via DLS.
This feature controls the showing of the HD Wideband Audio Icon.This function is enabled by default.
10 mS
20 mS
30 mS
Automatic
Codec Type
Audio transmission principle (codec) used.
Possible options:
G.711
G.722
G.729
7-142
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Packet Size
Size of the packet used to send the audio data packages. The entry is in milliseconds.
Automatic
10 ms
20 ms
30 ms
Codec Rank
Each available codec is assigned a priority. This is used when negotiating codecs between two devices. Value
range: A number between 1 and the number of available codecs.
Codec allowed
Codec usage can be explicitly allowed or denied.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-143
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Codec:
Audio transmission principle (codec) used.
Possible options:
G.711 Preferred
For the optiPoint 400 family.
G.723 Preferred
For the optiPoint 400 family.
G.723 Always
For the optiPoint 400 family.
Compression:
Compression procedure when the "LoBand" codec is selected.
Possible options:
G.723
G.729
Jitter Buffer:
Buffering duration (number of data packets).
Possible options:
7-144
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Short
two packets
Long
six packets
Normal
four packets
Packet Size:
Possible options:
10mS
20mS
30mS
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-145
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Silence Suppression
Checkbox for activating silence suppression.
Microphone disable
Checkbox for deactivating the microphone.
Loudspeech enable
Checkbox for activating the speakerphone function.
Music on Hold
Checkbox to activate Music on Hold.
7-146
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Prompt
An incoming pickup call is signaled by an alert on the phone GUI. As soon as the user goes off-hook or presses
the speaker key, the pickup call is accepted. Alternatively, the user can press the corresponding function key,
if configured.
Notify
An incoming pickup call is signaled by an alert on the phone GUI. To accept the call, the user must confirm
the alert or press the corresponding function key, if configured.
FPK only
An incoming pickup call is signaled at the corresponding function key only. To accept the call, the user must
press the function key.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-147
workpoint-configuration.fm
IP Devices
IP Phone Configuration
No.
SIP
HFA
Frequencies (Hz)
f1
f2
f3
c1
c2
c3
Yes
Yes
457
571
615
45
45
45
Yes
Yes
696
762
1067
30
30
30
Yes
Yes
400
444
500
35
35
35
Yes
Yes
1067
889
696
50
50
50
Yes
Yes
762
800
889
30
30
30
Yes
Yes
1000
1143
1333
40
40
40
Yes
Yes
400
457
593
50
50
50
Yes
Yes
533
667
90
150
60
Ringer Sequence:
Possible Options:
0.7 sec ON, 0.7 sec OFF, 0.7 sec OFF, 3 sec OFF
Lower IL Ringer
Name of the file that contains the distinctive ringtone to be used in place of the normal ringer for calls from a Lower
Impact level.
Ringer Settings (HFA)
Ringer Mode
Possible Values:
HiPath
Local Ringer
7-148
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
BLF
BLF Alerting
Optical alerting by key.
Possible Values:
Beep
Ring
Headset
Headset Mode
Connection mode of headset.
Possible Values:
Wired Headset
Cordless Headset
Conference Unit
Key klick
Volume
Defines the volume of key clicks.
Possible Values:
Off
Low
Medium
High
Keys
Defines which keys shall have audible clicks.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-149
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Possible Values:
Keypad only
All keys
7-150
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-151
workpoint-configuration.fm
IP Devices
IP Phone Configuration
General Data
"SNMP" Tab
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
7-152
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
SNMP Active
Checkbox for activating the SNMP function.
Trap Community:
SNMP community string for the SNMP manager receiving trap messages.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-153
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Diagnostic Traps
Diagnostic Traps active
If this checkbox is active, diagnostic traps are sent.
7-154
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-155
workpoint-configuration.fm
IP Devices
IP Phone Configuration
7.1.14 Applications
Call: Main Menu > IP Devices > IP Phone Configuration > Applications
This area features the following components:
General Data
"WAP" Tab
"Java" Tab
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
7-156
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Gateway Address:
IP address or host name of the WAP server.
Port Number:
Port number of the WAP server.
Connection type:
Protocol type for connection to the WAP server.
Possible options:
HTTP
WSP
Homepage:
URL of the splash screen where the WAP home page is located.
Username
User ID for identification at the WAP server
Password:
Password for the user ID.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-157
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Username:
User ID for identification at the HTTP gateway.
Password:
Password for the user ID.
Java Midlets
Downloading of Java Midlets allowed
If this checkbox is activated, you can download Java midlets to the workpoint.
7-158
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-159
workpoint-configuration.fm
IP Devices
IP Phone Configuration
These are server-side applications which communicate with the phone software via a specially defined XML
interface. The Unified Messaging system HiPath Xpressions also uses this interface. The interface enables the
workpoint to send user entries, to display data in textual and graphic form, and to control calls.
To set up an XML application on the workpoint, the following specifications are required: a freely selectable user
name, communication protocol to be used; server port to be used; start address of the server-side program.
XML applications are only available in OpenStage 60/80.
XML Applications
Application Name (Server):
This is the name of the HTTP servlet, and it is used internally by the workpoint software to identify the application.
For DLS XML applications, the names must be entered unchangend.
Possible values:
DeploymentService
LocationService
NewsService
7-160
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
MakeCall
Display Name:
This name is used for listing the application on the workpoint menu.
Program Name:
Path of the start file of the server-side program, in relation to the server address. For DLS XML applications, enter
the WEB application name, followed by the HTTP servlet name.
Server Address:
IP address of the server on which the program is running. For DLS XML Applications enter the IP address of the
DLS Server; for Multinode installation, enter the IP address of the cluster.
Example: 192.168.1.150
Server Port:
Port used by the server-side program for receiving data from the workpoint.
For DLS XML Applications use port 18080, as only HTTP is supported.
For OSV Assistant XML applications use 7789.
Examples: 80 (Apache default port); 8080 (Tomcat default port).
Transport:
Transport protocol used for transmitting XML data.
Possible options:
HTTP
HTTPS
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-161
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Instance Type:
Selection of the type of instance.
Possible options:
Normal
Xpressions
Phonebook
Icon URL:
URL of the application icon (not yet implemented).
Mode Key:
Select a mode key to start the application.
Possible options:
No Mode Key
Number of Tabs:
The number of embedded tabs within the XML application to be shown on phone display.
Value range: 0 ... 3
NOTE: For an XML-application with a number of Tabs > 0, one of the entries between Tab 1 Application Name and Tab 3 Application Name must be set to the same value as the Application Name
(Server) that it is associated with. When the XML application is started, the tab which has the same
name as the XML application is the tab that initially gets focus.
7-162
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-163
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Enable Application
Switch to enable application.
Autostart
Switch to enable autostart of application.
Restart Application
Switch to enable restart of application, if it is already running.
7-164
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
The parameters described below are available once for the currently active certificate and once for the imported
certificate.
Index:
Serial number of the CA certificate.
Status Active/Import:
Specifies whether a certificate is registered as imported and/or active on the phone. The five statuses listed below
are possible.
Possible values:
no certificate
different
equal
no active certificate
no imported certificate
Serial Number:
Serial number of the certificate (display only).
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-165
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Owner:
Owner of the certificate (display only).
Issuer:
Issuer of the certificate (display only).
Valid from:
Start of validity for the certificate (display only).
Valid to:
End of validity for the certificate (display only).
Key Algorithm
Key algorithm.
Key Size
Key size.
Fingerprint (SHA-1):
Test algorithm SHA-1 (160 bits/20 characters) for the security certificate.
7-166
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Alarm Status:
Displays the duration of validity for certificates when searching for certificates due to expire.
Possible values:
valid
expired
Activate certificate
Checkbox for activating the certificate. The active certificate is used to encrypt calls. The imported certificate will
be activated with the next saving. By activating an empty certificate, the certificate at the end device will be
deleted.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-167
workpoint-configuration.fm
IP Devices
IP Phone Configuration
7-168
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
7.1.15 LDAP
Call: Main Menu > IP Devices > IP Phone Configuration > LDAP
This area features the following components:
General Data
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-169
workpoint-configuration.fm
IP Devices
IP Phone Configuration
NOTE: LDAP Server Settings are also applicable for OpenStage 15/20 (SIP only), OpenStage 40
HFA & OpenScape Desk Phone IP 35 G /IP 35 G Eco / 55 G HFA phones.
LDAP Server Address:
IP address or host name of the LDAP server.
LDAP Transport:
Transport protocol used to transmit LDAP data.
Possible options:
TCP
TLS
LDAP Authentication:
Option for selecting the LDAP access.
Possible options:
Anonymous
Simple
7-170
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
LDAP User:
User name for authenticated LDAP access.
LDAP Password:
Password for authenticated LDAP access.
LDAP Digest:
Enter LDAP digest.
This item is grayed out.
10
60
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-171
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Index
Certificate index number.
Status Active/Import:
Content is automatically specified after import depending on whether active and/or imported certificates exist and
whether these are different or identical.
Possible options:
no certificate
different
equal
no active certificate
no imported certificate
Activate certificate
The imported certificate will be activated with the next saving. By activating an empty certificate, the certificate at
the end device will be deleted.
7-172
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Owner:
Owner of the active or imported certificate (display only).
Issuer:
Issuer of the active or imported certificate (display only).
Valid from:
Start of validity for the active or imported certificate (display only).
Valid to:
End of validity for the active or imported certificate (display only).
Key Algorithm
Key algorithm.
Key Size
Key size.
Fingerprint (SHA-1):
Test algorithm SHA-1 (160 bits/20 characters) for the security certificate.
7-173
workpoint-configuration.fm
IP Devices
IP Phone Configuration
NOTE: The value of the imported certificate is updated periodically dependent on the settings in
Administration > Alarm Configuration > "Settings" Tab > Alarm Configuration for Expiring
Certificates > Interval. Therefore it might be greater than the value of the active certificate until the
next update.
Alarm Status:
Current alarm status.
Possible values:
valid
expired
7-174
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
General Data
"Locks" Tab
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-175
workpoint-configuration.fm
IP Devices
IP Phone Configuration
7-176
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
NOTE: By clicking on a feature function, the feature shall be grayed out in the phones WBM menu.
The following functions can be locked in the configuration menus by activating the relevant checkbox:
1-Country options
The user can select a country from a list to adapt the phone to country specific conditions.
2-Language
The user can set the language for the user menu.
3-Date / Time
The user can set the local time, the current date, and the daylight saving time.
4-Call deflection
The user can activate or deactivate call deflection.
5-Call forwarding
The user can activate or deactivate call forwarding.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-177
workpoint-configuration.fm
IP Devices
IP Phone Configuration
7-Call duration
The user can determine whether the call duration is indicated on the display.
Only available in optiPoint workpoints.
8-Call waiting
The user can determine whether a second call is allowed during a connected call. If not, the caller hears the busy
tone.
9-Call transfer
The user can allow call transfer.
10-Transfer call
The user can enable or disable the posibility to interlink an active and a held call.
11-Contrast
The user can set the contrast for the display.
12-Dialing mode
The user can determine whether a number only or, alternatively, a name can be used for dialing.
Only available in optiPoint workpoints.
13-Call display
The user defines which information about the caller is displayed on an incoming call.
Only available in optiPoint workpoints.
7-178
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
14-Daylight Saving
The user can set the daylight saving time.
16-CFNR timer
The user can set the delay time that passes before a call is forwarded, if Call Forwarding on No Reply is activated.
NOTE: if the option "Support of Server Based Features" is enabled (under IP Devices>IP Phone
Configuration > Features> "Server based features" Tab ) the CFNR delay timer is not configurable
(greyed out).
18-Music on hold
The user can determine whether the music on hold stored in the phone is used. If music on hold is activated, it is
played as soon as the phone is put to hold.
20-Message waiting
The user can determine whether new messaes in the mailbox are signaled by a LED.
Only available in optiPoint workpoints.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-179
workpoint-configuration.fm
IP Devices
IP Phone Configuration
22-Conference
The user can allow system based conferences.
Only available in optPoint workpoints.
23-Local conference
The user can allow local 3-party conferences.
32-Auto answer
The user can determine whether incoming calls are accepted automatically by the CTI application which is
connected to the phone.
34-Auto reconnect
The user can determine whether a held call can be reconnected automatically by the CTI application.
7-180
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
38-Inactivity timeout
The user can set the delay time between the last entry and the return to the idle state.
43-Deflect address
The user can enter resp. modify the target number for call deflection.
44-Line settings
The user can modify the settings of a line key.
46-Call park
The user can allow call parking.
47-Call pickup
The user can allow pickup of a parked call.
48-Immediate dialing
The user can allow immediate dialing.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-181
workpoint-configuration.fm
IP Devices
IP Phone Configuration
53-Transfer on Ring
The user can determine whether a call is transferred as soon as the third participants phone rings, even if the
transferring participant has not hung up.
55-Call Recording
The user can activate call recording.
Only available in optiPoint workpoints.
7-182
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
57-Transfer on Hangup
The user can determine whether, when one call is active and another call is on hold, the user can connect these
calls by hanging up.
60-Audio Settings
The user can modify settings like ringtones and room character.
Only available in OpenStage workpoints.
61-Loudspeaker
The user can activate or deactivate handsfree talking.
Only available in OpenStage workpoints.
62-Forwarding Alert
The user can allow forwarding alert.
63-Join in Conference
The user can determine whether visual or acoustical warning notifications indicate an incoming call while call
forwarding is active.
Only available in OpenStage workpoints.
64-Bluetooth
The user can activate or deactivate bluetooth connectivity.
65-Display Skin
The user can choose the display theme.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-183
workpoint-configuration.fm
IP Devices
IP Phone Configuration
66-Screensaver
The user can activate the phoness screensaver and set the delay time for starting the screensaver.
Only available in OpenStage 60/80 workpoints.
68-BLF
The user can define how an incoming call for the phone supervised by the BLF key shall be displayed.
69-Toggle associate
The user can enable or disable the connecting of a first call and a second call by going on-hook. When "Toggle
associate" is activated, the following procedure will ensue: The user has accepted a second call, whereby the first
call is put to hold. As soon as the user has alternated back to the first call, and then again to the second call, he/
she can connect both calling parties by going on-hook.
Available in all OpenStage workpoints.
71- Headset
The user can define the type of headset connected to the phone.
Available for OpenStage 40/60/80 SIP/HFA.
7-184
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
76- Video On
The user can activate video calls.
Available for OpenStage 60/80 SIP/HFA.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-185
workpoint-configuration.fm
IP Devices
IP Phone Configuration
7-186
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Available for OpenStage 15/20/20E/40/41/60/80 & OpenScape Desk Phones 35 G/ 35 G Eco / 55 G (SIP only).
87- Delete Entry
The user can configure whether to delete calls log entries in case there is a call to an entry in Missed calls list.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-187
workpoint-configuration.fm
IP Devices
IP Phone Configuration
The following functions can be locked in the configuration menus by activating the relevant checkbox:
1-Abbreviated dialing
The user can set up abbreviated dialing numbers.
Only available in optiPoint workpoints.
2-User password
The user can change his password.
3-Phone lock
The user can lock the phone. If the phone is locked, no unauthorized person can call from this phone in a regular
manner or modify any settings. Only emergency numbers and pre-defined numbers from the dial plan can be
dialed.
NOTE: Phone Lock function can only be configured via DLS (not via Web Based Management
(WBM) nor locally).
If the function is locked,the menu is still visible, yet grayed out.
4-Memory
The user can delete all abbreviated dialing numbers and restore the factory settings.
Only available in optiPoint workpoints.
7-188
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
General Data
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-189
workpoint-configuration.fm
IP Devices
IP Phone Configuration
7-190
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-191
workpoint-configuration.fm
IP Devices
IP Phone Configuration
International Mobility ID
If this checkbox is activated, the device automatically adds the local country code to the extension, in addition to
the trunk number and local area code when a mobile user logs on. The international code is configured under IP
Devices > IP Phone Configuration > Dialing Properties > "Dialing Properties" Tab -> International Dial
Prefix.
Example: The user logs on to the device using the extension/mobility ID "31434". If the checkbox is activated, the
device sends the number "498972231434". Otherwise, the device sends the number "8972231434".
7-192
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
General Data
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-193
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Mobility Mode:
Determines how user data is managed with HFA Mobility. User data falls into two categories :
a) Common User Data (Screensavers,ring tones,volumes,room character,skin)
b) Private Data (Phone Book & associated pictures,Call Log & the user password)
Phones can be configured to support Basic, Data Privacy or Data Mobility modes of operation.
Basic
Default operation where user data is accessible to all users. Users are allowed to log on at any phone.
Data Privacy
Data Privacy forms an enhancement to the Basic HFA Mobility Mode in such way that Private Data for a
previous visitor or the owner of the phone are deleted or hidden whilst a visitor is logged on to a phone.
NOTE: Administrators are able to set the Mobility Mode from Basic to Data Privacy & vice versa.
Data Mobility
Data Mobility forms an enhancement to the Data Privacy Mode by supporting the transfer of a limited set of
additional user data items between phones that have been used by a user.
Private Data are made available to users wherever they are logged on, and are securely stored whilst they are
logged off. In addition the User Password is transferred along with the user as they move between phones.
NOTE: If an error is encountered when saving Mobility data, the user is warned & subsequently
informed when the problem is cleared.
7-194
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
7.1.19 Keysets/Keylayout
Call: Main Menu > IP Devices > IP Phone Configuration > Keysets/Keylayout
This area features the following components:
General Data
"Keysets" Tab
"Destinations" Tab
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-195
workpoint-configuration.fm
IP Devices
IP Phone Configuration
LED on Registration
If the checkbox is activated, the successful workpoint registration after a phone restart will be indicated.
Only available in SIP workpoints.
Rollover Ring:
Type of alerting to be used in the case that, during an active call, an incoming call arrives on a different line.
Possible options:
No ring
Alert Ring
Standard
Alerting
7-196
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Call hold
The original call is put on hold.
Release
The connection to the original call is cleared down (the call is ended).
Forwarding indicated
Checkbox for activating alerting on a line key when call forwarding is active for its destination.
Only available in SIP workpoints.
Single button
The action associated with the line key is executed as soon as the button is pressed, regardless of whether
or not the handset is in the cradle.
Preselection
Press the line key to preselect a line. This line is used the next time you seize a line (by lifting the handset,
for example).
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-197
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Bridging Priority:
Possible options:
Show Focus
Checkbox for activating the display showing which line is currently active (line has the focus).
Only available in SIP workpoints.
No preference
7-198
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
No preference
Forwarding Indication
If this checkbox is activated and station forwarding is active for this line, the LED of the line key blinks.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-199
workpoint-configuration.fm
IP Devices
IP Phone Configuration
10
15
20
30
40
50
60
7-200
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Index
Name of the key layout function.
Lock Key
Checkbox for locking the function key.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-201
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Device
Specifies the device to which the relevant layout applies.
Possible options:
Base device
Level
Key level for the Shift functionality.
Possible options:
1. Level
2. Level
3. Level
4. Level
Fixed Keys
Fixed Keys are assigned to a fixed key number. They cannot be deleted or created on the IP Device.
Key number
Number of the key assigned the relevant function.
Only available in SIP workpoints.
Key function:
The following key functions are supported:
Key unused
7-202
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Selected dialing
Abbreviated dialing
Repeat dialing
Missed calls
Voice messages
Forwarding
Loudspeaker
Mute
Ringer off
Hold
Alternate
Blind Transfer
Deflect
Setup menu
Room echoing
Room muffled
Shift
Notebook
Settings
Phone lock
Conference
Local Conference
Headset
Do not disturb
Group pickup
Repertory dial
Line
Feature Toggle
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-203
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Swap screen
Mobility
Call park
Call pickup
Cancel/Release
Ok Confirm
Callback Request
Cancel Callback
DSS
State Key
Call waiting
Immediate Ring
Preview Key
Call Recording
AICS Zip
Server Feature
Available for free programmable keys as well as for Fixed Keys.
BLF
Start Application
Available for free programmable keys as well as for Fixed Keys.
Send URL
Sends a configurable HTTP or HTTPS request to a remote server. Assigned to & available for free
programmable keys as well as for Fixed Keys.
The request string contains the Web server user ID, Web server password, Parameters,the phones IP
address & call number and the Symbolic Name
e.g
userid=jdoe&password=00secret&mode=remote&action=start&
ipaddress=192.168.1.244&phonenumber=3338&symbn=key4
Built-in Forwarding
Only available for Fixed Keys.
Built-in Release
Only available for Fixed Keys.
7-204
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Built-in Redial
Only available for Fixed Keys.
2nd Alert
Corporate Directory
NOTE: The Corporate Directory function is configured to the V3R3 WP_HI & WP_LO phones.
Key:
Indicates whether this key is a Fixed Keyor a freely programmable key.
Key label
A key label can be entered here for every key in the case of Self labeling Keys workpoints (for example,
optiPoint 420 standard).
Only available in SIP workpoints.
NOTE: For fixed keys,the key label remains unchanged when the Administration sets a different key
function to the default one.
7-205
workpoint-configuration.fm
IP Devices
IP Phone Configuration
$Q = clear (CL)
$R = consult (CS)
$S = OK
$T = Pause (PA)
Forwarding Type
Possible options:
on busy
on busy external
on busy internal
on no reply
on no reply external
on no reply internal
unconditionally
unconditionally external
unconditionally internal
DTMF Sequence
DTMF Sequence for this target.
Toggle text
Label for the "Feature Toggle" key function.
Only available in SIP workpoints.
7-206
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Application Name:
Name of the XML application to be started with the function key.
Protocol
Protocol of Web Server.
Possible options:
HTTP
HTTPS
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-207
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Port
Port number of web server: If the port is null, the fully qualified URL will not include the port element.
Path
Directory path and name of the program or web page.
Examples: servlet/IppGenericServlet or webpage/checkin.xml
The path should have a slash at the beginning and no slash at the end. If the slash at the beginning is missing, a
slash will be automatically inserted. If there is an additional slash at the end, it will be automatically removed. The
slashes in the path should be forward slashes (/). If backslashes (\) are used instead, the web server may not
find the appropriate program or web page.
Parameters
Null, one, or more parameter-value pairs in the format <parameter>=<value>, with each pair separated by an
ampersand (&), e. g. parameter1=value1¶meter2=value2. A comma (,) is not used as a separator
because it could be part of the key or value. If the key or value contains an ampersand, it must be replaced by
&.
The question mark will be automatically added between the path and the parameters. If there is a question mark
at the beginning of the parameters, it will be automatically stripped off.
HTTP Method
HTTP method to be used.
Possible options:
Get
Post
7-208
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Symbolic Name
Symbolic name known by the server. It is used for phone authentication by the server.
Push Support
Enables or disables push support.
Key Functionality
Possible options:
Unspecified Call
Unspecified
Address of record
Lines phone number and address of record.
Only available in SIP workpoints.
Realm
SIP realm for the lines address of record.
Only available in SIP workpoints.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-209
workpoint-configuration.fm
IP Devices
IP Phone Configuration
UserID
Only available in SIP workpoints.
Password
Only available in SIP workpoints.
Ring
Only available in SIP workpoints.
Hunt ranking
Only available in SIP workpoints.
Shared type
Possible options:
Private
Shared
Unknown
Intrusion allowed
Checkbox for enabling line intrusion.
Only available in SIP workpoints.
7-210
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Ordinary
Hot Line
Warm Line
Show in Overview
Checkbox for activating the line display in the line overview.
Only available in SIP workpoints.
Position in Overview
Position of key in Line Overview.
Only available in SIP workpoints.
Short Description
Description of relevant line.
Only available in SIP workpoints.
Line Type
Possible options:
Normal
Direct
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-211
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Line Action
Possible options:
Consultation
Transfer
No Action
Ringing Delay
Time before ringing starts for an alerting call.
7-212
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
For a parameter description, please refer to IP Devices > IP Phone Configuration > LDAP > "CA Certificates"
Tab.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-213
workpoint-configuration.fm
IP Devices
IP Phone Configuration
General Data
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
7-214
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Transfer Mode:
You can choose the standards IEEE 802.11b (802.11b only), or IEEE 802.11b and IEEE 802.11g (mixed mode)
for data transfer.
The main difference between these standards is the transmission rate. IEEE 802.11g is almost five times faster
than the others. If devices in the WLAN use different standards, you must keep the default value (Mixed Mode).
If IEEE 802.11g is entered as a fixed value for transfer mode in the access point or WLAN router, select Mixed
Mode in this tab.
Possible options:
only 802.11b
Mixed Mode
Transmission Rate:
The transmission rate is the speed in Mbps at which data is transmitted in the WLAN. The transmission rate
depends on the transfer mode selected.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-215
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Possible options:
1.0 Mbps
2.0 Mbps
5.6 Mbps
6.0 Mbps
9.0 Mbps
11.0 Mbps
12.0 Mbps
18.0 Mbps
24.0 Mbps
36.0 Mbps
48.0 Mbps
54.0 Mbps
Channel:
WLAN radio channel. The channel is configured in the access point or the WLAN router.
Channel Range:
The available channel range in each case can be selected. The restriction is required in some countries due to
the fact that the use of channel 12 and 13 is not permitted. Possible values: channel 1-11: for example USA,
channel 1-13: for example Germany, channel 1-14: for example Japan.
Scan Channels:
Scan channel selection.
5%
7-216
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
10 %
20 %
40 %
100 %
Threshold Values
Roaming Threshold (%):
Minimum reception strength expressed as a percentage. If the reception strength of the access point currently
connected falls below this value, the handset searches for and connects to another access point with better
connectivity.
Fragmentation Threshold
Size at which voice packets are fragmented. Fragmenting data packets into smaller packets improves data
throughput in a WLAN when the network is running at high capacity.
Value range: 256 ... 2346 bytes.
Default value: 2346 bytes (no fragmenting).
RTS/CTS Threshold:
Minimum packet size in bytes required for transmitting an RTS (Request To Send). Smaller packets are
transmitted directly to the access point without an RTS.
Value range: 1 ... 2347 bytes.
Default value: 2347 bytes (RTS/CTS mechanism deactivated).
NOTE: Activating this mechanism may reduce data throughput.
Preamble Type
A preamble is set before each data packet is transmitted in a WLAN. It enables the receiver to synchronize with
the transmission timing.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-217
workpoint-configuration.fm
IP Devices
IP Phone Configuration
A long preamble ensures more stable synchronization. A short preamble enables higher data throughput.
Not all WLAN devices support both preamble types.
Possible options:
Long
Short
7-218
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
NOTE: Encryption protects data exchange in the WLAN. It does not protect data exchange with
Ethernet networks or the Internet.
Encryption:
This field enables you to select the encryption procedure.
Possible options:
None
Data is not encrypted for transmission in the WLAN.
WPA
WPA encryption.
WPA-PSK
WPA-PSK encryption.
WEP
WEP encryption.
WPA2
WPA2 encryption
WPA2-PSK (AES)
WPA2-PSK encryption
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-219
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Encryption WPA-PSK
WPA-PSK Encryption Type:
Possible options:
TKIP
Encryption using the TKIP protocol. Designed for use with WPA-PSK.
Pre-Shared Key:
Entry field for PSK encryption key.
Encryption WPA2-PSK
Pre-Shared Key:
Entry field for WPA2-PSK encryption key.
Encryption WPA2
OKC:
Checkbox for activating the Opportunistic Key Caching (OKC).
Encryption WEP
WEP Mode
Information on the WEP key length. For 128 bits, the key must consist of 13 ASCII characters or 26 hexadecimal
characters. For 64 bits, it must consist of five ASCII characters or 10 hexadecimal characters.
WEP Key:
Entry field for WEP encryption key.
7-220
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Open System
The WEP key is only used for data encryption, not for authentication.
Shared Key
The WEP key is also used for authentication in the WLAN. In other words, the handset can only log on to the
WLAN if it transmits the correct key.
Encryption WPA
WPA Encryption Type:
Possible options:
TKIP
Encryption using the TKIP protocol. Designed for use with WPA.
Encryption WPA2-PSK
Pre-Shared Key
Entry field for PSK encryption key.
Encryption WPA2
OKC
Switch to activate Opportunistic Key Caching (OKC).
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-221
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Location Server
If this checkbox has been enabled, the data for an existing location server is used.
7-222
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
U-APSD Support
U-APSD
Activate U-APSD.
unlimited max. 15
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-223
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Timeout
Timeout after seconds.
7-224
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-225
workpoint-configuration.fm
IP Devices
IP Phone Configuration
General Data
For information on general interface operation, see Section 5.4.2, "Work Area".
7-226
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Status Active/Import:
Content is automatically specified after import depending on whether active and/or imported certificates exist and
whether these are different or identical.
Possible values:
no certificate
different
equal
no active certificate
no imported certificate
Activate certificate
The imported certificate is automatically activated.
PKI Configuration
Shows PKI configuration of imported certificate.
Serial Number:
Serial number of the active or imported certificate (display only).
Owner:
Owner of the active or imported certificate (display only).
Issuer:
Issuer of the active or imported certificate (display only).
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-227
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Valid from:
Start of validity for the active or imported certificate (display only).
Valid to:
End of validity for the active or imported certificate (display only).
Key Algorithm
Key algorithm.
Key Size
Key size.
Fingerprint (SHA-1):
Test algorithm SHA-1 (160 bits/20 characters) for the security certificate.
Alarm Status:
Current alarm status.
Possible values:
valid
expired
7-228
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
The parameters described below are available once for the currently active certificate and once for the imported
certificate.
Index:
Serial number of the CA certificate.
Status Active/Import:
Specifies whether a certificate is registered as imported and/or active on the phone. The five statuses listed below
are possible.
Possible values:
no certificate
different
equal
no active certificate
no imported certificate
PKI Configuration
Name of PKI configuration.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-229
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Serial Number:
Serial number of the active or imported certificate (display only).
Owner:
Owner of the active or imported certificate (display only).
Issuer:
Issuer of the active or imported certificate (display only).
Valid from:
Start of validity for the active or imported certificate (display only).
Valid to:
End of validity for the active or imported certificate (display only).
Key Algorithm
Key algorithm.
Key Size
Key size.
Fingerprint (SHA-1):
Test algorithm SHA-1 (160 bits/20 characters) for the security certificate.
7-230
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
NOTE: The value of the imported certificate is updated periodically dependent on the settings in
Administration > Alarm Configuration > "Settings" Tab > Alarm Configuration for Expiring
Certificates > Interval. Therefore it might be greater than the value of the active certificate until the
next update.
Alarm Status:
Displays the duration of validity for certificates when searching for certificates due to expire.
Possible values:
valid
expired
Activate certificate
The imported certificate will be activated with the next saving. By activating an empty certificate, the certificate at
the end device will be deleted.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-231
workpoint-configuration.fm
IP Devices
IP Phone Configuration
UDP
TCP
TLS
UDP
TCP
7-232
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
TLS Renegotiation
When activated, access is allowed to TLS Servers that dont support secure TLS renegotiation (through RFC
5746).
When disabled, access to servers without secure TLS Renegotiation (according to rfc) is denied.
This checkbox is disabled by default.
SDES Status
Select the SDES status.
Possible options:
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-233
workpoint-configuration.fm
IP Devices
IP Phone Configuration
SDP Negotiation
Select the SDP negotiation.
Possible options:
SRTP only
Fallback to RTP
SRTP Encryption
SRTP Encryption Method
Selects the SRTP encryption method to be used.
Possible options:
SHA1-32
SHA1-80
Choice 1
Choice 2
7-234
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
UDP
TCP
TLS
UDP
TCP
TLS
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-235
workpoint-configuration.fm
IP Devices
IP Phone Configuration
General Data
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
7-236
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Authentication Type
Possible values:
none
EAP-TLS
LEAP
PEAP
EAP-TLS
Validate Server Certificate
If this checkbox is activated, the telephone checks the validity of the server certificate sent by the access point.
IMPORTANT: In the case of OpenStage V3R0 phones (or later) the Server Certificate flag is
controlled by 802.1x Authentication Policy under IP Devices > IP Phone Configuration > Security
Settings > "Authentication Policy" Tab. Therefore, whatever the value of Authentication Type, this
checkbox is greyed out, thus not editable
Please refer to Section 7.1.7.10, ""Authentication Policy" Tab".
Login Name:
Login name for identification.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-237
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Password:
Password for identification.
EAP-TTLS or PEAP
Provide support for IEEE 802.1x [802.1x] which is a standard for port-based network access control. 802.1x
provides an authentication framework where a user (or device) is authenticated by a central authority (in RADIUS
model) and where the user (or device) also authenticates the central authority. With this selection EAP-TTLS or
PEAP protocol does the extensible authentication.
MSCHAP Identity:
Device name for MSCHAP-V2 in PEAP or EAP-TTLS.
NOTE: If the new value PEAP is selected, the attribute MSCHAP Identity (Item: mschap-identity)
is enabled.
MSCHAP Password:
Password for MSCHAP-V2 in PEAP or EAP-TTLS.
The value is write-only.
NOTE: If the new value PEAP is selected, the attribute MSCHAP Password (Item: mschap-pw)
is enabled.
EAP-TTLS Digest
Challenge digest for MD challenge with EAP-TTLS.
The value is write-only.
7-238
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
EAP-FAST
EAP-FAST Secret:
Secret for EAP-FAST.
The value is write-only.
LEAP
Login Name:
Login name for identification on the access point/WLAN router.
Password:
Password for identification on the access point/WLAN router.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-239
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Status Active/Import:
Content is automatically specified after import depending on whether active and/or imported certificates exist and
whether these are different or identical.
Possible options:
no certificate
different
equal
no active certificate
no imported certificate
PKI Configuration
PKI configuration of the imported certificate.
7-240
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Serial Number:
Serial number of the active or imported certificate (display only).
Owner:
Owner of the active or imported certificate (display only).
Issuer:
Issuer of the active or imported certificate (display only).
Valid from:
Start of validity for the active or imported certificate (display only).
Valid to:
End of validity for the active or imported certificate (display only).
Key Algorithm
Key algorithm.
Key Size
Key size.
Fingerprint (SHA-1):
Test algorithm SHA-1 (160 bits/20 characters) for the security certificate.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-241
workpoint-configuration.fm
IP Devices
IP Phone Configuration
NOTE: The value of the imported certificate is updated periodically dependent on the settings in
Administration > Alarm Configuration > "Settings" Tab > Alarm Configuration for Expiring
Certificates > Interval. Therefore it might be greater than the value of the active certificate until the
next update.
Alarm Status
Current alarm status.
Possible values:
valid
expired
7-242
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Status Active/Import:
Content is automatically specified after import depending on whether active and/or imported certificates exist and
whether these are different or identical.
Possible options:
no certificate
different
equal
no active certificate
no imported certificate
PKI Configuration
PKI configuration of the imported certificate.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-243
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Serial Number:
Serial number of the active or imported certificate (display only).
Owner:
Owner of the active or imported certificate (display only).
Issuer:
Issuer of the active or imported certificate (display only).
Valid from:
Start of validity for the active or imported certificate (display only).
Valid to:
End of validity for the active or imported certificate (display only).
Key Algorithm
Key algorithm.
Key Size
Key size.
Fingerprint (SHA-1):
Test algorithm SHA-1 (160 bits/20 characters) for the security certificate.
7-244
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
NOTE: The value of the imported certificate is updated periodically dependent on the settings in
Administration > Alarm Configuration > "Settings" Tab > Alarm Configuration for Expiring
Certificates > Interval. Therefore it might be greater than the value of the active certificate until the
next update.
Alarm Status
Current alarm status.
Possible values:
valid
expired
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-245
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Status Active/Import:
Content is automatically specified after import depending on whether active and/or imported certificates exist and
whether these are different or identical.
Possible options:
no certificate
different
equal
no active certificate
no imported certificate
PKI Configuration
PKI configuration of the imported certificate.
7-246
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Serial Number:
Serial number of the active or imported certificate (display only).
Owner:
Owner of the active or imported certificate (display only).
Issuer:
Issuer of the active or imported certificate (display only).
Valid from:
Start of validity for the active or imported certificate (display only).
Valid to:
End of validity for the active or imported certificate (display only).
Key Algorithm
Key algorithm.
Key Size
Key size.
Fingerprint (SHA-1):
Test algorithm SHA-1 (160 bits/20 characters) for the security certificate.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-247
workpoint-configuration.fm
IP Devices
IP Phone Configuration
NOTE: The value of the imported certificate is updated periodically dependent on the settings in
Administration > Alarm Configuration > "Settings" Tab > Alarm Configuration for Expiring
Certificates > Interval. Therefore it might be greater than the value of the active certificate until the
next update.
Alarm Status
Current alarm status.
Possible values:
valid
expired
7-248
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
7.1.23 Diagnosis
Call: Main Menu > IP Devices > IP Phone Configuration > Diagnosis
This area features the following components:
General Data
For information on general interface operation, see Section 5.4.2, "Work Area".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-249
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Easy Trace
Pre-defined profiles facilitate the controlling of trace parameters. Common trace levels for all components can be
configured, as well as groups of parameters which belong to a specific functional area of the phone.
Set all Trace Levels to:
Activates all trace points in code from OpenStage phones. A different value may be set for each trace level.
Possible Options:
Off
Fatal
Error
Warning
Trace
Debug
7-250
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Call connection
DAS connection
Mobility problems
Sidecar problems
Speech problems
Tone problems
USB backup/restore
802.1x problems
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-251
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Trace Level
Activates particular trace points in code from the OpenStage phones and locates errors. A different value may be
set for each trace level.
Admin phonelet:
Possible options:
Off
Fatal
Error
Warning
Trace
Debug
Phonebook phonelet:
Same options as for Admin phonelet:
CSTA service:
Same options as for Admin phonelet:
Directory service:
Same options as for Admin phonelet:
Instrumentation service:
Same options as for Admin phonelet:
7-252
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
SIP Messages:
Same options as for Admin phonelet:
AGP/Java phonelet:
Same options as for Admin phonelet:
Bluetooth service:
Same options as for Admin phonelet:
7-253
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Help phonelet:
Same options as for Admin phonelet:
Communications service:
Same options as for Admin phonelet:
Journal service:
Same options as for Admin phonelet:
Mobility service:
Same options as for Admin phonelet:
Pot service:
Same options as for Admin phonelet:
7-254
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Sidecar service:
Same options as for Admin phonelet:
Transport service:
Same options as for Admin phonelet:
SIP Signalling:
Same options as for Admin phonelet:
Application Framework:
Same options as for Admin phonelet:
Service Framework:
Same options as for Admin phonelet:
H.323 Messages:
Same options as for Admin phonelet:
7-255
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Health service:
Same options as for Admin phonelet:
OBEX service:
Same options as for Admin phonelet:
Team service:
Same options as for Admin phonelet:
7-256
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Desktop phonelet:
Same options as for Admin phonelet:
Service Registry:
Same options as for Admin phonelet:
802.1x service:
Same options as for Admin phonelet:
H.323 Security:
Same options as for Admin phonelet:
HTTP service:
Same options as for Admin phonelet:
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-257
workpoint-configuration.fm
IP Devices
IP Phone Configuration
7-258
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
7-259
workpoint-configuration.fm
IP Devices
IP Phone Configuration
7-260
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-261
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Remote Trace
If this checkbox is active, the phones sends its trace data directly to the destination entered in Remote Trace
Destination.
User Notification
If activated, the phone user will be notified when a trace is performed on the phone.
7-262
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-263
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Download of all Diagnosis and Security Log Files (from DLS Server to Client PC)
Download Files ...
Starts downloading all diagnosis and security log files from phone to DLS Server as a .zip-file.
save immediately
10%
20%
30%
35%
40%
45%
50%
55%
60%
65%
70%
80%
7-264
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
90%
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-265
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Settings for Periodical Upload for Diagnosis Files and Security Logs
Open Central Configuration for:
By clicking on the string, the central configuration in Administration > Automatic Upload Diagnosis- and
Security Log Files is opened. The name of the destination mask is displayed in the text field.
Trace File
When active, the trace file of the IP Device is uploaded periodically.
7-266
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Phone Database
When active, the phone database file is uploaded periodically.
Core Files
When active, the core files of the are IP Device uploaded periodically.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-267
workpoint-configuration.fm
IP Devices
IP Phone Configuration
7-268
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Certificate
Status Active/Import:
Content is automatically specified after import depending on whether active and/or imported certificates exist and
whether these are different or identical.
Possible options:
no certificate
different
equal
no active certificate
no imported certificate
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-269
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Serial Number:
Serial number of the active or imported certificate (display only).
Owner:
Owner of the active or imported certificate (display only).
Issuer:
Issuer of the active or imported certificate (display only).
Valid from:
Start of validity for the active or imported certificate (display only).
Valid to:
End of validity for the active or imported certificate (display only).
Fingerprint (SHA-1):
Test algorithm SHA-1 (160 bits/20 characters) for the security certificate.
7-270
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
NOTE: The value of the imported certificate is updated periodically dependent on the settings in
Administration > Alarm Configuration > "Settings" Tab > Alarm Configuration for Expiring
Certificates > Interval. Therefore it might be greater than the value of the active certificate until the
next update.
Alarm Status
Current alarm status.
Possible values:
valid
expired
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-271
workpoint-configuration.fm
IP Devices
IP Phone Configuration
7.1.24 Miscellaneous
Call: Main Menu > IP Devices > IP Phone Configuration > Miscellaneous
This area features the following components:
General Data
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
7-272
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Country:
Country where the workpoint is operated. This parameter corresponds to the country setting on the device.
Possible options:
AR - Argentina
AT - Austria
AU - Australia
BE - Belgium
BR - Brazil
CA- Canada
CH- Switzerland
CL - Chile
CN - China
CZ - Czech Republic
DE - Germany
DK - Denmark
EE - Estonia
ES - Spain
FI - Finland
FR - France
GB - United Kingdom
HR - Croatia
HU - Hungary
IE - Ireland
IN - India
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-273
workpoint-configuration.fm
IP Devices
IP Phone Configuration
IT - Italy
JP - Japan
LT - Lithuania
LU - Luxembourg
LV - Latvia
MX - Mexico
NL - Netherlands
NO - Norway
NZ - New Zealand
PL - Poland
PT - Portugal
RU - Russian Federation
SE - Sweden
SG - Singapore
SK - Slovakia
TH - Thailand
TR- Turkey
US - United States
VN - Vietnam
ZA - South Africa
CY - Wales
Language:
Language to be used for local applications.
Possible options:
bg - bulgarian
ca - catalan
cs - czech
da - danish
7-274
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
de - german
el - greek
en - english
en - english (US)
es - spanish
et - estonian
fi - finnish
fr - french
hr - croatian
hu - hungarian
id - indonesian
it - italian
ja - japanese
lt - lithuanian
lv - latvian
mk - macedonian
ms - malayan
nl - dutch
no - norwegian
pl - polish
pt - portuguese
pt-Br - brazilian
ro - romanian
ru - russian
sk - slovak
sl - slovenian
sr - serbian (Cyrillic)
sr - serbian (Latin)
sv - swedish
sr - serbian
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-275
workpoint-configuration.fm
IP Devices
IP Phone Configuration
tr - turkish
zh - chinese
cy- welsh
English
German
French
Spanish
American
Italian
7-276
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-277
workpoint-configuration.fm
IP Devices
IP Phone Configuration
7-278
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Beep on Error
Checkbox for activating acoustic error signaling during communication with Microsoft RTC.
Only available in SIP workpoints.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-279
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Handset Name
Handset Name:
Name of the WLAN handset shown on the handsets display.
Value range: max. 16 alphanumeric characters.
Display Settings
Display Theme
Defines the layout of the graphical user interface on OpenStage phones.
Possible options:
Silver Blue
Anthracite Orange
0 (no timeout)
10
7-280
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
20
30
60
120
Display Brightness
Sets the display brightness.
Possible Optionen:
-3
-2
-1
Default
+1
+2
+3
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-281
workpoint-configuration.fm
IP Devices
IP Phone Configuration
1 min
5 min
30 min
60 min
2 hours
3 hours
4 hours
5 hours
6 hours
7 hours
8 hours
0 (no timeout)
10
20
30
60
120
7-282
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
Screensaver
Enable Screensaver
This checkbox enables the screensaver.
10
20
30
60
Phone Settings:
Not used Timeout (min):
Defines how long (in minutes) the telephone will remain inactive before its ends a particular status.
Example: Exit the configuration menu after a specified time.
10
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-283
workpoint-configuration.fm
IP Devices
IP Phone Configuration
20
30
60
120
No auto hide
10
20
30
60
120
7-284
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-285
workpoint-configuration.fm
IP Devices
IP Phone Configuration
7-286
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-287
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Lock Phone
Locks the phone.
7-288
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
General Data
"Files" Tab
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-289
workpoint-configuration.fm
IP Devices
IP Phone Configuration
NOTE: LDAP Templates are also deployable to OpenStage 15/20 (SIP only) & OpenScape Desk
Phone IP 35 G / 35 G Eco phones.
File Deployment
SW Image Name:
Name of the Software Image.
File Name:
Name of the file.
File Type:
Usage of the file.
NOTE: For many file types on the FTP server can be used for multiple purposes. In such cases, there
is a table entry for each usage. For instance, a WAV file can be used as a ringtone and as music on
hold. Ringtone and music on hold files must not exceed 1MB in size, while screensaver and logo files
should not be larger than 300kB.
Example: LOGO (OpenStage 40/60/80) , SCREENSAVER (OpenStage 40/60/80).
Server Type:
Protocol used by the server which provides the file.
Possible values:
7-290
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Phone Configuration
FTP
HTTPS
HTTPS URL:
URL of the software image, if a HTTPS server is used.
FTP Server:
ID of the FTP server that provides the file. This is necessary if a FTP server is used.
Action:
Indicates what is to be done with the file.
Possible values:
delete
deploy
Deployment Status:
Status of the deployment action.
Status info:
Information about the status.
Deployment Date:
Date of the latest file deployment.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-291
workpoint-configuration.fm
IP Devices
IP Phone Configuration
Deployment Time:
Time of the latest file deployment.
Deployment Initiator:
Interface over which the deployment has been initiated.
Possible values:
DLS
WBM
Local
7-292
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
CTI Configuration
Gateway/Server
Ports
Quality of Service
Telephony
Dialing Properties
Audio/Video Settings
Directories/Address Books
Miscellaneous
Keysets/Keylayout
Dialup Site
OpenScape
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-293
workpoint-configuration.fm
IP Devices
IP Client Configuration
General Data
This part of the contents area is used for entering parameters in Search view to find a specific group of IP clients.
The base data associated with the IP clients found is displayed in Object view (no changes possible except under
Remarks).
NOTE: For further information about the Search view, please see Section 5.5, "Search Functionality".
IP Address:
IP address of the IP client.
Example: 192.117.1.193
The value is read-only if it was dynamically assigned with DHCP.
Device ID:
ID for unique identification of the IP device.
Device Type:
Device type of the IP client.
All IP client types supported by DLS can be found in Section 3.4, "Area of Application".
Example: optiClient 130
E.164:
Complete E.164 phone number of the IP client.
Example: 498972212345 (or no input).
For more information, see Chapter 17, "E.164".
7-294
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
SW Version:
Software version of the IP phone.
Example: 5.0.12
Information on the difference between the software and license version can be found in Section 15.7, "Distribution
of Workpoint Software".
Reg-Address:
IP address of the gateway or the gatekeeper where the workpoint must register. In HiPath 3000, this is the IP
address of the HG 1500, in HiPath 4000 it is the HG 3530 or the STMI board.
Last Registration:
Time of the last IP client registration.
For information on selecting a time segment for a search, see Section 5.4.2.4, "Content Area".
Remarks:
Fields for general information.
Location
Current location of the IP Device. The value is set during registration and is displayed only herein. (For meaning
and configuration of the location, see Section 6.3.2, "Location".)
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-295
workpoint-configuration.fm
IP Devices
IP Client Configuration
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
Deploy
Starts a job for distributing the configuration changes. For more information, see Section 15.1, "First Steps:
Changing IP Device Parameters".
Get
Loads a template that has already been saved. For more information, see Section 15.5, "Editing Templates".
Save
Saves configuration entries as a template. For more information, see Section 15.5, "Editing Templates".
Rename
Changes the name of a saved template. For more information, see Section 15.5, "Editing Templates".
Delete
Deletes a saved template. For more information, see Section 15.5, "Editing Templates".
7-296
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
General Data
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-297
workpoint-configuration.fm
IP Devices
IP Client Configuration
General Data
"Device" Tab
"Connection" Tab
"Dialup" Tab
"License" Tab
7-298
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
"Device" Tab
Call: Main Menu > IP Devices > IP Client Configuration > CTI Configuration > CTI HFA Provider > "Device" Tab
Phone Type:
Type of the phone which is to be controlled by the CTI provider.
Possible Options:
optiSet E comfort
optiSet E advance
Modules Type:
Type of the connected module, if present.
Possible Options:
Modules Count:
Number of existing modules.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-299
workpoint-configuration.fm
IP Devices
IP Client Configuration
Headset available
Checkbox to determinate whether a headset is connected.
7-300
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
"Connection" Tab
Call: Main Menu > IP Devices > IP Client Configuration > CTI Configuration > CTI HFA Provider > "Connection"
Tab
PBX Type:
Possible Options:
HiPath 3000
Includes HiPath, OpenScape MX/LX, and OpenOffice EE, too.
HiPath 4000
Connection Port:
Hardware port used for CTI communication with the device. If USB is used, a special driver is necessary, which
emulates a COM port. For futher information, see the administrator dcoumentation for optiClient.
Possible Options:
LAN
COM1
COM2
COM3
COM4
COM5
COM6
COM7
COM8
COM9
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-301
workpoint-configuration.fm
IP Devices
IP Client Configuration
Device Address:
IP address of the PBX.
User ID:
User address (extension) for the phone.
Password:
Password corresponding to the user ID.
ACD Number:
Needed if the user is working as ACD (Automatic Call Distribution) agent.
Emergency Number:
Emergency number configured in the device.
7-302
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
"Dialup" Tab
Call: Main Menu > IP Devices > IP Client Configuration > CTI Configuration > CTI HFA Provider > "Dialup" Tab
Extension area:
This parameter defines a pattern which enables to discern internal extensions. From a workpoints point of view,
extensions are internal if they are assigned to the same PBX. The extension area can be given as a regular
expression.
Example: Let 1xxx, 2xxx, 3xxx, 4xxx , 5xxx be (internal) extensions, and let 6xxx, 7xxx, 8xxx, 9xxx be external call
numbers. The regular expression ^[12345] defines that call numbers beginning with a digit from 1 to 5 are internal
extensions. If, for instance, the system identification number is 667, the call numbers from 6671xxx to 6675xxx
are treated as internal extensions.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-303
workpoint-configuration.fm
IP Devices
IP Client Configuration
Trunk Code:
Access code used for dialing out from a PBX to a PSTN. If multiple trunk codes are configured at the
communication system connected, enter them in this field using "|" as a separator (0 and 88 in the example). The
first value entered is always used to supplement the call number when dialing. Maximum length: 5 digits.
Examples: 0, 74, 9 (USA).
Prefix International:
Prefix for an international call. This data is determined by the network operator, and thus independent of the
configuration for the PBX. Maximum length: 21 digits.
Example: 01081
7-304
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-305
workpoint-configuration.fm
IP Devices
IP Client Configuration
"License" Tab
Call: Main Menu > IP Devices > IP Client Configuration > CTI Configuration > CTI HFA Provider > "License" Tab
Server:
IP address of the server that provides the licenses.
Password:
Password for access to the license.
Retries:
Number of retries to establish a connection to the license server.
Timeout (ms):
Timeout for tries to establish a connection to the license server.
Port:
Number of the port used by the license server for delivering licenses.
7-306
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
General Data
"Connection" Tab
"Dialup" Tab
"License" Tab
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-307
workpoint-configuration.fm
IP Devices
IP Client Configuration
"Connection" Tab
Call: Main Menu > IP Devices > IP Client Configuration > CTI Configuration > CSTA Service Provider >
"Connection" Tab
Subscriber ID:
Subscriber ID resp. extension which is controlled by the CSTA service provider.
Subscriber Name:
Logical name for the extension which is controlled by the CSTA service provider.
DNS Name:
DNS name of the CSTA service provider.
IP Address:
IP address of the CSTA service provider.
Password:
Password required for starting the CSTA service provider.
Normalize E.164:
Activates the normalization of call numbers to E.164 format.
7-308
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
"Dialup" Tab
Call: Main Menu > IP Devices > IP Client Configuration > CTI Configuration > CSTA Service Provider > "Dialup"
Tab
See Section 7.2.7.1, ""HFA Dialing Properties" Tab".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-309
workpoint-configuration.fm
IP Devices
IP Client Configuration
"License" Tab
Call: Main Menu > IP Devices > IP Client Configuration > CTI Configuration > CSTA Service Provider > "License"
Tab
Server:
IP address of the server that provides the licenses.
Password:
Passwort zum Lizenzserver.
Retries:
Number of retries to establish a connection to the license server.
Timeout (ms):
Timeout for triesto establish a connection to the license server.
Port:
Number of the port used by the license server for delivering licenses.
7-310
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
7.2.2 Gateway/Server
Call: Main Menu > IP Devices > IP Client Configuration > Gateway/Server
This area features the following components:
General Data
"Gateway" Tab
"Licenses" Tab
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-311
workpoint-configuration.fm
IP Devices
IP Client Configuration
General Data
This part of the contents area is used for entering parameters in Search view to find a specific group of IP clients.
The base data associated with the IP clients found is displayed in Object view (no changes possible except under
Remarks).
NOTE: For further information about the Search view, please see Section 5.5, "Search Functionality".
IP Address:
IP address of the IP client.
Example: 192.117.1.193
The value is read-only if it was dynamically assigned with DHCP.
Device ID:
ID for unique identification of the IP device.
Device Type:
Device type of the IP client.
All IP client types supported by DLS can be found in Section 3.4, "Area of Application".
Example: optiClient 130
E.164:
Complete E.164 phone number of the IP client.
Example: 498972212345 (or no input).
For more information, see Chapter 17, "E.164".
SW Version:
Software version of the IP phone.
7-312
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Example: 5.0.12
Information on the difference between the software and license version can be found in Section 15.7, "Distribution
of Workpoint Software".
Reg-Address:
IP address of the gateway or the gatekeeper where the workpoint must register. In HiPath 3000, this is the IP
address of the HG 1500, in HiPath 4000 it is the HG 3530 or the STMI board.
Last Registration:
Time of the last IP client registration.
For information on selecting a time segment for a search, see Section 5.4.2.4, "Content Area".
Remarks:
Fields for general information.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-313
workpoint-configuration.fm
IP Devices
IP Client Configuration
System Type:
Type and version of the communication platform at which the workpoint is operated.
Possible options:
HiPath 3000
Includes HiPath, OpenScape Office MX/LX, and OpenOffice EE, too.
HiPath 4000
Reg-Address:
IP address or host name of the PBX used to operate the workpoint.
Only applies to the HFA configuration of the IP client.
Gatekeeper ID:
Only applies to the HFA configuration of the IP client.
Subscriber Password:
Password of the IP client on the PBX.
Only applies to the HFA configuration of the IP client.
7-314
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
None
No voice encryption.
Reduced
One-way voice encryption (gatekeeper data not sent in encrypted form).
Full
Voice encryption both ways (workpoint and gatekeeper data both sent in encrypted form).
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-315
workpoint-configuration.fm
IP Devices
IP Client Configuration
System Type:
Type and version of the communication platform at which the workpoint is operated.
Possible options:
HiPath 3000
Includes HiPath, OpenScape Office MX/LX, and OpenOffice EE, too.
HiPath 4000
No standby system
Reg-Address (Standby):
IP address or host name of the standby PBX used to operate the workpoint.
Only applies to the HFA configuration of the IP client.
Gatekeeper ID:
Only applies to the HFA configuration of the IP client.
7-316
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Subscriber Password:
Password of the IP client on the (standby) PBX.
Only applies to the HFA configuration of the IP client.
None
No voice encryption.
Reduced
One-way voice encryption (gatekeeper data not sent in encrypted form).
Full
Voice encryption both ways (workpoint and gatekeeper data both sent in encrypted form).
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-317
workpoint-configuration.fm
IP Devices
IP Client Configuration
Directory:
Complete path of the directory where the IP client should search for software updates.
SW Update mode
Possible values:
None
No check.
Start
Check at program start.
Interval
Ongoing checks in intervals.
Interval (min):
Interval in minutes for ongoing checks for software updates.
7-318
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Device Phonetype:
The telephone type defines:
How many display lines are displayed in optiClient 130s free telephone (always two lines in the main bar in
integrated telephones).
If self labeling keys are available for the optiClients 130 devices
are available in the first column of the extended key field in optiClient 130.
Possible options:
optiSet E advance
optiSet E comfort
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-319
workpoint-configuration.fm
IP Devices
IP Client Configuration
7-320
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Terminal Name
Own IP Address
You can enter the optiClient IP address here. If this field is left empty, the optiClient defines its IP address
automatically.
Server Type
Possible options:
Standard
OpenScape Voice
hiQ4200
Time to Live
This value is three times the time taken by the workpoint to register at the gatekeeper to sustain the registration
validity. If the value for Time to Live is set to 3 minutes, for example, the workpoint registers every minute.
Value range: 0 ... 4320 minutes.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-321
workpoint-configuration.fm
IP Devices
IP Client Configuration
Address Conversion
E.164 Normalizing
Checkbox for activating phone number normalizing.
Hot Line
Address:
The address specified here is dialed once the delay time defined for line seizure (for example, on lifting the
handset) has elapsed.
SIP Session
SIP Session Timer
Checkbox for activating the SIP session timer. The timer is used to monitor the duration of an SIP session.
7-322
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-323
workpoint-configuration.fm
IP Devices
IP Client Configuration
Registrar Address:
IP address or host name of the SIP registrar.
This setting only applies to the SIP configuration of the IP client.
UserID:
The user ID is the first part of the SIP URL.
Password:
Password required for accessing the SIP server.
Realm:
SIP range in which the workpoint is operated. SIP realm is used to identify the telephone at the SIP server.
Main Line
Tooltip Text:
Defines the display text for the main line.
7-324
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Primary Line:
Checkbox for marking the main line as a primary line.
Ring
Checkbox for activating the call.
Delayed Ring
Checkbox for activating a delayed call.
Outgoing
Incoming
Private
Connection Settings
Connection
Possible options:
Registrar Port
Port number of the registrar server.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-325
workpoint-configuration.fm
IP Devices
IP Client Configuration
Proxy Address
IP address or host name of the SIP proxy.
This setting only applies to the SIP configuration of the IP client.
Connection Settings
Connection
Possible options:
Proxy Port
Port number of the proxy server.
7-326
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Gateway Address:
IP address or host name of the gateway.
This setting only applies to the SIP configuration of the IP client.
Connection Settings
Connection:
Possible options:
Gateway Port:
Port number of the gateway.
Outbound Domain
Outbound Domain
Checkbox for activating the outbound domain.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-327
workpoint-configuration.fm
IP Devices
IP Client Configuration
Outbound Domain:
Name of the outbound domain.
7-328
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Server Type:
Possible options:
Individual
OpenScape Voice/hiQ4200
Server Services
Video Connections
Checkbox for activating video connections.
Chat Connections
Checkbox for activating instant messaging connections.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-329
workpoint-configuration.fm
IP Devices
IP Client Configuration
Multilines / Stations
Checkbox for activating additional lines/stations.
7-330
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Time to Live:
This value is three times the time taken by the workpoint to register at the gatekeeper to sustain the registration
validity. If the value for Time to Live is set to 3 minutes, for example, the workpoint registers every minute.
Value range: 0 ... 4320 minutes.
Connection Settings
Connection:
Possible options:
Outbound Domain
Use Outbound Domain
Checkbox for activating use of the outbound domain.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-331
workpoint-configuration.fm
IP Devices
IP Client Configuration
Port:
Port number for access to the license server.
Default: 61740
Password:
Password for access to the license server.
Retries:
Maximum number of connection attempts.
Timeout (ms):
The maximum time (in milliseconds) for the attempt to set up a connection to the license server.
SIP License
7-332
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Server:
IP address or host name of the license server.
Port:
Port number for access to the license server.
Default: 61740
Password:
Password for access to the license server.
Retries:
Maximum number of connection attempts.
Timeout (ms):
The maximum time (in milliseconds) for the attempt to set up a connection to the license server.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-333
workpoint-configuration.fm
IP Devices
IP Client Configuration
VPN Mode:
Possible options:
None
VPN (Virtual Private Network) is not used.
Automatic
VPN is used with an automatically determined IP address.
Manual
VPN is used with the IP address specified in the case of VPN IP.
VPN IP:
IP address for the VPN (Virtual Private Network).
7-334
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
7.2.3 Ports
Call: Main Menu > IP Devices > IP Client Configuration > Ports
This area features the following components:
General Data
"Ports" Tab
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-335
workpoint-configuration.fm
IP Devices
IP Client Configuration
7-336
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-337
workpoint-configuration.fm
IP Devices
IP Client Configuration
7-338
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
General Data
"Settings" Tabs
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-339
workpoint-configuration.fm
IP Devices
IP Client Configuration
Layer 3 Select
Checkbox for activating layer 3 (network layer).
Layer 3 Signaling:
Priority for layer 3 signaling.
Can only be defined if Layer 3 Select is active.
Possible options:
Default
AF11
AF12
AF13
AF21
AF22
AF23
AF31
AF32
AF33
AF41
AF42
AF43
EF
CST
7-340
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Layer 3 Voice:
Priority for layer 3 voice.
Can only be defined if Layer 3 Select is active.
Same options as for Layer 3 Signaling.
Layer 2 Select
Checkbox for activating layer 2 (data link layer).
Layer 2 Signaling:
Priority for layer 2 signaling.
Can only be defined if Layer 2 Select is active.
Value range: 0 ... 7.
Layer 2 Voice:
Priority for layer 2 voice.
Can only be defined if Layer 2 Select is active.
Same options as for Layer 2 Signaling.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-341
workpoint-configuration.fm
IP Devices
IP Client Configuration
Layer 2 Signaling:
Priority for layer 2 signaling.
Can only be defined if Layer 2 Select is active.
Value range: 0 ... 7
Layer 2 Voice:
Priority for layer 2 voice.
Can only be defined if Layer 2 Select is active.
Same options as for Layer 2 Signaling.
Layer 3 Signaling
Can only be defined if Layer 3 Select (SIP) is active.
Possible options:
Default
AF11
AF12
AF13
7-342
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
AF21
AF22
AF23
AF31
AF32
AF33
AF41
AF42
AF43
EF
CST
Layer 3 Voice:
Priority for layer 3 voice.
Can only be defined if Layer 3 Select (SIP) is active.
Possible options:
Default
AF11
AF12
AF13
AF21
AF22
AF23
AF31
AF32
AF33
AF41
AF42
AF43
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-343
workpoint-configuration.fm
IP Devices
IP Client Configuration
EF
CST
7-344
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
7.2.5 Telephony
Call: Main Menu > IP Devices > IP Client Configuration > Telephony
This area features the following components:
General Data
"Telephony" Tab
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-345
workpoint-configuration.fm
IP Devices
IP Client Configuration
Emergency Number:
Contains the phone number that can be dialed in an emergency.
ACD Number:
ACD agent number if you are working as an ACD agent.
7-346
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Emergency Number:
Contains the phone number that can be dialed in an emergency.
ACD Number:
ACD agent number if you are working as an ACD agent.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-347
workpoint-configuration.fm
IP Devices
IP Client Configuration
General Data
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
7-348
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Reconnect Timeout:
Timeout for switchover to the main system.
Value range: 1 ... 255 seconds.
Retry Threshold:
Specifies the number of attempts permitted when switching back to the standby system.
Value range: 1 ... 255
Automated Switchback
Checkbox for activating the option for automatic switchback to the main system.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-349
workpoint-configuration.fm
IP Devices
IP Client Configuration
General Data
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
7-350
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Extension Area:
This parameter defines a pattern for detecting internal extension numbers. From the workpoints perspective,
extension numbers are internal if they are assigned to the same system. The extension area can be specified as
a regular expression.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-351
workpoint-configuration.fm
IP Devices
IP Client Configuration
Example: 1xxx, 2xxx, 3xxx, 4xxx, 5xxx are extensions and 6xxx, 7xxx, 8xxx, 9xxx are external phone numbers.
The regular expression ^[12345] indicates that phone numbers starting with the digits 1 to 5 are internal extension
numbers. If for example the system identification number is 667, all numbers from 6671xxxx to 6675xxx will be
used as internal extensions.
Trunk code:
Number for trunk seizure for an outbound external call.
Format: Up to five digits.
Examples: 0, 74, 9 (USA).
Prefix International:
Number for an outbound international call.
Format: Up to 21 digits.
Example: 01081
7-352
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-353
workpoint-configuration.fm
IP Devices
IP Client Configuration
7-354
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Extension Area:
This parameter defines a pattern for detecting internal extension numbers. From the workpoints perspective,
extension numbers are internal if they are assigned to the same system. The extension area can be specified as
a regular expression.
Example: 1xxx, 2xxx, 3xxx, 4xxx, 5xxx are extensions and 6xxx, 7xxx, 8xxx, 9xxx are external phone numbers.
The regular expression ^[12345] indicates that phone numbers starting with the digits 1 to 5 are internal extension
numbers. If for example the system identification number is 667, all numbers from 6671xxxx to 6675xxx will be
used as internal extensions.
Trunk code:
Number for trunk seizure for an outbound external call.
Format: Up to five digits.
Examples: 0, 74, 9 (USA).
Prefix International:
Number for an outbound international call.
Format: Up to 21 digits.
Example: 01081
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-355
workpoint-configuration.fm
IP Devices
IP Client Configuration
7-356
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Extension Area:
This parameter defines a pattern for detecting internal extension numbers. From the workpoints perspective,
extension numbers are internal if they are assigned to the same system. The extension area can be specified as
a regular expression.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-357
workpoint-configuration.fm
IP Devices
IP Client Configuration
Example: 1xxx, 2xxx, 3xxx, 4xxx, 5xxx are extensions and 6xxx, 7xxx, 8xxx, 9xxx are external phone numbers.
The regular expression ^[12345] indicates that phone numbers starting with the digits 1 to 5 are internal extension
numbers. If for example the system identification number is 667, all numbers from 6671xxxx to 6675xxx will be
used as internal extensions.
Trunk code:
Number for trunk seizure for an outbound external call.
Format: Up to five digits.
Examples: 0, 74, 9 (USA).
Prefix International:
Number for an outbound international call.
Format: Up to 21 digits.
Example: 01081
7-358
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-359
workpoint-configuration.fm
IP Devices
IP Client Configuration
General Data
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
7-360
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Codec Sequence:
Possible options:
G.711 Packetlength:
Possible options:
10
20
30
40
50
60
G.723 Packetlength:
Possible options:
30
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-361
workpoint-configuration.fm
IP Devices
IP Client Configuration
60
G.729 Packetlength:
Possible options:
10
20
30
40
50
60
Jitter-Buffer (ms):
Caching duration:
Possible options (in ms):
Value range: 20 ... 190 milliseconds.
Bandwidth Homeworker
Checkbox for activating the bandwidth for homeworker data transmission.
Bandwidth no polling
Checkbox for activating the bandwidth with no polling.
DMC activated
Checkbox for activating DMC bandwidth.
7-362
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
1st Codec:
First compression job.
Possible options:
G.711
G.722
G.729
2nd Codec:
Second compression job.
Possible options:
G.711
G.722
G.729
None
3rd Codec:
Third compression job.
Possible options:
G.711
G.722
G.729
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-363
workpoint-configuration.fm
IP Devices
IP Client Configuration
None
Codec Packetlength:
Possible options:
Automatic
10
20
56
64
128
256
512
1024
2048
3072
6144
10000
12288
24576
100000
1000000
56
64
7-364
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
128
256
512
1024
2048
3072
6144
10000
12288
24576
100000
1000000
H.263
H.264
H.263
H.264
None
Jitter-Buffer (ms)
Possible options:
20
30
40
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-365
workpoint-configuration.fm
IP Devices
IP Client Configuration
50
60
70
80
90
100
110
120
130
140
150
160
170
180
190
7-366
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
These tabs let you define hardware settings for the voice output or ringer devices, for example.
Local Administration of Audio Settings
If this checkbox is activated, the audio settings can be changed only on the optiClient, but not by the DLS. In this
case, the fields under Audio Schemes are only for display.
If this checkbox is inactive, the audio settings can be changed only by the DLS.
Index
Number of the setting.
Audioscheme
Name of the audioscheme.
Ringer Device
Audio hardware for the ringer device.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-367
workpoint-configuration.fm
IP Devices
IP Client Configuration
Voice In Device
Audio hardware for the voice in device.
Second Device
Audio hardware representing a second device. If a second device is selected here and this audioscheme is active,
an additional icon appears in the main menu for controlling the second device.
Audio Controller
Additional function for controlling hardware functions.
7-368
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Available Devices:
Index
Serial number of the audio device.
Device
Name of the audio device for alerting and voice.
Driver Version
Driver version for the audio device.
Channel Count
Number of available audio channels.
Wave-In Device ID
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-369
workpoint-configuration.fm
IP Devices
IP Client Configuration
Wave-Out Device ID
Controller
7-370
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Index
Number of the setting.
Video Scheme
Name of the video scheme.
Video Device
Camera for transmitting the picture in video connections.
Video Connection
optiClient 130 allows parties to connect their video pictures providing both parties have an operational video
system.
Possible options:
Locked
Optional
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-371
workpoint-configuration.fm
IP Devices
IP Client Configuration
Optimization Preference
Best Resolution
Optimization to the highest possible resolution.
Best Motion
Optimization to the best possible reproduction of movement.
7-372
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Index
Number of the setting.
Device
All cameras installed on the workstation are listed. Select the camera you wish to use. If no cameras are listed
here, your PC is not equipped with a video camera.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-373
workpoint-configuration.fm
IP Devices
IP Client Configuration
General Data
"LDAP" Tab
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
7-374
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
ID
Name of the LDAP server.
Port
Port number of the LDAP server.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-375
workpoint-configuration.fm
IP Devices
IP Client Configuration
Account
LDAP server account.
Password
Password for accessing the LDAP server.
Server Description
Descriptive text for the LDAP server.
Searchbase
During LDAP server configuration, this function allows you to specify a base level
which is used as a starting point for searching or displaying optiClient 130 entries in this LDAP directory.
You can use two different formats to define a base level:
<level 3>=<name>, <level 2>=<name>, <level 1>=<name> or
<level 1>=<name>/<level 2>=<name>/<level 3>=<name>
Example of an LDAP directory with the following elements:
Level 3: ou (for example for "organization unit"), name, for example, COM
7-376
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Display Name
Activates display name display and the entry of a label for the display name.
Surname
Activates name display and the entry of a label for the name.
Given Name
Activates second name display and the entry of a label for the second name.
First Name
Activates first name display and the entry of a label for the first name.
Title
Activates title display and the entry of a label for the title.
City
Activates city display and the entry of a label for the city.
Postal Code
Activates postal code display and the entry of a label for the postal code.
Postal Address
Activates postal address display and the entry of a label for the postal address.
Country
Activates country display and the entry of a label for the country.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-377
workpoint-configuration.fm
IP Devices
IP Client Configuration
State
Activates state display and the entry of a label for the state.
Company
Activates company display and the entry of a label for the company.
Department
Activates department display and the entry of a label for the department.
Comment
Activates comment display and the entry of a label for the comment.
Mail
Activates mailbox display and the entry of a label for the mailbox.
Mail 2
Activates second mailbox display and the entry of a label for the second mailbox.
Mail 3
Activates third mailbox display and the entry of a label for the third mailbox.
Assistant
Activates assistant display and the entry of a label for the assistant.
Business
Activates business display and the entry of a label for the business area.
7-378
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Business 2
Activates second business display and the entry of a label for the second business area.
Callback
Activates callback number display and the entry of a label for the callback number.
Car Phone
Activates car phone number display and the entry of a label for the car phone number.
Company Phone
Activates company phone number display and the entry of a label for the company phone number.
Private Phone
Activates private phone number display and the entry of a label for the private phone number.
Private Phone 2
Activates second private phone number display and the entry of a label for the second private phone number.
Mobile
Activates mobile phone number display and the entry of a label for the mobile phone number.
Other Phone
Activates another phone number display and the entry of a label for the other phone number.
Pager
Activates pager number display and the entry of a label for the pager number.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-379
workpoint-configuration.fm
IP Devices
IP Client Configuration
Primary
Radio
Fax
Activates fax number display and the entry of a label for the fax number.
Private Fax
Activates private fax number display and the entry of a label for the private fax number.
ISDN
Activates ISDN number display and the entry of a label for the ISDN number.
Other Fax
Activates another fax number display and the entry of a label for the other fax number.
Telex
Activates telex number display and the entry of a label for the telex number.
Room
Activates room number display and the entry of a label for the room number.
Cost Location
Activates cost location display and the entry of a label for the cost location.
7-380
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
URL
Activates URL display and the entry of a label for the URL.
Location
Activates location display and the entry of a label for the location.
Data Source
Activates data source display and the entry of a label for the data source.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-381
workpoint-configuration.fm
IP Devices
IP Client Configuration
You can configure different settings for accessing central and local directories. This access enables you to work
with directories and address books in optiClient 130.
Outlook Contacts
This directory contains all entries from the Contacts folder in a local Microsoft Outlook installation. If Outlook is not
installed or this directory is not configured for your users, then this directory is not available.
This checkbox creates a directory containing Outlook contact information in the optiClient 130.
Exchange Server
This directory contains all entries from the Microsoft Exchange Server Global Address Book (if installed).
This checkbox creates a directory containing Microsoft Exchange Server Information in the optiClient 130.
7-382
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
This checkbox creates a directory containing Lotus Notes contact information in the optiClient 130.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-383
workpoint-configuration.fm
IP Devices
IP Client Configuration
7-384
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
7.2.10 Miscellaneous
Call: Main Menu > IP Devices > IP Client Configuration > Miscellaneous
This area features the following components:
General Data
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-385
workpoint-configuration.fm
IP Devices
IP Client Configuration
7-386
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Voice Recording
Disable Voice Recording
Activates or deactivates voice recording.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-387
workpoint-configuration.fm
IP Devices
IP Client Configuration
Callback
Activating Code in case of no answer:
Code for controlling the "Callback-no reply" function on the server.
Call Pickup
Group Pickup Server type:
Possible options:
Other
OpenScape Voice
Broadsoft
Sylantro
HiQ8000
Genesys
7-388
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Huntgroup
Function Code for temporary logout from a hunt group
Huntgroup Code for "temporary logout".
OSV PAC default service name : Make Busy Toggle **13
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-389
workpoint-configuration.fm
IP Devices
IP Client Configuration
Call Forwarding
Time period for Call Forward
Enter the time after which unanswered calls are forwarded when call forwarding is active.
Automatic
Inband
Attendant Function
Join after hang up:
Activate this checkbox when you have two active connections (for example, during consultation hold) and then
hang up. If the checkbox is active, the two connected parties are connected to each another; if the checkbox is
not active, both connections are ended.
Sounds
Country spec. Tones:
Possible options:
7-390
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Brazil
China
Germany
France
Great Britain
International
Italy
Netherlands
Portugal
Spain
USA
Music on Hold:
Activate this checkbox if you want music on hold to be played in certain situations (for example, call forwarding,
call hold, consultation).
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-391
workpoint-configuration.fm
IP Devices
IP Client Configuration
7.2.11 Keysets/Keylayout
Call: Main Menu > IP Devices > IP Client Configuration > Keysets/Keylayout
This area features the following components:
General Data
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
7-392
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Index
Name of the key layout function.
Device
Device selection for the programmed key.
Possible options:
1st Sidecar
2nd Sidecar
3rd Sidecar
4th Sidecar
Base Device
Level
Level number of the programmed key.
Key number
Key number of the programmed key.
Label
Label displayed for the programmed key.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-393
workpoint-configuration.fm
IP Devices
IP Client Configuration
Index
Name of the key layout function.
Device
Device selection of the programmed key.
Possible options:
1st Sidecar
2nd Sidecar
3rd Sidecar
4th Sidecar
Base Device
Level
Level number of the programmed key.
Key number
Key number of the programmed key.
Label
Label displayed for the programmed key.
7-394
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Rollover Type:
Type of alerting to be used in the case that, during an active call, an incoming call arrives on a different line.
Possible options:
No tone
Normal beep
Special beep
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-395
workpoint-configuration.fm
IP Devices
IP Client Configuration
Hot Line
Address
Address resp. call number which is dialed after the line has been activated (e. g. by going off-hook) and the delay
time has expired.
7-396
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Index:
Line key number
Address of record:
Phone number for the line belonging to this line key.
Realm:
SIP realm for the lines address of record
UserID:
SIP user name of the lines address of record
Password:
Password for the SIP user name.
Description:
Description of the line.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-397
workpoint-configuration.fm
IP Devices
IP Client Configuration
Tooltip Text:
Text that appears in the ToolTip for the line.
7-398
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Index
Index number of the key function.
DSS Address
Phone number of the DSS (Direct Station Select) line.
Realm
SIP realm of the DSS line.
UserID
SIP user name of the DSS lines address of record.
Password
Password for the SIP user name.
Description
Description of the DSS line.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-399
workpoint-configuration.fm
IP Devices
IP Client Configuration
Tooltip Text
Text entry that appears in the ToolTip for the DSS line key.
7-400
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Index
Index number of the call forwarding key.
Type
Selection of conditions, under which call forwarding is executed.
All calls
Destination
Destination of SIP call forwarding.
Optional Text
Description of the type of SIP call forwarding configured here.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-401
workpoint-configuration.fm
IP Devices
IP Client Configuration
Index
Index number of the key function.
Type
Type of SIP keypad.
ID
SIP keypad ID.
Value
Value of the key.
User Text
Descriptive label for the SIP keypad.
7-402
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
General Data
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-403
workpoint-configuration.fm
IP Devices
IP Client Configuration
The parameters described below are available once for the currently active certificate and once for the imported
certificate.
Index
Index number for the certificate.
Status Active/Import:
Specifies whether a certificate is registered as imported and/or active on the phone. The five statuses listed below
are possible.
Possible values:
no certificate
different
equal
no active certificate
no imported certificate
PKI Configuration
Name of PKI configuration.
7-404
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Serial Number:
Serial number of the active or imported certificate (display only).
Owner:
Owner of the active or imported certificate (display only).
Issuer:
Issuer of the active or imported certificate (display only).
Valid from:
Start of validity for the active or imported certificate (display only).
Valid to:
End of validity for the active or imported certificate (display only).
Key Algorithm
Key Algorithm.
Key Size
Key Size.
Fingerprint (SHA-1):
Test algorithm SHA-1 (160 bits/20 characters) for the security certificate.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-405
workpoint-configuration.fm
IP Devices
IP Client Configuration
NOTE: The value of the imported certificate is updated periodically dependent on the settings in
Administration > Alarm Configuration > "Settings" Tab > Alarm Configuration for Expiring
Certificates > Interval. Therefore it might be greater than the value of the active certificate until the
next update.
Alarm Status:
Displays the duration of validity for certificates when searching for certificates due to expire.
Possible values:
valid
expired
Activate certificate
The imported certificate will be activated with the next saving. By activating an empty certificate, the certificate at
the end device will be deleted. The active certificate is used to encrypt calls.
IMPORTANT: In the case of OpenScape Desktop Clients, there is no impact when changing the TLS
certificates .
7-406
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
UDP
TCP
TLS
UDP
TCP
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-407
workpoint-configuration.fm
IP Devices
IP Client Configuration
Interval
Time interval in seconds in which the TLS connectivity is checked periodically.
Possible options: 60 - 600
7-408
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
UDP
TCP
TLS
UDP
TCP
TLS
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-409
workpoint-configuration.fm
IP Devices
IP Client Configuration
General Data
7-410
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Dialup Site
The name of the User Profile of IP Client. It is initially created through the Login Dialog of the IP Client.
Quality of Service
Layer 3 Select
Checkbox for activating the QoS configuration on layer 3.
Layer 3 Signaling:
Class of service value for call signaling on layer 3.
Possible options:
AF11
AF12
AF13
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-411
workpoint-configuration.fm
IP Devices
IP Client Configuration
AF21
AF22
AF23
AF31
AF32
AF33
AF41
AF42
AF43
EF
CS7
Default
Layer 3 Voice:
Class of service value for voice on layer 3.
Possible options:
AF11
AF12
AF13
AF21
AF22
AF23
AF31
AF32
AF33
AF41
AF42
AF43
EF
7-412
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
CS7
Default
Layer 2 Select
Checkbox for activating the QoS layer 2 configuration.
Layer 2 Signaling:
Class of Service value for call signaling on layer 2.
Value range: 0 ... 7
Layer 2 Voice:
Class of Service value for voice on layer 2.
Value range: 0 ... 7
Codec Settings
Codec Settings (SIP)
1st Codec:
First compression method.
Possible options:
G.711
G.722
G.729
2nd Codec:
Second compression method.
Possible options:
G.711
G.722
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-413
workpoint-configuration.fm
IP Devices
IP Client Configuration
G.729
None
3rd Codec:
Third compression method.
Possible options:
G.711
G.722
G.729
None
Codec Packetlength:
Possible options:
Automatic
10
20
Jitter-Buffer (ms):
Caching duration:
Possible options (in ms):
Value range: 20 ... 190 milliseconds.
7-414
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
G.711 Packetlength:
Possible options:
10
20
30
40
50
60
G.723 Packetlength:
Possible options:
30
60
G.729 Packetlength:
Possible options:
10
20
30
40
50
60
Jitter-Buffer (ms):
Cache size.
Possible options (in ms):
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-415
workpoint-configuration.fm
IP Devices
IP Client Configuration
DMC activated
Checkbox for activating DMC bandwidth.
7-416
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
7.2.14 OpenScape
Call: Main Menu > IP Devices > IP Client Configuration > OpenScape
This menu item consists of the following areas:
General Data
"Connection" Tab
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-417
workpoint-configuration.fm
IP Devices
IP Client Configuration
User ID:
User ID for accessing the OpenScape Connection Server.
Password:
Password for accessing the OpenScape Connection Server.
Server:
Address of the OpenScape Connection Server.
Port:
Port number of the OpenScape Connection Server.
7-418
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
User ID:
User ID for access to the OpenScape Instant Messaging (XMP) server.
Password:
Password for access to the OpenScape Instant Messaging (XMP) server.
Server:
Address of the server for OpenScape Instant Messaging (XMP).
Port:
Port number of the server for OpenScape Instant Messaging (XMP).
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-419
workpoint-configuration.fm
IP Devices
IP Client Configuration
Rules Configuration:
Rules Configuration for access to WEB server.
Rules Port:
Port number for access to the WEB server.
WebClient Server:
Address of the server for access to WebClient.
WebClient Port:
Port number of the server for access to WebClient.
7-420
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Client Configuration
Checkbox is disabled by default, thus implying use of the new WebClient interface.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-421
workpoint-configuration.fm
IP Devices
IP Gateway Configuration
Security Settings
IPSec/VPN
7-422
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Gateway Configuration
General Data
For information on general interface operation, see Section 5.4.2, "Work Area".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-423
workpoint-configuration.fm
IP Devices
IP Gateway Configuration
General Data
Call: Main Menu > IP Devices > IP Gateway Configuration > QoS Data Collection > General Data
This part of the contents area is identical for all interfaces associated with this menu. It is used for entering
parameters in Search view to find a specific group of IP gateways. The base data associated with the IP gateways
found is displayed in Object view.
The value displayed in the Remarks fields can be changed (all other fields are read-only).
IP Address:
IP address of the IP gateway.
Example: 192.117.1.193
The value is read-only if it was dynamically assigned with DHCP.
Device ID
ID that uniquely identifies this IP gateway.
Device Type:
IP gateway device type.
You can view all IP devices supported by the DLS in Section 3.4, "Area of Application".
Example: HG3500
PEN:
Position of the gateway assembly group (plug-in position).
SW Version:
Software version of the IP gateway.
Example: 5.0.12
7-424
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Gateway Configuration
Information on the difference between the software and license version can be found in Section 15.7, "Distribution
of Workpoint Software".
Last Registration:
Last time the IP gateway logged on to the DLS.
Remarks:
Fields for general information.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-425
workpoint-configuration.fm
IP Devices
IP Gateway Configuration
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
Get
Loads a template that has already been saved. For more information, see Section 15.5, "Editing Templates".
Save
Saves configuration entries as a template. For more information, see Section 15.5, "Editing Templates".
Discard
Discards any changes made and new entries.
Read
The parameters displayed on the new mask are read in again by the IP device.
Rename
Changes the name of a saved template. For more information, see Section 15.5, "Editing Templates".
Delete
Deletes a saved template. For more information, see Section 15.5, "Editing Templates".
7-426
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Gateway Configuration
Import Certificate
Imports a certificate for the selected IP device (only available in Certificate Management). For more information,
see Section 16.13, "Security: Administering Certificates".
Remove Certificate
Deletes a certificate for the selected IP device (only available in Certificate Management). For more information,
see Section 16.13, "Security: Administering Certificates".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-427
workpoint-configuration.fm
IP Devices
IP Gateway Configuration
SNMP Community:
Community string used for authorization on the SNMP server.
7-428
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Gateway Configuration
Report Mode:
Specifies when a report should be generated.
Possible options:
Report Interval:
Time interval in which a QoS report is sent.
Value range: 0 ... 3600 seconds.
Observation Interval:
Time interval in which threshold violation is checked.
Value range: 0 ... 5000 seconds.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-429
workpoint-configuration.fm
IP Devices
IP Gateway Configuration
Non-Compressing Codecs
Maximum Lost Packets Threshold:
Maximum number of total packets lost during uncompressed transmission. The number is specified in 1000packet increments.
Value range: 0 ... 255
7-430
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Gateway Configuration
Compressing Codecs
Maximum Lost Packets Threshold:
Maximum number of total packets lost during compressed transmission.
Value range: 0 ... 255
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-431
workpoint-configuration.fm
IP Devices
IP Gateway Configuration
General Data
"Settings" Tab
7-432
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Gateway Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-433
workpoint-configuration.fm
IP Devices
IP Gateway Configuration
Index
Indec number for the certificate.
Status Active/Import:
Content is automatically specified after import depending on whether active and/or imported certificates exist and
whether these are different or identical.
Possible options:
no certificate
different
equal
no active certificate
no imported certificate
Activate certificate
The imported certificate is automatically activated.
7-434
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Gateway Configuration
PKI Configuration
Shows PKI configuration of imported certificate.
Serial Number:
Serial number of the active or imported certificate (display only).
Owner:
Owner of the active or imported certificate (display only).
Issuer:
Issuer of the active or imported certificate (display only).
Valid from:
Start of validity for the active or imported certificate (display only).
Valid to:
End of validity for the active or imported certificate (display only).
Key Algorithm
Key Algorithm.
Key Size
Key Size.
Fingerprint (SHA-1):
Test algorithm SHA-1 (160 bits/20 characters) for the security certificate
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-435
workpoint-configuration.fm
IP Devices
IP Gateway Configuration
Alarm Status:
Current alarm status.
Possible values:
valid
expired
NOTE: For further information on importing and activating certificates, see Section 16.13, "Security:
Administering Certificates".
7-436
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Gateway Configuration
General Data
"Settings" Tab
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-437
workpoint-configuration.fm
IP Devices
IP Gateway Configuration
CRL Check
If this checkbox is activated, the Certificate Revocation List (CRL) in which invalid certificates can be entered is
verified.
Owner Check
If this checkbox is activated, the owners name is verified (Subjectname check).
7-438
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Gateway Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-439
workpoint-configuration.fm
IP Devices
IP Gateway Configuration
Status Active/Import:
Content is automatically specified after import depending on whether active and/or imported certificates exist and
whether these are different or identical.
Possible options:
no certificate
different
equal
no active certificate
no imported certificate
Activate certificate
The imported certificate is automatically activated.
PKI Configuration
Shows PKI configuration of imported certificate.
Serial Number:
Serial number of the active or imported certificate (display only).
7-440
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Gateway Configuration
Owner:
Owner of the active or imported certificate (display only).
Issuer:
Issuer of the active or imported certificate (display only).
Valid from:
Start of validity for the active or imported certificate (display only).
Valid to:
End of validity for the active or imported certificate (display only).
Key Algorithm
Key algorithm.
Key Size
Key size.
Fingerprint (SHA-1):
Test algorithm SHA-1 (160 bits/20 characters) for the security certificate
7-441
workpoint-configuration.fm
IP Devices
IP Gateway Configuration
Alarm Status:
Current alarm status.
Possible values:
valid
expired
NOTE: For further information on importing and activating certificates, see Section 16.13, "Security:
Administering Certificates".
7-442
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Gateway Configuration
Index
Index for identifying the SPE CA certificates.
Status Active/Import:
Content is automatically specified after import depending on whether active and/or imported certificates exist and
whether these are different or identical.
Possible options:
no certificate
different
equal
no active certificate
no imported certificate
Activate certificate
The imported certificate is automatically activated.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-443
workpoint-configuration.fm
IP Devices
IP Gateway Configuration
PKI Configuration
Shows PKI configuration of imported certificate.
Serial Number:
Serial number of the active or imported certificate (display only).
Owner:
Owner of the active or imported certificate (display only).
Issuer:
Issuer of the active or imported certificate (display only).
Valid from:
Start of validity for the active or imported certificate (display only).
Valid to:
End of validity for the active or imported certificate (display only).
Key Algorithm
Key algorithm.
Key Size
Key size.
Fingerprint (SHA-1):
Test algorithm SHA-1 (160 bits/20 characters) for the security certificate
7-444
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Gateway Configuration
Alarm Status:
Current alarm status.
Possible values:
valid
expired
NOTE: For further information on importing and activating certificates, see Section 16.13, "Security:
Administering Certificates".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-445
workpoint-configuration.fm
IP Devices
IP Gateway Configuration
Index
Index for identifying the CRL distribution points.
URL
URL of the CRL distribution point, for example, http://.... or ldap://...
7-446
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Gateway Configuration
7.3.4 IPSec/VPN
This area features the following components:
General Data
"Settings" Tab
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-447
workpoint-configuration.fm
IP Devices
IP Gateway Configuration
7-448
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Gateway Configuration
Index
Index number for the certificate.
Status Active/Import:
Content is automatically specified after import depending on whether active and/or imported certificates exist and
whether these are different or identical.
Possible options:
no certificate
different
equal
no active certificate
no imported certificate
Activate certificate
The imported certificate is automatically activated.
Serial Number:
Serial number of the active or imported certificate (display only).
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-449
workpoint-configuration.fm
IP Devices
IP Gateway Configuration
Owner:
Owner of the active or imported certificate (display only).
Issuer:
Issuer of the active or imported certificate (display only).
Valid from:
Start of validity for the active or imported certificate (display only).
Valid to:
End of validity for the active or imported certificate (display only).
Key Algorithm
Key algorithm.
Key Size
Key size.
Fingerprint (SHA-1):
Test algorithm SHA-1 (160 bits/20 characters) for the security certificate
7-450
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Gateway Configuration
Alarm Status:
Current alarm status.
Possible values:
valid
expired
NOTE: For further information on importing and activating certificates, see Section 16.13, "Security:
Administering Certificates".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-451
workpoint-configuration.fm
IP Devices
IP Gateway Configuration
Index
Status Active/Import:
Content is automatically specified after import depending on whether active and/or imported certificates exist and
whether these are different or identical.
Possible options:
no certificate
different
equal
no active certificate
no imported certificate
Activate certificate
The imported certificate is automatically activated.
Serial Number:
Serial number of the active or imported certificate (display only).
7-452
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Gateway Configuration
Owner:
Owner of the active or imported certificate (display only).
Issuer:
Issuer of the active or imported certificate (display only).
Valid from:
Start of validity for the active or imported certificate (display only).
Valid to:
End of validity for the active or imported certificate (display only).
Key Algorithm
Key algorithm.
Key Size
Key size.
Fingerprint (SHA-1):
Test algorithm SHA-1 (160 bits/20 characters) for the security certificate
7-453
workpoint-configuration.fm
IP Devices
IP Gateway Configuration
Alarm Status:
Current alarm status.
Possible values:
valid
expired
NOTE: For further information on importing and activating certificates, see Section 16.13, "Security:
Administering Certificates".
7-454
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Gateway Configuration
Index
Index for identifying the CRL files.
CRL Files
Directory path for CRL files.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-455
workpoint-configuration.fm
IP Devices
IP Device Interaction
Reset IP Devices
Ping IP Devices
Scan IP Devices
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
7-456
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Interaction
General Data
"Info" Tab
You can use this function to read out information from the IP Device. Only registered IP Devices will be
considered.
In this case, the data is synchronized between the IP Device and DLS database. The data is read without
IP Devices being reset (see Section 7.4.2, "Reset IP Devices"). In other words, no further actions or interventions
are performed at the workpoint.
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-457
workpoint-configuration.fm
IP Devices
IP Device Interaction
General Data
This part of the contents area is identical for the Read IP Device Data and Reset IP Devices interfaces associated
with this menu. It is used for entering parameters in Search view to find a specific group of IP Devices. The base
data associated with the IP Devices found is displayed in the Object view (no changes possible).
NOTE: For further information about the Search view, please see Section 5.5, "Search Functionality".
IP Address:
IP address of the IP Device. For OpenStage, in IPv4 or IPv6 address is displayed here. See also the description
of the IP Protocol Mode parameter.
Example: 192.117.1.193
The value is read-only if it was dynamically assigned with DHCP.
Device ID:
ID for unique identification of the IP device. In IP phones, this is generally the MAC address.
Example: 00:0E:A6:85:71:80
Device Type:
Workpoint device type.
All workpoint device types supported by DLS can be found in Section 3.4, "Area of Application".
Examples: optiPoint 410 standard, optiClient 130
E.164:
Complete E.164 subscriber number (Basic Profile or Mobile Profile).
Example: 498972212345
For information on the meaning of the E.164 station number in relation to mobility, see Section 3.8.3, "Mobility ID".
7-458
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Interaction
Basic E.164:
Complete E.164 phone number (Mobility Phone).
Example: 498972212345
For information on the meaning of the E.164 station number in relation to mobility, see Section 3.8.3, "Mobility ID".
IP Address 2:
Second IP address of the IP phone, if it has an IPv6 address.
Available for OpenStage only.
SW Version:
Software version used by the IP Device.
Example for IP phones and IP clients: 5.0.12
Information on the difference between the software and license version can be found in Section 15.7, "Distribution
of Workpoint Software".
SW Type:
Software type used by the IP Device.
Examples: Unify HFA, Unify SIP.
Reg-Address:
IP address of the gateway or the gatekeeper where the IP Device must register. In HiPath 3000, this is the IP
address of the HG 1500, in HiPath 4000 it is the HG 3530 or the STMI board.
Remarks:
Fields for general informations.
IP Protocol Mode
Indicates which IP version is used by the phone. If both versions are used, IP address contains the IPv4 address,
and IP address 2 contains the IPv6 address.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-459
workpoint-configuration.fm
IP Devices
IP Device Interaction
IPv4
IPv6
7-460
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Interaction
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
Reset IP Device
Restarts/resets the device.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-461
workpoint-configuration.fm
IP Devices
IP Device Interaction
Status:
Possible options:
in Service
IP phone that is currently in service.
license expired
IP phone with an expired license.
invalid SW signature
IP phone with an invalid software signature.
7-462
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Interaction
General Data
"Info" Tab
You can perform a reboot, a factory reset, and revoke all PSE-certificates used by this IP Device. No CA
certificates will be revoked.
For information on general interface operation, see Section 5.4.2, "Work Area".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-463
workpoint-configuration.fm
IP Devices
IP Device Interaction
Search
Searches for all registered workpoints that match the search criteria.
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
Reset IP Device
Restarts/resets the device.
7-464
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Interaction
Status:
IP phone status.
Possible options:
in Service
IP phone that is currently in service.
license expired
IP phone with an expired license.
invalid SW signature
IP phone with an invalid software signature.
Last Restart:
Displays date/time of last restart.
7-465
workpoint-configuration.fm
IP Devices
IP Device Interaction
7-466
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Interaction
General Data
"Info" Tab
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-467
workpoint-configuration.fm
IP Devices
IP Device Interaction
Search
Searches for all registered workpoints that match the search criteria.
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
Save
Starts a job for distributing the configuration changes. For more information, Section 15.1, "First Steps: Changing
IP Device Parameters".
Discard
The modifications carried out in the mask are discarded.
Refresh
Updates the window using the database.
7-468
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Interaction
State
Shows the state of the certificate.
Possible Options:
in Service
license expired
invalid SW signature
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-469
workpoint-configuration.fm
IP Devices
IP Device Interaction
General Data
"Info" Tab
7-470
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Interaction
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
Save
Starts a job for distributing the configuration changes. For more information, Section 15.1, "First Steps: Changing
IP Device Parameters".
Discard
The modifications carried out in the mask are discarded.
Refresh
Updates the window using the database.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-471
workpoint-configuration.fm
IP Devices
IP Device Interaction
7-472
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Interaction
General Data
This function enables you to use PINGs to check IP Device response, in other words , to check if they are still
contactable.
The following DLS areas contain information on successful or unsuccessful pings:
IP Devices > IP Device Management > Inventory Data > "Pings" Tab
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-473
workpoint-configuration.fm
IP Devices
IP Device Interaction
General Data
7-474
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Interaction
Discard
Discards any unsaved changes.
Refresh
Refreshes the content of the relevant page.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-475
workpoint-configuration.fm
IP Devices
IP Device Interaction
periodic Pings
Checkbox for activating periodic PINGs.
daily Pings
Checkbox for activating daily pings.
Execution Time:
Time for daily pings (for a calendar, see Section 5.4.2.4, "Content Area").
Only applies if "daily Pings" is active.
7-476
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Interaction
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday
Date/Time
Date/Time at which the action has started.
Device ID
Device ID of the IP Device.
E.164
E.164 number of the IP Device.
Remark
Remark on the IP Device.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-477
workpoint-configuration.fm
IP Devices
IP Device Interaction
You can define the chronological order of PING requests for IP clients in this tab.
For a description of the interface, see Section 7.4.5.1, ""IP Phones" Tab".
7-478
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Interaction
You can define the chronological order of PING requests for IP clients in this tab.
For a description of the interface, see Section 7.4.5.1, ""IP Phones" Tab".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-479
workpoint-configuration.fm
IP Devices
IP Device Interaction
General Data
"Configuration" Tab
This function lets a DLS user with an TAP, for example, create a DLS database of all IP Devices in the network
for processing purposes.
During a scan, the DLS sends a ContactMe request consisting of a short HTML message to every IP address in
the specified range. The DLS then waits to see if the relevant device sends a callback. If the ICMP ping is activated
for the scan (see "Configuration" Tab), an ICMP ping is sent before a ContactMe request to find out if the IP
address is assigned to a device.
Configuring an IP scanner
If you have not done so already, you must now create an IP scanner, that is, a configuration that indicates the IP
areas to be scanned and how the scan should proceed. To do this, proceed as follows:
1. Create a new IP scanner by clicking New.
2. Enter a name and a description for the IP scanner in the General Data area.
3. Enter the address range that should be scanned and the port where the devices can be reached for the DLS
in the "IP Ranges" Tab area.
4. If necessary, specify additional parameters in "Configuration" Tab.
Start scanning
A selection window is displayed when you click Scan IP Devices:
7-480
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Interaction
The administrator can decide whether the workpoint scan should take place first or at the same time as
registration:
Scan IP Devices
The IP devices are scanned.
Register IP Devices
The IP devices are registered.
If the administrator does not wish to allow all IP devices recognized by the scan to be registered, he or she must
delete the corresponding entries from the scan results.
NOTE: If you are using TAP to scan IP devices for the first time at a customer facility, (for example,
to record the inventory), ensure that Perform AutoDeployment is deactivated using deployment
rules. This prevents unwanted deployment in the customer network during operating hours.
If individual devices are not found during the scan, increase the timeout (see Timeout (sec)) and run a new scan.
If some of the workpoints are still not reached during scanning, a second scan operation is started for the affected
IP devices. This takes at least five minutes. During this time, the progress bar indicates 99%; the IP devices
identified during the first run can now be administered.
An entry is stored in the activity log for every IP device that was not reached during the second scan (see Section
14.1, "Job Control").
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-481
workpoint-configuration.fm
IP Devices
IP Device Interaction
NOTE: When scanning IP devices, a valid DLS server address is transferred to the scanned
IP device so that the device can contact the DLS server independently later.
This does not happen, however, if the IP device already received a DLS server address from a DHCP
server. In this case, the DLS address delivered by the DHCP server is maintained.
For information on general interface operation, see Section 5.4.2, "Work Area".
7-482
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Interaction
General Data
IP Scanner:
Name of the IP scanner.
Remarks:
Fields for general information.
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
Save
Saves any unsaved changes.
Discard
Discards any unsaved changes.
New
Creates a new IP scanner.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-483
workpoint-configuration.fm
IP Devices
IP Device Interaction
Delete
Deletes one or more IP scanners (multiple selections possible in table view).
Scan Workpoints
Starts the IP scanner displayed in Object view.
Refresh
Refreshes the content of the relevant page.
7-484
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Interaction
If the IP range specified contains other IP clients (not workpoints), malfunctions can sometimes occur
at the devices.
IP Address from
IP address for the lower limit of the IP range to be scanned.
Format: 000.000.000.000, 000 = value between 000 and 255.
IP Address to
IP address for the upper limit of the IP range to be scanned.
Format: 000.000.000.000, 000 = value between 000 and 255.
NOTE: The IP Address from and IP Address to appropriate value pair has to be identical.
Administrators are able to configure not only IP adresses,but DNS names as well.
Port
Port number for the IP addresses to be scanned.
The following default ports are used by the various workpoint types and should be entered here:
IP phone: 8085
IP Gateways: 8084
IP client: 8082
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-485
workpoint-configuration.fm
IP Devices
IP Device Interaction
WLAN phone: 80
Import File...
Loads a file in CSV format with existing IP ranges and port numbers into the IP range table.
Export File...
Saves the IP ranges and port numbers from the IP range table to a file in CSV format.
7-486
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Interaction
DLS Address:S
IP address of the DLS server on the EWS.
Format: 000.000.000.000 (000 = value between 000 and 255).
DLS Port:
Port number of the DLS server on the EWS.
Value range: Up to five digits.
Allow ICMP-Pings:
If the checkbox is activated, ICMP pings are used when scanning. This speeds up IP device scans because
ContactMe requests are only sent to IP addresses where the ICMP ping was successful.
NOTE: This checkbox must be deactivated if the network does not support ICMP pings as otherwise
the IP device scan is unable to deliver a result.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-487
workpoint-configuration.fm
IP Devices
IP Device Interaction
ICMP-Delay (ms):
Interval between ICMP pings to ensure that the ICMP pings are not blocked by the operating system.
Number of Retries:
Maximum number of retries for a scan. The value is evaluated for each IP address.
Default: 1
Timeout (sec)
The maximum amount of time that may elapse between a Contact-Me request from the DLS and registration of
the IP Devices involved.
The entered value must be greater than the value Section 6.9.2, ""DCMP" Tab"
Possible Options:
0 - 3600, default: 60 seconds
7-488
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Interaction
New
An IP Device that is reregistered during a scan is indicated by a checkmark.
Status
Displays the status of the scan for each individual IP Device.
Possible values:
running
confirmed
finished
failed
Device ID
Displays the device ID of the scanned IP Device. This is used for unique identification of the IP device. In
IP phones, this is generally identical to the MAC address.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-489
workpoint-configuration.fm
IP Devices
IP Device Interaction
IP Address
Displays the IP address of the scanned IP Device.
Port
Displays the port that the scanned IP Device uses to communicate with the DLS.
Protocol
Displays the protocol that the scanned IP Device uses to communicate with the DLS.
E.164
Displays the E.164 number of the scanned IP Device.
Basic E.164
Displays the basic E.164 number of the scanned IP Device.
Device Type
Displays the phone type of the scanned IP Device.
Example: optiPoint 410 advance
Software Type:
Displays the software type of the scanned IP Device.
Example: Unify HFA, Unify SIP.
SW Version
Displays the software version installed on the scanned IP Device.
Example: 6.0.53
7-490
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Interaction
Last Scan
Displays the data and time of the last scan.
Status:
Displays the current scan status.
Example: running, finished
Action Number:
Displays the action number for the current scan.
IP Addresses
To be scanned:
Displays how many IP addressed within the IP range are yet to be scanned.
Already scanned:
Displays how many IP addressed within the IP range are already scanned.
Workpoints
Detected:
Displays how many workpoints have been found by the scan.
Thereof new:
Displays how many of the workpoints found by the scan are not yet registered.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-491
workpoint-configuration.fm
IP Devices
IP Device Management
Inventory Data
Trash
IP Infrastructure
IP Device Configuration
7-492
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Management
General Data
"Information" Tab
"Accounting" Tab
"Pings" Tab
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-493
workpoint-configuration.fm
IP Devices
IP Device Management
General Data
This part of the content area is used for entering parameters in Search view to find a specific group of workpoints.
The base data associated with the workpoints found is displayed in the Object view (no changes possible except
under Remarks).
NOTE: For further information about the Search view, please see Section 5.5, "Search Functionality".
IP Address:
IP address of the workpoint. For OpenStage, in IPv4 or IPv6 address is displayed here. See also the description
of the IP Protocol Mode parameter
Example: 192.117.1.193
The value is read-only if it was dynamically assigned with DHCP.
Device ID:
ID for unique identification of the IP device. In IP phones, this is generally the MAC address.
Example: 00:0E:A6:85:71:80
Device Type:
Workpoint device type.
All workpoint types supported by DLS can be found in Section 3.4, "Area of Application".
Example: optiPoint 410 standard
E.164:
Complete E.164 subscriber number (Basic Profile or Mobile Profile).
Example: 498972212345
For information on the meaning of the E.164 station number in relation to mobility, see Section 3.8.3, "Mobility ID".
7-494
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Management
Basic E.164:
Complete E.164 phone number (Mobility Phone).
Example: 498972212345
For information on the meaning of the E.164 station number in relation to mobility, see Section 3.8.3, "Mobility ID".
IP Address 2:
Second IP address of the IP phone, if it has an IPv6 address.
Available for OpenStage only.
SW Version:
Software version used by the workpoint.
Example: 5.0.12
Information on the difference between the software and license version can be found in Section 15.7, "Distribution
of Workpoint Software".
SW Type:
Software type used by the workpoint.
Examples: Unify HFA, Unify SIP.
PEN:
Position of the gateway assembly group (plug-in position).
Reg-Address:
IP address of the gateway or the gatekeeper where the workpoint must register. In HiPath 3000, this is the IP
address of the HG 1500, in HiPath 4000 it is the HG 3530 or the STMI board.
Last Registration:
Time of the last workpoint registration.
For information on selecting a time segment for a search, see Section 5.4.2.4, "Content Area".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-495
workpoint-configuration.fm
IP Devices
IP Device Management
Remarks:
Fields for general information.
IP Protocol Mode
Indicates which IP version is used by the phone. If both versions are used, IP address contains the IPv4 address,
and IP address 2 contains the IPv6 address.
Only available for openStage.
Possible options:
IPv4
IPv6
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
Save
Starts a job for distributing the configuration changes. For more information, see Section 15.1, "First Steps:
Changing IP Device Parameters".
Discard
The modifications carried out in the mask are discarded.
7-496
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Management
Export File
The inventory data are exported into a csv formatted file.
Refresh
Refreshes the window contents from the database.
Clear Trash
Deletes completely all IP Devices marked to be deleted from the DLS.
Restore IP Device
Moves IP Device out of trash. Afterwards the IP Phone can be administered by DLS.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-497
workpoint-configuration.fm
IP Devices
IP Device Management
Part Number:
Part number of the workpoint; this number identifies the relevant hardware.
The value is read-only.
Language Package:
Name of installed Language Package.
The value is read-only.
Key Module:
Number of Self Labeling Keys Modules connected.
The value is read-only.
7-498
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Management
Byte 2
Byte 3
Byte 4
yyyywwww
wwdddlll
aassssss
sssssttt
Definition:
Section
Length
Meaning
Example
yyyy
4 bits
0001 = 2001
w...w
6 bits
Calendar week
000001 = Week 1
ddd
3 bits
Day
lll
3 bits
Design Line
aa
2 bits
Tester Group
0 - 3, factory setting
s...s
11 bits
Serial Number
0 ... 2047
ttt
3 bits
Tester Number
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-499
workpoint-configuration.fm
IP Devices
IP Device Management
Netboot Version:
Version of Netboot.
The value is read-only.
None
CCFL
LED
Signature module
Active when an optiPoint signature module is connected.
The value is read-only.
Recorder Adapter
Active when an optiPoint recorder module is connected.
The value is read-only.
Acoustic Adapter
Active when an optiPoint acoustic module is connected.
The value is read-only.
Gigabit Ethernet
Indicates whether the device has a gigabit LAN interface.
7-500
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Management
QWERTZ
(German layout)
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-501
workpoint-configuration.fm
IP Devices
IP Device Management
QWERTY
(American layout)
7-502
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Management
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-503
workpoint-configuration.fm
IP Devices
IP Device Management
Department:
Defined department of the associated Business Group subscriber.
Accounting ID:
Accounting ID of the subscriber.
Account ID is by default subscriber (Subscriber ID).
Retailer ID:
Retailer ID of the subscriber.
Retailer ID is by default subscriber (Subscriber ID).
Billing ID:
Billing ID of the subscriber.
Billing ID is by default subscriber (Subscriber ID).
7-504
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Management
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-505
workpoint-configuration.fm
IP Devices
IP Device Management
7.5.2 Trash
Call: Main Menu > IP Devices > IP Device Management > Trash
This area features the following components:
General Data
"Information" Tab
7-506
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Management
In Trash since:
Date at which the IP Device has been put into trash.
Last Synchronization:
Date of last element manager synchronization for this E.164 number.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-507
workpoint-configuration.fm
IP Devices
IP Device Management
7.5.3 IP Infrastructure
Call: Main Menu > IP Devices > IP Device Management > IP Infrastructure
In this screen, the administrator can view the IP infrastructure data sent by an application to the DLS. The
infrastructure policy is used for automatic adaptation: A default device profile is searched to which that location is
assigned for which this infrastructure policy is defined. This profile will be applied to the IP Phone.
The infrastructure policy is not part of the API interface, though it will be mapped from the switch IP address, the
switch port and the Network Policy. The mapping has to be configured by the administrator in the screen
Administration > Server Configuration > Infrastructure Policy.
This area features the following components:
General Data
7-508
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Management
Infrastructure Policy:
Currently enabled policy, mapped from Switch IP Address, Switch Port and Network Policy.
Switch Name
Name of the edge switch device is currently plugged in.
Switch Location
Location of the edge switch device is currently plugged in.
Switch IP Address
IP address of the edge switch device is currently plugged in
Switch Port
Port of the edge switch device is currently plugged in.
Port Alias
Port Alias
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-509
workpoint-configuration.fm
IP Devices
IP Device Management
Port ELIN
Port ELIN
Network Policy
Currently enabled network policy for this device.
Remediation Info
Long description of Network Policy.
Device Status
Connection status of device
Possible options:
plugged in
plugged off
unknown
7-510
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Management
General Data
"General" Tab
"Profile" Tab
"DCMP" Tab
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-511
workpoint-configuration.fm
IP Devices
IP Device Management
General Data
This part of the content area is used for entering parameters in Search view to find a specific group of IP Devices.
The base data associated with the IP Devices found is displayed in the Object view (no changes possible except
under Remarks).
NOTE: For further information about the Search view, please see Section 5.5, "Search Functionality".
IP Address:
IP address of the IP Device.
Example: 192.117.1.193
The value is read-only if it was dynamically assigned with DHCP.
Device ID:
ID for unique identification of the IP device. In IP phones, this is generally the MAC address.
Example: 00:0E:A6:85:71:80
7-512
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Management
Device Type:
IP Device type.
All IP Device types supported by DLS can be found in Section 3.4, "Area of Application".
Example: optiPoint 410 standard
E.164:
Complete E.164 subscriber number (Basic Profile or Mobile Profile).
Example: 498972212345
For information on the meaning of the E.164 station number in relation to mobility, see Section 3.8.3, "Mobility ID".
Basic E.164:
Complete E.164 phone number (Mobility Phone).
Example: 498972212345
For information on the meaning of the E.164 station number in relation to mobility, see Section 3.8.3, "Mobility ID".
IP Address 2:
Second IP address of the IP phone, if it has an IPv6 address.
Available for OpenStage only.
SW Version:
Software version used by the IP Device.
Example: 5.0.12
Information on the difference between the software and license version can be found in Section 15.7, "Distribution
of Workpoint Software".
SW Type:
Software type used by the IP Devices.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-513
workpoint-configuration.fm
IP Devices
IP Device Management
Reg-Address:
IP address of the gateway or the gatekeeper where the IP Device must register. In HiPath 3000, this is the IP
address of the HG 1500, in HiPath 4000 it is the HG 3530 or the STMI board.
Last Registration:
Time of the last IP Device registration.
For information on selecting a time segment for a search, see Section 5.4.2.4, "Content Area".
IP Protocol Mode
Indicates which IP version is used by the phone. If both versions are used, IP address contains the IPv4 address,
and IP address 2 contains the IPv6 address.
Only available for openStage.
Possible options:
IPv4
IPv6
Device Family:
Type of device.
Possible options:
IP Phone
IP Client
IP Gateway
Windows Account :
The respective domain \ Windows Account of the client. If the device is a client the field contains a value, else it
is void.
7-514
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Management
Cloud Pin:
The cloud pin string consists only of numeric digits. A redirect code is extracted from the pin entered by the phone
user, as part of the cloud deployment process.
The cloud pin is added as a new optional item in all workpoint messages initiating a connection with DLS and is
used by DLS for device identification with precedence over the E.164 number. The cloud-pin-value is sent by the
phone in SHA-256 hashed format.
NOTE: If DLS is unable to configure the phone based on the mac-addr inventory item alone, the DLS
will look at cloud-pin-value. If DLS is able to match the client-pin-value unambiguously, it will configure
the phone accordingly. This includes writing a new value for the e164 item (if a corresponding e.164phone number could be determined by DLS). If the cloud-pin value is not included in the inventory
items or is empty, the DLS will look at the E.164 inventory item for device identification.
NOTE: The value that should be entered in 'Cloud Pin' textbox is the same string assigned to the
phone after its factory reset. Cloud Pin contains the redirect code,hence the longer string.
Remarks:
Fields for general information.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-515
workpoint-configuration.fm
IP Devices
IP Device Management
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
Save
Starts a job for distributing the configuration changes. For more information, see Section 15.1, "First Steps:
Changing IP Device Parameters".
Discard
The modifications carried out in the mask are discarded.
Refresh
Refreshes the window contents from the database.
New
Creates a new configuration.
Delete
Deletes the record of the current selected IP Device from DLS database.
Export File
The configuration data are exported into a csv formatted file.
7-516
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Management
Import File
The configuration data are imported from a csv formatted file. Section 15.12, "Importing and Exporting Plug&Play
Data"describes the format.
Copy IP Device
Copy data of an IP Device, see als chapter Section 16.6, "Replacing an IP Device", Section 16.8, "Replacing HFA
with SIP Software and Vice Versa with Identical Device IDs", Section 16.13.7, "Replace IP Phone".
Simulate Plug&Play
Test of location and default profile configuration. Location data are entered and after clicking "Simulate
Plug&Play", the data sent to the phone which might register with the DLS, can be checked.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-517
workpoint-configuration.fm
IP Devices
IP Device Management
Administration disabled
If this checkbox is activated, IP Device administration via DLS is disabled. This temporary block prevents
accidental changes on the IP Device.
Autodeployment disabled
If this checkbox is activated, autodeployment (see Section 15.7.2, "Automatic Deployment") is disabled for the
IP Device.
Preconfigured IP Device
If this checkbox is automatically activated, the IP device is preconfigured.
7-518
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Management
Autoconfiguration
Activate Plug&Play
If this checkbox is activated, all data in this data record is assigned to the IP Device at the next registration.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-519
workpoint-configuration.fm
IP Devices
IP Device Management
Location
Current location of the IP Device. The value is set during registration and is displayed only herein. (For meaning
and configuration of the location, see Section 6.3.2, "Location".)
none
free
in use
multiple use
7-520
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Management
System Type:
Type of Element Manager assigned to the IP Device.
Possible values:
HiPath 4000
HiPath 3000/5000
Other
OpenScape Voice
Imported
OpenOffice EE
OpenScape Business
Switch:
Switch Name (For OpenScape Voice Assistant with Multiple Switch Support only).
Business Group:
Business Group Name (For OpenScape Voice Assistant).
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-521
workpoint-configuration.fm
IP Devices
IP Device Management
Last Synchronization:
Time of the last synchronization with the system.
Last Update:
Time of the last change to these settings.
7-522
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Management
NOTE: "Profile" Tab includes the info of the last deployed Profile. It does not specify nor bounds that
subscriber record to the Profile assigned since the profile parameters are a one-time only propagation
of data. As such, if an administrator modifies the name (or contents) of a Profile that won't be reflected
back in this UI section. Name will still depict the last Profile deployed and not the newly adjustable
profile name.
NOTE: Since there is no direct linkage after the initial Profile deployment has taken place, if those
fields are used as a search criteria by administrators, it should be first manually validated for any
changes in the configuration since new adaptations might not reflect properly anymore. Profile
Management of DLS will exclusively notify on the UI if Profile contained data have been altered and
those Profiles are already assigned on subscribers that changes won't take immediate effect unless
a Profile gets re-applied first.
Device Profile:
Selection of standard device configurations defined in Profile Management > Device Profile to be sent to the
IP Device. This sets all existing parameters in the profile and any values previously set are overwritten. The
parameters that are not replaced by the profile retain their values.
NOTE: When assigning a profile over a Virtual Device under IP Device Configuration,the list of
offered Profiles is filtered and matched to that of the "Supported Devices of IP Device" Tab for profiles.
Assigned:
Time and date when the device profile was last assigned to the IP Device.
Reapply:
Apply the Device Profile to the IP Device again.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-523
workpoint-configuration.fm
IP Devices
IP Device Management
Basic Profile:
Selection of a standard user configuration defined in Profile Management > User Data Profile to be sent to the
IP Device. This resets all parameters. The parameters that are not set by the profile are assigned default values.
Assigned:
Time when the Basic Profile was last assigned to the IP Device.
Reapply:
Apply the Basic Profile to the IP Device again.
7-524
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Management
DLS Connectivity
DLS Server Address:
IP address or host name of the DLS server. This value is automatically entered in the IP Device if a DHCP server
is available and appropriately configured ( refer tot he Unify Experts Wiki Portal under
http://wiki.unify.com/wiki/Configuring_the_DHCP_Server_for_DLS
DLS Port:
Port number of the DLS server. This value is automatically entered in the IP Device if a DHCP server is available
and appropriately configured (refer to the Unify Experts Wiki Portal under
http://wiki.unify.com/wiki/Configuring_the_DHCP_Server_for_DLS
Default: 18443
Contact-me URI:
This field is for display purposes and contains the complete URL used by the IP Device to set up a connection to
the DLS.
Security Settings
Secure mode required
If this checkbox is activated, mutual authentication is enabled for the DLS and the IP Device. The authentication
process (bootstrap) begins the next time the IP Device registers at the DLS or is scanned.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-525
workpoint-configuration.fm
IP Devices
IP Device Management
Security Status:
Display the security mode for communication between the DLS and the IP Device.
Possible options:
Standard
In this mode, the DLS is authenticated using a standard certificate which is the same for all DLS installations.
Insecure
The previous "Default" mode is considered unsecure once the checkbox "Secure mode required" is activated.
Secure
This status is displayed once mutual authentication has been carried out between the DLS and the IP Device.
Pending
The credentials have been transferred to the device, the device has responded but a secure connection
between the DLS and the device is not yet complete.
Credential transmitted
The credentials have been transferred to the device but the device has not yet responded.
Credential refused
The device rejects secure authentication (for example, because it is not technically ready).
Tan failed
In standard or individual PIN mode, both the device and the DLS must verify part of the PIN. If the number of
failed verification attempts on the DLS side exceeds the threshold set, the security status is set to "Tan failed".
Blocked
This security status is not currently in use.
Go to Default
This security state is displayed when the security mode has been changed, but the IP Device does not
respond.
PIN Mode:
Possible options:
No PIN
Access data is sent unencrypted to the IP Device.
Default PIN
A standard PIN is used for several IP Devices. This is generated automatically by the DLS (see Section 6.9.1,
""Secure mode" Tab").
Individual PIN
An individual PIN is created for the selected IP Device.
7-526
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Management
Unknown
This PIN mode is only available when the DLS interface is in Search mode. When moving the DLS to another
server, the PIN mode cannot be retrieved. Therefore, the PIN mode is set to "unknown". This has no influence
on the functionality.
Reset
If this checkbox is activated, the security mode can be reset to "Insecure" by clicking Save. The DLS must then
send a new security configuration to the IP Device, that is, the bootstrap operation must be repeated (see also
Secure mode required).
PIN:
This is entered locally at the IP Device and used to encrypt access data that was sent by the DLS and is required
for the transfer to secure mode. The device generally prompts you to enter the PIN. Alternatively, the PIN may be
preconfigured in the local administration menu.
Scan
Starts the scan for IP Devices (only with Device Family - IP Gateway). In the process of scanning, the
Bootstrapping process is executed. Bootstrapping is the process used to raise the interface security between an
IP Device and DLS from Default Mode to Secure Mode.
NOTE: If you select "Scan" for a device other than IP Gateway (ie. IP Phone or IP Client) the
action is finished with error :"1355: Server is not able to create a job: Device is not a IP Gateway".
Credentials
Client Credential
The device uses these credentials to authenticate itself at the DLS.
Possible options:
Active
The device last authenticated itself using the active client credentials.
Old
The device last authenticated itself using old client credentials.
Unknown
In the DLS, it is currently unknown whether the device possesses active, old or invalid client credentials (for
example, when new client credentials have been created or client credentials have been imported).
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-527
workpoint-configuration.fm
IP Devices
IP Device Management
Rejected
The device last attempted to authenticate itself using invalid client credentials.
Server Credential 1
Fingerprint of trust anchor relative to credential 1, deployed to IP Device and used to authenticate the DLS.
Server Credential 2
Fingerprint of trust anchor relative to credential 2, deployed to IP Device and used to authenticate the DLS.
NOTE: Any DLS that presents either credential 1 or credential 2 is accepted by the IP Device.
7-528
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Management
Security State
Maximum number of entries:
Maximum number of security log entries to be displayed.
Security State
Shows the security state of the IP Device at a given time.
Date/Time
Displays the time at which the IP Device had a particular security state.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-529
workpoint-configuration.fm
IP Devices
IP Device Management
Date/Time
Displays the time of the contact try.
Error reason
Error message.
Possible messages:
Error Message
Description
7-530
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Management
Error Message
Description
The IP Device has not accepted the new client certificate sent
by the DLS.
device is blocked
The IP Device must use the secure port (e. g. 18444) instead
of the standard port (e. g. 18443.
No DLS license
licenses exceeded
synchronisation exception
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-531
workpoint-configuration.fm
IP Devices
IP Device Management
Error Message
Description
missing e164
The E.164 has been expected by the DLS, but the IP Device
has not sent it.
missing items
try later
HFA mobility.
7-532
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Management
Poll Interval:
Specifies the intervals at which the device polls the DCMP.
DCMP state:
Provides information about the communication between the device and the DCMP.
Possible values:
Enabled
The device is in DCMP mode, that is, the DLS contacts the device via the DCMP server.
Disabled
The device is not in DCMP mode, that is, the DLS contacts the device directly.
Refused
The device denies DCMP mode (for example, when it is technically unable to operate in DCMP mode).
Outdated
DCMP data on the DLS has changed and must be communicated to the device.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-533
workpoint-configuration.fm
IP Devices
IP Device Management
Disable in progress
DCMP for this device is deactivated in the DLS and the modified configuration must be communicated to the
device.
7-534
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Management
Reset
Resets all fields to inactive.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-535
workpoint-configuration.fm
IP Devices
IP Device Management
Reset
Resets all fields to inactive.
7-536
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
workpoint-configuration.fm
For internal use only
IP Devices
IP Device Management
Reset
Resets all fields to inactive.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
7-537
workpoint-configuration.fm
IP Devices
IP Device Management
Archive:
Path for the ZIP archive file on the DLS system.
Archived by
Name of the DLS user who created the archive.
Archived at
Date and time of the archive.
Restored at
Date and time of the archive restore.
7-538
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
8 Mobile Users
Call: Main Menu > Mobile Users
This menu item consists of the following areas:
Mobility Statistics
The Mobile Users area is for displaying and modifying Mobile User parameters. For an introduction to mobility,
see Section 3.8, "DLS Mobility - General Information".
IMPORTANT: Changes to data in workpoint configuration masks created with templates are not
automatically applied to these templates.
These changes must be manually saved to the template (Section 15.5, "Editing Templates").
NOTE: A workpoint can only be configured after successful registration at the DLS. The workpoint
must be aware of the corresponding DLS IP address for registration. Registration at the DLS is
achieved by:
- reading out workpoint data via the DLS, see Section 7.4.6, "Scan IP Devices" and by
- plugging the LAN connector or power supply into the workpoint.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-1
mobile-users.fm
Mobile Users
Gateway/Server
IP Routing
Features
Quality of Service
Security Settings
Telephony
Dialing Properties
Time Parameters
Audio Settings
Applications
LDAP
User Settings
SIP Mobility
Keysets/Keylayout
Miscellaneous
8-2
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
General Data
This part of the contents area is identical for all interfaces associated with this menu. It is used for entering
parameters in Search view to find a specific group of IP phones. The base data associated with the IP phones
found is displayed in Object view (no changes possible except under Remarks).
NOTE: For further information about the Search view, please see Section 5.5, "Search Functionality".
E.164:
Complete E.164 phone number (Mobility ID or basic user phone number).
Example: 498972212345
For information on the meaning of the E.164 station number in relation to mobility, see Section 3.8.3, "Mobility ID".
IMPORTANT: While attempting the related jump, you shall be redirected to the SIP Mobile User
Configuration menu options available.
User Type:
Displays the type of data used.
Possible options:
Mobile User
Mobile User data.
For more information on mobility, see Section 3.8, "DLS Mobility - General Information".
Status:
Displays mobility status.
Possible options:
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-3
mobile-users.fm
Mobile Users
For more information on mobility, see Section 3.8, "DLS Mobility - General Information".
IP Address:
IP address of the IP phone.
Example: 192.117.1.193
The value is read-only at this location.
IMPORTANT: While attempting the related jump, you shall be redirected to the IP Phone
Configuration menu options available.
Device ID:
Physical MAC address of the IP phone.
Example: 00:0E:A6:85:71:80
IMPORTANT: While attempting the related jump, you shall be redirected to the IP Phone
Configuration menu options available.
Device Type:
Device type of the IP phone.
You can view all IP phone types supported by the DLS in Section 3.4, "IP Devices / versions supported".
Example: optiPoint 410 standard
IP Address 2:
Second IP address of the IP phone, if it has an IPv6 address.
This is a read only value.
8-4
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Remarks:
Fields for general information.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-5
mobile-users.fm
Mobile Users
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
Save
Starts a job for transmitting configuration changes to the selected object. For more information, see Section 15.1,
"First Steps: Changing IP Device Parameters". In Templates view, parameters are saved in the selected
templates. For more information, see Section 15.5, "Editing Templates".
Discard
The modifications made are not transmitted to the selected object and are deleted from the input mask.
Refresh
The parameters are reloaded from the database.
Get
Loads a template that has already been saved. For more information, see Section 15.5, "Editing Templates".
Rename
Changes the name of a saved template. For more information, see Section 15.5, "Editing Templates".
Delete
Deletes a saved template. For more information, see Section 15.5, "Editing Templates".
8-6
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
8.1.1 Gateway/Server
Call: Main Menu > Mobile Users > SIP Mobile User Configuration > Gateway/Server
This area features the following components:
General Data
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-7
mobile-users.fm
Mobile Users
8-8
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
SIP URL:
SIP address of the IP phone.
Format: <SIP user ID>@<Domain>.
Terminal Details
Terminal Name:
Name of the IP phone used as a synonym for the phone number during registration.
Only necessary if the Register by Name check box is selected and the registrar server is appropriately
configured.
Register by Name
Check box for activating the function that sends the contents of the Terminal Name field as part of registration.
If the check box is not active, the contents of the E.164 number field are also sent in the course of registration.
Display ID:
Name of the IP phone as shown on the workpoint display.
Value range: max. 24 alphanumeric characters.
NOTE: Please refer to Section 15.13.1, "Macro Command Syntax" in case you need to use macro
commands, otherwise the DLS will not save the proper Display ID.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-9
mobile-users.fm
Mobile Users
Use Display ID
If this check box is activated, the Display ID is shown on the workpoint.
8-10
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
SIP Routing:
Possible options:
Gateway
A gateway is used for SIP routing.
Server
An SIP proxy is used for SIP routing.
Direct
If Direct or Gateway is selected, no registration messages are sent. Registration messages are sent to the
registrar server for the Server routing mode.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-11
mobile-users.fm
Mobile Users
8-12
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Outbound Proxy
Check box for activating an SIP proxy for outbound calls.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-13
mobile-users.fm
Mobile Users
Together with SIP Default OBP Domain this check box controls outbound call routing on the basis of the number
dialed or the user ID.
For more information, see Chapter 17, "Outbound Proxy".
Sequence
CRLF
SIP Realm:
SIP range in which the workpoint is operated. SIP realm is used to identify the telephone at the SIP server.
SIP Password:
Password required for accessing the SIP server.
MLPP Settings
MLPP Base
Possible options:
Local
Server
8-14
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
dsn
dsn-000000
uc
uc-000000
dsn+uc
Other domain
Broadsoft
OpenScape Voice
Sylantro
other
HiQ8000
Genesys
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-15
mobile-users.fm
Mobile Users
8.1.2 IP Routing
Call: Main Menu > Mobile Users > SIP Mobile User Configuration > IP Routing
This area features the following components:
General Data
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
8-16
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Terminal Hostname:
Host name of the terminal.
Permitted characters: letters, digits, hyphens, underscores, and periods; case-sensitive; maximum length: 63
characters.
The value is read-only if it was dynamically assigned with DHCP.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-17
mobile-users.fm
Mobile Users
8.1.3 Features
Call: Main Menu > Mobile Users > SIP Mobile User Configuration > Features
This area features the following components:
General Data
"Availability" Tab
"Dialplan" Tab
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
8-18
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Group pick-up
Group Pickup URI:
URI of the group pickup.
Only available in SIP workpoints.
Station-controlled Conference
Conference Factory URI:
URI for setting up conference calls.
Only available in SIP workpoints.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-19
mobile-users.fm
Mobile Users
Callback
Callback-busy
URI of the server that controls the "Callback-busy" feature.
Only available for optiPoint and OpenStage up to V2.
Callback FAC
URI to be used for stimulus callback call requests.
Only available for OpenStage V3.0 onwards.
Deflection
Deflect Destination:
Destination number for call forwarding.
Only available in SIP workpoints.
8-20
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
BLF
BLF Pickup Code:
BLF Pickup Code.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-21
mobile-users.fm
Mobile Users
Ordinary
Hot Line
Warm Line
8-22
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Open Listening
Open Listening settings.
Possible options:
Standard Mode
To switch to Open Listening mode, the user must press and hold the Open Listening key while returning the
handset to the cradle.
US Mode
To switch to Open Listening mode, the user must first press the Open Listening key and then return the
handset to the cradle.
Call Recorder
Call recording
Check box for activating call recording.
Recording Mode
Determines the behaviour of the call recording.
Possible options:
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-23
mobile-users.fm
Mobile Users
Manual
Auto Start
All Calls
Disabled
(Display only)
Audible Notification
Select the tone for audible notification.
Possible options:
Off
On / Single Shot
Repeated
Automatic Start
When activated, call recording is started automatically, with incoming calls and outgoing calls. The user can switch
the recording on or off during a conversation.
The checkbox is effective only if voice recording is activated on the phone.
All Calls
When activated, call recording is started automatically, with incoming calls and outgoing calls. The user can not
control the recording.
The checkbox is effective only if voice recording is activated on the phone.
Audible Indication
A beep signals to the called party that the phone call is being recorded.
8-24
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Transfer on Ring
Checkbox for activating the "Transfer on Ring" feature
Only available in SIP workpoints.
Transfer on Hangup
Checkbox for activating the "Transfer on Hangup" feature.
Only available in SIP workpoints.
Bridging enabled
When active, call bridging is enabled.
Only available in SIP workpoints.
uaCSTA allowed
Checkbox to activate the "uaCSTA" feature.
Only available in SIP workpoints.
Phonebook lookup
Checkbox for activating the "Phonebook lookup" feature.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-25
mobile-users.fm
Mobile Users
Callback
Callback: Busy
Checkbox for activating the "Callback-busy" feature.
Only available in SIP workpoints.
Callback: No reply
Checkbox for activating the "Callback-no reply" feature.
Only available in SIP workpoints.
Callback: Cancel
When active, the user can cancel callback requests.
Callback
Activates Callback.
Only available for OpenStage V3 onwards.
On
Off
Call Logging
Enable Call Log
Checkbox that indicates whether Call logging is enabled.
Missed Logging
Indicates whether calls completed elsewhere will be logged on phone.
8-26
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Possible options:
Delete Entry
Indicates whether calls log entries are deleted in case there is a call to an entry in Missed calls list.
Possible options:
Outgoing calls that are made to entries in Missed calls tab of call log and that are connected will not be deleted
from call log.
Outgoing calls that are made to entries in Missed calls tab of call log and that are connected will be deleted from
call log.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-27
mobile-users.fm
Mobile Users
Video Calls
Allow Video Calls
Checkbox for activating Video Calls.
If the Allow Video Calls checkbox is activated , then video calls will be allowed.
Incoming Calls
Allow Deflection
Check box for activating Call Deflection.
8-28
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
CTI Calls
Auto answer
Check box for activating Auto Answer.
Only available in SIP workpoints.
Auto reconnect
Check box for activating automatic reconnection of a parked call.
Only available in SIP workpoints.
Immediate Dialing
If this check box is active, immediate dialing is executed as soon as the entered string matches a dial plan entry.
Only available in SIP workpoints.
Outgoing calls
Autodialing delay (sec):
Delay for Automatic Dialing in seconds.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-29
mobile-users.fm
Mobile Users
Callback
Allow Callback Busy
Checkbox for activating Callback on Busy.
Only available for OpenStage V1 and V2.
Callback Option
Callback Option.
Only available for OpenStage starting with V3.
Established Connections
Allow Call Transfer
Check box for activating Call Transfer.
8-30
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Allow Conferences
Check box for activating Conferences.
Toggle associate
Checkbox for activating associated toggle.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-31
mobile-users.fm
Mobile Users
Call Hold
Check box for activating the function for placing calls on hold.
Area of validity: Only applies to SIP workpoints.
Call deflection
Check box for activating manual forwarding for incoming calls (CD).
Only available in SIP workpoints.
Call forwarding
Check box for activating automatic call forwarding (CF).
Only available in SIP workpoints.
8-32
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Call duration
Check box for activating the function for displaying the call duration.
Only available in SIP workpoints.
Call waiting
Check box for activating visual and/or acoustic alerting for waiting calls (CW).
Only available in SIP workpoints.
Call transfer
Check box for activating the function for transferring calls (ECT).
Only available in SIP workpoints.
Call pickup
Check box for activating the function for picking up parked calls.
Only available in SIP workpoints.
Auto reconnect
Check box for activating the auto reconnect feature.
Only available in SIP workpoints.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-33
mobile-users.fm
Mobile Users
Music on hold
Check box for activating music on hold for held and parked calls.
Only available in SIP workpoints.
Do not disturb
Check box for activating the do-not-disturb function (optical alerting and ring only).
Only available in SIP workpoints.
Message waiting
Check box for activating alerting for waiting messages (MWI).
Only available in SIP workpoints.
Local conference
Check box for activating the function for setting up a local conference.
Only available in SIP workpoints.
Auto answer
Check box for activating auto answer.
Only available in SIP workpoints.
PC Interface
Check box for activating the PC interface.
8-34
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
LDAP on APM/DSM
Check box for activating the LDAP function on the optiPoint application module/display module.
Only available in SIP workpoints.
Telephony on APM/DSM
Check box for activating the telephony function on the optiPoint application module/display module.
Only available in SIP workpoints.
ENB on APM/DSM
Check box for activating the electronic notebook on the optiPoint application module/display module.
Only available in SIP workpoints.
Call park
Check box for activating the function for parking calls.
Only available in SIP workpoints.
Call join
Check box for activating the function for joining calls.
Only available in SIP workpoints.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-35
mobile-users.fm
Mobile Users
Blind Transfer
Checkbox for activating the feature "Blind Transfer".
Repertory Dial
Checkbox for activating the feature "Repertory Dial".
CTI
Checkbox for activating CTI.
Line Overview
Checkbox for activating the "Line Overview"
Feature Toggle
Checkbox for activating the feature "Feature Toggle".
8-36
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Group Pickup
Checkbox for activating the feature "Group Pickup".
Video Call
Checkbox for enabling the feature " Video Call ".
Ext/Int Forwarding
Checkbox for enabling / disabling the External/Internal Forwarding.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-37
mobile-users.fm
Mobile Users
8-38
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Digit String
Digit String Digit string for executing this action.
Only available in SIP workpoints.
Action
Action executed for this digit string.
Possible options:
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-39
mobile-users.fm
Mobile Users
Min Length
Minimum digit string length for digit string interpretation.
Only available in SIP workpoints.
Max Length
Maximum digit string length for digit string interpretation.
Only available in SIP workpoints.
Timer
Delay before the action is performed.
Value range: 1 ... 9 seconds.
Only available in SIP workpoints.
Terminating Character
Character that ends the digit string entered.
Possible options:
Special Indication
Possible options:
-b- bypass
Terminator sent
Displays whether the terminating character is included in the digit string.
8-40
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Dial Plan
Check box for activating the dial plan. The entries in the "Dialplan" Tab are interpreted if this check box is active.
Only available in SIP workpoints.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-41
mobile-users.fm
Mobile Users
NOTE: A template for Ringer Melody / Tone can be created by searching for an IP Device with
entries in Ringer Melody / Tone (empty entries are allowed as well). Use the action Copy to
Template to create a template. There must be 15 entries, which may be empty.
This template can be modified, saved, and applied.
MLPP Ringer File
Precedence ringer for priority calls.
Special Ringers
Internal call
Default value : Bellcore-dr1
External call
Default value : Bellcore-dr2
Recall
Default value : Bellcore-dr3
Emergency
8-42
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Special 3
Index
Specifies the sequence of the signaling entries.
This is automatically set. The field is provided for display only.
Alert Info
If the string specified here is identical with a special string which is sent to the phone in the SIP alert info header,
the corresponding ringtone is used
Only available in SIP workpoints.
Melody
Type of ring melody.
Possible options: Melody 1 ... 8, Melody off.
Only available in SIP workpoints.
Tone
Ringtone sequence.
Possible options:
1
= 1 sec ON, 4 sec OFF
2
= 1 sec ON, 2 sec OFF
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-43
mobile-users.fm
Mobile Users
3
= 0,7 sec ON, 0,7 sec OFF, 0,7 sec ON, 3 sec OFF
Tone Duration
Duration of the ringtone.
Value range: 1 ... 300 seconds.
Default: 60 seconds.
Only available in SIP workpoints.
Ringer File
Name of the audio file containing the ringtone.
These two configurations (special ringers & ringer melody table) cannot be performed in a single
step.A new Alert Info and Special Ringer cannot be added at the same time in the Special Ringers
table & the Distinctive Ringers table.Before a Special Ringer is configured, make sure its Alert Info is
already configured,
i.e. first configure Bellcore-dr1 in lower table, press Save and then configure this Alert Info in Special
Ringers Internal Call & press Save again.
8-44
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
NOTE: The additional Call Forwarding settings (for external/internal) shall be available if the option
"Support of Server Based Features" is enabled under Mobile Users> SIP Mobile User
Configuration> Features> "Server based Features" Tab.
Call Forwarding Unconditional
Forward Any Call
Checkbox for activating unconditional Call Forwarding.
Destination:
Call number of the Call Forwarding destination.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-45
mobile-users.fm
Mobile Users
Destination:
Call number of the External Call Forwarding destination.
Destination:
Call number of the Internal Call Forwarding destination.
Destination:
Call number of the Call Forwarding destination.
Destination:
Call number of the External Call Forwarding destination.
8-46
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Destination:
Call number of the Internal Call Forwarding destination.
Destination:
Call number of the Call Forwarding destination.
Destination:
Call number of the External Call Forwarding destination.
Destination:
Call number of the Internal Call Forwarding destination.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-47
mobile-users.fm
Mobile Users
Delay (sec):
As soon as this time span has expired without the call being accepted, the call is forwarded.
Visual
Check box for activating a visible alert on the forwarding phone.
Forwarding Party:
Select which forwarding party will be displayed when multiple forwarding is active.
Possible options:
Display first
Display last
Favorites
Forwarding 1:
Forwarding 2:
Forwarding 3:
Forwarding 4:
8-48
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Forwarding 5:
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-49
mobile-users.fm
Mobile Users
General Data
8-50
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-51
mobile-users.fm
Mobile Users
General Data
"Passwords" Tab
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
8-52
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
User Password:
Password for access to the workpoints user area.
NOTE: When a mobile user is logged on, User Password stands as Mobility Password (as described
in Section 8.2.1.1, ""Mobile / Basic User" Tab").
When the mobile user logs off, the User Password reverts back to the password of the basic user.
Active
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-53
mobile-users.fm
Mobile Users
Suspended
Disabled
Directory Guard
Directory Screen Password Guard required
This check box activates password protection on the directory screen. To use the screen, you must enter the
standard user password.
8-54
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
WBM Interface
Check box for activating the WBM interface.
Resource Sharing
Check box for activating resource sharing (shared use of mouse and keyboard).
Bluetooth Interface
Check box for activating the Bluetooth interface.
Phone Manager
Check box for activating the Phone Manager.
PC Interface
Check box for activating the interface between the PC and the device.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-55
mobile-users.fm
Mobile Users
8.1.6 Telephony
Call: Main Menu > Mobile Users > SIP Mobile User Configuration > Telephony
This area features the following components:
General Data
"Telephony" Tab
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
8-56
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Emergency Number:
Contains the phone number that can be dialed in an emergency.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-57
mobile-users.fm
Mobile Users
General Data
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
8-58
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-59
mobile-users.fm
Mobile Users
Operator Code(s)
The operator number. You may enter multiple numbers separated by commas.
8-60
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Emergency number(s)
You may enter multiple emergency numbers separated by commas.
Not used
Unchanged
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-61
mobile-users.fm
Mobile Users
Local Code
Digit or short digit string which can be used for dialing a particular prefix, for example.
International Code
Digit string, such as, a prefix, that is dialed at the beginning of the dialing operation using a particular digit.
8-62
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
General Data
"Time" Tab
For information on general interface operation, see Section 5.4.2, "Work Area".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-63
mobile-users.fm
Mobile Users
Date format:
Format for date entry. Manual entry is only necessary if this information is not automatically transmitted (for
example, PBX or DHCP server).
Possible options:
YY-MM-DD
Example: 04-10-05 for 5.10.2004
MM/DD/YY
Example: 10/05/04 for 5.10.2004
DD.MM.YY
Example: 05.10.04 for 5.10.2004
Time Format:
Time format.
Possible options:
12 hour
24 hour
8-64
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
General Data
For information on general interface operation, see Section 5.4.2, "Work Area".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-65
mobile-users.fm
Mobile Users
Music on Hold
If this checkbox is activated, the phone will play music to a caller when he is put on hold.
8-66
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Possible Options:
Prompt
An incoming pickup call is signaled by an alert on the phone GUI. As soon as the user goes off-hook or presses
the speaker key, the pickup call is accepted. Alternatively, the user can press the corresponding function key,
if configured.
Notify
An incoming pickup call is signaled by an alert on the phone GUI. To accept the call, the user must confirm
the alert or press the corresponding function key, if configured.
FPK only
An incoming pickup call is signaled at the corresponding function key only. To accept the call, the user must
press the function key.
Ringer Settings
Ringer Melody:
Possible Options see Section 7.1.12.3, "Ringer Melody:"
Ringer Sequence:
Possible Options:
0.7 sec ON, 0.7 sec OFF, 0.7 sec OFF, 3 sec OFF
Key klick
Volume
Defines the volume of key clicks.
Possible Values:
Off
Low
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-67
mobile-users.fm
Mobile Users
Medium
High
Keys
Defines which keys shall have audible clicks.
Possible Values:
Keypad only
All keys
8-68
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
8.1.10 Applications
Call: Main Menu > Mobile Users > SIP Mobile User Configuration > Applications
This area features the following components:
General Data
"WAP" Tab
"Java" Tab
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-69
mobile-users.fm
Mobile Users
Gateway Address:
IP address or host name of the WAP server.
Port Number:
Port number of the WAP server.
Connection type:
Protocol type for connection to the WAP server.
Possible options:
HTTP
WSP
Homepage:
URL of the welcome page where the WAP homepage is located.
Username
User ID for identification at the WAP server.
Password:
Password for the user ID.
8-70
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Java Midlets
Downloading of Java Midlets allowed
If this check box is activated, you can download Java midlets to the workpoint.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-71
mobile-users.fm
Mobile Users
For information on XML applications, please refer to Section 7.1.14.4, ""XML Applications" Tab"
XML Applications
Application Name (Server):
This name is used internally by the workpoint software to identify the application.
Display Name:
This name is used for listing the application on the workpoint menu.
Program Name:
Path of the start file of the server-side program, relativ to the server address.
8-72
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Server Address:
IP address of the server, on which the program is running.
Example: 192.168.1.150
Server Port:
Port used by the server-side program for receiving data from the workpoint.
Examples: 80 (Apache default port); 8080 (Tomcat default port).
Transport:
Transport protocol used for transmitting XML data.
Possible options:
HTTP
HTTPS
Instance Type:
Selection of the type of instance.
Possible options:
Normal
Xpressions
Phonebook
Icon URL:
URL of the application icon (not yet implemented).
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-73
mobile-users.fm
Mobile Users
Mode Key:
Select a mode key to start the application.
Possible options:
No Mode Key
Number of Tabs:
The number of embedded tabs within the XML application to be shown on phone display.
Value range: 0 ... 3
NOTE: For an XML-application with a number of Tabs > 0, one of the entries between Tab 1 Application Name and Tab 3 Application Name must be set to the same value as the Application Name
(Server) that it is associated with. When the XML application is started, the tab which has the same
name as the XML application is the tab that initially gets focus.
8-74
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Enable Application
Switch to enable application.
Autostart
Switch to enable autostart of application.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-75
mobile-users.fm
Mobile Users
Restart Application
Restart Application, if it is already running.
8-76
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-77
mobile-users.fm
Mobile Users
8.1.11 LDAP
Call: Main Menu > Mobile Users > SIP Mobile User Configuration > LDAP
This area features the following components:
General Data
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination"
IMPORTANT: In order to employ LDAP data (or any other File Deployment contents,e.g
logo,ringtone,screensaver) the mobile user must be logged on.
8-78
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
LDAP Transport:
Transport protocol used to transmit LDAP data.
Possible options:
TCP
TLS
LDAP Authentication:
Option for selecting the LDAP access.
Possible options:
Anonymous
Simple
LDAP User:
User name for authenticated LDAP access.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-79
mobile-users.fm
Mobile Users
LDAP Password:
Password for authenticated LDAP access.
LDAP Digest:
Enter LDAP Digest
10
60
8-80
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
General Data
"Locks" Tab
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-81
mobile-users.fm
Mobile Users
8-82
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
The following functions can be locked for the Mobile User in the configuration menus by activating the relevant
check box:
1-Country options
The user can select a country from a list to adapt the phone to country specific conditions.
2-Language
The user can set the language for the administration and user menu.
3-Date / Time
The user can set the local time, the current date, and the daylight saving time.
4-Call deflection
The user can activate or deactivate call deflection.
5-Call forwarding
The user can activate or deactivate call forwarding.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-83
mobile-users.fm
Mobile Users
7-Call duration
The user can determine whether the call duration is indicated on the display.
Only available in optiPoint workpoints.
8-Call waiting
The user can determine whether a second call is allowed during a connected call. If not, the caller hears the busy
tone.
9-Call transfer
The user can allow call transfer.
10-Transfer call
The user can enable or disable the posibility to interlink an active and a held call.
11-Contrast
The user can set the contrast for the display.
12-Dialing mode
The user can determine whether a number only or, alternatively, a name can be used for dialing.
Only available in optiPoint workpoints.
13-Call display
The user defines which information about the caller is displayed on an incoming call.
Only available in optiPoint workpoints.
8-84
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
14-Daylight Saving
The user can set the daylight saving time.
16-CFNR timer
The user can set the delay time that passes before a call is forwarded, if Call Forwarding on No Reply is activated.
18-Music on hold
The user can determine whether the music on hold stored in the phone is used. If music on hold is activated, it is
played as soon as the phone is put to hold.
20-Message waiting
The user can determine whether new messaes in the mailbox are signaled by a LED.
Only available in optiPoint workpoints.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-85
mobile-users.fm
Mobile Users
22-Conference
The user can allow system based conferences.
Only available in optPoint workpoints.
23-Local conference
The user can allow local 3-party conferences.
32-Auto answer
The user can determine whether incoming calls are accepted automatically by the CTI application which is
connected to the phone.
34-Auto reconnect
The user can determine whether a held call can be reconnected automatically by the CTI application.
38-Inactivity timeout
The user can set the delay time between the last entry and the return to the idle state.
8-86
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
43-Deflect address
The user can enter resp. modify the target number for call deflection.
44-Line settings
The user can modify the settings of a line key.
46-Call park
The user can allow call parking.
47-Call pickup
The user can allow pickup of a parked call.
48-Immediate dialing
The user can allow immediate dialing.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-87
mobile-users.fm
Mobile Users
53-Transfer on Ring
The user can determine whether a call is transferred as soon as the third participants phone rings, even if the
transferring participant has not hung up.
55-Call Recording
The user can activate call recording.
Only available in optiPoint workpoints.
8-88
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
57-Transfer on Hangup
The user can determine whether, when one call is active and another call is on hold, the user can connect these
calls by hanging up.
60-Audio Settings
The user can modify settings like ringtones and room character.
Only available in OpenStage workpoints.
61-Loudspeaker
The user can activate or deactivate handsfree talking.
Only available in OpenStage workpoints.
62-Forwarding Alert
The user can allow forwarding alert.
63-Join in Conference
The user can determine whether visual or acoustical warning notifications indicate an incoming call while call
forwarding is active.
Only available in OpenStage workpoints.
64-Bluetooth
The user can activate or deactivate bluetooth connectivity.
65-Display Skin
The user can choose the display theme.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-89
mobile-users.fm
Mobile Users
66-Screensaver
The user can activate the phoness screensaver and set the delay time for starting the screensaver.
Only available in OpenStage 60/80 workpoints.
68-BLF
The user can define how an incoming call for the phone supervised by the BLF key shall be displayed.
69-Toggle associate
The user can enable or disable the connecting of a first call and a second call by going on-hook. When "Toggle
associate" is activated, the following procedure will ensue: The user has accepted a second call, whereby the first
call is put to hold. As soon as the user has alternated back to the first call, and then again to the second call, he/
she can connect both calling parties by going on-hook.
Available in all OpenStage workpoints.
71- Headset
The user can define the type of headset connected to the phone.
Available for OpenStage 40/60/80 SIP/HFA.
8-90
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
76- Video on
Checkbox for activating the Video Call feature on non-keyset OpenStage phones.
This feature enables the user to make video calls.
Available for OpenStage 60/80 SIP/HFA.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-91
mobile-users.fm
Mobile Users
8-92
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Available for OpenStage 15/20/20E/40/41/60/80 & OpenScape Desk Phones 35 G/ 35 G Eco / 55 G (SIP only).
87- Delete Entry
The user can configure whether to delete calls log entries in case there is a call to an entry in Missed calls list.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-93
mobile-users.fm
Mobile Users
The following functions can be locked for the Mobile User in the configuration menus by activating the relevant
checkbox:
1-Abbreviated dialing
The user can set up abbreviated dialing numbers.
Only available in optiPoint workpoints.
2-User password
The user can change his password.
3-Phone lock
The user can lock the phone. If the phone is locked, no unauthorized person can call from this phone in a regular
manner or modify any settings. Only emergency numbers and pre-defined numbers from the dial plan can be
dialed.
4-Memory
The user can delete all abbreviated dialing numbers and restore the factory settings.
Only available in optiPoint workpoints.
8-94
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
General Data
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-95
mobile-users.fm
Mobile Users
8-96
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-97
mobile-users.fm
Mobile Users
International Mobility ID
If this check box is activated, the device automatically adds the local country code to the extension, in addition to
the trunk number and local area code when a mobile user logs on. The international code is configured under
Mobile Users > SIP Mobile User Configuration > Dialing Properties > "Dialing Properties" Tab ->
International Dial Prefix.
Example: The user logs on to the device using the extension/mobility ID "31434". If the check box is activated, the
device sends the number "498972231434". Otherwise, the device sends the number "8972231434".
8-98
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
8.1.14 Keysets/Keylayout
Call: Main Menu > Mobile Users > SIP Mobile User Configuration > Keysets/Keylayout
This area features the following components:
General Data
"Keysets" Tab
"Destinations" Tab
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-99
mobile-users.fm
Mobile Users
LED on Registration
Check box for activating the display when restarting the IP phone indicating whether the workpoint was registered
successfully.
Only available in SIP workpoints.
Rollover Ring:
Type of alerting when busy.
Possible options:
No ring
Alert Ring
Standard
Alerting
8-100
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Call hold
The original call is put on hold.
Release
The connection to the original call is cleared down (the call is ended).
Reservation Timer:
Time in seconds indicating how long a line reservation can be maintained.
Default: 60 s.
Only available in SIP workpoints.
Forwarding indicated
Check box for activating alerting on a line key when call forwarding is active for its destination.
Only available in SIP workpoints.
Single button
The action associated with the line key is executed as soon as the button is pressed, regardless of whether
or not the handset is in the cradle.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-101
mobile-users.fm
Mobile Users
Preselection
Press the line key to preselect a line. This line is used the next time you seize a line (by lifting the handset,
for example).
Bridging Priority
Possible options:
Show Focus
Check box for activating the display showing which line is currently active (line has the focus).
Only available in SIP workpoints.
No preference
8-102
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
No preference
Forwarding Indication
Checkbox for activating the forwarding indication.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-103
mobile-users.fm
Mobile Users
10
15
20
30
40
50
60
8-104
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Index:
Name of the key layout function.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-105
mobile-users.fm
Mobile Users
Lock Key
Locks the key for the user.
Device:
Specifies the device to which the relevant layout applies.
Possible options:
Base device
Level:
Key level for the Shift functionality.
Possible options:
1. Level
2. Level
3. Level
4. Level
Fixed Keys
Fixed Keys are assigned to a fixed key number. They cannot be deleted or created on the IP Device.
Key number:
Number of the key assigned the relevant function.
If Level "Fixed Keys" is selected, the following key numbers are fixed:
1 Fixed Keys - release
8-106
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Key function:
The following key functions are supported:
Key unused
Selected dialing
Abbreviated dialing
Repeat dialing
Missed calls
Voice messages
Forwarding
Loudspeaker
Mute
Ringer off
Hold
Alternate
Blind Transfer
Deflect
Setup menu
Room echoing
Room muffled
Shift
Notebook
Settings
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-107
mobile-users.fm
Mobile Users
Phone lock
Conference
Local Conference
Headset
Do not disturb
Group pickup
Repertory dial
Line
Feature Toggle
Swap screen
Mobility
Call park
Call pickup
Cancel/Release
Ok Confirm
Callback Request
Cancel Callback
DSS
State Key
Call waiting
Immediate Ring
Preview Key
Call Recording
AICS Zip
Server Feature
Available for free programmable keys as well as for Fixed Keys.
BLF
Start Application
Available for free programmable keys as well as for Fixed Keys.
8-108
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Send URL
Available for free programmable keys as well as for Fixed Keys.
Built-in Forwarding
Only available for Fixed Keys.
Built-in Release
Only available for Fixed Keys.
Built-in Redial
Only available for Fixed Keys.
2nd Alert
Corporate Directory
NOTE: The Corporate Directory function is configured to the V3R3 WP_HI & WP_LO phones.
Key:
Indicates whether this key is a Fixed Keyor a freely programmable key.
Key label:
A key label can be entered here for every function key in the case of Self labeling Keys workpoints (for example,
optiPoint 420 standard).
Only available in SIP workpoints.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-109
mobile-users.fm
Mobile Users
$Q = clear (CL)
$R = consult (CS)
$S = OK
$T = Pause (PA)
Forwarding Type:
Selection of situations when forwarding should be enabled.
Possible options:
on busy
on busy external
on busy internal
on no reply
on no reply external
on no reply internal
unconditionally
unconditionally external
unnconditionally internal
DTMF Sequence
DTMF Sequence for this target.
8-110
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Toggle Text:
Text describing the server function selected with Feature Toggle.
Only available in SIP workpoints.
Application Name:
Name of the application to be started with the function key.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-111
mobile-users.fm
Mobile Users
Protocol
Protocol of Web Server.
Possible options:
HTTP
HTTPS
Port
Port number of web server: If the port is null, the fully qualified URL will not include the port element.
Path
Directory path and name of the program or web page.
Examples: servlet/IppGenericServlet or webpage/checkin.xml
The path should have a slash at the beginning and no slash at the end. If the slash at the beginning is missing, a
slash will be automatically inserted. If there is an additional slash at the end, it will be automatically removed. The
slashes in the path should be forward slashes (/). If backslashes (\) are used instead, the web server may not
find the appropriate program or web page.
Parameters
Null, one, or more parameter-value pairs in the format <parameter>=<value>, with each pair separated by an
ampersand (&), e. g. parameter1=value1¶meter2=value2. A comma (,) is not used as a separator
because it could be part of the key or value. If the key or value contains an ampersand, it must be replaced by
&.
The question mark will be automatically added between the path and the parameters. If there is a question mark
at the beginning of the parameters, it will be automatically stripped off.
HTTP Method
HTTP method to be used.
Possible options:
8-112
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Get
Post
Symbolic Name
Symbolic name.
Push Support
Enables or disables push support.
Key Functionality
Possible options:
Unspecified Call
Unspecified
Address of record:
Only available in SIP workpoints.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-113
mobile-users.fm
Mobile Users
Realm:
Entry of the SIP realm.
Only available in SIP workpoints.
UserID:
Only available in SIP workpoints.
Password:
Only available in SIP workpoints.
Hunt ranking:
Only available in SIP workpoints.
Shared type:
Possible options:
Private
Shared
Unknown
Ring
Only available in SIP workpoints.
Intrusion allowed
Check box for allowing intrusion.
Only available in SIP workpoints.
8-114
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Hotline
Ordinary
Hot Line
Warm Line
Show in Overview
Checkbox for activating the line display in the line overview.
Only available in SIP workpoints.
Position in Overview
Position of key in Line Overview.
Only available in SIP workpoints.
Short Description:
Description of relevant line.
Only available on OpenStage devices.
Line Type:
Possible options:
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-115
mobile-users.fm
Mobile Users
normal
direct
Line Action:
Possible options:
Consult
Transfer
No Action
Ringing Delay:
Time before ringing starts for an alerting call.
8-116
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Please refer also to IP Devices > IP Phone Configuration > LDAP > "CA Certificates" Tab.
Activate certificate
The imported certificate will be activated with the next saving. By activating an empty certificate, the certificate at
the end device will be deleted.
IMPORTANT: This checkbox is an action checkbox and not an indication. This means that it does
not show any current state. That is why it is sometimes grayed out or unchecked.
Index
Certificate index number.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-117
mobile-users.fm
Mobile Users
Imported Certificate
Serial Number:
Serial number of the active or imported certificate (display only).
Owner:
Owner of the active or imported certificate (display only).
Issuer:
Issuer of the active or imported certificate (display only).
Valid from:
Start of validity for the active or imported certificate (display only).
Valid to:
End of validity for the active or imported certificate (display only).
Key Algorithm
Key algorithm.
Key Size
Key size.
Fingerprint (SHA-1):
Test algorithm SHA-1 (160 bits/20 characters) for the security certificate.
8-118
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
NOTE: The value of the imported certificate is updated periodically dependent on the settings in
Administration > Alarm Configuration > "Settings" Tab > Alarm Configuration for Expiring
Certificates > Interval. Therefore it might be greater than the value of the active certificate until the
next update.
Alarm Status:
Current alarm status.
Possible values:
valid
expired
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-119
mobile-users.fm
Mobile Users
General Data
For information on general interface operation, see Section 5.4.2, "Work Area".
8-120
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
UDP
TCP
TLS
SDES Status
Select the SDES status.
Possible options:
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-121
mobile-users.fm
Mobile Users
disabled
enabled
SDP Negotiation
Select the SDP negotiation.
Possible options:
SRTP only
Fallback to RTP
8-122
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
8.1.16 Miscellaneous
Call: Main Menu > Mobile Users > SIP Mobile User Configuration > Miscellaneous
This area features the following components:
General Data
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-123
mobile-users.fm
Mobile Users
Country:
Country where the workpoint is operated.
Possible options:
AF - Afghanistan
AL - Albania
AM - Armenia
AR - Argentina
AT - Austria
AU - Australia
AZ - Azerbaijan
BD - Bangladesh
BE - Belgium
BG - Bulgaria
BO - Bolivia
BR - Brazil
BY - Belarus
CH - Switzerland
CI - Ivory Coast
CL - Chile
CM - Cameroon
CN - China
CO - Columbia
CR - Costa Rica
8-124
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
CR - Serbia
CY - Cyprus
CZ - Czech Republic
DE - Germany
DZ - Algeria
DK - Denmark
EC - Ecuador
EE - Estonia
EG - Egypt
ES - Spain
FI - Finland
FR - France
GB - Great Britain
GE - Georgia
GR - Greece
GT - Guatemala
HN - Honduras
HK - Hong Kong
HR - Croatia
HU - Hungary
ID - Indonesia
IE - Ireland
IL - Israel
IN - India
IR - Iran
IT - Italy
JO - Jordan
JP - Japan
KE - Kenya
KG - Kyrgyzstan
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-125
mobile-users.fm
Mobile Users
KR - Korea
KW - Kuwait
KZ - Kazakhstan
LB - Lebanon
LK - Sri Lanka
LT - Lithuania
LU - Luxembourg
LV - Latvia
MA - Morocco
MD - Moldova
MK - Macedonia
MV - Maldives
MX - Mexico
MY - Malaysia
NA - Namibia
NG - Nigeria
NI - Nicaragua
NL - Netherlands
NO - Norway
NP - Nepal
NZ - New Zealand
OM - Oman
PA - Panama
PE - Peru
PH - Philippines
PK - Pakistan
PL - Poland
PT - Portugal
PY - Paraguay
RO - Romania
8-126
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
RU - Russia
SA - Saudi Arabia
SE - Sweden
SG - Singapore
SI - Slovenia
SK - Slovakia
SV - El Salvador
TH - Thailand
TJ - Tajikistan
TN - Tunisia
TR- Turkey
TM - Turkmenistan
TZ - Tanzania
UA - Ukraine
UY - Uruguay
UZ - Uzbekistan
VE - Venezuela
VN - Vietnam
ZA - South Africa
ZW - Zimbabwe
Language:
Language to be used for local applications.
Possible options:
bg - bulgarian
ca - catalan
cs - czech
da - danish
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-127
mobile-users.fm
Mobile Users
de - german
el - greek
en - english
es - spanish
et - estonian
fi - finnish
fr - french
hr - croatian
hu - hungarian
it - italian
ja - japanese
lv - latvian
mk - macedonian
ms - malayan
nl - dutch
no - norwegian
pl - polish
pt - portuguese
pt_Br - brazilian
ro - romanian
ru - russian
sk - slovak
sl - slovanian
sr - serbian (cyrillic)
sv - swedish
tr - turkish
zh - chinese
8-128
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-129
mobile-users.fm
Mobile Users
8-130
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-131
mobile-users.fm
Mobile Users
Beep on Error
Check box for activating acoustic error signaling during communication with Microsoft RTC.
Only available in SIP workpoints.
8-132
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Display Settings
Display Theme
Defines the layout of the graphical user interface on OpenStage phones.
Possible options:
Silver Blue
Anthracite Orange
0 (no timeout)
10
20
30
60
120
8-133
mobile-users.fm
Mobile Users
NOTE: Valid only for IP Devices with Display Backlight Type = CCFL or Display Backlight Type
= LED, see Section 7.5.1, "Inventory Data".
Possible Options:
1 min
5 min
30 min
60 min
2 hours
3 hours
4 hours
5 hours
6 hours
7 hours
8 hours
Screensaver
Enable Screensaver
This check box enables the screensaver.
10
20
30
60
8-134
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
No auto hide
10
20
30
60
120
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-135
mobile-users.fm
Mobile Users
8-136
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Lock Phone
Locks the phone.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-137
mobile-users.fm
Mobile Users
General Data
"Files" Tab
DLS supports the deployment of files such as LDAP Template, logos, ringtones and screensavers to mobile users
automatically at the time of logon.
For each file deployment configuration the data stored includes all the information needed by DLS in order to make
a file deployment request to a device (such as the file server address, the file name etc) as well as DLS specific
data such as the result of file deployment request (initially empty).
After a mobile user logs on, DLS looks up into the new table in the DB - based on the E164 number of the mobile
user - to see if there is any file deployment configured for this mobile user which has not been successfully
completed already. If there is a pending file deployment (i.e. not already successfully completed in previous
logons), DLS starts a new job to deploy the files and updates the result when file deployment finished in order to
avoid deploying the same file again at the next logon.
NOTE: When a mobile user is deleted, all the configured file deployment data and history data are
deleted as well.
8-138
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
NOTE: LDAP Templates are also deployable to OpenStage 15/20 (SIP only) & OpenScape Desk
Phone IP 35 G / 35 G Eco phones.
File Deployment
SW Image Name:
Name of the Software Image.
File Name:
Name of the file.
File Type:
Usage of the file.
NOTE: For many file types on the FTP server can be used for multiple purposes. In such cases, there
is a table entry for each usage. For instance, a WAV file can be used as a ringtone and as music on
hold. Ringtone and music on hold files must not exceed 1MB in size, while screensaver and logo files
should not be larger than 300kB.
Example: LOGO (OpenStage 40/60/80) , SCREENSAVER (OpenStage 40/60/80).
Server Type:
Protocol used by the server which provides the file.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-139
mobile-users.fm
Mobile Users
Possible values:
FTP
HTTPS
HTTPS URL:
URL of the software image, if a HTTPS server is used.
FTP Server:
ID of the FTP server that provides the file. This is necessary if a FTP server is used.
Action:
Indicates what is to be done with the file.
Possible values:
delete
deploy
Deployment Status:
Status of the deployment action.
Status info:
Information about the status.
Deployment Date:
Date of the latest file deployment.
8-140
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Configuration
Deployment Time:
Time of the latest file deployment.
Deployment Initiator:
Interface over which the deployment has been initiated.
Possible values:
DLS
WBM
Local
NOTE: The data for file deployment (but not the files themselves) are saved in the DLS DB as part
of the mobile user data and deployed to the device with the first 'start-up' after logon.
If the deployment is successful, DLS marks the file(s) as 'successfully deployed' in order not to deploy
the same file again at the next logon. DLS shall support a history of up to 20 deployed files per mobile
user including the date/time of deployment. Once a new file beyond the 20th is deployed, the oldest
deployed file is removed from the list. if file deployment is unsuccessful, another attempt is made at
the next user logon.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-141
mobile-users.fm
Mobile Users
Logon/Logoff
Automatic Logoff
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
8-142
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Interaction
General Data
This part of the contents area is identical for the SIP Mobile User and Logon/Logoff interfaces associated with
this menu. It is used for entering parameters in Search view to find a specific group of workpoints. The base data
associated with the workpoints found is displayed in the Object view (no changes possible).
NOTE: For further information about the Search view, please see Section 5.5, "Search Functionality".
E.164:
Complete E.164 phone number (Mobile Profile).
Example: 498972212345
For information on the meaning of the E.164 station number in relation to mobility, see Section 3.8.3, "Mobility ID".
User Type:
Displays which type of data the remainder of the fields contain.
Possible options:
Mobile User
Mobile User data.
For more information on mobility, see Section 3.8, "DLS Mobility - General Information".
Status:
Displays mobility status.
Possible options:
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-143
mobile-users.fm
Mobile Users
For more information on mobility, see Section 3.8, "DLS Mobility - General Information".
Basic E.164:
E.164-Rufnummer des Mobility -Telefons.
Beispiel: 498972212345
IP Address:
IP address of the workpoint.
Example: 192.117.1.193
The value is read-only if it was dynamically assigned with DHCP.
Device ID:
Physical MAC address of the workpoint.
Example: 00:0E:A6:85:71:80
Device Type:
Workpoint device type.
All workpoint types supported by DLS can be found in Section 3.4, "IP Devices / versions supported".
Remarks:
Fields for general information.
8-144
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Interaction
Clear Window
Deletes the contents of all fields in the Search view. This deletes all previous search criteria so you can enter new
criteria.
Save
Saves the changes.
Discard
Discards any changes made.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-145
mobile-users.fm
Mobile Users
New
Creates a new Mobile User or a default Mobile User.
Migration to Device
Migrate a logged on Mobile User to a Basic User.
Refresh
Refreshes the window contents from the database.
Delete
Delete an object.
8-146
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Interaction
General Data
For information on general interface operation, see Section 5.4.2, "Work Area".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-147
mobile-users.fm
Mobile Users
For information on mobility administration, see Section 16.14, "Configuring and Administrating
Mobility".
8-148
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Interaction
Reapply:
Apply the Mobile User profile to the Mobile User again. On starting this function, the DLS user will be asked
whether this should be done as a merge of the data or by replacing all user data by profile/default data. If the merge
option is chosen (click on "Yes"), those user parameters which are also configured in the profile are overwritten
by the profile data. That user data which is not contained in the profile will not be touched. If, for instance, the
profile contains additional keys, they will be added to the keys currently configured on the mobile users phone;
but in case of concurrent key definitions, the key definitions of the profile will overwrite those currently set on the
phone.
If the replace option (click on "No") is chosen instead of the merge option, those user parameters which are also
configured in the profile are overwritten by the profile data. That user data which is not contained in the profile will
be overwritten with default values.
Home Phone
E.164 number of the Home Phone assigned to this Mobile User.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-149
mobile-users.fm
Mobile Users
Tenant
Name of the tenant the Mobile User belongs to.
8-150
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Interaction
For information on mobility administration, see Section 16.14, "Configuring and Administrating
Mobility".
Archive:
Path for the ZIP archive file from the DLS system.
Archived by:
Name of the DLS user who created the archive.
Archived at:
Indicates the date and time of the archive.
Restored at:
Displays the date and time of the archive restore.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-151
mobile-users.fm
Mobile Users
Ping
The DLS tries to reach the IP Phone or IP Client via ping.
8-152
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Interaction
Logon Scenario
For Mobile User on foreign IP Phone
If activated, response tests are executed for a Mobile User at a foreign IP Phone, that is, at a phone which is not
the Home Phone of this Mobile User.
IP Phone
Last successful Response Test IP Phone
Date of the last successful response test for this IP Phone.
Failed IP Phone
IP Address of the IP Phone that could not be reached.
IP Client
Last successful Response Test IP Client
Date of the last successful response test for this IP Client.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-153
mobile-users.fm
Mobile Users
Failed IP Client
IP address of the IP Client that could not be reached.
8-154
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Interaction
8.2.2 Logon/Logoff
Call: Main Menu > Mobile Users > SIP Mobile User Interaction > Logon/Logoff
This area features the following components:
General Data
"History" Tab
For information on general interface operation, see Section 5.4.2, "Work Area".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-155
mobile-users.fm
Mobile Users
For information on mobility administration, see Section 16.14, "Configuring and Administrating
Mobility".
Device ID
Device ID of the Mobility Phone with which the action logged here has proceeded (display only).
IP Address
IP address of the Mobility Phone with which the action logged here has proceeded (display only).
Action
Type of action that took place (display only).
Possible entries:
Logon
Logoff
8-156
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Interaction
Time Logon/Logoff
Time of the logon, logoff or the failed attempt (display only).
Info
Additional information on the logon, logoff or the failed attempt (display only).
Possible entries:
Internal Error
Forced logoff
Successful Logon
Successful Logoff
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-157
mobile-users.fm
Mobile Users
This function enables the user to schedule a daily automatic logoff of all SIP mobile users for selected locations.
This ensures e.g. that all devices are logged at start of work, and thus are available for SIP mobile users.
NOTE: Automatic Logoff is not allowed for Mobile Users logged on at their Home Phones.
Only when a mobile user is logged on at another device (besides its home phone) will be able to
automatically log it off in order to return back to its home phone and by that ensure it will always be
possible to contact.
NOTE: For affected Mobile Users considered as part of an Automatic Logoff Location, no individual
jobs will be generated under Job Control while Automatic Logoff is executed.
Administrators will need to point under Mobile Users > SIP Mobile User Interaction > Logon/Logoff
User Interface to look for the successful logoff completion state and time.
Logoff at:
Next daily logoff is scheduled on this time. The current time of the timezone defined for this location will be used.
NOTE: Switching from daylight saving time to regular time (one hour back) will not lead to a second
execution of a job that has been started in the time interval hereby doubled. When switching from
regular time to daylight saving time (one hour advance), a job which is scheduled for this skipped time
will not be executed.
8-158
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Interaction
Location
Location where automatic logoff will happen at entered time. Locations are entered as described under Section
6.3.2, "Location".
Multiple Add
Add multiple locations to one logoff time.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-159
mobile-users.fm
Mobile Users
Device Type:
Select the device type for key layout.
Possible options:
OpenStage 15
OpenStage 40
OpenStage 60
OpenStage 80
8-160
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Interaction
Mobility on Key:
Number of the key where Mobility should be programmed.
Value range: 1 ... 19 or none.
Default: 10
Release on Key:
Configure Cancel/Release key on key
Value range: 1 ... 19 or none.
Defaults:
optiPoint 410/420 economy/economy plus/standard: 11
optiPoint 410 advance: 18
optiPoint 420 advance: 17
Shift on Key:
Number of the key where Shift should be programmed.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-161
mobile-users.fm
Mobile Users
8-162
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Interaction
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
Save
Saves any unsaved changes.
Discard
Discards any unsaved changes.
Refresh
Refreshes the content of the relevant page.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-163
mobile-users.fm
Mobile Users
General Data
"Protocol" Tab
8-164
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Interaction
General Data
10
20
30
40
50
60
90
120
240
Default value: 30
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-165
mobile-users.fm
Mobile Users
Discard
Discards any changes made.
Refresh
Refreshes the screen contents from the database.
8-166
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
SIP Mobile User Interaction
Remark
Annotation about the particular protocol entry.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-167
mobile-users.fm
Mobile Users
General Data
"Statistics" Tab
8-168
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
User Data Administration
General Data
This part of the contents area is identical for all interfaces associated with this menu. It is used for entering
parameters in Search view to find a specific group of IP phones. The base data associated with the IP phones
found is displayed in Object view.
E.164:
Complete E.164 phone number (Mobile Profile).
Example: 498972212345
For information on the meaning of the E.164 station number in relation to mobility, see Section 3.8.3, "Mobility ID".
Remarks:
Fields for general information.
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-169
mobile-users.fm
Mobile Users
Mobility Type
Shows the mobility type (SIP or HFA Mobility).
Last Download to
Date:
Date and time of the last sending of user data to the IP Device.
Device ID:
ID of the IP Device to which the user data have been sent.
IP Address:
IP address of the workpoint to which the user data have been sent.
8-170
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
User Data Administration
Device ID:
ID of the IP Device whose user data have been saved.
IP Address:
IP address of the IP Device whose user data have been saved.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-171
mobile-users.fm
Mobile Users
Mobility Statistics
General Data
8-172
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
Mobility Statistics
General Data
This part of the contents area is identical for all interfaces associated with this menu. In Search view, it is used for
entering parameters to find a specific group of statistics. In Object view, the base data associated with the
statistics found is displayed, or the base data for a new statistics are defined.
Statistics:
Name of the statistics.
Begin:
Begin of the time interval in which actions are observed. If Daily Statistics is active, this field is read-only.
End:
End of the time interval in which actions are observed. If Daily Statistics is active, this field is read-only.
Last Update:
Creation date of the statistics currently displayed.
Periods:
Sets the period during the observation time interval. After the expiration of each period, an entry in the table is
created.
Possible Options:
1 min
2 min
3 min
4 min
5 min
10 min
15 min
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-173
mobile-users.fm
Mobile Users
Mobility Statistics
20 min
30 min
1h
2h
3h
4h
6h
24 h
Daily Statistics
The checkbox indicates whether the statistics currently displayed is a Daily Statistics.
8-174
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
Mobility Statistics
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
Delete
Delete the statistics currently displayed.
New
Creates new statistics.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-175
mobile-users.fm
Mobile Users
Mobility Statistics
8-176
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
Mobility Statistics
Update Statistics
If the date of End (of the observation time interval) is later than the date of Last Update, the statistics can be
updated using this button. The button is inactive if the date of Begin and End are in the past.
Display Chart
Via this button, the content of the current statistics is displayed graphically.
Export
Via this button, the content of the current statistics is stored in a file in csv format. The file name will be requested
in a dialog window.
Date/Time:
Time stamp with date and time at the beginning of the observation period. if, f. e., the period is set to 5 min, all
successive values, actions etc. will be determined and entered in the table. At this, they are provided with the
appropriate time stamp.
Actions:
Total number of actions within the period indicated.
Logons:
Number of logons within the period indicated.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-177
mobile-users.fm
Mobile Users
Mobility Statistics
Logoffs:
Number of logons within the period indicated.
Failed:
Number of failed actions within the period indicated.
Max. Users:
Maximum number of mobile users logged on at the same time within the period indicated.
8-178
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
mobile-users.fm
For internal use only
Mobile Users
Mobility Statistics Configuration
1 min
2 min
3 min
4 min
5 min
10 min
15 min
20 min
30 min
1h
2h
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
8-179
mobile-users.fm
Mobile Users
3h
4h
6h
24 h
Discard
Discards previously unsaved modificationes in the configuration.
Refresh
Updates the display of the configuration from the database.
8-180
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
gateway-configuration.fm
For internal use only
Gateways
9 Gateways
Call: Main Menu > Gateways
This menu item consists of the following area:
Gateway Configuration
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
9-1
gateway-configuration.fm
Gateways
Gateway Configuration
General Data
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
9-2
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
gateway-configuration.fm
For internal use only
Gateways
Gateway Configuration
General Data
This part of the contents area only applies to the Gateway Configuration. It is used for entering parameters in
Search view to find a specific group of gateways. The base data associated with the gateways found is displayed
in the Object view (no changes possible).
NOTE: For further information about the Search view, please see Section 5.5, "Search Functionality".
Gateway IP Address:
IP address of the gateway.
Example: 192.117.1.193
Gateway Type:
Type of the gateway.
Possible options:
HG1500
HG3530
HG3540
HG3550
HG3570
HG3575
RG2700
PEN:
Position of the gateway board (slot).
Example: 1-17-3
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
9-3
gateway-configuration.fm
Gateways
Gateway Configuration
SW Version:
Gateway software version. This value is read-only in search results.
Last Update:
Time when the gateway was last updated. This value is read-only in search results.
For information on selecting a time segment for a search, see Section 5.4.2.4, "Time field with calendar button".
Remarks:
Fields for general information.
9-4
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
gateway-configuration.fm
For internal use only
Gateways
Gateway Configuration
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
New
Creates a new gateway.
Save
Saves the changes made to configuration entries.
Discard
Discards any unsaved changes.
Delete
Deletes all selected objects.
Refresh
Refreshes the content of the relevant page.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
9-5
gateway-configuration.fm
Gateways
Gateway Configuration
Direct Access
If this check box is activated, the connection between HiPath 4000/HG 3550 and the DLS is via direct access and
not via the Assistant.
Port:
Proxy port of the gateway.
Protocol:
Protocol used for communicating between the DLS and the gateway.
Possible options:
http
https
Account
User name for accessing the gateway proxy. The user ID is the first part of the URL.
9-6
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
gateway-configuration.fm
For internal use only
Gateways
Gateway Configuration
Password:
Password necessary for accessing the gateway proxy.
SNMP Community:
Community string used for authentication on the SNMP server.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
9-7
gateway-configuration.fm
Gateways
General Data
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
9-8
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
gateway-configuration.fm
For internal use only
Gateways
QoS Data Collection
General Data
This part of the contents area is used for entering parameters in Search view to find a specific group of gateways.
The base data associated with the gateways found is displayed in the Object view (no changes possible except
under Remarks).
NOTE: For further information about the Search view, please see Section 5.5, "Search Functionality".
Gateway IP Address:
IP address of the gateway.
Example: 192.117.1.193
Gateway Type:
Type of the gateway.
Possible options:
HG1500
HG3530
HG3540
HG3550
HG3570
HG3575
RG2700
PEN:
Position of the gateway board (slot).
Example: 1-17-3
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
9-9
gateway-configuration.fm
Gateways
SW Version:
Gateway software version. This value is read-only in search results.
Last Update:
Time when the gateway was last updated. This value is read-only in search results.
For information on selecting a time segment for a search, see Section 5.4.2.4, "Time field with calendar button".
Remarks:
Fields for general information.
9-10
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
gateway-configuration.fm
For internal use only
Gateways
QoS Data Collection
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
Get
Loads a template that has already been saved. For more information, see Section 15.5, "Editing Templates".
Save
Saves configuration entries as a template. For more information, see Section 15.5, "Editing Templates".
Rename
Changes the name of a saved template. For more information, see Section 15.5, "Editing Templates".
Delete
Deletes a saved template. For more information, see Section 15.5, "Editing Templates".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
9-11
gateway-configuration.fm
Gateways
9-12
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
gateway-configuration.fm
For internal use only
Gateways
QoS Data Collection
SNMP Community:
Name of the SNMP community. Matches the value entered in the gateway under Maintenance - SNMP Communities - Trap Communities.
Default: public
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
9-13
gateway-configuration.fm
Gateways
Report Mode:
Possible options:
Off
No report.
Report Interval:
Value range: 0 ... 3600 seconds.
Default: 60 seconds.
Observation Interval:
Value range: 0 ... 3600 seconds.
Default: 10 seconds.
9-14
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
gateway-configuration.fm
For internal use only
Gateways
QoS Data Collection
Default: 20 (= 2 seconds)
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
9-15
gateway-configuration.fm
Gateways
Non-Compressing Codecs
Maximum Lost Packets Threshold:
Maximum number of total packets lost during uncompressed transmission.
Value range: 0 ... 255 (per 1000 packets).
Default: 10
9-16
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
gateway-configuration.fm
For internal use only
Gateways
QoS Data Collection
Compressing Codecs
Maximum Lost Packets Threshold:
Maximum number of total packets lost during compressed transmission.
Value range: 0 ... 255 (per 1000 packets).
Default: 10
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
9-17
gateway-configuration.fm
Gateways
9-18
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
software-deployment.fm
For internal use only
Software Deployment
10 Software Deployment
Call: Main Menu > Software Deployment
This menu consists of the following submenus:
Workpoint Deployment
Manage Rules
The Software Deployment area is used for the user-friendly distribution of software images and other workpoint
software.
NOTE: Note the difference between Software Deployment and File Deployment in the DLS
interface (see Section 10.1.1 and Section 10.1.2).
Software deployment refers to the distribution of workpoint software (IP phones and IP clients).
File deployment, on the other hand, refers to the distribution of any binary or ASCII files that perform
a certain task in the workpoint.
Both functions are combined in the DLS main menu under Software Deployment.
For information on general interface operation, see Section 5.4.2, "Work Area".
NOTE: When distributing software for optiPoint WL2 professional workpoints, ensure that the
workpoints have sufficient battery capacity. If not, it may not be possible to operate the software
successfully.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
10-1
software-deployment.fm
Software Deployment
Workpoint Deployment
General Data
For information on general interface operation, see Section 5.4.2, "Work Area".
If you need this function frequently, you can automate it simply and conveniently with deployment jobs (see
Chapter 14, "Job Coordination").
10-2
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
software-deployment.fm
For internal use only
Software Deployment
Workpoint Deployment
General Data
This part of the contents area is identical for all interfaces associated with this menu. It is used for entering
parameters in Search view to find a specific group of workpoints. The base data associated with the workpoints
found is displayed in Object view (no changes possible except under Remarks).
Device ID:
Physical MAC address of the workpoint.
Example: 00:0E:A6:85:71:80
Device Type:
Workpoint device type.
All workpoint types supported by DLS can be found in Section 3.4, "IP Devices / versions supported".
Examples: optiPoint 410 standard, optiClient 130.
E.164:
Complete E.164 subscriber number (Basic Profile or Mobile Profile).
Example: 498972212345
For information on the meaning of the E.164 station number in relation to mobility, see Section 3.8.3, "Mobility ID".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
10-3
software-deployment.fm
Software Deployment
Workpoint Deployment
Basic E.164:
Complete E.164 phone number (Mobility Phone).
Example: 498972212345
For information on the meaning of the E.164 station number in relation to mobility, see Section 3.8.3, "Mobility ID".
IP Address 2:
Second IP address of the IP phone, if it has an IPv6 address.
Available for OpenStage only.
SW Version:
Software version used by the workpoint.
Example for IP phones and IP clients: 5.0.12.
Information on the difference between the software and license version can be found in Section 15.7, "Distribution
of Workpoint Software".
SW Type:
Software type used by the workpoint.
Examples: Unify HFA, Unify SIP.
Reg-Address:
IP address of the gateway or the gatekeeper where the workpoint must register. In HiPath 3000, this is the IP
address of the HG 1500, in HiPath 4000 it is the HG 3530 or the STMI board.
Last Registration:
Time of last IP phone registration.
For information on selecting a time segment for a search, see Section 5.4.2.4, "Time field with calendar button".
10-4
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
software-deployment.fm
For internal use only
Software Deployment
Workpoint Deployment
Location:
Current location of the IP Device.
Remarks:
Fields for general information.
IP Protocol Mode
Indicates which IP version is used by the phone. If both versions are used, IP address contains the IPv4 address,
and IP address 2 contains the IPv6 address.
Only available for openStage.
Possible options:
IPv4
IPv6
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
10-5
software-deployment.fm
Software Deployment
Workpoint Deployment
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
Deploy
A software or file deployment job is started in the Object and Table views. For more information, see Section 15.7,
"Distribution of Workpoint Software".
10-6
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
software-deployment.fm
For internal use only
Software Deployment
Workpoint Deployment
SW Version:
Software version used by the workpoint.
Example for IP phones and IP clients: 5.0.12
SW Image Path:
Path name of the directories in which the file is saved with the software image.
Examples: /Directory1/Subdirectory2 for IP phone files, \Directory1\Subdirectory2 for IP client files.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
10-7
software-deployment.fm
Software Deployment
Workpoint Deployment
SW Image Name:
File name of the software image.
Examples: vxworks.app, op410std-unify-hfa-V5.0.12-L12345678.app
Deployment Time:
Time when the last software deployment job was started (for a calendar, see Section 5.4.2.4, "Time field with
calendar button").
Deployment Status:
Result (status) of the last software deployment job.
Possible options:
Deployment rejected:
Deployment could not be started. Possible reason: Configuration settings only permit deployment to be
performed when the workpoint is idle; this was not the case.
Deployment initiated:
Deployment was started but is not yet complete.
Deployment finished:
Deployment was successfully completed.
Deployment failed:
An error occurred in the course of deployment.
10-8
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
software-deployment.fm
For internal use only
Software Deployment
Workpoint Deployment
File Path:
Path name of the directory in which the appropriate file type is saved.
Examples: /Directory1/Subdirectory2 for IP phone files, \Directory1\Subdirectory2 for IP client files.
File Name:
Name of the distributed file.
Deployment Time:
Time when the last software deployment job was started (for a calendar, see Section 5.4.2.4, "Time field with
calendar button").
Deployment Status:
The result (status) of the last software deployment job is displayed.
Possible status:
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
10-9
software-deployment.fm
Software Deployment
Workpoint Deployment
Deployment rejected:
Deployment could not be started.
Deployment initiated:
Deployment was started but is not yet complete.
Deployment finished:
Deployment was successfully completed.
Deployment failed:
An error occurred in the course of deployment.
10-10
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
software-deployment.fm
For internal use only
Software Deployment
Workpoint Deployment
SW Image Name:
The file name of the software downloaded.
Installation Date:
Date when the last software was downloaded or installed.
Installation Status:
The status of software installation is displayed here.
Language Package:
Shows the installed language package.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
10-11
software-deployment.fm
Software Deployment
Workpoint Deployment
NOTE: The description provided in Section 10.1.3, ""Software Inventory" Tab" applies to all fields in
this tab.
10-12
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
software-deployment.fm
For internal use only
Software Deployment
Workpoint Deployment
NOTE: The description provided in Section 10.1.3, ""Software Inventory" Tab" applies to all fields in
this tab.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
10-13
software-deployment.fm
Software Deployment
Workpoint Deployment
NOTE: The description provided in Section 10.1.3, ""Software Inventory" Tab" applies to all fields in
this tab.
INCA FW Version:
Version of INCA Firmware.
10-14
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
software-deployment.fm
For internal use only
Software Deployment
Workpoint Deployment
NOTE: The description provided in Section 10.1.3, ""Software Inventory" Tab" applies to all fields in
this tab.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
10-15
software-deployment.fm
Software Deployment
Workpoint Deployment
NOTE: The description provided in Section 10.1.3, ""Software Inventory" Tab" applies to all fields in
this tab.
10-16
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
software-deployment.fm
For internal use only
Software Deployment
Workpoint Deployment
Installation Date:
Date on which the last ringtones were downloaded or installed.
Installation Status:
The status of ringtone installation is displayed here.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
10-17
software-deployment.fm
Software Deployment
Workpoint Deployment
NOTE: The description provided in Section 10.1.3, ""Software Inventory" Tab" applies to all fields in
this tab.
APM FW Version:
Version of APM Firmware.
10-18
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
software-deployment.fm
For internal use only
Software Deployment
Workpoint Deployment
NOTE: The description provided in Section 10.1.3, ""Software Inventory" Tab" applies to all fields in
this tab.
NETBOOT FW Version:
Version of NETBOOT Firmware.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
10-19
software-deployment.fm
Software Deployment
Manage Rules
Device Type:
Device type of the workpoints to which the rule should apply.
Examples: optiPoint 410 standard, optiClient 130.
NOTE: In the case where you want to apply a SW to all devices regardless of the current location
that they are, create a default location with a device type equal to ALL.
However, the devices MUST not conform to any other individual manage rule per location.
SW Type:
Type of software type which is currently installed on the workpoints to which the rule should apply.
Examples: Unify HFA, Unify SIP.
WP SW Version:
Version of the software which is currently installed on the workpoints to which the rule should apply.
Location
Location name (IP range and gatekeeper) to which the deployment rules are assigned.
10-20
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
software-deployment.fm
For internal use only
Software Deployment
Manage Rules
SW Version:
Drop down list containing all available software images respective to Device Type and SW Type as those are
defined.
NOTE: SW Version drop down list returns Software Images located on the FTP server assigned to
the location selected. If no FTP server is assigned to location then an error message "Choice list not
available" will be displayed.
Example for optiPoint and optiClient: 5.0.12.
Change SW Type:
When switch is activated, the workpoint's software type is replaced by the one of the selected software image.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
10-21
software-deployment.fm
Software Deployment
Manage Rules
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
New
Adds a new deployment rule.
Save
Saves the changes. A newly created rule is immediately effective.
Discard
Discards any changes made.
Delete
Deletes an existing deployment rule.
Apply
Starts the automatic software distribution.
10-22
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
element-manager.fm
For internal use only
Element Manager
11 Element Manager
Call: Main Menu > Element Manager
Information on the relevant system types are managed here.
This menu consists of the following submenus:
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
11-1
element-manager.fm
Element Manager
General Data
"Protocol" Tab
11-2
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
element-manager.fm
For internal use only
Element Manager
Element Manager Configuration
General Data
This part of the contents area is used for entering parameters in Search view to find a specific group of Element
Managers. The base data associated with the Element Managers found is displayed in the Object view (no
changes possible except under Remark).
For more information on modifying the configuration, see Section 15.2, "Changing the Element Manager
Configuration and Creating Jobs".
Element Manager ID
Freely preset ID (mandatory). Uniquely identifies the Element Manager that supplies data to the workpoints when
necessary.
2nd EM Address
Hostname or IP address of the 2nd node.
NOTE: This parameter is only relevant for geographically separated OpenScape Voice clusters.
Port
Port used by the Element Manager for communication with the DLS. The following list specifies the ports used by
the individual Element Managers for different protocols:
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
11-3
element-manager.fm
Element Manager
NOTE: This port is locked & cannot be modified / checked as opposed to the rest EM options.
Protocol
Protocol used for exchanging data with the Element Manager.
Possible options:
http
https
E.164 Prefix
Prefix for the E.164 number. Used for workpoints on OpenScape Voice, HiPath 3000/5000, OpenOffice EE, and
HiPath DXWebPro. With Hipath 3000/5000 Version < V7, this is used only for HFA phones. If nothing is entered,
the call number of the workpoint must be unique in the net. In other DLS menus, only the call number has to be
entered for E.164. This field is not used for HiPath 4000; instead, the corresponding values should be entered in
the Virtual Node IDs (HFA) table in the "HiPath 4000 Assistant" tab. If nothing is entered here, the phone number
of the IP phone or IP client must be unique in the network. In other DLS interfaces, you only have to enter the
phone number for E.164 fields.
Example: 4989722 (or no input).
Account
The access code is needed for HiPath 4000 Assistant and for OpenScape Voice Assistant. The "uas_read"
account is needed for HiPath 4000 JDBC Assistant; this must be activated there.
For example, JDBC ID in HiPath 4000.
Password
Password required for Element Manager access. The entry is made by clicking the key icon in a dialog window.
For example, JDBC password in HiPath 4000.
11-4
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
element-manager.fm
For internal use only
Element Manager
Element Manager Configuration
OpenScape Business
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
11-5
element-manager.fm
Element Manager
IMPORTANT: Do not allow the synchronization interval to be set to lower than 60 min.
Although 0 is allowed,during upgrade all Element Managers with synchronization interval < 60 min
must be updated to the new minimum value of 60 minutes.
Remark
Field for general information.
11-6
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
element-manager.fm
For internal use only
Element Manager
Element Manager Configuration
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
New
Creates a new Element Manager configuration.
Save
Saves the Element Manager configuration.
Discard
Discards any changes made and new entries.
Delete
Deletes the Element Manager configuration.
Synchronize
Synchronization transfers registration data from the Element Manager to the DLS database. This operation runs
in the background. A protocol file is created after synchronization, which can take a few minutes. Synchronization
generates or modifies workpoints; it can also result in job generation. These jobs are generated without
consultation.
NOTE: An error message is issued if you try to start a synchronization session on the Element
Manager where a session is already in progress.
NOTE: A new Element Manager synchronization should not be triggered unless the previous one
has completed (regardless of being successful or not).
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
11-7
element-manager.fm
Element Manager
Refresh
Refreshes the contents of the current mask from the database.
11-8
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
element-manager.fm
For internal use only
Element Manager
Element Manager Configuration
NOTE: In order to synchronize with OpenScape Voice,you need to create the necessary appropriate
packet filter rule* to OpenScape Voice for local port 8769 and allow TCP Incoming Connection from
the remote Windows DLS server IP.
* firewall rule via OpenScape Voice Assistant
Compatibility Mode
Checkbox for configuration of the Compatibility Mode. If checked, then the last synch was in compatibility mode.
If unchecked, the last synch was in normal mode.
Last Synchronization
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
11-9
element-manager.fm
Element Manager
Time & date of the last synch. Read only Text with the following format :
YYYY-MM-DDThh:mm
Example: 2011-05-29T19:00
The defaullt value is set to void.
Reset
Clicking this button enables the option to clear/reset the last synchronization field value.
Synchronized Data
Display ID Synchronization
Checkbox for activating the synchronization of the display ID.
Deleted Subscribers
Check Box for activating the deletion of OSV Subscribers. If checked, then devices and line/DSS keys with
Address of Record that corresponds to non-existing (or deleted) OSV subscribers are deleted permanently from
the database.
If unchecked, then devices and line/DSS keys that correspond to non-existing (or deleted) OSV subscribers are
kept in DLS DB.
This box is unchecked by default.
Transport Protocol
Checkbox for configuration of the Transport Protocol. If checked, the Transport Protocol will be set to the same
value as the respective OSV subscriber for all devices that are created / updated during synchronization.
11-10
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
element-manager.fm
For internal use only
Element Manager
Element Manager Configuration
If unchecked, the transport protocol is set to the devices in DLS without taking into account the transport protocol
of the OSV subscribers although it could be set to the DLS device by CMP after a device modification ( that
happens out of the synchronization context ). However it is still taken into account for the proper setting of the SIP
gateway port (if enabled).
This box is unchecked by default.
Feature Codes
Checkbox for configuration of Feature Codes. If checked, Feature Access Codes will be set as configured at the
respective OSV Element Manager attributes for all Devices that are created/updated via synchronization.
If unchecked, Feature Access Codes will not be set.
This box is unchecked by default.
11-11
element-manager.fm
Element Manager
BG Name
Name of the Business Goup.
11-12
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
element-manager.fm
For internal use only
Element Manager
Element Manager Configuration
Branch Name
Name of the Branch.
Get Branches
Starts update of Branches and the tenants will be synchronized. The refresh is performed in the background; the
protocol file is only created at the end. It may take a few minutes to provide this file.
NOTE: When the selected Element Manager Type is OpenScape Voice Assistant ,you wont be able
to run Get Branches.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
11-13
element-manager.fm
Element Manager
IMPORTANT: The OSV Element Manager is enhanced to cover all the functionality offered by the
OSV Assistant EM (synchronization per BG and secure connection).Therefore the OSV Assistant EM
becomes obsolete and given the fact that it does not support Delta synchronization, it is strongly
recommended that any configured OSV Assistant EM in DLS should be replaced with OSV EM(s).
Please refer to Section 15.3, "How to replace OSV Assistant Manager with OSV Element Manager".
Tenants synchronization
When activated, the tenants will be synchronized as well when Update Business Groups is executed.
Display ID synchronization
Checkbox for activating the synchronization of the display ID.
Switches
Switch
Switch name of the administrated switch. The entry is optional. When clicking Update Business Groups, it will
be set by OpenScape Voice Assistant. The switch name is case-sensitive and must match to that one defined
inside the OpenScape Voice Assistant.
11-14
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
element-manager.fm
For internal use only
Element Manager
Element Manager Configuration
Business Groups
Name
Name of Business Group.
Enabled
Only enabled Business Groups will be synchronized.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
11-15
element-manager.fm
Element Manager
NOTE: Synchronization cannot be started while business groups are being refreshed. If you try,
however, an appropriate advisory message appears.
11-16
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
element-manager.fm
For internal use only
Element Manager
Element Manager Configuration
Virtual Node IDs (HFA): E.164 Prfix and Node Access Code are not fetched from Element Manager!
IMPORTANT: After the first synchronization you need to import information on Hi Path 4000
Assistant tab on Virtual Node IDs with valid data exported from HP4K regarding E164 prefix and Node
Access code on each mentioned Virtual Node ID entry that came from first synchronization.
Then, you need to re-synchronize and check the virtual Device entries that are generated.
Virtual Node ID
ID of the virtual node if a HiPath 4000 is distributed across several virtual nodes and different CO accesses are
used within the node. With this solution, you can generate unique E.164 numbers for all nodes by creating different
subscriber phone number/node number combinations. This value is supplied by HiPath 4000.
If entries are not available for either Virtual Node ID or E.164 Prefix, no HFA workpoints are transferred. If entries
are not available for Virtual Node ID, but there is an entry for E.164 Prefix, all HFA workpoints as assigned this
prefix.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
11-17
element-manager.fm
Element Manager
E.164 Prefix
Prefix for the E.164 number. This value is not supplied by HiPath 4000 - it must be configured.
If the table is empty or a virtual node ID is entered without an E.164 prefix, no workpoints are created. If a line
is present containing just one E.164 prefix and no virtual node ID, all HFA workpoints are assigned this prefix
(default prefix). If there are other entries, however, with one virtual node ID and one E.164 prefix each, the
corresponding prefix is used for each one. The default prefix is used for lines for which only the virtual node ID
is set without an assigned E.164 prefix.
If the E.164 prefix is modified and there are workpoint entries for it, then all associated E.164 numbers are
immediately adapted (the E.164 is composed of the extension and the E.164 prefix). Depending on the number
or workpoints, this process can take a few minutes but runs in the background. Synchronization cannot be
performed during this time. If you try, however, an appropriate error message appears.
Gateways (HFA): Gatekeeper ID, Security Time Window, H.235 Security Mode are not fetched from
Element Manager!
Reg-Address:
Host name or the gateway server address. This value is supplied by HiPath 4000.
Gatekeeper ID
Unique gatekeeper ID. This value is not supplied by HiPath 4000, it must be configured manually.
None
No voice encryption.
11-18
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
element-manager.fm
For internal use only
Element Manager
Element Manager Configuration
Reduced
One-way voice encryption (gatekeeper data not sent in encrypted form).
Full
Voice encryption both ways (workpoint and gatekeeper data both sent in encrypted form).
Update
Time of the last PBX or gateway server update.
Remark
Field for general information.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
11-19
element-manager.fm
Element Manager
None
No voice encryption.
Reduced
One-way voice encryption (gatekeeper data not sent in encrypted form).
Full
Voice encryption both ways (workpoint and gatekeeper data both sent in encrypted form).
Gatekeeper ID:
Gatekeeper ID. This value is not supplied by HiPath 3000/5000, it must be configured manually.
11-20
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
element-manager.fm
For internal use only
Element Manager
Element Manager Configuration
Date
Time of synchronization with the Element Manager identified in the Element Manager ID column.
Status
Identification status. This column may contain one of the following values:
OK
Not OK
Cancelled
OK (partially failed)
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
11-21
element-manager.fm
Element Manager
Result
Contents of the protocol file.
NOTE: In the case where no content is shown in the Protocol tab,you should clear the IE cache.
To achieve this,proceed with the following instructions :
1. In the Windows Start Menu,open Start > Settings > Control Panel.
2. Double-click Internet Options.
3. Click on the General Tab.
4. Click the Delete button under the Browsing History section.
5. In the Delete Browsing History click Delete by ensuring that only Temporary Internet files and
Cookies are checked.
6. Click OK,then Close.
7. Relaunch your browser.
11-22
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
element-manager.fm
For internal use only
Element Manager
Element Manager Security
Partial - the certificate (including certificate chain) provided by the remote entity is checked.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
11-23
element-manager.fm
Element Manager
a) the chain of trust for the digital signature provided by the remote entity ends up in one of the (root) CAcertificates, which are preconfigured for that interface on the product
b) all certificates in the chain are not expired (i.e. current date/time is within the certificate's given validity
period)
c) no certificate in the chain is revoked1
Full - the certificate (including certificate chain provided by the remote entity is checked against the same
criteria as in Trusted mode, plus :
a) for correct end entity identity (according to settings in SubjectAlternativeName (SAN) and/or the
common name (CN) in the Subject)
b) for correct use of all critical extensions (e.g. Basic constraints, Key Usage, Extended Key Usage). If
an extension is marked critical and is not recognized, the certificate must be rejected.
c) for correct use of known extensions not marked as critical (e.g. Basic constraints, Key Usage,
Extended Key Usage)
Client Credentials
The Client certificate is the one that is sent to the H8K during SSL handshake.The Client certificate can be issued
by the DLS PKI infrastructure or imported to the DLS( by default a SEN ROOT signed client certificate is installed
with the installation of DLS.)
The Client Certificate should be trusted by the H8K (this means that H8Ks truststore should be configured
properly).
1 Revocation checks are done using OCSP (Online Certificate Status Protocol) or based on CRL (Certificate Revocation Lists); Revocation
checks are controlled via independent configuration items and apply to both Full and Trusted mode. See more details in the section below.
11-24
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
profil-management.fm
For internal use only
Profile Management
12 Profile Management
Call: Main Menu > Profile Management
This menu consists of the following submenus:
Device Profile
Template Overview
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
12-1
profil-management.fm
Profile Management
Device Profile
General Data
"Templates" Tab
"Tenants" Tab
12-2
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
profil-management.fm
For internal use only
Profile Management
Device Profile
General Data
This part of the contents area is used for entering parameters in Search view to find a specific group of profiles,
and for entering parameters which are valid for all tabs. The base data associated with the profiles found is
displayed in the Object view.
Name:
Profile name.
Description:
Brief description of the profile.
Default Profile
If this check box is activated, the profile is also used during Plug & Play registration on new that have not entered
this profile under IP Devices > IP Device Management > IP Device Configuration > "Profile" Tab > Device
Profile. In order to use the default profile during Plug & Play, the following checkbox must be enabled :
The profile can only be used if the location and device type for the profile and the IP device match - unless the
switch Apply Profile to all Devices is active. This profile is also used when registering a IP device for which the
Apply Default Profiles at IP Device Registration check box is activated (IP Devices > IP Device Management
> IP Device Configuration > "General" Tab).
IMPORTANT: As of CV323 onwards, devices/subscribers that do not belong to the Default Location
(as seen under IP Device Configuration > "General" Tab > field: Location), will not be deployed by a
Default Profile belonging to the Default Location.
Only devices that have not met the criteria of other specific Locations and can be considered as leftout from exclusive Location conditions will get the Default Location assignment. Only then and only
for those "left-out" devices (in the context of Location definition) can receive a Default Profile that has
been configured to point to a Default Location.
This negates to the old behavior (CV322 backwards), where a Default Profile pointing to the Default
Location was intended to be deployable to all devices irrespectively of the exclusive Location those
devices could have been assigned.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
12-3
profil-management.fm
Profile Management
Device Profile
To use Location Service IP Infrastructure, a default device profile has to be defined and assigned to the IP
Infrastructure location.
Location
Location where the selected profile should apply as the default profile.
Parent Location
If available, also the templates of the parent locations default profiles are displayed.
Device Family
The profile is valid for the device family specified here.
Possible options:
IP Phone
IP Client
IP Gateway
Clear Window
Deletes the content of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
12-4
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
profil-management.fm
For internal use only
Profile Management
Device Profile
New
Creates a new Device Profile.
Save
Saves any unsaved changes.
Discard
Discards any unsaved changes.
Export Profile
Export the selected Device Profiles to a file in zip format.
Import Profile
Import a Device Profile from a file in zip format.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
12-5
profil-management.fm
Profile Management
Device Profile
Template Name
Name of the selected template.
Multiple Add
Adds multiple templates to one Device Profile.
12-6
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
profil-management.fm
For internal use only
Profile Management
Device Profile
Device Type
IP Device type.
All IP Devices supported by DLS can be found in Section 3.4, "Area of Application".
Examples: optiPoint 410 standard, optiClient 130.
SW Type:
Type of software for the device.
Examples: Unify HFA, Unify SIP.
SW Version
Example for optiPoint and optiClient: 5.0.12.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
12-7
profil-management.fm
Profile Management
Device Profile
Tenant
Name of the tenant.
Remark
Information on the tenant.
12-8
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
profil-management.fm
For internal use only
Profile Management
Device Profile
Parent Profiles
Name of parent locations profiles.
Multiple Add
Add multiple templates to one profile.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
12-9
profil-management.fm
Profile Management
General Data
"Templates" Tab
"Tenants" Tab
12-10
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
profil-management.fm
For internal use only
Profile Management
User Data Profile
General Data
This part of the contents area is used for entering parameters in Search view to find a specific group of profiles,
and for entering a description. The base data associated with the profiles found is displayed in the Object view.
Name:
Profile name. The defined profiles may be eighter used as Mobile User Profile in Mobile Users > SIP Mobile User
Interaction > SIP Mobile User > "Mobile / Basic User" Tab or as Basic Profile in IP Devices > IP Device
Management > IP Device Configuration > "Profile" Tab.
Description:
Brief description of the profile.
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
New
Creates a new User Data Profile.
Save
Saves any unsaved changes.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
12-11
profil-management.fm
Profile Management
Discard
Discards any unsaved changes.
Export Profile
Export selected User Data Profiles into a zip file.
Import Profile
Import User Data Profiles from a zip file.
12-12
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
profil-management.fm
For internal use only
Profile Management
User Data Profile
Template Name
Name of the template.
Multiple Add
Adds multiple templates to one User Data Profile.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
12-13
profil-management.fm
Profile Management
Tenant
Name of the tenant.
Remark
Information on the tenant.
12-14
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
profil-management.fm
For internal use only
Profile Management
Template Overview
export all templates in XML format into a .zip file or import them from a .zip file. Single templates can be
imported from a .zip file as well.
Changes to template attributes and attribute values are not possible here. For more information, see Section 15.5,
"Editing Templates".
IMPORTANT: If data changes are made in configuration forms that have been generated using
templates, these changes are not automatically applied to the templates.
These changes must be manually saved to the template (Section 15.5, "Editing Templates").
This area features the following components:
General Data
"Profiles" Tab
"Tenants" Tab
For information on general interface operation, see Section 5.4.2, "Work Area".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
12-15
profil-management.fm
Profile Management
Template Overview
General Data
This part of the content area is used for entering parameters in Search view to find a specific group of templates,
and for importing and exporting template data. The base data associated with the templates found is displayed in
the Object view (no changes possible).
NOTE: For further information about the Search view, please see Section 5.5, "Search Functionality".
Name:
Name of the template.
Description:
Description of the template.
Object:
Template object type.
Example: IP Phone SNMP Settings
Type:
Specifies the type of parameters stored in the template.
Possible entries:
IP client
IP phone
User Data
12-16
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
profil-management.fm
For internal use only
Profile Management
Template Overview
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
Save
Saves any unsaved changes.
Discard
Discards any unsaved changes.
Delete
Deletes one or more templates (multiple selections possible in table view).
Refresh
Refreshes the content of the relevant page.
Import Template
Import templates in XML format from a zip file. Single templates can be imported from a .zip file as well. They are
selected by name in a popup window.
NOTE: Existing templates with the same name are overwritten during an import.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
12-17
profil-management.fm
Profile Management
Template Overview
Export Template
Export the selected templates in XML format to a .zip file. Multiple template selection is possible in table view. A
pop-up window prompts you to enter the file path.
12-18
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
profil-management.fm
For internal use only
Profile Management
Template Overview
ID
ID for improved sorting (for example, for key assignments).
Attribute Name
Name of the attribute defined in the template.
Attribute Value
Value of the relevant attribute name.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
12-19
profil-management.fm
Profile Management
Template Overview
Device Profiles
Profile
Name of Device Profile.
Description
Description of Device Profile.
Location
Location of Device Profile.
12-20
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
profil-management.fm
For internal use only
Profile Management
Template Overview
Description
Description of User Data Profile.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
12-21
profil-management.fm
Profile Management
Template Overview
Tenant
Name of the tenant.
Remark
Information on the tenant.
12-22
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
xml-applications.fm
For internal use only
XML Applications
13 XML Applications
Call: Main Menu > XML Applications
The DLS can be used not only for installing and configuring XML applications, but also as application server itself.
NOTE: XML applications are available only for OpenStage 60 and OpenStage80 with firmware
versions SIP V1, SIP V2, and HFA V2.
This menu item consists of the following areas:
MakeCall
NewsService
NewsService Archive
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
13-1
xml-applications.fm
XML Applications
General Data
This part of the contents area is identical for the applications MakeCall and NewsService. It is used for entering
parameters in Search view to find a specific group of IP phones for configuring and executing XML applications.
If Object view is selected, the base data associated with the IP phones found is displayed.
IP Address:
IP address of the IP phone. For OpenStage, an IPv4 or IPv6 address is displayed here.
Example: 192.117.1.193
The value is read-only if it was dynamically assigned with DHCP.
Device ID:
ID for unique identification of the IP device. In IP phones, this is generally the MAC address.
Example: 00:0E:A6:85:71:80
Device Type:
IP phone device type. The icon
All IP phone types supported by DLS can be found in Section 3.4, "IP Devices / versions supported".
Example: OpenStage 60
E.164:
Complete E.164 subscriber number (Basic Profile or Mobile Profile).
Example: 498972212345
For information on the meaning of the E.164 station number in relation to mobility, see Section 3.8.3, "Mobility ID".
Basic E.164:
Complete E.164 phone number (Mobility Phone).
13-2
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
xml-applications.fm
For internal use only
XML Applications
Example: 498972212345
For information on the meaning of the E.164 station number in relation to mobility, see Section 3.8.3, "Mobility ID".
SW Version:
Software version of the IP phone.
Example: 5.0.12
Information on the difference between the software and license version can be found in Section 15.7, "Distribution
of Workpoint Software".
SW Type:
IP phone software type.
Examples: Unify HFA, Unify SIP.
Reg-Address
IP address or DNS name of the HFA or SIP server at which the device is registered.
Last Registration:
Time of last IP phone registration.
For information on selecting a time segment for a search, see Section 5.4.2.4, "Time field with calendar button".
Remarks:
Fields for general information.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
13-3
xml-applications.fm
XML Applications
MakeCall
13.1 MakeCall
Call: Main Menu > XML Applications > MakeCall
This mask enables the start (=push) of the XML application MakeCall. This application initiates calls from
selected end devices to a target end device. After this, it is possible to check in the call log whether all calls have
been executed. This check makes sense after a software update, for instance. The application can only be started
from the DLS only, not from the end devices.
To start the function, press the MakeCall action button. Then, a dialog window will request the target call number.
This area features the following components:
General Data
"Info" Tab
13-4
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
xml-applications.fm
For internal use only
XML Applications
MakeCall
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
MakeCall
Pushes the XML application MakeCall. A subsequent dialog window asks the MakeCall Destinationnumber.
Send Text-/Picture-File
Pushes the XML Application NewsService. A subsequent dialog window asks for the name of the Text-/PictureFile.
Delete
Deletes the saved news.
Refresh
Refreshes the window contents from the database.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
13-5
xml-applications.fm
XML Applications
MakeCall
MakeCall Destinationnumber
Displays the destination number for the last automatic call initiated by the XML Application MakeCall.
13-6
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
xml-applications.fm
For internal use only
XML Applications
NewsService
13.2 NewsService
Call: Main Menu > XML Applications > NewsService
This screen enables the start (=push) of the XML application NewsService. This application sends messages to
selected end devices. These can be text or picture files. There is a distinction between an info alert message and
a file message. On an info alert, the message is displayed on the end device along with an INFO symbol, until it
is confirmed by a button press. File messages are displayed on the end device within the application tab
NewsService.
The messages are created and sent by means of the DLS. Stored messages can be read again at the end device.
To send a message, press Send Info Alert or Send Text-/Picture File. Then, a dialog window will ask for the
Header and Text of the message, or for the name of the Text-/Picture-File.
This area features the following components:
General Data
"Info" Tab
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
13-7
xml-applications.fm
XML Applications
NewsService
Text-/Picture File
Name of last Text- (.txt) or Picture-File (.jpg, .bmp, .gif, .png) sent to IP Device by means of XML Application
'NewsService'.
13-8
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
xml-applications.fm
For internal use only
XML Applications
NewsService Archive
General Data
"Info" Tab
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
13-9
xml-applications.fm
XML Applications
NewsService Archive
General Data
NewsService ID
Continuous numbering
NewsServiceType
Type of message.
Possible Values:
Info Alert
Picture File
Text File
Account
Account name of the user who issued the message.
Execution Time
Execution time of the message sending job.
13-10
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
xml-applications.fm
For internal use only
XML Applications
NewsService Archive
Text File
Name of text file sent to IP Device.
Picture File
Name of picture file sent to IP Device.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
13-11
xml-applications.fm
XML Applications
NewsService Archive
IP Address
IP Address of IP Device the news is sent to.
E.164
Complete E.164 subscriber number of IP Device the news is sent to.
13-12
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
job-coordination.fm
For internal use only
Job Coordination
14 Job Coordination
Call: Main Menu > Job Coordination
This menu consists of the following submenus:
Job Control
Daily Status
Job Configuration
More complex deployment tasks are performed in the Job Coordination area. This area is used for configuring,
performing, and logging deployment jobs (see also the operating sequence in Section 15.8).
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
14-1
job-coordination.fm
Job Coordination
Job Control
General Data
This function lets you view a large volume of information on the individual jobs and discard, delete, or reactivate
existing jobs. New jobs are not created here but rather by defining the activities to be performed in the job (for an
example, see Section 15.8, "Using Job Coordination").
For information on general interface operation, see Section 5.4.2, "Work Area".
14-2
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
job-coordination.fm
For internal use only
Job Coordination
Job Control
General Data
This part of the contents area is used for entering parameters in Search view to find a specific group of jobs. The
base data associated with the jobs found is displayed in the Object view.
NOTE: For further information about the Search view, please see Section 5.5, "Search Functionality".
IP Address:
IP address of a IP Device or an address range.
In the case of jobs for IP ranges, 000.000.000.000 is displayed here in the Search view.
Format: 000.000.000.000, 000 = value between 000 and 255.
Device ID:
Device ID of an IP Device or address range.
In the case of jobs for device ID areas, 00:00:00:00:00:00 is displayed here in the Search view.
Format: XX:XX:XX:XX:XX:XX, XX = Hex value between 00 and FF.
Device Type:
IP Device type.
In the case of jobs for different device types, nothing is displayed here in the Search view.
Format: Up to 30 characters.
All IP Devices supported by DLS can be found in Section 3.4, "IP Devices / versions supported".
Example: optiPoint 410 standard, optiClient 130
E.164:
Complete phone number of an IP Device.
In the case of jobs for different phone numbers, nothing is displayed here in the Search view.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
14-3
job-coordination.fm
Job Coordination
Job Control
Format: Up to 15 characters.
See also Section 17.1, "E.164".
Reg-Address
IP address or host name of the registry server where the IP Device is registered.
SW Version:
Software version of an IP device.
In the case of jobs for different version numbers, nothing is displayed here in the Search view.
Example for optiPoint and optiClient: 5.0.12.
SW Type:
Type of Software to be downloaded.
In the case of jobs for different software types, nothing is displayed here in the Search view.
Examples: Unify HFA, Unify SIP.
Action Type:
Possible options:
IP Device Configuration
IP Device Notification
Software Deployment
14-4
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
job-coordination.fm
For internal use only
Job Coordination
Job Control
Netboot Deployment
IP Device Notification
Screensaver Deployment
File Deployment
Scan IP Devices
Reset IP Device
Gateway Configuration
Gateway Probe
File Upload
Action Status:
Possible action status:
expired
A timeout occurred when executing the deployment job because the time entered for Job Configuration was
exceeded, for example, by an IP Device that was unavailable for an extended period of time. The job can be
cancelled and deleted with the result that no more actions are performed for the job.
cancelled
The deployment job was cancelled. In the case of cancelled jobs, only the time of execution is modified (to restart the job at a future time). The job can be deleted.
active
The deployment job was entered in the job table but has not started running because the execution time,
for example, has not yet been reached. The job can be cancelled and deleted with the result that no more
actions are performed for the job.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
14-5
job-coordination.fm
Job Coordination
Job Control
confirmed
The deployment job was accepted by the IP Device and waits until the status of the IP Device permits
processing. The job can be cancelled and deleted with the result that the job execution is no longer interrupted.
failed
The deployment job was started but could not be executed. The job can be cancelled and deleted.
finished
The deployment job was executed correctly. The job can be cancelled and deleted.
running
The deployment job is currently being executed. The job can be cancelled and deleted with the result that the
job execution is no longer interrupted.
waiting
The deployment job is queued, it was entered in the job table but has not started running because the
IP Device is busy.The job status can turn to active if the amount of time that the job has been in waiting status
exceeds a configurable upper limit.
NOTE: The waiting status option is only supported in Openstage V3R3 phones.
Location:
Current location of the IP Device.
Remarks:
Fields for general information, remarks (e.g.comments) for each job.
These fields are editable for all job types and all job statuses.
14-6
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
job-coordination.fm
For internal use only
Job Coordination
Job Control
NOTE: Editable fields under Job Control that reflect values carried over from an initial action (e.g. a
Remark note over a subscriber), are considered editable only in the context of Job parameters and
will not reflect back the changes to the initial record from which the job itself has been originated.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
14-7
job-coordination.fm
Job Coordination
Job Control
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
Save
Saves changes to the existing deployment job. The Save option is only available after a change to an interrupted
job.
Discard
Discards changes to the existing deployment job. The Discard option is only available after a change to an
interrupted job.
Delete
Deletes the deployment job displayed in the Object view.
Cancel Job
Interrupts the deployment job displayed in the Object view.
14-8
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
job-coordination.fm
For internal use only
Job Coordination
Job Control
Activation Time:
Time for the activation of the deployment job (see Section 5.4.2.4, "Time field with calendar button").
Execution Time:
Time for the execution of the deployment job (see Section 5.4.2.4, "Time field with calendar button").
NOTE: Interrupted deployment jobs can be reactivated by entering a future point in time.
For all other job statuses, the time displayed here indicates the time of execution, irrespective of
whether it is in the past or the future.
End Time:
Time for ending the deployment job (see Section 5.4.2.4, "Time field with calendar button").
NOTE: For deployment jobs that were already executed, the time at which these job were ended is
displayed here.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
14-9
job-coordination.fm
Job Coordination
Job Control
Connection Attempts:
Number of retries needed to perform the job (0 means not yet executed).
Execution Attempts:
Number of execution retries needed to perform the job (0 means not yet executed).
Deploy Attempts:
Number of deployment retries needed to perform the job (0 means not yet executed, only for deployment jobs).
Failed Action:
In the job table, this is the number of the action that could not be successfully completed and caused DLS to
automatically generate and execute a Read IP Device Data.
The field only contains one value for jobs of the type Read IP Device Data generated by the DLS. The
administrator is shown as @DLS for these jobs.
Status Info:
Messages can indicate the successful completion of a deployment job as well as to a fault. The following status
messages are output (sorted in alphabetical order based on the Status Info):
Status Info
Description
Trigger
neutral
IP phone
failed
Failed.
IP phone
file-not-found
IP client
IP phone
IP client
initiated
neutral
neutral
invalid data
Invalid data.
IP phone
invalid format
Invalid format.
IP phone
IP phone
invalid Index
Invalid Index.
IP phone
IP phone
internal
14-10
implemented1
ERROR1
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
job-coordination.fm
For internal use only
Job Coordination
Job Control
Status Info
Description
Trigger
IP client
IP client
IP phone
IP phone
neutral
IP phone
IP phone
IP phone
IP phone
not implemented
Not implemented.
IP phone
not readable
Not readable.
IP phone
not supported
Not supported.
IP phone
OK
neutral
read only
Read-only.
IP phone
server-not-contactable
IP client
unknown item
Unknown item.
IP phone
IP phone
nonce not
valid1
1 For internal debugging only; Not relevant for the DLS user.
Job ID:
ID of the jobs. The Job ID is the name that was entered when the job was created (see Section 5.4.2.1, "Toolbar").
If a name was not entered, the action number is used for the job ID.
The job ID for jobs that distribute and activate a PSS (Pre-Shared Secret) are prefixed with PSS.
Action Number:
Action number of the job. This sequential number is automatically generated for every action in every deployment
job (one for each IP address edited).
Administrator:
User names for this job. The name corresponds to the user who defined the action. Enter @DLS as the name for
automatically generated actions.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
14-11
job-coordination.fm
Job Coordination
Job Control
NOTE: This field corresponds to which DLS account has performed an action for which a job has
been created inside DLSs Job Control list.
NOTE: The Administration user @DBUpdateVirtualDevices is an alias for the admin user used for
the Element Manager related scheduled tasks.
IP Scanner:
IP scanner for this job. The name is set when the IP scanner is configured, see Section 7.4.6, "Scan IP Devices".
Mobile User:
Mobile User currently logged on.
DCMP active
If this check box is activated, the device periodically checks for DLS jobs on the DCMP (DLS Contact-Me Proxy).
Poll Interval
Interval (in minutes) between two polls from the device to the DCMP.
14-12
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
job-coordination.fm
For internal use only
Job Coordination
Job Control
Software Deployment
Data for a job may be available in either the "Deployment Data" Tab or the "Configuration Data" Tab.
Repository:
IP address or host name of the FTP server (for IP phones) or network computer (for IP clients) from which the
software is downloaded.
File Path:
Directory on the FTP server (for IP phones) or on the network computer (for IP clients) from which the software is
downloaded. In the case of IP phone software, the path begins with the configured "virtual" root directory. For
IP client software, it begins with the shared network path.
File Name:
The file name of the software downloaded.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
14-13
job-coordination.fm
Job Coordination
Job Control
File Type:
Deployment type of the file downloaded.
Examples:
INCA (INCA firmware deployment)
MIDLET (Java midlet deployment)
LDAP (LDAP template file deployment)
LOGO (Logo file deployment)
RINGTONE (System and ringtone deployment)
APP (Software deployment)
MOH (Hold music file deployment)
Username:
Username ("login") of the FTP access to the server from which the software is downloaded.
Account
Not currently used in DLS.
Password:
Password of the FTP access to the server from which the software is downloaded.
Priority:
Signals whether deployment should pause when a IP Device is busy and wait until it frees up (normal) or if
deployment should be performed at the set time irrespective of the IP Device status (high).
Port:
Port used for the FTP server from which the software is downloaded. Permanently set to port 21.
SW Type:
Software type of the software that is downloaded (for software deployment).
Examples: Unify HFA, Unify SIP.
14-14
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
job-coordination.fm
For internal use only
Job Coordination
Job Control
SW Version:
Software version of the IP Device.
Example for optiPoint: 5.0.12.
License Version:
If the downloaded software requires a license, then this field contains the product version (HLM terminology) used
for registering the software in HiPath License Management (for software deployment).
Example for optiPoint only: 6.0.0
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
14-15
job-coordination.fm
Job Coordination
Job Control
Parameter
Name of the parameter used to perform modifications in this job.
Index
Index within the parameter you want to change (if available).
If a IP Device parameter can accept more values (value list), an index is created for each value. The field remains
empty if there is only one value.
Old Setting
Value of the parameter before the change. Only wildcards are displayed here if the parameter is a password.
New Setting
Value of the parameter after the change. Only wildcards are displayed here if the parameter is a password.
User Data
If this check box is active, user-specific data was sent to the IP device instead of device-specific data (display
only).
14-16
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
job-coordination.fm
For internal use only
Job Coordination
Job Control
Finished
Indicates if the parameter has already been changed.
Status Info
Information on the job status.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
14-17
job-coordination.fm
Job Coordination
Job Control
MakeCall
MakeCall Destinationnumber:
Dialing number of the end device to which an automatic call has been initiated by the XML application 'MakeCall'.
14-18
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
job-coordination.fm
For internal use only
Job Coordination
Daily Status
General Data
This function gives you a clear display of all jobs in a table. Additionally, you may search for Job Status or Job ID.
In addition to the job found according to the requested Job Status, all jobs belonging to the same day will be
displayed. In object view, you can switch between entire table view or individual table entries. The table can be
sorted by Job ID, Job Status, Activation Time, or End Time.
For information on general interface operation, see Section 5.4.2, "Work Area".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
14-19
job-coordination.fm
Job Coordination
Daily Status
General Data
This part of the contents area is used for entering parameters in Search view to find a specific group of jobs. The
data associated with the jobs found is displayed in the Object view.
Activation Date:
Time for the activation of the deployment job (see Section 5.4.2.4, "Time field with calendar button").
Last Update
Date of the last status information update.
Status:
Possible action status:
active
The deployment job was entered in the job table but has not started running because the execution time,
for example, has not yet been reached.
failed
The deployment job was started but could not be executed.
finished
The deployment job was executed correctly.
running
The deployment job is currently being executed.
14-20
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
job-coordination.fm
For internal use only
Job Coordination
Daily Status
Clear Window
Deletes the contents of all fields in this view. Existing entries can therefore be deleted in the Search view before
new search criteria are entered.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
14-21
job-coordination.fm
Job Coordination
Daily Status
Job ID
Job ID (or the action number) of the deployment job.
Job Status
Status of the deployment job.
Activation Time
Time of activation for the deployment job.
End Time
For jobs with the status finished: time of end of execution.
14-22
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
job-coordination.fm
For internal use only
Job Coordination
Job Configuration
General Data
"Gateways" Tab
This function can be used to influence the behavior of a job. Some configuration data can be entered differently
for IP phones and IP clients.
For information on general interface operation, see Section 5.4.2, "Work Area".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
14-23
job-coordination.fm
Job Coordination
Job Configuration
General Data
This part of the contents area is used for entering parameters which are valid for all tabs.
14-24
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
job-coordination.fm
For internal use only
Job Coordination
Job Configuration
Immediately
The job is started immediately.
After registration
The job is started on registration of the device.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
14-25
job-coordination.fm
Job Coordination
Job Configuration
Discard
Discards the changes you made under Job Configuration.
Refresh
Refreshes the content of the relevant page.
14-26
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
job-coordination.fm
For internal use only
Job Coordination
Job Configuration
Connection Request
Number of Retries:
Number of retries permitted before the execution of a job for IP phones should be cancelled after a set number of
automatic retries with the status cancelled.
Value range: 1 - 100
Default: 10
Timeout (sec):
Time in seconds that the DLS waits for an IP phone answer for each attempt if a job is performed.
Value range: 1 - 3600
Default: 60
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
14-27
job-coordination.fm
Job Coordination
Job Configuration
Job Execution
Number of Retries:
Number of retries permitted before the execution of a job for IP phones should be cancelled after a set number of
automatic retries with the status cancelled.
Value range: 1 - 100
Default: 10
Timeout (sec):
Time limit for complete job execution, including all retries.
Value range: 30 - 3600
Default: 300
NOTE: Waiting time is increased every time a job enters the 'Waiting' state and reset on each new
job execution attempt.
NOTE: Waiting time does not count in the job execution timer.
14-28
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
job-coordination.fm
For internal use only
Job Coordination
Job Configuration
Software Deployment
Number of Retries:
Number of retries permitted before the software deployment for IP phones should be cancelled after a set number
of automatic retries with the status cancelled.
Value range: 1 - 100
Default: 10
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
14-29
job-coordination.fm
Job Coordination
Job Configuration
Connection Request
Number of Retries:
Number of retries permitted before the execution of a job for IP phones should be canceled after a set number of
automatic retries with the status cancelled.
Value range: 1 - 100
Default: 10
Timeout (sec):
Time in seconds that the DLS waits for an IP phone answer for each attempt if a job is performed.
Value range: 1 - 3600
Default: 60
Job Execution
Number of Retries:
Number of retries permitted before the execution of a job for IP phones should be canceled after a set number of
automatic retries with the status cancelled.
14-30
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
job-coordination.fm
For internal use only
Job Coordination
Job Configuration
Timeout (sec):
Time limit for complete job execution, including all retries.
Value range: 30 - 3600
Default: 300
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
14-31
job-coordination.fm
Job Coordination
Job Configuration
Connection Request
Number of Retries:
Number of retries permitted before the execution of a job for IP gateways should be canceled after a set number
of automatic retries with the status cancelled.
Value range: 1 - 100
Default: 10
Timeout (sec):
Time in seconds that the DLS waits for an IP gateway answer for each attempt if a job is performed.
Value range: 1 - 3600
Default: 60
Job Execution
Number of Retries:
Number of retries permitted before the execution of a job for IP gateways should be canceled after a set number
of automatic retries with the status cancelled.
14-32
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
job-coordination.fm
For internal use only
Job Coordination
Job Configuration
Timeout (sec):
Time limit for complete job execution, including all retries.
Value range: 30 - 3600
Default: 300
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
14-33
job-coordination.fm
Job Coordination
Job Configuration
Connection Request
Number of Retries:
Number of retries permitted before the execution of a job for gateways should be canceled after a set number of
automatic retries with the status cancelled.
Value range: 1 - 200
Default: 20
Timeout (sec):
Time in seconds that the DLS waits for a gateway answer for each attempt if a job is performed.
Value range: 1 - 3600
Default: 60
Job Execution
Communication between DLS and Gateways:
Possible options:
14-34
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
job-coordination.fm
For internal use only
Job Coordination
Job Configuration
synchronous
The jobs are executed synchronously. The display on the DLS stops responding (the hourglass appears) until
these actions are fully complete. Clicking Refresh always results in the current data record.
asynchronous
The jobs are executed in the background allowing you to continue working in parallel. To see the result, you
must wait a little and then click Refresh. If you refresh too soon, the old data record is returned as a result.
Timeout (sec):
Time limit for complete job execution, including all retries.
Value range: 1 - 3600
Default: 300
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
14-35
job-coordination.fm
Job Coordination
Job Configuration
14-36
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
15 Operating Sequences
This chapter contains the following practical sequences:
Editing Templates
Backup/Restore
For information on general interface operation, see Section 5.4.2, "Work Area".
NOTE: The sequence descriptions provided here are intended as examples. The actual sequence
may vary from the description, depending on the particular DLS configuration, the servers or
IP Devices used, and the ongoing development of the DLS.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-1
bedienablaeufe.fm
Operating Sequences
15-2
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
First Steps: Changing IP Device Parameters
6. Click Table in the view bar to change to List view. Click a column header to sort the entire table according to
the value specified in the header (alternating between ascending and descending).
Click between two column headers and drag the mouse right or left to change the width of the left-hand
column.
Click a column header and drag the mouse right or left to change the order of the columns.
7. Now you can change any fields that have not been dimmed. This is possible in both Object view and Table
view.
8. To transmit the changes to a single IP Device, click Save. This sends the data directly to the IP Device.
NOTE: If you would like to transmit the changes to multiple IP Devices simultaneously, change
to Table view before you save the changes and mark additional IP Device entries in the list (see
Section 5.4.2.4, "Multiple selection and data transfer in Table view" for information on how to do
this).
Click Save. This sends the data directly to the selected IP Devices.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-3
bedienablaeufe.fm
Operating Sequences
1 This parameter is used when preparing to relocate a station to another system. Two data records exist during this operation with the same
E.164 number and different device IDs. One of the data records is assigned to system A, the other to system B. The parameter defined
here ensures that during synchronization between both systems, only the data record belonging to a particular system is updated.
15-4
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
How to replace OSV Assistant Manager with OSV Element Manager
15.3 How to replace OSV Assistant Manager with OSV Element Manager
The OSV Element Manager is enhanced to cover all the functionality offered by the OSV Assistant EM
(synchronization per BG and secure connection).Therefore the OSV Assistant EM becomes obsolete and given
the fact that it does not support Delta synchronization, it is strongly recommended that any configured OSV
Assistant EM in DLS should be replaced with OSV EM(s).
Please refer to the following detailed steps for this procedure:
1. Go to Main Menu > Element Manager > Element Manager Configuration and search for any OSV Assistant
EM entries:
2. Get the Element Manager Address (10.9.102.65 according to the example) and connect to the CMP portal.
Under Configuration > OpenScape Voice > Switches, all the configured OSV switches are displayed:
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-5
bedienablaeufe.fm
Operating Sequences
3. For every OSV switch listed above, create a new Element Manager in DLS as shown below:
By default the protocol is set to http, but it is recommended to be set to https. For the secure mode to work, the
correct information (certificates) should be set in the Element Manager Security mask (see below and also refer
to DLS Admin manual for more information):
15-6
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
How to replace OSV Assistant Manager with OSV Element Manager
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-7
bedienablaeufe.fm
Operating Sequences
4. Before performing any synchronization between DLS and the OSV, the corresponding PFR (packet filter rules)
should be set by the OSV administrator, so that DLS access is granted by OSV (see below):
15-8
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
How to replace OSV Assistant Manager with OSV Element Manager
5. Go back to Main Menu > Element Manager > Element Manager Configuration, fetch the OSV EM that has just
created above and (see also the example below):
a) Press the Update Business Groups button. This will bring all the available BGs of the corresponding
OSV.
b) Select any BG (that needs to be synchronized). This step is optional. If no BG is selected DLS will
synchronize all the subscribers of the switch.
c) Press the Synchronize button, in order to bring the subscribers / devices to DLS. Check the Protocol tab
to verify that the synchronization is successful.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-9
bedienablaeufe.fm
Operating Sequences
A configured FTP server for IP phone software images or a configured Windows network drive for IP client
software (see Section 6.3.4 or Section 6.3.7).
15-10
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
Registering Workpoint Software and Files
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-11
bedienablaeufe.fm
Operating Sequences
15-12
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
Editing Templates
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-13
bedienablaeufe.fm
Operating Sequences
Editing Templates
Enter a meaningful name under Template Name, such as, "QoS Configuration 1". Under Description, enter
a text that explains this template.
6. Click Save.
The name of the current template now appears after Template in the view bar.
You can also save multiple different templates for an area by using different template names.
You can export templates that you have saved (see Section 12.3, "Template Overview").
15-14
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
Editing Templates
Use Profile Management > Template Overview to check which individual attributes are
currently configured.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-15
bedienablaeufe.fm
Operating Sequences
Full Plug&Play
Provision of the workpoint with IP base data and DLS address data using the DHCP server.
Limited Plug&Play
Manual entry of IP base data and DLS address data at the workpoint.
NOTE: We recommend that you use a DHCP server in the DLS environment to :
For more information on how to configure a DHCP server, refer to refer to the Unify Experts Wiki
portal under http://wiki.unify.com/wiki/DHCP_Server_in_a_Windows_environment or Section 4.12.5,
"DHCP Server in a Linux/Unix Environment".
NOTE: Factory Reset with Plug&Play data stored is not possible in Secure Mode. The according IP
Devices must be revert to Default Mode first.
15.6.1 Requirements
Requirements for full Plug&Play
Functional DHCP infrastructure. Depending on the network topology, this consists of at least one DHCP
server and, where applicable, multiple DHCP relay agents.
The IP base data and the DLS address data is entered on the DHCP server so that it can be distributed
automatically to the terminals. For information on configuring the DHCP server, refer to the Unify Experts Wiki
portal under http://wiki.unify.com/wiki/Configuring_the_DHCP_Server_for_DLS ( Windows ) or Section 4.12.5
(Linux/Unix).
This ensures that an IP phone with factory settings receives its initial IP configuration when it is booted.
15-16
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
Workpoint Autoconfiguration (Plug&Play)
Manual storage of the complete IP base data (IP address, subnet mask, default IP gatekeeper, DNS server,
DNS domain suffix, etc.) and DLS address data on the IP phone.
This guarantees Plug&Play operation, albeit in a restricted form, in networks without DHCP infrastructure.
NOTE: For IP clients, full plug&play looks a little bit different.
As IP clients usually run on a host with proper IP configuration, the IP client can be provided with
missing DLS address data either using a "DHCP Inform" or with a "DNS Text Resource Request".
Both ways are considered full plug&play because in contrast to the exclusive use of a DNS with
IP phones, manual configuration is not necessary.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-17
bedienablaeufe.fm
Operating Sequences
As soon as the E.164 is considered free again, the virtual device gets a new Device ID, the Plug&Play active
flag is enabled again and its Plug&Play pool status reset to free. Now the virtual device is available again in
the number pool again. See also chapter Section 6.3.2.6, ""P&P Number Pool" Tab".
15-18
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
Workpoint Autoconfiguration (Plug&Play)
15.6.3 Registration
1. Connect the workpoint(s) (see the workpoint installation or administration manuals). If all requirements for full
Plug&Play are met, the workpoint will receive the DLS address data from DHCP.
The workpoint registers at the DLS with this data.
2. If the DLS can identify the unique Plug&Play data required by the workpoint performing registration, it
automatically sends it to the workpoint.
The DLS basically has three ways to determine Plug&Play data. For more information, see Section 15.6.2.1,
"Assignment Procedure".
3. If configuration templates have been defined (see Section 15.5) and grouped as the standard template, data
from the templates is transferred to the workpoint.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-19
bedienablaeufe.fm
Operating Sequences
4. The Plug&Play sequence is completed when all assigned data has been sent successfully.
15-20
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
Distribution of Workpoint Software
Software deployment refers to the distribution of workpoint software (IP phones and IP clients). In
contrast, file deployment means the distribution of any binary or ASCII files that perform a certain
task in the workpoint.
Both functions are combined in the DLS main menu under Software Deployment.
For automatic deployment, see Section 15.7.2, "Automatic Deployment".
NOTE: A single software deployment operation can take place for each workpoint at the same time
as a file deployment operation, but it is not possible for multiple software deployment operations or
multiple file deployment operations to take place simultaneously.
If you want to update workpoint software using a netboot server, and the update is not possible with a crosslink
cable (crossed LAN cable), the workpoint must be connected to the Netboot server via a hub.
NOTE: When distributing software for optiPoint WL2 professional workpoints, ensure that the
workpoints have sufficient battery capacity. If not, it may not be possible to operate the software
successfully.
Software image properties
A distinction between software images can be made on the basis of the following properties:
Software version (such as, CLA, DHCP, DNS, and FTP servers).5.1.3).
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-21
bedienablaeufe.fm
Operating Sequences
Requirements
The workpoints to be supplied have automatically registered at the DLS or were found by the DLS during a
manual scan (see Section 7.4.6, "Scan IP Devices").
The software to be distributed was either automatically or manually registered at the DLS (see Section 15.4,
"Registering Workpoint Software and Files").
Performing distribution
1. First decide which workpoints you want to provide with the software.
Do this by choosing the Software Deployment > Deploy Workpoints area and, if necessary, enter search
criteria in Search view. Click Search to start the search.
2. If one or more workpoints were found, the first entry is shown in Object view.
To select multiple workpoints, change to Table view and hold down the <CTRL> key to select a number of
individual workpoints or hold down the <SHIFT> key to select workpoint ranges.
3. Click Deploy.
NOTE: When you click Deploy, the system checks whether suitable software is available, that
is, registered, for the selected workpoints.
If this is not the case, an appropriate message is displayed. This is also true if you have selected
both IP clients and different IP phones (optiPoint, OpenStage) in a multiple selection.
15-22
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
Distribution of Workpoint Software
If a software image is not suitable for this workpoint type, the entry is displayed with a yellow triangle and
dimmed. If you hover the mouse pointer over this icon, a ToolTip appears with the reason for this.
For example, the ToolTip "Software not applicable for this device type" states that a specific registered HFA
software package cannot be distributed on Unify HFA workpoints.
IMPORTANT: You can use the check box Derestrict and deploy independent of the device
type to perform software deployment even for a workpoint that does not match the other
workpoints because of the software license information (see Section 15.4.2, "Understanding
License Information for IP Phone Software").
In general, this is only necessary if you want to perform deployment for a new device type
unknown to the DLS.
The result can involve the loss of the entire workpoint functionality.
If this check box is selected, all entries in the list (including ones that were previously dimmed)
are available for selection.
4. Select an Execution Time in the toolbar. To do this, click the calendar symbol
and select one of the time
options and the conditions for the deployment. For more information on the calendar button, see Section
5.4.2.4, "Time field with calendar button".
5. Choose the entry that you want and click Deploy to stipulate the performance time.
6. A dialog window where you can start software distribution appears. By default, the software is set on the basis
of the configured restrictions (see Section 6.3.2.7, ""SW Deployment Restrictions" Tab"). If you activate
Overwrite deployment restrictions, these restrictions are ignored.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-23
bedienablaeufe.fm
Operating Sequences
7. Activating Force deployment if device is busy forces the deployment procedure to be carried out without
delay even if a workpoint is busy (active call). You should only use this option in exceptional cases because it
interrupts a telephone connection on the workpoint.
8. Activating Overwrite deployment restrictions forces deployment regardless of any restrictions that may be
configured.
9. Click OK. If the license check was successful, individual jobs are generated for distribution to the selected
workpoints and carried out at the specified time. A progress bar shows job generation progress (see Section
5.4.2.6, "Message Windows").
For more information on job coordination, see Section 15.8, "Using Job Coordination".
15-24
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
Distribution of Workpoint Software
A working DLS infrastructure (such as CLA, DHCP, DNS and FTP servers).
The workpoints to be supplied have automatically registered at the DLS or were found by the DLS during a
manual scan (see Section 7.4.6, "Scan IP Devices").
The software to be distributed was registered at the DLS (see Section 15.4, "Registering Workpoint Software
and Files").
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-25
bedienablaeufe.fm
Operating Sequences
Repeat the procedure for each rule that you want to set up.
Automatic distribution sequence
Automatic software distribution is always initiated at the workpoint.
When registering a workpoint, the DLS first checks if there is a rule for the workpoint device type. If there is no
rule or if the rule has been deactivated by deselecting Deploy Default Software, no further processing takes
place.
If the distribution of the newest software is activated across the board, the newest software (software with the
highest software version number) is distributed to all workpoints with the same software type. Workpoints with
other software types do not receive new software.
If Deploy newest version is deactivated, each workpoint receives the software entered, without taking the
software type into consideration.
15-26
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
Using Job Coordination
Location
IP Phone Configuration
IP Client Configuration
IP Gateway Configuration
IP Device Interaction
Gateways
Software Deployment
You can assign specific configuration, deployment, and interaction tasks to particular jobs in these areas by
entering a name with Job ID and stipulating the execution time and execution option in the toolbar (see Section
5.4.2.4, "Time field with calendar button").
If a name was defined before the object was saved, this then appears later in Job Control in addition to the action
number. You can group individual actions into jobs to achieve greater clarity by manually entering a Job ID.
NOTE: Switching from daylight saving time to regular time (one hour back) will not lead to a second
execution of a job that has been started in the time interval hereby doubled. When switching from
regular time to daylight saving time (one hour advance), a job which is scheduled for this skipped time
will not be executed.
You can configure properties for executing and logging jobs (see Section 14.3, "Job Configuration").
15-27
bedienablaeufe.fm
Operating Sequences
15-28
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
Backup/Restore
15.9 Backup/Restore
The DLS client interface provides enhanced options for automatically saving DLS data and restoring backups.
The backup file is created with the name DLS_YYYYMMDD_HHMMSS.bak in the directory you selected.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-29
bedienablaeufe.fm
Operating Sequences
Backup/Restore
15-30
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
Backup/Restore
migrate a database backup with a current database definition (combine), see Section 15.9.2.3,
reset the database (delete all database data), see Section 15.9.2.4.
If the database to be restored is older (modified database definition), please perform a migration
instead of a restore (see Section 15.9.2.3, "Migrating DLS Database Data"). A migration should also
be performed if you are not sure if the database backup is still compatible.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-31
bedienablaeufe.fm
Operating Sequences
Backup/Restore
NOTE: There are some basic server configuration data which will never be restored as e.g.
The procedure for restoring a saved database is similar to the one already described for a backup.
1. Close all browser windows connected to the DLS.
2. End DeploymentService on the DLS server. Do this by clicking Programs > Deployment Service > Stop
Service in the Windows Start menu.
3. Restore the the DLS data by executing the following command:
[Installation path]\DeploymentService\Tomcat5\webapps\
DeploymentService\database\dbimport.bat <filename>.zip
4. Start DeploymentService on the DLS server. Do this by clicking Programs > Deployment Service > Start
Service in the Windows Start menu.
15-32
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
Backup/Restore
cd[Installation path]\DeploymentService\Tomcat5\webapps\
DeploymentService\database
dbinstall.bat delete
cd[Installation path]\DeploymentService\Tomcat5\webapps\
DeploymentService\database
5. Start DeploymentService on the DLS server. Do this by clicking Programs > Deployment Service > Start
Service in the Windows Start menu.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-33
bedienablaeufe.fm
Operating Sequences
Backup/Restore
4. Start the service "Deployment service" on the DLS server by clicking on Programs > Deployment Service >
Start Service in the Windows start menu.
15-34
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
Backup/Restore
NOTE: When you initiate a DLS upgrade the installer will automatically create a DLS Restore Point,
thus, deleting any previously taken restore point.
NOTE: In order to improve upgrade speed and lower data duplication, administrators should clear
the DLS trace (or move/maintain outside the DLS path if a copy is required), and also from within
<DLS installation path>\Tomcat5\bin to copy outside any possibly generated heapdumprelated files (heapdump.<data>.<id>.phd, javacore.<data>.<id>.txt, Snap.<data>.<id>.trc).
NOTE: Due to Microsoft SQL Server restrictions,in the case of deployments with active database
mirroring, no restore procedures can be performed.
In such cases,when an upgrade is performed in deployments with remote database ,a popup window
will be displayed at the beginning of the upgrade requesting to either remove the mirroring and retry
(retry), abort (abort) or continue (ignore) without the rollback feature.
At this point if the mirroring is active then the restore procedure cannot be executed.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-35
bedienablaeufe.fm
Operating Sequences
Backup & Restore On OpenScape Voice Integrated and Linux Standalone Installations
15.10.1 Backup
1. Log on at the Common Management Platform. The management platform is reached under
https://<IP of server>
2. Navigate to Operation & Mainentance > "Recovery" Tab. Create an archive for DLS backups, e. g. in /var/
siemens/backup/dls.
15-36
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
Backup & Restore On OpenScape Voice Integrated and Linux Standalone Installations
3. To create a backup, firstly open the folder Backup & Restore and click Backup. In the Backup window, in
the Select archive field, select the newly created archive.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-37
bedienablaeufe.fm
Operating Sequences
Backup & Restore On OpenScape Voice Integrated and Linux Standalone Installations
5. Wait until Status changes from RUNNING to OK (this screen refreshes automatically).
15-38
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
Backup & Restore On OpenScape Voice Integrated and Linux Standalone Installations
15.10.2 Restore
1. To restore a database, firstly open the folder Backup & Restore and click Restore. In the Restore window,
in the Select archive field, select the archive containing the desired backup, and click Next.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-39
bedienablaeufe.fm
Operating Sequences
Backup & Restore On OpenScape Voice Integrated and Linux Standalone Installations
2. Select the desired backup from the list. The backups are identified by a time stamp or optional comment. Click
Next.
15-40
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
Backup & Restore On OpenScape Voice Integrated and Linux Standalone Installations
4. You will be presented with a confirmation window. As this window will not refresh automa-tically, you can close
it any time.
5. To check the state of the restore process, use the Latest Job Status screen.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-41
bedienablaeufe.fm
Operating Sequences
Backup & Restore On OpenScape Voice Integrated and Linux Standalone Installations
15-42
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
Automatic Restore on Upgrade Failure
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-43
bedienablaeufe.fm
Operating Sequences
15-44
icon.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
Importing and Exporting Plug&Play Data
3. Use the Selected Entry view to import mapping data for a Windows PE / WE client.
4. In the Windows Account textbox enter the respective domain / Windows Account of the client.
5. In the E.164 textbox enter the number for this client.
6. In the Import and Export mapping data field press Import. Select the previously edited .csv file.
7. Press Save.
8. In Table view verify that the import was successful.
9. Login to the PE ( OpenScape Desktop Client Personal Edition) / WE (Web Embedded) client with the Windows
Account given by the previous mapping.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-45
bedienablaeufe.fm
Operating Sequences
15-46
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
Importing and Exporting Plug&Play Data
15-47
bedienablaeufe.fm
Operating Sequences
15-48
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
Importing and Exporting Plug&Play Data
2. For setting up a direct station select (DSS) key, 2 steps are required:
1. Set up a primary line
ModifyKey;false;218116230;line;000;0;1;
line-sip-uri=49897223500;line-primary=true;
2. Set up the direct station select key
ModifyKey;false;218116230;dss;000;0;3;line-sip-uri=498972233439
3. To delete a function key, set the key function to "Key Unused". In this example, key #3 is deleted:
ModifyKey;false;218116232;Key Unused;0;0;3
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-49
bedienablaeufe.fm
Operating Sequences
15-50
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
Importing and Exporting Plug&Play Data
15.12.4.10 Parameter Description for Create SIP/HFA Phone, Create SIP/HFA Client,
Create IP Gateway
Unless otherwise stated, it is about parameters in the menu IP Devices> IP Phone Configuration > Gateway/
Server.
Parameter
optional/required
DLS Parameter
Description
Device ID
optional
Device ID
e164 number
required
E.164
optional
Device Type
Software Type
optional
SW Type
Alphanumeric, max. 30
characters.
Table 10
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-51
bedienablaeufe.fm
Operating Sequences
Parameter
optional/required
DLS Parameter
Description
Software Version
optional
SW Version
Alphanumeric, max. 30
characters.
Device Profile
optional
Device Profile
Alphanumeric, max. 30
characters.
Remark
optional
Remark
Basic Profile
optional
optional
Terminal Name
optional
Terminal Name
Display ID
optional
Display ID
Alphanumeric, max. 24
characters
SIP User ID
optional
UserID
SIP Password
optional
Password
Password, max. 25
characters
SIP Realm
optional
SIP Realm
Alphanumeric, max. 93
characters.
optional
Reg-Adr
IP Address, max. 25
characters
optional
Reg-Port
optional
IP Address, alphanumeric,
max. 255 characters
optional
SIP Routing
optional
SIP Routing
optional
IP Address, alphanumeric,
max. 255 characters
optional
Subscriber Number
optional
Registration Subscriber
Number
Gatekeeper
optional
Gatekeeper ID
Table 10
15-52
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
Importing and Exporting Plug&Play Data
Parameter
optional/required
DLS Parameter
Description
Gatekeeper Password
optional
Subscriber Password
Registration Subscriber
Number (Standby)
Gatekeeper (Standby)
optional
Gatekeeper ID (Standby)
Gatekeeper Password
(Standby)
optional
Subscriber Password
(Standby)
Table 10
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-53
bedienablaeufe.fm
Operating Sequences
Parameter
optional/required
DLS Parameter
Description
Device ID
optional
Device ID
e164 number
required
E.164
key function
optional
level
optional
module
optional
Module
key-number
optional
attribute-name
optional
----
name
optional
----
reset
optional
No DLS parameter
15-54
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
Importing and Exporting Plug&Play Data
Parameter
optional/required
DLS Parameter
Description
Device ID
optional
Device ID
e164 number
required
E.164
attribute-name
optional
----
...\DeploymentService\api\doc\v200\dlsapi\
device\index_Device_EN.html
...\DeploymentService\api\doc\v200\dlsapi\
device\index_SIPRegistration_EN.html
...\DeploymentService\api\doc\v200\dlsapi\
device\index_HFARegistration_EN.html
OpenStage 5
OpenStage 15
OpenStage 20
OpenStage 20E
OpenStage 40
OpenStage 60
OpenStage 80
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-55
bedienablaeufe.fm
Operating Sequences
optiPoint 130
AC-Win 2Q IP
AC-Win MQ IP
HG1500
HG3500
HG3575
HOOEE
HOOME V1
HP2K V2.0
Function
Code
Key Unused
000
Selected Dialing
001
Abbreviated Dialing
002
Repeat Dialing
003
Missed Calls
004
Voice Messages
005
Forwarding
006
Loudspeaker
007
Mute
008
Ringer Off
009
Hold
010
Alternate
011
Blind Transfer
012
Join (optiPoint)
013
013
Deflect
014
Table 11
15-56
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
Importing and Exporting Plug&Play Data
Function
Code
Setup Menu
015
Room Echoing
016
Room Muffled
017
Shift
018
Notebook
019
Settings
020
Phone Lock
021
Conference
022
Local Conference
023
Headset
024
Do Not Disturb
025
Group Pickup
029
Repertory Dial
030
Line
031
Feature Toggle
032
033
Swap Screen
041
Mobility
042
Call Park
044
Call Pickup
045
Cancel/Release
046
Ok Confirm
047
Callback Request
048
Cancel Callback
049
consultation transfer
050
DSS
051
State Key
052
053
Immediate Ring
054
Preview Key
055
Call Recording
056
AICS Zip
057
058
BLF
059
start application
060
send url
063
built-in forwarding
064
Table 11
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-57
bedienablaeufe.fm
Operating Sequences
Function
Code
built-in release
065
066
built-in redial
067
start phonebook
068
2nd alert
069
Table 11
Name
DLS Parameter
DLS description
Type
key-destination
Destination
state-key-uri
Feature-URI
line-primary
Primary Line
line-sip-uri
Address of record
E.164 number
line-sip-realm
Realm
Alphanumeric, max. 48
characters
line-sip-user-id
UserID
User ID
Alphanumeric, max. 48
characters
line-sip-pwd
Password
Password
Alphanumeric, max. 48
characters
line-ring
Ring
Ring
line-hunt-sequence
Hunt Ranking
Hunt Ranking
0 ... 10
line-shared-type
Shared type
Shared type
Poss. Values:
Private
Shared
Unknown
feature-toggle-description
Toggle text
feature-toggle-codedescription-unicode
state-key-description-text
Alphanumeric, max. 22
characters
state-key-description-textunicode
Alphanumeric, max. 22
characters
Table 12
15-58
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
Importing and Exporting Plug&Play Data
Name
DLS Parameter
DLS description
Type
key-label
Key Label
key-label-unicode
line-hidden
Show on APM/DSM
line-int-allow
line-hld-active
line-hld
Alphanumeric, max. 60
characters
line-mlo-pos
Number, length 2
line-short-desc
Line Description
Description of Line
Alphanumeric, max. 10
characters
line-hot-line-warm-line
Poss. Values:
Normal
Hot Line
Warm Line
line-ring-delay
Ringing Delay
Number, length: 5
forwarding-type
Forwarding Type
Forwarding Type
Poss. Values:
on busy
on no reply
unconditionally
locked-function-keys
Lock Key
dss-sip-line-type
Line Type
Line Type
Poss. values:
normal
direct
Table 12
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-59
bedienablaeufe.fm
Operating Sequences
Name
DLS Parameter
DLS description
Type
dss-sip-line-action
Line Action
Line Action
Poss. Values:
Consultation
Transfer
No Action
Table 12
Internal name
DLS description
dss-sip-deflect
dss-sip-detect-timer
Number
dss-sip-refuse
line-key-operating-mode
Poss. Values:
Poss. Values:
originating-line-preference
Type
Call hold
Release
Primary line
preference
No preference
line-registration-leds
Registration LEDs
keyset-remote-forward-ind
keyset-reservation-timer
Reservation Timer
Number
Table 13
15-60
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
Importing and Exporting Plug&Play Data
Internal name
DLS description
Type
line-rollover-type
Rollover Type
Poss. Values:
No ring
Alert Ring
Standard
Alerting
line-rollover-volume
terminating-line-preference
Poss. Values:
Ringing line
preference
Ringing line
preference
Ringing line
preference with prime
line preferred
No preference
keyset-use-focus
Show Focus
line-button-mode
Poss. Values:
Single button
Preselection
line-preselection-timer
Number
line-preview-period
Number
shift-key-timeout
Number
stimulus-dtmf-
sequence
DTMF Sequence
DTMF Sequence
blf-audible
blf-popup
fpk-app-name
Application name
Application name
send-url-address
Table 13
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-61
bedienablaeufe.fm
Operating Sequences
Internal name
DLS description
Type
send-url-protocol
Protocol
Protocol
Poss. values:
0: HTTP
1: HTTPS
send-url-port
Port
Number
send-url-path
Path
send-url-query
Parameters
Parameters (e.g.:
Alphanumeric, max. 255
parameter1=value1&par chars
ameter2=value2)
send-url-method
HTTP method
HTTP method
Poss. values:
0: Get
1: Post
send-url-user-id
send-url-passwd
key-functionality
Key functionality
Key functionality
Poss. Values:
0: Toggle call forwarding
1: Unspecified call forwarding
2: Unspecified
Table 13
15-62
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
Copy Macro for P&P and Templates
begin index to end index (optional): only parts of the value are copied. $ represents the last index.
Example: Macro command %e164% copies the whole E.164 number; %e164[1,5]% copies the first 5 digits
of the E.164; %e164[$-4,$]% copies the last 5 digits of the E.164.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-63
bedienablaeufe.fm
Operating Sequences
Field
Item name
E.164
e164
Reg address
reg-addr
reg-number
Gatekeeper ID
reg-id
h235securitymode
System Type
hfa-pbx-type
E.164
e164
Reg address
reg-addr
registration-phone-no
Gatekeeper ID
gatekeeper-id
h235securitymode
Table 14
Field
E.164
Reg address
Registration Subscriber Number
Gatekeeper ID
H.235 Security Mode
Display ID
Display ID (Unicode characters)
Terminal Name
Handset Name
Terminal Hostname
E.164
Table 15
15-64
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
bedienablaeufe.fm
For internal use only
Operating Sequences
Copy Macro for P&P and Templates
Screen
Field
System Type
Reg address
Registration Subscriber Number
Gatekeeper ID
H.235 Security Mode
IP Devices > IP Client Configuration > Gateway / Server > SIP Terminal Name
Connection Tab
IP Devices > IP Phone Configuration > Keyset / Keylayout> " Address of record
Destinations " Tab
UserID
Key label
Key label (Unicode)
Mobile Users> SIP Mobile User Configuration > Keyset /
Keylayout> " Destinations" Tab
Address of record
UserID
Key label
Key label (Unicode)
Table 15
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
15-65
bedienablaeufe.fm
Operating Sequences
15-66
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
16 Administration Scenarios
This chapter contains the following administration scenarios:
Replacing an IP Device
Replacing HFA with SIP Software and Vice Versa with Identical Device IDs
Use Multi-Tenancy
Migration Scenarios
NOTE: The sequence descriptions provided here are intended as examples. The actual sequence
may vary from the description, depending on the particular DLS configuration, the servers or
IP Devices used, and the ongoing development of the DLS.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-1
administrationsszenarien.fm
Administration Scenarios
NOTE: This overload protection mechanism is only meant to support high load situations caused by
HFA devices .The minimum load for HFA devices to work with this mechanism is V2.R0.97.
Proceed with the following steps :
1. Stop DLS Service.
2. Open [InstallationPath]\DeploymentService\Tomcat\conf\server.xml
3. Edit the file as follows:
<!-- DLS - Workpoint Interface, default (bootstrapping) port -->
<Connector port="18443" maxThreads="100" backlog="50000" maxQueueSize="50000"
acceptCount="20000" enableLookups="false" connectionTimeout="150000" maxPostSize="1048576"
redirectPort="-1" scheme="https" SSLEnabled="true" sslProtocol="TLS"
ciphers="TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA,
SSL_RSA_WITH_3DES_EDE_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA,
TLS_DHE_RSA_WITH_AES_256_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA"
clientAuth="false" algorithm="IbmX509"
keystoreType="PKCS12" truststoreType="PKCS12" protocols="TLSv1"
SSLImplementation="de.siemens.icn.hipath.dls.connector.jsse.bsafe.BSAFEJSSE_WPI_Implementation"
/>
16-2
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Overload Protection with HiPath 4000
4. Open [InstallationPath]\DeploymentService\Tomcat\webapps\DeploymentService\WEBINF\filterContext.xml
5. Edit the file as follows :
<bean id="WPIFilter" class="de.siemens.icn.hipath.dls.wpi.v2.servlet.WPIServletFilter">
<property name="enabled" value="true"/>
<property name="maximumThreads" value="600"/>
<property name="wpiEngine">
<ref bean="wpi-engine"/>
</property>
</bean>
6. Start DLS Service.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-3
administrationsszenarien.fm
Administration Scenarios
A HiPath 4000 Assistant with deactivated access block1configured in the DLS (see Section 11.1.3).
Performing reinstallation
1. Configure the stations in the system, for example, with the help of HiPath 4000 Manager or AMOs. For more
information refer to the relevant documentation.
2. Select the Element Manager > Element Manager Configuration > "HiPath 4000 Assistant" Tab area.
3. Click Synchronize. This transmits all data for the stations configured in the system to the DLS.
4. Click the area IP Device Management > IP Device Configuration.
Click Search to find all configured workpoints. The first of the workpoints found is displayed in Object view.
5. Change to Table view and sort the table by E.164.
6. Select the desired, pre-configured virtual device from the table. The device ID generated by the DLS for a
virtual device is prefixed by "@".
7. Enter the Device ID of the workpoint.
8. Click Save.
9. Connect the workpoint.
This completes reinstallation.
1 To deactivate the access block, select Access Management > Password Management > System Password Management
> Password uas_read in the HiPath 4000 Assistant and deactivate the option Block password. Enter the password and save your
changes.
16-4
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Workpoint Reinstallation with HiPath 3000
Performing reinstallation
1. Configure the stations in the system. For more information refer to the relevant documentation.
2. Select the IP Devices > IP Device Management > IP Device Configuration area to create an station, that is,
a virtual device, in the DLS. Instead of a device ID, the virtual device receives a placeholder generated by the
DLS beginning with "@".
3. Enter the E.164 of the new station.
4. Click the Element Manager > Element Manager Configuration > "HiPath 3000/5000" Tab area.
5. Click Synchronize. If the E.164 already exists in one of the configured HiPath 3000/
5000 DB Feature Servers, the relevant gatekeeper address is added to the data record.
6. Enter the device ID of the workpoint in IP Devices > IP Device Management > IP Device Configuration.
7. Click Save.
8. Connect the workpoint.
This completes reinstallation.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-5
administrationsszenarien.fm
Administration Scenarios
HG3550 (for HiPath 4000, connection via the HiPath 4000 Assistant)
Gateway IP Address: IP address of the gateway.
Gateway Proxy IP Address: IP address of the relevant HiPath 4000 Assistant.
Gateway Proxy Port: 443.
Account: Access ID for HiPath 4000 Assistant (as configured on the Assistant). You must use an ID in the
HiPath 4000 Assistant that contains user rights for HG3550Mgr.
For information on creating IDs and assigning rights with this tool, refer to "Access Management" in the
HiPath 4000 Assistant online help.
Password: Password for accessing HiPath 4000 Assistant (configured on HiPath 4000 Assistant as
described above for the account).
HG3530, HG3570, HG3575 (for HiPath 4000, connection via SNMP proxy - an integral part of the DLS
server)
Gateway IP Address: IP address of the gateway.
16-6
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Configuring a Gateway in DLS
SNMP Community: Community string (for authenticating SNMP communication to the gateway). Default
community string: nbcs.
The community string must be set to the same value as the relevant gateway in HiPath 4000 (AMO HFAB:
TYP=SNMP, parameter: CS2).
NOTE: During DLS installation, the SNMP proxy is also installed at the same time and
automatically started as a local service on the DLS server PC. You can stop and start the
SNMP proxy manually on this PC.
To access this service, select: Start > Settings > Control Panel > Administrative Tools
> Services > DeploymentServiceSNMPProxy
6. Click Save to apply the entries.
HG1500: V5.0
HG3550: V2.0
HG3530: V2.0
HG3570: V2.0
HG3575: V2.0
RG2700: V1.0
VoIP Security
HG1500: V6.0
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-7
administrationsszenarien.fm
Administration Scenarios
This internal PKI operates like most other PKIs. It can create its own CA, create certificates signed by this CA,
and even automatically distribute these certificates. On top of this it can also maintain more than one internal PKI
to allow for certificate management of different functions within the phone.
NOTE: Certificate format: PKCS#12 formatted keystore or use of the Deployment Services internal
PKI infrastructure.
Figures 1 and 2 illustrate examples of certificate and PKI hierarchies.
In figure 1 the Deployment Service's public facing interfaces employ a certificate from the customers CA while the
phones certificates are managed by the Deployment Services internal PKI. The Deployment Service can
maintain more than one PKI to manage different phones functions requiring certificates. A single internal PKI can
also be used.
Figure 1
16-8
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Configuring Certificates in DLS
The OpenScape Deployment Service also supports integration with an external Microsoft certificate authority. In
this case the Deployment Service PKI depends on the Microsoft CA to manage and create certificates while the
DLS handles the distribution aspect. Use of the Microsoft CA is not discussed in this document. Instead please
refer to the OpenScape Deployment Service PKI Basic Configuration guide.
Figure 2 shows an example certificate hierarchy using a Microsoft certificate authority. The Deployment Service
uses a single internal PKI to manage both public facing Deployment Service interfaces and all phone functions
requiring certificates.
Figure 2
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-9
administrationsszenarien.fm
Administration Scenarios
16-10
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Configuring Certificates in DLS
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-11
administrationsszenarien.fm
Administration Scenarios
16-12
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Configuring Certificates in DLS
NOTE: A PKI does not need to be created in order to execute this section.
1. Navigate to IP Devices >IP Phone Configuration >Signaling and Payload Encryption (SPE) >"SPE CA
Certificates" Tab.
2. Click on Import Certificate.
3. Check Import certificates to DLS and activate on device (1-step). Select Import using:File.
Click on Browse and locate the file containing the CA certificates.
4. Finally, click OK. The certificate will be imported and a new entry will appear containing the CA certificate
information.
5. You can now enable certificate verification. Please refer to Section 16.5.2.2, "How to Enable SPE Certificate
Verification".
None:
The default option. No checking of the received certificate is performed. The received certificate is only used
to provide an encrypted connection.
Trusted:
The phone checks the expiration date and signature of the received certificate.
Full:
The phone checks the expiration date, signature, and certificate usage fields of the received certificate.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-13
administrationsszenarien.fm
Administration Scenarios
NOTE: All phones defined by this location will receive new WBM certificates. Locations can be
defined under Administration >Server Configuration >Location.
3. Click Import Certificate. Check Import using: PKI. Under Import from PKI select your PKI. Click OK.
4. Under Deploy Date select a date and time to deploy the certificates. Click Save.
16-14
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Configuring Certificates in DLS
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-15
administrationsszenarien.fm
Administration Scenarios
NOTE: If a phone is in secure mode and is unable to communicate with a DLS, it is possible to
manually take the phone out of secure mode. On an OpenStage phone login as admin and
navigate to Admin >Network >Update Service (DLS) >Options and select Default Security.
This will reset the phone it its default security mode. The phone will now be able to communicate
with any Deployment Service. If the phone is to communicate again with the existing
Deployment Service then the Deployment Service must also take the phone out of secure mode.
16-16
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Configuring Certificates in DLS
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-17
administrationsszenarien.fm
Administration Scenarios
Under the "Issuing CAs" Tab you shall see one certificate. Press the Synchronize button (located and offered
under the Plug-in configuration) and a second certificate shall appear under CA (SHA-1).
NOTE: After an upgrade to the DLS version having this patch (or fresh installation) you should
be able to see the two entries under Internal UI mask.
16-18
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Configuring Certificates in DLS
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-19
administrationsszenarien.fm
Administration Scenarios
16-20
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Configuring Certificates in DLS
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-21
administrationsszenarien.fm
Administration Scenarios
16-22
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Configuring Certificates in DLS
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-23
administrationsszenarien.fm
Administration Scenarios
16-24
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Configuring Certificates in DLS
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-25
administrationsszenarien.fm
Administration Scenarios
16-26
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Configuring Certificates in DLS
4. The procedure is complete. This connector can now be used for AutoSPE.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-27
administrationsszenarien.fm
Administration Scenarios
Replacing an IP Device
16-28
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Replacing an IP Device
If the DHCP does not send DLS address data to the workpoint, start the workpoint scan. In the scanning
dialog box, activate Register IP Devices and New IP Devices from Scan Results (see Section 7.4.6,
"Scan IP Devices") to register the new workpoint in the DLS.
If the DLS address data is sent automatically from the DHCP to the workpoint, registration in the DLS is
automatic.
For information on configuring a DHCP server to transfer DLS access data to the workpoints, refer to the
Unify Experts Wiki portal under http://wiki.unify.com/wiki/Configuring_the_DHCP_Server_for_DLS
NOTE: You should not delete the old workpoint data from the DLS database until after the new
workpoint is functioning.
This completes replacement.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-29
administrationsszenarien.fm
Administration Scenarios
A working DLS infrastructure (such as CLA, DHCP, DNS and FTP servers).
16-30
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Replacing HFA with SIP Software and Vice Versa with Identical Device IDs
16.8 Replacing HFA with SIP Software and Vice Versa with Identical Device
IDs
Requirements
A working DLS infrastructure (such as CLA, DHCP, DNS and FTP servers).
We recommend managing configuration data using templates. For more information, see Section 15.5.1,
"Creating a Template Manually".
If necessary, you can also transfer registration data via synchronization with the system. For more information,
see Section 11.1, "Element Manager Configuration".
5. Start software deployment (see Section 15.7.1, "Manual Deployment").
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-31
administrationsszenarien.fm
Administration Scenarios
Replacing HFA with SIP Software and Vice Versa with Identical Device IDs
The workpoint is restarted once the software is loaded to the phone. This completes the software replacement
operation.
16-32
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Configuring an IP Client 130 in the DLS
Procedure
1. Creating Templates
2. Settings at the optiClient 130
Start: the system checks for a new version when starting optiClient 130.
Interval: the system checks for a new version every X minutes based on the value set under Update
Mechanism Interval.
16-33
administrationsszenarien.fm
Administration Scenarios
14. Select Template in the view bar and set the template name.
15. Enter the necessary data here for the main network access, for example, 49 for the local country code.
16. Click Save and define the name for the template, for example, oC130 dialing properties HP4000.
17. Create more templates as needed, for example, if an LDAP server is available, the relevant data is in the
LDAP section.
16-34
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Configuring an IP Client 130 in the DLS
NOTE: For more information on configuring the optiClient 130, refer to the online help or the
optiClient 130 Administration Manual.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-35
administrationsszenarien.fm
Administration Scenarios
16-36
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Changing the IP Address and/or Port Number of the DLS
3. Restart all relevant workpoints (IP Devices > IP Device Interaction > Reset IP Devices).
NOTE: Note that the workpoints will communicate only with the new DLS after a restart. This
means that there is no message indicating whether this action was successfully executed for the
old DLS.
The workpoints register with the new DLS.
4. Deactivate the old DLS (to uninstall the DLS, see Section 4.13, "Uninstalling the Deployment Service").
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-37
administrationsszenarien.fm
Administration Scenarios
An FTP server installed on the TAP. For information on installation, see Section 4.12.1, "FTP Server".
The workpoint software to be deployed must be located on the EWS and registered in the DLS (see Section
6.3.4, "FTP Server Configuration", Section 6.3.5, "HTTPS Server Configuration" or Section 6.3.7, "Network
Drive Configuration").
The EWS must be connected to the customer LAN and assigned a free IP address from the customer LAN.
The IP address can be modified using the IP changer.
Restriction
DHCP can be activated or deactivated at the workpoint (DHCP=ON or DHCP=OFF). However, no DLS info may
be sent from the DHCP to the workpoint. "Vendor Class" must not be configured in the DHCP as described under
http://wiki.unify.com/wiki/Configuring_the_DHCP_Server_for_DLS
If the workpoint has already received the DLS info from the DHCP, this value can only be reset with a Factory
Reset.
16-38
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Using an EWS with DLS in a Customer Network Without Permanent DLS
16.11.2 Manipulating the DLS Database for Using the TAP at Different
Customer Facilities
The database used by the DLS must be modified to facilitate working with multiple databases on the TAP.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-39
administrationsszenarien.fm
Administration Scenarios
16-40
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Operating the DLS via the Program Interface (DlsAPI)
A PHP test script is available for the DLS API. Among other things, this enables you to monitor SOAP
communication, query particular IP phones in the DLS database, and modify configuration parameters for a
selected IP phone. For more information, please refer to the DLS Release Notes.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-41
administrationsszenarien.fm
Administration Scenarios
16-42
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Security: Administering Certificates
This dialog contains the device ID of the IP phone you have selected.
3. In the File name entry field, enter the entire local path including the name of the certificate or click Browse to
enter the path via the browser.
The certificate should be in PKCS#12 format.
4. Enter the key used to encrypt the PKCS#12 file you want to import in the Passphrase field.
5. Activate Import certificate to DLS and activate on device (1-step), if the certificate should be activated
immediately.
6. Click OK to import the certificate.
If you have selected several objects (see Section 5.4.2.4), select Apply to All to import certificates for all of
these objects. The additional question due to security reasons must be answered with Apply to All.
7. For activating the imported certificate, click Activate certificate and Save afterwards, if Import certificate to
DLS and activate on device (1-step) is not activated.
NOTE: Certificates should be deployed to devices when respective template (with PKI Connector
saved) is applied through Plug & Play
NOTE: Certificates won't be deployed to already registered devices even if a template with PKI
Connector saved, is applied.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-43
administrationsszenarien.fm
Administration Scenarios
This dialog contains the device ID of the IP phone you have selected.
4. Select the relevant certificate in the Certificate Type field. The option that corresponds to the tab is already
selected.
5. Activate the check box
Individual certificate files for each selected object to import an individual certificate for every IP phone (for
more information, see step 6).
6. In the File Name entry field (or Directory if the check box in step 5 is activated), enter the entire local path
including the certificate name (without the name if the check box in step 5 is activated) or click Browse to enter
the path via the browser.
NOTE: If you decided to import individual certificated for each IP phone in step 5, these certificates must already be available as follows:
All certificate file names must be based on:
- The device IDs of the telephones or
- The phones E.164 numbers
16-44
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Security: Administering Certificates
7. For phone certificates only: Enter the key used to encrypt the PKCS#12 file you want to import in the
Passphrase field (not necessary for RADIUS certificates).
8. Activate Import certificate to DLS and activate on device (1-step), if the certificate should be activated
immediately.
9. Click OK to import the certificate.
If you have selected several objects (see Section 5.4.2.4), select Apply to All to import certificates for all of
these objects. The additional question due to security reasons must be answered with Apply to All.
10. For activating the imported certificate, click Activate certificate and Save afterwards, when Import
certificate to DLS and activate on device (1-step) is not activated.
NOTE: Certificates should be deployed to devices when respective template (with PKI Connector
saved) is applied through Plug & Play
NOTE: Certificates won't be deployed to already registered devices even if a template with PKI
Connector saved, is applied.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-45
administrationsszenarien.fm
Administration Scenarios
This dialog contains the device ID of the IP phone you have selected.
3. You must enter the according Index, because the CA certificate is indexed.
4. In the File name entry field, enter the entire local path including the name of the certificate or click Browse to
enter the path via the browser.
The certificate should be in .pem format.
5. Enter the key used to encrypt the PKCS#12 file you want to import in the Passphrase field.
6. Click OK to import the certificate.
If you have selected several objects (see Section 5.4.2.4), select Apply to All to import certificates for all of
these objects. The additional question due to security reasons must be answered with Apply to All.
7. For activating the imported certificate. click Activate certificate and Save afterwards.
8. To import a second certificate, proceed as described for the first certificate.
16-46
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Security: Administering Certificates
NOTE: Certificates should be deployed to devices when respective template (with PKI Connector
saved) is applied through Plug & Play
NOTE: Certificates won't be deployed to already registered devices even if a template with PKI
Connector saved, is applied.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-47
administrationsszenarien.fm
Administration Scenarios
This dialog contains the device ID of the IP phone you have selected.
3. In the File Name entry field, enter the entire local path including the name of the certificate or click Browse to
enter the path via the browser.
The certificate should be in .pem format.
4. Activate Import certificate to DLS and activate on device (1-step), if the certificate should be activated
immediately.
5. Click OK to import the certificate.
If you have selected several objects (see Section 5.4.2.4), select Apply to All to import certificates for all of
these objects. The additional question due to security reasons must be answered with Apply to All.
6. For activating the imported certificate, click Activate certificate and Save afterwards, if Import certificate to
DLS and activate on device (1-step) is not activated..
7. To import a second certificate, proceed as described for the first certificate.
NOTE: Certificates should be deployed to devices when respective template (with PKI Connector
saved) is applied through Plug & Play
NOTE: Certificates won't be deployed to already registered devices even if a template with PKI
Connector saved, is applied.
16-48
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Security: Administering Certificates
The PIN must be declared to the IP Gateway board before the registration. This is done by the CLI interface
(activate dls pin <pin>)
4. When pressing the Scan button, the registration including bootstrapping will be executed.
5. Switch to IP Devices > IP Gateway Configuration > Signaling and Payload Encryption (SPE) > "SPE
Certificate" Tab and click on Import Certificate. An import dialog appears:
It is recommended to deploy an individual certificate for each gateway to which the own IP address is
assigned in Owner field (CN). This is absolutely neccessary if Owner check is activated. If DNS is used,
the host name of the gateway may be entered instead of its IP address.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-49
administrationsszenarien.fm
Administration Scenarios
6. Choose whether you want to import a SPE certificate or a SPE CA certificate. For SPE CA certificates, you
must enter the according Index, because this certificate is indexed.
7. In the File name entry field, enter the entire local path including the name of the certificate or click Browse to
enter the path via the browser.
The SPE certificate should be in PKCS#12 format, and the SPE CA certificate should be in .pem format.
8. For SPE certificate only: In the Passphrase field, enter the key used to encrypt the PKCS#12 file you want to
import.
9. Activate Import certificate to DLS and activate on device (1-step), if the certificate should be activated
immediately.
10. Click OK to import the certificate. If you have selected several objects (see Section 5.4.2.4, "Multiple selection
and data transfer in Table view"), select Apply to All to import certificates for all of these objects. The
additional question due to security reasons must be answered with Apply to All.
11. For activating the imported certificate, click Activate certificate and Save afterwards, if Import certificate to
DLS and activate on device (1-step) is not activated.
12. SPE Certificate as well as SPE CA certificate for IP Gateway must be imported.
13. Afterwards, the SPE Certificates for IP Phones / IP Clients must be imported as described in chapter Section
16.13.3, "Importing SPE CA Certificates for IP Phones" / Section 16.13.4, "Importing SPE CA Certificates for
IP Clients".
14. Switch to IP Devices > IP Phone Configuration > Signaling and Payload Encryption (SPE) > "SIP
Settings" Tab or "HFA Settings" Tab and set "TLS" in the entry fields SIP Transport Protocol resp. HFA
Transport Protocol. For IP Clients the values have to be entered the same way.
NOTE: Certificates should be deployed to devices when respective template (with PKI Connector
saved) is applied through Plug & Play
NOTE: Certificates won't be deployed to already registered devices even if a template with PKI
Connector saved, is applied.
16-50
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Security: Administering Certificates
4. For IEEE 802.1x certificates, select the certificate to be removed (if applicable). The option that corresponds
to the tab is already selected.
5. Activate Remove certificate from DLS and device (1-step), if the certificate should be remoced immediately.
6. Click OK to remove the certificate.
If you have selected several objects (see Section 5.4.2.4), select Apply to All to remove certificates for all of
these objects.
7. Click Activate certificate and Save to delete the certificate on the phone, if Remove certificate from DLS
and device (1-step) is not activated.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-51
administrationsszenarien.fm
Administration Scenarios
16-52
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Configuring and Administrating Mobility
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-53
administrationsszenarien.fm
Administration Scenarios
4. In the Name field, enter the name for the new profile. In the Description field, enter a short description of the
profile if required.
5. Click Save to save the profile.
16-54
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Configuring and Administrating Mobility
NOTE: During migration, the user data of the mobility enabled device are used for the creation
of a new mobile user. New E.164 number and new user data are copied to the mobility enabled
device for use when no user is logged on the device.
NOTE: As soon as migration has been completed, the previous basic user is migrated to mobile
user. The default password for new mobile user is "000000" .
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-55
administrationsszenarien.fm
Administration Scenarios
16-56
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Configuring and Administrating Mobility
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-57
administrationsszenarien.fm
Administration Scenarios
4. Phone A is not accepted by the DLS, because it is in Secure Mode, but does not have a valid certificate of this
DLS.
5. Phone A does not have the correct DLS-Address.
6. Phone A is in a phone call (see time before doing a Logoff while a Phone Call is ongoing: Main Menu > Mobile
Users > SIP Mobile User Configuration > SIP Mobility > "Mobility Logon/Logoff" Tab).
16-58
Key
Index
OpenStage 40
OpenStage 40 US
OpenStage
60 / 80
4001
Release icon
Conference icon
Release
icon
Conference icon
Conference icon
4002
Forward icon
Hold icon
Forward
icon
Hold icon
Hold icon
4003
Voice Dial
icon
4009
Redial icon
(Key not
present)
Transfer icon
Transfer icon
4010
(Key not
present)
Forward icon
Transfer icon
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Configuring and Administrating Mobility
Key
OS 40
Index
OS 40 US
OS 60
OS 80
Key icon /
Shift icon /
no imprinted no imprinted
label
label
Key icon /
Key icon /
Forward icon
no imprinted label no imprinted
label
Shift icon
Key icon /
Phonebook icon
no imprinted /
label
no imprinted
label
Key icon /
Key icon /
Pickup icon
no imprinted label no imprinted
label
Key icon /
no imprinted label
Key icon /
Pickup icon /
no imprinted no imprinted
label
label
Key icon /
Key icon /
DND icon
no imprinted label no imprinted
label
Key icon /
no imprinted label
Key icon /
Forward icon /
no imprinted no imprinted
label
label
Key icon /
Key icon /
(Key not present)
no imprinted label no imprinted
label
Key icon /
no imprinted label
DND icon /
Key icon /
no imprinted no imprinted
label
label
Key icon /
no imprinted label
Key icon /
Phone Screen
no imprinted icon /
label
no imprinted
label
Key icon /
Key icon /
(Key not present)
no imprinted label no imprinted
label
Key icon /
no imprinted label
(Key not
present)
Key icon /
no imprinted label
(Key not
present)
Key icon /
no imprinted label
(Key not
present)
Key icon /
(Key not present)
no imprinted
label
Whilst a mobile user is logged on, if DLS receives FPKs / FFKs as part of local changes, DLS shall compare the
received FFKs / FFKs with the default FPKs / FFKs of the phone (for the keys that are not locked) and then, it
shall perform the following handling:
a) If the received key has different key function:
Search the mobile user keys based on the received key index
Otherwise (no configured mobile user key), add a new mobile user key
b) If the received key has the default key function, but different key label:
Search the table with the custom key labels based on the received key function
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-59
administrationsszenarien.fm
Administration Scenarios
Otherwise (no configured custom key label), add a new custom key label for the received key function
c) If the received key has the default key function and label:
Search the mobile user keys based on the received key index and if there is configured mobile user
key, delete it
Search the table with the custom key labels based on the received key function and if there is
configured custom key label, delete it
Otherwise (no configured mobile user key or custom key label), nothing to do
NOTE: In the same manner, the "migrate to mobile user" functionality shall be enhanced to NOT
move the basic user FFKs / FPKs that have the default key functions and labels of the basic user
device type.
16.14.10.1 Preparation
Data backup should normally be performed on a network drive. Only one specific directory should be released for
mobile user data storage. The following steps are required for this:
1. Stop the DeploymentService, that is the DLS Web service. To do this, click Programs > DeploymentService
> Stop Service in the Windows Start menu.
2. As the DeploymentService runs after installation with the localadmin account for which no drives are normally
mapped, it can only access local drives at first. You should therefore assign the DeploymentService an
account which contains privileges for the network drive to be mapped.
IMPORTANT: Make sure that the DeploymentService account has administrator rights. Restrictions can lead to problems with DLS.
To assign a new account to the DeploymentService, select Settings > Administrative Tools > Services or
Settings > Control Panel > Administrative Tools > Services in the Windows Start menu. Double-click the
DeploymentService entry to open a window where you can change the properties of the service. Now
activate the This account check box in the Log On tab and click Browse to select the relevant user account.
16-60
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Configuring and Administrating Mobility
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-61
administrationsszenarien.fm
Administration Scenarios
5. The contents of the drive where the DLS is installed are displayed by default. Mark a directory name and then
click Directory Change or double-click the directory name to select the required destination directory. Click
Directory Up to move to a higher directory level.
6. Enter a file name for the ZIP archive and confirm with Save. Alternatively, you can mark an existing archive in
the list with a simple click and then press Save. In the ensuing selection window, you can choose if you want
to save the mobile user data to the existing archive (Write Data to existing Archive) or overwrite the existing
archive (Create new Archive).
16-62
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Configuring and Administrating Mobility
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-63
administrationsszenarien.fm
Administration Scenarios
3. Mark a .zip archive in the list and click Open. A list of all mobile user data records saved in this archive is
displayed.
4. Mark the data records you want or, where applicable, click Select All. You can also select Reset selection.
Use the Load User Data check box to specify whether or not non-configurable user data, such as, call lists or
phone book data, should be loaded to the DLS database.
NOTE: Call lists and phone book data must be saved in encrypted format.
5. If you click Open now, the selected mobile user data is loaded to the DLS database.
NOTE: It may take some time to load all user data depending on the data volume.
The size of the non-configurable user data can be requested over Mobile Users > User Data Administration
16-64
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Configuring and Administrating Mobility
Required
Required
optional
<Home Phone>
optional
Optional
Table 16
12345;000000;@profile;;;false
33333;000000;@profile;;;false
4411594311111;000000;MobUser;;;false
4411594312334566789;000000;MobUser;;12345;true
Example of data that have to be imported for the creation of Mobile User with SIP registration and KeyStet Data
are as follows:
1.Import of a Virtual device with the needed SIP registration data and Keyset configuration :
##CreateSIPPhone <ID> <e164> <type>...<SIP Server Addr.><SIP Server Port><SIP Reg Addr.><SIP Reg
Port>
CreateSIPPhone
10.7.1.54
5060
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-65
administrationsszenarien.fm
Administration Scenarios
16-66
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Configuring and Administrating Mobility
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-67
administrationsszenarien.fm
Administration Scenarios
Import the configuration from each node into the DLS using "Element Manager" (including the mobile
IP Clients). The mobile IP Clients are virtual devices on the DLS.
In IP Devices > IP Device Management > IP Device Configuration > "General" Tab activate the Use for
HFA Mobility with HiPath 3000 switch for each mobile IP Client in each node.
16-68
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
HFA Mobility with HiPath 3000
The IP Phone will then send a "mobility-configuration-request" message to the DLS. The DLS will then send
the correct registration information that will allow this mobile IP Client to log-on at the correct home node.
3. Deactivate (Mobile user logoff) by entering #9419.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-69
administrationsszenarien.fm
Administration Scenarios
Texts and default pictures are searched under <DLS installation path>/
DeploymentService/Tomcat5/webapps/XMLApplications/data/default
For customization by means of customer texts and pictures, it is possible to create a directory <DLS
installation path>/DeploymentService/Tomcat5/webapps/
XMLApplications/data/custom which will then serve as search path for the texts and pictures.
NOTE: It is recommended to copy the directory
.../XMLApplications/data/default to
.../XMLApplications/data/custom and then make the intended changes there.
Under
.../XMLApplications/data/DeploymentService,
.../XMLApplications/data/LocationService,
.../XMLApplications/data/MakeCall,
.../XMLApplications/data/NewsService
the texts for the respective XML applications are stored. These directories may not be changed by the user.
The directories
.../XMLApplications/data/DeploymentService,
.../XMLApplications/data/LocationService,
.../XMLApplications/data/MakeCall,
.../XMLApplications/data/NewsService
remain unchanged.
16-70
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Data Structures for DLS-hosted XML applications
The directory .../XMLApplications/data/custom is saved and will either be restored or copied to .../
XMLApplications/data/custom_<old Version>, dependent on the setting of Administration >
Backup/Restore > "Restore" Tab > Restore XML Application File too.
NOTE: If customizations have been made, these must be redone. For this, copy
.../XMLApplications/data/default to
.../XMLApplications/data/custom again or rename
.../XMLApplications/data/custom_old to .../XMLApplications/data/custom
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-71
administrationsszenarien.fm
Administration Scenarios
Use Multi-Tenancy
With multi-tenancy masks, it will make a difference whether the object is assigned to a tenant or not, that is, in the
tool bar under Tenant, either the tenants name or <not assigned> will be displayed.
When objects are added which require a license, the tenant specific limits are checked. If a tenant is created or
changed, the license dependent data are checked. The respective alarm thresholds are set tenant specific (see
Section 6.3.1, "Tenants"). Basically, there is a difference between tenant dependent and tenant independent
alarms.
IMPORTANT: The tenancy feature is stored in the database - but this feature is activated during
setup and so it is system dependent and NOT database dependent.
Hence it is possible to restore a DLS database that previously contained tenancy relations to a DLS
installation where the tenancy feature is not installed.
In this rare scenario, if you have installed a system without tenant and restore a tenant database you
will not see any tenants and no-tenant dependent objects afterwards since this feature was never
installed before.
16-72
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Use Multi-Tenancy
16.17.1.3 Uninstalling
Execute an update installation and, at Components, deactivate Multi-Tenancy.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-73
administrationsszenarien.fm
Administration Scenarios
Use Multi-Tenancy
16-74
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Use Multi-Tenancy
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-75
administrationsszenarien.fm
Administration Scenarios
Use Multi-Tenancy
For the location of a tenant, an E.164 pattern should be specified in order to ensure that the call number
configured for the mobile user is valid.
If call number bands are shifted from one tenant to another, the mobile users must be assigned to the new
tenant manually. For this, navigate to Mobile Users > SIP Mobile User Interaction > SIP Mobile User and
enter the tenant in the Tenant field.
16-76
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Migration Scenarios
Upgrade scenarios
From
To
Migration scenarios
Starting with CV422, DLS V7R2 currently supports the following:
From
To
NOTE: Windows DLS Single Node with Local or Remote Data Base is also supported.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-77
administrationsszenarien.fm
Administration Scenarios
Migration Scenarios
16-78
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Migration Scenarios
5. To migrate the DLS data, execute the following command on Command Prompt (run as administrator) for the
first DLS Node :
[Installationpath\DeploymentService\Tomcat\webapps\DeploymentService\database\
migrate.bat filename.zip
6. Start Deployment Service on DLS server for both Nodes by clicking Start > Programs > Deployment
Service > Start Service in the Windows Start menu.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-79
administrationsszenarien.fm
Administration Scenarios
Migration Scenarios
NOTE: When database mirroring is active for a Windows DLS Multi-Node, no migration of backups
is possible.
NOTE: In order to execute the "migrate.bat" command you should run the Command Prompt as
administrator (UAC windows feature).
NOTE: Nearly all data is wiped out on the target DLS installation if present.
Only the following data is conserved when data is migrated on the target load:
- configuration of license server (this is to avoid consuming all licenses on the license server when a
second DLS with same data is started)
- configuration of localized data which needs to be adopted to the current installation, e.g. trace file
directories.
NOTE: Due to enhancement changes in V6R1, from CV111.00 onwards the database representation
of the languages for the batch file, snmp and e-mail alarms has been swapped.
Therefore, in a migration attempt from any DLS (either Linux or Windows) CV110.00 or earlier to a
CV111.00 or later, expect the above mentioned alarm language configuration to be swapped (i.e.
German will be English and English will be German).
An IP adaptation must follow for a successful migration since the newly introduced DLS server will now hold a new
IP address. The procedure is described in the following paragraph:
Phones configured via DHCP: adapt DHCP server, the phones will use the new DLS address after
DHCP lease timed out. Since the lease may never time out, this may be a time-consuming action, it is
therefore recommended to:
16-80
restart all phones (outside business hours) - this will take some time and when all jobs are finished,
check failed jobs and/or search for all phones which are still configured for the old DLS IP address.
Either retry or resolve manually the problem, i.e. in case the phone is switched off.
Phones not configured via DHCP: manually set the new IP address using DLS before the IP is changed
or scan these phones using the new IP address.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Migration Scenarios
Gateways, HiPath 4000 Manager, HiPath 8000 Assistant, HiPath QoS: manual reconfiguration of DLS
address using the individual mechanisms of these products. As an example, reconfigure the DLS
parameters inside CMP to reflect the new IP address of the DLS Server.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-81
administrationsszenarien.fm
Administration Scenarios
Migration Scenarios
All devices, browsers and API clients are configured to use the Cluster IP and not the DLS Node IPs
No administrative tasks are allowed during the time that this procedure lasts. The functionality that is
guaranteed to work with the exception of the outage period, where the service is stopped is mobility
and device registration. Administrative tasks that are automatically triggered should also be disabled
(e.g. Element Manager Synchronization, Plug &Play)
All scheduled jobs must be deleted or cancelled before starting this process
If DCMP is installed on the DLS nodes, each node must have a DCMP instance configured in cluster
mode, as the DLS Admin Guide describes (see Section 4.4.2,Step 3). If the DCMP is on an external
system, it will not be affected.
Have the DLS Admin Guide in handy. All installation and configuration steps below should be done
according to the OpenScape Deployment Service Admin Guide.
For abbreviations and additional information,you can also refer to Section 17.1, "Abbreviations and Technical
Terms"
Prerequisites
16-82
The DLS Common Data folder to be located on an external computer (not in FEx or BEx).
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Migration Scenarios
For Microsoft NLB: NLB is automatically disabled when the DLS service is stopped (already done in
step a). Verify in the NLB Management Console from FE2 that FE1 appears in red and FE2 remains
converged.
For external Load Balancer: Configure the external Load Balancer as appropriate.
NOTE: At this point the DLS Cluster does not support High Availability nor Load Balancing,
however, the DLS service is still available from FE2 and BE2.
3. Installation of Windows Server 2008 R2
a) Installation of Windows Server 2008 R2 + Service Packs on FE1, BE1 and BE3.
b) Network configuration of FE1, BE1 and BE3.
c) Installation of the Microsoft NLB (if an external Load Balancer is used,skip this step).
Install the Microsoft NLB on FE1 by adding it as a feature from the Server Manager.
16-83
administrationsszenarien.fm
Administration Scenarios
Migration Scenarios
The Common DLS Data folder is recommended to be located on BE3 or on an external computer and
certainly NOT in the computer where CLA is installed.
Use the exact same configuration as the old system. If DCMP was installed, install DCMP on this new
system as well.
Do NOT install a hotfix directly. Instead first install the base version of the hotfix and then upgrade to
the hotfix (e.g. the base version of V6 R1 127.05 is the V6 R1 127.00).
For Microsoft NLB: NLB is automatically disabled when the DLS service is stopped (already done in
step b).
For external Load Balancer: Configure the external Load Balancer as appropriate
16-84
Create the Cluster using the same IP and configuration as in the old system.
For Microsoft NLB: Add FE1 to the Cluster. Using NLB Manager Console, select Create New Cluster
and proceed with the new Cluster with Host 1 = FE1 and Cluster IP = Virtual IP.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
administrationsszenarien.fm
For internal use only
Administration Scenarios
Migration Scenarios
For external Load Balancer: Configure the external Load Balancer as appropriate.
NOTE: From this point on the DLS service will be available again, serving from the newly
installed Windows Server 2008 R2 system.
8. Installation of Windows Server 2008 R2
a) Installation of Windows Server 2008 R2 on FE2 and BE2
b) Network configuration of FE2 and BE2.
c) Installation of the Microsoft NLB (if an external Load Balancer is used,skip this step).
Install the Microsoft NLB on FE1 by adding it as a feature from the Server Manager.
For Microsoft NLB: Add FE2 to the Cluster. Using NLB Manager Console, connect to the existing
cluster and then add FE2 as host on the Cluster.
For external Load Balancer: Configure the external Load Balancer as appropriate.
12. Verify that DLS login is possible using the Virtual IP of the cluster.
a) Enable any automated administrative tasks that were disabled before the migration procedure (e.g.
Element Manager Synchronization, P&P)
b) Activate any scheduled jobs that were cancelled before the migration procedure
The upgrade/migration is complete. The DLS Cluster should be operational again, without any data loss.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
16-85
administrationsszenarien.fm
Administration Scenarios
Migration Scenarios
The IP and MAC assignments of the computers as well as the DLS Nodes order within the Cluster and the
Database Mirroring should be unaffected.
16-86
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
glossar.fm
For internal use only
Appendix
Abbreviations and Technical Terms
17 Appendix
The appendix contains abbreviations and additional information.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
17-1
glossar.fm
Appendix
ASCII
(dec)
Characte ASCII
r
(hex)
ASCII
(dec)
Characte ASCII
r
(hex)
ASCII
(dec)
SP
20
32
40
64
^A
21
33
41
65
^B
"22
34
42
66
^C
23
35
43
^D
24
36
44
^E
25
37
^F
&
26
38
^G
'27
39
^H
28
40
^I
29
^J
0A
10
2A
^K
0B
11
^L
0C
12
^M
0D
13
^N
0E
14
^O
0F
^P
10
^Q
^R
Characte ASCII
r
(hex)
ASCII
(dec)
60
96
61
97
62
98
67
63
99
68
64
100
45
69
65
101
46
70
66
102
47
71
67
103
48
72
68
104
41
49
73
69
105
42
4A
74
6A
106
2B
43
4B
75
6B
107
2C
44
4C
76
6C
108
2D
45
4D
77
6D
109
2E
46
4E
78
6E
110
15
2F
47
4F
79
6F
111
16
30
48
50
80
70
112
11
17
31
49
51
81
71
113
12
18
32
50
52
82
72
114
^S
13
19
33
51
53
83
73
115
^T
14
20
34
52
54
84
74
116
^U
15
21
35
53
55
85
75
117
^V
16
22
36
54
56
86
76
118
^W
17
23
37
55
57
87
77
119
^X
18
24
38
56
58
88
78
120
^Y
19
25
39
57
59
89
79
121
^Z
1A
26
3A
58
5A
90
7A
122
1B
27
3B
59
5B
91
7B
123
1C
28
<
3C
60
5C
92
7C
124
1D
29
3D
61
5D
93
7D
125
1E
30
>
3E
62
5E
94
7E
126
1F
31
3F
63
5F
95
DEL
7F
127
17-2
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
glossar.fm
For internal use only
Appendix
Abbreviations and Technical Terms
ASCII
(dec)
Characte ASCII
r
(hex)
ASCII
(dec)
A0
160
C0
192
E0
224
Characte ASCII
r
(hex)
ASCII
(dec)
Characte ASCII
r
(hex)
ASCII
(dec)
80
128
81
129
A1
161
C1
193
E1
225
82
130
A2
162
C2
194
E2
226
83
131
A3
163
C3
195
E3
227
"
84
132
A4
164
C4
196
E4
228
...
85
133
A5
165
C5
197
E5
229
86
134
A6
166
C6
198
E6
230
87
135
A7
167
C7
199
E7
231
88
136
A8
168
C8
200
E8
232
89
137
A9
169
C8
201
E9
233
8A
138
AA
170
CA
202
EA
234
8B
139
AB
171
CB
203
EB
235
8C
140
AC
172
CC
204
EC
236
8D
141
AD
173
CD
205
ED
237
8E
142
AE
174
CE
206
EE
238
8F
143
AF
175
CF
207
EF
239
90
144
B0
176
D0
208
F0
240
91
145
B1
177
D1
209
F1
241
92
146
B2
178
D2
210
F2
242
"
93
147
B3
179
D3
211
F3
243
94
148
B4
180
D4
212
F4
244
95
149
B5
181
D5
213
F5
245
96
150
B6
182
D6
214
F6
246
97
151
B7
183
D7
215
F7
247
98
152
B8
184
D8
216
F8
248
99
153
B9
185
D9
217
F9
249
9A
154
BA
186
DA
218
FA
250
9B
155
BB
187
DB
219
FB
251
9C
156
BC
188
DC
220
FC
252
9D
157
BD
189
DD
221
FD
253
9E
158
BE
190
DE
222
FE
254
9F
159
BF
191
DF
223
FF
255
PU
Abbreviation for "Call Pickup".
If you have one workpoint in an office and another in a lab and want your contacts to be able to reach you at a
single subscriber number, you can create a pickup group containing both workpoints. The workpoint called rings.
The call can be accepted. The "call pickup" LED also flashes on the other workpoint. You can answer the call by
simply pressing the appropriate button.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
17-3
glossar.fm
Appendix
BE1
Abbreviation for "Back End 1".
This is the computer designated as Database Server having the Principal Role which is configured during the
installation of the system. If any fail-over has occurred since the installation of the system, BE1 might have
changed to the Mirror Role. BE1 is the system that was intended to be the Database Server with the Principal Role
during the initial installation of the system.
BE2
Abbreviation for "Back End 2".
This is the computer designated as Database Server having the Mirror Role. Look above (BE1) for clarifications.
BE3
Abbreviation for "Back End 3".
This is the computer designated as the Database Witness Server.
C-SWS
Abbreviation for "Central Software Supply Server".
Name of the central software supply server in Brussels.
CA
Abbreviation for "Certification Authority".
CAP
Abbreviation for "Common Application Platform".
CAT NetInstall
In Germany, you can use CAT NetInstall for installation on TAP.
CD
Abbreviation for "Call Deflection".
ISDN feature for call deflection in ringing state.
CF
Abbreviation for "Call Forwarding".
ISDN feature for automatic call forwarding.
The following types of call forwarding exist:
CFU
Call Forwarding Unconditional (immediate call forwarding)
CFNR
Call Forwarding No Reply (forward call if no reply)
CFB
Call Forwarding Busy (forward call if busy)
17-4
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
glossar.fm
For internal use only
Appendix
Abbreviations and Technical Terms
CLA
Abbreviation for "Customer License Agent".
The HLM component that encrypts the licenses for the product and assigns them to the relevant products.
CLI
Abbreviation for "Command Line Interface".
Operating network devices by entering data in a command line. This interface is usually password-protected and
is reached via Telnet.
CLM
Abbreviation for "Customer License Manager".
The HLM component that administers HiPath product licenses for the customer.
CSV
Abbreviation for "Comma-Separated Values".
File with tabular data. In some cases, the column labels are entered in the first line. In general, a column is set off
by a semicolon or comma, and a line change is indicated by the start of a new line. Can be imported with
Microsoft Excel, for example.
CTI
Abbreviation for "Computer Telephony Integration".
CTI uses computer technology to support telephone services. It not only supports the varied attendant functions
associated with service features but also system management and accounting.
CTS
Abbreviation for "Clear To Send".
Clear to send is an interface function signal. It is part of modem control in handshake mode and is also used for
access authorization in the CSMA/CA procedure. In this procedure (which is also used in WLANs with 802.11), a
station that wants to send data transmits an RTS (Ready To Send) packet. If the transmission route to the receiver
is clear, the station receives a CTS packet.
CW
Abbreviation for "Call Waiting".
ISDN feature for signaling the arrival of more calls during a call.
DBFS
Abbreviation for "Database Feature Server".
Manager for the HiPath 3000/5000 communication platform.
Default Route
A default route is a route that is suitable for each target address. This means that the route can be used for all
target addresses. The default route has the lowest priority and is only used if no other routes match. A route
essentially determines which path the packets should or can take for transport in the network if no path is
prescribed or known, the default route is used.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
17-5
glossar.fm
Appendix
DCMP
Abbreviation for "DLS-Contact-Me-Proxy". The DCMP acts as a proxy for routing between the DLS and devices
when a firewall or NAT prevents the DLS from sending Contact-Me messages to the devices. The DCMP can
communicate with the DLS over the firewall or NAT and is polled regularly by the devices for messages from the
DLS. If messages are present, the DCMP creates a connection between the device and the DLS. The DLS can
then send control and configuration data to the device.
DHCP
Abbreviation for "Dynamic Host Configuration Protocol".
Dynamic assignment of IP addresses for stations in an IP network using a central DHCP server.
DLS
Abbreviation for "OpenScape Deployment Service".
The DLS is an OpenScape Management application for administering IP devices (IP phones, IP client
installations, and IP gateways) in HiPath and non-HiPath networks.
DMC
Abbreviation for "Direct Media Connection".
Workpoints that use signaling to establish connections via a switching element (for example, a gateway) also
usually transmit reference data via this switching element. If both workpoints use the same signaling protocol and
the same type of reference data transmission, switching via the gateway can be used to directly exchange
reference data between the two workpoints. This direct exchange of reference data is referred to as "Direct Media
Connection".
DNS
Abbreviation for "Domain Name Service".
The DNS service converts an alphanumeric name query (such as www.unify.com/us/) into an IP address.
The large primary name servers at InterNIC and the national registration agencies (such as, en-NIC for Germany)
have database servers for this to assign the IP addresses to the host names.
Domain
A domain is a logical network of computers and can also be split up into subdomains. DNS servers are used for
resolving domain names. An example of a domain name is www.microsoft.com, for example. In this case, the "."
(period) stands for the ROOT of the DNS server, ".com" stands for the commercial top-level domain, ".microsoft"
stands for the company and "www" stands for the computer. Domain names are resolved from right to left.
Downgrade
Installation of software with a version number that is lower than the one currently in use.
DSM
Abbreviation for "optiPoint DIsplay Module".
A key module for optiPoint workpoints which features a touchscreen and enhanced functions, such as phone
book, browser, and Java programs.
17-6
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
glossar.fm
For internal use only
Appendix
Abbreviations and Technical Terms
DTMF
Abbreviation for "Dual-Tone Multifrequency".
This dual-tone procedure is used in phone systems for dialing. DTMF replaced the pulse-tone procedure used in
older rotary-dial telephones and establishes connections quickly in communications networks. The DTMF signal
consists of two tones which are generated by pressing the keys on a phone and transmitted to the switching
center. These two tones are taken from a set of eight different tones. They are assigned to the lines (1, 4, 7, star)
and rows (1, 2, 3) on a telephone keypad. The DTMF procedure can also be used to access menu-driven services
(for example, answering machines, mailboxes) directly via a telephone keypad.
E.164
Standardized phone number according to the ITUs international numbering plan with a maximum of 15 digits.
Normally composed of three parts: CC, (Country Code), NDC (National Destination Code) and SN (Subscriber
Number).
EAP
Abbreviation for "Extensible Authentication Protocol".
ECT
Abbreviation for "Explicit Call Transfer".
ISDN feature for call transfer during the call.
ENB
Abbreviation for "Electronic Note Book".
A personal phone book in a display or application module.
EOR
Abbreviation for "End Of Record".
Describes the end of a data record or reporting interval.
EOS
Abbreviation for "End Of Session".
Describes the end of a connection.
FE1
Abbreviation for "Front End 1".
This is the computer designated as DLS Node 1 of the DLS Cluster.
FE2
Abbreviation for "Front End 2".
This is the computer designated as DLS Node 2 of the DLS Cluster.
FTP
Abbreviation for "File Transfer Protocol".
Used for transferring files in networks, for example, for updating telephone software.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
17-7
glossar.fm
Appendix
G.711
Audio protocol for uncompressed voice transmission based on the Pulse Code Modulation (PCM) procedure.
Requires a bandwidth of 64 Kbps ("ISDN quality").
G.722
Audio protocol for compressed voice transmission with max. 7 kHz. Requires a bandwidth of 64 Kbps.
G.723
Audio protocol for compressed voice transmission. The quality is inferior to G.711 and G.729. Requires a
bandwidth of approximately 6 Kbps.
G.729
Audio protocol for compressed voice transmission. The quality is inferior to G.711 and superior to G.723. Requires
a bandwidth of approximately 8 Kbps.
Gatekeeper
A gatekeeper is a logical component of the H.323 standard that can be implemented as Windows or UNIX
software, as a router option, or as a part of an MCU or a Gateway.
Gateway
A system (computer or module) that transmits data between different networks. Where necessary, gateways
coordinate different protocols with each other, for example, IP network and ISDN network protocols. A gateway
can also simultaneously comprise a Router.
17-8
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
glossar.fm
For internal use only
Appendix
Abbreviations and Technical Terms
H.323 standard
The standard consists of at least three of the following components:
Terminals
Gateways
Gatekeeper
HFA
Abbreviation for "Hicom Feature Access" or "HiPath Feature Access".
Produces the connection using a gateway (for example, HG 1500 or HG 3530) between IP telephony and a PBX.
HLM
Abbreviation for "HiPath License Management".
HTTP
Abbreviation for "Hypertext Transfer Protocol".
Protocol for transmitting data in IP networks.
INCA
Abbreviation for "Interleaved Native Compiled Architecture".
Part of the software and hardware architecture of a workpoint.
IP
Abbreviation for "Internet Protocol".
IP address
Also called "IP" for short. Unambiguous address of a telephone in the network; both IPv4 and IPv6 can be used.
An IPv4 address consists of 4 number blocks, each between 0 and 255, separated by ".". Example:
1.222.44.123
An IPv6 address consists of 8 hexadecimal number blocks, separated by ":". Example:
2001:0db8:85a3:08d3:1319:8a2e:0370:7347
or, if not all blocks are used:
2000:1::3
IPSec
Abbreviation for "Internet Protocol Security".
Jitter
Runtime fluctuations during data transmission in IP networks.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
17-9
glossar.fm
Appendix
JDBC
Abbreviation for "Java Database Connectivity".
JDBC is an interface that establishes a connection between a Java program and a database.
Canonical format
Example of a phone number in canonical format:
Line number
(Local District Code - LDC)
Extension number
+49 (89) 72212345
Phone No.
Local Area Code (LAC)
Local Country Code (LCC)
To dial phone numbers saved in canonical format, these must be made "dialable" using output rules or dialing
properties. The various codes are recognized here as part of the phone number and, where applicable, replaced
with the corresponding dial prefixes (see DP) or the external access code (see EA).
Examples of number resolution:
Phone number saved in canonical LCC/IDP
format:
LAC/NDP
LDC/EA
49/00
89/0
722/0
12345
49/00
89/0
722/0
0559322581
49/00
89/0
722/0
0097218846543
49/00
89/0
722/0
00043562218622415
43/00
562/0
2186/9
22415
49/00
89/0
5593/9
972212345
49/00
9721/0
5593/74
7408972212345
43/00
562/0
2186/74
7400498972212345
Table 17
KDC
Abbreviation for "Key Distribution Center".
LAN
Abbreviation for "Local Area Network".
Layer 2
Second layer (data link layer) in the seven-layer OSI model for describing data transmission interfaces.
The "network access protocol" in the LAN is found in layer 2. The layer contains the access mechanism
(for example, CSMA/CD in the case of Ethernet) and MAC addresses.
17-10
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
glossar.fm
For internal use only
Appendix
Abbreviations and Technical Terms
Layer 3
Third layer (network layer) in the seven-layer OSI model for description of data transmission interfaces.
The network protocol, for example, IP (Internet Protocol) is found on layer 3. This can unambiguously transmit
data packets based on the address. Devices that perform this task are called routers.
LDAP
Abbreviation for "Lightweight Directory Access Protocol".
Simplified protocol for access to standardized directory systems, such as, a company telephone book.
LCD
Abbreviation for "Liquid Crystal Display".
Display of numbers, text, or graphics, using liquid crystal technology.
LEAP
Abbreviation for "Lightweight Extensible Authentication Protocol".
LED
Abbreviation for "Light Emitting Diode".
Cold-light lamp with low energy consumption and various colors.
LLDP-MED
Abbreviation for "Link Layer Discovery Protocol - Media Endpoint Discovery".
LOGO
A graphically designed image.
Mask
The subnet mask classifies networks into A, B, and C networks. Each class has a subnet mask that masks out 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. For example, 254 IP
addresses are available in a class C network.
MAC
Abbreviation for "Medium Access Control Address".
A 48-bit address with which each terminal (for example, IP telephone or network card) unambiguously identifies
itself globally in a network.
MCU
An MCU (Multipoint Control Unit) makes conferences possible between three or more geographically discrete
stations. The MCU acts as a kind of "star distributor", which connects the telephones (known as "commercial
systems") to one another.
MD5
Abbreviation for "Message Digest". The 5 stands for a new variant of the MD algorithm. MD5 is
a pure hash algorithm and generates a unique checksum comprising 128 bits (16 characters)
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
17-11
glossar.fm
Appendix
17-12
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
glossar.fm
For internal use only
Appendix
Abbreviations and Technical Terms
Dialed URI
(before proxy)
Outbound
Proxy
Payload
That percentage of the IP data or of an IP data package that contains the user data, such as, the voice data in the
VoIP .
PBX
Abbreviation for "Private Branch EXchange".
Private telephone system that connects different internal devices to the ISDN network.
PING
Abbreviation for "Packet Internet Groper".
Program for testing whether a connection can be set up to a defined IP destination. During the test, data is sent
to the destination and back again. The result that is output is the success or failure of the transmission and, if
applicable, additional information, such as transmission time.
Port
Ports are used to allow multiple communication connections at one time in IP networks. Different services often
have different port numbers.
Proxy
A proxy server is interim memory that saves information locally.
PSK
Abbreviation for "Pre-Shared Key".
A passphrase that is distributed and used for authenticating encrypted communication.
PSE
Abbreviation for "Personal Security Environment".
That covers e.g. phone certificate, WPI client certificate etc.
PSS
Abbreviation for "Pre-Shared Secret".
Password for authentication in VoIP Security.
PSTN
Abbreviation for "Public Switched Telephone Network", analog telephone network or analog connections to digital
network nodes, also public international telephone network.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
17-13
glossar.fm
Appendix
QCU
Abbreviation for "Quality Control Unit".
QDC
Abbreviation for "Quality Data Collection".
Concept for centrally collecting data on the quality of voice connections via IP networks.
QoS
Abbreviation for "Quality of Service".
Describes the subjectively detectable quality of a voice connection over IP networks. QoS properties are packet
loss rate, packet delay, delay variation, reserved bandwidth, type of bit rate (variable, constant, or unspecified bit
rate), and the bit rate.
RADIUS
Abbreviation for "Remote Authentication Dial-In User Service".
Protocol or software for user authentication via dial-up lines.
RAM
Abbreviation for "Random Access Memory".
Memory with read/write access.
RCC
Abbreviation for "Routing Control Center".
If central routing is used in a network, individual network nodes transmit local route information to the RCC in
regular intervals. The RCC saves this information and uses its global network knowledge to calculate the best
routes between nodes.
Regular expression
Character string that uses specific syntactic rules to describe a set or subset of character strings. Regular
expressions are firstly a type of text-based filter criterion that compares the expression in the form of a pattern with
the text. For instance, it lets your find all character strings starting with 1 or 2, without having to enter any
subsequent digits. Secondly, you can use regular expressions as a type of template for generating sets of digit
combinations without having to specify each individual digit combination.
ROM
Abbreviation for "Read Only Memory".
Memory with read-only access.
Router
Routers set up connections to gateways and have access to several subnets and other routers. Using the IP
address, a router determines the subnet or other router to which it should send data. It decides which path is the
most favorable for the data at a given time.
RSM
Abbreviation for "Realtime Service Manager".
17-14
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
glossar.fm
For internal use only
Appendix
Abbreviations and Technical Terms
RTC
Abbreviation for "Real-Time Communications Server" from Microsoft.
RTS
Abbreviation for "Ready To Send).
This transmission request is part of modem control and is also used in the collision-free access procedure CSMA/
CA (as implemented in 802.11). In modem control, the RTS signal is used in handshake mode as a control signal
between a modem and a digital device that initiates data transmission via the transmission line.
SDLP
Abbreviation for "Standard Device Level Protocol".
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
17-15
glossar.fm
Appendix
SHA-1
Abbreviation for "Secure Hash Algorithm". The 1 indicates a newer version. SHA-1 is a hash
algorithm and generates a checksum of 160 bits (20 characters) out of data lengths under 264
bits.
SIP
Abbreviation for "Session Initiation Protocol".
Protocol standard for initializing calls in IP networks.
SNMP
Abbreviation for "Simple Network Management Protocol".
The protocol is used for communicating with servers that take on network management functions. For example,
this includes logging errors that occur on network components (SNMP trap).
SNTP
Abbreviation for "Simple Network Time Protocol".
The protocol is used between time servers and telephones in a network in order to synchronize the time on the
telephones.
SPA
Abbreviation for "Software Product Assurance".
SQL
Abbreviation for Structured Query Language. This is programming language that was developed by IBM to retrieve
information from relational databases (for example, Microsoft Access).
Particular emphasis was placed on client/server environments (a client sends a request, the server provides the
relevant information) during development.
SRSR
Abbreviation for "Small Remote Side Redundancy".
Indicates that a redundancy system is available.
SRTP
Abbreviation for "Secure Realtime Transport Protocol".
Protocol for the secure transmission of multimedia data via symmetrical encryption.
SSID
Abbreviation for "Service Set IDentifier".
Network name in a WLAN.
SSL
Abbreviation for "Secure Socket Layer".
Technology for encrypted data transmission between client and server using authentication.
17-16
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
glossar.fm
For internal use only
Appendix
Abbreviations and Technical Terms
SSSO
Abbreviation for "Secure Single Sign On".
Access to the DLS is password-protected. The SSSO and all information in the DLS are transmitted in encrypted
form using SSL.
Switch
Switching center in a star-shaped network, for example, HiPath 4000 system.
TAP
Abbreviation for "Techniker ArbeitsPlatz" (EWS - Engineering Workstation).
TCP
Abbreviation for "Transmission Control Protocol".
Along with IP, this is the main protocol on the Internet. It provides a reliable, connection-oriented, full duplex
service in the form of a data flow.
TKIP
Abbreviation for "Temporal Key Integrity Protocol".
Algorithm for encryption in WLANs.
TLS
Abbreviation for "Transport Layer Security".
Standard protocol for performing computer authentication using certificates and encryption.
TTL
Abbreviation for "Time To Live".
This value specifies the lifespan of an IP data packet. Data packets transferred in IP networks can take different
routes to reach their destination. Every time the data packet moves to a new network it passes a router which
decrements the packets TTL value by one. The packet is discarded when the value reaches 0. This ensures that
packets that are unable to find their destination despite lengthy searches do not drift around the Internet ad
infinitum. The higher the original TTL value of a data packet, therefore, the longer the packet can try to reach its
destination.
UDP
Abbreviation for "User Datagram Protocol".
Can be used as an alternative to TCP if there are no requirements in terms of reliability. UDP does not guarantee
to deliver packets or supply them in a particular sequence.
URI/URL
Abbreviations for "Uniform Resource Identifier" and "Uniform Resource Locator".
These are the address of a file or a directory. The most common form of a URI is a URL. A typical URI indicates:
the mechanism for accessing the contents (for example, a protocol such as http, ftp, or file).
the specific name of the contents on this computer (usually a file name).
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
17-17
glossar.fm
Appendix
The parts are optional with the result that a file name is in itself a URL (even a relative one).
DP
Abbreviation for "Dial Prefix".
A distinction is made between the national DP (NDP or National Dial Prefix) and the international DP (IDP or
International Dial Prefix). For example, the national DP for Munich is the "0" in "089". See also Canonical format.
VLAN
Abbreviation for "Virtual Local Area Network".
Subdivision of an IP network into autonomous administration groups (domains). An option for identifying VLAN
membership is by using a VLAN ID.
VLAN is, therefore, a network structure with all the properties of a conventional LAN but without any physical
connections. In contrast to LANs where the distances between stations are subject to restriction, VLANs allows
nodes that are further apart to be combined into a virtual local network.
VoIP
Abbreviation for "Voice over IP".
This refers to voice transmission using IP technology.
VoIP Security
Abbreviation for "Voice over IP Security".
This describes measures for secure VoIP voice transmission.
17-18
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
glossar.fm
For internal use only
Appendix
Abbreviations and Technical Terms
VPN
Abbreviation for "Virtual Private Network".
A VPN connects two networks, a computer, and a network or two computers via public connections (for example,
the Internet).
A tunneling protocol encrypts and decodes transmitted data to ensure that it cannot be accessed by unauthorized
parties.
This technology was developed to cut costs as it is considerably cheaper for field workers to send data to
headquarters via public lines than to create individual networks.
WAP
Abbreviation for "Wireless Application Protocol".
This also refers to graphic applications on mobile telephones, organizers, and other suitable terminals that are
transmitted using the protocol of the same name.
WBM
Abbreviation for "Web-Based Management".
A Web-based workpoint (IP phone) interface for administering configurations and modifying user settings via
remote access.
WEP
Abbreviation for "Wired Equivalent Privacy".
Standard encryption for WLANs. All stations in a WLAN and the access point or WLAN router use the same key
for encrypting and decoding data. WEP distinguishes between 64- and 128-bit encryption.
See also WPA, WPA-PSK.
WLAN
Abbreviation for "Wireless Local Area Network".
Workpoint
Workpoint is a term for both IP telephones, such as, optiPoint 410 standard, and soft clients, such as
optiClient 130.
WPA
Abbreviation for "WI-FI Protected Access".
WPA provides security in WLANs by using dynamic keys for encryption. When a connection or session is set up,
dynamic keys are exchanged via the Extensible Authentication Protocol (EAP).
See also WEP, WPA-PSK.
WPA-PSK
Abbreviation for "WI-FI Protected Access with Pre-Shared Key".
An encryption procedure for WLANs. This procedure uses station-specific keys made up of a pre-shared key and
the MAC address of each device. These keys are automatically updated at regular intervals (rekeying intervals)
See also WEP, WPA.
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
17-19
glossar.fm
Appendix
WSP
Abbreviation for "Wireless Session Protocol".
Protocol for transmitting data on WAP-compatible telephones.
17-20
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
Index
Index
Index
A
Accessing help 3
Action Buttons 21, 7, 220
Activity and Error Log 144, 146
Administering Certificates 42
Alarm Classes 161
Alarm Configuration 158
Alarm List 156
Alarm Protocol 153, 156
ANAT Settings 36
API Notifications 118
APM Inventory 18
Application interface 3
Application List 168, 77
Archives Data 538, 151
Archiving automatic 221
Area of DLS application 4
Audio
Schemes 367
Settings 146
Audio Devices available 369
Audio Settings 65
Audit and Security Log 148, 150
Authentication Policy 119
Autoconfiguration 11
IP Client 536
IP Gateway 537
IP Phone 535
Availability 63, 32
B
Backing up the DLS database 29, 31
Backup 178
Backup/Restore 174
Basic Data 9
Basic E.164 15
Batch File 167
Business Groups 72
Buttons 21
C
CA Administration 207
CA Certificates 172
IPSec / VPN 452
CA CertificatesCertificates
CA 165
CA intern 49
Calender button 12
Call Forwarding 78, 401, 45
Call Log 287
Canonical Dial Lookup 134, 62
Capacity limits of the DLS 12
Certificate
phone certificate 240
RADIUS server CA certificate 243, 246
Certificate Deployment automatic 216
Certificate Deployment Restrictions 76
Certificate Renewal 44
Certificate Trap Settings 155
Certificates 17
administering certificates 42
CA 172
WBM server certificate 109, 122, 123
Changing parameters (first steps) 2
Changing workpoint parameters (first steps) 2
Check box 12
Cluster Configuration 137
Cluster Settings 142
Codecs/Compressing 140
Configuration 487
Activity and Error Log 146
Audit and Security Log 150
Configuration Data 16
Configuration Menus locked 177, 83
Configuration templates 13
Connection
OpenScape 418
Contact Me Notify 200
Context-sensitive help 3
Copy Macro for P&P 63
Country 273
Country & Language 124
CRL Distribution Points 446
CRL Files 455
CSTA Service Provider 307
CTI Configuration 297
CTI HFA Provider 298
D
Daylight Saving 137
DCMP 196, 533
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
-1
Index
E
E.164 Patterns 71
Element 12
Element Manager 2, 23
Protocol 21
Element Manager Configuration 1
Element Manager Security 23
EM Synchronization 521
Enabled Services 55
Exporting Plug&Play Data 44
-2
F
Feature
Settings 1 47, 19
Settings 2 50, 22
Features 10
Server based 71
Field name in the wizard
Configure FTP Server 82
Configure Logging 78
File Deployment 290, 138, 9
File Server 183
File Settings 259
File Types 7
Files
difference to software 1
registering in the DLS 10
Filter test 245, 246, 247
Format update of the DLS database (migration) 32
FTP configuration 11
FTP Server 286
FTP server configuration 83
G
Gateway 314, 327
Configuration 2
Connection 6
QoS Data Collection 8
Report Settings 14
Server Data 12
Threshold Values 16
Gateway (HFA) / SIP Server 12
Gateway (HFA)/SIP Server 8
Gateway (Standby) 15
Gateway/Server 8, 7
Gateways 34
General Features 34
H
Header 7
Help 3
Help function 3
Help Internet URL 285, 136
HFA
Codec Settings 361
Dialing Properties 351
Layout 393
Mobility 194
Mobility with HiPath 3000 68
Settings 235, 319
Settings SPE 409
HFA Client create 47
HFA Phone create 47
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
Index
HiPath 3000/5000 20
HiPath 4000 Assistant 17
HiPath SQL DB 386
History 156
Hot Line 22
How to replace OSV Assistant Manager with OSV
Element Manager (steps) 5
HTTP-Proxy 199, 200
HTTPS configuration 11
HTTPS Server CA Certificates 98, 112
HTTPS Server Configuration 92
I
IEEE
802.11b (Transfer Mode) 215
802.1x (import certificate) 44
802.1x (remove certificate) 51
802.1x phone/RADIUS certificates 236
IEEE 802.1x 44
Images on the Server 96
Import Mobile User Data 65
Importing Plug&Play Data 44
Importing WBM Server Certificates 43
INCA Inventory 14
Info
Deployment Server 141
Internal CA 52
IP Device Response Test 472
IP Device Revoke Certificates 469
Read IP Device Data 462
Reset IP Devices 465
Infrastructure Policies 73
Infrastructure Policy 114
Infrastructure Policy Table 117
Installation
DHCP server 45
DNS server (configuration) 48
FTP server 41
Instant Messaging (XMP) 419
Interaction 142
Interface of the DLS 3
Internal CA 49
Internet Pages 384
Inventory Data 498
management 11
Pings 505
tab 498
IP Address changing 37
IP Client Configuration 293
IP Clients 30
IP clients 478
IP Device
Interaction 456
Pinging 473
IP Device Configuration 518, 28
DCMP 533
DSL Connectivity 525
Profile 523
IP Devices 12
Scanning 14
To archive 226
IP Gateway create 48
IP Gateways 479, 32
IP Phone Configuration 2
IP Phones 27
IP Ranges 69
Scan IP Devices 485
IP Routing 27, 16
IP Switch Data 509
IPSec/VPN
Settings 448
IPv6 Settings 34
Issuer Administration 212
Issuing CAs 35
J
Java 158, 71
Java Midlet Inventory 15
Job
Configuration (interface) 23
Control (interface) 2
entering in the toolbar 7
using job coordination 27
Job Configuration 23
Job Control 2
K
Keylayout 195, 99
Keysets 195, 196
Destinations 201
L
Language 273
LDAP 375, 78
LDAP Inventory 12
LDAP Settings 170
License information 12
License state 251
Licenses 332
Licensing 7
Line Keys 397
List of ports in use 12
Local Functions locked 188, 94
Location 63
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
-3
Index
Location configuration 10
Location Server 222
Location Service 124
Locations 62
Locks 82
Logging On/Off Mobile Users 57
Login Policy 19
Login window 1
Logo File Inventor 16
Logoff automatic 158
Logon/Logoff 155
M
Macro Command Syntax 63
Main menu 4
MakeCall 126
Manage Rules 20
Menu
tree view 4
Menu line 8
Message Filter 244
Message window 22
Messaging Services 277, 130
Migration
DLS database 32
Migration Scenarios 1
Mobile
Users 1
Mobile Users 76
Application List 77
Archives Data 151
Audio Settings 65
Availability 32
Call Forwarding 45
Canonical Dial Lookup 62
Configuration Menus locked 83
Country & Language 124
Data saving 62
Destinations 105
Dialing Properties 58, 59
Dialplan 39
Display/Phone Settings 133
DNS Server 17
Enabled Services 55
Feature Settings 1 19
Feature Settings 2 22
Gateway (HFA)/SIP Server 8
Gateway/Server 7
Help Internet URL 136
History 156
Hot Line 22
Interaction 142
-4
IP Routing 16
Java 71
Keylayout 99
LDAP 78
Lggin on/off 57
Local Functions locked 94
Locks 82
Logoff automatic 158
Logon/Logoff 155
Messaging Services 130
Mobile/Basis User 148
Mobility Data 98
Mobility Logon/Logoff 96
Passwords 53
Phone Lock 137
Profile 54
Protocol 167
QoS Parameter 51
Quality of Service 50
Response Test Settings 152, 164
Ringer Melody 42
Security Settings 52
Send URL Server CA Certificate 117
Server based Features 38
SIP Error Notification 132
SIP Mobility 176
SIP Registering 1 11
SIP Registering 2 13
SIP Settings 121
SIP Terminal Settings 9
Statistics 170, 179
Telephony 57
Time 63
Time parameters 63
User Keylayout 160
User Settings 81
Call related 28
WAP 70
Warm Line 22
XML Applications 72
Mobile Users to archive 227
Mobile/Basis User 148
Mobility 190, 194
Adminstrating 53
Configuring 53
configuring (overview) 16
configuring a function 53
definitions 14
Function 15
Logon/Logoff 96
overview 14
profile concept 17
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
Index
subscriber number 16
Mobility Data 98
Modify Key 48
Modify Keyset 49
Modify OpenScape Data 51
Modifying passwords 10
MOH Inventory 13
Multi-Tenancy 72
N
NETBOOT Inventory 19
Network Drive Configuration 108
News Service 125
Notification 164
O
OCSR 1 Server CA Certificate 115
OCSR 1 Signature CA Certificate 117
OCSR 2 Signature CA Certificate 118
OpenScape Voice 9, 36
OptiClient in Call Centers 36
Options 127
Options field 12
P
P&P Import Protocols 152
P&P Number Pool 74
Parent Profiles 9
Password Change 17
Password Policy 14
Password Policy Settings dditional 102
Passwords 100, 53
Passwords modifying 10
Peer Credentials 449
Periodical File Upload 266
Phone Certificate 240
Phone Lock 288, 137
Ping IP Devices 476, 478
Pinging IP Device 473
Platform 6
Plug&Play
function overview 11
registering workpoints 16
Plug-In Properties 37
Policy Settings 12
Port list 12
Port Number changing 37
Ports 40, 336
Standby 43
Profile Management
Parent Profiles 9
Templates 6, 13
Tenants 8, 14, 22
Program Interface DlsAPI 40
Protocol 167
Activity and Error Log 147
Audit and Security Log 151
Automatic Archiving 228
Backup/Restore 181
Upload Diagnosis- and Security Log Files 233
Proxy 326
Q
QoS Data Collection 8
QoS Parameter 83, 51
Standby 90
Quality of Service 340, 50
R
RADIUS Certificates 44
RADIUS Server CA Certificate 243
Reg-Addresses 70
Registering
by scanning workpoints 480
workpoints by reading data 457
Registrar 324
Registration
software, automatic 11
Remote Trace 262
Renewal 54
Repeat filter 242
Replacing an Old Workpoint 30
Replacing HFA with SIP Software 31
Replacing SIP with HFA Software 32
Report
Settings 95, 429, 14
Request Parameter 42
Requirements
personnel 3
technical 1
Reset
DLS database 32
workpoints 463, 467, 470
Response Test Settings 152, 164
Restore 179
DLS database 30, 31
Restrictions of the DLS 12
Rights
Account Configuration 9
Roles and Rights 26
Ringer Melody 75, 42
Roles 8
Roles and Rights 22
Routing 27
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
-5
Index
S
Safety Mode 6
Saving the DLS database 29, 31
Scan IP Devices 14, 487
Scan Results 489
Search Functionality 26
Section 6.6.7 "Settings" Tab 55
Secure mode 188
Secure Shell (SSH) access 261
Secure Trace 269
Security EncryptionWLAN
Security Encryption 219
Security Log Files upload automatic 230
Security Settings 433, 52
Security State Protocol 529
Selecting views 11
Selection list field 12
Send URL Server CA Certificate 213, 117
Server Assignments 76
Server based Features 38
Server Configuration 56
Server Data 94, 428, 12
Server Licenses 248
Service Interface 40
Services (NW Stack) enabled 106
Services nabled 55
Session Policy 21
Settings
802.1x 237
Alarm Configuration 172
ANAT 36
Audio 146
Automatic Archiving 224
Automatic SPE Configuration 214
Codecs 140
Daylight Saving 137
Diagnostic 250
Display/Phone 280
HFA 235, 319
IPSec/VPN 448
IPv6 34
Remote Trace 262
Report 95
Secure Trace 269
SIP 232
SPE 438
SRSR 127, 349
Time 136
Trace Configuration 240
Video 371
-6
Index
Survivability 331
SW Deployment 318
SW Deployment Restrictions 75
Syslog 170
System
Functions 387
Requirements 2
Services 329
SYSTEM/RINGTONE Inventory 17
T
Tab
Standard Profile 80, 81
Syslog 170
Tabs
displaying 12
Inventory Data 498
Telephony 125, 346, 57
Templates 6, 13
Tenants 57
Account Configuration 10
FTP Server Configuration 90
HTTPS Server Configuration 103
Location 77
Network Drive Configuration 113
Profile Management 8, 14, 22
Text field 12
Threshold Values 97, 430, 16
Time 136, 63
Time parameters 135, 63
TLS Connector Configuration 130
Trace Configuration 234, 240
Trash 507
Tree menu 4
Trust Anchor 45, 46
Truststore DLS API 136
Truststore DLS Client GUI 134
View bar 11
VPN Settings 334
W
WAP 157, 70
Warm Line 22
WBM Importing Server Certificates 43
WBM Server Certificate 109
WBM Server Certificates 434
WEB Access 420
Web Service Interface 40
Windows for messages 22
WLAN
Debug 225
Location Server 222
Settings 215
Workpoint Firmware Installation 12
Workpoint Interface Configuration 186
X
XML Application Data 18
XML Applications 120, 160, 72, 1, 6, 70
Info 6
IP Devices 12
U
Uninstalling the DLS server 59
Update 318
Upgrading from SQL Server 2008 to SQL Server
2012 5
User Data Profile 10
User Keylayout 160
User Settings 175, 81
Call related 58, 28
Using the DLS 1
V
Video Devices available 373
Video Settings 371
P31003-S2370-M107-28-76A9, 11/2014
OpenScape Deployment Service V7, Administration & Installation Manual
-7