OpenTouch Business Edition enterprise/ale... · 2017. 11. 14. · OpenTouch Business Edition OTBE...

OpenTouch Business Edition

OTBE Installation Manual on a PhysicalMachineRelease 2.3 - June 2017

8AL90504USAH Ed. 01

Legal noticeThe information presented is subject to change without notice.

ALE International assumes no responsibility for inaccuracies contained herein.

Copyright © ALE International, 2017

DisclaimerWhile efforts were made to verify the completeness and accuracy of the information contained in thisdocumentation, this document is provided “as is”. To get more accurate content concerning CrossCompatibilities, Product Limits, Software Policy and Feature Lists, please refer to the accuratedocuments published on the Business Partner Web Site.

In the interest of continued product development, ALE International reserves the right to makeimprovements to this documentation and the products it describes at any time, without notice orobligation.

The CE mark indicates that this product conforms to the following Council Directives:

• 2014/53/EU for radio equipment• 2014/35/EU and 2014/30/EU for non radio equipment (including wired Telecom Terminal

Equipment)• 2014/34/EU for ATEX equipment• 2011/65/EU (RoHS)

Chapter 1About this document

1.1 About this document..............................................................................................................13

Chapter 2Reference documents

Chapter 3Quick Start

3.1 Installation Manual................................................................................................................... 18

Chapter 4Product Overview

4.1 Overview.............................................................................................................................................204.1.1 OpenTouch Business Edition on a physical machine....................................................... 20

Chapter 5Installation Overview

5.1 Overview.............................................................................................................................................225.1.1 Installation from scratch...................................................................................................................22

Table ofcontents OTBE Installation Manual on a

Physical Machine

8AL90504USAH - Ed. 01 - June 2017 - OTBE Installation Manual on a Physical Machine 3/241

5.1.2 Factory installation..............................................................................................................................22

5.2 OpenTouch Business Edition delivery................................................................. 235.2.1 Licenses...................................................................................................................................................23

Chapter 6Hardware Installation

6.1 Hardware installation.............................................................................................................25

Chapter 7Software Installation on physical machines

7.1 Overview.............................................................................................................................................27

7.2 Information required...............................................................................................................27

7.3 BIOS configuration...................................................................................................................277.3.1 HP Server (for servers: HP DL120 G7, DL 380 G8 and HP DL180 G9):................277.3.2 Lenovo System x3250 M6.............................................................................................................. 287.3.3 Verification.............................................................................................................................................. 28

7.4 Installation from the network......................................................................................... 287.4.1 Prerequisites..........................................................................................................................................297.4.2 OpenTouch installation overview.................................................................................................307.4.3 Configuring the network...................................................................................................................317.4.4 Specifying IP addresses and hostnames................................................................................327.4.5 Specifying installation files..............................................................................................................327.4.6 Verifying the integrity of installation files..................................................................................347.4.7 Saving configuration.......................................................................................................................... 357.4.8 Booting the target machine from the network....................................................................... 36

7.5 Installation from DVDs..........................................................................................................377.5.1 SUSE Linux Enterprise Server installation.............................................................................37


Physical Machine


7.5.2 OpenTouch Business Edition server pre-configuration.................................................... 387.5.3 OpenTouch Business Edition software installation.............................................................38

Chapter 8Post Installation

8.1 Post installation overview.................................................................................................44

8.2 OpenTouch Business Edition server post installation......................... 45

8.3 OmniVista 8770 additional installation.................................................................728.3.1 Accessing the vmManagement (first connection)............................................................... 728.3.2 Activating Windows............................................................................................................................738.3.3 Installing the OmniVista 8770 license manually.................................................................. 738.3.4 Accessing the OmniVista 8770 client (first connection)...................................................75

8.4 Manual installation of licenses.....................................................................................758.4.1 OpenTouch Business Edition license file installation........................................................ 758.4.2 OmniPCX Enterprise license installation.................................................................................768.4.3 OmniVista 8770 license file............................................................................................................77

8.5 OpenTouch Certificate management......................................................................778.5.1 Network security enabled................................................................................................................778.5.2 Network security disabled...............................................................................................................77

8.6 Hotfix installation.......................................................................................................................77

8.7 UPS..........................................................................................................................................................77

Chapter 9Updating settings on an operational system

9.1 Prerequisites.................................................................................................................................. 799.1.1 Checking the system version........................................................................................................ 799.1.2 Checking the license......................................................................................................................... 80


Physical Machine


9.1.3 Checking the service.........................................................................................................................809.1.4 Estimated time......................................................................................................................................819.1.5 Backup......................................................................................................................................................81

9.2 Rehosting infrastructure.................................................................................................... 819.2.1 Starting the rehosting........................................................................................................................819.2.2 Rehosting the OpenTouch infrastructure.................................................................................839.2.3 Rehosting the OmniPCX Enterprise.......................................................................................... 839.2.4 Rehosting the OXE-MS virtual machine.................................................................................. 869.2.5 Rehosting the OmniVista 8770 application virtual machine...........................................879.2.6 Rehosting the Advanced Communication Server............................................................... 88

9.3 Rehosting the Domain Name Server (DNS)..................................................... 90

9.4 Externalization of the Flex server..............................................................................91

9.5 Modification of the Network Time Protocol (NTP).....................................92

Chapter 10Connection Configuration

10.1 OmniVista 8770 connection.............................................................................................94

10.2 Firewall.................................................................................................................................................94

10.3 OmniPCX Enterprise configuration for SIP connections................... 9510.3.1 Required information.........................................................................................................................9510.3.2 Trunk group for the SIP gateway.................................................................................................9510.3.3 Set the trunk group local properties...........................................................................................9610.3.4 SIP gateway configuration..............................................................................................................9610.3.5 SIP proxy configuration....................................................................................................................9710.3.6 SIP registrar configuration.............................................................................................................. 9710.3.7 SIP external gateway configuration........................................................................................... 9710.3.8 Configuring SIP video settings................................................................................................... 10210.3.9 Trusted address configuration.................................................................................................... 10210.3.10 Codec configuration.........................................................................................................................10210.3.11 DPNSS prefix configuration......................................................................................................... 103

10.4 OXE-MS configuration on the OmniPCX Enterprise............................. 104


Physical Machine


10.4.1 Checking parameters on OXE-MS...........................................................................................10410.4.2 OXE-MS declaration........................................................................................................................10410.4.3 OXE-MS parameter configuration.............................................................................................10410.4.4 OXE-MS Ethernet (MAC) address configuration...............................................................105

Chapter 11OpenTouch Multimedia Conferencing and Collaboration

11.1 Overview...........................................................................................................................................10611.1.1 Required information ......................................................................................................................10611.1.2 Process overview..............................................................................................................................10611.1.3 Declaring the ACS in the OmniPCX Enterprise................................................................. 10611.1.4 Declaring the ACS in the OpenTouch server...................................................................... 10711.1.5 Configuring the ACS settings......................................................................................................107

11.2 Installing a Document Converter Software.................................................... 11211.2.1 Overview................................................................................................................................................11211.2.2 Installing a DCS on the OpenTouch server.......................................................................... 11311.2.3 Installing a DCS on an external server...................................................................................121

Chapter 12Ecosystem Configuration

12.1 Configuring Gmail as unified messaging server......................................12412.1.1 Configuration overview...................................................................................................................12412.1.2 Configuring Google settings........................................................................................................ 12512.1.3 Configuring the OpenTouch server.......................................................................................... 13112.1.4 Configuring polling options...........................................................................................................132

12.2 Configuring Microsoft Exchange as unified messaging server 13212.2.1 Implementation...................................................................................................................................13312.2.2 Information required.........................................................................................................................13312.2.3 Declaring the Microsoft Exchange server on the OpenTouch server......................133


Physical Machine


12.2.4 Configuring a dedicated account on the Microsoft Exchange server......................13412.2.5 Assigning rights to the privileged account on user mailboxes.................................... 13512.2.6 Configuring size and time limits allowed by the IIS web server................................. 13612.2.7 Verifying access to user mailboxes with the privileged account................................ 13612.2.8 Preventing privileged account from being used by unauthorized users................ 137

12.3 Configuring Office 365 as unified messaging server...........................13812.3.1 System requirements...................................................................................................................... 13812.3.2 Implementation...................................................................................................................................139

12.4 Configuring IBM Domino as unified messaging server.....................14112.4.1 Information required.........................................................................................................................14212.4.2 Lotus Domino configuration......................................................................................................... 142

12.5 Configuring an LDAP server.........................................................................................15812.5.1 Information required.........................................................................................................................15812.5.2 Declaring the LDAP server on the OpenTouch server....................................................159

12.6 Configuring a reverse proxy.........................................................................................159

12.7 Configuring the DNS server.......................................................................................... 159

12.8 Configuring an NTP server.............................................................................................159

12.9 Configuring a DHCP server on Windows Server 2008........................16012.9.1 Installing Windows Server 2008 DHCP Server..................................................................16012.9.2 Configuring a Vendor Class......................................................................................................... 16012.9.3 Configuring a scope of IP addresses...................................................................................... 16112.9.4 Configuring scope options............................................................................................................ 161

Chapter 13System Configuration

13.1 Backing up the OpenTouch server database...............................................16213.1.1 Backing up the OpenTouch Business Edition server database................................. 16213.1.2 Backing up the OpenTouch Multimedia Services server database..........................162

13.2 Configuring Global parameters................................................................................. 162

13.3 Dialing plan overview.......................................................................................................... 164


Physical Machine


13.4 Configuring ranges................................................................................................................166

13.5 OXE prefix (Conversation users)............................................................................. 16613.5.1 Overview................................................................................................................................................16613.5.2 Configuration.......................................................................................................................................168

13.6 Configuring dialing rules................................................................................................. 168

13.7 Configuring a voice mail system..............................................................................16913.7.1 Local storage voice mail configuration................................................................................... 16913.7.2 UM voice mail configuration.........................................................................................................170

13.8 Configuring music on hold............................................................................................ 171

13.9 Configuring the System TUI languages.............................................................171

13.10 Configuring TUI applications....................................................................................... 17213.10.1 Configuring the Voice homepage application....................................................................17213.10.2 Configuring the Advanced Cellular Extension (ACE) application..............................17513.10.3 Configuring the Telephony services application............................................................. 17613.10.4 Configuring the VoiceIt application..........................................................................................17913.10.5 Configuring the One number application............................................................................. 18213.10.6 Configuring the DVA application................................................................................................184

13.11 Configuring forwarding prefixes.............................................................................. 184

Chapter 14Connections to the System

14.1 Access to the OpenTouch Business Edition server..............................185

14.2 Local access.................................................................................................................................18514.2.1 Connection to the OpenTouch server..................................................................................... 18514.2.2 Connection to vmOXE, vmOMS and vmManagement virtual machines............... 185

14.3 Remote connection via a VNC over SSH tunnel....................................... 18714.3.1 Overview................................................................................................................................................18714.3.2 VNC over SSH tunnel remote access.....................................................................................187

14.4 Initial login and password configuration......................................................... 197


Physical Machine


Chapter 15OpenTouch network configuration

15.1 Overview...........................................................................................................................................199

15.2 Description.....................................................................................................................................199

15.3 Deployment................................................................................................................................... 20015.3.1 Prerequisites........................................................................................................................................20115.3.2 Declaring the OpenTouch nodes of the network............................................................... 20115.3.3 Associating the OpenTouch nodes in the network........................................................... 20215.3.4 Displaying OpenTouch network status................................................................................... 20315.3.5 Displaying users of a remote OpenTouch node.................................................................20515.3.6 Removing an OpenTouch node from the network............................................................ 20615.3.7 Forcing synchronization on an OpenTouch node..............................................................20715.3.8 Modifying the OpenTouch ecosystem configuration........................................................ 207

15.4 Troubleshooting: user synchronization issue due to duplicateddata ...................................................................................................................................................... 208

Chapter 16Update

16.1 Update overview....................................................................................................................... 209

16.2 Delivery..............................................................................................................................................210

16.3 Prerequisites................................................................................................................................ 211

16.4 Update operations...................................................................................................................211

16.5 Partitions switchover...........................................................................................................218

16.6 OpenTouch Fax Center update specificities.................................................220

16.7 Rollback after a switchover fails.............................................................................. 220

16.8 Additional operations on the inactive partition......................................... 220


Physical Machine


16.8.1 Presence of the inactive partition..............................................................................................22016.8.2 Partitioning implementation..........................................................................................................22016.8.3 Reading the content of the inactive partition....................................................................... 221

16.9 Log files.............................................................................................................................................221

Chapter 17Upgrade

17.1 Overview...........................................................................................................................................223

17.2 Software requirement..........................................................................................................223

17.3 Upgrading the OmniVista 8770 virtual machine........................................224

17.4 MIC mobile recognition in R2.2 (or higher).................................................... 224

17.5 Backing up the database of the OpenTouch server.............................. 226

17.6 Installing OpenTouch...........................................................................................................226

17.7 Launching the OpenTouch server database restoration.................. 22617.7.1 Database restoration during post-installation......................................................................22617.7.2 Database restoration after post-installation......................................................................... 228

Chapter 18Troubleshooting procedures and guides

18.1 Virtual machine problems............................................................................................... 229

18.2 Host problems............................................................................................................................ 233

18.3 USB problems.............................................................................................................................235

18.4 Flexlm server problems.....................................................................................................235

18.5 Removing a deployment package...........................................................................236


Physical Machine


Chapter 19Decommissioning

19.1 Decommissioning a non-virtualized OpenTouch server...................238

19.2 Decommissioning a virtualized OpenTouch server...............................241


Physical Machine


Chapter

1 About this document

1.1 About this documentThis document is intended for people in charge of installing and commissioning an OpenTouchBusiness Edition system.

This document details:

• Installation from scratch: installation of an OpenTouch version on a new server, without restorationof existing databases: see Installation from scratch on page 22

• Update operations: installation of a new OpenTouch version on top of an existing one, withconservation of existing databases (configuration databases are not lost during the update processand do not need to be restored). See Update on page 209

• Upgrade operations: installation from scratch of a new OpenTouch version (on the same server, oron a new one), followed by the restoration of configuration databases. See Upgrade on page 223

• Troubleshooting procedures: Troubleshooting procedures and guides on page 229• Decommissioning the applications: Decommissioning on page 238

This document includes quick start guidelines, which detail the mandatory operations to setup anOpenTouch Business Edition system, including installation and administration operations, as well asthe setup of 8082 My IC Phone sets and certificate management: Quick Start on page 18

This manual only addresses the installation of OpenTouch Business Edition on a physical machine.The installation of OpenTouch on a virtual machine, is described in the OpenTouch MultimediaServices documentation, in the document: "Installation on a Virtual Machine".


Chapter

2 Reference documents

The OpenTouch documentation consists in separated documents, each corresponding to a specificaspect of necessary and optional installations/administrations.

The full set of all available documents is updated every week and can be accessed on the BPWS TDL.

In the present document, cross-references are identified by the number in the first column of the tablebelow.

Part numbers are given in the last column, where the first two xx correspond to the language code ofthe document.

The documents for OpenTouch are:

table 2.1: OpenTouch documentation structure

Documentation title Part number

[1] OTBE Installation Manual on a Physical Machine

Summary: this document describes the software layout of an Open-Touch Business Edition on the provided hardware. Hardware and soft-ware installation are explained in detailed procedures. Post installation,connection and the basic configuration are also described with proce-dures. Software major and minor updates are explained and trouble-shooting guidelines are provided.

8AL90504xxxx

[2] OTMS Installation Manual on a Physical Machine

Summary: this document describes the software layout of an Open-Touch Multimedia Services on the provided hardware. Hardware andsoftware installation are explained in detailed procedures. Post installa-tion, connection and the basic configuration are also described withprocedures. Software major and minor updates are explained and trou-bleshooting guidelines are provided.

8AL90512xxxx

[3] OTBE/OTMS Administrator Manual

Summary: this document describes all the necessary procedures to im-plement an OpenTouch Business Edition or OpenTouch MultimediaServices system: from user configuration to advanced applications, de-vices (including video devices), conferencing and collaboration fea-tures, as well as call restriction management. CAC management, back-up and restore procedures and IP flows are also detailed.

8AL90505xxxx

[4] Installation Manual on a Virtual Machine

Summary: this document describes prerequisites and topologies for aninstallation of the system on a virtual machine. The installation proce-dure is described in detail for every system element. License manage-ment and license updates are also explained. Appendixes provideguidelines on the recommended software installation tools.

8AL90507xxxx



[5] ALEDS

Summary: this document describes the implementation of this deploy-ment tool in the various compatible topologies. This documents in-cludes requirements and procedures to install each software, amongwhich the OpenTouch. Software deployments and updates are ex-plained for physical and virtual machines.

8AL90508xxxx

[6] OpenTouch General Architecture

Summary: this document presents the available systems in relation tothe actual customer needs. Topologies and software architectures arepresented for OpenTouch Multimedia Services, OpenTouch BusinessEdition, and the native contact center. Hardware compatibilities are de-tailed per system.

8AL90509xxxx

[7] OpenTouch System Documentation

Summary: this document describes the services and applications spe-cific for Conversation users, as well as the One Number Service forConnection users. It also includes up-to-date recommendations on sys-tem security, certificates, encryption and best practices.

8AL90510xxxx

[8] OpenTouch Maintenance and Supervision

Summary: this document describes the available tools to monitor and/ortroubleshoot the OpenTouch and its ecosystem. This document alsoprovides guidelines on the maintenance portal and the supervision ofserver(s), devices and calls. A list of useful maintenance command isincluded, with explanations and examples.

8AL90511xxxx

[9] OT-C2D Administrator Guide 8AL90527xxxx

[10] OT-C2D User Guide 8AL90528xxxx

[11] Description of IP flows in OpenTouch solution

Summary: this document describes the IP flows involved for the sys-tem. This allows to configure firewall rules precisely, to open the optimalamount of ports required for an operating OpenTouch system, accord-ing to customer requirements.

8AL220303381xxxxx

[12] OpenTouch Web Services Technical Overview

Summary: this document describes how to develop, integrate and de-ploy third party applications with an OpenTouch, via API. This docu-ment includes a description of the available web services as well as in-formation on authentication and licensing.

8AL90532xxxx

Chapter 2 Reference documents



[13] OpenTouch Edge Server - Installation and administration manual

Summary: this document describes the implementation of this server tocontrol data flows (conferencing, data sharing, instant messaging orweb presentations) between OpenTouch client applications used off-site and the OpenTouch server, so as to secure the system. Installationand configuration procedures are provided, as well as upgrade andmaintenance guidelines.

8AL90535xxxx

[14] OpenTouch XMPP federation with Microsoft© Lync™ Server

Summary: this document describes how to implement the XMPP proto-col to achieve transparency of features between OpenTouch applica-tions and the MS Lync collaboration application. Configuration proce-dures and maintenance commands are provided for the OpenTouchand the MS servers.

8AL90539xxxx

[15] OpenTouch Client Administration Manual

Summary: this document describes the implementation of an Open-Touch ecosystem for clients connecting from remote locations. It alsoprovides deployment and configuration procedures, for each client - ontablets, PCs, smartphones, or from the web.

8AL90638xxxx

[16] OTMC Installation Manual

Summary: this document describes the installation of an OpenTouchMessage Center server on a physical server or on a virtual machine.Procedures detail the various steps of installation, as well as post-in-stallation, initial configuration on an OmniPCX Enterprise, TUI configu-ration and software upgrades.

8AL90120xxxx

[17] OTMC Administrator Manual

Summary: this document provides all the necessary configuration pro-cedures to implement an OTMC, from voice mail and user profiles, tomailboxes, e-mail, sms notifications, automated attendant, VPIM, IMAPand backup/restore.

8AL90121xxxxx

[18] OTMC High Availability

Summary: this documents explains how to implement a high availabilitysolution, consisting of having a backup system taking over in case offailure of the main OTMC system. The installation procedure is comple-ted by configuration details on the control of the solution, FQDNs, datareplication and service continuity. Backup/restore procedures are provi-ded along with information on monitoring and system repair.

8AL90123xxxx

[20] OpenTouch Conversation for PC User Guide 8AL90631xxxx

[26] OpenTouch Message Center User Guide 8AL90122xxxx

[28] OpenTouch Conversation for 8082 My IC Phone R300 User Manual 8AL90835xxxx




[29] OpenTouch Conversation for 8082 My IC Phone R300 User Guide 8AL90877xxxx

[30] OpenTouch Conversation for iPhone Release 2.0.x User Guide 8AL90884xxxx

[31] OpenTouch Documentation Note

This document lists all the modifications and updates since the previousdocumentation release.

8AL90911xxxx

[32] Alcatel-Lucent 8001 DeskPhone User Manual 8AL90895xxxx

[33] Dongle IP / Raspberry for OpenTouch Suite

Summary: this document covers the deployment of USB over IP donglewith OpenTouch and OmniPCX Enterprise systems. Requirements andpossible topologies are presented before procedures detailing the in-stallation and necessary configuration.

8AL90617xxxx

[34] ALE NFC Extended OXE Mobility Administration

Summary: this administration manual describes the implementation oftransparent call shifts from a device to the other via NFC tags. NFC taggeneration is detailed with screenshots from the application.

8AL90614xxxx

[35] OTBE/OTMS High Availability

Summary: this document explains how to implement a high availabilitysolution, consisting of having a backup system taking over in case offailure of the main OpenTouch system (OpenTouch Multimedia Servicesor OpenTouch Business Edition). The installation procedure is comple-ted by configuration details on the various network elements (edgeserver, reverse proxy), as well as system options (Exchange server, ex-ternal gateway for a fax) and a backup/restore procedure.

8AL90534xxxx

[36] OpenTouch Session Border Controler Configuration Guide

Summary: this document describes the implementation of this server tocontrol media (voice/video) communications between OpenTouch clientapplications used off-site and the OpenTouch server, so as to securethe system. Installation, configuration and maintenance procedures aredetailed in this document.

8AL90065xxxx

[37] OpenTouch Suite for MLE in virtualized environment, overview

This pre-sales document describes the OpenTouch Suite for MLE prod-ucts virtualization capabilities and the main principles regarding FlexLMdeployment

TBE031

[38] Virtualization Design Guide

This pre-sales document describes the deployment of OpenTouch Suitefor MLE products in a virtualized environment

TBE043



Chapter

3 Quick Start

Follow the procedure detailed below, respecting the order given for each step of the procedure. At theend of the process, the system will operate correctly but complementary configuration may benecessary for smooth implementation.

At the beginning or the end of each step of the procedure , use the hyperlinks located close to the

arrow icons ( or ) to navigate to the previous or next operation.

3.1 Installation Manual

Operating System deployment

Reboot

Basic configuration

Package deployment

Reboot

Post Installation

Factory installationDeployment via DVDs

Initial configuration

Topology

Eco System

OpenTouch configuration

User provisioning

Application advanced configuration

OmniVista 8770 connexionConference configuration

Gmail, MS Exchange, IBM dominoLDAP, Reverse Proxy, DNS, NTP, DHCP

Dialing plan, prefixesLocal storage voice mailTUI applications

Voice mails / Devices / Users

NomadicOne number serviceHome page applicationVideoConferencing applicationSearch directoryManager assistant

Network deploymentvia ALEDS

OS + packagedeployments

Boot Boot

Figure 3.1: Installation diagram


table 3.1: Installation steps

1. Product Overview on page 202. delivery on page 233. Hardware Installation on page 254. Software Installation on physical machines on page 275. server post installation on page 456. additional installation on page 727. Firewall on page 948. Codec configuration on page 1029. DPNSS prefix configuration on page 10310.Overview on page 10611.Dialing plan overview on page 16412.Configuring ranges on page 16613.OXE prefix ( users) on page 16614.Configuring dialing rules on page 16815.Local storage voice mail configuration on page 169

Chapter 3 Quick Start


Chapter

4 Product Overview

4.1 Overview

Quick Start on page 18 OpenTouch Business Edition delivery on page23

The OpenTouch® Business Edition is an ALE International software solution, delivered on a singlepiece of hardware, and including the following elements:

• An OmniPCX Enterprise• An OmniVista 8770 server• An OpenTouch server• An Alcatel-Lucent OpenTouch® Fax Center• A DCS (Document Conversion Server) on a virtual machine. This server is optional• An OXE Media Services

4.1.1 OpenTouch Business Edition on a physical machineThe OpenTouch Business Edition server contains virtual machines to host the different serversincluded in the solution.

License ServerVirtualization Server

SUSE Linux Enterprise Server Operating System

HardwareOTBE Server

Virtual Machines

Host

VmOXEVirtual Machine

Operating System

OmniPCXEnterprise

Communication Server

(CS)

OmniVista 8770 Network Management

System

Operating System

Window Server

VmManagementVirtual Machine

OpenTouch Server

DCSVirtual Machine

(optional)

OMSVirtual Machine

(optional)

Figure 4.1: OpenTouch Business Edition architecture

The OpenTouch Business Edition server is built on a SUSE Linux Enterprise Server operating system(SLES). This operating system is called host in this document.

On the SLES operating system, the following servers are installed:

• A virtualization server which allows all ALE International applications to operate on the same server.The virtualization layer creates virtual machines using their own operating system:


• The OmniPCX Enterprise virtual machine (vmOXE) consists of a Linux operating system and theCommunication Server application.

• The management virtual machine (vmManagement) consists of the Windows Server operatingsystem and the OmniVista 8770.

• A DCS (Document Conversion Server) on a virtual machine. This server is optional.• An OXE Media Services

• The OpenTouch server which includes:

• Telephony features• Messaging• Collaboration• Conferencing• Routing• Fax

The host has a physical Ethernet access. It also has its own IP address.

Each virtual machine has a virtual Ethernet access with an IP address.

Note:This document only presents OpenTouch Business Edition features. For more information on ALE Internationalapplications refer to the corresponding technical documentation.

Quick Start on page 18 OpenTouch Business Edition delivery on page23

Chapter 4 Product Overview


Chapter

5 Installation Overview

5.1 OverviewAccording to your order to ALE International, the installation procedure to follow is one of the following

• Installation from scratch. From a server matching requirements, install the software and configureapplications (see: Installation from scratch on page 22)

• Factory installation. Selected servers are prepared for you in factory before they are shipped. Theapplications are installed when you receive the machine(s), but they need your configuration (see: Factory installation on page 22)

5.1.1 Installation from scratchThe OpenTouch Business Edition server installation consists of:

1. Hardware installation: see Hardware Installation on page 252. OpenTouch Business Edition server software installation: see Software Installation on physical

machines on page 27

This software may already be installed in factory before shipping (in such a case, this operation isskipped).

3. OpenTouch Business Edition server "post installation": see Software Installation on physicalmachines on page 27

• Network parameters for the host and ALE International applications• Username and password for ALE International applications• License file installation (optional)• Certificate management (mandatory): see Certificate management on page 77

4. OpenTouch Business Edition server initial configuration: see Connection Configuration on page 94

This consists in configuring the various services of the OpenTouch Business Edition whoseparameters are not defined in the previous operation

After OpenTouch Business Edition is installed:

1. Installation of the remote clients of ALE International applications (if required)2. Application configuration

Note:Configuration of client applications is not described in this document. Refer to the technical documentation of theconcerned application for more information.

5.1.2 Factory installationBefore shipping, the software (operating system and OpenTouch Business Edition application software)is installed.

On the customer site, OpenTouch Business Edition server installation consists of:

• Post installation that is to say customer network configuration, username and passwordconfiguration and license installation: see Post Installation on page 44

• OpenTouch Business Edition server initial configuration: see Connection Configuration on page 94

This is the configuration of the various services of the OpenTouch Business Edition whoseparameters could not be defined previously

• Installation of the remote clients of ALE International applications (if required)


• Application configuration

Note:Configuration of client applications is not described in this document. Refer to the technical documentation of theconcerned application for more information.

5.2 OpenTouch Business Edition delivery

Product Overview on page 20 Hardware Installation on page 25

The OpenTouch Business Edition server delivery consists of:

• A dedicated server with the OpenTouch Business Edition software, either installed on the machineor not

• A USB dongle - delivered for virtualization packages only. When the OpenTouch is installed on aphysical machine, all technical items in the license file are signed using the ALUID (Alcatel-LucentUnique IDentifier)

• A set of DVDs for software installation and/or repair. For the DVD list, see: Software requirement onpage 39

Note:DVDs can be replaced by .iso files.

• A set of ALE International application CD-ROMs to install remote clients• A set of license files downloaded from the Business Portal.

5.2.1 Licenses

5.2.1.1 Windows server licenses

The OpenTouch server includes a Windows Server operating system (hosting the OmniVista 8770)which requires a Microsoft license number to operate.

Note:This license is included in the ALE International delivery.

5.2.1.2 OpenTouch Business Edition licenses5.2.1.2.1 Overview of licenses

Licenses (also called software locks) allow customers to purchase only the features that they need.License files rule the available features of a given OpenTouch Business Edition system.

An OpenTouch Business Edition is identified by:

• In case of installation on a physical machine: the ALUID (Alcatel-Lucent Unique Identifier)• In case of installation on virtual machines: a USB dongle

License files contain:

• The list of purchased features• The site identification (ALUID or USB dongle)• The hostname• A checksum

License file can only be used on the OpenTouch Business Edition with the specified identification.

If license files are missing, corrupted or if the site identification is incorrect, the correspondingOpenTouch Business Edition licensed features are not available:

Chapter 5 Installation Overview


• The OmniPCX Enterprise application switches to Panic mode. Refer to the OmniPCX Enterprisetechnical documentation for more information on panic mode.

• The OmniVista 8770 application is not available• The OpenTouch application is not available

5.2.1.2.2 List of license files

License files consist of:

• xxxxx.swk hardware.mao and xxxxx.zip for the OmniPCX Enterprise application (xxxxx=order identification)

• xxxxx.sw8770 for the OmniVista 8770 (xxxxx= order identification)• xxxxx.ice for the OpenTouch applications (xxxxx= order identification)

Product Overview on page 20 Hardware Installation on page 25

Chapter 5 Installation Overview


Chapter

6 Hardware Installation

6.1 Hardware installationOpenTouch Multimedia Services - InstallationOverview - OpenTouch Multimedia Servicesdelivery

OpenTouch Multimedia Services - SoftwareInstallation on a physical machine - Overview

When unpacking the OpenTouch server, read the ALUID on the sticker glued on the OpenTouch servercover.

In order to retrieve the OpenTouch Business Edition license files from the Enterprise Business Portal,the ALUID must be declared in the eLicensing Host Registration page. This is also true in case ofreplacement of the motherboard of the OpenTouch server: the ALUID must be read on the packagingof the new motherboard.

When only the software is ordered from the ALE International catalog, there is no sticker indicating theALUID on the OpenTouch server cover. The encrypted ALUID can be retrieved, either:

• After OS installation, using the command /usr/bin/getaluid• Before OS installation, using the ALEDS tool. The ALUID is read at server boot, via a boot menu

provided by the ALEDS engine. For more information, refer to [5]

For installation purposes, the OpenTouch server must be equipped with standard interface devices i.e.:

• A USB mouse• A USB keyboard• A video monitor

These items can be removed after installation.

OpenTouch™ ServerUSB

Mouse

USBKeyboard

VideoTo power

supply

To IP Network

USB Dongle (as of R2.0: only for virtualization packages)

Ethernet PortHost Console

Figure 6.1: Connections for wizard installation

The OpenTouch server is equipped with RAID disks technology (Redundant Array of IndependentDisks). The RAID devices must be configured before installation.

After post-installation, the raidstatus_cmd command can be used to check the status of the RAIDarray.

Network connections:


• Ethernet redundancy is not supported. Only one port must be connected.• Do not use the management port (reserved for specific machine vendor operations).

OpenTouch Business Edition - InstallationOverview - delivery

OpenTouch Multimedia Services - SoftwareInstallation on a physical machine

Chapter 6 Hardware Installation


Chapter

7 Software Installation on physicalmachines

Note:If software installation has been performed on the machine(s) before it was shipped to you, you may skip thefollowing paragraphs.

7.1 Overview

Hardware Installation on page 25 Server post installation on page 45

When the server is delivered without software, a software installation is required. There are two ways toinstall software on an OpenTouch server:

• From the network. This is used when no DVD drive is available on the server. See: Installation fromthe network on page 28.

• From DVDs. This requires a DVD drive on the server. See: Installation from DVDs on page 37

The OpenTouch server has two partitions:

• The active partition. This partition is used for the system in operation. This partition is mandatoryand must be installed first as described in this section.

• The inactive partition. This partition is used for updates and upgrades. This partition is optional. Formore information on installation, see: Update on page 209 or Upgrade on page 223.

7.2 Information requiredThe following information is required during software installation:

• The keyboard type• The installation country• The company name• The date, the time and the time zone• The server FQDN• The IP address of the server• The IP address of the default gateway• The IP address of the DNS server• The new password for the root account• The IP address and the port number of the external license server (required only when an external

license server is used)

7.3 BIOS configurationThe OpenTouch Business Edition package uses a virtualization process to host software componentssuch as the OmniPCX Enterprise, OmniVista 8770, and OXE Media Services. This must be enabled inBIOS configuration:

7.3.1 HP Server (for servers: HP DL120 G7, DL 380 G8 and HP DL180 G9):1. At server initialization, Press F9 to enter BIOS configuration2. Navigate to: System Options > Processor Options


3. Review/Modify the following attribute:

Intel Turbo Boost Technology Select: Enabled (default)

Intel Hyperthreading Options Select: Disabled

4. Navigate to: Power Management Options5. Review/Modify the following attributes:

HP Power Profile Select: Maximum Performance

HP Power Regulator Select: HP Static High Performance Mode

6. Navigate to: Power Management Options -> Advanced Power Management Options7. Review/Modify the following attributes:

Energy/Performance Bias Select: Maximum Performance

Memory Power Savings Mode * Select: Maximum Performance

Dynamic Power Savings Mode Re-sponse

Validate: Fast (default)

* Specific to DL 380 G8 server8. Check date and time, and update if needed9. Confirm your entries

7.3.2 Lenovo System x3250 M61. At server initialization, Press F1 to enter BIOS configuration.2. Navigate to: Boot Manager > Boot Modes > System Boot Mode3. Change UEFI Mode by LEGACY Mode4. Navigate to System Settings > Storage > Create virtual drive to create hard drives.5. Check date and time, and update if needed.6. Confirm your entries.

7.3.3 VerificationTo verify virtualization configuration (after SLES installation):

• Launch the server (if not already done)• Open a session• Enter the dmesg | grep kvm command

The following message is displayed: kvm: enable by bios

7.4 Installation from the networkThe OpenTouch Business Edition server can be installed from the network, without any DVD. This isperformed using the Alcatel-Lucent Enterprise Deployment Solution tool, also called ALEDS, availablefrom the Business Portal Web Site. This installation presents the advantage of a much reducedinstallation time.

Chapter 7 Software Installation on physical machines


7.4.1 PrerequisitesTo install the OpenTouch with the ALEDS, you need:

• A PC or laptop with an Ethernet cable, on which the WMware player has been installed, and theALEDS R3.4 or higher is running. This PC must be connected to the VLAN of your client server

Note:To check whether your machine can run a VMware player, use the VMware-guest64check-5.5.0-18463.exe tool. This tool can be downloaded from the VMware website

• The MAC address of the client server on which OpenTouch is to be installed• The .iso files which correspond to the applications to install:

Component File name (*.iso)

SLES operating system bootdvd.x.x.xxx.xxx.x86_64.iso

OpenTouch otx.x.xxx.xxx-1.isoNote:otx.x.xxx.xxx-2.iso provides additional softwarefor client integration and VM Flex and is not needed forOpenTouch installation.

OmniVista 8770 OTBEVM_Management-x.x.xxx.xxx-1.isoOTBEVM_Management-x.x.xxx.xxx-2.iso

OmniPCX Enterprise OTBEVM_OXE-x.x.xxx.xxx.iso

OpenTouch Fax Center (Fax software) (ifneeded)

OmniTouchFaxServer-x.x.x.x-suse12.iso

OXE Media Services (OXE-MS) OTBEVM_OMS-x.x.xxx.xxx.iso• License files for the different OpenTouch components

The figure below shows an example of an OpenTouch Business Edition network environment:



Target server with:

OpenTouch coreHostname: server1otIP address: 192.168.201.131DomainName: eudoc.euroscript.local

OmniPCX Enterprise virtual machineHostname: server1oxeIP address: 192.168.201.132

OmniVista 8770 virtual machineHostname: server18770IP address: 192.168.201.133

OMS virtual machineHostname: server1omsIP address: 192.168.201.137

DNS server(DNS resolution of OpenTouch, VmOXE, Vm8770, VmOMS) IP address: 192.168.201.200

GatewayIP address:192.168.201.249

License server (optional)Hostname: frbreseuro2licIP address: 192.168.201.150

Computer with ALEDS tool (software and engine)Hostname: pxeIP address: 192.168.201.128

Figure 7.1: OpenTouch Business Edition network environment example

7.4.2 OpenTouch installation overviewOnce the ALEDS is operational and connected to the VLAN of the server to install, installation of theOpenTouch can begin:

1. Configure the network parameters of the ALEDS virtual machine, see: Configuring the network onpage 31

2. Configure the IP address and hostname of the OpenTouch server, see: Specifying IP addresses andhostnames on page 32

3. Prepare the OpenTouch installation files, see: Specifying installation files on page 324. Create and start your virtual machine, see: Booting the target machine from the network on page

36



5. Physically start your client server and select the Network boot option from the boot menu, see: Booting the target machine from the network on page 36

Installation of the OpenTouch starts6. Install and run the OmniVista 8770

Your system is operational

For more information on the installation of the ALEDS and more detail on operations, see [5].

7.4.3 Configuring the network1. Start the ALEDS application

Figure 7.2: ALEDS network configuration example2. In the Engine tab, fill in the following fields:

• IP Address: enter the IP address of the engine. This address must be accepted by the VLAN,but there is no need to declare it in your DNS

• IP Mask: as per your VLAN• IP Gateway: as per your VLAN• DNS Server: as per your VLAN

The DNS server must resolve all names and IP addresses configured in the DNS/Targets tab(direct and reverse resolution).

The DNS server can be:

• The ALEDS itself, which can act as DNS server. In this case, the IP address must be thesame as the one entered in the IP address field (default configuration)

• An external DNS. In this case, the DNS must be reachable from the target machine



Even if an external DNS server address is entered, the ALEDS uses the engine IP address asdefault DNS server. The ALEDS automatically acts as DNS server for product installation on atarget machine. After product installation, the ALEDS replaces the engine IP address by theexternal DNS IP address configured in the target machine.

• Host name: enter the host name of the engine. You may keep the default pxe hostname• Domain name: must correspond to the domain name of the client server about to be installed

3. Click Save and go to the DNS server tab

7.4.4 Specifying IP addresses and hostnamesGo to the DNS/Targets tab of the ALEDS window

Figure 7.3: ALEDS DNS configuration example

In the host1 line, enter the IP address, the name (FQDN), the MAC address and select the Role ofthe OpenTouch server

7.4.5 Specifying installation files1. Ensure you have all the necessary iso files at hand

Note:License files are specified at post-installation, see: Post Installation on page 44

2. Go to the OT tab of the ALEDS window



Figure 7.4: File selection example for an OpenTouch Business Edition installation

By default, network settings are provided by the DHCP server. If preferred, to get the correctpredefined IP address, you may add the MAC address of the target machine in the DNS settingstab.

If, for instance, there is already another DHCP server on the connected network, you may force astatic IP address by selecting it from the drop-down list.

During installation, the built-in DNS is always used, it is only at end of installation that the DNSconfiguration is changed.

3. Enter the data requested in the corresponding fields:

• boot iso: browse to the location of the SLES iso file of the solution.

The name of the file is: bootdvd.x.x.xxx.xxx.x86_64.iso (where Xs vary according tosoftware version)

• core iso: browse to the location of the OpenTouch iso file of the solution

The name of the file is: otx.x.xxx.xxx-1.iso (where Xs vary according to software version)• OFS iso: browse to the location of the OpenTouch Fax Center iso file of the solution

The name of the file is: OmniTouchFaxServer-x.x.x.x-suse12.iso (where Xs varyaccording to software version)

• OXE vm: browse to the location of the iso file for vmOXE

The name of this file is: OTBEVM_OXE-x.x.xxx.xxx.iso (where Xs vary according tosoftware version)

• 8770 vm1 and 8770 vm2: browse to the location of the iso files for vmManagement



The name of this file is: OTBEVM_Management-x.x.xxx.xxx-1.iso andOTBEVM_Management-x.x.xxx.xxx-2.iso (where Xs vary according to software version)

• OMS iso: browse to the location of the iso files for vmOMS

The name of this file is: oms-<version>.iso (where Xs vary according to software version)• Licenses: If licenses files are specified in this tab, they are copied to the destination directory,

and in the /tmp/licenses directory, so that they can be retrieved when running the post-installwizard.

In case of installation on several machines, you may provide licenses for all targets in theLicenses field. Each licence file must be renamed using the MAC address of the first interface(eth0) of the target machine.

Example:

When the license file is named: license.ice and the MAC address is 112233445566, thelicense file must be renamed to [email protected] files for the OmniPCX Enterprise (license.swk) and license for the OmniVista 8770(license.sw8770) must be renamed on the same way.

4. Select the languages for your solution

7.4.6 Verifying the integrity of installation filesAn MD5 file is present for each installation file of the OpenTouch solution, in the same directory. ThisMD5 file is used to verify the integrity of the installation file. It is a text file, bearing the same name asthe installation file, but with the .md5 extension. For example, an OpenTouch core installation filenamed ot-2.1.000.061.iso is delivered with the MD5 file: ot-2.1.000.061.iso.md5.

After installation file selection (see: Specifying installation files on page 32), the ALEDS offers to verifythe integrity of each installation file by:

• Getting the MD5 encrypted code of the installation file (also called MD5 checksum)• Verifying this code with the original code present in the associated MD5 file

This feature is available from the ALEDS 3.3, and can apply to all or a selection of the installation files.

To verify the integrity of installation files:

1. From the OT tab of the ALEDS window, select the check box next to the installation file2. Repeat this operation for all the installation files to verify



Figure 7.5: Verification of file integrity example3. Click the Validate button next to MD5 checksum verification

A warning pop-up opens.

It displays the estimated time to check the first selected installation file. This duration depends onthe file location.

4. Click Yes to launch verification, or No to skip this verification

If Yes is selected, a progress bar is displayed. At the end of the process or if this operation isskipped, the warning pop-up opens for the next installation file to verify.

Caution:Once started, the MD5 checksum verification process cannot be stopped.

5. Repeat this operation for all the installation files to verify

Once the verification process is completed, a result pop-up opens.

It displays the list of installation files verified and their status: success, failure or MD5 text missingat source.

Note:MD5 text missing at source indicates that no MD5 file bearing the same name as the installation file ispresent in the directory.

6. Click OK

The ALEDS window is available again.

7.4.7 Saving configurationIf for some reason, you need to postpone OpenTouch deployment:



1. Exit the ALEDS2. When ready, open the ALEDS3. Click Load to load the previously saved configuration

7.4.8 Booting the target machine from the networkOnce all the necessary configuration has been prepared:

1. Click Start VM

The ALEDS engine starts

At the end of the initialization process, the list of deployed iso files is displayed

Figure 7.6: Example of list of iso files deployed2. Verify that all correspond to your expected deployment3. Physically start (or restart if the server is already running) the OpenTouch server, and wait a few

minutes4. On the OpenTouch server, start network boot

On most servers, press F12 after power on to enter in the BIOS, where the boot sequence isconfigured. For an HP DL120 G7 server, press F11.

5. In the Alcatel-Lucent ESD Deployment Server menu, select OpenTouch Installation



6. In the OpenTouch Installation menu, select OpenTouch Business Edition (OTBE)

The OpenTouch Business Edition software installation starts.

After software installation, the system reboots and you are prompted for post installation.

7.5 Installation from DVDs

7.5.1 SUSE Linux Enterprise Server installationWarning:Do not proceed with the following operations when the OpenTouch Business Edition software has already beeninstalled by ALE International on the server.

The OpenTouch Business Edition server uses SUSE Linux Enterprise Server (SLES) operating system.This SLES OS has been customized by ALE International.

To install SLES:

1. Use the release notes, available on the DVD, to verify that the DVD called OPENTOUCH BootDVD-R is compatible with the OpenTouch Business Edition release to install.

2. Insert this DVD in the drive3. Start the system. The system boots on the DVD. The SLES installation screen is displayed with

several installation options.

Note:If the server does not boot on the DVD drive change boot order in the server BIOS.

4. Press F2 to select your language and your keyboard type



Caution:By default, the keyboard is configured as English (US). If using a different keyboard, ensure you selectit now to avoid later mismatches.

5. Select the installation type:

• OpenTouch Business Edition to install the OpenTouch Business Edition package using theGUI, with an active and an inactive partition: this option allows smooth updates on the inactivepartition, but requires more disk space on the server.

• OpenTouch Business Edition (single partition) to install the OpenTouch BusinessEdition package using the GUI, with only an active partition: this option requires less disk spaceon the server, but smooth updates on the inactive partition are no longer possible.

SLES installation starts. Installation takes about 30 minutes.6. When installation is finished, the system reboots.

7.5.2 OpenTouch Business Edition server pre-configurationOpenTouch Business Edition pre-configuration consists in configuring network parameters.

1. Open a root session. The default password is letacla1You are prompted to change the root password.

2. Enter successively the current default password (letacla1), a new password for the rootaccount and confirm this new password

The password must contain at least one digit, one upper case character and one special character.

You are prompted to enter network configuration.3. Enter successively:

• The IP address of the OpenTouch Business Edition server• The FQDN of the server

This information is the concatenation of host name and domain name. Example:server1ot.eudoc.euroscript.local

• The network mask• The default gateway IP address• The DNS IP address

Note:The DNS server must be able to resolve the FQDN of the server (direct and reverse resolution).

You are prompted to confirm your entries4. Network configuration validation:

• Enter Yes to validate your entries• Enter No to modify

Note:By default eth0 is configured as network interface. If for some reason, eth0 cannot be physically connected, youmay use the setIPAddress.sh script, using the name of the target interface as argument. For example, ifusing eth2: setIPAddress.sh eth2

7.5.3 OpenTouch Business Edition software installationWarning:Do not proceed with the following operations when the OpenTouch Business Edition software has already beeninstalled by ALE International on the server.



7.5.3.1 Software requirement

The OpenTouch Business Edition software is provided by ALE International:

• OpenTouch core software (1 DVD):

OPENTOUCH x.x Core Setup DVD-R

Note:x.x represents the release identification.

• VmOXE (1 DVD):

OPENTOUCH x.x OXE VM DVD-R

Note:For a secured OpenTouch, a specific DVD including encryption software is delivered. For more information onsecured installation, see the OmniPCX Enterprise documentation - section IP Touch Security.

• VmOMS (1 DVD):

OPENTOUCH x.x OMS VM DVD-R• VmManagement (2 DVD):

• OPENTOUCH x.x 8770 VM-1 DVD-R• OPENTOUCH x.x 8770 VM-2 DVD-R

• OpenTouch Fax Center software (1 DVD):

7.5.3.2 Software installation procedure

1. Open a root session on the server console2. Insert the OpenTouch core software DVD in the DVD drive and mount the media:

• Enter the mount /media/cdrom command• Enter the ls -al /media/cdrom command to check. If the file list is displayed, the cdrom is

successfully mounted.3. Start the graphical interface, using the command:

systemctl start display-manager4. In the login window, click Not listed, and connect as root5. Open a terminal session: Applications > Utilities > XTerm6. Ensure the current directory is not the DVD reader directory

Enter the cd / command.7. Enter the /media/cdrom/checkSystemLinux.sh command to check your system and fix the

reported issues (if any).8. Entrer the /media/cdrom/setup.bin command to start installation.

The software installation wizard is started and the Wizard welcome page is displayed:



Figure 7.7: Installation wizard welcome page example

The following applies to all wizard screens:

Action buttons:

• Next: goes to the next page. It is possible to return to the previous page for modifications.• Back: goes to the previous page. The settings of the current page are not lost.• Cancel: exits the wizard

9. Click Next

The license agreement page is displayed:



Figure 7.8: License agreement page example10.Read the license agreement and select I accept the terms of the license agreement11.Click Next.

The information summary page is displayed:



Figure 7.9: Information summary page example12.Click Next to start software installation. This operation takes between 45-60 minutes.

A spinning hourglass is displayed. At the end of this operation, you are prompted to insert theOpenTouch Fax Center DVD in the DVD drive.

13.Insert the OpenTouch Fax Center DVD in the DVD drive14.Enter /media/cdrom as path for OpenTouch Fax Center installation15.Click Next to start OpenTouch Fax Center installation

A progress bar is displayed. When finish, you are prompted to insert the vmOXE installation DVD.16.Insert the vmOXE DVD in the DVD drive17.Enter /media/cdrom as path for vmOXE installation18.Click Next to start vmOXE installation

A progress bar is displayed. When finish, you are prompted to insert the vmOMS installation DVD.19.Click Next to start vmOMS installation

A progress bar is displayed. When finished, you are prompted to insert the vmManagementinstallation DVD.

20.Insert the first vmManagement DVD in the DVD drive21.Enter /media/cdrom as path for vmManagement installation22.Click Next to start the first part of the vmManagement installation

A progress bar is displayed. At the end of the process you are prompted to insert the secondvmManagement installation DVD.

23.Insert the second vmManagement DVD in the DVD drive



24.Click Next

A progress bar is displayed during the second DVD installation.

After DVD installation, the first backup is performed. This operation runs silently during up to 20 mn.Do not interrupt it.

At the end of the process, the installation wizard summary page is displayed:

Figure 7.10: Installation wizard summary page example

Validate the Reboot the server option if you want shutdown the system at the end of the process.

Do not validated the Reboot the server option, if you want to reboot to start the post-install wizard.25.Click Finish to exit the wizard

After reboot the Post Install wizard is started. See: server post installation on page 45.

Hardware Installation on page 25 Server post installation on page 45



Chapter

8 Post Installation

8.1 Post installation overviewOpenTouch server post installation (also called site installation) is performed at customer premises.

Post installation allows to configure network and application parameters of the OpenTouch BusinessEdition server.

The figure below shows an example of network environment. This example is the one illustrated in thescreens of section: OpenTouch Business Edition server post installation on page 45.

Target server with:

OpenTouch coreHostname: server1otIP address: 192.168.201.131DomainName: eudoc.euroscript.local

OmniPCX Enterprise virtual machineHostname: server1oxeIP address: 192.168.201.132

OmniVista 8770 virtual machineHostname: server18770IP address: 192.168.201.133

OMS virtual machineHostname: server1omsIP address: 192.168.201.137

DNS server (DNS resolution of OpenTouch, VmOXE, Vm8770, VmOMS) IP address: 192.168.201.200

GatewayIP address:192.168.201.249

License server (optional)Hostname: frbreseuro2licIP address: 192.168.201.150

Figure 8.1: OpenTouch environment example


8.2 OpenTouch Business Edition server post installationSoftware Installation on physical machineson page 27

OmniVista 8770 additional installation onpage 72

The post installation wizard is automatically started at first boot of the OpenTouch Business Editionserver (after software installation).

Note:It is possible to perform this operation on a test network, before modifying configuration at the customer site.

Note:In this wizard, default values can be set from the values defined during software installation.

The post installation wizard starts on the host console.

Procedure:

1. Boot the OpenTouch Business Edition server

The post installation wizard welcome page is displayed :

Figure 8.2: Post installation wizard welcome page2. Click Next. The Post-Installation Type window is displayed.

Chapter 8 Post Installation


3. Select Installation from scratch

Note:If upgrading from R2.0.2 or higher to R2.2 or higher, select Restore from archive. For more information, referto: Installing OpenTouch on page 226.

4. Click Next. The Local Settings Wizard page is displayed:



Figure 8.3: Local Settings wizard page example

Note:Default values are defined during software installation.

5. Enter local settings:

a. Keyboard: select your keyboard type

This parameter is used by the host operating system, OmniVista 8770 and the OmniPCXEnterprise virtual machine

Examples:

For a French keyboard select: french

For a German keyboard select: germanb. Country: select the customer country

This parameter is used by the OmniPCX Enterprise virtual machine and OmniVista 8770 server.c. Company: enter the customer company name

This entry must respect LDAP syntax (for example, no comma in the company name)

This parameter is used to configure the OmniVista 8770 application. The OmniVista 8770company directory is created under this Company name.

This parameter is also used by the OpenTouch applicationd. Time Zone: select the time zonee. D.S.T.: validate this option if daylight saving time (DST) applies to the time zone you have

selected earlierf. Click Next. The Host Network Settings page is displayed:



Figure 8.4: Host network setting wizard page example

Note:Default values are defined during software installation.

6. Enter host network parameters

a. General

• Host Name: enter the name of the OpenTouch Business Edition server (lower casemandatory)

• IP Address: enter the IP address of the OpenTouch Business Edition server• Subnet Mask: enter the subnet mask• Default Gateway IP Address: enter the IP address of the default gateway• Domain Name: enter the domain name of the OpenTouch server. Example:

eudoc.euroscript.local (lower-case mandatory)

The domain name to enter, depends on the used DNS server :

• If you use the customer DNS, enter the domain name of the customer (example ofdomain: mycompany.com). Lower-case is mandatory.

• If you use the local DNS (the DNS server embedded in the OpenTouch), create a subdomain (for example: ot), enter for example: ot.mycompany.com. You have also toconfigure the Forwarder 1 parameter (see below) with the customer DNS server address.

The reasons of this configuration are:

• A local DNS server does not forward requests for name belonging to its domain.• The OpenTouch DNS is configured only for OpenTouch elements.• Servers belonging to the customer network but outside the OpenTouch elements can

exist.



Note:If you configure the Domain Name without sub domain (for example: mycompany.com),OpenTouch clients which requests the local DNS never receives a positive answer for customerservers outside the OpenTouch elements.

b. DNS Server

• Local DNS server: validate this option if the local (embedded) OpenTouch Business Editionserver acts as DNS

Note:The Local DNS server can be used only when the OmniPCX Enterprise is not duplicated.

If this option is validated, the two following fields are displayed:

• Forwarder 1: enter the IP address of the first external DNS server where the local DNSserver forwards extra domain requests.

• Forwarder 2: enter the IP address of a second external DNS server. This server is usedwhen the DNS server specified above is not available.

When the local (embedded )DNS server is used, all OpenTouch Business Edition clients areconfigured with this embedded DNS server as a primary DNS server. This local DNS servermust be specified in DHCP server configuration.

• External DNS server: validate this option if the customer DNS is used.

If this option is validated, the two following fields are displayed:

• Server 1: enter the IP address of the external DNS server.

Note:When the OpenTouch server has been deployed using ALEDS (installation from the network), thisfield is automatically completed with the external DNS server address, as entered in the Engine tabof the ALEDS.

• Server 2: enter the IP address of a second external DNS server. This server is used whenthe first one is not available.

Important:The DNS server must be configured for resolution (forward and reverse resolution):

• OpenTouch server FQDN• OmniVista 8770 server FDQN• Mail server address• LDAP server address• NTP server, if an NTP server FQDN has been specified in NTP Server Setting• OmniPCX Enterprise Communication Server:

• No redundancy: Communication Server FQDN• Local redundancy: Communication Server main role FQDN• Spatial redundancy (i.e. where the two servers are located on different subnetworks):

each Communication Server FQDN• OXE-MS FQDN• OmniPCX Enterprise H.323 gateway FQDN

c. NTP Server

• Local Clock: select this check box when the host internal clock is not synchronized• External NTP Server: select this check box when the host clock is synchronized with an NTP

server. In this case, enter the IP address (or the name) of the NTP server (Server 1) andoptionally a second NTP server (Server 2). When two servers are configured, the local NTPprocess automatically selects the best server.

It is recommended to ensure that the firewall allows NTP requests.



The NTP client of each virtual machine is automatically configured to be synchronized on thehost NTP server.

d. Click Next. The High Availability Settings page is displayed:

Figure 8.5: High Availability Settings wizard page example (No High Availability)7. Leave the High Availability option disabled

Note:For more information on the installation of a new OpenTouch in an HA configuration, refer to document [35].

8. Click Next. The OmniPCX Enterprise page is displayed:



Figure 8.6: OmniPCX Enterprise wizard page example9. Enter OmniPCX Enterprise parameters:

The OmniPCX Enterprise page takes into account the CPU operation type:

• No redundancy:

1. Select the No redundancy radio button2. Complete the OmniPCX Enterprise parameters:

table 8.1: OmniPCX Enterprise parameters

Node Name Enter the node name of the OmniPCX Enterprise

CPU Host Name Enter the name of the OmniPCX Enterprise virtual ma-chine (lower case mandatory)

CPU IP Address Enter the IP address of the OmniPCX Enterprise virtualmachine

Subnet Mask Enter the subnet mask

Default Gateway Name Enter the default gateway name (lower case mandatory)

Default Gateway IP Address Enter the IP address of the default gateway

Network Number Enter the network number of the OmniPCX Enterprise vir-tual machine



Node Number Enter the node number of the OmniPCX Enterprise virtualmachine

SNMP Username Enter the username for SNMP

This account is used for SNMP communication betweenOmniPCX Enterprise and OmniVista 8770

SNMP Authentication Pass-word

Enter a password for this user

SNMP Encrypt Password Enter the encryption key for SNMP messages betweenOmniPCX Enterprise and OmniVista 8770.

SIP Trunk Group ID Enter the trunk group number of the SIP trunk group num-ber between Call Server and SIP Server.

In release prior to 1.3, this value was fixed to 1.

As of 1.3, you can choose a value between 0 and 1999.Default value: 1.

SIP TG Remote Network Enter the remote network number.

This number is free but it must be different from the Om-niPCX Enterprise network number.

In release prior to 1.3, this value was fixed to 15.

As of 1.3, you can choose a value between 0 and 255.Default value: 10

Notes:

• The CPU Host Name and the Node Name must be different• Show passwords: select this check box to display passwords in clear text

• Local redundancy:

The redundant CPU is hosted on an Appliance Server or a CS-2 (Common hardware CPU)located in the same subnetwork.

1. Select the local redundancy radio button2. Complete the fields described in Table 13. Click Next

An additional page is displayed to enter main CPU parameters and twin CPU parameters:



Figure 8.7: Main and twin OmniPCX Enterprise network settings for local redundancy wizardpage example

4. Complete the following fields:

• CPU Main:

• CPU Main name: enter the name of the CPU main• CPU Main IP Address: enter the IP address of the CPU main

• Twin OmniPCX Enterprise:

• Twin Name: enter the name of the twin CPU• Twin IP Address: enter the IP address of the twin CPU• Twin Subnet Mask: enter the subnet mask of the twin CPU

Note:The CPU Host Name, CPU Main Name, Node Name and the Twin Name must be different

• Spatial redundancy:

In this case, the redundant CPU is hosted on an Appliance Server or a CS-2 (Common hardwareCPU) located in a different remote subnetwork. For more information on spatial redundancy, seethe Alcatel-Lucent OmniPCX Enterprise Communication Server documentation.

1. Validate the spatial redundancy radio button2. Complete the fields described in Table 13. Click Next

An additional page is displayed to enter main CPU parameters and twin CPU parameters:



Figure 8.8: Main and twin OmniPCX Enterprise network settings for spatial redundancywizard page example

4. Complete the following fields:

• CPU Main:

• CPU Main name: enter the name of the main CPU when the main role is assigned tothe OmniPCX Enterprise virtual machine

• CPU Main IP Address: enter the IP address of the main CPU when the main role isassigned to the OmniPCX Enterprise virtual machine

• Twin OmniPCX Enterprise:

• Twin Name: enter the name of the twin CPU• Twin IP Address: enter the IP address of the twin CPU• Twin Subnet Mask: enter the subnet mask of the twin CPU• Twin Gateway Name: enter the name of the gateway used by the twin CPU• Twin Gateway IP Address: enter the IP address of the gateway used by the twin CPU• Twin Main name: enter the name of the main CPU when the main role is assigned to

the backup OmniPCX Enterprise hosted on the appliance server• Twin Main IP Address: enter the IP address of the main CPU when the main role is

assigned to the backup OmniPCX Enterprise hosted on the appliance server

Note:The CPU Host Name, CPU Main Name, Node Name, Twin Name and the Twin Main Name must bedifferent

10.Click Next

The OXE Media Services Virtual Machine Settings page is displayed



11.Enter the OXE Media Services Virtual Machine settings (OXE-MS):

• If no OXE-MS is requested, select off• If an OXE-MS is requested, select on and fill in the following parameters:

Host Name Enter the name of the oms (lower case mandatory, 15 char-acters maximum)

IP Address Enter the IP address of the OXE-MS

Subnet Mask Enter the subnet mask

Default Gateway IP Address Enter the IP address of the default gateway

Crystal board number Enter the crystal (shelf) number of the OXE-MS on the Om-niPCX Enterprise

root Password Enter the root password of the OXE-MS

admin Password Enter the admin password of the OXE-MS

Note:

When the OXE-MS is not activated at post-installation, it is possible to activate it later, using the command:

ot-config.sh --oms_active12.Click Next

The Applications Virtual Machine Settings page is displayed (the Applications Virtual Machinehosts the OmniVista 8770 application):



Figure 8.9: OmniVista 8770 parameters wizard page example13.Enter the 8770 parameters:

Configure network parameters for the vmManagement hosting the OmniVista 8770 application.

a. General:

• Host Name: enter the name of the vmManagement (lower case mandatory, 15 charactersmaximum)

• IP Address: enter the IP address• Subnet Mask: enter the subnet mask• Default Gateway IP Address: enter the IP address of the default gateway• OmniVista Network: enter the network number

This network number is used to create automatically the network with the specified number inthe Configuration application of the OmniVista 8770.

Default value: 0



Figure 8.10: Example of Network automatically created in the Configuration application• Management user accounts:

• Administrator Password: enter the password of the OmniVista 8770 administratoraccount (adminnmc account)

• ICE Password: enter the password of the ice account used to access the OmniVista8770 virtual machine (vmManagement)

14.Click Next

The OpenTouch Core Settings page is displayed:



Figure 8.11: OmniVista 8770 parameters to connect to the OpenTouch core server wizard pageexample

15.Enter the OpenTouch core parameters:

a. Host User Accounts parameters

• Show passwords: select this check box to display passwords in clear text• root Account Password: enter the root password• Maintenance Username: this user name is used for the maintenance account• Maintenance Password: enter the password for this user (eight characters minimum)

b. OpenTouch User Accounts parameters:

• Show passwords: select this check box to display passwords in clear text• Administrator Username: enter the user name used by OmniVista 8770 to connect to the

OpenTouch server with full administration rights

Note:8770 Administrator Username must be different from OpenTouch WBM Username.

• Administrator Password: enter the administrator password (8 characters minimum)• Profile Username: This user name is used by the OmniVista 8770 to connect to the

OpenTouch server with restricted rights for profile management.• Profile Password: enter the password for this user (8 characters minimum)• SNMP Engine ID: do not modify the default value• SNMP Username: This account is used for communication between OpenTouch core and

OmniVista 8770.• SNMP Authentication Password: enter the password for this user (8 characters minimum)• SNMP Encrypt Password: enter the encryption key for SNMP messages between

OpenTouch core and OmniVista 8770 (8 characters minimum).



Note:Account usernames must all be different and must not be admin, AdminNmc, otuser or any other existingaccounts defined in the system at this stage

c. Language parameters. For each of them, select either a language or Default. The Defaultoption refers to the language associated to the country configured in the Host Network Settingswizard page (see: Figure 4)

These parameters can be modified after the post-installation using the OpenTouch configurationwindow of OmniVista 8770 (see: Configuring the System TUI languages on page 171)

16.Click Next

The Advanced Communication Server Settings page is displayed:

17.Define the Advanced Communication Server Stack Name18.To allow remote users to join OpenTouch conferences from internet (or planning to do so in the

future), select Yes, and configure the conferencing service settings (FQDN and IP address) onOpenTouch server:

• Hostname: enter the conferencing service hostname• Domain Name: modify the domain name, if different from the OpenTouch domain name• IP Address: enter the conferencing service IP address, that must be different from the

OpenTouch IP address. This IP address must be located in the same subnetwork as theOpenTouch IP address

Caution:You may configure the conferencing service after post-installation, using the rehosting procedure.Note that using rehosting is the only way to configure the conferencing service if not done at post-installation time.

19.Click Next

The License Server Settings page is displayed:



Figure 8.12: License server settings wizard page20.Define your license server settings:

a. Select your license server type:

• Local: your license server is hosted in your OpenTouch server. No additional information isrequired

• External: your license server is hosted in a remote server.

An additional window is displayed to define the external license server:



Figure 8.13: License server settings wizard page example

Enter the external license server settings:

• Host name: enter the hostname of the license server• IP Address: enter the IP address of the license server• Domain Name: enter the domain name of the license server

Note:When an external license server is used, the license file must be copied on the external server and on thelocal server.

b. Click Next

The Licensing page is displayed:



Figure 8.14: Licensing wizard page example21.Typically, license files are stored on a USB key plugged on the local server.

Note:When the license file has been already installed with ALEDS, this item can be skipped.

All license files must be copied to a single directory.

License files include:

• OpenTouch license file with the .ice extension• OmniPCX Enterprise license files:

• The xxxx.swk file (the .swk extension must be written in lower case characters)• The offer_id.zip file (this file can be an empty zip file)• The hardware.mao file (this file can be an empty file)

• OmniVista 8770 license file with the .sw8770 extension

License installation procedure:

a. Plug in the USB key hosting the license filesb. Wait for a few secondsc. Click Browse... to select the license file directory

A browser opens



Figure 8.15: License browser windowd. Navigate to the license file directory:

• If licenses have been installed with the ALEDS, browse to /tmp/licences• If licenses are on a USB key, the USB key is typically mounted on the directory /media/

usbKey0e. Select the directory in which license files are stored

Note:The contents of directories is not displayed.

f. Click Open and select the Primary boxes corresponding to the license files to copy

The system checks whether license files exist in the selected directory and copies them on theOpenTouch server.

The system checks license validity and displays license status:



Figure 8.16: License status wizard page example

• If all statuses are OK, the Next button is available.• If a file status is Not OK or Missing, this means that the file is incorrect or missing. Fix the

problem before proceeding.

Caution:

If the skip option is used, the following operations must be performed after the post installation:

• A manual installation of the license files (see: Manual installation of licenses on page 75).• A manual configuration of the OmniPCX Enterprise and SIP connections (see: configuration

for SIP connections on page 95). If the OmniPCX Enterprise license files are not enteredhere, some declarations such as trunk group or the OmniPCX Enterprise are not performedautomatically. In this case, you must declare manually these objects on the OmniPCXEnterprise.

Note:When an external license server is used, the OK status indicates that the local file has been verified. Theconnection to the license server and its configuration is not tested.

22.Click Next and select your network security level:

a. Select the OFF radio button: pre loaded certificates are used. A confirmation window isdisplayed:



Figure 8.17: Certificate confirmation wizard page

Read the information on screen and confirm your choice.

The Legal mentions are:

"You have chosen to use a pre-loaded digital certificate for server & generic Certificate Trust Listto optimize the deployment" means that there is no need to sign the CTL on a signing 8082 MyIC Phone set. The signed CTL is automatically produced by the wizard and deployed on all 8082My IC Phone and 8012 Deskphone sets.

BEWARE: This choice is not recommended by ALE International, as it implies increased risks oftoll fraud, and unauthorized use of the services or functionalities on the system.

b. Select the ON radio button: a certificate type selection window is displayed.



Figure 8.18: Certificate type selection wizard page

Select the certificate type:

• To generate an internally autogenerated server certificate, select the Internal Certificate(autogenerated) radio button and select the Signature algorithm: SHA1 or SHA256 (defaultvalue)

For complementary information about SHA-2 based certificates, refer to the document [7](section SHA-2 TLS certificates).

• To install a PKCS12 certificate, select the External certificate (import pkcs#12 file) radiobutton. An external certificate selection window is displayed:



Figure 8.19: External certificate selection wizard page

1. Use the Browse.... button to select the certificate file2. Enter the appropriate secret passphrase (select show PassPhrase check box to display

the passphrase in clear)

Note:After post-installation, complementary operations are necessary for certificate management. For moreinformation on these operations, refer to OpenTouch Certificate management on page 77 below in thedocument.

23.Click Next

If selected, the external certificate is installed on the OpenTouch server

The OmniPCX Enterprise security page is displayed:



Figure 8.20: OXE security wizard page24.Select the security level for the OmniPCX Enterprise server:

• Level 0: no security function is activated. This configuration applies when a trusted IP network isused.

You must read the warning information and confirm your choice• Level 1: in this case the system requests a new password for the accounts root, swinst,

mtcl and adfexc.



Figure 8.21: OmniPCX Enterprise Security Levels page example

The new passwords must comply with password rules. For more information on password rules,see the OmniPCX Enterprise documentation on security

Note that the account name and password cannot be identical. For example: root is not a validpassword for the account root.

In addition, the system requests the maximum lifetime for the password of each account. Set tozero, the aging password option indicates that this option is deactivated for the correspondingaccount.

• Level 2: in this case new passwords are requested (as for Level 1). In addition the SSH functionis activated. The SSH function performs encryption of the calls between machines. For moreinformation on SSH , see the OmniPCX Enterprise documentation on security

• Level 3: in this case new passwords are requested (as for Level 1), in addition, the Call Serveris isolated from the IP network and can be reached by trusted hosts only

Trusted hosts can be declared later, using the netadmin tool.• Level 4: in this case:

• New passwords are requested (as for Level 1)• The SSH function is activated (as for Level 2)• The Call Server is isolated from the IP network (as for Level 3)

25.Click Next and define the media for backup storage (in the same way as with the ot-config.sh--storage command)

Note:Local backup is not recommended. USB or NFS backup should be preferred.

When LOCAL is selected, the storage media is the local disk of the OpenTouch server(path: /var/backup/). No configuration is required.



When USB is selected, a mount point is automatically created on the OpenTouch server (path: /media/usbdisk/), provided that a USB disk is plugged on the OpenTouch server.

When NFS is selected, additional parameters must be completed:

• NFS Host: enter the NFS server IP address• NFS Path: enter the access path to the shared NFS directory

Figure 8.22: Backup storage selection wizard page example26.Click Next

The parameter summary page is displayed.



Figure 8.23: Summary of parameters wizard page example27.Verify your configuration:

If settings are correct, click Next to display the System Update page.



Figure 8.24: System Update wizard page28.Perform one of the following:

• If no version update, click Finish to execute "post install". This operation takes 15-30 minutes.• If a version update is required, select the Update option and follow the instructions on screen.

At the end of the process, log in as root.

Software Installation on physical machineson page 27

OmniVista 8770 additional installation onpage 72

8.3 OmniVista 8770 additional installationOpenTouch Business Edition server post in-stallation on page 45

Accessing the OmniVista 8770 client (firstconnection) on page 75

8.3.1 Accessing the vmManagement (first connection)1. From the Virtual Machine Manager, connect to the vmManagement (for more information, refer

to: Connection to vmOXE, vmOMS and vmManagement virtual machines on page 185)2. Press Ctrl + Alt + Delete to log on3. Select the ice user and enter the default password (Sdfghjk1)

In case of partial setup, a temporary password may be activated in Windows. If Sdfghjk1 fails, useLetacla1



As the character corresponding to each key differs according to your type of keyboard, ensure thatthe characters you enter are correct

You are prompted to enter a new password.4. Enter a new password with:

• At least eight characters• At least one upper case character• At least one digit

OpenTouch Business Edition server post in-stallation on page 45

Accessing the OmniVista 8770 client (firstconnection) on page 75

8.3.2 Activating WindowsThe vmManagement hosts a Windows operating system. Its license must be entered to activate thesystem.

The Windows server is activated for 30 days only. You must activate the operating system before theend of this delay.

To activate the Windows license when the system is operating:

1. Navigate to Start menu > Execute2. Enter the slui command

A license window is opened displaying the Windows license status.

If the license is not active the Activate Windows online now button is available.3. Click Activate Windows online now4. Follow the instructions on screen and enter the product key

Note:The configuration of an Internet proxy may be required to access the Internet.

Note:When the software installation is performed in factory, the Windows operating system is activated before shipping.Skip this section.

8.3.3 Installing the OmniVista 8770 license manuallyThis procedure must be performed only when license installation has not been performed duringinstallation wizard (Figure 16).

The license file is named nmc.license and must be installed on vmManagement.

1. On vmManagement, open a session with the ice account2. Navigate to the C:\8770\etc directory3. Rename the nmc.license file to nmc.license.orig4. Copy your new license file to the C:\8770\etc directory5. Rename your license file: nmc.license6. Restart the OmniVista 8770 license server:

a. Launch the OmniVista 8770 Service Manager (Start>All Progams > Omnivista 8770 > Tools >Service Manager)

The Service Manager window is opened:



Figure 8.25: 8770 service managerb. In the Registered services area, select the NMC License server

Note:To select a service, click the service name (and not the check box). The selected service has a bluebackground.

c. Click Select

The Open window is displayed:

Figure 8.26: Service properties windowd. Validate the Write and Execute optionse. Click OK



f. On the Service manager window, click Stop

The NMC License server is stopping.g. Wait the service is stopped

8.3.4 Accessing the OmniVista 8770 client (first connection)

OmniVista 8770 additional installation onpage 72 Firewall on page 94

1. On vmManagement, open a session with the ice account2. Start the OmniVista 8770 local client

A connection window is open. You are prompted to select your server and port3. Select localhost in the Server Name field4. Enter 636 in the Port field5. Click OK

A login window is displayed.6. Enter adminnmc in the User Name field7. Enter superuser (default password) in the Password field

At the first connection, you are prompted to enter a new password.

Note:Your new password has a limited lifetime. Periodically, you will be prompted to change it.

8. Click OK

The OmniVista 8770 home window is opened.

You can also connect the OmniVista 8770 application from a remote OmniVista 8770 client. For moreinformation, see the corresponding product documentation.

OmniVista 8770 additional installation onpage 72 Firewall on page 94

8.4 Manual installation of licensesThis procedure must be performed only when license installation has not been performed during postinstallation (Figure 16).

8.4.1 OpenTouch Business Edition license file installationThe xxx.ice license file is a license file for the OpenTouch Business Edition server. This file mustcomply with:

• In a non-virtualized configuration, the ALUID and the host name of the OpenTouch server• In a virtualized configuration, the USB dongle and the host name of the OpenTouch server

8.4.1.1 Installation of the license file

To install the license file:

1. As root, copy the xxx.ice file on the server in the $LICENSES_HOME directory.

If you use an FTP transfer make sure the binary option is set.2. Restart OpenTouch Business Edition services:



• As root, enter: the service opentouchd restart command3. Check that the license server is running:

• Navigate to: /opt/Alcatel-Lucent/platform/flexlm• Enter the ./lmutil lmstat command

The status should be: license server UP

8.4.1.2 Verify activated licenses via WebAdmin

To check licenses:

1. Go to WebAdmin (https://[OT_FQDN]/WebAdmin)2. Log in, using the administrator account (otAdmin by default)3. Select System services > Applications > License4. Check that licenses are activated

8.4.2 OmniPCX Enterprise license installation

8.4.2.1 Installation of license files

The license installation procedure is the same as for the installation of a standalone OmniPCXEnterprise. See the OmniPCX Enterprise documentation for more information.

1. Open an mtcl session2. Copy the .swk file in the vmOXE, /DHS3dyn/BACKUP/OPS directory. Verify that the file

extension .swk is in lower case.

If you perform an FTP transfer make sure the binary option is set.3. Copy the hardware.mao file to the /DHS3dyn/BACKUP/OPS directory4. Copy the .zip file to the /DHS3dyn/BACKUP/OPS directory5. Open a swinst session6. Navigate to Expert menu (2) > OPS configuration (5) > Restore OPS from cpu

disk (2)7. Confirm the new license file installation

Installation dialog:...... Do you agree the new software keys (y/n): y..... Enter OPS working mode : 1=running 2=simulate (default is 1): 1..... ooo Job completed. at <26/07/10 10:49> ...ops 2.0.2: operation successfulTables updated. OK WITHOUT REBOOT !Do you wish to start the telephonic application (y/n, default y): nThe system is going down for reboot NOW !!

8. Wait until the OmniPCX Enterprise starts up9. Open an mtcl session10.Start the telephone application

Enter: RUNTELWait until the telephone application is started

8.4.2.2 Verify the license file

• Start the spadmin tool.

Enter: spadmin



• Select the Check active file coherency (3) option

The status is : File OK!

8.4.3 OmniVista 8770 license fileSee: Installing the OmniVista 8770 license manually on page 73.

8.5 OpenTouch Certificate management

8.5.1 Network security enabledIf your have enabled the network security by installing a customized server certificate during post-installation, it is necessary to perform these mandatory operations:

1. Create at least one 8088 Smart DeskPhone/8082 My IC Phone device that will execute CTLsignature operations (to create this device please refer to [3]: chapter "Implementing 8088 SmartDeskPhone and 8082 My IC Phone").

2. Perform CTL signature and CTL installation operations (please refer to [7] section " Deploying CTLon SIP devices")

Note:It is possible to configure/customize the server certificate after post-installation: see [7] section "Certificatemanagement".

8.5.2 Network security disabledIf you have disabled network security, you do not need a 8088 Smart DeskPhone/8082 My IC Phonedevice to execute CTL signature operations. The Master VHE device MAC address is automaticallyset to the default value 00:80:9F:7B:08:40. A CTL signed by this "virtual" set is used.

If you have to deploy the certificate, operate as detailed in: [7], section "Deploying the servercertificate").

8.6 Hotfix installationThis section outlines the generalities for installing a "Hotix". In this context, Hotfix refers to a smallsoftware modification. The installation details are provided with the hotfix package.

Launch ALFXXXX.bin and follow the instructions.

At the end of the hotfix installation, all services on the backup server are stopped.

Start the services using the standard command (service opentouchd start).

8.7 UPSA UPS can be installed to secure the main power supply.



UPS

OTBE ServerMGE UPS SYSTEMS

ellipse 1200

To Main

USB Status Cable

Figure 8.27: UPS Connection

The USB status cable transmits the UPS status to the OpenTouch server. When UPS batteries are low,this cable informs the server, which starts a clean shutdown procedure.

After installation, the OpenTouch server activates the UPS service.

To view the status of the UPS:

1. Open a root session2. Enter the upsc ups_on_usb@localhost command: all UPS parameters are displayed

The upsc [email protected] command returns only the current value of theselected parameter (battery.charge in this example)

If a message such as Error: Connection failure is displayed verify connections and restartthe ups service:

a. Enter the service ups stop command.b. Enter the service ups start command.

You can also check USB ports:

Enter the /sbin/lsusb command.(where the first letter corresponds to the letter "L"- lower case)

Example of command return:Bus 002 Device 001: ID 0000:0000Bus 002 Device 002: ID 0463:ffff MGE UPS Systems UPS <---UPS detectedBus 002 Device 003: ID 0000:0000Bus 001 Device 001: ID 0000:0000Bus 001 Device 002: ID 0529:0001 Addin Knowledge Systems HASP v0.06Bus 001 Device 003: ID 0000:0000



Chapter

9 Updating settings on an operationalsystem (rehosting)

This chapter describes how to modify settings on an operational system (after post-installation hasbeen performed).

Rehosting is forbidden in case of OmniPCX Enterprise with encryption units (IP Touch securitymodules).

Values defined during the post installation wizard can be modified.

9.1 PrerequisitesBefore you proceed with rehosting, ensure that the following conditions are met:

• The system is an OpenTouch Business Edition• The version of your OpenTouch Business Edition is equal or higher than 2.0.200.031• The licenses for OmniPCX Enterprise/OpenTouch Business Edition/OmniVista 8770 operate

correctly• All operations must be performed from the root account

9.1.1 Checking the system version1. Open a terminal2. Launch the command: getVersion all

This displays the details of product versions

All services must be started


9.1.2 Checking the license1. Open a terminal2. Launch the command: checkLicensing.sh

Figure 9.1: Licenses details example

Ensure all licenses are clear

9.1.3 Checking the service1. Open a terminal2. Launch the command: service opentouchd status

Chapter 9 Updating settings on an operational system (rehosting)


Figure 9.2: Status of services example

All services must be started

9.1.4 Estimated timeThe rehosting procedure takes approximately ninety minutes.

9.1.5 BackupCaution:Ensure you make a data backup before starting with rehosting.

Backups can be made with:

• The command: otbr.sh backup to make a backup of your data• The command: otbr.sh backup VMall to make a copy of your VM with your password,

Windows license, window configuration, etc.• The tool Clonezilla available on the web.

For more information on image creation using Clonezilla, refer to TC1625 (https://businessportal.alcatel-lucent.com/kcs?articleID=TC1625)

9.2 Rehosting infrastructureThe following paragraphs describe how to rehost the network infrastructure (hostname, IP, mask,gateway of OpenTouch, OmniPCX Enterprise, OmniVista 8770, OXE-MS) of your OpenTouch BusinessEdition.

9.2.1 Starting the rehosting1. Open a terminal2. Launch the command: ot-config.sh --rehost



https://businessportal.alcatel-lucent.com/kcs?articleID=TC1625

https://businessportal.alcatel-lucent.com/kcs?articleID=TC1625

Figure 9.3: ot-config.sh result example3. Select Y

All VM connectivity must be set to OK

Figure 9.4: VM connectivity details example4. Enter the password of the Windows account for OmniVista 8770 Virtual Management

This displays a confirmation and a warning insisting on the need for backup

5. Click OK



9.2.2 Rehosting the OpenTouch infrastructureModify the Host Network Parameters (hostname, IP address, subnet mask, default gateway, IPaddress, domain name)

Figure 9.5: Host network settings example

Note:You may change one single parameter or all of them

Caution:If you want to modify the NTP only, refer to Modification of the Network Time Protocol (NTP) on page 92.

9.2.3 Rehosting the OmniPCX Enterprise1. Modify the OmniPCX Enterprise IP and FQDN Parameters (node name, CPU hostname, CPU IP

address,subnet mask, default gateway name, default gateway IP address)



Figure 9.6: OmniPCX Enterprise settings example2. Click Next3. In case of Local Redundancy, complete the fields CPU Main Name, CPU Main IP Address, and

Twin Name, Twin IP Address, Twin Subnet Mask



Figure 9.7: Main and twin OmniPCX Enterprise network settings for local redundancy example4. Click Next5. In case of Spatial Redundancy, complete the fields CPU Main Name, CPU Main IP Address and

Twin Name, Twin Subnet Mask, Twin Gateway Name, Twin Gateway IP Address, Twin MainName, Twin Main IP Address



Figure 9.8: Main and twin OmniPCX Enterprise network settings for spatial redundancy example


6. Click Next

If you are using the OmniPCX Enterprise DHCP, or if you change hostnames, you must change the IPaddresses range after the rehosting procedure is finished:

1. In the OmniPCX Enterprise VM configuration tool (mgr), select DHCP Configuration > CPU MainSubnetwork > IP Addresses Range (local subnet)

Example:Node Number (reserved) : 1 DHCP Configuration : 1 Instance (reserved) : 1First address in range : 10.231.0.100End of address range : 10.231.0.200

2. Change the Range first address3. Change the Range last address4. Press Ctrl + V to validate5. Select DHCP Configuration > Apply modifications

9.2.4 Rehosting the OXE-MS virtual machine1. Modify the OXE Media Services virtual machine settings (new hostname, IP address, subnet mask,

default gateway IP Address



Figure 9.9: OXE Media Services Virtual Machine settingsexample


Caution:Do not change the value for the field Crystal board number

2. Click Next

9.2.5 Rehosting the OmniVista 8770 application virtual machine1. Modify the OmniVista 8770 virtual machine settings (new hostname, IP address, subnet mask,

default gateway IP Address)



Figure 9.10: OmniVista 8770 parameters example


2. Click Next

9.2.6 Rehosting the Advanced Communication Server

9.2.6.1 Stack name settings

1. Modify the Advanced Communication Server settings (stack name, main node ID)



Figure 9.11: OmniTouch 8460 ACS settings example (stack name)

Note:The stack name and the main node ID correspond to the federation of several ACS built in parallel.

Caution:All scheduled conference are lost when you change these values.

2. Click Next

9.2.6.2 Conferencing Service Address (ACS Cluster) settings

At this stage, you can configure the conferencing service, if not done at post-installation time, or modifythe parameters of the conferencing service defined at post-installation.

Caution:Note that using rehosting is the only way to configure the conferencing service if not done at post-installation time.

1. Modify the Conferencing Service Address settings (new hostname, domain name, IP address)



Figure 9.12: OmniTouch 8460 ACS settings example (Conferencing Service Address)


Caution:If you change or add a new value in these parameters, verify that the IP/hostname responds correctlyto a ping. if this is not the case, reboot the server.

2. Click Next

9.3 Rehosting the Domain Name Server (DNS)In case of an internal DNS, all parameters are rehosted automatically. It is possible to change thisinternal DNS to an external DNS, provided this external DNS exists and can be reached.

Caution:

If you decide to change the DNS to an external DNS, you must: .

1. Change the value of the new DNS, using the ot-config.sh command2. Enter all future IP and hostnames in the new DNS

If the external DNS is not declared previously in the OmniVista 8770, it will be necessary to reboot all 8082My IC Phones, as the new DNS value cannot be taken into account automatically.

To rehost the DNS:

1. Open a terminal2. Launch the command: ot-config.sh --dns

This command modifies the DNS declared in Eco system > IT Server, on the local host, the OXE-MS, the OmniPCX Enterprise and the OmniVista 8770.



Notes:

• Changing an external DNS change to an internal DNS is allowed• Changing an internal DNS to external DNS is allowed

9.4 Externalization of the Flex serverCaution:You may externalize the Flex Server (from an internal Flex server to external Flex server). The reverseprocedure (external Flex server to internal Flex server) is not authorized.

1. Open a terminal2. Launch the command: ot-config.sh --external_flex

Caution:All OpenTouch services must be stopped



Figure 9.13: Post installation example3. Click Next4. Enter the parameters of your Flex server (hostname, IP address, domain name)

Figure 9.14: License server settings example5. Click Next and validate your modifications

9.5 Modification of the Network Time Protocol (NTP)1. Open a terminal



2. Launch the command: ot-config.sh --ntp

3. Select Y4. Select N at the question Do you want to use local clock?5. Enter the IP addresses of your NTP servers 1 and 2

/etc/ntp.conf written/etc/ntp/step-tickers updatedActivating ntpd service at boot time.Restarting ntpdShutting down ntpd: [ OK ]Starting ntpd: [ OK ]ot-config.sh is completed.



Chapter

10 Connection Configuration

In this chapter, the OmniVista 8770 and the Alcatel-Lucent OmniPCX Enterprise CommunicationServer servers are configured. These servers must be loaded and started before configuration. Formore information, see the corresponding product documentation.

10.1 OmniVista 8770 connectionFor OpenTouch environment, the following creations are automatic:

• Network and subnetwork• OpenTouch server• OmniPCX Enterprise creation• OpenTouch topology creation

At first connection, the following synchronizations are recommended:

• Synchronization between the OmniVista 8770 and the OmniPCX Enterprise:

1. Check that the OmniPCX Enterprise is started2. Launch the OmniVista 8770 client3. Right click the OmniPCX Enterprise in the network tree structure, and select Synchronization >

Complete > Global4. In the Create multiple tasks in the Scheduler... window, click Apply5. Select Display the parameters of the task and go to the Status tab

• Synchronization between the OmniVista 8770 and the OpenTouch:

1. Right click on the OpenTouch in the network tree structure, and select Synchronization >Complete > Global

2. In the Create multiple tasks in the Scheduler... window, click Apply3. Select Display the parameters of the task and go to the Status tab

For information on synchronization, see the OmniVista 8770 documentation.

As of OpenTouch R2.1, three tabs are available for configuration. The Features tab provide a taskoriented display of the objects to configure. Each object is presented by feature in the order in whichthey must be configured after system installation. Several instances can be viewed at different placesof the tree, if they need to be configured at different moments of the configuration process.

10.2 Firewall

first connection on page 75 Codec configuration on page 102

Ports used by the OpenTouch server must be authorized by the firewall.

For the list of used ports, see [11].

Ports used by the Alcatel-Lucent OmniPCX Enterprise Communication Server are described in theOmniPCX Enterprise documentation.

Ports used by the Alcatel-Lucent OmniVista 8770 Network Management System are described in theOmniVista 8770 documentation (Security guide > Deploying the OmniVista 8770 in a Secure NetworkConfiguration).


first connection on page 75 Codec configuration on page 102

10.3 OmniPCX Enterprise configuration for SIP connectionsThe following paragraphs present the configuration of SIP connections between the OmniPCXEnterprise and the OpenTouch server.

This configuration can be performed on vmOXE via the mgr tool or on vmManagement via theConfiguration application of the OmniVista 8770 server.

Only relevant parameters are presented here. For all other parameters, leave the default value.

Note:This configuration is automatically created at the OpenTouch Business Edition server installation.

10.3.1 Required information• <SIP_TG_ID>: SIP trunk group number between Call Server and SIP Server• <RN_ID>: remote network number of the SIP Server• <Node_ID>: Call Server node number• <EXT_GW_ID>: SIP external gateway number. This external gateway leads to the SIP Server.• <EXT_GW_VoiceMail_ID>: SIP external gateway number defined for voice mail.• <OT-FQDN>: FQDN of the OpenTouch server• <OT_IP_ADDR>: IP address of the OpenTouch server• <DNS_IP_ADDR>: IP address of the DNS server

10.3.2 Trunk group for the SIP gatewayA trunk group is automatically created.

1. Select: Trunk Groups2. Verify the following attributes:

Trunk Group ID Trunk ID number defined at post installation

Default value: 1

In this configuration procedure this number is called:<SIP_TG_ID>

Trunk Group Name Enter the trunk group name for display only

Enter SIP for example.

Remote Network Remote Network ID defined at post installation

Default value: 10

In this configuration procedure this number is called: <RN_ID>

Node number Displays the node number defined at post installation:<Node_ID>

Q931 Signal variant ABC-F

T2 Specification SIP

Chapter 10 Connection Configuration


3. Confirm your entries

10.3.3 Set the trunk group local propertiesNote:This object is automatically created, verify parameters.

1. Select: Trunk Groups > Trunk Group2. Review/Modify the following attributes:

Trunk Group ID Enter the trunk group number (<SIP_TG_ID>)

End to End dialing No

DTMF End to End signal. No


10.3.4 SIP gateway configurationA SIP gateway is created by default.

1. Select: SIP > SIP Gateway2. Verify the following attributes:

SIP Subnetwork Remote Network ID defined at post install

Default value: 10

In this configuration procedure this number is called: <RN_ID>

SIP Trunk Group Trunk ID number defined at post install

Default value: 1

SIP Subscribe Min Duration 600

DNS local domain name Enter the DNS local domain name

In this configuration procedure this value is called: <mydo-main.com>

DNS type Enter DNS type:

• DNS A: the SIP gateway sends DNSA requests to resolvea domain name into one single IP address (default typeafter post installation)

• DNS SRV: the SIP gateway sends DNSSRV requests toresolve a domain name into one or several names or IPaddresses

SIP DNS1 IP Address Enter primary DNS address

In this configuration procedure this number is called:<DNS_IP_ADDR>

SIP DNS2 IP Address Enter secondary DNS address

Dynamic Payload type for DTMF Enter 101




10.3.5 SIP proxy configurationDefault settings of the SIP proxy may be wrong with certain versions of OpenTouch. The followingparameters must be checked and modified if necessary.

1. Select: SIP > SIP Proxy2. Review/modify the following attributes:

Minimal authentication method Select: SIP Digest

Only authenticated incomingcalls

Select: True


10.3.6 SIP registrar configurationNote:This object is automatically created, verify parameters.

1. Select: SIP > SIP Registrar2. Review/modify the following attributes:

SIP Min Expiration Date Enter: 600


10.3.7 SIP external gateway configurationCaution:In the following configurations, the values for the parameters SIP Remote domain and Belonging Domainmust not exceed fifty characters.

10.3.7.1 External gateway for OpenTouch SIP server

On a new OpenTouch® Business Edition installation, an external gateway for the OpenTouch SIPserver is automatically created. However, default settings may be wrong with certain versions ofOpenTouch. The following parameters must be checked and modified if necessary.

1. Select: SIP > SIP Ext Gateway2. Verify the following attributes:

SIP External Gateway ID Enter the SIP external gateway identifier

In this configuration procedure this number is called:<EXT_GW_ID>.

Gateway Name Enter the gateway name for display only

Enter To OpenTouch for example

SIP Remote domain Enter the FQDN of the OpenTouch server

In this configuration procedure this FQDN is called: <OT-FQDN>

SIP Port Number Enter: 5260



Transport Type Select: TCP

Belonging Domain • Leave blank, in case of OmniPCX Enterprise localredundancy or no redundancy

• Enter the FQDN of the OpenTouch server in case ofOmniPCX Enterprise spatial redundancy configuration, thevalue must be identical to the SIP Remote domainparameter defined above.

Supervision timer Enter 380

OPTIONS messages are sent every 380 seconds to monitorthe availability of the OpenTouch SIP Server. If no answer isprovided after Timer E expiration (3 seconds in the default con-figuration), the external gateway goes out of service and in-coming calls to OpenTouch users overflow to the attendantgroup or an overflow number (if configured).

Trunk group number Enter the trunk group number defined for SIP gateway, with theSIP specificity associated to variant Q931 : ABCF All country(<SIP_TG_ID>)

SIP DNS1 IP Address Enter the IP address of the DNS server

In this configuration procedure this IP address is called:<DNS_IP_ADDR>

SDP in 18x Select: False

For incoming calls, the OmniPCX Enterprise SIP Gatewaydoes not provide provisioning answer 180 or 183 with SDP forthe first INVITE transaction. The OmniPCX Enterprise does notdeliver a voice guide or Ring Back Tone to OpenTouch user inthe early media phase of the SIP dialog.

Minimal authentication method Select: SIP None

No authentication is required from the OpenTouch server

Ignore inactive/black hole Select: True

RE-INVITE message sent by the OpenTouch SIP server withSDP containing an active media line, port different from 0, andIP Address set to 0.0.0.0, will be acknowledged with 200 OKbut ignored by Call Handling, meaning the established RTPflow is maintained.



Contact with IP address Select:

• True in case of OmniPCX Enterprise spatial redundancy

The IP address of the main Call Server is provided in thecontact field. After switchover the value changes to the twinMain IP address.

• False in case of OmniPCX Enterprise local redundancy orno redundancy

The FQDN is provided in the contact field.

Dynamic Payload type forDTMF

Enter 101

Outbound Calls 100 REL Select: Supported

For outgoing calls to an OpenTouch user or application, thefirst INVITE message is sent with the header Supported asso-ciated to service 100 Rel, indicating that the Call Server canhandle a provisioning answer 180/183 with SDP and can senda PRACK message for acknowledgement. The OpenTouchMedia Server, AMS, can deliver a voice guide or ring back toneduring the early media phase of the first INVITE transaction. Atconnection of the call, an UPDATE message will be generatedby the OpenTouch SIP Server to provide the connected DeviceIP Address and port.

Incoming Calls 100 REL Select: Not requested

For incoming call starting with INVITE transaction provisioning,answer 180/183 does NOT contain the header Required asso-ciated to service 100 Rel. PRACK or UPATE messages are notaccepted in the early media phase of the SIP dialog. It match-es with the setting SDP in 18x set to False.

Gateway type Select: ICE type

Provides a proprietary field Alcatel_CSBU to implement ad-vanced services over the SIP protocol between the OmniPCXEnterprise and OpenTouch server.

Proxy identification on IP ad-dress

Select: True

Outbound calls only Select False

The calls are accepted on the SIP Server External Gateway.

Support UTF8 characters set Select: YES

Support CSTA User-to-User Select: YES

Video support profile Select: Un Restricted




10.3.7.2 External gateway for voice mail

On a new OpenTouch® Business Edition installation, an external gateway for the OpenTouch localstorage voice mail is automatically created. However, default settings may be wrong with certainversions of OpenTouch. The following parameters must be checked and modified if necessary.

1. Select: SIP > SIP Ext Gateway2. Review/modify the following attributes:

SIP External Gateway ID Enter the SIP external gateway number

In this configuration procedure this number is called:<EXT_GW_VoiceMail_ID>.

Gateway Name Enter the gateway name for display only

Enter To VoiceMail for example

SIP Remote domain Enter the FQDN of the OpenTouch server

In this configuration procedure this FQDN is called: <OT-FQDN>

SIP Port Number Enter: 5040

Transport Type Select: TCP

Belonging Domain • Leave blank, in case of OmniPCX Enterprise localredundancy or no redundancy

• Enter the FQDN of the OpenTouch server In case ofOmniPCX Enterprise spatial redundancy configuration, thevalue must be similar to the SIP Remote domainparameter defined above.

Supervision timer Enter 380

OPTIONS messages are sent every 380 seconds to monitorthe availability of the OpenTouch SIP Server. If no answer isprovided after Timer E expiration (3 seconds in the default con-figuration), the external gateway goes out of service and in-coming calls to OpenTouch users overflow to the attendantgroup or an overflow number (if configured).

Trunk group number Enter the trunk group number defined for SIP gateway, withspecificity SIP associated to Q931 variant: ABCF All country(<SIP_TG_ID>)

SIP DNS1 IP Address Enter the IP address of the DNS server

In this configuration procedure this IP address is called:<DNS_IP_ADDR>



SDP in 18x Select: False

For incoming calls, the OmniPCX Enterprise SIP Gatewaydoes not provide provisioning answer 180 or 183 with SDP forthe first INVITE transaction. The OmniPCX Enterprise does notdeliver a voice guide or Ring Back Tone to the OpenTouchuser in the early media phase of the SIP dialog.

Minimal authentication method Select: SIP None

No authentication is required from the OpenTouch server

Ignore inactive/black hole Select: True

The RE-INVITE message sent by the OpenTouch SIP serverwith SDP containing an active media line, port different from 0,and IP Address set to 0.0.0.0, is acknowledged with 200 OKbut ignored by Call Handling, meaning the established RTPflow is maintained.

Contact with IP address Select:

• True in case of OmniPCX Enterprise spatial redundancy

The IP address of the main Call Server is provided in thecontact field. After switchover the value changes to the twinMain IP address.

• False in case of OmniPCX Enterprise local redundancy orno redundancy

The FQDN is provided in the contact field.

Dynamic Payload type forDTMF

Enter 101

Outbound Calls 100 REL Select: Supported

For outgoing calls to an OpenTouch user or application, thefirst INVITE message is sent with the header Supported asso-ciated to service 100 Rel, indicating that the Call Server canhandle a provisioning answer 180/183 with SDP and can senda PRACK message for acknowledgement. The OpenTouchMedia Server, AMS, can deliver a voice guide or ring back toneduring the early media phase of the first INVITE transaction. Atconnection of the call, an UPDATE message is generated bythe OpenTouch SIP Server to provide the connected Device IPAddress and port.

Incoming Calls 100 REL Select: Not requested

For incoming call starting with INVITE transaction provisioning,answer 180/183 does NOT contain header Required associ-ated to service 100 Rel. PRACK or UPATE messages are notaccepted in the early media phase of the SIP dialog. It match-es with the setting SDP in 18x set to False.



Gateway type Select: ICE type

Provides a proprietary field Alcatel_CSBU to implement ad-vanced services over the SIP protocol between the OmniPCXEnterprise and the OpenTouch server.

Proxy identification on IP ad-dress

Select True

Outbound calls only Select True

With this configuration the two external gateways are associ-ated to the same Remote Domain Name but only the externalgateway from the SIP server is used to handle the call. Withthis setting set to true, no incoming call is accepted on thevoice mail external gateway.

Support UTF8 characters set Select: YES

Support CSTA User-to-User Select: YES


10.3.8 Configuring SIP video settingsThis configuration is required to support video on OmniPCX Enterprise. All configuration is described inthe document [15] (section: Configuring video settings for Connection users using SIP devices).

10.3.9 Trusted address configurationNote:This object is automatically created, verify parameters.

1. Select: SIP > Trusted IP Address2. Review/modify the following attributes:

Trusted address Enter the IP address of the OpenTouch server(<OT_IP_ADDR>)


10.3.10 Codec configuration

Firewall on page 94 DPNSS prefix configuration on page 103

1. Select: System > Other System Param. > Compression Parameters2. Review/modify the following attributes:

System Option Select: Compression Type

Compression Type Select: G729

3. Review/modify the following attributes:



System Option Select: Multi. Algorithms for Compression

Multi. Algorithms for Compres-sion

Select: False


Note:

Codec configuration also depends on the Intra (or Extra) IP domain Coding Algorithm parameter (object: IP >IP domain).

When the Default Voice Coding Algorithm parameter is set to Default, the codec type (with or withoutcompression) is defined by the Default Voice Coding Algorithm parameter (object: IP > INT/IP Parameters).

For more information on the compression algorithm, see the OmniPCX Enterprise documentation.

Firewall on page 94 DPNSS prefix configuration on page 103

10.3.11 DPNSS prefix configuration

Codec configuration on page 102 Overview on page 106

To avoid transfer problems in a loop constituted by a first Conversation user, a Connection user then asecond Conversation user, perform the following configuration:

10.3.11.1 Creating the DPNSS Prefix

1. Select Translator > Prefix Plan2. Create the following attributes:

Number Enter the DPNSS address of the local node

This number must be a free number of the numbering plan

Prefix Meaning Select: Local features.

Local Features Select: PCX address in DPNSS.


10.3.11.2 Routing Optimization

If DPNSS prefixes are used, the system option for routing optimization must be enabled.

1. Select System2. Review/modify the following attribute:

DPNSS Parameters

Routing Optimization Select YES

Default value: NO

3. Confirm your entry

Codec configuration on page 102 Overview on page 106



10.4 OXE-MS configuration on the OmniPCX EnterpriseThe following paragraphs present the configuration of the OXE Media Services (OXE-MS) on theOmniPCX Enterprise. This configuration is automatically performed when the OXE-MS is activated atthe OpenTouch Business Edition server post-installation. It can be used for verification.

This configuration can be performed on vmOXE via the mgr tool or on vmManagement via theConfiguration application of the OmniVista 8770 server. The following paragraphs present theconfiguration from the OmniPCX Enterprise configuration window of the OmniVista 8770.

Only relevant parameters are presented here.

Note:

The OXE-MS reboots until it can connect with the OmniPCX Enterprise, and declare itself under Shelf/board towhich it is assigned. This means that:

• The OXE-MS must be declared in the OmniPCX Enterprise• The MAC address of the OXE-MS Virtual Machine must be correct• The telephone must be started on the OmniPCX Enterprise

10.4.1 Checking parameters on OXE-MSTo check the OXE-MS MAC address and IP parameters:

1. Log in as root on vmOMS2. Enter the omsconfig command

The MAC address and IP parameters are displayed

10.4.2 OXE-MS declarationThe OXE-MS is declared as a media gateway in the OmniPCX Enterprise:

1. From the OmniPCX Enterprise configuration window of the OmniVista 8770, navigate to: MediaGateway

2. Verify the following attributes:

Main shelf Address Rack address of the OXE-MS media gateway (1 by default)

Main shelf type Displays Media Gateway Large

OXE Media Server Displays YES

10.4.3 OXE-MS parameter configurationThe OXE-MS rack declaration results in the automatic creation of a GD-3 board in the controllerposition (position 0).

1. From the OmniPCX Enterprise configuration window of the OmniVista 8770, navigate to: Shelf >Board


Shelf address Number of the OXE-MS media gateway (1 by default)

Board Address Displays 0 (controller position)



Interface Type Displays GD3

Caution:Do not modify this board type.

Max simultaneous voiceguides

Maximum number of simultaneous voice guides.

This value must comply with PCM rules. See note below.

N-part conference type Type of N-party conference

No. of Compressors for IPDevices

Number of compressors (VoIP channels) allowed for IP devices.

This number must be compatible with hardware resources.

Default value: 120

Max. number of 3-part con-ferences

Number of 3-party conferences allowed on the OXE-MS mediagateway.

Default value: 40

To take the modified value into account, the OXE-MS media gate-way must be restarted.

10.4.4 OXE-MS Ethernet (MAC) address configurationThe Ethernet (MAC) address of the OXE-MS Virtual Machine must be entered in the OXE-MS Ethernetparameters. The IP parameters (IP Coupler Address, IP Netmask, Default Gateway IP Address)must not be entered at this stage, they will be entered when the OXE-MS is started.

1. From the OmniPCX Enterprise configuration window of the OmniVista 8770, navigate to: Shelf >Board > Ethernet Parameters


Shelf address Number of the OXE-MS media gateway

Board Address Displays 0 (controller position)

Interface Type Displays GD3

Board Ethernet Address Displays the MAC address of the OXE-MS Virtual Machine



Chapter

11 OpenTouch MultimediaConferencing and Collaboration

11.1 OverviewOpenTouch Multimedia Services - Connec-tion Configuration - DPNSS prefix configura-tion

Dialing plan overview on page 164

This section covers the initial configuration required to allow the OpenTouch Multimedia Conferencingand Collaboration solution to operate with the OpenTouch. This includes the configuration for SIPconnections to and from the OpenTouch Multimedia Conferencing and Collaboration (also called ACS).See: Process overview on page 106.

For a complete configuration of the OpenTouch Multimedia Conferencing and Collaboration, refer tothe OpenTouch Administrator Manual [3].

The OpenTouch Multimedia Conferencing and Collaboration solution is fully integrated to theOpenTouch and installed with the OpenTouch on the same server. To be able to share certain types ofdocuments from OpenTouch clients such as OTC PC or OTC Web, the installation of a DocumentConverter Software (DCS) is required. For more information, see: Installing a Document ConverterSoftware on page 112.

Note:For readability purposes, the term ACS refers to the OpenTouch Multimedia Conferencing and Collaborationsolution in the rest of the document.

11.1.1 Required information• <ACS_Number>: number used to access the ACS conference bridge• <Ext_GW_ID>: SIP external gateway identifier (that is the OpenTouch server identifier) defined at

the OmniPCX Enterprise configuration for SIP connections. For more information, refer to:Document [1] Connection Configuration - External gateway for OpenTouch SIP server (in case ofOpenTouch Business Edition) orOpenTouch Multimedia Services - Connection Configuration -External gateway for OpenTouch SIP server (in case of OpenTouch Multimedia Services).

11.1.2 Process overviewThe ACS configuration consists in:

• Declaring the ACS in the OmniPCX Enterprise on page 106• Declaring the ACS in the OpenTouch server on page 107• Configuring the ACS settings on page 107• If required, Installing a Document Converter Software on page 112

11.1.3 Declaring the ACS in the OmniPCX EnterpriseThe ACS must be declared in the OmniPCX Enterprise as an external voice mail.

1. Select: Applications > External Voice Mail2. Create an external voice mail with the following attributes:


Voice Mail Dir.No. Enter the voice mail directory number

In this configuration procedure this number is called:<ACS_Number>.

Sub Type Select: Private

Directory Name Enter the ACS name for display only

Enter Conferencing ACS for example

External Gateway number Enter the external gateway number (<EXT_GW_ID>)

See: OpenTouch Multimedia Services - ConnectionConfiguration - SIP external gateway configuration


11.1.4 Declaring the ACS in the OpenTouch serverThis declaration is performed via the OmniVista 8770.

1. In the Configuration application, navigate to the OpenTouch server2. Select the OpenTouch server, right click and select Configure

The OpenTouch configuration page is displayed.3. Navigate to System services > Applications > Telephony Settings > Vocal applications > TUI

Application4. In the list of TUI applications look for the CONFERENCING type5. Modify the Number to <ACS_Number>6. Validate

11.1.5 Configuring the ACS settings

11.1.5.1 Accessing the ACS administration console

To configure the ACS settings, access the administration console as follows:

1. Open a session on the OmniVista 87702. Start the Configuration application3. In the Network window, select your OpenTouch node4. Right click and select WBM

The WBM logging page is displayed:

Chapter 11 OpenTouch Multimedia Conferencing and Collaboration


Figure 11.1: WBM logging page5. Enter your username and password.

Use the otAdmin credential configured at the OpenTouch server post installation. Other accountscan be created.

The WBM home page is displayed:

Figure 11.2: WBM home page6. Navigate to Users and devices > System Configuration

The ACS administration console is displayed:



Figure 11.3: Home page of the ACS administration console

11.1.5.2 Configure system options

1. Navigate to Configuration > System Options

When you open the home page for the first time, you can also access the system options by clickingthe message: The System Options page needs to be completed. Once configured, the messagedoes not appear in the home page anymore.

2. Verify and complete the parameters according to your needs.

The meaning of system options is detailed in the OpenTouch Administration Manual [3].3. Click Save

11.1.5.3 Configuring call routing rules

Call routing (DAS rules) applies to dialed digits before the call is processed by the ACS

1. Navigate to: Configuration > Advanced Settings > Edit DAS Rules2. In the Domain field, use the drop-down menu to select the domain to which the rules must be

applied3. Enter the specific rules you want the OpenTouch Multimedia Conferencing and Collaboration to

follow in processing dialed digits

The rules are applied in order, one after the other – the output of each rule is the input to the nextone. The result is used as the dialed digits to be processed by the OmniTouch 8460 ACS callprocessing.

Check that the following rules are declared before the rule adding 000 for externalinternational outgoing calls. If not, add them. This is necessary for OpenTouch Conversationclients to operate correctly with the ACS.

• s/^\+M/M/



• s/^\+N/N/• s/^\+V/V/Example of DAS rule for France:

Rules Comment

s/^\+[xX]?(\d{3,6})$/\1/ When a string starts with “+x” or “+” followed by from 3to 6 digits according to the dialing plan, the leading +x isremoved.

This rule is applied for internal calls:

before: +x123 -> after: 123

before: +12345 -> after: 12345

before: +123456 -> after: 123456

s/^\+(\d{3,6})$/+x\1/ When a string starts with “+” followed by from 3 to 6 dig-its according to the dialing plan, the leading +x is added:

before: +123 -> after: +x123

before: +123456 -> after: +x123456

s/^[\+]?x// before: +x123 -> after: 123

before: x123nn -> after: 123nn

s/^\+330/00/ before: +330122334455 -> after: 00122334455

s/^\+M/M/ necessary for OpenTouch Conversation clients to oper-ate correctly with the ACS

s/^\+N/N/ necessary for OpenTouch Conversation clients to oper-ate correctly with the ACS

s/^\+V/V/ necessary for video on OpenTouch Conversation clientsin conference (single client)

s/^\+/000/ before: +78121234455 -> after: 00078121234455

that is canonical number is translated as:

0 – external trunk

00 – international call prefix

international number:

(<country code>+<area code>+<local number>)

4. Click Save

For more information on the DAS rule configuration, refer to the OpenTouch Administrator Manual [3].

11.1.5.4 Configuring phone formatting rules

1. Navigate to: Configuration > Advanced Settings > Phone Formatting Rules



2. In the Extension pattern field enter : /^\s*\+*[xX]?(\d{3,6})\s*$/In this rule, the underlined digit must be equal to the maximum size of the device number orextension (internal dial plan) +1.

Example: if your dialing plan defines a maximum number of 5 digits for device number, enter 6.3. Click Save

11.1.5.5 Declaring the OpenTouch server as SIP proxy

Create a new SIP proxy:

1. Navigate to: Configuration > SIP Proxies2. In the field Default Outbound SIP Proxy the IP address of the OpenTouch server is filled in

automatically3. In the field Default Outbound SIP Proxy port enter: 52604. In the field Realm enter the FQDN of the OpenTouch server5. In the field Server IP address enter the IP address of the OpenTouch server6. In the field Port enter 52607. Click New to add a new SIP Proxy entry8. Click Save and Apply All Settings



Figure 11.4: SIP proxy configuration

Configure the SIP proxy to access the conference bridge:

1. Click Users

The Add or Edit Proxy User page is opened.2. Enter the <ACS_Number> (defined Declaring the ACS in the OmniPCX Enterprise on page 106) in

the field SIP User Name3. Validate the Do Not Register check box4. Click Update to save5. Click Go back to Proxy Config to close the Add or Edit Proxy User page6. Click Save and Apply All Settings

OpenTouch Business Edition - ConnectionConfiguration - DPNSS prefix configuration Dialing plan overview on page 164

11.2 Installing a Document Converter Software

11.2.1 OverviewThe Document Converter Software (DCS) allows end users to share documents from their OpenTouchclient. The documents that can be shared are: pdf documents, pictures (formats authorized: png, gifand jpeg), and Microsoft Office documents.



The ACS provides an internal DCS which handles pdf documents and pictures in the following formats:png, gif and jpeg.

The internal DCS does not handle Microsoft Office documents. In this case, this requires to install aDCS on the OpenTouch server or an external server. The DCS installation on the OpenTouch servercan be performed from any of the following:

• The ACS administration console (see: Installing a DCS on the OpenTouch server on page 113)• The Alcatel-Lucent Enterprise Deployment Solution (called ALEDS). For more information, refer to

the ALEDS documentation [5]

To share pdf documents from OpenTouch client application, the DCS performs the following operations:

• It converts each page of a pdf document into png files• It makes all png files available for sharing on the OpenTouch client application

Note:

The size of the set of png files produced by the document conversion is limited by the Disk Quota parameter,defined at organization or end user level. For more information, refer to the OpenTouch Administration Manual [9].

If the size of the set of png files (produced after document conversion) exceeds the value set in the Disk Quotaparameter, the content of the pdf document cannot be shared from OpenTouch client application. However, this pdfdocument can be uploaded from OpenTouch client application, provided that its size does not exceed the user'sdisk quota.

11.2.2 Installing a DCS on the OpenTouch serverThis section presents the DCS installation on the OpenTouch server to share Microsoft Officedocuments from OpenTouch client application.

Note:The DCS is called Document Conversion VM in the ACS administration console.

11.2.2.1 Requirements

• Local access to the system console• Refer to the release note of the OpenTouch version installed to retrieve the list of compatible

applications and OS.

11.2.2.2 Launching the DCS installation on the OpenTouch server

1. Access the ACS administration console (see: Accessing the ACS administration console on page107)

The ACS home page opens.2. Navigate to: Configuration > Advanced Settings > Construct an Internal Document

Conversion VM.



Figure 11.5: Document conversion VM3. Update and store the product keys on the OpenTouch server:

a. In the box labelled Step 1 Enter Product Keys, fill in the Windows Product Key and OfficeProduct Key.

b. Press Submit Keys and the OK button in the resulting dialog box.

Important:Make certain you accurately enter the keys. If errors are made, they will impact the process later,requiring a restart of this procedure.

4. Initialize a new KVM virtual machine on the OpenTouch server and automatically install Windowsand Office on the virtual machine.

a. Place the physical DVD of Windows into the OpenTouch server’s DVD drive.b. In the box labelled Step 2: Control VNC Connection, enter the name or IP address of your

client workstation (VNC Client IP) and click the Allow button.



When your entry is confirmed, the name or IP address disappears in the VNC Client IP field.This behavior is normal.

c. In the box labelled Step 3: Construct Document Conversion VM, click Start to begin theprocess.

The status of the construction of the document conversion begins as follows:

Important:The system will check for hardware virtualization support. If you have not enabled support for thisfeature in the server BIOS, you will receive an error. You will need to Cancel the construction,enable support for hardware virtualization, then start again from Step c above.

d. If you want to see the progress of the installation, you can use a VNC viewer to monitor theprogress after the status shows Installing Windows. This allows enough time for the VNCserver to begin after the initialization.

5. Start a TightVNC client viewer between your client workstation and the OpenTouch server.Note:You may need to set your client workstation’s firewall to allow the outbound VNC connection to the server.

a. Start the TightVNC viewer on your client workstationb. Enter the IP address or hostname of the OpenTouch server, followed by display number (9, by

default).c. Click Connect.



Note:Windows will take approximately 20 minutes to install. At the end of the installation, the vmConverter virtualmachine will restart and a script will run in a Command Prompt window. The script will wait for the OfficeCD to be inserted.

6. When prompted to insert the Office DVD, eject the Windows DVD, using the eject command ifneed be, insert the Office DVD, and click OK.

The Office installation should take 15-30 minutes.

At the end of the Office installation, the vmConverter virtual machine restarts again. On the ACShome page, the status changes from VM construction now complete. You will be redirected in30 seconds to a display of the Product entry screen.

7. Prior to marking the VM Construction complete, verify that your Office is correctly installed. If it isOK, both Windows and Office must be activated and automatic updates turned off (see below).

a. Return to the TightVNC Viewer windowb. Open a Windows explorer and go to %tmp%c. Open the "Microsoft Office Standard Setup...txt" filed. Verify that it does not contain the following error which indicates that an invalid product key was

entered previously:

Error: Invalid Product Key Type: 30::InvalidCDKeye. If OK, continue with next steps

In case of error, restart the procedure from the beginning, ensuring that the correct product keyhas been entered

8. Activate Windows:

a. Select the Start icon.b. In the Search box, type Activate Windows and follow the instructions given.c. When completed, exit the program.

9. Verify that Windows is set to not look for updates automatically.

a. Click the Start buttonb. Type Automatic Updatesc. Select Never check for updates (not recommended) from the drop-down menu



10.Open Microsoft Word and activate its license.

a. Click the Start button.b. Type Microsoft Word

11.Set up Office to not look for updates automatically.



12.Close Microsoft Word.13.Mark the installation as completed:

a. Return to the ACS home page on the client workstation. Navigate to: Configuration >Advanced Settings > Construct an internal Document Conversion VM.

b. In the box labelled Step 4: Complete or Cancel Document Conversion VM Construction,click the Complete button and the OK button in the resulting dialog box.

This operation shuts down the vmConverter virtual machine and save the disk image to be usedas backing store for a dynamic disk.

Important:

Completing the VM construction runs in the background. There is no indication when the diskimage is stable. It is important that the server does not reboot until the process is completed.

To check the progress, go to the ACS home page and select Monitoring > Server Status. The serverprocess named KVM Doc Conv VM has a RED status while services are restarted. The system isready when the status changes to GREEN.

14.Select Configuration > Shutdown and click the Restart button to restart the server.

Note:The document converter software (DCS) is automatically updated from the connected OpenTouch servers. Thisrequires no manual intervention.

11.2.2.3 Activating the DCS after a completed installation

If you did not activate your Microsoft Windows and your Microsoft Office during the installation process,you can use the following procedure to activate them after installation.

This requires to install TightVNC listener on your client workstation and an access to TightVNC listenerthrough any installed firewalls.

Note:If you do not have TightVNC listener installed on your machine, you can use one of the appropriate links at thebottom of the Construct an Internal Document Conversion VM page (Download TightVNC for Windows orTightVNC for other OS’s) to download and install the software. Accept ALL default options for TightVNCinstallation.

1. Start a TightVNC listener session between your OpenTouch server and your client workstation.

Note:You may need to configure your client workstation firewall to allow VNC connection.

a. Start a VNC client listener on your client workstation.b. Locate the option labeled Step 2: Open VM Window on the Construction of Document

Conversion VM page (this is accessed on the Web Administration console throughConfiguration > Advanced Settings.)

Enter the name or IP address of your client workstation (VNC Client IP) and click the Openbutton. Click the OK button in the resulting dialog box.

c. A TightVNC window (virtual machine) appears.

Note:If you do not see the TightVNC window, either the application is not running or a firewall on your clientworkstation blocks the VNC connection.

2. Return to your client workstation and locate the option labeled Step 3: option A on the ConstructDocument Conversion VM page. Only select the checkbox labeled Enable Manual Activation.

Important:Do not select Initialize or Install Windows and Office. This can damages the existing documentconverter and require a full re-installation.

3. Click the Start button on the Web Administration page and click OK in the resulting dialog box.



4. Switch to the TightVNC window.5. Activate Windows and Office:

a. Select the Start icon.b. In the Search field, type Activate Windows and follow the instructions on screen. When

completed, exit the program.c. Select Start->All Programs->Microsoft Office. Start Word and follow the instructions on

screen, selecting Internet activation. When completed, exit the program.6. Mark the installation as completed.

a. Return to the Web Administration window on the client workstation. Select: Configuration >Advanced Settings > Construct Document Conversion VM.

b. Locate the option labeled Step 4: Label VM Construction Complete or Cancel VMConstruction at the bottom of the page. Click the Complete button and click the OK button inthe resulting dialog box.

Note:Do not forget this operation, or parts of the DCS will not start when the OpenTouch server is powered on.

11.2.2.4 Repairing the DCS

After the DCS is completed, it is still possible to modify the image:

1. Navigate to Configuration > Advanced Settings > Repair an Internal Document ConversionVM.

2. Select Start .

3. At the server console, start X windows and select System > Virtual Machine Manager.4. Select vmConverter and click Open.5. After the repairs are done, select the Save and Mark as Working button on the Repair Document

Conversion VM Web Admin page to shut down the VM and recreate the backing store from thecurrent state of the disk.

Note:If the VM is not in usable state, select Don't Save, Mark as Not Working.

11.2.2.5 Stopping unnecessary Windows services

The size of the /mnt/virtualmachines/images/vmConverter.inc file can expand to unwantedvolume.

This file details all the changes made to the file system since the last system reboot, and includestemporary files.

Stopping three Windows services allows to limit the size of the .inc file.

1. Ensure that there is no document being shared2. Access the ACS administration console (see: Accessing the ACS administration console on page

107)3. Navigate to Configuration > Advanced Settings > Repair an Internal Document Conversion

VM.



4. Change the vmConverter status to « Repair » mode: Step 2

Wait a few minutes5. Access vmConverter either via VNC (ot_fqdn:9), or the virtualmanager for OpenTouch Business

Edition6. Stop the services:

• Windows Search• Windows Update• Windows Defender

Example of procedure for Windows 7:

a. Click the Start button, and in the search field, type the command services.msc and press theEnter key

b. Double click the service you wish to stop, for example Windows searchc. Select Disabled as Startup type

d. Click Stop to fully disable the service

e. Click OKf. Follow the same procedure for the other services to stop

7. Disable indexing on the local drive:

a. In a file browser, right-click the local drive and select Propertiesb. In the window which opens, uncheck the box Allow files on this drive to have content

indexed in addition to file propertiesc. Click OK and confirm the operation on all files and subfolders

8. Go back to the ACS administration console9. In the same menu, click Save and Mark as Working

This saves the log file in the vmConverter.qcow2 and resets it to zero

This reboots the vmConverter



11.2.2.6 Rebooting the vmConverter

Should you need to reboot the machine:

1. Access the ACS administration console (see: Accessing the ACS administration console on page107)

2. Navigate to Configuration > Advanced Settings > Repair an Internal Document ConversionVM.

3. Change the vmConverter status to « Repair » mode: Step 2

Wait a few minutes4. In the same menu, click Save and Mark as Working

This saves the log file in the vmConverter.qcow2 and resets it to zero

This reboots the vmConverter

11.2.3 Installing a DCS on an external serverThis section presents the procedure to install a DCS on an external server to share Microsoft Officedocuments from OpenTouch client application.

1. Ensure that there is no current document sharing2. Access the ACS administration console (see: Accessing the ACS administration console on page

107)3. Navigate to Configuration > Advanced Settings > Repair an Internal Document Conversion

VM.4. Change the vmConverter status in « Repair » mode : Step 2

Wait a few minutes5. In the same menu, click Save and Mark as Working

This saves the log file in the vmConverter.qcow2 and resets to zero. This reboots the vmConverter

11.2.3.1 Requirements

• Either a dedicated PC, server, or VM:

• 2 GB RAM• 50 GB disk• Unmanaged (part of private workgroup, not associated with a managed domain)

Refer to the release note of the OpenTouch version installed to retrieve the list of compatibleapplications and OS.

11.2.3.2 Launching the DCS installation on an external server

1. Install Windows and activate the license key

Use all default options.2. Install Office and activate the license key.



Use all default options.3. Use standard Microsoft procedures to apply all Mandatory updates for both Windows and Office

Important:Failure to perform these updates will result in documents that remain in the queued state and do notget converted.

4. Turn off the Windows firewall5. Turn off UAC (User Account Control)

a. Access the Control Panelb. Access User Accountsc. Access User accounts settings

6. Copy the following 3 files from /usr/vmware on the deployed server into c:\• dcs_vmware-*.zip• dcs_install.bat• unzip.exe

7. Run c:\dcs_install.batThis:

• Creates the \rawdocs and \slides shares• Unzips the dcs_vmware.zip file• Installs a startup link for startupExternal.bat

8. Perform the necessary backup/checkpointing/snapshotting in order to make this windows instanceavailable

9. Reboot the windows instance10.Login into Windows.

The DCS needs to run with administrator logged in. In order to avoid the administrator to login eachtime Windows reboots and to manually enter the admin password, activate the Windows automaticlogin.

To enable Windows automatic login, carry out the following procedure:

a. From the Start menu, click Runb. Enter regedit in the dialog box and click OKc. In the console tree, select HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Windows

NT > CurrentVersion > Winlogond. Modify or create new String Value keys as follow:

• AutoAdminLogon set to 1• DefaultPassword set to your_admin_password• DefaultUserName set to your_admin_login_name

e. Restart the server to take your changes into account11.Share the required OpenTouch directories to provide access to the external conversion server by

completing the following:

a. Access the ACS administration console (see: Accessing the ACS administration console onpage 107)

b. Navigate to: Configuration > Advanced Settings > Configure Access to a RemoteDocument Conversion VMNote:The DCS is called Document Conversion VM in the ACS administration console.

c. Enter the name or IP address of the Windows systemd. Enter the name of a user on the external conversion server with administrative privileges



e. Enter the domain name of the external conversion server on which the user has administrativeprivileges

The value of the Remote Document Converter User Domain field depends on thefollowing:

• If the DCS server is part of an MS Active Directory domain, and the user to authenticate is alocal user (local to the DCS server), enter the computer name

• If the DCS server is part of an MS Active Directory domain and the user to authenticate is anMSAD user, enter the MS domain (NetBios name or DNS suffix)

• If the DCS server is not part of an MS Active Directory domain (local user), leave this fieldempty

f. Enter the password of that userg. Click Save

Note:The document converter software (DCS) is automatically updated from the connected OpenTouch servers. Thisrequires no manual intervention.



Chapter

12 Ecosystem Configuration

The OpenTouch ecosystem consists in all the existing applications and network elements that existindependently of ALE International systems, but interacting with OpenTouch-related applications.

12.1 Configuring Gmail as unified messaging serverAs of R2.1, Gmail can be used for the storage of voice mails along with e-mails.

Users may access their e-mails and voice mails with any mail client connected to Gmail. Voice mailsstored in the Gmail repository can be accessed from any OpenTouch client where a voice mailapplication is available.

Example:

1. Alice calls Bob and Bob's set rings2. The call is routed to voice mail: the OpenTouch sends it over the internet to Bob's Gmail account3. Bob is notified on his iPhone that a voice mail has been received and can read the voice mail left by Alice

12

3

Voice mails are sent to Gmail via SMTP. They are read via IMAP.

Authentication is performed using the OAuth2 protocol.

Sub domains management is performed with a key obtained from Google. There is only one serviceauthentication for all users of a given sub domain.

Polling must be used for MWI notification. This implies that for a given OpenTouch server, a maximumof 500 Conversation users can have their voice mails stored in Gmail. The parameters to activate MWInotification by polling, as well as the polling period are specified in a property file.

12.1.1 Configuration overviewConfiguration consists in:

• Configuring Google settings on page 125• Configuring the OpenTouch server on page 131


12.1.2 Configuring Google settingsThis consists in:

• Creating a service account on page 125• Authorizing access for the service account on page 130

12.1.2.1 Creating a service account

The service account's credentials include a generated e-mail address that is unique, a client ID, and atleast one public/private key pair. With this service account, an administrator allows the OpenTouch toaccess the user mailbox without knowledge of their password.

1. Open a web browser and go to https://console.developers.google.com/2. Sign in or create a Google account

The developer console home page is displayed3. Select a project or create a new one: Click Create Project and enter a project name to generate

service account's credentials

4. Verify that the correct project is selected in the right part of the top bar

5. Open the options in the left part of the top bar

Chapter 12 Ecosystem Configuration


https://console.developers.google.com/

6. In the left hand side navigation bar, click API manager > Credentials

7. Click Create credentials and select Service account key



8. In the Service account menu, select New service account9. Enter a service account name, then select P12 in the Key type area, and click the Create button



A public/private key pair is generated and the p12 file is automatically downloaded.10.Select Manage service accounts

11.Note the service account e-mail address (it is required in the OpenTouch management)

Example:

12.Select the options of the created service account on the right part of the window, and select Edit

13.Select the Enable Google Apps Domain-wide Delegation check box and Click Save



The Google Console management is complete.

Before continuing with the configuration of the Google Apps Admin Console, retrieve the client IDbecause it is required in the Google Apps Admin console. To retrieve the client ID:

1. Open the API Manager page

2. In the left hand side navigation bar, select Credentials

This displays the client ID



Example:

At any point in time you may go back to the developers console to view the public key, client ID, andemail address, or to generate additional public/private key pairs. For more details about serviceaccount credentials in the Developers Console, see: https://developers.google.com/console/help/service-accounts (directly available from the Developers Console).

12.1.2.2 Authorizing access for the service account

After obtaining the client ID, the Service Account Email Address and private key from the DevelopersConsole, you need to authorize access for previously created service account/client by following thenext steps:

1. Open a web browser and go to https://admin.google.com/

Note:This page can also be accessed on the page https://mail.google.com/, from the domain administrator account,via the Settings button, on the top right of the window, and selection of the Manage this domain option

2. At the bottom of the page, select Security

3. Click Show More, and select Advanced Settings > Manage API client access

Authorized API clients options are displayed



https://developers.google.com/console/help/service-accounts

https://developers.google.com/console/help/service-accounts

https://admin.google.com/

https://mail.google.com/

4. Enter your previously created client ID in the Client Name field5. In the One or More API Scopes textbox, enter https://mail.google.com/6. Click Authorize

Example:

You can now use the service account e-mail address and associated private key (downloaded asexplained above, see: Creating a service account on page 125) and configure OpenTouch IT serverauthorizations.

12.1.3 Configuring the OpenTouch serverThis consists in:

1. Creating a mail server with IMAP on page 1312. Creating a transfer server on page 1323. Configuring polling options on page 1324. Creating a Unified Messaging voice mail system (see: UM voice mail configuration on page 170)

This operation only applies to the Gmail Enterprise. It does not apply to a classic Gmail solution.

12.1.3.1 Creating a mail server with IMAP

1. On the OmniVista 8770, open the OpenTouch configuration window2. Expand the tree structure and select Eco system > IT Server3. Access the contextual menu and select Create > Mail Server4. Enter a display name5. Enter the Gmail server FQDN6. In the Configuration tab, select IMAP 4 as protocol and Google mail as server type

7. Select or complete the fields:

• SSL for connection security• OAUTH2 for authentication• Enter the e-mail service, previously created on Google mail, in the OAUTH2 email service field• Enter the name of the certification file, previously retrieved from Google mail (bearing .p12 as

extension) in the OAUTH2 file containing key field8. Confirm your entries



Caution:You can now deploy the certificate file (bearing .p12 as extension) on the OpenTouch server in thedirectory /var/data/certificates

12.1.3.2 Creating a transfer server

1. On the OmniVista 8770, open the OpenTouch configuration window2. Expand the tree structure and select Eco system > IT Server3. Access the contextual menu and select Create > Transfer server4. Enter a display name and the Gmail server FQDN5. In the Configuration tab, select SMTP as Protocol and Google mail as Server type

The port is automatically specified by the system

6. Select STARTTLS for Connection security and OAUTH2 for authentication7. Confirm your entries

12.1.4 Configuring polling optionsTo configure the polling notification period: you may adjust the MWI notification period to a valuebetween 30 and 3600 seconds by modifying the value of the propertyimap.notif.producer.totalperiod (which is 60 seconds by default) in the file /opt/Alcatel-Lucent/infra_services/lama/lama.properties.

To deactivate polling: modify the value of the property imap.notif in the file /opt/Alcatel-Lucent/infra_services/lama/lama.properties. By default, this value is set toGOOGLE_MAIL_ONLY. This entails that polling notification is activated only for IMAP servers with Gmailserver type declared in the OpenTouch.

If need be, change this value to:

• NONE to deactivate polling notification for all IMAP servers declared in the OpenTouch.• ALL to activate polling notification for all IMAP servers declared in the OpenTouch.

12.2 Configuring Microsoft Exchange as unified messaging serverThe following paragraphs describe server configuration operations that must be carried out toimplement Unified Messaging with Microsoft Exchange.

This installation is available with Exchange 2007, 2010, 2013 and 2016 servers. The Exchange serverincludes Web Services that allow the OpenTouch to communicate with the Exchange server via asecured link (HTTPS). The default authentication method between the OpenTouch server andExchange Server is Kerberos.

Using Exchange Web Services (EWS) result in:

• No delay for mailbox reception (new voice messages, voice messages played and read/unread e-mails)



• After the creation of Conversation user mailboxes, the OpenTouch subscribes to the Exchangeevent service to receive events from user mailboxes. Mailbox access is achieved via OutlookWeb Access (OWA)

• The Exchange server notifies the OpenTouch when events, such as a new voice messages or e-mail, are spotted in a user mailbox s

• The OpenTouch updates user mailbox counters from these events• The procedure to send or receive voice messages is the same for Outlook Web Access or Outlook

• When an Conversation user leaves a voice message to other Conversation users, theOpenTouch Web Services stores the voice message in the Outbox folder of the sender

• When an Conversation user receives a voice message from a non-Conversation user, theOpenTouch Web Services stores the voice message in the Outbox folder of the receiver

• In any case, the Exchange server processes this voice message as it would an e-mail• The voice message is then available in the Sent Items folder

• Catering for Conversation users belonging to other IP domains than the Exchange server. Thisfeature is available with Exchange® 2010 only

12.2.1 ImplementationThis configuration consists in:

• Declaring the Microsoft Exchange server on the OpenTouch server on page 133• Configuring a dedicated account on the Microsoft Exchange server on page 134• Assigning rights to the privileged account on user mailboxes on page 135• If working with Windows Server 2008, Configuring size and time limits allowed by the IIS web server

on page 136• Verifying access to user mailboxes with the privileged account on page 136• Preventing privileged account from being used by unauthorized users on page 137

12.2.2 Information required• The Microsoft Exchange server FQDN• The Microsoft Exchange server version: 2007 or later• The port used to access the Microsoft Exchange server (default value is 443 for Exchange 2007 or

later)• The login and password to access the Microsoft Exchange server

12.2.3 Declaring the Microsoft Exchange server on the OpenTouch serverThe Exchange server must be declared as a mail server on the OpenTouch server.

1. On the OmniVista 8770, open the OpenTouch configuration window2. Expand the tree structure and select Eco system > IT Server3. Access the contextual menu and select Create > Mail Server4. Enter a display name5. Enter the Microsoft Exchange server FQDN6. In the Configuration tab, select Exchange Web Services



7. Enter 443 as port number used to access the Microsoft Exchange server8. Enter the Exchange login and password

The domain name must be included in the login. This can take the form: Domain\login orlogin@DOMAINNote:In versions before R2.2, this information was provided by the Attribute user Primary SMTP address, but incase of migration from a previous version, the system includes it in the Exchange Web services login field

The OpenTouch must be configured with the FQDN of the Exchange server in CAS role.9. Enter the address for the public URL, so that the Exchange server can access the OpenTouch

Note:

• This url uses http, rather than https• Add a firewall rule to allow Exchange to push notifications to the OpenTouch.• Ensure that the OpenTouch certificate is signed by a certified authority

10.Confirm your entries11.Add the Exchange rootca on the OpenTouch WBM certificate page:

a. On a web browser, connect to the OWA (Outlook Web App) URLb. Click the key to the right of the address bar and select Propertiesc. In the Properties window, click Certificates and select the Details tabd. Click Copy to File... and select Base-64 encoded X.509 (.CER) as export file formate. Save the file on the Exchange server desktop, and copy it on a machine accessible when

connecting to the OpenTouch WebAdminf. Log in to the OpenTouch WebAdmin with an account authorized to access the WBM applicationg. Select System services->Security->Certificate->Certificatesh. Select the Server CTL tabi. Click Addj. Click Select CTL server file, browse to select the rootca file, and click Import

12.2.4 Configuring a dedicated account on the Microsoft Exchange serverA dedicated account is used by the OpenTouch to access mailboxes on the Exchange server usingWeb Services. This privileged account must have an assigned mailbox. It must be granted Send-asand Full Access permissions on all user mailboxes:

• Full Access permission allows the privileged account user to access messages and e-mails of alluser mailboxes

• Send-as permission allows the privileged account user to use a user mailbox to send messages.All messages sent from the mailbox appear as if they were sent by the mailbox owner.

Note:This configuration must be performed with a Windows® administrator account.

To configure the privileged account:

1. On the Microsoft Exchange server, run Start > Programs > Administrative Tools > ActiveDirectory Users and Computers

2. Select the Users directory, right-click and select Create

The user creation window is displayed



Figure 12.1: Active Directory user creation window example3. Complete the requested information and click Next4. Validate the User cannot change password option5. Validate the Password never expires option6. Open User Properties and, in the Member of tag, add the user to the Domain Users group7. Run Start > Programs > Microsoft Exchange > System manager

Not relevant for Exchange 20108. Select Servers > <server_name> > First Storage Group > Mail Box Store Servers > MAIL >

First Storage Group > Mail Box Store

Not relevant for Exchange 20109. In the Security tab, add the user you have just created. In the Allow column, select the Received

as and Send as options

Not relevant for Exchange 201010.Go to the Exchange Management Console and assign a mailbox to this account (this is necessary

for the Exchange 2007/2010 Connector (cnt2007 or cnt 2010) to operate)

12.2.5 Assigning rights to the privileged account on user mailboxesConfigure the privileged account rights either via the management console or using shell commands.

To assign rights to the privileged account on user mailboxes via the management console:

1. Go to: Exchange Management Console > Recipient Configuration > Mailbox2. Select the desired users, right click and select Manage Send as Permission3. Select the privileged account created previously and click Manage4. Select the desired users, right click and select Full Access Permission5. Confirm your selection

To assign rights via a shell command, for each user to configure, enter:

• Add-MailboxPermission –Identity “<mailbox>” –User <privileged user> –AccessRights FullAccess



where <mailbox> corresponds to the e-mail address of the user on which the full access right isgranted to <privileged user>

• Add-ADPermission –Identity “<mailbox>” –User <privileged user> -ExtendedRights "send-as","full access"where <mailbox> corresponds to the e-mail address of the user on which the "send-as" and "fullaccess" rights are granted to <privileged user>

12.2.6 Configuring size and time limits allowed by the IIS web serverNote:The following paragraphs apply for Windows Server 2008 only

By default, the IIS Web Server on Windows Server 2008 configuration limits the duration (in seconds)of a request being executed before it is automatically shut down. It also limits the size of uploaded files.

These limits apply to HTTP requests between the cnt2007 (or cnt2010) connector and EWS on theExchange server, in other words to voice mail messages.

These limits must be configured according to the maximum expected size of voice messages.

To configure limits:

1. On the Windows Server 2008 hosting the Exchange server, go to the folder: C:\Program files\Microsoft\Exchange\clientAccess\exchweb\ews

2. Edit the file web.config with a text editor3. Locate the <system.web> tag in the file4. In the <system.web> tag, modifiy (or add, if missing) the <httpRuntime> tag using the following

syntax:

<httpRuntime maxRequestLength="size in kbytes"executionTimeout="seconds"/>for example <httpRuntime maxRequestLength="1000000" executionTimeout="100"/>

If the configuration of these values does not entail the expected result:

1. On the Windows Server 2008 hosting the Exchange server, run cmd.exe2. Run the following commands

a. cd c:\inetpub\adminScriptsb. cscript adsutil.vbsc. set w3svc/1/uploadreadaheadsize <maxRequestLength> where maxRequestLength

is the maximum IIS request size in bytes3. Restart the server

12.2.7 Verifying access to user mailboxes with the privileged accountOutlook Web Access (OWA) can be used to verify if you can access a user mailbox with the privilegedaccount.

This verification is possible when:

• The user ([email protected]) uses the OpenTouch Unified Messaging as voice messagingsystem

• The privileged account is configured in the Exchange server and OpenTouch (via the WebAdmintool).

To access the user mailbox:



1. Open a Web browser and type the URL: https://<CAS server>/<OWA folder>/[email protected]/Examples:

• https://e2k7.domain.com/owa/[email protected]/• https://e2k7.domain.com/exchange/[email protected]/

2. Log on to the user1 mailbox with the privileged account credentials (login and password)

If logon fails, verify that the privileged account is granted with Full Access permission on the user1mailbox

3. As you are connected to the user1 mailbox with the privileged account, send an e-mail to user1

You must receive it in the user1 mailbox. If it is not the case, verify that the privileged account isgranted the Send-as permission for the user1 mailbox

12.2.8 Preventing privileged account from being used by unauthorized usersThe privileged account can be granted with Full Access permissions on all user mailboxes. Thismeans that if an unauthorized person gets hold of the privileged account credentials, this person canaccess all user mailboxes using the privileged account from an Outlook Web Access (OWA) withdefault Exchange server configuration.

To limit this risk, several operations can be performed on the Exchange server and OpenTouch:

• Deny access to OWA for the Privileged Account. An unauthorized person cannot use OWA with theprivileged account credentials to access to user mailboxes.

This configuration is performed on the IIS manager settings of Exchange server as follows:

Figure 12.2: OAW Settings Configuration Example for the Exchange 2007 Server• Restrict access to the OpenTouch only, so that no other PC or server can access the Exchange

Web Services (EWS)

This configuration is performed on the IIS manager settings of Exchange server as follows:



Figure 12.3: EWS Settings Configuration Example for the Exchange 2007 Server• Allow a user to log on with the privileged account from the OpenTouch only. This depends on the

Active Directory architecture and can be managed using the Deny log on locally policy.• Change the default LDAP password on the OpenTouch. As privileged account credentials are

stored in the LDAP database, this operation prevents unauthorized users to connect to theOpenTouch via an LDAP browser and read the privileged account credentials

12.3 Configuring Office 365 as unified messaging serverAs of R2.2, MS Office 365 unified messaging with the Exchange server (including calendar andconference synchronization) can declared in the cloud . MS Office and Outlook must be at least inversions 2013.

12.3.1 System requirements• The OpenTouch only supports 2013 versions of Office and Outlook.• Office applications must run on user PCs.• Office 365 licenses are required:

• Business licenses apply when the total number of users is below 300• Enterprise licenses apply for a number of users over 300.

They can be any of E1, E3 or E4

E1 does not include Office applications on a PC but an existing Outlook client (with a standardlicense) can be connected to the Exchange server in the cloud.

When no Outlook client is installed on the PC, only unified messaging is available. It allows toreceive voice messages in the e-mail box, but does not provide an add-in for PPR features, norcalendar synchronization. Conference creation is available from OpenTouch applications only,not from Outlook.

With E3 and E4, the latest version of Office applications is in the package and can be installedon PCs, tablets and phones.



For more information, see:

https://products.office.com/en-us/exchange/compare-microsoft-exchange-online-plans.

12.3.2 ImplementationThis configuration consists in:

• Creating a Microsoft Office 365 account on page 139• Configuring http proxies on page 139• Configuring the mail server on page 140

12.3.2.1 Creating a Microsoft Office 365 account

OpenTouch users must have an Exchange account defined by the Exchange server, hosted byMicrosoft at: office365.com / portal.office.com.

Follow the instructions provided by Microsoft to create the domain name and associated accounts.

Once this is done, access to e-mails, calendar and other features is possible from a web browser orfrom an Outlook client (provided it is configured accordingly).

12.3.2.2 Configuring http proxies

The OpenTouch allows to specify proxies. One http proxy can be dedicated for end-user machines, forinstance the OpenTouch server, to access the internet.

The Exchange connector relies on an http proxy to reach the Exchange server lin the cloud.

1. On the OmniVista 8770, open the OpenTouch configuration window2. Expand the tree structure and select Eco system > IT Server3. Access the contextual menu and select Create > HTTP proxy4. Enter a name, FQDN and proxy port:



https://products.office.com/en-us/exchange/compare-microsoft-exchange-online-plans

Figure 12.4: Creating a proxy example5. Confirm your entries

12.3.2.3 Configuring the mail server

1. On the OmniVista 8770, open the OpenTouch configuration window2. Expand the tree structure and select Eco system > IT Server3. Access the contextual menu and select Create > Mail Server4. Enter a display name5. Enter the Microsoft Exchange server FQDN6. In the Configuration tab, select Exchange Web Services



Figure 12.5: Creating a mail server example7. Enter 443 as port number used to access the Microsoft Exchange server8. Enter the Exchange login and password

The domain name must be included in the login. This can take the form: Domain\login orlogin@DOMAINThe OpenTouch must be configured with the FQDN of the Exchange server in CAS role.

9. In the same Configuration tab:

• Declare the server as running in the cloud in the Location field

When the location is set to Cloud the FQDN is set to outlook.office365.com, This value can bemodified if need be

• Declare the public notification URL (for notifications from Exchange to the OpenTouch server)

This parameter is available only if the location field is set to Cloud. This value can be changedlater, if need be.

• Declare the http proxy (for requests from the OpenTouch to Exchange) if need be10.Enter the public URL

There is no need for a reverse proxy. A simple firewall rule is enough to authorize the Exchangeserver to connect to the OpenTouch.

Note:This URL uses http, not https.

11.Confirm your entries

12.4 Configuring IBM Domino as unified messaging serverThe following paragraphs describe server and client configuration operations that must be carried outto implement Unified Messaging with IBM eco-system.



The Domino plugin is available for 32 and 64 bits configurations.

12.4.1 Information required• The IBM Domino server FQDN• The IBM Domino server version: 2003 or 2007• The port used to access the IBM Domino server: default value is:

• 8000 for a Domino server running on a Windows OS• 8012 for a Domino server running on a Linux OS

• The SMTP port used by the IBM Domino Server: default is 25

12.4.2 Lotus Domino configurationThe present paragraphs describe all necessary operations to be carried out on the Domino server andthe Notes application to implement UM configuration and integration with OpenTouch.

The Lotus Domino configuration includes:

1. Installing the Domino plug-in on page 1422. Starting the SMTP Domino task on page 1443. Deploying the plug-in for Notes on page 146

12.4.2.1 Installing the Domino plug-in

To install the plug-in on the Domino server:

1. Turn off the Lotus Domino server2. On the Domino server, launch the file:

OT core DVD 2

for 32 bits releasePlugins/domino_plugins/domino_plugins.exe

or

for 64 bits releasePlugins/domino_64bits_plugins/domino_64bits_plugins.exe

3. Click Next4. Define customer information and click Next



Note:

As templates are not used any longer, the value of the parameter AlcMailMgr_useFormTemplate in notes.iniis 0.

• AlcMailMgr_useFormTemplate=0 <- RCP based extensions• AlcMailMgr_useFormTemplate=1 <- templates

5. Click Next

6. Click Install7. Click Finish.

The installation of the Domino plug-in is complete8. Restart the Domino server and check that the plug-in is started9. Check that Alcatel tasks are started.



Run the command show task on the Domino server console

12.4.2.2 Starting the SMTP Domino task

To start the SMTP Domino task, from the Domino administrator application:

1. Select the Configuration tab2. Click Server3. Click Current server documents4. In the Basics tab, enable the SMTP Listener task parameter

Figure 12.6: Enabling SMTP example



5. Start the SMTP task if not running.

In the Server > Status tab, select the Tasks menu6. Click Start7. Select the SMTP server8. Click Start Tasks9. Click Done

Figure 12.7: SMTP Server Tasks examples

Allow the incoming mail from a specific domain (e.g domino.com )

• Administrator

tab: Configuration

Messaging > Domain > General• tab: Basics



• tab: Conversions

12.4.2.3 Deploying the plug-in for Notes

The method to deploy the Alcatel-Lucent plug-in is based on widget mechanism.

Widget silent deployment is dedicated for mass provisioning but an alternative method may be usedlocally client per client.

12.4.2.3.1 Local deployment12.4.2.3.1.1 Installing the notes update site on Client

Launch the following application on the local PC:

OT core DVD 2Clients\ot_connection\notes_update_site\notes_update_site



12.4.2.3.1.2 Displaying the Application Management menu

1. Open the file [notes_home]\framework\rcp\plugin_customization.ini2. Add the line “com.ibm.notes.branding/enable.update.ui=true”3. Start IBM Notes 9.

A new menu entry is available: File > Application > Application Management

12.4.2.3.1.3 Installing the plug-in

1. From Notes, click File > Application > Install

2. Select the Search for a new feature option

a. Select the Add Folder Location optionb. Enter the path:

Program files/Alcatel-Lucent/Notes update site



The plug-in to be installed is displayed:



c. Click Next



d. Click 'I accept the terms in the license agreements' and Nexte. Click Finish

f. Select ‘Install this plug-in’ and click OK

12.4.2.3.1.4 Restarting Notes

Start Lotus Notes to take account the Alcatel plug-in.



If the toolbar with plug-in buttons is not displayed:

1. Modify the option in the view menu: View > Toolbar2. Untick the Show Toolbars Only When editing item

12.4.2.3.2 Mass provisioning deployment12.4.2.3.2.1 Creating the NSF bases to deploy the plug-in on Notes clients

1. From Lotus Notes, click File > Application > New2. In the application Server field, specify the Domino server on which to create the application3. In the Title field, specify the application title, for example “Update Site”4. In the File name field, specify an application name, for example updatesite.nsf5. In the template Server field, specify the server on which the template resides6. Click Show Advanced Templates and select Eclipse Update Site template (updatesite.ntf)7. Click to enable Inherit future design changes, and click OK



8. From Lotus Notes, click File > Application > New9. In the application Server field, specify the Domino server on which to create the application10.In the Title field, specify the application title, for example 'Widgets catalog'11.In the File name field specify an application name, for example toolbox.nsf12.In the template Server field, specify the server on which the template resides13.Click Show Advanced Templates and select the 'Widget Catalog' template (toolbox.ntf)14.Click to enable Inherit future design changes, and click OK



15.Assign ACLs to control access rights to the catalog application for administrators, power users, andstandard users

12.4.2.3.2.2 Installing the Alcatel Notes update site site.xml

1. Launch the following application on the local PC:

OT core DVD 2Clients\ot_connection\notes_update_site\notes_update_site

2. Open Server’s NSF base Update site located in the server with Notes3. Select the Import Local Update Site tab and browse the folder where is located site.xml (e.g. C:

\Program Files\Alcatel-Lucent\Notes update site)4. Open the site.xml file



12.4.2.3.2.3 Creating the Alcatel widget in the catalog

1. Modify extension.xml:

a. Copy the original extension.xml file on the local PCb. Modify the url attribute with the Domino server FQDN:

Ex: url="nrpc://vm3s11.s11.tss/updatesite.nsf/site.xml"c. Modify the extension version:

Ex: id="com.alcatel_lucent.ics.lotus.extensions.feature"version="4.0.200.0xx"match="perfect"d. Save the file

2. Open the server’s NSF Widget catalog3. Click the All Widgets view option4. Click Add Widget to Catalog, and enter a widget title, for example "Alcatel-Lucent”5. Click Category and type the new catalog category name, for example: communication6. Click Attach and select the extension.xml file



7. Save and Close

12.4.2.3.2.4 Provisionning the Alcatel-Lucent sidebar widget to users

1. Configure desktop policy settings:

a. Open the Domino Administrator and click People & Groups People > Policies > Settingsb. Click Add Settings and choose Desktopc. Set a name and a description in the Desktop Settings



d. Click the Widgets tab, and in the Widget catalog server field, specify the server on which thewidget catalog resides

e. In the Widget catalog application name field, specify the catalog name toolbox.nsff. In the Catalog categories to install field, specify the catalog category 'communication'g. Enable the Enable Live Text optionh. Enable the Show the My Widgets panel in the sidebar optioni. To apply this setting, select the Set value and prevent changes option

2. Configure the Policy Document:

a. Create a new policy



b. Click Add Policyc. Set a Policy name and the “Policy type” to “Explicit”d. Set Desktop with the policy settings'deploy alcatel widget'

3. Save and Close

4. Assign the policy to users:

a. Select the people or the group for which the new Policy should be applied and Assign Policyb. Select the new created policy



c. Click OK

12.4.2.3.2.5 Installing the widget to the user’s client

1. Start Lotus Notes.

Open the Mail database to download user’s policy

2. Restart Notes

12.5 Configuring an LDAP serverThe following paragraphs describe configuration operations that must be carried out when an LDAPserver is used for UDA (Universal Directory Access).

For more information on UDA, see [3] section Configuring the User Directory Access Service (UDAS).

12.5.1 Information required• LDAP FQDN



12.5.2 Declaring the LDAP server on the OpenTouch server1. On the OmniVista 8770, open the OpenTouch configuration window2. Expand the tree structure and select Eco system > IT Server3. Access the contextual menu and select Create > LDAP server4. Enter a name for the LDAP server5. Enter the LDAP server FQDN6. Modify the port number in the General tab, if needed7. Confirm your entries

12.6 Configuring a reverse proxyA reverse proxy is used to control access to OpenTouch web service from the outside of the enterprise.It provides an access control through login password.

The reverse proxy enables mobility to remote workers and access to the OpenTouch conferences foranonymous users (as of R2.2.1).

The configuration of a reverse proxy is described in the document [15].

12.7 Configuring the DNS serverThe Local DNS Server (one) and External DNS servers (two maximum) declared at post-installationare automatically declared in the OmniVista 8770 configuration application. Settings retrieved frompost-installation can be modified via rehosting only, and cannot be modified from the OmniVista 8770configuration application. Only new external DNS servers can be declared.

To configure a DNS server:

1. From the OmniVista 8770 configuration application: select your OpenTouch server and open theConfiguration window

2. Navigate to: Eco system > IT Server3. Right click and select: Create > DNS Server

The DNS configuration window is displayed.4. Enter values in the configuration fields:

• Display name: enter the DNS server name• FQDN: enter the DNS server FQDN• Element created during post-installation: this non-modifiable parameter indicates if the DNS

Server can be fully configured in the OmniVista 8770 (box unchecked) or if some parameterscan be modified only via rehosting (box checked)

• IP @: enter the DNS server IP address5. Click the validate icon to save your modification

12.8 Configuring an NTP serverThe internal NTP server (one) and External NTP servers (two maximum) declared at post-installationare automatically declared in the OmniVista 8770 configuration application. Settings retrieved frompost-installation can be modified via rehosting only, and cannot be modified from the OmniVista 8770configuration application. Only new external NTP servers can be declared.

To configure an NTP Server:




2. Navigate to: Eco system > IT Server3. Right click and select: Create > SNTP Server

The SNTP configuration window is displayed.4. Enter values in the configuration fields:

• Display name: enter the SNTP server name• FQDN: enter the SNTP server FQDN• Element created during post-installation: this non-modifiable parameter indicates if the SNTP

Server can be fully configured in OmniVista 8770 (box unchecked) or if some parameters can bemodified only via rehosting (box checked)

5. Click the validate icon to save your modification

12.9 Configuring a DHCP server on Windows Server 2008To configure a DHCP server on Windows Server 2008, you have to:

1. Enable the DHCP Server: see Installing Windows Server 2008 DHCP Server on page 1602. For each Vendor Class:

• Configure the Vendor Class: see Configuring a Vendor Class on page 160• Create a scope: see Configuring a scope of IP addresses on page 161• Configure scope options: see Configuring scope options on page 161

12.9.1 Installing Windows Server 2008 DHCP Server1. Click Add Roles from the Initial Configuration Tasks window or from Server Manager > Roles

The Add Roles Wizard comes up.2. Click Next3. Select the DHCP Server Role, and click Next4. In the Select Network Connection Bindings window, select the interface for which you want to

configure DHCP services and click Next5. In the Specify IPv4 DNS Server Settings window, enter the Parent Domain, the Primary DNS

Server, the Alternate DNS Server and click Next6. Click Next several times and finally Install

12.9.2 Configuring a Vendor ClassTo create a new user or vendor class:

1. In the console tree, click the applicable DHCP server2. On the Action menu, select Define Vendor Classes3. Click Add4. In the New Class dialog box, type a descriptive identifying name for the new option in the Display

name box. You may also add additional information to the Description box5. Click the right side of the text box and enter the Vendor Class ID in ASCII characters:

• D(ECT)49 for IP-DECT• alcatel.ictouch.0 for 8082 My IC Phone and 8012 Deskphone

6. Click OK, and then click Close



12.9.3 Configuring a scope of IP addressesA scope of IP addresses must be created for each vendor class. For example, if the DHCP server isserving IP-DECT stations, 8082 My IC Phone and 8012 Deskphone, you need two scopes:

• One scope for IP-DECT stations: Vendor Class D(ECT)49• One scope for 8082 My IC Phone and 8012 Deskphone: Vendor Class alcatel.ictouch.0To create a scope

1. Open the DHCP Microsoft Management Console (MMC) snap-in2. In the console tree, double-click the DHCP server you want to configure3. Right-click IPv4 and then click New Scope4. Click Next to the introduction wizard screen5. Enter a Scope name, for example MyIC8082 and click Next6. Enter the Starting IP address and Ending IP address of the range, the Subnet mask and click

Next7. Optionally, add specific IP address ranges that should be excluded from the scope and click Next8. Set the lease time value and click Next9. Configure DHCP options, such as default gateway, DNS servers, if specific to the scope. If not

configured here, DHCP options defined at server level will be used10.Click to activate the scope

12.9.4 Configuring scope options1. Open the DHCP Microsoft Management Console (MMC) snap-in2. Go to the scope for which you want to configure options and click Scope Options3. select 066 Boot Server Host Name and in the String value field, enter the address of the TFTP

server:

• For IP-DECT: enter the address of the OmniPCX Enterprise (main IP address)• For 8082 My IC Phone and 8012 Deskphone: enter the address of the OpenTouch server

4. Select the Vendor Class associated to this scope5. click OK



Chapter

13 System Configuration

13.1 Backing up the OpenTouch server database

13.1.1 Backing up the OpenTouch Business Edition server databaseThe following operation applies to the OpenTouch Business Edition (after an installation from scratch).

Before system configuration, it is recommended to back up the OpenTouch Business Edition serverdatabase on a storage media:

1. Open a root session on a CLI terminal2. Configure the storage media using the ot-config.sh --storage command3. Stop all virtual machines using the commands:

• oxe_cmd stop• management_cmd stop• oms_cmd stop

4. Back up the virtual machine data using the otbr.sh backup VMall command5. Start all virtual machines using the commands:

• oxe_cmd start• management_cmd start• oms_cmd start

6. Back up all application data using the otbr.sh backup appliall command

Complete details on the backup operation are provided in the Backup and restore section of thedocument [3].

13.1.2 Backing up the OpenTouch Multimedia Services server databaseThe following operation applies to the OpenTouch Multimedia Services (after an installation fromscratch).

Before system configuration, it is recommended to back up the OpenTouch Multimedia Services serverdatabase on a storage media:

1. Open a root session on a CLI terminal2. Configure the storage media using the ot-config.sh --storage command3. Back up all application data using the otbr.sh backup appliall command

Complete details on the backup operation are provided in the Backup and restore section of thedocument [3].

13.2 Configuring Global parametersGlobal parameters concern country, time zone and languages used by the system, users andadministrators. Global parameters are automatically configured after post-installation. They can be leftunchanged, or modified according to your needs.

To modify Global parameters:

1. From the OmniVista 8770 configuration application: select the OpenTouch Server and open theConfiguration window


2. Select: System services > Global parameters3. Review/modify the following parameters:

Country Select a country

Default value: Country configured at post-installa-tion in the Local Settings window

Value after an upgrade from a release lower than2.1: current country of the default dialing rule

Time zone Select a time zone

Default value: Time zone configured at post-instal-lation in the Local Settings window

Value after an upgrade from a release lower than2.1: GMT0

Conference Web interface language Displays the language selected at post-installation.

By default, this parameter is automatically set to thelanguage associated to the Country configured atpost-installation in the Local Settings window.

To modify the current value, select either:

• A language• Default value: the language associated to the

Country parameter is used

Users

GUI language Displays the language selected at post-installation.





Note:The modification of this parameter has an impact only onusers created after modification, but has no impact onexisting users.

Chapter 13 System Configuration


TUI language Displays the language selected at post-installation.





Note:The modification of this parameter has an impact only onusers created after modification, but has no impact onexisting users.

Administrators

Default language Displays the language selected at post-installation.





Note:The modification of this parameter has an impact only onadministrators created after modification, but has noimpact on existing administrators.

Warning mode


13.3 Dialing plan overview

Overview on page 106 Configuring ranges on page 166

The OpenTouch server includes two telephone switches:

• The OmniPCX Enterprise server which supports Connection users• The SIP Server which supports Conversation users



SIPTrunk Group

OmiPCX EnterpriseCall Server

SIP Server

Call ServerDialing Plan

SIP ServerDialing Plan

OpenTouch Server

Figure 13.1: OpenTouch switch organization

The dialing plans of OpenTouch and OmniPCX Enterprise must be homogenous: the same dialednumber has the same meaning whether the call is made from a Conversation user or a Connectionuser. All the internal numbers of the OmniPCX Enterprise must be declared in one or several numberranges on the OpenTouch server.

OpenTouch routing rules:

• On the SIP Server:

One or more Ranges are declared. These Ranges must correspond to all the internal numbers(users, voice mail, attendant, trunk prefix).

Note:Conversation users and Connection users can share the same ranges. This allows for example to changeConnection users into Conversation users without changing their numbers.

For outgoing calls, one or more Dialing rules are declared. These Dialing rules are used to accessthe public network via the OmniPCX Enterprise server. These Dialing rules must correspond to theOmniPCX Enterprise server external access prefixes.

Routing rule: when a number belonging to the Range(s) or to the Dialing rules is dialed, the call isrouted to the OmniPCX Enterprise server where it is processed.

Other numbers are processed locally.• On the OmniPCX Enterprise server:

Conversation users are declared as users having a SIP device and with an External Gatewaynumber that corresponds to the SIP Server

Routing rule: when such a user number is dialed, the OmniPCX Enterprise server routes the call tothe external gateway/SIP Server.

Other numbers are processed locally.• Prefixes:

It is recommended to configure SIP Server prefixes and OmniPCX Enterprise server prefixes withthe same value for the same usage.

Notes:

• SIP Server devices cannot be called directly by users (whether Conversation users or Connection users)• An Conversation user can only use SIP server devices• A Connection user can only use OmniPCX Enterprise devices

The dialing plans of the two telephone switches must be compatible.

Overview on page 106 Configuring ranges on page 166



13.4 Configuring ranges

Dialing plan overview on page 164 Configuring dialing rules on page 168

On the SIP Server, a Range defines dialing numbers which are processed in the OmniPCX Enterpriseserver.

Ranges include:

• All Connection user numbers• All multimedia user numbers• All OmniPCX Enterprise server voice mail numbers (46xx voice mail, UM, local storage).• Local storage numbers of Connection users• Attendant numbers• Trunk Group prefixes

To define a Range:

1. From the OmniVista 8770 configuration application: select the OpenTouch Server and open theConfiguration window

2. Navigate to: System services > Topology > OXE callservers > OXE network > OXEsubnetwork > Physical server > Call Server

3. Double click your OmniPCX Enterprise call server name to open the SIP Server properties window4. Select the Range tab5. Right click Number ranges and click Add6. In the Minimum field, enter the first number of the range7. In the Maximum field, enter the last number of the range8. Click Apply or Save

It is possible to add a new range:

1. Right click in the Range tab2. Select Add

New fields are added3. Enter the first and last number for this new range.

Dialing plan overview on page 164 OXE prefix (Conversation users) on page166

13.5 OXE prefix (Conversation users)

Configuring ranges on page 166 Configuring dialing rules on page 168

13.5.1 OverviewAn OXE prefix is used, on the OpenTouch server, to translate an OmniPCX Enterprise prefix receivedwith an external calling number.

On the OpenTouch server, as well as on the OmniPCX Enterprise server, a calling number is a "readyto use" number. In other words, the calling number displayed on a set, stored in a call log or stored in



the memory associated to a callback key is the exact number to dial to call back the calling party. Thisnumber includes the prefix required to make an external call.

For each external incoming call, the OmniPCX Enterprise server adds its outgoing prefix to the callingnumber. When outgoing prefixes are not identical on the OpenTouch and the OmniPCX Enterpriseserver, an OXE prefix translation is required.

Example of configuration requiring an OXE Prefix translation:

1

a

OmniPCX Enterpriseserver

Private network Public nework

OpenTouch server

PSTNPSTN

Trunk group

Internal SIP server user

External user

d

Outgoing Call4

3

c

2

Incoming CallSIP

Server

b

Figure 13.2: Example of outgoing and incoming calls with an OXE Prefix required

Outgoing call:

1. The Conversation user dials: 0, followed by the external number. Number 0 is the outgoing prefix toaccess the public network.

Number 0 belongs to a range of numbers processed by the OmniPCX Enterprise (see: Configuringranges on page 166)

2. The call is transmitted to the OmniPCX Enterprise server to be processed3. On the OmniPCX Enterprise server, 0 is defined as a speed dialing number. It is translated to ##12.

Number ##12 is defined as a public trunk group seizure prefix. It allows the call to be transmitted tothe public network.

4. The call is transmitted, via the public network, to the called party

Incoming call:

1. An external user dials the DID number of the Conversation user2. The OmniPCX Enterprise server receives the call. This call is for an Conversation user, the call is

transmitted to the OpenTouch server. The trunk group seizure prefix: ##12 is added to the callingnumber.

3. On the OpenTouch server number ##12 is configured as OXE prefix, it is translated to 0

The OpenTouch server transmits the call to the called user. The calling number becomes 0 followedby the external number of the calling party. This calling number can be used for callback, withoutfurther modification.



13.5.2 ConfigurationA translation of OmniPCX Enterprise prefix is required when a prefix added by the OmniPCXEnterprise to calling numbers is not identical on OpenTouch and on OmniPCX Enterprise. Example:OmniPCX Enterprise trunk group seizure prefix versus the OpenTouch outgoing prefix.

To configure OXE CS prefix translation:

1. From the OmniVista 8770 configuration application: select your OpenTouch Server and open theConfiguration window

2. Navigate to: System services > Topology > OXE CS > OXE CS prefix translation3. Click right and select Create4. Review/modify the following attributes:

Display name enter the name of this OXE CS prefix

Initial number enter the OXE CS prefix

Translated number enter the translation of the OXE CS prefix.

5. Click the validate icon to apply your modifications

Configuring ranges on page 166 Configuring dialing rules on page 168

13.6 Configuring dialing rules

Configuring ranges on page 166 Local storage voice mail configuration onpage 169

On the SIP Server a Dialing Rule is used to access the public network via the OmniPCX Enterpriseserver.

To create a Dialing Rule:


2. Navigate to: System services > Applications > Telephony settings > Dialing Rule3. Click right and select Create

A new Dialing Rule property window is opened.4. Review/modify the following attributes:

Display external prefix Enter the trunk seize prefix value defined on the OmniPCX Enterpriseserver

Country Select the country where the user or user group resides

If you leave Default value, the Country parameter will take the valueconfigured in Global parameters after validation.

Area code enter the area or regional code of the location where the user or usergroup resides

5. Select the Conditions for adding the external dialing prefix tab



Minimum length Enter your dialing plan length +1

The Minimum length parameter defines the number of digits fromwhich a number is considered as an external number.

Exception length Enter the number of digits that are exempted from the rule

Exception start Enter the first digits of the string defined in the Exception length pa-rameter. If there is no exception to the rule, leave this parameter blank


Create as many Dialing rule as OmniPCX Enterprise server trunk size prefixes used by Conversationusers.

Note:To review/modify Global parameters, refer to: Configuring Global parameters on page 162.

Configuring ranges on page 166 Local storage voice mail configuration onpage 169

13.7 Configuring a voice mail systemThe following voice mail are available:

• UM (Unified Messaging) defined on the OpenTouch server. Connection users and Conversationusers can be associated to this voice mail system. The voice mail storage can be:

• Hosted on an Microsoft Exchange server• Hosted on an IBM Domino server• Hosted on a Gmail Enterprise server

• Local Storage (LS), hosted on the OpenTouch. Connection users and Conversation users can beassociated to this voice mail system.

13.7.1 Local storage voice mail configuration

Configuring dialing rules on page 168 [3] section User creation and administration

13.7.1.1 OmniPCX Enterprise server configuration

The OmniPCX Enterprise server must be configured to route calls to the appropriate voice mail system.

On OmniPCX Enterprise server create two External Voice Mail:

1. Select: Application > External Voice Mail2. Create an external voice mail for Connection users with the following attributes:

Voice Mail Dir.No. Enter the voice mail number for Connection users

In this configuration procedure this number iscalled: <VM_OXE_Number>


Directory Name Enter the directory name for display only



External Gateway number Enter the <EXT_GW_VoiceMail_ID> number con-figured previously: see Document [2] section Con-nection Configuration - SIP external gateway con-figuration.

Subscription on registration Select: True

3. Confirm your entries4. Create an external voice mail for Conversation users with the following attributes:

Voice Mail Dir.No. Enter the voice mail number for Conversation users

In this configuration procedure this number iscalled: <VM_ICM_Number>



External Gateway number Enter the external gateway number leading to theSIP Server

(<EXT_GW_ID>)


The <VM_ICM_Number> and <VM_OXE_Number> numbers must belong to a Range defined in theSIP Server (see: Configuring ranges on page 166).

13.7.1.2 SIP server configuration

On SIP Server, the Local Storage voice mail system is declared by default.

Local Storage voice mail system configuration:


2. Navigate to: System services > Applications > Telephony > Vocal applications > TUIapplication

3. Look for the application with Type = Voice mail and User population = OXE call server4. In the field Number: enter the Local Storage voice mail system number defined for Connection

users (<VM_OXE_Number>)5. In the field Public Number: enter the public number of the Local Storage voice mail system6. Click the validate icon to apply your modifications7. Look for the application with Type = Voice mail and User population = Communication server8. In the field Number: enter the Local Storage voice mail system number defined for Conversation

users (<VM_ICM_Number>)9. In the field Public Number: enter the public number of the Local Storage voice mail system10.Click the validate icon to apply your modifications

Configuring dialing rules on page 168 [3] section User creation and administration

13.7.2 UM voice mail configurationWhen an external storage is used (Microsoft Exchange server, IBM Domino or Gmail Enterprise), youhave to create a voice mail system.



Voice mail system configuration:


2. Navigate to: System services > Topology > Voice Mail System3. Click right and select: Create > UM Voice Mail System to create the voice mail system for

Connection users4. In the field Transfer Server (optional): select the name of your transfer server in the drop-down list5. In the field Mail Server: select the mail server in the drop-down list6. Click the validate icon to apply your modifications

The Transfer server and the Mail server must be previously created for the voice mail storage used:

• Configuring a Microsoft Exchange server on page 132• or Configuring IBM Domino as unified messaging server on page 141• or Configuring Gmail as unified messaging server on page 124

13.8 Configuring music on holdMusic on Hold (MOH) uses wav files to provide music for callers waiting to be connected.

The music on hold can be customized. Specific music can be recorded using the Alcatel-Lucent AudioStation (AAS) application (see the corresponding documentation).

To install a new wav file:

1. Open root session2. Navigate to:

/opt/Alcatel-Lucent/voice_platform/AMS_MediaControl3. Enter the ./moh.sh -l <audio file path> command

Note:The music on hold for Connection users is managed on OmniPCX Enterprise.

13.9 Configuring the System TUI languagesAs of R2.2, TUI relies on .wav files for all languages (refer to [3] chapter "List of TUI.wav files" for thelist of supported languages).

Voice prompts in .wav are automatically installed with the system, when the system languages areselected.

One System TUI language must be defined for the system as the default TUI language.

If for some reason, the language of a user is unknown, or the message cannot be played in the userlanguage, voice prompts are played in the System TUI language.

To configure the System TUI language:

1. Go to System services > Applications > Telephony > Vocal applications > TUI Language andselect the corresponding language.



Figure 13.3: TUI language configuration example2. Select the System TUI language check box

Caution:Only one default language must be defined for the system.


13.10 Configuring TUI applications

13.10.1 Configuring the Voice homepage application


On the OmniPCX Enterprise server create an External Voice Mail:


Voice Mail Dir.No. Enter the Voice homepage application number forConnection users

In this configuration procedure this number iscalled: <VHP_OXE_Number>






(<EXT_GW_ID>)

For more information, see: OpenTouch MultimediaServices - Connection Configuration - SIP externalgateway configuration

Subscription on registration Select: False


Voice Mail Dir.No. Enter the Voice homepage application number forConversation users

In this configuration procedure this number iscalled: <VHP_ICM_Number>




(<EXT_GW_ID>)




The <VHP_OXE_Number> number and the <VHP_ICM_Number> number must belong to a Rangedefined in the SIP Server (see: Configuring ranges on page 166).


On the SIP Server, the Voice homepage application is declared by default.



3. Look for the application with Type = Voice homepage and User population = OXE call server



Figure 13.4: Default page for Connection user access to the Voice homepage application4. In the field Number: enter the number defined for Connection users (<VHP_OXE_Number>)5. Click the validate icon to apply your modifications6. Look for the application with Type = Voice homepage and User population = Communication

server



Figure 13.5: Default page for Conversation user access to the Voice homepage application7. In the field Number: enter the number defined for Conversation users (<VHP_ICM_Number>)8. Click the validate icon to apply your modifications

13.10.2 Configuring the Advanced Cellular Extension (ACE) applicationOn the OpenTouch server, the ACE application is declared by default.


2. Navigate to: System services > Applications > Telephony settings > Vocal applications > TUIapplication

3. Look for the application with Type = ACE



Figure 13.6: Default page for the ACE application4. In the field Number: enter the number defined for ACE application5. In the field Public number: enter the public number defined for ACE application

Note:The public number of ACE must be defined when OTC smartphone devices operate in cellular mode only ordual-mode (Wi-Fi/cellular). For more information, refer to the document [15].


13.10.3 Configuring the Telephony services application




Voice Mail Dir.No. Enter the voice Telephony services number for Con-nection users

In this configuration procedure this number iscalled: <TS_OXE_Number>






(<EXT_GW_ID>)




Voice Mail Dir.No. Enter the Telephony services number for Conversa-tion users

In this configuration procedure this number iscalled: <TS_ICM_Number>




(<EXT_GW_ID>)




The <TS_OXE_Number> number and the <TS_ICM_Number> number must belong to a Rangedefined in the SIP Server (see: Configuring ranges on page 166).


On the SIP Server, the Telephony services application is declared by default.



3. Look for the application with Type = Telephony services and User population = OXE call server



Figure 13.7: Telephony services configuration for Connection users4. In the field Number: enter the number defined for Connection users (<TS_OXE_Number>)5. Click the validate icon to apply your modifications6. Look for the application with Type = Telephony services and User population = Communication

server



Figure 13.8: Telephony services configuration for Conversation users7. In the field Number: enter the number defined for Conversation users (<TS_ICM_Number>)8. Click the validate icon to apply your modifications

13.10.4 Configuring the VoiceIt application




Voice Mail Dir.No. Enter the VoiceIt application number for Connectionusers

In this configuration procedure this number iscalled: <VI_OXE_Number>.






(<EXT_GW_ID>)




Voice Mail Dir.No. Enter the VoiceIt application number for Conversa-tion users.

In this configuration procedure this number iscalled: <VI_ICM_Number>.




(<EXT_GW_ID>)




The <VI_OXE_Number> number and the <VI_ICM_Number> number must belong to a Rangedefined in the SIP Server (see: Configuring ranges on page 166).


On the SIP Server, the VoiceIt Application is declared by default.



3. Look for the application with Type = VoiceIt and User population = OXE call server



Figure 13.9: TUI configuration for VoiceIt for Connection users4. In the field Number: enter the Voicelt application number defined for Connection users

(<VI_OXE_Number>)5. Click the validate icon to apply your modifications6. Look for the application with Type = VoiceIt and User population = Communication server



Figure 13.10: TUI configuration for VoiceIt for Conversation users7. In the field Number: enter the Voicelt application number defined for Conversation users

(<VI_ICM_Number>)8. Click the validate icon to apply your modifications

13.10.5 Configuring the One number application




Voice Mail Dir.No. Enter the One number application number for Con-nection users

In this configuration procedure this number iscalled: <1Nb_OXE_Number>






(<EXT_GW_ID>)




The <1Nb_OXE_Number> number must belong to a Range defined in the SIP Server (see: Configuringranges on page 166).


On the SIP Server, the One number Application is declared by default.



3. Look for the application with Type = One number

Figure 13.11: TUI configuration for One number Services4. In the field Number: enter the number defined for Connection users (<1Nb_OXE_Number>)5. Click the validate icon to apply your modifications



13.10.6 Configuring the DVA applicationOn the SIP Server, theDVA application is declared by default.



3. Look for the application with Type = DVA

Figure 13.12: Configuration for DVA application4. In the field Number: enter the number defined for DVA application5. Click the validate icon to apply your modifications

13.11 Configuring forwarding prefixesOn SIP Server the forwarding application works with prefixes. These prefixes must be configured.

For more information, see the administration manual [3] section "Configuring the telephone prefixes".



Chapter

14 Connections to the System

14.1 Access to the OpenTouch Business Edition serverYou can access the OpenTouch Business Edition server from:

• The local console

Where text and graphical interfaces are available.• A remote computer connected via the IP network

14.2 Local access

14.2.1 Connection to the OpenTouch server• Connect a keyboard and a monitor to the OpenTouch server• Open a session (otuser for example)

A Linux text interface is available.• Start the graphical interface, using the command:

systemctl start display-managerNote:In a system where the OpenTouch itself is virtualized, you must used the vSphere console associated to yourOpenTouch.

14.2.2 Connection to vmOXE, vmOMS and vmManagement virtual machinesThe Virtual Machine Manager tool is used to access virtual machines.

14.2.2.1 Start the virtual machine manager

On the OpenTouch server console:

• Open a session (otuser for example)• Enter the systemctl start display-manager command• Navigate to Applications > System Tools > YaST• In the Administrator settings window, in the Virtualization pane, select the Virtual Machine

Manager option

The virtual machines manager window opens


Figure 14.1: Virtual machine manager home page example

14.2.2.2 Operations on the virtual machine manager14.2.2.2.1 Access a specific virtual machine

From the Virtual Machine Manager home page:

1. Double click the virtual machine name

The virtual machine window opens :

Figure 14.2: Virtual machine window example2. Click anywhere in the virtual machine window to activate the virtual machine console

• The vmManagement is in graphical mode. The OpenTouch server mouse is replaced by thevmManagement mouse.

Chapter 14 Connections to the System


The vmManagement mouse only works within the vmManagement window . To enable theOpenTouch server mouse: press Ctrl + Alt.

• The vmOMS is in text mode: the mouse cursor is replaced by a text cursor.• The vmOXE is in text mode: the mouse cursor is replaced by a text cursor.

The OpenTouch server mouse is deactivated. To enable the OpenTouch server mouse: pressCtrl + Alt.

14.2.2.2.2 Start and stop a virtual machine

Start and stop a virtual machine using the Virtual Machine Manager buttons.

Note:These buttons are equivalent to an on/off switch on a real machine. Perform a clean shutdown before you stop avirtual machine.

14.3 Remote connection via a VNC over SSH tunnel

14.3.1 OverviewThis section describes remote access via a VNC over SSH tunnel.

Getting a remote access can be necessary for:

• Maintenance: system monitoring, patch and version installation• Administration: configuration, alarm verification, etc., using OmniVista 8770 and associated tools

14.3.1.1 Maintenance

OpenTouch software installation can be done using DVDs or ALEDS. Both methods require a physicalaccess to the OpenTouch server.

Remote installation is only possible for patch (upgrade) installation. Full installation requires a physicalaccess to the machine.

Remote system monitoring is possible, with or without GUI. For example: checking the logs does notrequire a GUI.

14.3.1.2 Administration

Remote system administration is possible.

The embedded Windows 2008 image for OpenTouch Business Edition allows system administrationwith remote access (remote desktop).

Note:The OpenTouch remote administration is not described in this document.

14.3.2 VNC over SSH tunnel remote accessWhy and when should we use VNC over an SSH tunnel?

• When the link with the OpenTouch server is not reliable, because an interruption of the networkservice terminates the SSH session but does not terminate what you have started locally on theserver using the tunnel

• If you have started a time-consuming process, you can re-establish the tunnel and check theprogress of your process, once the network service is back

In other words, if the network connection breaks down, the installation of a patch using a VNC over anSSH tunnel does not need to be started all over again. Restarting the SSH Tunnel and VNC resumesthe operation.



Installing any patch or launching any setup within a direct SSH session is not allowed. If thesession is closed while running (e.g. network outage), patch installation is halted and fails. Nopatch installation recovery is available.

14.3.2.1 Overview

This configuration requires:

1. A VNC server (integrated to the SLES delivery) which has to be started on the OpenTouch2. An SSH Putty connection from the remote computer to the OpenTouch server3. One (VNC) or more traffic forwarding opened in this tunnel to forward remote computer network

traffic to the OmniVista 8770 server.4. One (VNC) or more (OmniVista 8770, ..) client software on the remote computer to access the

associated application server on the OpenTouch server

OpenTouch Server

Xwindow GUI(not used for

remote access)

Remote computer

VNCclient

LAN / WAN SSH tunnel powered by Putty

Xvnc(VNC server)

OT Adminserver

(ICS/ACS/..)

SUSE Linux Enterprise Server

Host : server1ot / 192.168.201.131

TCP : 5904

Figure 14.3: VNC access to the OpenTouch example

In the above example, a tunnel is created between a remote computer (TCP source port = 5904) andthe OpenTouch server1ot server (TCP destination port = 5904) via a Putty/SSH tunnel.

Therefore, the remote computer VNC client establishes a connection to the local TCP port 5904(localhost). Note that this single Putty SSH session is used to log on to the OpenTouch server and toactivate the tunnel.

Remote session (Xwindow interface) is possible as long the SSH tunnel is up.

The tunnel is lost when the Putty client software on the remote computer is stopped. However, thecurrent session can be retrieved by restarting Putty/SSH and the VNC client software on the remotecomputer.

14.3.2.2 VNC over SSH configuration setup

In order to provide the above tunnel configuration, a specific Putty setup in necessary.

For the following configuration procedure, the following inputs must be used:

• OpenTouch server: server1ot/192.168.201.131• OpenTouch TCP port for VNC Server: 5904• Remote computer TCP port for SSH tunneling: 5904

The Putty software can be downloaded from several locations such as:



http://www.chiark.greenend.org.uk/~sgtatham/putty/

Note:An alternative to Putty, such as Kitty, can be also used: (http://kitty.9bis.com/).

14.3.2.3 Configuration procedure

1. On the remote computer, install and run the PuTTY SSH client software.2. Configure the OpenTouch server access.

• Hostname (or IP) of the OpenTouch server (Ex: 192.168.201.131)• Name for this session (Ex: server1ot_Tunnel):

Figure 14.4: Host configuration example3. Set the function keys and keypad type to Linux



http://www.chiark.greenend.org.uk/~sgtatham/putty/

Figure 14.5: Keypad configuration example4. Set the remote character set to UTF-8 (default for Linux servers)



Figure 14.6: Character translation configuration example5. Create a tunnel between the local computer port (5904) and the remote server port 5904

(127.0.0.1:5904).

Note:Using 127.0.0.1 is mandatory



Figure 14.7: Tunnel creation 16. Click the Add button.



Figure 14.8: Tunnel creation 27. Go back to the session window and click Save to save your parameters for later use



Figure 14.9: Save configuration example8. Open your SSH connection and log as otuser

Open the newly created SSH connection (server1ot_Tunnel) and log on to the OpenTouch server asotuser.

9. From this SSH console, start a local vncserver by running the following command:

vncserver :4 -localhost -nolisten tcpwhere :

• :4 stands for display number 4.

=> The associated TCP port will then be 5904 (5903 for display 3, …)• -localhost allows only local connections

Only requests on 127.0.0.1 are accepted.

This secures the operation and forbids remote VNC connections.• -nolisten tcp: selects the minimum required opened TCP ports (security reason)

10.When starting the vncserver for the first time, you are prompted for a password. This password isrequested during VNC connection and is independent from Linux accounts.

We can use alcatel-lucent for the password as example.

VNC server configuration example:login as: otuser Using keyboard-interactive authentication. Password: Last login: Tue Mar 29 16:39:46 2016 from 192.168.201.1 ------------------------------------------------ Product : OpenTouch™ Business Edition 2.2 Version : 11.0.013.011 ------------------------------------------------



[otuser@frbreseuroice ~]$ vncserver :4 -localhost -nolisten tcp You will require a password to access your desktops. Password:Verify: xauth: file /home/otuser/.Xauthority does not exist New 'frbreseuroice.eudoc.euroscript.local:4 (otuser)' desktop is frbreseuroice.eudoc.euroscript.local:4 Creating default startup script /home/otuser/.vnc/xstartupStarting applications specified in /home/otuser/.vnc/xstartup Log file is /home/otuser/.vnc/frbreseuroice.eudoc.euroscript.local:4.log [otuser@frbreseuroice ~]$

11.Keep your SSH session opened and start your favorite VNC viewer client software (for example:UltraVNC, TightVNC).

12.Open a VNC connection to local port 5904

Caution:

The syntax to use depends on the VNC software. Check the corresponding documentation.

This syntax can be localhost::5904 or localhost::4

This initiates a local connection to the tunnel "entry" on port 5904 (itself linked to the remoteOpenTouch vncserver).

Figure 14.10: VNC local port connection example13.Authenticate with the password defined for vncserver (here alcatel-lucent)



Figure 14.11: VNC authentication example

The X window is accessible:

Figure 14.12: OpenTouch GUI console via VNC example

Note:In order to minimize data flow in the SSH tunnel, change the background to a light one (for example: one singlecolor instead of the default image). This can be achieved by right clicking on the background and selectingChange Desktop Background).

14.To gain root privilege in a terminal, use: su –l root.

From there, access your applications (SSH ...).15.Once your work is completed, stop the VNC server with the command:

vncserver –kill :4This avoids using unnecessary resources.

Ensure you are logged in as the user who started the VNC server. If logged as a different user, youare informed that the pid file was not found.



14.4 Initial login and password configurationVirtual machine/

Application

Login Default password

Host root letacla1, modified after first login to SLES op-erating system, defined at post-installation.

Host otuser Defined at post-installation.

OpenTouch application otAdmin Defined at post-installation.

OpenTouch application otProfile Defined at post-installation.

OpenTouch application AdminSNMP Defined at post-installation.

OFS Administrator alcatel

vmOXE root letaclaThis default password must be modified at post-installation if the security level is set to 1 or high-er.

vmOXE mtcl mtclThis default password must be modified at post-installation if the security level is set to 1 or high-er.

vmOXE swinst SoftInstThis default password must be modified at post-installation if the security level is set to 1 or high-er.

vmOXE adfexc adfexcThis default password must be modified at post-installation if the security level is set to 1 or high-er

vmManagement administrator

vmManagement ice Sdfghjk1 and modified at post-installation

OmniVista 8770 adminnmc superuser and modified at first connection tothe OmniVista 8770.

vmOMS admin Defined at post-installation.

vmOMS root Defined at post-installation.

After installation, at first login, you are prompted to modify default passwords.



For more information on post-installation, see: Post Installation on page 44.



Chapter

15 OpenTouch network configuration

15.1 OverviewAs of R2.2.1, OpenTouch servers (OpenTouch Multimedia Services or OpenTouch Business Edition)can be networked. The OpenTouch network created allows users of an OpenTouch server to shareOpenTouch services with users of other OpenTouch servers.

The OpenTouch network addresses the OpenTouch server installed either on physical or virtualizedmachines. OpenTouch network deployment is not subject to license control. In an OpenTouch network,OpenTouch servers are called OpenTouch nodes.

In R2.2.1, OpenTouch network deployment is restricted to the following:

• This feature targets mainly Connection users, but Conversation users are also supported within theOpenTouch network

• The OpenTouch network is not compatible with OpenTouch High Availability solution• The OTMC servers cannot belong to an OpenTouch network• Some features are not supported such as:

• Supervision call pickup: only users declared on the same OpenTouch node can be part of asupervision group

• Scheduled video conference: it is not possible from devices in Remote Call Control (RCC) orassociated to SIP extension users. If users join a scheduled video conference, an error messageis displayed.

SIP extension with hardware SIP sets are not supported in OpenTouch (refer to feature list).Only OTC PC configured as a SIP extension is supported.

15.2 DescriptionAn OpenTouch network is defined by a network name, which must be shared by all OpenTouch nodesof the network (see: Declaring the OpenTouch nodes of the network on page 201). An OpenTouchnode can only belong to one OpenTouch network at the same time.

In an OpenTouch network, OpenTouch nodes remain associated to their respective OmniPCXEnterprise communication servers, limited to one OpenTouch node per OmniPCX Enterprisecommunication server. The OmniPCX Enterprise nodes associated to OpenTouch nodes must belongto the same OmniPCX Enterprise subnetwork, and share an homogeneous dialing plan. Associationwith OmniPCX Enterprise communication servers belonging to separate OmniPCX Enterprisesubnetworks is not supported in an OpenTouch network.

OpenTouch nodes within an OpenTouch network maintain two levels of dialog over dedicated links:

• At system level, by discovering users handled by other OpenTouch nodes (called remote users inthe rest of the document), and synchronizing periodically for relevant operations such as usercreation, user deletion and attribute change.

From a given OpenTouch node, remote users are created with a limited set of attributes defined asspecific entries in the node database and associated to their respective remote node. Entries areverified for unicity on the following parameters: user’s login name, directory number and e-mail.

• At user level, by handling remote users as if they were local users belonging to the same node,including:

• Getting extended attributes such as avatar pictures


• Exchanging presence status, sharing IM sessions and collaboration features for users logged into OpenTouch applications

OpenTouch network

‘‘MyOTNetwork’’ ‘‘MyOTNetwork’’

OTMS BOTMS A

OpenTouch network link

OXE C

OmniPCX Enterprise network

OXE D

OXE E OXE F

ABC-F

OTMS GStandalone server

SIP trunk group

OpenTouch network name

Figure 15.1: OpenTouch network example

In the example above:

• OTMS A provides OpenTouch services to Connection users handled by OXE C• OTMS B provides OpenTouch services to Connection users handled by OXEs D and F• OTMS G is a standalone server which provides OpenTouch services to Connection users handled

by OXE E

OpenTouch nodes may be deployed in different sites, possibly in different IP networks. In such aconfiguration, each OpenTouch node must be able to resolve the FQDN of the other OpenTouch nodesacross the network. This requires to declare the FQDN of all other OpenTouch nodes of the network inthe settings of each OpenTouch node (see: Associating the OpenTouch nodes in the network on page202).

15.3 DeploymentOpenTouch network deployment consists in:

• Declaring the OpenTouch nodes of the network on page 201• Associating the OpenTouch nodes in the network on page 202

The OpenTouch network deployment has an impact on the OpenTouch ecosystem. When deploymentis completed, you must adapt theOpenTouch ecosystem configuration to the customer environment(see: Modifying the OpenTouch ecosystem configuration on page 207).

When deployment is completed, you can also:

• Verify that the OpenTouch network is operational: see: Displaying OpenTouch network status onpage 203

Chapter 15 OpenTouch network configuration


• Perform the following operations:

• Removing an OpenTouch node from the network on page 206• Forcing synchronization on an OpenTouch node on page 207• Displaying users of a remote OpenTouch node on page 205

15.3.1 Prerequisites• The stack name of each OpenTouch node must be unique• OpenTouch nodes must not share the same ACS cluster FQDN (that is the conferencing service

FQDN)• The certificates of all the nodes must share the same trusted CA• The ACS node identifier of each OpenTouch node must be unique• OpenTouch nodes must not belong to a High Availability (HA) configuration• All OpenTouch nodes must have the same conferencing access code format (1 or 2 digits)

This is not controlled automatically. The administrator must check this manually• The DNS suffix must be the same for all OpenTouch nodes

All OpenTouch network nodes and/or OmniPCX Enterprises must be synchronized on time (by thesame external NTP source) to get good quality of E2E session synchronization and merge.

Rehosting is required to change stack name and node ID.

15.3.2 Declaring the OpenTouch nodes of the networkThis operation must be performed on each node of the OpenTouch network. It consists in enabling theOpenTouch networking and declaring the name of the OpenTouch network:

1. From the OmniVista 8770 configuration application, select an OpenTouch node and open theConfiguration window

2. Select the Features tab and navigate to: Multi-OT > OT network

Figure 15.2: OpenTouch network configuration window example3. Review/modify the following field:



Is networked Select the check box to enable OpenTouch networking

4. Click the validate icon to save your modification5. Review/modify the following fields:

Network name Enter the name of the OpenTouch network

Synchro interval, min Enter the time interval between two node synchronizations.

Default value: 60 minutes

6. Click the validate icon to save your modifications

15.3.3 Associating the OpenTouch nodes in the networkThis operation must be performed on each OpenTouch node of the network. It consists in declaring thelist of other OpenTouch nodes of the network in the settings of each OpenTouch node:


2. Select the Features tab and navigate to: Multi-OT > OT node

Figure 15.3: OpenTouch node configuration window example3. Access the contextual menu and select Create4. Review/modify the following field:

FQDN Enter the FQDN or IP address of an other OpenTouch nodeof the network

5. Click the validate icon to save your modification6. Repeat this procedure to add all other OpenTouch nodes of the network



The node list must be the same on each OpenTouch node. Once the remote OpenTouch nodes aredeclared, a synchronization is performed between all nodes of the network: each node synchronizesits user data with those of the other nodes.

Example:

An OpenTouch node (B) is declared in the node list of an OpenTouch node (A).Nodes A and B belong to thesame OpenTouch network identified by its name (see: Declaring the OpenTouch nodes of the network on page201):

• Node A synchronizes its user data with those of node B• Node B synchronizes its user data with those of node A• OpenTouch services are available for users of nodes A and B

The synchronization can fail in the following cases:

• The nodes do not comply with the Prerequisites on page 201• Synchronization is interrupted due to a network issue or node shutdown• Data of one single user exists on the two nodes of the network.

Example:

A node C is added to a network including two nodes A and B. Node C has a user, John Smith, alsoavailable on node B:

• When node C synchronizes its user data with those of node B, user Smith of node B is notsynchronized. The synchronization status for node B is: warn

• When node B synchronizes its user data with those of node C, user Smith of node C is notsynchronized. The synchronization status for node C is: warn

• The users of nodes A and B cannot have IM/presence with the user Smith of node C

15.3.4 Displaying OpenTouch network statusThis operation allows to verify if the synchronization with the other nodes of the OpenTouch networkhas been successfully completed.


2. Select the Features tab and navigate to: Multi-OT > OT node



Figure 15.4: OpenTouch network status window example

The following information is displayed for each OpenTouch node of the network. Content differsaccording to the OpenTouch node status:

Node FQDN Indicates the node FQDN

Version Indicates the OpenTouch software version installed on thenode

Status Indicates the status of the last synchronization:

• OK: the node is synchronized• Failed: the last synchronization did not start• Network configuration error: synchronization was not

performed because host is not part of a network or thisnetwork (network name differs)

• Warn: the last synchronization was completed with someerrors

• To be deleted: this node is marked for deletion• Failed to delete: this node was marked for deletion, and

an error occurred during last synchronization

Cause of failure Provides details in case of failure

Last data synchronized, KB Indicates the amount of data synchronized at last synchroni-zation (in kilobytes)

Users synchronized Number of users whose data has been collected at last syn-chronization

Users not synchronized Number of users whose data has not been collected at lastsynchronization



Total users synchronized Total number of users whose data has been analyzed at lastsynchronization

Note:

You can also view the OpenTouch network status by using the netstatus command:

1. Open a root session on the node console2. Enter the netstatus command

Example:[root@frbreseuroice ~]# netstatus OT network name is "networkot1". Remote nodes:No | FQDN | Last sync | Status | Users | Last attempt---------------------------------------------------------------------------------1 | server1ot.eudoc.local | 2016-11-15 15:55:35 | OK | 1/0/1 | 2016-11-15 15:55:35 [root@frbreseuroice ~]#

To get more details on the synchronization status, use the netstatus -a command.

Example:[root@frbreseuroice ~]# netstatus -a OT network name is "networkot1". Remote nodes:FQDN . . . . . . . . . . . . . . . . : server1ot.eudoc.localPrimary ACS node Id . . . . . . . . . : 3Secondary ACS node Id . . . . . . . . : ---Node version . . . . . . . . . . . . : 12.0.009.002Status . . . . . . . . . . . . . . . : OKLast synchro attempt . . . . . . . . : 2016-11-15 15:55:35Last synchro success . . . . . . . . : 2016-11-15 15:55:35Users synchronized (last attempt) . . : 1Users NOT synchronized (last attempt) : 0Total users synchronized . . . . . . : 1Transferred data . . . . . . . . . . : 1KB Synchro duration . . . . . . . . . . : 0.721s [root@frbreseuroice ~]#

15.3.5 Displaying users of a remote OpenTouch nodeAfter synchronization with a remote node, the user data collected for this remote node are availablelocally:

1. From the OmniVista 8770 configuration application, select the OpenTouch node to be deleted, andopen the Configuration window

2. Select the Features tab and navigate to: Multi-OT > Remote user



Only relevant information is displayed for each user. Users can be filtered by selecting the FQDN ofthe remote node to which they belong.

15.3.6 Removing an OpenTouch node from the networkYou can remove an existing OpenTouch node from a network:

1. From the OmniVista 8770 configuration application, select the OpenTouch node to be deleted, andopen the Configuration window

2. Select the Features tab and navigate to: Multi-OT > OT network

The OpenTouch network configuration window opens (see: Figure 2)3. Select the OpenTouch network name, and review/modify the following field:

Is networked Clear the check box

4. Click the validate icon to save your modification

The node is deleted from the OpenTouch network. It means that users of the OpenTouch networkhave no more access to the avatars, presence, and IM of the users belonging to the deleted node. Ifa user of the deleted node was in the favorite list of a user of the OpenTouch network, it remains inthe favorite list as a contact. No action is possible from this contact (for example: send an IM).

In addition, all users of the deleted node are no more available in search results performed onnodes of the OpenTouch network (except when search is performed on favorite lists).

Example:

If at synchronization between two nodes of the network (nodes A and B), node A detects that node B hasdisabled the networking feature, then node A removes:



• Remote users of node B• Network status of node B• Node B from its node list

Deletion takes time to complete: all nodes of the network must detect that a node is deleted andremove its user data from their internal directories. Node is deleted as the next synchronization sessionon each node starts, manually or automatically.

To verify that the node has been successfully deleted from the network, open the configuration windowof a node of the OpenTouch network and verify that the deleted node is not in its node list.

Note:

A node can also be removed manually from the node list.

From the OpenTouch node Configuration window (see: Figure 3), select the node to be removed from the nodelist, and perform any of the following:

• Access the contextual menu and select Delete• Select the Delete at the next synchro check box and validate the modification

At next synchronization, no synchronization is performed for this node:

• Associated remote users are removed• Associated network status is removed• The node is removed

15.3.7 Forcing synchronization on an OpenTouch nodeYou can force the synchronization on a particular node by using the netsync command.

When this command is used on a node, this node synchronizes its user data with those of other nodesof the OpenTouch network declared in its node list (see: Associating the OpenTouch nodes in thenetwork on page 202). Synchronization is bidirectional (two-ways): the node sends its user data toother nodes, which in turn, send their user data to this node.

Force synchronization does not interrupt a scheduled synchronization in progress. Forcedsynchronization only starts when scheduled synchronization is finished.

To force synchronization on a node:

1. Open a root session on the node console2. Enter the netsync command

15.3.8 Modifying the OpenTouch ecosystem configurationThe OpenTouch network deployment has an impact on the OpenTouch ecosystem. The OpenTouchecosystem configuration needs to be adapted to the customer environment:

• UDAS must be configured separately on each OpenTouch node with a common configuration toprovide a common level of service.

• External authentication must be configured separately on each OpenTouch node with a commonconfiguration to provide a common level of security.

• Voice mail service based on Unified Messaging and/or Local Storage can be differentiated on eachOpenTouch node and must be configured separately on each server.

• Conferencing service and DCS must be managed separately on each OpenTouch node. Its accessmust be shared by the local and remote users.

• Other Telephony and video services must be managed separately on each OpenTouch node, andmust only be provided to local users unless specified explicitly.



15.4 Troubleshooting: user synchronization issue due to duplicateddata

During the initial synchronization or incremental synchronization of remote user in the database, thesystem verifies the following parameters of the remote user: user’s login name, directory number ande-mail. If one of this parameter is duplicated regarding an existing user in the database, an error isdisplayed via the netstatus command.

Details on the remote user information is provided in the log file: /logs/cms/cms_networking.log.It indicates which parameter is duplicated. You must then modify one of the profiles to remove theduplicated data.

At the next incremental synchronization, the error status must disappear.



Chapter

16 Update

16.1 Update overviewAn update consists in installing a new software release on an existing system.

A machine having several partitions, two different software releases can be installed on the sameserver using active and inactive partitions.

To perform an update, you can:

• Install the new software release on the active partition. In this case, the system is down during theentire updating process.

• Install the new software release on the inactive partition. A command switches partitions and thesystem restarts on the new release.

The update procedure, using the inactive partition, allows smooth update: system downtime isreduced to datacopy and reboot time.

Note:There is a restriction for the OpenTouch Fax Center (fax software) , see: OpenTouch Fax Center updatespecificities on page 220.

A software update can be launched either from the system itself or from the network, with the ALEDS.This tool enables software updates on the active or inactive partitions of the system. But, partitionswitchover can only be carried out from the system itself.

The server is divided in three partitions:

• The first partition, called the active partition is used for the system in operation• The second partition, called the inactive partition, is used to install major, minor releases• The third partition, called the common partition, hosts OpenTouch data and virtual machines used

by the active partition

Figure 1 show the contents of each partition:


Common partitions

Active partition

. SLES

. OT core

. Fax software

Inactive partition

. SLES

. OT core

. Fax software

OpenTouch Business Edition

. Virtual machine for OMS

. Virtual machine for OmniVista 8770

. Virtual machine for DCS (optional)

. OpenTouch backup

Virtual machine for OmniPCX Enterprise

(active partition)

Virtual machine for OmniPCX Enterprise

(inactive partition)

Figure 16.1: Server partitions

There is no inactive partition for servers with a disk size under 350 Gb.

Note:Two 250 Gb disks belonging to the same RAID1 array are counted as one 250 Gb disk.

16.2 DeliveryALE International delivers new releases on any of the following:

• Physical DVD(s). This requires a DVD drive on the OpenTouch server.

When a DVD is inserted in a drive, the DVD is automatically mounted on the /media/cdrom path.• .iso files for the following components:


SUSE Linux Enterprise Server operating system bootdvd.x.x.xxx.xxx.x86_64.iso

OpenTouch core otx.x.xxx.xxx-1.iso

Fax server OmniTouchFaxServer-x.x.x.x-suse12.iso

OmniPCX Enterprise OXE-xx.xxx.xx.x.iso

OmniVista 8770 8770-<version>.iso

These .iso files must be copied on the OpenTouch server or on a remote server.

Chapter 16 Update


On the OpenTouch server, use of the/var/backup/tmp directory is recommended. With otherdirectories, there is a risk of not having enough disk space for installation.

An iso file must be mounted manually.

To mount an iso file:

• When the iso files are copied to the local server, enter the following command:

mount -o loop,ro /path/xxxx.iso /mounting_pathWhere the xxxx.iso stands for the name of the .iso file.

• When the iso files are copied to a remote CIFS server, enter the following command:

mount -t cifs -o username=AAAA,password=BBBB //server_address/path/xxxx.iso /mounting_pathWhere AAAA and BBBB are the account and the password used to access the remote NFSserver, and the xxxx.iso stands for the name of the .iso file.

According to the update, some components may not change. In this case, the DVD(s) or .iso file(s)for the unchanged components are not delivered.

Note:There is no DVD or iso file for the OXE-MS. The OXE-MS binary is included in the OmniPCX Enterprise binary andis automatically updated when the OmniPCX Enterprise is updated.

16.3 PrerequisitesBefore starting update operations, you must verify the server works properly by launching the followingcommands from a terminal:

• management_cmd check• oxe_cmd checkSolve problems if results are not OK. You must not proceed to the update operations as long as theresult of these commands is not OK.

16.4 Update operationsUpdate operations allow:

• Minor updates or SUSE Linux Enterprise Server operating system updates• To update the application software

Only update operations from the system are described in the rest of the document. For updateoperations from the network via ALEDS, refer to the document [5].

To proceed:

1. Open a root session on the server

Note:

When you are connected with the maintenance account (otuser), you can switch to the root account with thesu - command. The root password is required.

With the su - command, you recover the full root environment.2. To ensure that the entire system is updated, before you carry on:

a. Stop the OmniPCX Enterprise virtual machine

Chapter 16 Update


b. Back it up: for more information on backup, refer to [3] (chapter Backup and restore)c. Start the OmniPCX Enterprise virtual machine

3. When operating with .iso files, each file must be mounted before installation. Typically, mountingpaths are as follows:

• bootdvd.x.x.xxx.xxx.x86_64.iso is mounted on /media/os• otx.x.xxx.xxx-1.iso is mounted on /media/ice• OmniTouchFaxServer-x.x.x.x-suse12.iso is mounted on /media/fax• OXE-xx.xxx.xx.x.iso is mounted on /media/oxe• 8770-<version>.iso is mounted on/media/8770Note:The /media/cdrom directory is reserved for physical DVDs and cannot be used to mount an .iso file.

According to the .iso file location:

• Update from iso files located on a remote CIFS server:

Mount the file, using the command:

mount -t cifs -o loop,ro username=AAAA,password=BBBB //server_address/path/xxxx.iso /mounting_pathwhere AAAA and BBBB are the account and the password used to access the remote server.

where xxxx.iso is the name of the .iso file.• Update from .iso files located on a USB disk:

1. Locate the USB disk:

Enter the fdisk -l command

Result:

Disk /dev/cciss/c0d0: 500.0 GB, 500074307584 bytes255 heads, 63 sectors/track, 60797 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytesDevice Boot Start End Blocks Id System/dev/cciss/c0d0p1 * 1 64 514048+ 83 Linux/dev/cciss/c0d0p2 65 23822 190836135 8e Linux LVM/dev/cciss/c0d0p3 23823 41156 139235355 8e Linux LVM/dev/cciss/c0d0p4 41157 60797 157766332+ 5 Extended/dev/cciss/c0d0p5 41157 58490 139235323+ 8e Linux LVM/dev/cciss/c0d0p6 58491 60796 18522913+ 82 Linux swap / Solaris

Disk /dev/sda: 500.0 GB, 500074283008 bytes255 heads, 63 sectors/track, 60797 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System/dev/sda1 1 60798 488352768 7 HPFS/NTFS

Chapter 16 Update


The location of the USB disk is /dev/sda1.2. Mount the USB disk:

Enter the mount /dev/sda1 /media/usbdd command to mount the USB disk on the /media/usbdd directory

The /media/usbdd directory must have been created previously.3. Mount each .iso file :

Enter the mount -o loop /path/xxxx.iso /mounting_path command wherexxxx.iso is the name of the .iso file.

• Update from .iso files on the OpenTouch server:

Note:This procedure must be used only when the alternatives described above are not feasible.

1. Copy .iso files on the OpenTouch server

Use the /var/backup/tmp directory. With any other directory, you may not have enoughdisk space for installation

2. Mount each .iso file:

Enter the mount -o loop,ro /path/xxxx.iso /mounting_path command.

where xxxx.iso is the name of the .iso file4. Start the graphical interface, using the command:

systemctl start display-manager5. Open a terminal6. Navigate to the mounting path of the otx.x.xxx.xxx-1.iso file7. Enter the ./setup.bin command

The software installation wizard starts and the wizard welcome page is displayed.

Chapter 16 Update


Figure 16.2: Welcome page

Note:

On all wizard pages:

• Next: goes to the next page.• Back: goes to the previous page. The settings of the current page are not lost.• Cancel: exits the wizard

8. Click Next

The wizard checks the system. If it discovers an already installed OpenTouch, the Update typepage is displayed

When no previous version is found on the system, an installation from scratch is started. Seedetails: Software installation procedure on page 39.

Chapter 16 Update


Figure 16.3: Updade type page9. Select the update type:

• Validate the Active option to update the active partition. In this case, the OpenTouch server isstopped.

• Validate the Passive (with Clean Installation) option to update the inactive partition. In thiscase, OpenTouch server current operations, except for those relating to the OpenTouch FaxCenter (see: OpenTouch Fax Center update specificities on page 220), are not affected by theupdate process.

With this option, a full installation, as an upgrade, is performed on the passive partition.However, contrary to an upgrade, there is no need to set up all post-installation parameters andyou retrieve your current system and database from the initial partition by a simple switchovercommand.

10.Click Next. You are prompted to enter the mtcl password of the vmOXE.11.Click Next

The license file selection page is displayed:

Chapter 16 Update


Figure 16.4: License file selection page12.Select your new license file directory:

• If the license file is not changed, click Skip and Next• If the license file must be changed, click Browse to select your new license file directory and

click Next

The summary page is displayed:

Chapter 16 Update


Figure 16.5: Summary page13.Click Next to start update operations

When prompted, insert the DVD or enter the mounting path to the required update.

Click Next to validate. Update operations continue.

When completed, the Installation completed page is displayed:

Chapter 16 Update


Figure 16.6: Update completed page14.Click Finish to exit the wizard15.In case of installation of the new version on the inactive partition, switch partitions using the

switchover.sh command (see: Partitions switchover on page 218)

16.5 Partitions switchoverWhen the inactive partition is loaded, the switchover.sh command switches partitions: the activepartition becomes inactive and vice versa.

To switch partitions:

1. Open a root session2. Enter the switchover.sh --datacopy command:

This command:

a. Displays the status of partitionsb. Requests confirmation (use the -y option to bypass this confirmation)c. When the version on the inactive partition is greater or equal to the version on the active

partition, copies data from the active partition to inactive partitiond. When a new file has not been configured during the update procedure (see: Figure 4), copies

the license file from the active partition to the inactive partition.

Note:When a new file has been configured during the update procedure, this new license file is not overwritten.

e. Switches partitions and reboot

These operations consist of:

Chapter 16 Update


• Reboot OpenTouch server• Start the new OpenTouch server on inactive partition, which becomes active• Restart OmniVista 8770• Restart OmniPCX Enterprise virtual machine on the vmOXE inactive partition which becomes

active• Restart the OXE-MS

3. Verify that the license file has not been erased by the database restore. If necessary, installmanually the new license file again

Note:If switchover fails, rollback to the initial partition is possible (see: Rollback after a switchover fails on page 220).

The switchover.sh command supports the following options:

• --datacopy. With this option, the data from the active partition is copied to the inactive partition. Inaddition, this option translates data to match with the new software.

This operation is only possible when the version of the inactive partition is greater or equal to theversion on the active partition.

In addition, the license file is copied from the active partition to the inactive partition. When a newfile has been configured during the update procedure (see:Figure 4), this new license file is notoverwritten with the datacopy process.

For a first switchover or after a smooth upgrade with or without the Clean Installation option, thedatacopy option is mandatory.

• status. With this option, only partition status is displayed.

Example:

[root@server1ot ~]# switchover.sh status

Current boot partition is SUSE Linux Enterprise Server 12

---------------------

Versions on active partition (SUSE Linux Enterprise Server 12):

BootDVD: 12.0.002.004

ICE: Business Edition - 11.0.009.008

Linux: SUSE LINUX 12 3.12.28-4-default

OXE: l2.300.21.a

---------------------

Version on inactive partition (Partition-2):

BootDVD: 12.1.002.002

ICE: Business Edition - 11.0.013.011

Linux: SUSE LINUX 12.1 3.12.49-11-default

OXE: l2.300.26.e

When the two partitions are not completely detailed, partition switch is disable.• -y. With this option, no switch confirmation is requested• --help. With this option, the different operations triggered by the switchover.sh command are

displayed.

Chapter 16 Update


16.6 OpenTouch Fax Center update specificitiesThe OpenTouch Fax Center server uses data on active and inactive partitions.

For this reason, at the beginning of an update, the OpenTouch Fax Center server is automaticallystopped. The OpenTouch Fax Center server is unavailable during update operations, even whenupdate is performed on the inactive partition.

After update, the OpenTouch Fax Center server must be manually restarted to be available beforepartition switchover.

During a switchover, all servers, including the OpenTouch Fax Center, are restarted.

16.7 Rollback after a switchover failsIf after a switchover, the system boot fails (kernel panic), on the new partition you can roll back to theformer partition:

1. Reboot the OpenTouch

A partition selection screen is displayed

The default partition is the one which causes a kernel panic.2. Use the keyboard arrows to select the former partition3. Press Enter to reboot

16.8 Additional operations on the inactive partition

16.8.1 Presence of the inactive partitionWhen the OpenTouch disk size allows it, two partitions are created at software installation.

To verify the presence of the inactive partition:

Enter the ll /mnt command[otuser@server1ot ~]$ ll /mnt total 52drwxr-xr-x 2 root root 4096 Aug 29 17:11 inactive_partition <============drwxr-xr-x 2 root root 4096 Aug 29 17:39 iso-boot

16.8.2 Partitioning implementationAll the partitions on a volume vg_root_01 or vg_root_02 are duplicated.

The others are common. Common means that their content can be accessed by the two partitions.[otuser@server1ot ~]$ df -hFilesystem Size Used Avail Use% Mounted on/dev/mapper/vg_root_01-lv_root 30G 12G 16G 43% / <=== Duplicated partition/dev/mapper/vg_common-lv_var_backup 107G 4.7G 97G 5% /var/backup <=== Common partition/dev/mapper/vg_root_01-lv_slides 14G 164M 13G 2% /var/data/slides <=== Duplicated p./dev/mapper/vg_root_01-lv_drbd 39.7G 151M 9.1G 2% /var/data/oamp <=== Duplicated p./dev/mapper/vg_root_01-lv_drbd1 21G 184M 20G 1% /var/data/ics-group <=== Duplic./dev/mapper/vg_common-lv_libvirt 97G 71G 22G 77% /mnt/virtualmachines <=== Common/dev/mapper/vg_root_01-lv_ofs 2.0G 68M 1.8G 4% /var/data/ofs <=== Duplicated p./dev/mapper/vg_root_01-lv_drbd2 9.7G 282M 9.0G 3% /var/data/postgresql5433 <=== Dup./dev/mapper/vg_root_01-lv_postgresql 9.7G 218M 9.0G 3% /var/data/postgresql5432 <=== Dup./dev/mapper/vg_root_01-lv_logs 20G 583M 18G 4% /logs <=== Duplicated partition/dev/mapper/vg_root_01-lv_drbd4 124M 5.6M 113M 5% /var/data/moh <=== Duplicated p./dev/cciss/c0d0p1 487M 24M 438M 6% /boot <=== Duplicated partition

Chapter 16 Update


tmpfs 7.9G 4.0K 7.9G 1% /dev/shm <=== Duplicated partition

16.8.3 Reading the content of the inactive partitionYou may need to look at the content of the inactive partition, for example, to read log files.

Note:This operation must be exceptional, as the inactive partition can only be mounted when OpenTouch services arestopped.

To access the inactive partition:

Enter the mount /mnt/inactive_partition command

The content of the inactive partition is similar to the active partition, directories are identical. [root@server1ot ~]# ll /mnt/inactive_partition/total 132-rw-r--r-- 1 root root 0 Aug 27 08:36 0drwxr-xr-x 2 root root 4096 Aug 27 08:35 accessdrwxr-xr-x 2 root root 4096 Aug 28 04:06 bindrwxr-xr-x 2 root root 4096 Aug 27 08:30 bootdrwxrwxrwx 3 root root 4096 Aug 29 11:27 callLogsdrwxr-xr-x 2 root root 4096 Aug 27 08:49 devdrwxr-xr-x 99 900 900 12288 Aug 13 14:30 etc-rw-r--r-- 1 root root 0 Sep 7 07:23 haltdrwxr-xr-x 10 root root 4096 Aug 27 08:53 homedrwxr-xr-x 11 root root 4096 Aug 28 04:05 libdrwxr-xr-x 8 root root 4096 Aug 28 04:05 lib64drwxr-xr-x 5 root root 4096 Aug 27 12:12 logsdrwxr-xr-x 11 root root 4096 Sep 7 06:53 mediadrwxr-xr-x 2 root root 4096 Jul 29 2009 miscdrwxr-xr-x 5 root root 4096 Aug 28 08:02 mntdrwxr-xr-x 5 root root 4096 Aug 27 08:53 optdrwxr-xr-x 2 root root 4096 Aug 27 08:30 procdrwxr-x--- 17 root root 4096 Sep 7 15:14 rootdrwxr-xr-x 2 900 900 12288 Aug 13 14:30 sbindrwxr-xr-x 2 root root 4096 Aug 8 2008 selinuxdrwxr-xr-x 2 root root 4096 Aug 27 08:35 setuplrwxrwxrwx 1 htuser htgroup 17 Aug 27 08:48 slides -> /var/data/slides/drwxr-xr-x 2 root root 4096 Aug 8 2008 srv-rw------- 1 root root 1212 Sep 7 07:23 stdout.log-rwxr-xr-x 2 root root 4096 Aug 27 08:30 sysdrwxr-xr-x 3 root root 4096 Aug 27 08:47 tftpbootdrwxrwxrwx 22 root root 12288 Sep 7 15:13 tmpdrwxr-xr-x 49 900 900 4096 Aug 13 14:30 usrdrwxr-xr-x 28 root root 4096 Aug 27 12:40 var-rw-r--r-- 1 root root 86 Aug 27 12:23 variables

Example of access to the inactive partition: access to log files.

Enter the cd /mnt/inactive_partition/var /log/ICE/InstallLog command

Caution:

When finished with the inactive partition, unmount it.

Enter the umount /mnt/inactive_partition command

If the device is busy error occurs, verify that your working directory is not located in the inactivepartition.

16.9 Log filesLog files can be used to ensure update is successful, or to fix errors.

Log files for update operations are located in: /var/log/ICE/InstallLogs

Chapter 16 Update


The main log files are:

• oxe-update.log• management-update.log• main_setup.log: after an update operation, it is recommended to check that installation was

correct

Example:

03 Sep 2012 07:06:58,687 INFO [main] (IceWizard.java:133) - Dialog returncode is (0=Finish,1=Cancel,2=Error): 0

03 Sep 2012 07:06:58,687 INFO [main] (Configuration.java:1714) -Installation state : The Installation has successfully installed.

• bics-switchover.log• aluprestart.logIn case of update on inactive partition, before the switchover operation, log files are:

• /mnt/inactivepartition/var/log/ICE/Installation/oxe-update.log• /mnt/inactivepartition/var/log/ICE/Installation/management-update.log• /mnt/inactivepartition/var/log/ICE/Installation/aluprestart.log while

main_setup.log remains the same

Chapter 16 Update


Chapter

17 Upgrade

17.1 OverviewThis chapter describes the upgrade of the OpenTouch Business Edition.

An upgrade consists in installing a major release of an OpenTouch on a system where a previousrelease of the OpenTouch has been installed. Upgrades can include the installation of a new version ofthe Linux operating system. An upgrade is also performed when the hardware configuration of theserver has changed. For readability purposes, the server hosting the OpenTouch Business Edition iscalled the OpenTouch server in the rest of the documentation.

Upgrading the OpenTouch from R2.0.2 or higher to R2.2 or higher consists in:

1. If necessary, upgrading the OmniVista 8770 VM: see Upgrading the OmniVista 8770 virtual machineon page 224

2. Performing the backup of OpenTouch Business Edition (OpenTouch, OmniVista 8770 andOmniPCX Enterprise):see Backing up the database of the OpenTouch server on page 226

3. Installing OpenTouch from scratch: Installation from scratch on page 224. Performing the post-installation procedure using the Restore from archive option.

For more information on the post-installation procedure, see: Database restoration during post-installation on page 226

5. Manually installing the license file, if not already done during post-installation.

Upgrading the OpenTouch from R2.0.1 or lower consists in:

1. If necessary, upgrading the OmniVista 8770 VM: see Upgrading the OmniVista 8770 virtual machineon page 224

2. Performing the backup of the OpenTouch: see Backing up the database of the OpenTouch serveron page 226

3. Installing OpenTouch from scratch: Installation from scratch on page 224. Performing the post-installation procedure, as described in OpenTouch Business Edition server post

installation on page 455. Database restoration after post-installation on page 228

This restore operation translates the saved data to match with the new software.6. Installing manually the license file, if not already done during post-installation.

Note:

Customized voice prompts are deleted after the upgrade procedure.

If need be, to avoid losing customized voice prompts, save them, and upload them again after the upgrade.

17.2 Software requirementFor upgrades, ALE International delivers DVDs or *.iso files for the following components:


SUSE Linux Enterprise Server operating sys-tem

bootdvd.x.x.xxx.xxx.x86_64.iso

OpenTouch Business Edition otx.x.xxx.xxx-1.iso



OmniVista 8770 3.0.<version>.zipOTBEVM_Management-x.x.xxx.xxx-1.isoOTBEVM_Management-x.x.xxx.xxx-2.iso

OmniPCX Enterprise OTBEVM_OXE-x.x.xxx.xxx.iso

OXE-MS OTBEVM_OMS-x.x.xxx.xxx.iso

OpenTouch Fax Center (Fax software) OmniTouchFaxServer-x.x.x.x-suse12.iso

According to the upgrade to perform, some components may not change. In this case, the DVDs or .isofiles for the unchanged components are not delivered.

17.3 Upgrading the OmniVista 8770 virtual machineTo upgrade the OmniVista 8770 virtual machine (vmManagement):

1. From the OpenTouch server, connect to the OmniVista 8770 virtual machine, as described: Connection to vmOXE, vmOMS and vmManagement virtual machines on page 185

2. Upgrade the OmniVista 8770 server with the new OmniVista 8770 software version delivered(3.0.<version>.zip) and new licenses

17.4 MIC mobile recognition in R2.2 (or higher)As of R2.2, mobile clients from the previous generation ("MIC Mobile") do not work anymore.

When the OpenTouch is upgraded, the system:

1. Cleans the database and removes all previous information related to MIC Mobile management (datamodel, user/device association, associated resource)

2. Changes the recognition of these devices and switches them from MIC Mobile to OTC smartphonewhen possible

This applies to all users: Connection and Conversation users.

table 17.1: OpenTouch server perimeter

OpenTouch server release OpenTouch R2.2 Migration Path for Old-generation MIC MobileClients

As of R2.0.x Supported

As of R2.1.x Supported

Chapter 17 Upgrade


table 17.2: Automated device modification

From To Comments

iPhone registeredas Any Mobile

OTC smartphone(iPhone type)

Supported

Prerequisite: Any Mobile devices must be identified be-fore migration. From the OpenTouch configuration appli-cation of OmniVista 8770, select the devices to switch toOTC smartphone and set the Device comment field tothe otciphone value.

MIC v3 iPhone OTC smartphone(iPhone type)

Supported.

Uninstall MIC v3 and download OpenTouch Conversationapplication from the Apple Store

The client binary must be updated on the smartphone

MIC v3 Android OTC smartphone(Android type)

Supported.

Uninstall MIC v3 and download OpenTouch Conversationapplication from the Google Play


MIC v3 BlackBerry Any Mobile Supported.

If BlackBerry device is kept, no more application used,but ringing only

MIC v4 Android OTC smartphone(Android type)

Supported.

Uninstall MIC v4 and download OpenTouch Conversationapplication from the Google Play


MIC v4 BlackBerry Any Mobile Supported.

If BlackBerry device is kept, no more application used,but ringing only.

MIC Nokia No user profile cre-ated

No ringing capability.

Data model is definitively deleted

MIC Windows Mo-bile

No user profile cre-ated

No ringing capability.

Data model is definitively deleted

The operations above are performed at constant perimeter license (type and number) and withoutlicense handling at ACTIS level.

Recommendations:

The OTC smartphone devices are identified by a GSM number in canonical format (for example: +33(0) 612345678). The system sets the GSM number during the upgrade; if it is unable to compute thecanonical number then it sets a fake GSM number in the following ranges:+1<201..210>5550<100..199>.

Chapter 17 Upgrade


The GSM number is computed (in canonical format) based on the following:

• The dialing rule associated to users• The Device number or GSM number attribute depending on the former device type:

• OTC smartphone / former MIC v3 iPhone and Android: Device number attribute• OTC smartphone / former MIC v4 Android: GSM number attribute• Any Mobile / former MIC v3 BlackBerry: Device number attribute• Any Mobile / former MIC v4 BlackBerry: GSM number attribute

It is recommended to save the GSM numbers before migration.

Troubleshooting:

Verify that there is no migration failure in the migration.log file available on the OpenTouch server(directory: /logs/cms). Open the log file and search for the words WARNING and ERROR.

17.5 Backing up the database of the OpenTouch serverNote:Before proceeding to the database backup, check that the vmManagement has been updated to the requiredupgrade version (see Upgrading the OmniVista 8770 virtual machine on page 224).

To save your database on an external media:

1. From the OpenTouch server, open a root session2. Specify your external media as follows: enter the ot-config.sh --storage command and

follow the instructions on screen

Note:For more information, refer to the OpenTouch administrator manual [3]

3. Enter the otbr.sh backup or otbr.sh backup appliall command

Data, from all applications of the OpenTouch server, is saved on the external media defined by theot-config.sh command.

17.6 Installing OpenTouch1. Install the OpenTouch from scratch, as described in: Installation from scratch on page 222. The post installation wizard is automatically started at the first boot of the OpenTouch server:

• If upgrading from R2.0.1 or lower, follow the post-installation procedure, as described in serverpost installation on page 45 and restore the database, as described in Database restoration afterpost-installation on page 228

• If upgrading from R2.0.2 or higher to R2.2 or higher: follow the post-installation procedure andrestore the database, as described in Database restoration during post-installation on page 226

17.7 Launching the OpenTouch server database restoration

17.7.1 Database restoration during post-installation1. Click Next in the post installation wizard welcome page

The Post-Installation Type window displays

Chapter 17 Upgrade


2. Before selecting the Restore from archive option, you must specify the storage media where thebackup data is present:

• If the storage media is an external USB disk, enter the ot-config.sh --storage commandand follow the instructions on screen

Note:The USB disk on the remote server (including folder sharing) must be configured before launching adatabase restoration. For more information, refer to the Backup and restore section of the document [3].

• If the storage media is an NFS directory located on a remote server:

1. Create a directory restore in /media using the command: mkdir /media/restore2. Mount the access to NFS in /media/restore

Example: mount -t nfs <NFS server IP address>:/<path to NFS mountpoint>/ /media/restore/

• If data is stored on a remote computer, it must be exported on the local disk of the OpenTouchserver before restoration:

1. Open a file transfer software and launch an SFTP connection to the OpenTouch server (rootsession)

2. Transfer data from the remote computer to the OpenTouch server in the followingfolder: /var/backup/bics/save/datasave/host

3. Once the storage media is selected and configured, select Restore from archive In the Post-Installation Type window

Additional options are displayed4. In the Archive part, use the browse button to select the directory on which data is present

The server takes few minutes to retrieve data from the storage media and verify the availability ofthe BiCS.conf file.

5. If required, modify the current keyboard type and user accounts (root and maintenance)

Note:At this stage, you can renew the user accounts that will be updated in the database at the end of therestoration.

Chapter 17 Upgrade


6. Click Next

The License Server Settings page is displayed.7. Use the Browse button to select the license file

Caution:License is mandatory for OpenTouch server upgrade. If you skip the license during the post-installation wizard, the upgrade runs into a loop.

8. Click Next

The Summary page displays9. Click Next to launch the restoration

The screen displays the execution of restoration scripts

Note:

You can also access more detailed logs and follow the progress of the restoration operation via an SSHconnection. Enter the root password configured during the OpenTouch server software installation and launchthe following command:

tail -f /logs/bics_applications/bics-postinstall.log

In the log file more detailed information is provided. The restoration is complete when the following informationis displayed: End of 99-endpostinst.sh

The OpenTouch applications are restarted automatically and the database is restored.

17.7.2 Database restoration after post-installationIf the database has not been restored at post-installation, using the Restore from archive option,proceed as follows:

1. From the OpenTouch server, open a root session2. Stop services: enter the service opentouchd stop command3. Specify the external media where the backup data is present, using the ot-config.sh --

storage command and follow the instructions on screen

Note:For more information, refer to Document [3] OpenTouch Administrator Manual - Maintenance and Supervision -Backup and Restore - Configuring the backup media).

4. Copy backup data to the media configured above5. Enter the otbr.sh restore or otbr.sh restore appliall command

Data of all applications of the OpenTouch server is restored from the media configured by the ot-config.sh command

Note:Before restoring data on vmOXE, ensure that the telephone service is stopped. Use the swinst tool onvmOXE to display the telephone status.

6. Reboot the system

Note:The restore process includes translation operations. These translations are used when backup files are createdfrom a former release. Translation makes backup application data compatible with the upgraded software.

Chapter 17 Upgrade


Chapter

18 Troubleshooting procedures andguides

18.1 Virtual machine problemsProblem Description Action

First installation fails Impossible to ping usingIP addresses

Check the Ethernet network cable. It must be plug-ged on the Ethernet port numbered 1 at the rear ofthe OpenTouch server (corresponds to Eth0 in theLinux system)

Impossible to ping usinghostnames

If local DNS is used, restart it using the commandservice named restart when as logged asroot.

If external DNS is used, verify that it is accessiblevia the IP network, that it is running and configuredcorrectly (verify/configure if the host and VM entriesare specified in the DNS table)

The OmniPCX En-terprise is malfunc-tioning

License check failure

(OmniPCX Enterprise inpanic state)

Execute the spadmin command on the OmniPCXEnterprise

The possible causes for malfunction are:

• The Ethernet cable is not plugged on the Ethport numbered 1 at the rear of the OpenTouchserver

• The USB dongle is not plugged (as of R2.0, onlyfor virtualization packages)

• The product id does not match.

The product_id returned by the spadmincommand (option 2 Display active file) mustcorrespond to the Product_id written in the<xxxx>.k2 license file

• There is a Flex-id (as of R2.0, only forvirtualization packages) or ALUID (as of R2.0,when OpenTouch is installed on a physicalmachine) and hostname difference in the<xxxx>.k2 license file

• System/License parameters are not correct.

The expected values are:

• FLexLM Licensing Enable = Yes• FLexLM Server IP address = <host IP

address>• Flex Server Port = 27000• Product ID discovery = Yes


Problem Description Action

General Applicationmalfunctioning

The behavior of the appli-cation is abnormal, butcorresponds to a knownmalfunctioning

Refer to the troubleshooting documentation for theproduct

The behavior of the appli-cation is abnormal, butcorresponds to an un-known malfunctioning

Ensure that unknown services (not supported byALE International) are not running in the Host Oper-ating System. This can be, for example, a VM notused by the OpenTouch product.

Restart the VM. If the problem remains, call theTechnical Support to help you. You may be told toreplace the VM considered corrupted.

VM Backup fails VM still running Stop the VM before making the backup

Not enough disk size Remove unneeded files from the USB Disk

Disk unplugged, not de-tected by the system ornot mounted

See USB problems on page 235: USB Disk mount-ing fails

VM Restore fails VM still running Stop the VM before making the restoration

No VM backup on theUSB disk

Restart the VM, and execute the associated backupagain

Disk unplugged, not de-tected


Application backupfails

The VM involved is notresponding

Check the Ethernet cable (must be plugged on theEth port numbered 1)

No Application backup onthe USB disk

Restart the VM, and execute again the associatedbackup



Backup is interrupted toprompt password

Contact the Technical Support (the RSA key mustbe restored and copied into the host and each VM)

Application restorefails

The VM involved is notresponding

Verify the Ethernet cable (it must be plugged on theEth port numbered 1)

No Application backup onthe USB disk

Restart the VM, and execute the associated backupagain

Chapter 18 Troubleshooting procedures and guides





Backup is interrupted toprompt password

Contact the Technical Support (the RSA key mustbe restored and copied into the host and each VM)

Application/OScrashed in the VM


If the application and/or the guest OS crash and theVM is running, restart the associated VM. If it doesnot solve the problem, call the Technical Support.You may have to replace the VM considered corrup-ted or to upgrade the application,a nd/or the Operat-ing Systems.

VM crashes or doesnot respond


If the VM is not running in the Linux OS (processdisappeared), restart the associated VM. If the prob-lem remains, restart the OpenTouch server. If itdoes not solve the problem, restore the last savedVM (with its data).

VM corrupted Impossible to start theVM

Try another time, directly from the OpenTouch serv-er console

If the problem remains, restore the last saved VM(and restore the last saved data).

Command SSHfrom host is notworking

ssh ice@<vmMa-nagement IP>"set"| grepNMC_HOME

ssh: connect to host @IPport 22: No route to host”

Management VM is not started or its network is notcorrectly defined.

ssh: connect to host @IPport 22: Connection re-fused

Verify in the VM that the service Openssh SSHD isstarted (using services.msc):

• If the service is started, verify the rules for port22 in the firewall.

• If the service is not started, verify theconfiguration files in C:\Program Files(x86)\ICW\etc. sshd_config must be thesame as in C:\temp\postinstall\copssh\...generated\sshd_config.




ice@IP's password:” A password is requested, the public key is not cor-rect:

• Verify that the account ice has been created, inC:\Program Files (x86)\ICW\home.There must be an ice folder. If this not the case,you must declare the ice account:

Enter the command: C:\Program Files(x86)\ICW\bin\copsshadm - cactivateuser -u ice --shell /bin/bash -- passphrase "I am the iceadministrator"

• Verify that a public key has been defined in theroot account:

• Enter the ls ~root/ssh command

You must see the files id_rsa andid_rsa.pub.

• If this is not the case, generate the privateand public keys:

Enter the ssh-keygen –t rsa command

You can use any passphrase (or nopassphrase), but ensure you always use thesame

• Copy the root public key in C:\Program Files(x86)\ICW\home\ice\.ssh\...authorized_keysFrom the host, with the root account, enter thecommand: management_cmd updatekey (theice password is required)

• Check that the environment file in the C:\Program Files (x86)\ICW\home\ice\.ssh directory is created.

If this is not the case, open a command window:

• Navigate to C:\Program Files(x86)\ICW\home\ice\.ssh

• Enter the set > environment command

NMC_HOME='C:\8770 All is ok




Otbr restore or re-storeData returnserror

RestoreContext.ini filesare not the same : -nmcVersion :8770.1.0.ww.xx !=8770.1.0.yy.zz

The OmniVista 8770 forbids restoring a databasethat was saved with a version different than the cur-rent version. In case of OpenTouch reinstallation,you need to upgrade the OmniVista 8770 with the fi-nal version, in the previous installation, before otbrbackup or saveData operation.

Verify the version of the OmniVista 8770 in thenmcVersion field of the backup folder (save/data-save/WIN/xxxx/8770_ARC/...8770Backup/xx xx/RestoreContext.ini) .

Otbr backup or sa-veData returns error

com.alcatel_lucent.nms8770.infra.ldap.connection.NmdLdapException:Failed to connect to theLDAP server.”

• Restart the Sun Directory Server EnterpriseEdition 7.0 using OmniVista 8770\Tools\ServiceManager.

If this is ok, relaunch otbr backup or saveData.• Verify why the Sun Directory Server Enterprise

Edition 7.0 is not running. Logs are saved in theC:\8770\SunONE\slapd- 8770\logs\errors directory.

If you find a message such as Databaseversion mismatch (expecting 'Sun-ldbm/7.0' but found in directory C:/8770/SunONE/slapd-8770/db/nmcroot),open the C:\8770\SunONE\slapd- 8770\db\nmcroot\DBVERSION file and add the lineSun-ldbm/7.0 Windows_NT 6.1 x86.Restart the LDAP server, then relaunch otbrbackup or saveData.

18.2 Host problemsProblem Description Action

Host parameters Back-up/Restore fails


See USB problems on page 235: USB Diskmounting fails

Server crashed

Host Linux crashed

The system has auto-matically restarted

Analyze the cause in the system log files

The system cannot re-start

The repair procedure must be executed.




Disk crashed An error message in-forming about a “diskfailure” is displayed inthe system consoleor /var/log/messagefile or during reboot

Thanks to RAID1, only the crashed disk must bereplaced. Nothing to do. The mirroring of the sec-ond disk is automatically rebuilt.

Server is halted (in caseofUPS use)

UPS battery is empty(UPS is also halted)

OpenTouch server will start automatically oncepower supply is up again.

File system checksseen during server’sstarting

A power cut has beencaused without execut-ing a proper shutdown

If file system checks can be done, there is noth-ing to do.

If not, a repair procedure may be necessary to re-cover a normal state.

Check also if there is no file system checks in VMwhen starting (refer to corrupted VM problem)

Root/administratorpassword lost

Boot in rescue mode (see Red Hat Administratorguide)

xxx command not found xxx command limited toroot use

xxx command must be executed as root with fullpath name: /opt/Alcatel-Lucent/serv-iceability/bics_application/bin/xxx

OpenTouch commandaccess right denied

User has no right to ex-ecute the command

OpenTouch commands must be executed as root

Power redundancy(UPS, Pack battery)failed

UPS failed to rescueOpenTouch server dur-ing a power cut

Refer to “File system checks during server’sstarting” problem

Be careful: the used UPS may be not recommen-ded and supported. It is necessary to use theUPS recommended by Alcatel-Lucent.

Check the UPS connections to OpenTouch serv-er (refer to technical documentation)

Follow the procedure described in §2.16 to verifythat UPS is correctly managed and operational



18.3 USB problemsProblem Description Action

USB Disk mounting fails

(mount /media/usbdisk fails)

Disk unplugged Plug and start the USB disk

Disk not detected by thesystem (no informationin the system consoleor /var/log/messag-es file when the disk isplugged and/or startedor on OpenTouch re-boot)

Check the existing partition(s) on the disk: atleast one non-NTFS partition is required.

USB disk mounting fails(information isin /var/log/messageswhen the disk is plug-ged or on OpenTouchreboot, but no relatedentry exists in /etc/fstab)

Unplug/plug the disk. If necessary, power off thedisk and power it on again. If the problem re-mains, restart the OpenTouch server.

USB Disk partition fails Not enough disk size Minimal Space Disk required: 250Gb


See USB problems on page 235: USB Diskmounting fails

Installation procedurestops

USB plugged in at an in-appropriate time

Plugging in a USB disk can create confusion dur-ing the installation procedure. For example, if theUsb Disk is plugged on the server during Linuxinstallation, after the hardware detection steps,the installation stops because a new disk can berecognized as the installation destination.

18.4 Flexlm server problemsWhen license files are not correct, delete them and copy the new license files from the USB keyto /var/data/licenses.

In the VMOXE virtual machine, if the license file (<xxx>.swk) is not correct, delete it and copy a correctlicence file to the /DHS3dyn/BACKUP/OPS directory. Use the swinst tool (swinst > OPS >Restore OPS) to install the license file.

Then follow the procedure:

1. Plug in the USB dongle (as of R2.0, only for virtualization packages)2. Plug the Ethernet cable on the Eth port numbered 1 at the rear of the OpenTouch server3. In a terminal console to the OpenTouch host, stop the flexd service:

• Enter the su - command with the associated password



• Enter the service flexd stop command4. Wait at least one minute before restarting the flexd service:

Enter the service flexd start command5. Check the FlexLM server, which must be up:

• Enter the /opt/Alcatel-Lucent/platform/flexlm/lmutil lmstat –cfor_each_licence_file command

• Enter the ps -edf |grep lmgrd command.

lmgrd and ALCFIRM processes must be running.

If these verifications fail, verify the content of the license files (it must be consistent with the OpenTouchhostname, the Flex-Id of the USB dongle (as of R2.0, only for virtualization packages) or the ALUID ofthe OpenTouch server (as of R2.0, when OpenTouch is installed on a physical machine)), correctmistakes if needed and restart the procedure.

Verify that the OmniPCX Enterprise license is OK by executing spadmin / option 3 (checkactive file coherency) on the OmniPCX Enterprise.

The expected answer is: File is Ok

18.5 Removing a deployment packageIt is possible that a deployment package needs to be removed in the case of tests or verifications. Thereinstallation of the package can only be achieved if the removal is complete.

A second deployment can return a “success” status as it is still detected as present on the OpenTouchsystem.

This section only describes the removal procedure as the standard deployment procedure applies oncethe package has been fully removed.

To remove a package

1. From the Devices application, click the Deployment Package tab2. Expand the tree structure to display the packages3. Select the former package to which devices were attached. (before being attached to the package

to remove)4. Click the Devices line and click the selection button

A search window is displayed.5. Click the Magnify icon to display the list of devices and select the devices (the devices that are

currently attached to the package to remove) to which the package must be applied, then click OK6. Click the validate icon to save your modifications7. Right click the package and select Deploy Package.

The Task Type window is dislayed.8. Select Simple job

A scheduler window is displayed.9. Leave the values unchanged to deploy immediately and click OK10.Still in the package tree structure, right click the package to remove and select Delete Package11.Open the OpenTouch configuration window12.Expand the tree structure to “System services\Applications\Device management\Application

profile”



13.Click on the application profile you want to remove (its name is composed of DM package nameand creation date). The Application(s) field contains the name of the device application to removelater.

14.Right click on the application profile to remove and select Delete15.Expand the tree structure to “System services\Applications\Device management\device

application”16.Right click the device application to remove (see step 13.) and select Delete.

Note:

You can verify on the OpenTouch system that operations were performed correctly by checking that:

• /var/data/oamp/cms/incoming directory is empty• /var/data/cms/DeviceDeployment/fwictouch does not contain the application profile xml file or the device

application directory

If either is present, remove them manually.



Chapter

19 Decommissioning

This document describes how to technically decommission an OpenTouch system, removing all end-customer data from the server, or from the datacenter in case of installation on virtual machines.

Two procedures are detailed:

• Decommissioning a non-virtualized OpenTouch server on page 238• Decommissioning a virtualized OpenTouch server on page 241

At the end of these procedures: all configuration and user data (voice mails, conference recording etc),and all log files are irreversibly deleted, except for backup copies.

It is the responsibility of the Business Partner/Service Provider and the customer to ensure that allcopies of data are properly deleted. In case of hosted/cloud environments, it is the responsibility of thecustomer and Service provider to define by contract how customer data deletion can be proven.

19.1 Decommissioning a non-virtualized OpenTouch serverTo decommission a non virtualized OpenTouch Business Edition/OpenTouch Multimedia Servicesformat the server:

1. Go to a terminal console connected to the server2. Insert your boot DVD3. Reboot the server

The language selection menu is displayed

4. Select your language

A selection menu is displayed


5. Select Rescue6. Login to the system as root

7. Launch the decommissioning command: dd if=/dev/urandom of=/dev/sda bs=4096

Chapter 19 Decommissioning


8. At the end of the process, you are brought back to the start prompt9. Eject the DVD

10.Power the server off



19.2 Decommissioning a virtualized OpenTouch serverSuppress the OpenTouch virtual machines. This erases all OpenTouch data.



Date post:	15-Aug-2021
Category:	Documents
Upload:	others
View:	2 times
Download:	0 times

OpenTouch Business Edition enterprise/ale... · 2017. 11. 14. · OpenTouch Business Edition OTBE...

Documents