OpenTouch Suite for MLE

OpenTouch
Software Release 2.5 Overview

The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE.
Lesson Summary

Cross compatibility

Phase-out

Telephony services enhancements

OTC iPhone+ enhancements

 Cross compatibility
&
Phase-out

The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE.
Cross compatibility

OmniPCX Enterprise supported software releases

OpenTouch OpenTouch Opentouch Opentouch Opentouch Opentouch

OmniPCX Enterprise
R2.2 R2.2.1 R2.3 R2.3.1 R2.4 R2.5

OXE R11.0.x  (R11.0.1 mini.)     

OXE R11.2.x  (*)  (*)  (*)  (R11.2.2 mini.)  

OXE R12.0 and 12.1      

OXE R12.2   (**)    

OXE R12.3      

(*): Please note that OTC PC application for Connection user profiles does not work with OmniPCX Enterprise software releases lower than Release 11.2.1
Therefore, OTC PC application cannot be deployed with OXE Release 11.0, and, only with R11.2
OXE R11.2.1 or higher is required, and will be enough in front of the OTMS, when the OTC PC application is deployed in an OXE network.
Refer to latest edition of Technical Communication TC1782 to find the correct software patch version required
(**) An exception when OXE is deployed on a Generic appliance Server with Oxe R12.2,  the associated OpenTouch must use a minimum of R2.3
Cross compatibility

OmniVista 8770 supported software releases

OpenTouch OpenTouch OpenTouch OpenTouch OpenTouch OpenTouch

OmniVista 8770
R2.2 R2.2.1 R2.3 R2.3.1 R2.4 R2.5

OmniVista 8770 R3.2      

OmniVista 8770 R3.2.8      

OmniVista 8770 R4.0      

OmniVista 8770 R4.1      

Cross compatibility

Supported hypervisours

Hypervisor OTMS-V R2.5 OTMC-V R2.5 OT-SBC VE R2.3

6.7 6.5
VMware
6.5 6.0
ESXi (1) 6.0 5.5

Microsoft 2016
2016
Hyper-V v1 2012 R2

KVM provided by Linux version 2.6.32 or

KVM  later

 OpenTouch 2.5 is compatible with Microsoft Hyper-V virtualization - generation 1

Note:
VMware has stopped the General Support of vSphere / ESXi Release 5.5
Refer to the MLE Cross Compatibility document, to discover which VMware ESXi versions are compatible with a given ALE server, and also discover older VMware ESXi
release version Compatibility. This also includes minor revision the updates that VMware may release on different software lines
Cross compatibility

Supported Eco-system versions

 OpenTouch R2.5 supports Microsoft Office 2019 for:

 Outlook messaging add-in

 Contact synchronization

 Office suite integration with Outlook, Word, Excel, sharepoint

 Exchange server 2019 is also supported for:

 Unified messaging

 Calendar synchronization

 Calendar presence
Cross compatibility

Supported Eco-system versions

Office support

Outlook messaging add-ins From OT 2.1.1 From OT 2.1.1 From OT 2.1.1 From OT 2.5 (1)

Outlook Contact
From OT 2.1.1 From OT 2.1.1 From OT 2.1.1 From OT 2.5 (1)
Synchronization

Office Integration From OT 2.2 From OT 2.2 From OT 2.2 From OT 2.5 (1)

(1) Office 365 is supported with Office desktop applications only

Exchange support

Unify Messaging From OT 2.1.1 From OT 2.1.1 From OT 2.2.1 From OT 2.5 From OT 2.2
Calendar Synchro &
From OT 2.1.1 From OT 2.1.1 From OT 2.2.1 From OT 2.5 From OT 2.2
Presence
Cross compatibility

Smartphones

 OTC iphone+

iPhone 6, 6 Plus iPhone 7 iPhone 8 iPhone XS, XR

iPhone 5s iPhone SE iPhone X
6s,6s Plus 7 Plus 8 Plus XS max

OpenTouch R2.4 V V V V V V X

OpenTouch R2.5 V V V V V V V

 OTC Android

Android 5 Android 6 Android 7 Android 8 Android 9

Android 4.X
Lollipop Marshmallow Nougat Oreo Pie

OpenTouch R2.4 V V V V V X

OpenTouch R2.5 X V V V V V
Phase-out
Add-on policy < R2.2.x R2.2.x R2.3.x R2.4

OTBE
New Sales No No No No

 No more new OTBE sales Add-on Full (Add-on Light +

No No No Yes
Cabinets, Shelves)
Add-on Light (Boards,
No Yes Yes Yes
Software licenses)

OTBE End of Active Support End of Limited Support

OTBE 2.3.x April 2019 April 2020

OTBE 2.4 April 2020 April 2021

OTBE 2.5 October 2020 October 2023

 Migration to OpenTouch Suite for MLE (OTMS)

OXE R12.2 OXE R12.3 OV8770 R4.1 OTMS 2.5

OTBE <= R 2.2 Major upgrade Major upgrade Free Free

OTBE R2.3 Minor upgrade Minor upgrade Free Free
OTBE R2.4 Free Free Free Free
Phase-out

 OTMC

 No more sales with physical server provided  OTMC Android mobile client phase-out
OTMC with Appliance  Not supported anymore

server provided by ALE  Removed from Google Play Store

 No more compliance with the new Google Policy on permission

OTMC

Phase-out Suse Linux

OTMC Software Virtualized OTMC Do not confuse

OTMC Android client
with
OTMC OTMC-V OTC Android client
Suse Linux Suse Linux OTC Android client
Hypervisor is still available

Available
Phase-out

Embedded Automated Attendant

OpenTouch 2.5
 No more new sales with embedded AA for OTMS and OTMC April 2019

 Embedded AA is replaced by VAA (Visual Automated Attendant)

 Add-on to existing systems are possible First sale : Authorized Pre Phase-out
Add-on sale : Authorized First sale : Not authorized
Add-on sale : Authorized

 VAA delivery options:

VAA Software Virtualized VAA

VAA-V
Physical server for
VAA
OTMC is not provided
Suse Linux Suse Linux by ALE
Hypervisor
Phase-out

Embedded Automated Attendant

 It is possible, and it is recommended, to migrate the embedded AA to standalone VAA (Visual Automated Attendant)

 Migration is based on AA database backup and restore the backup to VAA server

 Data base schema update is performed during VAA start-up phase

 Embedded AA and VAA can coexist during the transition period:

 Both solutions can be used at the same time with different routing numbers

Backup OT AA Export OT AA
Modify Routing
database and prompts and
numbers on OXE
restore to VAA import them to VAA
 Telephony services enhancements

The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE.
Telephony services enhancements

Mute/unmute NOE deskphone OTC PC/MAC OTC PC One OTC IPhone OTC Android Skype for Business Sametime
Smartphone Integration Integration

 From OTC clients Yes No Yes Yes Yes Yes

 For multi-device configuration

 Purpose: Mute office phone when outside office

 Even when deskphone is muted:

Incoming call
Incoming call notification
notification
 Calls are presented to deskphone
Incoming call
notification
 Calls can be answered on

Muted NOE SEPLOS REX

deskphone SIP
Call
Main Secondary Secondary
Telephony services enhancements

Routing profile management

 Possibility to save/select specific routing configurations (profiles notion) from:

OTC PC/MAC OTC PC One OTC IPhone OTC Android Skype for Business Sametime Integration
Smartphone Integration
Yes No Yes Yes Yes Yes

 Profiles contain the following information:

 Routing: Select a existing
 « Dial from » device profile -> predefined
 Desk phone muted or not routing/forwarding
 List of devices to « Receive my calls on » configuration
 Other number configuration
Or
 Forwarding
 Voice mail or other number
 Condition (immediate, no answer, …)
Save current
configuration to
 Restriction:
a profile
 Profiles saved locally, not on OT server:
 No syncrhronisation between OTC clients
 Example: PC/mobile or 2 PCs
Telephony services enhancements

Force answer on deskphone from OTC PC

 Purpose: Answer on deskphone from OTC PC

in multi-device configuration with deskphone + softphone

Parameter validated:
Incoming calls answered from OTC PC toast
are established on desk phone

SEPLOS Parameter not validated:

Call Incoming calls answered from OTC PC toast
Main Secondary are established on OTC PC with Voice Over IP

 Available for:

OTC PC/MAC OTC PC One OTC IPhone OTC Android Skype for Business Sametime Integration
Smartphone Integration
Yes NA NA NA Yes Yes
Telephony services enhancements

Programmable keys on OTC PC

 Up to 30 programmable keys on OTC PC

OTC PC/MAC OTC PC One OTC IPhone OTC Android Skype for Business Sametime Integration
Smartphone Integration
Yes Yes No No Yes Yes

 No modification or transformation done by OT and dialing rules are not applied

 Possibility to use OXE prefixes (with or without overlapping)

 No control of the number called is performed by OpenTouch, if the call is successful or not
Telephony services enhancements

 Contacts

 Display name field for contacts created manually  Contact list can be importated

 Display name instead of first name and last name  Import several contacts in one step

 For new contact creation and modification of pre-existing contacts  csv file: 100 contacts max per list

 These two features are available on:

OTC PC/MAC OTC PC One OTC IPhone OTC Android Skype for Business Sametime Integration
Smartphone Integration
Yes Yes No No No No
Telephony services enhancements

Supervision

 Possibility to customize ringtone for supervision calls

 Available for people part of OpenTouch supervision group

 Feature available with:

OTC PC/MAC OTC PC One OTC IPhone OTC Android Skype for Business Sametime Integration
Smartphone Integration
Yes No No No Yes Yes
Telephony services enhancements

Professional mobile privacy

 Possibility to hide the professional mobile number displayed on OTC clients:

OTC PC/MAC OTC PC One OTC IPhone OTC Android Skype for Business Sametime Integration
Smartphone Integration
Yes Yes Yes Yes Yes Yes

 Managed by the administrator:

 Parameter at the user level

Privacy checked:
Privacy unchecked: Mobile number not
Mobile number available on displayed on contact card
contact card

 Restriction:
 If the mobile number was displayed before, because privacy parameter was not set or did not exist. Then this information might be
saved in the cache memory of different OTC clients, and, will continue to be displayed, even if « professional mobile privacy »
parameter is now checked
Telephony services enhancements

Display CCD information on OTC PC client

CCD OXE builds a ‘CCD display name’
Contact Center call distribution depending on agent group configuration.

CCD Display name

Incoming call toast

Pro-ACD/Agent set OTC PC Call history

Agent activity
 OTC iPhone+ enhancement

The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE.
OTC iPhone+ enhancement

CallKit features use enhancements

Answer Answer Answer Make an

Incoming an incoming an incoming OpenTouch
OpenTouch OpenTouch GSM call when call from
VoIP call by VoIP call already in an the IOS
sliding when already OpenTouch Contact
lock screen in a GSM call VoIP call application

OpenTouch
R2.3.1 R2.4 V V V X
OpenTouch
R2.5 V V V V

Note:
CallKit is a framework to allow application integration with the native Phone User Interface, to improve the VoIP
experience.
OTC iPhone+ application uses CallKit.
OTC iPhone+ enhancement

CallKit features use enhancement

 New features description:

Enable “Native call A list of applications appears after The ability to call via OTC + Calls are launched via OTC+ after Calls made using OTC+ are
integration” in the OTC+ a long press on the phone icon, appears on the main contact clicking on OTC+ marked as “OpenTouch+ Audio” in
settings including OTC + screen after the first call to the native iPhone call history
contact
OTC iPhone+ enhancement

VoIP everywhere

 Up to now with OTC iPhone+ and OpenTouch R2.3.1 & R2.4:

APNS
OXE OT
 Use of UDP on LAN -> possibility for OXE to repeat SIP invite messages
until OTC iPhone+ application wake up by APNS Suspended

SIP Invite
ignored

csta
callCreated

SIP Invite
ignored
callCreated

Wake-up
SIP Invite

200 OK Answer
call

 Restriction* for VoIP with OTC iPhone+ application when

outside the company (behind OT SBC) and in background mode: * Restriction only in WAN:
On LAN UDP is used so, OXE can repeat SIP messages
 Incoming calls always presented in cellular mode On WAN, TCP used and not UDP -> not possible to repeat
SIP messages
OTC iPhone+ enhancement

VoIP everywhere

 Problem

 Solution

 OpenTouch server will act as a SIP proxy

and will « store » SIP invite until REGISTER
from OTC client after wake-up
OTC iPhone+ enhancement

VoIP everywhere

 Architecture: 2 new componants

 kamailio-wasp: SIP proxy between SBC and OXE

 wspcfg: service to provide configuration for kamailio

OTC iPhone+ enhancement

VoIP everywhere

 Configuration

 OpenTouch server

 New SBC (used for OTC iPhone devices)

 Same FQDN as OT SBC

 Port 5265

 OT SBC

 Additionnal SIP interface

as to be declared for iPhone users

 Port 5265
OTC iPhone+ enhancement

 VoIP everywhere

 Maintenance

 Kamailio service  Wspcfg service

 service kamailio-wasp status|start|stop|restart  service wspcfgd status|start|stop|restart

 location: /var/log/localmessages  location: /logs/wspcfg/wspcfg.log

 change log level:  change log level:

 /usr/kamailio-wasp/loglevel.sh {level}  loglevel.sh component=wspcfg logger=* level={LEVEL}

{level}: 3=DBG, 2=INFO, 1=NOTICE, 0=WARN, -1=ERR Example: loglevel.sh component=wspcfg logger=* level=debug

Note: Logzipper includes kamailio and wspcfg logs

 Thank you for your attention

The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE.