Release Notes

Release Notes Version: V2.9

Product Name: OpenScape Deployment Service (DLS)

Product Version: V7 R3

Software Release is identified by Version: V7R3.25.0

Major Release Minor Release Fix Release Hotfix Release

Production Version: HI-DLS7R3.464.00

System:
File type Product Item Number / File name Size
archive zip file 464.00_singlenode.zip 600589017 bytes
archive zip file 464.00_multinode.zip 409350372 bytes

Export Control Classification Data AL: N ECCN: 5D002ENCU

Field Trial: eeQS: Limited Availability: General Availability:

Notice:
This document contains confidential information that is proprietary to Unify Software and Solutions GmbH &
Co.KG. No part of its contents may be used, copied, disclosed, or conveyed to any party in any manner
whatsoever without prior consent.

DECLARATION DATE: Date : 2016-12-21

DELIVERABLES: Full Release: Delta Release:

Copyright © Unify Software & Solutions GmbH & Co. KG, 2016
Mies-van-der-Rohe-Strasse 6, 80807 Munich, Germany
All rights reserved.
The information provided in this document contains merely general descriptions or characteristics of
performance which in case of actual use do not always apply as described or which may change as a result of
further development of the products. An obligation to provide the respective characteristics shall only exist if
expressly agreed in the terms of contract. Availability and technical specifications are subject to change
without notice.
Unify, OpenScape, OpenStage and HiPath are registered trademarks of Unify Software & Solutions GmbH &
Co. KG. All other company, brand, product and service names are trademarks or registered trademarks of
their respective holders.

Release Note page 1 (of 25) Openscape Deployment Service V7R3

 Table of Contents

1 HISTORY OF CHANGE................................................................................................................................4
1.1 RELEASE NOTES HISTORY ........................................................................................................................ 4
1.2 PRODUCT VERSION HISTORY .................................................................................................................... 4
2 IMPORTANT INFORMATION.......................................................................................................................6
2.1 SUPPORTED DEPLOYMENTS ..................................................................................................................... 6
2.1.1 Standalone Deployment (PostgreSQL DB) ................................................................................... 6
2.1.2 Multi - Node Deployment (MSSQL Server DB).............................................................................. 6
2.1.3 Integrated Deployment with OpenScape Voice ............................................................................. 6
2.1.4 Database Mirroring ........................................................................................................................ 7
2.1.5 Standalone Linux Deployment ....................................................................................................... 7
2.1.6 DLS Deployment on a SESAP Server ........................................................................................... 7
2.2 INSTALLATION.......................................................................................................................................... 7
2.2.1 Installing new DLS standalone deployment with postegreSQL installation................................... 7
2.3 UPGRADE / UPDATE ................................................................................................................................. 8
2.3.1 Single-node upgrade/update to DLS postgreSQL deployment ..................................................... 8
2.3.2 Multi-node upgrade/update ............................................................................................................ 9
2.3.3 License Information........................................................................................................................ 9
2.4 FALLBACK ............................................................................................................................................... 9
2.5 SECURITY CONSIDERATIONS .................................................................................................................... 9
2.6 SPECIAL SETTINGS AND INSTRUCTIONS ..................................................................................................... 9
3 REPORTED PROBLEMS / SYMPTOMS UNDER ANALYSIS ..................................................................10

4 RESTRICTIONS, WORKAROUNDS AND HINTS .....................................................................................11

4.1 RESTRICTIONS ...................................................................................................................................... 11
4.1.1 Old DLS backup .bak files (MSSQL Server) not supported with postgreSQL............................. 11
4.1.2 Create new phone credentials from older DLS releases (Warning Notice)................................. 11
4.1.3 Phones in secure mode ............................................................................................................... 11
4.1.4 DCMP........................................................................................................................................... 11
4.1.5 Recreate Element Manager after installation............................................................................... 11
4.1.6 Apply basic profile (mobile user or basic user) ............................................................................ 11
4.1.7 Automatic SPE Configuration ...................................................................................................... 11
4.2 W ORKAROUNDS / HINTS ........................................................................................................................ 12
4.2.1 Java applet replacement.............................................................................................................. 12
4.2.2 Upgrades...................................................................................................................................... 12
4.2.3 Element Manager Synchronization.............................................................................................. 12
4.2.4 Support of Desk Phone IP 35G & IP 55G Phones ...................................................................... 12
4.2.5 Restore of a backup file from a previous load ............................................................................. 13
4.2.6 New Credentials for Workpoint Interface – Migration to new PKI schema – Workaround for “Per
Device” deployment.................................................................................................................................... 13
4.2.6.1 Server Credentials – “Create” button:...................................................................................................... 13
4.2.6.2 Server Credentials – “Deploy” button: ..................................................................................................... 13
4.2.6.3 Client Credentials – “Create” button: ....................................................................................................... 13
4.2.6.4 Workaround for “Per Device” deployment of WPI Credentials:................................................................ 13
4.2.7 5-digit to 6-digit PINs adaptation prior to moving on from DLSV3 to a product line above to avoid
resets 15
4.2.8 Deletion of endpoints through API ............................................................................................... 15
4.2.9 Import / Export via DLS GUI ........................................................................................................ 15
4.2.10 Disable multi-tenancy feature ...................................................................................................... 15
5 CHANGES...................................................................................................................................................16
5.1 NEW IN THIS RELEASE ............................................................................................................................ 16
5.2 IMPLEMENTED CHANGE REQUESTS ......................................................................................................... 19
5.3 RESOLVED REPORTED PROBLEMS / SYMPTOMS ...................................................................................... 19
6 HARDWARE AND SOFTWARE COMPATIBILITY ...................................................................................20
6.1 HARDWARE REQUIREMENTS ................................................................................................................... 20

Release Note page 2 (of 25) Openscape Deployment Service V7R3

 6.1.1 Minimum Hardware Requirements for a DLS Server in a Single Node (standalone) Deployment
20
6.1.2 Minimum Hardware Requirements for a DLS Server in a Multi-Node Deployment..................... 20
6.1.3 Minimum Hardware Requirements for an MSSQL Database Server .......................................... 20
6.1.4 Minimum Hardware Requirements for an MSSQL Witness Server............................................. 20
6.1.5 Usage of DLS in a VMware environment..................................................................................... 21
6.2 FIRMWARE RELEASES ............................................................................................................................ 21
6.3 LOADWARE RELEASES ........................................................................................................................... 21
6.4 SOFTWARE RELEASES ........................................................................................................................... 21
6.5 OPERATING SYSTEMS (INCLUDING SECURITY ALERTS) ............................................................................. 22
6.5.1 Database...................................................................................................................................... 22
6.5.2 Operating Systems and Client PC Requirements ....................................................................... 22
6.6 COMPLIANT PRODUCTS (COMPATIBILITY MATRIX) ..................................................................................... 22
7 SERVICE INFORMATION ..........................................................................................................................25
7.1 MANAGEMENT INFORMATION BASE ......................................................................................................... 25
7.2 LICENSE MANAGEMENT .......................................................................................................................... 25

Release Note page 3 (of 25) Openscape Deployment Service V7R3

1 History of change

1.1 Release notes history

Version Date Changes

1.0 2015-06-01 Release of CV439.00 – GA for V6, V7R1, V8; eeQS for V8R1
1.1 2015-06-18 Release of CV440 – GA for V6, V7R1, V8
1.2 2015-07-06 Release of CV441 – GA for V6, V7R1, V8; eeQS for V8R1
1.3 2015-07-17 Re-release of CV441.00 + CV441.01 – GA for V6, V7R1, V8; eeQS for V8R1
1.4 2015-07-24 GA for OSV V8R1
1.5 2015-07-27 Release of CV442 – GA for V6, V7R1, V8, V8R1
1.6 2015-08-19 Release of CV443 – GA for V6, V7R1, V8, V8R1
1.7 2015-09-09 Release of CV444 – GA for V6, V7R1, V8, V8R1
1.8 2015-09-29 Release of CV445 – GA for V6, V7R1, V8, V8R1
1.9 2015-11-11 Release of CV447 – GA for V6, V7R1, V8, V8R1
2.0 2015-11-25 Re-release of CV447.00 + CV447.01 – GA for V6, V7R1, V8; V8R1
2.1 2015-12-21 Release of CV449 – GA for V6, V7R1, V8, V8R1
2.2 2016-02-16 Release of CV451 – GA for V6, V7R1, V8, V8R1
2.3 2016-03-08 Release of CV452 – GA for V6, V7R1, V8, V8R1
2.4 2016-04-19 Release of CV454 – GA for V6, V7R1, V8, V8R1, V9
2.5 2016-06-08 Release of CV456 – GA for V6, V7R1, V8, V8R1, V9
2.6 2016-07-11 Release of CV457 – GA for V6, V7R1, V8, V8R1, V9
2.7 2016-08-10 Release of CV459 – GA for V6, V7R1, V8, V8R1, V9
2.8 2016-10-17 Release of CV462 – Field Trial/eeQS for V9R1 Solution
2.9 2016-12-21 Release of CV464 – GA for V6, V7R1, V8, V8R1, V9

1.2 Product version history

List of all released Software Versions since Major Software Release (M3), i.e. all Software Releases in SWS
having been released within this Product version:

Software version Production version Date Remarks

(e.g. Vx[.y] Rm.f.h) (e.g. APS)
V7 R3.0.0 HI-DLS7R3.439.00 2015-06-01 GA for V6, V7R1, V8; eeQS for V8R1
V7 R3.1.0 HI-DLS7R3.440.00 2015-06-18 GA for V6, V7R1, V8; eeQS for V8R1
V7 R3.2.0 HI-DLS7R3.441.00 2015-07-06 GA for V6, V7R1, V8; eeQS for V8R1; Terminated from
SWS
V7 R3.2.1 HI-DLS7R3.441.01 and 2015-07-17 GA for V6, V7R1, V8, V8R1
441.00
V7 R3.3.0 HI-DLS7R3.442.00 2015-07-27 GA for V6, V7R1, V8, V8R1
V7 R3.4.0 HI-DLS7R3.443.00 2015-08-19 GA for V6, V7R1, V8, V8R1
V7 R3.5.0 HI-DLS7R3.444.00 2015-09-09 GA for V6, V7R1, V8, V8R1
V7 R3.6.0 HI-DLS7R3.445.00 2015-09-29 GA for V6, V7R1, V8, V8R1
V7 R3.8.0 HI-DLS7R3.447.00 2015-11-11 GA for V6, V7R1, V8, V8R1
V7 R3.8.1 HI-DLS7R3.447.01 and 2015-11-25 GA for V6, V7R1, V8, V8R1
447.00

Release Note page 4 (of 25) Openscape Deployment Service V7R3

 Software version Production version Date Remarks
(e.g. Vx[.y] Rm.f.h) (e.g. APS)
V7 R3.10.0 HI-DLS7R3.449.00 2015-12-21 GA for V6, V7R1, V8, V8R1
V7 R3.12.0 HI-DLS7R3.451.00 2016-02-16 GA for V6, V7R1, V8, V8R1
V7 R3.13.0 HI-DLS7R3.452.00 2016-03-08 GA for V6, V7R1, V8, V8R1
V7 R3.15.0 HI-DLS7R3.454.00 2016-04-19 GA for V6, V7R1, V8, V8R1, V9
V7 R3.17.0 HI-DLS7R3.456.00 2016-06-08 GA for V6, V7R1, V8, V8R1, V9
V7 R3.18.0 HI-DLS7R3.457.00 2016-07-11 GA for V6, V7R1, V8, V8R1, V9
V7 R3.20.0 HI-DLS7R3.459.00 2016-08-10 GA for V6, V7R1, V8, V8R1, V9
V7 R3.23.0 HI-DLS7R3.462.00 2016-10-17 Field Trial/eeQS for V9R1 Solution
V7 R3.25.0 HI-DLS7R3.464.00 2016-12-21 GA for V6, V7R1, V8, V8R1, V9

Release Note page 5 (of 25) Openscape Deployment Service V7R3

2 Important Information

2.1 Supported Deployments

2.1.1 Standalone Deployment (PostgreSQL DB)

In this deployment scenario, DLS is installed on its own Windows server. The database is PostgreSQL and
is installed by the DLS installer on the same server as DLS.

During a fresh installation or upgrade from MSSQL deployment, DLS installer also installs the postgreSQL
database. There is no need for MSSQL installation in this deployment. This deployment replaces the
existing standalone deployment (Single Node) with MSSQL Server. Single node DLS with PostgreSQL is
a local DB deployment only.

2.1.2 Multi - Node Deployment (MSSQL Server DB)

In a multi-node deployment, up to 4 DLS servers may be used for load distribution. The DLS nodes must
be attainable over one IP address, e.g. by employment of Windows network load balancer. A geographical
separation requires therefore a L2 network or OSPF Routing of minutes, which supports one IP address at
different locations.
This deployment model can also be used to achieve redundancy.
This feature is subject to licensing. The required licenses must be obtained for nodes 2 through 4.

2.1.3 Integrated Deployment with OpenScape Voice

With OpenScape Voice Integrated Simplex, DLS is installed on the server of the communication system.
Please refer to the latest V7R2 Applications Release Notes regarding this deployment.

OpenScape Voice Integrated Simplex:

Release Note page 6 (of 25) Openscape Deployment Service V7R3

 2.1.4 Database Mirroring
Starting with DLS V2 R3, synchronous database mirroring is offered.
The following deployment scenario can be implemented:
High availability with three servers
In this scenario, a Witness server monitors the Database and Mirror servers. An automatic failover is thus
guaranteed.

This feature is subject to licensing. The required license must be obtained for database mirroring.

2.1.5 Standalone Linux Deployment

The Stand-Alone Linux DLS Deployment is NOT supported. Customers, who have DLS installed as a
Standalone Linux Deployment, should consult DLS Product Management to request a migration procedure
towards a Standalone Windows Deployment.

2.1.6 DLS Deployment on a SESAP Server

This section lists all important information that affects this product:
DLS deployment on a SESAP server is supported, under certain conditions:
1. No mobility feature is used; in case there is mobility feature use, installation of DLS is not supported
on a SESAP server.
2. Number of subscribers is low (<1500); If the number of subscribers is more than that or in cases
where very high load on the DLS can be expected, then a separate server should be used for DLS.

2.2 Installation

2.2.1 Installing new DLS standalone deployment with postegreSQL installation

As described above, since CV464, postgreSQL DLS deployment replaces the existing standalone
deployment (Single Node) with MSSQL Server.

Release Note page 7 (of 25) Openscape Deployment Service V7R3

 Prerequisite: Before the installation of this deployment, Microsoft Visual C++ Redistributable Packages for
Visual Studio 2013 should be installed in the server. These can be downladed from:
https://www.microsoft.com/en-us/download/details.aspx?id=40784
Please install “vcredist_x64.exe” or “vcredist_x86.exe” for 64bit or 32 bit systems respectively.
DLS installer performs a check and tries to detect if the Microsoft Visual C++ Redistributable Packages for
Visual Studio 2013 is installed in the system, prior to installation.
If the above software is not installed, DLS installer will inform the user with the following message.

In this case, the user should abort the installation, install the Microsoft Visual C++ Redistributable
Packages for Visual Studio 2013 and re-initiate the installation.

2.3 Upgrade / Update

2.3.1 Single-node upgrade/update to DLS postgreSQL deployment

Preparation for the updrade/update to the DLSV7R3 CV464.00 postgreSQL deployment:
If you are upgrading from an MSSQL deployment to the new postgreSQL one, please consider taking a
backup (.bak) and/or a DB export (.zip) in a backup storage before starting the process.
Please also make sure that there is enough disk space in the partition that DLS is installed, at least twice the
size of the DLS DB.
An update of a standalone (singlenode) DLS system to DLSV7R3 CV464.00 postgreSQL deployment is
supported from DLSV7R3 CV446 (or newer) product version only.
An upgrade/update to DLSV7R3 CV446 (or a later verison) is required (prior to upgrade to CV464), if DLS is
in the following versions:
 All DLSV3R1 software loads up to and including CV852
 All DLSV6R1 software loads up to and including CV133.xx
 All DLSV7R0/R1/R2 software loads up to and including CV218.xx/CV323.xx respectively.
 All GA software loads under DLSV7R3 product line, prior to CV446
Same prerequisite of Microsoft Visual C++ Redistributable Packages for Visual Studio 2013 stands also in
the case of an upgrade to standalone postgreSQL DLS deployment. See chapter 2.2.1 for more details.
See relative restrictions under Section 4.
After upgrade/update from a singlenode MSSQL DLS deployment to the current singlenode postgreSQL DLS
deployment, the MSSQL Express installation will not be used by DLS any longer.
At the end of the upgrade/update, DLS installer will prompt the user to uninstall (if he wishes to) the MSSQL
Express installation.

Release Note page 8 (of 25) Openscape Deployment Service V7R3

 2.3.2 Multi-node upgrade/update
An upgrade/update of a multinode DLS system to DLSV7R3 CV464.00 MSSQL Server deployment is
supported from the following software levels:
 All DLSV3R1 software loads up to and including CV852
 All DLSV6R1 software loads up to and including CV133.xx
 All DLSV7R0/R1/R2 software loads up to and including CV218.xx/CV323.xx respectively.
 All GA software loads under the DLSV7R3 product line.
See relative restrictions under Section 4.

2.3.3 License Information

DLS V7 licenses must be installed on the CLA server prior to an upgrade or fresh installation. The
minimum supported CLA & CLM versions can be found on the Compatibility Matrix (section 6.6).

2.4 Fallback

NA

2.5 Security Considerations

NA

2.6 Special settings and instructions

NA

Release Note page 9 (of 25) Openscape Deployment Service V7R3

3 Reported Problems / Symptoms under Analysis
Summary
-

Release Note page 10 (of 25) Openscape Deployment Service V7R3

4 Restrictions, Workarounds and Hints

4.1 Restrictions

4.1.1 Old DLS backup .bak files (MSSQL Server) not supported with postgreSQL
As described above, starting with CV464, postgreSQL DLS standalone deployment replaces the
existing standalone deployment (Single Node) with MSSQL Server. Because of this change, any old
MSSQL Server backup files (.bak) cannot be used after upgrading to CV464, since these are not
compatible with postgreSQL DB.
From now on the DLS backup files will be saved as .zip files containing .xml files with the DB content.

4.1.2 Create new phone credentials from older DLS releases (Warning Notice)
Customers who are using credentials that were generated from CV7xx or CV8xx have to generate
new credentials since the backwards compatibility of these older credentials schema will be supported
until CV128.x.

4.1.3 Phones in secure mode

When WPI credentials used for secure mode are imported through respective import/export process,
then bootstrapping of devices in default mode is not possible. Bootstrapping process will require the
creation of new WPI credentials.

4.1.4 DCMP
DCMP is not a two-way (bi-directional) proxy which can be located in-between the DLS nodes and the
phones. DCMP is used to solve communication from DLS to the phones ONLY when the phones are
behind NAT and DLS cannot reach them. (One way proxy). The phones must always be able to reach
DLS in order to work properly. Therefore, DLS cannot be behind NAT; it should be located in a DMZ.
DCMP integrated on DLS is the default and recommended deployment. DCMP should not be installed
using the DCMP installer on a machine already running DLS.
It is required to state that after an upgrade to CV323 or newer from a past DLS software load under
the old brand name, the default password for the 'admin' user to the DCMP web access changes from
'Siemens2004' to 'Asd123!.'.

4.1.5 Recreate Element Manager after installation

It is required for customers to recreate the problematic Element Manager after having installed the fix
itself.

It is not enough to only upgrade to the target DLS load including the fix. Customers will also have to
follow up by a deletion and recreation of the problematic EM that undesirably communicates with port
5060. This issue of course is not valid for newly created Ems with the fix in place.

4.1.6 Apply basic profile (mobile user or basic user)

In order for a basic profile to be applied to a mobile user logged on to a device or to a basic user of a
device, we need to add a template relative to keyset / keylayout mask. The respective template should
include all necessary fixed allocated keys of the desirable device type.

4.1.7 Automatic SPE Configuration

For Automatic SPE Configuration, PKI configuration must be used.

Release Note page 11 (of 25) Openscape Deployment Service V7R3

4.2 Workarounds / Hints

4.2.1 Java applet replacement

Starting with CV464, the DLS Java applet has been replaced by the Java Web Start functionality. With
this change, DLS client will be now running outside the web browser (as a Java desktop application)
and therefore the previous need of supporting the Java plug-in by the web browsers is now
eliminated.
As a result, there is a slight difference in the user experience, when someone is accesing the DLS
GUI url. More specifically the user will be promted to download a .jnlp file:

After downloading the file, the user should “run” this .jnlp file and the DLS client will be loaded outside
the web browser. This can be also done in one step (download and execute), depending on each web
browser’s settings.

4.2.2 Upgrades
In Multinode deployments installation and subsequent upgrades must be always done using a
Windows account that has “sysadmin” role in the SQL Server logins.
In a multinode environment, if the roles of the mirror and principal MSSQL databases (failover
procedure) have been swapped prior to a DLS upgrade procedure, the following message may
appear,

In order to continue the DLS upgrade, please stop and start the DLS service manually on every node.

4.2.3 Element Manager Synchronization

In case the Element Manager Synchronization with type OpenScape Voice needs to be used, then the
CMP administrator needs to create the relevant packet filtering rule via:
“OSV Assistant – Administration – GeneralSettings – PacketFilterRules – Add menu”.
Local port 8769 should be used to allow TCP incoming connection from the IP of the remote
Windows DLS server.
As of this software release, Element Manager synchronization intervals are ranged in between 10mins
(min.) - 1440mins (max.) with 0 (zero) also allowed and intended to deactivate sync intervals.
Note though that the minimum value for OpenScape Voice Assistant EM type is set to 60 minutes
minimum since consider the most intensive by not supporting delta sync of data.

4.2.4 Support of Desk Phone IP 35G & IP 55G Phones

The DLS Administrator must ensure that the phone f/w V3R2 is used ONLY with the new Desk Phone
IP 35G & IP 55G phones and NOT with the OpenStage SIP phones.

Release Note page 12 (of 25) Openscape Deployment Service V7R3

 4.2.5 Restore of a backup file from a previous load
In a multinode environment, proceed with a restore (i.e., on node 1) of a back up file from a previous
load i.e., CV218. If the restore finishes succesfully, but DLS service on node 2 is down, start the DLS
service manually.

4.2.6 New Credentials for Workpoint Interface – Migration to new PKI schema –
Workaround for “Per Device” deployment
With the introduction of the new PKI design, on DLS V6R0, credentials coming from previous DLS
versions are considered deprecated and should be migrated to the new PKI design. DLS V6R1
CV128.x would be the last build where credentials from previous PKI design will be supported. From
CV129 PKI design from previous versions will not be supported.
In order for an administrator to migrate to the new PKI design, new credentials should be created and
deployed to devices contacting DLS in secure mode.
This is a functionality provided through Main Menu > Administration > Workpoint Interface -
Configuration > “Secure mode” Tab
Through “Server Credentials” and “Client Credentials” pane an administrator is able to create,
deploy and activate Server and Client credentials accordingly.

4.2.6.1 Server Credentials – “Create” button:

Creates an additional (inactive) server credential. Only one additional server credential may be
created.
A PKI configuration has to be enabled and selected (internal connector is by default enabled. If an MS
PKI connector shall be used activate needed PKI Configuration). 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.

4.2.6.2 Server Credentials – “Deploy” button:

Deploys the additional server credential to all devices already in secure state.
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.
NOTE: With the implementation of “Additional Credentials Transmission Settings” fields on
CV128, an administrator is able to provide a time interval that will be used to send credentials every X
minutes to Y devices.

4.2.6.3 Client Credentials – “Create” button:

Creates a new client credential. This new client credential is automatically activated and the client
credential previously active is deactivated and becomes outdated.
“Create” button does not trigger a deployment to all devices as well. Devices in secure state will get
new client credentials, as soon as they contact DLS.

4.2.6.4 Workaround for “Per Device” deployment of WPI Credentials:

In cases though that administrators would prefer to deploy new credentials on per-device basis, using
any device-specific criteria, and not on all devices in secure mode, then the below stated workaround
may be followed:
1. Proceed with creation of new Server and Client Credentials through respective action buttons.

Release Note page 13 (of 25) Openscape Deployment Service V7R3

 After selecting “Create” both Server and Client credentials are created but not deployed to devices in
secure state. No job is yet created.
NOTE: Do not proceed with “Deploy” of Server Credentials. Deployment should be done on next steps.
“Deploy” will initiate jobs for all devices in secure state.

2. Navigate to IP Device Management -> IP Device Configuration and select all desirable devices
(e.g. Per location, IP range, E164 etc)
3. On object view, navigate to “DLS Connectivity” tab. Select to “Reset” security state on one of the
devices and apply to all devices through bulk edit functionality (i.e. select “Reset” on object view for the
first device, go to table view, select all device and proceed with save).

4. For each device a job is created. Bootstrapping process is initiated and devices that were already in
secure mode are contacting DLS in secure port.
5. Proceed with steps 2 to 4 for all devices in secure mode. Eventually, all devices should be deployed
with both active and additional server credentials, as well as with active client credentials. Through IP
Device Management -> IP Device Configuration -> DLS Connectivity tab verify that all devices have
been deployed with both active and additional server credentials (“Server Credential 1” and “Server
Credential 2” will be filled in with respective values) and with active client credentials (“Client
Credential” field displays the value “Active”).

NOTE: When original credentials are from DLS versions previous to V6R0 the “Server Credential” fields
are displaying the fingerprint of DLS server credentials as those were generated. After the migration to
new PKI design –i.e. after administrator activates the newly created credentials – respective fields will
display the fingerprint of trust anchor relative to PKI configuration used.
6. New server credentials may now be activated and old credentials can be deleted through “Workpoint
Interface Configuration” mask. Devices in secure mode will be updated accordingly next time they
contact DLS.
NOTE: Please make sure that all OpenStage devices are deployed with firmware version V3R0.73.2 and
later or V3R1.35 and later.
7. Accordingly old client credentials may be deleted through “Workpoint Interface Configuration”
mask.

Release Note page 14 (of 25) Openscape Deployment Service V7R3

 4.2.7 5-digit to 6-digit PINs adaptation prior to moving on from DLSV3 to a
product line above to avoid resets
The mobile users should be bulk edited with a default password.
The procedure is the following:
1)Go to Mobile Users-> Security Settings-> Passwords
2) Search after selecting User Type:Mobile User.
3) Select the first mobile user and set the password.
4) Go to table view and select all the mobile users.
5) Press save.

All the mobile users will now have a user password that can be changed after the first logon.

4.2.8 Deletion of endpoints through API

Starting with this release, when an endpoint is deleted from the DLS API, it is permanently deleted from
DLS.

4.2.9 Import / Export via DLS GUI

DLS GUI import/export functionality has changed in order to work from the local machine (i.e. client pc)
instead of the server machine. Currently there is a known limitation in the above functionality for operations
that take too much time to be completed. This applies to export devices operation mainly. Until this issue is
resolved, if a user wants to export a large number of devices (e.g. more than 100 entries), an alternative
way is provided through the DLS toolkit (command line tool). This command line tool is called dlstoolkit.bat
and can be found under: <DLS installation directory>\Tomcat\webapps\DeploymentService\database.
More specifically for exporting devices the user should execute the following command in the directory
specified above: > dlstoolkit.bat export devices <filename>.csv

4.2.10 Disable multi-tenancy feature

Starting with CV445, customers can remove multi-tenancy using the following steps:
 Make a DB backup of the DLS database with the multi-tenancy feature enabled,
 Uninstall DLS
 Install DLS without multi-tenancy
 Restore the previously backed up DB

Release Note page 15 (of 25) Openscape Deployment Service V7R3

5 Changes

5.1 New in this release

FRN / JIRA Title Relevant RQs Produced in Status

Load
Released with Solution
FRN4347 CMP-DLS Single sign on CV410
V8 only
RQ00033876
Released with Solution
FRN5007 DLS Contact Me NOTIFY (RQ33020, RQ30944) RQ00033020 CV402
V8 only
RQ00030944
FRN5212 OpenStage SIP: Contact-Me during busy state RQ00033925 CV406 Released
RQ00034615
FRN5482 OpenStage SIP video - part2 CV408 Released
RQ00034575
FRN5964 DLS V7R2 TSA,Security checklist and PSA N/A Released

FRN6079 DLS PKI License usage count RQ00036914 CV421 Released

OpenStage SIP: User configuration for distinctive

FRN6108 RQ00035537 CV410 Released
ringing

Certify DLS with OpenScape Business V1 as the

FRN6781 RQ00036163 CV421 Released
successor of Hipath 3000

FRN7038 DLS: Support Desk Phone IP 35G Eco RQ00036640 CV422 Released

FRN7295 DLS support for OpenStage V3R0 HFA RQ00036797 CV420 Released

FRN7366 DLS: Replace OSV Assistant EM with OSV EM CV420 Released

Carry Over of FRN6865 : CR of Bundesagentur

FRN7377 fόr Arbeit - Delete entry from journal when called RQ00036210 CV418 Released
back

Carry Over of FRN6627 : CR of Bundesagentur

FRN7378 fόr Arbeit - Call Forwarding applies to all types of RQ00036211 CV418 Released
incoming calls

OpenStage and Desk Phone IP: FPK support for

FRN7403 RQ00037104 CV420 Released
access to LDAP client

RQ00036731
FRN7420 DLS API enhancements RQ00036952 CV420 Released

RQ00037368

FRN7460 'StartTLS for LDAP Phonebook in OpenStage RQ00037073 CV418 Released

Release Note page 16 (of 25) Openscape Deployment Service V7R3

 Carry Over of FRN7431 : RQ00037283: DLS
FRN7481 RQ00037283 CV420 Released
mobility LDAP template deployment

FRN7484 Carry Over of FRN5623 : Rebranding of the DLS CV419 Released

RQ00037941
FRN8108 DLS support of SHA2/MTLS CV425 Released
RQ00037947

FRN8592 DLS: Support new device configuration options CV428 Released

DLS Overload Protection OpenStage and Desk

FRN7251 RQ00037375 CV429 Under Test
Phone IP- step 1

DLS: LDAP server authentication for OpenStage RQ00037681

FRN7966 CV430 Released
and Desk Phone IP RQ00038311

DLS support for data mobility / privacy mode for RQ00037747

FRN7968 CV431 Under Test
OpenStage 15/20/40 and DeskPhone IP35G RQ00037749

DLS Overload Protection OpenStage and Desk

FRN8217 CV430 Under Test
Phone IP- step 2

FRN8687 Enhance DLS Hotfixing CV430 Released

DLS API enhancements for phone and WBM

FRN8534 CV432 Released
server certificate deployment

DLS Support PKI Connector enhancements RQ00038461

FRN8847 CV432 Released
(prerequisite of FRN8534) RQ00038460

DLS needs to support Windows 2012 for V7R2 CV432 Released

FRN9330

Support the usage of currentPhoneNumber as

FRN8610 CV434 Released
phone identification for HFA mobility

FRN6793 JHPT start from DLS GUI CV434 Released

FRN9408 DLS Rapidstat Improvements CV434 Released

RQ00037571
SIP and HFA phones: Configuration of OPUS,
FRN8303 RQ00037580 CV435 Released
DTLS and ICE
RQ00038008

Released only when the

FRN8495 DLS: Support Wave Evolution 1 CV435 new phone model is
available

FRN9488 DLS API - Export Last Logon / Logoff time RQ00038951 CV435 Released

Release Note page 17 (of 25) Openscape Deployment Service V7R3

FRN9548 DLS: Support TLSv1.2 RQ00038021 CV435 Released

DLS API - Allow update/delete mappings between

FRN9899 RQ00039117 CV435 Released
win account & E164

FRN4348 NG911 Emergency Calling (DLS impact) RQ00032339 CV436 Released

FRN5388 DLS: Support SNMPv3 traps RQ00034474 CV436 Released

Released only when the

DLS: Support new Wave Evolution WE3 phone
FRN8166 RQ00037741 CV436 new phone model is
model
available
Released only when the
DLS: Support new Wave Evolution WE4 phone
FRN8167 RQ00037742 CV436 new phone model is
model
available

OSEE - Simplify the steps needed for DLS

FRN9475 RQ00038822 CV436 Released
Configuration

RQ00033562,
FRN5999 DLS: Servicability Requirements for V7R3 CV437 Released
RQ00034413

DLS: SIEL ID - diplaying it over GUI / requesting it

FRN9730 CV438 Released
over DLS API

FRN9990 DLS: Update to Java 1.7 SR2-FP10 CV438 Released

DLS: Allow enabling both DCMP and SIP NOTIFY

FRN9996 RQ00039370 CV438 Released
for mixed handsets
Released ( Multi-tenancy
FRN4838 DLS - Multi Tenancy requirements RQ00029971 CV439 feature only available
with PSR )
DLS - Use windows username as device ID / RQ00034538 /
FRN5685 CV440 Released
Multiple plug and play RQ00039228

FRN7069 Change Tomcat user / access rights RQ00035488 CV442 Released

OSEE – Trigger HTTPS server scan via DLS

DLS-434 CV442 Released
toolkit

Enhance an intuitive way for the SW update

DLS-597 CV443 Released
during P&P that can be configured easily

P&P configuration precedes bootstrapping to

DLS-408 CV444 Released
secure mode affecting PIN prompt use case

DLS-616 Global UI indicator for active debug tracing CV444 Released

DLS-630 Release DLS with Win 2012 Active Directory CV444 Released

OSV EM: DA credentials synchronization shall

DLS-682 CV445 Released
work for DSS & non-primary line keys

DLS-675 Store / Validate WPI phone certificates CV445 Released

Server/Client certificate auto-renewal for the WPI

DLS-578/DLS-746 CV447 Released
interface

Modifying Audio Setting "Alert Type for Group

DLS-889 CV451 Released
Pickup" via DLS-API

Support BT localization & Eddystone beacon

DLS-1017 CV454 Released
features
DLS-829 Productize Mediatrix implementation CV456 Released

Release Note page 18 (of 25) Openscape Deployment Service V7R3

DLS-1010 Provide the default WE1 FPK keys for a mobile CV456 Released
user

DLS-1039 FRN8147 - Enhance DLS API to provide latest CV456 Released

firmware version per device family.

DLS-1039 Enhance DLS API to provide license information CV456 Released

DLS-1103 Adapt DLS functionality for Openscape Fusion for CV457 Released
Office

DLS-1163 Support a non-Keyset phone being monitored by CV459 Released

a DSS key

DLS-713 / DLS: Support of Single Node DLS deployment CV464 Released

FRN10231 using PostgreSQL

DLS-915, DLS- Support new phone models CP200, CP400 and RQ00039980 CV464 Released
916/FRN10463 CP600 with HFA

DLS-1174, DLS- Replace the JRE applet technology CV464 Released

817/FRN10318

DLS-1243 Add "Authentication Type", "MSCHAP Idenitity" CV464 Released

and "MSCHAP Password" attributes into the DLS
API

5.2 Implemented change requests

CR MR / CQ Summary
Number
N/A

5.3 Resolved Reported Problems / Symptoms

GSI Flow Ticket Summary Produced in Load

NA14965346 OSEE V9 - Cannot deploy firmware to phone CV464
NA14917533 Numerous AutoRenewal failure alarms CV464
PKI Connector returns 'Server not responding' when executing
NA14868638 CV464
an integration Test
Parameters 'SRTP Keymode' & 'SDP mode' not editable in
NA15136193 CV464
Template Mode for the CP family of devices
NA15076169 Check DLS mobility items being sent after phone registration CV464
NA15036838 Problems with JHPT and OpenStage 15 Devices CV464
Error message: 'PKI0002: Plug-In properties may not be
NA15024819 CV464
accepted' when attempting to sync to an MS CA
NA14988385 DLS Element Manager synchronization CV464
Tenants not available when login to DLS through SSO from
NA14916030 CV464
CMP
Cannot "force" S/W Deployment to use OSB via Location's
NA14853726 CV464
option 'Use OSBranch for Software Deployment'
'OpenScape Fusion for Office' device type not offered for
NA15149858 CV464
Profiles
NA15146611 False SPE certificate issued by DLS for HG3500-BG OS4K CV464
NA15134187 Certificate AutoRenewal not functioning CV464
NA15134132 File Deployment handling when adding contents CV464

Release Note page 19 (of 25) Openscape Deployment Service V7R3

6 Hardware and software compatibility
This section lists the hardware and software requirements. DLS is marketed only as a software product.
Consequently, the individual sales branch or the customer is responsible for the hardware and any third-party
hardware used for this solution.
In order to guarantee a high level of availability and resilience for our customers, SSDP and DLS should be
integrated in the customer environment.
Note: Only one DLS is permitted per domain.

6.1 Hardware requirements

6.1.1 Minimum Hardware Requirements for a DLS Server in a Single Node

(standalone) Deployment
DLS Standalone
CPU 3.1 GHz CPU (Intel Xeon E3-1220, 4C/4T)
RAM 8 GB
Ethernet 100 MBit (1GBit is recommended)
Disk Space 80 GB

Reference Server:
PRIMERGY RX100 S7
Intel Xeon E3-1220 4C/4T 3.10 GHz 8 MB , 8 GB DDR3 1333

6.1.2 Minimum Hardware Requirements for a DLS Server in a Multi-Node

Deployment
DLS Multi-Node
CPU Intel Xeon Quad Processor >= 2.9 GHz
RAM 8 GB
Ethernet 100 MBit (1GBit between the servers)
Disk Space 300GB

6.1.3 Minimum Hardware Requirements for an MSSQL Database Server

Database Server
CPU Intel Xeon Quad Processor >= 2.9 GHz
RAM 8 GB
Ethernet 100 MBit (1GBit between the servers)
Disk Space 80 GB

6.1.4 Minimum Hardware Requirements for an MSSQL Witness Server

Witness Server
CPU Intel Dual Core Processor
3 GHz

Release Note page 20 (of 25) Openscape Deployment Service V7R3

 RAM 2 GB
Ethernet 100 MBit (1GBit between the servers)
Disk Space 20 GB

6.1.5 Usage of DLS in a VMware environment

Please refer to the latest version of the OpenScape Solution Set Virtual Machine Resourcing and
Configuration Guide.

6.2 Firmware releases

N/A

6.3 Loadware releases

N/A

6.4 Software releases

This release note contains information pertinent to the OpenScape Deployment Service software only. Under
certain situations, additional software products may be required to install and operate. These products are
listed in the following table, which also includes the respective versions required to use with the current DLS
version and the location of their respective Release Notes in G-DMS where applicable. List below contains
also software modules installed automatically by DLS.

Product Software Version Release Date G-DMS Note

Software Modules included with this DLS load (some may require manual installation):
Tomcat V6.0 -
JRE IBM V1.7.x -
V3.5.1 (not incl. in DLS load but is a
.NET Framework -
prerequisite)
Microsoft Installer V4.5 (plus hotfixes) -
2008 R2 Express Edition (not incl. on
DLS load but is a prerequisite)
MS SQL -
2012 Express Edition (not incl. on DLS
load but is a prerequisite)
MS JDBC driver V3.0 -
SSDP Service Plugin
(refer to corresponding
V1 R13.0.2 (Windows) 03/31/14
documentation for supported
environments)
Remote Test Tool j-HPT V2R3.1.1 11/09/2014
HiPath License Management –
Customer License Client – CLC Customer Site Components Modular
[OpenScape-onboard / Linux (CSCm)
P30152-P1154-C200-18 -
standalone (SUSE),
MS Windows 32bit and 64bit] V1 R15.0.0 (TB-CCM.10.035)

PostgreSQL Windows x64, x86 9.4.5 -

Postgres JDBC 9.3.1101 -

Note: When 3rd party applications are to be installed separately, please consult the corresponding individual
software documentation for any applicable restrictions and limitations. All JRE vulnerabilities and future

Release Note page 21 (of 25) Openscape Deployment Service V7R3

corrections to those are solely a 3rd party Java topic and a customer's maintenance responsibility task in a
similar manner to Microsoft Operating System hotfixes or SQL fixes.

6.5 Operating systems (including security alerts)

All servers (DLS, Witness, Mirror) must be installed with Windows 2008 R2 / 2012 R2 (64-bit) Standard,
Enterprise or Datacenter Edition. The latest service packs and security patches must be installed.

6.5.1 Database
Since CV464 Single node DLS with MSSQL with local and remote DB deployments are replaced by Single
node DLS with PostgreSQL (wich is a local DB deployment only). MSSQL is supported in Multinode DLS
only.
Microsoft® SQL Server™ 2008 R2 or 2012 Enterprise Edition can be used for Multinode DLS
deployments, but requires 4 GB or 6 GB respectively. This database must be provided by the customer!
Since V6R1, DLS supports Microsoft® SQL Server™ 2008 R2 Datacenter Edition. This database must be
provided by the customer!
For usage of Microsoft SQL 2008 R2 or 2012 Enterprise or Datacenter Edition appropriate Microsoft
licences are needed. As a rule CPU licenses should be used, usage of device CAL 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.

6.5.2 Operating Systems and Client PC Requirements

Operating System Name / Client PC Requirement Operating System / PC Requirement Version
Servers:
DLS-Standalone/DLS-TAP:
 MS Windows 2008 Server Enterprise/Standard SP1, SP2 (x86 and x64) plus R2 (64bit)
 MS Windows 2012 R2 Server R2 (64bit)
Enterprise/Standard
Clients:
Service Packs:
Any Windows desktop version still officially
all available SPs
supported by Microsoft up to release of this DLS
Hot fixes:
load.
all available Security & Update Patches
Web Browser: Any browser
Java Runtime Environment minimum requirement JRE 1.7

6.6 Compliant products (compatibility matrix)

Hardware and software products that have been tested together with Deployment Service, including third-
party products, are listed in the following table, which also includes the respective versions required to use
with the current Deployment Service software and the location of their respective Release Notes in G-DMS.

1
Preferred Software Versions
Product Family Product
Version Status G-DMS Note
V9 R0.8.3 &
OpenScape Voice V9 GA
Applications V9 INF-16-000200

V8 R1.39.3 &
OpenScape Voice V8R1 GA INF-15-000290
Applications V7R3
OpenScape Voice
V8R0 PS34E03 &
OpenScape Voice V8R0 GA INF-15-000062
Applications V7R2

V7R1 PS42E02 &

OpenScape Voice V7R1 GA INF-15-000004
Applications V7R1

Release Note page 22 (of 25) Openscape Deployment Service V7R3

 1
Preferred Software Versions
Product Family Product
Version Status G-DMS Note
OpenScape Voice V6 Not Released - -
OpenScape 4000 V7R1 V7R1.39.0 GA INF-15-000156
OpenScape 4000 V7R0.12.0 and V7 INF-14- 000077
OpenScape 4000 V7 GA
Specific LW Hotfix 3 HF003682
OpenScape Meta V7 CV014 HF4 (V7
OpenScape 4000 Manager V7 GA
Management R0.14.4)
V6 R2.16.0 and V6
HiPath 4000 HiPath 4000 V6R2 GA
Specific LW Hotfix 1
HiPath Meta
HiPath Manager V6 V6 R2.51.5 GA
Management
HiPath 3000 V9R2
HiPath 3000 Latest GA GA
(via HG1500)
HiPath 3000 V8R5
Latest GA GA
(via HG1500)
OpenScape Business OpenScape Business V2 R0.x GA
OpenScape Office OSO (MX/LX) V3 PSR
OpenStage 5, 15, 20, 20E, 40, 40
OpenStage V3R0 HFA V3 R0.16.0 GA
US, 60, 80
DeskPhone IP 35G, DeskPhone IP
35G Eco, DeskPhone IP 55G

OpenStage 5, 15, 20, 20E, 40, 40

US, 60, 80

OpenScape Desk Phone CP200,

CP400, CP 600 SIP and HFA
SIP & HFA
Optipoint 400, 410, 420, 600,WLAN General Availability in
Clients and Devices SWS (please also
GA
consult the relevant
OptiClient 130 Solution RNs)

AC – Win

OpenScape Personal Edition (V4 or

latest)

Secure Enterprise Service and

V1.0 R2 and higher
Administration Platform (SESAP) GA
Secure Management
HiPath SPA Manager (HiSPA V1.0) V1.0 R3.88.0 and
GA
P30357-V7800-M110-1 and higher higher
OpenScape License Management GA
V1 R28.0.0 Windows
CLA GA
Licensing
OpenScape License Management GA
V1 R14.0.0 Windows
CLM GA
As per
As per relevant relevant
Common Management As per relevant Application Release
Application Release Application
Portal (CMP) Notes
Notes Release
Notes
SQL SERVER 2005 (SP1 to 4) SQL Server 2008 or R2
MS SQL GA
Enterprise edition Native Client
SQL SERVER 2008 (SP1,2,3) SQL Server 2008 or R2
GA
Enterprise edition Native Client

Release Note page 23 (of 25) Openscape Deployment Service V7R3

 1
Preferred Software Versions
Product Family Product
Version Status G-DMS Note
SQL SERVER 2008 R2 (SP1,2) SQL Server 2008 or R2
GA
Enterprise edition Native Client
SQL SERVER 2012 Enterprise SQL Server 2012
GA
edition Native Client

Notes:
1
We recommend customers to use the “Preferred Software Version” for the given products. The preferred
software versions offer higher levels of functionality.

Release Note page 24 (of 25) Openscape Deployment Service V7R3

7 Service information

7.1 Management information base

Product forwards SNMP traps according to a MIB:

7.2 License management

This product is certified for the following:

CLS: CSC: Other Licensing: If you are using others, please describe below:
Attachment
N/A

Release Note page 25 (of 25) Openscape Deployment Service V7R3