Ot2.1 Am Otclientadmin 8al90638usac 2 en

! "

Legal notice:
The information presented is subject to change without notice.
ALE International assumes no responsibility for inaccuracies contained

herein.
Copyright © ALE International, 2015
Disclaimer:
While efforts were made to verify the completeness and accuracy of the
information contained in this documentation, this document is provided “as
is”. To get more accurate content concerning Cross Compatibilities, Product
Limits, Software Policy and Feature Lists, please refer to the accurate
documents published on the Business Partner Web Site.
In the interest of continued product development, ALE International reserves

the right to make improvements to this documentation and the products it
describes at any time, without notice or obligation.
The CE mark indicates that this product conforms to the following Council
Directives:
- 2004/108/EC (concerning electro-magnetic compatibility)
- 2006/95/EC (concerning electrical safety)
- 1999/5/EC (R&TTE)
- 2011/65/EU (RoHS)
- 94/9/EC

Chapter 1
Overview
Overview ..................................................................................................... 10

About this document ............................................................................. 10
Chapter 2
Reference documents
Chapter 3
Implementing OpenTouch Ecosystem
Overview ..................................................................................................... 13

Configuring the firewall ........................................................................ 14
Configuring the DNS server ................................................................ 14
Recommendations .......................................................................................... 14
Configuring the internet DNS server ............................................................... 15
Configuring the intranet DNS server ............................................................... 15
Configuring a reverse proxy ............................................................... 16
!"# $ %& #'(

3/195

Overview ......................................................................................................... 16

Declaring the reverse proxy on OpenTouch ................................................... 17
Configuring a Blue Coat reverse proxy ........................................................... 18
Configuring an OpenTouch Session Border Controller ............ 22
Overview ......................................................................................................... 22
Declaring the OTSBC on OpenTouch ............................................................ 23
Associating the OTSBC to the OpenTouch client applications on OpenTouch
......................................................................................................................... 27
Installing and configuring an OTSBC ............................................................. 30
Configuring an OpenTouch Edge Server ....................................... 30
Chapter 4
Implementing OpenTouch Conversation for tablets
Overview ..................................................................................................... 31

About this section ................................................................................... 31
Available features ................................................................................... 31
Interface overview ................................................................................... 33
OTC iPad ........................................................................................................ 33
OTC Android Tablet ........................................................................................ 36
Topologies ................................................................................................. 40
On-site topology ............................................................................................. 40
Off-site topology (remote worker) ................................................................... 41
Deployment procedure overview ...................................................... 42
Configuring the OTC tablet .................................................................. 42

Process overview ........................................................................................... 43

Prerequisites ................................................................................................... 43

Creating and associating new OTC tablet to Conversation users .................. 43

Granting user access right to OTC tablet and conferencing ........................... 45
Configuring the OpenTouch ecosystem ......................................... 46
Installing the OTC tablet ....................................................................... 46
Installing the OTC Android Tablet .................................................................. 46
Installing the OTC iPad ................................................................................... 47
4/195 !"# $ %& #'(

Generating a QR code ........................................................................... 47

Importing the certificate used to connect to the reverse proxy
(remote worker) ........................................................................................ 48
Launching the OTC tablet .................................................................... 48
OTC iPad context ........................................................................................... 48
OTC Android Tablet context ........................................................................... 50
Configuring the OTC tablet settings ................................................ 52
OTC iPad context ........................................................................................... 52
Configuring the OpenTouch for conferences notifications by
e-mail ........................................................................................................... 54
Accessing logs ......................................................................................... 55
OTC iPad context ........................................................................................... 55
Chapter 5
Implementing OpenTouch Conversation for PC
Overview ..................................................................................................... 57

About this section ................................................................................... 57
Topologies ................................................................................................. 63
On site topology .............................................................................................. 63
Off site topology (remote worker) ................................................................... 64
Deployment procedure overview ...................................................... 66
Configuring the OTCV PC on the OpenTouch .............................. 66

Process overview ........................................................................................... 66

Prerequisites and information required ........................................................... 66

Creating and associating an OTCV PC to a user ........................................... 67

Granting users the right to access the application from a computer .............. 68

Configuring the OTCV PC as multiline device ................................................ 69
Configuring the OpenTouch ecosystem ......................................... 70
!"# $ %& #'(

5/195

Installing the OTCV PC on client computers ................................. 70

Overview ......................................................................................................... 70
Prerequisites ................................................................................................... 70
Performing a single client installation ............................................................. 71
Performing multiple client installation (mass provisioning) ............................. 77
Using certificates for OpenTouch access authentication ........ 78
Launching the OTCV PC ....................................................................... 82
Prerequisites ................................................................................................... 82
Connecting to the OpenTouch server ............................................................. 82
Configuring the OTCV PC extensions in Microsoft Outlook ... 84
Uninstalling the OTCV PC from client computers ....................... 85
Accessing logs ......................................................................................... 85
Chapter 6
Implementing OpenTouch Conversation for smartphones (Connection and
Conversation users)
Overview ..................................................................................................... 87

About this document ............................................................................. 87
Dual mode (Wi-Fi/cellular) within company premises ............... 93
VoIP communications outside company premises .................... 94
Topologies ................................................................................................. 95

Topologies for Conversation users ................................................................. 96

Topologies for Connection users .................................................................... 99
Deployment procedure overview .................................................... 100
Configuring the OTC smartphone for Conversation users .... 100
Process overview ......................................................................................... 100
Prerequisites and information required ......................................................... 101
Creating and associating an OTC smartphone to Conversation users ........ 101
Granting the Conversation user right to off-site mobility ............................... 103
Configuring the OTC smartphone for Connection users ........ 104
6/195 !"# $ %& #'(

Configuring the OmniPCX Enterprise for off-site mobility ............................. 104

Configuring the smartphones on the OmniPCX Enterprise and OpenTouch 106
Configuring the OTC smartphone for Connection users without deskphone 121
Configuring the OpenTouch ecosystem ....................................... 124
Installing the OTC smartphone application on smartphones 125
OTC Android Smartphone context ............................................................... 125
OTC iPhone context ..................................................................................... 126
Generating a QR code for OTC smartphone first startup ....... 126
Importing the certificate used to connect to the reverse proxy
....................................................................................................................... 127
Launching the OTC smartphone ..................................................... 128
Displaying the type of user logged in ............................................ 129
Modifying the connection parameters to the OpenTouch server
....................................................................................................................... 130


Uninstalling the OTC smartphone ................................................... 134
Accessing logs ....................................................................................... 135
Overview ....................................................................................................... 135
Accessing logs using the application ............................................................ 135
Accessing logs using a SysLog server ......................................................... 135
Generating a QR code or NFC tag for call routing and
switching .................................................................................................. 137
Generating a QR code .................................................................................. 138
Generating a NFC tag .................................................................................. 138
Chapter 7
Implementing OpenTouch Conversation for Web
Overview ................................................................................................... 140

Available features ................................................................................. 140
!"# $ %& #'(

7/195

Interface overview ................................................................................. 142

Topologies ............................................................................................... 145
On site topology ............................................................................................ 145
Off site topology (remote users) ................................................................... 146

Application deployment and configuration ................................. 147
WebRTC configuration ........................................................................ 148
WebRTC configuration on OpenTouch ........................................................ 148
WebRTC configuration on OTES ................................................................. 148
WebRTC configuration on OTSBC ............................................................... 149

List of supported operating systems and browsers ................ 154
Chapter 8
Implementing OpenTouch Connection for PC
Overview ................................................................................................... 155

About this section ................................................................................. 155
Interface overview ................................................................................. 156
Topologies ............................................................................................... 159
On site topology ............................................................................................ 159
Off site topology (remote worker) ................................................................. 159
Deployment procedure overview .................................................... 161
Configuring the OTCT PC for Connection users ....................... 161

Overview ....................................................................................................... 161

Prerequisite .................................................................................................. 161

Configuring the Connection users as SIP extension users .......................... 161

Configuring the Nomadic SIP for Connection users with physical deskphone 165
Configuring the OpenTouch ecosystem ....................................... 171
Installing the OTCT PC on client computers ............................... 171
Installing the OTCT PC application on computers as standalone client ....... 171
Installing the OTCT PC on computers with collaboration clients .................. 179
Installing the OTCT PC on computers with e-mail clients ............................ 181
Launching the OTCT PC ..................................................................... 182
8/195 !"# $ %& #'(

Prequisites .................................................................................................... 182

Connecting to the OpenTouch server ........................................................... 182
Configuring OTCT PC extension settings .................................... 184
Configuring OT2.0 Outlook extension settings ............................................. 184
Configuring OT2.0 Lotus Notes extension settings ...................................... 186
Uninstalling the OTCT PC from client computers ..................... 188
Chapter 9
Implementing OpenTouch Meeting Manager
Overview ................................................................................................... 189

List of supported operating systems ............................................. 190
Prerequisite ............................................................................................. 190
Accessing logs ....................................................................................... 191
Chapter 10
Implementing OpenTouch Conversation One
Overview ................................................................................................... 193

List of supported operating systems ............................................. 194
!"# $ %& #'(

9/195

1.1 Overview
The OpenTouch® solution offers client applications that combine voice, video and data
services through a user-friendly graphical user interface. The OpenTouch client applications
are divided into two categories:
- The client applications intended for Conversation users
• OpenTouch Conversation for PC
• OpenTouch Conversation for smartphones (iPhone and Android smartphone)
• OpenTouch Conversation for tablets (iPad and Android tablet)
• OpenTouch Conversation One
- The client applications intended for Connection users.
• OpenTouch Connection for PC
• OpenTouch Conversation for smartphones (iPhone and Android smartphone)
• OpenTouch Conversation One
In addition, the OpenTouch solution provides several applications for conferencing:
- The OTC Web allows anonymous users to join an OpenTouch conference using a
browser. As of R2.1.1, the establishment and support of audio flows between OTC Web
and other devices can be handled by the WebRTC technology, provided this technology is
implemented and embedded in the browser.
- The OpenTouch Meeting Manager allows Conversation users to handle OpenTouch
conferences using the Chrome browser.
1.2 About this document

The following paragraphs are intended for people in charge of configuring and commissioning
the OpenTouch client applications on customer sites.
10/195 !"# $ %& #'(

The complete OpenTouch documentation consists in separated documents, each

corresponding to a specific aspect of necessary and optional installations/administrations.
In the present document, cross-references are identified by the number in the first column of
the table below.
Part numbers are given in the last column, where xx corresponds to the language code of the
document.
The documents for OpenTouch are:
table 2.1: OpenTouch documentation structure
Documentation title Part number
[1] OTBE Installation Manual on a Physical Machine 8AL90504xxAF
[2] OTMS Installation Manual on a Physical Machine 8AL90512xxAF
[3] OTBE/OTMS Administrator Manual 8AL90505xxAF
[4] Installation Manual on a Virtual Machine 8AL90507xxAD
[5] ALEDS 8AL90508xxAE
[6] OpenTouch General Architecture 8AL90509xxAC
[7] OpenTouch System Documentation 8AL90510xxAC
[8] OpenTouch Maintenance and Supervision 8AL90511xxAC
[9] OT-C2D Administrator Guide 8AL90527xxAA
[10] OT-C2D User Guide 8AL90528xxAA
[11] Description of IP flows in OpenTouch solution 8AL220303381xx
ZZA
[12] OpenTouch Openness_API_Technical Overview 8AL90532xxAA
[13] OpenTouch Edge Server - Installation and administration manual 8AL90535xxAB
[14] OpenTouch XMPP federation with Microsoft© Lync™ Server 8AL90539xxAB
[15] OpenTouch Client Administration Manual 8AL90638xxAC
[16] OTMC Installation Manual 8AL90120xxAB
[17] OTMC Administrator Manual 8AL90121xxAAB
[18] OTMC High Availability 8AL90123xxAB
[19] ENT_MLE_015903 OpenTouch Suite for Medium and Large En- ENT_MLE_01590
terprises: Virtualized offers. 3
[20] OpenTouch Conversation for PC User Guide 8AL90631xxAA
[21] OpenTouch Connection for PC User Guide 8AL90632xxAA
[22] OpenTouch Connection for Microsoft©Outlook© User Guide 8AL90633xxAA
[23] OpenTouch Connection for Microsoft© Lync™ User Guide 8AL90634xxAA
[24] OpenTouch Connection for IBM Lotus Notes User Guide 8AL90636xxAA
[25] OpenTouch Connection for IBM Sametime User Guide 8AL90635xxAA
[26] OpenTouch Message Center User Guide 8AL90122xxAA
!"# $ %& #'(

11/195
Chapter 2 )*

Documentation title Part number

[27] OpenTouch Conversation for 8002/8012 Deskphone R110 User 8AL90879xxCB
Manual
[28] OpenTouch Conversation for 8082 My IC Phone R300 User 8AL90835xxCF
Manual
[29] OpenTouch Conversation for 8082 My IC Phone R300 User 8AL90877xxAB
Guide
[30] OpenTouch Conversation for iPhone Release 2.0.x User Guide 8AL90884xxAB
[31] OpenTouch Documentation Note 8AL90911xxAA
This document lists all the modifications and updates since the
previous documentation release.
[32] Alcatel-Lucent 8001 DeskPhone User Manual 8AL90895xxAA
[33] Dongle IP / Raspberry for OpenTouch Suite 8AL90617xxAA
[33] ALE NFC Extended OXE Mobility Administration 8AL90614xxAB
12/195 !"# $ %& #'(

3.1 Overview
The OpenTouch ecosystem consists of the network elements that exist independently of
systems provided by ALE International, but interacting with the OpenTouch server and
OpenTouch client applications. The network elements are used to control media and data
transmission between the OpenTouch client applications outside the company (off-site) and
the company intranet network (LAN).
If you are outside the company (off-site), you can connect to the company LAN either:
- Over a VPN connection:
IPsec VPN is supported for OTCV PC, OTCT PC OTC iPad and OTC iPhone, when such a
VPN connectivity is provided by the user device and the company network.
- Via a secured network infrastructure including the following network elements:
• The reverse proxy, used to control data communications (web services and device
management) through HTTPS connections (see: Configuring a reverse proxy )
• The OpenTouch Session Border Controller (OTSBC) used to control media
(voice/video) communications through SIP/TLS signaling and SRTP flows, or SIP over
WebSockets Secured signaling and DTLS-SRTP flows (see: Configuring an
OpenTouch Session Border Controller )
• The OpenTouch Edge Server (OTES) if it has been delivered with the OpenTouch
solution (optional component). If it is the case, the OTES is used to control data flows
(conferencing, data sharing, instant messaging or web presentations) through HTTPS
connections (see: Configuring an OpenTouch Edge Server )
The network elements to consider depend of the OpenTouch client application. For
example, the OTC Web requires the configuration of an OTES and OTSBC to support
audio on browsers. The table below indicates the network elements to configure for each
OpenTouch client application:
OpenTouch client ap-
OTES (*) Reverse proxy OTSBC
plication
OTC iPad Yes (optional) Yes Yes
OpenTouch Conversa- Yes (optional) Yes Yes
tion for Android Tablet
OTCV PC Yes (optional) Yes Yes
OTC iPhone Yes (optional) Yes Yes
OpenTouch Conversa- Yes (optional) Yes Yes
tion for Android smart-
phone
OTC Web Yes (mandatory) No Yes (**)
OTCT PC No Yes Yes
(*): mandatory if using off-site desktop sharing (for remote workers).
(**): In case of conferencing access via WebRTC, communications are through SIP over
WebSockets Secured signaling and DTLS-SRTP flows.
Note:
The following elements must also be configured:
!"# $ %& #'(

13/195
Chapter 3 +,
! -
- The firewall protecting the intranet (company LAN). It must allow access to the OpenTouch server
ports (see: Configuring the firewall )
- The Internet DNS server used to resolve the FQDNs of the network elements, when the OpenTouch
client application connects to the OpenTouch server (see: Configuring the internet DNS server ).
Within company premises, the intranet DNS server must be configured to resolve the private FQDN
of the OpenTouch server (see: Configuring the intranet DNS server ).
3.2 Configuring the firewall

Configure the corporate firewall to enable access to the ports used by the network elements.
For the complete list, refer to [11].
Figure 3.1: Firewall configuration
3.3 Configuring the DNS server
3.3.1 Recommendations
The FQDN configuration must comply with the following recommendations:
- The private FQDN of the OpenTouch server (for intranet access) and the public FQDN of
the OpenTouch server (for internet access) must be different.
- The private FQDN of the OpenTouch server and the public FQDN of the OTSBC must be
different.
- The private FQDN of the OpenTouch server must be impossible to resolve from the public
network.
- When an OTES is deployed, the two servers (OTES and OpenTouch) are considered as a
single system and must have a common FQDN (referred as a Cluster FQDN) defined on
the internet and intranet DNS servers. This cluster FQDN must point to OpenTouch on the
intranet network (LAN), and to the OTES from the internet network (WAN).
14/195 !"# $ %& #'(

+,
! -
- Public FQDNs must be configured on the internet DNS server only, and private FQDNs
must be configured on the intranet DNS server only (enterprise private DNS server).
3.3.2 Configuring the internet DNS server

Outside company premises, when there is no VPN, the OpenTouch client application must
connect to any of the following network elements: reverse proxy, OTSBC, and OTES. The
internet DNS server must be able to resolve the public FQDN of these network elements.
Figure 3.2: DNS configuration outside company premises

In all cases, the internet DNS server must be configured to translate the corresponding
element network FQDN into its IP address.
Once configured, verify that DNS resolution is correct:
1. From a computer connected to the internet, open a command-line interface
2. Type the nslookup command followed by the corresponding element network FQDN
Example:
If the OpenTouch public FQDN is otpublic.company.com, enter: c:>nslookup
otpublic.company.com
3.3.3 Configuring the intranet DNS server

Within company premises, the OpenTouch client application connects to the OpenTouch
server through the company intranet network. In this situation, the OpenTouch client
application connects with the private FQDN of the OpenTouch server.
!"# $ %& #'(

15/195
Chapter 3 +,
! -
Figure 3.3: DNS configuration within company premises

The intranet DNS server must be configured to translate the OpenTouch server private FQDN
into the OpenTouch server IP address. Typically, the intranet DNS server is already
configured, since this is required to install the OpenTouch server. For more information, refer
to [1] or [2].
To verify that the DNS resolution is correct:
1. From a computer connected to the internet, open a command-line interface
2. Type the nslookup command followed by the OpenTouch server private FQDN or IP
address
Example:
If the OpenTouch server private FQDN is opentouch.company.com and its IP address is
192.168.201.158, enter:
c:>nslookup opentouch.company.com
c:>nslookup 192.168.201.158
3.4 Configuring a reverse proxy
3.4.1 Overview
For OpenTouch client application deployment requiring a reverse proxy, ALE International
recommends to use the reverse proxies proposed in the Alcatel-Lucent Application Partner
Program (AAPP). Reverse proxies tested and certified by AAPP are the Blue Coat® reverse
proxy and NGINX reverse proxy.
The use of reverse proxies or others systems, non validated by ALE International, is
authorized under strict conditions. They must be compliant with the architecture tested and
technical requirements described in the Inter-Working Report (IWR) documents written for the
ProxySG appliance of Blue Coat and the NGINX Plus product. These IWR documents are
available on AAPP.
These requirements are:
- HTTPS Reverse Proxy service configured to associate a certificate with a public IP
16/195 !"# $ %& #'(

+,
! -
address
- Importing SSL keyrings and CA
- Hostname or domain name based SSL certificates
- Proxy supports portal mode optimization
- HTTP basic and cookie based Authentication using an AD/LDAP or RADIUS
- Powerful and flexible CPL policy
• HTTP header rewriting
• Cookie sharing between the different FQDN
- SSL rule modification to ignore hostname mismatch
However, if you encounter an issue, ALE International will check the same operation on a
reverse proxy supported in AAPP such as the Blue Coat, and with the same client/server
version provided by ALE International.
3.4.2 Declaring the reverse proxy on OpenTouch

To allow OpenTouch client application to connect to the OpenTouch server through a reverse
proxy (off-site mobility), a public URL must be configured for each concerned service of the
OpenTouch server.
1. From the OpenTouch configuration window of OmniVista 8770, select System services >
Topology > Reverse proxy
Figure 3.4: Reverse proxy configuration window example

2. Review/modify the following attributes:
!"# $ %& #'(

17/195
Chapter 3 +,
! -
Display name Enter a display name

API Enter the following URL: https://<public FQDN of the
OpenTouch server>
EVS Enter the following URL: https://<public FQDN of the
OpenTouch server>:8016
ACS If the OTES is provided with the OpenTouch solution, enter the follow-
ing URL: https://<ACS cluster FQDN>. For more information,
refer to [13]
If the OTES is not present, enter: https://<public FQDN of
the OpenTouch server>
DMS Enter the following URL: https://<public FQDN of the
OpenTouch server>/PublicDM
PublicDM allows the reverse proxy to distinguish requests addressed
to OpenTouch to those addressed to OmniVista 8770.
3. Click the validate icon to save your modifications
3.4.3 Configuring a Blue Coat reverse proxy

3.4.3.1 Overview
The following paragraphs provide a short guideline for Blue Coat reverse proxy configuration.
It only specifies the main operations to perform and the Blue Coat reverse proxy parameters to
configure. It does not provide any procedures and/or screens to help with the configuration of
Blue coat reverse proxy parameters. For more information, refer to the Inter-Working Report
(IWR) of the Blue Coat Reverse Proxy (ProxySG) available on the AAPP.
In all cases, open the web GUI interface of the Blue Coat reverse proxy, and perform these
main operations:
- Configuring certificate
- Configuring proxy services
- Configuring forwarding hosts
- Configuring realms for client authentication
- Configuring forwarding rules
- Configuring client authentication rule
- Configuring access rule
- Applying rules
3.4.3.2 Configuring certificate
To establish HTTPS connection, the reverse proxy sends its certificate to the OpenTouch
client application on behalf of the OpenTouch server. As the certificate is sent by the server,
before the server to reach by the OpenTouch client application is known, the certificate name
must match the name of all OpenTouch servers. This is why a wildcard certificate is requested
with a Common Name, such as *.mydomain.com which matches, for example
opentouch.mydomain.com.
The server must also have the Root Certificate that signed its own certificate. A large
number of public PKI Root Certificates (as Entrust or Verisign) are already loaded in the proxy
18/195 !"# $ %& #'(

+,
! -
but if you want to use your own PKI, you must import your root certificate.
From the management console, select Configuration > SSL, and perform the following
operations:
1. Import the Root CA Certificate
2. Create a wildcard certificate including:
• The creation of a keyring
• The creation of a Certificate Signing Request (CSR)
The CSR must be sent to the Certificate Signing Authority (or PKI) to provide a signed
certificate
• The import of the signed certificate
3.4.3.3 Configuring proxy services
This consists in activating the HTTPS services on the reverse proxy and configuring the
actions to perform when the reverse proxy listens for incoming requests. In OpenTouch
context, a proxy service must be defined for each HTTPS port used by the OpenTouch server:
443 for web services and 8016 for Event Server (EVS).
Note 1:
The port 8016 is not used for HTTPS connections with the OTC iPad.
From the management console, select Configuration > Services > Proxy Services, and
complete the following fields:
Web services Event Server
Proxy HTTPS Reverse Proxy
Keyring Name entered during the keyring creation
(see: Configuring certificate )
CA-Cert List Name of the Root CA Certificate
SSL options SSL V2, SSL V3 and TLS to select
Note 2:
- Do not select Verify Client for client authentication by login/password
- Select Verify Client for client authentication by certificate
Listeners Destination: Reverse proxy IP Destination: Reverse proxy IP address
address Port: 8016
Port: 443 Action: Intercept
Action: Intercept
3.4.3.4 Configuring forwarding hosts

This consists in declaring the back-end servers to which flows are forwarded. In OpenTouch
context, a forwarding host must be defined for each HTTPS port used by the OpenTouch
server. In OmniVista 8770 context, a forwarding host must be defined for the HTTP port (443)
used by the OmniVista 8770.
From the management console, Select Configuration > Forwarding > Forwarding Hosts,
and complete the following fields:
For OpenTouch server:
!"# $ %& #'(

19/195
Chapter 3 +,
! -
Web services Event Server

Host OpenTouch IP address
Type Server
Ports (HTTPS) 443 8016
For OmniVista 8770:

Host OmniVista 8770 IP address
Type Server
Ports (HTTPS) 443
3.4.3.5 Configuring realms for client authentication

The realm is used to authenticate and allow the OpenTouch client application to connect to the
reverse proxy. The OpenTouch client application authentication can be based on:
- Login/password. In this case, an LDAP realm must be configured.
From the management console, Select Configuration > Authentication > LDAP, and
perform the following operations:
1. Create the LDAP realm
2. Add a base DN such as: ou=users,dc=mydomain,dc=com
- Certificate. In this case, a certificate realm must be configured.
From the management console, Select Configuration > Authentication > Certificate,
and perform the following operations:
1. Create the certificate realm
2. Define the certificate realm (main and general) properties
3.4.3.6 Configuring forwarding rules
This consists in creating forwarding rules to define the mapping between the requests received
by the reverse proxy and those forwarded to the OpenTouch server and OmniVista 8770.
From the management console, Select Configuration > Policy > Visual Policy Manager,
1. Launch the Visual Policy Manager (VPM)
2. Select the Forwarding layer tab and add a rule for the port 443 (web services) of
OpenTouch server. Complete the following fields:
• For the Destination object:
Scheme HTTPS
Host OpenTouch private FQDN
Port 443
• For the Action object:

Forward to: Alias created in the forwarding host configuration for web services
(see: Configuring forwarding hosts )
3. Add a rule for the port 8016 (Event Server) of OpenTouch server. Complete the following
20/195 !"# $ %& #'(

+,
! -
fields:
Scheme HTTPS
Host OpenTouch private FQDN
Port 8016

Forward to: Alias created in the forwarding host configuration for Event Serv-
er (see: Configuring forwarding hosts )
4. Add a rule for the port 443 of OmniVista 8770. Complete the following fields:
Scheme HTTPS
Host OmniVista 8770 private FQDN
Port 443

Forward to: Alias created in the forwarding host configuration for Event Serv-
er (see: Configuring forwarding hosts )
3.4.3.7 Configuring client authentication rule

This consists in defining the client authentication rule to connect to the reverse proxy. The
client authentication rule can be based on any of the following:
- Login/password. From the management console, Select Configuration > Policy > Visual
Policy Manager, and perform the following operations:
2. Select Policy > Add Web Authentication Layer and add a new layer
3. Select the layer tab and right click the Action cell, then select the LDAP realm and the
Origin Cookie mode
- Certificate. From the management console, Select Configuration > Policy > Visual
Policy Manager, and perform the following operations:
2. Select Policy > Add Web Authentication Layer and add a new layer
3. Select the layer tab and right click the Action cell, then select the certificate realm and
the Auto mode
Note:
Client authentication by certificate is exclusive. If this authentication method is activated, the reverse
proxy does not allow authentication by login/password.
3.4.3.8 Configuring access rule

This consists in creating an access rule to define a combination of destination and apply
authorization rules such as the allowed time period.
From the management console, Select Configuration > Policy > Visual Policy Manager,
!"# $ %& #'(

21/195
Chapter 3 +,
! -

2. Select the Web Access Layer tab and add a rule
3. Right click the Destination cell and add all URLs in a combined destination object
3.4.3.9 Applying rules
Once the rules (forwarding, authentication, and access) configured, select Install Policy.
3.5 Configuring an OpenTouch Session Border Controller
3.5.1 Overview
The OpenTouch Session Border Controller (OTSBC) does not depend on the OpenTouch
solution. The OTSBC can be included in a secured network with or without OpenTouch. The
OTSBC runs on CentOS and cannot be installed on the same server than the OpenTouch
solution.
The OTSBC is used to secure communications between OpenTouch and WAN. Between
OpenTouch client applications and the company LAN, the secured flows are SIP/TLS and
SRTP flows.
___change-begin___
___change-end___
Figure 3.5: Off-site mobility with signaling and media encryption (SIP/TLS and SRTP)
In case of conferencing access via WebRTC, communications to secure between OTC Web
applications and the company LAN are SIP over WebSockets Secured and DTLS-SRTP flows.
___change-begin___
22/195 !"# $ %& #'(

+,
! -
___change-end___
Figure 3.6: Off-site mobility with signaling and media encryption (SIP over WebSokets and
DTLS-SRTP)
3.5.2 Declaring the OTSBC on OpenTouch

According to the types of connection to secure, the following must be declared:
- SIP/TLS and SRTP connections: Declaring the OTSBC for SIP/TLS and SRTP
connections
This solution is highly recommended to secure connections between OpenTouch client
applications and the company LAN.
- SIP and RTP connections: Declaring the OTSBC for SIP and RTP connections
Caution:
This solution is not secured and must be used only temporarily, for example, when the
supply/installation of a certificate on the OTSBC takes a long time (request sent to an external
KPI).
- SIP over WebSockets and DTLS-SRTP connections (In case of conferencing access via
WebRTC): Declaring the OTSBC for conferencing access via WebRTC .
3.5.2.1 Declaring the OTSBC for SIP/TLS and SRTP connections
1. From the OpenTouch configuration window of the OmniVista 8770, select Eco system >
IT Server
2. Right click and select Create > SBC Server
___change-begin___
!"# $ %& #'(

23/195
Chapter 3 +,
! -
___change-end___
Figure 3.7: OTSBC configuration window example
Display name Enter a display name used to identify the OTSBC in the OmniVista
8770
FQDN Enter the FQDN of the OTSBC
Network type Use the drop-down menu to select WAN
Port Select the port used to connect to the public SIP interface of the OTS-
BC. For example:
• 5261 for OTCV PC
• 5061 for OTCT PC
Default port: 5061
URI Schema Select SIP (default value)
Transport protocol Leave TLS (default value)
SRTP mode Select Strict
Video encryption Leave the check box selected (default value)

3.5.2.2 Declaring the OTSBC for SIP and RTP connections
IT Server
24/195 !"# $ %& #'(

+,
! -

The OTSBC configuration window is displayed (see: figure: OTSBC configuration window
example )
Display name Enter a display name used to identify the OTSBC in the OmniVista
8770
Port Select the port number used to connect to the public SIP interface of
the OTSBC. For example:
• 5260 for OTCV PC
• 5060 for OTCT PC
Default port: 5060
URI Schema Select SIP (default value)
Transport protocol Select TCP (default value)

3.5.2.3 Declaring the OTSBC for conferencing access via WebRTC
IT Server
___change-begin___
!"# $ %& #'(

25/195
Chapter 3 +,
! -
___change-end___
Figure 3.8: OTSBC configuration window example
Name Enter a display name used to identify the OTSBC in the OmniVista
8770
Port Enter the port used to connect to the public SIP interface of the OTS-
BC (default port: 8061). This port is used for audio communications
via WebRTC.
URI schema Leave SIP (default value)
Transport protocol Select WSS (only displayed when Network type is set to WAN)
Default value: TLS.
SRTP Mode Select Strict
DTMF mode Leave RFC2833 (default value)

Once the OTSBC is declared on OpenTouch, associate the OTSBC to the WAN SBC field
available in the collaboration configuration:
1. From the OpenTouch configuration window of the OmniVista 8770, select System
26/195 !"# $ %& #'(

+,
! -
services > Applications > Collaboration > Collaboration configuration

2. Select DEFAULT
The collaboration configuration window is displayed
3. In the properties area, select the WebRTC conferencing access tab
WAN SBC Use the drop-down menu to select the OTSBC configured for confer-
encing access via WebRTC
Session refresh re- Enter the maximum amount of time (in seconds) that can occur
quests interval(s) between two session refresh requests in a dialog before the session
is considered as timed out.
Default value: 3600.
Session timer re- Select the process used to perform session refresh.
fresher Default value: UAC.
3.5.3 Associating the OTSBC to the OpenTouch client applications on

OpenTouch
3.5.3.1 For Conversation users
1. From the Users application, click the Users tab
2. Expand the tree structure and select the corresponding OpenTouch client application
3. In the properties area, select the Advanced tab
!"# $ %& #'(

27/195
Chapter 3 +,
! -
Figure 3.9: Configuration window example for an OTCV PC client

4. Review/modify the following attribute:
SBC WAN Double click and use the drop-down menu to select the corresponding
OTSBC (see: Declaring the OTSBC on OpenTouch )
5. Click the validate icon to save your modification

Note:
This operation adds OTSBC information in the configuration file of the OpenTouch client application.
3.5.3.2 For Connection users referred to as SIP extension users
The following operation applies to Connection users declared as SIP extension on the
OmniPCX Enterprise.
2. Expand the tree structure and select the Windows Desktop device associated to the
corresponding SIP extension user
3. In the properties area, select the Security tab
28/195 !"# $ %& #'(

+,
! -
Figure 3.10: Configuration window example for a SIP extension user

SBC address Enter the FQDN of the OTSBC
SBC port Select the port number 5061 used to connect to the public SIP inter-
face of the OTSBC (default port: 5060)
SBC URI Scheme Select SIP (default value)
SBC protocol Select TLS
Default value: UDP

Note:
This operation adds OTSBC information in the device configuration file.
3.5.3.3 For Connection users other than SIP extension
The following operation applies to Connection users declared on the OmniPCX Enterprise
other than SIP extension. To allow these Connection users to use the OTCT PC outside
company premises, the Nomadic SIP feature is required. In this case, the OTSBC must be
declared for all SIP devices declared on the OpenTouch and reserved for the Nomadic SIP
feature. For more information on the Nomadic SIP feature, see: OpenTouch Clients (Mobile
and Desktop) - Implementing OpenTouch Connection for PC - Configuring the OTCT PC for
Connection users .
1. From the OpenTouch configuration window of OmniVista 8770, select System services >
Topology > OXE callservers > OXE SIP subscriber
!"# $ %& #'(

29/195
Chapter 3 +,
! -
2. Select each SIP device of the pool reserved for the Nomadic SIP feature
3. In the properties area, select the Security tab
Figure 3.11: Configuration window example for OXE SIP devices

SBC WAN Double click and use the drop-down menu to select the corresponding
OTSBC (see: Declaring the OTSBC on OpenTouch )
3.5.4 Installing and configuring an OTSBC

The installation and configuration of an OTSBC are described in the Technical Bulletin called:
OPENTOUCH FROM 0 TO REMOTE WORKER (reference: TC1990) available on the AAPP.
This document provides all procedures and screens of the configuration wizard used to deploy
an OTSBC.
3.6 Configuring an OpenTouch Edge Server

The installation and configuration of an OTES (procedures and screens) are described in the
document [13].
30/195 !"# $ %& #'(

4.1 Overview
the OpenTouch Conversation for tablet application (OTC tablet). This application is designed
to run on Android tablet and iPad and is only available for Conversation users.
For readability purposes, unless stated otherwise, the OpenTouch Conversation for iPad (OTC
iPad) and OpenTouch Conversation for Android Tablet (OTC Android Tablet) are called OTC
tablet in the rest of the document.
4.2 About this section

The following paragraphs detail:
- The list of available OTC tablet features (see: Available features )
- A quick overview of the OTC tablet screens (see: Interface overview )
- Details on the OTC tablet network infrastructure (see: Topologies )
- Configuration of the OTC tablet on the OpenTouch server (see: Configuring the OTC tablet
)
- Ecosystem configuration required for the OTC tablet use (see: Configuring the OpenTouch
ecosystem )
- OTC tablet installation on tablets (see: Installing the OTC tablet )
User operations are described in a dedicated user guide.
4.3 Available features

The following table provides the list of features supported by the OTC tablet applications:
Features OTC Android Tab- OTC iPad
let
Single User eXperience across multiple devices Yes Yes
Computer, tablet, smartphone and deskphone
GUI landscape mode Yes Yes
One business number Yes Yes
Voice over IP everywhere Yes Yes
Video over IP everywhere No Yes
Place, answer, and manage voice calls using the Yes Yes
enterprise dialing plan
Call anywhere using the corporate directory, local Yes Yes
directory or OpenTouch contacts
Manage ongoing conversations using a set of con- Yes Yes
ference controls such as transfer, mute, hold, re-
sume, hang up, add, promote
!"# $ %& #'(

31/195
Chapter 4 +,
% * &
Features OTC Android Tab- OTC iPad

let
Move the conversation from a device to another, Yes Yes
using the Rapid Session Shift feature
Join a scheduled meeting in one click Yes Yes
View the history of previous communications and Yes Yes
quickly redial a party
Display and manage voice messages as easily as Yes Yes
e-mails with the visual voice mail interface, which
allows to select, play back or delete messages in
any order
Check notifications on new conference, new voice Yes Yes
message, missed call or chat
View presence and availability of favorite contacts Yes Yes
and tap to start and manage collaborative conver-
sations
Start with a simple one-to-one chat and add Yes Yes
people, add voice, add content
Manage communications preferences and reach- Yes Yes
ability using call routing profiles, effortlessly while
on the move
Change my photo/avatar and presence Yes Yes
Enable/disable Call Supervision and Manager As- Yes Yes
sistant delegation
Schedule meetings on-the-go using predefined Yes Yes
meeting profiles that tailor OpenTouch conferen-
cing capabilities to match the type of meeting or
event
View and conduct presentations - view shared Yes Yes
presentations, PDFs, and bitmap images
Annotate shared presentations, PDFs, and im- Yes Yes
ages, and make real-time edition
View shared applications and desktops Yes Yes
Open past conversations to review notes and ex- Yes Yes
changes or restart the conversation where you left
it
Download from the Market Store Yes Yes
Client authentication via login/password Yes Yes
Client authentication via certificate Yes Yes
Server authentication via certificate Yes Yes
Secure Web Services signaling (HTTPS) Yes Yes
Infrastructure requirements (OTBE, OTMS, OTS- Yes Yes
BC, OTES, RP)
32/195 !"# $ %& #'(

+,
% * &
4.4 Interface overview
4.4.1 OTC iPad

The OTC iPad home page opens immediately after login, then the Conversation Wall is
loading.
___change-begin___
___change-end___
Figure 4.1: OTC iPad home page example
The OTC iPad home page consists of:
1. A Personal area which displays information on the user profile, such as: picture, first
name, presence with personal text message (user input), and current routing profile (that is
the device destination for incoming calls). Click the user picture to access user settings
The options may differ according to the user rights to features such as Manager/Assistant
or Supervision.
___change-begin___
!"# $ %& #'(

33/195
Chapter 4 +,
% * &
___change-end___
Figure 4.2: User settings page example
2. A Conversation wall presenting past, current and future conversations and conferences.
Click a contact to display the corresponding conversation window:
34/195 !"# $ %& #'(

+,
% * &
Figure 4.3: Conversation window example

Click successively the different conversation windows to display call history and contact
details:
From the conversation window, the available operations are:

• Make a new audio or video call
• Send an Instant Message (IM) to the selected contact
• Join a scheduled conference with the selected contact
• Share the computer desktop, an application, or a document with the selected contact
• Add the contact to your community of favorite contacts
• Send an e-mail to the address provided in the information window for the contact
!"# $ %& #'(

35/195
Chapter 4 +,
% * &
3. A Favorite contacts area used to access the list of favorite contacts. Click the star at the
bottom right of the OTC iPad home page to show (or hide) the list of favorite contacts:
Figure 4.5: Favorite contact area example

Favorite contacts are indicated by a star icon in the conversation wall.
4. An Application area used to access the OTC iPad applications:
Icon Application Select, to: • Available operations
Voice mail Access the Visual Voice Mail (VVM) • Listen to a voice message
to read and manage voice mes- • Delete a voice message
sages.
A counter indicates the number of
new messages
Conference Access the list of planned confer- • Consult scheduled conference
ences (scheduled and reservation details
less) and conference invitations • Join a scheduled conference
from other users • Create a scheduled conference
Search Access the search area • Search contact (local or corpor-
ate)
Keypad Open the dialing keypad • Make a call
• Pick up a call
4.4.2 OTC Android Tablet

The OTC Android Tablet home page opens immediately after login, then the Conversation
Wall is loading.
36/195 !"# $ %& #'(

+,
% * &
Figure 4.6: OTC Android Tablet home page example

The OTC Android Tablet home page consists of:
1. A Personal area which displays information on the user profile, such as: picture, first
name, presence with personal text message (user input), and current routing profile (that is
the device destination for incoming calls). Click the user picture to access user settings.
The options may differ according to the user rights to features such as Manager/Assistant
or Supervision.
!"# $ %& #'(

37/195
Chapter 4 +,
% * &

Other settings are also available from the icon present at the top right part of the home
page:
2. A Conversation wall presenting past, current and future conversations and conferences.
Click a contact to display the corresponding conversation in the Active area.
3. An Active area where the selected conversation takes place. From this area, the available
operations are:
38/195 !"# $ %& #'(

+,
% * &
• Make a new audio call (video calls are not available from this application)
• Send an Instant Message (IM) to the selected contact
• Listen an unread voice message
• Join a scheduled conference with the selected contact
• Share the computer desktop, an application, or a document with the selected contact
(display in full screen is available)
• Add the contact to your community of favorite contacts
• Send an e-mail to the address provided in the information window for the contact
Figure 4.9: Example of available operations

4. A Details area which displays additional information such as call history, contact details,
favorite contacts, directory lookup, IM conversation or conference details (owner,
participants, documents used). Information depends on the current conversation present in
the Active area and the icon pressed in the Application area.
5. An Application area including icons which differ according to the current operation in the
Active area. If there is no call or IM in progress, the main icons are:
Voice mail Access the Visual Voice Mail • Listen to a voice message
(VVM) to read and manage voice • Delete a voice message
messages.
new messages
Conference Access the list of planned confer- • Consult scheduled conference
from other users • Create a scheduled confer-
ence
• Pick up a call
Search Access the search area • Search contact (local or cor-
porate)
!"# $ %& #'(

39/195
Chapter 4 +,
% * &

Favorites Access the list of favorite contacts • Consult favorite contacts
• Start a conversation with a fa-
vorite contact
6. The icon allows to access a dashboard which provides a quick overview of the
missed calls, unread voice messages and future conferences.
4.5 Topologies
4.5.1 On-site topology

Within company premises, the OTC tablet relies on the company intranet network (LAN) for
media (voice/video) and data transmission. The OTC tablet connects to the company intranet
network using a wireless connection (Wi-Fi network).
The OTC tablet uses:
- SIP signaling and RTP connections to perform VoIP and video communications
Note:
VoIP and video communications are not encrypted within the company intranet network (no SIP/TLS
and SRTP connections).
- HTTPS connections to exchange data with the OpenTouch server (for example: web
services, ACS services, and conference data)
40/195 !"# $ %& #'(

+,
% * &
Figure 4.10: On site topology
4.5.2 Off-site topology (remote worker)

Outside company premises, the OTC tablet relies on the internet network (also called WAN)
for data transfer, SIP signaling and media flows (VoIP and video communications).
The cellular network (3G or 4G) can also be used for data transfer if a data SIM card is
inserted into the tablet.
!"# $ %& #'(

41/195
Chapter 4 +,
% * &
Figure 4.11: Off-site topology with a reverse proxy and OTSBC

In this configuration, a secured network infrastructure is required for media and data
transmission between the OTC tablet and the company intranet network (LAN). This is
achieved by the following network components:
- A reverse proxy, which controls data flows (web services and device management)
through HTTPS connections
- A Session Border Controller (SBC), which controls VoIP and video communications
through SIP/TLS and SRTP connections
In addition, an OpenTouch Edge Server (OTES) may also be deployed in the secure network
infrastructure (DMZ) if it is has been delivered with the OpenTouch solution (optional
component). If it is the case, the OTES is used to control data flows (conferencing, data
sharing, instant messaging or web presentations) through HTTPS connections.
Figure 4.12: Off-site topology with a reverse proxy, OTSBC and OTES
4.6 Deployment procedure overview

The OTC tablet deployment consists in:
- Configuring the OTC tablet
- Configuring the OpenTouch ecosystem
- Installing the OTC tablet
- Launching the OTC tablet
- Configuring the OTC tablet settings
4.7 Configuring the OTC tablet
42/195 !"# $ %& #'(

+,
% * &
4.7.1 Process overview

The OTC tablet configuration consists in:
- Creating and associating new OTC tablet to Conversation users
This operation automatically creates a configuration file on the OpenTouch server required
for OTC tablet commissioning
Caution:
• To avoid synchronization issues, use the Users application of the OmniVista 8770 to
create and associate OTC tablet to users. Only the procedure from the Users application
is presented here.
• IT managers must be informed that if users change their device model (Android tablet to
iPad or vice-versa), it is necessary to update the OTC tablet configuration with the new
device type. This requires to recreate and associate an OTC tablet (with the new device
type) to the relevant users.
- Granting user access right to OTC tablet and conferencing
4.7.2 Prerequisites
The Conversation user must be declared on OpenTouch. For more information, refer to the
chapter User creation and administration of [3].
4.7.3 Creating and associating new OTC tablet to Conversation users

To create and associate a new OTC tablet to a Conversation user in one step:
2. Expand the tree structure and select the user to which the OTC tablet must be associated
3. Access the contextual menu and select Associate SIP device > New, then select OTC
Tablet
!"# $ %& #'(

43/195
Chapter 4 +,
% * &
Figure 4.13: OTC tablet creation and association window example

4. Complete the following mandatory field in the General tab:
Directory number If you want to manually enter a directory number, complete this field
with the OTC tablet number, else use the Directory numbering
range field.
Note:
As of R1.2, when a range of free directory numbers is configured for devices
in the user meta profile, this attribute is automatically filled with the first avail-
able free number of the selected range, and becomes the directory number
associated to this device
Tablet type According to your tablet model, use the drop-down list to select either
iPad (by default) or Android
Directory numbering When ranges of free directory numbers are configured for devices,
range you can select a range for assigning automatically a directory number
to the OTC tablet. In this case, the first available free number of the
selected range is associated to the OTC tablet after creation. It is
automatically displayed in the Directory number field

The new OTC tablet is created in the corresponding OpenTouch and associated to the
corresponding user. This OTC tablet is displayed under the user in the tree structure of
Users application
6. Click the Video tab and change the video profile from Low (default value) to Medium
using the drop-down menu in the Video Profile field
44/195 !"# $ %& #'(

+,
% * &

When the OTC tablet is created and associated to a Conversation user, a configuration file is
automatically created on the OpenTouch server. It is copied on the OpenTouch in the
directory: /opt/Alcatel-Lucent/oamp/cms/DevicesDeployment/OTTablet.
The OTC tablet configuration file is identified by the SIP URI of the iPad or Android tablet as
follows: <directory number>@<OpenTouch server FQDN>.
The configuration file is built from the parameters entered at OTC tablet creation. When the
OTC tablet is successfully registered and installed, all parameters are saved in the OTC tablet
memory.
4.7.4 Granting user access right to OTC tablet and conferencing
Note 1:
License Tablet may have already been added while creating user and configuring its profile (refer to the
chapter User creation and administration of [3]).
2. Expand the tree structure and select the user to which the OTC tablet is associated
3. In the properties area, select the OT configuration tab, then select the Licenses tab
Figure 4.14: User right configuration window example

4. Complete the following field:
!"# $ %& #'(

45/195
Chapter 4 +,
% * &
Tablet Select the check box to allow the user to use an OTC tablet
Conferencing Select the check box to allow the user to have access to the confer-
ence service
Note 2:
Select also the voice mail check box if the user has a voice mailbox.
4.8 Configuring the OpenTouch ecosystem

systems provided by ALE International, but interacting with the OpenTouch server and the
OTC tablet. The network elements to consider are:
- The firewall protecting the intranet (company LAN)
- The DNS servers (internet and intranet), used to resolve the FQDNs of the network
elements
- The reverse proxy, used to control data flows (web services and device management)
between the OTC tablet and OpenTouch server
- The OpenTouch Session Border Controller (OTSBC), used to control VoIP
communications between the OTC tablet and OpenTouch server
- The OpenTouch Edge Server (OTES) if provided by the OpenTouch solution (optional
component). In this case, it is used to control data flows (conferencing, data sharing,
instant messaging or web presentations) between the OTC tablet and OpenTouch server
To configure these network elements, refer to: OpenTouch Clients (Mobile and Desktop) -
Implementing OpenTouch Ecosystem .
4.9 Installing the OTC tablet
4.9.1 Installing the OTC Android Tablet

4.9.1.1 Overview
The OTC Android Tablet must be downloaded and installed on the Android tablet using the
Google Play Store (access path: https://play.google.com).
4.9.1.2 Prerequisites
The OpenTouch Conversation must be present in the Play Store of Google.
The Android tablet must be connected to the internet.
4.9.1.3 Installing the OTC Android Tablet from the Android tablet
1. From the Android tablet home screen, select the Play store icon if placed as a shortcut on
the home screen, or access the Applications screen and select the corresponding icon
2. From the Play Store, search for the OpenTouch Conversation with keywords, for example:
Alcatel-Lucent or conversation
46/195 !"# $ %& #'(

+,
% * &
3. Follow the instructions on screen to download the OpenTouch Conversation. When

download is finished, the Android automatically installs the OpenTouch Conversation. After
installation, the OpenTouch icon ( ) is displayed in the Applications
4. To place the OTC Android Tablet on the home screen, long press the application icon
(click and hold) and move it to place a shortcut on the home screen
4.9.2 Installing the OTC iPad

4.9.2.1 Overview
The OTC iPad must be downloaded and installed on the iPad using the App Store.
The OpenTouch Conversation must be present in the App Store for Apple products.
The iPad must be connected to the internet.
4.9.2.3 Installing the OTC iPad from the iPad
From the iPad home page, access the App Store and load the OTC iPad. The iPad
automatically installs the OTC iPad. After installation, the OpenTouch icon ( ) is displayed
in the iPad home page
4.10 Generating a QR code

A QR code (or Quick Response code) can be used to provide easy access to the OTC tablet
at first startup.
At first startup, the OTC tablet enables to use a QR code to avoid entering, for example, the
public and private FQDNs of the OpenTouch server. This requires to generate previously a QR
code including information such as:
<otcInfos>
<privateUrl>Private FQDN of the server</privateUrl>
<publicUrl>Public FQDN of the serveur</publicUrl>
<login>user login</login>
<RpLogin>Reverse Proxy login</RpLogin>
</otcInfos>
Example:
<otcInfos>
<privateUrl>private.mydomain.local</privateUrl>
<publicUrl>public.mydomain.com</publicUrl>
<login>my_login</login>
<RpLogin>my_rp_login</RpLogin>
</otcInfos>
There are online tools that can be used to generate the QR code.
The result is a figure similar to a bar code that can be either published or broadcast.
!"# $ %& #'(

47/195
Chapter 4 +,
% * &
Note:
All fields are optional.
4.11 Importing the certificate used to connect to the reverse proxy

(remote worker)
Two client authentication rules are available to connect to the reverse proxy, when moving
outside company premises (remote worker): by login/password or certificate.
In some installations, for security reason, the user login/password is not sufficient. A solution to
increase security is that the reverse proxy authenticates the user by certificate.
The user authentication by certificate requires to install the certificate on the OTC tablet
(trusted root certification store). The certificate can be imported on the tablet using any of the
following solutions:
- Import certificate using iTunes (only for OTC iPad):
1. Connect the iPad to a computer on which iTunes is installed
2. From iTunes, copy the certificate from the computer to the iOS application (the file
extension must be either p12 or pfx). For more information, see:
http://support.apple.com/fr-fr/HT201301
3. From the iPad, launch the OTC iPad and click the Import a certificate button (see:
OTC iPad context )
A window opens with the list of all available p12 and pfx files
4. Select the certificate
A pop-up window opens for passphrase entry. The passphrase is used to protect
PKCS12 certificates
5. Enter the corresponding passphrase, and click OK
- Import certificate using e-mail:
1. From the tablet, access the e-mail application
2. Open the e-mail including the certificate (the file extension must be otcert)
3. Click the certificate
A windows opens with the applications able to handle the certificate
4. Select the OTC tablet
PKCS12 certificates
4.12 Launching the OTC tablet
4.12.1 OTC iPad context

From the iPad home page, click the OpenTouch icon to access the OpenTouch server and
open the OTC iPad login window.
A login window is displayed:
48/195 !"# $ %& #'(

+,
% * &
Figure 4.15: Login window example

1. At first startup, you are prompted to provide access parameters to OTC iPad
Parameters entry can be performed either manually or automatically using a QR code if
configured (see: Generating a QR code )
• Manually: You are prompted to review/modify the following parameters:
Server Enter the private FQDN of the OpenTouch
Note 1:
At startup, the OTC iPad first tries to reach the private FQDN of the
OpenTouch server.
User Name Enter the user's authentication login to access the OTC iPad
Password Enter the corresponding password
For off-site mobility, review/modify the parameters in the Remote access area:
Server Enter the public FQDN of the OpenTouch server
Note 2:
At startup, if the private FQDN of the OpenTouch server cannot be reached,
the OTC iPad tries to reach the OpenTouch server through its public FQDN.
User Name Enter the user's authentication login to access the reverse proxy
!"# $ %& #'(

49/195
Chapter 4 +,
% * &
• QR code: Press the icon at the left of the Sign In button

This action opens an application similar to a camera, that can be pointed to the QR
code (published or present on a computer screen). If the QR code is acknowledged,
the access parameters provided by the QR code are automatically filled
2. If the reverse proxy authenticates users by certificate, it is required to install the certificate
in the application. One solution is to press the Import a certificate button. For more
information, refer to: Importing the certificate used to connect to the reverse proxy (remote
worker)
3. Click the Sign In button
Note 3:
If the Remember password check box is selected, you do not have to enter any password the next time
you log in to the OTC iPad. The passwords are automatically saved by the system and filled every time
you log in.
4.12.2 OTC Android Tablet context

From the Android tablet home page, click the OpenTouch icon to access the OpenTouch
server and open the OTC Android Tablet login window.
A login window is displayed:
Figure 4.16: Login window example

1. At first startup, you are prompted to provide access parameters to OTC Android Tablet
configured (see: Generating a QR code )
50/195 !"# $ %& #'(

+,
% * &
• Manually: You are prompted to review/modify the following parameters:

Public hostname Enter the public FQDN of the OpenTouch server
Note 1:
At startup, if the private FQDN of the OpenTouch server cannot be reached,
the OTC Android Tablet tries to reach the OpenTouch server through its pub-
lic FQDN.
Private hostname Enter the private FQDN of the OpenTouch
Note 2:
At startup, the OTC Android Tablet first tries to reach the private FQDN of the
OpenTouch server.
User Name Enter the user's authentication login to access the OTC Android Tab-
let
• QR code: Press the Scan QR Code button

2. Click the Connect button to access the OpenTouch server and open the OTC Android
Tablet application
Note 3:
According to configuration, you may be invited to validate the reverse proxy certificate.
3. Accept the certificate installation
The reverse proxy authentication window opens
!"# $ %& #'(

51/195
Chapter 4 +,
% * &
Figure 4.17: Reverse proxy authentication window example

4. Enter the user's authentication login and password to access the reverse proxy, and click
OK
The OTC Android Tablet main window opens
4.13 Configuring the OTC tablet settings

At initial startup, connection parameters to the OpenTouch server can be modified from the
iPad settings page as follows:
1. From the iPad home page, click the Settings icon
The settings page opens
2. In the left part of the settings page, select the OpenTouch option
Figure 4.18: iPad settings page example

52/195 !"# $ %& #'(

+,
% * &
OPENTOUCH area:
Server Enter the OpenTouch private FQDN (for example:
otprivate.company.com)
User Name Enter the user's authentication login to access the OTC iPad
Password Enter the user's authentication password to access the OTC iPad
Favorite display Use the left arrow to select contact display format:
name • First name + name's first letter + dot (for example: Mark S.)
• Name + first name's first letter + dot (for example: Spencer M.)
Note 1:
The iPad automatically validates any change performed in this attribute.
Enable debug mode To send log messages by e-mail from the OTC iPad, set the paramet-
er to ON (see: Accessing logs ).
Important:
The iPad must be restarted to validate the modification.
REMOTEACCESS area:
Server Enter the public FQDN of the OpenTouch server (for example: ot-
public.company.com)
User Name Enter the user's authentication login to access the reverse proxy
Password Enter the user's authentication password to access the reverse proxy
Note 2:
There is no validation button: the iPad automatically validates any change performed in the settings
page.

At initial startup, connection parameters to the OpenTouch server can be modified using the
Exit button, as follows:
1. Click the icon available at the top right part of the OTC Android Tablet
The settings page opens
!"# $ %& #'(

53/195
Chapter 4 +,
% * &
Figure 4.19: Settings page example

2. Press the Exit button to log out and exit the application
3. Relaunch the application and modify the public and/or private FQDNs of the OpenTouch
server according to your needs (see: OTC Android Tablet context )
Note:
If the public FQDN of the OpenTouch server changes, the certificate is automatically cleared.
4.14 Configuring the OpenTouch for conferences notifications by

e-mail
An e-mail server address must be managed in the ACS part of the OpenTouch server to allow
conferences initiated by iPad or Android tablet to be notified by e-mail.
To configure the ACS settings, access the ACS administration console as follows:
1. Open a session on the OmniVista 8770
2. Start the Configuration application, then expand the tree structure and select the
OpenTouch to which the OTC tablet is connected
3. Right click and select WBM
The WBM logging page is displayed
4. Enter admin credentials and navigate to Users and devices > System Configuration
The ACS administration console is displayed
5. Select the Configuration tab, then select the System Options item
Smart Mail Relay Enter the mail server address used for notification.
Host
Note:
The address must be either a FQDN or an IP Address in brackets.
7. Reboot the system for modifications to be completely taken into account
54/195 !"# $ %& #'(

+,
% * &
4.15 Accessing logs

The OTC iPad provides applicative logs. These log messages can be sent by e-mail, provided
that an e-mail access has been configured on the iPad.
Sending logs by e-mail is performed from the OTC iPad settings:
1. Click the contact picture available at the top left part of the OTC iPad
The OTC iPad settings window opens
___change-begin___
___change-end___
Figure 4.20: OTC iPad settings window example
2. Click the Send log file option to send log messages by e-mail
Note:
If the Send log file option is not displayed, verify that the Enable application log is activated in the
settings page of iPad (see: Configuring the OTC tablet settings ).

The OTC Android Tablet provides applicative logs. These log messages can be sent by e-mail,
!"# $ %& #'(

55/195
Chapter 4 +,
% * &
provided that an e-mail access has been configured on the tablet.

Sending logs by e-mail is performed from the OTC Android Tablet settings:
1. Click the icon available at the top right part of the OTC Android Tablet and select
Advanced settings
The OTC Android Tablet settings window opens
Figure 4.21: OTC Android Tablet settings window example

2. Click the Send log by email option to send log messages by e-mail
56/195 !"# $ %& #'(

5.1 Overview
The OpenTouch Conversation for PC includes an embedded SIP softphone, and can be
installed in a user desktop environment, either:
- On a computer where no collaboration application is installed.
In such a configuration, the OpenTouch Conversation for PC application is installed on the
computer as a standalone client. It can run on computers with any of the following
operating systems: Windows XP, Windows 7 (32/64 bits), or Windows 8 (64 bits)
- On a computer where a collaboration application is already running (IBM Domino).
In this configuration available as of R2.1.1, the OpenTouch Conversation for PC
application is installed into the collaboration client and they operate as a unified user
interface. When this occurs, OpenTouch Conversation for PC services are available when
the user logs in the IBM Domino client. The supported versions is IBM Domino 9.0
Extensions of the OpenTouch Conversation for PC can also be installed on the e-mail client
present on the computer on which the OpenTouch Conversation for PC must run. OpenTouch
Conversation for PC extensions are available for the followed e-mail clients:
- Microsoft Outlook. The supported versions are Microsoft Outlook 2010 (32 or 64-bit) and
2013 (32 or 64-bit)
- IBM Notes (as of R2.1.1). The supported version is IBM Notes 9.0
These extensions provide services such as: messaging, telephony, Instant Messaging (IM),
and presence.
For readability purposes, the OpenTouch Conversation for PC is called OTCV PC in the rest of
the document.

- The list of available OTCV PC features (see: Available features )
- A quick overview of the OTCV PC screens (see: Interface overview )
- Details on the OTCV PC network infrastructure (see: Topologies )
- Configuration of the OTCV PC on the OpenTouch (see: Configuring the OTCV PC on the
OpenTouch )
- Ecosystem configuration required for the OTCV PC use (see: Configuring the OpenTouch
ecosystem )
- OTCV PC installation on client computer (see: Installing the OTCV PC on client computers
)

The OTCV PC supports business communication features such as:
!"# $ %& #'(

57/195
Chapter 5 +,
% * .
- Multimedia services:
• Audio call
• Video call
• Instant Messaging (IM)
• Web presentation
- Ad-hoc and scheduled conferences
Different types of conferences are available:
• Meeting: for interactive business meetings. All licensed features are available
• Webinar: for conferences with a large audience, where participants view and listen
web presentations privately
• Training: for teacher student scenarios. All licensed features are available. The
conference ends when the teacher hangs up
• Conference call: for dial-in voice-only conferences, with browser based control
- Call routing profiles
- Conversation history
- Business event notifications:
• Missed calls
• Missed IMs
• New voice messages
- Directory lookup
- Management of favorite contacts
- Rich presence (user and phone)
- Visual Voice Mail (VVM)
- Collaboration services:
• Web presentations
- Features available from a Microsoft Outlook 2010/2013 client:
• Voice messages (play, record, hang-up)
• Audio call (click-to-call)
• Presence (favorite contacts)
- Application and desktop sharing
From a contact card, or in a peer to peer communication (audio/video), or video
conference (Ad hoc or scheduled),Conversation users can launch an application or
desktop sharing
- Exchange Instant Messaging (IM) and presence with external users on a collaboration
client such as Microsoft Lync 2013
This requires to implement the OpenTouch XMPP federation with a Microsoft Lync Server,
in the OpenTouch ecosystem.
- Wideband audio (G.722.2) with SIP signaling for communications between client
computers. Narrowband audio (G.711 A-law/µlaw, G.729 Annex A) codecs are also
supported.
58/195 !"# $ %& #'(

+,
% * .
- SIP TLS/SRTP (with Reverse Proxy and SBC network elements) for communications
between client computers
- Call recording (available on request. Each call is stored as a voice message in the voice
mail system)
- Multiline capabilities:
• Forth/resume
• Ad-hoc conference services

The OTCV PC home page opens immediately after login.
___change-begin___
___change-end___
Figure 5.1: OTCV PC home page example
The OTCV PC home page consists of:
1. A Personal area which displays information on the user profile, such as: picture, first and
last names, presence, and current routing profile (indicates the devices to which calls are
routed and the device used to make calls). Click the user picture to access user settings:
___change-begin___
!"# $ %& #'(

59/195
Chapter 5 +,
% * .
___change-end___
The available menus are:
• Presence: to specify your presence
• Photo/Avatar: to select your user picture(s)
• Preferences: to configure settings such as:
• Start: to select the OTCV PC starting mode
• General: to define the GUI language, show/hide caller identity (Calling Line
Identification Restriction or CLIR), and remove all information displayed in the
conversation wall (history deletion)
• Phone numbers: to define user professional and personal phone numbers
• Routing profiles: to create/modify/delete routing profiles (each profile indicates the
devices to which calls are routed and the device used to make calls)
• Overflow: to specify the destination to reroute incoming calls when the user is
unavailable and/or does not answer
• Alerts and sounds: to select the ringing tone
• Audio device: to configure computer audio settings
• Video device: to configure computer video settings
• Support: to generate and send logs to your support team
2. A Conversation wall presenting past conversations, current conversations and the
conferences to come. Click a card to display the corresponding
contact/conference/conversation window on the stage:
___change-begin___
60/195 !"# $ %& #'(

+,
% * .
___change-end___
Figure 5.3: Contact card example
On the stage, the available operations are:
• For a contact card:
• Make a new audio or video call
• Send an Instant Message (IM)
• Share a document
• Send an e-mail
• Add or remove the contact to your favorite contacts list
• Schedule a conference
• Remove the contact card
• For a conference card:
• Join the conference (with all medias, audio only or without audio)
• Send an e-mail to the participants
• Modify/delete the conference
• Remove the conference card
Note 1:
Removing a contact card from the Conversation wall entails that all conversations (audio/video),
Instant messages, and voice mails associated to this contact are removed. In the same way, all
cards present on the Conversation wall can be removed in one go. But this deletion does not
concern the conferences to come.
In the example below (contact card), click to successively display the conversation history
and contact details:
___change-begin___
!"# $ %& #'(

61/195
Chapter 5 +,
% * .
___change-end___
3. A Favorite contacts area used to access the list of favorite contacts. Click the star at the
bottom right of the OTCV PC home page to show (or hide) the list of favorite contacts:
___change-begin___
___change-end___
Figure 5.5: Favorite contacts area example
Favorite contacts are indicated by a star icon in the conversation wall.
4. An Application area used to access the OTCV PC applications:
Icon Application Select, to: Available operations
Missed Access the list of missed events. • Call back the other party
events A counter indicates the number of • Read the IM
unacknowledged missed calls and
missed IMs
Voice mail Access the Visual Voice Mail • Listen to a voice message
messages. • Delete all voice messages
A counter indicates the number of in one go
new voice messages
Conference Access the list of planned confer- • View scheduled conference
ences (scheduled and reservation- details
less) and conference invitations • Delete a conference
from other users. • Join a scheduled confer-
Create new conferences ence
Keypad Open the dialing keypad • Make an audio or video call
Settings Access the application settings • Change your picture, pres-

ence, and application set-
tings
62/195 !"# $ %& #'(

+,
% * .
Note 2:
The icon only appears when you are member of a supervision group, and logged in to this
group. The number in a red circle indicates the number of active supervisors in the group. When you
click the icon, a window opens with the list of group members. This window allows you to modify your
group options.
According to your needs, the OTCV PC home page can be resized using the icons available at
the bottom of the home page:
Icon Select, to:
Display the conversation history and favorite contacts in a horizontal view
Display the conversation history and favorite contacts in a vertical view
Either display the conversation history or favorite contacts in a reduced vertic-

al view. You must use tabs to switch from the favorite contacts (default view)
to the conversation history, and vice-versa
5.5 Topologies
5.5.1 On site topology

Within company premises, the OTCV PC relies on the company intranet network (LAN) for
media (voice/video) and data transmission. The OTCV PC can connect to the company
intranet network using a wired connection (Ethernet cable) or a wireless connection (Wi-Fi
network).
The OTCV PC uses:
- SIP signaling and RTP connections to perform VoIP and video communications
Note:
SIP and RTP are not encrypted within the company intranet network (no SIP/TLS and SRTP
connections).
services and OmniTouch ACS services)
!"# $ %& #'(

63/195
Chapter 5 +,
% * .
5.5.2 Off site topology (remote worker)

Outside company premises, the OTCV PC can rely on any of the following:
- If configured, a VPN (Virtual Private Network) connection to control data transfer, SIP
signaling and media flows (VoIP and video communications through RTP).
Figure 5.7: Off-site topology with VPN
64/195 !"# $ %& #'(

+,
% * .
- If a VPN connection is not configured, the internet network (also called WAN) for data
transfer, SIP signaling and media flows (VoIP and video communications)

transmission between the OTCV PC and the company intranet network (LAN). This is
• A reverse proxy, which controls data flows (web services and device management)
• A Session Border Controller (SBC), which controls VoIP and video communications
sharing, instant messaging or web presentations) through HTTPS connections. With or without
OTES deployment, users have the same level of features from their OTCV PC, when moving
outside company premises (off-site).
!"# $ %& #'(

65/195
Chapter 5 +,
% * .
Figure 5.9: Off-site topology with a reverse proxy, OTSBC and OTES

The OTCV PC deployment consists in:
- Configuring the OTCV PC on the OpenTouch
- Installing the OTCV PC on client computers
- Launching the OTCV PC
5.7 Configuring the OTCV PC on the OpenTouch

OTCV PC configuration for Conversation users consists in:
- Creating and associating an OTCV PC to a user
This operation automatically creates a configuration file, required for OTCV PC
commissioning, on the OpenTouch server
Caution:
You must use the Users application of OmniVista 8770 to create and associate OTCV PC to
users. Do not use the OpenTouch configuration window even if this application allows to
perform the same operations. Therefore, only the procedure from the Users application is
presented here.
- Granting users the right to access the application from a computer
5.7.2 Prerequisites and information required
66/195 !"# $ %& #'(

+,
% * .
Conversation users must have been previously declared on the OpenTouch. For more
information, refer to the chapter User creation and administration of [3]
5.7.3 Creating and associating an OTCV PC to a user

To create and associate an OTCV PC to a user in one go:
2. Expand the tree structure and select the user to which the computer must be associated
3. Access the contextual menu and select Associate SIP device > New, then select the
OTC Windows Desktop option
___change-begin___
___change-end___
Figure 5.10: OTCV PC creation and association window example
4. Complete the following fields in the General tab:
SIP URI This field is automatically completed after OTCV PC creation. It dis-
plays the SIP URI of the OTCV PC, as follows: <directory num-
ber>@OpenTouch server FQDN
Device number Enter the directory number for the OTCV PC
Desktop Type Select: Windows Desktop.

The OTCV PC is created in the corresponding OpenTouch and associated to the selected
user. This OTCV PC is displayed under the user in the tree structure of the Users
application
!"# $ %& #'(

67/195
Chapter 5 +,
% * .
When the OTCV PC is created and associated to an OpenTouch user, a configuration file is
automatically created on the OpenTouch server. It is copied in the OpenTouch in the directory:
/opt/Alcatel-Lucent/oamp/cms/DevicesDeployment/MYICPCXX.
The configuration file is identified by the SIP URI of the OTCV PC, as follows: directory
number@OpenTouch server FQDN.xml. It contains the attributes required for OTCV PC
installation on a client computer
5.7.4 Granting users the right to access the application from a computer
Note:
The computer license may have already been added while creating users and configuring their profile.
2. Expand the tree structure and select the user to which the computer is associated
The configuration window for the rights for this user opens
Figure 5.11: User rights configuration window example

Desktop Select the check box to allow the user to access the application from
a computer
68/195 !"# $ %& #'(

+,
% * .
5.7.5 Configuring the OTCV PC as multiline device

As of R2.1.1, the OTCV PC can be multiline with a maximum number of ten lines. It defines
the number of simultaneous calls that can be supported by the application, before it is
considered as busy. When this occurs, next incoming calls are forwarded to the voice mail.
To make the application multiline:
2. Expand the tree structure and select the target application
3. In the properties area, select the Configuration tab, then select the General tab
The configuration window for the calls number for this user opens
___change-begin___
___change-end___
Figure 5.12: Multiline configuration window example
4. Review/modify the following field:
Maximum number of Enter the maximum number of lines supported by the application (10
lines maximum). If the value remains to one, the application can only pro-
cess one incoming call at a time
Default value: 1
!"# $ %& #'(

69/195
Chapter 5 +,
% * .

OTCV PC. The network elements to consider are:
elements
between the OTCV PC and OpenTouch server
communications between the OTCV PC and OpenTouch server
- The OpenTouch Edge Server (OTES) if provided by the OpenTouch solution (optional
component). In this case, it is used to control data flows (conferencing, data sharing,
instant messaging or web presentations) between the OTCV PC and OpenTouch server
Implementing OpenTouch Ecosystem . This also includes the VPN configuration when it is
used instead of these network elements.
5.9 Installing the OTCV PC on client computers
5.9.1 Overview
OTCV PC may either be installed on client computers from the client computers themselves
(see: Performing a single client installation ), or deployed on several computers in one go (see:
Performing multiple client installation (mass provisioning) ).
Extensions of the OTCV PC are also installed when the Microsoft Outlook client is present on
the computer. No specific extension installation is required. Installation is performed at
installation of the OTCV PC on the computer: the OTCV PC installation program automatically
detects the presence of Microsoft Outlook on the client computer. If present on the computer,
extensions are installed transparently. This applies to single or multiple client installation (mass
provisioning).
5.9.2 Prerequisites
- You must have local administration rights on the target computers to install or uninstall the
OTCV PC
- You must have the OTCV PC installation package (for example:
OpenTouchConversation-2.1.xxx.xxx.msi)
The current version is provided with the installation file (*.iso format) of the OpenTouch
core: edit the *.iso file and select Products > otc > Clients >
OpenTouchConversation.
- The OTCV PC cannot be installed on computers where the OTCT PC is already running.
The OTCT PC must be uninstalled before installing the OTCV PC
- The Microsoft Visual C++ redistributable package must be installed on computers.
70/195 !"# $ %& #'(

+,
% * .
• In a single client installation: OTCV PC installation also includes the installation of the
Microsoft Visual C++ redistributable package, provided that it has not been installed
previously on computer.
• In a multiple client installation (mass provisioning): this package must be installed
manually on computers before installing OTCV PC.
The minimum version required is Microsoft Visual C++ redistributable 2013. It is available
from the Microsoft web site:
http://www.microsoft.com/en-us/download/default.aspx
- The Microsoft .NET Framework must have been installed previously on computers.
The version required is Microsoft .NET Framework 3.5. This version is available from the
Microsoft web site:
- If running, the Microsoft Outlook must be stopped on computers before installing OTCV PC
Note:
A control is performed during OTCV PC installation on client computer. A warning message is
displayed if MS Outlook is running.
5.9.3 Performing a single client installation

To install the OTCV PC on an single client computer:
1. Double click the OTCV PC setup file (for example:
OpenTouchConversation-2.1.xxx.xxx.msi) or use the following command line:
msiexec /i <access path>\OpenTouchConversation-<version>.msi
This displays the installation wizard welcome page
___change-begin___
___change-end___
Figure 5.13: Welcome window example
!"# $ %& #'(

71/195
Chapter 5 +,
% * .
2. Click Next
The license agreement window is displayed
Figure 5.14: License agreement window example

3. Read and accept the terms of the license, and click Next
A directory location selection window is displayed
Note 1:
The installation package searches for a previous version of OTCV PC on the target computer. When
a previous version is found, the setup process offers to delete, repair or remove the software.
72/195 !"# $ %& #'(

+,
% * .
Figure 5.15: Installation directory selection window example

4. If desired, change the installation directory and click Next
The shortcut creation window is displayed
Figure 5.16: Shortcut creation window example

5. Select your desired type(s) of shortcut and click Next
!"# $ %& #'(

73/195
Chapter 5 +,
% * .
If Microsoft Outlook (2010 or 2013) is present on the computer, the installation wizard
allows to select OpenTouch features to deploy on Microsoft Outlook, such as scheduled
conferences.
Figure 5.17: OpenTouch feature selection window example

By default, all available OpenTouch features are installed on Microsoft Outlook if present
on the computer.
6. According to your needs, enable or disable the OpenTouch features that must be deployed
on Microsoft Outlook and click Next
A server information window is displayed
74/195 !"# $ %& #'(

+,
% * .
Figure 5.18: Server information window example

7. Complete the following parameters:
• Server's private address: Enter the private FQDN of the OpenTouch server. This
allows the OTCV PC to connect to the OpenTouch server within company premises
(see: On site topology )
• Server's public address: Enter the public FQDN of the OpenTouch server. This
allows the OTCV PC to connect to the OpenTouch server when outside company
premises (see: Off site topology (remote worker) )
8. Click Next
The installation confirmation window is displayed
!"# $ %& #'(

75/195
Chapter 5 +,
% * .
Figure 5.19: Installation confirmation window example

9. Click the Install button to start installation
Note 2:
If necessary, click the Back button to change any option previously configured.
At the end of the process, the installation wizard finalization window is displayed
___change-begin___
76/195 !"# $ %& #'(

+,
% * .
___change-end___
Figure 5.20: Installation wizard finalization window example
10. If desired, select the check box to automatically launch the OTCV PC after the installation
wizard is closed, and click Finish
This closes the installation wizard
5.9.4 Performing multiple client installation (mass provisioning)

Standard deployment tools are available to install several clients simultaneously from a remote
computer on the network.
These tools rely on command lines. For an OTCV PC installation with the msi package, the
command line used is: msiexec /i <access
path>\OpenTouchConversation-<version>.msi /qn where:
- /i specifies the msi package to run
- <access path> specifies where is located the msi package
- /qn requests installation to run silently
The command line can include additional options such as:
Option Value Meaning
INSTALL_VCREDIST2013 0 or 1 If set to 0, the Microsoft Visual Studio C++
2013 Redistribuable package installation
(execution of vcredist.exe) is disabled
OTC_TARGET_DIR Any valid path Specify the installation folder where the
OTCV PC must be installed
Note 1:
The default path is: <program
files>\Alcatel-Lucent\OpenTouch Con-
versation
OTC_DESKTOP_ICON True or False If set to True (default value), a shortcut to
OTCV PC is added to the computer
OTC_START_ICON True or False If set to True (default value), a shortcut to
OTCV PC is added to the computer start
menu
Note 2:
In the two cases, a shortcut is automatically
placed in the following path: Start > Alcatel-
Lucent > OpenTouch Conversation
OTC_SERVER_NAME Any valid FQDN (no Specify the private FQDN of the OpenTouch
IP address) server (on-site mobility)
This field is optional (can be left empty) and
has no default value.
!"# $ %& #'(

77/195
Chapter 5 +,
% * .

OTC_PROXY_NAME Any valid FQDN (no Specify the public FQDN of the reverse
IP address) proxy used by the OTCV PC to connect to
the OpenTouch server outside company
premises (off-site mobility)
This field is optional (can be left empty) and
has no default value.
OPTIONAL_FEATURES 0 to 3 In addition, the OTCV PC installation can in-
clude the installation of OpenTouch features
in Microsoft Outlook:
- 0: no feature
- 1: telephony and voice messaging
- 2: Instant Messaging (IM), presence and
click-to-call
- 3: all features (default value)
CONFERENCE_ADDIN 0 or 1 If set to 1, the OTCV PC installation also in-
cludes the installation of the conference fea-
ture in Microsoft Outlook (scheduled confer-
ences)
Default value: 1
AUTORUN_APP 0 or 1 If set to 1, the OTCV PC automatically
starts after installation
Default value: 0 (if the installation is per-
formed in silent mode)
These additional options must be entered in upper case (mandatory).

Example:
msiexec /i D:\soft\OpenTouchConversation-2.1.021.000.msi /qn
OTC_TARGET_DIR=C:\Program\Alcatel-Lucent\OpenTouchConversation
OTC_DESKTOP_ICON=False OTC_PROXY_NAME=rp.mycompany.com
5.10 Using certificates for OpenTouch access authentication

To allow the OTCV PC to authenticate the OpenTouch certificate, it is necessary to store the
Hierarchy of certification of the OpenTouch on the trusted root certificate store of OTCV PC. If
the server certificate cannot be authenticated, the following message is displayed at client
application startup:
78/195 !"# $ %& #'(

+,
% * .
When this occurs, press the button Proceed anyway to bypass this control and start the
application.
Based on the type of deployment of the certificate selected at installation, different files must
be retrieved and stored on the trusted root certificate store of OTCV PC:
- Installation with SECURITY set to OFF.
For such deployment, a default certificate is installed during the software deployment.
Connect to the OpenTouch server and retrieve the file server.pem from directory
/var/data/certificate.
- Installation with SECURITY set to ON with Auto-generated certificate.
For such deployment, a Root certificate is generated to build the server certificate.
Connect to the OpenTouch server and retrieve the file ca.pem from directory
/var/data/certificate.
- Installation with SECURITY set to ON with Customized certificate from an external PKI.
For such deployment, the PKI administrator must provide the Customized certificate for the
server along with one or several Root certificates of the certification hierarchy (from Root
certificate down to the certificate that signed the Server certificate).
Once the Root certificates have been retrieved, two deployment processes are available on
the computer on which the application runs:
- Automatic process using the Windows domain controller (GPO):
1. From the computer, click Start, point to Administrative Tools, and then click Group
Policy Management
2. From the console tree, double click Group Policy Objects in the forest, and domain
containing the Default Domain Policy Group Policy object (GPO) that you want to edit
3. Right click the Default Domain Policy GPO, then click Edit
4. From the Group Policy Management Console (GPMC), go to Computer
Configuration > Windows Settings > Security Settings, then click Public Key
Policies
5. Right click the Trusted Root Certification Authorities store and click Import
6. Follow the instructions in the Certificate Import Wizard to import the certificates
- Manual process using Administrator rights:
1. From the computer, rename the certificate files extension from *.pem into *.cer
2. Double click the Root certificate to view the certificate.
!"# $ %& #'(

79/195
Chapter 5 +,
% * .
For the Root certificate the Fields Issued to and Issued by are identical.
3. Click the Install certificate button
4. Select manually the store Trusted Root certificate authorities to force the certificate
to be trusted
80/195 !"# $ %& #'(

+,
% * .
5. Click the Next button, then Finish to load the certificate:
!"# $ %& #'(

81/195
Chapter 5 +,
% * .
If intermediate certificates are also provided, install these certificates signed by the
Root Certificate using this procedure and repeat this operation up to the certificate
which has signed the server certificate.
5.11 Launching the OTCV PC
5.11.1 Prerequisites
- OTCV PC users must be declared on the OpenTouch with rights to the Desktop feature
(see: Granting users the right to access the application from a computer ).
- If starting OTCV PC from outside company premises (off site mobility), ensure that the
public URLs of the network components have been configured (see: OpenTouch Clients
(Mobile and Desktop) - Implementing OpenTouch Ecosystem - Configuring the internet
DNS server ).
- Certificates for OpenTouch access authentication must be installed on OTCV PC (see:
Using certificates for OpenTouch access authentication )
5.11.2 Connecting to the OpenTouch server

Once the OTCV PC is installed on the client computer, proceed as follows:
1. Start the OTCV PC using any of the following methods:
• Select the shortcut from the start menu of Windows
• Click the icon on the client computer
At startup, the OTCV PC first tries to reach the private FQDN of the OpenTouch server. If
the private FQDN of the OpenTouch server can be reached, and this is your first login (or if
the Remember password option was not selected at previous login), the login window is
displayed.
82/195 !"# $ %& #'(

+,
% * .
Figure 5.25: OTCV PC login window example

2. Complete the parameters:
Server Modify if necessary the private FQDN of the OpenTouch server
entered at OTCV PC installation
Username Enter an authentication login to access the OTCV PC
Password Enter the password
3. Click Connect
At first connection, the OpenTouch server sends its certificate. If this certificate is validated
by the current Root certificates installed on the computer trusted store, you are logged in.
You may need to restart the application to take into account the language configured on
the OpenTouch server. This occurs when the user language, which is initially the language
of the operating System, differs from the language configured on the OpenTouch server.
The OTCV PC main window opens
Note 1:
An icon in the Windows task bar ( ) indicates telephone presence status. Place the mouse over
this icon to display the current routing profile.

If the private FQDN of the OpenTouch server cannot be reached, the OTCV PC tries to reach
the server through the public FQDN of the OpenTouch server. A remote connection
authentication window is displayed.
When this occurs, the following parameters must be entered:
- The public FQDN of the OpenTouch server
!"# $ %& #'(

83/195
Chapter 5 +,
% * .
- The authentication login to access the reverse proxy

- The password
Note 2:
At startup, the OTCV PC:
- Automatically detects the available audio sources:
• Microphone and speakers on the computer
• Digital audio devices (headset, earset, or speakers) connected to the computer
• Bluetooth devices associated to USB dongles connected to the computer
- Selects the most appropriate audio source
The same detection and selection apply when an audio device is connected to (or disconnected from) the
computer.
5.12 Configuring the OTCV PC extensions in Microsoft Outlook

To verify that OTCV PC extensions are present and active on the Microsoft Outlook client:
1. From the Microsoft Outlook interface, click the File menu and select the Options item
The Outlook option window is displayed
2. Select the Add-ins option
The list of active and inactive add-ins is displayed (example for Outlook 2010)
84/195 !"# $ %& #'(

+,
% * .
3. Verify that OTCV PC extensions are present in the list of add-ins

From this page, you can perform any of the following:
• Verify the OTCV PC extensions are active. At the bottom of the window, select COM
Add-ins in the Manage item and click Go
The check box must be selected for OTCV PC extensions.
If it is not the case, select the corresponding check box and click OK to validate your
modification
• Verify and modify if necessary the OTCV PC extension settings:
1. At the top of the window, click the Add-in Options button
The add-in option window is displayed
2. Click the OpenTouch tab to display the OTCV PC extension settings
Note:
For the OpenTouch Outlook® Conference Scheduling add-in, update the URLs and
password.
To use the OTCV PC extensions from Microsoft Outlook:
- A user e-mail account must be created in Outlook (access path: File > Info)
- The OTCV PC must be launched on the computer with the Conversation user credentials
At application startup, if a Microsoft Outlook client is installed on the PC, users are prompted to
select the OTCV PC as their IM provider:
- If they select Yes, application extensions are available in Microsoft Outlook
- If they select No, extensions are available in the home tab (audio call, video call), not from
MS Outlook
To access the features provided by OTCV PC extensions, click the Home tab and select the
Mail menu of the Microsoft Outlook interface. A group of commands dedicated to the
OpenTouch must be present in the Microsoft Outlook Ribbon (top button bar).
5.13 Uninstalling the OTCV PC from client computers

Prerequisite: Microsoft Outlook must be stopped on client computers before uninstalling the
OTCV PC. A control is performed at OTCV PC uninstallation on the client computer. A warning
message is displayed if Microsoft Outlook is running.
To uninstall the OTCV PC from a client computer:
1. Open the Add/remove programs interface in the Control panel of the client computer
2. Select the OpenTouch Conversation program and click Remove
Note:
The OTCV PC uninstallation cannot be performed from the Start menu.
Performing multiple client uninstallation is possible from the msi package, using the following
command line:
msiexec /x "<access path>\OpenTouchConversation-<version>.msi" /qn
5.14 Accessing logs

Saving log files is performed from the OTCV PC settings:
!"# $ %& #'(

85/195
Chapter 5 +,
% * .
1. In Personal area of the OTCV PC which displays information on the user profile, click the
user picture
The user settings window opens
2. Select Preferences > Support
___change-begin___
___change-end___
Figure 5.27: OTCV PC Settings window
3. Select the Activate logging check box (deactivated by default) and click Apply to allow
log files to be saved on the computer
Caution:
Logs are deactivated after each application startup.
4. Click Save logs… to save log files on computer.
A browser window opens
5. Select the folder on which log files must be saved and validate
86/195 !"# $ %& #'(

6.1 Overview
the OpenTouch Conversation for smartphone (OTC smartphone) available for Conversation
and Connection users. This application is designed to run on iPhones and Android
smartphones.
On each market store (Play Store for Google and App Store for Apple), there is only one single
application that can be used for both Conversation and Connection users. At user logon, the
application adapts its behavior according to the type of user logged in. After logon, the user
type can be verified using the About menu of the OTC smartphone.
Accessing the OTC smartphone is subject to license control. Refer to the license management
documentation and commercial catalog.
For readability purposes, unless stated otherwise, the OpenTouch Conversation for iPhone
(OTC iPhone) and OpenTouch Conversation for Android smartphone (OTC Android
Smartphone) are called OTC smartphone in the rest of the document.
6.2 About this document

- The list of available OTC smartphone features (see: Available features )
- A quick overview of the OTC smartphone screens (see: Interface overview )
- Details on dual mode (Wi-Fi/cellular) when the OTC smartphone operates within company
premises (see: Dual mode (Wi-Fi/cellular) within company premises )
- Details on VoIP communications when the OTC smartphone operates outside company
premises (see: VoIP communications outside company premises )
- Details on the OTC smartphone network infrastructure (see: Topologies )
- The configuration of the OTC smartphone for Conversation users (see: Configuring the
OTC smartphone for Conversation users )
- The configuration of the OTC smartphone for Connection users (see: Configuring the OTC
smartphone for Connection users )
- The ecosystem configuration required for OTC smartphone use (see: Configuring the
OpenTouch ecosystem )
- The installation of OTC smartphone on smartphones (see: Installing the OTC smartphone
application on smartphones )

Note:
The features are available for the two applications OTC iPhone and OpenTouch Conversation for
Android smartphone. Depending on the user type (Conversation or Connection), some features may not
!"# $ %& #'(

87/195
Chapter 6 +,
% *
/ %
0
be available.
Features Connection Conversation

Single User eXperience across multiple devices Yes
Computer, tablet, smartphone and deskphone
One business number Yes
View the history of voice calls (past and ongoing), Yes
instant messages (past and ongoing), and sched-
ules conferences (past, ongoing, and future)
Check notifications on new voice message, Yes
missed call, instant message, or scheduled con-
ference
Check notifications on callback request No Yes
Change my photo/avatar and presence Yes
Edit user profile to modify private phone numbers Yes
Consume a call routing profile predefined by the Yes
IT Manager
Create or delete a call routing profile No Yes
Call routing profile configuration with immediate Yes
forwarding to a user or voice mail
Directory lookup (local contact on the device, or Yes
corporate or OpenTouch use)
Voice over IP everywhere (*) No Yes
Visual voice mail with file download Yes
Make a call from a directory lookup, enterprise di- Yes
aling plan, conversation history, voice mail inter-
face, or scheduled conference
Calling line identification restriction (CLIR) activa- No Yes
tion/deactivation
Muting/unmuting microphone (**), loudspeaker Yes
on/off (**), call recording, hold, new call, starting
chat session (escalation)
Add participant No Yes
Handover from Wi-Fi to cellular No Yes
Pushing a call from mobile to another device Yes
Transferring a call (from idle mode, active call on No Yes
another device)
Muting/unmuting microphone (**), loudspeaker Yes
on/off (**), back and forth, attended call transfer,
3-party ad-hoc conference, leaving a conference,
ending a conference
n-party ad-hoc conference No Yes
Caller identification (when local or OpenTouch Yes
contact are identified)
88/195 !"# $ %& #'(

+,
% * /
%
0
Features Connection Conversation

Divert incoming call to the voice mail, number, or Yes
chat
Enable/disable Call Supervision and Manager As- No Yes
sistant delegation
Start with a simple one-to-one chat and add Yes
people, add voice, add content
View presence and availability of favorite contacts Yes
and tap to start and manage collaborative conver-
sations
Favorite list and rich presence Yes
Access from conversation history to any of the fol- Yes
lowing:
- An incoming scheduled conference
- The details of a past scheduled conference
- The details of a past chat session
Private call allowed when the application is run- Yes
ning
Download from the Market Store Yes
Remote configuration and provisioning Yes
Client authentication via login/password Yes
Client authentication via certificate Yes
Server authentication via certificate Yes
Secure Web Services signaling (HTTPS) Yes
SIP TLS, SRTP No Yes
OpenTouch platforms (OTBE, OTMS, OTEC) Yes
Edge connectivity (RP) Yes
Edge connectivity (SBC) No Yes
(*): The voice quality of calls depends on the corporate WLAN, Wi-Fi or cellular data network
connection.
(**): Available service for iPhone only in VoIP mode.

TheOTC smartphone home page opens immediately after login.
___change-begin___
!"# $ %& #'(

89/195
Chapter 6 +,
% *
/ %
0
___change-end___
Figure 6.1: OTC smartphone home page example
The OTC smartphone home page consists of:
1. A personal area, which displays information on the user profile such as: picture, first and
last names, and current routing profile (that is the destination for incoming calls). Press the
user picture to access user profile settings. The options may differ according to the
application used and the user rights to features such as Manager/Assistant or Supervision.
___change-begin___
90/195 !"# $ %& #'(

+,
% * /
%
0
___change-end___
Figure 6.2: User profile page example for an OTC iPhone
___change-begin___
!"# $ %& #'(

91/195
Chapter 6 +,
% *
/ %
0
___change-end___
Figure 6.3: User profile page example for an OTC Android Smartphone
2. An active area, which displays the current application.
The following figures provide a general overview of the applications that can be displayed
on the OTC iPhone home page. These figures are similar for OTC Android Smartphone.
___change-begin___
___change-end___
Figure 6.4: General overview of OTC iPhone applications
3. A selection area used to access the OTC smartphone applications:
92/195 !"# $ %& #'(

+,
% * /
%
0
Application Icon Select, to: Available operations

Home Access the conversation wall, • Make a call
presenting past, current and future • Filter calls (all calls or missed
conversations and conferences. calls only)
A counter indicates the number of • Manage calls (delete or ac-
missed events knowledge)
• Display call details
Contacts Access the list of contacts and fa- • Filter contacts (all or favorites
vorite contacts only)
• Search contact (local or corpor-
ate)
• Display contact details
• Make a call from the Contacts
tab (including private call cap-
ability)
• Pick up a call
Voice mail Access the Visual Voice Mail • Listen a voice message
messages. • Make a direct call back
new messages
Conference Access the list of the user's confer- • Consult scheduled conference
from other users
6.5 Dual mode (Wi-Fi/cellular) within company premises

When they are associated to Conversation users, within company premises, smartphones can
operate in cellular mode or dual-mode (Wi-Fi/cellular). This is defined by the Dual mode
parameter, available when the smartphone is declared in the OpenTouch server (see:
Configuring the OTC smartphone for Conversation users ).
In dual-mode, the OTC smartphone automatically uses the Wi-Fi enterprise network (that is
the WLAN) for call handling (VoIP calls). If the Wi-Fi is not available, the cellular network is
used for call handling. The OTC smartphone application can also switch manually between
Wi-Fi and cellular networks. The OTC smartphone relies on the smartphone (iPhone or
Android) platform for the data bearer choice.
When the dual-mode is active and the smartphone roams:
- From the cellular network to the Wi-Fi:
• If the smartphone is idle (no call in progress), the OTC smartphone automatically
detects that the smartphone is in a Wi-Fi coverage area and performs a SIP
registration on the OpenTouch server. After registration, the OTC smartphone handles
incoming and outgoing calls over the Wi-Fi as it would handle VoIP calls
• If the smartphone is in communication (cellular call), the communication remains on
the cellular network (no handover). When the communication is released, the OTC
smartphone application performs a SIP registration on the OpenTouch server. After
registration, the OTC smartphone application handles incoming and outgoing calls over
!"# $ %& #'(

93/195
Chapter 6 +,
% *
/ %
0
the Wi-Fi as it would handle VoIP calls

Note:
In the Wi-Fi coverage, users can handle private calls (incoming/outgoing) from their smartphone via
the cellular network, even if the smartphone is registered as SIP device in the OpenTouch server and
uses the Wi-Fi to handle business calls. While in communication, two situations can occur:
• The user is in business communication and receives a private call: he/she takes the
private call. The current business call is put on hold. When the private call is released,
the business call on hold must be resumed by the user
• The user is in private communication and receives a business call: he/she cannot take
the business call. The business call is directly routed to the user voice mail and the call
is seen as missed call
- From the Wi-Fi network to the cellular network:
• If the smartphone is idle (no call in progress), the OTC smartphone relies on the
platform features to select the 3G as a data bearer and all subsequent calls are made
using the cellular network
• If the smartphone is in communication (VoIP call), the user can manually switch the
communication to the cellular network without interruption of the communication
(seamless handover). The communication is then processed by the cellular network.
When the communication is released, the OTC smartphone handles incoming and
outgoing calls over the cellular network
6.6 VoIP communications outside company premises

Outside company premises, the OTC smartphone relies on the cellular network and PSTN
network for voice communications (no voice over IP). As of R2.1, when they are associated to
Conversation users, the OTC smartphone supports Voice over IP (VoIP) communications
outside company premises, using either the Wi-Fi internet network (home spot or public
hotspot) or cellular network (3G, 4G). The OTC smartphone automatically uses the Wi-Fi
internet network for VoIP call handling. If no Wi-Fi is available, the OTC smartphone switches
to the cellular network to handle VoIP calls.
An OpenTouch Session Border Controller (OTSBC) must be deployed to secure VoIP calls
between the OTC smartphone and OpenTouch server (see: Off-site topology ). This also
requires to install the OTSBC certificate on the smartphones (iPhone or Android) before using
the OTC smartphone. This certificate must be installed using the appropriate native iPhone or
Android capabilities (as any other security certificate).
When the smartphone is connected to the network (Wi-Fi or cellular), and the OTC
smartphone has received its settings such as the connection parameters to OTSBC, the
application performs a SIP registration on the OpenTouch server through the OTSBC. After
registration, the OTC smartphone can handle VoIP calls.
table 6.3: Roaming capabilities
Roaming from a network to another one SIP registration
Cellular network to Wi-Fi internet network (home or hotspot) Yes
Wi-Fi internet network to cellular network Yes
Cellular network to another type of cellular network (for ex- Yes
ample: 3G to 4G)
According to the type of network that the smartphone is connected to (Wi-Fi, 3G, 4G, EDGE,
GPRS), even if the SIP registration is successful, this connection may not be sufficient to
94/195 !"# $ %& #'(

+,
% * /
%
0
support VoIP calls (for example, EDGE or GPRS).

table 6.4: Handover capabilities
Active call on: Moving call to: Handover mechanism
VoIP over Enterprise Wi-Fi VoIP over 3G/4G via SBC (*) The end-user must therefore
trigger a handover to Voice
over Cellular in order to main-
tain the conversation.
As soon as the active call is re-
leased, the system will author-
ize 'VoIP over 3G/4G' registra-
tion.
VoIP over 3G/4G via SBC (*) VoIP over Enterprise Wi-Fi The end-user must therefore
trigger a handover to Voice
over Cellular in order to main-
tain the conversation.
ize 'VoIP over Enterprise Wi-Fi'
registration.
VoIP over Enterprise Wi-Fi Voice over Cellular The end-user must trigger a
handover to Voice over Cellular
in order to maintain the conver-
sation.
Voice over Cellular VoIP over Enterprise Wi-Fi Handover is not supported.
ize ‘VoIP over Enterprise Wi-Fi’
registration.
VoIP over Home Wi-Fi via VoIP over 3G/4G via SBC (*) Automatic handover is possible
SBC but not recommended due to
VoIP over 3G/4G via SBC VoIP over Home Wi-Fi via Quality of Service concern
SBC (poor 3G/4G mobile data cover-
age outside cities, voice packet
loss during switch).
VoIP over Home Wi-Fi via Voice over Cellular The end-user must trigger a
SBC handover to Voice over Cellular
in order to maintain the conver-
sation.
Voice over Cellular VoIP over Home Wi-Fi via Handover is not supported.
SBC As soon as the active call is re-
ize ‘VoIP over Home Wi-Fi’ re-
gistration.
(*): ‘VoIP via cellular network’ setting option is activated.

Take care about ‘VoIP over 3G/4G’ as mobile data coverage is poor outside cities.
6.7 Topologies
!"# $ %& #'(

95/195
Chapter 6 +,
% *
/ %
0
6.7.1 Topologies for Conversation users

6.7.1.1 On-site topology
Caution:
For better User eXperience, ALE International recommends to use the Wi-Fi network when it is
available (increasing response time concern on operator data networks due to increasing
smartphone market share).
When they are associated to Conversation users, within company premises, the OTC
smartphone can operate in cellular mode or dual-mode (see: Dual mode (Wi-Fi/cellular) within
company premises ). When the OTC smartphone operates in dual-mode, the application
automatically uses the enterprise Wi-Fi network (also called Wireless Local Area Network
(WLAN)) for data and voice transmission. In the Wi-Fi coverage area, smartphones are
identified as SIP devices by the OpenTouch server.
The OTC smartphone uses:
- SIP signaling and RTP connections to perform VoIP communications
Note:
connections).
- HTTPS connections to exchange data with the OpenTouch server (web services)
If the company Wi-Fi network is not available, the OTC smartphone uses the cellular network
(2.5G, 3G or 3G+) for voice and data transmission.
___change-begin___
96/195 !"# $ %& #'(

+,
% * /
%
0
___change-end___
Figure 6.5: On-site topology example
6.7.1.2 Off-site topology
Caution:
For better User eXperience, ALE International recommends to use the Wi-Fi network when it is
available (home spot or public hotspot).
When they are associated to Conversation users, outside company premises, the OTC
smartphone can operate on any of the following networks:
- The Wi-Fi internet network (home spot or public hotspot) for data transmission and VoIP
communications
- The cellular network (2.5G, 3G, 3G+ or 4G) and internet for data transmission and VoIP
communications
A secured network infrastructure is required for data transmission and VoIP communications
between the OTC smartphone application and the OpenTouch services of the OpenTouch
server. This is achieved by the following network components:
- A reverse proxy, which controls data transmission (web services and device management)
- An OpenTouch Session Border Controller (OTSBC), which controls VoIP communications
As an option, the Wi-Fi internet network (home spot or public hotspot) and GSM network can
also be used for data transmission.
___change-begin___
___change-end___
Figure 6.6: Off-site topology example
If the Wi-Fi internet network is not available, the OTC smartphone uses the cellular network for
!"# $ %& #'(

97/195
Chapter 6 +,
% *
/ %
0
data transmission and voice communications. If an OTSBC is not available, voice

communications rely on the cellular network and PSTN network.
sharing, instant messaging or web presentations) through HTTPS connections.
___change-begin___
___change-end___
Figure 6.7: Off-site topology example including an OTES
For the OTC iPhone application only:
A VPN (Virtual Private Network) connection can be configured on the iPhone to control data
transfer, as well as SIP signaling and media flows between the OTC iPhone and OpenTouch.
This solution does not require a network element such as a reverse proxy, OTSBC or OTES.
___change-begin___
98/195 !"# $ %& #'(

+,
% * /
%
0
___change-end___
6.7.2 Topologies for Connection users

6.7.2.1 On-site topology
When they are associated to Connection users, within company premises, the OTC
smartphone application relies on the enterprise Wi-Fi network for data transmission. Voice
flows are routed on the cellular network (2.5G, 3G, or 3G+) and PSTN.
___change-begin___
___change-end___
Figure 6.9: On-site topology example
6.7.2.2 Off-site topology

When they are associated to Connection users, outside company premises, the OTC
smartphone application relies on:
- The cellular network (2.5G, 3G, or 3G+) and WAN for data transmission
Note:
As an option, the Wi-Fi internet network (home spot or public hot spot) and GSM network can also be
used for data transmission.
- The cellular network (2.5G, 3G, or 3G+) and PSTN network for voice flows
A secured network infrastructure is required for data transmission between the smartphones
and the OTC smartphone services of the OpenTouch server. This is achieved by a reverse
proxy, which secures data transmission through HTTPS connections to or from the
OpenTouch server.
___change-begin___
!"# $ %& #'(

99/195
Chapter 6 +,
% *
/ %
0
___change-end___
Figure 6.10: Off-site topology example
For the OTC iPhone application only:
A VPN (Virtual Private Network) connection can be configured on the iPhone to control data
transfer, as well as SIP signaling and media flows between the OTC iPhone and OpenTouch.
This solution does not require a reverse proxy (see: figure: Off-site topology with VPN ).

The OTC smartphone deployment consists in:
- Configuring the OTC smartphone for Conversation users
- Configuring the OTC smartphone for Connection users
- Installing the OTC smartphone application on smartphones
6.9 Configuring the OTC smartphone for Conversation users

The OTC smartphone configuration for Conversation users consists in:
- Creating and associating an OTC smartphone to Conversation users
This operation automatically creates a configuration file on the OpenTouch server required
for OTC smartphone commissioning
100/195 !"# $ %& #'(

+,
% * /
%
0
Caution:
• You must use the Users application of OmniVista 8770 to create and associate OTC
smartphone to users. Do not use the OpenTouch configuration window even if this
application allows to perform the same operations. Therefore, only the procedure from
the Users application is presented here.
• IT managers must be informed that if users change their device model (Android
smartphone to iPhone or vice-versa), it is necessary to update OTC smartphone
configuration with the new device type. This requires to recreate and associate an OTC
smartphone (with the new device type) to the relevant users.
- Granting the Conversation user right to off-site mobility
6.9.2 Prerequisites and information required

- The Conversation users must be declared on OpenTouch. For more information, refer to
the chapter User creation and administration of [3]
- The following information is required for OTC smartphone configuration on the
OpenTouch:
• The public directory number of the SIM card of the smartphone (iPhone or Android) on
which the OTC smartphone runs.
• The external call prefix used to access the public network
Note:
The smartphone IMEI is not necessary for configuration on the OpenTouch. The smartphone is
created in the OpenTouch server regardless of the smartphone type (there is no hardware link
between the device and the OpenTouch). This simplifies smartphone creation, as the smartphone
IMEI is not necessary anymore.
6.9.3 Creating and associating an OTC smartphone to Conversation users

To create and associate an OTC smartphone to a Conversation user in one go:
2. Expand the tree structure and select the Conversation user to which the smartphone must
be associated
OTC Smartphone option
___change-begin___
!"# $ %& #'(

101/195
Chapter 6 +,
% *
/ %
0
___change-end___
Figure 6.11: OTC iPhone creation and association window example
4. Complete the following fields in the General tab:
Device identity This field is automatically completed after OTC smartphone creation. It
displays the OTC smartphone internal identifier as follows: MO-
BILE_<number>
Device number Enter the directory number for the OTC smartphone
Dual mode Select the check box to enable the OTC smartphone to use either the
cellular network or Wi-Fi network for call handling within company
premises (see: Dual mode (Wi-Fi/cellular) within company premises ).
If the check box is not selected, the OTC smartphone only uses the
cellular network for call handling within the company premises.
Note:
By default, the dual mode option is selected.
Type of mobile According to your device model, use the drop-down list to select either
iPhone (by default) or Android
GSM number Enter the GSM number of the smartphone on which the OTC smart-
phone runs.
The canonical format is: country code + external call prefix + public
directory number (for example: +33 (0) 6 12 34 56)
5. If necessary, activate SIP QoS (optional):

a. Select the Network tab and review/modify the following attribute:
102/195 !"# $ %& #'(

+,
% * /
%
0
SIP IP TOS Enter 35 (default value: 0)
b. Select the RTP tab and review/modify the following attribute:

RTP IP TOS Enter 56 (default value: 0)
RTP TOS enable Select the check box
By default, this option is not selected
RTP DSCP enable Select the check box
By default, this option is not selected

The OTC smartphone is created in the corresponding OpenTouch and associated to the
selected user. This OTC smartphone is displayed under the user in the tree structure of the
Users application
When the OTC smartphone is created and associated to a Conversation user, a configuration
file is automatically created on the OpenTouch server. It is copied in the OpenTouch in the
directory: /opt/Alcatel-Lucent/oamp/cms/DevicesDeployment/ICMMobile.
The configuration file is identified by a number specified at OTC smartphone creation. The
configuration file is named: MOBILE_<OpenTouch device identifier>@OpenTouch
FQDN.xml.
6.9.4 Granting the Conversation user right to off-site mobility
Note:
The off-site mobility license may have already been added while creating user and configuring its profile.
2. Expand the tree structure and select the Conversation user to which the remote extension
must be associated
The configuration window of rights for this user opens
!"# $ %& #'(

103/195
Chapter 6 +,
% *
/ %
0

Off site mobility Select the check box to allow the Conversation user to use the OTC
smartphone outside company premises (off-site)
6.10 Configuring the OTC smartphone for Connection users
6.10.1 Configuring the OmniPCX Enterprise for off-site mobility

The following paragraphs focus on the main parameters to configure on the OmniPCX
Enterprise for off-site mobility. They do not detail smartphone declaration and the association
of a smartphone to a Connection user (see: Configuring the smartphones on the OmniPCX
Enterprise and OpenTouch ).
6.10.1.1 Configuring the external callback translator
The External callback translator is used for incoming calls. It converts the number of the
external caller presented by the public carrier. The number to be translated is the exact
number that a user must dial to call back the caller. For more information, refer to the chapter
Numbering conversion of the OmniPCX Enterprise documentation called Public Networks
(reference: 8AL91005USxx).
From the OmniPCX Enterprise configuration window of OmniVista 8770:
1. Select: Translator > External numbering plan > Ext.Callback translation tables >
104/195 !"# $ %& #'(

+,
% * /
%
0
Ext.Callback translation rules

2. Access the contextual menu and select Create
Basic Number Enter area identifier, "DEF" for the default translator or "G".
Area identifier is the first digits of the number after preprocessing
Nb. Digits To Be Re- Enter the number of digits to be deleted from the start of the num-
moved ber received
Digits to add Enter the digits to be added at the beginning of the number
4. Click the validate icon to apply your modifications

6.10.1.2 Configuring DISA parameters
6.10.1.2.1 Declaring the DISA Trunk Group
An ISDN trunk group is necessary when the smartphone connects to the OmniPCX Enterprise
via the cellular network. This trunk group must allow DISA.
1. Select: Trunk Groups > Trunk Group
Trunk group ID Enter the trunk group number
Trunk Group used in Select: Yes (default value: No)
DISA
DISA Secret Code Leave this field empty

6.10.1.2.2 Declaring the DISA Prefix
This prefix is used when the smartphone performs an outgoing call or requires an OmniPCX
Enterprise service.
1. Select: Translator > Prefix Plan
Number Enter the prefix number. This number must be a DID number that
is compatible with the dialing plan
Prefix meaning Use the drop-down menu to select Remote Extension DISA

6.10.1.2.3 Configuring Automatic DISA substitution
For each call, the verification of the external calling party number must be first performed on
NDS then on NDI.
!"# $ %& #'(

105/195
Chapter 6 +,
% *
/ %
0

1. Select: System > Other System Param > DISA Parameters > Automatic DISA
Substitution Mode
Automatic DISA Substi- Use the drop-down menu and select With DID or Installation
tution Mode number
3. Click the validate icon to apply your modification
6.10.2 Configuring the smartphones on the OmniPCX Enterprise and

OpenTouch
Configuring a smartphone implies creating a smartphone in the OpenTouch server and a
remote extension device on the OmniPCX Enterprise, as shown in the following figure:
___change-begin___
___change-end___
6.10.2.1 Overview
The smartphone configuration for Connection users consists in:
1. Declaring virtual sets
2. Configuring the smartphone as remote extension on the OmniPCX Enterprise
3. Associating the remote extension to the Connection user on the OmniPCX Enterprise
4. Configuring the remote extension parameters
5. Configuring prefixes for the mobility solution
6. Creating and associating an OTC smartphone to Connection users
106/195 !"# $ %& #'(

+,
% * /
%
0
7. Associating the remote extension to the Connection user on OpenTouch

8. Granting the Connection user right to off-site mobility
9. Configuring parameters common to smartphones of a given type
6.10.2.2 Prerequisite and information required
The Connection user must be declared on the two systems (OmniPCX Enterprise and
OpenTouch) to benefit from OpenTouch services. For more information, refer to document [3].
Caution:
If Connection users have an analog set as main set, for the OpenTouch Conversation for
smartphone to work after login, you must change their set type to Analog with 4980 on the
OmniPCX Enterprise.
The parameters common to smartphones of this type must be verified in the OpenTouch
configuration window of OmniVista 8770 (see: Configuring parameters common to
smartphones of a given type ).
The fallback mode must be updated if needed.
To create a smartphone for a Connection user, you need the following information:
- The public directory number of the SIM card inserted in the smartphone (iPhone or
Android)
- The smartphone internal directory number, the number used to call the smartphone from
inside the enterprise. This number is the Connection user directory number.
- The external call prefix used to access the public network
Note:
Smartphone creation is simplified, as the smartphone IMEI is not necessary for configuration on the
OpenTouch. The smartphone is created in the OpenTouch server regardless of the smartphone type
(there is no hardware link between the device and the OpenTouch).
6.10.2.3 Declaring virtual sets

A virtual set (also called Ghost Z) is a configuration item required to set up a call from/to a
smartphone. To avoid congestion, one virtual set can be declared for each smartphone.
From the OmniPCX Enterprise configuration window of OmniVista 8770, perform the following:
1. Select: Users
2. Access the contextual menu, select Create
___change-begin___
!"# $ %& #'(

107/195
Chapter 6 +,
% *
/ %
0
___change-end___
Figure 6.14: Virtual set creation window example
3. In the General Characteristics tab, review/modify the following attributes:
Directory Number Enter the directory number of the virtual set. This number must be
compatible with the dialing plan. This number is never called
Set Type Select: ANALOG
4. In the Facilities tab, review/modify the following attributes:

Ghost Z Select the check box
Ghost Z Feature Use the drop-down menu to select Remote extension

6.10.2.4 Configuring the smartphone as remote extension on the OmniPCX Enterprise
This requires the configuration of the OmniPCX Integrated Cellular Client service (also called
Remote Extension). This service allows to configure smartphones as remote extensions on the
OmniPCX Enterprise. For more information, refer to the chapter OmniPCX Integrated
Cellular Client of the OmniPCX Enterprise documentation called Mobility (reference:
8AL91009USxx).
Important:
This operation automatically creates the remote extension on OpenTouch (listed in Devices
branch).
From the OmniPCX Enterprise configuration window of the OmniVista 8770, perform the
following:
108/195 !"# $ %& #'(

+,
% * /
%
0
1. Create the remote extension:

a. Select: Users
b. Access the contextual menu and select Create
___change-begin___
___change-end___
Figure 6.15: Remote extension creation window
c. Review/modify the following attributes:
Directory Number Enter the smartphone internal directory number (called remote ex-
tension internal number in the rest of this chapter)
Set Type Select: Remote Extension
d. Click the validate icon to apply your modifications

2. Modify the remote extension parameters:
a. Select: Users > <selected remote extension> > Remote extension
___change-begin___
!"# $ %& #'(

109/195
Chapter 6 +,
% *
/ %
0
___change-end___
Figure 6.16: Remote extension parameters configuration window
b. Review/modify the following attributes:
Remote extension Num- Enter the public number used to call the smartphone from inside
ber the enterprise, that is the external call prefix followed up by the
smartphone public directory number (called remote extension ex-
ternal number in the rest of this chapter)
Remote extension deac- If desired, select True to deactivate ringing on incoming calls on
tivation the smartphone
Default value: False
c. Click the validate icon to apply your modifications

3. If you want the smartphone to be identified automatically, the remote extension must be
listed in the speed dialing table as follows:
a. Select Speed Dialing > Direct Speed Dialing Numbers > Direct SpdDl No. Pref.
b. Access the contextual menu and select Create
___change-begin___
110/195 !"# $ %& #'(

+,
% * /
%
0
___change-end___
Figure 6.17: Direct speed dialing number configuration window example
Direct Speed Dialing No Enter the speed dialing number. This number must be compatible
Prefix with the dialing plan. This number is never called
Note:
The number can start with a letter followed by the internal number of the
remote extension (for example: A26000).
Call Number Enter the remote extension external number (external call prefix
followed by the smartphone public number)
External DISA Dir.No Enter the remote extension internal number

6.10.2.5 Associating the remote extension to the Connection user on the OmniPCX
Enterprise
This operation requires the configuration of the Twin Sets feature. This feature associates the
remote extension (that is the smartphone) to a Connection user who is already the user of a
deskphone related to the OmniPCX Enterprise. By grouping them under a single directory
number (which is the Connection user main set), they form a tandem. For more information,
refer to the chapter Twin Sets of the OmniPCX Enterprise documentation called User
Services (reference: 8AL91003USxx).
From the OmniPCX Enterprise configuration window of the OmniVista 8770, perform the
!"# $ %& #'(

111/195
Chapter 6 +,
% *
/ %
0
following:
1. Assign two lines to the remote extension:
Caution:
The two devices (twin sets) must be configured as multiline sets. The Connection user
deskphone must be created as multiline set before this configuration.
a. Select: Users > <selected remote extension> > Progr.Keys
b. Select a key not already assigned (generally Key No. 1 and 2)
___change-begin___
___change-end___
Figure 6.18: Multiline configuration window example
Function Use the drop-down menu and select: Multi-line
Directory Number Enter the remote extension internal number

e. Repeat this operation to configure the second multiline key
2. Associate the remote extension to the Connection user:
a. Select: Users
b. Select the corresponding Connection user
c. Select the Assoc.Sets tab in the properties area
___change-begin___
112/195 !"# $ %& #'(

+,
% * /
%
0
___change-end___
Figure 6.19: Remote extension association window example
d. Review/modify the following attributes from the main set of the Connection user:
Tandem
Tandem Directory Num- Enter the remote extension internal number
ber
Main set in the tandem Select the check box
By default, the check box is cleared.
e. Click the validate icon to apply your modifications

6.10.2.6 Configuring the remote extension parameters
A set of parameters can be defined and applied to all smartphones when they are configured
as remote extensions. To configure these parameters:
1. Select: Applications > Remote extension parameters
___change-begin___
!"# $ %& #'(

113/195
Chapter 6 +,
% *
/ %
0
___change-end___
Figure 6.20: Remote extension parameter configuration window example
Key features Select a function for Function key 1:
• Not Assigned: free key
• Consultation: activates the Consultation Call feature
• Broker: activates the Broker Call feature
• Three-Party Conference: activates the Three-Party Confer-
ence feature
• Transfer: activates the Transfer feature
• MPK Activation: activates programmable keys
• Soft release: activates the Soft release feature
2 to 9, 0, * and # Same as for key 1.
Escape sequence Enter the escape sequence to be used. This sequence can be ac-
tivated while on a call to confirm function key activation
Caution:
See note below.
114/195 !"# $ %& #'(

+,
% * /
%
0
CLI Format Select the Calling Line Identity (CLI) presentation format on the
external Cellular Client.
• Standard Plan: as for a public subscriber
• Private Plan: as for an internal user
• Subaddress: DISA number + * + internal number
For a supervision call, the Cellular Client set display will show:
• Standard Plan: DID number of the set supervised in a call
• Private Plan: number of the programmable key corresponding
to the set supervised in a call. For example, *XX*, where XX is
key number
• Subaddress: DISA number + *XX*, where XX is the number
of the programmable key corresponding to the set being su-
pervised in a call
Redirecting IE number Set the value to:
available • Yes in order to send the External Cellular Client number in the
Redirecting IE number available when the call is ISDN
• No in order not to send the Redirecting IE number available

Note:
The escape sequence must be compatible with the dialing plan. Although the escape sequence is not
analyzed by the translator, there can be some confusions. If a prefix or a number uses the same digits as
the escape sequence, the escape sequence may inadvertently start a call.
You must:
1. Select an escape sequence that is compatible with the dialing plan.
2. Create a speed dialing number (for example) corresponding to the same sequence. This number,
which will never be used, avoids the possibility of any later configurations creating a number identical
to the escape sequence.
6.10.2.7 Configuring prefixes for the mobility solution
Ringing deactivation on the remote extension is enabled by dialing a prefix (one to deactivate
and the other to activate). This prefix must be created in the OmniPCX Enterprise.
1. Select: Translator > Prefix plan
Number Enter the prefix number. This number must be a DID number that
is compatible with the dialing plan.
Prefix meaning Use the drop-down menu to select Set features.
Station Features Use the drop-down menu to select Remote extension Deactiva-
tion.

Repeat the above operation to create the prefix to activate ringing on incoming calls on the
remote extension. In the Station Features field, select the Remote Extension Activation
!"# $ %& #'(

115/195
Chapter 6 +,
% *
/ %
0
option.
6.10.2.8 Creating and associating an OTC smartphone to Connection users
To avoid synchronization issues, use the Users application of the OmniVista 8770 to create
and associate OTC smartphone to users. Only the procedure from the Users application is
presented here.
Important:
If Connection users have an OTC smartphone application already declared on the OpenTouch
with either the type Any Mobile (if running on iPhone) or MIC Android (if running on Android
smartphone), you must:
1. Disassociate and delete the applications
2. Recreate and associate the applications to users, with the model OTC Smartphone and the
appropriate type: iPhone or Android
To create and associate an OTC smartphone to a Connection user in one go:
1. From the Users window of OmniVista 8770, click the Users tab
2. Expand the tree structure and select the Connection user to whom the OTC smartphone
must be associated
OTC Smartphone option
___change-begin___
___change-end___
Figure 6.21: OTC smartphone creation and association window example
4. Review/modify the following fields in the General tab:
116/195 !"# $ %& #'(

+,
% * /
%
0
Device identity This field is automatically completed after OTC smartphone cre-
ation. It displays the OTC smartphone internal identifier as follows:
MOBILE_<number>
Device number Enter the directory number for the OTC smartphone
Type of mobile According to your device model, use the drop-down list to select
either iPhone (by default) or Android
GSM number Enter the GSM number of the smartphone on which the OTC
smartphone runs.
The canonical format is: country code + external call prefix + pub-
lic directory number (for example: +33 (0) 6 12 34 56)

The OTC smartphone is created in the corresponding OpenTouch and associated to the
selected user. This OTC smartphone is displayed under the user in the tree structure of
Users.
When the OTC smartphone is created and associated to a Connection user, a configuration
file is automatically created on the OpenTouch server. It is copied in the OpenTouch in the
directory: /opt/Alcatel-Lucent/oamp/cms/DevicesDeployment/ICMMobile.
The configuration file is identified by a number specified at OTC smartphone creation. It is
named: MOBILE_<OpenTouch device identifier>@OpenTouch FQDN.xml.
6.10.2.9 Associating the remote extension to the Connection user on OpenTouch
The remote extension must also be associated to the Connection users on the OpenTouch
server:
1. From the Users window of the OmniVista 8770, click the Users tab
2. Expand the tree structure and select the Connection user to whom the remote extension
must be associated
3. In the properties area, select the OT configuration tab, then select the Device tab
___change-begin___
!"# $ %& #'(

117/195
Chapter 6 +,
% *
/ %
0
___change-end___
Figure 6.22: Connection user device configuration window example
4. In the Devices parameter, double click and use the contextual menu to select Add a value
A new line is added to the Devices parameter.
5. Use the browser to select the remote extension for this Connection user
The remote extension identified by its device number is added to the Devices parameter.
6. Click the validate icon to apply your modification
6.10.2.10 Granting the Connection user right to off-site mobility
From the OpenTouch configuration window of OmniVista 8770, perform the following:
1. From the Users window of the OmniVista 8770, click the Users tab.
2. Select the corresponding Connection user
___change-begin___
118/195 !"# $ %& #'(

+,
% * /
%
0
___change-end___
Off site mobility Select the check box to allow the user to use a smartphone outside
the enterprise (off-site)

6.10.2.11 Configuring parameters common to smartphones of a given type
The OpenTouch server provides a set of parameters that can be applied to the OTC
smartphone application running on smartphones associated to Connection users. There is a
set of parameters common to each type of smartphone supported by the OpenTouch. Each
set of parameters can be verified and modified from the OpenTouch configuration window.
This set of parameters is stored in a common configuration file (*.xml format) downloaded by
the OTC smartphone after logon (see: Launching the OTC smartphone ).
From the OpenTouch configuration window of the OmniVista 8770:
1. Select: System Services > Applications > Device management > Common
configuration
2. Select the desired smartphone type: iPhoneCommon or AndroidCommon
This provides access to the parameters that can be applied to the OTC smartphone
application running on the selected type of smartphone
___change-begin___
!"# $ %& #'(

119/195
Chapter 6 +,
% *
/ %
0
___change-end___
Figure 6.24: OpenTouch Connection for smartphone application parameter example for iPhone
3. In the properties area, select the Telephony settings tab and review/modify the following
attributes:
Private plan size Enter the local plan size +1
Country code Enter the national code of the smartphone users country (for ex-
ample: +33 is the French national code)
International prefix Enter the international access prefix (for example: 00)
National prefix Enter the outgoing trunk group seize prefix (for example: 0)
Emergency numbers Enter the emergency numbers
4. Select the Data and application settings tab and review/modify the following attributes:
URL private for ICS Enter the private URL of the OpenTouch server
Public URL for ICS Enter the public URL of the OpenTouch server. This URL is
used when the smartphone is outside company premises
(off-site)
Authorize credentials stor- Select: True (right to save the password locally)
age in mobile
Application refresh timer Enter 3600
ICS eventing chunk timeout Enter 3600
120/195 !"# $ %& #'(

+,
% * /
%
0
ICS event chunk port Enter 8016 (mandatory)

Caution:
The value set by default may be incorrect. Verify and correct it if
necessary.

Verify that the following OmniPCX Enterprise parameters are correctly synchronized with the
OpenTouch server and displayed in the OpenTouch configuration window of the OmniVista
8770:
1. From the OpenTouch configuration window, navigate to: System Services > Topology >
OXE CS > OXE CS network > OXE CS subnetwork > OXE CS
___change-begin___
___change-end___
Figure 6.25: Telephony settings configuration page example
2. Select the Telephony settings tab and verify that the following fields are filled with the
values listed: Configuring the OmniPCX Enterprise for off-site mobility :
• Remote extension activation
• Remote extension deactivation
• Immediate forward
• Forward cancellation
• Remote extension DISA public number
6.10.3 Configuring the OTC smartphone for Connection users without

deskphone
!"# $ %& #'(

121/195
Chapter 6 +,
% *
/ %
0
This paragraph provides the OTC smartphone configuration for Connection users without
deskphone. Two configurations can be used:
- Connection users with smartphone in standalone mode
- Connection users with smartphone and PC (SIP extension)
6.10.3.1 Connection users with smartphone in standalone mode
6.10.3.1.1 SIP extension configuration
___change-begin___
___change-end___
Incoming calls: handled in smartphone through REX
Outgoing calls: handled in 3PCC mode from smartphone
Routing rules: smartphone only, forward
Routing profiles displayed on smartphone: personal computer and mobile, personal

computer
Route my call to displayed on smartphone (call forwarding): voice mail, user, number
SIP extension creation is performed on the OmniPCX Enterprise, without associated device.
This means that the OmniPCX Enterprise routes incoming calls to the smartphone. The PCX
option Forward if set is out of service (access path: Classes of service > Phone Features
COS) must be validated to have permanent call routing to the smartphone. In case of twin sets
(tandem), the PCX option Overflw to sec tandem if main OOS must be validated (access
path: System > Other System param. > System Parameters).
Note:
In PCX configuration, the option
Personal computer is displayed even when personal computer session is not open.
6.10.3.1.2 UA set configuration
___change-begin___
122/195 !"# $ %& #'(

+,
% * /
%
0
___change-end___
Incoming calls: handled in smartphone through REX
Outgoing call: handled in 3PCC mode from smartphone
Routing rules: smartphone only, forward
Routing profiles displayed on smartphone: deskphone, deskphone & mobile, other & mobile
For exemple, this configuration can be used with IPDSP.

Restriction: Wrong behavior has been noticed on routing rules.
Note:
In this configuration, the UA set is never put into service.
6.10.3.2 Connection users with smartphone and PC (SIP extension)

___change-begin___
___change-end___
Incoming calls: handled in smartphone through REX, and VoIP on OTCT PC application
Outgoing call: handled in 3PCC mode from smartphone, or from PC
!"# $ %& #'(

123/195
Chapter 6 +,
% *
/ %
0
Routing rules: PC only, PC + smartphone, smartphone only (PC off), forward
Routing profiles displayed on smartphone: personal computer and mobile, personal

computer
Routing profiles displayed on PC: personal computer
Route my call to displayed on PC: voice mail, forward to (*)
Routing profiles on smartphone and PC are not the same, and the display differs on the two
devices.
Overflow option Forward if set is out of service (access path: Classes of service > Phone
Features COS) must be validated to have permanent call routing to smartphone. In case of
twin sets (tandem), the PCX option Overflw to sec tandem if main OOS must be validated
(access path: System > Other System param. > System Parameters).
Nomadic cannot be used in this configuration.
Desk sharing is not compliant with this topology.
(*): Forward to Home, Colleague, and Personal mobile are visible when they have been
declared by the Connection user in the OTC smartphone application (that is phone numbers
configuration), or through My Profile web interface.
6.10.3.3 Overview and conclusion
CSTA and ser- OmniVista 8770 Routing (rules Conclusion

vices and DM consistency)
Smartphone Ok Ok (Users applic- Deskphone rout-
Standalone ation) ing rule useless
UA set
No consistent on
routing rules, but
can be combined
with IPDSP
Smartphone Ok Ok (Users applic- Ok
Standalone ation)
SIP extension
PCX SIP exten-
sion resource not
used, but ready to
a configuration
with PC
Smartphone and Ok Ok (Users applic- Ok
PC ation)
SIP extension

OTC smartphone. The network elements to consider are:
124/195 !"# $ %& #'(

+,
% * /
%
0
- For Connection users:

• The firewall protecting the intranet (company LAN)
• The DNS servers (internet and intranet), used to resolve the FQDNs of the network
elements
• The reverse proxy, used to control data flows (web services and device management)
between the OTC smartphone and OpenTouch server
- For Conversation users:
• The firewall protecting the intranet (company LAN)
• The DNS servers (internet and intranet), used to resolve the FQDNs of the network
elements
• The reverse proxy, used to control data flows (web services and device management)
between the OTC smartphone and OpenTouch server
• The OpenTouch Session Border Controller (OTSBC), used to control VoIP
communications between the OTC smartphone and OpenTouch server
• For OTC iPhone only: the OpenTouch Edge Server (OTES) if provided by the
OpenTouch solution (optional component). In this case, it is used to control data flows
between the OTC iPhone and OpenTouch server
6.12 Installing the OTC smartphone application on smartphones
6.12.1 OTC Android Smartphone context

6.12.1.1 Overview
The OTC Android Smartphone must be downloaded and installed on the Android smartphone
using the Google Play Store.
The OTC Android Smartphone must be present in the Play Store of Google.
The Android smartphone must work normally and be connected to the internet via the cellular
network.
6.12.1.3 Installing the application from the Android smartphone
1. From the Android home screen, select the Play store icon if placed as a shortcut on the
home screen, or access the Applications screen and select the corresponding icon
2. From the Play Store, search for the OTC Android Smartphone with keywords, for example:
3. Follow the instructions on screen to download the OTC Android Smartphone
When download is finished, the Android automatically installs the OTC Android
Smartphone. After installation, the OpenTouch icon ( ) is displayed in the Applications
page of Android smartphone
4. To place the OTC Android Smartphone on the home screen, long press the application
icon (click and hold) and move it to place a shortcut on the home screen
!"# $ %& #'(

125/195
Chapter 6 +,
% *
/ %
0
6.12.2 OTC iPhone context

6.12.2.1 Overview
The OTC iPhone must be downloaded and installed on the iPhone device using the App Store
(via a computer or directly from the iPhone).
The OTC iPhone must be present in the App Store for Apple products.
The iPhone must work normally and be connected to the internet via the cellular network.
6.12.2.3 Installing directly the application from the iPhone
1. From the iPhone home page, select the App Store icon to access the App Store
2. From the App Store, search for the OTC iPhone with keywords, for example:
3. Follow the instructions on screen to download the OTC iPhone
When download is finished, the iPhone automatically installs the OTC iPhone. After
installation, the OpenTouch icon ( ) is displayed in the iPhone home page
6.12.2.4 Installing the application on the iPhone via a computer

1. Connect the iPhone to the computer via a USB cable
2. From the computer, launch the iTunes software and select the iTunes Store menu
available in the left part of the iTunes home page
3. From the iTunes Store home page, select the AppStore icon to access the App Store
4. From the App Store, search for the OTC iPhone with keywords, for example:
5. Follow the instructions on screen to download the OTC iPhone on iTunes
6. From the iTunes home page, select the iPhone from the Devices menu, then select the
Applications tab
7. To download the OTC iPhone on the iPhone, launch a synchronization by selecting the
application and pressing the Sync button
When download is finished, the iPhone automatically installs the OTC iPhone. After
installation, the OpenTouch icon ( ) is displayed in the iPhone home page
6.13 Generating a QR code for OTC smartphone first startup

A QR code (or Quick Response code) can be used to provide easy access to the OTC
smartphone at first startup.
At first startup, the OTC smartphone enables to use a QR code to avoid entering, for example,
the public and private FQDNs of the OpenTouch server. This requires to generate previously a
QR code including information such as:
126/195 !"# $ %& #'(

+,
% * /
%
0
<otcInfos>
<privateUrl>Private FQDN of the server</privateUrl>
<publicUrl>Public FQDN of the serveur</publicUrl>
<login>user login</login>
<RpLogin>Reverse Proxy login</RpLogin>
</otcInfos>
Example:
<otcInfos>
<privateUrl>private.mydomain.local</privateUrl>
<publicUrl>public.mydomain.com</publicUrl>
<login>my_login</login>
<RpLogin>my_rp_login</RpLogin>
</otcInfos>
There are online tools that can be used to generate the QR code.
The result is a figure similar to a bar code that can be either published or broadcast.
Note:
All fields are optional.
6.14 Importing the certificate used to connect to the reverse proxy

Two client authentication rules are available to connect to the reverse proxy: by
login/password or certificate.
In some installations, for security reason, the user login/password is not sufficient. A solution to
increase security is that the reverse proxy authenticates the user by certificate. This solution
only applies to the Conversation or Connection users logged in to an OTC smartphone.
The user authentication by certificate requires to install the certificate on the OTC smartphone
(trusted root certification store). The certificate can be imported on the smartphone using any
of the following solutions:
- Import certificate using iTunes (only for OTC iPhone):
1. Connect the iPhone to a computer on which iTunes is installed
2. From iTunes, copy the certificate from the computer to the iOS application (the file
extension must be either p12 or pfx). For more information, see:
http://support.apple.com/fr-fr/HT201301
3. From the iPhone, launch the OTC iPhone and click the Import a certificate button
(see: Launching the OTC smartphone )
A window opens with the list of all available p12 and pfx files
4. Select the certificate
PKCS12 certificates
- Import certificate using e-mail:
1. From the smartphone, access the e-mail application
2. Open the e-mail including the certificate (the file extension must be otcert)
3. Click the certificate
!"# $ %& #'(

127/195
Chapter 6 +,
% *
/ %
0
A windows opens with the applications able to handle the certificate

4. Select the OTC smartphone
PKCS12 certificates
6.15 Launching the OTC smartphone

Once the OTC smartphone is installed on the smartphone, proceed as follows:
1. From the smartphone home page, click the OpenTouch icon
A login page opens
___change-begin___
___change-end___
Figure 6.29: Login page example
128/195 !"# $ %& #'(

+,
% * /
%
0
2. At first startup, you are prompted to provide access parameters to OTC smartphone
configured (see: Generating a QR code for OTC smartphone first startup )
• Manually: You are prompted to enter:
• The public and private FQDNs of the OpenTouch server
• The user credentials to access the application (login and password)
• QR code: Click the Scan QR Code button (OTC Android Smartphone) or press the
icon at the top right part of the screen (OTC iPhone)
3. For Conversation users logged in to an OTC iPhone: If the reverse proxy authenticates
users by certificate, it is required to install the certificate in the application. One solution is
to press the Import a certificate button. For more information, refer to: Importing the
certificate used to connect to the reverse proxy
4. Click the Connect button to access the OpenTouch server and open the OTC smartphone
Note:
According to configuration, you may be invited to validate the reverse proxy certificate.
The login page is displayed when the user credentials expire. When this occurs, the user is
prompted to enter new credentials.
6.16 Displaying the type of user logged in

After launching the application, you can verify your status (Conversation or Connection), by
using the About menu of the application. This menu also provides the current software version
of the application and its name.
Proceed as follows:
1. From the current page, press any of the following: OpenTouch icon, user picture or name
at the top part of the home page
The user profile page opens
2. Select About to access user and application information
___change-begin___
!"# $ %& #'(

129/195
Chapter 6 +,
% *
/ %
0
___change-end___
Figure 6.30: User and application information example
6.17 Modifying the connection parameters to the OpenTouch server

Connection parameters to the OpenTouch server can be modified from the user profile page,
as follows:
1. From the OTC Android Smartphone current page, press any of the following: OpenTouch
icon, user picture, or name at the top part of the home page
___change-begin___
130/195 !"# $ %& #'(

+,
% * /
%
0
___change-end___
Figure 6.31: User profile page example
2. Go to: Settings > Connections
The Connections page opens
___change-begin___
!"# $ %& #'(

131/195
Chapter 6 +,
% *
/ %
0
___change-end___
Figure 6.32: Connection page example
3. Modify the public and/or private FQDNs of the OpenTouch server according to your needs
4. Relaunch the OTC Android Smartphone with the modified parameters

At initial startup, connection parameters to the OpenTouch server can be modified using the
Sign out button, as follows:
1. From the OTC iPhone home screen, press the user picture or name at the top part of the
home page
___change-begin___
132/195 !"# $ %& #'(

+,
% * /
%
0
___change-end___
Figure 6.33: User profile page example
2. Press the Sign out button to log out and exit the application
The login page opens
___change-begin___
!"# $ %& #'(

133/195
Chapter 6 +,
% *
/ %
0
___change-end___
Figure 6.34: Login page example
3. Modify the public and/or private FQDNs of the OpenTouch server according to your needs
Note:
If the public FQDN of the OpenTouch server changes, the certificate is automatically cleared.
4. Click the Connect button to launch the OTC iPhone with the modified parameters
6.18 Uninstalling the OTC smartphone

To uninstall the OTC Android Smartphone from an Android smartphone:
1. From the Android smartphone home page, go to Settings > Apps
2. In the applications listed, search and press the OpenTouch icon ( )
A page opens with detailed information about the application
3. Click Uninstall
The OpenTouch icon is removed from the smartphone home page

To uninstall the OTC iPhone from an iPhone:
1.
134/195 !"# $ %& #'(

+,
% * /
%
0
) until all icons on the page start wiggling

A cross icon appears in the upper left hand corner of the OpenTouch icon
2. Press the cross icon
A confirmation dialog box opens
3. Click Delete
The OpenTouch icon is removed from the smartphone home page
6.19 Accessing logs
6.19.1 Overview
OTC smartphone provides applicative logs. These log messages can be retrieved from the
application itself (see: Accessing logs using the application ).
A SysLog server can also be used to retrieve OTC iPhone log files (see: Accessing logs using
a SysLog server ). This solution does not apply to OpenTouch Conversation for Android
smartphone.
6.19.2 Accessing logs using the application

6.19.2.1 OTC Android Smartphone context
The OTC Android Smartphone enables to send log files by e-mail. The e-mail address must be
declared in the OT user profile associated to the user of OTC Android Smartphone.
1. From the OTC Android Smartphone current page, press the OpenTouch icon ( ) or the
user picture or name at the top part of the home page
2. Select Settings > Advanced settings
The Advanced settings page opens
3. According to your needs, press the Logging level option and select the type of log
messages to send (Error option is selected by default)
4. Press the Send log by email option to send log messages by e-mail
6.19.2.2 OTC iPhone context
The OTC smartphone enables to send log files by e-mail. The e-mail address must be
declared in the OT user profile associated to the user of OTC iPhone.
1. From the OTC iPhone home page, press the user picture or name at the top part of the
home page
2. Select Settings > Send log to send log messages by e-mail
6.19.3 Accessing logs using a SysLog server
Note:
The SysLog server is only supported for OTC iPhone.
!"# $ %& #'(

135/195
Chapter 6 +,
% *
/ %
0
To retrieve log files of OTC iPhone from a SysLog server:

1. Install a SysLog server on the desired machine
2. Declare the SysLog server on the OpenTouch server:
a. From the OpenTouch configuration window of the OmniVista 8770, select: Eco
system > IT Server
b. Access the contextual menu and select Create > Syslog Server
___change-begin___
___change-end___
Figure 6.35: Server creation window example
c. In the General tab, review/modify the following attributes:
Display name Enter the Syslog server display name
FQDN Enter the FQDN of the Syslog server

The Syslog server is created in the server list
3. Declare the SysLog server in the OTC iPhone parameters:
a. From the Users configuration window of the OmniVista 8770, click the Users tab
b. Expand the tree structure and select the corresponding OTC iPhone
___change-begin___
136/195 !"# $ %& #'(

+,
% * /
%
0
___change-end___
Figure 6.36: OTC iPhone configuration window example
c. In the General tab, review/modify the following attribute:
Syslog Server Use the drop-down menu to select the Syslog server
d. Click the validate icon to apply your modification

4. If a session is opened, stop the OTC iPhone and relaunch it (see: Launching the OTC
smartphone )
6.20 Generating a QR code or NFC tag for call routing and

switching
From their OTC Android Smartphone, Conversation and Connection users can read a QR
code or NFC tag to:
- Modify their current call routing profile, including route incoming calls to an internal device
declared on the OpenTouch or OmniPCX Enterprise
This can only be performed when the OTC Android Smartphone is idle (no communication
in progress).
- Switch an active call to an internal device declared on the OpenTouch or OmniPCX
Enterprise
These actions require the previous generation of a QR code or NFC tag with the internal
!"# $ %& #'(

137/195
Chapter 6 +,
% *
/ %
0
device settings.
Note:
This is not available for OTC iPhone.
6.20.1 Generating a QR code

Online tools can be used to generate the QR code.
The syntax of information to be entered in the QR code differs:
- If the internal device is associated to an OpenTouch user.
The syntax must be: {"v":"1","DI":{"DiD":{"Int": "xxxxx",
"User":"xxxxx"}}}, where:
• "Int" refers to the device number (81276737 in the example below)
This field is used when the internal device and OTC Android Smartphone are declared
on the same node: the OTC Android Smartphone uses the device number as
destination for call routing or switching.
• "User" refers to the directory number of the OpenTouch user to whom the device is
associated (21876737 in the example below)
This field is used when the internal device and OTC Android Smartphone are declared
on two different nodes: the OTC Android Smartphone uses the user directory number
as destination for call routing and switching.
Example 1:
{"v":"1","DI":{"DiD":{"Int": "81276737", "User":"21876737"}}}
- If the internal device is associated to a Connection user, or is only an OmniPCX Enterprise
device (without OpenTouch features), the syntax must be:
{"v":"1","DI":{"DiD":{"User":"xxxxx"}}}. In this configuration, "User" refers
either to the user directory number (for OmniPCX Enterprise devices only), or the device
number (for devices associated to Connection users).
Example 2:
{"v":"1","DI":{"DiD":{"User":"21876737"}}}
The result is a figure similar to a bar code that can be either printed or broadcast.
6.20.2 Generating a NFC tag

The NFC tag must be generated using ALE NFC Extended OXE Mobility.
NFC tag generation consists in entering the internal device settings in the NFC Extended OXE
Mobility application:
- If the internal device is associated to an OpenTouch user, select the OT Device tab and
complete the following fields:
• User number: refers to the directory number of the OpenTouch user to whom the
device is associated. It is used when the internal device and OTC Android Smartphone
are declared on two different nodes. In this case, OTC Android Smartphone uses the
user directory number as destination for call routing and switching.
• Device number: refers to the device number used when the internal device and OTC
Android Smartphone are declared on the same node. In this case, OTC Android
Smartphone uses the device number as destination for call routing or switching.
- If the internal device is associated to a Connection user, select the OT Device tab and
138/195 !"# $ %& #'(

+,
% * /
%
0
complete the User number with the device number.

- If the internal device is an OmniPCX Enterprise device (without OpenTouch features),
select the OXE Device tab and complete the Local number of the set with the user
directory number.
The internal device settings must be then recorded on NFC tags.
For more information on NFC tag generation, refer to document [34].
!"# $ %& #'(

139/195

!
7.1 Overview
The OTC Web client is an application that enables anonymous users to join an OpenTouch
conference using a browser. An anonymous user is a person who is foreign to or not logged-in
to the host OpenTouch system. An anonymous user can be internal or external to the
company.
Conference scheduling cannot be done from the OTC Web. It must be performed from another
OpenTouch client or from the OpenTouch Outlook Scheduling add-in.
Access to the OTC Web is available by a URL, reachable from standard industry internet
browsers (see: List of supported operating systems and browsers ). A guest can join a
conference directly via this URL, or via OpenTouch Conversation or the Join Meeting button
in Outlook. Guests join as leader or participant, according to the rights granted by the owner of
the conference. According to the way used to connect to the conference (directly via URL or
via a client), a guest may have to enter a leader code to gain leader privileges. Leaders can
use all of the OpenTouch features and applicabilities whereas participants can use a limited
set of capabilities. For more information, refer to the document [7].
The conference owner invites leaders and participants when scheduling the meeting.
Conferences can include telephone communications (participants (and conference leaders)
can be called on their telephone set) or be limited to a web presentation, for some, or all
participants. In any case, conferences include access to shared documents and an instant
messaging interface.
As of OpenTouch R2.1.1, the OTC Web can detect if the browser used to join an OpenTouch
conference implements Web Real-Time Communication (WebRTC) capabilities. WebRTC
offers real-time communications from web browsers without using additional plug-ins. In the
case of OTC Web, WebRTC enables web browsers to handle OpenTouch conferences,
provided that:
- An OpenTouch Session Border Controller (OTSBC) is placed in the secured network
infrastructure. For communications via WebRTC, sessions are established through SIP
over WebSockets signaling and communications are encrypted through DTLS-SRTP.
OTSBC is used to control these communications through SIP over WebSockets signaling
and DTLS-SRTP flows.
- Guests join the OpenTouch conference from the Internet (access from LAN is not
supported for WebRTC). Once the URL for the conference entered in the web browser, the
access page of OTC Web provides an option enabling the guests to join the audio
conference via their web browser. If WebRTC is not supported by the browser, this option
is hidden in the access page of OTC Web.
- Internal or external microphone and speakers are available on guest devices. If not, the
option to join the audio conference through the web browser is hidden (no WebRTC use).
The volume of speakers and microphone are managed in the Operating System sound
parameters.
According to your internet browser capabilities, audio conferences can be performed using
either narrowband audio (G.711) or wideband audio (G.722). Video conferences are not
supported on OpenTouch 2.1.1.
140/195 !"# $ %& #'(

+,
% * 1&
The OTC Web offers:

- Dial-in and dial-out audio conferencing
- Web presentations: .pdf, .jpg, .png, .gif, and Microsoft Office file formats when the
Document Converter Software (DCS) is installed
- Attachment of files
- Multi-party chat
- Desktop sharing (scheduled conference only)
Desktop sharing is only available for conference leaders, provided they have installed the
OTCSharing plug-in on their device. This plug-in can only be installed on Windows
operating systems (not supported on MAC OS X and tablets).
Conference participants can view, but not modify the shared view.
Conference participants are attendees or conference leaders, their role is determined by the
URL they use to access the conference.
Although the login page looks identical, leaders and participants do not have the same rights:
Feature Specific rights Conference leader Conference parti-
cipants
Conference Schedule, start and Yes No
close
Invite a participant by
mail or telephone
Drop a participant
Join Yes Yes
Select an avatar
Upload an image to rep-
resent self
Take picture from web-
cam and display as
avatar
Multi-party chat Start a chat with another Yes Yes
participant
Attachment Attach and remove files Yes No
to the conference
Download files from the Yes Yes
conference
Dial out and dial in Mute/Unmute another Yes No
audio conferencing participant or leader
Mute/Unmute all parti-
cipants (giving a lecture)
Place a phone call
Show active speaker Yes Yes
Mute/Unmute self
Drop audio session
!"# $ %& #'(

141/195
Chapter 7 +,
% * 1&
Feature Specific rights Conference leader Conference parti-

cipants
Web presentation View a web presentation Yes Yes
Start/stop and navigate Yes No
on a web presentation
Switch between web
presentations
Prevent other leaders'
operations on the web
presentation
Grant control of the
presentation to another
leader
Participant control Promote a participant to Yes No
leader
Drop participant's audio
Drop participant

Once the URL for the conference is entered in the web browser, the access page (identical for
conference leader and conference participants) is displayed.
When the user joins a conference bridge, the OTC Web verifies that all parameters used to
support audio in the browser are met (internet access, OTSBC topology, browser capability)
and if enabled, adds the Call me on my computer option in the access page.
___change-begin___
142/195 !"# $ %& #'(

+,
% * 1&
___change-end___
Figure 7.1: Join page example (WebRTC not supported)
___change-begin___
!"# $ %& #'(

143/195
Chapter 7 +,
% * 1&
___change-end___
Figure 7.2: Join page example (WebRTC supported)
Enter your name, select a picture or avatar (optional), request to be called on the phone
(optional), and click Join.
When WebRTC is used:
- The conference service initiates an audio call on the browser, and a window prompts to
accept the audio call. Click Accept.
- The browser also prompts to confirm the use of a microphone on your computer. Click
Allow.
Once the audio call is established, the OTC Web automatically opens a dialing keypad
- Press the # button to enter in the conference
If call establishment fails (network connection loss, network quality, or configuration
issues), either transfer the call on a third party device using the phone icon on top of the
screen, or try again by reloading the conference web page.
The OTC Web conference window is displayed.
___change-begin___
144/195 !"# $ %& #'(

+,
% * 1&
___change-end___
Figure 7.3: OTC Web interface example
The following table displays annotation and screen display tools:
Icon Select, to:
Use any of: pen, eraser, highlighting pen, ruler
Change text color
Change font appearance
Switch to a mode adapted to the width of the screen
Switch from an HD resolution to a lower resolution
Switch to full screen
7.4 Topologies
!"# $ %& #'(

145/195
Chapter 7 +,
% * 1&
Within company premises, the OTC Web connects to the OpenTouch through the company
intranet network (LAN) for voice media and data transmission.
___change-begin___
___change-end___
7.4.2 Off site topology (remote users)

Outside of the company premises, for security reasons, OTC Web users access the
conference via an OpenTouch Edge Server (OTES).
___change-begin___
___change-end___
Figure 7.5: Off site topology
An OpenTouch Session Border Controller (OTSBC) is required when conferencing access is
performed via WebRTC.
___change-begin___
146/195 !"# $ %& #'(

+,
% * 1&
___change-end___
Figure 7.6: Off site topology for conferencing access via WebRTC
To configure the OTES and OTSBC, refer to: OpenTouch Clients (Mobile and Desktop) -
7.5 Application deployment and configuration

Plug-in installation is required when conference leaders wish to share their computer desktop
on the OTC Web. You can download this sharing plug-in, called OTCSharing.msi, from:
- The diagnostic button of the OTC Web access page
This button opens a window verifying that the sharing plug-in is installed on the computer,
and offering to download it, if needed.
- The sharing area, after joining a conference with the leader role
The sharing plug-in must be installed and started on the computer. If using Chrome or Firefox,
close your browser to complete installation with a certificate (required to secure
communications when sharing your desktop). If using Microsoft Internet Explorer, the
certificate is accepted without restart.
IT managers must be informed that:
- Guests must have administrator rights to install the sharing application
- The sharing application is installed as a service and is automatically started (auto start
mode activated at Windows login)
- The Microsoft Visual C++ 2010 runtime must be installed
- Uninstallation must be manual, and can be performed from:
• The Control panel (Add/remove programs interface)
• The menu Start > Programs > ALE International (taskbar of the Windows home
page)
From the OpenTouch server, there is only to verify that the web client used for the conference
is the OTC Web:
1. Access the administration console for the collaboration server as follows:
a. Open a session on the OmniVista 8770
b. Start the Configuration application and select the corresponding OpenTouch server
c. Right click and select WBM
d. Enter the otAdmin credentials
!"# $ %& #'(

147/195
Chapter 7 +,
% * 1&
e. Navigate to Users and devices > Conference server

The administration console is displayed
2. Navigate to: Configuration > System Options
3. Verify OTCWeb is selected as default web client
Figure 7.7: Selecting the default web client example
7.6 WebRTC configuration

If WebRTC is supported by the browser and used for audio conferencing with the OTC Web,
configure the WebRTC on the OpenTouch, OTES , and OTSBC.
7.6.1 WebRTC configuration on OpenTouch

On the OpenTouch server, declare the OTSBC used for conferencing access via WebRTC
(see: OpenTouch Clients (Mobile and Desktop) - Implementing OpenTouch Ecosystem -
Declaring the OTSBC for conferencing access via WebRTC ).
7.6.2 WebRTC configuration on OTES

On OTES, open the administration console and modify the following system options:
Use HTTPS only Select the check box
Conference URLS Select the HTTPS option
Anonymous registrar Enter the OpenTouch FQDN without SIP port (for ex-
ample: opentouch.ale.com)
148/195 !"# $ %& #'(

+,
% * 1&
Anonymous registrar Enter the OpenTouch FQDN with the default SIP port
(for example: opentouch.ale.com:5260)
For more information on OTES configuration, refer to document [13].
7.6.3 WebRTC configuration on OTSBC

7.6.3.1 Overview
On OTSBC, open the configuration wizard and perform the following operations:
- Verifying DTLS context for far end user of your OpenTouch server
- Creating a NAT translation table for WebSocket port
- Creating an IP profile for WebSocket
- Configuring the SIP interface table for WebRTC
- Creating a classification table for WebRTC
For more information on OTSBC configuration, refer to the Technical Bulletin called:
OPENTOUCH FROM 0 TO REMOTE WORKER (reference: TC1990) available on the AAPP.
Caution:
WebRTC can only be used if there is an auto-signed certificate available on OTSBC. The
certificate can be either signed by a well-known public authority or by a private/personal authority
certifying that this authority certificate is installed on the WebRTC user computer. For SBC
certificate installation, refer to the Technical Bulletin TC1990.
7.6.3.2 Verifying DTLS context for far end user of your OpenTouch server
1. From the home page, select Advanced and go to: VOIP > VOIP Network > IP group
table
2. Select the IP group corresponding to your Far end user of your OpenTouch server
(FEUOTCV_ice-il-5 in the figure below).
3. Verify that IP group contains a correct DTLS context (it must correspond to the OTSBC
signed certificate)
___change-begin___
!"# $ %& #'(

149/195
Chapter 7 +,
% * 1&
___change-end___
Figure 7.8: IP Group Table configuration example
7.6.3.3 Creating a NAT translation table for WebSocket port

1. From the home page, select Advanced and go to: VOIP > VOIP Network > NAT
translation Table
2. Create a row. Choose the source interface IF_INTERNET (interface for connection to the
WAN) and select your WebRTC ports on the Source Start Port and Source End Port
columns (10080 for RTP and 10081 for SRTP in the figure below).
These ports correspond to those configured on OpenTouch (see: OpenTouch Clients
(Mobile and Desktop) - Implementing OpenTouch Ecosystem - Declaring the OTSBC for
conferencing access via WebRTC ).
___change-begin___
150/195 !"# $ %& #'(

+,
% * 1&
___change-end___
Figure 7.9: NAT Translation Table configuration example
7.6.3.4 Creating an IP profile for WebSocket

1. From the home page, select Advanced and go to: VOIP > Coders and Profiles > IP
Profile Settings
2. Create a row for WebSocket
3. To have DTMF with WebRTC, edit the row and select the SBC Media tab
4. Modify the following fields:
RFC 2833 mode Select Disallow to disallow RFC 2833 mode for Web-
Socket
Alternative DTMF method Select INFO - Cisco
ICE Mode Select Lite
RTU Mux Select Supported
RTCP Feedback Select Enable
___change-begin___
!"# $ %& #'(

151/195
Chapter 7 +,
% * 1&
___change-end___
Figure 7.10: IP Profile Settings configuration example
5. To have DTMF with WebRTC, edit also the RTP IP profile and select the SBC Media tab
6. In the Alternative DTMF method field, select INFO - Cisco
7.6.3.5 Configuring the SIP interface table for WebRTC
152/195 !"# $ %& #'(

+,
% * 1&
1. From the home page, select Advanced and go to: VOIP > VOIP Network > SIP Interface
Table
2. Create a row for WebSocket, and complete the following fields:
Network Interface Choose IF_INTERNET for connection from the WAN
UPD Port and TCP Port This is for the unsecured connection port (10080 in
the example), for tests purpose only. Never deploy
unsecured WebSockets in this field.
TLS port Select the TLS port for WebSocket (10081 in the ex-
ample)
Encapsulating Protocol Select WebSocket
Media Realm Select INTERNET_MEDIA (this has been created
with first OTSBC configuration for OpenTouch. If it is
not the case, create Internet Media on the Media
Realm Table).
TLS context Select the OTSBC signed certificate
___change-begin___
___change-end___
Figure 7.11: SIP Interface Table configuration example
7.6.3.6 Creating a classification table for WebRTC

1. From the home page, select Advanced and go to: VOIP > VOIP Network >
Classification Table
2. Create a row for WebSocket, and complete the following fields:
Rule tab:
Source IP Interface Select your WebRTC SIP Interface
Action tab:
!"# $ %& #'(

153/195
Chapter 7 +,
% * 1&
Source IP Group Select the group for far end user of OpenTouch serv-
er
IP Profile Select the IP profile you have created before for Web-
Socket
___change-begin___
___change-end___
Figure 7.12: Classification Table configuration example
7.7 List of supported operating systems and browsers

Supported operating systems:
- Windows 8/8.1
- Windows 7 (32-bit , and 64-bit)
- Mac OSX 10.8/10.9
The minimum version for conferencing access via WebRTC is 10.9.
Supported web browsers:
- Google Chrome (version 32 or higher, to support conferencing access via WebRTC)
- Microsoft Internet Explorer (not supported for conferencing access via WebRTC)
- Mozilla Firefox (version 38 or higher, to support conferencing access via WebRTC)
- Safari (not supported for conferencing access via WebRTC)
Other standard web browsers (including tablet browsers) may work but have not been tested
or approved by ALE International.
154/195 !"# $ %& #'(

8.1 Overview
For readability purposes, the OpenTouch Connection for PC is called OTCT PC in the rest of
the section
The OTCT PC includes an embedded SIP, and can be installed in a user desktop
environment, either:
- On a computer where no collaboration application is installed.
In such a configuration, the OTCT PC application is installed on the computer as a
standalone client. It can run on computers with any of the following operating systems:
Windows XP, Windows 7 (32/64 bits), or Windows 8 (64 bits)
- On a computer where a collaboration application is already running (IBM Domino).
Extensions of the OTCT PC can also be installed on the e-mail client (Microsoft Outlook or
IBM Notes) present on the computer on which the OTCT PC must run.
These extensions provide services such as: messaging, Instant and One Number.
For details on the compatible versions of the collaboration application (IBM Domino) and
e-mail clients Microsoft Outlook and IBM Notes), refer to the Feature List.

- The list of available OTCT PC features (see: Available features )
- A quick overview of OTCT PC screens (see: Interface overview )
- Details on OTCT PC network infrastructure (see: Topologies )
- The configuration of the OTCT PC on the OpenTouch server and OmniPCX Enterprise
(see: Configuring the OTCT PC for Connection users )
- The mandatory ecosystem configuration for the OTCT PC (see: Configuring the
OpenTouch ecosystem )
- OTCT PC installation on client computers (see: Installing the OTCT PC on client
computers )

The OTCT PC supports business communication features such as:
- Integrated Softphone
- Deskphone control (Remote Call Control)
- Telephony services:
• Make and receive calls
• Call control
• Call session management
!"# $ %& #'(

155/195
Chapter 8 +,
* .
• Call forwarding and overflow

- Scheduled conferences from the Outlook Conference Add-in or MyProfile Web Page
- Current device management
- Call logs (history)
- Business event notifications:
• Missed calls
• New voice messages
• Callback requests
- Directory lookup (UDA)
- Instant Messaging (IM)
- Rich presence for favorite contacts (mixed of telephony and IM)
- Visual Voice Mail (VVM)
- Wideband audio (G.722.2) with SIP signaling for communications between client
computers
- SIP TLS/SRTP (with Reverse Proxy and SBC network elements) for communications
between client computers

After login (see: Launching the OTCT PC ), the OTCT PC appears at the bottom right of the
Windows taskbar. It consists of an icon placed in the status bar (System Tray) and a
search/call box.
Figure 8.1: General view of OTCT PC

The OTCT PC icon provides immediate indication on the user and application status, such as:
incoming call (or event), no device associated, presence status. It also provides access to:
- A status window which displays your current telephone settings, such as: presence status,
current device (that is the device on which incoming calls are directed) and call forwarding,
if configured. Point the mouse cursor on the icon to view related information:
Figure 8.2: Status window example

- The Events Dashboard which displays current incoming calls, notifications (callback
156/195 !"# $ %& #'(

+,
* .
requests, missed calls, and new voice mail messages) and call history. Double click the
corresponding icon:
Figure 8.3: Events Dashboard example

- A menu page to configure application and user settings. Click or right click the
corresponding icon:
Figure 8.4: Menu page example

The available menus are:
• Help: To access help contents
• About: To display the OTCT PC software version
• Options: to configure settings such as:
Option Meaning
Start To select the starting mode
General To define TUI and GUI languages, time zone, and applica-
tion login
Password To define TUI and GUI passwords
Phone numbers To define professional and personal phone numbers
!"# $ %& #'(

157/195
Chapter 8 +,
* .
Option Meaning
Call settings To define the destination to reroute incoming calls, when the
user is unavailable
Search/Call box To define the Search/Call box starting mode
Desktop alert To define the alert messages when receiving incoming calls
Notifications window To define the display of event dashboard
Update To define the OTCT PC update options
IBM Notes To configure OTCT PC features when installed in the Lotus
Notes client (see: Configuring OT2.0 Lotus Notes extension
settings )
• Hide Search/Call box: to show or hide the Search/Call box

• Open Messages: to access the e-mail client present on the computer
• Events Dashboard: to access the Events Dashboard
• Route Calls to: to define the destination device for incoming calls
• Exit: to log out and exit the OTCT PC
The Search/call box is used to initiate a communication, either:
- By dialing the desired number or by entering the name of your contact in the corresponding
box
- By selecting a search mode (by name, telephone number, or e-mail address) and starting
to enter the first digits or letters corresponding to the directory number or name of your
contact. The system automatically suggests contacts as you type (predictive search)
In all cases, click the contact name to start the call or click the arrow icon next to the contact to
display the contact information card.
Clicking the box displays a list of the latest contacts called or searched (redial list).
158/195 !"# $ %& #'(

+,
* .
Figure 8.5: Examples of Search/Call box
8.5 Topologies

Within company premises, the OTCT PC relies on the company intranet network (LAN) for
voice media and data transmission. The OTCT PC can connect to the company intranet
network using a wired connection (Ethernet cable) or a wireless connection (Wi-Fi network).
The OTCT PC uses:
- SIP signaling and RTP connections to perform VoIP communications
Note:
connections).
services and device management)
___change-begin___
___change-end___
8.5.2 Off site topology (remote worker)

Outside company premises, the OTCT PC can rely on any of the following:
- If configured, a VPN (Virtual Private Network) connection to control data transfer, SIP
signaling and media flows (VoIP and video communications through RTP).
!"# $ %& #'(

159/195
Chapter 8 +,
* .
___change-begin___
___change-end___
- If a VPN connection is not configured, the internet network (also called WAN) for data
transfer, SIP signaling and media flows (VoIP communications)
___change-begin___
___change-end___
transmission between the OTCT PC and the company intranet network (LAN). This is
• A reverse proxy, which controls data flows (web services and device management)
160/195 !"# $ %& #'(

+,
* .

• A Session Border Controller (SBC), which controls VoIP communications through
SIP/TLS and SRTP connections
• An OpenTouch Edge Server (OTES) if it is has been delivered with the OpenTouch
solution (optional component). If it is the case, the OTES is used to control data flows
(conferencing, data sharing, instant messaging or web presentations) through HTTPS
connections.

The OTCT PC deployment consists in:
- Configuring the OTCT PC for Connection users
- Installing the OTCT PC on client computers
- Launching the OTCT PC
8.7 Configuring the OTCT PC for Connection users
8.7.1 Overview
The configuration differs according to the Connection user type:
- Connection users declared as SIP extension on the OmniPCX Enterprise (referred as SIP
extension users): the configuration consists in associating the Windows Desktop device
to the SIP extension users and granting them the right to use the OTCT PC (see:
Configuring the Connection users as SIP extension users )
This configuration applies to Connection users who have not physical phone sets. They
work only on personal computer. They have their own virtual SIP device and all SIP
settings and SBC parameters are configured in this virtual SIP device.
- For Connection users other than SIP extension: only the Nomadic SIP feature must be
configured to allow Connection users to use an OTCT PC outside company premises (see:
Configuring the Nomadic SIP for Connection users with physical deskphone )
This configuration applies to Connection users who have physical phone sets within
company premises. When they work outside company premises, they need to switch to
personal computer mode also called Nomadic SIP.
8.7.2 Prerequisite
Connection users must have been previously declared on the OmniPCX Enterprise and
OpenTouch. For more information, refer to the chapter User creation and administration of
document [3].
Caution:
If Connection users have an analog set as main set, for the application to work after login, you
must change their set type to Analog with 4980 on the OmniPCX Enterprise.
8.7.3 Configuring the Connection users as SIP extension users
!"# $ %& #'(

161/195
Chapter 8 +,
* .
8.7.3.1 Process overview

The OTCT PC configuration for SIP extension users consists in:
1. Declaring the OmniVista 8770 Device Management Server
2. Associating the windows desktop device to the SIP extension users
3. Granting the SIP extension users the right to use the OTCT PC
4. Configuring the SIP extension type on the OpenTouch
8.7.3.2 Declaring the OmniVista 8770 Device Management Server
The Device Management Server (DMS) is required for Connection users declared as SIP
extension in the OmniPCX Enterprise. The DMS located in the OmniVista 8770 server must be
declared on the OpenTouch server.
1. From the OpenTouch configuration window of OmniVista 8770, select Eco system > IT
Server
2. Right click and select Create > Device management server
Figure 8.9: DMS configuration window example

Display name Enter a display name
FQDN Enter the FQDN of the computer on which the OmniVista 8770 server
is running
162/195 !"# $ %& #'(

+,
* .
8.7.3.3 Associating the windows desktop device to the SIP extension users
Caution:
To avoid synchronization issues, use the Users application of the OmniVista 8770 to associate
the windows desktop device to the SIP extension users. Only the procedure from the Users
application is presented here.
To associate the windows desktop device to the SIP extension users:
2. Expand the tree structure and select the SIP extension users
3. Access the contextual menu and select Associate SIP device > New, then select
Windows Desktop
Figure 8.10: Windows desktop device association window example

4. Complete the following field in the General tab:
Device identity Enter the windows desktop device identifier as follows: <directory
number>@<OpenTouch server FQDN>

The windows desktop device is created and associated to the corresponding SIP extension
user. Windows desktop device is displayed under the SIP extension user in the tree
structure of Users application
When the Windows desktop device is associated to a SIP extension user, a configuration file is
automatically created on the OmniVista 8770 server. It is placed in the directory:
C:\8770\data\DM\deploy\MYICPC01. This file is available using the following URL:
!"# $ %& #'(

163/195
Chapter 8 +,
* .
http://<OmniVista 8770 server FQDN>/DM/MYICPC01/<directory

number>@<OpenTouch server FQDN>.
The device configuration file is identified by the SIP URI of the SIP extension user as follows:
<directory number@OpenTouch server FQDN>.
8.7.3.4 Granting the SIP extension users the right to use the OTCT PC
Note:
The computer license may have already been added while creating users and configuring their profile.
To grant SIP extension users the right to access the application from a computer:
2. Expand the tree structure and select the corresponding SIP extension user

Desktop Select the check box to allow the SIP extension user to use the OTCT
PC
Caution:
The Nomadic SIP check box must not be selected.
8.7.3.5 Configuring the SIP extension type on the OpenTouch
SIP extension users can connect to an OTCT PC, provided that their SIP extension type is set
164/195 !"# $ %& #'(

+,
* .
to softphone in OpenTouch configuration.

To modify the SIP extension type:
2. Expand the tree structure and select the corresponding SIP extension user
3. In the properties area, select the OT configuration tab, then select the Device tab
___change-begin___
___change-end___
Figure 8.12: Device configuration window example
SIP extension type Use the drop-down menu to select the Softphone option.
Default value: Deskphone
Caution:
Do not validate the Deskphone option.
8.7.4 Configuring the Nomadic SIP for Connection users with physical
deskphone
8.7.4.1 Overview
Caution:
The Nomadic SIP feature does not apply to Connection users declared as SIP extension in the
OmniPCX Enterprise.
!"# $ %& #'(

165/195
Chapter 8 +,
* .
The Nomadic SIP feature is required to allow Connection users to use the OTCT PC as a VoIP
SIP device outside the enterprise using VoIP over internet (SIP/RTP), via the audio capabilities
of the computer:
- On site, the OTCT PC provides remote call control of an OmniPCX Enterprise device (for
example, an IP Touch set)
- Off site, a user can activate the nomadic SIP mode by selecting Personal Computer as
current phone, allowing to make incoming and outgoing calls through the OTCT PC
The Nomadic SIP feature configuration consists in:
1. Configuring the ghosts Z on the OmniPCX Enterprise
2. Declaring the ghosts Z on the OpenTouch server
3. Configuring SIP external devices on the OmniPCX Enterprise
4. Declaring SIP external devices on the OpenTouch server
5. Granting the right to the Nomadic SIP feature to Connection users
8.7.4.2 Configuring the ghosts Z on the OmniPCX Enterprise
Virtual resources (also called Ghosts Z) are required to use the Nomadic SIP feature.
To create a Ghost Z:
1. From the OmniPCX Enterprise configuration window of the OmniVista 8770, select Users
Figure 8.13: User configuration window example on the OmniPCX Enterprise
166/195 !"# $ %& #'(

+,
* .

Directory Number Enter the directory number of the Ghost Z
Shelf Address 255
Board Address 255
Equipment Address 255
Set Type Select: Analog
Note 1:
The Ghost Z does not have a physical connection.
4. In the Facilities tab, review/modify the following attributes:
Ghost Z Select the check box
Ghost Z feature Select Nomadic

Do not forget to configure the correct connection class of service of Ghosts Z, which must offer
the same right as for Connection users.
Note 2:
- Create more or less virtual resources depending on the mode assigned to the Connection users.
- If, for example, the system has a potential of 50 users using the OTCT PC:
• If these users are home-workers and need the Nomadic SIP feature with no service interruption,
you must create 50 virtual phone sets (one per user)
• If some of these users only require the Nomadic SIP feature temporarily, and if this service is not
critical, you can create a pool of 10 virtual phone sets only (there is no strict rule for the dynamic
mode)
8.7.4.3 Declaring the ghosts Z on the OpenTouch server
services > Topology > OXE CS > OXE resources
!"# $ %& #'(

167/195
Chapter 8 +,
* .
Figure 8.14: OmniPCX Enterprise resource configuration window example

Display name Enter a display name for the Ghost Z range of numbers. This
name is used to identify the Ghost Z range of numbers in the
OpenTouch configuration window
OXE Application server Use the drop-down menu to select the OmniPCX Enterprise on
which the Ghosts Z have been configured
Z ghosts min value Enter the first directory number of the Ghost Z range
Z ghosts max value Enter the last directory number of the Ghost Z range

8.7.4.4 Configuring SIP external devices on the OmniPCX Enterprise
A pool of SIP devices must be created on the OmniPCX Enterprise. A device of this pool is
used for each Connection user who has the right to the Nomadic SIP feature.
The number of devices to be created in the pool depends on the number of users and on
traffic.
The user configuration window opens (see: figure: User configuration window example on
the OmniPCX Enterprise )
168/195 !"# $ %& #'(

+,
* .
Directory Number Enter the directory number of the SIP device

Shelf Address Enter 255
Board Address Enter 255
Equipment Address Enter 255
Set Type Select SIP device
4. In the SIP tab, review/modify the following attributes:

URL UserName Enter the URL user name, for example, the directory number of
SIP device
SIP Passwd Enter the password

Do not forget to configure the correct connection class of service of SIP devices, which must
offer the same rights as for Connection users.
8.7.4.5 Declaring SIP external devices on the OpenTouch server
For each SIP device of the pool created on the OmniPCX Enterprise, create an OXE SIP
subscriber on the OpenTouch:
services > Topology > OXE CS > OXE SIP Subscriber
Figure 8.15: OmniPCX Enterprise SIP subscriber configuration window example

3. In the General tab, review/modify the following attributes:
!"# $ %& #'(

169/195
Chapter 8 +,
* .
SIP nomadic Directory Enter the directory number of the SIP device created on the Omni-
Number PCX Enterprise
OXE CS Select the OmniPCX Enterprise on which SIP devices have been
created
SIP Login Enter the value set in the URL UserName field for SIP device con-
figuration (see: Configuring SIP external devices on the OmniPCX
Enterprise )
SIP Password Enter the value set in the SIP Passwd field for SIP device config-
uration (see: Configuring SIP external devices on the OmniPCX
Enterprise )

8.7.4.6 Granting the right to the Nomadic SIP feature to Connection users
To grant Connection user the right to the Nomadic SIP feature:
1. From the OpenTouch configuration window of the OmniVista 8770, select Users and
devices > Device
2. Select the device of the Connection user
Figure 8.16: Device configuration window example

3. On the General tab, review/modify the following attributes:
170/195 !"# $ %& #'(

+,
* .
Home OXE Select the OmniPCX Enterprise on which the Connection user has
been created
User remote connection Select True (default value) to grant access to the Nomadic SIP
mode feature
Cellular Select True (default value)

5. From the OpenTouch configuration window of the OmniVista 8770, select Users and
devices > Users
6. Select the Connection user to modify
7. In the Licenses tab, review/modify the following attribute:
Nomadic SIP Select the check box to enable the Nomadic SIP feature
9. Select the Connection user
The user configuration window opens (see: figure: User configuration window example on
the OmniPCX Enterprise )

OTCT PC. The network elements to consider are:
elements
between the OTCT PC and OpenTouch server
communications between the OTCT PC and OpenTouch server
8.9 Installing the OTCT PC on client computers
8.9.1 Installing the OTCT PC application on computers as standalone client

8.9.1.1 Overview
The OTCT PC may either be installed on client computers from the client computers
themselves (see: Performing a single client installation ), or deployed on several computers in
one go (see: Performing multiple client installation (mass provisioning) ).
!"# $ %& #'(

171/195
Chapter 8 +,
* .
- You must have local administration rights on the target computers to install or uninstall the
OTCT PC
- You must have the OTCT PC installation package (for example:
OpenTouchConnection-2.1.xxx.xxx.msi and
OpenTouchConnection-2.1.xxx.xxx.exe must be delivered)
The current version is provided with the installation file (*.iso format) of the OpenTouch
core: edit the *.iso file and select Products > ot_connection > Clients >
OpenTouchConnection
- The OTCT PC cannot be installed on computers where the OmniTouch™ 8600 My Instant
Communicator mobile Edition is already running. The OmniTouch™ 8600 My Instant
Communicator must be uninstalled before the OTCT PC is installed
- The Microsoft .NET Framework must have been previously installed on computers.
The versions required are Microsoft .NET Framework 3.5 and 4.0. These versions are
available from the Microsoft web site:
Important:
A control is performed during OTCT PC installation on the client computer: a warning
message is displayed when the installed version of Microsoft .NET Framework is not
compatible with the OTCT PC version to install.
- The Microsoft Visual Studio Tools for Office Runtime (VSTOR) must be installed on
computers only when an extension of the OTCT PC must be included to the e-mail client
present on computers (Microsoft Outlook or IBM Lotus Notes).
The minimum version required is Microsoft VSTOR 10.0.40219. This version is available
from the Microsoft web site:
Example:
A control is performed during OTCT PC installation on the client computer, if applicable, a warning
message indicates that VSTO 2010 is required and provides the download URL.
8.9.1.3 Performing a single client installation
Note 1:
The installation wizard also installs the OTCT PC extension when a Microsoft Outlook client is present on
the computer.
To install the OTCT PC on a single client computer:
1. Double click the OTCT PC setup file (for example:
OpenTouchConnection-2.1.xxx.xxx.msi) or use the following command line:
msiexec.exe /i <access path>\OpenTouchConnection-<version>.msi
This displays the installation wizard welcome page
___change-begin___
172/195 !"# $ %& #'(

+,
* .
___change-end___
Figure 8.17: Welcome window example
Note 2:
A warning message is displayed when the OTCT PC software version is not compatible with the
computer operating system (32 or 64-bit). When this occurs, the message indicates which OTCT PC
setup file must be used.
2. Click Next
The license agreement window is displayed
___change-begin___
!"# $ %& #'(

173/195
Chapter 8 +,
* .
___change-end___
Figure 8.18: License agreement window example
3. Read and accept the terms of the license, and click Next
A directory location selection window is displayed
Note 3:
The installation package searches for a previous version of OTCT PC on the target computer. When
a previous version is found, the setup process offers to delete, repair or remove the software.
___change-begin___
174/195 !"# $ %& #'(

+,
* .
___change-end___
Figure 8.19: Installation directory selection window example
4. If desired, change the installation directory and click Next
The shortcut creation window is displayed
___change-begin___
___change-end___
Figure 8.20: Shortcut creation window example
5. Select your desired type(s) of shortcut and click Next
The following window is only displayed when a Microsoft Outlook client is present on the
computer.
___change-begin___
!"# $ %& #'(

175/195
Chapter 8 +,
* .
___change-end___
Figure 8.21: OTCT PC extension configuration window example
6. To install the OTCT PC extension in Microsoft Outlook, click Next. To reject the installation
of the OTCT PC extension, right click the folder icon in the tree structure and select the
option This feature will not be available
A server information window is displayed
___change-begin___
176/195 !"# $ %& #'(

+,
* .
___change-end___
Figure 8.22: Server information window example
7. Complete the following parameters:
• Hostname: Enter the private FQDN of the OpenTouch server. This allows the OTCT
PC to connect to the OpenTouch server within company premises (see: On site
topology )
• Reverse Proxy: Enter the public FQDN of the OpenTouch server. This allows the
OTCT PC to connect to the OpenTouch server when outside company premises (see:
Off site topology (remote worker) )
8. Click Next
The installation confirmation window is displayed
Figure 8.23: Installation confirmation window example

9. Click the Install button to start installation
Note 4:
If necessary, click the Back button to change any option previously configured.
At the end of the process, the installation wizard finalization window is displayed
___change-begin___
!"# $ %& #'(

177/195
Chapter 8 +,
* .
___change-end___
Figure 8.24: Installation wizard finalization window example
10. If desired, select the check box to automatically launch the OTCT PC after the installation
wizard is closed, and click Finish
This closes the installation wizard
8.9.1.4 Performing multiple client installation (mass provisioning)
Standard deployment tools are available to install several clients simultaneously from a remote
computer on the network.
These tools rely on command lines. For an OTCT PC installation with the msi package, the
command line used is: msiexec /i <access
path>\OpenTouchConnection-<version>.msi /qn where:
- /i specifies the msi package to run
- <access path> specifies where is located the msi package
- /qn requests installation to run silently
The command line can include additional options such as:
INSTALLDIR Any valid path Specify the installation folder where the
OTCT PC must be installed
Note 1:
The default path is: <program
files>\Alcatel-Lucent\OpenTouchCon
nection
178/195 !"# $ %& #'(

+,
* .

ISSHORTCUTDESKTOP True or False If set to True (default value), a shortcut to
OTCT PC is added to the computer
ISSHORTCUTSTARTUP True or False If set to True (default value), a shortcut to
OTCT PC is added to the computer start
menu
Note 2:
In the two cases, a shortcut is automatically
placed in the following path: Start > Alca-
tel-Lucent > OpenTouch Conversation
SERVER_LOCATION Any valid FQDN (no Specify the private FQDN of the
IP address) OpenTouch server (on-site mobility)
PUBLIC_LOCATION Any valid FQDN (no Specify the public FQDN of the reverse
IP address) proxy used by the OTCT PC to connect to
the OpenTouch server outside company
premises (off site mobility)
APPLICATIONMODE ACU or INTEGRATED Specify the user desktop environment:
- ACU (default value): OTCT PC installa-
tion on a computer where no collabor-
ation application is running
- INTEGRATED: OTCT PC installation
on a computer where a collaboration
application is running
COMMUNICATIONCLIENT OTCTPC, LYNC, or Specify the type of implementation:
ST - OTCTPC: OTCT PC as standalone cli-
ent
- LYNC: OTCT PC installed with a Mi-
crosoft Lync client
- ST: OTCT PC integration into an IBM
Sametime client
OUTLOOKCONTACTPLUGIN True or False If set to True (default value), a plug-in is
installed on Microsoft Outlook to syn-
chronize the contacts of OTCT PC with
those of Microsoft Outlook
OUTLOOKEXTENSIONS True or False If set to True (default value), an extension
of OTCT PC is installed on Microsoft Out-
look
These additional options must be entered in upper case (mandatory).

Example:
msiexec /i D:\soft\OpenTouchConnection-2.1.117.002.msi /qn
INSTALLDIR=C:\Program\Alcatel-Lucent\OpenTouchConnection
ISSHORTCUTDESKTOP=False PUBLIC_LOCATION=rp.mycompany.com
8.9.2 Installing the OTCT PC on computers with collaboration clients

8.9.2.1 Installing the OTCT PC in Microsoft Lync integration mode
!"# $ %& #'(

179/195
Chapter 8 +,
* .
To install the OTCT PC with a Microsoft Lync client on the same computer, perform the
following operations:
1. From the OpenTouch configuration window of the OmniVista 8770, declare the Microsoft
Lync server in OpenTouch parameters:
a. Select: Eco system > IT Server
b. Access the contextual menu and select Create > OCS Server
Figure 8.25: Server creation window example

Display name Enter the Lync server display name
FQDN Enter the FQDN of the Lync server
d. In the Configuration tab, keep the server port default value: 443
The Lync server is created in the server list
2. On the Lync client computer:
a. Install the Microsoft Lync 2010 SDK redistributable file available from the following
Microsoft web site:
http://code.msdn.microsoft.com/office/Adding-Lync-2010-SDK-4d0b92f5/file/22181/9/
Lync%202010%20Adding%20Lync%202010%20SDK%20Runtime%20to%20an%
20Application%20Installation%20Program.zip:
i. Extract the content of the zip file and go to the folder: C# > Lync2010SDK
ii. Launch the LyncSdkRedist.msi file on the computer and follow the instructions
on screen
b. Install the OTCT PC client solution as follows:
i. Launch the following command line:
180/195 !"# $ %& #'(

+,
* .
msiexec.exe /i <access path>\OpenTouchConnection-<version>.msi

SERVER_LOCATION=<OpenTouchFQDN> APPLICATIONMODE=<INTEGRATED>
COMMUNICATIONCLIENT=<LYNC>
An installation wizard welcome page opens.
ii. Follow the instructions on screen (see: Performing a single client installation )
8.9.2.2 Installing the OTCT PC in IBM Sametime integration mode
To integrate OTCT PC services into an IBM Sametime client, perform the following operations:
1. From the OpenTouch configuration window of the OmniVista 8770, declare the Sametime
server in the OpenTouch parameters:
a. Select: Eco system > IT Server
b. Access the contextual menu and select Create > Sametime server
The server creation window opens (see: figure: Server creation window example )
Display name Enter the Sametime server display name
FQDN Enter the FQDN of the Sametime server
d. In the Configuration tab, keep the server port default value: 1516
The Sametime server is created in the IT server list
Important:
• If your system includes an OpenTouch Multimedia Conferencing and Collaboration server
(also called ACS) and a Sametime server, the operating collaboration server for users
must be IBM Lotus Sametime
• A system cannot integrate IBM Lotus Sametime and Microsoft Office Communicator as
collaboration service, they are mutually exclusive.
2. On the Lotus Sametime client computer, install the OTCT PC client solution using the
following command line: msiexec.exe /i <access
path>\OpenTouchConnection-<version>.msi SERVER_LOCATION=<OpenTouchFQDN>
APPLICATIONMODE=<INTEGRATED>, COMMUNICATIONCLIENT=<ST> . An installation wizard
welcome page opens. Follow the instructions on screen (see: Performing a single client
installation )
8.9.3 Installing the OTCT PC on computers with e-mail clients

8.9.3.1 Installing the OTCT PC in Microsoft Outlook integration mode
No specific extension installation is required. The extension installation is performed during the
installation of the OTCT PC on the computer: the OTCT PC installation program automatically
detects the presence of Microsoft Outlook on the client computer. If Microsoft Outlook is
installed on the computer, the corresponding extension is installed transparently.
This applies for a single or multiple client installation (see: Installing the OTCT PC application
on computers as standalone client ).
To enable users to handle their voice messages from a Microsoft Outlook client, it is required
to implement a Unified Messaging voice mail system using a Microsoft Exchange server. To
implement a Unified Messaging voice mail system, refer to the section Configuring voice mail
services of [3].
!"# $ %& #'(

181/195
Chapter 8 +,
* .
8.9.3.2 Installing the OTCT PC in Lotus Notes integration mode

No specific extension installation is required. The extension installation is performed during the
installation of the OTCT PC on the computer: the OTCT PC installation program automatically
detects the presence of Lotus Notes on the client computer. If Lotus Notes is installed on the
computer, the corresponding extension is installed transparently.
This applies for a single or multiple client installation (see: Installing the OTCT PC application
on computers as standalone client ).
To enable users to handle their voice messages from a Lotus Notes client, it is required to
implement a Unified Messaging voice mail system using an IBM Domino server. To implement
a Unified Messaging voice mail system, refer to the section Configuring voice mail services of
[3].
8.10 Launching the OTCT PC
8.10.1 Prequisites
- Connection users must be declared on the OpenTouch with rights to the following features:
• Desktop (see: Granting the SIP extension users the right to use the OTCT PC )
• Nomadic SIP (see: Granting the right to the Nomadic SIP feature to Connection users
)
- If starting the OTCT PC from outside company premises (off site mobility), ensure that the
public URLs of the network components have been configured (see: OpenTouch Clients
(Mobile and Desktop) - Implementing OpenTouch Ecosystem - Configuring the internet
DNS server )
8.10.2 Connecting to the OpenTouch server

Once the OTCT PC is installed on the client computer, proceed as follows:
1. Start the OTCT PC using any of the following methods:
• Select the shortcut from the start menu of Windows
• Click the icon on the client computer
At startup, the OTCT PC first tries to reach the private FQDN of the OpenTouch server. If
the private FQDN of the OpenTouch server can be reached, the login window is displayed.
182/195 !"# $ %& #'(

+,
* .
Figure 8.26: OTCT PC login window example

2. Complete the parameters:
Username Enter an authentication login to access the OTCT PC
Password Enter the password
3. Click Sign In
A certificate installation window opens
4. Click OK, and install the certificate following the instructions on screen
The OTCT PC main window opens (see: Interface overview )
If the private FQDN of the OpenTouch server cannot be reached, the OTCT PC tries to reach
the server through the public FQDN of the OpenTouch server. A remote connection
authentication window is displayed.
!"# $ %& #'(

183/195
Chapter 8 +,
* .
Figure 8.27: OTCT PC login window example for remote connection

If this occurs, the following parameters must be entered:
- The authentication login to access the reverse proxy
- The password
8.11 Configuring OTCT PC extension settings
8.11.1 Configuring OT2.0 Outlook extension settings

1. Open the Microsoft Outlook present on the computer
2. From the Microsoft Outlook interface, click the File menu and select the Options item
The Outlook option window is displayed
3. Select the Add-ins option
The list of active and inactive add-ins is displayed
4. Select the OTCT PC extensions present in the list of add-ins
5. At the top of the window, click the Add-in Options button
The add-in option window is displayed
6. Click the OpenTouch tab to display the OTCT PC extension settings
184/195 !"# $ %& #'(

+,
* .
Figure 8.28: Extension configuration window for Microsoft Outlook

7. Review/modify the following parameters:
!"# $ %& #'(

185/195
Chapter 8 +,
* .
Start automatically If the check box is selected, the extensions are automatically started
with Microsoft Outlook.
Use private code If the check box is selected, a private code must be entered by the
user before performing the call. Use the Private Code box to enter
the corresponding private code.
No contact card If the check box is selected, no contact card is displayed on incoming
call.
Display contact card If the check box is selected, the contact card of the caller is displayed
(local contacts and/or global address list are searched according to
the user option selected below).
Search in personal If the check box is selected, a search is performed by the application
address book in the user contacts.
Search in global ad- If the check box is selected, a search is performed by the application
dress book in the Microsoft Exchange global address list.
Create contact card If the check box is selected, when no search result is available, an
Outlook contact sheet is displayed for creation. This allows to create
a contact card for the caller.
8. Click Ok
8.11.2 Configuring OT2.0 Lotus Notes extension settings

1. From the Windows taskbar of the computer, right click the OTCT PC icon
The menu page opens
2. Open the Options window and select the Lotus Notes option
186/195 !"# $ %& #'(

+,
* .
Figure 8.29: Extension configuration window for Lotus Notes

3. Review/modify the following parameters:
Create a contact card If the check box is selected, when no search result is available, a Lo-
tus Notes contact sheet is displayed for creation.
Search contact card If the check box is selected, a search is performed by the application
in personal address in the user personal address book.
book
Search contact card If the check box is selected, a search can be performed by the ap-
in global address plication in the global address book.
book
!"# $ %& #'(

187/195
Chapter 8 +,
* .
Search contact card If the check box is selected, a search can be performed by the ap-
in enterprise address plication in the enterprise address book.
book
Server Enter the address of the server including the enterprise address
book.
Address book name Enter the name of the address book.
Call the business If the check box is selected (default option), the call of a Lotus Notes
number contact is performed directly with the business phone number.
Choose the number If the check box is selected, the list of all the phone numbers re-
in the list trieved from the contact list is displayed.
Note 1:
This check box is not selected by default.
Associate a project If the check box is selected, a private/project code must be entered
code to the calls by the user before performing the call.
Note 2:
This check box is not selected by default.
4. Click Apply
8.12 Uninstalling the OTCT PC from client computers

Prerequisite: Microsoft Outlook must be stopped on client computers before uninstalling the
OTCT PC. A control is performed during OTCT PC uninstallation on the client computer. A
warning message is displayed if Microsoft Outlook is running.
The OTCT PC uninstallation can be performed, either:
- From the Start menu: select Alcatel-Lucent > OpenTouch Connection > Uninstall and
follow the instructions on screen
Note:
In Lync or Sametime integration mode, uninstallation from the Start menu is not available (if you
have installed the OTCT PC using command line with specific parameters).
- From the Add/remove programs interface in the Control panel of the client computer: select
the OpenTouch Connection program and click Remove
Performing multiple client uninstallation is possible from the msi package, using the following
command line:
msiexec.exe /x <access path>\OpenTouchConnection-<version>.msi /qn
188/195 !"# $ %& #'(

"
"
9.1 Overview
The OpenTouch Meeting Manager provides an easy way to handle OpenTouch conferences. It
is a Chrome application which behaves as a Rich Internet Application (RIA) to schedule and
manage multimedia conferences.
___change-begin___
___change-end___
Figure 9.1: Interface example

- Display the list of conferences : your conferences and the conferences you are invited to
- Join a conference
!"# $ %& #'(

189/195
Chapter 9 +,
, ,
- Create conferences and permanent rooms

- Update and delete conferences
- Display conference details
- Select participants from your Favorites list and corporate directory
- Invite participants by e-mail
9.3 List of supported operating systems

The supported operating systems are:
- Windows 7 (64-bit)
- Windows 8/8.1 (64-bit)
- Mac OSX 10.10 “Yosemite”
Chrome must be up-to-date to use OpenTouch Meeting Manager.
Once Chrome is installed, user privileges are enough to install and run the application.
9.4 Prerequisite
To schedule and manage conferences, the OpenTouch Meeting Manager requires user option:
3BA09423JA, in complement to OpenTouch user license with Conferencing services. This
corresponds to the license ACS_CONFERENCE_SCHEDULING.

1. From the Chrome browser, access the Chrome Web Store
2. Search for the OpenTouch Meeting Manager with keywords
3. Click the ADD TO CHROME button
An OpenTouch Meeting Manager icon ( ) is displayed in the Chrome Application
Launcher
Note 1:
For regular use, it is convenient to pin the shortcut of the application in the Task Bar
4. Click the OpenTouch Meeting Manager icon
A login page opens
___change-begin___
190/195 !"# $ %& #'(

+,
, ,
___change-end___
5. At first startup, you are prompted to enter:
• The public and private FQDNs of the OpenTouch server (internal and external
accesses)
6. Click the Sign In button
The OpenTouch Meeting Manager opens
Note 2:
The interface language corresponds to that of Chrome.
Note 3:
The software is automatically updated for each new version, and always up-to-date with the latest
enhancements and fixes.
9.6 Accessing logs

The OpenTouch Meeting Manager provides applicative logs. Log messages can be retrieved
from the application itself:
1. From the OpenTouch Meeting Manager home page, click the information icon ( ) at the
top of the home page
2. Click the Logs link
3. Select the destination directory for logs
!"# $ %& #'(

191/195
Chapter 9 +,
, ,
192/195 !"# $ %& #'(

10.1 Overview
The OpenTouch Conversation One provides an easy way to handle OpenTouch services from
computers. It is a Chrome application which behaves as a Rich Internet Application (RIA) to
manage your contacts and access multimedia services (audio call and Instant Messaging).
This application is available for Conversation and Connection users.
___change-begin___
___change-end___
Figure 10.1: Interface example
OpenTouch Conversation One does not require any license or user configuration.

!"# $ %& #'(

193/195
Chapter 10 +,
%
- Audio call (click-to-call)

- Instant Messaging (IM)
- Presence (mixed of telephony and IM)
- Directory lookup
- P2P collaboration (documentation sharing)
10.3 List of supported operating systems

The supported operating systems are:
- Windows
- Mac OSX
- Linux
- Chromebook
Chrome must be up-to-date to use OpenTouch Conversation One.
Once Chrome is installed, user privileges are enough to install and run the application.

1. From the Chrome browser, access the Chrome Web Store
2. Search for the OpenTouch Conversation One with keywords
3. Click the ADD TO CHROME button
An OpenTouch Conversation One icon ( ) is displayed in the Chrome Application
Launcher
4. Click the OpenTouch Conversation One icon
A login page opens
___change-begin___
194/195 !"# $ %& #'(

+,
%
___change-end___
5. At first startup, you are prompted to enter:
• The public and private FQDNs of the OpenTouch server (internal and external
accesses)
6. Select the Show remote access check box to use the OpenTouch Conversation One from
any location (provided you have been granted you the right to off-site mobility)
7. Select the Remember password check box to skip entering your password the next time
you log in
8. Click the Login button
The OpenTouch Conversation One opens
Note 1:
The interface language corresponds to your Chrome language.
Note 2:
The software is automatically updated for each new version, and always up-to-date with the latest
enhancements and fixes.
!"# $ %& #'(

195/195
###
$%$&
$

Ot2.1 Am Otclientadmin 8al90638usac 2 en

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

Ot2.1 Am Otclientadmin 8al90638usac 2 en

Uploaded by

Copyright:

Available Formats



The information presented is subject to change without notice.

ALE International assumes no responsibility for inaccuracies contained

Copyright © ALE International, 2015

In the interest of continued product development, ALE International reserves

 Overview ..................................................................................................... 10

 Overview ..................................................................................................... 13

 !"# $ %& #'( 

 Overview ......................................................................................................... 16

 Overview ..................................................................................................... 31

4/195  !"# $ %& #'( 

 Generating a QR code ........................................................................... 47

 Overview ..................................................................................................... 57

 !"# $ %& #'( 

 Installing the OTCV PC on client computers ................................. 70

 Overview ..................................................................................................... 87

6/195  !"# $ %& #'( 

  Configuring the OmniPCX Enterprise for off-site mobility ............................. 104

 Overview ................................................................................................... 140

 !"# $ %& #'( 

 Interface overview ................................................................................. 142

 On site topology ............................................................................................ 145

 Off site topology (remote users) ................................................................... 146

  WebRTC configuration on OpenTouch ........................................................ 148

  WebRTC configuration on OTES ................................................................. 148

  WebRTC configuration on OTSBC ............................................................... 149

 Overview ................................................................................................... 155

8/195  !"# $ %& #'( 

  Prequisites .................................................................................................... 182

 Overview ................................................................................................... 189

 Overview ................................................................................................... 193

 !"# $ %& #'( 

1.2 About this document

10/195  !"# $ %& #'( 

The complete OpenTouch documentation consists in separated documents, each

 !"# $ %& #'( 

Documentation title Part number

12/195  !"# $ %& #'( 

 !"# $ %& #'( 

3.2 Configuring the firewall

Figure 3.1: Firewall configuration

3.3 Configuring the DNS server

14/195  !"# $ %& #'( 

3.3.2 Configuring the internet DNS server

Figure 3.2: DNS configuration outside company premises

3.3.3 Configuring the intranet DNS server

 !"# $ %& #'( 

Figure 3.3: DNS configuration within company premises

3.4 Configuring a reverse proxy

16/195  !"# $ %& #'( 

3.4.2 Declaring the reverse proxy on OpenTouch

Figure 3.4: Reverse proxy configuration window example

 !"# $ %& #'( 

Display name Enter a display name

3. Click the validate icon to save your modifications

3.4.3 Configuring a Blue Coat reverse proxy

18/195  !"# $ %& #'( 

3.4.3.4 Configuring forwarding hosts

 !"# $ %& #'( 

Web services Event Server

For OmniVista 8770:

3.4.3.5 Configuring realms for client authentication

• For the Action object:

Overview ..................................................................................................... 10

Overview ..................................................................................................... 13

!"# $ %& #'(

Overview ......................................................................................................... 16

Overview ..................................................................................................... 31

4/195 !"# $ %& #'(

Generating a QR code ........................................................................... 47

Overview ..................................................................................................... 57

!"# $ %& #'(

Installing the OTCV PC on client computers ................................. 70

Overview ..................................................................................................... 87

6/195 !"# $ %& #'(

Configuring the OmniPCX Enterprise for off-site mobility ............................. 104

Overview ................................................................................................... 140

!"# $ %& #'(

Interface overview ................................................................................. 142

On site topology ............................................................................................ 145

Off site topology (remote users) ................................................................... 146

WebRTC configuration on OpenTouch ........................................................ 148

WebRTC configuration on OTES ................................................................. 148

WebRTC configuration on OTSBC ............................................................... 149

Overview ................................................................................................... 155

8/195 !"# $ %& #'(

Prequisites .................................................................................................... 182

Overview ................................................................................................... 189

Overview ................................................................................................... 193

!"# $ %& #'(

10/195 !"# $ %& #'(

!"# $ %& #'(

12/195 !"# $ %& #'(

!"# $ %& #'(

14/195 !"# $ %& #'(

!"# $ %& #'(

16/195 !"# $ %& #'(

!"# $ %& #'(

18/195 !"# $ %& #'(

!"# $ %& #'(

20/195 !"# $ %& #'(

!"# $ %& #'(

24/195 !"# $ %& #'(

26/195 !"# $ %& #'(

!"# $ %& #'(

28/195 !"# $ %& #'(

!"# $ %& #'(

30/195 !"# $ %& #'(

!"# $ %& #'(

32/195 !"# $ %& #'(

34/195 !"# $ %& #'(

!"# $ %& #'(

36/195 !"# $ %& #'(

!"# $ %& #'(

38/195 !"# $ %& #'(

!"# $ %& #'(

40/195 !"# $ %& #'(

!"# $ %& #'(

42/195 !"# $ %& #'(

!"# $ %& #'(

44/195 !"# $ %& #'(

!"# $ %& #'(