Mod01 GL OSAV100SDS CD3343EN00CD PDF

20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Welcome to this Web Based Training, which is about the new OpenScape UC V10
C
features, released in December 2019.

00
E N
43
33
D
C
DD4353FN10DD_BACZZZWTRM
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Let’s start with the introduction.

C
00
E N
43
33
D
C
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
The release software candidates are:

C
00
• OpenScape UC V10 R0.3.0 120300 - Please always have a look at the latest
release notes, if new software candidates have been released
E N
• For Fusion for Office it is V2.0.1.0 build 111 or later – Again, check the latest release
43
notes.
33
D
C
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Please note the following:

C
00
• WebClient 1.0 is no longer supported. It is not even possible to open this web page.
Also, the WebClient 1.0 API is no longer available.
E N
• WebRTC Clients for MacOS and Linux will be released as a late feature. This also
43
means that there is a WebRTC client, on a browser basis, which can run on a
33
Windows operating system.

D
C
• A new OSMO Pro version 1.2.0 supports Android Push Notification against SBC
• Like it is for every new version, new OpenScape UC licenses are required. Please
bear in mind that this statement is valid for OpenScape User Management as well.
CMP User Manager is now also on version 10
• To carry out an upgrade from OpenScape UC V9, create an osc-setup repository
with the basic OpenScape UC V10 ISO files, including the latest hotfix, and carry
out „osc-setup“
• Direct upgrade from V7R3 is not supported, you must upgrade to V9R4 first. After
this, you can perform the previously described step. Or you should wait until a new
version of upgradeUC is available. Please keep in mind that in case of upgradeUC
usage, a fresh installation of OpenScape UC is required, where the identical knut
responsefile.txt configuration is required. Only the deployment type can be changed
to a larger one.
• Currently, the only released operating system is SLES12 service pack 4. When this
service pack becomes outdated, the next released service pack 5 will be supported
instead. There are no plans to support SLES 15.
In the case of OpenScape UC on SLES 11 SP4, upgrade the operation system to
SLES 12 SP4 first, before you perform the upgrade of OpenScape UC to version10
3
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Now let us talk about the ‘Feature Overview’

C
00
• Finally, OpenScape UC WebClient supports chat conversations with attachments.

N
• The WebClient of OpenScape UC V10 is designed to support Screen Reader

E
applications
43
33
• There can be a coloured frame around the point of focus in the WebClient V10. Also,
a browsers High Contrast mode is supported.
D
C
• WebClient V10 supports navigation using the tab key, the arrow keys and many pre-
defined hot keys
• Beside the Contact Filtering, the Contact Search in all connected Global Address
Books now supports the transformation of all German ‘Umlaut’ into the appropriate
substitutes.
• Fusion for Office now offers a better way to notify the user about incoming
notifications by supporting a beep, or the feature ‘text to speech’
• Fusion for Office has an improved Favourites Panel
• And Fusion for Office can now be used in a VMWare Horizon infrastructure in CTI
and SIP mode
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• OSMO Pro for Android is already released with Push Notification Support
C
00
• And in December 2019 the feature ‘OSV Backup OND Routing’ was tested with
OpenScape UC V9R4. As soon as the feature has been implemented successfully
E N
in V9R4, it will be implemented in OpenScape UC V10 as well.

43
33
D
C
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
The OpenScape UC V9R4 late features are:

C
00
• The integration of the OpenScape Xpressions announcement management

integrated into the OpenScape UC WebClient.
E N
• And the opportunity to create Visibility Groups and assign them to OpenScape UC
43
users via the CMP.

33
D
C
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
So, what’s new in conjunction with the OpenScape UC feature - Chat?

C
It is the opportunity to transmit attachments during a chat.

00
E N
43
33
D
C
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Both OpenScape Fusion V2 and OpenScape Web Client (UC V10) allow users to
C
send files attached to chat messages.

00
• Therefore, an additional Web Server (or file server) will be installed on Openfire
E N
automatically.
43
33
D
C
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
There a slight difference between OpenScape Fusion V2 and OpenScape Web Client
C
(UC V10) as to how to open an attachment.

00
• In OpenScape Fusion V2, images are presented directly within the conversation, but
E N
other files can be downloaded, saved and opened through buttons that appear when
43
hovering.
33
• OpenScape WebClient (UC V10), images are also presented directly within the
D
conversation, but other files can be downloaded, saved and opened via the browser.
C
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
When a UC user wants to upload an attachment during a chat conversation, the first
C
message will be sent from the UC client through all UC components and through the
00
Openfire up to the HTTP File Upload Web Server. This message is “request to upload
EN
a chat attachment”.
43
33
D
C
10
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
The response from the HTTP File Upload Web Server is a URL, which has to be
C
addressed by the UC client. This URL contains the FQDN of the HTTP File Upload
00
Web Server.
EN
43
33
D
C
11
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Now the UC client addresses the previous transmitted URL and uploads the chat
C
attachment onto the HTTP File Upload Web Server. On this server, individual folders
00
will be created for every single conversation. The folder name is the group chat ID, or
EN
in the case of a 1-to-1 chat, a string that has been calculated based on both user IDs.
43
33
D
C
12
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
In the next step, the UC client that will receive the chat attachment, sends a request to
C
the HTTP File Upload Web Server, to download the attachment.

00
EN
43
33
D
C
13
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
First, the HTTP File Upload Web Server has to confirm the request with HTTP_200
C
OK” then in the second step, it will send the chat attachment to the UC client.
00
EN
43
33
D
C
14
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Openfire has a new directory for this feature: /opt/openfire/httpfileupload

C
00
• This directory contains the configuration file: httpfileuploadcomponent.conf

EN
43
33
D
C
15
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The feature “Chat Attachment” uses the “HTTP File Upload Web Server”, which
C
loads the properties of the following configuration file:

00
httpfileuploadcomponent.conf
EN
43
The following is only for informatino purpose:

33
• All supported properties and a description of them can be displayed with the
D
C
following Java command:

/opt/siemens/share/ibm-java-x86_64-80/jre/bin/java –jar
/opt/openfire/httpfileupload/httpfileuploadcomponent.jar
–help
16
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• On this, and on the following slides, the properties of the configuration file
C
httpfileuploadcomponent.conf are listed and described:

00
• The value of the property ‘announcedWebHost’ is the hostname or IP address that is

EN
to be used by the end users and is part of the transmitted URL.

43
• The value of the property ‘announcedWebPort’ is the TCP port number that is to be
33
used by the end users and is also part of the transmitted URL.
D
The default port number is 12121.

C
• The value of the property ‘announcedWebProtocol’ is the protocol that is to be used

by the end users.
The default value is the protocol “http”.
• The value of the property ‘domain’ is the domain that will be used for the component
with the XMPP domain
The default domain name is “upload”.
• The value of the property ‘fileRepo’ is the definition of a directory provided by the file
system to store the attached files. The path must exist.
The default path is “/opt/openfire/httpfileupload/storage”. It can also be a network
share. In this case you have to make sure that the user “root” has permanent
access to this share, even after system restart.
• The value of the property ‘httpMaxThreads’ is the maximum number of threads that
the HTTP server can spawn.
The default value is 200.
17
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The value of the property ‘httpMinThreads’ is the minimum number of threads that
C
the HTTP server can spawn.

00
The default value is 8.

EN
• The value of the property ‘maxFileSize’ is the maximum allowed size per file, in
43
bytes. Use a value of -1 to disable the file size limit. The default is 5242880 bytes (or
33
five MB).
D
• The value of the property ‘maxOccupancy’ is the maximum allowed occupancy of

C
the hard disc. No further attachments will be stored after this threshold has been
reached.
The default is 0.9, which means 90% usage.
• The value of the property ‘mimeWhitelist’ is a whitelist of supported MIME types. A
MIME type defines the file extension and the standard operating system program,
that should be used to open this attachment.
The defaults are: application/pdf, image/jpeg, image/png, image/gif and text/plain
18
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Additional supported MIME types have to be added manually!

C
00
EN
43
33
D
C
19
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Only the listed MIME types can be transmitted in a chat!

C
00
EN
43
33
D
C
20
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
The value of the property ‘sharedSecret’ is used to authenticate this component with
C
the XMPP domain and must not be changed!

00
EN
43
33
D
C
21
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The value of the property ‘tempFileRepo’ is ‘true’ or ‘false’ and defines whether files
C
should be stored in the temporary directory provided by the file system.

00
• The value of the property ‘timerDuration’ is the duration expiration timer in minutes,
EN
to define the time a client has to upload a file.

43
The default duration is 5 minutes.

33
• The value of the property ‘webHost’ is the hostname or IP address on which the
D
webserver will run. It defaults to an arbitrary, non-local address.

C
• The value of the property ‘webPort’ is the TCP port number that the webserver
listens on.
The default TCP port number is 12121.
• The value of the property ‘xmppHost’ is the FQDN or IP address of the Openfire
server (not the XMPP Domain Name) that this component will connect to. It defaults
to 'localhost'.
22
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The value of the property ‘xmppMaxQueueSize’ is the maximum size of the XMPP
C
server (or Openfire) message queue. The typical value of this property is 1000.
00
• The value of the property ‘xmppMaxThreads’ is the maximum number of threads

EN
that the XMPP server (or Openfire) will spawn. The typical value of this property 17.
43
• And finally, the value of the property ‘xmppPort’ is the TCP port number on the
33
xmppHost (or Openfire), to which a connection will be made. The default value of
D
this property is 5275.

C
23
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• An empty white list will allow all kind of files to be sent. Therefore this is not a
C
recommended configuration for security reasons.

00
• UC clients (Fusion and WC) use MIME ‘application/octet-stream’ as default MIME.

EN
This means that any file without a MIME definition is going to be identified with this
43
MIME.
33
• To keep control of what is being transferred via UC Chat, this MIME should never be
D
included in the White list.

C
24
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
This table describes the default MIME types, which are set by default after the
C
Openfire installation:
00
• The property “text/plain” - The parameter of this main type is the specification of a
EN
character set. Sub-type, predefined plain text without formatting.

43
• The property “image/jpeg” defines the sub-type for images, which is JPEG.
33
• The property “audio/basic” defines the sub-type for sound, where the codec of the
D
C
ISDN is predefined.
• The property “video/mpeg” defines the sub-type for movies, which is MPEG.
• The property “application/octet-stream” is intended to save the data and not
explicitly to start an application program.
• The property “application/postscript” defines the sub-type which should lead to the
printing of the data.
25
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Some more examples of mimes for the white list:

C
00
• image/gif,
EN
• image/png,
43
• image/bmp,
33
• audio/wav,
D
• audio/mpeg,
C
• video/x-msvideo,
• video/mp4,
• video/avi,
• application/pdf,
• application/msword,
• application/x-zip-compressed,
• application/zip,
• application/x-msdownload,
• application/vnd.openxmlformats-officedocument.wordprocessingml.document,
26
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Based on the transmitted Chat ID a new directory will be created for every single
C
chat session, which contains the transmitted attachments:

00
/opt/openfire/httpfileupload/storage/<chatID>
EN
• In case of an attachment in a group chat, the group <chatID> is taken as directory

43
name such as in the example shown here.

33
The ID of all active group chats is displayed within the Openfire Admin Console
D
under Group Chat > Room Administration

C
• In the case of an attachment in a 1-to-1 chat, no <chatID> exists. In this case the
directory name is calculated based on the UUIDs of both participants, as per the
example shown
27
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• A <chatID> sub-directory contains every single attachment, file by file.

C
00
• But all files have been renamed and file extensions don’t exist anymore.
EN
43
33
D
C
28
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Next is a short description, of how attachments work with OpenScape Fusion V2.
C
00
• Images can be attached,

EN
43
33
D
C
29
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• via “drag-and-drop” into the content line,

C
00
EN
43
33
D
C
30
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• or by clicking on the paperclip icon and selecting the file that should be attached.
C
00
EN
43
33
D
C
31
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• or via copy and paste

C
00
EN
43
33
D
C
32
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Images are presented directly in the conversation.

C
00
EN
43
33
D
C
33
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• By clicking on an attached image file, the “Fusion Image Viewer” will be opened.
C
00
EN
43
33
D
C
34
C
D
33
43
EN
00
C
D
_R
._
C
av
ie
re
s_
31
-0
3-
20
35
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The “Fusion Image Viewer” displays all images, which have been transmitted during
C
this conversation.
00
EN
43
33
D
C
36
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Clicking on another image will enlarge it in the “Fusion Image Viewer”.

C
00
EN
43
33
D
C
37
C
D
33
43
EN
00
C
D
_R
._
C
av
ie
re
s_
31
-0
3-
20
38
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• By hovering the mouse over the enlarged image, the icon to download this image
C
becomes visible.
00
EN
43
33
D
C
39
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Other supported MIME types are displayed with a symbolic icon, which makes it
C
easy to identify the file type.

00
EN
43
33
D
C
40
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Before a file can be opened, it has to be downloaded into the Fusion for Office
C
default temporary download folder:

00
%localappdata%\unify\nativechat\<username>\conversation –<host>
EN
43
33
D
C
41
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Now it’s possible to open an attachment or save it in a folder.

C
00
EN
43
33
D
C
42
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The folder %localappdata%\unify\nativechat\<username>\conversation –

C
<host> will be created at Fusion startup automatically.

00
EN
43
33
D
C
43
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• This folder contains all supported icons and contact pictures of stored chats after
C
Fusion startup.
00
EN
43
33
D
C
44
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• As soon as a chat has been opened, individual subfolders will be created for all
C
attached and automatically displayed images.

00
EN
43
33
D
C
45
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• An image folder contains the image in the original size and a copy of it in a
C
“thumbnail” size.
00
EN
43
33
D
C
46
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• As soon as a “non-image” attachment type has been downloaded, a new subfolder

C
will be created.
00
EN
43
33
D
C
47
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• An “non-image” folder contains the downloaded file in the original size.

C
00
EN
43
33
D
C
48
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• This folder will be deleted automatically at Fusion shutdown.

C
00
EN
43
33
D
C
49
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• And now a short description of how attachments work in OpenScape WebClient

C
V10:
00
• Images are presented directly in the conversation.

EN
43
33
D
C
50
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• By clicking on an attached image file, the image will be opened in the browser
C
viewer.
00
EN
43
33
D
C
51
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Clicking on another image will enlarge it in the browser viewer.

C
00
EN
43
33
D
C
52
C
D
33
43
EN
00
C
D
_R
._
C
av
ie
re
s_
31
-0
3-
20
53
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• A right mouse-click on any of shown images will open a small browser window,
C
which offers the feature to download the selected one.

00
EN
43
33
D
C
54
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Other supported MIME types are displayed with a symbolic icon, which makes it
C
easy to identify the file type.

00
EN
43
33
D
C
55
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Attachments will be downloaded every time, whenever they are opened.

C
00
EN
43
33
D
C
56
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Now the browser offers two features:

C
00
– Open the attachment with a program or Save the file

EN
43
33
D
C
57
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
OpenScape UC WebClient Screen Reader support

C
00
EN
43
33
D
C
58
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• UC V10 is also improved, with basic functionality for screen readers (such as Jaws)
C
and the idea is to continue this improvement in further releases.

00
• In the JAWS Settings Center, the following configuration is recommended for

EN
WebClient usage.
43
33
D
C
59
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Select the “Application” to be configured. In this example it is “Chrome”.

C
00
EN
43
33
D
C
60
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Select in:
C
“User > Typing Echo”

00
“Typing Echo” = “Words”

EN
43
33
D
C
61
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Select in:
C
“Web / HTML / PDFs >

00
Reading > Web Verbosity Level” = “Low”

EN
43
33
D
C
62
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Also in Reading, uncheck the feature: “Speak Access Keys Within Web Pages”
C
00
EN
43
33
D
C
63
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Select in:
C
“Web / HTML / PDFs >

00
Images / Graphics” > “For an Image” = “Alt Text”

EN
43
33
D
C
64
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Select in:
C
“Keyboard > General > Navigation Quick Keys”

00
“Navigation Quick Keys” = “Off”

EN
43
33
D
C
65
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
OpenScape WebClient improvements for Navigation and High Contrast

C
00
EN
43
33
D
C
66
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• We now support keyboard navigation with the tab and arrow keys.
C
00
• But how do we know where the current place of focus is in the WebClient?
EN
43
33
D
C
67
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• A coloured frame around the UI element can be enabled to help users during
C
navigation.
00
EN
43
33
D
C
68
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Like that shown here on this page.

C
00
EN
43
33
D
C
69
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• With V10 it is possible to enable a feature, such that the “Tab” key has to be pressed
C
after a “Search” string has been entered.

00
EN
43
33
D
C
70
C
D
33
43
EN
00
C
D
_R
._
C
av
ie
re
s_
31
-0
3-
20
71
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• This moves the focus on to the “magnifying glass”.

C
00
EN
43
33
D
C
72
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Now, “Enter” can be pressed to initiate the search.

C
00
EN
43
33
D
C
73
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The support of high contrast already exists from previous versions. (UCV9R4 or
C
earlier).
00
EN
43
33
D
C
74
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• A browser plug-in has to be installed to modify the colours of a web page.

C
00
EN
43
33
D
C
75
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• In addition, UC V10 supports high contrast mode for the header bar only.
C
00
EN
43
33
D
C
76
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• This feature is required to change the contrast in the header bar, even if high
C
contrast is already enabled.

00
EN
43
33
D
C
77
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• This feature adds the effect to the header bar even if high contrast is not enabled.
C
00
EN
43
33
D
C
78
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
OpenScape WebClient Keyboard Navigation and Hotkey Support

C
00
EN
43
33
D
C
79
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Hotkeys were created for the main functionalities.

C
00
EN
43
33
D
C
80
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Alt+K opens a help window to display the list of these keyboard shortcuts in IE,
C
Edge and Chrome

00
EN
43
33
D
C
81
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Alt+Shift+K opens a help window to display the list of these keyboard shortcuts in
C
Firefox.
00
EN
43
33
D
C
82
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• This table lists the OpenScape UC Keyboard Navigation Hotkeys, provided by

C
Internet Explorer, Edge and Chrome.

00
EN
43
33
D
C
83
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Whereas this table lists the OpenScape UC Keyboard Navigation Hotkeys, provided
C
by Firefox.
00
EN
43
33
D
C
84
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• It is important to remember that Fusion already has several hotkeys for different
C
functions.
00
• The differences in Hotkey support from OpenScape Fusion for Office V1R8, are that
EN
the following additional hotkeys are supported:

43
– + Hotkey for “Open Fusion Bar”

33
– + Hotkey for “Repeat announcement of notification”

D
C
• Keep in mind the Fusion for Office enabled hotkeys overwrite the default operation
system hotkey configuration.
85
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Contact Search with German ‘Umlaut’

C
00
EN
43
33
D
C
86
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• With UC V9R0 Contact Filtering of the Private Contact List supports the feature to
C
transform the German “umlaut”:

00
• Ä with an umlaut into ae

EN
• Ö with an umlaut into oe

43
33
• And ü with an umlaut into ue

D
• With UC V10R0, this feature is also supported in the case of a Contact Search in
C
the Global Contact List and all connected Global Address Book Servers (or LDAP)
87
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
As an example, let’s carry out a Contact Search:

C
00
• Enter a search string with an Umlaut, e.g. “smö” and press „Enter“ to get a search
result.
EN
43
33
D
C
88
C
D
33
43
EN
00
C
D
_R
._
C
av
ie
re
s_
31
-0
3-
20
89
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The result is that Global Contact List contacts are listed, where the Last Name or
C
the First Name starts with “smoe”.

00
EN
43
33
D
C
90
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• In general, other languages, like Russian, Polish or Chinese are also supported in
C
the case of a Contact Search.

00
EN
43
33
D
C
91
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Fusion for Office V2 Notifications

C
00
EN
43
33
D
C
92
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Incoming calls, team calls and chat messages can be announced by Fusion for
C
Office V2.
00
EN
43
33
D
C
93
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The announcement can be received via a “Beep” or “Name” or both together.

C
00
EN
43
33
D
C
94
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The default Windows audio engine is used to play a beep or speak the function
C
(“Ringing”) and the originator´s name (“Irmi Innig”).

00
EN
43
33
D
C
95
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The “text-to-speech” is based on the Microsoft Windows Speech configuration.

C
00
EN
43
33
D
C
96
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Fusion for Office V2 Favorites Panel

C
00
EN
43
33
D
C
97
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• With Fusion V2, a user is able to dock the favorites panel to the Fusion tool bar.
C
00
EN
43
33
D
C
98
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• To open the “Favourites Panel” menu, click on the “3-point-icon” in the top left corner
C
00
EN
43
33
D
C
99
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
A menu will be opened

C
00
EN
43
33
D
C
100
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The “Favorites Panel” can be “Docked” and “Undocked” against the “Fusion Bar”
C
00
EN
43
33
D
C
101
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Click on “Layout” to change how it looks.

C
00
EN
43
33
D
C
102
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• A submenu opens, where one of three layout types can be selected:

C
00
– Detailed
EN
– Compact
43
– Pictures
33
D
C
103
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Shown here is the detailed view.

C
00
• Followed by the compact view.

EN
• And finally we have the picture view.

43
33
D
C
104
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• By clicking on “Search”, the “Favourites Panel” will be enlarged to offer the “Search”
C
functionality.
00
EN
43
33
D
C
105
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• By pressing “Enter” the search procedure will be carried out.

C
00
EN
43
33
D
C
106
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Fusion for Office V2 in VMWare Horizon

C
00
EN
43
33
D
C
107
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
There are already two known deployment modes of Fusion for Office:
C
00
• Fusion as a UC CTI client. (or Fusion in CTI mode)

EN
– For operation as CTI client, Fusion for Office has to be installed in the Horizon
Pools like any other application.
43
33
• Fusion as a UC CTI client including a SIP Softphone (or Fusion softphone)

D
– For operation as CTI + Softphone, in addition to the installation in the Horizon

C
Pools, a Fusion VDI component has to be installed on the user´s machines.

This is what it is called ‘VDI operation in virtual environments’.
108
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
The Fusion VDI component functions like the Windows “Remote Audio” driver, which
C
runs on the local machine.

00
EN
43
33
D
C
109
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• This is similar to what is already released for Citrix, in previous Fusion for Office
C
versions.
00
EN
43
33
D
C
110
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• This drawing shows an overview of the internal communication paths

C
00
EN
43
33
D
C
111
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Fusion V2 is also prepared to offer an offline media solution for VMWare Horizon.
C
00
EN
43
33
D
C
112
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The Fusion for Office VDI Component has to be installed on the client pc, where the
C
VMWare Horizon Client has been installed.

00
The Fusion4Office VDI Component is in between the Windows operating system

EN
and the VMWare Horizon Client.

43
33
D
C
113
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
OpenScape Fusion for Office has to be installed in the VMWare Horizon Farm, on
C
the Windows Terminal Server or the Windows Desktop pc.

00
EN
43
33
D
C
114
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
After the VMWare Horizon Client has established the connection against a Windows
C
Terminal Server or the Windows Desktop pc of the Horizon Pool, a virtual channel
00
has been opened.

EN
43
33
D
C
115
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Now OpenScape Fusion for Office can be started on the remote computer.
C
OpenScape Fusion for Office will establish directly the connection against the DLS
00
and the OpenScape UC Frontend server.

EN
43
33
D
C
116
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
But the SIP registration and SIP communication of the softphone is against the
C
OpenScape Voice or the SBC, and in the case of a call, the RTP stream will be
00
handled by the Fusion for Office VDI Component on the local computer.
EN
43
33
D
C
117
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
The supported Horizon deployment modes are:

C
00
First, Windows Server RDS (virtual desktop sessions):

EN
• Which consists of publishing applications on a Windows Server operating system.

The Windows Server operating system is shared with the users, that can then
43
access a virtual desktop session.

33
Second is Virtual Desktop:

D
C
• Which consists of providing remote PC access to a Windows Desktop operating

system.
Each user accesses their own Desktop, without sharing it with other users.
118
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
On this slide, you can see a screenshot of the VMWare Horizon 7 Administrator, and
C
what the source assignment of a configured Windows Terminal Service looks like.
00
EN
43
33
D
C
119
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
And on this slide, you can see a screenshot of the VMWare Horizon 7 Administrator
C
and what the source assignment of Virtual Desktops looks like.

00
EN
43
33
D
C
120
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Important Notes:
C
00
• The Horizon client must be installed before the installation of VDI component
(vdi.exe), otherwise an important REGISTRY Key will not be created and VDI will
EN
not work.
43
33
The details are shown here.

D
• HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware
C
VDPService\Plugins\OpenScape.VdpService\
• dll = C:\Program Files (x86)\Unify\OpenScape Desktop Client VDI
Softphone\bin\horizon\client64\vdiclient.dll
121
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Only the official VMWare Horizon Client application is supported, HTML access and
C
Horizon client from the Microsoft Store have no support.

00
• The VDI component must be installed by executing the installer "vdi.exe" on the
EN
local desktop client computers.

43
• The prerequisites for the VDI component are automatically downloaded from the
33
internet, if they are not already present.

D
C
• If no internet connection is available, the prerequisites can be installed through the

"prerequisites" package before installing the VDI component.
122
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The Firewall on the local pc has to be configured by the system administrator to

C
allow incoming SIP signalling from OpenScape Voice, otherwise Fusion for Office
00
will not be able to establish voice calls.

EN
• After login to the Horizon VM, Fusion for Office is already installed or users may
43
install Fusion for Office like any other application (with administration rights).
33
• Fusion for Office on a Horizon VM uses the: “Virtual SIP Service Provider”
D
C
123
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
In this section, we’ll look at OSMO Pro improvements

C
00
EN
43
33
D
C
124
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• To use OSMO Pro with Android Push Notification support, the required SBC version
C
V9_R4_12_xx or higher must be used.

00
• The outgoing network traffic from OSMO Pro devices goes over the ports: 5228 –
EN
5230 and an existing Firewall must have those ports opened.

43
• The required OSMO Pro version is 1.2.0 or higher.

33
• Both OSMO Pro flavours, (Push enabled or not) are supported for a period of time,
D
C
until HAProxy/UC push notification is implemented

• Therefore it is possible to have the feature ‘SIP Push Notification’ disabled…
125
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
….or enabled.
C
00
EN
43
33
D
C
126
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• But be warned that VoIP calls fail, if the Server does not support Android Push
C
Notification.
00
EN
43
33
D
C
127
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The required SBC version V9_R4_12_xx already provides the default Google
C
Firebase certificate, which is visible under “Certificate Management”.

00
EN
43
33
D
C
128
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The correct “Certificate Profile” has already been assigned to be used as: “Android
C
Push certificate profile”.

00
EN
43
33
D
C
129
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• In the “Push Notification Service” configuration, the default “Firebase Database

C
URL” is not visible.

00
• The “Firebase Database URL” field must only be completed with the client Firebase
EN
Database URL, in the case of an individual user certificate upload.

43
• This would be the case, if a customer already uses some other Firebase Cloud
33
services, and wishes to use their own existing certificate for our SIP Push
D
Notifications.
C
130
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• All required components are visible on this slide.

C
00
• There is an existing OSMO configuration for the Main Device ONS.

EN
43
33
D
C
131
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• When OSMO Pro has been started on the Android smartphone, OSMO Pro
C
registers itself against the Google Firebase.

00
EN
43
33
D
C
132
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• After successful registration, Google Firebase responds with an App/Device token to

C
inform OSMO Pro of the successful registration. This token will be used as an
00
identifier for this particular registered OSMO Pro App, and will be assigned to every
EN
further transmitted request for this OSMO Pro App.

43
33
D
C
133
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• During the OSMO Pro registration against the SBC, this Google Firebase token will
C
be transmitted to the SBC. The SBC has to keep the token for further requests.
00
EN
43
33
D
C
134
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• OSMO Pro stays inactive in the background of the smartphone. In fact, OSMO Pro
C
consumes very little power.

00
EN
43
33
D
C
135
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• If there is a call for the „Main Device ONS“ and if the OSMO Pro is registered, this
C
call will be forwarded to OSMO Pro automatically.

00
EN
43
33
D
C
136
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Now there will be a SIP INVITE sent from the OpenScape Voice to the SBC, to
C
notify OSMO Pro about an incoming call.

00
EN
43
33
D
C
137
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Then the SBC takes the stored APP/Device Token to inform the Google Firebase
C
about the incoming call for the registered OSMO Pro App.
00
EN
43
33
D
C
138
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Google Firebase processes this notification and as result, sends a ‘Push Notification’
C
to OSMO Pro.
00
EN
43
33
D
C
139
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Due to the ‘Push Notification’, OSMO Pro will be woken up on demand.

C
00
EN
43
33
D
C
140
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• After OSMO Pro has been woken up, the App sends the request “Call retrieve” to
C
the SBC.
00
EN
43
33
D
C
141
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The SBC answers with the forwarding of the ‘SIP INVITE’ message to OSMO Pro.
C
And finally, the incoming call will be signalled on the smartphone.

00
EN
43
33
D
C
142
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
In this OSMO Pro V10 roadmap:

C
00
The time line for “User Experience” shows upcoming changes in the OSMO Pro user
interface
EN
The time line for “Messaging” shows upcoming improvements to the OSMO Pro
43
feature “Chat” and other OpenScape UC messaging services.

33
The time line for “Security” shows upcoming improvements to supporting MDM
D
C
applications
The time line for “Architecture” shows upcoming changes to the internal
communication architecture. These changes have a massive impact on the direct link
of OSMO Pro against the Façade server, because in this situation these listed features
will no longer work.
The time line for “Other features” shows the upcoming implementation of other
features.
The time line for “Mobile Platforms” should be an identification, that OSMO Pro will be
kept ‘up to date’ and will always support the latest iOS and Android operating system.
143
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Note the start of OSMO V10, with a 1st drop planned for the end of January 2020.
C
00
EN
43
33
D
C
144
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
User Experience - Short term

C
00
User Interface Improvements for Call stage, Call history, Contacts

EN
• Today the user experience between OpenScape Mobile Pro and the OpenScape UC
Web or Fusion for Office client is different. With the planned UI improvements within
43
OpenScape Mobile Pro for Call stage, Call history, and Contacts, users will have the
33
same user experience as well as the same features set on the mobile app, as they
D
have with the OpenScape UC Web or Fusion for Office client, when working in the
C
office.
145
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Architecture - Short term

C
00
Moving to HA Proxy Call stage, Call history, Contacts and Chat

EN
• As already done for the new call control features plus conferencing, the Facade
server interfaces (Call stage, Call history, Contacts and Chat) will be moved step
43
wise to the new REST API (via HA Proxy) of the OpenScape UC Web and Fusion
33
for Office client. This will have the effect that an implementation of features on
D
OpenScape Mobile Pro, which are available already in the OpenScape UC Web and
C
Fusion for Office client, can be done with less effort. The effect of this architecture
change has as result, that OSMO Pro doesn’t work in an OpenScape UC V7
environment anymore.
146
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Other features - Short term

C
00
Feature Improvement – Rules

EN
• Switching Rules on and off, will be implemented to be used within the OpenScape
Mobile Pro app. The creation or changing of Rules needs to be done in the
43
OpenScape UC Web or Fusion for Office client. With this approach users have the
33
same feature set available on the mobile app as they have with the OpenScape UC
D
Web or Fusion for Office Client in the office.

C
147
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
User Experience - Short term

C
00
UI Improvements for Chat

EN
43
OpenScape Mobile Pro for Chat, users will have the same user experience as well
33
as the same feature set on the mobile app, as they have with the OpenScape UC
D
Web and Fusion for Office client when working in the office.
C
148
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Messaging - Short term

C
00
Chat attachments
EN
Web/Fusion for Office client is different. With the planned possibility to send and
43
receive Chat attachments within OpenScape Mobile Pro, users will have the same
33
user experience as well as the same feature set on the mobile app as they have
D
with the OpenScape UC Web and Fusion for Office client when working in the office.
C
149
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Security - Mid term

C
00
Support of MDM for Android

EN
• Support of Mobile Device Management (or MDM) additionally for Android, as we

have already implemented for iOS. Automatic rollout of user credentials via an MDM
43
system enables a higher level of security as well as reduced roll out times. Planned
33
providers are MobileIron, AirWatch and Citrix XEN Mobile as the three leading
D
platforms.
C
150
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
User Experience - Mid term

C
00
UI Improvements for other features

EN
43
OpenScape Mobile Pro the users will have the same options on the mobile app as
33
they have with the OpenScape UC Web or Fusion for Office client, when working in
D
the office (e.g. better Search and Call history functionality).

C
151
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Messaging - Mid term

C
00
Push Notifications (UC Part for iOS and Android)

EN
• The implementation of Push notification for the UC Part of OpenScape Mobile Pro
e.g. Chat, Presence and Preferred device for iOS and Android. A prerequisite to
43
accomplish this, is moving the required interface to the new REST API, via HA
33
Proxy. The technical implementation of Push notifications also has a performance

D
benefit to the mobile device, including an improved battery life.

C
152
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Architecture - Mid term

C
00
Moving to HA Proxy (other features)

EN
• As already done for the new call control features plus conferencing, additional
Facade server interfaces will be moved step wise to the new REST API (via HA
43
Proxy), of the OpenScape UC Web and Fusion for Office client. This will have the
33
effect that an implementation of features on OpenScape Mobile Pro, which are

D
available already in the OpenScape UC Web or Fusion for Office client can be done
C
with less effort. (e.g. better search and further feature functionality).
• The Value proposition is better feature implementation, architectural improvements
and reduced complexity.
153
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Other features - Mid term

C
00
URI Dialling
EN
• URI dialling enables the user to attend video conferences with other parties, from
OpenScape Mobile Pro.
43
33
D
C
154
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
OSV Preferred Device (or OND) Backup Routing in the case of a UC Outage
C
00
EN
43
33
D
C
155
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• For UC, the OSV offers the new feature "Enable Backup Preferred Device Routing“.
C
00
• In the case of a UC CSTA shut down or a UC CSTA connection break down, the
OSV will forward all incoming call to the last-selected UC Preferred Device (OND).
EN
43
33
D
C
156
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• To have this feature support, a UC ONS number must not be a logged-on Contact
C
Center Agent!
00
• UC “Name Device Lists” are not supported.

EN
• In case of OSV OSMO configuration, the "Backup Preferred Device Routing"

43
interface option must not be enabled, because by default OSMO routing logic
33
supersedes CF-SOND.
D
C
157
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The feature: “Enable Backup Preferred Device Routing” has to be enabled in:
C
00
– Administration > Signalling Management > CSTA > Applications. Then select the
[Application_UC-IP] and Interface Options”
EN
• By default, the feature “Enable Backup Preferred Device Routing” is disabled.

43
33
D
C
158
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The following information pops up, after the feature check box has been checked:
C
00
• “Before modifying this CSTA Interface Option, verify that OpenScape UC

EN
Subscribers will not logon as

OpenScape Contact Center Agents.”
43
• Click on “OK”, to confirm this popup.

33
D
C
159
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Now the configuration change can be “Saved”.

C
00
EN
43
33
D
C
160
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The following information pops up, after the configuration has been “Saved”:
C
00
EN
43
33
D
C
161
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• “Modifying any CSTA Interface Option associated with the OpenScape Contact
C
Center application may ONLY be performed after consulting with OpenScape

00
Contact Center support group for approval or by confirming that the option being
EN
changed is documented as supported in the OpenScape Contact Center

43
administration guide. Do you wish to proceed with this change?”

33
D
C
162
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• By clicking on “OK”, the information popup will be closed.

C
00
EN
43
33
D
C
163
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Work Flow
C
00
• UC has to send the CSTA request <StartApplicationSession> at CSTA connection

startup.
EN
• This CSTA request contains two timers:

43
33
– <requestedSessionDuration> = 900 seconds

D
– <scx:requestedHBT> = 10 seconds
C
• If the <requestedSessionDuration> expires, the complete CSTA session must be re-

established from scratch.
• The <scx:requestedHBT> is a Heart Beat timer. If this expires, the OSV activates
the feature “OND Backup Routing” until this timer is reset by UC.
164
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• UC has enhanced the CSTA request <MonitorStart> and <MonitorStop> which

C
transmits the OND number in the <privateData> section as value of

00
<scx:staticOndDN>:
EN
• The value of <scx:staticOndDN> is the UC users Preferred Device (OND), which will
43
be stored in the OSV database and which is visible in the OSV Subscriber feature
33
“One Number Service” as the destination in “Call Forwarding –Static OND DN”.
D
• The transmitted Preferred Device Number is shown and will be stored in „Static
C
OND DN“.
165
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Preferred Device changes, initiate a CSTA request <SetForwarding>, which

C
transmits the OND number in the <privateData> section as a value of

00
</scx:staticOndDN>.
EN
• The transmitted Preferred Device Number is shown and will be stored in ‘Static OND
43
DN’.
33
D
C
166
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The OSV activates the “Static OND Routing” automatically for all monitored
C
subscribers within this session, in the case that the HBT timer expires.
00
EN
43
33
D
C
167
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The OSV feature “Static OND Routing” stays active, until UC sends the CSTA
C
request <ResetApplicationSessionTimer> with a value for <scx:requstedHBT> in

00
seconds.
EN
43
33
D
C
168
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• If the <requestedSessionDuration> has also expired, UC must re-initialize the whole

C
CSTA session and must set all Monitor Points again!

00
Also during this period of time, the OSV “Static OND Routing” feature remains
EN
active.
43
33
D
C
169
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
To help describe the basic message flow, we have on the left the bcom or CSTA
C
interface of OpenScape UC and on the right, the CSTA interface of the OpenScape
00
Voice.
EN
43
33
D
C
170
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
OpenScape UC sends the CSTA ‘Start Application Session Request’, which contains
C
the ‘requested Session Duration’ timer with the value of 900 seconds and the
00
‘requested Heart Beat Timer’ with the value of 10 seconds.

EN
43
33
D
C
171
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
The OpenScape Voice confirms the application start and both timers by sending a
C
‘Start Application Session Response’. This response additionally contains a ‘session

00
ID’.
EN
43
33
D
C
172
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
As a result, the application session with the OpenScape Voice defined ‘Application
C
Session ID’ has been established.

00
EN
43
33
D
C
173
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Both sides, OpenScape UC and the OpenScape Voice, have also set the ‘Heart Beat
C
Timer’ for this particular session ID.

00
EN
43
33
D
C
174
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
In this example the ‘Application Session 1212’ has been established.

C
00
EN
43
33
D
C
175
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Now, it is mandatory that OpenScape UC resets both session timers for this particular
C
‘session ID’ by sending the CSTA request ‘Reset Application Session Timer’, before the
00
‘Heart Beat Timer’ has expired.

EN
43
33
D
C
176
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
The OpenScape Voice confirms the CSTA request ‘Reset Application Session Timer’
C
for this particular ‘session ID’ by sending a ‘Reset Application Session Timer
00
Response’.
EN
43
33
D
C
177
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Both sides, OpenScape UC and the OpenScape Voice, will then reset the ‘Heart Beat
C
Timer’ for this particular session ID.

00
EN
43
33
D
C
178
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
The ‘Application Session 1212’ is still established.

C
00
EN
43
33
D
C
179
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
OpenScape UC sends, for every single OpenScape Voice subscriber that is assigned
C
to an OpenScape UC user as ONS/OND via the CMP, a CSTA request ‘Monitor Start’.
00
The improvement is that the CSTA request ‘Monitor Start’ for an ONS, contains in
EN
addition, the number of the last preferred device.

43
33
D
C
180
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
According to the definition in CSTA III the OpenScape Voice answers with a ‘Monitor
C
Start Response’ and the ‘Monitor Cross Reference ID’ for the monitored device.
00
EN
43
33
D
C
181
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
The ‘Application Session 1212’ is still established.

C
00
EN
43
33
D
C
182
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
If an OpenScape UC user changes his preferred device, a CSTA request ‘Set

C
Forwarding’ will be sent to the OpenScape Voice. This CSTA request doesn’t contain
00
any flag of a specific type of call forwarding. But it contains the private data
EN
‘staticOndDN’ to keep the OpenScape Voice informed about the last preferred device
43
number. Based on this information the OpenScape Voice updates the ‘staticOndDN’ in
33
its data base, for the particular monitored device.

D
Please Note. CF-SOND is the assignment of the CSTA private data information, as
C
defined in CSTA III 269.
183
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
According to the definition in CSTA III the OpenScape Voice answers with a ‘Set
C
Forwarding Response’.
00
EN
43
33
D
C
184
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Due to the change of the ‘staticOndDN’, the OpenScape Voice initiates in the process
C
flow, the sending of a ‘ForwardingEvent’ to OpenScape UC. This can be compared to a

00
user action on the OpenScape Voice side. It’s like a user has changed the call
EN
forwarding destination directly on the phone.

43
33
D
C
185
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
UC V9R4 Late Feature - Xpressions Announcement Integration

C
00
EN
43
33
D
C
186
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• With UC V9R4, a new way to integrate the Xpressions V7R1.5 Hotfix 26

C
Announcement was introduced.

00
• The new tab ‘Voicemail’ is visible in the OpenScape UC WebClient Settings, if the
EN
Xpressions integration is configured correctly.

43
• The appearance of the tab ‘Voicemail’ will be checked online by asking the
33
OpenScape Xpressions server, in which flavour this feature is currently configured?

D
C
• If the Voicemail Integration is enabled, the use’s OpenScape Xpressions ‘Voicemail

Settings’ can be managed via the OpenScape WebClient
• With Xpressions V7R1.5 Hotfix 33, the support of this feature via CMP User
Management has been released.
• All Xpressions mailboxes must be set to: ‘Use default system settings’.
187
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
The features to select, to record and to play Xpressions announcements have been
C
integrated into the UC WebClient.

00
EN
43
33
D
C
188
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• From a UC perspective, the following property value must be enabled to make this
C
new integration option available:

00
/opt/siemens/HiPathCA/config/common/WebClientUI.cfg
EN
UseNewVmSettings = true
43
33
D
C
189
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• From an Xpressions perspective, the following new database attribute has been
C
added, to make this new integration option available:

00
• “UC_MODE”
EN
43
33
D
C
190
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The supported “UC_MODE” values are described in detail here.

C
00
EN
43
33
D
C
191
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• If the supported ‘UC_MODE’ value is ‘empty’, the integration runs in Xpressions

C
Mode.
00
EN
43
33
D
C
192
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The result in the UC WebClient is: A hyperlink to the personal Xpressions Web
C
Assistant.
00
• By clicking on the hyperlink: “Configure your voicemail here”, the UC user’s personal
EN
Xpressions Web Assistant will be opened.

43
33
D
C
193
C
D
33
43
EN
00
C
D
_R
._
C
av
ie
re
s_
31
-0
3-
20
194
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• But what additional values can be set for ‘UC_MODE’?

C
00
EN
43
33
D
C
195
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
If the supported ‘UC_MODE’ value is ‘X’, the integration runs in ‘Xpressions Mode’.
C
00
EN
43
33
D
C
196
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The result is the same as before. There is a hyperlink in the UC WebClient to the
C
personal Xpressions Web Assistant.

00
• Clicking on the hyperlink: ‘Configure your voicemail here’ opens the UC user’s
EN
personal Xpressions Web Assistant.

43
33
D
C
197
C
D
33
43
EN
00
C
D
_R
._
C
av
ie
re
s_
31
-0
3-
20
198
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
So, what other values can be set for ‘UC_MODE’?

C
00
EN
43
33
D
C
199
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• If the supported ‘UC_MODE’ value is ’U, the integration runs in ‘UC Mode’.
C
00
EN
43
33
D
C
200
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The result in the UC WebClient is that the features to select, to record and to play
C
Xpressions announcements are offered in the UC WebClient.

00
• This kind of Xpressions announcement management is fixed and can’t be changed

EN
by a UC user.
43
33
D
C
201
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Are there any additional values that can be set for ‘UC_MODE’?
C
00
EN
43
33
D
C
202
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Well, if the supported ‘UC_MODE’ value is ‘O’, the integration runs firstly in
C
‘Xpressions Mode’ but with the User option to use ‘UC Mode’.
00
EN
43
33
D
C
203
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The result in the UC WebClient is an additional selection offer.

C
00
• By clicking on the hyperlink: “OpenScape Xpressions” the UC user’s personal

Xpressions Web Assistant will be opened.
EN
43
33
D
C
204
C
D
33
43
EN
00
C
D
_R
._
C
av
ie
re
s_
31
-0
3-
20
205
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• By clicking on the hyperlink: “new mode” the following choices are offered:
C
00
EN
43
33
D
C
206
C
D
33
43
EN
00
C
D
_R
._
C
av
ie
re
s_
31
-0
3-
20
207
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• “Yes, activate the new mode” and…

C
00
• “No, keep the way it is”

EN
43
33
D
C
208
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• By clicking on the button: “Yes, activate the new mode”…

C
00
EN
43
33
D
C
209
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
…the result in the UC WebClient is that the features to select, to record and to play
C
Xpressions announcements are offered in the UC WebClient.

00
EN
43
33
D
C
210
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• In addition, the value of the XPR attribute ‘UC_MODE’ will be changed to ‘N’.
C
00
• This change stores the current UC WebClient selection.

EN
43
33
D
C
211
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Further options are offered at the bottom, in the “Voicemail settings”:

C
00
EN
43
33
D
C
212
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• These are the “OpenScape Xpressions options”

C
00
EN
43
33
D
C
213
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• By clicking on the hyperlink at the bottom of the UC WebClient: “The greetings

C
recorded previously in OpenScape Xpressions can be downloaded here”, the

00
existing recorded Xpressions greetings, can be downloaded in a .zip file format.

EN
• This is helpful, because in case the of a change from “Xpressions Mode” to “UC
43
Mode” the existing recorded greetings are not available here.

33
D
C
214
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• After that, the previously recorded Xpressions greetings can be uploaded via the UC
C
WebClient, by clicking on: “Load from file”

00
EN
43
33
D
C
215
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• By clicking on the hyperlink: “You can reactivate OpenScape Xpressions

C
configuration” a UC User will get both selection offers back.

00
EN
43
33
D
C
216
C
D
33
43
EN
00
C
D
_R
._
C
av
ie
re
s_
31
-0
3-
20
217
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• By checking the checkbox: “Don’t show OpenScape Xpressions configuration again”

C
and by “Saving” this selection, the result in the UC WebClient is that the features to
00
select, to record and to play XPR announcements have been integrated into the UC
EN
WebClient.
43
33
D
C
218
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• This is now fixed and can no longer be changed by a UC user.

C
00
EN
43
33
D
C
219
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• In fact, the value of the Xpressions attribute ‘UC_MODE’ has been changed to ‘U’
C
00
EN
43
33
D
C
220
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• What additional options are available for ‘UC_MODE’?

C
00
EN
43
33
D
C
221
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• If the supported ‘UC_MODE’ value is ‘N’, the integrations runs first in ‘UC_Mode’
C
with the User option, to use the ‘Xpressions Mode’

00
EN
43
33
D
C
222
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The result in the UC WebClient is that the features to select, to record and to play
C
XPR announcements are offered in the UC WebClient.

00
EN
43
33
D
C
223
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Further options are offered at the bottom in the “Voicemail settings”:

C
00
EN
43
33
D
C
224
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• These are the “OpenScape Xpressions options”

C
00
EN
43
33
D
C
225
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• By clicking on the hyperlink at the bottom in the UC WebClient: “The greetings

C
recorded previously in OpenScape Xpressions can be downloaded here”, the

00
existing recorded Xpressions greetings can be downloaded in a .zip file format.

EN
• This is helpful, because in the case of a change from “Xpressions Mode” to “UC
43
Mode” the previously recorded greetings are not available here.

33
D
C
226
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• After that, the previously recorded Xpressions greetings can be uploaded via the UC
C
WebClient by clicking on: “Load from file”

00
EN
43
33
D
C
227
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• By clicking on the hyperlink: “You can reactivate OpenScape Xpressions

C
configuration”…
00
EN
43
33
D
C
228
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The result in the UC WebClient is: an additional selection offer.

C
00
• The following choices are offered:

EN
• “Yes, restore OpenScape Xpressions”

43
• “No, keep current settings”

33
D
C
229
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• By clicking on the button: “Yes, restore OpenScape Xpressions”…

C
00
EN
43
33
D
C
230
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The result in the UC WebClient is an additional selection offer:

C
“You can activate the new mode to define greetings for your voicemail, or you can
00
keep using the configuration via OpenScape Xpressions.”

EN
43
33
D
C
231
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• In addition, the value of the Xpressions attribute ‘UC_MODE’ will be changed to ‘O’.
C
This change stores the current UC WebClient selection.

00
EN
43
33
D
C
232
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• And finally, what other value can be set for ‘UC_MODE’?

C
00
EN
43
33
D
C
233
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• If the supported ‘UC_MODE’ value is ‘D’, the integration of the OpenScape

C
Xpressions Web Assistant Access via the OpenScape WebClient is disabled.

00
EN
43
33
D
C
234
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The result in the UC WebClient is that the “Voicemail” tab is no longer available.
C
00
• There is no option to open the personal Xpressions Web Assistant via the UC
WebClient.
EN
43
33
D
C
235
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• But the UC WebClient feature to have access to the personal Xpressions voicemail
C
box is still available.

00
EN
43
33
D
C
236
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Note that in the case of an invalid ‘UC_MODE’ value, an error message appears in
C
the “OpenScape UC Settings > Voicemail” tab

00
EN
43
33
D
C
237
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
Visibility Group - Configuration and Assignment via the CMP

C
00
EN
43
33
D
C
238
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The feature “Visibility Groups” was introduced with UC V7R2.

C
00
• The feature “Visibility Groups” is a User Group model, to allow a group-specific

selection of LDAP directory connectors.
EN
• UC software allows the use of multiple directory connectors for contact search.
43
33
• This feature offers selective access to LDAP connectors on a per user basis.
D
• Unfortunately, in V7R2 and in all further UC releases, the CMP didn’t offer any
C
configuration via GUI.

• In V7R2, a maximum number of 16 LDAP connectors or ‘Visibility Groups’ were
released.
239
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• As a V9R4 Late Feature (Hotfix 20), the CMP provides the configuration of “Visibility
C
Groups” and the assignment to UC users via GUI.

00
• With V9R4 the maximum number of supported LDAP connectors or ‘Visibility

EN
Groups’ was increased to 260.

43
• “Visibility Groups” are also used as a group-specific Caller ID Address Book.

33
D
C
240
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• “Visibility Groups” can be created in the CMP in:

C
00
• “Configuration >
EN
• Unified Communications >

43
• Configuration >
33
• Visibility Groups”
D
C
241
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The pre-requisites are:

C
00
• A number of configured LDAP connectors

EN
43
33
D
C
242
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The LDAP Connectors must not be activated.

C
00
EN
43
33
D
C
243
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Now “Visibility Groups” can be added

C
00
EN
43
33
D
C
244
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• A unique “Name” has to be entered.

C
00
EN
43
33
D
C
245
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The addition of a “Description” is optional.

C
00
EN
43
33
D
C
246
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• An already configured “LDAP Connector” has to be selected from the drop-down list
C
and must be assigned to a “Visibility Group”,

00
EN
43
33
D
C
247
C
D
33
43
EN
00
C
D
_R
._
C
av
ie
re
s_
31
-0
3-
20
248
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• There is always a 1-to-1 relationship between a “Visibility Group” and an “LDAP

C
Connector”.
00
EN
43
33
D
C
249
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• In the end a list of “Visibility Groups” exists in the CMP.

C
00
• “Visibility Groups can also be created via a ‘domain_management.csv’ import:

EN
43
33
D
C
250
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• After that, one or multiple “Visibility Groups” can be assigned to OpenScape UC

C
users.
00
This has to be done in:

EN
43
Configuration > Unified Communications > Configuration > Accounts > List
33
D
C
251
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• A new tab has been added to the UC user configuration - “Visibility Groups”.
C
00
EN
43
33
D
C
252
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• By clicking on “Connect…” an OpenScape UC user can be assigned to one, or

C
multiple “Visibility Groups”.

00
EN
43
33
D
C
253
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• The list of configured “Visibility Groups” will be opened.

C
00
EN
43
33
D
C
254
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Now one, or multiple “Visibility Groups” can be selected.

C
00
• The selection will be accepted by clicking on “OK”.

EN
43
33
D
C
255
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• All previous selected “Visibility Groups” are displayed in the overview.

C
00
EN
43
33
D
C
256
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• This “Visibility Group” assignment will be saved by clicking on “Save”.

C
00
EN
43
33
D
C
257
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
• Visibility Groups can be also connected to an OpenScape UC user, via a

C
‘domain_management.csv’ import.
00
EN
43
33
D
C
258
20
3-
-0
31
s_
re
ie
av
C
._
_R
D
And that brings us to the end of this OpenScape UC V10 Update web based training.
C
00
Thank you very much for your attention, and we look forward to seeing you again soon
EN
on our website.
43
33
D
C
259

Mod01 GL OSAV100SDS CD3343EN00CD PDF

Uploaded by

Document Information

Original Description:

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

Mod01 GL OSAV100SDS CD3343EN00CD PDF

Uploaded by

Copyright:

Available Formats

20

features, released in December 2019.

Let’s start with the introduction.

The release software candidates are:

Please note the following:

Windows operating system.

Now let us talk about the ‘Feature Overview’

• Finally, OpenScape UC WebClient supports chat conversations with attachments.

• The WebClient of OpenScape UC V10 is designed to support Screen Reader

in V9R4, it will be implemented in OpenScape UC V10 as well.

The OpenScape UC V9R4 late features are:

• The integration of the OpenScape Xpressions announcement management

users via the CMP.

So, what’s new in conjunction with the OpenScape UC feature - Chat?

It is the opportunity to transmit attachments during a chat.

send files attached to chat messages.

(UC V10) as to how to open an attachment.

the HTTP File Upload Web Server, to download the attachment.

• Openfire has a new directory for this feature: /opt/openfire/httpfileupload

• This directory contains the configuration file: httpfileuploadcomponent.conf

loads the properties of the following configuration file:

The following is only for informatino purpose:

following Java command:

httpfileuploadcomponent.conf are listed and described:

• The value of the property ‘announcedWebHost’ is the hostname or IP address that is

to be used by the end users and is part of the transmitted URL.

The default port number is 12121.

• The value of the property ‘announcedWebProtocol’ is the protocol that is to be used

the HTTP server can spawn.

The default value is 8.

• The value of the property ‘maxOccupancy’ is the maximum allowed occupancy of

Additional supported MIME types have to be added manually!

Only the listed MIME types can be transmitted in a chat!

the XMPP domain and must not be changed!

should be stored in the temporary directory provided by the file system.

to define the time a client has to upload a file.

The default duration is 5 minutes.

webserver will run. It defaults to an arbitrary, non-local address.

• The value of the property ‘xmppMaxThreads’ is the maximum number of threads

this property is 5275.

recommended configuration for security reasons.

• UC clients (Fusion and WC) use MIME ‘application/octet-stream’ as default MIME.

included in the White list.

character set. Sub-type, predefined plain text without formatting.

Some more examples of mimes for the white list:

chat session, which contains the transmitted attachments:

• In case of an attachment in a group chat, the group <chatID> is taken as directory

name such as in the example shown here.

under Group Chat > Room Administration

• A <chatID> sub-directory contains every single attachment, file by file.

• Images can be attached,

• via “drag-and-drop” into the content line,

• or via copy and paste

• Images are presented directly in the conversation.

• Clicking on another image will enlarge it in the “Fusion Image Viewer”.

easy to identify the file type.

default temporary download folder:

• Now it’s possible to open an attachment or save it in a folder.

• The folder %localappdata%\unify\nativechat\<username>\conversation –

<host> will be created at Fusion startup automatically.

attached and automatically displayed images.

• As soon as a “non-image” attachment type has been downloaded, a new subfolder