ODCPE V7R1.47.92 ReleaseNotes 2.07

Public
Release Notes
Release Notes Version: V2.07, 2022-11-11
Atos Unify OpenScape Desktop Client Personal Edition V7

Software Version: V7 R1.47.92
☐ Major Release ☐ Minor Release ☒ Fix Release ☐ Hotfix Release
Current release status can be verified via the Software Supply Server (SWS)
Deliverables
☒ Full Release ☐ Delta Release
Export Control Classification Data

AL: 5D002C1A ECCN: 5D002ENCU
© Copyright 2022, Unify Software and Solution GmbH & Co. KG All rights reserved.
This document provides general information about the release, generics, and other relevant notes for the corresponding product
and its correction versions.
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.
Atos, the Atos logo, Atos|Syntel are registered trademarks of the Atos group. © 2022 Atos.
Confidential information owned by Atos, to be used by the recipient only. This document, or any part of it, may not be
reproduced, copied, circulated and/or distributed nor quoted without prior written approval from Atos.
Atos Unify OpenScape Desktop Client Personal Edition (ODC-PE) V7 R1.47.92
Table of Contents
1 HISTORY OF CHANGE ............................................................................................. 3

1.1 RELEASE NOTES CONTENT........................................................................................ 3
1.2 PRODUCT VERSIONS HISTORY .................................................................................... 3
2 CHANGES ............................................................................................................ 5
2.1 IMPLEMENTED CHANGE REQUESTS / NEW FEATURES.......................................................... 5
2.2 RESOLVED REPORTED PROBLEMS / SYMPTOMS .............................................................. 10
2.3 RESOLVED VULNERABILITIES ................................................................................... 11
3 IMPORTANT ISSUES, WORKAROUNDS, HINTS AND RESTRICTIONS ................................ 12
3.1 IMPORTANT ISSUES ............................................................................................. 12
3.2 WORKAROUNDS, HINTS ........................................................................................ 13
3.3 RESTRICTIONS ................................................................................................... 14
4 INSTALLATION AND UPGRADE / UPDATE ................................................................. 25
4.1 INSTALLATION ................................................................................................... 25
4.2 UPGRADE / UPDATE / MIGRATION ............................................................................ 33
4.3 SPECIAL SETTINGS AND INSTRUCTIONS ........................................................................ 35
5 HARDWARE AND SOFTWARE COMPATIBILITY ........................................................... 56
5.1 HARDWARE...................................................................................................... 56
5.2 FIRMWARE....................................................................................................... 57
5.3 LOADWARE ...................................................................................................... 57
5.4 SOFTWARE / APPLICATIONS ................................................................................... 57
5.5 OPERATING SYSTEMS ........................................................................................... 57
5.6 COMPLIANT PRODUCTS ......................................................................................... 57
6 SERVICE INFORMATION ........................................................................................ 61
6.1 MANAGEMENT INFORMATION BASE ............................................................................ 61
6.2 LICENSE MANAGEMENT ......................................................................................... 61
6.3 REMOTE SERVICEABILITY ....................................................................................... 61
6.4 PRODUCT TOOLING STRUCTURE ................................................................................ 61
6.5 CASE TRACKING SYSTEM ........................................................................................ 61
7 DOCUMENTATION REFERENCE ............................................................................... 61
8 REFERENCES ...................................................................................................... 61
Release Notes Page 2 of 61

1 History of Change
1.1 Release notes content
Version Date Description of changes
2.00 2022-05-13 Released new ODC-PE V7 R1.47.88 eeQA/Pilot usage.
2.02 2022-06-15 Added info about configure TLS protocol via PE settings (chapter 2.1).
2.04 2022-07-29 Add regedit key for specific Scenario related to Genesis WDE (chapter 3.1.3).
1.2 Product versions history

Software Version Production Version Date Remarks
V7 R1.47.14 70.1.47.0014 2016/02/18
V7 R1.47.15 70.1.47.0015 2016/03/30
V7 R1.47.17 70.1.47.0017 2016/04/29
V7 R1.47.19 70.1.47.0019 2016/06/10
V7 R1.47.23 70.1.47.0023 2016/07/08
V7 R1.47.26 70.1.47.0026 2016/08/04
V7 R1.47.27 70.1.47.0027 2016/08/29
V7 R1.47.28 70.1.47.0028 2016/10/03
V7 R1.47.30 70.1.47.0030 2016/11/11
V7 R1.47.33 70.1.47.0033 2016/12/21
V7 R1.47.35 70.1.47.0035 2017/03/17
V7 R1.47.36 70.1.47.0036 2017/04/13
V7 R1.47.37 70.1.47.0037 2017/06/01
V7 R1.47.38 70.1.47.0038 2017/07/07
V7 R1.47.40 70.1.47.0040 2017/09/01
V7 R1.47.41 70.1.47.0041 2017/09/14
V7 R1.47.43 70.1.47.0043 2017/11/24
V7 R1.47.44 70.1.47.0044 2017/12/21
V7 R1.47.45 70.1.47.0045 2018/02/16
V7 R1.47.46 70.1.47.0046 2018/03/16
V7 R1.47.48 70.1.47.0048 2018/04/27
V7 R1.47.49 70.1.47.0049 2018/05/24
V7 R1.47.50 70.1.47.0050 2018/06/14
V7 R1.47.53 70.1.47.0053 2018/07/13
V7 R1.47.54 70.1.47.0054 2018/08/10
V7 R1.47.55 70.1.47.0055 2018/10/04

Software Version Production Version Date Remarks

V7 R1.47.56 70.1.47.0056 2018/11/29
V7 R1.47.58 70.1.47.0058 2019/01/21
V7 R1.47.59 70.1.47.0059 2019/03/19
V7 R1.47.60 70.1.47.0060 2019/05/17
V7 R1.47.61 70.1.47.0061 2019/05/28
V7 R1.47.62 70.1.47.0062 2019/07/12
V7 R1.47.63 70.1.47.0063 2019/08/09
V7 R1.47.64 70.1.47.0064 2019/08/27
V7 R1.47.65 70.1.47.0065 2019/09/24
V7 R1.47.66 70.1.47.0066 2019/11/13
V7 R1.47.67 70.1.47.0067 2019/12/20
V7 R1.47.68 70.1.47.0068 2020/02/03
V7 R1.47.69 70.1.47.0069 2020/03/13
V7 R1.47.70 70.1.47.0070 2020/03/25
V7 R1.47.71 70.1.47.0071 2020/05/13
V7 R1.47.72 70.1.47.0072 2020/06/09
V7 R1.47.73 70.1.47.0073 2020/08/14
V7 R1.47.74 70.1.47.0074 2020/11/13
V7 R1.47.75 70.1.47.0075 2020/12/02
V7 R1.47.76 70.1.47.0076 2021/01/15
V7 R1.47.77 70.1.47.0077 2021/02/12
V7 R1.47.78 70.1.47.0078 2021/03/26
V7 R1.47.79 70.1.47.0079 2021/04/30
V7 R1.47.80 70.1.47.0080 2021/05/28
V7 R1.47.81 70.1.47.0081 2021/07/16
V7 R1.47.82 70.1.47.0082 2021/08/20
V7 R1.47.83 70.1.47.0083 2021/09/17
V7 R1.47.84 70.1.47.0084 2021/10/29
V7 R1.47.85 70.1.47.0085 2021/12/10
V7 R1.47.86 70.1.47.0086 2022/01/25
V7 R1.47.87 70.1.47.0087 2022/02/16
V7 R1.47.88 70.1.47.0088 2022/05/13
V7 R1.47.89 70.1.47.0089 2022/06/14
V7 R1.47.90 70.1.47.0090 2022/08/26
V7 R1.47.91 70.1.47.0091 2022/09/29
V7 R1.47.92 70.1.47.0092 2022/11/11
Note: List of all released software versions since [major] or [minor] software release in SWS.

2 Changes
2.1 Implemented Change Requests / New features
Tracking Internal Summary Released

Reference Reference in Version
UCBE-23102 Allow manual configuration TLS transport protocol in PE. V7 R1.47.89
RQ00042977 UCBE-30025 Emergency Call Disclaimer feature active by registry key V7 R1.47.88
RQ00042977 UCBE-29344 Emergency call disclaimer should be presented. V7 R1.47.88
RQ00042675 UCBE-27287 OS Personal Edition Diversion Header Support. V7 R1.47.83
RQ00042761 UCBE-27137 Disable the “hold” button present on the window of OS V7 R1.47.81
Personal Edition.
RQ00042674 UCBE-26493 Discrete notification about central DLS changes. V7 R1.47.81
RQ00042410 DLS provisioning for Local Journal Provider (PE side) V7 R1.47.78
RQ00042412 WhiteNoise in HKEY_CURRENT_USER - Part2 V7 R1.47.78
RQ00042559 Disable PE device features via DLS V7 R1.47.78
RQ00042553 Disable PE desktop notifications via DLS (PE side) V7 R1.47.77
RQ00042333 Auto profile creation for OpenScape Desktop Client V7 R1.47.77
RQ00042412 WhiteNoise in HKEY_CURRENT_USER V7 R1.47.77
UCBE-25309 Project: split channels - SETUP changes. V7 R1.47.75
UCBE-25305 Project: split channels. V7 R1.47.75
UCBE-23059 ODC-PE support for the NG112 project. V7 R1.47.72
UCBE-19700 Silent Monitoring with Whisper. V7 R1.47.61
UCBE-15931 ODC PE should support Tel URI protocol. V7 R1.47.50
RQ00041355 Change number of characters for Digest Authentication. V7 R1.47.49
UCBE-10524 Project: ODC-PE - Basic uaCSTA support. V7 R1.47.38

Tracking Internal Summary Released

Reference Reference in Version
UCBE-10525 Project: ODC-PE - Distinctive Ringing. V7 R1.47.38
UCBE-10526 Project: ODC-PE has to run in the background (no GUI). V7 R1.47.38
UCBE-10529 Project: ODC-PE - License Mechanism. V7 R1.47.38
UCBE-11108 ODC PE: SoftOla TLSv1.2 support - OSBiz. V7 R1.47.38
DCMP Support V7 R1.47.28
FRN10072 UC Softphone: Support of Sennheiser Headsets V7 R1.47.15
FRN9838 UC Clients: Support JabraUSBHidTelephonySDK_V1.0 V7 R1.47.15
UCBE-53 Clients Support of Windows 10 V7 R1.47.15
UCBE-50 softphone support new Plantronics Spokes 3.0 interface. V7 R1.47.15

2.1.1 Manual configuration of TLS protocol via ODC-PE (HFA Stackless).

A new feature was implemented since version V7 R1.47.89: Manual configuration of TLS transport
protocol via ODC-PE GUI (HFA Stackless).
Such new feature has the objective to allow the User to manually configure the use of TLS transport
protocol via ODC-PE GUI settings (more precisely for HFA Stackless).
That’s because with problems of Covid, we have a lot of customers configuring ODC-PE to be used as
SRS client on the OS4K.
The greatest challenge for them here, is that a DLS is needed to allow TLS functionality for ODC-PE
(since SRS only works with TLS).
Considering standard Unify devices can have transport protocol and port configured to use TLS, was
decided that it would be a good enhancement to allow local configuration of TLS for HFA Stackless
(effectively port 4061 instead of 4060).
Example:
Figure 1. Example of Local/Manual TLS transport protocol configuration via ODC-PE settings GUI

2.1.2 Emergency call disclaimer
A new feature was implemented since version V7 R1.47.88: Emergency Call Disclaimer.
Such new feature has the objective to inform all users that ODC-PE should not be used to make
emergency calls.
That’s because doing so might result in the call not being routed properly to emergency service
provider or provide incorrect location information.
Also, we recommend (if necessary) to use a land line or mobile phone to make an emergency call.
The warning window will be presented at every ODC-PE start until user accepts the disclaimer by
checking "Accept" box.
Example:
Figure 2. Example of Emergency call Disclaimer

Activation:
By default, it’s not active such feature.
To enable/active the Emergency Call Disclaimer feature a registry key should be created.
It should be a DWORD 32-bit named "ShowEmergencyCallDisclaimer" with value=1.
(64 bit) regedit ➔ HKLM\Software\WOW6432Node\Siemens\OpenScape
(32 bit) regedit ➔ HKLM\Software\Siemens\OpenScape
PS: The same warning window can be seen via ODC-PE systray menu ➔ About ➔ Emergency call
Disclaimer (even after user has accepted it).
Example:
Figure 3. Example of Emergency call Disclaimer

2.2 Resolved Reported Problems / Symptoms
Tracking Internal Summary Released in

Reference Reference Version
PRB000062606 UCBE-31379 ODC-PE frequently without payload. V7 R1.47.92
PRB000060704 UCBE-30860 ODC-PE: Client with DLS no longer stores local contacts V7 R1.47.92
and call journal.
UCBE-31413 ODC-PE: Sennheiser audio scheme is removed after V7 R1.47.92

update.
UCBE-31390 ODC-PE: SecomSDK.exe is not started in some computers. V7 R1.47.92
PRB000060651 UCBE-30855 ODCPEV70R1.47.88 problem when using multiple monitors V7 R1.47.91

with different scaling size.
PRB000059401 UCBE-30395 ODC-PE: Scale size from windows display (125%) flickering V7 R1.47.91
in some sections/buttons on Pearl GUI.
PRB000056206 UCBE-30944 For ODC-PE as UFIP in OS4K V8R2 the SA (hunt group) V7 R1.47.91
login/logoff function does not work.
UCBE-30962 After activating secure mode with PIN in DLS, PIN entry is V7 R1.47.91
not required at any time. ODC PE opens the application
normally.
UCBE-31186 ODC PE terminates the application after configuring the V7 R1.47.91
DLS server for use.
ODC-PE: newer versions (like V7 R1.47.80 and V7 R1.47.88) V7 R1.47.90

has a PAYLOAD missing first 1-2 seconds spoke during
PRB000059274 UCBE-30420
incoming calls (old version like V7 R1.47.67 does NOT have
problem).
ODC-PE: Call Forward display signaling continues after V7 R1.47.90
PRB000060485 UCBE-30791
CFU deactivated (within PE MainBar's Display).
PRB000055141: ODC-PE Directory search with "ü" is not V7 R1.47.90

PRB000055141 UCBE-30894
working.
Allow manual configuration of TLS transport protocol in V7 R1.47.89

UCBE-23102
PE.
ODC-PE shows "Sammelanschlus" instead "Hunt Group" in V7 R1.47.89

UCBE-29956
PRB000058078 ODC-PE English.
CLONE - ODC-PE: Poly Calisto 5300: Ringtone is not V7 R1.47.89

UCBE-30218
played in this speaker audio device.

Tracking Internal Summary Released in

Reference Reference Version
No RTP packets after MUTE was pressed => leads to V7 R1.47.88
PRB000058007 UCBE-29878
connection clearing by provider.
Genesys agent cannot retrieve the call from hold if the V7 R1.47.88
PRB000057605 UCBE-29767
hold was initiated from ODC-PE.
Checking and clarifying dependency with Visual C++ 2010 V7 R1.47.88

PRB000057585 UCBE-29763
Runtime (EOL in 2020).
PE cannot retrieve the call from hold if the hold was V7 R1.47.88
PRB000056995 UCBE-29607
initiated from Genesys.
PRB000056265 UCBE-29583 After logging (to PE), a TSP error occurs. V7 R1.47.88
V7 R1.47.88
PRB000055872 UCBE-29154 OCS file Export/Import problem with LDAP PASSWORD.
PE after deactivating the local function "second call" via V7 R1.47.87

PRB000055875 UCBE-29157
DLS , no busy signal is played (if a direct call to the agent).
Problem with OpenScape Desktop Client on Display with V7 R1.47.87

PRB000055760 UCBE-28753
2560-1440 pixel
PE Client Crashes all the time even in IDLE state (ALL V7 R1.47.87
PRB000055840 UCBE-29173
Users/PCs with this crash).
PRB000055698 UCBE-29058 ODC-PE: Digital Signature expired. V7 R1.47.86
PRB000055566 UCBE-28961 ODC PE is using unsecure log4net.dll 1.2.13.0. V7 R1.47.86
PRB000055760 UCBE-28753 Problem with OpenScape Desktop Client on Display with V7 R1.47.86
2560-1440 pixel
PRB000054573 UCBE-28293 PE not follows RFC2833: DTMF tones transmission from V7 R1.47.86
the PE client to the UC Suite does not work.
V7 R1.47.85
PRB000054541 UCBE-28122 ODC-PE with startup/registrar problem.
ODC-PE incoming call tone control failure if auto answer is V7 R1.47.85

PRB000054988 UCBE-28537
used.
ODC-PE No discrete notification when changing job via V7 R1.47.85

PRB000054301 UCBE-28182
DLS.
2.3 Resolved Vulnerabilities

Not applicable for this release.

3 Important Issues, Workarounds, Hints and Restrictions

This section provides the latest information at time of software release and is only pertaining to the
time of release notes generation.
3.1 Important Issues

For all following issues, there is no need to open PRB tickets (issues already under investigation by
Dev Team to fix asap):
Tracking Internal Summary
Reference Reference
UCBE-30963 After change parameter in the DLS, sporadically ODC-PE does not receive
restart popup.
Workaround: After restart ODC-PE any new parameters will be downloaded

from DLS as expected.
3.1.1 Regarding Citrix VDI

o This version of ODC-PE supports VDI functionality.
o Restriction: Direct upgrade of current ODC-PE VDI softphone component over version V7 R1.47.10
(or older) is not supported.
Due that:
Old ODC-PE VDI softphone V7R1.47.10 (or older) must be removed prior install new ODC-PE VDI
softphone.
o Direct upgrade of this ODC-PE VDI softphone component over last GA version is supported.
o OpenScape 4K V7 R2 is supported for SIP provider.
3.1.2 Regarding HFA H323 / HFA Stackless

HFA (H323) is not supported anymore by ODC-PE.
Since ODC-PE V7 R1.46.10 (and newer), the only supported variant of HFA is the HFA Stackless.
Since version V7 R1.47.26 the ODC-PE also supports OpenScape 4000 with HFA Stackless.
The PBX list with supported HFA Stackless:

- OpenScape 3000
- OpenScape Office
- OpenScape Business
- OpenScape 4000 (since version V7 R1.47.26)
Resuming: Any/all other kind of HFA (not Stackless) is NOT supported!!

3.1.3 Regarding Genesys WDE (retrieving a call on hold via ODC-PE)

(Based on PRB000056995) if a customer (that is using Genesys WDE) and he wants to retrieve (from
ODC-PE) a call put on hold by Genesys, there is only one way to activate such functionality.
For this a DWORD named "GenesysHoldRetrieve" with value "1" needs to be added under
"HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Siemens\OpenScape".
IMPORTANT: To not break all other existing scenarios, this functionality can only be enabled via a
Windows registry change. And should ONLY be done/used by Customer that really wants such
behavior.
IMPORTANT: This key will only work if configured at PCs with ODC-PE V7 R1.88 (and newer),
3.2 Workarounds, Hints
3.2.1 Revoked Workarounds

3.2.2 Workarounds
3.2.3 Hints

3.3 Restrictions
3.3.1 New, Permanents or still valid ones
• EPOS / Sennheiser:
Since ODC-PE V7 R1.47.92 and newer, was removed from Personal Edition setup the
EPOS / Sennheiser SDK (also known as SecomSDK).
Customers/Users that intend to use such brand audio Devices must download/install
(from vendor site) the newest version of EPOS Connect:
https://www.eposaudio.com/en/ch/enterprise/software/epos-connect
Problem Description
When EPOS/Sennheiser audio devices are used, the PE client integration has
historically worked with either the EPOS Connect software (preferred way) or with an
old software development kit (SDK) provided by Sennheiser long ago (fallback way).
Recent Microsoft Windows updates have created some incompatibilities for the old SDK,
which is no longer supported by EPOS/Sennheiser. Therefore, the fallback way has
been removed.
As of the new Personal Edition release, the use of EPOS/Sennheiser audio devices
requires the EPOS Connect software for the integration to work.
Users with such Audio Devices, that do not install the new EPOS Connect will have their
Personal Edition Audio Schemes unavailable to use.
To fix that either:
=> install the new EPOS Connect
or
=> change the controller to SoundCard
(but this way lost control of Audio Device buttons).
Affected Product and Software Releases

As of OpenScape Desktop Client Personal Edition V7 R1.47.92 (and newer versions), the
use of EPOS/Sennheiser audio device requires the EPOS Connect software (or any
other software recommended by the vendor) to be installed on the client machine.
Permanent Solution (for users with EPOS/Sennheiser Audio Devices)

The use of the EPOS Connect software is anticipated to be the permanent solution.
The availability and ongoing support of this software is the responsibility of the vendor.
IMPORTANT: The ODC-PE client does not start new EPOS Connect software, nor any
utilities associated with the Connect software. It is necessary to install and launch the
EPOS Connect Software separately.
Impact of Taking No Action

Starting with ODC-PE V7 R1.47.92 (and newer), the integration with EPOS/Sennheiser
audio devices will not work unless the EPOS Connect software (or any other software
recommended by the vendor) is installed on the client machine.

• Resolution & Windows scales

Not new, but sometimes Users forget these mandatory steps: If/when User attempts to
change the Windows Resolution and/or Windows Scales, its mandatory to do it in the
following sequence:
#1: CLOSE ODC-PE (prior any changes on resolution and/or Windows scales like change
to 125%).
#2: Change to what is desired (example Windows scale from 100% to 125%)
#3: Restart ODC-PE
• ODC-PE with other Clients

This is NOT possible.
Due the same question appears quite often; this restriction will be kept here on top from
now.
It is NOT possible to install ODC-PE in case any of the following is already installed:
OpenScape Fusion (for Office or for Notes) V1 or V2 (F4O V1 or F4O V2)
OpenScape Client Integrations
OpenScape Desktop Integration Tool (Di-Tool)
OpenScape Desktop App (DeskApp)
So, it is required to uninstall the previous installed OpenScape application prior ODC-PE.
• ODC-PE + Notes installation FAILS / ABORT:

Not a new restriction, but also because some Customers seems to forget, so adding here
the info to help Service/Customers remember that:
Sometimes ODC-PE + Notes installation fails when Customer forgets about grant
permissions to User running the installation.
So:
The user running the installation MUST HAVE sufficient permission to allow ODC-PE
installer complete access/permissions at...
C:\Program Files\Notes (when Customer has Notes installed)
C:\Program Files\
C:\
• OpenSSL 1.0.2r
Since PE V7 R1.47.77 was implemented, security uses OpenSSL version 1.0.2r.
• VDI/CITRIX:
This is not a new restriction. Just to make it clear (due some questions from Customers),
what ODC-PE does supports (or not) now:
▪ ODC-PE SIP ONLY supports CITRIX in VDI mode (media offload).
▪ ODC-PE HFA does NOT support any scenarios.
IMPORTANT: be aware that newer versions (of Citrix Receiver) have changed the app
name to Citrix WorkspaceApp (but the instructions/steps are the same as for Citrix
Receiver named app).
• Windows “Modern StandBy” feature:
Windows 10 Modern Standby expands Win 8.1 Connected Standby power model.

Both models enable an <instant on / instant off> user experience, like smartphone
power models.
Since MS(Windows) does not inform other apps that computer is going to enter/leave
such power mode ➔ Other apps (such ODC-PE) is unable to react to it (breaks SIP/HFA
registration handling).
IMPORTANT: Since this is a Microsoft restriction; same restrictions apply also to older
ODC-PE versions. Therefore, our recommendation is to Disable Modern Standby mode.
Tickets of problems caused directly by Modern Standby mode will be refused.
PS: Hopefully, Microsoft will review the chosen behavior in a near future, since this may
affect not only OpenScape/Unify solutions, but also other Realtime applications.
More details about “Modern StandBy” feature:
Figure 4. Changed of Legacy Standby (Win8) to new “Modern StandBy” (Win10).
S0 state
With Modern Standby (with Win10) a system stays in the S0 state and waking simply
requires a hardware interrupt. Thus, it may eliminate any need for firmware interaction.
Win8.1 Connected Standby systems wakeup at least once every 30 sec to process work.
How to Control/Disable Modern Standby:

If you're using a Windows 10 with Modern Standby, you can switch between
Connected Standby and Disconnected Standby in the System Settings menu. Select:
- The Power and Sleep tab under System Settings, and
- uncheck 2 boxes under "Wi-Fi": that allow PC to stay connected in sleep mode.
Also, it’s possible a more direct way (if you have permissions), via regedit:
Try the following steps below to disable the Modern Standby:
1. On the search bar, type "Registry Editor" and click on it.
2. Navigate to:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Po
wer
3. Double Click on "CsEnabled" and change the data value to 0
4. On the search bar, type "Command Prompt" (or just “cmd”)
5. Type "powercfg /a", then hit Enter and check the provided results/settings.

Example:
Figure 5. new “Modern StandBy”(Win10) => Checking status/settings.

• ODC-PE + VDI + DLS
Check subchapter 4.1.7.4 for more infos about ODC-PE in combination with VDI and DLS.
• Auto Answer feature

PS: Not new feature, but due frequent questions, its here for a quick overview.
PE supports “AutoAnswer” feature. However, it’s used only in CSTA MakeCall requests.
I.e., when user makes outgoing call via CTI application, OSV sends a SIP INVITE with the
“info=autoanswer”
attribute in the “Alert-Info” header (also known as “3PCC Call” or “CTI Assisted Call”).
ODC-PE reacts to it by replying with a 200 OK (instead of a 180 Ring).
ODC-PE has no setting to allow user to disable the “AutoAnswer” handling. Differently
from the OpenStage (which provides such setting), on ODC-PE, the “AutoAnswer”
handling is always active.
In case ODC-PE has an incoming ringing call, and the user answers it via a CTI application,
the OSV sends a NOTIFY with the “Event: talk” and then ODC-PE replies with a 200 OK.
PS1: note it is a “CSTA AnswerCall” scenario, which has nothing to do with “AutoAnswer”
feature.
PS2: If what Customer seeks is a way to auto answer any incoming call (no CSTA
monitoring), unfortunately ODC-PE does NOT support it.
• New Feature “Disable Local Features via DLS”

Since version V7 R1.47.78 the ODC-PE supports/allows to disable local features via DLS.
PS: Such new feature does NOT support the ODC-PE VDI (for the moment).
• Audio Devices problems

Since PE V7 R1.47.76 was implemented improve/fixes regarding Audio
Devices/Schemes. Due that new PRB Ticket (prior open), must be (also)
tested/collected logs from PE V7 R1.47.76 (or newer).

• Resolution 4K
Since the V7 R1.47.75 we had improves/fix done regarding High Resolutions up to 4K,
but to proper work, the process of changing Windows resolutions must be:
▪ First: CLOSE ODC-PE;
▪ Second: Change the Resolution (up to 4K) and Scale font;
Scale font, to avoid problems please use the recommend by Windows);
▪ Third: Starts ODC-PE => The Client then should displays contend accordingly.
• SIP diversion header

PE doesn’t support information display provided via SIP diversion header in Toaster &
Call Control.
• “OptiSet” models can NOT be used anymore

From ODC-PE V7 R1.47.71 forward the ODC-PE HFA STACKLESS can NOT be configured
to work as an OptiSet telephone model. The reason for that is that the OS4K V10 and
forward does not support any more such old telephone model.
So, do not select it (during configuration) since you may have problems within OS4K.
Example of models that should not to be use:
Figure 6. Example of not valid telephones models.

• “Free SIP” mode removed
From ODC-PE V7 R1.47.71 forward the “Free SIP” mode is disabled/removed due
company decision.
• CLA/CLM versions
Due released new versions of CLA/CLM (LICENSES), any older versions mentioned here
(mentioned before here or by other older Release Notes) were set to obsolete within
SWS.
Minimum versions GAs (equal or newer)
CLA: V1R42.0.0 CLA: V1R43.0.0
CLM: V1R21.0.0 CLM: V1R22.0.0
• WARNING about LDAP / LDAPS

From ODC-PE V7 R1.47.67 forward will support LDAPS (LDAP SECURE mode TLS).
• DLS Bootstrapping and Secure Mode

ODC-PE now supports the DLS feature “Bootstrapping and Secure Mode”.

• VDI/CITRIX:
Tce PE V7 R1.47.60 release the Client brings a new CLC (V2R20.0.0).
This new CLC is based on company ideas to use only TLS 1.2 without.
The CLC (Customer License Client API) was upgraded to provide better security.
Because of that, the CLA must be updated to V1 R42.0.0 or greater.
Currently, the implemented security uses OpenSSL version 1.0.2r.
So far, there are no plans to migrate to OpenSSL 1.1.1.
• TLS 1.2
By default, only TLS 1.2 should be enabled.
However, customers are able to enable the fallback to TLS 1.1 and 1.0 via Windows
registry key:
Creating a DWORD named "EnableTls11AndTls10", with value "1", under
"HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\OpenScape"
• TABLET
The ODC-PE does NOT support any type of Tablet or similar devices.
ODC-PE only supports PCs Desktops with Windows 10 and Notebooks/Laptops with
Windows 10.
• Delays for incoming calls

Some Customers could eventually complain about delay during pickup Incoming calls.
Such delays could happen because slow behavior within hardware’s connections like:
- Several network hardware’s (cascade);
- PCs with slow processor.
- PCs with not ideal amount of memory for all applications running at same time of call;
- PBXs with a high use/demand/phones among others.
Due that ODC-PE in large environments could take something between 600ms -1
second.
PS: Some specific situations (like if Hardware/network requirements are met but we
have a re-INVITE with new SDP), could also have delay due ODC-PE.
Resuming: if any Customer/User complains about DELAY for pickup calls:
➔ First it is necessary to be sure/check the real time/delay (via Wireshark):
- IF delay less than a 1 second to establish a call => This is Work as Designed
since its totally normal and expected in such environments.
- IF (the confirmed) delay is over 1 second than please raise a Customer ticket
for DEV.
• Tel URI protocol

Since ODC-PE V7 R1.47.50 the ODC-PE has implemented the Tel URI protocol, to allow
browser application to perform calls using Windows applications registered for this
purpose.
• Concierge attendant
ODC-PE does support (starting with ODC-PE V7 R1.47.48) to be used as device for it.

• IPv6 is not supported.
• Jabra Evolve 65 and Jabra Direct

According to Jabra, the device Jabra Evolve 65 has a glitch.
If both the device and the dongle are connected to the PC, Jabra Direct will always focus
the dongle. Therefore, at the ODC's Audio Scheme settings, the audio scheme for the
dongle (Jabra Link 360) must have higher priority.
• NAT
Since V7 R1.47.28 (or newer) behind a router using NAT is now supported due new DCMP.
• HFA H323 is no longer supported

Since ODC-PE V7 R1.46.10, the only supported variant of HFA is the HFA Stackless.
• Outlook 64 bit
MS Outlook Integration, which enables Outlook Users to deploy features of ODC-PE
(like access to Outlook Contacts by PE to allow names resolution), is NOT supported for
Outlook 64-bit versions.
• Regarding DockStation
▪ During Calls remember to never disconnect Notebook from DockStation => User
should wait until finish the current call BEFORE disconnects (or network errors can
eventually happen).
▪ After “order” notebook to Hibernate/Sleep, do NOT disconnects Notebook from

DockStation =>User should wait a few minutes until process complete BEFORE
disconnects (or network issues can eventually happen).
• Mikey protocol for Video Calls

ODC-PE does NOT support Mikey protocol for Video Calls (so please use SDES instead).
• “Pearl” Module/Window
Pearl is the MAIN and MANDATORY Module. Due that (by System Definition) the ODC-PE
can not run without the PEARL Module active. What User could do is minimize it and/or
resize it.
The optional modules are the internal ones like: Call Control, Contacts, Journal, etc.
• HotKeys
Must not define the function keys [F1] or [F12] as hotkeys (ODC-PE keyboard
Assignments).
Only supported [F2 ... F11] as hotkeys => This is due Operational System restrictions.

• Windows “N” operating systems

The N editions are delivered without Windows Media Player and without media
components.
Due to that some ODC-PE “media related” features (e.g. playing mp3 files as ringtones)
may work.
• Disconnected from LAN/WAN during active Calls

User Computer can NOT be disconnected from LAN/WAN during active Calls.
This could and will have collateral issues that (besides losing for sure the active call itself),
could left the Client on a Network erratic scenario.
• TLS does not play local MoH.
• If subscriber has DMC enabled, all calls are released after to be answered.
• The option “leave the conference” does not work in OSO.
• When transferred call in two steps the call control disappears.
• ODC-PE does not Out-of-Service when/if HG is OUT.
• Call Pickup Beep

The default status is disabled the beep.
To activate the Call Pickup Tone* feature (assuming the ODC-PE is also a member
from the Call Pickup Group) is necessary to add the following keys within regedit:
(64 bit) regedit ➔ HKLM\Software\WOW6432Node\Siemens\OpenScape
(32 bit) regedit ➔ HKLM\Software\Siemens\OpenScape
=> Create a new DWORD(32) with “NoPickupTone“ and value set to 0
=> Create a new DWORD(32) with “PickupToneWhenInCall“ and value set to 1
PS: Call Pickup Tone* feature is the (“beep” sound) that is played to signal the
existence of an Incoming call to any member of current Call Pickup Group.
Figure 7. Example of Call Pickup Tone settings via Regedit.

• The Additional Lines–Deferred Ring option: Once defined such option, the Deferred Ring
forces the ODC-PE waits 5 seconds to start Ringing. This also goes for the Main Line:
Figure 8. Example of Additional Lines window.

Important to notice: That once Deferred Ring option selected, the selected Additional
Line (By Definition) will not have any kind of GUI signalization (not Toaster and neither
Call Control).
To have GUI signal must disable Deferred Ring and select Preferred Line for incoming
Calls.
• Outlook Dial button integration

The previous Outlook Dial button integration may not work as expected for some special
characters (for example like Korean).
The newer ODC-PE versions fixes this but if upgrades from very old versions performed
(not clean install) then it’s possible to some errors continues.
The reason for that is because the file outlook.db3 (that contains the Outlook contacts
cache) has Outlook contacts stored with old format.
To fix (besides with upgrade actions):
It’s necessary to delete manually outlook.db3 so a new file could be created
(automatically) and all contacts stored with the Unicode format.
The steps to be performed in this case are:
1) Close Outlook
2) Install/Upgrade to this new ODC-PE
3) IF problem with Outlook contacts continues, close Outlook and ODC-PE
4) Delete the file “outlook.db3” from folder “%appdata%\unify\openscape”
5) Restart Outlook and ODC-PE client
6) Wait some minutes (need time to recreate file and populate with all
Outlook Contacts – depends directly of number of contacts). After that Dial
should work as expected.
• CFW + SUPPRESSED/RESTRICTED numbers

CFW-U is not working for suppressed/restricted numbers. If you have a telephone
with suppressed/restricted number, the feature CFW-U does not work as expected:
➔ The call is transferred but only shows the incoming call within MainBar
(freephone display) and the CallControl and Toaster does not show anything.

• TLS / SRTP Video

Limitations with TLS/SRTP video: Video conference calls using the video MCU
should not be used. Start the conference calls as audio only.
• Feature AutoSPE not supported

The ODC-PE does not support feature AutoSPE:
The AutoSPE feature is responsible to deploy automatically Certificates to
devices but it’s not implemented within ODC-PE.
So, if User wants to use SPE and activates the AutoSPE ➔ DLS will deploy
Certificates to Telephones Devices but not to ODC-PE ➔ SPE will continue to
work for both (Telephones and ODC-PEs) because PE does not check the
Certificate.
• Device Plantronics DA45

The mute-function integration between Plantronics Devices and ODC-Softphone does
not work all the time for device Plantronics DA45.
Device DA45 will not work mute 100%, because it does not allow to light up the led by
code. It will work if turn on/off mute only via the device DA45 or only via the ODC-PE.
• To guarantee optimal operation and correct display of OpenScape Desktop Client

Personal Edition, make sure that the following settings are fixed:
Font Size Small Fonts (Normal size, 96 dpi).
• Using of USB Hubs

We want to point out that there are several problems with USB hubs, which constrain
the whole workstation and not only the OpenScape Desktop Client Personal Edition. It
could be that you have too low bandwidth for all connected devices, so that single
devices will be taken out of service.
It also could be that you run in CPU performance problems, especially with camera
devices.
If you want to be sure that everything will work, then it is recommended to connect
the USB audio devices and the USB camera devices not via a USB hub, but directly at
a USB I/F connector at the workstation.
• Mobile HFA Logon

The "Mobile HFA Logon" feature is not supported by ODC-PE. For users, who want to
use different phone numbers at ODC-PE, they must work with different user profiles.
• Integrated phone
Selection of 4-line devices and display in a 2-line “Integrated phone”:
When selecting device types with a 4-line display (optiPoint 410/420 advance) in some
procedures may not be possible to display the “correct” lines on the only 2-line display
of “Integrated phone”.
If user does not like it, he can fall back on using the “Free phone” displaying the 4 lines.
• VPN
On some PC’s the VPN tunnel is closed, if the ODC-PE fails to connect. please follow
this link to download the driver and install it. After this the problem should be solved.
http://www.cs.columbia.edu/~hgs/research/projects/RTPMonitor/driverman.html

• Echo Cancellation
Echo Cancellation might not take effect in some scenarios like:
▪ Cross-talking,
▪ Different devices for playback and recording like using the sound-card speaker
and the microphone of a webcam.
▪ Microphone booster enabled.
• LDAP ID not acceptable

The words Notes or Exchange will not be accepted as LDAP ID by ODC-PE because
of an internal code restriction.
• Restrictions for Windows 10

Windows 10 Creators:
Generally, Win10 update system will automatically download & install Creators once
available.
The Windows 10 Creators will provide some features/tools – one of them is the new
Windows Defender (Windows native antivirus) - that will provide a “Security Central”.
Due that, Customer may experience slow/blocking issues IF ODC-PE (main
executable files) not provided with enough clearance (like explained before for
regular AntiVirus programs).
• Restrictions with Headsets

Plantronics Devices:
Due the upgrade to the new Plantronics SDK (FRN7162/UCBE-50), scenarios
with two or more Plantronics audio devices have changed:
ODC-PE is not capable anymore to choose which device to use.
The active device must be set on the Plantronics HUB application.
Senheiser Devices:
ODC-PE does NOT support two Sennheiser headsets plugged at same time.
Senheiser devices are not supported when ODC-PE and MS Lync are open at
same time. Must close MS Lync to have devices properly working with PE.
Two Audio Devices from same manufacturer

Our client (OpenScape Desktop Client Personal Edition) cannot be connected to
a PC with 2 devices from the same manufacturer at the same time.
This will cause problems / incorrect behaviors.
Example: 2 devices Plantronics WO100.
Jabra own Ring

Some newer Audio Devices (from JABRA) has its own RING, and some
Customers complain that is annoying 2 rings. So:
DEVICE RING can be deactivated from Jabra Direct Software. To do that, just
close the ODC-PE, configure the Jabra device by Jabra Direct sw and startup
the ODC-PE again.

4 Installation and Upgrade / Update

4.1 Installation
4.1.1 Data and information security
It is mandatory to apply the Security Checklist so that system default settings are hardened according
to best practices. This is most relevant after a first installation, but also strongly recommended after
each Major or Minor version upgrade. It presents a checklist to ensure all necessary installation and
configuration steps can be taken and adapted to the individual customer’s environment and security
policy. Deviations from the standard settings should be documented in the security checklist in
consultation with the customer's contact person.
The best possible standard of data security and protection is only provided on our latest solutions or
product versions. It is recommended to regularly install product updates in order to remove identified
security vulnerabilities and software defects, improve stability and add latest functionality.
Country-specific regulations must be observed.
4.1.2 Installations main steps

1. Ensure the pre-installation requirements are met (chapter 4.1.4).
2. Install the OpenScape Desktop Client Personal Edition (via Setup.exe or command-line).
3. Configure the OpenScape Desktop Client Personal Edition for the First Time (or use DLS).
4.1.3 Access rights

It is necessary to check if the “Installation User” (the one that will install the ODC-PE), has:
- Administration rights.
And
- complete rights to the following folders:
C:\Users\Public\Desktop and/or C:\Users\Public\Public Desktop
This is necessary because the ODC-PE’s Icon is installed on this folder to be used by any user.
Figure 9. Access rights example

4.1.4 Installation prerequisites

• Before installing ODC-PE, all other applications must be closed.
• For installing you need administration rights.
• Microsoft .NET Framework 4.0 or higher

The ODC-PE setup only performs a check of the installed .NET Framework version.
PS: If not enough version discovered, ODC-PE setup will fail with an appropriate msg.
• Microsoft Visual C++ 2010 Redistributable

Since version V7 R1.47.88, the "Visual Studio C++ 2010 SP1 Redistributable" packages were
updated to version 10.0.40219.325.
The Microsoft Visual C++ redistributable package list now is the following:
vcredist_x86_2010.exe
To summarize the changes, the package:
- "vcredist_x64.exe" was renamed to "vcredist_x64_2010.exe".
- All redistributable packages are automatically installed when running the "setup.exe".
PS: Need to be installed prior performing a silent installation or mass deployment.
• Security (AntiVirus / Firewall)

If PC where was/is installed ODC-PE has security applications, such as following examples:
Antivirus: McAfee, etc
Security: Firewall app
or Windows traditional apps: like Windows Defender or Windows Firewall.
It is necessary to configure the following processes as trusted exceptions1 in any/all anti-
virus/Firewall software’s running/installed at current PC to ensure optimum use of ODC-PE:
o For SIP:
▪ Unify.OpenScape.exe
o For HFA STACKLESS:
▪ Unify.OpenScape.exe
▪ SoftOla.exe
1
Such trusted exceptions is necessary due anti-virus/Firewall software’s may be the source
of half-way paths (lost payload) and/or also produce false positive reports (false
virus/malware reports).
• Windows 10 Creators:
Generally, Windows 10 update system will automatically download & install Creators once
available.
The Windows 10 Creators will provide some features/tools – one of them is the new
Windows Defender (Windows native antivirus) - that will provide a “Security Central”.
Due that, Customer may experience slow/blocking issues IF ODC-PE (main executable files)
not provided with enough clearance (like explained before for regular AntiVirus programs).

4.1.5 Packages included within install files

The following files/packages are the requested to install and use OpenScape Desktop Client –
Personal Edition. Each one of them is informed if is already included or not within Install files:
PE V7 HFA Stackless PE V7 SIP

Packages
(already included within
ODC-PE installation files) Win.10 Win.10 Win.11 Win.10 Win.10 Win.11
32-bit 64-bit 64-bit 32-bit 64-bit 64-bit
Microsoft .NET Framework 4.0 or higher
Plantronics Hub YES YES YES YES YES YES
TSPx64.msi YES YES
TSPx86.msi YES
Microsoft Visual C++ 2010 Redistributable

YES YES YES YES YES YES
Microsoft Visual C++ 2010 Redistributable

YES YES YES YES YES YES
*Only if a JABRA device is connected to OpenScape Desktop Client – Personal Edition

*Since JABRA released the new Jabra Direct, become unnecessary to install Jabra PC Suite.
PS1: Since version PE V7 R1.47.48 there is no need for install Microsoft Visual C++ 2005
Redistributable. Also, due that was removed it from Packages included within Install files.
PS2: Due market new hardware´s like Tablets or 2-1 Tablets, we need to reenforce the info that
ODC-PE does NOT support any type of Tablet and similar devices.
Only supported with PCs Desktops (with Windows 10) and Notebooks/Laptops (with Windows 10).
PS3: Since version PE V7 R1.47.90 started the official support for Windows 11.

4.1.6 Command-line installation (mass roll-out)

Important
Please check the OpenScape Desktop Client Personal Edition installation guide for details and
instructions of each option for command line-based install.
Command-line installation is generally done in big Customers (mass roll-out installs).

ODC-PE can be installed as SIP Provider or HFA Stackless Provider.
4.1.6.1 Command line-based installation (SIP Provider)

ODC-PE with SIP provider can be installed via command line (similar as installed as via setup.exe).
The difference is that via command-line the administrator/user has control about WHAT & HOW it’s
going to be installed by using specific parameters.
Example:
msiexec /i OpenScapeClient.msi DEFAULTPROVIDER="SIP-Provider" INTEGRATIONWC=none
INTEGRATIONACC=no /L*vx %TEMP%\PE-install-log.txt /qb
4.1.6.2 Command line-based installation (HFA Stackless Provider)

Regarding HFA STACKLESS, since ODC-PE V6 the TSP installer is separated of ODC-PE installer.
Due that, after installed the ODC-PE (using the command line as mentioned on manual or this RN
examples) will be necessary to also run the following command line:
msiexec /i TSPx86.msi
or
msiexec /i TSPx64.msi (if your operational system is 64-bit).
Example:
msiexec /i OpenScapeClient.msi DEFAULTPROVIDER=HiPath-Provider INTEGRATIONWC=none
INTEGRATIONACC=no REGISTRYDLS=0 /l*v C:\PE.log /qn
After ODC-PE installed, needs to do the TSP installation:
msiexec /i "C:\ODCPEV70R1.47.80\TSPx64.msi" /qn (if 64 bit)
msiexec /i "C:\ODCPEV70R1.47.80\TSPx86.msi" /qn (if 32 bit)
4.1.6.3 Command line-based installation (Outlook or Notes) Dial button

Regarding (Outlook and/or Notes) Dial button that is installed by default:
If user does not want to have installed such Dial button, then the following option is necessary to be
included within the installation command-line with parameter:
CLIENTINTEGRATION="no"
Example:
msiexec /i OpenScapeClient.msi DEFAULTPROVIDER="SIP-Provider" INTEGRATIONWC=none
CLIENTINTEGRATION="no" INTEGRATIONACC=no /L*vx %TEMP%\PE-install-log.txt /qb

4.1.6.4 Command line-based installation (Plantronics SDK)

Since ODC-PE V7 R1.47.11 are necessary 2 packages for Plantronics devices:
SpokesSDKRuntime.msi and SpokesSDKNativeRuntime.msi.
And since V7 R1.47.76 the Plantronics msi packages changed to HubSDKRuntime.msi and
HubSDKNativeRuntime.msi respectively.
You can also install them via the following command prompt:
msiexec /i HubSDKRuntime.msi /qb /lvx* <path>\Spokes.log
and
msiexec /i HubSDKNativeRuntime.msi /qb /lvx* <path>\SpokesNative.log
WARNING: There is (available within Plantronics official site) an app called Plantronics HUB.
ODC-PE is also compatible with Plantronics HUB app but having both (Plantronics HUB and our
provided Plantronics SDKs) installed at same time may cause the Plantronics headset integration
not to work as expected.
So, User must decide what use/install:
Provided Plantronics SDKs
or
Plantronics HUB.
PS: If Customer wants to use Plantronics HUB in a PC/machine with ODC-PE already installed with
Plantronics SDKs, prior to install the Plantronics HUB, must uninstall the Plantronics SDK (via same
MSI packages above).
4.1.6.5 Command line-based installation (JABRA SDK)

No need to install a specific package for Jabra Devices. It’s encapsulated by Client install.
4.1.6.6 Command line-based installation (Senheiser SDK)

No need to install a specific package for Senheiser Devices. It’s encapsulated by Client install.

4.1.7 Installation of ODC-PE on Citrix Terminal Server

- Specific ODC-PE licenses are required for this VDI functionality.
- Shut down all programs (especially Microsoft Outlook and IBM Notes) before begin installation.
- ODC-PE VDI is supported in the environment with Windows 2016 Server and Citrix XenApp.
Versions Supported:
- Citrix XenApp 6.5 Server
- 7.15 to 7.18 LTS
- Citrix Virtual App 1903.
IMPORTANT: Only Citrix XenApp is supported with ODC-PE for VDI solution.
So, a VDI solution based only in Windows 2016 Server (without Citrix XenApp) is NOT supported.
4.1.7.1 Restrictions for ODC-PE on Citrix environment

• Custom ring tones are not supported.
• Auto update feature is not supported.
• Only the domain administrator should install the Citrix Receiver and the ODC-PE VDI
component.
• The ODC-PE built-in screensaver functionality is not supported.
• Hotkeys are not supported.
• Only available for SIP provider.
• Only released for OpenScape Voice and OpenScape 4000 PBX.
• Video is not supported.
• upgrade from V7 R1.47.10 (regarding VDI) is not supported.
• Configuration lost on clients if anonymous allowed on Citrix.
• ODC-PE cannot be published as streamed on Citrix.
• DLS IP conflict for all VDI clients: client’s config via DLS not possible with ODC-PE as it is
done for standard ODC-PE install. For alternatives configurations check chapter 4.1.7.4.
4.1.7.2 Installation on Server Side

On Citrix Server machine, run the setup.exe file in the folder ODCPEV70R1.47.xx
Information regarding installation chapters 4.1.1 to 4.1.5, applies also to installation of ODC-PE in
Citrix Server.
The exceptions are mentioned in topic 4.1.7.1.
Prerequisite’s list:
- Installed:
Citrix XenApp 6.5 Server or
7.15 LTSR (also supported until 7.18 LTSR) or
Citrix Virtual App 1903 (evolution of XenApp/XenDesktop).
- For user to be able to access their local drive via hierarchical tree in File Selection Dialog, the
Administrator could configure Citrix to map the user’s local drive.
- After install Citrix XenApp 6.5 Server (or 7.15 LTSR or 7.18 LTSR or Citrix Virtual App 1903), ODC-
PE must be published for streaming in Citrix AppCenter.
- OpenScape Personal Edition only supports Citrix Receiver 4.2 and higher.
- Windows 10 supports Citrix Receiver 4.1 and higher.
- Example of an installation with default settings via command line:
msiexec /i "<path>/OpenScapeClient.msi"
<path> indicates the absolute path to the OpenScapeClient.msi file.

The setup starts in English language by default.

For further details about each parameter, please check the OpenScape Personal Edition installation
guide (chapter 4.3.3.3. How to Install OpenScape Personal Edition VDI - Client Installation via
Command Prompt).
4.1.7.3 Installation on Client Side

On Client side, install of the VDI module must be done with a user account with domain
administration rights.
The exceptions are mentioned in topic 4.1.7.1.
➔ Prerequisites
- .NET Framework 4.0 or higher
Due to the significant size of the full package of .NET Framework 4.0 (or higher) the .NET
Framework installation package is not delivered with the installation package of ODC-PE VDI.
Please download from Microsoft’s Download Center and install it before installation of ODC-PE
VDI.
The ODC-PE VDI setup only performs a check of the installed .NET Framework version. In case
not enough version of .NET Framework is discovered the ODC-PE setup will fail with an
appropriate message.
- Citrix Receiver must be installed before install ODC-PE.
Attention that newer versions (of Citrix Receiver) changed the name to Citrix WorkspaceApp.
- ODC-PE supports only Citrix Receiver 4.2 and higher.

To download & install Citrix Receiver, connect to Citrix Server as Administrator, and in the
sequence, you will be prompted to download Citrix Receiver.
a) You must be logged on as Administrator to install Citrix Receiver and ODC-PE.
b) If ODC-PE is installed with a restricted installation of Citrix Receiver (by someone other than
an Administrator), uninstall both Citrix Receiver and ODC-PE, delete registry entries if
necessary, and reinstall in the correct order, logged on as administrator.
c) After a Citrix Receiver update, re-install or repair ODC-PE (logged as administrator).
d) For a user to be able to access their local drive via the hierarchical tree in the File Selection
Dialog, the Administrator must configure Citrix to map the user’s local drive.
➔ Installations: Command-line
- Custom folder/location Install. Example:
msiexec /i softphone.msi /qb /lvx* <path>\softphone.log INSTALLDIR=c:\folder
- Default folder Install. Example:
msiexec /i softphone.msi /qb /lvx* <path>\softphone.log
PS: The same commands are used to install upgrades.
➔ Installations: Manual
The administrator must:
- First install the Citrix receiver software (if did not install yet);
- After Citrix receiver has been installed: install ODC-PE VDI component
(Running the file setup.exe under the folder ODCPEV70R1.47.XX_VDI of the package/CD)
- The prerequisites* will be automatically installed prior the installation of the ODC-PE VDI
component.

* .NET Framework 4.0 or higher:

It’s also a prerequisite but due to the significant size of the full package of .NET Framework 4.0
or higher the .NET Framework installation package is not delivered with the installation
package of ODC-PE VDI.
The ODC-PE VDI setup only performs a check of the installed .NET Framework version. In the
case not enough version of .NET Framework is discovered, the ODC-PE setup will fail with an
appropriate msg.
IMPORTANT:
- Use ODCPEV70R1.47.XX_VDI for the Client installation (LOCAL PC).
- Standard ODC-PE version must not be used on the Client as it will install ODC-PE without Citrix
capabilities.
4.1.7.4 ODC-PE + VDI + DLS

Combination of ODC-PE + VDI + DLS (where could exists several simultaneous instances of ODC-PE
at same Server, and the port 8082 can only be used by one instance) could be a problem.
Further details:
Problem is that the DLC (DLS client) binds the TCP port 8082 to listen to “contact me” requests from
DLS.
Since can be just one bind per TCP port, only the very first ODC-PE instance can do it (the other
instances on the same server will not have a functional DLC).
For such scenario there are 2 possibilities/solutions:
#1: via/use DCMP ("DLS Contact Me Proxy").
When DCMP is enabled, connections are established only from the client to the DLS.
Therefore, the DLC does not need to bind local ports.
Or
#2: via configuring a regedit key
This solution is to make each instance (of ODC-PE) to use an exclusive port for DLC.
#2.1: Creating a DWORD named "DLCPortRangeEnd",
and as the key name implies, with value been the "DLC port range end", under
"HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Siemens\OpenScape".
Example:
If we want a range of 101 ports, starting from 8082, we should configure the registry with “8182”.
#2.2: Together with the existing setting on ODC-PE

(“Settings => Advanced => General => Central Configuration => Client (DLC) => Port”)
the administrator can set a port range (e.g., from 8082 to 8182).
Then, the first ODC-PE instance will use TCP port 8082,
The second will use 8083, The third 8084, and so on.
IMPORTANT: This #2 configurations were specifically implemented to address the Citrix issue.

4.2 Upgrade / Update / Migration

4.2.1 Fallback
4.2.2 Upgrade / Update

For more detailed information about any type of update, please consult Program Update in
OpenScape Desktop Client Personal Edition Installation and User Guide file (chapter 3.3.1.6).
Basically, there are 3 ways to execute an update:
#1 Via ODC-PE Settings
Can configure the ODC-PE to automatically check/update when a newer version is available at a pre-
selected folder.
Figure 10. Example Program Update folder configuration
#2 Via Setup.exe
Via executing directly, the new version/build, replacing the previously version.
#3 Via command-line
Via running the same command-line used before to install the first time.
Important information:
- For update, administrator rights are required.
- All configuration data are saved in a version-independent folder during an update.
- Since ODC-PE V7 R1.46.10, won’t offer and support the HFA (H323) provider connection any longer.
4.2.3 Update of ODC-PE on Citrix Terminal Server

The update must be done in the server and in the client sides.
4.2.3.1 Update on Server side
Basically, you can follow the same procedure/instructions as mentioned before in chapter 4.2.2, just
remember to consider the restrictions mentioned in chapter 4.1.7.1.
4.2.3.2 Update on Client side

In case of updating only the ODC-PE VDI component, it’s just a case of running setup.exe file under
the folder PEV70R1.47. XX_VDI

4.2.3.3 Supported update versions (standard or Citrix install)

In case of having to update the Citrix Receiver version, update:
- First the Citrix receiver
- Next in the sequence update the ODC-PE VDI component.
IMPORTANT:
➔ The update of ODC-PE VDI component is demanded after the Citrix Receiver update.
(Even though there is not a new version of ODC-PE VDI).
➔ The VDI upgrade from version V7 R1.47.10 does not work. In this case please uninstall ODC-PE
V7 R1.47.10 VDI softphone component on Citrix Client machine, and next install the newest ODC-PE
V7 R1.47. XX_VDI softphone component.
Supported update versions:

• Any build since 70.1.47.0061 (V7 R1.47.61) to newer builds should work.
4.2.4 Repair
This option is only to repair a damaged ODC-PE existent installation.
Go to Windows Control Panel ➔ “Programs and Features” panel
select “OpenScape Desktop Client” and click on Repair option.
Figure 11. Example Repair option

PS: Should not be used to include or remove ODC-PE features.
4.2.5 Uninstall
To uninstall ODC-PE, you must do it via Windows Control Panel ➔ “Programs and Features” panel
select “OpenScape Desktop Client” and click on Uninstall option.
Figure 12. Example of Uninstall option
PS: User profile data is not removed in this procedure. To remove it you must go to user’s appdata
folder and remove the OpenScape folder under the Siemens folder.

4.3 Special settings and instructions

4.3.1 Licensing
Licensing is a mandatory and active part of ODC-PE.
4.3.1.1 Versions and protocols supported

- With CLA (Customer License Agent) installed.
The CLA should be available via network or can also be installed locally (same PC as one of the ODC-
PE installed).
PS: A valid license for every OpenScape Desktop Client on the CLA is required for full features
access.
- Without CLA installed (SIP only).

Without CLA installed, the ODC-PE works in a reduced/minimum range of features (simple SIP calls).
The full range of features is only available with CLA installed.
- Also due to the changes/upgrades regarding Licenses, the old licenses files that is valid for older
ODC-PE V6 will NOT work (are not compatible) with the new clients ODC-PE V7 (like this one).
- ODC-PE specific licenses are required for VDI functionality (ODC-PE on Citrix):
For using license management, you must enter the IP-address or name of the license server under
Settings\Licensing\Server
The Loop-Back IP-address is set as default value for local CLA installation.
- Since PE V7 R1.47.60 was released, the Client brings a new CLC (V2R20.0.0).
This new CLC is within company ideas to use only TLS 1.2 without fallback.
PS: For more details about fallback/TLS please check next chapter 4.3.1.2.
- The CLC (Customer License Client API) was upgraded to provide better security.
- Currently, implemented security uses OpenSSL version 1.0.2r. So far, no plans to migrate to
OpenSSL 1.1.1.
- Due the improves/upgrades within licenses, minimum and GA versions of CLA/CLM should be (at
least):
GAs (equal or
Minimum versions newer)
CLA: V1R42.0.0 CLA: V1R43.0.0
CLM: V1R21.0.0 CLM: V1R22.0.0
4.3.1.2 Fallback TLS supported

By default, only TLS 1.2 should be enabled (since the newer versions of Licenses and ODC-PE).
However, customers should be able to enable fallback to TLS 1.1 and 1.0 via Windows registry key
PS: On each and all ODC-PE windows that needs to work with old TLS:
Creating a DWORD named "EnableTls11AndTls10", with value "1", under
"HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\OpenScape"

4.3.2 Modify ODC-PE Folders

It’s possible to change the individual folders where will be saved configurations and user data
settings from an ODC-PE already installed.
This can be done using the Settings Folders Tool application from the following path:
C:\Program Files (x86)\Unify\OpenScape Desktop Client\Tools\Settings Folders Tool
Settings Folders Tool is a link to an executable file that wil re-define the folders settings accord to
your new definitions.
Example:
Figure 13. Example of changing Folders locations
IMPORTANT:
- This only works if run as Administrator.
- Before running it, be sure of having closed the ODC-PE application.
- Remember that User must have read & write rights for the default directory
<\\Documents and Settings\All Users\Application Data\Unify\OpenScape>
(or for new data directory changed by Settings Folder Tool).
4.3.3 New Audio Devices: Auto Detect

The ODC-PE has an automatically feature that allows to Auto Detect a new Audio Device (without
the need for manually configuration). User only needs to press OK once presented the new Audio
Scheme window.
But there are some considerations to be checked:

1) The device must never be added (to PC) before started ODC-PE ➔ it’s the only way to PE
receives info from OS (Windows) reporting that a new Audio Device was connected to PC
and then its really a new Audio Device and therefore automatically connected/configured
the Audio Scheme;
2) If a “device1”(example DA45) was connected (manually or configured) to ODC-PE (example

via USB1) and then removed and added other one (device2 also DA45) to same USB1 the
auto feature will not work since ODC-PE interpreters such situation as if both devices are
actually the same unique device.

4.3.4 Microphone not working

It’s very rare scenario but eventually could happen that a specific Audio Device Microphone does not
work (example due some trash noises, mutes, or not payload at all).
There is a quick and easy test to confirm if the Microphone issue is a problem between:
OS (Windows)  Audio Device
Or
ODC-PE  Audio Device
You can prove that by yourself via

Windows ➔ Sound Control:
If the problem is somewhere OS (Windows)  Audio Device ➔ User could change the volume as
much desires, but nothing will change (unless changes done via specific device menu).
PS: Also, you could try to test the microphone volume and it won’t work.
Figure 14. Attempt to change Volume via Windows systray bar (Sound Control).
If confirmed the wrong behavior above, then its error between OS (Windows)  Audio Device.
That’s because Device Sound is not manageable by Windows (for this specific Device of course).
In such case, ODC-PE also will fails because when ODC-PE attempts to change volume via API (ergo
Windows), so no control volumes for any other third (OS point of view) application such our ODC-PE.
Further tip/ info ➔ keep in mind that other applications (like VLC, MediaPlayer, etc) despite they
“seem” to control the volume, in fact they are controlling their own sound (application sound) and
can not be used as “prove” that Audio Device + OS is working as expected.
Example:
If Audio Device volume is configured to 45% of volume, the MediaPlayer will control (00%  100%)
of his own sound based on the 45% available volume (so: 00% - 45% max in this example).

4.3.5 Mobile Registration with OpenStage Devices

When using the "Mobile Registration" feature with OpenScape 4000 in connection with OpenStage
hardware devices, the device type optiPoint 420 standard (key module with slk) must be set in
ODC-PE - available from OpenStage V1 R2.
When using the "Mobile Registration" feature with OpenScape 3000 in connection with OpenStage
hardware devices the device type optiPoint 420 standard (key module with slk) must be set in
ODC-PE - available from OpenScape 3000 V7 R5.1.0 / OpenStage V1 R2.
ODC-PE does NOT support the key layout of OpenStage phones.

For this reason, an “optiPoint 420 standard” device must be selected which has a different number
of keys.
In consequence OpenStage phones have more keys than OpenScape Desktop Client.
By using the “optiPoint 420 advanced” device OpenScape Desktop Client offers more keys than the
OpenStage phones.
PS: The additional number of keys cannot be synchronized with the OpenStage phones.
4.3.6 Local Recording

Generally, any User can start at any call/conversation the feature local recording.
To prevent the user from accidental use it (and due to legal or corporate regulations), the new setting
‘Disable Voice Recording’ has been created in the ‘System functions’ section of the ‘SIP Service
Provider’ settings.
If/when checked the corresponding voice recording control doesn’t appear in UI.
Example:
Figure 15. Voice Recording Activation

4.3.7 SPE (Signaling Payload Encryption)

The ODC-PE has this feature (SPE) for HFA and SIP Providers.
For both Providers, the activation is done simultaneously for Payload and Signaling.
For SIP Provider:

- The activation is done via ODC-PE (for instructions check Installation Guide chapter 9.24.7).
- The ODC-PE does not check/validates Certificates.
For HFA Provider:

- The activation is done via DLS (for instructions check the Installation Guide chapter 9.24.8).
- The ODC-PE does not check/validates Certificates.
About autoSPE:
- autoSPE is not the same as SPE.
- The ODC-PE does not support feature AutoSPE:

AutoSPE: Feature responsible to deploy automatically Certificates to devices but it’s
not implemented within Personal Edition.
SPE: responsible to encrypt Signaling and Payload and it does work with ODC-PE.
- So, if Customer wants to use SPE and activates the AutoSPE ➔ DLS will deploy Certificates
to Telephones Devices but not to ODC-PE ➔ SPE will continue to work for both (Telephones
and ODC-PEs) because PE does not check the Certificate.
4.3.8 Monitor/Display with Audio Device

By Default, Client cannot use Monitor's audio device (Devices connected via Monitor’s display port).
But there is some Users that wishes to use Audio Device connected direct via Monitor’s display port.
For such situations, there is a regedit key that allows such Audio Device (via Monitor port) to be
recognized and used by the Client (ODC-PE).
Device will be recognized if register key LineAsWaveOut, DWORD with value 1 is created within path:
32-bit => HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\Openscape
64-bit => HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Siemens\Openscape
4.3.9 Custom Ring via MP3 file

By default, it’s possible for the User define/use a desired MP3 file as Ring tone (instead the default
tone). Check the “Use Individual ring tones” and next search over User’s desired MP3 file:
Figure 16. Custom Ring via MP3 file via SIP Provider and HFA Provider.

Restriction: If selected a MP3 file, it won’t play at audio device defined via Sound Schemes.
Once User selects to play a MP3 file, Windows Media Player will be used automatically by Windows.
So, will play on selected Audio Device as default on Windows Sound Settings.
PS: Regular Ring tone plays because it's not media file (using Audio Device defined like PC Speaker).
WorkAround:
If User insists to use a specific Audio Device (Example PC Speaker for Ring MP3 file) then User needs
to select the desired Audio Device as DEFAULT via Windows ➔ Sound ➔ Playback.
Example: to define a new Audio Device as the new Windows DEFAULT Playback Sound device:
Figure 17. Defining a new Audio Device as Windows DEFAULT
4.3.10 Directory Search (search for contacts)

This feature is used to allow user to Search over for Contacts.
Important: Not all kind of search is allowed.
There are some important situations that need to be mentioned to prevent wrongly complains
and/or doubts regarding such searches:
#1 The Directory Search (as the name says) is only for directories (LDAP, etc):
- Therefore, LOCAL Outlook contacts are not part of them.
- Searches can be done ONLY by NAME or partial NAME (not phone number).
Figure 18. Examples of attempt searchs via NAME (VALID) and number (INVALID).
#2 If Customer wants to perform a ClicktoDial or Receives a call:
(If local outlook Contact) ➔ ODC-PE should be able to search for it “indirectly” (via CallControl,
not via Directory Search) and due that shows correct number/name at Call Control / Journal.
IMPORTANT:
- Microsoft Outlook Integration: Enables Microsoft Outlook Users to deploy features of the ODC-PE
(direct access to Outlook Contacts from ODC-PE Client to allow Resolution NAMES).
- Microsoft Outlook Integration, more specific Resolution NAMES is NOT available for Outlook 64-bit.

4.3.11 White Noise

4.3.11.1 White Noise feature
White Noise (or Artificial Noise) is a feature that allows the users keep the impression that the call is
not set to hold (total silence).
The User (if desired) could use the regedit SupressWN parameter to activate or deactivate the
artificial noise in the line during an active call.
Also, if the User desires to control the volume of this artificial noise, the LevelWN registry parameter
should be used.
NOTE1: SupressWN flag controls whether Comfort Noise should/shouldnt be forwarded to the
handset of the SoftClient. Therefore ODC-PE with SupressWN flag activated means that White Noise
will be DISABLED and thefore not sent to connected Audio Device.
NOTE2: SupressWN and LevelWN registry values are not automatically created by ODC-PE setup.
How to create or use such parameters:

#1. Open the Windows registry editor (regedt32 or regedit).
#2. Switch to the directory:

32-bit => HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\Openscape
64-bit => HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Siemens\Openscape
#3. Create new DWORD (32 bit) value(s) named SupressWN and/or LevelWN, as desired.
#4. For SupressWN, double clicking the entry you can define one of the following two values for this
parameter in the open Configuration dialog:
Activating/deactivating the Supression of White Noise:
0: artificial noise activated
1: artificial noise disabled
For LevelWN, double clicking entry you can set any value between 1 (minimum) and 100 (maximum).
NOTE3: If the parameter SupressWN does not exist in the above directory, artificial noise is created in
a silent line during a call by DEFAULT.
NOTE4: If parameter LevelWN does not exist in above directory, artificial noise is created in volume 7.
NOTE5: If wanted to configure White Noise via DLS, please check next chapter.
4.3.11.2 Suppress White Noise (configuration via DLS)

This new feature is used to controlling ODC-PE White Noise via DLS.
Was created a new field/option for White Noise within ODC-PE module Sounds and allows such
configuration to be done via DLS.
Starting with ODC-PE V7 R1.47.77, there are 2 ways to activate/disable the SUPPRESS for White
Noise:

#1: Via ODC-PE:

Settings>>Advanced>>SIP Service Provider >> Sounds>>Suppress white noise
Figure 19. Example of configuration (in example disabled) of suppress white noise.
#2: Via DLS:

DLS config >> IP Client Configuration>>Miscellaneous>>Sounds>> Suppress white noise
Figure 20. Example of configuration (in example disabled) of suppress white noise.
IMPORTANT: IF configuration is done via regedit (check about it within chapter 4.3.10.1) be aware that
the registry entry has priority over the DLS configuration.

4.3.12 Directory Search (search for contacts)

This feature is used to allow user to Search over for Contacts, but not all kind of search is allowed.
There are some important situations that need to be mentioned to prevent wrongly complains
and/or doubts regarding such searches:
#1 The Directory Search (as the name says) is only for directories (LDAP, etc):
- Therefore, LOCAL Outlook contacts are not part of them.
- Searches can be done ONLY by NAME or partial NAME (not phone number).
Example:
Figure 21. Examples of attempt searchs via NAME (VALID) and number (INVALID).
#2 If Customer wants to perform a ClicktoDial or Receives a call:

(If local outlook Contact) ➔ ODC-PE should be able to search for it “indirectly” (via CallControl –
not via Directory Search) and due that shows correct number/name at Call Control / Journal.
IMPORTANT:
- Microsoft Outlook Integration: Enables Microsoft Outlook Users to deploy features of the ODC-PE
(direct access to Outlook Contacts from ODC-PE Client to allow Resolution NAMES).
- Microsoft Outlook Integration, more specific Resolution NAMES is NOT available for Outlook 64-bit.
4.3.13 Shortcut for ODC-PE Settings/configuration

By default, the ODC-PE bypass automatically the login window once started (if not the first time).
If becomes necessary to access the ODC-PE Settings/Configuration, there is 2 ways to do it:
#1: SHIFT key
Press and HOLD the SHIFT key while clicking/pressing enter over the ODC-PE icon.
#2: edit Shortcut
If SHIFT key does not work (such environments like CITRIX or MS RDS) then use follow parameter:
- Add the parameter “-settings” to the command-line parameters field.
PS: Please note that is necessary to create a NEW shortcut for this one.
Figure 22. Example for creating a shortcut to ODC-PE settings

4.3.14 Tel URI protocol

The solution implements since the ODC-PE V7 R1.47.50 for Tel URI protocol is to allow the browser
application to perform calls using Windows applications registered for this purpose.
Was also implemented the capability to register our ODC-PE solution as a Windows application to
handle basic Tel URI requests.
If the user defines ODC-PE as the default application for TEL protocol in his Windows machine, the
call will be started immediately after the click.
If no application is defined as default, user will receive a Windows prompt asking to choose one
application.
Example:
Suppose that your internet page has the following facility:
Call me at +554133418888
This will be coded in HTML as:
Call me at <a href="tel:+554133418631">+554133418631</a>
No special configuration is needed to ODC-PE make calls using TEL protocol, just install it and
choose it as default apps for TEL protocol in the first use.
If the user already has another default application selected for the Tel protocol, user can change
this configuration and select the ODC-PE as default app:
Example:
Figure 23. Example to set ODC-PE as default app
ODC-PE selection for TEL protocol within Windows 10:
Figure 24. Example for TEL protocol (configuring Windows 10 to use our ODC-PE)

4.3.15 Call without Payload (microphone privacy settings on Win 10)

In cases the user makes calls without payload in Windows 10, it is possible that the Windows privacy
settings should be changed.
Windows 10 requires the user authorization to use the microphone.

This configuration can be found on
Windows Start > Settings > Privacy Settings > Microphone
The setting “Allow apps to access your microphone” should be on.
Example can be seen on the screenshot:
Figure 25. “Allow apps to access your microphone” should be on

4.3.16 ODC-PE supports the DLS feature “Bootstrapping and Secure mode”
The ODC-PE now supports the DLS feature “Bootstrapping and Secure Mode”.
This feature can be activated in DLS server, as we can see below:

- Setting the flag “Secure mode required”
Main Menu > IP Devices > IP Phone Configuration > Security Settings > "DLS Connectivity"
Tab
Secure mode required

If this feature (Secure mode required) 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 (ODC-PE) registers at the
DLS.
➔ This checkbox is disabled by default.
Figure 26. Example from activating feature Secure mode within DLS for the desired ODC-PE.
In the sequence, when secure mode is enabled, there is three possible PIN options:
- No PIN: Access data is sent unencrypted to the IP Device.
- Default PIN: Standard PIN is used for several IP Devices. This is generated automatically by
the DLS.
- Individual PIN: An individual PIN is created for the selected IP Device.
- Reset: When the flag “reset” is marked in DLS, the bootstrapping process is restarted. It
means that the certificates will be exchanged again (and if necessary, the PIN code should be
inserted).

After ODC-PE first start, a PIN dialog will be shown, and the respective PIN code should be inserted:
Figure 27. Example of PIN window

➔ In cases when cancel option selected, at ODC-PE next start the PIN code will be prompted again.
Important related DLS configurations

To have the PIN created to be used, its necessary to perform some configurations via DLS prior
activating the Secure Mode, as follow:
Figure 28. Example of PIN definition and option to generate it again (if necessary).
Default PIN: To be used by all users.
Retries for PIN submissions: Specifies the number of failed attempts permitted when entering the
PIN at the IP Device.
TAN Verifications: TAN (Target’s Authentication Number) is the last 3 characters of PIN to be used by
provisioning service to authenticate the target device in Secure Mode.
Certificate Check Policy: The settings are used only for devices in secure mode.
Restriction: When using Free Seating environments, option "Certificate Check Policy" must be set to
"Trusted":
Administration > Workpoint Interface Configuration > Secure Mode > Certificate Check Police =
Trusted

4.3.17 LDAP Secure (LDAPS)

This new feature is used to allow the use of LDAPS mode (via TLS).
IMPORTANT: This was required to follow Security Advisory OBSO-1911-01 recommendations.

Due to that, our ODC-PE now supports LDAP over TLS (LDAPS) by enabling the "Secure" option in the
LDAP Directory Configuration Dialog.
This option changes the port used for this connection automatically to 636 and encrypts the
communication between client and server.
Example:
Figure 29. Example of GOOD configuration of LDAP LDAPS (Secure).

Some comments/mandatory steps:

#1: The support for LDAPS started with ODC-PE V7 R1.47.67 and forward.
#2: Client computer (ODC-PE) must trust the server certificate, therefore the root certificate of the
server must be added (INSTALLED) to the Trusted Root Certification Authorities store (ODC-PE PC).
Example:
Figure 30. Example of installed Certificate within ODC-PE PC.
#3: Once/if PE is activated with checkbox SECURE it will change automatically to port 636 (default
for LDAPS). Example:
Figure 31. Example of Configuring LDAPS (port) via ODC-PE.

#4: Server address MUST be configured with FQDN when using Secure mode (IP address is not
allowed / can NOT be used for Secure mode). Example:
Figure 32. Example of Configuring LDAPS (Server address) via ODC-PE.
#5: This implementation was required to follow Security Advisory OBSO-1911-01 recommendations.
#6: Examples of error msgs that could occur due some invalid/incomplete LDAPS configuration:
Example1: Error due wrong Port configured (non-secure port 389 instead secure 636):
Figure 33. Example1: Error due wrong Port configured (non-secure port 389 instead 636).

Example2: Error due used IP address instead Server FQDN:
Figure 34. Example2: Error due used IP (instead FQDN).
4.3.18 Disable the “HOLD” button

This new feature was created only for specific cases (like big Contact Centers) with scenarios like
======================================================================
Several agents use the telephone for handling the call flow and all the functions (calling, answering,
transferring, etc)”.
Such control isn’t managed by ODC-PE but via customized GUI.
So, such specific cases, the Hold button can be disabled (to prevent wrong use/conflict).
======================================================================
To disable the Hold button:

It's necessary to create a registry key in the OpenScape path
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Siemens\OpenScape
The name of the registry key should be "DisableHoldButton" (DWORD 32bit) with value 1.

4.3.19 ODC-PE Running modes

The ODC-PE (since the version V7 R1.47.71 and forward) has a minor change on running
modes/Licenses => was removed the “Free SIP” mode.
This subchapter explains (in a basic way) how each mode runs. There are from now on 3 modes as
the ODC-PE could run/work: Licensed, FOP & Evaluation Period.
4.3.19.1 “License period” mode

- If connected to a CLA with valid license will work under Licensed mode.
4.3.19.2 “Evaluation period” mode

- If connected to a CLA without valid license available will work only 30 days under Evaluation
mode (with all ODC-PE Features but only 10 SIP, 10 VDI and 10 HFA).
4.3.19.3 “FOP or GP period” mode

FOP (Fail Over Period) or also known by some Customers as GP (Grace Period). It allows the user to
keep using all the ODC-PE features for a certain amount of time when the CLA is unreachable.
It has the following rules (to work or not within FOP/GP):

===============================================
- It is available only if ODC-PE has successfully retrieved a license from CLA at least once.
- It begins when ODC-PE is started while CLA is unreachable.
- Once it begins, all the product features are available for 30 days (in a row).
- It ends with any occurrence of these two situations:
1. The CLA is reachable again: This also resets the number of days for a new failover period. I.e.,
independently of the previous failover period duration, if the CLA becomes unreachable again, the
new failover period will last up to 30 days.
2. The 30 days expired: After 30 days without a successful CLA connection, ODC-PE will stop
working (at least until a new valid license is acquired by Customer).
===============================================
4.3.20 Auto profile creation

This new feature was created to allow Customers that uses DLS (for configuration) and wishes to
avoid the need to a User create the profile during first start up.
With this feature activated, the ODC-PE profile will be created automatically (without the User
interaction). Such automatically profile will be created with name = OpenScape
To activate this feature:

Create a registry key named "AutoStartWithRoamingProfile" with value 1.
It is a DWORD (32bit) registry key that should be created in the
"HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Siemens\OpenScape\"
Additional infos:
- It can also be used for auto-login (scenario without DLS) but User must have a pre-existing profile
configuration.
- It can also be used for Users with Roaming profiles.

4.3.21 ODC-PE desktop notifications via DLS

This new feature is used to allow controlling of ODC-PE notifications via DLS.
Was created a new field/option for incoming calls within ODC-PE module Desktop Notifications and
also allows such configuration to be done via DLS.
Starting with ODC-PE V7 R1.47.77, there are 2 ways to control Desktop Notifications:
#1: Via ODC-PE:
Settings>>Advanced>>Desktop Notifications 4.0>>Enable Incoming call toaster
Figure 35. Example of configuration (in example activated) the Incoming Call Toaster.
#2: Via DLS:

DLS config >> IP Client Configuration>>General>>Notifications>> Enable incoming call toaster
Figure 36. Example of configuration (in example disabled) the Incoming Call Toaster via DLS.

4.3.22 Disable Local features via DLS

Was created 4 new field/options to DISABLE the following local features:
Call Forwarding
Do Not Disturb
Second Call
Second Call without tone
Such configuration can be also done via DLS.

Starting with ODC-PE V7 R1.47.78, there are 2 ways DISABLE local features:
#1: Via ODC-PE:

Settings>>Advanced>>SIP Service Provider >> Additional functions >>Disable Local Features
Figure 37. Example of configuration (in example Local Features that can be disabled.
#2: Via DLS:

DLS config >> IP Client Configuration >> Miscellaneous >> Disable local features
Figure 38. Example config (in example local features that can be disabled) via DLS configuration.

4.3.23 DLS Discrete notification

This new feature was created so ODC-PE can receive several DLS changes (jobs) in the background
during runtime, and to apply them to its local configuration.
The notification will be in the Pearl menu only (to inform the User that these changes will only
become active the next time the application is restarted).
PS: This it is NOT an error message, just warning.
To activate the “discrete notification” feature it's necessary to create a registry key in the OpenScape
path HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Siemens\OpenScape
The name of the registry key should be "EnableDiscreteNotification" (DWORD 32bit) with value 1.
Figure 39. Example of Notifications regarding DLS changes.
4.3.24 Diversion header

Calls into hunt group cannot be distinguished from direct dialed calls to the DID/DDI since (old) PE
didn’t support for SIP Diversion header. To improve such case, was implemented this new feature.
Since ODC-PE V7 R1.47.83 has support for Diversion Header. No additional regedit/configuration.
Figure 40. Example of Diversion Header support.

5 Hardware and Software Compatibility

5.1 Hardware
5.1.1 Server (for ODC-PE VDI solution only)
Hardware Product Revision / Comments
MEMORY For Citrix Terminal Server consider use of 80 Mbytes of RAM per each ODC-PE VDI session.
5.1.2 Client – ODC-PE Standalone

Hardware Product Revision / Comments
CPU Min. 1 GHz or higher (2 GHz recommended).
MEMORY Additionally, min. 256 MB free RAM for the OpenScape Desktop Client Personal Edition
processing.
- Min. 1,0 GB memory if running Windows XP (not supported anymore);
- Min. 1,5 GB memory if running Windows Vista (not supported anymore);
- Min. 1,5 GB memory if running Windows 7; (not supported anymore);
- Min. 1,5 GB memory if running Windows 8;
- 2 GB memory recommended.
VIDEO Minimum hardware and software requirements for all resolutions:

- Latest available driver for the graphic adapter
- Minimum 2 GB or more of RAM.
- For computers that have many applications open, 4 GB or more of RAM is recommended.
- Camera: no specific camera is required. However, you must install the latest available driver
from the manufacturer (the Windows driver may be out of date).
HD cameras – To use HD cameras with:

- HD resolution (download bandwidth of 12000 kbits/s or higher): needs at least core i5
- Lower resolution (download bandwidth of 6000 kbits/s or higher): needs at least Pentium
Dual Core 1.83 GHz. (ODC will choose CIF, VGA or another appropriate resolution according to
the selected download bandwidth).
Audio Call only => Download bandwidth above 192 kbits/s. Values below this threshold will
cause problems.
VGA or lower resolution cameras

- Pentium Dual Core 1.83 GHz and above
AUDIO Additional requirements for audio:

min. SSE2 if using G.729 codec (further details see e.g. http://en.wikipedia.org/wiki/SSE2)
Codecs for SIP Provider

The Audio Codecs that OpenScape Desktop Client (SIP Provider) supports are:
G.711, G.722 and G.729.
PS: The G.723 is not supported!!
Codecs for HFA Stackless Provider

The Audio Codecs that OpenScape Desktop Client (HFA Stackless) supports are:
G.711, G.723 and G.729.
PS: The G.722 is not supported!!

5.2 Firmware
5.3 Loadware
5.4 Software / Applications

Product Software Version Release Date Nuxeo Note
CLA (License Agent) CLA_V1 R43.0.0 2019-12-04 INF-19-000396
CLM (License Management) CLM_V1_R1.22.0.0 2019-12-03 INF-19-000386
ODC Personal Edition ODC-PE V7 R1.47.92 2022-11-11 INF-22-000264
5.5 Operating systems

Operating System Name Operating System Version
Windows 10 (32 bits) - only Pro and Enterprise Editions Supported for both SIP and HFA Stackless variant
(“N” Editions are not supported)
5.6 Compliant products

This section lists the versions associated with the communication platforms, other products and third-
party products that have been tested for use with this version of the product and are known to work.
5.6.1 Communication platforms

Hardware and software products that have been tested together with this version of the product are
listed in the common compatibility matrix, which also includes the respective versions required to use
with the current version of this product.
The current Common Compatibility Matrix can be found on the Atos Unify Partner Portal
https://unify.com/en/partners/partner-portal under Sell - Portfolio Information.
Note: Use the “Search & Find” option under Portfolio Information and Search Documentation for “Common
Compatibility Matrix” (search on title only!).
Microsoft Outlook
ODC-PE V7 is compliant with MS Outlook (2007, 2010, 2013 and 2016) via:
- OpenScape “Click-To-Dial” button available for Microsoft Office 2007, 2010, 2013 and 2016, for
both x86 and x64 Outlook versions.
- The Microsoft Outlook Integration, that enables Microsoft Outlook users to deploy features of the
OpenScape Personal Edition (direct access to Outlook Contacts from our client) is available only for
32-bit versions of Microsoft Office 2007, 2010, 2013 and 2016.

5.6.1.1 ODC-PE Standalone ➔ SIP only
Preferred Software Versions1

Product Family Product
Version Status Nuxeo Note
Check SWS for
V6 R0 V6 R0.x GA
latest load
Check SWS for
V7 V7 R1.x GA
latest load
Check SWS for
V7 R2 V7 R2.x GA
latest load
DLS Check SWS for
V10 R0 V10 R0.x GA
latest load
Check SWS for
V10 R1 V10 R1.x GA
latest load
V10 R2
Check SWS for
V10 R2.4.0 V10 R2.x GA
latest load
(HI-DLS10R2.627.00)
HiPath 2000 not released
OpenScape Check SWS for
V2 V2 Rx GA
Business latest load
V7 not released
Check SWS for
V7 R1 V7 R1.x GA
latest load
Check SWS for
V7 R2 V7 R2.x GA
OpenScape 4000 latest load
Check SWS for
V8 V8 Rx GA
latest load
Check SWS for
V10 V10 R0 GA
latest load
Check SWS for
OpenScape Voice V7.1 V7 R1.x GA
latest load
Check SWS for
OpenScape Voice V8.0 V8 R0.x GA
latest load
Check SWS for
OpenScape Voice OpenScape Voice V8.1 V8 R1.x GA
latest load
Check SWS for
OpenScape Voice V9 V9 Rx GA
latest load
Check SWS for
OpenScape Voice V10 R0 V10 R0.x GA
latest load
OpenScape Voice V10 R1 Check SWS for
V10 R1.x GA
V10 R1.8.2 latest load

5.6.1.2 ODC-PE Standalone ➔ HFA Stackless only

V6 R0 Check SWS for
V6 R0.x GA
latest load
Check SWS for
V7 V7 R1.x GA
latest load
Check SWS for
V7 R2 V7 R2.x GA
latest load
DLS Check SWS for
V10 R0 V10 R0.x GA
latest load
Check SWS for
V10 R1 V10 R1.x GA
latest load
V10 R2
Check SWS for
V10 R2.4.0 V10 R2.x GA
latest load
(HI-DLS10R2.627.00)
OpenScape 2000 not released
-- not
HP3000 V7
released --
Check SWS for
OpenScape 3000 HP3000 V8 R5 V8 R5.x GA
latest load
Check SWS for
HP3000 V9 R2 V9 R2.x GA
latest load
V7 (SL HFA only with Check SWS for
OpenScape 4000 V7 R2.24.x GA
SoftGate) latest load
V8 (SL HFA only with Check SWS for
V8 Rx GA
SoftGate and STMIX) latest load
Check SWS for
V10 V10 R0 GA
latest load
OpenScape Check SWS for
V2 V2 Rx GA
Business latest load

5.6.1.3 ODC-PE VDI ➔ SIP only

Check SWS for
V7 V7 R1.x GA
latest load
Check SWS for
V7 R2 V7 R2.x GA
latest load
Check SWS for
V10 R0 V10 R0.x GA
DLS latest load
Check SWS for
V10 R1 V10 R1.x GA
latest load
V10 R2
Check SWS for
V10 R2.4.0 V10 R2.x GA
latest load
(HI-DLS10R2.627.00)
V7.15 LTSR
Citrix XenApp
V7.16 LTSR
Citrix Receiver 4.9.0.2539 (14.9.0.2539)
Citrix Workspace
19.3.0.4 (1903)
App
Check SWS for
OpenScape Voice V7.1 V7 R1.x GA latest load
Check SWS for
OpenScape Voice V8.0 V8 R0.x GA latest load
Check SWS for
OpenScape Voice OpenScape Voice V8.1 V8 R1.x GA latest load
Check SWS for
OpenScape Voice V9 V9 Rx GA
latest load
Check SWS for
OpenScape Voice V10 R0 V10 R0.x GA
latest load
OpenScape Voice V10 R1 Check SWS for
V10 R1.x GA
V10 R1.8.2 latest load
Notes:
1 We recommend customers use the “Preferred Software Version” for the given products. The
preferred software versions offer higher levels of functionality. However, the OSCV solution can also
operate with “Backward Compatibility” software.
The current Common Compatibility Matrix can be found on the Atos Unify Partner Portal
https://unify.com/en/partners/partner-portal
under Sell - Portfolio Information.
“Backward Compatibility”, with the caveat that recently added interoperability or advanced features
may not be possible when using these versions. In some cases, if a defect is found when using a
backward compatible version, it may be necessary to update to the preferred version.
5.6.2 Other products

5.6.3 Third-Party products


6 Service Information
6.1 Management information base
☐ Product sends SNMP V2 traps ☐ Product sends SNMP V3 traps ☐ Not supported
The following MIBs are supported:
6.2 License management

This product is licensed using:
☒ CLS ☐ CSC ☐ Other or not relevant, as described below
6.3 Remote serviceability

This product is certified for the following:
☐ RSP ☐ HiSPA ☐ RTPatch ☐ Other remote access or not relevant, as described below
6.4 Product tooling structure

Main Category Applications
Product Family OpenScape
Product OpenScape Personal Edition
Product Version V7 R1.47.92
Product Item Number P30152-P1510-C1-W8
6.5 Case tracking system

Tickets can be generated and tracked via the Atos WEB Support Portal (AWSP).
http://atosunify.service-now.com/unify
A short instruction can be found on the AWSP directly.
7 Documentation Reference
The product documentation can be found on the Atos Unify Partner Portal
https://unify.com/en/partners/partner-portal under Sell - Portfolio Information.
8 References
Further related information can be found under the following links:
Description Link
Start SWS Main Page https://sws.unify.com/SWS/SWSIntra.aspx
ODC-PE Installation and https://nuxeo.unify.com/nuxeo/site/proxy/nxdoc/view/pdf/9b1ec65
Administration guide b-ada7-48ae-a3af-4850fd60d9c2
ODC-PE User guide https://nuxeo.unify.com/nuxeo/site/proxy/nxdoc/view/raw/b6f3a2b
0-9266-4852-8fce-2f64907f409b

ODCPE V7R1.47.92 ReleaseNotes 2.07

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ODCPE V7R1.47.92 ReleaseNotes 2.07

Uploaded by

Copyright:

Available Formats

Public

Atos Unify OpenScape Desktop Client Personal Edition V7

Export Control Classification Data

1 HISTORY OF CHANGE ............................................................................................. 3

Release Notes Page 2 of 61

1.2 Product versions history

Release Notes Page 3 of 61

Software Version Production Version Date Remarks

Release Notes Page 4 of 61

Tracking Internal Summary Released

RQ00042977 UCBE-29344 Emergency call disclaimer should be presented. V7 R1.47.88

RQ00042675 UCBE-27287 OS Personal Edition Diversion Header Support. V7 R1.47.83

RQ00042412 WhiteNoise in HKEY_CURRENT_USER - Part2 V7 R1.47.78

RQ00042559 Disable PE device features via DLS V7 R1.47.78

RQ00042553 Disable PE desktop notifications via DLS (PE side) V7 R1.47.77

RQ00042333 Auto profile creation for OpenScape Desktop Client V7 R1.47.77

RQ00042412 WhiteNoise in HKEY_CURRENT_USER V7 R1.47.77

UCBE-25309 Project: split channels - SETUP changes. V7 R1.47.75

UCBE-25305 Project: split channels. V7 R1.47.75

UCBE-23059 ODC-PE support for the NG112 project. V7 R1.47.72

UCBE-19700 Silent Monitoring with Whisper. V7 R1.47.61

UCBE-15931 ODC PE should support Tel URI protocol. V7 R1.47.50

RQ00041355 Change number of characters for Digest Authentication. V7 R1.47.49

UCBE-10524 Project: ODC-PE - Basic uaCSTA support. V7 R1.47.38

Release Notes Page 5 of 61

Tracking Internal Summary Released

UCBE-10529 Project: ODC-PE - License Mechanism. V7 R1.47.38

UCBE-11108 ODC PE: SoftOla TLSv1.2 support - OSBiz. V7 R1.47.38

DCMP Support V7 R1.47.28

FRN10072 UC Softphone: Support of Sennheiser Headsets V7 R1.47.15

FRN9838 UC Clients: Support JabraUSBHidTelephonySDK_V1.0 V7 R1.47.15

UCBE-53 Clients Support of Windows 10 V7 R1.47.15

UCBE-50 softphone support new Plantronics Spokes 3.0 interface. V7 R1.47.15

Release Notes Page 6 of 61

2.1.1 Manual configuration of TLS protocol via ODC-PE (HFA Stackless).

Release Notes Page 7 of 61

2.1.2 Emergency call disclaimer

Figure 2. Example of Emergency call Disclaimer

Release Notes Page 8 of 61

Figure 3. Example of Emergency call Disclaimer

Release Notes Page 9 of 61

2.2 Resolved Reported Problems / Symptoms

Tracking Internal Summary Released in

PRB000062606 UCBE-31379 ODC-PE frequently without payload. V7 R1.47.92

UCBE-31413 ODC-PE: Sennheiser audio scheme is removed after V7 R1.47.92

UCBE-31390 ODC-PE: SecomSDK.exe is not started in some computers. V7 R1.47.92

PRB000060651 UCBE-30855 ODCPEV70R1.47.88 problem when using multiple monitors V7 R1.47.91

ODC-PE: newer versions (like V7 R1.47.80 and V7 R1.47.88) V7 R1.47.90

PRB000055141: ODC-PE Directory search with "ü" is not V7 R1.47.90

Allow manual configuration of TLS transport protocol in V7 R1.47.89

ODC-PE shows "Sammelanschlus" instead "Hunt Group" in V7 R1.47.89

CLONE - ODC-PE: Poly Calisto 5300: Ringtone is not V7 R1.47.89

Release Notes Page 10 of 61

Tracking Internal Summary Released in

Checking and clarifying dependency with Visual C++ 2010 V7 R1.47.88

PE after deactivating the local function "second call" via V7 R1.47.87

Problem with OpenScape Desktop Client on Display with V7 R1.47.87

PRB000055698 UCBE-29058 ODC-PE: Digital Signature expired. V7 R1.47.86

PRB000055566 UCBE-28961 ODC PE is using unsecure log4net.dll 1.2.13.0. V7 R1.47.86

ODC-PE incoming call tone control failure if auto answer is V7 R1.47.85

ODC-PE No discrete notification when changing job via V7 R1.47.85

2.3 Resolved Vulnerabilities

Release Notes Page 11 of 61