TBE046 OpenTouch R2.2.1 Overview Ed01

OpenTouch R2.2.
1 Overview
Edition 01: November 2016
Pre-Sales presentation
OpenTouch R2.2.1 Overview Ed01
Pre-Sales
With speaker notes
COPYRIGHT 2016 ALE International. ALL RIGHTS RESERVED.
History
Edition 01: Creation for release 2.2.1 General Availability
Disclaimer
This documentation is provided for reference purposes only and does not fully describe the capabilities of each Product and related features. Therefore, ALE
International declines any liability for inaccuracies contained herein. For an exhaustive view on features list and product limits for the current product release please
see the required Feature List/Product Limits document available through the ALE eBusiness Portal web site.
In the interest of continued product development, ALE International reserves the right to make improvements or other changes to this document and the products it
describes at any time without prior notice.
Copyright
Copyright ALE International 2016. Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright
holder.
Distribution of the work or derivative of the work in any standard (paper) book form for commercial purposes is prohibited unless prior permission is obtained from the
copyright holder.

Pre-Sales
2
Preamble
The objective of this presentation is to introduce the new release R2.2.1 of the following
products:
OpenTouch Multimedia Services (OTMS),
OpenTouch Message Center (OTMC) and
OpenTouch Business Edition (OTBE)
Complementary information related to some of the evolutions is provided in other presales

presentations or design guide. Such documents are mentioned via the sign
as well as in the
Reference documentation section of this presentation.

Pre-Sales
3
OpenTouch R2.2.1 at a glance

MESSAGING SERVICES
ARCHITECTURE
OTMS-V + OXE: quotation & license control modification
OpenTouch voice messaging mobile client
OTES functions provided by Reverse Proxy
Graphical password management from NOE deskphones
OpenTouch networking
Security improvements
OpenTouch redundancy over extended L2 network
Automated Attendant traffic statistics
Support of TLS v1.2 (*)
COLLABORATION & GROUPWARE SERVICES
OXE TELEPHONY INTEGRATION
OT Supervision & call pick-up groups for Connection users
Callback request on busy
Laser pointer (document sharing)
Support of OXE Desk Sharing feature
DEVICES & USERS
ECO-SYSTEM
OTC PC VDI support, including VoIP
OTC PC ergonomic enhancements
Microsoft Exchange 2016 support
Support of AEC on OTC PC

OpenTouch Mass Provisioning improvement

Pre-Sales
4
Agenda
1.
2.
3.
4.
5.
6.
7.
8.
General information
Architecture
Messaging services
Collaboration & groupware services
OXE telephony integration
Eco-system
Devices & users
Reference documentation

Pre-Sales
5
General information
Delivery Planning
OTMS/OTMC/OTBE release 2.2.1 are part of the OpenTouch Suite for MLE H2 2016 offer that is
commercially available from November 28th 2016.
Release 2.2.1 is a minor release. Upgrade from a previous product release 1.x and 2.0.x is
covered by an active SPS.
Related e-flash:
EF-Phase-in-C078-EN: OpenTouch Suite for Mid and Large Enterprises H2 2016
EF-Phase-out-C077-EN: OpenTouch Suite for Mid and Large Enterprises H2 2016
ACTIS tool version 21.0 minimum for release 2.2.1

Pre-Sales
6
General information
OpenTouch Suite for MLE H2 2016 offer products release evolution
OpenTouch suite
OXER11.2.2
R11.2.2
OXE
OT-SBCR2.1.1
R2.1.1
OT-SBC
OTMSR2.2.1
R2.2.1
OTMS
All-in-one package
OTCCSE
SER10.6
R10.6(*)
(*)
OTCC
OV8770R3.1
R3.1
OV8770
OTBER2.2.1
R2.2.1
OTBE
OXER11.2.2
R11.2.2
OXE
OTMCR2.2.1
R2.2.1
OTMC
OTFCR7.6.1
R7.6.1
OTFC
(*) Availability delayed till mid December

Pre-Sales
7
OV8770R3.1
R3.1
OV8770
OTCCSE
SER10.5
R10.5
OTCC
General information
OTMS delivery modes
Hardware platform cross-compatibility
Refer to OTCP (*) tool to ensure the platform
compatibility with the actual OTMS deployment
OTMS up to 5000 users
Physical appliance server

provided by BP / customer
OTMSR2.2.1
R2.2.1
OTMS
Virtualization platform cross-compatibility

VMware ESXi/vSphere 5.5 or 6.0
Only VMware ESXi 6.0 in case of internal FlexLM topology
OTMS-V
OTMS-V up to 5000 users
OTMS
SLES 12
VMware
OTMS
software
pack
Virtualization

Pre-Sales
Operating system
Suse Linux Enterprise Server 12 SP 1
8
General information
OTMC delivery modes
compatibility with the actual OTMC deployment
New platform for pre-packaged delivery
Pre-packaged delivery
with OpenTouch Server ONE
(Lenovo X.3250 M5/6)
Lenovo X.3250 M6 (**)

Physical appliance server
provided by BP / customer
SLES 12
OTMC up to 15000 mailboxes

OTMC-V
OTMC
OTMCR2.2.1
R2.2.1
OTMC
NEW

OTMC
software
pack
VMware
Virtualization
Pre-Sales
OTMC-V up to 15000 mailboxes
Operating system
9
General information
OTBE delivery modes
OTBER2.2.1
R2.2.1
OTBE
OXER11.2.2
R11.2.2
OXE
OpenTouch Server ONE for pre-packaged delivery

Up to 1000 users and 1000 devices
OV8770R3.1
R3.1
OV8770
NEW
OTCCSE
SER10.5
R10.5
OTCC
applies also to existing OTBE installed on HP servers in case

of 100% Connection deployment, otherwise 500 users max.
New platform: Lenovo X.3250 M6 (**)

compatibility with the actual OTMC deployment

OTBE-V

OTBE-V up to 1500 users
or
Pre-packaged delivery
with OpenTouch Server ONE
(Lenovo X.3250 M5/6)
OTBE
software pack
VMware
Operating system
Virtualization
Pre-Sales
10
General information
Cross compatibility with OmniPCX Enterprise
OpenTouch R1.3
OpenTouch R2.0.x
OpenTouch R2.1.x
OpenTouch R2.2.x
OXE R9.1
OXE R10.0
OXE R10.1
OXE R10.1.1
OXE R11.0.x
(*)
OXE R11.1
(from R2.0.1)
(*)
OXE R11.2
(*)
OXE R11.2.1 / R11.2.2
OmniPCX Enterprise
(*): Supported only if OTC Software Client on PC is not deployed.

The single client OT Conversation for Connection profile, available as of OTMS R2.2, does not work with
OmniPCX Enterprise release inferior to R11.2.1. In case of OXE network, OXE R11.2.1 is required (and
enough) in front of the OTMS R2.2.x.
Extract from cross compatibility Ed30l
Pre-Sales
11
General information
Cross compatibility with OmniVista 8770
OmniVista 8770
R2.6 MD2
OmniVista 8770
R3.0
OmniVista 8770
R3.1
OmniVista 4760
R5.2.3
OTBE / OTMS / OTMC R1.x - R2.0.x R2.1.x
OTBE / OTMS / OTMC R2.2.x
OXE R6.0 to R11.1
up to R11.0.1
OXE R11.2.x
OXO R5.0 to R10.2
up to R9.1
OXO R10.3
OXO Connect R2
OpenTouch BE / MS / MC
OmniPCX Enterprise
OmniPCX Office
OmniTouch 8400 ICS (UUM only)

ICS R6.7.1 (minimum) + hotfix (*)
Pre-Sales
12
General information
Cross compatibility with hypervisors
Hypervisor
OmniPCX Enterprise
R11.2.2
OX
EV
CS
VMware
ESXi (1)
PC
SV
A4
64
5V
OX
E
M
S
OS
T6
4
6.0
5.5
5.1 (except OXE MS)
OpenTouch
OTMSV
R2.2.
1
OTBEV
R2.2.
1
6.0
5.5 (5)
OTMC
-V
R2.2.
1
Edge servers
OTFCV
R7.6.1
6.0
5.5
5.1
5.0
OTESV
R2.2.
1
6.0
5.5
OTSBC
VE
R2.1.1
6.0
(4 )
5.5
5.1
OTCC SE-V
R10.6
Management
OV877
0-V
R3.1
6.0
5.5
5.1
5.0
DAP
Confi
gurat
or-V
R170
6.0
5.5
5.1
5.0
OXE
wit
h
CC
D
CC
S
sr
v
C
C
A
sr
v
NEW
NEW
NEW
NEW
6.0
5.5
5.1
6.0
5.5
5.1
(3)
(3)
Microsoft
Hyper-V
2012
R2
2012
R2
2008
2012
2012
R2
KVM
RedHat (RHEL 6.4

64bits)
Suse (SLES 12)
(2)
(3)
Refer to MLE Cross Compatibility document to know which VMware ESXi version is compatible with a given ALE server older release
(1): Compatibility with a given VMware ESXi version also covers the updates (ie minor revision) that VMware may release on this software line
Pre-Sales
13
A
C
R
sr
v
Agenda
1.
2.
3.
4.
5.
6.
7.
8.
General information
Architecture
Messaging services
Eco-system
Devices & users

Pre-Sales
14
Architecture
Virtualization
Evolutions introduced after R2.2 GA
Officialization of topologies with internal OpenTouch FlexLM server
Requires OpenTouch R2.2 minimum and VMware ESXi 6.0
Support of Raspberry Pi 3 Model B for USB/IP dongle implementation

Requires FlexLM Virtual Machine v2.1.100.009
Retro-compatibility with OXE as of R11.1 and OpenTouch as of R2.1 MD1 (VMware ESXi 5.5 min)
Same pre-requisites as Raspberry Pi 2 model B box
Refer to OpenTouch Suite for MLE Virtualization Design Guide H2 2016 Offer for more details
Evolution brought by OpenTouch for MLE H2 2016 offer

OTMS-V configuration with OXE on physical platform
1. Quotation in one step (instead of two) as of Actis 21.0 (concerns both OTMS-V and OTMC-V)
2. OXE uses back its CPU-ID instead of FlexLM server & dongle for license control
Already installed configuration can keep the current OXE license control based on the dongle ID
Note: this is an eBuy evolution that also requires Actis 21.0

Pre-Sales
15
Architecture
OTES functions provided by Reverse Proxy (1/3)
Reminder: OTES is a front-end server allowing an external guest (or a corporate user) to join,
via OTC Web, a conference/web collaboration through a HTTPs session
OT R2.2.1 simplifies the edge infrastructure which is required for the following use cases:
Remote corporate user using the OTC client from the Internet (without VPN)
Remote guest participants to a scheduled conference configured on the OpenTouch server
The edge infrastructure is now based on industry standard components:

Reverse proxy for all data traffic (web services, data sharing), including OTES functions
OT-SBC for SIP signaling and voice media (video depending on the OTC client used)
Benefits
Standard Reverse Proxy is expected to reach better IS/IT adoption than OTES
Less operational costs, no strong dependencies between edge server and OT server as with OTES
Multi-tenancy capabilities of standard Reverse Proxy

Pre-Sales
16
Architecture
Public FQDNs
Customer premises
OTMS
OT-SBC
SIP signaling & media interface
pub-sip-services.company.com
Remote user
Internet
Reverse
Proxy
Connected users interface for remote workers

pubOT.company.com
(NGINX+)
Web collaboration interface for external guests

conference.company.com
External guest
Design rules
DMZ
OXE
Remote worker configuration: support of AAPP qualified RPs, as well as the ones compliant with OT
requirements (refer to Official statement regarding reverse proxies application note available on
BPWS)
External guest configuration: only support of AAPP qualified RPs, due to its more complex tuning
Currently, only NGINX-Plus R10 has been qualified ongoing work with BlueCoat
OTES remains available in R2.2.1 but the component will be removed in R2.3 (targeted for MLE offer H1 2017)
Refer to Solutions for remote user access OpenTouch presentation for more details

Pre-Sales
17
Architecture
New sales
ALE strongly recommends to not deploy anymore OTES to address external guest use case but instead
to consider NGINX-Plus Reverse Proxy (*)
If no other choices, OTES is still available in R2.2.1
Install base
External guest only topology
(ie only OTES is present)
OTES can be kept or may be replaced by NGINX-Plus (*)
Topology with both remote worker and external guest use cases
(ie OT-SBC, RP and OTES are present)
If the Reverse Proxy is already NGINX-Plus, integration of OTES functions requires a configuration update
If the Reverse Proxy is not NGINX-Plus,
either check with AAPP the possibility to qualify the concerned Reverse Proxy
or replace, in the edge infrastructure, the OTES by a NGINX-Plus dedicated to external guest use case
If no other choice, the OTES can be kept in R2.2.1
(*) The IWR provides complete RP configuration files samples for both remote worker and guest use cases

Pre-Sales
18
Architecture
OpenTouch networking (1/9)
Reminder: before OT R2.2.1, multi-instances OT configuration within an OXE ABC network
Up to x20 OpenTouch instances (OTMS/OTMC/OTBE) in the ABC subnet

Up to x1 OpenTouch instance associated to each OXE node
An OTMS/OTMC can be associated with up to x20 OXE nodes within the ABC subnet
Up to x20,000 OpenTouch users (Connection and/or Conversation) managed in total
Level of service
OTMS 2
Universal Directory Access via external LDAP server

Remote favorites without presence
Local attendant services
Conferencing (anonymous access for remote users)
Local Messaging services
OXE 2
OXE 3
OTMS 3
OXE 4
OXE ABC subnet

Local API Web Services
OTMC 1
Other services (IM, Presence, video) not available
OXE 1
OXE 6
Telephony services between OpenTouch users delivered via ABC network
(ABC-F2 level of service)
OXE 7

Pre-Sales
19
OXE 5
Architecture
Go beyond simple multi-instances by sharing information directly between OT servers to
provide collaboration & conferencing services between users located on different OT
Targeted topologies
Large configurations above OTMS product limits
Green field or ICS/ACS migration of large ICS systems
Medium and large distributed deployments spanning multiple sites with local autonomy required
Cross-compatibility within an OpenTouch network

Full compatibility with the next OpenTouch major release (starting from R2.2.1)
Allow upgrading progressively the OT nodes without service degradation for the users across the network
A subsequent release may add features while retaining full compatibility with the level of the
previous release.
Feature not subject to a specific license

Pre-Sales
20
Architecture
OT network name: MyOTNetwork

Some vocabulary
(from OTMS 1 standpoint)
OTMS 1
OpenTouch network
OTMS 2
OT network link
Group of OT systems linked together for service federation purposes

defined by an OT network name, shared by all OT nodes
OXE 1
OXE 2
B
OT node
An OT system configured as part of an OT network
OT local user
A Connection user hosted on OTMS 1
OXE 3
OXE 4
OXE ABC subnet

OTMS 3
D
OT remote node
Stand alone system
One of the other OT nodes within the OT network OTMS 1 belongs to

OT nodes list: list of all OT remote nodes with their FQDN and some additional technical parameters
OT remote user
A Connection user hosted on a remote node of the OT network (known by local OT thanks to inter-nodes users synchronization)

Pre-Sales
21
Architecture
Design rules
The different OT nodes have to be attached to OXE nodes located within a single OXE ABC subnetwork
Up to x6 OT nodes and up to x20,000 OpenTouch users in the OT network
Fully meshed topology between the different OpenTouch nodes
The OT may be deployed on different sites, possibly in different IP subnetworks
OpenTouch nodes can be either OTMS or OTBE, up to the maximum supported provisioning level
Deployed either on physical platform or virtualized
OpenTouch networking is supported only for a 100% Connection users population

An OT node can only belong to one OT network at a time
Reminder:
Up to 1 OpenTouch instance associated to each OXE node
An OTMS/OTMC can be associated with up to 20 OXE nodes within the ABC subnet

Pre-Sales
22
Architecture
Level of service between a local OT
user and a remote OT user:
Contact management
Search for remote OT user

Contact card (with allowed actions)
Tag remote user as favorite
PresenceBuddy presence
Non-buddy presence
IM session
IM P2P
IM session add OT participant
Document sharing (incl. annotation)
Desktop sharing
Sharing Sharing session add remote user
Invite remote OT user
Join remote audio/data conference
Join remote video conference
Scheduled conference
Management (mute, leader promo, list

users)
P2P audio conversation
Ad-hoc audio conference (3 participants)
TelephonySupervision group (incl. remote user)
Remote users in history (audio & IM
sessions)
Video (P2P, ad-hoc conference)
Video
OTC One
OTC
smartphone
(Android,
iPhone)
OTC PC
OTC MAC
n.a.
n.a.
n.a.
(viewer mode only)

n.a.
n.a.
n.a.
n.a.
n.a.
n.a.
(audio only)
(viewer mode only)
n.a.
n.a.
(audio + data only)
n.a.
n.a.
n.a.
(RCC)
n.a.
n.a.
n.a.
n.a.
n.a.
n.a.
n.a.
n.a.
n.a.
n.a.
(audio + data
only)
n.a.
n.a.
n.a.
n.a.
n.a.
n.a.
n.a.
n.a.
n.a.
Note: Audio calls remain carried though the underlying OXE ABC subnetwork, as in previous releases
Non exhaustive list of features. For a detailed information, refer to OpenTouch Feature List and System Documentation
Pre-Sales
OTC Web
23
Architecture
OT networking link
OpenTouch network link
Proprietary protocol
based on SIP over TCP
(443)protocol over TCP (5672)
Binary
Secured
with TLS
Functional link (IM& presence federation)basedonACSremotesitecapabilities

Information flow between nodes is driven by events as they occur (status provided via ACS WBM)
Configuration link for user directory exchanges and general network management
Dialog subject to periodic synchronization
OpenTouch network monitoring CLI tool (netstatus)
Fully meshed connectivity between the different nodes of an OpenTouch network

Links secured, based on TLS v1.2
Certificates of all OT nodes must share the same trusted CA
Users directory
All OT users are shared between OT nodes of a network
Each node tries to connect to remote nodes to upload their users in its local database
only limited set of remote user attributes (including photo) are transferred across the network
User attributes expected to be unique within the network: login name, directory number & e-mail address

Pre-Sales
24
Architecture
Synchronization
Synchronization between two OT nodes shall occur on a regular basis
The time interval between synchronizations is adjustable (1 hour by default)
OT Node change log: list of changes since the last synchronization
Synchronization time depends on the number of users to be synchronized (average sync rate: 70 users/min)
Before synchronization, checks between OT nodes

ACS Node ID, ACS cluster FQDN and OT stack name technical parameters of each OT nodes must be unique
All OT nodes must have the same OT network name and the same conference access code format (1 or 2 digits)
If immediate propagation is required, the administrator can force the synchronization

CLI command, netsync, on a given OT node: synchronization launched with each remote note
Events triggering a synchronization:
Full synchronization
Partial synchronization
New OpenTouch node added
Scheduled synchronization
Requested changes no more in the change

log
Upon OpenTouch node startup

Forced synchronization

Pre-Sales
25
Architecture
Functional restrictions
Conversation users are not supported in an OpenTouch network
OpenTouch native High Availability is not supported
VMware HA service can be used instead
A local Connection user joining a scheduled conference configured on a remote OT node is connected
with audio + data only, without video media
Connection users belong to an OT supervision group must be declared on the same OT node
No integration with Skype for Business / Sametime
No need for OT networking when collaboration services are provided by Microsoft / IBM
Maintenance operations
No direct rehosting: remove first the OT node from the network before performing the rehosting
Backup & restore: ALE recommends to force full synchronization before launching the backup
Moving a user on another node implies a user deletion/re-creation: all the user settings are lost
Pre-Sales
26
Architecture
Design rules for remote corporate user / external guest user:
One OT-SBC instance and NGINX+ Reverse Proxy instance can support several OXE/OTMS systems
Leverage this capability when replacing OTES by Reverse Proxy
If OTES is considered instead, one OTES instance is required per OpenTouch node
Customer premises
OTMS 1
OXE 1
OT-SBC
Remote user
(with OTC client
or OTC Web
Internet
OXE 2
Reverse
Proxy
(NGINX+)
External guest
(with OTC Web)
OTMS 2
DMZ

Pre-Sales
OT network
27
OXE 3
OXE ABC subnet
Topology
example without
OTES
Architecture
OpenTouch redundancy over extended L2 network (1/3)
OT native HA feature between two different locations interconnected by a layer 2 link
In previous product releases, both OpenTouch servers had to be deployed on the same physical location
Split-brain resolution is addressed through the notion of preferred OpenTouch server
Upon network recovery, the preferred server remains active
OpenTouch services on the other server are restarted with standby role and replication is resumed
Configuration & user preferences are replaced by the ones on the preferred server
New voicemails are lost but scheduled conferences are kept
Preferred:
Active OT
Preferred:
L2 subnet
Active OT
Active OT
Network
recovery

Pre-Sales
28
L2 subnet
replication
Standby OT
Architecture
Split-brain resolution is not synchronized between OT and OXE systems
L2 subnet
Reminder on OXE algorithm:

1.
2.
3.
4.
Call
Call
Call
Call
Server
Server
Server
Server
connected to reference IP Media Gateway

with the preferred CS IP address
with the highest number of links with IPMGs
with the highest IP address
Standby OT
Active OT
replication
replication
Depending on the configuration, main OXE CS and active

OT server may end up on different data centers
Main OXE CS
Standby OXE CS
ALE recommends to manage accordingly both split-brain resolution mechanisms

Pre-Sales
29
Architecture
Infrastructure pre-requisites between both data centers
Maximum authorized network latency
Max round-trip delay time as a function of the number of users
Required network bandwidth for OpenTouch replication

Provided by OpenTouch Capacity Planning (OTCP) v2.2.1 tool
Underlying network topology

Must guarantee transparent mechanism of floating IP addresses that relies on gratuitous ARP
Both sites must be interconnected with a layer 2 link
Configuration of different default gateways for Primary and Secondary is not yet supported
Routers on both locations must be configured with a common virtual IP address (via VRRP or a similar networking protocol)
Recommendation to limit the effects of split-brain

Network routing configured so as to avoid inter Data Center link failure results in user traffic split, if possible

Pre-Sales
30
Agenda
1.
2.
3.
4.
5.
6.
7.
8.
General information
Architecture
Messaging services
Eco-system
Devices & users

Pre-Sales
31
Messaging services
OpenTouch Voice Messaging Mobile Client
Available on Android Smartphone
Official name: OTMC Android smartphone
Target: mobile users with only OT messaging services (OTMS, OTMC, OTBE)
Visual voicemail message consultation and management
GUI for personal greeting management (recording / activation)
Included in the user license (OTMC) or in the messaging option (OTMS)
Simplified deployment: For remote users, edge infrastructure requires Reverse Proxy only (no SBC)
Automated Attendant statistics

Historical report on how many calls are distributed through the trees and branches
Increases knowledge of incoming traffic
Essential feedback for administrators to analyze whether call flow is well designed and implemented

Pre-Sales
32
Messaging services
Graphical User Interface Improvements Password Management
In addition to TUI, voice mail passwords can be changed from connection desk phone GUI (*)
Visual voicemail
Full voicemail GUI on
NOE deskphones (*)
Message listening
Message
rewind/advance/pause
Greetings (incl. name)

management
Security Enhancements
NEW
Password
management
New and improved security options to increase user and administrator
acceptance
and therefore
enhance security itself
Refer to OpenTouch Message Center Design and Quotation Guide presentation for more details

Pre-Sales
33
Agenda
1.
2.
3.
4.
5.
6.
7.
8.
General information
Architecture
Messaging services
Eco-system
Devices & users

Pre-Sales
34

OpenTouch supervision and call pick-up groups for Connection users (1/2)
Provide to Connection users the same feature introduced in R1.2 for Conversation users
On supervisor side, it is available only on OTC PC client (MAC included) and NOT on OXE deskphones
But a supervisor with an OTC PC client can supervise OXE deskphones
No link with OXE supervision feature (no management synchronization)

OT supervision group is defined in OpenTouch management and monitored via OpenTouch services
Possibility to manage both features accordingly
OXE deskphone (NOE)
Supervised users
(REX)
OXE supervision
feature (supervision
keys)
Analog
NOE
OTC clients
Design rules:
(SIP integrated)
Supervisor
OT supervision group
(GUI on OTC PC)
OTC clients
Mixing Connection and Conversation users in an OT supervision group is not allowed

Group members may be declared on different OXE nodes but must be attached to the same OT node

Pre-Sales
35

OpenTouch supervision and call pick-up groups for Connection users (2/2)
OXE feature
Interaction with OT supervision and call pick-up group feature
Manager/assistant
if the assistant is a supervised member of an OT group, filtered calls are taken into account
Forwarding
User with different

directory numbers
Only the main phone number of a supervised user is monitored. Calls to a secondary line with a
different directory number are not supervised.
Twinset
The secondary set of a supervised user is also supervised (even if the caller calls directly the
secondary set directory number and not the main one).
Overflow
a call overflow to a supervised user is monitored.

a supervised user can have overflow rules and they are followed by the monitoring.
Pick-up
An incoming call, notified through OT group supervision, can be picked-up by an OXE user not linked
to the OT supervision group. In this case, the call must disappear from the OT groups supervisor(s)
GUI.

Pre-Sales
The OXE routing is prior to the OT supervision group feature:

- Incoming calls to a supervised member, with an immediate forward to a non supervised
destination, are not monitored by OT supervision group.
- Incoming calls to a supervised member, with a busy or no response forward, follows this
routing and could be no more monitored by OT supervision group.
An incoming call forwarded to a supervised member is taken into account by OT supervision
group, except if the supervision on final mode is not activated.
Pick-up service is not modified by forwarding state of the supervisor.
36

Document sharing enhancement
NEW
Support of laser pointer on OTC PC
Already supported on OTC Web since release R2.0
Pointer color and

thickness

Pre-Sales
37
Agenda
1.
2.
3.
4.
5.
6.
7.
8.
General information
Architecture
Messaging services
Eco-system
Devices & users

Pre-Sales
38

Callback request enhancement
Callback request button on OTC PC (Connection profile)
Callback request on no reply: already available in R2.2
Callback request on busy
NEW
Request available in SIP softphone, RCC and nomadic modes
Reminder: callback notification on OTC PC
In the History tab, this red badge is

associated to a contact card of the
person that has requested the callback
Ask for a callback when

calling party does not answer
calling party is busy
Note: no timestamp for callback request

Pre-Sales
Conversation history with the callback

requestor
39

Support of OXE Desk Sharing
OTC PC client is now fully compatible with OXE Desk Sharing feature
From OTC PC, the Connection user can remotely release the deskphone he is logged on
Optimize the shared deskphones availability
Remote release of the DSS
Desk Sharing
Set (DSS)
User away from office

(home, business trip,
)
The Connection user is able to switch to nomadic mode without being logged on a deskphone
Audio on either the PC (nomadic VoIP) or on another device (such as home phone, cellular, )
Note: the Desk Sharing set must be released before switching to nomadic mode
No deskphone is frozen optimize the shared deskphones availability

Not available on OTC Mac
OpenTouch R2.2.1 Overview Not
Ed01available with remote worker, unless VPN connectivity
is used
40
Pre-Sales
Agenda
1.
2.
3.
4.
5.
6.
7.
8.
General information
Architecture
Messaging services
Eco-system
Devices & users

Pre-Sales
41
Eco-system
OTC PC client in VDI environment
(*) VMware release 6.x doesnt support the client release 5
Refer to OpenTouch clients in VDI environment pre-sales presentation for more details
Support of Microsoft Exchange 2016

Pre-Sales
42
Agenda
1.
2.
3.
4.
5.
6.
7.
8.
General information
Architecture
Messaging services
Eco-system
Devices & users

Pre-Sales
43
Devices & users

OTC PC client
Ergonomics evolutions
1. New search
Including search results display
Switch between local

(favorites, Outlook
contacts) and directory
search
2. Dual ring indicator

3. Use of right-click
In any window (history, favorites, conference creation, visual voicemail )
4. Multiple e-mail addresses choice

5. OTC PC connection status in Outlook add-in
Support of AEC (Acoustic Echo Canceler)

Functional evolutions (already covered in previous slides)
. Supervision and call pick-up groups for Connection users, GUI for callback request on busy, Support of OXE Desk
Sharing feature, Application sharing, Support of laser pointer (document sharing), VDI
Pre-Sales
44
Devices & users

8001G deskphone for Conversation user
New hardware edition providing gigabit connectivity
Country dependent availability (refer to Country Saleable Solutions List document)
Status on OTC iPhone and OTC iPad

These clients are not fully compatible with iOS10
Issues occur on incoming applicative events when the software client is in sleeping mode only
No IM, notification (missed calls or new voice message deposit), update on routing profile modification
Incoming VoIP (Conversation profile only) and cellular calls are still correctly managed
OTC mobile users shall be warned not to upgrade their iPhone/iPad device in iOS10
Correction in progress, to be released in a next-coming client software version

Pay attention that this evolution will only be valid for iPhone software client

Pre-Sales
45
Devices & users

Mass Provisioning import/export enhancement
Achieve the same level of easiness as in OXE configuration
Configuration application
Easier exported template file: no hidden attributes, format help (mandatory tag, default value ), localized file (txt, csv)
Import a file with the minimum of attributes

Possibility to combine different actions (create/modify/delete) on different objects in the same import file
Users application (Unified User Management)

Offline creation of an import file with just the attributes to modify
Export a user as a template
Attributes to fill in Attributes automatically filled by the meta-profile
Attributes automatically copied from exported user

Pre-Sales
46
Agenda
1.
2.
3.
4.
5.
6.
7.
8.
General information
Architecture
Messaging services
Eco-system
Devices & users

Pre-Sales
47
Reference Documents
Available on Business Portal by MLE offer General Availability date
(https://businessportal2.alcatel-lucent.com/)
Pre-Sales presentations / guidance :

Solutions for remote user access OpenTouch
OpenTouch architecture and network design principles
OpenTouch high availability for Connection users
Updated for OpenTouch R2.2.1

OpenTouch clients in VDI environment

New document for OpenTouch R2.2.1
OpenTouch Message Center Design and Quotation Guide
OpenTouch Suite for MLE Virtualization Design Guide
Updated for H2 2016 Offer
OpenTouch Suite for MLE in virtualized environment overview
OpenTouch Suite for MLE security design guide
How To Quote Starter for OTBE
How To Quote Starter for OTMS
OmniVista 8770 NMS Global Presentation

Pre-Sales

Updated for OmniVista R3.1
48
Reference Documents
Complementary product information
OpenTouch R2.2.1 Release Presentations
OpenTouch BE/MS/MC R2.2.1 Feature List & Provisioning Level
OmniPCX Enterprise R11.2.2 Feature List & Provisioning Level
Cross Compatibility
Release Policy
OTC PC R2.2.1 for Connection user profile Product Presentation
Official statement regarding reverse proxies application note
E-flash related to MLE H2 2016 offer
EF-Phase-in-C078-EN, EF-Phase-out-C077-EN
Technical Documentation Library

OpenTouch Release 2.2.1 Technical Documentation
TC2244 Release note for OpenTouch Release 2.2.1

Pre-Sales
49
Follow us on:
Twitter.com/ALUEnterprise
Facebook.com/ALUEnterprise
Youtube.com/user/enterpriseALU
Linkedin.com Group: Alcatel-Lucent Enterprise
Slideshare.net/tagged/Enterprise
Storify.com/ALUEnterprise

Pre-Sales
enterprise.alcatel-lucent.com

Pre-Sales
OpenTouch Server ONE

Lenovo X.3250 M6
Main characteristics: of X.3250 M6 :

1 * Xeon e3-1230 v5,
24 GB RAM,
2 * 1 TB SATA HDD,
Server RAID M5200
2 * gigabit Ethernet ports
mono 300W power supply

Pre-Sales
52

TBE046 OpenTouch R2.2.1 Overview Ed01

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

TBE046 OpenTouch R2.2.1 Overview Ed01

Uploaded by

Copyright:

Available Formats

OpenTouch R2.2.

With speaker notes

COPYRIGHT 2016 ALE International. ALL RIGHTS RESERVED.

OpenTouch R2.2.1 Overview Ed01

Complementary information related to some of the evolutions is provided in other presales

OpenTouch R2.2.1 Overview Ed01

OpenTouch R2.2.1 at a glance

OpenTouch voice messaging mobile client

OTES functions provided by Reverse Proxy

Graphical password management from NOE deskphones

OpenTouch redundancy over extended L2 network

Automated Attendant traffic statistics

Support of TLS v1.2 (*)

COLLABORATION & GROUPWARE SERVICES

OXE TELEPHONY INTEGRATION

OT Supervision & call pick-up groups for Connection users

Callback request on busy

Laser pointer (document sharing)

Support of OXE Desk Sharing feature

DEVICES & USERS

OTC PC ergonomic enhancements

Microsoft Exchange 2016 support

Support of AEC on OTC PC

OpenTouch R2.2.1 Overview Ed01

OpenTouch R2.2.1 Overview Ed01

ACTIS tool version 21.0 minimum for release 2.2.1

OpenTouch R2.2.1 Overview Ed01

Physical appliance server

Virtualization platform cross-compatibility

OTMS-V up to 5000 users

OpenTouch R2.2.1 Overview Ed01

Lenovo X.3250 M6 (**)

OTMC up to 15000 mailboxes

Virtualization platform cross-compatibility

Only VMware ESXi 6.0 in case of internal FlexLM topology

OTMC-V up to 15000 mailboxes

OpenTouch Server ONE for pre-packaged delivery

applies also to existing OTBE installed on HP servers in case

New platform: Lenovo X.3250 M6 (**)

Refer to OTCP (*) tool to ensure the platform

Virtualization platform cross-compatibility

VMware ESXi/vSphere 5.5 or 6.0

OTBE-V up to 1500 users

OXE R11.2.1 / R11.2.2

(*): Supported only if OTC Software Client on PC is not deployed.

OTBE / OTMS / OTMC R1.x - R2.0.x R2.1.x

OTBE / OTMS / OTMC R2.2.x

OXE R6.0 to R11.1

OXO R5.0 to R10.2

OmniTouch 8400 ICS (UUM only)

RedHat (RHEL 6.4

OpenTouch R2.2.1 Overview Ed01

Support of Raspberry Pi 3 Model B for USB/IP dongle implementation

Evolution brought by OpenTouch for MLE H2 2016 offer

Note: this is an eBuy evolution that also requires Actis 21.0

OpenTouch R2.2.1 Overview Ed01

The edge infrastructure is now based on industry standard components:

OpenTouch R2.2.1 Overview Ed01

Connected users interface for remote workers

Web collaboration interface for external guests

OpenTouch R2.2.1 Overview Ed01

(ie only OTES is present)

OTES can be kept or may be replaced by NGINX-Plus (*)